Bug 2356490

Summary: python-pymssql-2.3.9 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-pymssqlAssignee: Mohamed El Morabity <pikachu.2014>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cstratak, epel-packagers-sig, orion, pikachu.2014
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-pymssql-2.3.9-1.fc41 python-pymssql-2.3.9-1.fc42 python-pymssql-2.3.9-1.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-22 01:01:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2362565    
Bug Blocks: 2412614, 2414622    
Attachments:
Description Flags
Update to 2.3.3 (#2356490)
none
Update to 2.3.4 (#2356490)
none
Update to 2.3.5 (#2356490)
none
Update to 2.3.6 (#2356490)
none
Update to 2.3.7 (#2356490)
none
Update to 2.3.8 (#2356490)
none
Update to 2.3.9 (#2356490) none

Description Upstream Release Monitoring 2025-04-01 02:17:28 UTC
Releases retrieved: 2.3.3
Upstream release that is considered latest: 2.3.3
Current version/release in rawhide: 2.3.2-1.fc42
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 1 Upstream Release Monitoring 2025-04-01 02:17:33 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-u5wbe7s0/python-pymssql.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1743465600
error: Bad file: ./pymssql-2.3.3.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./pymssql-2.3.3.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 2 Upstream Release Monitoring 2025-04-01 02:17:35 UTC
Created attachment 2082871 [details]
Update to 2.3.3 (#2356490)

Comment 3 Upstream Release Monitoring 2025-04-02 04:51:32 UTC
Releases retrieved: 2.3.4
Upstream release that is considered latest: 2.3.4
Current version/release in rawhide: 2.3.2-1.fc42
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 4 Upstream Release Monitoring 2025-04-02 04:51:35 UTC
Created attachment 2083019 [details]
Update to 2.3.4 (#2356490)

Comment 5 Upstream Release Monitoring 2025-04-02 04:56:00 UTC
the-new-hotness/release-monitoring.org's scratch build of python-pymssql-2.3.4-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=131001173

Comment 6 Upstream Release Monitoring 2025-06-25 14:11:10 UTC
Releases retrieved: 2.3.5
Upstream release that is considered latest: 2.3.5
Current version/release in rawhide: 2.3.2-3.fc43
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 7 Upstream Release Monitoring 2025-06-25 14:11:14 UTC
Created attachment 2095105 [details]
Update to 2.3.5 (#2356490)

Comment 8 Upstream Release Monitoring 2025-06-25 14:17:43 UTC
the-new-hotness/release-monitoring.org's scratch build of python-pymssql-2.3.5-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=134383796

Comment 9 Upstream Release Monitoring 2025-06-29 05:42:39 UTC
Releases retrieved: 2.3.6
Upstream release that is considered latest: 2.3.6
Current version/release in rawhide: 2.3.2-3.fc43
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 10 Upstream Release Monitoring 2025-06-29 05:42:43 UTC
Created attachment 2095599 [details]
Update to 2.3.6 (#2356490)

Comment 11 Upstream Release Monitoring 2025-06-29 05:48:48 UTC
the-new-hotness/release-monitoring.org's scratch build of python-pymssql-2.3.6-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=134535455

Comment 12 Upstream Release Monitoring 2025-07-11 09:06:19 UTC
Releases retrieved: 2.3.7
Upstream release that is considered latest: 2.3.7
Current version/release in rawhide: 2.3.2-3.fc43
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 13 Upstream Release Monitoring 2025-07-11 09:06:23 UTC
Created attachment 2096980 [details]
Update to 2.3.7 (#2356490)

Comment 14 Upstream Release Monitoring 2025-07-11 09:12:58 UTC
the-new-hotness/release-monitoring.org's scratch build of python-pymssql-2.3.7-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=134750747

Comment 15 Upstream Release Monitoring 2025-10-12 03:02:23 UTC
Releases retrieved: 2.3.8
Upstream release that is considered latest: 2.3.8
Current version/release in rawhide: 2.3.2-7.fc44
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 16 Upstream Release Monitoring 2025-10-12 03:02:27 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-tw9w1u_4/python-pymssql.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1760227200
error: Bad file: ./pymssql-2.3.8.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./pymssql-2.3.8.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 17 Upstream Release Monitoring 2025-10-12 03:02:29 UTC
Created attachment 2109397 [details]
Update to 2.3.8 (#2356490)

Comment 18 Upstream Release Monitoring 2025-11-07 00:19:54 UTC
Releases retrieved: 2.3.9
Upstream release that is considered latest: 2.3.9
Current version/release in rawhide: 2.3.2-7.fc44
URL: https://github.com/pymssql/pymssql

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://docs.fedoraproject.org/en-US/package-maintainers/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/19938/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pymssql

Comment 19 Upstream Release Monitoring 2025-11-07 00:19:57 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-jujn1zw_/python-pymssql.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1762473600
error: Bad file: ./pymssql-2.3.9.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./pymssql-2.3.9.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 20 Upstream Release Monitoring 2025-11-07 00:19:59 UTC
Created attachment 2113108 [details]
Update to 2.3.9 (#2356490)

Comment 21 Charalampos Stratakis 2025-11-10 23:52:35 UTC
This update resolves the FTBFS with the new Cython, but requires setuptools >= 80

Comment 22 Fedora Update System 2025-11-12 08:35:53 UTC
FEDORA-2025-301cad7fa1 (python-pymssql-2.3.9-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-301cad7fa1

Comment 23 Fedora Update System 2025-11-12 08:35:54 UTC
FEDORA-2025-8b99ed4140 (python-pymssql-2.3.9-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8b99ed4140

Comment 24 Fedora Update System 2025-11-13 01:42:38 UTC
FEDORA-2025-301cad7fa1 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-301cad7fa1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-301cad7fa1

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

Comment 25 Fedora Update System 2025-11-13 02:00:04 UTC
FEDORA-2025-c31fd3a435 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c31fd3a435`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c31fd3a435

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

Comment 26 Fedora Update System 2025-11-13 03:16:07 UTC
FEDORA-2025-8b99ed4140 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8b99ed4140`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8b99ed4140

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

Comment 27 Fedora Update System 2025-11-22 01:01:05 UTC
FEDORA-2025-8b99ed4140 (python-pymssql-2.3.9-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 28 Fedora Update System 2025-11-22 01:11:54 UTC
FEDORA-2025-301cad7fa1 (python-pymssql-2.3.9-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 29 Fedora Update System 2025-11-22 01:29:07 UTC
FEDORA-2025-c31fd3a435 (python-pymssql-2.3.9-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.