Your message dated Thu, 12 Oct 2017 10:18:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#839186: libsoup2.4: dpkg-buildpackage builds
everything as root
has caused the Debian Bug report #839186,
regarding libsoup2.4: dpkg-buildpackage builds everything as root
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.)
--
839186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839186
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libsoup2.4
Version: 2.56.0-1
Dear maintainer:
As a normal user, I do this:
$ apt-get source libsoup2.4
$ cd libsoup2.4-2.56.0
$ debian/rules build
and this is what happens:
make: 'build' is up to date.
(There is already a directory called "build")
As a result, "dpkg-buildpackage" (without -A or -B) builds most
stuff as root. This is from the reproducible builds site:
[...]
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --with gir,gnome
dh_testdir
dh_auto_clean
dh_autoreconf_clean
dh_gnome_clean
dh_clean
debian/rules build
make: 'build' is up to date.
fakeroot debian/rules binary
dh binary --with gir,gnome
dh_testdir
dh_update_autotools_config
debian/rules override_dh_autoreconf
make[1]: Entering directory '/build-1st/libsoup2.4-2.56.0'
[ most of the build happens here, as root(fakeroot) ]
Policy says "The build target should perform all the configuration and
compilation of the package", so building everything as root is clearly
undesirable.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2.60.0-1
Am 12.10.2017 um 03:16 schrieb Jeremy Bicha:
> Control: tags -1 +unreproducible +moreinfo
>
> libsoup2.4 has a very ordinary minimal dh7 rules file.
>
> https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/libsoup2.4/debian/rules?view=markup
>
> Please provide more detail about the issue you reported. Otherwise, we
> will be forced to close this bug.
The problem Santiago was encountering happens when the source tarball
ships a "build" directory so dh/make thinks the "build" target is
already up-to-date. One usually can work around that by marking that
target as .PHONY, but with dh this is afaik not really possible.
Anyway, this particular issue was indeed fixed upstream by renaming the
build directory [1].
Closing the bug report accordingly.
Fwiw, this is by far not the only package possibly affected by this.
In the past, a lot of GNOME packages shipped the win32 build files in a
build/ directory. I think there was a recent push to move those from
build/win32 to win32/
I still quite a few packages with a build directory though. An
incomplete list:
atkmm/build
cairo/build
clutter/build
clutter-gst/build
clutter-gtk/build
cogl/build
exempi/build
gconfmm/build
gcr/build
glade/build
glib/build
glibmm/build
gmime/build
gnome-keyring/build
gsettings-desktop-schemas/build
gtk+/build
gtkmm/build
libchamplain/build
libsecret/build
libsigcplusplus/build
libxml++/build
loudmouth/build
mm-common/build
pangomm/build
realmd/build
seahorse/build
Michael
[1] https://git.gnome.org/browse/libsoup/commit/?id=94b6b3da
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
