Michael Pobega wrote:
On Sun, Apr 01, 2007 at 09:05:54PM +0100, Paul Cupis wrote:
On Wed, Mar 28, 2007 at 09:40:06PM -0400, Michael Pobega wrote:
Package: firestarter
Version: 1.0.3-1.3
Followup-For: Bug #338550
It seems that the Etch package for Firestart is indeed broken, because
it happened to me on my system. I just apt-pinned it from unstable
into testing, and purged it, and it purged firestarter from my system
fine.
I had only installed it once, but I never got it to purge right. After
my biweekly cleaning of cruft packages I decided to just report a bug
on it, and it seems this bug was already reported (And, to an extent,
solved). But I just thought I'd throw my two cents in there for anyone
else having the same problem as I did on Debian Etch.
This bug is confirmed in version 1.0.3-1.3 which will be the version
released with Etch. The freeze for Etch means that the fixed package
1.0.3-2 will not make it in.
A bug as annoying as that should still fall through the freeze though,
no? I thought that bug fixes were still allowed to pass through the
freeze?
I have already requested that the release team consider 1.0.3-2 for
Etch, on the basis of the outdated BOGONS file (non-routables) which
already affect users of the package. This request was denied as we are
too close to the release (hopefully over Easter).
See http://lists.debian.org/debian-release/2007/03/msg00773.html for my
request and the reply from the release team. Only fixes for
release-critical bugs are being allowed to pass Etch now, as is proper
for the freeze.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
