[opensuse-buildservice] Important osc version 0.119 release !
The new osc version 0.119 is released and available in the openSUSE:Tools project. It comes with a new build script package as well. You will need this version of osc to handle new kinds of requests, which will come soon to api.opensuse.org. So an update is highly recommended. This release has a lot of fixes and new features, but also some argument changes compared to former releases. We decided to do these changes to have a more consistent UI and to avoid conflicts in the future. However, osc always tells you when you use a command in a no longer supported way and points you to the new command. Find a list of changes at the bottom of this mail. Main Features/Bugfixes ====================== osc request: osc now supports multiple kinds of requests (needs OBS version 1.7, api.opensuse.org will get upgraded soon). You can create requests with the following commands: * osc submitrequest (or just "osc sr") * osc submitrequest DESTPRJ [DESTPKG] * osc submitrequest SOURCEPRJ SOURCEPKG DESTPRJ [DESTPKG] * osc deleterequest PROJECT [PACKAGE] * osc changedevelrequest PROJECT PACKAGE DEVEL_PROJECT [DEVEL_PACKAGE] And there is one new command that deals with all kind of requets: * osc request list [-M] [PRJ [PKG]] * osc request log ID * osc request show [-d] [-b] ID * osc request accept [-m TEXT] ID * osc request decline [-m TEXT] ID * osc request revoke [-m TEXT] ID osc build: * Image building now uses the correct pool of packages * plain "osc build" command now picks a correct repository Package tracking has now been enabled by default. That means you can do all kind of local changes in a checked out project with multiple packages and submit them all together in one step. This includes adding new packages or deleting them. You can find a more detailed list, including all smaller changes in the "NEWS" file of the osc package. Command UI changes ================== osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild Download URL ============ http://download.opensuse.org/repositories/openSUSE:Tools/ We plan to make an official update of osc and build for former distros. It will include either this version or the next one. Btw, it is really great that we get more and more contributors to osc lately. This release would not have been possible without the work of mvyskocil, mcihar, dimstar, mmeeks, Ming Xi Wu, MartinMohring, Marcus Huewe, prusnak, lnussel and some person I always forget (sorry in advance ;) ! Go on and make this your tool, only the users know it best ! ;) thanks a lot adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2009-06-16 15:13:45 +0200, Adrian Schröter wrote:
The new osc version 0.119 is released and available in the openSUSE:Tools project. It comes with a new build script package as well.
You will need this version of osc to handle new kinds of requests, which will come soon to api.opensuse.org. So an update is highly recommended.
This release has a lot of fixes and new features, but also some argument changes compared to former releases. We decided to do these changes to have a more consistent UI and to avoid conflicts in the future.
However, osc always tells you when you use a command in a no longer supported way and points you to the new command. Find a list of changes at the bottom of this mail.
Main Features/Bugfixes ======================
osc request: osc now supports multiple kinds of requests (needs OBS version 1.7, api.opensuse.org will get upgraded soon). You can create requests with the following commands: * osc submitrequest (or just "osc sr") * osc submitrequest DESTPRJ [DESTPKG] * osc submitrequest SOURCEPRJ SOURCEPKG DESTPRJ [DESTPKG] * osc deleterequest PROJECT [PACKAGE] * osc changedevelrequest PROJECT PACKAGE DEVEL_PROJECT [DEVEL_PACKAGE]
And there is one new command that deals with all kind of requets: * osc request list [-M] [PRJ [PKG]] * osc request log ID * osc request show [-d] [-b] ID * osc request accept [-m TEXT] ID * osc request decline [-m TEXT] ID * osc request revoke [-m TEXT] ID
osc build: * Image building now uses the correct pool of packages * plain "osc build" command now picks a correct repository
Package tracking has now been enabled by default. That means you can do all kind of local changes in a checked out project with multiple packages and submit them all together in one step. This includes adding new packages or deleting them.
You can find a more detailed list, including all smaller changes in the "NEWS" file of the osc package.
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Download URL ============
http://download.opensuse.org/repositories/openSUSE:Tools/
We plan to make an official update of osc and build for former distros. It will include either this version or the next one.
Btw, it is really great that we get more and more contributors to osc lately. This release would not have been possible without the work of mvyskocil, mcihar, dimstar, mmeeks, Ming Xi Wu, MartinMohring, Marcus Huewe, prusnak, lnussel and some person I always forget (sorry in advance ;) !
Go on and make this your tool, only the users know it best ! ;)
so all the voice that raised concerns about this major break in the user interface were just ignored, even though there was the statement there will be a meeting to discuss this before a release? this is a great way to listen to your community darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 16. Juni 2009 15:18:48 schrieb Marcus Rueckert:
On 2009-06-16 15:13:45 +0200, Adrian Schröter wrote: ...
Btw, it is really great that we get more and more contributors to osc lately. This release would not have been possible without the work of mvyskocil, mcihar, dimstar, mmeeks, Ming Xi Wu, MartinMohring, Marcus Huewe, prusnak, lnussel and some person I always forget (sorry in advance ;) !
Go on and make this your tool, only the users know it best ! ;)
so all the voice that raised concerns about this major break in the user interface were just ignored, even though there was the statement there will be a meeting to discuss this before a release?
this is a great way to listen to your community
There is no single community, always multiple opionions. There was no really working solution suggested in the last two weeks and we can't block Henne's plan forever because of this. And we have in fact changed some commands doing different reporting now that before. It is not that we did nothing. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, Le mardi 16 juin 2009, à 15:13 +0200, Adrian Schröter a écrit :
The new osc version 0.119 is released and available in the openSUSE:Tools project.
Can you make sure it enters openSUSE:Factory too? Would be better to have a working osc experience out of the box ;-)
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Hrm. I didn't see the thread about this, but I would have also mentioned that breaking the UI for this isn't really a good thing. Sure, it'll be necessary at some point, but I don't agree it was necessary for those new features. Some complete redesign would probably have been better, since we're probably keeping some bad UI. Eg: - renaming rebuildpac but not copypac or linkpac is a bit weird. - remotebuildlog while we have rdelete, rdiff, etc. (sure, rbuildlog is an alias, but then why keep remotebuildlog?) - we have results, but buildlog, buildinfo, buildconfig, etc.? I would have expected buildresults (so my main issue is that we're breaking the UI now, and we'll probably have to break it again later) Also, why not keep the old commands for compatibility when possible (ie, not for req)? Was this difficult for some reason, or was it just lack of time? Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 16. Juni 2009 16:44:05 schrieb Vincent Untz:
Hi,
Le mardi 16 juin 2009, à 15:13 +0200, Adrian Schröter a écrit :
The new osc version 0.119 is released and available in the openSUSE:Tools project.
Can you make sure it enters openSUSE:Factory too? Would be better to have a working osc experience out of the box ;-)
it is on the way ...
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Hrm. I didn't see the thread about this, but I would have also mentioned that breaking the UI for this isn't really a good thing. Sure, it'll be necessary at some point, but I don't agree it was necessary for those new features. Some complete redesign would probably have been better, since we're probably keeping some bad UI.
Eg: - renaming rebuildpac but not copypac or linkpac is a bit weird. - remotebuildlog while we have rdelete, rdiff, etc. (sure, rbuildlog is an alias, but then why keep remotebuildlog?) - we have results, but buildlog, buildinfo, buildconfig, etc.? I would have expected buildresults
(so my main issue is that we're breaking the UI now, and we'll probably have to break it again later)
We think that these changes avoid exactly that we need to break request handling commands again. But keeping the old ones would create conflicts again and again.
Also, why not keep the old commands for compatibility when possible (ie, not for req)? Was this difficult for some reason, or was it just lack of time?
The thread was on opensuse-buildservice when the 0.118/9 beta versions where announced. We kept the old commands where it caused no conflicts, but we wanted to have a UI which can be conflict free in future in first place. It was basically conflicts or inconsitencies. For example the word "delete" should do similar things in different contexts. Replies please to opensuse-buildservice ml only for this thread. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Le mardi 16 juin 2009, à 17:07 +0200, Adrian Schröter a écrit :
Am Dienstag, 16. Juni 2009 16:44:05 schrieb Vincent Untz:
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Hrm. I didn't see the thread about this, but I would have also mentioned that breaking the UI for this isn't really a good thing. Sure, it'll be necessary at some point, but I don't agree it was necessary for those new features. Some complete redesign would probably have been better, since we're probably keeping some bad UI.
Eg: - renaming rebuildpac but not copypac or linkpac is a bit weird. - remotebuildlog while we have rdelete, rdiff, etc. (sure, rbuildlog is an alias, but then why keep remotebuildlog?) - we have results, but buildlog, buildinfo, buildconfig, etc.? I would have expected buildresults
(so my main issue is that we're breaking the UI now, and we'll probably have to break it again later)
We think that these changes avoid exactly that we need to break request handling commands again. But keeping the old ones would create conflicts again and again.
I'd disagree about not needing to change the request handling commands anymore. At least, I disagree if we want to have a good UI. First thing that strikes me is that submitrequest is not a good name anymore. I mean: deleterequest and changedevelrequest are pretty clear, since they are about "delete" and "change devel". But submitrequest is about "submit"? What does that mean? Also, when I do deletereq, I submit a delete request. So it could have lived as a subcommand of submitreq (assuming the accept/decline/revoke/delete subcommands were moved, which is the case since the moved to the request command). IMHO, we can't really make the UI good if we don't look at the big picture. And the bigger issue about the osc UI is that osc does multiple things: + commands to work on a local checkout (co, commit, add, rm, build, etc.) + commands to work on the project structure of obs (meta, copypac, linkpac, etc.) + commands for the collaboration features (branch, sr, req, etc.) + some misc commands to interact with the build service (maintainer, platforms, search) + (maybe some other categories) All those commands are mixed at the same level. So it can be hard to know what's the difference between delete, deletereq and rdelete, eg. I don't have a good solution for all this, and I'm not saying it's easy. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 16. Juni 2009 17:27:18 schrieb Vincent Untz:
Le mardi 16 juin 2009, à 17:07 +0200, Adrian Schröter a écrit :
Am Dienstag, 16. Juni 2009 16:44:05 schrieb Vincent Untz:
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Hrm. I didn't see the thread about this, but I would have also mentioned that breaking the UI for this isn't really a good thing. Sure, it'll be necessary at some point, but I don't agree it was necessary for those new features. Some complete redesign would probably have been better, since we're probably keeping some bad UI.
Eg: - renaming rebuildpac but not copypac or linkpac is a bit weird.
yes, might be. question is if copy(pac) and link(pac) should also work local in future (now that we have package tracking) and if that works without conflicts.
- remotebuildlog while we have rdelete, rdiff, etc. (sure, rbuildlog is an alias, but then why keep remotebuildlog?)
actually from my point of view buildlog and rbuildlog are bother remote commands, because they got the log from the server. an "osc buildlog" may would show the build log from your local build, would that make sense ? Of course again an incompatible change.
- we have results, but buildlog, buildinfo, buildconfig, etc.? I would have expected buildresults
hm, maybe a good idea, we could rename and keep an alias to the old name.
(so my main issue is that we're breaking the UI now, and we'll probably have to break it again later)
We think that these changes avoid exactly that we need to break request handling commands again. But keeping the old ones would create conflicts again and again.
I'd disagree about not needing to change the request handling commands anymore. At least, I disagree if we want to have a good UI.
First thing that strikes me is that submitrequest is not a good name anymore. I mean: deleterequest and changedevelrequest are pretty clear, since they are about "delete" and "change devel". But submitrequest is about "submit"? What does that mean?
So what do you propose, call it "mergerequest" or "copyrequest" ? We could do so with the new command styles and keep compatibility now :)
Also, when I do deletereq, I submit a delete request. So it could have lived as a subcommand of submitreq (assuming the accept/decline/revoke/delete subcommands were moved, which is the case since the moved to the request command).
IMHO, we can't really make the UI good if we don't look at the big picture. And the bigger issue about the osc UI is that osc does multiple things:
+ commands to work on a local checkout (co, commit, add, rm, build, etc.) + commands to work on the project structure of obs (meta, copypac, linkpac, etc.) + commands for the collaboration features (branch, sr, req, etc.) + some misc commands to interact with the build service (maintainer, platforms, search) + (maybe some other categories)
All those commands are mixed at the same level. So it can be hard to know what's the difference between delete, deletereq and rdelete, eg.
I don't have a good solution for all this, and I'm not saying it's easy.
I would suggest that we work on a good proposal in the wiki first. This time we had the additional proplem that we were under time pressure as well. But we can avoid this, if we plan now for the future. Afterwards we do a last incompatible implementation and name osc 1.0 with the goal to keep the UI. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Jun 16, 2009 at 05:27:18PM +0200, Vincent Untz wrote:
Le mardi 16 juin 2009, à 17:07 +0200, Adrian Schröter a écrit :
Am Dienstag, 16. Juni 2009 16:44:05 schrieb Vincent Untz:
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Hrm. I didn't see the thread about this, but I would have also mentioned that breaking the UI for this isn't really a good thing. Sure, it'll be necessary at some point, but I don't agree it was necessary for those new features. Some complete redesign would probably have been better, since we're probably keeping some bad UI.
Eg: - renaming rebuildpac but not copypac or linkpac is a bit weird. - remotebuildlog while we have rdelete, rdiff, etc. (sure, rbuildlog is an alias, but then why keep remotebuildlog?) - we have results, but buildlog, buildinfo, buildconfig, etc.? I would have expected buildresults
(so my main issue is that we're breaking the UI now, and we'll probably have to break it again later)
We think that these changes avoid exactly that we need to break request handling commands again. But keeping the old ones would create conflicts again and again.
I'd disagree about not needing to change the request handling commands anymore. At least, I disagree if we want to have a good UI.
First thing that strikes me is that submitrequest is not a good name anymore. I mean: deleterequest and changedevelrequest are pretty clear, since they are about "delete" and "change devel". But submitrequest is about "submit"? What does that mean?
Also, when I do deletereq, I submit a delete request. So it could have lived as a subcommand of submitreq (assuming the accept/decline/revoke/delete subcommands were moved, which is the case since the moved to the request command).
IMHO, we can't really make the UI good if we don't look at the big picture. And the bigger issue about the osc UI is that osc does multiple things:
+ commands to work on a local checkout (co, commit, add, rm, build, etc.) + commands to work on the project structure of obs (meta, copypac, linkpac, etc.) + commands for the collaboration features (branch, sr, req, etc.) + some misc commands to interact with the build service (maintainer, platforms, search) + (maybe some other categories)
I'd like to add my 2c here: We also have the same set of commands to work on: -- local checked out copy of a package/project -- remote versions of packages/projects And there are vast inconsistencies in the handling of the differences between the two. This is pretty frustrating to develop around. Some commands are only available on a local checked-out copy of a project when it seems like they should work remotely just as well. Some examples: results / rresults but: results_meta has no remote equivalent buildinfo: no remote Personally, what I would like to see would be something like: osc --local results ... osc --remote --project XXX --package YYY results ... or something similar so that both remote and local commands all have the same command line structure and a defined way to run them remotely. Of course, there are going to be some commands that dont make sense remotely, like 'osc resolved', for example. -- Michael
Am Dienstag, 16. Juni 2009 18:10:03 schrieb Michael E Brown:
On Tue, Jun 16, 2009 at 05:27:18PM +0200, Vincent Untz wrote:
Le mardi 16 juin 2009, à 17:07 +0200, Adrian Schröter a écrit :
Am Dienstag, 16. Juni 2009 16:44:05 schrieb Vincent Untz:
Command UI changes ==================
osc submitreq create -> osc submitreq osc submitreq accept/decline/show/revoke -> osc request accept/... osc submitreq delete -> osc request wipe osc deletepac -> osc delete or osc rdelete osc deleteprj -> osc rdelete osc rlog -> osc log osc rprjresults -> osc prjresults osc rresults -> osc results osc req -> osc api osc rebuildpac -> osc rebuild
Hrm. I didn't see the thread about this, but I would have also mentioned that breaking the UI for this isn't really a good thing. Sure, it'll be necessary at some point, but I don't agree it was necessary for those new features. Some complete redesign would probably have been better, since we're probably keeping some bad UI.
Eg: - renaming rebuildpac but not copypac or linkpac is a bit weird. - remotebuildlog while we have rdelete, rdiff, etc. (sure, rbuildlog is an alias, but then why keep remotebuildlog?) - we have results, but buildlog, buildinfo, buildconfig, etc.? I would have expected buildresults
(so my main issue is that we're breaking the UI now, and we'll probably have to break it again later)
We think that these changes avoid exactly that we need to break request handling commands again. But keeping the old ones would create conflicts again and again.
I'd disagree about not needing to change the request handling commands anymore. At least, I disagree if we want to have a good UI.
First thing that strikes me is that submitrequest is not a good name anymore. I mean: deleterequest and changedevelrequest are pretty clear, since they are about "delete" and "change devel". But submitrequest is about "submit"? What does that mean?
Also, when I do deletereq, I submit a delete request. So it could have lived as a subcommand of submitreq (assuming the accept/decline/revoke/delete subcommands were moved, which is the case since the moved to the request command).
IMHO, we can't really make the UI good if we don't look at the big picture. And the bigger issue about the osc UI is that osc does multiple things:
+ commands to work on a local checkout (co, commit, add, rm, build, etc.) + commands to work on the project structure of obs (meta, copypac, linkpac, etc.) + commands for the collaboration features (branch, sr, req, etc.) + some misc commands to interact with the build service (maintainer, platforms, search) + (maybe some other categories)
I'd like to add my 2c here:
We also have the same set of commands to work on: -- local checked out copy of a package/project -- remote versions of packages/projects
And there are vast inconsistencies in the handling of the differences between the two. This is pretty frustrating to develop around. Some commands are only available on a local checked-out copy of a project when it seems like they should work remotely just as well.
Some examples: results / rresults but: results_meta has no remote equivalent
buildinfo: no remote
Personally, what I would like to see would be something like: osc --local results ... osc --remote --project XXX --package YYY results ...
or something similar so that both remote and local commands all have the same command line structure and a defined way to run them remotely. Of course, there are going to be some commands that dont make sense remotely, like 'osc resolved', for example.
The advantage of that UI would be that it would be easily compatible for all forseable future. But the disadvantage would be that you would need to type way more than now. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, uninstallable via yast/zypper on SLE_10 obs:~ # zypper in osc Die Systemquellen werden wiederhergestellt... Metadaten werden analysiert fürSDK SP2... Metadaten werden analysiert füropenSuSE_Archiving_Backup... Metadaten werden analysiert für-20080709-220611... Metadaten werden analysiert fürruby... Metadaten werden analysiert fürlua... Metadaten werden analysiert fürSLES 10 SP2 Updates... Metadaten werden analysiert fürExtras... Metadaten werden analysiert fürhttp... Metadaten werden analysiert fürSLES 10 SP2... Metadaten werden analysiert fürSIT_Extras... RPM-Datenbank wird analysiert... Zusammenfassung: <install>[S3:0][package]build-2009.06.04-47.2.noarch <install>[S3:0][package]osc-0.119-2.1.x86_64 <uninstall>[S0:0][package]osc-0.117-9.1.x86_64 <uninstall>[S0:0][package]build-2009.04.23-46.1.noarch fortfahren? [y/n]: y Downloading: [S3:0][package]build-2009.06.04-47.2.noarch, 85,5 K(402,0 K unpacked) Installing: [S3:0][package]build-2009.06.04-47.2.noarch [S3:0][package]build-2009.06.04-47.2.noarch Subprocess failed. Error: RPM failed: Invalid object Invalid object Installing: [S3:0][package]build-2009.06.04-47.2.noarch [S3:0][package]build-2009.06.04-47.2.noarch Subprocess failed. Error: RPM failed: (with nodeps)Invalid object (with nodeps)Invalid object Installing: [S3:0][package]build-2009.06.04-47.2.noarch [S3:0][package]build-2009.06.04-47.2.noarch Subprocess failed. Error: RPM failed: (with nodeps+force)Invalid object (A)bbrechen, E(r)neut versuchen, (I)gnorieren? I Downloading: [S3:0][package]osc-0.119-2.1.x86_64, 234,4 K(771,3 K unpacked) Installing: [S3:0][package]osc-0.119-2.1.x86_64 [S3:0][package]osc-0.119-2.1.x86_64 Subprocess failed. Error: RPM failed: Invalid object Invalid object Installing: [S3:0][package]osc-0.119-2.1.x86_64 [S3:0][package]osc-0.119-2.1.x86_64 Subprocess failed. Error: RPM failed: (with nodeps)Invalid object (with nodeps)Invalid object Installing: [S3:0][package]osc-0.119-2.1.x86_64 [S3:0][package]osc-0.119-2.1.x86_64 Subprocess failed. Error: RPM failed: (with nodeps+force)Invalid object (A)bbrechen, E(r)neut versuchen, (I)gnorieren? I Regards Chris Adrian Schröter schrieb:
The new osc version 0.119 is released and available in the openSUSE:Tools project. It comes with a new build script package as well.
You will need this version of osc to handle new kinds of requests, which will come soon to api.opensuse.org. So an update is highly recommended.
This release has a lot of fixes and new features, but also some argument changes compared to former releases. We decided to do these changes to have a more consistent UI and to avoid conflicts in the future.
However, osc always tells you when you use a command in a no longer supported way and points you to the new command. Find a list of changes at the bottom of this mail.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
but on console obs:/srv/ftp/pub/mirror/opensuse/repositories/openSUSE:/Tools/SLE_10/noarch # rpm -Uvh build-2009.06.04-47.1.noarch.rpm Preparing... ########################################### [100%] 1:build ########################################### [100%] obs:/srv/ftp/pub/mirror/opensuse/repositories/openSUSE:/Tools/SLE_10/x86_64 # rpm -Uvh osc-0.119-2.1.x86_64.rpm Preparing... ########################################### [100%] 1:osc ########################################### [100%] it is working. zypper/YAST broken ? bye Chris Christian schrieb:
Hi,
uninstallable via yast/zypper on SLE_10
obs:~ # zypper in osc Die Systemquellen werden wiederhergestellt... Metadaten werden analysiert fürSDK SP2... Metadaten werden analysiert füropenSuSE_Archiving_Backup... Metadaten werden analysiert für-20080709-220611... Metadaten werden analysiert fürruby... Metadaten werden analysiert fürlua... Metadaten werden analysiert fürSLES 10 SP2 Updates... Metadaten werden analysiert fürExtras... Metadaten werden analysiert fürhttp... Metadaten werden analysiert fürSLES 10 SP2... Metadaten werden analysiert fürSIT_Extras... RPM-Datenbank wird analysiert... Zusammenfassung: <install>[S3:0][package]build-2009.06.04-47.2.noarch <install>[S3:0][package]osc-0.119-2.1.x86_64 <uninstall>[S0:0][package]osc-0.117-9.1.x86_64 <uninstall>[S0:0][package]build-2009.04.23-46.1.noarch fortfahren? [y/n]: y Downloading: [S3:0][package]build-2009.06.04-47.2.noarch, 85,5 K(402,0 K unpacked) Installing: [S3:0][package]build-2009.06.04-47.2.noarch [S3:0][package]build-2009.06.04-47.2.noarch Subprocess failed. Error: RPM failed:
Invalid object Invalid object Installing: [S3:0][package]build-2009.06.04-47.2.noarch [S3:0][package]build-2009.06.04-47.2.noarch Subprocess failed. Error: RPM failed:
(with nodeps)Invalid object (with nodeps)Invalid object Installing: [S3:0][package]build-2009.06.04-47.2.noarch [S3:0][package]build-2009.06.04-47.2.noarch Subprocess failed. Error: RPM failed:
(with nodeps+force)Invalid object (A)bbrechen, E(r)neut versuchen, (I)gnorieren? I Downloading: [S3:0][package]osc-0.119-2.1.x86_64, 234,4 K(771,3 K unpacked) Installing: [S3:0][package]osc-0.119-2.1.x86_64 [S3:0][package]osc-0.119-2.1.x86_64 Subprocess failed. Error: RPM failed:
Invalid object Invalid object Installing: [S3:0][package]osc-0.119-2.1.x86_64 [S3:0][package]osc-0.119-2.1.x86_64 Subprocess failed. Error: RPM failed:
(with nodeps)Invalid object (with nodeps)Invalid object Installing: [S3:0][package]osc-0.119-2.1.x86_64 [S3:0][package]osc-0.119-2.1.x86_64 Subprocess failed. Error: RPM failed:
(with nodeps+force)Invalid object (A)bbrechen, E(r)neut versuchen, (I)gnorieren? I
Regards Chris
Adrian Schröter schrieb:
The new osc version 0.119 is released and available in the openSUSE:Tools project. It comes with a new build script package as well.
You will need this version of osc to handle new kinds of requests, which will come soon to api.opensuse.org. So an update is highly recommended.
This release has a lot of fixes and new features, but also some argument changes compared to former releases. We decided to do these changes to have a more consistent UI and to avoid conflicts in the future.
However, osc always tells you when you use a command in a no longer supported way and points you to the new command. Find a list of changes at the bottom of this mail.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
Christian -
Marcus Rueckert -
Michael E Brown -
Vincent Untz