Control: retitle -1 libcrypt1: Wrong soname on ia64
On 14 Mar 2020, at 14:20, John Paul Adrian Glaubitz
wrote:
>
> Package: libcrypt1
> Version: 1:4.4.15-1
> Followup-For: Bug #953562
> User: debian-i...@lists.debian.org
> Usertags: ia64
>
> Hello!
>
> This actually causes issues on ia64 now:
Package: segemehl
Version: 0.3.4-1
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i3
Package: tabix
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386.
Package: samtools
Version: 1.9-4
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386
Package: qtltools
Version: 1.1+dfsg-3
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any
Package: libhts2
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386
Package: libhts-dev
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i
Package: delly
Version: 0.8.1-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386.
Package: augustus
Version: 3.3.2+dfsg-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on a
Package: nanopolish
Version: 0.11.0-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any
Looks like this common issue is in fact #921272.
(i.e. the currently-packaged tabu broke with recent TeX Live)
James
Control: forcemerge 919855 919857
On Sun, Jan 20, 2019 at 02:22:38PM +, Thorsten Glaser wrote:
> Ben Hutchings dixit:
>
> >the new Debian version crashes on s390x. It looks like this is due to
> >an address collision between the build ID in the shared library and
> >the code in the executable
Control: forcemerge 916062 -1
> On 15 Jan 2019, at 14:05, Ritesh Raj Sarraf wrote:
>
> Source: cowdancer
> Version: 0.87
This was already reported as the bug mentioned above and fixed in the 0.88
upload a week ago. Also please don't forward raw multi-part MIME messages; you
end up with the horr
Control: tag -1 pending
Hello,
Bug #916004 in makefs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/bsd-team/makefs/commit/563dfab97012c40a82f1d28607d097e3526b
Control: tag -1 pending
Hello,
Bug #916062 in cowdancer reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pbuilder-team/cowdancer/commit/92044b3f09b5085e99ee7361d
Package: libmariadb3
Version: 1:3.0.3-2
Severity: serious
Hi,
Trying to install libmariadb3 on a system which already has libmariadb2
installed fails with:
> Unpacking libmariadb3:amd64 (1:3.0.3-2) ...
> dpkg: error processing archive
> /var/cache/apt/archives/libmariadb3_1%3a3.0.3-2_amd64.deb (
On 25 Apr 2018, at 17:16, Mike Gabriel wrote:
>
> Control: reopen -1
>
> Hi James, hi Adrian, hi Niels,
> (also Cc:ed: Mihai Moldovan, upstream nx-libs)
>
> On Do 12 Apr 2018 13:02:45 CEST, James Clarke wrote:
>
>> Source: nx-libs
>> Version: 3.5.99
On Sun, Jan 14, 2018 at 11:20:49PM +0200, Adrian Bunk wrote:
> Source: libgc
> Version: 1:7.4.2-8.1
> Severity: serious
>
> https://buildd.debian.org/status/fetch.php?pkg=libgc&arch=armel&ver=1%3A7.4.2-8.1&stamp=1515764936&raw=0
>
> ...
>dh_makeshlibs -a
> dh_makeshlibs: Compatibility levels be
Source: nx-libs
Version: 3.5.99.16-1
Severity: serious
Hi,
Currently, nx-libs FTBFS (likely only probabilistically) when built with
parallel > 1; this occurred on the ia64 buildd lenz[1], but I have
reproduced it locally in an amd64 cowbuilder chroot.
Please either fix the Makefile dependency iss
Package: sbuild
Version: 0.74.0-1
Severity: serious
Hi,
Now that lintian defaults to enabled in 0.74.0-1, sbuild by default will
need lintian installed, but it has no dependency on it, and thus fails
with:
> Error reading configuration: LINTIAN binary 'lintian' does not exist or is
> not executa
Package: sbuild
Version: 0.74.0-1
Severity: serious
[Feel free to downgrade severity, but from my PoV this needs addressing before
Buster is released]
Hi,
In the latest upload, #870263 was fixed (which I support, for what it's worth;
any+all builds is the right default for users), meaning that bu
On Thu, Mar 01, 2018 at 05:00:28PM +0100, John Paul Adrian Glaubitz wrote:
> The of_path_of_nvme function (commit 2391d57, ieee1275: add nvme
> support within ofpath) introduced a functional regression:
>
> On systems which are not based on Open Firmware but have at
> least one NVME device, find_ob
On Tue, Jan 31, 2017 at 09:32:23AM +, Matthias Klose wrote:
> Package: src:jackd2
> Version: 1.9.10+20150825git1ed50c92~dfsg-4
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-7
>
> Please keep this issue open in the bug tracker for the package it
On 8 Feb 2018, at 19:46, Holger Levsen wrote:
>
> On Thu, Feb 08, 2018 at 03:04:22PM +0100, Petter Reinholdtsen wrote:
>> [Clint Adams]
>>> objdump -p /usr/lib/ghc/bin/ghc-pkg | grep RUNPATH
>
> $ objdump -p /usr/lib/ghc/bin/ghc-pkg | grep RUNPATH
> RUNPATH
>
> $ORIGIN/../terminfo-0.4.0.2:$
Control: tags -1 moreinfo
On Wed, Feb 07, 2018 at 05:02:09PM +0100, Holger Levsen wrote:
> Package: ghc
> Version: 8.0.2-11
> Severity: serious
>
> Selecting previously unselected package ghc.
> Preparing to unpack .../ghc_8.0.2-11_amd64.deb ...
> Unpacking ghc (8.0.2-11) ...
> Setting up libbsd-d
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=792845
Control: tag -1 upstream patch
On Mon, Oct 30, 2017 at 09:09:12PM +0100, Lucas Nussbaum wrote:
> Source: libgudev
> Version: 232-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-
Source: e2fsprogs
Version: 1.43.8-1
Severity: serious
Tags: upstream patch
Hi,
The latest upload of e2fsprogs FTBFS on all big-endian architectures due
to two problems in swapfs.c:
> ../../../../lib/ext2fs/swapfs.c: In function 'ext2fs_swap_super':
> ../../../../lib/ext2fs/swapfs.c:132:2: warning
Package: xul-ext-quotecolors
Version: 0.3-4
Severity: serious
Hi,
Icedove has been re-rebranded to Thunderbird, but xul-ext-quotecolors
depends on icedove | iceape. Please fix this to depend on thunderbird
(perhaps | icedove) so the extension can be installed again.
Regards,
James
On Fri, Dec 08, 2017 at 09:49:05AM +0100, Andreas Tille wrote:
> Hi Flavien,
>
> I have put the porter lists of the affected architectures in CC whether
> there is somebody who has a hint for a better solution than removing
> these architectures from the supported architectures. This kind of
> "ra
On Tue, Oct 17, 2017 at 06:03:20PM +0300, Adrian Bunk wrote:
> Package: dpkg-dev
> Version: 1.19.0.1
> Severity: serious
>
> 14:39 < _rene_> hmm. dpkg-dev 1.19.0.1 broken for anyone else? looks like it
> doesn't call build(-arch,indep) anymore at
> dpkg-buildpackage -b, but just bi
Control: tags -1 patch
On Tue, Sep 26, 2017 at 02:07:07PM +0300, Adrian Bunk wrote:
> Source: haskell-cryptonite
> Version: 0.23-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=haskell-cryptonite&suite=sid
>
> ...
> [119 of 119] Compiling Crypto.Cipher.AES ( Crypto/Cipher/
Package: ax25-tools
Version: 0.0.10-rc4-1
Severity: serious
Tags: upstream patch
Hi,
As discussed on IRC, various tools in ax25-tools segfault when run. For
example:
> $ /usr/sbin/kissnetd -p 5
> kissnetd V 1.5 by Frederic RIBLE F1OAT - ATEPRA FPAC/Linux Project
> [1]22672 segmentation fault
On 4 Oct 2017, at 14:43, Anton Gladky wrote:
> 2017-10-04 15:13 GMT+02:00 Andreas Tille :
>> Hi,
>>
>> to deal with #877419 I'd suggest the following approach:
>>
>> 1. Ignore test suite errors on those architectures that are
>> known to fail (see attached patch, NOT TESTED, please review
Source: haskell-text-show
Version: 3.4.1.1-1
Severity: serious
Hi,
haskell-text-show now FTBFS in unstable[0] due to overlapping instances;
the relevant part of the build log is given below:
> tests/Spec/Data/List/NonEmptySpec.hs:27:32: error:
> * Overlapping instances for Data.Functor.Classe
Source: haskell-vector
Version: 0.11.0.0-8
Severity: serious
Hi,
haskell-vector now FTBFS in unstable[0]; the relevant tail of the log is
given below:
> Data/Vector.hs:223:14: error:
> Ambiguous occurrence `fromList'
> It could refer to either `Exts.fromList',
>
>>> Control: affects 873508 horst
>>>>
>>>> On 2017-08-28 15:22:20, James Clarke wrote:
>>>>> As discussed on IRC, ppc64 and sparc64 are also affected; while they are
>>>>> not release architectures and are thus less important, it would
On 28 Aug 2017, at 20:10, Antoine Beaupré wrote:
> On 2017-08-28 20:53:02, Uwe Kleine-König wrote:
>> Hello,
>>
>> On 08/28/2017 04:32 PM, Antoine Beaupré wrote:
>>> Control: severity 873508 serious
>>> Control: affects 873508 horst
>>>
>>
Source: zimlib
Version: 2.0.0-1
Severity: serious
Hi,
Once again zimlib FTBFS due to symbols file diffs. Please at least *try*
to get a working symbols file; you can at least build amd64 locally, and
we have porterboxen for a reason...
James
On 5 Aug 2017, at 01:04, Andreas Tille wrote:
> On Sat, Aug 05, 2017 at 12:09:30AM +0100, James Clarke wrote:
>> Source: mptp
>> Version: 0.2.2-1
>> Severity: serious
>>
>> Hi,
>> mptp FTBFS when built with sufficient levels of parallelism (15 is
>> e
Source: mptp
Version: 0.2.2-1
Severity: serious
Hi,
mptp FTBFS when built with sufficient levels of parallelism (15 is
enough); the relevant tail of the log is given below:
> gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I. -O3
> -mtune=native -Wall -Wsign-compare -g -lgsl -lgs
Source: haskell-yesod-bin
Version: 1.5.2.3-1
Severity: serious
Hi,
The latest upload of haskell-yesod-bin FTBFS everywhere:
> dh_install -pyesod dist-ghc/build/yesod-ghc-wrapper/yesod-ghc-wrapper usr/bin
> dh_install: Cannot find (any matches for)
> "dist-ghc/build/yesod-ghc-wrapper/yesod-ghc-wr
Source: haskell-yaml
Version: 0.8.23-2
Severity: serious
Hi,
haskell-yaml FTBFS on every architecture (except all) due to testsuite
failures:
> Failures:
>
> test/Data/YamlSpec.hs:440:
> 1) Data.Yaml.Data.Yaml encode invalid numbers
>expected: ".\n"
> but got: ".\n...\n"
>
>
Source: haskell-http-link-header
Version: 1.0.3-1
Severity: serious
Hi,
haskell-http-link-header FTBFS on every architecture (other than all):
> Network.HTTP.Link
> writeLinkHeader tests: : commitBuffer: invalid argument (invalid
> character)
> Test suite tests: FAIL
Regards,
James
Source: haskell-websockets
Version: 0.9.8.2-1
Severity: serious
Hi,
It seems the B-D on libghc-sha-dev got dropped when importing the new
upstream version; it's still needed:
> hlibrary.setup: Encountered missing dependencies:
> SHA >=1.5 && <1.7
> /usr/share/cdbs/1/class/hlibrary.mk:142: recipe
63493):
+- [VarDumper] Relax tests to adapt for php 7.1rc4
+- [VarDumper] Relax line number for CliDumperTest
+
+ -- James Clarke Sat, 27 May 2017 20:39:09 +0100
+
symfony (2.8.7+dfsg-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru symfony-2.8.7+dfsg/debian/patches/series sy
Source: symfony
Version: 2.8.7+dfsg-1.2
Severity: serious
Tags: patch upstream fixed-upstream
Hi,
I noticed that symfony now FTBFS after the upload of php7.0 7.0.18-1,
with the following error in the test suite:
> 1) Symfony\Component\VarDumper\Tests\CliDumperTest::testThrowingCaster
> Failed ass
Source: linux
Version: 4.9.25-1
Severity: serious
Tags: jessie-ignore stretch-ignore
[{jessie,stretch}-ignore pre-approval from jcristau]
Hi,
Invoking debian/rules manually without the help of dpkg-buildpackage
causes src:linux to FTBFS:
> dh_strip: -strip --strip-debug --remove-section=.comment
> On 20 Apr 2017, at 14:52, James Clarke wrote:
> I have checked the build (no symbol diff, even warnings) on amd64 and
> i386. I will continue to test other architectures and update this bug
> later today.
Attached is an updated patch.
I have done porterbox test builds for t
://launchpadlibrarian.net/315416100/zimlib_1.4-2_1.4-2ubuntu1.diff.gz
>From 0ebfab1dd29efa1c1a35b7eada65290880a747d6 Mon Sep 17 00:00:00 2001
From: James Clarke
Date: Thu, 20 Apr 2017 14:34:07 +0100
Subject: [PATCH] Clean up symbols file
Closes: #860625
---
d
Source: ruby-unf-ext
Version: 0.0.7.2-2
Severity: serious
Hi,
While investigating #859463 with Niels, we noticed that the file in
question, ext/unf_ext/unf/table.hh, is pre-generated, but the original
sources[1] (and script used to process the sources[2]) are not present
in main.
Regards,
James
stems.
+ * Use correct integer type for Fortran prototypes and variables
+(Closes: #857067)
+
+ -- James Clarke Tue, 28 Mar 2017 18:22:35 +0100
+
dsdp (5.8-9.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru dsdp-5.8/debian/patches/type-mismatch.patch dsdp-5.8/debian/patches
Control: reopen 857067
Control: tags 857067 - patch
On Tue, Mar 28, 2017 at 04:39:07PM +, Debian Bug Tracking System wrote:
> Changes:
> dsdp (5.8-9.3) unstable; urgency=medium
> .
>* Non-maintainer upload.
>* Initialize all INFO vars. Closes: #857067
This is not the right fix at al
28 17:46:46.0 +0100
@@ -1,3 +1,11 @@
+dsdp (5.8-9.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use correct integer type for Fortran prototypes and variables
+(Closes: #857067)
+
+ -- James Clarke Tue, 28 Mar 2017 17:46:46 +0100
+
dsdp (5.8-9.2) unstable; urgency=m
Control: reassign -1 release.debian.org
Control: user release.debian@packages.debian.org
Control: usertags -1 binnmu
Control: severity -1 normal
Control: retitle -1 nmu: mariadb-10.1_10.1.21-5
On 14 Feb 2017, at 22:00, Otto Kekäläinen wrote:
>> 2017-02-14 23:58 GMT+02:00 James
> On 14 Feb 2017, at 21:54, Otto Kekäläinen wrote:
>
> So you suggest I upload 10.1.21-6 and go though all the hassle of
> filing unblocks etc? Is there no possibility to trigger a rebuild on
> amd64 with the current source package?
I don't know which is preferred, just that both solve the probl
Source: mariadb-10.1
Version: 10.1.21-5
Severity: serious
As can be seen in the discussion for #852709, the source+amd64 upload
for 10.1.21-5 did not include mariadb-plugin-tokudb, despite the
package's architecture being base-any-any-amd64. Either a binNMU or a
new source upload is needed (a test
Package: apt
Version: 1.4~rc1
Severity: serious
It seems invoking apt build-dep on a dsc doesn't always work:
> jrtc27@deb4g:~$ sudo apt build-dep
> ~/src/debian-installer/debian-installer_201701XX.dsc
> Note, using file
> '/home/jrtc27/src/debian-installer/debian-installer_201701XX.dsc' to get
Source: kodi
Version: 2:17.0~rc3+dfsg1-2
Severity: serious
In a freshly-unpacked source directory, dpkg-buildpackage (or pdebuild,
or sbuild) blocks in the clean target trying to reverse some patches,
because they were never applied (they get applied during configure) and
patch prompts the user fo
On 31 Jan 2017, at 17:09, James Clarke wrote:
> On 31 Jan 2017, at 14:56, James Clarke wrote:
>> However, given that I did not notice the "--build .dsc-file" bit when I first
>> re-read it, I have changed my mind and will allow the old style to work. This
>> *w
On 31 Jan 2017, at 14:56, James Clarke wrote:
> However, given that I did not notice the "--build .dsc-file" bit when I first
> re-read it, I have changed my mind and will allow the old style to work. This
> *will* give a deprecation warning though, and I intend to remove it
generated automatically based on the git commit message)
---
commit 86493b05640cc2dd1dde303f69805b293ae5b432
Author: James Clarke
Date: Tue Jan 31 16:50:48 2017 +
parameter.c: Allow commands to come later, but give deprecation warning
Closes: #852434
Control: tags -1 - wontfix
Control: severity -1 serious
On 31 Jan 2017, at 12:41, Thorsten Glaser wrote:
>
> James Clarke dixit:
>
>> Your mail server rejected my message (again). My guess is you didn't get the
>> message from the mailing list because it saw it wa
g-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport additional upstream patches needed to fix FTBFS:
+- Update IpValidatorTest data set with a valid reserved IP
+- Relax 1 test failing with latest PHP versions
+
+ -- James Clarke Sun, 29 Jan 2017 16:05:28 +
+
sy
On 29 Jan 2017, at 15:24, Otto Kekäläinen wrote:
> 2017-01-29 17:12 GMT+02:00 James Clarke :
>> Yeah, I'm not sure what's wrong with your setup. I would suggest checking the
>> version of dpkg-dev inside your chroot, since that should be the only thing
>> determini
On 29 Jan 2017, at 09:27, Otto Kekäläinen wrote:
> Hello!
>
> 2017-01-28 3:32 GMT+02:00 James Clarke :
>> Are you using a very old chroot? You need dpkg-dev (>= 1.18.11) to support
>> quadruplets in the Architecture field, though that was uploaded on the 6th
>>
pload.
+ * Fix PHP 7.0/7.1 related failures (Closes: #832858)
+ * Do not depend on a fixed date in layout tests (fixes FTBFS in 2017 and
+beyond)
+
+ -- James Clarke Sun, 29 Jan 2017 13:54:28 +
+
symfony (2.8.7+dfsg-1) unstable; urgency=medium
[ Fabien Potencier ]
diff -Nru symfony-2.8.7
> On 27 Jan 2017, at 21:07, Otto Kekäläinen wrote:
>
> I've now built and uploaded 10.1.21-5.
>
> Post upload I diffed the filelists (public at
> http://labs.seravo.fi/~otto/debian/mariadb-10.1-sid-amd64/?C=M;O=D)
> and I noticed my amd64 sid pbuilder is not generating
> mariadb-plugin-tokudb an
Patch actually attached this time...
Regards,
James
>From 47cc704d11d8991818fb7bf5ebff63c5a727da01 Mon Sep 17 00:00:00 2001
From: James Clarke
Date: Thu, 26 Jan 2017 21:46:28 +
Subject: [PATCH] Allow mariadb-plugin-tokudb/mroonga on non-linux and
non-release arches
---
debian/control
On Thu, Jan 26, 2017 at 09:42:01PM +, James Clarke wrote:
> On Thu, 26 Jan 2017 22:07:51 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
> wrote:
> > Great work Dieter!
> >
> > I'll merge and upload immediately. I just hope this will be in time
> > befor
On Thu, 26 Jan 2017 22:07:51 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> Great work Dieter!
>
> I'll merge and upload immediately. I just hope this will be in time
> before the Feb 5th freeze... Because the unstable->testing counter
> resets on every upload, all old fixes are still pendi
Source: mariadb-10.1
Version: 10.1.21-2
Severity: serious
During the build, mariadb-plugin-tokudb and mariadb-plugin-mroonga get
removed from debian/control if their binaries are not built. This is
relevant for release architectures - mariadb-plugin-tokudb only seems to
be built on amd64, and mari
Control: severity -1 wishlist
Control: tags -1 wontfix
Control: retitle -1 cowbuilder: No longer accepts command later in arguments
list
> On 24 Jan 2017, at 12:07, Thorsten Glaser wrote:
>
> Package: cowbuilder
> Version: 0.84
> Severity: grave
> Justification: renders package unusable
>
> tg
On Mon, Nov 07, 2016 at 12:51:52PM +, Riku Voipio wrote:
> On Sun, Nov 06, 2016 at 03:59:12PM +, James Cowgill wrote:
> > On Thu, 3 Nov 2016 13:15:47 +0300 Michael Tokarev wrote:
> > > 03.11.2016 12:46, Toby Speight wrote:
> > > > I was able to work around this issue by hand-editing the po
generated automatically based on the git commit message)
---
commit d36c9110a6993b4845649a3aa992961b1a6b4426
Author: James Clarke
Date: Fri Jan 6 19:02:11 2017 +
Symlink multiarch path to non-multiarch path
This is not ideal, since some users may already have updated their
Package: cowdancer
Version: 0.82
Severity: serious
Running cowbuilder --update gives a load of the following errors:
> ERROR: ld.so: object '/usr/lib/cowdancer/libcowdancer.so' from LD_PRELOAD
> cannot be preloaded (cannot open shared object file): ignored.
The entire update process runs under
On Sat, Dec 24, 2016 at 08:32:26AM +0100, Petter Reinholdtsen wrote:
> [Adrian Bunk]
> > https://buildd.debian.org/status/fetch.php?pkg=gdk-pixbuf&arch=mips64el&ver=2.36.2-1&stamp=1482373676
> [...]
> > ERROR: pixbuf-randomly-modified
>
> I tried reproducing this on eller.debia.org, but when I buil
Control: retitle -1 python-passlib: FTBFS with probability of 0.46% due to
non-deterministic testsuite
On Sun, Nov 13, 2016 at 04:25:30PM +, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0], we noticed
> that python-passlib's testsuite will non-determinstically FTBFS:
it's not exactly easy
to test properly...
Regards,
James
>From 8984ec2d25b0d0c73423350cc29139cd71237926 Mon Sep 17 00:00:00 2001
From: James Clarke
Date: Sat, 12 Nov 2016 22:29:25 +
Subject: [PATCH] Handle .xz, .bz2 and uncompressed Sources and Packages files
---
scanlib.pm | 39
Hi Lisandro,
On Fri, Jan 22, 2016 at 01:42:25PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Just for the sake of completeness, we are trying to remove this package from
> the archive. We still have quite a lot of packages to fix, but we hope to get
> this done before Stretch's release.
Th
41124)
+
+ -- James Clarke Tue, 18 Oct 2016 08:13:34 +0100
+
elfutils (0.166-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru elfutils-0.166/debian/patches/series
elfutils-0.166/debian/patches/series
--- elfutils-0.166/debian/patches/series2016-07-23 17:46:11.
Control: tags -1 patch fixed-upstream
On Mon, Oct 17, 2016 at 08:40:21PM +0100, James Clarke wrote:
> Source: elfutils
> Version: 0.166-2.1
> Severity: serious
>
> Hi,
> My NMU (#832584) FTBFS on amd64[1]. However, the only changes were
> adding Build-Depends on sparc64, and
Source: elfutils
Version: 0.166-2.1
Severity: serious
Hi,
My NMU (#832584) FTBFS on amd64[1]. However, the only changes were
adding Build-Depends on sparc64, and 0.166-2 itself FTBFS in a clean
amd64 chroot (log attached), so it seems the more recent dependencies
are problematic.
Important part o
Control: found -1 0.224
Control: severity -1 important
Hi Thorsten,
> On 8 Oct 2016, at 21:20, Thorsten Glaser wrote:
>
> Package: pbuilder
> Version: 0.226.1
> Severity: serious
> Justification: breaks basic use
>
> The remove_packages function in pbuilder-modules contains:
>
>if (dpk
generated automatically based on the git commit message)
---
commit 8d69336a654a37f03d2f72351d92a2a4934cdc66
Author: James Clarke
Date: Tue Jul 19 22:26:06 2016 +0100
pbuilder-modules: Don't trash CHROOTEXEC when using eatmydata
Closes: #831823
Control: reassign -1 pbuilder 0.225
Control: affects -1 cowbuilder cowdancer
Hi Emilio,
> On 19 Jul 2016, at 21:31, Emilio Pozuelo Monfort wrote:
>
> Package: cowbuilder
> Version: 0.80
> Severity: grave
> Tags: security
Agreed.
> I enabled eatmydata by adding EATMYDATA=eatmydata to my ~/.pbui
Control: affects -1 - src:qemu
On Thu, 19 May 2016 18:07:27 +0300 Michael Tokarev wrote:
> Control: affects -1 - qemu
> Control:
That should have been src:qemu; fixed above :)
Regards,
James
signature.asc
Description: Message signed with OpenPGP using GPGMail
Control: severity -1 important
On Fri, May 13, 2016 at 03:25:44PM +0200, Michael Prokop wrote:
> * Peter Pentchev [Thu Apr 28, 2016 at 01:28:54PM +0300]:
> > Package: qemubuilder
> > Version: 0.79
> > Severity: grave
> > Tags: patch
>
> What's the rational for marking this as grave?
>
> (Asking be
Package: src:firebird3.0
Version: 3.0.0.32483.ds4-1
Severity: serious
Tags: upstream patch
Justification: Policy 4.2
Control: forwarded -1 https://github.com/FirebirdSQL/firebird/pull/21
As can be seen from
https://buildd.debian.org/status/package.php?p=firebird3.0&suite=experimental,
this packag
Control: tag 822849 pending
Hello,
Bug #822849 in cowdancer reported by you has been fixed in the Git repository.
You can
see the commit message below, and you can check the diff of the fix at:
https://anonscm.debian.org/git/pbuilder/cowdancer.git/commit/?id=464f508
(this message was gener
Control: tags -1 confirmed
Hi,
> On 28 Apr 2016, at 11:28, Peter Pentchev wrote:
>
> Package: qemubuilder
> Version: 0.79
> Severity: grave
> Tags: patch
>
> Hi,
>
> Thanks for writing and maintaining cowdancer, cowbuilder, and qemubuilder!
I didn’t write it originally, I just maintain it :)
Control: reassign -1 xfsprogs
Control: forcemerge 822369 -1
Control: affects -1 src:qemu
(hopefully I got it right this time…)
> On 27 Apr 2016, at 00:05, James Clarke wrote:
>
> Control: package xfsprogs
> Control: forcemerge 822369 -1
> Control: affects -1 src:qemu
>
>
Control: package xfsprogs
Control: forcemerge 822369 -1
Control: affects -1 src:qemu
On Wed, 27 Apr 2016 00:02:56 +0200 John Paul Adrian Glaubitz
wrote:
>> This smells like a bug in the build environment, not in qemu.
>> There must be ability to include both headers without failing
>> to build.
I have also run into this, but I found that upgrading libgjs0e to 1.45.3-1 from
experimental resolves it.
Regards,
James
signature.asc
Description: Message signed with OpenPGP using GPGMail
tags 704303 patch
thanks
Hi,
Please find attached a patch to include the full text for the MPL-1.1 and
MPL-2.0 licenses inside debian/copyright.
Regards,
James
debian-copyright.diff
Description: Binary data
94 matches
Mail list logo
