Bug#597340: marked as done (dpkg-gencontrol: implicit substvar at the end of every field)
"Debian Bug Tracking System" <[email protected]> Sun, 07 Jun 2026 01:17:01 +0000
| Newsgroups | gmane.linux.debian.devel.dpkg.bugs |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1780795021-1195424-0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Your message dated Sun, 7 Jun 2026 03:14:09 +0200 with message-id <[email protected]> and subject line Re: Bug#597340: dpkg-gencontrol: implicit substvar at the = end of every field has caused the Debian Bug report #597340, regarding dpkg-gencontrol: implicit substvar at the end of every field to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) --=20 597340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D597340 Debian Bug Tracking System Contact [email protected] with problems ------------=_1780795021-1195424-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by bugs.debian.org; 18 Sep 2010 19:24:28 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5-bugs.debian.org_2005_01_02 (2008-06-10) on busoni.debian.org X-Spam-Level: X-Spam-Bayes: score:0.0000 Tokens: new, 9; hammy, 140; neutral, 63; spammy, 4. spammytokens:0.993-1--H*M:23032, 0.993-1--H*MI:23032, 0.985-+--News, 0.886-+--news hammytokens:0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug, 0.000-+--HX-Debbugs-Cc:sk:debian- X-Spam-Status: No, score=-12.1 required=4.0 tests=AWL,BAYES_00,FROMDEVELOPER, HAS_PACKAGE,URIBL_CNKR,XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham version=3.2.5-bugs.debian.org_2005_01_02 Return-path: <[email protected]> Received: from epice.ouaza.com ([92.243.25.41]) by busoni.debian.org with esmtp (Exim 4.69) (envelope-from <[email protected]>) id 1Ox31J-0005cR-Gu for [email protected]; Sat, 18 Sep 2010 19:24:28 +0000 Received: from soleymieux.ouaza.com (soleymieux.ouaza.com [78.225.60.32]) by epice.ouaza.com (Postfix) with ESMTPSA id B1A9A3DC06; Sat, 18 Sep 2010 21:24:13 +0200 (CEST) Received: by soleymieux.ouaza.com (Postfix, from userid 1000) id 96807332E9D; Sat, 18 Sep 2010 21:23:51 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" From: =?utf-8?q?Rapha=C3=ABl_Hertzog?= <[email protected]> To: Debian Bug Tracking System <[email protected]> Subject: dpkg-gencontrol: implicit substvar at the end of every field Message-ID: <[email protected]> X-Mailer: reportbug 4.12.6 Date: Sat, 18 Sep 2010 21:23:51 +0200 X-Debbugs-Cc: [email protected], [email protected] X-Virus-Scanned: clamav-milter 0.96.1 at epice X-Virus-Status: Clean Content-Transfer-Encoding: quoted-printable Delivered-To: [email protected] Package: dpkg-dev Version: 1.15.8.5 Severity: wishlist Every time that debhelper needs to adjust a dependency it provides a new substvar and the maintainer needs to put it in the right field. I was thinking that we could avoid the second half if some specific substvars was added at the end of every field. dpkg-gencontrol could be modified to always append the value of ${implicit:<fieldname>} at the end of the corresponding field. Maybe we should even support multiple substvars (say ${implicit:<fieldname>:<origin>}) so that there's no coordination problem if multiple tools want to add something at the end of the same field. This would even make it possible for debhelper to add dependencies that are not at all present in debian/control, like for example Breaks... this would have been handy for example when several dh_* tools have stopped doing their work on the assumption that the triggerized version of the postinst snippet was available on the system. With a break, it could ensure that the relevant package had been upgraded... With such a system, the ${misc:Depends} that we are currently adding everywhere would not have been needed. CCing -devel and Joey Hess to have some input on this idea. Do you think it would be useful ? Do you have comments and suggestions ? Cheers, --=20 Rapha=C3=ABl Hertzog =E2=97=88 Debian Developer =E2=97=88 [Flattr=3D20693= ] Follow my Debian News =E2=96=B6 http://RaphaelHertzog.com (English) =E2=96=B6 http://RaphaelHertzog.fr (Fran=C3=A7ais) ------------=_1780795021-1195424-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 597340-done) by bugs.debian.org; 7 Jun 2026 01:14:12 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-111.5 required=4.0 tests=ALL_TRUSTED,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FROMDEVELOPER, HAS_BUG_NUMBER,SPF_HELO_NONE,SPF_NONE,USER_IN_DKIM_WELCOMELIST,VERSION autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 22; hammy, 150; neutral, 69; spammy, 0. spammytokens: hammytokens:0.000-+--Hx-spam-relays-external:36ff, 0.000-+--H*r:36ff, 0.000-+--H*RT:sk:master., 0.000-+--H*RT:fe40, 0.000-+--H*RT:36ff Return-path: <[email protected]> Received: from master.debian.org ([2001:41b8:202:deb:216:36ff:fe40:4001]:33848) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <[email protected]>) id 1wW25c-0050pN-0z for [email protected]; Sun, 07 Jun 2026 01:14:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.master; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To:Cc: Content-ID:Content-Description; bh=dTWFYhqi5bEzQYYxznkDvPLTPkfe2ISsmtWkjZ7p8IM=; b=qdL2KuaLZJJ4Q+7DN6nObhK7Ou DRckB+Sw0H9ukNer8kRZHVZeffJOhx+YO7vAz9kG33Glpww7xtt4LdLENvIbSb/4hXcAo3wAsxTQA tQGGYnNcYrmoRm0P/vdCox8HAmetHuIum34el3jxgy5yXbfHTFby5Kl1Z4uph1fRpzgsFC/ZfDOwY K4B1frbCrM3d/vs6A0Fywa08tu/7oFP4r0+hpQctwdQhUChBObbyt9m88gC5y/p3d3ASknHkX4tFs UyvMqmYV2e7wk6PX0pxe6Aig4oP1G3S8E81Q3LhCTM9ZBitkEkM+N1Mhjz5jEor6WTdRK4U8S2o4a y2XsIHUA==; Received: from guillem by master.debian.org with local (Exim 4.96) (envelope-from <[email protected]>) id 1wW25a-00CRNi-2L; Sun, 07 Jun 2026 01:14:10 +0000 Date: Sun, 7 Jun 2026 03:14:09 +0200 From: Guillem Jover <[email protected]> To: =?utf-8?Q?Rapha=C3=ABl?= Hertzog <[email protected]>, [email protected] Subject: Re: Bug#597340: dpkg-gencontrol: implicit substvar at the end of every field Message-ID: <[email protected]> References: <[email protected]> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <[email protected]> Version: 1.23.0 On Sat, 2010-09-18 at 21:23:51 +0200, Raphaƫl Hertzog wrote: > Package: dpkg-dev > Version: 1.15.8.5 > Severity: wishlist > Every time that debhelper needs to adjust a dependency it provides a new > substvar and the maintainer needs to put it in the right field. I was > thinking that we could avoid the second half if some specific substvars > was added at the end of every field. > > dpkg-gencontrol could be modified to always append the value of > ${implicit:<fieldname>} at the end of the corresponding field. Maybe > we should even support multiple substvars (say > ${implicit:<fieldname>:<origin>}) so that there's no coordination problem > if multiple tools want to add something at the end of the same field. > > This would even make it possible for debhelper to add dependencies that > are not at all present in debian/control, like for example Breaks... this > would have been handy for example when several dh_* tools have stopped > doing their work on the assumption that the triggerized version of > the postinst snippet was available on the system. With a break, it could > ensure that the relevant package had been upgraded... > > With such a system, the ${misc:Depends} that we are currently adding > everywhere would not have been needed. > > CCing -devel and Joey Hess to have some input on this idea. Do you think > it would be useful ? Do you have comments and suggestions ? This got somehow implemented with the implicit substvars defined in deb-substvars(5) by the $= operator. I don't think further implicitness would be wise here, so the current support seems sufficient to me. And I'm thus closing this report now. Thanks, Guillem ------------=_1780795021-1195424-0--