Your message dated Thu, 1 Feb 2018 15:48:47 +0800
with message-id <[email protected]>
and subject line Not a bug
has caused the Debian Bug report #888101,
regarding libpinyin13-dev ships same files as libpinyin7-dev without Conflicts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
888101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888101
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpinyin13-dev
Version: 2.1.0-1~exp3
Severity: serious
libpinyin13-dev and libpinyin7-dev both include these files:
/usr/lib/x86_64-linux-gnu/libpinyin.a
/usr/lib/x86_64-linux-gnu/libpinyin.so
/usr/lib/x86_64-linux-gnu/pkgconfig/
/usr/lib/x86_64-linux-gnu/pkgconfig/libpinyin.pc
I think you need to add Conflicts: libpinyin7-dev.
See Debian Policy § 7.4
https://www.debian.org/doc/debian-policy/#conflicting-binary-packages-conflicts
By the way, why haven't you uploaded the new libpinyin to unstable yet?
Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
The current control for libpinyin13-dev is:
Package: libpinyin13-dev
Provides: libpinyin-dev
Conflicts: libpinyin-dev
And after checking the policy, I think it falls to the following case
described in policy:
Conflicts should be used
..
* in conjunction with Provides when only one package providing a given
virtual facility may be unpacked at a time (see Virtual packages - Provides),
So I think we don't need to Conflicts libpinyin7-dev.
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
--- End Message ---
