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

Questions about inconsistencies in the documentation

Path	csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From	Soren Stoutner <soren@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Questions about inconsistencies in the documentation
Date	Mon, 16 Sep 2024 23:00:02 +0200
Message-ID	<JnqZc-cLL8-37@gated-at.bofh.it> (permalink)
X-Original-To	Debian Python <debian-python@lists.debian.org>
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Sep 16 20:59:29 2024
Old-Return-Path	<soren@debian.org>
X-Amavis-Spam-Status	No, score=-114.561 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_SCAM1=0.1, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
Organization	Debian
MIME-Version	1.0
Content-Type	multipart/signed; boundary="nextPart2930224.R5YjpgUAEL"; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Debian-User	soren
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/22341
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/17098179.uKUmxEHf3W@soren-desktop
Approved	robomod@news.nic.it
Lines	91
Sender	robomod@news.nic.it
X-Original-Date	Mon, 16 Sep 2024 13:59:09 -0700
X-Original-Message-ID	<17098179.uKUmxEHf3W@soren-desktop>
Xref	csiph.com linux.debian.maint.python:16281

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

While reading over the documentation I noticed a couple of inconsistencies.

1.
https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst

"All team members should of course follow the main discussion list:
debian-python@lists.debian.org”

"Team members who have broad interest should subscribe to the mailing list
debian-python@lists.debian.org whereas members who are only interested in some
packages should use the Package Tracking System to follow the packages."

I am already subscribed to the list, so I am not concerned about this 
personally.  But it seems like we ought to pick one recommendation on this 
subject.

2.
https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst

"debian/master - The Debianized upstream source directory.”

https://wiki.debian.org/Python/GitPackaging

"debian/main (formerly debian/master) - The Debianized upstream source 
directory.”

"To prove that all the branches got pushed correctly, in this fresh clone, 
checkout the debian/master”

"You will need to push the debian/master branch”

"Set debian-branch value to debian/master in debian/gbp.conf”

"Commit to debian/master branch (use git branch -m master debian/master to 
rename the branch).”

"Update .git/config branch debian/master to refer to merge = refs/heads/debian/
master.”

"On Salsa, set the default branch to the new debian/master branch.”

“debian-branch=debian/master”

etc. (there are quite a few other references to debian/master).

I am uncertain whether debian/master or debian/main is recommended.

-- 
Soren Stoutner
soren@debian.org

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

Thread

Questions about inconsistencies in the documentation Soren Stoutner <soren@debian.org> - 2024-09-16 23:00 +0200
  Re: Questions about inconsistencies in the documentation Soren Stoutner <soren@debian.org> - 2024-10-29 20:50 +0100

csiph-web