Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 791856 - sys-apps/portage: package moves not applied with FEATURS=binpkg-multi-instance when any package instance for the same CPV already exists: Cannot update binary: Destination exists
Summary: sys-apps/portage: package moves not applied with FEATURS=binpkg-multi-instanc...
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Binary packages support (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 925715
  Show dependency tree
 
Reported: 2021-05-24 16:58 UTC by William Throwe
Modified: 2024-02-28 15:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Throwe 2021-05-24 16:58:28 UTC 
After every --sync I get the error

!!! Cannot update binary: Destination exists.
!!! app-emacs/emacs-common-gentoo-1.6-r3 -> app-emacs/emacs-common-1.6-r3

Looking at these packages, I have

/var/cache/packages/app-emacs/emacs-common:
emacs-common-1.6-1.xpak     emacs-common-1.6-r3-1.xpak  emacs-common-1.8-1.xpak
emacs-common-1.6-r1-1.xpak  emacs-common-1.6-r4-1.xpak

/var/cache/packages/app-emacs/emacs-common-gentoo:
emacs-common-gentoo-1.6-r3-2.xpak


It looks like (from this and from looking at the source) portage is using the CPV string to identify packages to move, but with FEATURES="binpkg-multi-instance" multiple packages can share the same CPV.
Comment 1 Zac Medico gentoo-dev 2021-05-24 17:36:06 UTC 
It's questionable whether you'd even want to bother to apply these updates, since the packages can be older that what you currently have installed.
Comment 2 Zac Medico gentoo-dev 2021-05-24 17:41:08 UTC 
It's not desirable that it skips application of the update and then it will not try to apply it again until the corresponding file timestamp in profiles/updates changes again.