1.7.01 mainline on debian has installed a wrong package

Server NGINX
1

after running the upgrade to 1.7.01 mainline version on debian, the
nginx
version check (service nginx -V) lists:
0.91-ubuntu1 - even though 1.7.01 is listed in the package manager in
debian.

does this mean that debains repos are serving an incorrect package?

Posted at Nginx Forum:

2

On 27 April 2014 22:37, ura [email protected] wrote:

after running the upgrade to 1.7.01 mainline version on debian, the nginx
version check (service nginx -V) lists:
0.91-ubuntu1 - even though 1.7.01 is listed in the package manager in
debian.

does this mean that debains repos are serving an incorrect package?

You will have more than one repo enabled which is capable of providing
the “nginx” package, I suspect.

Try “apt-cache policy nginx” (or nginx-full, depending on what you
think you have installed) to see the versions your system knows about,
and where it thinks they come from. Then work out how to get the
correct version: disable a repo, or install a different package name,
or apt-pin a version, or something else; you’ll have to have a good
poke at it.

J

3

thanks for assisting. i ran that command and see 3 repos which provide
nginx. from what i see there, the 1.7.0-1 wheezy package is the
candidate
and also has been installed.

i just checked my local development machine which is running lmde - the
version of nginx is also the same spurious ubuntu 0.91 version… yet the
2
machine are using different repos.

i am not seeing 0.91 listed anywhere other than when i run service nginx
-V

Posted at Nginx Forum:

4

On 27 April 2014 23:00, ura [email protected] wrote:

thanks for assisting. i ran that command and see 3 repos which provide
nginx. from what i see there, the 1.7.0-1 wheezy package is the candidate
and also has been installed.

i just checked my local development machine which is running lmde - the
version of nginx is also the same spurious ubuntu 0.91 version… yet the 2
machine are using different repos.

i am not seeing 0.91 listed anywhere other than when i run service nginx -V

“which nginx” will show you the specific binary you’re running when
you execute nginx-V. It may well be a different one from that which
your initscript invokes.

“dpkg -L nginx” (or whichever package you have installed) will show
you which files on disk are from that package.

I suspect you’ll discover your actual problem by examining the the
output of these two commands.

J

5

those two commands don’t show any version numbers, so i am not presently
any
closer to identifying the issue here.
the paths returned look fine to me, from what i know already.

Posted at Nginx Forum:

6

On 27 April 2014 23:14, ura [email protected] wrote:

those two commands don’t show any version numbers

No, they don’t - they show paths.

so i am not presently any
closer to identifying the issue here.
the paths returned look fine to me, from what i know already.

Ok. Good luck finding the problem. Check your init script.

J

7

On Sunday 27 April 2014 17:37:26 ura wrote:

after running the upgrade to 1.7.01 mainline version on debian, the nginx
version check (service nginx -V) lists:
0.91-ubuntu1 - even though 1.7.01 is listed in the package manager in
debian.

does this mean that debains repos are serving an incorrect package?

By running “service nginx -V” you’re checking the version of “service”.

wbr, Valentin V. Bartenev

8

aha! yes, i needed to remove ‘service’.
now i see the correct 1.7 version code. thanks!

Posted at Nginx Forum: