quickpkg (portage-2.1.9.25) generates unusable package of e2fsprogs, bind etc. Many executables are empty, means file sizes are zero (e.g. /sbin/fsck.ext4). The attached e2fsprogs-1.41.12.tbz2 demonstrates this (size is only 535kB). Same ebuild produced with portage-2.1.8.3 is right an has a file size of 708kB. Other ebuild has also problems e.g. bind. As I saw on the python source '/usr/bin/quickpkg' there has been massive changes from portage 2.1.8.3 -> 2.1.9.25. Reproducible: Always Steps to Reproduce: 1. emerge -av =sys-apps/portage-2.1.9.25 2. emerge -av e2fsprogs 3. quickpkg --include-config=y =sys-fs/e2fsprogs-1.41.12 3. (cd /var/tmp/packages/sys-fs ; tar xvjf e2fsprogs-1.41.12.tbz2) 4. Take a look on generated sbin directory (e.g. fsck.ext4) Actual Results: Machines updated with such packages have massive problems, because system executables doesn't work. Expected Results: Size of some executables (I assume that those who has same contents, has the problems). Produce right packages.
I was not able to attached the file 'e2fsprogs-1.41.12.tbz2', but is not necessary, because it take only a couple of minutes to to produced it.
*** This bug has been marked as a duplicate of bug 338509 ***
This doesn't really belong to tools-portage...reopening.
