Timeline for Failed to fetch Trusty binary-i386/Packages 404 Not Found [IP: 138.201.14.197 80]
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2019 at 16:22 | comment | added | JohnBR | @DJCrashdummy and yes, the update is inevitable (as borgs saying: "resistance is futile"), but I am doing tests on my laptop (with a new SSD) bionic beaver (18.04.1), most is OK, "snap" is a "snap" but uses many resources (with SSD we again have to plan storage space) worst is having to get back to gnome GUI, mouse and key shortcuts....takes time, and patience, not to mention systemctl. | |
| Feb 8, 2019 at 16:16 | comment | added | JohnBR | @DJCrashdummy my tests here indicate several possibilities (like you have already noted too), but yesterday the self update of the tor app did update (ie. pop-up showing update available, I agreed, download progress completed and update did finish). But as SEdude noted the ppa/repository still is missing. | |
| Feb 6, 2019 at 10:37 | comment | added | DJCrashdummy |
@JohnBR well... the error is not on your side. - your options are either reach somehow out to the tor-project, report that trusty builds are missing and wait/hope for the builds, or (which is the more sustained solution) consider an upgrade to (at least) xenial because trusty support is running out anyway in 2 months (april 2019).
|
|
| Feb 5, 2019 at 22:02 | comment | added | JohnBR | I still do not know if this is caused by a manual install, instead for a ubuntu repository installation. Or a repository failure when I was updating my system. I am still checking. | |
| Feb 4, 2019 at 6:05 | review | First posts | |||
| Feb 18, 2019 at 6:05 | |||||
| Feb 4, 2019 at 6:03 | history | answered | SEdude | CC BY-SA 4.0 |