openSUSE Build Service August 2014

buildservice@lists.opensuse.org

44 participants
45 discussions

[opensuse-buildservice] + char in version
by Dmitry Roshchin 05 Aug '14

05 Aug '14

According to wiki page [1] scm snapshots must use '+' or '.' as version delimiter. But '+' causes error in obs service tar_scm: > Files could not be expanded: service tar_scm failed: > Running /usr/lib/obs/service/tar_scm --url > https://github.com/JuliaLang/julia.git --scm git --versionformat > 0.2.0+git%cd.%h --outdir /lxc.tmp.5012/out Argument --versionformat got an > argument with not supported char. This check was added in git commit [2]. Is '+' char really unsafe? At least osc service localrun works fine. [1] http://en.opensuse.org/openSUSE:Package_naming_guidelines [2] https://github.com/openSUSE/obs-service-tar_scm/commit/acecb041929bc8210c41… -- 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] Is it possible to get a {compressed} list of all packages on the opensuse build service ?
by doiggl＠velocitynet.com.au 05 Aug '14

05 Aug '14

Hello Is it possible to get a {compressed} list of all packages on the opensuse build service ? Can all the packages across openSUSE Build Service be listed. I know this is a long..long list [34,552 project entries] [ 249,332... packages] and it would change over time as packages are added/removed. - Can gzip 9 or similar be use to compress the list. - Where would the {compressed} listing be located ? - Does the build service already produce a list with this content ? Thanks Glenn Say one line per package. formatted like {Project name} package name example: {home:awk2007:scm} dracut {Kernel:stable} kernel-desktop {Kernel:stable} kernel-vanilla .. .. {openSUSE:Factory} lvm2 {openSUSE:Factory} screen -- 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] osc lbl does not recognize apihost
by Olaf Hering 04 Aug '14

04 Aug '14

With osc from openSUSE:Tools, osc build and chroot know about apihost. But lbl does not: ibs lbl SLE_12 x86_64 > x Traceback (most recent call last): File "/usr/bin/osc", line 26, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 60, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 484, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1214, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 5043, in do_localbuildlog 'repo': repo, 'arch': arch} KeyError: 'apihost' build-root = /some/where/%(apihost)s/%(project)s-%(package)s/%(repo)s-%(arch)s Olaf -- 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] Scientific Linux 6: choice error for libjpeg-devel
by Srivats P 03 Aug '14

03 Aug '14

Hi, https://build.opensuse.org/package/show/home:pstavirs:ostinato/ostinato The above package is not building for ScientificLinux 6 due to the below error - have choice for libjpeg-devel needed by qt-devel: libjpeg-devel, libjpeg-turbo-devel As per http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Expansion_err…, I should report this here to get it fixed for everyone. Thanks in advance, Srivats -- 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] OBS Appliance stilll stall doing build
by Lars Nielsen 01 Aug '14

01 Aug '14

Hello I still have a problem with our OBS Appliance. But I have come a little further. I now know that if I try this: /usr/bin/qemu-kvm -no-reboot -nographic -vga none -net none -cpu host -kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/sda panic=1 quiet no-kvmclock nmi_watchdog=0 rw rd.driver.pre=binfmt_misc elevator=noop console=ttyS0 init=/.build/build -m 256 -drive file=/var/cache/obs/worker/root_8/root,if=none,id=disk,serial=0,cache=unsafe -device ide-hd,drive=disk -drive file=/var/cache/obs/worker/root_8.swap,if=none,id=swap,serial=1,cache=unsafe -device ide-hd,drive=swap -smp 1 I get to this point [ 0.075731] NET: Registered protocol family 2 [ 0.076112] TCP established hash table entries: 2048 (order: 3, 32768 bytes) [ 0.076611] TCP bind hash table entries: 2048 (order: 3, 32768 bytes) [ 0.077067] TCP: Hash tables configured (established 2048 bind 2048) [ 0.077514] TCP: reno registered [ 0.077749] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.078164] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.078626] NET: Registered protocol family 1 [ 0.078948] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 0.079369] pci 0000:00:01.0: PIIX3: Enabling Passive Release [ 0.079776] pci 0000:00:01.0: Activating ISA DMA hang workarounds [ 0.080249] Unpacking initramfs... and qemu-kvm thread stalls for 8.5 hours and then terminates. But if I bump the command up to use -m 512 instead I get passed this but get this: [ 0.374929] Waiting for device /dev/sda1 to settle... [ 2.377787] Waiting for device /dev/sda1 to settle... [ 4.385698] Waiting for device /dev/sda1 to settle... [ 6.393584] Waiting for device /dev/sda1 to settle... [ 0.340756] Including oem partition info file [ 0.349662] Searching for boot device... [ 0.353829] Found boot device: /dev/sda [ 0.371520] Filesystem of OEM system is: unknown -> /dev/sda1 [ 0.374929] Waiting for device /dev/sda1 to settle... [ 2.377787] Waiting for device /dev/sda1 to settle... [ 4.385698] Waiting for device /dev/sda1 to settle... [ 6.393584] Waiting for device /dev/sda1 to settle... [ 8.417719] /sbin/init no such file or not executable [ 8.418671] rebootException: reboot in 120 sec... Can anyone help me on from this point because this is actually the only blockade for me now (I hope). Best Regards Lars Nielsen -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service August 2014