Re: Using pristine-tar

2014-10-20 Thread Thomas Goirand
On 10/21/2014 06:18 AM, Charles Plessy wrote: > I you generate a orig.tar.xz by yourself, then you can (or have to if it is > the > packaging team's requirement) register it with the command “pristine-tar > ”. Since it is not much work, I thing that it > is fair to ask people to do it even if pe

Re: Using pristine-tar

2014-10-20 Thread Matthias Urlichs
Hi, Charles Plessy: > Pristine-tar is much about preparing a package update while not having access > to the Debian archive at the same time. Two' invokations of git-archive will > not necessary generate byte-identical tarballs. Two invocations of pristine-tar will not, either, if you happen to

Re: Using pristine-tar

2014-10-20 Thread Charles Plessy
Le Tue, Oct 21, 2014 at 12:42:56AM +0800, Thomas Goirand a écrit : > > So, just generating the orig.tar.xz from upstream Git tag, in practice, > does the same thing as pristine-tar, except that you *know* you have to > take past orig.tar.xz from the Debian archive, always, instead of > discovering

Re: Using pristine-tar

2014-10-20 Thread Thomas Goirand
On 10/13/2014 06:14 AM, Barry Warsaw wrote: > In practice, I haven't seen any problems with pristine-tar. And given that > archive uploads still currently require a tarball, and PyPI releases are > overwhelmingly tarball-based, I think it still makes sense for DPMT to > continue to use pristine-ta

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-13 Thread Barry Warsaw
On Oct 14, 2014, at 07:57 AM, Charles Plessy wrote: >Ah sorry, it was a message from Henrique de Moraes Holschuh. > >https://lists.debian.org/debian-devel/2014/08/msg00694.html Thanks, Henrique's posting does make sense. :/ -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.de

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-13 Thread Charles Plessy
Le Mon, Oct 13, 2014 at 10:40:00AM -0400, Barry Warsaw a écrit : > > I search d-d on gmane and wasn't able to find Joey's specific message about > pristine-tar bitrot. pristine-tar does have a few bugs that could be > relevant. I'm not sure where that leaves us though. Ah sorry, it was a messag

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-13 Thread Barry Warsaw
Hi Charles, thanks for the information. On Oct 13, 2014, at 08:41 AM, Charles Plessy wrote: >in the Debian Med team, we had concrete evidence last May that the >pristine-tar data bitrots with time in the way explained by Joey on >debian-devel. > >Sorry to not have a high-quality summary to propos

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread Charles Plessy
Le Sun, Oct 12, 2014 at 06:14:19PM -0400, Barry Warsaw a écrit : > On Oct 12, 2014, at 01:27 PM, Tristan Seligmann wrote: > > >That's interesting, I didn't know about that. I'm not really sure I > >understand how dgit replaces pristine-tar, unless you assume that > >every tarball you want to store

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread Barry Warsaw
On Oct 12, 2014, at 01:27 PM, Tristan Seligmann wrote: >That's interesting, I didn't know about that. I'm not really sure I >understand how dgit replaces pristine-tar, unless you assume that >every tarball you want to store is in the archive. (Perhaps that's a >reasonable assumption?) And since we

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread Tristan Seligmann
n-pristine-tar-packaging/ This doesn't load for me at the moment (database error). Okay, found it in Google's cache; unfortunately the post doesn't say much beyond "I'm going to stop using pristine-tar". -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBS

Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread W. Martin Borgert
On 2014-10-12 14:49, Thomas Goirand wrote: > Let's say there's a few more other people which > were not accounted for and that were not at Debconf, those who prefers > having upstream source code in the VCS are still the majority. And some weren't at Debconf and prefer to work with upstream source