You are not logged in.
This is not the first time this happens. Though I've never had a real problem with it, I'd like to know why. All packages are pulled off the official repos, and these outputs are after a pacman -Sy, just to be clear.
$ pacman -Qs jack-audio
local/jack-audio-connection-kit 0.109.0-1
$ pacman -Ss jack-audio
extra/jack-audio-connection-kit 0.103.0-1
$ pacman -Qs ardour
local/ardour 2.2-1
$ pacman -Ss ardour
extra/ardour 2.1-1
Syu'ing gives a warning with jack-audio-connection-kit ".. is newer than extra .."
and with ardour ".. forcing upgrade .."
Now where did I get these packages if they're not in the repos yet? I know both of them are officially released though.. And also, what is the recommended action in cases like these, should I downgrade to keep my machine in sync with the repos?
Offline
Now where did I get these packages if they're not in the repos yet? I know both of them are officially released though.. And also, what is the recommended action in cases like these, should I downgrade to keep my machine in sync with the repos?
Maybe the dev uploaded the packages, and decided only just after that that something was wrong with these packages and forced a downgrade. But then again, is just a guess.
Offline
I have the same issue.
[root@archlinux bionnaki]# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
warning: jack-audio-connection-kit: local (0.109.0-1) is newer than extra (0.103.0-1)
local database is up to date
Offline
I've had this before, usually when changing my mirror. I put it down to the fact that the mirror's don't all sync at the same time. Just a guess. Had either of you changed your mirror before syncing?
Offline
I'm having this same exact issue (only with Jack, but i don't have Ardour installed so...). Also, i used the same mirror i'm currently using for installing the package.
Offline
jack-audio-connection-kit 0.107.2-20070704 from proaudio, so i dunno where from you could get *109*. don't fret, why not just pacman -S jack-audio-connection-kit?
Last edited by schivmeister (2008-01-25 18:51:08)
I need real, proper pen and paper for this.
Offline
i had noticed the jack issue too. i only use 1 mirror and my pacman.conf doesnt even have an Include line. i thought it only happened with pacman 3.1.0 though
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
It's not a pacman problem, it's a problem in the database.
So maybe a problem with database scripts? It has happened several times already, it's annoying.
http://bugs.archlinux.org/task/9337
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I just learnt something, it is:
if [ pacman is screwing you ];
then pacman -Syy
else
find some other way
but
do that first && pacman -S $problematic-pkgs
fi
Last edited by schivmeister (2008-01-25 20:21:00)
I need real, proper pen and paper for this.
Offline
Same warning like yours.
Offline
its been fixed. wait for your mirror to sync
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
This sort of behavior is really rare, but I still haven't got an answer to *why* it happens. Not that it's a big thing, but a thing anyway. I kind of got the idea from that bug report shinig did, but could someone please explain the same thing in english Was it just a new package with old version info?
Anyway, as dolby said all is good with ardour and jack now.
Offline
Was it just a new package with old version info?
Something like that.
When you do pacman -Ss, pacman looks at its sync databases, located in /var/lib/pacman/sync/
pacman -Ss ardour found the following directory :
/var/lib/pacman/sync/extra/ardour-2.1-1/
Inside that directory, you have two meta-info files, which contain information like package name, version, and filename.
For this broken entry, it looked like that :
> head -n8 /var/lib/pacman/sync/extra/ardour-2.1-1/desc
%FILENAME%
ardour-2.2-1-i686.pkg.tar.gz
%NAME%
ardour
%VERSION%
2.1-1
Notice that both the VERSION here, and the version in the directory name are 2.1-1.
But the version in the filename is 2.2-1 !
So when you installed ardour with pacman -S ardour, it actually downloaded the ardour-2.2-1-i686.pkg.tar.gz package,
and so installed ardour version 2.2-1.
So in the end, you had ardour 2.2-1 locally installed in your system. But the version listed in the sync database was still 2.1-1.
Now that the database is fixed, this is how it looks :
> head -n8 /var/lib/pacman/sync/extra/ardour-2.2-1/desc
%FILENAME%
ardour-2.2-1-i686.pkg.tar.gz
%NAME%
ardour
%VERSION%
2.2-1
We see 2.2-1 everywhere now, so it's fine.
Note that I only described how these two entries were broken, not how it happened in the first place, because I don't have any clue.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline