March 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] [PATCH 1/2] [backend] Add support for xz compressed tarballs
by Hector Oron 19 Mar '12

19 Mar '12

Debian sources are also compressed in xz format. Signed-off-by: Hector Oron <hector.oron(a)collabora.co.uk> --- src/backend/bs_publish | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/backend/bs_publish b/src/backend/bs_publish index dabda6f..bc57a95 100755 --- a/src/backend/bs_publish +++ b/src/backend/bs_publish @@ -1034,7 +1034,7 @@ sub publish { $p = "$bin"; } elsif ($bin =~ /\.raw(:?\.install)?(:?\.sha256)?$/) { $p = "$bin"; - } elsif ($bin =~ /\.tar\.(:?gz|bz2)(:?\.sha256)?$/) { + } elsif ($bin =~ /\.tar\.(:?gz|bz2|xz)(:?\.sha256)?$/) { $p = "$bin"; } elsif ($bin =~ /\.ovf(:?\.sha256)?$/) { $p = "$bin"; -- 1.7.9.1 -- 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] A collaboration problem
by Dave Plater 19 Mar '12

19 Mar '12

I'm continually coming across a collaboration problem with spec files and changes files when working on a package in my home:plater projects and sub projects in which I keep the packages where I'm the primary maintainer mostly from multimedia. When I wish to check a package through the devel project to factory, I find that another users changes to the files are marked for deletion. The only way I can work around this is to delete my package and rebranch it or checkout the changed files from the devel project to my home project package's local copy and then redo my changes. In the past this problem caused a conflict which was even more complicated to repair so this is definitely an improvement. Isn't there an easier way to merge my changes with the other ones? There's also a problem that came up where I resubmitted a package to factory when it had been fixed by another user and submitted already with no notification to me. I'm a busy maintainer and struggling to catch up after an absence and this involves working on more than one package at once, currently blender and lilypond which on a difficulty scale of 1 to 10 lilypond must rate at 9 and blender at least deserves a 7. One other feature from the old style build service that I would like to see returned is the ability to copy a tarball directly from upstream without involving source services. I have a real maximum upload speed of 64K bits per second but can download at 384K so you can understand why I need this feature, the new blender tarball took a long time to check in. Currently the copy from url service causes problems with factory. Dave -- 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] buildhost stuck
by Wolfgang Rosenauer 16 Mar '12

16 Mar '12

Hi, as OBS is very busy these days and fails to finish projects within a few days I've noticed in the status monitor that build25 seems to be stuck. build26 also looks strange to me. Thanks, Wolfgang -- 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] web frontend, "Build Status" refresh button broken
by Ruediger Meier 16 Mar '12

16 Mar '12

Hi, since yesterday the "Build Status" refresh button on package overview page does not work anymore. cu, Rudi -- 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] subscribe
by Xaver Wurzenberger 15 Mar '12

15 Mar '12

-- 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] copy/move package inclusive commit history
by Ruediger Meier 14 Mar '12

14 Mar '12

Hi, is it possible to copy or move a package between projects without losing commit history? cu, Rudi -- 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] Mandriva_2010.1 ctdb builds help needed
by Lars Müller 14 Mar '12

14 Mar '12

Hi, the build of ctdb fails for Mandriva 2010.1 in the OBS network:samba:STALE repository. The log ends with ### log begin Requires(postun): /bin/sh Requires: bash libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.3.2) libc.so.6(GLIBC_2.4) rtld(GNU_HASH) Processing files: ctdb-devel-1.2.29-38.1 Finding Provides: /usr/lib/rpm/mandriva/filter.sh ' ' ' ' '/home/abuild/rpmbuild/BUILDROOT/ctdb-1.2.29-38.1.i386' /usr/lib/rpm/mandriva/find-provides error: line 1157: Version required: + added a debugging option --node-ip error: Failed to find Provides: Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(VersionedDependencies) <= 3.0.3-1 RPM build errors: line 1157: Version required: + added a debugging option --node-ip Failed to find Provides: ### log end The full log is available from https://build.openSUSE.org/package/live_build_log?arch=i586&package=ctdb&pr… Maybe one of you has seen this before and give use a hint what's going wrong here. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

2 1

[opensuse-buildservice] New gem requirements on master
by Stephan Kulow 14 Mar '12

14 Mar '12

Hi, I just wanted to mention, that I merged my branch into master now that 2.3 release is more concrete. This means you need some more rubygems if you work with git. openSUSE:Tools should have them all of course. Greetings, Stephan -- 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] Automated way to generate .changes from RPM spec file?
by Gerrit Beine 13 Mar '12

13 Mar '12

Hi folks, I'd like to migrate all my packages in Build Service to use changes files instead of the spec file section. Is there a tool for this or do I have to do it manual? Thanks & best regards Gerrit -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

Re: [opensuse-buildservice] Reworking the software search, part II
by "Stefan Brüns" 12 Mar '12

12 Mar '12

Am 03/12/12, schrieb Thomas Schmidt <tom(a)opensuse.org>: > Hi, > thanks for your feedback regarding our mockups for the software search. We implemented a > working prototype which now also contains a search form. > > Please check the new search at: > http://software.opensuse.org/search/find > and see an example app page here: > http://software.opensuse.org/package/kopete > > Please let me know what you think of the current state. Hi Thomas, really looks nice and is a vast improvement to the old search page. A few comments: 1. How is the distribution determined which is chosen for the large "Direct Install" button? Is there some possibility to select this, I would even be willing to accept a Cookie for this ... 2. Is it possible to expand the section for the currently chosen distribution? Otherwise the fact there are several good choices for the package might be overlooked. 3. CSS: - the package description has: "white-space: pre-line" - intended? - If a project has many repositories (e.g. KDE:Unstable:Playground), formatting breaks, IMHO the repositories should be a single (multiline) block 4. Regarding projects with many repositories, the package download links can not be differentiated easily (at least firefox elides the interesting part of the link). Otherwise, great work! Regards, Stefan -- 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] mozilla:yasm - Broken signatures
by Claudio Freire 12 Mar '12

12 Mar '12

I was trying to update firefox on an old 11.1 installation. I found that the mozilla project in OBS contains 11.1, so I set it up and started updating. The "yasm" in that project is failing to install (only yasm), complaining about bad signatures. I did a full refresh to make sure I had the latest GPG keys (I had some expired ones), and it's still broken. Can someone trigger a rebuild please? (it might get fixed with a rebuild). -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] using build directly vs. post-build-checks
by Frank Lichtenheld 12 Mar '12

12 Mar '12

Hi. When building with OBS, not only the BuildRequires seem to get installed in the build chroot, but also the hardcoded Requires from the spec file. This is necessary for at least the post-build-checks to work correctly. When building with "build" directly (i.e. using build's internal expanddeps script to resolve BuildRequires), the Requires do not seem to get installed and so the post-build-checks fail. Would you consider that a bug? I.e. should the default behavior be changed to install Requires, too? Or should a new command line option be introduced to control the behavior? I'm happy to provide a patch for either solution. Or am I missing something completely and this should work already? Gruesse, Frank -- Frank Lichtenheld frank.lichtenheld(a)sophos.com | Lead Engineer Astaro GmbH & Co. KG - a Sophos company | www.astaro.com | www.sophos.com Phone +49-721-255-16-362 | Fax -200 | Mobile +49-174-1748211 Amalienbadstr. 41/ Bau 52 | 76227 Karlsruhe | Germany Astaro GmbH & Co. KG - a Sophos company, Commercial Register: Mannheim HRA 702710, Headquarter Location: Karlsruhe, Represented by the General Partner Astaro Verwaltungs GmbH Commercial Register: Mannheim HRB 708248 Amalienbadstr. 41/ Bau 52 | 76227 Karlsruhe | Germany Executive Board: Gert Hansen, Markus Hennig, Jan Hichert, Günter Junk, Dr. Frank Nellissen -- 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] different packages installed in local build chroot than in OBS build
by Uwe Geuder 09 Mar '12

09 Mar '12

Hi! As already initially discussed on IRC I have observed that my local chroot build environments get different packages installed than the build environment on the OBS workers. I think the discussion there confirmed my assumption that the local chroot should have exactly the same contents as the build environment on the host[1]. Both OBS and my local environment are just chroot, no virtualization[2]. I have a hierarchy (<path> in buildinfo) of 4 projects, the "lowest" one has a project configuration. I'm using the highest one and there I see the difference in the build roots. The main properties are: - worker architecture is x86_64, same for my local machine - target architecture is arm, all execection uses binfmt_misc and qemu-arm-static The differences are related to some preinstalls. The preinstalls are defined in the project configuration of the "lowest" project, e. g. like this %if %speedbash Preinstall: bash-x86-arm ncurses-libs-x86-arm Runscripts: bash-x86-arm %endif (This is just one example, there are several similar cases in the whole project config) This configuration is copied correctly into .osc/_buildconfig... when I run osc build. However, it appears that on the OBS the %speedbash macro is true (resulting in some x86 preinstalls), in my local builds it must be false (these preinstalls are missing). So I end up with different preinstalls locally than remote. The %speedbash macro depends on other %if macros, but in the beginning of the chain some macro must just be initialized differently on the worker host than locally. How can I find out where these macros are actually intialized and where the difference comes from? When looking at http://en.opensuse.org/openSUSE:Build_Service_prjconf, I read: > The prjconf denotes the (build) configuration of a project. The main > part of this file (/usr/lib/build/configs/$distro.conf) is the > definition of the build environment So do these conf files actually play a role in the initialization of the macros? If yes, is it the one on the host or the one in the chroot? I don't really understand how that should work: We are talking about the initialization of the chroot, so I can't see how the conf files from inside the chroot could be used, because they are not there yet when we need to decide our preinstalls. But on the other side if the ones of the host are used, the host could influence the contents of the chroot, contradicting the purpose of the chroot being a well-defined isolated build envoironment. Any explanations to solve this knot are welcome. Or are these conf files for the "second" kind of macros only, which are used by rpmbuild, not those used in the prjconf? Any hints to trace down were the difference is created? I have already tried to debug osc a bit, but at least so far I have not found any place where these macros are handled. When I execute "osc build", is the difference likely to be caused already on the OBS (I don't have any access to the installation than a normal user account) and included e.g. in the buildinfo sent from the OBS to my local build or does the relevant processing happen first locally in my own machine (where I could debug it)? Regards, Uwe Geuder Nomovok Ltd. Tampere, Finland uwe.gxuder@xxxxxxxxxxx (bot check: humans correct 1 obvious spelling error) [1] As far as installed packages are concerned. Of course there will be other differences like the kernel, the amount of memory and a million other parameters that could cause nasty problems if things go really wrong. [2] chroot in OBS is a security risk. This is a private OBS instance in a closed intranet with only "trusted" users. -- 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] Debootstrap as a replacement of debian chroot creation in obs
by Helio Chissini de Castro 07 Mar '12

07 Mar '12

Hi Since we're starting to experiment full OBS build of a debian derivative distro, we detected some faults in the chroot creation related sometimes to scripting and post script runs as order of package install too. So, for our personal test, we decided to replace the internal parts related to dpkg in init_buildsystem ( obs-build ), for a single one common solution to debian and ubuntu, which is debootstrap. First difficulty i found was the lack of debian tools in RPM distros, rendering workers unnefective, so i made a proper rpm for debootstrap, debhelper, autotools-dev and apt ( which i called apt-debian ) to both Fedora and openSUSE. openSUSE need less tools than Fedora, since have package deb which contains dpkg + debhelper. Having this, i was able to replace many parts of init_buildsystem script for two steps: - Generate a proper debian repos locally using apt-ftparchive - Execute debootstrap First step uses an script, that now is limited to test i386 and armhf for our purposes Second uses the buildd option of debootsrap, looking in local already downloaded packages. We already are using it as default in our internal OBS and so far so good, the process shown some progress. It's working in both deb and rpm workers I'm open to opinions, ideas of how far we can go, improve the script and if maybe we can adapt this to upstream in future. You can see the branch of obs-build here: https://github.com/heliocastro/obs-build And all packages in my home:heliochissini on build.opensuse.org https://build.opensuse.org/project/show?project=home%3Aheliochissini []'s -- Helio Chissini de Castro Collabora -- 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] How do I unmark packages as a devel project?
by Dave Plater 07 Mar '12

07 Mar '12

After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either. The problem I attempted to address is a real problem though, there should be a way for a maintainer to lock the package that he's working on, especially before release when there's a lot of activity. Dave -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] add GIT as possible value for URL in spec file
by Tomas Cech 06 Mar '12

06 Mar '12

Hi, I'm using GIT protocol in URL in spec files and I have always warning like this one: evas.x86_64: W: invalid-url URL git://git.enlightenment.org/git/e.git I'd be glad if GIT would be one of correct protocols. What is your opinion here? I'm aware that Enlightenment has it's web page in this case. Thanks Tomas Cech Sleep_Walker

2 1

[opensuse-buildservice] RedHat:RHEL-4 => DISCONTINUED:
by Adrian Schröter 05 Mar '12

05 Mar '12

JFYI, RHEL 4 is out of maintenance. So I copied to the DISCONTINUED: area and will remove the RedHat:RHEL-4 plus all repositories still building against it in the next days. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] where to submit packages for the bug fix update
by Togan Muftuoglu 05 Mar '12

05 Mar '12

hi I'm trying to maintain a package which I have branched using osc mbranch once I fix the issue which project do I send the submitrequest ie in my case the package to be fixed is for openSUSE 12.1 according to <http://en.opensuse.org/openSUSE:Package_maintenance#Submit_your_changes> I should osc sr openSUSE:12.1:Update:Test not being sure I did via webui and it submitted to openSUSE:Maintenance which for some reason doesn't feel right Thanks Togan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] Cross compilation dependency handling
by Carsten Munk 05 Mar '12

05 Mar '12

Hi, One of the discussion points about my SB2-OBS patch is that we ought to work towards a common strategy for denoting these special kind of dependencies in prjconf instead of using "SB2install" "CBinstall" etc. Daniel Gollub suggested that we work with N amount of 'sysroots' and N rpm databases and I tend to agree. Right now in SB2 I distinguish between host (/) and target /target, but it might be more flexible to do with N targets instead. The question is of course, can we effectively work with multiple dependency trees (maybe even across schedulers?) within the current code and how do we do it best? Adrian suggested something like Preinstall($hostarch) to indicate that this needs to be preinstalled on host architecture. My suggestion would be perhaps to indicate through configuration where to put things, for example, Roots: host=/ armv7l=/opt/cross/armv7l, etc, so we can do dynamic labeling and telling what location on the build filesystem things should go in. What are your thoughts? BR Carsten Munk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 9

[opensuse-buildservice] Reworking the software search page
by Thomas Schmidt 05 Mar '12

05 Mar '12

As part of the current boosters sprint[1] which aims at integrating the appstream[2] project into our distribution we would like to enhance the web view on our packages at software.o.o/search. With the final target of an web-based appstore we began thinking of how to display a package (app) to the user. The challenge is to make available the matrix of different OS versions, repositories and package versions in a clear way while making it easy for the standard user to get the latest stable version for his OS without getting confused. We already have a mockup available: http://dl.dropbox.com/u/294274/software.o.o/package-view.png Feedback appreciated :-) Greetings [1] https://trello.com/board/appstream/4f156e1c9ce0824a2e1b8831 [2] http://distributions.freedesktop.org/wiki/AppStream -- Thomas Schmidt (tom [at] opensuse.org) openSUSE Boosters Team "Don't Panic", Douglas Adams (11.03.1952 - 11.05.2001) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 13

[opensuse-buildservice] Can we build for SLE-11-SP2 yet
by Magnus Lewis-Smith 02 Mar '12

02 Mar '12

Are the SLE-11 SP2 repositories available for building against yet? We have a local instance OBS server, with projects configured as ... <repository name="SLE_11_SP1"> <path project="openSUSE.org:SUSE:SLE-11:SP1:Update" repository="standard"/> <path project="openSUSE.org:SUSE:SLE-11:SP1" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="SLE_11_SP2"> <path project="openSUSE.org:SUSE:SLE-11:SP2" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> ... The SLE_11_SP1 repository builds are OK, but as yet there is nothing happening in the SLE_11_SP2 repo. It doesn't even appear on the overview/build status page. Incidentally, how are the SLE repositories configured? The SUSE:SLE-11:SP1 project contains no packages -- so how do they get "used for build"? Regards Magnus Lewis-Smith -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] OBS 2.3 state & openSUSE Maintenance Rollout meeting minutes
by Adrian Schröter 02 Mar '12

02 Mar '12

present: lnussel, bbrunner, meissner, dirk, rommel, mls, saschpe, adrian Rollout plan ============ * switch openSUSE maintenance to OBS mechanics and new model in two steps. 8th March: switch openSUSE:11.4 to new mechanism ================================================ - define openSUSE:11.4:Update as update project - disable update project syncing from euklid - disable openSUSE in SWAMP - reimport all released updates - convert running updates into incidents 15th March: new maintenance workflow for packagers ================================================ - send mail describing the change and pointing to documentation some days ago - find and update wiki pages about maintenance and point to: - Update OBS maintenance documentation: http://doc.opensuse.org/products/draft/OBS/obs-reference- guide_draft/cha.obs.maintenance_setup.html Blocking wishes =============== * openSUSE Maintenance issues - update feeder must work AI: dirk - update test channel generation must work (should be fixed with new deployment) * open incident ordering - no patchinfo exists - patchinfo rating - ready to release, but no release request - release request creation date AI: saschpe * Handle project wide requests better in webui like maintenance requests for entire projects. AI: adrian/sascha, clarify how to solve it either during request creation or in webui. * patchinfo issue listing needs option documented=false Done in api/backend, webui needs to take care on incident overview page. Optional wishes for 2.3 ======================= * osc jobhistory should contain delta jobs AI: mls * special page for maintenance_incendent accept: - show existing incidents which contains added issues - offer to merge into incident * Even more speedup of incident overview page AI: saschpe * osc rq watch command to wait for changing results * implement osc prjres --watch * enhance createrepo for delta downloads AI: sascha * Show binaries in release requests view * Show issue descriptions in request view * mbranch api return value shall list all packages Implemented requests ==================== * webui incident overview => show patchinfo summary instead of project summary => show package names of incident => show all incidents => show declined release requests AI: saschpe * Add support to fetch CVE descriptions from upstream AI: adrian * patchinfo build result must be broken without package -> openSUSE:Maintenance:288 AI: mls * broken flag to document to define "stopped" with a text comment => build result must be broken AI: adrian * reimport issues from bugzillas to fix URL's AI: adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] %make_install in Evergreen_11.1
by Cristian Morales Vega 01 Mar '12

01 Mar '12

Hi There would be some way to make spec files without the BuildRoot tag and using the %make_install macro build against Evergreen_11.1? I have been playing with the prjconf but I was unable to define the macro only for pre-11.2 distros (no %if's after "Macros:"?) Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1