Message: previous - next
Month: August 2020

Re: [trinity-users] questions about upgrade to Beowulf/Buster - correction

From: Slávek Banko <slavek.banko@...>
Date: Thu, 27 Aug 2020 17:05:17 +0200
On Thursday 27 of August 2020 16:40:40 William Morder via trinity-users 
> Okay guys, so I am stumped and confuzzled.
> I just did an upgrade to Devuan Beowulf (= Debian Buster), and
> everything went fine; except once up and running, I couldn't download
> more than a few of Trinity's packages.
> After trying different repositories, and playing with my sources list, I
> managed to do just a bit better, then I saved the day with some extreme
> voodoo using about config [*I meant to say, apt-get* ... writing on
> auto-pilot] (scrolling through the manpages to find something
> that work). I ended up getting enough the Trinity packages to download
> by using --ignore-hold and dselect-upgrade options. I even searched out
> the links to deb packages on the developers' repositories, and
> downloaded them with wget, so that I could try forcing install using
> dpkg.
> Now at least (at last) I do have a working system which is a reasonable
> facsimile of my previous one, but it does seem like it ought to have
> been easier. For about the past three days now, I've lived in the
> command-line.
> Also I would like recommendations for a firewall that displays active
> connections and rules, etc., like the old Firestarter used to do. I
> catch all kinds of problems by noticing activity on my firewall, but now
> I cannot seem to find one that displays active connections, and
> Firestarter can no longer be hacked to make it work on a newer system.
> Thanks for any advice or comments,
> Bill

Hi Bill,

what problems do you observe? Do packages report incorrect size / checksum 
after download? Or do you get a 404 response? Or something else?

Lately, I've been seeing more often that probably due to a malfunctioning 
transparent proxy somewhere at the provider, I'm getting corrupted and apt 
lists or damaged packages. And I have to download them repeatedly and 
repeatedly and... For such cases, it usually helps me to set up apt to 
know that the broken proxy is in the way:

Acquire::http::Pipeline-Depth "0";