dotnet-sig / dotnet-2-1

#3 Update to .NET Core Runtime 2.1.2 and SDK 2.1.302
Merged by rhea. Opened by omajid.
dotnet-sig/ omajid/dotnet-2-1 master  into  master

Download 3.patch

Build here: https://copr.fedorainfracloud.org/coprs/g/dotnet-sig/dotnet/build/789492/

I have actually run out of space on fedorapeople.org. So I am looking for alternative hosting locations. But the SRPM should include the source tarball. Either way, the tarball can be built from cloning source-build repo and running ./build-source-tarball.sh dotnet-%{runtime_version}; tar cvzf dotnet-%{runtime_version}.tar.gz dotnet-%{runtime_version}

Edit: fixed title. I will open a separate PR for 2.1.3/2.1.401

rebased onto 64ff682878628eadf661624f1de439b51d97e709

This went from 2%{?dist} to 1%{?dist}, is that number supposed to reset instead of increment?

Other than my one question, this looks fine to me.

RPM package versions are split into 2 pieces: the upstream version (called Version) and the RPM-version (called the Release). It's expected that Release is reset every time Version is bumped.

https://fedoraproject.org/wiki/Packaging:Versioning#Simple_versioning:

Use a Release: tag starting with 1 (never 0). Append the Dist tag. Increment the release (by 1) for each update you make. Reset to 1 whenever you change Version:.

Pull-Request has been merged by rhea
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.