Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Bo YU Newsgroups: linux.debian.maint.python Subject: Re: morph's abandoned packages (list) Date: Sat, 30 Mar 2024 02:10:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Mar 30 01:08:43 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.579 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, FVGT_m_MULTI_ODD=0.02, LDO_WHITELIST=-5, MONEY=0.5, RCVD_IN_DNSWL_NONE=-0.0001, STOCKLIKE=1] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: AOJu0YxzcnYI7Tr5ExdpVq1V+pAtlLaVDR3wV4rFKEtlqs/yf9PqcQvI KwAZRGFZ9JY1+K6Wf8uXrbqdZKKGveG+lLBzIH9DZKwa3UjT0sZVWRalBmc9ST4dxTyDyBu29/8 2NZX6L6Gf10pNukeSCdMZ7o2GW78= X-Google-SMTP-Source: AGHT+IGjVAGsB1LGS7cUqVYZXr9++Ik0bMgUvRcXmhJZ6RiDf1QgIOUJicLpdYF6CJoWvB1OwE5OocUtnanHDg2o5IU= X-Received: by 2002:a67:f354:0:b0:476:7d83:9db3 with SMTP id p20-20020a67f354000000b004767d839db3mr3573851vsm.10.1711760899909; Fri, 29 Mar 2024 18:08:19 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/21698 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAKq8=3JO9OGyuhfBtOu_Yhu=14kM1=HqQW=doEp2c4rmxY1PrQ@mail.gmail.com Approved: robomod@news.nic.it Lines: 71 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, roehling@debian.org X-Original-Date: Sat, 30 Mar 2024 09:08:08 +0800 X-Original-Message-ID: X-Original-References: <76kqxoclohkgpd54zhpnvmb6jut6tipz3jsq56jyfvts4asnhr@cfo3ai7zcogx> <41393ddc-754d-46e0-8f84-30bf3ad4e86f@debian.org> <8176cd5d-0713-493e-ab95-777ef83dc983@debian.org> Xref: csiph.com linux.debian.maint.python:15686 hi! On Sat, Mar 30, 2024 at 8:20=E2=80=AFAM Thomas Goirand wr= ote: > > On 3/29/24 21:18, Timo R=C3=B6hling wrote: > > Hi Thomas, > > > > * Thomas Goirand [2024-03-17 23:09]: > >> Anyone is welcome to join, it's just that I'm using git tag workflow, > >> so it doesn't fit in the DPT, but that's the only thing. > > I am not familiar with that workflow and could not find any > > documentation. Can you give me a quick overview what I should do > > differently from the "regular" DPT workflow? > > > > Cheers > > Timo > > I'm not using pristine-tar, or gbp import-orig, and don't use upstream > tarballs, but git only. Everything is done in a single (debian) branch. Just share the workflow of DPT I always follow[0]: ``` $ uscan # Download your package's upstream original tarball $ tar -xvf srcpkgname_1.0.orig.tar.gz $ cd srcpkgname_1.0 $ git init $ git checkout -b upstream $ git add . $ git commit -m "import srcpkgname_1.0.orig.tar.gz" $ git tag -s upstream/1.0 $ pristine-tar commit ../srcpkgname_1.0.orig.tar.gz upstream $ git checkout -b debian/master ``` And upgrade upstream release[1]. These should be enough. If given team maintenance, I would like to suggest to follow this. [0]: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package [1]: https://wiki.debian.org/Python/GitPackaging#New_upstream_release > The only thing that needs to be done, is to push upstream tags to the > Debian repository. The git history contains all upstream commits then, > because the workflow is to merge upstream tag. > > To upgrade to a newer upstream tag, simply do: > > ./debian/rules fetch-upstream-remote > git merge -X theirs > dch --newversion -m "New upstream release." > > Then simply generate the upstream tarball from the git tag: > ./debian/rules gen-orig-xz > > The fetch-upstream-remote and gen-orig-xz are from the > openstack-pkg-tools package, though I heard others in Debian have > standardized on something else. But who cares what wrapper one is using, > really. The point is to fetch upstream tags, merge them, and use "git > archive" to generate an orig tarball before building and uploading to > Debian. > > If the upstream release was already uploaded to Debian, best is to > download it instead of generating it, as (like with pristine-tar) > regenerating it may (in some cases) lead to a different checksum. > TIL also, thanks. BR, Bo > Cheers, > > Thomas Goirand (zigo) >