On 07/29/2013 05:17 AM, Michael Schroeder wrote:
On Fri, Jul 26, 2013 at 04:16:13PM -0400, Michel Bourget wrote:
'osc rdelete project -r -f' do not delete everything but, rather, copy some stuff to the "_deleted" project directory and keep bazillions of files related to that project under:
* ./trees/ * ./repos/.../.../... * /repos_sync/ The publisher should eventually delete the ./repos and ./repos_sync stuff.
Interesting ... Didn't notice. Likely, I didn't dig/research it enough.
The sources of the packages in the project are kept because you can undelete projects.
(Keeping all sources is kind of an obs feature, we promise that you can at any time get the sources for packages that were built with obs. You can use 'rpm -q --qf '%{DISTURL'}\n'<rpm>' to query a built package for a reference to its sources.)
Hi Michael, thanks for feedback. The real I have is about an asymmetric semantic, ie: - non-admin user can create "home:user:blah" project. - but can't wipe it, ie. only admin can do it. Imo, a user should be able to "wipe" a project he/she created. "osc rwipe" ? Here's the scenario I went thru: -1. osc meta {prj,prjconf} home:user:blah -2. osc add a couple of packages ... -3. something goes really wrong. Hey, let's restart -4. osc rdelete -f -r home:user:blah -5. re-do step 1 and 2 but better and/or with fixes. -6. re-do step 2 in same manner. Here is where it goes wrong. In step 6, new _pkg and _service files were checked/committed. OBS then states "nothing to do" somehow. Guess what , the buildlog ( and service logs details ) were restored back to what they were, even showing impossible errors because some fixes were applied to a (new, btw ) /usr/lib/obs/service/script. Doing an "osc service remoterun" fixes that ... but, needless to say, it wasn't obvious. At any rate, being able to "osc rwipe" would be a "Very Nice to have(Tm)" :) For the sake of our operations, I wrote a little script to accomplish this on the OBS server as "Admin". Script attached. Thanks !
Cheers, Michael.