[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-29 Thread Mike Miller
The latest openconnect 3.20-1 release builds in Lucid. https://launchpad.net/ubuntu/+source/openconnect/3.20-1 ** Changed in: openconnect (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread dwmw2
This should fix it sanely on Lucid, I think: http://david.woodhou.se /lucid-openssl-compat.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955371 Title: Build deps don't reflect failure of

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread Mike Miller
Fixed patch to this, still fails to build: dtls.c: In function 'dtls_try_handshake': dtls.c:321: error: 'BIO_CTRL_DGRAM_SET_TIMEOUT' undeclared (first use in this function) dtls.c:321: error: (Each undeclared identifier is reported only once dtls.c:321: error: for each function it appears in.)

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread Ubuntu Foundation's Bug Bot
The attachment lucid-openssl-compat.patch of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread Mike Miller
** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955371 Title: Build deps don't reflect failure of simple backport on Lucid's openssl To manage notifications about this bug go

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread dwmw2
OK, doing this blind from the OpenSSL CVS history probably isn't the sanest approach; the whole point being that Lucid's OpenSSL has diverged somewhat from any upstream version that ever existed? Can I have a shell on a Lucid box? http://david.woodhou.se/authorized_keys {,asc} -- You received

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread Mike Miller
I can't help you with access to a shell, maybe someone else can, I'm building in a chroot for this and will eventually set up a Lucid VM for further testing. If you want to see if you can use the static version of the Lucid build with your --with-openssl option, you can try this: mkdir lucidssl

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread dwmw2
This one is even tested (albeit with my own build of Lucid's OpenSSL from its source, statically linked and run on Fedora): http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/0c94594f88 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-10 Thread Mike Miller
Great, thanks David! Builds and works on my freshly installed Lucid VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955371 Title: Build deps don't reflect failure of simple backport on Lucid's

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-09 Thread Mike Miller
Confirmed. This will be fixed in 3.18-2. ** Changed in: openconnect (Ubuntu) Status: New = In Progress ** Changed in: openconnect (Ubuntu) Assignee: (unassigned) = Mike Miller (mtmiller) -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-09 Thread dwmw2
Er, you have a version of OpenSSL 0.9.8g which *has* the Cisco DTLS compatibility backported (otherwise you wouldn't be building this code at all), but which *doesn't* have BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT? Um do we really care about making it work with that strange version of OpenSSL, or can

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-09 Thread dwmw2
Something like http://david.woodhou.se/openssl-wtf.patch should make it build, perhaps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955371 Title: Build deps don't reflect failure of simple

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-09 Thread Mike Miller
I was going to go with the latter, simply require 0.9.8m and newer. I'd say this was an oversight when I took over the Debian package and updated from 3.02 to 3.15. Backporting to lucid would require backporting openssl as well. -- You received this bug notification because you are a member of

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-05-09 Thread dwmw2
I could probably do with making upstream build on lucid anyway. Can you show me what the dtls1_stop_timer() function looks like there? Ideally I can reproduce its effects somehow, or failing that I'll just make it build without DTLS there. It really does suck that dtls1_stop_timer() is hidden

[Bug 955371] Re: Build deps don't reflect failure of simple backport on Lucid's openssl

2012-03-14 Thread Phil M
** Description changed: When I try to build on Lucid, I get the following compiler errors: - CC openconnect-dtls.o +   CC openconnect-dtls.o dtls.c: In function ‘dtls_try_handshake’: dtls.c:310: error: ‘struct dtls1_state_st’ has no member named ‘next_timeout’ dtls.c:311: