Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #300717

Bug#987441: s390x installation bugs

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Control: block 987441 by 926539
Control: block 987441 by 987788

Hi Valentin,

Thanks for your suggestions.

Valentin Vidic <vvidic@debian.org> (2021-05-02):
> Probably not critical, but maybe these installation bugs on s390x
> could be fixed for the release?
> 
> rootskel: steal-ctty no longer works on at least sparc64
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539

From skimming through the bug log, it seems it was initially a sparc64
problem, that was fixed in the kernel (inconsistent naming) eventually.
The same issue exists on s390x but isn't apparently going to get fixed
so we need to have d-i be smarter (hence the merge request)?

I'd suggest at least retitling the bug report to mention s390x (release
arch, affected) instead of sparc64 (port arch, no longer affected), to
lower the chances people could overlook this issue, thinking it's only
about a port arch.

I know it's been around for a while, but trying to get that merged right
now doesn't feeel right; trying to make the change only kick in on s390x
(in an attempt to fix s390x while not risking regressing elsewhere)
might eat up some time (lots of conditionals there), but it would feel a
little safer.

Would it make sense to have two for loops (one version “after” for s390x
only, and one version “before” for all archs) as a temporary measure for
bullseye? We could then switch all archs to the “after” version at the
beginning of the bookworm release cycle and deal with possible
regressions then?

In any cases, I'm happy to keep an eye on #926539 via #987441, even if
we don't block the release on it.

> debian-installer: qemu-system-s390x installation fails due to segfault in main-menu
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987788

Yes, it seems works keeping an eye on. I had asked on tips on how to
test s390x but haven't had a chance to follow up on this yet.

Also adding to the list of bugs to keep an eye on (again, possibly not
blocking the release on its being resolved; we could have the issue
listed in errata, and possibly fixed in a point release).


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Back to linux.debian.bugs.rc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#987441: s390x installation bugs Valentin Vidic <vvidic@debian.org> - 2021-05-02 23:00 +0200
  Bug#987441: s390x installation bugs Cyril Brulebois <kibi@debian.org> - 2021-05-03 08:40 +0200
    Bug#987441: Bug#926539: Bug#987441: s390x installation bugs John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2021-05-03 13:00 +0200
  Bug#987441: s390x installation bugs Valentin Vidic <vvidic@debian.org> - 2021-08-01 22:00 +0200

csiph-web