January 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] OBS 1.7Beta2 graphs
by Jon Nelson 25 Jan '10

25 Jan '10

Starting a new thread. The graphs on the monitor page aren't working for me. Here is a snippet from the logs.... [I|#25052] * [JOB] acquiring lock on DelayedPlots [D|#25052] Delayed::Job Update (0.6ms) UPDATE `delayed_jobs` SET locked_at = '2010-01-21 15:35:41' WHERE (id = 65 and locked_by = 'delayed_job host:$HOSTNAME pid:25052') [D|#25052] --> direct_http url: #<URI::Generic:0x7fbab8c4af48 URL://$HOSTNAME:80/public/status/history?key=waiting_armv5el&hours=24> [D|#25052] http_do #1: method: GET url: http://$HOSTNAME:80/public/status/history?key=waiting_armv5el&hours=24 [D|#25052] Request took 0.027771 seconds [D|#25052] SQL (0.1ms) BEGIN [D|#25052] Delayed::Job Update (0.3ms) UPDATE `delayed_jobs` SET `updated_at` = '2010-01-21 15:35:41', `locked_at` = NULL, `run_at` = '2010-01-21 15:40:02', `attempts` = 4, `locked_by` = NULL WHERE `id` = 65 [D|#25052] SQL (0.9ms) COMMIT [E|#25052] * [JOB] DelayedPlots failed with ActiveXML::Transport::NotFoundError: <?xml version="1.0" encoding="UTF-8"?> <status code="not_found"> <summary>no route found to match "/index.html" with {:method=>:get}</summary> <details></details> </status> - 4 failed attempts [E|#25052] <?xml version="1.0" encoding="UTF-8"?> <status code="not_found"> <summary>no route found to match "/index.html" with {:method=>:get}</summary> <details></details> </status> -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] [osc] Enhancement request for 'osc prjresults'
by David Haller 23 Jan '10

23 Jan '10

Hello, what's the chance / what would you think of switching x/y in the output of 'osc prjresults', i.e. instead of: pkg1 | pkg2 | | pkg3 . . . repo1 . . . repo2 . . . repo3 to have repo1_arch1 | repo1_arch2 | | repo2_arch1 . . . pkg1 . . . pkg2 . . . pkg3 preferably even repo1_arch1 | repo1_arch2 | | repo2_arch1 . . . pkg1 . . . pkg2 . . . pkg3 0. Is that doable? 1. I'd guess many projects tend to have more packages than repos, and it'd be easier to read that way (or they're still easy to read anyway) and I think it'd be easier to read. (I think it'd already be easier to read with a 9 pkgs / 6 repos w/ 2 archs project, as that's the case where I just thought of this). 2. It'd also match the WUI "project build monitor" layout/"dimensions" Just a thought for a possible "enhancement" ... I might do a few sample 'x/y' switches of output of a couple of (small and large) example projects for all to look at, if asked nicely ;) -dnh -- I have wondered what would be outside the universe. Half a step after "a different kind of nothing", I stopped. -- M. Wiltink -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Extra newlines in base64 passx on SLES 10 (python 2.4.2)
by Luke Imhoff 22 Jan '10

22 Jan '10

When converting an older oscrc that contained a random password, the add_section part that was rewriting the password to be bz2 and base64 encoded died with: Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/osc/babysitter.py", line 46, in run return prg.main() File "/usr/lib64/python2.4/site-packages/osc/cmdln.py", line 300, in main self.postoptparse() File "/usr/lib64/python2.4/site-packages/osc/commandline.py", line 115, in postoptparse override_verbose = self.options.verbose) File "/usr/lib64/python2.4/site-packages/osc/conf.py", line 617, in get_config add_section(conffile, url, user, password) File "/usr/lib64/python2.4/site-packages/osc/conf.py", line 505, in add_section cp.set(url, 'passx', passwd.encode('bz2').encode('base64')) File "/usr/lib64/python2.4/ConfigParser.py", line 640, in set ConfigParser.set(self, section, option, value) File "/usr/lib64/python2.4/ConfigParser.py", line 359, in set sectdict[self.optionxform(option)] = value File "/usr/lib64/python2.4/site-packages/osc/OscConfigParser.py", line 134, in __setitem__ self._add_option(key, val) File "/usr/lib64/python2.4/site-packages/osc/OscConfigParser.py", line 119, in _add_option self._lines.append(OptionLine(optname, line)) File "/usr/lib64/python2.4/site-packages/osc/OscConfigParser.py", line 182, in __init__ self.format(line) File "/usr/lib64/python2.4/site-packages/osc/OscConfigParser.py", line 186, in format key, val = mo.group('option', 'value') AttributeError: 'NoneType' object has no attribute 'group' Looking at the encoded password it was passx = 'QlpoOTFBWSZTWdaogbUAAAWPgDwAGgRGEBA8oEAgACKAAaeo8oUwmmgNMT1QmTbwV1iAUV8XckU4\nUJDWqIG1\n' the original password is pass = 'ZlUBqC2PELx4j3bio1kT' It seemed odd to me that base64 encoding would include \n, so I tried using base64 instead of encode('base64'): passx = base64.b64encode(passwd.encode('bz2')) passx = 'QlpoOTFBWSZTWdaogbUAAAWPgDwAGgRGEBA8oEAgACKAAaeo8oUwmmgNMT1QmTbwV1iAUV8XckU4UJDWqIG1' If you compare the two encodings you'll notice that the only difference is the infix newline and the newline at the end. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] osc init question
by Dave Plater 22 Jan '10

22 Jan '10

Hi, I need to limit my internet bandwidth usage and I'm used to using osc init to do so. Use case :- I have a need to test the operation of pre_checkin.sh for graphics blender but my branch home:plater:branches:graphics blender has svn blender-2.50 in it so I delete it and recreate a branch to graphics blender which contains stable blender-2.49b. Next I copy my local graphics/blender files into home:plater:branches:graphics/blender and use osc init home:plater:branches:graphics blender to initialize as a working copy and I've tried various combinations of copying the files over both before and after "osc init" and still osc wants to delete everything on checkin even though the working copy matches the online package. I've succeeded with this method in the past and it's essential to me to avoid unnecessary uploads and downloads. Thanks Dave P -- 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] Re: [PATCH] do not fill crap into our database by default
by Pavol Rusnak 22 Jan '10

22 Jan '10

On 01/22/2010 09:04 AM, OBS osc wrote: > From: Adrian Schröter <adrian(a)suse.de> > > --- > osc/core.py | 18 ++++++++---------- > 1 files changed, 8 insertions(+), 10 deletions(-) It might make sense to run update on existing database and to remove these default entries from there. Or is it already done? :-) > > diff --git a/osc/core.py b/osc/core.py > index d9473c0..2cdf92a 100644 > --- a/osc/core.py > +++ b/osc/core.py > @@ -43,12 +43,10 @@ exclude_stuff = [store, 'CVS', '*~', '#*#', '.*', '_linkerror'] > new_project_templ = """\ > <project name="%(name)s"> > > - <title>Short title of NewProject</title> > - > - <description>This project aims at providing some foo and bar. > - > -It also does some weird stuff. > -</description> > + <title></title>  > + <description> > +  > + </description> > > <person role="maintainer" userid="%(user)s" /> > <person role="bugowner" userid="%(user)s" /> > @@ -108,17 +106,17 @@ It also does some weird stuff. > new_package_templ = """\ > <package name="%(name)s"> > > - <title>Title of New Package</title> > + <title></title>  > > <description> > -LONG DESCRIPTION > -GOES > -HERE > + > </description> > > <person role="maintainer" userid="%(user)s"/> > <person role="bugowner" userid="%(user)s"/> > + > > <!-- > use one of the examples below to disable building of this package -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz 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

1 0

[opensuse-buildservice] openSUSE Build Service 1.7 Beta 2 available
by Adrian Schröter 22 Jan '10

22 Jan '10

We released the openSUSE Build Service(OBS) Beta 2 today ======================================================== This release is now feature complete and also the API should be final by now. Biggest changes since beta 1 are: * Switch to Ruby on Rails 2.3.5 * The branch call is doing full copies of packages now, not just _link + project.diff anymore * Repository status + dirty flag is calculated and displayed in the web interface (and with osc 0.125) * many bugfixes esp. in api and webui * Workers can get auto configured via SLP. In total we look good to be able to release an RC soon and the final release on 9th February. Download OBS 1.7 Beta 2 ======================= Packages for OBS 1.7 Beta 2 are available via our openSUSE:Tools:Unstable project. You need to add this and the openSUSE:Tools project to get supporting packages. http://download.opensuse.org/repositories/openSUSE:Tools/ http://download.opensuse.org/repositories/openSUSE:Tools:Unstable/ The version of the packages are 1.6.90. We do not release packages for non-SUSE systems, because we have currently no active packager for other platforms. If you are interested in doing this, please speak up. OBS-Appliance ============= This release is the first one which comes also with an appliance. This appliance can be used for just demo purposes, but also to run a production OBS server. Furthermore it can be used to deploy OBS workers in your network. Please find details about this on this wiki page: http://en.opensuse.org/Build_Service/OBS-Appliance This appliance is of course built in openSUSE Build Service itself ;) Have a nice 2010 Your openSUSE Build Service team -- 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

4 13

[opensuse-buildservice] Debian:Etch -> DISCONTINUED:Debian:4.0
by Adrian Schröter 21 Jan '10

21 Jan '10

Hello, as usual we will phase out debian 4.0 next month when their security support ends. Just in case you still want to provide updates for unsecure systems the DISCONTINUED project has been created. Please note that I changed the "Etch" to "4.0" to please our naming scheme. Debian:Etch* will get removed next month. 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

1 0

[opensuse-buildservice] unrepeatable failed builds
by Paul Elliott 21 Jan '10

21 Jan '10

Everyso often I get a build that ends with this error: ------------- breaking dependency polkit -> lib64polkit1_0 cycle: lib64GConf2_4 -> GConf2 breaking dependency GConf2 -> lib64GConf2_4 cycle: lib64ORBit2_0 -> ORBit2 breaking dependency lib64ORBit2_0 -> ORBit2 cycle: lib64ldap2.4_2 -> openldap breaking dependency openldap -> lib64ldap2.4_2 cycle: lib64avahi-client3 -> avahi breaking dependency avahi -> lib64avahi-client3 cycle: x11-proto-devel -> lib64xau6-devel breaking dependency x11-proto-devel -> lib64xau6-devel cycle: x11-proto-devel -> lib64xt6-devel breaking dependency lib64xt6-devel -> x11-proto-devel cycle: x11-proto-devel -> lib64xt6-devel -> lib64x11_6-devel breaking dependency lib64xt6-devel -> lib64x11_6-devel cycle: lib64ice6-devel -> x11-proto-devel -> lib64xt6-devel -> lib64sm6-devel breaking dependency lib64xt6-devel -> lib64sm6-devel cycle: lib64ice6-devel -> x11-proto-devel -> lib64xt6-devel breaking dependency x11-proto-devel -> lib64xt6-devel done booting XEN kernel ... xm create -c /var/run/bsworker_4/build/xen.conf name=build:4_root memory=750 disk=phy:/dev/abuild/4_root,hda1,w disk=phy:/dev/abuild/4_swap,hda2,w extra=quiet init=/.build/build panic=1 console=ttyS0 Using config file "/var/run/bsworker_4/build/xen.conf". argh, no buildstatus set, assuming bad build host... Error: Device 769 (vbd) could not be connected. Hotplug scripts not working. ------------------- I trigger a rebuild and the error goes away! -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 2

[opensuse-buildservice] Expanding dependson and whatdependson to across projects
by Luke Imhoff 20 Jan '10

20 Jan '10

Is there any work being done on expanding the osc dependson and whatdependson command to include dependencies and dependents in other projects? The help for the commands say that you need to use the buildinfo to get the cross-project information, but calculating whatdependson would require calling buildinfo on all project/package pairs, which doesn't seem feasible for any large number of packages. However, I would think that bs_sched must have the full whatdependson information in memory since how else can it know what to rebuild when a package is rebuilt or a scanrepo event comes in? Would it be possible to output the information bs_sched has in a manner similar to the :depends file that (what)dependson is using now? I've been searching through bs_sched, but I only use perl to hack on OBS, so I'm having troubles figure out which variables have such global depends information. -- 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] OBS Developer presence on fairs this year
by Adrian Schröter 20 Jan '10

20 Jan '10

Hi, I started a small wiki page to list fairs for 2010 where OBS developers will attend. In case you want to have some support, a group discussion about a certain topic or a hack event, please speak up. http://en.opensuse.org/Build_Service/Fair_Presence And please extend the page, if you are developing on OBS and go somewhere :) 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

1 0

[opensuse-buildservice] Build service bug.
by Dave Plater 20 Jan '10

20 Jan '10

I have three lilypond projects, one the parent, one is a branch and one is a link (home:plater lilypond). All of a sudden, after working fine since inception the branched project gives me a "broken: conflict in file lilypond.spec" error but if I look at the build log the package is building. Osc pull refuses to do anything (sorry I didn't save the output), osc up makes no difference and osc ci say's nothing to checkin. I delete the package and then branch again. At the time of branching lilypond is building in the parent, the x86_64 packages were previously failed for the last couple of builds and I know how to fix it and the current build is with the fix. After the new branch has completed, I have copies of the parents binaries from x86_64 only no i586 ones. This doesn't seem like normal behavior. The binaries that appeared are also marked as failed without any attempt to build even after the parent had built successfully. Maybe one shouldn't branch a package until it's stopped building? Or maybe this is work in progress, it would be nice if somebody acknowledged that :- a) This is unfixable and I must just work around it or b) We are aware of this problem and are busy fixing it or c) Thanks for letting us know. Glad to help Dave P -- 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] Changelogs for debian repositories
by Luke Imhoff 20 Jan '10

20 Jan '10

I have repositories for our internal OBS setup as deb repositories in apt. Update-manager in Ubuntu sees the updates, but it says it can't display the changelog: Changes for the versions: 2009.07.27.6-1 2009.07.27.7-1 This change is not coming from a source that supports changelogs. Do I have something misconfigured or is this a known issue with deb repositories in OBS? -- 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] Publishing certain subpackages only
by Guido Berhoerster 20 Jan '10

20 Jan '10

Hello, is it possible to publish only certain subpackages built from a common source package, e.g. is it possible to build kdebase4-workspace and only publish the klipper (sub)package built from it? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] What to do with "broken: conflict in file lilypond.spec"?
by Dave Plater 20 Jan '10

20 Jan '10

Hi, "broken: conflict in file lilypond.spec" is happening in my branch of openSUSE:Factory:Contrib lilypond everytime I update the spec file in the main project, how do I avoid this? A bit of background, the branch project is building against a linked Printing:ghostscript ghostscript-library whereas the main project doesn't. Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 3

[opensuse-buildservice] strange build failure: "package already exists: %debugsource"
by Mathias Homann 20 Jan '10

20 Jan '10

Hi, all of a sudden builds are failing for me that have been working fine just the other day. the error i'm getting is this: + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:lemmy04:snowglobe/openSUSE_11.2/43a17f7b109da… snowglobe' --eval %suse_insert_debug_package /usr/src/packages/SOURCES/snowglobe.spec error: Package already exists: %package debugsource what is going on there? bye, MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] OBS generates .ymp with non-exported repositories
by Lubos Lunak 20 Jan '10

20 Jan '10

Hello, My problem: Go to http://kde-apps.org/content/show.php/WMIface?content=40425 and try to install the package on openSUSE. As kde-apps has OBS integration, you can a link to 1-Click-Install file. However, if you just keep clicking next-next-next, the install will fail, because the .ymp includes a repo under home:llunak:distro: that is not published. The user has to find out that repo has to be unchecked from the list of repos to use (and to make it more fun, there's no way to go back, so the whole procedure has to be restarted). Those home:llunak:distro: repositories are a bit like devel:tools:building, they are used only to help building the packages and are not useful for installing. As most of them don't contain any packages, they don't exist on download.opensuse.org, and even if they did, I wouldn't want them to be exported (devel:tools:building publishes the packages, that's why that one works). What can be done to fix this? Preferably without the workaround of including some dummy package in each of those build repos, which would at least make it work by letting people add that for them useless repository. I had a look at the OBS sources and makeymp() in /src/backend/bs_repserver makes all repos recommended except the one in the list, if it's not the only one. I don't quite understand the logic, to me it looks like a hackish attempt to avoid including openSUSE:* repos. Is there e.g. a flag that could be set for a repo to say it should not be included there? The 'publish' setting does not seem to be right, as that'd break the .ymp if the repo of the package itself had publishing disabled at the moment. There's 'binarydownload', but I assume that's something else, although I don't know what it is for exactly. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak(a)suse.cz , l.lunak(a)kde.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Request for web interface feature
by Dave Plater 20 Jan '10

20 Jan '10

Hi, next time somebody's playing with the build service web interface, it would be nice if a link to the package that was blocking the build of my package was present on the web interface. Regards Dave P -- 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] How To Set Access Permission For Group In Squid
by Abel Wang 20 Jan '10

20 Jan '10

Dear All, I am using squid 3.0 on Opensusue, but I do not know if I can block a certain group (which stored in ldap, such as group HRA) to access a certain website, if you know,kindly please give me some advice on how to set,how to write rules in squid.conf Any suggestion will be appreciated, thanks in advance. With best regards, Abel -- 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] build-2009.12.10-66.1 breaks OBS 1.6 KIWI builds
by Michael_E_Brown＠Dell.com 19 Jan '10

19 Jan '10

In /usr/lib/build/Build/Kiwi.pm, line 201: $ret->{'exclarch'} = [ unify(@requiredarch) ]; The 'exclarch' is set to an empty array if there are no required arches. In bs_srcserver, line 1222: $rinfo->{'error'} = 'excluded' if $d->{'exclarch'} && !grep {$_ eq $arch} @{$d->{'exclarch'}}; Which checks if the arch is in the exclarch array. If the array is empty, then the current build arch can *never* be in this empty array, thus disabling all KIWI builds. My fix was to change Kiwi.pm to this: $ret->{'exclarch'} = [ unify(@requiredarch) ] if scalar(@requiredarch); ie. only set exclarch array if there are, in fact, exclusive arches. There is another possible way to fix this by changing bs_srcserver to check for the empty array, but I believe that changing Kiwi.pm is the more logical choice. -- Michael -- 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] osc 0.125: "osc branch" without arguments results in traceback
by Jon Nelson 19 Jan '10

19 Jan '10

osc branch (without arguments): Traceback (most recent call last): File "/usr/bin/osc", line 21, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.6/site-packages/osc/babysitter.py", line 46, in run return prg.main() File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 308, in main return self.cmd(args) File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 331, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 447, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 1177, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.6/site-packages/osc/commandline.py", line 1607, in do_branch expected = 'home:%s:branches:%s' % (conf.config['user'], args[0]) IndexError: list index out of range -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Two packages linked to the same package one installs giflib and one doesn't, why?
by Dave Plater 19 Jan '10

19 Jan '10

Hi, I'm trying to find out why lilypond fails to build intermittently and going through the diff of the two build logs both fro 11.2 x86_64 builds, the successful build from home:plater lilypond has :- "installing giflib-4.1.6-12.3" which the home:plater:branches:openSUSE:Factory:Contrib one doesn't. I've double checked and the local copies are identical. Any tips on why this would happen? Thanks Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 19 Jan '10

19 Jan '10

present: adrian, mls, coolo, tschmidt, cwh, freitag * 1.7 Release * schema validation in api * branch / openSUSE Build Serivce setup Status round ============ mls: * continued work on branch handling, seems to work now also in special cases * perl URL dispatcher checks arguments based on cmd= parameter already coolo: * added popup for build status in request page (for 1.8) * bugfixing esp. in api code * added database table definitions some not null conditions tschmidt: * working on upcomming distribution status page (for 1.8) * Created blog how to bugfix a package in openSUSE:Factory * Created version change(update) RSS feed for Factory cwh: * kiwi bugfixing (efi boot for x86_64) * integrating external code for s390 into kiwi code * fighting with emacs and kiwi indention stale adrian: * Got finally 1.7 beta 2 out! * Created first OBS appliance * bugfixing (appliance is great for running tests) * osc 0.125.1 submission * hopefully osc maintenance update today freitag: * hermes can twitter now, but still needs debugging 1.7 Release =========== * open bugs - webui page for doing an attribute change may be broken - atttibute api docs have broken links - webui has still some broken and webui links in neutral theme - neutral theme has still references to opensuse.org - Live CD and ovf/vmware/virtualbox appliance is not yet working Schema validation in api ======================== API is theoretically checking all xml based on content, but is not validate with the schemas. We will enable schema validation ASAP after 1.7 release, however, we expect that some schemas are not correct and needs fixing. branch / openSUSE Build Serivce setup ===================================== We will branch 1.7 today. openSUSE.org build service will be kept on running on master. So it must be kept working. -- 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

1 0

[opensuse-buildservice] debian build with experimental gcc-4.5?
by Paul Elliott 19 Jan '10

19 Jan '10

I have a bug report that my program, peless, fails to build with gcc-4.5 & g++-4.5. These are in the experimental distribution. Is it possible to build under debian 5.0 using gcc-4.5 using the opensuse-buildservice? -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 4

[opensuse-buildservice] Pushing to gitorious
by Luke Imhoff 18 Jan '10

18 Jan '10

How do I push to gitorious so a patch I have will show up as a merge request? I tried just git push, but got back: The git:// protocol is read-only. Please use the push url as listed on the repository page. I didn't see a push url on http://www.gitorious.org/opensuse/osc, just the clone one. -- 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] Change in behavior of --prefer-pkgs with multiple packages with same name
by Luke Imhoff 18 Jan '10

18 Jan '10

In 0.119.6, if there were two rpms with the same name given with --prefer-pkgs, then the second rpms mentioned won: first_path/ foo-1-1.rpm second_path/ foo-1-0.rpm are passed to osc build --prefer-pkgs first_path --prefer-pkgs second_path foo-1-0.rpm wins. However, after upgrading to osc 0.123, foo-1-1.rpm wins because it has a newer release. The problem with this comes in that there is no way to actually prefer an older rpm. An 'older' rpm may be preferred if the user has a server built rpm foo-version-check_in_count.build_count.rpm like foo-1-16.1.rpm while also having a locally built foo-1-0.0.rpm. The locally built rpm does not know the check_in_count nor build_count so it defaults to 0.0 and therefore appears older than the server built rpm. So, how does the user use his locally built foo-1-0.0.rpm over the foo-1-16.1.rpm if they are both in local --prefer-pkgs directories? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 7