Who the HELL has approved to submit openvpn-2.0.4-r1 to x86?????????? It is broken as well as the submitter's mind. Sorry! I expected the x86-tag to be stable and don't need to care about migration problems and instead the ebuild was NOT tested by the submitter or even the comitter. 2.0.4-r2 works back again. No excuses please. Just FIX this! Reproducible: Always Steps to Reproduce: Guess how... Actual Results: Broken VPN Expected Results: Working VPN Change the comitter please!
Excellent, absolutely useless bug. What about posting some error messages and actual problems instead of ranting and insulting developers, huh? INVALID.
The only comment that is useless is yours. Look into the ebuild, big master, and you will see the obvious error. Just a hint for you ebuild-experts (openvpn.init). If you can submit faulty ebuilds, you can also track errors.
OK, here's the story 2.0.4 was added to the tree with the new init script, then it was bumped to stable due to a security bug (x86 and ppc where affected) We whipped that out and then added 2.0.4-r1 with the original init script and 2.0.4-r2 with the new init script. So the init script for 2.0.4-r1 is the same one that the stable arches have always had, 2.0.4-r2 getting the new script. Sorry for the inconvenience caused.
