Bug#1036113: libpurple0: license conflict with libsasl2
On Wed, 28 Jun 2023 10:14:00 +0200 Bastian Germann wrote: > Am 28.06.23 um 04:42 schrieb Richard Laager: > > What is the remaining instance of RSA-MD licensed code after #767? > > https://github.com/cyrusimap/cyrus-sasl/issues/769 Fyi: that issue has now been closed with https://github.com/cyrusimap/cyrus-sasl/pull/770 -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1019292: marked as pending in gnome-calls
Control: tag -1 pending Hello, Bug #1019292 in gnome-calls reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/DebianOnMobile-team/gnome-calls/-/commit/9c81b4ea72bf176b21506ec477641782d5ca4ffa d/patches: Fix build on IPv6 only buildd Closes: #1019292, thanks Adrian Bunk Also remove the patch that disabled a different test. I suspecting the intermittent failures seen there are of the same nature as #1019292. (this message was generated automatically) -- Greetings https://bugs.debian.org/1019292
Bug#1018134: [Debian-on-mobile-maintainers] Bug#1018134: Bug#1018134: chatty: bump severity to serious for ongoing evolution transitions
Hi, On Tue, 2022-09-06 at 08:40 +0200, Guido Günther wrote: > Just so that everybody is on the same page: the next chatty > release switches to libcmatrix and we can then switch to libsoup3 > via > > https://source.puri.sm/Librem5/libcmatrix/-/merge_requests/18 just a quick update: There will be a release and upload to Debian very soon now. During the libsoup3 port a segmentation fault was found in libsoup3 which can happen when using HTTP2 [0] and I've also filed it in the BTS [1] since someone is bound to hit this sooner or later and it also includes a workaround. [0] https://gitlab.gnome.org/GNOME/libsoup/-/issues/302 [1] https://bugs.debian.org/1019913 -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003
control -1 tags patch
Hi,
I'm not quite sure which is the preferred form to supply a patch,
so I'll attach a `git format-patch` based on my `wip/cve` branch on salsa [0].
If for further discussions should be needed before this can be uploaded
or the patch in a different form is preffered, please give me a shout.
[0] https://salsa.debian.org/devrtz/sofia-sip/-/tree/wip/cve
--
Cheers,
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
From 3687228cab738c9819bd82f6e171180e19b50c19 Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras
Date: Sat, 13 Aug 2022 04:24:34 +0200
Subject: [PATCH 1/2] Add patches to fix reported CVEs; add copyright of
patches
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
closes: bug#1016974, thanks Moritz Mühlenhoff!
For further information see:
- CVE-2022-31001[0]:
- CVE-2022-31002[1]:
- CVE-2022-31003[2]:
[0] https://security-tracker.debian.org/tracker/CVE-2022-31001
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31001
[1] https://security-tracker.debian.org/tracker/CVE-2022-31002
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31002
[2] https://security-tracker.debian.org/tracker/CVE-2022-31003
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31003
---
debian/copyright | 18
.../1003-cve-fix-oob-read-sip_method_d.patch | 28
.../1004-cve-fix-oob-read-url_canonize.patch | 45 +++
.../1005-cve-fix-heap-overflow-by-two.patch | 39
debian/patches/series | 3 ++
5 files changed, 133 insertions(+)
create mode 100644 debian/patches/1003-cve-fix-oob-read-sip_method_d.patch
create mode 100644 debian/patches/1004-cve-fix-oob-read-url_canonize.patch
create mode 100644 debian/patches/1005-cve-fix-heap-overflow-by-two.patch
diff --git a/debian/copyright b/debian/copyright
index e9c3efcf..a6b1642e 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -245,6 +245,24 @@ License-Grant:
License: GPL-3+
Reference: debian/copyright
+Files:
+ debian/patches/1003*
+ debian/patches/1004*
+ debian/patches/1005*
+Copyright:
+ 2022 Andrey Volk
+License-Grant:
+ This library is free software;
+ you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License
+ as published by the Free Software Foundation;
+ either version 2.1 of the License,
+ or (at your option) any later version.
+License-Grant:
+ Licensed under LGPL.
+ See file COPYING.
+License: LGPL-2.1+
+
License: BSD-3-clause
Redistribution and use in source and binary forms,
with or without modification,
diff --git a/debian/patches/1003-cve-fix-oob-read-sip_method_d.patch b/debian/patches/1003-cve-fix-oob-read-sip_method_d.patch
new file mode 100644
index ..d6e12d1d
--- /dev/null
+++ b/debian/patches/1003-cve-fix-oob-read-sip_method_d.patch
@@ -0,0 +1,28 @@
+From: Andrey Volk
+Commit: e96b4b89fc37a074bc95fc8fc24bb4b5297048ad
+Date: Mon, 18 Apr 2022 17:11:26 +0300
+Subject: Fix Out-of-bound read in sip_method_d
+
+Bug: https://security-tracker.debian.org/tracker/CVE-2022-31001
+Bug-Debian: https://bugs.debian.org/1016974
+
+Last-Update: 2022-08-13
+---
+ libsofia-sip-ua/sip/sip_parser.c | 4
+ 1 file changed, 4 insertions(+)
+
+diff --git a/libsofia-sip-ua/sip/sip_parser.c b/libsofia-sip-ua/sip/sip_parser.c
+index 3a4593d..b94be9b 100644
+--- a/libsofia-sip-ua/sip/sip_parser.c
b/libsofia-sip-ua/sip/sip_parser.c
+@@ -413,6 +413,10 @@ sip_method_t sip_method_d(char **ss, char const **return_name)
+
+ #undef MATCH
+
++ if (strlen(s) < n) {
++return sip_method_invalid;
++ }
++
+ if (IS_NON_WS(s[n]))
+ /* Unknown method */
+ code = sip_method_unknown;
diff --git a/debian/patches/1004-cve-fix-oob-read-url_canonize.patch b/debian/patches/1004-cve-fix-oob-read-url_canonize.patch
new file mode 100644
index ..46a3b030
--- /dev/null
+++ b/debian/patches/1004-cve-fix-oob-read-url_canonize.patch
@@ -0,0 +1,45 @@
+From: Andrey Volk
+Commit: 32a209f00763d4e506ed68ab68ffea3ead9cc8de
+Date: Mon, 18 Apr 2022 17:22:55 +0300
+Subject: Fix Out-of-bound read in url_canonize2 and url_canonize3
+
+Bug: https://security-tracker.debian.org/tracker/CVE-2022-31002
+Bug-Debian: https://bugs.debian.org/1016974
+
+Last-Update: 2022-08-13
+---
+ libsofia-sip-ua/url/url.c | 14 --
+ 1 file changed, 12 insertions(+), 2 deletions(-)
+
+diff --git a/libsofia-sip-ua/url/url.c b/libsofia-sip-ua/url/url.c
+index 7df6ab0..b379562 100644
+--- a/libsofia-sip-ua/url/url.c
b/libsofia-sip-ua/url/url.c
+@@ -364,7 +364,12 @@ char *url_canonize2(char *d, char const * const s, size_t n,
+ continue;
+ }
+
+-h1 = s[i + 1], h2 = s[i + 2];
++h1 = s[i + 1];
++if (!h1) {
++*d = '\0';
++return NULL;
++}
++h2 = s[i + 2];
+
+ if (!IS_HEX(h1) || !IS_HEX(h2)) {
+ *d = '\0';
+@@ -422,7 +4
Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003
control -1 tags pending Hi again, On Thu, 2022-08-11 at 23:52 +0200, Moritz Muehlenhoff wrote: > On Thu, Aug 11, 2022 at 11:08:49PM +0200, Evangelos Ribeiro Tzaras wrote: > > > > > If you fix the vulnerabilities please also make sure to include the > > > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. > > > > ACK. > > Is there a specific format needed when referencing the CVE? > > Not really, just mention them in debian/changelog :-) alright, so the patches apply cleanly and d/changelog mentions the CVEs (and closes this bug). > In addition we'll keep security-tracker.debian.org updated when the upload > reaches unstable. > > Once the fix is in unstable (and if there are issues reported after a few > days) we can sort out an update for bullseye-security. Sounds good to me! I think bullseye-security would be great, because I'm certain it is also vulnerable (oldstable potentially too - haven't checked) -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1017063: gnome-weather: fails to start up;
On Fri, 2022-08-12 at 11:47 -0400, Jeremy Bicha wrote: > On Fri, Aug 12, 2022 at 11:18 AM Evangelos Ribeiro Tzaras > wrote: > > gnome-weather errors out with a critical on my testing/sid system when > > trying to launch it: > Please check if downgrading your libmozjs-91-0 to the version from Testing > fixes your issue. You're on point: It does! Let's see if I do this right... control: reassign -1 libmozjs-91-0 control: affects -1 gnome-weather control: tags -1 + sid -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003
Hi Moritz, On Wed, 2022-08-10 at 22:08 +0200, Moritz Mühlenhoff wrote: > Source: sofia-sip > X-Debbugs-CC: t...@security.debian.org > Severity: grave > Tags: security > > Hi, > > The following vulnerabilities were published for sofia-sip. I will try to apply the patches and prepare a release! > CVE-2022-31001[0]: ... > CVE-2022-31002[1]: ... > CVE-2022-31003[2]: ... > > If you fix the vulnerabilities please also make sure to include the > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. ACK. Is there a specific format needed when referencing the CVE? > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2022-31001 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31001 > [1] https://security-tracker.debian.org/tracker/CVE-2022-31002 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31002 > [2] https://security-tracker.debian.org/tracker/CVE-2022-31003 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31003 > Please adjust the affected versions in the BTS as needed. Will do once I've checked in some detail. -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#993088: tootle FTBFS: error: The name `get_phrase' does not exist in the context of `Soup.Status'
Hi Adrian, On Fri, 27 Aug 2021 13:32:22 +0300 Adrian Bunk wrote: > Source: tootle > Version: 1.0-alpha2-1 > Severity: serious > Tags: ftbfs bookworm sid > ... > ../../src/Services/Network.vala:69.19-69.40: error: The name `get_phrase' does not exist in the context of `Soup.Status' (libsoup-2.4) > var reason = Soup.Status.get_phrase (code); > ^^ This was fixed with the latest upload. because the there was a small oversight with the changelog [0] (1.0-3 never actually made it to unstable) the bug did not get autoclosed. [0] https://metadata.ftp-master.debian.org/changelogs/main/t/tootle/tootle_1.0-ds1-4_changelog -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1016927: [Debian-on-mobile-maintainers] Bug#1016927: gnome-console: Shortcuts being executed without shift being hold
control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/-/issues/5095 Hi, On Tue, 2022-08-09 at 21:00 -0300, Thiago Bellini Ribeiro wrote: > Hey Jeremy, > > I not only closed and reopened the app but I also restarted my pc after my > last update to Debian Sid. > > Also, as I mentioned in the upstream bug, this issue affected both my office > pc and my personal one the same way, both which I restarted after updating all > pacakges (they both run Debian Sid). > > On Tue, Aug 9, 2022 at 8:58 PM Jeremy Bicha > wrote: > > On Tue, Aug 9, 2022 at 7:45 PM Thiago Bellini Ribeiro > > wrote: > > > After upgrading to the current gnome-console version in Debian Sid > > > (43~beta-1), > > > all shortcuts are being executed even without pressing shift. > > > > > > For example, ctrl+c is executing a copy (together with a SIGINT) just as > > > if I > > > pressed ctrl+shift+c > > > ctrl+v is pasting without requiring shift being hold > > > ctrl+w is closing the current tab > > > > I'm not able to reproduce that bug either with Ubuntu 22.10 which is > > running a similar version of gnome-console. According to the devs it appears to be a X11 specific gtk bug. Apparently it should be reproducible with `$ GDK_BACKEND=x11 kgx` which wasn't the case for me. PS: Two Ribeiro's in this bug \o/ -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1
Hi again,
On Sat, 2 Jul 2022 03:32:30 +0200 Evangelos Ribeiro Tzaras
wrote:
> Dear maintainer,
>
> I've prepared an NMU for olm (versioned as 3.2.11~dfsg-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
It was uploaded and (expectedly) REJECT'ed (because I'm DM).
This is good
because loosening the {build-,}dep version constraints on binaryen
in the emscripten package (#1011708)
also fixes the build.
Jochen will handle the upload.
--
Cheers,
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
signature.asc
Description: This is a digitally signed message part
Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1
Dear maintainer,
I've prepared an NMU for olm (versioned as 3.2.11~dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
This is a second version, because I forgot to remove the autopkgtest suite,
which depends on the removed libjs-olm.
Sorry for any confusion this may have caused.
Regards.
diff -Nru olm-3.2.11~dfsg/debian/changelog olm-3.2.11~dfsg/debian/changelog
--- olm-3.2.11~dfsg/debian/changelog 2022-04-16 10:37:50.0 +0200
+++ olm-3.2.11~dfsg/debian/changelog 2022-07-02 02:57:25.0 +0200
@@ -1,3 +1,11 @@
+olm (3.2.11~dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove javascript bindings
+Closes: #1011712 (thanks Lucas Nussbaum)
+
+ -- Evangelos Ribeiro Tzaras Sat, 02 Jul 2022 02:57:25 +0200
+
olm (3.2.11~dfsg-1) unstable; urgency=medium
[ upstream ]
diff -Nru olm-3.2.11~dfsg/debian/tests/control olm-3.2.11~dfsg/debian/tests/control
--- olm-3.2.11~dfsg/debian/tests/control 2022-04-16 10:37:50.0 +0200
+++ olm-3.2.11~dfsg/debian/tests/control 1970-01-01 01:00:00.0 +0100
@@ -1,30 +0,0 @@
-Test-Command:
- sed -i -e 's,\.\./olm,@matrix-org/olm,' javascript/test/*.spec.js
- && cd javascript && jasmine --config=test/jasmine.json
-Depends:
- node-jasmine,
- node-matrix-org-olm,
-
-Test-Command: node -e "
- const domino = require('domino');
- const window = domino.createWindow('');
- const document = window.document;
- require('/usr/share/javascript/olm/olm');
- require('/usr/share/javascript/olm/olm.min');
- require('/usr/share/javascript/olm/olm_legacy');
- require('/usr/share/javascript/olm/olm_legacy.min');
- "
-Depends:
- libjs-olm,
- node-domino,
- nodejs,
-Restrictions: superficial
-
-Test-Command:
- cd /usr/share/javascript &&
- eslint --no-eslintrc --format tap --env browser --parser-options '{ "ecmaVersion": 2015 }' olm/*.js
-Depends:
- eslint,
- libjs-olm,
- node-js-yaml,
-Restrictions: superficial
Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1
Control: tags 1011712 + patch Control: tags 1011712 + pending Dear maintainer, I've prepared an NMU for olm (versioned as 3.2.11~dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru olm-3.2.11~dfsg/debian/changelog olm-3.2.11~dfsg/debian/changelog --- olm-3.2.11~dfsg/debian/changelog 2022-04-16 10:37:50.0 +0200 +++ olm-3.2.11~dfsg/debian/changelog 2022-07-02 02:57:25.0 +0200 @@ -1,3 +1,11 @@ +olm (3.2.11~dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Remove javascript bindings +Closes: #1011712 (thanks Lucas Nussbaum) + + -- Evangelos Ribeiro Tzaras Sat, 02 Jul 2022 02:57:25 +0200 + olm (3.2.11~dfsg-1) unstable; urgency=medium [ upstream ]
Bug#1011712: olm: FTBFS: unsatisfiable build-dependency: binaryen (< 105+) but 106-1 is to be installed
Hi, On Sun, 26 Jun 2022 10:18:13 +0200 Hubert Chathi wrote: > On Sat, 25 Jun 2022 00:49:15 +0200, Evangelos Ribeiro Tzaras said: > > [...] > > > - Drop the javascript bindings for olm (libjs-olm). The only reverse > > dependency of libjs-olm is libjs-matrix-sdk which itself has no > > reverse dependencies. > > FWIW, libjs-matrix-js-sdk upstream is looking into switching to the new > rust implementation of olm, so some future version may stop using > libjs-olm anyways. But I'm not sure of the timeline for that. Good to know :) > > Aside from that, I'd like to look into updating emscripten somehow, but > I'm currently on VAC so I won't be able to do it for a little while. So > in the mean time, I don't have any objection to someone doing something > to resolve the situation temporarily. Alright, nmudiff following shortly (which removes the javascript bindings). -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
Bug#1009917: gtk4 applications randomly crash
Control: tags -1 fixed-upstream On Wed, 20 Apr 2022 18:03:34 +0200 ZenWalker wrote: > > Unable to run these applications 10 times without crash with mobian pinephone: > > megapixels, gnome-calculator, and gnome-clocks and probably more gtk4 apps > > the crash, running in terminal: > > Gsk:ERROR:../../../gsk/gl/gskglcommandqueue.c:1266:gsk_gl_command_queue_create_r ender_target: assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cd6 == 0x8cd5) > Bail out! Gsk:ERROR:../../../gsk/gl/gskglcommandqueue.c:1266:gsk_gl_command_queue_create_r ender_target: assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cd6 == 0x8cd5) > Aborted (core dumped) > > The issue in gtk repo: > https://gitlab.gnome.org/GNOME/gtk/-/issues/4763 > > This patch fixes the bug: > https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4570.patch > A couple of patches that fix the issue have been merged upstream: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4687 Cheers -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1011712: olm: FTBFS: unsatisfiable build-dependency: binaryen (< 105+) but 106-1 is to be installed
Hi, On Thu, 23 Jun 2022 13:33:55 +0200 Markus Koschany wrote: > Hi, > > I didn't know that there was some coordination required between binaryen and > emscripten. Nobody talked about that in the past. Sorry to ditch your request > but I don't plan to maintain emscripten. Thanks for your reply and good to know. > The only reason why I introduced > binaryen and wabt to Debian was to compile web assembly code from source in > ublock-origin. Apart from that I am not really involved in the Javascript > ecosystem either. I think it is best if someone takes over emscripten and > binaryen and maintains them together. > Having looked a bit into olm and emscripten I can imagine a few possible solutions: - binaryen is a build dep for emscripten "only" for running the tests (). This suggest to me, that it should be possible to get a build going without the tests. I've tried running building with DEB_BUILD_OPTIONS=nocheck and dropping the build dep on binaryen, but this alone didn't stop the build from failing. d/rules is rather complex beast and I haven't managed to rip everything "unneeded" out. Maybe someone more knowledgeable will have more success.. Although I'm not sure how good of an idea it would be to simply skip the tests. - Drop the javascript bindings for olm (libjs-olm). The only reverse dependency of libjs-olm is libjs-matrix-sdk which itself has no reverse dependencies. - Have someone maintain binaryen and emscripten and always upgrade in lockstep, as the sources [0] suggest, that the actual and "expected" binaryen version at most differ by one version number. Maybe there are other ideas of how to resolve this. If no other solution presents itself I'm inclined to drop libjs-olm in a NMU with DELAYED/7. [0] https://salsa.debian.org/js-team/emscripten/-/blob/debian/latest/tools/building.py#L1475 Cheers -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1011712: olm: FTBFS: unsatisfiable build-dependency: binaryen (< 105+) but 106-1 is to be installed
Dear maintainers, On Thu, 26 May 2022 08:44:43 +0200 Lucas Nussbaum wrote: > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > > > Install main build dependencies (apt-based resolver) > > > > > > > > The following packages have unmet dependencies: > > emscripten : Depends: binaryen (< 105+) but 106-1 is to be installed > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. > > > The full build log is available from: > http://qa-logs.debian.net/2022/05/25/olm_3.2.11~dfsg-1_unstable.log > Since emscripten was recently orphaned [0] I was wondering if the matrix team or the binaryen maintainer (which I cc'ed) would be interested in taking over (ideally before emscripten gets autoremoved)? I'd like for olm (and by extension emscripten) to not get removed, because it will trigger autoremoval for chatty[1], which I have the pleasure of maintaining. I'm afraid I'm not able to step up myself here, because I don't like javascript and know nothing about the ecosystem and tooling. Anyway: Thank you for your work on maintaining olm! [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013374 [1] https://tracker.debian.org/pkg/chatty Cheers, -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1011823: marked as pending in purple-xmpp-http-upload
Control: tag -1 pending Hello, Bug #1011823 in purple-xmpp-http-upload reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/DebianOnMobile-team/purple-xmpp-http-upload/-/commit/f480bf62f1640548d02f5af4a0a0659344a53b05 Adjust shlibdeps override Closes: #1011823, thanks to Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/1011823
Bug#1011166: Chatty can no longer start since the last update
Hi, On Sun, 22 May 2022 02:06:31 +0200 (CEST) Julien wrote: > Sorry for my silly question but why does Chatty still fail to start? My pinephone is my daily driver, can you tell me what still needs to be fixed? Do I have to use "ln -s" in the meantime? > it should migrate to testing in ~4 days, in the meantime you could grab it from unstable or add a suitable LD_LIBRARY_PATH, f.e. on amd64 $ LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/purple-2 chatty Cheers signature.asc Description: This is a digitally signed message part
Bug#1011166: [Debian-on-mobile-maintainers] Bug#1011166: Bug#1011166: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0
Hi, On Thu, 2022-05-19 at 22:23 -0500, Richard Laager wrote: > On 5/19/22 04:04, Evangelos Ribeiro Tzaras wrote: > > Thanks for the patch! I'll upload a fixed version soon. > > If you upload a new version, you (or I) can then close the binNMU > request, bug #1011201. just uploaded, and closing #1011201, thanks again! Cheers, Evangelos signature.asc Description: This is a digitally signed message part
Bug#1011166: [Debian-on-mobile-maintainers] Bug#1011166: Bug#1011166: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0
Hi, On Thu, 2022-05-19 at 22:23 -0500, Richard Laager wrote: > On 5/19/22 04:04, Evangelos Ribeiro Tzaras wrote: > > Thanks for the patch! I'll upload a fixed version soon. > > If you upload a new version, you (or I) can then close the binNMU > request, bug #1011201. I have prepared an update on salsa [0]. I was wondering one thing though: The packaging used to have override dh_shlibdeps: dh_shlibdeps -l/usr/lib/purple-2 which I stripped, because a) the path is now wrong b) it doesn't seem to get used at all, judging by compairing packages built with an updated path and without the override Since I'm not 100% sure if this was ever actually needed, I was curious if you could potentially shed some light ;) [0] https://salsa.debian.org/DebianOnMobile-team/chatty/-/merge_requests/22 Cheers -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1011166: [Debian-on-mobile-maintainers] Bug#1011166: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0
Hi,
On Wed, 2022-05-18 at 03:04 -0500, Richard Laager wrote:
> Control: notfound 1011166 pidgin/2.14.9-2
> Control: tags 1011166 patch
>
> On 5/17/22 15:34, Paul Gevers wrote:
> > I note that
> > the library moved location from /usr/lib/purple-
> > 2/libjabber.so.0.0.0 to
> > /usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0.0.0.
>
> I converted from an ancient compat version to modern debhelper. This
> brought in multiarch support. Rather than fight it, I just went with
> that, since the problem looked tractable.
>
> > Naively I would
> > have expected it to be picked up, but maybe the /purple-2 in the
> > middle
> > of the path is preventing that.
>
> -- BEGIN RED HERRING --
>
> I would expect it to be picked up.
>
> libpurple/plugin.c sets up the search path for that purple-2
> directory
> (which is where all libpurple plugins are installed):
> purple_plugins_add_search_path(LIBDIR);
>
> In libpurple/Makefile.am, AM_CPPFLAGS has:
> -DLIBDIR=\"$(libdir)/purple-$(PURPLE_MAJOR_VERSION)/\"
>
> This should cause us to find libxmpp.so, the protocol plugin. It then
> needs to bring in libjabber.so, an internal library. It should be
> finding this with RUNPATH, I believe:
>
> $ readelf -a /usr/lib/x86_64-linux-gnu/purple-2/libxmpp.so | grep -i
> path
> 0x001d (RUNPATH) Library runpath:
> [/usr/lib/x86_64-linux-gnu/purple-2]
>
> If I run: LD_DEBUG=libs pidgin -n
>
> That is indeed what happens:
> 43864: find library=libjabber.so.0 [0]; searching
> 43864: search
> path=/usr/lib/x86_64-linux-gnu/purple-2/glibc-hwcaps/x86-64-
> v3:/usr/lib/x86_64-linux-gnu/purple-2/glibc-hwcaps/x86-64-
> v2:/usr/lib/x86_64-linux-gnu/purple-
> 2/tls/haswell/x86_64:/usr/lib/x86_64-linux-gnu/purple-
> 2/tls/haswell:/usr/lib/x86_64-linux-gnu/purple-
> 2/tls/x86_64:/usr/lib/x86_64-linux-gnu/purple-2/tls:/usr/lib/x86_64-
> linux-gnu/purple-2/haswell/x86_64:/usr/lib/x86_64-linux-gnu/purple-
> 2/haswell:/usr/lib/x86_64-linux-gnu/purple-2/x86_64:/usr/lib/x86_64-
> linux-gnu/purple-2
> (RUNPATH from file
> /usr/lib/x86_64-linux-gnu/purple-2/libxmpp.so)
>
> If I run: LD_DEBUG=libs chatty
>
> It fails:
>
> 43926:find library=libjabber.so.0 [0]; searching
> 43926: search path=/usr/lib/purple-2 (RUNPATH from
> file chatty)
> 43926: trying file=/usr/lib/purple-2/libjabber.so.0
> 43926: search cache=/etc/ld.so.cache
> 43926: search
> path=/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3:/lib/x86_64-linux-
> gnu/glibc-hwcaps/x86-64-v2:/lib/x86_64-linux-
> gnu/tls/haswell/x86_64:/lib/x86_64-linux-gnu/tls/haswell:/lib/x86_64-
> linux-gnu/tls/x86_64:/lib/x86_64-linux-gnu/tls:/lib/x86_64-linux-
> gnu/haswell/x86_64:/lib/x86_64-linux-gnu/haswell:/lib/x86_64-linux-
> gnu/x86_64:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/glibc-
> hwcaps/x86-64-v3:/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-
> v2:/usr/lib/x86_64-linux-gnu/tls/haswell/x86_64:/usr/lib/x86_64-
> linux-gnu/tls/haswell:/usr/lib/x86_64-linux-
> gnu/tls/x86_64:/usr/lib/x86_64-linux-gnu/tls:/usr/lib/x86_64-linux-
> gnu/haswell/x86_64:/usr/lib/x86_64-linux-gnu/haswell:/usr/lib/x86_64-
> linux-gnu/x86_64:/usr/lib/x86_64-linux-gnu:/lib/glibc-hwcaps/x86-64-
> v3:/lib/glibc-hwcaps/x86-64-
> v2:/lib/tls/haswell/x86_64:/lib/tls/haswell:/lib/tls/x86_64:/lib/tls:
> /lib/haswell/x86_64:/lib/haswell:/lib/x86_64:/lib:/usr/lib/glibc-
> hwcaps/x86-64-v3:/usr/lib/glibc-hwcaps/x86-64-
> v2:/usr/lib/tls/haswell/x86_64:/usr/lib/tls/haswell:/usr/lib/tls/x86_
> 64:/usr/lib/tls:/usr/lib/haswell/x86_64:/usr/lib/haswell:/usr/lib/x86
> _64:/usr/lib
> (system search path)
>
> At first glance, it felt like the RUNPATH from chatty was winning
> over
> that from libxmpp.so.
>
> -- END RED HERRING --
>
> Upon further investigation, the real issue is that chatty is directly
> linking to libjabber.so, and they're setting a RUNPATH to do it.
>
> chatty's src/meson.build has:
> executable('chatty', chatty_sources, resources,
> include_directories: src_inc,
> dependencies: chatty_deps,
> link_with: libchatty.get_static_lib(),
> install: true,
> install_rpath: purple_plugdir,
> )
>
> Note the install_rpath.
>
> and src/purple/meson.build has (manual wrapping added for email):
>
> purple_plugdir = purple_dep.get_pkgconfig_variable('plugindir')
> jabber = meson.get_compiler('c').find_library(
> 'jabber', dirs: purple_plugdir)
>
> In terms of "Who is at fault?", I blame chatty for explicitly linking
> to
> an internal library. However, in fairness, I understand that they
> have
> their reasons and a better solution was never found with upstream (at
> least in part because no significant changes are going to go into
> purple
> 2 at this point):
> https://source.puri.sm/Librem5/chatty/-/issues/266
>
thanks for the thorough analysis!
> The good news here is that a rebuild of chatty is all that's
> necessary.
Indeed. I noticed this whil
Bug#965829: sofia-sip: diff for NMU version 1.12.11+20110422.1-2.2
Control: tags 965829 + pending Dear maintainer, I've prepared an NMU for sofia-sip (versioned as 1.12.11+20110422.1-2.2) and if I read the policy right, it should be uploaded to DELAYED/0, but will leave that to the sponsors discretion. See bug #1003853 for the RFS. Regards. Evangelos diff -u sofia-sip-1.12.11+20110422.1/debian/changelog sofia-sip-1.12.11+20110422.1/debian/changelog --- sofia-sip-1.12.11+20110422.1/debian/changelog +++ sofia-sip-1.12.11+20110422.1/debian/changelog @@ -1,3 +1,10 @@ +sofia-sip (1.12.11+20110422.1-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Bump dh-compat to 13 (Closes: #965829) + + -- Evangelos Ribeiro Tzaras Sat, 15 Jan 2022 12:03:56 +0100 + sofia-sip (1.12.11+20110422.1-2.1) unstable; urgency=medium * Non-maintainer upload.
Bug#965829:
Hi, so I've made a new minimal patch that would only bump the debhelper compat and not touch anything else. The resulting binary packages are only minimally different, except for the doc-package: Superficially it looks the same from browsing through the html, but some images are now svg instead of png and some additional html/js files are present which I would attribute to changes in doxygen. The revised (minimal) patch is attached. Is there someone willing to NMU this with the patch applied? I'm only a lowly DM, so I can't upload myself. Side note: Trying to use debdiff on the .dsc's it only outputted changes in debian/changelog, but not in other files (in case you're wondering why I've not attached a .debdiff) -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 diff -r sofia-sip-1.12.11+20110422.1/debian/changelog sofia-sip-1.12.11+20110422.1.untouched/debian/changelog 1,7d0 < sofia-sip (1.12.11+20110422.1-2.2) unstable; urgency=medium < < * Non-maintainer upload. < * Bump dh-compat to 13 (Closes: #965829) < < -- Evangelos Ribeiro Tzaras Sat, 15 Jan 2022 12:03:56 +0100 < diff -r sofia-sip-1.12.11+20110422.1/debian/compat sofia-sip-1.12.11+20110422.1.untouched/debian/compat 1c1 < 13 --- > 5 diff -r sofia-sip-1.12.11+20110422.1/debian/control sofia-sip-1.12.11+20110422.1.untouched/debian/control 5c5 < Build-Depends: debhelper (>= 13), pkg-config, libglib2.0-dev, libssl-dev, --- > Build-Depends: debhelper (>= 5), pkg-config, libglib2.0-dev, libssl-dev,
Bug#965829: sofia-sip: Removal of obsolete debhelper compat 5 and 6 in bookworm
Hi Niels, On Mon, 2021-12-27 at 09:54 +0100, Niels Thykier wrote: > On Wed, 22 Dec 2021 09:37:46 +0100 Evangelos Ribeiro Tzaras > wrote: > > Just as a follow up: > > > > I could imagine adopting the package (possibly within the VoIP > > team) > > in case the maintainer is willing to part with it. I don't want to > > be > > stepping on any toes, which is why I'm cautiously putting that > > option > > on the table :) > > > > Cheers > > -- > > Evangelos > > PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 > > > > > > Hi, > > FTR, I think this package might be a candidate for the [ITS process] > in > case you are interested in maintaining it. Thanks for the link! Jonas has filed an [ITS bug]. > > ~Niels > > [ITS process]: > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging > > [ITS bug] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003706 Cheers -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
Bug#965829:
Just as a follow up: I could imagine adopting the package (possibly within the VoIP team) in case the maintainer is willing to part with it. I don't want to be stepping on any toes, which is why I'm cautiously putting that option on the table :) Cheers -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
Bug#965829: sofia-sip: Removal of obsolete debhelper compat 5 and 6 in bookworm
control: -1 tags patch quit Hi, On Mon, 20 Jul 2020 19:35:35 + Niels Thykier wrote: > Source: sofia-sip > Version: 1.12.11+20110422.1-2.1 > Severity: normal > Usertags: compat-5-6-removal > > Hi, > > The package sofia-sip uses debhelper with a compat level of 5 or 6, > which is deprecated and scheduled for removal[1]. > > Please bump the debhelper compat at your earliest convenience > /outside the freeze/! > > * Compat 13 is recommended (supported in stable-backports) > > * Compat 7 is the bare minimum I have tried my hand at producing a patch to bump debhelper (and hopefully don't break anything), which I'll attach here. The patch could probably be improved to only skip the failing test instead of disabling the whole testsuite, but this is as far as I got after a few hours of poking it with a stick :) > > At the time of filing this bug, compat 5 and 6 are expected to be > removed "some time during the development cycle of bookworm". > As far as I can see sofia-sip is now marked for removal from testing on 2022-01-19, so I thought it would be somewhat urgent to get this fixed soon. > > Thanks, > ~Niels > > > [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html > > [2] https://release.debian.org/bullseye/FAQ.html > > [3] The choice of 2021-01-01 as a "deadline" is set before the actual > freeze deadline to provide a safe cut off point for most people. > > Mind you, it is still your responsibility to ensure that the upload > makes it into testing even if you upload before that date. > Cheers, -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 From ef68921183553b8cdfefd5076da5e8ebd0afb1d8 Mon Sep 17 00:00:00 2001 From: Evangelos Ribeiro Tzaras Date: Wed, 22 Dec 2021 07:35:39 +0100 Subject: [PATCH 1/2] Bump debian compat to 13 and adapt to changes * Bump to debhelper-compat 13 * Install paths got wildcards included /usr/lib/... vs /usr/lib/*/... * Install generated libtool .la files * Disable tests because of the following test failure: * Closes #965829 FAIL: check_sres_sip Running suite(s): Unit tests for SIP URI resolver 0%: Checks: 19, Failures: 19, Errors: 0 check_sres_sip.c:182:F:1 - Test simple resolving:invalid:0: Early exit with return value 0 check_sres_sip.c:212:F:1 - Test simple resolving:not_found:0: Early exit with return value 0 check_sres_sip.c:237:F:1 - Test simple resolving:failure:0: Early exit with return value 0 check_sres_sip.c:298:F:1 - Test simple resolving:timeout:0: Early exit with return value 0 check_sres_sip.c:326:F:1 - Test simple resolving:found_a:0: Early exit with return value 0 check_sres_sip.c:464:F:1 - Test simple resolving:found_cname:0: Early exit with return value 0 check_sres_sip.c:380:F:1 - Test simple resolving:found_ip:0: Early exit with return value 0 check_sres_sip.c:414:F:1 - Test simple resolving:found_maddr_a:0: Early exit with return value 0 check_sres_sip.c:522:F:1 - Test simple resolving:found_maddr_ip:0: Early exit with return value 0 check_sres_sip.c:570:F:1 - Test simple resolving:found_a_:0: Early exit with return value 0 check_sres_sip.c:604:F:1 - Test simple resolving:found_naptr:0: Early exit with return value 0 check_sres_sip.c:670:F:1 - Test simple resolving:found_bad_naptr:0: Early exit with return value 0 check_sres_sip.c:634:F:1 - Test simple resolving:found_naptr_nohint:0: Early exit with return value 0 check_sres_sip.c:755:F:1 - Test simple resolving:found_naptr2:0: Early exit with return value 0 check_sres_sip.c:809:F:1 - Test simple resolving:found_naptr3:0: Early exit with return value 1 check_sres_sip.c:865:F:1 - Test simple resolving:found_naptr_with_a:0: Early exit with return value 0 check_sres_sip.c:708:F:1 - Test simple resolving:ignore_naptr:0: Early exit with return value 0 check_sres_sip.c:901:F:1 - Test simple resolving:found_srv:0: Early exit with return value 1 check_sres_sip.c:1082:F:1 - Test simple resolving:found_multi_srv:0: Early exit with return value 0 FAIL check_sres_sip (exit status: 1) SKIP: run_test_sresolv == ./run_test_sresolv: started named pid 443084 ./run_test_sresolv: cannot start named ./run_test_sresolv: perhaps you have to disable apparmor protection for named SKIP run_test_sresolv (exit status: 77) --- debian/compat | 1 - debian/control | 2 +- debian/libsofia-sip-ua-dev.install | 6 +- debian/libsofia-sip-ua-glib-dev.install | 6 +- debian/libsofia-sip-ua-glib3.install| 4 +- debian/libsofia-sip-ua0.install | 3 +- debian/rules| 101 ++-- debian/sofia-sip-doc.docs | 4 +- 8 files changed, 20 insertions(+), 107 deletions(-) delete mode 100644 debian/compat diff --git a/debian/compat b/debian/compat deleted file mod
Bug#982696: [PATCH] drm-info: FTBFS: tables.c:247:2: error: duplicate case value
Hi, On 2/16/21 6:20 PM, Dennis Filder wrote: The attached patch drm-info-fourcc_py.patch fixes the issue by ensuring case labels are not printed twice. Thanks for providing a patch! Applied in [0] I also noticed that d/watch hardcodes "drm_info" with an underscore in the filenamemangle expression which was probably not intended. drm-info-watchfile.patch consists of what I found in the uscan manpage. Again thanks for the patch! Applied in [1] Regards, Dennis. @Birger: Could you upload the updated package? [0] https://salsa.debian.org/swaywm-team/drm-info/-/commit/cdeeb4ee2d850dfcb5939b69ff9e5a89ad5a183d [1] https://salsa.debian.org/swaywm-team/drm-info/-/commit/799b20d6ebf388bc9e2a607efa117f52bc4d2b63 Cheers
Bug#982696: drm-info: FTBFS: tables.c:247:2: error: duplicate case value
Hi, On 2/13/21 6:03 PM, Lucas Nussbaum wrote: Source: drm-info Version: 2.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210213 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. thanks for your report! Relevant part (hopefully): cc -Idrm_info.p -I. -I.. -I/usr/include/libdrm -I/usr/include/json-c -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -D_POSIX_C_SOURCE=200809L -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ drm_info.p/meson-generated_.._tables.c.o -MF drm_info.p/meson-generated_.._tables.c.o.d -o drm_info.p/meson-generated_.._tables.c.o -c tables.c tables.c: In function ‘modifier_str’: tables.c:247:2: error: duplicate case value 247 | case DRM_FORMAT_MOD_LINEAR: | ^~~~ tables.c:245:2: note: previously used here 245 | case DRM_FORMAT_MOD_LINEAR: | ^~~~ tables.c:251:2: error: duplicate case value 251 | case DRM_FORMAT_MOD_SAMSUNG_16_16_TILE: | ^~~~ tables.c:241:2: note: previously used here 241 | case DRM_FORMAT_MOD_SAMSUNG_16_16_TILE: | ^~~~ [4/6] cc -Idrm_info.p -I. -I.. -I/usr/include/libdrm -I/usr/include/json-c -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -D_POSIX_C_SOURCE=200809L -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ drm_info.p/json.c.o -MF drm_info.p/json.c.o.d -o drm_info.p/json.c.o -c ../json.c [5/6] cc -Idrm_info.p -I. -I.. -I/usr/include/libdrm -I/usr/include/json-c -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -D_POSIX_C_SOURCE=200809L -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ drm_info.p/pretty.c.o -MF drm_info.p/pretty.c.o.d -o drm_info.p/pretty.c.o -c ../pretty.c ninja: build stopped: subcommand failed. dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1 make: *** [debian/rules:6: binary] Error 25 Applying the patches generously provided by Dennis Filder I can build in a up to date schroot. The full build log is available from: http://qa-logs.debian.net/2021/02/13/drm-info_2.2.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. Cheers
Bug#980601: [Debian-on-mobile-maintainers] Bug#980601: Bug#980601: chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a ty
On 1/21/21 4:00 AM, Evangelos Ribeiro Tzaras wrote: Hi, On 1/20/21 9:25 PM, Lucas Nussbaum wrote: Source: chatty Version: 0.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. thanks for your report! Relevant part (hopefully): c++ -Isrc/libchatty.so.p -Isrc -I../src -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpurple -I/usr/include/libhandy-1 -I/usr/include/evolution-data-server -I/usr/include/nss -I/usr/include/nspr -I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gsettings-desktop-schemas -I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/libchatty.so.p/chatty-phone-utils.cpp.o -MF src/libchatty.so.p/chatty-phone-utils.cpp.o.d -o src/libchatty.so.p/chatty-phone-utils.cpp.o -c ../src/chatty-phone-utils.cpp In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? 47 | static const ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[] | ^~~~ | AuxillaryParseTableField In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:88:30: error: ‘ConstStringParam’ is not a member of ‘google::protobuf’ 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h:88:82: error: expected primary-expression before ‘*’ token 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:84: error: ‘value’ was not declared in this scope 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:89: error: expression list treated as compound expression in initializer [-fpermissive] 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:218:71: error: ‘google::protobuf::ConstStringParam’ has not been declared 218 | static inline bool CountryCodeSource_Parse(::PROTOBUF_NAMESPACE_ID::ConstStringParam name, | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h: In static member function ‘static bool i18n::phonenumbers::PhoneNumber::CountryCodeSource_Parse(int, i18n::phonenumbers::PhoneNumber::CountryCodeSource*)’: /usr/include/phonenumbers/phonenumber.pb.h:220:59: error: ‘i18n::phonenumbers::PhoneNumber_CountryCodeSource_Parse’ cannot be used as a function 220 | return PhoneNumber_CountryCodeSource_Parse(name, value); | ^ [36/65] cc -Isrc/chatty.p -Isrc -I../src -I../src/xeps/prpl/jabber -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-
Bug#980601: [Debian-on-mobile-maintainers] Bug#980601: chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you
Hi, On 1/20/21 9:25 PM, Lucas Nussbaum wrote: Source: chatty Version: 0.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. thanks for your report! Relevant part (hopefully): c++ -Isrc/libchatty.so.p -Isrc -I../src -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpurple -I/usr/include/libhandy-1 -I/usr/include/evolution-data-server -I/usr/include/nss -I/usr/include/nspr -I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gsettings-desktop-schemas -I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/libchatty.so.p/chatty-phone-utils.cpp.o -MF src/libchatty.so.p/chatty-phone-utils.cpp.o.d -o src/libchatty.so.p/chatty-phone-utils.cpp.o -c ../src/chatty-phone-utils.cpp In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? 47 | static const ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[] | ^~~~ | AuxillaryParseTableField In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:88:30: error: ‘ConstStringParam’ is not a member of ‘google::protobuf’ 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h:88:82: error: expected primary-expression before ‘*’ token 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:84: error: ‘value’ was not declared in this scope 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:89: error: expression list treated as compound expression in initializer [-fpermissive] 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:218:71: error: ‘google::protobuf::ConstStringParam’ has not been declared 218 | static inline bool CountryCodeSource_Parse(::PROTOBUF_NAMESPACE_ID::ConstStringParam name, | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h: In static member function ‘static bool i18n::phonenumbers::PhoneNumber::CountryCodeSource_Parse(int, i18n::phonenumbers::PhoneNumber::CountryCodeSource*)’: /usr/include/phonenumbers/phonenumber.pb.h:220:59: error: ‘i18n::phonenumbers::PhoneNumber_CountryCodeSource_Parse’ cannot be used as a function 220 | return PhoneNumber_CountryCodeSource_Parse(name, value); | ^ [36/65] cc -Isrc/chatty.p -Isrc -I../src -I../src/xeps/prpl/jabber -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpurple -I/usr/include/libhandy-1 -I/usr/include/evol
