From: [email protected]

Hi,

I've been notified that pbuilder runs "dpkg-buildpackage -S" on target package
source trees without having previously satisfied build dependencies.

'pbuilder' does not run dpkg-buildpackage -S.

'pdebuild' however, does.

The problem is already addressed:
although it is not yet the default behavior,
'pdebuild' with '--use-pdebuild-internal' already addresses that problem.



There is not much that can be done about this bugreport,
if there is any specific action that can be taken,
please add to this bug; otherwise, I will close this bugreport.



regards,
junichi


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

On Sat, Aug 21, 2004 at 10:18:21AM +0900, Junichi Uekawa wrote:

I've been notified that pbuilder runs "dpkg-buildpackage -S" on target package
source trees without having previously satisfied build dependencies.

'pbuilder' does not run dpkg-buildpackage -S.

'pdebuild' however, does.

Ah, ok. Sorry for the confusion.

The problem is already addressed:
although it is not yet the default behavior,
'pdebuild' with '--use-pdebuild-internal' already addresses that problem.

Then I think it should be the default behaviour. When not doing this, pdebuild has a chance of breaking the target package. Users tend to think the target package is actualy broken, which generates a lot of confusion.

Would you please consider changing that to the default option?

--
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\ (kernel of *(Berkeley Software Distribution))


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

Package: pbuilder
Version: 0.114
Severity: important

Hi!

I've been notified that pbuilder runs "dpkg-buildpackage -S" on target package source trees without having previously satisfied build dependencies.

This is not correct, since "dpkg-buildpackage -S" runs the clean target, and packages may assume in their clean targets that the build dependencies are installed. In fact, running the clean target without the build dependencies may result in serious breakage in some packages (e.g. grub). See Policy 7.6, which reads:

"The Build-Depends and Build-Conflicts fields must be satisfied when any of
the following targets is invoked: [...], clean, [...]."

Please note that I filed this bug as "important" because pbuilder only fails with some packages because of this, but when dpkg-buildpackage is fixed to check for build dependencies before running the clean target, pbuilder will presumably fail with every target package and hence this bug would be "grave".

-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i386)
Kernel: GNU/kFreeBSD 5.2.1-5
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to C)

Versions of packages pbuilder depends on:
ii coreutils 5.2.1-2 The GNU core utilities
ii debianutils 2.8.4 Miscellaneous utilities specific t pn debootstrap Not found.
ii gcc 4:3.3.4-2 The GNU C compiler
ii wget 1.9.1-4 retrieves files from the web


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)