Your message dated Wed, 4 Mar 2015 21:14:35 +0100
with message-id
<CAKjSHr35G=pnQENFZ2BD7yAogApdOfukMg=Hb75Cxbs9Et=g...@mail.gmail.com>
and subject line not a patch bug
has caused the Debian Bug report #777520,
regarding patch: regression causes u-boot to FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
777520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777520
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
It was a problem in u-boot, which asked patch to overwrite an already
existing file. As it has a security risk, patch now refuses to do it.
--- End Message ---
