Building against older versions in update repo's
Hi All, I have the need to build a packages against older versions of libraries in various update repositories. I came up with a prototype below but packages other then the current one are marked "Unresolvable" when using Build Requires against the "flavor". Is this something that should currently be possible, if not how hard would it be to implement. Unfortunately I need to preserve the NT_GNU_BUILD_ID so branching repo's and rebuilding the prexisting library then adding that project to the config isn't an option. https://build.opensuse.org/package/show/home:simotek:ulp/openssl-1_1-livepat... Thanks -- 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
On Thu, Sep 02, 2021 at 05:56:54PM +0930, Simon Lees wrote:
you can either aggregate the binaries you actually need in the same project. e.g. aggregate glibc.XXX etc. or openssl-1_1.XXXX from the update. The kernel updates e.g. repository link against SUSE:Maintenance:xxxx incidents of the associated kernel update. OR you can capture the old _buildenv and rebuild with that, which is a big hammer. Ciao, Marcus
Hi On 9/2/21 18:33, Marcus Meissner wrote:
I set up https://build.opensuse.org/project/show/home:simotek:ulp with multiple aggregated packages however when building [1] obs still only finds one version to build against (this time a different one so the aggregates do work if you just do one). To me it seems like the resolver just doesn't handle using %{flavor} in build requires properly, I guess I should create a bugreport for this. Cheers Simon 1. https://build.opensuse.org/package/show/home:simotek:ulp/openssl-1_1-livepat... -- 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
On Sep 03 2021, Simon Lees wrote:
You cannot build against multiple versions of the same package in a single repository. For each binary with a given name, there can only be a single version available for build in the same repository. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
On 9/3/21 16:46, Andreas Schwab wrote:
How hard would it be to adapt obs to overcome this limitation in some cases? Would this be a feature the obs team would be willing to look at? Into the future we will need to be doing this on a scale where creating separate repo's wont be manageable so we will likely need to work around it by copying the binaries out of the build service into one tarball then uploading them again as a secondary source of the package. This is a pretty ugly solution but its probably the only feasible one we have at the moment. Cheers -- 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
On Fri, Sep 03, 2021 at 06:35:17PM +0930, Simon Lees wrote:
That's quite a bug change in the internals of the build service. As long as this as absolutly needed by some big project that brings SUSE a lot of money we wont do that.
We need to talk about your setup. Do you really need those aggregates? Wouldn't it be better do directly address the maintenance projects in the livepatches builds? (I know that this can't be currently done in OBS, but this would be easier to change than the handling of the "useforbuild" repository.) Cheers, Michael. -- Michael Schroeder SUSE Software Solutions Germany GmbH mls@suse.de GF: Felix Imendoerffer HRB 36809, AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
participants (4)
-
Andreas Schwab
-
Marcus Meissner
-
Michael Schroeder
-
Simon Lees