On 15/10/07 at 11:47 +1000, Niv Sardi wrote: > > On Sun, 2007-09-30 at 16:13 +0200, Lucas Nussbaum wrote: > > Hi, > > > > While reviewing packages that were not included in Etch, your package > > came up as a possible candidate for removal from Debian, because: > > > > * 1 RC bug opened for a long time. > > This bug is tagged help for a while and nobody has stepped in.
Still, you are the maintainer, so you are the one supposed to find a way to fix it ... Have you tried contacting the people who could help you? Like the X.org team, or the upstream author? If the bug only affects a small number of systems, you also have the solution to downgrade its severity until you can figure out exactly what's needed to reproduce it... > > * useless with X.org, superseded by skippy-xd. > > It's only superseeded by skippy-xd on systems where composite runs > reasonably fast, witch is only a little share of all. Last time I tried skippy, it was very slow. So, on machines where compositing doesn't work reasonably fast, skippy is also probably very slow... > > If you think that it should be orphaned instead of being removed from > > Debian, please reply to this bug and tell so. > > I've been thinking about orphaning/removing skippy, but I still feel > that it can be usefull to some. Fine, but please try to fix the problems: the package hasn't migrated to testing for over a year and wasn't included in etch. There's not much point in keeping in Debian if it's broken... -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]