Taking a look back at this, Ubuntu carried a unique change so it was not automatically sync'ed. Up until this bug was filed, no one looked to see if the package needed to be updated. At this point we were past feature freeze and so it needed extra approvals. We need two separate plans:
1. Hardy: Prepare an update to address the serious bugs (no one appears to have filed a "mailscanner won't work at all" bug yet. a. File such a bug with a patch (see step 3 in procedure in https://wiki.ubuntu.com/StableReleaseUpdates for what needs to be in such a bug). Subscribe me to the bug. b. I'll take that and prepare an upload. I'll also address the RC bug fix that caused this bug to be files (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472489). c. Once I get that uploaded to hardy-proposed, it will need testing. d. Once tested it gets released to hardy-updates and we have a working (if old) mailscanner. 2. Intrepid: Request a sync a. I'll do that. Once sync's are processed, then it will update automatically from Debian up to Debian Import Freeze. 3. Hardy part two: Request a backport Once it's in Intrepid: a. build and test this version in Hardy. b. If it works, ask for a backport (https://bugs.launchpad.net/hardy-backports/+filebug) see https://wiki.ubuntu.com/BackportRequestProcess c. Once it's approved, the archive admins will add it to hardy-backports and the current version will be available through official Ubuntu repositories for Hardy. -- [FFe] Please sync mailscanner 4.66.5-2 from Debian(Unstable) https://bugs.launchpad.net/bugs/204546 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
