Pacman wanting to downgrade a package

Antti Alien · 2007-04-26 06:30:07

I have package ipw3945-beyond version 1.2.0 installed from a custom pkgbuild. Now, when I'm trying to upgrade all packages, pacman insists on downgrading ipw3945-beyond to the version in extra repository, 1.1.3.

So, what's happening?

Last edited by Antti Alien (2007-04-26 06:30:27)

stonecrest · 2007-04-26 06:43:53

It has options=("FORCE") in it.

Antti Alien · 2007-04-26 06:54:24

Ok... I brutally removed it for now, but is there a correct way to get pass that and why on earth does it have force option enabled?

Now pacman kindly tells me that

":: ipw3945-beyond: local (1.2.0-1) appears to be newer than repo (extra/1.1.3-3)"

Yes, I know, that is the reason I used my own package

tomk · 2007-04-26 08:16:36

Until the repo package is up to date, put ipw3945-beyond on an IgnorePkg line in /etc/pacman.conf.

Last edited by tomk (2007-04-26 08:17:07)

Antti Alien · 2007-04-26 08:26:11

Thanks, that seemed to do the trick. Though pacman still keeps whining about repo package being older, but I guess I'll just have to ignore it.

patroclo7 · 2007-04-26 09:05:15

The solution to avoid that whining is to build your own local repo and put is as the first repo in /etc/pacman.conf. 'man pacman' includes all the informations to accomplish this task.

stonecrest · 2007-04-26 21:29:19

Actually, unless I'm confusing this with something else, I think that pacman3 no longer displays warnings for packages in IgnorePkg.

Snowman · 2007-04-27 04:19:14

pacman3 still displays warnings for packages in IgnorePkg.

stonecrest · 2007-04-27 04:45:34

Ah nevermind, I was thinking of a slightly different situation involving IgnorePkg and forcing. Pacman 3 no longer prompts you to upgrade, but I guess the warnings are still there.

.:B:. · 2007-04-27 05:01:30

patroclo7 wrote:

The solution to avoid that whining is to build your own local repo and put is as the first repo in /etc/pacman.conf. 'man pacman' includes all the informations to accomplish this task.

This is what I do; however, I noticed, if you have duplicate entries (packages), pacman will not prompt you about dependencies being too old (i.e. lower packages version number than required being present on your own repo), it will just say it cannot install package X due to unresolved dependencies Y and Z .

To make it more concrete: I have slimmer builds of nautilus & nautilus-cd-burner on my own repo, but use the sound-juicer package from extra. Pacman would not upgrade nautilus & nautilus-cd-burner with those available in extra, it just complained about unresolved dependencies for sound-juicer.

Which, of course, is another problem, but I just wanted to point that out .

Last edited by B (2007-04-27 05:03:36)

Antti Alien · 2007-04-28 09:48:05

patroclo7 wrote:

The solution to avoid that whining is to build your own local repo and put is as the first repo in /etc/pacman.conf. 'man pacman' includes all the informations to accomplish this task.

I created a custom repository with the instructions given in http://wiki.archlinux.org/index.php/Cus … nd_gensync and now everything is working great. Thanks for the help :-]

Arch Linux

#1 2007-04-26 06:30:07

Pacman wanting to downgrade a package

#2 2007-04-26 06:43:53

Re: Pacman wanting to downgrade a package

#3 2007-04-26 06:54:24

Re: Pacman wanting to downgrade a package

#4 2007-04-26 08:16:36

Re: Pacman wanting to downgrade a package

#5 2007-04-26 08:26:11

Re: Pacman wanting to downgrade a package

#6 2007-04-26 09:05:15

Re: Pacman wanting to downgrade a package

#7 2007-04-26 21:29:19

Re: Pacman wanting to downgrade a package

#8 2007-04-27 04:19:14

Re: Pacman wanting to downgrade a package

#9 2007-04-27 04:45:34

Re: Pacman wanting to downgrade a package

#10 2007-04-27 05:01:30

Re: Pacman wanting to downgrade a package

#11 2007-04-28 09:48:05

Re: Pacman wanting to downgrade a package

Board footer