Bug 12365 - Why is there yaml in non-free?
Summary: Why is there yaml in non-free?
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: release_blocker critical
Target Milestone: ---
Assignee: Thomas Spuhler
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks: 11704
  Show dependency tree / graph
 
Reported: 2014-01-20 11:08 CET by Samuel Verschelde
Modified: 2014-01-24 21:14 CET (History)
5 users (show)

See Also:
Source RPM: yaml
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Verschelde 2014-01-20 11:08:58 CET 
According to changelog, yaml was submitted to nonfree during a mass rebuild on January 14th, 2013. It's there since then, in Mageia 3 (not fixable) and Mageia cauldron.

http://mageia.madb.org/package/show/name/libyaml0_2/release/cauldron/application/0

Reproducible: 

Steps to Reproduce:
Samuel Verschelde 2014-01-20 11:09:07 CET

Keywords: (none) => Triaged

Comment 1 Manuel Hiebel 2014-01-21 00:02:13 CET 
could someone move it ?

CC: (none) => dmorganec, pterjan, sysadmin-bugs

Comment 2 Samuel Verschelde 2014-01-21 08:56:33 CET 
(In reply to Manuel Hiebel from comment #1)
> could someone move it ?

Not move it, re-move it (it's also in Core)
David Walser 2014-01-21 17:20:04 CET

Blocks: (none) => 11704

Comment 3 Thomas Spuhler 2014-01-22 22:20:10 CET 
yea, let's just remove it from nonfree , but leave it in core
$ urpmq --whatrequires libyaml0_2
libyaml-devel
libyaml0_2
php-yaml
python-yaml
ruby
ruby
ruby
ruby
suricata

Status: NEW => ASSIGNED

Comment 4 Thomas Spuhler 2014-01-22 22:39:17 CET 
I asked admin to remove them from nonfree
David Walser 2014-01-23 21:43:21 CET

Priority: Normal => release_blocker
CC: (none) => luigiwalser
Severity: normal => critical

Comment 5 Thomas Backlund 2014-01-24 21:14:37 CET 
yaml nuked from nonfree

Status: ASSIGNED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.