Prerequisites download fails if gpg authentication fails on over-aggressive caches

An interesting point is the attempt to use an Australian mirror despite my mirror settings in update-manager's preferences being set to Taiwan. I don't know if this is a contributer to this bug or a separate bug.

I have reset my mirrors to the main servers using update-manager's preferences, and manually confirmed that AU is not mentioned in /etc/apt/sources.list or any files in /etc/apt/sources.list.d.

Then I ran update-manager -c -d. It failed as above.

Now checking /etc/apt/sources.list.d/prerequists-sources.list I find AU as my mirror:

# sources.list fragment for pre-requists (one with countrymirror, one fallback)
deb http://au.archive.ubuntu.com/ubuntu feisty-backports main/debian-installer
#deb http://archive.ubuntu.com/ubuntu feisty-backports main/debian-installer
# below is just for testing
#deb http://archive.dogfood.launchpad.net/ubuntu feisty-backports main/debian-in

The prerequists-sources.list.save looks correct though:

# sources.list fragment for pre-requists (one with countrymirror, one fallback)
deb http://archive.ubuntu.com/ubuntu/ feisty-backports main/debian-installer
# deb http://archive.ubuntu.com/ubuntu feisty-backports main/debian-installer
# below is just for testing
# deb http://archive.dogfood.launchpad.net/ubuntu feisty-backports main/debian-installer

The current way of choosing the country mirror seems to be incorrect for you, what is puzzling is that the fallback did not work either, I mark this high priority.

Today things went a lot further before failing with package authentication issues. This leads me to suspect the main source of problems is Bug #33505 or similar.

/etc/apt/sources.list.d/prerequists-sources.list no longer exists but did get replaced during the upgrade with one using the AU mirror.

Does this prerequisites bug have anything to do with THIS prerequisites bug? https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/153980

I have a simular bug andmaybe i found a workaround.

1. start the update-manager with sudo update-manager and wait until it crash
2. kopie the prerequists-sources.list from /tmp/NAMECALLEDINCONSOLE into /etc/apt/sources.list.d/ as prerequists-sources.list
3. delete the {archiv} part from this file
4. start the update-manager

Thanks for your reply,

I'm having an update of adept downloadong at the momment, if it doesen't
fix the bug, I'll try your method.

regards

Le dimanche 21 octobre 2007 à 21:04 +0000, Ari a écrit :
> I have a simular bug andmaybe i found a workaround.
>
> 1. start the update-manager with sudo update-manager and wait until it crash
> 2. kopie the prerequists-sources.list from /tmp/NAMECALLEDINCONSOLE into /etc/apt/sources.list.d/ as prerequists-sources.list
> 3. delete the {archiv} part from this file
> 4. start the update-manager
>
--
Anthony MAUDRY

I have the same problem described here.

I've tried almost all the suggestions I've seen related to sources.list and also the suggestion above by 'ari' with no difference.

I guess I'll either post my logs (as requested) to an existing report, or open a new one.

Any suggestions for other workarounds to try?

rocketman wrote:
> I have the same problem described here.
>
> I've tried almost all the suggestions I've seen related to sources.list
> and also the suggestion above by 'ari' with no difference.
>
> I guess I'll either post my logs (as requested) to an existing report,
> or open a new one.
>
> Any suggestions for other workarounds to try?

If you just want a workaround, use ftp instead of http as the protocol when
selecting a mirror.

--
Stuart Bishop <email address hidden> http://www.canonical.com/
Canonical Ltd. http://www.ubuntu.com/

This bug hasn't had any discussion in about 16 months, and there's been a couple more Ubuntu releases since. Do the problems still occur?

People are still talking about it constantly here: https://bugs.launchpad.net/bugs/153980

@loomy: 153980 doesn't seem to me to be the same bug, but I didn't study it in depth. If it is the same bug, these two should be marked as duplicates. Either way, it doesn't look to me like people are discussin the actual bug, but dealing with end-of-lifed releases.

@mvo: I suggest both bugs may be closed, actually, but not wanting to close bugs you might think are still releavant, I don't want to confuse things by closing them myself.

Closing this bug report due to the reasons mentioned above: Obsolete versions and lack of activity.

If a similar bug appears in Ubuntu 10.10, please open a new report.