gtk.gdk.threads_init()
No, that is not the problem. That is a perfectly valid call. If it doesn't work, your system is broken. .
I do agree with you, something is locally broken, but my system is not, because it is intact (see below).

I'm building local versions keeping the system versions ...

Keeping basic system components the same throughout a release cycle has the advantage of promoting stability.
There is absolutely no doubt on this point, this is why I'm moving to Salix.

I'm building local versions keeping the system versions intact (LD_LIBRARY_PATH ?). I came across this problem ...

The problem is most likely not glib-2.46 alone, but that you'd have to rebuilt almost everything that depends on it

Oh, I did not expect such statement. What is the idea behind dynamic linking then?

Glib2 does not break ABI, so you don't have to rebuild anything when you upgrade it (unless of ...

gapan wrote:You don't have to update the dependency information at all.

Yes I don't have to, but it is nice to do, so if I attempt to remove B, i get an warning or something. It is just easier for me to maintain my system. The local repository seems a plausible solution for me.

The problem is caused by glib-2.46, which I was experimenting. Changing my LD path, pygtk was loading that version. Anyway, this is a problem to consider, since It reflects a problem in using threading https://lists.debian.org/debian-python/2014/10/msg00004.html .

I didn't have time to lock at the ...

gapan wrote:What do you want to do that would require a douninst?

Update font cache, icon cache, mktexlsr? to name a few.

I did a fresh install of Salix 14.1, followed by a package upgrade. Now when I run sourcery i get the following error:

SLKBUILD files have the doinst() functions to execute commands when a package is installed. But I don't understand why it does douninst to execute command after package removal.

Hello,

I have a question regarding the way Salix handles dependencies. Since Salix it does not bundle dependencies information inside the package. My problem is that if I recompile a package A which is provided by Salix/Slackware, but adding feature that requires the installation of additional ...

Hello,

I'm slowly moving to Salix, escaping from the very fast moving Arch that keeps my machine a test field. However, I build a lot of package myself, using makepkg and PKGBUILD under Arch, probably was the only thing that kept me running this system for such long time.

Now, I was wondering if ...