Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1886170 - Rust Crate Packages For Release Branches
Summary: Rust Crate Packages For Release Branches
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F34Changes
TreeView+ depends on / blocked
 
Reported: 2020-10-07 19:28 UTC by Ben Cotton
Modified: 2020-10-15 13:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-15 13:20:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ben Cotton 2020-10-07 19:28:44 UTC 
This is a tracking bug for Change: Rust Crate Packages For Release Branches
For more details, see: https://fedoraproject.org/wiki/Changes/Rust_Crate_Packages_For_Release_Branches

This Change proposal aims to enable shipping Rust crate packages (rust-$CRATE_NAME) on release branches of fedora.
Currently, they are only available for rawhide, which makes building Rust packages for release branches difficult.
Comment 1 Fabio Valentini 2020-10-08 14:34:36 UTC 
Pull Request for releng scripts:
https://pagure.io/releng/pull-request/9798
Comment 2 Fabio Valentini 2020-10-15 11:11:07 UTC 
The releng script changes have been merged.

No other changes are necessary to implement this Change (though I continue to work through the Rust stack to get it into its best possible shape before the f34 branch point to minimize the Change impact).

So from my point of view, this tracking bug can be closed.
Comment 3 Ben Cotton 2020-10-15 13:20:21 UTC 
Closing. Since I now use a tracking bug for changes, this will still get branched appropriately.
Note You need to log in before you can comment on or make changes to this bug.