March 2024 - openSUSE Build Service - openSUSE Mailing Lists

repository setup is broken for each repository of RockyLinux:8
by Martin Weber 23 Apr '24

23 Apr '24

Hi, https://build.opensuse.org/project/show/RockyLinux:8 is broken. It says "The repository setup is broken, build or publish not possible (unresolvable preinstalls: nothing provides perl-interpreter)" If I run osc build I get buildinfo is broken... it says: unresolvable: preinstalls: nothing provides perl(IO::Socket::SSL) >= 1.56 needed by perl-HTTP-Tiny Viele Grüße, Martin Weber -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? | Martin Weber | Razorcat Development GmbH | Witzlebenplatz 4 fon: +49-(30)-536 357 46 | 14057 Berlin fax: +49-(30)-536 357 60 | |-------------------------------------------- | Geschäftsführer: Michael Wittner | Sitz der Gesellschaft: Berlin | Amtsgericht: Berlin, HRB 65326

3 5

How to change my e-mail address for build.o.o
by Martin Winter 08 Apr '24

08 Apr '24

There are several threads asking this very same question. The latest I found was this one: https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/th…. However I still do not find an answer to that question. What I tried: - Going to my profile on build.o.o and edit my profile: The e-mail address is not editable. - Change the user meta via `osc meta user -e letsfindaway`: Does not change anything. - Login to Micro Focus and try to edit my profile there: The e-mail address is not editable. So what is the way to change the e-mail address listed on my profile in build.o.o and used to send e-mail notifications? Thanks for any insights and pointers! Martin

8 15

Unable to upload Sources to obs instance
by Christian 01 Apr '24

01 Apr '24

Hi, getting some strange error while trying to update one of my packages: osc is just telling: Try env VC_REALNAME=... Sending nats-server.SIT_Leap-15.5_Update/_service Deleting nats-server.SIT_Leap-15.5_Update/_servicedata Deleting nats-server.SIT_Leap-15.5_Update/nats-server-2.9.24.tar.gz Sending nats-server.SIT_Leap-15.5_Update/nats-server.changes Sending nats-server.SIT_Leap-15.5_Update/nats-server.spec Sending nats-server.SIT_Leap-15.5_Update/vendor.tar.gz Transmitting file data .Server returned an error: HTTP Error 400: Bad Request service validation error: 17:0: ERROR: Invalid attribute mode for element service while obs api is saying: E, [2024-03-31T21:01:07.118310 #18202] ERROR -- : [86ad16b2-8297-408b-bc9a-09031d03d70c] [18202:247657.14] validation error: 17:0: ERROR: Invalid attribute mode for element service I, [2024-03-31T21:01:07.120848 #18202] INFO -- : [86ad16b2-8297-408b-bc9a-09031d03d70c] [18202:247657.14] method=PUT path=/source/home:computersalat:branches:OBS_Maintained:nats-server/nats-server.SIT_Leap-15.5_Update/_service format=xml controller=SourceController action=update_file status=400 duration=323.69 view=0.59 db=50.21 params={"xmlhash"=>{"service"=>[{"name"=>"obs_scm", "param"=>[{"name"=>"url", "_content"=>"https://github.com/nats-io/nats-server.git"}, {"name"=>"scm", "_content"=>"git"}, {"name"=>"revision", "_content"=>"v2.9.25"}, {"name"=>"versionformat", "_content"=>"@PARENT_TAG@"}, {"name"=>"versionrewrite-pattern", "_content"=>"v(.*)"}, {"name"=>"exclude", "_content"=>".git"}, {"name"=>"changesgenerate", "_content"=>"disable"}]}, {"name"=>"set_version", "mode"=>"buildtime"}, {"name"=>"tar", "mode"=>"buildtime"}, {"name"=>"recompress", "mode"=>"buildtime", "param"=>[{"name"=>"file", "_content"=>"*.tar"}, {"name"=>"compression", "_content"=>"xz"}]}, {"name"=>"go_modules", "mode"=>"manual", "param"=>{"name"=>"archive", "_content"=>"nats-server-2.9.25.obscpio"}}]}, "rev"=>"repository", "project"=>"home:computersalat:branches:OBS_Maintained:nats-server", "package"=>"nats-server.SIT_Leap-15.5_Update", "filename"=>"_service"} host=2001:1620:53a4:0:5448:6c1b:d45d:2353 time=610152.61 backend=0 user=computersalat what exactly is meant with "Invalid attribute mode for element service"? I have same 'obs-service' packages installed on my obs instance as on my local box. local services do work and build also. Can someone please help me to understand this error ? Something seem to be missing on my instance ... Thank you Kind Regards -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

2 2

linkpac to a specific revision
by Gregor Dschung 25 Mar '24

25 Mar '24

Hello, I'm trying to link home:chkpnt:nextcloud/nextcloud to a specific revision of server:php:applications/nextcloud, but it's not really working. This is my _link: <link project="server:php:applications" package="nextcloud" rev="211">...</link> My intention is to build Nextcloud 26.0.7. If I checkout server:php:applications/nextcloud at revision 211, I'm getting the correct version. But my linkpac package always gives me the latest revision of server:php:applications/nextcloud: https://build.opensuse.org/package/show/home:chkpnt:nextcloud/nextcloud Have I misunderstood something? Regards, Gregor

4 7

Re: OBS rpm no public key
by Marco Moock 20 Mar '24

20 Mar '24

Am 20.03.2024 um 10:57:05 Uhr schrieb Adrian Schröter: > On Mittwoch, 20. März 2024, 10:24:14 CET Marco Moock wrote: > > Am 20.03.2024 um 08:08:23 Uhr schrieb Adrian Schröter: > > > > > On Dienstag, 19. März 2024, 16:59:20 CET Marco Moock wrote: > > > > Hello! > > > > > > > > Today I tried to use OBS to build for Fedora 39 on Debian > > > > Unstable (there runs osc). > > > > > > > > Verifying integrity of cached packages > > > > using keys from Fedora:39, OBS > > > > warning: > > > > /var/tmp/osbuild-packagecache/Fedora:39/standard/x86_64/alternatives-1.25-1.fc39.x86_64.rpm: > > > > Header V4 RSA/SHA256 Signature, key ID 18b8e74c: NOKEY > > > > > > > > What is the proper way to add these keys? > > > > Should I use rpm --import? > > > > I have tried that with the key from > > > > https://fedoraproject.org/fedora.gpg, but osc doesn't seem to > > > > care. > > > > > > > > What is the proper way to handle that? > > > > > > You are using a chroot build environment. This is not safe against > > > evil attackes, so you would need to trust these rpms via import. > > > > Which key do I need to import. From where do I get it? > > Usually from the distro. However, please note that this means > that anyone from Fedora can modify your Debian system. So the proper way is to use --vm-type? > Usually you do not want to grant this. Of course not. I though that the builds will be done in a separated environment independent of my current operating system. Thanks for the clarification. -- Gruß Marco Send unsolicited bulk mail to 1710928625muell(a)cartoonies.org

3 3

OBS rpm no public key
by Marco Moock 20 Mar '24

20 Mar '24

Hello! Today I tried to use OBS to build for Fedora 39 on Debian Unstable (there runs osc). Verifying integrity of cached packages using keys from Fedora:39, OBS warning: /var/tmp/osbuild-packagecache/Fedora:39/standard/x86_64/alternatives-1.25-1.fc39.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 18b8e74c: NOKEY What is the proper way to add these keys? Should I use rpm --import? I have tried that with the key from https://fedoraproject.org/fedora.gpg, but osc doesn't seem to care. What is the proper way to handle that? -- kind regards Marco Send unsolicited bulk mail to 1710863334muell(a)cartoonies.org

3 3

How to make a spec file specific for Leap repositories with their default numeric names?
by Paul McAuley 17 Mar '24

17 Mar '24

At https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.multibuild… it states "Specific files can be created to be built for a specific repository. Append the repository name of the build container behind the package name with a -. For example hello-openSUSE_13.2.spec. " This works in my package (https://build.opensuse.org/package/show/home:paul4us/klassy) for Fedora and Mageia. My problem is that I want to make a .spec file specifically for Leap 15.5 and Leap 15.6 but the default repository names are just "15.5" and "15.6" respectively. When I try to name a .spec file with packagename-15.5.spec or packagename-15.6.spec these spec files are ignored and the default packagename.spec is used instead, giving "unresolvable" statuses. I suspect that this is because the repository names are numeric with no letters. How do I make a .spec file specific to these 15.5 and 15.6 repositories? I don't want to make new repositories with a different name as people will be subscribed to the existing ones. Thanks, Paul

2 4

Problem with osc builds 15.6 Build 630
by Larry Finger 15 Mar '24

15 Mar '24

Hi, I am trying to build the virtualbox modules to check out [Bug 1221165] Can not install VirtualBox. Starting a VM gets a NULL request, but I do not have the debug info for the kernel module that breaks. When I try to ose osc to build it locally, I get the following: Verifying integrity of cached packages using keys from SUSE:SLE-15-SP3:Update, SUSE:SLE-15:GA, SUSE:SLE-15-SP4:GA, SUSE:SLE-15:Update, SUSE:SLE-15-SP6:GA, SUSE:SLE-15-SP4:Update, SUSE:SLE-15-SP5:Update, openSUSE:Backports:SLE-15-SP6, SUSE:SLE-15-SP5:GA, SUSE:SLE-15-SP3:GA, SUSE:SLE-15-SP1:Update, SUSE:SLE-15-SP2:Update, SUSE:SLE-15-SP2:GA, SUSE:SLE-15-SP1:GA, Virtualization warning: /var/tmp/osbuild-packagecache/SUSE:SLE-15-SP6:GA/toberemoved/x86_64/glibc-2.38-150600.6.2.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3fa1d6ce: NOKEY /var/tmp/osbuild-packagecache/SUSE:SLE-15-SP6:GA/toberemoved/x86_64/glibc-2.38-150600.6.2.x86_64.rpm : public key not available /var/tmp/osbuild-packagecache/SUSE:SLE-15-SP6:GA/toberemoved/x86_64/sed-4.9-150600.1.3.x86_64.rpm : public key not available /var/tmp/osbuild-packagecache/SUSE:SLE-15-SP6:GA/toberemoved/x86_64/libselinux1-3.5-150600.1.45.x86_64.rpm : public key not available /var/tmp/osbuild-packagecache/SUSE:SLE-15-SP6:GA/toberemoved/x86_64/liblzma5-5.4.6-150600.1.16.x86_64.rpm : public key not available followed by a lot more messages. Is there a fix? Thanks, Larry

2 2

Open Build Service 2.10.22
by Daniel Donisa 15 Mar '24

15 Mar '24

Hello People, We have just released Open Build Service 2.10.22 which fixes security vulnerabilities. You should update your installations as soon as possible. ## Fixed Issues Frontend: * Update rack to version 2.2.8.1 - Fixed ReDoS in Accept header parsing [CVE-2024-26146] - Fixed ReDoS in Content Type header parsing [CVE-2024-25126] - Reject Range headers which are too large [CVE-2024-26141] DoS Vulnerability in Multipart MIME parsing. ## How to Update Package updates are available from the 2.10 repositories https://build.opensuse.org/project/show/OBS:Server:2.10 Fixed appliances can be downloaded from http://openbuildservice.org/download Kind regards, --- Daniel Donisa daniel.donisa(a)suse.com Build Solutions Team SUSE Software Solutions Germany GmbH

2 2

Incorrect perl dependencies for RHEL8/RHEL9
by obs＠dibo.sk 11 Mar '24

11 Mar '24

Hello, I managed to make builds for RHEL8/RHEL9 using private instance with development version of OBS. Unfortunately when building perl modules dependencies are not being calculated correctly. Looks like scripts generating perl dependencies aren't run. What is strange if I run it with rpmbuild even perl dependencies perl(ModuleName) dependencies are calculated correctly so I wandering if there's something special required in project config. Thanks for any hints Regards Dibo ⁣Get BlueMail for Android

1 0