retitle 673648 vpnc: stop to ship vpnc-script and depend on common vpnc-scripts package instead block 673648 by 675131 thanks
Hi Mike, > > 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 > > When you say move to vpnc-scripts.git, do you mean a separate > src:vpnc-scripts package? well, I've seen packages collecting several sources from different places, but it doesn't make things easier. So: yes > > 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. > > If your answer to the above was "yes", then these both end up at the > same long-term conclusion, correct? It's just a difference in how we > get there. yes. > I have finally gotten around to filing an ITP for vpnc-scripts [1] and > will be working on getting that package into Debian shortly. Thank you, I think that's a good way forward. You solve things for openconnect now, and I move vpnc over to depend on that work and package after wheezy. I leave this bug open as a reminder. Florian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
