[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#709038: marked as done (new luatex breaks old context/mtxrun)



Your message dated Mon, 20 May 2013 15:18:40 +0000
with message-id <E1UeRrE-0002et-HU@franck.debian.org>
and subject line Bug#709024: fixed in luatex 0.76.0-2
has caused the Debian Bug report #709024,
regarding new luatex breaks old context/mtxrun
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
709024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709024
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 4.03
Severity: grave


Coin,

This is not the same bug as #709025.

As texlive-lang is in NEW and textile-doc is not available for the 2013.20130520 version i did an upgrade instead of a dist-upgrade to avoid having them removed.

It gives the following result:
Setting up tex-common (4.03) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time...
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.968prcQ9
Please include this file if you report a bug.

# cat /tmp/mtxrun.968prcQ9
/usr/bin/mtxrun:15228: attempt to index field 'loaders' (a nil value)

Maybe this is due to 2012 packages still being around, but in this case either dependencies are not tight enough, either there's missing Breaks.

Regards.

--
Marc Dequènes

--- End Message ---
--- Begin Message ---
Source: luatex
Source-Version: 0.76.0-2

We believe that the bug you reported is fixed in the latest version of
luatex, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 709024@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining <preining@debian.org> (supplier of updated luatex package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 20 May 2013 22:17:04 +0900
Source: luatex
Binary: luatex
Architecture: source amd64
Version: 0.76.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian TeX Maintainers <debian-tex-maint@lists.debian.org>
Changed-By: Norbert Preining <preining@debian.org>
Description: 
 luatex     - next generation TeX engine
Closes: 709024
Changes: 
 luatex (0.76.0-2) unstable; urgency=low
 .
   * break against older context (Closes: #709024)
Checksums-Sha1: 
 6030c4421f159dcbcf8177a6daabf09ac515c0ed 1487 luatex_0.76.0-2.dsc
 5190a16402e077dcc88341842878b80189373cb1 16914 luatex_0.76.0-2.debian.tar.gz
 3c8977e14fa7e8b10a7aeabcce1525872539f356 3726834 luatex_0.76.0-2_amd64.deb
Checksums-Sha256: 
 3f2d59e833579641070ef10be0907b5b7759d9b64fc56d7b97b9c4e1abbb7933 1487 luatex_0.76.0-2.dsc
 e2af893f543e15743130a7f3080713d3ebb15fff8cb9bf21d8d197cf62645933 16914 luatex_0.76.0-2.debian.tar.gz
 d71da21e8033f3131bc78ea49070512f9ac5d6d1f99bf21b1e70c64b301d00f0 3726834 luatex_0.76.0-2_amd64.deb
Files: 
 2060ae20e04b06f88617f7e41f7a4892 1487 tex optional luatex_0.76.0-2.dsc
 8a4bb5a10bd3f9cc0e5eac99de197e38 16914 tex optional luatex_0.76.0-2.debian.tar.gz
 f8578696e798e7b133140ab2356597af 3726834 tex optional luatex_0.76.0-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQFRmiX80r9KownFsJQRAggqAJ444rbahhZYgT23VwnGNApCTrQVMgCgids6
1tf7AAMy6dT6rpCv6JxxVhU=
=Rkb+
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: