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


Groups > linux.debian.user > #194872

Re: Error while upgrading from Wheezy to Stretch

From David Parker <dparker@utica.edu>
Newsgroups linux.debian.user
Subject Re: Error while upgrading from Wheezy to Stretch
Date 2018-04-19 17:50 +0200
Message-ID <vGjYR-2RI-3@gated-at.bofh.it> (permalink)
References (3 earlier) <vDPix-qn-1@gated-at.bofh.it> <vGjct-2jm-5@gated-at.bofh.it> <vGjvP-2G7-3@gated-at.bofh.it> <vGjFw-2KB-13@gated-at.bofh.it> <vGjPb-2Og-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

I never thought to use the backports repo in Jessie to keep pacemaker
installed.  That's a great idea, I'll give it a try and see what happens.

Regarding Pacemaker's data and config, as far as I could tell, it was
gone.  I'm not positive what happened with it, but I wonder if the fact
that the pacemaker package was missing entirely from the new release caused
apt to just get rid of it during the upgrade.  I can also re-try that and
keep closer track of what gets removed.  I do know that when I upgraded
from Wheezy to Jessie and then to Stretch, and then I re-installed
Pacemaker in Stretch, it didn't find any old config data and acted like a
new installation.

Thanks!
Dave

On Thu, Apr 19, 2018 at 11:32 AM, Roberto C. Sánchez <roberto@debian.org>
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
> --
> Roberto C. Sánchez
>
>


-- 
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Error while upgrading from Wheezy to Stretch David Parker <dparker@utica.edu> - 2018-04-11 21:40 +0200
  Re: Error while upgrading from Wheezy to Stretch deloptes <deloptes@gmail.com> - 2018-04-11 23:20 +0200
  Re: Error while upgrading from Wheezy to Stretch Patrick Bartek <nemommxiv@gmail.com> - 2018-04-12 01:40 +0200
  Re: Error while upgrading from Wheezy to Stretch David Wright <deblis@lionunicorn.co.uk> - 2018-04-12 03:00 +0200
    Re: Error while upgrading from Wheezy to Stretch Dan Ritter <dsr@randomstring.org> - 2018-04-12 12:50 +0200
      Re: Error while upgrading from Wheezy to Stretch David Wright <deblis@lionunicorn.co.uk> - 2018-04-12 20:40 +0200
        Re: Error while upgrading from Wheezy to Stretch David Parker <dparker@utica.edu> - 2018-04-19 17:00 +0200
          Re: Error while upgrading from Wheezy to Stretch Roberto C. Sánchez <roberto@debian.org> - 2018-04-19 17:20 +0200
            Re: Error while upgrading from Wheezy to Stretch Greg Wooledge <wooledg@eeg.ccf.org> - 2018-04-19 17:30 +0200
              Re: Error while upgrading from Wheezy to Stretch Roberto C. Sánchez <roberto@debian.org> - 2018-04-19 17:40 +0200
                Re: Error while upgrading from Wheezy to Stretch David Parker <dparker@utica.edu> - 2018-04-19 17:50 +0200
                Re: Error while upgrading from Wheezy to Stretch Roberto C. Sánchez <roberto@debian.org> - 2018-04-19 19:50 +0200
                Re: Error while upgrading from Wheezy to Stretch Gene Heskett <gheskett@shentel.net> - 2018-04-19 20:50 +0200
                Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch) Greg Wooledge <wooledg@eeg.ccf.org> - 2018-04-19 21:00 +0200
                Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch) <tomas@tuxteam.de> - 2018-04-19 21:30 +0200
                Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch) Gene Heskett <gheskett@shentel.net> - 2018-04-19 21:50 +0200
                Re: Pinning (was Re: Error while upgrading from Wheezy to Stretch) Greg Wooledge <wooledg@eeg.ccf.org> - 2018-04-19 22:30 +0200
                Re: Error while upgrading from Wheezy to Stretch Dan Ritter <dsr@randomstring.org> - 2018-04-19 21:30 +0200
                Re: Error while upgrading from Wheezy to Stretch Gene Heskett <gheskett@shentel.net> - 2018-04-19 22:40 +0200
                Re: Error while upgrading from Wheezy to Stretch Roberto C. Sánchez <roberto@debian.org> - 2018-04-20 00:50 +0200
          Re: Error while upgrading from Wheezy to Stretch <tomas@tuxteam.de> - 2018-04-19 17:30 +0200
  Re: Error while upgrading from Wheezy to Stretch songbird <songbird@anthive.com> - 2018-04-12 17:00 +0200
  Re: Error while upgrading from Wheezy to Stretch Jimmy Johnson <field.engineer@gmail.com> - 2018-04-20 05:00 +0200

csiph-web