The FTI bugs say you can ask on devel.org Example: https://bugzilla.redhat.com/show_bug.cgi?id=2220568#c1 It should probably be https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ instead
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
People that need help might not know where to get help
PS: I could not find the text in this repo - git grep devel.org returns nothing, so no clue where this needs to be fixed.
git grep devel.org
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Hi @davidsch, so in the comment on BZ there is a link to the repo that is generating that message. Here is the msg template https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/reminder-fti.j2
I don't understand how this happened, maybe some glitch while parsing the template?
The email that I got from bugzilla says:
https://bugzilla.redhat.com/show_bug.cgi?id=2220568 Fedora Fails To Install <fti-bugs@fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(david08741@gmail. | |com) --- Comment #1 from Fedora Fails To Install <fti-bugs@fedoraproject.org> --- Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on devel@lists.fedoraproject.org if you are unsure how to fix this bug.
So this looks like the Bugzilla web interface hides that address and converts it to "devel.org" -- but only when I am not logged in.
We could use the link instead of the email address to work around this weird behavior (probably designed to hide email addresses from spammers).
Thanks for the investigation, that explains why I couldn't find it git-grep'ing for devel.org. That is ceratinly some (for me) unexpected behavior in bugzilla.
I wanted to open a PR, but that complains that the commit isn't signed. Is that intentionally? Can it be done from the web interface?
I have no idea why this repository enforces signed commits. It can be done from a web interface but I am afraid once you've done it without the required bit in the commit message, Pagure won't let you amend it :(
I've opened https://pagure.io/releng/issue/11587 as a followup for this requirement.
Enforce signed-off commits in pull-request are marked optional now!
Metadata Update from @churchyard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)