openSUSE Build Service July 2020

buildservice@lists.opensuse.org

21 participants
16 discussions

[opensuse-buildservice] 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. (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… https://w3.nue.suse.com/~sjamgade/ccachereport.html 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-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 1 month

[opensuse-buildservice] Short OBS downtime this Saturday

by Michael Schroeder

Hi OBS users, we need to do a little database maintenance on Saturday at 21:00 UTC. The buildservice will not be available for about 30 minutes. The build service will still schedule and finish builds in that time, but the API and the Web UI will not be available. Thanks for your understanding and have a nice weekend, Michael. -- Michael Schroeder SUSE Software Solutions Germany GmbH mls(a)suse.de GF: Felix Imendoerffer HRB 36809, AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 1 month

[opensuse-buildservice] Packages have been published but don't show up on Download package page

by Roman Chistokhodov

Hello. I made a package https://build.opensuse.org/package/show/home:FreeSlave/qt-sprite-image-plug… My packages were published for enabled distributions, they have succeeded status and I can see binary packages if I click on a certain repository, and they are available for downloading. But some of the enabled distros (Debian and Ubuntu) still don't show up on the "Download package" page, only Fedora does. Note that I disabled some repositories specifically for this package compared to the list of enabled repositories of the home project. Also I build two packages from one source. Maybe some of these details cause the trouble? There's also a similar issue reported on the forums by other user https://forums.opensuse.org/showthread.php/540382-Some-RPMs-are-not-publish… -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 9 months

[opensuse-buildservice] Invalid keydata in home repository

by Sebix

Dear list, I have a problem with the signkey of a home repository. After it expired, I renewed / extended the sign key using: osc signkey --extend home:sebix:intelmq osc signkey --create home:sebix:intelmq (I do not remember the order which I used anymore) Now, I get this error on Tumbleweed: > Retrieving repository 'home:sebix:intelmq' metadata ...................................................................................................................................................................................[error] > Repository 'home:sebix:intelmq' is invalid. > [http-download.opensuse.org-5ac6b65c|http://download.opensuse.org/repositories/home:/sebix:/intelmq/openSUSE_Tumbleweed/] Valid metadata not found at specified URL > History: > - File /var/tmp/TmpFile.vc7Jia doesn't contain public key data > > Please check if the URIs defined for this repository are pointing to a valid repository. > Skipping repository 'home:sebix:intelmq' because of the above error. An Ubuntu 16.04 user reported a similar error (also after the signkey renewal): > W: Failed to fetch http://download.opensuse.org/repositories/home:/sebix:/intelmq/xUbuntu_16.0… The following signatures were invalid: KEYEXPIRED 1594988315 How can I fix these errors or properly re-create or extend the signkey? best regards Sebastian

1 year, 9 months

[opensuse-buildservice] 335 builds failed today with 'No space left on device' / old-atreju

by Harald Welte

Dear OBS community, this morning I was flooded with 335 e-mails notifying me of build failures, all boiling down to variants of the following message: ------ Last lines of build log: /var/cache/obs/cache/47/471d708c4377c6f34a22d6377c9a439f.18970 write: No space left on device (worker was old-atreju1:9) ------ In case anyone is interested in all of the failures, I've exported them to https://people.osmocom.org/laforge/tmp/20200723-obs-fails.mbox All of those builds had 'old-atreju' in the name. Is that all just one physical machine? Or did dozens of machines all run out of space at the same time? I was a bit surprised that nobody had brought this up on the list yet, given that I'm sure our Osmocom packages are not the only ones with massive build-failure e-mail floods this morning. Thanks! Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 9 months

[opensuse-buildservice] Sick

by David Kang

Hi, Today I'm not feeling well. I will stay at home and recover. David -- David Dionisio Kang - dkang(a)suse.de | dkang(a)suse.com BuildService Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 10 months

[opensuse-buildservice] Downlink link does not work with upper/lowercase

by Spiro Trikaliotis

Hello, I have a second problem. On the page of my package: https://build.opensuse.org/package/show/home:strik/OpenCBM there is the "Download package" link to the right in the upper area. Unfortunately, that link refers to https://software.opensuse.org//download.html?project=home%3Astrik&package=O… which is empty! If I change the link manually in my browser, changing OpenCBM to all lowercase: https://software.opensuse.org//download.html?project=home%3Astrik&package=o… then I get my packages. How can I fix this issue, so that the links points to the right location? Regards Spiro. -- Spiro R. Trikaliotis http://spiro.trikaliotis.net/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 10 months

[opensuse-buildservice] Debian Testing & Unstable: "unresolvable: have choice for libsystemd0 needed by libdbus-1-3: libelogind0 libsystemd0"

by Spiro Trikaliotis

Hello, I am packaging OpenCBM: https://build.opensuse.org/package/show/home:strik/OpenCBM I have a problem with the targets "Debian Testing" and "Debian stable". These do not compile, because "unresolvable: have choice for libsystemd0 needed by libdbus-1-3: libelogind0 libsystemd0" Having a look into the sources for libelogind0 on Debian, I see that it also provided libsystemd0. Now, how can I force the installation of one of them? I do not rely on either them (at least, not directly, and not that I know of). I tried to add "libsystemd0", then "systemd", then "libelogind0" as build-depends, because I hoped it would force the one or the other solution. However, this problem persists. Does anyone have an idea what is going on? I assume it has to do with my build-depends, because my other projects cc65 and xa65 do not exhibit this problem with the same targets. I am out of ideas here. Regards Spiro. -- Spiro R. Trikaliotis http://spiro.trikaliotis.net/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 10 months

[opensuse-buildservice] Dependency resolution for rpm packages with same name

by Vyacheslav Barinov

Hello, Is it possible to have two packages with same name and different versions in single rpm repository of OBS project? Currently I have: - package pkg-old with subpackage libdep-1-1.1.rpm providing libdep.so.1 - package pkg-new with subpackage libdep-2-1.1.rpm providing libdep.so.2 Non-suffixed libdep.so is not provided at all. When I try to use libdep for different apps, applications using libdep.so.1 are fine, but for ones requiring libdep.so.2 OBS reports 'nothing provides libdep.so.2', though I can see this tag in 'Provides' list for package in web-interface. Moreover that: when I try to add synthetic rpm tag using 'Provides:', this tag is generated successfully, but does not help to resolve the situation. As far as I understand, the repository is sorted in alphanumeric order and only first libdep-1-1.1.rpm is processed when dependency tree is constructed. The RPM itself is capable of distinguishing these packages, so it's just OBS internal thing. Is this a bug or planned behavior? Thank you, Slava Barinov. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 10 months

[opensuse-buildservice] OBS Partners Page

by ddemaio

Hi All, We started an openSUSE Partners page at https://en.opensuse.org/Partners. It is currently work in progress, but it would be great to have people fill in the OBS partners page with some info - https://en.opensuse.org/Portal:Build_Service/Partners The page is for projects, companies, startups etc. to are encourage these groups share how they use the Open Build Service. It should provide a good view for the various projects and orgs that are out there using OBS. Please consider adding info or providing feedback on what else could be added to the page. There is also a page for openQA - https://en.opensuse.org/openSUSE:OpenQA/Partners v/r Doug -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 10 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service July 2020