[Bug 1740114] Re: apt's IPv4 fallback in case of a malfunctioning IPv6 connection works horribly

T-artem 1740114 at bugs.launchpad.net
Tue Dec 26 21:31:12 UTC 2017


I've already worked around this problem, thank you very much.

Most end users are *not* IT pros to even understand what's wrong with
their systems: they rightfully presume that Ubuntu sucks/doesn't work on
their PCs not because it inherently sucks or it's unusable but because
you insist on the things which might not work as you believe they should
and everything goes tits up.

You see, guys, you all speak like lunatics:

I tell you that Ubuntu/Debian should not default to IPv6 ever - you say fix your systems.
I tell you that sane timeouts should be introduced - you say fix your systems.
I tell you that you're breaking various RFCs by having insane defaults - you say fix your systems.

I've even given you a perfect reproducible bug report: run Ubuntu on a
system which has an IPv6 address but lacks a an IPv6 route and you still
insist that the world should bend over for you. It will not. A sane OS
should not assume anything.

Your ends users must not lose their shit over the things you decided for
them and for the entire world.

And while we're arguing you still actively choose to neglect the
stackexchange topic which clearly indicates that you're doing something
wrong for a *ton* of your users.

Please don't bother any more. Your attitude towards making Ubuntu (and
Debian, since I'm perfectly sure this bug applies to Debian as well)
usable in real world use cases is perfectly clear - you don't give a
flying f-word. You'll resort to blaming the user, the world, the
position of the stars above one's head but you won't admit that
something might not be suitable for common use cases your users are
facing every freaking day.

This bug report according to you is invalid. So be it. Let Ubuntu users
google. After all it won't be a true Linux distro without a lot of
tinkering.

Amen.

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



More information about the foundations-bugs mailing list