The problem came back, so I tried the cleanup again and no joy. Then a
little while later things cleared, then the problem returned. So it
looks like something intermittent. One posting suggested that there
might be a timing problem with update manager not waiting long enough
for response. Anyone any ideas about that. If I manually try to fetch
the file that is listed as failing I can get it OK. If it is a timing
glitch, that would explain the diversity of "fixes", which likely just
get lucky.
JN
On 13-08-23 11:53 AM, Prof J C Nash (U30A) wrote:
Seems 'sudo apt-get clean' and 'sudo apt-get autoclean' got rid of a
problem in the cache as JFM suggested.
Thanks folks.
JN
On 13-08-23 10:00 AM, Paul Belanger wrote:
On Fri, Aug 23, 2013 at 9:04 AM, Prof J C Nash (U30A)
<nashjc [ at ] uottawa [ dot ] ca> wrote:
I've been having an issue with one of my machines that is running
Linux Mint
Olivia, which is based on Ubuntu Raring (13.04). The apt-get update
equivalent (or that run in a terminal) gives failures with
Failed to fetch
http://security.ubuntu.com/ubuntu/dists/raring-security/main/
and related to following strings.
http://security.ubuntu.com raring-security Release.gpg
This causes update to fail.
There are many (misleading) posts about things to do on the net, none of
which have worked for me. I think the gpg signatures might be the
issue, and
I'm tempted to simply delete them from the /etc/apt/ area, which in
13.04 is
no longer set up with apt.conf but has a directory apt.conf.d that is
much
more complex to sort out.
Anyone with experience of this problem?
No issues here. Maybe something is stale. What do your apt keys look
like?
$ sudo apt-key list
_______________________________________________
Linux mailing list
Linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca
http://oclug.on.ca/mailman/listinfo/linux