Build problem with multi spec
Hello everyone, I have a problem and acceptance with a request for factory. I want to build a package which builds an application with different versions for Leap and Tumbleweed. First attempt was to query in spec what is built and then set the version number dynamically. Worked in the home and devel repo. But was then rejected by factory. Second try was with 3 spec and change files for Leap 15.5, 15.6 and for Tumblweed. Also worked in home and devel repo. But again factory rejects it. Factory says it has no change file. But it actually has three! What should or can I do now to have a package that builds once for Leap in version A and for Tumbleweed in version X? Regards Eric
On Freitag, 12. April 2024, 11:36:26 CEST Eric Schirra wrote:
Hello everyone,
I have a problem and acceptance with a request for factory.
I want to build a package which builds an application with different versions for Leap and Tumbleweed.
First attempt was to query in spec what is built and then set the version number dynamically. Worked in the home and devel repo. But was then rejected by factory.
Second try was with 3 spec and change files for Leap 15.5, 15.6 and for Tumblweed. Also worked in home and devel repo. But again factory rejects it. Factory says it has no change file. But it actually has three!
What should or can I do now to have a package that builds once for Leap in version A and for Tumbleweed in version X?
a bit stupid question, but why do you want to press this at all into one package source? What do you win? -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Am Freitag, 12. April 2024, 14:57:16 CEST schrieb Adrian Schröter:
On Freitag, 12. April 2024, 11:36:26 CEST Eric Schirra wrote:
Hello everyone,
I have a problem and acceptance with a request for factory.
I want to build a package which builds an application with different versions for Leap and Tumbleweed.
First attempt was to query in spec what is built and then set the version number dynamically. Worked in the home and devel repo. But was then rejected by factory.
Second try was with 3 spec and change files for Leap 15.5, 15.6 and for Tumblweed. Also worked in home and devel repo. But again factory rejects it. Factory says it has no change file. But it actually has three!
What should or can I do now to have a package that builds once for Leap in version A and for Tumbleweed in version X?
a bit stupid question, but why do you want to press this at all into one package source? What do you win?
On the one hand, I only have one package in devel. Secondly, I don't want to maintain and update two packages. At some point, Leap, or its successor, will also be more up-to-date again in order to return to the "normal" package structure. Thirdly, the package in the devel project only builds for Tumbleweed, as other packages for Leap also need to be updated. I have been using the application for several years although it does not officially build for Leap. The reason it doesn't build for Leap is that various necessary packages don't want to be updated there. Although it has zero problems. As I said, zero problems for several years. If I were to apply for a new package, they would never build it. At least not officially. But practically they do. Therefore a package. The package was also built with the latest version until recently, but since a few versions have been released, the effort would simply be far too great and would interfere deeply with the sysem, so that the application for Leap can no longer be built. However, it is much more up-to-date than the official version in Leap. I hope I was able to explain the problem and the reason to some extent. Regards Eric
participants (2)
-
Adrian Schröter -
Eric Schirra