-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Well, then I wonder if there is something wrong with the easynews mirror? Doing a 'pacman -Si kernel26' yields 2.6.31.6-1 as its version and this is now 4:20 AM Mount time. I usually have good luck with this mirror. Wonder if I need to change mirrors or something. On Wed, Dec 30, 2009 at 02:49:54PM +0800, Ray Rashif wrote:

2009/12/30 Steve Holmes :

...

Hey, when I did a 'pacman -Syu' this evening, it tried to upgrade speakup from Community but failed because it was expecting a later version of kernel26.  Is the newer kernel on its way?

Yes. If not, it's a bug.

This happens when (1) the packager has yet to update that specific package (in this case kernel26) or (2) the mirror has only sync'd part of the repo (in this case speakup but not kernel26).

-- GPG/PGP ID: B42DDCAD -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAks7N5EACgkQWSjv55S0LfEH/gCfQN0X7PyWq4wwDSkKTNgtvJBK 7msAoN4QkJrmosdyFZUkvLz2mhYjg2VK =CVCx -----END PGP SIGNATURE-----

I changed mirrors and that seemed to have done the trick. Well, umm, not really. What I mean is two kernel26.32 packages got updated but now my machine is completely dead in the water! I guess I'm gonna have to boot with the live CD when I get home and start downgrading some packages <sigh>. This is the first time I've upgraded kernel packages and have my machine fall completely over! no boot! I'm at work now so can't deal further with this until I get home tonight but... Ray Rashif wrote:

2009/12/30 Steve Holmes :

...

Hey, when I did a 'pacman -Syu' this evening, it tried to upgrade speakup from Community but failed because it was expecting a later version of kernel26. Is the newer kernel on its way?

Yes. If not, it's a bug.

This happens when (1) the packager has yet to update that specific package (in this case kernel26) or (2) the mirror has only sync'd part of the repo (in this case speakup but not kernel26).

Laurie Clark-Michalek wrote:

2009/12/30 Steve Holmes :

...

I changed mirrors and that seemed to have done the trick. Well, umm, not really. What I mean is two kernel26.32 packages got updated but now my machine is completely dead in the water! I guess I'm gonna have to boot with the live CD when I get home and start downgrading some packages <sigh>. This is the first time I've upgraded kernel packages and have my machine fall completely over! no boot! I'm at work now so can't deal further with this until I get home tonight but...

Hi,

Did you pacman -Syu, or did you just update the kernel when you updated after you changed the mirror? Also, you can expect problems with the 26.32 series, as it has just been introduced. However, in all the time I have been using Arch, I have never had my machine break massivly from a kernel update.

Thanks, Laurie

P.S. Don't top post, it can make things hard to read.

Yes I did. I recalled 4 packages being specified for update. I forget their exact names now but two of them were kernel26-32 related. They each had an additional qualifier like driver, module, etc. Sorry, I'm not at that computer right now and it can't boot yet anyway <sigh>.