openSUSE Packaging March 2020

packaging@lists.opensuse.org

21 participants
10 discussions

[opensuse-packaging] How to handle -doc packages?

by Ludwig Nussel

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

1 year, 10 months

[opensuse-packaging] factory_auto declines package with commented out patch

by Atri Bhattacharya

Hi, It seems factory_auto declines packages where a patch needing to be rebased is commented out from the sources entirely, yet this is the only way to avoid applying the patch when using `%autosetup`. See, for example, sr#773323 which has Patch12 marked as 'NEEDS-REBASE' and commented out. It has been duly declined. Is there any way, short of doing away with `%autosetup`, to get this through factory_auto? Thanks for any advice. [1] https://build.opensuse.org/request/show/773323 -- Atri Bhattacharya Sent from openSUSE Tumbleweed 20200214 on tp-yoga260. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years

[opensuse-packaging] Require a specific major version go1.X

by Johannes Kastl

Good morning ladies and gentlemen, is there any documentation on how to exactly require a specific version of go1.X (use go1.10, not any later version? Use go1.12 or later?)? I am (once again) new to packaging golang packages, and have some that seem to require newer versions, e.g. go1.12 or go.14. Others like git-lfs seem to not build correctly unless I tell them to build with go1.10. Not sure if this really fixes the build problems, and as I am not a go expert I cannot tell if this idea is complete bogus. Nevertheless, I'd like to try out... ;-) This seems to work: BuildRequire: go < 1.13 BuildRequire: go >= 1.12 This does not: BuildRequire: go1.12 Nope: BuildRequire: go = 1.12 (as the available version is 1.12.9 or something like that) Seems like this would be a useful information to add to https://en.opensuse.org/openSUSE:Packaging_Go (which I will update once I find out how to do that). Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)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

2 years, 1 month

[opensuse-packaging] OBS downtime on thursday

by Adrian Schröter

Hi, we will have around 30 minutes downtime for maintenance work this thursday between 07:00 and 08:00 UTC. We will upgrade our last SLE 12 server to SLE 15 and convert a database in the source server. bye adrian PS: Yes, I will add a note about that on build.o.o once I find out how :) -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 1 month

[opensuse-packaging] usage of /etc/profile.d

by Axel Braun

Hi, I used to write some alias into /etc/bash.bashrc.local : %pre #Write environment changes to /etc/bash.bashrc.local cat > /etc/bash.bashrc.local << "EOF" alias cdutil='cd /usr/bin' #(and some more...) EOF Now I was advised to use /etc/profile.d instead. This directory contains a bunch of non-executable files ending on sh, .csh, .ssh etc. So how is the procedure? create a new file myaddons.sh, write the above stuff into it and it gets processed/pulled-in automatically? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 1 month

[opensuse-packaging] Building a set of RPM packages locally

by Jakub Olczyk

Hi! I am still very new to the OBS ecosystem and I couldn't find information about building sets of packages (depending on each other) locally in a way that for example `mock` (where you can use the `--chain` option for that). Is it possible to build set of packages locally without sending the information to build.opensuse.org? I found in the documentation that building the set of packages can be done by creating them within the project, however for now I cannot do this, as they are part of a commercial program that later on will be distributed for openSUSE, I try to create a custom version specifically for this platform. Am I wrong here to assume that I need to send the information to the external service? Thanks in advance! Cheers, Jakub Olczyk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 1 month

[opensuse-packaging] Relative or absolute symlinks?

by Thorsten Kukuk

Hi, it's really great that we agree on if we want relative or absolute links and that we clearly don't test our scripts :( We have scripts which converts relative links to absolute links only to warn in the next step about absolute links: https://bugzilla.suse.com/show_bug.cgi?id=1166667 What's now correct? Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (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

2 years, 2 months

[opensuse-packaging] Python2 expulsion

by Hans-Peter Jansen

[Sorry for cross post] Dear Christophe, while I understand your strive for getting rid of Python2 builds, I have to dispute the way, it is done right now. Look at python-qt5, you added: %if 0%{?suse_version} > 1500 ExclusiveArch: do_not_build %endif for the Python2 flavor. This procedure makes it exceptionally hard for those of us, that still have to deal with Python2 legacy, since it forces us to edit each and every spec, just to remove these lines. Suggestion/RFC Create an conditional symbol at project level: %if 0%{?suse_version} > 1500 %bcond_with deprecated_python2_build %else %bcond_without deprecated_python2_build %endif and in package specs: %if ! %{with deprecated_python2_build} ExclusiveArch: do_not_build %endif This way, we get the desired default behavior, while allowing maintainers for legacy code to deal with this issue much more efficiently (on project level). We all have to deal with limited resources, therefor we need to cooperate. Seriously. Thanks for consideration/discussion, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 2 months

[opensuse-packaging] python3-base dependency problem while porting a package from different RPM distro

by Jakub Olczyk

Hi! First of all, I am sorry, if I am posting to the wrong mailing list. Please, let me know if there is a more appropriate place to post my question and I'll be on my way there. I am currently in a process of creating a package of a database product that I work on at my current job. We want to be able to provide it to openSUSE users. The package I have currently works for CentOS and I am in the process of finding the right dependencies for openSUSE. Currently, I am using Leap 15.1 and the `build` command (btw, a really solid tool!) for iterative changes in the spec file I have. Correct me if I am wrong, but it seems that I found a possible packaging bug in the repository: logging output to /var/tmp/build-root/.build.log... [ 0s] Memory limit set to 3647708KB [ 0s] Using BUILD_ROOT=/var/tmp/build-root [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] [ 0s] [ 0s] linux-4uxa started "build eurodb-9.6.spec" at Fri Mar 6 10:40:26 UTC 2020. [ 0s] [ 0s] [ 0s] processing recipe /usr/src/packages/SPECS/eurodb-9.6.spec ... [ 0s] init_buildsystem --configdir /usr/lib/build/configs --cachedir /var/cache/build --repository zypp:// /usr/src/packages/SPECS/eurodb-9.6.spec ... [ 0s] expanding package dependencies... [ 3s] Warning: distribution not specified, assuming '15.1-x86_64' (see /usr/lib/build/configs). [ 6s] expansion error [ 6s] have choice for libffi.so.7()(64bit) needed by python3-base: ghc-bootstrap libffi7 [ 6s] have choice for libffi.so.7(LIBFFI_BASE_7.0)(64bit) needed by python3-base: ghc-bootstrap libffi7 [ 6s] have choice for libffi.so.7(LIBFFI_CLOSURE_7.0)(64bit) needed by python3-base: ghc-bootstrap libffi7 [ 6s] [ 6s] linux-4uxa failed "build eurodb-9.6.spec" at Fri Mar 6 10:40:32 UTC 2020. [ 6s] Shouldn't the `ghc-bootstrap` have a dependency on `libffi7` ? I am very new to the openSUSE-way of package management (and repositories layout for that matter), could you please tell me if I am doing something wrong here? Or maybe there is some document that I have missed that might relate to my issue while building? Thank you in advance! Cheers, Jakub Olczyk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 2 months

[opensuse-packaging] python3-base dependency problem while porting a package

by Jakub Olczyk

Hi! First of all, I am sorry, if I am posting to the wrong mailing list. Please, let me know if there is a more appropriate place to post my question and I'll be on my way there. I am currently in a process of creating a package of a database product that I work on at my current job. We want to be able to provide it to openSUSE users. The package I have currently works for CentOS and I am in the process of finding the right dependencies for openSUSE. Currently, I am using Leap 15.1 and the `build` command (btw, a really solid tool!) for iterative changes in the spec file I have. Correct me if I am wrong, but it seems that I found a possible packaging bug in the repository: logging output to /var/tmp/build-root/.build.log... [ 0s] Memory limit set to 3647708KB [ 0s] Using BUILD_ROOT=/var/tmp/build-root [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] [ 0s] [ 0s] linux-4uxa started "build eurodb-9.6.spec" at Fri Mar 6 10:40:26 UTC 2020. [ 0s] [ 0s] [ 0s] processing recipe /usr/src/packages/SPECS/eurodb-9.6.spec ... [ 0s] init_buildsystem --configdir /usr/lib/build/configs --cachedir /var/cache/build --repository zypp:// /usr/src/packages/SPECS/eurodb-9.6.spec ... [ 0s] expanding package dependencies... [ 3s] Warning: distribution not specified, assuming '15.1-x86_64' (see /usr/lib/build/configs). [ 6s] expansion error [ 6s] have choice for libffi.so.7()(64bit) needed by python3-base: ghc-bootstrap libffi7 [ 6s] have choice for libffi.so.7(LIBFFI_BASE_7.0)(64bit) needed by python3-base: ghc-bootstrap libffi7 [ 6s] have choice for libffi.so.7(LIBFFI_CLOSURE_7.0)(64bit) needed by python3-base: ghc-bootstrap libffi7 [ 6s] [ 6s] linux-4uxa failed "build eurodb-9.6.spec" at Fri Mar 6 10:40:32 UTC 2020. [ 6s] Further search have indeed found that -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 2 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging March 2020