- openSUSE Build Service

Enhancements in Content Moderation: Updates in OBS
by Rubhan Azeem 06 Mar '24

06 Mar '24

Hey everyone, We've been diligently working on refining the content moderation features in OBS, and I'm pleased to inform you that we've implemented several key improvements. For a comprehensive overview of these updates, please take a moment to check out our latest blog post <https://openbuildservice.org/2024/03/06/content-moderation/>. Thank you for your ongoing support and collaboration. Best regards, Team OBS -- *Rubhan Azeem* SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany HRB 36809, AG Nürnberg Geschäftsführer: Felix Imendörffer

1 0

cannot build Fedora_39 (ppc64le) and openSUSE_tumbleweed (x86_64)
by Martin Diehl 01 Mar '24

01 Mar '24

Hello, after implementing an upstream update (but potentially unrelated to that) I observe two build failures. Unfortunately, there is almost no information given by OBS: - For Fedora_39, ppc64le I just see a red triangle with an exclamation mark - For openSUSE_Tumbleweed, the build is blocked and the only information available is a truncate list of packages. Is there the possibility to get more information? The link to the project is https://build.opensuse.org/project/show/home:MarDieh thanks in advance for any help Martin -- KU Leuven Department of Computer Science Department of Materials Engineering Celestijnenlaan 200a 3001 Leuven, Belgium

2 1

Heads Up: Changes in the OBS Notification Mail Headers
by Henne Vogelsang 29 Feb '24

29 Feb '24

Hey, on Monday 15:00 CET we will change a couple of headers in some of the OBS Notification mails. So far mails about comments, requests and user changes included a "From:" header pointing to the address of the person that "caused" this notification, the author so to speak. So if I made a comment on your project you would receive mail From: Henne Vogelsang <hvogel(a)opensuse.org> Subject: New comment in project $project by hennevogel From Monday on *all* OBS notification mails from contain a "From:" header pointing to a general address. So if I made a comment on your project you would receive mail From: Henne Vogelsang (hennevogel) <noreply(a)opensuse.org> Reply-To: Henne Vogelsang <hvogel(a)opensuse.org Subject: New comment in project $project by hennevogel We need to do this because more and more MTA's get strict on SPF¹ and classify those emails as SPAM. The rest of the headers will stay as they where... Henne ¹ https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/ -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson

1 0

build.opensuse.org wrong sender email address
by Stefan Seyfried 28 Feb '24

28 Feb '24

Hi all, build.opensuse.org sends mail from noreply(a)opensuse.org This is an invalid address: ~> telnet mx2.opensuse.org 25 Trying 195.135.221.158... Connected to mx2.opensuse.org. Escape character is '^]'. 220 mx2.opensuse.org ESMTP Postfix (3.7.2) helo seife 250 mx2.opensuse.org mail from: seife(a)opensuse.org 250 2.1.0 Ok rcpt to: noreply(a)opensuse.org 550 5.7.1 <noreply(a)opensuse.org>: Recipient address rejected: This Email address is not monitored. Please contact admin(a)opensuse.org in case you need personal assistance. quit 221 2.0.0 Bye Connection closed by foreign host. ~> My mail provider only allows verified addresses (postfix option "reject_unverified_sender") so it would be useful to change this maybe to admin(a)opensuse.org? Best regards, -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

2 1

Fedora Rawhide builds stuck on downloading packages in my home project
by Neal Gompa 22 Feb '24

22 Feb '24

Hey all, I'm trying to build libzypp in OBS for Fedora Rawhide in a home project[1] for a bug report about libzypp's test suite[2], but it seems to have been stuck for a couple of days trying to download packages. Anyone have any idea what's going on? [1]: https://build.opensuse.org/package/show/home:Pharaoh_Atem:Zypper_Fedora/lib… [2]: https://github.com/openSUSE/libzypp/issues/522 -- 真実はいつも一つ！/ Always, there's only one truth!

2 4

disable build with osc meta
by Axel Braun 20 Feb '24

20 Feb '24

Hello, I want to disable the build of a package with osc meta .... What syntax does the parameter --set expect? -s <disable repository="15.6"/> does not work.... Thx! Axel

2 1

Building Debian packages from git
by Michal Suchánek 17 Feb '24

17 Feb '24

Hello, I have a git repository, and I want to build an openSUSE and Debian package out of these sources. For rpm packages there are tar_scm and set_version services which can in tandem generate updated packaging file automatically. There is the hiccup that tar_scm can only create a new tar file abd not delete the old file which can be avoided by not including the version in the tar file. That's messy but at least tehre is a way to generate the package automatically. For Debina package it is unclear how they can be built in OBS at all. Sure, you can download a full Debian package created with Debian tools on a Debian distribution, create a package container in OBS, upload the package files there, and you have a 1:1 clone of the original package. There are supposed to be some tools for managing Debian packages for the case when rpm package is built out of the same source, and as a result the source tarball needs to be available under mulltiple names to satisfy both the debian namig rules and th rpm naming conventions. There is a wiki page https://en.opensuse.org/openSUSE:Build_Service_Debian_builds which mentions a debtransform tool which is not documented any where I could find, and an example package that does not exist. Even on that page it is assumed that a Debian changelog exists but the changesgenerate option of tar_scm service generates an OBS changelog, not a Debian changelog. Is there a tool that can convert OBS changelog to DEbian changelog? Is there any documentation of debtransform? Thanks Michal

1 0

Building Tumbleweed based ISO image:
by opensuse.lietuviu.kalba 12 Feb '24

12 Feb '24

Hi, I try to create ISO image based on openSUSE Tumbleweed in openSUSE Build Service. But I get error: EXEC: [chroot /usr/src/packages/KIWI-iso/build/image-root dracut --verbose --no-hostonly --no-hostonly-cmdline --install /.profile --add kiwi-live pollcdrom --omit multipath Lietukas_T_mini.x86_64-2021.initrd 6.7.1-2-default] EXEC: Failed with stderr: (no output on stderr), stdout: /usr/bin/dracut: line 1070: /sys/module/firmware_class/parameters/path: No such file or directory [ 351s] dracut[F]: Cannot find module directory /lib/modules/6.7.1-2-default/ [ 351s] dracut[F]: and --no-kernel was not specified See full log here: - https://build.opensuse.org/package/live_build_log/home:embar-:Lietukas/Liet… - https://paste.opensuse.org/pastes/a8072f79bbc4 (copy of today build log) See image configuration here: https://build.opensuse.org/package/show/home:embar-:Lietukas/Lietukas_T_mini Can you please help to figure out how to fix error? -- Regards, Mindaugas

3 7

Re: repository setup is broken for each repository of RockyLinux:8
by Andreas Vögele 12 Feb '24

12 Feb '24

Martin Weber wrote: >>> https://build.opensuse.org/project/show/RockyLinux:8 is broken. [...] >> 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 I've put the following workaround into my Project Config. %if 0%{?rocky_version} == 800 Ignore: perl-HTTP-Tiny %endif This works unless your own packages depend on perl-HTTP-Tiny.

3 2

Building AArch64 and ARM7 for Ubuntu 22.04 on x86_64
by Dirk Stöcker 11 Feb '24

11 Feb '24

Hello, I'm trying to build packages for Ubuntu 22.04 AArch64 and ARMv7 architecture on a x86_64 system. The same approach works fine for openSUSE_15.5: I'm building locally with osc in home:dstoecker:base repository. I'm calling osc: "osc build --local-package -j 4 --vm-type=qemu --no-verify openSUSE_Leap_15.5 aarch64 package.spec". This fires up qemu and builds the package. Similar for ARM7 with "osc build --local-package -j 4 --vm-type=qemu --no-verify openSUSE_Leap_15.5_ARM armv7l package.spec" For Ubuntu I do: "osc build --local-package -j 4 --vm-type=qemu --no-verify Ubuntu_22.04 aarch64 package.dsc" and it fails with --- [ 5s] booting qemu... [ 5s] Using UART console [ 5s] ERROR: No kernel image for the target architecture available! [ 5s] You may want to use vmtype=kvm instead if you do not want to emulate a foreign architecture. --- I tried using --vmtype=kvm instead of --vmtype=qemu, but that doesn't fix the issue. Same issue when called with armv7l. The relevant parts of Project meta configuration: <repository name="openSUSE_Leap_15.5_ARM"> <path project="openSUSE:Leap:15.5:ARM" repository="ports"/> <arch>armv7l</arch> </repository> <repository name="openSUSE_Leap_15.5"> <path project="openSUSE:Leap:15.5:Update" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> <arch>aarch64</arch> </repository> <repository name="Ubuntu_22.04"> <path project="Ubuntu:22.04" repository="universe"/> <arch>x86_64</arch> <arch>i586</arch> <arch>aarch64</arch> <arch>armv7l</arch> </repository> Does anyone know what's missing or wrong? For Freedom In Peace -- http://www.dstoecker.eu/ (PGP key available)

3 2