FS#22177 - [mercurial] 1.7.2-1 commit broken after upgrade to python 2.7.1-3

Attached to Project: Arch Linux
Opened by Normand Fortier (nfortier) - Tuesday, 21 December 2010, 19:19 GMT
Last edited by Allan McRae (Allan) - Wednesday, 22 December 2010, 01:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Giovanni Scafora (giovanni)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: trying to commit changes in Mercurial results in error: "utf8 codec can't decode byte 0xee in position 1: invalid continuation byte" or "utf-8 codec can't decode byte 0x88 in position 0: invalid start byte".
Last succesful commit: 2010-12-20 16:09.
Pacman upgrade 2010-12-20 21:31 (see attached log).


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
   pacman_2010-12-20.log (1.9 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 22 December 2010, 01:48 GMT
Reason for closing:  Not a bug
Additional comments about closing:  bug is probably in leafpad  FS#22176 
Comment by Allan McRae (Allan) - Tuesday, 21 December 2010, 23:04 GMT
Can you confirm downgrading python fixes this issue?
Comment by Normand Fortier (nfortier) - Wednesday, 22 December 2010, 01:18 GMT
Actually, no, downgraded to python2-2.7.1-2 and the commit fails with a similar message.
Comment by Normand Fortier (nfortier) - Wednesday, 22 December 2010, 01:33 GMT
I just committed succesfully through the Netbeans mercurial plugin. Then re-upgraded to python2-2.7.1-3; commit is now working properly.
The issue was most probably caused by a bug in LeafPad which I am using as editor; it got upgraded together with python2 yesterday, but apparently fixed today.
See  FS#22176  - leafpad 0.8.18 produces corrupted files.
Thank you for your help.

Loading...