Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21069 - [cherrytree] fix and rebuild for python

Attached to Project: Community Packages
Opened by Alexander Haeussler (eminor) - Monday, 04 October 2010, 22:16 GMT
Last edited by Brad Fanella (cesura) - Tuesday, 05 October 2010, 03:47 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Brad Fanella (cesura)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

cherrytree does not work with python from testing and needs to be fixed:

http://allanmcrae.com/2010/10/big-python-transition-in-arch-linux/

I also noticed that the md5sum of the source tarball does not match with the one from PKGBUILD.

Additional info:
* cherrytree 0.14.2-2, python2 2.7-1
This task depends upon

Closed by  Brad Fanella (cesura)
Tuesday, 05 October 2010, 03:47 GMT
Reason for closing:  Fixed
Comment by Brad Fanella (cesura) - Tuesday, 05 October 2010, 00:30 GMT
Fixed here on my system and I have released it. Can you confirm that it is indeed fixed for for you so I can close this?
Comment by Brad Fanella (cesura) - Tuesday, 05 October 2010, 01:43 GMT
Uh-oh. I think I screwed up (again). :-(
Comment by Brad Fanella (cesura) - Tuesday, 05 October 2010, 02:12 GMT
Okay. I apologize for that. *Now* it should be fixed. :-)
Comment by Allan McRae (Allan) - Tuesday, 05 October 2010, 03:12 GMT
Updated package is working for me.
Comment by Alexander Haeussler (eminor) - Tuesday, 05 October 2010, 03:27 GMT
No problem, works now, Thanks! Do you know why the md5 sums did not match? It was not the checksum from 0.14.1 in the PKGBUILD, so you did not forget to change it and if it wasn't completely wrong all the time, the source code must have been modified within the same version!? Just to be sure... ;-)
Comment by Allan McRae (Allan) - Tuesday, 05 October 2010, 03:40 GMT
You'd be surprised at how often source code is re-released with slight changes without changing the version number...
Comment by Brad Fanella (cesura) - Tuesday, 05 October 2010, 03:47 GMT
Honestly, I have no idea! :-) It could be what Allan had said, or just a corrupt file on my part. Either way, this can now safely be closed.

Loading...