** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959532
Title:
[22.04 FEAT] Transparent PCI device recovery
To manage notifications about this bug
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962578
Title:
[UBUNTU 20.04] Fix SIGP processing on KVM/s390
To manage
Patch request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-March/thread.html#128621
changing status to 'In Progress'.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Summary changed:
- [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
+ [22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
--
You received this bug notification because you are a
Thanks for the quick answer.
Ok, so in this case I'll try to keep the patch as small as possible, means only
make sure it's properly in include/uapi/linux/kvm.h.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@IBM Am I right assuming that the KVM_CAP_S390_MEM_OP_EXTENSION capability
level needs to be set to 211 in 'include/uapi/linux/kvm.h', but also in
'tools/include/uapi/linux/kvm.h'?
(That is at least where I see other settings aligned.)
--
You received this bug notification because you are a
** Summary changed:
- [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set Capability 211
+ [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
--
You received this bug
*** This bug is a duplicate of bug 1960182 ***
https://bugs.launchpad.net/bugs/1960182
These patches were already addressed by:
https://lists.ubuntu.com/archives/kernel-team/2022-February/128125.html
(LP#1960182)
(see comment:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for
debdiff for zlib_1.2.11.dfsg-2ubuntu7 to zlib_1.2.11.dfsg-2ubuntu8
(except the of the top line of the changelog:
zlib (1:1.2.11.dfsg-2ubuntu8) impish; urgency=medium
the debdiff is the same for impish and jammy)
* d/p/410-lp1961427.patch ported from zlib #410, fixing
compressBound() with hw
Kernel SRU request submitted for jammy:
https://lists.ubuntu.com/archives/kernel-team/2022-March/thread.html#128531
changing status to 'In Progress'.
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in:
** Description changed:
SRU Justification:
==
[Impact]
* KVM uses lazy storage key enablement as Linux does no longer make use of
- the storage keys. When the guest enters keyed mode, then KVM will
- save/restore the key during paging, provide change/reference
Additional comment to #16: adjust capability number to 211 to account for an
outstanding merge in kvm-next that changed it:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d328
--
You received this bug notification because you are a member of
Btw. I had to slightly adjust the backport (commit #16) due to changed
context, that was caused by a diag 318 patch that has landed meanwhile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962831
Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-March/thread.html#128468
changing status to 'In Progress'.
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * KVM uses lazy storage key enablement as Linux
** Summary changed:
- [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(Backport to focal)
+ [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
A test build is now available at the PPA here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1962831
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962831
Title:
[UBUNTU 20.04] KVM: Enable
** Description changed:
SRU Justification:
==
[Impact]
- * The SIGP processing on KVM/s390x is incorrect and not fully conformant to
- the 'Principles of Operations', the IBM Z architecture definition
- and documentation.
+ * The SIGP processing on KVM/s390x is
SRU request submitted to the Ubuntu kernel team mailing list for impish and
focal:
https://lists.ubuntu.com/archives/kernel-team/2022-March/thread.html#128449
Changing status to 'In Progress' for impish and focal.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
**
Many thx, Eric!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962578
Title:
[UBUNTU 20.04] Fix SIGP processing on KVM/s390
To manage notifications about this bug go to:
Some stats in the changes:
patches.tar.gz:
Documentation/virt/kvm/api.txt|2
arch/s390/include/asm/uaccess.h | 26 +
arch/s390/kvm/gaccess.c | 424 +-
arch/s390/kvm/gaccess.h |
Hi @Diego, may I ask about the status of a revised patch?
I'm asking because we are getting extremely close to the end of the 22.04
development cycle (and are already past feature freeze). Hence it would be good
to know if this is still valid for this cycle, or if it need to be moved to the
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959984
Title:
[22.04 FEAT] KVM: Allow long kernel command lines for QEMU
Kernel test builds:
linux - 5.13.0-32.35~lp1962578
linux - 5.4.0-102.115~lp1962578
that incl. the commits mentioned above are available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1962578
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- [UBUNTU 20.04] Fix SIGP processing (KVM: s390)
+ [UBUNTU 20.04] Fix SIGP processing on KVM/s390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962578
Title:
[UBUNTU 20.04]
To avoid any regressions after upgrades, it's needed that Impish/21.10 is
patched, too.
(SIGP fix is already addressed for jammy in LP#/1959735)
I just check the impish master-next tree and the situation is the same like on
focal.
Just the following two need to be added to focal and impish:
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Importance:
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960255
Title:
Prevent do-release-upgrades on P8 systems from focal or
This bug is a consequence of LP#1962286.
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
That's why I like upstream stable tags so much ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961850
Title:
[UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap
To manage
Many thanks Ilya!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954676
Title:
jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >=
11.2.0-10ubuntu1 / gcc-11 PLT regression on
And for focal this commit is included (as 00501b41aaf7) in Ubuntu-5.4.0-100
(and higher).
It came in via upstream stable bug: https://bugs.launchpad.net/bugs/1956381
And since focal-updates includes 5.4.0-100.113 right now, I'm updating the
focal entry to Fix Released.
(just having to wait for
The commit has already landed in jammy (as ba91ab72d4f8).
It's included in Ubuntu-5.15.0-15.15 (and higher).
Hence updating the affects jammy entry to Fix Released.
And for impish its included in Ubuntu-5.13.0-31 (and newer) as 7ca2229ccb56.
5.13.0-30.33 is in impish-updates
and 5.13.0-32.35 in
Public bug reported:
An attempt to merge sshuttle prior to jammy FF failed, because of
autopkgtest failures.
The delta between Debian and Ubuntu is d/t/* only.
A v1.1.0-1ubuntu1 is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/sshuttle
The failures can be found here:
Patch request submitted:
https://lists.ubuntu.com/archives/kernel-team/2022-February/thread.html#128313
Updating status to 'In Progress'.
Assigning kernel entry to 'Canonical Kernel Team'.
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: linux (Ubuntu)
Yes, that's already incl. in the pull request that I've mentioned in the
comment above ...
and with that also incl. in the test kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933179
Title:
Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-February/thread.html#128293
changing status to 'In Progress'.
A test build was done here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1933179/
** Changed in: linux (Ubuntu)
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960117
Title:
[22.04 FEAT] Add new CPU-MF Counters for new IBM Z Hardware
To manage notifications
Hi @Boris, no, not not needed - if added J, I and F as affected here.
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
**
** Changed in: s390-tools-signed (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: s390-tools (Ubuntu Impish)
** Changed in: ubuntu-z-systems
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935666
Title:
s390-tools FTBFS
Since the patch got upstream with 5.16, I think it needs to be applied
to Impish/5.13 and jammy/5.15, too.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance:
** Changed in: s390-tools-signed (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: s390-tools (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a
Uploaded another updated debdiff that now includes the three patches
from LP#1959965 that were made available over night.
debdiff for version bump from 2.17 to 2.20 (including LP#1959965)
** Patch removed: "debdiff_s390-tools_2.17_to_2.20.diff"
** Patch added: "debdiff_s390-tools-signed_2.17_to_2.20.diff"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1959420/+attachment/5562573/+files/debdiff_s390-tools-signed_2.17_to_2.20.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
updated debdiff with 81-dpm.rules included in
d/debian/s390-tools.install
** Patch added: "debdiff_s390-tools_2.17_to_2.20.diff"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1959420/+attachment/5562572/+files/debdiff_s390-tools_2.17_to_2.20.diff
--
You received this bug
** Patch removed: "s390-tools-signed debdiff for version bump from 2.17 to 2.20"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1959420/+attachment/5559598/+files/debdiff_s390-tools-signed_2.17_to_2.20.diff
** Patch removed: "debdiff for version bump from 2.17 to 2.20"
debdiff for version bump from 2.17 to 2.20 (+ 3 additional fixes on top)
** Patch removed: "debdiff for version bump from 2.17 to 2.20"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1959420/+attachment/5559541/+files/debdiff_s390-tools_2.17_to_2.20.diff
** Patch added: "debdiff
Many thx, Jan!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959420
Title:
[22.04 FEAT] Upgrade s390utils/s390-tools to latest version
To manage notifications about this bug go to:
Many thx!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961518
Title:
Please merge 3.10.3-12 into jammy
To manage notifications about this bug go to:
Hi Erich, no, unfortunately not - there are several Ubuntu specifics
inside ('remaining changes').
(https://launchpadlibrarian.net/587063476/atlas_3.10.3-12ubuntu1_source.changes)
atlas (3.10.3-12ubuntu1) jammy; urgency=low
.
* Merge from Debian unstable. (LP: #1961518)
Solved merge
A successful test build of the merged v3.10.3-12ubuntu1 was done for jammy here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961518
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961518
Title:
Public bug reported:
tracking bug
__
from atlas report:
atlas
Mon Dec 20 15:46:45 2021
Below now follows the report of the automated merge of the Ubuntu
changes to the atlas source package against the new Debian version.
This file is designed to be both human readable and
** Package changed: linux (Ubuntu) => zlib (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
You received this bug notification because you are a
Hi Nick.
output for 1.
https://pastebin.ubuntu.com/p/mKtMTzhSpn/
and for 2.
$ apt-config dump | grep APT::Architecture
APT::Architecture "ppc64el";
APT::Architectures "";
APT::Architectures:: "ppc64el";
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959419
Title:
[22.04 FEAT] Upgrade openCryptoki to latest version (>=
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960182
Title:
[UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Tags added: jammy
** Description changed:
- == Comment: #2 - Daniel John Axtens - 2020-11-05
19:50:03 ==
- This bug covers the grub part of our LPAR Secure Boot design, which I'd like
to propose for your 21.04 release.
+ Feature Freeze Exception (FFe):
+
+ Due to the fact that the work
** Tags added: jammy
** Changed in: ubuntu-power-systems
Importance: Medium => High
** Changed in: grub2 (Ubuntu)
Importance: Medium => High
** Description changed:
+ Feature Freeze Exception (FFe):
+
+ Due to the fact that the work and backlog on grub2 in jammy is pretty
+ big and the
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961027
Title:
[FFE] merge virt-manger >3.2 for Jammy once released
To manage notifications about this bug go to:
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960875
Title:
[UBUNTU 21.10] s390/cio: verify the driver availability for path_event
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959419
Title:
[22.04 FEAT] Upgrade openCryptoki to latest version (>=
Meanwhile tigervnc v1.12 landed in jammy,
hence closing this ticket as Fix Released.
** Changed in: tigervnc (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: New => Fix Released
--
You received this bug notification because you are a member
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
--
You received this bug notification because you are a member of Ubuntu
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959420
Title:
[22.04 FEAT] Upgrade s390utils/s390-tools to latest version
To manage notifications
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959419
Title:
[22.04 FEAT] Upgrade openCryptoki to latest version (>= 3.17)
To manage
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959529
Title:
Hipersocket page allocation failure on Ubuntu 20.04 based
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance:
@Christian thx for sponsoring and yes, I'll guide the -proposed
migration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960814
Title:
Sync tigervnc 1.12.0+dfsg-2 (universe) from Debian unstable
A test compile of the Debian unstable release was done for jammy here:
https://launchpad.net/~fheimes/+archive/ubuntu/tigervnc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960814
Title:
Sync
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Wishlist
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
You received this bug notification
urgency=medium
* debian/patch/0001-Update-Surface_X11.cxx.patch
TigerVNC 1.11.0 contains a regression that causes vncviewer to display
incorrect colors when vncviewer and X11 server use different endianness.
(LP: #1929790)
-- Frank Heimes Mon, 20 Sep 2021 19:57:36 +0200
"
and it
Since a separate ticket got opened for the kernel part here: LP#1960580
I'm removing the 'affects kernel' portion from this one.
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959984
Title:
[22.04 FEAT] KVM: Allow long kernel command lines for QEMU
To manage
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959984
Title:
[22.04 FEAT] KVM: Allow long kernel command lines for QEMU
So just for the records:
with first picking:
277c8389386e ("390/kexec_file: move kernel image size check")
before
5ecb2da660ab ("s390: support command lines longer than 896 bytes")
I get the code into jammy's master-next.
--
You received this bug notification because you are a member of Ubuntu
Thanks to Krzysztof, who spend some time to get this properly in,
there is now a patched focal/20.04 kernel 5.4 available here:
https://launchpad.net/~krzk/+archive/ubuntu/linux-testing
https://launchpad.net/~krzk/+archive/ubuntu/linux-testing/+build/23143306
Since some more effort got spent like
@Viktor, yes sure - and Christian already started to get it in (#7).
But since jammy is an LTS I think it would just make sense to have the kernel
patch in 5.15 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959984
Title:
[22.04 FEAT] KVM: Allow long kernel command lines for QEMU
To manage notifications
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960004
Title:
Update openssl-ibmca to latest version 2.2.2 to ensure
Public bug reported:
Starting with Ubuntu Server 22.04 ppc64el is compiled for Power 9 processors.
Prior to 22.04 it was/is compiled for Power 8 processors.
Hence P8 processors are not able to run, install or upgrade to jammy.
So do-release-upgrades on a Power 8 system from last LTS (focal) or
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959421
Title:
[22.04 FEAT] Upgrade libica to latest version (crypto)
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960004
Title:
Update openssl-ibmca to latest version 2.2.2 to ensure
Meanwhile 'bookworm' has a 1.12, we should sync/merge this to jammy -
which is on my todo list ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929790
Title:
Request to backport fix for
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959421
Title:
[22.04 FEAT] Upgrade libica to latest version (crypto)
yes, I started to work on the version bump based on LP#1959420
A first debdiff is nearly ready ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935666
Title:
s390-tools FTBFS when built with
In preparation for the libica transition the reverse dependent packages were
rebuild:
$ reverse-depends -a source src:libica
Reverse-Build-Depends
* opencryptoki (for libica-dev)
* openssl-ibmca (for libica-dev)
Package "openssl-ibmca" was re-build as part of
Test build is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1960004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960004
Title:
Update openssh-ibmca to latest version 2.2.2 to
This updated openssl-ibmca version v2.2.2 works now fine with the new
libica v4.0.1 (https://bugs.launchpad.net/bugs/1959421).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960004
Title:
Update
Since an updated version (4.0.1) came on short notice that incl. some fixes,
I've removed the old debdiff and attached this new one.
A test build in PPA (https://launchpad.net/~fheimes/+archive/ubuntu/lp1959421)
is fine,
no lintian errors nor warning (using -EvIL +pedantic)
and the test is fine:
** Patch removed: "debdiff"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959421/+attachment/5558727/+files/debdiff_libica_3.9.0_to_4.0.0.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959427
Title:
[22.04 FEAT] Upgrade cryptsetup to latest version (crypto)
I could successfully build an openssh-ibmca v2.2.0 having a PPA
dependency in place to lp1959421 that includes a libica4.0.0 build.
(but will have to update lp1959421 again, since meanwhile a libica 4.0.1
got released)
--
You received this bug notification because you are a member of Ubuntu
debdiff for version bump from 2.2.1 to 2.2.2
2.2.2 is needed for libica4 compatibility
** Patch added: "debdiff for version bump from 2.2.1 to 2.2.2"
https://bugs.launchpad.net/ubuntu/+source/openssl-ibmca/+bug/1960004/+attachment/5559151/+files/debdiff_openssl-ibmca_2.2.1_to_2.2.2.diff
**
601 - 700 of 5804 matches
Mail list logo
