Le mardi 07 juin 2011 à 18:53 +0200, Julien Valroff a écrit : > I think this method is somehow outdated now that we have a very reliable > tool which takes care of that automatically: git-buildpackage > > Using git-import-* tools and gbp-clone makes the workflow very easy, I > suggest you have a look at these tools. > > I have also in the meantime managed to understand why gbp fails to detect the > compression format with imports from your method. It is linked to the commit > message which is based on the following template when using git-import-orig: > pristine-tar data for <package>_<version>.orig.tar.gz > > I haven't checked the code though, but here is the verbose output of > git-buildpackage: > gbp:debug: ['git', 'log', '--pretty=format:%H', '--grep=pristine-tar .* > extundelete_0.2.0\\.orig.tar\\.', 'pristine-tar', '--'] > gbp:debug: ['git', 'log', '-n1', '--pretty=format:%s', 'pristine-tar'] > gbp:debug: Determined compression type 'None' > gbp:warn: Unknown compression type of Adding pristine-tar version 0.2.0., > assuming gzip > > The pristine-branch contains: > extundelete_0.2.0.orig.tar.gz.delta extundelete_0.2.0.orig.tar.gz.id > > But the commit log only states: > Adding pristine-tar version 0.2.0. > > Which means the --grep cannot lead to any result. > > I don't think it is a problem, as gbp is meant to be used with git-import-orig > and not in a different worfklow. > > Give me your thoughts on gbp, I thin kit's worth having a look at it. >
I will have a look asap. Thanks showing that method. -- Christophe Monniez <christophe.monn...@fccu.be> _______________________________________________ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel