Hi,
On Thu, 2024-08-22 at 21:39 +0100, Adam D. Barratt wrote:
> I've also prepared 2.111+deb11u1, but not yet uploaded it as the
> debdiff ends up as:
>
> Mirrors.
Hi,
On Wed, 2024-08-14 at 22:15 +0200, Cyril Brulebois wrote:
> Hi Adam,
>
> Adam D. Barratt (2024-08-14):
>
[...]
> > I'd like to suggest that we get in the habit of updating the
> > choose-mirror package more often, in order to provide a more
> > cur
Control: tags -1 + confirmed
On Tue, 2024-07-23 at 22:50 +0200, Aurelien Jarno wrote:
> [ Reason ]
> The upstream glibc stable branch got a fixes since the last stable
> updates. This hasn't been missed in the last point release, so the
> number of fixes is slightly higher than usual.
Please go a
Hi,
choose-mirror is the d-i component responsible for presenting users
with a list of available mirrors from which packages can be installed.
The list it provides is periodically updated based on the "masterlist"
maintained by the Mirrors Team.
I'd like to suggest that we get
Chris Hofstaedtler writes:
> On Tue, Apr 30, 2024 at 12:16:23AM +0200, Håvard F. Aasen wrote:
>> Could default home folder permissions lean towards greater privacy,
>> while administrators can adjust permissions to be less strict if
>> necessary?
Isn't it worth noting that normal users can adjus
On Mon, 2024-06-24 at 21:55 +0200, Cyril Brulebois wrote:
> Cyril Brulebois (2024-06-24):
> > I'm not seeing this with netboot's mini.iso, so usual suspects
> > would
> > be the GTK stack, the X stack, and the kernel.
>
> Instead: Have you tried turning kibi off and on again?
>
> Sorry for the P
ut of the shadows anyway, but what a terrible user experience… we
> *might* be able to accept (and document) the regression, but I would
> prefer *not* to do that…
Bah. :-(
> Adam, what timeframe are you comfortable with, to give me some time
> to figure that out? (i.e. d-i/bullseye mus
On Thu, 2024-06-20 at 22:35 +0100, Jonathan Wiltshire wrote:
> - Saturday 17th August: this would mean freezing on the 10th, before
> security support ends, so the security team's cooperation in
> keeping non-critical DSAs off the table during the freeze period
> would be required
>
> - Satur
Control: severity -1 normal
Control: tags -1 + confirmed
On Tue, 2024-04-30 at 23:31 +, Bastien Roucariès wrote:
> [ Reason ]
> CVE-2023-52160 security bug
Please go ahead.
Regards,
Adam
Control: severity -1 normal
On Tue, 2024-04-30 at 23:03 +, Bastien Roucariès wrote:
> Package: release.debian.org
> Severity: important
>
p-u requests are always "normal"; fixed.
> [ Reason ]
> CVE-2023-52160 security bug
Please go ahead.
Regards,
Adam
press@ - please could you comment on the dates proposed below
Thanks,
Adam
On Mon, 2024-05-27 at 13:07 +0100, Jonathan Wiltshire wrote:
> Hi,
>
> The final bullseye point release 11.10 (and therefore also 12.6 for
> versioning) should be soon after 10th June, when security team
> support
> will
On Mon, 2024-05-27 at 13:07 +0100, Jonathan Wiltshire wrote:
> The final bullseye point release 11.10 (and therefore also 12.6 for
> versioning) should be soon after 10th June, when security team
> support
> will end.
>
> Please indicate availability for:
>
> Saturday 15th June
> Saturday 22n
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 m
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 be
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
is round though
> > :)
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055908
>
> I was trying to suggest filing both in the same request, to have them
> scheduled in one go.
Yes, please. #1055908 also doesn't mention the dependency between the
binNMUs.
> In any case, actually binNMUing both packages would be nice, as we've
> been lacking d-i daily builds for some days already.
Done.
Regards,
Adam
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 texlive
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 bookworm
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
Jonathan Hettwer writes:
> Package: partman-crypto
> Version: 121
> Severity: normal
> Tags: d-i
> X-Debbugs-Cc: j24...@gmail.com
>
> Dear Maintainer,
>
> The `crypto_check_mountpoints` script prevents you from setting up an
> encrypted root filesystem without a
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 Win
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
4812.
>
> Local changes in dillon include:
> - mailing kibi@d.o instead of debian-boot@, because debugging and
> other
>annoyances listed as d-i.debian.org bug reports; I don't want more
>junk to be sent to the list.
> - hardcoded paths in an additional $ua->ssl_o
r that.
>
> Yep, now it boots successfully :D
Are you still able to reproduce the state where Debian is successfully
installed to a btrfs rootfs, but where btrfs-progs is not installed?
From what I can tell, that is the nature of this [by now most likely
historical] bug.
Regards,
Nicholas
signature.asc
Description: PGP signature
Dimitri John Ledkov writes:
> On 6 August 2014 03:46, Russell Coker wrote:
>> Package: debian-installer
>> Severity: normal
>>
>> http://www.spinics.net/lists/linux-btrfs/msg36461.html
>>
>> BTRFS has some issues that can cause system lockups, filesystem deadlocks
>> that
>> prevent writing to
P.S.
> Dimitri John Ledkov writes:
>
>> On 6 August 2014 03:46, Russell Coker wrote:
snip
>>> be that we should have a warning. BTRFS isn't at the stage where someone
>>> with
>>> little knowledge of it can just use it. To have it work reliably the
>>> sysadmin
>>> needs to know more about
t;btrfs subvolume
> set-default ..." to it. Don't ask me why I did. But this caused d-i
> to stop installation without much error report.
>
Agreed, silent failure is a major problem.
> EXPECTED BEHAVIOR:
>
> 1. Clearly mention the use of subvolume @rootfs in d-i dialog
Dear Leslie,
I'm sorry no one noticed your bug. Reply follows inline:
Jeremy, thank you for following up on this bug! This brought the bug to
my attention :)
Leslie Rhorer writes:
> On 7/13/2023 5:18 PM, Jeremy Davis wrote:
>> [Just a random passer-by that might have an idea?]
>>
>> It looks
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
>fu
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 stret
leaves finding a date (and me learning what to do :) ).
>
> We have (if earlier mentioned dates still work for those involved):
> May | June
> > kibi - 13, 20, 27 d-i
> > mhy - 13, 20, 27 ftp
&
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 implementatio
Hi James,
James Abernathy writes:
> I reran an install but this time when I remounted the @ and @home
> subvolumes I only used the default, compress=zstd, and subvol= options.
>
Thank you.
> This time it worked. After booting successfully, I edited fstab to add in
> noatime and it still worked
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 confi
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
> soon)
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 t
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
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 d
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:
- Decembe
Pascal Hambourg writes:
> On 03/09/2022 at 06:32, Philip Hands wrote:
>> Ansgar writes:
>>
[snip]
>>>
>>> However, mounting the root filesystem failed: /target contained only a
>>> "@rootfs" subdirectory. So running a shell in the target fs failed.
>>> Manually mounting the filesystem with `-o su
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 su
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 n
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
>
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 couple
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 look
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_op
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 Mall
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 you would
>
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
On Thu, 2022-03-17 at 19:29 -0400, Daniel Kahn Gillmor wrote:
> On Thu 2022-03-17 17:49:04 +, 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 +, 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
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 breaka
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 +, 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/n
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
> app
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
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 espe
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.
> >
>
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 accide
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 wor
urg wrote:
>>>Le 03/12/2021 à 22:08, Nicholas D Steeves a écrit :
>>>>
>>>>
>>>> c) parse /target/etc/fstab, and attempt to mount other partitions
>>>
>>>The rescue system already offers to do it for separate /boot and /boot/efi,
&
lation.
2. Reassign to src:rescue, and fix the rescue system.
a) before chrooting, test for the presence of /target/bin/sh
b) if /bin/sh is not found, either emit error to the user and present a
dialogue for selecting /usr partition, or
c) parse /target/etc/fstab, and attempt to mount oth
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'
Control: tag -1 + moreinfo
Hi Steve,
I've written my reply assuming this isn't a usermerged system, because
if it is one, then I wonder if this is a usrmerge-related bug. Ie: I
wonder if a splitting / and /usr onto different partitions is never
supported on usrmerged systems. Alternatively, may
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 su
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 wo
Holger Wansing writes:
> Hi,
>
> David wrote (Sat, 9 Oct 2021 21:56:24 +1100):
>> I see that the suggestion to use 'cat' comes
>> from #604839.
>>
>> Yes, 'cat' will "work", however I feel there is no
>> good reason to use 'cat' there.
>>
>> Because the purpose of 'cat' is for concatenating
>>
"Andrew M.A. Cater" writes:
> As mentioned on debian-user: the debian-11.1.0-amd64-netinst.iso or the
> debian-11.1.0-amd-DVD-1.iso are the appropriate ones to use.
>
> The debian-mac images are for a couple of specific models from 2008/2009
> which had problems recognising El Torito images.
>
O
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
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,
1 - 100 of 708 matches
Mail list logo
