Re: [arch-general] error: key "A6234074498E9CEE" could not be looked up remotely
On Wed, 11 Feb 2015 22:11:49 -0500 Genes Lists wrote: > On 02/11/2015 10:06 PM, mick wrote: > > The last few days when I try to update (pacman -Syyu) I get the following:- > .. > > error: key "A6234074498E9CEE" could not be looked up remotely > > error: required key missing from keyring > > error: failed to commit transaction (unexpected error) > > Errors occurred, no packages were upgraded. > > > > how do I fix it?? > > > > Try changing keyserver line in /etc/pacman.d/gnupg/gpg.conf >to > > hkp://pgp.mit.edu:11371 > > rerun pacman -Syu > and accept the import the new key. > > Let us know if that gets around the problem. > > You can change it back or not after this - experts can opine more. > > Gene > Many thanks, that did it
Re: [arch-general] error: key "A6234074498E9CEE" could not be looked up remotely
On 02/11/2015 10:06 PM, mick wrote: The last few days when I try to update (pacman -Syyu) I get the following:- .. error: key "A6234074498E9CEE" could not be looked up remotely error: required key missing from keyring error: failed to commit transaction (unexpected error) Errors occurred, no packages were upgraded. how do I fix it?? Try changing keyserver line in /etc/pacman.d/gnupg/gpg.conf to hkp://pgp.mit.edu:11371 rerun pacman -Syu and accept the import the new key. Let us know if that gets around the problem. You can change it back or not after this - experts can opine more. Gene
Re: [arch-general] error: key "A6234074498E9CEE" could not be looked up remotely
On Thursday, February 12, 2015 14:06:39 mick wrote: > error: key "A6234074498E9CEE" could not be looked up remotely https://bbs.archlinux.org/viewtopic.php?id=193382 Regards, Felix Yan signature.asc Description: This is a digitally signed message part.
[arch-general] error: key "A6234074498E9CEE" could not be looked up remotely
The last few days when I try to update (pacman -Syyu) I get the following:- (29/29) checking keys in keyring [##] 100% downloading required keys... error: key "A6234074498E9CEE" could not be looked up remotely error: required key missing from keyring error: failed to commit transaction (unexpected error) Errors occurred, no packages were upgraded. how do I fix it??
Re: [arch-general] pacman security when importing new keys?
1 little observation - i had a network blackout (traveling) just as was asking me to ok the import. pacman exited. When i reconnected and tried again - i did not get a Y/n prompt to import - i just get error. The only way I found to proceed with any update after that was to change the key server to hkp://pgp.mit.edu:11371 as documented on website. Then it asked once again to import and all proceeded. Just FYI in case anyone else gets flaky behaviour. Be interesting to know for those that said 'n' to the import - if they got asked a second time or not. Thx. gene
[arch-general] NFS won't start since 2015-2-11 update (solved)
Do # systemctl enable rpcbind.service and reboot or `systemctl restart nfs-utils`. It seems that the before rpcbind-0.2.2 this service were preset to "enabled" but this is no longer the case, so it will default to "disabled". Just my €0.02. -- Rodrigo
Re: [arch-general] fdisk vs. gdisk for GPT partitioning
2015-02-11 19:13 GMT+01:00 Jude DaShiell : > Yes, I couldn't create an ef02 partition using fdisk. I ended up using > gdisk and the job got done with no problem at all. You can create a BIOS boot partition ("ef02" in gdisk) in fdisk: Press "p" to change partition type, press "L" to list partition types, and look for "BIOS boot partition": "4 BIOS boot ..." type "4" done! Or did you mean something else?
Re: [arch-general] fdisk vs. gdisk for GPT partitioning
Yes, I couldn't create an ef02 partition using fdisk. I ended up using gdisk and the job got done with no problem at all. On Tue, 16 Dec 2014, Sebastiaan Lokhorst wrote: > Hello everyone, > > Since more than a year now, fdisk (provided by util-linux) has had GPT > support. This theoretically makes gdisk a duplicate of fdisk, and we could > replace gdisk with fdisk. > > Now, I'm not asking to drop gdisk or anything like that, but in an effort > to clean up the Beginners' guide of the Arch Wiki, we want to use a single > partitioning tool for both MBR and GPT partitioning instructions.[1] > util-linux fdisk is able to provide this functionality, but we are not > completely sure if it is stable by now (it should be, I think). > > So, now my question: is there anyone who has had bad experiences with fdisk > and GPT partitions, where gdisk was superior? Or any other objections why > we should keep gdisk instructions in the Beginners' guide? > > Thanks! > Sebastiaan > > [1] > https://wiki.archlinux.org/index.php/Talk:Beginners%27_guide#remove_gdisk_instructions_for_install_medium_2013-11 > > jude Twitter: @JudeDaShiell
Re: [arch-general] broken locale after glibc upgrade
On Wed, Feb 11, 2015 at 10:57 AM, Sebastiaan Lokhorst wrote: > 2015-02-11 10:47 GMT+01:00 arnaud gaboury : > >> I had to manually edit /etc/locale.gen, uncomment the needed locales, >> then run locale-gen to fix this issue. >> > > You likely overwrote locale.gen with locale.gen.pacnew and forgot to > uncomment any locales. certainly! Thank you -- google.com/+arnaudgabourygabx
Re: [arch-general] broken locale after glibc upgrade
2015-02-11 10:47 GMT+01:00 arnaud gaboury : > I had to manually edit /etc/locale.gen, uncomment the needed locales, > then run locale-gen to fix this issue. > You likely overwrote locale.gen with locale.gen.pacnew and forgot to uncomment any locales.
[arch-general] broken locale after glibc upgrade
After a recent upgrade, my locale was broken. Here is extract from pacman.log: [2015-02-11 08:19] [PACMAN] Running 'pacman -Syu' [2015-02-11 08:19] [PACMAN] synchronizing package lists [2015-02-11 08:19] [PACMAN] starting full system upgrade [2015-02-11 08:20] [ALPM] transaction started [2015-02-11 08:20] [ALPM] transaction failed [2015-02-11 08:21] [PACMAN] Running 'pacman -Syu' [2015-02-11 08:21] [PACMAN] synchronizing package lists [2015-02-11 08:21] [PACMAN] starting full system upgrade [2015-02-11 08:21] [ALPM] transaction started [2015-02-11 08:22] [ALPM] upgraded linux-api-headers (3.18.1-1 -> 3.18.5-1) [2015-02-11 08:22] [ALPM] upgraded glibc (2.20-6 -> 2.21-2) [2015-02-11 08:22] [ALPM-SCRIPTLET] Generating locales... [2015-02-11 08:22] [ALPM-SCRIPTLET] Generation complete. I had to manually edit /etc/locale.gen, uncomment the needed locales, then run locale-gen to fix this issue. Any idea about what happened ? -- google.com/+arnaudgabourygabx