One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-cmeh3i70/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1618531200\nerror: Bad file: ./bluepyopt-1.9.151_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.9.151_version.py: No such file or directory\n'

Latest upstream release: 1.9.153
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-3ynsmwbh/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1618876800\nerror: Bad file: ./bluepyopt-1.9.153_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.9.153_version.py: No such file or directory\n'

Latest upstream release: 1.10.9
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-wn0fa3jt/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1619049600\nerror: Bad file: ./bluepyopt-1.10.9_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.9_version.py: No such file or directory\n'

Latest upstream release: 1.10.12
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-91r32cri/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1619049600\nerror: Bad file: ./bluepyopt-1.10.12_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.12_version.py: No such file or directory\n'

Latest upstream release: 1.10.14
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-7ua_gykt/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1619654400\nerror: Bad file: ./bluepyopt-1.10.14_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.14_version.py: No such file or directory\n'

Latest upstream release: 1.10.21
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-0hnsr_qf/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1619654400\nerror: Bad file: ./bluepyopt-1.10.21_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.21_version.py: No such file or directory\n'

Latest upstream release: 1.10.24
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-4zk9zgzt/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1619654400\nerror: Bad file: ./bluepyopt-1.10.24_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.24_version.py: No such file or directory\n'

Latest upstream release: 1.10.27
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-b0n750g8/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1620345600\nerror: Bad file: ./bluepyopt-1.10.27_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.27_version.py: No such file or directory\n'

Latest upstream release: 1.10.30
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-lhnafx5v/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1620604800\nerror: Bad file: ./bluepyopt-1.10.30_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.30_version.py: No such file or directory\n'

Hi Anil,

Do you think it's OK to update to the latest release in all Fedora releases? Are there any major changes we should be aware of?

https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases

Cheers,
Ankur

Hi Ankur,

I think it is safe to update since there is no change in the dependencies and their versions.

Best
Anil

Thanks, that sounds good. I'll update the Fedora package when I can find the time. On my tasklist now.

Cheers,

Latest upstream release: 1.10.33
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-rk4yll8o/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1621382400\nerror: Bad file: ./bluepyopt-1.10.33_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.33_version.py: No such file or directory\n'

Latest upstream release: 1.10.36
Current version/release in rawhide: 1.9.149-1.fc35
URL: https://pypi.org/project/bluepyopt/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/30785/

One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-7ukcxblp/python-bluepyopt.spec'] returned 1: b'setting SOURCE_DATE_EPOCH=1621382400\nerror: Bad file: ./bluepyopt-1.10.36_version.py: No such file or directory\n\n\nRPM build errors:\n    Bad file: ./bluepyopt-1.10.36_version.py: No such file or directory\n'

FEDORA-2021-2ce46684ef has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2ce46684ef

FEDORA-2021-d4012edd62 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d4012edd62

FEDORA-2021-2ce46684ef has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2ce46684ef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2ce46684ef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-d4012edd62 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d4012edd62`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d4012edd62

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-2ce46684ef has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2021-d4012edd62 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.