Hi Andreas,
On Sat, Feb 1, 2014 at 6:54 PM, Andreas Tille <[email protected]> wrote: > Hi Luis > > On Sat, Feb 01, 2014 at 02:00:28PM -0500, Luis Ibanez wrote: > > A bit more progress: > > > > > > The upstream branch has now been tagged, > > and pushed to the Git repository in Alioth. > > > > The following works now ....at least for me... :-) > > But may be you forgot to push the pristine-tar branch? > > I tried indeed to setup the pristine-tar branch, but the VistA-M tar.gz if too big for git. Here is the error message (from my previous email): Pristine Tar: ----------------- When building the repository, I first attempted to import the source tarball with the --pristine-tar option, as recommended here: https://wiki.debian.org/PackagingWithGit#pristine-tar but got the following error message: gbp:info: No git repository found, creating one. gbp:info: Tag upstream/0.20130405 not found, importing Upstream tarball xdelta: warning: no matches found in from file, patch will apply without it error: excessively large binary delta for /tmp/pristine-tar.ETnVfcsL8q/origtarball (Please consider filing a bug report.) pristine-tar: failed to generate delta gbp:error: Couldn't commit to 'pristine-tar' with upstream 'upstream': /usr/bin/pristine-tar returned 1 The VistA-M tarball is 407Mb. This is probably the reason... > > vista-foia(master) $ git-buildpackage > gbp:info: Orig tarball 'vista-foia_0.20130405.orig.tar.gz' not found at > '../tarballs/' > gbp:warning: Pristine-tar branch "pristine-tar" not found > pristine-tar: no pristine-tar branch found, use "pristine-tar commit" first > gbp:error: Couldn't checkout "vista-foia_0.20130405.orig.tar.gz": > /usr/bin/pristine-tar returned 1 > > For me, git-buildpackage goes ahead and creates the tar.gz files from the content of the upstream branch. > vista-foia(master) $ git tag > upstream/0.20130405 > > Yeap, using this branch and tag. > vista-foia(master) $ git branch > * master > upstream > > > In case you have no idea what I'm talking about please seek for > pristine-tar in the Debian Med policy. You can do this import > even on top of your current directory (it will just result in > a warning that the upstream tag is just known). > > I did try indeed to create the pristine-tar branch, but failed due to the tar.gz file size. We will have to find an alternative to the large size of the tar.gz file. I'm open to any suggestions... > If the pristine-tar branch is lacking I can not reproduce the > original tar file at my side from the Git repository. > > I'm curious as to why git-buildpackage behaves different for me. E.g. it generates the tar.gz files even though they are missing from the pristine-tar branch. Is there a default option in git-buildpackage, that could alter this behavior ? Luis
