[pkg-fso-maint] cornucopia-status
Nikita V. Youshchenko
yoush at debian.org
Fri Aug 28 19:53:25 UTC 2009
> Hi Nikita,
>
> Am Montag 24 August 2009 21:49:01 schrieb Nikita V. Youshchenko:
> > I may look into the packages and sponsor upload if needed.
> > Where to get those?
>
> Thanks for your interest.
> The packages (fso-misc-vapi, libfsobasics, libfsoframework, fso-usaged)
> are in the pkg-fso pool (source, i386, armel) and on git.debian.org.
>
> Heiko
I've looked into git repos of these packages, and I have a workflow-related
question.
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?
Or maybe you just forgot to push pristine-tar branch to alioth? :)
Nikita
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090828/c5414122/attachment.pgp>
More information about the pkg-fso-maint
mailing list