openSUSE Packaging May 2020

packaging@lists.opensuse.org

29 participants
22 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

11 months, 1 week

[opensuse-packaging] Compiler Cache (Ccache) support in Open Build Service

by Sumit Jamgade

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

1 year

[opensuse-packaging] Is there a way to wipe old packages from a repo?

by Mathias Homann

Hi, it seems that there is "old junk" in the repo for my home project, i.e. rpm packages for stuff that I don't build in my home anymore, and that I don't even **have** there anymore. How can I get rid of the rpm packages? Cheers Mathias -- 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 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 year

[opensuse-packaging] Need help check on Veyon package before submiiting to openSUSE security team.

by andythe_great

Hello, I build Veyon package with help form malcolmlewis. https://build.opensuse.org/package/show/home:andythe_great:branches:home:lr… The RPMLINT error show E: polkit-untracked-privilege which it suggest to ask security team about it. I just want to make sure the spec file is correct before submitting to them. Some thing I am not sure is Requires(post): permissions, should I use Requires(post) or Prereq: permissions? I could not fix position-independent-executable-suggested warning even if I add -fPIE flag to it. Kind Regards, Andy -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 year

Re: [opensuse-packaging] What's happened with shared-mime-info? SOLVED

by Dave Plater

On 5/19/20, Ben Greiner <code(a)bnavigator.de> wrote: > Hi, > > > Fixed in https://build.opensuse.org/request/show/807255 > > > Am 19.05.20 um 12:40 schrieb Dave Plater: >> >> >> On 18/05/2020 17:23, Stefan Brüns wrote: >>> >>> Claiming ownership of a file below e.g./usr/share/mime/audio/ is >>> wrong, as >>> the mime type may be registered from several packages. > > > -%attr(0644,root,root) %ghost %{_datadir}/mime/audio/x-bzt.xml > -%attr(0644,root,root) %ghost %{_datadir}/mime/audio/x-bzt-xml.xml This is the developers mime creation but I see that it occurs when update-mime-database is run so should be removed. > > >> Just to make this clear, the package buzztrax which BuildRequires >> shared-mime-info which owns - /usr/share/mime/audio now fails because >> shared-mime-info no longer has ownership of this directory: >> [ 387s] buzztrax-0.10.2+git20191209-100.16.x86_64.rpm: directories >> not owned by a package: >> [ 387s] - /usr/share/mime/audio >> >> I'm surprised that such a major change in the package shared-mime-info >> wasn't documented. >> >> Thanks >> Dave P >> > > These RPMlint warnings probably need to be addressed too: > > > buzztrax-plugins.x86_64: W: desktopfile-without-binary > /usr/share/applications/buzztrax-songio-buzz.desktop buzztrax-edit > the .desktop file is for a file not present in the package. You should > check > the requires or see if this is not a error This is the package's developer's addition. > > buzztrax-plugins.x86_64: W: empty-%post > buzztrax.x86_64: W: empty-%post > buzztrax-plugins.x86_64: W: empty-%postun This is fixed, all of those macros have been null placeholders for a while now but I was wary of removing something that wasn't broken, maybe obs service should do it on checkin.. > > > > Regards, > Ben > I've found the answer to my question. The autotools version of the shared-mime-info runs update-mime-database at the end of make install, the meson version doesn't but the package does during installation. This is why, although the package creates them, they aren't owned by shared-mime-info anymore. Running update-mime-database shouldn't be run during make install, it should be run during rpm installation. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 year, 1 month

[opensuse-packaging] What's happened with shared-mime-info?

by Dave Plater

Hi, package openSUSE:Factory/buzztrax started to fail to build around 9 May due to a shared-mime-info directory no longer existing, in fact none of the files under /usr/share/mime/application exist anymore and the directories under /usr/share/mime/ such as audio don't exist anymore. I searched the changes file and the packages NEWS file but can't find any information about this change, is this possibly as a result of the switch to meson build? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 year, 1 month

[opensuse-packaging] Is OBS suspended for build?

by Konstantin Voinov

Hi, Yesterday I've found that all my projects don't starts building. Not on "rebuild trigger" or any other command. But there wasn't any announce about OBS maintenance . -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 year, 1 month

Re: [opensuse-packaging] Re: Is OBS suspended for build?

by İsmail Dönmez

Hi, On 17 May 07:16 2020, Mathias Homann wrote: > > Am 17.05.2020 um 05:20 schrieb Malcolm: > > On Sun 17 May 2020 09:49:14 AM CDT, Konstantin Voinov wrote: > > > >> Hi, > >> > >> Yesterday I've found that all my projects don't starts building. Not > >> on "rebuild trigger" or any other command. > >> But there wasn't any announce about OBS maintenance . > > Hi > > backend-home is broken for i586 and x86_64 builds, likely will get > > sorted after the weekend... > > https://build.opensuse.org/monitor > > > Is it normal to take several hours for them to start back up? A cold start is very slow, but luckily they are back up now. - ismail -- Hard work pays off in the future, but laziness pays off right now. SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)

1 year, 1 month

Re: [opensuse-packaging] Re: Is OBS suspended for build?

by İsmail Dönmez

Hi On 17 May 03:20 2020, Malcolm wrote: > On Sun 17 May 2020 09:49:14 AM CDT, Konstantin Voinov wrote: > > >Hi, > > > >Yesterday I've found that all my projects don't starts building. Not > >on "rebuild trigger" or any other command. > >But there wasn't any announce about OBS maintenance . > Hi > backend-home is broken for i586 and x86_64 builds, likely will get > sorted after the weekend... > https://build.opensuse.org/monitor Thank you for the heads up, I restarted the schedulers on back-home and they are in cold start. It'll take some time until they start processing again. I'll keep an eye on it during the day. Regards, ismail -- Hard work pays off in the future, but laziness pays off right now. SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)

1 year, 1 month

[opensuse-packaging] Trying to package pi-hole for arm boards

by Paul Gonin

Hi ! I started a new project to build pi-hole packages for arm boards (armv7l & aarch64) I found packages built in a personal space, but those are only available for x86 (and i586) https://build.opensuse.org/package/show/home:Smar:pi-hole/pi-hole So I branched it and enabled armv7l & aarch64 https://build.opensuse.org/project/show/home:paulgonin:branches:home:Smar:p… I am puzzled by the results. The builds succeeded on some cases tumbleweed armv7l & aarch64 as well as SLE15SP1 aarch64... but failed on Leap15.1 armv7l & aarch64 and SLES15SP1 armv7l Apparently some packages are 'unresolvable'. (nothing provides sususer-tools, rpm-build & gcc-PIE). I checked from a rpi2 with Leap15.1 and those packages are available (with zypper se) Any guidance from a more experienced packager / open build service on how to move forward and resolve that situation ? thanks ! Paul -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 year, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging May 2020