Re: dealing with testing and security
On Fri, 19 Sep 2003, Chad M Stewart wrote:
>
> I'm tired of the stale nature of stable. Last weekend I upgraded to
> testing. I'm wondering what is the recommended method of dealing with
> security updates for testing?
>
> Should I downgrade and only upgrade the few packages that I want newer
> versions of, like mailman, spamassassin, and bind.
Like someone else already told you, you might choose to go back to woody
and use the backports a lot of people graciously make available.
Another possibility is to build them yourself. To illustrate one such
recent update I'll show you what you need to do to get the latest ssh on
your testing box.
1) Add these to your /etc/apt/sources.list:
deb-src http://http.us.debian.org/debian unstable main contrib non-free
deb-src http://non-us.debian.org/debian-non-US unstable/non-US main
contrib non-free
2) Update your current list of packages:
apt-get update
3) Get the source:
apt-get source ssh
4) Enter the directory where your new source is unpacked:
cd ./openssh-3.6.1p2
5) Review the README and changelog:
less ./debian/README.Debian
less ./debian/changelog
6) Verify all the dependencies are statisfied:
apt-get build-deb ssh
Decide if you want to continue, after reading the output [1]
7) Build a .deb file from the source:
dpkg-buildpackage -rfakeroot -uc -b [2]
8) Go up one directory to where the resulting deb is placed:
cd ..
9) Install your freshly made package:
dpkg -i ssh_3.6.1p2-9_i386.deb
10) See for yourself what dpkg has to show:
dpkg -l ssh
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii ssh 3.6.1p2-9 Secure rlogin/rsh/rcp replacement
(OpenSSH)
11) Get a beer and drink on the health of the maintainers making all
this possible in the knowledge you're safe from another bug
[1] In this case a lot of kde-packages will be listed as candidates for
removal (at least that's what happened here), you need to decide for
yourself where your priorities are.
[2] You might need to install fakeroot to make this work.
HTH
Grx HdV
Reply to: