Package: patch Version: 2.7.4-1 Severity: serious Justification: causes FTBFS in other packages Control: affects -1 u-boot
$ dpkg-source -x u-boot_2014.10+dfsg1-2.dsc dpkg-source: warning: failed to verify signature on ./u-boot_2014.10+dfsg1-2.dsc dpkg-source: info: extracting u-boot in u-boot-2014.10+dfsg1 dpkg-source: info: unpacking u-boot_2014.10+dfsg1.orig.tar.xz dpkg-source: info: unpacking u-boot_2014.10+dfsg1-2.debian.tar.xz dpkg-source: info: applying add-debian-revision-to-u-boot-version ... The next patch would create the file tools/logos/solidrun.bmp, which already exists! Skipping patch. dpkg-source: info: the patch has fuzz which is not allowed, or is malformed dpkg-source: info: if patch 'cubox-i/cubox-i-support.diff' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: info: restoring quilt backup files for cubox-i/cubox-i-support.diff dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/cubox-i/cubox-i-support.diff/ --reject-file=- < u-boot-2014.10+dfsg1/debian/patches/cubox-i/cubox-i-support.diff gave error exit status 1 After downgrading to patch 2.7.1-6 from jessie, I'm able to unpack the source just fine. I suspect some of the recent CVE fixes to be the cause, but haven't looked deeply into the issue. I may be able to work around the issue in u-boot by adjusting the patch, but this may affect other packages as well and result in FTBFS in security updates and binNMUs. FWIW, I've filed a more detailed bug on u-boot specifically: https://bugs.debian.org/777518 live well, vagrant
signature.asc
Description: PGP signature
