Bug 226168 – Merge Review: mx4j

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 226168 - Merge Review: mx4j

Summary:	Merge Review: mx4j

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	mx4j (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Spike
QA Contact:	Fedora Package Reviews List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-01-31 14:44 EST by Nobody's working on this, feel free to take it
Modified:	2015-05-28 12:10 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-05-28 12:10:09 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Nobody's working on this, feel free to take it 2007-01-31 14:44:00 EST

Fedora Merge Review: mx4j

http://cvs.fedora.redhat.com/viewcvs/devel/mx4j/
Initial Owner: fnasser@redhat.com

Comment 1 Spike 2010-10-28 08:37:07 EDT

I'll take this one.

Comment 2 Spike 2010-10-28 09:43:42 EDT

Please update to 3.0.2 before I start the merge review: http://sourceforge.net/projects/mx4j/files/

Comment 3 Cole Robinson 2015-02-11 15:38:04 EST

Mass reassigning all merge reviews to their component. For more details, see this FESCO ticket:

  https://fedorahosted.org/fesco/ticket/1269

If you don't know what merge reviews are about, please see:

  https://fedoraproject.org/wiki/Merge_Reviews

How to handle this bug is left to the discretion of the package maintainer.

Comment 4 Alexander Kurtakov 2015-05-28 12:10:09 EDT

Closing the bug as no feasible action is coming.

Note You need to log in before you can comment on or make changes to this bug.