Bug#972715: atril: segfault on opening an epub file

[Bernhard Übelacker]

Dear Maintainer,
I could reproduce this issue and attached patch avoids the crash.
This makes it possible to view at least some pages.
But there is still another issue with referencing the pages
containing a space in their names, which got encoded in
content.opf to %20, and atril encodes again to %2520.
I guess upstream needs to have a look at this epub.

Kind regards,
Bernhard
Description: Avoid crash on certain epub files

Author: Bernhard Übelacker 
Bug-Debian: https://bugs.debian.org/972715
Forwarded: no
Last-Update: 2020-11-01

Index: atril-1.24.0/backend/epub/epub-document.c
===
--- atril-1.24.0.orig/backend/epub/epub-document.c
+++ atril-1.24.0/backend/epub/epub-document.c
@@ -1280,7 +1280,7 @@ setup_document_index(EpubDocument *epub_
 		xml_parse_children_of_node(navLabel,(xmlChar*)"text",NULL,NULL);
 linknode *newnode = g_new0(linknode,1);
 		newnode->linktext = NULL;
-		while (newnode->linktext == NULL) {
+		while (xmlretval && newnode->linktext == NULL) {
 		newnode->linktext = (gchar*)xml_get_data_from_node(xmlretval,XML_KEYWORD,NULL);
 			xmlretval = xmlretval->next;
 		}
@@ -1599,7 +1599,7 @@ page_set_function(linknode *Link, GList
 	contentListNode *pagedata;
 
 	guint flag=0;
-	while (!flag) {
+	while (listiter && !flag) {
 		pagedata = listiter->data;
 		if (link_present_on_page(Link->pagelink, pagedata->value)) {
 			flag=1;


# Bullseye/testing amd64 qemu VM 2020-11-01


apt update
apt dist-upgrade


apt install systemd-coredump mc htop psmisc net-tools fakeroot quilt lightdm 
xserver-xorg mate rr gdb atril-dbgsym libglib2.0-0-dbgsym libatrilview3-dbgsym 
libatrildocument3-dbgsym
apt build-dep atril


reboot

# for current rr
dpkg --purge rr
apt install sshfs
echo 1 > /proc/sys/kernel/perf_event_paranoid
mkdir -p /home/bernhard/data/entwicklung/2020/rr
sshfs -o allow_other,uid=1000,gid=1000 
bernhard@192.168.178.25:/home/bernhard/data/entwicklung/2020/rr 
/home/bernhard/data/entwicklung/2020/rr




mkdir /home/benutzer/source/atril/orig -p
cd/home/benutzer/source/atril/orig
apt source atril
cd


wget 
"https://arkhamarchivist.com/ebook/The%20Complete%20Works%20of%20HP%20Lovecraft.epub;
 -O Lovecraft.epub


export DISPLAY=:0
LANG=C atril /tmp/Lovecraft.epub



benutzer@debian:~$ export DISPLAY=:0
benutzer@debian:~$ LANG=C atril /tmp/Lovecraft.epub
Speicherzugriffsfehler (Speicherabzug geschrieben)


root@debian:~# journalctl -e
Nov 01 00:26:12 debian kernel: EvJobScheduler[8349]: segfault at 18 ip 
7fad28609570 sp 7fad20bfb8f8 error 4 in 
libepubdocument.so[7fad28608000+7000]
Nov 01 00:26:12 debian kernel: Code: 48 85 f6 74 0d 4c 89 e7 e8 bd ed ff ff e9 
10 ff ff ff ba 05 00 00 00 48 8d 35 84 5d 00 00 e9 38 ff ff ff 0f 1f 80 00 00 
00 00 <48> 8b 77 18 48 8b 3d a5 9a 00>
Nov 01 00:26:12 debian systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
Nov 01 00:26:12 debian systemd[1]: Started Process Core Dump (PID 8350/UID 0).
Nov 01 00:26:13 debian systemd[1]: systemd-coredump@0-8350-0.service: Succeeded.


root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Sun 2020-11-01 00:26:13 CET8336  1000  1000  11 present   /usr/bin/atril




root@debian:~# cd /home/benutzer/source/atril/orig/atril-1.24.0/backend/epub
root@debian:/home/benutzer/source/atril/orig/atril-1.24.0/backend/epub# 
coredumpctl gdb 8336
   PID: 8336 (atril)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Sun 2020-11-01 00:26:12 CET (1min 37s ago)
  Command Line: atril /tmp/Lovecraft.epub
Executable: /usr/bin/atril
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: 6f6865f89dce40bd9780531de2826637
Machine ID: 33f18f39d2a9438eb75b0ed52848afcd
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.atril.1000.6f6865f89dce40bd9780531de2826637.8336.160418677200.zst
   Message: Process 8336 (atril) of user 1000 dumped core.

Stack trace of thread 8349:
#0  0x7fad28609570 n/a (libepubdocument.so + 0x3570)
#1  0x7fad2860a4d5 n/a (libepubdocument.so + 0x44d5)
#2  0x7fad3410e602 ev_document_load (libatrildocument.so.3 
+ 0x14602)
#3  0x7fad3411031b ev_document_factory_get_document 
(libatrildocument.so.3 + 0x1631b)
#4  0x7fad340c223c n/a (libatrilview.so.3 + 0x1f23c)
#5  0x7fad340c3242 n/a (libatrilview.so.3 + 0x20242)
#6  0x7fad3329ddbd n/a (libglib-2.0.so.0 + 0x7adbd)
#7  0x7fad330c5ea7 start_thread (libpthread.so.0 + 0x8ea7)
#8  0x7fad32ff5d4f __clone (libc.so.6 + 0xfdd4f)

Stack trace of 

Bug#750156: puddletag: Puddletag does not Album Art panel (under Gnome 3/Gnome Shell)

[Paul Wise]

On Mon, 02 Jun 2014 09:16:59 +0200 Ralph Aichinger wrote:

> There is supposed to be a Album Cover/Album Art panel in puddletag.
> When I select the corresponding menu item (Windows>Artwork) nothing
> happens though. No panel is added, no window is opened, nothing.
> Album Art information is accessible by using a workaround (extended
> tags), it just is not very convenient.

puddletag was recently reintroduced to Debian unstable, it would be
great if you could check the new version.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#599920: ktechlab: segfault when pasting components, Switch::calculateCurrent

[Paul Wise]

On Tue, 12 Oct 2010 15:31:00 +0300 Timo Juhani Lindfors wrote:

> I tried to prototype some simple circuits today. ktechlab crashed
> three times.

ktechlab was recently reintroduced to unstable, it would be great if
you could test to see if you can reproduce the crashes or not.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#973513: ricks-amdgpu-utils: undocumented dependencies

[tmo1]

Package: ricks-amdgpu-utils
Version: 3.5.0-1
Severity: normal
X-Debbugs-Cc: tmo...@gmx.com

Plotting requires the python3-cairocffi package; without it installed,
gpu-mon fails ungracefully with something like:

*

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_cairo.py", 
line 15, in 
import cairo
ModuleNotFoundError: No module named 'cairo'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_cairo.py", 
line 21, in 
import cairocffi as cairo
ModuleNotFoundError: No module named 'cairocffi'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/bin/gpu-plot", line 66, in 
from matplotlib.backends.backend_gtk3cairo import FigureCanvasGTK3Cairo as 
FigureCanvas
  File 
"/usr/lib/python3/dist-packages/matplotlib/backends/backend_gtk3cairo.py", line 
6, in 
from . import backend_cairo, backend_gtk3
  File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_cairo.py", 
line 23, in 
raise ImportError(
ImportError: cairo backend requires that pycairo>=1.11.0 or cairocffiis 
installed
gpu-plot has closed
Quitting...

*

It also requires the package python3-gi-cairo to work properly; without
it, the plotting screen opens but the plotting doesn't work, with many
copies of:

TypeError: Couldn't find foreign struct converter for 'cairo.Context'

being printed to the console.

I think that in addition, python3-gi is necessary for any GUI
functionality, and gnuplot is necessary for plotting.

These various dependencies should either be specified as either
recommends or at least suggests, and / or documented in the
documentation. My personal opinion is that both should be done.
ear Maintainer,

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

Kernel: Linux 5.9.0-1-amd64 (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

Versions of packages ricks-amdgpu-utils depends on:
ii  python3 3.8.6-1
ii  python3-gpumodules  3.5.0-1

ricks-amdgpu-utils recommends no packages.

ricks-amdgpu-utils suggests no packages.

-- no debconf information

Bug#973512: RuntimeError: dictionary keys changed during iteration

[Kingsley G. Morse Jr.]

Package: onioncircuits
Version: 0.7-1
Severity: normal

Dear Maintainer,

Thank you for maintaining onioncircuits.

Much like the tenet of patron privacy that public
libraries hold dear, I love the ideal of voters
using TOR to privately and safely explore new
ideas without fear of repercussion from neighbors
or employers, and ultimately become a better
informed electorate that can actually rule itself
wisely enough to successfully sustain a democratic
form of government.

The main reason I'm writing is to suggest
improving the dependency info for the
onioncircuits package to specify at least version
1.8.0-2 of the python3-stem package.

It currently accepts any version, but when I tried
1.7.1-1, onioncircuits failed with

Traceback (most recent call last):
  File "/usr/bin/onioncircuits", line 668, in 
app = OnionCircuitsApplication()
  File "/usr/bin/onioncircuits", line 644, in __init__
self.connect_controller()
  File "/usr/bin/onioncircuits", line 658, in connect_controller
self.controller = stem.connection.connect(**connect_args)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 291, in 
connect
return _connect_auth(control_connection, password, password_prompt, 
chroot_path, controller)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 375, in 
_connect_auth
return controller(control_socket, is_authenticated = True)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 1057, in 
__init__
super(Controller, self).__init__(control_socket, is_authenticated)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 585, in 
__init__
self._post_authentication()
  File "/usr/lib/python3/dist-packages/stem/control.py", line 3902, in 
_post_authentication
owning_pid = self.get_conf('__OwningControllerProcess', None)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2170, in 
get_conf
entries = self.get_conf_map(param, default, multiple)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2273, in 
get_conf_map
for key in reply:
RuntimeError: dictionary keys changed during iteration


Doing 

root$ aptitude install python3-stem

fixed it.

Thanks, and kind regards,
Kingsley

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages onioncircuits depends on:
ii  gir1.2-glib-2.01.62.0-5
ii  gir1.2-gtk-3.0 3.24.13-1
ii  python3-gi 3.34.0-6
ii  python3-pkg-resources  41.1.0-1
ii  python3-pycountry  20.7.3+ds1-1
ii  python3-stem   1.8.0-2
pn  python3:any

onioncircuits recommends no packages.

Versions of packages onioncircuits suggests:
ii  tor-geoipdb  0.4.2.7-1

-- no debconf information

Bug#972994: iw should no longer recommend crda

[Paul Wise]

On Tue, 27 Oct 2020 11:33:54 + Paride Legovini wrote:

>* d/control: drop Recommends: crda (deprecated since linux v4.15)
>  Thanks to Diederik de Haas (Closes: #972994)

I note that this means wireless-regdb will no longer be installed but
that is the location of the WiFi regulatory database and is still
needed in order for the Linux kernel to comply with WiFi regulations,
so I recommend that wireless-regdb be added to recommends in order to
replace the crda dependency on wireless-regdb.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#973511: miniupnpd: new upstream release 2.2.0 available

[Ryutaroh Matsumoto]

Source: miniupnpd
Version: 2.1-6.1
Severity: wishlist

Dear Maintainer,

A new upstream release 2.2.0 become available at
http://miniupnp.free.fr/files/

As far as I experienced, nftables backend becomes sufficiently stable
in 2.2.0.

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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

Bug#973510: ITP: nim-hts -- wrapper for hts C library

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: nim-hts -- wrapper for hts C library
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: nim-hts
  Version : 0.3.12
  Upstream Author : Brent Pedersen
* URL : https://github.com/brentp/hts-nim
* License : Expat
  Programming Lang: C
  Description : wrapper for hts C library
 The hts library is well accepted for the handling of millions of
 DNA sequences from what once was the high-throughput sequencing machines
 in biological research and medical diagnostics/therapy control.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/nim-hts

Bug#940967: ECDH now not experimental

[Jonas Smedegaard]

Quoting Janus Troelsen (2020-11-01 01:52:01)
> If you update to the latest master, ECDH is now no longer 
> experimental. So I think this can be closed once the version is 
> updated.

Yes, I followed the upstream issue issue.

Thanks for mentioning here as well.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#973038: autopkgtest-build-qemu installs grub-pc on arm64 which is unavailable

[Ryutaroh Matsumoto]

>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973484
>> if you have interest...
> That sounds like a major road block indeed, unfortunately...

I found a workaround, then I met another obstacle... as below:

One can attach a USB serial to QEMU (5.1) arm emulater with machine "virt"
by -device qemu-xhci -device usb-serial,chardev=somedefinedID.

But QEMU USB serial is much different from QEMU serial.
The USB serial is considered unplugged from VM by QEMU,
when there is no process on host associated with the host socket
corresponding to USB serial in VM!!!.

On the other hand, autopkgtest_virt_qemu opens and closes the
UNIX socket associated with VM's ttyS1 many times.

I made attached changes to autopkgtest_virt_qemu and setup-testbed,
and the testbed can be executed until some point as below.
In order to have QEMU autopkgtestbed on arm, one of the following may
be necessary:
(1) Modify QEMU to allow multiple "-serial" as /dev/ttyAMA? in VM, or
(2) Modify autopkgtest_virt_qemu to keep the socket to VM's ttyS1 open
all the time.

Both of them involves major design decision by the upstreams.
So I stop my investigation here unless a good idea occurs.
There seems no easy fix.

# autopkgtest -u debci -B bash -- qemu --debug --efi  
/var/lib/debci/qemu/sid-arm64.img
autopkgtest [11:34:32]: starting date: 2020-11-01
autopkgtest [11:34:32]: version 5.15
autopkgtest [11:34:32]: host raspi4-bullseye; command line: 
/usr/bin/autopkgtest -u debci -B bash -- qemu --debug --efi 
/var/lib/debci/qemu/sid-arm64.img
autopkgtest-virt-qemu: DBG: executing open
autopkgtest-virt-qemu: DBG: execute-timeout: qemu-img info --output=json 
/var/lib/debci/qemu/sid-arm64.img
autopkgtest-virt-qemu: DBG: Creating temporary overlay image in 
/tmp/autopkgtest-qemu.scy36yci/overlay.img
autopkgtest-virt-qemu: DBG: execute-timeout: qemu-img create -f qcow2 -F qcow2 
-b /var/lib/debci/qemu/sid-arm64.img /tmp/autopkgtest-qemu.scy36yci/overlay.img
autopkgtest-virt-qemu: DBG: find_free_port: trying 10022
autopkgtest-virt-qemu: DBG: find_free_port: 10022 is free
autopkgtest-virt-qemu: DBG: Forwarding local port 10022 to VM ssh port 22
autopkgtest-virt-qemu: DBG: ['qemu-system-aarch64', '-m', '1024', '-smp', '1', 
'-nographic', '-net', 'nic,model=virtio', '-net', 
'user,hostfwd=tcp:127.0.0.1:10022-:22', '-object', 
'rng-random,filename=/dev/urandom,id=rng0', '-device', 
'virtio-rng-pci,rng=rng0,id=rng-device0', '-monitor', 
'unix:/tmp/autopkgtest-qemu.scy36yci/monitor,server,nowait', '-serial', 
'unix:/tmp/autopkgtest-qemu.scy36yci/ttyS0,server,nowait', '-virtfs', 
'local,id=autopkgtest,path=/tmp/autopkgtest-qemu.scy36yci/shared,security_model=none,mount_tag=autopkgtest',
 '-drive', 
'file=/tmp/autopkgtest-qemu.scy36yci/overlay.img,cache=unsafe,if=virtio,index=0,format=qcow2',
 '-machine', 'virt', '-cpu', 'host', '-chardev', 
'socket,id=usbserial,path=/tmp/autopkgtest-qemu.scy36yci/ttyS1,server', 
'-device', 'qemu-xhci', '-device', 'usb-serial,chardev=usbserial', '-drive', 
'if=pflash,format=raw,read-only,file=/usr/share/AAVMF/AAVMF_CODE.fd', '-drive', 
'if=pflash,format=raw,file=/tmp/autopkgtest-qemu.scy36yci/efivars.fd', 
'-enable-kvm']
qemu-system-aarch64: -chardev 
socket,id=usbserial,path=/tmp/autopkgtest-qemu.scy36yci/ttyS1,server: info: 
QEMU waiting for connection on: 
disconnected:unix:/tmp/autopkgtest-qemu.scy36yci/ttyS1,server
autopkgtest-virt-qemu: DBG: expect: " login: "
autopkgtest-virt-qemu: DBG: expect: found ""login prompt on ttyS0""
autopkgtest-virt-qemu: DBG: expect: "ok"
autopkgtest-virt-qemu: DBG: expect: found ""b'ok'""
autopkgtest-virt-qemu: DBG: setup_shell(): there already is a shell on ttyS1
autopkgtest-virt-qemu: DBG: expect: "#"
autopkgtest-virt-qemu: DBG: expect: found ""b'#'""
autopkgtest-virt-qemu: DBG: expect: "#"
autopkgtest-virt-qemu: DBG: expect: found ""b'#'""
autopkgtest-virt-qemu: DBG: expect: "# "
autopkgtest-virt-qemu: DBG: expect: found ""b'# '""
autopkgtest-virt-qemu: DBG: Copying host timezone Asia/Tokyo to VM
autopkgtest-virt-qemu: DBG: expect: "#"
autopkgtest-virt-qemu: DBG: expect: found ""b'#'""
autopkgtest-virt-qemu: DBG: expect: "/python"
autopkgtest-virt-qemu: DBG: expect: found ""b'/python'""
autopkgtest-virt-qemu: DBG: expect: "# "
autopkgtest-virt-qemu: DBG: expect: found ""b'# '""
autopkgtest-virt-qemu: DBG: execute-timeout: 
/tmp/autopkgtest-qemu.scy36yci/runcmd true
qemu-system-aarch64: terminating on signal 15 from pid 25851 (/usr/bin/python3)
autopkgtest-virt-qemu: DBG: cleanup...
Unexpected error:
Traceback (most recent call last):
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 739, in mainloop
command()
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 668, in command
r = f(c, ce)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 258, in cmd_open
caller.hook_open()
  File "/usr/bin/autopkgtest-virt-qemu", line 648, in hook_open
make_auxverb(shareddir)
  File "/usr/bin/autopkgtest-virt-qemu", line 449, in make_auxverb
status = 

Bug#940967: ECDH now not experimental

[Janus Troelsen]

If you update to the latest master, ECDH is now no longer
experimental. So I think this can be closed once the version is
updated.

Bug#973508: bazel-bootstrap FTBFS

[Adrian Bunk]

Source: bazel-bootstrap
Version: 3.4.0+ds-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bazel-bootstrap.html
https://buildd.debian.org/status/package.php?p=bazel-bootstrap=sid

...
[1,619 / 1,622] Executing genrule //src:package-zip_nojdk; 3s 
local

ERROR: /<>/src/BUILD:326:9: Executing genrule 
//src:package-zip_nojdk failed (Exit 1): bash failed: error executing command 
  (cd /tmp/bazel_6346MX9l/out/execroot/io_bazel && \
  exec env - \
CCACHE_DISABLE=1 \
CCACHE_TEMPDIR=/<>/debian/ccachetmp \

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \
  /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; 
bazel-out/aarch64-dbg/bin/src/package-bazel-on-host-platform.sh 
bazel-out/aarch64-dbg/bin/src/package_nojdk.zip  
bazel-out/aarch64-dbg/bin/src/embedded_tools_nojdk.zip 
bazel-out/aarch64-dbg/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
 bazel-out/aarch64-dbg/bin/src/install_base_key_nojdk 
bazel-out/aarch64-dbg/bin/src/platforms.zip 
bazel-out/aarch64-dbg/bin/src/main/java/com/google/devtools/build/lib/syntax/libcpu_profiler.so
 bazel-out/aarch64-dbg/bin/src/main/native/libunix.so 
bazel-out/aarch64-dbg/bin/src/main/tools/build-runfiles 
bazel-out/aarch64-dbg/bin/src/main/tools/process-wrapper 
src/main/tools/jdk.BUILD bazel-out/aarch64-dbg/bin/src/main/tools/linux-sandbox 
bazel-out/aarch64-dbg/bin/tools/osx/xcode-locator 
bazel-out/aarch64-dbg/bin/src/main/tools/daemonize')
Execution platform: //:default_host_platform
[1,620 / 1,622] checking cached actions

cp: failed to access 
'/build/bazel-bootstrap-3.4.0+ds/output/usr/share/bazel': No such file or 
directory
[1,620 / 1,622] checking cached actions

INFO: Elapsed time: 245.830s, Critical Path: 166.09s
[1,620 / 1,622] checking cached actions

INFO: 1586 processes: 906 local, 680 worker.
[1,620 / 1,622] checking cached actions

FAILED: Build did NOT complete successfully

FAILED: Build did NOT complete successfully

ERROR: Could not build Bazel
make[1]: *** [debian/rules:54: override_dh_auto_build] Error 1

Bug#972572: emacs-gtk: scrolling upward with the mouse wheel actually scrolls downward when the cursor needs repositioning

[Vincent Lefevre]

Control: retitle -1 emacs-gtk: with misc-fixed 13-pixel fonts, unexpected 
scroll when the cursor is on the last line of the window

The cause is that with the cairo version (like in Debian),
row->phys_ascent > row->ascent. There are 2 issues:

1. The fact that this condition is true with misc-fixed 13-pixel fonts.

2. The fact that this condition is handled incorrectly by Emacs.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#973507: libsis-jhdf5-java: incorrect license text for source/c/jni/

[Sean Whitton]

Source: libsis-jhdf5-java
Version: 19.04.0+dfsg-1
Severity: serious
Justification: Policy 2.3, 4.5, 12.5
X-Debbugs-CC: ftpmas...@debian.org

Hello,

The file source/c/jni/COPYING is a different HDF license to that which
applies to source/java/hdf/hdf5lib.  The version in NEW has the same
problem as what's currently in the archive.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#973472: fetchmail: Fails to connect using SSL

[Bill Wohler]

Same here.

Will you be able to fix this now so that everyone using fetchmail can
get mail without having to jump through hoops like building fetchmail or
finding the previous package?

-- 
Bill Wohler  aka 
http://www.newt.com/wohler/, GnuPG ID:610BD9AD

Bug#972900: Acknowledgement (pychess has an unlisted dependency on python3-sqlalchemy)

[Brian Vaughan]

I downloaded and installed python3-pychess_1.0.2-1_all.deb from

https://github.com/pychess/pychess/releases

And this version did pull in python3-sqlalchemy as a dependency.

Bug#973506: packagekit: offline system update don't work after upgrading from 1.1.13-2+b1 to 1.2.1-1

[Andrey Skvortsov]

Package: packagekit
Version: 1.2.1-1
Severity: important

Dear Maintainer,


after updating packagekit from 1.1.13-2+b1 to 1.2.1-1 updates are not
installed anymore. 
If new packages are available software center shows that there are some
update. User can press download, packages will be downloaded and after
that it press "reboot and install". Devices reboots into systemd target
system-update.target, but nothing is installed. Afterwards it reboots
back into user session.
Because nothing was installed, then software center shows again that the
same updates are still available.

I've checked 1.2.1-1 package content and the problem is that symlink for
packagekit-offline-update.service in 
/lib/systemd/system/system-update.target.wants is missing.

After following command
cd /lib/systemd/system/system-update.target.wants; ln -s 
../packagekit-offline-update.service packagekit-offline-update.service
offline system updates work again.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.8-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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)

Versions of packages packagekit depends on:
ii  init-system-helpers 1.58
ii  libappstream4   0.12.11-1
ii  libapt-pkg6.0   2.1.11
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-15
ii  libglib2.0-02.66.1-2
ii  libglib2.0-bin  2.66.1-2
ii  libgstreamer1.0-0   1.18.0-3
ii  libpackagekit-glib2-18  1.2.1-1
ii  libpolkit-gobject-1-0   0.105-29
ii  libsqlite3-03.33.0-1
ii  libstdc++6  10.2.0-15
ii  libsystemd0 246.6-2
ii  policykit-1 0.105-29

Versions of packages packagekit recommends:
pn  packagekit-tools  
ii  systemd   246.6-2

Versions of packages packagekit suggests:
ii  appstream  0.12.11-1

-- no debconf information

Bug#973505: akregator: Feeds no longer update

[Francois Marier]

Package: akregator
Version: 4:20.08.2-3
Severity: grave
Justification: renders package unusable

Since the last upgrade, feed updates no longer work.

I see the following error when I start akregator from a terminal:

  kf.kio.core: couldn't create slave: "klauncher said: Erreur lors du 
chargement de « /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so »."

which roughly translates to:

  Error while loading /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so.

I have also seen these errors in my logs, though I'm not 100% sure they are
related to akregator:

  kf.i18n: KCatalog being used without a Q*Application instance. Some 
translations won't work
  Il est impossible d'ouvrir la bibliothèque « 
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so ».
  Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so: 
(/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found (required 
by /lib/x86_64-linux-gnu/libQt5Network.so.5))
  Il est impossible d'ouvrir la bibliothèque « 
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so ».
  Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so: 
(/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found (required 
by /lib/x86_64-linux-gnu/libQt5Network.so.5))

Francois

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

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.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

Versions of packages akregator depends on:
ii  kinit  5.74.0-2
ii  kio5.74.0-2
ii  libc6  2.31-4
ii  libgcc-s1  10.2.0-16
ii  libkf5codecs5  5.74.0-2
ii  libkf5completion5  5.74.0-2
ii  libkf5configcore5  5.74.0-2
ii  libkf5configgui5   5.74.0-2
ii  libkf5configwidgets5   5.74.0-2
ii  libkf5coreaddons5  5.74.0-2
ii  libkf5crash5   5.74.0-2
ii  libkf5grantleetheme-plugins20.08.2-2
ii  libkf5grantleetheme5 [libkf5grantleetheme5-20.08]  20.08.2-2
ii  libkf5i18n55.74.0-3
ii  libkf5jobwidgets5  5.74.0-2
ii  libkf5kcmutils55.74.0-2
ii  libkf5kiocore5 5.74.0-2
ii  libkf5kiogui5  5.74.0-2
ii  libkf5kiowidgets5  5.74.0-2
ii  libkf5kontactinterface5 [libkf5kontactinterface5-20.08]20.08.2-2
ii  libkf5libkdepim5 [libkf5libkdepim5-20.08]  4:20.08.2-2
ii  libkf5messageviewer5abi1 [libkf5messageviewer5-20.08]  4:20.08.2-2
ii  libkf5mimetreeparser5abi1 [libkf5mimetreeparser5-20.08]4:20.08.2-2
ii  libkf5notifications5   5.74.0-2
ii  libkf5notifyconfig55.74.0-2
ii  libkf5parts5   5.74.0-2
ii  libkf5pimcommon5abi2 [libkf5pimcommon5-20.08]  4:20.08.2-2
ii  libkf5pimtextedit5abi2 [libkf5pimtextedit5-20.08]  20.08.2-2
ii  libkf5service-bin  5.74.0-2
ii  libkf5service5 5.74.0-2
ii  libkf5syndication5abi1 1:5.74.0-2
ii  libkf5textwidgets5 5.74.0-2
ii  libkf5webengineviewer5abi1 [libkf5webengineviewer5-20.08]  4:20.08.2-2
ii  libkf5widgetsaddons5   5.74.0-3
ii  libkf5xmlgui5  5.74.0-2+b1
ii  libkuserfeedbackcore1  1.0.0-3
ii  libkuserfeedbackwidgets1   1.0.0-3
ii  libqt5core5a   5.15.1+dfsg-2
ii  libqt5dbus55.15.1+dfsg-2
ii  libqt5gui5 5.15.1+dfsg-2
ii  libqt5network5 5.15.1+dfsg-2
ii  libqt5printsupport55.15.1+dfsg-2
ii  libqt5webenginecore5   5.15.1+dfsg-5
ii  libqt5webenginewidgets5   

Bug#853736: Battery sometimes not detected (Macbook Air 2011 and Macbook Pro 2012)

[robert b]

I am running 4.9.0-14 and I also have this problem.  Only by rebooting into 
MacOSX (I have a dual-boot system) first before rebooting into Linux does the 
battery consistently get detected and put into /sys/class/power_supply/ 
correctly.  I have a MacBookPro8,1 .

Bug#954353: Acknowledgement (guile-2.2: FTBFS on hppa - 'mra' undeclared)

[John David Anglin]

Ping!!!

Regards,
Dave Anglin

-- 
John David Anglin  dave.ang...@bell.net

Bug#973494: plan: Error in append mode

[DieSpinne]

Package: plan
Version: 1.10.1-5+b1
Severity: important

Dear Maintainer,

I cannot use Plan in append mode. For example, if I try to schedule an 
appoitment for 7 o' clock
with

plan 0700

, I get the error

plan: main.c:334: non_interactive: Assertion `sizeof(l) < 6' failed.

. I have tried many variations of the command, including adding options such
as `-l`, but to no avail.

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

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

Versions of packages plan depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10
ii  libice62:1.0.9-2
ii  libx11-6   2:1.6.7-1+deb10u1
ii  libxext6   2:1.3.3-1+b2
ii  libxm4 2.3.8-2
ii  libxpm41:3.5.12-1
ii  libxt6 1:1.1.5-1+b3

plan recommends no packages.

Versions of packages plan suggests:
pn  netplan  

-- debconf information:
  plan/holiday: none

Bug#973504: ITP: nemo-preview -- quick previewer for nemo

[Joshua Peisach]

Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: nemo-preview
  Version : 4.6.0
  Upstream Author : Clement Lefebvre , Cosimo Cecchi

* URL : https://github.com/linuxmint/nemo-
extensions/tree/master/nemo-preview
* License : GPL-2+
  Programming Lang: C, JS
  Description : quick previewer for nemo

I will maintain this by myself until I can hopefully get it into cinnamon-team.

Bug#973337: dh-runit: autopkgtest-virt-lxc failure on armel

[Ryutaroh Matsumoto]

> Therefore you might have a look at 'cat /proc/cpu/alignment',
> and maybe as a workaround change it temporarily
> by 'echo 3 > /proc/cpu/alignment' and retest.

Thank you for paying attention to this.
I am using Debian stock kernel
# uname -a
Linux raspi4-bullseye 5.9.0-1-arm64 #1 SMP Debian 5.9.1-1 (2020-10-17) aarch64 
GNU/Linux

in Debian testing on Raspberry Pi 4B, but
# find /proc -name \*align\* -print
shows nothing...

I don't have /proc/cpu/alignment...

Ryutaroh

Bug#973503: "missing-build-dependency-for-dh-addon pgxs => postgresql-server-dev-all" is missing postgresql-all

[Christoph Berg]

Package: lintian
Version: 2.100.0
Severity: normal

Hi,

The tag "missing-build-dependency-for-dh-addon pgxs => 
postgresql-server-dev-all"
needs to consider "postgresql-all" as a possible alternative build-dependency.

Christoph

Bug#973337: dh-runit: autopkgtest-virt-lxc failure on armel

[Bernhard Übelacker]

Hello Ryutaroh Matsumoto,
I just tried to reproduce this and got such a "Bus error" while
running an armhf testing chroot on a physical armv7l system,
unfortunately not running a stock debian kernel, instead
a lineageos kernel.

Here the "Bus error" is given because of an stmib instruction
operating on a unaligned memory address.
Unfortunately this happens inside something what looks like
stack swapping, therefore cannot point to the source of this
instruction.

Therefore you might have a look at 'cat /proc/cpu/alignment',
and maybe as a workaround change it temporarily
by 'echo 3 > /proc/cpu/alignment' and retest.

Attached file contains some debugging and a manual -v3 rebuild of
the testrunner showing the used compile and link parameters.

I guess this issue need some investigation of someone who
knows more about the ghc internals.

Kind regards,
Bernhard


=> 0xd0670: stmib   r1, {r9, lr}
(gdb) print/x $r1 % 4
$2 = 0x2


# Bullseye/testing chroot 2020-10-31 running on Android/LineageOS kernel


apt update
apt dist-upgrade


apt install mc htop psmisc net-tools strace sshfs wget gdb gdbserver 
autopkgtest dh-runit
apt build-dep dh-runint



root@localhost:~# lscpu
Architecture: armv7l
Byte Order:   Little Endian
CPU(s):   4
On-line CPU(s) list:  0
Off-line CPU(s) list: 1-3
Thread(s) per core:   1
Core(s) per socket:   1
Socket(s):1
Vendor ID:Qualcomm
Model:0
Model name:   Krait
Stepping: 0x1
CPU max MHz:  1728,
CPU min MHz:  384,
BogoMIPS: 13.50
Flags:swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 
idiva idivt
root@localhost:~# uname -a
Linux localhost 3.4.113-g2fff5b1955c0 #1 SMP PREEMPT Sun Mar 8 06:23:52 CST 
2020 armv7l GNU/Linux

groupadd -g 3001 aid_net_bt_admin
groupadd -g 3002 aid_net_bt
groupadd -g 3003 aid_inet
groupadd -g 3004 aid_net_raw
groupadd -g 3005 aid_net_admin
groupadd -g 3006 aid_net_bw_stats
groupadd -g 3007 aid_net_bw_acct
groupadd -g 3008 aid_net_bt_stack
usermod -G 3003,3004 -a root
usermod -G 3003 -a benutzer
usermod -g 3003 -G 3003,3004 -a _apt






mkdir /home/benutzer/source/dh-runit/orig -p
cd/home/benutzer/source/dh-runit/orig
apt source dh-runit
cd

mkdir /home/benutzer/source/ghc/orig -p
cd/home/benutzer/source/ghc/orig
apt source ghc
cd






autopkgtest dh-runit -- null
autopkgtest --shell-fail dh-runit -- null



benutzer@localhost:~$ autopkgtest dh-runit -- null
autopkgtest [16:04:08]: starting date: 2020-10-31
autopkgtest [16:04:08]: version 5.15
autopkgtest [16:04:08]: host localhost; command line: /usr/bin/autopkgtest 
dh-runit -- null
autopkgtest [16:04:08]: testbed dpkg architecture: armhf
autopkgtest [16:04:08]: testbed running kernel: Linux 3.4.113-g2fff5b1955c0 #1 
SMP PREEMPT Sun Mar 8 06:23:52 CST 2020
autopkgtest [16:04:08]:  apt-source dh-runit
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.Mw0OcQGe/trustedkeys.kbx': 
General error
gpgv: Signature made Di 21 Jul 2020 10:55:07 UTC
gpgv:using RSA key 92978A6E195E4921825F7FF0F34F09744E9F5DD9
gpgv: Can't check signature: No public key
dpkg-source: Warnung: Fehler beim Überprüfen der Signatur von 
./dh-runit_2.9.0.dsc
autopkgtest [16:04:10]: testing package dh-runit version 2.9.0
autopkgtest [16:04:10]: build not needed
autopkgtest [16:04:11]: test command1: preparing testbed
autopkgtest [16:04:11]: test command1: make autopkgtest
autopkgtest [16:04:11]: test command1: [---
ghc testrunner.hs
[1 of 1] Compiling Main ( testrunner.hs, testrunner.o )
Linking testrunner ...
AUTOPKGTEST=1 ./testrunner
Bus error
make: *** [Makefile:7: autopkgtest] Error 135
autopkgtest [16:04:29]: test command1: ---]
autopkgtest [16:04:29]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 2
autopkgtest [16:04:29]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
Bus error
make: *** [Makefile:7: autopkgtest] Error 135
autopkgtest [16:04:29]:  summary
command1 FAIL non-zero exit status 2
benutzer@localhost:~$


benutzer@localhost:~/autopkgtest-dh-runit-output$ autopkgtest --shell-fail 
dh-runit -- null
autopkgtest [16:10:06]: starting date: 2020-10-31
autopkgtest [16:10:06]: version 5.15
autopkgtest [16:10:06]: host localhost; command line: /usr/bin/autopkgtest 
--shell-fail dh-runit -- null
autopkgtest [16:10:07]: testbed dpkg architecture: armhf
autopkgtest [16:10:07]: testbed running kernel: Linux 3.4.113-g2fff5b1955c0 #1 
SMP PREEMPT Sun Mar 8 06:23:52 CST 2020
autopkgtest [16:10:07]:  apt-source dh-runit
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.G8OGzlGp/trustedkeys.kbx': 
General error
gpgv: Signature made Di 21 Jul 2020 10:55:07 UTC
gpgv:  

Bug#972928: claws-mail: Crash when attempted to enter IMAP folder

[pioruns2019]

On 31/10/2020 11:27, Ricardo Mones wrote:

> Is that reproducible? I've seen similar sporadic segfaults in the past
> and is unlikely is Claws Mail fault only. You can try translate the
> faulting address into some more meaningful, see [1]. Also, if it's
> reproducible you'll have to install debugging packages and get a proper
> backtrace [2].
>
> regards,
>
> [1] https://stackoverflow.com/a/2549363

This now leaves some trail:

$ addr2line -e /usr/bin/claws-mail -f 004a35bd
folderview_close_opened
??:?

> [2] https://wiki.debian.org/HowToGetABacktrace

I've never encountered it before. If it happens again, I will attach it
to the debugger.


--
Kind regards,
pioruns2019

Bug#955211: release.debian.org: Transition r-base for 4.0.0

[Dirk Eddelbuettel]

On 31 October 2020 at 18:46, Sebastian Ramacher wrote:
| On 2020-05-28 11:58:09 -0500, Dirk Eddelbuettel wrote:
| > 
| > Thanks everybody for the help with the transition: 4.0.0-3 is now in 
testing.
| 
| So let's close this one.

Indeed. Thanks for catching that!

Dirk
 
| Cheers
| 
| > 
| > Which is lovely as upstream is already at work with 4.0.1 which will drop on
| > June 6 [1]. I'll likely make an rc upload.
| > 
| > Special thanks to Graham for calmly pulling a few strings here and there.
| > 
| > Cheers, Dirk
| > 
| > 
| > [1] Details as always at http://developer.r-project.org/, and just to be
| > plain it is of course _not_ a binary change needing an API change.
| > -- 
| > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
| > 
| 
| -- 
| Sebastian Ramacher
| x[DELETED ATTACHMENT signature.asc, application/pgp-signature]

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#966301: guile OOM test failures on ppc64el

[Christoph Berg]

Re: Matthias Klose
> On 8/14/20 11:33 AM, Matthias Klose wrote:
> > I'm now NMUing both guile-2.2 and guile-3.0 to just ignore the test results 
> > on
> > ppc64el, without closing the bug reports.  It's blocking the gcc-10 
> > migration to
> > testing.
> 
> now, the NMUs fail with the same OOM error on armhf (3.0) and armhf/i386 (2.2)
> as well... Maybe just don't run the OOM tests, instead of ignoring the test 
> results?

There are more test failures of the same kind on hurd-i386 kfreebsd-*
powerpc and sparc64. I've added these archs to the list where test
results are ignored.

Also, #961230 was back in the form of "invalid syntax in conditional":

dpkg-buildpackage: info: host architecture kfreebsd-amd64
 fakeroot debian/rules clean
debian/rules:69: *** invalid syntax in conditional.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2

NMU diff attached.

Christoph

No differences were encountered between the control files

diff -Nru guile-2.2-2.2.7+1/debian/changelog guile-2.2-2.2.7+1/debian/changelog
--- guile-2.2-2.2.7+1/debian/changelog	2020-08-14 20:03:59.0 +0200
+++ guile-2.2-2.2.7+1/debian/changelog	2020-10-31 22:43:06.0 +0100
@@ -1,3 +1,11 @@
+guile-2.2 (2.2.7+1-5.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "invalid syntax in conditional" error in debian/rules.
+  * Ignore test failures on hurd-i386 kfreebsd-* powerpc sparc64.
+
+ -- Christoph Berg   Sat, 31 Oct 2020 22:43:06 +0100
+
 guile-2.2 (2.2.7+1-5.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru guile-2.2-2.2.7+1/debian/rules guile-2.2-2.2.7+1/debian/rules
--- guile-2.2-2.2.7+1/debian/rules	2020-08-14 20:03:59.0 +0200
+++ guile-2.2-2.2.7+1/debian/rules	2020-10-31 22:43:03.0 +0100
@@ -66,9 +66,10 @@
 deb_pkg_basename := guile-$(deb_src_eff_ver)
 deb_guile_bin_path := /usr/bin/guile-$(deb_src_eff_ver)
 
-ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${#x}" -lt 4 ] && echo ok;))
-  $(error ERROR: alternatives priority expects min version < 1000)
-endif
+# this raises "invalid syntax in conditional", disable -- myon 2020-10-31
+#ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${#x}" -lt 4 ] && echo ok;))
+#  $(error ERROR: alternatives priority expects min version < 1000)
+#endif
 
 # Up to and including some releases of 2.0.11, this was (incorrectly)
 # majminmic (i.e. 2011 for 2.0.11), so stick with something compatible
@@ -194,7 +195,7 @@
 	&& $(MAKE) -j "$(joblimit)"
 
 override_dh_auto_test:
-ifneq (,$(filter $(DEB_HOST_ARCH), armhf i386 ppc64el))
+ifneq (,$(filter $(DEB_HOST_ARCH), armhf i386 hurd-i386 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64el sparc64))
 	-dh_auto_test
 else
 	dh_auto_test

Bug#969029: pitivi fresh install gives missing dependecies message: GSound plugin, libav

[Richard B. Kreckel]

Hi!

After installing gir1.2-gsound-1.0, this message goes away.
Pitivi already suggests installing gir1.2-gsound-1.0.
This is perfectly correct, according to the Debian policy, section 7.2.
On the other hand, it wouldn't hurt making this dependency stronger, 
would it?


  -richy.
--

Bug#973502: RFS: nemo-pastebin/4.6.0-1 [ITP] -- Nemo extension to send files to a pastebin

[Joshua Peisach]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-pastebin":

 * Package name: nemo-pastebin
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre , Michael Webster

 * URL : https://community.linuxmint.com/software/view/nemo-
pastebin
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-pastebin
   Section : utils

It builds those binary packages:

  nemo-pastebin - Nemo extension to send files to a pastebin

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

  https://mentors.debian.net/package/nemo-pastebin/

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

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-pastebin/nemo-
pastebin_4.6.0-1.dsc

The repo is hosted on Salsa: https://salsa.debian.org/ItzSwirlz-guest/nemo-
pastebin

This closes ITP bug #973321: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=973321

Changes for the initial release:

 nemo-pastebin (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #973321)

Regards,
--
  Joshua Peisach



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

Kernel: Linux 5.8.0-25-generic (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#973501: RFS: nemo-media-columns/4.6.0-1 [ITP] -- Nemo Extension to display music/EXIF and PDF metadata

[Joshua Peisach]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-media-columns":

 * Package name: nemo-media-columns
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre 
 * URL : https://community.linuxmint.com/software/view/nemo-media-
columns
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-media-
columns
   Section : utils

It builds those binary packages:

  nemo-media-columns - Nemo Extension to display music/EXIF and PDF metadata

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

  https://mentors.debian.net/package/nemo-media-columns/

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

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-media-
columns/nemo-media-columns_4.6.0-1.dsc

This is hosted on Salsa: https://salsa.debian.org/ItzSwirlz-guest/nemo-media-
columns

This closes ITP Bug #972984): https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=972984

Changes for the initial release:

 nemo-media-columns (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #972984)

Regards,
--
  Joshua Peisach



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

Kernel: Linux 5.8.0-25-generic (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#973500: RFS: nemo-image-converter/4.6.0-1 [ITP] -- nemo extension to mass resize or rotate images

[Joshua Peisach]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-image-converter":

 * Package name: nemo-image-converter
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre 
 * URL : https://community.linuxmint.com/software/view/nemo-image-
converter
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-image-
converter
   Section : utils

It builds those binary packages:

  nemo-image-converter - nemo extension to mass resize or rotate images

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

  https://mentors.debian.net/package/nemo-image-converter/

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

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-image-
converter/nemo-image-converter_4.6.0-1.dsc

This repo is hosted on salsa: https://salsa.debian.org/ItzSwirlz-guest/nemo-
image-converter

This closes ITP Bug 972367: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=972367

Changes for the initial release:

 nemo-image-converter (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #972367)

Regards,
--
  Joshua Peisach



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

Kernel: Linux 5.8.0-25-generic (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#793800: filezilla: Links open two tabs containing same link

[Andreas Ronnquist]

On Mon, 27 Jul 2015 18:20:15 +0200 Andreas =?UTF-8?B?UsO2bm5xdWlzdA==?=
 wrote:
> Package: filezilla
> Version: 3.9.0.5-1
> Severity: minor
> 
> Dear Maintainer,
> 
> Clicking on links in the program (This includes both the webpage link
> in the about dialog, and also the links in the welcome dialog) opens
> the links twice in the webbrowser. I am using Iceweasel and open
> external links in a new tab, but the filezilla links opens two new
> tabs both containing the same address.
> 
> The problem is present on both Jessie and Sid.

I cannot reproduce this any longer, neither on unstable nor stable.
Feel free to close it.

/Andreas
gus...@debian.org
andr...@ronnquist.net

Bug#973499: rust-onig: autopkgtest fails on i386/armhf with new bindgen/onig-sys

[peter green]

Package: rust-onig
Version: 5.0.0-3
Severity: serious

The autopkgtest for rust-onig fails with memory errors on i386 and armhf.


https://ci.debian.net/data/autopkgtest/testing/armhf/r/rust-onig/7843624/log.gz

Caused by:
  process didn't exit successfully: 
`/tmp/tmp.p7bE9eMN2s/target/armv7-unknown-linux-gnueabihf/debug/deps/onig-38f586f8e98643ab`
 (signal: 7, SIGBUS: access to undefined memory)


https://ci.debian.net/data/autopkgtest/testing/i386/r/rust-onig/7842255/log.gz

Caused by:
  process didn't exit successfully: 
`/tmp/tmp.SP8w1ClZkZ/target/i686-unknown-linux-gnu/debug/deps/onig-cd997929b710cbf4`
 (signal: 11, SIGSEGV: invalid memory reference)


Doing some searching I notice that the onig, syntect and bat crates have all 
had new major versions released.
So I decided to test the latest version of onig on i386, unfortunately that 
failed too.

I then tried doing a test outside of the "debcargo" environment, I first tried 
using
an upstream git checkout but that failed to find it's embedded copy of libonig
so I decided to use cargo clone instead.

cargo install cargo clone
cargo clone onig
cd onig
cargo test

I have reported this upstream at 
https://github.com/rust-onig/rust-onig/issues/155

Bug#973495: mingw-w64-common: Conflicting definition of std::max_align_t with stddef.h of gcc-mingw-w64-i686-posix

[Jonathan Wakely]

This is https://sourceforge.net/p/mingw-w64/bugs/778/

Bug#963551: python3-bitstring: Update, DeprecationWarning

[Matthias Urlichs]

Hello Graham,
>
>> There is another problem: broken backslash sequences trigger a
>> DeprecationWarning. This makes the package unusable with pytest.
> Would you please provide the steps to reproduce this issue?

Correction: only if you tell it to treat all deprecation warnings as
errors, which some packages do in their test runs.

$ cat t.py

import bitstring

$ pytest t.py

 test session starts 

platform linux -- Python 3.8.6rc1, pytest-4.6.9.2.10, py-1.7.0, pluggy-0.13.0
rootdir: /src/bitstring
plugins: anyio-0.0.0, pep8-1.0.6, trio-0.5.2, requests-mock-1.5.2, 
hypothesis-5.32.1, pylint-0.15.1, doctest-custom-1.1.0.dev0, cov-2.8.1, 
asyncio-0.10.0
collected 0 items   
    

= warnings summary 
==
bitstring.py:2
  /src/bitstring/bitstring.py:2: DeprecationWarning: invalid escape sequence \ 
    """

-- Docs: https://docs.pytest.org/en/latest/warnings.html
 1 warnings in 0.04 seconds 
=

$ echo $?
5
$

-- 
-- Matthias Urlichs



signature.asc
Description: OpenPGP digital signature

Bug#973495: mingw-w64-common: Conflicting definition of std::max_align_t with stddef.h of gcc-mingw-w64-i686-posix

[Jonathan Wakely]

A minimal reproducer:

#ifdef STDDEF_FIRST
# include 
#endif
#include 
static_assert( alignof(max_align_t) == 16 );


$ x86_64-w64-mingw32-g++ -c max.cc  -m32 && echo ok
ok
$ x86_64-w64-mingw32-g++ -c max.cc  -m32 -DSTDDEF_FIRST && echo ok
max.cc:6:37: error: static assertion failed
6 | static_assert( alignof(max_align_t) == 16 );
  |~^

The problem is that  includes  after
defining __need_wint_t and __need_wchar_t. GCC's  is
included, which immediately does #include_next , which finds
the base mingw , which does almost nothing because
__need_wint_t and __need_wchar_t are defined:

# 29 "/usr/share/mingw-w64/include/stdint.h" 2 3 4

#define __need_wint_t 
#define __need_wchar_t 
#include 

# 32 "/usr/share/mingw-w64/include/stdint.h" 3 4
# 1 "/usr/lib/gcc/i686-w64-mingw32/10-posix/include/stddef.h" 1 3 4
#include_next 
# 1 "/usr/lib/gcc/i686-w64-mingw32/10-posix/include/stddef.h" 3 4
# 1 "/usr/share/mingw-w64/include/stddef.h" 1 3 4

After defining wchar_t and wint_t the mingw  does almost
nothing else, skipping the rest of that header.

We then return to GCC's , which sees that max_align_t has
not been defined yet, and so defines it (using the modern definition
that includes __float128).

When STDDEF_FIRST is defined in the reproducer above,  is
included without defining __need_wint_t and __need_wchar_t, which
means the base mingw  defines everything, not just those two
types. That includes the old definition of max_align_t, without
__float128. GCC's  sees that _GCC_MAX_ALIGN_T has been
defined, so doesn't both to define it again.

So whether you get the old max_align_t from mingw's  or the
new max_align_t from GCC's  depends on whether 
gets included directly or as a side effect of including some other
header.

The simplest solution would be to just add the __float128 member to
max_align_t in the mingw header.

Bug#973498: RFS: nemo-filename-repairer/4.6.0-1 [ITP] -- Nemo extension for filename encoding repair

[Joshua Peisach]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-filename-repairer":

 * Package name: nemo-filename-repairer
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre , Choe Hwanjin

 * URL : https://community.linuxmint.com/software/view/nemo-
filename-repairer
 * License : GPL-1
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-filename-
repairer
   Section : utils

It builds those binary packages:

  nemo-filename-repairer - Nemo extension for filename encoding repair

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

  https://mentors.debian.net/package/nemo-filename-repairer/

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

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-filename-
repairer/nemo-filename-repairer_4.6.0-1.dsc

If you need, the repo is also hosted on Salsa:
https://salsa.debian.org/ItzSwirlz-guest/nemo-filename-repairer

This bug closes: #973466: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=973466

Changes for the initial release:

 nemo-filename-repairer (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #973466)

Regards,
--
  Joshua Peisach



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

Kernel: Linux 5.8.0-25-generic (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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#973494: plan: Error in append mode

[Petter Reinholdtsen]

[DieSpinne]
> I cannot use Plan in append mode. For example, if I try to schedule an
> appoitment for 7 o' clock with

You might want to know that plan is no longer maintained in Debian.
I've moved to ical on Freedombox myself, and use various ical enabled
calendars instead of plan.

There is even a tool available to migrate the plan database to ical.

-- 
Vennlig hilsen
Petter Reinholdtsen
Once maintainer of plan

Bug#973497: RFS: dmagnetic/0.26-1 -- Interpreter to play textadventures from Magnetic Scrolls in glorious ANSI Art

[dettus]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "dmagnetic":

* Package name : dmagnetic
Version : 0.26-1
Upstream Author : Thomas Dettbarn 
* URL : https://www.dettus.net/dMagnetic/
* License : BSD-2-Clause
* Vcs : [fill in URL of packaging vcs]
Section : games

It builds those binary packages:

dmagnetic - Interpreter to play textadventures from Magnetic Scrolls in 
glorious ANSI Art


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


https://mentors.debian.net/package/dmagnetic/

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

dget -x 
https://mentors.debian.net/debian/pool/main/d/dmagnetic/dmagnetic_0.26-1.dsc


Changes since the last upload:

dmagnetic (0.26-1) unstable; urgency=medium
.
* Update to release 0.26.
* Amstrad CPC images in the DSK format can be used

Regards,


Thomas Dettbarn

Bug#973496: dolphin crashes upon right-click if dolphin-plugins not same version

[Marco Möller]

Package: dolphin
Version: 4:20.08.2-1
Severity: important

Dear Maintainer,
Dolphin crashes upon right-click if dolphin-plugins is not exact same version,
observed in Debian/testing with dolphin 20.08.2 and dolphin-plugins 20.04.2

The crash upon placing a right-click with the mouse somewhere in the Dolphin
app does not occure in other apps or other KDE apps or the KDE Plasma desktop,
it also does not depend on the linux kernel in use. It appears to only appear
in Dolphin.
I first consulted the debian-kde mailing list for advice, and here ist the
relevant text of interest from that conversation:

My provided log text extracted from the KDE Bug Reporting Tool --> Developer
Information:

Application: Dolphin (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7275e01bc0 (LWP 3280))]

Thread 8 (Thread 0x7f725cd6e700 (LWP 3289)):
#0  0x7f72796c035f in __GI___poll (fds=0x7f7240004a60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f7277c19dde in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7277c19eff in g_main_context_iteration () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#3  0x7f7279a8931b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f7279a324db in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f72798598de in QThread::exec() () from /lib/x86_64-linux-
gnu/libQt5Core.so.5
#6  0x7f727985aa01 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f72786adea7 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f72796cad4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f725dca3700 (LWP 3288)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x56084070bbc8) at
../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56084070bb78,
cond=0x56084070bba0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x56084070bba0, mutex=0x56084070bb78) at
pthread_cond_wait.c:638
#3  0x7f726aa3cc9b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7f726aa3c777 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7f72786adea7 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f72796cad4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f725e4a4700 (LWP 3287)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x56084070bbc8) at
../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56084070bb78,
cond=0x56084070bba0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x56084070bba0, mutex=0x56084070bb78) at
pthread_cond_wait.c:638
#3  0x7f726aa3cc9b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7f726aa3c777 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7f72786adea7 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f72796cad4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f725eca5700 (LWP 3286)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x56084070bbc8) at
../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56084070bb78,
cond=0x56084070bba0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x56084070bba0, mutex=0x56084070bb78) at
pthread_cond_wait.c:638
#3  0x7f726aa3cc9b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7f726aa3c777 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7f72786adea7 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f72796cad4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f725f4a6700 (LWP 3285)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x56084070bbc8) at
../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56084070bb78,
cond=0x56084070bba0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x56084070bba0, mutex=0x56084070bb78) at
pthread_cond_wait.c:638
#3  0x7f726aa3cc9b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7f726aa3c777 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7f72786adea7 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f72796cad4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f7269039700 (LWP 3284)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5608408af7bc) at
../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608408af768,
cond=0x5608408af790) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5608408af790, mutex=0x5608408af768) at
pthread_cond_wait.c:638
#3  0x7f726aa3cc9b in ?? () from 

Bug#936809: Processed: severity of 936809 is serious

[Moritz Muehlenhoff]

On Sat, Oct 31, 2020 at 07:22:25PM +0100, Pino Toscano wrote:
> severity 936809 important
> thanks
> 
> Hi Moritz,
> 
> In data domenica 25 ottobre 2020 10:45:05 CET, Debian Bug Tracking System ha 
> scritto:
> > Processing commands for cont...@bugs.debian.org:
> > 
> > > severity 936809 serious
> > Bug #936809 [src:kross-interpreters] kross-interpreters: Python2 removal in 
> > sid/bullseye
> > Severity set to 'serious' from 'normal'
> 
> This bug was already marked py2keep, as it depends only on
> src:python2.7, and we want to ship it in the next stable for now
> (it is not even fixed upstream).
> 
> Hence, lowering its severity to important.

That's not possible, Python 2 is unsupported for run time dependencies in 
Bullseye.

Cheers,
Moritz

Bug#973302: libboost-python1.71.0,: _Py_NewReference undefined in library

[Giovanni Mascellani]

Hi,

thanks for the report!

Il 28/10/20 15:57, Alastair McKinstry ha scritto:

_Py_NewReference undefined in library breaks the package as used in 
python-escript.
See bug #973225


I cannot reproduce that, because if I try to build python-escript with 
sbuild it fails much earlier:



   dh_update_autotools_config -O-v
   dh_autoreconf -O-v
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Build steps for py3
mkdir -p /<>/debian/stage3
scons  -j12   cc_optim=' -O3  '  build_dir=/<>/debian/tmp3 verbose=on 
prefix=/<>/debian/stage3 options_file=debian/sid_options.py docs
scons: Reading SConscript files ...
3.8.6 (default, Sep 25 2020, 09:36:53) 
[GCC 10.2.0]

Building with the following additional flags from debian: [['cpp_flags', '-Wdate-time 
-D_FORTIFY_SOURCE=2'], ['cxx_extra', '-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-uninitialized'], ['ld_extra', '-Wl,-z,relro -Wl,-z,now']]
Using options in debian/sid_options.py.
/bin/sh: 1: svnversion: not found
Using svn revision information from file. Got revision = 6948
Checking whether the C++ compiler works... no
Cannot run C++ compiler 'g++' (check config.log)
make[1]: *** [debian/rules:66: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


This does not seem to be related to Boost. Do you know how to fix this?

On the other hand, I see there is another package (caffe) which fails 
with the same error with Boost 1.71, but succeeds with Boost 1.74 that I 
recently uploaded and will eventually became the default version. 
Hopefully this is the same problem and will be fixed as well.


Giovanni.
--
Giovanni Mascellani 

Bug#973495: mingw-w64-common: Conflicting definition of std::max_align_t with stddef.h of gcc-mingw-w64-i686-posix

[Manuel Bilderbeek]

Package: mingw-w64-common
Version: 8.0.0-1
Severity: important

Dear Maintainer,

When cross compiling for 32-bit Windows, I noticed that some translation units
had a different value for std::max_align_t than others. It appears that (for
some reason), one included it from:
/usr/share/mingw-w64/include/stddef.h
and another from:
/usr/lib/gcc/i686-w64-mingw32/10-posix/include/stddef.h

These have conflicting definitions, see http://paste.debian.net/1169371/

According to people on #gcc IRC:
 the issue seems to be that one of your stddef headers is old and 
predates the addition of __float128 support, which required increasing the 
alignment of max_align_t

If this is true, then something is wrong with the stddef.h in mingw-w64-common,
as it doesn't include that __float128 support. (But I wonder in the first place
why both mingw-w64-common and gcc-mingw-w64-i686-posix provide a stddef.h,
which apparently both can be found and then have a different definition...!?)

Anyway, this is all not my specialism, but I think it's still important to
report it. Please let me know if you need more information. I'll do my best to
provide it.

Thanks for taking a look at this!

Kind regards,
Manuel

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

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#973444: binNMU: ruby packages affected by #972702

[Lucas Kanashiro]

List of packages:

$ apt-file search vendor_ruby | grep '\.so' | cut -d ':' -f 1 | uniq
facter
libgv-ruby
libstfl-ruby
passenger
puma
raspell
ruby-atomic
ruby-augeas
ruby-bcrypt-pbkdf
ruby-bindex
ruby-bootsnap
ruby-cairo
ruby-cairo-gobject
ruby-character-set
ruby-charlock-holmes
ruby-cool.io
ruby-curb
ruby-curses
ruby-dataobjects-mysql
ruby-dataobjects-postgres
ruby-dataobjects-sqlite3
ruby-debian
ruby-debug-inspector
ruby-eb
ruby-ed25519
ruby-escape-utils
ruby-eventmachine
ruby-exif
ruby-fast-blank
ruby-fast-stemmer
ruby-fast-xs
ruby-fcgi
ruby-ferret
ruby-ffi
ruby-ffi-yajl
ruby-fftw3
ruby-filesystem
ruby-fusefs
ruby-gd
ruby-getspg
ruby-gio2
ruby-github-linguist
ruby-github-markdown
ruby-glib2
ruby-gobject-introspection
ruby-god
ruby-gpgme
ruby-grib
ruby-gstreamer
ruby-gtk2
ruby-gtk3
ruby-guestfs
ruby-hamlit
ruby-hdfeos5
ruby-hiredis
ruby-hivex
ruby-http-parser
ruby-http-parser.rb
ruby-json
ruby-kgio
ruby-kyotocabinet
ruby-lapack
ruby-ldap
ruby-levenshtein
ruby-libprelude
ruby-libvirt
ruby-mecab
ruby-mpi
ruby-msgpack
ruby-multibitnums
ruby-multibitnums-dbg
ruby-mysql2
ruby-narray
ruby-ncurses
ruby-netcdf
ruby-nfc
ruby-ngraph
ruby-nio4r
ruby-nokogiri
ruby-nokogumbo
ruby-notmuch
ruby-obexftp
ruby-odbc
ruby-oily-png
ruby-oj
ruby-ox
ruby-pango
ruby-password
ruby-pcaprub
ruby-pg
ruby-posix-spawn
ruby-prof
ruby-prometheus-client-mmap
ruby-psych
ruby-qdbm
ruby-raindrops
ruby-rblineprof
ruby-rbtrace
ruby-rdiscount
ruby-re2
ruby-redcarpet
ruby-redcloth
ruby-regexp-property-values
ruby-remctl
ruby-rinku
ruby-rjb
ruby-rmagick
ruby-rpam-ruby19
ruby-rpatricia
ruby-rrd
ruby-rugged
ruby-sdl
ruby-selinux
ruby-semanage
ruby-sequel-pg
ruby-serialport
ruby-shadow
ruby-sigar
ruby-sqlite3
ruby-strptime
ruby-svn
ruby-termios
ruby-thrift
ruby-timfel-krb5-auth
ruby-tioga
ruby-tokyocabinet
ruby-uconv
ruby-unf-ext
ruby-unicode
ruby-version-sorter
ruby-vmstat
ruby-websocket-driver
ruby-xapian
ruby-xmlhash
ruby-xmlparser
ruby-xmmsclient
ruby-yajl
ruby-zoom
subtle
thin
unicorn
$ apt-file search vendor_ruby | grep '\.so' | cut -d ':' -f 1 | uniq | wc -l
141

-- 
Lucas Kanashiro

Bug#968385: FTBFS on kfreebsd-*

[Jessica Clarke]

On Fri, Aug 14, 2020 at 10:39:22AM +0200, Laurent Bigonville wrote:
> Source: libgc
> Version: 1:8.0.4-2
> Severity: important
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> 
> Hello,
> 
> libgc FTBFS on kfreebsd-*
> 
> This is happening because some symbols are marked in the symbols file as
> non-existant on these architectures while they are actually existing.
> 
> Shouldn't the symbols file be adjusted? Or are these symbols really not
> supposed to be present?

For the record, it seems that having the symbols appear is correct. The
last successful build was 1:7.6.4-0.4, with the next build in unstable,
1:8.0.4-1, failing (experimental failed but only due to aptitude itself
being uninstallable) with the symbol error. Looking at the changelog,
7.6.6 has the following entry:

* Define GC_FREEBSD_THREADS and GC_ADD_CALLER macros for kFreeBSD

Given that the symbols that started to appear are guarded by
PARALLEL_MARK, I assume this means that PARALLEL_MARK started to be
enabled as a result of having threading enabled.

Jess

Bug#973472: fetchmail: Fails to connect using SSL

[Klaumi Klingsporn]

On Sat, 31 Oct 2020 19:50:09 +0100 Klaumi Klingsporn
 wrote:

> I think it's because the new version of fetrchmail is
> compiled against openssl in sid, which is blocked there
> because of regressions.

As I thought: I rebuilt the fetchmail 6.4.13-1 package in
testing against the openssl-libraries in testing and voilá
all works fine again!

As a workaround you can find my fetchmail-package
6.4.13-1~kmk1 at 

apt.klaumikli.de/testing

Dear maintainer,
it would be nice, if you updated the package in unstable to
version 6.4.13-2 and changed the dependencies for libssl1.1
to '(=1.1.1h)'. Fetchmail seems to worry about the
libraries it is compiled against.

Have a nice day again!

Klaumi



---
Klaus-Michael Klingsporn 
mail: klaumi...@gmx.de
web: www.klaumikli.de

Bug#956285: Problems identified in debian/copyright

[Moritz Mühlenhoff]

On Thu, Oct 29, 2020 at 03:14:44PM +0100, Petter Reinholdtsen wrote:
> [Moritz Mühlenhoff]
> > JFTR, this is fixed in 1.2.9
> 
> Great.  Now if the maintainer or someone else could just upload it to
> unstable, my vlc-plugin-bittorrent package would have a fighting chance
> to become part of Bullseye...
> 
> Cristian or Andrew, please, do you have time to have a look?

Actually 1.2.9 seems even present in salsa.git

Cheers,
Moritz

Bug#973459: uim: FAIL: test-composer.scm

[Dmitry Shachnev]

Control: unblock 972278 by -1

On Sat, Oct 31, 2020 at 09:53:26AM +0200, Adrian Bunk wrote:
> On Fri, Oct 30, 2020 at 11:38:09PM +0100, Sebastian Ramacher wrote:
> >...
> > uim failed to build on armel:
> >...
>
> It built for me on abel, which is exactly the same hardware as the 
> buildds where it failed.
>
> This makes it feel more like a generic race condition that only happened
> to hit here than an armel-specific bug.

Indeed, after the second retry uim built fine.

Removing the block, but not closing because a race condition may be a
valid bug.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#973493: src:rust-log: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: rust-log
Version: 0.4.8-4
Severity: serious
Control: close -1 0.4.11-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 970463

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:rust-log in
its current version in unstable has been trying to migrate for 61 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-log




signature.asc
Description: OpenPGP digital signature

Bug#973492: abseil: Please consider explicitly enable -latomic with armel build

[Boyuan Yang]

Source: abseil
Severity: important
Version: 0~20200923.1-1
X-Debbugs-CC: bba...@debian.org
Tags: patch

Dear Debian abseil maintainer,

One of the packages I maintain build-depends on abseil library. As
indicated in https://buildd.debian.org/status/package.php?p=libgav1 ,
it currently fails to build for armel due to the following reason:

/usr/bin/ld: /usr/lib/arm-linux-
gnueabi/libabsl_debugging_internal.so.20200923: undefined reference to
`__atomic_compare_exchange_8'
/usr/bin/ld: /usr/lib/arm-linux-
gnueabi/libabsl_spinlock_wait.so.20200923.0.0: undefined reference to
`__atomic_load_8'
/usr/bin/ld: /usr/lib/arm-linux-
gnueabi/libabsl_spinlock_wait.so.20200923.0.0: undefined reference to
`__atomic_store_8'

Looking into the buildlog of abseil of armel (
https://buildd.debian.org/status/fetch.php?pkg=abseil=armel=0%7E20200923.1-1=1602525704=0
), I found some related information:

dpkg-shlibdeps: warning: symbol __atomic_load_8 used by
debian/libabsl20200923/usr/lib/arm-linux-
gnueabi/libabsl_flags_internal.so.20200923.0.0 found in none of the
libraries
dpkg-shlibdeps: warning: symbol __atomic_store_8 used by
debian/libabsl20200923/usr/lib/arm-linux-
gnueabi/libabsl_flags_internal.so.20200923.0.0 found in none of the
libraries

I am not familiar with ARM so I did some googling. It seems that one
way to circumvent this issue is to explicitly add "-latomic" during
building for armel. I enabled this flag in my libgav1 build but it was
not working. So my guess is that you might need to enable the flag in
the build of abseil library.

If you find it reasonable, please consider adding the following lines
in the front of debian/rules file:

ifneq (,$(filter $(DEB_HOST_ARCH), armel))
  export DEB_LDFLAGS_MAINT_APPEND=-latomic
endif

Hope this patch can fix the build error of libgav1. Let me know if you
have any thoughts.

Thanks,
Boyuan Yang


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

Bug#973472: fetchmail: Fails to connect using SSL

[Klaumi Klingsporn]

On Sat, 31 Oct 2020 09:39:46 +0100 Alex Bernier
 wrote:
> Package: fetchmail
> Version: 6.4.13-1
> Severity: important
> 
> Connections using SSL fails with the following error
> message :
> 
> fetchmail: Loaded OpenSSL library 0x1010107f older than
> headers 0x1010108f, refusing to work. 

Same here! Since todays upgrade in testing fetchmail doesn't
work any more:
"fetchmail: Loaded OpenSSL library 0x1010107f older than
headers 0x1010108f, refusing to work."

I think it's because the new version of fetrchmail is
compiled against openssl in sid, which is blocked there
because of regressions.

This should not happen! Most people will only recognize it
after hours or even days!

klaumi

---
Klaus-Michael Klingsporn 
mail: klaumi...@gmx.de
web: www.klaumikli.de

Bug#936809: Processed: severity of 936809 is serious

[Pino Toscano]

severity 936809 important
thanks

Hi Moritz,

In data domenica 25 ottobre 2020 10:45:05 CET, Debian Bug Tracking System ha 
scritto:
> Processing commands for cont...@bugs.debian.org:
> 
> > severity 936809 serious
> Bug #936809 [src:kross-interpreters] kross-interpreters: Python2 removal in 
> sid/bullseye
> Severity set to 'serious' from 'normal'

This bug was already marked py2keep, as it depends only on
src:python2.7, and we want to ship it in the next stable for now
(it is not even fixed upstream).

Hence, lowering its severity to important.

Thanks,
-- 
Pino Toscano

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

Bug#971589: clazy's test suite uses the default clang, while the package uses the versioned one

[Pino Toscano]

severity 971589 important
tag 971589 + needinfo
thanks

Hi,

In data venerdì 2 ottobre 2020 13:12:19 CET, Matthias Klose ha scritto:
> Package: src:clazy
> Version: 1.7-3
> Severity: serious
> Tags: sid bullseye
> 
> This is seen when updating llvm-defaults to point to 11, and then running the
> autopkg test.  The test tries to run with the updated default clang (11), but
> the package is still built using the previous 10 version.  The package itself
> uses a versioned clang for building, and also gets this dependency encoded in
> the package.  The plugins are not compatible across versions, so the test 
> should
> always use the version that the package was built for.

clazy will run against the clang version it was built with. The two
unversioned invocations of clang are done only for diagnostic (one by
the run-tests autopkgtest, and one by the upstream script used for
testing).

Considering the situation described is already what happens, I'm
lowering the severity, and requesting for more information.

-- 
Pino Toscano

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

Bug#973387: [Pkg-rust-maintainers] Bug#973387: does debian's libclang-dev support static linking?

[peter green]

Severity 973387 normal
Retitle 973387 rust-bindgen cannot be built with "static" feature.

On 29/10/2020 19:44, Sylvestre Ledru wrote:

Hello,

Le 29/10/2020 à 20:39, peter green a écrit :

I was looking at an autopkgtest failure in rust-bindgen. The failure happened when when 
testing with the "static"
feature. It appears the failure was caused by a lack of libclang.a

We should disable this test in bindgen probably.

I have gone ahead and done that for now, but I find shipping binary packages 
for featuresets that can't actually be
built questionable. In the longer term IMO it should be either fixed or dropped.

Bug#973449: qtbase-opensource-src FTCBFS for ppc64el: missing spec file

[Dmitry Shachnev]

Hi Helmut!

On Fri, Oct 30, 2020 at 08:20:19PM +0100, Helmut Grohne wrote:
> Source: qtbase-opensource-src
> Version: 5.15.1+dfsg-2
> Tags: patch upstream
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
>
> qtbase-opensource-src still fails to cross build. When you attempt to
> cross build it for ppc64el it fails quite early, because it lacks
> mkspecs. For some reason, qt needs these for every single architecture
> even though they could be generated automatically. I'm attaching the
> patch for ppc64el based on the relevant arm64 files, but I do wonder
> whether this could be solved generically somehow. Any ideas?

Using a separate mkspec for every possible architecture is the upstream
approach for cross-building.

In Debian I was trying to use a different approach for cross-compiling
Qt applications and modules (except qtbase): using a generic mkspec
(linux-g++) and specifying the toolchain in a qt.conf file.

Ideally a similar thing should be used for qtbase. The configure script
does not seem to support passing qt.conf file, but one can pass variables
like QMAKE_CXX=... etc to it.

(Unfortunately I don't have time to look at it now.)

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#973404: (no subject)

[Jérôme Pasquier]

Hi,

I confirm this issue. I have the same laptop (Thinkpad T14 amd), the same 
kernel (debian bullseye, kernel 5.9.1) and the same problem (mic does not work).

The microphone works out-of-the-box with a live CD of Manjaro XFCE 20.1.

Thank you

Bug#973453: RFS: liboauth/1.0.3-4 -- C library implementing OAuth Core 1.0a API (runtime)

[Tobias Frost]

On Sat, Oct 31, 2020 at 02:48:21PM +0100, Laurin Hagemann wrote:

> I noticed (https://mentors.debian.net/package/liboauth/) that "Package closes
> bugs in a wrong way", which I don't understand, because I executed the retitle
> command once before the upload but it is getting ignored, even if I try again
> now:
> ```
> $ bts retitle 973473 "ITA: liboauth -- C library implementing OAuth Core 1.0a
> API (development files)"
> $ bts status 973473bug_num 973473
> ...
> subject O: liboauth -- C library implementing OAuth Core 1.0a API (development
> files)
> ...
> I also tried to perform the same action via email to cont...@bugs.debian.org -
> no success.
> Can you help me out here? What am I doing wrong?

I see that eventually the change reached the BTS…
Probably you've waited not long enough…
BTS interactions are not instant. Its mail based and can take a few minutes.

PS: Your public GPG key adds a lots of noise to the bug. Do you really
need it to be added to every mail?

-- 
tobi

Bug#971068: linux-image-5.8.0-2-686-pae: Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation

[наб]

retitle 971068 linux-image-5.9.0-1-686-pae: Assertion failure in i915 
intel_display.c#assert_plane() after resume from hibernation
found 971068 5.9.1-1
thanks

Turns out the delay was because my system was horriby starved for I/O,
switching to an SSD revealed that the display is ready immediately after
unhibernating, so the impact of this is low.

Here's the crashes for 5.9.1-1 (uname -a:
Linux nabtop 5.9.0-1-686-pae #1 SMP Debian 5.9.1-1 (2020-10-17) i686 GNU/Linux):

-- >8 --
Oct 31 17:30:48 nabtop kernel: [ cut here ]
Oct 31 17:30:48 nabtop kernel: primary B assertion failure (expected off, 
current on)
Oct 31 17:30:48 nabtop kernel: WARNING: CPU: 1 PID: 31490 at 
drivers/gpu/drm/i915/display/intel_display.c:1299 assert_plane+0xb9/0xd0 [i915]
Oct 31 17:30:48 nabtop kernel: Modules linked in: tcp_diag udp_diag raw_diag 
inet_diag unix_diag af_packet_diag netlink_diag cuse fuse nls_utf8 cifs 
dns_resolver fscache zram zsmalloc ghash_generic gf128mul gcm ccm algif_aead 
des_generic libdes ctr cbc ecb algif_skcipher bnep cmac sha512_generic md4 
algif_hash af_alg binfmt_misc zfs(POE) zunicode(POE) zlua(POE) zcommon(POE) 
znvpair(POE) zavl(POE) icp(POE) spl(OE) joydev btusb btrtl btbcm btintel 
bluetooth jitterentropy_rng uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_common drbg videodev mc aes_generic crypto_simd cryptd 
ansi_cprng ecdh_generic ecc libaes snd_hda_codec_conexant snd_hda_codec_generic 
ledtrig_audio i915 iTCO_wdt iwldvm intel_pmc_bxt snd_hda_intel 
iTCO_vendor_support kvm_intel snd_intel_dspcfg watchdog mac80211 kvm 
snd_hda_codec libarc4 nls_ascii irqbypass snd_hda_core iwlwifi snd_hwdep 
i2c_i801 wmi_bmof pcspkr psmouse i2c_smbus evdev nls_cp437 snd_pcm vfat 
cfg80211 sg fat drm_kms_helper sky2 lpc_ich snd_timer
Oct 31 17:30:48 nabtop kernel:  toshiba_acpi snd cec soundcore industrialio 
i2c_algo_bit sparse_keymap toshiba_bluetooth rfkill toshiba_haps ac button 
acpi_cpufreq nft_counter nf_log_ipv6 nf_log_ipv4 nf_log_common nft_log 
nft_limit nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables 
nfnetlink drm ip_tables x_tables ext4 crc16 mbcache jbd2 crc32c_generic sd_mod 
t10_pi crc_t10dif sr_mod crct10dif_generic cdrom crct10dif_common uhci_hcd 
ehci_pci ehci_hcd sdhci_pci cqhci ahci libahci libata sdhci serio_raw mmc_core 
firewire_ohci usbcore usb_common wmi battery video pkcs8_key_parser coretemp 
firewire_sbp2 firewire_core crc_itu_t scsi_mod parport_pc ppdev lp parport 
autofs4
Oct 31 17:30:48 nabtop kernel: CPU: 1 PID: 31490 Comm: kworker/u4:4 Tainted: P  
  W  OE 5.9.0-1-686-pae #1 Debian 5.9.1-1
Oct 31 17:30:48 nabtop kernel: Hardware name: TOSHIBA Satellite Pro 
U400/Satellite Pro U400, BIOS V5.0010/26/2010
Oct 31 17:30:48 nabtop kernel: Workqueue: events_unbound async_run_entry_fn
Oct 31 17:30:48 nabtop kernel: EIP: assert_plane+0xb9/0xd0 [i915]
Oct 31 17:30:48 nabtop kernel: Code: 90 b9 f6 72 bd f8 84 c0 ba f2 72 bd f8 89 
c8 0f 44 c2 89 c7 89 f0 84 c0 57 0f 45 d1 52 ff 73 0c 68 08 9f bb f8 e8 e7 8d 
56 df <0f> 0b 83 c4 10 e9 70 ff ff ff e8 f8 9f c9 df 8d b4 26 00 00 00 00
Oct 31 17:30:48 nabtop kernel: EAX: 0036 EBX: ecf17000 ECX: f6fe5140 EDX: 
ffd8
Oct 31 17:30:48 nabtop kernel: ESI:  EDI: f8bd72f6 EBP: d3ad9cc4 ESP: 
d3ad9ca0
Oct 31 17:30:48 nabtop kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010292
Oct 31 17:30:48 nabtop kernel: CR0: 80050033 CR2:  CR3: 18bb2000 CR4: 
06f0
Oct 31 17:30:48 nabtop kernel: Call Trace:
Oct 31 17:30:48 nabtop kernel:  intel_disable_pipe+0x81/0x210 [i915]
Oct 31 17:30:48 nabtop kernel:  i9xx_crtc_disable+0x6c/0x310 [i915]
Oct 31 17:30:48 nabtop kernel:  ? __pm_runtime_resume+0x58/0x80
Oct 31 17:30:48 nabtop kernel:  ? gen2_read8+0x170/0x170 [i915]
Oct 31 17:30:48 nabtop kernel:  ? intel_synchronize_irq+0x19/0x20 [i915]
Oct 31 17:30:48 nabtop kernel:  ? intel_crtc_disable_pipe_crc+0x9b/0xb0 [i915]
Oct 31 17:30:48 nabtop kernel:  ? i830_enable_pipe+0x520/0x520 [i915]
Oct 31 17:30:48 nabtop kernel:  intel_old_crtc_state_disables+0x106/0x160 [i915]
Oct 31 17:30:48 nabtop kernel:  intel_atomic_commit_tail+0xcb2/0x12c0 [i915]
Oct 31 17:30:48 nabtop kernel:  ? __schedule+0x27a/0x940
Oct 31 17:30:48 nabtop kernel:  ? add_wait_queue_exclusive+0x60/0x60
Oct 31 17:30:48 nabtop kernel:  ? add_wait_queue_exclusive+0x60/0x60
Oct 31 17:30:48 nabtop kernel:  intel_atomic_commit+0x325/0x3b0 [i915]
Oct 31 17:30:48 nabtop kernel:  ? intel_atomic_commit+0x325/0x3b0 [i915]
Oct 31 17:30:48 nabtop kernel:  ? intel_atomic_commit_tail+0x12c0/0x12c0 [i915]
Oct 31 17:30:48 nabtop kernel:  drm_atomic_commit+0x3a/0x50 [drm]
Oct 31 17:30:48 nabtop kernel:  
drm_atomic_helper_commit_duplicated_state+0xb6/0xd0 [drm_kms_helper]
Oct 31 17:30:48 nabtop kernel:  __intel_display_resume+0x73/0xd0 [i915]
Oct 31 17:30:48 nabtop kernel:  intel_display_resume+0x75/0xe0 [i915]
Oct 31 17:30:48 nabtop kernel:  i915_drm_resume+0xb2/0x110 [i915]
Oct 31 17:30:48 

Bug#973038: autopkgtest-build-qemu installs grub-pc on arm64 which is unavailable

[Christian Kastner]

On 10/31/20 4:42 PM, Ryutaroh Matsumoto wrote:
> (2) For arm emulation of autopkgtest-virt-qemu, I am in the mood of giving up.
> See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973484
> if you have interest...

That sounds like a major road block indeed, unfortunately...

Bug#973491: debian-policy: ch-opersys refers to wrong manpage section for systemd.unit

[Martin Schwarz]

Package: debian-policy
Version: 4.3.0.3
Severity: minor

Dear Maintainer,

policy.html/ch-opersys.html (and
policy.html/_sources/ch-opersys.rst.txt) contains a reference to
  "the man page systemd.unit(8)."

However, I couldn't find that manual page in section 8 -- but there is
one in section 5.

So the text should probably be changed to refer to
  "the man page systemd.unit(5)."

Thanks!

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

Kernel: Linux 4.19.0-12-amd64 (SMP w/1 CPU core)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

debian-policy depends on no packages.

Versions of packages debian-policy recommends:
ii  libjs-sphinxdoc  1.8.4-1

Versions of packages debian-policy suggests:
pn  doc-base  

-- no debconf information

Bug#973490: libsane: plustek fails to detect scanner, prints sanei_access_lock failed: 11

[Gregor Riepl]

Package: libsane
Version: 1.0.31-2
Severity: important
X-Debbugs-Cc: onit...@gmail.com

Dear Maintainer,

sane seems to have trouble interacting with certain USB scanners.
In particular: A Canon LiDE30 scanner, which is fully supported by the plustek
driver.

USB device permissions don't seem to be the problem, all udev rules are in
place, the workstation user is in the scanner group, and sane-find-scanner
correctly repost the scanner model.

Yet, when running scanimage -L, no scanner is found.

Enabling sane-plustek debug messages reveals that it is somehow not able to
lock the device:

[18:09:01.316974] [plustek] usbDev_open(auto,) - 0x5631a0273570
[18:09:01.316987] [plustek] sanei_access_lock failed: 11
[18:09:01.316994] [plustek] open failed: -1
[18:09:01.317001] [plustek] sane_get_devices (0x7ffd2dd4f860, 0)
scanimage: no SANE devices found

(the rest of the log file is attached)

I found an older message on the sane-devel list that points to a lock file
access problem: https://alioth-lists.debian.net/pipermail/sane-
devel/2005-August/014301.html
It doesn't look like the path is correct for recent sane versions though, or
this may be a red herring.

Is this a bug in sane or sane-plustek? Do I need to fix some permissions?



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

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

Versions of packages libsane depends on:
ii  libsane1  1.0.31-2

libsane recommends no packages.

libsane suggests no packages.

-- no debconf information
[18:10:42.055792] [sanei_debug] Setting debug level of plustek to 255.
[18:10:42.055878] [plustek] Plustek backend V0.52-12, part of sane-backends 
1.0.31-debian
[18:10:42.055889] [plustek] Retrieving all supported and conntected devices
[18:10:42.055895] [plustek] Checking for 0x07b3-0x0010
[18:10:42.055901] [plustek] Checking for 0x07b3-0x0011
[18:10:42.055906] [plustek] Checking for 0x07b3-0x0013
[18:10:42.055912] [plustek] Checking for 0x07b3-0x0017
[18:10:42.055917] [plustek] Checking for 0x07b3-0x0015
[18:10:42.055922] [plustek] Checking for 0x07b3-0x0015
[18:10:42.055927] [plustek] Checking for 0x07b3-0x0017
[18:10:42.055933] [plustek] Checking for 0x07b3-0x0013
[18:10:42.055938] [plustek] Checking for 0x07b3-0x0011
[18:10:42.055943] [plustek] Checking for 0x07b3-0x0010
[18:10:42.055948] [plustek] Checking for 0x07b3-0x0014
[18:10:42.055954] [plustek] Checking for 0x07b3-0x0014
[18:10:42.055959] [plustek] Checking for 0x07b3-0x0016
[18:10:42.055964] [plustek] Checking for 0x07b3-0x0017
[18:10:42.055969] [plustek] Checking for 0x07b3-0x0017
[18:10:42.055974] [plustek] Checking for 0x07b3-0x0007
[18:10:42.055980] [plustek] Checking for 0x07b3-0x000f
[18:10:42.055985] [plustek] Checking for 0x07b3-0x000f
[18:10:42.055990] [plustek] Checking for 0x07b3-0x0005
[18:10:42.055996] [plustek] Checking for 0x07b3-0x0014
[18:10:42.056001] [plustek] Checking for 0x07b3-0x0012
[18:10:42.056006] [plustek] Checking for 0x0400-0x1000
[18:10:42.056011] [plustek] Checking for 0x0400-0x1001
[18:10:42.056017] [plustek] Checking for 0x0400-0x1001
[18:10:42.056022] [plustek] Checking for 0x0458-0x2007
[18:10:42.056027] [plustek] Checking for 0x0458-0x2008
[18:10:42.056032] [plustek] Checking for 0x0458-0x2009
[18:10:42.056037] [plustek] Checking for 0x0458-0x2013
[18:10:42.056043] [plustek] Checking for 0x0458-0x2015
[18:10:42.056048] [plustek] Checking for 0x0458-0x2016
[18:10:42.056053] [plustek] Checking for 0x03f0-0x0505
[18:10:42.056058] [plustek] Checking for 0x03f0-0x0605
[18:10:42.056064] [plustek] Checking for 0x04b8-0x010f
[18:10:42.056069] [plustek] Checking for 0x04b8-0x011d
[18:10:42.056074] [plustek] Checking for 0x1606-0x0050
[18:10:42.056079] [plustek] Checking for 0x1606-0x0060
[18:10:42.056085] [plustek] Checking for 0x1606-0x0160
[18:10:42.056090] [plustek] Checking for 0x049f-0x001a
[18:10:42.056095] [plustek] Checking for 0x04a9-0x2206
[18:10:42.056100] [plustek] Checking for 0x04a9-0x2207
[18:10:42.056106] [plustek] Checking for 0x04a9-0x2208
[18:10:42.056111] [plustek] Checking for 0x04a9-0x220d
[18:10:42.056116] [plustek] Checking for 0x04a9-0x220e
[18:10:42.056122] [plustek] Checking for 0x04a9-0x2220
[18:10:42.056127] [plustek] Checking for 0x0a82-0x4600
[18:10:42.056132] [plustek] Checking for 0x0a82-0x6620
[18:10:42.056137] [plustek] Checking for 0x04a7-0x0427
[18:10:42.056143] [plustek] Checking for 0x0a53-0x1000
[18:10:42.056148] [plustek] Checking for 0x0a53-0x2000
[18:10:42.056153] [plustek] Available and supported devices:
[18:10:42.056158] [plustek] Device: >libusb:001:010< - 

Bug#972839: buster-pu: package systemd/241-7~deb10u5

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2020-10-24 at 21:28 +0200, Michael Biebl wrote:
> I'd like to make a stable upload for systemd fixing two issues:
> 
> - #963488
>   systemd-network assigns a random network address to bridge
> interfaces
>   Helmut Grohne explicitly asked for a back port of this specific fix
> 
> https://salsa.debian.org/systemd-team/systemd/-/commit/99e4b8f0c74731b4a80fa7ed8c31c540a69cc997
> 
> 
> - #964926
>   systemctl show  prints "Failed to parse bus message:
> Invalid  argument" before output
> 
> Reported by several people running buster with a kernel >= 5.8
> (either self-compiled or via bpo)

Please go ahead.

Regards,

Adam

Bug#973489: libvirt-daemon-system: upgrade overwrites generated file /etc/libvirt/qemu/networks/default.xml

[Thorsten Glaser]

Package: libvirt-daemon-system
Version: 6.8.0-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de

I suspect this file should not have been a conffile, i.e. not
shipped in /etc (but somewhere under /usr and copied to /etc
during postinst).

NOTE: Migrating to _that_ setup is dangerous as well, see #971683
for what can happen when done naïvely.

[…]
Preparing to unpack .../23-libvirt-daemon-system_6.8.0-1_amd64.deb ...
Unpacking libvirt-daemon-system (6.8.0-1) over (6.6.0-2) ...
[…]
Setting up libvirt-daemon (6.8.0-1) ...
Setting up libvirt-daemon-driver-qemu (6.8.0-1) ...
Setting up libvirt-daemon-system (6.8.0-1) ...
Installing new version of config file /etc/apparmor.d/abstractions/libvirt-qemu 
...
Installing new version of config file /etc/apparmor.d/usr.sbin.libvirtd ...
Installing new version of config file /etc/libvirt/libvirtd.conf ...

Configuration file '/etc/libvirt/qemu/networks/default.xml'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** default.xml (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/libvirt/qemu/networks/default.xml  2015-06-03 22:04:56.021794155 
+0200
+++ /etc/libvirt/qemu/networks/default.xml.dpkg-new 2020-10-01 
09:50:39.0 +0200
@@ -1,16 +1,7 @@
-
-
 
   default
-  aaf572f9-67bf-4d32-9d39-ffca92ff9784
-  
-  
-  
+  
+  
   
 
   

Configuration file '/etc/libvirt/qemu/networks/default.xml'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** default.xml (Y/I/N/O/D/Z) [default=N] ? _


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

Kernel: Linux 5.9.0-1-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libvirt-daemon-system depends on:
ii  adduser 3.118
ii  debconf [debconf-2.0]   1.5.74
ii  gettext-base0.19.8.1-10
ii  iptables1.8.5-3
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-16
ii  libglib2.0-02.66.1-2
ii  libvirt-clients 6.8.0-1
iu  libvirt-daemon  6.8.0-1
ii  libvirt-daemon-system-sysv  6.8.0-1
ii  libvirt06.8.0-1
ii  libxml2 2.9.10+dfsg-6.2
ii  logrotate   3.17.0-1
ii  policykit-1 0.105-29

Versions of packages libvirt-daemon-system recommends:
ii  dmidecode 3.2-4
pn  dnsmasq-base  
ii  iproute2  5.9.0-1
pn  mdevctl   
ii  parted3.3-4

Versions of packages libvirt-daemon-system suggests:
pn  apparmor
pn  auditd  
pn  nfs-common  
pn  open-iscsi  
pn  pm-utils
pn  radvd   
pn  systemd 
pn  systemtap   
pn  zfsutils

-- Configuration Files:
/etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-arp.xml'
/etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-dhcp-server.xml'
/etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-dhcp.xml'
/etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
/etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/allow-ipv4.xml'
/etc/libvirt/nwfilter/clean-traffic-gateway.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml'
/etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic.xml'
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-arp-spoofing.xml'
/etc/libvirt/nwfilter/no-ip-multicast.xml 

Bug#973455: locales: kab_DZ.UTF-8 not supported?

[Aurelien Jarno]

Hi,

On 2020-10-30 22:00, Holger Wansing wrote:
> Package: glibc
> Severity: normal
> X-Debbugs-CC: Slimane Selyan Amiri 
> X-Debbugs-CC: debian-b...@lists.debian.org
> 
> 
> Hi,
> 
> we are currently in the process of adding Kabyle as a new language to our
> debian-installer.
> 
> The locale settings for the Kabyle language are supposed to be 
>   language: Kabyle - kab
>   country:  Algeria - DZ
>   -> kab_DZ
> 
> I have added Kabyle to the localechooser package, and it correctly shows up as
> a language in the "Choose language" dialog.

I confirm that the kab_DZ is available in glibc, it has been added in
version 2.27. You can also check that the date is properly displayed on
a running Debian system.

$ LC_ALL=kab_DZ date
Sed 31 Tub 2020 17:36:48 CET

> But I have a problem now in the text-based installer:
> (in graphical installer everything is ok!)
> While displaying the installer dialogs in Kabyle is fine, it fails to switch
> the keyboard to the desired "Berber (Latin)" layout.

Keyboard layout is not something handled by the glibc locales.

> I also noticed that the installer states to use "kab_DZ" as locale, while
> in the other languages there is an UTF-8 locale (like "de_DE.UTF-8" for 
> German).
> Maybe that's the reason for the installer failing to switch keyboard 
> correctly ... ?

This is correct, because the kab_DZ locale is only available as UTF-8.
de_DE.UTF-8 exists because the default de_DE locale is ISO-8859-1
encoded. The same way there is also a de_DE@euro locale defaulting to
ISO-8859-15.
 
> When diagnosing the list of supported locales, I see that in locales package
> the situation is the same:
> 
> ned@t520:~$ grep kab /usr/share/i18n/SUPPORTED 
> kab_DZ UTF-8
> ned@t520:~$ 
> 
> Only "kab_DZ" shows up in /usr/share/i18n/SUPPORTED, instead of
> "kab_DZ.UTF-8/UTF-8" like for many other languages.

This is perfectly normal. There are many other locales without UTF-8 in
their name, see for example fy_DE or en_NG.

> Please accept my appologies, if I got something wrong here, but for me it
> seems there is something wrong/missing... ?
> Shouldn't UTF-8 be the default for years already? 
> (Hmm, not for all languages/locales maybe ... ?)

Yes, that's exactly because UTF-8 is the default for years already that the
Kabylian locale is only available as kab_DZ.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#973476: src:enigmail: autopkgtest failure (unit tests gone)

[Michael Biebl]

Am 31.10.20 um 11:34 schrieb Gregor Riepl:

Package: src:enigmail
Version: 2:2.2.4-0.1
Severity: normal
Tags: patch
X-Debbugs-Cc: onit...@gmail.com, jcris...@debian.org, bi...@debian.org

After uploading 2:2.2.4-0.1 to buildd, we now have autopkgtest failures:
https://ci.debian.net/data/autopkgtest/testing/amd64/e/enigmail/7837910/log.gz

The reason for these is that the unit test target is gone in 2.2.4.

Please apply the attached patch to drop the "make unit" from autopkgtest.



Thanks for the patch, Gregor.
I tried to run the autopkgtest suite (using the lxc runner), but this 
fails here:



...
autopkgtest [15:09:22]: test tbird-sqlite: [---
*** You are running in headless mode.
[calBackendLoader] Using Thunderbird's libical backend
console.warn: Lightning: Warning:  Using guessed timezone
  Africa/Abidjan (UTC+).
This ZoneInfo timezone seems to match the operating system timezone this 
year.

This ZoneInfo timezone was chosen based on matching the operating system
timezone with known timezones in alphabetical order of timezone id.


At this point, autopkgtest just hangs.



I guess the tests need further tweaks.


Michael

Bug#973488: RFS: lebiniou-data/3.50-1 -- datafiles for Le Biniou

[Olivier Girondel]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "lebiniou-data":

 * Package name: lebiniou-data
   Version : 3.50-1
   Upstream Author : Olivier Girondel 
 * URL : https://biniou.net
 * License : GPL-2+
   Section : graphics

It builds this binary package:

lebiniou-data - datafiles for Le Biniou

The package appears to be lintian-clean.

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

  https://mentors.debian.net/package/lebiniou-data


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

  dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou-data/lebiniou-data_3.50-1.dsc

Changes since the last upload:

  * New upstream release 3.50.
  * debian/control: Breaks: lebiniou << 3.50.

Regards,
  Olivier Girondel

Bug#973487: anbox: Anbox can't start: "/run/anbox-container.socket: No such file or directory"

[Shengjing Zhu]

On Sun, Nov 1, 2020 at 12:03 AM Teo  wrote:
>
> Package: anbox
> Version: 0.0~git20200526-1+b2
> Severity: important
> Tags: patch
> X-Debbugs-Cc: teodoro777.coluc...@live.com
>
> I installed anbox, then I loaded ashmen and binder kernel drivers with
> "modprobe ashmem_linux" and "modprobe binder_linux". So I enabled and started
> the service with "systemctl enable anbox-container-manager.service" and
> "systemctl start anbox-container-manager.service", but but it continues to
> crash at the start on a graphic level.
> Indeed with "anbox session-manager" it returns "[daemon.cpp:61@Run] Failed to
> connect to socket /run/anbox-container.socket: No such file or directory".

It means your anbox-container-manager.service is not started successfully.
Have you followed the instruction in /usr/share/doc/anbox/README.Debian?

-- 
Shengjing Zhu

Bug#973487: anbox: Anbox can't start: "/run/anbox-container.socket: No such file or directory"

[Teo]

Package: anbox
Version: 0.0~git20200526-1+b2
Severity: important
Tags: patch
X-Debbugs-Cc: teodoro777.coluc...@live.com

I installed anbox, then I loaded ashmen and binder kernel drivers with
"modprobe ashmem_linux" and "modprobe binder_linux". So I enabled and started
the service with "systemctl enable anbox-container-manager.service" and
"systemctl start anbox-container-manager.service", but but it continues to
crash at the start on a graphic level.
Indeed with "anbox session-manager" it returns "[daemon.cpp:61@Run] Failed to
connect to socket /run/anbox-container.socket: No such file or directory".



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

Kernel: Linux 5.8.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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

Versions of packages anbox depends on:
ii  init-system-helpers 1.58
ii  iptables1.8.5-3
ii  libboost-filesystem1.71.0   1.71.0-7+b1
ii  libboost-iostreams1.71.01.71.0-7+b1
ii  libboost-log1.71.0  1.71.0-7+b1
ii  libboost-program-options1.71.0  1.71.0-7+b1
ii  libboost-thread1.71.0   1.71.0-7+b1
ii  libc6   2.31-4
ii  libegl1 1.3.2-1
ii  libgcc-s1   10.2.0-15
ii  libgles21.3.2-1
ii  liblxc1 1:4.0.4-5
ii  libprotobuf-lite23  3.12.3-2+b1
ii  libsdl2-2.0-0   2.0.12+dfsg1-4
ii  libsdl2-image-2.0-0 2.0.5+dfsg1-2
ii  libstdc++6  10.2.0-15
ii  libsystemd0 246.6-2
ii  lxc 1:4.0.4-5

Versions of packages anbox recommends:
ii  dbus-user-session  1.12.20-1

anbox suggests no packages.

-- no debconf information

Bug#973486: RFS: lebiniou/3.50-1 -- displays images that evolve with sound

[Olivier Girondel]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "lebiniou":

 * Package name: lebiniou
   Version : 3.50-1
   Upstream Author : Olivier Girondel 
 * URL : https://biniou.net
 * License : GPL-2+
   Section : graphics

It builds this binary package:

  lebiniou - displays images that evolve with sound

The package appears to be lintian-clean.

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

  https://mentors.debian.net/package/lebiniou

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

  dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou/lebiniou_3.50-1.dsc

Changes since the last upload:

  * New upstream release 3.50.
  * debian/control: Depends: Add libjs-jquery, libjs-jquery-ui.
  * debian/control: Depends: Add lebiniou-data (>= 3.50).
  * debian/control: Build-Depends: Remove libxml2-dev (>= 2.6).
  * debian/copyright: Updated.
  * debian/lebiniou.links: Added.
  * debian/lebiniou.lintian-overrides: Updated.
  * debian/source/lintian-overrides: Added.

Regards,

Olivier Girondel








signature.asc
Description: OpenPGP digital signature

Bug#973038: autopkgtest-build-qemu installs grub-pc on arm64 which is unavailable

[Ryutaroh Matsumoto]

Hi Christian,

Thank you for your attention!

(1) I checked the patch at
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=973038;filename=diff-auto.txt;msg=14
on an amd64 machine. With that patch, as root, 

debci setup -b qemu -s sid -a amd64
autopkgtest -u debci -B autopkgtest -- qemu --efi 
/var/lib/debci/qemu/sid-amd64.img

worked fine.

(2) For arm emulation of autopkgtest-virt-qemu, I am in the mood of giving up.
See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973484
if you have interest...

Ryutaroh

Bug#973485: gdm3 starts gnome instead of .xsession even when "Default X11 session" is selected

[Christoph Berg]

Package: gdm3
Version: 3.38.1-2
Severity: grave

gdm3 does not start my ~/.xsession anymore but boots gnome instead.

Sorry if that bug was already reported, but no way I'm going to read
through the 300 (!) open gdm3 bugs. Please do some BTS house keeping.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.55-3
ii  adduser   3.118
ii  awesome [x-window-manager]4.3-5
ii  dbus  1.12.20-1
ii  dconf-cli 0.38.0-1
ii  dconf-gsettings-backend   0.38.0-1
ii  debconf [debconf-2.0] 1.5.74
ii  gir1.2-gdm-1.03.38.1-2
ii  gnome-session [x-session-manager] 3.38.0-2
ii  gnome-session-bin 3.38.0-2
ii  gnome-session-common  3.38.0-2
ii  gnome-settings-daemon 3.38.0-2
ii  gnome-shell   3.38.1-1
ii  gnome-terminal [x-terminal-emulator]  3.38.0-1
ii  gsettings-desktop-schemas 3.38.0-2
ii  libaccountsservice0   0.6.55-3
ii  libaudit1 1:2.8.5-3.1
ii  libc6 2.31-4
ii  libcanberra-gtk3-00.30-7
ii  libcanberra0  0.30-7
ii  libgdk-pixbuf2.0-02.40.0+dfsg-5
ii  libgdm1   3.38.1-2
ii  libglib2.0-0  2.66.1-2
ii  libglib2.0-bin2.66.1-2
ii  libgtk-3-03.24.23-2
ii  libkeyutils1  1.6.1-2
ii  libpam-modules1.3.1-5
ii  libpam-runtime1.3.1-5
ii  libpam-systemd246.6-2
ii  libpam0g  1.3.1-5
ii  librsvg2-common   2.50.1+dfsg-1
ii  libselinux1   3.1-2+b1
ii  libsystemd0   246.6-2
ii  libx11-6  2:1.6.12-1
ii  libxau6   1:1.0.8-1+b2
ii  libxcb1   1.14-2
ii  libxdmcp6 1:1.1.2-3
ii  lsb-base  11.1.0
ii  mutter [x-window-manager] 3.38.0-2
ii  policykit-1   0.105-29
ii  procps2:3.3.16-5
ii  rxvt-unicode [x-terminal-emulator]9.22-8
ii  ucf   3.0043
ii  x11-common1:7.7+21
ii  x11-xserver-utils 7.7+8

Versions of packages gdm3 recommends:
ii  at-spi2-core2.38.0-2
ii  desktop-base10.0.3
ii  x11-xkb-utils   7.7+5
ii  xserver-xephyr  2:1.20.8-2
ii  xserver-xorg1:7.7+21
ii  zenity  3.32.0-6

Versions of packages gdm3 suggests:
pn  gnome-orca
pn  libpam-fprintd
ii  libpam-gnome-keyring  3.36.0-1

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3

Christoph

Bug#973373: blueman: Blueman requires authentication twice on start-up

[Christopher Schramm]

31.10.20 13:26 Andrew McCarthy:
Error checking for authorization org.blueman.network.setup: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted 
callers (e.g. uid 0 or an action owner) can use CheckAuthorization() for 
subjects belonging to other identities


That means that the blueman-applet process is not running as the same 
user as you're running the pkcheck command with. Assuming that you're 
running pkcheck as the mentioned pi user who's in the netdev group, 
that's not the case for blueman-applet then.

Bug#714836: qucsator release

[Felix Salfelder]

Dear all.

We have released qucsator-0.0.20 [1]. It has been part of qucs, but it
is also being used without qucs. It will also work in combination with
any statically linked (qt3, non-debian) build of qucs or some of its
forks. I think it will be good to have qucsator in Debian. Please
consider packageing it e.g. within the electronics team [2].

The qucs qt5 implementation is progressing, and it will still support
qucsator as a simulator backend.

cheers
felix

[1] 
https://sourceforge.net/projects/qucs/files/qucs/0.0.20/qucsator-0.0.20.tar.gz
[2] https://salsa.debian.org/electronics-team

Bug#963551: python3-bitstring: Update, DeprecationWarning

[Graham Inggs]

Control: tags -1 + moreinfo
Control: forwarded -1 https://github.com/scott-griffiths/bitstring/pull/206

Hi Matthias

On Tue, 23 Jun 2020 at 18:15, Matthias Urlichs  wrote:
> The bitstring package is at version 3.1.7 upstream.

I've just uploaded 3.1.7-1 to unstable.

> There is another problem: broken backslash sequences trigger a
> DeprecationWarning. This makes the package unusable with pytest.

Would you please provide the steps to reproduce this issue?

Regards
Graham

Bug#837973: licensecheck should check license of font files

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2016-09-16 09:46:58)
> Quoting Pirate Praveen (2016-09-16 06:34:29)
> > Many times ftp master reject a package because copyright of embedded 
> > fonts are missing. It wuld be nice if licensecheck can find it 
> > before the upload itself.
> 
> Thanks for reporting this!
> 
> This is already on my mental TODO-list (therefore thanks for making it 
> visible by this bugreport!): One of the reasons for my adopting and 
> refactoring licensecheck was to incorporate the extensions developed 
> as part of CDBS - including the /usr/lib/cdbs/license-miner which 
> extracts metadata from binary files like fonts and graphics files.

My current workaround for this no longer rely on CDBS, but essentially 
does this:

1>&2 exiftool '-textOut!' %d%f.%e:meta -short -short -recurse -ext ttf .
licensecheck --copyright --deb-machine --recursive --lines 0 --check '.*' 
--ignore '.*\.ttf$' -- *
find -type f -name '*.ttf' -delete

My actual workaround scripts are tailored to each package, and typically 
the one most detailed and most up-to-date is the one for ghostscript: 
https://sources.debian.org/src/ghostscript/9.53.3%7Edfsg-5/debian/copyright-check/


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#973469: licensecheck: extract licenses from SVG files

[Jonas Smedegaard]

Hi Andrius,

Quoting Andrius Merkys (2020-10-31 07:20:11)
> SVG files sometimes contain licensing information, for example [1]:
> 
> rdf:about="">
> image/svg+xml
> rdf:resource="http://purl.org/dc/dcmitype/StillImage; />
> rdf:resource="http://creativecommons.org/licenses/GPL/2.0/; />
> Hard disk
> 
>   
> Luca Ferretti elle@libero.it
>   
> 
[...]
> It would be nice if licensecheck could extract license and copyright
> owner from this file. To do so, XPath analysis should be sufficient.

Agreed, licensecheck should ideally detect structured licensing data 
like above RDF metadata.

For now, a workaround is to extract such metadata using exiftool (debian 
package libimage-exiftool-perl), e.g. like this:

1>&2 exiftool '-textOut!' %d%f.%e:meta -short -short -recurse -ext svg .
licensecheck --copyright --deb-machine --recursive --lines 0 --check '.*' 
--ignore '.*\.svg$' -- *
find -type f -name '*.svg' -delete

More elaborate use of that workaround (although not for SVG files 
specifically) can be found e.g. here: 
https://sources.debian.org/src/ghostscript/9.53.3%7Edfsg-5/debian/copyright-check/


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#973484: qemu-system-arm: -machine virt does not allow two serial port for arm emulation

[Ryutaroh Matsumoto]

Package: qemu-system-arm
Version: 1:5.1+dfsg-4+b1
Severity: wishlist
Tags: upstream
Control: block 973038 by -1

Dear Maintainer,

I am trying to make autopkgtest-virt-qemu usable on arm64 as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973038

autopkgtest-virt-qemu needs two serial ports in the emulation.
But qemu-system-aarch64 only allows at most one serial port.
This is an upstream design decision as
https://lists.nongnu.org/archive/html/qemu-discuss/2018-11/msg1.html

An unofficial patch is available at
https://unix.stackexchange.com/questions/479085/can-qemu-m-virt-on-arm-aarch64-have-multiple-serial-ttys-like-such-as-pl011-t

Best regards, Ryutaroh Matsumoto


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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 qemu-system-arm depends on:
ii  libaio1 0.3.112-8
ii  libc6   2.31-4
ii  libcapstone34.0.1+really+3.0.5-2+b1
ii  libepoxy0   1.5.4-1
ii  libfdt1 1.6.0-1
ii  libgbm1 20.1.9-1
ii  libgcc-s1   10.2.0-15
ii  libglib2.0-02.66.1-2
ii  libgnutls30 3.6.15-4
ii  libibverbs1 31.0-1
ii  libjpeg62-turbo 1:2.0.5-1.1
ii  libnettle8  3.6-2
ii  libnuma12.0.12-1+b1
ii  libpixman-1-0   0.36.0-1
ii  libpmem11.9.1-3
ii  libpng16-16 1.6.37-3
ii  librdmacm1  31.0-1
ii  libsasl2-2  2.1.27+dfsg-2
ii  libseccomp2 2.4.4-1+b1
ii  libslirp0   4.3.1-1
ii  libspice-server10.14.3-1
ii  libstdc++6  10.2.0-15
ii  liburing1   0.7-1
ii  libusb-1.0-02:1.0.23-2
ii  libvdeplug2 4.0.1-2
ii  libvirglrenderer1   0.8.2-4
ii  qemu-system-common  1:5.1+dfsg-4+b1
ii  qemu-system-data1:5.1+dfsg-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages qemu-system-arm recommends:
ii  ipxe-qemu 1.0.0+git-20190125.36a4c85-5
ii  qemu-efi-aarch64  2020.08-1
ii  qemu-efi-arm  2020.08-1
pn  qemu-system-gui   
ii  qemu-utils1:5.1+dfsg-4+b1

Versions of packages qemu-system-arm suggests:
pn  qemu-block-extra  
pn  samba 
pn  vde2  

-- no debconf information

Bug#973483: mate-themes: wrong license LGPL-2.1+ (should be LGPL-2.1)

[Jonas Smedegaard]

Package: mate-themes
Version: 3.22.21-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

copyright file lists numerous files as licensed LGPL-2.1+,
with a comment of "Assuming license found in COPYING file."

The file COPYING contains the license LGPL-2.1
(and at the end a usage _sample_ of how to express LGPL-2.1+).

For files licensed "same as the file COPYING"
(which arguably the mere existence of such file is no evidence of,
but that is a different matter),
the licensing is therefore LGPL-2.1 (not LGPL-2.1+).

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+ddsMACgkQLHwxRsGg
ASERtw//eHDtKI1wGo4hzahv/6olozahnngbhAVU6CpC4Bqe+ZPUDha/ArwcPfZ1
uIQ9UcpRd0XSm2W4AMZiFrCToOS8/r/77ou9vVNZfGwS6rkXMg32qaGvKDbO5iVl
/lL6d5y2zVMLZDTV+CckakOBywLBgrRqk8POJB86blsIA26eHBRNZ8GerL+h3DiX
YOQxX23qj4T1cXBQOEh7w6unxo45RRYaPpzxQoWmTJQfPNQjdu+n27SK0QRykPm/
W5Y4sBZBhAksYZREAtQcluanTJ6uHW6e3GA6YTF2Y9mpZ5qqhRmLw0uixJSNNuWz
VW4tE93h+oNNlUQIW4TOQ5HeSklLCc8y7YluPuGUBVKN3WDFL6fIJVDH3HUMYmTU
0xPdwjSBImgVB0THYEUsh+xlM+UlxBNq6b9zXrq02HlTfQXh0ZPBRYOaJS8duGBv
NueFiUyBB8rbyP15wnXAtfhbtTkAECha1FnbE5rehELRZvIxrxnpQss/eZQ9h3rE
K12lxihfvL+EWRXGh3dQ7qfZZMIM5Jv/aGMqfPSDOFAwhTa5YbYM137lZ7DfJKtY
cuA9ZTmlms05QYPlNTvbx3VmpPaOEb5c/KcFqPOX95nrsKtDLIn8cPE3qUmtVQpV
oIlJgNhARv5bZfNzXA143M061ogFuwAvlLJLgK/LtG5Ffya6Mf4=
=DJWA
-END PGP SIGNATURE-

Bug#973482: petsc: f951: out of memory allocating 140 bytes after a total of 1874202624 bytes

[Adrian Bunk]

On Sat, Oct 31, 2020 at 03:22:10PM +0100, Sebastian Ramacher wrote:
>...
> | f951: out of memory allocating 140 bytes after a total of 1874202624 bytes
>...

After looking at what kind of workarounds have been done for this in the 
past, and considering that it is unlikely there are any users on mipsel,
I am wondering whether I should just file RM bugs for the mipsel binaries
of petsc and reverse dependencies.

I've already tried the usual "-g0 -O0" tricks without success.

cu
Adrian

Bug#973481: ITP: please -- Please, a sudo clone with regex support

[Geert Stappers]

On Sat, Oct 31, 2020 at 01:59:49PM +, Edward Neville wrote:
> 
> * Package name: please
>   Upstream Author : Ed Neville 
> * URL : https://gitlab.com/edneville/please
> * License : GPL
>   Programming Lang: Rust
>   Description : Please, a sudo clone with regex support
> 
...
> 
> A sponsor is required.
> 

Sponsor reporting for duty;-)


Regards
Geert Stappers
DD
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Bug#973261: libhdf5-openmpi-dev: installing requires /proc being mounted

[Gilles Filippini]

Hi Josh,

Johannes 'josch' Schauer a écrit le 27/10/2020 à 18:45 :
> Package: libhdf5-openmpi-dev
> Version: 1.10.6+repack-2
> Severity: wishlist
> 
> Hi,
> 
> when installing libhdf5-openmpi-dev in a chroot that doesn't have /proc
> mounted, one will get the following error:
> 
> Setting up libhdf5-openmpi-dev (1.10.6+repack-2) ...
> /var/lib/dpkg/info/libhdf5-openmpi-dev.postinst: line 56: /dev/fd/63: No such 
> file or directory
> dpkg: error processing package libhdf5-openmpi-dev (--configure):
>  installed libhdf5-openmpi-dev package post-installation script subprocess 
> returned error exit status 1
> 
> The problem is, that the postinst script uses the bash-feature to write:
> 
> while read x; do ... done < <(cmd2 args ...)
> 
> Fortunately, these instances can easily be rewritten as:
> 
> cmd2 args | while read x; do ... done
> 
> Please consider making this change.

Unfortunately it doesn't work this way. Consider this test script:

$ cat test.sh
#!/bin/bash
declare -A foo bar
while read var; do
  foo["$var"]="$var"
done < <(seq 1 3)
seq 1 3 | while read var; do
  bar["$var"]="$var"
done
echo "foo=${foo[@]}"
echo "bar=${bar[@]}"

$ ./test.sh
foo=3 2 1
bar=

Using a pipe makes variable assignments into the while loop inefficient.
That's why I had to use the process substitution syntax.

Any other idea?

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#973482: petsc: f951: out of memory allocating 140 bytes after a total of 1874202624 bytes

[Sebastian Ramacher]

Source: petsc
Version: 3.14.0+dfsg1-3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

The build on mipsel failed:
| mpif90 -c -g -O2 -fstack-protector-strong -fPIC -ffree-line-length-0   
-fdebug-prefix-map=/<>=. -I/<>/include 
-I/<>/mipsel-linux-gnu-real-debug/include -I/usr/include/hypre 
-I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi-MMD -MP 
/<>/src/sys/classes/bag/f2003-src/fsrc/bagenum.F90 -o 
mipsel-linux-gnu-real-debug/obj/sys/classes/bag/f2003-src/fsrc/bagenum.o 
-J/<>/mipsel-linux-gnu-real-debug/include
| mpicc -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -fdebug-prefix-map=/<>=. 
-I/<>/include 
-I/<>/mipsel-linux-gnu-real-debug/include -I/usr/include/hypre 
-I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi  -Wdate-time 
-D_FORTIFY_SOURCE=2   -MMD -MP 
/<>/src/tao/leastsquares/impls/brgn/brgn.c -o 
mipsel-linux-gnu-real-debug/obj/tao/leastsquares/impls/brgn/brgn.o
| mpif90 -c -g -O2 -fstack-protector-strong -fPIC -ffree-line-length-0   
-fdebug-prefix-map=/<>=. -I/<>/include 
-I/<>/mipsel-linux-gnu-real-debug/include -I/usr/include/hypre 
-I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi-MMD -MP 
/<>/src/sys/objects/f2003-src/fsrc/optionenum.F90 -o 
mipsel-linux-gnu-real-debug/obj/sys/objects/f2003-src/fsrc/optionenum.o 
-J/<>/mipsel-linux-gnu-real-debug/include
| mpicc -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -fdebug-prefix-map=/<>=. 
-I/<>/include 
-I/<>/mipsel-linux-gnu-real-debug/include -I/usr/include/hypre 
-I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi  -Wdate-time 
-D_FORTIFY_SOURCE=2   -MMD -MP 
/<>/src/tao/leastsquares/impls/pounders/pounders.c -o 
mipsel-linux-gnu-real-debug/obj/tao/leastsquares/impls/pounders/pounders.o
| mpif90 -c -g -O2 -fstack-protector-strong -fPIC -ffree-line-length-0   
-fdebug-prefix-map=/<>=. -I/<>/include 
-I/<>/mipsel-linux-gnu-real-debug/include -I/usr/include/hypre 
-I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi-MMD -MP 
/<>/src/vec/f90-mod/petscvecmod.F90 -o 
mipsel-linux-gnu-real-debug/obj/vec/f90-mod/petscvecmod.o 
-J/<>/mipsel-linux-gnu-real-debug/include
| mpif90 -c -g -O2 -fstack-protector-strong -fPIC -ffree-line-length-0   
-fdebug-prefix-map=/<>=. -I/<>/include 
-I/<>/mipsel-linux-gnu-real-debug/include -I/usr/include/hypre 
-I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist 
-I/usr/include/scotch -I/usr/include/hdf5/openmpi-MMD -MP 
/<>/src/mat/f90-mod/petscmatmod.F90 -o 
mipsel-linux-gnu-real-debug/obj/mat/f90-mod/petscmatmod.o 
-J/<>/mipsel-linux-gnu-real-debug/include
|
| f951: out of memory allocating 140 bytes after a total of 1874202624 bytes
| gmake[5]: *** [gmakefile:207: 
mipsel-linux-gnu-real-debug/obj/mat/f90-mod/petscmatmod.o] Error 1
| gmake[4]: *** [/<>/lib/petsc/conf/rules:49: libs] Error 2
| **ERROR*
|   Error during compile, you need to increase the memory allocated to the VM 
and rerun 
| 

| gmake[3]: *** [makefile:40: all] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=petsc=mipsel=3.14.0%2Bdfsg1-3=1604119704=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#948374: (no subject)

[João Azevedo]

The Peertube project has changed name and git hosting website.

The project (and package) is now called: Cuttlefish

The source code and development is currently being done here:

 https://gitlab.shinice.net/artectrex/Cuttlefish

And the project description slightly changed, also the project is now
aiming GTK4:

> Cuttlefish
> Cuttlefish is a free (as in freedom) client for PeerTube, the
> federated video hosting service. It is Free Software as specified by
> the GPL, version 3 (or later).
> The logo was made using a representation of a cuttlefish by Pixelz
Studio (Distributed under the Creative Commons CCBY license).

> What is this?
> Cuttlefish is a client for PeerTube. PeerTube is a federated
video hosting service and uses WebTorrent - a version of BitTorrent that
runs in the browser - to help serve videos to users.
Cuttlefish is a desktop client for PeerTube, but will work on
GNU/Linux-based phones
> (like the Librem 5 or Pinephone) as well. We want the experience of
watching PeerTube videos and using PeerTube in general to be better, by
making a native application that will become the best and most efficient
way to hook into the federation of interconnected video hosting
services.
> Eventually, it will allow people to continue sharing watched videos with
other PeerTube users for longer periods of time, instead of discarding
the video when done watching. It will also help bridge PeerTube's gap
between the - now separated - BitTorrent and WebTorrent networks by
speaking both of those protocols.

> Dependencies, protocols
> We use GTK4 for the UI, with libhandy to support mobile form-factors.
We will use libtorrent to speak the WebTorrent and BitTorrent protocols
(since libtorrent now also supports WebTorrent). GStreamer will handle
the video decoding. We use libsoup for interacting with the PeerTube API.
> Cuttlefish is written in C++, but using GTK in C (instead of with gtkmm).



-- 
João Azevedo
Purism support


OpenPGP_0x70718D0922DB3F93.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#973480: transition: llvm-defaults

[Sebastian Ramacher]

Control: tags -1 + moreinfo
Control: block -1 by 971415

On 2020-10-31 14:35:36 +0100, Sylvestre Ledru wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello,
> 
> One more time, it is time to have upgrade llvm.
> I would like to ship bullseye with 11 and skip -10 (it had some performance 
> regression in the
> binary generated).
> 
> I am building a version with the ppc64el fix.
>
> llvm-defaults has been pointing to 11 in experimental for quite sometime.
> Happy to upload it in unstable when you give me the go.

This transition is at least blocked by the ocaml transition as that
needs to finish before llvm-toolchain-11 can migrate.

> Rust already relies on -11 in experimental.

What about the other reverse dependencies? Do they all build fine with
llvm-toolchain-11?

> 
> Thanks
> Sylvestre
> 
> Ben file:
> 
> title = "llvm-defaults";
> is_affected = .depends ~ "~" | .depends ~ /(clang|llvm)1?-(?[3456789]|?10)/ | 
> .depends ~ "~" | .depends ~ /(clang|llvm)1?-?[11]/;
> is_good = .depends ~ "~" | .depends ~ /(clang|llvm)1?-?[11]/;
> is_bad = .depends ~ "~" | .depends ~ /(clang|llvm)1?-(?[3456789]|?10)/;

I'm not sure what .depends ~ "~" is supposed to catch here and it causes
a parser failure. So I've merged this ben file with the one from the
llvm-defaults 9 transition. Once the tracker is available, please check
if that looks sane.

Cheers

> 
> 
> (not certain about the is_bad regexp :/)
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (900, 'testing'), (600, 'unstable'), (500, 'oldstable'), (300, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/28 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#973481: ITP: please -- Please, a sudo clone with regex support

[Edward Neville]

Package: wnpp
Severity: wishlist
Owner: Edward Neville 

* Package name: please
  Version : 0.3.12
  Upstream Author : Ed Neville 
* URL : https://gitlab.com/edneville/please
* License : GPL
  Programming Lang: Rust
  Description : Please, a sudo clone with regex support

Please is a sudo clone with a strong preference for delegation of access 
defined by regular expression rules.

The aim is to allow admins to delegate accurate least privilege access 
with ease. There are times when what is intended to be executed can be 
expressed easily with a regex to expose only what is needed and nothing 
more.

When a subset of complex commands are only required and implementing the 
principle of least privilege, it is easier to use regular expressions to 
define the commands. Often intermediate scripts with sudo to do the same 
can confuse end users.

A sponsor is required.

Ed

Bug#973453: RFS: liboauth/1.0.3-4 -- C library implementing OAuth Core 1.0a API (runtime)

[Laurin Hagemann]

Thanks Tobi, for your detailed response.

I re-uploaded the package (https://mentors.debian.net/package/liboauth/) with
all the mistakes that you mentioned fixed.
 - now from 1.0.3-4 as base package
 - not downgrading Standards-Version
 - a more detailed changelog containing "Closes: #973473"
 - debhelper compat version 13
 - w/o gbp.conf

Let me know if there are more mistakes/improvements to be made.

I noticed (https://mentors.debian.net/package/liboauth/) that "Package closes
bugs in a wrong way", which I don't understand, because I executed the retitle
command once before the upload but it is getting ignored, even if I try again
now:
```
$ bts retitle 973473 "ITA: liboauth -- C library implementing OAuth Core 1.0a
API (development files)"
$ bts status 973473bug_num 973473
...
subject O: liboauth -- C library implementing OAuth Core 1.0a API (development
files)
...
```
I also tried to perform the same action via email to cont...@bugs.debian.org -
no success.
Can you help me out here? What am I doing wrong?
-- 
/Laurin

-BEGIN PGP PUBLIC KEY BLOCK-

mQINBFiM64ABEAC1oAm0/aU+T+Tb4f5q9KALm/UfaZ34dmgXY3QcU3lF34MEpATC
JxRmiLJoQiBvLyDPpHEuQcAArUrMEImySQOWcst9S1TKlIE51CXNpvCXkA2RQ7BU
mV+UnRbMqndSXo5qkawgb2ogrppeztxvFjL6jkFHp+rnTqV5RvXRLZwOH2dnkDwz
0DP0J01tECFJo+wRaj/rDnaVlLrTEi+58isVv0HDf6JEiD9wp7U59VKqgeJWezUb
YKWbjn7s1KTNw7NG3SDDniwOAw8HCtV86Z4L6sfHUtX9CIn9S/ykLsXXCkbVlCd/
15VcPweblCtC+spXKcL2wY+80Y6QG+wW9Mg1Kd7ifi2sCM7o561hjPAd/nEQXqo5
8pUohCyAfySdTTwlV+rjIpGOARbZfIknCX1938P2ZnWU9QEBRVc2SdPNewJOMBHl
lHp7yUX1GZFXgzHiGhuo9fRyFLvMhDRYKduBpDrPLeuvGKpmbVdw60jjRQKYzluk
bUqnAfQ4k3K83ZxuDQMoNVw6XZqXSu86wGPcC6nGtTpAY56bCmZXVjgVJ5Adu8lT
vqhF2xxh0ikhzRXIO31sQDs19IJSduJD90UjAUe7B3di1FDspUvz/zH2c+OLNrVH
HoejAa2E8iU7dEvzlka0wiNT53mLeFW6OYrkrEoJkdo7tSRLZmb/Zmgp2wARAQAB
tChMYXVyaW4gSGFnZW1hbm4gKHByaXYpIDxsYXVyaW5oZ0BnbXguZGU+iQJVBBMB
CgA/AhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgBYhBNTe458o1Pr66+mJyJMF
9xHAQy4EBQJdimC0BQkIv9w0AAoJEJMF9xHAQy4Ed1UP/0gHxxM6LFDv87OaMvf3
dU0BlVAzGtS9B5icNmaEo+4avTywyEl/G//UL134bll9lQBkxzQeQheINxJ4MRTM
f/9lkigZA0pmY5VS29x9hidO6N8YfvDomYwzan6oZb+/8lgDru749zIGRbvGs/WT
IE8vrGP65/MEPbQ0Ok+57JYHh0DhOLGGVEO9eJE3QWsVyHiPXjaNILkDeOxHjK+u
wfyqx5VVDNtKqTbNsUCTu0M8g/jtwWbBl/EvhvzbkHrbEnL/7Yz421wN1gCreYZL
e3mEh/3aHo/TKqm8rG1EeLoD6PQbNVJQj0/wVUzwRS85R2us4ozy13G79AbS27qe
hEUc+4UJeN45h4LXTXzHrI/zQ3Ge14QhfeF+g0OMMC8F/yU9Mx8vGbR8p+6K3Z+L
mShIy6v8Vxg4HgM3gEkoQM8zRhSsjQrBzeuy1XZWsFRUuNmHylAW/oRCfKECg9jr
ZrDOUHxqunarGPGQp4LXfQiMnN3PrKoxHo0Cs1qT/j7J6qxjal9N5F4IwsRPbRAb
Of1j06IUi5e86+3oK2/27sjBS286TPTuuKr0RHU9iOJWHzsgKvCnyZfi1gHlluxI
OqMBvAu1Zs8NcWS6nvSkcIQLUwKiqEQMR3ePZmAP16dtZAV32/2alXQgD121uSZ0
00To44F8DrNB8Zx78bQ63reuuQINBFiM64ABEADzLYr10BFIdqpeiw21IPLXbChz
RfIxEV3xq4UlwtIdAoSTtQOm0AHfiweSJb1PeRMV9LAmu8UJZbhbLnZvDU4p/ecv
XN3dkrxhde9GqQZDij6WdYb2ZDtQG1uk4f1BrOACojP0KxgOEsRS5a8GRnl5GZXJ
gJb3+kpiM0o5OUockxtuSgH8eQimlkPlVDjTs92wQs0ZQgM8xdu0H7pQy36u9/wi
bhMQXWXHaUWmjQDnenRc8QFi3kNUsrzIRiKLgjWqHHGmKCce+FWvm7OQg32f/1r4
n6OViIZwCevjCrsTGv/WcxP6vev2upk8G6nOpucIt4XnUPTnMEE7hXRSE4lasUtG
kWaMATxheKk5su3+PzmsquG7tn5tgvikMZ0Ft0iTkWFez3IS1FA55+H4AW2zIl04
RkX6yhjRpud1mUwjFCBXU65g5BmVsyTuCMG5QhzkuiA9Sj9rYAQgqQITXVzRYxD7
eGhWJX6XtYOlUUKMOx32KMTLATqdkb59XdQ5/23gw6n/6GAlAgyu3fLNTYFwr60L
rRPcwtqwZENO7Bgm79lI6Ibn+oFrXY3C8UIbB7gJzLqbXgTzzGjDwM97+nWLc+B9
eGCu2C1UGXAuGfaZbpnYTF4vgoNzXeI0UpnQMmFmZgIuJRxZ9YJcZRsTVp0xc6SB
gQ20KoSWQKQvigE9HQARAQABiQI8BBgBAgAmAhsMFiEE1N7jnyjU+vrr6YnIkwX3
EcBDLgQFAl1cI0wFCQW8hcwACgkQkwX3EcBDLgRgGA/+Lz4ahjcNlpoQLZH/LVAE
y6lEj50YuVnWlVy2+08IsXEWtQFC+OCf1yahxynUQFg9EUJGkwGVkp6pOhQJhkYj
fDETv0T7CdKAY2qIKkIaJFFTORlDLpBtBB3bdYxZ9DlU4Yfv4Nsbs2RrHXZPp7x1
6dpoI3Yf9XG1CodhN6ez1X/BuiKeKFURb/pb6XhfSCGuSqgPoFmDMYDyJI2Qa+h2
cTaQVnBXoWHlC269u5kfiE1OLNjbhZs2tgx4sGjARI3eL1uj48A3lcGZpD05TZtx
Q6E57+hcd+IFh6In8ai8EarMv3jbx1lIY/qNvf9IwrLxIyCm5iVglbDOzsvMTDbo
dwkjaWil8Gj5GHtFPNHRLynqHgWCcPHPqzQ0GjGQ4IRitqS7Ysmd7GAQBnrdTWOX
HL1O3K9qNndFXYbCUTxy3rDTptm5eZ9iK1GyBP4m0M4tDIwmWxLySL71XMCpiJsj
5MM+2IfVVFu9th3RTAFFvdq+kDp95MXAxoBfKG+fvzUP6g2++5eiwBZaviA5+kBr
iFn6mHi1ul96Jm9auUd2QJvirWk5yxEaczwpWZBW7byyo4dIOeKzi4mwtpFCfWWl
T3BMYHPN0JY9KxJiVAviUFmCqseQuSYP+/wvnslGrFYotEDUS5g5gIApdut9xOKm
CYjPkDA2K1CR/XA27Y87NWg=
=lXQM
-END PGP PUBLIC KEY BLOCK-


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

Bug#973480: transition: llvm-defaults

[Sylvestre Ledru]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello,

One more time, it is time to have upgrade llvm.
I would like to ship bullseye with 11 and skip -10 (it had some performance 
regression in the
binary generated).

I am building a version with the ppc64el fix.
llvm-defaults has been pointing to 11 in experimental for quite sometime.
Happy to upload it in unstable when you give me the go.

Rust already relies on -11 in experimental.

Thanks
Sylvestre

Ben file:

title = "llvm-defaults";
is_affected = .depends ~ "~" | .depends ~ /(clang|llvm)1?-(?[3456789]|?10)/ | 
.depends ~ "~" | .depends ~ /(clang|llvm)1?-?[11]/;
is_good = .depends ~ "~" | .depends ~ /(clang|llvm)1?-?[11]/;
is_bad = .depends ~ "~" | .depends ~ /(clang|llvm)1?-(?[3456789]|?10)/;


(not certain about the is_bad regexp :/)


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

Kernel: Linux 5.4.0-4-amd64 (SMP w/28 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#973479: RM: llvm-toolchain-8 -- ROM; No longer needed

[Sylvestre Ledru]

Package: ftp.debian.org
Severity: normal

Hello

We should decrease the number of versions of llvm in the archive.

Cheers,
Sylvestre

Bug#973038: autopkgtest-build-qemu installs grub-pc on arm64 which is unavailable

[Christian Kastner]

Control: block -1 #973467

Hi Ryutaroh,

(I'm not a maintainer)

On 10/31/20 9:34 AM, Ryutaroh Matsumoto wrote:
> Control: tags -1 + patch
> Control: retitle -1 autopkgtest-build-qemu does not build a working arm64 
> qemu testbed

Unconditionally switching from BIOS to UEFI might be the right thing to
do, but does have its risks. I think this might break i386. Did you get
a chance it with that architecture?

In any case, I think the cleaner solution would be make this a new
option, eg:

autopkgtest-build-qemu --boot=

where =grub or =uefi. The default could even be conditional on
the architecture (uefi on amd64 and arm64, bios on i386).


Regardless of which solution is picked, this all depends on the vmdb2
GRUB plugin supporting multiple architectures (the #973467 that you
reported). One solution might be to add an arch: option to the plugin
(similar to the QEMU-debootstrap pluging), defaulting to the host
architecture.


Adding arm64 support so that it works out-of-the-box would be a great
addition to autopkgtest, I (as a user) would definitely appreciate such
a feature!

Bug#973373: blueman: Blueman requires authentication twice on start-up

[Andrew McCarthy]

Results from running command: pkcheck --action-id org.blueman.network.setup
--process $PID

*Without authentication at startup:*
Error checking for authorization org.blueman.network.setup:
GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted
callers (e.g. uid 0 or an action owner) can use CheckAuthorization() for
subjects belonging to other identities

*Following authentication at startup (privileges required for network
settings and rfkill)*
Error checking for authorization org.blueman.network.setup:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject
does not have uid set

On Fri, 30 Oct 2020 at 22:00, Christopher Schramm 
wrote:

> (Please don't forget to send your replies to 973...@bugs.debian.org as
> well. Thanks)
>
> 30.10.20 16:32 Andrew McCarthy:
> > The netdev group already has the user pi added to it. pi is the user
> > account of the gnome session.
>
> You can verify the Polkit-1 setup by running
>
> pkcheck --action-id org.blueman.network.setup --process $PID
>
> with the PID of the blueman-applet process. If that does not give an
> error, please elaborate on the authentication prompt that you get.
>

Bug#973478: lintian: Can't call method "is_dir" on an undefined value

[Baptiste Beauplat]

Package: lintian
Severity: normal

Dear maintainers,

I tried to run lintian against the attached packaged and it exit with a 
non-zero status and the following warning messages:


Warning in group hello/1.0-1: Can't call method "is_dir" on an undefined 
value at /usr/share/lintian/bin/../lib/Lintian/Index.pm line 499.

warning: cannot run cruft check on package source:hello/1.0-1
skipping check of source:hello/1.0-1
Warning in group hello/1.0-1: Can't call method "is_dir" on an undefined 
value at /usr/share/lintian/bin/../lib/Lintian/Index.pm line 499.

warning: cannot run files/names check on package source:hello/1.0-1
skipping check of source:hello/1.0-1
Warning in group hello/1.0-1: Can't call method "is_dir" on an undefined 
value at /usr/share/lintian/bin/../lib/Lintian/Index.pm line 499.

warning: cannot run origtar check on package source:hello/1.0-1
skipping check of source:hello/1.0-1

I'm using the lastest version (2.100.0). This issue was not present in 
lintian 2.98.


--
Baptiste BEAUPLAT - lyknode


hello_1.0.orig.tar.xz
Description: application/xz


hello_1.0-1.debian.tar.xz
Description: application/xz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 02 Dec 2018 22:38:11 +0100
Source: hello
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent TIME 
Changed-By: Vincent TIME 
Closes: 0
Changes:
 hello (1.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #0)
Checksums-Sha1:
 94e8b786567240d9da58546609b9565e1907a5ab 1141 hello_1.0-1.dsc
 3140c12322194d4cf4a4b7f48c8c32b43ed3249f 192 hello_1.0.orig.tar.xz
 11a72d451fd0aa5abd34c9b0936a571e078069dd 748 hello_1.0-1.debian.tar.xz
 a5ff03ba90e1c06c67808e3b441d0017ea71905e 5989 hello_1.0-1_source.buildinfo
Checksums-Sha256:
 439c04f9cac6cfbf49df394036024501518daec7dc510f444f9620df33ea7f0b 1141 
hello_1.0-1.dsc
 b8ef54ea11186e88ec0102791c808f51ac95ae95d5160a608f8e8388d82743c1 192 
hello_1.0.orig.tar.xz
 e01b8d3954ec9b95d033b53eb41c21f4cec35367fb8ea0e10052786251b5aa3e 748 
hello_1.0-1.debian.tar.xz
 6e509e90a9938366b7bbdbbcd271320e4a00acc6478d3ee5c77b4395a5379fa0 5989 
hello_1.0-1_source.buildinfo
Files:
 1ffe7fc6f84b315a5659cf0d30c54aec 1141 utils optional hello_1.0-1.dsc
 483ac781bce9df489231caff082ffa43 192 utils optional hello_1.0.orig.tar.xz
 d6f5b35d1cf8b71682d2b981b211c1ef 748 utils optional hello_1.0-1.debian.tar.xz
 73b238807fe8c3d7df35825447269736 5989 utils optional 
hello_1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSzz3sz+AdjONtPqA6HkZKDEXU71wUCX51VJQAKCRCHkZKDEXU7
1yrIAQDce76W2y1EoEUeYq3V6iKPYLY40Vd7Vq36JWhhWehKGwD9F1rcothVi093
l4wJJrqErOo55C1E2Z+diJsdqulzHAk=
=o+e6
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.0
Source: hello
Architecture: source
Version: 1.0-1
Checksums-Md5:
 1ffe7fc6f84b315a5659cf0d30c54aec 1141 hello_1.0-1.dsc
Checksums-Sha1:
 94e8b786567240d9da58546609b9565e1907a5ab 1141 hello_1.0-1.dsc
Checksums-Sha256:
 439c04f9cac6cfbf49df394036024501518daec7dc510f444f9620df33ea7f0b 1141 
hello_1.0-1.dsc
Build-Origin: Debian
Build-Architecture: amd64
Build-Date: Sat, 31 Oct 2020 12:14:28 +
Build-Tainted-By:
 usr-local-has-configs
 usr-local-has-libraries
 usr-local-has-programs
Installed-Build-Depends:
 autoconf (= 2.69-11.1),
 automake (= 1:1.16.2-4),
 autopoint (= 0.19.8.1-10),
 autotools-dev (= 20180224.1),
 base-files (= 11),
 base-passwd (= 3.5.48),
 bash (= 5.1~rc1-2),
 binutils (= 2.35.1-2),
 binutils-common (= 2.35.1-2),
 binutils-x86-64-linux-gnu (= 2.35.1-2),
 bsdextrautils (= 2.36-3+b1),
 bsdmainutils (= 12.1.7),
 bsdutils (= 1:2.36-3+b1),
 build-essential (= 12.8),
 bzip2 (= 1.0.8-4),
 calendar (= 12.1.7),
 clang-10 (= 1:10.0.1-7),
 clang-11 (= 1:11.0.0-3),
 clang-9 (= 1:9.0.1-14+b1),
 coreutils (= 8.32-4+b1),
 cpp (= 4:10.2.0-1),
 cpp-10 (= 10.2.0-15),
 cpp-8 (= 8.4.0-4),
 cpp-9 (= 9.3.0-18),
 dash (= 0.5.10.2-7),
 debconf (= 1.5.74),
 debhelper (= 13.2.1),
 debianutils (= 4.11.2),
 dh-autoreconf (= 19),
 dh-strip-nondeterminism (= 1.9.0-1),
 diffutils (= 1:3.7-3),
 dpkg (= 1.20.5),
 dpkg-dev (= 1.20.5),
 dwz (= 0.13-5),
 file (= 1:5.38-5),
 findutils (= 4.7.0+git20201010-2),
 g++ (= 4:10.2.0-1),
 g++-10 (= 10.2.0-15),
 gawk (= 1:5.0.1+dfsg-1),
 gcc (= 4:10.2.0-1),
 gcc-10 (= 10.2.0-15),
 gcc-10-base (= 10.2.0-15),
 gcc-8 (= 8.4.0-4),
 gcc-8-base (= 8.4.0-4),
 gcc-9 (= 9.3.0-18),
 gcc-9-base (= 9.3.0-18),
 gettext (= 0.19.8.1-10),
 gettext-base (= 0.19.8.1-10),
 grep (= 3.4-1),
 groff-base (= 1.22.4-5),
 gzip (= 1.10-2),
 hostname (= 3.23),
 init-system-helpers (= 1.58),
 install-info (= 6.7.0.dfsg.2-5),
 intltool-debian (= 0.35.0+20060710.5),
 lib32gcc-s1 (= 10.2.0-15),
 lib32stdc++6 (= 10.2.0-15),
 libacl1 (= 2.2.53-8),
 libarchive-zip-perl (= 1.68-1),
 libasan5 (= 9.3.0-18),
 libasan6 (= 10.2.0-15),
 libatomic1 (= 10.2.0-15),
 libattr1 (= 1:2.4.48-5),
 libaudit-common (= 1:2.8.5-3.1),
 libaudit1 (= 1:2.8.5-3.1),
 libbinutils (= 2.35.1-2),
 libblkid1 (= 2.36-3+b1),
 

Bug#972928: claws-mail: Crash when attempted to enter IMAP folder

[Ricardo Mones]

control: tags -1 moreinfo

On Mon, Oct 26, 2020 at 10:33:35AM +, curious_debian wrote:
> Package: claws-mail
> Version: 3.17.3-2
> Severity: normal
> 
> When attempted to enter IMAP folder, window instantly dissapeared (crash)
> 
> dmesg:
> 
> [Mon Oct 26 10:23:55 2020] claws-mail[1879911]: segfault at 1f ip
> 004a35bd sp 7ffe5872a4e0 error 4 in claws-mail[442000+23]
> [Mon Oct 26 10:23:55 2020] Code: 30 85 c0 0f 84 a4 02 00 00 c7 05 3e f6 2e 00
> 00 00 00 00 31 f6 48 89 df e8 c0 fc ff ff 49 8b 84 24 88 00 00 00 48 85 c0 74
> 19 <48> 8b 00 31 f6 83 38 04 48 8b 43 50 40 0f 94 c6 48 8b 78 30 e8 5a
> 
> Context: Folder I was entering to was just downloaded via "Check for new
> folders" option.
> 
> Using Debian Stable AMD64.

Is that reproducible? I've seen similar sporadic segfaults in the past
and is unlikely is Claws Mail fault only. You can try translate the
faulting address into some more meaningful, see [1]. Also, if it's
reproducible you'll have to install debugging packages and get a proper
backtrace [2].

regards,

[1] https://stackoverflow.com/a/2549363
[2] https://wiki.debian.org/HowToGetABacktrace
-- 
  Ricardo Mones 
  ~
  00:45 < hammar> cool.. have you used rssyl?  
  00:46 <@Ticho> um, yesSeen on #sylpheed



signature.asc
Description: PGP signature

Bug#973477: julia FTBFS on i386: test failure

[Adrian Bunk]

Source: julia
Version: 1.5.2+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=julia=i386=1.5.2%2Bdfsg-1=1603712592=0

...
./openblas_utest
TEST 1/28 amax:samax [OK]
TEST 2/28 ismax:negative_step_2 [OK]
TEST 3/28 ismax:positive_step_2 [OK]
TEST 4/28 ismin:negative_step_2 [OK]
TEST 5/28 ismin:positive_step_2 [OK]
TEST 6/28 drotmg:drotmg_D1_big_D2_big_flag_zero [OK]
TEST 7/28 drotmg:rotmg_D1eqD2_X1eqX2 [OK]
TEST 8/28 drotmg:rotmg_issue1452 [OK]
TEST 9/28 drotmg:rotmg [OK]
TEST 10/28 axpy:caxpy_inc_0 [OK]
TEST 11/28 axpy:saxpy_inc_0 [OK]
TEST 12/28 axpy:zaxpy_inc_0 [OK]
TEST 13/28 axpy:daxpy_inc_0 [OK]
TEST 14/28 zdotu:zdotu_offset_1 [OK]
TEST 15/28 zdotu:zdotu_n_1 [OK]
TEST 16/28 dsdot:dsdot_n_1 [OK]
TEST 17/28 swap:cswap_inc_0 [OK]
TEST 18/28 swap:sswap_inc_0 [OK]
TEST 19/28 swap:zswap_inc_0 [OK]
TEST 20/28 swap:dswap_inc_0 [OK]
TEST 21/28 rot:csrot_inc_0 [OK]
TEST 22/28 rot:srot_inc_0 [OK]
TEST 23/28 rot:zdrot_inc_0 [OK]
TEST 24/28 rot:drot_inc_0 [OK]
TEST 25/28 potrf:smoketest_trivial [OK]
TEST 26/28 potrf:bug_695 [OK]
TEST 27/28 kernel_regress:skx_avx  ** On entry to DGESVD parameter number  2 
had an illegal value
[FAIL]
  ERR: test_kernel_regress.c:49  expected 0.000e+00, got 5.747e+02 (diff 
-5.747e+02, tol 1.000e-10)
TEST 28/28 fork:safety [OK]
RESULTS: 28 tests (27 ok, 1 failed, 0 skipped) ran in 362 ms
make[5]: *** [Makefile:45: run_test] Error 1

Bug#961412: fetchmail: restart silently fails, then start doesn't help

[Leszek Dubiel]

W dniu 31.10.2020 o 09:29, Matthias Andree pisze:

Control: tags -1 + moreinfo

fetchmail 6.4.13 contains some additional PID handling fixes, but it's
unclear whether those fixes address the issue described here. The logs
provided are insufficient. Please provide logs with full debug trace.



Sorry for missing email in May.
Version on Debian is 6.4.0.beta4+GSS+NTLM+SDPS+SSL-SSLv2-SSLv3+NLS+KRB5.



Here is the output of

/etc/init.d/fetchmail debug-run


:



Script started on 2020-10-31 11:31:00+01:00 [TERM="xterm-256color" TTY="/dev/pts/0" 
COLUMNS="104" LINES="53"]
root@orion:/tmp# pgrep fetchmail
8707
root@orion:/tmp# service fetchmail restart


 no PID after restart



root@orion:/tmp# pgrep fetchmail
root@orion:/tmp# /etc/init.d/fetchmail debug-run
/etc/init.d/fetchmail: Initiating debug run of system-wide fetchmail service...
/etc/init.d/fetchmail: script will be run in debug mode, all output to forced to
/etc/init.d/fetchmail: stdout. This is not enough to debug failures that only
/etc/init.d/fetchmail: happen in daemon mode.
/etc/init.d/fetchmail: You might want to direct output to a file, and tail -f 
it.
/etc/init.d/fetchmail: Stopping the service...
[] Stopping fetchmail (via systemctl): fetchmail.service[ ok .
/etc/init.d/fetchmail: exit status of service stop was: 0
/etc/init.d/fetchmail: RUNUSER is fetchmail
/etc/init.d/fetchmail: OPTIONS would be  -f /etc/fetchmailrc --pidfile 
/var/run/fetchmail/fetchmail.pid --syslog
/etc/init.d/fetchmail: Starting service in nodetach mode, hit ^C (SIGINT/intr) 
to finish run...
Old UID list from besthosting.atthost24.asdafsadfasdp:
 

Old UID list from besthosting.atthost24.asdafsadfasdp:
 


... LESZEK DUIBEL HAS CUT HERE MANY SIMILAR LINES


Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Old UID list from naboo.endor.asdafsadfasdp:
 

Scratch list of UIDs:
 

fetchmail: uruchamianie fetchmaila 6.4.0.beta4 w trybie demona
fetchmail: 6.4.0.beta4 łączy się z besthosting.atthost24.asdafsadfasdp 
(protokół POP3) o godzinie sob, 31 paź 2020, 11:31:30: odpytywanie rozpoczęte
Próba połączenia z 185.255.40.42/995...połączono.
fetchmail: Loaded OpenSSL library 0x1010104f newer than headers 0x1010101f, 
trying to continue.
fetchmail: SSL verify callback depth 2: preverify_ok == 1, err = 0, ok
fetchmail: Łańcuch certyfikatów od korzenia do serwera, począwszy od głębokości 
2:
fetchmail: Organizacja wystawcy: The USERTRUST Network
fetchmail: CommonName wystawcy: USERTrust RSA Certification Authority
fetchmail: CommonName podmiotu: USERTrust RSA Certification Authority
fetchmail: SSL verify callback depth 1: preverify_ok == 1, err = 0, ok
fetchmail: Certyfikat na głębokości 1:
fetchmail: Organizacja wystawcy: The USERTRUST Network
fetchmail: CommonName wystawcy: USERTrust RSA Certification Authority
fetchmail: CommonName podmiotu: Sectigo RSA Domain Validation Secure Server CA
fetchmail: SSL verify callback depth 0: preverify_ok == 1, err = 0, ok
fetchmail: Certyfikat serwera:
fetchmail: Organizacja wystawcy: Sectigo Limited
fetchmail: CommonName wystawcy: Sectigo RSA Domain Validation Secure Server CA
fetchmail: CommonName podmiotu: atthost.asdafsadfasdp
fetchmail: Alternatywna nazwa podmiotu: atthost.asdafsadfasdp
fetchmail: Alternatywna nazwa podmiotu: *.atthost.asdafsadfasdp
fetchmail: Alternatywna nazwa podmiotu: *.atthost24.asdafsadfasdp
fetchmail: Alternatywna nazwa podmiotu: *.atthouse.asdafsadfasdp
fetchmail: Odcisk klucza besthosting.atthost24.asdafsadfasdp: 
CD:1A:2A:17:A0:1F:71:59:52:25:A8:6F:92:08:2B:BC
fetchmail: SSL/TLS: using protocol TLSv1.2, cipher ECDHE-RSA-AES256-GCM-SHA384, 
256/256 secret/processed bits
fetchmail: POP3< +OK AttHost mail system.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< AUTH-RESP-CODE
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN LOGIN
fetchmail: POP3< .
fetchmail: POP3> 
USERinfo@asdfasfqrewqrqwreqwrqwxxxlxustra.asdafsadfasdp
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: ponowna próba połączenia z domyślnym folderem
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: Nie ma poczty 
dlainfo@asdfasfqrewqrqwreqwrqwxxxlustra.asdafsadfasdp
  na besthosting.atthost24.asdafsadfasdp
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.4.0.beta4 łączy się z besthosting.atthost24.asdafsadfasdp 
(protokół POP3) o godzinie sob, 31 

Bug#973476: src:enigmail: autopkgtest failure (unit tests gone)

[Gregor Riepl]

Package: src:enigmail
Version: 2:2.2.4-0.1
Severity: normal
Tags: patch
X-Debbugs-Cc: onit...@gmail.com, jcris...@debian.org, bi...@debian.org

After uploading 2:2.2.4-0.1 to buildd, we now have autopkgtest failures:
https://ci.debian.net/data/autopkgtest/testing/amd64/e/enigmail/7837910/log.gz

The reason for these is that the unit test target is gone in 2.2.4.

Please apply the attached patch to drop the "make unit" from autopkgtest.



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

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From ba169d7446c5713b34471ecd6a8ccba43a31ad9d Mon Sep 17 00:00:00 2001
From: Gregor Riepl 
Date: Sat, 31 Oct 2020 11:29:46 +0100
Subject: [PATCH] Disable unit tests

---
 debian/run-tests | 5 -
 1 file changed, 5 deletions(-)

diff --git a/debian/run-tests b/debian/run-tests
index 3ab10c78..edb5da64 100755
--- a/debian/run-tests
+++ b/debian/run-tests
@@ -26,9 +26,4 @@ EOF
 export TMPDIR="$(pwd)/tmp"
 
 make check
-# only run the test during autopkgtest, since it times out for some
-# reason i don't understand on the buildds:
-if [ "$1" = autopkgtest ]; then
-make unit
-fi
 head -n 200 -v test-profile/prefs.js
-- 
2.28.0

Bug#973475: abcm2ps: new upstream, wrong GPL version

[Nicolas Boulenguez]

Package: abcm2ps
Version: 8.14.7-0.2
Severity: normal
Tags: patch

Hello.

Upstream has released two versions, 8.14.8 and 8.14.9.

The license granted by the upstream author has changed from GPL-2+ to
GPL-3+, but debian/copyright has not been updated GPL-2+ (I have
missed this when packaging 8.14.2-0.1).

It is common to distribute the packaging work under the same license
than the upstream material, but of course this decision is yours.

Do you agree to relicense for the packaging from GPL-2+ to GPL-3+?

May I proceed to an NMU with the attached changes?

May I add myself to Uploaders and update the package without this
bug/NMU cycle in the future?
--- a/abcm2ps.h
+++ b/abcm2ps.h
@@ -532,8 +532,8 @@
 	int dblrepbar, decoerr, dynalign, flatbeams, flatbeamgracing, infoline;
 	int gchordbox, graceslurs, graceword,gracespace, hyphencont;
 	int keywarn, landscape, linewarn;
-	int measurebox, measurefirst, measurenb, micronewps;
-	int oneperpage;
+	int measurebox, measurefirst, measurenb;
+	int nedo, oneperpage;
 #ifdef HAVE_PANGO
 	int pango;
 #endif
--- a/abcparse.c
+++ b/abcparse.c
@@ -1585,13 +1585,17 @@
 		if (microscale == 0) {
 			d--;
 			d += (n - 1) << 8;	/* short [ (n-1) | (d-1) ] */
-			for (n = 1; n < MAXMICRO; n++) {
+			if (d == 0) {
+n = MAXMICRO - 1;
+			} else {
+			for (n = 1; n < MAXMICRO; n++) {
 if (parse.micro_tb[n] == d)
 	break;
 if (parse.micro_tb[n] == 0) {
 	parse.micro_tb[n] = d;
 	break;
 }
+			}
 			}
 			if (n == MAXMICRO) {
 syntax("Too many microtone accidentals", p);
--- a/configure
+++ b/configure
@@ -1,8 +1,8 @@
 #! /bin/sh
 
 # (automatic update)
-VERSION=8.14.7
-VDATE=2020-02-19
+VERSION=8.14.9
+VDATE=2020-06-21
 
 CC=gcc
 PKG_CONFIG=pkg-config
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+abcm2ps (8.14.9-1) UNRELEASED; urgency=medium
+
+  * Change license of packaging sources: GPL-2+ -> GPL-3+.
+
+  [ Nicolas Boulenguez  ]
+  * New upstream release.
+  * Debhelper 13.
+  * Fix license of upstream sources: GPL-2+ -> GPL-3+. Close: #FIXME.
+
+ -- Anselm Lingnau   Sat, 31 Oct 2020 10:04:28 +
+
 abcm2ps (8.14.7-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Anselm Lingnau 
 Build-Depends:
- debhelper-compat (= 12),
+ debhelper-compat (= 13),
  libfreetype6-dev,
  libpango1.0-dev,
  pkg-config,
--- a/debian/copyright
+++ b/debian/copyright
@@ -2,23 +2,17 @@
 Upstream-Name: abcm2ps
 Upstream-Contact: Jean-François Moine 
 Source: http://moinejf.free.fr/
-License: GPL-2+
 
 Files: *
 Copyright: 1998-2020 Jean-François Moine (http://moinejf.free.fr)
1996-1998 Michael Methfessel 
-License: GPL-2+
-
-Files: debian/*
-Copyright: 2004-2018 Anselm Lingnau 
+   2004-2018 Anselm Lingnau 
2018-2020 Nicolas Boulenguez http://moinejf.free.fr)
+ * Copyright (C) 1998-2020 Jean-François Moine (http://moinejf.free.fr)
  * Adapted from abc2ps, Copyright (C) 1996-1998 Michael Methfessel
  *
  * This program is free software; you can redistribute it and/or modify it
@@ -983,6 +983,9 @@
 		}
 		a2b("%d %s%d ", n, acc_tb[acc & 0x07], d);
 	} else {
+		if (acc >> 3 != 0
+		 && cfmt.nedo)		// %%MIDI temperamentequal 
+			n = n >> 8) + 1) * 12) - 1) * 256 + cfmt.nedo - 1;
 		a2b("%s%d ", acc_tb[acc & 0x07], n);
 	}
 }
@@ -2873,10 +2876,16 @@
 	x1 = s1->x - 7;
 
 	if (s2->dur > s2->prev->dur) {
-		if (s2->next)
-			x2 = s2->next->x - s2->next->wl - 8;
-		else
-			x2 = realwidth - 6;
+		sy = s2->next;
+		if (!sy			// maybe a note in an overlay voice
+		 || sy->time != s2->time + s2->dur) {
+			for (sy = s2->ts_next; sy; sy = sy->ts_next) {
+if ((sy->sflags & S_SEQST)
+ && sy->time >= s2->time + s2->dur)
+	break;
+			}
+		}
+		x2 = sy ? sy->x - sy->wl - 5 : realwidth - 6;
 	} else {
 		x2 = s2->x + 2;
 		if (s2->u.note.notes[s2->nhd].shhd > 0)
@@ -4617,17 +4626,18 @@
 			s2 = s->prev;
 			if (!s2)
 break;
-			x2 = s2->x;
-			if (s2->type != BAR)
-x2 += s2->wr;
+			if (s2->type == BAR)
+x2 = s2->x;
+			else
+x2 = s->x - s->xmx;
 			staff = s->staff;
 			x = xstaff[staff];
 			if (x >= 0) {
 if (x >= x2)
 	continue;
 draw_staff(staff, x, x2);
+xstaff[staff] = s->x;
 			}
-			xstaff[staff] = s->x;
 			break;
 		default:
 //fixme:does not work for "%%staves K: M: $" */
--- a/format.c
+++ b/format.c
@@ -95,7 +95,6 @@
 	{"measurefirst", , FORMAT_I, 0},
 	{"measurefont", _tb[MEASUREFONT], FORMAT_F, 2},
 	{"measurenb", , FORMAT_I, 0},
-	{"micronewps", , FORMAT_B, 0},
 	{"musicfont", , FORMAT_S, 1},
 	{"musicspace", , FORMAT_U, 0},
 	{"notespacingfactor", , FORMAT_R, 1},
--- a/music.c
+++ b/music.c
@@ -3330,6 +3330,9 @@
 
 		// if bar already, keep it in sequence
 		voice = p_voice - voice_tb;
+		bar_start = p_voice->bar_start;
+		p_voice->bar_start = 0;
+
 		if (last_s
 		 && last_s->voice == voice && last_s->type == BAR) {
 			p_voice->last_sym = last_s;
@@ -3337,10 

Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

[Salvatore Bonaccorso]

Hi 

On Tue, Sep 15, 2020 at 02:00:51PM +0530, Vasudev Kamath wrote:
> Tzafrir Cohen  writes:
> 
> > Hi,
> >
> > A patch for fix of the regression is in 4.19.145 (commit 
> > 044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys 
> > switch id if not in switchdev mode").
> >
> > Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster 
> > kernel tree.
> >
> > -- Tzafrir
> 
> I just created another ticket as this bug is already archived [1]. And
> mail is not getting tracked in the BTS.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970350

Please have look at 
https://salsa.debian.org/kernel-team/linux/-/merge_requests/278 

Still it should be evaluated if this has no other impact as it was
previously only enabled for armhf.

Regards,
Salvatore

Bug#962747: sane-backends: further tests

[Ben Ruhnow]

Source: sane-backends
Followup-For: Bug #962747
X-Debbugs-Cc: b.ruh...@web.de

Dear Maintainer,

after further test of my scanner and upgrades of the packages, it seems that 
everything works fine.

Thanks a lot,

Ben

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: 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

Bug#768005: retitle

[Diederik de Haas]

Control: retitle -1 Please add bash-completion support for xl commands

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