Description of problem: When updating from version 5 to 6 using network with the mga applet, if one chooses to first download all RPMs in a folder, and select a folder that contains UTF-8 characters (like Téléchargements, in the French version), the download fails with a message like « no right to write in [path] » folder, even as root, and in the path the UTF-8 characters are displayed as if they were latin-1. After that, the distribution update application does not display in the desktop, but thanksfully an update of all packages after that seems to work... How reproducible: Difficult to say, since after that the update worked using the standard update mechanism
Summary: Update failure when RPM download folder include UTF-8 characters => Update failure when RPM download folder includes UTF-8 characters
Source RPM: (none) => mgaonlineComponent: Installer => New RPM package requestBlocks: (none) => 21340
Component: New RPM package request => RPM PackagesAssignee: bugsquad => mageiatools
Created attachment 9558 [details] in my testing, it wasn't possible to actually change the directory on mga6
Status: NEW => ASSIGNEDAssignee: mageiatools => thierry.vignaudCC: (none) => thierry.vignaud
Created attachment 9559 [details] fix directory not being UTF-8 Can you test this patch?
Keywords: (none) => PATCH
I'm sorry, but the computer I used was finally updated to Mageia 6 so I cannot test anything concerning the update know :( I'll have other computers to upgrade at work, but can't do anything before two weeks. And then, could you please explain how to use the patch before making the upgrade? Thanks,
Created attachment 9562 [details] fix directory not being UTF-8 previous patch included debug stuff
Attachment 9559 is obsolete: 0 => 1
(In reply to Emmanuel Curis from comment #3) Sorry, that would be running the following commands as root in a terminal: cd /usr/lib/libDrakX/drakfirsttime/ patch -p1 < /where/it/was/downloaded/0001-fix-directory-not-being-UTF-8-mga-21433.patch
Thanks. Just to be sure I've understood correctly: I guess the command is to be executed on a computer with Mageia 5 installed, before starting an upgrade to Mageia 6. Is there any operation to do be sure that when running the mgaapplet for the upgrade from its icon in WindowMaker dock's, the patched version is really running?
This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL) in about 3 weeks from 2020-08-05 as it is "Assigned" to a maintainer. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
CC: (none) => ouaurelien
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Resolution: (none) => OLDStatus: ASSIGNED => RESOLVED