I would say that the current way is OK, the bot asks fedora-scm-requests
admins to validate the requests, because it is marked as exception.
After being validated it gets created.
Or if there should be an exception for Rust packages, we can add name
validation and if the name of the package is rust something, we can skip
the validation process. But this unfortunately let people create any
repository with name rust with exception set to true without any
validation and I'm not sure if we want this.
The solution from kevin that the fedpkg request will actually say that
it's a compat request and provides name of the previous package, it
could be validated by bot itself and automated. Right now the bot
doesn't really know if this is a compat package or not, the request
doesn't have that info.
Michal
On 18. 01. 23 23:13, Kevin Fenzi wrote:
On Wed, Jan 18, 2023 at 12:36:35PM -0600, Michel Alexandre Salim wrote:
Hi Michal,
On Wed, 2023-01-11 at 17:13 +0100, Michal Konecny wrote:
Hi everyone,
all the remaining issues were solved and the bot is now processing
tickets as it should. I will watch the SCM request repository for
next few days to see if everything is working as it should.
Thanks for your patience.
Where can I direct feature requests? Per
https://pagure.io/releng/fedora-scm-requests/issue/50507 seems like
requesting repos with exceptions (e.g. for Rust compat packages) is
currently not automated.
I'm not sure how we can automate this.
I mean I guess we could just check that the requestor is a packager and
let them create any package name they wish? Or is there some programic
way we can tell it's a compat package and that its correctly named?
Perhaps we could extend fedpkg to ask for and provide more info to the
processing ticket? like name of orig package (check that it exists, etc)
and that the new compat package has a name thats based on it?
Thoughts?
kevin
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
