Bug 18602

Summary:	Texlive scriplet failed on upgrade
Product:	Mageia	Reporter:	Thomas Spuhler <thomas>
Component:	RPM Packages	Assignee:	Bruno Cornec <bruno>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	bruno, marja11, pkg-bugs
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	texlive-20130530-29.mga6.x86_64)	CVE:
Status comment:

Description Thomas Spuhler 2016-06-01 19:35:30 CEST

Description of problem:

warning: %posttrans(texlive-20130530-29.mga6.x86_64) scriptlet failed, exit status 1
ERROR: 'script' failed for lib64ptexenc1-20130530-28.mga6.x86_64
Version-Release number of selected component (if applicable):

Comment 1 Marja Van Waes 2016-06-01 20:17:04 CEST

Assigning to maintainer, who might be MIA. So also CC'ing pkg-bugs@ml

CC: (none) => marja11, pkg-bugs
Assignee: bugsquad => pmdenielou

Marja Van Waes 2016-06-01 20:17:21 CEST

Summary: scriplet failed on upgrade => Texlive scriplet failed on upgrade

Comment 2 David Walser 2016-06-03 23:21:38 CEST

I don't understand the reference to libptexenc1, as that doesn't have any scriplets.

For the texlive %posttrans, I doubt it's having an issue with the rm, but maybe one of the other commands exits with an error.

It's a horrible scriplet BTW, using predictable filenames in /tmp (big no-no):
rm -f %{texmfdir}/ls-R %{texmfdistdir}/ls-R %{texmfconfdir}/ls-R
%{_bindir}/texhash > /tmp/texlive-texhash.log 2>&1
%{_bindir}/updmap-sys --syncwithtrees > /tmp/texlive-updmap-sys.log 2>&1
export TEXMF=/usr/share/texmf-dist
export TEXMFCNF=/usr/share/texmf-dist/web2c
export TEXMFCACHE=/var/lib/texmf
%{_bindir}/mtxrun --generate > /tmp/texlive-mtxrun.log 2>&1
%{_bindir}/fmtutil-sys --all &> /tmp/texlive-fmtutil-sys.log 2>&1

Comment 3 Thomas Spuhler 2016-06-03 23:31:59 CEST

I don't know where it comes from. This si the first upgrade showing this bug. It was a different before.

Comment 4 Bruno Cornec 2016-10-01 02:33:06 CEST

This should be fixed with the 20160523 version. please test again (release -4 on its way).

Status: NEW => ASSIGNED
CC: (none) => bruno
Assignee: pmdenielou => bruno

Comment 5 Marja Van Waes 2017-03-29 07:32:14 CEST

(In reply to Bruno Cornec from comment #4)
> This should be fixed with the 20160523 version. please test again (release
> -4 on its way).

No one complained it did not get fixed, so the fix must have been good. Closing.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED