Re: SVN texlive (new) commit: r2484 - in texlive-new/trunk: all/debian texlive-base/debian texlive-bin/debian texlive-extra/debian texlive-lang/debian

[Frank Küster <frank@kuesterei.ch>]

Norbert Preining <preining@logic.at> wrote:

> On Mon, 19 Feb 2007, Frank Küster wrote:
>> still complains that it cannot find lamed for copying, although I
>> blacklisted it.  I didn't have time to investigate it, except that it
>
> See below ...
>
>
> Index: texlive-bin/debian/texlive-base-bin.links.dist
> ===================================================================
> --- texlive-bin/debian/texlive-base-bin.links.dist	(revision 2483)
> +++ texlive-bin/debian/texlive-base-bin.links.dist	(working copy)
> @@ -1,2 +1,5 @@
>  usr/share/man/man1/xdvi.1.gz usr/share/man/man1/xdvi-xaw.bin.1.gz
>  usr/share/man/man1/getnonfreefonts.1.gz usr/share/man/man1/getnonfreefonts-sys.1.gz
> +/usr/bin/pdftex /usr/bin/etex
> +/usr/bin/pdftex /usr/bin/pdfetex
> +/usr/bin/pdftex /usr/bin/pdflatex
>
> NO NO NO dh_link expects relative path names, not absolute ones!
> Please check this, but I am 99% sure.

It seems I hit the 1%:

,---- DH_LINK(1)
|
|  Be sure you do specify the full filename to both the source and
|  destination files (unlike you would do if you were using something
|  like ln(1)).
| 
|  dh_link will generate symlinks that comply with debian policy -
|  absolute when policy says they should be absolute, and relative
|  links with as short a path as possible. It will also create any
|  subdirectories it needs to to put the symlinks in.
`----

> +blacklist;file;bin/etex
> +blacklist;file;bin/pdfetex
> +blacklist;file;bin/pdflatex
>
> bin/[^/]*/etex

Thanks, I already found that out...

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)