On Sun, 2017-08-27 at 16:48 +0100, Jonathan Wiltshire wrote:
> I'm working on dates for 9.2; by a two month cycle we're aiming for
> around 23rd September. How about one of:
>
> 23rd/24th September
> 30th Septmber/1st October
>
> [SRMs: needs one of you too please :) ]
I'd prefer to avoid the
Control: tags -1 + confirmed d-i
On Fri, 2017-09-29 at 22:39 +0200, Christoph Biedl wrote:
> there are several non-dsa issues open for busybox. Now wearing the
> maintainer's hat (together with Chris Boot, cc'd), I'd like to fix
> them in an upcoming point release, for both jessie and stretch.
Control: tags -1 + confirmed d-i
On Fri, 2017-09-29 at 22:44 +0200, Christoph Biedl wrote:
> as mentioned in #-1, I'd like to fix the existing non-dsa
> issues in busybox.
>
As for the stretch request, I'm happy with the patch but we'll need a
d-i ack.
Regards,
Adam
Control: tags -1 + pending
On Sun, 2017-09-24 at 09:16 +0200, Sven Joachim wrote:
> On 2017-09-23 19:59 +0100, Adam D. Barratt wrote:
>
> > Control: tags -1 -moreinfo +confirmed
> >
> > On Thu, 2017-09-07 at 19:06 +0200, Cyril Brulebois wrote:
> > > Sven Joac
On Thu, 2017-08-24 at 22:59 +0530, Pirate Praveen wrote:
> On വ്യാഴം 24 ആഗസ്റ്റ് 2017 09:46 വൈകു, Cyril Brulebois wrote:
> > Great thing that point releases usually happen once every 3 months, right?
> >
> > Anyway: right now, D-I Buster Alpha 1 has the priority; point release
> > material can
Control: tags -1 + confirmed d-i
On Mon, 2017-08-28 at 10:21 +0200, Ondřej Surý wrote:
> this is the next update in the series of KSK-2017 RZ KSK rollover.
>
> Only the default keys have been updated.
This looks fine to me, but will need a d-i ack due to the fact that the
package generates a
Control: tags -1 + confirmed d-i
On Mon, 2017-08-28 at 11:03 +0200, Ondřej Surý wrote:
> this is the jessie counterpart of bind9 update to KSK-2017.
>
> No other change has been done to the package.
Nonetheless, the udeb means that we need a d-i ack.
+bind9 (1:9.9.5.dfsg-9+deb8u13.1) jessie;
Hi,
The next point release for "jessie" (8.10) is scheduled for Saturday,
December 9th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.3) is scheduled for Saturday,
December 9th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + confirmed
On Sun, 2017-10-29 at 19:48 +0100, Lukas Schwaighofer wrote:
> I hereby ask for permission to update the syslinux package in jessie
> as
> well. The update fixes a bug in the isolinux isohybrid MBR causing
> boot
> failures with some old BIOS [1].
>
Please go
Control: tags -1 + pending
On Sat, 2017-11-18 at 19:10 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Sun, 2017-10-29 at 19:48 +0100, Lukas Schwaighofer wrote:
> > I hereby ask for permission to update the syslinux package in
> > jessie
> > as
On 2017-11-15 18:30, Steve McIntyre wrote:
On Wed, Oct 25, 2017 at 05:00:16PM +0100, Adam Barratt wrote:
On 2017-09-24 17:38, Jonathan Wiltshire wrote:
Hi,
Our target for 9.3 and 8.10 is the first weekend in December (this
happily
makes the following target the beginning of February, avoiding
On Thu, 2017-11-16 at 08:02 +, Adam D. Barratt wrote:
> On 2017-11-15 18:30, Steve McIntyre wrote:
> > On Wed, Oct 25, 2017 at 05:00:16PM +0100, Adam Barratt wrote:
> > > On 2017-09-24 17:38, Jonathan Wiltshire wrote:
[...]
> > > > 2nd December
> > >
On 2017-09-24 17:38, Jonathan Wiltshire wrote:
Hi,
Our target for 9.3 and 8.10 is the first weekend in December (this
happily
makes the following target the beginning of February, avoiding the
festive
season).
Accordingly I'm looking at one of:
[...]
2nd December
9th December (but
and now without the typo in KiBi's address *sigh*
On Mon, 2018-05-14 at 20:55 +0100, Adam D. Barratt wrote:
> [CC += KiBi]
>
> On Mon, 2018-05-14 at 18:19 +0100, Jonathan Wiltshire wrote:
> > We're due a point release any day now. Please indicate your
> >
[CC += KiBi]
On Mon, 2018-05-14 at 18:19 +0100, Jonathan Wiltshire wrote:
> We're due a point release any day now. Please indicate your
> availablility
> out of:
>
> - May 26th (meaning freeze this coming weekend, which might be a big
> ask)
> - Jun 2nd (which may require an unusual SRM)
> -
On 2018-06-08 18:51, Adam D. Barratt wrote:
[Cc += debian-kernel]
On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
On 15037 March 1977, Jonathan Wiltshire wrote:
[...]
We're past any of the above by now, and while looking through the to-do
list for the final jessie point release, I
-kernel: any chance of a yes/no ASAP, please?
On 2018-06-08 18:51, Adam D. Barratt wrote:
[Cc += debian-kernel]
On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
On 15037 March 1977, Jonathan Wiltshire wrote:
> - May 26th (meaning freeze this coming weekend, which might be a
&g
[Cc += debian-kernel]
On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
> On 15037 March 1977, Jonathan Wiltshire wrote:
> > - May 26th (meaning freeze this coming weekend, which might be a
> > big
> > ask)
>
> No.
>
> > - Jun 2nd (which may require an unusual SRM)
>
> Possible.
>
>
Hi,
On Mon, 2018-06-18 at 20:02 +0200, Cyril Brulebois wrote:
> Adam D. Barratt (2018-06-18):
> > One thing I'd overlooked when scheduling binNMUs for d-i in
> > preparation for the point release is that there's been a kernel ABI
> > change (actually, two) in opu since the p
[recipient list dropped to KiBi, -boot and -release]
On Tue, 2018-05-15 at 22:56 +0200, Cyril Brulebois wrote:
Anything June/July-ish should be good for me.
>
>
> debian-boot@, if there's anything needing a fix in jessie, please
> follow up to the list and myself.
One thing I'd overlooked when
[Sorry, this got stuck in drafts]
On Mon, 2018-06-25 at 22:06 +0200, Cyril Brulebois wrote:
> Adam D. Barratt (2018-06-25):
> > After some discussion on IRC, we've decided to go with the 14th and
> > look at making the press side more handleable for that date.
>
> S
On Wed, 2018-06-27 at 23:00 +0200, Cyril Brulebois wrote:
> Adam D. Barratt (2018-06-27):
> > On Mon, 2018-06-25 at 22:06 +0200, Cyril Brulebois wrote:
> > > Not that I have big plans right now, except maybe working on the
> > > dini ftbfs within stretch (once the
Hi,
The next point release for "stretch" (9.5) is scheduled for Saturday,
July 14th. Processing of new uploads into stretch-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
On Tue, 2018-06-12 at 18:00 +0200, Laura Arjona Reina wrote:
>
> El 12 de junio de 2018 13:44:52 CEST, "Adam D. Barratt" rratt.org.uk> escribió:
[...]
> > - July 7th
>
> This we (publicity) can, and prefer it.
>
> > - July 14th
>
> This, coul
On Tue, 2018-06-12 at 12:44 +0100, Adam D. Barratt wrote:
[...]
> Given all of the above, I think the sanest option is to concentrate
> on getting 8.11 done and jessie off our radar and then get 9.5
> sorted.
>
> For suggested dates for 9.5, we know that June 30th is a no-go,
&
On Sat, 2018-02-10 at 12:27 +0100, Julien Cristau wrote:
> Can you please let us know your availability on the following:
> - March 3
This works, but would be my least preferred option as it means the p-u
freeze would be in just over a week's time.
> - March 10
> - March 17
> - March 24
Any of
Hi,
The next point release for "stretch" (9.4) is scheduled for Saturday,
March 10th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Sat, 2018-02-10 at 12:27 +0100, Julien Cristau wrote:
> Hi,
>
> we shipped 9.3 a couple of months ago, so we're overdue for 9.4.
>
> Can you please let us know your availability on the following:
> - March 3
> - March 10
> - March 17
> - March 24
> - March 31
The useful options look to be
On Wed, 2018-06-27 at 20:16 +0100, Adam D. Barratt wrote:
> [Sorry, this got stuck in drafts]
>
> On Mon, 2018-06-25 at 22:06 +0200, Cyril Brulebois wrote:
> > Adam D. Barratt (2018-06-25):
> > > After some discussion on IRC, we've decided to go with the 14th
> &
Hi,
On Tue, 2018-07-10 at 02:36 +0200, Cyril Brulebois wrote:
> Hi Adam,
>
> Adam D. Barratt (2018-07-08):
> > As with 8.11, there's been a kernel ABI bump for stretch since 9.4,
> > so
> > we'll need a source d-i upload in order to accommodate that.
> >
Hi,
On Wed, 2018-07-11 at 06:11 +0200, Cyril Brulebois wrote:
> In the end I've been out longer than I thought I would, so I only
> managed to give it a go during the night. Being bugged by the
> perspective of only build-testing d-i before the upload, I've gone
> ahead with the whole “hack an
On Wed, 2018-07-11 at 06:52 +0100, Adam D. Barratt wrote:
> If that upload gets accepted and built during the day, I can
> > probably take care of dini this evening.
>
> Thanks; flagged for acceptance.
All of the builds were accepted in time for the 13:52 dinstall, so
ev
On Thu, 2018-07-12 at 01:41 +0200, Cyril Brulebois wrote:
> Adam D. Barratt (2018-07-11):
> > All of the builds were accepted in time for the 13:52 dinstall, so
> > everything should be in place for the dini upload.
>
> Right, I had seen the successful builds earlier but d
On 2018-10-23 15:35, Daniel Kahn Gillmor wrote:
Thanks to Adam for your ongoing work on the stable releases!
I just wanted to clarify a few points here.
On Tue 2018-10-23 08:57:08 +0100, Adam D. Barratt wrote:
An issue is that the gnupg update itself doesn't really qualify for
stable-updates
On Tue, 2018-10-23 at 10:35 -0400, Daniel Kahn Gillmor wrote:
> The fact that the upstream-supported version of enigmail that works
> with the upcoming stretch version of thunderbird depends on these
> fixes is, as you say, another reason to suggest inclusion in debian
> stretch.
>From
Hi,
The next point release for "stretch" (9.6) is scheduled for Saturday,
November 10th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Mon, 2018-10-22 at 22:06 +0200, Ansgar Burchardt wrote:
> Hi,
>
> "Adam D. Barratt" writes:
> > - November 10th
>
> This would work if needed, though I don't mind someone else doing the
> archive side (still have some things to sort out *sigh*).
This i
On Sun, 2018-07-29 at 08:40 +0100, Steve McIntyre wrote:
> On Fri, Jul 27, 2018 at 09:29:22PM +0800, Jonathan Wiltshire wrote:
> > On Fri, Jul 27, 2018 at 09:20:57PM +0800, Jonathan Wiltshire wrote:
> > > On Fri, Jul 27, 2018 at 06:18:06PM +0800, Jonathan Wiltshire
> > > None
> > > of these work
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 2019-02-20 18:37, Steve McIntyre wrote:
On Wed, Feb 20, 2019 at 06:28:05PM +, Jonathan Wiltshire wrote:
Hi,
Please indicate your availablility out of:
- April 13
- April 20 (Easter weekend)
I'm away on holiday for both of these, I'm afraid, and so is chief CD
tester Andy.
- April
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.
> > >
Hi,
The next point release for "stretch" (9.9) is scheduled for Saturday,
April 27th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
> > > * Rebuild the debian-installer images, pulling in updates from
> > > stretch-updates, leaving only armhf netboot targets broken.
> >
> > Expanding a bit: rebuilding
On Thu, 2017-11-30 at 20:17 +0100, Christoph Biedl wrote:
> Second attempt, updated debdiff attached.
>
> Changes:
>
> also address:
>
> + * Fix integer overflow in bzip2 decompresson.
> +Closes: #879732 [CVE-2017-15873]
> + * Filter out terminal escape sequence filtering in
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:
> > > > >
On Fri, 2019-01-18 at 18:44 +, Jonathan Wiltshire wrote:
> 9.7 is a bit overdue already (current events being a bit of a time-
> sink).
>
> Please indicate your availablility out of:
>
> - (Feb 2 unlikely, FOSDEM)
> - Feb 9
> - Feb 16
As we had a short-notice 9.7, this is now planning
Hi,
The next point release for "stretch" (9.8) is scheduled for Saturday,
February 16th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Sun, 2019-07-14 at 19:35 +0100, Jonathan Wiltshire wrote:
> So, the first point release for buster would normally be about a
> month after release, or something like 3rd August. But I'm aware that
> already doesn't work for some people, so we might have to get a bit
> creative with it.
>
>
Control: tags -1 + confirmed d-i
On Wed, 2019-08-07 at 18:01 +0200, Sven Joachim wrote:
> I have just uploaded ncurses 6.1+20181013-2+deb10u1 to Buster which
> contains a one-line fix for bug #933053[1], the same as in version
> 6.1+20190713-2 which is now in testing.
>
> Some background: for
Control: tags -1 + confirmed d-i
On Sat, 2019-08-17 at 11:03 +0200, Guilhem Moulin wrote:
> Buster's cryptsetup (2:2.1.0-5) doesn't cope well with LUKS2 headers
> without any bound keyslot: adding a new key slot to such a header
> fails, both via the crypt_keyslot_add_by_volume_key() API call and
Control: tags -1 + confirmed d-i
On Fri, 2019-08-16 at 18:04 +1000, Hugh McMaster wrote:
> On Sun, 4 Aug 2019 at 11:13 am, Hugh McMaster wrote:
> > Control: retitle -1 stretch-pu: package freetype/2.6.3-3.2+deb9u1
> >
> > Updated debdiff, now with correct update version.
> >
>
> Just following
Control: tags -1 + confirmed
On 2019-08-14 09:17, Simon McVittie wrote:
glib2.0 in stretch has some minor security vulnerabilities for which
the security team have declined to issue DSAs: the most recent is also
pending review as a buster update (#933535) and the others were already
fixed
Control: tags -1 + confirmed d-i
[full quote for KiBi's benefit]
On 2019-08-21 20:05, Daniel Kahn Gillmor wrote:
On Wed 2019-08-21 18:19:06 +0100, Adam D. Barratt wrote:
* We adopt GnuPG's upstream approach of making keyserver access
default to self-sigs-only. This means
Control: tags -1 + moreinfo
[Recipients changed to use the p-u bug rather than the win32-loader one]
On 2019-08-16 07:55, Didier 'OdyX' Raboud wrote:
Le dimanche, 4 août 2019, 08.43:49 h CEST Yetoo Happy a écrit :
Dear Maintainer,
Checksums need to be updated for new stable release, download
Control: tags -1 + d-i confirmed
On Mon, 2019-08-26 at 19:18 +0200, Guilhem Moulin wrote:
> Another regression was found in cryptsetup :-/ Its scope is quite
> narrow as it only affects mapped device size ≥2TiB (2³² 512-bits
> sectors) on 32-bits platforms. And AFAICT ‘crypt’ targets are not
>
Control: tags -1 -moreinfo +confirmed
On 2019-08-21 09:14, Didier 'OdyX' Raboud wrote:
Le mardi, 20 août 2019, 16.55:47 h CEST Adam D. Barratt a écrit :
Control: tags -1 + moreinfo
[Recipients changed to use the p-u bug rather than the win32-loader
one]
On 2019-08-16 07:55, Didier 'OdyX
Hi,
The first point release for "buster" (10.1) is scheduled for Saturday,
September 7th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.10) is scheduled for Saturday,
September 7th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + confirmed
On Wed, 2019-07-31 at 11:13 +0100, Simon McVittie wrote:
> GLib in buster is vulnerable to CVE-2019-13012 (configuration files
> and directories created with more open permissions than intended),
> which the security team have indicated is too minor for a DSA.
>
Control: tags -1 + confirmed d-i
On Sun, 2019-07-21 at 20:52 +0200, Michael Biebl wrote:
> I'd like to make a stable upload for stretch.
>
> It fixes an issue in networkd, which is not enabled by default, but
> apparently sees increased usage, so it seems worthwile fixing it, as
> it can result
Control: tags -1 + confirmed d-i
On 2019-06-12 08:29, Colin Watson wrote:
I'd like to upload an update to stretch's grub2 which adds support for
booting Xen on UEFI hosts. This consists of four straight cherry-picks
from upstream (somewhat complex, but mostly confined to the multiboot
loader
Control: tags -1 + confirmed d-i
On 2019-07-24 10:45, Hugh McMaster wrote:
Package: release.debian.org
Severity: normal
Tags: patch
Please either set the metadata appropriately here to indicate a stable
update, or use reportbug which will do it for you. (In this case,
someone already
Control: tags -1 + confirmed d-i
On 2019-07-16 06:36, Moritz Muehlenhoff wrote:
This update for OpenSSH fixes a dead lock in AuthorizedKeysCommand
(#905226).
The fixed package is running fine on a formerly affected Stretch system
(https://phabricator.wikimedia.org)
This looks OK to me, but
On Wed, 2019-11-06 at 12:08 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On 2019-11-04 19:12, Simon McVittie wrote:
> > A recent security fix to ibus (CVE-2019-14822, #940267, DSA-4525-1)
> > exposed an interoperability bug between GLib's impleme
On Wed, 2019-11-06 at 11:54 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On 2019-11-02 19:10, Sven Joachim wrote:
> > I would like to upload ncurses 6.1+20181013-2+deb10u2 to buster,
> > fixing
> > several bugs in tic's parser which have been re
Control: tags -1 + confirmed d-i
On 2019-11-04 19:12, Simon McVittie wrote:
A recent security fix to ibus (CVE-2019-14822, #940267, DSA-4525-1)
exposed an interoperability bug between GLib's implementation of D-Bus
and the reference implementation libdbus (#941018). The practical
impact
is
Control: tags -1 + confirmed d-i
On 2019-11-02 19:10, Sven Joachim wrote:
I would like to upload ncurses 6.1+20181013-2+deb10u2 to buster, fixing
several bugs in tic's parser which have been reported last month. Two
of them are heap buffer overflows that have been assigned CVE numbers
and a
Hi,
The next point release for "buster" (10.2) is scheduled for Saturday,
November 16th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + confirmed d-i
On Mon, 2019-12-02 at 15:24 +, Simon McVittie wrote:
> On Wed, 06 Nov 2019 at 13:01:41 +, Simon McVittie wrote:
> > A recent security fix to ibus (CVE-2019-14822, #940267, DSA-4525-1)
> > exposed an interoperability bug between GLib's implementation of D-
Hi,
It's (really past) time to consider a date for the second buster point
release.
I've listed some suggested dates below; please indicate which you would
be available for.
- November 2nd
- I'm not available; also means that the freeze would have to be this
coming weekend
- November 9th
-
Control: tags -1 + confirmed d-i
On Wed, 2019-10-16 at 17:18 +0200, Michael Biebl wrote:
> I'd like to make a stable upload for systemd, fixing various issues,
> including a CVE.
>
Looks good to me; making the d-i status explicit.
Regards,
Adam
Control: tags -1 + confirmed d-i
On Wed, 2020-01-29 at 19:24 +0100, Michael Biebl wrote:
> systemd (241-7~deb10u3) buster; urgency=medium
>
> * core: set fs.file-max sysctl to LONG_MAX rather than ULONG_MAX.
> Since kernel 5.2 (but also stable kernels like 4.19.53) the
> kernel thankfully
On Sat, 2020-01-18 at 19:49 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On Sun, 2020-01-12 at 00:24 +, Colin Watson wrote:
> > https://bugs.debian.org/946242 reports an OpenSSH regression on old
> > kernels on certain architectures
Hi Holger,
On Sun, 2020-02-23 at 10:23 +0100, Holger Wansing wrote:
> we would like to change the font used for Korean PDF (once again),
> which would need an additional package (fonts-noto-cjk) to be
> installed on the relevant machines (dillon and wolkenstein).
>
> A 'git format-patch' patch
On Thu, 2020-01-09 at 14:24 +0100, Laura Arjona Reina wrote:
> So, please count my ACK to apply the patch adding fonts-nanum and
> fonts-nanum-coding.
Thanks:
The following NEW packages will be installed:
fonts-nanum fonts-nanum-coding
The following packages will be upgraded:
Hi,
The next point release for "stretch" (9.12) is scheduled for Saturday,
February 8th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.3) is scheduled for Saturday,
February 8th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + confirmed d-i
On Sun, 2020-01-12 at 00:24 +, Colin Watson wrote:
> https://bugs.debian.org/946242 reports an OpenSSH regression on old
> kernels on certain architectures (e.g. i386) prompted by the
> interaction between an OpenSSL update and a seccomp filter. It's
>
Control: tags -1 + confirmed d-i
On Thu, 2020-01-09 at 22:34 -0500, Theodore Y. Ts'o wrote:
> +e2fsprogs (1.44.5-1+deb10u3) buster; urgency=medium
> +
> + * Fix CVE-2019-5188: potential stack underflow in e2fsck (Closes:
> #948508)
> + * Fix use after free in e2fsck (Closes: #948517)
>
This
Control: tags -1 + confirmed d-i
On Mon, 2020-01-20 at 10:02 +0100, Andrej Shadura wrote:
> wpa (2:2.4-1+deb9u5) stretch; urgency=medium
> .
>* SECURITY UPDATE:
> - AP mode PMF disconnection protection bypass.
>More details:
> + https://w1.fi/security/2019-7/
>
On Sun, 2020-01-12 at 18:38 +0100, Holger Wansing wrote:
> A new build has taken place, however on the website we still have a
> mixup of old and newer files, and still no example-preseed.txt.
> While in the lessoften log it looks fine.
> No installmanual build available to me tough...
The file
On Wed, 2020-01-01 at 19:52 +0100, Holger Wansing wrote:
> Hi,
>
> Laura Arjona Reina wrote:
> > Hi
> >
> > The cron job will do the 'git pull' on wolkenstein the next time it
> > runs.
>
> yes, that worked, thanks.
> So, the build was performed via the new script, and thanks to that we
> now
On Sat, 2020-01-04 at 15:44 +0100, Holger Wansing wrote:
> Hi,
>
> Huh?
> I'm totally confused. See below...
>
> "Adam D. Barratt" wrote:
> > On Wed, 2020-01-01 at 19:52 +0100, Holger Wansing wrote:
> > > Hi,
> > >
> > > Laura
Hi,
It's (really past) time to consider a date for the next point releases
for buster and stretch.
I've listed some suggested dates below; please indicate which you would
be available for.
- January 25th
- February 1st
- February 8th
- February 15th
Thanks,
Adam
On Sun, 2020-01-05 at 17:46 +0100, Holger Wansing wrote:
> Hi,
>
> Holger Wansing wrote:
[...]
> > We could ask DSA to install 'fonts-nanum' and 'fonts-nanum-coding'
> > at wolkenstein,
> > to get that build successful again.
> > Would that be an option?
>
> Patch (from git format-patch) again
Hi,
The next point release for "buster" (10.4) is scheduled for Saturday,
May 9th. Processing of new uploads into buster-proposed-updates will be
frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + confirmed d-i
On Mon, 2020-03-23 at 00:30 +0100, Samuel Thibault wrote:
> I would like to upload the attached changes to buster, they are
> already in buster-p-u.
Well, no, they're in stable-new. :)
> The story is that Orca was recently enhanced to support Braille
> device
Hi folks,
I realise things are a little unusual right now, but it's about time
that we started looking at dates for 10.4.
I guess the biggest impact of current circumstances on the process is
likely to be around image testing, as there won't be a bunch of people
with local access to Steve's
Control: tags -1 + confirmed
On Thu, 2019-12-26 at 21:43 +, Simon McVittie wrote:
> We've been asked to fix a crash bug (#898960) in buster. Would you
> be willing to consider a direct backport of 1.42.4-8 when it has had
> some more time in unstable? In addition to a simple crash fix, it
>
Control: tags -1 + confirmed d-i
On Tue, 2020-03-24 at 11:33 +0100, Andrej Shadura wrote:
> I’m proposing to upload a couple of upstream patches improving Wi-Fi
> connectivity in some cases especially on certain hardware.
>
> For two of them, the relevant issues are #942164 and LP: #1867908.
>
Control: tags -1 + confirmed d-i
On Wed, 2020-04-08 at 16:11 +0200, Michael Biebl wrote:
> I'd like to make a stable/buster upload for systemd fixing CVE-2020-
> 1712
> https://security-tracker.debian.org/tracker/CVE-2020-1712
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950732
>
> After
Control: tags -1 + d-i
On Sat, 2020-04-25 at 19:17 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Wed, 2020-04-22 at 22:56 +0200, László Böszörményi wrote:
> > There are two RC bugs fixed in fuse3 for Bullseye but not yet for
> > Buster.
>
Control: tags -1 + d-i
On Sat, 2020-04-25 at 19:16 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Wed, 2020-04-22 at 22:56 +0200, László Böszörményi wrote:
> > There are two RC bugs fixed in fuse for Bullseye but not yet for
> > Buster.
> > Fir
On Mon, 2020-04-27 at 22:41 +0100, Adam D. Barratt wrote:
> On Mon, 2020-04-27 at 19:17 +0200, Michael Biebl wrote:
> > Am 25.04.20 um 21:41 schrieb Adam D. Barratt:
> > > On Wed, 2020-04-08 at 16:11 +0200, Michael Biebl wrote:
> > > I'd be OK with that, but this wil
On Mon, 2020-04-27 at 19:17 +0200, Michael Biebl wrote:
> Am 25.04.20 um 21:41 schrieb Adam D. Barratt:
> > On Wed, 2020-04-08 at 16:11 +0200, Michael Biebl wrote:
> > I'd be OK with that, but this will need a KiBi-ack, so CCing and
> > tagging accordingly.
>
> After
On Sat, 2020-05-02 at 18:36 +0200, Sebastian Andrzej Siewior wrote:
> I'm fairly late, I know.
Just a little. :-( Particularly as OpenSSL builds udebs.
CCing KiBi and -boot so they're aware of the discussion, but this does
come quite late.
> The last update was addressed via DSA providing only
On Sat, 2020-05-02 at 22:29 +0200, Sebastian Andrzej Siewior wrote:
> On 2020-05-02 20:32:01 [+0100], Adam D. Barratt wrote:
> > On Sat, 2020-05-02 at 18:36 +0200, Sebastian Andrzej Siewior wrote:
> > > I'm fairly late, I know.
> >
> > Just a little. :-( Partic
On Sat, 2020-04-25 at 20:17 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On Tue, 2020-03-24 at 11:33 +0100, Andrej Shadura wrote:
> > I’m proposing to upload a couple of upstream patches improving Wi-
> > Fi
> > connectivity in some cases esp
On Sun, 2020-02-02 at 17:38 +0100, Cyril Brulebois wrote:
> Trying to build the binaries to get that tested in a d-i environment,
> I
> ended up with a build failure:
[...]
> >
../src/ap/drv_callbacks.o: In function `hostapd_notif_assoc':
> > ./wpa_supplicant/../src/ap/drv_callbacks.c:66:
301 - 400 of 522 matches
Mail list logo
