On Sun, 2011-11-27 at 11:26 +0800, Antonio Borneo wrote:
> On Sat, Nov 26, 2011 at 5:14 PM, David Woodhouse wrote:
> > On Fri, 2011-11-25 at 08:24 +0800, Antonio Borneo wrote:
> >> no reason, should be applied.
> >> I'll commit it in the weekend.
> >
> > If you don't want to just delete vpnc-scrip
On Sat, Nov 26, 2011 at 5:14 PM, David Woodhouse wrote:
> On Fri, 2011-11-25 at 08:24 +0800, Antonio Borneo wrote:
>> no reason, should be applied.
>> I'll commit it in the weekend.
>
> If you don't want to just delete vpnc-script from the vpnc repo, then it
> would be best to pull in *all* the fi
On Fri, 2011-11-25 at 08:24 +0800, Antonio Borneo wrote:
> no reason, should be applied.
> I'll commit it in the weekend.
If you don't want to just delete vpnc-script from the vpnc repo, then it
would be best to pull in *all* the fixes from the git tree rather than
diverging.
In fact, if you wan
On Thu, Nov 24, 2011 at 6:29 AM, Florian Schlichting
wrote:
> David, Antonio, Eric:
>
> On Sat, Sep 10, 2011 at 09:45:17AM +0100, David Woodhouse wrote:
>> On Sat, 2011-09-10 at 15:52 +0800, Antonio Borneo wrote:
>> >
>> > In the fix you provide,
>> > 1) you add ";s/ipid 0x//g" at the end of s
On Wed, 2011-11-23 at 23:29 +0100, Florian Schlichting wrote:
> > I was just thinking that I should submit a patch which removes the
> > out-of-date script from vpnc altogether. There have been a number of
> > other fixes in the git tree too.
>
> What do you mean "remove" the script from vpnc - ho
On Wed, Nov 23, 2011 at 10:34:40PM +, David Woodhouse wrote:
> Note: That "fuzz" you speak of when applying the patch... that's due to
> the rest of the fixes to vpnc-script since it was imported into its own
> git repo, surely?
yes, the line numbers don't match - there are another 23 lines in
David, Antonio, Eric:
On Sat, Sep 10, 2011 at 09:45:17AM +0100, David Woodhouse wrote:
> On Sat, 2011-09-10 at 15:52 +0800, Antonio Borneo wrote:
> >
> > In the fix you provide,
> > 1) you add ";s/ipid 0x//g" at the end of string.
> >This does not impact backward compatibility. I'm in fav
On Sat, 2011-09-10 at 15:52 +0800, Antonio Borneo wrote:
>
> In the fix you provide,
> 1) you add ";s/ipid 0x//g" at the end of string.
>This does not impact backward compatibility. I'm in favour to
> commit it.
It's not sufficient. We originally had this in the vpnc-scripts.git
repositor
(Resending to Debian bug since I just got a bizarre complaint that my
reply didn't have a Package: line at the start. Perhaps it didn't like
the original mail being S/MIME signed?)
On Sat, 2011-09-10 at 15:52 +0800, Antonio Borneo wrote:
> In the fix you provide,
> 1) you add ";s/ipid 0x//g" a
Antonio Borneo wrote:
> Hi Jason,
> I added in copy the list vpnc-devel.
That's a good idea.
>
> In the fix you provide,
> 1) you add ";s/ipid 0x//g" at the end of string.
>This does not impact backward compatibility. I'm in favour to commit it.
>Could you please provide, as refere
On Fri, Sep 9, 2011 at 2:31 PM, Jason White wrote:
> Package: vpnc
> Version: 0.5.3r449-2.1
> Severity: normal
>
> The provided vpnc-script is not compatible with recent versions of iproute,
> apparently, as the output format has changed corresponding to version 2.6.39
> and later of the kernel. (
Package: vpnc
Version: 0.5.3r449-2.1
Severity: normal
The provided vpnc-script is not compatible with recent versions of iproute,
apparently, as the output format has changed corresponding to version 2.6.39
and later of the kernel. (It isn't clear to me whether the change was in the
kernel itself
12 matches
Mail list logo
