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
In a lot of roles, we are including a specific debian package version, which is generally ok, but we are also specifying the "debian revision" part (https://www.debian.org/doc/debian-policy/ch-controlfields.html#version). This is, if I'm not mistaken not guaranteed to be kept in the debian archives.
The proposal is to remove the last part and keep only the upstream version. For instance lnls-ans-role-python recently broke (88e75fe) as the revision "-1" was not available anymore,
The text was updated successfully, but these errors were encountered:
ok, @lerwys. For a few commits now we have been moving away from specifying the last part of the revision numbering. Soon I will submit a PR finishing the process.
In a lot of roles, we are including a specific debian package version, which is generally ok, but we are also specifying the "debian revision" part (https://www.debian.org/doc/debian-policy/ch-controlfields.html#version). This is, if I'm not mistaken not guaranteed to be kept in the debian archives.
The proposal is to remove the last part and keep only the upstream version. For instance lnls-ans-role-python recently broke (88e75fe) as the revision "-1" was not available anymore,
The text was updated successfully, but these errors were encountered: