openSUSE Build Service May 2023

buildservice@lists.opensuse.org

24 participants
16 discussions

Spam on the public buildservice instance
by Florian "sp1rit" 23 May '23

23 May '23

Hello, I've noticed that the user scottlawler[0] on the public instance has added a comment under one of my packages[1] promoting some sort of shitty mobile games website. Since there isn't any way of seeing all comments a user has made, I'm unable to see if this was a one-off or if the account has promoted his "serviced" under other packages too. Since there isn't any other way to report spam and other malicious behavior, I'm posting about it here. Regards, Florian "sp1rit" [0]:https://build.opensuse.org/users/scottlawler [1]:https://build.opensuse.org/package/show/X11:Wayland/hyprland?notificatio… -- $\int_\text{now}^{+\infty}\text{Keep trying}$ Matrix: @sp1rit:tchncs.de <sp1rit(a)disroot.org> D248BF2F4C6A82A1E0569D897D8C1CD573166D09 <sp1rit(a)national.shitposting.agency> BBDE032EAAFBFC627FB7E635B1F4055D8460CE34

4 3

Safely convert an existing package into a Link / branched package?
by Johannes Kastl 23 May '23

23 May '23

Hi all, I think we had this topic before (2019, AFAICS), so maybe there is an update on this: How can I safely convert an existing package into a link / branch package? Without losing any changes on the "to be converted" package? Back then the only options were "osc branch -f" or manually creating the _link file. Is this still valid? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 1

The result obtained by osc results project package is "succeed*"?
by liuxueping.snow＠bytedance.com 22 May '23

22 May '23

The result of executing osc results project package is not the expected "succeed" but "succeed*",why is there an extra * in the succeed?

2 1

How/where to ask for a GPG key renewal on a home project
by Nicolas Formichella 18 May '23

18 May '23

Greetings, I have my home project[1], home project which has a GPG key that is near expiration (exp date: 2023-06-15) Will the renewal of the key be an automatic process where I don't have to do anything? If I need to do something, do I need to email the admin list for that? Regards, Nicolas FORMICHELLA [1]: https://build.opensuse.org/project/keys_and_certificates/home:stig124

3 2

Submitting new package to devel project and dependency question
by Michael Pujos 16 May '23

16 May '23

Hi, I want to submit package A from my home project to devel project P. package A depends on package B that is only found in devel project Q. In my home project, B was simply a link to Q, allowing A to build. How does it work when submitting A to P, for A to find B when built in P ?

2 2

Show a diff for a whole project (aka all packages in that project) or only packages with a diff?
by Johannes Kastl 11 May '23

11 May '23

Hi all, can I find out which linked/branches packages in a project have differences to their origin/parent package? I know I can loop over all packages, enter the package folder, do a diff, go back, next package. But I was wondering if there is something only showing packages that have changes. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 2

"osc service disabledrun" creates both obscpio and tar.gz sometimes?
by Johannes Kastl 11 May '23

11 May '23

Good <insert time of day here> everyone, I noticed today that running "osc service disabledrun" sometimes creates both obscpio and tar.gz files. Today it happened with helm 3.12.0 using this _service file: > <services> > <service name="obs_scm" mode="disabled"> > <param name="url">https://github.com/helm/helm.git</param> > <param name="scm">git</param> > <param name="exclude">.git</param> > <param name="versionformat">@PARENT_TAG@</param> > <param name="versionrewrite-pattern">v(.*)</param> > <param name="revision">v3.12.0</param> > <param name="changesgenerate">enable</param> > </service> > <service name="tar" mode="buildtime"/> > <service name="recompress" mode="buildtime"> > <param name="file">helm-*.tar</param> > <param name="compression">gz</param> > </service> > <service name="set_version" mode="disabled"> > </service> > <service name="go_modules" mode="disabled"/> > </services> The file looks similar to dozens of others that I touched in the last couple of weeks, where this did not happen? What do I miss? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

1 0

DisplayCAL RPM package for OpenSuSE 15.5
by Jacek Rużyczka 09 May '23

09 May '23

Good evening. Unfortunately, the DisplayCAL frontend for ArgyllCMS has been kicked out of OpenSuSE because it had stuck with Python 2. Now there is a Python 3 version of this software available at GitHub https://github.com/eoyilmaz/displaycal-py3. Its maintainer has also created a spec file for the RPM https://github.com/eoyilmaz/displaycal-py3/issues/235. Some details of the spec file will have to be edited, though (the target directory, for instance). Now somebody will have to build a ready-to-use RPM package of DisplayCAL. I can't do that myself as I "only" have OpenSuSE 15.4 with its age-old Python 3.6, the current OpenSuSE 15.5 beta still contains 3.6, and DisplayCAL requires at least 3.10. So: What can we do to get the RPM done? For myself, I have zero experience in building RPMs. Thank you. Kind regards Jacek Rużyczka

1 0

How do I add the Tumbleweed repository to the ISO, so that it exists when starting the Live ISO?
by Ruach 08 May '23

08 May '23

ISO: https://build.opensuse.org/package/show/home:hopeandtruth6517:nova-flow-os/…

1 0

Key missing for openSUSE:Leap:15.5:Update?
by Johannes Kastl 08 May '23

08 May '23

Good morning, when building for 15.5 locally I get the following warning: > Verifying integrity of cached packages > using keys from SUSE:SLE-15-SP3:Update, SUSE:SLE-15:GA, SUSE:SLE-15-SP4:GA, SUSE:SLE-15:Update, SUSE:SLE-15-SP4:Update, SUSE:SLE-15-SP3:GA, SUSE:SLE-15-SP5:GA, SUSE:SLE-15-SP2:GA, SUSE:SLE-15-SP1:Update, SUSE:SLE-15-SP2:Update, SUSE:SLE-15-SP1:GA, SUSE:SLE-15-SP5:Update, devel:languages:python, home:ojkastl_buildservice, openSUSE:Leap:15.5 > warning: /home/Buildservice/22_packagecache/openSUSE:Leap:15.5:Update/standard/x86_64/rpmlint-mini-1.10-lp155.4.2.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY > /home/Buildservice/22_packagecache//openSUSE:Leap:15.5:Update/standard/x86_64/rpmlint-mini-1.10-lp155.4.2.1.x86_64.rpm : public key not available I looked into the old thread for missing keys with SLES12, back then this needed to be adapted on the build service side. Not sure if this is the same error, but if it is, could someone fix this, please? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service May 2023