[opensuse-buildservice] RFC: openSUSE:Dropped project
Hi there Following the "Package foo needs new maintainer" resp. "Drop request for package foo" mails on opensuse-packaging for a while. Community members already asked for more details when a package is dropped from Factory. So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an overview about currently dropped packages? Means: 1) Packager sends drop request internally 2) Project manager agrees => drop package ^^^^^ Same as before. 3) the latest checked in package source (regardless if successful building or not) is copied into the project openSUSE:Dropped ^^^^^ New - formerly we just moved the source to an internal backup space and marked it as deleted in PDB. ---- 4) People can always see, which formerly packages are removed from the current Factory (and therefore will not be in the next release) looking at the openSUSE:Dropped repository 5) Interested community packagers can use/copy the latest source from openSUSE:Dropped Open questions: 1) Is this idea worth to be implemented? 2) What about packages with security problems? - Publishing should be disabled for all packages in the openSUSE:Dropped repo. But is this enough? 3) What to do with undropped packages? * If a package is maintained by community - regardless of the project -, should it be removed from openSUSE:Dropped? * Should it be removed ONLY if the package is in openSUSE:Contrib? Best solution for 2 (in my eyes) could be: Community packager wants to maintain a dropped package => he builds it in his home-Project => he sends a request to the openSUSE:Contrib project => openSUSE:Contrib maintainers are also maintainers of openSUSE:Dropped and can remove the package from openSUSE:Dropped as soon as it is accepted for openSUSE:Contrib With kind regards, Lars -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Le mercredi 04 mars 2009, à 13:06 +0100, Lars Vogdt a écrit :
Hi there
Following the "Package foo needs new maintainer" resp. "Drop request for package foo" mails on opensuse-packaging for a while. Community members already asked for more details when a package is dropped from Factory.
So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an overview about currently dropped packages?
FWIW, for the GNOME team, I try to keep dropped packages available in projects like home:vuntz:Attic_11.0, home:vuntz:Attic_11.1, etc. Build is disabled there but at least it makes it easy for someone to take the package back if he wants. So I think your idea makes at least some sense :-) 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
On Wed, 4 Mar 2009, Lars Vogdt wrote:
Hi there
Following the "Package foo needs new maintainer" resp. "Drop request for package foo" mails on opensuse-packaging for a while. Community members already asked for more details when a package is dropped from Factory.
So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an overview about currently dropped packages?
Means: 1) Packager sends drop request internally
2) Project manager agrees => drop package ^^^^^ Same as before.
3) the latest checked in package source (regardless if successful building or not) is copied into the project openSUSE:Dropped ^^^^^ New - formerly we just moved the source to an internal backup space and marked it as deleted in PDB.
----
4) People can always see, which formerly packages are removed from the current Factory (and therefore will not be in the next release) looking at the openSUSE:Dropped repository 5) Interested community packagers can use/copy the latest source from openSUSE:Dropped
Open questions: 1) Is this idea worth to be implemented?
Yes, I think so.
2) What about packages with security problems? - Publishing should be disabled for all packages in the openSUSE:Dropped repo. But is this enough?
Since they are dropped, they should not be built. Who wants it should be forced to build it themselves.
3) What to do with undropped packages? * If a package is maintained by community - regardless of the project -, should it be removed from openSUSE:Dropped? * Should it be removed ONLY if the package is in openSUSE:Contrib?
Best solution for 2 (in my eyes) could be: Community packager wants to maintain a dropped package => he builds it in his home-Project => he sends a request to the openSUSE:Contrib project => openSUSE:Contrib maintainers are also maintainers of openSUSE:Dropped and can remove the package from openSUSE:Dropped as soon as it is accepted for openSUSE:Contrib
Sounds good. -- Mit freundlichen Gruessen, Andreas Vetter Informations- und Kommunikationstechnik Fakultaet fuer Physik und Astronomie Universitaet Wuerzburg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 4 Mar 2009, Lars Vogdt wrote:
Hi there
Following the "Package foo needs new maintainer" resp. "Drop request for package foo" mails on opensuse-packaging for a while. Community members already asked for more details when a package is dropped from Factory.
So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an overview about currently dropped packages?
Means: 1) Packager sends drop request internally
2) Project manager agrees => drop package ^^^^^ Same as before.
3) the latest checked in package source (regardless if successful building or not) is copied into the project openSUSE:Dropped ^^^^^ New - formerly we just moved the source to an internal backup space and marked it as deleted in PDB.
I would suggest instead of copying to create a versioned source-link to openSUSE:Factory instead. Wait ... this would require a fix for bnc#479945. Richard. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 04 March 2009 13:06:09 Lars Vogdt wrote:
So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an
What about packages which have to be dropped from the distribution for legal/licensing reasons and likely can't be because of that in OBS? Bye, Steve -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Samstag, 7. März 2009 11:39:34 schrieb Stephan Binner:
On Wednesday 04 March 2009 13:06:09 Lars Vogdt wrote:
So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an
What about packages which have to be dropped from the distribution for legal/licensing reasons and likely can't be because of that in OBS?
right, but this happens not really often. I can remember only one case several years ago, where we had to remove a package from ftp server after release. We check these kind of issues before checkin usually ;) 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
participants (6)
-
Adrian Schröter -
Andreas Vetter -
Lars Vogdt -
Richard Guenther -
Stephan Binner -
Vincent Untz