Not sure what caused this weirdness, but I thought it best to make a report, just in case it actually matters.
I was trying to find a desktop calculator that I actually like, and among those that I downloaded was kcalc-trinity, which I've used before. But when I downloaded my list of packages and dependencies, I kept getting an error message:
Err:1 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-testing chimaera/main amd64 kcalc-trinity amd64 4:14.1.0~s244-0debian11.0.0+12 404 Not Found [IP: 37.205.10.16 80] E: Failed to fetch http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-testing/pool/main/t... 404 Not Found [IP: 37.205.10.16 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
After trying apt-get build-dep, and then apt-get update, which did not improve my results, it occurred to me to try changing my sources.list from Devuan Chimaera to Debian Bullseye; and presto! worked like a charm.
Some may recall an earlier discussion (when Leslie was attempting a new Devuan installation), I posited my opinion that there is probably no difference between these packages when it comes to third-party repositories (such as Trinity itself). From what I can tell, third-party developers thus far do not create special Devuan packages, and most do not even acknowledge the existence of Devuan, so Debian packages work just fine.
For the Trinity repositories, I assume that the link to Chimaera packages is just a redirect to the Debian packages. Otherwise, this would be a reduplication of effort and server space, If this is wrong, I expect to be corrected by somebody who knows better. However, this seems like proof of concept, since the package was available by changing to the Debian links.
I do know that Debian and Devuan packages definitely should not be used interchangeably. When Devuan was first forked, this was almost true, except for a few systemd-dependent items, but now they have diverged more and more. These changes do not appear to have prompted third-party developers to create packages specifically for Devuan, but I am sure that this will be changing.
It could be that this package alone is missing, or that there is a problem with the link to this server, or that redirection is failing, or whatever. But I did try several times, with the same bad result, and after changing the lines in my sources.list for the Trinity repositories, everything worked like normal.
By the way, I am using the PTB repositories now, following Slavek's recent recommendation.
Bill
Dne po 21. listopadu 2022 10:47:27 William Morder via tde-users napsal(a):
Not sure what caused this weirdness, but I thought it best to make a report, just in case it actually matters.
I was trying to find a desktop calculator that I actually like, and among those that I downloaded was kcalc-trinity, which I've used before. But when I downloaded my list of packages and dependencies, I kept getting an error message:
Err:1 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-testing chimaera/main amd64 kcalc-trinity amd64 4:14.1.0~s244-0debian11.0.0+12 404 Not Found [IP: 37.205.10.16 80] E: Failed to fetch http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-testing/pool/ma in/t/tdeutils-trinity/kcalc-trinity_14.1.0%7es244-0debian11.0.0%2b12_amd6 4.deb 404 Not Found [IP: 37.205.10.16 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
After trying apt-get build-dep, and then apt-get update, which did not improve my results, it occurred to me to try changing my sources.list from Devuan Chimaera to Debian Bullseye; and presto! worked like a charm.
Some may recall an earlier discussion (when Leslie was attempting a new Devuan installation), I posited my opinion that there is probably no difference between these packages when it comes to third-party repositories (such as Trinity itself). From what I can tell, third-party developers thus far do not create special Devuan packages, and most do not even acknowledge the existence of Devuan, so Debian packages work just fine.
For the Trinity repositories, I assume that the link to Chimaera packages is just a redirect to the Debian packages. Otherwise, this would be a reduplication of effort and server space, If this is wrong, I expect to be corrected by somebody who knows better. However, this seems like proof of concept, since the package was available by changing to the Debian links.
I do know that Debian and Devuan packages definitely should not be used interchangeably. When Devuan was first forked, this was almost true, except for a few systemd-dependent items, but now they have diverged more and more. These changes do not appear to have prompted third-party developers to create packages specifically for Devuan, but I am sure that this will be changing.
It could be that this package alone is missing, or that there is a problem with the link to this server, or that redirection is failing, or whatever. But I did try several times, with the same bad result, and after changing the lines in my sources.list for the Trinity repositories, everything worked like normal.
By the way, I am using the PTB repositories now, following Slavek's recent recommendation.
Bill
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
Cheers
On Monday 21 November 2022 07:26:58 Slávek Banko wrote:
Dne po 21. listopadu 2022 10:47:27 William Morder via tde-users napsal(a):
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
No, I did an apt-get update after the first failure, yhen again and again, and after changing my sources.list, yet another.
I did, however, resist doing a full upgrade, because I saw it would be very large. And it's true that I don't always upgrade with every release, as there is not always time.
As a general rule, I try to make sure that my present configuration is updated and working before I do such a major upgrade (because it looked like practically everything, both TDE and pure Devuan packages, would be replaced). I keep all my downloaded packages, sorted into folders, etc., so that if something goes wrong, I can always return to my previous working version by using dpkg and downgrading. Also, whenever the internet goes down (which happens even here in San Francisco sometimes), I can still get a working machine.
On your suggestion, I will give it another go, see what happens. I did just save all my packages, so my present working system is good for my backup.
Thanks, Slavek!
Bill
On Monday 21 November 2022 07:26:58 Slávek Banko wrote:
Dne po 21. listopadu 2022 10:47:27 William Morder via tde-users napsal(a):
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
Cheers
P.S. My last full upgrade was 18 Sept 2022
Bill
On Monday 21 November 2022 07:26:58 Slávek Banko wrote:
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
Cheers
The continuing saga ...
I just now did an upgrade, which worked okay until I got this error:
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/f/firefox-esr/firefo... Error reading from server. Remote end closed connection [IP: 146.75.118.132 80] E: Failed to fetch http://ftp.fau.de/trinity/deb/trinity-testing/pool/main/t/tdebase-trinity/td... Connection timed out [IP: 131.188.12.211 80] E: Failed to fetch http://ftp.fau.de/trinity/deb/trinity-testing/pool/main/t/tdebase-trinity/td... Connection timed out [IP: 131.188.12.211 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Same kind of error, but different packages. Also I notice an attempt to download the firefox upgrade from a Debian server. But I don't have any Debian servers in my sources.list! Devuan only.
The only Debian packages will come from third-party repositories where the developers don't do Devuan. At present, TDE is my only third-party repository.
Bill
On Monday 21 November 2022 09:15:02 William Morder wrote:
On Monday 21 November 2022 07:26:58 Slávek Banko wrote:
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
Cheers
P.P.S.
Okay, so everything did eventually download without errors or changing anything. I don't know if it was that my connection here suddenly slowed down (when everybody else gets on the internet, during working hours), or if it was whatever server I'm downloading from.
In any case, I did get everything upgraded using the current PTB repositories, using the devuan chimaera lines in my sources.list. However, the download slowed to mere bits per second, not mb or kb, but b, so it took a long time.
Thanks again!
Bill
On Monday 21 November 2022 07:26:58 Slávek Banko wrote:
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
Cheers
So the apt-get update and upgrade went fine, or seemed to do, until I tried to install some other packages, then I got an error message about needing GLIBCXX. Turns out that is glibc++, and I don't know what happened.
Another thing I noticed during my recent upgrade, and again during this reinstallation: apt seems to try to connect to a Debian server, even though I have only Devuan repositories enabled. After a few seconds, it shows a Devuan server, and all appears to be okay again, but I am left wondering what that was about. Again, not sure if it's related to this issue.
This is why I resist doing upgrades sometimes. But I looked over my folders of saved packages (which I date and sort), and I find that I generally have done an upgrade about every month or two, so at least I am pretty regular.
When I did a fresh reinstallation of my system, I got a message that seemed like it might relate to that problem:
apt-listchanges glibc (2.31-13+deb11u4) bullseye; urgency=medium
I have not pasted the whole message, as I'm sure the developers are already familiar with it.
Well, so now I am back up and running.
Bill
Dne út 22. listopadu 2022 19:34:34 William Morder via tde-users napsal(a):
On Monday 21 November 2022 07:26:58 Slávek Banko wrote:
Hi Bill,
it looks like you haven't done an "apt update" in a while, because the version 14.1.0~s244 corresponds to the version from October 28th, while the current version is 14.1.0~s247 from November 18th.
So you can try to do "apt update" and install the packages afterwards.
Cheers
So the apt-get update and upgrade went fine, or seemed to do, until I tried to install some other packages, then I got an error message about needing GLIBCXX. Turns out that is glibc++, and I don't know what happened.
Another thing I noticed during my recent upgrade, and again during this reinstallation: apt seems to try to connect to a Debian server, even though I have only Devuan repositories enabled. After a few seconds, it shows a Devuan server, and all appears to be okay again, but I am left wondering what that was about. Again, not sure if it's related to this issue.
This is why I resist doing upgrades sometimes. But I looked over my folders of saved packages (which I date and sort), and I find that I generally have done an upgrade about every month or two, so at least I am pretty regular.
When I did a fresh reinstallation of my system, I got a message that seemed like it might relate to that problem:
apt-listchanges glibc (2.31-13+deb11u4) bullseye; urgency=medium
I have not pasted the whole message, as I'm sure the developers are already familiar with it.
Well, so now I am back up and running.
Bill
Hi Bill,
as far as I know, the Devuan sources are designed in such a way that it is a merger of the Debian repository together with a repository containing Devuan specific packages. See "merged" in apt source path.
Therefore, when downloading packages, unchanged packages from Debian are redirected directly to the Debian repository. This is why you can observe downloads from the Debian repository.
Cheers
-
Slávek Banko -
William Morder