Re: Need to upgrade to jessie need help

[Mark Fletcher]

On Fri, Jul 28, 2017 at 12:04:54PM -0400, Greg Wooledge wrote:
> 
> The concern is that you may have used some shared library to compile a
> third-party program which is installed in /usr/local or /opt, or anywhere
> else that's outside of Debian's knowledge.  Debian would not know that
> the library is still being used, and therefore might autoremove it.
> 
> The impact of this is directly proportional to how many things you
> compile yourself, and how important those things are to you.
> 
If you compiled a program yourself, you probably know what its runtime 
dependencies are. Just create a dummy debian package with the right 
dependencies (this is a simple two-step task with the "equivs" package 
installed). Install that package using dpkg -i  and 
now Debian knows you don't want those libraries removed. And then you 
can safely use apt autoremove to keep your system clean.

I'd emphasise that using equivs is *NOT* a big ton of work -- you can 
very quickly throw together a dummy package even with a decent sized 
list of dependencies, and decent instructions are only a google away...

One thing you might trip over -- when you come to install the dummy 
package representing your self-built software, if any of the 
dependencies are not already installed, dpkg -i will fail. Use the -f 
option to force it to install anyway, then follow up with apt install 
--fix-broken or aptitude install or whatever to get it to fix the broken 
dependencies (by installing the missing dependencies, and recognising 
they are required for the dummy package you installed representing your 
self-built software).

Later, probably *much* later, you might get upgrade problems where the 
system wants to upgrade those libraries but can't because of the 
dependcies from your dummy package. The response to that should probably 
be to recognise that the self-built software may need re-building 
against the upgraded libraries, to do which you would remove the dummy 
package, let the upgrade happen, rebuild the self-built package, and 
then use equivs again to make a new dummy package. The kind of scenario 
I have in mind here is one where library upgrades change library package 
names -- I seem to recall fun a while back with with gnome libraries 
around the time of the upgrade from Gnome 2 to Gnome 3 (Wheezy to 
Jessie? Or was it earlier?) that had to do with this. The symptom was an 
attempt to upgrade wanting to remove half the system... At the time I 
wasn't much of a ninja with apt dependencies, but once I figured out the 
cause, the solution in that case was just marking libraries as 
auto-installed that were marked as non-auto and which nothing depended 
on. That is a different problem but produces a very similar effect to a 
dummy package depending on libraries whose package names change with an 
upgrade.

I suspect you, Greg, already know a lot of this, but nonetheless 
hopefully this will be useful for the archives.

Mark

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 28-07-17, Greg Wooledge wrote:
> On Fri, Jul 28, 2017 at 05:39:39PM +0200, Dejan Jocic wrote:
> > So, same question as above, did and of those they messed up? Are there
> > opened bugs that autoremove from any of used tools in debian removes
> > packages it should not? And qualifications for that statement are years
> > of use of both apt-get and aptitude with autoremove following
> > update/upgrade. Never had any trouble with it.
> 
> The concern is that you may have used some shared library to compile a
> third-party program which is installed in /usr/local or /opt, or anywhere
> else that's outside of Debian's knowledge.  Debian would not know that
> the library is still being used, and therefore might autoremove it.
> 
> The impact of this is directly proportional to how many things you
> compile yourself, and how important those things are to you.
> 

If you manually installed shared library, did autoremove removed
it/proposed to removed it? Or, it was installed as dependency of some
other package that you removed? If former, it is bug. If later, you
should have mark it as manually installed, if your compiled software
depends on it.

Also, if you compile third party programs, there are ways to make debian
packages out of them and keep yourself and your preferred debian package
tool happy. Just saying.

Re: Need to upgrade to jessie need help

[Greg Wooledge]

On Fri, Jul 28, 2017 at 05:39:39PM +0200, Dejan Jocic wrote:
> So, same question as above, did and of those they messed up? Are there
> opened bugs that autoremove from any of used tools in debian removes
> packages it should not? And qualifications for that statement are years
> of use of both apt-get and aptitude with autoremove following
> update/upgrade. Never had any trouble with it.

The concern is that you may have used some shared library to compile a
third-party program which is installed in /usr/local or /opt, or anywhere
else that's outside of Debian's knowledge.  Debian would not know that
the library is still being used, and therefore might autoremove it.

The impact of this is directly proportional to how many things you
compile yourself, and how important those things are to you.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 27-07-17, David Wright wrote:
> On Tue 25 Jul 2017 at 16:16:44 (+0200), Dejan Jocic wrote:
> > On 25-07-17, Greg Wooledge wrote:
> > > Is there any way to permanently neuter apt-get autoremove, so that even
> > > if something invokes it against my will, it will *never* remove anything?
> > > 
> > > And more, is there a way to get apt and apt-get to *stop* prompting me
> > > to run it, and *stop* spamming me with a list of packages that it would
> > > like me to remove?  (Maybe that's the same as the first question, maybe
> > > not.)
> > > 
> > > My strategy so far has been "ignore the spam, and never willingly run
> > > autoremove".  This mostly works, but I recently learned that tasksel
> > > will apparently run an autoremove, without warning, whether I want it
> > > to or not ().
> > > 
> > > If autoremove will also remove *kernels*, which this thread seems to
> > > indicate is the case, then my concerns just went up another notch.
> > > 
> > > I suppose one could manually mark each and every single installed
> > > package as "manually installed", but you'd have to remember to repeat
> > > this periodically, and it seems clumsy and inelegant compared to some
> > > sort of master switch that can just tell autoremove to go die in a fire.
> > > 
> > 
> > Your fear from autoremove is silly. It
> 
> Please note that "it" is "they", viz: apt and apt-get, …
> 

Sure it is they. Did any of those they ever removed something that you
needed with autoremove? Or they always remove just things that you do not
need any more, packages that are just sitting there doing nothing,
former dependencies that are not needed for anything?

> > will not remove anything you
> > really need and, if you stick to default settings, 
> 
> … and that they have different defaults. What's more, apt's behaviour
> may change between versions, so unqualified statements like this
> should really be confirmed before being relied on.
> 

So, same question as above, did and of those they messed up? Are there
opened bugs that autoremove from any of used tools in debian removes
packages it should not? And qualifications for that statement are years
of use of both apt-get and aptitude with autoremove following
update/upgrade. Never had any trouble with it.

> > will keep all
> > packages it replaced in /var/cache/apt/archives, as far as I know. And
> > if you have some package that you really, really want to keep, you can
> > always pin it, or put it on hold with apt-mark. It is not spam, it is
> > keeping your system clean.
> 
> Cheers,
> David.
> 

All best,
Dejan

Re: Need to upgrade to jessie need help

[David Wright]

On Tue 25 Jul 2017 at 20:56:31 (-0700), Patrick Bartek wrote:
> On Wed, 26 Jul 2017 00:24:00 +0100 Brian  wrote:
> 
> > On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> > 
> > > On Tue, 25 Jul 2017 20:06:01 +0100 Brian 
> > > 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
> > > > >  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- 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

 

Re: Need to upgrade to jessie need help

[David Wright]

On Tue 25 Jul 2017 at 16:16:44 (+0200), Dejan Jocic wrote:
> On 25-07-17, Greg Wooledge wrote:
> > Is there any way to permanently neuter apt-get autoremove, so that even
> > if something invokes it against my will, it will *never* remove anything?
> > 
> > And more, is there a way to get apt and apt-get to *stop* prompting me
> > to run it, and *stop* spamming me with a list of packages that it would
> > like me to remove?  (Maybe that's the same as the first question, maybe
> > not.)
> > 
> > My strategy so far has been "ignore the spam, and never willingly run
> > autoremove".  This mostly works, but I recently learned that tasksel
> > will apparently run an autoremove, without warning, whether I want it
> > to or not ().
> > 
> > If autoremove will also remove *kernels*, which this thread seems to
> > indicate is the case, then my concerns just went up another notch.
> > 
> > I suppose one could manually mark each and every single installed
> > package as "manually installed", but you'd have to remember to repeat
> > this periodically, and it seems clumsy and inelegant compared to some
> > sort of master switch that can just tell autoremove to go die in a fire.
> > 
> 
> Your fear from autoremove is silly. It

Please note that "it" is "they", viz: apt and apt-get, …

> will not remove anything you
> really need and, if you stick to default settings, 

… and that they have different defaults. What's more, apt's behaviour
may change between versions, so unqualified statements like this
should really be confirmed before being relied on.

> will keep all
> packages it replaced in /var/cache/apt/archives, as far as I know. And
> if you have some package that you really, really want to keep, you can
> always pin it, or put it on hold with apt-mark. It is not spam, it is
> keeping your system clean.

Cheers,
David.

Re: Need to upgrade to jessie need help

[Brian]

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.

Re: Need to upgrade to jessie need help

[Greg Wooledge]

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

Re: Need to upgrade to jessie need help

[Patrick Bartek]

On Wed, 26 Jul 2017 00:24:00 +0100 Brian  wrote:

> On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> 
> > On Tue, 25 Jul 2017 20:06:01 +0100 Brian 
> > 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
> > > >  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

Re: Need to upgrade to jessie need help

[Gene Heskett]

On Tuesday 25 July 2017 10:02:50 Greg Wooledge wrote:

> Is there any way to permanently neuter apt-get autoremove, so that
> even if something invokes it against my will, it will *never* remove
> anything?
>
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it, and *stop* spamming me with a list of packages that it
> would like me to remove?  (Maybe that's the same as the first
> question, maybe not.)
>
> My strategy so far has been "ignore the spam, and never willingly run
> autoremove".  This mostly works, but I recently learned that tasksel
> will apparently run an autoremove, without warning, whether I want it
> to or not ().
>
> If autoremove will also remove *kernels*, which this thread seems to
> indicate is the case, then my concerns just went up another notch.
>
In that event, see man apt and find the "pin" instructions.

I recently had a rt kernel wiped on a raspi, which kills linuxcnc.

I pulled the sd card in here, and replaced the missing kernel, then 
following the pin instructions, and then watching the --upgradable 
listings, added 2 more stanza's to a file in /etc/apt/preferences.d, 
named kernel.pref, so it looks like this:
  
pi@picncsheldon:~/linuxcnc/configs/sheldon-lathe $ 
cat /etc/apt/preferences.d/kernel.pref 

Package:linux-kernel
pin: version 4.4.4-rt9-v7+
Pin-Priority: 1001

Package: linux-headers
Pin: version 4.4.4-rt9-v7+
Pin-Priority: 1001

Package: raspberrypi-bootloader
Pin: version 1.20170427-1
Pin-Priority: 1001

Package: raspberrypi-kernel
Pin: version 1.20170427-1
Pin-Priority: 1001

pi@picncsheldon:~/linuxcnc/configs/sheldon-lathe $ 

I know, that is an older rt kernel, but the performance of the newer ones 
is horrifying, missing keyboard events to the point of completely 
unusable.

> I suppose one could manually mark each and every single installed
> package as "manually installed", but you'd have to remember to repeat
> this periodically, and it seems clumsy and inelegant compared to some
> sort of master switch that can just tell autoremove to go die in a
> fire.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Need to upgrade to jessie need help

[David Christensen]

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

Re: Need to upgrade to jessie need help

[Brian]

On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:

> On Tue, 25 Jul 2017 20:06:01 +0100 Brian  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
> > >  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.

Re: Need to upgrade to jessie need help

[Patrick Bartek]

On Tue, 25 Jul 2017 20:06:01 +0100 Brian  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
> >  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

Re: Need to upgrade to jessie need help

[Brian]

On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:

> On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
>  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.

Re: Need to upgrade to jessie need help

[Greg Wooledge]

On Tue, Jul 25, 2017 at 07:40:17PM +0100, Brian wrote:
> /usr/share/doc/apt/examples/configure-index.gz has
> 
>  AutomaticRemove "false";   
>  HideAutoRemove "false";
> 
> as configuration directives. I've never tried them but wouldn't mind
> "true" being tested by someone and learning what happens.

Oh, that looks promising.

titan:~$ cat /etc/apt/apt.conf.d/99local
// APT::NeverAutoRemove ".";
titan:~$ sudo apt-get -u upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  docutils-common docutils-doc firebird2.5-common firebird2.5-common-doc
  firebird2.5-server-common firebird3.0-common firebird3.0-common-doc
  fvwm-icons imagemagick-common liba52-0.7.4 libalgorithm-c3-perl
  libarchive-extract-perl libasn1-8-heimdal libavcodec56 libavdevice55
  libavformat56 libavresample2 libavutil54 libb-hooks-endofscope-perl
  libbind9-90 libbluetooth3 libboost-system1.55.0 libc6-i686:i386
  libclamav-client-perl libclass-c3-perl libclass-c3-xs-perl
  libclass-method-modifiers-perl libclass-xsaccessor-perl libcolamd2.8.0
  libcpan-changes-perl libcpan-meta-perl libdata-perl-perl
  libdata-section-perl libdca0 libdevel-caller-perl
  libdevel-globaldestruction-perl libdevel-lexalias-perl libdirectfb-1.2-9


titan:~$ sudo vi /etc/apt/apt.conf.d/99local
titan:~$ cat /etc/apt/apt.conf.d/99local
APT::NeverAutoRemove ".";
titan:~$ sudo apt-get -u upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

That'll work!  Thanks.

Re: Need to upgrade to jessie need help

[Brian]

On Tue 25 Jul 2017 at 10:02:50 -0400, Greg Wooledge wrote:

> Is there any way to permanently neuter apt-get autoremove, so that even
> if something invokes it against my will, it will *never* remove anything?
> 
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it, and *stop* spamming me with a list of packages that it would
> like me to remove?  (Maybe that's the same as the first question, maybe
> not.)
> 
> My strategy so far has been "ignore the spam, and never willingly run
> autoremove".  This mostly works, but I recently learned that tasksel
> will apparently run an autoremove, without warning, whether I want it
> to or not ().
> 
> If autoremove will also remove *kernels*, which this thread seems to
> indicate is the case, then my concerns just went up another notch.
> 
> I suppose one could manually mark each and every single installed
> package as "manually installed", but you'd have to remember to repeat
> this periodically, and it seems clumsy and inelegant compared to some
> sort of master switch that can just tell autoremove to go die in a fire.

/usr/share/doc/apt/examples/configure-index.gz has

 AutomaticRemove "false";   
 HideAutoRemove "false";

as configuration directives. I've never tried them but wouldn't mind
"true" being tested by someone and learning what happens.

-- 
Brian.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Greg Wooledge wrote:
> Is there any way to permanently neuter apt-get autoremove, so that even
> if something invokes it against my will, it will *never* remove anything?
> 
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it, and *stop* spamming me with a list of packages that it would
> like me to remove?  (Maybe that's the same as the first question, maybe
> not.)
> 
> My strategy so far has been "ignore the spam, and never willingly run
> autoremove".  This mostly works, but I recently learned that tasksel
> will apparently run an autoremove, without warning, whether I want it
> to or not ().
> 
> If autoremove will also remove *kernels*, which this thread seems to
> indicate is the case, then my concerns just went up another notch.
> 
> I suppose one could manually mark each and every single installed
> package as "manually installed", but you'd have to remember to repeat
> this periodically, and it seems clumsy and inelegant compared to some
> sort of master switch that can just tell autoremove to go die in a fire.
> 

Your fear from autoremove is silly. It will not remove anything you
really need and, if you stick to default settings, will keep all
packages it replaced in /var/cache/apt/archives, as far as I know. And
if you have some package that you really, really want to keep, you can
always pin it, or put it on hold with apt-mark. It is not spam, it is
keeping your system clean.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Cindy-Sue Causey wrote:
> 
> 
> Ok, so this is where the OP, VigneshDhanraj, could pin their kernel if
> they know the release number... That's a-suming one can pin out of
> numerical sequence...

No, that script is for automatically marking for autoremoval no longer
needed kernels and keeping at least last 2. If he wants to pin it, it is
done as always at /etc/apt/preferences, or even better under some file
under /etc/apt/preferences.d/. Or he can simply use apt-mark to put it
on hold. If that is what he really want. In my opinion, it is better
just to give a shot to new kernel and keep old one just as long as he
needs to be sure that new one works. Besides, if he does not clean apt
archives in /var/cache/apt/archives, he will have there older kernels
that can be installed with dpkg.
> 
> The "deal" about it, the rationale that the toggle is buried there
> would be that pinning, not pinning kernels versus "just" other
> software would most likely matter most to someone who is tech savvy
> enough to have that need. That person would know they need to go
> digging for the toggle that helps preserve their tear stained kernel.
> :)
> 
> Interesting to know. I JUST yesterday downloaded the .xz tar for
> 4.12.3 for purposes of self-education. The new tip learned from this
> thread is perfectly timed and priceless. :)
> 
> Cindy :)
> -- 
> Cindy-Sue Causey
> Talking Rock, Pickens County, Georgia, USA
> 
> * runs with duct tape *
> 

Re: Need to upgrade to jessie need help

[Patrick Bartek]

On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
 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

Re: Need to upgrade to jessie need help

[Greg Wooledge]

Is there any way to permanently neuter apt-get autoremove, so that even
if something invokes it against my will, it will *never* remove anything?

And more, is there a way to get apt and apt-get to *stop* prompting me
to run it, and *stop* spamming me with a list of packages that it would
like me to remove?  (Maybe that's the same as the first question, maybe
not.)

My strategy so far has been "ignore the spam, and never willingly run
autoremove".  This mostly works, but I recently learned that tasksel
will apparently run an autoremove, without warning, whether I want it
to or not ().

If autoremove will also remove *kernels*, which this thread seems to
indicate is the case, then my concerns just went up another notch.

I suppose one could manually mark each and every single installed
package as "manually installed", but you'd have to remember to repeat
this periodically, and it seems clumsy and inelegant compared to some
sort of master switch that can just tell autoremove to go die in a fire.

Re: Need to upgrade to jessie need help

[Cindy-Sue Causey]

On 7/25/17, Dejan Jocic  wrote:
> On 25-07-17, Cindy-Sue Causey wrote:
>> On 7/25/17, Dejan Jocic  wrote:
>> > On 25-07-17, Greg Wooledge wrote:
>> >> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
>> >> > When you upgrade to Jessie, it will install new kernel
>> >> > automatically.
>> >> > However, it should not remove your Wheezy kernel, because upgrading
>> >> > kernels always leaves one old one there, in case that you can not
>> >> > boot
>> >> > into your new kernel for some reason. You can then mark that kernel
>> >> > via
>> >> > grub options as one you would like to boot in. You can do it during
>> >> > boot
>> >> > in grub, or by setting it as default in /etc/default/grub.
>> >>
>> >> All true.
>> >>
>> >> > You will also
>> >> > have to use apt-mark to put that kernel on hold, to prevent removing
>> >> > it
>> >> > on future updates, or to do some apt pinning.
>> >>
>> >> False.  The kernel will simply sit there forever, unless you take some
>> >> explicit action to remove it.  No holds or pinning or other wrestling
>> >> required.
>> >>
>> >
>> > That is not true, if you use autoremove. Only 2 last kernels will be
>> > kept. This is upgrade from Jessie here. I have 4.9.0.2 and 4.9.0.3
>> > kernels. Jessie kernel is long gone with autoremove.
>>
>>
>> Well, that's a little... scary. *frown*
>>
>> Except that... I just deleted the rest of what I first wrote because
>> it hit me. Autoremove is what apt-get tells me to use to remove
>> packages. that are no longer needed that are no longer
>> "dependencies". What it actually tells *me* is something like "apt
>> autoremove" (not "apt-get autoremove").
>>
>> Aaaa... So in autoremove's mind... It might touch on that previous
>> kernel and say... hm, nothing's using it now, nothing needs it to
>> function properly, so trash it
>>
>> Or something like that there.. :)
>>
>> Cindy :)
>> --
>> Cindy-Sue Causey
>> Talking Rock, Pickens County, Georgia, USA
>>
>> * runs with duct tape *
>>
>
> What it touch is /etc/kernel/postinst.d/apt-auto-removal that generates
> /etc/apt/apt.conf.d/01autoremove-kernels file. Those decide what kernels
> to keep. And, in case of /etc/kernel/postinst.d/apt-auto-removal it is
> clearly stated:
>
> # Mark as not-for-autoremoval those kernel packages that are: - the
> # currently booted version - the kernel version we've been called for -
> # the latest kernel version (as determined by debian version number) -
> # the second-latest kernel version
> #
> # In the common case this results in two kernels saved (booted into the
> # second-latest kernel, we install the latest kernel in an upgrade), but
> # can save up to four. Kernel refers here to a distinct release, which
> # can potentially be installed in multiple flavours counting as one
> # kernel.


Ok, so this is where the OP, VigneshDhanraj, could pin their kernel if
they know the release number... That's a-suming one can pin out of
numerical sequence...

The "deal" about it, the rationale that the toggle is buried there
would be that pinning, not pinning kernels versus "just" other
software would most likely matter most to someone who is tech savvy
enough to have that need. That person would know they need to go
digging for the toggle that helps preserve their tear stained kernel.
:)

Interesting to know. I JUST yesterday downloaded the .xz tar for
4.12.3 for purposes of self-education. The new tip learned from this
thread is perfectly timed and priceless. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Cindy-Sue Causey wrote:
> On 7/25/17, Dejan Jocic  wrote:
> > On 25-07-17, Greg Wooledge wrote:
> >> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> >> > When you upgrade to Jessie, it will install new kernel automatically.
> >> > However, it should not remove your Wheezy kernel, because upgrading
> >> > kernels always leaves one old one there, in case that you can not boot
> >> > into your new kernel for some reason. You can then mark that kernel via
> >> > grub options as one you would like to boot in. You can do it during
> >> > boot
> >> > in grub, or by setting it as default in /etc/default/grub.
> >>
> >> All true.
> >>
> >> > You will also
> >> > have to use apt-mark to put that kernel on hold, to prevent removing it
> >> > on future updates, or to do some apt pinning.
> >>
> >> False.  The kernel will simply sit there forever, unless you take some
> >> explicit action to remove it.  No holds or pinning or other wrestling
> >> required.
> >>
> >
> > That is not true, if you use autoremove. Only 2 last kernels will be
> > kept. This is upgrade from Jessie here. I have 4.9.0.2 and 4.9.0.3
> > kernels. Jessie kernel is long gone with autoremove.
> 
> 
> Well, that's a little... scary. *frown*
> 
> Except that... I just deleted the rest of what I first wrote because
> it hit me. Autoremove is what apt-get tells me to use to remove
> packages. that are no longer needed that are no longer
> "dependencies". What it actually tells *me* is something like "apt
> autoremove" (not "apt-get autoremove").
> 
> Aaaa... So in autoremove's mind... It might touch on that previous
> kernel and say... hm, nothing's using it now, nothing needs it to
> function properly, so trash it
> 
> Or something like that there.. :)
> 
> Cindy :)
> -- 
> Cindy-Sue Causey
> Talking Rock, Pickens County, Georgia, USA
> 
> * runs with duct tape *
> 

What it touch is /etc/kernel/postinst.d/apt-auto-removal that generates
/etc/apt/apt.conf.d/01autoremove-kernels file. Those decide what kernels
to keep. And, in case of /etc/kernel/postinst.d/apt-auto-removal it is
clearly stated:

# Mark as not-for-autoremoval those kernel packages that are: - the
# currently booted version - the kernel version we've been called for -
# the latest kernel version (as determined by debian version number) -
# the second-latest kernel version
#
# In the common case this results in two kernels saved (booted into the
# second-latest kernel, we install the latest kernel in an upgrade), but
# can save up to four. Kernel refers here to a distinct release, which
# can potentially be installed in multiple flavours counting as one
# kernel.

Re: Need to upgrade to jessie need help

[Cindy-Sue Causey]

On 7/25/17, Dejan Jocic  wrote:
> On 25-07-17, Greg Wooledge wrote:
>> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
>> > When you upgrade to Jessie, it will install new kernel automatically.
>> > However, it should not remove your Wheezy kernel, because upgrading
>> > kernels always leaves one old one there, in case that you can not boot
>> > into your new kernel for some reason. You can then mark that kernel via
>> > grub options as one you would like to boot in. You can do it during
>> > boot
>> > in grub, or by setting it as default in /etc/default/grub.
>>
>> All true.
>>
>> > You will also
>> > have to use apt-mark to put that kernel on hold, to prevent removing it
>> > on future updates, or to do some apt pinning.
>>
>> False.  The kernel will simply sit there forever, unless you take some
>> explicit action to remove it.  No holds or pinning or other wrestling
>> required.
>>
>
> That is not true, if you use autoremove. Only 2 last kernels will be
> kept. This is upgrade from Jessie here. I have 4.9.0.2 and 4.9.0.3
> kernels. Jessie kernel is long gone with autoremove.


Well, that's a little... scary. *frown*

Except that... I just deleted the rest of what I first wrote because
it hit me. Autoremove is what apt-get tells me to use to remove
packages. that are no longer needed that are no longer
"dependencies". What it actually tells *me* is something like "apt
autoremove" (not "apt-get autoremove").

Aaaa... So in autoremove's mind... It might touch on that previous
kernel and say... hm, nothing's using it now, nothing needs it to
function properly, so trash it

Or something like that there.. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Greg Wooledge wrote:
> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> > When you upgrade to Jessie, it will install new kernel automatically.
> > However, it should not remove your Wheezy kernel, because upgrading
> > kernels always leaves one old one there, in case that you can not boot
> > into your new kernel for some reason. You can then mark that kernel via
> > grub options as one you would like to boot in. You can do it during boot
> > in grub, or by setting it as default in /etc/default/grub.
> 
> All true.
> 
> > You will also
> > have to use apt-mark to put that kernel on hold, to prevent removing it
> > on future updates, or to do some apt pinning.
> 
> False.  The kernel will simply sit there forever, unless you take some
> explicit action to remove it.  No holds or pinning or other wrestling
> required.
> 

That is not true, if you use autoremove. Only 2 last kernels will be
kept. This is upgrade from Jessie here. I have 4.9.0.2 and 4.9.0.3
kernels. Jessie kernel is long gone with autoremove.

Re: Need to upgrade to jessie need help

[Greg Wooledge]

On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> When you upgrade to Jessie, it will install new kernel automatically.
> However, it should not remove your Wheezy kernel, because upgrading
> kernels always leaves one old one there, in case that you can not boot
> into your new kernel for some reason. You can then mark that kernel via
> grub options as one you would like to boot in. You can do it during boot
> in grub, or by setting it as default in /etc/default/grub.

All true.

> You will also
> have to use apt-mark to put that kernel on hold, to prevent removing it
> on future updates, or to do some apt pinning.

False.  The kernel will simply sit there forever, unless you take some
explicit action to remove it.  No holds or pinning or other wrestling
required.

Re: Need to upgrade to jessie need help

[Georgi Naplatanov]

On 07/25/2017 09:12 AM, VigneshDhanraj G 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. 


Hi Vignesh,

why do you want to use Wheezy's kernel on Jessie, custom kernel space
drivers maybe? I'm just curious.

On the other hand Jessie's kernel (3.16) became kernel.org LTS release
and is well maintained.

Kind regards
Georgi

Re: Need to upgrade to jessie need help

[VigneshDhanraj G]

Thanks Dejan Jocic. Let me try and get back to you.

On Tue, Jul 25, 2017 at 1:11 PM, Dejan Jocic  wrote:

> On 25-07-17, VigneshDhanraj G 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?
> >
> > Regards,
> > VigneshDhanraj G
>
> When you upgrade to Jessie, it will install new kernel automatically.
> However, it should not remove your Wheezy kernel, because upgrading
> kernels always leaves one old one there, in case that you can not boot
> into your new kernel for some reason. You can then mark that kernel via
> grub options as one you would like to boot in. You can do it during boot
> in grub, or by setting it as default in /etc/default/grub. You will also
> have to use apt-mark to put that kernel on hold, to prevent removing it
> on future updates, or to do some apt pinning. But, since Wheezy will be
> out of support soon, doubt that you will be able to expect security
> updates for that kernel. It would be wise to check if newer kernel works
> for you, and if it does to move to it completely and forget about Wheezy
> kernel.
>
>
>
>

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, VigneshDhanraj G 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?
> 
> Regards,
> VigneshDhanraj G

When you upgrade to Jessie, it will install new kernel automatically.
However, it should not remove your Wheezy kernel, because upgrading
kernels always leaves one old one there, in case that you can not boot
into your new kernel for some reason. You can then mark that kernel via
grub options as one you would like to boot in. You can do it during boot
in grub, or by setting it as default in /etc/default/grub. You will also
have to use apt-mark to put that kernel on hold, to prevent removing it
on future updates, or to do some apt pinning. But, since Wheezy will be
out of support soon, doubt that you will be able to expect security
updates for that kernel. It would be wise to check if newer kernel works
for you, and if it does to move to it completely and forget about Wheezy
kernel.