Re: [packman] TLS support on packman.links2linux.org
Hi Indraj, On Thu, 2024-04-25 at 18:57 +, Indraj Gandham wrote: > I noticed the other day that packman.links2linux.org does not appear to > support TLS. > > This may be a problem because YaST automatically fetches the Packman > signing key over an insecure connection and then asks the user to > verify that the key's fingerprint is correct. Since the website is no > longer delivered over HTTPS, this cannot be done safely. > > Apologies in advance if there is anything I have misunderstood. I have seen this too, and asked Marc to have a look at it. Thank you for notifying us! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Seems, i586 workers need activation
Hi, On Wed, 2024-03-27 at 19:05 +0300, Егор Кузнецов wrote: > Hi, seems i586 workers require manual intervention. Builds for Mesa i586, for > example, disabled, so cannot update Tumbleweed with packages of Mesa-32bit, > they need new version. This is not a problem of the workers, but the package A_tw-Mesa:drivers does not build ATM. It is linked to OBS:factory. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Fixed!, was: Re: Packages do not build due to qemu-kvm errors
Hi all, I injected a factory-derived build in PMBS and builds for Tumbleweed are on their way again. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packages do not build due to qemu-kvm errors
On Mon, 2024-03-25 at 11:27 +0100, Stefan Seyfried wrote: > On 23.03.24 19:35, Natasha Ament wrote: > > Hi, > > > > Since friday afternoon no package is building anymore on Tumbleweed, no > > package at all. All builds fail just after the VM is started. Packages that > > were built previously and have not changed will eventually seem like they > > build but they do not (as there is no change). You can also se the > > difference in the status graph that building of packages is erratic. > > https://bugzilla.opensuse.org/show_bug.cgi?id=1221759 > > Probably this one. > > Stefan might need to update the build package on the build service > server (because that gets injected into the workers and apparently > causes the issue), probably followed by a "obs_admin --drop-badhosts" to > get the workers into the scheduler again. Thank you, Stefan! I did have a short look Yesterday morning, and could identify, that the only Repository affected is Tumbleweed, and had a look at the common pitfalls for PMBS, like stale files, or missing updates. The problems started Wednesday evening, very close to the Tumbleweed snapshot around 8 p.m. CET, so - yes, seems right. I will try to find a fixed obs-build or build it myself to bring PBS back on track. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Gstreamer codecs outdated and conflict with gstreamer-plugins-bad-codecs-32bit
Hi Aaron, sorry for the late reply. On Mon, 2024-03-11 at 19:02 +, Aaron wrote: > Thank you, > I have created a login again for ukbeast89, could you please activate that > one. :) > > P.S. I also apologise for sending sending twice, I thought my email didn't go > through > Sent with Proton Mail secure email. Your account is no enabled in PMBS, happy packaging! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Gstreamer codecs outdated and conflict with gstreamer-plugins-bad-codecs-32bit
Hi Aaron, On Sun, 2024-03-10 at 14:09 +, Aaron wrote: : > Could I also please have my username activated, ukbeast89 for pmbs :) At least this I can do. You have created two accounts in the past: ukbeast and ubkeast89, both of which have been automatically deleted (in the OBS meaning) due do non-activation. I have removed all remaining entries and stale projects for these users now, please create your desired account again and reply, I will then activate this new account. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account activation
Hello Michele, On Sat, 2024-03-09 at 09:34 +0100, ConteZero wrote: > /Hello, /I would like to request account activation for /username alucardx on > //PMBS//. /Kind regards, I have activated your account, happy packaging! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Activate acccount on PMBS
Hi Маматазим Козубаев, On Tue, 2024-03-05 at 15:58 +0600, Маматазим Козубаев wrote: > Hello, can you activate my account on PMBS? My username is Nakadzima. > I want build some packages for me and other people. I have activated your account, happy packaging! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Signed up
Hi Natasha, On Thu, 2024-02-29 at 06:58 +0100, Natasha Ament wrote: > I've signed up with my username stacheldrahtje for the packman buildservice. > > Could you please enable my account so I can use it. Thank you for signing up, your account is confirmed (enabled) in PMBS. Happy packaging, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] FYI: Server Status - armv7l & aarch64 - dead
Hi Stefan, On Fri, 2024-02-09 at 10:39 +0100, Stefan Seyfried wrote: > Hi Stefan, > > On 06.02.24 13:53, Stefan Botter wrote: > > Hi munix9, > > > > On Tue, 2024-02-06 at 10:35 +0100, munix9 wrote: > > > FYI: Server Status - i586 & x86_64 - dead > > > > > > https://pmbs.links2linux.de/monitor > > > > Thank you for the hint, the schedulers are running again. > > Today the ARM schedulers are dead ;-) > > Have fun anyway ...running again! > seife Gretings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] FYI: Server Status - i586 & x86_64 - dead
Hi munix9, On Tue, 2024-02-06 at 10:35 +0100, munix9 wrote: > FYI: Server Status - i586 & x86_64 - dead > > https://pmbs.links2linux.de/monitor Thank you for the hint, the schedulers are running again. Geetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] New user 00sapo
Hi Frederico, On Tue, 2024-01-09 at 19:46 +0100, Federico Simonetta wrote: > Hi, I have enabled your account in PMBS. > The official openSUSE repos on nvidia.com are fine. The CUDA RPM, instead, is > not the best. I think it would be better if it was in a repo so that it would > also offer updates and they could be in sync with the drivers. > > Anyway, the real reason why I wanted to re-distribute CUDA is that it is > needed for building NCCL. From my understanding, in OBS, all the dependencies > should be available at the building step because it works without a network > connection. Consequently, I would need to upload CUDA RPM to openSUSE's OBS, > but it is not allowed because it's not compliant with the OSI. > > So the question is: > a) would it be possible to redistribute the CUDA libraries from a home: > project in packman? I am not on top of the redistribution rights of the CUDA Tooklit SLA, but in 1.1.2 Distribution Requirements, 1. "material additional functionality" is requested. Also in 1.1.6. Components Under Other Licenses, the possible existence of components with separate terms is mentioned. These components may disallow redistribution. Nevertheless, we do not export user's home project, so you cannot publish anything from your home project. > b) could I use that home: project as a BuildRequires of another project > (maybe on openSUSE's OBS)? I do not think that OBS allows reference to projects from remote build service instances. Anyhow, I myself had trouble using PMBS projects in a private build services instance, probably due to a PMBS configuration shortcoming, so I am pretty sure my answer to your question is also: no. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Slowroll: missing 'libplacebo.so.292()(64bit)' for ffmpeg-6 installation
Hi Terje, On Sun, 2023-11-19 at 14:44 +0100, Terje J. Hanssen wrote: > When I should install ffmpeg-6 for Slowroll, it reports missing dependices: > > zypper in ffmpeg-6 > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > Problem: nothing provides 'libplacebo.so.292()(64bit)' needed by the > to be installed libavfilter9-6.0-1699.5.pm.1.x86_64 > Solution 1: do not install ffmpeg-6-6.0-1699.5.pm.1.x86_64 > Solution 2: break libavfilter9-6.0-1699.5.pm.1.x86_64 by ignoring > some of its dependencies > > It would be fine to also get the latest ffmpeg 6.1 release for Slowroll > ASAP! > ffmpeg 6.1 is apparently going to be used by Cinelerra-GG soon. Due to kind help on the buildservice mailing list the build problems for the Slowroll packages heve been resolved. There had been stale files in the build service internals, which affected only some packages for Slowroll - probably rather random, and only during a 25 min time slot. These problems are fixed, the Slowroll packages should have been build by now and are probably on the mirrors already. Please give it a try! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Slowroll: missing 'libplacebo.so.292()(64bit)' for ffmpeg-6 installation
Hi Stefan, On Wed, 2023-11-22 at 11:27 +0100, Stefan Seyfried wrote: > On 20.11.23 08:08, Stefan Botter wrote: > > On Sun, 2023-11-19 at 14:44 +0100, Terje J. Hanssen wrote: > > > When I should install ffmpeg-6 for Slowroll, it reports missing > > > dependices: > > > > : [dependency problem with ffmpeg-6] > > > > > It would be fine to also get the latest ffmpeg 6.1 release for Slowroll > > > ASAP! > > > ffmpeg 6.1 is apparently going to be used by Cinelerra-GG soon. > > : > > > Rgds > > > > > > Terje J. Hanssen > > > > Several x64_64 builds for Slowroll are not starting on our workers for > > quite a while now, since approx. late September. The individual build > > environment for the worker process is not set up correctly, the build > > fail, and I have no clue, why that is. Manual builds initialize the > > build environment correctly. This is for now limited to Slowroll and > > some (for PMBS) unusual repos like xUbuntu_x.y. > > I tried raising a question for help on buildservice at opensuse.org > > several weeks ago, but there were no replies - to be fair, I did not > > expect any real help there, PMBS and all private OBS installations are > > only a nuisance there. > > > > I do not have time a energy to debug these edge cases, as builds for > > Leap and TW are running successful. Due to my rant (was not meant that way ...) Adrian, Bernhard, Manfred and Andreas chimes in on the problem, and meanwhile I identified and fixed the cause. > I still have an unused pmbs openvpn config/certificate which I'll use to > set up an x86_64 worker and try to reproduce / debug the issue. Not sure > when I'll get to it, though. > > So don't be surprised if another worker pops up ;-) Not needed anymore, but proceed at your own discretion :) Thank you for your offer, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Slowroll: missing 'libplacebo.so.292()(64bit)' for ffmpeg-6 installation
Hi Terje, On Sun, 2023-11-19 at 14:44 +0100, Terje J. Hanssen wrote: > When I should install ffmpeg-6 for Slowroll, it reports missing dependices: : [dependency problem with ffmpeg-6] > It would be fine to also get the latest ffmpeg 6.1 release for Slowroll > ASAP! > ffmpeg 6.1 is apparently going to be used by Cinelerra-GG soon. : > Rgds > > Terje J. Hanssen Several x64_64 builds for Slowroll are not starting on our workers for quite a while now, since approx. late September. The individual build environment for the worker process is not set up correctly, the build fail, and I have no clue, why that is. Manual builds initialize the build environment correctly. This is for now limited to Slowroll and some (for PMBS) unusual repos like xUbuntu_x.y. I tried raising a question for help on buildservice at opensuse.org several weeks ago, but there were no replies - to be fair, I did not expect any real help there, PMBS and all private OBS installations are only a nuisance there. I do not have time a energy to debug these edge cases, as builds for Leap and TW are running successful. For the time being I cannot offer any help, Slowroll from Packman is not completely built. All available packages are roughly in their state since late September. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] The i586 runner needs a kick
Hi Carsten, Am Donnerstag, dem 12.10.2023 um 17:10 +0200 schrieb Carsten Ziepke: : > http://ftp.pbone.net/mirror/packman.iu-bremen.de/suse/openSUSE_Tumbleweed/Essentials/i586/ > Mesa-23.2.1-1699.361.pm.1.i586.rpm 06-Oct-2023 00:25 53K Wow! Where did they get these files from? packman.iu-bremen.de is gone for a long time, and even the replacement DNS name packman.jacobs- university.de is not working anymore for at least 2 years now. They deleted the virtual machine and did not restore it, although they promised :( I am not working there anymore. The most reliable mirror to use is probably GWDG. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] The i586 runner needs a kick
Hi Felix, Am Mittwoch, dem 11.10.2023 um 03:08 -0400 schrieb Felix Miata: > Andreas Schneider composed on 2023-06-30 18:57 (UTC+0200): > > > https://pmbs.links2linux.org/package/show/Essentials/A_tw-Mesa > > > > built for x86_64 but i586 didn't build Mesa 23.1.3 so I'm unable to > > install it > > as Mesa-32bit is still on the old version. > > > Could someone please take a look? > > Nothing on gwdg.de mirror now. Is this considered expected any more? As far as I can see the Mesa packages have been built correctly for Tumbleweed x86_64 and i586. The actual version is 23.2.1, building succeeded on Oct 5th, between 8 and 9 p.m. CEST. Right now at least GWDGs mirror has the actual build results. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Workers for x86/_64 are borked :-)
Hi Stefan, picking up on that: Am Freitag, dem 29.09.2023 um 20:48 +0200 schrieb Stefan Seyfried: > Hi Bjørn, > > On 29.09.23 17:23, Bjørn Lie wrote: > > Heads-up people - seems the build workers are on strike. : > > This goes on and on until > > > > [ 193s] Generating "/run/initramfs/rdsosreport.txt" > > [ 193s] > > [ 193s] > > [ 193s] Entering emergency mode. Exit the shell to continue. > > [ 193s] Type "journalctl" to view system logs. > > [ 193s] You might want to save "/run/initramfs/rdsosreport.txt" to a > > USB > > stick or /boot > > [ 193s] after mounting them and attach it to a bug report. > > [ 193s] > > [ 193s] > > [ 193s] Give root password for maintenance > > Is this failing for all builds? Or only for certain distributions? > It seems like some "VMinstall: kernel-obs-build" is missing from the > prjconf (or it is trying to build for a distribution that's not > providing a kernel-obs-build), and the host's initrd is not good > enough > for an OBS build VM. > > -kernel /boot/vmlinuz --initrd /boot/initrd > > You have to be lucky if that works nowadays with hostonly initrds. I see, that some - if not all - builds for Slowroll fail on my workers (buildwk1 and 3) like in the above described scenario. Do you have an idea? OBS_VM_KERNEL and OBS_VM_INITRD are not set, and most other distributions work (we had a report about xUbuntu a few days ago). LG Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] x264-152 for Ubuntu 20.04
Hi Kye, On Wed, 2023-09-13 at 16:09 +, Kye Westwood wrote: > https://pmbs.links2linux.org/package/show/home:vmp/x264-152 > I can not build x264-152: > 400 remote error: connect to api.opensuse.org 443 No route to host > (worker was buildwk1:4) I have triggered a rebuild (already on Saturday), as the above message usually is a transient one. The package does not build, as the build environment on the worker does not initialize correctly for xUbuntu. Here I am not sure what is needed for build environments other than our usual openSUSE projects. ATM I do not believe, that this package can be built on PMBS due to the setup issues on the build workers. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] packman repository
Hallo Kye, On Thu, 2023-09-07 at 04:42 +, Kye Westwood wrote: > wie kommen fertig gebaute packages in packman repository (home:vmp)? Gar nicht. Der Buildserver veröffentlicht nur die offiziellen Projekte Essentials, Multimedia, Extra und Games. Wenn Du ein Paket in Deinem Homeprojekt baust, kannst Du es in eins der o.a. Projekte senden (osc sr ...). Wenn es dort gebaut wird, werden die Pakete auf die Mirror publiziert. LG Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Aktivierung des accounts für den username: vmp
Hallo Kye, On Tue, 29 Aug 2023 11:24:52 + (UTC) Kye Westwood wrote: > mit meiner alten email adresse kann ich keine emails an packman > verschicken, sie kommen dort nicht an. ich brauche aktivierung für > username: vmp Ich habe den Account vmp aktiviert. Du hattest noch den Account vmpt in einer separaten Mail erwähnt, soll es eher dieser sein? In dem Fall würde ich vmp wieder deaktivieren und vmpt aktivieren. LG Stefan PS: wie immer, wenn es solche Sachen zu tun gibt, bin ich im Urlaub! Es dauert leider immer wieder mal etwas länger. ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] The i586 runner needs a kick
Hi Andreas, Am Freitag, dem 30.06.2023 um 18:57 +0200 schrieb Andreas Schneider: > Hi, > > https://pmbs.links2linux.org/package/show/Essentials/A_tw-Mesa > > built for x86_64 but i586 didn't build Mesa 23.1.3 so I'm unable to > install it > as Mesa-32bit is still on the old version. > > Could someone please take a look? The schedulers are running again. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] The i586 runner needs a kick
Hi Andreas, Am Freitag, dem 30.06.2023 um 18:57 +0200 schrieb Andreas Schneider: > Hi, > > https://pmbs.links2linux.org/package/show/Essentials/A_tw-Mesa > > built for x86_64 but i586 didn't build Mesa 23.1.3 so I'm unable to > install it > as Mesa-32bit is still on the old version. > > Could someone please take a look? The schedulers are running again. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] aarch64 scheduler is dead...
Hi Stefan, hi all, Am Mittwoch, dem 21.06.2023 um 22:09 +0200 schrieb Stefan Seyfried: > see $subject, the aarch64 scheduler is dead ;-) > > Best regards, I am temporarily back from an extended bike tour, sorry for the delay! The schedulers are running again. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Could you activate my account please?, I'm umireon
Hi Kaito Udagawa, On Tue, 2023-06-20 at 02:14 +0900, Kaito Udagawa wrote: > I am a maintainer of an obs-studio plugin > (https://github.com/royshil/obs-backgroundremoval) and want to add our > plugin package to the Packman registry. > > Many people frequently ask us to provide packages for Fedora and > OpenSUSE, and I believe here is the right place to provide them with > the packages. > > My username is umireon and please activate my account. > https://pmbs.links2linux.org/project/show/home:umireon Welcome, and happy packaging, your account is enabled. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Introducing myself
Hello Mantari, On Thu, 2023-05-11 at 02:22 +, Muhammad Akbar Yanuar Mantari wrote: > Hai, everyone. > > In this opportunity, please allow me to introduce myself. My name is Mantari > (@mantarimay). Recently i maintenance mplayer on my > [repo](https://build.opensuse.org/package/show/home:mantarimay:apps/MPlayer). > I wish i can directly maintenance on Packman because there has been no > maintenance for a long time. > > That’s all I can say about this introduction. Thanks for your attention. Have > a nice day. Welcome! Your account is enabled, happy packaging! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Dead PMBS schedulers (x86_64 and aarch64...)
Hi seife, On Thu, 2023-05-04 at 18:59 +0200, Stefan Seyfried wrote: > See $SUBJECT, > > schedulers for aarch64 and x86_64 are dead... Thank you, they are running again. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Leap 15.3 is EOL, shouldn't it be deactivated to save resources and unnecessary builds?
Hi all, Am Mittwoch, dem 22.03.2023 um 10:39 +0100 schrieb Stefan Botter: > On Wed, 2023-03-22 at 10:09 +0100, munix9 wrote: > > Leap 15.3 is EOL, shouldn't it be deactivated to save resources and > > unnecessary builds? > > You are correct, this is on my calendar for next weekend. The weekend is there, openSUSE 15.3 is gone, and packages for openSUSE 15.5 are ready to be published to the mirrors. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Leap 15.3 is EOL, shouldn't it be deactivated to save resources and unnecessary builds?
Hi munix, On Wed, 2023-03-22 at 10:09 +0100, munix9 wrote: > Leap 15.3 is EOL, shouldn't it be deactivated to save resources and > unnecessary builds? You are correct, this is on my calendar for next weekend. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] pmbs i586 worker status - dead once more
Hi Simon, On Wed, 2023-03-22 at 00:20 +0100, Simon Vogl wrote: > Hello everyone, > > it appears like the i586 workers of pmbs have stopped working once more, > could someone please take a look at them? The scheduler is working again. There has been a strange situation with two of the workers, which did refuse to build. This should be fixed, at least temporarily. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Activate Packman OBS account
Hi Robert, Am Freitag, dem 17.03.2023 um 07:59 +0100 schrieb Robert Herb: > I am new at this list and want to say hello to all members! > > Can you (re)activate my OBS account, please? > It is quite a while since i registered and it seems I never asked for > activation. My username is Herbster0815 . Your account is activated, happy packaging! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] pmbs i586 worker status - dead
Hi Simon, On Sun, 2023-03-05 at 13:28 +0100, Simon Vogl wrote: > it appears like the i586 workers of pmbs are dead at the moment, could > someone please take a look at them? Thank you for the hint, the scheduler is running again. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account activation
Hi Nagllort, On Wed, 2023-03-01 at 21:05 +0300, Dmitry Balakin wrote: > Hello. Please activate my account. > Login: nagllort Your account is activated. Happy packaging, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Request to join your project
Hi Dima, sorry for the late reply, the cold got to me :( On Fri, 2023-02-24 at 12:13 +0300, Dmitry Balakin wrote: > Could you please send the required information as mentioned at > http://packman.links2linux.org ? Please follow the instructions laid out on https://pmbs.links2linux.de/: 1. sign up on the page (right side, e.g. enter username, email address and a password, click "Sign Up"). 2. subscribe to the mailing list packman at links2linux dot de, and 3. send a mail to that list introducing yourself (preferably mentioning your username). I need that trigger to activate your account, as the build system software does not have a notification mechanism notifying admins of pending new user sign-up. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Publishing in PMBS
Hi Eugene,
On Mon, 2023-02-20 at 23:15 +0200, Євген Попов wrote:
> First of all, thank you for activating my account. I already branched the
> package I needed and built it successfully. But now I can't figure out how to
> publish it properly: the publish flag for this repository is enabled and I
> can even see the rpms and can download them, but the link to the download
> repository is somehow broken and returns 404. Also, I can't find any
> documentation on the PMBS. How to properly publish a package in PMBS?
Publishing in packman is a layered process. We publish the repositories
of the projects Essentials, Extra, Games and Multimedia using hooks in
the build system's publisher to a staging server, where the packages are
singed with the published gpg key, introduced in the database for the
web page https://packman.links2linux.{org,de}, and prepared as download
repositories for the mirrors, which pull the then ready-to-use repos in
their schedule.
All other projects are not published in the sense of "public
availability". This is done to prohibit abuse, and conserve bandwidth of
the build system, which currently is hosted on a rented machine with an
ample, but nevertheless limited bandwidth, which it shares with several
other services running on the same host.
So, to answer your question for properly publishing in PMBS: build the
package in your home, submit it to one of the above mentioned projects.
Greetings,
Stefan
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account activation
Hi Evgeny, Am Mittwoch, dem 15.02.2023 um 11:12 +0200 schrieb Евгений Попов: > I just created my account, so, as stated in the instructions, I ask > you to activate it. My username is epopov. I plan to use the PMBS for > my personal purposes. Your account is now activated, happy packaging! Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] How do I subscribe to the mailing list?
Hi Roke, On Mon, 2023-02-13 at 20:28 +, roke beedell wrote: > I'd like to activate my account for the PMBS (rokejulianlockhart) but I'm > confused by the instructions. To subscribe to the mailing list simply send an empty mail with the subject "subscribe" to packman-requ...@links2linux.de, or visit the web site https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman and enter your email address in the entry field behind "Your email address:" in the "Subscribing to Packman" section, and press the "Subscribe" button. I have enabled your account in PBMS meanwhile. Greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi crash
Hi Eric, On Thu, 2023-02-02 at 16:34 +0100, Eric Schirra wrote: > Since probably kodi version 20, kodi crashes under Leap 15.4. > Is this only happening to me or to others as well? At least for my players kodi 20 is working without problem on 15.4. I have 4 instances, 2 are NUCs, one is an older Intel Celeron S with buildin graphics and the last one is my workstation with NVidia graphics. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Error when importing Packman repomd.xml.key
Hi Dominik, sorry for the late reply. On Tue, 2023-01-24 at 12:46 +0100, Dominik Heidler wrote: > @Stefan: > > Is there a chance to update the key? > It seems that the file was last changed about 9 years ago. IIRC we got aware of that problem a while back already. Again, IIRC, it is caused by or connected with the version of createrepo used on our publishing machine. This is Marc's domain, and he is still traveling, with limited online opportunities. He is aware of the issue, but can only attack that, when he is back and has the needed resources to make the appropriate changes to that system. Please be patient, it will be fixed! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Mesa-drivers x86_64 build fails with out-of-memory
Hi, On Mon, 2023-01-30 at 09:38 -0600, Malcolm wrote: > On Mon 30 Jan 2023 04:13:39 PM CST, Simon Vogl wrote: > : > > so maybe giving the workers a bit more than 1GB memory is still worth > > trying as a work-around? > > > > Hi > Checking buildwk1:1 through 4 and buildwk3:1 through 4 with `osc > workerinfo x86_64:buildwk1:1` shows the workers are using jobs=1, > memory=512M and swap=512. Sorry for that. Both machines have again 4 workers each, now with 5744M and 7509M per worker, respectively. What happened? Short answer: the obs-* packages from the stable release got updated, I rebooted the machines for the kernel update, and I missed to check for the correct amount of RAM in the worker VMs. Long version: OBS is rather lazy and dumb in automatically adjusting to the available hardware, it just takes exactly half of the available RAM and splits it up among the number of workers, which is taken from the number of CPU cores available, or defaulting to 512M. Apart from that one can define the amount of RAM for the worker instances using the config variable OBS_INSTANCE_MEMORY. If you have a considerable amount of RAM using just half of it is wasting resources. I modified obsstoragesetup from obs-common to take all available RAM, minus some small amount to give the OS place to breathe, and split the then available amount of RAM evenly between the worker instances. My patch does even more for NUMA machines, where the physical memory is divided between CPUs. Here the smallest NUMA block is considered and the available RAM is evaluated for the whole for all NUMA blocks combined. Unfortunately I seem to be the only one feeling the limitation of the original approach, and everyone else is fine with using just holf of the available RAM or is fiddling with individual manual RAM assignment. My PR has not seen any action (https://github.com/openSUSE/open-build-service/pull/10016), and each time the obs packages are updated, my patch is overwritten. Of course I could compile the packages myself to get out of that loop Monitoring could be another approach, but I am not even coming around to properly monitor the running schedulers. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] FYI: Server Status - i586 - dead
Hi munix9, On Thu, 2023-01-26 at 22:06 +0100, munix9 wrote: > FYI: Server Status - i586 - dead ... again :^X running again! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Mesa-32bit
Hi Michael, On Mon, 2023-01-16 at 18:41 +0100, mikey wrote: > Sorry I'm fairly new to using your repository, so please excuse me if this > isn't the right forum for asking this question. > > I have the Mesa and Mesa-32bit installed on version 22.3.2 and there is a > new version of Mesa 22.3.3 in your repo, but it would seem no corresponding > 32 bit package. > > According to zypper info the source package for Mesa-32bit is the same as > for Mesa. So has something changed or is there some type of delay in > publishing the 32 bit package? Some components of the build system software are not as reliable as we would like to have them, and sometimes a component, that decides and directs which packages when and how to build just stalls. In this case you see mismatches of package versions between architectures. Once the scheduler is restarted, all unbuilt packages will be built and - with a slight delay published. Meanwhile Mesa-32bit should be ready for installation in your desired version. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] FYI: Server Status - i586 - dead
Hi munix, On Sun, 2023-01-15 at 09:51 +0100, munix9 wrote: > FYI: Server Status - i586 - dead > > https://pmbs.links2linux.de/monitor > > thx ... and for quite a while, I have to admit. Running again. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account for PMBS
Hi David, sorry for the long wait, your account is now active. Am Dienstag, dem 15.11.2022 um 15:07 +0100 schrieb David Sterba: > I'd like to experiment with multimedia packages hosted in packman, > please activate my account. Login is 'dsterba' Happy packaging, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] x86_64 worker is down
Hi Hans-Peter, thank you for the notification! On Tue, 2022-11-08 at 16:27 +0100, Hans-Peter Jansen wrote: > Hi Stefan, > > FYI, the x86_64 worker is in failed state on PMBS! The schedulers are running again. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Signing up for PMBS
Hi somwang, On Tue, 2022-10-04 at 09:21 +, mnonw742710 wrote: > Hi I'm interested in contributing to the Packman repository. > My username is "somwang" > Can one of the admin activate my account please. > Thank you. I have confirmed your account, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] aarch64 scheduler dead (was: Server Status - i586/x86_64 - dead)
Hi Stefan, On Fri, 2022-09-09 at 07:08 +0200, Stefan Seyfried wrote: > On 05.09.22 05:33, munix9 wrote: > > > > FYI: Server Status - i586/x86_64 - dead > > now the aarch64 scheduler died... running again. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] glibc 2.36 update in Tumbleweed causes makemkv 1.17.1-1.5 to launch with fatal error
Hi Manfred, Am Mittwoch, dem 07.09.2022 um 10:57 +0200 schrieb Manfred Hollstein: : > Until then PMBS should be fixed, though! @Stefan, can you please have > a look at it? Thx! I rebooted PMBS and everything should be fine again. Greetings from holidays, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] yt-dlp 2022.08.08 broken on 15.3
Hi, On Fri, 2022-08-12 at 18:30 +0900, Masaru Nomiya wrote: : > In the Changelog of yt-dlp, it is written as follows; > > ### 2022.08.08 > > * **Remove Python 3.6 support** > > So, I tried to build yt-dlp with python 3.8, the I could get yt-dlp rpm. > That is, the build requirement is python 3.8 or higher. Luigi made the successful submit request sr#994385 in OBS for the change to use python 3.9 for all versions older than Tumbleweed, in fact all distributions since 15.0 (he mentioned that earlier). We at PMBS build several packages linked to OBS sources, where there are some changes needed with respect to limitations, which OBS cannot provide, eg. legal causes or the like, we build the source with the respective modifications. > I can't understand why packman requires python 3.9 or higher. > Moreover, > > 1. I think python 3.9 is the development version > > and, > > 2. The following repo has the stable version of python 3.10 > >https://download.opensuse.org/repositories/devel:/languages:/python/15.3/ > >↑__ I have not checked if all modules are available here. Python 3.9 is available via the official update channel to at least 15.3 and 15.4 as packages python39*. yt-dlp requires now at least python 3.8, so version 3.9 is the closest fit we can manage. Python 3.10 ist not (perhaps yet) available for Leap. We build packages in a way, that there are no outside dependencies for packages installed from packman. The term "outside" includes everything, which is not provided by PMBS itself, or the distribution repository and their respective update repositories. There is no possibility to build packages, which are not in these repositories. Your choice of python 3.10 resides in a different repository, which is not configured in a vanilla openSUSE Leap 15.x installation with added Packman repo. We have to stick with 3.9. > I don't know the merit of upgrading to python 3.10 for the sake of > yt-dlp, but in general, I think there is merit in doing so as more > and more applications are being developed in python. As someone mentioned earlier in this thread, you can have multiple versions of python installed, an this is handled using the alternative mechanism, so apart from a little additional disk space no harm is done, and you can use yt-dlp. > However, this is a troubling problem for regular releases such as > leap, isn't it? Probably :) Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Supplements missing in Packman repositories (createrepo issue)
Hi Gryffus, On Wed, 2022-05-25 at 15:34 +0200, Lukáš Krejza wrote: > I have discovered, that all Packman packages are missing "Supplements:" > dependency. During investigation I found, that the packages themselves > contain > it, but it is missing from primary.xml.gz, which is generated by createrepo i > believe. > > You can check this with: > > curl -L "http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Tumbleweed/ > repodata/primary.xml.gz"|zcat |grep supplements|wc -l > > and compare with for example OSS repository: > > curl -L "http://download.opensuse.org/tumbleweed/repo/oss/repodata/ > e29fac71347fcd31da42b149614449997adc8a3634964098ae8c84406992dd04- > primary.xml.gz"|zcat |grep supplements|wc -l > > There were some reports, that was probably caused by this, for example [1] . > I > believe it causes more unreported issues. > > Is there anything I can do to help resolve this? This is most probably caused by the version of createrepo used at our publishing server. We push all builds from PMBS to said publishing server, where all packages are signed with the packman key, and put in the then published repos for download. It is unlikely, that this will change in the near future due to lack of time. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] New Member activation
Hi Lukáš, On Sun, 2022-05-15 at 12:28 +0200, Lukáš Krejza wrote: > i would like to ask for activation of my account. I have not finished > activation before and i would like to start using it (currently getting "Your > account is disabled. Please contact the administrator for details." message). Yes, your account was disabled, as you tried to create it years back. I could not enable the account through PMBS' web frontend - for reasons unknown, but probably due to the fact, that the account has been set to the disabled state. The other proposed way through the rails console like for changing a forgotten password does not work anymore - but that was never really documented anyway. User management with obs-own tools is still after so many years rather crude, there is no notification and also no user-centric password recovery mechanism :( I have now manually edited the backend database entry for your account and set the account to 'confirmed'. Please give it a try - it may fail due to the fact, that your home project has not been created yet - I do not know when exactly this project is created. > I am currently aiming to package some drivers for fingerprint readers and the > packages are ready, i just need to get them to Packman :) That sounds good, but isn't OBS a more suitable place for such things? Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Enable openSUSE Leap 15.4 for the Multimedia project?
Hi, On Wed, 2022-03-09 at 16:59 -0400, Giacomo Comes wrote: > On Wed, Mar 09, 2022 at 07:26:50PM +0100, Stefan Seyfried wrote: > > On 09.03.22 11:30, Manfred Hollstein wrote: > > Hi there, > > > On Wed, 02 Mar 2022, 14:42:54 +0100, Manfred Hollstein wrote: > > > Hi there, > > > > > I see Leap 15.4 is already enabled in the Essentials project. Now that > > > Leap 15.4 Beta is out, can it be added and enabled for the Multimedia > > > project, too, please? > > > can the Multimedia maintainers please take a look at this? As Bjørn > > suggested we should disable building for openSUSE Leap 15.2, too, but > > don't remove the built packages! > > I have build-disabled 15.2 and enabled 15.4 the same way 15.3 was in the > > project config. > > Important note: Just because I have the permissions to do that, this does > > not mean that I am especially knowledgeable ;-) So please take a look if > > everything works out as expected. > > None of the mirrors have 15.4 yet. > Is that intended or there is something that has to be done? Yes, and yes :) It is not really intended by means "I do not want that", but publishing to mirrors is an "opt-in" process. I have to prepare several things on our publishing server and then enable staging on PMBS for the respective repos. This is a liitle bit time-consuming, and I did not have time to do this. I hope that I will find the time next weekend. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Publishing non-functional again?
Hi Manfred, Am Donnerstag, den 03.03.2022, 20:25 +0100 schrieb Manfred Hollstein: > On Thu, 03 Mar 2022, 19:57:20 +0100, Stefan Botter wrote: : > > Until half an hour ago there have been no builds on Tumbleweed since > > Feb > > 27th, and there was no problem with the schedulers on PMBS. > > which is not true! If you look at > > < > https://pmbs.links2linux.org/packages/MakeMKV/job_history/Multimedia/openSUSE_Tumbleweed/x86_64 > > > > you can see that new packages have been built on February 28, 2022 > 08:29 and they haven't arrived at the PMBS repo at > > < > http://pmbs.links2linux.de:8080/Multimedia/openSUSE_Tumbleweed/x86_64/ > > > > > I believe this is correct, and you were also right - PMBS repos are > > filled immediately, and no "expensive" publishing steps are > > necessary. > > Still they don't show up there :( > > > In some hours there may be new packages in the published repos on > > PMBS and a little while later on the mirrors. > > Again, I'm not talking about the mirrors ;) Yes, you are right, and I just have had a look at the uploading workflow. PMBS did everything right, apart from the obspublisher service, which did not acknogledge finishing of builds in Multimedia's openSUSE_Tumbleweed repo. I do not know why, as all status files looked ok. I guess, that the stalled/delayed publish_hook we use for uploading published PMBS-repos to packman.links2linux.de (due to the initial problem fixed by Marc on Wednesday) blocked the obspublisher service for the specific repo. I cannot reproduce this behavior, but as there are several design shortcomings in the obs services regarding locking, logging and manageability, I will put that to the "sh*t happens" stack. Thank you for your patience so far, I have restarted the obspublisher service around 9:25 a.m. CEST today and it immediately published the repo and uploaded it for distribution to the mirrors. I hope everything is back in good working order, greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Publishing non-functional again?
Hi Manfred, Am Donnerstag, den 03.03.2022, 13:28 +0100 schrieb Manfred Hollstein: > On Wed, 02 Mar 2022, 11:28:29 +0100, Manfred Hollstein wrote: > > <http://pmbs.links2linux.de:8080/Multimedia/openSUSE_Tumbleweed/> > > This repo still has no newer packages, so I still guess there is an > issue with it! > > > isn't it? If this is local to PMBS, it should show newer packages, > > but it doesn't. > > > > > Greetings, > > > > > > Stefan > > No longer confused... Until half an hour ago there have been no builds on Tumbleweed since Feb 27th, and there was no problem with the schedulers on PMBS. I believe this is correct, and you were also right - PMBS repos are filled immediately, and no "expensive" publishing steps are necessary. In some hours there may be new packages in the published repos on PMBS and a little while later on the mirrors. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Publishing non-functional again?
On Wed, 2022-03-02 at 10:38 +0100, Manfred Hollstein wrote: > On Wed, 02 Mar 2022, 10:25:05 +0100, Marc Schiffbauer wrote: > > * Stefan Botter schrieb am 28.02.22 um 21:13 Uhr: > > > It looks indeed like a internal problem in our custom publishing step > > > between PMBS and our repo server. I have asked Marc to have a look. > > > > Should be fixd! > > Essentials indeed appears to be fixed, but Multimedia is still in the > same situation! Give it a little time ;) PMBS has dropped all built packages to the repo server, and now all packages are resigned with the packman GPG Key on that machine. This takes time, and once this step is done the packages will be distributed to the mirrors, which in turn is scheduled hourly or 4-hourly (individual mirror preference). If the mirror upload exceeds a certain amount of data it is split over multiple sync windows. My guess would be, that everything is back in expected order during evening hours GMT today. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Publishing non-functional again?
Hi Manfred, thank you for notifying. On Mon, 2022-02-28 at 17:41 +0100, Manfred Hollstein wrote: > the last packages published to the Essentials and Multimedia repos are > from Feb 27 early in the night. I know that I have built new packages > for MakeMKV today and according to PMBS they are there: > > $ osc -A pmbs ls Multimedia/MakeMKV --binaries > openSUSE_Tumbleweed/x86_64 : > Still, in the Multimedia repo > > <http://pmbs.links2linux.de:8080/Multimedia/openSUSE_Tumbleweed/x86_64/> > > there's only the older version: makemkv-1.16.5-1.10.x86_64.rpm > > Wrt/ Essentials, I'm not exactly sure if there's a publishing issue, > too, but I doubt that there's no newer package than > vlc-beta-debugsource-20220225.38d5ee479d-4.2.x86_64.rpm dated 2022-02-27 > 00:11! > > @Stefan, do you think there might be a publishing issue in PMBS? It looks indeed like a internal problem in our custom publishing step between PMBS and our repo server. I have asked Marc to have a look. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] pipewire-lang package is uninstallable due to version mismatch
Hi Stefan and all other interested ;) I am sorry for not replying to your offer - I simply skipped over your mail. Am Samstag, den 12.02.2022, 10:58 +0100 schrieb Stefan Seyfried: > Hi Stefan, : > I have some spare raspi-style hardware lying around unused, which I > could set up as obsworkers: > * bananapi m2 zero (IIRC, a raspi-zero lookalike with h3 chip) > * raspberry pi (the original) x 2 > * raspberry pi 2 > * raspberry pi 3 (this one should at least be aarch64 capable) > > I would also be willing to buy a raspi 400 (which is the only raspi-4 > like machine available right now) and even send one to you if it > improves the state of workers. > > Not that I am using openSUSE and thus packman on any ARM machine, but > keeping PMBS running seems important to me :-) > > > Unless we nuke arm*/aarch* I cannot do anything about that. > > Anyone with more insight may shed more light in here, Olaf, > > Guillaume? > > If you want me to setup some of the spare raspi boxes as workers, > contact me with instructions, if you want a raspberry pi 400 heading > your way, contact me with a delivery address ;-) If you are willing to host a worker please contact me via PM with a PGP/GnuPG signed mail. I will then send you VPN details for setting up a tunnel to PMBS for the worker(s). Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS is back up again
Hi packmans, PMBS is back up again. Performance will be reduced for a little while as I move bits around a bit. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS downtime postponed to tomorrow, Sunday, Feb 13th
Hi packmans, due to unforeseen schedule issues I am not able to do the migration today. I will try to do it tomorrow. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS will be down today - Saturday, Feb 12th - for some time
Hi all, as mentioned a weekend before last I have to reinstall the hypervisor for my virtual machines, including PMBS, due to storage media issues. I plan on doing this today, and will have to shut down PMBS for that purpose later today. The exact timeframe depends on the availability of a rescue terminal at the hoster, so please expect PMBS to be down any minute now. I will get back to you once everything is back up. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] pipewire-lang package is uninstallable due to version mismatch
Hi Bjørn and S., Am Freitag, den 11.02.2022, 21:52 +0100 schrieb Bjørn Lie: : > I noticed the same thing, see my email to list > > https://lists.links2linux.de/pipermail/packman/2022-January/017024.html > > pipewire-lang is removed, but since the aarch64 builders are down, > the > old full pipewire suite exists for aarch64 and armv7l, and hence also > the noarch lang package produced by it (same with > gstreammer-plugins-ugly-lang and probably more). > > Check https://pmbs.links2linux.org/monitor -> select aarch64, > timeframe > 1 month > and > Essentials aarch64 openSUSE_Tumbleweed have had pending blocked: 14 > scheduled: 33 for aarch for "ages" due to this. > armv7l have unresolvable: 1 blocked: 18 scheduled: 29 - but they are > all waiting for workers that are not there at the moment. > > I assume Stefan will get to it when he has the time / willpower :-) > and us nagging about it will not do any good. > > /Bjørn This is actually not really a thing I do :( Yes, we do not have any armv7l workers anymore, as my banana pi (swrj01) was not building correctly for some time now, and both cubietrucks (swrj02 and swrj03) broke down due to hardware issues during the past two months. Anyhow, these three workers are armv7l only, and Leap 15.3 seems to be the last openSUSE to build with armv7l, Tumbleweed for a while seems to enforce a more recent cpu (64bit), thus none of my late workers was suitable. Unless we nuke arm*/aarch* I cannot do anything about that. Anyone with more insight may shed more light in here, Olaf, Guillaume? Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] New Member!
Hi Jimmy, welcome! Am Freitag, den 04.02.2022, 12:51 -0600 schrieb Jimmy Henderson: > I am xcentrik4, an avid user of SuSE since 9.3 and a flight-simming, > Mincraft- and WoW-playing content creator (Twitch and YouTube). > > I'm making an account so I can post in the requests area - so am > awaiting > an admin to approve the account! > > Anywho, been a long-time user of Packman, and am so thankful for > everything > through the years! Your account is confirmed, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS up again
Hi Packmans, PMBS is up again, with no data loss. Before I started the update of the hypervisor, I suspended all machines, and they started up nicely, once I was able to regain control of the server. I will have to re-install the hypervisor once again and move away from the USB stick. Please expect another downtime next week, but I will properly announce it this time. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS down, was: Re: Problems with gstreamer-plugins-bad and related packages from Packman on TW
Hi Manfred, hi packmans, On 2022-01-29 20:14, Manfred Hollstein wrote: : @Stefan: dunno if you've seen, but PMBS is completely dead! Yes, I know, and not only PMBS but the whole hypervisor with all virtual machines. I updated the underlying machine to fix the security issues, and now it does not boot anymore. I want to reinstall the hypervisor, unfortunately my attempts since 6 p.m. were to no avail, as the virtual console always stalls after about 15 minutes, which is not enough for the upload of the installation medium. I will give it a try again tomorrow morning, in the hope that upload is better then. If everything fails, my last backup state is from today about either 4:11 p.m., so not that much may be lost. EMail communication is a little bit hampered, as my usual mail server is also located there and not available. I will keep you posted, greetings, Stefan ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] account request
Hello Nei, Am Samstag, den 15.01.2022, 14:09 +0100 schrieb Ailin Nemui: > I'm an openSUSE user. > > My account is ailin_nemui, could you enable it? welcome to PMBS! Your account is confirmed, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] subscribe pack...@koma.han.de
Hello Kai, On Mon, 2022-01-10 at 16:19 +0100, Kai Dupke wrote: > Dear Packman-Project, > > I requested an account and would like to introduce myself to the list. > > I am working in the product management area on Linux support, working > with Linux since 1992. > > I did some work on the enablement of the ALPHA platform and on ISDN > (that was Urlichs-ISDN). > > However, mostly I am a user of Linux and tools and work on the business > side of the house. Welcome to PMBS, your account is confirmed, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] digests SIGNATURES NOT OK
Hi Marc, Am Samstag, den 11.12.2021, 22:20 -1000 schrieb Marc Schiffbauer: > we should really create a new gpg key for the repo. > > @Stefan: What do you think? I am all for it! PMBS is not in the way, as you are re-signing all packages on the distribution host. As far as I understand, you have to create a new key, publish that with the Essentials/rpmkey-packman package a few days ahead of changing the signing step to the new key. Of course Stefan and Carlos have more insight in the key handling. Lets talk PM about any changes needed. As for the mirror issues, we should have a mirrorbrain somewhere to ease the problems with inconsistent, outdated or disappearing mirrors. Unfortunately my hosting machine is at capacity with both RAM and disk, so I cannot set up such a site. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] jacobs university mirror
Hi Patrick, Am Samstag, den 11.12.2021, 16:47 -0800 schrieb Patrick Finie: > Is the Jacobs university mirror going to be back up? it was one of > the best mirrors for my location and the only packman mirror i could > use when at opensuse events at USC, UCLA or going to my local > colleges. > > Any update would be appreciated. I was promised a return of this machine. There are certain formalities to go through - create secure access for me and recovery of data, and I am still waiting for to go ahead. I will try asking again. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] packman.jacobs-university
Hallo Hubert, On Mon, 2021-11-15 at 09:44 +0100, Hubert wrote: > http://packman.jacobs-university.de/ ist seit einigen Tagen nicht mehr > erreichbar Ja, das ist bekannt, ich stehe gerade mit denen in Kontakt. Liebe Grüße, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account activation
Hi Giacomo, Am Samstag, den 13.11.2021, 14:57 -0400 schrieb Giacomo Comes: > my name is Giacomo. I have created a new account (gcomes.pmbs) and I > ask for its activation. > My first task is to fix the longstanding memory issue of aMule. Your account is confirmed, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] packman.jacobs-university.de down
Hallo Christian, Am Freitag, den 12.11.2021, 14:14 +0100 schrieb Christian: > seit gestern abend ist der Packman-Server der Jacobs-University Bremen > down. > Wollte ich nur allgemein mitteilen für die, die es noch nicht > mitbekommen haben. :-) > > Vielleicht weiß ja auch jemand, was bei denen gerade technisch los ist > - ich wechsel jedenfalls mal zur FAU nach Erlangen... :-) Ja, sieht so aus. Seit ca 15:30 Uhr am Donnerstag ist der nicht mehr zu erreichen. Ich habe da mal nachgefragt. In jedem Fall sain FAU oder GWDG gute Alternativen. LG Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] pipewire-media-session 0.3.39 missing
Hi Luis, On Sun, 2021-10-31 at 04:03 +, Luis Ortega Pinillos wrote: > As the subject says, that package is missing! Zypper asks to change to > openSUSE's own pipewire-media-session but i don't think that's ok... > Thanks, have a great day According to the changelog of package pipewire there is a new separate package pipewire-media-session (to speeding up fading out that module in favor of WirePlumber). It is probably ok to switch to the package from openSUSE.org - the new package is not on PMBS, and most probably does not have to be compile separately. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] vivaldi 2.1.1337.51-lp151.1.2 (openSUSE_Leap 15.1/x86_64)
Hi all, On Wed, 2021-10-27 at 08:03 +0200, Stefan Seyfried wrote: > Unfortunately the schedulers are down right now (I already notified > Stefan), so this will take some time to propagate. They are running again. Consistent monitoring of them ist still on my to-do list :) Greetings, Stefan -- Stefan Botter zu HauseBremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] FYI: i586 dead, x86_64 TW lot of "failed build attempts"
Hi Stefan, Am Samstag, den 25.09.2021, 11:49 +0200 schrieb Stefan Seyfried: : > OK, I retried on a 15.3 machine and it fails the same way as on PMBS. PMBS and all workers are still 15.2, and I use the Stable branch from OBS 2.10 as installation source. > The fun thing is: the rootfs can be mounted but for some reason it is > not deemed "usable_root" by dracut > > debugged this and found, that "/sys" is missing. > > And alas, the update of the "build" package from > > * Fri Aug 20 2021 Adrian Schröter > Features: > ... > - Also create the /sys dir when preinstalling (to satisfy dracut) > > The commit in github is much older: > > commit 207a4729849c055f12ff8592e927a3e3db236097 > Author: Michael Schroeder > Date: Wed Feb 24 11:31:48 2021 +0100 > > Also create the /sys dir when preinstalling > > The background for this change is that dracut has a usable_root() > function that checks the existance of /proc, /sys, and /dev. > > diff --git a/init_buildsystem b/init_buildsystem > index 80dcdb7..b5106d2 100755 > --- a/init_buildsystem > +++ b/init_buildsystem > @@ -569,6 +569,7 @@ fi > mkdir -p "$BUILD_ROOT" || cleanup_and_exit 4 > mkdir -p "$BUILD_ROOT/.build" || cleanup_and_exit 4 > mkdir -p "$BUILD_ROOT/proc" || cleanup_and_exit 4 > +mkdir -p "$BUILD_ROOT/sys" || cleanup_and_exit 4 > mkdir -p "$BUILD_ROOT/dev/pts" || cleanup_and_exit 4 > touch $BUILD_IS_RUNNING > > > I did simply add the "mkdir -p $BUILD_ROOT/sys" to > /usr/lib/build/init_buildsystem on my 15.3 system and now everything > works locally. > Doing the same on your OBS server machine should do the trick as well > (the workers fetch the build code from the OBS server IIRC). Thank you very much! This did the trick, also on 15.2/2.10. Tumbleweed builds are working again, I will start the 2 old workers too. > Or just update to the latest version of the build package :-) Nice suggestion, but where do I get the up-to-date-version of build? Definitively not from the https://download.opensuse.org/repositories/OBS:/Server:/2.10 branch. Thanks again, and have a nice remaining weekend, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Hello Everyone!
Hi Simon, welcome! Am Samstag, den 25.09.2021, 20:34 +0200 schrieb Simon Vogl: > First things first, my name is Simon Vogl, and I recently joined the > packman mailing lists & signed up for the packman build service with > the user name "DarkWav". I have confirmed your account, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] FYI: i586 dead, x86_64 TW lot of "failed build attempts"
Hi munix9,
Am Donnerstag, den 23.09.2021, 21:07 +0200 schrieb munix9:
> for "i586 dead" see
> https://pmbs.links2linux.de/monitor
This I could fix.
> for "x86_64 TW lot of failed build attempts" see eg.
> https://pmbs.links2linux.de/package/live_build_log/Multimedia/aften/openSUSE_Tumbleweed/x86_64
Here I am lost. Suddenly all build attempts on all workers fail with
"unable to mount root fs". I am not sure, if this is limited to
tumbleweed, It has definitively nothing to do with the OS version or
other setup of the build hosts ("I did not do anything, I swear!" ;).
I will look into this as time permits.
Greetings,
Stefan
--
Stefan Botter zu Hause
Bremen
signature.asc
Description: This is a digitally signed message part
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Hi
Hi Dominik, Am Freitag, den 24.09.2021, 13:28 +0200 schrieb Dominik Heidler: > I'm Dominik, one of the maintainers of the opi tool that installs > packages from OBS and Packman on openSUSE. > I created an account with the username "dheidler" at PMBS (I need a > user account to use the search routine in opi > to search for packman packages). Thank you for your introduction, I have confirmed your account. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Server Status i586 dead
HI munix9, Am Mittwoch, den 02.06.2021, 10:26 +0200 schrieb munix9: > Server Status i586 dead > > https://pmbs.links2linux.de/monitor > > thx Thank you for notifying me, the schedulers are running again. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account activation
Hi Gregor, Am Donnerstag, den 13.05.2021, 12:46 +0200 schrieb Gregor: > I'm Gregor and would like to package ImageMagick with heic-support for > my Leap 15.2 installation. For this I created a new account (@chkpnt) > and ask for its activation. Your account is now confirmed, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Account approval request
Hi İsmail, Am Sonntag, den 09.05.2021, 10:21 +0200 schrieb İsmail Dönmez: > Hi all, > > Some of you might know me already, but here is a quick introduction. I > am İsmail Dönmez, until recently worked for SUSE. I used to have a > Packman account but had to get it removed due to some conflicts that > were out of my reach. Now those conflicts do no longer apply, I'd like > to get my account approved. > > I'd like to first add AAC support to pipewire (sent an SR on OBS > already) and package libopenaptx for better Bluetooth support. Your account is confirmed, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Introduction
Hi Nicolas, Am Samstag, den 17.04.2021, 15:22 + schrieb Nicolas Formichella: > Hello, > > I'm Nicolas, French Python developer and Linux aficionado for years > > And especially OpenSUSE since ~1y. I created an account on PMBS > (stig124) to try to fix a bug in OBS Studio packaging (missing > dependencies that breaks webcam support) I have confirmed your account, happy packaging! Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Server Status i586 & x86_64 dead
Hi munix9, Am Freitag, den 16.04.2021, 13:02 +0200 schrieb munix9: > The annoying human monitor reports again :-\ > > Server Status i586 & x86_64 dead > > https://pmbs.links2linux.de/monitor > > thx I have rebooted the server and extended the swap partition. The schedulers died due to an OOM-condition. I am not really sure, where that comes from, as the processes run smooth for an extended period of time, and suddenly request RAM like mad. Probably a bug in the scheduler software. Unfortunately there is no (at least not known to me) possibility to monitor the processes from checkmk, where I could build automation for restarting the missing processes. Also, as all scheduler processes for all architectures are started with one systemd service, systemd is not able to watch the processes and possibly restart them. At least at the moment I am not able to read mails during the day and have to postpone any maintenance to the weekends. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] x86_64 and i586 done and already on several mirros, was Re: PMBS: Multimedia repo publishing
Hi Packmans, Multimedia is back! aarch64 and armv7l are still building, but x86_64 and i586 are ready and published and have reached the first mirrors minutes ago. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] PMBS: Multimedia repo publishing
Am Sonntag, den 21.03.2021, 17:15 + schrieb pack...@howorth.org.uk: > Would it be sensible/feasible/desirable to add a fake > 'destination-packman' dependency to all multimedia packages that are > to be published on packman? Then in any similar circumstances a > rebuild of all packman packages could be triggered by > touching/updating the dependency. Or is a complete rebuild of > Multimedia the sensible long-term solution? I do not think it feasible, as you would have put a dependency in each and every package in Multimedia, old and new. Anyway, the solution is really simple: https://lists.opensuse.org/archives/list/buildserv...@lists.opensuse.org/thread/OGBVX3C2DEVHV2OGE5YUNMR6Z3QUAMCV/ (Coolo's answer to my request) Change the project config temporarily, and trigger rebuild for all packages. Change the project config back once all packages are done and published. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] PMBS: Multimedia repo publishing
Hi again, Am Sonntag, den 21.03.2021, 10:31 +0100 schrieb Stefan Botter: > I do not know how to force a unconditional rebuild of a while project, Coolo was really really fast with help, and I have triggered the rebuild of the whole Multimedia project. This will take a while, and hopefully afterwards all packages are available again on the mirrors. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] PMBS: Multimedia repo publishing
Hello everyone, Am Samstag, den 20.03.2021, 13:46 +0100 schrieb Stefan Botter: : > Building has started again about half an hour ago. > If the key-juggling was successful, we will see once a whole > repository of the Multimedia project has finished building and staging > to packman.links2linux.de is finished. I will have a look at the log > files there later today. ... well - "tomorrow" would have been correct :) The good news: it is working! The bad news: All packages in project Multimedia built between Feb 24th and Mar 20th, and have not been changed to cause a rebuild - either through a commit or an upstream dependency change, are still signed with the temporary key not accepted by packman's re-signer, and are hence not published. Three ways out of that: - wait, - force a complete rebuild of Multimedia, or - re-sign packages in Multimedia with the actual key and re-publish. Waiting is lame. I do not know how to force a unconditional rebuild of a while project, and also do not know if and how it is possible to re-sign already built packages . I reached out to openSUSE's buildservice mailing list, and am waiting for input. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] PMBS: Multimedia repo publishing
Hi again, Am Freitag, den 19.03.2021, 12:44 +0100 schrieb Stefan Botter: : > Multimedia packages built on PMBS could be signed again only after I > replaced the Multimedia project signing key on Feb 24th. > This in turn broke the verification on packman.links2linux.de, so > Multimedia packages arriving there are not re-signed and hence not > published to the mirrors. > As I do not have access to the re-signing part on packman, I cannot > simply update/trust the new project key. Marc is offline ATM, and > cannot help me right now, so I will try to replace Multimedia's key > with another already trusted key in our publishing chain. I did that now after some testing on my private build service instance. > This will likely break something, as I am try-and-erroring. I hope, that the "error" part was limited to my own instance, and building with the more-or-less "new" key for Multimedia solves the situation. Building has started again about half an hour ago. If the key-juggling was successful, we will see once a whole repository of the Multimedia project has finished building and staging to packman.links2linux.de is finished. I will have a look at the log files there later today. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS: Multimedia repo publishing
Hi Packmans, for the past four weeks there has been an publishing problem with the Multimedia project: Packages have been build successfully on PMBS, but never made it to the mirrors. As outlined in a mail on Feb 27th, PMBS' publishing stages build projects to packman.links2linux.de, where all packages are re-signed with the official packman GPG key. Once this is done, the packages are finally published and pushed to the mirrors. Before the packages are re-signed, the process checks the validity of the then existing signatures against a list of known keys - these are then PMBS-project keys, we manually maintain the list of trusted keys on packman. The standard GPG key for PMBS expired last July unnoticed. This did not cause the current problem for Multimedia, but apart from the nuisance of no further account creation, it exposed the circumstance, that the Multimedia key was an old key, created before the standard PMBS key (which is used by the signer to access the project keys). (I really **really** do not understand, how PMBS was able to sign packages with the old key since May 2014!) Multimedia packages built on PMBS could be signed again only after I replaced the Multimedia project signing key on Feb 24th. This in turn broke the verification on packman.links2linux.de, so Multimedia packages arriving there are not re-signed and hence not published to the mirrors. As I do not have access to the re-signing part on packman, I cannot simply update/trust the new project key. Marc is offline ATM, and cannot help me right now, so I will try to replace Multimedia's key with another already trusted key in our publishing chain. This will likely break something, as I am try-and-erroring. For that I have stopped the schedulers for all architectures apart aarch64. Once all packages there have been built, I will stop the dispatcher, make a snapshot of the VM, replace the Multimedia key and start everything up again. I am looking forward to resolve the publishing issue with this. I will send another mail, when I implemented the change. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Missing packages for openSUSE Tumbleweed
Hi Alessandro, Am Samstag, den 06.03.2021, 11:57 +0100 schrieb Alessandro: > I want to point out that for about a week, the following packages, > which > I had previously installed from the Packman repository, have been no > longer available: [long list removed] > I have tried to change several mirrors, but always without success. Yes, the problem is known, and probably connected with the signing/publication issue. After the move of PMBS last weekend I was busy with all the handover stuff from my old job until Yesterday. Unfortunately also Yesterday an issue in my private live occurred, which will occupy me for the next few days. Marc told me, that the re-signing on packman should not be a problem. Without checking the upload logs, and comparing the missing packages on the mirrors with the recently built packages, it is entirely possible, that a changed build result of the respective packages will lead to a new successful publishing to packman and subsequently to the mirrors. I will have a look at this, but ATM I simply do not have the time. I am looking forward to have more time around Wednesday or Thursday. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS backup again!
Hi Packmans, PMBS is back up and packages are building! Greetings, Stefan -- Stefan Botter zu HauseBremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] PMBS downtime - it takes longer
Hi Packmans, On Sun, 2021-02-28 at 09:20 +0100, Stefan Botter wrote: > I now expect PMBS to be transferred during the early morning hours of > monday, an will then probably being able to start it up again Monday > before noon. The good news: PMBS's virtual machine is transferred successfully. The bad news: My backup vm is still in transit, and will so for another 5-6 hours. I would really like to wait until it is transferred, and afterwards change my internal network configuration to match the one I am currently using, which in turn will ease all other config tasks like backup and monitoring. There is a chance, that PMBS will be back this evening. Greetings, Stefan -- Stefan Botter zu HauseBremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman repo para openSUSE Leap 15.2 "403 Forbidden"
On Sun, 2021-02-28 at 13:12 +0100, Carlos E. R. wrote: > On 27/02/2021 18.56, Sergio wrote: > > Hola, > > > > Escribo para informar que el repositorio > > http://packman.inode.at/suse/openSUSE_Leap_15.2/repodata/repomd.xml > > muestra, al menos desde hoy 27-feb-2021 "HTTP 403 Forbidden". > > Es sabido y anunciado. > > > < > https://lists.links2linux.de/pipermail/packman/2021-February/016587.html > > I am pretty sure, that inode.at's access problems are unrelated to the downtime of PMBS. The correct solution would be to use a different mirror from the mirror list: http://packman.links2linux.de/mirrors Greetings, Stefan -- Stefan Botter zu HauseBremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS downtime - it takes longer
Hi Packmans, transfer of PMBS takes longer than expected, 15 hours in I see only 45% moved. Unfortunately the bandwidth used is reduced to about 200MBit/s, from something around 500MBit/s Yesterday in the afternoon. I am running 3 moves in parallel, in order to clean up the old VM's home until Monday, I cannot really speed things up. I now expect PMBS to be transferred during the early morning hours of monday, an will then probably being able to start it up again Monday before noon. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package availability, was: Re: signing seems to hang somewhere
Hi Marc, Am Sonntag, den 28.02.2021, 00:12 -0500 schrieb Marc Schiffbauer: > * Stefan Botter schrieb am 27.02.21 um 02:11 Uhr: > > There are two possible ways to fix this: > > 1. allow the actual Multimedia repo key to be accepted on > > packman.links2linux.de > > 2. reinstate the old Multimedia repo key on PMBS. > > > > The first option needs an action on packman.links2linux.de -> I have > > to > > ask Marc to do the change (he is busy ATM, and this may take a > > while). > > Within the next days I can add a new key ID to be accepted for > re-signing. That is fantastic! -> PM Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS will go down in a few minutes - back probably tomorrow around noon
Hi Packmans, as announced earlier, PMBS will be down for the move. I have to do a cold migration, as I am changing architectures (Intel to AMD), and previous moves suggest a transfer time of about 8-10 hours. As I will probably sleeping when the machine is transferred, I will start it back tomorrow. I will move my mail setup also, and will thus not be able to write a mail about it at that time, but will get back to you as soon I am able to write mails again. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package availability, was: Re: signing seems to hang somewhere
Hi Dave, Am Samstag, den 27.02.2021, 11:47 +0200 schrieb Dave Plater: : > Something must have been fixed, avidemux3 is now available in the > normal repository No, unfortunately it is not that easy. avidemus3 ist still on PMBS, and available in the Leap 15.2 repo, but not the fresh built package for Tumbleweed. This is connected with the signature/sign issue, and I will get to it probably tomorrow or on Monday. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS downtime ahead - this weekend, and > 12 hours
Hi Packmans, as announced earlier, I will have to move all my virtual machines including PMBS to a new server. Hetzer finally handed the new machine over to me, and I have to make the move this weekend, as I have to remove my own hardware from my current employer next week (until Friday - but I would prefer to move the ~ 100kg of equipment on Monday or Tuesday). I am preparing the new server for the move, and will start probably later today. For PMBS this means a downtime of at least 12 hours, probably more. I will send a separate announcement some minutes before the move. Also, as I will move my own mail server, I will not be reading mails during that time. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Package availability, was: Re: signing seems to hang somewhere
Hi all, as I have feared, there are problems with publishing of packages. Am Mittwoch, den 24.02.2021, 16:25 +0100 schrieb Stefan Botter: : > Yes, I can confirm this problem. It is connected with the expired GPG > key - and probably with something I fscked meanwhile. > > I have been trying for a while now, and could be the Multimedia > project > to sign. There might be a problem with > - other projects/repositories, and > - publishing to the packman server Exactly that happened. This is caused by the unique way we publish built packages to the repositories, which are synced to the mirrors: PMBS builds packages (the regular OBS way) and signs them with the respective repository key. Once all packages for a repo are built, the repo gets published - and here we sync them to packman.links2linux.de. There is a publishing mechanism, which re-signs the packages with the official packman key, puts entries in the database backing the website and creates the repositories for the mirrors. For security reasons the re-signing step checks the signatures, with which the packages arrive. There is a positive-list, and only signatures on that list are considered "okay" for re-signing and publishing. As I wrote last Wednesday, the ultimate problem was the expired PMBS key, which in turn sings the publishing keys for PMBS's repos, and I had to recreate the key for the Multimedia repo. This key has changed, and re-signing at packman.links2linux.de fails, and the packages are not published to the mirrors. There are two possible ways to fix this: 1. allow the actual Multimedia repo key to be accepted on packman.links2linux.de 2. reinstate the old Multimedia repo key on PMBS. The first option needs an action on packman.links2linux.de -> I have to ask Marc to do the change (he is busy ATM, and this may take a while). The second option may work, as I have backups, and the Open Build Service keeps such information. I have read somewhere, that manually forcing a pre-existing key in a build service instance, but do not know - how to do that (probably something with obs_admin), and - if this will succeed. Anyway, the packages will resurface, but it may take time. I will announce a downtime for PMBS in my next mail, and can face the repo-key issue after I have moved PMBS to its new home at the hosted server. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] signing seems to hang somewhere
Hi munix9, Am Mittwoch, den 24.02.2021, 05:31 +0100 schrieb munix9: > signing seems to hang somewhere > > eg. > https://pmbs.links2linux.de/project/monitor/Multimedia?utf8=%E2%9C%93=0=1_aarch64=1_armv7l=1_i586=1_x86_64=1_openSUSE_Leap_15_2=1_openSUSE_Leap_15_3=1_openSUSE_Tumbleweed=1 Yes, I can confirm this problem. It is connected with the expired GPG key - and probably with something I fscked meanwhile. I have been trying for a while now, and could be the Multimedia project to sign. There might be a problem with - other projects/repositories, and - publishing to the packman server I will have an eye on that later, I have to have a break now. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] PMBS migration to cloud host probably delayed
Hi Packmans, I had the hope to being able to move PMBS along with my other virtual machines to its new home at Hetzner this weekend. Unfortunately my order from last week with a prospected delivery time of 3-5 working days seems to be delayed (current orders have an estimation of 13-15 days). As explained in one of my last mails, I will try to move things over a weekend to not put any burden on my university's internet connection to impair teaching. As of right now, I do not expect the move to happen this weekend, it would then hopefully take place during the next weekend. Anyway, I will announce the downtime, perhaps with very little lead time. Greetings, Stefan -- Stefan Botter zu Hause Bremen signature.asc Description: This is a digitally signed message part ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
