December 2021 - openSUSE Build Service

"Additional projects in backend" mail
by Morschhäuser, Mark 22 Oct '24

22 Oct '24

Hello, I get mails from my OBS instance with the content Additional projects in backend: ["Test"] What is the problem and how do I fix the issue? Best regards, Mark Morschhäuser

4 4

[opensuse-buildservice] Add external source to a package?
by Carsten Ziepke 12 Sep '23

12 Sep '23

Hello, I want to update the package ja2-stracciatella in the games repository to version 0.17.0. https://build.opensuse.org/package/show/home:Kieltux:branches:games/ja2-str… The new version needs the library string_theory which is not available for openSUSE. The build process wants to download string_theory from github, because it is not found. [ 36s] Scanning dependencies of target string_theory [ 36s] [ 12%] Creating directories for 'string_theory' [ 37s] [ 25%] Performing download step (download, verify and extract) for 'string_theory' [ 37s] -- Downloading... [ 37s] dst='/home/abuild/rpmbuild/BUILD/ja2-stracciatella-0.17.0/build/dependencies/lib-string_theory/builder/string_theory-prefix/src/3.1.tar.gz' [ 37s] timeout='none' [ 37s] -- Using src='https://github.com/zrax/string_theory/archive/3.1.tar.gz' [ 37s] -- Retrying... Can I add string_theory (string_theory-3.1.tar.gz) manually to the package and patch the build process? Thank you, Carsten -- Well, since MS cant be sure of the username of someone downloading things, they are going to play it safe and have everything dowloaded and executed by Explorer as suid root. That way, it will run on ANY system anywhere. :) -- George Bonser <grep(a)cris.com>

3 4

Implementing a new APT publisher
by Arnaud Ferraris 30 Mar '22

30 Mar '22

Hi, We currently use OBS for building and publishing APT packages for the Apertis project[1] (a Debian derivative distribution). At the moment we use downstream patches for the publisher (src/backend/bs_publish) in order to use reprepro instead of dpkg-scanpackages/dpkg-scansources. As we're considering implementing a new APT publisher based on aptly[2], we'd like to do so in a way that can be upstreamed to OBS so it can benefit the whole community. This obviously raises several questions as to how we should proceed, so I'm sending this email as a call for advice/comments/suggestions. We're considering the following: - this new publisher would be implemented in addition to the existing dpkg-scan* based one and be selectable through global configuration options. - using aptly opens up possibilities, but it isn't always as straightforward as a few system() call; we would therefore need to either ship a helper tool or add a new BSPublisher submodule (the latter is the preferred option atm) - aptly can also be used through a REST API, which implies some asynchronous processing would be preferrable. Is there currently a way to handle async processing in OBS, or would that require another helper tool/module, if possible at all? We're only at the planning and design stage for now, so we would be very interested in your opinion and comments regarding the above. Thanks, Arnaud [1] https://apertis.org [2] https://aptly.info

3 3

The new OBS GIT/SCM bridge
by Adrian Schröter 20 Jan '22

20 Jan '22

Yes, really yet another obs git integration, but it might be the last one... ***** This is a disruptive change since it would offload really all source management and workflows into any git, gitlab, pagure or github instances. ***** OBS will just following defined git repositories for all the packageing files (like spec, kiwi or Dockerfiles, but also the upstream sources in form of tar balls or scm repositories). Any native OBS mechanics may *NOT* be usable anymore though. As this would affect more or less all development workflows and tooling, we like to get feedback from you. Esp. in the regard how you would use any the functionality. Some stuff to touch =================== mls and me worked on something the last two weeks what we wanted to have since a long time. We consider this version 0.1, meaning some parts are already working via some workarounds in some cases. We may change it incompatible at any time until the next OBS release happened. There are example setups in OBS to demonstrate this. And also hopefully enables us to discuss about possible setups and workflows for future projects. ***** Just to be clear, do *NOT* use this atm for any package which needs to be submitted to any of our active distributions! So defintive not in any official devel project. ***** If you want to test the existing examples you need to use a forked osc. You get it the tooling via the following commands, but be aware that I did not test much (even though I use it now permanent on my workstation): # zypper ar https://download.opensuse.org/repositories/home:/adrianSuSE:/OBSGIT/15.3/ OBSGIT # zypper dup --from OBSGIT This should update osc and the build package. Also the new obs-scm-bridge package gets installed. Afterwards at the absolute the minimum the follow commands should work: # osc co home:adrianSuSE:OBSGIT/git-example-1 # cd home:adrianSuSE:OBSGIT/git-example-1 # osc build What happens here is that the checkout is detecting that this is a scm bridged package. This is currently implemented as temporary hack via the special string in the package meta title element: <title>obs-scm:https://github.com/adrianschroeter/git-example-1</title> This currently defines the git repository which provides the sources. This will go into a sepecial structure later, but since this affects also remote OBS instances we need a longer prepared update for the stable versions before. osc is therefore not downloading any source files on his own but calls the bridge instead. The bridge is doing two things: 1) clone the git repository into the home:adrianSuSE:OBSGIT/git-example-3 directory. You can use any git command there now. You can *NOT* use osc to submit any change! 2) downloading all the assets. Assets are referenced files in the build descriptions. Esp. tar balls should not become part of these git repositories as this would not scale. But also upstream SCM can be refernced here. Please find out more about assets, how they can setup and how verification can be done in our pbuild documentation: http://opensuse.github.io/obs-build/pbuild.html#_remote_assets We have three examples in OBS to demonstrate how packages could get maintained this way: git-example-1 ============= This is one has our packaging specific files in git and is downloading the upstream files, like the tar ball via the asset mechanism. git-example-2 ============= This one is building directly from some git repository. Everyhing needed is part of this single git repository. The spec might got added in a branch controlled by the package maintainer. Updating the source would work via git merge or rebase. git-example-3 ============= This is basically building from 2 independend git repositories. The packaging specific files are in our own git. The upstream sources come from another git repository, specified inside of the spec file. Note: when you do a checkout using osc, you get currently the upstreams source inside of an .obscpio archive. I will change this to get the git repository as clone. Another example? Please try it on your own, all what you need to have is a git repository and set the <title> element in any package meta.... Please note that IBS has not yet deployed this new code, only build.opensuse.org is working atm. On Project Level ================ You can use the same <scmsync> element to specify a git repository in project meta. Any directory there is considered to be a package. Any build configuration parts (what you have in "osc meta prjconf" usually) can be stored in a file called '_config'. We support this in multiple ways: 1) One plain single repository providing everything. You can find a real life example here: https://build.opensuse.org/project/show/home:adrianSuSE:OBSGIT:Project-exam… or the git repo here: https://github.com/geckito/image-RaspBerryPi4-pi-hole As you notice, it is a repositoy from our Geckito project. This means the same project can get build inside of OBS or it can be build entirely independend using the "pbuild" tool. 2) An example which is more likely to suite larger projects, like our distributions is using git submodules. You can find an example here: https://build.opensuse.org/project/show/home:adrianSuSE:OBSGIT:Project-exam… or the git repo here: https://github.com/adrianschroeter/git-project-example-submodules This is just referencing two git repositories from our earlier examples. 3) A possible later option: We may support URLs on project level pointing to github/gitlab/pagure projects. And listing all repositories inside of these to build these. Tell if you think this would be useful. Disadvantage would be the lack of a signed reference to a git repository. The advantage would be that one would not need to deal with git submodules. In general some first documentation of this functionality can not be found here: https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.scm_bridge… -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

3 7

fc35 osc depends on python 3.9
by Stefan van der Eijk 19 Jan '22

19 Jan '22

I'm seeing a python abi dependency issue with the osc package in the fc35 repo: $ sudo dnf update Dependencies resolved. Problem: cannot install the best update candidate for package osc-0.175.0-321.4.noarch - nothing provides python(abi) = 3.9 needed by osc-0.175.0-321.5.noarch - nothing provides python3.9dist(chardet) needed by osc-0.175.0-321.5.noarch - nothing provides python3.9dist(m2crypto) needed by osc-0.175.0-321.5.noarch ============================================================================================================================================================================================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================================================================================================================================================================================= Skipping packages with broken dependencies: osc noarch 0.175.0-321.5 openSUSE_Tools 479 k Transaction Summary ============================================================================================================================================================================================================================================================================================================================= Skip 1 Package Nothing to do. Complete! FC35 comes with Python 3.10 installed: $ python --version Python 3.10.0 A previous package (still installed) did depend on the correct python version. This is the Requires difference between previous (osc-0.175.0-321.4.noarch, installed on my system) and current (osc-0.175.0-321.5.noarch, on the repo) package: $ diff <(rpm -qR osc | sort) <(rpm -qpR osc-0.175.0-321.5.noarch.rpm |sort) -U0 --- /dev/fd/63 2021-12-16 10:45:21.493561420 +0100 +++ /dev/fd/62 2021-12-16 10:45:21.494561419 +0100 @@ -1,3 +1,3 @@ -config(osc) = 0.175.0-321.4 -python3.10dist(chardet) -python3.10dist(m2crypto) +config(osc) = 0.175.0-321.5 +python3.9dist(chardet) +python3.9dist(m2crypto) @@ -6 +6 @@ -python(abi) = 3.10 +python(abi) = 3.9

3 5

Failed to connect to bus
by passiontech passiontech 29 Dec '21

29 Dec '21

Hi, I've struck a problem packaging/building Rivendell for openSUSE Leap 15.2. The "osc build --local-package" completes fine, but the "osc ci" build then fails: [ 1202s] ... testing for pre/postinstall scripts that are not idempotent [ 1202s] Failed to connect to bus: No such file or directory [ 1202s] postinstall script of rivendell-3.5.0-1.x86_64.rpm failed A link to the build log is here... https://build.opensuse.org/build/home:passiontech:rivendell:rivendell3/open… ... which is littered with several instances of the "Failed to connect to bus: No such file or directory" error, beginning as early as the buildsystem update/installation stage... [ 56s] wicked-service-0.6.63-lp152.1.3 ######################################## [ 56s] Failed to connect to bus: No such file or directory [ 56s] Created symlink /etc/systemd/system/network.service -> /usr/lib/systemd/system/wicked.service. Later instances of the "Failed to connect to bus: No such file or directory" error would be in response to... %post /bin/systemctl daemon-reload ... /bin/systemctl restart rivendell ... The spec file includes "BuildRequires: systemd" and the local build completes fine. As a relative newcomer to OBS, I was under the impression that if a package successfully builds locally, then it would also build on the server. What's gone wrong? Thanks for any helpful pointers. Best regards, Peter

1 0

What should the repo names for Leap be?
by Eric Schirra 24 Dec '21

24 Dec '21

Hello all, I hope I am in the right place with my question. It concerns the names of the repositories for Leap in the Build Service. Lately I notice that the names are handled differently. One time the name is openSUSE_Leap_15.4, the other time it is just 15.4. But which is correct? Where is defined and described how to name the repositories? But this does not only affect 15.4. For Leap 15.3 there are even two repos in devel:languages:perl. One is 15.3 and the other is openSUSE_Leap_15.3. Leap 15.4 is still completely missing. What should the name for Leap 15.4 be? Translated with www.DeepL.com/Translator (free version) Best regards Eric

5 6

package build stuck on blocked (AlmaLinux 8)
by Neal Gompa 23 Dec '21

23 Dec '21

Hey, I'm trying to build a package with AlmaLinux 8 and it seems to be stuck waiting to download 12 packages. See here: https://build.opensuse.org/package/show/home:Pharaoh_Atem:alma-nginx-module… It seems weird that it's stuck like that for so long on that... Can someone look and see what's going wrong? Thanks in advance, Neal -- 真実はいつも一つ！/ Always, there's only one truth!

4 7

OBS User Tsdgg32t2363t36: suspicious behaviour
by Carsten Ziepke 20 Dec '21

20 Dec '21

Hello, the RSS feed for build.opensuse.org showed some suspicious behaviour: https://build.opensuse.org/project/subprojects/home:Tsdgg32t2363t36 The subprojects, filenames, comments in this repository are all flooded with long text files. Look at this package for example: https://build.opensuse.org/package/show/home:Tsdgg32t2363t36:branches:home:… Maybe OBS User Tsdgg32t2363t36 is looking for some security leaks in obs? Bye, Carsten -- When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*". -- Linus Torvalds

6 7

Notifications Feature Release for All Users
by Daniel Donisa 17 Dec '21

17 Dec '21

Hi everyone, we just rolled a new feature out of the beta program: Notifications! This feature has been tested by the users taking part of the beta program since a while now. So we are confident enough to release it for every user. Check out our blog post for more details! https://openbuildservice.org/2021/12/17/notifications-feature-release-for-a… Kind regards, Your Build Solutions Team -- Dani Donisa, Build Solutions SUSE Software Solutions Germany GmbH

1 0