If I remember correctly, in my case the problem was caused (a long time
ago already, maybe it is gone already) by nneeding to use a proxy: the
update did not consider the system setting and I had to set it somewhere
in the configuration manually. O rone had to wait for a very long time
(1h), then
I just found the proxy related bug, this is 772531
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release failed for overloaded mirrors with no
descriptive error
For me the problem isn't so much the wording, but the fact the same
error message can arise from completely different causes. This needs to
be fixed before you can change the wording of the message, just because
the message is shown doesn't mean that there is a problem with the
mirror.
--
You
Steve suggests adding try again later, so how about this:
After updating your packaging information, the essential package '%s'
could not be located. Please check the availability of your archive
mirrors, which may be overloaded or otherwise inaccessible. Please try
again later.
--
You received
@Brian: You're right, but unfortunately, at the point at which this
error message is displayed, we have no idea what is causing the problem,
only that the package isn't available. The best we can do I think is to
suggest a diagnosis and patience. ;)
--
You received this bug notification because
We're never going to know with certainty what the cause of the failure
is, but we should be providing better guidance to users about *probable*
causes for the bug rather than leaving them with an opaque error
message. Mirror unavailability is a very likely cause for this error.
How about:
After
** Branch linked: lp:~barry/update-manager/bug-873468
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release failed for overloaded mirrors with no
descriptive error
On Apr 17, 2012, at 03:37 PM, Steve Langasek wrote:
We're never going to know with certainty what the cause of the failure
is, but we should be providing better guidance to users about *probable*
causes for the bug rather than leaving them with an opaque error
message. Mirror unavailability is a
** Branch linked: lp:update-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release failed for overloaded mirrors with no
descriptive error message
To manage
This bug was fixed in the package update-manager - 1:0.156.13
---
update-manager (1:0.156.13) precise; urgency=low
* Improve the error message used when a package cannot be located after
updating, probably caused by an overloaded mirror. (LP: #873468)
-- Barry Warsaw
@Barry and @Steve, in my case when I see this error, the most probably
cause is that update-manager has misidentified my repositories in
sources.list as third party repositories and disabled all of them.
Without telling me. As such it can't find the essential packages -
because they don't exist!
On Apr 17, 2012, at 11:22 PM, Brian May wrote:
I have reported this problem in #773823, which unfortunately was merged
with a different bug. Requests to have this fixed have been ignored. As
such, if the mirrors are getting overloaded, maybe this is because
people are unable to use anything but
Given that we want to provide a more useful error message, specifically
indicating a possible problem contacting the mirrors, I think the bug is
easy to fix. The tricky part is coming up with the best error message.
Here's what it currently says (from DistUpgradeController.py):
After your
I'm experiencing the same issue and assuming that is because I'm using a
mirror. But we use an inhouse mirror because it makes sense to do so,
for everyone; we download the packages once. How do we make do-release-
upgrade use our mirror (which has the 12.04 files on it)?
--
You received this
Chris Puttick, the message generated is rather generic, and can have a
number of completely different causes. So I suspect it may not have
anything to do with overloaded mirrors.
Unfortunately, my bug report, https://bugs.launchpad.net/ubuntu/+source
/update-manager/+bug/773823, was marked as a
** Changed in: update-manager (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release failed for overloaded
Downgrading this back to 'high'. This doesn't actually cause installs
to fail, it's an upgrade issue - and the bug here doesn't *cause*
upgrades to fail either, it's overloaded mirrors at release time that
cause that. If the machine can't reach the mirror to do the download,
nothing we do in
** Changed in: update-manager (Ubuntu Precise)
Assignee: Stéphane Graber (stgraber) = Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release
** Changed in: update-manager (Ubuntu Precise)
Assignee: Canonical Foundations Team (canonical-foundations) = Stéphane
Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Changing to Critical because this causes failed installs, potentially
for a large number of people
** Changed in: update-manager (Ubuntu Precise)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: update-manager (Ubuntu Precise)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release failed for overloaded mirrors with
Don't know if all these bug-reports, has to do with Precise update-manager
hangs when trying to check for update or even trying installing updates.
Nothing happens at all. it just hangs and looks like it's trying to do what job
ever executed in update-manager.
be back with logs if i can get it
** Changed in: update-manager (Ubuntu Precise)
Milestone: None = ubuntu-12.04
** Changed in: update-manager (Ubuntu Precise)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873468
Title:
Update to latest Release failed for overloaded mirrors with no
descriptive error message
To manage
** Summary changed:
- Update to Oneiric failed for overloaded mirrors with no descriptive error
message
+ Update to latest Release failed for overloaded mirrors with no descriptive
error message
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
25 matches
Mail list logo
