Control: severity -1 important
Control: retitle -1 Not buildable on some ports architectures due to missing
rustc / cargo
On Sun, 2024-11-17 at 20:06 +0100, Drew Parsons wrote:
> python-orjson Build-Depends: cargo
>
> But cargo was removed from Debian (unstable) in May 2024.
The cargo _source_
On Fri, 2024-07-19 at 16:13 +0200, Diederik de Haas wrote:
> [ adding debian-release to the list for some troubling observations ]
>
> On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote:
>
[...]
> > Note that
> > https://www.debian.org/releases/stable/amd64/apcs01.en.html
> > does not re
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 ganet
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
> > th
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: 470
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
&
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&#x
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":
libtrapperkeeper-w
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 w
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. Ar
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 u
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
> >
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
sec
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 due
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
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
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
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&arch=amd64
> >
> > ...
> > Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all
> > Jan 4 03:57:23.25
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
Version
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 1.3.0-1
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)
> * (CVE-
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 inst
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):
>
> 2
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
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
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 -
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',
rsvg_internals/s
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 all
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
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
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:
make
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 nex
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,
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:
> > > > Control: severity
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:
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: release.debian.
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 least
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:
M
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 th
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
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 w
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 debdi
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 see
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.
> > >
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
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:
> > > > > https:/
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
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
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 unst
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
>
>
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
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:
> https:/
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 differe
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
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 update a
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
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 th
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
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 dns
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 incorrect.
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
>
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 Cr
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
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&arch=mips64el&;
> ver=1.9.1-1&stamp=1506204287&raw=0
>
> This happens because:
> - The RLIMIT_NOFILE
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
> > p
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
>
&
5 06:30:03 2017 -12
> > gpg: using RSA key C5CE5DC2C542CD59
> > gpg: BAD signature from "Adam D. Barratt "
> > [unknown]
[...]
> The difference between the keyrings is the trust packets:
[...]
> This is happening because of a combination of several factors
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 anyo
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` uses
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
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 the
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
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&#
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 r
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
https:
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
https://lists.exim.org/lurker/message/20161012.203414.c4c043d5.en
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)
atta
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
> U
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
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
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 believe,
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. Mo
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
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 upgra
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
On Mon, 2016-03-28 at 14:39 +0200, Mathieu Parent (Debian) wrote:
> 2016-03-26 18:35 GMT+01:00 Adam D. Barratt :
> > On Sat, 2016-03-26 at 17:14 +0100, Mathieu Parent wrote:
> >> tags 816205 + jessie-ignore
> >> thanks
> >
> > Was that discussed with anyone
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 maintai
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 only other
> > > > change needed was in build/
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.
>
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 G
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 the
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 unusab
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 conflict
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] https://
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 bl
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 C
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.
>
> Ca
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 informatio
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
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 i
1 - 100 of 1551 matches
Mail list logo
