Bug#1004292: debian-installer:s390x: installer fails to format dasd disc on s390x systems
Thanks Cyril!
From:
"Cyril
Brulebois" <kibi@debian.org>
To:
"Dipak
Zope1" <Dipak.Zope1@ibm.com>, 1004292@bugs.debian.org
Date:
26/01/2022
12:20 AM
Subject:
[EXTERNAL]
Re: Bug#1004292: debian-installer:s390x: installer fails to format dasd
disc on s390x systems
Hi Dipak,
Dipak Zope1 <Dipak.Zope1@ibm.com> (2022-01-25):
> This is the only fix I have for s390-dasd and we can release the package
> to unstable. This is good for back-porting to bullseye as well. However,
I
> am still testing the installer and more bugs/fixes are on their way
for
> s390 installer packages.
Alright!
> I am new to this but I am committed to supporting s390x moving forward.
So
> I would like to know how I should ideally move forward with this fix.
May
> be through the package update and sponsorship path?
This is great news. I'd suggest creating an account on Salsa, and
requesting access from https://salsa.debian.org/installer-team
To contribute patches to our packages, you can fetch the git repository
e.g. via debcheckout, and either push directly to master, or open merge
requests. Filing bugs/attaching patches via the bug tracker would work
too.
Once patches are made their way to the relevant git tree, a developer
can check everything looks good and sponsor the package. After a while,
you can be trusted to upload a subset of packages, by becoming a Debian
Maintainer.
Regarding the backporting to bullseye, I'm usually coordinating them
with the release team, so I'd suggest focussing on preparing things for
unstable, and getting ahold of me so that I deal with the backport. :)
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
[attachment "signature.asc" deleted by Dipak Zope1/India/Contr/IBM]
Reply to: