On 10/02/2021 03.16, Simon Lees wrote:
On 2/10/21 4:18 AM, L A Walsh wrote:
On 2021/02/09 05:34, email@example.com mailto:firstname.lastname@example.org wrote:
- Component is incorrect - this is not a valid upgrade problem.
But it is an upgrade problem in that it is trying to upgrade the rpm-package that is failing from opensuse sources.
Do you mean trying to rebuild the rpm package with an old version of rpm is failing? Because i'm not sure thats something we need to support.
Yes, we do, IMHO.
Distribution ships version A of rpm, then upgrades to version B of rpm. Version B of necessity has to be built with version A installed and running.
- Bug report claims a GPL violation, but the GPLv2
(Clause 3) clearly spells out the obligation of the licensee is to distribute "all the source code for all modules it contains.
By definition opensuse claims that the src-rpm is sufficient to reproduce the binary package. If this is not the case, then the src-rpm is broken. If you feel the src-rpm is broken, you welcome to re-assign this to someone who handles the release of rpm.
With the right tooling it is sufficient, all the tooling we use is open source and you are able to download it and install it yourself if you wish.
I also believe the src rpm is the right tooling, not an OBS instance. Otherwise, IMHO we are breaking the license terms.
the rpmbuild shipped with openSUSE is the exact binary I am trying to build. You are claiming I need some specific version of rpm, like rpm-4.15-build to build rpm-4.15? Too clearly, that is not possibly. The rpm.spec is supposed to include the requirements needed to build that rpm. It doesn't specify a version of rpm.
Yep this is a minor rpm packaging bug, you could file a bug and the maintainer will fix it if they have time, alternatively it would probably take you 10 minutes to fork the package on obs fix it then resubmit it, i'm happy to help with that process if you'd like.
If my memory serves, the bug was submitted and rejected. It is a major issue for L A Walsh, her machine is not upgradeable because of this failure.
AFAIK, the machine suffered a hardware problem that blocked normal update for some time (months?). After that the existing rpm program on the machine can not handle the upgrade because it can not handle the new compression scheme, and she can not build a new rpm program on her machine, either, because of bug after bug that has been closed without solution.
That's my understanding from memory and with gaps.