[Desktop-packages] [Bug 1888797] Re: missing luahbtex

2021-04-27 Thread mhosken
Norbert, ping. It sounds you were so close. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1888797 Title: missing luahbtex Status in texlive-base package in Ubuntu: Confirmed

Re: [Desktop-packages] [Bug 1888797] Re: missing luahbtex

2020-07-28 Thread mhosken
Daer Norbert, > > Thank you Norbert. That would be great. I think your running the PPA > > would be a far better solution. > > Fine with me! I could help the Ubuntu people also for their versions, > but I don't **run** for them. If they would ask ... Sure. > Hmmm, the page I linked >

[Desktop-packages] [Bug 1888797] Re: missing luahbtex

2020-07-27 Thread mhosken
I do notice I and fighting with /usr/local/lib leakage into my build. Thank you Norbert. That would be great. I think your running the PPA would be a far better solution. The current (2019) version is 2019.20190605.51237-3build2 in the main repo So might I suggest

[Desktop-packages] [Bug 1888797] Re: missing luahbtex

2020-07-26 Thread mhosken
Thanks. Yes, it would be great if texlive 2020 was in Ubuntu 20.04. But I doubt it will happen given the feature packages for 20.04 are fixed now. I downloaded texlive-bin 2020 and tried to debuild. But I have harfbuzz 2.6.4 and there seems to be some mismatch in xetex over whether harfbuzz-icu

[Desktop-packages] [Bug 1888797] [NEW] missing luahbtex

2020-07-24 Thread mhosken
Public bug reported: I'm trying to install luahbtex. texlive-luatex implies it includes the corresponding luahbtex CTAN package, but the only filename containing the characters hb, installed by texlive-luatex is man1/luahbtex.1.gz which makes no reference to luahbtex within it. Yours, wanting to

[Desktop-packages] [Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()

2014-06-01 Thread mhosken
When I ran the test, I got not failure. But I did notice that when I ran the test using valgrind (still with no failure) valgrind reported a number of memory problems in python3.4. No errors were reported from anywhere in gtk or lower (pango, graphite, etc.). The command I used to test was:

[Desktop-packages] [Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()

2014-05-31 Thread mhosken
A couple of initial queries: Is there any way we can find out what the font was that was being initialised when the crash occurred? I ask because if the font isn't a graphite font, then what was causing a graphite font to try to be created? Looking at the input text being Burmese, I'll assume

[Desktop-packages] [Bug 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()

2014-05-31 Thread mhosken
In addition. If this is a memory corruption bug, is running the test under valgrind of any use? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1303516 Title: ubiquity crashed with

[Desktop-packages] [Bug 1166125] Re: Broken fonts for Gtk based applications

2013-10-22 Thread mhosken
pango-graphite and its dependent libgraphite3 should be removed from any dependencies and from the repos. The replacement (libgraphite2-3, yeh I know it's a funny order) integrates with harfbuzz-ng. I'm assuming that pango uses harfbuzz rather than its own shaping modules now? I don't know the