The error informations: Package 'sys-libs/db-4.8.30' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message.
Created attachment 230225 [details] build.log
Created attachment 230227 [details] emerge --info =sys-libs/db-4.8.30
emerge -pqv =sys-libs/db-4.8.30 [ebuild NS ] sys-libs/db-4.8.30 [4.7.25_p4] USE="-doc -examples -java -nocxx -tcl -test"
*** Bug 318369 has been marked as a duplicate of this bug. ***
*** Bug 318371 has been marked as a duplicate of this bug. ***
Quoting in db.eclass broke it: mv: cannot move `/var/tmp/portage/sys-libs/db-4.7.25_p4/image//usr/bin/db_archive' to `/var/tmp/portage/sys-libs/db-4.7.25_p4/image//usr/bin\\/db4.7_archive': No such file or directory
*** Bug 318375 has been marked as a duplicate of this bug. ***
Created attachment 230235 [details, diff] Trivial but tested patch People will have to re-emerge 4.7 and 4.8 to fix the consequences of the bug. Specifically, if /usr/bin/db_* matches anything you need to re-emerge.
sorry for stupid question, should I apply this patch to all needed db-versions?
I mask all sys-libs/db-4.8.* packages,and type "revdep-rebuild" to solve broken packages.
(In reply to comment #8) > Created an attachment (id=230235) [details] > Trivial but tested patch > > People will have to re-emerge 4.7 and 4.8 to fix the consequences of the bug. > Specifically, if /usr/bin/db_* matches anything you need to re-emerge. > works for me :)
(In reply to comment #6) > Quoting in db.eclass broke it: > > mv: cannot move > `/var/tmp/portage/sys-libs/db-4.7.25_p4/image//usr/bin/db_archive' to > `/var/tmp/portage/sys-libs/db-4.7.25_p4/image//usr/bin\\/db4.7_archive': No > such file or directory > Perfect working - THX
(In reply to comment #8) > Created an attachment (id=230235) [details] > Trivial but tested patch > > People will have to re-emerge 4.7 and 4.8 to fix the consequences of the bug. > Specifically, if /usr/bin/db_* matches anything you need to re-emerge. > Sorry comment12 was wrong quoted.... This patch works for me
Fixed in the tree and available via rsync mirrors. Do we have to take further action for users who installed sys-libs/db using the borked eclass?
> Do we have to take further action for users who installed sys-libs/db using the > borked eclass? Not sure. They have the db_* commands instead of the db4.7_* and/or db4.8_* commands, so if something looks for them it will miss them. They'll go away when updating to a subsequent version in the same slot. The libraries names are ok though, so I'm not convinced anybody really cares.
(In reply to comment #15) > > Do we have to take further action for users who installed sys-libs/db using the > > borked eclass? > > Not sure. They have the db_* commands instead of the db4.7_* and/or db4.8_* > commands, so if something looks for them it will miss them. They'll go away > when updating to a subsequent version in the same slot. The libraries names > are ok though, so I'm not convinced anybody really cares. > just sync now.
(In reply to comment #16) > (In reply to comment #15) > > > Do we have to take further action for users who installed sys-libs/db using the > > > borked eclass? > > > > Not sure. They have the db_* commands instead of the db4.7_* and/or db4.8_* > > commands, so if something looks for them it will miss them. They'll go away > > when updating to a subsequent version in the same slot. The libraries names > > are ok though, so I'm not convinced anybody really cares. > > > > just sync now. > THX all is working fine again, I'm installing my new Laptop atm and had no problems with different slots for sys-libs/db
No more problems reported, closing now.
db-4.8.30 still collides with db-4.7.25_p4 Reemerged 4.7.25_p4, db.4.8.30 still failed with collisions. ... * /usr/docs/java/style.css * /usr/docs/license/license_db.html * /usr/docs/porting/BDB-Porting-Guide.pdf * /usr/docs/porting/buildtarget.html * /usr/docs/porting/certport.html * /usr/docs/porting/gettingStarted.css * /usr/docs/porting/index.html * /usr/docs/porting/introduction.html * /usr/docs/porting/modifytest.html * /usr/docs/porting/modscope.html * /usr/docs/porting/newbinary.html * /usr/docs/porting/portprocess.html * /usr/docs/porting/preface.html * /usr/docs/porting/sourceintegrate.html * /usr/docs/porting/testport.html * /usr/docs/porting/testreview.html * /usr/docs/porting/testrun.html * * Package 'sys-libs/db-4.8.30' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. This bug needs to be reopened.
adamf10@pobox.com: you posted the EXACT same comment yesterday. This is not the same bug, it was for collisions on the binaries, and you have documentation that is colliding. Please open a new bug. Something is wrong with your builds I think, as they don't collide here: $ equery f =sys-libs/db-4.8* |grep style.css /usr/share/doc/db-4.8.30/html/java/style.css $ equery f =sys-libs/db-4.7* |grep style.css /usr/share/doc/db-4.7.25_p4/html/java/style.css
