[Bug 1093693] New: All texlive commands failing after update to texlive-2018
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693 Bug ID: 1093693 Summary: All texlive commands failing after update to texlive-2018 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: hiwatari.seiji@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After the recent update to texlive 2018, every latex execution fails with the following error. This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/TeX Live for SUSE Linux) (preloaded format=pdflatex) \write18 enabled. ---! /var/lib/texmf/web2c/pdftex/pdflatex.fmt made by different executable version (Fatal format file error; I'm stymied) This same error is thrown, no matter what implementation I use. (xelatex, lualatex, pdflatex, ...). All crash with more or less the same error message. I also was not able to find out, by what package the mentioned file is provided. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
Seiji Hiwatari
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c1
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c2
--- Comment #2 from Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c3
--- Comment #3 from Seiji Hiwatari
solver.cleandepsOnRemove = true
Yesterday evening, I used the time to install a dependency I will need when it starts working again. I used YaST2 to install the package "texlive-dtk". At the end of the installation, a small dialog showing a progressbar opened, reporting (I think) some script progress taking really long. After YaST2 finished the installation, TeX suddenly started working again. Might this be some problem in combination with packagekit? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c4
Dr. Werner Fink
I updated the system using the update-dialog in xfce4 (packagekit, I think?). The only thing I changed in the zypper-settings is:
solver.cleandepsOnRemove = true
Yesterday evening, I used the time to install a dependency I will need when it starts working again. I used YaST2 to install the package "texlive-dtk". At the end of the installation, a small dialog showing a progressbar opened, reporting (I think) some script progress taking really long. After YaST2 finished the installation, TeX suddenly started working again.
Might this be some problem in combination with packagekit?
Hmmm ... I've no idea what PackageKit does or use here but the %post as well as the %posttrans scriptlets should do work ... shouldn't they? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c5
Dominique Leuenberger
(In reply to Seiji Hiwatari from comment #3)
I updated the system using the update-dialog in xfce4 (packagekit, I think?). The only thing I changed in the zypper-settings is:
solver.cleandepsOnRemove = true
Yesterday evening, I used the time to install a dependency I will need when it starts working again. I used YaST2 to install the package "texlive-dtk". At the end of the installation, a small dialog showing a progressbar opened, reporting (I think) some script progress taking really long. After YaST2 finished the installation, TeX suddenly started working again.
Might this be some problem in combination with packagekit?
Hmmm ... I've no idea what PackageKit does or use here but the %post as well as the %posttrans scriptlets should do work ... shouldn't they?
PK uses the 'zypper up' algo to update packages. In most cases, this is 'ok', but with large stack updates, it often happens that legacy packages must be marked for removal. Only 'zypper dup' is able to cope with this complexity in Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c6
--- Comment #6 from Seiji Hiwatari
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c7
--- Comment #7 from Dominique Leuenberger
The update was 2220 packages in size, so that probably counts as large stack update, I guess?
size doesn't matter, complexity does. As a rule of thumb: only ever use zypper dup with tumbleweed; it can save you a lot of trouble -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c8
--- Comment #8 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c9
--- Comment #9 from Seiji Hiwatari
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693#c10
--- Comment #10 from Dominique Leuenberger
Is there a reason why packagekit does not user zypper dup instead of zypper up?
https://bugzilla.opensuse.org/show_bug.cgi?id=1030829 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693
David R
http://bugzilla.opensuse.org/show_bug.cgi?id=1093693 Bug 1093693 depends on bug 1030829, which changed state. Bug 1030829 Summary: PackageKit should use "zypper dup" instead of "zypper up" on Tumbleweed http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com