https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193682#c4 contains a comment added by the ports commit hook. The changelog itself contained one UTF-8 character (in the Submitted by:, "Siebörger") which is present and properly encoded in the commit log mailed out to the lists, but has been replaced by a question mark in the bug's comment. The Bugzilla rendered bug page claims to also be encoded as UTF-8, so it's not clear why the umlaut got lost.
Please change the bug tracker such that UTF-8 characters get properly recorded and rendered.
That should have been https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193682#c3
This might be related due to several issues.
The notifier script for example does not declare a content encoding in the mail being generated, which might then be just reencoded/played safe on picking up the mail.
I'm adding portmgr@ to keep them informed about the test outcome.
Local tests show that it is related to the (missing) content encoding.
@portmgr: Can we assume commit messages to be UTF-8 encoded and add a
echo 'Content-Type: text/plain; charset="UTF-8"'
into hooks/scripts/notify_bz.sh? Otherwise the content encoding is guessed randomly, with a fallback to the executing user's locale.
Internally, Subversion stores everything as UTF-8 encoded unicode, or so the SVNBook.red-bean.com claims:
Now the client (svn) will re-encode according to the locale setting, I'm not sure what svnlook does. So in order to play it safe, you'll probably want to add
or more radical and to the point
to the notify_bz.sh to enforce the declared encoding (C.UTF-8 or POSIX.UTF-8 causes complaining about svn not being able to set LC_CTYPE).
Please test what svnlook renders, I don't currently have a server-side repo at hand.
What's the status of this? Did someone of portmgr@ look into the necessary adjustments for notify_bz.sh?
portmgr@: is there any progress on this issue?
If it's script adjustments, we need to get bugmeister on the hook. Not sure if we can expect much help from portmgr@, so let's just try bugmeister.
Sorry - I see that bugmeister reassigned to portmgr in September already. Reverting my changes.
Any news on this?
Is this an area where non-maintainer commits get reverted?
Else it's time for someone else to invoke maintainer timeout and take action.
I don't see any patch provided in this bug report, why would timeout be invoked?
Also, this probably affects base and docs, it's not specific to ports so I'm not sure portmgr is the right contact (maybe svnadm@ / peter@)
(In reply to Antoine Brodin from comment #12)
> Also, this probably affects base and docs, it's not specific to ports so
> I'm not sure portmgr is the right contact (maybe svnadm@ / peter@)
Yes, it will affect all commits, which also write something into Bugzilla. So the problem will be the same for all different source trees, be it ports, doc or base. The issue is (in my opinion) simple to fix (see comment #3) and "only" would have an impact on Bugzilla comments. Should we give a fix a go?
Got bitten with it in https://bugs.freebsd.org/196964 so adding me to the CC.
@Marcus, is your add code suggestion in comment 3 still valid? If so I can add a patch here. If not, if someone else could that would be great.
Who is the maintainer/owner of the SVN hook scripts? We should assign the Product/Component/Assignee accordingly.
Spoke to Peter on IRC, over to him (and clusteradm). Thanks Pete!
I was planning to make some adjustments to the way bugzilla receives email, I'll take care of this as well.
This is still a problem.