| Summary: | during the last update, an anomaly occured when upgrading tex-live | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | peter lawford <petlaw726> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lewyssmith |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | return of urpmi --auto-update | ||
|
Description
peter lawford
2019-11-09 13:14:16 CET
Created attachment 11346 [details]
return of urpmi --auto-update
This is the same problem as bug 24771: the texlive updates are successful, but sometimes output these 'broken pipe 'errors. I wonder whether this is due to their huge size. The other complainant used journalctl to verify the package installation: https://bugs.mageia.org/show_bug.cgi?id=24771#c3 You might want to do that: $ journalctl --list-boots to pin down the session in question; then $ journalctl -b <boot number> to show its journal. But read carefully about the -b option. Alternatively, use the -S and -U (since & until) options; again, read carefully about them. Also, you can confirm with $ rpm -q <package-name> that you really do have the updated packages. This is certainly a harmless affair. *** This bug has been marked as a duplicate of bug 24771 *** CC:
(none) =>
lewyssmith |