[Bug 1740114] Re: apt-get update hangs forever trying to fetch data via a non-working IPv6 connection

[T-artem]

> Its not our fault that you misconfigured your system and throw money
out the window.

That's what wrong with you, Mr. David. For some reasons you believe that
if a configured resolver returns an AAAA record and there's literally
any IPv6 address attached to the NIC, then surely IPv6 must be working.
Guess what? IPv6 requires a working IPv6 route (which is _not_ present
on our systems), it also requires a configured address which doesn't
start with the fe80 prefix (again, globally routable IPv6 addresses are
not present on our systems). I guess checking for these two
prerequisites is way too difficult and counter-intuitive for you
distinguished Debian/Ubuntu developers.

More importantly though is that implementing a fallback after a certain
timeout is way beyond your ego and your magical world of technology
where all people have magically received globally routable IPv6
addresses.

It's weird that some other Linux favours like Fedora implement fallbacks
after a certain timeout, and so do many other OSes like *BSD, Windows
and even Android.

However it's obvious that Debian and Ubuntu are above all of that and
implementing such pesky requests from users is just not worth your time.

> 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.

I would have believed that, sir, but a 20 to 30 minutes fallback (last
time I waited for more than 10 minutes) is certainly not something a
sane person would have ever thought of. I cannot think of any Internet
connection which might be usable beyond a standard 300 seconds IPv4
connection attempt timeout. Perhaps, though Debian/Ubuntu developers
believe networking standards don't apply to them.

I would have agreed to all your reasoning however the mentioned thread
at stackexchange dot com has literally hundreds of likes and hundreds of
thousands of views, which indicates that IPv6 is still not in a shape
where you should even *default* to it.

What makes you *default* to IPv6 in a world where there are countries
with zero connected IPv6 endpoints? What makes you *default* to IPv6 in
a world where there are hundreds of ISPs which don't provide IPv6
routing for their clients?

Why does my wonderful Ubuntu/Debian distro must be configured around the
things which must work out of the box? You strive to make Linux a first
class desktop OS, yet you do everything to make your potential users
endure as much pain and suffering as possible because ... you can?

-- 
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's IPv4 fallback in case of a malfunctioning IPv6 connection works
  horribly

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