Bug 1459712

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 2.0.11
Current version/release in rawhide: 2.0.8-2.fc26
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 2.0.12
Current version/release in rawhide: 2.0.8-3.fc27
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 2.0.13
Current version/release in rawhide: 2.0.8-3.fc27
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 2.0.14
Current version/release in rawhide: 2.0.8-3.fc27
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 3.0.0
Current version/release in rawhide: 2.0.8-3.fc27
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 3.0.3
Current version/release in rawhide: 2.0.8-3.fc27
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Latest upstream release: 3.0.4
Current version/release in rawhide: 2.0.8-3.fc27
URL: https://github.com/benediktschmitt/py-filelock

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/11739/

One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs

Can we have this in Fedora 29?

It's a major version bump due to a behavioral change. Looks like f29 shows no dependencies on this package, though.

What is the reason for pulling it into f29? python-tox?

Since this is a major bump, wouldn't I need to talk to FESCO? On a related note, what is the policy for major bumps in EPEL?

(In reply to Scott K Logan from comment #17)
> It's a major version bump due to a behavioral change. Looks like f29 shows
> no dependencies on this package, though.

python-cartopy-0:0.17.0-1.fc30.src
python-pytest-xdist-0:1.24.1-1.fc30.src
python3-tox-0:3.5.3-1.fc30.noarch

> What is the reason for pulling it into f29? python-tox?

Yes.


> Since this is a major bump, wouldn't I need to talk to FESCO?

Not necessarily, use your best judgement.If' it's really a major bump when it comes to API, maybe just say "no".

Talk to owners of python-cartopy, python-pytest-xdist and python-tox. Since python-cartopy and python-pytest-xdist only BR it, try to rebuild them and if it works, assume it's fine, but talk to them nevertheless.

> On a related
> note, what is the policy for major bumps in EPEL?

https://fedoraproject.org/wiki/EPEL_Updates_Policy

python-filelock-3.0.12-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-48aa349cec

python-filelock-3.0.12-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-48aa349cec

python-filelock-3.0.12-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.