April 2015 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] enabling networking for workers
by Darin Perusich 19 Dec '17

19 Dec '17

Hello All, I'm running a private instance and I'd like to enable networking on my workers so they can build some java apps, via maven, which need to download pom's/war's from the net. I ask google but he wasn't much help so I'm hoping someone here can help;-) How can I go about doing this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 10

[opensuse-buildservice] broken mirror tux.rainside.sk
by Olaf Hering 16 Jan '17

16 Jan '17

Not sure what the correct list is to report mirror issues, but http://tux.rainside.sk/opensuse/ is empty. laf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Ghost package
by trcs＠gmx.com 14 Dec '15

14 Dec '15

Hi. There is a ghost package in my OBS home project. I'm using the web interface, not the command line one. If you go to https://build.opensuse.org/project/show/home:jcsl:LXDE you can see the real 10 packages in the Packages box on left side, but if you look in the Build Results box, on the right side, you see 11 next to the "succeeded" text. If you then click the succeeded link you find the pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package "pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It even appears in the scheduled and building states when something I'm building triggers its build (I don't know how can this be). Any hints? Greetings. -- 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] submitting a _link
by Olaf Hering 12 May '15

12 May '15

In packman its often requested create a new package which just links back to OBS. But the SR would always expand the _link in the destination project, so the actual content and intent is lost. What has to be done to copy the pkg contents as is from source prj to destination prj via a submit request? Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 18

[opensuse-buildservice] syntax to create _link to specific revsions
by Olaf Hering 07 May '15

07 May '15

For short: How do I incrementally _link to each revision of a given package? The obvious way with 'osc log ; osc linkpac -r NUM' does not work for me. The first attempt fails with 'revision not found', but according to osc log r144 is the latest: pbs linkpac -f -r 131 -C copy openSUSE.org:GNOME:Factory gobject-introspection home:olh gobject-introspection Revision '131' does not exist Perhaps PMBS or osc can not talk to remotes? Then I tried it in OBS, which does not work either: obs setlinkrev -r 131 Server returned an error: HTTP Error 400: conflict in file gobject-introspection.spec conflict in file gobject-introspection.spec obs setlinkrev -r 130 set revision to 0a89b97678cca77c5cb6ed8b26628d65 for package gobject-introspection obs up -e Expanding to rev 8fe7b258738f5d078d312bc32263b5b5 A g-ir-dep-tool.patch A gi-find-deps.sh A gobject-introspection-1.44.0.tar.xz A gobject-introspection-rpmlintrc A gobject-introspection-typelib.template A gobject-introspection.changes A gobject-introspection.spec A gobjectintrospection.attr D _link At revision 8fe7b258738f5d078d312bc32263b5b5. But: r130 is certainly not package version 1.44. I wonder what 'osc log' output and 'osc linkpac|setlink' is supposed to represent. 8fe7b258738f5d078d312bc32263b5b5 does not appear in any 'osc log' output. Olaf -- 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] Building of noarch packages
by Stanislav Baiduzhyi 02 May '15

02 May '15

I've noticed that packages, having "BuildArch: noarch" in spec files, are still built for all the architectures. Is that expected behaviour, or am I doing something wrong? -- Regards, Stas -- 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] OBS source_service usage with upstream git sources -- syntax for .spec file's dynamic Source:/Version:/Release: values?
by PGNd 29 Apr '15

29 Apr '15

I am creating a pkg, intending to use upstream git repo for its source. Manually pulling the source repo into local obs workspace, tar.gz'ing it, works as expected. I need to prepare for frequent updates of multiple packages' upstream git sources, and wish to automate the process. For triggerable automation of the process, OBS' Source Services are appropriate, 8 Source Services http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.source… For my current test pkg, osc mkpac pgnd-cryptodev cd ./pgnd-cryptodev 'add' the obs source_service template osc add git://github.com/openSUSE/obs-build.git edit for the target git source's URL edit _service - <param name="url">git://github.com/openSUSE/obs-build.git</param> + <param name="url">https://github.com/cryptodev-linux/cryptodev-linux.git</param> The docs state The default mode of a service is to always run after each commit on the server side and locally before every local build. Iiuc, all that the workspace package dir requires, is project/ package/ _service package.spec and a local osc build ... should trigger the source pull. Since the upstream's git revision is (1) changing frequently, and (2) typically added to the local package's version etc strings, what's the correct form & syntax for the Source: Version: Release: variables, as well as the package name value %setup -q -n XXX in the .spec file be? e.g. edit pgnd-cryptodev.spec %define basepkgname cryptodev Name: pgnd-%{basepkgname} Version: ??? Release: ??? Summary: cryptodev test Group: Productivity/Networking/Security Url: http://cryptodev-linux.org/ License: GPL2 Source: ??? Provides: ??? BuildRequires: kernel-desktop-devel BuildRoot: /tmp/%{basepkgname}-%{version}-build %description cryptodev test install %prep %setup -q -n ??? %build make %install make install DESTDIR="%buildroot" %clean %post %postun %files %changelog One good example would be useful, and helpful if added to the docs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

Re: [opensuse-buildservice] Debian 8.0 and Ubuntu 15.04 got imported
by Dmitriy Perlow 27 Apr '15

27 Apr '15

Builder will freeze when udev is installed for 15.04: https://build.opensuse.org/package/show/home:DarkSS:deb/itmages-dolphin-ext… [ 104s] [363/399] installing udev-219-7ubuntu3 [ 104s] /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found [ 104s] * Stopping the hotplug events dispatcher udevd [ 104s] ...done. [ 104s] * Starting the hotplug events dispatcher udevd [ 104s] ...done. [ 104s] update-initramfs: deferring update (trigger activated) [ 104s] Processing triggers for man-db (2.7.0.2-5) ... [28914s] qemu: terminating on signal 15 from pid 29916 [ 258s] [361/397] installing udev-219-7ubuntu3 [ 259s] /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found [ 259s] * Stopping the hotplug events dispatcher udevd [ 259s] ...done. [ 259s] * Starting the hotplug events dispatcher udevd [ 259s] ...done. [ 259s] update-initramfs: deferring update (trigger activated) [ 260s] Processing triggers for man-db (2.7.0.2-5) ... … wrote after some minutes freezing. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- 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-packaging] How to configure osc subproject to use GCC v5 from devel:gcc by default, for all packages?
by PGNd 27 Apr '15

27 Apr '15

Per advice, moving from opensuse-packaging to opensuse-buildservice, as it's an OBS/OSC-specific question On Sat, Apr 25, 2015, at 07:13 PM, PGNd wrote: > I want to use gcc-5 from > > http://download.opensuse.org/repositories/devel:/gcc/openSUSE_13.2 > > by default in all builds within an osc subproject. > > To use gcc-5 preferentially in local builds, I mod the local ENV with > > export CC="/usr/bin/gcc-5" > export CXX="/usr/bin/g++-5" > ln -sf /usr/bin/gcc-5 /usr/bin/gcc > ln -sf /usr/bin/g++-5 /usr/bin/g++ > ln -sf /usr/bin/gcc-5 /usr/bin/cc > ln -sf /usr/bin/g++-5 /usr/bin/c++ > ln -sf /usr/bin/cpp-5 /usr/bin/cpp > > For OBS builds, I've added the source repo to the subproject's 'meta prj' > > <repository name="openSUSE_13.2"> > <path project="Kernel:stable" repository="standard"/> > + <path project="devel:gcc" repository="openSUSE_13.2"/> > <path project="openSUSE:13.2" repository="standard" /> > <arch>x86_64</arch> > </repository> > > For project-wide setting of gcc == v5.0 for OBS builds, is adding > > %define gcc_version 50 > > to my project's 'meta prjconf' sufficient? > > Do I also need to > > (1) modify the ENV (CC, CXX, ln ...) prior to %configure/%make > &/or > (2) specify BuildRequires: gcc-5 ... ? > -- > To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org > -- 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] Re: [opensuse-packaging] 'osc build' fails @ RPM error: "file not found". spec file's BuildRoot:/%{buildroot} ignored, files instead installed under 'build-root' from ~/.oscrc.
by PGNd 27 Apr '15

27 Apr '15

Per advice, moving from opensuse-packaging to opensuse-buildservice, as it's an OBS/OSC-specific question On Sun, Apr 26, 2015, at 09:50 AM, PGNd wrote: > > > On Sun, Apr 26, 2015, at 05:28 AM, Jan Engelhardt wrote: > > > > Subject : Re: [opensuse-packaging] 'osc build' fails @ RPM error: "file not > > found". spec file's BuildRoot:/%{buildroot} ignored, files > > instead installed under 'build-root' from ~/.oscrc. > > > > Yes, the spec file BuildRoot is ignored in modern RPM - rpm will > > use a sane default so you don't have to. > > > > Secondly, buildroot inside ~/.oscrc specifies the chroot osc will use, > > not the rpm-level "BuildRoot". That will be in addition. > > Thanks for the hints. It clarified chroot. The 'file not found' issue, for me, remains. > > Apparently > > @.spec "BuildRoot" -> unused > @.oscrc "build-root" != rpm-level "BuildRoot" > @.oscrc "build-root" == OSC chroot dir > > Parameter naming used could certainly be less confusing ... > > The default in ~/.oscrc > > #build-root = /var/tmp/build-root/%(repo)s-%(arch)s > > is easily modified, and, as mentioned, correctly defines the chroot location.; nothing in the ./<package>.spec affects the chroot. > > Thanks, that clears that up. > > As for the actual BuildRoot ... > > The docs at > > https://en.opensuse.org/openSUSE:Specfile_guidelines > ... > Metadata Tags > The BuildRoot tag should always be used, even if newer rpms override it anyway. The preferred path is %{_tmppath}/%{name}-%{version}-build. > ... > > hint at the possibility of rpm override. Also raises the question of why it "always" needs to be added if it's completely overridden & ignored. > > Removing > > BuildRoot: ... > > from the <package>.spec results in NO error or warning on exec of 'osc build ...' > > I've now setup my local osc env as > > obs workspace: /usr/local/src/obs_workspace > @ ~/.oscrc > build-root = /usr/local/src/obs_workspace/build-chroot/%(package)s > packagecachedir = /usr/local/src/obs_workspace/build-packagecache > > With that, the package I'm working on is found @ > > /usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux > cryptodev-linux-1428749261.da73010.tar.gz > cryptodev-linux.spec > _service > > Exec of 'osc build ...' now reports > > [ 0s] Using BUILD_ROOT=/usr/local/src/obs_workspace/build-chroot//usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux/cryptodev-linux > > It appears %(package)s expands as > > /path/to/obs/workspace/home:<user>:<project>/<package>/<package> > > (1) "<package>/<package>" seems wrong > (2) The prepended '/path/to/obs/workspace' seems completely unncessary > > I'd hope %(package)s would expand simply as > > <package> > > so that, as provided as example in ~/.oscrc, the form > > /srv/oscbuild/%(repo)s-%(arch)s-%(project)s-%(package)s > > would NOT expand to > > [ 0s] Using BUILD_ROOT= > /usr/local/src/obs_workspace/build-chroot/openSUSE_13.2-x86_64-home:pgnd:pgnd-stack-/usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux/cryptodev-linux > > but to a more sane > > /usr/local/src/obs_workspace/build-chroot/openSUSE_13.2-x86_64-home:pgnd:pgnd-stack-cryptodev-linux > > Simply avoiding that confusion for the moment, ~/.oscrc > > - build-root = /usr/local/src/obs_workspace/build-chroot/%(package)s > + build-root = /usr/local/src/obs_workspace/build-chroot/%(project)s > > returns > > [ 0s] Using BUILD_ROOT= > /usr/local/src/obs_workspace/build-chroot/home:pgnd:pgnd-stack > > which is more manageable. That's sorted, for now. > > With the setup above, and a .spec, unchanged from above, of > > %prep > %setup -q -n %{name}-%{version} > make clean > > %build > gcc -v > export CXXFLAGS+=" -std=c++11" > make V=1 %{?_smp_mflags} > > %install > make DESTDIR=%{buildroot} install > > %clean > rm -rf %{buildroot} > > %files > %defattr(-, root, root) > /usr/include/crypto/cryptodev.h > > exec of 'osc build ...' fails > > ... > [ 47s] Processing files: cryptodev-linux-1428749261.da73010-0.x86_64 > [ 47s] error: File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h > [ 47s] > [ 47s] > [ 47s] RPM build errors: > [ 47s] File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h > > The buildroot was: /usr/local/src/obs_workspace/build-chroot/home:pgnd:pgnd-stack > > This error appears INsensitive to 'make DESTDIR=...' above. If > > - make DESTDIR=%{buildroot} install > + make install > > exec still fails with the identical > > [ 42s] Processing files: cryptodev-linux-1428749261.da73010-0.x86_64 > [ 42s] error: File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h > [ 42s] > [ 42s] > [ 42s] RPM build errors: > [ 42s] File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h > > The buildroot was: /usr/local/src/obs_workspace/build-chroot/home:pgnd:pgnd-stack > > The OP'd question remains, > > (1) What in the spec file needs to change so that the build process finds the built file in the correct buildroot? > -- > To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0