On 11281 March 1977, Dave Hall wrote: >> > I think there is a bit of a problem with internal processes if no one >> > watching the bug queue was advised of this - until now.
For the future you might want to add http://packages.qa.debian.org/p/phpgroupware.html (replacing the package name with whatever you are interested in) as a site to look at. It has some pretty good summaries whats going on with packages, and for the last weeks it also showed that this package is orphaned and requested for removal.[1] >> There are enough sources to know if a package gets orphaned including >> the wnpp-alert tool or the weekly Work-needing packages report mails on >> the debian-devel list... > Ok so as upstream we need to not only watch the bug queues of all the > distros which include packages for our project, but we need to learn the > idiosyncratic process each project uses for deciding if the package/s > are to be dropped? In this case subscribing to a developer centric high > traffic list or use some distro specific tool - you can't be serious. Ideally the maintainer of a package works closely together with upstream and does that work / or tells you what pages like the above mentioned are there. >> and that the package has only few users... > Our nightly build from stable RPMs are popular with users as they > contain many bug fixes which can't be backported to debian. I > understand the debian policy on this stuff, which is why it is my server > distro of choice. There is no reliable way to know how many people run > Debian and use phpGroupWare via the official debs or other sources. Well, the packages are removed from unstable. They will go away from testing as soon as nothing in there depends on them anymore (which in case of phpgroupware might be the case already, so going away soon). They wont go away from stable AKA etch or oldstable AKA sarge. So currently it "only" means no such packages in the upcoming stable release. Updated packages *can* be added to the Distribution again, entering unstable, if there is someone willing to maintain it (or a whole team for it). They got removed because they looked unmaintained (in Debian) *AND* the maintainer was unresponsive to at least two pings from our MIA team. If that someone also talks to the security team / builds the bridge between them and upstream it should be possible to have it in lenny again. (Unless $someone takes way too long and we have frozen before anything gets done). [1] It doesnt show this anymore now, as the removal has been done. -- bye Joerg Five exclamation marks, the sure sign of an insane mind. -- Terry Pratchett, Reaper Man -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
