Bug 2119077 - libxml2-2.10.2 is available
Summary: libxml2-2.10.2 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libxml2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-17 13:22 UTC by Upstream Release Monitoring
Modified: 2022-11-13 01:12 UTC (History)
1 user (show)

Fixed In Version: libxml2-2.10.3-1.fc36 libxml2-2.10.3-2.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-25 13:12:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources libxml2 pull-request 12 0 None None None 2022-09-08 13:56:00 UTC

Description Upstream Release Monitoring 2022-08-17 13:22:51 UTC
Releases retrieved: 2.10.0
Upstream release that is considered latest: 2.10.0
Current version/release in rawhide: 2.9.14-3.fc37
URL: http://xmlsoft.org/

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/1783/


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

Comment 1 Upstream Release Monitoring 2022-08-17 13:22:55 UTC
Scratch build failed. Details below:

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

StdOut:
error: Bad source: ./libxml2-2.10.0.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/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.10/site-packages/hotness/builders/koji.py", line 188, 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 2022-08-25 12:00:02 UTC
Releases retrieved: 2.10.1
Upstream release that is considered latest: 2.10.1
Current version/release in rawhide: 2.9.14-3.fc37
URL: http://xmlsoft.org/

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/1783/


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

Comment 3 Upstream Release Monitoring 2022-08-25 12:00:06 UTC
Scratch build failed. Details below:

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

StdOut:
error: Bad source: ./libxml2-2.10.1.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/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.10/site-packages/hotness/builders/koji.py", line 188, 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 4 Upstream Release Monitoring 2022-08-29 15:31:35 UTC
Releases retrieved: 2.10.2
Upstream release that is considered latest: 2.10.2
Current version/release in rawhide: 2.9.14-3.fc37
URL: http://xmlsoft.org/

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/1783/


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

Comment 5 Upstream Release Monitoring 2022-08-29 15:31:39 UTC
Scratch build failed. Details below:

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

StdOut:
error: Bad source: ./libxml2-2.10.2.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/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.10/site-packages/hotness/builders/koji.py", line 188, 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 6 Fedora Admin user for bugzilla script actions 2022-08-31 00:56:20 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 7 Fedora Admin user for bugzilla script actions 2022-08-31 12:44:29 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 8 Fedora Update System 2022-10-20 15:05:08 UTC
FEDORA-2022-a6812b0224 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a6812b0224

Comment 9 Fedora Update System 2022-10-20 15:20:35 UTC
FEDORA-2022-aeafd24818 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-aeafd24818

Comment 10 Fedora Update System 2022-10-20 18:21:40 UTC
FEDORA-2022-a6812b0224 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a6812b0224`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a6812b0224

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

Comment 11 Fedora Update System 2022-10-21 09:47:57 UTC
FEDORA-2022-aeafd24818 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-aeafd24818`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-aeafd24818

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

Comment 12 Fedora Update System 2022-10-21 12:08:12 UTC
FEDORA-2022-fcf5dbb447 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fcf5dbb447

Comment 13 Fedora Update System 2022-10-22 14:55:23 UTC
FEDORA-2022-fcf5dbb447 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fcf5dbb447`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fcf5dbb447

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

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

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

Comment 15 Fedora Update System 2022-10-24 14:13:45 UTC
FEDORA-2022-aeafd24818 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-aeafd24818`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-aeafd24818

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

Comment 16 Fedora Update System 2022-10-24 14:19:43 UTC
FEDORA-2022-fcf5dbb447 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fcf5dbb447`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fcf5dbb447

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

Comment 17 Fedora Update System 2022-10-25 13:12:58 UTC
FEDORA-2022-aeafd24818 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2022-11-01 14:46:52 UTC
FEDORA-2022-a6812b0224 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a6812b0224`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a6812b0224

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

Comment 19 Fedora Update System 2022-11-04 08:54:42 UTC
FEDORA-2022-a6812b0224 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a6812b0224`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a6812b0224

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

Comment 20 Fedora Update System 2022-11-04 10:55:34 UTC
FEDORA-2022-fcf5dbb447 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fcf5dbb447`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fcf5dbb447

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

Comment 21 Fedora Update System 2022-11-13 01:12:30 UTC
FEDORA-2022-a6812b0224 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.