June 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] [PATCH] Add --build-abuild-id to osc and build and add --map-repo to osc
by David Greaves 22 Feb '10

22 Feb '10

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..."

3 5

[opensuse-buildservice] Import build service packages into git
by Andreas Gruenbacher 21 Aug '09

21 Aug '09

Hello, I have been working on an import tool from the build service into git repositories; the result seems to be basically working now. It is available as: home:agruen:Factory/bsgit The git repository is available at: http://git.opensuse.org/?p=people/agruen/bsgit.git Exporting changes into the build service is not supported yet, but it's a start. Integration into osc also hasn't happened, yet. The tool tries to be nice to the server and not request the same data over and over again. Still, when fetching a package, this retrieves all the package's revisions unless you create a shallow copy using bsgit's --depth=N option. So please do not blindly fetch huge packages with a long history just to see what happens. (What would happen is pretty clear -- I would get into troubles with the build service maintainers!) Here is how to use bsgit: $ mkdir stuff $ cd stuff $ git init $ bsgit fetch home:agruen:Factory bsgit Fetching home:agruen:Factory/bsgit (1) Fetching home:agruen:Factory/bsgit (2) Branch 'bsgit' created. $ git branch -a * bsgit remotes/api.opensuse.org/home/agruen/Factory/bsgit $ bsgit pull Fetching home:agruen:Factory/bsgit (3) Branch 'bsgit' updated. $ bsgit fetch Already up-to-date. Observe that bsgit created a remote branch with a long name that encodes the server, project, and package. This is the state of the package in the build service. A local branch, 'bsgit', tracks that remote branch. You may make changes on the local branch. When you fetch a package, this will leave the local branch alone (except for creating it when it doesn't exist). A pull does a fetch, followed by a rebase of the local branch. (It doesn't do a merge because we will not be able to export merges to the build service anyways, at least not with the current backend.) When bsgit detects a source link, it creates a remote branch for the target package as well (i.e., the package linked to), and it expands the source link. Source links are expanded against the revision of the target package that they were *created* against. Very unfortunately, the build service backend does not record the revision it creates a source link against. Until that is fixed (and I hope soon!), some guessing is involved, and some source links may be expanded against the wrong revision. Here is a source link example: $ bsgit clone home:coolo:branches:home:darix:Factory FastCGI Fetching openSUSE:Factory/FastCGI (1) Fetching openSUSE:Factory/FastCGI (2) Fetching openSUSE:Factory/FastCGI (3) Fetching home:darix:Factory/FastCGI (1) Fetching home:coolo:branches:home:darix:Factory/FastCGI (1) Fetching home:coolo:branches:home:darix:Factory/FastCGI (2) Branch 'FastCGI' created. $ git branch -a * FastCGI remotes/api.opensuse.org/home/coolo/branches/home/darix/Factory/FastCGI remotes/api.opensuse.org/home/darix/Factory/FastCGI remotes/api.opensuse.org/openSUSE/Factory/FastCGI Cheers, Andreas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 15

[opensuse-buildservice] Extreme waste of space by source RPMs
by Peter Poeml 11 Jul '09

11 Jul '09

Hi, we waste extreme amounts of space on our download server (and on the mirrors) by the way we publish source RPMs. The source package is published in every repository, so it can be duplicated considerably. For instance, an Apache httpd source package is 5.3 MB, but altogether they occupy more than the ten-fold: # du -sch repositories/Apache/openSUSE_11.1/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/openSUSE_11.1/src/apache2-2.2.11-10.1.src.rpm 5.3M total # du -sch repositories/Apache/*/src/apache2-*.src.rpm 5.3M repositories/Apache/CentOS_5/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/Fedora_10/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/Fedora_9/src/apache2-2.2.11-10.1.src.rpm 5.2M repositories/Apache/Mandriva_2008/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/openSUSE_10.3/src/apache2-2.2.11-10.1.src.rpm 5.2M repositories/Apache/openSUSE_11.0/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/openSUSE_11.1/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/openSUSE_Factory/src/apache2-2.2.11-10.2.src.rpm 5.3M repositories/Apache/RHEL_5/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/SLE_10_server_database_postgresql/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/SLE_10/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/SLE_11/src/apache2-2.2.11-10.1.src.rpm 5.3M repositories/Apache/SLES_9/src/apache2-2.2.11-10.1.src.rpm 68M total (This probably being a rather harmless example, but illustrative.) To set this in perspective, I estimate that 25-50% of space might be wasted. Let's look at some numbers: 98M repositories/Apache/*/src 342M repositories/Apache 9M repositories/home:/poeml/*/src 18M repositories/home:/poeml 22G repositories/games/*/src 50G repositories/games Wow, it's even worse than I thought... What can we do about this? From my understanding, each of the source rpms could be used to achieve the same build result. (Or isn't that the case?) The source RPMs should be published once only, if at all. What do you think? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

7 8

[opensuse-buildservice] Hermes for local OBS
by Luke Imhoff 08 Jul '09

08 Jul '09

I just upgraded our local version of OBS to 1.5 and I'd like to get Hermes setup for notifications, but besides a few lines in BSConfig.pm.template I can't find any mention of how to get Hermes and set it up. I found the source at https://forgesvn1.novell.com/svn/opensuse/trunk/infrastructure/hermes/, but is that it? Do I have to make rpms myself or did I just miss where they are? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] Mandriva_2009 problem: error: Package already exists: %package debug
by Marcin Wojdyr 02 Jul '09

02 Jul '09

Hi, I have a simple package that builds on all RPM-based distros in OBS but Mandriva_2009. I have debuginfo enabled globally, perhaps that's the reason. I get this error on both i586 and x86_64: + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:wojdyr/Mandriva_2009/2005528086e7d471f208a74a…' --eval %suse_insert_debug_package /usr/src/rpm/SOURCES/xylib.spec error: Package already exists: %package debug The package is here: https://build.opensuse.org/package/show?package=xylib&project=home%3Awojdyr Thanks, Marcin -- Marcin Wojdyr | http://www.unipress.waw.pl/~wojdyr/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] Headers for kernel module
by Matwey V. Kornilov 01 Jul '09

01 Jul '09

Hi, We develop kernel module for the interface for our scientific devices. We have to provide headers of the module, because they provide ioctl's for user-space software. Unfortunately I didn't find any information about how to do it correctly. The first way is to put headers into /usr/include/linux tree. The second way is to put all of the sources into /usr/src/kernel- modules tree. Which way is the correct for 3th-party module? What name is correct for the '-devel' rpm package of kmp? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Why is an empty linked package an error?
by Luke Imhoff 30 Jun '09

30 Jun '09

Why does OBS consider an empty linked package an error? If I can check out an empty package to upload source, why I can't I checkout a link to that package and expand it to an empty directory? This comes up for our internal use cases where a developer wants to check that a new package builds in all the distros that are going to link in the package before checking it in. Right now they have to upload some file to the linked to package first so the linking package can be checked out to do an osc build locally. This is more a design philosophy question as I can easily change osc to ignore the error (or change the server to not treat it as a error). It just seems that if you think of the link as a symlink (with versioning) to a directory then you should be able to checkout an empty directory just the same as a directory with contents. Am I missing something in the design that makes this analogy not accurate? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] MonoOSC annouce
by Petit Eric 30 Jun '09

30 Jun '09

Hi After testing and use MonoOSC during several day , we are happy to annouce a stable release of MonoOSC(MonoOSC-1.0.1.9-30.1) when running with Mono >=2.3 Aviable here http://software.opensuse.org/search?baseproject=ALL&p=1&q=monoosc or at sourceforge svn . Also i just added a new "gadget" feature, show/hide panels : http://picpaste.com/ShowHide.png This make it more easy to read. People who like MonoOSC can use the folowing form (all fields are optionals :-)) : http://monoosc.sourceforge.net/MonoOSCSign.php you will find some info of MonoOSC herer : http://monoosc.sourceforge.net/ and OBS : https://build.opensuse.org/ -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] debtransform patches
by Lubos Lunak 30 Jun '09

30 Jun '09

Hello, I've used the debtransform functionality of the buildservice and I'll like to propose the two attached patches: 1) Debian-based distros require the tarball to be .tar.gz , which is annoying with cross-distro packaging. This patch adds support for using .tar.bz2 or .zip and debtransform converts the archive to .tar.gz , in addition to renaming it as it does now. I've tested this locally with osc build and it seems to work fine. If this is accepted, can you give me an estimate for when it gets deployed? It'd save me a bit of writing in a howto, but I don't insist :). 2) Applying patches using debian.series has a different default for the -p argument of patch. While .spec defaults to -p0, debtransform defaults to -p1. This is again annoying with cross-distro packaging. This is a backwards-incompatible change, but I would consider this to be a bugfix and I expect there aren't many packages that rely on the default in debtransform now, because of it not being consistent with .spec . -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak(a)suse.cz , l.lunak(a)kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz

3 6

[opensuse-buildservice] dead-lock in BS (error saving package: value of develpackage, ...)
by Petr Mladek 30 Jun '09

30 Jun '09

Hi, I am completely lost!!! I tried to upload OOo-3.1.1-alpha2 sources into the project OpenOffice_org:UNSTABLE. I got many curious errors like: --- cut --- Checking OpenOffice_org-bootstrap... Sending ooo310-m14-bootstrap.tar.bz2 Sending ooo-build-3.1.0.98.2.tar.gz Sending OpenOffice_org-bootstrap.changes Sending OpenOffice_org-bootstrap.spec Deleting ooo-build-3.1.0.98.1-kde4-subpackage.diff Deleting ooo-build-3.1.0.98.1.tar.gz Deleting ooo310-m13-bootstrap.tar.bz2 Server returned an error: HTTP Error 400: Bad Request error saving package: value of develpackage has to be a existing package (packag e 'OpenOffice_org-bootstrap' does not exist) Transmitting file data --- cut --- Why? 'OpenOffice_org-bootstrap' exists. In addition, 'OpenOffice_org-bootstrap-devel' does not exists, so what is it complaining about? --- cut --- Checking OpenOffice_org-libs-core... Sending ooo310-m14-libs-core.tar.bz2 Sending OpenOffice_org-libs-core.changes Sending OpenOffice_org-libs-core.spec Deleting ooo310-m13-libs-core.tar.bz2 Server returned an error: HTTP Error 400: Bad Request error saving package: value of develpackage has to be a existing package (packag e 'OpenOffice_org-libs-core' does not exist) Transmitting file data --- cut --- Both OpenOffice_org-libs-core and OpenOffice_org-libs-core-devel exists. Why is it complaining? !!!! IMPORTANT: !!!! I uploaded all the package sources in a script. The second package source was "OpenOffice_org-artwork". It is a really ugly package. Only the "OpenOffice_org-artwork-devel" package exists. It is possible that it caused everything. Why are not allowed -devel-only packages? Why did it blocke the other packages? ------ It is even worse. The packages got broken. I am not able to commit them again because they are not longer up-to-date (according to osc). I am not able to check out the older version, for example: --- cut --- pmladek@walk:/prace/OOo/bs> osc co OpenOffice.org\:UNSTABLE/OpenOffice_org-boots A OpenOffice.org:UNSTABLE/OpenOffice_org-bootstrap A OpenOffice.org:UNSTABLE/OpenOffice_org-bootstrap/OpenOffice_org-bootstrap-r A OpenOffice.org:UNSTABLE/OpenOffice_org-bootstrap/OpenOffice_org-bootstrap.c A OpenOffice.org:UNSTABLE/OpenOffice_org-bootstrap/OpenOffice_org-bootstrap.s A OpenOffice.org:UNSTABLE/OpenOffice_org-bootstrap/ooo-build-3.0.0.10-extensi Server returned an error: HTTP Error 404: Not Found ooo-build-3.1.0.98.1-kde4-subpackage.diff: no such file --- cut --- Well, it helps to remove any file by the UI, to unblock this no-such-file-error. But I am still not able to commit new version. I tried to add fake -artwork package to make it happy but I am not able to sommit it into BS. It looks like a real deadlock. Could you please help me? -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4