https://bugzilla.redhat.com/show_bug.cgi?id=1814349
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Rename Request: |Rename Request:
|google-caladea-fonts - |ht-caladea-fonts - Caladea,
|Caladea, a serif font |a serif font family
|family metric-compatible |metric-compatible with
|with Cambria font family |Cambria font family
--- Comment #12 from Parag Nemade <pnemade(a)redhat.com> ---
I am sorry for not changing this review request bug summary. I am going to
retire google-caladea-fonts now and will request again new ht-caladea-fonts
package request.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823721
Bug ID: 1823721
Summary: gettext-0.20.2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Keywords: FutureFeature, Triaged
Assignee: petersen(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jjanco(a)redhat.com, nphilipp(a)redhat.com,
petersen(a)redhat.com, praiskup(a)redhat.com,
suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.20.2
Current version/release in rawhide: 0.20.1-4.fc32
URL: http://www.gnu.org/software/gettext/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/898/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1569354
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
CC| |pnemade(a)redhat.com
Resolution|--- |WORKSFORME
Last Closed| |2020-04-27 15:09:13
--- Comment #1 from Parag Nemade <pnemade(a)redhat.com> ---
The MATE Compiz Live iso run showed below packages
[liveuser@localhost-live ~]$ rpm -qa | grep ims
imsettings-1.8.2-1.fc32.x86_64
imsettings-mate-1.8.2-1.fc32.x86_64
imsettings-libs-1.8.2-1.fc32.x86_64
[liveuser@localhost-live ~]$
After installing F32 MATE system, I see still same results that is no
imsettings-gsettings package installed on the system.
[test@localhost ~]$ rpm -qa imsettings-mate mate-settings-daemon
imsettings-gsettings
mate-settings-daemon-1.24.0-1.fc32.x86_64
imsettings-mate-1.8.2-1.fc32.x86_64
[test@localhost ~]$
Therefore, This bug is already fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1405539
Kamil Páral <kparal(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|RejectedBlocker |RejectedBlocker
| |https://fedoraproject.org/w
| |iki/Common_F32_bugs#keyboar
| |d-layout-update-plymouth
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #10 from Akira TAGOH <tagoh(a)redhat.com> ---
(In reply to Hans Ulrich Niedermann from comment #8)
> I have removed the terminus-fonts package, and automagically the
> gnome-terminal terminal and the gnome-terminal font selection dialog have
> changed to stop including terminus. After re-installing the terminus-fonts
> package, both have automagically started showing terminus fonts again. This
> behaviour is the same both with the older terminus-fonts-4.48-3.fc32.noarch
> package (with updates-testing disabled) and (with updates-testing enabled)
> the newer terminus-fonts-4.48-5.fc32.noarch package.
Right. that should works on WS. and is the off topic for this issue and misled
by comment#1. please ignore it.
> However, nobody needs to select those broken italic version from the font
> selection box, as the fonts actually provided by terminus-fonts are in
> perfect working order. The user experience is certainly better if you
> install "terminus-fonts" if you want to use the Terminus font inside, say,
> your gnome-terminal and emacs, and just ignore the obviously broken italic
> font variant. The alternative is a separate package with legacy fonts for
> Emacs, and the user having to find out about actually needing the legacy
> variant package, then installing that legacy variant package in addition to
> the standard one to have Terminus for both gnome-terminal and Emacs, and
> then they see the broken italic font variants in the gnome-terminal font
> selection dialog again.
Right.. In that sense, applications which are going to deal with un-supported
format should ignore them in their code to query fonts, in general at least.
(In reply to Hans Ulrich Niedermann from comment #9)
> So... is this actually just a duplicate of
> <https://bugzilla.redhat.com/show_bug.cgi?id=1750891>?
No, I don't think so.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1814349
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|nobody(a)fedoraproject.org |nicolas.mailhot(a)laposte.net
--- Comment #10 from Parag Nemade <pnemade(a)redhat.com> ---
Thank you for this package review.
Will remove that macro before package import.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #9 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> ---
So... is this actually just a duplicate of
<https://bugzilla.redhat.com/show_bug.cgi?id=1750891>?
FWIW, I have just created a bug describing the italic issue at
<https://bugzilla.redhat.com/show_bug.cgi?id=1827905> because regardless of
whether the legacy fonts are inside terminus-fonts or split off into
terminus-fonts-legacy-foo, that issue will stay with us for a few more years
until software using the legacy font rendering is actually out of circulation.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #8 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> ---
I have updated my F31 system to F32 yesterday specifically for reproducing this
issue. However, my gnome-terminal font selection dialog behaves exactly the
same on F32 as it did on F31. It shows four font variants, two of which are
actually provided by the terminus-fonts package, and two of which are invented
by the fonts software stack for some reason:
Terminus Medium
Terminus Bold
<series of unicode hex code glyphs>
Terminus Bold Italic
Anyway, the reporter of this bug is showing something *very* different: His
gnome-terminal font selection dialog shows four apparent font variants in a
very diffent way:
<series of rectangles>
<series of rectangles>
<series of unicode hex code glyphs>
<series of rectangles>
(BTW, I am still looking for the proper term for those unicode hex code glyphs.
If you know that term, please let me know.)
I have removed the terminus-fonts package, and automagically the gnome-terminal
terminal and the gnome-terminal font selection dialog have changed to stop
including terminus. After re-installing the terminus-fonts package, both have
automagically started showing terminus fonts again. This behaviour is the same
both with the older terminus-fonts-4.48-3.fc32.noarch package (with
updates-testing disabled) and (with updates-testing enabled) the newer
terminus-fonts-4.48-5.fc32.noarch package.
I interpret this as the font installation and removal working very well and as
intended, and that ostree is messing up those automagical updates to the state
of the font set. So it looks as if ostree/fontconfig or something along those
lines is responsible for the reporter's issue and I cannot see what the
terminus-fonts package could do about this.
So either this bug needs to be address by ostree/fontconfig/something or I just
close it for terminus-fonts.
That the fonts software stack insists on inventing a broken italic version of a
font which explicitly choses not to ship an italic version is an *entirely*
*different* *issue*, and not the topic of this bug.
However, nobody needs to select those broken italic version from the font
selection box, as the fonts actually provided by terminus-fonts are in perfect
working order. The user experience is certainly better if you install
"terminus-fonts" if you want to use the Terminus font inside, say, your
gnome-terminal and emacs, and just ignore the obviously broken italic font
variant. The alternative is a separate package with legacy fonts for Emacs, and
the user having to find out about actually needing the legacy variant package,
then installing that legacy variant package in addition to the standard one to
have Terminus for both gnome-terminal and Emacs, and then they see the broken
italic font variants in the gnome-terminal font selection dialog again.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #7 from Parag Nemade <pnemade(a)redhat.com> ---
If I remove the all *.pcf.gz fonts, I can see correct rendering for Italic font
on Fedora 32.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1814349
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|fedora-review? |fedora-review+
--- Comment #9 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
You can probably remove the following line, looks like a cut & paste leftover
%global fontsex fonts/otf/*SC*otf
And given the description, maybe some Cambo aliasing would be in order (seems
Caladea is the same design, tweaked to fit into Cambria metrics
But, this is fine tuning. The spec works fine and we have a real active
upstream for the font family at last
APPROVED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1134299
Pravin Satpute <psatpute(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |WORKSFORME
Last Closed|2016-07-19 12:04:00 |2020-04-24 11:04:33
--- Comment #23 from Pravin Satpute <psatpute(a)redhat.com> ---
Closing bug as a working for me. Feel free to reopen if problem reproduced
again.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1814349
--- Comment #7 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.zgK8wx
+ umask 022
+ cd /builddir/build/BUILD
+ cd Caladea-336a529cfad3d103d6527752686f8331d13e820a
+ grep -E '^"/usr/share/fontconfig/conf.avail/.+\.conf"'
/builddir/build/BUILD/Caladea-336a529cfad3d103d6527752686f8331d13e820a/ht-caladea-fonts.list
+ xargs '-I{}' -- sh -c 'xmllint --loaddtd --valid --nonet
'\''/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64{}'\''
>/dev/null && echo
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64{}:
OK'
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/30-0-ht-caladea-fonts.conf:2:
warning: failed to load external entity
"/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/fonts.dtd"
<!DOCTYPE fontconfig SYSTEM "../fonts.dtd">
^
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/30-0-ht-caladea-fonts.conf:3:
validity error : Validation failed: no DTD found !
<fontconfig>
^
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/62-ht-caladea-fonts.conf:2:
warning: failed to load external entity
"/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/fonts.dtd"
<!DOCTYPE fontconfig SYSTEM "../fonts.dtd">
^
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/62-ht-caladea-fonts.conf:3:
validity error : Validation failed: no DTD found !
<fontconfig>
^
error: Bad exit status from /var/tmp/rpm-tmp.zgK8wx (%check)
Bad exit status from /var/tmp/rpm-tmp.zgK8wx (%check)
You need to fix your DTD declaration. See also
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
(sorry about this, it was not possible to validate all fontconfig files by
default with the previous macro system)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
Akira TAGOH <tagoh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|fontconfig |terminus-fonts
Assignee|tagoh(a)redhat.com |rhbugs(a)n-dimensional.de
--- Comment #5 from Akira TAGOH <tagoh(a)redhat.com> ---
Ah, well, my comments are basically based on Peng Wu's comment at comment#2
(which is basically same to Bug#1750891) but it seems not what the original
report claims.
That is because terminus-fonts contains two format and Pango/freetype doesn't
support synthesizing the legacy bitmap fonts for Italic. that's why we wanted
to make it sub-packaged to avoid issues.
We may have two options to fix:
1. Separate packages for both OTB and the legacy bitmap
2. Drop legacy bitmap (at least for rawhide according to new font packaging
guidelines)
3. Disable embolden flag for certain apps
I don't know if 2) is really a good idea for f32 though. anyway, this isn't
something we can deal with fontconfig itself. reassigning back to
terminus-fonts.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690295
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2020-04-21 07:28:34
--- Comment #4 from Jens Petersen <petersen(a)redhat.com> ---
For zh_SG this was fixed in langtable-0.0.43-1.fc30, by defaulting SG to en_SG
instead.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #3 from Akira TAGOH <tagoh(a)redhat.com> ---
Think of 3) as a solution/workaround for SB specific, we could assume that
caches having 0 timestamp is always the latest because updates of all the
files under /usr won't appear without reboot on SB and /usr is read-only, and
fc-cache is triggered on %transfiletrigger* in fontconfig rpm.
So it should reasonably works for SB.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495172
vishalvvr <vishalvijayraghavan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(vvijayra(a)redhat.c |
|om) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495172
vishalvvr <vishalvijayraghavan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vishalvijayraghavan(a)gmail.c
| |om
--- Comment #15 from vishalvvr <vishalvijayraghavan(a)gmail.com> ---
(In reply to Akira TAGOH from comment #14)
>
> Vishal, could you report this to upstream as well? or if you already did,
> can you add a link here?
Reported in upstream[1], Thanks
[1] https://gitlab.gnome.org/GNOME/gtk/-/issues/2636
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1825060
Bug ID: 1825060
Summary: Cannot add input method to ibus
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: jon780(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When starting ibus (ibus-daemon --xim or just ibus-daemon) after updating last
night (dnf update) ibus lost my input method (anthy). If I go into preferences
to re-add it, after hitting close and re-opening preferences, it's gone again.
It won't actually save it. Also I get the following output in the terminal
after launching ibus-daemon:
"portal is not running: Timeout was reached"
I've also tried adding other input methods with the same results.
Version-Release number of selected component (if applicable): iBus 1.5.21
How reproducible:
Every time, even after completely rebooting the PC.
Steps to Reproduce:
1. Run ibus-daemon
2. Go to Preferences > Input Method > Add > Japanese > Anthy > Add
3. Click close
4. Re-open Preferences and go to Input Method tab, it will still be empty.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1784430
Bug ID: 1784430
Summary: Please package python3-polib for EPEL 8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: python-polib
Assignee: suanand(a)redhat.com
Reporter: vtrefny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: diegobz(a)gmail.com, dingyichen(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
ivazqueznet(a)gmail.com, moez.roy(a)gmail.com,
reallylongword(a)gmail.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
It's available for EPEL 7 and it would be nice to have it for CentOS/RHEL 8
too.
I'm packager and I can help as a co-maintainer if needed.
--
You are receiving this mail because:
You are on the CC list for the bug.