portage-utils installs q-reinitialize (/etc/portage/postsync.d) with doins. The executable bit (enabled manually upon first install) is thus discarded when re-installing portage-utils. Reproducible: Always Steps to Reproduce: 1. emerge portage-utils 2. chmod +x /etc/portage/postsync.d/q-reinitialize 3. emerge portage-utils Actual Results: +x has been stripped from q-reinitialize. Expected Results: q-reinitialize keeps +x
Created attachment 217083 [details, diff] Possible patch This is a possible (quick'n'dirty) patch. Not sure if I'm using ${ROOT} correctly.
you cant use ROOT in src_* i'm pretty sure this is a one time issue. previous ebuilds didnt install the files as part of src_*, but current ones do.
(In reply to comment #2) > you cant use ROOT in src_* Please don't say such things. It's WRONG.
it is not wrong. you cannot change the contents of $D based on $ROOT otherwise you completely screw up binpkg support.
I want a severity setting called "pain in the ass" to use on this bug. At least now, having been bitten by it at least twice, I'm remembering to check.
(In reply to comment #2) > i'm pretty sure this is a one time issue. previous ebuilds didnt install the > files as part of src_*, but current ones do. what do you mean by "one time"? I can confirm this happens every time portage-utils is emerged.
guess portage changed behavior wrt pushing permission bits on existing files. ebuild should sync the bits itself now. http://sources.gentoo.org/app-portage/portage-utils/portage-utils-0.3.1.ebuild?r1=1.2&r2=1.3
