Hi, I stumbled over a strange error, e.g. for https://build.opensuse.org/package/show/devel:tools:scm/rcs For the repos 15.4 and 15.5, the build error is "Nothing provides lzip", although Leap 15.4 and Leap 15.5 both have this package available. And the spec file rcs.spec does list "BuildRequires: lzip" as needed. Does anybody have a clue what is going on? Thanks, Manfred
On Aug 10 2023, Manfred Schwarb wrote:
I stumbled over a strange error, e.g. for https://build.opensuse.org/package/show/devel:tools:scm/rcs For the repos 15.4 and 15.5, the build error is "Nothing provides lzip", although Leap 15.4 and Leap 15.5 both have this package available.
The lzip package comes from openSUSE Backports, not from SLES. The project only uses the SLES subset of Leap. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Am 10.08.23 um 13:26 schrieb Andreas Schwab:
On Aug 10 2023, Manfred Schwarb wrote:
I stumbled over a strange error, e.g. for https://build.opensuse.org/package/show/devel:tools:scm/rcs For the repos 15.4 and 15.5, the build error is "Nothing provides lzip", although Leap 15.4 and Leap 15.5 both have this package available.
The lzip package comes from openSUSE Backports, not from SLES. The project only uses the SLES subset of Leap.
That is unfortunate. RCS (https://ftp.gnu.org/pub/gnu/rcs/) has started to provide tarballs exclusively with lzip-compression. And I guess other GNU projects do as well. So no OBS-building for lzip-compressed software out of the box... Is there a mechanism to selectively import such required packages into a specific package? I know the owner of devel:tools:scm could add additional repositories into the meta configuration. But is such a thing also possible for individual packages? Thanks, Manfred
On Aug 10 2023, Manfred Schwarb wrote:
I know the owner of devel:tools:scm could add additional repositories into the meta configuration. But is such a thing also possible for individual packages?
No, the repository definition is part of the project. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Am 10.08.23 um 14:35 schrieb Andreas Schwab:
On Aug 10 2023, Manfred Schwarb wrote:
I know the owner of devel:tools:scm could add additional repositories into the meta configuration. But is such a thing also possible for individual packages?
No, the repository definition is part of the project.
I feared a much. So I will simply create my own package in my home project and recompress the source. Thanks, Manfred
On Thursday 2023-08-10 15:10, Manfred Schwarb wrote:
Am 10.08.23 um 14:35 schrieb Andreas Schwab:
On Aug 10 2023, Manfred Schwarb wrote:
I know the owner of devel:tools:scm could add additional repositories into the meta configuration. But is such a thing also possible for individual packages?
No, the repository definition is part of the project.
I feared a much. So I will simply create my own package in my home project and recompress the source.
Why, do you have a fear of asking maintainers?
Am 10.08.23 um 23:41 schrieb Jan Engelhardt:
On Thursday 2023-08-10 15:10, Manfred Schwarb wrote:
Am 10.08.23 um 14:35 schrieb Andreas Schwab:
On Aug 10 2023, Manfred Schwarb wrote:
I know the owner of devel:tools:scm could add additional repositories into the meta configuration. But is such a thing also possible for individual packages?
No, the repository definition is part of the project.
I feared a much. So I will simply create my own package in my home project and recompress the source.
Why, do you have a fear of asking maintainers?
Did you respond to my typo? Should read "feared as much", of course. Not at all, but I made mixed experiences with project maintainers. There is usually a "collective" of maintainers, and nobody feels really responsible for the project. So typically you do not get an answer at all. And in this case, the answer will be (if I get an answer at all), that this is actually a more fundamental issue not limited to this particular package/project, and that they hesitate to paper over this issue therefore. Just guessing. But I filed an bugzilla entry (boo#1214167), so this doesn't get lost. Cheers, Manfred
On Thursday 2023-08-10 13:02, Manfred Schwarb wrote:
I stumbled over a strange error, e.g. for https://build.opensuse.org/package/show/devel:tools:scm/rcs For the repos 15.4 and 15.5, the build error is "Nothing provides lzip", although Leap 15.4 and Leap 15.5 both have this package available.
SLE-15.5-Base `-- SLE-15.5-Update <- devel:tools:scm is pointing here `-- SLE-15.5-Backports <- lzip is available from here `-- Leap:15.5 `-- Leap:15.5:Update
participants (3)
-
Andreas Schwab -
Jan Engelhardt -
Manfred Schwarb