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!
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!
FS#40063 - [python2-lockfile] upstream is in flux
Attached to Project:
Community Packages
Opened by Roman Neuhauser (roman-neuhauser) - Thursday, 24 April 2014, 10:43 GMT
Last edited by Thorsten Töpper (Atsutane) - Tuesday, 29 April 2014, 19:36 GMT
Opened by Roman Neuhauser (roman-neuhauser) - Thursday, 24 April 2014, 10:43 GMT
Last edited by Thorsten Töpper (Atsutane) - Tuesday, 29 April 2014, 19:36 GMT
|
Detailsthe code moved to github, but there are no tags on the repo, and unfortunately, tarballs are gone from googlecode :(
https://github.com/smontanaro/pylockfile/issues/9#issuecomment-33012826: "I've asked a number of times in a couple different venues looking fire someone to take over thus project. Would you like to?" ([sic]x2) not sure what to do about this one... |
This task depends upon
Closed by Thorsten Töpper (Atsutane)
Tuesday, 29 April 2014, 19:36 GMT
Reason for closing: Upstream
Additional comments about closing: I follow the issue and update the package when there's a stable link available. Just using a commit ID as workaround is imho not the proper solution. Thanks for your effort.
Tuesday, 29 April 2014, 19:36 GMT
Reason for closing: Upstream
Additional comments about closing: I follow the issue and update the package when there's a stable link available. Just using a commit ID as workaround is imho not the proper solution. Thanks for your effort.