Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Maintaining all of the testing-cabal packages under the OpenStack team
Date: Mon, 29 Jun 2020 16:40:05 +0200
Message-ID: <An36Z-5Od-45@gated-at.bofh.it>
References: <AmJrA-2fD-13@gated-at.bofh.it> <AmZG1-3Ec-1@gated-at.bofh.it> <An2Nz-5HX-3@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1934440.YWli6qz7PM"; micalg="pgp-sha512"; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 83
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12696

--nextPart1934440.YWli6qz7PM
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Monday, June 29, 2020 10:17:57 AM EDT Scott Talbert wrote:
> On Mon, 29 Jun 2020, Scott Kitterman wrote:
> >>>     More over, mock debhelper was upgraded to 13, for no apparent
> >> 
> >> reason
> >> 
> >>>     (yet another "cosmetic fix" that isn't helping?). I'd like to
> >> 
> >> remind
> >> 
> >>>     everyone that, increasing debhelper compat version to a number
> >> 
> >> that
> >> 
> >>>     isn't in stable, without a specific reason (like the need of a
> >> 
> >> specific
> >> 
> >>>     feature that wasn't there before) is just annoying for anyone
> >>>     maintaining backports. That's truth even for when debhelper
> >> 
> >> itself is
> >> 
> >>>     backported to oldstable (it's always nicer to be able to build a
> >>>     backport without requiring another backport at build time).
> >>> 
> >>> nope, this is not true. Using the newest debhelper compat level is
> >>> recommended, see man page. There is no reason to __not__ upgrade
> >>> debhelper compat level. I will always upgrade debhelper in my
> >> 
> >> packages
> >> 
> >>> to the newest debhelper as soon as possible. Please newer downgrade
> >>> debhelper in my packages again without asking.
> >> 
> >> I don't agree this is best practice when backports are to be expected.
> > 
> > I'm substantially less enthusiastic about bumping compat levels than
> > Ondrej, but since debhelper 13 is available in buster-backports,
> > backporting is unrelated to whether it's a good idea or not.
> 
> Can you elaborate on other reasons not the upgrade the compat levels?
> 
> Scott

This is a matter of personal preference, but since the behavior of debhelper 
changes between compat versions, I prefer no to change it unless I have time 
to thoroughly QA changes in the package.  This generally means I don't change 
it often.

Unless there are issues with a specific compat level (hello compat 11) or the 
compat level has been deprecated, I tend to not to do it, but I'm generally 
pretty minimalist in my package updates.  That doesn't mean someone else is 
wrong to do so if they've checked that package is correct after the change.

Scott K
--nextPart1934440.YWli6qz7PM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl75/ScACgkQeNfe+5rV
mvEjzw/+Ly8STO0+op6zsL9JOymEgE5mACmksd4HUmtpgLQUlCPuI5fle4VwACRL
6iBvu+mSVMPv3PtKYVV03+QZnauN9z3Cfv51YWE8oeImt2UrDfIXEoLf00NzA3aC
22ui8arAgtuwk7+QzKD2A5Gd6lZD7qFWVWdi+tqkjTsCxAClPH4wMDBMZGWS3S8T
Q2cAY8hkHEtcNkANoAIvTGArYRa/T0XOqXVFHqxMCADhJq57QQj+3u/5W8iDaI40
7fuWILYO0E1eFPV/q/yXMBtyrZA9dtoLFyEQLiqkHQTxjZOk7HRj6+N5jyiM1Ee2
dEoGDL7Uey/7RRGa5vbYG+1CmGUl82tWvxUYF57sdfz36nwD7jJYugzlyGBOxZV1
fpy8C/IdPUS5njvMn0EUwy5mFGjm980HXSYk6BEuvjsheHymjrFS+j5JQjf6N+Xc
3sl2SPYEkoeWabLK0R40U5lcUaAPsI9pGku+WBcyJc4HWTZY3sQxDo04nJrgEAe2
p5BSY4zb8qmMJBq16tpY7WXGJgU0Q1P6hbGg0nUUhsfhv5VcO/h/G2jWydQhFDSG
6elb4c2HLoJ2Jd0Vbv6nZw3e//j/0XEwWZ9nTfxITVo6my28GHGjs7vLT6StpDPV
5h6myi2wCWiIREYUyZnzfiU15/hmXrx7SkyshjqoXt+vpmalWWc=
=yAzy
-----END PGP SIGNATURE-----

--nextPart1934440.YWli6qz7PM--