Your message dated Sat, 11 Jul 2009 17:16:39 +0200
with message-id <20090711151639.gc8...@jones.dk>
and subject line Re: [Build-common-hackers] Bug#486848: cdbs binary-arch,
binary-indep targets should depend the build target (per Debian Policy 4.9)
has caused the Debian Bug report #486848,
regarding cdbs binary-arch, binary-indep targets should depend the build target
(per Debian Policy 4.9)
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.)
--
486848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdbs
Version: 0.4.52
Severity: normal
>From Debian Policy 4.9:
The binary target must be all that is necessary for the user to build the
binary
package(s) produced from this source package. It is split into two parts:
binary-arch builds the binary packages which are specific to a particular
architecture, and binary-indep builds those which are not.
[...]
Both binary-* targets should depend on the build target, or on the appropriate
build-arch or build-indep target, if provided, so that the package is built if
it has not been already. It should then create the relevant binary package(s),
using dpkg-gencontrol to make their control files and dpkg-deb to build them
and
place them in the parent of the top level directory.
In the situation where the package needs to be built before the binary package
can be prepared, making the `binary` target will fail because CDBS does not have
the `binary-arch` or `binary-indep` targets depending on `build`.
I am working on a lockrun package through Debian mentors which you can grab:
dget
http://mentors.debian.net/debian/pool/main/l/lockrun/lockrun_0~20080520-1.dsc
The debian/rules can be viewed directly via:
http://svn.debian.org/wsvn/collab-maint/deb-maint/lockrun/trunk/debian/rules?op=file&rev=10271&sc=1
In this instance, the `binary` target fails because the patches have been
applied:
nsla...@bytesexual: ~/software/debian/lockrun/trunk $ fakeroot ./debian/rules
binary
test -x debian/rules
dh_testroot
dh_clean -k
dh_installdirs -A
sed "s/@version@/0~20080520/" < lockrun.c > lockrun.sed.c
cc lockrun.sed.c -o lockrun
cp lockrun debian/lockrun/usr/bin
help2man -N -n "a cron job overrun protection utility" ./lockrun > lockrun.1
help2man: can't get `--help' info from ./lockrun
make: *** [common-install-prehook-impl] Error 1
I have added the following line as a temporary workaround:
binary-arch binary-indep: build
I am hoping something similar can be added to CDBS to fix this problem.
Thanks,
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.20.3-bytemark-uml-2
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages cdbs depends on:
ii debhelper 7.0.10 helper programs for debian/rules
Versions of packages cdbs recommends:
ii autotools-dev 20080123.1 Update infrastructure for config.{
-- no debconf information
--
Noah Slater, http://bytesexual.org/nslater/
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Mon, Jun 22, 2009 at 08:27:52PM +0200, Bastian Kleineidam wrote:
>setting this to serious since it is a policy violation and generates FTBFS
>errors, see eg. #526572.
>The workaround for the above bug was to add this to debian/rules:
>binary-arch binary-indep: install-arch install-indep
CDBS properly invokes all required rules when "binary" is called, so
does not violate Policy. Or at least it is believed to not violate the
parts of Policy initially quoted in this bug report.
It seems that you simply make the wrong assumption that all build rules
are completed before install rules are started.
You can enforce such serialization yourself by adding the following:
install/linkchecker-gui:: install/linkchecker
Or you can do other rearrangements of your packaging, having in mind
that each binary package may be configured, built, installed and
packaged independently of each other unless explicitly enforced to "wait
for each other".
Closing as a non-bug.
If you still believe that this is a case of violating the parts of
policy initially quoted then please elaborate.
If you believe this violates other parts of Policy, then please file a
separate bugreport with more details.
Thanks a lot for your info and concern about cdbs.
- Jonas
- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBCgAGBQJKWKzXAAoJECx8MUbBoAEhz4MP/jDMAhqbgZtFSJ2rynUHoVak
OLwK10X9JuGs52kC460DQNfWi7yLGnupYxAtiQvVbgJnFELiZZ0ad44FANGygaIj
DyceMGXKJqIwMrpernJCxzcizG12to9MeoYREfwq40JIBi0YZY/dk3+GkrhDrrn6
ulS6MJ4JZenTa+BziXkQ2k8jE0PkEsaDKHPYtElJVpQCJ5rftPPP22gayJqPZVEr
5NiNDTWmed9g4lPpd8e5P8WHQfR5tCA0eCbP2uiIy/NL3uUIXBurqz7wXhlN4amg
tM077eMraPKz9mOlRIMffo0d9sD+lpN9r+AROTiQArnnGkizUP51rKyHXqM8gy+b
BeHW5Jr7+pmLln0+h6NN7Q++WAzZNjKAHHFQedR9/IwK6Rhs+4rzSIDQIeBMNwxH
aARql8CozN9rA9VDb2XO71YsBqWbUdusrzke1aSgtNYHYT3WXn1Ng+woBzJh2RXn
nA4q6m4+BiVf+qD78t1u6VUot+jYPTN6iU4nm0Lz6OEJd22S6bY99S3ZuEJEdo3S
jNQzoBuRudwBa5zYOJUK3pWTm32fNSk2rcT7YJPMXHRahSW6YpRlDgRYZ8hIMLUw
0AU9rO37ayqQqwNw0PBTODzLAFx01Y0hfev8HRPp4cn5JTQ6RPik4Hmh0McBawQi
AfDTMB1MLFfSmkFT25UK
=Jzez
-----END PGP SIGNATURE-----
--- End Message ---
