[Touch-packages] [Bug 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar

2022-12-05 Thread Frank Heimes
After getting the successful test results, I'm attaching the debdiff ...

** Attachment added: 
"debdiff_zlib_lunar_from_1.2.13.dfsg-1ubuntu2_to_1.2.13.dfsg-1ubuntu3.diff~"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1998470/+attachment/5634588/+files/debdiff_zlib_lunar_from_1.2.13.dfsg-1ubuntu2_to_1.2.13.dfsg-1ubuntu3.diff~

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1998470

Title:
  re-add s390x vectorized crc32 support to zlib in lunar

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Triaged

Bug description:
  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring.
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.
  https://launchpad.net/ubuntu/+source/zlib/+changelog

  The new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.

  So a few things needed to happen (from the changelog):
    * Re-add vectorized crc32 support for s390x by adding
  d/p/s390x-vectorize-crc32.patch
  (crc32vx-v4: s390x: vectorize crc32).
  This replaces the previously dropped patch:
  lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
    * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
  commented out, since it's no longer needed with the new s390x crc32 code.

  And since I bumped into a little build issue, I've also needed to:
    * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
  due to unused "const char *endptr;".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar

2022-12-04 Thread Frank Heimes
Cross-referencing Ilya's comment about testing from here:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1982583/comments/7
"
I ran tests 1-3 with Frank's 1:1.2.13.dfsg-1ubuntu3. They all pass; the 
performance improvement is also measurable.

Test 4 turned out to be meaningless: Ubuntu requires at least z13.
"

Just notice that we have z13 as minimal required Z architecture starting
with Ubuntu 20.04/focal anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1998470

Title:
  re-add s390x vectorized crc32 support to zlib in lunar

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Triaged

Bug description:
  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring.
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.
  https://launchpad.net/ubuntu/+source/zlib/+changelog

  The new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.

  So a few things needed to happen (from the changelog):
    * Re-add vectorized crc32 support for s390x by adding
  d/p/s390x-vectorize-crc32.patch
  (crc32vx-v4: s390x: vectorize crc32).
  This replaces the previously dropped patch:
  lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
    * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
  commented out, since it's no longer needed with the new s390x crc32 code.

  And since I bumped into a little build issue, I've also needed to:
    * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
  due to unused "const char *endptr;".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar

2022-12-01 Thread Frank Heimes
** Changed in: zlib (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1998470

Title:
  re-add s390x vectorized crc32 support to zlib in lunar

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Triaged

Bug description:
  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring.
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.
  https://launchpad.net/ubuntu/+source/zlib/+changelog

  The new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.

  So a few things needed to happen (from the changelog):
    * Re-add vectorized crc32 support for s390x by adding
  d/p/s390x-vectorize-crc32.patch
  (crc32vx-v4: s390x: vectorize crc32).
  This replaces the previously dropped patch:
  lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
    * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
  commented out, since it's no longer needed with the new s390x crc32 code.

  And since I bumped into a little build issue, I've also needed to:
    * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
  due to unused "const char *endptr;".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar

2022-12-01 Thread Frank Heimes
Test builds of the updated package are currently running in this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1998470

** Description changed:

  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
- since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring. 
+ since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring.
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.
+ https://launchpad.net/ubuntu/+source/zlib/+changelog
  
- This new patch is now available as
+ The new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839
  
  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.
  
  So a few things needed to happen (from the changelog):
-   * Re-add vectorized crc32 support for s390x by adding
- d/p/s390x-vectorize-crc32.patch
- (crc32vx-v4: s390x: vectorize crc32).
- This replaces the previously dropped patch:
- lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
-   * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
- commented out, since it's no longer needed with the new s390x crc32 code.
+   * Re-add vectorized crc32 support for s390x by adding
+ d/p/s390x-vectorize-crc32.patch
+ (crc32vx-v4: s390x: vectorize crc32).
+ This replaces the previously dropped patch:
+ lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
+   * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
+ commented out, since it's no longer needed with the new s390x crc32 code.
  
  And since I bumped into a little build issue, I've also needed to:
-   * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
- due to unused "const char *endptr;".
+   * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
+ due to unused "const char *endptr;".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1998470

Title:
  re-add s390x vectorized crc32 support to zlib in lunar

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring.
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.
  https://launchpad.net/ubuntu/+source/zlib/+changelog

  The new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.

  So a few things needed to happen (from the changelog):
    * Re-add vectorized crc32 support for s390x by adding
  d/p/s390x-vectorize-crc32.patch
  (crc32vx-v4: s390x: vectorize crc32).
  This replaces the previously dropped patch:
  lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
    * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
  commented out, since it's no longer needed with the new s390x crc32 code.

  And since I bumped into a little build issue, I've also needed to:
    * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
  due to unused "const char *endptr;".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998470] [NEW] re-add s390x vectorized crc32 support to zlib in lunar

2022-12-01 Thread Frank Heimes
Public bug reported:

At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
At this time it was already clear that this new version is no longer compatible 
with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring. 
Hence this patch was dropped and it was decided to backport (or better 'forward 
port'?) this vectorized crc32 implementation for s390x.

This new patch is now available as
crc32vx-v4: "s390x: vectorize crc32"
https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

This LP bug is now to track the re-integration of the vectorized crc32
implementation for s390x.

So a few things needed to happen (from the changelog):
  * Re-add vectorized crc32 support for s390x by adding
d/p/s390x-vectorize-crc32.patch
(crc32vx-v4: s390x: vectorize crc32).
This replaces the previously dropped patch:
lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
commented out, since it's no longer needed with the new s390x crc32 code.

And since I bumped into a little build issue, I've also needed to:
  * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
due to unused "const char *endptr;".

** Affects: ubuntu-z-systems
 Importance: Medium
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New

** Affects: zlib (Ubuntu)
 Importance: Medium
 Assignee: Frank Heimes (fheimes)
 Status: New


** Tags: s390x

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1998470

Title:
  re-add s390x vectorized crc32 support to zlib in lunar

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring. 
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.

  This new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.

  So a few things needed to happen (from the changelog):
* Re-add vectorized crc32 support for s390x by adding
  d/p/s390x-vectorize-crc32.patch
  (crc32vx-v4: s390x: vectorize crc32).
  This replaces the previously dropped patch:
  lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
* Remove option '--crc32-vx' for s390x in d/rules, that was previously just
  commented out, since it's no longer needed with the new s390x crc32 code.

  And since I bumped into a little build issue, I've also needed to:
* Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
  due to unused "const char *endptr;".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

2022-11-28 Thread Frank Heimes
** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ubuntu-z-systems
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997579

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

2022-11-24 Thread Frank Heimes
Oh yes, makes sense - thanks for the hint!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997579

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

2022-11-24 Thread Frank Heimes
Hmm, I just checked the changelog of the relevant packages (openssl and
systemd), assuming to find a fix that might have landed in between your
two attempts - but not much, mainly CVE fixes.

(I also assume you haven't installed any local packages either...)

And you've used the same packages than I did.

So right now I can't really say what happened...

Anyway, would you be okay with me closing this bug?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997579

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

2022-11-23 Thread Frank Heimes
Btw. before you retry, you may fix the broken packaging state of your system 
with:
sudo apt-get -y -f install
and then:
sudo apt update 
...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997579

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

2022-11-23 Thread Frank Heimes
** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
   Status: New => Incomplete

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1997579

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1983128] Re: linux-lowlatency fails to build on arm64 due to kernel option settings

2022-11-17 Thread Frank Heimes
set to invails, since this was for a previous proposed migrations issue
that was meanwhile solved

** Changed in: linux-lowlatency (Ubuntu)
   Status: New => Invalid

** Changed in: zlib (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1983128

Title:
  linux-lowlatency fails to build on arm64 due to kernel option settings

Status in linux-lowlatency package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Invalid

Bug description:
  The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression':
  "autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: 
Regression ♻"

  The regression is highly likely not due to zlib itself, but due to NEW kernel 
options, that don't have a default yet and a check-config FAIL, see:
  ...
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config: 
loading config
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations 
loading annotations
  check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
   -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
  check-config: 11323/11324 checks passed -- exit 1
  ...
  Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
  Error in reading or end of file.
  ...
  Initialize kernel stack variables at function entry
  > 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
    2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
    3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
  choice[1-3?]:
  Error in reading or end of file.
  ...

  Full log is here:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz

  (this might be caused by the recent compiler update)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1983128/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-10-24 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Released
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * As of today the architectural (level) name 'arch14' is used
 as CPU name for the new IBM z16 system.

   * The real name 'z16' couldn't be used until officially announced.

   * That happened meanwhile, hence we can now add and use the real
  name.

  [Test Plan]

   * Check if the same (proper) opcodes are detected on an IBM z16
 system with and without the patch.
 Since only the identification and name of a z16 system was modified.

   * Or the simplest test is probably to check
 (after having 'binutils' installed on an Ubuntu 22.04 s390x system)
 if not only:
 'as -m64 -march=arch14 --target-help'
 but also:
 'as -m64 -march=z16 --target-help'
 succeeds and leads to the same output.
 (As it does for '-march=arch13' and '-march=arch15'.)

  [Where problems could occur]

   * Issues could happen if the conditional statement that look
 for architectural / CPU name are paired wrongly, since:

   * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc.

   * If these pairs are not handled correctly,
 or the identification is erroneous
 a wrong system might be identified and wrong instructions used etc.

  [Other]

   * This is a hardware enablement SRU to enhance the IBM z16 support.

  __

  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.

  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.

  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-10-24 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Released
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * The latest glibc uses DT_RELR relocations,
 but it turned out that the linker support is still incomplete,
 as of binutils-2.38-3ubuntu1 on Ubuntu 22.04.

   * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc
  addresses'.

   * As discussed at the binutils mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/119921.html
 this fixes several (glibc) regressions (from 574 to 17).

   * Instead of stashing r_offset final address calculations in
 ppc64_elf_size_stubs for use by ppc64_elf_build_stubs,
 section/offset pairs need to be kept.

  [Test Plan]

   * Build and run the official (make) check:
 git clone git://sourceware.org/git/glibc.git
 mkdir build && cd build
 ../glibc/configure --prefix=/usr && make -j8 && make check

  [Where problems could occur]

   * In case relr_addr is not replaced everywhere it's deletion in
 elf64-ppc.c can cause problems, which will mainly occur at build time.

   * The relr section/offset array may lead to problems if the array is not
 properly handled or used.

   * The rewrite of append_relr_off may cause issues due to wrong allocs
 erroneous pointer arithmetic or array handling.

   * The entirely new sort_relr function may introduce new code issues
 or performance issues.

   * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to
 the new relr code could be done wrong
 in which case the linker support is still not working.

   * But the patch was discussed at the upstream mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921

   * and is limited to ppc, and even to file 'elf64-ppc.c'.
  __

  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:

  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html

  Contact Information = Matheus Castanho/mscasta...@ibm.com

  ---uname output---
  N/A

  Machine Type = N/A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check

  Userspace tool common name: binutils

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Userspace tool obtained from project website:  na

  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-10-21 Thread Frank Heimes
** Summary changed:

- [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is 
used
+ [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  Triaged
Status in zlib source package in Jammy:
  Triaged
Status in zlib source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
     in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
     hardware and newer and impacts all JDK versions (8,11,17, etc.)
     that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
     platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
     Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
     on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
     of a small test program (in C) that makes use of the zlib1g library
     or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
     https://launchpadlibrarian.net/626003193/410-lp1990379.patch
     and there are not many issues to expect.

   * There could be a potential problem with the adler field
     in the strm struct.
     For example in case the struct is not as assumed or contains
     and unexpected value, which would then ripple through
     the other fields, too.

   * Structural changes could be identified with a test build that was done
     for all affected Ubuntu releases and for all major architectures:
     https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]

   * The patch itself is the same for all zlib version in
     20.04, 22.04 and 22.10 - no further adjustments were needed.

   * This bug (LP#1990379) is solved in combination with LP#1982583,
 so that only one package update is needed.
 However, this bug affects Kinetic, jammy and Focal,
 but LP#1982583 only Jammy and Kinetic.

   * The debdiffs for Kinetic and Jammy should be taken from LP#1982583,
 and the remaining debdiff for Focal from here.

  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-10-07 Thread Frank Heimes
** Description changed:

  SRU Justification:
  --
  
  [ Impact ]
  
-  * The zlib function inflate() does not update strm.adler
-in case DFLTCC is used.
+  * The zlib function inflate() does not update strm.adler
+    in case DFLTCC is used.
  
-  * This issue was exposed by Java Certification Kit (JCK) running on z15
-hardware and newer and impacts all JDK versions (8,11,17, etc.)
-that use the system default settings.
+  * This issue was exposed by Java Certification Kit (JCK) running on z15
+    hardware and newer and impacts all JDK versions (8,11,17, etc.)
+    that use the system default settings.
  
-  * The JCK failure impacts the ability to certify Java SDKs on this
-platform/Linux-distribution combination.
+  * The JCK failure impacts the ability to certify Java SDKs on this
+    platform/Linux-distribution combination.
  
-  * On top the incorrect alder32 result may cause functional issues with
-Java applications that depend on the result.
+  * On top the incorrect alder32 result may cause functional issues with
+    Java applications that depend on the result.
  
  [ Test Plan ]
  
-  * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
-on a z15/LinuxONE III or newer system is needed.
+  * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
+    on a z15/LinuxONE III or newer system is needed.
  
-  * Then it's possible to test the updated package with the help
-of a small test program (in C) that makes use of the zlib1g library
-or run the Java Certification Kit.
+  * Then it's possible to test the updated package with the help
+    of a small test program (in C) that makes use of the zlib1g library
+    or run the Java Certification Kit.
  
-  * Test will be done by IBM.
+  * Test will be done by IBM.
  
  [ Where problems could occur ]
  
-  * The patch is a one-line change:
-https://launchpadlibrarian.net/626003193/410-lp1990379.patch
-and there are not many issues to expect.
+  * The patch is a one-line change:
+    https://launchpadlibrarian.net/626003193/410-lp1990379.patch
+    and there are not many issues to expect.
  
-  * There could be a potential problem with the adler field
-in the strm struct.
-For example in case the struct is not as assumed or contains
-and unexpected value, which would then ripple through
-the other fields, too.
+  * There could be a potential problem with the adler field
+    in the strm struct.
+    For example in case the struct is not as assumed or contains
+    and unexpected value, which would then ripple through
+    the other fields, too.
  
-  * Structural changes could be identified with a test build that was done
-for all affected Ubuntu releases and for all major architectures:
-https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379
+  * Structural changes could be identified with a test build that was done
+    for all affected Ubuntu releases and for all major architectures:
+    https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379
  
  [ Other Info ]
-  
-  * The patch itself is the same for all zlib version in
-20.04, 22.04 and 22.10 - no further adjustments were needed.
+ 
+  * The patch itself is the same for all zlib version in
+    20.04, 22.04 and 22.10 - no further adjustments were needed.
+ 
+  * This bug (LP#1990379) is solved in combination with LP#1982583,
+so that only one package update is needed.
+However, this bug affects Kinetic, jammy and Focal,
+but LP#1982583 only Jammy and Kinetic.
+ 
+  * The debdiffs for Kinetic and Jammy should be taken from LP#1982583,
+and the remaining debdiff for Focal from here.
+ 
  __
  
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.
  
  Found with a JDK test.
  
  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349
  
  Updated zlib PR: https://github.com/madler/zlib/pull/410
  
  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920
  
  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620
  
  Ubuntu 20.04 and later need to be fixed.
  
  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if
  DFLTCC is used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Jammy:
  In Progress
Status in zlib source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib 

[Touch-packages] [Bug 1982583] Re: Fix for zlib CRC32 optimization for s390x

2022-10-07 Thread Frank Heimes
** Description changed:

+ SRU Justification:
+ --
+ 
+ [ Impact ]
+ 
+  * There were two issues identified in the current
+zlib CRC32 optimization for s390x implementation:
+ 
+  * 1) s390_crc32_vx() signature mismatch
+   which causes a warning
+ 
+  * 2) '-DS390_CRC32_VX' was not added to SFLAGS
+   which results in vectorization being enabled only in the static library.
+ 
+  * The fixes are quite small and affect each only one line:
+ 
+  * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx
+ declaration
+ 
+  * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"'
+ 
+ [ Test Plan ]
+ 
+  * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed
+on a z15/LinuxONE III or newer system is needed.
+ 
+  * Then it's possible to test the updated package with the help
+of a small test program (in C) that checks for
+s390_crc32_vx() signature mismatches.
+ 
+  * The bug reporter has a set of s390x-specific tests that will be
+ executed.
+ 
+  * Test will be done by IBM.
+ 
+ [ Where problems could occur ]
+ 
+  * The fixes are each limited to one line, hence there are
+not many issues to expect, other than:
+ 
+  * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS,
+ 
+  * in case the changed data type in s390_crc32_vx is causing issues
+inside of s390_crc32_vx or in other parts of the code.
+ 
+  * Structural and syntactical issues can be identified with a test build
+that was done for all affected Ubuntu releases and for all major archs:
+https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583
+ 
+ [ Other Info ]
+ 
+  * This bug (LP#1982583) is solved in combination with LP#1982583,
+so that only one package update is needed.
+However, LP#1982583 also affects Focal, but this bug only Jammy and 
Kinetic.
+ 
+  * To fix LP#1982583 also for focal the debdiff mentioned there is needed, 
too.
+ __
+ 
  'zlib CRC32 optimization for s390x works only in a static library'
  
  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:
  
  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.
  
  I've attached the updated patch.

** Description changed:

  SRU Justification:
  --
  
  [ Impact ]
  
-  * There were two issues identified in the current
-zlib CRC32 optimization for s390x implementation:
+  * There were two issues identified in the current
+    zlib CRC32 optimization for s390x implementation:
  
-  * 1) s390_crc32_vx() signature mismatch
-   which causes a warning
+  * 1) s390_crc32_vx() signature mismatch
+   which causes a warning
  
-  * 2) '-DS390_CRC32_VX' was not added to SFLAGS
-   which results in vectorization being enabled only in the static library.
+  * 2) '-DS390_CRC32_VX' was not added to SFLAGS
+   which results in vectorization being enabled only in the static library.
  
-  * The fixes are quite small and affect each only one line:
+  * The fixes are quite small and affect each only one line:
  
-  * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx
+  * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx
  declaration
  
-  * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"'
+  * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"'
  
  [ Test Plan ]
  
-  * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed
-on a z15/LinuxONE III or newer system is needed.
+  * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed
+    on a z15/LinuxONE III or newer system is needed.
  
-  * Then it's possible to test the updated package with the help
-of a small test program (in C) that checks for
-s390_crc32_vx() signature mismatches.
+  * Then it's possible to test the updated package with the help
+    of a small test program (in C) that checks for
+    s390_crc32_vx() signature mismatches.
  
-  * The bug reporter has a set of s390x-specific tests that will be
+  * The bug reporter has a set of s390x-specific tests that will be
  executed.
  
-  * Test will be done by IBM.
+  * Test will be done by IBM.
  
  [ Where problems could occur ]
  
-  * The fixes are each limited to one line, hence there are
-not many issues to expect, other than:
+  * The fixes are each limited to one line, hence there are
+    not many issues to expect, other than:
  
-  * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS,
+  * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS,
  
-  * in case the changed data type in s390_crc32_vx is causing issues
-inside of s390_crc32_vx or in other parts of the code.
+  * in case the changed data type in s390_crc32_vx is causing issues
+    inside of s390_crc32_vx or in other parts of the code.
  
-  * Structural and syntactical issues can be identified with a test build
-that was done for all affected 

[Touch-packages] [Bug 1982583] Re: Fix for zlib CRC32 optimization for s390x

2022-10-07 Thread Frank Heimes
I transferred the modification into a separate patch 
(d/p/lp1982583-fix-for-zlib-crc32-optimization-for-s390x.patch),
and build a patched version (for all major architectures) in PPA for jammy and 
kinetic:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583
and attaching here the debdiff for jammy and kinetic - which are for both LP 
bugs, this LP#1982583 and LP#1990379.

** Attachment added: "lp1990379+lp1982583_debdiffs.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1982583/+attachment/5622051/+files/lp1990379+lp1982583_debdiffs.tgz

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: zlib (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: zlib (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1982583

Title:
  Fix for zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  'zlib CRC32 optimization for s390x works only in a static library'

  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:

  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.

  I've attached the updated patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-10-07 Thread Frank Heimes
I've just noticed another bug that I want to fix with the same package update: 
LP#1982583
But LP#1982583 affects only jammy and kinetic, not focal.

This means for fixing this bug (LP#1990379) for jammy and kinetic, please use 
these debdiffs:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/comments/2
and for fixing this bug (LP#1990379) for focal, please take the focal debdiff 
from the previous comment:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/comments/7

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Jammy:
  In Progress
Status in zlib source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982583] Re: zlib CRC32 optimization for s390x works only in a static library

2022-10-07 Thread Frank Heimes
** Description changed:

+ 'zlib CRC32 optimization for s390x works only in a static library'
+ 
  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:
  
  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.
  
  I've attached the updated patch.

** Summary changed:

- zlib CRC32 optimization for s390x works only in a static library
+ Fix for zlib CRC32 optimization for s390x

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1982583

Title:
  Fix for zlib CRC32 optimization for s390x

Status in zlib package in Ubuntu:
  New

Bug description:
  'zlib CRC32 optimization for s390x works only in a static library'

  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:

  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.

  I've attached the updated patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1982583/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-10-04 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Released
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Released
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Released
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 

[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-29 Thread Frank Heimes
** Changed in: zlib (Ubuntu Kinetic)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Jammy:
  In Progress
Status in zlib source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-29 Thread Frank Heimes
** Also affects: zlib (Ubuntu Kinetic)
   Importance: Medium
   Status: In Progress

** Also affects: zlib (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: zlib (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: zlib (Ubuntu Focal)
   Status: New => In Progress

** Changed in: zlib (Ubuntu Jammy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Jammy:
  In Progress
Status in zlib source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-28 Thread Frank Heimes
** Description changed:

  SRU Justification:
  --
  
  [ Impact ]
  
   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.
  
   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.
  
   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.
  
   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.
  
  [ Test Plan ]
  
   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.
  
   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.
  
   * Test will be done by IBM.
  
  [ Where problems could occur ]
  
   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.
  
   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.
  
   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379
  
  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __
  
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.
  
  Found with a JDK test.
  
  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349
  
  Updated zlib PR: https://github.com/madler/zlib/pull/410
  
  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920
  
  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620
  
  Ubuntu 20.04 and later need to be fixed.
+ 
+ ---
+ External link: https://warthogs.atlassian.net/browse/PEI-28

** Tags added: pei-28

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  

[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-28 Thread Frank Heimes
debdiffs for F, J and K

** Attachment added: "debdiffs.tgz"
   
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+attachment/5619739/+files/debdiffs.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-28 Thread Frank Heimes
** Description changed:

+ SRU Justification:
+ --
+ 
+ [ Impact ]
+ 
+  * The zlib function inflate() does not update strm.adler
+in case DFLTCC is used.
+ 
+  * This issue was exposed by Java Certification Kit (JCK) running on z15
+hardware and newer and impacts all JDK versions (8,11,17, etc.)
+that use the system default settings.
+ 
+  * The JCK failure impacts the ability to certify Java SDKs on this
+platform/Linux-distribution combination.
+ 
+  * On top the incorrect alder32 result may cause functional issues with
+Java applications that depend on the result.
+ 
+ [ Test Plan ]
+ 
+  * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
+on a z15/LinuxONE III or newer system is needed.
+ 
+  * Then it's possible to test the updated package with the help
+of a small test program (in C) that makes use of the zlib1g library
+or run the Java Certification Kit.
+ 
+  * Test will be done by IBM.
+ 
+ [ Where problems could occur ]
+ 
+  * The patch is a one-line change:
+https://launchpadlibrarian.net/626003193/410-lp1990379.patch
+and there are not many issues to expect.
+ 
+  * There could be a potential problem with the adler field
+in the strm struct.
+For example in case the struct is not as assumed or contains
+and unexpected value, which would then ripple through
+the other fields, too.
+ 
+  * Structural changes could be identified with a test build that was done
+for all affected Ubuntu releases and for all major architectures:
+https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379
+ 
+ [ Other Info ]
+  
+  * The patch itself is the same for all zlib version in
+20.04, 22.04 and 22.10 - no further adjustments were needed.
+ __
+ 
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.
  
  Found with a JDK test.
  
  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349
  
  Updated zlib PR: https://github.com/madler/zlib/pull/410
  
  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920
  
  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620
  
  Ubuntu 20.04 and later need to be fixed.

** Changed in: zlib (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  

[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-28 Thread Frank Heimes
Ok, that's a (minimal) patch that can be handled nicely, thanks Ilya!

Test packages are now being build in the following PPA
for focal/20.04, jammy/22.04 and kinetic/22.10:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379
https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379/+packages

It would be great if someone (for example 'rahil'?!) could test (probably) at 
least the focal package upfront, to ensure that the situation is really solved, 
and with that, give us confidence for the SRU process.
(Please notice that this would be on top of the official verification request 
that will come up later during the SRU process).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-27 Thread Frank Heimes
So the next step would be to get more clarity on the complexity of the patch 
that is required.
We have the (initial) PR 410 incl. in the zlib package, plus the patches from 
LP#1899621 and LP#1961427 on top.
Hence we cannot directly use the new version of PR 410: 
https://github.com/madler/zlib/pull/410
and also the zlib diff: 
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620
seems to incl. more than just the fix for 'zlib: inflate() does not update 
strm.adler if DFLTCC is used'.

For example I'm pretty sure that the modifications in contrib/s390/dfltcc.c and 
infback.c (as listed in the zlib diff) are part of the fix, but since I'm not 
the author I am unsure if this is everything that's needed.
Are the changes in the crc32 needed on top?
I think the typo fixes can be largely neglected ...

Hence can you please provide us with a patch/backport for the minimal changes 
that are needed to fix 'zlib: inflate() does not update strm.adler if DFLTCC is 
used' and that applies on top of what's already in the zlib package (obviously 
after the quilt patches were applied)?
Ideally based on the kinetic package (but the zlib packages in jammy and focal 
are pretty close, hence I assume that a backport will apply there too.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-23 Thread Frank Heimes
** Changed in: zlib (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-23 Thread Frank Heimes
Thanks for reporting this, Ilya.
Can you please elaborate about the potential impact of this issue - that 
'inflate() does not update strm.adler if DFLTCC is used'?
Especially because this is marked with severity medium, but the Ubuntu stable 
release update process (SRUs: https://wiki.ubuntu.com/StableReleaseUpdates) is 
generally in order to fix high-impact bugs.
With updating stable releases (like in this case 20.04 and 22.04) there is huge 
carefulness needed,  and especially with updating key packages and libraries 
like zlib, since zlib has significant package reverse dependencies and a huge 
amount of reverse build dependencies (both in the thousands).
Furthermore a potential update will impact multi-millions of installations, 
cross architecture, and we won't do that for a non-critical bugs, that maybe 
even only impact a small number of installations.
However, there might be a little chance to piggy-back a fix like this with a 
more severe zlib update that might come up in future.

** Changed in: zlib (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-22 Thread Frank Heimes
** 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)

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-09-22 Thread Frank Heimes
Well, I had comment #11 in mind where the 1:1.2.11.dfsg-2ubuntu1.3 was 
successfully verified on focal.
Meanwhile that version got overruled by a security update:
zlib (1:1.2.11.dfsg-2ubuntu1.3) focal-security; urgency=medium
and became 'already used', hence a new version was needed for this bug and so 
we are now at:
1:1.2.11.dfsg-2ubuntu1.4 - but it incl. the same patches.
Anyway, I'll ask to get 1:1.2.11.dfsg-2ubuntu1.4 verified again on focal.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Released
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Released
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted 

[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-09-13 Thread Frank Heimes
Hi Andreas, thanks for the verification, I'm going to adjust the tags
accordingly.

Don't worry about the potential regression, it's an automated mail based on the 
results of the autopkgtests that run automatically while processing such an SRU 
like this - and binutils trigger a lot of tests.
Such regressions can be caused by several different things, like a different 
package that is handled at the same time and triggers similar tests or a flaky 
test etc. - we deal with it.
(IF we think it's due to s390x-specific code, we may reach out to you ;-)

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Committed
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * As of today the architectural (level) name 'arch14' is used
 as CPU name for the new IBM z16 system.

   * The real name 'z16' couldn't be used until officially announced.

   * That happened meanwhile, hence we can now add and use the real
  name.

  [Test Plan]

   * Check if the same (proper) opcodes are detected on an IBM z16
 system with and without the patch.
 Since only the identification and name of a z16 system was modified.

   * Or the simplest test is probably to check
 (after having 'binutils' installed on an Ubuntu 22.04 s390x system)
 if not only:
 'as -m64 -march=arch14 --target-help'
 but also:
 'as -m64 -march=z16 --target-help'
 succeeds and leads to the same output.
 (As it does for '-march=arch13' and '-march=arch15'.)

  [Where problems could occur]

   * Issues could happen if the conditional statement that look
 for architectural / CPU name are paired wrongly, since:

   * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc.

   * If these pairs are not handled correctly,
 or the identification is erroneous
 a wrong system might be identified and wrong instructions used etc.

  [Other]

   * This is a hardware enablement SRU to enhance the IBM z16 support.

  __

  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.

  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.

  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-09-12 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Released
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Released
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-09-05 Thread Frank Heimes
Thx Iliya! (updating tag accordingly)

** Tags removed: verification-needed verification-needed-focal 
verification-needed-jammy
** Tags added: verification-done verification-done-focal verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Released
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  Fix Committed
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
    

[Touch-packages] [Bug 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)

2022-08-23 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841

Title:
  [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and
  attributes (crypto)

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in p11-kit package in Ubuntu:
  Fix Released

Bug description:
  Add support for IBM specific attributes and mechanis to the PKCS11 
client-server implementation of p11-kit to p11-kit.
  This enables customers to access IBM Z HSMs remotely via a PKCS #11 API.

  Upstream Target: p11-kit 0.25.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)

2022-08-23 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841

Title:
  [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and
  attributes (crypto)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in p11-kit package in Ubuntu:
  Fix Committed

Bug description:
  Add support for IBM specific attributes and mechanis to the PKCS11 
client-server implementation of p11-kit to p11-kit.
  This enables customers to access IBM Z HSMs remotely via a PKCS #11 API.

  Upstream Target: p11-kit 0.25.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-08-23 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Committed
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * As of today the architectural (level) name 'arch14' is used
 as CPU name for the new IBM z16 system.

   * The real name 'z16' couldn't be used until officially announced.

   * That happened meanwhile, hence we can now add and use the real
  name.

  [Test Plan]

   * Check if the same (proper) opcodes are detected on an IBM z16
 system with and without the patch.
 Since only the identification and name of a z16 system was modified.

   * Or the simplest test is probably to check
 (after having 'binutils' installed on an Ubuntu 22.04 s390x system)
 if not only:
 'as -m64 -march=arch14 --target-help'
 but also:
 'as -m64 -march=z16 --target-help'
 succeeds and leads to the same output.
 (As it does for '-march=arch13' and '-march=arch15'.)

  [Where problems could occur]

   * Issues could happen if the conditional statement that look
 for architectural / CPU name are paired wrongly, since:

   * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc.

   * If these pairs are not handled correctly,
 or the identification is erroneous
 a wrong system might be identified and wrong instructions used etc.

  [Other]

   * This is a hardware enablement SRU to enhance the IBM z16 support.

  __

  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.

  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.

  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-08-23 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  Fix Committed
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * The latest glibc uses DT_RELR relocations,
 but it turned out that the linker support is still incomplete,
 as of binutils-2.38-3ubuntu1 on Ubuntu 22.04.

   * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc
  addresses'.

   * As discussed at the binutils mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/119921.html
 this fixes several (glibc) regressions (from 574 to 17).

   * Instead of stashing r_offset final address calculations in
 ppc64_elf_size_stubs for use by ppc64_elf_build_stubs,
 section/offset pairs need to be kept.

  [Test Plan]

   * Build and run the official (make) check:
 git clone git://sourceware.org/git/glibc.git
 mkdir build && cd build
 ../glibc/configure --prefix=/usr && make -j8 && make check

  [Where problems could occur]

   * In case relr_addr is not replaced everywhere it's deletion in
 elf64-ppc.c can cause problems, which will mainly occur at build time.

   * The relr section/offset array may lead to problems if the array is not
 properly handled or used.

   * The rewrite of append_relr_off may cause issues due to wrong allocs
 erroneous pointer arithmetic or array handling.

   * The entirely new sort_relr function may introduce new code issues
 or performance issues.

   * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to
 the new relr code could be done wrong
 in which case the linker support is still not working.

   * But the patch was discussed at the upstream mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921

   * and is limited to ppc, and even to file 'elf64-ppc.c'.
  __

  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:

  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html

  Contact Information = Matheus Castanho/mscasta...@ibm.com

  ---uname output---
  N/A

  Machine Type = N/A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check

  Userspace tool common name: binutils

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Userspace tool obtained from project website:  na

  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)

2022-08-22 Thread Frank Heimes
Had to re-upload the debdiff - now with fixed URLs in the Origin, section of 
the DEP3 header.
(Notice the prefix 'new_' in the new version ...)

** Patch added: 
"new_debdiff_p11-kit_kinetic_from_0.24.1-1_to_0.24.1-1ubuntu1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1982841/+attachment/5610777/+files/new_debdiff_p11-kit_kinetic_from_0.24.1-1_to_0.24.1-1ubuntu1.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841

Title:
  [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and
  attributes (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in p11-kit package in Ubuntu:
  In Progress

Bug description:
  Add support for IBM specific attributes and mechanis to the PKCS11 
client-server implementation of p11-kit to p11-kit.
  This enables customers to access IBM Z HSMs remotely via a PKCS #11 API.

  Upstream Target: p11-kit 0.25.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1987062] [NEW] console-setup.sh is causing setfont: ERROR kdfontop.c: put_font_piofontx: ioctl(PIO_FONTX)

2022-08-19 Thread Frank Heimes
Public bug reported:

On 22.04.1 I've noticed the following error in systlog:

Aug 16 06:19:15 s1lp10 console-setup.sh[783]: setfont: ERROR kdfontop.c:266 
put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for 
device
Aug 16 06:19:15 s1lp10 console-setup.sh[786]: setfont: ERROR kdfontop.c:266 
put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for 
device

(It happened for me on a s390x system, but I saw at least one report of
it on amd64 in March 2022 [https://forum.ubuntu-
fr.org/viewtopic.php?id=2070514], hence I believe it's not architecture
specific).

** Affects: console-setup (Ubuntu)
 Importance: Medium
 Assignee: Canonical Foundations Team (canonical-foundations)
 Status: New


** Tags: jammy s390x

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1987062

Title:
  console-setup.sh is causing setfont: ERROR kdfontop.c:
  put_font_piofontx: ioctl(PIO_FONTX)

Status in console-setup package in Ubuntu:
  New

Bug description:
  On 22.04.1 I've noticed the following error in systlog:

  Aug 16 06:19:15 s1lp10 console-setup.sh[783]: setfont: ERROR kdfontop.c:266 
put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for 
device
  Aug 16 06:19:15 s1lp10 console-setup.sh[786]: setfont: ERROR kdfontop.c:266 
put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for 
device

  (It happened for me on a s390x system, but I saw at least one report
  of it on amd64 in March 2022 [https://forum.ubuntu-
  fr.org/viewtopic.php?id=2070514], hence I believe it's not
  architecture specific).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1987062/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-08-17 Thread Frank Heimes
libnettle8 3.8.1-2 finally landed in kinetic,
hence updating the status to Fix Released and closing this ticket.

** Changed in: nettle (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
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in nettle package in Ubuntu:
  Fix Released
Status in nettle package in Debian:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-08-13 Thread Frank Heimes
Meanwhile libnettle8 3.8.1-2 landed in kinetic-proposed, hence updating status 
to Fix Committed.
(thx to Magnus Holmgren)

** Changed in: nettle (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in nettle package in Ubuntu:
  Fix Committed
Status in nettle package in Debian:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-08-08 Thread Frank Heimes
Regarding zlib focal-proposed migration:

For libbio-samtools-perl it's the same situation like on kinetic.
samtools-legacy requires the PR #1258, and libbio-samtools-perl a rebuild (to 
link against the new libbio-dev). See update-excuse bug LP#1983255.

On top vcftools misses the 'Remove compressBound assertions' (PR #1258) fix as 
well.
I created a separate update-execuse bug LP#1983867.

The mentioned issue with htslib/1.10.2-3 is because the patched htslib 
1.10.2-3ubuntu0.1 (that again incl. PR #1258) is needed:
https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#htslib

This htslib 1.10.2-3ubuntu0.1 will at least solve kallisto, libtabixpp
and probably samtools as well.

The isues with the kernels linux-hwe-5.11, linux-hwe-5.13 and linux-
hwe-5.15 are all time outs on arm64, resspectively amrhf builds. So it's
worth to retrigger these.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  Fix Committed
Status in zlib source package in Focal:
  Fix Committed
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  

[Touch-packages] [Bug 1982841] Re: [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and attributes (crypto)

2022-08-05 Thread Frank Heimes
The requested commits/patches were added and test packages '0.24.1-1ubuntu1' 
were build in PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1982841/+packages

The builds also trigger intensive tests, that were all successful:
Testsuite summary for p11-kit 0.24.1

# TOTAL: 762
# PASS:  762
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
(https://launchpadlibrarian.net/616683202/buildlog_ubuntu-kinetic-s390x.p11-kit_0.24.1-1ubuntu1_BUILDING.txt.gz)

Attaching a debdiff for kinetic as patch.

** Patch added: "debdiff p11-kit kinetic from 0.24.1-1 to 0.24.1-1ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1982841/+attachment/5607146/+files/debdiff_p11-kit_kinetic_from_0.24.1-1_to_0.24.1-1ubuntu1.diff

** Changed in: p11-kit (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

** Changed in: p11-kit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: New => In Progress

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841

Title:
  [22.10 FEAT] [SEC2210] p11-kit: add IBM specific mechanisms and
  attributes (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in p11-kit package in Ubuntu:
  In Progress

Bug description:
  Add support for IBM specific attributes and mechanis to the PKCS11 
client-server implementation of p11-kit to p11-kit.
  This enables customers to access IBM Z HSMs remotely via a PKCS #11 API.

  Upstream Target: p11-kit 0.25.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982841/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-08-05 Thread Frank Heimes
There is now a solution for LP#1983255.

Meanwhile I've noticed that gdcm is now flagged as a new regression for
zlib's proposed miration at 'update excuses' (was not the case before).

Found that this happened on Debian too:
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1863513.html
(with exactly the same error: 
https://ci.debian.net/data/autopkgtest/testing/s390x/g/gdcm/23826805/log.gz)
but seems to be solved meanwhile: https://qa.debian.org/excuses.php?package=gdcm
So can obviously be solved by an update from (Ubuntu) 3.0.13-2 to (Debian) 
3.0.13-3 (sync),
( according to changelog: 
https://metadata.ftp-master.debian.org/changelogs//main/g/gdcm/gdcm_3.0.13-3_changelog
 )

Just noticed that it was already synched a few hours ago:
"3.0.13-3 release (universe) 19 hours ago"
(https://launchpad.net/ubuntu/+source/gdcm)

So I assume it's a matter of time until update-excuses reflects this
gdcm update and get's again rid of the regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, 

[Touch-packages] [Bug 1983128] Re: linux-lowlatency fals to build on arm64 due to kernel option settings

2022-08-02 Thread Frank Heimes
So yes, this is a new feature / kernel option for (arm only) introduced with 
the migration to gcc 12:
[v3,1/2] AARCH64: Add gcc Shadow Call Stack support
https://patchwork.kernel.org/project/linu
x-hardening/patch/20220303074323.86282-1-ashim...@linux.alibaba.com/#24774364

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1983128

Title:
  linux-lowlatency fals to build on arm64 due to kernel option settings

Status in linux-lowlatency package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression':
  "autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: 
Regression ♻"

  The regression is highly likely not due to zlib itself, but due to NEW kernel 
options, that don't have a default yet and a check-config FAIL, see:
  ...
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config: 
loading config
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations 
loading annotations
  check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
   -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
  check-config: 11323/11324 checks passed -- exit 1
  ...
  Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
  Error in reading or end of file.
  ...
  Initialize kernel stack variables at function entry
  > 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
    2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
    3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
  choice[1-3?]:
  Error in reading or end of file.
  ...

  Full log is here:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz

  (this might be caused by the recent compiler update)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1983128/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-08-01 Thread Frank Heimes
Looks like libbam-dev is the reason for the libbio-samtools-perl regression
on s390x. libbam-dev is used by libbio-samtools-perl and build based on it's
source package samtools-legacy, which includes another version of bgzf,
that misses the 'Remove compressBound assertions' (PR #1258) fix.

Problematic is that the code differs quite a bit from the one in the htslib
or bedtools package (no bgzf_hopen etc. - looks pretty much out of date),
so the PR does not apply cleanly.

According to upstream 'https://github.com/lh3/samtools-legacy' the project
is "For testing only." and marked as "DON'T USE!" and it's last update
is from Nov 9, 2013.
I've created a separate 'update-excuse' but for this: LP#1983255

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-07-29 Thread Frank Heimes
zlib 1:1.2.11.dfsg-2ubuntu10 is stuck in kinetic-proposed for some time:

http://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#zlib
https://wiki.ubuntu.com/ProposedMigration

Several of the initial regressions were due to timeouts and network
issues and are solved meanwhile. Two (red) regressions are left (aot):

I opened LP#1983128 for:
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: Regression 
♻"

and due to:
"autopkgtest for libbio-samtools-perl/1.43-3build2: amd64: Pass, arm64: Pass, 
armhf: Pass, ppc64el: Pass, s390x: Regression ♻"
I re-ran the autopkgtest (using LXD) for libbio-samtools-perl explicitly on 
s390x (using the zlib PPA) which worked fine for me (see attachemnt),
hence I'm going to ask for a re-run. (I don't have permissions yet to 
re-trigger it myself.)

(While looking into libbio-samtools-perl and other related packages, I
found that there is yet another htslib bundled in tabix - which is not
great. But this at at least already the needed patch.)

** Attachment added: "autopkgtest_local_for_libbio-samtools-perl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1961427/+attachment/5605907/+files/autopkgtest_local_for_libbio-samtools-perl.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and 

[Touch-packages] [Bug 1983128] [NEW] linux-lowlatency fals to build on arm64 due to kernel option settings

2022-07-29 Thread Frank Heimes
Public bug reported:

The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression':
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: Regression 
♻"

The regression is highly likely not due to zlib itself, but due to NEW kernel 
options, that don't have a default yet and a check-config FAIL, see:
...
check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config: 
loading config
check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations 
loading annotations
check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
 -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
check-config: 11323/11324 checks passed -- exit 1
...
Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
Error in reading or end of file.
...
Initialize kernel stack variables at function entry
> 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
  2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
  3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
choice[1-3?]:
Error in reading or end of file.
...

Full log is here:
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz

(this might be caused by the recent compiler update)

** Affects: linux-lowlatency (Ubuntu)
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: zlib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kinetic update-excuse

** Attachment added: "log.gz"
   https://bugs.launchpad.net/bugs/1983128/+attachment/5605906/+files/log.gz

** Also affects: zlib (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression'.
+ The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression':
+ "autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: 
Regression ♻"
+ 
  The regression is highly likely not due to zlib itself, but due to NEW kernel 
options, that don't have a default yet and a check-config FAIL, see:
- 
  ...
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config: 
loading config
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations 
loading annotations
- check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64': 
-  -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
+ check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
+  -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
  check-config: 11323/11324 checks passed -- exit 1
  ...
- Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW) 
+ Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
  Error in reading or end of file.
  ...
  Initialize kernel stack variables at function entry
  > 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
-   2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
-   3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
- choice[1-3?]: 
+   2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
+   3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
+ choice[1-3?]:
  Error in reading or end of file.
  ...
  
  Full log is here:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz
  
  (this might be caused by the recent compiler update)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1983128

Title:
  linux-lowlatency fals to build on arm64 due to kernel option settings

Status in linux-lowlatency package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  New

Bug description:
  The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a 
kinetic-proposed migration process (for zlib) and runs into a 'regression':
  "autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: 
Regression ♻"

  The regression is highly likely not due to zlib itself, but due to NEW kernel 
options, that don't have a default yet and a check-config FAIL, see:
  ...
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config: 
loading config
  check-config: 
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations 
loading annotations
  check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
   -, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-07-21 Thread Frank Heimes
I've noticed that the updated zlib for kinetic just landed in -proposed:
"zlib | 1:1.2.11.dfsg-2ubuntu10  | kinetic-proposed"
hence I'm updating the corresponding entry to Fix Committed.

** Changed in: zlib (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  Fix Released
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Fix Committed
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-07-21 Thread Frank Heimes
zlib debdiffs for kinetic, jammy and focal (latest, with proper dep3)

** Patch removed: "zlib debdiffs for jammy and kinetic (latest)"
   
https://bugs.launchpad.net/ubuntu/+source/htslib/+bug/1961427/+attachment/5604504/+files/debdiffs_J_K.tar.gz

** Attachment added: "zlib debdiffs for kinetic, jammy and focal (latest)"
   
https://bugs.launchpad.net/ubuntu/+source/htslib/+bug/1961427/+attachment/5604515/+files/debdiffs_K_J_F.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-07-21 Thread Frank Heimes
Since the zlib package progressed meanwhile due to a security update, I
created new debdiffs for jammy and kinetic - see debdiffs_J_K.tar.gz.

** Attachment added: "zlib debdiffs for jammy and kinetic (latest)"
   
https://bugs.launchpad.net/ubuntu/+source/htslib/+bug/1961427/+attachment/5604504/+files/debdiffs_J_K.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     

[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-19 Thread Frank Heimes
** Bug watch added: Debian Bug tracker #1015346
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015346

** Also affects: nettle (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015346
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress
Status in nettle package in Debian:
  Unknown

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-07-19 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  In Progress
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  In Progress
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * As of today the architectural (level) name 'arch14' is used
 as CPU name for the new IBM z16 system.

   * The real name 'z16' couldn't be used until officially announced.

   * That happened meanwhile, hence we can now add and use the real
  name.

  [Test Plan]

   * Check if the same (proper) opcodes are detected on an IBM z16
 system with and without the patch.
 Since only the identification and name of a z16 system was modified.

   * Or the simplest test is probably to check
 (after having 'binutils' installed on an Ubuntu 22.04 s390x system)
 if not only:
 'as -m64 -march=arch14 --target-help'
 but also:
 'as -m64 -march=z16 --target-help'
 succeeds and leads to the same output.
 (As it does for '-march=arch13' and '-march=arch15'.)

  [Where problems could occur]

   * Issues could happen if the conditional statement that look
 for architectural / CPU name are paired wrongly, since:

   * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc.

   * If these pairs are not handled correctly,
 or the identification is erroneous
 a wrong system might be identified and wrong instructions used etc.

  [Other]

   * This is a hardware enablement SRU to enhance the IBM z16 support.

  __

  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.

  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.

  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-07-19 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  In Progress
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Jammy:
  In Progress
Status in binutils source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * The latest glibc uses DT_RELR relocations,
 but it turned out that the linker support is still incomplete,
 as of binutils-2.38-3ubuntu1 on Ubuntu 22.04.

   * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc
  addresses'.

   * As discussed at the binutils mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/119921.html
 this fixes several (glibc) regressions (from 574 to 17).

   * Instead of stashing r_offset final address calculations in
 ppc64_elf_size_stubs for use by ppc64_elf_build_stubs,
 section/offset pairs need to be kept.

  [Test Plan]

   * Build and run the official (make) check:
 git clone git://sourceware.org/git/glibc.git
 mkdir build && cd build
 ../glibc/configure --prefix=/usr && make -j8 && make check

  [Where problems could occur]

   * In case relr_addr is not replaced everywhere it's deletion in
 elf64-ppc.c can cause problems, which will mainly occur at build time.

   * The relr section/offset array may lead to problems if the array is not
 properly handled or used.

   * The rewrite of append_relr_off may cause issues due to wrong allocs
 erroneous pointer arithmetic or array handling.

   * The entirely new sort_relr function may introduce new code issues
 or performance issues.

   * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to
 the new relr code could be done wrong
 in which case the linker support is still not working.

   * But the patch was discussed at the upstream mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921

   * and is limited to ppc, and even to file 'elf64-ppc.c'.
  __

  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:

  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html

  Contact Information = Matheus Castanho/mscasta...@ibm.com

  ---uname output---
  N/A

  Machine Type = N/A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check

  Userspace tool common name: binutils

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Userspace tool obtained from project website:  na

  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-18 Thread Frank Heimes
Here is the debdiff for this version bump (from
3.7.3-1build2_to_3.8-0ubuntu1).

** Patch added: "debdiff_nettle_3.7.3-1build2_to_3.8-0ubuntu1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1959469/+attachment/5603732/+files/debdiff_nettle_3.7.3-1build2_to_3.8-0ubuntu1.diff

** Changed in: nettle (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-18 Thread Frank Heimes
Since the symbol files are a bit tricky in this case (because the incl.
arch-specific entries), I'm uploading them here separately, too.

** Attachment added: "updated_symbols.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1959469/+attachment/5603726/+files/updated_symbols.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-07-14 Thread Frank Heimes
** Attachment removed: "reverse dependencies, gathered on focal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1961427/+attachment/5597497/+files/reverse%20dependencies%2C%20gathered%20on%20focal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
    

[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-07-11 Thread Frank Heimes
** Description changed:

+ SRU Justification:
+ ==
+ 
+ [Impact]
+ 
+  * The latest glibc uses DT_RELR relocations,
+but it turned out that the linker support is still incomplete,
+as of binutils-2.38-3ubuntu1 on Ubuntu 22.04.
+ 
+  * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc addresses'.
+ 
+  * As discussed at the binutils mailing list:
+https://sourceware.org/pipermail/binutils/2022-March/119921.html
+this fixes several (glibc) regressions (from 574 to 17).
+ 
+  * Instead of stashing r_offset final address calculations in
+ppc64_elf_size_stubs for use by ppc64_elf_build_stubs,
+section/offset pairs need to be kept.
+ 
+ [Test Plan]
+ 
+  * Build and run the official (make) check:
+git clone git://sourceware.org/git/glibc.git
+mkdir build && cd build
+../glibc/configure --prefix=/usr && make -j8 && make check
+ 
+ [Where problems could occur]
+ 
+  * In case relr_addr is not replaced everywhere it's deletion in
+elf64-ppc.c can cause problems, which will mainly occur at build time.
+ 
+  * The relr section/offset array may lead to problems if the array is not
+properly handled or used.
+ 
+  * The rewrite of append_relr_off may cause issues due to wrong allocs
+erroneous pointer arithmetic or array handling.
+ 
+  * The entirely new sort_relr function may introduce new code issues
+or performance issues.
+ 
+  * The adjustments of ppc64_elf_size_stubs and ppc64_elf_build_stubs to
+the new relr code could be done wrong
+in which case the linker support is still not working.
+ 
+  * But the patch was discussed at the upstream mailing list:
+https://sourceware.org/pipermail/binutils/2022-March/thread.html#119921
+ 
+  * and is limited to ppc, and even to file 'elf64-ppc.c'.
+ __
+ 
  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:
-  
+ 
  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858
  
  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html
-  
- Contact Information = Matheus Castanho/mscasta...@ibm.com 
-  
+ 
+ Contact Information = Matheus Castanho/mscasta...@ibm.com
+ 
  ---uname output---
  N/A
-  
- Machine Type = N/A 
-  
+ 
+ Machine Type = N/A
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  git clone git://sourceware.org/git/glibc.git
+  git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check
-  
- Userspace tool common name: binutils 
-  
- The userspace tool has the following bit modes: 64-bit 
+ 
+ Userspace tool common name: binutils
+ 
+ The userspace tool has the following bit modes: 64-bit
  
  Userspace rpm: binutils
  
- Userspace tool obtained from project website:  na 
-  
+ Userspace tool obtained from project website:  na
+ 
  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  New
Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New
Status in binutils source package in Kinetic:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

   * The latest glibc uses DT_RELR relocations,
 but it turned out that the linker support is still incomplete,
 as of binutils-2.38-3ubuntu1 on Ubuntu 22.04.

   * It lacks the fix/commit 'PowerPC64 DT_RELR relative reloc
  addresses'.

   * As discussed at the binutils mailing list:
 https://sourceware.org/pipermail/binutils/2022-March/119921.html
 this fixes several (glibc) regressions (from 574 to 17).

   * Instead of stashing r_offset final address calculations in
 ppc64_elf_size_stubs for use by ppc64_elf_build_stubs,
 section/offset pairs need to be kept.

  [Test Plan]

   * Build and run the official (make) check:
 git clone git://sourceware.org/git/glibc.git
 mkdir build && cd build
 ../glibc/configure --prefix=/usr && make -j8 && make check

  [Where problems could occur]

   * In case relr_addr is not replaced everywhere it's deletion in
 elf64-ppc.c can cause problems, which will mainly occur at build time.

   * The relr section/offset array may lead to problems if the array is not
 properly handled or 

[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-07-11 Thread Frank Heimes
** Description changed:

+ SRU Justification:
+ ==
+ 
+ [Impact]
+ 
+  * As of today the architectural (level) name 'arch14' is used
+as CPU name for the new IBM z16 system.
+ 
+  * The real name 'z16' couldn't be used until officially announced.
+ 
+  * That happened meanwhile, hence we can now add and use the real name.
+ 
+ [Test Plan]
+ 
+  * Check if the same (proper) opcodes are detected on an IBM z16
+system with and without the patch.
+Since only the identification and name of a z16 system was modified.
+ 
+  * Or the simplest test is probably to check
+(after having 'binutils' installed on an Ubuntu 22.04 s390x system)
+if not only:
+'as -m64 -march=arch14 --target-help'
+but also:
+'as -m64 -march=z16 --target-help'
+succeeds and leads to the same output.
+(As it does for '-march=arch13' and '-march=arch15'.)
+ 
+ [Where problems could occur]
+ 
+  * Issues could happen if the conditional statement that look
+for architectural / CPU name are paired wrongly, since:
+ 
+  * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc.
+ 
+  * If these pairs are not handled correctly,
+or the identification is erroneous
+a wrong system might be identified and wrong instructions used etc.
+ 
+ [Other]
+ 
+  * This is a hardware enablement SRU to enhance the IBM z16 support.
+ 
+ __
+ 
  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:
  
  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)
  
- IBM zSystems: Add support for z16 as CPU name.
- 
- So far z16 was identified as arch14. After the machine has been
- announced we can now add the real name.
- 
- (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
- (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)
+ IBM zSystems: Add support for z16 as CPU name.
+ 
+ So far z16 was identified as arch14. After the machine has been
+ announced we can now add the real name.
+ 
+ (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
+ (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  New
Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New
Status in binutils source package in Kinetic:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

   * As of today the architectural (level) name 'arch14' is used
 as CPU name for the new IBM z16 system.

   * The real name 'z16' couldn't be used until officially announced.

   * That happened meanwhile, hence we can now add and use the real
  name.

  [Test Plan]

   * Check if the same (proper) opcodes are detected on an IBM z16
 system with and without the patch.
 Since only the identification and name of a z16 system was modified.

   * Or the simplest test is probably to check
 (after having 'binutils' installed on an Ubuntu 22.04 s390x system)
 if not only:
 'as -m64 -march=arch14 --target-help'
 but also:
 'as -m64 -march=z16 --target-help'
 succeeds and leads to the same output.
 (As it does for '-march=arch13' and '-march=arch15'.)

  [Where problems could occur]

   * Issues could happen if the conditional statement that look
 for architectural / CPU name are paired wrongly, since:

   * 'z16' belongs to 'arch14', 'z15' to 'arch13', etc.

   * If these pairs are not handled correctly,
 or the identification is erroneous
 a wrong system might be identified and wrong instructions used etc.

  [Other]

   * This is a hardware enablement SRU to enhance the IBM z16 support.

  __

  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.

  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.

  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-07-11 Thread Frank Heimes
** Changed in: binutils (Ubuntu Jammy)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: binutils (Ubuntu Kinetic)
   Importance: Undecided => Medium

** Changed in: binutils (Ubuntu Jammy)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  New
Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New
Status in binutils source package in Kinetic:
  New

Bug description:
  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.
  
  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.
  
  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-07-11 Thread Frank Heimes
** Changed in: binutils (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: binutils (Ubuntu Kinetic)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

** Changed in: binutils (Ubuntu Jammy)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  New
Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New
Status in binutils source package in Kinetic:
  New

Bug description:
  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:
   
  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html
   
  Contact Information = Matheus Castanho/mscasta...@ibm.com 
   
  ---uname output---
  N/A
   
  Machine Type = N/A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check
   
  Userspace tool common name: binutils 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: binutils

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-08 Thread Frank Heimes
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-07-06 Thread Frank Heimes
Just to clarify - only 21.10/impish got dropped.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-16 Thread Frank Heimes
You are right, these are 'just' fixes w/o ABI changes and I am not aware 
(couldn't find) of any cases of static linkages - I apologize.
So fortunately the complexity of this will be far less.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in htslib source package in Impish:
  Invalid
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-15 Thread Frank Heimes
Thx for the retest!
With that I would go from Incomplete back to In Progress ...

** Changed in: ubuntu-z-systems
   Status: Incomplete => In Progress

** Changed in: zlib (Ubuntu)
   Status: Incomplete => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in htslib source package in Impish:
  Invalid
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
   

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-15 Thread Frank Heimes
I would like to proceed on this (to not loose to much time...)

To sum things up:

On top of the actual zlib fix,
there is another patch 'Remove compressBound assertions. (PR #1258)'
needed for htslib.
Unfortunately there is a standalone 'htslib' package,
as well as a htslib version included in (some) 'bedtools' packages.
Both need to be patched.
The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. and embedded
htslib, hence does not need to be (actually can't be) patched.

Due to the fact that now in total 3 packages are involved and two libraries 
(zlib and htslib, well and the libraries included in bedtools), this will cause 
a bigger transition (especially for htslib in focal, and zlib itself on all 
affected Ubuntu releases).
(The transition(s) need to be planned here: 
https://people.canonical.com/~ubuntu-archive/transitions/index.html)

** Attachment added: "reverse dependencies, gathered on focal.txt"
   
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597497/+files/reverse%20dependencies%2C%20gathered%20on%20focal.txt

** Changed in: htslib (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in htslib source package in Impish:
  Invalid
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-15 Thread Frank Heimes
** Patch added: 
"debdiff_bedtools_jammy_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu0.1.patch"
   
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597489/+files/debdiff_bedtools_jammy_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu0.1.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in htslib source package in Impish:
  Invalid
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-15 Thread Frank Heimes
** Patch added: 
"debdiff_bedtools_impish_from_2.30.0+dfsg-1_to_2.30.0+dfsg-1ubuntu0.1.patch"
   
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597490/+files/debdiff_bedtools_impish_from_2.30.0+dfsg-1_to_2.30.0+dfsg-1ubuntu0.1.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in htslib source package in Impish:
  Invalid
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
   

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-15 Thread Frank Heimes
** Patch added: 
"debdiff_bedtools_kinetic_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu1.patch"
   
https://bugs.launchpad.net/ubuntu/focal/+source/bedtools/+bug/1961427/+attachment/5597488/+files/debdiff_bedtools_kinetic_from_2.30.0+dfsg-2_to_2.30.0+dfsg-2ubuntu1.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in htslib source package in Impish:
  Invalid
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-06-15 Thread Frank Heimes
** Description changed:

  SRU Justification:
  ==
  
  [Impact]
  
  * zlib: compressBound() returns an incorrect result on IBM z15 hardware.
  
  * Passing the result of compressBound() to compress() results
    in an error code.
  
  * This is because compressBound() is not adjusted for DFLTCC.
  
  [Fix]
  
  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().
  
  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
  
  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
+ 
+ * On top of this actual zlib fix, there is another patch needed:
+  'Remove compressBound assertions. (PR #1258)' for htslib.
+ 
+ * But there is a standalone 'htslib' package version, as well as a
+   htslib version included in (some) 'bedtools' packages.
+   Both need to be patched (see '[Other]' for more details).
  
  [Test Plan]
  
  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).
  
  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }
  
  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.
  
  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.
  
  [Where problems could occur]
  
  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.
  
  * The compression can become errorneous with the new changes,
    e.g. in compressBound.
  
  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.
  
  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
  
  [Other Info]
  
- * Ubuntu jammy, impish and focal are affected.
+ * Ubuntu jammy, impish and focal are affected by the zlib issue.
+ 
+ * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
+   already includes the patch,
+   hence only htslib '1.10.2' in focal needs to be patched.
+ 
+ * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
+   requires the patch,
+   but version '2.27.1+dfsg' bedtools in focal does not incl. an
+   embedded htslib, hence does not need to be (actually can't be)
+   patched.
+ 
+ * Patched version of the affected htslib and bedtools packages
+   are build and also available at this PPA:
+   https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  
+ 
  __
  
  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
  
  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

** Also affects: htslib (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: htslib (Ubuntu Impish)
   Status: New => Invalid

** Changed in: htslib (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: bedtools (Ubuntu Focal)
   

[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-06-09 Thread Frank Heimes
** Also affects: binutils (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  New
Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New
Status in binutils source package in Kinetic:
  New

Bug description:
  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.
  
  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.
  
  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-06-09 Thread Frank Heimes
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

** Changed in: glibc (Ubuntu)
   Importance: Undecided => Medium

** Package changed: glibc (Ubuntu) => binutils (Ubuntu)

** Also affects: binutils (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: binutils (Ubuntu Kinetic)
   Importance: Medium
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129

Title:
  Incomplete support for DT_RELR relocations on Ubuntu 22.04

Status in The Ubuntu-power-systems project:
  New
Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New
Status in binutils source package in Kinetic:
  New

Bug description:
  == Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
  ---Problem Description---
  Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:
   
  PowerPC64 DT_RELR relative reloc addresses
  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

  As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
  https://sourceware.org/pipermail/binutils/2022-March/119921.html
   
  Contact Information = Matheus Castanho/mscasta...@ibm.com 
   
  ---uname output---
  N/A
   
  Machine Type = N/A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   git clone git://sourceware.org/git/glibc.git
  mkdir build && cd build
  ../glibc/configure --prefix=/usr && make -j8 && make check
   
  Userspace tool common name: binutils 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: binutils

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Frank Heimes
Well, it's a bit difficult to give remote recommendation for a system in this 
state.
(Ideally I want to login to it by myself ...)

It would be good to know how many of the installed packages are still
packages from impish, and how many already from jammy.

One, may try to move forward to jammy (and forcing it),
but I think it's better to be careful and go one step back first of all.

So I would replace all occurrences of jammy in /etc/apt/sources.list back to 
impish
and do an 'apt clean' and 'apt update'.

Now I provoked a /similar/ situation like yours by manually downloading
the jammy package and force installing it:

$ wget http://launchpadlibrarian.net/592653998/libpam-modules-
bin_1.4.0-11ubuntu2_s390x.deb

$ sudo dpkg -i --force-depends ./libpam-modules-bin_1.4.0-11ubuntu2_s390x.deb
(Reading database ... 83842 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.4.0-11ubuntu2_s390x.deb ...
Unpacking libpam-modules-bin (1.4.0-11ubuntu2) over (1.3.1-5ubuntu11) ...
Setting up libpam-modules-bin (1.4.0-11ubuntu2) ...
Processing triggers for man-db (2.9.4-2) ...

After that apt full-upgrade shows the same error like on your system:

$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 
1.4.0-11ubuntu2 is installed
  Recommends: update-motd but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

Now - since we want to go back to impish - the opposite can be done to
solve the situation, means forcing the installation of the impish
package:

$ wget http://launchpadlibrarian.net/558628390/libpam-modules-
bin_1.3.1-5ubuntu11_s390x.deb

$ sudo dpkg -i --force-depends ./libpam-modules-bin_1.3.1-5ubuntu11_s390x.deb
dpkg: warning: downgrading libpam-modules-bin from 1.4.0-11ubuntu2 to 
1.3.1-5ubuntu11
(Reading database ... 83840 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.3.1-5ubuntu11_s390x.deb ...
Unpacking libpam-modules-bin (1.3.1-5ubuntu11) over (1.4.0-11ubuntu2) ...
Setting up libpam-modules-bin (1.3.1-5ubuntu11) ...
Processing triggers for man-db (2.9.4-2) ...

After that apt is happy again:

$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  apport-symptoms eatmydata libavahi-core7 libdaemon0 libeatmydata1
  libregexp-assemble-perl libwrap0 python3-debconf python3-jinja2
  python3-json-pointer python3-jsonpatch python3-jsonschema python3-markupsafe
  python3-pyrsistent python3-systemd squashfs-tools
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

(Please notice that forcing packages is usually a bad idea and can break
the packaging system, and should only be done with caution and in rare
corner cases!)

And it could be that more packages are affected and in such a 'limbo' state,
so further steps like this might be needed.

Once apt doesn't report further issues, and a
sudo apt update && sudo apt full-upgrade
runs fine and you ideally restarted the system afterwards,
it might be the time for a new "do-release-upgrade' ideally in a screen session,
in case the connection breaks and to save the output).

(But please think about a backup before doing all this )

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1977493

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in pam package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Upgrade from Ubuntu 21.10 to 22.4 fails

  I run do-release-upgrade and I got a message upgrade completed with
  errors. I rebooted the server and it is now in an undefined state
  between 21.10 and 22.04. Not all packages have been installed. I
  attach apt log and output of some commands:

  root@tuxmaker:~# cat /etc/os-release 
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish

  root@tuxmaker:~# do-release-upgrade 
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgrading.

  root@tuxmaker:~# apt 

[Touch-packages] [Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Frank Heimes
First of all I assume there was no previous attempt of doing a 'do-
release-upgrade' or even an attempt that was stopped/interrupted, or an
attempt to get the system updated in a different way, for example (in
the abs. not recommended way to) to change all 'impish' entries in
/etc/apt/sources.list to jammy or so.

Launchpad (https://launchpad.net/ubuntu/+source/pam/) clearly shows that 
21.10/impish has currently 1.3.1-5ubuntu11 (and 22.04/jammy has 
1.4.0-11ubuntu2).
A different way to check this is:
$ rmadison --arch=s390x libpam-modules | egrep "impish|jammy"
 libpam-modules | 1.3.1-5ubuntu11  | impish | s390x
 libpam-modules | 1.4.0-11ubuntu2  | jammy  | s390x
(And since no 'impish-updates' line is listed here, this particular package was 
also never updated during the impish release.)

So since your current system is (still) 21.10, it must have version 
1.3.1-5ubuntu11 installed.
$ lsb_release -cs
impish
$ apt-cache policy libpam-modules 
libpam-modules:
  Installed: 1.3.1-5ubuntu11
  Candidate: 1.3.1-5ubuntu11
  Version table:
 *** 1.3.1-5ubuntu11 500
500 http://ports.ubuntu.com/ubuntu-ports impish/main s390x Packages
100 /var/lib/dpkg/status
... but I must not have 1.4.0-11ubuntu2 installed, since this is the version of 
the 22.04 release.

Calling 'apt-cache policy libpam-modules' on your system will give a hint where 
the currently installed version was taken from.
Sharing the output of this command from your system would be interesting - in 
addition to the 'sudo apt update' and 'lsb_release -a' output and the file 
/etc/apt/sources.list.

Such a situation could have been caused if someone downloaded the jammy version 
of a package manually and (forcefully) installed it
or if someone wanted to try packages from a different release and added an 
archive line pointing to that different Ubuntu release (e.g. jammy) to the 
/etc/apt/sources.list file.

The line "'1 upgraded, 0 newly installed, 0 to remove and 1208 not
upgraded." is also very suspicious, because 1208 must be close to the
overall number of packages in your system (a default install on s390x
has about 1020 packages).

So please check that no packages are taken from an Ubuntu release other than 
the currently installed one:
$ lsb_release -cs
impish
Means check the content of /etc/apt/sources.list (and maybe further sources* 
files in that folder).
You should also monitor the output of 'sudo apt update' while updating the 
package indices and check if a wrong Ubuntu release is listed.

In case a wrong archive line is listed, fix it by editing the file and execute:
$ sudo apt clean && sudo apt update
If everything is fine now, upgrade the current system to the very latest level:
$ sudo apt full-upgrade   # or maybe: apt dist-upgrade
before re-doing the 'do-release-upgrade'.

(IF a previous do-release-upgrade broke, or an attempt was made to upgrade the 
system in a different way, the system might be in a pretty bad shape and 
difficult to fix.
And 'sudo apt-get install --fix-broken' might be needed or even a forceful 
remove of a wrong package.
Hence, as long as you have access to this system, backup any important data!)

** Changed in: ubuntu-z-systems
   Status: New => Incomplete

** Changed in: pam (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1977493

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in pam package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Upgrade from Ubuntu 21.10 to 22.4 fails

  I run do-release-upgrade and I got a message upgrade completed with
  errors. I rebooted the server and it is now in an undefined state
  between 21.10 and 22.04. Not all packages have been installed. I
  attach apt log and output of some commands:

  root@tuxmaker:~# cat /etc/os-release 
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish

  root@tuxmaker:~# do-release-upgrade 
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgrading.

  root@tuxmaker:~# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 
1.4.0-11ubuntu2 is installed

[Touch-packages] [Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Frank Heimes
** Package changed: linux (Ubuntu) => pam (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 member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1977493

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

Status in Ubuntu on IBM z Systems:
  New
Status in pam package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Upgrade from Ubuntu 21.10 to 22.4 fails

  I run do-release-upgrade and I got a message upgrade completed with
  errors. I rebooted the server and it is now in an undefined state
  between 21.10 and 22.04. Not all packages have been installed. I
  attach apt log and output of some commands:

  root@tuxmaker:~# cat /etc/os-release 
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish

  root@tuxmaker:~# do-release-upgrade 
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgrading.

  root@tuxmaker:~# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 
1.4.0-11ubuntu2 is installed
Recommends: update-motd but it is not installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

  root@tuxmaker:~# apt --fix-broken install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
libpam-modules
  The following packages will be upgraded:
libpam-modules
  1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded.
  4 not fully installed or removed.
  Need to get 0 B/279 kB of archives.
  After this operation, 1,024 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Preconfiguring packages ...
  (Reading database ... 401827 files and directories currently installed.)
  Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ...
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack):
   new libpam-modules:s390x package pre-installation script subprocess returned 
error exit status 2
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)


  Contact Information = pp...@de.ibm.com 
   
  ---uname output---
  Linux tuxmaker 5.13.0-44-generic #49-Ubuntu SMP Wed May 18 13:30:03 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = z15, 8561-701 
   
  ---boot type---
  upgade
   
  ---Kernel cmdline used to launch install---
  do-release-upgrade
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  http://ports.ubuntu.com:80/
   
  ---Point of failure---
  Other failure during installation (stage 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974056] Re: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x

2022-06-01 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1974056

Title:
  iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
  bitwise_0 fails on s390x

Status in iptables:
  Unknown
Status in Ubuntu on IBM z Systems:
  In Progress
Status in iptables package in Ubuntu:
  New

Bug description:
  In Ubuntu, we execute the full iptables shell testcases across all
  architectures.

  They seem to all pass everywhere, however

  iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
  bitwise_0

  is currently failing on s390x like so:

  command17FAIL stderr: W: [FAILED]  ././testcases/nft-
  only/0009-needless-bitwise_0: expected 0 but got 1

  i wonder if there is some endian bug, as this is currently Ubuntu's
  only big-endian architecture.

  this can be reproduced with:

  pull-lp-source iptables
  cd iptables-1.8.7/
  chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0
  cd iptables/tests/shell
  sudo ./run-tests.sh --host

To manage notifications about this bug go to:
https://bugs.launchpad.net/iptables/+bug/1974056/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2022-05-28 Thread Frank Heimes
** Changed in: lvm2 (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => 
(unassigned)

** Changed in: ubuntu-z-systems
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1874381

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-19 Thread Frank Heimes
Thx Ilya, restarted to work on this by adding updated bedtools to the
PPA ...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974115] Re: [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

2022-05-19 Thread Frank Heimes
** Package changed: linux (Ubuntu) => binutils (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: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: binutils (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical 
Foundations Team (canonical-foundations)

** Tags added: rls-kk-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115

Title:
  [UBUNTU 22.04] BINUTILS: Adding new platform name IBM z16

Status in Ubuntu on IBM z Systems:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  After the announcement support for the official machine name z16 has
  been added to binutils. Please consider picking up the following patch
  from 2.37 branch:

  commit e24d2a2d11008aa363366c1087219f3e3405782a
  (origin/binutils-2_37-branch, 2.37)

  IBM zSystems: Add support for z16 as CPU name.
  
  So far z16 was identified as arch14. After the machine has been
  announced we can now add the real name.
  
  (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c)
  (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974115/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974056] Re: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x

2022-05-18 Thread Frank Heimes
** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

** Tags added: reverse-proxy-bugzilla

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1974056

Title:
  iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
  bitwise_0 fails on s390x

Status in iptables:
  Unknown
Status in Ubuntu on IBM z Systems:
  New
Status in iptables package in Ubuntu:
  New

Bug description:
  In Ubuntu, we execute the full iptables shell testcases across all
  architectures.

  They seem to all pass everywhere, however

  iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
  bitwise_0

  is currently failing on s390x like so:

  command17FAIL stderr: W: [FAILED]  ././testcases/nft-
  only/0009-needless-bitwise_0: expected 0 but got 1

  i wonder if there is some endian bug, as this is currently Ubuntu's
  only big-endian architecture.

  this can be reproduced with:

  pull-lp-source iptables
  cd iptables-1.8.7/
  chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0
  cd iptables/tests/shell
  sudo ./run-tests.sh --host

To manage notifications about this bug go to:
https://bugs.launchpad.net/iptables/+bug/1974056/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-10 Thread Frank Heimes
Just for the records: the standalone htslib package 1.13+ds-2build1 in jammy 
includes PR-1258 already.
(and the PPA build is finished)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-10 Thread Frank Heimes
@xnox Well, initially I was also a bit puzzled noticing that not the standalone 
htslib is used, but an embedded htslib in bedtools.
But this is also upstream the case and htslib is not the only component that is 
bundled:
$ ls ./src/utils/
BamToolsBlockedIntervals  fileTypelineFileUtilities  tabFile
BamTools-Ancillary  chromsweepgeneral NewChromsweep  ToolBase
bedFile Contexts  GenomeFile  Point  VectorOps
bedFilePE   drivergzstreamRecordOutputMgrversion
bedGraphFileFasta htslib  sequenceUtilities
BinTree FileRecordTools   KeyListOps  stringUtilities
And solving the situation for all of these will be a nighmare with a high risk 
of introducing problems on top and more difficulties on maintaining and making 
sure that the components are in place in the correct version ...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
  

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-10 Thread Frank Heimes
Ok, thx.
(and yes, the builders are currently a bit busy - just noticed the 140 jobs in 
the queue ...
guess it's a matter of maybe 2+ hours ...)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-10 Thread Frank Heimes
So, I've now created an updated bedtools package for jammy (having patched the 
bundled htslib with 515f6df-Remove-compressBound-assertions.-PR-1258.patch) for 
jammy,
and since the zlib package received some CVE patches meanwhile, I also created 
a new patched zlib version (that incl. 410-lp1961427.patch) for jammy.

@Ilya would you mind trying this combination on a z15 running jammy?
Meanwhile I will also look at the stand-alone htslib (and wonder how often 
htslib might be bundled somewhere else too ...)

Once I get your okay, I will restart this work, by patching kinetic
first and then going down the road ... (and reaching out to the
maintainer of the Debian packages, too).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-09 Thread Frank Heimes
That bundled htslib seems to make the situation a bit messy,
since bedtools does not clearly list the htslib version that was bundled or I 
can't find it (oh, maybe it's 1.9) and the commit does not apply cleanly.
So my guess is that this should be fixed in bedtools upstream first... but even 
that is not perfect, since it would fix the latest upstream version only.
Well, this needs some further discussions ...

** Also affects: bedtools (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in bedtools package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Incomplete
Status in bedtools source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  New
Status in zlib source package in Impish:
  New
Status in bedtools source package in Jammy:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-04 Thread Frank Heimes
Good to have this follow-up, indeed ...
(For a fix in htslib either a new LP bug is needed or htslib needs to be added 
to this one as 'affecting package'.)

So I did some investigations and found that the "Remove compressBound 
assertions." merge request #1258 got upstream accepted with htslib v1.13:
$ git log --oneline --grep "Remove compressBound assertions"
515f6df Remove compressBound assertions. (PR #1258)
$ git tag --contains 515f6df
1.13
1.14
1.15
1.15.1
But we already have v1.13 in the latest Ubuntu releases:
$ rmadison -a source htslib
 htslib | 0.2.0~rc3-1 | trusty/universe  | source
 htslib | 1.2.1-2ubuntu1  | xenial/universe  | source
 htslib | 1.7-2   | bionic/universe  | source
 htslib | 1.10.2-3| focal/universe   | source
 htslib | 1.13+ds-2   | impish/universe  | source
 htslib | 1.13+ds-2build1 | jammy/universe   | source
 htslib | 1.13+ds-2build1 | kinetic/universe | source

So PR #1258 is already included in the htslib version of kinetic/22.10, 
jammy/22.04 and impish/21.10 (and I even double-checked the code).
It's not included in focals/20.04 v1.10.x - and it looks like the PR cannot be 
simply applied to v1.10, since the code in v1.10 is too different - which will 
be a problem.

Since the regression was found in jammy's zlib 1.2.11.dfsg-2ubuntu8 in 
combination with 1.13+ds-2build1 - I am unsure if PR #1258 is really the fix or 
if there something else needed on top?
Any thoughts?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in zlib package in Ubuntu:
  Incomplete
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-05-04 Thread Frank Heimes
We are waiting on Ilya (iii-i) for a refined patch.
He mentioned that this can take a while ...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in zlib package in Ubuntu:
  Incomplete
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959408] Re: [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware

2022-04-07 Thread Frank Heimes
Since this LP bug is already closed as 'Fix Released', I'm afraid to say
that we need a separate LP bug on this cherry-pick.

22.04 is already past beta, hence these (minor) changes need to be added
post-GA as SRU, which should be possible, since this can be considered
as new 'hardware enablement'.

(And btw. binutils 2.3.8 made it into jammy:
binutils | 2.38-3ubuntu1   | jammy )

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1959408

Title:
  [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  BINUTILS: Support for new IBM Z Hardware

  Upstream target: binutils = 2.37

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959408/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-21 Thread Frank Heimes
** Changed in: zlib (Ubuntu Jammy)
   Status: In Progress => Incomplete

** Changed in: ubuntu-z-systems
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in zlib package in Ubuntu:
  Incomplete
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  Incomplete

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1905022] Re: [22.04 FEAT] Upgrade OpenSSL to version 3.0

2022-03-17 Thread Frank Heimes
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1905022

Title:
  [22.04 FEAT] Upgrade OpenSSL to version 3.0

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Upgrade OpenSSL to version 3.0.
  At this point in time, Alpha 8 is available, see https://www.openssl.org/.

  Just in case this package will make the deadline.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905022/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959407] Re: [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware - GDB Part

2022-03-17 Thread Frank Heimes
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1959407

Title:
  [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware - GDB Part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  BINUTILS: Support for new IBM Z Hardware

  This request will track the inclusion of the patches for this feature
  in GDB to provide the GDB disassembler support for the new
  instructions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959407/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959408] Re: [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware

2022-03-17 Thread Frank Heimes
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1959408

Title:
  [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  BINUTILS: Support for new IBM Z Hardware

  Upstream target: binutils = 2.37

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959408/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959463] Re: [22.04 FEAT] Upgrade binutils to latest version

2022-03-17 Thread Frank Heimes
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1959463

Title:
  [22.04 FEAT] Upgrade binutils to latest version

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  Upgrade binutils to latest version

  Description:
  Update binutils to latest version (2.37)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959463/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-15 Thread Frank Heimes
Sorry, the impish version needs to be of course "1.2.11.dfsg-2ubuntu7.1" - to 
keep the upgrade path working.
Here is the updated debdiff 
(debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu7.1_impish.diff).

** Patch removed: 
"debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1961427/+attachment/5569358/+files/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_impish.diff

** Patch added: 
"debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu7.1_impish.diff"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1961427/+attachment/5569372/+files/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu7.1_impish.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-15 Thread Frank Heimes
And - just for the reason of completeness - the debdiff for impish, that
is equal to the jammy debdiff, except the release name at the top line
in the changelog
(debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8).

** Patch added: "debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1961427/+attachment/5569358/+files/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_impish.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-15 Thread Frank Heimes
The patch applies cleanly not only to the impish and jammy versions, but
also to the focal version of zlib.

To be on the save side I did another test build for focal:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

And here is the focal debdiff attached
(debdiff_zlib_1.2.11.dfsg-2ubuntu1.2_to_zlib_1.2.11.dfsg-2ubuntu1.3).

** Patch added: 
"debdiff_zlib_1.2.11.dfsg-2ubuntu1.2_to_zlib_1.2.11.dfsg-2ubuntu1.3"
   
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1961427/+attachment/5569357/+files/debdiff_zlib_1.2.11.dfsg-2ubuntu1.2_to_zlib_1.2.11.dfsg-2ubuntu1.3_focal.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-15 Thread Frank Heimes
Let me check if the patch applies to the focal version, too.
A separate debdiff is needed for focal anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-15 Thread Frank Heimes
** Also affects: zlib (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Description changed:

  SRU Justification:
  ==
  
  [Impact]
  
  * zlib: compressBound() returns an incorrect result on IBM z15 hardware.
  
  * Passing the result of compressBound() to compress() results
    in an error code.
  
  * This is because compressBound() is not adjusted for DFLTCC.
  
  [Fix]
  
  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().
  
  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
  
  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
  
  [Test Plan]
  
  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).
  
  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }
  
  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.
  
  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.
  
  [Where problems could occur]
  
  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.
  
  * The compression can become errorneous with the new changes,
    e.g. in compressBound.
  
  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.
  
  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
  
  [Other Info]
  
- * Only impish and jammy are affected.
+ * Ubuntu jammy, impish and focal are affected.
  __
  
  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
  
  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix 

[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-15 Thread Frank Heimes
** Description changed:

  SRU Justification:
  ==
  
  [Impact]
  
  * zlib: compressBound() returns an incorrect result on IBM z15 hardware.
  
  * Passing the result of compressBound() to compress() results
-   in an error code.
+   in an error code.
  
  * This is because compressBound() is not adjusted for DFLTCC.
  
  [Fix]
  
  * Adjust compressBound() for DFLTCC like it's already done
-   for deflateBound().
+   for deflateBound().
  
  * Since zlib project does not accept patches at the moment,
-   the fix has been integrated into the DFLTCC pull request:
-   https://github.com/madler/zlib/pull/410
-   The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
+   the fix has been integrated into the DFLTCC pull request:
+   https://github.com/madler/zlib/pull/410
+   The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
  
  * The fix extracted out of the above is:
-   
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
+   
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
  
  [Test Plan]
  
  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
-   with Ubuntu Server 21.10 (or 22.04).
+   with Ubuntu Server 21.10 (or 22.04).
  
  * A test can be done  based on the following C test program:
-   #include 
-   #include 
-   #include 
-   int main() {
-   Bytef in_buf[128], out_buf[1024];
-   for (size_t i = 0; i < sizeof(in_buf); i++)
-   in_buf[i] = rand();
-   uLongf dest_len = compressBound(sizeof(in_buf));
-   assert(dest_len <= sizeof(out_buf));
-   int ret = compress(out_buf, _len,
-  in_buf, sizeof(in_buf));
-   assert(ret == Z_OK);
-   }
+   #include 
+   #include 
+   #include 
+   int main() {
+   Bytef in_buf[128], out_buf[1024];
+   for (size_t i = 0; i < sizeof(in_buf); i++)
+   in_buf[i] = rand();
+   uLongf dest_len = compressBound(sizeof(in_buf));
+   assert(dest_len <= sizeof(out_buf));
+   int ret = compress(out_buf, _len,
+  in_buf, sizeof(in_buf));
+   assert(ret == Z_OK);
+   }
  
  * The test needs to be done by IBM, due to the requirements
-   for the special z15 hardware.
+   for the special z15 hardware.
+ 
+ * A successful test was just completed, based on the version in jammy-
+ proposed, which is at the same code level that the impish version this
+ SRU is targeted for.
  
  [Where problems could occur]
  
  * If the adjustment of compressBound() for DFLTCC is done
-   erroneously the issue can still be present or in worst case
-   even affect Z systems other than z15 only.
- 
- * The crc table can be broken, in case the endian detection
-   or the register initialization is done wrong.
+   erroneously the issue can still be present or in worst case
+   even affect Z systems other than z15 only.
  
  * The compression can become errorneous with the new changes,
-   e.g. in compressBound.
+   e.g. in compressBound.
  
  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
-   (incl. the bit definitions), may cause various and unforseen defects.
+   (incl. the bit definitions), may cause various and unforseen defects.
  
  * Any build time issues that might have been introduced by this patch
-   can be identified by a test build; this was done and is available here:
-   https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
+   can be identified by a test build; this was done and is available here:
+   https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
  
  [Other Info]
  
  * Only impish and jammy are affected.
  __
  
  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
  
  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
  

  1   2   3   4   5   6   >