XZise added a comment. Okay in https://phabricator.wikimedia.org/rPWBCd6b6e4b37a33f4aafb418a5d44769e1cf53ae71d I added that the complete version number must match a certain scheme. You commented there:
> There are also 'official' distro releases with their own generator suffix, > which we 'should' support, or at least track which cases currently fail, and > have TODO's for any important cases which are not handled correctly. > > https://wikiapiary.com/wiki/Generator:Generators/DEBIAN > https://wikiapiary.com/wiki/Generator:Generators/CUSTOM So it seems this is on of those cases. If there is a sensible scheme behind this we could add it but what if it's 1.19.20 with backported features from newer versions? There is no sensible match then (except for the lowest common denominator). Also the docstring of `force_version` specifically says that it can be used for that: The site is usually using the version number from the servers' siteinfo, but if there is a problem with that it's possible to return a non-empty string here representing another version number. (I just noticed it should be server's) So for now I can only suggest to add the capability to return a callable which converts a incompatible version number in a compatible one (so that it's at least somewhat flexible). TASK DETAIL https://phabricator.wikimedia.org/T96813 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: XZise Cc: XZise, jayvdb, Aklapper, pywikipedia-bugs _______________________________________________ Pywikipedia-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-bugs
