Hi, I'm the maintainer for the distributed-net package. A new version of the package was uploaded to unstable on December 3rd with priority low. As such it was too young when the freeze happened and now can't migrate to etch. I would like to have this package considered for a manual inclusion into etch. The version is testing is 2.9012.497-3 and the version in unstable is 2.9013.498-1 with an interveining 2.9012.497-4. Version 2.9013.498-1 does include a new upstream release, however the changes are minimal and I don't expect that they could cause problems with the timeline for the release of etch. The reason that I'm asking for the update is: Version 2.9012.497-4 fixed 5 outstanding bugs (#99954, #155845, #212871, #346168, #398454). Some of these are rather longstanding, and most of them had the potential to be annoying to the users of the package. So it would be nice if the version that ships with etch could be free of these issues. Since the last version was uploaded one new bug has come up (#402873). While this issue is somewhat annoying it is not the end of the world. So if you're willing to consider the package in testing for an update, it would be nice if I could update it to fix this issue, however I will leave this up to you. Thanks, James
Attachment:
pgpLnxMqfh3bJ.pgp
Description: PGP signature