Le 07.01.2007, à 12:18:29, Jason Day a écrit: > On Sun, Jan 07, 2007 at 05:15:19PM +0100, Ludovic Rousseau wrote: > > Package: jpilot-syncmal > > Severity: serious > > Justification: Policy 7.6 > > > > jpilot-syncmal 0.73 has a Build-Depends: libmal-dev (>= 0.42-1) but > > libmal-dev has been removed from Debian on my request, see #394544 > > This is the first I've heard of bugs 394544 or 389353. I guess I'm not > subscribed to the debian libmal bug tracker, but nobody forwarded the > bugs to me. I will admit that I am pretty slow to update libmal, but I > haven't stopped maintaining it. In fact, I just released version 0.43 > last month. Perhaps this fixes 389353?
The problem now is not with a bug in jpilot-syncmal or libmal but that libmal and libmal-dev are no more in Debian. So jpilot-syncmal can't be built any more. > > I now file a RC bug (this one) and a request to remove jpilot-syncmal > > (#405946). > > > > jpilot-syncmal should not be distributed in Etch and can be removed from > > testing until it is completely removed also from unstable. > > It seems there are very few users of jpilot-syncmal and libmal now. > Both packages recently had a serious bug that went unnoticed for months. > It's true that I no longer use them directly myself, but I will continue > to fix bugs (that I know about). If 389353 is the only reason for > removing libmal and jpilot-syncmal, then please reconsider. I offered malsync for adoption in [1] but got no positive answer. I do not use malsync, jpilot-syncmal or any libmal related software since some time now. So I am not in a good position to maintain these packages. Bye, [1] http://lists.debian.org/debian-devel/2006/10/msg00663.html -- Dr. Ludovic Rousseau [EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
