How can I specify the Version for the dotnet rpm command? #90

New Issue

claunia · 2026-01-29T16:29:18Z

claunia commented

2026-01-29 16:29:18 +00:00

Originally created by @SparkyTD on GitHub (Dec 2, 2020).

Before using this project, I was deploying to linux by using dotnet publish and passing the version (a git tag) as a -p:Version=$currentTag parameter to it. Unfortunately it seems like dotnet rpm doesn't accept this command line argument, and the only way to specify the rpm's version is by changing the <Version> tag in the .csproj file.

Is there a better way to pass a version to dotnet when creating an rpm so I can integrate this tool into my deployment pipeline?

Originally created by @SparkyTD on GitHub (Dec 2, 2020). Before using this project, I was deploying to linux by using `dotnet publish` and passing the version (a git tag) as a `-p:Version=$currentTag` parameter to it. Unfortunately it seems like dotnet rpm doesn't accept this command line argument, and the only way to specify the rpm's version is by changing the `<Version>` tag in the .csproj file. Is there a better way to pass a version to dotnet when creating an rpm so I can integrate this tool into my deployment pipeline?

claunia commented

2026-01-29 16:29:19 +00:00

@markpendlebury commented on GitHub (Oct 23, 2021):

+1 this issue is the reason i'm no longer using this package. It's massivley overly complicated to update the version number in CI due to this. Having to change the version number as part of my ci and create an additional commit simply to bump the version number just isn't feasable.

If we could pass the version number in from a parameter for example dotnet deb --version=${VERSION_NUMBER} i'll start using this package again, until then i'm back to doing it manually

@markpendlebury commented on GitHub (Oct 23, 2021): +1 this issue is the reason i'm no longer using this package. It's massivley overly complicated to update the version number in CI due to this. Having to change the version number as part of my ci and create an additional commit simply to bump the version number just isn't feasable. If we could pass the version number in from a parameter for example `dotnet deb --version=${VERSION_NUMBER}` i'll start using this package again, until then i'm back to doing it manually

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dotnet-packaging#90