Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40660 - [python2-babel] pip complains "cannot find svn location"

Attached to Project: Community Packages
Opened by Marti (intgr) - Tuesday, 03 June 2014, 15:43 GMT
Last edited by Balló György (City-busz) - Saturday, 09 August 2014, 09:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: When I run any pip commands with python2-babel installed, it always reports the following warnings:

Warning: cannot find svn location for Babel==1.3-20140317
## FIXME: could not find svn URL in dependency_links for this package:
Babel==1.3-20140317

This task depends upon

Closed by  Balló György (City-busz)
Saturday, 09 August 2014, 09:51 GMT
Reason for closing:  Upstream
Comment by Marti (intgr) - Tuesday, 03 June 2014, 15:44 GMT
Sorry, the exact command is: pip2 freeze
Comment by Balló György (City-busz) - Friday, 08 August 2014, 15:20 GMT
I think it's not a bug, just a warning message. Please contact with the upstream maintainers of pip if you think so: https://github.com/pypa/pip/issues
Comment by Marti (intgr) - Friday, 08 August 2014, 15:37 GMT
Yes it's "just a warning", but it's annoying to see it every time I'm using pip freeze.

The warning is printed because of the way python2-babel is packaged in Arch Linux. If I install Babel from PyPI with pip commands, this does not occur. So it's hard to claim this is an upstream bug.
Comment by Balló György (City-busz) - Friday, 08 August 2014, 16:05 GMT
I guess that pip assumes babel installed from SVN, because it has a version number 1.3-20140317. It should be fixed by upstream (either in babel or pip).

Loading...