Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #184197 > unrolled thread

Need to upgrade to jessie need help

Started byVigneshDhanraj G <vigneshdhanraj.g@gmail.com>
First post2017-07-25 08:40 +0200
Last post2017-07-26 02:30 +0200
Articles 9 on this page of 29 — 11 participants

Back to article view | Back to linux.debian.user

Contents

  Need to upgrade to jessie need help VigneshDhanraj G <vigneshdhanraj.g@gmail.com> - 2017-07-25 08:40 +0200
    Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-25 09:50 +0200
      Re: Need to upgrade to jessie need help VigneshDhanraj G <vigneshdhanraj.g@gmail.com> - 2017-07-25 09:50 +0200
      Re: Need to upgrade to jessie need help Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-25 14:00 +0200
        Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-25 15:00 +0200
          Re: Need to upgrade to jessie need help Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-07-25 15:30 +0200
            Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-25 15:40 +0200
              Re: Need to upgrade to jessie need help Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-07-25 16:00 +0200
                Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-25 16:10 +0200
                Re: Need to upgrade to jessie need help Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-25 16:10 +0200
                  Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-25 16:20 +0200
                    Re: Need to upgrade to jessie need help David Wright <deblis@lionunicorn.co.uk> - 2017-07-27 17:50 +0200
                      Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-28 17:50 +0200
                        Re: Need to upgrade to jessie need help Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-28 18:10 +0200
                          Re: Need to upgrade to jessie need help Dejan Jocic <jodejka@gmail.com> - 2017-07-28 18:20 +0200
                          Re: Need to upgrade to jessie need help Mark Fletcher <mark27q1@gmail.com> - 2017-07-29 17:30 +0200
                  Re: Need to upgrade to jessie need help Brian <ad44@cityscape.co.uk> - 2017-07-25 20:50 +0200
                    Re: Need to upgrade to jessie need help Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-25 21:00 +0200
                  Re: Need to upgrade to jessie need help Gene Heskett <gheskett@shentel.net> - 2017-07-26 02:40 +0200
    Re: Need to upgrade to jessie need help Georgi Naplatanov <gosho@oles.biz> - 2017-07-25 10:30 +0200
    Re: Need to upgrade to jessie need help Patrick Bartek <nemommxiv@gmail.com> - 2017-07-25 16:10 +0200
      Re: Need to upgrade to jessie need help Brian <ad44@cityscape.co.uk> - 2017-07-25 21:10 +0200
        Re: Need to upgrade to jessie need help Patrick Bartek <nemommxiv@gmail.com> - 2017-07-26 01:20 +0200
          Re: Need to upgrade to jessie need help Brian <ad44@cityscape.co.uk> - 2017-07-26 01:30 +0200
            Re: Need to upgrade to jessie need help Patrick Bartek <nemommxiv@gmail.com> - 2017-07-26 06:00 +0200
              Re: Need to upgrade to jessie need help David Wright <deblis@lionunicorn.co.uk> - 2017-07-27 18:50 +0200
            Re: Need to upgrade to jessie need help Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-26 14:30 +0200
              Re: Need to upgrade to jessie need help Brian <ad44@cityscape.co.uk> - 2017-07-26 15:10 +0200
    Re: Need to upgrade to jessie need help David Christensen <dpchrist@holgerdanske.com> - 2017-07-26 02:30 +0200

Page 2 of 2 — ← Prev page 1 [2]

#184219

FromPatrick Bartek <nemommxiv@gmail.com>
Date2017-07-25 16:10 +0200
Message-ID<u78H7-3MX-11@gated-at.bofh.it>
In reply to#184197
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.

B

[toc] | [prev] | [next] | [standalone]

#184235

FromBrian <ad44@cityscape.co.uk>
Date2017-07-25 21:10 +0200
Message-ID<u7dns-6Lb-13@gated-at.bofh.it>
In reply to#184219
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.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184246

FromPatrick Bartek <nemommxiv@gmail.com>
Date2017-07-26 01:20 +0200
Message-ID<u7hhn-SP-3@gated-at.bofh.it>
In reply to#184235
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.

B

[toc] | [prev] | [next] | [standalone]

#184249

FromBrian <ad44@cityscape.co.uk>
Date2017-07-26 01:30 +0200
Message-ID<u7hr3-W4-11@gated-at.bofh.it>
In reply to#184246
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.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184259

FromPatrick Bartek <nemommxiv@gmail.com>
Date2017-07-26 06:00 +0200
Message-ID<u7lEm-3wP-1@gated-at.bofh.it>
In reply to#184249
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?

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.

But, FYI: VirtualBox 5.1 got upgraded from Oracle's repo few days ago
It wasn't installed from the Debian repo to begin with.  And
Firefox-esr a few days before which came from Debian's Security repo.

B

[toc] | [prev] | [next] | [standalone]

#184317

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2017-07-27 18:50 +0200
Message-ID<u7U94-8vc-7@gated-at.bofh.it>
In reply to#184259
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.

[toc] | [prev] | [next] | [standalone]

#184265

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2017-07-26 14:30 +0200
Message-ID<u7tBV-e9-33@gated-at.bofh.it>
In reply to#184249
On Wed, Jul 26, 2017 at 12:24:00AM +0100, Brian wrote:
> On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> > 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.

Here's a result from one wheezy server, if that helps any:

# grep upgrade /var/log/dpkg.log
2017-07-03 12:48:42 upgrade libxml2-dev:amd64 2.8.0+dfsg1-7+wheezy7 2.8.0+dfsg1-7+wheezy8
2017-07-03 12:48:42 upgrade libxml2:amd64 2.8.0+dfsg1-7+wheezy7 2.8.0+dfsg1-7+wheezy8
2017-07-03 12:48:42 upgrade libarchive12:amd64 3.0.4-3+wheezy5+deb7u1 3.0.4-3+wheezy6
2017-07-03 12:48:42 upgrade libxml2-utils:amd64 2.8.0+dfsg1-7+wheezy7 2.8.0+dfsg1-7+wheezy8
2017-07-03 12:48:42 upgrade sudo:amd64 1.8.5p2-1+nmu3+deb7u3 1.8.5p2-1+nmu3+deb7u4
2017-07-11 10:37:15 upgrade libgcrypt11:amd64 1.5.0-5+deb7u5 1.5.0-5+deb7u6
2017-07-11 10:37:16 upgrade libsqlite3-0:amd64 3.7.13-1+deb7u3 3.7.13-1+deb7u4
2017-07-11 10:37:16 upgrade libtiff4:amd64 3.9.6-11+deb7u6 3.9.6-11+deb7u7
2017-07-13 13:36:33 upgrade nginx-common:all 1.2.1-2.2+wheezy4 1.2.1-2.2+wheezy4+deb7u1
2017-07-13 13:36:33 upgrade nginx-full:amd64 1.2.1-2.2+wheezy4 1.2.1-2.2+wheezy4+deb7u1
2017-07-13 13:36:33 upgrade nginx:all 1.2.1-2.2+wheezy4 1.2.1-2.2+wheezy4+deb7u1
2017-07-17 11:20:51 upgrade bind9-host:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade dnsutils:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade libisc84:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade libdns88:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade libisccc80:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade libisccfg82:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade liblwres80:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade libbind9-80:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u16 1:9.8.4.dfsg.P1-6+nmu2+deb7u17
2017-07-17 11:20:51 upgrade xserver-xorg-dev:amd64 2:1.12.4-6+deb7u6 2:1.12.4-6+deb7u7
2017-07-21 09:54:15 upgrade vim:amd64 2:7.3.547-7+deb7u3 2:7.3.547-7+deb7u4
2017-07-21 09:54:15 upgrade vim-tiny:amd64 2:7.3.547-7+deb7u3 2:7.3.547-7+deb7u4
2017-07-21 09:54:15 upgrade vim-runtime:all 2:7.3.547-7+deb7u3 2:7.3.547-7+deb7u4
2017-07-21 09:54:16 upgrade vim-common:amd64 2:7.3.547-7+deb7u3 2:7.3.547-7+deb7u4
2017-07-24 08:21:39 upgrade qemu-keymaps:all 1.1.2+dfsg-6+deb7u20 1.1.2+dfsg-6+deb7u22
2017-07-24 08:21:39 upgrade qemu-utils:amd64 1.1.2+dfsg-6+deb7u20 1.1.2+dfsg-6+deb7u22
2017-07-25 14:56:22 upgrade libtasn1-3:amd64 2.13-2+deb7u4 2.13-2+deb7u5
2017-07-25 14:56:22 upgrade bind9-host:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade dnsutils:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade libisc84:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade libdns88:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade libisccc80:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade libisccfg82:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade liblwres80:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18
2017-07-25 14:56:22 upgrade libbind9-80:amd64 1:9.8.4.dfsg.P1-6+nmu2+deb7u17 1:9.8.4.dfsg.P1-6+nmu2+deb7u18

[toc] | [prev] | [next] | [standalone]

#184268

FromBrian <ad44@cityscape.co.uk>
Date2017-07-26 15:10 +0200
Message-ID<u7ueC-Iw-1@gated-at.bofh.it>
In reply to#184265
On Wed 26 Jul 2017 at 08:22:19 -0400, Greg Wooledge wrote:

> On Wed, Jul 26, 2017 at 12:24:00AM +0100, Brian wrote:
> > On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> > > 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.
> 
> Here's a result from one wheezy server, if that helps any:

Both you and Patrick Bartek have helped.

> # grep upgrade /var/log/dpkg.log
> 2017-07-03 12:48:42 upgrade libxml2-dev:amd64 2.8.0+dfsg1-7+wheezy7 2.8.0+dfsg1-7+wheezy8
> 2017-07-03 12:48:42 upgrade libxml2:amd64 2.8.0+dfsg1-7+wheezy7 2.8.0+dfsg1-7+wheezy8

[...]

I was trying to sort out to my satisfaction what "supported" is in
practice regarding wheezy. It seems to have a different meaning from
"supported" in jessie, where point releases can bring in minor
enhancements as well as security updates and backports can give some
assurance of keeping up-to-date with some packages.

Nevertheless, no matter what is on the system, there must be some agreed
expectation of what Debian will provide. It appears to me that the most
which can be expected is support from the LTS team. Anything through
wheezy-backports is at the discretion of a maintainer. An interesting
thread begins at

  https://lists.debian.org/debian-backports/2016/05/msg00067.html

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184253

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2017-07-26 02:30 +0200
Message-ID<u7in8-1wt-21@gated-at.bofh.it>
In reply to#184197
On 07/24/17 23:12, VigneshDhanraj G wrote:
> 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?

I prefer and recommend backing up, removing the system drive, installing 
a fresh system drive, doing a fresh install of the new operating system, 
and restoring.  If the process fails, it is easy to start over and/or 
revert to the old system drive.  Mobile docks facilitate the process.


David

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web