'evening!
Tristan Seligmann wrote:
> Looks like your Debian account is marked emeritus; if you wish to
> re-activate it you could follow the process described here:
>
> https://www.debian.org/doc/manuals/developers-reference/developer-duties.html#returning
Thanks for the info, maybe later...
>
On 10/17/2014 01:01 AM, Tristan Seligmann wrote:
> If such a tarball exists, and is suitable
> for use in Debian, then having the upstream source in Debian match the
> tarball distributed by upstream byte-for-byte makes it much easier to
> verify that the source in Debian is unmodified from the ups
On 10/12/2014 09:30 PM, Scott Kitterman wrote:
>> Also, during the Debconf discussion, we decided we would use the
>> pristine-tar workflow, *not* using upstream VCS merge. A
>> "git-import-orig" normally goes into a single commit, which I don't
>> think would bother anyone (not on the list, or on
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
On 10/13/2014 06:11 AM, Barry Warsaw wrote:
>> While I don't agree with this decision, I prefer to just import upstream VCS
>> and do packaging based on tags, but I will still respect it when packaging in
>> the DPMT.
>
> Thank you. I personally appreciate the accommodations to the majority team
On Oct 21, 2014, at 12:48 AM, Thomas Goirand wrote:
>While I think it's important to do team work, and agree on some workflow
>conventions, I still want to explain my point of view, in the hope to
>make things better. I just hope I don't bother everyone too much with
>it... (I know I do...). Pleas
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
On 19 October 2014 23:21, Florent Rougon wrote:
> Thank you very much, that was quick! I have subscribed using:
>
>
> http://packages.qa.debian.org/cgi-bin/pts.cgi?what=advanced&package=source_package_name&email=y...@email.com
>
> The package is already uploaded, right?
It is, and processed th
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
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
On 10/21/2014 01:55 AM, Barry Warsaw wrote:
> It occurs to me too that the switch from svn to git (e.g. git-dpm) is already
> a large change to current team workflow, and dropping pristine-tar might just
> be too big a move to also do right now.
And things should move/improve incrementally as well
11 matches
Mail list logo
