Re: lmodern fonts and sarge
Florent Rougon <f.rougon@free.fr> schrieb:
> Works like a charm.
>
[...]
> Get:1 copy: sid/binary-all/ foo 1.1-1 [1756B]
> Get:2 copy: sid/binary-all/ bar 1.1-1 [1864B]
> Fetched 3620B in 0s (0B/s)
> (Reading database ... 79773 files and directories currently installed.)
> Preparing to replace foo 1.0-1 (using .../apt/archives/foo_1.1-1_all.deb) ...
> Unpacking replacement foo ...
> Preparing to replace bar 1.0-1 (using .../apt/archives/bar_1.1-1_all.deb) ...
> Unpacking replacement bar ...
Fine. It seems that dpkg now in which order to unpack packages. So it's
fine with lmodern.
And this means that in this other case, arabtex, we needn't be afraid of
doubled dist-upgrade runs, or doubled debconf phases. It will just go
smoothly if tetex Conflicts with arabtex <= 3.10-5.
I also noticed that the old lmodern package could have the same problem
as arabtex:
frank@alhambra:~/latex$ dpkg -l lmodern
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================-=====================-==========================================================
ii lmodern 0.86-4 Latin Modern Fonts
frank@alhambra:~/latex$ dpkg -L lmodern | grep dvips/config
/usr/share/texmf/dvips/config
frank@alhambra:~/latex$
Also in lmodern, it's a directory, not a link. I don't know how I could
even install it without dpkg complaining. Anyway, as soon as the new
lmodern package is in the archive, we should conflict with older
versions.
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: