Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 193903 - gnome-desktop-2.20 should depend on gail
Summary: gnome-desktop-2.20 should depend on gail
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-26 19:27 UTC by Maxxer
Modified: 2007-10-03 09:34 UTC (History)
0 users

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 Maxxer 2007-09-26 19:27:46 UTC
I was upgrading to gnome 2.20, and at gnome-desktop emerge failed during configure due to missing gail package.
Emerging Gail and then gnome-desktop worked fine.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-09-26 19:45:31 UTC
Don't see gnome-desktop-2.20 anywhere. Is this from some overlay or what?
Comment 2 Mart Raudsepp gentoo-dev 2007-09-26 19:47:17 UTC
Yes, and reports as such are very much welcome to the GNOME team, so we can fix them even before they hit the tree soon now(tm)
Comment 3 Mart Raudsepp gentoo-dev 2007-10-03 01:36:34 UTC
Sorry, but there are exactly zero references to gail anywhere in the gnome-desktop tarball. This must have been happening due to something else, but as you provided no error message whatsoever, I can't do anything about that until you do.
If this problem is still there, please provide more information and reopen. There have been some circular dependency fixes prior to which it might have caused gail problem in some lower level package than gnome-desktop.
Purely based on the description, this problem is invalid, I'll have to mark it as such. Thanks for reporting it though - please next time include more information, such as the error log and emerge --info. Thank you.
Comment 4 Maxxer 2007-10-03 09:34:03 UTC
(In reply to comment #3)
> Purely based on the description, this problem is invalid, I'll have to mark it
> as such. Thanks for reporting it though - please next time include more
> information, such as the error log and emerge --info. Thank you.

Yep, I understand.
Sadly when I ran into the error I didn't save any output. 
Just after some time I realized it could be useful, so I posted what I remembered.

I'm sorry it hasn't be helpful. I'll pay more attention next time.