On Thursday 27 of August 2020 17:52:16 Slávek Banko wrote: > On Thursday 27 of August 2020 17:13:46 William Morder via trinity-users > > wrote: > > On Thursday 27 August 2020 08:05:17 Slávek Banko wrote: > > > On Thursday 27 of August 2020 16:40:40 William Morder via > > > trinity-users > > > > > > wrote: > > > > 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"; > > > Acquire::http::No-Cache=True; > > > Acquire::BrokenProxy=true; > > > > > > Cheers > > > > Ordinarily I would always use a proxy -- and have no problems at all > > -- but tork-trinity, tor, etc., are some of the packages that will not > > download. > > > > The packages are listed when I do apt-cache search, etc., but then > > when I tried to download, it would ask for dependencies that seemed > > like they were for Bullseye. So then I tried using Sid, Bullseye, > > unstable, etc., but finally went back to vanilla Devuan Beowulf, and > > Buster for the Trinity repositories. When I ran Jessie, I would always > > use your PSB repo, and now I also have tried PTB repo, but it kept > > saying I needed 11.0 Buster packages. So I went back to the Trinity > > ppa repo (I believe it's Tim's or a mirror thereof), along with > > vanilla Devuan (pkgmaster, etc.), and then I played with dpkg and > > apt-get as already described. > > > > Now it's working, but I still have problems finding or downloading > > packages, even though I see them listed. > > > > Bill > > I remember seeing package availability issues when I wanted to prepare > build-root for Devuan Chimaera. There were exclusively Devuan apt > sources and for me it seemed that there was some broken state of the > merge process of the Debian + Devuan packages on Devuan side. I didn't > try to examine it in more detail - I didn't want to waste time - and I > put it off until later. > > Cheers Now I took a closer look at the problem on my builder and found that this is not a problem on the Devuan side. On the builder I use squid-deb-proxy and there are listed servers from which the download of packages is allowed. Devuan uses the Debian redirector for Debian packages, as a result there are attempts to download packages from servers that are not allowed in the squid-deb-proxy. That's why it doesn't work properly on my builder. So this is a different problem than you observe. Cheers -- Slávek
Attachment:
signature.asc
Description: This is a digitally signed message part.
