Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 601508 - portage do not update directory mode when merging
Summary: portage do not update directory mode when merging
Status: RESOLVED DUPLICATE of bug 141619
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-03 10:43 UTC by LABBE Corentin
Modified: 2016-12-03 20:31 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LABBE Corentin 2016-12-03 10:43:45 UTC
I have some directories which are 777.
Re-emerging ebuild which own thoses directories do not change directory rights.
Example:
before:
ls -ld /usr/share/doc/xz-utils-5.2.2/
drwxrwxrwx 4 root root 4096 déc.   3 11:33 /usr/share/doc/xz-utils-5.2.2/
after:
ls -ld /var/tmp/portage/app-arch/xz-utils-5.2.2/image/usr/share/doc/xz-utils-5.2.2/
drwxr-xr-x 4 root root 4096 déc.   3 11:33 /var/tmp/portage/app-arch/xz-utils-5.2.2/image/usr/share/doc/xz-utils-5.2.2/
ls -ld /usr/share/doc/xz-utils-5.2.2/
drwxrwxrwx 4 root root 4096 déc.   3 11:33 /usr/share/doc/xz-utils-5.2.2/

So content is copied but directory right is not updated

Reproducible: Always

Actual Results:  
directory mode is never chanegd

Expected Results:  
dirctory mode is exactly the same as it is in imagedir
Comment 1 Mike Gilbert gentoo-dev 2016-12-03 14:38:29 UTC
What should happen when multiple packages install files in the same directory?
Comment 2 Zac Medico gentoo-dev 2016-12-03 20:31:03 UTC
(In reply to Mike Gilbert from comment #1)
> What should happen when multiple packages install files in the same
> directory?

Good question.

I suppose that a system like dpkg-statoverride could provide a way to track conflicts and allow the user to choose resolutions. See bug 396153.

*** This bug has been marked as a duplicate of bug 141619 ***