-
Notifications
You must be signed in to change notification settings - Fork 0
Fix all the violations and warnings #29
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
base: release-9.0
Are you sure you want to change the base?
Conversation
/retest |
Hi @rakshithakamath94, you'll need to set |
actually, I went ahead and added back |
ea31427
to
d273113
Compare
/retest |
1 similar comment
/retest |
b025643
to
e6d05ae
Compare
/retest |
c2e708d
to
68513a2
Compare
/retest |
b34482d
to
98fa334
Compare
/retest |
f1dfcb5
to
f2e3b99
Compare
/retest |
9821dcc
to
c3ff4bc
Compare
/retest |
1 similar comment
/retest |
8f32ef6
to
d6699ab
Compare
/retest |
388c0fa
to
0d6b8ad
Compare
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once I get my work in for rhel10 can you please rebase this to pull in the new rpms.repo, compose.repo and rpms.lock.yaml? We might have to finish up the rpm and compose related violations in another PR so that I can coordinate it with the container automation.
"options": { | ||
"dnf": { | ||
"odcs-4414456": { | ||
"rhceph-8-tools-for-rhel-9-x86_64-rpms": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we get the rhceph-9-*
repo ids created and allowed?
946c67d
to
56cca83
Compare
Signed-off-by: Rakshitha-Kamath <[email protected]>
56cca83
to
28f98e8
Compare
No description provided.