Bug 27844 - grep write error broken pipe running urpmi
Summary: grep write error broken pipe running urpmi
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-16 10:16 CET by papoteur
Modified: 2020-12-18 21:48 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description papoteur 2020-12-16 10:16:11 CET 
I caught an error running urpmi auto-update

    $MIRRORLIST: media/core/release/glibc-devel-2.32-6.mga8.x86_64.rpm
    $MIRRORLIST: media/core/release/glibc-2.32-6.mga8.x86_64.rpm                             
installation de glibc-2.32-6.mga8.x86_64.rpm glibc-devel-2.32-6.mga8.x86_64.rpm depuis /var/cache/urpmi/rpms
Préparation...                   ###########################################################
      1/2: glibc                 ###########################################################
Reloading postfix configuration (via systemctl):           [  OK  ]
      2/2: glibc-devel           ###########################################################
      1/2: désinstallation de glibc-devel-6:2.32-5.mga8.x86_64
                                 ###########################################################
      2/2: désinstallation de glibc-6:2.32-5.mga8.x86_64
                                 ###########################################################
grep: erreur d'écriture: Relais brisé (pipe)
Vous devriez relancer votre ordinateur pour glibc
redémarrage de urpmi
Comment 1 Lewis Smith 2020-12-16 21:25:23 CET 
This looks like the end of the first part of a 2-stage update : "redémarrage de urpmi" -> the main update list. Did that happen? If yes, nothing to worry about. If it did not, and you re-launched the update, did that work?

Given that this is the only open error report like this, I see no hope of finding it.

CC: (none) => lewyssmith

Comment 2 papoteur 2020-12-18 09:38:15 CET 
Hi Lewis,
The update continued without problem.
I filled this report only because I found that this message is quiet hurting.
Comment 3 Lewis Smith 2020-12-18 21:27:27 CET 
Merci. Disons 'disconcerting'.
Given the happy ending, and the spurious nature of the incident, I do not think you will be offended if we close this.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED

Comment 4 Thomas Backlund 2020-12-18 21:48:16 CET 
not really resolved, but its more of a cosmetic enhancement to polish the distro
Note You need to log in before you can comment on or make changes to this bug.