05:30:21 <paragan> #startmeeting i18n
05:30:21 <zodbot> Meeting started Mon Mar 21 05:30:21 2022 UTC.
05:30:21 <zodbot> This meeting is logged and archived in a public location.
05:30:21 <zodbot> The chair is paragan. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
05:30:21 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
05:30:21 <zodbot> The meeting name has been set to 'i18n'
05:30:22 <paragan> #meetingname i18n
05:30:22 <zodbot> The meeting name has been set to 'i18n'
05:30:22 <paragan> #topic agenda and roll call
05:30:22 <paragan> #link https://fedoraproject.org/wiki/I18N/Meetings/2022-03-21
05:31:19 <juhp[m]> hello
05:31:40 <pwu> hi
05:32:06 <paragan> I think we 3 are only
05:32:27 <paragan> should we proceed or cancel this meeting?
05:32:53 <paragan> #chair juhp[m] pwu
05:32:53 <zodbot> Current chairs: juhp[m] paragan pwu
05:33:31 <juhp[m]> Anything particular to discuss?
05:34:53 <paragan> I think only about hunspell package update, that it should be fixed and available in latest F36 Beta RC iso
05:35:13 <paragan> #info https://bugzilla.redhat.com/show_bug.cgi?id=2064189
05:35:16 <juhp[m]> Okay
05:35:25 <pwu> Cool
05:35:34 <juhp[m]> Hope we will see an another Beta RC soon
05:36:06 <paragan> current target Beta release is on 29th March
05:36:16 <juhp[m]> Seems all the blockers have been addressed fortunately
05:36:47 <paragan> #info https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist
05:37:47 <paragan> yes
05:40:12 <juhp[m]> I just saw some more comments were added to the hunspell bug, which I had missed
05:40:53 <paragan> yeah I already read them
05:41:35 <paragan> good to see some insights by Michal Domonkos there
05:44:53 <juhp[m]> I moved the Cangjie bug to ON_QA
05:46:14 <juhp[m]> https://pagure.io/workstation-ostree-config/pull-request/271
05:46:43 <paragan> yeah I am surprised that Change bug is not even considered by bcotton for any FESCo reporting
05:47:21 <juhp[m]> ohh
05:47:27 <paragan> I mean generally there comes some comment to move bug status, there was no such comments on https://bugzilla.redhat.com/show_bug.cgi?id=2046333
05:47:30 <juhp[m]> Well maybe because it was in NEW?
05:48:17 <paragan> I don't think so. Maybe some other reason
05:48:21 <juhp[m]> Let's include the tracking bugs in our tracking tickets so it is easier to follow along
05:48:38 <juhp[m]> ah right
05:48:40 <paragan> Ok
05:48:57 <juhp[m]> I think we missed this one too
05:49:07 <juhp[m]> At least I did
05:50:03 <juhp[m]> Returning to KDE - I thought imsettings-systemd was getting installed now but need to recheck - the ongoing Freeze quite hampers testing and development
05:50:15 <juhp[m]> ah maybe not for Kinoite
05:51:30 <paragan> Ok
05:53:39 <juhp[m]> I will try to retest ibus on KDE this week
05:54:22 <paragan> ok
05:55:21 <juhp[m]> And I will open a PR to add a weak dep for gtk2 on ibus-gtk2
05:57:44 <juhp[m]> Anything else?
05:59:57 <fujiwara> Do you wish the dependency instead of the recommendation?
06:03:03 <juhp[m]> I think a rich dependency should be fine
06:03:22 <juhp[m]> fujiwara: do you prefer to carry it in ibus.spec?
06:03:24 <fujiwara> ok
06:03:47 <fujiwara> I think it cannot be resolved in ibus
06:04:05 <juhp[m]> I was about to open a PR for gtk2
06:04:22 <fujiwara> ok
06:04:49 <juhp[m]> It might be good to add one later for gtk3 too
06:05:16 <juhp[m]> and maybe ibus-qt
06:06:21 <fujiwara> maybe
06:07:05 <juhp[m]> Though it should be symmetric - so it shouldn't really matter whether the rich dep is in gtk or ibus
06:07:50 <fujiwara> ? I think it cannot be resolved in ibus.
06:08:49 <juhp[m]> It can
06:09:42 <juhp[m]> I think
06:10:55 <juhp[m]> eg https://pagure.io/fedora-workstation/issue/180#comment-735251
06:12:48 <juhp[m]> Let's finish the meeting?
06:13:18 <paragan> Sure
06:13:29 <paragan> thanks for this discussion
06:13:34 <paragan> #endmeeting