Bug 239227 - Bugzilla does not auto-assign bugs properly anymore
Summary: Bugzilla does not auto-assign bugs properly anymore
Status: In Progress
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Oleksandr Tymoshenko
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2019-07-15 15:19 UTC by Tobias Kortkamp
Modified: 2019-07-16 01:58 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Kortkamp freebsd_committer 2019-07-15 15:19:58 UTC 
The auto-assigner for Ports bugs does not seem to work properly anymore.

It failed to add the maintainer-feedback fields to bug #239225, bug #239222,
or bug #239195 for example.

Bug #239195 should ask have been assigning to kde@ automatically, bug #239222
to me.

Maybe I am missing an obvious mistake in those bugs though.
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2019-07-16 01:34:03 UTC 
Thanks for the report Tobias.

Bugmeister is aware of this (as of yesterday) and is investigating
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2019-07-16 01:46:41 UTC 
Error observed with (loading) bug 239231, in case you didnt see it:

Global symbol "$s" requires explicit package name (did you forget to declare "my $s"?) at ./extensions/FBSDAutoAssign/Extension.pm line 82.
Compilation failed in require at Bugzilla/Extension.pm line 71.
Comment 3 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2019-07-16 01:54:44 UTC 
(In reply to Kubilay Kocak from comment #2)

Fat fingers on my side, fixed now.
Comment 4 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2019-07-16 01:58:21 UTC 
There is a problem with host/jail versions that caused to fail command that obtains information about maintainer: 

make: "/home/ports/Mk/bsd.port.mk" line 1189: UNAME_r (12.0-BETA3) and OSVERSION (1101515) do not agree on major version number.

As a workaround, I put UNAME_r=11.0-RELEASE env variable to the command. I'll try to come up with a more permanent solution.