* Josh Boyer: >> * TOPIC: Next Week's Chair (@sgallagh:fedora.im, 17:34:58) >> * INFO: 2024-11-26 meeting is CANCELED due to lack of expected >> quorum (@sgallagh:fedora.im, 17:39:34) >> * INFO: F42/F43 Election questions will be reviewed and approved >> async using the FastTrack process (@sgallagh:fedora.im, 17:40:24) >> * ACTION: zbyszek to chair 2024-12-03 meeting >> (@sgallagh:fedora.im, 17:41:29) >> * TOPIC: Open Floor (@sgallagh:fedora.im, 17:41:43) >> * INFO: nirik raised an issue with a package whose name exceeded >> the maximum size of components for Bugzilla. FESCo recommends that the >> package be renamed in Fedora, citing technical limitations. We should >> also document this and, ideally, update fedora-package-review. >> (@sgallagh:fedora.im, 17:52:12) > > The character limit is 64. > >> * INFO: Addendum: also modify fedora-scm-requests to detect this. >> (@sgallagh:fedora.im, 17:53:27) > > Random observation: the limit should probably be the tool in the > pipeline that has the most restrictive component limit. I'd hope that > would be bugzilla, but with a potential new git forge it might be > worth checking there too. I think Neal was alluding to this in the > chat. Historically, forge limits have been handled by rewriting SRPM names in tools similar to fedpkg and fedpkg-simple. I still think we should ban package names containing + and consisting entirely of keywords (“tree”). The rewriting tends to leak all over the place. Thanks, Florian -- _______________________________________________ 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
