Bug 23548

Summary:	Mercurial No Module Named Peer
Product:	Mageia	Reporter:	John <johnms>
Component:	RPM Packages	Assignee:	Philippe Makowski <makowski.mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mercurial-4.6.21.mga6.x86_64	CVE:
Status comment:
Attachments:	Strace hg status

Description John 2018-09-08 09:31:14 CEST

Description of problem:
when running hg commands, e.g. hg incoming, hg status, the error:
abort: No module named peer! 
appears.


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


How reproducible: Very.


Steps to Reproduce:
1. Install mercurial
2. run hg status 
3. See abort: No module named peer!

Comment 1 John 2018-09-08 12:28:29 CEST

I don't know the cause of this, but when I removed and then reinstalled everything related to mercurial it worked again.

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

Comment 2 John 2018-09-23 09:25:14 CEST

So I figured out why it worked again, as when I reinstalled it, I selected the 4.1.3 version, and when updating to again to the 4.6.2 version it broke in the same manner again.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 3 John 2018-09-23 09:29:26 CEST

Created attachment 10381 [details]
Strace hg status

The strace of running hg status in one of my repositories on my system.

Comment 4 Marja Van Waes 2018-10-06 10:10:03 CEST

Sorry for seeing so late that you reopened this report, John!

Assigning to the registered maintainer.

Assignee: bugsquad => makowski.mageia
CC: (none) => marja11

Comment 5 Aurelien Oudelet 2020-08-16 18:59:10 CEST

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: REOPENED => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD