November 2014 - openSUSE Build Service

[opensuse-buildservice] OBS 2.6 Beta 1
by Adrian Schröter 05 Nov '14

05 Nov '14

Good news admins.... ... you have new work :) The best way that we hear and solve your update problem is to update to OBS 2.6 Beta 1 right now (you may use a test system). OBS 2.6 Beta is available as version 2.5.90 inside of OBS:Server:2.6 project. You can find appliances and package repositories here: http://download.opensuse.org/repositories/OBS:/Server:/2.6/ SLE_12 needs one more fix to be available. You can find the temporary release and update notes here: https://github.com/openSUSE/open-build-service/blob/2.6/ReleaseNotes-2.6 We will improved it a bit more before the release. -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] MemoryCrash with rpmlint (32bit)
by Raymond Wooninck 05 Nov '14

05 Nov '14

Hi, At this moment I am receiving a memorycrash for rpmlint when building chromium. The buildlog shows: [ 9524s] + rpmlint_logfile=/home/abuild/rpmbuild/OTHER/rpmlint.log [ 9524s] + rm -f //home/abuild/rpmbuild/OTHER/rpmlint.log [ 9524s] + ret=0 [ 9524s] + mount -n -tproc none //proc [ 9524s] + su -s /opt/testing/bin/rpmlint abuild -- --info //home/abuild/rpmbuild/RPMS/i586/chromium-beta- ffmpegsumo-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium- beta-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium-beta- desktop-gnome-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromedriver-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/RPMS/i586/chromium-beta-desktop- kde-39.0.2171.42-1.3.i586.rpm //home/abuild/rpmbuild/SRPMS/chromium- beta-39.0.2171.42-1.3.src.rpm [ 9745s] Traceback (most recent call last): [ 9745s] File "rpmlint.py", line 384, in <module> [ 9745s] File "rpmlint.py", line 169, in main [ 9745s] File "rpmlint.py", line 231, in runChecks [ 9745s] File "BinariesCheck.py", line 382, in check [ 9745s] File "BinariesCheck.py", line 179, in __init__ [ 9745s] File "Pkg.py", line 93, in getstatusoutput [ 9745s] MemoryError [ 9745s] + ret=1 [ 9745s] + cat //home/abuild/rpmbuild/OTHER/rpmlint.log [ 9745s] 1 packages and 0 specfiles checked; 0 errors, 2 warnings. This is however only for the i586 buildhosts and I would like to know how I can resolve this ? I already have a _constraints file that is requesting 4Gb of memory, but I can't imagine that rpmlint requires more. The 64bit builds goes fine. Thanks Regards Raymond ----------------------------------------- -- 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] Need an RSA key for openssl signing, please create a new key
by Jörg Lorenzen 05 Nov '14

05 Nov '14

Hi, I have a problem with building KMP-packages for openSUSE 13.2 and higher (Factory). When I branch e.g. package virtualbox from project Virtualization, the build process ends successfully for repositories < 13.2, but fails for openSUSE 13.2 with following message: "Need an RSA key for openssl signing, please create a new key" Non-KMP-packages are build successfully for all repositories, it only fails for packages that provide kernel object files. Is there anything I forgot as I added repository for 13.2 or is this an error in OBS? Greetings Jörg Lorenzen -- 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] Project-Meta Information to build for/against tumbleweed and factory
by Johannes Kastl 04 Nov '14

04 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, as Tumbleweed and Factory merged, what to change in a home project's meta settings, to build for/against the new tumbleweed and the new factory? I have not seen (or may have missed) information on this. Are these still valid entries, or are they merging, getting new names or whatever? <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Tumbleweed" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_Factory"> <path project="openSUSE:Factory" repository="snapshot"/> <arch>i586</arch> <arch>x86_64</arch> </repository> Regards, Johannes - -- It is dangerous to be right when the government is wrong. (Voltaire) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlRZJiEACgkQzi3gQ/xETbKO7ACggodcP/EtCX0VZA2bbtOnsVd0 hMcAn27g3uSFVrQefzupy3vSG/TOrmKB =21BN -----END PGP SIGNATURE----- -- 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] inject _pubkey to imported SUSE:SLE-12:GA (own instance)
by Christian Schneemann 04 Nov '14

04 Nov '14

Hi, at the moment I have to do local builds with osc build SUSE:SLE-12:GA x86_64 --no-verify, because there is no pubkey for this repository. Is it possible to inject the pub key somehow? I have imported the RPMs from the ISO files. Regards, Christian -- Christian Schneemann System Management & Monitoring Architect Tel.: +49-175-7250665 Mail: schneemann(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 -- 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] Issue with sqlite and libxml2 packages in SLE12 ?
by Rashmi Ranjan Mohanty 03 Nov '14

03 Nov '14

Hi, Is there any issue with the sqlite and libxml2 packages in SLE12 OBS repository ? One package I was building failed while linking to these libraries. When I tried to compile the package on an installed SLE12 system, it worked just fine. Only in OBS its failing. Project : home:mrashmiranjan:zmd-backend Package : solv-backend Can someone please help what is the problem ? Thanks and Regards Rashmi -- 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] [Fwd: Re: [Openvpn-users] RE 2.3.5 - systemd] fail on the OBS 2/2
by Hans Witvliet 01 Nov '14

01 Nov '14

Please have a look at the comment of one of the developpers of openvpn.. How can i provide: libsystemd.pc or libsystemd-daemon.pc files ? Hans -------- Forwarded Message -------- > From: David Sommerseth <openvpn.list(a)topphemmelig.net> > Reply-to: openvpn-users(a)lists.sourceforge.net > To: Gert Doering <gert(a)greenie.muc.de>, J.Witvliet(a)mindef.nl > Cc: hwit(a)a-domani.nl, openvpn-users(a)lists.sourceforge.net > Subject: Re: [Openvpn-users] RE 2.3.5 - systemd > Date: Fri, 31 Oct 2014 21:51:22 +0100 > > On 30/10/14 19:28, Gert Doering wrote: > > Hi, > > > > On Thu, Oct 30, 2014 at 11:39:22AM +0100, J.Witvliet(a)mindef.nl > > wrote: > >> My first assumption was that on this particular build-node, > >> system was not found, But that makes no sense, as 2.3.4 builds > >> OK, with or without system on OS12.2, OS12.3, OS13.1, OS13.2, > >> OSFactory, SLES11SP3 and SLES12 > >> > >> Have to dive a bit deeper, I guess. > >> > > > > 2.3.4 doesn't link to systemd, just call the binary - 2.3.5 > > contains the additional check "is systemd running?" via libsystemd. > > So, on a system that does not actually have systemd installed, > > 2.3.4 would compile just fine, and possibly just not use the > > systemd ask-password at run-time, while 2.3.5 will not build. > > > > If there *is* systemd on that node, it should compile, though... > > > > David, this is yours to diagnose further and patch :-) > > Yes, 2.3.4 and earlier did not carry any libsystemd or > libsystemd-daemon if compiled with --enable-systemd. However, the > check if the system was booted with systemd or not was not optimal > earlier on either. That has improved now. > > The dependency of libsystemd or libsystemd-daemon (depends on which > version of systemd is installed) is caused by us now calling > sd_booted() now instead of checking if the cgroups file tree with > systemd traces is present or not. By calling sd_booted(), systemd > provides us a sane way to do this check, even if they decide to change > the check mechanism under the hood. > > When OpenVPN is built for a system using systemd, it doesn't matter if > it has this dependency or not, systemd will always be available. And > if not, the OpenVPN package should pull in the needed systemd package > when being installed. For RPM based distributions, the complete > distro is built either with or without systemd, there is no "maybe > systemd is here" scenario. > > The problem in this particular case is solely that the RPM .spec file > openSuSE uses is not updated with the dependency on the systemd-devel > package (that's what it's called in Fedora at least). That package > carries the needed pkg-config files telling how to include the needed > systemd library when linking the openvpn binary. This [1] is what the > Fedora packager did when building 2.3.5 for Fedora. > > [1] > <http://pkgs.fedoraproject.org/cgit/openvpn.git/commit/?id=ef86d1da9850e23a6…> > > So, Hans, please ensure that the package providing the proper > libsystemd.pc or libsystemd-daemon.pc files are installed. OpenVPN > now needs a BuildRequirement for that particular package, as well as > Requires on the systemd-libs package (which should carry libsystemd.so > and/or libsystemd-daemon.so). If the systemd packages have similar > names as Fedora, then you can look what's done in the Fedora .spec file. > > > -- > kind regards, > > David Sommerseth -- 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] systemd detection 1/2
by Hans Witvliet 01 Nov '14

01 Nov '14

Hi all, It seems that I hit a snag, that as a noob I am not able to solve. Let me first explain that, until now, I only used the web-interface. I cloned one of the existing packages with succes: https://build.opensuse.org/package/show/home:testhans:network:network:vpn/o… As you can see, they all build successfully, even 13.2 and sles12 So i dared to try to build the latest release (not to be found anywhere else on the obs) https://build.opensuse.org/package/show/home:testhans:network:network:vpn/o… After some tweaking the spec-file, some build succeeded But those using systemd failed. Initially, i assumed PEBKAC, but next I checked upstream, and they said if i used ./configure with --enable-systemd all should be fine Next the dev's wrote because it used to work, and still works for non-systemd, the original author of previous patch should correct it. However, that author blames the build-environment, the obs. I'll forward his conclusion next to the list... ========================================================================================== From: Witvliet, J, DMO/OPS/I&S/HIN Sent: woensdag 29 oktober 2014 17:41 To: 'openvpn-users(a)lists.sourceforge.net' Subject: RE [Openvpn-users] 2.3.5 - systemd Indeed, as David said: No package 'libsystemd-daemon' found OTOH, it should be enabled… (excerpt from the spec:) … %configure \ --enable-iproute2 \ --enable-x509-alt-username \ --enable-password-save \ %if %{with_systemd} --enable-systemd \ %endif --enable-plugins \ --enable-plugin-down-root \ --enable-plugin-auth-pam \ --with-lzo-headers=%_includedir/lzo \ CFLAGS="$CFLAGS $(getconf LFS_CFLAGS) -fPIE $PLUGIN_DEFS" \ And it seems to be “turned-on”, in the log: [ 46s] systemd-210-44.1 But some lines further: [ 71s] checking for libsystemd... no [ 71s] checking for libsystemd... no [ 71s] configure: error: Package requirements (libsystemd-daemon) were not met: [ 71s] [ 71s] No package 'libsystemd-daemon' found My first assumption was that on this particular build-node, system was not found, But that makes no sense, as 2.3.4 builds OK, with or without system on OS12.2, OS12.3, OS13.1, OS13.2, OSFactory, SLES11SP3 and SLES12 Have to dive a bit deeper, I guess. Hans °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° -----Original Message----- Hi, On Wed, Oct 29, 2014 at 03:41:53PM +0100, J.Witvliet(a)mindef.nl wrote: > Does that imply any required-change during building? > I tried to build on a remote build-farm, and much to my surprise only the targets (SLES12, openSUSE_13.2, openSUSE_13.1) with systemd fails, while others like sles11sp3 and openSUSE_12.2 succeed. Well, if you use --enable-systemd, it should better be there (as it will now try to link to it). If you do not use that, it MUST NOT fail building, whether or not systemd is there. So - how are you calling configure, what is the error message? gert =================================================================== -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2