April 2019 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x
by Usman Haider 27 Nov '19

27 Nov '19

Hi, I am new and trying local build on s390x with SLE_12_SP3 using the following command sudo osc build but I get the public key not available for many packages. You can see the output by clicking the following link https://pastebin.com/YBQk3vGe I know that I can use --noverify option to bypass this and builds complete successfully when I use --noverify option but how can I fix this? What will happen if I don't fix it? -- Usman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 9

[opensuse-buildservice] Cannot upload big source files to private OBS instance
by Karsten Keil 10 May '19

10 May '19

Hi, I try to build qt5.12 in our own OBS instance (running OBS version 2.9.5). When I try to upload the big complete qt-everywhere-src-5.12.3.tar.xz tarball (~485MB) from the libqt5-qtdoc package to the server the upload hangs forever regardless if I use osc commit or file upload via the WEB UI. The file never hit the /srv/obs/source directory. I did successful upload files only a little bit smaller (~442MB) some time ago. Here is enough disk space on the server. Free shows about 2.5 GB free memory without buffers on the server. No errors on the logs, but also no entry about this file in the logs. The network shows high traffic for some tens of seconds to the obs server, then low traffic, so it seems that the file got transfered, at least a big part oft it. Any hints howto debug this ? Is here a place where the file is saved temporary during the API put operation ? Do I need to increase some limits ? Thanks Karsten -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Ubuntu 19.04
by Martin Koegler 26 Apr '19

26 Apr '19

A prefer is missing for Ubuntu 19.04: have choice for fakeroot needed by devscripts: fakeroot pseudo (https://build.opensuse.org/package/show/home:e9925248:grandorgue/grandorgue) Regards, Martin -- 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] Issue with set_version service
by Morschhäuser, Mark 25 Apr '19

25 Apr '19

Hi, I use the set_version service in combination with the tar_scm service to replace the version number in my spec file. Replacing the version in the head of the spec file works, but I use the %{version} macro in the %build section and here I get the original value instead of the replaced value. I also found out that if I grep the version from the spec file (like grep ^Version: *.spec) I also get the original value instead of the replaced one (and there is only one spec, I listed all files from the %build section). I did not look at the source RPM but if the file is not properly rewritten, then the srpm probably contains a wrong spec file. Did I do something wrong or does the service work differently? Regards, Mark ____________________________________________________________________ [TestingExpo_Footer]<http://www.testing-expo.com/europe/en/> Besuchen Sie DSA auf der Automotive Testing Expo 2019 in Stuttgart - wir freuen uns auf Sie! Stand 8448, 21. - 23. Mai 2019 Für Terminvereinbarungen und kostenlose Besucherausweise wenden Sie sich gerne an Frau Vanessa Sack: Tel.: +49 2408 9492-794 E-Mail: vanessa.sack(a)dsa.de Visit DSA at Automotive Testing Expo 2019 in Stuttgart - we look forward to welcoming you! Booth 8448, May 21 to 23, 2019 For appointments and free visitor badges please get in touch with Ms. Vanessa Sack: Phone: +49 2408 9492-794 Email: vanessa.sack(a)dsa.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] build dependencies show as blocked -- for packages that are built/available. wrong config?
by PGNet Dev 25 Apr '19

25 Apr '19

I have a home:/ project, https://build.opensuse.org/project/monitor/home:pgnd:security:netfilter configured to build/use my own, local gcc8 project, https://build.opensuse.org/projects/home:pgnd:security:netfilter/meta ... <repository name="openSUSE_Leap_15.0" rebuild="transitive" block="all" linkedbuild="all"> ... ==> <path project="home:pgnd:devel:gcc8" repository="openSUSE_Leap_15.0"/> ... </repository> ... where I've set the block="all", per https://en.opensuse.org/openSUSE:Build_Service_Concept_build_scheduling_str… Block mode ... all: The default behaviour, don't start the build if a depending package is currently building. ... Checking, the gcc8 project _is_ (re)built, in state "succeeded", https://build.opensuse.org/project/show/home:pgnd:devel:gcc8 but my dependent ...:netfilter project is completely 'blocked', https://build.opensuse.org/project/monitor/home:pgnd:security:netfilter?arc… iproute2 blocked ipset blocked iptables blocked libmnl blocked libnetfilter_acct blocked libnetfilter_conntrack blocked libnetfilter_cthelper blocked libnetfilter_cttimeout blocked libnetfilter_log blocked libnetfilter_queue blocked libnfnetlink blocked libnftnl blocked shorewall blocked xtables-addons blocked where the blocks include gcc*; e.g., for the 'shorewall' package, the block is reported as: gcc-PIE, gcc, binutils, libgmp10, gcc8, cpp, libstdc++6, libmpfr6, libmpc3, cpp8, libasan5, libatomic1, libgomp1, libitm1, liblsan0, libmpx2, libmpxwrappers2, libtsan0, libubsan1 checking, e.g., gcc-PIE, it's currently built & directly available as https://build.opensuse.org/package/binary/home:pgnd:devel:gcc8/gcc/openSUSE… and in the repos already in the same version https://download.opensuse.org/repositories/home:/pgnd:/devel:/gcc8/openSUSE… Same holds true for the other gcc*-built packages I've checked ... (1) Why do the blocks appear in my ...:netfilter for packages that are available? (2) Is there additional/different project config I need to avoid these blocks, and keep the projects in sync? -- 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] Increase space for single package build
by Giovanni Santini 23 Apr '19

23 Apr '19

Hey everyone, I pushed a package to OBS (mongodb) for ArchLinux which is available here: https://build.opensuse.org/package/show/home:ItachiSan:archlinux/mongodb but the build fails due to limited disk space. Is it possible e.g. through package metadata to increase disk space usage for this specific package? Thanks in advance Giovanni Santini -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Re: [opensuse-kernel] Compiling Kernel:Stable kernel-default on OBS -- "version mismatch" with just-built kernel-source ?
by PGNet Dev 23 Apr '19

23 Apr '19

On 4/22/19 10:15 PM, Jiri Slaby wrote: > On 23. 04. 19, 7:14, PGNet Dev wrote: >> patches.addon/series.conf > > Sorry, my bad. Remove the .conf suffix. > ugh. I should've looked 1st in kernel-source > apply-patches ! as soon as back-home's back up, I'll put it in place. thx -- 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] Ubuntu 19.04 config
by Martin Koegler 23 Apr '19

23 Apr '19

https://build.opensuse.org/projects/Ubuntu:19.04/meta list as URLs, eg: http://ftp.halifax.rwth-aachen.de/ubuntu/disco/main The URLs are missing a /dists, eg: http://ftp.halifax.rwth-aachen.de/ubuntu/dists/disco/main/ Regards, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Ubuntu 19.04 DOD not working
by Rosanne DiMesio 23 Apr '19

23 Apr '19

I've added Ubuntu 19.04 to my project, but the build shows as unresolvable. Nothing is being downloaded. -- 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

2 1

[opensuse-buildservice] Triggering rebuild in home project has no effect
by Christian Neyers 23 Apr '19

23 Apr '19

Hello list, I'm trying to trigger a rebuild for a package in my home project but I cannot get it to work. When I click 'Trigger Rebuild' on [1], I'm redirected to the overview page of the package and the message Triggered rebuild for home:cney/pijul successfully. is shown at the top. Nothing happens after though. I tried from the command line with osc as well, but no rebuild happens. % osc -d rebuild home:cney pijul openSUSE_Tumbleweed x86_64 POST https://api.opensuse.org/build/home:cney?cmd=rebuild&arch=x86_64&repository… ok Is manually triggering a rebuild allowed/forbidden for home projects? I couldn't find anything on the topic with a quick web search. Thanks and cheers [1] https://build.opensuse.org/package/live_build_log/home:cney/pijul/openSUSE_… -- 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] Why no more openQA tests for TW PowerPC ?
by Normand 23 Apr '19

23 Apr '19

Since a while, there is no more triggering of openQA tests for TW PowerPC, last one is dated 20190326 (1) Is it related to the ttm strange output as reported below ? (2) and how to investigate such problem ? (1) https://openqa.opensuse.org/group_overview/4 (2) === $~/work/openSUSE-release-tools/totest-manager.py --dry --debug run openSUSE:Factory:PowerPC WARNING:ttm.manager:we have only 0 jobs INFO:ttm.manager:current_snapshot 20190414: inprogress DEBUG:ttm.manager:current_qa_version 20190414 DEBUG:ttm.manager:No ttm_amqp_url configured in oscrc - skipping amqp event emission INFO:ttm.manager:setting failed snapshot to DEBUG:ttm.manager:Snapshot 20190414 is still in progress === -- Michel Normand -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Re: [opensuse-kernel] Compiling Kernel:Stable kernel-default on OBS -- "version mismatch" with just-built kernel-source ?
by PGNet Dev 23 Apr '19

23 Apr '19

On 4/22/19 9:40 PM, Jiri Slaby wrote: > On 23. 04. 19, 0:43, PGNet Dev wrote: >> Bingo. Hadn't thought to re-check the manual edits; I mistakenly >> assumed they'd merge. >> >> Updating the series.conf seems to do the trick. > > Put your own series.conf into patches.addon.tar.bz2. They will merge then. That'd certainly be simpler/cleaner. I removed the 'full', edited series.conf (which was working) and instead added 'my' series.conf patches.addon/ patches.addon/xen-pvh-uefi.patch patches.addon/series.conf where cat patches.addon/series.conf patches.addon/xen-pvh-uefi.patch tar'd it up as, patches.addon.tar.bz2 and UL'd it; e.g., https://build.opensuse.org/package/show/home:pgnd:Kernel:stable:xen-uefi-fi… The build does NOT seem to pick up / apply the patch ; at least there's no current trace of the "xen-pvh-uefi.patch" in the logfile, https://build.opensuse.org/build/home:pgnd:Kernel:stable:xen-uefi-fix/openS… -- 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] Compiling Kernel:Stable kernel-default on OBS -- "version mismatch" with just-built kernel-source ?
by PGNet Dev 22 Apr '19

22 Apr '19

I'm building a Kernel:stable instance -- as closely as possible, a project clone of the Kernel:stable repo -- that I can patch, etc locally in my home: instance. It's been generally well behaved. Intermittently -- like, now -- I get a 'failed' build, only of the dependent kernel-default pkg, https://build.opensuse.org/project/show/home:pgnd:Kernel:stable ; its parent kernel-source build fine. But, intermittently -- like, now -- I get a 'failed' build, only of the dependent kernel-default pkg; its parent kernel-source builds OK. The build log shows the fail as a 'Kernel release mismatch', https://build.opensuse.org/package/live_build_log/home:pgnd:Kernel:stable/k… ... [ 58s] ++ make -s kernelrelease ARCH=x86 --output-sync -j8 [ 60s] + krel=5.0.8-21.g7bd8353-default [ 60s] + '[' 5.0.8-21.g7bd8353-default '!=' 5.0.9-21.g7bd8353-default ']' [ 60s] + echo 'Kernel release mismatch: 5.0.8-21.g7bd8353-default != 5.0.9-21.g7bd8353-default' [ 60s] Kernel release mismatch: 5.0.8-21.g7bd8353-default != 5.0.9-21.g7bd8353-default [ 60s] + exit 1 [ 60s] error: Bad exit status from /var/tmp/rpm-tmp.kow8W6 (%prep) ... At the time of the fail, kernel-source _had_ built successfully; packages _were_ available as v5.0.9x, https://build.opensuse.org/package/binaries/home:pgnd:Kernel:stable/kernel-… As I understand it, kernel-default is simply derived from my obs instance's kernel-source, https://build.opensuse.org/package/view_file/home:pgnd:Kernel:stable/kernel… <link project="home:pgnd:Kernel:stable" package="kernel-source" cicount="copy" /> To rebuild the entire project, I exec osc wipebinaries home:pgnd:Kernel:stable osc rebuildpac --all home:pgnd:Kernel:stable I thought that's sufficient to clean + rebuild all from scratch ... but it simply re-failed. Other than from a build remnant _oustide_ my OBS build root, I can't see where the "mismatched" v5.0.*8* is originating. What do I need to do to eliminate/avoid this FAIL, & ensure that my kernel-default builds are in-sync with, and using, the parent kernel-source sources? -- 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] Re: [opensuse-kernel] Compiling Kernel:Stable kernel-default on OBS -- "version mismatch" with just-built kernel-source ?
by PGNet Dev 22 Apr '19

22 Apr '19

> Your _link file for the kernel-default (and other derivatives, if any) > should look like: > <link project="Kernel:stable" package="kernel-source" cicount="copy" /> > > Where project is your own project. > Sorry, I'm unfortunately missing your point. >From my OP, below, I'd verified that I _do_ have, >> https://build.opensuse.org/package/view_file/home:pgnd:Kernel:stable/kernel… >> >> <link project="home:pgnd:Kernel:stable" package="kernel-source" cicount="copy" /> >> Isn't that already exactly what you're suggesting it should look like? On 4/22/19 1:50 PM, Jeff Mahoney wrote: > On 4/22/19 12:59 PM, PGNet Dev wrote: >> I'm building a Kernel:stable instance -- as closely as possible, a project clone of the Kernel:stable repo -- that I can patch, etc locally in my home: instance. > > I think you're probably missing the bit that keeps the release numbers > in lockstep. > > Your _link file for the kernel-default (and other derivatives, if any) > should look like: > <link project="Kernel:stable" package="kernel-source" cicount="copy" /> > > Where project is your own project. > > -Jeff > > >> It's been generally well behaved. Intermittently -- like, now -- I get a 'failed' build, only of the dependent kernel-default pkg, >> >> https://build.opensuse.org/project/show/home:pgnd:Kernel:stable >> >> ; its parent kernel-source build fine. >> >> But, intermittently -- like, now -- I get a 'failed' build, only of the dependent kernel-default pkg; its parent kernel-source builds OK. >> >> The build log shows the fail as a 'Kernel release mismatch', >> >> https://build.opensuse.org/package/live_build_log/home:pgnd:Kernel:stable/k… >> >> ... >> [ 58s] ++ make -s kernelrelease ARCH=x86 --output-sync -j8 >> [ 60s] + krel=5.0.8-21.g7bd8353-default >> [ 60s] + '[' 5.0.8-21.g7bd8353-default '!=' 5.0.9-21.g7bd8353-default ']' >> [ 60s] + echo 'Kernel release mismatch: 5.0.8-21.g7bd8353-default != 5.0.9-21.g7bd8353-default' >> [ 60s] Kernel release mismatch: 5.0.8-21.g7bd8353-default != 5.0.9-21.g7bd8353-default >> [ 60s] + exit 1 >> [ 60s] error: Bad exit status from /var/tmp/rpm-tmp.kow8W6 (%prep) >> ... >> >> At the time of the fail, kernel-source _had_ built successfully; packages _were_ available as v5.0.9x, >> >> https://build.opensuse.org/package/binaries/home:pgnd:Kernel:stable/kernel-… >> >> As I understand it, kernel-default is simply derived from my obs instance's kernel-source, >> >> https://build.opensuse.org/package/view_file/home:pgnd:Kernel:stable/kernel… >> >> <link project="home:pgnd:Kernel:stable" package="kernel-source" cicount="copy" /> >> >> >> To rebuild the entire project, I exec >> >> osc wipebinaries home:pgnd:Kernel:stable >> osc rebuildpac --all home:pgnd:Kernel:stable >> >> I thought that's sufficient to clean + rebuild all from scratch ... but it simply re-failed. >> >> Other than from a build remnant _oustide_ my OBS build root, I can't see where the "mismatched" v5.0.*8* is originating. >> >> What do I need to do to eliminate/avoid this FAIL, & ensure that my kernel-default builds are in-sync with, and using, the parent kernel-source sources? >> >> > > -- 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] Linked spec files not updating after file is patched?
by IBBoard 21 Apr '19

21 Apr '19

Hi, I'm having some problems with custom builds that require spec file changes. While the changes themselves work, it seems to cause OBS to stop tracking the upstream changes. I don't know whether this is a bug, expected behaviour, or something that I've done wrong. I've branched Gnome Books from GNOME:Factory [1]. I'm fairly sure I didn't tick the "stay on this revision" box. I've added some diffs for custom patches and put a "<topadd>" tag in my _link [2] to add the patches without having to make an actual .diff file for the .spec. Gnome 3.32 has been released* and the upstream spec file is showing v3.32 [3]. Meanwhile, my spec file is still showing 3.30.1 [4]. However, I *do* see the 3.32 tarball in my (merged) sources, as well as the old 3.30 one [5]. Is there a way to fix this so that my packages modify the .spec to add patches but also track the upstream changes? I'm happy to fix breakages if the spec file changes a lot upstream (as that's basically what I'd have to do with a diff file if upstream changed a lot). Thanks, IBBoard * Yes, I know this breaks my example package, because Gnome Books has been separated, but I think that's separate from the underlying spec change issue [1] https://build.opensuse.org/package/show/home:IBBoard:desktop/gnome-documents [2] https://build.opensuse.org/package/view_file/home:IBBoard:desktop/gnome-doc… [3] https://build.opensuse.org/package/view_file/GNOME:Factory/gnome-documents/… [4] https://build.opensuse.org/package/view_file/home:IBBoard:desktop/gnome-doc… [5] https://build.opensuse.org/package/show/home:IBBoard:desktop/gnome-document… -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 6

[opensuse-buildservice] Ubuntu 19.04 unresolvable
by Rosanne DiMesio 21 Apr '19

21 Apr '19

Ubuntu 19.04 is now available through expert mode, but the builds show as unresolvable; nothing is being installed. -- 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

[opensuse-buildservice] Qt5 issue building vlc for TW on a local obs
by Hans-Peter Jansen 20 Apr '19

20 Apr '19

Hi, struggling with a strange issue here, when building vlc for TW. Many other packages, including vlc for other targets, and the kernel, build fine. Build log, stripped to the essentials: [ 69s] libQt5Core5-5.12.2-1.2 ######################################## [ 69s] libQt5DBus5-5.12.2-1.2 ######################################## [ 69s] libQt5Network5-5.12.2-1.2 ######################################## [ 70s] libQt5Gui5-5.12.2-1.2 ######################################## [ 70s] libQt5Widgets5-5.12.2-1.2 ######################################## [ 70s] libQt5OpenGL5-5.12.2-1.2 ######################################## [ 71s] libQt5Svg5-5.12.2-1.1 ######################################## [ 71s] libQt5X11Extras5-5.12.2-1.1 ######################################## [ 71s] libQt5Test5-5.12.2-1.2 ######################################## [ 71s] libqt5-qtbase-common-devel-5.12.2-1.2 ######################################## [ 71s] libQt5Core-devel-5.12.2-1.2 ######################################## [ 72s] libQt5Gui-devel-5.12.2-1.2 ######################################## [ 72s] libQt5Widgets-devel-5.12.2-1.2 ######################################## [ 72s] libQt5Core-private-headers-devel-5.12.######################################## [ 81s] libQt5Gui-private-headers-devel-5.12.2######################################## [ 160s] checking for Qt5Core >= 5.5.0 Qt5Widgets Qt5Gui Qt5Svg... yes [ 160s] checking for Qt5X11Extras... yes [ 160s] checking for moc-qt5... /usr/lib64/qt5/bin/moc-qt5 [ 160s] checking for rcc-qt5... /usr/lib64/qt5/bin/rcc-qt5 [ 160s] checking for uic-qt5... /usr/lib64/qt5/bin/uic-qt5 [ 242s] UIC gui/qt/ui/equalizer.h [ 242s] /usr/lib64/qt5/bin/uic-qt5: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory [ 242s] make[2]: *** [Makefile:31005: gui/qt/ui/equalizer.h] Error 127 Something is wrong with libQt5Core.so.5, hence I instrumented the spec: %build ls -l /usr/bin/uic-qt5 ldd /usr/bin/uic-qt5 ls -l /usr/lib*/libQt5Core.* rpm -qi libQt5Core5 rpm -V libQt5Core5 rpm -qi libqt5-qtbase-common-devel rpm -V libqt5-qtbase-common-devel uic-qt5 --help Result (newlines added for orientation): [ 122s] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.jAXdQH [ 122s] + umask 022 [ 122s] + cd /home/abuild/rpmbuild/BUILD [ 122s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/vlc-3.0.6-301.1.x86_64 [ 122s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/vlc-3.0.6-301.1.x86_64 [ 122s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT [ 122s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/vlc-3.0.6-301.1.x86_64 [ 122s] + cd vlc-3.0.6 [ 122s] + ls -l /usr/bin/uic-qt5 [ 122s] -rwxr-xr-x 1 root root 614056 Apr 4 13:35 /usr/bin/uic-qt5 [ 122s] + ldd /usr/bin/uic-qt5 [ 122s] linux-vdso.so.1 (0x00007ffe01c95000) [ 122s] libQt5Core.so.5 => not found [ 122s] libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fa168883000) [ 122s] libc.so.6 => /lib64/libc.so.6 (0x00007fa1686be000) [ 122s] libm.so.6 => /lib64/libm.so.6 (0x00007fa16857a000) [ 122s] /lib64/ld-linux-x86-64.so.2 (0x00007fa168aba000) [ 122s] libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa168560000) [ 122s] + ls -l /usr/lib64/libQt5Core.prl /usr/lib64/libQt5Core.so /usr/lib64/libQt5Core.so.5 /usr/lib64/libQt5Core.so.5.12 /usr/lib64/libQt5Core.so.5.12.2 [ 122s] -rw-r--r-- 1 root root 1169 Apr 4 13:35 /usr/lib64/libQt5Core.prl [ 122s] lrwxrwxrwx 1 root root 20 Apr 4 13:33 /usr/lib64/libQt5Core.so -> libQt5Core.so.5.12.2 [ 122s] lrwxrwxrwx 1 root root 20 Apr 4 13:33 /usr/lib64/libQt5Core.so.5 -> libQt5Core.so.5.12.2 [ 122s] lrwxrwxrwx 1 root root 20 Apr 4 13:33 /usr/lib64/libQt5Core.so.5.12 -> libQt5Core.so.5.12.2 [ 122s] -rwxr-xr-x 1 root root 5433704 Apr 4 13:35 /usr/lib64/libQt5Core.so.5.12.2 [ 122s] + rpm -qi libQt5Core5 [ 122s] Name : libQt5Core5 [ 122s] Version : 5.12.2 [ 122s] Release : 1.2 [ 122s] Architecture: x86_64 [ 122s] Install Date: Sat Apr 13 16:19:50 2019 [ 122s] Group : Development/Libraries/X11 [ 122s] Size : 5625913 [ 122s] License : LGPL-2.1-with-Qt-Company-Qt-exception-1.1 or LGPL-3.0-only [ 122s] Signature : RSA/SHA256, Thu Apr 4 13:56:55 2019, Key ID b88b2fd43dbdc284 [ 122s] Source RPM : libqt5-qtbase-5.12.2-1.2.src.rpm [ 122s] Build Date : Thu Apr 4 13:37:12 2019 [ 122s] Build Host : wildcard2 [ 122s] Relocations : (not relocatable) [ 122s] Packager : https://bugs.opensuse.org [ 122s] Vendor : openSUSE [ 122s] URL : https://www.qt.io [ 122s] Summary : Qt 5 Core Library [ 122s] Description : **stripped** [ 122s] Distribution: openSUSE Tumbleweed [ 122s] + rpm -V libQt5Core5 [ 122s] + rpm -qi libqt5-qtbase-common-devel [ 122s] Name : libqt5-qtbase-common-devel [ 122s] Version : 5.12.2 [ 122s] Release : 1.2 [ 122s] Architecture: x86_64 [ 122s] Install Date: Sat Apr 13 16:19:52 2019 [ 122s] Group : Development/Libraries/X11 [ 122s] Size : 7187721 [ 122s] License : LGPL-2.1-with-Qt-Company-Qt-exception-1.1 or LGPL-3.0-only [ 122s] Signature : RSA/SHA256, Thu Apr 4 13:57:05 2019, Key ID b88b2fd43dbdc284 [ 122s] Source RPM : libqt5-qtbase-5.12.2-1.2.src.rpm [ 122s] Build Date : Thu Apr 4 13:37:12 2019 [ 122s] Build Host : wildcard2 [ 122s] Relocations : (not relocatable) [ 122s] Packager : https://bugs.opensuse.org [ 122s] Vendor : openSUSE [ 122s] URL : https://www.qt.io [ 122s] Summary : Qt 5 Core Development Binaries [ 122s] Description : **stripped** [ 122s] Distribution: openSUSE Tumbleweed [ 122s] + rpm -V libqt5-qtbase-common-devel [ 122s] + uic-qt5 --help [ 122s] uic-qt5: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory [ 122s] error: Bad exit status from /var/tmp/rpm-tmp.jAXdQH (%build) Puzzled. the ldd result is really strange. Apart from being unable to locate libQt5Core.so.5, it is significantly different from running the command locally: $ ldd /usr/bin/uic-qt5 linux-vdso.so.1 (0x00007ffd430aa000) libQt5Core.so.5 => /usr/lib64/libQt5Core.so.5 (0x00007fd52aa0c000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fd52a87f000) libc.so.6 => /lib64/libc.so.6 (0x00007fd52a6ba000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd52a699000) libsystemd.so.0 => /usr/lib64/libsystemd.so.0 (0x00007fd52a5e0000) libz.so.1 => /lib64/libz.so.1 (0x00007fd52a5c6000) libicui18n.so.suse64.1 => /usr/lib64/libicui18n.so.suse64.1 (0x00007fd52a2bb000) libicuuc.so.suse64.1 => /usr/lib64/libicuuc.so.suse64.1 (0x00007fd52a0dd000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fd52a0d8000) libpcre2-16.so.0 => /usr/lib64/libpcre2-16.so.0 (0x00007fd52a039000) libdouble-conversion.so.2 => /usr/lib64/libdouble-conversion.so.2 (0x00007fd52a02c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007fd529f08000) libm.so.6 => /lib64/libm.so.6 (0x00007fd529dc2000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fd529da8000) /lib64/ld-linux-x86-64.so.2 (0x00007fd52b005000) librt.so.1 => /lib64/librt.so.1 (0x00007fd529d9d000) liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fd529d66000) liblz4.so.1 => /usr/lib64/liblz4.so.1 (0x00007fd529d46000) libcap.so.2 => /usr/lib64/libcap.so.2 (0x00007fd529d3f000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fd529d11000) libgcrypt.so.20 => /usr/lib64/libgcrypt.so.20 (0x00007fd529bf1000) libicudata.so.suse64.1 => /usr/lib64/libicudata.so.suse64.1 (0x00007fd529bee000) libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fd529b5e000) libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007fd529b3a000) Hrmpf. It looks like ldconfig isn't doing correctly for this specific case, is it? TW is setup as usual: <repository name="openSUSE_Tumbleweed"> <path project="openSUSE.org:openSUSE:Factory" repository="snapshot"/> <arch>i586</arch> <arch>x86_64</arch> </repository> prjconf doesn't contain anything obvious, that could affect this. OBS is set up conservatively, and was updated to 2.9.6 a few days ago: 1 | OBS_Server_2.9 | 2.9 version of the Open Build Service Server (openSUSE_42.3) | Yes | (r ) Yes | Yes 2 | openSUSE:Leap:42.3 | openSUSE:Leap:42.3 | Yes | (r ) Yes | Yes 3 | openSUSE:Leap:42.3:Update | openSUSE:Leap:42.3:Update | Yes | (r ) Yes | Yes 4 | openSUSE:Tools | openSUSE:Tools | Yes | (r ) Yes | Yes Any idea, what could result in such a mess, and how to fix this is much appreciated. Thanks in advance, Pete -- 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] Changing the OBS server's FQDN
by Morschhäuser, Mark 15 Apr '19

15 Apr '19

Hi, I found out that our OBS internally uses a wrong domain name: I saw the name as an alias in /etc/hosts, removed it and then the web UI did not show any build results anymore. After changing it back in /etc/hosts, it worked again. I guess some service uses the wrong name and maybe also the database from OBS contains the name somehow. I saw that some perl files in /usr/lib/obs/server use Net::Domain::hostfqdn(); from perl to resolve the hostname and it looks into /etc/resolv.conf and takes the first domain from the search(!) entry which is a bug I think. This is probably how the wrong domain name was introduced in the first place. Now... how can I change the currently used FQDN to the right one for all services and everything? Also: I actually wanted to find out how to change the URL for the package download from the Binaries page ("Detailed Information About foo.rpm" links to http://localhost/build/<Project>/<arch>/foo/foo.rpm and the localhost must be configurable somewhere - or it is resolved again and defaults to localhost because the resolve does not work properly). Regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 13

[opensuse-buildservice] OBS Appliance - Unable to Update
by Khalil Graves 15 Apr '19

15 Apr '19

I am running OBS Appliance 2.8.2 on VMware ESX. When the appliance boots I get an error "Failed to start LSB: Finds the storage device to be used for OBS server and/or worker." I have included a dump of systemctl status obsstoagesetup.service below. I Just want to confirm if this is normal or should be addressed. I also attempted and update of a clone of my appliance via zypper but 2 GB root drive is not sufficient for upgrades. Update begins but end with "Error Code: Write Error". I checked root drive and it was up to 100% utilization from 93% prior to update. I decided to install latest version of OBS appliance over existing install. New appliance adopts my old setting but now I am getting and error on boot "Failed to start LSB: open build service source service server." In addition I am unable to build rpms in this current state. Not sure what to do next to get the cloned appliance to build a package. SYSTEMCTL status obsstoragesetup.service obsstoragesetup.service - LSB: Finds the storage device to be used for OBS server and/or worker Loaded: loaded (/etc/init.d/obsstoragesetup; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-03-06 18:44:59 UTC; 16min ago Docs: man:systemd-sysv-generator(8) Process: 1365 ExecStart=/etc/init.d/obsstoragesetup start (code=exited, status=1/FAILURE) Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_SERVER_SIZE=38912 Mar 06 18:44:59 linux obsstoragesetup[1365]: TOTAL_SWAP_SIZE=1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE = 12284 - 38912 - 25600 - 1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE=-53252 Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_WORKER_ROOT_SIZE=-26626 Mar 06 18:44:59 linux obsstoragesetup[1365]: MIN_WORKER_ROOT_SIZE=4096 Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Control process exited, code=exited status=1 Mar 06 18:44:59 linux systemd[1]: Failed to start LSB: Finds the storage device to be used for OBS server and/or worker. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Unit entered failed state. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Failed with result 'exit-code'. SYSTEMCTL status obsservice.service obsservice.service - LSB: open build service source service server Loaded: loaded (/etc/init.d/obsservice; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-03-09 11:59:39 UTC; 3min 34s ago Docs: man:systemd-sysv-generator(8) Process: 1761 ExecStart=/etc/init.d/obsservice start (code=exited, status=7) Mar 09 11:59:38 linux systemd[1]: Starting LSB: open build service source service server... Mar 09 11:59:39 linux startproc[1788]: startproc: exit status of parent of /usr/lib/obs/server/bs_service: 13 Mar 09 11:59:39 linux obsservice[1761]: Initializing obsservice..failed Mar 09 11:59:39 linux systemd[1]: obsservice.service: Control process exited, code=exited status=7 Mar 09 11:59:39 linux systemd[1]: Failed to start LSB: open build service source service server. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Unit entered failed state. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Failed with result 'exit-code'. '. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] is kicad-doc rebuild forever by OBS reason of no iso for openQA tests ?
by Normand 12 Apr '19

12 Apr '19

Since more than 3 weeks, there is no iso passed from OBS openSUSE:Factory:PowerPC (1) to openQA (2) from the GUI view, it seems that OBS is trying to rebuild the kicad-doc package forever, as I previously addressed in issue#50036 (3) If this is not the source of the failure, what could be the cause ? (1) https://build.opensuse.org/project/show/openSUSE:Factory:PowerPC (2) https://openqa.opensuse.org/group_overview/4 (3) https://progress.opensuse.org/issues/50036 -- Michel Normand -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] How to convert a package to a link
by Johannes Kastl 11 Apr '19

11 Apr '19

Hi all, how can I convert a package to a link? Say I created a package in foo:bar, SR'ed it to some offical devel project and from there to Factory. Now I would like my package in foo:bar to be in sync with the offical Factory package (or the one in the devel-Project), and would like it to be linked, so "osc sr" does not need any additional arguemnts... ;-) I thought I had seen a mail long time ago, but did not find anything. Any ideas or hints? 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

5 6

[opensuse-buildservice] obs-ui - to create project, it take several minutes (~3mn)
by Renato _ 04 Apr '19

04 Apr '19

Hey everyone, I am running on my own OBS v. 2.9.5 based on openSUSE 42.3. Each app are working on separate BareMetals except the DB. (1xobs-ui, 4xobs-worker, 1xobs-db in to a virtual machine) Everything is working fine. Except when we create (from UI) a new project. It takes several minutes to complete (approximately ~3mn). I noticed the same when someone NEW connect the first time on the UI. I expect, a mechanism from the obs-ui that create the own home::dir and is timing out for something. Once created, all is fast and running fine. Does someone have any clue what is going on? a track to watch or operations. Since there are no interesting logs, I could suspect something related on the DB. but I am not a DBA expert. Thank you very Much, note: all boxes are pretty much IDLE even then jobs are running. no load, no I/O disk, etc..-- 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] Project deletion broken?
by Carsten Hoeger 04 Apr '19

04 Apr '19

Hi, as I already wrote we have problems with the diskspace of our buildservice filling up. I now did a fresh and clean installation of the latest version (2.9.6), created a project, uploaded sources, waited for the build to finish and removed the project again. Guess what, the sources are still there. Is that a configuration issue or a bug? How can one permanently delete sources from within /srv/obs/sources? -- kind regards, Carsten Hoeger Engineering Services Phone: +49 2761 75252 00 Fax: +49 2761 75252 30 Email: carsten.hoeger(a)open-xchange.com ------------------------------------------------------------------------------------- Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, 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

2 1

[opensuse-buildservice] Trouble with Raspbian: "apt-key not found" during init_buildsystem
by Harald Welte 03 Apr '19

03 Apr '19

Dear OBS team, I'm trying to build packages on Raspbian 9, and I'm facing a problem where I'm not quite sure how it happens: The problem occurs during init_buildsystem, i.e. even before the rules/control files I provide take over. The last few lines are: [ 105s] [177/225] installing raspbian-archive-keyring-20120528.2 [ 105s] /var/lib/dpkg/info/raspbian-archive-keyring.postinst: 8: /var/lib/dpkg/info/raspbian-archive-keyring.postinst: apt-key: not found [ 105s] dpkg: error processing package raspbian-archive-keyring (--install): [ 105s] subprocess installed post-installation script returned error exit status 127 [ 105s] Errors were encountered while processing: [ 105s] raspbian-archive-keyring [ 105s] exit ... The full log is available at https://build.opensuse.org/public/build/network:osmocom:nightly/Raspbian_9.… Any idea how to further debug this? What can I as somebody packaging a program to do affect the existance of apt-key during the build_init stage? AFAIR apt-key is part of the 'apt' package, and I am somewhat puzzled how it could not be present on a system that obviously uses apt. But then, I'm mostly used to Debian and not Raspbian. As can be seen at https://build.opensuse.org/project/monitor/network:osmocom:nightly the same package builds fine on Debian9, including armv7l. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -- 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] Open Build Service (OBS) 2.9.6 released
by David Kang 03 Apr '19

03 Apr '19

OBS 2.9.6 released ================ This is a security and bugfix release. It's applying fixes related to permissions and authorizations and a patch for a Rails security update, that was assigned with the CVE identifier CVE-2019-5419. Updaters from any OBS 2.9 release can upgrade the packages and restart all services. Updaters from former releases should read the README.UPDATERS file. OBS update is available from the following project: https://build.opensuse.org/project/show/OBS:Server:2.9 The appliance can be downloaded from: http://openbuildservice.org/download Details from the Release Notes of 2.9.6: ================================ Bugfixes ======== Frontend: * Rails security update was patched (CVE-2019-5419). * Added upper-limit to range to avoid long running queries in Webui::MonitorController. * In WebUI, only admins are allowed to create DoD repositories. * In WebUI, only admins are allowed to create sourceaccess/access repositories flags. * Added missing authorization to move repository path in Webui::ProjectController. * Require sourceaccess by default in `require_package`. Regards, David -- David Dionisio Kang -dkang(a)suse.de |dkang(a)suse.com BuildService Engineer 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) -- David Dionisio Kang - dkang(a)suse.de | dkang(a)suse.com BuildService Engineer 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)

1 0

[opensuse-buildservice] maintenance branching
by Morschhäuser, Mark 02 Apr '19

02 Apr '19

Hi, I learned about how the maintenance process works but I cannot explain what the osc branch -M option actually does differently from normal branching. Can someone tell me please? osc help just prints " Create project and package in maintenance mode". And also I want to ask if the web interface misses this special kind of branching feature (or maybe it does it automatically if I branch from a maintained project?). Best regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] back-main schedulers missing
by Andreas Schwab 02 Apr '19

02 Apr '19

On back-main there are currently three schedulers AWOL. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] i586 builds disabled?
by Tobias Klausmann 01 Apr '19

01 Apr '19

Hi, for some reason the i586 builds seem to be disabled (despite repositories enabling it) and the repositories got wiped as well. Is this intentional to reduce the schedulers load? PS: Some package are needed in their -32bit version for x86_64, which are missing as well right now. Greetings, Tobias -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] kernel-obs-build is missed in private OBS
by Matwey V. Kornilov 01 Apr '19

01 Apr '19

Hello, I am facing the following strange issue and I need your little help to debug the issue. I am running private OBS obs-api-2.9.4 with x86_64 workers and one aarch64 worker. The ARM worker uses KVM type to run the builds. Some time ago, ARM worker stopped preinstalling kernel-obs-build for all builds. And this broke the worker since now it unsuccessfully tries to use /boot/Image and /boot/initrd to boot KVM guest. Both OBS_VM_KERNEL and OBS_VM_INITRD are set to "none" in /etc/sysconfig/obs-server Using osc buildinfo console command I see that kernel-obs-build is in the list of dependencies: <bdep name="kernel-obs-build" vminstall="1" notmeta="1" version="5.0.5" release="1.1" arch="armv7hl" project="openSUSE.org:openSUSE:Factory:ARM" repository="standard" /> In the worker logs I see the following: [ 22s] [1/11] preinstalling libcrypt1... [ 22s] [2/11] preinstalling libdb-4_8... [ 23s] [3/11] preinstalling libmnl0... [ 23s] [4/11] preinstalling libsepol1... [ 24s] [5/11] preinstalling libsmartcols1... [ 24s] [6/11] preinstalling libuuid1... [ 24s] [6/11] preinstalling libuuid1... [ 25s] [7/11] preinstalling libblkid1... [ 25s] [8/11] preinstalling perl-base... [ 26s] [9/11] preinstalling iproute2... [ 27s] [10/11] preinstalling libmount1... [ 27s] [11/11] preinstalling util-linux... [ 28s] copying packages... [ 42s] reordering...cycle: libncurses6 -> terminfo-base [ 42s] breaking dependency terminfo-base -> libncurses6 The kernel-obs-build package is missed from the list of preinstalled packages. The kernel-obs-build package is also missed from /var/cache/obs/worker/root_1/.build.rpmlist Do I understand correctly, that the package is filtered somewhere in bs_worker script? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5