On Mon, 26 Feb 2007 22:39:29 +0200, Ville Skyttä wrote: > > > Of course it's possible that removing an orphan will break a non orphan > > > package, so what do we do there? Let it be broken and the maintainer > > > can bring the orphan back if they want? > > > > Is that a problem? Removing the orphans would create a broken deps report > > in that case and mail all package owners that depend on the orphan. If it > > happens early enough, there should be plenty of time to find a new owner > > and rebuild the package. > > This is certainly not something I'd like to see in non-devel distros, > especially if the mindset for fixing the resulting broken dep chains is that > there's "plenty of time" to do it. But perhaps that's not what you meant for > non-devel distros? Restoring the packages (after running into unexpected broken deps) could be as easy as copying them into the repository or resubmitting a build job for the last known tag. In my view, "broken deps" imply that there are package owners, who depend on the orphans and who need to decide on what to do with the orphans. The least thing that should happen for non-devel branches is to put these package owners into the Cc field of the orphans. -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
