[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-octave-devel] Octave 3.4



Thomas Weber <tweber@debian.org> writes:

> On Thu, Dec 15, 2011 at 12:37:29PM +0100, Sébastien Villemot wrote:
>> Thomas Weber <tweber@debian.org> writes:
>> Removing debian/clean helps. I am then able to run git-buildpackage
>> without any option when starting from a clean repository.
>> 
>> But then if I try to do a second build in a row, dpkg-source complains
>> about modified files (both text and binary files). I think this is not
>> policy compliant. I attach a patch which fixes the problem.
>
> This is strange. I actually thought that building twice in a row worked
> for me (I cannot test it right now). 
>
> Can you just paste the commands you run when building?

Starting from a clean repository pointing at commit ddabaf39, I do:

$ git-buildpackage --git-pristine-tar -j8
$ git-buildpackage --git-pristine-tar --git-ignore-new -j8

The first gbp suceeds. The second one fails: dpkg-source complains about
modifications to binary files that it does not know how to represent.

After adding the relevant exclusion rules to debian/source/options
(commit 188c6a2c), the second gbp succeeds.

>> From b4e3a2e27e82edf2598a61f9106627bf9fff12e2 Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?S=C3=A9bastien=20Villemot?= <sebastien.villemot@ens.fr>
>> Date: Thu, 15 Dec 2011 12:32:32 +0100
>> Subject: [PATCH] debian/source/options: exclude various regenerated files
>>  from source diff
>
> There's no need to ask for my opinion for improvements before you push
> them into the repo - just go ahead and commit it ;)

Thanks for the clarification. I pushed the changes.

> Anyway, unless something unforeseen happens[1], I intend to upload to
> experimental this weekend - which doesn't mean much, we will go through
> NEW anyway.

Please go ahead. I also think the package is ready for an upload.

Best,

-- 
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-49-90 - GPG Key: 4096R/381A7594

Attachment: pgpMQpubzvGby.pgp
Description: PGP signature


Reply to: