[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Error while upgrading from Wheezy to Stretch

On Thursday 19 April 2018 11:32:28 Roberto C. Sánchez wrote:

> On Thu, Apr 19, 2018 at 11:26:20AM -0400, Greg Wooledge wrote:
> > According to http://packages.debian.org/pacemaker there is also a
> > backport of the stretch version of the package in the
> > jessie-backports repository.  So perhaps there is some way to
> > convince the jessie upgrade to use the jessie-backports version of
> > this package rather than removing it.  But that's beyond my
> > experience.
> I totally forgot about backports. Generally, including backports
> repositories of the upgrade target (i.e., the suite being upgraded to)
> is not a good idea. However, this situation would qualify as
> extenuating circumstances. Plus, someone who manages a HA cluster
> almost certainly has the skills to deal with the occasional minor
> hiccup assocaited with mixing backports into an upgrade.
> The only thing I would say is use apt "pinning" to prioritize the
> backports repository lower than the other repositories so you don't
> accidentally get backports for *everything* that has a backport
> available.
> Regards,
> -Roberto

Hijacking a thread here, but it reads like I might be reading an expert.

"Pinning" is an interesting subject Roberto, interesting because the info 
on how to do it is generally skipped over, or only mentioned in passing, 
with NO examples of how to do it in the man pages available. I have it 
working on one machine, but it was a heck of a trip getting there, and I 
still have had no confirmation that I actually did it correctly. That 
machine is a raspi-3b running jessie. But with an rt-preempt kernel 
because its main reason-de-terre is LinuxCNC.  Its running a 3/4 ton 
metal working lathe.

In /etc/apt/preferences.d/kernel.pref:
pi@picnc:/etc/apt/preferences.d $ cat kernel.pref
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

Is this the approved method? All I know is that for me, its working, and 
anything related to a kernel update is skipped.

Thanks for any further insight.

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 <http://geneslinuxbox.net:6309/gene>

Reply to: