How to properly clean up the entire project ?
Hey Everyone, I used this cmd line to clean up my project with the entire packages. - "osc rdelete ProjectFoo -m cleanup" All traces have disappeared in that directory, like: /srv/obs/build. But On the other hand, there are always traces on: /srv/obs/sources.Which this takes up a lot of space in the long term. What is the exact way to delete things in that dir.(/srv/obs/sources)? And What's the best way to make up for other projects that already deleted in the past? # ls -al /srv/obs/sources/|wc -l 52336 Thank you very much, -ren
On Freitag, 4. Dezember 2020, 11:00:40 CET Ren Lan wrote:
Hey Everyone, I used this cmd line to clean up my project with the entire packages.
- "osc rdelete ProjectFoo -m cleanup"
All traces have disappeared in that directory, like: /srv/obs/build. But On the other hand, there are always traces on: /srv/obs/sources.Which this takes up a lot of space in the long term.
What is the exact way to delete things in that dir.(/srv/obs/sources)? And What's the best way to make up for other projects that already deleted in the past?
OBS is there to guarantee that all old builds are reproducible, therefore
it would never ever remove sources.
However, you may want to play as admin with
obs_admin --remove-old-sources
option nevertheless.
--
Adrian Schroeter
Thank you Adrian. I am running an older version of OBS.(obs-server-2.6.10) the man says: " --remove-old-sources <days> <y> (--debug) WARNING: this is an experimental feature atm. It may trash your data, but you have anyway a backup, right? remove sources older than <x> days, but keep <y> number of revisions --debug for debug output " Except to backup "/srv/obs/sources", Is there anything else I can back up before I run the remove-old-sources? And if something goes wrong, just restoring the "/srv/obs/sources" folder will do the trick? Thanks for the details. -ren
participants (2)
-
Adrian Schröter
-
Ren Lan