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


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

Error while upgrading from Wheezy to Stretch

Started byDavid Parker <dparker@utica.edu>
First post2018-04-11 21:40 +0200
Last post2018-04-20 05:00 +0200
Articles 3 on this page of 23 — 11 participants

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


Contents

  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

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


#194867

From<tomas@tuxteam.de>
Date2018-04-19 17:30 +0200
Message-ID<vGjFv-2KB-1@gated-at.bofh.it>
In reply to#194861
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Apr 19, 2018 at 10:57:09AM -0400, David Parker wrote:
> Hi all,
> 
> Sorry I didn't get back to this sooner, had some crazy life stuff getting
> in the way.
> 
> I should have said in my original post that there is a reason I'm trying to
> jump from Wheezy to Stretch.  These boxes are in an HA cluster with
> Pacemaker, Corosync, and DRBD.  I have all 3 of these installed from the
> Debian packages.  Pacemaker is not in Jessie (apparently the devs missed
> the deadline for inclusion), so an upgrade to Jessie uninstalls pacemaker
> and all of its configuration.  That's what I was hoping to avoid, because
> setting up an configuring Pacemaker always takes me a while to get right,
> so an upgrade path which does not include the removal of it is preferable.
> 
> I did read the documentation and I did try Wheezy -> Jessie - > Stretch
> first, but the problem was that Pacemaker was removed.  Hence, I was hoping
> to skip Jessie.

[...]

Ah, but it is in jessie-backports [1]. I'd try to include those in your
jessie sources.list, perhaps that works out cleanly.

Cheers

[1] https://packages.debian.org/jessie-backports/pacemaker
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEUEARECAAYFAlrYtD0ACgkQBcgs9XrR2karzwCdHigm1KB6gme1VnM69pIdmyTb
QooAlirVC3IKdWMcVewH/wFP5qSmcL8=
=S3nD
-----END PGP SIGNATURE-----

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


#194726

Fromsongbird <songbird@anthive.com>
Date2018-04-12 17:00 +0200
Message-ID<vDLRE-6vV-5@gated-at.bofh.it>
In reply to#194710
David Parker wrote:
...

  given they are test boxes you should go straight
to reinstall from netinst image or whatever you can
get that will do it.  :)

  much much faster than trying to fiddle around with
upgrades.  especially when many versions in between.

  of course, always check installation notes for 
errata and look to see if there are a lot of issues
reported for your specific hardware.


  songbird

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


#194900

FromJimmy Johnson <field.engineer@gmail.com>
Date2018-04-20 05:00 +0200
Message-ID<vGurg-1u8-13@gated-at.bofh.it>
In reply to#194710
On 04/11/2018 12:31 PM, David Parker wrote:
> Hello,
> 
> I am trying to upgrade two test boxes from Wheezy to Stretch (skipping
> Jessie).  The upgrade worked on one of them, although I ran into errors and
> had to run "apt-get -f install" a few times, but that resolved the issues
> and it ultimately worked.
> 
> However, on the second box, I ran into an error about halfway through the
> upgrade, and I'm not able to get past it.  No matter what I do, I keep
> running into version mismatch issue with libpam-modules.  It's preventing
> the upgrade from finishing.
> 
> # apt-get -f install
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Correcting dependencies... Done
> The following packages were automatically installed and are no longer
> required:
>    libcfg4 libcib1 libclass-isa-perl libconfdb4 libcoroipcc4 libcoroipcs4
> libcrmcluster1 libcrmcommon2 libevs4 liblogsys4 libpe-status3 libpengine3
> libpload4 libquorum4 libsam4 libstonithd1 libswitch-perl
>    libsystemd-login0 libtransitioner1 libvotequorum4
> Use 'apt autoremove' to remove them.
> The following additional packages will be installed:
>    libpam-modules
> The following packages will be upgraded:
>    libpam-modules
> 1 upgraded, 0 newly installed, 0 to remove and 199 not upgraded.
> 2 not fully installed or removed.
> Need to get 0 B/308 kB of archives.
> After this operation, 62.5 kB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Preconfiguring packages ...
> dpkg: dependency problems prevent processing triggers for man-db:
>   man-db depends on bsdmainutils; however:
>    Package bsdmainutils is not configured yet.
> 
> dpkg: error processing archive
> /var/cache/apt/archives/libpam-modules_1.1.8-3.6_amd64.deb (--unpack):
>   dependency problems - leaving triggers unprocessed
> Errors were encountered while processing:
>   /var/cache/apt/archives/libpam-modules_1.1.8-3.6_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Any ideas or suggestions for resolving this will be greatly appreciated.


Yes, use aptitude until you get going again.  Aptitude will analyze the 
problem and make suggestions. aptitude update and aptitude -f install.

Cheers,
-- 
Jimmy Johnson

Devuan ASCII - Trinity TDE-3 version R14.0.5 - Intel P8400 - EXT4 at sda6
Registered Linux User #380263

[toc] | [prev] | [standalone]


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

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


csiph-web