Bug#980280: remmina: Window closes after entering password every other time

[Philip Wyett]

On Sun, 2021-01-17 at 06:58 +, Philip Wyett wrote:
> On Sun, 2021-01-17 at 06:43 +, Philip Wyett wrote:
> > Package: remmina
> > Version: 1.4.10+dfsg-1
> > Severity: normal
> > 
> > Hi,
> > 
> > When trying to access remote desktop. Entering password and
> > proceeding
> > results in every other time be that hitting ENTER or using mouse to
> > click on OK, will result in window closing.
> > 
> > In test case. buster/stable (xorg) with remmina backport to updated
> > bullseye/testing (wayland) machine running gnome-remote-desktop.
> > 
> > Videos attached to show issue.
> > 
> > Regards
> > 
> > Phil
> > 
> 
> Also affects bullseye/testing and sid/unstable (wayland) when
> attempting to access gnome-remote-desktop on bullseye/testing
> (wayland)
> machine.
> 
> Regards
> 
> Phil
> 

Hi,

Debug window output when window closes on attempting to connect.

(remmina_plugin_vnc_rfb_output) - VNC returned: colordepth  =
32
(remmina_plugin_vnc_rfb_output) - VNC returned: format.depth=
24
(remmina_plugin_vnc_rfb_output) - VNC returned: format.bitsPerPixel =
32
(remmina_plugin_vnc_rfb_output) - VNC returned: format.blueShift= 0
(remmina_plugin_vnc_rfb_output) - VNC returned: format.redShift =
16
(remmina_plugin_vnc_rfb_output) - VNC returned: format.trueColour   = 1
(remmina_plugin_vnc_rfb_output) - VNC returned: format.greenShift   = 8
(remmina_plugin_vnc_rfb_output) - VNC returned: format.blueMax  =
255
(remmina_plugin_vnc_rfb_output) - VNC returned: format.redMax   =
255
(remmina_plugin_vnc_rfb_output) - VNC returned: format.greenMax =
255
(remmina_plugin_vnc_rfb_output) - VNC returned: format.bigEndian= 0
(remmina_plugin_vnc_rfb_output) - VNC returned: VNC server supports
protocol version 3.8 (viewer 3.8)
(remmina_plugin_vnc_rfb_output) - VNC returned: We have 1 security
types to read
(remmina_plugin_vnc_rfb_output) - VNC returned: 0) Received security
type 2
(remmina_plugin_vnc_rfb_output) - VNC returned: Selecting security type
2 (0/1 in the list)
(remmina_plugin_vnc_rfb_output) - VNC returned: Selected Security
Scheme 2
(rmnews_periodic_check) - periodic_rmnews_last_get is 0
(rmnews_periodic_check) - remmina_pref.periodic_news_permitted is 0
(remmina_plugin_vnc_rfb_output) - VNC returned: VNC authentication
succeeded
(remmina_plugin_vnc_rfb_output) - VNC returned: Desktop name "GNOME"
(remmina_plugin_vnc_rfb_output) - VNC returned: Connected to VNC
server, using protocol version 3.8
(remmina_plugin_vnc_rfb_output) - VNC returned: VNC server default
format:
(remmina_plugin_vnc_rfb_output) - VNC returned:   32 bits per pixel.
(remmina_plugin_vnc_rfb_output) - VNC returned:   Least significant
byte first in each pixel.
(remmina_plugin_vnc_rfb_output) - VNC returned:   TRUE colour: max red
255 green 255 blue 255, shift red 16 green 8 blue 0
(rco_on_connect) - Connect signal emitted
(rco_on_connect) - Saving credentials
(rco_on_connect) - Trying to present the window
(remmina_plugin_vnc_rfb_output) - VNC returned: Got new framebuffer
size: 1366x768
(remmina_plugin_vnc_rfb_output) - VNC returned: client2server supported
messages (bit flags)
(remmina_plugin_vnc_rfb_output) - VNC returned: 00: 00ff 0081  
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: 08:    
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: 10:    
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: 18:    
-    0008
(remmina_plugin_vnc_rfb_output) - VNC returned: server2client supported
messages (bit flags)
(remmina_plugin_vnc_rfb_output) - VNC returned: 00: 001f 0080  
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: 08:    
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: 10:    
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: 18:    
-    
(remmina_plugin_vnc_rfb_output) - VNC returned: Connected to Server
"GNOME Remote Desktop (VNC) (LibVNCServer 0.9.13)"
(remmina_plugin_vnc_rfb_output) - VNC returned: read (104: Connection
reset by peer)
(rco_on_disconnect) - Disconnect signal received on
RemminaProtocolWidget
(rco_on_disconnect) - Disconnected
(rmnews_periodic_check) - periodic_rmnews_last_get is 0
(rmnews_periodic_check) - remmina_pref.periodic_news_permitted is 0

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#980282: Should depend on gnome-remote-desktop instead of vino

[David Prévot]

Package: gnome
Version: 1:3.38+2
Severity: wishlist
X-Debbugs-Cc: Philip Wyett 
Control: submitter -1 Philip Wyett 

The following report was sent to debian-devel@l.d.o.

Hi,

Installing Debian testing and now also using bullseye-DI-alpha3, the
default desktop install/gnome is still installing vino and not
installing gnome-remote-desktop by default.

As we know, vino does not work with wayland and is not being actively
developed and focus has shifted to the wayland ready gnome-remote-
desktop.

Could we pre bullseye general availability (GA), rectify this issue and
have gnome-remote-desktop as the default installed?

Regards

Phil


signature.asc
Description: PGP signature

Bug#980281: q2-dada2: autopkgtest failure: missing depends python3-biom-format

[Juhani Numminen]

Package: q2-dada2
Version: 2020.11.1-1
Severity: serious

Hi!

Debci reports the following failure (source: 
https://ci.debian.net/packages/q/q2-dada2/testing/amd64/)

 ERRORS 
___ ERROR collecting q2_dada2/tests/test_denoise.py 
ImportError while importing test module 
'/tmp/autopkgtest-lxc.nkzw0lkg/downtmp/autopkgtest_tmp/q2_dada2/tests/test_denoise.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
q2_dada2/__init__.py:9: in 
from ._denoise import denoise_single, denoise_paired, denoise_pyro
q2_dada2/_denoise.py:14: in 
import biom
E   ModuleNotFoundError: No module named 'biom'

That is, q2-dada2 tries to import biom but does not declare
Depends: python3-biom-format. 

--
Juhani

Bug#980280: remmina: Window closes after entering password every other time

[Philip Wyett]

On Sun, 2021-01-17 at 06:43 +, Philip Wyett wrote:
> Package: remmina
> Version: 1.4.10+dfsg-1
> Severity: normal
> 
> Hi,
> 
> When trying to access remote desktop. Entering password and
> proceeding
> results in every other time be that hitting ENTER or using mouse to
> click on OK, will result in window closing.
> 
> In test case. buster/stable (xorg) with remmina backport to updated
> bullseye/testing (wayland) machine running gnome-remote-desktop.
> 
> Videos attached to show issue.
> 
> Regards
> 
> Phil
> 

Also affects bullseye/testing and sid/unstable (wayland) when
attempting to access gnome-remote-desktop on bullseye/testing (wayland)
machine.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#980119: libgnutls30: "An unexpected TLS packet was received" when connecting to FTPS (FTP/TLS) servers

[Andreas Metzler]

On 2021-01-16 "Boyd Stephen Smith Jr."  wrote:
> On Saturday, January 16, 2021 6:35:13 AM CST Andreas Metzler wrote:
> > Does
> > env GNUTLS_DEBUG_LEVEL=4711 lftp 
> > produce more verbose output?

> Yes.  But, probably not verbose enough:
> ---8<---
> % env GNUTLS_DEBUG_LEVEL=4711 lftp -u boyd.stephen.smith...@gmail.com.125388 
> bos-sr-2-36.akliz.net
> gnutls[2]: Enabled GnuTLS 3.7.0 logging...
> gnutls[2]: getrandom random generator was detected
> gnutls[2]: Intel SSSE3 was detected
> gnutls[2]: Intel SHA was detected
> gnutls[2]: Intel AES accelerator was detected
> gnutls[2]: Intel GCM accelerator (AVX) was detected
> gnutls[2]: cfg: unable to access: /etc/gnutls/config: 2
> Password: 
> lftp boyd.stephen.smith...@gmail.com.125...@bos-sr-2-36.akliz.net:~> ls
> ls: Fatal error: gnutls_record_recv: An unexpected TLS packet was received.
> --->8---

Hello,

ah, lftp overrides this with gnutls_global_set_log_level(). Does wget
also fail? If it does can you try something like
env GNUTLS_DEBUG_LEVEL=4711 wget --verbose--debug --ask-password 
--user=boyd.stephen.smith...@gmail.com.125388 
ftps://bos-sr-2-36.akliz.net/somefile 

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#980279: remmina: UK keyboard @ translates to Ω on machine being accessed

[Philip Wyett]

Package: remmina
Version: 1.4.10+dfsg-1
Severity: normal

UK keyboard @ translates to Ω on machine being accessed.

In test case. buster/stable (xorg) with remmina backport to updated
bullseye/testing (wayland) machine running gnome-remote-desktop.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#980278: dar: par2 support doesn't work

[John Goerzen]

Package: dar
Version: 2.6.2-1+b10
Severity: normal

Hi,

According to the manpage, I should be able to add "par2" and just have that 
work.  However, I had several issues:

1) First, it said it was an unrecognized target.  par2 was listed in 
/etc/darrc, but I had to add -B /etc/darrc for par2 to be recognized.

2) /usr/share/doc/dar/examples/dar_par.dcf has the wrong path to 
dar_par_create.duc and dar_par_test.duc (they are in 
/usr/share/doc/dar/examples, not /usr/share/dar/samples).

I'm not entirely sure that /usr/share/doc/dar/examples is a good place for 
something that gets invoked in this manner, but that is a more minor and 
perhaps separate question.


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

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

Versions of packages dar depends on:
ii  libassuan0 2.5.2-1
ii  libattr1   1:2.4.48-4
ii  libbz2-1.0 1.0.6-9.2~deb10u1
ii  libc6  2.28-10
ii  libdar64-6000  2.6.2-1+b10
ii  libgcc11:8.3.0-6
ii  libgcrypt201.8.4-5
ii  libgpg-error0  1.35-1
ii  libgpgme11 1.12.0-6
ii  liblzma5   5.2.4-1
ii  liblzo2-2  2.10-0.1
ii  libstdc++6 8.3.0-6
ii  zlib1g 1:1.2.11.dfsg-1

dar recommends no packages.

Versions of packages dar suggests:
ii  dar-docs  2.6.2-1
ii  par2  0.8.0-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/doc/dar/examples/dar_par.dcf (from dar package)

Bug#918075: Newer librsync now available

[John Goerzen]

Hi,

Sid and bullseye now have a newer librsync; perhaps this can be 
done yet before freeze, at least for binary deltas?


Thanks!

John

Bug#980273: util-linux: overzealous canonicalization breaks zfs mounts

[Antonio Russo]

Package: util-linux
Version: 2.36.1-4
Severity: important
Tags: patch

Dear maintainer,

Recent version of util-linux include a new feature to canonicalize paths
related to mounting.  Unfortunately, this mangles non-path descriptions
used by some filesystems (in this case, zfs), because the string being
passed to libmount happens to correspond to an actual path, causing
libmount to add a / character at the beginning---see [1] and discussions
referenced in [2].

Upstream has addressed this (at least for zfs) in [2], which is not yet
included in the Debian version.

Would it be possible to cherry-pick that commit?

Thanks,
Antonio Russo

[1] https://github.com/openzfs/zfs/issues/11448
[2] 
https://github.com/karelzak/util-linux/commit/372ce5b74e79470b1bda1fc284c19a313a422361


OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#980277: gcc: c99(1) provided by c99-gcc(1) isn't conforming to POSIX

[WHR]

Package: gcc
Version: 4:8.3.0-1
Severity: minor

POSIX has option '-O ' for c99(1) command, which means 'c99 -O 1 ...'
should be exactly same as 'c99 -O1 ...'; however it is not in c99-gcc(1):

$ ls -l /etc/alternatives/c99
lrwxrwxrwx 1 root root 16 Sep 14 17:12 /etc/alternatives/c99 -> /usr/bin/c99-gcc
$ c99 -O1 hello.c 
$ c99 -O 1 hello.c 
gcc: error: 1: No such file or directory

See https://pubs.opengroup.org/onlinepubs/9699919799/utilities/c99.html

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

Kernel: Linux 4.19.147-rivoreo-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc depends on:
ii  cpp4:8.3.0-1
ii  gcc-8  8.3.0-6

Versions of packages gcc recommends:
ii  libc6-dev [libc-dev]  2.28-10

Versions of packages gcc suggests:
ii  autoconf  2.69-11
ii  automake  1:1.16.1-4
ii  bison 2:3.3.2.dfsg-1
ii  flex  2.6.4-6.2
pn  gcc-doc   
pn  gcc-multilib  
ii  gdb   8.2.1-2+b3
ii  libtool   2.4.6-9
ii  make  4.2.1-1.2
ii  manpages-dev  4.16-2

-- no debconf information

Bug#980261: RFS: jgmenu/4.3.0-1 [RFP] -- Simple X11 menu

[Leandro Cunha]

Hi,

Change the bug to ITP instead of RFP and put you as
the owner and after that you block the ITP bug to this
bug.

[1] https://www.debian.org/devel/wnpp/index.en.html
[2] https://www.debian.org/Bugs/server-control.html

Thanks!

-- 
Cheers,
Leandro Cunha
Debian Contributor and developer.

Bug#980276: Chromium freeze with video reproduction using nouveau

[leandro]

Package: chromium
Version: 87.0.4280.141-0.1
Severity: important
Tags: upstream

Chromium is freezing when playing videos on YouTube for example affecting the
entire system using Nouveau, not know this problem occurs on other hardware.



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

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 chromium depends on:
ii  chromium-common  87.0.4280.141-0.1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-6
ii  libavformat587:4.3.1-6
ii  libavutil56  7:4.3.1-6
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op1-7
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.103-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.3-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.6.7-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.1-1
ii  libre2-9 20201101+dfsg-2
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libx11-xcb1  2:1.7.0-2
ii  libxcb1  1.14-2.1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  87.0.4280.141-0.1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n87.0.4280.141-0.1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-2
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox   87.0.4280.141-0.1
ii  fonts-liberation   1:1.07.4-11
ii  gnome-shell [notification-daemon]  3.38.3-1
ii  libgl1-mesa-dri20.3.3-1
ii  libu2f-udev1.1.10-3
ii  notification-daemon3.20.0-4
ii  system-config-printer  1.5.14-1
ii  upower 0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- no debconf information

Bug#980272: nodejs: '/usr/bin/node' started with executable stack

[James Addison]

Package: nodejs
Version: 14.13.0~dfsg-1
Severity: normal
X-Debbugs-Cc: j...@jp-hosting.net

Dear Maintainer,

The /usr/bin/node ELF binary in the nodejs package has an executable stack and
although I'm not certain whether this implies any potential for attack, it
seemed worth reporting.  I do not believe that the binary requires an
executable stack.

The following command can be used to read and check the stack headers for the
binary:

$ readelf --program-headers --wide /usr/bin/node | grep -w GNU_STACK
  GNU_STACK  0x00 0x 0x 0x00 
0x00 RWE 0x10


In particular the flags (RWE above) include the 'E' flag for executable in the
package versions checked, which are: 12.19.0~dfsg-1 (bullseye), 12.20.1~dfsg-3
(sid) and 14.13.0~dfsg-1 (experimental).

This was discovered from observation of the following message in the dmesg
output on a Debian host:

'/usr/bin/node' started with an executable stack


There's some potentially-relevant reading in the Ubuntu and Gentoo security
team documentation below:

- https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart
- https://wiki.ubuntu.com/SecurityTeam/Roadmap/ExecutableStacks


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

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

Versions of packages nodejs depends on:
ii  libc6  2.31-9
ii  libnode83  14.13.0~dfsg-1

Versions of packages nodejs recommends:
ii  ca-certificates  20200601
pn  nodejs-doc   

Versions of packages nodejs suggests:
pn  npm  

-- no debconf information

Bug#948698: [Python-modules-team] Bug#948698: python3-flask-sqlalchemy: Please update to latest release 2.4.1

[Nick Gasson]

On 01/12/20 11:31 am, Emmanuel Arias wrote:
>
> I've just push to salsa, the new upstream release.
>
> I will need sponsorship, please.
>

Any chance of the updated version getting into the bullseye release?

--
Thanks,
Nick

Bug#980270: python3-setools: needs newer dependencies

[Russell Coker]

Package: python3-setools
Version: 4.3.0-1.1+b1
Severity: normal

# sesearch -A -s httpd_t -d httpd_sys_content_t
Traceback (most recent call last):
  File "/usr/bin/sesearch", line 20, in 
import setools
  File "/usr/lib/python3/dist-packages/setools/__init__.py", line 78, in 

from .infoflow import InfoFlowAnalysis
  File "/usr/lib/python3/dist-packages/setools/infoflow.py", line 23, in 

import networkx as nx
  File "/usr/lib/python3/dist-packages/networkx/__init__.py", line 114, in 

import networkx.generators
  File "/usr/lib/python3/dist-packages/networkx/generators/__init__.py", line 
14, in 
from networkx.generators.intersection import *
  File "/usr/lib/python3/dist-packages/networkx/generators/intersection.py", 
line 13, in 
from networkx.algorithms import bipartite
  File "/usr/lib/python3/dist-packages/networkx/algorithms/__init__.py", line 
16, in 
from networkx.algorithms.dag import *
  File "/usr/lib/python3/dist-packages/networkx/algorithms/dag.py", line 23, in 

from fractions import gcd
ImportError: cannot import name 'gcd' from 'fractions' 
(/usr/lib/python3.9/fractions.py)

The above happens on a system that hasn't had a full dist-upgrade, just
upgrades of selected packages and their dependencies.

Firstly the package depends on libsepol1 (>= 2.9), if that was even possible
to install it probably wouldn't work.  Changing the dependencies to the latest
version of the SE Linux libraries every time is probably the best strategy.

It turns out that having python3-networkx version 2.2-1 installed (significantly
newer than the version 2.0 that python3-setools depends on) caused the problem.
Upgrading python3-networkx to 2.5+ds-2 made sesearch work correctly.

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages python3-setools depends on:
ii  libc6  2.31-9
ii  libselinux13.1-2+b2
ii  libsepol1  3.1-1
ii  python33.9.1-1
ii  python3-networkx   2.2-1
ii  python3-pkg-resources  40.8.0-1

python3-setools recommends no packages.

python3-setools suggests no packages.

-- no debconf information

Bug#980067: libqmatrixclient: new upstream release, with a rename

[Hubert Chathi]

On Wed, 13 Jan 2021 14:54:55 -0500, Andres Salomon  said:

> There have been several new releases of this package, with the latest
> version being 0.6.3. In addition, the upstream package was renamed to
> libQuotient. It would be good to get a newer package that includes the
> rename.

Hi Andres,

Upstream has indicated that it may be a good idea for us to package the
next Quaternion beta in Debian, which will require libQuotient.  Will
you be able to upload it soon? (e.g. within the next week?)  If not, I
can look into packaging and uploading it on Monday.

BTW, feel free to join us in #debian-matrix:matrix.org

Hubert

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

Bug#980236: u-boot: Stop exporting CROSS_COMPILE

[Vagrant Cascadian]

Control: tags 980236 -patch

On 2021-01-16, Nicolas Boulenguez wrote:
> debian/rules sets CROSS_COMPILE in the environment and the Make
> command line.
>
> Makefile overrides the environment with the value from the command
> line, so the export by debian/rules is a confusing no-op.

With this applied, an attempted cross compile shows the exported
variable is still needed:

  ld.bfd: arch/arm/lib/crt0_64.o: Relocations in generic ELF (EM: 183)
  ld.bfd: arch/arm/lib/crt0_64.o: Relocations in generic ELF (EM: 183)
  ld.bfd: arch/arm/lib/crt0_64.o: Relocations in generic ELF (EM: 183)
  ld.bfd: arch/arm/lib/crt0_64.o: Relocations in generic ELF (EM: 183)
  ld.bfd: arch/arm/lib/crt0_64.o: error adding symbols: file in wrong
  format
  make[4]: *** [/<>/scripts/Makefile.build:342:
  arch/arm/lib/built-in.o] Error 1
  make[4]: *** Waiting for unfinished jobs
  make[3]: *** [/<>/Makefile:1784: arch/arm/lib] Error 2
  make[3]: Leaving directory
  '/<>/debian/build/pinebook-pro-rk3399'
  make[2]: *** [Makefile:167: sub-make] Error 2
  make[2]: Leaving directory '/<>'
  dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true"
  PKG_CONFIG=aarch64-linux-gnu-pkg-config CXX=aarch64-linux-gnu-g\+\+
  CC=aarch64-linux-gnu-gcc V=1 O=debian/build/pinebook-pro-rk3399 returned
  exit code 2


Other tools in u-boot's Makefiles probably need it as well...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#980275: Please depend on media-types instead of mime-support

[Charles Plessy]

Package: apache2

Dear apache2 maintainers,

I have recently split the `mime-support` package into two: `mailcap` for
the mailcap system, and `media-types` for providing `/etc/mime.types`.
The goal is to allow minimal systems without `mailcap`.

`mime-support` is now a transitional package, and it would be great if
users could be able to remove it after the _Bookworm_ release.

Please Depend on `media-types` instead of `mime-support` if you only
need the `/etc/mime.types` file.

Have a nice week-end,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Tooting from work,   https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy

Bug#980274: lomiri-api: Symbol mismatch when built with -O3

[Logan Rosen]

Package: lomiri-api
Version: 0.1.1-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Hi,

We build on ppc64el in Ubuntu with -O3 enabled, and there is a symbol
mismatch for lomiri-api. [1]

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

  * Mark two symbols as optional to fix build with -O3 on ppc64el.

Thanks for considering the patch.

Logan

[1] https://launchpad.net/ubuntu/+source/lomiri-api/0.1.1-3/+build/20205674
diff -Nru lomiri-api-0.1.1/debian/liblomiri-api0.symbols 
lomiri-api-0.1.1/debian/liblomiri-api0.symbols
--- lomiri-api-0.1.1/debian/liblomiri-api0.symbols  2020-09-27 
14:30:59.0 -0400
+++ lomiri-api-0.1.1/debian/liblomiri-api0.symbols  2021-01-16 
20:01:23.0 -0500
@@ -128,8 +128,8 @@
  _ZNK6lomiri9Exception6reasonB5cxx11Ev@Base 0.1.0
  
_ZNK6lomiri9Exception9to_stringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.1.0
  
_ZNK6lomiri9Exception9to_stringEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.1.0
- _ZNSt14_Function_baseD1Ev@Base 0.1.1
- _ZNSt14_Function_baseD2Ev@Base 0.1.1
+ (optional=templinst)_ZNSt14_Function_baseD1Ev@Base 0.1.1
+ (optional=templinst)_ZNSt14_Function_baseD2Ev@Base 0.1.1
  
(optional=templinst)_ZNSt15__exception_ptr12__dest_thunkIN6lomiri13FileExceptionEEEvPv@Base
 0.1.0
  
(optional=templinst)_ZNSt15__exception_ptr12__dest_thunkIN6lomiri14LogicExceptionEEEvPv@Base
 0.1.0
  
(optional=templinst)_ZNSt15__exception_ptr12__dest_thunkIN6lomiri16SyscallExceptionEEEvPv@Base
 0.1.0

Bug#957383: jamin: ftbfs with GCC-10

[Logan Rosen]

Package: jamin
Version: 0.98.9~git20170111~199091~repack1-1
Followup-For: Bug #957383
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

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

  * d/p/gcc_10.patch: Fix FTBFS with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch 
jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch
--- jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch 
1969-12-31 19:00:00.0 -0500
+++ jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch 
2021-01-16 20:57:51.0 -0500
@@ -0,0 +1,21 @@
+--- a/src/hdeq.h
 b/src/hdeq.h
+@@ -65,7 +65,7 @@
+ int get_current_notebook1_page ();
+ 
+ 
+-GtkNotebook *l_notebook1;
++extern GtkNotebook *l_notebook1;
+ 
+ 
+ #endif
+--- a/src/callbacks.c
 b/src/callbacks.c
+@@ -71,6 +71,7 @@
+ static GtkWidget*scene_name_dialog, *about_dialog;
+ static GtkEntry *l_scene_name_entry;
+ static GdkColor l_main_color, l_eq_color, l_comp_color[XO_NBANDS], 
l_limiter_color;
++GtkNotebook *l_notebook1;
+ 
+ 
+ void
diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/patches/series 
jamin-0.98.9~git20170111~199091~repack1/debian/patches/series
--- jamin-0.98.9~git20170111~199091~repack1/debian/patches/series   
2017-01-11 15:31:55.0 -0500
+++ jamin-0.98.9~git20170111~199091~repack1/debian/patches/series   
2021-01-16 20:57:34.0 -0500
@@ -5,3 +5,4 @@
 1005_desktop_file.patch
 NEWS.patch
 fix_typos.patch
+gcc_10.patch

Bug#957478: libsml: ftbfs with GCC-10

[Logan Rosen]

Package: libsml
Version: 0.1.1+git20180125-1
Followup-For: Bug #957478
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

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

  * d/p/gcc-10.patch: Cherrypick upstream Git commit to fix FTBFS with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru libsml-0.1.1+git20180125/debian/patches/gcc-10.patch 
libsml-0.1.1+git20180125/debian/patches/gcc-10.patch
--- libsml-0.1.1+git20180125/debian/patches/gcc-10.patch1969-12-31 
19:00:00.0 -0500
+++ libsml-0.1.1+git20180125/debian/patches/gcc-10.patch2021-01-16 
20:21:25.0 -0500
@@ -0,0 +1,200 @@
+From 0738cd50632eadb9cd2c21e07b70f984a9cf444b Mon Sep 17 00:00:00 2001
+From: r00t 
+Date: Mon, 28 Dec 2020 01:03:43 +0100
+Subject: [PATCH] [test] fix building with -fno-common (gcc10 default),
+
+see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
+---
+ test/src/sml_boolean_test.c  | 2 +-
+ test/src/sml_buffer_test.c   | 2 +-
+ test/src/sml_file_test.c | 2 +-
+ test/src/sml_get_profile_pack_request_test.c | 2 +-
+ test/src/sml_list_test.c | 4 ++--
+ test/src/sml_message_test.c  | 2 +-
+ test/src/sml_number_test.c   | 2 +-
+ test/src/sml_octet_string_test.c | 2 +-
+ test/src/sml_open_request_test.c | 2 +-
+ test/src/sml_status_test.c   | 2 +-
+ test/src/sml_time_test.c | 2 +-
+ test/src/sml_tree_test.c | 2 +-
+ test/src/sml_value_test.c| 2 +-
+ 13 files changed, 14 insertions(+), 14 deletions(-)
+
+diff --git a/test/src/sml_boolean_test.c b/test/src/sml_boolean_test.c
+index 90b5f3d..0fbebf1 100644
+--- a/test/src/sml_boolean_test.c
 b/test/src/sml_boolean_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_boolean);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_boolean) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_buffer_test.c b/test/src/sml_buffer_test.c
+index bf8e714..45eacc2 100644
+--- a/test/src/sml_buffer_test.c
 b/test/src/sml_buffer_test.c
+@@ -22,7 +22,7 @@
+ TEST_GROUP(sml_buffer);
+ 
+ int buffer_len = 512;
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_buffer) {
+   buf = sml_buffer_init(buffer_len);
+diff --git a/test/src/sml_file_test.c b/test/src/sml_file_test.c
+index 1b1bb15..9ded16f 100644
+--- a/test/src/sml_file_test.c
 b/test/src/sml_file_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_file);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_file) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_get_profile_pack_request_test.c 
b/test/src/sml_get_profile_pack_request_test.c
+index c03d6ab..44f1f07 100644
+--- a/test/src/sml_get_profile_pack_request_test.c
 b/test/src/sml_get_profile_pack_request_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_get_profile_pack_request);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_get_profile_pack_request) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_list_test.c b/test/src/sml_list_test.c
+index 9a5f583..56d6ed2 100644
+--- a/test/src/sml_list_test.c
 b/test/src/sml_list_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_list);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_list) {
+   buf = sml_buffer_init(512);
+@@ -100,7 +100,7 @@ TEST_GROUP_RUNNER(sml_list) {
+ 
+ TEST_GROUP(sml_sequence);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_sequence) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_message_test.c b/test/src/sml_message_test.c
+index 7462435..3d4bb07 100644
+--- a/test/src/sml_message_test.c
 b/test/src/sml_message_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_message);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_message) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_number_test.c b/test/src/sml_number_test.c
+index 9a5eece..09c00ca 100644
+--- a/test/src/sml_number_test.c
 b/test/src/sml_number_test.c
+@@ -23,7 +23,7 @@
+ 
+ TEST_GROUP(sml_number);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_number) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_octet_string_test.c 
b/test/src/sml_octet_string_test.c
+index 2a47632..c37d219 100644
+--- a/test/src/sml_octet_string_test.c
 b/test/src/sml_octet_string_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_octet_string);
+ 
+-sml_buffer *buf;
++static sml_buffer *buf;
+ 
+ TEST_SETUP(sml_octet_string) {
+   buf = sml_buffer_init(512);
+diff --git a/test/src/sml_open_request_test.c 
b/test/src/sml_open_request_test.c
+index 89beba5..23b917f 100644
+--- a/test/src/sml_open_request_test.c
 b/test/src/sml_open_request_test.c
+@@ -22,7 +22,7 @@
+ 
+ TEST_GROUP(sml_open_request);
+ 
+-sml_buffer 

Bug#978674: python3-build: Fails to work unless pip is installed

[Sergio Durigan Junior]

On Tuesday, December 29 2020, Martina Ferrari wrote:

> As I was trying out the new PEP-517 build system, I installed python3-build 
> and
> tried to run it, only to get this stacktrace:
>
> /tmp/build-env-axtchyw0/bin/python: No module named ensurepip
> /tmp/build-env-axtchyw0/bin/python: No module named pip
> Traceback (most recent call last):
>   File "/usr/bin/pyproject-build", line 33, in 
> sys.exit(load_entry_point('build==0.1.0', 'console_scripts', 
> 'pyproject-build')())
>   File "/usr/lib/python3/dist-packages/build/__main__.py", line 206, in 
> entrypoint
> main(sys.argv[1:])
>   File "/usr/lib/python3/dist-packages/build/__main__.py", line 202, in main
> build_package(args.srcdir, outdir, distributions, config_settings, not 
> args.no_isolation, args.skip_dependencies)
>   File "/usr/lib/python3/dist-packages/build/__main__.py", line 81, in 
> build_package
> _build_in_isolated_env(builder, outdir, distributions)
>   File "/usr/lib/python3/dist-packages/build/__main__.py", line 45, in 
> _build_in_isolated_env
> with IsolatedEnvBuilder() as env:
>   File "/usr/lib/python3/dist-packages/build/env.py", line 55, in __enter__
> executable, pip_executable = _create_isolated_env(self._path)
>   File "/usr/lib/python3/dist-packages/build/env.py", line 187, in 
> _create_isolated_env
> subprocess.check_call([executable, '-Im', 'pip', 'uninstall', 
> 'setuptools', '-y'])
>   File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command 
> '['/tmp/build-env-axtchyw0/bin/python', '-Im', 'pip', 'uninstall', 
> 'setuptools', '-y']' returned non-zero exit status 1.
>
>
> I don't know why build requires pip (I don't think it should?), but in any 
> case
> it seems it should be added as a dependency.

Thanks for the bug report, Martina.

Yeah, this is strange.  I don't think it should require pip, and after
installing python3-pip here and re-running /usr/bin/pyproject-build I
noticed that it (obviously) invokes pip and downloads several things,
which IMO is a no-no.

The reason I packaged python3-build is because check-manifest started
depending on it.  I'm thinking about removing the
/usr/bin/pyproject-build program and just shipping the library.  Do you
think it could work?  (Sorry, I'm not a PEP-517 expert).

Thanks in advance,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#967989: lookup: Removal of sys_nerr and sys_errlist

[Logan Rosen]

Package: lookup
Version: 1.08b-12
Followup-For: Bug #967989
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch

Hi,

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

  * lib/output.c: Fix FTBFS against glibc 2.32 by using strerror() instead of
removed sys_nerr and sys_errlist.

Thanks for considering the patch.

Logan
diff -u lookup-1.08b/lib/output.c lookup-1.08b/lib/output.c
--- lookup-1.08b/lib/output.c
+++ lookup-1.08b/lib/output.c
@@ -769,13 +769,7 @@
else
errval = errno;
 
-   if (errval >= 0 && errval < sys_nerr)
-   str = sys_errlist[errval];
-   else
-   {
-   sprintf(temp_error_buff, "#%d", errval);
-   str = temp_error_buff;
-   }
+   str = strerror(errval);
}
 
if (format[-2] == '%')

Bug#123150: bb audio still causes video to stop iff pulseaudio is installed

[Axel Beckert]

Hi Matt,

thanks for the prompt response!

Matt Taggart wrote:
> On 1/16/21 10:25 AM, Axel Beckert wrote:
> 
> > Matt: You said, you had the issue also on the console. Could you check
> > if that "pasuspender -- env PULSE_SERVER= bb" command workarounds the
> > issue for you on the virtual console, too? Maybe there's more virtual
> > console support from pulseaudio nowadays…
> 
> When I run that on a vc I get a brief error flash by about not being able to
> open an audio device and then BB runs, but no audio (even though I selected
> it). But at least it doesn't hang.

I see. Might be a separate issue then, not necessarily in bb.

Then again, in the meanwhile I was able to reproduce this issue even
on a virtual console — on a minimal Raspberry Pi running Debian
Testing/Bullseye. It was more or less a minimal installation. I
installed pulseaudio and rebooted to be sure the logins are setup with
pulseaudio.

I though also got a lot of pulseaudio warnings on the console about
audio driver issues. But these seemed hardware-specific.

But in the end, the workaround described in the README.Debian with
"pasuspend -- env PULSE_SERVER= bb" worked there, too.

So I will simplify the README.Debian and focus on that variant as it
seems to help in most if not all cases.

Oh, and I found another workaround, but I can't really recommend it:
Run it as root on the virtual console. Seems to work because
pulseaudio isn't started for root. ;-D

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#980271: installation-reports: Toshiba Tecra 8000 Installation report Bullseye

[Charles Curley]

Package: installation-reports
Severity: normal
Tags: d-i
X-Debbugs-Cc: charlescur...@charlescurley.com

Dear Maintainer,

-- Package-specific info:

Boot method: CD-ROM
Image version: debian-bullseye-DI-alpha3-i386-netinst.iso
Date: 14 January 2021

Machine: Toshiba Tecra 8000
Partitions: 

Filesystem Type  Size  Used Avail Use% Mounted on
udev   devtmpfs  110M 0  110M   0% /dev
tmpfs  tmpfs  25M  560K   24M   3% /run
/dev/sda6  ext4  6.8G  1.1G  5.4G  17% /
tmpfs  tmpfs 121M 0  121M   0% /dev/shm
tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
tmpfs  tmpfs 4.0M 0  4.0M   0% /sys/fs/cgroup
/dev/sda2  ext4   95M   35M   53M  40% /boot
tmpfs  tmpfs  25M 0   25M   0% /run/user/1000
tmpfs  tmpfs  25M 0   25M   0% /run/user/0

Disk /dev/sda: 7.63 GiB, 8195604480 bytes, 16007040 sectors
Disk model: IBM-DYLA-28100  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000ce2ac

Device Boot   Start  End  Sectors   Size Id Type
/dev/sda1  * 63   208844   208782 101.9M  b W95 FAT32
/dev/sda2208845   417689   208845   102M 83 Linux
/dev/sda3417751 16000739 15582989   7.4G  5 Extended
/dev/sda5417753  1461914  1044162 509.8M 82 Linux swap / Solaris
/dev/sda6   1461978 16000739 14538762   6.9G 83 Linux



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [E]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Installed via debian-bullseye-DI-alpha3-i386-netinst.iso. Expert
install via text using a RW-CD. Due to low memory, language and
keyboard are US English, which is fine for me.

The d-i kernel gets hung up for a while on "probing EDD". I haven't
tried adding "edd=off" to the command line yet.

For obvious reasons, d-i used low memory mode. Also, the installer is
*slow*. If you must install on this machine, have patience.

d-i does not detect the Ethernet card. This machine has a Netgear FA411
Ethernet card in a PCMCIA; it seems to like the axnet_cs driver. Even
after I selected it in the menu, d-i didn't use it. It worked in
Stretch. Once the installation was complete, all I had to do was add it
to /etc/network/interfaces, and run "ifup eth0".

However, it does not continue to work smoothly, so it may be a a
hardware issue. I get a lot of dropped packets, frame errors, and
errors on RX; none on TX. Misconfiguration of the Ethernet
configuration???

I got an entirely bogus question about installing GRUB in the EFI
fallback. Would a machine this old have EFI on it?

According to d-i, the BIOS has corrupted hw-PMU resources (MSR-186 is
40002e). Whatever that means.

The graphical installer bombed. I don't think it could launch X. I did
not investigate.

fdisk seems to think it has a floppy disk at fd0. It doesn't.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20201202"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux (none) 5.9.0-4-686 #1 SMP Debian 5.9.11-1 (2020-11-27) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 
82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 02)
lspci -knn: Subsystem: Toshiba Corporation Satellite 4010 [1179:0001]
lspci -knn: 00:04.0 VGA compatible controller [0300]: Neomagic Corporation 
NM2200 [MagicGraph 256AV] [10c8:0005] (rev 20)
lspci -knn: Subsystem: Toshiba Corporation Device [1179:0001]
lspci -knn: 00:05.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ISA 
[8086:7110] (rev 02)
lspci -knn: 00:05.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:05.2 USB controller [0c03]: Intel Corporation 82371AB/EB/MB 
PIIX4 USB [8086:7112] (rev 01)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB 

Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3

[Sudip Mukherjee]

Thanks Moritz.

On Sat, Jan 16, 2021 at 6:39 PM Moritz Muehlenhoff  wrote:
>
> Package: ftp.debian.org
> Severity: normal
> X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org
>
> Please remove offlineimap. It depends on Python and upstream won't port it
> to Python 3. There's however a fork, which has been packaged as 
> src:offlineimap3
> (and removing this obsolete package allows adding a transitional package 
> eventually)

I was asking in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937184#76 if it will
be easier to update offlineimap and mark the binary package as
transitional package instead of removing it and then going via bin-NEW
? If offlineimap is removed and I add it as transitional package in
offlineimap3 then it will need an epoch in the version.


-- 
Regards
Sudip

Bug#979523: FTCBFS due to misuse of build system C compiler

[Bill Allombert]

On Thu, Jan 14, 2021 at 05:33:18PM -0500, John Scott wrote:
> Here's a new patch. It's the same as before, but with sed to modify the 
> config 
> files appropriately. I'd have smashed the sed commands together if not for 
> readability, and for the text alignment being so nice as-is 

Did you compare the pari.cfg files obtained ?

I tried something similar and there was some discrepancies,
in particular with LD and DLLD and modules_build
(modules_build is what gp2c actually uses).

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#970704: tiger: "Don't have required command DIFF" on Linux kernel 5.x

[Javier Fernandez-Sanguino]

Dear Vicent,

Thank you for your bug report

On Tue, 22 Sept 2020 at 08:18, Vincent Danjean  wrote:

>   Hi,
>
>   Using backported kernels in buster, I've been hit by this bug,
> very similar to #785589.
>   The workaround is the same (but the numbers to bump) :
>
>   cd /usr/lib/tiger/systems/Linux/
>   sudo ln -s 4 5
>

This fix was introduced in package version 1:3.2.4~rc1-2, in this package
the  symlink already exists and is created by debian/rules. Actually, there
is a "default" symlink which should make it work regardless of the Linux
kernel version in use:

$  ls -la /usr/lib/tiger/systems/Linux/
total 24
drwxr-xr-x 5 root root 4096 dic 13 22:27 .
drwxr-xr-x 4 root root 4096 ago 19  2019 ..
drwxr-xr-x 3 root root 4096 dic 13 22:27 0
drwxr-xr-x 3 root root 4096 dic 13 22:27 1
drwxr-xr-x 2 root root 4096 dic 13 22:27 2
lrwxrwxrwx 1 root root1 ago 19  2019 3 -> 2
lrwxrwxrwx 1 root root1 ago 19  2019 4 -> 2
lrwxrwxrwx 1 root root1 ago 19  2019 5 -> 2
lrwxrwxrwx 1 root root1 ago 19  2019 default -> 2

You can also fix the issue in your system by creating the default symlink
as shown above.

The tiger package can be easily backported to buster. If this might be of
use I could create a backported version of it fixing this problem.

Best regards

Javier

Bug#980269: Please depend on media-types instead of mime-support

[Charles Plessy]

Package: lighttpd

Dear lighttpd maintainers,

I have recently split the `mime-support` package into two: `mailcap` for
the mailcap system, and `media-types` for providing `/etc/mime.types`.
The goal is to allow minimal systems without `mailcap`.

`mime-support` is now a transitional package, and it would be great if
users could be able to remove it after the _Bookworm_ release.

Please Depend on `media-types` instead of `mime-support` if you only
need the `/etc/mime.types` file.

Have a nice week-end,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Tooting from work,   https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy

Bug#973442: libcjson1: infinite loop in patched cJSON_Minify function

[Boyuan Yang]

Control: fixed -1 1.7.14-1

Please see the stable update request https://bugs.debian.org/980268 .

-- 
Thanks,
Boyuan Yang


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

Bug#980267: qdjango: FTBFS on buildds

[Ivo De Decker]

package: src:qdjango
version: 0.6.2-3
severity: serious
tags: ftbfs

Hi,

The latest upload of qdjango to unstable fails on the buildds:

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

Cheers,

Ivo

Bug#980268: buster-pu: cjson/1.7.10-1.1+deb10u1

[Boyuan Yang]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu


Dear Release Team,

I intend to fix https://bugs.debian.org/973442 in Buster. Under some
circumstances, the user input will cause an infinite loop in libcjson
library. This is a regression introduced by the patch of CVE-2019-11835
and was fixed in cjson/1.7.12. Currently Buster has 1.7.10-1.1. Sid and
Testing has 1.7.14 so Testing/Sid are not affected by this bug.

This upload cherry-picks a commit provided by upstream as well as
corresponding testsuite. The full debdiff is in the attachment.

Thanks and please let me know if you have any questions.

Regards,
Boyuan Yang
diff -Nru cjson-1.7.10/debian/changelog cjson-1.7.10/debian/changelog
--- cjson-1.7.10/debian/changelog	2019-05-14 04:52:20.0 -0400
+++ cjson-1.7.10/debian/changelog	2021-01-16 17:33:31.0 -0500
@@ -1,3 +1,11 @@
+cjson (1.7.10-1.1+deb10u1) buster; urgency=medium
+
+  * Cherry pick upstream commit 08d2bc766a82cd75764d036f9efef444590d1cf9,
+which fixes an infinite loop regression introduced in the previous
+patch. (Closes: #973442)
+
+ -- Boyuan Yang   Sat, 16 Jan 2021 17:33:31 -0500
+
 cjson (1.7.10-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru cjson-1.7.10/debian/patches/08d2bc766a82cd75764d036f9efef444590d1cf9.patch cjson-1.7.10/debian/patches/08d2bc766a82cd75764d036f9efef444590d1cf9.patch
--- cjson-1.7.10/debian/patches/08d2bc766a82cd75764d036f9efef444590d1cf9.patch	1969-12-31 19:00:00.0 -0500
+++ cjson-1.7.10/debian/patches/08d2bc766a82cd75764d036f9efef444590d1cf9.patch	2021-01-16 17:33:24.0 -0500
@@ -0,0 +1,50 @@
+From 08d2bc766a82cd75764d036f9efef444590d1cf9 Mon Sep 17 00:00:00 2001
+From: Max Bruckner 
+Date: Thu, 16 May 2019 20:01:02 +0200
+Subject: [PATCH] Fix infinite loop in cJSON_Minify
+
+Bug-Debian: https://bugs.debian.org/973442
+Applied-Upstream: https://github.com/DaveGamble/cJSON/commit/08d2bc766a82cd75764d036f9efef444590d1cf9
+---
+ cJSON.c  | 2 ++
+ tests/minify_tests.c | 7 +++
+ 2 files changed, 9 insertions(+)
+
+diff --git a/cJSON.c b/cJSON.c
+index 3a5dc547..f9c2ffa5 100644
+--- a/cJSON.c
 b/cJSON.c
+@@ -2717,6 +2717,8 @@ CJSON_PUBLIC(void) cJSON_Minify(char *json)
+ else if (json[1] == '*')
+ {
+ skip_multiline_comment();
++} else {
++json++;
+ }
+ break;
+ 
+diff --git a/tests/minify_tests.c b/tests/minify_tests.c
+index e39a9446..000821db 100644
+--- a/tests/minify_tests.c
 b/tests/minify_tests.c
+@@ -152,6 +152,12 @@ static void cjson_minify_should_minify_json(void) {
+ free(buffer);
+ }
+ 
++static void cjson_minify_should_not_loop_infinitely(void) {
++char string[] = { '8', ' ', '/', ' ', '5', '\n', '\0' };
++/* this should not be an infinite loop */
++cJSON_Minify(string);
++}
++
+ int CJSON_CDECL main(void)
+ {
+ UNITY_BEGIN();
+@@ -162,6 +168,7 @@ int CJSON_CDECL main(void)
+ RUN_TEST(cjson_minify_should_remove_multiline_comments);
+ RUN_TEST(cjson_minify_should_remove_spaces);
+ RUN_TEST(cjson_minify_should_not_modify_strings);
++RUN_TEST(cjson_minify_should_not_loop_infinitely);
+ 
+ return UNITY_END();
+ }
diff -Nru cjson-1.7.10/debian/patches/series cjson-1.7.10/debian/patches/series
--- cjson-1.7.10/debian/patches/series	2019-05-14 04:52:20.0 -0400
+++ cjson-1.7.10/debian/patches/series	2021-01-16 17:32:41.0 -0500
@@ -1 +1,2 @@
 0001-PATCH-Rewrite-cJSON_Minify-fixing-buffer-overflows-f.patch
+08d2bc766a82cd75764d036f9efef444590d1cf9.patch


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

Bug#951948: Fixed upstream

[Sam Geeraerts]

This is due to improper use of setuptools_scm in docs/conf.py. This is
fixed [1] in version 0.16.8, along with other build errors. Please
consider packaging the new version.

[1]
https://github.com/pimutils/vdirsyncer/commit/b1214cd693d7a6c6693da3d070e8b9965a84a88e

Bug#980266: RFS: duperemove/0.11.2-1 -- extent-based deduplicator for file systems

[Peter Zahradnik]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name : duperemove
Version : 0.11.2-1
Upstream Author : Mark Fasheh 
* URL : https://markfasheh.github.io/duperemove/
* License : GPL-2+, GPL-2, Expat, BSD-2-Clause
* Vcs : https://salsa.debian.org/petzah/duperemove
Section : admin

It builds those binary packages:

duperemove - extent-based deduplicator for file systems

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


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

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

dget -x 
https://mentors.debian.net/debian/pool/main/d/duperemove/duperemove_0.11.2-1.dsc


Changes since the last upload:

duperemove (0.11.2-1) unstable; urgency=medium
.
* Bump version
* Update compat, debhelper, standards, copyright
* Drop patches which were included in upstream/kernel

Regards,
Peter Zahradnik

Bug#979174: node-express-generator: Incompatible with current node-commander and node-mkdirp

[Ivo De Decker]

Control: tags -1 + bullseye

Hi,

On Sun, Jan 03, 2021 at 09:39:56PM +0100, Xavier Guimard wrote:
> Package: node-express-generator
> Version: 4.0.0-2
> Severity: grave
> Tags: sid, ftbfs

Tagging bugs only 'sid' and not the tag for testing usually doesn't give the
correct result. Adding the bullseye tag as well.

Did you add the ftbfs tag by mistake? I don't see an ftbfs anywhere.

> Justification: renders package unusable
> 
> node-express-generator isn't compatible with current node-commander,
> neither node-mkdirp. As it has no reverse dependency, I suggest to
> remove it from Debian

If you want the package removed, you should probably file an FTP removal bug.

Cheers,

Ivo

Bug#980252: ovs interfaces from /etc/network/interfaces not configured at boot

[Pim van den Berg]

Package: openvswitch-switch
Version: 2.15.0~git20210104.def6eb1ea+dfsg1-3

Hi Thomas Goirand,

Since 2.15.0~git20210104.def6eb1ea+dfsg1-3 ovs interfaces from 
/etc/network/interfaces are not configured at boot time anymore.


My /etc/network/interfaces file looks like the example from 
README.Debian:


allow-ovs br0
iface br0 inet dhcp
ovs_type OVSBridge
ovs_ports eth0

allow-br0 eth0
iface eth0 inet manual
ovs_bridge br0
ovs_type OVSPort

After downgrading to 2.15.0~git20210104.def6eb1ea+dfsg1-2 it worked 
again.


Similar bug report: https://bugs.debian.org/910297

Bug#980251: New upstream version utalk 1.0.2

[johnlee476]

Package: utalk
Version: 1.0.1.beta-9

Hello, there is a new upstream version utalk 1.0.2 in 
http://utalk.ourproject.org.

Changelog:

* utalk 1.0.2

- Add insert text in the middle of a line (in addition to default overwrite)
- Add default additional key bindings for ins, del, home, end, pg up, pg down
- Add make uninstall
- Fix some problems redrawing the screen after a delete or backspace operation
- Fix terminal resize functionality on modern Linux
- Fix build issues with gcc 10


-- 
 Sent with Tutanota, the secure & ad-free mailbox: 
 https://tutanota.com

Bug#968574: ffmpeg: Please backport upstream patch to fix build on powerpc and ppc64

[John Paul Adrian Glaubitz]

Hi!

On 8/17/20 10:56 PM, John Paul Adrian Glaubitz wrote:
> ffmpeg currently FTBFS on powerpc and ppc64 [1]:
> (...)
> Upstream has a patch for that, see [2]. Could you backport that patch?

The bug is unfortunately still present and the package still fails to build from
source on Debian powerpc [1] and ppc64 [2].

I think this patch is trivial enough that it can be included without any further
testing besides the testing on Debian powerpc and ppc64, where I have verified
the patch to fix the problem.

Could the patch be included with the next package revision?

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=ffmpeg=powerpc=7%3A4.3.1-6=1610485996=0
> [2] 
> https://buildd.debian.org/status/fetch.php?pkg=ffmpeg=ppc64=7%3A4.3.1-6=1610485440=0

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#980265: prosody has unsatisfiable cross Build-Depends

[Helmut Grohne]

Source: prosody
Version: 0.11.7-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability

prosody cannot be cross built from source, because its Build-Depends are
not satisfiable. Instead of looking into this difficult problem, I
looked into which dependencies would be easily droppable. It turns out
that lua-busted, lua5.2* and openssl are only used for running
build-time tests. Such tests are usually disabled during cross building,
so we can mask out the relevant dependencies via . Please
consider applying the attached patch. A thus tagged nocheck build
reproduces the same binary artifacts as a regular full build on amd64
here.

Helmut
diff --minimal -Nru prosody-0.11.7/debian/changelog 
prosody-0.11.7/debian/changelog
--- prosody-0.11.7/debian/changelog 2020-10-02 11:37:42.0 +0200
+++ prosody-0.11.7/debian/changelog 2021-01-16 23:05:55.0 +0100
@@ -1,3 +1,10 @@
+prosody (0.11.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Annotate test dependencies with . (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 16 Jan 2021 23:05:55 +0100
+
 prosody (0.11.7-1) unstable; urgency=medium
 
   * New upstream version 0.11.7
diff --minimal -Nru prosody-0.11.7/debian/control prosody-0.11.7/debian/control
--- prosody-0.11.7/debian/control   2020-10-02 11:37:42.0 +0200
+++ prosody-0.11.7/debian/control   2021-01-16 23:05:47.0 +0100
@@ -13,11 +13,11 @@
  libidn11-dev,
  liblua5.2-dev,
  libssl-dev,
- lua-busted,
- lua5.2,
- lua5.2-expat,
- lua5.2-socket,
- openssl,
+ lua-busted ,
+ lua5.2 ,
+ lua5.2-expat ,
+ lua5.2-socket ,
+ openssl ,
  txt2man,
 Standards-Version: 4.5.0
 Homepage: http://www.prosody.im/

Bug#980264: kwindowsystem: reduce Build-Depends

[Helmut Grohne]

Source: kwindowsystem
Version: 5.78.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

kwindowsystem participates in a small dependency graph of packages
relevant to bootstrap. Instead of analyzing the mess, I looked into
easily droppable Build-Depends and kwindowsystem has two:

 * graphviz is entirely unused. I suppose that it was a support
   dependency for doxygen.
 * libxcb-icccm4-dev is only used for a testcase. It can be annotated
   , which makes it irrelevant to bootstrapping.

Please consider applying the attached patch.

Helmut
diff --minimal -Nru kwindowsystem-5.78.0/debian/changelog 
kwindowsystem-5.78.0/debian/changelog
--- kwindowsystem-5.78.0/debian/changelog   2021-01-13 02:32:44.0 
+0100
+++ kwindowsystem-5.78.0/debian/changelog   2021-01-16 22:52:28.0 
+0100
@@ -1,3 +1,13 @@
+kwindowsystem (5.78.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Reduce Build-Depends: (Closes: #-1)
++ Drop unused graphviz.
++ Annotate libxcb-icccm4-dev  as it is only used in
+  autotests/kwindowinfox11test.cpp.
+
+ -- Helmut Grohne   Sat, 16 Jan 2021 22:52:28 +0100
+
 kwindowsystem (5.78.0-1) experimental; urgency=medium
 
   [ Norbert Preining ]
diff --minimal -Nru kwindowsystem-5.78.0/debian/control 
kwindowsystem-5.78.0/debian/control
--- kwindowsystem-5.78.0/debian/control 2021-01-11 14:56:43.0 +0100
+++ kwindowsystem-5.78.0/debian/control 2021-01-16 22:52:20.0 +0100
@@ -8,11 +8,10 @@
debhelper-compat (= 13),
doxygen,
extra-cmake-modules (>= 5.78.0~),
-   graphviz,
libqt5sql5-sqlite:native,
libqt5x11extras5-dev (>= 5.14.0~),
libx11-dev,
-   libxcb-icccm4-dev,
+   libxcb-icccm4-dev ,
libxcb-keysyms1-dev,
libxcb-res0-dev,
libxcb-xfixes0-dev,

Bug#980164: firmware-amd-graphics: amd rx 6800 compatibility

[Nicholas D Steeves]

Hi,

alain  writes:

> Package: firmware-amd-graphics
> Version: 20201118-1
> Followup-For: Bug #980164
> X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
>
> here is my last try .
>
> installed firmware-amd-graphics 20201118-1 (testing)
> copied sienna_cichlid* from git .
>
> nothing .

RX6800 support requires firmware-amd-graphics newer than 20201118-1 (sid
has 20201218-1).

> black screen with the irq's scanning in front of it .
>
> the only way to come in debian is to pass the "nomodeset=1" to the grub 
> (letter
> "e" at grub boot time)
>
> firmwares are wrong .
> testing and sid .
>
> could you help me , please ?
>

The BTS isn't a user support forum (see https://www.debian.org/support),
and

> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (100, 'unstable'), (100, 'stable'), (1, 
> 'experimental')

mixing distributions like this can result in an "if it breaks, you get
to keep the pieces and debug it on your own" scenario.

The graphics stack is made of up of packages from linux-source,
firmware, llvm-toolchain, mesa, and now the new vulkan stuff.  When
mixing distributions, it is the user's responsibility to ensure that the
mix of packages installed to the system doesn't result in a random and
broken state of incompatible versions.

  https://wiki.debian.org/DontBreakDebian

With a supported distribution, test for GPU success, then if it doesn't
work, shutdown, reboot with ctrl+alt+del, add "nomodeset=1" to the
kernel cmdline, as root run "journalctl -k --boot=-1 | xz >
boot.log.xz", and attach that log to this bug.

If you're accessing the system using ssh, "journalctl -k | xz >
boot.log.xz" without a reboot, and send that log to this bug.

For this bug to be actionable, you'll need to make it reproducible on a
supported distribution.  This means using only bullseye/testing (testing
doesn't have new enough firmware-amd-graphics), or using unstable/sid.
Please take care to manually downgrade any packages installed from
experimental to their version in sid; however, note that package
downgrades are also not supported...

An easier option may be to create a minimal unstable/sid installation on
a USB stick, ensure firmware-amd-graphics 20201218-1 is installed, boot
from that, and test for a functional Linux framebuffer (with modesetting)
console, and provide logs to this bug report if this simple test fails.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#942853: ITP: python-mitogen - Python library for writing distributed self-replicating programs

[Stefano Rivera]

Hi Emmanuel (2020.10.26_11:37:19_-0700)
> > > I created this salsa repo
> > > https://salsa.debian.org/python-team/packages/python-mitogen
> >
> > Are you okay if I start pushing changes there directly? I'll ping you
> >
> yes of course start pushing :D
> 
> I'm in IRC as eamanu

Pushed some packaging.

Listed everyone who expressed interest in this thread as Uploaders.

Notable bits of my packaging:

1. I broke the package into two binary packages: python3-mitogen and
   ansible-mitogen.
2. Symlinked the strategies into ansible.plugins.strategies, so that no
   configuration is required to make them available.
3. Removed the (Python 2.4 compatibility) vendored simplejson module. It
   can't be parsed python 3.9, which breaks tooling in a couple of
   places. Simpler to remove it.

I'll upload this to NEW, shortly.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#977819: licenseutils FTCBFS: uses the build architecture pkg-config

[Mattia Rizzolo]

On Mon, Dec 21, 2020 at 12:47:05PM +0100, Helmut Grohne wrote:
> licenseutils fails to cross build from source, because the configure
> script detects the build architecture pkg-config. Please use the
> standard macro PKG_PROG_PKG_CONFIG (which is already implicitly used via
> PKG_CHECK_MODULES) as it will find the correct pkg-config. I'm attaching
> a patch for this.

I've applied the patch and also forwarded upstream.
Though upstream seems to have lost interest so I don't expect much at
this point.

> Beyond this, licenseutils uses help2man and - since it knows that doing
> so breaks cross compilation - it skips generating manual pages.
> Unfortunately, installing the absent pages fails. There are many
> solutions to this problem all with their own disadvantages:
>  * Stop using help2man and write real manual pages.
>  * The package can be built twice (once for build and once for host),
>but the dependencies of licenseutils seem to complex to allow this.
>  * Split manual pages to an Architecture: all package (though this
>violates a policy should).
>  * Generate manual pages on the upstream side and skip regenerating them
>during build.

I prefer the last option here, but I don't plan on implementing it at
this time; I'm writing this here as future doc (if anybody will ever
discover this bug).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#980263: taskwarrior: Filtering for project-names containing hyphen and number stopped working

[Nicola Chiapolini]

Package: taskwarrior
Version: 2.5.3+dfsg-1
Severity: important

Dear Maintainer,

I use taskwarrior since several years and have a large number of
projects. One common pattern looks like 'c.vs.2021-01'. After updating
from 2.5.1+dfsg-11 to 2.5.3+dfsg-1, searches for such projects (`task
project:c.vs.2021-01`) fail with error 'Cannot subtract strings'.

Downgrading fixes the problem.


Thanks for all the work. Let me know if I should report this upstream or can 
support in any other way.

best regards
Nicola


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

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

Versions of packages taskwarrior depends on:
ii  libc62.31-9
ii  libgcc-s110.2.1-3
ii  libgnutls30  3.7.0-5
ii  libstdc++6   10.2.1-3
ii  libuuid1 2.36.1-4

taskwarrior recommends no packages.

taskwarrior suggests no packages.

-- no debconf information

Bug#980119: libgnutls30: "An unexpected TLS packet was received" when connecting to FTPS (FTP/TLS) servers

[Boyd Stephen Smith Jr.]

On Saturday, January 16, 2021 2:26:52 PM CST Boyd Stephen Smith Jr. wrote:
> On Saturday, January 16, 2021 6:35:13 AM CST Andreas Metzler wrote:
> > Does
> > env GNUTLS_DEBUG_LEVEL=4711 lftp 
> > produce more verbose output?
> 
> Yes.  But, probably not verbose enough:

I don't know about GNU TLS, but I got lftp to tell me more about what it is 
doing:
---8<---
% env GNUTLS_DEBUG_LEVEL=4711 lftp -e 'set cmd:trace yes' -e 'set log:enabled 
true' -u boyd.stephen.smith...@gmail.com.125388 bos-sr-2-36.akliz.net
gnutls[2]: Enabled GnuTLS 3.7.0 logging...
gnutls[2]: getrandom random generator was detected
gnutls[2]: Intel SSSE3 was detected
gnutls[2]: Intel SHA was detected
gnutls[2]: Intel AES accelerator was detected
gnutls[2]: Intel GCM accelerator (AVX) was detected
gnutls[2]: cfg: unable to access: /etc/gnutls/config: 2
Password: 
lftp boyd.stephen.smith...@gmail.com.125...@bos-sr-2-36.akliz.net:~> ls
 Connecting to bos-sr-2-36.akliz.net (8.48.33.7) port 21
<--- 220 (vsFTPd 2.2.2)
---> FEAT
<--- 211-Features:   
<---  AUTH SSL
<---  AUTH TLS
<---  EPRT
<---  EPSV
<---  MDTM
<---  PASV
<---  PBSZ
<---  PROT
<---  REST STREAM
<---  SIZE   
<---  TVFS
<---  UTF8
<--- 211 End
---> AUTH TLS
<--- 234 Proceed with negotiation.
---> OPTS UTF8 ON
Certificate: CN=bos-sr-2-36.akliz.net
 Issued by:C=US,O=Let's Encrypt,CN=R3
 Checking against: C=US,O=Let's Encrypt,CN=R3
  Trusted
Certificate: C=US,O=Let's Encrypt,CN=R3
 Issued by: O=Digital Signature Trust Co.,CN=DST Root CA X3
  Trusted
<--- 200 Always in UTF8 mode.
---> USER boyd.stephen.smith...@gmail.com.125388
<--- 331 Please specify the password.
---> PASS 
<--- 230 Login successful.   
---> PWD
<--- 257 "/" 
---> PBSZ 0
<--- 200 PBSZ set to 0.  
---> PROT P
<--- 200 PROT now Private.   
---> PASV
<--- 227 Entering Passive Mode (8,48,33,7,4,186).
 Connecting data socket to (8.48.33.7) port 1210
 Data connection established   
---> LIST
<--- 150 Here comes the directory listing.
 gnutls_handshake: An unexpected TLS packet was received.
 Closing data socket
 gnutls_record_recv: An unexpected TLS packet was received.
 Closing control socket
ls: Fatal error: gnutls_record_recv: An unexpected TLS packet was received.
lftp boyd.stephen.smith...@gmail.com.125...@bos-sr-2-36.akliz.net:/> bye
--->8---

-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#980119: libgnutls30: "An unexpected TLS packet was received" when connecting to FTPS (FTP/TLS) servers

[Boyd Stephen Smith Jr.]

On Saturday, January 16, 2021 6:35:13 AM CST Andreas Metzler wrote:
> Does
> env GNUTLS_DEBUG_LEVEL=4711 lftp 
> produce more verbose output?

Yes.  But, probably not verbose enough:
---8<---
% env GNUTLS_DEBUG_LEVEL=4711 lftp -u boyd.stephen.smith...@gmail.com.125388 
bos-sr-2-36.akliz.net
gnutls[2]: Enabled GnuTLS 3.7.0 logging...
gnutls[2]: getrandom random generator was detected
gnutls[2]: Intel SSSE3 was detected
gnutls[2]: Intel SHA was detected
gnutls[2]: Intel AES accelerator was detected
gnutls[2]: Intel GCM accelerator (AVX) was detected
gnutls[2]: cfg: unable to access: /etc/gnutls/config: 2
Password: 
lftp boyd.stephen.smith...@gmail.com.125...@bos-sr-2-36.akliz.net:~> ls
ls: Fatal error: gnutls_record_recv: An unexpected TLS packet was received.
--->8---

-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#980119: libgnutls30: "An unexpected TLS packet was received" when connecting to FTPS (FTP/TLS) servers

[Boyd Stephen Smith Jr.]

On Friday, January 15, 2021 12:02:35 PM CST Andreas Metzler wrote:
> Is this reproducible with gnutls-cli?
> 
> -
> gnutls-cli  --starttls-proto=ftp bos-sr-2-36.akliz.net
> ...
> USER _loginhere_
> PASS _passwordhere_
> PWD
> -

That works:

---8<---
% gnutls-cli  --starttls-proto=ftp bos-sr-2-36.akliz.net
Processed 126 CA certificate(s).
Resolving 'bos-sr-2-36.akliz.net:ftp'...
Connecting to '8.48.33.7:21'...
- Certificate type: X.509
- Got a certificate list of 2 certificates.
- Certificate[0] info:
 - subject `CN=bos-sr-2-36.akliz.net', issuer `CN=R3,O=Let's Encrypt,C=US', 
serial 0x03f0eed09043a9a3dbf803d708af1c69e2cb, RSA key 2048 bits, signed using 
RSA-SHA256, activated `2020-12-03 23:00:42 UTC', expires `2021-03-03 23:00:42 
UTC', pin-sha256="69VuNIHD0lVaLOn9/cadykjHGtIcENyTp7HOQC+ppts="
Public Key ID:
sha1:aaf17878dc41169ab8998a5244753fb5440fb852

sha256:ebd56e3481c3d2555a2ce9fdfdc69dca48c71ad21c10dc93a7b1ce402fa9a6db
Public Key PIN:
pin-sha256:69VuNIHD0lVaLOn9/cadykjHGtIcENyTp7HOQC+ppts=

- Certificate[1] info:
 - subject `CN=R3,O=Let's Encrypt,C=US', issuer `CN=DST Root CA X3,O=Digital 
Signature Trust Co.', serial 0x400175048314a4c8218c84a90c16cddf, RSA key 2048 
bits, signed using RSA-SHA256, activated `2020-10-07 19:21:40 UTC', expires 
`2021-09-29 19:21:40 UTC', pin-
sha256="jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0="
- Status: The certificate is trusted. 
- Successfully sent 0 certificate(s) to server.
- Description: (TLS1.0-X.509)-(ECDHE-SECP256R1)-(AES-128-CBC)-(SHA1)
- Session ID: 78:CC:6C:F1:66:01:CA:0C:7A:4E:FC:FF:DA:04:59:30:44:7C:
81:B7:59:44:6D:44:71:56:72:62:EA:DA:0E:41
- Options: safe renegotiation,
- Handshake was completed

- Simple Client Mode:

USER boyd.stephen.smith...@gmail.com.125388
331 Please specify the password.
PASS R7Pr6Uq6RC4N7we!
230 Login successful.
PWD
257 "/"
--->8---

But, I clearly don't know enough about raw FTP protocol to get a data transfer 
started:
---8<---
LIST
425 Use PORT or PASV first.
PASV
227 Entering Passive Mode (8,48,33,7,4,208).
LIST
522 Data connections must be encrypted.
HELP
214-The following commands are recognized.
 ABOR ACCT ALLO APPE CDUP CWD  DELE EPRT EPSV FEAT HELP LIST MDTM MKD
 MODE NLST NOOP OPTS PASS PASV PORT PWD  QUIT REIN REST RETR RMD  RNFR
 RNTO SITE SIZE SMNT STAT STOR STOU STRU SYST TYPE USER XCUP XCWD XMKD
 XPWD XRMD
214 Help OK.
HELP PORT
214-The following commands are recognized.
 ABOR ACCT ALLO APPE CDUP CWD  DELE EPRT EPSV FEAT HELP LIST MDTM MKD
 MODE NLST NOOP OPTS PASS PASV PORT PWD  QUIT REIN REST RETR RMD  RNFR
 RNTO SITE SIZE SMNT STAT STOR STOU STRU SYST TYPE USER XCUP XCWD XMKD
 XPWD XRMD
214 Help OK.
CWD /custom-minecraft
250 Directory successfully changed.
NLST
522 Data connections must be encrypted.
PORT
500 Illegal PORT command.
--->8---

Note that connection in both FileZilla and lftp only fails once I try to list 
the contents of the current directory.  They are port able to connect and 
login as well.

-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#980119: libgnutls30: "An unexpected TLS packet was received" when connecting to FTPS (FTP/TLS) servers

[Boyd Stephen Smith Jr.]

On Saturday, January 16, 2021 2:23:43 PM CST Boyd Stephen Smith Jr. wrote:
> On Friday, January 15, 2021 12:02:35 PM CST Andreas Metzler wrote:
> > Is this reproducible with gnutls-cli?
> 
> That works:
> 
> But, I clearly don't know enough about raw FTP protocol to get a data
> transfer started:
> 
> Note that connection in both FileZilla and lftp only fails once I try to
> list the contents of the current directory.  They are port able to connect
> and login as well.

I tried again, but I'm betting gnutls-cli doesn't handle the weirdness that is 
FTP well.  I'm going to try to do a passive transfer, because I'm behind at 
least one NAT, so I don't think active transfer is going to work:

It starts as before with the certificate, and me logging in:

---8<---
230 Login successful.
PBSZ 0
200 PBSZ set to 0.
PROT P
200 PROT now Private.
PASV
227 Entering Passive Mode (8,48,33,7,5,1).
LIST
---8<---

Here the connect appears to hang for too long, and I end up sending some more 
commands before the LIST command ends

---8<---

HELP
PWD
425 Failed to establish connection.
214-The following commands are recognized.
 ABOR ACCT ALLO APPE CDUP CWD  DELE EPRT EPSV FEAT HELP LIST MDTM MKD
 MODE NLST NOOP OPTS PASS PASV PORT PWD  QUIT REIN REST RETR RMD  RNFR
 RNTO SITE SIZE SMNT STAT STOR STOU STRU SYST TYPE USER XCUP XCWD XMKD
 XPWD XRMD
214 Help OK.
257 "/"
PASV
227 Entering Passive Mode (8,48,33,7,4,225).
LIST 
425 Failed to establish connection.
--->8---

For that last LIST, I simply waited calmly until I got the result.

(The password I sent in plaintext earlier is no longer valid, BTW.)

If you think PASV is the issue, I should be able to retry from a system that's 
not NAT'd or otherwise configure the network for a PORT connection.  But, I 
don't know GNU TLS is going to handle that any better.  Let me know if it is 
worth an attempt.

If you've got some hints on how to use gnutls-cli for a PASV transfer, I'll 
gladly take them.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#980262: Please add bash-completion to default Debian installs

[Y]

Package: bash-completion
Version: 1:2.11-2
Severity: wishlist
X-Debbugs-Cc: laks...@hotmaol.com

Dear Maintainer,


   * What led up to the situation?
Couldn't autocomplete commands like "apt install na"
   * What was the outcome of this action?
No autocompletion
   * What outcome did you expect instead?
Being able to autocomplete commands in Debian

bash-completion is a useful tool that should be installed by default in Debian, 
please include it in the next releases. Thank you.


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

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

-- no debconf information

Bug#980261: RFS: jgmenu/4.3.0-1 [RFP] -- Simple X11 menu

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: jgmenu
   Version : 4.3.0-1
   Upstream Author : Johan Malm 
 * URL : https://jgmenu.github.io/
 * License : LGPL-2+, GPL-2+, Expat, LGPL-3+
 * Vcs : https://github.com/mati75/jgmenu
   Section : x11

It builds those binary packages:

  jgmenu-xfce4-panel-applet - xfce4-panel applet for jgmenu
  jgmenu - Simple X11 menu

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/j/jgmenu/jgmenu_4.3.0-1.dsc

Changes for the initial release:

 jgmenu (4.3.0-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #882210)

Regards,
--
  Mateusz Łukasik

Bug#980260: RFS: openbox-menu/0.8.0+hg20161009-3 -- openbox pipe-menu to display entries in *.desktop files

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "openbox-menu":

 * Package name: openbox-menu
   Version : 0.8.0+hg20161009-3
   Upstream Author : [fill in name and email of upstream]
 * URL : https://bitbucket.org/fabriceT/openbox-menu
 * License : GPL-3+
 * Vcs : https://github.com/mati75/openbox-menu.git
   Section : x11

It builds those binary packages:

  openbox-menu - openbox pipe-menu to display entries in *.desktop files

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

  https://mentors.debian.net/package/openbox-menu/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/openbox-menu/openbox-menu_0.8.0+hg20161009-3.dsc

Changes since the last upload:

 openbox-menu (0.8.0+hg20161009-3) unstable; urgency=medium
 .
   * Fix test running.

Regards,
--
  Mateusz Łukasik

Bug#980259: buster-pu: package cyrus-imapd/3.0.8-6+deb10u5

[Xavier Guimard]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
The /etc/cron.daily/cyrus-imapd cron script is not executed because the
Cyrus version check does not match the cyrus version installed on Debian
Buster

[ Impact ]
Dala loss risk

[ Tests ]
No test added

[ Risks ]
Trivial patch

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable (see #935431)

[ Changes ]
Regex fix

Cheers,
Xavier
diff --git a/debian/changelog b/debian/changelog
index c96adf9c..240d1f4d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cyrus-imapd (3.0.8-6+deb10u5) buster; urgency=medium
+
+  * Fix cron script (Closes: #980240)
+
+ -- Xavier Guimard   Sat, 16 Jan 2021 21:34:16 +0100
+
 cyrus-imapd (3.0.8-6+deb10u4) buster; urgency=medium
 
   * Add BACKUP type to cyrus-upgrade-db (Closes: #930764)
diff --git a/debian/cyrus-common.cyrus-imapd.cron.daily 
b/debian/cyrus-common.cyrus-imapd.cron.daily
index eca5ffe5..c92eca15 100644
--- a/debian/cyrus-common.cyrus-imapd.cron.daily
+++ b/debian/cyrus-common.cyrus-imapd.cron.daily
@@ -33,7 +33,7 @@ umask 022
 && [ -f /usr/lib/cyrus/cyrus-hardwired-config.txt ] \
 || exit 0
 # Check if Cyrus is installed (vs. removed but not purged)
-grep -qE '^PACKAGE_VERSION[[:blank:]]+[30][.][245]' \
+grep -qE '^PACKAGE_VERSION[[:blank:]]+3.0[.][2458]' \
/usr/lib/cyrus/cyrus-hardwired-config.txt >/dev/null 2>&1 || exit 0
 
 # 1. backup mailbox database

Bug#980258: ruby-rugged: tries to contact github.com during build (and fails)

[Paul Gevers]

Source: ruby-rugged
Version: 1.1.0+ds-2
Severity: serious
Tags: ftbfs

Dear maintainer,

I just noticed that ruby-rugged FTBFS on arm64 because it "failed to
connect to github.com:".

This is a violation of the Debian policy 4.9 [1]:
"""
For packages in the main archive, no required targets may attempt
network access, except, via the loopback interface, to services on the
build host that have been started by the build.
"""

Paul

[1]
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules



OpenPGP_signature
Description: OpenPGP digital signature

Bug#980257: puppet-module-puppetlabs-mysql: autopkgtest regression in testing: Service "mysql" is expected to be enabled

[Paul Gevers]

Source: puppet-module-puppetlabs-mysql
Version: 8.1.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change somewhere outside of your package (I suspect in
mariadb-server) the autopkgtest of your package started to fail. I
copied some of the output at the bottom of this report. Can you please
investigate the situation and fix it?

I'm wondering. Is this puppet-module installing mariadb "under water"?
In a way then the package (or at least the test) sort of depends on
mariadb. I understand you'd not want the test to depend on it because
then it is already installed, but you can at least make sure that your
test is run when mariadb gets updated, if you add a "dummy" test with
the dependency on it. Please refer to the autopkgtest specification [1]
under the hint-testsuite-triggers restriction.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1]
https://salsa.debian.org/ci-team/autopkgtest/-/raw/master/doc/README.package-tests.rst

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet-module-puppetlabs-mysql/951/log.gz

autopkgtest [22:19:50]: test command1: [---

Package "puppet-module-puppetlabs-mysql"
  is expected to be installed

Command "puppet apply --detailed-exitcodes --execute "include
mysql::client""
  exit_status
is expected to eq 2

Package "mariadb-client"
  is expected to be installed

Command "puppet apply --detailed-exitcodes --execute "include
mysql::server""
  exit_status
is expected to eq 2

Package "mariadb-server"
  is expected to be installed

Service "mysql"
  is expected to be enabled (FAILED - 1)
  is expected to be running

Failures:

  1) Service "mysql" is expected to be enabled
 Failure/Error: it { should be_enabled }
   expected Service "mysql" to be enabled
   /bin/sh -c ls\ /etc/rc3.d/\ \|\ grep\ --\ \'\^S..mysql\$\'\ \|\|\
grep\ \'\^\ \*start\ on\'\ /etc/init/mysql.conf

 # ./spec/localhost/use_spec.rb:20:in `block (2 levels) in '

Finished in 14.27 seconds (files took 0.34764 seconds to load)
7 examples, 1 failure

Failed examples:

rspec ./spec/localhost/use_spec.rb:20 # Service "mysql" is expected to
be enabled

autopkgtest [22:20:05]: test command1: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#980111: pam breaks frr autopkgtest on armhf and ppc64el: non-zero exit status 1

[Ivo De Decker]

Control: reassign -1 frr/7.4-1

Hi,

On Thu, Jan 14, 2021 at 05:00:26PM +0100, Paul Gevers wrote:
> With a recent upload of pam the autopkgtest of frr fails in testing on
> armhf and ppc64el when that autopkgtest is run with the binary packages
> of pam from unstable. It passes when run with only packages from
> testing. In tabular form:
> 
>passfail
> pamfrom testing1.4.0-2
> frrfrom testing7.4-1
> all others from testingfrom testing

> autopkgtest [11:36:52]: test py-frr-reload: [---

Paul gave me access to a machine similart to the one that's running the test
on armhf. It looks like it's a race condition in the test itself (or in the
frr scripts):

The test runs 
  service frr reload
and then runs
  vtysh -c 'show running-config'
to check if the output is changed. With the new pam, this command still shows
the old config immediately after the reload. A few seconds later, it shows the
new config. I suspect the changes in pam affect the timing of some of the
steps involved.

As it looks like this is an issue in the frr test (or the frr package), I'm
reassigning the bugs there.

Cheers,

Ivo

Bug#976811: transition: php8.0

[Salvatore Bonaccorso]

Hi,

On Fri, Jan 15, 2021 at 07:58:10PM +0100, Ondřej Surý wrote:
> Thinking about it, security-wise it might be better. Microsoft will
> support the security backports to EOL versions of PHP 7.x, but they
> announced they won’t do it for PHP 8.x, so we are (maybe) bit more
> covered with PHP 7.4.

Ok, sounds good then.

Btw, we are currently at 7.4.11-1 in unstable, while at least updating
up to 7.4.14 would fix as well CVE-2020-7071.

If nothing speaks against it, it would be good to start bullseye with
a version most near with upstream stable released version (we would
otherwise anyway need to otherwise rebase to the next 7.4.y version in
the first DSA for php7.4).

Are you planning to update to 7.4.14 (or later) before the soft
freeze?

Regards,
Salvatore

Bug#980256: git-buildpackage: autopkgtest armhf regression: /usr/bin/python: not found

[Paul Gevers]

Source: git-buildpackage
Version: 0.9.21
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of git-buildpackage the autopkgtest of
git-buildpackage fails in testing on armhf when that autopkgtest is run
with the binary packages of git-buildpackage from unstable. It passes
when run with only packages from testing. In tabular form:

   passfail
git-buildpackage   from testing0.9.21
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
git-buildpackage/0.9.21. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=git-buildpackage

https://ci.debian.net/data/autopkgtest/testing/armhf/g/git-buildpackage/9735149/log.gz

+ python3 -c import setuptools
+ mktemp -d
+ GBP_TEMPDIR=/tmp/tmp.thAvJcvD7A
+ gbp buildpackage-rpm --git-packaging-dir=packaging/
--git-export-dir=/tmp/tmp.thAvJcvD7A -D%__python3 /usr/bin/python3
-D%__python /usr/bin/python3 -bb --nodeps
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found
sh: 1: /usr/bin/python: not found

Bug#980203: linux-image-5.10.0-1-686:i386 ipw2200 returns bogus MAC address. Security implications????

[Charles Curley]

On Sat, 16 Jan 2021 09:19:45 +0100
Bastian Blank  wrote:

> On Fri, Jan 15, 2021 at 05:55:47PM -0700, Charles Curley wrote:
> > On boot, NetworkManager does its thing correctly, and gets the
> > machine on the network. However, I use DHCP with fixed addresses.
> > Getting the wrong MAC address throws this off, which is how the
> > problem came to my attention. This is an intermittent problem. Not
> > every boot results in the wrong MAC address.  
> 
> NetworkManager can change MAC addresses for privacy reasons.  Did you
> disable this feature?

I was completely unaware of it until you mentioned it.

The man page for NetworkManager.conf says, in part:

   wifi.mac-address-randomization

   If left unspecified, MAC address randomization is disabled.
   This setting is deprecated for wifi.cloned-mac-address.

So if I read that correctly, one must affirmatively enable it.

A search of the various NetworkManager.conf files did not turn up any
use of that keyword. Nor did a check of the connection-specific file.

root@dragon:~# locate NetworkManager | grep conf$ | xargs grep -i rand
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:wifi.scan-rand-mac-address=no
root@dragon:~# locate NetworkManager | grep conf.d | xargs ls
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf

/crc/dragon/etc/NetworkManager/conf.d:

/etc/NetworkManager/conf.d:

/usr/lib/NetworkManager/conf.d:
no-mac-addr-change.conf
root@dragon:~# 

A search of the GTK GUI did not turn up any settings for it.

So, as far as I know, the answer to your question is that it is not
currently enabled.

> 
> > Jan 15 16:15:45 dragon kernel: [278773.780936] wlp2s2: Setting MAC
> > to 8a:f5:74:20:7c:9e  
> 
> So something _deliberately_ sets a local administered MAC address.

Maybe. But what? I don't see anything in /etc/modprobe.d/, modules, or
modules-load.d/.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Bug#966524: lvm2: "lvconvert --merge" does not remove the snapshot fter completing

[Antonio]

Dear maintenance,
to remember that this problem still exists (and is necessary restart the 
system, after the snapshot revert process has completed)


Thanks
Antonio

Bug#976448: bitcoin: CVE-2020-14198

[Salvatore Bonaccorso]

Hi Petter,

On Sat, Jan 16, 2021 at 08:18:53PM +0100, Petter Reinholdtsen wrote:
> [Salvatore Bonaccorso]
> > The following vulnerability was published for bitcoin.
> > 
> > CVE-2020-14198[0]:
> > | Bitcoin Core 0.20.0 allows remote denial of service.
> 
> Is this issue fixed in version 0.21.0~~rc5-1 in experimental?

That is not clear,  we have so far no indication if the issue was
already fixed in upstream anywhere.

Upsream information on this is (or was when filling the issue) very
scarce.

The next step would probably be to try to contact upstream to get more
information as
https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2020-14198
gives not enough details.

Regards,
Salvatore

Bug#123150: bb audio still causes video to stop iff pulseaudio is installed

[Matt Taggart]

On 1/16/21 10:25 AM, Axel Beckert wrote:


Matt: You said, you had the issue also on the console. Could you check
if that "pasuspender -- env PULSE_SERVER= bb" command workarounds the
issue for you on the virtual console, too? Maybe there's more virtual
console support from pulseaudio nowadays…


When I run that on a vc I get a brief error flash by about not being 
able to open an audio device and then BB runs, but no audio (even though 
I selected it). But at least it doesn't hang.


--
Matt Taggart
tagg...@debian.org

Bug#980209: misclassified?

[Dave Dyer]

I'm not sure how you internally characterize these things, but
I think this goes with the "calamares" installer, not the debian
installer.

Bug#976448: bitcoin: CVE-2020-14198

[Petter Reinholdtsen]

[Salvatore Bonaccorso]
> The following vulnerability was published for bitcoin.
> 
> CVE-2020-14198[0]:
> | Bitcoin Core 0.20.0 allows remote denial of service.

Is this issue fixed in version 0.21.0~~rc5-1 in experimental?
-- 
Happy hacking
Petter Reinholdtsen

Bug#979309: New upstream version available

[François de Metz]

Package: pipewire
Version: 0.3.19-1
Followup-For: Bug #979309

Dear Maintainer,

I have packaged a new version of pipewire 0.3.19 that should fix this bug.

I uploaded a new version there:
https://mentors.debian.net/debian/pool/main/p/pipewire/pipewire_0.3.19-0.1.dsc

This my first patch on Debian, I'm eager to learn more and improve the patch if 
needed.

Regards,
François

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

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

Versions of packages pipewire depends on:
ii  init-system-helpers  1.60
ii  libpipewire-0.3-modules  0.3.19-1
ii  pipewire-bin 0.3.19-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information
>From dfedd4c61a8a31948fc3714a6689f42db86cfed5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fran=C3=A7ois=20de=20Metz?= 
Date: Sat, 16 Jan 2021 18:03:10 +0100
Subject: [PATCH] New upstream release

---
 debian/changelog  | 12 ++
 debian/control|  1 +
 debian/libpipewire-0.3-0.symbols  |  1 +
 ...col-native-do-version-check-on-HELLO.patch | 42 ---
 debian/patches/series |  1 -
 .../pipewire-audio-client-libraries.install   |  3 --
 debian/pipewire-bin.install   |  3 ++
 debian/rules  |  2 -
 8 files changed, 17 insertions(+), 48 deletions(-)
 delete mode 100644 debian/patches/protocol-native-do-version-check-on-HELLO.patch
 delete mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index e49b6f2c..b3ae5cbf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+pipewire (0.3.19-0.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release (Closes: #979309)
+  * Drop patch d/p/protocol-native-do-version-check-on-HELLO.patch
+It was applied upstream.
+  * Add pipewire-pulse (Closes: #976654)
+  * Add pw-dump and pw-top tool
+  * Remove pipewire-libpulse as removed by upstream
+
+ -- François de Metz   Sat, 16 Jan 2021 18:03:10 +0100
+
 pipewire (0.3.15-1) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/control b/debian/control
index 38b0a0ed..0a2699ed 100644
--- a/debian/control
+++ b/debian/control
@@ -11,6 +11,7 @@ Build-Depends: debhelper-compat (= 13),
libgstreamer-plugins-base1.0-dev,
libgstreamer1.0-dev,
libjack-jackd2-dev (>= 1.9.10),
+   libncurses-dev,
libpulse-dev (>= 11.1),
libsbc-dev,
libsdl2-dev,
diff --git a/debian/libpipewire-0.3-0.symbols b/debian/libpipewire-0.3-0.symbols
index 9467b811..fb9ed6e1 100644
--- a/debian/libpipewire-0.3-0.symbols
+++ b/debian/libpipewire-0.3-0.symbols
@@ -265,6 +265,7 @@ libpipewire-0.3.so.0 libpipewire-0.3-0 #MINVER#
  pw_properties_setva@Base 0.3.1
  pw_properties_update@Base 0.3.1
  pw_properties_update_keys@Base 0.3.1
+ pw_properties_update_string@Base 0.3.19-1
  pw_protocol_add_listener@Base 0.3.1
  pw_protocol_add_marshal@Base 0.3.1
  pw_protocol_destroy@Base 0.3.1
diff --git a/debian/patches/protocol-native-do-version-check-on-HELLO.patch b/debian/patches/protocol-native-do-version-check-on-HELLO.patch
deleted file mode 100644
index f8637928..
--- a/debian/patches/protocol-native-do-version-check-on-HELLO.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From: Wim Taymans 
-Date: Wed, 4 Nov 2020 16:12:25 +0100
-Subject: protocol-native: do version check on HELLO
-
-Always do the version check on HELLO because the connection could
-have been moved from a v3 portal to a v0 client (like chrome)
-
-Bug: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/270
-Origin: upstream, 0.3.16, commit:https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b8c7b36d3b8be16593f554964cf2f852c21b5c2c

- src/modules/module-protocol-native/connection.c | 4 +---
- 1 file changed, 1 insertion(+), 3 deletions(-)
-
-diff --git a/src/modules/module-protocol-native/connection.c b/src/modules/module-protocol-native/connection.c
-index 84fad68..1807833 100644
 a/src/modules/module-protocol-native/connection.c
-+++ b/src/modules/module-protocol-native/connection.c
-@@ -72,7 +72,6 @@ struct impl {
- 
- 	uint32_t version;
- 	size_t hdr_size;
--	unsigned int checked:1;
- };
- 
- /** \endcond */
-@@ -319,7 +318,7 @@ static int prepare_packet(struct pw_protocol_native_connection *conn, struct buf
- 	buf->msg.opcode = p[1] >> 24;
- 	len = p[1] & 0xff;
- 
--	if (!impl->checked) {
-+	if (buf->msg.id == 0 && buf->msg.opcode == 1) {
- 		if (p[3] >= 4) {
- 			pw_log_warn("old version 

Bug#979072: Bug#979047: RM: pepperflashplugin-nonfree -- RoQA; No longer work; upstream eol

[Adam D. Barratt]

On Fri, 2021-01-15 at 18:48 +0100, Andreas Beckmann wrote:
> On Sat, 2 Jan 2021 22:09:07 +0800 Shengjing Zhu 
> wrote:
> > On Sat, Jan 2, 2021 at 9:59 PM Adam D. Barratt <
> > a...@adam-barratt.org.uk> wrote:
> > > On Sat, 2021-01-02 at 19:53 +0800, Shengjing Zhu wrote:
> > > > On Sat, Jan 2, 2021 at 7:51 PM Shengjing Zhu 
> > > > wrote:
> > > > > As Adobe has shutdown the download of flash, this package now
> > > > > no
> > > > > longer works.
> > > > > 
> > > > > https://www.adobe.com/products/flashplayer/end-of-life.html
> > > > 
> > > > If possible, remove it from stable and old-stable too.
> > > - for removal from stable, please "reportbug release.debian.org"
> > > and
> > > follow the prompts.
> 
> I think it would be better to replace the broken installer package
> with
> a dummy package stating the EoL fact. (see #978954 for more
> discussion)
> I uploaded such a dummy as 1.8.8 to sid today.

Do you have a proposed diff for such an upload?

Regards,

Adam

Bug#980255: debbugs: version graph only show on package for bugs assigned to multiple packages

[Paul Gevers]

Package: debbugs
Version: 2.6.1
Severity: minor

Hi Don, all,

As you may be aware, I (and several others) have been filing a lot of
bugs regarding autopkgtest regressions [1]. As a regression in an
autopkgtest from package a, due to an upload of package b, may either
indicate something wrong with (the autopkgtest of) package a (the
version in testin), or with the new upload of b (in unstable). Hence, I
file these bugs against package a and b, with the version of a in
testing (which often is the same as in unstable) and the version of b in
unstable (which per definition is different than in testing).

However, currently the version graph only shows one of the involved
packages. Probably generating a graph for all involved packages (I
remember debbugs supports "unlimited" involved packages) may be a bit
much, but showing only one is a bit misleading. If generating a plot
with both/all isn't feasible, maybe it's better to show no graph at all.

Paul

[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian...@lists.debian.org






OpenPGP_signature
Description: OpenPGP digital signature

Bug#937184: offlineimap: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

Am Sat, Jan 16, 2021 at 11:12:21AM + schrieb Sudip Mukherjee:
> Hi All,
> 
> On Mon, Nov 09, 2020 at 08:14:38PM +0100, Moritz Mühlenhoff wrote:
> > On Sun, Aug 02, 2020 at 06:24:44PM +0300, Ilias Tsitsimpis wrote:
> > > Control: severity -1 serious
> > > 
> > > On Sun, Jul 26, 2020 at 01:21PM, Moritz Mühlenhoff wrote:
> > > > Nine months later there's no progress, let's remove?
> > > 
> > > Agreed.
> > > 
> > > Raising the severity to serious to remove from testing, and then I will
> > > request for removal.
> > 
> > Now that offlineimap3 is available in experimental, let's go ahead with 
> > removal
> > of src:offlineimap?
> 
> I have uploaded offlineimap3 to unstable but will not migrate untill we
> have 'python3-imaplib2' in testing, which is blocked by #937831, which is
> again blocked by this #937184.
> 
> Can we go ahead with this removal please? I can then add a dummy
> transitional package so that users of offlineimap can upgrade to
> offlineimap3 with Bullseye.
> 
> Since I have the ITA on offlineimap, do I file the RM bug or that needs
> to be done by Ilias ?

I've went ahead and filed an RM bug.

Cheers,
Moritz

Bug#123150: bb audio still causes video to stop iff pulseaudio is installed

[Patrice Duroux]

Yes great!

Before my proposal, I have simply tried without success:
pasuspender -- bb

I have added a case here:
https://wiki.debian.org/PulseAudio#Stop_running_the_pulseaudio_daemon_for_a_while

So I hope it is just not noise.


On Sat, 16 Jan 2021 19:25:17 +0100 Axel Beckert  wrote:
> Hi again,
> 
> Axel Beckert wrote:
> > Patrice Duroux wrote:
> > > Another solution to keep pulseaudio installed is just to inactive it
> > > before running bb.
> […]
> > Thanks! Will create a README.pulseaudio with that information to
> > mitigate this issue a bit more than disabling audio by default already
> > did.
> 
> Actually we have that already in README.Debian since 2015 (and I wrote
> that file — seems as if I'm getting demented):
> 
> ---8<---
> BB vs PulseAudio
> 
> 
> Unfortunately BB does not work under X if PulseAudio is active and
> Music is requested. Due to this issue Music in BB is turned off by
> default in Debian.
> 
> If you have PulseAudio installed and want to show off BB with Music,
> you can do that by either:
> 
> * switching to the virtual text console and running "bb" there, or by
> 
> * temporarily letting PulseAudio release the audio hardware and hiding
>   from "bb" the fact that there is a PulseAudio server with the
>   following command:
> 
>   pasuspender -- env PULSE_SERVER= bb
> 
> This issue is tracked in the Debian Bug Tracking System at
> https://bugs.debian.org/761023
> 
>  -- Axel Beckert , Sat, 11 Apr 2015 15:22:37 +0200
> --->8---
> 
> Andrej: Does this help you?
> 
> Matt: You said, you had the issue also on the console. Could you check
> if that "pasuspender -- env PULSE_SERVER= bb" command workarounds the
> issue for you on the virtual console, too? Maybe there's more virtual
> console support from pulseaudio nowadays…
> 
>   Regards, Axel
> -- 
>  ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
> 
> 

Bug#980254: RM: offlineimap -- RoQA; Depends on Python 2, superceded by src:offlineimap3

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: sudipm.mukher...@gmail.com, ilias...@debian.org

Please remove offlineimap. It depends on Python and upstream won't port it
to Python 3. There's however a fork, which has been packaged as src:offlineimap3
(and removing this obsolete package allows adding a transitional package 
eventually)

Cheers,
Moritz

Bug#976811: transition: php8.0

[Moritz Mühlenhoff]

Am Fri, Jan 15, 2021 at 07:58:10PM +0100 schrieb Ondřej Surý:
> Thinking about it, security-wise it might be better. Microsoft will support 
> the security backports to EOL versions of PHP 7.x, but they announced they 
> won’t do it for PHP 8.x, so we are (maybe) bit more covered with PHP 7.4.

Even better :-)

Cheers,
Moritz

Bug#980253: libsdl1.2debian: unexpected key down release

[Maximilian Engelhardt]

Package: libsdl1.2debian
Version: 1.2.15+dfsg2-4
Severity: important
Tags: patch

Hi,

since some time I noticed a problem within a game (Unreal Tournament 2004)
using libsdl1.2 that the forward movement suddenly stopped, while I still had
the forward key pressed. This is an quite annoying bug when playing the game.
The bug likely also affects many other games using libsdl1.2.

I traced this behavior down to change [1] in the X server. Further analysis
showed that patches solving this issue haven been added to libsdl2. I opened an
upstream bug about backporting these to the SDL-1.2 branch and they have been
quickly accepted in [2].

A cherry-pick of the upstream patch from the SDL-1.2 fixing the issue is
available as merge request here:

https://salsa.debian.org/sdl-team/libsdl1.2/-/merge_requests/2

It would be really great to get this included in bullseye.

Thanks,
Maxi

[1]
https://cgit.freedesktop.org/xorg/xserver/commit/?id=c67f2eac56518163981af59f5accb7c79bc00f6a
[2] https://hg.libsdl.org/SDL/rev/336bcaa9432c



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

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

Bug#938509: Intent to request the removal from Debian

[Markus Koschany]

Hello,

Am Samstag, den 16.01.2021, 14:13 -0300 schrieb Caleb Marshall:
[...]
> Hello Markus,
> Last October I tried to port snowballz to python 3. I have it mostly
> working except for the GUI, which flickers when I move the mouse. If you
> could advise me on where to send a tar or diff I could fix the issues.
> Thanks,
> Caleb Marshall

You could attach a compressed tarball of your diff to your next email and I can
take a look at your changes. If the file is > 5 MB you could also send it to me
privately.

Regards,

Markus


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

Bug#123150: bb audio still causes video to stop iff pulseaudio is installed

[Axel Beckert]

Hi again,

Axel Beckert wrote:
> Patrice Duroux wrote:
> > Another solution to keep pulseaudio installed is just to inactive it
> > before running bb.
[…]
> Thanks! Will create a README.pulseaudio with that information to
> mitigate this issue a bit more than disabling audio by default already
> did.

Actually we have that already in README.Debian since 2015 (and I wrote
that file — seems as if I'm getting demented):

---8<---
BB vs PulseAudio


Unfortunately BB does not work under X if PulseAudio is active and
Music is requested. Due to this issue Music in BB is turned off by
default in Debian.

If you have PulseAudio installed and want to show off BB with Music,
you can do that by either:

* switching to the virtual text console and running "bb" there, or by

* temporarily letting PulseAudio release the audio hardware and hiding
  from "bb" the fact that there is a PulseAudio server with the
  following command:

  pasuspender -- env PULSE_SERVER= bb

This issue is tracked in the Debian Bug Tracking System at
https://bugs.debian.org/761023

 -- Axel Beckert , Sat, 11 Apr 2015 15:22:37 +0200
--->8---

Andrej: Does this help you?

Matt: You said, you had the issue also on the console. Could you check
if that "pasuspender -- env PULSE_SERVER= bb" command workarounds the
issue for you on the virtual console, too? Maybe there's more virtual
console support from pulseaudio nowadays…

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#980250: debbugs: rc export not great for bugs assigned to multiple packages

[Paul Gevers]

Package: debbugs
Version: 2.6.1
Severity: normal

Hi Don, all,

As you're probably well aware, the Release team is using the exports [1]
from the bts to influence the migration of packages from unstable to
testing.

As you may be aware, I (and several others) have been filing a lot of
bugs regarding autopkgtest regressions [2]. As a regression in an
autopkgtest from package a, due to an upload of package b, may either
indicate something wrong with (the autopkgtest of) package a (the
version in testin), or with the new upload of b (in unstable). Hence, I
file these bugs against package a and b, with the version of a in
testing (which often is the same as in unstable) and the version of b in
unstable (which per definition is different than in testing).

However, currently this doesn't (always??) get listed on the excuses
page, because the export lists the bug for package b under both testing
and unstable.

Example case that's currently there: bug #980111, with

paul@mulciber ~ $ rmadison frr
frr| 6.0.2-2+deb10u1 | stable | source, amd64, arm64,
armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
frr| 6.0.2-2+deb10u1 | stable-debug   | source
frr| 7.4-1   | testing| source
frr| 7.4-1   | unstable   | source
frr| 7.4-1   | unstable-debug | source
frr| 7.4-1+b1| testing| amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x
frr| 7.4-1+b1| unstable   | amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x

and

paul@mulciber ~ $ rmadison pam
pam| 1.1.8-3.1+deb8u2 | oldoldstable   | source
pam| 1.1.8-3.6| oldstable  | source
pam| 1.3.1-5  | stable | source
pam| 1.3.1-5  | testing| source
pam| 1.4.0-2  | unstable   | source
pam| 1.4.0-2  | unstable-debug | source

and

elbrus@respighi:~$ grep 980111  ~release/britney/state/rc-bugs-*
/home/release/britney/state/rc-bugs-testing:src:frr 980111,972767
/home/release/britney/state/rc-bugs-testing:src:pam 956355,980111
/home/release/britney/state/rc-bugs-unstable:src:frr 980111,972767
/home/release/britney/state/rc-bugs-unstable:src:pam 980111

I would expect that bug 980111 would only be listed for pam in the
unstable export.

Paul

[1] https://bugs.debian.org/release-critical/britney/${suite}-nr
[2]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian...@lists.debian.org




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977520: buster-pu: package steam/1.0.0.59-4+deb10u1

[Adam D. Barratt]

Hi,

Sorry for the delay in getting back to you.

On Tue, 2020-12-15 at 23:36 +, Simon McVittie wrote:
> Collect selected changes from unstable, in particular:
> * Avoid redirecting stderr by default, which interferes with
> upstream's
>   usual support/diagnostic process
> * Add missing dependencies and Recommends, variously needed by
> proprietary
>   games installed via Steam or via Steam's new container runtime
> system
> * Update udev rules to cover more game controllers
[...]
> If the release team would accept it, a backport of the .deb from
> testing/unstable would be a reasonable alternative to this.

Does that include many changes that aren't in your proposed list?

> The source
> debdiff would be large, but the practical differences would be small:
> reviewing unpacked .deb trees would be more effective than a source
> debdiff, since all meaningfully reviewable changes are in text files
> anyway.

Could we see what that looks like, please? As usual, a filtered diff
would be fine.

Regards,

Adam

Bug#959469: buster-pu: package openssl/1.1.1g-1

[Kurt Roeckx]

On Thu, Jan 14, 2021 at 09:13:49PM +0100, Sebastian Andrzej Siewior wrote:
> On 2021-01-14 19:03:37 [+0100], Kurt Roeckx wrote:
> > > Do you have pointers to upstream issues?
> > 
> > There are a whole bunch of other issues and pull requests related to
> > this. I hope this is the end of the regressions in the X509 code.
> 
> Okay. Please ping once this gets sorted out and I will prepease
> unstalbe/stable uploads. The m2crypto issue got resolved in unstable
> \o/.

So I went over the open issues and pull requests, and currently
don't see a reason not to upload it to unstable with those 2
patches. I don't know about any other regressions in 1.1.1.


Kurt

Bug#977028: buster-pu: package sane-backends/1.0.27-3.2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2020-12-10 at 09:44 +0100, Jörg Frings-Fürst wrote:
> The udev rule to change the owner/group of usb scanners are not
> included.
> 
> [ Impact ]
> Scanner working only as root
> 
> [ Risks ]
> Trivial. The same rule are included in older sane-backends releases.
> The same rule is working in bullseye
[...]
>  * Fix missing udev rules (Closes: #941038)
>- New debian/99-libsane.rules.

The metadata for that bug does not include a fixed version, and implies
that it affects the package in unstable. That seems to be in direct
contradiction to your comment in the "risks" section above.

Assuming that this is simply an oversight, please add an appropriate
fixed version to #941038 and go ahead.

Regards,

Adam

Bug#977511: buster-pu: package edk2/0~20181115.85588389-3+deb10u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2020-12-15 at 14:53 -0700, dann frazier wrote:
> Address CVE-2019-14584 (#977300), for which the security team has
> declined to
> release a DSA.
> 

Sorry for the delay. Please go ahead.

Regards,

Adam

Bug#123150: bb audio still causes video to stop iff pulseaudio is installed

[Axel Beckert]

Control: retitle -1 bb: Enabling audio causes video to freeze iff pulseaudio is 
running

Hi Patrice,

Patrice Duroux wrote:
> Another solution to keep pulseaudio installed is just to inactive it
> before running bb.
> Within systemd user session you can do:
> 
> systemctl --user mask pulseaudio.socket
> systemctl --user stop pulseaudio.service
> 
> And then activate back your pulseaudio service:
> 
> systemctl --user unmask pulseaudio.socket
> systemctl --user start pulseaudio.service
> 
> Hope it helps!

Thanks! Will create a README.pulseaudio with that information to
mitigate this issue a bit more than disabling audio by default already
did.

Also retitling the bug report to be even more precise.

> ps: pulseaudio -k is generally not enough for many reasons.

*sigh*

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#980249: wiki.debian.org: 408 Request Timeout editing U-boot/Status

[Vagrant Cascadian]

Package: wiki.debian.org
Severity: normal

Sometime in the last few weeks, I'm only able to successfully edit
https://wiki.debian.org/U-boot/Status maybe 1 out of every 5 or 10
attempts. Either preview or save changes button usually ends with:

  Request Timeout

  Server timeout waiting for the HTTP request from the client.
  Apache Server at wiki.debian.org Port 443

I'm using firefox-esr on buster.


live well,
  vagrant


-- System Information:
Debian Release: 10.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (12, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64

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


signature.asc
Description: PGP signature

Bug#979724: buster-pu: package libmaxminddb/1.3.2-1+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2021-01-10 at 21:39 +0200, Faidon Liambotis wrote:
> This is an buster proposed update to fix CVE-2020-28241:
> > libmaxminddb before 1.4.3 has a heap-based buffer over-read in
> > dump_entry_data_list in maxminddb.c.
> 
> The security team has marked the CVE as " (Minor issue)", and
> filed #973878 against the package.
> 

Please go ahead.

Regards,

Adam

Bug#977735: buster-pu: package node-ini/1.3.5-1+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2020-12-19 at 20:53 +0100, Xavier Guimard wrote:
> node-ini is vulnearable to CVE-2020-7788: if an attacker submits a
> malicious
> INI file to an application that parses it with ini.parse, they will
> pollute
> the prototype on the application. This can be exploited further
> depending
> on the context. (#977718)

Please go ahead.

Regards,

Adam

Bug#864338: gpsd: Provide a way to initialize GPS mode on cards like Ericsson F5521gw or F3507g

[Bernd Zeimetz]

Hi,

please note that this is not a forum and not a user help lines, its a
bug tracker. Please fix your device and permissions issues first, with
the help from a debian-user mailinglist for example, and if you can send
a proper report, do so.


> Now I am confused that none of the previously working steps led to any output 
> on my device port.

what is a "device port"?

> In the past it wasn't possible to directly read /dev/ttyACM2 because of 
> permission issues.

permission issues are not a problem that gpsd can fix for you. Use udev
rules or whatever else is necessary.

> The necessary information are posted here: 
> https://forum.ubuntuusers.de/topic/gpsd-mit-ericsson-f5521gw-mobile-broadband-mod/#post-6727147
>  . 
> For now I can only report that gpsd can't read from the pipe mentioned in 
> this post.

Which is just fine, because what you are doing there is sad sad
nonsense. Learn to fix device permissions.

> I turned the gps receiver on in the way I was able to remember, went outside, 
> but couldn't get any output of the NMEA stream when reading from 
> /dev/ttyACM2. I tried around with hard-resets and different ways connecting 
> clients, reading directly from port, but nothing turned out to work for me.

Thas a LTE modem or something similar, you'll probably have to switch it
into gps mode first. Nothing gpsd will do for you.


So basically:

1. fix your permission issues (using a pipe is not a fix!), maybe using
udev or whatever else is necessary.
2. learn how to put your modem into a working mode
3. trigger gpsd to read from you device.


If you then run into bugs, run gpsd in debug mode...


Bernd

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#979749: buster-pu: package emacs/1:26.1+1-3.2+deb10u1

[Adam D. Barratt]

On Sun, 2021-01-10 at 20:08 -0600, Rob Browning wrote:
> dkg has requested that we consider fixing this bug in buster:
> 
>   Debian: https://bugs.debian.org/919642
>   Upstream: https://debbugs.gnu.org/34121
> 
> which is fairly straightforward (just the new patch at the end,
> cherry-picked directly from the upstream fix):

The metadata for that bug implies that it still affects the package in
unstable (hence the lack of any green on the version graph). I suspect
this is simply because the "fixed" version doesn't correspond to an
actual Debian package version. Please could you add a fixed version
that indicates the earliest upload to Debian that included the fix.

Also, while it's possibly slightly picky:

+emacs (1:26.1+1-3.2+deb10u2~1.gbp7c5887) UNRELEASED; urgency=medium
+
+  ** SNAPSHOT build @7c5887c8ae064398fafa38b8fea4c5d500830d5f **
+
+  * UNRELEASED
+
+ -- Rob Browning   Sun, 10 Jan 2021 19:22:48 -0600

could we have a finalised version of that, please? :-)

Assuming the above small points get resolved, the patch looks fine to
me; thanks.

Regards,

Adam

Bug#123150: bb audio still causes video to stop iff pulseaudio is installed

[Patrice Duroux]

Hi,

Another solution to keep pulseaudio installed is just to inactive it before
running bb.
Within systemd user session you can do:

systemctl --user mask pulseaudio.socket
systemctl --user stop pulseaudio.service

And then activate back your pulseaudio service:

systemctl --user unmask pulseaudio.socket
systemctl --user start pulseaudio.service

Hope it helps!
;-)

ps: pulseaudio -k is generally not enough for many reasons.

On Sat, 16 Jan 2021 16:43:27 +0100 Axel Beckert  wrote:
> Control: retitle -1 bb audio causes video to stop iff pulseaudio is installed
> Control: tag -1 + confirmed upstream
> 
> Hi,
> 
> Andrej Shadura wrote:
> > I also still observe this issue.
> 
> JFTR: It works fine for me for ages. (But see below.)
> 
> > In fact, I don’t remember ever being able to run BB with sound on
> > Linux :(
> 
> According to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=123150#108 this
> was suspected to be an issue with libmikmod, esd and pulseaudio. It
> had been said to be fixed with some libmikmod upload, but then was
> said to still occur.
> 
> Even though this detail was posted nearly a decade ago and later
> partially invalidated since the proposed libmikmod changes didn't
> help, I did a quick crosscheck: And yes, installing pulseaudio
> triggers this issue: Sound continues, but video stops. Not immediately
> if installed during bb is running, but upon the next start of bb.
> 
> No idea why, though. On the one hand I avoid pulseaudio as much as
> possible for a multitude of reasons including issues like this one.
> Which is probably also the reason why I never ran into this myself.
> 
> At least I don't have any experience with programming audio or video
> processsing itself. So any hint on why pulseaudio triggers this issues
> (or even better, patches :-) would be very appreciated. (i.e. the
> "help" tag is still valid.)
> 
> P.S.: After purging pulseaudio again, bb works again as expected, too.
> But I had to kill a running pulseaudio process manually despite I
> didn't have to start it manually when I installed the package. *sigh*
> 
> P.P.S.: Yes, the double "f" in "iff" is on purpose. See
>   https://en.wiktionary.org/wiki/iff
> 
>   Regards, Axel
> -- 
>  ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
> 
> 

Bug#980164: firmware-amd-graphics: amd rx 6800 compatibility

[alain]

Package: firmware-amd-graphics
Version: 20201118-1
Followup-For: Bug #980164
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr

here is my last try .

installed firmware-amd-graphics 20201118-1 (testing)
copied sienna_cichlid* from git .

nothing .
black screen with the irq's scanning in front of it .

the only way to come in debian is to pass the "nomodeset=1" to the grub (letter
"e" at grub boot time)

firmwares are wrong .
testing and sid .

could you help me , please ?




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

Kernel: Linux 5.10.0-1-amd64 (SMP w/16 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.139

-- no debconf information

Bug#979296: u-boot: Restructure the packaging

[Vagrant Cascadian]

On 2021-01-16, Nicolas Boulenguez wrote:
> Source: u-boot
> Followup-For: Bug #979296
>
> Please only consider this version, rebased on 96b110eb.
> 32296e74 is of little interest by itself, but documents 1f3d5824.
> 6125bcad only applies on top, so I am submitting it here for now.
>
> Nothing seems unexpected in the output of the following commands (with
> patches from bugs 979482 979660 980234 980235 980237 applied).

You've clearly put a lot of work into improving u-boot, so big thanks!

I suspect I will eventually apply the changes, but it is a bit
overwhelming for me to consider this late in the bullseye development
cycle...

On the other hand, it might be nice to get this in now, to avoid great
divergence between bullseye and bookworm, should we ever need to make
changes during the stable release cycle of bullseye...

I recognize it is a large change overall, but maybe there are a few more
incremental steps that could be split out into separate patches that
could make the progression easier to follow? Or maybe not; it is simply
a large change.


A few minor comments below.

> diff --git a/debian/control b/debian/control
> index 6f4cc17906..ff3e528e50 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -47,7 +47,9 @@ Description: A boot loader for embedded systems
>   intended to be easy to port and to debug, and runs on many
>   supported architectures, including PPC, ARM, MIPS, x86, m68k,
>   NIOS, and Microblaze.
> - ${uboot:platforms}
> + .
> + Included platforms:
> + ${u-boot:platforms}

These changes are unrelated to restructuring the package. Please drop
them for now and/or submit separatelty. I've considered changes like
this in the past, though left them out... one reason is "u-boot"
contains no target platforms on armhf, for example, although at this
point it might be worth dropping the "u-boot" package on armhf.


> From: Nicolas Boulenguez 
> Date: Thu, 14 Jan 2021 09:47:43 +0100
> Subject: [PATCH 4/4] Remove the pkg.u-boot.subarch.* profiles
>
> The new packaging is more flexible.
> ---
>  debian/rules | 10 ++
>  1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/debian/rules b/debian/rules
> index b207c032f1..3331ebffe5 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -37,14 +37,8 @@ notools := $(filter 
> pkg.uboot.notools,$(DEB_BUILD_PROFILES))
>  
>  # Select the subarchs for DEB_HOST_ARCH
>  all_subarchs := $(shell dh_listpackages --arch --no-package=u-boot-tools)
> -# DEB_BUILD_PROFILES=pkg.uboot.subarch.SUBARCH may
> -# limit builds to only certain subarchitectures
> -# e.g. pkg.uboot.subarch.rockchip will only build rockchip targets.
> -ifeq (,$(filter pkg.uboot.subarch.%,$(DEB_BUILD_PROFILES)))
> -  built_subarchs := $(all_subarchs)
> -else
> -  built_subarchs := $(patsubst pkg.uboot.subarch.%,u-boot-%,$(filter 
> pkg.uboot.subarch.%,$(DEB_BUILD_PROFILES)))
> -endif
> +# This variable is intended for command line override:
> +built_subarchs := $(all_subarchs)
>  
>  %:
># The -N options prevents a lots of warnings about obviously missing files.
> -- 
> 2.20.1

How is this to be used with, say, sbuild?


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#980248: cgit: kernel regression breaks cgit's sendfile()

[Johannes Berg]

Package: cgit
Version: 1.2.3+git2.25.1-1
Severity: normal

Dear Maintainer,

Having changed my virtual machine setup to run kernel 5.10.4,
I've noticed that a kernel regression breaks cgit's use of
sendfile() in e.g. fcgiwrap setups like mine, because sendfile()
to a pipe() no longer works. See also

https://lore.kernel.org/lkml/C8KER7U60WXE.25UFD8RE6QZQK@oguc/

(I reported the additional pipe() issue there, bug the list is
currently down). A simple test program I wrote is here:

https://p.sipsolutions.net/b8b30d96fd9428a8.txt


In any case - this is obviously not really a bug in cgit but
rather in the kernel, but I thought perhaps a warning might be
something you'd appreciate.

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

Kernel: Linux 5.10.4+ (SMP w/6 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages cgit depends on:
ii  libc62.31-6
ii  liblua5.1-0  5.1.5-8.1+b3
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages cgit recommends:
ii  nginx-core [httpd]  1.18.0-6+b1
ii  nginx-full [httpd]  1.18.0-6

Versions of packages cgit suggests:
ii  python3   3.9.1-1
ii  python3-docutils  0.16+dfsg-3
pn  python3-markdown  
ii  python3-pygments  2.7.1+dfsg-1

-- Configuration Files:
/etc/cgitrc changed [not included]

-- no debconf information

Bug#978098: closed by Debian FTP Masters (reply to Alberto Garcia ) (Bug#978098: fixed in webkit2gtk 2.31.1-1)

[Alberto Garcia]

On Sat, Jan 16, 2021 at 04:09:07PM +, Debian Bug Tracking System wrote:
> We believe that the bug you reported is fixed in the latest version
> of webkit2gtk, which is due to be installed in the Debian FTP
> archive.

Hmmm... however WebKitGTK 2.31.1 introduced a new dependency on
libmanette and I didn't realize that that one is linux-only :-(

I'll change that for the next upload.

I saw that the some of the changes needed for the Hurd were already
upstreamed, so I applied only the one concerting the realpath()
function, although I decided to use #if OS(HURD) for the time being
rather than using the POSIX version.

Berto

Bug#955479: apparmor fixes for xline_db and geoip

[Filippo Giunchedi]

On Wed, Apr 01, 2020 at 07:03 PM, Marc Dequènes wrote:
> I added this line to the apparmor policy:
>   /usr/share/GeoIP/GeoIP.dat r,
> 
> Btw the package could also Suggest geoip-database needed for this module.
 
Thank you for the report, I'm not an apparmor expert but I'm happy to
include support in the package (at
https://salsa.debian.org/debian/inspircd)
 
Suggesting 'geoip-database' is a good idea, I'll add that!

Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON

[Ard Biesheuvel]

On Sat, 16 Jan 2021 at 18:24, Diederik de Haas  wrote:
>
> On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> > Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64 builds
>
> Is there a reason why it shouldn't be included in armhf builds? If not, then
> I'd like to see it enabled there too.
> (And possibly in linux-image-rpi on armel as well?)

Agreed for armhf, assuming CONFIG_CRYPTO_ADIANTUM is already enabled
on those platforms too. For armel, it depends on whether kernel mode
NEON is already enabled in the first place.

Bug#980214: linux-image-5.10.0-1-arm64: please enable CONFIG_CRYPTO_NHPOLY1305_NEON

[Diederik de Haas]

On zaterdag 16 januari 2021 10:42:19 CET Ard Biesheuvel wrote:
> Please enable CONFIG_CRYPTO_NHPOLY1305_NEON as a module for arm64 builds

Is there a reason why it shouldn't be included in armhf builds? If not, then 
I'd like to see it enabled there too.
(And possibly in linux-image-rpi on armel as well?)


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

Bug#980202: FTBFS: gscan2pdf tests fail

[Jeff]

This seems to be a bug in imagemagick preventing imagemagick from 
migrating from unstable to testing:


https://tracker.debian.org/pkg/imagemagick

https://ci.debian.net/packages/g/gscan2pdf/testing/amd64/



OpenPGP_signature
Description: OpenPGP digital signature

Bug#975075: tech-ctte: non-systemd dependencies in non-NM packages

[Russ Allbery]

Matthew Vernon  writes:

> The maintainer won't talk to me, nor will they engage with me (or anyone
> else) on this thread, though they will it seems talk to the TC in
> private.

> I think, though, that it is common ground between submitter and
> maintainer that the Depends is necessary for udisks2 (unlike in
> network-manager where it turned out not to be).

> There was some discussion about whether elogind works with udisks2 in
> early 2019 and again in early 2020. On 2020-03-15 Nils draws the
> maintainer's attention to the explicit mention of elogind support in
> udisks upstream changelog.

Looking at this bug, I agree with Matthew: there is no indication that I
can see in the bug discussion that the solution proposed there would not
work.  I can speculate about why the maintainer may have not wanted to
change the dependency, but it's somewhat pointless to do so in the absence
of any additional information.

There may be some Policy work necessary to make it clear that this
dependency can also be used for packages that use the C ABI, not just the
D-Bus ABI, but I don't see any clear reason why that should block this
change.

If the question is one of maintainer support, adding some note in
README.Debian or in a reportbug prescript to say that only systemd is
directly supported by the package maintainer and problems on non-systemd
systems will require someone else to step forward to analyze and help with
the problem feels like a better solution for the project as a whole than
not changing the dependency.

> I have not come to the TC to ask them to overrule the maintainer
> frivolously nor before exploring as many other options as I could.

I understand (oh, boy, do I ever) how strained relationships are after the
long-running init system battles, but it's very hard to resolve problems
without the TC when one of the parties is unwilling to communicate.  There
have been a lot of other hostile and aggressive threads about init system
issues, but this specific bug is not one of them as far as I can tell.

I don't want to force anyone into communicating when they don't want to
(general rule 2.1.1), but then I think they need to welcome NMUs or a
co-maintainer who can deal with the things they don't want to have to
think about or *something*.  This kind of silent treatment is really
demoralizing to other people in the project who are not at fault for any
of the historical init system hostility.

-- 
Russ Allbery (r...@debian.org)  

Bug#938509: Intent to request the removal from Debian

[Caleb Marshall]

On Mon, 21 Dec 2020 14:03:10 +0100 Markus Koschany  wrote:
> Hi,
>
> as previously announced on debian-devel-games [1] I intend to request the
> removal of this source or binary package from Debian at the end of January
> 2021. If you are interested in fixing this bug, please let me know in
time to
> avoid the removal from Debian.
>
> Markus
>
>
> [1] https://lists.debian.org/debian-devel-games/2020/12/msg00013.html

Hello Markus,
Last October I tried to port snowballz to python 3. I have it mostly
working except for the GUI, which flickers when I move the mouse. If you
could advise me on where to send a tar or diff I could fix the issues.
Thanks,
Caleb Marshall

Bug#971040: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency

[Samuel Henrique]

Control: tags -1 - fixed + pending

Hello Bruno,

Thanks for pointing out to the fix and providing an MR, I have also
replied there.

I removed the "fixed" tag as it doesn't apply to this situation, I
believe "pending" would be more appropriate. I'm gonna test the fix
and upload if everything works (as said on the MR, feel free to change
it to apply a patch instead of changing upstream).

Cheers

--
Samuel Henrique 

Bug#975124: dogecoin: FTBFS: qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type ‘class QPainterPath’

[Petter Reinholdtsen]

[Lucas Nussbaum]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > qt/trafficgraphwidget.cpp: In member function ‘void 
> > TrafficGraphWidget::paintPath(QPainterPath&, QQueue&)’:
> > qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type 
> > ‘class QPainterPath’
> >53 | path.moveTo(x, YMARGIN + h);
> >   | ^~~~

Perhaps the code is missing a '#include ', ref
https://doc.qt.io/qt-5/qpainterpath.html >?

-- 
Happy hacking
Petter Reinholdtsen

Bug#980245: ITP: r-cran-scattermore -- GNU R scatterplots with more points

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-scattermore -- GNU R scatterplots with more points
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-scattermore
  Version : 0.7
  Upstream Author : Mirek Kratochvil
* URL : https://cran.r-project.org/package=scattermore
* License : GPL-3+
  Programming Lang: GNU R
  Description : GNU R scatterplots with more points
 This GNU R package provides a C-based conversion of large
 scatterplot data to rasters.  It speeds up plotting of data
 with millions of points.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-scattermore

Bug#980244: python3-alsaaudio: upgrade to new upstream version 0.9

[Oswald Buddenhagen]

Package: python3-alsaaudio
Version: 0.8.4-1.1+b3
Severity: normal

the new release has been available for a while already. please upgrade.


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

Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, 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 python3-alsaaudio depends on:
ii  libasound2  1.2.4-1.1
ii  libc6   2.31-9
ii  python3 3.9.1-1

Versions of packages python3-alsaaudio recommends:
ii  libjs-jquery  3.5.1+dfsg+~3.5.5-5
ii  libjs-underscore  1.9.1~dfsg-1

python3-alsaaudio suggests no packages.

-- no debconf information

Bug#980233: uscan: please allow for non-GPG signature verification mechanisms

[Mattia Rizzolo]

On Sat, Jan 16, 2021 at 09:35:55AM -0500, Ryan Kavanagh wrote:
> Please allow users to specify arbitrary scripts to verify upstream
> release tarballs. For example, the OpenSMTPD and OpenBSD projects use
> signify-openbsd (from the signify-openbsd package) instead of GnuPG to
> verify their releases.

I suppose that's a fine feature to add, however keep in mind that the
upstrem gpg signatures have a much wider support, including in dpkg
itself.
Perhaps you may wish to start a broader discussion about this topic and
get dpkg & friends onboard?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature