David Liontooth wrote: > Package: unicode-data > Version: 4.1.0-1 > Severity: normal > > > When installing unicode-data, my console-common and console-data get removed: > > The following packages will be REMOVED: > console-common console-data > The following NEW packages will be installed: > unicode-data > 0 upgraded, 1 newly installed, 2 to remove and 38 not upgraded. > Remv console-common [0.7.59] > Remv console-data [20060609] > Inst unicode-data (4.1.0-1 Debian:unstable) > Conf unicode-data (4.1.0-1 Debian:unstable) > > Surely this isn't intended -- and couldn't the effect be rather dramatic? (I > did a simulation install only.) > > The Conflicts says console-data (<< 2:1.0-1), but console-data versioning is > now using a date string, 20060609. > > Dave > > > This is intended - I have split off unicode-data from the console-data package, and placed it in a new package 'unicode-data'. Today I am uploading a new console-data version 2:1.0-1, which resolves this conflict. (the change is in subversion already)
I hadn't expected someone to jump on the new unicode-data package so fast! > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.16 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Regards Alastair -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
