Adding Debian security repos to LMDE sources
Posted: Thu Jan 10, 2013 2:38 pm
Hi All,
I have recently converted to LMDE from Ubuntu 12.10 and 12.04 before that, and must say I'm enjoying the LMDE experience so far. I do have one query regarding how LMDE/ Debian in general handles security updates. Apologies if this is a noob question, I have read around the forums a bit and can't quite find the answer to my query.
I understand that LMDE organises the rolling release Debian testing branch into Update Packs which are then periodically released. The main benefit of this being, as I understand, that any potential bugs/ breakages from the Debian testing branch can be ironed out before being pushed out to unsuspecting people like myself. Conversely, I understand that a downside to this approach is that security updates can be slower reaching LMDE than they are reaching the pure Squeeze/ Wheezy branches.
My question, or rather questions, are as follows.
1) Can we get around the delay in LMDE security updates by adding the standard Debian security repo to the sources list, or is this a recipe for conflicts?
2) If we can, is it best to add the squeeze security repo "deb http://security.debian.org/ squeeze/updates main contrib non-free", or the wheezy security repo "deb http://security.debian.org/ wheezy/updates main contrib non-free"
3) Is there any merit in adding both repos? As I understand it the Debian Security team primarily provides support for Debian Stable, and then for Debian testing (http://www.debian.org/security/faq#testing). Are there therefore likely to be security patches in stable that have not been added in testing, or have a read this all wrong?
4) Taking answers to the above into account (sorry, I'm getting there, I promise) am I likely to encounter issues with a sources list that currently looks like this:
deb http://mirror.tuxis.nl/packages/ debian main upstream import
deb http://www.mirrorservice.org/sites/debi ... ian/latest testing main contrib non-free
deb http://www.mirrorservice.org/sites/debi ... t/security testing/updates main contrib non-free
deb http://www.mirrorservice.org/sites/debi ... multimedia testing main non-free
deb http://ftp.us.debian.org/debian testing main contrib non-free
deb-src http://ftp.us.debian.org/debian testing main contrib non-free
deb http://repository.spotify.com stable non-free
deb-src http://repository.spotify.com stable non-free
deb http://security.debian.org squeeze/updates main contrib non-free
deb-src http://security.debian.org squeeze/updates main contrib non-free
deb http://security.debian.org wheezy/updates main contrib non-free
deb-src http://security.debian.org wheezy/updates main contrib non-free
Apologies for the long-winded first post, any guidance would be appreciated.
Many thanks,
Jim
I have recently converted to LMDE from Ubuntu 12.10 and 12.04 before that, and must say I'm enjoying the LMDE experience so far. I do have one query regarding how LMDE/ Debian in general handles security updates. Apologies if this is a noob question, I have read around the forums a bit and can't quite find the answer to my query.
I understand that LMDE organises the rolling release Debian testing branch into Update Packs which are then periodically released. The main benefit of this being, as I understand, that any potential bugs/ breakages from the Debian testing branch can be ironed out before being pushed out to unsuspecting people like myself. Conversely, I understand that a downside to this approach is that security updates can be slower reaching LMDE than they are reaching the pure Squeeze/ Wheezy branches.
My question, or rather questions, are as follows.
1) Can we get around the delay in LMDE security updates by adding the standard Debian security repo to the sources list, or is this a recipe for conflicts?
2) If we can, is it best to add the squeeze security repo "deb http://security.debian.org/ squeeze/updates main contrib non-free", or the wheezy security repo "deb http://security.debian.org/ wheezy/updates main contrib non-free"
3) Is there any merit in adding both repos? As I understand it the Debian Security team primarily provides support for Debian Stable, and then for Debian testing (http://www.debian.org/security/faq#testing). Are there therefore likely to be security patches in stable that have not been added in testing, or have a read this all wrong?
4) Taking answers to the above into account (sorry, I'm getting there, I promise) am I likely to encounter issues with a sources list that currently looks like this:
deb http://mirror.tuxis.nl/packages/ debian main upstream import
deb http://www.mirrorservice.org/sites/debi ... ian/latest testing main contrib non-free
deb http://www.mirrorservice.org/sites/debi ... t/security testing/updates main contrib non-free
deb http://www.mirrorservice.org/sites/debi ... multimedia testing main non-free
deb http://ftp.us.debian.org/debian testing main contrib non-free
deb-src http://ftp.us.debian.org/debian testing main contrib non-free
deb http://repository.spotify.com stable non-free
deb-src http://repository.spotify.com stable non-free
deb http://security.debian.org squeeze/updates main contrib non-free
deb-src http://security.debian.org squeeze/updates main contrib non-free
deb http://security.debian.org wheezy/updates main contrib non-free
deb-src http://security.debian.org wheezy/updates main contrib non-free
Apologies for the long-winded first post, any guidance would be appreciated.
Many thanks,
Jim