"rpm" is a universe package (and quite 'alien' on Debian/Ubuntu):
$ apt-cache policy rpm
rpm:
Installed: (none)
Candidate: 4.12.0.1+dfsg1-3build3
Version table:
4.12.0.1+dfsg1-3build3 500
500 http://archive.ubuntu.com/ubuntu xenial/universe s390 Packages
As a universe package it's community supported,
and the Ubuntu package is synch'ed over from Debian.
Hence it need to be fixed upstream and in the Debian package first.
Just as a side-note: Please keep in mind that in Ubuntu the main package
management tools are deb-packages or snaps.
Reading that rpm is used - and not knowing the exact use case - let me think
that possibly the wrong tooling is used on Ubuntu.
Standard answer for universe packages is:
This package is part of the universe section of the Ubuntu archive. Universe
packages are maintained by the community, and the maintainers do not
necessarily work for Canonical, therefore these packages are not always
directly supported by Canonical.
The existing process to update packages in the Universe archive with patches,
is as follows:
1. Upstream: Upstream your fix to the appropriate upstream project.
2. Debian: once your patch is ack’ed and accepted upstream, you need to request
a merge of this patch to the package in Debian stable.
https://www.debian.org/Bugs/Reporting use this link to report your issue and
submit a fix.
3. Ubuntu: Once it is merged into Debian stable, request a merge of this
package with Ubuntu. https://wiki.ubuntu.com/Debian/Bugs will provide you an
overview on how to handle bugs that are reported to Debian and subsequently to
Ubuntu.
- The merge request lands by default in Ubuntu's current development release
(today ‘Artful’).
- If required an SRU may follow to get the changes into already released Ubuntu
versions (like ‘Xenial’ or ‘Zesty’).
Work with the respective upstream maintainers (Debian and Ubuntu) is required
during this process. For critical issues we can advise you as you go through
this process and help push the patches through by chasing the appropriate
project contributors.
[To find out if a package is a universe package use: apt policy <package-name>.]
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709314
Title:
Unbreak size and archive size generation of built RPMs on big-endian
systems
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
We use the rpm tools version 4.12.0.1 that come with Ubuntu Xenial to build
packages.
However, that very version still has a bug:
https://github.com/rpm-software-
management/rpm/commit/104856ea17161eb3a508913c2b7ed701f2e4f6aa
On Big-Endian systems (and that's what we use), the Archive-Size field is
handled wrongly.
---uname output---
Linux mclinx 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:02 UTC 2017
s390x s390x s390x GNU/Linux
Machine Type = IBM zSeries 2964 (z13)
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Build an RPM on a 64-bit Big-Endian system on Ubuntu-Xenial and check the
Archive-Size field of the built RPM afterwards:
rpm -qp --xml example-1.3.0-1.s390x.rpm > example_1.3.0-1_rpm.xml
With the broken version you should find contents like these:
<rpmTag name="Archivesize">
<integer>0</integer>
</rpmTag>
In case the Archive-Size is lower than 4GiB you'll always see a "0" as value
here. The corrected rpmbuild command should post the correct archive size.
Userspace tool common name: rpmbuild
The userspace tool has the following bit modes: 64-bit
Userspace rpm: rpm
Userspace tool obtained from project website: na
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1709314/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
