Re: Need to upgrade to jessie need help
On Tue 25 Jul 2017 at 20:56:31 (-0700), Patrick Bartek wrote:
> On Wed, 26 Jul 2017 00:24:00 +0100 Brian <ad44@cityscape.co.uk> wrote:
>
> > On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> >
> > > On Tue, 25 Jul 2017 20:06:01 +0100 Brian <ad44@cityscape.co.uk>
> > > wrote:
> > >
> > > > On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:
> > > >
> > > > > On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
> > > > > <vigneshdhanraj.g@gmail.com> wrote:
> > > > >
> > > > > > Hi Team,
> > > > > >
> > > > > > I am using kernel 3.2.x, i know that support from wheezy will
> > > > > > be stopped soon. can i upgrade to jessie with same kernel
> > > > > > version.
> > > > > >
> > > > > > Is that correct way of handling?
> > > > >
> > > > > LTS (Long Term Support) for Wheezy ends May 2018. So, you have
> > > > > time to consider all your options.
> > > >
> > > > I have got it into my head that LTS for wheezy focuses on security
> > > > fixes and package updates are either non-existent or few and far
> > > > between. There may be reasons for staying with that distribution
> > > > but I am very unsure what "supported" for the next year means. As
> > > > far as non-security issues are concerned it appears not to have
> > > > any great significance.
> > >
> > > I get upgrades, both security and "other," several times a week
> > > most of the time. I check daily. I've never gone more than a week
> > > without something coming down the pike. In fact, just a couple
> > > days ago, I got a fairly lengthy one for multiple apps, libraries,
> > > etc. IIRC, none were security related. In other words, Wheezy is
> > > still alive support-wise.
> >
> > A mention of the names of some of these apps would be helpful. A
> > record will be in your logs.
>
> Why?
Because without evidence, it seems likely that you have confused your
wheezy server with a jessie system; there was a point release for
jessie from 8.8 to 8.9 between 23rd and 24th of this month. I've
searched in vain for an upgrade this month on wheezy which lacks a
CVE number.
> My system, a box under my desk I custom built 10.5 years ago which
> has been upgraded numerous times since, is minimal and very
> non-typical: No desktop, just a window manager and a single panel with
> menus. Even X is minimal. No games. No wifi. Apache isn't installed
> Neither is samba. No local DNS. No email server. There is no local
> network. I'm only connected to the Internet. Nothing is installed that
> isn't needed. So, what gets upgraded on my system will have little
> bearing on yours. Just take satisfaction that Wheezy is supported and
> will continue to be until May 2018.
My wheezy server is, I would hope, a fairly typical desktop for a
person using X, fvwm, LaTeX, firefox, emacs, CUPS, libreoffice, etc.
As I process my email with mutt on it, I upgrade it at least every day
if any packages arrive (it updates and downloads every three hours).
Here's the month of July, each one annotated with the corresponding CVEs.
Start-Date: 2017-07-02 23:13:25
Commandline: apt-get upgrade
Upgrade: vorbis-tools:i386 (1.4.0-1, 1.4.0-1+deb7u1)
End-Date: 2017-07-02 23:13:40
CVE-2015-6749 CVE-2014-9638 CVE-2014-9639 CVE-2014-9640
Start-Date: 2017-07-03 15:18:11
Commandline: apt-get upgrade
Upgrade: sudo:i386 (1.8.5p2-1+nmu3+deb7u3, 1.8.5p2-1+nmu3+deb7u4)
End-Date: 2017-07-03 15:18:25
CVE-2017-1000368
Start-Date: 2017-07-06 07:36:43
Commandline: apt-get upgrade
Upgrade: libgcrypt11:i386 (1.5.0-5+deb7u5, 1.5.0-5+deb7u6), libgraphite2-2.0.0:i386 (1.3.6-1~deb7u2, 1.3.10-1~deb7u1)
End-Date: 2017-07-06 07:36:57
CVE-2017-7771 CVE-2017-7772 CVE-2017-7773 CVE-2017-7774 CVE-2017-7775 CVE-2017-7776 CVE-2017-7777 CVE-2017-7778
Start-Date: 2017-07-08 08:41:41
Commandline: apt-get upgrade
Upgrade: libmpg123-0:i386 (1.14.4-1+deb7u1, 1.14.4-1+deb7u2)
End-Date: 2017-07-08 08:41:46
CVE-2017-10683
Start-Date: 2017-07-09 08:01:44
Commandline: apt-get upgrade
Upgrade: libsqlite3-0:i386 (3.7.13-1+deb7u3, 3.7.13-1+deb7u4)
End-Date: 2017-07-09 08:01:56
CVE-2017-10989
Start-Date: 2017-07-11 23:32:46
Commandline: apt-get upgrade
Upgrade: libtiff4:i386 (3.9.6-11+deb7u6, 3.9.6-11+deb7u7)
End-Date: 2017-07-11 23:32:58
CVE-2017-9936
Start-Date: 2017-07-14 07:53:48
Commandline: apt-get upgrade
Upgrade: bind9-host:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), dnsutils:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), libdns88:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), libisccc80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), liblwres80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), libbind9-80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), libisccfg82:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17), libisc84:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 9.8.4.dfsg.P1-6+nmu2+deb7u17)
End-Date: 2017-07-14 07:54:07
CVE-2017-3142 CVE-2017-3143
Start-Date: 2017-07-14 12:58:26
Commandline: apt-get upgrade
Upgrade: xserver-common:i386 (1.12.4-6+deb7u6, 1.12.4-6+deb7u7), xserver-xorg-core:i386 (1.12.4-6+deb7u6, 1.12.4-6+deb7u7)
End-Date: 2017-07-14 12:58:35
CVE-2017-10971 CVE-2017-10972
Start-Date: 2017-07-18 07:32:20
Commandline: apt-get upgrade
Upgrade: vim-common:i386 (7.3.547-7+deb7u3, 7.3.547-7+deb7u4), vim-tiny:i386 (7.3.547-7+deb7u3, 7.3.547-7+deb7u4)
End-Date: 2017-07-18 07:32:37
CVE-2017-11109
Start-Date: 2017-07-19 07:37:39
Commandline: apt-get upgrade
Upgrade: evince-common:i386 (3.4.0-3.1, 3.4.0-3.1+deb7u1), libevdocument3-4:i386 (3.4.0-3.1, 3.4.0-3.1+deb7u1), gir1.2-evince-3.0:i386 (3.4.0-3.1, 3.4.0-3.1+deb7u1), evince:i386 (3.4.0-3.1, 3.4.0-3.1+deb7u1), libevview3-3:i386 (3.4.0-3.1, 3.4.0-3.1+deb7u1)
End-Date: 2017-07-19 07:38:04
CVE-2017-1000083
Start-Date: 2017-07-25 08:13:01
Commandline: apt-get upgrade
Upgrade: libtasn1-3:i386 (2.13-2+deb7u4, 2.13-2+deb7u5), catdoc:i386 (0.94.4-1.1, 0.94.4-1.1+deb7u1)
End-Date: 2017-07-25 08:13:19
CVE-2017-10790
CVE-2017-11110
Start-Date: 2017-07-25 14:34:24
Commandline: apt-get upgrade
Upgrade: bind9-host:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), dnsutils:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), libdns88:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), libisccc80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), liblwres80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), libbind9-80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), libisccfg82:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18), libisc84:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u17, 9.8.4.dfsg.P1-6+nmu2+deb7u18)
End-Date: 2017-07-25 14:34:44
regression introduced in previous upload
Perhaps you were fooled by the number of packages that make up bind.
Cheers,
David.
Reply to: