Hi,
Andreas Metzler wrote:
---
Somehow make dpkg-buildpackage -B make use of the build-arch target
if present. Either by detecting it automatically or by something like
#229357.
---
The entire issue circles around not being able to reliably detect
whether the target
Frank Lichtenheld writes (Re: Bug#390915: Revised patch):
This would probably fix #207289 on the side because it makes all
read-only files in the tar ball writable, right? (At least for all
remotely practical umask settings...)
Yes.
Will apply the patch.
Excellent, thanks.
Ian.
--
To
Simon Richter [EMAIL PROTECTED] writes:
Hi,
Andreas Metzler wrote:
---
Somehow make dpkg-buildpackage -B make use of the build-arch target
if present. Either by detecting it automatically or by something like
#229357.
---
The entire issue circles around not
Hello,
Goswin von Brederlow wrote:
The seconds part requires that tools like sbuild and pbuilder know
beforehand if build or build-arch will be used.
For packages that do not implement build-arch, it is acceptable to call
the build target with only B-D installed, because that is the way the
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.4
# patch is against dpkg-source
reassign 426752 dpkg-dev
Bug#426752: Ubuntu-specific Maintainer: field processing, safety check
Bug reassigned from package `dpkg' to `dpkg-dev'.
End
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.4
reassign 430367 dpkg-dev
Bug#430367: Integrate support of a newer dpkg-shlibdeps working at the symbol
level
Bug reassigned from package `dpkg' to `dpkg-dev'.
End of message,
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.4
tags 391435 - patch
Bug#391435: dpkg: [INTL:da] Updated Danish program translations
Tags were: l10n patch
Tags removed: patch
# someone forgot to cc [EMAIL PROTECTED]
tags 391435
Processing commands for [EMAIL PROTECTED]:
tag 375506 - patch
Bug#375506: dpkg --search needs more escaping
Tags were: patch
Tags removed: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
On Mon, Jul 02, 2007 at 06:16:31PM +0200, Frank Lichtenheld wrote:
tag 375506 - patch
thanks
On Wed, Jul 05, 2006 at 05:41:54PM +1000, Brendan O'Dea wrote:
On Sat, Jul 01, 2006 at 07:07:11PM +0200, Nicolas François wrote:
On Thu, Jun 29, 2006 at 05:43:48PM +1000, Brendan O'Dea wrote:
tag 375506 - patch
thanks
On Wed, Jul 05, 2006 at 05:41:54PM +1000, Brendan O'Dea wrote:
On Sat, Jul 01, 2006 at 07:07:11PM +0200, Nicolas François wrote:
On Thu, Jun 29, 2006 at 05:43:48PM +1000, Brendan O'Dea wrote:
We could do something similar for --search (see patch following),
On Wed, May 30, 2007 at 03:32:59PM -0600, Bruce Sass wrote:
On Wed May 30 2007 12:42:07 pm you wrote:
If you have any comments regarding our approach we'd of course be
happy to hear about them.
I don't think it is a good idea to hard-code downstream specific bits
into the source...
I
On Mon, Jul 02, 2007 at 12:23:33PM -0400, Justin Pryzby wrote:
On Mon, Jul 02, 2007 at 06:16:31PM +0200, Frank Lichtenheld wrote:
Just for the record, I would opose both patches on the ground of very
confusing and undefined behaviour.
Also, if this is not intended to work, it's okay to close
Your message dated Mon, 02 Jul 2007 23:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#428470: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#430008: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#428169: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#427827: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#428169: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#207289: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#427988: fixed in dpkg 1.14.5
has caused the attached Bug report 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
Your message dated Mon, 02 Jul 2007 23:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#428470: fixed in dpkg 1.14.5
has caused the attached Bug report 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
20 matches
Mail list logo
