October 2023 - openSUSE Build Service - openSUSE Mailing Lists

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

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

KVM preinstall on workers in own obs instance trouble
by Stefan Botter 21 Nov '23

21 Nov '23

Hi there, I am running the build server for the Packman builds - PMBS. Since a few weeks we are tying to build for Slowroll also. Since about a month (~ Sep 26th or around), builds fail on my two workers for Slowroll. It is possible, that there are repos, for which building is also failing - possibly xUbuntu_20.04, but for the main targets Leap and Tumbleweed everything is fine. Build server and workers are running Leap 15.5 and current packages from the OBS:Server:2.10 repo. The notable difference is the empty preinstall in worker setup. The respective file (/var/cache/obs/worker/root_?/.build.rpmlist) has an empty "preinstall:" line, whereas for successfully building projects the line is filled with the packages for the KVM setup environment. We have successful builds for Slowroll in PMBS, but these results date back to approx. Sep 26th. Around that time "something" must have changed - "I didn't do anything, I swear!" :) Where does the preinstall information come from, how can I further debug, how can I fix builds for Slowroll (and possibly other affected projects)? Thank you for input, Greetings, Stefan -- Stefan Botter zu Hause Bremen

4 5

Understanding when/why a package seems to have been removed from OBS
by Robert Norris 11 Nov '23

11 Nov '23

Sorry if this is not the right place to ask such a question, please direct me to appropriate channels if that is the case. Previously I have been a user of the related packages mingw64-libnova-devel and mingw64-libnova; which I'm sure were available about 1 year or so ago, which used to be under: https://build.opensuse.org/project/show/windows:mingw:win64 However, they are no longer listed - so I'm wondering what happened to them? AFAIK they don't have any reason to be obsoleted / unmaintained. The standard openSUSE factory version is still available: https://build.opensuse.org/package/show/openSUSE:Factory/libnova If necessary, I will recreate a suitable .spec file to generate the mingw versions myself, but it would be nice if I didn't need to recreate such an item. IIRC the spec for the Windows version seemed quite straight-forward - i.e. the cross compile worked without any additional changes. My own web searches have come up blank for a version of this .spec file (and indeed that mingw variants were in OBS at all). Thanks for any information on this matter. -- Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you.

2 2

CentOS 8 Stream builds unresolvable
by Martin Tůma 10 Nov '23

10 Nov '23

Hi, For some time, CentOS 8 Stream builds are unresolvable because of the following error: unresolvable: nothing provides gcc = 8.5.0-18.el8 needed by gcc-c++, (got version 8.5.0-15.el8), nothing provides libgomp = 8.5.0-15.el8 needed by gcc, (got version 8.5.0-18.el8) Can someone please have a look at it? I doubt that it is a Centos problem and they have broken gcc packages in the distro for weeks... Thanks M.

2 1

Fedora 39 missing i586
by Rosanne DiMesio 06 Nov '23

06 Nov '23

I have Fedora 39 added to Emulators:Wine:Fedora and i586 enabled, but it is not showing up when I build. It looks like Fedora:39 is missing https://kojipkgs.fedoraproject.org/repos/f39-build/latest/i386/ from the Meta Configuration. Please add it. -- Rosanne DiMesio <dimesio(a)earthlink.net>

2 2

New blog post about failed notifications from SCM/CI workflow runs
by Rubhan Azeem 31 Oct '23

31 Oct '23

Hi everyone, We have recently introduced notifications about failed workflow runs in SCM/CI integration. Please refer to our new blog post<https://openbuildservice.org/2023/10/30/notifications-failed-workflow-runs/> to know more about it. Kind regards, The Build Solutions Team 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

Need help with a _service file
by Adrian 29 Oct '23

29 Oct '23

Sorry if this is dumb question, I'm new to OBS, I am probably missing something obvious. I managed to create a github integration and have the *.dsc and *.tar.xz files needed for Debian builds downloaded automatically from github: https://build.opensuse.org/package/view_file/home:mx-packaging/xdelta3-gui However, the files have a "_service:" prefix and the build doesn't start (I assume because of the prefix, but not sure). Here's my _service file https://build.opensuse.org/package/view_file/home:mx-packaging/xdelta3-gui/… Can anybody please take a look and let me know why this is not building (it shows "success" but there's no binary created)? Do I need to rename the downloaded files, how? Thanks, Adrian

3 2

RetroShare Debian Repo GPG key expired
by Marek Küthe 25 Oct '23

25 Oct '23

Hello, I was referred here via an [issue](https://github.com/RetroShare/RetroShare/issues/2625) from RetroShare. The GPG key for the Debian repo seems to have expired. ``` Err:9 http://download.opensuse.org/repositories/network:/retroshare/Debian_10 InRelease The following signatures were invalid: EXPKEYSIG 62EB1A0917280DDF network OBS Project <network(a)build.opensuse.org> ... An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org/repositories/network:/retroshare/Debian_10 InRelease: The following signatures were invalid: EXPKEYSIG 62EB1A0917280DDF network OBS Project <network(a)build.opensuse.org> W: Failed to fetch http://download.opensuse.org/repositories/network:/retroshare/Debian_10/InR… The following signatures were invalid: EXPKEYSIG 62EB1A0917280DDF network OBS Project <network(a)build.opensuse.org> W: Some index files failed to download. They have been ignored, or old ones used instead. ``` Could someone look into this or tell me who to contact? Greetings Marek Küthe -- Marek Küthe m.k(a)mk16.de er/ihm he/him

3 2

Debian:11 and Debian:12 security updates
by Nicholas Brown 24 Oct '23

24 Oct '23

Look at the meta for the Debian:11 project I notice that this uses the following 3 sources: https://build.opensuse.org/projects/Debian:11/meta <repository name="standard"> <download arch="x86_64" url="http://ftp.de.debian.org/debian/bullseye/main" repotype="deb"> <repository name="update"> <download arch="x86_64" url="http://ftp.de.debian.org/debian/bullseye-updates/main" repotype="deb"> <repository name="backports"> <download arch="x86_64" url="http://ftp.de.debian.org/debian/bullseye-backports/main" repotype="deb"> I wonder if should also include the debian security source? This will contain security fixes that are neither in update or standard (until the next twice yearly point release of standard). deb http://deb.debian.org/debian-security/ bullseye-security main See: https://wiki.debian.org/SourcesList for full details of debian sources. (the same would apply to Debian:12 too)

1 0