On Aug 07, 2015, at 02:37 PM, Sandro Tosi wrote:

>are we? when was the last update on it? from an external pov, there's
>not much happening on the matter

Yes, we really are.  Stefano and I (mostly him) has spent a *ton* of time
getting the conversion scripts working for the vast majority of packages.
Stefano has put up several test repos for people to play with.  There are a
few packages that will have to be converted or fixed up manually for various
reasons, but that's a very small number.  Everything I've looked at looks
great.  I hope team members will have played with those repos too.

I think the only reason why we haven't pulled the trigger before now is
because of vacation schedules and debconf.  I kind of hope that folks at
debconf will JFDI <hint, hint>.

>talking about the 'patch regime' and a tool to codify our workflow
>(which is completely unrelated to the migration) is kinda far away
>from 'everything'.

Sure, let's talk about a tool to codify our workflow!  As you say, that's a
completely different topic, so do start a new thread on that.  There have been
several attempts at pieces of that, but so far no one has pulled it all
together.

But, let's not let that block the migration.  We've needed to do it for way
too long now.  We have scripts that perform the migration to a high degree of
fidelity.  We have test repos you can play with now to get familiar with the
tools and workflow.  We have some pretty good documentation which will get
better over time.  It's time to move on.

I will say this about git-dpm vs. straight-up quilt.  If you really don't like
using git-dpm, then the experiment I'd like you to try is to clone some
packages from Stefano's test repos, try to make some changes using only
quilt.  Commit those.  Then see if they survive a `git-dpm checkout-patched`
and `git-dpm update-patches` round-trip.  If they do, then we're done.  If
not, why not?

The point is that git-dpm makes patch management easier for most people.  Some
won't like it and want to use straight up quilt, but if that's a purely a
local decision, then that's fine.  It's not like the choice between git-dpm
and git-pq because that is *not* a local decision.

Cheers,
-Barry


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150807102612.5a2df...@limelight.wooz.org

Reply via email to