December 2016 - i18n-bugs - Fedora Mailing-Lists

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 --- Comment #13 from Jonathan Underwood <jonathan.underwood(a)gmail.com> --- OK, I mostly buy that. But, I think you're arguing that this is data for fontconfig (and applications using it), so it might more naturally fit under /usr/share/fontconfig than /usr/lib/fontconfig. Right? -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 --- Comment #12 from Matthew Miller <mattdm(a)redhat.com> --- I agree with Colin's assessment that the FHS doesn't really cover this situation well. From the section on /var: /var is specified here in order to make it possible to mount /usr read-only. Everything that once went into /usr that is written to during system operation (as opposed to installation and software maintenance) must be in /var. But here, we're talking about stuff that is written specifically and only during "installation and software maintenance". That's just not well-accounted-for in the spec. Generate-at-build-time as I suggest above might (I hope) work for fontconfig, but it won't for /etc/ld.so.cache -- and I guess that living in /etc may be a reflection of the above problem. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 Matthew Miller <mattdm(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mattdm(a)redhat.com --- Comment #11 from Matthew Miller <mattdm(a)redhat.com> --- Rather than moving the cache around -- or, I guess, in addition to it, but obviating an concern about FHS or dyanamic, unmanaged files in /usr, could we just pregenerate the cache files at _build_ time rather than install time? They appear to be arch specifc (well, word size and order specific) but not really host-specific. Bonus: faster system install (when not using ostree; I guess faster ostree generation too). -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 --- Comment #10 from Colin Walters <walters(a)redhat.com> --- Rather than thinking of the above things as "caches", they're more like "indexes" or "lookup tables". The distinction is that they're *only* written or generated during a software installation. A good example of another one of these to move to /usr would be /etc/ld.so.cache. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 --- Comment #9 from Colin Walters <walters(a)redhat.com> --- There's many other derived caches in /usr. gtk-update-icon-cache is one offhand. GNU info pages (`install-info`). kernel modules (depmod -a). Remember that in the ostree model: https://ostree.readthedocs.io/en/latest/manual/adapting-existing/ Things like the RPM database are also moved to /usr/share/rpm. OSTree also *enforces* that /usr is read-only at runtime - but with rpm-ostree, we construct a new tree on the client side, and run %posts there with it mutable, then it's sealed back up at runtime. An important thing to keep in mind with the FHS is that they tried to push for having /usr be NFS mountable, which Fedora (and all systemd systems), don't support. It's just not relevant - it's easier to NFS mount /, and do something like ostree on the server to dedup the /usr content between different hosts. Basically, the FHS requirements are from a previous mindset - the https://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken/ merge pushed the semantics for /usr in a different direction, and OSTree goes much farther with it. The main concern I have here about breaking things is more around upgrades for people who are using yum/dnf on the host. I could probably change rpm-ostree to include an e.g. `OSTREE_SEMANTICS=1` environment variable, and the fontconfig %post could key off that. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 Vít Ondruch <vondruch(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vondruch(a)redhat.com --- Comment #8 from Vít Ondruch <vondruch(a)redhat.com> --- (In reply to Jonathan Underwood from comment #6) > Unfortunately this proposal isn't compatible with the FHS requirements Agree with this. Can't see how /usr could be the right choice. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 --- Comment #7 from Jonathan Underwood <jonathan.underwood(a)gmail.com> --- .. by "read only" I really mean static rather than dynamically generated. /var/cache really is the right location for this sort of thing. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1377367] fontconfig cache in /var incompatible with ostree model; unable to `rpm-ostree install emacs`

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1377367 Jonathan Underwood <jonathan.underwood(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.underwood(a)gmail.co | |m --- Comment #6 from Jonathan Underwood <jonathan.underwood(a)gmail.com> --- Unfortunately this proposal isn't compatible with the FHS requirements of /usr, which is supposed to be read only. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1405629] Feature request for changing ibus keyboard shortcuts ( Ctrl + Shift + e, Ctrl +Shift + u, ...) or for disabling them

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1405629 --- Comment #2 from fujiwara <tfujiwar(a)redhat.com> --- I have the plan to customize Ctrl-Shift-e after the UI is moved from IBusEngineSimple to IBusPanel. But I have no plan to change Ctrl-Shift-u until Gtk will be changed since IBus inherit that implementation from GtkIMContextSimple which does not use GSettings. I may drop Ctrl-Shift-u if the emoji typing can combined the Unicode typing too but not sure until the actual implementation is done. So I accept the customization of Ctrl-Shift-e in this bug at the moment. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1326156] New: kernel hung when using fbterm on vmware workstation 12

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1326156 Bug ID: 1326156 Summary: kernel hung when using fbterm on vmware workstation 12 Product: Fedora Version: 23 Component: fbterm Severity: high Assignee: bazanluis20(a)gmail.com Reporter: kuro(a)adm.tamagawa.ac.jp QA Contact: extras-qa(a)fedoraproject.org CC: bazanluis20(a)gmail.com, dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Description of problem: kernel hung up when using fbterm on vmware workstation 12 Version-Release number of selected component (if applicable): fbterm 1.7-7.fc23.x86_64 kernel 4.4.6-301.fc23 How reproducible: yes Steps to Reproduce: 1.login console 2.run fbterm 3.run find / -print Actual results: kernel hung up when printing find command result. Expected results: find command complete. Additional info: Kernel 4.2.300 is not hung up,but fbterm display is not correctly. I also test virtualbox with kernel 4.4.6-301,but not reproducible. -- You are receiving this mail because: You are on the CC list for the bug.

7 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs December 2016