May 2009 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] Change an Packagename
by Sascha 'saigkill' Manns 18 May '09

18 May '09

Am Montag 18 Mai 2009 11:03:50 you wrote: > osc copypac PrjName oldname PrjName newname > osc rdelete PrjName oldname Thanks, that works :-) -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

1 0

[opensuse-buildservice] Change an Packagename
by Sascha 'saigkill' Manns 18 May '09

18 May '09

Hello Mates, if i create an new Package, i give OBS an Name, Topic and Extra Information. Is it possible, to change the first Name of the Package? Or must i create an new Folder and copy the Stuff into that new Folder? -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

1 0

[opensuse-buildservice] [PATCH] print package name before complaining about broken link
by Anas Nashif 15 May '09

15 May '09

Hi, Here is a one-liner patch that resolves an annoyance when updating a project with lots of links. osc will complain about broken links and being able to apply the project diff, but never prints what package is broken. Anas -- --- buildservice/src/clientlib/python/osc/osc/core.py (revision 7339) +++ buildservice/src/clientlib/python/osc/osc/core.py (working copy) @@ -443,6 +443,7 @@ elif state == ' ': # do a simple update p = Package(os.path.join(self.dir, pac)) + print 'Updating %s' % p.name rev = None if expand_link and p.islink() and not p.isexpanded(): rev = p.linkinfo.xsrcmd5 @@ -452,7 +453,6 @@ print 'Unexpanding to rev', rev elif p.islink() and p.isexpanded(): rev = p.latest_rev(); - print 'Updating %s' % p.name p.update(rev) elif state == 'D': # TODO: Package::update has to fixed to behave like svn does -- 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] Editing Watchlist
by Karl Eichwalder 15 May '09

15 May '09

In my watchlist "project=translation" is listed, but this does not exist anymore. How can I remove "translation" from my watchlist? -- 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

2 2

[opensuse-buildservice] osc 0.117 with "repairlink" and "changelog" support
by Adrian Schröter 15 May '09

15 May '09

A new osc release, version 0.117 is out. This one has as main features the long awaited "repairlink" functionality to fix broken source links due to conflicting source changes and also tool support to maintain the .changes file easier. "osc repairlink" was implemented by Michael Schroeder. It checks out a package with merged source changes. It usesa 3-way merge to resolve file conflicts. After reviewing/repairing the merge, 'osc ci' will re-create a working source link. "osc vc" was implemented by Michal Vyskocil and can collect commit messages to prepare a changelog entry in the .changes file. Please note that the entries there get read by users of the package, so commit messages like "get it building" or "yet another try to get the patch applied" are not helpfull for them and should get removed from the .changes file. An alternative solution to maintain the changelog is to call "buildvc" directly, which gets provided by the also released build.rpm There are also a number of bugfixes and improvements inside to make your life easier: * You do not need to specify project and package anymore on "osc getbinaries" when your cwd is a checkout package. * "osc branch" got a new option to define a different branch project name. * "osc branch" got a new option to checkout the package directly after branching * "osc co PACKAGE" works inside of a checked out project directory You can find the latest version of osc and build rpms in openSUSE:Tools project as usual. http://download.opensuse.org/repositories/openSUSE:/Tools/ I hope this makes your life much easier now :) 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

3 5

[opensuse-buildservice] osc submitreq list [-M|--mine]
by Dominique Leuenberger 15 May '09

15 May '09

Hi, Inspired by the fact that OBS Webclient can show me 'my' submitreqs I hacked up a bit on osc and added the parameter -M to the sr list command. Examples: osc sr list guesses if $pwd is a prj / pkg and shows SR's against it. PRJ and PKG can both be defined on the cmdline. All this is unchanged. NEW: if you start osc sr list -M it will show ALL SRs created by YOU, in state NEW I think this can be very handy to keep an overview. Of course, constructs like osc sr list -M PRJ shows me all MY SR's of the specified project It can even be extended with -s (for the state). Any comments on it? Best regards, Dominique

2 1

[opensuse-buildservice] [PATCH] get build log starting from the offset
by Ming Xi Wu 14 May '09

14 May '09

Hi, When I fix some building errors on our build service, it's very painfull to wait for loading all the build log especially Firefox's 38M bytes log, while I only want to see the last few lines where the error meets. Luckily, web API provides a parameter to set the offset which is not included in the CLI, so I just add an option for the CLI to set the it. Moreover, I hope osc can provide an API & option for only access the last lines of build log. From my experience, it makes sense for 80% time. BR, Mingxi

2 1

[opensuse-buildservice] Conflicting libraries
by Michal Hrusecky 12 May '09

12 May '09

Hi, I'm trying to resolve conflict between two packages which both provides the same library. I've got for example sblim-cmpi-nfsv3 package which depends among others on cim-server and sblim-cmpi-devel. sblim-cmpi-devel is in BuildRequires and cim-server in Requires. cim-server is provided by tog-pegasus or sblim-sfcb. tog-pegasus provides same library as sblim-cmpi-devel, so I added Conflicts to the spec files of both packages. But when I try to build sblim-cmpi-nfsv3 it pulls in both sblim-cmpi-devel and tog-pegasus although it can pull only sblim-sfcb (which is pulled in anyway (it's in PreReq)) and therefore satisfy cim-server dependency without encountering conflict. Question is simple, what am I doing wrong? One last note, it happened in build service only. I can built package locally without problem using osc. I guess that's because cim-server is in Requires only so it isn't needed during build at all but it is needed during some additional testing buildservice does? -- Michal Hrusecky

2 1

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 12 May '09

12 May '09

Present: mls, lrupp, adrian, froh, abauer, freitag, rlihm, poeml Topics: * Status round * "request" handling XML change Status Round ============ abauer: * worked on library to simplify Active XML infrastructure. Result will be OBS specific, but simplier to maintain than the general purpose Active XML before. * worked on request handling in frontend code. mls: * Fixed a bug in search call (version search is possible now) * Debugging signature errors, when built packages are randomly failing. lrupp: * Thinking about how to update docbook documentation for OBS from wiki pages automatically. freitag: * Changed notifications for submit requests creation. By default notifications are only send to people in target project/package. * Will create Hermes product in FATE. adrian: * rolled 1.6 RC 1 packages, not yet tested. needs to be tested together with new build and kiwi releases. * working on request handling together with abauer. Request Handling Changes ======================== Discussion about problems with current XML spec for requests. Currently new request types must get supported also in all clients to allow listing based on given affected project or package. To solve this and to allow multiple requests in one XML submission, we agreed on the following new format. We should keep the old submit request format still supported (but not the newly introduced delete request from last week). <requests> <request type="submit"> <source project=".." package=".." /> <target project=".." package=".." /> </request> <request type="delete"> <target project=".." package=".." /> </request> <history... <state... </requests> -- 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] osc branch error
by Christian 11 May '09

11 May '09

Hi, using 0.117 when I branch a package I get: christian@chrisw:~/OBS> osc -A https://api.opensuse.org branch server:monitoring nagios home:computersalat:devel Traceback (most recent call last): File "/usr/bin/osc", line 12, in <module> r = babysitter.run(osccli) File "/usr/lib64/python2.6/site-packages/osc/babysitter.py", line 40, in run return prg.main() File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 256, in main return self.cmd(args) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 279, in cmd retval = self.onecmd(argv) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 395, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 1070, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib64/python2.6/site-packages/osc/commandline.py", line 940, in do_branch devloc = r.split('branches:')[1] IndexError: list index out of range but package is sucessfully branched. normal behavior ? Bye Chris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0