headers
Hamish Moffatt | 1 Nov 2005 03:46
Picon
Favicon

Bug#336713: tex-common: prompted about /etc/texmf/updmap.d/00updmap.cfg which I had not changed

Package: tex-common
Version: 0.8
Severity: normal

When tex-common 0.8 was installed during a routing apt-get upgrade, I was 
asked about my changes to /etc/texmf/updmap.d/00updmap.cfg. I have not
changed that file and indeed did not know that it existed until now.

The file must have been changed by some package or other.
The diff was as follows.

--- 00updmap.cfg.dpkg-old       2005-11-01 13:36:54.000000000 +1100
+++ 00updmap.cfg        2005-11-01 13:36:54.000000000 +1100
 <at>  <at>  -47,7 +47,7  <at>  <at> 
 # the fonts. The pdf files will get bigger, though.
 # Valid settings are true (download the fonts) or false (don't download
 # the fonts). Adobe recomments to embed all fonts.
-pdftexDownloadBase14 false
+pdftexDownloadBase14 true

 #
 # dvipdfmDownloadBase14
 <at>  <at>  -57,7 +57,7  <at>  <at> 
 # the fonts. The pdf files will get bigger, though.
 # Valid settings are true (download the fonts) or false (don't download
 # the fonts).
-dvipdfmDownloadBase14 false
+dvipdfmDownloadBase14 true

 ################################################################
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hamish Moffatt | 1 Nov 2005 03:50
Picon
Favicon

Bug#336714: tetex-base: asked about upgrade of previously non-existent conffile /etc/texdoctk/texdocrc

Package: tetex-base
Version: 3.0-10
Severity: normal

When upgrading to tetex-base 3.0-10, I was asked about my changes to
the file /etc/texdoctk/texdocrc through ucf. When I asked to see the
differences against my installed version, the diff was against /dev/null
so every line was new.

I did not delete the previous version of this file, and did not even
know it existed. This package or another either removed it or failed
to install it. However, I shouldn't have been asked about it.

thanks
Hamish

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages tetex-base depends on:
ii  dpkg                          1.13.11    package maintenance system for Deb
ii  tex-common                    0.8        Common infrastructure for using an
ii  ucf                           2.003      Update Configuration File: preserv
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Michlmayr | 1 Nov 2005 08:25

Bug#336743: doesn't break long \hrefs in DVI while PDF does

Package: tetex-bin
Version: 3.0-10.1
Severity: normal

I just upgraded to 3.0 and noticed that DVI does not break long \hrefs
across a line - while PDF does.  A simple test case is attached.

BTW, this new xdvi is cool.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages tetex-bin depends on:
ii  debconf [debconf-2.0]    1.4.58          Debian configuration management sy
ii  debianutils              2.15            Miscellaneous utilities specific t
ii  dpkg                     1.13.11.0.1     package maintenance system for Deb
ii  ed                       0.2-20          The classic unix line editor
ii  libc6                    2.3.5-7         GNU C Library: Shared libraries an
ii  libgcc1                  1:4.0.2-3       GCC support library
ii  libice6                  6.8.2.dfsg.1-10 Inter-Client Exchange library
ii  libkpathsea4             3.0-10.1        path search library for teTeX (run
ii  libpaper1                1.1.14-3        Library for handling paper charact
ii  libpng12-0               1.2.8rel-5      PNG library - runtime
ii  libsm6                   6.8.2.dfsg.1-10 X Window System Session Management
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Küster | 1 Nov 2005 10:08
Picon
Favicon

Bug#336713: tex-common: prompted about /etc/texmf/updmap.d/00updmap.cfg which I had not changed

Hamish Moffatt <hamish <at> debian.org> wrote:

> Package: tex-common
> Version: 0.8
> Severity: normal
>
> When tex-common 0.8 was installed during a routing apt-get upgrade, I was 
> asked about my changes to /etc/texmf/updmap.d/00updmap.cfg. I have not
> changed that file and indeed did not know that it existed until now.
>
[...]
> Mysterious conffile changes are one of my least favourite parts of Debian :-|

Same for me...  Thanks for reporting and for the diff.  Can you also
send the md5sum of the old version (the file is ucf-managed)?

Regards, Frank
--

-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Permalink | Reply | 0 comments |
headers
Frank Küster | 1 Nov 2005 10:09
Picon
Favicon

Bug#336714: tetex-base: asked about upgrade of previously non-existent conffile /etc/texdoctk/texdocrc

Hamish Moffatt <hamish <at> debian.org> wrote:

> Package: tetex-base
> Version: 3.0-10
> Severity: normal
>
> When upgrading to tetex-base 3.0-10, I was asked about my changes to
> the file /etc/texdoctk/texdocrc through ucf. When I asked to see the
> differences against my installed version, the diff was against /dev/null
> so every line was new.
>
> I did not delete the previous version of this file, and did not even
> know it existed. This package or another either removed it or failed
> to install it. However, I shouldn't have been asked about it.

Was this an upgrade from 3.0-9 or from 2.0.2c-9?

TIA, Frank
--

-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Permalink | Reply | 0 comments |
headers
Hamish Moffatt | 1 Nov 2005 12:51
Picon
Favicon

Bug#336714: tetex-base: asked about upgrade of previously non-existent conffile /etc/texdoctk/texdocrc

On Tue, Nov 01, 2005 at 10:09:36AM +0100, Frank Küster wrote:
> Hamish Moffatt <hamish <at> debian.org> wrote:
> 
> > Package: tetex-base
> > Version: 3.0-10
> > Severity: normal
> >
> > When upgrading to tetex-base 3.0-10, I was asked about my changes to
> > the file /etc/texdoctk/texdocrc through ucf. When I asked to see the
> > differences against my installed version, the diff was against /dev/null
> > so every line was new.
> >
> > I did not delete the previous version of this file, and did not even
> > know it existed. This package or another either removed it or failed
> > to install it. However, I shouldn't have been asked about it.
> 
> Was this an upgrade from 3.0-9 or from 2.0.2c-9?

2.0.2c-9.

Thanks,
Hamish
-- 
Hamish Moffatt VK3SB <hamish <at> debian.org> <hamish <at> cloud.net.au>

--

-- 
To UNSUBSCRIBE, email to debian-tetex-maint-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Hart | 1 Nov 2005 15:15
Picon
Picon
Favicon

Bug#336743: try the breaklinks option

If you use the breaklinks option of hyperref this should fix this problem,
but *might* cause others, especially of links break across pages.

Rob

This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.
Permalink | Reply | 0 comments |
headers
Robert Hart | 1 Nov 2005 15:30
Picon
Picon
Favicon

Bug#336807: xdvi: crashes with (breaklinks) hyperrefs

Package: tetex-bin
Version: 3.0-10.1
Severity: normal

I have experience srgfaults with xdvi on a file containing
hyperrefs. The page that causes the crash contains a (landscape)
table, which happens to contain links (but I don't believe they are
part of the problem. The following page starts with a hyperlink (due
to a \cite). I'm guessing that this link has been broken across
several pages (due to the floatpage in between.

I reported this bug to xdvik-ja (as that is where I discovered it) but
it applies to tetex-bin's version too. See bug 336783, for debugging
info, which I hope is relevant to the tetex codebase too.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.6
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages tetex-bin depends on:
ii  debconf [debconf-2.0]    1.4.58          Debian configuration management sy
ii  debianutils              2.15            Miscellaneous utilities specific t
ii  dpkg                     1.13.11.0.1     package maintenance system for Deb
ii  ed                       0.2-20          The classic unix line editor
ii  libc6                    2.3.5-7         GNU C Library: Shared libraries an
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Küster | 1 Nov 2005 16:00
Picon
Favicon

Bug#336743: try the breaklinks option

Robert Hart <enxrah <at> nottingham.ac.uk> wrote:

> If you use the breaklinks option of hyperref this should fix this problem,
> but *might* cause others, especially of links break across pages.

Indeed - this is not a LaTeX/hyperref/whatever bug, it is a limitation
of the different ways to process files.  If you use latex/dvips/ps2pdf
(or any other gs-based way to create pdf files), you'll not get a
functional link to http://www.debian.org with breaklinks=true; I don't
know about latex/dvips/distiller.  Without the breaklinks option,
dvips/ps2pdf can produce working hyperlinks.  And pdftex can do it with
or without it.

Regards, Frank

--

-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Permalink | Reply | 0 comments |
headers
Richard Lewis | 1 Nov 2005 16:10
Picon

Re: Bug#336743: doesn't break long \hrefs in DVI while PDF does

Martin Michlmayr <tbm <at> cyrius.com> writes:

> I just upgraded to 3.0 and noticed that DVI does not break long \hrefs
> across a line - while PDF does.  A simple test case is attached.

Adding "breaklinks=true" to the hyperref options fixes this.

>From the hyperref manual, section 3.2:

  breaklinks 	 boolean 	 false 	

  Allows link text to break across lines; since this cannot be
  accommodated in PDF, it is only set true by default if the pdftex
  driver is used. This makes links on multiple lines into different PDF
  links to the same target.

Maybe this is a "hyperref should default to breaklinks=true for all
drivers" wishlist?
Permalink | Reply | 0 comments |

Gmane