[pkg-fso-maint] cornucopia-status

[Heiko Stübner]

Hi Nikita,

Am Freitag 28 August 2009 21:53:25 schrieb Nikita V. Youshchenko:
> In past I've faced an issue with git-buildpackage that each time it
> recreates slightly different .orig.tar.gz for the same package version
> (likely because of timestamps or something like that - I never looked into
> detail). Which in turn causes upload rejections because newer uploads
> reference .orig.tar.gz files with different size and/or md5 than one
> previously uploaded to archive.
>
> Before, I always used git-buildpackage's prstine-tar support to avoid this
> issue.
>
> Of the 4 packages in question, only one (libfsobasics) contains
> pristine-tar branch, other 3 don't.
>
> Does that mean that other 3 packages assume some other, not
> pristine-tar-based workflow? If so, could you please explain how use
> git-buildpackage properly to to build these packages?

the FSO-guys don't publish official tars at the moment and the snapshots used 
come directly from the upstream git. From Luca I got the hint to just use the 
tar.gz git-buildpackage creates on the first run as pristine-tar commit when no 
official tar.gz is available. This is exactly what I did with libfsobasics.

While building the other packages I found a very nasty bug which disabled 
suspends in fsousaged completly and after the bug hunt with Mickey and the 
happieness when it finally ran again, I think I simply forgot to add the 
pristine-tars to the other gits. :-)

I will add the tars in the same manner as in libfsobasics in a moment.

I hope I could make this a bit clearer
Heiko