182551 2007-06-19 08:45 0000 gnome-base/gnome-2.18.0 needs some keywords loving on hppa 2007-06-22 21:47:03 0000 1 1 1 Unclassified Gentoo Linux Ebuilds 2007.0 All Linux RESOLVED FIXED P2 normal --- 1 jakub@gentoo.org hppa@gentoo.org gnome@gentoo.org jakub@gentoo.org 2007-06-19 08:45:26 0000 gnome-base/gnome-2.18.0: nonsolvable depset(rdepends) keyword(~hppa) profile (default-linux/hppa/2007.0): solutions: [ >=gnome-base/gnome-volume-manager-2.17.0, >=gnome-extra/gnome-screensaver-2.18.0, >=app-accessibility/orca-2.18, >=gnome-extra/gnome-power-manager-2.18.0 ] jer@gentoo.org 2007-06-21 14:32:16 0000 Why were keywords for all of these dropped in the first place? Unbelievable that this keeps happening without notice to the relevant arch team.. jer@gentoo.org 2007-06-21 14:58:14 0000 http://devmanual.gentoo.org/keywording/index.html "Sometimes you may need to remove a keyword because of new unresolved dependencies. If you do this, you _must_ file a bug notifying the relevant arch teams." For one thing, it's not clear for which dependencies the keywords were dropped in the first place, and secondly, the HPPA team wasn't notified. :\ remi@gentoo.org 2007-06-21 17:47:48 0000 I haven't looked at ChangeLogs or anything, but it's possible that if you keyworded those packages after we forked our gnome ebuilds, we may have forgotten to add those in our 2.18 ebuilds when we merged. In which case it's an honest mistake. jer@gentoo.org 2007-06-22 21:47:03 0000 (In reply to comment #3) > I haven't looked at ChangeLogs or anything, but it's possible that if you > keyworded those packages after we forked our gnome ebuilds, we may have > forgotten to add those in our 2.18 ebuilds when we merged. *gnome-2.18.0 (09 Apr 2007) 09 Apr 2007; Remi Cardona <remi@gentoo.org> +gnome-2.18.0.ebuild: gnome-2.18.0 meta ebuild Shouldn't repoman have shown the breakage that early, i.e. when the 2.18 ebuilds were committed to CVS? > In which case it's an honest mistake. I guess so. I am not one to suspect evil intentions so easily. :) Fixed without merging or testing: if anyone had gnome-base/gnome on a ~hppa system (of which bugzilla shows no evidence) this issue would have come up months ago, so I think it's best to let nurture run its course and see what bugs simply re-keywording will bring. Naturally, I will be testing 2.18 on a stable HPPA system in due time.