September 2019 - openSUSE Build Service

[opensuse-buildservice] OBS ignoring %define _lto_cflags %{nil} in spec file
by Rosanne DiMesio 14 Sep '19

14 Sep '19

Wine does not build with LTO enabled. I have %define _lto_cflags %{nil} in my spec file, and this has worked in the past to disable it, but my Tumbleweed builds are suddenly failing with lto errors: wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libadsiid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libdmoguids.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libdxguid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libmfuuid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libstrmiids.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libuuid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libwmcodecdspuuid.a [ 993s] This archive does not contain a non-empty .text section. The archive was not [ 993s] created with -ffat-lto-objects option. My project is https://build.opensuse.org/package/show/home:dimesio/wine. -- 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

3 4

[opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not?
by Manfred Hollstein 13 Sep '19

13 Sep '19

Hi there, I've given up (I think) trying to understand why OBS sometimes behaves different than what I'd expect. Here is my (current) challenge: I'm trying to build firefox69 in my own project in home:manfred-h:mozilla. The repository metadata is set up as follows: $ osc meta prj home:manfred-h:mozilla <project name="home:manfred-h:mozilla"> <title>mozilla</title> <description> Mozilla based projects and support packages. </description> <person userid="manfred-h" role="maintainer"/> <build> <disable/> </build> <repository name="openSUSE_Leap_42.3"> <path project="home:manfred-h:devel:languages:rust" repository="openSUSE_Leap_42.3"/> <path project="mozilla" repository="openSUSE_Leap_42.3"/> <path project="openSUSE:Leap:42.3:Update" repository="standard"/> <path project="openSUSE:Leap:42.3" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.1"> <path project="devel:languages:rust" repository="openSUSE_Leap_15.1"/> <path project="mozilla" repository="openSUSE_Leap_15.1"/> <path project="openSUSE:Leap:15.1:Update" repository="standard"/> <path project="openSUSE:Leap:15.1" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.0"> <path project="home:manfred-h:devel:languages:rust" repository="openSUSE_Leap_15.0"/> <path project="mozilla" repository="openSUSE_Leap_15.0"/> <path project="openSUSE:Leap:15.0:Update" repository="standard"/> <path project="openSUSE:Leap:15.0" repository="standard"/> <arch>x86_64</arch> </repository> </project> As you can see, nothing should get build by default (this is enabled purely on a package by package case) and repositories are setup so that "rust" and related packages should be taken from - devel:languages:rust for openSUSE_Leap_15.1 - home:manfred-h:devel:languages:rust for 42.3 and 15.0 firefox69 now needs rust-cbindgen >= 0.9.0, so I copied that package to my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 Still OBS thinks "nothing provides rust-cbindgen >= 0.9.0" for 15.0 and 42.3, but the packages are there: <https://build.opensuse.org/package/binary/home:manfred-h:devel:languages:ru…> <https://build.opensuse.org/package/binary/home:manfred-h:devel:languages:ru…> both providing: rust-cbindgen = 0.9.0-1.1 rust-cbindgen(x86-64) = 0.9.0-1.1 FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to rust-cbindgen in the home:manfred-h:devel:languages:rust project, but this did not change anything unfortunately. Can anybody tell me what I'm doing wrong here? Or is this a bug in the OBS resolver? TIA, cheers. l8er manfred PS: No complaints wrt/ 42.3, I'm not yet done with migrating all systems I maintain to 15.1 yet! Therefore I'm trying to keep those packages still building which are not services but still as close to the Internet as possible, i.e. the _bad world_ ;)

7 32

[opensuse-buildservice] Error "Version is invalid" for JeOS 15 and 15SP1
by Vincent Moutoussamy 11 Sep '19

11 Sep '19

Hi there, When selecting "SLE 15 JeOS and SLE 15 SP1 JeOS” from https://build.opensuse.org/image_templates and trying to “create appliance”, I get the following error message: > Kiwi File 'JeOS.kiwi' has errors: > • Preferences: > • Version is invalid on page like: https://build.opensuse.org/package/view_file/home:gameboy974:branches:SUSE:… my-kiwi-templates-SLES15-JeOS/JeOS.kiwi?expand=1 I think this is because the kiwi file contains the following, instead of 15.0.0: <preferences profiles="kvm-and-xen"> <version>15.0</version> At least it works for openSUSE and their kiwi files contains: <preferences profiles="kvm-and-xen"> <version>15.1.0</version> So my question is it really a hard requirement to have version as X.Y.Z instead of X.Y or is this a bug? Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager

3 3

[opensuse-buildservice] Enhancement ideas for https://build.opensuse.org/image_templates
by Vincent Moutoussamy 11 Sep '19

11 Sep '19

Hi, I think the former SUSE Studio UI* was a bit better than what we have on https://build.opensuse.org/image_templates. So here are some of my idea to improve the existing page: 1) Having “Template for”/“Templates using" in the name of each projects might be too much? In that regard I could rename “SLE 15 Code Line” by just “SUSE Linux Enterprise 15” and you could rename "Templates using openSUSE Leap 15.1” by just “openSUSE Leap 15.1”. 2) Emphasis on openSUSE and SLE latest version - By having a “UI frame” called "openSUSE and SLE latest versions” containing Leap 15.1, Tumbleweed and SLE 15.1. - Then a frame called “others” containing everything else but with Leap 15.0 and SLE 15.1 at the top, then the rest So do you like my ideas? I’m wondering if I could contribute/do this on my own and how? Thanks and have a nice day, Regards, * for reference https://nocnypingwin.pl/wp-content/uploads/2014/02/zrzutekranu23.png -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager

3 4

[opensuse-buildservice] Removing old template from Studio Express
by Vincent Moutoussamy 11 Sep '19

11 Sep '19

Hi there, Would it be possible to remove all the following unsupported openSUSE/SLE versions from https://build.opensuse.org/image_templates? Unsupported versions: - SLE: 12SP2, 12SP3, 11SP4, - Leap: 42.3 Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] missing _rpmmacrodir for SLE 12 / Leap 42 in devel:languages:ruby PRJ
by Christian 10 Sep '19

10 Sep '19

Hi, may we have the following added to projconf of devel:languages:ruby please ? ### seems that _rpmmacrodir is not known on SLE 12 / Leap 42 %if %{suse_version} == 1315 Macros: %_rpmmacrodir /etc/rpm :Macros %endif This will fix some of the existing build errors in devel:languages:ruby Thank you :-) -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

2 2

[opensuse-buildservice] Mirroring an Open Build Service repository
by Linux Kamarada 09 Sep '19

09 Sep '19

Hi, everyone! Is it possible to mirror an Open Build Service repository? I tried some commands such as: # rsync -avz --delete rsync://download.opensuse.org/repositories/home:/kamarada:/15.1/ /srv/www/htdocs/kamarada-repo/15.1/ or # lftp -c mirror https://ftp.opensuse.org/pub/opensuse/repositories/home:/kamarada:/15.1/ /srv/www/htdocs/kamarada-repo/15.1/ But they didn't work. Thanks! Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] python3.4-venv and python3-wheel missing from Ubuntu 14.04 standard
by Neal Gompa 06 Sep '19

06 Sep '19

Hey, I'm trying to build packages with python3.4-venv and python3-wheel as build dependencies on Ubuntu 14.04, but they appear to be missing. These packages are included in the Ubuntu main repo, so I would have expected them to exist in the Ubuntu 14.04 standard target... Can someone please fix this? Thanks in advance, Neal -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7

[opensuse-buildservice] repodata not matching sha256 for a package
by Julio Gonzalez 06 Sep '19

06 Sep '19

I have this strange issue: https://github.com/uyuni-project/uyuni/issues/1261#issuecomment-528854701 The repodata XML [1] says that the package zypp-plugin-python-0.6.2- lp150.2.1.noarch.rpm has the following sha56sum: e713e07a5d980f49da0224348e9d5c65414feb3d8257eb7f8e43e32493081f68 While downloading the package from the repository [2] and running sha25tsum returns: ec3b1d39297966d6e972b449f02a161ebc1b93f794e3bfde16d53cb63e9ea234 In case it's relevant, the source package: https://build.opensuse.org/package/ show/systemsmanagement:Uyuni:Stable:openSUSE_Leap_15-Uyuni-Client-Tools/zypp- plugin Was "promoted" using "osc release" (as you can see at the package history). Other packages seem to be fine. So the thing is: is there any way of republishing the repodata without rebuilding any package? Why did this happen? Did we do anything wrong? Best regards. [1] https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ Stable:/openSUSE_Leap_15-Uyuni-Client-Tools/openSUSE_Leap_15.0/repodata/ fda1b74b6cc4109175630e001eaea9f02f9c3f0a684763ba47920303dd0918ed- primary.xml.gz [2] https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ Stable:/openSUSE_Leap_15-Uyuni-Client-Tools/openSUSE_Leap_15.0/noarch/zypp- plugin-python-0.6.2-lp150.2.1.noarch.rpm -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[opensuse-buildservice] Extracting spec file from a git repo on OBS
by Dominig ar Foll (Intel Open Source) 04 Sep '19

04 Sep '19

Hello, I would like to maintain my spec file in git repo like I do for the rest of the code with "obs_scm" in "_service". It would allow to enforce the same change control process on spec files than on the rest of the code. I know that Tizen in it's time, had done a hack on their own OBS, but I wonder if the same facility would be now available on the public OpenSUSE OBS. A pointer to a solution would be very appreciated. Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 6