On 10/29/20 1:28 PM, L A Walsh wrote:
On 2020/10/27 14:34, Carlos E. R. wrote:
And all this, is on Leap or on Factory?
Because maybe you are trying to build an rpm prepared for Factory on a Leap machine, and in this case you may hit a problem with the new compressing program used by the new rpm, which Leap does not support.
---- I think I was supposed to post to 'opensuse@os.org', if it was leap based, yes?
No, that changed a while back, opensuse-support@o.o is the best place to ask support questions for any openSUSE Distro, opensuse-factory@o.o is no longer a place for any support questions. But given your question is closer to a development / packaging question here and or opensuse-packaging is ok.
I have a tumbleweed based install, but my machine was dead due to disk corruption on the mains and backups. Finally pulled together a mostly working copy on the backups and restored the most important stuff, but to a new main array, w/backup array still operating in degraded mode because the locate disk function seems broken on one of the two 12-disk containers I got to replace the older / in worse shape previous ones. I still lost the rpms for the binaries and sources which weren't backed up, as I they were being refreshed from downloads ... so I try grabbing the current bin+src rpms and end up with the rpm error rpm(PayloadIsζστδ)** when I try to extract any of the new rpms with my last good rpm.
Um...I don't suppose anyone thought about how users who missed a few months of internet connectivity might resync or make use of the new format rpms if they can't even install + build source-rpms. "They all seem Greek to me" (as in not something not being decipherable or understandable)
I'm not sure how much we claim to support building openSUSE rpm's as source rpm's on there own. openSUSE rpm spec files often depend on variables that are defined in project config files in open build service, as such just using rpmbuild may result in packages not building or building with different configurations. Generally we recommend people fork the package in open build service instead and then use the command line tool to build the packages. From memory to fix the issue you described I just passed --clean to osc build and it magically created me a fresh working buildroot. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B