Your message dated Thu, 18 Dec 2025 17:56:25 -0700
with message-id <3766497.R56niFO833@soren-desktop>
and subject line Re: Bug#1123568: dh-exec-filter-build-profiles: error: 
'!nodoc' is not a valid build profile restriction formula
has caused the Debian Bug report #1123568,
regarding dh-exec: pass full build-profile formula to 
Dpkg::BuildProfiles::parse_build_profiles
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.)


-- 
1123568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123568
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dh-exec
Severity: important
Version: 0.30
Control: affects -1 src:util-linux
X-Debbugs-CC: Guillem Jover <[email protected]>

Hi,

dpkg 1.23.0 made the parser used in 
Dpkg::BuildProfiles::parse_build_profiles more strict. It now 
rejects Build-Profiles strings which are not surrounded by '<' and 
'>'. This makes the util-linux build fail with:

  dh-exec-filter-build-profiles: error: '!nodoc' is not a valid build profile 
restriction formula

An example line in debian/util-linux.install is:

  <!nodoc> usr/share/man/man8/sulogin.8

After some discussion with Guillem, we'd like to propose this 
minimal diff to dh-exec, to make it work with the newer dpkg:


diff -Nru dh-exec-0.30/lib/dh-exec-filter-build-profiles 
dh-exec-0.30+nmu1/lib/dh-exec-filter-build-profiles
--- dh-exec-0.30/lib/dh-exec-filter-build-profiles      2024-05-19 
12:30:01.000000000 +0200
+++ dh-exec-0.30+nmu1/lib/dh-exec-filter-build-profiles 2025-12-17 
23:02:26.000000000 +0100
@@ -34,7 +34,7 @@
     if (!/<([^>]*)>/) {
         $line_concerned = 1;
     }
-    while (/<([^>]*)>/) {
+    while (/(<([^>]*)>)/) {
         $line_concerned |= profile_concerned ($1, $_);
         s/<([^>]*)>\s+//;
     }


I've verified this fixes the util-linux build.

I understood Guillem would appreciate it if a fix could land soon in dh-exec.

Thanks,
Chris

diff -Nru dh-exec-0.30/lib/dh-exec-filter-build-profiles dh-exec-0.30+nmu1/lib/dh-exec-filter-build-profiles
--- dh-exec-0.30/lib/dh-exec-filter-build-profiles	2024-05-19 12:30:01.000000000 +0200
+++ dh-exec-0.30+nmu1/lib/dh-exec-filter-build-profiles	2025-12-17 23:02:26.000000000 +0100
@@ -34,7 +34,7 @@
     if (!/<([^>]*)>/) {
         $line_concerned = 1;
     }
-    while (/<([^>]*)>/) {
+    while (/(<([^>]*)>)/) {
         $line_concerned |= profile_concerned ($1, $_);
         s/<([^>]*)>\s+//;
     }

--- End Message ---
--- Begin Message ---
On Thursday, December 18, 2025 1:30:33 AM Mountain Standard Time gregor 
herrmann wrote:
> On Wed, 17 Dec 2025 19:20:41 -0700, Soren Stoutner wrote:
> >I didn’t receive this error a few days ago when building 1.5.1-1 for
> >experimental, so I assume this was a change introduced with debhelper 
13.29.
> 
> Or dpkg 1.23.{0,1,2} … My guess would be 1.23.0, and there are build
> profiles related fixes in .1 and .2, according to the changelog.

Thanks for the pointer.  It just built successfully with dpkg 1.23., which was 
uploaded to unstable today.

-- 
Soren Stoutner
[email protected]

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to