The attachment
"debdiff_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
** Patch added:
"debdiff_signed_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594575/+files/debdiff_signed_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch
--
You received this bug notification because you
** Patch added:
"debdiff_signed_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594573/+files/debdiff_signed_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch
--
You received this bug notification because you
** Patch added: "debdiff_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594574/+files/debdiff_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch
--
You received this bug notification because you are a member of
** Patch added: "debdiff_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594572/+files/debdiff_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch
--
You received this bug notification because you are a member of
Hi Benjamin, that is already fixed (but thanks for mentioning this).
The PPA was updated several days ago - now with proper (and ready to upload)
packages (with proper version numbers: 2.20.0-0ubuntu3.1 for jammy and
2.20.0-0ubuntu4 for kinetic) and with s390-tools-signed packages:
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Also affects: s390-tools-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: s390-tools-signed (Ubuntu)
Status: New => In Progress
** Changed in:
Hi Benjamin, first of all thx for testing and your thoughts.
First of all sorry, I usually have to increment the package version, but
wanted to avoid it this time (due to s390-tools-signed), but the usual
habit hit me - anyway you found a way to get it installed ...
I was also wondering about
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * The recently introduced chreipl-fcp-mpath tool,
+available since 22.04 in a separate binary package,
+fails, due to a wrong location for the helper files.
+
+ * In Addition some less critical
Hi Benjamin; there is a plan for doing a larger s390-tools update for jammy
(incl. more z16 enablements), and this should be incl. as well.
For now I created a PPA test build (that addresses LP#1971993 only) which is
available here:
10 matches
Mail list logo