[Bug 992543] Re: 0.5.3r512 cannot be built with dpkg-buildpackage due to unexpected upstream changes

2012-05-01 Thread Reuben Firmin
Launchpad wouldn't let me attach it. Here's a paste of the file: Description: short summary of the patch TODO: Put a short summary on the line above and replace this paragraph with a longer explanation of this change. Complete the meta-information with other relevant fields (see below for

[Bug 992543] Re: 0.5.3r512 cannot be built with dpkg-buildpackage due to unexpected upstream changes

2012-05-01 Thread Stefano Rivera
We use quilt for managing patches http://wiki.debian.org/UsingQuilt Or if you don't want to learn how to use it, just use dpkg-source --commit, as the error suggests. ** Changed in: vpnc (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of

[Bug 992543] Re: 0.5.3r512 cannot be built with dpkg-buildpackage due to unexpected upstream changes

2012-05-01 Thread Reuben Firmin
That's fine (and I will look into it), but did this deliberately change between 0.5.3r449 and 0.5.3r512? Surely there were patches in r449 that did not trip up buildpackage. Per my description, the buildpackage route worked fine on 0.5.3r449. Reopening just to get an answer for this. If yes then

[Bug 992543] Re: 0.5.3r512 cannot be built with dpkg-buildpackage due to unexpected upstream changes

2012-05-01 Thread Stefano Rivera
Note in the changelog entry for 0.5.3r449-3: * Use source 3.0 (quilt) 3.0 (quilt) is used in most packages these days: http://upsilon.cc/~zack/stuff/dpkg-v3/ Please stick your nose into #ubuntu-packaging, if you want some help. ** Changed in: vpnc (Ubuntu) Status: New = Invalid --

[Bug 992543] Re: 0.5.3r512 cannot be built with dpkg-buildpackage due to unexpected upstream changes

2012-05-01 Thread Mathieu Trudel-Lapierre
Unfortunately, we can't even ship vpnc with that change, since the actual license violation remains an issue which prohibits us shipping the package. If you want to email me to explain the reason why you need vpnc to be compiled against OPENSSL, which I thought we had already all fixed in recent