Tangential to this report, now all the output from %%posttrans commands in texlive are redirected to /dev/null, except:
%{_bindir}/texconfig-sys rehash 2> /dev/null

this is a la Fedora, I think the user doesn't gain much from seeing huge loads of lines printed. (ACK'ed by dmorgan).

So, you won't see the errors again, but they aren't fixed -> leaving the report open.

seems to be resolved her, closing ?

Not exactly resolved, the errors are still there, just not shown any more.

@ pterjan

Is this bug still there in current cauldron?

CC: (none) => marja11

see bug 1538 for possible fix (unsure if it's the same thing here)

CC: (none) => alien

(In reply to comment #4)
> @ pterjan
> 
> Is this bug still there in current cauldron?

ping?

Or in 1?

Thank you for your bug report.
We are sorry, but we recieved no answer to the questions above and we no longer maintain this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:WONTFIX

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

(In reply to comment #7)
> Thank you for your bug report.
> We are sorry, but we recieved no answer to the questions above and we no longer
> maintain this version of Mageia. Please upgrade to the latest version and

Huh?  I take it the above should reworded to say that the package
should be updated, rather then the distribution.

> reopen this bug against that version if this bug exists there.
> As a result we are setting this bug to CLOSED:WONTFIX

CC: (none) => davidwhodgins

(In reply to comment #7)
> Thank you for your bug report.
> We are sorry, but we recieved no answer to the questions above and we no longer
> maintain this version of Mageia. Please upgrade to the latest version and
> reopen this bug against that version if this bug exists there.
> As a result we are setting this bug to CLOSED:WONTFIX

Shouldn't this be assigned to maintainer? or is there no maintainer for this?

it's dmorgan, but to busy I guess......

Keywords: NEEDINFO => (none)
Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)
Assignee: bugsquad => dmorganec

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

@ dmorgan

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me in this report again ;)

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

2x no reply, closing as old.

Please reopen when needed and tell for which version(s) of Mageia this bug is still valid

If it is valid for both cauldron and Mageia 2, then please put MGA2TOO on the whiteboard and let version remain set to cauldron

Status: REOPENED => RESOLVED
Resolution: (none) => OLD