sources.list entry for mod_security testing release?

Question

I have a debian "squeeze" installation, but the mod_security delivered with this release is quite old. So I'm thinking of adding an additional line to my sources.list to get the "wheezy" version (wheezy = the version after the current version "squeeze") of mod_security.

What should I add to sources.list to receive only the next available version of mod_security?

This is one of my entires in sources.list:

deb http://ftp.de.debian.org/debian/ squeeze main contrib non-free

The current name of mod_sec is libapache-mod-security

score 1 · Accepted Answer · edited Apr 13 '17 at 12:14

1

Careful - adding a full new repository can light up new versions for more than just that one individual package, putting you in this situation.

Feel free to add the repo:

deb http://ftp.de.debian.org/debian/ wheezy main contrib non-free

BUT, don't let it get used for more than just the package you need from it, unless you want to update the whole system.

Modify your /etc/apt/preferences file, adding configuration to lower the priority of the testing release:

Package: *
Pin: release a=testing
Pin-Priority: 450

And up the priority for the package that you're interested in (by the way, the package name changed):

Package: libapache2-modsecurity
Pin: release a=testing
Pin-Priority: 550

Verify with apt-cache policy that the testing repo is lower than the stable repos, and verify with apt-cache policy libapache2-modsecurity that the individual package prefers testing.

edited Apr 13 '17 at 12:14

Community

1

answered Aug 19 '11 at 16:13

Shane Madden

114,520
13
181
251

Cool, thanks for the explanation! When I run `apt-cache policy` the wheezy branch does not show up. Do I have to refresh apt-get, or something else? – powtac Aug 19 '11 at 16:41
@powtac Yeah - `apt-get update` – Shane Madden Aug 19 '11 at 16:43
found it already. Now wheezy shows up with 450 when running `apt-cache policy` and libapache2-modsecurity not. I think this is ok? – powtac Aug 19 '11 at 16:47
And I can now run apt-get upgrade without problems? – powtac Aug 19 '11 at 16:48
When I start apt-get, bastille shows up without updated, when I revert all changes from above back, bastille does not show up?! – powtac Aug 19 '11 at 16:53
Check where it's trying to come from - `apt-cache policy bastille`? – Shane Madden Aug 19 '11 at 17:30
`apt-cache policy bastille` outputs: `450 http://ftp.de.debian.org/debian/ wheezy/main i386 Packages` and `100 /var/lib/dpkg/status` – powtac Aug 22 '11 at 13:55

sources.list entry for mod_security testing release?

1 Answers1