Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect key file location in linux rpm packages-microsoft-prod-1.0-1.noarch #111757

Open
KnHell opened this issue Jan 23, 2025 · 0 comments
Open
Labels
area-Setup untriaged New issue has not been triaged by the area owner

Comments

@KnHell
Copy link

KnHell commented Jan 23, 2025

Description

The package mentioned above contains an incorrect URL for the key file. January 20th this was changed to
https://packages.microsoft.com/centos/8/prod/repodata/repomd.xml.key
but the package still incorrectly holds the old location, effectively eliminating any attempts to eg install dotnet7

Reproduction Steps

Install packages-microsoft-prod-1.0-1.noarch and try yum search for eg aspnet-runtime. This fails. Changing the key file location in /etc/yum.repos.d/microsoft-prod.repo fixes this

Expected behavior

yum search aspnet should return a nonempty string

Actual behavior

yum search aspnet produces nothing, should have produced a package location

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jan 23, 2025
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jan 23, 2025
@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Setup untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

3 participants