Bug 1602

Summary:	backport request: amule-2.3.1 RC2
Product:	Mageia	Reporter:	Olivier Delaune <olivier.delaune>
Component:	Backports	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	mageia, marja11
Version:	1
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	http://www.amule.org
Whiteboard:
Source RPM:	amule	CVE:
Status comment:

Description Olivier Delaune 2011-06-05 14:38:59 CEST

Hello,
amule-2.3.1 is unstable version. Could yoou also package amule-2.2.6 (last stable version) and push stable version in main depository and rc version in backport or testing depository?

Comment 1 Manuel Hiebel 2011-09-09 23:11:10 CEST

I don't think we can return so the 2.2.6 version, so better backport the last RC.

Summary: amule-2.3.1 in backport and amule-2.2.6 in main => backport request: amule-2.3.1 RC2
Source RPM: amule-2.3.1-0.rc1.2.mga1.x86_64.rpm => amule
Whiteboard: (none) => Backport

Samuel Verschelde 2011-09-13 13:04:06 CEST

Keywords: (none) => Backport
Whiteboard: Backport => (none)

Comment 2 Marja Van Waes 2011-11-25 16:41:27 CET

Also see bug 1445 (mark that that one was against cauldron)

CC: (none) => marja11
Severity: minor => enhancement

Comment 3 Olivier Delaune 2011-11-25 16:49:59 CET

The final version 2.3.1 was released. So maybe, you could push amule-2.3.1 in Mageia 1. It is better to have stable version compared to development version.

Comment 4 Marja Van Waes 2012-08-01 08:10:00 CEST

@ Olivier

Do you still need this package in Mga 1, or can this bug be closed?

Keywords: Backport => (none)
Component: RPM Packages => Backports

Comment 5 Olivier Delaune 2012-08-01 09:39:56 CEST

Oh, I had forgotten this bug report. No I do not need anymore this package in Mga 1. You can close it.

Comment 6 Sander Lepik 2012-08-01 09:48:53 CEST

Closing..

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => OLD