On 2022-03-21 22:11:17 [+0100], Julien Cristau wrote:
> Hi,
Hi,
> Specifically, we were hoping to better understand the risk of openssl
> changes breaking existing setups. It's possible the issues with gnutls
> and libnet-ssleay-perl tests were narrowly scoped enough that that risk
> is low, but
Your message dated Mon, 21 Mar 2022 23:28:18 +0100
with message-id
and subject line Re: Bug#1006233: transition: poppler
has caused the Debian Bug report #1006233,
regarding transition: poppler
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On 2022-03-21 22:04:08 [+0100], Salvatore Bonaccorso wrote:
> Hi Sebastian,
Hi Salvatore,
> > +gnutls28 (3.6.7-4+deb10u7.1) buster; urgency=medium
>
> As not yet uploaded, can you change this to 3.6.7-4+deb10u8 instead.
Just did so.
> Regards,
> Salvatore
Sebastian
Control: retitle -1 buster-pu: package libnet-ssleay-perl/1.85-2+deb10u1
On Mon, Mar 21, 2022 at 10:02:15PM +0100, Salvatore Bonaccorso wrote:
> Hi Adrian,
Hi Salvatore,
> On Mon, Mar 21, 2022 at 05:55:00PM +0200, Adrian Bunk wrote:
> > --- libnet-ssleay-perl-1.85/debian/changelog
Processing control commands:
> retitle -1 buster-pu: package libnet-ssleay-perl/1.85-2+deb10u1
Bug #1008056 [release.debian.org] buster-pu: package libnet-ssleay-perl/1.85-2.1
Changed Bug title to 'buster-pu: package libnet-ssleay-perl/1.85-2+deb10u1'
from 'buster-pu: package
Cyril Brulebois (2022-03-21):
> Hopefully that's fine, but I could understand if you'd prefer
> 0.0.64+deb10u1 with just the dasd-config.c change. At least initially,
> it seemed to make sense to use the same approach for both buster and
> bullseye uploads.
Changes were prepared days ago, forgot
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Dipak Zope1
Hi,
Dipak Zope was kind enough to dig into s390x issues, and found s390-dasd
to be the missing piece in bullseye. I'm therefore proposing this change
Control: tags -1 confirmed
On 2022-03-21 18:54:38 +0100, Jérémy Lal wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: Debian Javascript Maintainers
>
>
> Hi,
>
> this transition correspond to a nodejs
Processing control commands:
> tags -1 confirmed
Bug #1006944 [release.debian.org] transition: proj
Added tag(s) confirmed.
--
1006944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 confirmed
Bug #1008063 [release.debian.org] transition: nodejs
Added tag(s) confirmed.
--
1008063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 confirmed
On 2022-03-08 18:11:58 +0100, Bas Couwenberg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org
> Control: block -1 by 998833
> Control:
Your message dated Mon, 21 Mar 2022 22:37:01 +0100
with message-id <2410b455-e75d-91ce-2d20-b7b57d55c...@debian.org>
and subject line Re: Bug#1007792: nmu: fdroidcl_0.5.0-3+b3
has caused the Debian Bug report #1007792,
regarding nmu: fdroidcl_0.5.0-3+b3
to be marked as done.
This means that you
Hi,
On Fri, 18 Mar 2022 16:22:56 +0100 Julien Cristau
wrote:
[...]
> Can you clarify the issue and how the 3 affected packages interact?
The
> mailing list links seem to talk about plasma-discover's KNS backend so
I guess
> I understand that part, how are plasma-desktop and knewstuff
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Dipak Zope1
Hi,
Dipak Zope was kind enough to dig into s390x issues, and found s390-dasd
to be the missing piece in bullseye. I'm therefore proposing this change
to
Hi,
Specifically, we were hoping to better understand the risk of openssl
changes breaking existing setups. It's possible the issues with gnutls
and libnet-ssleay-perl tests were narrowly scoped enough that that risk
is low, but we're just not sure right now. Other input would be
welcome.
Hi Adrian,
On Mon, Mar 21, 2022 at 05:55:00PM +0200, Adrian Bunk wrote:
> --- libnet-ssleay-perl-1.85/debian/changelog 2018-09-02 23:19:51.0
> +0300
> +++ libnet-ssleay-perl-1.85/debian/changelog 2022-03-21 17:36:31.0
> +0200
> @@ -1,3 +1,11 @@
> +libnet-ssleay-perl (1.85-2.1)
Hi Sebastian,
On Mon, Mar 21, 2022 at 06:48:37PM +0100, Sebastian Andrzej Siewior wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: pu
> Tags: buster
> Severity: normal
>
> I prepared an update to fix the debci regression caused by the openssl
>
I would like to stop receiving these emails
How do I stop these emails
On Mon, Mar 21, 2022, 3:27 PM Adam D. Barratt
wrote:
> On Sun, 2022-03-20 at 22:00 +0100, Paul Gevers wrote:
> > Dear Sebastian, Kurt,
> >
> > On 19-03-2022 12:33, Adam D Barratt wrote:
> > > Upload details
> > > ==
> > >
> > > Package: openssl
> > >
On Sun, 2022-03-20 at 22:00 +0100, Paul Gevers wrote:
> Dear Sebastian, Kurt,
>
> On 19-03-2022 12:33, Adam D Barratt wrote:
> > Upload details
> > ==
> >
> > Package: openssl
> > Version: 1.1.1n-0+deb10u1
> >
> > Explanation: new upstream release
>
> We're seeing a regression in
Hi mips porters,
On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers wrote:
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:gcc-defaults-mipsen has been trying to
migrate
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: buster
Severity: normal
I prepared an update to fix the debci regression caused by the openssl
update. The complete analysis is in #959469.
The patch affects only the testsuite which is run as part of
On Mon, 2022-03-21 at 11:03 +0100, Andreas Beckmann wrote:
> On 20/03/2022 00.45, Adam D. Barratt wrote:
> > The window closes "tomorrow", which is mostly "when Adam has had
> > enough", but is usually by the start of the 19:52 dinstall at the
> > latest.
>
> Not sure if relative date "tomorrow"
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: Debian Javascript Maintainers
Hi,
this transition correspond to a nodejs 12 -> 14 major major bump.
I carefully checked (twice, actually) that all build-dependencies of
X-Debbugs-Cc: gnutl...@packages.debian.org, Kurt Roeckx , Paul
Gevers , Sebastian Andrzej Siewior
On 2022-03-21 Sebastian Andrzej Siewior wrote:
> On 2022-03-21 00:12:11 [+0100], To Kurt Roeckx wrote:
> > doesn't help here but
> > -cipher "ALL:@SECLEVEL=1"
> > does.
> Only debci is
On 2022-03-21 17:55:00 [+0200], Adrian Bunk wrote:
> > * Backport upstream fix for test failures with OpenSSL 1.1.1n.
> > (Closes: #1008055)
Thank you Adrian.
Sebastian
Processing changes file: systemd_247.3-7_mipsel-buildd.changes
ACCEPT
On Mon, 14 Mar 2022 02:30:08 +0100 Matthias Klose wrote:
> >
> > I have not tested by myself, but I heard from an archlinux
> > developer that this API bump breaks a lot packages. And
> > some upstreams decided to disable or drop tbb support as
> > a result. I guess we can take similar measures
Processing changes file: systemd_247.3-7_mips64el-buildd.changes
ACCEPT
On Mon, Mar 21, 2022 at 05:46:21PM +0200, Adrian Bunk wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: Debian Perl Group
> , Debian OpenSSL Team
>
>
> * Backport upstream fix for test failures
Processing changes file: systemd_247.3-7_arm64-buildd.changes
ACCEPT
Processing changes file: systemd_247.3-7_armel-buildd.changes
ACCEPT
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Perl Group ,
Debian OpenSSL Team
* Backport upstream fix for test failures with OpenSSL 1.1.1n.
(Closes: #1008055)
The fix touches only tests and
Processing changes file: systemd_247.3-7_amd64-buildd.changes
ACCEPT
Processing changes file: systemd_247.3-7_armhf-buildd.changes
ACCEPT
Processing changes file: systemd_247.3-7_i386-buildd.changes
ACCEPT
Processing changes file: systemd_247.3-7_ppc64el-buildd.changes
ACCEPT
Processing
Am 21.03.22 um 15:56 schrieb Julien Cristau:
On Mon, Mar 21, 2022 at 03:46:01PM +0100, Michael Biebl wrote:
Am 21.03.22 um 15:36 schrieb Julien Cristau:
Yes. Thanks for the due diligence.
Just a quick question:
Which version number should I pick?
a/ 1.30.6-1~deb11u1
b/ 1.30.6-1+deb11u1
On Mon, Mar 21, 2022 at 03:46:01PM +0100, Michael Biebl wrote:
>
> Am 21.03.22 um 15:36 schrieb Julien Cristau:
>
> > Yes. Thanks for the due diligence.
>
> Just a quick question:
> Which version number should I pick?
>
> a/ 1.30.6-1~deb11u1
> b/ 1.30.6-1+deb11u1
> c/ 1.30.6-2
>
>
> I
On Saturday, March 19, 2022 12:42:32 PM EDT Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Fri, 2022-01-07 at 13:01 -0500, Scott Kitterman wrote:
> > This is similar to #1003261 for bullseye, although there are fewer
> > Debian specific changes because most weren't applicable to or
On Saturday, March 19, 2022 12:12:35 PM EDT Julien Cristau wrote:
> Control: tag -1 confirmed
>
> On Fri, Jan 07, 2022 at 12:37:35AM -0500, Scott Kitterman wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: bullseye
> > User: release.debian@packages.debian.org
> > Usertags:
Am 21.03.22 um 15:36 schrieb Julien Cristau:
Yes. Thanks for the due diligence.
Just a quick question:
Which version number should I pick?
a/ 1.30.6-1~deb11u1
b/ 1.30.6-1+deb11u1
c/ 1.30.6-2
I think, now that I have made changes (with the revert of the WPA3 bits)
compared to 1.30.6-1,
Control: tag -1 confirmed
On Mon, Mar 21, 2022 at 03:28:48PM +0100, Michael Biebl wrote:
>
> Hi Julien
>
> Am 18.03.22 um 16:46 schrieb Julien Cristau:
> > Control: tag -1 moreinfo
> >
> > Hi Michael,
> >
> > Sorry it took so long to get to this. I've got a couple of questions
> > from the
Processing control commands:
> tag -1 confirmed
Bug #994622 [release.debian.org] bullseye-pu: package
network-manager/1.30.6-1~deb11u1
Added tag(s) confirmed.
--
994622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hi Julien
Am 18.03.22 um 16:46 schrieb Julien Cristau:
Control: tag -1 moreinfo
Hi Michael,
Sorry it took so long to get to this. I've got a couple of questions
from the NEWS file; will keep looking at the actual diff though.
On Mon, Sep 20, 2021 at 01:09:00PM +0200, Michael Biebl wrote:
On 2022-03-21 00:12:11 [+0100], To Kurt Roeckx wrote:
> doesn't help here but
>-cipher "ALL:@SECLEVEL=1"
>
> does.
Only debci is affected. The package builds because this testsuite is not
part of the build process.
I prepared a NMU against Buster for gnutls. I can open later today a
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
node-mermaid is vulnerable to XSS attack (CVE-2021-23648)
[ Impact ]
medium vulnerability
[ Tests ]
Test passed, new upstream test not applicable here
[ Risks ]
Low
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1003948 = bullseye pending
Bug #1003948 [release.debian.org]
package release.debian.org
tags 1003948 = 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: systemd
Version: 247.3-7
Processing changes file: intel-microcode_3.20220207.1~deb10u1_multi.changes
ACCEPT
Processing changes file: intel-microcode_3.20220207.1~deb11u1_multi.changes
ACCEPT
Processing changes file: systemd_247.3-7_source.changes
ACCEPT
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1008030 = buster pending
Bug #1008030 [release.debian.org] buster-pu:
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1008031 = bullseye pending
Bug #1008031 [release.debian.org]
package release.debian.org
tags 1008031 = 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: intel-microcode
Version:
package release.debian.org
tags 1008030 = buster pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian buster.
Thanks for your contribution!
Upload details
==
Package: intel-microcode
Version:
Your message dated Mon, 21 Mar 2022 11:16:01 +0100
with message-id
and subject line Re: Bug#1006456: transition: openldap
has caused the Debian Bug report #1006456,
regarding transition: openldap
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On 20/03/2022 00.45, Adam D. Barratt wrote:
The window closes "tomorrow", which is mostly "when Adam has had
enough", but is usually by the start of the 19:52 dinstall at the
latest.
Not sure if relative date "tomorrow" meant Sunday or Monday. If it's too
late now, no problem, we can postpone
On 20/03/2022 19.00, Adam D. Barratt wrote:
Just to confirm, this and nvidia-modprobe - as the only packages from
the set so far uploaded AFAICS - are OK to be included in 11.3 without
needing the remainder of the updates?
Yes, they are fully independent. But the remaining */470 uploads are
On 19/03/2022 18.27, Adam D. Barratt wrote:
Please go ahead; thanks.
FTR, the incremental debdiff from 470.103.01-1 to 470.103.01-3~deb11u1
it contains the same additional changes also added with the tesla-450
upload and some preparations for phasing out tesla-460 in favor of
tesla-470.
On 19/03/2022 17.50, Adam D. Barratt wrote:
Please go ahead.
FTR, the incremental debdiff from 470.103.01-1 to 470.103.01-2~deb11u1
dropping 'Depends: | libnvidia-tesla-460-cfg1' in preparation for
migrating from tesla-460 to tesla-470 does not harm even if we don't
switch tesla-460 to
56 matches
Mail list logo
