On Thu, 28 Jan 2016 18:57:05 -0500 Francis Gerund wrote:

Should this be reported as a bug (or 2-3 bugs)?

No, it's not a bug. Info about this has been all over the mailing lists, forums, and IRC for days. Do some checking around.

On 1/28/2016 6:49 PM, Francis Gerund wrote:

On Thu, Jan 28, 2016 at 7:13 PM, Doug Newgard wrote:

...

On Thu, 28 Jan 2016 18:57:05 -0500 Francis Gerund wrote:

...

Should this be reported as a bug (or 2-3 bugs)? No, it's not a bug. Info about this has been all over the mailing lists, forums, and IRC for days. Do some checking around.

I'm sort of new to Arch. I just installed yesterday, so didn't know about that. I did not see a bug report (maybe I missed it).

And I thought that even if it is flagged as out-of-date, it would still install.

I thought it was a reasonable question to ask (with some detail provided), and I was tring to be helpful.

I don't know the etiquette here yet. Sorry.

And Gnucash is really important to me.

I will try checking the email archives.

At Arch, is IRC preferred over mailing lists as a source of information?

IRC is much harder for em to use effectively; it's like trying to dring from a fire hose.

This seems reasonable to me. Even if a package is flagged out of date, it will still download and install successfully, unless there's a problem with it's gpg signature. If that's the case, pacman will fail with a sometimes cryptic error. If you want, I can try building a package from current stable gnucash source and upload it somewhere where you can fetch until arch updates it's package. Thanks Kendell clark

On Thu, Jan 28, 2016 at 7:54 PM, kendell clark wrote:

On 1/28/2016 6:49 PM, Francis Gerund wrote:

...

On Thu, Jan 28, 2016 at 7:13 PM, Doug Newgard wrote:

On Thu, 28 Jan 2016 18:57:05 -0500

...

Francis Gerund wrote:

Should this be reported as a bug (or 2-3 bugs)?

...

No, it's not a bug. Info about this has been all over the mailing lists, forums, and IRC for days. Do some checking around.

I'm sort of new to Arch. I just installed yesterday, so didn't know about that. I did not see a bug report (maybe I missed it).

And I thought that even if it is flagged as out-of-date, it would still install.

I thought it was a reasonable question to ask (with some detail provided), and I was tring to be helpful.

I don't know the etiquette here yet. Sorry.

And Gnucash is really important to me.

I will try checking the email archives.

At Arch, is IRC preferred over mailing lists as a source of information?

IRC is much harder for em to use effectively; it's like trying to dring from a fire hose.

This seems reasonable to me. Even if a package is flagged out of date, it will still download and install successfully, unless there's a problem with it's gpg signature. If that's the case, pacman will fail with a sometimes cryptic error. If you want, I can try building a package from current stable gnucash source and upload it somewhere where you can fetch until arch updates it's package. Thanks Kendell clark

Kendall, Thanks for your reply. After checking the mailing list archives, I found a similar problem was with the "courage" package, which was solved by (as root): pacman-key --refresh-keys I tried that, and it *seems* to have worked. I downloaded Gnucash 2.6.10-1, and it *appears* to be okay. So, don't go to the trouble of building a package. But thanks for offering. I appreciate it!

On Fri, Jan 29, 2016 at 12:48 AM, Ralf Mardorf wrote:

On Thu, 28 Jan 2016 20:23:14 -0500, Francis Gerund wrote:

...

After checking the mailing list archives, I found a similar problem was with the "courage" package, which was solved by (as root):

pacman-key --refresh-keys

Actually your install suffers from not being updated. The refresh was needed, when the keyring package was only available by the testing repository, but since a few days it's provided by core [1].

I never used pacmatic, so perhaps you should consider to update using 'sudo pacman -Syu'. If your install is up-to-date, then the output of 'pacman -Q archlinux-keyring' must be 'archlinux-keyring 20160123-1'.

[1] [rocketmouse@archlinux ~]$ grep "upgraded archlinux-keyring" /var/log/pacman.log | grep 2016 [2016-01-26 08:16] [ALPM] upgraded archlinux-keyring (20151220-1 -> 20160123-1) [rocketmouse@archlinux ~]$ grep pkgver= /var/abs/core/archlinux-keyring/PKGBUILD pkgver=20160123 [rocketmouse@archlinux ~]$ pacman -Si archlinux-keyring | grep Ver Version : 20160123-1

Thanks for the info guys, but now this is weird: After doing: sudo pacman -Syyuv and sudo pacman -Syyuv archlinux-keyring and sudo pacman-key --refresh-keys and sudo pacman-key --refresh-keys --updatedb and sudo pacman -Syyuv and rebooting . . . and then doing it all again, I still get: sudo pacmatic -Q archlinux-keyring archlinux-keyring 20151220-1 sudo pacmatic -Ss archlinux-keyring core/archlinux-keyring 20151220-1 [installed] Arch Linux PGP keyring But there sure seems to be a newer version in core: 1 exact match found. Arch Repo Name Version Description Last Updated Flag Date any Core archlinux-keyring https://www.archlinux.org/packages/core/any/archlinux-keyring/ 20160123-1 Arch Linux PGP keyring 2016-01-25 Yet my system won't even admit that a newer version exists! Is there a way to update archlinux-keyring without reinstalling the whole system?

On Sat, 30 Jan 2016 09:13:01 -0600, Doug Newgard wrote:

On Sat, 30 Jan 2016 10:08:58 -0500 Francis Gerund wrote:

...

https://www.archlinux.org/packages/core/any/archlinux-keyring/

Is there a way to update archlinux-keyring without reinstalling the whole system?

Yes, there is. The above link provides a box named "Package Actions". One option is "Download From Mirror". To install a downloaded package run "# pacman -U /path/to/package/package_name-version.pkg.tar.xz" - https://wiki.archlinux.org/index.php/pacman#Additional_commands However, you should follow Doug's hint.

Try a different mirror

Edit your mirrorlist, perhaps there's a file /etc/pacman.d/mirrorlist.pacnew. If so, compare the new list with the mirrors you're using now. Maybe some mirrors aren't valid anymore. Regards, Ralf

On Sat, Jan 30, 2016 at 10:48 AM, Francis Gerund wrote:

On Sat, Jan 30, 2016 at 10:13 AM, Doug Newgard wrote:

...

On Sat, 30 Jan 2016 10:08:58 -0500 Francis Gerund wrote:

...

But there sure seems to be a newer version in core:

1 exact match found. Arch Repo Name Version Description Last Updated Flag Date any Core archlinux-keyring https://www.archlinux.org/packages/core/any/archlinux-keyring/ 20160123-1 Arch Linux PGP keyring 2016-01-25 Yet my system won't even admit that a newer version exists!

Is there a way to update archlinux-keyring without reinstalling the whole system?

Try a different mirror

Thanks Doug.

That was indeed the problem (and solution). Why didn't I think of that?

Thanks Ralf, for that. And to all who replied. The problems seems to be fixed. I just need to remember to keep the mirrorlist up to date.