[Pkg-sympa-devel] Problems with building Sympa packages

[Stefan Hornburg (Racke)]

On 10/27/2010 11:57 AM, Jonas Smedegaard wrote:
> On Wed, Oct 27, 2010 at 11:16:08AM +0200, Stefan Hornburg (Racke) wrote:
>> On 10/27/2010 10:28 AM, Jonas Smedegaard wrote:
>>> Hi Stefan,
>>>
>>> On Wed, Oct 27, 2010 at 09:02:12AM +0200, Stefan Hornburg (Racke) wrote:
>>>> I'm trying to build Sympa 6.1.1~dfsg-2 packages to fix the recent RC
>>>> bug. The build with git-buildpackage fails with the following message:
>>> [snip]
>>>> dpkg-source: error: aborting due to --abort-on-upstream-changes
>>>
>>> The clean target needs to clean perfectly when building on top of git.
>>>
>>> Perhaps you did not cleanup maunally after some unusual work (e.g. an
>>> interrupted or failed test build)?
>>>
>>> Or perhaps our packaging do not generally cleanup properly at the
>>> moment?
>>>
>>> You can try be lazy and build with the --git-export option, but really
>>> the proper thing to do is figure out why it isn't clean, and fix it so
>>> that it is.
>>>
>>> Perhaps try gbp-clone --pristine-tar from a fresh dir - if that works
>>> (also with repeated builds cleaning in-between - then it is simply your
>>> own git clone that got messed up due to some custom work of yours.
>>>
>>
>> No, there seems to be something flaky with the cleanups.
>>
>> gbp-clone --pristine-tar
>> ssh://racke@git.debian.org/git/collab-maint/sympa
>
> A suggestion: use the protocol-less form for read/write access:
>
> gbp-clone --pristine-tar git.debian.org:/git/collab-maint/sympa
>
> NB! note colon after hostname (has puzzled me many times when missed)
>
> That form is shorter (more likely to fit on a single email line) and
> reusable among us when username is left out.
>
> If you use a different username at Alioth than locally, then add
> something like this to your local ~/.ssh/config file:
>
> Host *.debian.org *.debian.net
> User racke
>
>
>
>> cd sympa
>> git buildpackage
>>
>> Result:
>> dpkg-source -i -I --after-build sympa
>> dpkg-source: info: using options from
>> sympa/debian/source/local-options: --unapply-patches
>> --abort-on-upstream-changes
>> dpkg-source: info: unapplying 2006_force_removal_po_stamp_files.patch
>> dpkg-source: error: LC_ALL=C patch -R -t -N -p1 -u -V never -g0 -E
>> --no-backup-if-mismatch <
>> sympa/debian/patches/2006_force_removal_po_stamp_files.patch gave
>> error exit status 1
>> The next patch, when reversed, would create the file po-wwsympa/stamp-po,
>> which already exists! Skipping patch.
>
> Ah, you are right.
>
> That particular problem was missed by my routines - I build in a
> cowbuilder chroot.
>
>
> Patch 2006 looks plain wrong to me: Autogenerated files should not be
> patched, unless their autogeneration can safely be avoided (as is the
> case with some autotools files when maintainer-mode is enabled).
>
>
> Try revert commit 03829af (which will need manual removal of the patch,
> due to my later unfuzzing it), and see if that works.
>

Removing this patch looks like it is going to work.

Regards
	Racke

-- 
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team