Your message dated Thu, 13 Oct 2022 23:17:10 +0200
with message-id <[email protected]>
and subject line Re: Bug#677474: Substvars for Build-Depends in the .dsc file
has caused the Debian Bug report #677474,
regarding dpkg-dev: support substvars in Build-Depends
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.)
--
677474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677474
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: dpkg_1.17.10
Severity: wishlist
Tags: patch
User: [email protected]
Usertags: rebootstrap
Dear dpkg maintainers,
Let us revisit a less intrusive variant of #677474. My request is to
enable interpolation of ${source:Version} in Build-Depends and friends.
Of course this arises from a practical need:
Quite a few packages use the binaries created in the process of building
the package. A primary example affecting 200 packages is help2man.
Unfortunately those binaries are not always executable. Most notably
they are not executable when cross compiling. Rather than resorting to
ugly hacks it would be nice to just use the build version of those tools
to generate manual pages or facilitate other tasks. In most cases that
would amount to:
Source: foo
Build-Depends: foo <profile.cross>
In many cases this would be correct, but ideally we want to ensure that
the manual pages created match the source. So the dependency needs to be
rather stricter:
Build-Depends: foo (= ${source:Version}) <profile.cross>
This use of substvars would not pose any problems for regular
build-ability of the package, because the dependency is not evaluated in
the absence of the cross profile.
Thanks for considering
Helmut
diff -Nru dpkg-1.17.10/debian/changelog dpkg-1.17.10+nmu1/debian/changelog
--- dpkg-1.17.10/debian/changelog 2014-06-05 21:05:39.000000000 +0200
+++ dpkg-1.17.10+nmu1/debian/changelog 2014-06-12 22:26:03.000000000 +0200
@@ -1,3 +1,10 @@
+dpkg (1.17.10+nmu1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Support interpolating ${source:Version} in Build-Depends. Closes: #-1
+
+ -- Helmut Grohne <[email protected]> Thu, 12 Jun 2014 22:25:43 +0200
+
dpkg (1.17.10) unstable; urgency=medium
[ Guillem Jover ]
diff -Nru dpkg-1.17.10/scripts/dpkg-source.pl
dpkg-1.17.10+nmu1/scripts/dpkg-source.pl
--- dpkg-1.17.10/scripts/dpkg-source.pl 2014-05-30 18:30:50.000000000 +0200
+++ dpkg-1.17.10+nmu1/scripts/dpkg-source.pl 2014-06-12 22:25:39.000000000
+0200
@@ -341,6 +341,7 @@
my ($ok, $error) = version_check($v);
error($error) unless $ok;
$fields->{$_} = $v;
+ $substvars->set_version_substvars($v);
} elsif (m/^Binary-Only$/) {
error(_g('building source for a binary-only release'))
if $v eq 'yes' and $options{opmode} eq '-b';
--- End Message ---
--- Begin Message ---
On Thu, 2012-06-14 at 17:01:37 +0200, Guillem Jover wrote:
> tag 677474 wontfix
> thanks
> Sorry, but this is not going to happen, the fact that these source
> handling programs do not automatically honour substvars is on purpose.
> It's the same principle as in #5210 and friends. Tagging accordingly.
Some time ago I added an entry in the dpkg FAQ
<https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_are_substvars_not_effective_.28by_default.29_on_parts_of_debian.2Fcontrol.3F>,
so I don't see much point in keeping this open wontfix bug. Thus
closing.
Thanks,
Guillem
--- End Message ---
