#50662 rpm changes for rust-by-default
Closed: wontfix 3 years ago by spichugi. Opened 4 years ago by firstyear.

Issue Description

After https://pagure.io/389-ds-base/pull-request/50633 we'll be in a position where we can ship dependencies and consider rust-by-default. This may need to spec changes for downstream vendors and their build processes.

This is to add the changes to the upstream spec, but to also work with @mreynolds and @tjaalton to ensure our major distros are all ready for the upcoming change and can coordinate which release will have rust-by-default so that we can begin adding features in the language (looking at fernet sso tokens here as the first most likely).

If there are other distro maintainers I have forgotten please CC them here.


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

4 years ago

Metadata Update from @mreynolds:
- Issue priority set to: major
- Issue set to the milestone: 1.4.3 (was: 1.4.2)

4 years ago

I think we are ready to do this upstream @firstyear. I just tested Fedora 31 and RHEL 8.3 and it built fine (it took a little longer, but it worked).

But for downstream builds we need to gather all the rust "downloads" prior to building, like what we do with the cockpit UI and npm packages. So we need to include this in make -f rpm.mk dist-bz2

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.4 (was: 1.4.3)

3 years ago

But for downstream builds we need to gather all the rust "downloads" prior to building, like what we do with the cockpit UI and npm packages. So we need to include this in make -f rpm.mk dist-bz2

It was added in https://pagure.io/389-ds-base/pull-request/50633

But for downstream builds we need to gather all the rust "downloads" prior to building, like what we do with the cockpit UI and npm packages. So we need to include this in make -f rpm.mk dist-bz2

It was added in https://pagure.io/389-ds-base/pull-request/50633

Awesome, then we can move forward with this!

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3717

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata