Processing commands for cont...@bugs.debian.org:
> block 987377 with 987587
Bug #987377 [rescue-mode] rescue-mode: when in graphical mode, locks up one
prompt before the shell
987377 was not blocked by any bugs.
987377 was blocking: 987441
Added blocking bug(s) of 987377: 987587
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> block 987441 with 987587
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for
Bullseye
987441 was blocked by: 987449 987377 987568 987368
987441 was not blocking any bugs.
Added blocking bug(s) of 987441: 987587
> thanks
St
On 25/04/21 at 11:04 +0200, Cyril Brulebois wrote:
> > B) In the installer, detect that firmware-amd-graphics or
> > firmware-misc-nonfree should be installed, and either install it (?),
> > or redirect the user to the unofficial installer that includes them.
>
> That could be achieved for an inst
Package: libpango1.0-udeb
Version: 1.44.7-3
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: debian-boot@lists.debian.org
Hi,
In the “better late than never” department… I've completed a debugging session
that shows that upgrading libpango1.0-udeb from 1.42.4-8 to 1
Cyril Brulebois (2021-04-25):
> I've ran out of (apparently stupid this time around…) wild guesses, so
> I suppose after a little nap it's going to be (heavy) hammer time…
I'm attaching an almost unedited version of my notes from yesterday.
It's not a definitive guide but might give someone else
Am 25. April 2021 10:12:13 MESZ schrieb Holger Wansing :
>>https://hosted.weblate.org/projects/debian-installer/#languages
>
>That's great.
>Thanks for taking care of that.
>
>I will activate Japanese on Weblate.
Done.
Holger
--
Sent from /e/ OS on Fairphone3
Salut Étienne,
Étienne Mollier (2021-04-25):
> I did further testing, so tried to wrap up my findings in a
> hopefully nice Karnaugh table below (dreading mta rewrap at
> this instant):
>
> Layout Plain RaidLVM LVM+Crypto
> LocaleDevice
> en_US Satablank blank ok
Hi,
Holger Wansing (2021-04-25):
> Chris Hofstaedtler :
> > I spent a few hours today on this issue, but did not get very far.
> > Not totally unexpected if you know nothing about the installer.
And yet!
> > I have, however, a perf top output to share. I believe this more or
> > less means the
Package: partman-base
Severity: normal
X-Debbugs-Cc: vagr...@debian.org, alk...@gmail.com
For armhf/arm64 rockchip platforms, the bootloader may be installed
somewhere past the typical initial partition of 2048, but some platforms
install parts of the boot firmware past this boundary.
This was fi
Control: found -1 2.1.2-1
Cyril Brulebois (2021-04-25):
> I'm currently chasing other blocking bugs for the installer, but I'll
> add this bug to the list, and try to get back to it later.
A quick debsnap shows at least those versions are affected:
2.1.2-1
2.1.2-2
2.1.3-1
2.1.3-2
but i
Processing commands for cont...@bugs.debian.org:
> block 987441 with 987568
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for
Bullseye
987441 was blocked by: 987449 987377 987368
987441 was not blocking any bugs.
Added blocking bug(s) of 987441: 987568
> thanks
Stopping
Package: open-iscsi-udeb
Version: 2.1.3-2
Severity: serious
Justification: not installable
X-Debbugs-Cc: debian-boot@lists.debian.org
Hi,
The udeb isn't installable at the moment, due to:
Depends: libc6-udeb (>= 2.31), libcrypto1.1-udeb (>= 1.1.1i), libisns-udeb,
libkmod2-udeb (>= 28), libm
I did further testing, so tried to wrap up my findings in a
hopefully nice Karnaugh table below (dreading mta rewrap at
this instant):
Layout Plain RaidLVM LVM+Crypto
Locale Device
en_US Satablank blank ok ok
en_US NVMeok blank ok ok
fr_FR Sat
Hi,
Chris Hofstaedtler wrote (Sun, 25 Apr 2021 14:13:05 +0200):
> While the -exact- same bug does not appear on the
> 20210424-7/amd64/iso-cd/debian-testing-amd64-netinst.iso image, I
> think the bug is still there, just better hidden.
> I managed to make debconf hang by:
> - select Marathi
>
Hi Steve,
On 2021-04-24 21:40, Steve McIntyre wrote:
> On Sat, Apr 24, 2021 at 04:14:16PM -0400, Martin wrote:
> >Please restore the correct formula, thank you! (Or even allow
> >users to chose a swap size for the auto-partioner (e.g. if a
> >users already plans to upgrade the RAM, see #780208).
>
* Holger Wansing [210425 16:53]:
> Chris Hofstaedtler wrote (Sun, 25 Apr 2021 14:13:05 +0200):
> > While the -exact- same bug does not appear on the
> > 20210424-7/amd64/iso-cd/debian-testing-amd64-netinst.iso image, I
> > think the bug is still there, just better hidden.
> > I managed to make de
Hi,
Cyril Brulebois wrote (Sun, 25 Apr 2021 11:53:22 +0200):
> Given the question below, I suppose you could revert this change
> manually and restart the installer (after all, it's about a symlink and
> a line in a config file).
Sure. I did that already.
But this does not gain any value, becaus
Hi,
Chris Hofstaedtler wrote (Sat, 24 Apr 2021 23:45:13 +0200):
> Hello,
>
> * Holger Wansing [210424 21:42]:
> > While trying to debug another problem yesterday, I found that the RC1
> > graphical
> > installer fails to go forward, when selecting one of these languages:
> > - Kannada
> >
Cyril Brulebois (2021-04-24):
>
>
> cdebconf-* were updated. There's a change in there but apparently only
> for the text frontend.
>
> At least for src:cdebconf's udebs, the libc they were built against is
> no longer the same (2.29 vs. 2.31).
>
> This might very well be a red herring, though
Cyril Brulebois, on 2021-04-25 14:17:36 +0200:
> Steve McIntyre (2021-04-22):
> > From checking (as discussed in IRC with Phil), rescue-mode moved from
> > 1.78 to 1.80 between those two builds. The only changes were in
> > translations, so the problem must be elsewhere. :-(
>
> Must it really?
>
Hi,
"Andrew M.A. Cater" wrote (Sat, 24 Apr 2021 15:26:00
+):
> Initial boot: [O ]
> Detect network card:[O ]
> Configure network: [O ]
> Detect media: [O ]
> Load installer modules: [O ]
> Clock/timezone setup: [O ]
> User/password setup:[O ]
> Detect hard
Steve McIntyre (2021-04-22):
> From checking (as discussed in IRC with Phil), rescue-mode moved from
> 1.78 to 1.80 between those two builds. The only changes were in
> translations, so the problem must be elsewhere. :-(
Must it really?
With a fresh install (with LVM but oh well), using netboot/
Hi,
* Holger Wansing [210425 11:34]:
> Chris Hofstaedtler wrote (Sat, 24 Apr 2021 23:45:13 +0200):
> > * Holger Wansing [210424 21:42]:
> > > While trying to debug another problem yesterday, I found that the RC1
> > > graphical
> > > installer fails to go forward, when selecting one of these l
On Sun, Apr 25, 2021 at 12:18:03PM +0100, Rebecca N. Palmer wrote:
> Cyril Brulebois wrote:
> > getting my hands on relevant hardware is in progress
>
> Note that https://lists.debian.org/debian-boot/2021/04/msg00247.html implies
> the affected hardware is _not_ simply "all AMD/ATI or NVidia hardw
Cyril Brulebois wrote:
getting my hands on relevant hardware is in progress
Note that https://lists.debian.org/debian-boot/2021/04/msg00247.html
implies the affected hardware is _not_ simply "all AMD/ATI or NVidia
hardware". Do we know of hardware that is reproducibly affected?
YunQiang Su
Hideki Yamane (2021-04-25):
> On Fri, 23 Apr 2021 23:21:47 +0200
> Cyril Brulebois wrote:
> > It seems both tasksel and debian-installer were updated to use the
> > replacement on the deb and udeb fronts respectively, so you should be
> > good to go I think?
>
> Thank you, let's go.
In hindsig
On Fri, 23 Apr 2021 23:21:47 +0200
Cyril Brulebois wrote:
> It seems both tasksel and debian-installer were updated to use the
> replacement on the deb and udeb fronts respectively, so you should be
> good to go I think?
Thank you, let's go.
--
Regards,
Hideki Yamane henrich @ debian.org
Updating the issue with "previously missing information"
- Forwarded message from "Andrew M.A. Cater" -
Date: Sun, 25 Apr 2021 10:13:59 +
From: "Andrew M.A. Cater"
To: debian-boot@lists.debian.org
Subject: Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules
not i
Holger Wansing (2021-04-25):
> Cyril Brulebois wrote (Sun, 25 Apr 2021 11:53:22 +0200):
> > Given the question below, I suppose you could revert this change
> > manually and restart the installer (after all, it's about a symlink and
> > a line in a config file).
>
> Sure. I did that already.
> B
On Sun, Apr 25, 2021 at 10:26:42AM +0200, Holger Wansing wrote:
> Hi,
>
> Holger Wansing wrote (Sun, 25 Apr 2021 10:08:32 +0200):
> > >I don't understand:
> > >does this mean that the issue that you reported in
> > >https://lists.debian.org/debian-boot/2020/12/msg00026.html can be
> > >considered
For context: Andrew is testing various hardware and reporting back,
but some part of it ended up on IRC instead of in bug reports.
Geert Stappers (2021-04-25):
> On Sun, Apr 25, 2021 at 10:31:00AM +0200, Holger Wansing wrote:
> > Hi,
> >
> > "Andrew M.A. Cater" wrote (Sat, 24 Apr 2021 15:26:00
Hallo Michael,
Michael Biebl (2021-04-25):
> On Fri, 23 Apr 2021 22:57:40 +0200 Cyril Brulebois wrote:
>
> > - broken rescue mode
>
> Is this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952450 or
> something else?
No, I hadn't the bug report handy when I wrote the quick text, but it's
Holger Wansing (2021-04-25):
> Chris Hofstaedtler wrote (Sat, 24 Apr 2021 23:45:13 +0200):
> > Hello,
> >
> > * Holger Wansing [210424 21:42]:
> > > While trying to debug another problem yesterday, I found that the RC1
> > > graphical
> > > installer fails to go forward, when selecting one of
Hi kibi
On Fri, 23 Apr 2021 22:57:40 +0200 Cyril Brulebois wrote:
> - broken rescue mode
Is this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952450 or
something else?
I.e. do you consider #952450 a blocker for d-i?
Regards,
Michael
signature.asc
Description: This is a digitally signed
Hi,
Lucas Nussbaum wrote (Sun, 25 Apr 2021 10:30:30 +0200):
> > (Also: Look at the other reports I quoted in my mail above for more user
> > cases.)
>
> But aren't all those other reports from either the buster installer, or
> from installers for releases before buster?
Arrr, yes, you are righ
Your message dated Sun, 25 Apr 2021 11:17:12 +0200
with message-id <20210425091712.rdj4qiyso4u7k...@gpm.stappers.nl>
and subject line Re: Bug#987492: installation-reports: Successful upgrade of
Bullseye from Buster
has caused the Debian Bug report #987492,
regarding installation-reports: Successfu
Moin moin,
On Sun, Apr 25, 2021 at 10:31:00AM +0200, Holger Wansing wrote:
> Hi,
>
> "Andrew M.A. Cater" wrote (Sat, 24 Apr 2021 15:26:00
> +):
> > Initial boot: [O ]
> > Detect network card:[O ]
> > Configure network: [O ]
> > Detect media: [O ]
> > Load insta
[ cc+=-x@ ]
Hi Lucas,
Thanks for your summary, I'm not sure about every single detail, but it
seems to be a good basis for discussion. I might point to it from our
errata page (I didn't have a specific bug report when I wrote the most
recent entries):
https://www.debian.org/devel/debian-install
Hi,
Lucas Nussbaum wrote (Sat, 24 Apr 2021 11:30:03 +0200):
> With Debian 10, the behaviour was that the installation succeeded
> without installing firmware-* packages, and then, and the first boot, X
> would start in a "degraded" mode (using, for example, the vesa driver).
> The user would gene
Holger Wansing (2021-04-24):
> Maybe add
> #987449: [rc-1 graphical d-i] graphical installer hangs at language chooser
> step for several languages
> here?
Sure, thanks.
Feel free to “nominate”/mention any other bug reports that seem worth
considering. I've seen you went through a number of in
Processing commands for cont...@bugs.debian.org:
> block 987441 with 987449
Bug #987441 [src:debian-installer] debian-installer: D-I must get ready for
Bullseye
987441 was blocked by: 987368 987377
987441 was not blocking any bugs.
Added blocking bug(s) of 987441: 987449
> thanks
Stopping process
On 25/04/21 at 10:26 +0200, Holger Wansing wrote:
> Hi,
>
> Holger Wansing wrote (Sun, 25 Apr 2021 10:08:32 +0200):
> > >I don't understand:
> > >does this mean that the issue that you reported in
> > >https://lists.debian.org/debian-boot/2020/12/msg00026.html can be
> > >considered fixed? And th
Hi,
Holger Wansing wrote (Sun, 25 Apr 2021 10:08:32 +0200):
> >I don't understand:
> >does this mean that the issue that you reported in
> >https://lists.debian.org/debian-boot/2020/12/msg00026.html can be
> >considered fixed? And that the situation improved between buster and
> >bullseye?
>
> F
Am 25. April 2021 06:46:40 MESZ schrieb YOSHINO Yoshihito
:
>Dear d-i l10n coordinator,
>
>I am trying to update ja translation for d-i, while the previous
>translator kmuto is no longer active. He used to commit all the ja
>translation things from himself and other translators.
>Instead I would l
Am 25. April 2021 09:48:20 MESZ schrieb Lucas Nussbaum :
>On 24/04/21 at 23:27 +0200, Holger Wansing wrote:
>> Results:
>>
>> Installing Buster (with GNOME DE) lead to a system failing to start X,
>> system hangs on the console, latest entry is "Starting GNOME Display
>> Manager".
>> The needed f
On 24/04/21 at 23:27 +0200, Holger Wansing wrote:
> Results:
>
> Installing Buster (with GNOME DE) lead to a system failing to start X,
> system hangs on the console, latest entry is "Starting GNOME Display Manager".
> The needed firmware package (firmware-amd-graphics) was NOT installed.
> Instal
46 matches
Mail list logo
