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

devel-project: automatically prune devel-whitelist once included as devel project #1018

Open
jberry-suse opened this issue Jul 19, 2017 · 6 comments

Comments

@jberry-suse
Copy link
Contributor

Seems reasonable to automatically remove projects from devel-whitelist in remote config (#1014) once they are elevated to a devel project.

@jberry-suse
Copy link
Contributor Author

Would seem to make sense to just make it part of list --write otherwise perhaps add --prune option, but that should be included in nightly run on packagelists.

@akshat5302
Copy link

Is this issue is open??
I would like to contribute to it if open please elaborate on it...

@coolo
Copy link
Member

coolo commented Mar 21, 2022

Yeah, the issue is open. But 'less complex' is mostly relative - for someone understanding the full context, not really for initial contributors.

@akshat5302
Copy link

From where to start I'm interested @coolo

@coolo
Copy link
Member

coolo commented Mar 22, 2022

Well, this is what I mean - Jimmy labeled it "less complex", but meant for himself :)

I don't even think it's possible for a bot to write the OSRT:Config attribute. But this is what the issue is asking for: compare the devel project whitelist in the config with the existing devel projects (calculcated in list mode) and if the whitelist contains an existing project, erase it from the config's white list.

I'll remove the tag

@akshat5302
Copy link

Ok @coolo

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

3 participants