[SOLVED] Understanding pacman's IgnorePkg messages

Leonid.I · 2010-09-22 16:29:41

Hi community,

I just realized that my understanding of pacman messages regarding packages in the IgnorePkg array is quite spotty. So, here is my IgnorePkg from pacman.conf:

IgnorePkg   = gnuplot fetchmail gnome-mplayer cups libcups djvulibre fcron vim-runtime gvim blas lapack

And this is the output from pacman -Syu:

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
warning: blas: ignoring package upgrade (3.2.2-11 => 3.2.1-2)
warning: cups: local (1.4.4-31) is newer than extra (1.4.4-3)
warning: djvulibre: local (3.5.22-11) is newer than extra (3.5.22-2)
warning: fcron: ignoring package upgrade (3.0.6-1 => 3.0.6-3)
warning: fetchmail: local (6.3.17-11) is newer than extra (6.3.17-1)
warning: gnome-mplayer: local (0.9.9.2-11) is newer than community (0.9.9.2-1)
warning: gnuplot: local (4.4.0-11) is newer than extra (4.4.0-1)
warning: gvim: ignoring package upgrade (7.3.3-11 => 7.3.3-1)
warning: lapack: local (3.2.2-11) is newer than extra (3.2.1-2)
warning: libcups: local (1.4.4-31) is newer than extra (1.4.4-3)
warning: screen: local (4.0.3-81) is newer than extra (4.0.3-8)
warning: subversion: local (1.6.12-12) is newer than extra (1.6.9-5)
warning: vim-runtime: ignoring package upgrade (7.3.3-11 => 7.3.3-1)
 ...

All the above packages are built locally (sometimes I don't wait upon official repos and compile a newer version, sometimes I want to change compile-time options and append $pkgrel with a '1').

And my question is: why does pacman want to update blas, gvim and vim-runtime, but is OK with gnuplot, cups, etc.? Especially if my blas is newer than /extra.

Thanks.

Last edited by Leonid.I (2010-09-24 17:14:02)

brisbin33 · 2010-09-22 16:54:45

In the case of blas, gvim, etc it is likely because options=(force) is specified in the PKGBUILD(s) and pacman will always want to (up|down)grade a force package in the case of a version mismatch*

*note: This is my understanding, please someone correct me if I'm wrong

Leonid.I · 2010-09-22 19:27:25

brisbin33 wrote:

In the case of blas, gvim, etc it is likely because options=(force) is specified in the PKGBUILD(s) and pacman will always want to (up|down)grade a force package in the case of a version mismatch*
*note: This is my understanding, please someone correct me if I'm wrong

Note to myself: RTFM; slap the forehead.

Yes, it was indeed due to the force option... Thank you, the wise one

Arch Linux

#1 2010-09-22 16:29:41

[SOLVED] Understanding pacman's IgnorePkg messages

#2 2010-09-22 16:54:45

Re: [SOLVED] Understanding pacman's IgnorePkg messages

#3 2010-09-22 19:27:25

Re: [SOLVED] Understanding pacman's IgnorePkg messages

Board footer