Bug 13918

Summary:	Urpmi update repo error message
Product:	Mageia	Reporter:	Valek Saikov <saikov.vb>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	sysadmin-bugs
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	screenshot error

Description Valek Saikov 2014-08-16 14:07:58 CEST

Description of problem: Error message if i used urpmi --auto-update

values on reference is experimental at /usr/lib/perl5/vendor_perl/5.18.1/urpm/main_loop.pm line 232.
values on reference is experimental at /usr/lib/perl5/vendor_perl/5.18.1/urpm/main_loop.pm line 232.
values on reference is experimental at /usr/lib/perl5/vendor_perl/5.18.1/urpm/main_loop.pm line 245.
values on reference is experimental at /usr/lib/perl5/vendor_perl/5.18.1/urpm/main_loop.pm line 245.


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

NAME="Mageia"
VERSION="5"
ID=mageia
ID_LIKE="mandriva fedora"
PRETTY_NAME="Mageia 5"
ANSI_COLOR="1;36"
HOME_URL="http://www.mageia.org/"
SUPPORT_URL="http://www.mageia.org/support/"
BUG_REPORT_URL="https://bugs.mageia.org/"

How reproducible:

Steps to Reproduce:
1. Install boot-nonfree.iso on virtualbox
2. Change MATE
3. urpmi --auto-update


Reproducible: 

Steps to Reproduce:

Comment 1 Valek Saikov 2014-08-16 14:11:17 CEST

Created attachment 5347 [details]
screenshot error

Comment 2 James Kerr 2014-08-16 16:45:23 CEST

These are just warnings; urpmi should still work.

https://wiki.mageia.org/en/Mageia_5_Errata#urpmi

The fix will be applied the next time urpmi is re-built.

James Kerr 2014-08-16 16:46:11 CEST

Component: Release (media or process) => RPM Packages

Comment 3 Valek Saikov 2014-08-16 17:03:09 CEST

So while this message is displayed? As it is impossible to fix? Or it will be fixed in Mageia 5 alpha 3?

Comment 4 James Kerr 2014-08-16 17:24:10 CEST

It has already been fixed. The fix will appear in the package when urpmi is next re-built which will probably be when the mass rebuild is done (planned for mid-September), if it is not done earlier. The fixed package should be available in Beta 1, planned for late September.

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