Bug#483147: package pinning should allow using a release
Package: apt
Version: 0.7.13
Severity: wishlist
Hi,
I have my own local archive with packages where I add local packages
or bugsfixes to debian packages. Or, as in the case of wine, a
diversion of the debian package.
Normaly I want newer versions of debian packages to override local
packages on the assumption that they will include the bugfixes the
local packages have. So I don't want to have a higher pin for the
archive. But for wine I want to keep my locally modified packages.
So I thought I would use the following:
Package: *wine*
Pin: release o=local
Pin-Priority: 600
But 2 things don't work there:
1) no wildcards on Package names
2) no release pinning on package pins
The first I can understand but why the second?
I also have a second use case for exactly the same: I use mplayer from
the multimedia repository. So now I want to make sure I keep the
mplayer from the multimedia repository but not have it replace
e.g. bash. That can not be expressed with either a repository pin or a
package pin.
MfG
Goswin
-- Package-specific info:
-- (/etc/apt/preferences present, but not submitted) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (400, 'unstable-i386')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25-kvm
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages apt depends on:
ii debian-archive-keyring 2008.04.16+nmu1 GnuPG archive keys of the Debian a
ii libc6 2.7-11 GNU C Library: Shared libraries
ii libgcc1 1:4.3.0-5 GCC support library
ii libstdc++6 4.3.0-5 The GNU Standard C++ Library v3
apt recommends no packages.
-- no debconf information
Reply to: