February 2022 - openSUSE Build Service

[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

adding a debian repository from open build service
by Michael Behrisch 19 Jul '22

19 Jul '22

Hi, I try to add my home project's repo to a debian installation and did: sudo add-apt-repository https://download.opensuse.org/repositories/home:/behrisch/Debian_11/ sudo apt update and got the following error: apt update Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Ign:4 https://download.opensuse.org/repositories/home:/behrisch/Debian_11 bullseye InRelease Err:5 https://download.opensuse.org/repositories/home:/behrisch/Debian_11 bullseye Release 404 Not Found [IP: 195.135.221.134 443] Reading package lists... Done E: The repository 'https://download.opensuse.org/repositories/home:/behrisch/Debian_11 bullseye Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. The repository has a Release file and I can also retrieve it (using wget for instance). Reading the apt-secure manpage I thought it might be an issue with authentication but "apt update --allow-unauthenticated" gives the same error. I also tried it with ubuntu with the same results. Adding ubuntu ppas from launchpad works however. Thanks for any hints! Best regards, Michael

5 10

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

Use of kernel.obs.guest/initrd.obs.guest
by Marcus Schäfer 10 Mar '22

10 Mar '22

Hi, I have an image build here: osc rbl Virtualization:Appliances:Images:Testing_x86:debian test-image-live-disk -M Disk images x86_64 It starts Qemu with [ 18s] /usr/bin/qemu-kvm ... -kernel /boot/kernel.obs.guest -initrd /boot/initrd.obs.guest I assume it does this because there is no kernel-obs-build or any other kernel (linux-generic) installed when building the test for debian I wanted to extend the testing matrix and add a test for luks (I plan to add support for luks2 in kiwi and wanted to have it really tested everywhere) When I do this the build ends with: [ 317s] [ DEBUG ]: 08:33:34 | EXEC: [cryptsetup --key-file /var/tmp/kiwi_9teoanif luksOpen /dev/mapper/loop0p2 luksRoot] [ 319s] [ 300.670200] device-mapper: table: 254:3: crypt: unknown target type Device mapper complains because the kernel or the initrd did not offer support for dm_crypt. Now the question is where does kernel.obs.guest and initrd.obs.guest come from ? How can I influence them, e.g providing an initrd that has dm_crypt as module, or a kernel that has it compiled in ... or any other solution suggestion :) Thanks much Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer Am Unterösch 9 Tel: +49 7562 905437 D-88316 Isny / Rohrdorf Germany -------------------------------------------------------

2 2

CentOS 8 EOL and OBS
by Oliver Smith 10 Mar '22

10 Mar '22

Hi, with CentOS 8 being EOL, and the binary repositories now gone: * will building packages for CentOS 8 keep working in the public OBS? * will building packages for CentOS 8 keep working in private instances for OBS? Right now, both are still working. I guess this is because of cached packages, that will expire at some point and then it starts failing? Or is the public OBS possibly building all of the CentOS packages and that gets used instead of the official repositories, and it will keep on working for some years? If that assumption is true, is that also where the private OBS instances download packages from? Thanks! Best, Oliver

2 1

Wrong path to %{name}.lang in %files section when use tarball-less source service
by Alexey Svistunov 28 Feb '22

28 Feb '22

Hello! I am try to follow a 'Avoid tar balls' section of OBS documentation at https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.best-pract… and got an error when processing a lang package files: "[ 555s] Processing files: mypackage-lang-1.0.noarch [ 555s] error: Could not open %files file /home/abuild/rpmbuild/BUILD/home/abuild/rpmbuild/SOURCES/mypackage-lang-1.0.noarch/mypackage.lang: No such file or directory" Extra leading directories are present in the path: /home/abuild/rpmbuild/BUILD/home/abuild/rpmbuild/SOURCES/... I was looking for how %files -f works, but it looks like the basic rpm functionality, not a macro. Probably I can fix it by setting some variable manually before processing? My specfile looks like at guide: %if %{build_tar_ball} Source0: %{name}-%{version}.tar.bz2 %else Source0: _service %endif ... %prep %if %{build_tar_ball} %setup -q %else %setup -n %_sourcedir/%name-%version -T -D %endif _service: <services> <service name="obs_scm"> <param name="url">git://git.code.sf.net/p/mypackage/code</param> <param name="scm">git</param> <param name="versionformat">2.5+git%cd.%h</param> <param name="filename">mypackage</param> </service> <service mode="buildtime" name="set_version"/> </services> But when %define build_tar_ball 1 - the package build successful, %file -f path is correct. Looks like a bug... Or I am doing something wrong?

1 0

Building Arch Linux packages
by Michael Ströder 28 Feb '22

28 Feb '22

HI! I'm trying to build mostly Python modules for Arch Linux: https://build.opensuse.org/project/show/home:stroeder:arch-iam This works as long the packages does not have a dependency on another module built in this local repo. With such a dependency build fails with a message like this: PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.10/site-packages/ldap0-1.4.8-py3.10.egg-info/PKG-INFO' If I remove the local repo dependency such a package builds but without the correct dependency. Any clue what's going on? Anything I have to add to the project config to make it work? Many thanks in advance. Ciao, Michael.

3 4

Enhancement Request: Proper extensions for SRPMs
by Stefan Bluhm 24 Feb '22

24 Feb '22

Hello, I would like to request a feature for SRPMs (assuming this is the right group). When creating static links in the repo, a package with just the name but not the version is generated and linked to the latest package with the version. I.e: https://download.opensuse.org/repositories/home:/sbluhm/CentOS_8/x86_64/pac… links to https://download.opensuse.org/repositories/home:/sbluhm/CentOS_8/x86_64/pac… This is great as I can always reference a package that never has a changing name. Unfortunately, the identical reference is kept for SOURCE packages. So source packages are named "package.rpm" and not "package.src.rpm". i.e. https://download.opensuse.org/repositories/home:/sbluhm/CentOS_8/src/packag… links to https://download.opensuse.org/repositories/home:/sbluhm/CentOS_8/src/packag… Is there any chance to implement a feature so that https://download.opensuse.org/repositories/home:/sbluhm/CentOS_8/src/packag… links to the corresponding source package? I have an application that blocks the package.rpm as not being a source package. Thank you and best wishes, Stefan

1 0

Something corrupt on build.opensuse.org storage for Ubuntu 20.04 cached data?
by Neal Gompa 24 Feb '22

24 Feb '22

Hey all, So the problem I'm seeing with CentOS Stream 9 stuff[1] is now happening to my Ubuntu 20.04 builds. Server returned an error: HTTP Error 400: Bad Request 86remote error: remote error http //ftp.halifax.rwth-aachen.de/ubuntu/pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-mit_2.1.27+dfsg-2ubuntu0.1_amd64.deb /srv/obs/build/Ubuntu 20.04/update/arch/ full/.dod.23611.libsasl2-modules-gssapi-mit.deb No such file or directory 87 This affects running "osc build" on packages in my private OBS interconnected with the openSUSE Build Service. Building *in* the private OBS or openSUSE Build Service itself is fine, but using "osc build" locally is not. :( Can anyone help? [1]: https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/th… -- 真実はいつも一つ！/ Always, there's only one truth!

2 1

CentOS-8 build now fails in obs
by Marcus Schäfer 23 Feb '22

23 Feb '22

Hi, we build integration test images for CentOS8 in obs here: https://build.opensuse.org/project/show/Virtualization:Appliances:Images:Te… As you can see the images_CentOS8 target has stopped to resolve. The error message is osc buildinfo -M Disk images_CentOS8 x86_64 <buildinfo project="Virtualization:Appliances:Images:Testing_x86:centos" repository="images_CentOS8" package="test-image-live-disk-v8:Disk" downloadurl="https://download.opensuse.org/repositories"> <arch>x86_64</arch> <error>unresolvable: nothing provides system-packages:repo-creation</error> <srcmd5>491553c3ee749cec881ba097a5794705</srcmd5> <verifymd5>81b4d6bfb024ee04a096064363c621f5</verifymd5> <rev>19</rev> <specfile>_service:obs_scm:appliance.kiwi</specfile> <file>_service:obs_scm:appliance.kiwi</file> <versrel>1.3.0-19</versrel> <bcnt>1</bcnt> <release>19.1</release> <debuginfo>0</debuginfo> <imagetype>oem</imagetype> <module>virt-rhel</module> </buildinfo> And I have no clue where this comes from. Help is appreciated Thanks Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer Am Unterösch 9 Tel: +49 7562 905437 D-88316 Isny / Rohrdorf Germany -------------------------------------------------------

1 0