openSUSE Packaging June 2020

packaging@lists.opensuse.org

18 participants
10 discussions

[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] Compiler Cache (Ccache) support in Open Build Service
by Sumit Jamgade 18 Jun '20

18 Jun '20

Hello, Long running compilation can now leverage ccache[1] to speed up the build process. This feature can be enabled per package in the project config: BuildFlags: useccahe:<packagename> example: https://build.opensuse.org/projects/home:sjamgade:branches:science:machinel… Once enabled per package, it will be enabled for all architectures and repositories. https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.prjconfig.… (grep ccache) --- The ccache tar file is collected only on *successful builds with changed result*. It is extracted for every build at /.ccache/ if enabled. This build artifact is not versioned and only the latest tar is stored. It can be downloaded from the webui or osc. https://build.opensuse.org/package/binaries/home:sjamgade:branches:science:… osc getbinaries --ccache -M standard home:sjamgade:branches:science:machinelearning tensorflow openSUSE_Tumbleweed x86_64 _ccache.tar osc getbinaries --ccache $prj $pkg $repo $arch _ccache.tar This archive can be further used for local builds too. osc build --pkg-ccache /full/path/to/_ccache.tar (please use the latest osc) --- Ccache config file is stored in /.ccache/ccache.conf and is writable by the build user. So, it could also be disabled (or configured as per package requirements) echo "disable = true" >> /.ccache/ccache.conf For possible build time comparisons: https://build.opensuse.org/packages/tensorflow:standard/job_history/home:sj… Thank you, Sumit Jamgade and OBS Team [1] - https://ccache.dev/ PS: Some packages (eg: tensorflow) need extra plumbing in spec file to enable access to /.ccache and use of ccache cmd: export CC_PREFIX=ccache; ln -s /.ccache/ ~/.ccache -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] OBS: where is "link diff"?
by Bernhard Voelker 15 Jun '20

15 Jun '20

Hi, is the functionality "link diff" gone, or where do I find it? Sometimes, when branching off from an official package to fix something, one may commit several times in the home project until the result is the wanted. Finally, before creating the submit request, I'd like to see the difference to the original package. Now, there's only the diff from one revision to another. Previously, there was the "link diff" button which then showed the differences between the linked project and the latest revision of the branched package. Has this function gone? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

Re: [opensuse-packaging] osc up incomplete
by İsmail Dönmez 10 Jun '20

10 Jun '20

On 09 Jun 10:22 2020, Axel Braun wrote: > Hi, > > when running osc up on an already checked-out package the result is > incomplete: > > docb@X1E:~/buildservice/Application:ERP:GNUHealth:Factory/trytond> osc up > At revision 89b1e20e3a692c82a8f4db407e683dc8. > docb@X1E:~/buildservice/Application:ERP:GNUHealth:Factory/trytond> dir > insgesamt 56 > -rw-r--r-- 1 docb users 1355 4. Mär 13:50 fix_werkzeug.patch > -rw-r--r-- 1 docb users 226 10. Mär 10:45 revert_werkzeug_setup.patch > -rw-r--r-- 1 docb users 10528 4. Jun 11:59 trytond.changes > -rw-r--r-- 1 docb users 3795 4. Okt 2016 trytond.conf > -rw-r--r-- 1 docb users 3801 4. Okt 2016 trytond.conf.example > -rw-r--r-- 1 docb users 585 11. Jun 2018 trytond_log.conf > -rw-r--r-- 1 docb users 470 26. Mai 2015 trytond.service > -rw-r--r-- 1 docb users 4262 4. Jun 11:59 trytond.spec > -rw-r--r-- 1 docb users 8809 15. Dez 12:38 tryton-server.README.SUSE > > -> the source tarball is missing! > Same I noticed with other projects, e.g. Application:ERP:GNUHealth:3.6/ > gnuhealth which links to Application:ERP:GNUHealth:Factory/gnuhealth, and, > after an update, still contains the old tarball locally > > > rpm -qa | grep osc > osc-0.169.1-1.1.noarch > > local system is TW > > Any idea? What does "osc st" says? - ismail -- "In this world, you must be oh so smart, or oh so pleasant. Well, for years I was smart. I recommend pleasant." SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)

3 7

[opensuse-packaging] osc up incomplete
by Axel Braun 09 Jun '20

09 Jun '20

Hi, when running osc up on an already checked-out package the result is incomplete: docb@X1E:~/buildservice/Application:ERP:GNUHealth:Factory/trytond> osc up At revision 89b1e20e3a692c82a8f4db407e683dc8. docb@X1E:~/buildservice/Application:ERP:GNUHealth:Factory/trytond> dir insgesamt 56 -rw-r--r-- 1 docb users 1355 4. Mär 13:50 fix_werkzeug.patch -rw-r--r-- 1 docb users 226 10. Mär 10:45 revert_werkzeug_setup.patch -rw-r--r-- 1 docb users 10528 4. Jun 11:59 trytond.changes -rw-r--r-- 1 docb users 3795 4. Okt 2016 trytond.conf -rw-r--r-- 1 docb users 3801 4. Okt 2016 trytond.conf.example -rw-r--r-- 1 docb users 585 11. Jun 2018 trytond_log.conf -rw-r--r-- 1 docb users 470 26. Mai 2015 trytond.service -rw-r--r-- 1 docb users 4262 4. Jun 11:59 trytond.spec -rw-r--r-- 1 docb users 8809 15. Dez 12:38 tryton-server.README.SUSE -> the source tarball is missing! Same I noticed with other projects, e.g. Application:ERP:GNUHealth:3.6/ gnuhealth which links to Application:ERP:GNUHealth:Factory/gnuhealth, and, after an update, still contains the old tarball locally > rpm -qa | grep osc osc-0.169.1-1.1.noarch local system is TW Any idea? Cheers Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Migration to /usr/libexec: openldap2
by Callum Farmer 08 Jun '20

08 Jun '20

openldap2 was one of the affected packages in Factory:Staging:A. Is it acceptable to use %if to temporarily solve the problem of it currently being %{_libdir} but after %{_libexecdir}. And what about 32bit and 64bit in /usr/libexec afterwards? Questions from Michael Ströder (openldap2 packager) Callum Farmer {gmbr3} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] Re: PPC build failures of packages using gnulib: test-float abort
by Bernhard Voelker 07 Jun '20

07 Jun '20

On 2020-06-07 17:31, Andreas Schwab wrote: > On Jun 06 2020, Bernhard Voelker wrote: > >> Any idea? > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95450 Thanks. Is this the same issue? I mean, the test program in that bug report also aborts on x86_64 while the gnulib testsuite succeeds everywhere but on ppc and ppcle. Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] PPC build failures of packages using gnulib: test-float abort
by Bernhard Voelker 06 Jun '20

06 Jun '20

Hi *, since end of May, packages using gnulib and running gnulib's testsuite are failing on ppc and ppc64le (but apparently not on ppc64), e.g. coreutils, findutils, grep. [ 1061s] ../build-aux/test-driver: line 112: 21591 Aborted "$@" > $log_file 2>&1 [ 1061s] FAIL: test-float I assume this is some fallout from the version bump to GCC-10? Unfortunately, I don't have access to a PowerPC LE host with GCC-10 (and the LE ones in gcc compile farm don't have a recent compiler available on /opt/cfarm). Any idea? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] how to solve "conflict for providers of bc" for tumbleweed-busybox-image ppc64le
by Normand 05 Jun '20

05 Jun '20

In https://build.opensuse.org/package/show/devel:kubic:containers/tumbleweed-b… there is "unresolvable" for ppc64le: "conflict for providers of bc needed by powerpc-utils, (provider bc is in conflict with busybox-misc)" I tried adding a "Prefer: bc" or "Prefer: busybox-misc" in my branch project config but that do not help. https://build.opensuse.org/projects/home:michel_mno:branches:devel:kubic:co… any suggestion ? -- Michel Normand -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] download repos rollback?
by Mathias Homann 04 Jun '20

04 Jun '20

Hi, was there some massive rollback to a backup from january on download.opensuse.org? In the actual download repos i see a lot of old content dated january 05, even of packages that have been rebuilt as recently as last night, but some repos show current content - maybe they have been rebuilt already? update repos seem unaffected, a lot under /repositories is. What happened? cheers MH -- Mathias Homann Mathias.Homann(a)openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy(a)tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

4 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging June 2020