| View previous topic :: View next topic |
| Author |
Message |
curmudgeon
Veteran
Joined: 08 Aug 2003
Posts: 1741
|
 Posted: Wed Nov 29, 2006 4:42 am Post subject: packages built in wrong order |
 |
|
Hi guys,
First, let me post the portion from my emerge.log that covers this:
| Code: | 1164702382: *** emerge --verbose twinkle
1164702383: >>> emerge (1 of 5) dev-libs/boost-1.33.1 to /
1164702383: === (1 of 5) Cleaning (dev-libs/boost-1.33.1::/usr/portage/dev-libs/boost/boost-1.33.1.ebuild)
1164702384: === (1 of 5) Compiling/Merging (dev-libs/boost-1.33.1::/usr/portage/dev-libs/boost/boost-1.33.1.ebuild)
1164705106: >>> AUTOCLEAN: dev-libs/boost
1164705106: --- AUTOCLEAN: Nothing unmerged.
1164705107: === (1 of 5) Post-Build Cleaning (dev-libs/boost-1.33.1::/usr/portage/dev-libs/boost/boost-1.33.1.ebuild)
1164705107: ::: completed emerge (1 of 5) dev-libs/boost-1.33.1 to /
1164705107: >>> emerge (2 of 5) net-libs/ccrtp-1.5.0 to /
1164705107: === (2 of 5) Cleaning (net-libs/ccrtp-1.5.0::/usr/portage/net-libs/ccrtp/ccrtp-1.5.0.ebuild)
1164705108: === (2 of 5) Compiling/Merging (net-libs/ccrtp-1.5.0::/usr/portage/net-libs/ccrtp/ccrtp-1.5.0.ebuild)
1164705333: >>> AUTOCLEAN: net-libs/ccrtp
1164705338: === Unmerging... (net-libs/ccrtp-1.3.6)
1164705340: >>> unmerge success: net-libs/ccrtp-1.3.6
1164705340: === (2 of 5) Post-Build Cleaning (net-libs/ccrtp-1.5.0::/usr/portage/net-libs/ccrtp/ccrtp-1.5.0.ebuild)
1164705340: ::: completed emerge (2 of 5) net-libs/ccrtp-1.5.0 to /
1164705340: >>> emerge (3 of 5) dev-cpp/commoncpp2-1.5.1-r1 to /
1164705340: === (3 of 5) Cleaning (dev-cpp/commoncpp2-1.5.1-r1::/usr/portage/dev-cpp/commoncpp2/commoncpp2-1.5.1-r1.ebuild)
1164705341: === (3 of 5) Compiling/Merging (dev-cpp/commoncpp2-1.5.1-r1::/usr/portage/dev-cpp/commoncpp2/commoncpp2-1.5.1-r1.ebuild)
1164705741: >>> AUTOCLEAN: dev-cpp/commoncpp2
1164705746: === Unmerging... (dev-cpp/commoncpp2-1.3.22)
1164705748: >>> unmerge success: dev-cpp/commoncpp2-1.3.22
1164705748: === (3 of 5) Post-Build Cleaning (dev-cpp/commoncpp2-1.5.1-r1::/usr/portage/dev-cpp/commoncpp2/commoncpp2-1.5.1-r1.ebuild)
1164705748: ::: completed emerge (3 of 5) dev-cpp/commoncpp2-1.5.1-r1 to /
1164705748: >>> emerge (4 of 5) net-libs/libzrtpcpp-0.9.0 to /
1164705748: === (4 of 5) Cleaning (net-libs/libzrtpcpp-0.9.0::/usr/portage/net-libs/libzrtpcpp/libzrtpcpp-0.9.0.ebuild)
1164705748: === (4 of 5) Compiling/Merging (net-libs/libzrtpcpp-0.9.0::/usr/portage/net-libs/libzrtpcpp/libzrtpcpp-0.9.0.ebuild)
1164705816: >>> AUTOCLEAN: net-libs/libzrtpcpp
1164705816: --- AUTOCLEAN: Nothing unmerged.
1164705816: === (4 of 5) Post-Build Cleaning (net-libs/libzrtpcpp-0.9.0::/usr/portage/net-libs/libzrtpcpp/libzrtpcpp-0.9.0.ebuild)
1164705816: ::: completed emerge (4 of 5) net-libs/libzrtpcpp-0.9.0 to /
1164705816: >>> emerge (5 of 5) net-im/twinkle-0.9-r1 to /
1164705816: === (5 of 5) Cleaning (net-im/twinkle-0.9-r1::/usr/portage/net-im/twinkle/twinkle-0.9-r1.ebuild)
1164705816: === (5 of 5) Compiling/Merging (net-im/twinkle-0.9-r1::/usr/portage/net-im/twinkle/twinkle-0.9-r1.ebuild)
1164706653: === (5 of 5) Updating world file (net-im/twinkle-0.9-r1)
1164706653: >>> AUTOCLEAN: net-im/twinkle
1164706658: === Unmerging... (net-im/twinkle-0.7.1)
1164706660: >>> unmerge success: net-im/twinkle-0.7.1
1164706660: === (5 of 5) Post-Build Cleaning (net-im/twinkle-0.9-r1::/usr/portage/net-im/twinkle/twinkle-0.9-r1.ebuild)
1164706660: ::: completed emerge (5 of 5) net-im/twinkle-0.9-r1 to /
1164706660: *** Finished. Cleaning up...
1164706670: *** exiting successfully.
1164706674: *** terminating. |
The problem comes from portage building cctrp before commoncpp2.
It actually links against it:
| Code: | $ ldd /usr/lib64/libccrtp1-1.5.so.0.0.0
libccgnu2-1.5.so.0 => /usr/lib/libccgnu2-1.5.so.0 (0x00002b48323b0000)
[...] |
The twinkle ebuild has both ccrtp and commoncpp2 in RDEPEND, with DEPEND=${RDEPEND} (and another package).
The ccrtp ebuild also has commoncpp2 in RDEPED (also with DEPEND=${RDEPEND} and more).
Why does portage build ccrtp first?
I filed a bug report about it, but I admit I didn't do a very good job of explaining things:
https://bugs.gentoo.org/show_bug.cgi?id=156537
The bug report got slammed, but this still seems like a real problem to me.
Something is wrong somewhere. This seems very basic to require one package get built before another.
Should I reopen the bug? Contact the twinkle developer? Something else?
Thank you in advance for your assistance. |
|
| Back to top |
|
 |
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4975
Location: Gothenburg, Sweden
|
| Posted: Wed Nov 29, 2006 3:19 pm Post subject: |
|
|
I guess your bug report got closed becuase of the summary not really saying what was wrong (the deps are correct) and because you didn't post the part of emerge log showing the incorrect merge order. I'd suggest you quickpkg the packages (so you can quickly re-install them), unmerge them and then run | Code: | | emerge -dpv twinkle >> emerge_twinkle.log |
Check that file and if portage still wants to install the packages in the wrong order you should reopen the bug and attach emerge_twinkle.log to the bug. You should then also post the output of emerge --info to the bug.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
