Package: libdc0
Version: 0.3.2-1
Severity: serious
Justification: Policy 7.3

"A Conflicts entry should almost never have an "earlier than" version
clause. This would prevent dpkg from upgrading or installing the package
which declared such a conflict until the upgrade or removal of the
conflicted-with package had been completed."

Package: libdc0
Version: 0.3.7-1
Conflicts: dcgui-qt (<< 0.3.3)

Package: dcgui-qt
Version: 0.3.2-2
Depends: ... libdc0 (>= 0.3.1) ...

It is now impossible to install dcgui-qt because it depends on libdc0,
which in turn conflicts with it. Policy states that versioned conflicts
with less than clauses are horribly broken - dpkg will not be able to
upgrade libdc0 and dcgui-qt in the same run, because dcgui-qt will need
to be FULLY UNINSTALLED (as is the definition of Conflicts) before libdc0
can be upgraded, so you will need to invoke dpkg once to remove
dcgui-qt, and then again to install libdc0 and upgrade dcgui-qt.

If the reason for adding this conflict is that libdc0 has broken binary
compatibility, then the shlibs file of libdc-dev should make the
resultant libdc0 dependency more version-specific. This is not the
correct way to deal with breaking ABIs.

Regards,
Rob

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-alpha2
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages libdc0 depends on:
ii  libbz2-1.0                  1.0.2-5      high-quality block-sorting file co
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libgcc1                     1:3.4.3-9    GCC support library
ii  libssl0.9.7                 0.9.7e-3     SSL shared libraries
ii  libstdc++5                  1:3.3.5-8    The GNU Standard C++ Library v3
ii  libxml2                     2.6.16-2     GNOME XML library
ii  zlib1g                      1:1.2.2-4    compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to