On Wed, May 14, 2008 at 10:57 AM, Steve Holdoway <[EMAIL PROTECTED]> wrote: > On Wed, 14 May 2008 10:12:19 +1200 > Roy Britten <[EMAIL PROTECTED]> wrote: > >> 2008/5/14 Nick Rout <[EMAIL PROTECTED]>: >> > Anyway I am trying to update a system remotely (over ssh of course, how >> > ironic). >> > >> > The openssh-client and -server updates don't seem to get applied: >> > >> > [EMAIL PROTECTED]:~$ sudo apt-get upgrade >> > Reading package lists... Done >> > Building dependency tree >> > Reading state information... Done >> > The following packages have been kept back: >> > openssh-client openssh-server >> > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. >> > >> > >> > Any idea why not? aptitude does much the same. This is on hardy, with >> > no changes to the default sources.list. >> >> do you need >> sudo apt-get dist-upgrade > No, that is intended upgrade to a new distro - gutsy to hardy for example. > > Steve > -- > Steve Holdoway <[EMAIL PROTECTED]> >
No its also useful where a new dependency is introduced (as in here where there is a new dependency on openssh-blacklist). see also here http://www.debian-administration.org/articles/69 And indeed I have lost connectivity and will fix it tonight. Never mind if I cannot log in I suppose no-one else can either :-) so in short the way to update openssh-* is to use dist-upgrade which will install the new dependency. This fubar seems to have rocked confidence in debian, but perhaps thats another discussion.
