Hilmar Preusse [EMAIL PROTECTED] wrote:
Sure. Here we go.
Thanks.
As you can see, when the second debug snippet is written, Make has
already taken the wrong decision of rebuilding debian/rules (the fact
that the snippet is printed means that Make is running the commands to
update
Hi,
Frank Lichtenheld [EMAIL PROTECTED] wrote:
tetex-base contains /usr/share/doc/texmf/doc as a symlink.
I suppose you mean /usr/share/texmf/doc.
In woody the package ivritex contained this as a directory.
This is a bug that was partially fixed in ivritex 1.0-3 and finally
fixed in version
Julian Gilbey [EMAIL PROTECTED] wrote:
In woody, tetex-base already contained this as a symlink, so surely it
was an RC issue all that time ago already?
Yes. I think the problem was not noticed before because if tetex-base is
unpacked before ivritex, this sentence of Policy applies:
A
Hi,
Kurt Roeckx [EMAIL PROTECTED] wrote:
Your package is failing to build in experimental. It
seems to be stuck in an endless loop doing this over and
over again:
[...]
Here is my (partial) understanding of the problem:
debian/rules contains a rule that causes it to be remade (which is
Kurt Roeckx [EMAIL PROTECTED] wrote:
Note that I'm doing this on a 2.6 kernel, which has sub-second
timestamps on files, which might be why you're not seeing it.
Good to know (I'm working with a 2.4 kernel). Now, I have a possible
explanation:
Suppose we start debian/rules with the rules file
tags 306586 + confirmed
thanks
Hi,
I can reproduce the problem, both with teTeX 2 and teTeX 3. However, I
don't know whom the bug should be forwarded to; babel or hyperref
maintainers?
[ I used 'frenchb' instead of 'english' as the alternate option for
babel, so it seems the problem only
severity 306089 wishlist
thanks
IMHO, this is at most wishlist. I let it to the more regular teTeX
maintainers to decide if they want to forward this request to
upstream...
--
Florent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Hi,
Petr Tesarik [EMAIL PROTECTED] wrote:
The same happens when I run updmap with a fresh installation of
tetex-base.
But /usr/share/texmf/dvips/tetex/bsr-interpolated.map is shipped in
tetex-extra, not tetex-base.
What happens is that the default file
tags 304294 + experimental
thanks
Hi,
Tobias Hilbricht [EMAIL PROTECTED] wrote:
Trying to install additional fonts into the tetex-system according to the
manual given in /usr/share/doc/tetex-bin/README.Debian.gz does not work
because the map files are not distributed properly:
You're
Hi,
Description : Live365, local, Xiph and 'pythonÂ? (various) plugins
for streamtuner.
It seems to me that all of these are in the streamtuner package,
therefore this RFP should be closed, right?
--
Florent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Hi,
I've worked a little bit on the packaging. Except the two following
entries:
* Remove the dependencies (in debian/control) on pythonX.Y-gd because
these packages don't exist in Debian and I don't intend to use this
backend.
* Don't apply Vittorio's patch to the default
Chirik [EMAIL PROTECTED] wrote:
Is this a packaging rule or an issue with updmap? The assumption I used is
that if it's empty, it's probably not being used by another package, but I
don't know if that's safe or not.
It is a packaging (and system administration) rule. If a file or
Florent Rougon [EMAIL PROTECTED] wrote:
I think that version 0.98 is not suitable for unstable (without several
fixes). First, the problem with lmtt not being really monospaced is
*not* solved.
0.982 is out there and the fontdimens in the lmtt TFM files are still
wrong. Not to mention
Hi,
Frank Küster [EMAIL PROTECTED] wrote:
I don't grok the perl script completely; but anyway: I has not changed
between 2.0.2 and 3.0, and it works in 2.0.2. So probably xdvi has
changed.
I am unable to debug the Perl script, but I see another possibility: due
to the error message you
Hi,
Frank Küster [EMAIL PROTECTED] wrote:
I hope it is safe to use something like test `id -u` = 0. In this
I would use '-eq' instead of '=', even though '=' looks unlikely to
break anything before long.
More importantly, maybe you could add a warning when UID 0 is detected
but the
Frank Küster [EMAIL PROTECTED] wrote:
Bonjour Florent,
Salut !
ftp://bop.eps.gda.pl/pub/lm/0info098.txt
Good news; thank you very much for the notice. I'll be busy for a few
days but will look at it in about a week, or a bit less.
Regards,
--
Florent
--
To UNSUBSCRIBE, email to [EMAIL
[EMAIL PROTECTED] (Frank Küster) wrote:
He said that he just didn't know that this was sufficient. Therefore, if
you have checked that it fixes the problem, and does it for all font
shapes, yours is better.
Well, the LaTeX Companion (1st edition, p. 200) clearly documents that
it should work:
Hi,
So, according to Walter, it is not worth the risk or lack of
traceability patching the TFM files, because very few people would be
using plain TeX with T1 encoding and these fonts, and he expects Hans
Hagen to write a ConTeXt-specific patch if he cared about the problem,
etc.
All in all, it
[EMAIL PROTECTED] (Frank Küster) wrote:
You are right, this is a drawback. We can still give lmodern.sty a new
version number, even if it is in fact the tfm files that have changed,
to ease debugging a little.
Yes.
Moreover, the new documents would not compile
on non-Debian systems where
[EMAIL PROTECTED] (Frank Küster) wrote:
Hallo Florent,
Hallo, and thanks for the report.
Maybe this can be changed in the afm files, and the tfm files
regenerated with afm2tfm?
I wouldn't feel comfortable with that. I would prefer using tftopl on
the tfm files, modifying the fontdimens in
[EMAIL PROTECTED] (Frank Küster) wrote:
Ralf Stubner has suggested a different approach in de.comp.text.tex: We
could add the corrected tfm files with names changed, and patch
lmodern.sty to use these changed tfm files. plain TeX users would have
to do it themselves, but they could do it.
Ludovic Courtes [EMAIL PROTECTED] wrote:
Hi,
Hi,
The `lmodern' currently depends on TeX which is unfortunate since other
packages (such as `lout') would benefit from being able to use the Latin
Modern fonts without having to install several megabytes of TeX related
software.
Right, I
301 - 322 of 322 matches
Mail list logo
