Bug 742735 - Mercurial gives Python errors in Fedora 16 Rawhide
Summary: Mercurial gives Python errors in Fedora 16 Rawhide
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mercurial
Version: 19
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Becker
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-02 09:33 UTC by Dave Jeffery
Modified: 2015-02-17 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:54:38 UTC
Type: ---


Attachments (Terms of Use)
Typical terminal output from Mercurial in Fedora 16 Rawhide (2.72 KB, text/plain)
2011-10-02 09:33 UTC, Dave Jeffery
no flags Details

Description Dave Jeffery 2011-10-02 09:33:24 UTC
Created attachment 525911 [details]
Typical terminal output from Mercurial in Fedora 16 Rawhide

Description of problem:
Mercurial in Rawhide seems to give Python errors.

Version-Release number of selected component (if applicable):
Mercurial Distributed SCM (version 1.9.2)
using Python 2.7.2 (default, Jul  8 2011, 18:54:16) [GCC 4.6.1 20110627 (Red Hat 4.6.1-1)] via Gnome Terminal 3.2.0

How reproducible:
Always.

Steps to Reproduce:
1.Go to a folder containing a repository
2.Type hg status, hg clone, etc.
  
Actual results:
Python error message (attached in fromterminal.txt)

Expected results:
Clone of repository to be created or status printed in terminal.

Additional info:

Comment 1 Mads Kiilerich 2011-10-15 23:49:59 UTC
The most obvious explanation of this would be that you have some kind of repository corruption, probably caused by something else than Mercurial.

Can you confirm that you see this with _all_ repositories, also newly created repositories?

Comment 2 Fedora End Of Life 2013-04-03 16:29:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Fedora End Of Life 2015-01-09 16:48:25 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 13:54:38 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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