Hello Graham, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.27 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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 Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Bug description: When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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
