| Summary: | release version of libreoffice or his requires block update of fresh installed mageia 8 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | katnatek <j.alberto.vc> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | libreoffice | CVE: | |
| Status comment: | |||
| Attachments: | Full log with the update with urpmi --auto --auto-update | ||
|
Description
katnatek
2023-10-12 02:34:09 CEST
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) =>
libreoffice (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 =>
RESOLVED |