[Bug 2054741] Re: dpkg-buildpackage ignores DEB_BUILD_PROFILES

[Brian Murray]

Hello Luca, or anyone else affected,

Accepted dpkg into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dpkg/1.21.1ubuntu2.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: dpkg (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.
https://bugs.launchpad.net/bugs/2054741

Title:
  dpkg-buildpackage ignores DEB_BUILD_PROFILES

Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg source package in Jammy:
  Fix Committed
Status in dpkg source package in Mantic:
  Fix Committed
Status in dpkg source package in Noble:
  Fix Released

Bug description:
  [Impact]

  DEB_BUILD_PROFILES= can be used in Debian to specify a build profile
  to use with dpkg-buildpackage. We want to use it in the systemd
  project to build the upstream packages for the Ubuntu autopkgtest
  cloud CI on Github. But in the Ubuntu's fork of dpkg,
  DEB_BUILD_PROFILES's value is ignored and unconditionally swapped with
  'noudeb'. This makes it impossible to use package-specific profiles,
  and it's a regression w.r.t Debian.

  [Fix]

  Backport patch from Noble that fixes the issue: https://code.launchpad.net/~bluca/ubuntu/+source/dpkg/+git/dpkg/+merge/461136
  and takes into account if the environment variable is set when reading the profile

  [Test]

  To reproduce it, simply print the content of DEB_BUILD_PROFILES in
  d/rules in any package and build with DEB_BUILD_PROFILES=foo dpkg-
  buildpackage. Before the fix, whatever is passed via the env var is
  ignored. After the fix, it will be respected.

  [Regression Potential]

  dpkg-buildpackage is used to build all packages, so in case of
  unforeseen issues other packages could potentially fail to build. A
  unit test exercising this change is included in the patch to minimize
  potential for regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2054741/+subscriptions