Your message dated Mon, 20 Feb 2017 05:36:44 +0100
with message-id <[email protected]>
and subject line Re: Bug#855527: [dpkg-dev] dpkg-buildpackage doesn't build in
parallel with --jobs/--jobs-try without custom dh_auto_build --parallel argument
has caused the Debian Bug report #855527,
regarding [dpkg-dev] dpkg-buildpackage doesn't build in parallel with
--jobs/--jobs-try without custom dh_auto_build --parallel argument
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.)
--
855527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855527
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.18.22
Severity: normal
Starting to package up udisks2 for Devuan (I'm new to packaging in
general), I noticed that even though I was telling dpkg-buildpackage to
build in parallel ('dpkg-buildpackage -b --jobs=auto -i.*'), only one
core was being used.
Reading the manpage on --jobs and --jobs-try, it sounds like various
things are being set to ensure parallel building, but it took overriding
dh_auto_build for that to be actually paid attention to:
==================================
override_dh_auto_build:
dh_auto_build --parallel
==================================
Is that intended behaviour?
Thanks
--- System information. ---
Architecture: Kernel: Linux 4.9.0-1-amd64
Debian Release: stretch/sid
990 testing 10.1.0.3 500 unstable 10.1.0.3 500
quodlibet-unstable lazka.github.io
--- Package information. ---
Depends (Version) | Installed
============================-+-============
perl:any | libdpkg-perl (= 1.18.22) | 1.18.22
tar (>= 1.28-1) | 1.29b-1.1
bzip2 | 1.0.6-8.1
xz-utils | 5.2.2-1.2
patch (>= 2.7) | 2.7.5-1
make | 4.1-9
binutils | 2.27.90.20170124-2
Recommends (Version) | Installed
======================================-+-===========
build-essential | 12.3
gcc | 4:6.3.0-1
OR c-compiler | fakeroot
| 1.21-3.1
gnupg | 2.1.18-3
OR gnupg2 | 2.1.18-3
gpgv | 2.1.18-3
OR gpgv2 | libalgorithm-merge-perl
| 0.08-3
Suggests (Version) | Installed
=============================-+-===========
debian-keyring | 2017.01.20
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi!
On Sun, 2017-02-19 at 19:43:36 +0000, OmegaPhil wrote:
> Package: dpkg-dev
> Version: 1.18.22
> Severity: normal
>
> Starting to package up udisks2 for Devuan (I'm new to packaging in
> general), I noticed that even though I was telling dpkg-buildpackage to
> build in parallel ('dpkg-buildpackage -b --jobs=auto -i.*'), only one
> core was being used.
>
> Reading the manpage on --jobs and --jobs-try, it sounds like various
> things are being set to ensure parallel building, but it took overriding
> dh_auto_build for that to be actually paid attention to:
>
> ==================================
>
> override_dh_auto_build:
> dh_auto_build --parallel
>
> ==================================
>
> Is that intended behaviour?
Yes, there are many reasons why the build system both in debian/rules
are not going to honor the parallel request, for example because they
are not Makefiles, etc. Please read the debhelper(1) and dh(1) man pages,
it's explained there. As an aside, you can simply use:
,---
%:
dh $@ --parallel
`---
Closing, as a non-bug.
Thanks,
Guillem
--- End Message ---
