Processed: not a bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 963495
Bug #963495 [selinux-policy-default] selinux-policy-default: reportbug 
Segmentation faulted when Selinux is in Enforcing mode
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: not a bug for that version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 963497
Bug #963497 [selinux-policy-default] selinux-policy-default: Let's Encrypt 
certbot tools crashed into Segmentation fault with SELinux Enforcing mode
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 976211

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 976211 9.4.35-1
Bug #976211 [src:jetty9] jetty9: CVE-2020-27218
Marked as fixed in versions jetty9/9.4.35-1.
Bug #976211 [src:jetty9] jetty9: CVE-2020-27218
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
976211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#976211: closing 976211

[Salvatore Bonaccorso]

close 976211 9.4.35-1
thanks

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Chirayu Desai]

>From a quick check it looks the asm for ARM is present, it's just put
directly in the header
x86/mips (and their 64-bit variants) have AsmGetRegs*.S
arm and aarch64 has it in the header file,
see:
https://android.googlesource.com/platform/system/core/+/refs/tags/android-10.0.0_r1/libunwindstack/include/unwindstack/RegsGetLocal.h


On Thu, Dec 31, 2020 at 5:19 AM Hans-Christoph Steiner  wrote:

> also, it looks like libunwindstack uses asm and there isn't any for ARM.
>   So if someone wants to keep the arm packages, they'll need to figure
> that out.  I have zero asm skills.
>

Processed: Re: pipemeter FTBFS: error: format not a string literal and no format arguments

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #972958 [src:pipemeter] pipemeter FTBFS: error: format not a string literal 
and no format arguments
Added tag(s) patch.

-- 
972958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972958: pipemeter FTBFS: error: format not a string literal and no format arguments

[Logan Rosen]

Package: pipemeter
Version: 1.1.4-1
Followup-For: Bug #972958
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/format-security-error.patch: Fix format-security error by using fputs
instead of fprintf.
  * d/p/fix-make-install.patch: Fix issues with make install by using DESTDIR
and adjusting install arguments.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 
'groovy'), (100, 'groovy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-33-generic (SMP w/8 CPU threads)
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
diff -Nru pipemeter-1.1.4/debian/patches/fix-make-install.patch 
pipemeter-1.1.4/debian/patches/fix-make-install.patch
--- pipemeter-1.1.4/debian/patches/fix-make-install.patch   1969-12-31 
19:00:00.0 -0500
+++ pipemeter-1.1.4/debian/patches/fix-make-install.patch   2020-12-31 
00:13:00.0 -0500
@@ -0,0 +1,13 @@
+--- a/Makefile.in
 b/Makefile.in
+@@ -24,8 +24,8 @@
+   
+ 
+ install: pipemeter pipemeter.1
+-  install -p pipemeter $(PREFIX)/bin
+-  install -p pipemeter.1 $(PREFIX)/man/man1
++  install -Dp -t $(DESTDIR)$(PREFIX)/bin pipemeter
++  install -Dp -t $(DESTDIR)$(PREFIX)/man/man1 pipemeter.1
+ 
+ dist: pipemeter
+   sh pkgpipemeter.sh
diff -Nru pipemeter-1.1.4/debian/patches/format-security-error.patch 
pipemeter-1.1.4/debian/patches/format-security-error.patch
--- pipemeter-1.1.4/debian/patches/format-security-error.patch  1969-12-31 
19:00:00.0 -0500
+++ pipemeter-1.1.4/debian/patches/format-security-error.patch  2020-12-31 
00:12:44.0 -0500
@@ -0,0 +1,29 @@
+--- a/pipemeter.c
 b/pipemeter.c
+@@ -397,7 +397,7 @@
+ fprintf(stderr,"\n");
+ exit(1);
+   } else {
+-fprintf(stderr,trailer);
++fputs(trailer,stderr);
+   }
+ }
+  
+@@ -487,7 +487,7 @@
+   }
+ 
+   strncpy(progressbar+1,progressfill,progress);
+-  fprintf(stderr, progressbar);
++  fputs(progressbar,stderr);
+   fprintf(stderr," %s/s",buf2);
+   formatbytes(buf2,bytes);
+   fprintf(stderr," %s",buf2);
+@@ -497,7 +497,7 @@
+ fprintf(stderr,"\n");
+ exit(0);
+   } else {
+-fprintf(stderr,trailer);
++fputs(trailer,stderr);
+   }
+ }
+ 
diff -Nru pipemeter-1.1.4/debian/patches/series 
pipemeter-1.1.4/debian/patches/series
--- pipemeter-1.1.4/debian/patches/series   1969-12-31 19:00:00.0 
-0500
+++ pipemeter-1.1.4/debian/patches/series   2020-12-31 00:13:00.0 
-0500
@@ -0,0 +1,2 @@
+format-security-error.patch
+fix-make-install.patch

Bug#957127: marked as done (ddccontrol: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 05:18:21 +
with message-id 
and subject line Bug#957127: fixed in ddccontrol 0.4.4-1.1
has caused the Debian Bug report #957127,
regarding ddccontrol: ftbfs with GCC-10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
957127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ddccontrol
Version: 0.4.4-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ddccontrol_0.4.4-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from main.c:22:
/usr/include/glib-2.0/glib/deprecated/gthread.h:261:10: note: declared here
  261 | void g_thread_init   (gpointer vtable);
  |  ^
main.c:406:2: warning: ‘g_mutex_new’ is deprecated [-Wdeprecated-declarations]
  406 |  combo_change_mutex = g_mutex_new();
  |  ^~
In file included from /usr/include/glib-2.0/glib.h:110,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from main.c:22:
/usr/include/glib-2.0/glib/deprecated/gthread.h:273:17: note: declared here
  273 | GMutex *g_mutex_new (void);
  | ^~~
LC_ALL=C /usr/bin/intltool-merge  -d -u -c ../../po/.intltool-merge-cache 
../../po gddccontrol.desktop.in gddccontrol.desktop
Generating and caching the translation database
NOTICE: ../../po/fr.po is not in UTF-8 but ISO-8859-1, converting...
NOTICE: ../../po/pl.po is not in UTF-8 but ISO-8859-2, converting...
Merging translations into gddccontrol.desktop.
/bin/bash ../../libtool  --tag=CC   --mode=link gcc -I/usr/include/libxml2 
-pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall  -DDATADIR="\"/usr/share/ddccontrol-db\"" 
-DBINDIR="\"/usr/bin\"" -lxml2 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 
-latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 
-lgobject-2.0 -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -lm 
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o gddccontrol main.o noteboo
 k.o gprofile.o fspatterns.o ../lib/libddccontrol.la -lpci -lm
libtool: link: gcc -I/usr/include/libxml2 -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Bas Couwenberg]

Package: chardet
Version: 4.0.0-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:requests src:qgis

Dear Maintainer,

Upgrading python3-chardet causes the removal of many packages:

 The following packages will be REMOVED:
   chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
python3-qgis
   python3-reportbug python3-requests python3-requests-oauthlib 
python3-s3transfer python3-sphinx python3-sphinx-astropy 
python3-sphinx-automodapi python3-sphinx-gallery pywps qgis qgis-plugin-grass 
reportbug system-config-printer
   system-config-printer-common system-config-printer-udev torbrowser-launcher
 The following packages will be upgraded:
   python3-chardet
 1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.

python3-requests does not support version 3.1.0 or higher:

  python3-chardet (<< 3.1.0)

With the freeze coming in a few months it may be wise to revert back to 3.0.x 
for bullseye.

Otherwise the python3-chardet rdeps need to fixed before that time.

Kind Regards,

Bas

Processed: chardet: Upgrading python3-chardet breaks many packages

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:requests src:qgis
Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages
Added indication that 978739 affects src:requests and src:qgis

-- 
978739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978437: marked as done (geoclue-2.0: regression in 2.5.7-1, no geolocation returned)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 04:33:51 +
with message-id 
and subject line Bug#978437: fixed in geoclue-2.0 2.5.7-2
has caused the Debian Bug report #978437,
regarding geoclue-2.0: regression in 2.5.7-1, no geolocation returned
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: geoclue-2.0
Version: 2.5.7-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After the upgrade from 2.5.6-1 to 2.5.7-1 geoclue2 doesn't give me
any geolocation information anymore. I first noticed this with
redshift, but I can reproduce it with pure src:geoclue-2.0.

Situation (with 2.5.6-1):

* /etc/geoclue/geoclue.conf unmodified (except for a redshift stanza
  at the bottom)
* No desktop enviroment or other fancy things.
* I start /usr/libexec/geoclue-2.0/demos/agent as my user, which then
  (or later when a client comes around?) starts /usr/libexec/geoclue
  (as user geoclue)

Here everything works:

% /usr/libexec/geoclue-2.0/demos/where-am-i
Client object: /org/freedesktop/GeoClue2/Client/2

New location:
Latitude:…
Longitude:   …
Accuracy:1000.00 meters
Timestamp:   Sun Dec 27 14:19:54 2020 (1609075194 seconds since the Epoch)
  
Good.


After updating to 2.5.7-1:

* Accept new /etc/geoclue/geoclue.conf.
* Kill /usr/libexec/geoclue-2.0/demos/agent and /usr/libexec/geoclue.
* Start /usr/libexec/geoclue-2.0/demos/agent again.
* Call /usr/libexec/geoclue-2.0/demos/where-am-i

Result: nothing, i.e. it times out after the default 30 seconds.
(redshift at this point just hangs with "Waiting for current location to become
available...")

/usr/libexec/geoclue is again running as user geoclue.


And that's it. So "something" (with system apps? or accuracy level?
or something else?) changed which breaks how at least for me geoclue
has worked for a couple of years.


Cheers,
gregor


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages geoclue-2.0 depends on:
ii  adduser 3.118
ii  libavahi-client30.8-3
ii  libavahi-common30.8-3
ii  libavahi-glib1  0.8-3
ii  libc6   2.31-6
ii  libglib2.0-02.66.4-1
ii  libjson-glib-1.0-0  1.6.0-2
ii  libmm-glib0 1.14.8-0.1
ii  libnotify4  0.7.9-2
ii  libsoup2.4-12.72.0-2

Versions of packages geoclue-2.0 recommends:
pn  avahi-daemon  
pn  iio-sensor-proxy  
pn  modemmanager  
ii  wpasupplicant 2:2.9.0-16

geoclue-2.0 suggests no packages.

- -- Configuration Files:
/etc/geoclue/geoclue.conf changed [not included]

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl/oj65fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgahlQ/+PPQ8nTbnf4q02+o4U3NDnZz2HFGFqs0LAlJDJ6qUwk/Tt1sX36ex58Y0
mV3EfEA5pjrRRoQhm9uwerBrOOy0XYCwNhs4aok1hyAeSyE3Vym+6LAUOwzUsTdX
BYe76jgnAIagQUf0Ph9yg7IsDhNZvPQsrJjHTm7NBVbjF0uUEezMeDuevE1Qn0mY
G1NyGraJqHSHDXIFzuAIEZVAvkVp7PgfGeZeM2jSAQDzS5j7Y1BgKPzod3dVug3z
ngsEo0NP5bQclE/upM+Ykwa4tPzwtfqLLx6t33MKVH7Tr++rGSvvSx7gwXvLydyE
dHmdYb0s5JN28W9bv+JB+/zwYHTrj06vxOjfGSGFx/58Eyun2H/ewHjxrjlUnVWu
xF1oIzaw7wVCrwaPNHwFIpcEcmTfAy2ZrDxWUI7pzZePVy/iH08USFHwSSu7LSDV
srkXwO8jAjk38GgaD+Dhk0nWj4jz9XqaTMXG+WQvihmzWFM6zXYsItLYZrlezsmI
4IwnZ4U14vs3mgaJYn/1SDxGr0YYAj2pFaWz8WjYC/a4mHbje//D78JDMM9rThrr
gsHDH6RRRydzo+iiSnP91uMZJuBKbMbQOrPmcBFx4/yiqx+rf9m0BF83GyDanWR/
TO9TiopczPGhfkDSAcFvdg6uHc0WHsnEGwNSz2UI2T7cUGXpCg4=
=JYf1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: geoclue-2.0
Source-Version: 2.5.7-2
Done: Laurent Bigonville 

We believe that the bug you reported is fixed in the latest version of
geoclue-2.0, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them 

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

[James McCoy]

On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote:
> The OpenSSL devs intended this to be a breaking change - but it's not
> documented anywhere.  Sigh.
> 
> I've got a WIP patch against trunk that causes test_ssl to pass - see below. 
> It also seems to work with OpenSSL 1.1.1h as well as OpenSSL 1.1.1i /
> 1.1.1-stable, AFAICT.
> 
> James: can you please give it a try as well?

Yes, I can confirm this fixes test_ssl_handshake on trunk.  There's
enough difference between trunk and branches/1.3.x that it doesn't apply
cleanly there.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#975539: marked as done (buku's autopkg tests fail with Python 3.9)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 03:33:26 +
with message-id 
and subject line Bug#975539: fixed in buku 4.5+ds-1
has caused the Debian Bug report #975539,
regarding buku's autopkg tests fail with Python 3.9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:buku
Version: 4.4+ds-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

https://ci.debian.net/data/autopkgtest/testing/amd64/b/buku/8348926/log.gz

[...]
tests/test_bukuDb.py:1082:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

caplog = <_pytest.logging.LogCaptureFixture object at 0x7f31084b1d30>
read_in_retval = 'y'

@pytest.mark.parametrize('read_in_retval', ['y', 'n', ''])
def test_update_rec_update_all_bookmark(caplog, read_in_retval):
"""test method."""
if (sys.version_info.major, sys.version_info.minor) == (3, 8):
caplog.set_level(logging.DEBUG)
with mock.patch('buku.read_in', return_value=read_in_retval):
import buku
bdb = buku.BukuDb()
res = bdb.update_rec(index=0, tags_in='tags1')
if read_in_retval != 'y':
assert not res
return
assert res
try:
if (sys.version_info.major, sys.version_info.minor) == (3, 8):
assert caplog.records[0].getMessage() == \
   'update_rec query: "UPDATE bookmarks SET tags = ?",
args: [\',tags1,\']'
else:
>   assert caplog.records[0].getMessage() == \
   'query: "UPDATE bookmarks SET tags = ?", args:
[\',tags1\']'
E  IndexError: list index out of range

tests/test_bukuDb.py:1071: IndexError
=== warnings summary ===
/usr/lib/python3/dist-packages/_pytest/mark/structures.py:331
  /usr/lib/python3/dist-packages/_pytest/mark/structures.py:331:
PytestUnknownMarkWarning: Unknown pytest.mark.non_tox - is this a typo?  You can
register custom marks to avoid this warning - for details, see
https://docs.pytest.org/en/latest/mark.html
warnings.warn(

tests/test_bukuDb.py::test_print_rec_hypothesis
  /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170:
HypothesisDeprecationWarning: tests/test_bukuDb.py::test_print_rec_hypothesis
uses the 'caplog' fixture, which is reset between function calls but not between
test cases generated by `@given(...)`.  You can change it to a module- or
session-scoped fixture if it is safe to reuse; if not we recommend using a
context manager inside your test function.  See
https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details on
fixture scope.
note_deprecation(

tests/test_bukuDb.py::test_print_rec_hypothesis
  /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170:
HypothesisDeprecationWarning: tests/test_bukuDb.py::test_print_rec_hypothesis
uses the 'setup' fixture, which is reset between function calls but not between
test cases generated by `@given(...)`.  You can change it to a module- or
session-scoped fixture if it is safe to reuse; if not we recommend using a
context manager inside your test function.  See
https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details on
fixture scope.
note_deprecation(

tests/test_bukuDb.py::test_delete_rec_range_and_delay_commit
  /usr/lib/python3/dist-packages/hypothesis/extra/pytestplugin.py:170:
HypothesisDeprecationWarning:
tests/test_bukuDb.py::test_delete_rec_range_and_delay_commit uses the 'setup'
fixture, which is reset between function calls but not between test cases
generated by `@given(...)`.  You can change it to a module- or session-scoped
fixture if it is safe to reuse; if not we recommend using a context manager
inside your test function.  See
https://docs.pytest.org/en/latest/fixture.html#sharing-test-data for details on
fixture scope.
note_deprecation(

tests/test_bukuDb.py::test_load_firefox_database[True]
tests/test_bukuDb.py::test_load_firefox_database[False]
  /tmp/autopkgtest-lxc.6o7juwq1/downtmp/build.1GI/src/tests/test_bukuDb.py:1206:
YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the
default Loader is unsafe. Please read https://msg.pyyaml.org/load for full 
details.
res_yaml = yaml.load(f)

-- Docs: https://docs.pytest.org/en/latest/warnings.html

--- 

Processed: Re: Bug#978437: geoclue-2.0: regression in 2.5.7-1, no geolocation returned

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 978437 https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/142
Bug #978437 [geoclue-2.0] geoclue-2.0: regression in 2.5.7-1, no geolocation 
returned
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/142'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978437: geoclue-2.0: regression in 2.5.7-1, no geolocation returned

[Laurent Bigonville]

forwarded 978437 https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/142
thanks

Le 30/12/20 à 16:43, gregor herrmann a écrit :

Thanks for the testing!

The following line is actually the real problem, I did all my tests on 
laptop with wifi cards, I just tried on my desktop and I get the same 
error (and timeout as you)

(geoclue:10479): Geoclue-WARNING **: 16:26:35.098: Failed to create query: No 
WiFi devices available


It looks like geoclue is not doing any request to the Mozilla Location 
Service is there is no wifi cards (or wifi network around) anymore

Processed: severity of 978437 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 978437 serious
Bug #978437 [geoclue-2.0] geoclue-2.0: regression in 2.5.7-1, no geolocation 
returned
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978675: libsys-hostname-long-perl: FTBFS, tests fail

[gregor herrmann]

On Wed, 30 Dec 2020 10:35:52 +, Holger Levsen wrote:

> On Wed, Dec 30, 2020 at 06:12:55AM +0100, Axel Beckert wrote:
> > gregoa: I'll leave up to you if you already want to close the bug
> > report or not. Feel free to replace my fixed tag with a pending tag or
> > so.
> I've already closed the bug :)

Thanks, Axel and Holger.

So the situation is:

I've uploaded -2 in order to
- see what the buildds say
- get more diagnostics
- get a .buildinfo file

And the result is:
- it built on my laptop and on the buildd
- we should have a .buildinfo file :)
- it still fails on the reproducible build servers
- and the diagnostics there failed as well (fixed in git, I got the
  order wrong)

Taking a step back: What the very simple module does is to try and
guess the FQDN of a machine, with various methods. And it seems this
doesn't always work (cf. "hostname: Temporary failure in name
resolution" in the logs of the failures but all other methods
which are tried later apparently fail as well).

So I guess we can say
- that the module and the tests probably work in most "real"
  situations
- but it can fail under "special" circumstances, which the RB hosts
  and Holger's build machine triggered (but nothing else or before,
  like Lucas' archive rebuilds).

We can now
- say "good enough" and forget about the issue
- or reopen the bug and lower the severity (and retitle it to
  something like "Sys::Hostname::Long fails if there is not
  networking/no DNS/something").
  
I'm not sure if/how the bug can be fixed, or if a failing `hostname'
is ultimately a bug in the package or in the environment.

Hm, and after writing this mail, I think that an environment where
`hostname' fails is maybe really to special in order to re-open the
bug.

But I'd still like to hear other opinions, that's why I started this
mail in the first place even if the bug is already closed :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Kings of Convenience: My Ship Isn't Pretty


signature.asc
Description: Digital Signature

Bug#975668: marked as done (lxpanel FTBFS: includes without dependency)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 00:34:15 +
with message-id 
and subject line Bug#975668: fixed in lxpanel 0.10.0-3
has caused the Debian Bug report #975668,
regarding lxpanel FTBFS: includes  without 
dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxpanel
Version: 0.10.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

To reproduce: build lxpanel on a release architecture in unstable (I used
amd64).

> plugin.c:32:10: fatal error: gdk-pixbuf-xlib/gdk-pixbuf-xlib.h: No such file 
> or directory
>32 | #include 
>   |  ^~~
> compilation terminated.

This is because the deprecated gdk-pixbuf-xlib-2.0 module used to be
pulled in as an indirect dependency by GTK 2. However, GTK 2 doesn't
actually use that module, and as a result libgtk2.0-dev no longer depends
on it, causing lxpanel to fail to build.

In the short term, please build-depend on either

libgdk-pixbuf-xlib-2.0-dev | libgdk-pixbuf2.0-dev

if you want backports to older Debian to be possible, or

libgdk-pixbuf-xlib-2.0-dev

if not. That's enough to close this bug. (This might also be a good
opportunity to check that all the other packages required at build time
are in the Build-Depends.)

For the longer term, the upstream maintainers of gdk-pixbuf have deprecated
the gdk-pixbuf-xlib-2.0 module[0] and do not intend to maintain it further,
so it would be better if lxpanel can stop using it.

Thanks,
smcv

[0] https://gitlab.gnome.org/Archive/gdk-pixbuf-xlib
--- End Message ---
--- Begin Message ---
Source: lxpanel
Source-Version: 0.10.0-3
Done: Andriy Grytsenko 

We believe that the bug you reported is fixed in the latest version of
lxpanel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andriy Grytsenko  (supplier of updated lxpanel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 02:05:06 +0200
Source: lxpanel
Architecture: source
Version: 0.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 

Changed-By: Andriy Grytsenko 
Closes: 975668
Changes:
 lxpanel (0.10.0-3) unstable; urgency=medium
 .
   * Adding libgdk-pixbuf-xlib-2.0-dev | libgdk-pixbuf2.0-dev into build
 dependencies (Closes: #975668).
   * Forcing autoreconf_clean for autoreconf (may be required on backport).
   * Reposition Vcs-* to the Debian Salsa.
   * Bump Standards-Version to 4.5.1.
   * Dropping lxpanel-dbg package in favor of autogenerated debug one.
   * Adding 'Rules-Requires-Root: no' header.
Checksums-Sha1:
 16726a0e7396c13d90a54fd5a152cab36803d0b6 2305 lxpanel_0.10.0-3.dsc
 6c30d0bc337b06ba61c295efd72f0ed8e1e21154 15080 lxpanel_0.10.0-3.debian.tar.xz
 9b35ee8af47afa5f274272091d7571815774cf16 12786 lxpanel_0.10.0-3_amd64.buildinfo
Checksums-Sha256:
 37e96a88f527ac17d00f173c894bfd5eaae3ea73e4add5eafa4617826005061a 2305 
lxpanel_0.10.0-3.dsc
 1c854730b41d80b8a60c0a2bf753c180640c2b80714f3c22f6de268b00715147 15080 
lxpanel_0.10.0-3.debian.tar.xz
 d8a1fd3e22a4732389c89a6b3c3f93595f276860e3ad06caebb04e55be6e24dc 12786 
lxpanel_0.10.0-3_amd64.buildinfo
Files:
 e0af3cbd10209026e1b02bf13024c9fc 2305 x11 optional lxpanel_0.10.0-3.dsc
 36ac30bfbaebf3cbb81493bd335d1e72 15080 x11 optional 
lxpanel_0.10.0-3.debian.tar.xz
 6f19c3d31c94402de1cf316b86928a03 12786 x11 optional 
lxpanel_0.10.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJf7RgXAAoJEAV2MC/hidTSrrcQAJoQqqSQjGZzp14Xig2bWm38
k4c7YRdZizNIsTeLsMTQ/Libq5UCOPxu1Zxoy7Cb3fvjplCivfJMzpTS9mLG4pZB
Pj2g903HaI/6fIcD8CQZRIrcTACnYiKxjT9tfGcJINEJPMozX2MBAW20x2ljlHMS
WIEPyf/wvHXQ1kg3gih7w4gM2IzllC3E5WHDruw/MSaYKdWr+4GZm3R5ippI/ixm
JwIdCqoj8abt0Uf4PvQJYeEQBk5TYrgSp5+mYaskbExXXtFj4JqZFv7FfK9i4PGL
u2ByATQRF8IOrFbcjUg/nwz0fuIVenkxRmcrP3Et5RXPY/psUOQNN8kAZJy/f7qs
wGPEMbJe44AJ2bzujIp6bA9pTXvBsh2CIYVGbevG3yTJN9P2LfkojOu1VaJO3oji

Processed: reassign 972659 to tpm2-tss, fixed 972659 in tpm2-tss/3.0.1-2, found 972659 in tpm2-tss/3.0.0-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 972659 tpm2-tss
Bug #972659 {Done: Ying-Chun Liu (PaulLiu) } 
[libtss2-esys0] libtss2-esys0: bumps SONAME without changing package name
Bug reassigned from package 'libtss2-esys0' to 'tpm2-tss'.
No longer marked as found in versions tpm2-tss/3.0.0-1.
No longer marked as fixed in versions tpm2-tss/3.0.1-2.
> fixed 972659 tpm2-tss/3.0.1-2
Bug #972659 {Done: Ying-Chun Liu (PaulLiu) } [tpm2-tss] 
libtss2-esys0: bumps SONAME without changing package name
Marked as fixed in versions tpm2-tss/3.0.1-2.
> found 972659 tpm2-tss/3.0.0-1
Bug #972659 {Done: Ying-Chun Liu (PaulLiu) } [tpm2-tss] 
libtss2-esys0: bumps SONAME without changing package name
Marked as found in versions tpm2-tss/3.0.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Hans-Christoph Steiner]

also, it looks like libunwindstack uses asm and there isn't any for ARM. 
 So if someone wants to keep the arm packages, they'll need to figure 
that out.  I have zero asm skills.

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Hans-Christoph Steiner]

Roger Shimizu:

On Wed, Dec 30, 2020 at 3:46 AM Hans-Christoph Steiner  wrote:


Ok, I fixed the dependency issue, now it gets reliably to the point rosh
gets to:


Thanks for fixing the build dependency issue!
I fixed a few other issues (operator script & mterp generation, etc),
and pushed to rosh/refine branch.

Current build breaking point is the same as previous one.
I tried to use different c++ library, such as libstdc++-8-dev, and
clang-9, but seems no help.


I have android-platform-art building as a stage1 now, so I'm working 
again on android-platform-system-core.  I haven't found where these 
symbols are supposed to come from:


clang++ fastboot/bootimg_utils.cpp fastboot/fastboot.cpp 
fastboot/fastboot_driver.cpp fastboot/fs.cpp fastboot/main.cpp 
fastboot/socket.cpp fastboot/tcp.cpp fastboot/udp.cpp 
fastboot/usb_linux.cpp fastboot/util.cpp fs_mgr/liblp/builder.cpp 
fs_mgr/liblp/images.cpp fs_mgr/liblp/partition_opener.cpp 
fs_mgr/liblp/reader.cpp fs_mgr/liblp/utility.cpp fs_mgr/liblp/writer.cpp 
-o fastboot/fastboot -g -O2 
-fdebug-prefix-map=/build/android-platform-system-core-10.0.0+r36=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-std=gnu++2a -fpermissive -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-UDEBUG -I/usr/include/android -DPLATFORM_TOOLS_VERSION='"28.0.2"' 
-Iinclude -Imkbootimg/include/bootimg -Iadb -Ibase/include 
-Idemangle/include -Idiagnose_usb/include -Ifs_mgr/include 
-Ifs_mgr/include_fstab -Ifs_mgr/liblp/include -I/usr/include/android 
-I/usr/include/android/f2fs_utils -I/usr/include/android/openssl 
-Ilibsparse/include -Ilibziparchive/include -Wl,-z,relro -Wl,-z,now 
-fPIC -Wl,-rpath=/usr/lib/x86_64-linux-gnu/android -Wl,-rpath-link=. -L. 
-lziparchive -lsparse -lbase -lcutils -ladb -lutils -lssl -lcrypto 
-L/usr/lib/x86_64-linux-gnu/android -lart -l7z -lunwind
/usr/bin/ld: /tmp/utility-794e29.o: in function 
`android::fs_mgr::GetDescriptorSize(int, unsigned long*)':
./fs_mgr/liblp/utility.cpp:49: undefined reference to 
`get_block_device_size'
/usr/bin/ld: ./libbacktrace.so.0: undefined reference to `typeinfo for 
art_api::dex::DexFile'


Check my forks for the most current commits:
https://salsa.debian.org/eighthave/android-platform-art
https://salsa.debian.org/eighthave/android-platform-system-core

.hc

Bug#978347: marked as done (foxeye: FTBFS: configure:9276: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 23:33:27 +
with message-id 
and subject line Bug#978347: fixed in foxeye 0.12.1-3
has caused the Debian Bug report #978347,
regarding foxeye: FTBFS: configure:9276: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foxeye
Version: 0.12.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> DC-Build-Header: foxeye 0.12.1-2 / 2020-12-26 18:41:32 +
> DC-Task: type:rebuild-full source:foxeye version:0.12.1-2 chroot:unstable 
> esttime:45 logfile:/tmp/foxeye_0.12.1-2_unstable.log modes:
> DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source 
> --apt-update -d unstable -v --no-run-lintian foxeye_0.12.1-2'
> sbuild (Debian sbuild) 0.78.1 (09 February 2019) on 
> ip-172-31-3-196.eu-central-1.compute.internal
> 
> +==+
> | foxeye 0.12.1-2 (amd64)  Sat, 26 Dec 2020 18:41:32 
> + |
> +==+
> 
> Package: foxeye
> Version: 0.12.1-2
> Source Version: 0.12.1-2
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> Build Type: full
> 
> I: NOTICE: Log filtering will replace 
> 'var/run/schroot/mount/sid-amd64-sbuild-1aa135d7-5d6e-4d06-b81f-8c421b05d4a4' 
> with '<>'
> I: NOTICE: Log filtering will replace 'build/foxeye-6c1NAs/resolver-9hdqL6' 
> with '<>'
> 
> +--+
> | Update chroot   
>  |
> +--+
> 
> Get:1 http://127.0.0.1:12990/debian sid InRelease [153 kB]
> Get:2 http://127.0.0.1:12990/debian sid/main Sources.diff/Index [27.9 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main amd64 Packages.diff/Index [27.9 
> kB]
> Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-12-26-0800.12.pdiff 
> [3765 B]
> Get:5 http://127.0.0.1:12990/debian sid/main Sources 2020-12-26-1401.32.pdiff 
> [20.3 kB]
> Get:5 http://127.0.0.1:12990/debian sid/main Sources 2020-12-26-1401.32.pdiff 
> [20.3 kB]
> Get:6 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-12-26-0800.12.pdiff [3354 B]
> Get:7 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-12-26-1401.32.pdiff [25.2 kB]
> Get:7 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-12-26-1401.32.pdiff [25.2 kB]
> Fetched 262 kB in 1s (255 kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Calculating upgrade...
> The following packages will be upgraded:
>   libsystemd0 libudev1
> 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 540 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1 http://127.0.0.1:12990/debian sid/main amd64 libsystemd0 amd64 247.2-3 
> [374 kB]
> Get:2 http://127.0.0.1:12990/debian sid/main amd64 libudev1 amd64 247.2-3 
> [166 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 540 kB in 0s (9510 kB/s)
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 12355 files and directories currently installed.)
> Preparing to unpack .../libsystemd0_247.2-3_amd64.deb ...
> Unpacking libsystemd0:amd64 (247.2-3) over (247.2-2) ...
> Setting up libsystemd0:amd64 (247.2-3) ...
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%

Bug#978431: texlive-base: dist-upgrade buster->bullseye fails

[Hilmar Preuße]

Am 27.12.2020 um 12:42 teilte Rene Engelhard mit:

Hi Rene,

Many thanks for the report!


dist-upgrade buster->bullseye which just caused my system to not get out of apt 
-f install anymore:

Entpacken von texlive-base (2020.20201203-2) über (2018.20190227-2) ...
dpkg: Fehler beim Bearbeiten des Archivs 
/tmp/apt-dpkg-install-nSKKZq/20-texlive-base_2020.20201203-2_all.deb (--unpack):
  Versuch, »/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« zu 
überschreiben, welches auch in Paket texlive-plain-generic 2018.20190227-2 ist
dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Datenübergabe 
unterbrochen (broken pipe)) getötet
Regenerating '/var/lib/texmf/fmtutil.cnf-DEBIAN'... done.
Regenerating '/var/lib/texmf/fmtutil.cnf-TEXLIVEDIST'... done.
update-fmtutil has updated the following file(s):
 /var/lib/texmf/fmtutil.cnf-DEBIAN
 /var/lib/texmf/fmtutil.cnf-TEXLIVEDIST
If you want to activate the changes in the above file(s),
you should run fmtutil-sys or fmtutil.
[...]

Did you find the conflict by chance or do you systematically do 
dist-upgrade test? Just a question: if I do an upload to solve this 
conflict I'd like to solve all conflicts of this type.


Many thanks!

Hilmar
--
sigfault




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977225: marked as done (openscad FTBFS with Boost 1.74)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 22:49:49 +
with message-id 
and subject line Bug#977225: fixed in openscad 2019.05-4
has caused the Debian Bug report #977225,
regarding openscad FTBFS with Boost 1.74
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openscad
Version: 2019.05-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=openscad

...
src/import.cc:53:10: fatal error: boost/detail/endian.hpp: No such file or 
directory
   53 | #include 
  |  ^
compilation terminated.
make[2]: *** [Makefile:3559: objects/src/import.o] Error 1
--- End Message ---
--- Begin Message ---
Source: openscad
Source-Version: 2019.05-4
Done: Kristian Nielsen 

We believe that the bug you reported is fixed in the latest version of
openscad, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kristian Nielsen  (supplier of updated openscad 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Dec 2020 14:21:30 +0100
Source: openscad
Architecture: source
Version: 2019.05-4
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: Kristian Nielsen 
Closes: 945162 977225
Changes:
 openscad (2019.05-4) unstable; urgency=medium
 .
   * Make openscad-testrun default to run tests in parallel.
   * Limit --parallel build based on available memory (Closes: #945162).
   * Fix build with newer boost library (Closes: #977225).
   * Clean up some lintian warnings.
Checksums-Sha1:
 71e3d71bc191944eb8f5d8b0a08b91271df6a013 2883 openscad_2019.05-4.dsc
 b82835bd7e4cfa0a18e33614e17bff2403d68a2b 45028 openscad_2019.05-4.debian.tar.xz
 e43d7055b1539211f806adbae79a8ed6da69191f 16316 
openscad_2019.05-4_amd64.buildinfo
Checksums-Sha256:
 00fab83e089d203ec753cc35f59fabc4012681cb4c58b5b4bbe9a543e82dc24b 2883 
openscad_2019.05-4.dsc
 cc3764d6419af27e0585778ad4af3210de09bccf9ac2f4bd28debba36bb6c606 45028 
openscad_2019.05-4.debian.tar.xz
 3dadced368ebc483b4b09d06ebb0a070857081e0358ec68fbb62d23f2a39aeca 16316 
openscad_2019.05-4_amd64.buildinfo
Files:
 c35ccb2509428084ffd025835ae9f8e7 2883 graphics optional openscad_2019.05-4.dsc
 b00526311c58c4ce6ae3222af7120acc 45028 graphics optional 
openscad_2019.05-4.debian.tar.xz
 bd71998057a3c65307631e407c4adbda 16316 graphics optional 
openscad_2019.05-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAl/s/18ACgkQdCY7N/W1
+RMVVA//R4BjOMRioiw4HIQdfsi79ZY68+Xqh5h+rJBpxaaLMHe8mgUM5qEE9284
hjIYhUV0gajXsTguUHOyX36/gkreD4pjIaWoJb39YwidispvAzNvgaHuj0xuNFT4
dxrB+nDomhJ0XCUPVppOhQdAkYLeZZYM3Syhz/HHQDq79Pj9KGUV08y9pnGIEWa2
X03SJlav7lBHrMe5kYWtPsif7nKZsLyTgjDMjT8mweAw2aNDPEozK7RPiZVGyBTf
aKT1c5aaijx84hm5ZFPN8E99Gk8uwEzo9t77RXsmscBola3xZ10mSVFwk5a5NSJb
ub0qNQzI1I2ijaFs9SFJ62T2t3+j2sXXfJwk5cKiK6QNCkeod7LVIWThUL2yWpkG
UXqeW9k71+/I6BbLw3r6qW6hvDSmTjktBj/l+9IP/zOL0zTa5i1UEvB501dXyY3s
/JqvU9FdzL/Hzt9YpVf64F7c4S2K0MgL6Hswe6Mrd6DQuIBr40V2p3UvItToUtam
rRq4jCQUhCHTpI09xutLTyynB8B1DXstPkcaC63PuSIOeyeHUF5p4t98aNGpEp86
UdqynScwKeD4Ongpc552PEng0/vsdZ0AGwFG6IcDnFJaGGRgqyMjsg8APnva3Pk5
2/jvRZQbQ9qJ0jLqcEU4iKuh1rPPVef+5boXFWR3xHAjKI0Slf0=
=eVOf
-END PGP SIGNATURE End Message ---

Bug#978640: undefined symbol: _ZTIN3fmt2v612format_errorE

[Hubert Chathi]

On Tue, 29 Dec 2020 23:26:38 +0530, Utkarsh Gupta  said:

> Hi Hubert,
> On Tue, Dec 29, 2020 at 11:17 PM Hubert Chathi  wrote:
>> Hmm.  Can you try installing libfmt7 (from sid) and see if that fixes
>> it?

> The issue could be fixed by rebuilding nheko against the newly updated
> libfmt-dev version. I've prepared and pushed a fix to the salsa
> repository. If it's okay with you, can I do the upload as well?

binNMU requested at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978722

Apparently waiting for an update to spdlog.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Processed: Re: openms: FTBFS: glpk.h:36:16: error: using typedef-name ‘glp_prob’ after ‘struct’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #978194 [src:openms] openms: FTBFS: glpk.h:36:16: error: using typedef-name 
‘glp_prob’ after ‘struct’
Added tag(s) patch.

-- 
978194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978194: openms: FTBFS: glpk.h:36:16: error: using typedef-name ‘glp_prob’ after ‘struct’

[Logan Rosen]

Package: openms
Version: 2.6.0+cleaned1-1
Followup-For: Bug #978194
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/fix-glpk-version-check.patch: Fix GLPK version check that doesn't
account for major version, fixing FTBFS against GLPK 5.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 
'groovy'), (100, 'groovy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-33-generic (SMP w/8 CPU threads)
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
diff -Nru openms-2.6.0+cleaned1/debian/patches/fix-glpk-version-check.patch 
openms-2.6.0+cleaned1/debian/patches/fix-glpk-version-check.patch
--- openms-2.6.0+cleaned1/debian/patches/fix-glpk-version-check.patch   
1969-12-31 19:00:00.0 -0500
+++ openms-2.6.0+cleaned1/debian/patches/fix-glpk-version-check.patch   
2020-12-30 13:01:49.0 -0500
@@ -0,0 +1,11 @@
+--- a/src/openms/include/OpenMS/DATASTRUCTURES/LPWrapper.h
 b/src/openms/include/OpenMS/DATASTRUCTURES/LPWrapper.h
+@@ -51,7 +51,7 @@
+ #define GLP_PROB_DEFINED
+ // depending on the glpk version
+ // define glp_prob as forward or struct
+-#if OPENMS_GLPK_VERSION_MINOR < 48
++#if OPENMS_GLPK_VERSION_MAJOR == 4 && OPENMS_GLPK_VERSION_MINOR < 48
+ typedef struct
+ {
+   double _opaque_prob[100];
diff -Nru openms-2.6.0+cleaned1/debian/patches/series 
openms-2.6.0+cleaned1/debian/patches/series
--- openms-2.6.0+cleaned1/debian/patches/series 2020-12-15 08:29:00.0 
-0500
+++ openms-2.6.0+cleaned1/debian/patches/series 2020-12-30 13:00:56.0 
-0500
@@ -1,2 +1,3 @@
 sonameAndNameLinkSkipCmakeBuildSystem.patch
 installDirsSettingsCmakeBuildSystem.patch
+fix-glpk-version-check.patch

Bug#963058: marked as done (android-platform-art ftbfs on arm64)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 21:18:29 +
with message-id 
and subject line Bug#963058: fixed in android-platform-art 10.0.0+r36-1~stage1
has caused the Debian Bug report #963058,
regarding android-platform-art ftbfs on arm64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
963058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:
Version: 8.1.0+r23-4
Severity: serious
Tags: sid bullseye

android-platform-art ftbfs on arm64:

[...]
python3 tools/generate-operator-out.py runtime runtime/arch/instruction_set.h
runtime/base/allocator.h runtime/base/callee_save_type.h runtime/base/enums.h
runtime/base/mutex.h runtime/debugger.h runtime/base/unix_file/fd_file.h
runtime/dex_file.h runtime/dex_file_layout.h runtime/dex_instruction.h
runtime/dex_instruction_utils.h runtime/gc_root.h runtime/gc/allocator_type.h
runtime/gc/allocator/rosalloc.h runtime/gc/collector_type.h
runtime/gc/collector/gc_type.h runtime/gc/heap.h runtime/gc/space/region_space.h
runtime/gc/space/space.h runtime/gc/weak_root_state.h runtime/image.h
runtime/instrumentation.h runtime/indirect_reference_table.h
runtime/invoke_type.h runtime/jdwp/jdwp.h runtime/jdwp/jdwp_constants.h
runtime/lock_word.h runtime/mirror/class.h runtime/oat.h
runtime/object_callbacks.h runtime/process_state.h runtime/stack.h
runtime/suspend_reason.h runtime/thread.h runtime/thread_state.h
runtime/ti/agent.h runtime/verifier/verifier_enums.h > operator_out.cc
clang -o runtime/interpreter/mterp/out/mterp_arm64.o -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -c -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG
-I/usr/include/android -UDEBUG -Umips -DART_BASE_ADDRESS_MAX_DELTA=0x100
-DART_BASE_ADDRESS_MIN_DELTA=-0x100 -DART_BASE_ADDRESS=0x6000
-DART_DEFAULT_COMPACT_DEX_LEVEL=fast -DART_DEFAULT_GC_TYPE_IS_CMS
-DART_ENABLE_ADDRESS_SANITIZER=1 -DART_ENABLE_CODEGEN_arm
-DART_ENABLE_CODEGEN_arm64 -DART_ENABLE_CODEGEN_mips -DART_ENABLE_CODEGEN_mips64
-DART_ENABLE_CODEGEN_x86 -DART_ENABLE_CODEGEN_x86_64 -DART_FRAME_SIZE_LIMIT=6400
-DART_READ_BARRIER_TYPE_IS_BAKER=1 -DART_STACK_OVERFLOW_GAP_arm=8192
-DART_STACK_OVERFLOW_GAP_arm64=8192 -DART_STACK_OVERFLOW_GAP_mips=16384
-DART_STACK_OVERFLOW_GAP_mips64=16384 -DART_STACK_OVERFLOW_GAP_x86_64=20480
-DART_STACK_OVERFLOW_GAP_x86=16384 -DART_USE_READ_BARRIER=1 -DBUILDING_LIBART=1
-DIMT_SIZE=43 -DUSE_D8_DESUGAR=1 -I. -I/usr/include/android/nativehelper
-I/usr/include/valgrind -Icmdline -Iruntime -Iruntime/generated -Isigchainlib
runtime/interpreter/mterp/out/mterp_arm64.S
runtime/interpreter/mterp/out/mterp_arm64.S:392:23: error: expected
'[su]xt[bhw]' with optional integer in range [0, 4]
add x25, x21, w0, lsl #2
  ^
runtime/interpreter/mterp/out/mterp_arm64.S:395:23: error: expected
'[su]xt[bhw]' with optional integer in range [0, 4]
add x20, x20, w0, lsl #1
  ^
:1:19: error: expected '[su]xt[bhw]' with optional integer in
range [0, 4]
add x17, x21, w3, lsl #2
  ^
runtime/interpreter/mterp/out/mterp_arm64.S:489:5: note: while in macro
instantiation
--- End Message ---
--- Begin Message ---
Source: android-platform-art
Source-Version: 10.0.0+r36-1~stage1
Done: Hans-Christoph Steiner 

We believe that the bug you reported is fixed in the latest version of
android-platform-art, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated android-platform-art 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Oct 2020 17:10:14 +0200
Source: android-platform-art
Architecture: source
Version: 10.0.0+r36-1~stage1
Distribution: unstable
Urgency: low
Maintainer: Android Tools Maintainers 

Changed-By: Hans-Christoph Steiner 
Closes: 963058
Changes:
 android-platform-art (10.0.0+r36-1~stage1) unstable; urgency=low
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Use correct machine-readable copyright file URI.
   * Bump debhelper from old 11 to 12.
 

Bug#978520: marked as done (tao-pegtl: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 19:48:43 +
with message-id 
and subject line Bug#978520: fixed in tao-pegtl 2.8.3-3
has caused the Debian Bug report #978520,
regarding tao-pegtl: non-standard gcc/g++ used for build (gcc-9)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tao-pegtl
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: tao-pegtl
Source-Version: 2.8.3-3
Done: Birger Schacht 

We believe that the bug you reported is fixed in the latest version of
tao-pegtl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Birger Schacht  (supplier of updated tao-pegtl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Dec 2020 16:23:59 +0100
Source: tao-pegtl
Architecture: source
Version: 2.8.3-3
Distribution: unstable
Urgency: medium
Maintainer: Birger Schacht 
Changed-By: Birger Schacht 
Closes: 978520
Changes:
 tao-pegtl (2.8.3-3) unstable; urgency=medium
 .
   * d/rules: force -Wno-error=type-limits to enable build with gcc 10
 (Closes: #978520)
   * d/control: bump standards-version to 4.5.1 (no changes required)
Checksums-Sha1:
 9904dfab595d20237422c4f9fa485ce85641781f 1874 tao-pegtl_2.8.3-3.dsc
 0a7292de66992a67ec99aa24de8da69b03c5c3d5 2440 tao-pegtl_2.8.3-3.debian.tar.xz
 fcc452f4bf0f7ab6978b8795f295837070718290 6333 tao-pegtl_2.8.3-3_amd64.buildinfo
Checksums-Sha256:
 0ba597daedc6bd92c057585341bc73a6f0d96b7e64bece67760e2f253f9ec6ca 1874 
tao-pegtl_2.8.3-3.dsc
 3a85a9b04c015822f2917df51114ff20f5fdf22829ce3e59907360f1f993783b 2440 
tao-pegtl_2.8.3-3.debian.tar.xz
 91a612ce567fc11bfec7c8a438deced1500ba8cfbe0f61dbe9c97a69e664be77 6333 
tao-pegtl_2.8.3-3_amd64.buildinfo
Files:
 12053f6b0ac736c62065f69a5ccc7b00 1874 libs optional tao-pegtl_2.8.3-3.dsc
 0c20eff31d051fcd3ed1109045291a02 2440 libs optional 
tao-pegtl_2.8.3-3.debian.tar.xz
 e35b77177129d85ee89d665e044d503e 6333 libs optional 
tao-pegtl_2.8.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEOvC8tnwmrEjOtOW8KgxdYPIEvbAFAl/s084SHGJpcmdlckBk
ZWJpYW4ub3JnAAoJECoMXWDyBL2wNW8P/ibT/DiRLBD77quSpsL3q/7RuoMTJWnn
po5Y3gt7/o1KbpFhW22p7VAuCNdj9krNZlkJDOptJZvbbJc9Et3c0bxJmxh/zEPQ
F+80LxjRHKIyeWpC4N9JRNywAEhtZdsbwkQTB1EGERdjeQiIW9uaHNh1CUAQBzvC
a+Ixm03MftSgVEWtaMvrNhAqfYvtmfXMKCIaFqBIjzR2S94V2GigLFiEBO7OEe5J
FdVMKa2YfVSrzBxUmJN1L2jROUTCVD8YXXzwouiJNaqld5u8mKYqZVX+JF6xHiMe
Y3Q4sLJ0ypz5H1JOv9VcyjdiIqXnymYbN0muOcx34S/WGDWHSCs68iGEaajFAipb
9PHFeMRunsD/6zaq6DSH7gJzuEC7jBW9vxvqo5z8na+k227Eyipxn+LoAQj7lC6j
Z/nLbUzRc0nFkl43sREuSZo6duVogUlKPko7IMRa6v3BAXWf5uwgf1VB2gVlHU/X
6DJrnI8dotUTl4wjHuo9nerkVxO6yRIG5FDP3H1TQoQVCpIIohiiQ8xilTTocx7s
h41Wx70shHGPoK7J6Ne4wavNFYWZdUjZBt4tYMDd89NeoOe72tYGCHxV/UXdJya1
uNP5bD44RoZPoR/CJIWRq9sd/O3zCbppbdWyooTN6dE5xAaTUmDqLf//0uj3WcTF
OUZHjeAgzyTY
=Z3bV
-END PGP SIGNATURE End Message ---

Bug#976092: marked as done (ocrmypd fails autopkg tests in testing)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 12:46:02 -0700
with message-id <87v9cj5b7p@melete.silentflame.com>
and subject line Re: Bug#976092: ocrmypd fails autopkg tests in testing
has caused the Debian Bug report #976092,
regarding ocrmypd fails autopkg tests in testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocrmypdf
Version: 10.3.1+dfsg-1
Severity: serious
Tags: sid bullseye

ocrmypd fails autopkg tests in testing, but not in unstable. Looks like a
missing break on some dependency?

see https://ci.debian.net/packages/o/ocrmypdf

[...]
resources =
PosixPath('/tmp/autopkgtest-lxc.fy1hic18/downtmp/build.Qgv/src/tests/resources')
outdir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_rotate_deskew_timeout0')

def test_rotate_deskew_timeout(resources, outdir):
check_ocrmypdf(
resources / 'rotated_skew.pdf',
outdir / 'deskewed.pdf',
'--rotate-pages',
'--rotate-pages-threshold',
'0',
'--deskew',
'--tesseract-timeout',
'0',
'--pdf-renderer',
'sandwich',
)

correlation = check_monochrome_correlation(
outdir,
reference_pdf=resources / 'ccitt.pdf',
reference_pageno=1,
test_pdf=outdir / 'deskewed.pdf',
test_pageno=1,
)

# Confirm that the page still got deskewed
>   assert correlation > 0.50
E   assert 0.0 > 0.5

tests/test_rotation.py:214: AssertionError
- Captured stderr call -

Scanning contents:   0%|  | 0/1 [00:00--- End Message ---
--- Begin Message ---
Hello,

On Sun 29 Nov 2020 at 04:38PM +01, Matthias Klose wrote:

> Package: src:ocrmypdf
> Version: 10.3.1+dfsg-1
> Severity: serious
> Tags: sid bullseye
>
> ocrmypd fails autopkg tests in testing, but not in unstable. Looks like a
> missing break on some dependency?

The tests are passing now.  While there is in some sense still a non-RC
bug here as ocrmypdf does not have a version restriction to prevent the
tests running with a broken version of the broken dependency (which is
probably ghostscript -- thanks James), I'm closing the bug as that
broken version is no longer in the archive.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#947272: blt builds fine with gcc-10

[Holger Levsen]

On Wed, Dec 30, 2020 at 06:36:23PM +0300, Sergei Golovan wrote:
> There isn't Tcl/Tk 8.7 in unstable yet, only an alpha in experimantal.
> After the Tcl/Tk 8.7 will be released, I'll deal with this bug in
> unstable.

ah, ok, makes sense. 

probably it would still be nicer to downgrade this bug to severity important
until that tcl/tk version has reached unstable.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

Dance like no one's watching. Encrypt like everyone is.


signature.asc
Description: PGP signature

Bug#960454: marked as done (chromium: Make Chromium ask before downloading and enabling DRM)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 17:04:08 +
with message-id 
and subject line Bug#960454: fixed in chromium 87.0.4280.88-0.4
has caused the Debian Bug report #960454,
regarding chromium: Make Chromium ask before downloading and enabling DRM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
960454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 80.0.3987.162-1~deb10u1
Severity: wishlist

Dear Maintainer,


When using Chromium and visiting websites that need DRM to be enabled, Chromium
automatically downloads and enables DRM.
These are binary blobs that are not free software.
No notification is made to the user that (s)he is now using non-free software.

If possible if would be great to have a switch in the settings for this (like
Firefox has).
Or at least that the user be showned a message that this website has made
chromium now using non-free software.



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), 
LANGUAGE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  80.0.3987.162-1~deb10u1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.3.0-6
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.4-1~deb10u1
ii  libavformat587:4.1.4-1~deb10u1
ii  libavutil56  7:4.1.4-1~deb10u1
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6+deb10u3
ii  libdbus-1-3  1.12.16-1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-2+deb10u1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6+deb10u1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1+deb10u2
ii  libopenjp2-7 2.3.0-2+deb10u1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4+deb10u1
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-6
ii  libvpx5  1.7.0-3+deb10u1
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2.2~deb10u1
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  80.0.3987.162-1~deb10u1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n80.0.3987.162-1~deb10u1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1+deb10u1

Versions of packages chromium-common recommends:
ii  chromium-sandbox   80.0.3987.162-1~deb10u1
ii  fonts-liberation   1:1.07.4-9
ii  gnome-shell [notification-daemon]  3.30.2-11~deb10u1
ii  libgl1-mesa-dri18.3.6-2+deb10u1
ii  libu2f-udev1.1.9-1
ii  notification-daemon3.20.0-4
ii  upower 0.99.10-1

Versions of packages chromium-sandbox depends on:
ii  libatomic1  8.3.0-6
ii  libc6  

Bug#978704: securefs: autopkgtests hard-code dependency on libcrypto++6

[Yanhao Mo]

thanks for the reports, I will fix this in the next couple days

Sebastian Ramacher  writes:

> On 2020-12-30 15:06:19 +0100, Sebastian Ramacher wrote:
>> Source: securefs
>> Version: 0.11.1+ds-1
>> Severity: serious
>> X-Debbugs-Cc: sramac...@debian.org
>> 
>> securefs' autopkgtests hard-code dependencies on a bunch of shared
>> libraries: libcrypto++6, libfuse2, libjsoncpp1, and libutf8profc2. This
>> is most certainly wrong when securefs is rebuilt for transitions. At
>> least the dependencies on libcrypto++6 and libjsoncpp1 are no longer
>> correct.
>> 
>> Having dependencies on the -dev packages there or installing securefs
>> would make more sense to get the right runtime libraries.
>
> On second thought, installing securefs could also give the wrong
> results. So the former would make more sense. In any case, this issue
> causes autopkgtest failures:
>
> autopkgtest [05:13:56]: test command2: cd obj-x86_64-linux-gnu && 
> ./securefs_test
> autopkgtest [05:13:56]: test command2: [---
> ./securefs_test: error while loading shared libraries: libcrypto++.so.8: 
> cannot open shared object file: No such file or directory
> autopkgtest [05:13:56]: test command2: ---]
> autopkgtest [05:13:56]: test command2:  - - - - - - - - - - results - - - - - 
> - - - - -
> command2 FAIL non-zero exit status 127
>
> See
> https://ci.debian.net/data/autopkgtest/testing/amd64/s/securefs/9241910/log.gz
>
> Cheers

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

[Bernhard Schmidt]

Dear Gianfranco,

Thanks for filing this bug report. I’m away for the next couple of days and 
could not check, but wouldn’t just patching the pkgconfig file (your second 
option) be a lot easier? Upstream merged both libraries and they probably just 
forgot to change the pkgconfig file as well.

In the end linphone upstream does not seem to care much about other programs 
using their library. 

Bernhard

> Am 29.12.2020 um 11:00 schrieb Gianfranco Costamagna 
> :
> Source: mediastreamer2
> Version: 1:4.4.21-2
> Severity: serious
> 
> Hello, looks like with autotools, the library provides libmediastreamer_base 
> and libmediastreamer_voip,
> while with cmake it doesn't.
> 
> the pkgconfig file is obviously wrong, but I don't know which solution you 
> prefer (and if you are aware of this issue).
> 
> I propose two solutions:
> 1) implement the library split in cmake, and upstream it (this might be the 
> preferred and easier solution to this issue)
> 2) patch pkgconfig file and cmake helpers to provide only one library to link.
> 
> if we choose 1, we should probably also change the ABI, so call it 
> libmediastreamer11a or similar, to trigger a rebuild of reverse dependencies.
> 
> If you agree with 1) I can try to provide a patch as soon as possible.
> 
> thanks
> 
> Gianfranco

Bug#978695: notepadqq: Input windows hangs so input is not possible

[Michael Rasmussen]

Package: notepadqq
Version: 2.0.0~beta1-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When notepadqq is started you expect to see an empty tab
or tabs with reason files, but neither happens. Try to open a tab
resolves in a frozen application and if started from command line
the following is seen:

js: Uncaught ReferenceError: $ is not defined
js: Uncaught ReferenceError: $ is not defined
Now close application and this is shown:
js: Uncaught TypeError: Cannot read property 'isClean' of undefined

>From here only way to actually quit the application is ^C

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

Kernel: Linux 5.9.0-5-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.UTF-8
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages notepadqq depends on:
ii  coreutils8.32-4+b1
ii  libc62.31-6
ii  libgcc-s110.2.1-3
ii  libjs-highlight.js   9.18.1+dfsg1-3
ii  libjs-jquery 3.5.1+dfsg+~3.5.5-4
ii  libjs-mathjax2.7.9+dfsg-1
ii  libjs-modernizr  2.6.2+ds1-3
ii  libjs-requirejs  2.3.6+ds-1
ii  libqt5core5a 5.15.2+dfsg-2
ii  libqt5gui5   5.15.2+dfsg-2
ii  libqt5network5   5.15.2+dfsg-2
ii  libqt5printsupport5  5.15.2+dfsg-2
ii  libqt5svg5   5.15.2-2
ii  libqt5webchannel55.15.2-2
ii  libqt5webenginewidgets5  5.15.2+dfsg-3
ii  libqt5widgets5   5.15.2+dfsg-2
ii  libstdc++6   10.2.1-3
ii  libuchardet0 0.0.7-1

notepadqq recommends no packages.

notepadqq suggests no packages.

-- no debconf information



This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.

Bug#947272: blt builds fine with gcc-10

[Sergei Golovan]

Hi Holger,

On Wed, Dec 30, 2020 at 6:26 PM Holger Levsen  wrote:
>
> Hi Sergei,
>
> On Wed, Dec 30, 2020 at 05:26:53PM +0300, Sergei Golovan wrote:
> > This bug is actually about blt 2.5.3+dfsg-5 and failure to build with
> > Tcl/Tk 8.7. So the serious severity is justified. The bug title is
> > misleading though, so I'm changing it. Sorry for not doing it sooner.
>
> ah, cool!
>
> now I just wonder why it still builds in unstable?

There isn't Tcl/Tk 8.7 in unstable yet, only an alpha in experimantal.
After the Tcl/Tk 8.7 will be released, I'll deal with this bug in
unstable.

-- 
Sergei Golovan

Bug#978681: Ignore my previous message, sent by mistake

[Domenico Andreoli]

Hi,

Please ignore my previous message, was sent by mistake. Apologies for
the spam.

Regards,
Domenico

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05

Bug#947272: blt builds fine with gcc-10

[Holger Levsen]

Hi Sergei,

On Wed, Dec 30, 2020 at 05:26:53PM +0300, Sergei Golovan wrote:
> This bug is actually about blt 2.5.3+dfsg-5 and failure to build with
> Tcl/Tk 8.7. So the serious severity is justified. The bug title is
> misleading though, so I'm changing it. Sorry for not doing it sooner.

ah, cool!

now I just wonder why it still builds in unstable?


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

Never waste a crisis.


signature.asc
Description: PGP signature

Bug#971209: marked as done (rust-redox-syscall: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 15:19:08 +
with message-id 
and subject line Bug#971209: fixed in rust-redox-syscall 0.1.57-2
has caused the Debian Bug report #971209,
regarding rust-redox-syscall: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo build returned exit code 101
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
971209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-redox-syscall
Version: 0.1.40-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> export RUSTC_BOOTSTRAP=1; \
> case x86_64-unknown-linux-gnu in \
> arm-*|x86-*|x86_64-*) \
>   dh_auto_test;; \
> *) \
>   dh_auto_test || true;; \
> esac
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling redox_syscall v0.1.40 (/<>)
>  Running `CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_NAME=redox_syscall 
> CARGO=/usr/bin/cargo 
> CARGO_PKG_REPOSITORY='https://github.com/redox-os/syscall' 
> CARGO_PKG_AUTHORS='Jeremy Soller ' 
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PRE= 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_VERSION=0.1.40 
> CARGO_PKG_VERSION_PATCH=40 CARGO_PKG_DESCRIPTION='A Rust library to access 
> raw Redox system calls' CARGO_PKG_HOMEPAGE= 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name syscall src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi --crate-type lib 
> --emit=dep-info,metadata,link -C debuginfo=2 -C metadata=65c14a21970da5f1 -C 
> extra-filename=-65c14a21970da5f1 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn 
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix 
> /<>=/usr/share/cargo/registry/redox-syscall-0.1.40`
> error: the legacy LLVM-style asm! syntax is no longer supported
>  --> src/arch/x86_64.rs:4:5
>   |
> 4 |   asm!("int 0x80"
>   |   ^---
>   |   |
>   |  _help: replace with: `llvm_asm!`
>   | |
> 5 | | : "={rax}"(a)
> 6 | | : "{rax}"(a)
> 7 | | : "memory"
> 8 | | : "intel", "volatile");
>   | |___^
>   |
>   = note: consider migrating to the new asm! syntax specified in RFC 2873
>   = note: alternatively, switch to llvm_asm! to keep your code working as it 
> is
> 
> error: the legacy LLVM-style asm! syntax is no longer supported
>   --> src/arch/x86_64.rs:14:5
>|
> 14 |   asm!("int 0x80"
>|   ^---
>|   |
>|  _help: replace with: `llvm_asm!`
>| |
> 15 | | : "={rax}"(a)
> 16 | | : "{rax}"(a), "{rbx}"(b)
> 17 | | : "memory"
> 18 | | : "intel", "volatile");
>| |___^
>|
>= note: consider migrating to the new asm! syntax specified in RFC 2873
>= note: alternatively, switch to llvm_asm! to keep your code working as it 
> is
> 
> error: the legacy LLVM-style asm! syntax is no longer supported
>   --> src/arch/x86_64.rs:25:5
>|
> 25 |   asm!("int 0x80"
>|   ^---
>|   |
>|  _help: replace with: `llvm_asm!`
>| |
> 26 | | : "={rax}"(a)
> 27 | | : "{rax}"(a), "{rbx}"(b)
> 28 | | : "memory", "rbx", "rcx", "rdx", "rsi", "rdi", "r8",
> 29 | |   "r9", "r10", "r11", "r12", "r13", "r14", "r15"
> 30 | | : "intel", "volatile");
>| |___^
>|
>= note: consider migrating to the new asm! syntax specified in RFC 2873
>= note: alternatively, switch to llvm_asm! to keep your code working as it 
> is
> 
> error: the legacy LLVM-style asm! syntax is no longer supported
>   --> src/arch/x86_64.rs:36:5
>|
> 36 |   asm!("int 0x80"
>|   ^---
>|   |
>|  _help: replace with: `llvm_asm!`
>| |
> 37 | | : "={rax}"(a)
> 38 | | : "{rax}"(a), 

Processed: Set +pending on the wrong bug. Remeding.

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 978681 -pending
Bug #978681 [xfce4-mpc-plugin] xfce4-mpc-plugin: build-depends on obsolete 
package.
Ignoring request to alter tags of bug #978681 to the same tags previously set
> tag 978691 +pending
Bug #978691 [src:dwarves-dfsg] dwarves-dfsg: New upstream version available 
(1.19)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978681
978691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#976586: marked as done (boxbackup: FTBFS: latex undefined control sequence)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 15:54:23 +0100
with message-id 
and subject line Build failure solved
has caused the Debian Bug report #976586,
regarding boxbackup: FTBFS: latex undefined control sequence
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boxbackup
Version: 0.13~~git20200326.g8e8b63c-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[1]: Entering directory '/<>/docs'
>   [XLSTPROC] docbook/bb-book.xsl docbook/instguide.xml
> make[1]: Leaving directory '/<>/docs'
> cd docs/docbook && docbook2pdf instguide.xml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/docs/docbook/instguide.xml
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
> (preloaded format=pdfjadetex)
>  restricted \write18 enabled.
> entering extended mode
> 
> (/<>/docs/docbook/inst
> guide.tex
> JadeTeX 2003/04/27: 3.13
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
> Elements will be labelled
> Jade begin document sequence at 20
> No file instguide.aux.
> (/usr/share/texmf/tex/latex/tipa/t3ptm.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd) 
> [1.0.32{/var/lib/texm
> f/fonts/map/pdftex/updmap/pdftex.map}] [2.0.32]
> 
> Package Fancyhdr Warning: \fancyfoot's `E' option without twoside option is 
> use
> less on input line 183.
> 
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.224 {0:2}}
> \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.228 ...-mode}}License\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.232 {0:2}}
> \Seq%
> 
> LaTeX Warning: Reference `0:2' on page iii undefined on input line 238.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.238 {0:2}}\endNode{}\endSeq{}\endLink
>{}\endSeq{}\endPar{}\Par%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.256 {0:17}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.262 ...}}Introduction\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.266 {0:17}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:17' on page iii undefined on input line 272.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.272 {0:17}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.282 {0:21}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.288 ...}Client daemon\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.292 {0:21}}
>  \Seq%
> 
> LaTeX Warning: Reference `0:21' on page iii undefined on input line 298.
> 
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.298 {0:21}}\endNode{}\endSeq{}\endLink
> {}\endSeq{}\endPar{}\Seq%
> ! Undefined control sequence.
>  \Hy@colorlink 
>   
> l.308 {0:29}}
>  \Seq%
> ! Undefined control sequence.
> \close@pdflink ->\Hy@endcolorlink 
>   \Hy@VerboseLinkStop \pdfendlink 
> l.314 ...e}}Restoration\endNode{}\endSeq{}\endLink
>   {}\Seq%
> ! Undefined control sequence.
>  

Bug#978681: +pending

[Domenico Andreoli]

set -1 +pending
thanks

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05

Processed: retitle 947272 to blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error: argument 'argv' doesn't match prototype

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 947272 blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error: argument 
> 'argv' doesn't match prototype
Bug #947272 [src:blt] blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
Changed Bug title to 'blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error: argument 
'argv' doesn't match prototype' from 'blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): 
error:'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
947272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Roger Shimizu]

On Wed, Dec 30, 2020 at 3:46 AM Hans-Christoph Steiner  wrote:
>
> Ok, I fixed the dependency issue, now it gets reliably to the point rosh
> gets to:

Thanks for fixing the build dependency issue!
I fixed a few other issues (operator script & mterp generation, etc),
and pushed to rosh/refine branch.

Current build breaking point is the same as previous one.
I tried to use different c++ library, such as libstdc++-8-dev, and
clang-9, but seems no help.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#947272: blt builds fine with gcc-10

[Sergei Golovan]

retitle 947272 blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
argument 'argv' doesn't match prototype
severity 947272 serious
thanks

Hi Holger!

This bug is actually about blt 2.5.3+dfsg-5 and failure to build with
Tcl/Tk 8.7. So the serious severity is justified. The bug title is
misleading though, so I'm changing it. Sorry for not doing it sooner.

On Wed, Dec 30, 2020 at 5:06 PM Holger Levsen  wrote:
>
> control: severity -1 important
> thanks
>
> Hi Andreas,
>
> it seems blt builds fine with gcc-10 as can be seen from the recent upload,
> so I'm downgrading the severity and am wondering if we should actually close
> this bug (=ftbfs with gcc-9). What do you think?
>
>
> --
> cheers,
> Holger
>
>  ⢀⣴⠾⠻⢶⣦⠀
>  ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
>  ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
>  ⠈⠳⣄
>
> Dance like no one's watching. Encrypt like everyone is.



-- 
Sergei Golovan

Bug#978382: Fwd: The phpMyAdmin package needs a review on a merge request

[David Prévot]

Hi William,

I indeed missed your call for help on Debian-Devel, sorry about it and 
thank you for forwarding it to me quickly. I’m adding the Debian PHP 
PEAR (and Composer) Maintainers list in the hope someone may join the 
effort (and thus copying your whole message after mine to provide the 
full context).


That answers my recent questions on #978382 (CCed): it’s probably not 
worth investigating time and efforts fixing hundreds of PHPUnit 9 
related issues, since the latest PHPMyAdmin upstream is declared 
compatible with PHPUnit 9 (and PHP 8). Better get the latest PHPMyAdmin 
upstream version in shape for Debian inclusion ASAP (winter^W the freeze 
is coming).


Cheers

David

Le 30/12/2020 à 06:33, William Desportes a écrit :

Hi,

I am forwarding the email to you because I am into a critical situation 
where I need to make the next version of phpMyAdmin enter Debian to 
replace 4.9.x


I lack reviews and would need some expert eyeballs to have a look to 
https://salsa.debian.org/phpmyadmin-team/phpmyadmin/-/merge_requests/30 


I hope you can help me :)

Known issues:
- Metro theme has some fonts that I found out after another dev told me 
Apache2 was not GPL2 compatible as beeing Apache2 files (extreme 
possible solution: drop the theme on Debian): 
https://github.com/phpmyadmin/phpmyadmin/pull/16547


- 1 or 2 js files could be linked to Debian packages but nothing very 
important


Please let me know what you think about that

Kind regards,
William Desportes from the phpMyAdmin team

 Forwarded Message 
Subject: The phpMyAdmin package needs a review on a merge request
Date: Wed, 2 Dec 2020 08:07:46 + (UTC)
From: William Desportes 
To: debian-de...@lists.debian.org



Hi developers,
I am unsure about the format of my email but I decided to write here.
As a team member of phpMyAdmin and also of the packaging team I want to 
have the latest version packaged.


Currently 4.9 is in Debian, I prepared all the work for 5.0.

I am asking for the help to review my work, there is nothing 
particularly difficult in the diff. I am a new DM and need to be sure 
the changes I do are correct.


You can find the merge request here: 
https://salsa.debian.org/phpmyadmin-team/phpmyadmin/-/merge_requests/30


Feel free to comment or send approvals if you think the work is good to 
be integrated into Debian.


Tips: you can navigate to the debian/* files diffs using the hierarchy 
button on 
https://salsa.debian.org/phpmyadmin-team/phpmyadmin/-/merge_requests/30/diffs 



You can find all the branches duplicated and named {name}-5.x ready to 
be merged in {name}.


Kind regards,
William Desportes

Processed (with 1 error): Re: Bug#947272: blt builds fine with gcc-10

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 947272 blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
Bug #947272 [src:blt] blt: FTBFS with GCC 9: error: argument 'argv' doesn't 
match prototype
Changed Bug title to 'blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:' from 
'blt: FTBFS with GCC 9: error: argument 'argv' doesn't match prototype'.
> argument 'argv' doesn't match prototype
Unknown command or malformed arguments to command.
> severity 947272 serious
Bug #947272 [src:blt] blt: FTBFS with Tcl/Tk 8.7 (>= 8.7.0~a3): error:
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
947272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978419: marked as done (enablement symlinks are not cleaned up on upgrades)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 14:21:08 +
with message-id 
and subject line Bug#978427: fixed in ppp 2.4.8-1+2
has caused the Debian Bug report #978427,
regarding enablement symlinks are not cleaned up on upgrades
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ppp
Version: 2.4.8-1+1
Severity: normal

Hello,

the latest ppp update dropped the SysV init script and the systemd
service file.
Unfortunately, those are not properly cleaned up on upgrades:

# ls /etc/rc?.d/???pppd-dns
/etc/rcS.d/S11pppd-dns

# find /etc/systemd/system/ -name pppd-dns.service
/etc/systemd/system/multi-user.target.wants/pppd-dns.service

Those (now dangling) symlinks should be removed on upgrades.

To deregister those services, please use

update-rc.d -f pppd-dns remove
deb-systemd-helper purge pppd-dns.service

in postinst

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ppp depends on:
ii  libc6   2.31-6
ii  libcrypt1   1:4.4.17-1
ii  libpam-modules  1.3.1-5
ii  libpam-runtime  1.3.1-5
ii  libpam0g1.3.1-5
ii  libpcap0.8  1.9.1-4
ii  libssl1.1   1.1.1i-1
ii  libsystemd0 247.2-3
ii  procps  2:3.3.16-5

ppp recommends no packages.

ppp suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ppp
Source-Version: 2.4.8-1+2
Done: Chris Boot 

We believe that the bug you reported is fixed in the latest version of
ppp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Boot  (supplier of updated ppp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Dec 2020 13:49:46 +
Source: ppp
Architecture: source
Version: 2.4.8-1+2
Distribution: unstable
Urgency: medium
Maintainer: Chris Boot 
Changed-By: Chris Boot 
Closes: 968589 978427
Changes:
 ppp (2.4.8-1+2) unstable; urgency=medium
 .
   * Clean up correctly after pppd-dns init script and systemd unit removal.
 (Closes: #978427)
   * Don't touch resolv.conf when systemd-resolved is running.
 (Closes: #968589)
 .
   [ Samuel Thibault ]
   * Mark forwarded patches.
Checksums-Sha1:
 70bc92c99cbc979feb9e4458ca3df7a1f9ccd3b2 2287 ppp_2.4.8-1+2.dsc
 8c534406420d950367ab805ad7553f445c0a8c6c 117972 ppp_2.4.8-1+2.debian.tar.xz
Checksums-Sha256:
 ce4b7f7715df762a9b666bd7f75944b00f17254a6332f609a0fa1b0d79ae54cc 2287 
ppp_2.4.8-1+2.dsc
 03ed9d49507b339d17d837cdc96492ca245f083fa722c9ba8ecfe109af4cd6fd 117972 
ppp_2.4.8-1+2.debian.tar.xz
Files:
 dd52c3f38acb821381c3b4c74fe93ad5 2287 admin optional ppp_2.4.8-1+2.dsc
 d98edefc206151ceaaad6e16107de458 117972 admin optional 
ppp_2.4.8-1+2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKlBAEBCgCPFiEEakxNgo23DDPFqbsY1o29Dt2gqWQFAl/shjBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZB
NEM0RDgyOERCNzBDMzNDNUE5QkIxOEQ2OERCRDBFRERBMEE5NjQRHGJvb3RjQGRl
Ymlhbi5vcmcACgkQ1o29Dt2gqWQz7RAAlrVttE+uz1JpntdsYcsoqOhLxOKlFEJa
Ze6fLX8jKkZ3FK4XtrmdZU4bn1QeEqJL+VpJ7DJ8hWg67ylJg8Kts2EfbkXZQzs5
D7LcuHnTJtsN+soCnQM2L5aT309c3zjIoSpOGTSfvkC72zq3w0CCPjVhZ52SpHzM
Azdie1cyKmWGKTR0Kfgoc8YRQ3uAIioUsnknXpXYNrAik0pFVPRXCozL1I8qXjsV
0XU+qxbZXCqC1oOUR7+cK3TpyBhH6PZ0gloOY1h3m9AAGisLK6NI9H9NBf2YR5WO
3eUfoo+FP/Znab4qy31NrR+biPeKCy8k2V1jwxL/8CQ2z1pXXqp0/yWWk5RJqCKG
AYTTr+cP3ftI68txn6dXJDE/Jxixn1FDK+uWq4gdJZV0Ww2QBla41+OWXvCTxitS
t4vMKJlXHD6rOU6ONPEnVxBTGrdQd6z5h2J/zqbtWUT5mCbBQ7+zDiwsUzTSh+e5
yGKzthCp+f4qcmE9u5fHXs9ogwDsZYE8j/SyR5/Hk6VnTbMan7NikooAyY9/gkSy

Bug#978427: marked as done (ppp: Updates create a copy of /lib/systemd/system/pppd-dns.service and dangling symlink)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 14:21:08 +
with message-id 
and subject line Bug#978427: fixed in ppp 2.4.8-1+2
has caused the Debian Bug report #978427,
regarding ppp: Updates create a copy of /lib/systemd/system/pppd-dns.service 
and dangling symlink
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ppp
Version: 2.4.8-1+1~exp1
Severity: serious

Hello,

On upgrade, I see dpkg telling me the following:

Obsolete conffile /lib/systemd/system/pppd-dns.service has been modified by you.
Saving as /lib/systemd/system/pppd-dns.service.dpkg-bak ...

Two problems here:

1) I never modified this file
2) This is not a conffile and the file should be removed by the package

In any case, if a user would need to modify a systemd .service file,
they would never modify the file in the (/usr)/lib hierarchy, but in
/etc.

Please drop the following line in ppp.maintscript (AFAIK, that should
never be called on files that are not conffiles):

rm_conffile /lib/systemd/system/pppd-dns.service 2.4.8-1+1~exp1~

Moreover, the package leave dangling symlink
(/etc/systemd/system/multi-user.target.wants/pppd-dns.service) as the
service was enabled before... There are also leftover in
/var/lib/systemd/deb-systemd-helper-enabled.

On update you should call the following commands to make sure all these
files are removed:

if dpkg --compare-versions "$2" le-nl "2.4.8-1+2~"; then
  rm -f /lib/systemd/system/pppd-dns.service.dpkg-bak
  deb-systemd-helper purge pppd-dns.service >/dev/null
  deb-systemd-helper unmask pppd-dns.service >/dev/null
fi

Kind regards,
Laurent Bigonville


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages ppp depends on:
ii  libc6   2.31-6
ii  libcrypt1   1:4.4.17-1
ii  libpam-modules  1.3.1-5
ii  libpam-runtime  1.3.1-5
ii  libpam0g1.3.1-5
ii  libpcap0.8  1.9.1-4
ii  libssl1.1   1.1.1i-1
ii  libsystemd0 247.2-3
ii  procps  2:3.3.16-5

ppp recommends no packages.

ppp suggests no packages.

-- Configuration Files:
/etc/chatscripts/gprs [Errno 13] Permission non accordée: 
'/etc/chatscripts/gprs'
/etc/chatscripts/pap [Errno 13] Permission non accordée: '/etc/chatscripts/pap'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ppp
Source-Version: 2.4.8-1+2
Done: Chris Boot 

We believe that the bug you reported is fixed in the latest version of
ppp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Boot  (supplier of updated ppp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Dec 2020 13:49:46 +
Source: ppp
Architecture: source
Version: 2.4.8-1+2
Distribution: unstable
Urgency: medium
Maintainer: Chris Boot 
Changed-By: Chris Boot 
Closes: 968589 978427
Changes:
 ppp (2.4.8-1+2) unstable; urgency=medium
 .
   * Clean up correctly after pppd-dns init script and systemd unit removal.
 (Closes: #978427)
   * Don't touch resolv.conf when systemd-resolved is running.
 (Closes: #968589)
 .
   [ Samuel Thibault ]
   * Mark forwarded patches.
Checksums-Sha1:
 70bc92c99cbc979feb9e4458ca3df7a1f9ccd3b2 2287 ppp_2.4.8-1+2.dsc
 8c534406420d950367ab805ad7553f445c0a8c6c 117972 ppp_2.4.8-1+2.debian.tar.xz
Checksums-Sha256:
 ce4b7f7715df762a9b666bd7f75944b00f17254a6332f609a0fa1b0d79ae54cc 2287 
ppp_2.4.8-1+2.dsc
 03ed9d49507b339d17d837cdc96492ca245f083fa722c9ba8ecfe109af4cd6fd 117972 
ppp_2.4.8-1+2.debian.tar.xz
Files:
 dd52c3f38acb821381c3b4c74fe93ad5 2287 admin optional ppp_2.4.8-1+2.dsc
 

Bug#978704: securefs: autopkgtests hard-code dependency on libcrypto++6

[Sebastian Ramacher]

On 2020-12-30 15:06:19 +0100, Sebastian Ramacher wrote:
> Source: securefs
> Version: 0.11.1+ds-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> securefs' autopkgtests hard-code dependencies on a bunch of shared
> libraries: libcrypto++6, libfuse2, libjsoncpp1, and libutf8profc2. This
> is most certainly wrong when securefs is rebuilt for transitions. At
> least the dependencies on libcrypto++6 and libjsoncpp1 are no longer
> correct.
> 
> Having dependencies on the -dev packages there or installing securefs
> would make more sense to get the right runtime libraries.

On second thought, installing securefs could also give the wrong
results. So the former would make more sense. In any case, this issue
causes autopkgtest failures:

autopkgtest [05:13:56]: test command2: cd obj-x86_64-linux-gnu && 
./securefs_test
autopkgtest [05:13:56]: test command2: [---
./securefs_test: error while loading shared libraries: libcrypto++.so.8: cannot 
open shared object file: No such file or directory
autopkgtest [05:13:56]: test command2: ---]
autopkgtest [05:13:56]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 127

See
https://ci.debian.net/data/autopkgtest/testing/amd64/s/securefs/9241910/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#978704: securefs: autopkgtests hard-code dependency on libcrypto++6

[Sebastian Ramacher]

Source: securefs
Version: 0.11.1+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

securefs' autopkgtests hard-code dependencies on a bunch of shared
libraries: libcrypto++6, libfuse2, libjsoncpp1, and libutf8profc2. This
is most certainly wrong when securefs is rebuilt for transitions. At
least the dependencies on libcrypto++6 and libjsoncpp1 are no longer
correct.

Having dependencies on the -dev packages there or installing securefs
would make more sense to get the right runtime libraries.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: blt builds fine with gcc-10

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #947272 [src:blt] blt: FTBFS with GCC 9: error: argument 'argv' doesn't 
match prototype
Severity set to 'important' from 'serious'

-- 
947272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#947272: blt builds fine with gcc-10

[Holger Levsen]

control: severity -1 important
thanks

Hi Andreas,

it seems blt builds fine with gcc-10 as can be seen from the recent upload,
so I'm downgrading the severity and am wondering if we should actually close
this bug (=ftbfs with gcc-9). What do you think?


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

Dance like no one's watching. Encrypt like everyone is.


signature.asc
Description: PGP signature

Bug#976544: marked as done (fontconfig: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 15:05:09 +0100
with message-id <73cfacdd-ac1d-3019-1fa2-741771d9f...@web.de>
and subject line Build failure solved
has caused the Debian Bug report #976544,
regarding fontconfig: FTBFS: latex errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontconfig
Version: 2.13.1-4.2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc'
> gcc -DHAVE_CONFIG_H -I. -I..  -c -o edit-sgml.o edit-sgml.c
> sed -e 's,@CONFDIR\@,,' ./confdir.sgml.in | awk '{if (NR > 1) printf("\n"); 
> printf("%s", $0);}' > confdir.sgml
> rm -f fonts-conf.5; \
> docbook2man local-fontconfig-user.sgml && \
> rm -f manpage.*
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/doc/local-fontconfig-user.sgml
> gcc -o edit-sgml edit-sgml.o   
> rm -f fcatomic.sgml; \
> ./edit-sgml ./func.sgml < './fcatomic.fncs' > fcatomic.sgml
> rm -f fcblanks.sgml; \
> ./edit-sgml ./func.sgml < './fcblanks.fncs' > fcblanks.sgml
> rm -f fccache.sgml; \
> ./edit-sgml ./func.sgml < './fccache.fncs' > fccache.sgml
> rm -f fccharset.sgml; \
> ./edit-sgml ./func.sgml < './fccharset.fncs' > fccharset.sgml
> rm -f fcconfig.sgml; \
> ./edit-sgml ./func.sgml < './fcconfig.fncs' > fcconfig.sgml
> rm -f fcconstant.sgml; \
> ./edit-sgml ./func.sgml < './fcconstant.fncs' > fcconstant.sgml
> rm -f fcdircache.sgml; \
> ./edit-sgml ./func.sgml < './fcdircache.fncs' > fcdircache.sgml
> rm -f fcfile.sgml; \
> ./edit-sgml ./func.sgml < './fcfile.fncs' > fcfile.sgml
> rm -f fcfontset.sgml; \
> ./edit-sgml ./func.sgml < './fcfontset.fncs' > fcfontset.sgml
> rm -f fcformat.sgml; \
> ./edit-sgml ./func.sgml < './fcformat.fncs' > fcformat.sgml
> rm -f fcfreetype.sgml; \
> ./edit-sgml ./func.sgml < './fcfreetype.fncs' > fcfreetype.sgml
> rm -f fcinit.sgml; \
> ./edit-sgml ./func.sgml < './fcinit.fncs' > fcinit.sgml
> rm -f fclangset.sgml; \
> ./edit-sgml ./func.sgml < './fclangset.fncs' > fclangset.sgml
> rm -f fcmatrix.sgml; \
> ./edit-sgml ./func.sgml < './fcmatrix.fncs' > fcmatrix.sgml
> rm -f fcobjectset.sgml; \
> ./edit-sgml ./func.sgml < './fcobjectset.fncs' > fcobjectset.sgml
> rm -f fcobjecttype.sgml; \
> ./edit-sgml ./func.sgml < './fcobjecttype.fncs' > fcobjecttype.sgml
> rm -f fcpattern.sgml; \
> ./edit-sgml ./func.sgml < './fcpattern.fncs' > fcpattern.sgml
> rm -f fcrange.sgml; \
> ./edit-sgml ./func.sgml < './fcrange.fncs' > fcrange.sgml
> rm -f fcstring.sgml; \
> ./edit-sgml ./func.sgml < './fcstring.fncs' > fcstring.sgml
> rm -f fcstrset.sgml; \
> ./edit-sgml ./func.sgml < './fcstrset.fncs' > fcstrset.sgml
> rm -f fcvalue.sgml; \
> ./edit-sgml ./func.sgml < './fcvalue.fncs' > fcvalue.sgml
> rm -f fcweight.sgml; \
> ./edit-sgml ./func.sgml < './fcweight.fncs' > fcweight.sgml
> rm -f func.refs; \
> docbook2man -o devel-man local-fontconfig-devel.sgml && \
> mv devel-man/manpage.refs func.refs &&\
> mv devel-man/*.3 . && \
> rm -f devel-man/manpage.* &&  \
> rmdir devel-man || rm func.refs || :
> rm -f fontconfig-user.txt; \
> docbook2txt fontconfig-user.sgml
> rm -f fontconfig-devel.txt; \
> docbook2txt fontconfig-devel.sgml
> Done.
> rm -f fontconfig-user.pdf; \
> docbook2pdf fontconfig-user.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#html
> Working on: /<>/doc/fontconfig-user.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#html
> Working on: /<>/doc/fontconfig-devel.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/doc/local-fontconfig-devel.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/doc/fontconfig-user.sgml
> Done.
> rm -f fontconfig-devel.pdf; \
> docbook2pdf fontconfig-devel.sgml
> Using catalogs: /etc/sgml/catalog
> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> Working on: /<>/doc/fontconfig-devel.sgml
> Done.
> rm -f fontconfig-user.html; \
> docbook2html -u fontconfig-user.sgml > fontconfig-user.html
> rm -f -r fontconfig-devel; \
> 

Bug#911464: marked as done (free42-nologo: Numbers entered incorrectly on arm architectures)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 13:48:49 +
with message-id 
and subject line Bug#911464: fixed in free42-nologo 2.5.22+ds-1
has caused the Debian Bug report #911464,
regarding free42-nologo: Numbers entered incorrectly on arm architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
911464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: free42-nologo
Version: 1.4.77-1.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

entering numbers in free42-nologo does not work on armhf and arm64 
architectures (but does work as expected on i386 and amd64).

I would expect that typing [1][0][enter] would have the (decimal) number 10 in 
the x register and on the display.
While this works on i386 ans amd64 versions, arm versions behave different:

1 -> 1
2 -> 2
9 -> 9
10 -> 16
11 -> 16
16 -> 16
17 -> 17
19 -> 19
20 -> 32
21 -> 32
31 -> 32
33 -> 33
39 -> 39
40 -> 64

You get the idea.
Not being able to enter numbers correctly renders the calculator unusable.

regards
Alan

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 4.4.154 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages free42-nologo depends on:
ii  libc6   2.27-6
ii  libgcc1 1:8.2.0-7
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-6
ii  libglib2.0-02.58.1-2
ii  libgtk2.0-0 2.24.32-3
ii  libstdc++6  8.2.0-7
ii  libx11-62:1.6.7-1
ii  libxmu6 2:1.1.2-2

free42-nologo recommends no packages.

free42-nologo suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: free42-nologo
Source-Version: 2.5.22+ds-1
Done: Stephen Kitt 

We believe that the bug you reported is fixed in the latest version of
free42-nologo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated free42-nologo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Dec 2020 14:31:19 +0100
Source: free42-nologo
Architecture: source
Version: 2.5.22+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Stalp 
Changed-By: Stephen Kitt 
Closes: 775598 775599 775601 911464 959420 967351
Changes:
 free42-nologo (2.5.22+ds-1) unstable; urgency=medium
 .
   [ Christian Stalp ]
   * New upstream release (Closes: #775601, #911464)
   * debian/patches:
 - delete patch fix-free42-makefile.patch, no longer applicable
 - delete patch hash-style-makefile.patch, no longer applicable
 - update patch gcc6 to new Makefile
 - adding new patch libbidgc to build package with intelrdfpmath
 .
   * debian/control
 - changing Build-Depends libgtk2.0-dev to libgtk-3-dev (Closes: #967351)
 - adding libintelrdfpmath-dev to Build-Depends
 .
   * debian/rules
 - adapting rules file to new icon names (icon.xpm to icon-48x48.xpm)
 .
   [ Stephen Kitt ]
   * Add myself to Uploaders. (Closes: #959420.)
   * Use the secure homepage URL.
   * Switch to debhelper compatibility level 13.
   * Point to the Salsa repository.
   * Set “Rules-Requires-Root: no”.
   * Remove debian/patches/gcc6.patch which is no longer necessary.
   * Standards-Version 4.5.1, no further change required.
   * Enable support for ALSA audio. (Closes: #775598.)
   * Install the decimal variant. (Closes: #775599.)
   * Ensure build flags are applied.
   * Install desktop files instead of a menu entry.
   * Drop obsolete X11 build dependencies.
Checksums-Sha1:
 e015f0860e3bc2f49b72553e7b38aa38570de604 2002 free42-nologo_2.5.22+ds-1.dsc
 3c4f86be8303c19f21202ef8d3ef59f865554cbb 424492 
free42-nologo_2.5.22+ds.orig.tar.xz
 2e9960bda965428dd74ffc6ed812d8a7494a7b06 4780 

Processed: (No Subject)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 977246 fixed-upstream
Bug #977246 [lutris] lutris should depend on python3-dbus
Added tag(s) fixed-upstream.
> tags 978557 fixed-upstream
Bug #978557 [lutris] lutris: Add German translation
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
977246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977246
978557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978517: marked as done (seqan3: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 12:33:36 +
with message-id 
and subject line Bug#978517: fixed in seqan3 3.0.2+ds-6
has caused the Debian Bug report #978517,
regarding seqan3: non-standard gcc/g++ used for build (gcc-9)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seqan3
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: seqan3
Source-Version: 3.0.2+ds-6
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
seqan3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated seqan3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Dec 2020 11:55:26 +0100
Source: seqan3
Architecture: source
Version: 3.0.2+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 978517
Changes:
 seqan3 (3.0.2+ds-6) unstable; urgency=medium
 .
   * Try again with default gcc (gcc-10). Closes: #978517
Checksums-Sha1:
 8832d0a9dae33f0ed078cdbd24f84b39e82cb969 2477 seqan3_3.0.2+ds-6.dsc
 97630e51b5d7517ecbf65e8902915485c80264e8 10708 seqan3_3.0.2+ds-6.debian.tar.xz
 bbd1e1900a62a9d4519f292619cef1f999794db8 13631 
seqan3_3.0.2+ds-6_source.buildinfo
Checksums-Sha256:
 5a53281ab01db8825bcedcf73382639350dd8727a9530c3bd8d41e58d5fe4f59 2477 
seqan3_3.0.2+ds-6.dsc
 4eaa542e48e3ce36ab3ebfd904f035be79eddff14a86e8fbb6c5dc28c6bf5d0e 10708 
seqan3_3.0.2+ds-6.debian.tar.xz
 7787e40b3d6baaaccda7db07cbefd92214684b4a891048b126556aec9eea42bd 13631 
seqan3_3.0.2+ds-6_source.buildinfo
Files:
 51dbef0489341cb1e291331a7d1969c6 2477 science optional seqan3_3.0.2+ds-6.dsc
 2fda51e8c32c118727dd7bec1089a721 10708 science optional 
seqan3_3.0.2+ds-6.debian.tar.xz
 e73cef985b2fc759a45bd0351ad01a6c 13631 science optional 
seqan3_3.0.2+ds-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl/sbmIACgkQPCZ2P2xn
5uITExAAnA5YDLK8IRVvLU2bMYd4mPWwY+18npZ2vNT+esgYcqXPhMtzi+q/iVnR
z+eGHjKV6ORaynwULHa1PLYiUOhYYJu9uL4bFfK9GzylObbCTSUtAiBXSV/bqljf
SXlmXmK5zbg4enQMN5yK3MvsF0ixFpuuIPqQUftMNSzahDXSS1s/XWhH0yD8MskV
kbUvR3G0IsOoQZmQ6WRDyAgYlLANDtB3yO8oE3yd8xWzENqabT9gPfrvXq6CBKmw
X+GK+r4f4qBdXKxRGCmC9eqKUIdayMaa56sCpvclsO+H2u9QR+9mYnsfu2ExKcfw
xlmsm8y36UM/rasq8C+4GHaRS9+hIrYROvdzL91uC0WZ8AYooUB7UN5syhwDpNZf
SKh+ImL7Dl6ZhWh7Kqk0vORfxa4hJdr3AvvGdRNq7EotOtnfTXoFJsMSACcqC5tZ
V6vf0hlAkv8QwCOtO3WSZzcwQCseUmNQkKP8zuLhCsrkdJxzapqxBCiyYLYDtZm+
T8Vul6td3hfY84G1oqGbsDJYTiBTIYwXtjAUhEnE6B6s1QM/qqkewBOKjz2shA20
LmAQ8KH7X4gaU5D21jqSwWqmG4PLBOCUqpcP+0dBU1207dvKRb2XWX9pyDkg9H+u
PUBhN9KgqH9fxDyGsDy2nVnYeZFqSranyPyynwQozvO/y31kmkQ=
=J/YH
-END PGP SIGNATURE End Message ---

Bug#978657: unknown-horizons: Crash on startup with xml AttributeError "no attribute 'getchildren'"

[Simon McVittie]

Control: reassign -1 python3-fife 0.4.2-2
Control: affects -1 + unknown-horizons

On Tue, 29 Dec 2020 at 20:54:44 +0100, Steffen Langenbach wrote:
> I encountered a problem starting unknown-horizons.
...
>   File "/usr/lib/python3/dist-
> packages/fife/extensions/serializers/simplexml.py", line 386, in _validateTree
> for c in self._root_element.getchildren():
> AttributeError: 'xml.etree.ElementTree.Element' object has no attribute
> 'getchildren'

This looks like an incompatibility between fife and Python 3.9, similar to
. The getchildren method was removed
from xml.etree in the Python 3.9 standard library, and fife probably
needs to use "for c in self._root_element:" instead.

smcv

Processed: Re: Bug#978657: unknown-horizons: Crash on startup with xml AttributeError "no attribute 'getchildren'"

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-fife 0.4.2-2
Bug #978657 [unknown-horizons] unknown-horizons: Crash on startup with xml 
AttributeError "no attribute 'getchildren'"
Bug reassigned from package 'unknown-horizons' to 'python3-fife'.
No longer marked as found in versions unknown-horizons/2019.1-2.
Ignoring request to alter fixed versions of bug #978657 to the same values 
previously set
Bug #978657 [python3-fife] unknown-horizons: Crash on startup with xml 
AttributeError "no attribute 'getchildren'"
Marked as found in versions fife/0.4.2-2.
> affects -1 + unknown-horizons
Bug #978657 [python3-fife] unknown-horizons: Crash on startup with xml 
AttributeError "no attribute 'getchildren'"
Added indication that 978657 affects unknown-horizons

-- 
978657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978675: libsys-hostname-long-perl: FTBFS, tests fail

[Holger Levsen]

hi Axel,

On Wed, Dec 30, 2020 at 06:12:55AM +0100, Axel Beckert wrote:
> gregoa: I'll leave up to you if you already want to close the bug
> report or not. Feel free to replace my fixed tag with a pending tag or
> so.

I've already closed the bug :)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

There are only two kinds of nazis: stupid ones and those without an excuse.
(Volker Strübing)


signature.asc
Description: PGP signature

Bug#978675: marked as done (libsys-hostname-long-perl: FTBFS, tests fail)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 10:06:08 +
with message-id <20201230100608.gb6...@layer-acht.org>
and subject line Re: Bug#978675: Acknowledgement (libsys-hostname-long-perl: 
FTBFS, tests fail)
has caused the Debian Bug report #978675,
regarding libsys-hostname-long-perl: FTBFS, tests fail
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
978675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsys-hostname-long-perl
Version: 1.5-1
Severity: serious

Dear Maintainer,

when trying to build libsys-hostname-long-perl in current sid it fails:

I: Building the package
I: Running cd /build/libsys-hostname-long-perl-1.5/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent" 
dpkg-buildpackage -us -uc
dpkg-buildpackage: info: source package libsys-hostname-long-perl
dpkg-buildpackage: info: source version 1.5-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Axel Beckert 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in 
use)
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building libsys-hostname-long-perl using existing 
./libsys-hostname-long-perl_1.5.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building libsys-hostname-long-perl in 
libsys-hostname-long-perl_1.5-1.debian.tar.xz
dpkg-source: info: building libsys-hostname-long-perl in 
libsys-hostname-long-perl_1.5-1.dsc
 debian/rules build
dh build
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/build/libsys-hostname-long-perl-1.5=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 
-fdebug-prefix-map=/build/libsys-hostname-long-perl-1.5=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Sys::Hostname::Long
Writing MYMETA.yml and MYMETA.json
   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1
make[1]: Entering directory '/build/libsys-hostname-long-perl-1.5'
cp testall.pl blib/lib/Sys/Hostname/testall.pl
cp lib/Sys/Hostname/Long.pm blib/lib/Sys/Hostname/Long.pm
Manifying 1 pod document
make[1]: Leaving directory '/build/libsys-hostname-long-perl-1.5'
   dh_auto_test
dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/build/libsys-hostname-long-perl-1.5'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" 
t/
hostname: Temporary failure in name resolution
t/local.t ..
1..1
# Running under perl version 5.032000 for linux
# Current time local: Tue Dec 29 23:17:35 2020
# Current time GMT:   Tue Dec 29 23:17:35 2020
# Using Test.pm version 1.31
not ok 1
Your hostname =
Failed 1/1 subtests
Sys::Hostname::Long - Last Dispatch method = ip at 
/build/libsys-hostname-long-perl-1.5/blib/lib/Sys/Hostname/Long.pm line 206.
Use of uninitialized value $hostname in string ne at t/local.t line 10.
# Failed test 1 in t/local.t at line 10
#  t/local.t line 10 is: ok($hostname ne "");
Use of uninitialized value $hostname in concatenation (.) or string at 
t/local.t line 12.

Test Summary Report
---
t/local.t (Wstat: 0 Tests: 1 Failed: 1)
  Failed test:  1
Files=1, Tests=1,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.04 cusr  0.00 
csys =  0.07 CPU)
Result: FAIL
make[1]: Leaving directory '/build/libsys-hostname-long-perl-1.5'
Failed 1/1 test programs. 1/1 subtests failed.
make[1]: *** [Makefile:830: test_dynamic] Error 255
dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2
make: *** [debian/rules:4: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I: copying local configuration
E: Failed 

Processed: tagging 911464

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 911464 + pending
Bug #911464 [free42-nologo] free42-nologo: Numbers entered incorrectly on arm 
architectures
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
911464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 977604 to fails to compile templates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 977604 fails to compile templates
Bug #977604 [smarty3] smarty3: broken internal parsetree code
Changed Bug title to 'fails to compile templates' from 'smarty3: broken 
internal parsetree code'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
977604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#975803: marked as done (lnav: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 09:18:39 +
with message-id 
and subject line Bug#975803: fixed in lnav 0.9.0-1
has caused the Debian Bug report #975803,
regarding lnav: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned 
exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lnav
Version: 0.8.5-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/<>/test'
> PASS: test_abbrev
> PASS: test_ansi_scrubber
> PASS: test_auto_fd
> PASS: test_auto_mem
> PASS: test_bookmarks
> PASS: test_date_time_scanner
> PASS: test_format_installer.sh
> PASS: test_cli.sh
> PASS: lnav_doctests
> PASS: test_line_buffer2
> PASS: test_format_loader.sh
> FAIL: test_listview.sh
> PASS: test_grep_proc.sh
> PASS: test_grep_proc2
> PASS: test_meta.sh
> PASS: test_json_op.sh
> PASS: test_json_ptr_walk.sh
> PASS: test_log_accel
> PASS: test_json_format.sh
> PASS: test_pcrepp
> PASS: test_reltime
> PASS: test_scripts.sh
> PASS: test_shlexer.sh
> PASS: test_sql_coll_func.sh
> PASS: test_sessions.sh
> PASS: test_sql_json_func.sh
> PASS: test_sql_fs_func.sh
> PASS: test_sql_time_func.sh
> PASS: test_sql_str_func.sh
> PASS: test_yajlpp
> PASS: test_pretty_print.sh
> PASS: test_curl.sh
> PASS: test_data_parser.sh
> PASS: test_cmds.sh
> PASS: test_line_buffer.sh
> =
>lnav 0.8.5: test/test-suite.log
> =
> 
> # TOTAL: 35
> # PASS:  34
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test_listview.sh
> ==
> 
> Listview doesn't start down one line?
> FAIL test_listview.sh (exit status: 1)
> 
> 
> Testsuite summary for lnav 0.8.5
> 
> # TOTAL: 35
> # PASS:  34
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> Please report to l...@googlegroups.com
> 
> make[4]: *** [Makefile:1347: test-suite.log] Error 1
> make[4]: Leaving directory '/<>/test'
> make[3]: *** [Makefile:1455: check-TESTS] Error 2
> make[3]: Leaving directory '/<>/test'
> make[2]: *** [Makefile:1767: check-am] Error 2
> make[2]: Leaving directory '/<>/test'
> make[1]: *** [Makefile:471: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/lnav_0.8.5-3_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!

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.
--- End Message ---
--- Begin Message ---
Source: lnav
Source-Version: 0.9.0-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
lnav, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated lnav package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Dec 2020 10:01:56 +0100
Source: lnav
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Salvatore Bonaccorso 
Changed-By: Salvatore Bonaccorso 
Closes: 975803
Changes:
 lnav (0.9.0-1) unstable; urgency=medium
 .
   * New upstream version 0.9.0
   * 

Processed: Bug#975803 marked as pending in lnav

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975803 [src:lnav] lnav: FTBFS: dh_auto_test: error: make -j4 check 
VERBOSE=1 returned exit code 2
Added tag(s) pending.

-- 
975803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#975803: marked as pending in lnav

[Salvatore Bonaccorso]

Control: tag -1 pending

Hello,

Bug #975803 in lnav reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/carnil/lnav/-/commit/ea9faa66577f735c6d97d7c61fe9c0329f6fd538


Disable broken test_listview.sh test in testsuite

Closes: #975803


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975803

Bug#977927: marked as done (DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id 
and subject line Bug#977926: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977926,
regarding DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.3.0-1
Severity: important

Dear Maintainer,

In a fresh container with Debian testing, running mitmproxy with any
arguments produces the following output:

Traceback (most recent call last):
  File "/usr/bin/mitmproxy", line 33, in 
sys.exit(load_entry_point('mitmproxy==5.3.0', 'console_scripts', 
'mitmproxy')())
  File "/usr/bin/mitmproxy", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/mitmproxy/tools/main.py", line 22, in 

from ._main import *  # noqa
  File "/usr/lib/python3/dist-packages/mitmproxy/tools/_main.py", line 14, in 

from mitmproxy import exceptions, master
  File "/usr/lib/python3/dist-packages/mitmproxy/master.py", line 7, in 
from mitmproxy import addonmanager
  File "/usr/lib/python3/dist-packages/mitmproxy/addonmanager.py", line 8, in 

from mitmproxy import eventsequence
  File "/usr/lib/python3/dist-packages/mitmproxy/eventsequence.py", line 4, in 

from mitmproxy import flow
  File "/usr/lib/python3/dist-packages/mitmproxy/flow.py", line 5, in 
from mitmproxy import connections
  File "/usr/lib/python3/dist-packages/mitmproxy/connections.py", line 9, in 

from mitmproxy.net import tcp
  File "/usr/lib/python3/dist-packages/mitmproxy/net/tcp.py", line 12, in 

from mitmproxy.net import tls
  File "/usr/lib/python3/dist-packages/mitmproxy/net/tls.py", line 17, in 

from mitmproxy.contrib.kaitaistruct import tls_client_hello
  File 
"/usr/lib/python3/dist-packages/mitmproxy/contrib/kaitaistruct/tls_client_hello.py",
 line 7, in 
from pkg_resources import parse_version
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3239, 
in 
def _initialize_master_working_set():
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3222, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3251, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 567, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 884, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 770, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was not 
found and is required by mitmproxy

The mitmproxy package appears to be missing the following dependencies:
python3-hyperframe (>= 6.0)
python3-h2 (>= 4.0)

After installing these packages, mitmproxy appears to work correctly.

Thanks,
Kevin

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

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

Versions of packages mitmproxy depends on:
ii  dpkg  1.20.5
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-4
ii  python3   3.9.0-4
ii  python3-asgiref   3.3.1-1
ii  python3-blinker   1.4+dfsg1-0.3
ii  python3-brotli1.0.9-2+b2
ii  python3-certifi   2020.6.20-1
ii  

Bug#977927: marked as done (DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id 
and subject line Bug#977927: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977927,
regarding DistributionNotFound: 'hyperframe>=6.0' due to missing dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.3.0-1
Severity: important

Dear Maintainer,

In a fresh container with Debian testing, running mitmproxy with any
arguments produces the following output:

Traceback (most recent call last):
  File "/usr/bin/mitmproxy", line 33, in 
sys.exit(load_entry_point('mitmproxy==5.3.0', 'console_scripts', 
'mitmproxy')())
  File "/usr/bin/mitmproxy", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/mitmproxy/tools/main.py", line 22, in 

from ._main import *  # noqa
  File "/usr/lib/python3/dist-packages/mitmproxy/tools/_main.py", line 14, in 

from mitmproxy import exceptions, master
  File "/usr/lib/python3/dist-packages/mitmproxy/master.py", line 7, in 
from mitmproxy import addonmanager
  File "/usr/lib/python3/dist-packages/mitmproxy/addonmanager.py", line 8, in 

from mitmproxy import eventsequence
  File "/usr/lib/python3/dist-packages/mitmproxy/eventsequence.py", line 4, in 

from mitmproxy import flow
  File "/usr/lib/python3/dist-packages/mitmproxy/flow.py", line 5, in 
from mitmproxy import connections
  File "/usr/lib/python3/dist-packages/mitmproxy/connections.py", line 9, in 

from mitmproxy.net import tcp
  File "/usr/lib/python3/dist-packages/mitmproxy/net/tcp.py", line 12, in 

from mitmproxy.net import tls
  File "/usr/lib/python3/dist-packages/mitmproxy/net/tls.py", line 17, in 

from mitmproxy.contrib.kaitaistruct import tls_client_hello
  File 
"/usr/lib/python3/dist-packages/mitmproxy/contrib/kaitaistruct/tls_client_hello.py",
 line 7, in 
from pkg_resources import parse_version
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3239, 
in 
def _initialize_master_working_set():
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3222, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3251, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 567, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 884, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 770, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was not 
found and is required by mitmproxy

The mitmproxy package appears to be missing the following dependencies:
python3-hyperframe (>= 6.0)
python3-h2 (>= 4.0)

After installing these packages, mitmproxy appears to work correctly.

Thanks,
Kevin

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

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

Versions of packages mitmproxy depends on:
ii  dpkg  1.20.5
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-4
ii  python3   3.9.0-4
ii  python3-asgiref   3.3.1-1
ii  python3-blinker   1.4+dfsg1-0.3
ii  python3-brotli1.0.9-2+b2
ii  python3-certifi   2020.6.20-1
ii  

Bug#977926: marked as done (Missing required dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id 
and subject line Bug#977927: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977927,
regarding Missing required dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.3.0-1
Severity: grave

Installing mitmproxy in a clean sid chroot, and running it (with no arguments)
results into a large backtrace that ends with...
  pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was 
not found and is required by mitmproxy

After installing the package python3-hyperframe, the error becomes:
  pkg_resources.DistributionNotFound: The 'h2>=4.0' distribution was not found 
and is required by mitmproxy
...in turn fixed by installing the package python3-h2.

It looks like at least those two dependencies are missing, preventing
the package from working out of the box in any configuration. Both of
these were in the Depends for the 4.0.4-5 version (buster's).

I did not check whether other features require more dependencies, as I'm
not too familiar with all of mitmproxy's operation modes.

Regards,
Faidon
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 5.3.0-2
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
mitmproxy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mitmproxy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Dec 2020 09:51:56 +0100
Source: mitmproxy
Architecture: source
Version: 5.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andrej Shadura 
Closes: 977926 977927
Changes:
 mitmproxy (5.3.0-2) unstable; urgency=medium
 .
   * Pre-wrap dependencies of the binary package.
   * Fix the dependencies of the binary package (Closes: #977926, #977927)
   * Drop an explicit dependency on h11, wsproto depends on it already.
Checksums-Sha1:
 059a438544dcf617dacf26e7392cad58db4c3d92 2708 mitmproxy_5.3.0-2.dsc
 e809d69349b0137fda550ddf4e9164a37e4c8169 11856 mitmproxy_5.3.0-2.debian.tar.xz
Checksums-Sha256:
 c2fd57e9aed352ed4234e4e19711673141667ed2333a4537881c1973c00ccb85 2708 
mitmproxy_5.3.0-2.dsc
 abc1c71780480c92415e65d247896170532152b6008e90edf2c6bf6cc3831448 11856 
mitmproxy_5.3.0-2.debian.tar.xz
Files:
 aa62148b29e71506db547c46e2c3c72f 2708 net optional mitmproxy_5.3.0-2.dsc
 612cdaaa85a4bef2d3fe3a4657493911 11856 net optional 
mitmproxy_5.3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/sP98ACgkQXkCM2RzY
OdJuRgf/XNw0EtFGvBWIdpZneWTRcY3LYZfsya2dC0vhZvVdC/txZtaIE48Kw+hA
m+7xqZDcn7QQZYbeGC23ShfooYGO1u/tATDMBagp0BWz9Iz+YKvDlDtgbsgNZEW7
mDeh0jVegfKbE1mcG2gtUfQ66X5cf6+pRomD8bkd1/UoZbNzuadRLzu4QVY7n0eS
4LtdfRuClCP36rKPTs3XhtFZcESTIC6BabBjBGq7rT3cfW6CC2vP2Y1TeAxdLg0C
fibekFkD8ejrRN98TgrJH6sD1TQQht5xjHuk/OYndCjVhslech/uqLq5K0b9Z8Vc
tQjoLEVIxFXUeSm0Vu+lerHMaDEaBA==
=42uc
-END PGP SIGNATURE End Message ---

Bug#977926: marked as done (Missing required dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 30 Dec 2020 09:03:48 +
with message-id 
and subject line Bug#977926: fixed in mitmproxy 5.3.0-2
has caused the Debian Bug report #977926,
regarding Missing required dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.3.0-1
Severity: grave

Installing mitmproxy in a clean sid chroot, and running it (with no arguments)
results into a large backtrace that ends with...
  pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was 
not found and is required by mitmproxy

After installing the package python3-hyperframe, the error becomes:
  pkg_resources.DistributionNotFound: The 'h2>=4.0' distribution was not found 
and is required by mitmproxy
...in turn fixed by installing the package python3-h2.

It looks like at least those two dependencies are missing, preventing
the package from working out of the box in any configuration. Both of
these were in the Depends for the 4.0.4-5 version (buster's).

I did not check whether other features require more dependencies, as I'm
not too familiar with all of mitmproxy's operation modes.

Regards,
Faidon
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 5.3.0-2
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
mitmproxy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mitmproxy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Dec 2020 09:51:56 +0100
Source: mitmproxy
Architecture: source
Version: 5.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andrej Shadura 
Closes: 977926 977927
Changes:
 mitmproxy (5.3.0-2) unstable; urgency=medium
 .
   * Pre-wrap dependencies of the binary package.
   * Fix the dependencies of the binary package (Closes: #977926, #977927)
   * Drop an explicit dependency on h11, wsproto depends on it already.
Checksums-Sha1:
 059a438544dcf617dacf26e7392cad58db4c3d92 2708 mitmproxy_5.3.0-2.dsc
 e809d69349b0137fda550ddf4e9164a37e4c8169 11856 mitmproxy_5.3.0-2.debian.tar.xz
Checksums-Sha256:
 c2fd57e9aed352ed4234e4e19711673141667ed2333a4537881c1973c00ccb85 2708 
mitmproxy_5.3.0-2.dsc
 abc1c71780480c92415e65d247896170532152b6008e90edf2c6bf6cc3831448 11856 
mitmproxy_5.3.0-2.debian.tar.xz
Files:
 aa62148b29e71506db547c46e2c3c72f 2708 net optional mitmproxy_5.3.0-2.dsc
 612cdaaa85a4bef2d3fe3a4657493911 11856 net optional 
mitmproxy_5.3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/sP98ACgkQXkCM2RzY
OdJuRgf/XNw0EtFGvBWIdpZneWTRcY3LYZfsya2dC0vhZvVdC/txZtaIE48Kw+hA
m+7xqZDcn7QQZYbeGC23ShfooYGO1u/tATDMBagp0BWz9Iz+YKvDlDtgbsgNZEW7
mDeh0jVegfKbE1mcG2gtUfQ66X5cf6+pRomD8bkd1/UoZbNzuadRLzu4QVY7n0eS
4LtdfRuClCP36rKPTs3XhtFZcESTIC6BabBjBGq7rT3cfW6CC2vP2Y1TeAxdLg0C
fibekFkD8ejrRN98TgrJH6sD1TQQht5xjHuk/OYndCjVhslech/uqLq5K0b9Z8Vc
tQjoLEVIxFXUeSm0Vu+lerHMaDEaBA==
=42uc
-END PGP SIGNATURE End Message ---

Processed: severity of 978686 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 978686 normal
Bug #978686 [src:dh-python] dh-python cannot parse python_version dependency
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
978686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unmerging 977926, cloning 977926, reassign -2 to src:dh-python ..., forcibly merging 977926 977927

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 977926
Bug #977926 [mitmproxy] Missing required dependencies
Bug #977927 [mitmproxy] DistributionNotFound: 'hyperframe>=6.0' due to missing 
dependencies
Disconnected #977926 from all other report(s).
> clone 977926 -2
Bug #977926 [mitmproxy] Missing required dependencies
Bug 977926 cloned as bug 978686
> reassign -2 src:dh-python
Bug #978686 [mitmproxy] Missing required dependencies
Bug reassigned from package 'mitmproxy' to 'src:dh-python'.
No longer marked as found in versions mitmproxy/5.3.0-1.
Ignoring request to alter fixed versions of bug #978686 to the same values 
previously set
> retitle -2 dh-python cannot parse python_version dependency
Bug #978686 [src:dh-python] Missing required dependencies
Changed Bug title to 'dh-python cannot parse python_version dependency' from 
'Missing required dependencies'.
> forcemerge 977926 977927
Bug #977926 [mitmproxy] Missing required dependencies
Bug #977927 [mitmproxy] DistributionNotFound: 'hyperframe>=6.0' due to missing 
dependencies
Merged 977926 977927
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
977926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977926
977927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977927
978686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems