Hello Robert, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in apt source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: New Bug description: [Impact] APT takes a long time to notice when certain connections time out [Test case] * Change the default route to not route stuff successfully (wrong gateway, for example) * Make your sources.list look like this: deb http://archive.ubuntu.com/ubuntu bionic main restricted deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted * Run apt update You should see that it fails with a long verbose error message for the first entry, with all possible IP addresses listed in it; while for the second one it fails with just "Unable to connect to archive.ubuntu.com:http:" as it recognizes it has been blacklisted. [Regression potential] APT will not attempt to retry the host given that it could not connect to it for previous entries. If your network recovered in the meantime, it might update less than previously. [Original bug report] When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
