Opened 12 years ago
Closed 11 years ago
#38693 closed defect (fixed)
py-eyed3: getGenre() API call prints "boo" on the console
Reported by: | macports@… | Owned by: | elelay (Eric Le Lay) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | ||
Port: | py-eyed3 |
Description
See https://bugs.launchpad.net/ubuntu/+source/eyed3/+bug/1067039 for a full description and patch
Change History (11)
comment:1 Changed 12 years ago by mf2k (Frank Schima)
Owner: | changed from macports-tickets@… to elelay@… |
---|
comment:2 follow-up: 4 Changed 12 years ago by macports@…
Doesn't trac E-mail the maintainers if the "port" field is filled in? If not, I'll file a bug against trac.
comment:3 follow-ups: 5 6 Changed 12 years ago by elelay (Eric Le Lay)
What do you expect from me ? I'm reluctant to apply such out-of-band patches to a package. What's the problem with a little boo on the console that can't wait for next release of eyed3?
comment:4 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to macports@…:
Doesn't trac E-mail the maintainers if the "port" field is filled in? If not, I'll file a bug against trac.
No, it doesn't. We believe we would have to write a Trac plugin to do that, and nobody has found it important enough yet to figure out how to do that.
comment:5 follow-up: 7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | py-eyed3 added; py27-eyed3 removed |
---|---|
Summary: | getGenre() API call prints "boo" on the console → py-eyed3: getGenre() API call prints "boo" on the console |
Replying to elelay@…:
I'm reluctant to apply such out-of-band patches to a package.
Seems like a pretty easy one-line change to include in the port.
What's the problem with a little boo on the console that can't wait for next release of eyed3?
It would also be fine to wait for a new upstream release; it's up to you.
comment:6 follow-up: 8 Changed 12 years ago by macports@…
Replying to elelay@…:
What do you expect from me ?
I found a bug in software installed via port. I found the easy fix was already available. I reported it. What you do with that information is up to you. Personally I found it very annoying to see a line with "boo" in every display of id3 tags.
Thanks for your hard work on this port.
comment:7 Changed 12 years ago by macports@…
Replying to ryandesign@…:
It would also be fine to wait for a new upstream release; it's up to you.
The last upstream release is 0.7.1 (final) from November 2012. I wouldn't hold my breath waiting on a new release fixing this bug in 0.6.18.
comment:8 Changed 11 years ago by elelay (Eric Le Lay)
Replying to macports@…:
Replying to elelay@…:
What do you expect from me ?
I found a bug in software installed via port. I found the easy fix was already available. I reported it. What you do with that information is up to you. Personally I found it very annoying to see a line with "boo" in every display of id3 tags.
Thanks for your hard work on this port.
Excuse me: it didn't come out as I meant it. You were right to post :-)
Now, I've updated to 0.7.1 in r105445, which doesn't print "boo" anymore. Let me know if you see regressions.
Cheers and thanks for reporting
-- grumpy maintainer
comment:9 Changed 11 years ago by elelay (Eric Le Lay)
0.7.1 doesn't build under python25
---> Building py25-eyed3 DEBUG: Executing org.macports.build (py25-eyed3) DEBUG: Environment: CPATH='/opt/local/include' CFLAGS='' CXXFLAGS='' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.6' CXX='/usr/bin/g++-4.2' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_mports_dports_python_py-eyed3/py25-eyed3/work/.CC_PRINT_OPTIONS' F90FLAGS='' LDFLAGS='' FCFLAGS='' OBJC='/usr/bin/gcc-4.2' OBJCFLAGS='' FFLAGS='' CC_PRINT_OPTIONS='YES' CC='/usr/bin/gcc-4.2' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_mports_dports_python_py-eyed3/py25-eyed3/work/eyeD3-0.7.1" && /opt/local/bin/python2.5 setup.py build' DEBUG: Executing command line: cd "/opt/local/var/macports/build/_opt_mports_dports_python_py-eyed3/py25-eyed3/work/eyeD3-0.7.1" && /opt/local/bin/python2.5 setup.py build Traceback (most recent call last): File "setup.py", line 10, in <module> paver.tasks.main() File "paver-minilib.zip/paver/tasks.py", line 816, in main File "paver-minilib.zip/paver/tasks.py", line 785, in _launch_pavement File "pavement.py", line 377 print(prompt + ' ', end='') ^ SyntaxError: invalid syntax Command failed: cd "/opt/local/var/macports/build/_opt_mports_dports_python_py-eyed3/py25-eyed3/work/eyeD3-0.7.1" && /opt/local/bin/python2.5 setup.py build Exit code: 1 Error: org.macports.build for port py25-eyed3 returned: command execution failed DEBUG: Error code: CHILDSTATUS 66819 1
Since no port is depending on it there is no python25-only port depending on it, so I'm quietly removing 25 from python.versions in r105450
comment:11 Changed 11 years ago by elelay (Eric Le Lay)
Resolution: | → fixed |
---|---|
Status: | new → closed |
In the future, please Cc the port maintainer(s).