Bug#1095353: [Pkg-xmpp-devel] Bug#1095353: libsignal-protocol-c: FTBFS: #error This file was generated by a newer version of protobuf-c which is incompatible with your libprotobuf-c headers.

On Sun, 02/16/2025 03:13:35 PM, Hefee wrote: > I would expect you need to use the current headers from libprotobuf-c-dev > headers and the problem is solved. You may right. Thanks. The files are located in https://sources.debian.org/src/protobuf-c/1.5.1-1/protobuf-c and also in the project: ht

Bug#1095353: libsignal-protocol-c: FTBFS: #error This file was generated by a newer version of protobuf-c which is incompatible with your libprotobuf-c headers.

Maybe this is the reason of the bug: ( cd protobuf ; /usr/bin/make ) make[2]: Entering directory '/<>/protobuf' protoc-c --c_out=../src/ WhisperTextProtocol.proto LocalStorageProtocol.proto FingerprintProtocol.proto [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please u

Bug#1070457: dino-im: FTBFS: error: ‘struct _gpgme_key’ has no member named ‘subkeys_length1’

I found this bug at upstream project: Dino 0.4.3 fails to compile after Vala-c update to 0.56.17 https://github.com/dino/dino/issues/1576 -- Stefan

Bug#1032655: psi-plus segfaults

On Fri, Mar 10, 2023 at 03:45:38PM +0100, Lee Garrett wrote: > psi-plus currently simply segfaults on a stock bookworm installation: > > $ psi-plus > [20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile > (unknown:0, unknown) > [20230310 15:43:12] W:libpng warning: iCCP: know

Bug#1011684: t4kcommon: FTBFS: t4k_menu.c:1264:6: error: conflicting types for ‘set_font_size’; have ‘void(_Bool)’

Control: owner -1 ! Control: tags -1 + patch The problem is the declaration of function set_font_size. I added the bool parameter to the declaration. -voidset_font_size(); +voidset_font_size(bool); See attached patch file for more information. Index: b/src/t4k_menu.c

Bug#930991: gajim in Debian stretch does not start anymore

Control: severity -1 normal Hello, there was no feedback on this bugreport. I will set the severity to normal, because: * I was not able to reproduce this bug * The bug is reported on o-o-stable * There was no feedback See: https://www.debian.org/Bugs/Developer.en#severities -- Stefan

Bug#1006966: gajim: Gajim won't start due to gajim.c.storage.cache error

Control: severity -1 important Hello Leandro, I will reduce the severity from grave to important. I'm using 1.3.3-1~bpo11+1 on my laptop and it's working. I also checked where the cache.db is stored. file ~/.cache/gajim/cache.db says: SQLite 3.x database, user version 6, last written using SQLi

Bug#1006966: gajim: Gajim won't start due to gajim.c.storage.cache error

Hello, I just found this issue note on upstream project: https://dev.gajim.org/gajim/gajim/-/issues/10779#note_204952 It's sounds quite similar. Maybe a corrupted internal gajim db-file. -- Stefan