Bug 318 - mgarepo command to kill a package
Summary: mgarepo command to kill a package
Status: RESOLVED OLD
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Nicolas Vigier
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 858
  Show dependency treegraph
 
Reported: 2011-03-09 15:24 CET by Jerome Quelin
Modified: 2011-12-16 16:16 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jerome Quelin 2011-03-09 15:24:43 CET
sometimes packages die. in that case, we need to:
- remove it from svn twice (spec+binrepo)
- remove source + rpms
- whoever knows what else

i'd like a command in mgarepo that would do all the needed stuff.


Reproducible: 

Steps to Reproduce:
D Morgan 2011-03-09 15:58:20 CET

Assignee: dmorganec => boklm

Comment 1 Nicolas Vigier 2011-03-09 15:59:36 CET
Ok, good idea. I will look at adding this.
Comment 2 Nicolas Vigier 2011-03-09 16:19:49 CET
Or maybe youri could remove obsoleted packages from svn, or move them in an "obsolete" directory.
Nicolas Vigier 2011-04-17 17:42:26 CEST

Blocks: (none) => 858

Comment 3 Ahmad Samir 2011-05-21 00:24:51 CEST
*** Bug 1357 has been marked as a duplicate of this bug. ***

CC: (none) => thierry.vignaud

Comment 4 Marja Van Waes 2011-10-05 17:44:44 CEST
@ Jerôme
@ Nicolas

Any news on this enhancement?

CC: (none) => marja11

Comment 5 Marja Van Waes 2011-12-11 21:34:57 CET
@ Assignee
I think this bug was assigned correctly, but please confirm by putting "OK" on the whiteboard or by confirming in a comment
Comment 6 Nicolas Vigier 2011-12-16 16:16:15 CET
It is now planned to create a task-obsolete package (bug #3786), to obsolete packages from the repository.

Steps to obsolete a package will be :
 - add obsolete in task-obsolete package
 - move package on svn to obsolete directory

So I don't think an mgarepo command will be needed anymore.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.