Bug#672615: lintian: binaries-have-file-conflict misses virtual Conflicts/Provides
Package: lintian
Version: 2.5.6
Severity: normal
Hi,
Lintian shows several binaries-have-file-conflict warnings for
firebird2.5 due to it not considering the virtual packages provided
and conflicted with.
Example:
W: firebird2.5 source: binaries-have-file-conflict firebird2.5-classic-common firebird2.5-super usr/bin/fbstat
But:
Package: firebird2.5-classic-common
Provides: firebird-udf, firebird-utils
Conflicts: firebird-udf, firebird-utils, …
Package: firebird2.5-super
Provides: firebird-server, firebird-utils, firebird-udf
Conflicts: firebird-server, firebird-utils, firebird-udf, …
So in reality the two packages do conflict with each other and there
is no real file conflict.
Sorry for not providing a patch, I have delayed filing this bug enough
already hoping to be able to find time for a patch.
Thanks,
dam
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lintian depends on:
ii binutils 2.22-6
ii bzip2 1.0.6-1
ii diffstat 1.55-2
ii file 5.11-1
ii gettext 0.18.1.1-7
ii intltool-debian 0.35.0+20060710.1
ii libapt-pkg-perl 0.1.26+b1
ii libc-bin 2.13-32
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.31-1+b2
ii libdpkg-perl 1.16.3
ii libemail-valid-perl 0.190-1
ii libipc-run-perl 0.91-1
ii libparse-debianchangelog-perl 1.2.0-1
ii libtimedate-perl 1.2000-1
ii liburi-perl 1.60-1
ii locales 2.13-32
ii locales-all [locales] 2.13-32
ii man-db 2.6.1-2
ii patchutils 0.3.2-1.1
ii perl [libdigest-sha-perl] 5.14.2-10
ii unzip 6.0-6
lintian recommends no packages.
Versions of packages lintian suggests:
ii binutils-multiarch <none>
ii dpkg-dev 1.16.3
ii libhtml-parser-perl 3.69-2
ii libtext-template-perl 1.45-2
ii man-db 2.6.1-2
ii xz-utils 5.1.1alpha+20110809-3
-- no debconf information
Reply to: