Bug 17269 – ebuild enhancement (libglad-0.17)

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Chayim I. Kirshen 2003-03-10 19:36:31 UTC]

This is an updated ebuild for libglade-0.17-r6 (should now be named r7).  It
doesn't have the dependency for db1 explicitly listed.  This caused my emerge on
the multi-gnome-terminal to bust after upgrading some gnome libs.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Chayim I. Kirshen 2003-03-10 19:37:39 UTC]

Created attachment 9234 [details]
updated ebuild file.

[Comment 2 foser (RETIRED) 2003-03-16 14:23:44 UTC]

how did it 'bust' ?

[Comment 3 Chayim I. Kirshen 2003-03-17 08:16:57 UTC]

There were failed linker problems because db1 wasn't installed.  I had unmerged it (db1) earlier in the day, and that broke my multi-term.  Reading the bust I saw that libglade needed to be rebuilt.
Rebuilding libglade showed me that db1 was needed to compile it.  If you want to reproduce it:

1) emerge unmerge db-1.85 that's what I had installed)
2) emerge unmerge libglade multi-gnome-terminal
3) emerge multi-gnome-terminal (libglade build pukes b/c of no db1, even if you have db3 installed).

[Comment 4 foser (RETIRED) 2003-03-17 09:12:22 UTC]

yes maybe, i think libglade just triggered a lib that needed db. libglade itsself doesn't seem to need it. So unless you come with some convincing output im closing this one.

In general you shouldnt just unmerge random libs unless you really know what you are doing.

[Comment 5 Chayim I. Kirshen 2003-03-17 09:38:10 UTC]

Actually I knew exactly what I was doing.  I was pretty sure that db1 wasn't needed by anything else on the system (and hence the unmerge).  But if you feel that's not a bug, then don't worry about it.

Thanks.

[Comment 6 foser (RETIRED) 2003-03-17 09:42:33 UTC]

then i would like to know what exactly the error was during the libglade merge.