July 2020 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] RFC: Guidelines change: obsolete systemd requirements
by Ludwig Nussel 05 Aug '20

05 Aug '20

Hi, The section "(Build) Requirements" in https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#.28Build.29_R… is obsolete as rpm-build requires systemd-rpm-macros and the bcond is not relevant on current distros anymore. Therefore I propose to remove the section without replacement. Following the change process¹ the update will be applied if there are no strong objections within 14 days. cu Ludwig [1] https://en.opensuse.org/openSUSE:Packaging_guidelines_change_process#Proces… -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, HRB 36809 (AG Nürnberg), GF: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

11 31

[opensuse-packaging] RFC: Guidelines change: remove mention of init scripts
by Ludwig Nussel 05 Aug '20

05 Aug '20

Hi, https://en.opensuse.org/openSUSE:Packaging_guidelines#Init_scripts is a bit outdated. I propose to replace the whole section with --->8--- === Systemd Services === openSUSE uses systemd to start services. Detailed guidelines how to package service files are at [[openSUSE:Systemd_packaging_guidelines]]. --->8--- Consequently https://en.opensuse.org/openSUSE:Packaging_init_scripts needs to gain some warning that the information is obsolete. Do we have some template for that? Following the change process¹ the update will be applied if there are no strong objections within 14 days. cu Ludwig [1] https://en.opensuse.org/openSUSE:Packaging_guidelines_change_process#Proces… -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, HRB 36809 (AG Nürnberg), GF: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] Packaging Warpinator for openSUSE
by Daniel Stevenson 28 Jul '20

28 Jul '20

Hello all, I am attempting to package Linux Mint's Warpinator[1] for openSUSE and have a few questions. First of all, Clem has elected to denote versions using Git tags instead of creating release tarballs. I was (unsurprisingly) unable to find any documentation on how to build an RPM in such a situation. My best guess would be to remove the '%setup' macro from '%prep' and replace it with something like git clone %{source} ${name} cd ${name} git checkout %{version} However, I'm not entirely clear on whether the '%setup' macro handles the download (and therefore I should include the git clone), or if there is some other piece of logic I need to edit (or even _can_ edit) to retrieve the source that I would then manipulate in '%prep.' Additionally, Meson is used to configure and Ninja to build/install. The wiki page on build system recipes[2] neither provided a macro for this setup nor make any mention of it, and a general search of the wiki was similarly unhelpful. However, I'd like to make sure that I have not missed any relevant documentation before I publish a specfile that calls the build commands directly, as this seems like a fairly nonstandard thing to do. Thanks in advance for your help! 1: https://github.com/linuxmint/warpinator 2: https://en.opensuse.org/openSUSE:Build_system_recipes -- Daniel Stevenson -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 5

[opensuse-packaging] How to handle -doc packages?
by Ludwig Nussel 13 Jul '20

13 Jul '20

Hi, Some packages split out their man pages or other documentation into a sub package. More often than not that subpackage then is recommended. IOW installed by default which is undesirable. We also have a pattern for documenation though. So IMO it makes sense to link installing such documenation packages to the pattern. The question is how though. Assuming we have foo, foo-doc and patterns-base-documentation I see several ways: 1. pattern is in charge a. in patterns-base-documentation Recommends: foo-doc b. in patterns-base-documentation Recommends: foo-doc if foo 2. package is in charge a. in foo Recommends: foo-doc if patterns-base-documentation b. in foo-doc Supplements: packageand(foo:patterns-base-documentation) 1) pro: when looking at the pattern eg. in YaST one can actually see an overview of what documentation is available. con: pattern needs to be adjusted for every change in packaging. Extra step and easy to forget. 2) pro: packager can add, split, merge or drop packages any time con: package installation is a bit more black magic. The pattern leads to pulling in more packages than expected. Thoughts? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 27

[opensuse-packaging] Boolean dependencies problem
by Ralf Becker 13 Jul '20

13 Jul '20

What I'm trying to archive is quite simple and on a Debian/Ubuntu it would be: Requires: nginx || apache2 Require either Nginx or Apache, prefer Nginx unless user already have one of them installed or specified together with my package. Obviously that can only work on newer RPM distributions supporting boolean dependencies (not CentOS 7 or SLE12 for example). What I tried so far: Requires: (nginx >= 1.14 or apache2 >= 2.4) With and without Recommends or Suggests: nginx I also tried: Requires: (nginx >= 1.14 without apache or apache2 >= 2.4 without nginx) Again with or without recommending or suggesting nginx. I done more extensive tests on openSUSE Leap 15.1: - independent of the order in requires, Apache is always preferred (maybe because it's the first in alphabet ...) - recommending Nginx or specifying it together in with package causes both Apache and Nginx to be installed - an already installed Nginx would always install Apache too Is there a way with rpm / openSUSE or CentOS to archive what I need? The package is: https://build.opensuse.org/package/view_file/server:eGroupWare:trunk/egroup… I know I could create own conflicting Nginx and Apache packages doing nothing else as requiring the original packages ... Thanks for any input :) Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

6 10

[opensuse-packaging] Leap 15.2 and the ressource issues on OBS
by Mathias Homann 03 Jul '20

03 Jul '20

Hi, in the course of upgrading some systems from 15.1 to 15.2 I came across a few repos that I use that aren't available for 15.2 yet ... but are still being built for openSUSE 13 and Leap 42... Shouldn't those get cleaned up a bit? Cheers MH -- Mathias Homann Mathias.Homann(a)openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

3 2