Hi!
On Wed, 2016-11-09 at 23:46:42 +, James Clarke wrote:
> Package: dpkg-dev
> Version: 1.18.13
> Severity: important
> User: debian-sp...@lists.debian.org
> Usertags: sparc64
> X-Debbugs-Cc: debian-sp...@lists.debian.org
> Unfortunately, your new specs files lead to segfaults on sparc64:
>
Hi!
On Wed, 2016-11-09 at 00:34:30 +0100, Hilko Bengen wrote:
> Package: dpkg
> Version: 1.18.13
> Severity: important
> recent rebuilds of supermin on a few architectures (at least powerpc,
> ppc64, sh4, sparc64) failed gcc no longer produces static binaries.
>
> It looks as if this breakage wa
Package: dpkg
Version: 1.18.10ubuntu1
Severity: important
Tags: patch
Dear Maintainer,
Running dpkg-parsechangelog on changelogs that produce date parsing
problems, e.g.:
Tue, 17 May 2008 10:93:55 -0500
(don't ask me how it got there, but it happened in one Ubuntu publish).
ends up with an err
Package: dpkg-dev
Version: 1.18.13
Severity: important
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc: debian-sp...@lists.debian.org
Hi Guillem,
Unfortunately, your new specs files lead to segfaults on sparc64:
> $ cat exit.c
> #include
>
> int main(int argc, char **argv) {
>
Ian Jackson:
> [1]
> Shell path glob patterns are mostly like normal glob patterns:
>
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13_03
>
> Glob patterns' bracketed [] character sets are mostly like regexp ones:
>
> http://pubs.opengroup.org/onlinepubs/9
Hi Michael,
On Wed, Nov 09, 2016 at 07:16:53PM +0100, Michael Biebl wrote:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html
> Do you also have builds for i386? (which this issue is about, amd64 is fine)
yes, they are linked from that url as well, though you can
Hi Holger,
Am 09.11.2016 um 18:10 schrieb Holger Levsen:
> On Sat, Nov 05, 2016 at 08:58:06PM +0100, Michael Biebl wrote:
>> As this breaks packages to build successfully, I'm bumping this to RC.
>> E.g. I'm unable to successfully build systemd in a freshly created
>> chroot on i386. I suspect onc
Am 09.11.2016 um 18:10 schrieb Holger Levsen:
> Hi,
>
> On Sat, Nov 05, 2016 at 08:58:06PM +0100, Michael Biebl wrote:
>> As this breaks packages to build successfully, I'm bumping this to RC.
>> E.g. I'm unable to successfully build systemd in a freshly created
>> chroot on i386. I suspect once t
Hi,
On Sat, Nov 05, 2016 at 08:58:06PM +0100, Michael Biebl wrote:
> As this breaks packages to build successfully, I'm bumping this to RC.
> E.g. I'm unable to successfully build systemd in a freshly created
> chroot on i386. I suspect once the buildds update their chroot, it will
> affect a lot
Ian Jackson writes ("dpkg-buildpackage should set LC_COLLATE=C.UTF-8"):
> [1]
> Shell path glob patterns are mostly like normal glob patterns:
>
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13_03
>
> Glob patterns' bracketed [] character sets are mostly like
For the record, rpm seems to have added support for boolean operations [0].
and - requires all operands to be fulfilled for the term to be True.
Conflicts: (pkgA and pkgB)
or - requires one of the operands to be fulfilled
Requires: (pkgA >= 3.2 or pkgB)
if - requires the first operand to be fu
Package: dpkg-dev
Version: 1.18.12
According to POSIX, the meaning of glob patterns is unspecified in
locales other than `the POSIX locale'. [1] It's not easy to see from
the spec, but the relevant env var is LC_COLLATE.
Many package build rules, dh rules, etc., rely on shell globbing.
This shel
On Wed, 9 Nov 2016, Guillem Jover wrote:
> You can do one of these:
>
> * Pass DEB_BUILD_OPTIONS=parallel=1
OK, that’s hard to do system-wide though, plus
it overrides actual user choice.
> * Pass -J1 or --jobs-try=1
To whom? Where?
> * Set jobs-try=1 in one of the dpkg-buildpackage.con
Hi!
On Wed, 2016-11-09 at 11:35:36 +0100, Thorsten Glaser wrote:
> how can we disable parallel-by-default builds now?
> #842845 was not all to clear in that.
>
> Reasons:
> • build something on a desktop while working in parallel
> • build several packages in parallel
> • run multiple buildd inst
Hi,
how can we disable parallel-by-default builds now?
#842845 was not all to clear in that.
Reasons:
• build something on a desktop while working in parallel
• build several packages in parallel
• run multiple buildd instances in parallel
So we need something that works no matter how deep dpkg
15 matches
Mail list logo
