-1

What's the best way to keep packages up-to-date (ie with the last security fixes) without worried about major version update ?

For instance, apache2 for squeezeis is 2.2.16 (https://packages.debian.org/source/squeeze/apache2)

However, last apache2 version for the 2.2.x branch is 2.2.27

Test repository can't be used since they use the 2.4.x versions and I'd like to stick on the 2.2.x (to avoid migration issues)

How would you handle this situation and how can I update to 2.2.27 ?

Quentin
  • 101
  • 1
  • You understand that generally people backport security fixes right? Looking at only the version number is often meaningless. – Zoredache Aug 25 '14 at 15:46
  • So you are saying that package are up to date with security backport and different version names ? However some package don't seem up do date at all (ie last tomcat6 security fix is from 2013 - http://metadata.ftp-master.debian.org/changelogs//main/t/tomcat6/tomcat6_6.0.35-1+squeeze4_changelog) – Quentin Aug 25 '14 at 16:02

1 Answers1

0

Usually just upgrading your packages from native repositories should be enough provided you have security.debian.org repository enabled in /etc/apt/sources.list.

At the moment limited "LTS" support is only available for previous ("oldstable") Debian release codename "squeeze". Read the following page for instructions how to configure your system to pull LTS updates:

From security prospective it is always better to use current Debian release a.k.a. "stable" which perhaps will be better supported than "LTS".

Read more:

Onlyjob
  • 328
  • 1
  • 7
  • I'm a bit lost with the security repository, security updates aren't included in the https://packages.debian.org/squeeze ? So only bug-fixes are included in this repository ? – Quentin Aug 26 '14 at 10:09
  • High priority security fixes (only) are shipped through "security.debian.org". Bug and security fixes are shipped through other repositories. See https://wiki.debian.org/SourcesList and check example "sources.list". – Onlyjob Aug 27 '14 at 00:22