Your message dated Wed, 6 Sep 2017 03:09:48 +0200
with message-id <20170906010948.3wmpxe6qvgix5...@gaara.hadrons.org>
and subject line Re: Bug#864934: dpkg-buildpackage: Don't check builddeps for
source-only builds
has caused the Debian Bug report #864934,
regarding dpkg-buildpackage: Don't check builddeps for source-only builds
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.)
--
864934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.18.24
I recently updated my development computer to Ubuntu 17.10 and a
change introduced in dpkg 1.18.18 is annoying especially on Ubuntu
which only allows source-only uploads.
dpkg-buildpackage now fails if build dependencies are not installed
unless the -d or --no-check-builddeps flags are passed.
Please enable that option by default when -S or --build=source is used.
I build my binary packages with sbuild, but do source-only uploads
with "debuild -S".
Thanks,
Jeremy Bicha
-- System Information:
Debian Release: stretch/sid
APT prefers artful
APT policy: (500, 'artful')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.10.0-22-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Control: tag -1 wontfix
On Sat, 2017-06-17 at 13:52:19 -0400, Jeremy Bicha wrote:
> On Sat, Jun 17, 2017 at 1:04 PM, Guillem Jover <guil...@debian.org> wrote:
> > Yes, because dpkg-buildpackage will run the debian/rules clean target,
> > which by policy requires the Build-Depends/Conflicts to be satisfied.
>
> For most packages I build, dpkg-buildpackage -S running clean works
> fine without all build-dependencies installed. I manually pass -nc
> when I don't feel like installing the extra debhelper addons like
> pkg-kde-tools.
That's still an unsafe assumption, that someone knowing the packages
at hand might be able to make, but certainly it's not a good default.
> > I don't see any compelling argument presented here besides the implicit
> > "it breaks my workflow!" [W].
>
> Yes, but I think it's an extremely common workflow on Ubuntu as I
> already explained. If you're unwilling to do this for Debian, it may
> still make sense on Ubuntu.
>
> The odd part is that the behavior changed for me when I installed
> Ubuntu 17.10 Alpha but not with 17.04 (dpkg 1.18.10) so it feels like
> a recent "regression" on Ubuntu but I can't explain why I wasn't
> affected for the past year in 16.10 and 17.04.
>
> I did workaround the issue by changing my build configuration to use
> -d by default.
I think doing that by default would be a bad idea, but what is done in
Ubuntu's package is in a way not my problem so… :)
Given that there's an option available that can be used to override
the default behavior, and which can be configured as a local default,
I'm just going to close this.
Thanks,
Guillem
--- End Message ---
