Three years later, this bug still exists. It looks as though the problem could be solved by giving changelogs.ubuntu.com an IPv6 address, so the meta-release file could be accessed by a v6-only host. Surely that's a straightforward enough change that it shouldn't take years to implement.
Three years later, this bug still exists. It looks as though the problem could be solved by giving changelogs. ubuntu. com an IPv6 address, so the meta-release file could be accessed by a v6-only host. Surely that's a straightforward enough change that it shouldn't take years to implement.