Your message dated Sat, 11 May 2024 11:20:22 +0200
with message-id <3ee6f845-bcb8-4c4f-859a-e7ce46bfe...@mailbox.org>
and subject line Re: d-i.debian.org: PO spellchecking broken
has caused the Debian Bug report #783950,
regarding d-i.debian.org: PO spellchecking broken
to be marked a
Hi,
Cyril Brulebois (2024-03-12):
> Your NMU broke this package's shlibs.
>
> Before:
>
> libmtdev 1 libmtdev1
> udeb: libmtdev 1 libmtdev1-udeb
>
> After:
>
> libmtdev 1 libmtdev1t64
>
> At the moment, at least the following package is bro
Your message dated Tue, 19 Mar 2024 12:31:36 +0100
with message-id <20240319113136.w3x36ynyk4jjv...@shell.thinkmo.de>
and subject line Re: Bug#923091: base-installer: Allow installing w/o the
broken merged-usr-via-symlinks
has caused the Debian Bug report #923091,
regarding base-installer:
Source: ntfs-3g
Version: 1:2022.10.3-1.1
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-boot@lists.debian.org, Benjamin Drung
Hi,
Here's what debian/libntfs-3g89t64/DEBIAN/shlibs looks like after
a build:
libntfs-3g 89 libntfs-3g89
udeb: libntfs-3g 89
Source: mtdev
Version: 1.1.6-1.1
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-boot@lists.debian.org, Benjamin Drung
Hi,
Your NMU broke this package's shlibs.
Before:
libmtdev 1 libmtdev1
udeb: libmtdev 1 libmtdev1-udeb
After:
libmtdev 1
variant=fakechroot still fails in testing, but it apparently fails in a
different way. (Do I need a new bug report?)
`fakeroot fakechroot debootstrap --variant=fakechroot testing testing`
fails.
Whereas `fakeroot fakechroot debootstrap --variant=minbase testing
testing` succeeds.
But at
(sorry, accidental Ctrl+Enter...)
With Bookworm, it totally broke.
If the preseeding happens after netcfg (url=...), when setting the
hostname from the kernel parameters, d-i keeps it, but does not get the
domain from DHCP as before; only setting both a hostname and a domain
name makes
Dear developers,
I confirm that something broke between Bullseye and Bookworm (IIRC it
worked even with Bookworm RC2) regarding netcfg's behavior when the
host's IP address can't be found in the DNS.
I also think it's a different bug from the one originally reported
(which were for Jessie).
Hello.
I just tried with bookworm net installer and things changed since
bullseye.
On a bullseye, netcfg use the domain returned by DHCP which is not the
case on bookworm.
I think that the rDNS check before using the DHCP domain should be
removed.
It looks like on bullseye, domain was
Control: tag -1 - patch
Hi,
Thanks for the proposed patch but as discussed elsewhere it seemed too
risky to force 32 bpp on everyone, so I went for what looked like the
least risky (adding bochs.ko and cirrus.ko, manually and for the time
being).
Ben Hutchings (2023-05-14):
> I think the
Processing control commands:
> tag -1 - patch
Bug #1036019 [debian-installer] debian-installer: Broken X display with QEMU
under UEFI with cirrus and std graphics
Removed tag(s) patch.
--
1036019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036019
Debian Bug Tracking System
Contact
On Sun, 2023-05-14 at 19:40 +0200, Ben Hutchings wrote:
[...]
> This works for me with all the QEMU graphics devices. But I haven't
> tested on real hardware.
Now tested successfully on 2 custom desktops:
- Asus P8Z68-V LX motherboard, Intel Core i5 2500 CPU, integrated GPU
- ASRock B450 PRO4,
Control: tag -1 patch
On Sun, 2023-05-14 at 00:21 +0200, Ben Hutchings wrote:
[...]
> So I suppose there's a regression in either efifb or fbdev_drv.
I'm not spotting any functional changes in fbdev or the submodules it
depends on between bullseye and bookworm. So this implicates either
efifb
Processing control commands:
> tag -1 patch
Bug #1036019 [debian-installer] debian-installer: Broken X display with QEMU
under UEFI with cirrus and std graphics
Added tag(s) patch.
--
1036019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036019
Debian Bug Tracking System
Contact
Cyril Brulebois (2023-05-14):
> Also, I should note that while my focus was on netboot-gtk mini.iso
> (because it's much quicker to rebuild/tweak than a netinst image), I'm
> replicating those results with the netinst images:
[…]
> - Bookworm RC 1 has a “text-like” GRUB, all good.
> - Bookworm
Hi Ben,
Thanks for all those details!
Ben Hutchings (2023-05-14):
> >
> > +-+-+-+-+
> > | Graphics | Bullseye 11.7 | Bookworm RC 2 | Daily builds |
> >
On Sat, 2023-05-13 at 10:22 +0200, Cyril Brulebois wrote:
[...]
> Kernel-side
> ===
>
> The fb-modules udeb hasn't changed much since 4+ years, with some DRM
> modules getting added alongside existing ones, leading to the following
> contents in Bullseye (5.10.178-3):
[...]
> Those
by regular image testers to the following page:
https://wiki.debian.org/SecureBoot/VirtualMachine
But I was a little shocked to discover a broken X display when booting
under UEFI! It seems I'm not the only one since that page has the
following, even if there are no references to any bug reports
The last few debian releases (buster and bullseye at least) configuring
encrypted swap has been broken for me. I don't know if it's the same as
what the user in #792456 is seeing, but likely.
I have most recently tested it in Bookworm RC1 and here is what I did:
* run by hand partitioning
On Fri, 21 Apr 2023 at 12:25:29 +0200, Guilhem Moulin wrote:
> Bookworm (debian-bookworm-DI-rc1-amd64-netinst.iso + cryptsetup
> 2:2.6.1-4~deb12u1,
> graphical install), 1024M RAM:
>
> root@debian:~# cryptsetup luksDump /dev/vda5 | grep -A3 PBKDF
> PBKDF: argon2id
>
On Fri, 21 Apr 2023 at 13:02:24 +0200, Cyril Brulebois wrote:
> Summing up some out-of-band brainstorming about what “a bit crippled”
> means, it might just be libargon2-1-udeb's being built without pthread
> support:
>
>
Guilhem Moulin (2023-04-21):
> Just uploaded 2:2.6.1-4 to sid, and locally prepared a rebuild for
> bookworm (2:2.6.1-4~deb12u1).
\o/
> Bottom line:
>
> * The upstream patches in the patch-queue (the 2 backported earlier
>from upstream MR !490 plus the new other two from upstream MR !498)
Hi,
On Thu, 20 Apr 2023 at 20:02:27 +0200, Cyril Brulebois wrote:
>> * Backport upstream MR !498, let it mature in sid for a few
>> weeks then upload 2:2.6.1-4~deb12u1 via t-p-u. There are only 2
>> upstream commits to cherry-pick and neither is large nor intrusive;
>> moreover like the commits
Hi,
(Letting Paul and the bug report know about our little chat.)
Guilhem Moulin (2023-04-20):
> AFAICT the issue is now fully fixed upstream: on systems without swap
> the memory cost won't exceed half the amount of free memory during
> PBKDF benchmarking.
As a reminder: the “no swap” case
Hi kibi,
On Sat, 01 Apr 2023 at 01:34:54 +0200, Guilhem Moulin wrote:
> Ah right, reopened the upstream issue but forgot to follow-up here :-(
> https://gitlab.com/cryptsetup/cryptsetup/-/issues/802#note_1328592911
AFAICT the issue is now fully fixed upstream: on systems without swap
the memory
Your message dated Thu, 13 Apr 2023 13:03:56 +
with message-id
and subject line Bug#1033913: fixed in partman-efi 99
has caused the Debian Bug report #1033913,
regarding partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in
UEFI mode
to be marked as done.
This mean
I've just pushed an update to the code here...
On Mon, Apr 10, 2023 at 05:45:15PM +0200, Pascal Hambourg wrote:
>On 10/04/2023 at 15:13, Steve McIntyre wrote:
>>
>> Overall comment: I'm not trying to make the heuristics 100% reliable
>> here, as I don't think that's actually possible. Instead,
On 10/04/2023 at 15:13, Steve McIntyre wrote:
Overall comment: I'm not trying to make the heuristics 100% reliable
here, as I don't think that's actually possible. Instead, I'm trying
to tread the fine line of:
* minimising false negatives - let's try to pick up on the most
common cases
Hey Pascal, and thanks for the review!
Overall comment: I'm not trying to make the heuristics 100% reliable
here, as I don't think that's actually possible. Instead, I'm trying
to tread the fine line of:
* minimising false negatives - let's try to pick up on the most
common cases where
partman-efi "Fix detection of BIOS-bootable systems" provides a
significant improvement over previous behaviour. However I have a few
comments.
1a) The patch assumes that a GPT disk may be BIOS-bootable only if it
has a BIOS boot partition. But a GPT disk can be BIOS-bootable even
without a
Hello,
On 03/04/2023 at 21:50, Cyril Brulebois wrote:
- It very much looks like the intermediary states are slightly
different when setting up LVM and when setting up encrypted LVM, and
the LVM case case leads to some confusion in partman-efi's
/lib/partman/init.d/50efi (which
Package: partman-auto-lvm
Version: 87
Severity: serious
Justification: Maintainer says so
TL;DR: Answering “Yes” to the “Force UEFI installation?” makes sure the
installer pulls the right bootloader packages, despite misreading the
situation.
I've discovered this while testing D-I Bookworm RC 1
Hi kibi,
On Sat, 01 Apr 2023 at 00:36:35 +0200, Cyril Brulebois wrote:
> Cyril Brulebois (2023-03-26):
>> I'm happy to have the patches included, and I can definitely live with
>> possible temporary regressions (should that happen) that might arise
>> from having them.
>
> Pre-upload testing
Hi again,
Cyril Brulebois (2023-03-26):
> I'm happy to have the patches included, and I can definitely live with
> possible temporary regressions (should that happen) that might arise
> from having them.
Pre-upload testing shows that the situation seems unchanged with
2:2.6.1-3~deb12u1:
Hi Guilhem,
Guilhem Moulin (2023-03-26):
> In https://bugs.debian.org/1032235#107 elbrus (CC'ed) asked for a t-p-u
> upload of cryptsetup to fix a potential major regression should
> bookworm's src:argon2 ever be rebuilt with the bookworm toolchain. The
> version currently in sid, 2:2.6.1-3,
Hi kibi,
In https://bugs.debian.org/1032235#107 elbrus (CC'ed) asked for a t-p-u
upload of cryptsetup to fix a potential major regression should
bookworm's src:argon2 ever be rebuilt with the bookworm toolchain. The
version currently in sid, 2:2.6.1-3, also includes 2 upstream patches to
Package: installation-reports
(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)
Boot method: USB
Image version:
https://cdimage.debian.org/cdimage/bookworm_di_alpha2/amd64/iso-cd/
Control: retitle -1 cryptsetup might OOMK on low memory systems
Hi Guilhem,
Guilhem Moulin (2023-02-18):
> By default the PBKDF benchmark caps the memory cost at 1GiB or half of
> the physical memory, whichever is smaller. So indeed with 1G RAM and
> ~50% free one might trigger the OOM killer.
Processing control commands:
> retitle -1 cryptsetup might OOMK on low memory systems
Bug #1028250 [debian-installer] debian-installer: broken cryptsetup support
Changed Bug title to 'cryptsetup might OOMK on low memory systems' from
'debian-installer: broken cryptsetup support'.
--
1028
X-Debbugs-Cc: pkg-cryptsetup-de...@alioth-lists.debian.net
Hi kibi!
On Thu, 16 Feb 2023 at 20:14:20 +0100, Cyril Brulebois wrote:
> Cyril Brulebois (2023-01-09):
>> Cyril Brulebois (2023-01-08):
>>> I'm seeing at least two problems with cryptsetup while testing daily
>>> builds:
>>> - with
Subject: Bug#1028250: debian-installer: broken cryptsetup support
cc += cryptsetup maintainers (hi, long time no see!)
Cyril Brulebois (2023-01-09):
> Cyril Brulebois (2023-01-08):
> > I'm seeing at least two problems with cryptsetup while testing daily
> > builds:
> >
cc += cryptsetup maintainers (hi, long time no see!)
Cyril Brulebois (2023-01-09):
> Cyril Brulebois (2023-01-08):
> > I'm seeing at least two problems with cryptsetup while testing daily
> > builds:
> > - with 6.1.0-1 (currently getting into the archive), my very usual 1G
> >RAM / 5G
Your message dated Tue, 24 Jan 2023 18:21:00 +
with message-id
and subject line Bug#1029352: fixed in netcfg 1.182
has caused the Debian Bug report #1029352,
regarding netcfg: broken ifupdown support for wireless interfaces
to be marked as done.
This means that you claim that the problem has
pose we can postpone wondering what to do about hotplug support
(netcfg currently believes everything is hotpluggable…) to a later time
(after bookworkm) given the broken “allow-hotplug” support at boot-up
(third issue) was an ifupdown regression in the end: #1022843.
My current plan includes more
Processing control commands:
> tag -1 pending
Bug #1029352 [netcfg] netcfg: broken ifupdown support for wireless interfaces
Added tag(s) pending.
--
1029352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
from a simple user: I hate so say, but IMO ifupdown and/or
/etc/network/interfaces format is broken by design. Stanzas mix link
layer and network layer parameters and this causes various issues when
you have several stanzas for the same interface. Link layer parameters
should be applied once per inter
Similar Trouble here:
A smoothly running Debian-Bookworm system here with ethernet eno1 managed by
ifupdown, wlp1s0 is managed by NetworkManager.
After today's bigger Update consisting of:
qttranslations5-l10n:amd64 (5.15.7-2, 5.15.8-2), qtbase5-dev-tools:amd64
(5.15.7+dfsg-2,
Package: netcfg
Severity: serious
Tags: patch
Justification: no networking after installation
X-Debbugs-Cc: ifupd...@packages.debian.org, w...@packages.debian.org
Hi,
I'm putting both ifupdown and wpa maintainers in the loop since I'd like
to get some feedback of the proposed resolution for this
Processing control commands:
> severity -1 important
Bug #1028250 [debian-installer] debian-installer: broken cryptsetup support
Severity set to 'important' from 'serious'
--
1028250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028250
Debian Bug Tracking System
Contact
Control: severity -1 important
Cyril Brulebois (2023-01-08):
> I'm seeing at least two problems with cryptsetup while testing daily
> builds:
> - with 6.1.0-1 (currently getting into the archive), my very usual 1G
>RAM / 5G storage setup can no longer get an automated encrypted LVM
>
Package: debian-installer
Severity: serious
Justification: not releasable
Hi,
I'm seeing at least two problems with cryptsetup while testing daily
builds:
- with 6.1.0-1 (currently getting into the archive), my very usual 1G
RAM / 5G storage setup can no longer get an automated encrypted LVM
/regulatory.db (regulatory.db) in auto mode
update-alternatives: warning: not replacing /lib/firmware/regulatory.db with a
link
update-alternatives: warning: forcing reinstallation of alternative
/lib/firmware/regulatory.db-debian because link group regulatory.db is broken
update-alternatives
Julien Cristau (2022-04-25):
> Control: tag -1 upstream patch
> Control: forwarded -1
> https://gitlab.freedesktop.org/xorg/app/setxkbmap/-/merge_requests/4
>
> On Mon, Apr 25, 2022 at 03:44:59PM +0200, Cyril Brulebois wrote:
> > And thanks again for the quick turnaround for the libxrandr2 udeb
Package: x11-xkb-utils-udeb
Version: 7.7+6+b1
Severity: serious
Tags: d-i
Justification: breaks graphical installer
X-Debbugs-Cc: debian-boot@lists.debian.org
Hi X people,
And thanks again for the quick turnaround for the libxrandr2 udeb
addition. The next issue is is_xwayland() erroring out at
Hi Scott,
Scott (2021-11-19):
> I have a feeling that non-free firmware inclusion is not working in
> simple-cdd on Bullseye.
kibi@tokyo:~$ apt-cache show simple-cdd
…
Maintainer: Simple-CDD Developers
…
Cc-ing accordingly.
> Can anyone confirm that they have a simple-cdd
Hi,
I have a feeling that non-free firmware inclusion is not working in
simple-cdd on Bullseye.
Can anyone confirm that they have a simple-cdd project which has been
observed to include non-free firmware in the image when run on Bullseye?
I have a simple-cdd project which includes non-free
Your message dated Tue, 02 Nov 2021 11:33:43 +
with message-id
and subject line Bug#985481: fixed in debootstrap 1.0.125
has caused the Debian Bug report #985481,
regarding debootstrap: Detection of docker container is broken with cgroup v2
to be marked as done.
This means that you claim
Control: retitle -1 FTBFS: uses tempfile in build, appears to use deprecated
which(1)
A closer look indicates that tempfile is only actually used to build the
package. The apparent use of which(1) is actually a shell function, however…
On Wed, Aug 18, 2021, at 16:18, Cyril Brulebois wrote:
> >
Processing control commands:
> retitle -1 FTBFS: uses tempfile in build, appears to use deprecated which(1)
Bug #992457 [console-setup] Broken by removal of tempfile in debianutils
Changed Bug title to 'FTBFS: uses tempfile in build, appears to use deprecated
which(1)' from 'Broken by remo
Joseph Carter (2021-08-18):
> Presumably /installer-team/console-setup would be a better package to
> patch, unless cdebconf uses tempfile somehow. I'll see what I can
> do this evening.
Sure thing, miscompleted in my browser history plus slightly distracted,
sorry.
Cheers,
--
Cyril
On Wed, Aug 18, 2021, at 14:01, Cyril Brulebois wrote:
> T. Joseph Carter (2021-08-18):
> > It's debianutils' bug, really, and the bugs keep getting filed (and
> > resolved), but there's a half a dozen packages on my system that are
> > broken by it. Yours happens to
Control: retitle -1 Broken by removal of tempfile in debianutils
Hi,
T. Joseph Carter (2021-08-18):
> Debianutils >= 5 removes tempname and puts a deprecation notice on the
> which command. The setupcon script (at least) uses both of these,
> causing people's initramfs's to be s
Processing control commands:
> retitle -1 Broken by removal of tempfile in debianutils
Bug #992457 [console-setup] Broken by irresponsible removal of tempfile in
debianutils
Changed Bug title to 'Broken by removal of tempfile in debianutils' from
'Broken by irresponsible removal of tempf
Package: console-setup
Version: 1.205
Severity: important
X-Debbugs-Cc:
Debianutils >= 5 removes tempname and puts a deprecation notice on the
which command. The setupcon script (at least) uses both of these,
causing people's initramfs's to be subtly broken and leaving them
without a key
Your message dated Thu, 29 Jul 2021 20:00:46 +0200
with message-id <8df29295-1dd8-991a-257d-b285ed927...@molgen.mpg.de>
and subject line Re: Bug#991625: debootstrap: extra-suites= broken; attempts
Package.* fetches from primary suite
has caused the Debian Bug report #991625,
regarding deboo
Package: debootstrap
Version: 1.0.123
Severity: important
X-Debbugs-Cc: deb...@iam.tj
Dear Maintainer,
* What led up to the situation?
Attempting to reproduce another bug reported on IRC about Ubuntu and
debootstrap
* What exactly did you do (or not do) that was effective (or
Hello,
Boyuan Yang, le jeu. 06 mai 2021 11:10:41 -0400, a ecrit:
> I received a user report that
> https://www.debian.org/releases/bullseye/amd64/apbs05.en.html#preseed-hooks
> provides an incorrect code example:
>
> # This command is run immediately before the partitioner starts. It may be
> #
Source: installation-guide
Severity: normal
X-Debbugs-CC: sthiba...@debian.org
I received a user report that
https://www.debian.org/releases/bullseye/amd64/apbs05.en.html#preseed-hooks
provides an incorrect code example:
# This command is run immediately before the partitioner starts. It may be
# second-stage in docker, we cannot detect it is
# inside docker... just ignore warning
in_target mount -t sysfs sysfs /sys || true
umount_on_exit /sys
fi
At this point, it seems to me that applying this patch would not change
things dramatically.
There would be a c
Hey Arnaud, thanks for the CC (and sorry for the delay).
On Mon, 12 Apr 2021 at 20:48, Arnaud Rebillout wrote:
> > Originally, ".dockerenv" was for transmitting the environment
> > variables of the container across the container boundary -- I would
> > not recommend relying on its existence
Processing control commands:
> affects -1 release-notes
Bug #985481 [debootstrap] debootstrap: Detection of docker container is broken
with cgroup v2
Added indication that 985481 affects release-notes
--
985481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985481
Debian Bug Track
Control: affects -1 release-notes
Hi Arnaud!
Adding src:docker.io maintainers and Shengjing Zhu (recent uploader) to
CC list.
Arnaud Rebillout writes:
> Hello Nicholas! Thanks for your feedback here, see replies below.
>
You're welcome :-)
> On Sun, 11 Apr 2021 11:51:20 -0400 Nicholas D
Hello Nicholas! Thanks for your feedback here, see replies below.
On Sun, 11 Apr 2021 11:51:20 -0400 Nicholas D Steeves
wrote:
> I'm not sure that systemd-detect-virt and your patch are
> forward-compatible in light of
>
> Originally, ".dockerenv" was for transmitting the environment
>
.org
> Usertags: origin-kali
>
> Dear Maintainer,
>
> The code that is meant to detect if debootstrap is running from within a
> docker container is broken with cgroup v2. Talking about this particular
> function and line in the file `functions`:
>
I agree that Bullseye
rmal
> Tags: patch
> User: de...@kali.org
> Usertags: origin-kali
>
> Dear Maintainer,
>
> The code that is meant to detect if debootstrap is running from within a
> docker container is broken with cgroup v2. Talking about this particular
> function and line in the file `funct
Package: debootstrap
Version: 1.0.123
Severity: normal
Tags: patch
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
The code that is meant to detect if debootstrap is running from within a
docker container is broken with cgroup v2. Talking about this particular
function and line
Processing commands for cont...@bugs.debian.org:
> retitle 970678 Network preseeding using http is broken
Bug #970678 [debian-installer] udev-udeb: setup /dev/fd, /dev/std{in,out,err}
symlinks
Changed Bug title to 'Network preseeding using http is broken' from 'udev-udeb:
setup /dev/fd, /
Spammers have harvested the email alias used to report this issue, and
actively abuse it. As a consequence I'm suspending it. I'm subscribed to the
bug report using another address.
Follow-up sent to the bug will reach me. For instructions on how to email me
directly, please follow
Ben Hutchings writes:
> On Mon, 2020-09-21 at 20:42 +0100, Ben Hutchings wrote:
>> On Mon, 2020-09-21 at 17:43 +0200, Martin Samuelsson wrote:
>> > Philip Hands @ 2020-09-21 (Monday), 15:30 (+0200)
>> > > Martin Samuelsson writes:
>> > >
>> > > Just to be clear on this point, are you saying
On Mon, 2020-09-21 at 20:42 +0100, Ben Hutchings wrote:
> On Mon, 2020-09-21 at 17:43 +0200, Martin Samuelsson wrote:
> > Philip Hands @ 2020-09-21 (Monday), 15:30 (+0200)
> > > Martin Samuelsson writes:
> > >
> > > Just to be clear on this point, are you saying [...]
> >
> > I'm saying there
Philip Hands @ 2020-09-21 (Monday), 22:38 (+0200)
BTW The example I pasted was just busybox running on my laptop running
full Debian, so was not supposed to be demonstrating it working under
d-i.
I could likely have been more precise from the beginning about the exact
cause. Sorry for making
Martin Samuelsson writes:
> I'm saying there is no /dev/fd/ at all
Oh, fair enough. That's odd.
BTW The example I pasted was just busybox running on my laptop running
full Debian, so was not supposed to be demonstrating it working under
d-i.
...
> --- http.orig 2020-09-21 17:21:24.159480072
On Mon, 2020-09-21 at 17:43 +0200, Martin Samuelsson wrote:
> Philip Hands @ 2020-09-21 (Monday), 15:30 (+0200)
> > Martin Samuelsson writes:
> >
> > Just to be clear on this point, are you saying [...]
>
> I'm saying there is no /dev/fd/ at all on current daily debian-installer
> images and
Geert Stappers @ 2020-09-21 (Monday), 17:18 (+0200)
Under which circumstance does the bug shows itself?
As far as I understand /dev/fd seems to be completely missing. Haven't dug
into it. For what its worth, it seems /proc/self/fd is still available. I
did experiment with redirecting sed
Philip Hands @ 2020-09-21 (Monday), 15:30 (+0200)
Martin Samuelsson writes:
Just to be clear on this point, are you saying [...]
I'm saying there is no /dev/fd/ at all on current daily debian-installer
images and hasn't been since at least 20200818 (which was the oldest one I
could try
On Mon, Sep 21, 2020 at 03:30:27PM +0200, Philip Hands wrote:
> Martin Samuelsson writes:
>
> > Booting the installer with DEBCONF_DEBUG=5 and debuging /bin/preseed_fetch,
> > /bin/fetch-url and /usr/lib/fetch_url/http shows that wget404() in the
> > latter is what's failing. It seems the
Martin Samuelsson writes:
> Booting the installer with DEBCONF_DEBUG=5 and debuging /bin/preseed_fetch,
> /bin/fetch-url and /usr/lib/fetch_url/http shows that wget404() in the
> latter is what's failing. It seems the pipeline fails since /dev/fd/4 does
> not exist.
Just to be clear on this
Martin Samuelsson writes:
...
> Reading README.wget404[1] clearly states this output redirection dance is
> never actually used, and that this convoluted expression merely exists
> because it could possibly-maybe be useful some day. As far as I can see the
> callers of wget404() does indeed
Package: debian-installer
Version: 20200920
Debian installer fails to fetch preseed files over http.
How to reproduce:
Boot the installer with url=http://pxeserver./example.txt
Where example.txt contains:
d-i preseed/include string something.txt \
other.txt \
more.txt
The installer
Control: retitle -1 text installer: unable to switch keyboard layouts -
kbd_mode broken
Control: severity -1 critical
Control: reassign -1 kbd
Bernhard wrote:
> One small error found:
> In the command line of the boot image, the option keymap=de don't work.
> In installer, there is US
Processing control commands:
> retitle -1 text installer: unable to switch keyboard layouts - kbd_mode broken
Bug #969965 [installation-reports] Installation of Debian 11 mostly successfully
Changed Bug title to 'text installer: unable to switch keyboard layouts -
kbd_mode broken' f
Hi,
Steve McIntyre wrote:
> I think you've misinterpreted this. We *don't* try to keep the daily
> builds around for more than a few days. They're a moving target. The
> only reason that the 2019 images are still around at all is that
> they're the last few builds where we had a build for mips.
On Thu, Sep 17, 2020 at 07:25:36PM +0100, Ben Hutchings wrote:
>On Tue, 2020-09-15 at 10:01 +0100, Steve McIntyre wrote:
>>
>> And fixed as of today's daily builds.
>>
>> Thanks for the report!
>
>Thanks Steve. We probably should have thought to update that after
>changing the dependencies
to use one of the Sid DI netinst firmware images and they
> > > seem to be broken for about a week or so now. After picking the
> > > language and keyboard, the iso is unable to mount. I am using an EFI
> > > machine with a usb flash drive and don't have a disk drive to test
On Mon, Sep 14, 2020 at 09:51:57AM +0100, Steve McIntyre wrote:
>Hi Brandon,
>
>On Sun, Sep 13, 2020 at 03:17:11AM -0400, Brandon Werner wrote:
>>Hi,
>>
>>I tried to use one of the Sid DI netinst firmware images and they
>>seem to be broken for about a week or so
Hey Holger,
On Mon, Sep 14, 2020 at 10:21:39PM +0200, Holger Wansing wrote:
>Steve McIntyre wrote:
>> Hi Brandon,
>>
>> On Sun, Sep 13, 2020 at 03:17:11AM -0400, Brandon Werner wrote:
>> >Hi,
>> >
>> >I tried to use one of the Sid DI netins
Hi,
Steve McIntyre wrote:
> Hi Brandon,
>
> On Sun, Sep 13, 2020 at 03:17:11AM -0400, Brandon Werner wrote:
> >Hi,
> >
> >I tried to use one of the Sid DI netinst firmware images and they
> >seem to be broken for about a week or so now. After picking the
Hi Brandon,
On Sun, Sep 13, 2020 at 03:17:11AM -0400, Brandon Werner wrote:
>Hi,
>
>I tried to use one of the Sid DI netinst firmware images and they
>seem to be broken for about a week or so now. After picking the
>language and keyboard, the iso is unable to mount. I am using
Hi,
I tried to use one of the Sid DI netinst firmware images and they seem to be
broken for about a week or so now. After picking the language and keyboard, the
iso is unable to mount. I am using an EFI machine with a usb flash drive and
don't have a disk drive to test if the error occurs
Your message dated Fri, 21 Aug 2020 04:58:02 +0200
with message-id <20200821045802.07acb7c9ded347064600d...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs --- round 5
has caused the Debian Bug report #917350,
regarding installation-reports: ibus behavior is
1 - 100 of 1571 matches
Mail list logo
