© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
> All comments in the bug indicate one of the following:
> (a) bug in libc and fixed now
> (b) temporary network issues
> (c) misconfiguration
I'm not sure that my comment indicates one of those.
> At no point did any comment indicate a bug in APT. Unless you can show that
>
> sudo debootstrap natty natty; sudo chroot natty apt-get update
>
> (and then bisect for maverick, lucid) does not work, please do not comment further
> on this issue. Or try reproducing it with a chroot of your own release instead of natty
> and see if it works, thus ruling out (c).
This did not occur in natty (was it fixed there?)
This is also not an end user use case. I shouldn't have to chroot anything to recreate a bug.
> This bug turned into a network setup support channel, which is not the intention
> of bugs.
Oh I agree, and that is what is so frustrating trying to find a workaround or fix for this issue.
Almost every thread I find on this issue digresses into router configurations, DNS, NAT, etc etc which is not the issue here.
My network configuration is correct. The URLs apt complains about can be accessed as seen in my wget example above.
> I do not want to hear anything about clicking anything,
That's unfortunate.
I am trying to transition from an rpm based linux distribution to Ubuntu so I am unfamiliar with much of how apt works.
The workaround I posted above with UI steps for removing 3rd party repositories from apt was intended to help users affected with this same issue.
Based on your comments I will assume you are very familiar with the Ubuntu / synaptic / apt framework. You should then be able to understand what these use case steps through the UI do at a lower level to the apt configuration. And that might possibly help you to understand why removing 3rd party repositories through the UI steps I outline above would workaround the issues seen both through the GUI and through the apt CLI.
I posted here only hoping that it might help others experiencing the same issues with 3rd party repos and the misleading error messages indicating that apt cannot download from URLs (not from the 3rd party repos) which clearly can be resolved and accessed.
> whether $RANDOM
> programs work, or which networks are used.
> Unless someone serious can reproduce the bug in a clean natty environment, there is no bug.
I can appreciate that you feel I am not someone serious.
Still apt shouldn't choke because 3rd party repos make it unable to access the main Ubuntu repos, and subsequently complain with inaccurate error messages about the URLs it thinks it cannot access.