August 2020 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] How to point to the right package in case of multibuild from the meta in OBS
by Dominig ar Foll (Intel Open Source) 25 Aug '20

25 Aug '20

I try to build a package which requires the GTK3 no-stl version of wx-widgets. wx-widgets 3.2 is now built with the multibuild model and so present multiple repos. <multibuild> <package>GTK2</package> <package>GTK3</package> <package>GTK3-nostl</package> <package>Qt</package> </multibuild> The compilation in OBS succeed as the -devel package is the same for all flavour, but the link fails because OBS select the GTK2 release by default. I have tried to guess multiple syntaxes but have miserably failed. My question. How can I force the selection of the right package set in OBS from a project which is built with multibuild service? <repository name="openSUSE_Leap_15.1"> <path project="X11:wxWidgets:GTK3" repository="openSUSE_Leap_15.1"/> <path project="openSUSE:Leap:15.1" repository="standard"/> <arch>x86_64</arch> </repository> Thanks in advance for the help. -- Dominig ar Foll Senior Software Architect -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] osc stacktrace after installing latest updates
by Carsten Höger 17 Aug '20

17 Aug '20

Hi, after I installed the latest updates on our buildservice, the local osc command starts every output with buildservice:~ # osc meta prj backend-develop Error initializing plugin Google = keyrings.alt.Google. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/keyring/backend.py", line 171, in _load_plugins init_func = ep.load() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2343, in load return self.resolve() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2349, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib/python3.6/site-packages/keyrings/alt/Google.py", line 14, in <module> import gdata.docs.service File "/usr/lib/python3.6/site-packages/gdata/__init__.py", line 27, in <module> import atom File "/usr/lib/python3.6/site-packages/atom/__init__.py", line 133, in <module> CreateClassFromXMLString) File "/usr/lib/python3.6/site-packages/atom/__init__.py", line 97, in mark_deprecated optional_warn_function.func_name = f.func_name AttributeError: 'function' object has no attribute 'func_name' ... osc-0.170.0-lp151.307.1.noarch any idea on how to get rid of that output? -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger(a)open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Andreas Gauger, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] OBS builds for Leap 15.2 has wrong sle_version
by Christian 15 Aug '20

15 Aug '20

Hi, building here: https://build.opensuse.org/project/monitor/home:computersalat:certbot having the following in prjconf: %if 0%{?is_opensuse} && 0%{?sle_version} >= 150000 %if 0%{?is_opensuse} && 0%{?sle_version} == 150000 Release: lp150.<CI_CNT>.<B_CNT>.CS %endif %if 0%{?is_opensuse} && 0%{?sle_version} == 150100 Release: lp151.<CI_CNT>.<B_CNT>.CS %endif %if 0%{?is_opensuse} && 0%{?sle_version} == 150200 Release: lp152.<CI_CNT>.<B_CNT>.CS %endif %else Release: <CI_CNT>.<B_CNT>.CS %endif info taken from here: https://en.opensuse.org/openSUSE:Packaging_for_Leap Build results: builds for Leap 15.1: https://build.opensuse.org/package/live_build_log/home:computersalat:certbo… [ 81s] build: extracting built packages... [ 81s] RPMS/noarch/python3-acme-1.6.0-lp151.1.2.CS.noarch.rpm [ 81s] RPMS/noarch/python2-acme-1.6.0-lp151.1.2.CS.noarch.rpm [ 81s] SRPMS/python-acme-1.6.0-lp151.1.2.CS.src.rpm builds for Leap 15.2: https://build.opensuse.org/package/live_build_log/home:computersalat:certbo… [ 81s] build: extracting built packages... [ 81s] RPMS/noarch/python3-acme-1.6.0-lp151.1.2.CS.noarch.rpm [ 81s] RPMS/noarch/python2-acme-1.6.0-lp151.1.2.CS.noarch.rpm [ 81s] SRPMS/python-acme-1.6.0-lp151.1.2.CS.src.rpm for Leap 15.2 it should be 'lp152' Why is it not correctly set ? How to fix ? -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

3 2

[opensuse-buildservice] Scheduler not pulling recommended packages
by sergio 12 Aug '20

12 Aug '20

Hi, I am trying to find a way to cover unexpected dependencies indirectly pulled by a package, ie. emacs or vim pulling x11* (see https://progres s.opensuse.org/issues/16122) I had the idea of abusing OBS with a fake package that will install the package in the worker VM and check for pulled packages. But, it seems that because of the wanted build environment isolation, the scheduler is expected to pull only the necessary packages so the build can be performed offline (as in not network). The scheduler doesn't pull the recommended packages so zypper will not behave as in a real scenario inside the worker VM. Is that right? So, would it be possible to workaround it so that recommended packages are also taken into account? Kind Regards -- Sergio Lindo Mansilla <slindomansilla(a)suse.com> QA Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

2 2

[opensuse-buildservice] New blog post from Build Solutions Team: Yes, we do SRE!
by Saray Cabrera Padrón 04 Aug '20

04 Aug '20

How do you think we keep our reference instance up and running? In our new blog post, you can find an introduction to how we do operations and Site Reliability Engineering (SRE). Don't miss out. https://openbuildservice.org/2020/07/31/we-do-sre The Build Solutions Team -- Saray A. Cabrera Padrón | scabrerapadron(a)suse.de | scabrerapadron(a)suse.com Full Stack Web Developer - Open Build Service SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Packages have been published but don't show up on Download package page
by Roman Chistokhodov 03 Aug '20

03 Aug '20

Hello. I made a package https://build.opensuse.org/package/show/home:FreeSlave/qt-sprite-image-plug… My packages were published for enabled distributions, they have succeeded status and I can see binary packages if I click on a certain repository, and they are available for downloading. But some of the enabled distros (Debian and Ubuntu) still don't show up on the "Download package" page, only Fedora does. Note that I disabled some repositories specifically for this package compared to the list of enabled repositories of the home project. Also I build two packages from one source. Maybe some of these details cause the trouble? There's also a similar issue reported on the forums by other user https://forums.opensuse.org/showthread.php/540382-Some-RPMs-are-not-publish… -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] i586 packages say succeeded and published, but were not actually built
by Rosanne DiMesio 01 Aug '20

01 Aug '20

In my home project, I updated my Wine packages to 5.14. The x86_64 packages built without any problem and are published. The i586 packages didn't build at all, though the page says "succeeded" for all versions (Leap 15.0, 15.1, 15.2, and Tumbleweed). If you click on the "succeeded" and look at the build log, it is the log from two weeks ago for Wine 5.13, and the Wine packages in my i586 repositories are all still 5.13. https://build.opensuse.org/package/show/home:dimesio/wine I was able to build the 32-bit baselibs locally for Leap 15.0, but when I tried to build i586 packages locally for Leap 15.2 I got an error message that nothing provides strace or rzsz. -- Rosanne DiMesio <dimesio(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0