Hi Mike, you're right to keep following up on this issue, even though seeing as time flies and the freeze approaches, I'm not sure I'm going to change mutch for vpnc before wheezy. There are a few patches in vpnc-script, some of which are upstream now but not yet synced to vpnc SVN, and others which are deprecated and scheduled to go away after wheezy. I'm not sure it makes sense to start a new vpnc-scripts package based on git and then patch it with legacy stuff that's going away again straight after the release. Also, the mechanism to extend vpnc-script with local snippets is a little different upstream than what has been shipped in several Debian releases, so config files will need to be moved around and taken over by a different package etc. Looking at my time and other plans for wheezy, I'd rather work on this when wheezy is out of the door.
From my perspective, this leaves two ways forward: a) src:vpnc builds a new package vpnc-script(s) containing the script in its current location with legacy patches, perhaps including a few more commits which I expect upstrem to commit to SVN until the end of May; after wheezy, we move on to unpatched vpnc-scripts.git b) you go ahead packaging the git scripts and using them from openvpn, and I move vpnc over to depending on that package when I'm ready. Either way, a new binary package is created, which will need to go through NEW. I recently asked David to include copyright statements in all the vpnc scripts, which he promptly did, so I don't think that's going to be a problem. I'm not sure if shipping the same script twice for some time is going to make somebody mad, though... I'm somewhat AFK for the next seven days; I'd say feel free to choose either path or something else, but let's not stir up the current vpnc package too much at this time. Florian
smime.p7s
Description: S/MIME cryptographic signature
