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

[Issue]:6.1.x default.xml loss definition of <remote name="KhronosGroup"> #3146

Closed
SpinEch0 opened this issue May 22, 2024 · 6 comments
Closed

Comments

@SpinEch0
Copy link

Problem Description

branch 6.1.x

repo init faile with wrong manifest:

fatal: manifest 'default.xml' not available
fatal: remote KhronosGroup not defined in .repo/manifests/default.xml
================================================================================
Repo command failed: UpdateManifestError
	Unable to sync manifest default.xml

Operating System

macos

CPU

none

GPU

AMD Instinct MI300X

ROCm Version

ROCm 6.1.0

ROCm Component

ROCm

Steps to Reproduce

No response

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support

No response

Additional Information

No response

@SpinEch0 SpinEch0 changed the title [Manifest]:6.1.x default.xml loss definition of <remote name="KhronosGroup"> [Issue]:6.1.x default.xml loss definition of <remote name="KhronosGroup"> May 22, 2024
@ppanchad-amd
Copy link

@SpinEch0 Please provide OS and steps to reproduce your issue? Thanks!

@lgrz
Copy link

lgrz commented May 28, 2024

Remote name for KhronosGroup is missing from the default.xml:

https://github.com/ROCm/ROCm/pull/3098/files#diff-d9b8e4a48f8e111ec5d21480d9d33a893b365dfa7f8550bbc0577e4d42afeac8L4

@perovskikh
Copy link
Contributor

I suggest #3172 gh pr checkout 3172

@SpinEch0
Copy link
Author

I suggest #3172 gh pr checkout 3172
yes, this pr solves the problem, I close the issue.

@saadrahim saadrahim reopened this May 29, 2024
@saadrahim
Copy link
Member

Don't close an issue until the PR is merged.

@samjwu
Copy link
Member

samjwu commented May 29, 2024

@samjwu samjwu closed this as completed May 29, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants