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
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
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
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
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
> > > J
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
>
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
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 t
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
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 r
s who followed up with helpful discussions.
From: deloptes [delop...@gmail.com]
Sent: Thursday, February 22, 2018 12:35 PM
To: debian-user@lists.debian.org
Subject: Re: Wheezy to Stretch
Roberto C. Sánchez wrote:
> Just keep in mind that we all have diff
Roberto C. Sánchez wrote:
> Just keep in mind that we all have different experiences and different
> reasons for thinking and believing the things that we think and believe.
I can only support this (in fact all your writing, but removed most of it to
make it easier to read).
12+ Years ago I had
On Wed, Feb 21, 2018 at 11:07:09PM -0800, Jimmy Johnson wrote:
>
> First off you're quoting something you have read and not from any real
> experience.
You have aboslutely no evidence to support your statement. I don't
think rhkramer has specifically stated whether he is basing his
statements o
On Thursday, February 22, 2018 02:07:09 AM Jimmy Johnson wrote:
> On 02/21/2018 07:02 PM, rhkra...@gmail.com wrote:
> > On Wednesday, February 21, 2018 03:40:51 PM Jimmy Johnson wrote:
> >> On 02/21/2018 10:47 AM, Roberto C. S�nchez wrote:
> >>> Note that upgrades skipping a release (e.g., wheezy -
On 2018-02-21, Jimmy Johnson wrote:
[...]
> I know what I'm talking about ...
Dude, you're talking to a Debian developer.
OP, if you're reading this, I urge you to follow the advice of Roberto
and other wiser heads.
--
Liam
Hello,
On Thu, Feb 22, 2018 at 08:17:43AM +0100, deloptes wrote:
> Jimmy Johnson wrote:
> > I never said that! But I do know what I'm talking about because I do
> > what I'm talking about constantly.
>
> you have said that, because in the official upgrade notes, as Roberto
> pointed out, it says
Jimmy Johnson wrote:
> I never said that! But I do know what I'm talking about because I do
> what I'm talking about constantly.
>
you have said that, because in the official upgrade notes, as Roberto
pointed out, it says you can go only one level up at a time.
Perhaps your setup has nothing sp
On 02/21/2018 07:02 PM, rhkra...@gmail.com wrote:
On Wednesday, February 21, 2018 03:40:51 PM Jimmy Johnson wrote:
On 02/21/2018 10:47 AM, Roberto C. S�nchez wrote:
Note that upgrades skipping a release (e.g., wheezy -> stretch instead
of wheezy -> jessie -> stretch) are not supported. A fresh
On Wednesday, February 21, 2018 03:40:51 PM Jimmy Johnson wrote:
> On 02/21/2018 10:47 AM, Roberto C. Sánchez wrote:
> > Note that upgrades skipping a release (e.g., wheezy -> stretch instead
> > of wheezy -> jessie -> stretch) are not supported. A fresh install
> > sounds like the better route in
On Wed, 21 Feb 2018 17:45:51 + "Kleene, Steven (kleenesj)"
wrote:
> I am running Wheezy (v7 = oldoldstable) and intend to replace it with
> a fresh install of Stretch (v9 = stable) before Wheezy's support runs
> out on May 31st. I will try the default systemd installation and see
> how I lik
On 02/21/2018 02:10 PM, Karol Augustin wrote:
On 2018-02-21 21:42, Jimmy Johnson wrote:
On 02/21/2018 01:31 PM, deloptes wrote:
Jimmy Johnson wrote:
For all the "Na" Sayers here, nothing lost except for sometime and
something to gan the system you want and if you can't make it work
format and
On 02/21/2018 02:18 PM, Sven Joachim wrote:
On 2018-02-21 16:49 -0500, Greg Wooledge wrote:
On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:
Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
Stretch is that there is no _package_ named sysvinit in Stretch, so
On 2018-02-21 16:49 -0500, Greg Wooledge wrote:
> On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:
>> Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
>> Stretch is that there is no _package_ named sysvinit in Stretch, so you
>> will
On 2018-02-21 21:42, Jimmy Johnson wrote:
> On 02/21/2018 01:31 PM, deloptes wrote:
>> Jimmy Johnson wrote:
>>
>>> For all the "Na" Sayers here, nothing lost except for sometime and
>>> something to gan the system you want and if you can't make it work
>>> format and do a new system, but remember t
On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:
> Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
> Stretch is that there is no _package_ named sysvinit in Stretch, so you
> will be left with the old sysvinit from Wheezy and have to do a manual
>
On 02/21/2018 01:31 PM, deloptes wrote:
Jimmy Johnson wrote:
For all the "Na" Sayers here, nothing lost except for sometime and
something to gan the system you want and if you can't make it work
format and do a new system, but remember there is no "sysvinit" in
Stretch.
OK, I have a question:
a new
>> system, but remember there is no "sysvinit" in Stretch.
>
> There is. It's just not the default.
Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
Stretch is that there is no _package_ named sysvinit in Stretch, so you
will be left with the
On 02/21/2018 01:01 PM, Greg Wooledge wrote:
On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote:
For all the "Na" Sayers here, nothing lost except for sometime and something
to gan the system you want and if you can't make it work format and do a new
system, but remember there is no "
Jimmy Johnson wrote:
> For all the "Na" Sayers here, nothing lost except for sometime and
> something to gan the system you want and if you can't make it work
> format and do a new system, but remember there is no "sysvinit" in
> Stretch.
OK, I have a question:
Why do you think you are smarter th
On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote:
> For all the "Na" Sayers here, nothing lost except for sometime and something
> to gan the system you want and if you can't make it work format and do a new
> system, but remember there is no "sysvinit" in Stretch.
There is. It's jus
On 02/21/2018 10:39 AM, Jimmy Johnson wrote:
On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
I am running Wheezy (v7 = oldoldstable) and intend to replace it with
a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st. I will try the default systemd inst
On Wed, Feb 21, 2018 at 12:40:51PM -0800, Jimmy Johnson wrote:
> I know what I'm talking about
Same here.
> and if I can do it anybody can do it,
There is a big difference between *can* and *should*.
> Debian
> has given us all the tools we need to upgrade any stable release to current
> stable
On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st. I will try the default systemd installation and see how I like it.
Okay, but I s
On 2/21/2018 7:47 PM, Roberto C. Sánchez wrote:
On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote:
On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's
te in this case.
>
> Roberto, OP said he want to replace wheezy with fresh install. Just FYI.
>
Right. Then Jimmy made the rather unwise suggestion of upgrading
directly from wheezy to stretch and than also something about adding
backports source prior to upgrading.
I was simply rei
On 02/21/2018 10:47 AM, Roberto C. Sánchez wrote:
On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote:
On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy'
Roberto C. Sánchez wrote:
> Right. Then Jimmy made the rather unwise suggestion of upgrading
> directly from wheezy to stretch and than also something about adding
> backports source prior to upgrading.
>
> I was simply reinforcing the OP's original position that a fresh in
Roberto C. Sánchez wrote:
> Note that upgrades skipping a release (e.g., wheezy -> stretch instead
> of wheezy -> jessie -> stretch) are not supported. A fresh install
> sounds like the better route in this case.
Roberto, OP said he want to replace wheezy with fresh install. Just FYI.
regards
On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote:
> On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
> > I am running Wheezy (v7 = oldoldstable) and intend to replace it with a
> > fresh
> > install of Stretch (v9 = stable) before Wheezy's support runs out on May
> > 31st. I
Greg Wooledge composed on 2018-02-21 13:11 (UTC-0500):
> If you simply want to boot *once* into multi-user.target without
> changing the default target, you can edit the kernel command line
> and add the option "systemd.unit=multi-user.target".
> Which is a whole lot more typing than adding the o
On Wed, Feb 21, 2018 at 05:45:51PM +, Kleene, Steven (kleenesj) wrote:
> With sysvinit, I would set initdefault to runlevel 3
> in /etc/inittab. In /etc/rc3.d, I would rename gdm3 so that I would boot
> into a terminal interface (command line) instead of Gnome. Then I would
> quickly install
I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st. I will try the default systemd installation and see how I like it.
After the installation, I will want to build my system from my favorite
w
On 06/24/2017 02:04 AM, Andrew wrote:
Ive tried to update a non GUI system from Wheezy to Stretch and its gone
horribly wrong.
Theres so many errors I cant even begin to fathom out what has gone
wrong and I think the only solution is going to be a clean install.
New infrastructure, new apt
I started in synaptic, first upgrading Debian tools and the kernel,
that blew out synaptic with dpkg errors and I went to the console and
ran apt-get -f install and then dpkg --configure -a, back in business, I
had to do that a few times and then able to switch to using the new apt
and clean u
Le 06/24/17 à 16:16, deloptes a écrit :
> Henrique de Moraes Holschuh wrote:
>
>> Which kinda means it would have been faster for you to do a full backup
>> (which you should always do before major upgrades, anyway) and install
>> stretch from scratch, I suppose.
>
> upgrade to jessie and then to
Henrique de Moraes Holschuh wrote:
> Which kinda means it would have been faster for you to do a full backup
> (which you should always do before major upgrades, anyway) and install
> stretch from scratch, I suppose.
upgrade to jessie and then to stretch would have worked if OP would have
read th
On Sat, 24 Jun 2017, Andrew wrote:
> Ive tried to update a non GUI system from Wheezy to Stretch and its gone
> horribly wrong.
...
> Would I have been wise to upgrade it to Jessie first?
Yes. The safest procedure is:
1. Update to the latest point-release of the version you have inst
On Sat, Jun 24, 2017 at 11:10:58AM +0200, Erwan David wrote:
> Le 06/24/17 à 11:04, Andrew a écrit :
> > Ive tried to update a non GUI system from Wheezy to Stretch and its gone
> > horribly wrong.
> >
> > Theres so many errors I cant even begin to fathom out what has
Le 06/24/17 à 11:04, Andrew a écrit :
> Ive tried to update a non GUI system from Wheezy to Stretch and its gone
> horribly wrong.
>
> Theres so many errors I cant even begin to fathom out what has gone
> wrong and I think the only solution is going to be a clean install.
>
&
Ive tried to update a non GUI system from Wheezy to Stretch and its gone
horribly wrong.
Theres so many errors I cant even begin to fathom out what has gone
wrong and I think the only solution is going to be a clean install.
Would I have been wise to upgrade it to Jessie first?
Regards
On Sun, 8/23/15, Jimmy Johnson wrote:
// While kdm still works in upstream stretch/testing, I've been told it is
// no longer being supported by systemd and has been replaced with sddm,
// but if you want to see your desktop currently you need to follow the
// instructions I gave you. For plasma
On 08/23/2015 01:19 PM, Ldten K wrote:
On Sun, 8/23/15, Jimmy Johnson wrote:
It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098
It may be the same issue though I'm not sure why I was getting the error about
missing /home/luser/.Xsession file. I manually copied /etc/kde4/kd
On Sun, 8/23/15, Jimmy Johnson wrote:
> It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098
It may be the same issue though I'm not sure why I was getting the error about
missing /home/luser/.Xsession file. I manually copied /etc/kde4/kdm/Xsession
file as /home/luser/.Xsession
On 08/23/2015 02:16 AM, Ldten K wrote:
Hi,
Tried upgrading from wheezy to stretch, just to see how it would go. It mostly
went OK though there is an issue: when trying to log in from kdm the system now
complains that it's unable to start X session --- no /home/luser/.xsession
file, no
Hi,
Tried upgrading from wheezy to stretch, just to see how it would go. It mostly
went OK though there is an issue: when trying to log in from kdm the system now
complains that it's unable to start X session --- no /home/luser/.xsession
file, no /home/luser/.Xsession file, no session man
68 matches
Mail list logo
