FS#12003 - mercurial deprecation warning breaks

Attached to Project: Arch Linux
Opened by Sven Richter (sveri) - Wednesday, 05 November 2008, 15:57 GMT
Last edited by Allan McRae (Allan) - Thursday, 04 December 2008, 11:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Douglas Soares de Andrade (dsa)
Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When i try to commit something with mercurial i always
get the following error:

/usr/lib/python2.6/site-packages/mercurial/demandimport.py: 46:
DeprecationWarning: the sha module is deprecated: use the hashlib module instead

and mercurial stops working.


Please have a look at:
http://www.selenic.com/mercurial/bts/issue1338


Additional info:
mercurial 1.0.2-2

Steps to reproduce:
Simply try to commit or push something with mercurial:
hg push ssh://host
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 04 December 2008, 11:16 GMT
Reason for closing:  Fixed
Comment by Artem kakoytotam (feeeyanin) - Tuesday, 11 November 2008, 21:26 GMT
'hg clone' gives the same result
Comment by Allan McRae (Allan) - Thursday, 20 November 2008, 06:10 GMT
Relevant patches:

http://selenic.com/repo/index.cgi/hg/rev/e160f2312815
http://selenic.com/repo/index.cgi/hg/rev/118720f857b9
http://selenic.com/repo/index.cgi/hg/rev/3130c9ded04e
http://selenic.com/repo/index.cgi/hg/rev/fcfb6a0a0a84
http://selenic.com/repo/index.cgi/hg/rev/4674706b5b95
Comment by Allan McRae (Allan) - Thursday, 20 November 2008, 06:57 GMT
Trying to figure out what breaks here. I can do "hg cloneanon@hg.opensolaris.org/hg/fuse/fusefs&quot"> ssh://anon@hg.opensolaris.org/hg/fuse/fusefs" using the mercurial build from the repos and get the files. Sure there are a lot of warnings (and the patches above reduce them) but these are just warnings.

I don't have a repo that I have push access to in order to test out that but the warning in itself should not cause this issue.
Comment by Allan McRae (Allan) - Wednesday, 03 December 2008, 06:00 GMT
Does mercurial 1.1-1 fix this?
Comment by Sven Richter (sveri) - Wednesday, 03 December 2008, 09:09 GMT
I cannot tell for sure.
As of 10.14.08 it was stated as fixed in crew and mainline repositories, whatever they may be.
But now the Status is Resolved.

Maybe someone can compile the current version and check it out.
Comment by Allan McRae (Allan) - Wednesday, 03 December 2008, 09:13 GMT
well, someone has and 1.1-1 is in the repos for your testing pleasure...
Comment by Sven Richter (sveri) - Thursday, 04 December 2008, 10:38 GMT
Ah, today i got the upgrade.
Indeed, it is fixed in 1.1-1 and works now for me.

Loading...