Your message dated Thu, 13 Oct 2022 23:41:24 +0200
with message-id <Y0iGBBjJ/ddlo...@thunder.hadrons.org>
and subject line Re: Bug#5210: dpkg-source complains on substitution variables
has caused the Debian Bug report #5210,
regarding dpkg-gencontrol: Support substvars in names of binary packages
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 ow...@bugs.debian.org
immediately.)
--
5210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=5210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.8.3.1
Severity: normal
dpkg-gencontrol fails to function if package names contain variables.
For example, a control file containing:
Package: libgimpprint${Upstream-Version}
Will not work. Calling dpkg-gencontrol fails:
scribe% dpkg-gencontrol -VUpstream-Version=4.1.5 -plibgimpprint4.1.5
dpkg-gencontrol: error: package libgimpprint4.1.5 not in control info
Calling it with "-plibgimpprint\${Upstream-Version}" yeilds:
dpkg-gencontrol: unknown option `-plibgimpprint${Upstream-Version}'
Debian Release: testing/unstable
Kernel Version: Linux scribe 2.4.0 #4 Fri Jan 19 13:22:59 EST 2001 i586 unknown
Versions of the packages dpkg-dev depends on:
ii binutils 2.10.91.0.2-4 The GNU assembler, linker and binary utiliti
ii cpio 2.4.2-36 GNU cpio -- a program to manage archives of
ii make 3.79.1-4 The GNU version of the "make" utility.
ii patch 2.5.4-3 Apply a diff file to an original
ii perl 5.6.0-21 Larry Wall's Practical Extracting and Report
^^^ (Provides virtual package perl5)
--- End Message ---
--- Begin Message ---
Hi!
On Fri, 1996-11-01 at 09:14:57 +1100, Mr Stuart Lamble wrote:
> Package: dpkg
> Version: 1.4.0.2
> When I was building up libelf0, I tried using ${MAJOR} in debian/control:
>
> Package: libelf${MAJOR}
> ...
> Package: libelf${MAJOR}-dev
>
> in an attempt to not have to edit the control file when libelf 1.0.0 comes
> out. (yeah, I'm lazy. :) dpkg-source barfs on this, despite having setup
> substvars properly, claiming that the package has two conflicting names,
> libelf0 and libelf${MAJOR}.
>
> I worked around it by changing the ${MAJOR}s to 0, but as I read the manual,
> it should know how to use substvars to do the required job. 'Course, I could
> be showing off my ignorance here. :)
This has been marked as wontfix for a long time, and that's not going
to change (at least in the foreseeable future). Some time ago I added an
entry covering this to the dpkg FAQ at
<https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_are_substvars_not_effective_.28by_default.29_on_parts_of_debian.2Fcontrol.3F>,
so there's no point in keeping this wontfix bug open, thus closing it
now.
Thanks,
Guillem
--- End Message ---
