[Bug 1740114] Re: apt-get update hangs forever trying to fetch data via a non-working IPv6 connection
David Kalnischkies
1740114 at bugs.launchpad.net
Tue Dec 26 20:00:44 UTC 2017
Thanks for your well written bugreport and a very happy Christmas to
you, too, sir. Please proceed to the checkout counter and accept a full
refund and our sincere apologizes.
Unfortunately, I am neither a ubuntu developer, nor do I drink kool-aid
apart from the seasonal appropriate hot cocoa, but as an APT developer
who is paid splendidly by the many thanks of people like you for
investing his freetime it feels like my obligation to pay back some
times:
Its not our fault that you misconfigured your system and throw money out
the window. APT wouldn't be using IPv6 if your system wouldn't say that
it is available. Talk to your ISP: You pay them a lot for your router
and network usage presumably. Enough to make non-broken IPv6 available
to you – you will need it sooner than later.
APT also performs fallbacks – not quickly, we are working on that, but
it eventually does: Too quick and naive a fallback and we break for
systems which have high latency, but otherwise working configuration.
So, as this "bugreport" adds exactly nothing to improve the situation
expect perhaps "helping" that I and other volunteers are never going to
look at bugs written by "fucking insane morons" I am closing as
"opinion" for fucks sake.
P.S.: apt isn't launchpad either. These guys likely wouldn't appreciate
the nice ton of your message either, through.
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1740114
Title:
apt-get update hangs forever trying to fetch data via a non-working
IPv6 connection
Status in apt package in Ubuntu:
Opinion
Bug description:
I kindly request that Ubuntu developers stop drinking so much Kool-Aid
and realize not everyone in this world has a working IPv6 connection
and an IPv4 fallback must be used in case an IPv6 request takes too
much time:
# time apt-get update
Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
0% [Connecting to security.ubuntu.com (2001:67c:1560:8001::11)]^C
real 6m10.351s
user 0m0.056s
sys 0m0.020s
What the fuck??? My server doesn't have a working IPv6 connection. The
apt-get update command apparently never completes. Could there be a
sane timeout before apt switches to IPv4?
Why the Internet is full of requests how to disable IPv6 support in
apt when it takes a few seconds to fix this problem in the first
place?
Why the fuck there are such crucial bugs in the first place? Could you
for fuck's sake make your software usable and bugs-free before trying
to add a ton of barely working new shiny features?
Of course, there's this nice thread
https://unix.stackexchange.com/questions/9940/convince-apt-get-not-to-
use-ipv6-method
which fixes this issue, but why the fuck am I supposed to start
googling from the get go after installing a brand new release of
Ubuntu
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
Also why the fuck are you sending a password reset URL which uses
plain HTTP? Are you fucking insane?
What the fuck is this shit?
http://login.launchpad.net/token/xxxxxxxxxxxxxxxxxxxxxxxxx/+resetpassword/example@example.com
What the fuck is wrong with you people?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1740114/+subscriptions
More information about the foundations-bugs
mailing list