Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Scott Talbert Newsgroups: linux.debian.maint.python Subject: Re: xlsxwriter: How to change homepage url Date: Fri, 17 Sep 2021 18:10:02 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Sep 17 16:09:30 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.139 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, FVGT_m_MULTI_ODD=0.02, LDO_WHITELIST=-5, MISSING_HEADERS=1.021, MURPHY_DRUGS_REL8=0.02] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 X-X-Sender: talbert@bear.techie.net User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Mailing-List: archive/latest/19336 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/alpine.DEB.2.22.394.2109171208140.271316@bear.techie.net Approved: robomod@news.nic.it Lines: 44 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Fri, 17 Sep 2021 12:09:13 -0400 (EDT) X-Original-Message-ID: X-Original-References: <4H8dyr2Y52z9rxP@submission02.posteo.de> <20210915134621.69c57cdd@felix.codehelp> <63d3ca4c-4a26-d5df-caff-d15d2c9cec13@debian.org> <4H8jkR055kz9rxH@submission02.posteo.de> <4H8kYP0lkFz6tmW@submission01.posteo.de> <87r1do18qu.fsf@DigitalMercury.dynalias.net> Xref: csiph.com linux.debian.maint.python:13541 On Fri, 17 Sep 2021, Scott Talbert wrote: >>>> Looking in the salsa repo [0], it is very old. And that shouldn't >>>> happen. I >>>> can updated to the last unstable version tonight/tomorrow. >>> >>> Just to improve my knowledge about Debian processes: What does it mean >>> to update the salsa repo to the current upstream? Is it the same as >>> create a new package? Or is it just one step into creating a new >>> package? >>> >> >> I didn't look at the packages in question, but as a matter of team >> policy, the Debian Python Team uses git-buildpackage repositories, with >> pristine-tar, and a repo's layout is as follows: >> >> 1. Pristine-tar branch (upstream tarball is imported here) >> 2. Upstream branch (upstream tarball is unpacked here) >> 3. Debian packaging branch (name varies) >> * https://dep-team.pages.debian.net/deps/dep14/ is the standardisation >> effort the DPT has adopted. >> * another key phrase is a "patches unapplied" packaging branch. >> >> `gbp import-orig --pristine-tar --uscan` downloads the latest tarball >> and puts it in #1, then unpacks it to #2, then creates an >> upstream/new_version tag on this upstream branch, then merges that tag >> to #3. One then needs update the version of the current changelog entry >> (if UNRELEASED), or create a new one with `dch >> -v$new_upstream_version-1`. Finally, one may need to use `gbp pq` to >> import, rebase, and export an existing quilt patch series onto the new >> upstream release. >> >> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#git-procedures >> https://wiki.debian.org/Python/FAQ >> https://wiki.debian.org/Python/GitPackaging >> >> Other teams/individuals have different policies and practises. > > I'm working on updating this package. Package has been updated to version 3.0.1 and brought up to current standards. :) Scott