Summary: | python-2.5 - pysqlite-2* blockers should be mutual | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lukasz Ligowski <orangewarrior> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dju, spatz |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 148333, 166612 | ||
Attachments: | Patch for dev-python/pysqlite-2.3.1 |
Description
Lukasz Ligowski
2006-09-25 12:34:34 UTC
changing the pysqlite ebuilds to block on >=dev-lang/python-2.5 is trivial, so why is this bug open for so long? will sending a patch/updated ebuilds help? Created attachment 112333 [details, diff]
Patch for dev-python/pysqlite-2.3.1
Patch attached.
It's my first time submitting a patch, sorry if I did anything wrong.
Actually python 2.5 and pysqlite should not block at all, since the sqlite integrated in python 2.5 has the module name sqlite3, which does not collide with pysqlite's sqlite2 module. The bump to the python ebuild I just committed removes the block. |