March 2023 - openSUSE Build Service - openSUSE Mailing Lists

package signing
by Ivan Ekimov 29 Mar '23

29 Mar '23

Hello, I'm using a local obs server and got a problem with package signing. I tried this guideline https://en.opensuse.org/openSUSE:Build_Service_Signer, but it's outdated and after a few workarounds like coping files from ~/.gnupg/* to /srv/obs/gnupg/ got this message [11882] signer exiting... [12254] signer started waiting for an event... signing x86_64/*** 127.0.0.1: Connection refused sign failed: 256 - checking digest /srv/obs/jobs/x86_64/***.src.rpm: digests OK sign failed: sign /srv/obs/jobs/x86_64/***src.rpm failed sign -k returning key perfectly also, I tried to use obs_admin --update-project-signing-key project ./key.pgp.pub ./_signkey and got error no secret key BR, Ivan

3 3

Debian:11 project security repository
by Nicholas Brown 27 Mar '23

27 Mar '23

Look at the meta for the `Debian:11` project (https://build.opensuse.org/project/show/Debian:11) I notice that this uses the following 3 sources: <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 upstream debian `security` source? This will contain security fixes that are neither in update or standard (until the next 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 standard/update/security sources.

1 0

Add Ubuntu 23.04 to openSUSE Build Service?
by Wong Hoi Sing Edison 24 Mar '23

24 Mar '23

Hi Everyone, Ubuntu 23.04 is now currently pre-Beta, Beta scheduled on 2023-03-30, and final release scheduled on 2023-04-20: * https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284 * https://wiki.ubuntu.com/Releases#Future * https://cdimage.ubuntu.com/daily-live/current/ Could we start getting it added to OBS now? Regards, Edison Wong

2 2

Unable to edit user account.
by Larma Doive 24 Mar '23

24 Mar '23

1 0

How to divide the obs server into three servers
by liuxueping.snow＠bytedance.com 24 Mar '23

24 Mar '23

I want to divide obs server into api server, source server and repo server, what should I do? Or is there an instruction manual?

1 0

How to add a new project under specific namespace?
by Kentaro Hayashi 24 Mar '23

24 Mar '23

Hi, According to https://build.opensuse.org/project/new, When I want to create a new project outside of my home project, I need to contact via email, but, apparently, it will not work because it bounces email (noreply(a)opensuse.org) It seems that it is a known-issue since 2022. [1] https://github.com/openSUSE/open-build-service/issues/12356 Is there documented instruction on how to request a new project under existing specific namespace (such as server:mail) ? What I learned from the existing documentation, it should create a new project in my case, but I couldn't find official documentation to do it yet. I've tried to use obs under my home project [2] whether it satisfies our requirement in beforehand. Here are our requirements for milter-manager project: 1. maintain the package under the meaningful namespace * package itself may be maintained under the home project, but it is better to maintain under a more meaningful namespace because milter-manager is related to mail service. 2. publish multiple versions in the same repository * maintain the latest version only is not enough. * It may work by submitting multiple versioned package to server:mail namespace, but it causes namespace polutions with milter-manager-1.x.x, milter-manager-2.x.x and more. * To avoid such a situation, it should be server:mail:milter-manager project to group multiple versions under it's own project namespace. 3. want to publish not only openSUSE, but also other distributions * It requires configuring project meta information to do, so it can't be satisfied with submitting packages to server:mail. It need to own server:mail:milter-manager project namespace. To satisfy both of them, I want to create a new project. Correct me if I understand wrongly. Regards, [2] https://build.opensuse.org/project/show/home:kenhys

1 1

obs dependency resolver problems
by ahmedmoselhi55＠gmail.com 22 Mar '23

22 Mar '23

Hi there, I'm trying to build qt6 packages in my project version 6.5.0-rc the problem is while qt-base built successfully like in here https:// build.opensuse.org/package/show/home:ahmedmoselhi2:branches:Emulators/qt6-b… I got unresolvable issues in all other qt6 packages for example qt6-3d in https://build.opensuse.org/package/show/home:ahmedmoselhi2:branches:Emulato… qt6-3d complains about the following when build for leap 15.4 x64_86: unresolvable: nothing provides cmake(Qt6Concurrent) = 6.5.0, nothing provides cmake(Qt6Core) = 6.5.0, nothing provides cmake(Qt6Gui) = 6.5.0, nothing provides cmake(Qt6Network) = 6.5.0, nothing provides cmake(Qt6OpenGL) = 6.5.0, nothing provides cmake(Qt6Widgets) = 6.5.0, nothing provides cmake(Qt6Core) = 6.5.0 needed by qt6-core-private-devel, nothing provides cmake(Qt6DeviceDiscoverySupportPrivate) = 6.5.0 needed by qt6-gui-private- devel, nothing provides cmake(Qt6EglFSDeviceIntegrationPrivate) = 6.5.0 needed by qt6-gui-private-devel, nothing provides cmake(Qt6EglFsKmsSupportPrivate) = 6.5.0 needed by qt6-gui-private-devel, nothing provides cmake(Qt6FbSupportPrivate) = 6.5.0 needed by qt6-gui-private-devel, nothing provides cmake(Qt6InputSupportPrivate) = 6.5.0 needed by qt6-gui-private- devel, nothing provides cmake(Qt6OpenGL) = 6.5.0 needed by qt6-opengl-private- devel, nothing provides qt6-core-private-devel = 6.2.2 needed by qt6-qml- private-devel, (got version 6.5.0~rc-lp154.13.1), nothing provides qt6-core- private-devel = 6.2.2 needed by qt6-quick-private-devel, (got version 6.5.0~rc-lp154.13.1), nothing provides qt6-gui-private-devel = 6.2.2 needed by qt6-quick-private-devel, (got version 6.5.0~rc-lp154.13.1), nothing provides qt6-core-private-devel = 6.2.2 needed by qt6-shadertools-private-devel, (got version 6.5.0~rc-lp154.13.1) how can i resolvethis depencies issues in spec files?

2 1

Re: inconsistent CFLAGS between standard and v3 builds
by Marcus Meissner 21 Mar '23

21 Mar '23

On Fri, Mar 10, 2023 at 10:39:51AM -0300, Cristian Rodríguez wrote: > Hi: > > Just in case it is a known issue, writing here first: > > I expect x86-64-v3 packages to be built with the same > CFLAGS/LDFLAGS7CXXFLAGS/etc of the standard packages ´plus > -march=x86-64-v3 . however this is not currently the case, LTO appears > to be disabled as well stack clash protection and stack protector > strong. it seems it is picking the wrong information. > > CFLAGS currently in use for x86_64-v3 seem to be > > "-O2 -g -march=x86-64-v3 -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 > -fstack-protector -funwind-tables -fasynchronous-unwind-tables" > > while standard builds are: > > " -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 > -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables > -fstack-clash-protection -Werror=return-type -flto=auto -g" > > This cannot be intentional.. I am missing something? it seems to be falling back to some default buildops flag. Not sure if the projectconfig needs a new Optflags: x86_64-v3 Or if the build script needs to be fixed. Ciao, Marcus

5 6

New Blog Post! Continuing on API Documentation
by Dario Leidi 21 Mar '23

21 Mar '23

Hello everyone, The Build Solutions team keeps working on the API Documentation by adding more Sources endpoints. Please check out our latest blog post to learn more: https://openbuildservice.org/2023/03/21/continuing-api-docs-sources/ Kind regards, The Build Solutions Team

1 0

Slow builds on PPC64
by Reinhard Max 20 Mar '23

20 Mar '23

Hi, since mid last week or so I've seen builds on PPC64 workers that take very long, e.g. > 5h for a package that normally builds in less than 10 minutes. Sometimes the log just pauses several times for more than an hour each. Here is an example: https://build.opensuse.org/package/live_build_log/home:rmax:branches:securi… Is this a known problem? cu Reinhard

2 1