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
On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote:
>
> "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
> worki
On Thursday 19 April 2018 15:23:16 Dan Ritter wrote:
> On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote:
> > On Thursday 19 April 2018 11:32:28 Roberto C. Sánchez wrote:
> > > The only thing I would say is use apt "pinning" to prioritize the
> > > backports repository lower than the ot
On Thu, Apr 19, 2018 at 03:46:17PM -0400, Gene Heskett wrote:
> I realize that Greg, but debian's support for armhf for unusual
> applications that require a realtime environment, is at its finest, an
> afterthought and discarded. We linuxcnc runners are used to it. So we
> build our own kernel
On Thursday 19 April 2018 14:59:04 Greg Wooledge wrote:
> On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote:
> > 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 d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Apr 19, 2018 at 02:59:04PM -0400, Greg Wooledge wrote:
> On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote:
> > Hijacking a thread here, but it reads like I might be reading an expert.
> >
> > "Pinning" is an interesting subject Rob
On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote:
> On Thursday 19 April 2018 11:32:28 Roberto C. Sánchez wrote:
>
> > 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 backport
On Thu, Apr 19, 2018 at 02:47:05PM -0400, Gene Heskett wrote:
> 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
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
On Thu, Apr 19, 2018 at 11:45:11AM -0400, David Parker wrote:
>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.
Neither of the package front-ends
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 pac
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 jess
On Thu, Apr 19, 2018 at 11:18:43AM -0400, Roberto C. Sánchez wrote:
> - backup your pacemaker configurations and user-generated files, let
>the upgrade process remove the packages, then restore everything
>after the upgrade is complete
I'm still stumped by the claim that the configuration
-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
On Thu, Apr 19, 2018 at 10:57:09AM -0400, David Parker wrote:
>
>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.
>If it's simply not possible to do this upgrade the
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 insta
On Thu 12 Apr 2018 at 06:42:33 (-0400), Dan Ritter wrote:
> On Wed, Apr 11, 2018 at 07:57:07PM -0500, David Wright wrote:
> > On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote:
> > > I am trying to upgrade two test boxes from Wheezy to Stretch (skipping
> > > Jessie). The upgrade worked o
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
On Wed, Apr 11, 2018 at 07:57:07PM -0500, David Wright wrote:
> On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote:
> > 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-
On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote:
> 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 ult
On Wed, 11 Apr 2018 15:31:32 -0400 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 a
David Parker wrote:
> Any ideas or suggestions for resolving this will be greatly appreciated.
it is definitely less effort to upgrade to jessie and then to stretch - it
just takes a bit more time, but less effort in debugging.
can you reinstall or configure bsdmainutils?
or purge man and bsdmai
22 matches
Mail list logo
