Hi,
As we had to postpone 12.6, let's look at alternative dates.
April 13th
- Not great for me for personal reasons, mhy previously said no. I
could probably do if need be
April 20th
- Doesn't work for me; I'm away from the Tuesday before until late on
the Friday
April 27th
- Doesn't work for
On Fri, 2024-02-16 at 17:35 +, Jonathan Wiltshire wrote:
> The next point release for "bookworm" (12.6) is scheduled for
> Saturday, April 6th. Processing of new uploads into bookworm-
> proposed-updates will be frozen during the preceeding weekend.
Due to recent events, the point release has
On Mon, 2024-02-12 at 18:04 +, Jonathan Wiltshire wrote:
> 12.6 should be around 10th April, so please indicate availability
> for:
>
> 7 April
I assume you mean the 6th here. That should be doable.
> 13 April
Could work, but I would prefer not to for personal reasons.
> 20 April
I'll
Hi,
The next point release for "bullseye" (11.9) is scheduled for Saturday,
February 10th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bookworm" (12.5) is scheduled for Saturday,
February 10th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Tue, 2023-12-19 at 21:25 +, Jonathan Wiltshire wrote:
> It's time to set a date for 12.5 (taking account of the emergency .4)
> and 11.9. I expect this to be the penultimate update for bullseye
> before LTS.
>
> Please indicate availability for:
>
> Saturday 3rd February (preferred for
Hi,
The upgrade is now done. Please let DSA know (preferably either on IRC in
#debian-admin or via a new ticket) if you spot any issues.
Regards,
Adam
On Sun Nov 19 07:53:22 2023, hwans...@mailbox.org wrote:
> Hi,
>
> Am 19. November 2023 02:05:46 MEZ schrieb Cyril Brulebois
> :
> > Hi Adam,
> >
> > Adam D. Barratt via RT (2023-11-18):
[...]
> >> The d-i.debian.org metapackage fails to install on bull
On Sat, 2023-11-18 at 16:21 +0100, Cyril Brulebois wrote:
> Scott Talbert (2023-11-16):
> > > Scott Talbert (2023-11-13):
> > > > Package: release.debian.org
> > > > Severity: normal
> > > > User: release.debian@packages.debian.org
> > > > Usertags: binnmu
> > > > X-Debbugs-Cc:
Hi kibi, -boot,
I'd like to look at upgrading dillon to bullseye in the not-too-distant future.
The d-i.debian.org metapackage fails to install on bullseye, because it depends
on ko.tex-base, which no longer exists in bullseye. The removal notice suggests
that its replacement is
Hi,
The next point release for "bookworm" (12.3) is scheduled for Saturday,
December 9th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Thu, 2023-11-09 at 14:55 +, Steve McIntyre wrote:
> On Fri, Oct 27, 2023 at 11:28:21AM +0100, Steve McIntyre wrote:
> > Argh, forgot to respond to this. :-(
> >
> > On Sat, Oct 07, 2023 at 06:59:03PM +0100, Jonathan Wiltshire wrote:
> > > Hi,
> > >
> > > The next point release for
On Sat, 2023-10-07 at 21:59 +0100, Jonathan Wiltshire wrote:
> On Sat, Oct 07, 2023 at 06:59:03PM +0100, Jonathan Wiltshire wrote:
> > How about:
> > 4th December (better for cadence)
> > 11th December (more likely suitable in practice)
>
> Erm, astute readers will realise the 4th and 11th are
On Wed, 2023-09-13 at 22:48 +0200, Sebastian Andrzej Siewior wrote:
> OpenSSL upstream released 1.1.1w which the last stable update to the
> 1.1.1 series because it is EOL since last Monday.
> The update is fairly small and contains a few fixes for memory leaks.
> The mentioned CVE affects only
Control: tags -1 confirmed
On Wed, 2023-09-27 at 23:47 +0200, Aurelien Jarno wrote:
> The upstream glibc stable branch got a few fixes since the latest
> point
> released, including two security fixes.
>
Please go ahead.
Regards,
Adam
On Sat, 2015-05-09 at 05:02 +0200, Cyril Brulebois wrote:
> Cyril Brulebois (2015-05-09):
> > I've crafted a patch and I'll block this bug report with it; I
> > might set
> > up some workaround until this is resolved in a proper way.
>
> That's #784812.
>
> Local changes in dillon include:
> -
On Thu, 2023-07-13 at 17:51 +0100, Simon McVittie wrote:
> On Thu, 13 Jul 2023 at 16:58:54 +0100, Adam D. Barratt wrote:
> > On Wed, 2023-07-12 at 12:34 +0100, Simon McVittie wrote:
> > > On Wed, 12 Jul 2023 at 12:12:47 +0100, Simon McVittie wrote:
> > >
Control: tags -1 + confirmed
On Tue, 2023-07-11 at 20:51 +0200, Aurelien Jarno wrote:
> The upstream stable branch got a few fixes during the bookworm freeze
> period, and this update pulls them into the debian package. In short:
> - Fix a buffer overflow and memory corruption in the gmon
>
Control: tags -1 + confirmed
On Wed, 2023-07-12 at 12:34 +0100, Simon McVittie wrote:
> On Wed, 12 Jul 2023 at 12:12:47 +0100, Simon McVittie wrote:
> > [ Reason ]
> > https://bugs.debian.org/1040790
> > [ Changes ]
> > All changes are part of resolving or testing #1040790.
>
> Debdiff attached.
Hi Donald,
On Wed, 2023-06-21 at 06:33 -0400, Donald Norwood wrote:
> Hi,
>
> On 6/20/23 13:15, Adam D. Barratt wrote:
> > The traditional cadence for oldstable point releases is four
> > months,
> > rather than two. That technically means that 11.8 would be due
&
On Mon, 2023-06-19 at 22:02 +0100, Jonathan Wiltshire wrote:
> I'm sending this separately to a similar mail for 12.1. That's
> because the
> timings are far enough out that they would make sense on separate
> weekends,
> but they could also be stretched[1] and combined.
>
> Two months from 29th
On Mon, 2023-06-19 at 22:04 +0100, Jonathan Wiltshire wrote:
> The promised 4-6 weeks following release for 12.1 looks like:
>
> 8th July (4)
> 15th July (5)
> 22nd July (6)
>
Any of those should work for me. I'd prefer one of the latter two.
> The first of them would combine with a very
Hi,
Sorry for taking so long to get back to the dates question. I hope to
also have a useful reply to your other mail by the end of this weekend.
On Thu, 2023-04-20 at 11:32 +0200, Paul Gevers wrote:
> On 13-04-2023 11:29, Paul Gevers wrote:
> > For me to do the release, I'd need to get my hands
On Thu, 2023-04-20 at 11:32 +0200, Paul Gevers wrote:
> Dear all,
>
> Progress \o/.
>
> On 13-04-2023 11:29, Paul Gevers wrote:
> > For me to do the release, I'd need to get my hands on the key.
>
> I'm in contact with Jonathan and we're convinced we'll be able to
> get the key to me in time.
>
Control: tags -1 + confirmed d-i
On Tue, 2023-04-18 at 00:06 +0200, Aurelien Jarno wrote:
> There are multiple fixes in this upload, all coming from the upstream
> stable branch:
> - Multiple crashes or memory leak in printf-family functions
> - Overflow fix in the AVX2 implementation of wcsnlen
Control: tags -1 + confirmed d-i
On Thu, 2022-12-22 at 12:13 +, Luca Boccassi wrote:
> We'd like to upload several bug fixes, including security fixes, for
> systemd to bullseye.
> The fixes come from the upstream stable branches which are covered by
> CI and confirmed by reporters.
>
Hi,
The next point release for "bullseye" (11.7) is scheduled for Saturday,
April 29th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Wed, 2023-03-15 at 20:33 +, Jonathan Wiltshire wrote:
> We're overdue for 11.7 and need it done with a keyring update
> included
> before bookworm can be released. The wheels are turning on the
> keyring so
> how do dates in April look for everybody? Saturdays are 1st (probably
> too
>
Hi,
Sorry for the delayed reply, apparently I'm further behind than I
realised. :-(
On Fri, 2023-02-17 at 21:56 +0100, Paul Gevers wrote:
[...]
> What do people think of the idea
> to start picking a release date already?
>
[...]
> Adam, I think we'd also want to do a point release before that
Control: tags -1 + confirmed d-i
On Mon, 2023-01-09 at 14:04 +0100, Bastian Blank wrote:
> Under not completely understood conditions, dhclient completely
> removes
> IPv6 addresses from use and is unable to restore them. This problem
> was
> fixed in the separate script upstream maintains some
Control: tags -1 + confirmed d-i
On Fri, 2022-12-02 at 15:42 +0100, Jordi Mallach wrote:
> I'm requesting the acceptance of a new nano update for stable,
> with 3 additional upstream patches that fix two crash conditions
> and a data-loss condition.
>
Please go ahead.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.6) is scheduled for Saturday,
December 17th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Thu, 2022-11-17 at 21:33 +, Adam D. Barratt wrote:
> We've managed to slip behind on getting a bullseye point release
> sorted, again. :-( I realise we're heading towards the holidays at a
> surprising rate of knots, but hopefully we can find a generally
> agreeable date.
>
Hi,
We've managed to slip behind on getting a bullseye point release
sorted, again. :-( I realise we're heading towards the holidays at a
surprising rate of knots, but hopefully we can find a generally
agreeable date.
Please could you indicate your availability and preferences between:
-
Control: tags -1 + confirmed d-i
On Sun, 2022-08-07 at 15:31 +0200, Michael Biebl wrote:
> I'd like to make a stable upload for systemd fixing two issues in
> systemd-detect-virt
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013342
> systemd - Please backport support for Hyper-V on
Hi,
The next - and final - point release for "buster" (10.13) is scheduled
for Saturday, September 10th. Processing of new uploads into buster-
proposed-updates will be frozen during the weekend of August 27th.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.5) is scheduled for Saturday,
September 10th. Processing of new uploads into bullseye-proposed-
updates will be frozen during the preceding weekend.
Regards,
Adam
Hi,
On Thu, 2022-07-28 at 17:09 +0100, Adam D. Barratt wrote:
> Use of buster-security will pass from the Security Team to LTS in a
> few
> days time, so we should get the EOL point release organised. We need
> at
> least a couple of weeks to get things sorted, so as s
Hi,
Use of buster-security will pass from the Security Team to LTS in a few
days time, so we should get the EOL point release organised. We need at
least a couple of weeks to get things sorted, so as some suggestions:
- August 20
- [August 27 doesn't work for at least me and the Images Team, so
Hi Colin,
On Fri, 2022-03-18 at 08:43 +0100, Cyril Brulebois wrote:
> Adam D. Barratt (2022-03-17):
> > As openssh builds a udeb, I'm CCing KiBi and tagging the bug
> > accordingly.
>
> Making sure upgrades have a chance to work properly seems more
> important
> th
Hi,
The next point release for "bullseye" (11.4) is scheduled for Saturday,
July 9th. Processing of new uploads into bullseye-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi Steve,
On Sun, 2022-06-19 at 18:04 +0100, Steve McIntyre wrote:
> Hey Adam!
>
> On Fri, Jun 17, 2022 at 08:31:23PM +0100, Adam Barratt wrote:
> > We're (again) running behind in getting the next point release for
> > bullseye sorted, and I know we're about to run into the
> > Deb{Camp,Conf}
>
Hi,
We're (again) running behind in getting the next point release for
bullseye sorted, and I know we're about to run into the Deb{Camp,Conf}
period. I think the possible dates that make sense are:
- July 2nd (means freezing next weekend, but so be it)
- July 9th
I think there's already a
Control: tags -1 + confirmed d-i
On Sat, 2022-04-09 at 23:04 +, Thorsten Alteholz wrote:
>
> The attached debdiff for fribidi fixes CVE-2022-25308, CVE-2022-25309
> and
> CVE-2022-25310 in Bullseye. These CVEs have been marked as no-dsa by
> the
> security team.
This looks OK to me,
Control: tags -1 + confirmed d-i
On Thu, 2022-04-28 at 22:21 +1000, Hugh McMaster wrote:
> This update fixes three security vulnerabilities in FreeType
> 2.10.4+dfsg-1.
>
> - CVE-2022-27404: heap buffer overflow via invalid integer decrement
> in
> sfnt_init_face() and woff2_open_font().
> -
Control: tags -1 + d-i
The changes are probably beneficial to the use of nano-udeb as well,
but in any case tagging and CCing for inforamation.
On Fri, 2022-03-18 at 18:15 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
>
> On Mon, Nov 22, 2021 at 01:29:56AM +0100, Jordi Mallach wrote:
On Fri, 2022-03-18 at 14:12 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-18 09:21:50 [+], Adam D. Barratt wrote:
> > Apologies if the status here got confused - based on the above, I
> > was
> > assuming that in the absence of a negative response
On Wed, 2022-03-09 at 08:45 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
> > Feel free to upload; we'll wait for the d-i ack before accepting
> > the
> > package into p-u.
>
> There will be the release of 1.1.1n
On Thu, 2022-03-17 at 19:29 -0400, Daniel Kahn Gillmor wrote:
> On Thu 2022-03-17 17:49:04 +0000, Adam D. Barratt wrote:
> > On Sat, 2022-02-19 at 22:24 -0500, Daniel Kahn Gillmor wrote:
> > > On Sat 2022-02-19 17:09:21 +0000, Adam D. Barratt wrote:
> > > > Co
Control: tags -1 + confirmed d-i
On Tue, 2022-03-15 at 15:20 +, Colin Watson wrote:
> OpenSSH in stable breaks on 32-bit architectures (at least armhf,
> reportedly also i386) after upgrading libc6 to the version in
> bookworm,
> due to changes in its system call interface that affect
Control: tags -1 + confirmed d-i
On Wed, 2022-03-16 at 00:50 +0100, Aurelien Jarno wrote:
> A big part of the changes have been in the buster git branch for many
> months, but I failed to submit the package for a point release up to
> now. What triggered me to look at it again is breakage in the
On Tue, 2022-03-15 at 20:33 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On Thu, 2022-02-17 at 23:15 +0100, Aurelien Jarno wrote:
> > There are multiple fixes in this upload:
> > - 4 security bugs
> > - a fix to avoid preinst script failure when
On Sat, 2022-02-19 at 22:24 -0500, Daniel Kahn Gillmor wrote:
> On Sat 2022-02-19 17:09:21 +0000, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed d-i
> >
[...]
> > That looks fine to me, but will need a d-i ack as the package
> > builds a
> > ud
Control: tags -1 + confirmed d-i
On Thu, 2022-02-17 at 23:15 +0100, Aurelien Jarno wrote:
> There are multiple fixes in this upload:
> - 4 security bugs
> - a fix to avoid preinst script failure when running on kernel x.y.z
> with z > 255.
> - a fix to avoid changes to /etc/nsswitch.conf to be
Hi,
The next point release for "buster" (10.12) is scheduled for Saturday,
March 26th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.3) is scheduled for Saturday,
March 26th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + confirmed d-i
On Sun, 2022-02-20 at 11:01 +0100, Holger Wansing wrote:
> I would like to do a little update to tasksel, to make tasksel
> install
> CUPS for all desktop tasks.
> In the past (buster and before), it was like this as well, via a
> different
> approach: there was a
Control: tags -1 + confirmed d-i
On Mon, 2022-02-21 at 00:07 +0100, Samuel Thibault wrote:
> People have reported that when they work on the linux console with
> the
> espeakup screen reader, if they e.g. cat a long file, and the reader
> starts speaking it, and the user presses some key to
Control: tags -1 + confirmed d-i
On Sun, 2022-02-20 at 21:35 +0100, Samuel Thibault wrote:
> Users have reported that when they are building large packages in
> parallel, or generally loading the system a bit, the espeakup screen
> reader becomes very laggy. This is because espeakup gets
Hi,
As you may have noticed, we're a bit overdue now for both 11.3 and the
penultimate buster point release, 10.12.
Some potential dates:
- March 19th (means freezing next weekend, so not ideal)
- March 26th
- April 2nd
- April 9th
(For personal reasons, I'd rather avoid that last weekend, and
On Sat, 2022-02-19 at 18:52 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-02-19 17:04:16 [+], Adam D. Barratt wrote:
> > Control: tags -1 + confirmed d-i
> …
> > Thanks. Assuming the above is still accurate, then this looks good
> > to
> > me.
> &g
Control: tags -1 + confirmed d-i
On Sun, 2022-02-13 at 13:44 +, Simon McVittie wrote:
> Typeahead search in the file chooser (File -> Save As... dialog)
> doesn't
> work on networked filesystems (NFS/CIFS) under some circumstances.
> (Having Tracker installed might accidentally avoid the bug,
Control: tags -1 + confirmed d-i
On Thu, 2022-01-27 at 17:02 -0500, Daniel Kahn Gillmor wrote:
> Please consider an update to GnuPG in debian bullseye, from version
> 2.2.27-2 to 2.2.27-2+deb11u1.
>
The version mentioned above is correct, but the proposed changelog is
not:
+gnupg2
Control: tags -1 + confirmed d-i
On Tue, 2022-01-11 at 00:00 +0100, Sebastian Andrzej Siewior wrote:
> This is an update to the latest stable update of the openssl package
> provided by upstream. It contains fixes for bugs which were not
> identified as security critical but still worth fixing.
>
Control: tags -1 + confirmed d-i
On Tue, 2021-11-23 at 15:43 +, plugwash wrote:
> When downloading a file greater than 2GB on a 32-bit system wget on
> bullseye
> will truncate it to 2GB. No error is reported, the length of the file
> is simply
> reported as less than it's true length. This
Hi,
The next point release for "bullseye" (11.2) is scheduled for Saturday,
December 18th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
It's (a little past) time that we organised the next point release. As
an "every other" release, this time will only be for stable.
Any of the first three weekends of December would work for me, although
the 4th is my least preferred as it means freezing over the coming
weekend and I'm not
Control: tags -1 + confirmed d-i
Apologies for somehow not processing this upload for so long.
On Thu, 2021-10-07 at 00:34 +0200, Samuel Thibault wrote:
> Bug#994729 was noticed only recently: when installing Debian with
> sysvinit rather than systemd, Braille output wouldn't work in the X
>
On Mon, 2021-09-27 at 12:38 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
To confirm some IRC conversations - given the closeness of the freeze
for 11.1, please feel free to upload and kibi can review the package
from stable-new.
Regards,
Adam
> Control: fix
Control: tags -1 + confirmed d-i
Control: fixed 994042 2.32-3
Hi,
On Sun, 2021-09-26 at 22:16 +0200, Aurelien Jarno wrote:
> Hi,
>
> On 2021-09-26 20:46, Adam D. Barratt wrote:
> > On Tue, 2021-09-21 at 23:47 +0200, Aurelien Jarno wrote:
> > [...]
> > > In the mea
On Tue, 2021-09-21 at 23:47 +0200, Aurelien Jarno wrote:
[...]
> In the meantime another issue that would need to be fixed in sid
> > > came
> as
> bug#994042.
>
> This time the issue is in the preinst. To summarize, in the case
> debconf is not usable to prompt the user about the upgrade, the
>
Control: tags -1 + confirmed d-i
On Fri, 2021-09-10 at 02:17 +0200, Samuel Thibault wrote:
> [ Reason ]
> Espeak-ng cannot drive the mbrola-fr4 speech synthesis voice if the
> mbrola-fr1 package is not installed. This is because some of the mb-
> fr4
> espeak rules refer to the fr1 voice while
Hi,
The first point release for "bullseye" (11.1) is scheduled for
Saturday, October 9th. Processing of new uploads into bullseye-
proposed-updates will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.11) is scheduled for Saturday,
October 9th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
Thanks for the responses everyone. Mark indicated on IRC that he'd be
happy to be ftpmaster-du-jour on any of the dates.
On Mon, 2021-09-06 at 12:51 +0100, Adam D. Barratt wrote:
> We've ended up being late with planning 10.11 due to the timing of
> the bullseye release, and als
Hi,
We've ended up being late with planning 10.11 due to the timing of the
bullseye release, and also need to look at getting 11.1 sorted.
Traditionally, we've combined stable and oldstable point releases (at
2- and 4-month cadences) while both are supported. That would still be
my preference,
Control: tags -1 + confirmed d-i
On Sun, 2021-08-22 at 14:58 +0200, Aurelien Jarno wrote:
> During the upgrade from Buster to Bullseye, the SSH server is not
> restarted following the libc6 upgrade, causing new SSH connections to
> get rejected until the SSH server is restarted later in the
On Sat, 2021-07-17 at 22:25 +0200, Paul Gevers wrote:
> 14 August (day before DebCamp)
> 21 August (last day of DebCamp)
> RT: elbrus
These both look OK.
> 28 August (DebConf)
> RT: elbrus
That's a holiday weekend in the UK; I'll be visiting family and then
the Debian UK BBQ.
> 4
On Fri, 2021-06-11 at 11:06 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On Thu, 2021-06-03 at 13:31 +0200, Andreas Metzler wrote:
> > I would like to fix the non-DSA CVE-2021-33560 for buster by
> > cherrypicking the respective commit from 1.8.
Hi,
On Mon, 2021-05-31 at 01:52 +0200, Cyril Brulebois wrote:
> Hi,
>
> Adam D. Barratt (2021-05-29):
> > Apologies for letting this fall through the cracks for a while.
> >
> > As glib2.0 produces a udeb, this will need a KiBi-ack, so CCing and
> > tagging ap
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
> Hi all,
>
> On 06-06-2021 20:03, Paul Gevers wrote:
> > With the availability of Adam now known (and some off-list info),
> > we have:
> >
[...]
> > So, what to pick? We still believe that shorter freezes are better
> > for
> > the Debian
On Sun, 2021-05-30 at 09:09 +0200, Paul Gevers wrote:
> 26 June
> 3 July
> 10 July
> 17 July [Steve (CD), press]
> 24 July [Steve (CD), press]
> 31 July
> 7 August
> 14 August
July 17th doesn't work well for me unfortunately*.
The others currently all look OK, although I'd prefer not to do two
Hi,
The next point release for "buster" (10.10) is scheduled for Saturday
June 19th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
We're now a little overdue for 10.10, but it looks like we're ready in
terms of shim etc. changes, so we should look at dates.
Please could you indicate your availability for (and any preferences
amongst) the following:
Saturday June 12th
Saturday June 19th
Saturday June 26th
The 12th is
Control: tags -1 + confirmed d-i
On Sat, 2021-03-27 at 17:21 +, Simon McVittie wrote:
> Backport security fixes from testing/unstable. The security team say
> they do not intend to issue a DSA for these.
>
> [ Impact ]
> * CVE-2021-28153: symlink attack allowing an attacker to create an
>
[I'm quite behind on list mail in general, and tend to use the BTS for
tracking / processing SRM work. Direct mail often works better than
waiting for me to notice list mail]
On Wed, 2021-04-21 at 21:19 +0200, Paul Gevers wrote:
> I've seen replies from Steve for CD, from Donald for Press and
Hi Steve,
On Fri, 2021-03-19 at 11:42 +, Steve McIntyre wrote:
> Houston, we have a problem. I know that you've announced the 27th for
> the point release, but we're not going to have a new shim ready for
> then.
>
> We've been hard at work testing and fixing things for the last couple
> of
Hi,
The next point release for "buster" (10.9) is scheduled for Saturday
March 27th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
It's that time again, when we should look at organising the next point
release.
Please could you confirm your availability, and any preferences, for
the following:
- March 27th
- April 3rd
- April 10th
I'd prefer to avoid April 10th if possible, for slightly selfish
reasons. :-)
Regards,
I somehow missed that libbsd produces a udeb when I was processing
stable-new, so CCing KiBi and -boot now.
Regards,
Adam
On Wed, 2021-03-03 at 12:05 +0100, Gianfranco Costamagna wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: pu
> Tags: buster
>
Control: tags -1 + confirmed d-i
Hi,
On Fri, 2021-01-29 at 17:47 +0100, Michael Biebl wrote:
> I'd like to make a stable upload for systemd fixing #975561:
>
> journal: do not trigger assertion when journal_file_close() get
> NULL
>
> The rest is autopkgtest updates, as the current state is
On Sun, 2021-01-24 at 12:25 +0100, Sebastian Andrzej Siewior wrote:
> On 2021-01-22 16:38:28 [+], Adam D. Barratt wrote:
> > Both would be good, please.
>
> Here is the complete diff against the last openssl release in Buster.
Thanks.
I realise that this has been dragging on
On Thu, 2021-01-21 at 21:06 +0100, Sebastian Andrzej Siewior wrote:
> On 2021-01-16 19:14:53 [+0100], Kurt Roeckx wrote:
> > So I went over the open issues and pull requests, and currently
> > don't see a reason not to upload it to unstable with those 2
> > patches. I don't know about any other
Hi,
The next point release for "buster" (10.8) is scheduled for Saturday
February 6th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Mon, 2021-01-11 at 15:57 +0100, Cyril Brulebois wrote:
> Hi,
>
> Adam D. Barratt (2020-12-31):
> > Sorry for the delay in picking this back up.
>
> Same here.
>
> > As grub produces udebs, this will need a KiBi-ack, so tagging and
> > CCing accordi
Hi,
It's that time again, when we should get 10.8 out.
Please could you confirm your availability, and any preferences, for
the following:
- January 30th (would mean we would have to freeze next weekend, so a
bit tight)
- February 6th
My personal preference would be the 6th.
Cheers,
Adam
Hi,
On Fri, 2021-01-08 at 23:59 +0100, Kurt Roeckx wrote:
> On Fri, Jan 08, 2021 at 11:39:13PM +0100, Sebastian Andrzej Siewior
> wrote:
[...]
> > The i release in unstable managed to migrate to testing. It was
> > blocked due to ci by m2crypto and swi-prolog. The swi-prolog issue
> > got fixed
Control: tags -1 + confirmed d-i
On Sun, 2020-11-29 at 16:57 +, Colin Watson wrote:
> Following the security updates in July for the "BootHole" set of
> vulnerabilities, we had a number of reports of failures to boot after
> the upgrade. These weren't fundamentally a new problem, in that
>
On Fri, 2020-11-20 at 21:04 +0100, Sebastian Andrzej Siewior wrote:
> On 2020-11-20 17:24:30 [+], Adam D. Barratt wrote:
> > Predictably we're again quite close to a point release. :-( (One
> > week from freeze, specifically.)
>
> oh.
In fairness, given an approxim
On Sun, 2020-11-15 at 11:29 +0100, Sebastian Andrzej Siewior wrote:
> control: retitle -1 buster-pu: package openssl/1.1.1h-1
>
> On 2020-05-02 22:34:40 [+0100], Adam D. Barratt wrote:
> > > > Do we have any feeling for how widespread such certificates
> > >
1 - 100 of 522 matches
Mail list logo
