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

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

Re: DPMT Policy

From Barry Warsaw <barry@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: DPMT Policy
Date 2015-10-21 15:50 +0200
Message-ID <qm1Wc-4CG-39@gated-at.bofh.it> (permalink)
References (1 earlier) <qlqae-8it-37@gated-at.bofh.it> <qlMaK-6E0-19@gated-at.bofh.it> <qlMNt-7E9-65@gated-at.bofh.it> <qlPV0-3Ig-1@gated-at.bofh.it> <qm0nn-2tz-7@gated-at.bofh.it>
Organization The Organization of Unorganized Woozalists

Show all headers | View raw

On Oct 21, 2015, at 02:06 PM, Piotr Ożarowski wrote:

>Only version to version upstream changes should be kept in the repository -
>complete upstream git history should be avoided. In order to make it
>easier to cherry-pick upstream commits as patches, add remote repository
>(example below).
> 
>  git remote add upstream_repo git://example.com/foo.git
>  git fetch upstream_repo
>  git-dpm checkout-patched
>  git cherry-pick any_upstream_commit
>  git-dpm update-patches

How about this:

"""
DPMT requires a pristine-tar branch, and only upstream tarballs can be used to
advance the upstream branch.  Complete upstream git history should be avoided
in the upstream branch.
"""

I like the cherry picking advice, so I added that to the wiki.

>I simply suggest to:
>
>s/, either as a source package for use with ``pbuilder``, ``sbuild``, etc. or as a binary package directory/ (it can be configured to use sbuild, pbuilder, etc.)/
>
>or remove this part completely

I removed the sentence about gbp.  That's a local decision so it doesn't need
to go in policy.

>nothing against this paragraph, just wanted to state that wiki will not have
>to mention it if we have a tool that configures new package the way policy
>wants.

+1

>> >I'm wondering about something that bit me recently: `gbp pull` instead
>> >of `git pull` - should we put that into policy or is wiki warning enough?
>> 
>> I think wiki is enough. It is possible to operate with just straight `git
>> pull` because it will still fetch all commits, but when you switch to one of
>> the other branches, you'll see that its head is out of date, and git will
>> prompt you to pull in that branch to update it.  `gbp pull` is mostly
>> convenience.
>
>gbp buildpackage will fail if you never switched to pristine-tar (and
>git didn't warn you about new commits). It wasn't obvious to me why
>it fails when it hit me for the first time.

Yep.  Again though, since this is a local decision, it should go in the wiki.

Cheers,
-Barry

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

Thread

Python Policy Barry Warsaw <barry@debian.org> - 2015-10-19 19:40 +0200
  Re: Python Policy Scott Kitterman <debian@kitterman.com> - 2015-10-19 20:50 +0200
  Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 21:10 +0200
    Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 21:30 +0200
      Re: Python Policy Ben Finney <ben+debian@benfinney.id.au> - 2015-10-19 21:40 +0200
        Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 21:50 +0200
    Re: Python Policy Brian May <bam@debian.org> - 2015-10-20 00:30 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 00:40 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:50 +0200
          Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:10 +0200
    Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:40 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:00 +0200
  Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-19 23:30 +0200
    Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:30 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:20 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 22:20 +0200
    Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-20 23:00 +0200
      Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-20 23:10 +0200
        Re: Python Policy Ben Finney <ben+debian@benfinney.id.au> - 2015-10-21 02:20 +0200
          Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 02:50 +0200
          Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-21 10:00 +0200
            Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 16:00 +0200
              Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 11:30 +0200
                Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-22 11:40 +0200
                Re: DPMT Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 12:30 +0200
      Re: Python Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 23:40 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 03:00 +0200
          Re: Python Policy Vincent Bernat <bernat@debian.org> - 2015-10-21 10:40 +0200
            Re: Python Policy Brian May <brian@microcomaustralia.com.au> - 2015-10-21 11:50 +0200
              PyPI wheels (was Re: Python Policy) Barry Warsaw <barry@debian.org> - 2015-10-21 16:00 +0200
                Re: PyPI wheels (was Re: Python Policy) Ian Cordasco <graffatcolmingov@gmail.com> - 2015-10-21 16:50 +0200
                Re: PyPI wheels (was Re: Python Policy) Jeremy Stanley <fungi@yuggoth.org> - 2015-10-21 17:50 +0200
            Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-21 15:50 +0200
          Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-21 14:10 +0200
            Re: DPMT Policy Barry Warsaw <barry@debian.org> - 2015-10-21 15:50 +0200
              Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-21 16:20 +0200
                Re: DPMT Policy Ben Finney <ben+debian@benfinney.id.au> - 2015-10-21 23:40 +0200
                Re: DPMT Policy Barry Warsaw <barry@debian.org> - 2015-10-22 01:00 +0200
      Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 11:20 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-23 01:40 +0200
      Re: Python Policy IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-22 11:20 +0200
        Re: Python Policy Barry Warsaw <barry@debian.org> - 2015-10-23 01:40 +0200
  Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 00:00 +0200
    Re: DPMT Policy Brian May <bam@debian.org> - 2015-10-20 00:30 +0200
    Re: DPMT Policy Barry Warsaw <barry@debian.org> - 2015-10-20 16:10 +0200
      Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 17:10 +0200
        Re: DPMT Policy Piotr Ożarowski <piotr@debian.org> - 2015-10-20 23:40 +0200
  Re: Python Policy Brian May <bam@debian.org> - 2015-10-20 00:00 +0200

csiph-web