Hello,
I was experimenting with nginx and, since I want all dependencies and
updates managed easily and without regular compilation on my own, I
chose a Debian package. However, upon trying to start my initial test
setup the system answers:
bjoern@schiller:~$ sudo /etc/init.d/nginx start
Starting nginx: 2008/05/23 11:18:35 [emerg] 6366#0: unknown directive
“ssl” in /etc/nginx/nginx.conf:32
Do I have to activate ssl before I use “ssl on”, or is it simply that
the package was compiled without SSL support? Can I somehow see what
flags nginx was compiled with?
Greetings,
Björn
On Fri, 23 May 2008 11:22:54 +0200
Björn Keil [email protected] wrote:
Do I have to activate ssl before I use “ssl on”, or is it simply that
the package was compiled without SSL support? Can I somehow see what
flags nginx was compiled with?
SSL support must be enabled at compile-time. You can check which build
options were passed to the configure script by issuing “nginx -V” in a
terminal. My bet is that the Debian packager disabled SSL…
Cheers,
Björn Keil wrote:
Do I have to activate ssl before I use “ssl on”, or is it simply that
the package was compiled without SSL support? Can I somehow see what
flags nginx was compiled with?
What does “strings which nginx | grep ‘configure arguments’” say?
2008/5/23 Björn Keil [email protected]:
I was experimenting with nginx and, since I want all dependencies and
updates managed easily and without regular compilation on my own, I
chose a Debian package. However, upon trying to start my initial test
setup the system answers:
It’s probably bad form to post a link to my own site but I wrote this
while trying to add SSL to the Debian nginx package so it might help
you along -
http://blog.unixdaemon.net/cgi-bin/blosxom.pl/operatingsystems/linux/debian/rebuilding_debian_packages.html
HTH,
Dean
Thanks for your replies… I build my own nginx and now it does indeed
work. Guess I gotta maintain this myself now, but this way I could also
compile the upstream hash module in.
Am Freitag, den 23.05.2008, 11:22 +0200 schrieb Björn Keil:
On Fri, 2008-05-23 at 11:19 +0100, Dean Wilson wrote:
2008/5/23 Björn Keil [email protected]:
I was experimenting with nginx and, since I want all dependencies and
updates managed easily and without regular compilation on my own, I
chose a Debian package. However, upon trying to start my initial test
setup the system answers:
It’s probably bad form to post a link to my own site
As long as it’s relevant, it’s perfectly acceptable.
Regards,
Cliff
On Fri, May 23, 2008 at 09:15:07AM -0700, kingler wrote:
I believe the Debian nginx package is pretty old version as well.
Etch(Stable) branch is version 0.4.13
Debian -- Error
I wish I knew more about Debian packaging. But if someone is familiar
with the packaging process, maybe he could ping the maintainer of the
package and offer assistance to update the nginx package. It will
definitely make things easier for nginx first-timers to try out on
Debian platform.
Actually, I created Debian packages some time ago.
I may include them in tarball, however, I have no Debian to test it.
BTW, is it possible to create packages without updating package
changelog ?
I believe the Debian nginx package is pretty old version as well.
Etch(Stable) branch is version 0.4.13
http://packages.debian.org/etch/nginx
I wish I knew more about Debian packaging. But if someone is familiar
with the packaging process, maybe he could ping the maintainer of the
package and offer assistance to update the nginx package. It will
definitely make things easier for nginx first-timers to try out on
Debian platform.
-Liang
Igor S. wrote:
definitely make things easier for nginx first-timers to try out on
Debian platform.
Debian has a backports repository,[0] where one can use via APT to grab
newer nginx packages built against the current (etch) and oldstable
(sarge) Debian dependencies. Current backport version is
0.5.35-1~bpo40+1.
[0] http://www.backports.org
Also, there is a concise list of all nginx packages available across
Debian versions on the Package Tracking System;[1] with some knowledge
of Debian’s packaging infrastructure, it is possible for one to backport
more recent versions of the nginx package (or even the latest 0.6.31
source, just needing Debian-specific configuration,) to older Debian
releases.
[1] Debian -- Package Search Results -- nginx
Actually, I created Debian packages some time ago.
I may include them in tarball, however, I have no Debian to test it.
BTW, is it possible to create packages without updating package changelog ?
Yes, if you’re using the full Debian packaging infrastructure with
devscripts,[2] you can do a debuild on the unpacked source root
directory with the debian/ tree on it to do a build, regardless of
whether the changelog is updated. Furthermore, you can do a build that
doesn’t generate GPG-signed .dsc and .changes files by doing a debuild -us -uc instead.
[2] Debian -- Package Search Results -- devscripts
Cheers,
Zakame
José Miguel Parrella Romero wrote:
Feel free to file a bug in the Debian BTS [1] if you need a specific
compile option or feature added to the package.
[1] http://bugs.debian.org/nginx/
the link should be http://bugs.debian.org/nginx
Cheers,
Jozef
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
kingler escribió:
I believe the Debian nginx package is pretty old version as well.
Etch(Stable) branch is version 0.4.13
Debian -- Error
I wish I knew more about Debian packaging. But if someone is familiar
with the packaging process, maybe he could ping the maintainer of the
package and offer assistance to update the nginx package. It will
definitely make things easier for nginx first-timers to try out on
Debian platform.
Hello,
Me and Fabio Tranchitella are the maintainers of the nginx package in
Debian, which is also sync’ed with Ubuntu (from Sid)
Debian 4.0 (Etch) shipped with an old nginx because an update was not
allowed by the Release Managers at the moment. Debian Lenny and Debian
Sid have up-to-date nginx packages at the moment.
Hopefully Debian Lenny will release with a 0.6 release. The absolute
minimum will be 0.5.35.
We’re also planning to include 0.7 in experimental in the next week. We
are also handling the package metadata using SVN, so updates are
really easy in every branch (except Etch :))
Feel free to file a bug in the Debian BTS [1] if you need a specific
compile option or feature added to the package.
[1] http://bugs.debian.org/nginx/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIOC/8UWAsjQBcO4IRAlMuAKCF2ShoZqU5aAser20tXeA4ZAQJ3gCgjQYb
4auq4pMq0dWjvO00jW+A7jo=
=fjam
-----END PGP SIGNATURE-----
kingler wrote:
I believe the Debian nginx package is pretty old version as well.
Etch(Stable) branch is version 0.4.13
Debian -- Error
I wish I knew more about Debian packaging. But if someone is familiar
with the packaging process, maybe he could ping the maintainer of the
package and offer assistance to update the nginx package. It will
definitely make things easier for nginx first-timers to try out on
Debian platform.
-Liang
The Debian philosophy is not make any version upgrades in stable
distribution. Only security ones. This way the stability and safe
upgrading is achieved. The testing version is the place where the
upgrades happens. It’s possible to mix stable and testing or there are
the backports, if anyone needs recent version then there is in stable.
Cheers,
Jozef