I know this is an old development thread, but since it is one of the first
results on Google:
How did you resolve this package conflict?
I tried several commands like
apt-get install -f
apt-get remove texlive*
apt-get purge texlive*
but none of them resolved the conflict.
My machine became
Hi Moritz
Try
apt-get -y purge tex-common # you may even have to dpkg -fP tex-common, if
that works didn't check the syntax now
dpkg --configure -a
apt-get -f install
apt-get -y dist-upgrade
Regards,
Jan
On 13 January 2015 at 15:54, Moritz Schappler schapp...@irt.uni-hannover.de
wrote:
I
Hi
How can I test it?
I did
apt-add-repository ppa:texlive-backports/ppa
apt-get update
apt-get source thailatex
apt-get install build-essential devscripts
tar xvzf thailatex_0.4.7-3~precise1.debian.tar.gz
apt-get build-dep thailatex
cd thailtex-0.4.7
vim debian/triggers
and I seem to be stuck
I just encountered this problem on a precise to quantal amd64 upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027661
Title:
thailatex and texlive-latex-base errors when upgrading from 12.04
From comment #7
postinst called with unknown argument 'triggered'
Wait.. The last sympthom was still the same. It's not about trigger
change, then. This problem is caused by tex-common generated postinst.
(See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648697 for more
info.)
It's
Ah, I see. tex-common in Precise is still 2.10. How can we get newer
one?
The latest version is 3.13. And thailatex requires tex-common (= 3.4).
How did the build pass in the first place?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi
On 3 October 2012 10:34, Theppitak Karoonboonyanan
t...@linux.thai.netwrote:
The latest version is 3.13. And thailatex requires tex-common (= 3.4).
How did the build pass in the first place?
I am testing texlive-backports on precise, though other users experience
this problem
on an
On Wed, Oct 3, 2012 at 4:38 PM, Jan Groenewald j...@aims.ac.za wrote:
On 3 October 2012 10:34, Theppitak Karoonboonyanan
t...@linux.thai.netwrote:
The latest version is 3.13. And thailatex requires tex-common (= 3.4).
How did the build pass in the first place?
I am testing
Hi
If I install that thailatex deb manually wiht dpkg,
then tex-common manages to finish configuring.
0 root@sudan:~#dpkg --configure -a
Processing triggers for tex-common ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Building
Hi
If I install that thailatex deb manually wiht dpkg,
then tex-common manages to finish configuring.
0 root@sudan:~#dpkg --configure -a
Processing triggers for tex-common ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Building
On Wed, Oct 3, 2012 at 7:01 PM, Jan Groenewald j...@aims.ac.za wrote:
If I install that thailatex deb manually wiht dpkg,
then tex-common manages to finish configuring.
You mean the deb from quantal? That's because it's built with
tex-common in quantal, not because tex-common in older system
Hi
On 3 October 2012 15:16, Theppitak Karoonboonyanan
t...@linux.thai.netwrote:
On Wed, Oct 3, 2012 at 7:01 PM, Jan Groenewald j...@aims.ac.za wrote:
If I install that thailatex deb manually wiht dpkg,
then tex-common manages to finish configuring.
You mean the deb from quantal? That's
On Wed, Oct 3, 2012 at 8:38 PM, Jan Groenewald j...@aims.ac.za wrote:
This says tex-common 3.13 :
https://launchpad.net/~texlive-backports/+archive/ppa
OK. That's more than sufficient.
Regards,
--
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/
--
You received this bug notification
Just seen this via Debian QA page.
So, it seemed the initial problem was caused by an old tex-common, as
fixed here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648697
Then, the last trigger problem after the rebuild should be caused by the
new texlive files being moved from
Hi
On 8 September 2012 11:59, Julian Taylor
jtaylor.deb...@googlemail.comwrote:
a rebuild was done in quantal to get the package xz compressed
is this still an issue?
It persists.
Processing triggers for thailatex ...
Customizing babel.sty...failed: system babel.sty does not exists.
confirmed in an 12.04 - 12.10 upgrade
it tries to trigger thailatex before tex is configured.
** Changed in: thailatex (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
a rebuild was done in quantal to get the package xz compressed
is this still an issue?
** Changed in: thailatex (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
17 matches
Mail list logo
