First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 188067
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Python Gentoo Team <python@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Brian <bkbetts@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
emerge-info.txt emerge --info output. text/plain Brian 2007-08-08 02:01 0000 2.61 KB Details
pyid3lib.diff Patch to compile pyid3lib with emerge. patch Brian 2007-08-08 02:03 0000 919 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 188067 depends on: Show dependency tree
Bug 188067 blocks: 148333
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: 2007-08-08 02:00 0000 
Cannot compile pyid3lib 0.5.1 on Gentoo AMD64. Get deprecated type warnings and
errors relating to not being able to use int with Py_ssize_t. In Python 2.5,
sequence indices were changed from int to Py_ssize_t. Please see
http://www.python.org/dev/peps/pep-0353/ for more information. I based my fix
on this information and the helpful checking script linked to from that URL.

Reproducible: Always

Steps to Reproduce:
1. Emerge pyid3lib.

Actual Results:  
Emerge fails with deprecated warnings and compiler typing errors.

Expected Results:  
Emerge to successfully build pyid3lib, at least without errors, but preferably
without warnings, as well.

I have a less than optimal patch that allows me to compile pyid3lib on my amd64
machine with no errors or warnings. I have did some simple testing with my
program that utilizes the library to manage MP3s using ID3 tagging.

emerge --info output and patch will be attached.

------- Comment #1 From Brian 2007-08-08 02:01:58 0000 ------- 
Created an attachment (id=127221) [details]
emerge --info output.

------- Comment #2 From Brian 2007-08-08 02:03:36 0000 ------- 
Created an attachment (id=127222) [details]
Patch to compile pyid3lib with emerge.

This patch is not backward compatible with previous Python versions. Please see
http://www.python.org/dev/peps/pep-0353/ for proper backward compatibility
handling.

------- Comment #3 From Ali Polatel (RETIRED) 2007-08-08 21:46:42 0000 ------- 
(In reply to comment #2)
> This patch is not backward compatible with previous Python versions. Please >see
> http://www.python.org/dev/peps/pep-0353/ for proper backward compatibility
> handling.
> 

I modified your patch a bit for backwards compatibility and added to cvs.
version 0.5.1-r1 in portage fixes this.
I've tested it on an amd64 box with py2.4 and 2.5 and it seems to work fine.
Please reopen the bug if you still have problems.
Thanks for reporting! :)

------- Comment #4 From Jakub Moc (RETIRED) 2007-09-08 11:43:23 0000 ------- 
*** Bug 191678 has been marked as a duplicate of this bug. ***

------- Comment #5 From Farid 2007-09-09 12:11:32 0000 ------- 
(In reply to comment #4)
> *** Bug 191678 has been marked as a duplicate of this bug. ***
> 

pyid3lib-0.5.1-r1 fixes the problem. Thanks!

For some reason /usr/sbin/python-updater tries to pull in the 0.5.1 version and
not the r1 version, even though the line "dev-python/pyid3lib ~amd64" is
present in /etc/portage/package.keywords.
Emerging pyid3lib normally works as expected though. After emerging it normally
python-updater does not complain either, just as expected.
Maybe this behaviour should be fixed in python-updater?
First Last Prev Next    No search results available      Search page      Enter new bug