I'm getting this when trying to update/upgrade the system and packages:
For system update with apt-.get upgrade
Fetched 591B in 6s (90B/s) W: GPG error: hag-linux.eu.org hag Release: The following signatures were invalid: KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 W: GPG error: hag-linux.eu.org hag-magic Release: The following signatures were invalid: KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 W: GPG error: hag-linux.eu.org hag-dev Release: The following signatures were invalid: KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? [guest@meanpt-nFluxUbuntu1004 ~]$
For packages updates using synaptic:
W: GPG error: hag-linux.eu.org hag Release: The following signatures were invalid: KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 W: GPG error: hag-linux.eu.org hag-magic Release: The following signatures were invalid: KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 W: GPG error: hag-linux.eu.org hag-dev Release: The following signatures were invalid: KEYEXPIRED 1276005470 KEYEXPIRED 1276005470 KEYEXPIRED 1276005470
hello meanpt are you running from livecd/usb or installed to hard drive?
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
that sounds like you have synaptic open and trying to do apt-get/aptitude in terminal the Hag gpg error is harmless; they just need to renew their gpg, etc
so, shutdown synaptic and close any terminal using apt-get, etc and it should work fine
Hi, thanks for the reply. I'm booting from a HD install in a VBox's vm machine.
Ran again the GUI Update Manager without with terminal closed and got these:
Could not download all repository indexes
The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.