September 2021 - openSUSE Build Service

Changes in the 'configure_repositories' step configuration
by Saray Cabrera Padron 17 Sep '21

17 Sep '21

Hey! 😁 If you are playing around with the integration between OBS and an SCM, please be aware that we have introduced a little change in the 'configure_repositories' step configuration. We renamed the key 'source_project' to simply 'project'. Please check the YAML example in this post <https://openbuildservice.org/2021/08/02/link-package-configure-repositories…>. Regards, The Build Solutions Team -- Saray Cabrera Padrón Build Solutions Team SUSE

1 0

False positives in submission by factory-auto
by Johannes Weberhofer 17 Sep '21

17 Sep '21

Good morning! I currently have an issue submitting an update to factory in request https://build.opensuse.org/request/show/919620 There is a false message saying: Output of check script: Attention, FreeRDP-2.4.0.tar.gz is not mentioned in spec files as source or patch. Attention, freerdp-builtin-channels-off-link-fix.diff is not mentioned in spec files as source or patch. Attention, freerdp-rpmlintrc is not mentioned in spec files as source or patch. The spec contains: Source0: https://github.com/FreeRDP/FreeRDP/archive/%{version}.tar.gz#/FreeRDP-%{ver… Source1: freerdp-rpmlintrc Patch0: freerdp-builtin-channels-off-link-fix.diff Is this an already known bug? Should I file a bug-report? Best regards! -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna

2 3

Problem with my new OBS instance
by Kai Liu 15 Sep '21

15 Sep '21

Hi experts, I just set up a new private OBS instance and I've run into few frustrating problems. Could you give me some advice on how can I debug this problems, such as what logs to look at, how to reset things? My setup is simple, on a single server running openSUSE Leap 15.3, with OBS 2.10 installed from the repository. Then setup by the /usr/lib/obs/server/setup-appliance.sh script. Then I noticed these issues. Firstly, in the configuration UI, I tried to uncheck the i586 and armv7l architectures. But they keep coming back. I also tried removing them from /configuration API, still the same. This is really confusing. Secondly, I connected my instance with the boo instance, and tried to start building some test packages. I soon noticed that my kernel and inird setup was not correct so the worker VM cannot boot into the guest OS. So I edited /etc/sysconfig/obs-server to use a different initrd. But I made a mistake here, I put the wrong path name there thus the VM cannot find the initrd. I can see build logs about the VM cannot start, as expected. The problem is OBS didn't think the build failed, instead it kept restarting the VM. Thus I have to abort the build. The abort succeeded. But later after I corrected the initrd path (and restarted the worker service), the package stuck in the "scheduled" state, never started building, even after I reboot the server. The message I got was "waiting for 8 compliant workers (8 of them bad) ". The package was able to start building before I corrected the initrd path problem so there is no unmet constraint (I didn't put any in place either). I left it overnight and it still stuck there. Then I thought I should delete this package to start from scratch again. This caused more problem... The package I deleted is no longer visible in the package list, but it still showed as "scheduled" in the monitor. And I have "scheduled: 1" on the web UI build result section... It seems my instance is not in a consistent state now. But I can't find enough documentation to help me on debugging it. Any suggestions or hints or link to useful docs are greatly appreciated. Thanks, Kai

3 7

DoD - is it a good idea to build against a DoD in the same project?
by Srinidhi B 15 Sep '21

15 Sep '21

Hello List, Is it a good idea to build against the DoD that is defined in the same project? For example, consider a project with the following meta: <project name="ProjectA"> <title>Packages for ProjectA</title> <description/> <person userid="srinidhi" role="maintainer"/> <build> <disable/> <enable repository="SLE_15_SP3"/> </build> <publish> <disable/> <enable repository="SLE_15_SP3"/> </publish> <debuginfo> <enable/> </debuginfo> <repository name="my_dod"> <download arch="x86_64" url="http://my-example.com/repo/" repotype="rpmmd"> <archfilter>noarch,x86_64</archfilter> </download> <download arch="i586" url="http://my-example.com/repo/" repotype="rpmmd"> <archfilter>noarch,i586</archfilter> </download> <path project="ProjectB" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="SLE_15_SP3"> <path project="ProjectA" repository="my_dod"/> <path project="ProjectB" repository="standard"/> <path project="openSUSE.org:SUSE:SLE-15-SP3:GA" repository="pool"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> The reason I'm asking this question is because we have another project called "ProjectB" that requires the built binaries from "ProjectA/SLE_15_SP3" repository: <project name="ProjectB"> <title>Packages for ProjectB</title> <description/> <person userid="srinidhi" role="maintainer"/> <build> <disable/> <enable repository="standard"/> </build> <publish> <disable/> <enable repository="standard"/> </publish> <debuginfo> <enable/> </debuginfo> <repository name="standard"> <path project="ProjectA" repository="SLE_15_SP3"/> <path project="openSUSE.org:SUSE:SLE-15-SP3:GA" repository="pool"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> Please note that both the ProjectA and ProjectB projects show up in their corresponding project meta. Because of these inter-dependencies between ProjectA and ProjectB, we are ending up with cycles in the scheduler: # grep "^cycle:" /bs/log/scheduler_x86_64.log ... cycle: ProjectB/standard -> ProjectA/SLE_15_SP3 ... This issues gets amplified for every repository snapshot we create and whenever we create the Maintenance projects for both ProjectA and ProjectB! In this case, would it be better to move the DoD repository configuration into a completely separate project? Any other suggestions or critique on how we are setting up our projects? Regards, Srinidhi.

1 0

RPM multiarch package
by Mathias Radtke 15 Sep '21

15 Sep '21

Hi we are currently struggling to build a package for RPM systems. This package contains various libraries and prebuild binaries for x86_64 and aarch64 architecure. How can we create one rpm package that includes both binaries and installs them, depending on the machine arhcitecture? Using BuildArch: noarch did fail. Not using any BuildArch entry in the spec file results in arch-independent-package-contains-binary-or-object Is there any way to disable this check or how to create one mutliarch package? Regards Mathias -- opsi - Open PC-Server-Integration das Open Source Client-Management-System von uib gmbh Mathias Radtke Entwicklung eMail: m.radtke(a)uib.de Tel. +49 6131 / 27561-01 Fax +49 6131 / 27561-22 uib gmbh Bonifaziusplatz 1B 55118 Mainz Internet: https://uib.de https://opsi.org Geschftsfhrer: Dr. Detlef Oertel, Erol Ülükmen Handelsregister: Amtsgericht Mainz HRB 6942

2 1

AW: RPM multiarch package
by Mathias Radtke 15 Sep '21

15 Sep '21

Just to clarify, wen only need aarch64 packages for Debian 10 and 11. RPM doesn't need to build the aarch64 package, just the x86_64 one. Debian packages build fine with the "architcture:all" flag Regards Mathias -----Ursprüngliche Nachricht----- Von: Mathias Radtke <m.radtke(a)uib.de> Gesendet: Mittwoch 15. September 2021 14:30 An: buildservice(a)lists.opensuse.org Betreff: RPM multiarch package Hi we are currently struggling to build a package for RPM systems. This package contains various libraries and prebuild binaries for x86_64 and aarch64 architecure. How can we create one rpm package that includes both binaries and installs them, depending on the machine arhcitecture? Using BuildArch: noarch did fail. Not using any BuildArch entry in the spec file results in arch-independent-package-contains-binary-or-object Is there any way to disable this check or how to create one mutliarch package? Regards Mathias -- opsi - Open PC-Server-Integration das Open Source Client-Management-System von uib gmbh Mathias Radtke Entwicklung eMail: m.radtke(a)uib.de Tel. +49 6131 / 27561-01 Fax +49 6131 / 27561-22 uib gmbh Bonifaziusplatz 1B 55118 Mainz Internet: https://uib.de https://opsi.org Geschftsfhrer: Dr. Detlef Oertel, Erol Ülükmen Handelsregister: Amtsgericht Mainz HRB 6942

2 1

api.opensuse.org: How to GET the list of users (along with their roles) of any given package?
by Adrien Glauser 14 Sep '21

14 Sep '21

Hello, I would like to perform the API action described in the topic above, ideally in a single request. Is that feasible? Thanks in advance, Adrien

8 11

New Blog Post for the Integration Between OBS and SCM
by Dany Marcoux 14 Sep '21

14 Sep '21

Hey everyone! After a quiet vacation month in August, we’re back with changes to improve workflows in the integration between OBS and source code management systems (SCM) like GitHub and GitLab. Let us know what you think: https://openbuildservice.org/2021/09/14/scm-more-pull-request-actions-and-u… Cheers -- Dany Marcoux <dmarcoux(a)suse.de> Full Stack Web Developer - Open Build Service SUSE Linux GmbH Maxfeldstrasse 5 90409 Nürnberg Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg)

1 0

Is there any documentation on Repository configs
by Ralph Schaffner 13 Sep '21

13 Sep '21

I have several projects in OBS and I've basically guessed at what repositories I need to add to the projects. Is there any documentation that explains how to find repositories and what the different options mean? For instance, I was told recently I should be using "openSUSE:Backports:SLE-15-SP3" for updates for SLES 15 SP3, even though there exists "SUSE:SLE-15-SP3:Update". neotinker@ros-15_1:~/devel/OSC> osc ls | grep -E "^SUSE:SLE-15-SP3|^openSUSE:Backports:SLE-15-SP3" SUSE:SLE-15-SP3:GA SUSE:SLE-15-SP3:Update SUSE:SLE-15-SP3:Update:Products:MicroOS51 SUSE:SLE-15-SP3:Update:Products:MicroOS51:Update openSUSE:Backports:SLE-15-SP3 openSUSE:Backports:SLE-15-SP3:Checks openSUSE:Backports:SLE-15-SP3:Staging openSUSE:Backports:SLE-15-SP3:Staging:A openSUSE:Backports:SLE-15-SP3:Staging:B openSUSE:Backports:SLE-15-SP3:Staging:adi:1 openSUSE:Backports:SLE-15-SP3:Staging:adi:3 openSUSE:Backports:SLE-15-SP3:Update neotinker@ros-15_1:~/devel/OSC> Then once you pick a project, how do you know which repo to select? Most have "standard" which the documentation I have found says 'The repository="standard" is just for future extensions (forks of a repository).' but there are a variety of other options like "pool", "ports", "step", etc. Is there somewhere that describes these different repos? What the names mean and when to use which? https://en.opensuse.org/openSUSE:Build_Service_Tutorial#Step_Three.C2.A0.E2… Thanks in advance. Neotinker

2 1

open build service ccache issue
by TommyLike Hu 12 Sep '21

12 Sep '21

Hey team I am from openEuler community and we use OBS for our package building, we found there is a discussion regarding CCache support in OBS around May 2020, and we would like to use this feature in our environment, but unfortunately we can't find any ccache support code in code release branches(2.10.xxx), it only exists in master branch [1], so may I ask does OBS support configure Ccache? how can we find the support branch and configure it. Thanks in advance. TommyLike 09/11/2021 [1]: https://github.com/openSUSE/open-build-service/blob/2acf0549256926c6b96190b…

2 2