Re: "gschemas.compiled" not found



On Mon, Dec 9, 2013 at 2:55 PM, Kai Willadsen <kai willadsen gmail com> wrote:
On 30 November 2013 08:46, Scott Kostyshak <skostysh princeton edu> wrote:
On Fri, Nov 29, 2013 at 5:39 PM, Kai Willadsen <kai willadsen gmail com> wrote:
On 30 November 2013 08:33, Scott Kostyshak <skostysh princeton edu> wrote:
On Fri, Nov 29, 2013 at 5:25 PM, Kai Willadsen <kai willadsen gmail com> wrote:
On 30 November 2013 08:22, Scott Kostyshak <skostysh princeton edu> wrote:
On Ubuntu 13.10 with a fresh git clone I get the following when trying
to run meld:

Traceback (most recent call last):
  File "/usr/local/bin/meld", line 180, in <module>
    import meld.meldapp
  File "/usr/local/lib/python2.7/dist-packages/meld/meldapp.py", line
33, in <module>
    import meld.preferences
  File "/usr/local/lib/python2.7/dist-packages/meld/preferences.py",
line 32, in <module>
    from meld.settings import settings, interface_settings
  File "/usr/local/lib/python2.7/dist-packages/meld/settings.py", line
25, in <module>
    False,
gi._glib.GError: Failed to open file
'/usr/share/meld/gschemas.compiled': open() failed: No such file or
directory

I did a search on meld-list and did not find any related thread. Any advice?

See https://mail.gnome.org/archives/meld-list/2013-November/msg00017.html
and https://mail.gnome.org/archives/meld-list/2013-November/msg00011.html

cheers,
Kai

Thanks for the quick response Kai.

I'm mostly just terrified by how many people seem to have come to
expect Meld to work from a git HEAD checkout. I mean... *I* expect it
to work but then it would be a worry if I didn't.

GSettings/dconf is actually really unpleasant here. I don't know of
any sensible way I can have Meld work without a build step anymore.
(It'll be a minimal build step, but still...)  We *could* try to run
glib-compile-schemas if we think we're in a checkout, but that's not
the sanest notion ever.


Makes sense. Sounds tricky.

I applied brute force. We now try to compile schemas if we don't find
them, which is horrible but makes it More Likely To Work ™. We also
try to install schemas, so Meld HEAD should be back to working-ish by
default.

As for expecting git HEAD to work, I did
not. Well, I would have guessed that it would work, but I was
definitely not surprised when it did not. Perhaps I should have made
it more clear that I was just asking for advice and not trying to
report a "bug".

No, that's all good. I like that people expect HEAD to work, and I
never push anything that means that I can't run Meld... but build
stuff sometimes falls by the wayside temporarily.

I like being able to build on git HEAD because I've reported a couple
of meld bugs. It is nice to reproduce bugs on the development version
and it's also nice to be able to do bisects (e.g. there was a bug that
you couldn't reproduce that was specific to Ubuntu. I think in the end
it might have ended up being an Ubuntu bug that was triggered by a
meld commit).

And that's definitely appreciated from this side.

Anyway, Meld HEAD is back to a point where non-working-ness because of
GSettings is unexpected, rather than a snafu. There are still plenty
of GTK3, etc. related rough edges however, and a big migrations or two
(GtkGrid, CSS styles?, maybe some height-for-width, Python 3!) to go.


Good to know. Thanks for all of the information and explanations, Kai.
And please let me know if there's anything in particular you would
like for me to test on Ubuntu 13.10.

Scott


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]