Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #9541

Re: PAPT git migration

Path csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Simon McVittie <smcv@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: PAPT git migration
Date Thu, 01 Jun 2017 01:20:01 +0200
Message-ID <tNl4d-34b-5@gated-at.bofh.it> (permalink)
References <tNh0B-4U-7@gated-at.bofh.it> <tNjvr-20L-1@gated-at.bofh.it> <tNk89-2vg-7@gated-at.bofh.it>
X-Original-To debian-python@lists.debian.org
X-Mailbox-Line From debian-python-request@lists.debian.org Wed May 31 23:17:00 2017
Old-Return-Path <smcv@debian.org>
X-Amavis-Spam-Status No, score=-6.88 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -5
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
User-Agent NeoMutt/20170306 (1.8.0)
X-Mailing-List <debian-python@lists.debian.org> archive/latest/14918
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20170531231639.jbfujevwijz2bu55@perpetual.pseudorandom.co.uk
Approved robomod@news.nic.it
Lines 70
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Thu, 1 Jun 2017 00:16:39 +0100
X-Original-Message-ID <20170531231639.jbfujevwijz2bu55@perpetual.pseudorandom.co.uk>
X-Original-References <20170531185815.GA1153@bach.rivera.co.za> <20170531173220.6df84975@subdivisions.wooz.org> <20170531221645.GB1153@bach.rivera.co.za>
Xref csiph.com linux.debian.maint.python:9541

Show key headers only | View raw


On Thu, 01 Jun 2017 at 00:16:45 +0200, Stefano Rivera wrote:
> Hi Barry (2017.05.31_23:32:20_+0200)
> > $ gbp pq export
> > - This doesn't work until you at least do a first pq import, but now I see the
> >   d/p/changlog-docs patch gets changed in ways that lose information:
> 
> Sounds like a limitation of pq import. I'm suprised it doesn't support
> DEP3.

DEP3 describes some metadata fields, and a family of incompatible formats
(which do not necessarily seem to be designed for machine-readability) that
use those metadata fields.

gbp pq import consumes patches in `git format-patch` format. One of the
possible formats in the DEP3 family (with RFC2822-style From/Date/Subject,
unindented long description, and all non-email fields in a trailing
pseudo-header similar to common practice for Signed-off-by) is compatible
with that:

    From: ...
    Date: ...
    Subject: First line of description

    More description
    more description
    yet more description

    Bug-Debian: ...
    Applied-upstream: ...
    More-DEP3-fields-in-pseudo-header: ...
    ---
     optional diffstat here

    diff --git ...
    ...

but this style (which is a DEP3 invention, and not used outside Debian and its
derivatives) is not:

    Author: ...
    Description: First line of description
     More description
     more description
     yet more description
    Bug-Debian: ...

Converting the latter into the former seems like a valid gbp pq feature
request, but might not be practically feasible (detecting that style
mechanically so that it can be parsed is probably not trivial).

For packages that are maintained in git, either upstream or downstream,
preferring the former format makes a lot of sense IMO. Anything that relies
on round-tripping patches through git like gbp pq does is going to want
git-format-patch-compatible patches.

> So, our options are:
> 1. fix pq
> 2. modify all the patches to a format that pq understands
> 3. leave this to the maintainer to resolve (I think we expect all pq use
>    to be entirely local, so pq use isn't something we're imposing on
>    anyone)

I think it would make sense to leave the patches as-is during initial
conversion, and expect maintainers who are interested in using gbp pq
to resolve this when they import and re-export the patch series. Hopefully
a lot of current patches will become unnecessary with newer upstream
software versions, so preferring git format-patch style for new patches
might be a good "90%" solution.

    S

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-05-31 21:00 +0200
  Re: PAPT git migration "W. Martin Borgert" <debacle@debian.org> - 2017-05-31 23:00 +0200
    Re: PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-06-01 00:30 +0200
  Re: PAPT git migration Barry Warsaw <barry@debian.org> - 2017-05-31 23:40 +0200
    Re: PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-06-01 00:20 +0200
      Re: PAPT git migration Mattia Rizzolo <mattia@debian.org> - 2017-06-01 01:20 +0200
      Re: PAPT git migration Simon McVittie <smcv@debian.org> - 2017-06-01 01:20 +0200
        Re: PAPT git migration Scott Kitterman <debian@kitterman.com> - 2017-06-01 05:10 +0200
          Re: PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-06-01 06:10 +0200
        Re: PAPT git migration Brian May <brian@linuxpenguins.xyz> - 2017-06-01 07:10 +0200
        Re: PAPT git migration Brian May <brian@linuxpenguins.xyz> - 2017-06-01 07:10 +0200
          Re: PAPT git migration Simon McVittie <smcv@debian.org> - 2017-06-01 08:20 +0200
    Re: PAPT git migration Brian May <brian@linuxpenguins.xyz> - 2017-06-01 02:00 +0200
      Re: PAPT git migration Raphael Hertzog <hertzog@debian.org> - 2017-06-05 11:00 +0200
        Re: PAPT git migration Mattia Rizzolo <mattia@debian.org> - 2017-06-05 11:20 +0200
  Re: PAPT git migration Jordan Justen <jljusten@gmail.com> - 2017-07-10 03:00 +0200
  Re: PAPT git migration Daniel Stender <debian@danielstender.com> - 2017-08-01 00:40 +0200

csiph-web