[arch-general] Local packages newer than ones from core?

[A Rojas]

kendell clark wrote:

> 
> Hi all
> I just tried to update my internal system with #pacman -Syyu tonight and
> recieved the following warnings from pacman.
>   warning: binutils: local (2.23-1) is newer than core (2.22-10)
> warning: e2fsprogs: local (1.42.6-1) is newer than core (1.42.5-1)
> warning: gcc: local (4.7.2-2) is newer than core (4.7.2-1)
> warning: gcc-libs: local (4.7.2-2) is newer than core (4.7.2-1)
> warning: glib2: local (2.34.1-1) is newer than core (2.32.4-1)
> warning: glibc: local (2.16.0-5) is newer than core (2.16.0-4)
> warning: hwids: local (20121022-1) is newer than core (20121012-1)
> warning: iproute2: local (3.6.0-2) is newer than core (3.5.1-1)
> warning: iptables: local (1.4.16.2-1) is newer than core (1.4.15-1)
> warning: linux-api-headers: local (3.6.3-1) is newer than core (3.5.5-1)
> warning: perl: local (5.16.1-2) is newer than core (5.16.1-1)
> I don't mean to sound like a noob but I still am, smiles. I've never
> seen this warning message before and as far as I know this isn't
> possible, as I only pull packages from core, community, and multilib. I
> have built some local aur packages, espeak development version, dropbox,
> dropbox daemon, and mangler. THis could be the cause, although I'm not
> sure how to find out. Any help would be greatly appreciated. i'm
> beginning to really love arch, especially without pulseaudio.
> One final note: I have the linux-lts package installed as opposed to the
> latest 3.6.x kernel, as speakup is broken in  kernels later tahn 3.4.
> Thanks
> Kendell clark

Those packages are from [testing]. You propably had it enabled at some point 
and now you don't.