Ask Your Question
2

Scriptlet Output

asked 2014-02-12 17:05:48 -0500

fedie gravatar image

updated 2014-02-13 13:31:22 -0500

mether gravatar image

Fresh install of fedora 20. I ran 'sudo yum update', the packages updated successfully but when I checked the transaction with "sudo yum history list" and "sudo yum history info", it was marked "EE" and showed the following scriptlet output: 1 2 1k 3 2k 4 3k ................. -------up until 105 104k

Any ideas what these numbers mean?

Edit: link to the output of 'yum history info': http://ur1.ca/gm9uy

edit retag flag offensive close merge delete

Comments

Can you provide the output here ? Then, give us the link to check. The EE means "The transaction completed fine, but had warning/error output during the transaction."

NickTux gravatar imageNickTux ( 2014-02-12 17:30:16 -0500 )edit
1

This is the whole output of "yum history info": http://ur1.ca/gm9uy The scriptlet output is at the end.

fedie gravatar imagefedie ( 2014-02-12 17:52:30 -0500 )edit
1

I really don't know what this scriptlet output could possible mean. As for the EE , I have already answered (see man yum) . I would suggest to open a question in yum mailing list and ask about this strange scriptlet output. (if someone from here don't answer).

NickTux gravatar imageNickTux ( 2014-02-12 18:11:28 -0500 )edit

I see numbers from time to time. They appear to be some sort of statistics. They never came across as errors, so I've never really bothered to check. The yum mailing list would be the correct place to ask. It's probably the output of a command used in the post installation scriptlet, like update-mime-info or something. Running yum with debug info enabled may have given more info, but it's too late for that now. FWIW, your yum transaction says "Success" so I expect things to be fine.

FranciscoD_ gravatar imageFranciscoD_ ( 2014-02-12 20:15:13 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2014-02-12 20:57:12 -0500

marcindulak gravatar image

Looks like something triggered by updates of selinux-policy-targeted.

rpm -q selinux-policy-targeted
# selinux-policy-targeted-3.12.1-122.fc20.noarch

yum -y downgrade selinux-policy selinux-policy-targeted
...
Running transaction
Installing : selinux-policy-3.12.1-106.fc20.noarch                        1/4 
Installing : selinux-policy-targeted-3.12.1-106.fc20.noarch               2/4 
libsepol.print_missing_requirements: conman's global requirements were not met: type/attribute conman_port_t  (No such file or directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file or directory).
/usr/sbin/semodule:  Failed!
525k <----------------------------------------- here it comes!
Cleanup    : selinux-policy-targeted-3.12.1-122.fc20.noarch               3/4 
...

Now, at this point one still gets 525k when doing yum -y update selinux-policy selinux-policy-targeted

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2014-02-12 17:05:48 -0500

Seen: 188 times

Last updated: Feb 12 '14