Debian Bug report logs - #673648
vpnc: stop to ship vpnc-script and depend on common vpnc-scripts package instead

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Mike Miller <mtmiller@ieee.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: vpnc: split vpnc-script from vpnc for use by openconnect

Date: Sun, 20 May 2012 09:18:47 -0400

Package: vpnc
Severity: normal

Hi Florian, I want to get this done before the upcoming freeze and I
want to have a public record of our discussion.

We've been talking about splitting vpnc-script from vpnc for a few
weeks now but no concrete plans yet.  This could be done from your
vpnc source package or as a new package based on
http://git.infradead.org/users/dwmw2/vpnc-scripts.git .  I have looked
at both options.  The advantage of building from the vpnc source
package is momentum, the script is already there, but the downside is
you need to manually patch and sync changes from dwmw2.  The advantage
of using the git repo is it is more up to date, but it will have to go
through new package approval.

I am leaning towards the second option because the script you include
is already heavily patched, this approach will more accurately capture
the script's origin and make it more clear that it is independent of
either VPN.  I have already started working on packaging dwmw2's git
repo.  I am perfectly willing to take this on if you are ok with this.
 Let me know if you agree.

Thanks.

-- 
mike

Message #10 received at 673648@bugs.debian.org (full text, mbox, reply):

From: Florian Schlichting <fschlich@ZEDAT.FU-Berlin.DE>

To: Mike Miller <mtmiller@ieee.org>, 673648@bugs.debian.org

Subject: Re: Bug#673648: vpnc: split vpnc-script from vpnc for use by openconnect

Date: Sun, 20 May 2012 18:13:25 +0200

[Message part 1 (text/plain, inline)]

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 (application/x-pkcs7-signature, attachment)]

Message #15 received at 673648@bugs.debian.org (full text, mbox, reply):

From: Mike Miller <mtmiller@ieee.org>

To: Florian Schlichting <fschlich@zedat.fu-berlin.de>

Cc: 673648@bugs.debian.org

Subject: Re: Bug#673648: vpnc: split vpnc-script from vpnc for use by openconnect

Date: Thu, 24 May 2012 08:05:00 -0400

On Sun, May 20, 2012 at 12:13 PM, Florian Schlichting
<fschlich@zedat.fu-berlin.de> wrote:
> [...]
> 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?

> 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.

> [...]
> 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.

Yes, I completely understand that you have a working package and
configuration and that it's probably more work for you to migrate to a
different setup than for me to add a new feature.

If you agree that the best long-term solution is a separate
src:vpnc-scripts package, then I will start working on that.

Thanks for your feedback.

-- 
mike

Message #20 received at 673648@bugs.debian.org (full text, mbox, reply):

From: Mike Miller <mtmiller@ieee.org>

To: Florian Schlichting <fschlich@zedat.fu-berlin.de>

Cc: 673648@bugs.debian.org

Subject: Re: Bug#673648: vpnc: split vpnc-script from vpnc for use by openconnect

Date: Tue, 29 May 2012 22:27:47 -0400

On Thu, May 24, 2012 at 8:05 AM, Mike Miller <mtmiller@ieee.org> wrote:
> If you agree that the best long-term solution is a separate
> src:vpnc-scripts package, then I will start working on that.

I have finally gotten around to filing an ITP for vpnc-scripts [1] and
will be working on getting that package into Debian shortly.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675131

-- 
mike

Message #25 received at 673648@bugs.debian.org (full text, mbox, reply):

From: Florian Schlichting <fschlich@ZEDAT.FU-Berlin.DE>

To: Mike Miller <mtmiller@ieee.org>, 673648@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#673648: vpnc: split vpnc-script from vpnc for use by openconnect

Date: Thu, 31 May 2012 21:54:46 +0200

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

Message #36 received at 673648-close@bugs.debian.org (full text, mbox, reply):

From: Florian Schlichting <fsfs@debian.org>

To: 673648-close@bugs.debian.org

Subject: Bug#673648: fixed in vpnc 0.5.3r550-1

Date: Sat, 06 Sep 2014 22:34:34 +0000

Source: vpnc
Source-Version: 0.5.3r550-1

We believe that the bug you reported is fixed in the latest version of
vpnc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 673648@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Florian Schlichting <fsfs@debian.org> (supplier of updated vpnc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 07 Sep 2014 00:18:19 +0200
Source: vpnc
Binary: vpnc
Architecture: source amd64
Version: 0.5.3r550-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting <fsfs@debian.org>
Changed-By: Florian Schlichting <fsfs@debian.org>
Description:
 vpnc       - Cisco-compatible VPN client
Closes: 595660 673648
Changes:
 vpnc (0.5.3r550-1) unstable; urgency=medium
 .
   * Import Upstream version 0.5.3r550
     + ignores leading/trailing whitespace in config file (closes: #595660)
     + fetches split DNS information (LP: 954747)
     + includes 03_vpnc.8.patch
   * Add VCS-* fields
   * Update fix_makefile_VERSION.patch to report full Debian package version
   * Email change: Florian Schlichting -> fsfs@debian.org
   * Update copyright holders and years
   * Remove deprecated "Target networks" and "DNSupdate" extensions
   * Move user-created connect-action scripts to the new hook directories
   * Use vpnc-script from the vpnc-scripts package (closes: #673648)
   * Add a NEWS file to alert people with non-default configurations
   * Drop fix_make_test.patch, cert issue fixed upstream
   * Declare compliance with Debian Policy 3.9.5
Checksums-Sha1:
 d93d39b1c651df39a3d6008734946387fdd763be 1868 vpnc_0.5.3r550-1.dsc
 519fb5b09c03bde3d2a850f6b018a9ca6beba0ff 128136 vpnc_0.5.3r550.orig.tar.gz
 51dd8c611d4f072ec7d62581029d635e6d8d17e6 10420 vpnc_0.5.3r550-1.debian.tar.xz
 10f2928cfce6e259447d149a2da6499b52dc9cef 80184 vpnc_0.5.3r550-1_amd64.deb
Checksums-Sha256:
 cae4af05d2af2aea02d5ca2bfa94aa9a9708c132a0aeb3e1cfea5689031bc651 1868 vpnc_0.5.3r550-1.dsc
 a6afdd55db20e2c17b3e1ea9e3f017894111ec4ad94622644fc841c146942e71 128136 vpnc_0.5.3r550.orig.tar.gz
 c9fdf3b93713efa060e75980832ee9f59eedad256db9d7e1cfcce7ec578e52c6 10420 vpnc_0.5.3r550-1.debian.tar.xz
 3cd099421d01f65e82c6a740fd81ee19573cba9453ee9766160e1ec5e62ec76b 80184 vpnc_0.5.3r550-1_amd64.deb
Files:
 68f13a54342ccd823b6084179ff57529 80184 net extra vpnc_0.5.3r550-1_amd64.deb
 44299e294930b94a996d7ba7c51e2a71 1868 net extra vpnc_0.5.3r550-1.dsc
 44a471f529f1d33e0f8223ef1eee52be 128136 net extra vpnc_0.5.3r550.orig.tar.gz
 94f39aa30409502b23a03ddb1c6e78fe 10420 net extra vpnc_0.5.3r550-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUC4mgAAoJEBKXO25y3Ae1dnAP/A7UnmqT4oKykvNvKD6vt63k
ArPktaleVclXzOUSEmYtxXHRquKyVix5opeb4GnWQUduTgVM1x7Yr1pIUVgjTUxu
GeDOqtIrOPbqMLBpJmlbRVXwkrvMzw8CsHtXCFEE2OMB2VRIqZvEqDQfZEby7iWf
KEx+9GevhmSnjmZHyXR0bNZaZgXd92XlrLFtbGtkvPufAEZbUahgCcdiHv0sJL1O
z3xVM1GlBn0ZwftSV/ZYza3hCtoAb8MS1t23Kaho6R1659mAryJw7IJ1FKUC82bq
ZvZlm3Z2y34JVAD6RJ9a7ODhLJNA5618eYt8euKXHwsg0zUxxl+3CsIPv6lNB63r
HfBPIa0cDN6xYwMujP4hnp9G47l2JX+uC+5yktLasel7S52SH7wco/Tt7jKwQHGe
5fQotbGjSoZRaH1GekmoG2DTDqB08q199eIsJkiWJ3vVPzHFjeWS5XgqruQdDiSM
p3+RgFU8tfj7DKf7yy8RMONgpG6uEXuo6zyeEjHA2UuapjTQO6tpo0jluGvUVM1q
HpctfgKDIABSrKEiqpfXvMEaoBK7kLUcsRWdag5ZouqNHxmvT1ZSgm4nE/FlzA3P
oQPHVer9MlKM6U8MpSPkeyW50OSnZdVvpf9OFKTrZ06B4pZhdddQZKI7l9GbVNDW
Gj2I3h2RzUkK2uj9Vk2u
=a74W
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.