Hi, I'm trying to find pcre2 for SLES 12 in the buildservice. Syslog-ng is switching to pcre2 from pcre, and SLES 12 does not include it by default. As there are still requests related to my unofficial syslog-ng repo for SLES 12, I'd like to add pcre2 to my repo, so I could keep compiling syslog-ng. On software.opensuse.org I found pcre2 in https://build.opensuse.org/package/show/devel%3Alibraries%3Ac_c%2B%2B/pcre2, but that does not seem to build for SLES 12. Clicking expert download brings me to an old source rpm download. But is there a way I could link to this old version using osc or in the web interface without downloading and re-uploading the rpm? The web interface seems to link to the very latest version. Peter
You can use osc setlinkrev to modify the link revision. -- 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 7/11/23 19:55, Andreas Schwab wrote:
You can use osc setlinkrev to modify the link revision.
Hi, Thanks! I tried this, then I also tried: osc linkpac devel:libraries:c_c++ pcre2 home:czanik:syslog-ng-githead -r 42, but both resulted in "broken" message. In the end I downloaded the old source rpm, unpacked it and uploaded it to my project, and it worked perfectly. And the latest syslog-ng git snapshot is now available for SLES 12 SP5. I must admit that I'm counting down the days until SLES 12 and RHEL 7 are finally end of life next Summer :-) But until that I try to make sure that the latest syslog-ng is available even for these ancient distro versions... Peter
On Jul 11 2023, Peter Czanik wrote:
Thanks! I tried this, then I also tried: osc linkpac devel:libraries:c_c++ pcre2 home:czanik:syslog-ng-githead -r 42, but both resulted in "broken" message.
You need to use the revision of the expanded source package (the srcmd5). You can get that from the build history. $ osc buildhist devel:libraries:c_c++ pcre2 SLE_12_SP5 x86_64 TIME SRCMD5 VER-REL.BUILD# REV DURATION 2020-01-28 08:45:43 72a5a0636df27bbf198bddd74e5e19fd 10.34-45.1 41 213 2020-04-19 12:41:37 57d57ad6210bb9a91b84a918613fa7f5 10.34-46.1 42 205 2020-04-23 08:24:47 57d57ad6210bb9a91b84a918613fa7f5 10.34-46.2 42 230 2020-04-23 08:29:31 57d57ad6210bb9a91b84a918613fa7f5 10.34-46.3 42 254 -- 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 11.07.23 at 20:19 Peter Czanik wrote:
On 7/11/23 19:55, Andreas Schwab wrote:
You can use osc setlinkrev to modify the link revision.
Thanks! I tried this, then I also tried: osc linkpac devel:libraries:c_c++ pcre2 home:czanik:syslog-ng-githead -r 42, but both resulted in "broken" message. In the end I downloaded the old source rpm, unpacked it and uploaded it to my project, and it worked perfectly. And the latest syslog-ng git snapshot is now available for SLES 12 SP5.
If the package that you are linking is a link itself, you need to use the link target and link from there. Something like "osc linkpac openSUSE:Factory pcre2 home:czanik:syslog-ng-githead -r not_42", where the revision is not 42 but the corresponding revision from the Factory package. I have not found another way to get a non-broken package in this case. -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Mittwoch, 12. Juli 2023, 08:33:26 CEST Johannes Kastl wrote:
On 11.07.23 at 20:19 Peter Czanik wrote:
On 7/11/23 19:55, Andreas Schwab wrote:
You can use osc setlinkrev to modify the link revision.
Thanks! I tried this, then I also tried: osc linkpac devel:libraries:c_c++ pcre2 home:czanik:syslog-ng-githead -r 42, but both resulted in "broken" message. In the end I downloaded the old source rpm, unpacked it and uploaded it to my project, and it worked perfectly. And the latest syslog-ng git snapshot is now available for SLES 12 SP5.
If the package that you are linking is a link itself, you need to use the link target and link from there.
Something like "osc linkpac openSUSE:Factory pcre2 home:czanik:syslog-ng-githead -r not_42", where the revision is not 42 but the corresponding revision from the Factory package.
I have not found another way to get a non-broken package in this case.
Keep in mind that the revision numbers often include a link pointing to openSUSE:Factory
head branch, so they are likely to cause conflicts.
What you can do is find the merged md5 sum (xsrcmd5) via
osc buildhist
and use that with either setlinkrev -r or copypac -r command.
--
Adrian Schroeter
On Jul 12 2023, Adrian Schröter wrote:
What you can do is find the merged md5 sum (xsrcmd5) via
osc buildhist
and use that with either setlinkrev -r or copypac -r command.
That assumes that the revision you are looking for has ever been built successfully. -- 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."
On Mittwoch, 12. Juli 2023, 09:19:54 CEST Andreas Schwab wrote:
On Jul 12 2023, Adrian Schröter wrote:
What you can do is find the merged md5 sum (xsrcmd5) via
osc buildhist
and use that with either setlinkrev -r or copypac -r command.
That assumes that the revision you are looking for has ever been built successfully.
yes
--
Adrian Schroeter
participants (5)
-
Adrian Schröter
-
Andreas Schwab
-
Andreas Schwab
-
Johannes Kastl
-
Peter Czanik