Bug#1036113: libpurple0: license conflict with libsasl2

[Evangelos Ribeiro Tzaras]

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#1041411: [Debian-on-mobile-maintainers] Bug#1041411: libfeedback-dev: Documentation not registered with doc-base

[Evangelos Ribeiro Tzaras]

Control: close -1 0.2.0-3
Control: tags pending

On Tue, 2023-07-18 at 18:02 +0200, Evangelos Ribeiro Tzaras wrote:
> Package: libfeedback-dev
> Version: 0.2.0-2
> Severity: wishlist
> Tags: patch
> X-Debbugs-Cc: Evangelos Ribeiro Tzaras 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> libfeedback-dev ships documentation but it is not registered with doc-base.

MR on salsa has been accepted:
https://salsa.debian.org/DebianOnMobile-team/feedbackd/-/merge_requests/20


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#1041411: libfeedback-dev: Documentation not registered with doc-base

[Evangelos Ribeiro Tzaras]

Package: libfeedback-dev
Version: 0.2.0-2
Severity: wishlist
Tags: patch
X-Debbugs-Cc: Evangelos Ribeiro Tzaras 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libfeedback-dev ships documentation but it is not registered with doc-base.
>From d286cc983c0b24eb05f4c546d32d1cd1e614e1eb Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras 
Date: Tue, 18 Jul 2023 17:59:03 +0200
Subject: [PATCH] lfb-dev: Register documentation with doc-base

---
 debian/libfeedback-dev.doc-base | 12 
 1 file changed, 12 insertions(+)
 create mode 100644 debian/libfeedback-dev.doc-base

diff --git a/debian/libfeedback-dev.doc-base b/debian/libfeedback-dev.doc-base
new file mode 100644
index 000..a8d9780
--- /dev/null
+++ b/debian/libfeedback-dev.doc-base
@@ -0,0 +1,12 @@
+Document: libfeedback
+Title: libfeedback Reference Manual
+Author: Guido Günther
+Abstract: A library to trigger feedback (such as haptic feedback)
+ from your application. This document covers the C API,
+ but it also useful for GObject introspection bindings
+ of your favourite programming language.
+Section: Programming
+
+Format: HTML
+Index: /usr/share/doc/libfeedback-dev/libfeedback-0/index.html
+Files: /usr/share/doc/libfeedback-dev/libfeedback-0/*.html
-- 
2.40.1


- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libfeedback-dev depends on:
ii  gir1.2-lfb-0.0 0.2.0-2
ii  libfeedback-0.0-0  0.2.0-2
ii  libglib2.0-dev 2.74.6-2

libfeedback-dev recommends no packages.

libfeedback-dev suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuThlVLfdJmvLjimpkPDJsYprShkFAmS2tjYACgkQkPDJsYpr
ShlUfhAAiYUeATLrAdIlzgyE4fo4/6JbsAPeTXCVrkYl/mBm62R2GUxnv5umjCgO
giDs1egFVafLwn+rGsBYwpPpsHhSjLz8TEuboWuiOwCW+GU12F0HP+8JI3Fo7B/v
vADL1wsDeSeiirmh7ENOcV5LH5Jw7UIucvVgK8a8/42Fj7aURVe82OFokB5sXqZ7
qp7b586k0E8LOW6ZL0T9woIOPQKYS1ZJrC3uc7fk6p5w4heaMSDj33keuq2iVkmr
4HmLNrDCM4SQW7iHEcUuobHUboG5i7jJT5V64FEkV5vVrABOc2zIvF0uCO3OqUOz
WkhQ/zHhMxdgCE7raX3G3F4Rlagsl7XtcJNDFeJlOJOiNCmrTnbdwVUBsZn/rR0g
kFFnt0/8rTs6AoVGhMbbwh2BqRj8bwHTzLsaGse9JSyc4fTO1209PKU7B2PrgbwV
K+czXeVmE+BZ+La8B0YoKzP+AWofeSPHjTWnz677Hh0fn0OXkVyhSSv8Z1UBKb/G
aCbuskKoEMyYwxy3AGHqMbChOV3x0b0ankWpWbMdj8idq+E5hwG+D9n6AIyYDTtN
fkRYMJlhJM2pyJTMgbHVbDcaIjqtXSHl3Fd4pyDUkYrYI2m5HQGpwh9zUU/HZm3s
8KuSiVIY7Wp5VQPjOFLjA0IG7Y6lfYBcDNNEwtccfb2NOMqEcl4=
=X8K6
-END PGP SIGNATURE-

Bug#1037075: diffoscope: Get's killed trying to diff 2 large images (> 5GB)

[Evangelos Ribeiro Tzaras]

I forgot to add how to build the images:

On Sat, 03 Jun 2023 14:08:12 +0200 Evangelos Ribeiro Tzaras
 wrote:
> Package: diffoscope
> Version: 242
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Dear Maintainer,
> 
> I was trying to see if Mobian images build for the Librem5 would be
reproducible.

To build the images grab the mobian-recipes [0] repo from salsa.
The recipes are used by debos to build images.

My invocation looked like:

./build.sh -t librem5

[0] https://salsa.debian.org/Mobian-team/mobian-recipes/



> They were not.reproducible, so I wanted to run diffoscope on it, but sadly it
get's killed:

[...]

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#1037075: diffoscope: Get's killed trying to diff 2 large images (> 5GB)

[Evangelos Ribeiro Tzaras]

Package: diffoscope
Version: 242
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I was trying to see if Mobian images build for the Librem5 would be 
reproducible.
They were not.reproducible, so I wanted to run diffoscope on it, but sadly it 
get's killed:


> $ ls -l l5-phosh-{1,2}/mobian-librem5-phosh-20230603.img
- -rw-r--r-- 1 fortysixandtwo fortysixandtwo 60 Jun  3 06:22 
l5-phosh-1/mobian-librem5-phosh-20230603.img
- -rw-r--r-- 1 fortysixandtwo fortysixandtwo 60 Jun  3 06:45 
l5-phosh-2/mobian-librem5-phosh-20230603.img

  

  > 
$ diffoscope --debug l5-phosh-{1,2}/mobian-librem5-phosh-20230603.img

  
2023-06-03 13:58:43 D: diffoscope.main: Starting diffoscope 242

  
2023-06-03 13:58:43 D: diffoscope.presenters.formats: Will generate the 
following presenter formats: text

  
2023-06-03 13:58:43 D: diffoscope.environ: Normalising locale, timezone, etc. 
PATH is 
/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/x86_64-linux-gnu

  
2023-06-03 11:58:43 D: diffoscope.main: Starting comparison

  
2023-06-03 11:58:43 D: diffoscope.comparators: Loaded 90 comparator classes

  
2023-06-03 11:58:43 D: diffoscope.comparators.utils.specialize: 
l5-phosh-1/mobian-librem5-phosh-20230603.img not identified by any comparator. 
Magic says: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), 
end-CHS (0x3ff,255,63), startsector 1, 11718749 sectors, extended partition 
table (last)

  
2023-06-03 11:58:43 D: diffoscope.comparators.utils.specialize: 
l5-phosh-2/mobian-librem5-phosh-20230603.img not identified by any comparator. 
Magic says: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), 
end-CHS (0x3ff,255,63), startsector 1, 11718749 sectors, extended partition 
table (last)

  
2023-06-03 11:58:43 D: diffoscope.comparators.utils.compare: Comparing 
l5-phosh-1/mobian-librem5-phosh-20230603.img (FilesystemFile) and 
l5-phosh-2/mobian-librem5-phosh-20230603.img (FilesystemFile)

  
2023-06-03 11:58:43 D: diffoscope.comparators.utils.specialize: 
l5-phosh-1/mobian-librem5-phosh-20230603.img not identified by any comparator. 
Magic says: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), 
end-CHS (0x3ff,255,63), startsector 1, 11718749 sectors, extended partition 
table (last)

  
2023-06-03 11:58:43 D: diffoscope.comparators.utils.specialize: 
l5-phosh-2/mobian-librem5-phosh-20230603.img not identified by any comparator. 
Magic says: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), 
end-CHS (0x3ff,255,63), startsector 1, 11718749 sectors, extended partition 
table (last)

  
2023-06-03 11:58:43 D: diffoscope.comparators.utils.file: 
has_same_content(l5-phosh-1/mobian-librem5-phosh-20230603.img, 
l5-phosh-2/mobian-librem5-phosh-20230603.img)

 

Bug#1037061: battery-stats: does not find power supply on Librem 5

[Evangelos Ribeiro Tzaras]

Package: battery-stats
Version: 0.5.6-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I have installed battery-stats on Debian bookworm on my Librem 5
and noticed that the "Battery Charge Graph" was showing an empty plot.

Further /var/log/battery-stats did not contain anything useful.
So I updated the existing patch that fixed #998418.

Please find my patch attached below, or on salsa:
https://salsa.debian.org/debian/battery-stats/-/merge_requests/2

Note, that I did not explicitly test on any laptop.


*** ./0001-Update-patch-adding-more-power-supplies.patch
- From 3a66fa24bd80a4a1902457ef624dec1ee07f64ee Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras 
Date: Sat, 3 Jun 2023 03:30:43 +0200
Subject: [PATCH] Update patch adding more power supplies

Chargers and Batteries on the L5 are not recognized
(because they do not use BAT0, AC, ..)

$ ls /sys/class/power_supply
bq25890-charger  max170xx_battery  tps6598x-source-psy-0-003f

This update considers $foo a battery
if it's /sys/class/power_supply/$foo/type reads "Battery".
And $foo is considered a charger
if it exposes the file /sys/class/power_supply/$foo/online
- ---
 ...1000-add-more-power-supplies-support.patch | 40 +--
 1 file changed, 28 insertions(+), 12 deletions(-)

diff --git a/debian/patches/1000-add-more-power-supplies-support.patch 
b/debian/patches/1000-add-more-power-supplies-support.patch
index d9aac0a..5b5bda9 100644
- --- a/debian/patches/1000-add-more-power-supplies-support.patch
+++ b/debian/patches/1000-add-more-power-supplies-support.patch
@@ -1,15 +1,19 @@
- -Description: Add support for more power supplies
- - Depending on the computer, a different power_supply name can be used.
- - Add support for more power supplies and use a loop to factorize code.
- -Author: Nicolas Schodet 
+From: Nicolas Schodet 
+Date: Sat, 3 Jun 2023 03:06:04 +0200
+Subject: Add support for more power supplies
+
 Bug-Debian: 998412
 
+Depending on the computer, a different power_supply name can be used.
+Add support for more power supplies and use a loop to factorize code.
+
+Last-Updated: 2023-06-03
 ---
- - src/battery-stats-collector | 15 ---
- - 1 file changed, 8 insertions(+), 7 deletions(-)
+ src/battery-stats-collector | 19 +++
+ 1 file changed, 11 insertions(+), 8 deletions(-)
 
 diff --git a/src/battery-stats-collector b/src/battery-stats-collector
- -index 8e3cff7..c5d054a 100755
+index 8e3cff7..d20b828 100755
 --- a/src/battery-stats-collector
 +++ b/src/battery-stats-collector
 @@ -22,13 +22,14 @@ get_logline() {
@@ -24,13 +28,25 @@ index 8e3cff7..c5d054a 100755
 -aconline=$(cat /sys/class/power_supply/ADP1/online)
 -else
 +aconline=notfound
- -+for ac in AC AC0 ACAD ADP0 ADP1; do
- -+if [ -f /sys/class/power_supply/$ac/online ]; then
- -+aconline=$(cat /sys/class/power_supply/$ac/online)
- -+break
- -+fi
++for ac in /sys/class/power_supply/*; do
++  if [ -f "$ac/online" ]; then
++  aconline=$(cat "$ac/online")
++  break
++  fi
 +done
 +if [ notfound = "$aconline" ]; then
  echo "No power supply found"
  fi
  
+@@ -40,8 +41,10 @@ get_logline() {
+ 
+ now="energy_now"
+ full="energy_full"
+-for f in /sys/class/power_supply/BAT*; do
++for f in /sys/class/power_supply/*; do
+ [ -e "$f" ] || continue
++  [ -f "$f/type" ] || continue
++  [ "Battery" = $(cat "$f/type") ] || continue
+ if [ ! -e $f/$now ] ; then now="charge_now"; fi
+ if [ ! -e $f/$full ] ; then full="charge_full"; fi
+ energy_now=$(cat $f/$now) # uWh
- -- 
2.40.1



- -- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages battery-stats depends on:
ii  bc 1.07.1-3+b1
ii  gzip   1.12-1
ii  init-system-helpers1.65.2
ii  logrotate  3.21.0-1
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages battery-stats recommends:
ii  gnuplot-nox [gnuplot]  5.4.4+dfsg1-2+b2
ii  libtext-csv-perl   2.02-2
ii  python33.11.2-1+b1
ii  python3-matplotlib 3.6.3-1+b1

battery-stats suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuThlVLfdJmvLjimpkPDJsYprShkFAmR6sYUACgkQkPDJsYpr
Shn2cA//XC8nxDaAlb8G0N

Bug#1036914: [Debian-on-mobile-maintainers] Bug#1036914: unblock: librem5-flash-image/0.0.3-1

[Evangelos Ribeiro Tzaras]

On Mon, 2023-05-29 at 13:15 +0200, Guido Günther wrote:
> [ Other info ]
> I apologize for being late here, I simply missed that the version
> is outdated. I could have backported the patch but just using the
> upstream version (which didn't bring any other features) seemed more
> reasonable here.
> 
> unblock librem5-flash-image/0.0.3-1

I just wanted to add that the wiki on flashing Debian on to a L5 [0]
refers to this package (and suggests using a newer version),
so it would be very nice if the unblock request be granted :)

Thanks!

[0] https://wiki.debian.org/InstallingDebianOn/Purism/Librem5Phone

Bug#1036909: unblock: sofia-sip/1.12.11+20110422.1+1e14eea~dfsg-6

[Evangelos Ribeiro Tzaras]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: sofia-...@packages.debian.org
Control: affects -1 + src:sofia-sip

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please unblock package sofia-sip

I was made aware of another CVE in sofia-sips STUN handling
and have made an upload (debdiff attached) to sid.

Thanks in advance.

PS: I was told I can do it until 12:00 CEST :))


unblock sofia-sip/1.12.11+20110422.1+1e14eea~dfsg-6


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuThlVLfdJmvLjimpkPDJsYprShkFAmR0dcMACgkQkPDJsYpr
ShmYKw/9Eyjl90pBOM3PRe15EzUhfL1L047bN73goqIuYgfqXOzSBSg/7agi07ux
JmefVPpilU/tTjtA6We+E7uU26ik41WpNeydgznY495Y1ijy0FZXAazJ8iThVNqL
BQWmY0jUITgUhYnpRke+mfQjvhIIibWN22k33aHb37u+WVsao/LYLJw90SseC3zp
mGd1oiFzP8WDMhUpH8RgDaecI8Uw2nygXKVQxGhXFOnXIgSffQvfLVgS95C2h1SF
9nNIUoKeQgcyw9cqwK+xAlQHFGnS72x+oF3sX289hQcXgPdeyxnLGdukUvCBxWgH
GlQ+etTXHzaNeNScCfMJArrSSk2fIxdkR+NcGbGS7nDbKC8ztpYOEeOpM5vR23WK
0gqLeb+VOApwZpE0HdNbXvSHrF1xOs8EyqsTl51lTfRIO++kf3S99Se7tdP1+PQL
8IpQXZQxeL9hcz8EXZMyNZIvVDLcJ8068W6IajD71rapGWSVW+VlPGbCDOpOpJLl
GQiK8+6QQhHmaWOyjzQxxKrjLdsac3JZQn25dinrRIIyBdzrvolPiaoTxFHeBYlQ
YguSjrUf38NOeZj0psL8sQPR+HPG3esGZltN5gqnChIm8k0qYDdPD0Bvmm67mH1J
+L+j3hM8uD84sY0HXRbSlaQBv65e48YtgPJNllzAKW43TWoC7io=
=Lb2h
-END PGP SIGNATURE-
diff -Nru sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog
--- sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog  2023-05-23 
05:53:48.0 +0200
+++ sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog  2023-05-29 
11:36:38.0 +0200
@@ -1,3 +1,13 @@
+sofia-sip (1.12.11+20110422.1+1e14eea~dfsg-6) unstable; urgency=medium
+
+  * Add patch to fix reported CVE-2023-32307.
+For further information see:
+- CVE-2023-32307[0]
+[0] https://security-tracker.debian.org/tracker/CVE-2023-32307
+   https://www.cve.org/CVERecord?id=CVE-2023-32307 (closes: bug#1036847)
+
+ -- Evangelos Ribeiro Tzaras   Mon, 29 May 
2023 11:36:38 +0200
+
 sofia-sip (1.12.11+20110422.1+1e14eea~dfsg-5) unstable; urgency=medium
 
   * Add patch to fix reported CVE; add copyright of patch.
diff -Nru 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0008-stun-add-checks-for-attribute-length-before-read-fro.patch
 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0008-stun-add-checks-for-attribute-length-before-read-fro.patch
--- 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0008-stun-add-checks-for-attribute-length-before-read-fro.patch
1970-01-01 01:00:00.0 +0100
+++ 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0008-stun-add-checks-for-attribute-length-before-read-fro.patch
2023-05-29 11:31:03.0 +0200
@@ -0,0 +1,36 @@
+From: Xu Biang 
+Date: Sat, 6 May 2023 05:51:55 +0800
+Subject: stun: add checks for attribute length before read from it
+
+(cherry picked from commit c3bbc50c88d168065de34ca01b9b1d98c1b0e810)
+---
+ libsofia-sip-ua/stun/stun_common.c | 9 +
+ 1 file changed, 9 insertions(+)
+
+diff --git a/libsofia-sip-ua/stun/stun_common.c 
b/libsofia-sip-ua/stun/stun_common.c
+index 93b53ec..5540d16 100644
+--- a/libsofia-sip-ua/stun/stun_common.c
 b/libsofia-sip-ua/stun/stun_common.c
+@@ -250,6 +250,10 @@ int stun_parse_attr_error_code(stun_attr_t *attr, const 
unsigned char *p, unsign
+   uint32_t tmp;
+   stun_attr_errorcode_t *error;
+ 
++  if (len < 4) {
++return -1;
++  }
++
+   memcpy(, p, sizeof(uint32_t));
+   tmp = ntohl(tmp);
+   error = (stun_attr_errorcode_t *) malloc(sizeof(*error));
+@@ -271,6 +275,11 @@ int stun_parse_attr_uint32(stun_attr_t *attr, const 
unsigned char *p, unsigned l
+ {
+   uint32_t tmp;
+   stun_attr_changerequest_t *cr;
++
++  if (len < 4) {
++return -1;
++  }
++
+   cr = (stun_attr_changerequest_t *) malloc(sizeof(*cr));
+   memcpy(, p, sizeof(uint32_t));
+   cr->value = ntohl(tmp);
diff -Nru sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series
--- sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series 
2023-05-23 05:53:48.0 +0200
+++ sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series 
2023-05-29 11:31:03.0 +0200
@@ -5,3 +5,4 @@
 0003-cve-fix-heap-overflow-by-two.patch
 0004-cve-check-stun-message-and-attr-len.patch
 0005-cve-dos-wrong-assert.patch
+0008-stun-add-checks-for-attribute-length-before-read-fro.patch

Bug#1036625: unblock: sofia-sip/1.12.11+20110422.1+1e14eea~dfsg-5

[Evangelos Ribeiro Tzaras]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: sofia-...@packages.debian.org, t...@security.debian.org
Control: affects -1 + src:sofia-sip

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please unblock package sofia-sip

The latest version fixes bug#1031729 sofia-sip
informing of a denial of service CVE.

The fix for this CVE has been backported from the upstream sources.

You can find the debdiff between
1.12.11+20110422.1+1e14eea~dfsg-4 (currently in testing) and
1.12.11+20110422.1+1e14eea~dfsg-5
attached to this unblock request.

I have taken the liberty of uploading the package already
in anticipation that this request be granted on account that it fixes
a denial of service vulnerability.

unblock sofia-sip/1.12.11+20110422.1+1e14eea~dfsg-5

Cheers,
Evangelos

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuThlVLfdJmvLjimpkPDJsYprShkFAmRsqTgACgkQkPDJsYpr
ShkLCw/7B8AxGxufx6AiZ/2M684vpNTByWW4HVqvi1l37DemoxD9d2Bn8QGvhOE7
cYwleQiHwJ0QZxDAyCKrF4VC9Z51GY6F6GwAVK207MNMoksrnw77VSVyOVTJvOV4
Eix8bkniRTH9lyrv3lgUyYhWoNZqtyrNsO1KIYveVTT9VZpuBvS6cX12Tmng7Y0U
VcltDfrgCu+LQYOyjT04zs7tQt6VHncWhv7CSV/p0cIT8A8ZeJOU7RiQDkMBomyL
04FMG7nYdWQk+spSZ4/nLY4XzZ8NLZllTrtavVas7dPCqywX+VVvG3Zhb1e5hgqL
gVkkEL7lYN2uknPoCie7t2yXrIb65z8iQqYGYN/Kvk2m34X/haExHpsXB4iU1cUt
84FFOFMWEvTfV4iH1oxvd+vRtySsl3Kr276fvP/YilWvScQu8XI1iyLr/IxH8CJd
72NBxdGh/m1NfoK2kIv4fy/6F/BVBWl3mQy+yEkMJBmrFHCqQ6gN0rRFwxJSpwQv
8GadOpo4USNylLt+IND3VCnSHnl4Pv3H69oiiIuftt1QO8cmnGbDdURkkjAjRUMK
07L5j7kcUUCshNWmt+LXtbGPXaloRWalCM15roG/92vu790zo93hl8+yFJRGcsQk
FjRHDpa9BG/Z3LFpENPxRNygndb/AUE5NxWPChFzsfuHvqo7RzU=
=cxDT
-END PGP SIGNATURE-
diff -Nru sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog
--- sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog  2023-02-08 
09:46:57.0 +0100
+++ sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/changelog  2023-05-23 
05:53:48.0 +0200
@@ -1,3 +1,13 @@
+sofia-sip (1.12.11+20110422.1+1e14eea~dfsg-5) unstable; urgency=medium
+
+  * Add patch to fix reported CVE; add copyright of patch.
+For further information see:
+- CVE-2022-47516[0]
+[0] https://security-tracker.debian.org/tracker/CVE-2022-47516
+https://www.cve.org/CVERecord?id=CVE-2022-47516 (closes: bug#1031792)
+
+ -- Evangelos Ribeiro Tzaras   Tue, 23 May 
2023 05:53:48 +0200
+
 sofia-sip (1.12.11+20110422.1+1e14eea~dfsg-4) unstable; urgency=high (fixes a 
CVE)
 
   * Rename patches to indicate they have been picked from upstream
diff -Nru sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/copyright 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/copyright
--- sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/copyright  2023-02-08 
09:46:57.0 +0100
+++ sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/copyright  2023-05-23 
05:53:48.0 +0200
@@ -250,6 +250,7 @@
 Copyright:
   2022  Andrey Volk 
   2022  Qiuhao Li 
+  2022  Dave Horton 
 License-Grant:
  This library is free software;
  you can redistribute it and/or modify it
diff -Nru 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0005-cve-dos-wrong-assert.patch
 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0005-cve-dos-wrong-assert.patch
--- 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0005-cve-dos-wrong-assert.patch
1970-01-01 01:00:00.0 +0100
+++ 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/0005-cve-dos-wrong-assert.patch
2023-05-23 05:53:48.0 +0200
@@ -0,0 +1,22 @@
+From: Dave Horton 
+Date: Mon, 28 Nov 2022 14:44:30 -0500
+Subject: remove assert that can reasonably be expected to happen
+
+(cherry picked from commit cadf505d88e2971d24b6a4379ddbb1398d8ec443)
+---
+ libsofia-sip-ua/tport/tport.c | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/libsofia-sip-ua/tport/tport.c b/libsofia-sip-ua/tport/tport.c
+index c3bc2b6..18dfd47 100644
+--- a/libsofia-sip-ua/tport/tport.c
 b/libsofia-sip-ua/tport/tport.c
+@@ -3309,8 +3309,6 @@ tport_t *tport_tsend(tport_t *self,
+   tp_name_t tpn[1];
+   struct sigcomp_compartment *cc;
+ 
+-  assert(self);
+-
+   if (!self || !msg || !_tpn) {
+ msg_set_errno(msg, EINVAL);
+ return NULL;
diff -Nru sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series 
sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series
--- sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series 
2023-02-08 09:46:57.0 +0100
+++ sofia-sip-1.12.11+20110422.1+1e14eea~dfsg/debian/patches/series 
2023-05-23 05:53:48.0 +0200
@@ -4,3 +4,4 @@
 0002-cve-fix-oob-read-url_canonize.patch
 0003-cve-fix-heap-overflow-by-two.patch
 0004-cve-check-stun-message-and-attr-len.patch
+0005-cve-dos-wrong-assert.patch

Bug#1035662: unblock: libomemo/0.8.1-3

[Evangelos Ribeiro Tzaras]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: libom...@packages.debian.org
Control: affects -1 + src:libomemo

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please unblock package libomemo

Version 0.8.1-2 was uploaded earlier today to address #1034996,
but sadly introduced a similar issue when upgrading from
testing 0.8.1-1 to 0.8.1-2 because it was missing a Breaks/Replaces
relationship.

I have attached a debdiff from both 0.8.1-1 (currently in bookworm)
and 0.8.1-2 (uploaded earlier to sid) to
0.8.1-3 below.

I have manually tested the upgrade paths for the version in bullseye
(the original issue) as well as what we currently have in bookworm
to ensure no issues crop up.

I've gone ahead and uploaded the 0.8.1-3 already as the fix
is pretty small.
(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

Thanks in advance

unblock libomemo/0.8.1-3


*** /home/fortysixandtwo/git/salsa/tmp-omemo/libomemo_0.8.1-1_0.8.1-3.diff
diff -Nru libomemo-0.8.1/debian/changelog libomemo-0.8.1/debian/changelog
- --- libomemo-0.8.1/debian/changelog   2022-05-27 08:33:03.0 +0200
+++ libomemo-0.8.1/debian/changelog 2023-05-07 11:27:30.0 +0200
@@ -1,3 +1,17 @@
+libomemo (0.8.1-3) unstable; urgency=medium
+
+  * d/control: Add Breaks/Replaces on libomemo-dev
+which shipped link to shared object
+
+ -- Evangelos Ribeiro Tzaras   Sun, 07 May 
2023 11:27:30 +0200
+
+libomemo (0.8.1-2) unstable; urgency=medium
+
+  * Team upload.
+  * libomemo0: move libomemo.so back to -dev package (Closes: #1034996)
+
+ -- Arnaud Ferraris   Sun, 07 May 2023 10:51:51 +0200
+
 libomemo (0.8.1-1) unstable; urgency=medium
 
   * Use better git-buildpackage defaults
diff -Nru libomemo-0.8.1/debian/control libomemo-0.8.1/debian/control
- --- libomemo-0.8.1/debian/control 2022-05-27 08:33:03.0 +0200
+++ libomemo-0.8.1/debian/control   2023-05-07 11:27:30.0 +0200
@@ -20,6 +20,8 @@
 Rules-Requires-Root: no
 
 Package: libomemo-dev
+Breaks: libomemo0 (<= 0.8.1-2)
+Replaces: libomemo0 (<= 0.8.1-2) 
 Section: libdevel
 Architecture: any
 Multi-Arch: same
diff -Nru libomemo-0.8.1/debian/libomemo0.install 
libomemo-0.8.1/debian/libomemo0.install
- --- libomemo-0.8.1/debian/libomemo0.install   2022-05-27 08:33:03.0 
+0200
+++ libomemo-0.8.1/debian/libomemo0.install 2023-05-07 11:09:49.0 
+0200
@@ -1 +1 @@
- -usr/lib/*/libomemo.so*
+usr/lib/*/libomemo.so.*
diff -Nru libomemo-0.8.1/debian/libomemo-dev.install 
libomemo-0.8.1/debian/libomemo-dev.install
- --- libomemo-0.8.1/debian/libomemo-dev.install2022-05-27 
08:33:03.0 +0200
+++ libomemo-0.8.1/debian/libomemo-dev.install  2023-05-07 11:09:49.0 
+0200
@@ -1,2 +1,3 @@
 usr/include/*
+usr/lib/*/libomemo.so
 usr/lib/*/pkgconfig/*.pc

*** /home/fortysixandtwo/git/salsa/tmp-omemo/libomemo_0.8.1-2_0.8.1-3.diff
diff -Nru libomemo-0.8.1/debian/changelog libomemo-0.8.1/debian/changelog
- --- libomemo-0.8.1/debian/changelog   2023-05-07 10:51:51.0 +0200
+++ libomemo-0.8.1/debian/changelog 2023-05-07 11:27:30.0 +0200
@@ -1,3 +1,10 @@
+libomemo (0.8.1-3) unstable; urgency=medium
+
+  * d/control: Add Breaks/Replaces on libomemo-dev
+which shipped link to shared object
+
+ -- Evangelos Ribeiro Tzaras   Sun, 07 May 
2023 11:27:30 +0200
+
 libomemo (0.8.1-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru libomemo-0.8.1/debian/control libomemo-0.8.1/debian/control
- --- libomemo-0.8.1/debian/control 2023-05-07 10:51:51.0 +0200
+++ libomemo-0.8.1/debian/control   2023-05-07 11:27:30.0 +0200
@@ -20,6 +20,8 @@
 Rules-Requires-Root: no
 
 Package: libomemo-dev
+Breaks: libomemo0 (<= 0.8.1-2)
+Replaces: libomemo0 (<= 0.8.1-2) 
 Section: libdevel
 Architecture: any
 Multi-Arch: same


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuThlVLfdJmvLjimpkPDJsYprShkFAmRXfDgACgkQkPDJsYpr
ShmE4RAAnTv39PPtBUxT1LI0O6aVy07k/uVG/SW7wzVFEYTaHV7BHcoBjS/SHNqa
lqKACCkxhlq8Vt/NFvOR6ArhK5FWpcZSXm7udi2JHJR96QKuxYloTIv5DV++eoMq
hcjtQO44ox1j7HKZnmml/0B/uILwVr4hfnxkDCTQAnZD4y76v/86Ex8JkqeNM/RH
PJigLFwKn8/L0tYBOM6SGx1y5nsAa1WEENMa6XsVpmXuBBsAoaJJZIW0WipQvutu
8uzxGvhDmyNL4v/cvnt0MYP1/bM6sbCMmKvzKu9ehPyavKI2v6MZejotISJIGkXK
2XDdc4pTQ6Z0QhOs8wcKCUaMdvnXO+HQspWhrl+RtapRDAmu/SmcFSefPk76eECq
Xyp2LnZJ4h1lkQW3n7/h+VSO2pVXzEyvEoVjLG0jRgjehFWsidaQkHdCHJmw/Umn
IW5F9nxnXaG/7Qa8Fl2JxmZFNcv+HTemkft8RT7nlYJm4QWXk5gH7W0l815hd/Wj
LoyE/opqPj9OjFLV1t1YPhSeb/vwu13BYESHSFprsWGL9cxpD1S4nvYJB3BpRAaf
0RZLS74xAPBDizAct0gt1dX2MEnwNyUMiK/66kA0Xc2wYq1TZoa0APDysR3nsdRw
bncN6r8+1MPBIlOQY/OeXHy2t2q+C1usJHg9p24sD1RcMyhBQHU=
=MpTj
-END PGP SIGNATURE-

Bug#1028201: [Debian-on-mobile-maintainers] Bug#1028201: riseup-vpn unable to find a usable polkit agent under phosh

[Evangelos Ribeiro Tzaras]

Hi,

On Sun, 2023-01-08 at 18:54 +0530, Pirate Praveen via Debian-on-mobile-
maintainers wrote:
> Package: riseup-vpn,phosh
> severity: grave
> 
> On mobian under phosh (librem 5), riseup-vpn gives error.
> output of riseup-vpn attached.
> 
> phosh provides polkit-1-auth-agent
> 
> phosh 0.23
> riseup-vpn 0.21.11+ds1-2+b1

I've tried to reproduce this by running 
$ pkexec echo bla

On both my Pinephone running Mobian, as well as on my Librem 5 running PureOS
the polkit authentication dialog is presented.

If you send a SIGUSR1 to phosh you can enable debug logging.
You should find something like the following in your journal:

Jan 17 18:10:04 hades phosh[1264]: New prompt for Authentication is needed to
run `/usr/bin/echo' as the super user
Jan 17 18:10:04 hades phosh[1264]: Adding PHOSH_STATE_MODAL_SYSTEM_PROMPT to
shells state. New state: PHOSH_STATE_MODAL_SYSTEM_PROMPT

While I've not tried it with riseup this test should already indicate whether
polkit authentication itself is working in phosh itself.


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#1018134: [Debian-on-mobile-maintainers] Bug#1018134: Bug#1018134: chatty: bump severity to serious for ongoing evolution transitions

[Evangelos Ribeiro Tzaras]

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#1019913: libsoup3: segmentation fault when using HTTP2

[Evangelos Ribeiro Tzaras]

Source: libsoup3
Version: 3.2.0-1
Severity: important
Forwarded: https://gitlab.gnome.org/GNOME/libsoup/-/issues/302

Dear Maintainer,

libsoup3 sometimes runs into a segmentation fault when using HTTP2
that can be worked around by forcing HTTP1 usage with the environment variable
SOUP_FORCE_HTTP1=1


Logs will show the following type of warnings:

libsoup-http2-WARNING **: 18:32:30.072: 
(../http2/soup-client-message-io-http2.c:410):io_read: runtime check failed: 
(io->in_callback == 0)

before running into a segmentation fault.


Thank you for your work on maintaining libsoup3
and especially your work on the recent transition!


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1019207: git-buildpackage: Update documentation of gbp-push to reflect skipping debian-branch was dropped

[Evangelos Ribeiro Tzaras]

Package: git-buildpackage
Version: 0.9.28
Severity: wishlist

Dear Maintainer,

the docs (wrongly) mention that one can pass an empty string for the 
debian-branch,
but apparently this functionality was dropped without updating the 
documentation.

>From `man gbp-push`:

   --debian-branch=branch_name
  The  branch  in  the Git repository the Debian package is being 
developed on. If set to
  the empty value the branch will not be pushed.

Trying it:

> $ gbp push --debian-branch='' salsa_rw
gbp:error: You are not on branch '' but on 'debian/master'
gbp:error: Use --ignore-branch to ignore or --debian-branch to set the branch 
name.

> $ gbp push --debian-branch= salsa_rw
gbp:error: You are not on branch '' but on 'debian/master'
gbp:error: Use --ignore-branch to ignore or --debian-branch to set the branch 
name.


Thanks for maintaing git-buildpackage!

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages git-buildpackage depends on:
ii  devscripts 2.22.2
ii  git1:2.37.2-1
ii  man-db 2.10.2-3
ii  python33.10.6-1
ii  python3-dateutil   2.8.1-6
ii  python3-pkg-resources  59.6.0-1.2
ii  sensible-utils 0.0.17

Versions of packages git-buildpackage recommends:
ii  cowbuilder0.89
ii  pbuilder  0.231
ii  pristine-tar  1.49
ii  python3-requests  2.27.1+dfsg-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.9.11p3-1
ii  unzip6.0-27

-- no debconf information

Bug#688228: python-gi: Add README.Debian explaining how to get information on the python bindings

[Evangelos Ribeiro Tzaras]

control: retitle -1 Provide doc package on how to use python bindings
control: tags -1 patch

On Sat, 23 Jan 2021 18:40:05 + Stephan Lachnit
 wrote:
> Just reading through this issues, and this seems to be fixed a while ago.
> 
> 1. The documentation for PyGObject is available now [1].

Ideally this should be build as a -doc package,
for which I've created a WIP MR on salsa [2].

I've also attached it as a patch, but I want to point out again, 
that this is not quite working, so any help would be appreciated.

> 2. Gtk bindings are now in a separate package, e.g. gir1.2-gtk-3.0
> 
> I think this can be closed by now.

I think this should only be closed once the (proposed) -doc package hits the
archive.

> [1] https://lazka.github.io/pgi-docs/
[2] https://salsa.debian.org/gnome-team/pygobject/-/merge_requests/7

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
From 97a672f0e2511df76f728e2bad398aeb06219697 Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras 
Date: Sun, 4 Sep 2022 11:08:06 +0200
Subject: [PATCH] Install docs in new python-gi-doc package

Closes: #688228
---
 debian/control   | 19 +++
 debian/control.in| 19 +++
 debian/python-gi-doc.install |  1 +
 debian/rules | 10 ++
 4 files changed, 49 insertions(+)
 create mode 100644 debian/python-gi-doc.install

diff --git a/debian/control b/debian/control
index 7201034e..c9b5c4e3 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Build-Depends: at-spi2-core ,
debhelper-compat (= 13),
dh-sequence-gnome,
dh-sequence-python3,
+   dia ,
dpkg-dev (>= 1.16.1~),
gir1.2-gtk-3.0 ,
libcairo2-dev,
@@ -25,6 +26,8 @@ Build-Depends: at-spi2-core ,
python3-flake8 ,
python3-pytest ,
python3-setuptools,
+   python3-sphinx ,
+   python3-sphinx-rtd-theme ,
xauth ,
xvfb 
 Rules-Requires-Root: no
@@ -40,6 +43,7 @@ Depends: gir1.2-glib-2.0 (>= 1.48.0),
  ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends}
+Suggests: python-gi-doc
 Description: Python 3 bindings for gobject-introspection libraries
  GObject is an abstraction layer that allows programming with an object
  paradigm that is compatible with many languages. It is a part of Glib,
@@ -96,3 +100,18 @@ Description: Python 3 Cairo bindings for the GObject library
  .
  This package contains the Python 3 Cairo bindings for GObject. It is mostly
  used by other bindings to map their GObjects to Python objects.
+
+Package: python-gi-doc
+Architecture: all
+Section: doc
+Build-Profiles: 
+Depends:
+ ${misc:Depends},
+ ${sphinxdoc:Depends},
+Description: Documentation for python3 bindinfs for gobject-introspection libraries
+ GObject is an abstraction layer that allows programming with an object
+ paradigm that is compatible with many languages. It is a part of Glib,
+ the core library used to build GTK+ and GNOME.
+ .
+ This package contains the documentation for how to use the
+ python3 bindings.
diff --git a/debian/control.in b/debian/control.in
index 5ea09bc9..688d4867 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -8,6 +8,7 @@ Build-Depends: at-spi2-core ,
debhelper-compat (= 13),
dh-sequence-gnome,
dh-sequence-python3,
+   dia ,
dpkg-dev (>= 1.16.1~),
gir1.2-gtk-3.0 ,
libcairo2-dev,
@@ -21,6 +22,8 @@ Build-Depends: at-spi2-core ,
python3-flake8 ,
python3-pytest ,
python3-setuptools,
+   python3-sphinx ,
+   python3-sphinx-rtd-theme ,
xauth ,
xvfb 
 Rules-Requires-Root: no
@@ -36,6 +39,7 @@ Depends: gir1.2-glib-2.0 (>= 1.48.0),
  ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends}
+Suggests: python-gi-doc
 Description: Python 3 bindings for gobject-introspection libraries
  GObject is an abstraction layer that allows programming with an object
  paradigm that is compatible with many languages. It is a part of Glib,
@@ -92,3 +96,18 @@ Description: Python 3 Cairo bindings for the GObject library
  .
  This package contains the Python 3 Cairo bindings for GObject. It is mostly
  used by other bindings to map their GObjects to Python objects.
+
+Package: python-gi-doc
+Architecture: all
+Section: doc
+Build-Profiles: 
+Depends:
+ ${misc:Depends},
+ ${sphinxdoc:Depends},
+Description: Documentation for python3 bindinfs for gobject-introspection libraries
+ GObject is an abstraction layer that allows programming with an object
+ paradigm that is compatible with many languages. It is a part of Glib,
+ the core library used to build GTK+ and GNOME.
+ .
+ This package c

Bug#1019132: pygobject: FTBFS if build twice in a row

[Evangelos Ribeiro Tzaras]

control: tags -1 patch

On Sun, 04 Sep 2022 11:44:43 +0200 Evangelos Ribeiro Tzaras
 wrote:
> Source: pygobject
> Version: 3.42.2-2
> Severity: normal
> User: debian...@lists.debian.org
> Usertags: qa-doublebuild
> 
> Hi,
> 
> while playing with the package I've noticed that the package FTBFS if
> build twice in a row with the following error:
> 
> 
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pygobject using existing
./pygobject_3.42.2.orig.tar.xz

[...]

> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -i -I -b . subprocess returned exit
status 1

I've opened a MR on salsa [0] as well as attaching the patch here
as I'm not sure how you prefer to receive patches

[0] https://salsa.debian.org/gnome-team/pygobject/-/merge_requests/6

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
From caea89235bb9e851d34047f4b52e4640e287b7fd Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras 
Date: Sun, 4 Sep 2022 11:27:56 +0200
Subject: [PATCH] d/rules: Clean up all build files

we want to have a pristine directory after running
debian/rules clean

This patch gets rid of all the files left behind.

Closes: #1019132
---
 debian/rules | 9 +
 1 file changed, 9 insertions(+)

diff --git a/debian/rules b/debian/rules
index c2a3ef0a..981f6f0e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -70,3 +70,12 @@ override_dh_makeshlibs:
 
 override_dh_installchangelogs:
 	dh_installchangelogs -XChangeLog
+
+override_dh_clean:
+	dh_clean
+	rm -f config.h
+	rm -f gi/*.so
+	rm -f tests/*.gir
+	rm -f tests/*.typelib
+	rm -f tests/*.so
+	rm -f tests/gschemas.compiled
-- 
2.37.2



signature.asc
Description: This is a digitally signed message part

Bug#1019132: pygobject: FTBFS if build twice in a row

[Evangelos Ribeiro Tzaras]

Source: pygobject
Version: 3.42.2-2
Severity: normal
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

while playing with the package I've noticed that the package FTBFS if
build twice in a row with the following error:


dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building pygobject using existing 
./pygobject_3.42.2.orig.tar.xz
dpkg-source: error: cannot represent change to 
gi/_gi.cpython-310-x86_64-linux-gnu.so: binary file contents changed
dpkg-source: error: add gi/_gi.cpython-310-x86_64-linux-gnu.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 
'gi/_gi.cpython-310-x86_64-linux-gnu.so' will not be represented in diff
dpkg-source: error: cannot represent change to 
gi/_gi.cpython-310d-x86_64-linux-gnu.so: binary file contents changed
dpkg-source: error: add gi/_gi.cpython-310d-x86_64-linux-gnu.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 
'gi/_gi.cpython-310d-x86_64-linux-gnu.so' will not be represented in diff
dpkg-source: error: cannot represent change to 
gi/_gi_cairo.cpython-310-x86_64-linux-gnu.so: binary file contents changed
dpkg-source: error: add gi/_gi_cairo.cpython-310-x86_64-linux-gnu.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 
'gi/_gi_cairo.cpython-310-x86_64-linux-gnu.so' will not be represented in diff
dpkg-source: error: cannot represent change to 
gi/_gi_cairo.cpython-310d-x86_64-linux-gnu.so: binary file contents changed
dpkg-source: error: add gi/_gi_cairo.cpython-310d-x86_64-linux-gnu.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 
'gi/_gi_cairo.cpython-310d-x86_64-linux-gnu.so' will not be represented in diff
dpkg-source: error: cannot represent change to 
tests/GIMarshallingTests-1.0.typelib: binary file contents changed
dpkg-source: error: add tests/GIMarshallingTests-1.0.typelib in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: error: cannot represent change to tests/Regress-1.0.typelib: 
binary file contents changed
dpkg-source: error: add tests/Regress-1.0.typelib in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: error: cannot represent change to tests/gschemas.compiled: binary 
file contents changed
dpkg-source: error: add tests/gschemas.compiled in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: error: cannot represent change to tests/libgimarshallingtests.so: 
binary file contents changed
dpkg-source: error: add tests/libgimarshallingtests.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 'tests/libgimarshallingtests.so' 
will not be represented in diff
dpkg-source: error: cannot represent change to tests/libregress.so: binary file 
contents changed
dpkg-source: error: add tests/libregress.so in debian/source/include-binaries 
if you want to store the modified binary in the debian tarball
dpkg-source: warning: executable mode 0755 of 'tests/libregress.so' will not be 
represented in diff
dpkg-source: error: cannot represent change to 
tests/testhelper.cpython-310-x86_64-linux-gnu.so: binary file contents changed
dpkg-source: error: add tests/testhelper.cpython-310-x86_64-linux-gnu.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 
'tests/testhelper.cpython-310-x86_64-linux-gnu.so' will not be represented in 
diff
dpkg-source: error: cannot represent change to 
tests/testhelper.cpython-310d-x86_64-linux-gnu.so: binary file contents changed
dpkg-source: error: add tests/testhelper.cpython-310d-x86_64-linux-gnu.so in 
debian/source/include-binaries if you want to store the modified binary in the 
debian tarball
dpkg-source: warning: executable mode 0755 of 
'tests/testhelper.cpython-310d-x86_64-linux-gnu.so' will not be represented in 
diff
dpkg-source: error: unrepresentable changes to source
dpkg-buildpackage: error: dpkg-source -i -I -b . subprocess returned exit 
status 1


Thanks for maintaing pygobject!

Bug#1018940: devhelp: Scrolling does not immediately update the view

[Evangelos Ribeiro Tzaras]

Some more information below.

On Fri, 02 Sep 2022 10:05:40 +0200 Evangelos Ribeiro Tzaras
 wrote:
> Package: devhelp
> Version: 43~beta-2
> Severity: normal
> 
> Dear Maintainer,
> 
> on my system devhelp does not scroll as it used to.
> If I try scrolling the view either using the mouse scroll wheel
> or by keyboard navigation using the up/down arrow the view will not update.
> 
> However if I click inside the view it will update by the previously scrolled
amount.
> 
> I'm using this in a GNOME (wayland) session.

and using AMD graphics (in case this is relevant)

> I'll follow up later with `WAYLAND_DEBUG=1`, maybe it contains something
pointing
> to the underlying issue.

[3487939.134] wl_callb...@53.done(30222081)
[3492764.387] wl_pointer@13.axis_source(0)
[3492764.402] wl_pointer@13.axis_discrete(0, 1)
[3492764.405] wl_poin...@13.axis(30226906, 0, 10.)
[3492764.409] wl_pointer@13.frame()
[3493389.382] wl_pointer@13.axis_source(0)
[3493389.400] wl_pointer@13.axis_discrete(0, 1)
[3493389.403] wl_poin...@13.axis(30227531, 0, 10.)
[3493389.407] wl_pointer@13.frame()
[3494088.416] wl_pointer@13.axis_source(0)
[3494088.432] wl_pointer@13.axis_discrete(0, 1)
[3494088.437] wl_poin...@13.axis(30228230, 0, 10.)
[3494088.440] wl_pointer@13.frame()
[3495337.607] wl_pointer@13.axis_source(0)
[3495337.624] wl_pointer@13.axis_discrete(0, 1)
[3495337.628] wl_poin...@13.axis(30229479, 0, 10.)
[3495337.631] wl_pointer@13.frame()
[3501268.617] wl_pointer@13.axis_source(0)
[3501268.640] wl_pointer@13.axis_discrete(0, 1)
[3501268.643] wl_poin...@13.axis(30235410, 0, 10.)
[3501268.646] wl_pointer@13.frame()

All of the above is scrolling (using the mouse)

[3533684.461] xdg_wm_b...@30.ping(30267826)
[3533684.490]  -> xdg_wm_b...@30.pong(30267826)
[3533684.496] wl_pointer@13.button(17474, 30267826, 272, 1)
[3533684.505] wl_pointer@13.frame()
[3533693.329]  -> wl_surface@38.attach(wl_buffer@52, 0, 0)
[3533693.342]  -> wl_surface@38.set_buffer_scale(1)
[3533693.346]  -> wl_surface@38.damage(391, 67, 589, 1033)
[3533693.351]  -> xdg_toplevel@41.set_min_size(290, 139)
[3533693.354]  -> xdg_toplevel@41.set_max_size(0, 0)
[3533693.357]  -> xdg_surface@40.set_window_geometry(20, 20, 960, 1080)
[3533693.371]  -> wl_surface@38.frame(new id wl_callback@53)
[3533693.379]  -> wl_surface@38.commit()
[3533693.897] wl_buffer@52.release()
[3533700.824] wl_display@1.delete_id(53)
[3533700.834] wl_callb...@53.done(30267843)
[3533700.945]  -> wl_surface@38.attach(wl_buffer@52, 0, 0)
[3533700.961]  -> wl_surface@38.set_buffer_scale(1)
[3533700.965]  -> wl_surface@38.damage(965, 67, 15, 1033)
[3533700.968]  -> xdg_toplevel@41.set_min_size(290, 139)
[3533700.970]  -> xdg_toplevel@41.set_max_size(0, 0)
[3533700.972]  -> xdg_surface@40.set_window_geometry(20, 20, 960, 1080)
[3533700.984]  -> wl_surface@38.frame(new id wl_callback@53)
[3533700.988]  -> wl_surface@38.commit()
[3533701.160] wl_buffer@52.release()
[3533708.721] wl_display@1.delete_id(53)


The surface will only get damaged/redrawn once I click (wl_pointer@13.button).

I've also tested epiphany-browser as I've suspected this might actually be a
webkit-gtk bug, but could not reproduce it there.


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1018940: devhelp: Scrolling does not immediately update the view

[Evangelos Ribeiro Tzaras]

Package: devhelp
Version: 43~beta-2
Severity: normal

Dear Maintainer,

on my system devhelp does not scroll as it used to.
If I try scrolling the view either using the mouse scroll wheel
or by keyboard navigation using the up/down arrow the view will not update.

However if I click inside the view it will update by the previously scrolled 
amount.

I'm using this in a GNOME (wayland) session.

I'll follow up later with `WAYLAND_DEBUG=1`, maybe it contains something 
pointing
to the underlying issue.

Thanks for maintaing devhelp!


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages devhelp depends on:
ii  libc62.34-7
ii  libdevhelp-3-6   43~beta-2
ii  libglib2.0-0 2.73.3-3
ii  libgtk-3-0   3.24.34-3
ii  libpango-1.0-0   1.50.9+ds-1
ii  libwebkit2gtk-4.1-0  2.36.7-1
ii  python3  3.10.6-1

Versions of packages devhelp recommends:
ii  libglib2.0-doc   2.73.3-3
ii  libgtk-3-doc 3.24.34-3
ii  libpango1.0-doc  1.50.9+ds-1

devhelp suggests no packages.

-- no debconf information

Bug#1018707: ITP: gnss-share -- Share GNSS character devices over a unix socket

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: gnss-share
  Version : 0.4
  Upstream Author : Clayton Craft 
* URL : https://gitlab.com/postmarketOS/gnss-share
* License : GPL-3+
  Programming Lang: Go
  Description : Share GNSS character devices over a unix socket

An app for sharing GNSS location data, with support multiple clients and
loading/saving AGPS data.
This is meant to replace things like gpsd, and gps-share, and work together
with geoclue* or other clients that support fetching NMEA location data over
sockets.


I plan to maintain this within the DebianOnMobile-team umbrella.

Bug#1018706: ITP: satellite-gtk -- satellite-gtk

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: satellite-gtk
  Version : 0.2.7
  Upstream Author : Teemu Ikonen 
* URL : https://codeberg.org/tpikonen/satellite/
* License : GPL-3+
  Programming Lang: Python
  Description : Adaptive GTK application which displays GNSS data

 Satellite is an adaptive GTK / libhandy application
 which displays global navigation satellite system (GNSS: GPS et al.) data
 obtained from ModemManager API.
 .
 It can also be used to record gpx tracks.


The project was originally written with the PinePhone in mind,
but there is also some work for bringing it to the Librem5
which relies on gnss-share (needs to be packaged in Debian)
instead of using ModemManager.

This package is useful for checking the number of satellites in view,
their
I plan to maintain it as part of either DebianOnMobile-team
or the Python (Application) team.

Bug#1018680: libsofia-sip-ua0: STUN module uses version dependent SSL/TLS methods

[Evangelos Ribeiro Tzaras]

Package: libsofia-sip-ua0
Version: 1.12.11+20110422.1+1e14eea~dfsg-3
Severity: normal

Bug #871435 was not fixed completely in 1.12.11+20110422.1+1e14eea~dfsg-2
as there is still an instance of version dependent methods
as found by grepping for '(SSL|TLS).*_method'

libsofia-sip-ua/stun/stun.c:1356 ctx = SSL_CTX_new(TLSv1_client_method());

Bug#1017975: [Debian-on-mobile-maintainers] Bug#1017975: ModemManager does not install qmicli needed for unlocking scripts.

[Evangelos Ribeiro Tzaras]

Hi and thanks for your report!

On Tue, 2022-08-23 at 13:56 +0300, Ilja Sidoroff wrote:
> Package: modemmanager
> Version: 1.18.10-1
> Severity: normal
> 
> In reference to bug #1004447.
> 
> The FCC unlocking scripts (in /usr/share/ModemManager/fcc-
> unlock.available.d) 105b and 1199 use `qmicli-binary` to perform the
> unlocking operation. The binary, which is in libqmi-utils -package is
> not installed by default or as a dependency to modemmanager-package.
> If the binary is missing, the symptoms of the bug are as described in
> #1004447. This can probably simply be fixed by adding libqmi-utils as
> a dependency to modemmanager?

I don't think it should be a `Depends`, but a `Recommends:`

> 
> I also noticed that the script `1eac` uses mbimcli-binary, which also
> doesn't seem to installed by default, but I haven't examined that
> further.

same as above



-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#1017635: ITP: lsip6 -- Find link-local IPv6 address of remote end in point-to-point USB connections

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: lsip6
  Version : 0.1.0
  Upstream Author : Martijn Braam 
* URL : https://git.sr.ht/~martijnbraam/lsip6
* License : MIT
  Programming Lang: Python
  Description : Finds remote link-local IPv6 address in point-to-point IPv6 
network

 `lsip6` is a `ls` for link-local IPv6 addresses
 This is very handy in finding e.g. USB connected mobile phone
 even without DHCP set up.
 .
 It sends a ICMPv6 (ping) to ff02::1
 (all devices on link)
 causing devices on the link to start Neighbor Solicitation
 (part of the IPv6 Neighbour Discovery Protocol NDP)
 in order to figure out how to talk to each other.



I intend to package this as part of the Python Application or
Debian on Mobile teams.

Bug#911075: tootle: sometimes doesn't refresh new data/timestamps

[Evangelos Ribeiro Tzaras]

Hi Jonathan,

thanks for the report!

On Mon, 15 Oct 2018 11:58:50 +0100 Jonathan Dowland  wrote:
> Package: tootle
> Version: 0.1.5-1
> Severity: normal
> 
> Sometimes a long-running tootle seems to not be refreshing any more;
> besides not receiving new toots, the timestamps on the toots displayed
> in the window are very out of date (e.g. still displaying "now" for
> toots originally tooted hours ago, including my own toots, as authored
> in tootle)

This was marked as fixed in tootle/1.0-alpha1-1,
since we have that in the archive for some time now and 
have even updated to a non alpha 1.0
I'm taking the liberty to close this bug.

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#910425: tootle: scaling breaks the layout

[Evangelos Ribeiro Tzaras]

Hi ghost,

thanks for the report!

On Sat, 06 Oct 2018 06:31:19 + ghost  wrote:
> Package: tootle
> Version: 0.1.5-1
> Severity: normal
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
>    I am using KDE and scale the display by 1.5 since my laptop has a
>    small screen.
> 
>    * What exactly did you do
>    Open the installed tootle.
> 
>    * What was the outcome of this action?
>    A part of the UI is invisible, I think it can be similarly reproduced
>    by setting GDK_DPI_SCALE=1.5
> 
>    * What outcome did you expect instead?
>    It should display properly with scaling.

This was marked as fixed in tootle/1.0-alpha1-1,
since we have that in the archive for some time now and 
have even updated to a non alpha 1.0
I'm taking the liberty to close this bug.

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1013305: tootle: please update to newer version

[Evangelos Ribeiro Tzaras]

A new version has been uploaded [0],
but we forgot to close the bug.

On Tue, 21 Jun 2022 10:58:22 +0200 Evangelos Ribeiro Tzaras
 wrote:
> Package: tootle
> Version: 1.0-alpha2-1+b1
> Severity: wishlist
> 
> I just noticed there's a 1.0 version out.
> 
> Would be cool to have this in unstable
> (and perhaps the latest 2.0 alpha in experimental).


[0] https://tracker.debian.org/media/packages/t/tootle/changelog-1.0-ds1-4
-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003

[Evangelos Ribeiro Tzaras]

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 +427,12 @@ char *url_canonize3(c

Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003

[Evangelos Ribeiro Tzaras]

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#1017068: [Debian-on-mobile-maintainers] Bug#1017068: gnome-calls: sip test fails when builds are running on machines without network

[Evangelos Ribeiro Tzaras]

Hi Shannon,

thanks for your report!

On Fri, 2022-08-12 at 16:30 -0400, Shannon Brady via Debian-on-mobile-
maintainers wrote:
> Package: gnome-calls
> X-Debbugs-Cc: shannonbr...@google.com
> Version: 43~alpha.2-1
> Severity: important
> 
> Dear Maintainer,
> When building this version of gnome-call on a system that is not connected to
> the network, builds will always fail the SIP test with the following error



> (/<>/_build/tests/sip:50791): CallsSipMediaPipeline-WARNING **:
> 12:24:34.431: Error on the message bus: Could not get/set settings from/on
> resource. (../gst/udp/gstmultiudpsink.c(1228):
> gst_multiudpsink_configure_client (): /GstPipeline:media-
> pipeline/GstUDPSink:rtcp-udp-sink:
> Invalid address family (got 10))
> --
> 
> Note that address_family 10 corresponds to AF_INT6, which is odd because the
> addresses that are assigned in the test are IPv4 addresses
> (https://gitlab.gnome.org/GNOME/calls/-/blob/master/tests/test-sip.c#L274) .
> Specifically 127.0.0 which is IPv4 localhost 

This is very interesting, thanks for investigating so thoroughly!

> However, this test will succeed on a build network that does have network and
> DNS.Is this expected behaviour? I would have assumed that builds should be
> able to succeed without internet connection.

Yeah it **should**.
I'll have to reproduce this on my end and see what can be done about it
upstream.

-- 
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;

[Evangelos Ribeiro Tzaras]

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#1017063: gnome-weather: fails to start up;

[Evangelos Ribeiro Tzaras]

Package: gnome-weather
Version: 43~beta-1
Severity: important

Dear Maintainer,


gnome-weather errors out with a critical on my testing/sid system when trying 
to launch it:

(org.gnome.Weather:2558104): Gjs-Console-CRITICAL **: 17:07:12.604: Error: 
Expected type object for argument 'boxed_type' but got type undefined
_init/GObject.ParamSpec.jsobject@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:404:24
@resource:///org/gnome/Weather/js/app/thermometer.js:49:36

I'm not quite sure if this warrants a higher severity or not,
I read the BTS docs as suggesting this might be `grave` indeed ;)


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-weather depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  geoclue-2.0  2.6.0-1
ii  gir1.2-adw-1 1.2~beta-1
ii  gir1.2-geoclue-2.0   2.6.0-1
ii  gir1.2-glib-2.0  1.72.0-1+b1
ii  gir1.2-gtk-4.0   4.6.6+ds-2
ii  gir1.2-gweather-4.0  4.0.0-2
ii  gjs  1.73.1-1
ii  libglib2.0-bin   2.72.3-1+b1

gnome-weather recommends no packages.

gnome-weather suggests no packages.

-- no debconf information

Bug#1016974: sofia-sip: CVE-2022-31001 CVE-2022-31002 CVE-2022-31003

[Evangelos Ribeiro Tzaras]

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#970697: tootle FTCBFS: does not pass a crossfile to meson

[Evangelos Ribeiro Tzaras]

Hi,

On Mon, 21 Sep 2020 23:09:21 +0200 Helmut Grohne  wrote:
> Source: tootle
> Version: 1.0-alpha1-1
> Tags: patch
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
> 
> tootle fails to cross build from source, because it does not pass a
> crossfile to meson. The easiest way of doing so - using
> dh_auto_configure - makes tootle cross buildable. Please consider
> applying the attached patch.
> 
> Helmut

Thanks for the report.

This was fixed with the latest upload with your patch applied
but because of  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#993088: tootle FTBFS: error: The name `get_phrase' does not exist in the context of `Soup.Status'

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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#1015419: gnome-calls: ftbfs with LTO (link time optimization) enabled

[Evangelos Ribeiro Tzaras]

control: forwarded -1 https://gitlab.gnome.org/GNOME/calls/-/issues/427

Hi Matthias and thanks for your report!

On Tue, 19 Jul 2022 16:52:35 + Matthias Klose  wrote:
> Package: src:gnome-calls
> Version: 43~alpha.1-1
> Severity: minor
> Tags: sid bookworm
> User: debian-...@lists.debian.org
> Usertags: ftbfs-lto
> 
> This package currently fails to build (at least on the amd64
> architecture) with link time optimizations enabled.  For a background
> for LTO please see
> 
> https://wiki.debian.org/ToolChain/LTO
> 
> The goal is to enable this optimization by default in an upcoming
> Debian release in dpkg-buildflags for 64bit architectures.  The goal
> is to get this package to build with link time optimizations, or to
> explicitly disable link time optimizations for this package build.
> 
> To reproduce the build failure, enable the lto optimization in
> testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
> in the debian/rules file, or if this macro is unset, just set it:
> 
> export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

I could reproduce the issue just now, thanks for the pointer.

Part of the problem seems to be that some wrapped symbols
(`--wrap` is passed to `ld`)
is being stripped/optimized away.

I will investigate and try to come up with a fix upstream
so that the we don't need to be wrapping the symbol any more.

It is currently used to stop the code from making contact lookups
which I've expected to fail in test environments such as in CI or buildd.
For this reason the tests use --wrap to stub out the relevant functions.

The correct fix would be making sure that the contact lookups with folks
are using some sort of dummy backend
as discussed in the upstream issue.

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


signature.asc
Description: This is a digitally signed message part

Bug#1001994: python3-pyotp: new upstream version

[Evangelos Ribeiro Tzaras]

Hi,

On Sun, 19 Dec 2021 21:58:32 +0100 Jean Felder 
wrote:
> Package: python3-pyotp
> Version: 2.3.0-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> Upstream released pyopt 2.6 in February 2021. Could you consider to
update the package?

I would also like to see 2.6 in Debian because numberstation [0]
depends on a feature that is not available in 2.3 [1]



[0] https://tracker.debian.org/pkg/numberstation
[1]
https://git.sr.ht/~martijnbraam/numberstation/tree/master/item/numberstation/otpurl.py#L51


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1014878: gtk4: FTBFS with nocheck profile; python3-gi missing from build-deps

[Evangelos Ribeiro Tzaras]

Control:
patch -1

On Wed, 13 Jul 2022 18:17:27 +0200 Evangelos Ribeiro Tzaras
 wrote:
> Source: gtk4
> Version: 4.6.5+ds-1pureos2
> Severity: normal
> 
> Dear Maintainer,
> 
> while building gtk4 in PureOS (hence the -) we ran into a FTBFS when
using nocheck:
> python3-gi is missing when building with nocheck, see:
> 
> ../../../testsuite/introspection/meson.build:1:0: ERROR: python3 is
missing modules: gi
> 
> from
>
https://lists.community.puri.sm/pipermail/librem5-builds/2022-July/003824.html
> 
> 

Patch attached


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
diff --git a/debian/control.in b/debian/control.in
index 4b611f9352..6be477143f 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -63,7 +63,7 @@ Build-Depends: adwaita-icon-theme ,
meson (>= 0.59),
pkg-config,
python3-docutils ,
-   python3-gi (>= 3.40) ,
+   python3-gi (>= 3.40),
sassc,
ttf-bitstream-vera ,
wayland-protocols (>= 1.23) [linux-any],

Bug#1014878: gtk4: FTBFS with nocheck profile; python3-gi missing from build-deps

[Evangelos Ribeiro Tzaras]

Source: gtk4
Version: 4.6.5+ds-1pureos2
Severity: normal

Dear Maintainer,

while building gtk4 in PureOS (hence the -) we ran into a FTBFS when using 
nocheck:
python3-gi is missing when building with nocheck, see:

../../../testsuite/introspection/meson.build:1:0: ERROR: python3 is missing 
modules: gi

from
https://lists.community.puri.sm/pipermail/librem5-builds/2022-July/003824.html


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1

[Evangelos Ribeiro Tzaras]

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#1014325: ITP: megapixels-postprocessd -- Image processing utility meant as companion for megapixels application

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: megapixels-postprocessd
  Version : 0.2.1
  Upstream Author : Martijn Braam 
* URL : https://git.sr.ht/~martijnbraam/postprocessd
* License : GPL-3+
  Programming Lang: C
  Description : Image processing utility meant as companion for Megapixels 
application

Companion project to Megapixels providing a native postprocessing pipeline,
It aims to improve the quality of pictures taken with Megapixels.

It can be used as a drop-in replacement for the postprocess.sh,
that gets shipped as part of the megapixels package.

As this package is closely related to Megapixels
It should also be maintained in the DebianOnMobile team.

Bug#1004899: ITP: numberstation -- TOTP Authenticator application

[Evangelos Ribeiro Tzaras]

Hi Thomas,

On Thu, 03 Feb 2022 10:05:34 +0100 Thomas Goirand  wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Thomas Goirand 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name    : numberstation
>   Version : 1.0.1
>   Upstream Author : Martijn Braam 
> * URL : https://git.sr.ht/~martijnbraam/numberstation
> * License : LGPL-3
>   Programming Lang: C, Python
>   Description : TOTP Authenticator application
> 
>  A Gnome Authenticator clone. This generates 2fa tokens based on secrets
>  installed. It registers as uri-handler for otpauth:// urls so they can be
>  added from Megapixels.
> 
> 


ftpmasters rejected the initial upload because one of the svg icon not being
mentioned in `d/copyright` [0]
and the binary package missing the `Section` field [1].

I've addressed these concerns in the attached patches and in MR on salsa [2]
(not sure what you're preference is).

I've also taken the liberty of adding a watch file and excluding another icon
(numberstation/icon/delete-symbolic.svg) where no license can be found in the
metadata.

I hope this helps getting the package into Debian!

[0]
https://alioth-lists.debian.net/pipermail/debian-on-mobile-maintainers/2022-February/001728.html
[1]
https://alioth-lists.debian.net/pipermail/debian-on-mobile-maintainers/2022-February/001700.html
[2]
https://salsa.debian.org/DebianOnMobile-team/numberstation/-/merge_requests/1


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
From 75221b86cdba4e26380ef8ffce2121629c299f88 Mon Sep 17 00:00:00 2001
From: Evangelos Ribeiro Tzaras 
Date: Sat, 2 Jul 2022 15:13:49 +0200
Subject: [PATCH 1/4] Update copyright

---
 debian/copyright | 446 +++
 1 file changed, 446 insertions(+)

diff --git a/debian/copyright b/debian/copyright
index 9f750ab..729234f 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -7,6 +7,14 @@ Files: *
 Copyright: (c) 2021, Martijn Braam 
 License: LGPL-3
 
+Files: data/org.postmarketos.Numberstation.svg
+Copyright: 2019  GNOME Design Team
+License: CC-BY-SA-4.0
+
+Files: data/org.postmarketos.Numberstation.appdata.xml
+Copyright: 2021  Martijn Braam
+License: CC0-1.0
+
 Files: debian/*
 Copyright: (c) 2022, Thomas Goirand 
 License: LGPL-3
@@ -27,3 +35,441 @@ License: LGPL-3
  .
  On Debian systems, the complete text of the GNU Lesser General
  Public License can be found in "/usr/share/common-licenses/LGPL-3".
+
+License: CC0-1.0
+ To the extent possible under law, the author(s) have dedicated all copyright
+ and related and neighboring rights to this software to the public domain
+ worldwide. This software is distributed without any warranty.
+ .
+ You should have received a copy of the CC0 Public Domain Dedication along with
+ this software. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.
+ .
+ On Debian systems, the complete text of the CC0 1.0 Universal license can be
+ found in ‘/usr/share/common-licenses/CC0-1.0’.
+
+License: CC-BY-SA-4.0
+ Attribution-ShareAlike 4.0 International
+ .
+ ===
+ .
+ Creative Commons Corporation ("Creative Commons") is not a law firm and
+ does not provide legal services or legal advice. Distribution of
+ Creative Commons public licenses does not create a lawyer-client or
+ other relationship. Creative Commons makes its licenses and related
+ information available on an "as-is" basis. Creative Commons gives no
+ warranties regarding its licenses, any material licensed under their
+ terms and conditions, or any related information. Creative Commons
+ disclaims all liability for damages resulting from their use to the
+ fullest extent possible.
+ .
+ Using Creative Commons Public Licenses
+ .
+ Creative Commons public licenses provide a standard set of terms and
+ conditions that creators and other rights holders may use to share
+ original works of authorship and other material subject to copyright
+ and certain other rights specified in the public license below. The
+ following considerations are for informational purposes only, are not
+ exhaustive, and do not form part of our licenses.
+ .
+ Considerations for licensors: Our public licenses are
+ intended for use by those authorized to give the public
+ permission to use material in ways otherwise restricted by
+ copyright and certain other rights. Our licenses are
+ irrevocable. Licensors should read and understand the terms
+ and conditions of the license they choose before applying it.
+ Licensors should also secure all rights necessary before
+ applying our licenses so that the public can reuse the
+ material as expected. Licensors should clearly mark any
+ material not subject to the license. This includes other CC-
+ licensed material, or material u

Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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#1011668: gnome-control-center: Hang on "cancelling" wired network settings panel

[Evangelos Ribeiro Tzaras]

Hi,

On Thu, 26 May 2022 04:57:41 + undef  wrote:
> Package: gnome-control-center
> Version: 1:42.1-2
> Severity: normal
> X-Debbugs-Cc: undef 
> 
> Dear Maintainer,
> 
> Since at least Gnome Control Center 42 closing the network panel causes g-c-c
to hang. The following steps reliably reproduce the issue:
> 1. Open g-c-c -> Network.
> 2. Select a network and edit it using the cog icon.
> 3. Without changing any setting, select cancel in the top left.
> 4. Observe the hang.
> 
> The following error is printed on the console:
> 
> (gnome-control-center:96744): Gtk-WARNING **: 03:34:34.701: Finalizing
GtkCheckButton 0x5823a9488d70, but it still has children left:
> 
> (gnome-control-center:96744): Gtk-WARNING **: 03:34:34.701:    - GtkBox
0x5823aa4bafa0
> 
> (gnome-control-center:96744): Gtk-CRITICAL **: 03:34:34.713:
WirelessSecurityWPAEAP 0x5823aa68b180 has a parent GtkBox 0x5823aa473680 during
dispose. Parents hold a reference, so this should not happen.
> Did you call g_object_unref() instead of gtk_widget_unparent()?
> 
> (gnome-control-center:96744): Gtk-CRITICAL **: 03:34:34.714:
gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
> 
> (gnome-control-center:96744): Gtk-CRITICAL **: 03:34:34.714:
gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed 
> 
> 
> I have tested this on my Debian desktop machine and my Mobian mobile device
(using Debian's g-c-c) to the same effect. A nearby Fedora 36 workstation prints
the same two warnings, but not the critical messages and does not hang.
> 
> Thank you.
> 
> 

I did run into the same issue at the time, but now it seems to be fixed (or at
least I cannot reproduce it any more).

I think this can be closed?

-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1013317: ITP: python3-banking -- FinTS banking application suitable for small screens

[Evangelos Ribeiro Tzaras]

On Tue, 21 Jun 2022 16:20:27 +0200 Evangelos Ribeiro Tzaras
 wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Evangelos Ribeiro Tzaras 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name    : python3-banking
>   Version : 0.5.1
>   Upstream Author : Jan-Michael Brummer 
> * URL : https://gitlab.com/tabos/banking
> * License : GPL-3+
>   Programming Lang: Python
>   Description : FinTS banking application suitable for small screens

One thing I forgot to mention:

I plan to maintain this within the Python team.

Cheers
-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19





signature.asc
Description: This is a digitally signed message part

Bug#1013317: ITP: python3-banking -- FinTS banking application suitable for small screens

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python3-banking
  Version : 0.5.1
  Upstream Author : Jan-Michael Brummer 
* URL : https://gitlab.com/tabos/banking
* License : GPL-3+
  Programming Lang: Python
  Description : FinTS banking application suitable for small screens

A GTK based banking application using the FinTS standard.
Check your balance and transactions.
It adapts to small screens, so it can be used on your mobile devices.


Not sure about the package name, could also go with banking-gtk or similar.

Bug#1013305: tootle: please update to newer version

[Evangelos Ribeiro Tzaras]

Package: tootle
Version: 1.0-alpha2-1+b1
Severity: wishlist

I just noticed there's a 1.0 version out.

Would be cool to have this in unstable
(and perhaps the latest 2.0 alpha in experimental).

Thank you for maintaining tootle!

Evangelos

Bug#1013292: ITP: git-of-theseus -- Analyze git repositories and create fancy plots

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: git-of-theseus
  Version : 0.2.0
  Upstream Author : Erik Bernhardsson 
* URL : https://github.com/erikbern/git-of-theseus
* License : Apache
  Programming Lang: Python
  Description : Analyze git repositories and create fancy plots

Create various plots on a git repository:
- Stack plots showing the total amount of code broken down by year it was added.
- Line plots showing percentage of code contributed by different authors.
- Survival plots showing how much of code has survived over the years.


I plan to maintain this package inside the Python Team.

Bug#1012050: ITP: alpine-chroot-install -- bootstrap Alpine Linux into a chroot

[Evangelos Ribeiro Tzaras]

Very nice! I can imagine this and pmbootstrap will come in quite handy!

On So, Mai 29 2022 at 14:21:52 +0200, Adam Borowski 
 wrote:

Package: wnpp
Severity: wishlist
Owner: Adam Borowski >
X-Debbugs-Cc: debian-de...@lists.debian.org 



* Package name: alpine-chroot-install
  Version : 0.13.3
  Upstream Author : Jakub Kirutka
* URL : 


* License : MIT
  Programming Lang: shell
  Description : bootstrap Alpine Linux into a chroot

 This script builds an Alpine Linux chroot, fetching packages from a 
network
 mirror.  The installed system is quite minimal, but contains enough 
to let

 you install whatever you need using "apk".
 .
 In other words, it's alpine's debootstrap.


This package will let us spy on the competition, steal their 
enablement

of musl, and possibly similar naughty deeds.

In theory it could also be used to port your stuff to Alpine, but 
that'd

be treason, right?

Bug#1011166: Chatty can no longer start since the last update

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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 

Bug#1007328: sofia-sip: please consider upgrading to 3.0 source format

[Evangelos Ribeiro Tzaras]

Hi Lucas,

On Tue, 15 Mar 2022 08:52:03 +0100 Lucas Nussbaum 
wrote:
> Source: sofia-sip
> Version: 1.12.11+20110422.1-2.2
> Severity: wishlist
> Tags: bookworm sid
> Usertags: format1.0 format1.0-nkp-nv
> 
> Dear maintainer,
> 
> This package is among the few (1.9%) that still use source format 1.0
in
> bookworm.  Please upgrade it to source format 3.0, as (1) this format
has many
> advantages, as documented in
https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
> this contributes to standardization of packaging practices.
> 
> Please note that this is also a sign that the packaging of this
software
> could maybe benefit from a refresh. It might be a good opportunity to
> look at other aspects as well.
> 
> 

This is fixed now (but we forgot to reflect this in the changelog [1]).
Thanks for the report!

[1]
https://metadata.ftp-master.debian.org/changelogs//main/s/sofia-sip/sofia-sip_1.12.11+20110422.1+1e14eea~dfsg-2_changelog

Cheers

Evangelos


signature.asc
Description: This is a digitally signed message part

Bug#1011001: ITP: picplanner -- GTK application for photography planning

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: picplanner
  Version : 0.1.0
  Upstream Author : Zwarf 
* URL : https://gitlab.com/Zwarf/picplanner/
* License : GPL-3.0+
  Programming Lang: C
  Description : GTK application for photography planning

A GTK application for photographers
tracking the movements of the Sun, Moon and the Milky Way.
Given a position on Earths surface and a time
it can calculate where the other celestial bodies are,
if they are visible
(and in which direction)

Bug#1010796: licensecheck: Licensecheck reports bogus exception

[Evangelos Ribeiro Tzaras]

Package: licensecheck
Version: 3.3.0-1
Severity: normal

Dear Maintainer,

while checking the license of
https://salsa.debian.org/pkg-voip-team/sofia-sip/-/raw/debian/latest/m4/sac-coverage.m
4
with licensecheck --deb-machine

it misdetects two exceptions

Files: m4/sac-coverage.m4
Copyright: 2001, 2004, Nokia and others.
License: GPL-2+ with Autoconf-2.0_AND_Autoconf-2.0~g10 exception

while it should be just Autoconf-2.0.


Cheers and thanks for maintaining licensecheck!

Evangelos

Bug#1003706: ITS: sofia-sip

[Evangelos Ribeiro Tzaras]

Hi,

On Fri, 14 Jan 2022 01:24:23 +0100 Jonas Smedegaard 
wrote:
> Source: sofia-sip
> Version: 1.12.11+20110422.1-2.1
> Severity: important
> X-Debbugs-Cc: Ron Lee 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Dear Ron,
> 
> It seems sofia-sip is not actively maintained, and I hereby request
to
> salvage the package.
> 
> The package has seen no uploads from you for 8 years, an NMU was made
5
> years ago seemingly uncommented by you, and several important bugs
have
> been open for several years with no comment from you.
> 
> Point is not to point fingers, only to elaborate on why I propose
that
> salvation is needed and I thereby initiate that process.  If you
prefer
> to maintain the package yourself then that's great - please do.
> 
> As per the salvaging process, I now give you some some time to
respond,
> and otherwise will issue a delayed NMU which effectuates my
salvation.
> 
> (I will most likely salvage as part of the VoIP team, and maintain it
> together with Evangelos, in case someone wonders about how this might
> collide/relate with the discussion in bug#965829).

Happy to be working with you in case this package gets salvaged.

> 
> 
> Kind regards,
> 
>  - Jonas
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHgwrIACgkQLHwxRsGg
> ASHuXg/+N35mRC4wIB8X0nrnYr13PNSMuAZTxNJ7i2r3ew5rvTidCVJD7iGHx60z
> uzocaTriKF7EhFH8HfRzoZ8gjyeGq35JLip/WgDnGKgmysl5GeMk7mfV3s1Glp3o
> +IoJw9M37lBfljyCleHzV0CTE6fk+0xdVC/ZW257xOn8LYjuYc3GWj0JRmsAK7+q
> MtWckVLwsFN4zz+bUWXgiUiWnLvh/jaFBUrxHIW8iw1iECW5FD2IVRY4l6LcdBM0
> ZRUJoDpy/A79LGcsa1kELz1TrN2adwXnUHu4RgHuPRrJHvKcTgMqKdYLI1S65sgE
> UDy+CuFo2mW9KVP+VilxNC+q65JODdnQVzXaxttjHnzx7XsxHEqP5XnMaqOJWuei
> SdXkPvP4pA5w8xV1rx80khojEcprGjuY1eVLqMNulGkpaLe3rkuLQ6YSOkYI8CZ4
> bOLWXvoPFLVbx57ciImvbdbM8mP2GERHwYROvuy64hTvxSg//v7CIkgnQbQ1xo60
> irKh2UQ23qNCiabWLIdcxjFKi8zARYQZHB1f5lRRrIw7e7ugNk2633dinfXceMXg
> 6gyr98TGwEWAiEMA5GpU4j2Ueb3pD5Q16Dzioqh3io0fFI//mqYdcXjc0C6nzgo3
> 4r+7O0SBpxRK20AC8Vnmu56jsk+wivphpiz0P+Q6YudFAQuzEVo=
> =gIB5
> -END PGP SIGNATURE-
> 
> 
Cheers
-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19





signature.asc
Description: This is a digitally signed message part

Bug#965829: sofia-sip: diff for NMU version 1.12.11+20110422.1-2.2

[Evangelos Ribeiro Tzaras]

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#1003853: RFS: sofia-sip/1.12.11+20110422.1-2.2 [NMU] [RC] -- Sofia SIP library

[Evangelos Ribeiro Tzaras]

Hi,

I forgot: If I understand the [Policy] correctly, this should be a
DELAYED/0, right?

[Policy]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu

On Sun, 2022-01-16 at 23:43 +0100, Evangelos Ribeiro Tzaras wrote:
> Package: sponsorship-requests
> Severity: important
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "sofia-sip":
> 
>  * Package name    : sofia-sip
>    Version : 1.12.11+20110422.1-2.2
>    Upstream Author : Pekka Pessi, Martti Mela, Kai Vehmanen
>  * URL : http://sofia-sip.sourceforge.net/
>  * License : LGPL-2.1
>  * Vcs :
> http://git.debian.org/?p=users/ron/sofia-sip.git;a=summary
>    Section : net
> 
> It builds those binary packages:
> 
>   sofia-sip-bin - Sofia-SIP library utilities
>   libsofia-sip-ua0 - Sofia-SIP library runtime
>   libsofia-sip-ua-dev - Sofia-SIP library development files
>   libsofia-sip-ua-glib3 - Sofia-SIP library glib/gobject interfaces
> runtime
>   libsofia-sip-ua-glib-dev - Sofia-SIP library glib/gobject interface
> development files
>   sofia-sip-doc - Sofia-SIP library documentation
> 
> To access further information about this package, please visit the
> following URL:
> 
>   https://mentors.debian.net/package/sofia-sip/
> 
> Alternatively, one can download the package with dget using this
> command:
> 
>   dget -x
> https://mentors.debian.net/debian/pool/main/s/sofia-sip/sofia-sip_1.12.11+20110422.1-2.2.dsc
> 
> I have uploaded the package on salsa under 
> https://salsa.debian.org/devrtz/sofia-sip/-/tree/minimal-nmu
> Judging by debdiff (as mentioned in #965829) there is basically only
> some 
> changes in the -doc package which I believe are due to a newer
> doxygen being used.
> 
> I've also tested with one rdep (gnome-calls of which I'm the
> maintainer) that
> it still builds and runs fine.
> 
> Changes since the last upload:
> 
>  sofia-sip (1.12.11+20110422.1-2.2) unstable; urgency=medium
>  .
>    * Non-maintainer upload.
>    * Bump dh-compat to 13 (Closes: #965829)
> 
> Regards,

Bug#1003853: RFS: sofia-sip/1.12.11+20110422.1-2.2 [NMU] [RC] -- Sofia SIP library

[Evangelos Ribeiro Tzaras]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "sofia-sip":

 * Package name: sofia-sip
   Version : 1.12.11+20110422.1-2.2
   Upstream Author : Pekka Pessi, Martti Mela, Kai Vehmanen
 * URL : http://sofia-sip.sourceforge.net/
 * License : LGPL-2.1
 * Vcs : http://git.debian.org/?p=users/ron/sofia-sip.git;a=summary
   Section : net

It builds those binary packages:

  sofia-sip-bin - Sofia-SIP library utilities
  libsofia-sip-ua0 - Sofia-SIP library runtime
  libsofia-sip-ua-dev - Sofia-SIP library development files
  libsofia-sip-ua-glib3 - Sofia-SIP library glib/gobject interfaces runtime
  libsofia-sip-ua-glib-dev - Sofia-SIP library glib/gobject interface 
development files
  sofia-sip-doc - Sofia-SIP library documentation

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/sofia-sip/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/s/sofia-sip/sofia-sip_1.12.11+20110422.1-2.2.dsc

I have uploaded the package on salsa under 
https://salsa.debian.org/devrtz/sofia-sip/-/tree/minimal-nmu
Judging by debdiff (as mentioned in #965829) there is basically only some 
changes in the -doc package which I believe are due to a newer doxygen being 
used.

I've also tested with one rdep (gnome-calls of which I'm the maintainer) that
it still builds and runs fine.

Changes since the last upload:

 sofia-sip (1.12.11+20110422.1-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump dh-compat to 13 (Closes: #965829)

Regards,
-- 
  Evangelos Ribeiro Tzaras

Bug#965829:

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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#1003476: [Debian-on-mobile-maintainers] Bug#1003476: libomemo cross misbuilds

[Evangelos Ribeiro Tzaras]

Hi,

On Mon, 2022-01-10 at 21:01 +0100, Helmut Grohne wrote:
> Source: libomemo
> Version: 0.7.0-1
> Tags: patch
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
> 
> When cross building libomemo it uses the build architecture multiarch
> dir, but it should be using the host architecture one.

This confused me for a moment (in fact I wondered if it shouldn't be
the other way around), because I naively misunderstood the meaning of
"build" (as in the architecture for which to build) and "host" (as in
the host I'm building on), but after looking it up [1] it makes a lot
more sense ;)

>  It's because it
> derives it from gcc -print-multiarch. In order to fix that one needs
> to
> use $(CC) and pass CC to make install. Please consider applying the
> attached patch.

Thanks a lot for providing a patch!

Out of curiosity: That patch works because in a cross compilation CC
will f.e. be aarch64-linux-gnu-gcc because that is set via the included
/usr/share/dpkg/buildtools.mk, right?

Initially I contemplated including /usr/share/dpkg/architecture.mk and
somehow using DEB_TARGET_GNU_TYPE, but your patch seems much cleaner,
so thanks a lot!

Since this actually issue came up [2] some time ago upstream and the 
$(CC) bit could go there, do you want to submit this part of the patch
or should I do this (preserving your authorship of course!)?

[1] http://gcc.gnu.org/onlinedocs/gccint/Configure-Terms.html
[2] https://github.com/gkdr/libomemo/issues/6#issuecomment-849190527

Cheers,
-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#965829:

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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 mode 100644
i

Bug#996699: [Debian-on-mobile-maintainers] Bug#996699: Bug#996699: chatty: Cross-building fails to resolve libpurple-dev

[Evangelos Ribeiro Tzaras]

Hi,

On Wed, 2021-10-20 at 14:59 +0200, Helmut Grohne wrote:
> 
> On Wed, Oct 20, 2021 at 10:17:30AM +0200, Evangelos Ribeiro Tzaras
> wrote:
> > On Sun, 2021-10-17 at 09:26 -0400, Travis Wrightsman via Debian-on-
> > mobile-maintainers wrote:
> > > Package: chatty
> > > Version: 0.4.0-1
> > > Severity: serious
> > > Justification: fails to build from source
> > > Tags: ftbfs upstream
> 
> We do not yet categorize cross build issues as ftbfs. In any case,
> cross
> build issues are not release critical as Sebastian Ramacher pointed
> out.
> Please refrain from filing cross build bugs without patches.
> 

Good to know!

> > 
> 
> > CCing debian-cross in the hopes that someone can shed some light
> > here
> > :)
> 
> Very good. That was the right thing to do.

That is always nice to hear, isn't it? :)


> As a general thing, if you want to look into why something doesn't
> cross
> build, go check at our cross build quality assurance:
> http://crossqa.debian.net/src/chatty
> 

Mentally noted!

> We learn a couple of things there:
>  * chatty doesn't have satisfiable cross-Build-Depends for any
>    architecture and consequently has never been built.
>  * There are no linked bug reports (at the time of this writing, but
> the
>    usertagging should make this bug show up there soon).
>  * The dependency issue is with libpurple-dev (as you correctly
>    identified).
> 
> crossqa uses dose to check dependency issues, so it can only see one
> of
> many problems and the first issues it happens to see is with
> libpurple-dev. To see the others, we check the bootstrap.d.n link:
> https://bootstrap.debian.net/cross_all/chatty.html
> 
> Good news: It's libpurple-dev and libpurple-dev only.
> 
> Time to look into libpurple-dev, right?
> 
> It's an Architecture: all package and those can never satisfy cross
> Build-Depends unless marked Multi-Arch: foreign. So clear thing, we
> mark
> it Multi-Arch: foreign and we're done, right? Unfortunately, not.
> libpurple-dev Depends on libpurple0 (among other things) and quite
> clearly, it exposes libpurple0. Since libpurple0 is
> architecture-dependent and exposed by libpurple-dev, libpurple-dev
> cannot be Multi-Arch: foreign. The thing is: When we issue a
> dependency
> on libpurple-dev (for a particular architecture), we want a matching
> libpurple0 (of the requested architecture). And this constraint
> cannot
> be transferred through Architecture: all packages. That issue is
> known
> as the "multiarch interpreter problem", because it happened with
> interpreters first. In any case, the canonical solution to this
> problem
> is to turn libpurple-dev Architecture: any. At that point the
> resolver
> will pick the host architecture libpurple-dev and the dependency will
> ensure that we also get the host architecture libpurple0.
> 
> If this leaves any questions, don't hesitate to ask
> (debian-cr...@lists.debian.org).

Thanks a lot for taking the time to explain this and providing a patch!


--
Evangelos


signature.asc
Description: This is a digitally signed message part

Bug#996699: [Debian-on-mobile-maintainers] Bug#996699: chatty: Cross-building fails to resolve libpurple-dev

[Evangelos Ribeiro Tzaras]

Hi and thanks for your report!

On Sun, 2021-10-17 at 09:26 -0400, Travis Wrightsman via Debian-on-
mobile-maintainers wrote:
> Package: chatty
> Version: 0.4.0-1
> Severity: serious
> Justification: fails to build from source
> Tags: ftbfs upstream
> 
> Chatty fails to cross-build due to a dependency resolution error for
> the
> libpurple-dev package.
> 
> I'm not sure this is a chatty-specific bug but I'm also not sure where
> else to place it.

I've just checked with another package which uses libpurple-dev (f.e.
purple-matrix)  and ran (perhaps unsurprisingly) into the same issue
when crossbuilding.
CCing the pidgin maintainer.


> 
> It occurs on Debian Salsa builds:
> https://salsa.debian.org/DebianOnMobile-team/chatty/-/jobs/1940649#L1475

Possibly (probably?) related crossbuild failure in pidgin:
https://salsa.debian.org/debian/pidgin/-/jobs/2035973#L1446 

 pidgin-cross-build-deps:arm64 : Depends: libxml-parser-perl:arm64 but
it is not installable
 Depends: python3:arm64 but it is not
going to be installed
Unable to resolve dependencies!  Giving up...


I've also looked at libxml-parser-perl which fails both locally with
the pbuilder invocation from below and in CI.
https://salsa.debian.org/devrtz/libxml-parser-perl/-/jobs/2100268#L1425

The following packages have unmet dependencies:
 builddeps:/build/libxml-parser-perl_2.46-2.dsc:arm64 : Depends:
libdevel-checklib-perl:arm64 but it is not installable


I've not (yet) dived any deeper than this.

> 
> It also occurs when using git-buildpackage to cross-build for my
> (arm64)
> PinePhone from my (amd64) laptop.
> 
> $ BUILDER=pbuilder DIST=bookworm git-pbuilder create
> $ echo 'PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-
> satisfydepends-apt"' > ~/.pbuilderrc
> $ BUILDER=pbuilder gbp buildpackage --git-pbuilder --git-pbuilder-
> options="--host-arch arm64" --git-dist=bookworm
> [...]
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  builddeps:/build/chatty_0.4.0-1.dsc:arm64 : Depends: libpurple-
> dev:arm64 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> E: pbuilder-satisfydepends failed.
> [...]
> 

I can reproduce this, but I don't really understand why this happens as
I'm not intimately familiar with all the intricacies of crossbuilding
because I usually "cross"build in natively in an arm64 qemu chroot.

CCing debian-cross in the hopes that someone can shed some light here
:)

More generally: What should be the next steps?

I guess I could reassign this bug to the pidgin source package (as it
provides libpurple-dev)?
And open bugs to
a) libxml-parser-perl
b) libdevel-checklib-perl
c) python3 (and/or all the packages that make python FTCBFS)

> Chatty builds successfully on the PinePhone using git-buildpackage.
> 
> 

--
Cheers,
Evangelos

Bug#995267: Re: Bug#995267: devhelp doesn't load the selected content

[Evangelos Ribeiro Tzaras]

Hi,

On Sat, 02 Oct 2021 23:46:10 +0300 =?UTF-8?B?UmluYXQgSWJyYWdpbW92?=
 wrote:
> Looks like it's sufficient to remove
~/.local/share/mime/application/x-extension-html.xml
> and then to regenerate database:
> 
> update-mime-database ~/.local/share/mime
> 

On my system I still had some 'user-extension-*htm*.xml' files in
~/.local/share/mime/packages and updating the database would regenerate
the files under ~/.local/share/mime/applications.

After removing *those* as well and regenerating the database it started
working again.


-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19





signature.asc
Description: This is a digitally signed message part

Bug#995436: [Debian-on-mobile-maintainers] Bug#995436: confy: new upstream 0.6.1

[Evangelos Ribeiro Tzaras]

Hi,

On Fri, 2021-10-01 at 02:08 -0700, Vagrant Cascadian wrote:
> Package: confy
> Version: 0.6.0-1
> Severity: minor
> 
> There is a new upstream version.
> 
> It is really helpful with virtual conferrences in a different
> timezone.
> 

Glad you find it useful!

> It looks like confy.git on salsa has the new upstream version, and
> building it just required removing the one patch in debian/patches
> and
> updating debian/changelog, so it seems almost ready to build and
> upload to unstable.

It should get uploaded soon, thanks for the offer though!

> 
> Happy to help and/or sponsor an upload, if needed.
> 
> Thanks for maintaining confy!
> 
> live well,
>   vagrant
> 
> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#993714: conffile which got removed during upgrade reported missing

[Evangelos Ribeiro Tzaras]

Package: debsums
Version: 3.0.2
Severity: normal

Dear Maintainer,

I'm trying to upgrade the gnome-calls package where the a .desktop file changed 
and got renamed

from /etc/xdg/autostart/sm.puri.Calls-daemon.desktop 
to /etc/xdg/autostart/org.gnome.Calls-daemon.desktop

In my debian/gnome-calls.maintscript I've put

rm_conffile /etc/xdg/autostart/sm.puri.Calls-daemon.desktop 41~alpha-1~

and I've made sure that it indeed removes the old file when upgrading
from the latest version (0.2.0-2):


$ sudo dpkg -i ../gnome-calls_41\~rc-1_amd64.deb
(Reading database ... 437749 files and directories currently
installed.)
Preparing to unpack .../gnome-calls_41~rc-1_amd64.deb ...
Unpacking gnome-calls (41~rc-1) over (0.2.0-2) ...
Setting up gnome-calls (41~rc-1) ...
Removing obsolete conffile /etc/xdg/autostart/sm.puri.Calls-
daemon.desktop ...
Processing triggers for mailcap (3.70) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for libglib2.0-0:i386 (2.68.4-1) ...
Processing triggers for libglib2.0-0:amd64 (2.68.4-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.9.4-2) ...


Salsa CI had a failing piuparts job [1]:


1m37.0s DUMP: 
   debsums: missing file 
/tmp/tmpqxks8a8q/etc/xdg/autostart/sm.puri.Calls-daemon.desktop (from 
gnome-calls package)
   1m37.0s DEBUG: Command failed (status=2), but ignoring error: ['debsums', 
'--root', '/tmp/tmpqxks8a8q', '-ac', '--ignore-obsolete']
   1m37.0s ERROR: FAIL: debsums reports modifications inside the chroot:
 debsums: missing file /etc/xdg/autostart/sm.puri.Calls-daemon.desktop 
(from gnome-calls package)


which is very weird to me, since it's _supposed_ to not be there.
See a couple of lines above:

Removing obsolete conffile /etc/xdg/autostart/sm.puri.Calls-daemon.desktop ...


Now I'm not familiar with debsums but since that seems to be at the
heart of the failing piuparts job I've tested the following:

$ debsums -e gnome-calls  
debsums: missing file /etc/xdg/autostart/sm.puri.Calls-daemon.desktop (from 
gnome-calls package)
/etc/xdg/autostart/org.gnome.Calls-daemon.desktop OK

Is this behaviour expected? Could it be that the new `remove-on-upgrade`
feature added to dpkg in 1.20.9 is not (yet) understood by debsums?

Thanks,
Evangelos

[1] https://salsa.debian.org/devrtz/gnome-calls/-/jobs/1904855

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debsums depends on:
ii  libdpkg-perl  1.20.9
ii  libfile-fnmatch-perl  0.02-2+b8
ii  perl  5.32.1-5
ii  ucf   3.0043

debsums recommends no packages.

Versions of packages debsums suggests:
ii  bash-completion  1:2.11-3

-- no debconf information

Bug#990006: libolm3: Possibly clashing symbols

[Evangelos Ribeiro Tzaras]

Package: libolm3
Version: 3.2.1~dfsg-7
Severity: normal

Dear Maintainer,

there is an issue [1] with private symbols being exported which can
lead to
symbols conflicting with other libraries or applications.
There is a fix available upstream [2] and on salsa [3].

We've run into this issue with chatty[4], which leads to segmentation
faults.
Since the affected chatty version has not made it into bullseye and
no other user of libolm{3,-dev} seems to have run into this problem
I guess "normal" priority is appropriate (?)

[1] https://github.com/matrix-org/olm/issues/47
[2]
https://gitlab.matrix.org/matrix-org/olm/-/commit/1b7973626e27beb05a55df6085f643a1323db987
[3] https://salsa.debian.org/matrix-team/olm/-/merge_requests/1
[4] https://source.puri.sm/Librem5/chatty/-/issues/450

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500,
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-7-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libolm3 depends on:
ii  libc6   2.31-12
ii  libstdc++6  10.2.1-6

libolm3 recommends no packages.

libolm3 suggests no packages.

-- no debconf information

-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#985940: appstream-glib: fails to validate appdata starting with non-ascii characters

[Evangelos Ribeiro Tzaras]

Source: appstream-glib
Severity: normal

Dear Maintainer,

while running reprotest on salsa CI my package chatty [0]
failed to build during the locale variation with the russian locale [1].

It has been pointed out to me that non-ascii characters are not
handled correctly when it comes to checking for sentence case.
The offending code was identified here [2].

[0] https://salsa.debian.org/DebianOnMobile-team/chatty
[1] https://salsa.debian.org/DebianOnMobile-team/chatty/-/jobs/1536009#L2992[2] 
https://sources.debian.org/src/appstream-glib/0.7.18-1/libappstream-glib/as-app-validate.c/?hl=203#L135

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.10.0-4-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#982250: [Debian-on-mobile-maintainers] Upstream Efforts

[Evangelos Ribeiro Tzaras]

Hi Christopher,

I've not really looked in depth into your packaging, but I have two 
comments.


On 3/23/21 1:50 AM, Christopher Talbot wrote:

Hello,

Per this discussion, I created Debian packaging for upstream mmsd:
https://source.puri.sm/kop316/mmsd/-/tree/debian/latest



This should probably live on salsa.debian.org


Commit f4b8b32477a411180be1823fdc460b4f7e1e3c9c (the commit before
adding the Debian Packaging) is in sync with
https://git.kernel.org/pub/scm/network/ofono/mmsd.git (upstream)

There is only one patch, and it removes a compiler flag (-WError).
It is required to allow mmsd to compile.



Instead of removing -WError I think it would be better to see where the 
warning comes from and fix that :)


--
Cheers,
Evangelos

Bug#982696: [PATCH] drm-info: FTBFS: tables.c:247:2: error: duplicate case value

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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#982250: TAG: mmsd-mm -- mmsd is a lower level daemon that transmits and recieves MMSes. It works with both the ofono stack and the Modem Manager stack. This packaging only works with modem manager

[Evangelos Ribeiro Tzaras]

Hi Christopher,


Package: wnpp
Severity: ITP

mmsd-mm mmsd is a lower level daemon that transmits and recieves
Multimedia Service Messages. It works with both the ofono stack and the
Modem Manager stack. This packaging only works with modem manager.

The original upstream is here: 
https://git.kernel.org/pub/scm/network/ofono/mmsd.git


and my package is maintained here:

https://source.puri.sm/kop316/mmsd/

The "Master" Branch is the same as the upstream branch:
https://source.puri.sm/kop316/mmsd/-/tree/master

and all of my patches are maintained in the "ModemManager" branch:
https://source.puri.sm/kop316/mmsd/-/tree/ModemManager

The Debian packaging is here:
https://source.puri.sm/kop316/mmsd/-/tree/debian/modemmanager/latest

To the submitter's knowledge, no other package exists that does this,
and MMSD is not packaged for Debian. In addition, to the submitter's
knowledge, no stack exists in Modem Manager that supports MMS.

As of now, the submitter has been working primarily alone, but has had
the support of both the Mobian community and the Purism Community. The
Submitter will welcome co-maintainers, especially for the Ofono side of
the packaging/testing.


I think this would be a good candidate for maintaining as a part of the 
DebianOnMobile-team [0].



[0] https://salsa.debian.org/DebianOnMobile-team


--
Cheers,
Evangelos

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

[Evangelos Ribeiro Tzaras]

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

[Evangelos Ribeiro Tzaras]

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 

Bug#978420: ITP: confy -- Conference schedule viewer written in Python.

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: confy
  Version : 0.4.1
  Upstream Author : fabrixxm 
* URL : https://confy.kirgroup.net/
* License : GPL3
  Programming Lang: Python
  Description : Conference schedule viewer written in Python.

Navigate conference schedules, mark favourite talks 
and get reminded when talks are coming up.
Works offline after initial data download and is usable
on mobile devices.

Bug#964087: RFS: TomboyReborn/1.0-1 - Drop in replacement of deprecated Gnome Tomboy

[Evangelos Ribeiro Tzaras]

Hi,

I originally got started with [1], however you should probably consult the new
version [2]. This should hopefully help you figure things out.

[1] https://www.debian.org/doc/manuals/maint-guide/index.html
[2] https://www.debian.org/doc/devel-manuals#debmake-doc

On 7/1/20 9:20 PM, Joan Moreau wrote:
> Hi
> 
> I am really sorry to bother you, but I am a bit lost.
> 
> I created a .deb file (see
> https://github.com/grosjo/tomboy-reborn/tree/master/packages ) so I should now
> create a deb-src package, right ?
> 
> The wiki page you mentioned does not really explain how to do so. Is there a
> simple, step-by-step, process described somewhere ?
> 
> THank you so much
> 
> 
>  
> 
> 
> On 2020-07-01 18:46, Andrey Rahmatullin wrote:
> 
>> On Wed, Jul 01, 2020 at 05:35:21PM +0100, Joan Moreau wrote:
>>> This is not a "source package" as the source is in Pascal (using Lazarus
>>> compiler package). Should I include the Pascal source also ?
>> You need to create a Debian source package that can be built to produce a
>> Debian binary package.
>> It doesn't really matter what language is used or what should be contained
>> in the binary package. The workflow is the same.
>> https://wiki.debian.org/Packaging/SourcePackage

---

Evangelos Ribeiro Tzaras

Bug#963802: ITP: drm-info -- Small utility to dump info about DRM devices

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 

* Package name: drm-info
  Version : 2.2.0
  Upstream Author : Scott Anderson 
* URL : https://github.com/ascent12/drm_info
* License : MIT
  Programming Lang: C
  Description : Small utility to dump info about DRM devices

drm_info dumps information about drm devices such as available devices,
planes, encoders, crtcs and connectors and their DRM properties.

Related RFP: #962861
After completing the packaging I will reach out to X Strike Force
packaging team or the swaywm team for team maintainership.

Bug#962861: RFP: drm-info -- Small utility to dump info about DRM devices

[Evangelos Ribeiro Tzaras]

On Tue, 16 Jun 2020 16:42:14 +0100 Sudip Mukherjee
 wrote:
> On Mon, Jun 15, 2020 at 09:35:56AM +0200, Guido Günther wrote:
> > Package: wnpp
> > Severity: wishlist
> >
> 
> >
> > drm_info dumps information about available drm device like available
> > devices, planes, encoders, crtcs and connectors and their DRM
> > properties.
>
> This looks like an useful utility and I did an initial packaging. But
> while testing I get a segfault after printing all the information.
>
> $ drm_info
> Node: /dev/dri/card0
> ├───Driver: bochs-drm (bochs dispi vga interface (qemu stdvga))
version 1.0.0 (20130925)
> │ ├───DRM_CLIENT_CAP_STEREO_3D supported
> │ ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
> │ ├───DRM_CLIENT_CAP_ATOMIC supported
> │ ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
> │ ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
> │ ├───DRM_CAP_DUMB_BUFFER = 1
> │ ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
> │ ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 24
> │ ├───DRM_CAP_DUMB_PREFER_SHADOW = 0
> │ ├───DRM_CAP_PRIME = 0
> │ ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
> │ ├───DRM_CAP_ASYNC_PAGE_FLIP = 0
> │ ├───DRM_CAP_CURSOR_WIDTH = 64
> │ ├───DRM_CAP_CURSOR_HEIGHT = 64
> │ ├───DRM_CAP_ADDFB2_MODIFIERS = 0
> │ ├───DRM_CAP_PAGE_FLIP_TARGET = 0
> │ ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
> │ ├───DRM_CAP_SYNCOBJ = 0
> │ └───DRM_CAP_SYNCOBJ_TIMELINE = 0
> Segmentation fault
>

Did you get it running yet? I could build and run it on a few different
systems with just plain meson/ninja without any problems.> I also tried
with "drm_info -j" and that works pergectly without any error.
I would also be interested in packaging this but don't want to have
duplicated work.
If you intent to package it, could you open a ITP?
> I also tried with "drm_info -j" and that works pergectly without any
error.

>
> Note: I have used Debian packages of json-c, libdrm and libpci. It will
> be good to have a manpage along with the fix for segfault.
>
> --
> Regards
> Sudip
>
>

-- 
Regards
Evangelos Ribeiro Tzaras

Bug#951118: Current status

[Evangelos Ribeiro Tzaras]

Hello Olivier,

i wanted to ask how the packaging is coming along.
I had previously written you an email and CC'ed the DebianOnMobile
maintainers mailinglist, but have not yet received an answer, so I
thought it would give it a try on this more public channel.

The DebianOnMobile team has prepared packaging of the dependencies
(axc[1], and libomemo[2]) and has also done some packaging of our own on
lurch [3].
libomemo has not yet been uploaded to ftp masters because of a possible
bug which still needs investigating.

We are interested in purple-lurch because it would enable encrypted
messaging in our libpurple client chatty [4].

I look forward to your reply

[1] https://salsa.debian.org/DebianOnMobile-team/libaxc
[2] https://salsa.debian.org/DebianOnMobile-team/libomemo
[3] https://salsa.debian.org/DebianOnMobile-team/purple-lurch
[4] https://salsa.debian.org/DebianOnMobile-team/chatty

Bug#960486: ITP: gnome-chatty -- XMPP and SMS messaging

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 

* Package name: gnome-chatty
  Version : 0.0.8
  Upstream Author : Mohammed Sadiq 
* URL : https://source.puri.sm/Librem5/chatty
* License : GPL-3+
  Programming Lang: C
  Description : XMPP and SMS messaging

A libpurple messaging client for XMPP and SMS messaging using
ModemManager.

This is a useful package for use on mobile devices (Pinephone, Librem5).
I plan to maintain it as part of the Debian On Mobile team.

Bug#960228: ITP: calls -- A phone dialer and call handler

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 

* Package name: calls
  Version : 0.1.4
  Upstream Author : Guido Günther 
* URL : https://source.puri.sm/Librem5/calls
* License : GPLv3, X11
  Programming Lang: C
  Description : A phone dialer and call handler for mobile devices

A dialer program for telephony calls on mobile devices 
supporting multiple backends (ModemManager, oFono, Phonesim).

This package is useful for running debian on mobile phones
providing call functionality. It is commonly used in phosh.

I would like to maintain in a packaging team, namely Debian On Mobile
I am also looking for a sponsor.

Bug#960025: ITP: python3-pyzbar -- Reads one dimensional barcodes and QR codes in python using libzbar

[Evangelos Ribeiro Tzaras]

Package: wnpp
Severity: wishlist
Owner: Evangelos Ribeiro Tzaras 

* Package name: python3-pyzbar
  Version : 0.1.8
  Upstream Author : Lawrence Hudson 
* URL : https://github.com/NaturalHistoryMuseum/pyzbar/
* License : MIT
  Programming Lang: Python
  Description : Reads one dimensional barcodes and QR codes in python using 
libzbar

It is a pure python package that works with PIL / Pillow images, 
OpenCV / numpy arrays and raw bytes. 

I have noticed there is python3-zbar available already, but I do not
know how these two packages compare, since I am using it as a dependency
and therefore do not have the choice of switching to python3-zbar.

I have already packaged pyzbar for a downstream project called Mobian
and wish to have it packaged for debian itself.

This python module is a dependency for the authenticator app (see
ITP #958555). I plan maintaining it through the python modules team.
I do need a sponsor.