March 2021 - openSUSE Build Service - openSUSE Mailing Lists

Unconditional rebuild of project - or re-signing every package in a project
by Stefan Botter 21 Mar '21

21 Mar '21

Hi everyone, I need help on a private instance of OBS: Packman (PMBS). Due to oversight/lazyness the standard GPG key expired a while ago. Once I extended the key, one of the projects could not be signed anymore. Most probably while fixing the expired-key-problem I removed a very old standard key from the keyring, which in turn signed the project key of the now failing project. I could get the project working and signing by issuing a new project key using 'osc signkey ...'. So far everything is ok, but with Packman we have an external publishing mechanism (through publishing_hooks), which stages published repos to an external server, where the packages are re-signed with the Packman RPM key. Part of the re-signing is a check for the original key used by PMBS. If they used key on PMBS is not in the keyring of the re-signer, the packages are not re-signed and hence not published. Totally our problem. The way out for me is either a) allow the new key on the re-signer, or b) change the project key on PMBS for said project. Option "a" is easy, but I am not allowed to do that, and our fellow with access is not available at the moment. I chose option "b" using a modified already known key and injected it to the project using 'obs_admin -update-project-signing-key ...'. This is working perfectly. Now the problem at hand: New packages are signed, re-signed and published through our workflow as expected. All other packages built since the issue with the renewed project signing key started and before I set the actual working project key are still signed with the "unknown" key and are not re-singed and published. I see three possible ways out of this situation: 1. wait for a occasional rebuild of the respective package, 2. rebuild the whole project unconditionally, or 3. re-sign all packages form the project with the new project key, and republish through PMBS. Solution 1 is of course the "natural" way, but it is unclear, when rebuild and publishing happens, and it is sort of random - lame :) Solution 2 is acceptable, but is costlier than 3. Solution 3 seems the fastest, but I am unsure, if this can be triggered from PMBS. TL;DR: How can I trigger an unconditional rebuild of all packages inside a project? Can I trigger only a re-signing of packages in a project, and trigger a fresh publishing from PMSB? Any help is greatly appreciated! TIA, Stefan PS: The project in question is "Multimedia", which seems to be quite popular :) -- Stefan Botter zu Hause Bremen

2 2

How to remove decommissioned workers from OBS monitoring page
by Morschhäuser, Mark 18 Mar '21

18 Mar '21

Hello, we created some test workers for our private OBS instance and wonder how to remove them from the monitoring page. Is there a command to do that? Thank you in advance, Mark

2 1

Re: How can I add in a spec file the build version and distribution version in a spec file?
by Erico Mendonca 17 Mar '21

17 Mar '21

Have you tried using something like "-DANTIMICROX_PKG_VERSION=\"'%{version}-%{release} (openSUSE Leap/x86_64)'\"" in your SPEC? [cid:dd6920b0-e198-4ad7-ac2d-fba2ac510d7d] Erico Mendonca Premium Services SUSE ________________________________ From: Carsten Ziepke Sent: Wednesday, March 17, 2021 2:45 PM To: opensuse-buildservice(a)opensuse.org Subject: How can I add in a spec file the build version and distribution version in a spec file? Hello, a package I maintain in OBS added a new feature to enable reproducible builds: https://github.com/AntiMicroX/antimicrox/pull/143 "By default, the date and time of the build are embedded into the binary as sort of origin/version/etc. marker. This is not, however, reproducible. This patch makes it so that packagers can define a præprocessor macro, ANTIMICROX_PKG_VERSION, to a C string which is then used instead; if this macro is not defined nothing changes." For example: "-DANTIMICROX_PKG_VERSION=\"'3.1.4-1 (Debian sid/amd64)'\"" How can I do this in the same way in OBS (add buildversion and distribution version) via spec file? Thank you, Carsten -- Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of code using nothing but vi or emacs. AAAAACK! -- Discussion on the intuitiveness of commands, especially Emacs

1 0

How can I add in a spec file the build version and distribution version in a spec file?
by Carsten Ziepke 17 Mar '21

17 Mar '21

Hello, a package I maintain in OBS added a new feature to enable reproducible builds: https://github.com/AntiMicroX/antimicrox/pull/143 "By default, the date and time of the build are embedded into the binary as sort of origin/version/etc. marker. This is not, however, reproducible. This patch makes it so that packagers can define a præprocessor macro, ANTIMICROX_PKG_VERSION, to a C string which is then used instead; if this macro is not defined nothing changes." For example: "-DANTIMICROX_PKG_VERSION=\"'3.1.4-1 (Debian sid/amd64)'\"" How can I do this in the same way in OBS (add buildversion and distribution version) via spec file? Thank you, Carsten -- Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of code using nothing but vi or emacs. AAAAACK! -- Discussion on the intuitiveness of commands, especially Emacs

1 0

Repository Signing Key Expiry
by Mark Grant 16 Mar '21

16 Mar '21

This email is specific to Debian / Raspbian repos. 1) This is the first problem. Over the weekend the repo signing key downloaded during initial set-up expired. (This sort of set-up https://software.opensuse.org//download.html?project=home%3Am-grant-prg&pac…) This led to all attempts to use the repsitory to error out, (eg apt-get update, apt-get install....). The errors appeared as below:- sudo apt-get update Hit:1 http://archive.raspberrypi.org/debian buster InRelease Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:3 http://download.opensuse.org/repositories/home:/m-grant-prg/Raspbian_10 InRelease [1,531 B] Hit:4 https://apt.syncthing.net syncthing InRelease Err:3 http://download.opensuse.org/repositories/home:/m-grant-prg/Raspbian_10 InRelease The following signatures were invalid: EXPKEYSIG 3FD1CDB63E00F70B home:m-grant-prg OBS Project <home:m-grant-prg@build.opensuse.org> This happened to me and to an unknown size user community. 2) This is the second problem. I established that the key had been refreshed on opensuse.org and now had a mid-2023 expiry date so I thought re-downloading it using the curl command in the instructions should do the trick. The command worked OK but the curl command had changed from using a target keyring of "home:m-grant-prg.gpg" to "home_m-grant-prg.gpg". So the curl command did not overwrite the old keyring. The end result was that the old expired key was still found and repository actions still errored out. The solution I have suggested to the user community is to remove the offending keyring. It seems obvious that this exact same problem will occur in 2023 (at least problem 1). I am sure that OBS has a transparent solution for this and I just have never seen it. I would be most grateful if someone could point me in the direction of the relevant documentation. Thanks, Mark

2 2

No live log available" when a separate worker build job finished
by ynliu＠linx-info.com 16 Mar '21

16 Mar '21

I had installed a private OBS server (2.9.6 appliance)on x86_64 machine and disable obs worker component, Meanwhile, I also installed a separate x86_64 worker on another machine and a arm64 obs worker on raspberry pi4, I configure obs server and these two separate obs worker(x86_64 and arm64 pi4) according to manual "https://openbuildservice.org/help/manuals/obs-admin-guide/" and "https://openbuildservice.org/help/manuals/obs-user-guide/" Meanwhile, the following content was gotten on dispatcher.log file on obs server "badhost event: home:<username>:<projectname>/hello/x86_64/x86_64:obs-worker-x86:1 Use of uninitialized value in concatenation (.) or string at /usr/lib/obs/server/bs_dispatch line 628. Use of uninitialized value in concatenation (.) or string at /usr/lib/obs/server/bs_dispatch line 629. " on obs worker machine, look up /var/cache/obs/worker/root_x, all debs(debian packages) may be made successufully. why does I alway get the ERRROR? Could you give me any help or advices ? I can registered two separate obs workers to obs server (2.9.6) and build jobs may be started (both arm64 and x86_64), but alway get the following hint on WebUI/API after I start debian package "hello" building "No live log available: package 'hello' has no logfile" Additionally,I also test 2.10.10, But I can confirm that it is problem about bs_worker, because I found a "Logfile is not that big" output from function 'stream_logfile()' in /usr/lib/obs/server/worker/bs_worker through looking up rep_server.log or capturing network packet by wireshark tools

1 0

Server Status - back-home i586/x86_64 dead - back-other i586 dead
by munix9 14 Mar '21

14 Mar '21

Server Status back-home i586/x86_64 dead back-other i586 dead https://build.opensuse.org/monitor

2 1

Kindly unsubscribe me from mailing list
by Nitesh Konkar 12 Mar '21

12 Mar '21

1 0

new devel project plus some spring cleanup
by Paolo Stivanin 11 Mar '21

11 Mar '21

Hello all, I'd like to start promoting openSUSE in the astro world, but in order to do that I'd like to first do some OBS cleanup/reorg. What I'd like to do is: * Push graphics/CImg to openSUSE:Factory * Push science/ccfits to openSUSE:Factory * Create devel project "Application:Astrophotography" * Move from KDE:Extra to Application:Astrophotography (the maintainer wrote in an old SR I made that they put libindi there because no one else wanted to maintain it) - libindi * Move from Application:Geo to Application:Astrophotography (I'm the current maintainer for this, so no issue here I guess) - phd2 * Delete from Science (I'm the one pushing to Science/ASTAP*, but because of the fast release cycle I stopped doing that and kept only the one in my home) - ASTAP{,-dbs,-g17data} * Move from home:polslinux:astrophotography to Application:Astrophotography - libindi-3rdparty (this is a must, having only libindi is of very little to no use. But I don't think this can be pushed to Factory. There are way too many firmware :)) - Skychart{,-data} - sirilic - lin_guider - ASTAP{,-dbs,-h17data} (the guys in Science told me that due to licensing issue -dbs can't go to factory, and without dbs it's of no use this program) - ser_player - astrometetry.net What are your thoughts on this? Thanks a lot, Best regards, Paolo

4 6

Please switch to an updated Fedora:Rawhide mirror
by Neal Gompa 10 Mar '21

10 Mar '21

Hey all, The mirror being used for most Fedora:Rawhide targets (ftp.fau.de) is no longer an official mirror and has been out of sync for over a month now. Can someone please switch it to another mirror that is kept up to date, such as ftp-stud.hs-esslingen.de (used already for some of them). Thanks in advance! -- 真実はいつも一つ！/ Always, there's only one truth!

2 1