Path: csiph.com!goblin1!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!bofh.it!news.nic.it!robomod From: Brian May Newsgroups: linux.debian.maint.python Subject: Re: Git migration schedule Date: Tue, 06 Oct 2015 02:40:02 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 6 00:30:04 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.68 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FOURLA=0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no autolearn_force=no X-Policyd-Weight: DYN_NJABL=SKIP(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=SKIP(-1.5) CL_IP_EQ_HELO_IP=-2 (check from: .microcomaustralia. - helo: .mail-ig0-x22a.google. - helo-domain: .google.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microcomaustralia.com.au; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=0zGJls8XwhLd7unvA2591cUbWlYhnKVThTlQlq4eUxI=; b=YkORV/fvrtKq4f4AXzfzxMNpDVlE1oQqiPq0hoOj3lrAjSELq1fWGJIUUvqw2DNAYJ daLV/NzNhCZJTC/aXX2ecm0fznsIXjNaiwNFowXe1yWg+zt0TNjIamPdDtsucFz+ortu u19TvVTnH6xtOdLcl3G9s8ot69N+9b8CDSygg= X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=0zGJls8XwhLd7unvA2591cUbWlYhnKVThTlQlq4eUxI=; b=RhTDsBJZW632d0oPl3+Ju6GqvTe0xIX/UDc2I9jXCUlPl2w2En4WeTByREZ6qlXn3H t7+FHXI6CugcJDi1UqX7x1gpKilMwxMjAhbpG5Poki29DKBgmiKnbuNBhhSS6/XpAqnw 5D99A/95XPhOWsOzyYsVkXWmxaghOYBkqZr98/qIVO7FO+vL8CyNm3qicjU2cXVPaRJl oaKJYXh2apNPOlZeKYuyvUokp8AckzH8kAxiwxuaNz4IiIU+/cv4gz+2Gs7IkU2iH9O7 0qQ5oc8ByBADg1pt7n27dMVUEJ5gCgS0XiIzPF9hgmRu2cpxnRhyaL1oLnhKgwqWYJhE IwOA== X-Gm-Message-State: ALoCoQlFQE6nkHE+YkYwbJFcg5dj8tpaSunEh77zV6wYWwHsFE0/iSm7Q+sukvbfMKKe1R+Yznpg X-Received: by 10.50.6.16 with SMTP id w16mr12773601igw.74.1444091385619; Mon, 05 Oct 2015 17:29:45 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7ba979721043f3052164ba8c X-Mailing-List: archive/latest/12799 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAA0ZO6BzjoCfmFk5j_wxAJJfkdtfeF6y8Ybdcs-9w6q9fcx4LQ@mail.gmail.com Approved: robomod@news.nic.it Lines: 84 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 06 Oct 2015 00:29:35 +0000 X-Original-Message-ID: X-Original-References: <20151002102428.37362c96@limelight.wooz.org> <20151003094748.GB3567@bach.rivera.co.za> <20151003185221.GC3567@bach.rivera.co.za> <20151005114901.296f23b6@limelight.wooz.org> Xref: csiph.com linux.debian.maint.python:7488 --047d7ba979721043f3052164ba8c Content-Type: text/plain; charset=UTF-8 On Tue, 6 Oct 2015 at 02:49 Barry Warsaw wrote: > Waiting longer isn't an option IMHO. It's helping to add to the > dysfunction > of the team. I will also offer to help if the 3.5 transition gets stuck > because of the git conversion. > Hurry up and break my packages :-) Do the Vcs-* headers in debian/control get updated automatically or do these need to be updated manually? Looks like it gets updated automatically. Good. Maybe after the migration, add a check to lintian to check for obsolete Vcs-*? Might ensure no accidents happen, e.g. with somebody building and uploading from old subversion by mistake. Thinking it might be good to have a list somewhere of packages that should get manually checked (and where this hasn't happened yet) after the migration is complete. Otherwise we might all assume somebody else has checked a package, and it gets forgotten. I guess I should look at my packages. They tend to be relatively simple, don't expect any problems. Just one problem(?) I do see, some of the commits corresponding to patches have the following committer: Stefano Rivera e.g. https://anonscm.debian.org/cgit/python-modules/svn-migration/django-tables.git/commit/?id=17afaee37dc0be9d40ba5bdd1af8f254ef42a46a from: https://anonscm.debian.org/cgit/python-modules/svn-migration/django-tables.git/ This looks like a mistake to me, Stefano didn't contribute these changes. Suspect it might be a default used because there was no author information in the original debian/patches/* file. --047d7ba979721043f3052164ba8c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, 6 Oct 2015 at 02:49 Barry Warsaw <barry@debian.org> wrote:
Waiting longer isn't an option= IMHO.=C2=A0 It's helping to add to the dysfunction
of the team.=C2=A0 I will also offer to help if the 3.5 transition gets stu= ck
because of the git conversion.

Hurry up= and break my packages :-)

Do the Vcs-* headers in debian= /control get updated automatically or do these need to be updated manually?= Looks like it gets updated automatically. Good.

Maybe after the mig= ration, add a check to lintian to check for obsolete Vcs-*? Might ensure no= accidents happen, e.g. with somebody building and uploading from old subve= rsion by mistake.

Thinking it might be good to have a lis= t somewhere of packages that should get manually checked (and where this ha= sn't happened yet) after the migration is complete. Otherwise we might = all assume somebody else has checked a package, and it gets forgotten.
<= br>
I guess I should look at my packages. They tend to be relativ= ely simple, don't expect any problems.

Just one probl= em(?) I do see, some of the commits corresponding to patches have the follo= wing committer:

Stefano Rivera <stefano@rivera.za.net>

e.g.

https://anonscm.debian.= org/cgit/python-modules/svn-migration/django-tables.git/commit/?id=3D17afae= e37dc0be9d40ba5bdd1af8f254ef42a46a

This looks like a mistake to me, Ste= fano didn't contribute these changes. Suspect it might be a default use= d because there was no author information in the original debian/patches/* = file.
--047d7ba979721043f3052164ba8c--