Bug#1071272: linux: building the bookworm-backports armhf kernel causes OOM on buildds

Source: linux Version: 6.7.12-1~bpo12+1 Severity: serious X-Debbugs-CC: debian-...@lists.debian.org X-Debbugs-CC: d...@debian.org Hi, armhf builds of the bookworm-backports kernel appear to have led to outages on several buildds recently. Each of arm-ubc-04, arm-ubc-05 and arm-ubc-06 (QEMU

Bug#1031888: emacs-nox: bullseye-security update fails to install on mips64el

On Thu, 2024-05-16 at 17:01 +0100, Sean Whitton wrote: > control: reopen 1031888 > > Hello Adam, > > On Fri 21 Apr 2023 at 10:19am +01, Adam D. Barratt wrote: > [...] > > With my DSA hat on, I'm not aware of it having been confirmed to > > fix > > the

Bug#1067016: nvidia-settings 470.239.06-1 flagged for acceptance

package release.debian.org tags 1067016 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-settings Version:

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

On Sun, 2023-11-05 at 21:46 +0100, Markus Koschany wrote: > Am Sonntag, dem 05.11.2023 um 20:35 + schrieb Adam D. Barratt: > > [...] > > After a bit of searching, I happened across a discussion of a > > similar > > change in a different product that mentioned the &

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

On Sun, 2023-11-05 at 19:18 +0100, Markus Koschany wrote: > Am Sonntag, dem 05.11.2023 um 16:33 + schrieb Adam D. Barratt: > > [...] > > Do you have an idea how simple rebuilding the bullseye package on > > buster would be? I'm happy to try that in general, but I've not

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

On Sat, 2023-11-04 at 20:33 +0100, Markus Koschany wrote: > Could you install the version of trapperkeeper-webserver-jetty9- > clojure from Bullseye and reinstall the jetty9 security update and > report back if this solves your problem? Doing that directly doesn't "just work":

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

Source: jetty9 Version: 9.4.50-4+deb10u1 Severity: serious X-Debbugs-Cc: d...@debian.org Hi, Upgrading libjetty9-java and libjetty9-extra-java to the version from DLA 3641-1 reliably causes PuppetDB to fail to start, with the stacktrace shown below. Downgrading resolves the issue. I'm not sure

Bug#1052129: acpica-unix: Failed to migrate to Testing; missing s390x build not properly handled

On Sun, 2023-09-17 at 14:58 -0400, Boyuan Yang wrote: > If you are clear that upstream is completely not supporting big- > endian build anymore, please > submit a package removal request to Debian Release Team (using > reportbug tool) to remove > the current s390x package in Debian Testing. No.

Bug#1039743: christianriesen-base32: FTBFS with phpunit 10: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2

On Wed, 2023-06-28 at 17:57 -0300, Athos Ribeiro wrote: > Source: christianriesen-base32 > Version: 1.6.0-3 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: pkg-php-p...@lists.alioth.debian.org > Usertags: phpunit > > Hi, > > We will start the phpunit 10 transition in

Bug#1031888: emacs-nox: bullseye-security update fails to install on mips64el

On Fri, 2023-04-21 at 12:08 +0300, Adrian Bunk wrote: > On Tue, Mar 14, 2023 at 02:04:19PM -0700, Sean Whitton wrote: > > Version: 1:28.2+1-11 > > > > Hello, > > > > On Sun 26 Feb 2023 at 09:41PM +02, Adrian Bunk wrote: > > > > > While I suspect they are the same, there is no proof that this >

Bug#1031888: emacs-nox: bullseye-security update fails to install on mips64el

Source: emacs Version: 1:27.1+1-3.1+deb11u2 Severity: grave Control: affects -1 + security.debian.org Control: affects -1 + release.debian.org X-Debbugs-Cc: t...@security.debian.org X-Debbugs-Cc: debian-ad...@lists.debian.org Hi, Upgrading emacs-nox on a bullseye mips64el system to the latest

Bug#1030160: chromium: FTBFS on arm64/armhf in bullseye-security (V4L issues)

Source: chromium Version: 109.0.5414.119-1~deb11u1 Severity: serious Tags: FTBFS X-Debbugs-CC: t...@security.debian.org Control: affects -1 + security.debian.org Control: affects -1 + release.debian.org Hi, The most recent chromium upload to bullseye-security fails to build on arm64 and armhf

Bug#1029215: debian-archive-keyring: bookworm SRM key

Source: debian-archive-keyring Version: 2021.1.1 Severity: serious X-Debbugs-Cc: debian-rele...@lists.debian.org Hi, We need an SRM key for bookworm, so that we can include it in the release. Regards, Adam

Bug#1029214: debian-archive-keyring: bookworm archive signing keys

Source: debian-archive-keyring Version: 2021.1.1 Severity: serious X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org Hi, We need new archive signing keys for bookworm, so that we can include them in the release. Regards, Adam

Bug#1027925: spamassassin FTBFS on IPV6-only buildds

On Wed, 2023-01-04 at 18:31 +, Adam D. Barratt wrote: > One difference at least is that "IPv6-only" buildds *do* have IPv4 > networking, but only on lo. As a result, your have_inet4 test will > return true: > > adsb@x86-conova-01:~$ ip --brief -4 a > lo

Bug#1027925: spamassassin FTBFS on IPV6-only buildds

On Wed, 2023-01-04 at 10:01 -0800, Noah Meyerhans wrote: > On Wed, Jan 04, 2023 at 06:58:30PM +0200, Adrian Bunk wrote: > > https://buildd.debian.org/status/logs.php?pkg=spamassassin=amd64 > > > > ... > > Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all > > Jan 4 03:57:23.255

Bug#1024400: net-luminis-build-plugin: broken maintainer field

Source: net-luminis-build-plugin Version: 0.2.0-4 Severity: serious X-Debbugs-Cc: ta...@debian.org Hi, The upload of net-luminis-build-plugin which orphaned it appears to have generated a broken Maintainer field: Package: net-luminis-build-plugin Binary: libnet-luminis-build-plugin-java

Bug#1023811: golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1 sources changed in the archive?

On Thu, 2022-11-10 at 15:53 +0200, Adrian Bunk wrote: > Get:1 https://deb.debian.org/debian experimental/main golang-github- > grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc) [2857 B] > Err:1 https://deb.debian.org/debian experimental/main golang-github- > grpc-ecosystem-go-grpc-middleware

Bug#1023424: Re; Bug#1023424: Vulnerabilities CVE-2022-1292, CVE-2022-2068, CVE-2022-2097

Control: severity -1 important Control: tags -1 - bullseye On Thu, 2022-11-03 at 20:35 +, nospam099-git...@yahoo.com wrote: > The component OpenSSL1.1.1n-0+deb11u3 suffers from 3 vulnerabilities: > * (CVE-2022-1292)[https://nvd.nist.gov/vuln/detail/CVE-2022-1292] > (critical) > *

Bug#1014556: firefox-esr: FTBFS on mipsel ("terminate called after throwing an instance of 'std::bad_alloc'")

Source: firefox-esr Version: 91.0esr-1 Severity: serious Tags: ftbfs Control: found -1 91.9.0esr-1~deb11u1 Hi, firefox-esr fails to build on mipsel for some time now. The exact module generating the issue seems to vary, but the general pattern is always: terminate called after throwing an

Bug#988086: Exim delivery process crashes on each mail with NULL-pointer

On Wed, 2021-05-05 at 11:07 +, halfdog wrote: > This is weird: I have only bullseye/bullseye-updates/bullseye- > security > in my sources list. I applied all updates on 2nd of May with > no Exim package available. Then after the 21nails disclosure > I run the updates (timestamps in UTC): > >

Bug#977910: debian-archive-keyring: bullseye SRM key

On Tue, 2020-12-22 at 18:40 +, Adam D. Barratt wrote: > We need an SRM key for bullseye, so that we can include it in the > release. > I've generated the key, just seeing if JMW wants to add a sig. Regards, Adam

Bug#982122: redis: experimental package OOMs s390x buildds

Hi Chris, On Mon, 2021-02-15 at 18:28 +, Chris Lamb wrote: > Ah, indeed, the failure mode means that the log never made it to > > buildd.d.o. > > Curious, not heard of that failure mode — is there someplace I can > learn about that? No worries if not. I'm not sure if it's documented, but in

Bug#982123: librsvg: FTBFS on ppc64el

Source: librsvg Version: 2.44.10-2.1+deb10u3 Severity: serious Tags: ftbfs Hi, The librsvg package in proposed-updates fails to build on ppc64el. >From the most recent attempt: ERROR: rsvg-test thread '' panicked at 'assertion failed: bounds.x1 >= bounds.x0',

Bug#982122: redis: experimental package OOMs s390x buildds

Source: redis Version: 5:6.2~rc3-1 Severity: serious Tags: ftbfs Hi, Both s390x buildds hit OOM conditions while attempting to build redis 6.2 in experimental. The log from zani ends with: [33/63 done]: integration/rdb (10 seconds) Testing integration/corrupt-dump [ok]: corrupt payload: #7445

Bug#975372: minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge

ess the > "fallout" from the logdir move and so adress #975372. > > Adam D. Barratt is Cc'ed in this message, who is a stable release > managers in case he would like to indicate a preference. > > Adam would that be fine with you with your SRM hat on, to let a

Bug#977911: debian-archive-keyring: bullseye archive signing key

Source: debian-archive-keyring Version: 2019.1 Severity: serious X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org Hi, We need a new archive signing key for bullseye, so that we can include it in the release. Regards, Adam

Bug#977910: debian-archive-keyring: bullseye SRM key

Source: debian-archive-keyring Version: 2019.1 Severity: serious X-Debbugs-Cc: debian-rele...@lists.debian.org Hi, We need an SRM key for bullseye, so that we can include it in the release. Regards, Adam

Bug#973660: thunderbird: FTBFS on s390x in buster

Package: src:thunderbird Version: 78.3.1-2~deb10u1 Severity: serious Tags: ftbfs Control: affects -1 release.debian.org security.debian.org X-Debbugs-Cc: t...@security.debian.org Hi, Since 78.3.1, thunderbird FTBFS on s390x in buster(-security). The relevant part of the logs appears to be:

Bug#968102: [Pkg-mozext-maintainers] Bug#968102: Bug#968102: new upstream release (2.16)

On Wed, 2020-10-07 at 11:11 +0200, Carsten Schoenert wrote: > Hello Mechtilde, > > Am 07.10.20 um 10:34 schrieb Mechtilde: > > Hello, > > > > I will do a update-proposal for buster ASAP. > > > > Do I still have to consider something to get it drectly into buster > > and > > not just with the

Bug#964291: stretch-pu: package mariadb-10.1 10.1.45-0+deb9u1

Control: severity -1 normal On Sun, 2020-07-05 at 09:59 +0300, Otto Kekäläinen wrote: > Package: release.debian.org > Severity: serious No. p-u bugs (and basically all release.d.o bugs) are (still) normal at most. Please don't inflate severity like that. It may be RC for your individual package,

Bug#932296: qa.debian.org: getwatch filling up /tmp

On Wed, 2020-06-17 at 00:14 +0200, Lucas Nussbaum wrote: > On 16/06/20 at 21:07 +0100, Adam D. Barratt wrote: > > On Tue, 2020-06-16 at 16:40 +0200, Julien Cristau wrote: > > > On Wed, Dec 18, 2019 at 02:03:13PM +0100, Julien Cristau wrote: > > > >

Bug#932296: qa.debian.org: getwatch filling up /tmp

On Tue, 2020-06-16 at 16:40 +0200, Julien Cristau wrote: > On Wed, Dec 18, 2019 at 02:03:13PM +0100, Julien Cristau wrote: > > Control: severity -1 serious > > > > On Thu, Aug 08, 2019 at 01:45:27PM +0200, Julien Cristau wrote: > > > On Wed, Jul 17, 2019 at 10:11:39PM +0200, Lucas Nussbaum wrote:

Bug#950309: stretch-pu: package mariadb-10.1 10.1.44-0+deb9u1

Control: tags -1 +confirmed -moreinfo Control: severity -1 normal On Fri, 2020-01-31 at 10:32 +0200, Otto Kekäläinen wrote: > Package: release.debian.org > Severity: serious Nope. > Tags: stretch, moreinfo Filing the request with "moreinfo" is an interesting choice. :-) > User:

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

On Thu, 2019-11-07 at 10:49 -0800, Felix Lechner wrote: > Also, as a side note, would someone please explain why someone still > on stretch would need lintian? I am personally on stable, but most > package maintainers out there seem to track testing or the bleeding > edge, unstable. Well, at

Bug#940521: buster-pu: package mariadb-10.3 10.3.18-0+deb10u1

Control: severity -1 normal Control: tags -1 -moreinfo +confirmed [For reference, X-Debbugs-Cc is generally better than your mail client's CC when submitting bugs, as it means the recipient gets the mail from the BTS with the bug number included] On 2019-09-16 20:08, Otto Kekäläinen wrote:

Bug#939866: [debian-mysql] Bug#939866: Bug#939866: mariadb-server-10.1: replication hangs in state "Slave_IO_Running: Preparing" after upgrade from 10.1.38 to 10.1.41

On Fri, 2019-09-13 at 21:10 +0300, Otto Kekäläinen wrote: > To clarify, 10.3.18 has been uploaded to Debian unstable. Issue is > still open for Buster and Stretch. Is there a likely ETA for when this might be resolvable? If you could prepare (preferably targeted) updates via the usual p-u path

Bug#933002: docker.io: CVE-2019-13139

On Sun, 2019-08-18 at 16:22 +0100, Adam D. Barratt wrote: > On Sun, 2019-08-18 at 16:56 +0200, Arnaud Rebillout wrote: > > * The bug you want to fix in stable must be fixed in unstable > > already (and not waiting in NEW or the delayed queue) > > > > My iss

Bug#933002: docker.io: CVE-2019-13139

On Sun, 2019-08-18 at 16:56 +0200, Arnaud Rebillout wrote: > * The bug you want to fix in stable must be fixed in unstable >   already (and not waiting in NEW or the delayed queue) > > My issue with this particular bug (#933002) is that for now, > docker.io  doesn't build in unstable. It

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

Control: tags 919043 + confirmed On Sun, 2019-04-14 at 12:26 +0200, Sebastian Andrzej Siewior wrote: > On 2019-04-13 22:25:19 [+0100], Adam D. Barratt wrote: > > On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote: > > > I'm proposing this attached debdiff. &

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote: > On 2019-02-02 14:46:54 [+0100], Andreas Beckmann wrote: > > I'm not going to touch that package, please go ahead with preparing > > a > > NMU (or probably rather QA upload if it is gone from sid) to > > stretch, > > since you

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

On Tue, 2019-03-26 at 10:39 -0700, Vagrant Cascadian wrote: > On 2019-03-26, Adam D. Barratt wrote: > > On 2019-03-15 06:44, Adam D. Barratt wrote: > > > The updated images for armhf have been available in p-u for a > > > couple of > > > days now. > > >

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

On 2019-03-15 06:44, Adam D. Barratt wrote: The updated images for armhf have been available in p-u for a couple of days now. Feedback would be appreciated, as we would like to be able to accept the new kernel upload into p-u, which will block a further rebuild here as it brings an ABI bump

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

On Sun, 2019-03-10 at 09:51 -0700, Vagrant Cascadian wrote: > On 2019-03-10, Cyril Brulebois wrote: > > Vagrant Cascadian (2019-03-09): > > > > > Thanks for your report; that's known and fixed on the kernel > > > > > side > > > > > already; how to deal with d-i is discussed in: > > > > >  

Bug#875358: Powermock RC #875358

On Fri, 2019-03-01 at 23:34 +0100, Markus Koschany wrote: > I have removed powermock from all reverse-dependencies. This bug > should no longer be a blocker for Buster and powermock can be safely > removed from testing. You didn't, however, ask for unblocks for the reverse-dependencies. I've now

Bug#916520: devscripts: depends on gnupg | .., gnupg removed from unstable

On Sat, 2018-12-15 at 12:51 +, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sat, 2018-12-15 at 13:34 +0100, Bernd Zeimetz wrote: > > devscripts depends on gnupg | gnupg2. As buildds/sbuild/... only > > install the first altenative package, builds of a

Bug#916520: devscripts: depends on gnupg | .., gnupg removed from unstable

Control: tags -1 + moreinfo On Sat, 2018-12-15 at 13:34 +0100, Bernd Zeimetz wrote: > devscripts depends on gnupg | gnupg2. As buildds/sbuild/... only > install the first altenative package, builds of all packages > which depend on devscripts in a way are broken since gnupg was > removed from

Bug#913674: release.debian.org: Regression: Recent upgrade of opensc breaks Yubikey NEO support

Control: severity -1 normal On Tue, 2018-11-13 at 22:54 +0100, Hilko Bengen wrote: > Package: release.debian.org > Severity: grave RC bugs in psuedo-packages / teams generally don't make much sense. (On the whole, anything > normal against release.d.o is likely to be wrong.) > Tags: stretch >

Bug#905332: debdiff

On 2018-11-06 14:43, wf...@niif.hu wrote: Dear Security Team, please consider yourselves notified and please debian-secur...@lists.debian.org is *not* a contact point for the Security Team, it's a public discussion list. Regards, Adam

Bug#910543: bfs 1.2.4-1 fstype test fails on Hurd

Control: severity -1 important On Sun, 2018-10-07 at 21:28 +, Tavian Barnes wrote: > Package: bfs > Version: 1.2.4-1 > Severity: serious > Justification: fails to build from source (but built successfully in > the past) > > Dear Maintainer, > > bfs recently failed to build on Hurd: >

Bug#910009: exim4-config: upgrade fails when trying to execute conffile difference visualizer

Control: tags -1 + moreinfo unreproducible On 2018-10-01 10:19, Vincent Lefevre wrote: Package: exim4-config Version: 4.91-8 Severity: grave Justification: renders package unusable [...] *** exim4.conf.template (Y/I/N/O/D/Z) [default=N] ? D dpkg (subprocess): unable to execute conffile

Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade

On Thu, 2018-07-19 at 18:23 +0100, Adam D. Barratt wrote: > On Thu, 2018-07-19 at 18:42 +0200, Christoph Martin wrote: > > tags 860064 +stretch > > tags 860064 +jessie > > thanks > > > > Am 01.07.2018 um 15:38 schrieb Adam D. Barratt: > > > On Sun, 20

Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade

On Thu, 2018-07-19 at 18:42 +0200, Christoph Martin wrote: > tags 860064 +stretch > tags 860064 +jessie > thanks > > Am 01.07.2018 um 15:38 schrieb Adam D. Barratt: > > On Sun, 2018-07-01 at 11:38 +, Martin, Christoph wrote: > > > dns-root-data had an

Bug#903406: gridengine: FTBFS on armhf due to OpenJDK VM changes

On Mon, 2018-07-09 at 16:43 +0100, Adam D. Barratt wrote: > gridengine fails to build on armhf due to the VM-related changes in  > OpenJDK 8u144-b01-2, which mean that the lib/server directory no > longer exists on that architecture. > > I've build-tested the attached patch on abel

Bug#903406: gridengine: FTBFS on armhf due to OpenJDK VM changes

Source: gridengine Version: 8.1.9+dfsg-4 Severity: serious Tags: patch Control: block 903015 by -1 Hi, gridengine fails to build on armhf due to the VM-related changes in OpenJDK 8u144-b01-2, which mean that the lib/server directory no longer exists on that architecture. I've build-tested

Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade

On Sun, 2018-07-01 at 11:38 +, Martin, Christoph wrote: > dns-root-data had an update a week before. the file with the dns root > keys was updated. at least the format has changed. To re-iterate, no such change has happened recently in stretch. I understand that the update in jessie may have

Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade

On Mon, 2018-06-25 at 10:44 +0200, Christoph Martin wrote: > severity 860064 critical > On which grounds are you claiming this qualifies for critical severity? It doesn't introduce a security hole, cause severe data loss or break your whole system. I have difficulty with dnsmasq and

Bug#860064: #860064 dnsmasq will not start after dns-root-data upgrade

On Mon, 2018-06-25 at 10:44 +0200, Christoph Martin wrote: > severity 860064 critical > tags 860064 +jessie > thanks > > yesterday jessie and stretch upgraded the dns-root-data package, > which includes the new root DNSSEC keys with a time to live value > added. This is factually

Bug#901185: exim4-config: fails to install

Control: tags -1 + moreinfo On Sun, 2018-06-10 at 00:17 +0200, Eric Valette wrote: > Paramétrage de exim4-config (4.91-5) ... > /etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype > : commande introuvable > /etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype >

Bug#883071: [release.debian.org] need to recompile eclipse-titan (6.1.0-1) in stable

severity 883071 normal user release.debian@packages.debian.org usertags 883071 + nmu tags 883071 + stretch retitle 883071 nmu: eclipse-titan thanks On 2017-11-29 9:50, Pilisi Gergely wrote: Package: release.debian.org [1] Severity: grave No. The bug in your package might well be Release

Bug#879231: security update: ruby2.3

On Sat, 2017-11-04 at 22:08 +0100, Salvatore Bonaccorso wrote: > Hi Antonio > > Sorry for the late reply > > On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote: > > Hi security team, > > > > I have prepared a security update for ruby2.3. > > > > It includes all the pending recent

Bug#876768: Re: ruby-pygments.rb: fails to run if RLIMIT_NOFILE is very high

Control: block 877043 by -1 Hi, On Mon, 2017-09-25 at 17:44 +0100, James Cowgill wrote: > weechat recently FTBFS due to asciidoctor dying: > https://buildd.debian.org/status/fetch.php?pkg=weechat=mips64el; > ver=1.9.1-1=1506204287=0 > > This happens because: > - The RLIMIT_NOFILE hard limit is

Bug#864947: Re: parl-desktop-world depends on cruft package firefox-esr-l10n-be

On Sun, 2017-06-18 at 12:19 +0100, peter green wrote: > Tags 864947 +patch > Thanks > > > parl-desktop-world depends on firefox-esr-l10n-be which is no > > longer built by firefox-esr. I'm still trying to figure out where > > this is coming from, I can't find any evidence of it in the source > >

Bug#872525: [pkg-gnupg-maint] Bug#872525: debian-archive-keyring FTBFS with gnupg 2.1.23

On Fri, 2017-08-18 at 21:30 +0100, Adam D. Barratt wrote: > 1. Have the rules that generate the keyrings clean them afterwards. For > example, changing: > > keyrings/debian-archive-keyring.gpg: active-keys/index > jetring-build -I $@ active-keys > > to > &

Bug#872525: [pkg-gnupg-maint] Bug#872525: debian-archive-keyring FTBFS with gnupg 2.1.23

5 06:30:03 2017 -12 > > gpg: using RSA key C5CE5DC2C542CD59 > > gpg: BAD signature from "Adam D. Barratt <a...@adam-barratt.org.uk>" > > [unknown] [...] > The difference between the keyrings is the trust packets: [...] > This is happening because of a c

Bug#863101: Uscan uses all available memory of the system when run against guitarix

On Sun, 2017-05-21 at 23:09 +0200, Víctor Cuadrado Juan wrote: > On 21/05/17 22:05, Adam D. Barratt wrote: > > > > I've been unable to reproduce this using either jessie or sid's uscan > > (running on a jessie host, admittedly). I'd be interested if anyone e

Bug#863101: Uscan uses all available memory of the system when run against guitarix

Control: tags -1 + moreinfo unreproducible On Sun, 2017-05-21 at 21:06 +0200, Víctor Cuadrado Juan wrote: > When run against guitarix package git repo, at commit 7ff29bd, > for obtaining `guitarix2-0.35.3.tar.xz` that would become the > `guitarix_0.35.3.orig.tar.xz` symlink, `uscan --verbose`

Bug#859255: binNMU needed for more R packages.

severity 859255 normal user release.debian@packages.debian.org usertags 859255 binnmu thanks On Sat, 2017-04-01 at 15:24 +0900, Charles Plessy wrote: > Package: release.debian.org > Severity: grave > X-Debbugs-CC: debian-...@lists.debian.org, debian-scie...@lists.debian.org I fixed this last

Bug#855970: [debian-archive-keyring] The release repository of testing (Stretch), and security updates repository too, have three misiing public keys

Control: severity -1 normal Control: tags -1 -security +moreinfo On Thu, 2017-02-23 at 22:30 +0100, Łukasz Konieczny wrote: > Package: debian-archive-keyring > Version: 2014.3 > Severity: serious > Tags: security > X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org > > --- Please enter

Bug#734837: Why is tk8.4 removal triggering autoremoval messages of not depending packages at this point in time (Was: staden is marked for autoremoval from testing)

On Sat, 2016-12-31 at 15:38 +0100, Thibaut Paumard wrote: > I would believe removing tk8.4 by hand from testing could fix the lot of > associated autoremovals. > > Dear release team, thoughts on that? tk8.4 and tcl8.4 were already re-removed from testing this morning. Regards, Adam

Bug#847575: closed by Hilko Bengen <ben...@debian.org> (no embedded dietlibc)

On Tue, 2016-12-27 at 16:13 -0500, Theodore Ts'o wrote: > On Tue, Dec 27, 2016 at 07:56:36PM +0000, Adam D. Barratt wrote: > > Thankfully none of that worked. I say thankfully, because you'd have > > given release.d.o an allegedly RC bug (it may be RC for e2fsprogs, it's >

Bug#847575: closed by Hilko Bengen <ben...@debian.org> (no embedded dietlibc)

Control: clone -1 -2 Control: close -1 Control: reassign -2 release.debian.org Control: severity -2 normal Control: retitle -2 nmu: e2fsck-static Control: tags -2 + jessie pending On Tue, 2016-12-27 at 12:31 -0500, Theodore Ts'o wrote: > retitle -1 release.debian.org: binNMU for e2fsck-static to

Bug#840589: Questioning severity of the bug

On Sun, 2016-10-16 at 18:25 +0200, Ole Streicher wrote: > Hi Peter, > > could you explain why you think this is of severity "serious"? In my > opinion, FTBFS should be "important" as long as there is at least one > useful architecture. Your opinion is not consistent with RC bug policy. See

Bug#840355: Failed to create spool file /var/spool/exim4//input//...-D: Permission denied

On Tue, 2016-10-11 at 04:38 +0800, 積丹尼 Dan Jacobson wrote: > Can't send mail, because: > 2016-10-11 04:30:53 Failed to create spool file > /var/spool/exim4//input//1bthDp-0002gq-Fy-D: Permission denied That looks awfully similar to

Bug#833574: monotone: FTBFS on powerpc (test suite failure)

On Sat, 2016-10-08 at 00:29 +0300, Adrian Bunk wrote: > I would suggest to upload 1.1-4+deb8u2 (created on top of 1.1-4+deb8u1) > with 51-sigpipe-test.diff added to jessie, but Julien (or any other SRM) > should confirm that. Please open a p-u bug with the proposed fix (as a source debdiff)

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

Control: tags -1 +confirmed -patch +jessie Control: severity -1 normal On Sun, 2016-09-04 at 07:32 +0100, Christopher Hoskin wrote: > Package: release.debian.org > Severity: critical *No*. The bug you're fixing may be critical, the request to fix it in stable is at most normal. > Tags: patch >

Bug#826667: Bug#826714: jessie-pu: package biber/1.9-3+deb8u1

Control: tags 826714 + pending On Fri, 2016-06-10 at 19:04 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Fri, 2016-06-10 at 10:06 +0300, Niko Tyni wrote: [...] > > IMO updating biber in jessie to work around this (like it already does > > in sid/stretch

Bug#826667: Bug#826714: jessie-pu: package biber/1.9-3+deb8u1

Control: tags -1 + confirmed On Fri, 2016-06-10 at 10:06 +0300, Niko Tyni wrote: > I think the root cause is in libunicode-linebreak-perl, now filed as > #826932. Thanks for the information. > IMO updating biber in jessie to work around this (like it already does > in sid/stretch) is the safest

Bug#826563: stable-updates fix for Bug#826563: perl: Apparent regression in TryCatch

On Tue, 2016-06-07 at 00:46 +0100, Dominic Hargreaves wrote: > On Mon, Jun 06, 2016 at 08:54:23PM +0100, Dominic Hargreaves wrote: [...] > > In hindsight, it's obvious that Debian's testing of this update wasn't > > sufficient either. Such breaking changes in perl stable updates are, > > I

Bug#826334: dget: removes existing dir by default without asking

Control: reassign -1 dpkg-dev 1.17.27 Control: affects -1 devscripts Control: retitle -1 dpkg-source -x overwrites existing directories On Sat, 2016-06-04 at 18:08 +0200, ydir...@free.fr wrote: > dget unpacks the downloaded source by default, even if the target directory > was > pre-existing.

Bug#823274: login error

Control: forcemerge 823236 -1 On Tue, 2016-05-03 at 02:00 +0530, Hema .p wrote: > Package: sso.debian.org > Severity: grave > > Hi, > > I can't login to sso.debian.org using my Alioth account "hemaprathaban-guest". > > Error message: > Authentication failed > Invalid authenticating information

Bug#819958: totem: This file cannot be played over the network. Try downloading it locally first.

On 2016-04-07 10:03, Raphael Hertzog wrote: [...] ii gstreamer1.0-plugins-bad1.6.3-1+b2 ii gstreamer1.0-plugins-base 1.6.3-1 ii gstreamer1.0-plugins-good 1.6.3-1 1.6.3 plugins but ii libgstreamer1.0-0 1.8.0-1 1.8.0 library I solved the problem by

Bug#819586: debian-installer-netboot-images: unhelpful handling of GPG errors

Source: debian-installer-netboot-images Version: 20120712 Severity: serious Justification: silently ignores failures, creating broken packages Hi, Whilst preparing the dini uploads for the upcoming point releases, on debdiffing the binary packages against the previous versions I noticed that one

Bug#816205: tagging 816205

On Mon, 2016-03-28 at 14:39 +0200, Mathieu Parent (Debian) wrote: > 2016-03-26 18:35 GMT+01:00 Adam D. Barratt <a...@adam-barratt.org.uk>: > > On Sat, 2016-03-26 at 17:14 +0100, Mathieu Parent wrote: > >> tags 816205 + jessie-ignore > >> thanks > > > >

Bug#816205: tagging 816205

On Sat, 2016-03-26 at 17:14 +0100, Mathieu Parent wrote: > tags 816205 + jessie-ignore > thanks Was that discussed with anyone on the Release Team before the tag was added? >From a quick look at the bug log it may well be suitable for a -ignore tag, but it shouldn't simply be added by the

Bug#808874: debian-installer: FTBFS on i386: 586 vs. 686

On Fri, 2015-12-25 at 18:55 +0100, Cyril Brulebois wrote: > Ben Hutchings (2015-12-24): > > On Thu, 2015-12-24 at 03:30 +0100, Cyril Brulebois wrote: > > > Ben Hutchings (2015-12-24): > > > > I already updated base-installer for this, and I think the

Bug#806387: menu tests paradoxical

Control: severity -1 normal On Thu, 2015-11-26 at 22:47 +0100, Jörg Frings-Fürst wrote: > Package: lintian > Version: 2.5.38.1 > Severity: serious Definitely not. > Hi, > > Since the tech-ctte decision at bug #741573 is the command listed both in a > menu file and a desktop file prohibited. >

Bug#802474: Error in dist squeeze armel content list

Control: reassign -1 ftp.debian.org Control: forcemerge 801200 -1 On 2015-10-20 13:25, Andreas Hänel wrote: Package: release.debian.org Severity: grave The Release Team don't run the archive. Reassigning to ftp.debian.org. When trying to install python on following release: uname -a Linux

Bug#799717: stress: ships /usr/share/info/dir.gz on arm64

Control: tags -1 -jessie On 2015-10-11 16:56, Eriberto Mota wrote: tags 799717 jessie thanks Hi Uwe, Thanks for your report. Currently, this issue is found in Jessie, not in Sid. So, I added a tag 'jessie'. That's not how to indicate that. If the bug is fixed in sid, mark it as fixed in

Bug#801770: devscripts: rmadison does not run properly but instead has a mishmash of rubbish

Control: tags -1 + moreinfo unreproducible Control: severity -1 important On 2015-10-14 13:12, Sharon Kimble wrote: Package: devscripts Version: 2.15.9 Severity: grave Justification: renders package unusable An issue with a single script in the package does not render the whole package

Bug#740998: closed by Michael Gilbert <mgilb...@debian.org> (Bug#740998: fixed in ndisc6 1.0.1-2)

On Sun, 2015-10-11 at 16:50 +0100, Dominic Hargreaves wrote: > On Sat, Feb 14, 2015 at 01:36:05AM +, Debian Bug Tracking System wrote: > > > ndisc6 (1.0.1-2) unstable; urgency=medium > > . > >* QA upload. > >* Set maintainer to the Debian QA Group (see #713004). > >* Add

Bug#791112: #791112: libcrypto++: library transition may be needed when GCC 5 is the default

On Mon, 2015-08-17 at 11:16 +0200, Christian Hofstaedtler wrote: Hi, I've noticed a new libcrypto++ has entered sid, but the transition tracker[1] doesn't seem to agree on the library names, or something (it still shows libcrypto++ as bad). What's going on there? [1]

Bug#792365: lintian gives false positive for minified js file

Control: severity -1 normal On 2015-07-14 9:26, Pirate Praveen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 package: lintian version: 2.5.33 severity: grave reason: gives wrong lintian error A single false positive for a tag that's not on the auto-reject list is in no way Release

Bug#791467: Processed: block 791467 with 792468, block 792379 with 792468

Control: unblock 792379 with 792468 On Wed, 2015-07-15 at 04:15 +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: [...] Bug #792379 [sponsorship-requests] RFS: plowshare4/1.0.5-2 [RC] -- filesharing website tool implemented in bash 792379 was not

Bug#791751: Please give back openldap (2.4.40+dfsg-2) on mipsel

On Wed, 2015-07-08 at 18:44 +0200, Luca Bruno wrote: Dear wb-team, latest openldap upload (2.4.40+dfsg-2) saw a spurious failure in its testsuite on mipsel. As diff with previous version is quite limited and failure unrelated, we suspect this was a momentary glitch somewhere. Can we

Bug#791469: apt-get upgrade generates Python errors

Control: reassign -1 python-aptdaemon 0.31+bzr413-1.1+deb6u1 On Sun, 2015-07-05 at 09:06 -0400, Bruce Momjian,,, wrote: Running apt-get upgrade or apt-get purge generates this Python error: Reading package lists... Done Building dependency tree Reading state information...

Bug#787515: tortoisehg: uninstallable in sid

Package: tortoisehg Version: 3.1.1-1 Severity: serious Hi, tortoisehg depends on mercurial (= 3.0~), mercurial ( 3.2~), but 3.4 has been in unstable for a month now, rendering tortoisehg uninstallable. This is the last package blocking the migration of mercurial 3.4 to testing so I may

Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.

On Tue, 2015-05-12 at 12:13 +0100, Andy G Wood wrote: Hi Sebastiaan, On Tuesday 12 May 2015 12:03:43 Sebastiaan Couwenberg wrote: [...] Justification: breaks unrelated software This justification is not supported by your bugreport. Which unrelated software does this issue break?

Bug#784979: Make package fit for testing

On Mon, 2015-05-11 at 14:02 +0200, Jörg Frings-Fürst wrote: remove the packages libgphoto2-2-dev and libgphoto2-port10 at update to make the package fit for testing and finish the auto-libgphoto2 transition. Those binary packages have already stopped being built by libgphoto2. That's normal for

Bug#784763: libsane-common: fails to upgrade from 1.0.24-9

On Fri, 2015-05-08 at 21:32 +0200, Andreas Ronnquist wrote: This might be solvable using a simple versioned pre-depends on dpkg - see http://man7.org/linux/man-pages/man1/dpkg-maintscript-helper.1.html#INTEGRATION_IN%20PACKAGES Nope. The problem is that the preinst simply calls rm_conffile,

  1   2   3   4   5   6   7   8   9   10   >