[aur-general] Merging request.
Could elementary-icons-bzr be merged into elementary-icon-theme-bzr to be in sync with elementary-icon-theme from [community] ?
On Fri, Aug 23, 2013 at 7:12 PM, Jagmjp Janpgm < darkelfdarkelf666@yahoo.co.uk> wrote:
Could elementary-icons-bzr be merged into elementary-icon-theme-bzr to be in sync with elementary-icon-theme from [community] ?
Merged, thx. -- Maxime
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys,
Could elementary-icons-bzr be merged into elementary-icon-theme-bzr to be in sync with elementary-icon-theme from [community] ?
Merged, thx.
Let me join the discussion here, as I'm concerned by this merge. I've installed the elementary-icons-bzr package a few days ago from the AUR repository. After the merge to elementary-icon-theme-bzr occurred, with the current AUR implementation, the AUR helpers like yaourt cannot intercept a warning from the AUR stating that the package name has changed. It's a good thing I've subscribed to this mailing list and I'm reading all messages that transit via my mailbox. Without this subscription, I wouldn't have been aware of that name change and my package would remain installed and become outdated with time. Am I doing something wrong? How to prevent that to happen? Is there a tool to circumvent this AUR implementation problem? Regards, - -- William Gathoye <william@gathoye.be> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQIcBAEBAgAGBQJSF+77AAoJEA595SwE1xaD/rkQAN19mEZD4Dla/Euo7wnnfZpN OvZXTmeFdjD9lQDbSfQudobCIov1QNMgc6BY5GLA4DlbTS06xOwsd51GbmzeFaw9 Ik7vdJvWfR848zs34sDwrQGIIoiKqnb8z0ltGOfgcf2U2jlLFu9STSzZVbKhZMQs ygp6TzhAH4SFbWDQ9sGSIuJ2EErlv+Gdau/OQram6JjLPErM86oKa6IVE+NKvf2H Iwn0Ub5myZCwsITWrd2e6HkJ82YMGO/oM5r1UT5ixTB3CGgpE3+0OFrp7U4hNzZE b6WHEK+w8wWcpZoQ5pB3jrgmfw30GUwvC6oSM9YJKRLGIah6N73HazOSXV4vTfsJ fJhjjIg1nzGatykaXBhHPkZpPzhwPcGm5wu2TZUuFwMsqxdvZovnAisrlEvar/9q 1O8PE7esP8nAsRw7u4eypCd1+RTTqctTVN5Jx1gjcS9E331AvlynZYgXbnnuc8X9 cMEo1Gfxs7SyhSLTd3oZpbdZxp65qJzcuMMAqJkyOg+PE8qJJiUYcXe5xLC/v2Xs jBk1Wvonv5F/8mhw+c+RPvZlI3+I+boK4UMFK4IQKcWknEc6nm8pryu0Z7bgTTQD i7yWU4xDbO0372Fn/pSYhbc8Bn8GJ6dvSQcK1+eEru1mdvQEpba1Rss9jkiX3HE6 qaxG6Y7jVZqg4hfMb2QO =6oq0 -----END PGP SIGNATURE-----
On 24 Aug 2013 07:23, "William Gathoye" <william@gathoye.be> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi guys,
Could elementary-icons-bzr be merged into elementary-icon-theme-bzr to be in sync with elementary-icon-theme from [community] ?
Merged, thx.
Let me join the discussion here, as I'm concerned by this merge.
I've installed the elementary-icons-bzr package a few days ago from the AUR repository. After the merge to elementary-icon-theme-bzr occurred, with the current AUR implementation, the AUR helpers like yaourt cannot intercept a warning from the AUR stating that the package name has changed.
It's a good thing I've subscribed to this mailing list and I'm reading all messages that transit via my mailbox. Without this subscription, I wouldn't have been aware of that name change and my package would remain installed and become outdated with time.
Am I doing something wrong? How to prevent that to happen? Is there a tool to circumvent this AUR implementation problem?
It's not an implementation problem, it's a usage problem. If you subscribe to notifications from the package you'd receive a notification. Good aur tools can always alert you if the package is no longer found. Ask their developers. The aur is not supposed to be used as just another repository (like how yaourt and Co pretend it is), more manual intervention is needed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
It's not an implementation problem, it's a usage problem. If you subscribe to notifications from the package you'd receive a notification. Good aur tools can always alert you if the package is no longer found. Ask their developers.
The aur is not supposed to be used as just another repository (like how yaourt and Co pretend it is), more manual intervention is needed.
After your comment, I decided to look in the yaourt help. I solved my problem by changing DETAILUPGRADE=1 to DETAILUPGRADE=2 in my /etc/yaourtrc file. Now yaourt is warning me when a package has been orphaned, flagged as out of date or not found. Thanks, - -- William Gathoye <william@gathoye.be> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQIcBAEBAgAGBQJSGLO/AAoJEA595SwE1xaDmlYP/RmQ9irIfq/mrsh5nrHUM7Bp MTSxP4pKH5gtyKzgrJO1+ToB5FHzJu4G/9SSVN0ksMEpgEMzCK1Du7VTQPiFuN8p BJWB1xQJX7KsC1mR3wRL90mRsTqdsgR1rBHDLFcu6MJCtfroweOJkLcZPeWqSHmG yMeLdm8ywsVqwKLx4AsWlRq2eNejvsNBtDvBpj5KT4oOT3PgmXtx7vEKlfMGHT3Q gm+VMCg+DD/FxMYN0l7eIFafuHkIx1v2OocwIRKt8ChG39PZnhhP7yoAd9ngU1Oi WmAreHRV62NrsH3dPsvpyTvSPas0DA+Pt2aBQlSrk+T6FgU8Jx12L+fqftjQIPg7 B8btp8P7It3v9TcpX+EpFUtEGJC4/qQmlFzkGYJeGqW0yHGVp7Qc6/yOmGkpwYHt Jjjw3ADaNyXbDtBMypeI0ry58DngS3rhsDvcr96iL3FMooiSVDSBMi0L69+J1Huw 0BZi3mJS7kBThzlB0OkDK88Wa188ABwcQKRrhdV6A6lnkJ6KNH+maO4THRiwBYHj DKiMc+1ozqJikWAWcMvi13qtB5IHmZcDVQwA7KJ7R0bpthh68sstGUYTVMWu2tp5 i8AKyt1HZ8iOwvcgLwTSsYmjv8D86BTNUahSWcnd0SAnhLUn23K3F9Y3N1es92PS lOulza84mMg7oJEzXV3K =lYwj -----END PGP SIGNATURE-----
participants (4)
-
Jagmjp Janpgm
-
Maxime GAUDUIN
-
Oon-Ee Ng
-
William Gathoye