Bug 25672 - during the last update, an anomaly occured when upgrading tex-live
Summary: during the last update, an anomaly occured when upgrading tex-live
Status: RESOLVED DUPLICATE of bug 24771
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-09 13:14 CET by peter lawford
Modified: 2019-11-09 21:56 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
return of urpmi --auto-update (18.90 KB, text/plain)
2019-11-09 13:15 CET, peter lawford
Details

Description peter lawford 2019-11-09 13:14:16 CET
Description of problem:
during the last update, when updating the pkgs texlive-collection-basic and texlive-dist, the mention:
yes: standard output: Broken pipe
appeared
but the update process successfully completed
I don't know if there is a bug or not, but it seems to me abnormal
see the attached file: return of the command urpmi --auto-update
the same occured on one another mag7 system when upgrading using dnf:
dnf --refresh upgrade

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 peter lawford 2019-11-09 13:15:18 CET
Created attachment 11346 [details]
return of urpmi --auto-update
Comment 2 Lewis Smith 2019-11-09 21:56:04 CET
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
Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.