Bug 2270858 - Review Request: rust-roxmltree0.18 - Represent an XML as a read-only tree
Summary: Review Request: rust-roxmltree0.18 - Represent an XML as a read-only tree
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2250422
TreeView+ depends on / blocked
 
Reported: 2024-03-21 21:21 UTC by Michel Lind
Modified: 2024-03-30 01:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-29 04:10:40 UTC
Type: ---
Embargoed:
ngompa13: fedora-review+


Attachments (Terms of Use)

Description Michel Lind 2024-03-21 21:21:50 UTC
Spec URL: https://salimma.fedorapeople.org/rust-roxmltree0.18.spec
SRPM URL: https://salimma.fedorapeople.org/rust-roxmltree0.18-0.18.1-1.fc39.src.rpm

Description:
Represent an XML as a read-only tree.

Fedora Account System Username: salimma

Comment 1 Neal Gompa 2024-03-21 21:24:18 UTC
Review notes:

* Packaging largely generated by rust2rpm, simplifying reviews
* Packaging follows Rust packaging guidelines
* Package licensing is correct and valid
* Package builds and installs
* No serious issues from rpmlint

PACKAGE APPROVED.

Comment 2 Fedora Admin user for bugzilla script actions 2024-03-21 21:32:27 UTC
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-roxmltree0.18

Comment 3 Fedora Update System 2024-03-21 22:56:41 UTC
FEDORA-EPEL-2024-b4810eef76 (rust-roxmltree0.18-0.18.1-1.el9 and rust-roxmltree-0.19.0-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b4810eef76

Comment 4 Fedora Update System 2024-03-21 22:57:00 UTC
FEDORA-2024-4468834184 (rust-roxmltree0.18-0.18.1-1.fc38 and rust-roxmltree-0.19.0-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-4468834184

Comment 5 Fedora Update System 2024-03-21 22:57:10 UTC
FEDORA-2024-1802ca1080 (rust-roxmltree0.18-0.18.1-1.fc39 and rust-roxmltree-0.19.0-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-1802ca1080

Comment 6 Fedora Update System 2024-03-21 22:57:20 UTC
FEDORA-2024-3be9ba9cf3 (rust-roxmltree0.18-0.18.1-1.fc40 and rust-roxmltree-0.19.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-3be9ba9cf3

Comment 7 Fedora Update System 2024-03-21 22:57:33 UTC
FEDORA-2024-5ed5cc7e72 (rust-roxmltree0.18-0.18.1-1.fc41 and rust-roxmltree-0.19.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5ed5cc7e72

Comment 8 Fedora Update System 2024-03-21 23:02:20 UTC
FEDORA-2024-5ed5cc7e72 (rust-roxmltree0.18-0.18.1-1.fc41 and rust-roxmltree-0.19.0-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 9 Fedora Update System 2024-03-22 01:55:57 UTC
FEDORA-EPEL-2024-b4810eef76 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b4810eef76

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

Comment 10 Fedora Update System 2024-03-22 02:09:30 UTC
FEDORA-2024-3be9ba9cf3 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3be9ba9cf3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3be9ba9cf3

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

Comment 11 Fedora Update System 2024-03-22 02:11:23 UTC
FEDORA-2024-4468834184 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4468834184`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4468834184

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

Comment 12 Fedora Update System 2024-03-22 02:35:39 UTC
FEDORA-2024-1802ca1080 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1802ca1080`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1802ca1080

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

Comment 13 Fedora Update System 2024-03-29 04:10:40 UTC
FEDORA-2024-3be9ba9cf3 (rust-roxmltree0.18-0.18.1-1.fc40 and rust-roxmltree-0.19.0-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2024-03-30 00:37:14 UTC
FEDORA-EPEL-2024-b4810eef76 (rust-roxmltree0.18-0.18.1-1.el9 and rust-roxmltree-0.19.0-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2024-03-30 01:09:24 UTC
FEDORA-2024-1802ca1080 (rust-roxmltree0.18-0.18.1-1.fc39 and rust-roxmltree-0.19.0-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2024-03-30 01:44:11 UTC
FEDORA-2024-4468834184 (rust-roxmltree0.18-0.18.1-1.fc38 and rust-roxmltree-0.19.0-1.fc38) has been pushed to the Fedora 38 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.