Re: /usr-merge and DEP17 update: what happens next and how you can help

Path	csiph.com!news.mixmin.net!weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod
From	Simon Richter <sjr@debian.org>
Newsgroups	linux.debian.devel
Subject	Re: /usr-merge and DEP17 update: what happens next and how you can help
Date	Tue, 10 Oct 2023 08:20:01 +0200
Message-ID	<Hneg1-eO2A-1@gated-at.bofh.it> (permalink)
References	<HmIzw-esqD-1@gated-at.bofh.it> <HmXoR-eBTt-1@gated-at.bofh.it> <Hn3aV-eHl4-5@gated-at.bofh.it>
X-Original-To	debian-devel@lists.debian.org
X-Mailbox-Line	From debian-devel-request@lists.debian.org Tue Oct 10 06:13:25 2023
Old-Return-Path	<sjr@debian.org>
X-Amavis-Spam-Status	No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .psionic.psi5. - helo-domain: .psi5.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5
MIME-Version	1.0
User-Agent	Mozilla Thunderbird
Content-Language	en-US
Content-Type	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding	7bit
X-Mailing-List	<debian-devel@lists.debian.org> archive/latest/357518
List-ID	<debian-devel.lists.debian.org>
List-URL	<https://lists.debian.org/debian-devel/>
List-Archive	https://lists.debian.org/msgid-search/1c9e04d7-2b20-4adc-b3ba-67b665232420@debian.org
Approved	robomod@news.nic.it
Lines	26
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Tue, 10 Oct 2023 15:12:56 +0900
X-Original-Message-ID	<1c9e04d7-2b20-4adc-b3ba-67b665232420@debian.org>
X-Original-References	<20231008202544.GA1568690@subdivi.de> <ZSPtswShrwsZ9Crj@meyneth> <20231009181632.GA892914@subdivi.de>
Xref	csiph.com linux.debian.devel:109513

Show key headers only | View raw

Hi,

On 10/10/23 03:16, Helmut Grohne wrote:

> For one thing, dh_installsystemd generates maintainer scripts for
> restarting services. Before version 13.11.6, it did not recognize the
> /usr location. If you were to backport such a package, bookworm's
> debhelper would not generate the relevant maintainer scripts. You can
> mitigate this by issuing "Build-Depends: debhelper (>= 13.11.6~)". Thus,
> you'll be using a backported debhelper (unless the backporter carelessly
> deletes this dependency).

If that would be the only reason to require a backported debhelper, then 
it would probably be better to make the file move conditional on the 
target distribution (from "dpkg-parsechangelog -S distribution") -- the 
intention of that is immediately readable, while a versioned build 
dependency needs to be explained or a backporter might want to 
carelessly delete it.

gcc does something similar, although that uses "lsb_release -cs", which 
is technically not entirely correct since it looks at the build system, 
not the current package, but for the purpose of backports is good enough 
and avoids corner cases like "stable-proposed-updates" not matching 
"bookworm" or "bookworm-backports".

    Simon

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

Thread

Re: /usr-merge and DEP17 update: what happens next and how you can  help Andrea Bolognani <eof@kiyuko.org> - 2023-10-09 14:20 +0200
  Re: /usr-merge and DEP17 update: what happens next and how you can  help Sven Joachim <svenjoac@gmx.de> - 2023-10-09 20:20 +0200
  Re: /usr-merge and DEP17 update: what happens next and how you can  help Helmut Grohne <helmut@subdivi.de> - 2023-10-09 20:30 +0200
    Re: /usr-merge and DEP17 update: what happens next and how you can  help Andrea Bolognani <eof@kiyuko.org> - 2023-10-10 00:30 +0200
    Re: /usr-merge and DEP17 update: what happens next and how you can  help Simon Richter <sjr@debian.org> - 2023-10-10 08:20 +0200

csiph-web