somewhere along the way we seem to have made this issue disappear, and
there seems to be no issues with the hardware. as for the logs you refer
to I'm not sure what you mean about not getting them as you reference the
files directly.
Eric
On Fri, Jun 6, 2014 at 1:28 AM, Hilmar Preusse
On Sun, 08 Jun 2014, Eric Fort wrote:
somewhere along the way we seem to have made this issue disappear, and
Does that mean the bug is not occurring anymore?
In this case I will close the bug as there is no way
to track it down.
there seems to be no issues with the hardware. as for the logs
yes the bug has (unfortunately in this case) been squashed and is no longer
happening. Hardware seems solid.
Eric
On Sun, Jun 8, 2014 at 5:29 AM, Norbert Preining prein...@logic.at wrote:
On Sun, 08 Jun 2014, Eric Fort wrote:
somewhere along the way we seem to have made this issue
On 06.06.14 Norbert Preining (prein...@logic.at) wrote:
Hi,
root@beaglebone:~# diff log2 log3
I didn't get the logs ...
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=99;filename=logs.zip;att=2;bug=750496
The mail didn't make it to the list.
H.
--
sigmentation fault
signature.asc
root@beaglebone:/var/lib/dpkg/info# dpkg-reconfigure texlive-xetex
+ TEXMFTREES=/usr/share/texmf /var/lib/texmf
+ FULLTEXMFTREES=/usr/share/texmf /var/lib/texmf /usr/share/texlive/texmf
/usr/share/texlive/texmf-dist
+ update-updmap --quiet
+ update-language
+ update-fmtutil
+
On 05.06.14 Eric Fort (eric.f...@gmail.com) wrote:
Hi,
=
(/usr/share/texlive/texmf-dist/tex/latex/base/preload.cfg
(/usr/share/texlive/texmf-dist/tex/latex/base/preload.ltx)) page nos.,
x-ref,
environments, center, verbatim, math definitions, boxes,Killed
unless you already know the answer, it's not a stupid question. Am I
correct that you are asking if 'dpkg-reconfigure texlive-xetex' always
terminates at the same place? or are you asking about the long many
package apt-get install referenced earlier? I believe that the answer to
both is yes,
On 05.06.14 Eric Fort (eric.f...@gmail.com) wrote:
Hi,
unless you already know the answer, it's not a stupid question. Am
I correct that you are asking if 'dpkg-reconfigure texlive-xetex'
always terminates at the same place?
I'd like you to run the following:
fmtutil-sys --all --cnffile
On 05.06.14 Eric Fort (eric.f...@gmail.com) wrote:
Hi,
root@beaglebone:~# diff log2 log3
root@beaglebone:~# diff log2 log4
root@beaglebone:~# diff log2 log5
root@beaglebone:~# diff log2 log6
root@beaglebone:~# diff log2 log7
root@beaglebone:~# diff log2 log8
root@beaglebone:~# diff log2
root@beaglebone:~# diff log2 log3
I didn't get the logs ...
So, all these log files are equal and the xetex call is always
successful. Exactly the call, which fails in case of an installation.
Strange
I have to says, there i something fishy on that system. Did you
consider to check
Yes, but instead put
set -x
in there and then send me the full output (lots!) of the dpkg run.
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live
modified that allows things to run:
root@beaglebone:/var/lib/dpkg/info# cat texlive-xetex.postinst
#!/bin/sh
exit 0
set -e
# Automatically added by dh_installtex
##
## postinst-tex
##
## postinst snippets for everything TeX related (mktlsr, hyphenation
## patterns, formats, font maps)
##
##
On Wed, 04 Jun 2014, Eric Fort wrote:
modified that allows things to run:
Yeah, sure, adding
exit 0
helps.
Please *remove* the
exit 0 line
Add a
set -x
line
(yeah, then there are two set lines. You can also write
set -e -x
if you prefer)
Norbert
script as it is now (original except -x added to set line)
Eric_Admin@INSPIRON1545 ~
$ ssh 192.168.1.5 -l root
Debian GNU/Linux 7
BeagleBoard.org BeagleBone Debian Image 2014-05-14
Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
Last login: Wed Jun 4 05:53:36 2014 from
Then please run
dpkg-reconfigure texlive-xetex
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live Debian Developer
GPG: 0x860CDC13 fp: F7D8
Package: texlive-xetex
Version: 2012.20120611-5
Severity: grave
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
(marked grave, as it's uninstallable as is and crashes the install of other
packages being installed simultaniously)
* What led up to the
On 03.06.14 Eric Fort (eric.f...@gmail.com) wrote:
Hi,
fmtutil: running `xetex -ini -jobname=xelatex -progname=xelatex -etex
xelatex.ini' ...
This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012/Debian)
(INITEX)
restricted \write18 enabled.
Killed
Could you run
I did not see a core file but I will look again. nope, no core file.
here's the session running the command as a normal user:
debian@beaglebone:~$ xetex
-ini
This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012/Debian)
(INITEX)
restricted \write18
enabled.
**
Please type the name of your
tags 750496 + unreproducible more-info
severity 750496 normal
thanks
fmtutil: running `xetex -ini -jobname=xelatex -progname=xelatex -etex
xelatex.ini' ...
This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012/Debian)
(INITEX)
restricted \write18 enabled.
Killed
AGAIN. IT'S THE INSTALLATION THAT'S THE ISSUE, *NOT THE XETEX
BINARY* dpkg is crashing on this one and only pkg, **NOT** the xetex
binary itself! follow along below:
Setting up texlive-xetex (2012.20120611-5) ...
Running mktexlsr. This may take some time... done.
Building
Hi
On Tue, 03 Jun 2014, Eric Fort wrote:
AGAIN. IT'S THE INSTALLATION THAT'S THE ISSUE, *NOT THE XETEX
BINARY* dpkg is crashing on this one and only pkg, **NOT** the xetex
binary itself! follow along below:
Wrong.
fmtutil: running `xetex -ini -jobname=xelatex
(Norbert)
my apologies on my last reply. I am grateful for your assistance and also
somewhat frustrated. M y apologies if that shows a bit as it's not
directed at you I think we both just want things to work. It's also a
bit confusing in that it's stating that dpkg returned 1 (an error) and
On Tue, 03 Jun 2014, Eric Fort wrote:
packaging works so I defer to you. Here's the command, run as root in a
single line and the output:
Ok, so it works. Strange.
Can you run
dpkg --configure -a
as root?
Norbert
before I ' dpkg --configure -a' should I remove the exit 0 I placed at
the top of the postinstall script such that it would continue past the
error?
On Tue, Jun 3, 2014 at 8:55 PM, Norbert Preining prein...@logic.at wrote:
On Tue, 03 Jun 2014, Eric Fort wrote:
packaging works so I defer to
24 matches
Mail list logo