Currently, FEATURES=unmerge-backup skips the quickpkg call if there is an existing binary package of the same version. It would be better to compare the BUILD_TIME metadata, and call quickpkg if no binary package exists with the same BUILD_TIME (this can involve comparison with multiple binary packages due to FEATURES=binpkg-multi-instance).
There's a patch in the following branch: https://github.com/zmedico/portage/tree/bug_586410 I've posted it for review here: https://archives.gentoo.org/gentoo-portage-dev/message/23b934e413c9071c87f07b5d27c61a88
This is in the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=3d5382f3e2c437285a009db356c719bc3d77bdd9
Consider documenting the changes... The current documentation says: > unmerge-backup Call quickpkg(1) to create a backup of each package before > it is unmerged (if a binary package of the same version does > not already exist). And it causes a lot of confusion when packages got overwritten when it's already exists...
This is fixed in portage-2.3.0. (In reply to Fat-Zer from comment #3) > Consider documenting the changes... The current documentation says: > > > unmerge-backup Call quickpkg(1) to create a backup of each package before > > it is unmerged (if a binary package of the same version does > > not already exist). > > And it causes a lot of confusion when packages got overwritten when it's > already exists... If you enable FEATURES=binpkg-multi-instance then packages will never overwritten.
(In reply to Zac Medico from comment #4) > This is fixed in portage-2.3.0. > > If you enable FEATURES=binpkg-multi-instance then packages will never > overwritten. By the word, it's not documented on the man page either...
(In reply to Fat-Zer from comment #5) > (In reply to Zac Medico from comment #4) > > This is fixed in portage-2.3.0. > > > > If you enable FEATURES=binpkg-multi-instance then packages will never > > overwritten. > > By the word, it's not documented on the man page either... Thanks, I've opened bug 608356 for this.
