[arch-general] How can packages be "Newer than testing"??

[Allan McRae]

David C. Rankin wrote:
> Listmates,
>
> 	On an i586 box with kde4 from testing, I am now unable to login. kdm starts to login, crashes and restarts. (detailed in a separate post)  I was hoping that this would be fixed by an update or two, but upon checking this evening, I received the following:
>
> 19:27 supersff:~> pms -u
> :: Synchronizing package databases...
>  kdemod-legacy is up to date
>  testing is up to date
>  kde-unstable is up to date
>  core is up to date
>  extra is up to date
>  community is up to date
>  archlinuxfr               25.2K   47.3K/s 00:00:01 [##################################################] 100%
> :: Starting full system upgrade...
> warning: akonadi: local (1.1.95-1) is newer than testing (1.1.2-2)
> warning: kdebase-runtime: local (4.2.95-1) is newer than testing (4.2.4-2)
> warning: kdelibs: local (4.2.95-1) is newer than testing (4.2.4-3)
>  local database is up to date
>
> Huh???
>
> 	I guess what it is saying is that akonadi, etc. are newer than the versions in "testing",  but why would that message ever be generated with "kde-unstable" available?
>
> 	Also, could this also be a cause of the crashed kdm login on the i586 box?
>
>   
kde-unstable needs to be above [testing].

Allan