Description of problem: I set up a VM with Mageia 8 Xfce i586 installed with Classic ISO, after finish the installation and boot to the system, I set up the repositories and try to update with urpmi --auto --auto-update, before made the test for the glibc bug (bug#32357) and find that update can't finish due conflicts related to libreoffice requires, uninstall libreoffice and again run urpmi --auto --auto-update, the update could finish, and I proceed to test the updates for the mentioned bug. Then I clean install again Mageia 8 Xfce i586, and try to reproduce the fail, the issue happened again Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Fresh install Mageia 8, include libreoffice packages in the installation 2. Not set additional repositories, neither update in the installation process 3. After boot in Mageia 8, setup the repositories and try to update with urpmi --auto --auto-update 4. The update can't finish due to conflicts with libreoffice or his requirements
Created attachment 14047 [details] Full log with the update with urpmi --auto --auto-update In this log you find the error described, and the solution. I don't know why have rpm db errors this time, but I include that also in log
Although Mageia 8 is on its way out, it is still supported and this bug merits academic attention. No-one in real life would install Mageia 8 now that 9 is out; and we could bounce bugs related to doing that: install Mageia 9! Assigning to ThierryV for libreoffice.
Source RPM: (none) => libreofficeAssignee: bugsquad => thierry.vignaud
(In reply to Lewis Smith from comment #2) > Although Mageia 8 is on its way out, it is still supported and this bug > merits academic attention. No-one in real life would install Mageia 8 now > that 9 is out; and we could bounce bugs related to doing that: install > Mageia 9! > > Assigning to ThierryV for libreoffice. I see that coming :)
I had to reinstall the VM, this time I set the online repositories and when I boot to the system only a few updates more were installed, this time without issues. So, I guess the advice for upgrade is valid for installing a system long time after his release, set up the online repositories in the process
Closing as invalid
Status: NEW => RESOLVEDResolution: (none) => INVALID