Bug#599270: update-manager-core: Does not honour version lock on xvidcap
Andreas Neudecker
zapyon at gmx.net
Wed Oct 6 09:58:51 UTC 2010
Package: update-manager-core
Version: 0.200.4-1
Severity: normal
Hi.
I have recently installed the package xvidcap. First using debian-
multimedia.org (yes, I know, it's not official Debian), then by manually
installing the Debian package provided by xvidcap.sf.net.
Because the version from xvidcap.sf.net is 1.1.7 and the one from debian-
multimedia.org (which is still in my sources list due to other programs) is
1.1.7-0.5, I have locked the manually installed version 1.1.7 in synaptic.
Now, whenever update-manager is started (I use the GNOME GUI) it includes
xvidcap in the list of packages to be updated, not honouring the lock set by
synaptic. With other packages like sane, sane-utils, xsane, xsane-common,
libsane, libsane-extras, libsane-hpaio, etc. locked versions older than the
current version in squeeze is honoured by update-manager.
It is unclear to me why this is different with xvidcap. May be because it is
from a different repository?
After my opinion locks should be honoured regardless of the repository (in
sources.list) the newer version is originally from.
Best regards
Andreas
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages update-manager-core depends on:
ii lsb-release 3.2-23.1 Linux Standard Base version report
ii python 2.6.5-13 interactive high-level object-orie
ii python-apt 0.7.97.1 Python interface to libapt-pkg
ii python-support 1.0.10 automated rebuilding support for P
Versions of packages update-manager-core recommends:
ii update-manager-gnome 0.200.4-1 GNOME application that manages sof
update-manager-core suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list