Created attachment 579534 [details] emerge --info output In concurrence with Bug #464662, having FEATURES=unmerge-backup and then re-emerging a thus-created package with --usepkg=y causes config files and init scripts of that package to be silently overwritten by files containing only the line "# empty file because --include-config=n when `quickpkg` was used". Steps to reproduce (similar with FEATURES=downgrade-backup): 1. make sure that FEATURES=buildpkg or buildsyspkg are NOT set and that there is no previous package for the tested ebuild present in PKGDIR 2. perform clean install of any package, so that we can unmerge it in step 3 emerge --usepkg=n sys-apps/lm_sensors && wc -l /etc/init.d/lm_sensors ==> should output a line count > 1, i.e. a plausible file content 3. trigger creation of binary package through unmerge-backup by re-emerging FEATURES=unmerge-backup emerge --usepkg=n sys-apps/lm_sensors 4. merge the same package a third time, now using the generated package emerge --usepkg=y sys-apps/lm_sensors && wc -l /etc/init.d/lm_sensors ==> observe that the file length now is reduced to one line ==> also observe that the init script (and config files) have been silently overwritten.
I am uncertain wether additionally, quickpkg --include-config=n should generate these dummy files at all. Maybe changing that behaviour would be a cleaner fix for this bug?
