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

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

unhappy upgrade

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

Contents

  unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-02 18:00 +0200
    Re: unhappy upgrade "Andrew M.A. Cater" <amacater@einval.com> - 2021-10-02 18:30 +0200
      Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 17:10 +0200
        Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 19:20 +0200
          Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 19:30 +0200
    Re: unhappy upgrade Greg Wooledge <greg@wooledge.org> - 2021-10-02 18:40 +0200
      Re: unhappy upgrade "Andrew M.A. Cater" <amacater@einval.com> - 2021-10-02 20:20 +0200
        Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 18:30 +0200
      Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 18:20 +0200
    Re: unhappy upgrade David Christensen <dpchrist@holgerdanske.com> - 2021-10-02 20:40 +0200
      Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 18:30 +0200
        Re: unhappy upgrade David Christensen <dpchrist@holgerdanske.com> - 2021-10-03 20:10 +0200
    Re: unhappy upgrade Patrick Bartek <nemommxiv@gmail.com> - 2021-10-03 06:20 +0200
      Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-03 18:50 +0200
        Re: unhappy upgrade Greg Wooledge <greg@wooledge.org> - 2021-10-03 19:00 +0200
          Re: unhappy upgrade David Wright <deblis@lionunicorn.co.uk> - 2021-10-03 20:00 +0200
        Re: unhappy upgrade Patrick Bartek <nemommxiv@gmail.com> - 2021-10-04 01:50 +0200
          Re: unhappy upgrade Greg Wooledge <greg@wooledge.org> - 2021-10-04 02:00 +0200
            Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-04 21:30 +0200
              Re: unhappy upgrade David Wright <deblis@lionunicorn.co.uk> - 2021-10-05 02:00 +0200
                Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-05 03:20 +0200
                  Re: unhappy upgrade David Wright <deblis@lionunicorn.co.uk> - 2021-10-05 15:10 +0200
                    Re: unhappy upgrade Kenneth Parker <sea7kenp@gmail.com> - 2021-10-05 16:50 +0200
                      Re: unhappy upgrade David Wright <deblis@lionunicorn.co.uk> - 2021-10-05 18:20 +0200
                      Re: unhappy upgrade Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-06 07:00 +0200
                    Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-05 17:00 +0200
                      Re: unhappy upgrade David Wright <deblis@lionunicorn.co.uk> - 2021-10-05 18:20 +0200
          Re: unhappy upgrade "Roy J. Tellason, Sr." <roy@rtellason.com> - 2021-10-04 20:50 +0200
            Re: unhappy upgrade Patrick Bartek <nemommxiv@gmail.com> - 2021-10-05 05:40 +0200

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

#240894

On Monday 04 October 2021 07:55:25 pm David Wright wrote:
> On Mon 04 Oct 2021 at 15:25:23 (-0400), Roy J. Tellason, Sr. wrote:
> > On Sunday 03 October 2021 07:53:39 pm Greg Wooledge wrote:
> > > On Sun, Oct 03, 2021 at 04:48:38PM -0700, Patrick Bartek wrote:
> > > > On Sun, 3 Oct 2021 12:49:12 -0400 "Roy J. Tellason, Sr." wrote:
> > > > > I did do a download from their site.  But it's not clear to me where
> > > > > I need to put it and how to tell the package management software
> > > > > about it.
> > > > 
> > > > Did you download the .deb file of it?  You can use dpkg to install, but
> > > > it won't automatically take care of dependencies.  I use gdebi-core, a
> > > > command line utility, that will install the .deb file correctly and
> > > > install any dependencies. You must be root to install.
> > > 
> > > You can also use this command to install a locally-downloaded .deb
> > > package and its dependencies:
> > > 
> > > apt install ./filename.deb
> > 
> > Okay,  I was using a bunch of diferent apt-get commands to do the upgrade.  This is part of why I'm getting confused,  too many tools with very similar
> > names...  :-) 
> > 
> > That *did* install it,  and also gave me a really long list of stuff that it said wasn't needed any more,  but which I didn't deal with at all.  I assume that the next
> > time around the apt-get autoremove command will take care of that?  It also downloaded one library to work with the package,  no big deal there. 
> > 
> > I don't see virtualbox in my applications menu.  Rebooting,  I am seeing a *lot* of disk activity,  don't know what it's doing there,  during the boot process.  After
> > it gets the whole way booted,  everything is smaller on my screen!  This is _not_ good for these 70-YO eyes, 
> > 
> > I had thought initially that the program had not been installed into my applications menu.  But it turns out that they changed the name!  Instead of being in there
> > under "virtualbox" it's now in there umder "Oracle VM Virtualbox",  which is why I missed it. 
> > 
> > Tried it out,  it runs.  I'm not going to start it right now as I'm currently still running it on this laptop,  and that would not go well.  I guess I need to deal with
> > moving some files around,  maybe do an rsync or something,  and then shut this one down. 
> > 
> > Incidentally the issues with Konqueror and Okular seem to have gone away as well.
> > 
> > Now the only thing I need to do is get things back to something like the sizes I had before so I can read 'em.  Hell,  I can't even read the clock in my taskbar! 
> > Any thoughts as to how to do that? 
> 
> It would help people trying to follow what you are doing just to confirm at each stage which version you're now running.
> I /think/ you've got as far as stretch.

Yes,  I wanted to get the issues that I was seeing resolved before I went ahead and proceeded with the rest of the upgrades.  At this point I've copied things from the laptop (which got very flaky on me) back to the workstation and I am doing my mail there,  like I used to.  The font is too damn small,  though.
 
> So the main things to confirm as working are the specific points mentioned in the respective Release Notes. In stretch that would
> be, for example, the 4.9 kernel is finding everything, 

About the only issue that I've noticed after this stuff all getting fixed is that there's something up with the sound.  Given the details of what advice I saw someone else getting,  I have a few things to look at.  The virtualbox OS complained about it too.  :-)

> that X may be running as a user (rather than root) on the console it's started from, 

I'm not sure I see the concern here.

> and that your ethernet or wireless connectivity is still good. (Changes were made to the kernel device naming.) 

Ethernet is working fine here,  as evidenced by the fact that I'm moving lots of data back and forth (32GB for this virtualbox stuff ferinstance) and that I'm doing my mail on this system now.  If there had been any issues with that I sure would've been jumping all over it,  as I tend to use networking rather heavily.  And there is no wireless on this machine.
 
> Those are just a few I recall, but note they all relate to the OS rather than details in configuring third-party applications.
> Once that's done, time to read the next set of Release Notes. Note that even things like the best tool (apt-get or aptitude) to
> upgrade with may vary from release to release which, remember, are normally separated by a couple of years of tool development.
 
I saw a couple of references that stated that aptitude had been recommeded earlier but that apt was now a better choice.

So we'll see how it goes from here.  My upgrade path for this step went like this:

apt-get autoremove
edit the sources.list file replacing jessie with stretch
apt-get update
apt-get upgrade
apt-get dist-upgrade

And then reboot,  and see how well things work.  Or maybe reboot a couple of times...

We'll see how it goes.

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

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

#240910

On Mon 04 Oct 2021 at 21:16:06 (-0400), Roy J. Tellason, Sr. wrote:
> On Monday 04 October 2021 07:55:25 pm David Wright wrote:

> > It would help people trying to follow what you are doing just to confirm at each stage which version you're now running.
> > I /think/ you've got as far as stretch.
> 
> Yes,  I wanted to get the issues that I was seeing resolved before I went ahead and proceeded with the rest of the upgrades.  At this point I've copied things from the laptop (which got very flaky on me) back to the workstation and I am doing my mail there,  like I used to.  The font is too damn small,  though.
>  
> > So the main things to confirm as working are the specific points mentioned in the respective Release Notes. In stretch that would
> > be, for example, the 4.9 kernel is finding everything, 
> 
> About the only issue that I've noticed after this stuff all getting fixed is that there's something up with the sound.  Given the details of what advice I saw someone else getting,  I have a few things to look at.  The virtualbox OS complained about it too.  :-)

I can't see the point unless you depend on, say, a screen reader to be
able to move forward at all. After all, how long are you intending to
run stretch for?

> > that X may be running as a user (rather than root) on the console it's started from, 
> 
> I'm not sure I see the concern here.

An issue that caught some people out was finding the X server log,
as it had to move out of /var/log/ (users don't have permission),
and into a "hidden" directory, ~/.local/share/xorg/. Running
root-owned applications is different, and you can get permissions
problems with opening devices. Unusual though.

> > and that your ethernet or wireless connectivity is still good. (Changes were made to the kernel device naming.) 
> 
> Ethernet is working fine here,  as evidenced by the fact that I'm moving lots of data back and forth (32GB for this virtualbox stuff ferinstance) and that I'm doing my mail on this system now.  If there had been any issues with that I sure would've been jumping all over it,  as I tend to use networking rather heavily.  And there is no wireless on this machine.
>  
> > Those are just a few I recall, but note they all relate to the OS rather than details in configuring third-party applications.
> > Once that's done, time to read the next set of Release Notes. Note that even things like the best tool (apt-get or aptitude) to
> > upgrade with may vary from release to release which, remember, are normally separated by a couple of years of tool development.
>  
> I saw a couple of references that stated that aptitude had been recommeded earlier but that apt was now a better choice.

Yes, I think apt is recommended for an interactive upgrade.

> So we'll see how it goes from here.  My upgrade path for this step went like this:
> 
> apt-get autoremove
> edit the sources.list file replacing jessie with stretch
> apt-get update
> apt-get upgrade
> apt-get dist-upgrade
> 
> And then reboot,  and see how well things work.  Or maybe reboot a couple of times...

Yes, apt-get was recommended for upgrading to stretch. Note however
that if you perform your next upgrades with apt, as recommended,
some of the command names (like dist-upgrade) will differ in apt.

> We'll see how it goes.

Good luck.

Cheers,
David.

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

#240921

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

On Tue, Oct 5, 2021, 9:04 AM David Wright <deblis@lionunicorn.co.uk> wrote:

> On Mon 04 Oct 2021 at 21:16:06 (-0400), Roy J. Tellason, Sr. wrote:
> > On Monday 04 October 2021 07:55:25 pm David Wright wrote:
>
> > > It would help people trying to follow what you are doing just to
> confirm at each stage which version you're now running.
> > > I /think/ you've got as far as stretch.
> >
> > Yes,  I wanted to get the issues that I was seeing resolved before I
> went ahead and proceeded with the rest of the upgrades.  At this point I've
> copied things from the laptop (which got very flaky on me) back to the
> workstation and I am doing my mail there,  like I used to.  The font is too
> damn small,  though.
> >
> > > So the main things to confirm as working are the specific points
> mentioned in the respective Release Notes. In stretch that would
> > > be, for example, the 4.9 kernel is finding everything,
> >
> > About the only issue that I've noticed after this stuff all getting
> fixed is that there's something up with the sound.  Given the details of
> what advice I saw someone else getting,  I have a few things to look at.
> The virtualbox OS complained about it too.  :-)
>
> I can't see the point unless you depend on, say, a screen reader to be
> able to move forward at all. After all, how long are you intending to
> run stretch for?
>
> > > that X may be running as a user (rather than root) on the console it's
> started from,
> >
> > I'm not sure I see the concern here.
>
> An issue that caught some people out was finding the X server log,
> as it had to move out of /var/log/ (users don't have permission),
> and into a "hidden" directory, ~/.local/share/xorg/. Running
> root-owned applications is different, and you can get permissions
> problems with opening devices. Unusual though.
>
> > > and that your ethernet or wireless connectivity is still good.
> (Changes were made to the kernel device naming.)
> >
> > Ethernet is working fine here,  as evidenced by the fact that I'm moving
> lots of data back and forth (32GB for this virtualbox stuff ferinstance)
> and that I'm doing my mail on this system now.  If there had been any
> issues with that I sure would've been jumping all over it,  as I tend to
> use networking rather heavily.  And there is no wireless on this machine.
> >
> > > Those are just a few I recall, but note they all relate to the OS
> rather than details in configuring third-party applications.
> > > Once that's done, time to read the next set of Release Notes. Note
> that even things like the best tool (apt-get or aptitude) to
> > > upgrade with may vary from release to release which, remember, are
> normally separated by a couple of years of tool development.
> >
> > I saw a couple of references that stated that aptitude had been
> recommeded earlier but that apt was now a better choice.
>
> Yes, I think apt is recommended for an interactive upgrade.
>
> > So we'll see how it goes from here.  My upgrade path for this step went
> like this:
> >
> > apt-get autoremove
> > edit the sources.list file replacing jessie with stretch
> > apt-get update
> > apt-get upgrade
> > apt-get dist-upgrade
> >
> > And then reboot,  and see how well things work.  Or maybe reboot a
> couple of times...
>
> Yes, apt-get was recommended for upgrading to stretch. Note however
> that if you perform your next upgrades with apt, as recommended,
> some of the command names (like dist-upgrade) will differ in apt.
>

I thought "dist-upgrade" is used to upgrade packages that need a "version
change" (like, sometimes the Kernel).  Is this recent (i.e. Stretch?)

Kenneth Parker

>

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

#240927

On Tue 05 Oct 2021 at 10:48:03 (-0400), Kenneth Parker wrote:
> On Tue, Oct 5, 2021, 9:04 AM David Wright <deblis@lionunicorn.co.uk> wrote:

> > Yes, apt-get was recommended for upgrading to stretch. Note however
> > that if you perform your next upgrades with apt, as recommended,
> > some of the command names (like dist-upgrade) will differ in apt.
> >
> 
> I thought "dist-upgrade" is used to upgrade packages that need a "version
> change" (like, sometimes the Kernel).  Is this recent (i.e. Stretch?)

Over-caution on my part, I think, though there's never any harm in
checking the Release Notes for the correct command, and the man page
for what that does. I had mentioned aptitude in a previous post here,
and that does have incompatible command names, and ISTR side effects
as well, such as cleaning the cache.

Cheers,
David.

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

#240954

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

On Ma, 05 oct 21, 10:48:03, Kenneth Parker wrote:
> On Tue, Oct 5, 2021, 9:04 AM David Wright <deblis@lionunicorn.co.uk> wrote:
> 
> > Yes, apt-get was recommended for upgrading to stretch. Note however
> > that if you perform your next upgrades with apt, as recommended,
> > some of the command names (like dist-upgrade) will differ in apt.
> >
> 
> I thought "dist-upgrade" is used to upgrade packages that need a "version
> change" (like, sometimes the Kernel).  Is this recent (i.e. Stretch?)

With `apt-get`, yes. With `apt` just `upgrade` is sufficient as well as 
safer, because it allows installation of new packages, but not removals.

It's also shorter to type ;)

See apt-get(8) and apt(8) for details.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#240922

On Tuesday 05 October 2021 09:04:03 am David Wright wrote:
> > > So the main things to confirm as working are the specific points mentioned in the respective Release Notes. In stretch that would
> > > be, for example, the 4.9 kernel is finding everything, 
> > 
> > About the only issue that I've noticed after this stuff all getting fixed is that there's something up with the sound.  Given the details of what advice I saw someone else getting,  I have a few things to look at.  The virtualbox OS complained about it too.  :-)
> 
> I can't see the point unless you depend on, say, a screen reader to be
> able to move forward at all. 

Youtube videos,  for one example?  I did get some sound going,  fired up kmix and found that the one slider was turned all the way down for some reason.  That gets me sound in the main OS,  but there still appears to be some kind of issue in virtualbox.  I'll work it out...

> After all, how long are you intending to run stretch for?

I'm not sure just yet,  after all of that I'm no exactly in a big hurry to move forward.
 
> > > that X may be running as a user (rather than root) on the console it's started from, 
> > 
> > I'm not sure I see the concern here.
> 
> An issue that caught some people out was finding the X server log,
> as it had to move out of /var/log/ (users don't have permission),
> and into a "hidden" directory, ~/.local/share/xorg/. Running
> root-owned applications is different, and you can get permissions
> problems with opening devices. Unusual though.

I just looked,  and that's not a problem here.
 
(snip)

> > So we'll see how it goes from here.  My upgrade path for this step went like this:
> > 
> > apt-get autoremove
> > edit the sources.list file replacing jessie with stretch
> > apt-get update
> > apt-get upgrade
> > apt-get dist-upgrade
> > 
> > And then reboot,  and see how well things work.  Or maybe reboot a couple of times...
> 
> Yes, apt-get was recommended for upgrading to stretch. Note however that if you perform your next upgrades with apt, as recommended,
> some of the command names (like dist-upgrade) will differ in apt.
 
I guess I'll have to pay attention to the release notes on that stuff...

There's just one other issue I'm not sure of the best way to deal with it.  Some time back the monitor that I was using died,  and when I replaced it with one of a similar size,  the new one had a higher resolution.  Which was not a problem as long as the software was feeding it a lower resolution.  But apparently somewhere in the upgrade process it decided to change this,  and as a result a lot of stuff got *tiny*.  I was able to change font sizes in a number of places,  and icon sizes in my taskbar,  but not in the one in virtualbox,  and this old kmail that I'm running (by preference) is only giving me the choice of changing it in some places.  The composter not being one of them.  Unread msgs being another one.  My recollection of other software was that you could,  say,  right-click on the desktop and get a choice of changing your screen resolution to something else.  I'm not seeing that here.  I'm sure that there's someplace to fiddle with that setting,  I just haven't found it yet.

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

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

#240929

On Tue 05 Oct 2021 at 10:55:36 (-0400), Roy J. Tellason, Sr. wrote:
> On Tuesday 05 October 2021 09:04:03 am David Wright wrote:
> > > > So the main things to confirm as working are the specific points mentioned in the respective Release Notes. In stretch that would
> > > > be, for example, the 4.9 kernel is finding everything, 
> > > 
> > > About the only issue that I've noticed after this stuff all getting fixed is that there's something up with the sound.  Given the details of what advice I saw someone else getting,  I have a few things to look at.  The virtualbox OS complained about it too.  :-)
> > 
> > I can't see the point unless you depend on, say, a screen reader to be
> > able to move forward at all. 
> 
> Youtube videos,  for one example?  I did get some sound going,  fired up kmix and found that the one slider was turned all the way down for some reason.  That gets me sound in the main OS,  but there still appears to be some kind of issue in virtualbox.  I'll work it out...
> 
> > After all, how long are you intending to run stretch for?
> 
> I'm not sure just yet,  after all of that I'm no exactly in a big hurry to move forward.

Fair enough. I'm among those who feel that you could be tripling your
workload by configuring every application in each of the Debian
revisions. But at least you'll get better support each time.

> There's just one other issue I'm not sure of the best way to deal with it.  Some time back the monitor that I was using died,  and when I replaced it with one of a similar size,  the new one had a higher resolution.  Which was not a problem as long as the software was feeding it a lower resolution.  But apparently somewhere in the upgrade process it decided to change this,  and as a result a lot of stuff got *tiny*.  I was able to change font sizes in a number of places,  and icon sizes in my taskbar,  but not in the one in virtualbox,  and this old kmail that I'm running (by preference) is only giving me the choice of changing it in some places.  The composter not being one of them.  Unread msgs being another one.  My recollection of other software was that you could,  say,  right-click on the desktop and get a choice of changing your screen resolution to something else.  I'm not seeing that here.  I'm sure that there's someplace to fiddle with that setting,  I just haven't found it yet.

Yes, again, my own opinion would be to fix that once, in bullseye.
I don't use a DE, only a WM, but the impression I get from the list
is that how you make changes is itself always changing.

Cheers,
David.

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

#240882

On Sunday 03 October 2021 07:48:38 pm Patrick Bartek wrote:
> On Sun, 3 Oct 2021 12:49:12 -0400
> "Roy J. Tellason, Sr." <roy@rtellason.com> wrote:
> > > Also, read and follow the Release Notes of dist-upgrade for each
> > > version.  
> > 
> > Where are these to be found?
> 
> https://www.debian.org/releases/jessie/releasenotes
> https://www.debian.org/releases/stretch/releasenotes
> https://www.debian.org/releases/buster/releasenotes
> https://www.debian.org/releases/stable/releasenotes (Bullseye)

Okay,  looking the first one over it's not particularly pertinent since I'm not upgrading to jessie,  but away from it.  Looking over the next one,   lots of stuff in there amd I can see where some of it doesn't apply to my situation here but out of the rest of it I'm not sure just what _does_ apply.  I haven't looked over the last two yet, figuring that I'm not there yet and will worry about that a bit later...
 
> Here's the main document page:
> 
> https://www.debian.org/doc/

Noted.
 
> > > Reboot after each version upgrade, then do an apt-get update/upgrade, etc.  
> > 
> > Are you suggesting that I go through that for all of the versions, one after another?
> 
> Yes.  You want to make sure that each version is fully up to date BEFORE dist-upgrading to the next.

How specifically do I do that?

> Also, check that the repo sources list is correct for each version.

I'm assuming that you refer to /etc/apt/sources.list?  At the beginning of this process I edited it changing references to jessie to refer to stretch.  I apparently messed up with not including the line to read the DVD,  so I ended up downloading a *lot* of stuff that I already had on hand here.  One thing that I found curious is that I saw the system also downloading some i386 packages,  and am not sure why it did that since I'm only expecting to need the amd64 packages.  I suppose I could find these and delete them to free up some disk space,  but space isn't that much of a problem on the system in question at the moment.  I appear to have in excess of 150GB free space at the moment...
 
> > > > For some reason,  the software decided to remove virtualbox.
> > > > Which is a real problem,  because it's inside a virtual machine
> > > > that I do all of my mail,  so I couldn't get at my mail for a
> > > > while.  In Synaptic Package Manager if I try to install it I get
> > > > the following error message:
> > > > 
> > > > "Package virtualbox has no available version, but exists in the
> > > > database.  This typically means that the package was mentioned in
> > > > a dependency and never uploaded,  has been obsoleted or is not
> > > > available with the contents of sources.list"
> > > > 
> > > > I got temporarily past this by installing 8 on this laptop I'm
> > > > currently typimg on.  Some things are decidedly less convenient.  
> > > 
> > > Complete the dist-upgrade for all versions, then reinstall
> > > VirtualBox. Be sure you saved all your VMs before the
> > > dist-upgrade(s).  They may be deleted.
> > 
> > Yes,  I did save them and will do so again before I proceed,  since
> > I'm modifying this one as I type here... 

Still...

> > > I don't use the VB version in the Debian repos, but download and
> > > install the .deb directly from their web site.  During the install
> > > the VB repo will be set up.  
> > 
> > I did do a download from their site.  But it's not clear to me where
> > I need to put it and how to tell the package management software
> > about it.
> 
> Did you download the .deb file of it?  

Yes.

> You can use dpkg to install, but it won't automatically take care of dependencies.  I use gdebi-core, a
> command line utility, that will install the .deb file correctly and
> install any dependencies. You must be root to install.

Is that another package that I should install?

> > > > Firefox is majorly different,  apparently having gone from 68.9.0
> > > > --> 78.14.0esr.  It no longer uses the font that I'm telling it
> > > > to,  and for some odd reason won't play any youtube videos any
> > > > more.  Instead I see a message on the screen that says "if video
> > > > doesn't start momentarily restart your device".  Huh?
> > > > 
> > > > Konqueror is also broken,  I get "Could not start proess Unable to
> > > > create io-slave: klauncher said: Error loading 'kio_file'"...
> > > > 
> > > > Trying to open a file with Okular gets me a similar message.  
> > > 
> > > Complete the entire dist-upgrade before trying to fix problems.
> > > The problems may fix themselves.  
> > 
> > For all of the versions,  straight through to 11?
> 
> More or less.  Check the repos are the correct for that version,
> Update/upgrade, then reboot. The Release Notes gives full
> instructions.

In addition to the release notes,  I have tabs open in firefox detailing the upgrade from each version to the next,  and that's what I was using to do what I've done so far...
  
> > > > I don't see any way to back out of these changes,  or any obvious
> > > > place to look for where the problems are.  Suggestions welcomed.  
> > > 
> > > I avoid dist-upgrading, if I can because of such problems, and do a
> > > clean install of the newest version on a free partition keeping the
> > > old install as fallback in case something goes awry.  
> > 
> > I have done similar in the passt,  with Slackware.  Which isually
> > involves stickinng another hard drive in the machine.  I don't have
> > one handy at present,  though,  and probably won't be getting one in
> > the near-term.
> 
> You really only need enough free space on a single drive to install
> the new version.  I share the swap partition to conserve space. So, I
> only need / and /home partitions for the new install. Some share
> the /home partition, too, but I never have. The installer should take
> care of setting up dual or multibooting as required.

Okay,  now it sounds like you're talking about setting up another partition and doing a fresh install to that.  Which isn't what I did,  and I don't particularly plan to on that machine.  I've already done the one upgrade here,  it's somewhat broken,  though partially functional,  and I'd much rather spend my energies to fix that,  rather than going that route...

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

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

#240898

On Mon, 4 Oct 2021 14:49:10 -0400
"Roy J. Tellason, Sr." <roy@rtellason.com> wrote:

> On Sunday 03 October 2021 07:48:38 pm Patrick Bartek wrote:
> > On Sun, 3 Oct 2021 12:49:12 -0400
> > "Roy J. Tellason, Sr." <roy@rtellason.com> wrote:  
>
>[snip]
>  
> > > > Reboot after each version upgrade, then do an apt-get
> > > > update/upgrade, etc.    
> > > 
> > > Are you suggesting that I go through that for all of the
> > > versions, one after another?  
> > 
> > Yes.  You want to make sure that each version is fully up to date
> > BEFORE dist-upgrading to the next.  
> 
> How specifically do I do that?

Make sure your repo list in /etc/apt/ is correctly configured for
the version you just dist-upgraded to, then as root apt update ... apt
upgrade (NOT dist-upgrade).  That should do it.
 
> > Also, check that the repo sources list is correct for each
> > version.  
> 
> I'm assuming that you refer to /etc/apt/sources.list?  At the

Yes. Also check /etc/apt/sources.list.d for anything just in case.

> [snip]
> 
> > You can use dpkg to install, but it won't automatically take care
> > of dependencies.  I use gdebi-core, a command line utility, that
> > will install the .deb file correctly and install any dependencies.
> > You must be root to install.  
> 
> Is that another package that I should install?

It isn't installed as part of the OS. So, yes. However, if you don't
want to, use dpkg to install and apt-get -f to resolve the dependencies.

> > > > > [snip]
> > > 
> > > I have done similar in the passt,  with Slackware.  Which isually
> > > involves stickinng another hard drive in the machine.  I don't
> > > have one handy at present,  though,  and probably won't be
> > > getting one in the near-term.  
> > 
> > You really only need enough free space on a single drive to install
> > the new version.  I share the swap partition to conserve space. So,
> > I only need / and /home partitions for the new install. Some share
> > the /home partition, too, but I never have. The installer should
> > take care of setting up dual or multibooting as required.  
> 
> Okay,  now it sounds like you're talking about setting up another
> partition and doing a fresh install to that.  Which isn't what I
> did,  and I don't particularly plan to on that machine.  I've already
> done the one upgrade here,  it's somewhat broken,  though partially
> functional,  and I'd much rather spend my energies to fix that,
> rather than going that route...

I am. That's what I do.  I avoid dist-upgrading as I usually use
the OS until Long Term Support ends ... about 5 years, which is about
2 release versions. Saves a lot of time and headaches. In your case, it
would be the easiest, less problematical way to go since your first
dist-upgrade is partially broken. Just install Bullseye as a new
install, install what apps you need, copy over your data ... Done.

B

[toc] | [prev] | [standalone]

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

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

csiph-web