February 2020 - openSUSE Build Service

[opensuse-buildservice] AlpineLinux and OBS
by David Sugar 21 Feb '20

21 Feb '20

This is just to raise the question to simply initiate a discussion, why not have AlpineLinux on OBS too? On the positive side, it should be relatively easy to adapt since it is really rather similar to Arch, which is already supported on OBS, but simpler. On the other hand, unlike Arch, it also has 6 month releases that are supported for 2 years. I do appreciate those would accumulate over time. It also has a lot more architectures supported. So I do appreciate that it could also become a maintenance time sink in OBS. Also, I have no sense of the real size of the AlpineLinux using community, and I suspect most use it from the docker and container perspective, which is a valid and potential community that could benefit from OBS. In my particular case, I do use Alpine very broadly, and specifically for headless arm/IoT devices.-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 8

[opensuse-buildservice] OBS KIWI sometimes fails with "Problem: nothing provides /usr/bin/PROGRAM"
by opensuse.lietuviu.kalba 21 Feb '20

21 Feb '20

Hi, Maybe someone could help figure out, why sometimes OBS KIWI build fails with "Problem: nothing provides /usr/bin/PROGRAM"? But sometimes does not fail? E.g. from https://build.opensuse.org/package/live_build_log/X11:Pantheon:Branch:Media… [ 181s] [ DEBUG ]: 07:41:05 | system: Problem: nothing provides /usr/bin/kdesu needed by calamares-3.2.15-3.1.x86_64 [ 181s] [ DEBUG ]: 07:41:05 | system: Solution 1: do not install calamares-3.2.15-3.1.x86_64 [ 181s] [ DEBUG ]: 07:41:05 | system: Solution 2: break calamares-3.2.15-3.1.x86_64 by ignoring some of its dependencies (calamares recently added "requires: /usr/bin/kdesu" and forced starting via kdesu) -- Regards -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] signing issues with local OBS since yesterday
by Hans-Peter Jansen 20 Feb '20

20 Feb '20

Hi, It started with stalling in kernel-default signing process since tonight obsserver:~# l /srv/obs/events/signer/ total 20 drwxr-xr-x 2 obsrun obsrun 4096 Feb 1 10:41 ./ drwxr-xr-x 11 obsrun obsrun 4096 Jan 29 02:04 ../ prw-rw-rw- 1 obsrun obsrun 0 Feb 1 10:38 .ping| -rw-r--r-- 1 obsrun obsrun 141 Feb 1 03:35 finished:x86_64:LISA:Kernel::openSUSE_15.0::kernel-default-574de2f90256a108fe2108a7e0cff115 -rw-r--r-- 1 obsrun obsrun 141 Feb 1 03:35 finished:x86_64:LISA:Kernel::openSUSE_15.1::kernel-default-574de2f90256a108fe2108a7e0cff115 -rw-r--r-- 1 obsrun obsrun 141 Feb 1 03:34 finished:x86_64:LISA:Kernel::openSUSE_15.2::kernel-default-574de2f90256a108fe2108a7e0cff115 Even a complete rebuild of the repository doesn't change this state for the kernel-default builds. It's the first build of kernel 5.5, as linked from Kernel:stable/kernel-source OBS state is idle. All services are up. Looking into build log of one package (libdrm) shows: getbinaries: missing packages: libpciaccess0 (worker was obsserver:2) Accessing other build logs results in: No live log available: connect to 127.0.0.1:42947: Connection refused All updates for OBS Server 2.10 applied, rebooted, no change. OBS_Server_2.10_Staging added, upgraded, rebooted, no change. Any ideas anybody? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] How to ensure consistency for the "deleted" project? ("rails fix_project project=deleted" fails)
by Srinidhi B 19 Feb '20

19 Feb '20

Hello List, Every week, I receive an email from my local OBS Instance regarding the inconsistency between API and backend. It lists one item as follows: Additional projects in api: ["deleted"] I remember that Adrian had once suggested on this list on how to clean this up, but I'm unable to find that post. Looking at "rails -T" output and a few ReleaseNotes files, I found that I can run "rails {check,fix}_project" commands. When I run check_project, I get: $ run_in_api rails check_project project=deleted Project deleted lost on backend When I run fix_project, it fails with: $ run_in_api rails fix_project project=deleted rails aborted! ActiveRecord::StatementInvalid: Mysql2::Error: Cannot delete or update a parent row: a foreign key constraint fails (`api_production`.`path_elements`, CONSTRAINT `path_elements_ibfk_2` FOREIGN KEY (`repository_id`) REFERENCES `repositories` (`id`)): DELETE FROM `repositories` WHERE `repositories`.`id` = 3818 /srv/www/obs/api/app/jobs/consistency_check_job.rb:64:in `rescue in check_project' /srv/www/obs/api/app/jobs/consistency_check_job.rb:59:in `check_project' /srv/www/obs/api/app/jobs/consistency_check_job.rb:36:in `fix_project' /srv/www/obs/api/lib/tasks/delayed_job.rake:27:in `block in <top (required)>' bin/rails:4:in `require' bin/rails:4:in `<main>' Caused by: Mysql2::Error: Cannot delete or update a parent row: a foreign key constraint fails (`api_production`.`path_elements`, CONSTRAINT `path_elements_ibfk_2` FOREIGN KEY (`repository_id`) REFERENCES `repositories` (`id`)) /srv/www/obs/api/app/jobs/consistency_check_job.rb:64:in `rescue in check_project' /srv/www/obs/api/app/jobs/consistency_check_job.rb:59:in `check_project' /srv/www/obs/api/app/jobs/consistency_check_job.rb:36:in `fix_project' /srv/www/obs/api/lib/tasks/delayed_job.rake:27:in `block in <top (required)>' bin/rails:4:in `require' bin/rails:4:in `<main>' Caused by: ActiveXML::Transport::NotFoundError: <status code="404"> <summary>project 'deleted' does not exist</summary> <details>404 project 'deleted' does not exist</details> </status> /srv/www/obs/api/lib/backend/connection.rb:122:in `handle_response' /srv/www/obs/api/lib/backend/connection.rb:31:in `get' /srv/www/obs/api/lib/backend/connection_helper.rb:48:in `http_get' /srv/www/obs/api/lib/backend/api/sources/project.rb:78:in `packages' /srv/www/obs/api/app/jobs/consistency_check_job.rb:60:in `check_project' /srv/www/obs/api/app/jobs/consistency_check_job.rb:36:in `fix_project' /srv/www/obs/api/lib/tasks/delayed_job.rake:27:in `block in <top (required)>' bin/rails:4:in `require' bin/rails:4:in `<main>' Tasks: TOP => fix_project (See full trace by running task with --trace) Am I doing something wrong or is something missing on the API side? Or am I using the command incorrectly? Regards, Srinidhi. PS: run_in_api is a function I have extracted from OBS scripts: $ type run_in_api run_in_api is a function run_in_api () { export RAILS_ENV="production"; sudo chroot --userspec=wwwrun:www / /bin/bash -c "cd $API_ROOT && RAILS_ENV='production' /usr/bin/bundle.ruby2.5 exec $*" }

2 2

[opensuse-buildservice] More responsive and mobile friendly
by Lukas Krause 18 Feb '20

18 Feb '20

Hey there, We started to make the UI of the Open Build Service more responsive and mobile friendly. Please checkout our latest blog post to find out more|:| |https://openbuildservice.org/2020/02/17/mobile-first-layout/| || || We are looking forward to hearing from you. The OBS Team -- Lukas Krause, Build Solutions SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 0

[opensuse-buildservice] KIWI build
by Roger Oberholtzer 18 Feb '20

18 Feb '20

I am trying to an OS image using KIWI in the build service. It had been working as of a month or so ago. Now it complains with: have choice for product_flavor (openSUSE) needed by openSUSE-release: followed by a number of packages that I guess are needed to run kiwi and whatever. I know what this generally means with dependencies in an RPM spec type of build. I do not know what to do about this in the context of KIWI. Is if that it wants to know if I want Leap 15.1, 15.2, or Tumbleweed? I am happy with either 15.1 or Tumbleweed. If this is what I need to be specifying, where do I do this? The docs about the web interface (https://en.opensuse.org/openSUSE:Build_Service_prjconf) didn't help me. Or at least I'm not sure what I need to be setting. That doc's reference to an advanced tab is odd as I do not see such a tab. I guess using the actual tab name might be better than using the name of what one might call what the tab contains. My project is https://build.opensuse.org/package/show/home:rogeroberholtzer:RSL/oem In the project top (https://build.opensuse.org/package/show/home:rogeroberholtzer:RSL) Meta, I have this: <repository name="images"> <path project="Virtualization:Appliances:Builder" repository="openSUSE_Leap_15.1"/> <path project="openSUSE:Leap:15.1" repository="standard"/> <arch>x86_64</arch> </repository> I thought that should select openSUSE Leap 15.1 Maybe that's not enough or the correct place? Or I'm simply confused... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 5

[opensuse-buildservice] OBS 2.10.1 released
by Adrian Schröter 18 Feb '20

18 Feb '20

OBS 2.10.1 released =================== This release provides compability for interconnect to build.opensuse.org, so an update is highly recommended. It is also providing support for RHEL 8 and CentOS 8 rpm-md modules. However, this is still considered to be as experimental. A little background, these distros provide many packages in (sub)-modules inside of repositories. You would get conflicts due to conflicting packages with OBS 2.9 and before. OBS 2.10.0 filtered therefore all module packages to allow to solve a dependency at all. This 2.10.1 release offers a way to enable selected modules via project config. However, we may still modify the behaviour here, so don't consider this as final implementation.s. Apart from this we backport some further features and fixes from master branch. See the attached ReleaseNotes file for details. Updaters from OBS 2.10.0 release can just ugrade the packages and restart all services. Updaters from former releases should read the README.UPDATERS file. OBS update are available from the following projects: https://build.opensuse.org/project/show/OBS:Server:2.10 The appliance can be downloaded from http://openbuildservice.org/download Details from ReleaseNotes file ============================== Features ======== Backend: * EXPERIMENTAL: Add support for rpm-md modules (RHEL/CentOS 8 only). Modules can get enabled via ExpandFlags: module:$MODULE_NAME in build configuration. Note: they tend to conflict. * bs_publish: support Debian's InRelease file * support zchunk compression for rpm-md metadata * new systemd-nspawn backend * Support zstd compression for rpm and deb Bugfixes ======== Frontend: * Fix partial editor option hash defaults (obs#8018) * Fixed inconsistent data on package undelete * Sphinx startup fixes * Fix maintained projects link Backend: * Support openssl 1.1 and newer * fix publisher sleeping behaviour (obs#8276) * bs_publish: fix $rsync_extra_options handling (obs#8384) * service expansion: tweak oldfiles handling (obs#7596) * fix publishing of containers when no registry is configured Shipment: * obsdodup starts after obsapisetup Bugfixes: * Make cleanup_scm_cache cron job work again * Fix LogRotate setup -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Dynamic BuildRequires and issues I've found around
by Igor Gnatenko 18 Feb '20

18 Feb '20

Hello, I've been looking into using OBS for building Rust packages from Fedora. Those are, of course, using latest and greatest features of RPM. Dynamic BuildRequires is one of them. Each spec file on top has %bcond_with/%bcond_wihout and %cargo_generate_buildrequires is using variables defined by those to control which dependencies it emits. That said, I've found some obstacles on getting 900+ packages built in OBS: 1. Since there are some dependency loops and I've already pushed all specs, changing prjconf to have %_without_check 1 did not force OBS to re-evaluate dependencies, I basically had to remove build target for F31 and add it back. Neither, after initial bootstrap, removing that macro did anything. 2. There are few packages which got into some weird state and I could not fix them. 2.1. rust-qrcode says that there are broken deps on crate(image), but that one is definitely is in the same OBS repo and is built fine 2.2. rust-restson complaining about missing hyper 0.12 while I've already uploaded new version which depends on hyper 0.13, making an empty commit to a repo does not help 3. Neal told me that OBS somehow can do the bootstrap of packages, but I could not find a way to set it up (everything what's needed is try to build with %_without_check defined, that will solve 99% of dependency loops). https://build.opensuse.org/project/show/home:ignatenkobrain:rust Meawhile, if you can tell me some way to kick OBS to regenerate Dynamic BuildRequires, this would be much appreciated! Thanks goes to Neal Gompa for helping me to set up an OBS project and continuous help with issues I run into. -- -Igor Gnatenko -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Fedora Modular repositories
by David Adam 17 Feb '20

17 Feb '20

Hi all, Is it possible to produce Fedora modular repositories using OBS? I couldn't find anything in the documentation or on GitHub, but perhaps I have overlooked something simple. The reason that I'm interested is that our package (shells:fish) is also in a lot of downstream projects, including Fedora. It's part of a separate module in Fedora 31. Unfortunately, module packages always take priority over standalone packages, so our OBS repository is never going to be selected by `dnf install`. Many thanks, David Adam zanchey(a)ucc.gu.uwa.edu.au -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Fedora Rawhide repository setup is broken
by Rosanne DiMesio 17 Feb '20

17 Feb '20

Fedora Rawhide, both i586 and x86_64, shows "The repository setup is broken, build or publish not possible." -- Rosanne DiMesio <dimesio(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1