Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 182551 - gnome-base/gnome-2.18.0 needs some keywords loving on hppa
Summary: gnome-base/gnome-2.18.0 needs some keywords loving on hppa
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: HPPA Porters
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-19 08:45 UTC by Jakub Moc (RETIRED)
Modified: 2007-06-22 21:47 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Moc (RETIRED) gentoo-dev 2007-06-19 08:45:26 UTC
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 ]
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2007-06-21 14:32:16 UTC
Why were keywords for all of these dropped in the first place? Unbelievable that this keeps happening without notice to the relevant arch team..
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2007-06-21 14:58:14 UTC
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. :\
Comment 3 Rémi Cardona (RETIRED) gentoo-dev 2007-06-21 17:47:48 UTC
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.
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2007-06-22 21:47:03 UTC
(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.