Summary: | dev-python/htmlgen doesn't work with Python >=2.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | egolem+gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 148333 | ||
Attachments: |
Build log
modified version string on line 71 to match original file |
Description
Diego Elio Pettenò (RETIRED)
2009-07-17 15:05:08 UTC
Created attachment 198320 [details]
Build log
This bug probably occurs only with Python >=2.5. Fixed. Created attachment 202313 [details, diff]
modified version string on line 71 to match original file
The ebuild patch failed for me on line 71 due to version string didn't match the original file (HTMLutil.py).
(In reply to comment #4) CVS needlessly reinterpreted $Id$ keyword :( . Fixed. Am I mistaken, or did this fix not get its own version bump on htmlgen? I had to purge htmlgen completely out of /usr/portage/dev-python and get HTMLgen.tz out of distfiles in order to force portage to redownload what would otherwise appear to have been an unchanged ebuild, only it's got the fixed patch file in it. Doesn't this fly in the face of the gentoo package versioning policies? Thanks. (In reply to comment #6) Maybe you failed to run `emerge --sync`. There was only a patch with keyword broken by CVS. The patch has been fixed. The original, committed version of patch was failing to apply, so it was only build failure. Revision bumps shouldn't be used for fixes for build failures. (In reply to comment #7) > (In reply to comment #6) > > Maybe you failed to run `emerge --sync`. Huh... weird... my systems have emerge sync on a cronjob, so maybe it was just unlucky timing on the submission of the fixed patch file and I would've gotten it normally after tomorrow's sync (scheduled for the early AM EST for me). But I'm pretty sure that I did another sync when I first got the failure, thinking that perhaps it'd pull down a new version. It didn't and so I just tried re-emerging it and that didn't work. Sorry about the confusion. Not sure why it didn't work for me and I had to purge htmlgen out completely. |