Bug 4817

Summary:	remove yajl from core/updates-testing (was Backport of yajl from Cauldron)
Product:	Mageia	Reporter:	Armando Basile <hmandevteam>
Component:	RPM Packages	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, sysadmin-bugs, tmb
Version:	1
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	yajl-2.0.4-1.mga1.src.rpm	CVE:
Status comment:

Description Armando Basile 2012-03-06 16:20:37 CET

There is now yajl-2.0.4 in core/updates_testing to validate
-------------------------------------------------------


Suggested advisory:
-------------------
already present in Cauldron, is a backport

Comment 1 claire robinson 2012-03-06 16:45:38 CET

This one is a true backport Armando, not present in Mdv 2010.2.

Until backports are open I think this will break our packaging policy. Have you checked with your mentor/other packagers?

We'll be happy to QA these if they are being allowed to be backported.

Comment 2 Armando Basile 2012-03-07 14:19:23 CET

ok, i understand, for Mageia 1 for now only Mdv2010.2 updates :)

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

Comment 3 claire robinson 2012-03-07 15:30:46 CET

Thanks Armando. I've reopened and added sysadmin into CC.

Sysadmin could you please *remove* yajl-2.0.4-1.mga1.src.rpm from core/updates_testing.

Thankyou!

Status: RESOLVED => REOPENED
CC: (none) => sysadmin-bugs
Resolution: FIXED => (none)

Manuel Hiebel 2012-03-07 17:58:00 CET

Assignee: qa-bugs => sysadmin-bugs
Summary: Backport of yajl from Cauldron => remove yajl from core/updates-testing (was Backport of yajl from Cauldron)
Severity: enhancement => normal

Comment 4 Thomas Backlund 2012-03-08 15:59:42 CET

Removed from primary mirror

Status: REOPENED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED

Comment 5 Dave Hodgins 2012-03-16 01:35:49 CET

Also need to remove yajl-debug, libyajl2, and libyajl-devel
rpm packages.

Status: RESOLVED => REOPENED
CC: (none) => davidwhodgins
Resolution: FIXED => (none)

Comment 6 Marja Van Waes 2012-07-06 15:06:17 CEST

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

Comment 7 Thomas Backlund 2012-08-06 19:44:36 CEST

yajl-debug, libyajl2, and libyajl-devel packages dropped

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