# Debian package

**URL:** <https://www.ruby-forum.com/t/debian-package/228886>\
**Category:** NGINX\
**Created:** [May 11, 2013, 5:53am UTC](https://www.ruby-forum.com/t/debian-package/228886 "2013-05-11T05:53:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![B.R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@B.R](https://www.ruby-forum.com/u/B.R)\
**Post date:** [May 11, 2013, 5:53am UTC](https://www.ruby-forum.com/t/debian-package/228886/1 "2013-05-11T05:53:47Z")

</div>

Hello,

Is Wheezy supported for Nginx?

Would it be possible to use role-based package selection for the Nginx  
APT  
source?  
That means using:

deb [Index of /packages/debian/](http://nginx.org/packages/debian/) _stable_ nginx  
deb-src [Index of /packages/debian/](http://nginx.org/packages/debian/) _stable_ nginx

Instead of:

deb [Index of /packages/debian/](http://nginx.org/packages/debian/) _squeeze_ nginx  
deb-src [Index of /packages/debian/](http://nginx.org/packages/debian/) _squeeze_ nginx

## Thanks,

_B. R._

---

<div class="post-metadata">

**Author:** ![B.R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@B.R](https://www.ruby-forum.com/u/B.R)\
**Post date:** [May 12, 2013, 12:20am UTC](https://www.ruby-forum.com/t/debian-package/228886/2 "2013-05-12T00:20:07Z")

</div>

On 11 May2013, at 07:52 , B.R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Hello,
> 
> Is Wheezy supported for Nginx?

Not yet. I plan to build packages for wheezy and ubuntu 13.04 in a  
week or two.

> Would it be possible to use role-based package selection for the Nginx APT  
> source?

No, I see potential problems here: nginx binary depends on certain  
libraries versions,  
for example nginx for wheezy will be built with spdy module and thus  
will require  
openssl \>= 1.0.1. But what will be happened when testing becames stable  
and stable -  
oldstable? As far as I understand it may result in someone will install  
wheezy package  
on squeeze and it will not start at all.

---

<div class="post-metadata">

**Author:** ![B.R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@B.R](https://www.ruby-forum.com/u/B.R)\
**Post date:** [May 14, 2013, 7:06pm UTC](https://www.ruby-forum.com/t/debian-package/228886/3 "2013-05-14T19:06:14Z")

</div>

Thanks for your answer.

I don’t really see the problem.

If the user also uses role-based sources (which is not the default  
setting  
in Squeeze, didn’t check in Wheezy), if he tries to get the ‘stable’  
Nginx  
package, then his system has already the ‘stable’ packages from the  
distribution, hence he satisfies all required dependencies.  
When ‘stable’ goes ‘old-stable’ and ‘testing’ goes ‘stable’, on his next  
upgrade, he’ll pull all system packages from the new stable, at the same  
time he pulls the new Nginx package.

In short: Someone can’t pull the ‘stable’ Nginx package without having  
his/her system pulling the ‘stable’ packages from Debian.

Of course, to support users which will need time to make the upgrade to  
the  
new stable, you will need to maintain an ‘old-stable’ package for the  
‘old-stable’ ditribution, hence a version of Nginx that people can  
install  
on Squeeze (without spdy or openssl \>= 1.0.1).  
I suppose that you’ll freeze the ‘old-stable’ at some point (which  
you’ll  
need to decide since 1.4 got out before Wheezy) and only rebuild the  
‘old-stable’ package in cases of security issues.

## IMHO, there is no system incoherence scenario in which someone would try to install the Wheezy-built Nginx on Squeeze using the ‘stable’ role-based sources.

_B. R._