Cannot start shellinabox with ssl enabled about shellinabox

[GoogleCodeExporter]

I built the packages on Karmic. It is quite possible that Hardy is too old for 
the 
binary packages. Can you try building from source and see if that gives you a 
package 
that works for you?

The INSTALL.Debian file has detailed instructions on how to build a new package.

Original comment by [email protected] on 26 Nov 2009 at 5:42

[GoogleCodeExporter]

Yes compiling from source on the hardy box worked fine.

Original comment by [email protected] on 26 Nov 2009 at 6:40

[GoogleCodeExporter]

I am glad to hear that recompiling fixes the problem for you.

This is a general issue with releasing binary packages. It is hard or even 
impossible 
to create binary packages that work for everybody. In general, building from 
source 
is much safer.

I occasionally contemplate not offering any binary packages, but it seems that 
for 
some users having to built from source is a major hurdle -- and if the binary 
package 
happens to work for them, then they are very well served by it. It's all a big 
trade-
off.

For now, I'll close this bug -- even though, I don't have a good solution that 
would 
make everybody happy.

Original comment by [email protected] on 26 Nov 2009 at 6:47

• Changed state: WontFix

[GoogleCodeExporter]

I've created a ppa on launchpad where I'll put pre-built packages for Ubuntu. 
Dunno if 
that's useful to you/anyone.

https://edge.launchpad.net/~popey/+archive/shellinabox

So far I've added karmic, but the build for hardy fails. See attachment.

Will play a bit more..

Original comment by [email protected] on 26 Nov 2009 at 6:57

Attachments:

• hardybuildfail.txt

[GoogleCodeExporter]

Ok, fixed that after speaking to experts in #ubuntu-motu :)

Once launchpad has some capacity there should be binaries for hardy, jaunty and 
karmic. I'll give lucid a bash once that's stable - given it's LTS.

Original comment by [email protected] on 26 Nov 2009 at 7:14

[GoogleCodeExporter]

Yes, that build failure is a little annoying. Something keeps resetting the 
compatibility level for no good reason. You can safely decrease it back to six.

I'll put something into my build scripts to always reset it going forward.

As for the PPA on Launchpad, that sounds like a great idea. Let me know, when 
it is 
fully populated and I'll link to it from the project's front page.

Also, I'd love to find somebody who can sponsor the project so that it becomes 
an 
official Debian and/or Ubuntu package. Having it become part of the 
distribution 
would be a great way of making sure that users get properly built binary 
packages. 

But I am not quite aware of what the steps are to get this done. So, if you 
have any 
insight, I'd appreciate your help.

Original comment by [email protected] on 26 Nov 2009 at 9:02

[GoogleCodeExporter]

http://mentors.debian.net/

Is apparently the best place to start. File an ITP bug in debian to get your 
package 
in there. Once in Debian it will filter to Ubuntu.

Original comment by [email protected] on 26 Nov 2009 at 9:43

[GoogleCodeExporter]

https://edge.launchpad.net/~popey/+archive/shellinabox

Now in the ppa.

Original comment by [email protected] on 27 Nov 2009 at 9:26

[GoogleCodeExporter]

Thanks. I added a link to the project's home page.

Original comment by [email protected] on 30 Nov 2009 at 9:33