Bug 16150

Summary:	mgaapplet-upgrade-helper does not find release 5
Product:	Mageia	Reporter:	Daniel Le Berre <le.berred>
Component:	Release (media or process)	Assignee:	Manuel Hiebel <manuel.mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	High	CC:	doktor5000, sysadmin-bugs
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Daniel Le Berre 2015-06-20 14:38:58 CEST

Description of problem:

When trying to upgrade my mageia 4 box from the command line, the 
mgaapplet-upgrade-helper does not find the new release on the server.

It might simply be the case that the new release is not yet available on the mirrors. There is however an error message on the console which might also explain why the process does not complete sucessfully:

$ mgaapplet-upgrade-helper --new_distro_version=5
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 296.
  x86_64?product=Default&version=4&mgaonline_version=3.10.1 récupéré
could not find version '5' in the distro update list


Version-Release number of selected component (if applicable):

mgaonline-3.10.1-1.mga4

How reproducible:

Always (since this morning)



Reproducible: 

Steps to Reproduce:

Comment 1 Rémi Verschelde 2015-06-20 15:09:49 CEST

Thanks for reporting this, Manuel is indeed updating the API right now, so there command does not work yet.

Priority: Normal => High
Assignee: bugsquad => manuel.mageia

Florian Hubold 2015-06-20 15:56:33 CEST

CC: (none) => doktor5000

Comment 2 Mageia Robot 2015-06-20 16:58:02 CEST

commit 598300ead05ebc4674470be3792fc05563674e29
Author: Manuel Hiebel <leuhmanu@...>
Date:   Sat Jun 20 16:56:26 2015 +0200

    enable upgrade from mga4 to mga5 (mga#16150)
---
 Commit Link:
   http://gitweb.mageia.org/web/releases/commit/?id=598300ead05ebc4674470be3792fc05563674e29

Comment 3 Manuel Hiebel 2015-06-20 16:59:13 CEST

Did some test, no issue found, upgrade will be notified on users, and the mgaapplet-upgrade-helper will work.

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

Comment 4 Daniel Le Berre 2015-06-20 17:20:26 CEST

I confirm that it works now. Thanks.