Hello Peter see my inline comments On Mon, Oct 21, 2024 at 10:10 AM Peter Czanik <peter@czanik.hu> wrote:
Hi,
I just received a request to include syslog-ng in Leap 16.0 (https://build.opensuse.org/request/show/1215878). I'd love to accept it, but before that I have a couple of questions:
- what is the process, if I want to have syslog-ng in Leap 16.0, but the current state of syslog-ng packaging does not work on Leap 16.0? If I decline now, will there be a new request soon, or I should do that once fixing packaging is ready? If yes: how?
You can decline that is fine, ideally once it's fixed please submit it to openSUSE:Leap:16.0. We might want to open bugs for such issues.
- what sle_version / suse_version should I use, when I want to enable / disable something for the syslog-ng Leap 16.0 pacakge? I guess that "%if 0%{?suse_version} > 1500" is no more just Factory...
I've updated https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto SLES / SLFO (was ALP) stopped using sle_version macro, perhaps because of past product name uncertainty. I'll raise it with them, because how else would we distinguish individual releases on a spec-level.
- how can I check which packages are heading to Leap 16.0? All three
current problems are about dependencies. Two of them are missing dependencies: libpaho-mqtt and python3-kuernetes. Are they coming to 16.0, or I should disable features building on these?
Your email basically shows the process, Max mass submits packages from Factory (of course with some filter in place). Maintainers review, they might decline/approve the submission perhaps with some comments. We'd be happy for any submissions directly from maintainers. Otherwise unprocessed SRs can be seen here: https://build.opensuse.org/staging_workflows/openSUSE:Leap:16.0
Peter
Hope it helps! -- Best regards Luboš Kocman openSUSE Leap Release Manager