[arch-general] Making pacman ignore specific packages in a repo?
Is it possible to configure pacman to completely ignore a set of packages from a specific repository? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
On Tue, Mar 22, 2011 at 10:31 AM, Magnus Therning <magnus@therning.org>wrote:
Is it possible to configure pacman to completely ignore a set of packages from a specific repository?
What do you mean? Ignore it from one repo but accept it from another? -- Cédric Girard
2011/3/22 Cédric Girard <girard.cedric@gmail.com>:
On Tue, Mar 22, 2011 at 10:31 AM, Magnus Therning <magnus@therning.org>wrote:
Is it possible to configure pacman to completely ignore a set of packages from a specific repository?
What do you mean? Ignore it from one repo but accept it from another?
Yes, e.g., package foo is in [repoA] and [repoB], I want pacman to *never* consider foo in [repoB] for installation. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
put a over b in pacman conf and it will always install from a and if it cant be found it will move to b. Ignorepkg repob/package might work too
2011/3/22 jesse jaara <jesse.jaara@gmail.com>:
put a over b in pacman conf and it will always install from a and if it cant be found it will move to b. Ignorepkg repob/package might work too
The problem with that is that the package from b *will be considered*, and it'll actually be be chosen in some cases. Is there a way to make sure pacman *never* considers the package from b? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
2011/3/22 Magnus Therning <magnus@therning.org>:
2011/3/22 jesse jaara <jesse.jaara@gmail.com>:
put a over b in pacman conf and it will always install from a and if it cant be found it will move to b. Ignorepkg repob/package might work too
The problem with that is that the package from b *will be considered*, and it'll actually be be chosen in some cases. Is there a way to make sure pacman *never* considers the package from b?
/M
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
No this is not possible. I guess for strange-non-supported pacman cases you should do this manually -- Angel Velásquez angvp @ irc.freenode.net Arch Linux Developer / Trusted User Linux Counter: #359909 http://www.angvp.com
2011/3/22 Ángel Velásquez <angvp@archlinux.org>:
2011/3/22 Magnus Therning <magnus@therning.org>:
2011/3/22 jesse jaara <jesse.jaara@gmail.com>:
put a over b in pacman conf and it will always install from a and if it cant be found it will move to b. Ignorepkg repob/package might work too
The problem with that is that the package from b *will be considered*, and it'll actually be be chosen in some cases. Is there a way to make sure pacman *never* considers the package from b?
No this is not possible.
I guess for strange-non-supported pacman cases you should do this manually
Yes, but I wanted to avoid it when doing some "exploratory package building" :-) Thanks for the help and information provided anyway. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
2011/3/22 jesse jaara <jesse.jaara@gmail.com>
Ignorepkg repob/package might work too
This does not work. I've just tried enabling [community-testing] and ignoring a package set to be updated (with --ignore and with IgnorePkg). The ignored package is still set to be updated. -- Cédric Girard
participants (4)
-
Cédric Girard
-
jesse jaara
-
Magnus Therning
-
Ángel Velásquez