On Thu, 16 Feb 2012 21:52:27 +0000 Fons Adriaensen <fons@xxxxxxxxxxxxxx> wrote: > On Thu, Feb 16, 2012 at 10:41:53PM +0100, Karol Blazewicz wrote: > > > On Thu, Feb 16, 2012 at 10:36 PM, Fons Adriaensen <fons@xxxxxxxxxxxxxx> > > wrote: > > > > > Because it is apparently a dependency of octave. And pacman tried to > > > install it, but failed due to the 'no version information'. > > > > 'pacman -S foo' doesn't work that way. > > Could you elaborate a bit on that ? Isn't 'pacman -S foo' supposed > to either install (if not yet installed) or update any dependencies > of 'foo' ? That anyway is what apperently it has done for the last > three years I've been using it... > > I can perfectly understand that this will trigger an avalanche of > updates on a system that is mostly out of date, and that the result > can't be guaranteed in such cases and a full system update is in order. > > But that is not the case here. What happens is that one library fails > to install (also separately) as a result of 'no version information'. > > Ciao, > Simply put there are 2 pkg trees: in the official repos and on your system. They are supposed to be in-sync -- that's what pacman -Sy does. pacman -S fetches pkg according to YOUR tree. Over time the sync is lost, so YOUR tree may have nothing in common with the repo (e.g. some packages may not even exist anymore). -- Leonid Isaev GnuPG key ID: 164B5A6D Key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Attachment:
signature.asc
Description: PGP signature
