On Fri, 11 Dec 2009, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

patch 2.6 changed its output in some cases, leading to a test-suite
failure. Upstream has already corrected the failure logged here:
http://git.savannah.gnu.org/cgit/quilt.git/commit/?id=c60ec97737f46fda9fa9cb96f874768f5ccfb57b

I pushed that patch in the git repo. But other tests are failing here
with the new patch and are not failing in the upstream master
branch. So it looks like we have some other oddities related to the
Debian specific patches.

[17] $ quilt push -- failed
Applying patch patches/patch          == Applying patch patches/patch
patching file other.txt               != can't find file to patch at input line 
3
Hunk #1 FAILED at 1.                  != Perhaps you used the wrong -p or 
--strip option?
1 out of 1 hunk FAILED -- rejects in file other.txt != The text leading up to 
this was:
Patch patches/patch does not apply (enforce with -f) != 
--------------------------
~                                     != |--- subdir/file.txt
~                                     != |+++ subdir/other.txt
~                                     != --------------------------
~                                     != No file to patch.  Skipping patch.
~                                     != 1 out of 1 hunk ignored
~                                     != Patch patches/patch does not apply 
(enforce with -f)
[30] $ quilt push -qf -- failed
Applying patch patches/patch          == Applying patch patches/patch
1 out of 1 hunk FAILED -- saving rejects to file other.txt.rej != The text 
leading up to this was:
Applied patch patches/patch (forced; needs refresh) != 
--------------------------
~                                     != |--- subdir/file.txt
~                                     != |+++ subdir/other.txt
~                                     != --------------------------
~                                     != No file to patch.  Skipping patch.
~                                     != 1 out of 1 hunk ignored
~                                     != Patch patches/patch appears to be 
empty; applied
[41] $ cd .. -- ok
[42] $ rm -rf d -- ok
15 commands (13 passed, 2 failed)
make[1]: *** [test/.file-not-found.ok] Error 2

In fact that test is Debian-specific... I can update it but it would fail with
older patch releases, I'm not sure what the proper course of action is.  Maybe
simply remove it because it tests for a debian specific bug and that upstream
is unlikely to merge that supplementary test ?

I'll disable it for now.

Cheers,
-- 
Raphaƫl Hertzog



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to