Control: merge 1033200 1033208 1033209 Hi,
On Sun, Mar 19, 2023 at 11:19:23AM -0400, WILLIAM ORVILLE RICHMOND wrote: > Package: apt-get > Version: 2.2.4 > Subject: This info seems to have inadvertently been omitted from the > Debian Bug report logs The package is called "apt", a package named "apt-get" doesn't exist, so the bugs were assigned to a catch-all package – from there it got assigned now to where you probably intended to report it against in the first place… Just, please don't make every of your mails a new bugreport. You can add a message by replying to 1033...@bugs.debian.org (or just reply-all to this message here). Thanks. > When, for example, I do: > > orville@flinta:~$ sudo apt-get install lynx […] > Ign:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all > 2.9.0dev.6-3~deb11u1 > Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all > 2.9.0dev.6-3~deb11u1 > Connection failed [IP: 199.232.34.132 80] […] > E: Failed to fetch > http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb > Connection failed [IP: 199.232.34.132 80] The IP belongs to Fastly, a big CDN, sponsoring Debian. Can you reach the IP in a browser, e.g. with "http://199.232.34.132/";? (It is normal if the page you see isn't very informative and just talks about "Fastly error: unknown domain". Not normal would be an error message from your browser about being unable to connect or some such.) > I have been considering that maybe some part of the update process, (curl > ??), has been being intercepted ... perhaps by my ISP?? ... but I don't curl is not part of the "update process". Sure, 'something' could potentially interfere with your network, but while a real attack could look the same, it is usually just some local misconfiguration and not some sinister plot by your ISP or country (if you don't happen to live in a sinister country of course). Have you e.g. recently changed something in your router configuration? Is your machine connected to the right wlan network? Sometimes, these issues turn out to be just some new neighbor with an open wlan… Or do you have a proxy configuration? Adblocker? A open hotspot near by with a captive portal? … You can change the apt sources.list to use 'https' instead of 'http' to potentially avoid some problems with external interference (although, some interference is considered good interference, so this isn't a default in Debian for now). A VPN would indeed eliminate far more of potential external interference, but for now that seems like overkill. > It has seemed to be to be unlikely that I am the only person with these > problems, however I do apologize for waiting so long, As the world isn't burning (well, it is given climate and wars, but I digress) it is actually very likely that you are the only person with these problems as we would have literal thousands of people reporting such issues, especially if they were ongoing for months, while we are even in the process of releasing a new major version of Debian and so many people interact with our servers for upgrades. In fact, between 16 and 17 March the mail reception of the BTS and a couple other things went down for a few hours only, and the outcry was huge [0]. Problems for "months" is nearly 100% proof that this problem is local to your setup. I somewhat suspect that the reason Fedora isn't effected is simple that the configuration you accidentally broke network reaching tools on Debian with hasn't reached your Fedora setup yet, so I would start with figuring out what makes your Fedora machines different from the Debian ones. Are they in a different (sub)net on your network for example? All in all, I don't really see a way to help you as I don't really see how it could be a problem originating from "apt". Especially if you have similar network problems with other tools. Best regards David Kalnischkies [0] https://lists.debian.org/debian-infrastructure-announce/2023/03/msg00003.html
signature.asc
Description: PGP signature
