Your message dated Thu, 13 Oct 2022 23:41:24 +0200
with message-id <Y0iGBBjJ/[email protected]>
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 [email protected]
immediately.)
--
5210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=5210
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.10.4
Severity: wishlist
Sometimes the-p flag for dpkg-gencontrol is just not a valid option, and
so there is no way to tell it what package to act on. Consider:
Source: linux-wlan-ng
...
Package: linux-wlan-ng-modules-${kvers}
...
Package: linux-wlan-ng
To run dpkg-gencontrol using this control file, I need to use -p since
there are multiple packages, but the name of the modules package is not
known until after the expansion is done.
joey@dragon:~package/linux-wlan-ng>dpkg-gencontrol
-p'linux-wlan-ng-modules-${kvers}'
dpkg-gencontrol: error: Illegal package name `linux-wlan-ng-modules-${kvers}'
zsh: exit 13 dpkg-gencontrol -p'linux-wlan-ng-modules-${kvers}'
joey@dragon:~package/linux-wlan-ng>dpkg-gencontrol
-p'linux-wlan-ng-modules-2.4.18' -Vkvers=2.4.18
dpkg-gencontrol: error: package linux-wlan-ng-modules-2.4.18 not in control info
The only way out at the moment is the hack of trimming the second entry
from the control file temporarily before calling dpkg-gencontrol, and then
running it wihout a -p, in which case it automatically uses the first
(and only) package.
I think that what it should do is expand variables when scanning the control
file the first time, so I can call it with -plinux-wlan-ng-modules-2.4.18.
I guess another approach could be a --package-num=1 option to pick by number,
but I don't like that idea.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux dragon 2.4.18 #1 Thu Jul 25 18:10:57 EDT 2002 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages dpkg-dev depends on:
ii binutils 2.12.90.0.1-4 The GNU assembler, linker and bina
ii cpio 2.5-1 GNU cpio -- a program to manage ar
ii make 3.79.1-14 The GNU version of the "make" util
ii patch 2.5.4-11 Apply a diff file to an original
ii perl [perl5] 5.6.1-7 Larry Wall's Practical Extraction
ii perl-modules 5.6.1-7 Core Perl modules.
--- 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 ---
