On Thu, Apr 03, 2014 at 01:12:33PM +0200, Stefan Wollny wrote:
> Hi Zé,
> 
> I tried again at ftp.openbsd.org, ftp.fr.openbsd.org, ftp.eu.openbsd.org, 
> ftp.bytemine.net, openbsd.cs.fau.de:
> None of them has any claws-mail-* packages. The last two have been checked 
> for 11+ hours ...
> 
> Trying to install from ports gives an error:
> $ claws-mail
> **
> GLib-GObject:ERROR:gtype.c:2731:g_type_register_static: assertion failed: 
> (static_quark_type_flags)
> Abort trap (core dumped) 
> 
> Almost the same with xombrero:
> $ xombrero
> xombrero:/usr/lib/libsqlite3.so.27.0: /usr/lib/libsqlite3.so.26.0 : WARNING: 
> symbol(sqlite3_version) size mismatch, relink your program
> xombrero:/usr/lib/libsqlite3.so.27.0: /usr/lib/libsqlite3.so.26.0 : WARNING: 
> symbol(sqlite3OpcodeProperty) size mismatch, relink your program
> xombrero:/usr/lib/libsqlite3.so.27.0: /usr/lib/libsqlite3.so.26.0 : WARNING: 
> symbol(sqlite3Config) size mismatch, relink your program
> xombrero:/usr/local/lib/libestdc++.so.14.0: /usr/lib/libstdc++.so.57.0 : 
> WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink 
> your program
> 
> (process:17970): GLib-GObject-WARNING **: cannot register existing type 
> 'gchar'
> **
> GLib-GObject:ERROR:gvaluetypes.c:455:_g_value_types_init: assertion failed: 
> (type == G_TYPE_CHAR)
> Abort trap 
> 
> 
> Veeeery strange... Any hint on how to proceed is welcome!
> (dmesg at the end)
>  
> Cheers,
> STEFAN 

I rebuilt glib2 and the packages it depends on from ports, and then
replaced the already installed packages with the freshly built ones.
Maybe the uninstall/install process cleaned things up and removed the
old file Gregor mentioned. I did the same with vim, and it works now,
but so does xombrero, which I didn't rebuild. So I think reinstalling
glib2 is enough, but don't take this for granted, I'm not entirely sure.

Anyway, I think the best strategy is to remove the file manually and
reinstall (pkg_add -r) any packages that fail.

Bear in mind that the claws-mail-* package files *are* on the servers (I
just re-checked on a different computer, using a browser). It's the
clients you use to fetch them that are failing.

-- 

Reply via email to