This https://wiki.ubuntu.com/MOTU/SRU documents the procedure to get an bug-fix into a stable release. There are three possible conditions of which at least one needs to be met in order to commit a bug-fix. For this, "Bugs which represent severe regressions from the previous release of Ubuntu" might apply. I do not know how great a percentage of users of vpnc is affected, but since this bug get comments from 10+ people affected, I think this condition is met.
>From what I understand, this also mean that the bug open for >network-manager-vpnc will not get fixed for Feisty. For Gutsy it could be >solved if upstream commited the changes (or if someone else wrote a patch that >would be merged with Gutsy's version of the package) but I am afraid they >would (and I think correctly) say that this needs to be solved in vpnc itself >so I doubt they would add the configuration option. Therefore, I think the best way to solve this (until it gets "properly" solved in upstream) is to revert the patch (06_stolen_from_head) (actually, an ideal would be if someone reviewed the patch and removed only those parts that directly cause this bug). Well, now, according to the procedure, a MOTU is needed for agreeing with the fix. For Gutsy, this wil hopefully get included as well, but there is time for that at least until August 16th, the https://wiki.ubuntu.com/UpstreamVersionFreeze. -- vpnc dead peer detection disconnects immediately https://bugs.launchpad.net/bugs/93413 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
