Re: Solved, maybe (was: Re: Help updating a Jessie installation to Jessie LTS)
On Sun 31 Mar 2019 at 16:35:44 (-0400), rhkramer@gmail.com wrote:
> On Saturday, March 30, 2019 04:12:05 PM rh kramer wrote:
> > I already made an attempt, and I'm a little worried that I may have messed
> > things up -- I'd like to try to recover and get back to a reliable Jessie
> > system.
Saw your post too late to help much.
> Things might be OK. Things I did:
>
> * googled for errorackage -- found some pages but not much help -- some
> pages gave long lists of instructions to try, but it sounded more like a
> shotgun approach than any real knowledge based thing. Some people thought it
> meant a hardware bus error, some thought some kind of memory problem (hardware
> or not), others just suggested commands to try -- maybe there is a better page
> out there that I didn't find
I hit this bizarre page that has a comparable multitude of possibilities.
https://stackoverflow.com/questions/212466/what-is-a-bus-error
> * Aside: what the heck does errorackage mean / stand for and what is it
> telling me? Who came up with that "word"?
In school arithmetical notation:
Reading package lists... 89% +
Bus error
----------------------------
Bus errorackage lists... 89%
----===========-------------
> * I edited sources.list to get rid of the jessie-updates (I don't think
> that did anything significant with respect to the errorackage error)
>
> * I did a df and found /boot and /var close to full, I examined /var
> expecting to find a lot of space used for the apt archives, but instead there
> was a bunch of stuff (in /var/tmp as opposed to /var/cache/apt/archives)
> related to mkinit... (I'm writing from a different computer, so I couldn't copy
> and paste) -- something like over 1.5 GB -- deleted all that, then did:
Yes, that's one of the options in that page, but the link to the
report is broken:
for me the partition containing /var/cache was simply full
https://askubuntu.com/a/915520/493379
> apt-get update
>
> apt-get upgrade
>
> That seemed to work pretty well, I mean, it seemed to install everything
> except the new linux kernel which was held back.
>
> tried:
>
> apt-get dist-upgrade
>
> Found a message in there that said a partition / filesystem was out of space --
> /var looked ok, so cleared out some space in /boot by deleting an old kernel
> (something like n.n.n -04)
>
> tried
>
> apt-get dist-upgrade
>
> This time saw a message that it didn't work and suggested that I try apt-get
> -f install <and then, presumably, a packagename>
>
> instead, I tried
>
> apt-get -f dist-upgrade
>
> That seemed to work, so things may be ok -- I guess I'll have to watch the
> system for a while and think about rebooting (to put the new kernel in
> service).
> > What I did and why:
> >
> > I understood from some other posts on the list that the mirrored
> > repositories for Wheezy and Jessie went away in early March, so (for
> > Jessie) I found a post that told me what the content of
> > /etc/apt/sources.list should be for Jessie LTS.
Yes, on my two legacy jessie systems, I cut sources.list down to:
# this was wheezy and was upgraded to jessie
#deb cdrom:[Debian GNU/Linux 7.1.0 _Wheezy_ - Official i386 NETINST Binary-1 20130615-21:53]/ wheezy main
deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
I figured that sources were of no use to me.
I also took out all the backports packages because, for example,
I no longer do video manipulation with ffmpeg on these machines.
After finding which packages with apt-show-versions, I reinstalled
them with
# apt-get -s -o Acquire::http::Proxy="http://192.168.1.17:3142/"; install foo=1.2.3
using the -s option at first to make sure I grouped their removal
where necessary.
So now my jessie systems are clean apart from xtoolwait from squeeze
and fonts-hack-ttf from stretch, both with no dependencies.
> > Oh, an extra credit question: are there mirrors I can use for Jessie LTS or
> > must I use debian.org? If there are mirrors I can use, where would I find
> > those?
ftp.us.debian.org has always worked for me (eg wheezy until late last year).
Cheers,
David.
Reply to: