openSUSE Build Service November 2009

buildservice@lists.opensuse.org

62 participants
94 discussions

[opensuse-buildservice] openSUSE 10.3 runs out of maintenance

by Adrian Schröter

Hello, is usual, openeSUSE 10.3 runs out of maintenance and I will remove all repos building against it in OBS. openSUSE:10.3 project has been moved to DISCONTINUED: namespace as announced a while ago. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 years, 9 months

[opensuse-buildservice] osc help

by Karl Eichwalder

osc help lists commands alphabetically. Please, sort them by topic as rpm, zypper, and similar tools do. [Yes, svn also sorts alphabetically, but that list is not that huge.] -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 4 months

[opensuse-buildservice] _buildinfo inconsistency

by Michal Marek

Hi, $ osc api /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t1 $ osc api -m POST -d 'Name: test' \ /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t2 $ diff -u t[12] --- t1 2009-09-08 15:56:54.000000000 +0200 +++ t2 2009-09-08 15:56:57.000000000 +0200 @@ -1,13 +1,5 @@ <buildinfo project="home:michal-m" repository="openSUSE_11.0" package="nafe" downloadurl="http://download.opensuse.org/repositories"> <arch>x86_64</arch> - <srcmd5>4f263493abe82e1f59603b5a5642b4a0</srcmd5> - <verifymd5>4f263493abe82e1f59603b5a5642b4a0</verifymd5> - <rev>2</rev> - <specfile>nafe.spec</specfile> - <file>nafe.spec</file> - <versrel>0.1-2</versrel> - <bcnt>2</bcnt> - <release>2.2</release> <debuginfo>0</debuginfo> <bdep name="aaa_base" preinstall="1" runscripts="1" notmeta="1" version="11.0" release="79.1" arch="x86_64" project="openSUSE:11.0" repository="standard" /> <bdep name="acl" preinstall="1" notmeta="1" version="2.2.45" release="40.1" arch="x86_64" project="openSUSE:11.0" repository="standard" /> Because of the missing <release>2.2</release> element, osc doesn't substitute release numbers when building locally. Should osc work around this (get the buildinfo a second time to find out the release) or should the backend be fixed (bs_repserver, function getbuildinfo(), that doesn't fetch the required pieces when called from getbuildinfo_post())? Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 6 months

[opensuse-buildservice] [PATCH] Add --build-abuild-id to osc and build and add --map-repo to osc

by David Greaves

When building locally in a qemu/chroot and debugging I find I want to edit the files in the chroot from my desktop gui editor but they're all owned by 399:399. This pair of patches allows me to set the uid:gid to match my local user and eases this process. usage is: build --build-abuild-id uid:gid or more usually: osc build --build-abuild-id 500:500 osc also accepts (and extends the default) .oscrc settings: build-abuild-id = 500:500 It only supports numeric ids. The osc patch also adds --map-repo to aggregatepac which allows repository mapping(s) to be given as SRC=TARGET[,SRC=TARGET] eg, a real usage: osc aggregatepac -m MerStable_Debian_5.0=Mer0.13_Debian_5.0,MerStable_Ubuntu_9.04=Mer0.13_Ubuntu_9.04 Maemo:Mer:0.13:HW:N8x0 advanced-power Maemo:Mer:Stable:HW:N8x0 https://build.opensuse.org/package/view_file?file=_aggregate&package=advanc… David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..."

10 years, 9 months

[opensuse-buildservice] first draft of a dod implementation

by Marcus Hüwe

Hi, here's a first (incomplete!) version of a patch which adds dod support to the backend. Before I implement the missing parts in bs_repserver I just want to know if this is the right way to do it (especially the parts in bs_sched and BSSolv.xs (the implementation in the repserver is just a quick hack to test the scheduler)). Note: currently it doesn't use the changes which were committed in r9280 because the scheduler rescans the repo directly if the repserver fetched new packages (although this might be problem in case the build finishes before the scheduler finishes the reposcan/processed the new event - I need to check if this can happen...). Feedback is welcome:) Marcus

10 years, 11 months

[opensuse-buildservice] faster web interface

by Stephan Kulow

Hi, I commited my port now to trunk and deployed it on build.opensuse.org. While it was online on stage, only a fraction of the problems were found the deployment on the real thing showed in the first hour ;) Anyway, the issues seen are fixed and in case you see more, don't hesitate to reply. For most things I get a direct email with the details of the problem, but for more subtle problems it might be in order to report them. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years

[opensuse-buildservice] Suggestion on the 'build log view'

by Dominique Leuenberger

Good morning, While checking some of 'my' failed packages, I came up with an idea (that could help) in the webinterface. Typically I use the 'build monitor' to identify failed packages, check the buildlog and take actions. Once in a while the identified problem is not due to the package itself but due to buildhost errors and the 'solution' for those is to just trigger a rebuild. Unfortunately, to do this, I have to change to the package view, identifying the specific failed target/arch and trigger a rebuild (no need to rebuild all archs for one failed host). I think it could be really handy to have at the end of the build log a 'trigger rebuild for this package / repo / arch. An option otherwise could be to detect known build failures like: copying packages... reordering...done booting XEN kernel ... xm create -c /var/run/bsworker_16/build/xen.conf name=build:16_root memory=750 disk=phy:/dev/abuild/16_root,hda1,w disk=phy:/dev/abuild/16_swap,hda2,w extra=quiet init=/.build/build panic=1 console=ttyS0 Using config file "/var/run/bsworker_16/build/xen.conf". Error: Device 770 (vbd) could not be connected. Hotplug scripts not working. argh, no buildstatus set, assuming bad build host... and just trigger those packages again. Any thoughts? Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years

[opensuse-buildservice] Hermes Fix: Maintainer versus Bugowner

by Klaas Freitag

Hi, Hermes had the malfunction that the code which gets the maintainer for a package did consider a potential bugowner as well as the maintainer. That might have lead to messages that made you wonder why you get it. I today deployed a fix that only searches the maintainer list. I am sorry for confusion, Klaas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years

[opensuse-buildservice] how to backport kernels

by schoappied

Hi, How do I backport kernels the good way? I want to backport the generic kernel (which is used for i386 and amd64 afaik) and the realtime kernel (image-rt) from Ubuntu karmic/9.10 to Ubuntu jaunty/9.04. 1) I'm not sure which packages I should take? The metapackages, the linux-firmware, just the kernels? (it's for 32 and 64bits) 2) for some packages, for example linux-image-2.6.31-9-rt I get this error: blocked linux-libc-dev Thanks in advance, ~ d -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years

Re: [opensuse-buildservice] Ubuntu backports

by schoappied

I tried to build it this way: http://en.opensuse.org/Build_Service_Tutorial But the build says: nothing provides libjack-dev Itś a build for ubuntu hardy, and libjack-dev is in ubuntu hardy... build log: Error Details: *Errorcode: *unknown *Message: *<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http Very strange... Besides that. I wonder how I could backport this way, but only changing the changelog file... So I do: dget -ux http://that_link/foo.dsc"; and I get these files: phasex_0.11.1-1.diff.gz phasex_0.11.1-1.dsc phasex_0.11.1-1.dsc.asc phasex_0.11.1-1_i386.build phasex_0.11.1-1_i386.changes phasex_0.11.1-1_i386.deb phasex_0.11.1.orig.tar.gz and a folder phasex Can I just edit something in that folder, cp that folder and the above listed files to my new directory with the name of my new package (osc meta pkg -e home:<username> <packagename>) and upload the files? Or should I first build the package and upload for examples these files: phasex phasex_0.11.1-1~8.04derick1.diff.gz phasex_0.11.1-1~8.04derick1.dsc phasex_0.11.1-1~8.04derick1.dsc.asc phasex_0.11.1-1~8.04derick1_i386.build phasex_0.11.1-1~8.04derick1_i386.changes phasex_0.11.1-1~8.04derick1_i386.deb I try to get this clear and find out what the best way is to backport from debian to ubuntu lts ~D -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2009