Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 125719
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Python Gentoo Team <python@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jacob Smullyan <smulloni@smullyan.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
psycopg-2.0.2.ebuild Psycopg2 post release ebuild (second poin release) text/plain John McFarlane 2006-06-13 10:31 0000 643 bytes Details
psycopg-2.0.2.ebuild psycopg-2.0.2.ebuild text/plain Dustin J. Mitchell 2006-07-25 14:04 0000 925 bytes Details
psycopg-2.0.2-nodebug.patch psycopg-2.0.2-nodebug.patch patch Dustin J. Mitchell 2006-07-25 14:05 0000 586 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 125719 depends on: Show dependency tree
Bug 125719 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-03-10 08:02 0000 
Currently, psycopg >= 1.99 is masked because psycopg in that version had a
different api than psycopg1 but kept the same package name.  However, from
psycopg 2 on, the package name was changed to psycopg2, and hence can be
installed simultaneously in a different SLOT and doesn't need to be masked.  I
propose dropping the 1.99 ebuild (no one should use it, it is broken),
unmasking and slotting psycopg2, and while you are at it version bumping to
2.0beta8.  I'll add an ebuild to this bug shortly.

------- Comment #1 From Jacob Smullyan 2006-03-10 08:07:35 0000 ------- 
Actually, the ebuild for 2.0beta5 is already SLOTted, so it just needs a
version bump to beta8, no changes necessary.

------- Comment #2 From Jacob Smullyan 2006-03-10 08:29:18 0000 ------- 
2.0_beta8 can also be keyworded ~ppc.

------- Comment #3 From Maciej Zieba 2006-05-08 02:53:53 0000 ------- 
Psycopg 2.0_beta8 also runs fine on amd64.

------- Comment #4 From John McFarlane 2006-06-13 10:28:27 0000 ------- 
Psycopg2 was officially released 2006/06/08.  I'm currently running    
psycopg2-2.0.2 without any problems (x86).  In the event it's helpfull I'll
post the ebuild I'm using.


Cheers, John M.

------- Comment #5 From John McFarlane 2006-06-13 10:31:35 0000 ------- 
Created an attachment (id=89055) [details]
Psycopg2 post release ebuild (second poin release)

works for me on x86.

------- Comment #6 From Alastair Tse (RETIRED) 2006-07-19 00:57:43 0000 ------- 
before it gets unmasked, we have to go through the tree to change all the deps
of packages to <dev-python/psycopg-1.99.

dev-python/adodb-py
dev-python/django
dev-python/orm
dev-python/sqlobject
net-zope/zpsycopgda
www-apps/trac

------- Comment #7 From Dustin J. Mitchell 2006-07-25 14:04:59 0000 ------- 
Created an attachment (id=92742) [details]
psycopg-2.0.2.ebuild

New ebuild supporting 'debug' USE flag

------- Comment #8 From Dustin J. Mitchell 2006-07-25 14:05:42 0000 ------- 
Created an attachment (id=92743) [details]
psycopg-2.0.2-nodebug.patch

patch used by psycopg-2.0.2.ebuild

------- Comment #9 From Dustin J. Mitchell 2006-07-25 14:06:21 0000 ------- 
I just added a newer version of the 2.0.2 ebuild which removes the
'PSYCOPG_DEBUG' flag unless the 'debug' USE flag is specified.

------- Comment #10 From Alastair Tse (RETIRED) 2006-07-28 05:32:39 0000 ------- 
thanks dustin, i've now unmasked psycopg-2.0.2 along with modifying all the
psycopg deps for packages that do not support both versions.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug