You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenBSD packages sometimes have a patch level present in their package version, such as 1.3pl20210902 above, which shows up as problematic in repology. This plXXX should be ignored and treated as just the version by itself.
Observed behavior plXXX is counted in the patch version and leads to the package marked as problematic.
Expected behavior
Ignore plXXX and unmark the problematic setting.
The text was updated successfully, but these errors were encountered:
As said, it (mixing up the way of conveying upstream version components and local snapshots) is a problem of openbsd repository
We're handling it (IMO) the most graceful way possible - ignoring *pl*, which leads to
Snapshots getting ignored status - the least penalizing among the ignored statuses family, and the same as we're using for snapshots in any other repo
Upstream p{,atch,post} versions getting ignored (again, the least penalizing) status when coming solely from openbsd, but getting expected status when there's matching p* version from any other repo
Projects affected
OpenBSD packages in general, with a concrete example of schema2ldif - https://repology.org/project/schema2ldif/versions
OpenBSD packages sometimes have a patch level present in their package version, such as
1.3pl20210902
above, which shows up as problematic in repology. ThisplXXX
should be ignored and treated as just the version by itself.Observed behavior
plXXX
is counted in the patch version and leads to the package marked as problematic.Expected behavior
Ignore
plXXX
and unmark the problematic setting.The text was updated successfully, but these errors were encountered: