Re: teTeX and sarge-release
Hilmar Preusse <hille42@web.de> schrieb:
> Hi,
>
> In the Last Debian Weeky News I found a paragraph, which alarmed me a
> little bit.
Grab your towel and don't panic!
> <quote>
> Sarge Release Progress. Nathanael Nerode [37]reported about the
> status of several important packages for sarge (glibc, GCC, GNOME 2,
> KDE 3, debian-installer, Apache etc.). Most packages are in a
> relative good state, but some still require a certain amount of work.
> He writes that if issues in a limited number of packages were dealt
> with, sarge could probably be released for i386 in about two weeks.
>
> 37. http://lists.debian.org/debian-devel-0401/msg00264.html
> </quote>
>
> Two weeks can be a very short time.
I don't know what role Nathanael has. But in any case, if you read his
whole message, you'll notice that this only related to i386 (and we
won't release sarge for only one architecture). Generally he says
,----
| a big push could get sarge released within a month or two, no problem
`----
I severely doubt that one month would be sufficient. Still you are
correct that we should be prepared for the release.
> There are a few bugs in teTeX,
> which could have that tag pending and which could be closed, without
> breaking anything. I would like to have these uploaded to unstable
> ASAP, so that stuff has still enough time to migrate into testing
> before release. I think of:
>
> - texdoc manpage update (just another patch attached). Remark about
> that: There is a files-section in the original manpge, which tells
> me that there is a config file for texdoc called texdoc.cnf. I have
> doubt, that this is true.
$ grep -i cnf `which texdoc`
$
> - #213310
Let's do it; has anybody really tried to find the packages that call
update-updmap?
> - #223729
combining this patch, your corrections and my patch for 227203 this
gives a new patch to README.Debian. I'll try to include an attachment in
the middle of a mail for the first time, tell me whether this makes
problems.
--- tetex-bin-2.0.2/debian/README.Debian.orig Fri Jan 16 09:52:26 2004
+++ tetex-bin-2.0.2/debian/README.Debian Fri Jan 16 09:52:35 2004
@@ -3,18 +3,44 @@
TeX binaries built from teTeX-src-*.tar.gz
+Note on dvips:
+=============
+
+Per default, dvips is in secure mode and won't execute shell commands
+in \special commands, like backticks in \DeclareGraphicsRule etc. To
+enable this, change "z1" to "z0" in /etc/texmf/dvips/config.ps (second
+entry).
+
Note on update-texmf:
====================
-- to customize texmf.cnf, create an appropriate file (or files) in
- /etc/texmf/texmf.d/ and then run "update-texmf". This will generate
- desired texmf.cnf under /var/lib/texmf/web2c (not /etc/texmf !) for you.
- You should name a file like "40macros.cnf"; numeral will decide the order
- to be read with update-texmf so it is very important.
+- The TeX binaries are built to look for texmf.cnf (the master config
+ file for TeX and MetaFont) in /usr/share/texmf/web2c/texmf.cnf.
+ Since /usr/share/texmf/web2c/ is a symbolic link to
+ /var/lib/texmf/web2c/, the file /var/lib/texmf/web2c/texmf.cnf is
+ used. The Debian packaging of TeX includes a mechanism for
+ constructing texmf.cnf from a collection of files under
+ /etc/texmf/texmf.d/. To customize texmf.cnf while retaining the
+ Debian-supplied configuration, create an appropriate file (or files)
+ in /etc/texmf/texmf.d/ and then run "update-texmf". This will
+ generate the desired texmf.cnf under /var/lib/texmf/web2c (not
+ /etc/texmf !) for you.
+
+ You should name your customization file something like "40macros.cnf";
+ the leading numerals will decide the order in which configuration
+ fragments will be assembled by update-texmf, so it is very important
+ to place your customizations in an appropriate place in the sequence.
+
+- If a file /etc/texmf/texmf.cnf is found when tetex-bin is installed,
+ you will be asked whether to preserve your modified texmf.cnf rather
+ than adopt the Debian configuration approach. If you opt to stick
+ with your existing configuration, a symbolic link will be created
+ from /var/lib/texmf/web2c/texmf.cnf to your /etc/texmf/texmf.cnf.
+ So long as /var/lib/texmf/web2c/texmf.cnf is a symbolic link,
+ update-texmf will refrain from overwriting it.
-- how to preserve your modified texmf.cnf
- your modified version would be reserved in /etc/texmf/texmf.cnf
- so if you want to preserve your modifications you should do the following
- steps manually, sorry for that.
+ If you want to adopt the /etc/texmf/texmf.d/ mechanism after having
+ chosen to preserve your modifications during installation, you should
+ do the following steps manually (sorry for the inconvenience):
* compare the new generated texmf.cnf with texmf.cnf.dpkg-old
* extract really necessary modifications and write them in some file(s)
Note that 227302 also suggests a patch to config.ps, e.g. as follows:
--- tetex-base-2.0.2/texmf/dvips/config/config.ps.orig Mon Jan 12 09:33:21 2004
+++ tetex-base-2.0.2/texmf/dvips/config/config.ps Mon Jan 12 09:32:26 2004
@@ -7,8 +7,8 @@
% to determine this number. (It will be the only thing printed.)
m 3500000
-% Execution of external programs is disabled by default. Set
-% to z0 if you want backticks in \special commands enabled.
+% Execution of external programs is disabled by default ("secure mode").
+% Set to z0 if you want backticks in \special commands enabled.
z1
% How to print, maybe with lp instead lpr, etc. If commented-out, output
> All these bugs belong to tetex-bin (AFAICS), so no new tetex-base is
> needed.
The second patch for 227302 (explanation in config.ps) would affect
tetex-base. But we can safely delay this, I would say.
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: