On Mon, 03 Dec 2012 13:11:56 -0800 Russ Allbery wrote:
> Miguel Telleria de Esteban writes:
>
>
> >... or maybe subsequent git-buildpackage invocations may generate
> >md5sum different .orig.tar.gz?? I guess not (although I will
> > check).
>
> Every time you generate an *.orig.tar.gz
Miguel Telleria de Esteban writes:
> * In a pure git storage scenario, pristine-tar doesn't add much
>benefit since we can always generate an orig.tar.gz from an upstream
>tag and obtain the same result...
>... or maybe subsequent git-buildpackage invocations may generate
>md5su
Thanks everybody for your answers.
After some review on my files and seeing your responses I can see that:
* The orig.tar.gz was not created because the debian/changelog version
lacked a - to differentiate "upstream_version" from "debian
versions".
As a result gbp considered my pa
On Mon, Dec 03, 2012 at 03:30:09PM +0100, Antonio Ospite wrote:
> In my limited experience if the upstream project uses git already and
> _tags_ stable releases it is very easy to avoid using pristine-tar
It's also very easy to avoid it in any other workflow: just don't enable
it. There is no diffe
On Mon, Dec 03, 2012 at 01:44:55PM +0100, Miguel Telleria de Esteban wrote:
> Why does git-buildpackage need pristine-tar to generate the orig.tar.gz
> file?.
It doesn't and it's even not enabled by default.
> Can't it just pick the contents from the upstream branch
> together with version number
On 12/03/2012 10:30 PM, Antonio Ospite wrote:
> in debian/gbp.conf there are just these lines:
> [DEFAULT]
> debian-branch = debian
> upstream-branch = master
> upstream-tag = v%(version)s
>
> By just running "git buildpackage" the package builds fine, and
> the .orig.tar.gz
On Mon, 3 Dec 2012 13:44:55 +0100
Miguel Telleria de Esteban wrote:
> Dear all,
>
> After several months of using git-buildpackage with the "recommended"
> pristine-tar option I still keep making myself the following question.
>
> Why does git-buildpackage need pristine-tar to generate the orig
Hi,
On 03.12.2012 13:44, Miguel Telleria de Esteban wrote:
> and it works !!
> so why does not git-buildpackage do this?
Try:
md5sum $orig_tarball_from_pristine_Tar
vs
md5sum $orig_tarball_recreated_from_the_upstream_branch
While the /contents/ of the tarball are identical, the tarball
Dear all,
After several months of using git-buildpackage with the "recommended"
pristine-tar option I still keep making myself the following question.
Why does git-buildpackage need pristine-tar to generate the orig.tar.gz
file?. Can't it just pick the contents from the upstream branch
together
9 matches
Mail list logo
