[09:38] ravage: the end of the topic explains what is meant by the beginning, I hope. [10:01] still says RT [10:01] but at least it mentions an email :) [10:03] Yes, it explains what we mean by "use RT". [14:23] hello - may I ask for an assist on an updated resource for how to create your own repository? not exactly a mirror but thought I'd ask [17:02] hello, "tr.archive.ubuntu.com" is extremely and painfully slow. even directory listing is taking more than 50 seconds. is it possible you to change A records of that mirror to point archive.ubuntu.com? [17:02] $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' http://tr.archive.ubuntu.com [17:02] Total: 101.663106s [17:06] mert: i'm just another user but i can already tell you that your report is appreciated but you'll need to send it to the email address given in the channel /topic [17:07] thank you tomreyn, i'll do it. [17:08] 👍 [17:27] bG9s, 'reprepro' (package) could help you. [17:27] neat ty ty [17:27] will check here shortly [17:27] Fluor: ty [17:31] bG9s, for a more manual/dirty solution, look into dpkg-scanpackages / dpkg-scansources [17:32] manual is nice, just now taking a loowk [17:51] i'm told that others have seen mirror issues? I came looking after my caching-proxy mirror (which i dont really have access to logs for) had a client fail with: https://pastebin.mozilla.org/URqu6kVL/raw [17:51] apt would normally use by-hash, but i think the following line indicates taht didn't work and it fell back: [17:51] Failed to fetch http://my-mirror/path/ubuntu/dists/focal-updates/main/binary-amd64/Packages.xz Hash Sum mismatch [18:02] i've seen recent reports about what looked like tcp timeout issues with TR and US.archive.ubuntu.com, not hash sum mismatches [18:02] smoser: ^ [18:03] of course those could be due to your local mirror failing to get updates from the origin [18:07] https://launchpad.net/ubuntu/+archivemirrors appears to be mostly good on the first look, https://status.canonical.com/ also [18:08] right, my caching-proxy mirror could have had an issue with its GET and that manifested this way. [18:09] and this woudl be the first time i've ever had an issue other than "Hashsum mismatch" with official mirrors, so absotlutely it could have been our link. [18:10] thanks. [19:37] hello all, yes sorry we've had a weird outage on our archive servers but things should be back in shape now [20:25] thanks, axino . the result of this is better for me anyway, now i have 'by-hash=force' which i previously didn't kniow about.