> I made the bisect on your git repo and the bad commit seems to be
> cb394e1acb7565c4d918fd8662009a74c7b32758
> In other words, 8dbfc0191aa815d5ab70c9ca6246cdf9356387f2 is the last
> working commit/revision.
that's interesting, so what breaks vpnc for you is one of the upstream
changes between r481 and r512. Looking at the diff, there are a lot of
changes to vpnc-script, which was renamed from vpnc-script.in. The MTU
calculation in particular was changed, and an option was introduced to
set the MTU from the commandline / config file ('--ifmtu 1412').
"Everything halts until the server terminates a stale connection" could
very well be an MTU issue. You may try running vpnc with the above
option, or add 'set -x' at the top of vpnc-script and compare the output
to see what's happening.
> I also checked out upstream svn trunk in order to find the last working
> revision, but, so far, I could not find any revision that actually
> works. I have no clue why -- my expectation was that r449 should be
> working, but it is not.
>
> Now, a few questions come into my mind:
> 1. Which debian git revision was used for the debian package
> vpnc_0.5.3r449-3_amd64.deb? From which upstream svn revision was that
> git revision created?
The revision tagged debian/0.5.3r449-3, that is
ecf8c6f28d19873c1acf51383a361ee03af9d6a3
> 2. How about debian patches, are they already included in the git repo?
The are located in debian/patches/, as quilt patches; they are
automatically applied when you download a source package with 'apt-get
source', but you will have to apply them manually when just checking out
the git repo (setting QUILT_PATCHES=debian/patches in ~/.quiltrc may
help)
> 3. Is there an easy way to build debian packages from the git tree? When
> bisecting I used to do the builds via a simple "make" command. Is this
> the exact way the code is compiled when debian packages are generated?
The clean way is to build in a minimal chroot using a tool such as
sbuild or pbuilder/cowbuilder. Using debuild or 'dpkg-buildpacke -uc
-us' should do about the same without the chroot. Either way will make
sure the available Debian patches are applied.
As the vpnc sources don't need configuration in order to be built, a
simple 'make' yields a valid result (provided you have applied the
Debian patches), but 'make install' will go to /usr/local, and when run
directly from the build tree without installation, vpnc will still call
vpnc-script vom /etc/vpnc by default, so be careful which script is used
when debugging.
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
