FS#73424 - python-watchdog package wrong upstream release version tracking
Attached to Project:
Community Packages
Opened by Luka Žaja (Venom) - Wednesday, 19 January 2022, 21:19 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 28 December 2022, 03:55 GMT
Opened by Luka Žaja (Venom) - Wednesday, 19 January 2022, 21:19 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 28 December 2022, 03:55 GMT
|
Details
Description:
This task has nothing to do with the package being outdated because it technically isn't. The problem is that python-watchdog is using the 0.10.x upstream's releases instead of the 2.x releases which are meant for newer Python versions (> 3.5). I've flagged the package as outdated a few months ago despite it being updated to the latest (at the time of writing this) 0.10.x release. I believe that it'd be in Arch's "spirit", so to speak, to use the 2.x releases instead - that is, the latest available version: https://github.com/gorakhargosh/watchdog/releases/tag/v2.1.6 Perhaps a quote from the readme file will explain this issue better: "Works on 3.6+. If you want to use Python 2.6, you should stick with watchdog < 0.10.0. If you want to use Python 2.7, 3.4 or 3.5, you should stick with watchdog < 1.0.0." It could be (I don't know, honestly) that the 2.x version somehow breaks one or more dependencies of this package in which case those ought to be fixed, somehow, beforehand. Package link - https://archlinux.org/packages/community/any/python-watchdog/ Additional info: * package version(s) - 0.10.7-3 * config and/or log files etc. - as packaged * link to upstream bug report, if any - nothing pertinent to this task Steps to reproduce: - none, visit the linked package's page |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 28 December 2022, 03:55 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Wednesday, 28 December 2022, 03:55 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
![Link to this comment](../themes/ArchLinux/comment.png)
This bug was, in the meantime, resolved and as such can be safely
closed. Thank you, felixonmars!