Package: musixtex
Version: 1:0.112.2-3
Followup-For: Bug #455133

Hi!

I've had a similar bug for latex-cjk-chinese-arphic and 
latex-cjk-japanese-wadalab.

The reason is simple: dh_installtex has now a default priority of 20.  This 
means that  /etc/texmf/updmap.d/10musixtex.cfg (MD5SUM 
a756ed5611331524655d361ec052e359) is now obsolete according to "dpkg -s".

dpkg doesn't automatically remove obsolete conffiles, so Norbert Preining, one 
of the Debian TeX maintainers, has suggested the following:

> Yes, you should remove the 10*.cfg files, they are obsolete. If you want
> to be *very* picky (not that I recommend it) you could try to merge the
> changes from the 10* into the 20*.
> 
> In the preinst you could do:
> - if the md5sum of the 10*.cfg file is the one of the 10*.cfg file AS
>   SHIPPED then just remove it.
> - if the md5sums differ (i.e. when the admin has changed the file) then
>   either warn the user or replace 20*.cfg with 10*.cfg. But that should 
>   be done only when upgrading from a version with 10* to 20*, NOT when
>   doing the upgrade from a 20* version to a 20* version because 
>   changes to the 20* version could get lost.


Best regards


/Danai SAE-HAN


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-hermes (PREEMPT)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages musixtex depends on:
ii  libc6                      2.7-5         GNU C Library: Shared libraries
ii  perl                       5.8.8-12      Larry Wall's Practical Extraction 
ii  tex-common                 1.10          common infrastructure for building
ii  texlive-base               2007-13       TeX Live: Essential programs and f
ii  texlive-base-bin           2007.dfsg.1-2 TeX Live: Essential binaries

musixtex recommends no packages.

-- no debconf information



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

Reply via email to