Bug#976898: xorg-server: reproducible builds: Embeds running kernel version

[Vagrant Cascadian]

Source: xorg-server
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: kernel
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org


The /usr/bin/Xorg binary and other generated binaries embed the running
kernel version:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/diffoscope-results/xorg-server.html

  ./usr/bin/Xorg
  2623  Linux·4.19.0-13-amd64·x86_642623Linux·4.19.0-13-686-pae·i686


This is due to configure.ac setting a default value with "uname -srm"
for OSNAME, which includes the running kernel version:

  
https://tests.reproducible-builds.org/debian/issues/unstable/captures_kernel_version_issue.html


The attached patch passes --with-os-name=DEB_HOST_ARCH_OS to configure
which avoids embedding the running kernel version in the shipped
binaries.


Thanks for maintaining xorg-server!


live well,
  vagrant

From 6f3281f6dbf0cc15a40c2561de822f10e169c798 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 9 Dec 2020 07:01:19 +
Subject: [PATCH] debian/rules.flags: Specify --with-os-name as
 DEB_HOST_ARCH_OS to avoid embedding the running kernel version, which may
 vary between builds.

https://tests.reproducible-builds.org/debian/issues/unstable/captures_kernel_version_issue.html
---
 debian/rules.flags | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules.flags b/debian/rules.flags
index 03486bb81..38596fe72 100644
--- a/debian/rules.flags
+++ b/debian/rules.flags
@@ -18,6 +18,7 @@ confflags += \
 	--disable-strict-compilation \
 	--disable-debug \
 	--with-int10=x86emu \
+	--with-os-name="$(DEB_HOST_ARCH_OS)" \
 	--with-os-vendor="$(VENDOR)" \
 	--with-builderstring="$(SOURCE_NAME) $(SOURCE_VERSION) ($(SUPPORT))" \
 	--with-xkb-path=/usr/share/X11/xkb \
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#976899: texlive-latex-extra: powersem and seminar classes broken: Extra \endgroup

[Meelis Roos]

Package: texlive-latex-extra
Version: 2020.20201129-1
Severity: normal
X-Debbugs-Cc: mr...@linux.ee

Dear Maintainer,

The document classes seminar and powerseem seem to be broken and result
in "Extra \endgroup" error. Using article documentclass instead works
fine, but powersem and seminar are broken like below:

latex ajut.tex:
[...]
`pst-ovl' v0.07b, 2020/05/01 (tvz,hv)))
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/seminar/sem-page.sty)))
! Extra \endgroup.
\document ->\endgroup
  \the \before@document \begingroup \UseOneTimeHook {beg...
l.3 \begin{document}

?
! Emergency stop.
\document ->\endgroup
  \the \before@document \begingroup \UseOneTimeHook {beg...
l.3 \begin{document}

No pages of output.
Transcript written on ajut.log.



This is the minimal file that shows the problem:
---
\documentclass{powersem}

\begin{document}
Text!
\end{document}
---


$ latex -recorder ajut.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./ajut.tex
LaTeX2e <2020-10-01> patch level 2
L3 programming layer <2020-10-27> xparse <2020-03-03>
(/usr/share/texlive/texmf-dist/tex/latex/texpower/powersem.cls
Document Class: powersem 2004/07/27 v0.8a Create online Presentations with semi
nar.
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/seminar/seminar.cls
Document Class: seminar 2014/01/17, 1.61
Documentclass: `seminar' v1.61 <2014/01/17> (tvz,hv)
(/usr/share/texlive/texmf-dist/tex/latex/pst-ovl/pst-ovl.sty
(/usr/share/texlive/texmf-dist/tex/latex/pstricks/pstricks.sty
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def))
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/pst-xkey.tex
(/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.tex
(/usr/share/texlive/texmf-dist/tex/generic/pstricks/pst-fp.tex
`pst-fp' v0.05, 2010/01/17 (hv))
(/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common-lists.t
ex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfkeys.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfkeysfiltered.code.t
ex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgffor.code.tex
Loading pgffor.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmath.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathcalc.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathutil.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathparser.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.basic.code
.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.trigonomet
ric.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.random.cod
e.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.comparison
.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.base.code.
tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.round.code
.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.misc.code.
tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.integerari
thmetics.code.tex)))
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfloat.code.tex)))
`PSTricks' v3.01  <2020/09/18> (tvz,hv)
(/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.con))
(/usr/share/texlive/texmf-dist/tex/generic/pstricks/pst-fp.tex))
(/usr/share/texlive/texmf-dist/tex/generic/pst-ovl/pst-ovl.tex
`pst-ovl' v0.07b, 2020/05/01 (tvz,hv)))
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/seminar/sem-page.sty)))
! Extra \endgroup.
\document ->\endgroup
  \the \before@document \begingroup \UseOneTimeHook {beg...
l.3 \begin{document}

?

Resulting ajut.fls file is attached.

 List of ls-R files

-rw-r--r-- 1 root root 1733 Dec  9 

Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64

[Lars Wirzenius]

On Tue, Dec 08, 2020 at 05:12:57PM +, David Edmondson wrote:
> I figured that out today (need to specify a 64 bit CPU) and provided an
> updated set of patches.

I'll just note that David updated his patches and that I've merged
them now.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#976704: po4a: Missing dependency on libpod-parser-perl

[Helge Kreutzmann]

Hello Martin,
On Tue, Dec 08, 2020 at 11:18:12PM +0100, Martin Quinson wrote:
> it seems to me that this is an upstream bug that you will never encounter 
> when using the Debian package (neither source nor binary). Do you agree?

I'm using the Debian package, not the something from other sources. My
intend is to rebuild other packages or upstream packages, but not
installing them, as I'm only interested in up-to-date de.po files.

The first time I hit this problem was when I tried to rebuild the
upstream sources of dpkg.

> - Le 7 Déc 20, à 9:24, Helge Kreutzmann deb...@helgefjell.de a écrit :

…

> > After installing libpod-parser-perl, the build suceedes.

…

And once libpod-parser-perl from Debian is installed the build suceeds. So 
to me it appears as if libpod-parser-perl is required to operate po4a at 
least with packages like dpkg and po4a.

Thus I think this is a Debian bug, not an upstream one (or a bug in
both, if libpod-parser-perl is not meant to be used, which I cannot
judge).

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#964496: libjson-validator-perl: URL is gone, this is now RC

[Andrius Merkys]

Hi Wouter,

I have uploaded libjson-validator-perl with cache links for OpenAPI
schemas. Please upload sreview-web 0.6.1-2 without the obstructing cache
files.

Cheers,
Andrius

Bug#976645: git-lfs: please create golang-github-git-lfs-git-lfs-dev binary package

[Stephen Gelman]

On Dec 6, 2020, at 7:28 AM, Pirate Praveen  wrote:
> 
> Package: git-lfs
> Version: 2.12.1-1
> Severity: wishlist
> 
> Hi,
> 
> Please create golang-github-git-lfs-git-lfs-dev binary package in addition to 
> git-lfs binary package.
> 
> New version of gitaly needs github.com/git-lfs/git-lfs as a build dependency.
> 
> Thanks
> Praveen
> 

This has been uploaded and is sitting in NEW 
(https://ftp-master.debian.org/new/git-lfs_2.12.1-2.html 
)

Stephen

Bug#976897: osmo-sgsn FTBFS with libosmocore 1.4.1: error: redefinition of ...

[Adrian Bunk]

Source: osmo-sgsn
Version: 1.3.0-3
Severity: serious
Tags: ftbfs
Control: close -1 1.6.2+dfsg1-2

https://buildd.debian.org/status/package.php?p=osmo-sgsn

...
In file included from gtphub.c:41:
/usr/include/osmocom/core/socket.h:24:8: error: redefinition of ‘struct 
osmo_sockaddr’
   24 | struct osmo_sockaddr {
  |^
In file included from gtphub.c:35:
../../include/osmocom/sgsn/gtphub.h:38:8: note: originally defined here
   38 | struct osmo_sockaddr {
  |^
...


This seems to be already fixed in the version in experimental.

Bug#976896: osmo-mgw FTBFS with libosmocore 1.4.1: test failure

[Adrian Bunk]

Source: osmo-mgw
Version: 1.4.0-1
Severity: serious
Tags: ftbfs bullseye sid
Control: close -1 1.7.0+dfsg1-1

https://buildd.debian.org/status/fetch.php?pkg=osmo-mgw=amd64=1.4.0-1%2Bb1=1607470883=0

...
./testsuite.at:27: exit code was 134, expected 0
4. testsuite.at:24: 4. mgcp (testsuite.at:24): FAILED (testsuite.at:27)
...


This seems to be already fixed in the version in experimental.

Bug#903871: Re.: libsane: sane-genesys backend segfaults

[Jörg Frings-Fürst]

Hello Alison,

after there are several new releases from upstream, I close this bug.

If the bug still exists, please open a new bug report against the current
version.

Many thanks.


CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#890922: sane: Agfa SnapScan 1212U does not work after upgrade to stretch.

[Jörg Frings-Fürst]

Hello Michael,

please can you check if the bug still exists in the current version? 


CU
Jörg 
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#976791: Acknowledgement (Enable CONFIG_SOUNDWIRE (and related drivers))

[Matt Corallo]

Oops, it seems I was confused about when this landed upstream. Enabling soundwire on 5.9 doesn't accomplish much, but 
5.10 should bring support for audio on new Dell machines, presumably with something like the following:


CONFIG_REGMAP_SOUNDWIRE=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK=y
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE=m
CONFIG_SND_SOC_RT700=m
CONFIG_SND_SOC_RT700_SDW=m
CONFIG_SND_SOC_RT711=m
CONFIG_SND_SOC_RT711_SDW=m
CONFIG_SND_SOC_RT715=m
CONFIG_SND_SOC_RT715_SDW=m
CONFIG_SOUNDWIRE=m
CONFIG_SOUNDWIRE_CADENCE=m
CONFIG_SOUNDWIRE_INTEL=m
CONFIG_SOUNDWIRE_GENERIC_ALLOCATION=m

On 12/7/20 6:18 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 976791: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976791.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian Kernel Team 

If you wish to submit further information on this problem, please
send it to 976...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#976895: libasound2: regression (stops working): Alsa_driver: recover: pcm_status(): Broken pipe

[Thorsten Glaser]

Package: libasound2
Version: 1.2.4-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, debian-multime...@lists.debian.org
Control: notfound -1 1.2.3.2-1+b1

The latest libasound2 introduced a severe regression:


Starting musescore3 and loading a score, e.g. like this…

$ musescore3 /usr/share/mscore3-3.2/demos/Reunion.mscz

… quickly brings the whole system down because it spits tons of lines…

Alsa_driver: recover: pcm_status(): Broken pipe

… to the xterm in which it was invoked.


Running it without output…

$ musescore3 /usr/share/mscore3-3.2/demos/Reunion.mscz >/dev/null 2>&1

… just results in…

  PID USER  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   
24181 tglase 0  871224 218944  73920 D 100.0   2.7   0:06.67 musescore3 
/usr/share/mscore3-3.2+

… and the user has to kill the offending program by ^Cing in the terminal
(as killing when in “D” state cannot work).


This is where I started:

ii  alsa-utils1.2.4-1   
  amd64Utilities for con>
ii  libasound2:amd64  1.2.4-1   
  amd64shared library fo>
ii  libasound2:i386   1.2.4-1   
  i386 shared library fo>
ii  libasound2-data   1.2.4-1   
  all  Configuration fil>
ii  libatopology2:amd64   1.2.4-1   
  amd64shared library fo>

Downgrading to…

ii  libasound2:amd64  1.2.3.2-1+b1  
  amd64shared library fo>
ii  libasound2:i386   1.2.3.2-1+b1  
  i386 shared library fo>
ii  libasound2-data   1.2.3.2-1 
  all  Configuration fil>
ii  libatopology2:amd64   1.2.3.2-1+b1  
  amd64shared library fo>

… allowed this to work again, and libatopology2:amd64 (which could be
individually upgraded) quickly turned out to be unconnected. So this
is clearly something in libasound2 and/or libasound2-data.

Playing music with mpg123 _does_ work with 1.2.4-1 so this is tricky.
I’m not filing it with RC severity as it doesn’t impact “all” use, but
this is, very much, a showstopper IMHO.

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

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

Versions of packages libasound2 depends on:
ii  libasound2-data  1.2.4-1
ii  libc62.31-5

libasound2 recommends no packages.

Versions of packages libasound2 suggests:
pn  libasound2-plugins  

-- no debconf information

Bug#971631: udev: /bin/setfacl -m g:scanner:rw ' failed when USB scanner plugged in

[Jörg Frings-Fürst]

Hello,

no answer since 2 month.

Closed.


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#976894: telegram-desktop: Telegram crashes because X11 connection broke

[Chandra Sekar]

Package: telegram-desktop
Version: 2.2.0+ds-4
Severity: important
X-Debbugs-Cc: chandru...@gmail.com

Dear Maintainer,

Telegram crashes when starting up, with the below error.

$ telegram-desktop
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
error: : cannot open
error: : cannot open
error: : cannot open
The X11 connection broke (error 2). Did the X11 server die?

This crash is specific to Telegram. Other Qt applications like KeePassXC
work fine, so this doesn't seem related to wayland being ignored.

-- Package-specific info:

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

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

Versions of packages telegram-desktop depends on:
ii  libavcodec58  7:4.3.1-5
ii  libavformat58 7:4.3.1-5
ii  libavutil56   7:4.3.1-5
ii  libc6 2.31-5
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libgcc-s1 10.2.0-19
ii  libgdk-pixbuf-2.0-0   2.40.0+dfsg-8
ii  libglib2.0-0  2.66.3-2
ii  libgtk-3-03.24.23-3
ii  libhunspell-1.7-0 1.7.0-3
ii  liblz4-1  1.9.2-2
ii  liblzma5  5.2.4-1+b1
ii  libminizip1   1.1-8+b1
ii  libopenal11:1.19.1-2
ii  libopus0  1.3.1-0.1
ii  libqrcodegencpp1  1.5.0-2
ii  libqt5core5a [qtbase-abi-5-15-1]  5.15.1+dfsg-4
ii  libqt5dbus5   5.15.1+dfsg-4
ii  libqt5gui55.15.1+dfsg-4
ii  libqt5network55.15.1+dfsg-4
ii  libqt5waylandclient5 [qtwayland-client-abi-5-15-  5.15.1-3
ii  libqt5widgets55.15.1+dfsg-4
ii  librlottie0-1 0.1+dfsg-1
ii  libssl1.1 1.1.1h-1
ii  libstdc++610.2.0-19
ii  libswresample37:4.3.1-5
ii  libswscale5   7:4.3.1-5
ii  libx11-6  2:1.6.12-1
ii  libxcb-screensaver0   1.14-2
ii  libxcb1   1.14-2
ii  libxxhash00.8.0-1
ii  qt5-image-formats-plugins 5.15.1-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans  1.11-1

telegram-desktop suggests no packages.

-- no debconf information
[2020.12.09 09:48:15] Launched version: 2002000, install beta: [FALSE], alpha: 
0, debug mode: [FALSE]
[2020.12.09 09:48:15] Executable dir: /usr/bin/, name: telegram-desktop
[2020.12.09 09:48:15] Initial working dir: /home/chandru/
[2020.12.09 09:48:15] Working dir: /home/chandru/.local/share/TelegramDesktop/
[2020.12.09 09:48:15] Command line: telegram-desktop
[2020.12.09 09:48:15] Executable path before check: /usr/bin/telegram-desktop
[2020.12.09 09:48:15] Logs started
[2020.12.09 09:48:15] Launcher filename: telegramdesktop.desktop
[2020.12.09 09:48:15] Connecting local socket to 
/run/user/1000/4e80fa8db6e7ac41686aa9d18413afb2-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2020.12.09 09:48:15] Socket connect error 0, starting server and app...
[2020.12.09 09:48:15] Moved logging from 
'/home/chandru/.local/share/TelegramDesktop/log_start0.txt' to 
'/home/chandru/.local/share/TelegramDesktop/log.txt'!
[2020.12.09 09:48:15] Primary screen DPI: 96
[2020.12.09 09:48:15] App Info: reading settings...
[2020.12.09 09:48:15] App Info: reading encrypted settings...
[2020.12.09 09:48:15] Lang Info: Loaded cached, keys: 2802
[2020.12.09 09:48:15] OpenAL Logging Level: (not set)
[2020.12.09 09:48:15] Audio Playback Devices: Built-in Audio Analog Stereo
[2020.12.09 09:48:15] Audio Playback Default Device: Built-in Audio Analog 
Stereo
[2020.12.09 09:48:15] Audio Capture Devices: Built-in Audio Analog 
Stereo;Monitor of Built-in Audio Analog Stereo
[2020.12.09 09:48:15] Audio Capture Default Device: Built-in Audio Analog Stereo
[2020.12.09 09:48:15] System tray available: [FALSE]
[2020.12.09 09:48:15] Not using D-Bus global menu.
[2020.12.09 09:48:15] Not using Unity 

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[Jeff Blake]

On Tue, 08 Dec 2020 12:33:57 +0100 Michel Le Bihan  wrote:
> Hello,
> 
> I started work on updating the chromium package (you can see my work
> here:
> https://salsa.debian.org/mimi8/chromium/-/commit/af70b14701aaf6bdb34e23af01657676e27ba5d4
> ), but got stuck because `libvpx` is too old in Debian testing. It
> needs to be updated before I can continue work.
> 
> Michel Le Bihan
> 
> 
> 

I've managed to successfully update the ungoogled-chromium debian package [1], 
which is based upon 
the official debian package.

Until libvpx is updated (or a new release is made) you could use Chromium's 
bundled version of libvpx [2].

Feel free to have a look around my repo, as you might well encounter some of 
the same problems that 
I had in getting things to build.


Jeff Blake 


[1] https://github.com/berkley4/ungoogled-chromium-debian/commits/87.0.4280.88

[2] 
https://github.com/berkley4/ungoogled-chromium-debian/commit/05ffc529e685817aac8a9c5bb419daba17204a66

Bug#976799: [pkg-php-pear] Bug#976799: Please update php-doctrine-inflector autoloader’s path

[Robin Gustafsson]

Hi David,

> Looks like you’ve made a nice script to generate the autoload.php files
> for the binary packages! It would be awesome to make something like that
> part of pkg-php-tools (modulo a semi-automatic way to create the
> $autoloaders translation from the composer name to the autoloader
> path…).

Sounds good to me! I'll look into contributing an improved/generalized
version to pkg-php-tools when I find the time.

> Anyway, this bug report is about a request to change one of these paths.
> I intend to soon update php-doctrine-inflector in unstable to the
> version currently available in experimental. The autoload.php file path
> changed, so you’ll need to update the related autoload.php files on your
> side too. The following untested patch should do the trick, but I didn’t
> dig very far:
>
> https://salsa.debian.org/php-team/pear/php-laravel-framework/-/merge_requests/1

Thanks for noticing this and for providing a patch.

> Could you please test that your packages work correctly with this patch
> and the php-doctrine-inflector package from experimental? (According to
> their composer.json file, php-laravel-framework and
> php-illuminate-support should be compatible, but better safe than
> sorry).

I've tested it now and it seems to be all good.

> If all goes well, I intend to upload php-doctrine-inflector 2 to
> unstable in a few days (in sync with php-doctrine-common 3,
> php-doctrine-orm 2.8 and php-doctrine-persistence 2 as currently
> available in experimental). It would be nice to have an updated
> php-laravel-framework uploaded in sync too (at worst, it will be partly
> broken until this bug gets fixed).
> [...]
> Please, do tell if you (dis)agree with the proposed plan or timeline, I
> don’t mind also adapting to your needs.

I'm fine with this. My ability to sync the upload is limited though as
I cannot upload packages myself. If you have the time, you could
upload this change too of course. I assume you don't though, in which
case I'll fix the breakage afterwards as soon as I can get the upload
sponsored.

Regards,
Robin

Bug#976123: (no subject)

[Christopher Chavez]

I want to agree with the reporter that U-Boot USB detection is unreliable, at 
least for certain hardware. However the reporter probably needs to be more 
specific about any messages displayed or if/where U-Boot is stuck, and what 
devices are affected (USB vendor and device IDs).

In my case I am using U-Boot from recent openSUSE on Raspberry Pi 3 Model B, 
and certain USB PATA bridges such as 0c0b:b311 initially fail to be detected 
("usb_new_device: Cannot read configuration, skipping device 0c0b:b311"). The 
workaround I use at the moment is to enter `usb reset` at the command prompt 
until the drive is detected, and then I can `boot` into GRUB2.

Bug#976845: wxpython-tools needs source upload for Python 3.9 transition

[Scott Talbert]

On Tue, 8 Dec 2020, Adrian Bunk wrote:


In a more general note, do the tools have to use
the versioned interpreter instead of python3?


They probably don't.  The tools are really just setuptools entry point 
scripts.  The dependency is just coming from the shebang in those scripts 
I believe.


Scott

Bug#976888: snapper: Snapper does not create snapshots on systems with sysv init

[Alex]

Package: snapper
Version: 0.8.14-1
Severity: important

Dear Maintainer,
snapper seems not to ship the neccessary scripts to run on systems with
sysv init. It installs .timer units for systemd, but probably requires
cron.d scripts on systems with sysvinit, which seem to be missing.

(The attached system information is from a system that booted with systemd
and has a working snapper, but still does not have sysv scripts installed.
The problem occurs on a debian buster system with sysvinit-core
installed)

with kind regards,
Alex


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

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

Versions of packages snapper depends on:
ii  libboost-thread1.71.0  1.71.0-7+b1
ii  libc6  2.31-5
ii  libdbus-1-31.12.20-1
ii  libgcc-s1  10.2.0-19
ii  libmount1  2.36.1-2
ii  libsnapper50.8.14-1
ii  libstdc++6 10.2.0-19

snapper recommends no packages.

snapper suggests no packages.

-- Configuration Files:
/etc/default/snapper changed [not included]

-- no debconf information

Bug#976886: movim: Blocking transition of php-illuminate-database

[Robin Gustafsson]

Package: movim
Version: 0.17.1-1
Severity: normal

Dear Maintainer,

A recent upload of mine triggered a transition [1] involving movim. The
cause is movim's upper limit on the version of php-illuminate-database,
which disallows version 6.x.

The current version of movim already has support for the new version of
php-illuminate-database upstream, but I see that it has been patched [2]
to instead depend on the version that has been in Debian so far.

Please revert the relevant part of the patch to resolve the issue. If
you don't have the time/resources/energy for this in the near future,
let me know and I'll try to arrange a NMU.

Sorry for the lack of advance notice. I ensured that movim had support
for the new version, but I failed to account for the patch.

[1] 
https://release.debian.org/transitions/html/auto-upperlimit-php-illuminate-database.html
[2] 
https://salsa.debian.org/xmpp-team/movim/-/blob/master/debian/patches/composer-versions.diff#L28

Regards,
Robin

Bug#976893: ITP: upstream-ontologist -- discover information about upstream software projects

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij 
X-Debbugs-Cc: debian-de...@lists.debian.org, gathers information about the 
upstream part of a package

* Package name: upstream-ontologist
  Version : 0.1
  Upstream Author : Jelmer Vernooij 
* URL : https://github.com/jelmer/upstream-ontologist
* License : GPL
  Programming Lang: Python
  Description : discover information about upstream software projects

The upstream ontologist gathers information about the upstream part of a
software package, by introspecting various common data files,
such as cargo files, setup.py files or dist.ini files.

(this is code currently included in lintian-brush, but being factored out)

Bug#976892: autoconf: Please package new version (2.70)

[Boyuan Yang]

Source: autoconf
Severity: important
X-Debbugs-CC: pfaff...@debian.org

The new autoconf release is now available at
http://ftp.gnu.org/gnu/autoconf/autoconf-2.70.tar.gz . Please seriously
consider testing it and have it packaged.

Regards,
Boyuan Yang


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

Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Gabriel Francisco]

Package: fastboot
Version: 1:10.0.0+r36-1~stage1.3
Severity: normal

Dear Maintainer,

I found that the latest version of fastboot packages replaces the fastboot
binary with a shell script that prints the message "fake placeholder until
fastboot builds" and then exit.

Best,
Gabriel Francisco

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

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

fastboot depends on no packages.

Versions of packages fastboot recommends:
ii  android-sdk-platform-tools  27.0.0+12

fastboot suggests no packages.

-- no debconf information

Bug#974011: xmille: Incorrect license/copyright for xmille

[Ryan Armstrong]

On 2020-12-07 12:12 p.m., Keith Packard wrote:

Adrian Bunk  writes:


On Sun, Nov 08, 2020 at 07:06:52PM -0500, Ryan Armstrong wrote:

...
I have been researching old terminal and X games recently, and realized
that much of the code from 'xmille' orignated from the terminal game
'mille', which is part of bsdgames.

Specifically, the following files are notably similar between the two
games:
comp.c
end.c
extern.c
init.c
mille.c & mille.h
misc.c
move.c
types.h
varpush.c

Many of these even contain telltale BSD version/date comments, even a
few not listed above that are common but extensively re-written.
However, all of the original source files contain the 3-term BSD
license, as follows:
...
This has been stripped out of all code in the xmille distribution.
Also, none of the included materials give credit to the original author,
Ken Arnold.

I'm not sure what the best solution is, exactly. Extensively patch the
source until it complies with the BSD license again?

Presumably, the copyright file needs to change at the very least.
...

Keith, do you remember the copyright history of this code?

I may have copied the underlying mille sources *before* copyrights were
added to each file; I started work on the X10 version of xmille around
1985 or 1986. I guess I could have mistakenly removed them? Thanks for
discovering this error; I can fix these "upstream" and publish a new
version?


I just did a bit of digging, since I previously had a 2.11 BSD VM set up 
in SIMH (fun!). It looks like the version of mille in that release was 
indeed from about the 1985/1986 time frame, and the copyright headers 
were not yet added. So that makes much more sense then removing them.


I guess the question becomes, would they still require a change in 
copyright status, or is the previous status correct?


Also, should a credit for Ken Arnold be added?

Ryan

Bug#976884: UDD: encoding issue in bug titles

[Felix Lechner]

Hi,

> â\u0080\u0098class

I had a very similar issue in Lintian's database a few weeks ago. It
was caused by uploading (properly UTF-8 encoded) JSON to Postgres. The
Perl driver DBD::Pg encoded the data again and picked the 7-bit clean
escape sequences according to RFC4627, which is what I believe you are
seeing. They are further described here:

https://metacpan.org/pod/JSON::PP#ascii

My solution was to disable the automatic decoding layer in DBD::Pg via
'pg_enable_utf8 => 0'. It mirrors how I handle encoding elsewhere
(i.e. explicitly and without PerlIO, Bug#972878) and works great, but
did not enjoy much support on IRC in either the Perl or the Postgres
communities..

Kind regards
Felix Lechner

Bug#976803: mrpt uses private binutils shared library

[José Luis Blanco-Claraco]

Hi Matthias:

I'm curious about the rationale of not using libbinutils as shared
libraries... sorry if this seems a stupid question!

The dependency was added in this last version to enable using BFD to
find debug info in binaries and expose that in the upstream library
functionality.

Cheers,
JL

On Tue, Dec 8, 2020 at 7:51 AM Matthias Klose  wrote:
>
> Package: src:mrpt
> Version: 1:2.1.5-1
> Severity: serious
> Tags: sid bullseye
>
> mrpt uses private binutils shared libraries:
>
> Package: libmrpt-core2.1
> Depends: libbinutils (>= 2.35.1), libbinutils (<< 2.35.2), [...]
>
> Please don't do this. Either disable the use of these libraries, or
> link these statically and add a Built-Using attribute to the binary package.



-- 

/**
 * Jose Luis Blanco-Claraco
 * Universidad de Almería - Departamento de Ingeniería
 * [Homepage]( https://w3.ual.es/~jlblanco/ )
 * [GH profile]( https://github.com/jlblancoc )
 */

Bug#976889: classpath-contains-relative-path is a false-positive for libX-clojure packages

[Louis-Philippe Véronneau]

On 2020-12-08 19 h 26, Felix Lechner wrote:
> Hi Louis-Philippe,
> 
> On Tue, Dec 8, 2020 at 3:33 PM Louis-Philippe Véronneau
>  wrote:
>>
>> It seems that when packaging a Clojure package that also has a
>> d/libX-clojure.classpath file, the "classpath-contains-relative-path"
>> tag is emitted.
> 
> In order to investigate your filing, we require a package reference
> (or a pointer to temporary build artifacts, for example on Salsa).
> Will you please provide additional details to help us? Thank you!

You can have a look at src:core-async-clojure 1.3.610-2 (currently in
incoming.d.o). Sadly, the Salsa repo [1] doesn't use Salsa-CI.

[1]: https://salsa.debian.org/clojure-team/core-async-clojure

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#964284: guile-gnutls: update to use guile 3.0

[Rob Browning]

Ludovic Courtès  writes:

> It looks as though the public or private key were corrupt, but nothing
> obvious.
>
> Unfortunately, there doesn’t seem to be a similar test case in C.  The
> closest one is ‘tls12-rehandshake-cert-auto’, but it uses anonymous
> certificates and different priority strings.
>
> Ideas for further debugging would be welcome!

Hmm, I know almost nothing about gnutls (or even, yet, this particular
test), but I wondered (in general) how hard it might be to create a C
level test that does the same thing.  If it's easy, might be worth a
try.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#976889: classpath-contains-relative-path is a false-positive for libX-clojure packages

[Felix Lechner]

Hi Louis-Philippe,

On Tue, Dec 8, 2020 at 3:33 PM Louis-Philippe Véronneau
 wrote:
>
> It seems that when packaging a Clojure package that also has a
> d/libX-clojure.classpath file, the "classpath-contains-relative-path"
> tag is emitted.

In order to investigate your filing, we require a package reference
(or a pointer to temporary build artifacts, for example on Salsa).
Will you please provide additional details to help us? Thank you!

Kind regards
Felix Lechner

Bug#976815: [pkg-php-pear] Bug#976815: php-monolog: FTBFS: ReflectionException: Class Egulias\EmailValidator\EmailValidator does not exist

[Robin Gustafsson]

Control: tags -1 patch

This can be fixed by using SwiftMailer's new autoloader. That one will
also load its dependencies.

I have submitted a MR for this on Salsa [1].

[1] https://salsa.debian.org/php-team/pear/php-monolog/-/merge_requests/1

Bug#976868: libelogind-dev: does not provide libsystemd-dev

[Maxim Chintalov]

Package: libelogind-dev
Version: 243.7-1+debian1
Severity: normal
X-Debbugs-Cc: maximchinta...@mail.ru

Dear Maintainer,

I am attempting to install libgnome-desktop-3-dev, which has a dependency on 
libsystemd-dev, but it ended in APT error. Although libelogind0 provides 
libsystemd0, libelogind-dev is not providing libsystemd-dev.

Please add Provides: libsystemd-dev to control.


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

Kernel: Linux 5.9.0-12.1-liquorix-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages libelogind-dev depends on:
ii  libelogind0  243.7-1+debian1

libelogind-dev recommends no packages.

Versions of packages libelogind-dev suggests:
pn  libelogind-dev-doc  

-- no debconf information

Bug#966395: Any plans on doing this for Bullseye?

[Luigi Gangitano]

Hi Amos,

Can you please tell me more about the technicalities needed to support libssl1? 
I would like to make a plan for finally enable SSL/TLS in squid, if possible.

Cheers,

L

--
Luigi Gangitano -- mailto:lu...@debian.org>> -- 
mailto:gangit...@lugroma3.org>>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26
GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5  0F6D 0284 F20C 2BA9 7CED

> On 5 Dec 2020, at 07:47, Amos Jeffries  wrote:
> 
> On 2/12/20 10:36 pm, Santiago Garcia Mantinan wrote:
>> I'd like to know if there are any plans on having Bullseye version compiled
>> with --with-openssl,
> 
> 
> I am leaving the decision to Luigi for libssl1 builds.
> 
> 
> For my part I will only add it for libssl3 or later where we do not have to 
> rely on a technicality. The upstream work still needs some help testing 
> changes against libssl 1.1.
> 
> 
> Amos
> 

Bug#976808: d-i Alpha 3 seems unusable for qemu-system-aarch64

[Ryutaroh Matsumoto]

> So maybe there should be message "Debian is for SBC, please use
> $OTHER_DISTRO for servers/etc" on d-i website?

Debian Bullseye arm64 disk image for ACPI systems
can be built on an amd64/arm64 Debian host  by mmdebstrap
(or probably qemu-debootstrap) and grub-install in grub-efi-arm64
as I did at
https://github.com/emojifreak/qemu-arm-image-builder

"Debian is for SBC" sounds too strong...

Ryutaroh

Bug#976890: RFP: seamly2d -- pattern making program

[Bernd Zeimetz]

Package: wnpp
Severity: wishlist

* Package name: seamly2d
  Version : 0.6.0.2+20201207 (latest weekly snapshot for now ->
  target experimental)
* URL : https://github.com/FashionFreedom/Seamly2D
* License : gpl3
  Programming Lang: c++
  Description : pattern making program


 Seamly2D enables creative parametric patterns which conform to an
 individual's body measurements and to multiple sizing tables. It blends
 new technologies with traditional methods to remove Victorian-era gender,
 ethnic, and size biases from clothing design. Seamly2D is created to
 allow independent patternmakers and designers to profitably scale
 their small batch clothing production.



I've started to prepare some packaging based on upstream's work on

Vcs-Git: https://salsa.debian.org/debian/pkg-seamly2d.git
Vcs-Browser: https://salsa.debian.org/debian/pkg-seamly2d


But I'm not keen on maintaining it, I have enough packages to take care
of.


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

Bug#975727: util-linux: [util-linux] 2.36.1-1 breaks davfs mount

[Hormet Yiltiz]

I added the unstable into source list, apt update and installed util-linux by 
specifying the version from the experimental. I did not do an apt upgrade, but 
since util-linux has libmount1 dependency, I guess it might have upgraded 
libmount1 and its other dependencies to satisfy? If the new version indeed 
wants a specific version of libmount1 etc., then its .deb package should 
probably specify it so next time when I do `apt update` and `apt install 
util-linux=SOME-VERSION`, it works as intended (by the devs) along with all its 
dependencies.

Chris Hofstaedtler:

* hyiltiz  [201203 02:57]:

Package: util-linux
Version: 2.36.1-2
Followup-For: Bug #975727
X-Debbugs-Cc: hyil...@gmail.com

Just pulled to util-linux 2.36.1-2 from unstable into testing and rebooted just
to be sure, but am still seeing the same error davfs2 1.6.0-1.


What exactly did you do?

Did you update libmount1, mount, etc. as well?


ii  libmount1  2.36.1-1


Doesn't look like it?

Chris

Bug#976889: classpath-contains-relative-path is a false-positive for libX-clojure packages

[Louis-Philippe Véronneau]

Package: lintian
Version: 2.104.0
Severity: normal

Dear maintainers,

It seems that when packaging a Clojure package that also has a
d/libX-clojure.classpath file, the "classpath-contains-relative-path"
tag is emitted.

The tag's description says:

"Note, Lintian assumes that all (relative) classpaths pointing to
/usr/share/java/ (but not subdirs thereof) are satisfied by dependencies
as long as there is at least one strong libX-java dependency."

Since Clojure packages also push jars in "/usr/share/java" but aren't
named "libX-java", I'm assuming this is a false-positive.

In my opinion, this check should also take for granted classpaths are
satisfied by strong libX-clojure dependencies.

I would like to think I'll have time to submit a patch to fix this
problem this week, but if someone else wants to have a go, I certainly
won't mind.

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#892325: Bug#925638: closed by Debian FTP Masters (reply to Bernhard Schmidt ) (Bug#925638: fixed in belle-sip 4.3.1+dfsg-1)

[Michael Prokop]

Hi,

* Bernhard Schmidt [Wed Dec 09, 2020 at 12:12:20AM +0100]:

> >> Both linphone and linphone-desktop have now been updated and are
> >> currently in NEW (linphone already is, linphone-desktop should be within
> >> the next hour). Hopefully we will have them accepted soon.

> > This is great news, thanks a lot for taking care!

> > Are you planning to upload belle-sip 4.4.13+dfsg-1 towards unstable
> > or is anything else blocking this for now?

> I'd like to wait for linphone and linphone-desktop to clear the NEW
> queue. The stack is closely coupled and I don't want to have this
> transition getting stuck.

I see, thanks!

regards
-mika-


signature.asc
Description: Digital signature

Bug#976808: Bullseye arm64 d-i Alpha 3: Items cannot be selected by space

[Ryutaroh Matsumoto]

Hi Alper, thank you for paying attention.

> On that specific question, you use the arrow keys to navigate between

Neither the space bar nor arrow keys worked for me with Alpha 3...

When I tried a weekly build of d-i on November or October,
at least "v" and "^" worked,  d-i failed on "tasksel", and
the installation cannot be completed

But Alpha 3 does not seem to recognize "v" or "^" as subtitutes of arrow keys,
and the situation got worse. Ryutaroh

Bug#892325: Bug#925638: closed by Debian FTP Masters (reply to Bernhard Schmidt ) (Bug#925638: fixed in belle-sip 4.3.1+dfsg-1)

[Bernhard Schmidt]

Hi,

>> Both linphone and linphone-desktop have now been updated and are
>> currently in NEW (linphone already is, linphone-desktop should be within
>> the next hour). Hopefully we will have them accepted soon.
> 
> This is great news, thanks a lot for taking care!
> 
> Are you planning to upload belle-sip 4.4.13+dfsg-1 towards unstable
> or is anything else blocking this for now?

I'd like to wait for linphone and linphone-desktop to clear the NEW
queue. The stack is closely coupled and I don't want to have this
transition getting stuck.

Bernhard

Bug#976887: texlive-base: Should not migrate to testing for now.

[Hilmar Preusse]

Package: texlive-base
Version: 2020.20201203-2
Severity: serious

Dear Maintainer,

The new texlive-base has an impact on docbook based documentations,
see

https://bugs.debian.org/976475
https://bugs.debian.org/976508
https://bugs.debian.org/976519
https://bugs.debian.org/976535
https://bugs.debian.org/976538
https://bugs.debian.org/976544
https://bugs.debian.org/976547
https://bugs.debian.org/976554
https://bugs.debian.org/976556
https://bugs.debian.org/976574
https://bugs.debian.org/976586

Prevent it from migration to testing for now until the issue is sorted
out.

Hilmar
-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

lrwxrwxrwx 1 root root 31 Dec  4 20:07 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Dec  2 00:27 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Dec  4 20:07 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Dec  4 20:07 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3342 Dec  7 08:36 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Nov 10  2008 mktex.cnf
-rw-r--r-- 1 root root 475 Dec  2 00:27 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 5.9.0-4-686-pae (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libpaper-utils 1.1.28+b1
ii  sensible-utils 0.0.12+nmu1
ii  tex-common 6.15
ii  texlive-binaries   2020.20200327.54578-5
ii  ucf3.0043
ii  xdg-utils  1.1.3-2

Versions of packages texlive-base recommends:
pn  lmodern  

Versions of packages texlive-base suggests:
ii  ghostscript [postscript-viewer]  9.53.3~dfsg-5
ii  gv [postscript-viewer]   1:3.7.4-2
ii  perl-tk  1:804.035-0.1+b1
ii  xpdf [pdf-viewer]3.04-13
pn  xzdec

Versions of packages tex-common depends on:
ii  dpkg  1.20.5
ii  ucf   3.0043

Versions of packages tex-common suggests:
ii  debhelper  13.3

Versions of packages texlive-base is related to:
ii  tex-common6.15
ii  texlive-binaries  2020.20200327.54578-5

-- debconf information:
  tex-common/check_texmf_missing:
  tex-common/check_texmf_wrong:
* texlive-base/binary_chooser: pdftex, dvips, dvipdfmx, xdvi
  texlive-base/texconfig_ignorant:

Bug#892325: Bug#925638: closed by Debian FTP Masters (reply to Bernhard Schmidt ) (Bug#925638: fixed in belle-sip 4.3.1+dfsg-1)

[Michael Prokop]

Hi Bernhard,

* Bernhard Schmidt [Tue Dec 08, 2020 at 11:12:58PM +0100]:
> Am 04.12.20 um 23:45 schrieb Bernhard Schmidt:
> > Am 04.12.20 um 19:23 schrieb Bernhard Schmidt:

> >>> belle-sip is currently missing in Debian/testing AKA bullseye
> >>> because of this issue (which is only fixed in experimental yet):

[...]
> > The code is at
> > https://salsa.debian.org/pkg-voip-team/linphone-stack/linphone-desktop .
> > Together with the packages already in experimental this COULD work. I
> > can't test right now because I'm running out of time and I am sitting in
> > front of a stable system, so no easy way to run experimental.

> > Anyone willing to take a look?

> Both linphone and linphone-desktop have now been updated and are
> currently in NEW (linphone already is, linphone-desktop should be within
> the next hour). Hopefully we will have them accepted soon.

This is great news, thanks a lot for taking care!

Are you planning to upload belle-sip 4.4.13+dfsg-1 towards unstable
or is anything else blocking this for now?

regards
-mika-


signature.asc
Description: Digital signature

Bug#976885: RFS: sayonara/1.6.0~beta6-1 [ITP] -- Small and lightweight music player

[SteveM]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

Sayonara is a small, clear and fast audio player for Linux written in C++ and 
supported by the Qt framework.

 * Package name : sayonara
   Version   : 1.6.0~beta6-1
   Upstream Author : Michael Lugmair 
 * URL: https://sayonara-player.com
 * License  : GPLv3
 * Vcs : 
https://gitlab.com/luciocarreras/sayonara-player/
   Section   : sound

It builds those binary packages:
  sayonara -  Launches the GUI player
  sayonara-ctl- CLI, Sends commands to the GUI (eg. play, pause)
  sayonara-query  - CLI, Get information about the music being played (eg. 
artist, album)


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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/sayonara/sayonara_1.6.0~beta6-1.dsc

Changes since the last upload:

* Initial release (Closes: #854408)


This package was [ITP] earlier in the year but did not complete (bug 950824). I 
have the go ahead from Ko Ko Ye` to continue his work and have attempted to get 
sponsorship from Boyuan Yang but have not heard back from him so I am assuming 
that he is too busy and I need to find another person to sponsor sayonara.

Regards,
--
  Steve Meliza

Bug#840336: elpa-markdown-mode: Freezes Emacs when using TeX input mode in a header

[Christophe Troestler]

I can no longer reproduce this bug either (I'm using Emacs 27.1 now).

Regards,
C.


On  8 December 2020 at 15:23 CET, Nicholas D Steeves  wrote:
>
> Control: tags -1 = unreproducible
> Control: fixed -1 markdown-mode/2.3+154-2
>
> Hi Christophe,
>
> I was unable reproduce the issue on sid with emacs 1:27.1+1-3 and
> elpa-markdown-mode 2.4-1.
>
> This bug looks safe to close now, but I'll leave it open for six months
> on the off chance a new trigger can be identified.
>
> Regards,
> Nicholas

Bug#976352: transition: libjsoncpp

[Gianfranco Costamagna]

Hello,
On Tue, 8 Dec 2020 23:13:07 +0100 Sebastian Ramacher  
wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-libjsoncpp.html
> Control: tags -1 + confirmed
> 
> On 2020-12-08 23:04:05 +0100, Gianfranco Costamagna wrote:
> > Hello again
> > 
> > polybar is now ok too, because of the xcb-proto fix
> > 
> > remaining failures are down to 4, only one without patch and one out from 
> > testing.
> > 
> > kopanocore  fail (unrelated: #969297)
> > libseqlib   fail (#976414) forwarded upstream that might be 
> > easily patchable
> > spring  fail (#976452 with patch)
> > springlobby fail (#976451 with patch)
> 
> Please go ahead.
> 

done thanks!

G.

Bug#976704: po4a: Missing dependency on libpod-parser-perl

[Martin Quinson]

Hello Helge,

it seems to me that this is an upstream bug that you will never encounter when 
using the Debian package (neither source nor binary). Do you agree?

Thanks for reporting,
Mt 

- Le 7 Déc 20, à 9:24, Helge Kreutzmann deb...@helgefjell.de a écrit :

> Package: po4a
> Version: 0.61-1
> Severity: important
> 
> Trying to build po4a upstream itself (with po4 installed by Debian)
> fails with:
> 
> helge@samd:/tmp/po4a-doc$ LC_ALL=C ./Build
> Created META.yml and META.json
> Discard blib/man/ca/man1/po4a-display-man.xml (6 of 24 strings; only 25%
> translated; need 80%).
> Discard blib/man/ca/man1/po4a-display-pod.xml (6 of 23 strings; only 26.08%
> translated; need 80%).
> Unknown format type: pod.
> po4a::chooser: Module loading error: Can't locate Pod/Parser.pm in @INC (you 
> may
> need to install the Pod::Parser module) (@INC contains: lib /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.32.0 /usr/local/share/perl/5.32.0
>   /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5
>   /usr/lib/x86_64-linux-gnu/perl-base 
> /usr/lib/x86_64-linux-gnu/perl/5.32
>   /usr/share/perl/5.32 /usr/local/lib/site_perl) at 
> lib/Locale/Po4a/Pod.pm line
>   14.
>   BEGIN failed--compilation aborted at lib/Locale/Po4a/Pod.pm 
> line 14.
>   Compilation failed in require at (eval 39) line 1.
>   BEGIN failed--compilation aborted at (eval 39) line 1.
> 
> List of valid formats:
>  - asciidoc: AsciiDoc format.
>  - dia: uncompressed Dia diagrams.
>  - docbook: DocBook XML.
>  - guide: Gentoo Linux's XML documentation format.
>  - ini: INI format.
>  - kernelhelp: Help messages of each kernel compilation option.
>  - latex: LaTeX format.
>  - man: Good old manual page format.
>  - pod: Perl Online Documentation format.
>  - rubydoc: Ruby Documentation (RD) format.
>  - sgml: either DebianDoc or DocBook DTD.
>  - texinfo: The info page format.
>  - tex: generic TeX documents (see also latex).
>  - text: simple text document.
>  - wml: WML documents.
>  - xhtml: XHTML documents.
>  - xml: generic XML documents (see also docbook).
>  - yaml: YAML documents.
> Died at Po4aBuilder.pm line 184.
> 
> 
> After installing libpod-parser-perl, the build suceedes.
> 
> Please note that the information below, that po4a depends on
> libpod-parser-perl is incorrect:
> root@samd:~# LC_ALL=C apt-get remove libpod-parser-perl
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>  libpod-parser-perl
> 0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
> After this operation, 260 kB disk space will be freed.
> Do you want to continue? [Y/n]
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>  APT prefers testing
>  APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL
> set to de_DE.UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages po4a depends on:
> ii  gettext 0.19.8.1-10
> ii  libpod-parser-perl  1.63-2
> ii  libsgmls-perl   1.03ii-36
> ii  libyaml-tiny-perl   1.73-1
> ii  opensp  1.5.2-13+b1
> ii  perl5.32.0-5
> ii  perl-modules-5.22 [libpod-parser-perl]  5.22.2-5
> 
> Versions of packages po4a recommends:
> ii  liblocale-gettext-perl 1.07-4+b1
> ii  libterm-readkey-perl   2.38-1+b2
> ii  libtext-wrapi18n-perl  0.06-9
> ii  libunicode-linebreak-perl  0.0.20190101-1+b3
> 
> po4a suggests no packages.
> 
> -- no debconf information
> 
> --
>  Dr. Helge Kreutzmann deb...@helgefjell.de
>   Dipl.-Phys.   http://www.helgefjell.de/debian.php
>64bit GNU powered gpg signed mail preferred
>Help keep free software "libre": http://www.ffii.de/

Bug#976101: systemd: Offline update installation in systemd (via gnome-update) doesn't cleanly unmount filesystem

[Michael Biebl]

Control: reassign -1 fwupd
Control: retitle -1 fwupdtool keeps / fs busy on shutdown/reboot

Am 08.12.20 um 21:05 schrieb Michael Biebl:

Am 08.12.20 um 20:39 schrieb Josh Jones:

Amazing, that has taught me something very useful!

shutdown-log.txt attached and error is visible!



Thanks.
So from a quick glance it seems fwupd keeps your / busy and prevents it 
from being remounted ro.



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953679 looks related

If you don't have a system/BIOS vendor supported by fwupd, you might 
consider purging the package to verify that the problem is solved.


Given the existing information, I'm going to reassign this to fwupd


Regards,
Michael

Bug#938927: #938927: patch available

[Markus Koschany]

Control: block 941480 by -1

Hi,

On Thu, 5 Sep 2019 18:30:33 +0300 mer...@debian.org wrote:
> control: tags -1 + patch
> 
> Hello,
> 
> Please find attached a patch to build libthrift-java.
> 
> Best wishes,
> Andrius


What is the status of this bug report? I also need libthrift-java for packaging
a newer version of mediathekview. 

Regards,

Markus


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

Bug#925775: mediastreamer2: ftbfs with GCC-9

[Bernhard Schmidt]

Am 06.12.20 um 21:33 schrieb Paul Gevers:

Hi Paul,

> On Wed, 27 Mar 2019 19:47:03 + Matthias Klose  wrote:
>> The package fails to build in a test rebuild on at least amd64 with
>> gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
>> severity of this report will be raised before the bullseye release,
>> so nothing has to be done for the buster release.
> 
> Do you intent to fix this in unstable soon too? The freeze is getting
> closer and we'd like to have this fixed in bullseye too.

Yes, sorry about that.

The whole linphone stack has to be updated at once. I have staged the
latest upstream releases in experimental. As soon as linphone and
linphone-desktop clear the NEW queue I think we are ready. The
transition is mostly self-contained and should be easy.

Bernhard

Bug#976352: transition: libjsoncpp

[Sebastian Ramacher]

Control: forwarded -1 
https://release.debian.org/transitions/html/auto-libjsoncpp.html
Control: tags -1 + confirmed

On 2020-12-08 23:04:05 +0100, Gianfranco Costamagna wrote:
> Hello again
> 
> polybar is now ok too, because of the xcb-proto fix
> 
> remaining failures are down to 4, only one without patch and one out from 
> testing.
> 
> kopanocore  fail (unrelated: #969297)
> libseqlib   fail (#976414) forwarded upstream that might be 
> easily patchable
> spring  fail (#976452 with patch)
> springlobby fail (#976451 with patch)

Please go ahead.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#892325: Bug#925638: closed by Debian FTP Masters (reply to Bernhard Schmidt ) (Bug#925638: fixed in belle-sip 4.3.1+dfsg-1)

[Bernhard Schmidt]

Am 04.12.20 um 23:45 schrieb Bernhard Schmidt:
> Hi,
> 
> 
> Am 04.12.20 um 19:23 schrieb Bernhard Schmidt:
>> Dear Mika,
>>
>>> belle-sip is currently missing in Debian/testing AKA bullseye
>>> because of this issue (which is only fixed in experimental yet):
>>>
>>> | Migration status for belle-sip (- to 1.6.3-5): BLOCKED: Rejected/violates 
>>> migration policy/introduces a regression
>>> | Issues preventing migration:
>>> | Updating belle-sip introduces new bugs: #925638.
>>>
>>> I'm aware that "This package will soon be part of the auto-belle-sip
>>> transition", but given that the bullseye freeze is coming closer,
>>> I'm just wondering if there are any plans to upload belle-sip
>>> v4.3.1+dfsg-1 towards unstable and whether we might see it in
>>> bullseye?
>>
>> yes, I have been dragging this far too long, sorry :-(
>>
>> The problem is, the whole linphone library stack is ready, but I did not
>> manage yet to build a package for linphone(-desktop), the Qt successor
>> of the old Gtk client in src:linphone. The build system is weird, with a
>> lot of fiddling I can get it to build something, but it is installed in
>> weird paths relative to the buildpath and I cannot figure out why. Nor
>> have I managed to workaround this.
> 
> I have sat down and did another stab at it. The repositories for
> OpenSuSE and Arch Linux were very helpful to find the necessary
> settings, but it still looks messy.
> 
> The code is at
> https://salsa.debian.org/pkg-voip-team/linphone-stack/linphone-desktop .
> Together with the packages already in experimental this COULD work. I
> can't test right now because I'm running out of time and I am sitting in
> front of a stable system, so no easy way to run experimental.
> 
> Anyone willing to take a look?

Both linphone and linphone-desktop have now been updated and are
currently in NEW (linphone already is, linphone-desktop should be within
the next hour). Hopefully we will have them accepted soon.

Bernhard

Bug#976868: libelogind-dev: does not provide libsystemd-dev

[Mark Hindley]

Control: tags -1 wontfix

Maxim,

Thanks for this.

On Tue, Dec 08, 2020 at 08:00:53PM +, Maxim Chintalov wrote:
> Package: libelogind-dev
> Version: 243.7-1+debian1
> Severity: normal
> X-Debbugs-Cc: maximchinta...@mail.ru
> 
> Dear Maintainer,
> 
> I am attempting to install libgnome-desktop-3-dev, which has a dependency on
> libsystemd-dev, but it ended in APT error. Although libelogind0 provides
> libsystemd0, libelogind-dev is not providing libsystemd-dev.

As Thorsten has already suggested, this is by design. Debian packages are only
built against libsystemd-dev. The libelogind0/libsystemd0 compatibility is a
*runtime* option, not compile-time. We don't even know (and can't test) if all
of the source packages depending on libsystemd-dev will compile against
libelogind-dev.

> Please add Provides: libsystemd-dev to control.

This would be both unwise and counter-productive. Having libelogind0 provide
libsystemd0 was a very controversial move and getting it accepted into Bullseye
a hard won victory. I am very reluctant to do anything that might jeopardise
that.

If you have an libelogind0 system and need to compile against libsystemd-dev,
please use one of the various build chroots or containers. This requirement is
already documented in libelogind0's README.Debian.

I propose to tag this wontfix, but leave it open to document the issue.

I hope that is acceptable.

Best wishes

Mark

Bug#976352: transition: libjsoncpp

[Gianfranco Costamagna]

Hello again

polybar is now ok too, because of the xcb-proto fix

remaining failures are down to 4, only one without patch and one out from 
testing.

kopanocore  fail (unrelated: #969297)
libseqlib   fail (#976414) forwarded upstream that might be easily 
patchable
spring  fail (#976452 with patch)
springlobby fail (#976451 with patch)

G.

Bug#976884: UDD: encoding issue in bug titles

[Lucas Nussbaum]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: udd

19:36 < jcristau> looks like something's messing up my bug title in 
  
https://buildd.debian.org/status/package.php?p=firefox=sid
20:14 < bunk> string sanitizing to prevent exploits through bug titles?
20:34 < aurel32> that or encoding issues
20:34 < aurel32> it's taken from udd
20:38 < aurel32> and there is the same issue in udd, at least in the web 
interface
21:16 < aurel32> and udd returns:  976731 | firefox: FTBFS on arm64 (explicit 
specialization 
 in non-namespace scope â\u0080\u0098class 
 js::wasm::BaseRegAllocâ\u0080\u0099)
21:19 < aurel32> so this just looks like a UDD issue when importing the data

Bug#976883: ITP: python-vttlib -- extract VTT (Microsoft Visual TrueType) font hinting data

[Romain Porte]

Package: wnpp
Severity: wishlist
Owner: Romain Porte 
X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org,
 debian-fo...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: python-vttlib
  Version : 0.9.1
  Upstream Author : Nikolaus Waxweiler 
* URL : https://github.com/daltonmaag/vttLib
* License : MIT
  Programming Lang: Python
  Description : extract VTT (Microsoft Visual TrueType) font hinting data

A library to:
- Extract VTT hinting data from a OpenType font prepared with Microsoft Visual
  TrueType (VTT) and store it in a FontTools TTX dump
- Merge it back from a TTX dump into an OpenType font and
- Compile the data inside to font to ship it (turn TSI* tables into fpgm,
  etc.).

The primary use case is version control of hinting data of fonts.

This package is introduced as a dependency for python-gftools package. I
intent to maintain this package under the umbrella of the debian-python
team.


signature.asc
Description: PGP signature

Bug#976585: libcereal: FTBFS: writer.h:430:67: error: comparison is always true due to limited range of data type [-Werror=type-limits]

[Lucas Nussbaum]

Hi,

On 08/12/20 at 19:16 +0100, Andreas Tille wrote:
> Control: severity -1 important
> Control: tags -1 confirmed
> 
> > This package only builds Arch:all binary packages. ...
> 
> Thus I'm decreasing its severity.
> 
> I was able to reproduce the issue on my pinebook64 and will try to
> forward the issue upstream.

For your information, it also fails on ppc64.

I wonder if this package is broken everywhere except on amd64. It could
be interesting to upload a Arch:any package to experimental just to
assess the damage.

Lucas

Bug#959138: Error in build time tests (Was: numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators')

[Andreas Tille]

Control: forwarded -1 https://github.com/nipy/nipy/issues/466

Bug#976867: [Pkg-rust-maintainers] Bug#976867: RUSTSEC-2020-0077: memmap: memmap is unmaintained

[Sylvestre Ledru]

Le 08/12/2020 à 21:59, Moritz Mühlenhoff a écrit :

On Tue, Dec 08, 2020 at 09:10:22PM +0100, Sylvestre Ledru wrote:

Could you please explain why you set the severity as important?
AFAIK, there isn't a security exploit. Not in the binary shipping in Debian 
either.

It was important enough to get published with the RUSTSEC advisory flow.


Not sure what you mean: Rustsec doesn't say much.

The crate is still available and published here: 
https://crates.io/crates/memmap with a lot of daily usage.






The fact that it is unmaintained upstream isn't a blocker on the Debian side 
AFAIK.

Is anyone in the Rust maintainers able/willing to step in with an upstream fix
in case there's a security issue in rust-memmap occurs?
With BurntSushi as comaintainer, I am not worried that he will step in 
case it happens:


https://github.com/danburkert/memmap-rs/issues/90#issuecomment-737587767


If so, feel free to close
it.


ok, thanks, will do.


S

Bug#959138: Error in build time tests (Was: numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators')

[Yaroslav Halchenko]

FWIW those were reported "upstream"
https://github.com/nipy/nipy/issues/466

unfortunately I had no time to look at them (again :-/)
On Tue, 08 Dec 2020, Andreas Tille wrote:

> Control: tags -1 pending
> Control: tags -1 help

> Hi,

> I've updated nipy Git[1] to version 0.4.3~rc1 which solves the
> originally reported issue.  However, there are some remaining failures
> in the build time test:

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik

Bug#976882: osmo-bsc: possible null pointer dereferences

[Steve Langasek]

Package: osmo-bsc
Version: 1.3.0-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear maintainers,

As in bug #976866, osmo-bsc is failing to build fro source on s390x in
Ubuntu, because the compiler detects that certain pointer dereferences may
be acting on a null pointer:

[...]
In file included from /usr/include/osmocom/core/msgb.h:24,
 from /usr/include/osmocom/gsm/tlv.h:6,
 from /usr/include/osmocom/gsm/gsm48.h:7,
 from bsc_subscriber.c:29:
bsc_subscriber.c: In function ‘bsc_subscr_find_or_create_by_imsi’:
bsc_subscriber.c:132:18: error: potential null pointer dereference 
[-Werror=null-dereference]
  132 |  OSMO_ASSERT(bsub->use_count < INT_MAX);
  |  ^~~
cc1: some warnings being treated as errors
[...]

  (https://launchpad.net/ubuntu/+source/osmo-bsc/1.3.0-3/+build/20177922)

I haven't looked into why this build failure doesn't happen on other archs,
or why it wasn't seen on s390x in Debian; but I've confirmed that the
compiler's errors are correct.

In addition, while investigating this I found some errors from the compiler
due to possible snprintf truncation.  As far as I can see the right solution
here is to suppress that error.

The attached patch avoids the possible null-pointer dereferences and lets
the package build.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru osmo-bsc-1.3.0/debian/patches/no-null-pointer-derefence.patch 
osmo-bsc-1.3.0/debian/patches/no-null-pointer-derefence.patch
--- osmo-bsc-1.3.0/debian/patches/no-null-pointer-derefence.patch   
1969-12-31 16:00:00.0 -0800
+++ osmo-bsc-1.3.0/debian/patches/no-null-pointer-derefence.patch   
2020-12-08 13:15:17.0 -0800
@@ -0,0 +1,30 @@
+Description: avoid possible null dereferences
+ Detected by the compiler on Ubuntu s390x
+Author: Steve Langasek 
+Last-Update: 2020-12-08
+
+Index: osmo-bsc-1.3.0/include/osmocom/bsc/gsm_data.h
+===
+--- osmo-bsc-1.3.0.orig/include/osmocom/bsc/gsm_data.h
 osmo-bsc-1.3.0/include/osmocom/bsc/gsm_data.h
+@@ -1026,6 +1026,8 @@
+ 
+ static inline char *gsm_lchan_name(const struct gsm_lchan *lchan)
+ {
++  if (!lchan)
++  return NULL;
+   return lchan->name;
+ }
+ 
+Index: osmo-bsc-1.3.0/src/osmo-bsc/bsc_subscriber.c
+===
+--- osmo-bsc-1.3.0.orig/src/osmo-bsc/bsc_subscriber.c
 osmo-bsc-1.3.0/src/osmo-bsc/bsc_subscriber.c
+@@ -129,6 +129,7 @@
+ struct bsc_subscr *_bsc_subscr_get(struct bsc_subscr *bsub,
+  const char *file, int line)
+ {
++  OSMO_ASSERT(bsub != NULL);
+   OSMO_ASSERT(bsub->use_count < INT_MAX);
+   bsub->use_count++;
+   LOGPSRC(DREF, LOGL_DEBUG, file, line,
diff -Nru osmo-bsc-1.3.0/debian/patches/series 
osmo-bsc-1.3.0/debian/patches/series
--- osmo-bsc-1.3.0/debian/patches/series2020-08-09 10:28:26.0 
-0700
+++ osmo-bsc-1.3.0/debian/patches/series2020-12-08 12:59:17.0 
-0800
@@ -2,3 +2,4 @@
 0002-Fix-one-struct-for-big-endian-archs.patch
 0003-Hack-in-test-suite-at-the-right-place-to-make-it-pas.patch
 gcc10.patch
+no-null-pointer-derefence.patch
diff -Nru osmo-bsc-1.3.0/debian/rules osmo-bsc-1.3.0/debian/rules
--- osmo-bsc-1.3.0/debian/rules 2018-11-15 12:41:35.0 -0800
+++ osmo-bsc-1.3.0/debian/rules 2020-12-08 13:08:39.0 -0800
@@ -6,6 +6,8 @@
 
 CHANGELOG_DATE ?= $(shell LC_ALL=C date -u -d @$(SOURCE_DATE_EPOCH) +"%d %B 
%Y")
 
+export DEB_CFLAGS_MAINT_APPEND = -Wno-format-truncation
+
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all

Bug#975475: package takes much more space

[duck]

Control: tags -1 +help


Quack,

I tried building with LTO but it does not work with problems similar to 
this:

  https://sourceware.org/bugzilla/show_bug.cgi?id=12762
I tried the workarounds to no avail.

I do not wish to sacrifice the hardening flags just to save some space, 
knowing that's still a small amount compared to the size of most games. 
Help welcome.


\_o<

--
Marc Dequènes

Bug#976867: [Pkg-rust-maintainers] Bug#976867: RUSTSEC-2020-0077: memmap: memmap is unmaintained

[Moritz Mühlenhoff]

On Tue, Dec 08, 2020 at 09:10:22PM +0100, Sylvestre Ledru wrote:
> Could you please explain why you set the severity as important?
> AFAIK, there isn't a security exploit. Not in the binary shipping in Debian 
> either.

It was important enough to get published with the RUSTSEC advisory flow.

> The fact that it is unmaintained upstream isn't a blocker on the Debian side 
> AFAIK.

Is anyone in the Rust maintainers able/willing to step in with an upstream fix
in case there's a security issue in rust-memmap occurs? If so, feel free to 
close
it. Otherwise work towards adapting reverse dependencies to the alternatives
listed in https://rustsec.org/advisories/RUSTSEC-2020-0077.html

Cheers,
Moritz

Bug#976868: libelogind-dev: does not provide libsystemd-dev

[Thorsten Glaser]

On Tue, 8 Dec 2020, Maxim Chintalov wrote:

> I am attempting to install libgnome-desktop-3-dev, which has a
> dependency on libsystemd-dev, but it ended in APT error. Although
> libelogind0 provides libsystemd0, libelogind-dev is not providing
> libsystemd-dev.

I think this is by design; applications are supposed to build
against the systemd headers and then, if they only use functions
also exposed by libelogind0 they can also run with that.

Normally, you only need those -dev packages in buildd chroots,
which nowadays are/can be init-less, anyway.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

Mit unserem Consulting bieten wir Unternehmen maßgeschneiderte Angebote in
Form von Beratung, Trainings sowie Workshops in den Bereichen
Softwaretechnologie, IT Strategie und Architektur, Innovation und Umsetzung
sowie Agile Organisation.

Besuchen Sie uns auf https://www.tarent.de/consulting .
Wir freuen uns auf Ihren Kontakt.

*

Bug#976881: Allow to configure compression algorithms other than GZIP

[Paul Menzel]

Package: tiny-initramfs-core
Version: 0.1-5+b10
Severity: wishlist


Dear Debian folks,


I only learned about tiny-initramfs today, when Ben Hutchings told me 
about it. What a great program! Thank you for packaging it for Debian.


On my test device, the resulting initrd is 1.3 MB big:

-rw--- 1 root root 1,3M  8. Dez 20:15 
/boot/initrd.img-5.9.0-3-amd64


The resulting boot time is 12.6 ms:

[0.199542] calling  populate_rootfs+0x0/0x109 @ 1
[0.199574] Trying to unpack rootfs image as initramfs...
[0.212449] Freeing initrd memory: 1328K
[0.212455] initcall populate_rootfs+0x0/0x109 returned 0 after 
12606 usecs


Using a different compression algorithm, can improve this even more.

For example, LZ4 is expected to increase the image size but to be much 
faster when decompressing.


Editing `/usr/sbin/mktirfs` to use `lz4 -9 -l` (copied from `mkinitramfs`)

find . ! -name . -print0 | sort -z | cpio --null -o --quiet -R 0:0 
-H newc | lz4 -9 -l >> "$image_name"


and running `sudo update-tirfs`, the initrd image size increases a 
little to 1.6 MB:


-rw--- 1 root root 1,6M  8. Dez 21:37 initrd.img-5.9.0-3-amd64

But loading and unpacking takes now only 3.6 ms:

[0.203611] calling  populate_rootfs+0x0/0x109 @ 1
[0.203638] Trying to unpack rootfs image as initramfs...
[0.207279] Freeing initrd memory: 1552K
[0.207289] initcall populate_rootfs+0x0/0x109 returned 0 after 
3588 usecs


So, it’d be really great, if the compression algorithm could be changed.


Kind regards,

Paul


PS: For the record, here is my initrd content:

```
$ lsinitramfs /boot/initrd.img-5.9.0-3-amd64
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/.enuineIntel.align.0123456789abc
kernel/x86/microcode/GenuineIntel.bin
crc16.ko
crc32c_generic.ko
crc32c-intel.ko
crct10dif_common.ko
crct10dif_generic.ko
crc-t10dif.ko
crct10dif-pclmul.ko
dev
ext4.ko
init
jbd2.ko
mbcache.ko
mmc_block.ko
mmc_core.ko
modules
nvme-core.ko
nvme.ko
proc
scsi_mod.ko
sd_mod.ko
t10-pi.ko
target
```

Bug#959138: Error in build time tests (Was: numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators')

[Andrey Rahmatullin]

On Tue, Dec 08, 2020 at 09:44:51PM +0100, Andreas Tille wrote:
> > https://github.com/nipy/nipy/issues/461
> 
> As far as I can see that's included into 0.4.3~rc1.
If by "it" you mean requiring sympy older than the Debian one then yes.
But the package evidently doesn't enforce this requirement.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#976880: transition: dtkcore

[Arun Kumar Pariyar]

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

Dear Release Team,

Please schedule a transition slot for dtkcore, the new version of dtkcore is
uploaded to experimental.
Also, I'd like to mention that dtkwidget has SONAME change.

Ben file:

title = "dtkcore and dtkwidget";
is_affected = .depends ~ "libdtkcore-bin" | .depends ~ "libdtkcore2" | .depends
~ "libdtkwidget2" | .depends ~ "libdtkcore5-bin" | .depends ~ "libdtkcore5" |
.depends ~ "libdtkwidget5-bin" | .depends ~ "libdtkwidget5";
is_good = .depends ~ "libdtkcore5-bin" | .depends ~ "libdtkcore5" | .depends ~
"libdtkwidget5-bin" | .depends ~ "libdtkwidget5";
is_bad = .depends ~ "libdtkcore-bin" | .depends ~ "libdtkcore2" | .depends ~
"libdtkwidget2";

--
Arun Kumar Pariyar

Bug#976838: librocksdb.so: missing libdl linkage

[GCS]

Control: tags -1 +confirmed

On Tue, Dec 8, 2020 at 1:39 PM Adrian Bunk  wrote:
> Package: librocksdb6.11
> Version: 6.11.4-2
[...]
> https://buildd.debian.org/status/fetch.php?pkg=rocksdb=amd64=6.11.4-2=1607384772=0
[...]
> dpkg-shlibdeps: warning: symbol dlopen used by 
> debian/librocksdb6.11/usr/lib/librocksdb.so.6.11.4 found in none of the 
> libraries
[...]
> https://buildd.debian.org/status/fetch.php?pkg=balboa=amd64=2.0.0%2Bds-3%2Bb1=1607421100=0
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -pipe -Ofast -flto -s -fwhole-program 
> -fmax-errors=3 -D__GCC__ -std=c11 -Wall -Wextra -D_GNU_SOURCE -D__TRACE__ 
> -DNDEBUG -I. -I../lib -DMPACK_HAS_CONFIG ../lib/trace.c ../lib/daemon.c 
> ../lib/protocol.c ../lib/engine.c ../lib/mpack.c rocksdb-impl.c main.c -o 
> build/balboa-rocksdb -Wl,-z,relro -Wl,-z,now -lrocksdb -pthread -latomic
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: 
> undefined reference to `dlopen'
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: 
> undefined reference to `dlclose'
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: 
> undefined reference to `dlerror'
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: 
> undefined reference to `dlsym'
> collect2: error: ld returned 1 exit status
 Strange. Build tested balboa at least twice on pbuilder with the new
rocksdb version and it was compiled correctly.
Going to look into it and fix this soon.

Regards,
Laszlo/GCS

Bug#959138: Error in build time tests (Was: numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators')

[Andreas Tille]

On Tue, Dec 08, 2020 at 11:11:27PM +0500, Andrey Rahmatullin wrote:
> https://github.com/nipy/nipy/issues/461

As far as I can see that's included into 0.4.3~rc1.  Yaroslav, would
you mind commenting on this?  It would be great to have some kind of
0.4.3~rc2 to get nipy fixed.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#936020: /var/lib/dpkg/info/sympa.prerm: 33: [: =: unexpected operator upon removal

[Paul Gevers]

Control: tags -1 pending

Hi Chris,

On Tue, 8 Dec 2020 18:23:34 +0100 Chris Halls
 wrote:
> The problem happens if there is no database configured when the prerm 
> script is invoked. I was able to trigger this on another package by 
> installing without a database (question dbconfig-install=false), and 
> then running dpkg-reconfigure on the package.
> 
> Patched attached to add the missing quotes.

Good catch (the code is only nearly 5 years old). We need to fix it in
dpkg/config too (as the text one line higher hints at).

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976879: gitlab: Missing dependency on "file" (being used in postinst script)

[Lars Kruse]

Package: gitlab
Version: 13.4.6-1~fto10+1
Severity: normal

Dear Maintainer,

there are two occurrences of "file" being called in the postinst script.

One example is the following:

> if [ "$(file /etc/gitlab/ssl/gitlab.crt|awk '{ print $NF }')" = 
> "/etc/letsencrypt/live/${GITLAB_HOST}/fullchain.pem" ]; then

Thus the gitlab package should probably depend on the "file" package.

Thank you for maintaining the gitlab package!

Cheers,
Lars

Bug#976878: apr-util FTCBFS: uses mysql_config

[Helmut Grohne]

Source: apr-util
Version: 1.6.1-5
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

apr-utils fails to cross build from source, because it uses mysql_config
and mysql_config does never work during cross compilation. A good
alternative is using pkg-config. I'm attaching an upstreamable patch to
update configure to use pkg-config. Since it uses the standard
PKG_CHECK_MODULES macro, it requires pkg.m4 from pkg-config. In
apr-util, doing so requires an appropriate sinclude directive. Very
likely, upstream would want a vendor copy of pkg.m4, which is not
included in my patch. Beyond this, pkg-config only kicks in when passing
yes to --with-mysql, otherwise it keeps using mysql_config for maximum
backwards compatibility. Please consider applying the patch.

Helmut
--- apr-util-1.6.1.orig/build/dbd.m4
+++ apr-util-1.6.1/build/dbd.m4
@@ -167,23 +167,32 @@
 
   AC_ARG_WITH([mysql], APR_HELP_STRING([--with-mysql=DIR], [enable MySQL DBD driver]),
   [
-if test "$withval" = "yes"; then
-  AC_PATH_PROG([MYSQL_CONFIG],[mysql_config])
-  if test "x$MYSQL_CONFIG" = "x"; then
-AC_PATH_PROG([MYSQL_CONFIG],[mariadb_config])
-  fi
-  if test "x$MYSQL_CONFIG" != 'x'; then
-mysql_CPPFLAGS="`$MYSQL_CONFIG --include`"
-mysql_LDFLAGS="`$MYSQL_CONFIG --libs_r | sed -e 's/-l[[^ ]]\+//g'`"
-mysql_LIBS="`$MYSQL_CONFIG --libs_r`"
+AS_IF([test "$withval" = "yes"],[
+  PKG_CHECK_MODULES([MYSQLCLIENT],[mysqlclient],[
+  APR_ADDTO(CPPFLAGS,[$MYSQLCLIENT_CFLAGS])
+  APR_ADDTO(LIBS,[$MYSQLCLIENT_LIBS])
 
-APR_ADDTO(CPPFLAGS, [$mysql_CPPFLAGS])
-APR_ADDTO(LIBS, [$mysql_LIBS])
+  if echo "$MYSQLCLIENT_LIBS" | grep -q mariadb; then
+  my_library=mariadb
+  fi
+  ],[
+AC_PATH_PROG([MYSQL_CONFIG],[mysql_config])
+if test "x$MYSQL_CONFIG" = "x"; then
+  AC_PATH_PROG([MYSQL_CONFIG],[mariadb_config])
+fi
+if test "x$MYSQL_CONFIG" != 'x'; then
+  mysql_CPPFLAGS="`$MYSQL_CONFIG --include`"
+  mysql_LDFLAGS="`$MYSQL_CONFIG --libs_r | sed -e 's/-l[[^ ]]\+//g'`"
+  mysql_LIBS="`$MYSQL_CONFIG --libs_r`"
 
-	if $MYSQL_CONFIG --libs_r | grep -q mariadb; then
-	  my_library="mariadb"
-	fi
-  fi
+  APR_ADDTO(CPPFLAGS, [$mysql_CPPFLAGS])
+  APR_ADDTO(LIBS, [$mysql_LIBS])
+
+  if $MYSQL_CONFIG --libs_r | grep -q mariadb; then
+my_library="mariadb"
+  fi
+fi
+  ])
 
   AC_CHECK_HEADERS([mysql.h errmsg.h], [apu_have_mysql=1], [apu_have_mysql=0; break])
   if test "$apr_have_mysql" = "0"; then
@@ -193,7 +202,9 @@
 	AC_CHECK_HEADERS([my_global.h my_sys.h mysql/my_global.h mysql/my_sys.h])
 	AC_CHECK_LIB($my_library, mysql_init,, [apu_have_mysql=0])
   fi
-  if test "$apu_have_mysql" = "1" && test "x$MYSQL_CONFIG" != 'x'; then
+  if test "$apu_have_mysql" = 1 && test "x$MYSQLCLIENT_CFLAGS" != x; then
+APR_ADDTO(APRUTIL_PRIV_INCLUDES, [$MYSQLCLIENT_CFLAGS])
+  elif test "$apu_have_mysql" = "1" && test "x$MYSQL_CONFIG" != 'x'; then
 	APR_ADDTO(APRUTIL_PRIV_INCLUDES, [$mysql_CPPFLAGS])
   fi
 elif test "$withval" = "no"; then
@@ -231,7 +242,7 @@
   if test "$apu_have_mysql" = "1"; then
 APR_ADDTO(APRUTIL_PRIV_INCLUDES, [$mysql_CPPFLAGS])
   fi
-fi
+])
   ])
 
   AC_SUBST(apu_have_mysql)

Bug#976877: atlc FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Source: atlc
Version: 4.6.1-4
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

atlc fails to cross build from source, because its test suite fails in
the presence of DEB_BUILD_OPTIONS=nocheck. Please consider applying the
attached patch to add support for the nocheck build option. Doing so
makes atlc cross buildable.

Helmut
diff --minimal -Nru atlc-4.6.1/debian/changelog atlc-4.6.1/debian/changelog
--- atlc-4.6.1/debian/changelog 2020-12-03 00:47:25.0 +0100
+++ atlc-4.6.1/debian/changelog 2020-12-06 14:15:13.0 +0100
@@ -1,3 +1,10 @@
+atlc (4.6.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Honour DEB_BUILD_OPTIONS=nocheck. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 06 Dec 2020 14:15:13 +0100
+
 atlc (4.6.1-4) unstable; urgency=medium
 
   * fix typo in VCS entries in control
diff --minimal -Nru atlc-4.6.1/debian/rules atlc-4.6.1/debian/rules
--- atlc-4.6.1/debian/rules 2020-12-03 00:47:25.0 +0100
+++ atlc-4.6.1/debian/rules 2020-12-06 14:15:12.0 +0100
@@ -34,7 +34,9 @@
 build-stamp:   config.status
dh_testdir
$(MAKE)
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
$(MAKE) check
+endif
touch build-stamp
 
 clean:

Bug#976876: e-mem FTCBFS: unusual compiler variable naming

[Helmut Grohne]

Source: e-mem
Version: 1.0.1-2
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

e-mem fails to cross build from source, because it uses the variable CC
to store a C++ compiler. During a cross build, dh_auto_build overrides
it with a C compiler, which fails linking e-mem. Please use standard
variables (CXX/CXXFLAGS) to make e-mem cross buildable out of the box.

Helmut
--- e-mem-1.0.1.orig/Makefile
+++ e-mem-1.0.1/Makefile
@@ -2,9 +2,9 @@
 BIN_DIR := $(CURDIR)
 endif
 
-CC= g++
+CXX   = g++
 EXEC  = e-mem
-CFLAGS   += -Wall -Wextra -Wunused -std=gnu++0x -fopenmp 
+CXXFLAGS += -Wall -Wextra -Wunused -std=gnu++0x -fopenmp 
 CDEBUG= -g -ggdb -gdwarf-3 -DDEBUG 
 CPROF= -g -ggdb -gdwarf-3 -DDEBUG -pg 
 COPTIMIZE = -Wuninitialized -O3 -fomit-frame-pointer
@@ -19,11 +19,11 @@
 CPUARCH := $(shell uname -m)
 
 ifeq ($(MAKECMDGOALS),debug)
-CFLAGS += $(CDEBUG)
+CXXFLAGS += $(CDEBUG)
 else ifeq ($(MAKECMDGOALS),profile)
-CFLAGS += $(CPROF)
+CXXFLAGS += $(CPROF)
 else
-CFLAGS += $(COPTIMIZE)
+CXXFLAGS += $(COPTIMIZE)
 endif
 
 .PHONY: all clean pack bin
@@ -36,7 +36,7 @@
 
 bin:
 	@echo :: Compiling \"$(NAME)\" \($(CPUARCH)\) ...
-	$(CC) $(CFLAGS) $(CSRCS) $(CLIBS) -o $(BIN_DIR)/$(EXEC) $(LDFLAGS)
+	$(CXX) $(CXXFLAGS) $(CSRCS) $(CLIBS) -o $(BIN_DIR)/$(EXEC) $(LDFLAGS)
 	chmod 755 $(BIN_DIR)/$(EXEC)
 	@echo :: Done
 

Bug#976875: elfutils: build profile pkg.elfutils.nodebuginfod broken

[Helmut Grohne]

Source: elfutils
Version: 0.180-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

The pkg.elfutils.nodebuginfod build profile broke with the introduction
of libdebuginfod. I suggest also covering the library with the profile.
Please consider applying the attached patch to that end.

Helmut
--- a/debian/rules
+++ b/debian/rules
@@ -46,6 +46,7 @@
 	./configure $(confflags) --prefix=/usr \
 		--libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
 		--program-prefix=eu- --disable-silent-rules \
+		--$(if $(filter pkg.elfutils.nodebuginfod,$(DEB_BUILD_PROFILES)),dis,en)able-libdebuginfod \
 		--$(if $(filter pkg.elfutils.nodebuginfod,$(DEB_BUILD_PROFILES)),dis,en)able-debuginfod

 build: build-stamp

Bug#976874: audacity: CVE-2020-11867

[Salvatore Bonaccorso]

Source: audacity
Version: 2.4.2~dfsg0-3
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for audacity.

CVE-2020-11867[0]:
| Audacity through 2.3.3 saves temporary files to
| /var/tmp/audacity-$USER by default. After Audacity creates the
| temporary directory, it sets its permissions to 755. Any user on the
| system can read and play the temporary audio .au files located there.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-11867
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11867
[1] https://salvatoresecurity.com/the-many-perils-of-tmp/
[2] https://bugzilla.suse.com/show_bug.cgi?id=1179449

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#891830: Fix for check_raid mdstat fails to parse 'sdd2[3](W)(S)'

[debbugs]

Dear maintainer, hi everyone,

I got the same issue and I've made a simple fix on the regex, instead of
"?" which is valid for "0" or "1" occurence, I used "*".

It seems to work well on my side, maybe you could try?

I'm using the latest version available on Debian 10.

Here is my patch:

Regards,

Aymeric.


--- /usr/lib/nagios/plugins/check_raid  2020-12-08 21:05:25.067753313 +0100
+++ /tmp/check_raid 2020-12-08 21:05:20.219799196 +0100
@@ -3558,7 +3558,7 @@
    my $re = qr{^
    (\S+)   # devname
    (?:\[(\d+)\])   # desc_nr
-   (?:\((.)\))?    # flags: (W|F|S) -
WriteMostly, Faulty, Spare
+   (?:\((.)\))*    # flags: (W|F|S) -
WriteMostly, Faulty, Spare
    $}x;
    my @disks = ();
    my $personality;

Bug#915113: lyx: Has problem exporting to Postscript - fails on converting certain images

[Pavel Sanda]

On Fri, 30 Nov 2018 17:05:58 +0100 Adrian Immanuel Kiess  
wrote:
> currently in Debian/testing LyX fails on exporting to Postscript documents due
> to error in exporting or converting certain images (if not all).

Is this problem fixed for you now?
Otherwise I would like to see the full output of when running postscript build
(via View->Messages Pane). You ca ncopy paste the output directly into them 
email.

Thanks,
Pavel

Bug#976873: golang-github-hashicorp-go-slug: CVE-2020-29529

[Salvatore Bonaccorso]

Source: golang-github-hashicorp-go-slug
Version: 0.4.1-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/hashicorp/go-slug/pull/12
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-hashicorp-go-slug.

CVE-2020-29529[0]:
| HashiCorp go-slug up to 0.4.3 did not fully protect against Zip Slip
| attacks while unpacking tar archives, and protections could be
| bypassed with specific constructions of multiple symlinks. Fixed in
| 0.5.0.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-29529
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29529
[1] https://github.com/hashicorp/go-slug/pull/12

Regards,
Salvatore

Bug#976854: samba: not built with io_uring support

[Frederik Himpe]

Package: samba
Version: 2:4.13.2+dfsg-3
Severity: normal
X-Debbugs-Cc: frede...@frehi.be

The vfs_io_uring module is missing from Debian's samba-vfs-modules package.

https://wiki.samba.org/index.php/Samba_4.12_Features_added/changed#.27io_uring.27_vfs_module




-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
* /var/lib/samba/dhcp.conf not present

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

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

Versions of packages samba depends on:
ii  adduser  3.118
ii  dpkg 1.20.5
ii  init-system-helpers  1.59
ii  libbsd0  0.10.0-1
ii  libc62.31-5
ii  libgnutls30  3.6.15-4
ii  libldb2  2:2.2.0-3+b1
ii  libpam-modules   1.3.1-5
ii  libpam-runtime   1.3.1-5
ii  libpopt0 1.18-2
ii  libpython3.9 3.9.1~rc1-2
ii  libtalloc2   2.3.1-2+b1
ii  libtasn1-6   4.16.0-2
ii  libtdb1  1.4.3-1+b1
ii  libtevent0   0.10.2-1
ii  libwbclient0 2:4.13.2+dfsg-3
ii  lsb-base 11.1.0
ii  procps   2:3.3.16-5
ii  python3  3.9.0-4
ii  python3-dnspython2.0.0-1
ii  python3-samba2:4.13.2+dfsg-3
ii  samba-common 2:4.13.2+dfsg-3
ii  samba-common-bin 2:4.13.2+dfsg-3
ii  samba-libs   2:4.13.2+dfsg-3
ii  tdb-tools1.4.3-1+b1

Versions of packages samba recommends:
pn  attr
ii  logrotate   3.17.0-2
pn  python3-markdown
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.13.2+dfsg-3

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp | chrony   
pn  smbldap-tools  
pn  ufw
ii  winbind2:4.13.2+dfsg-3

-- no debconf information

Bug#976872: CVE-2020-29565: Open redirect in workflow forms (OSSA-2020-008)

[Thomas Goirand]

Source: horizon
Severity: important
Tags: patch

==
OSSA-2020-008: Open redirect in workflow forms
==

:Date: December 03, 2020
:CVE: CVE-2020-29565


Affects
~~~
- - Horizon:  <15.3.2, >=16.0.0 <16.2.1, >=17.0.0 <18.3.3, >=18.4.0 <18.6.0


Description
~~~
Pritam Singh (Red Hat) reported a vulnerability in Horizon's workflow
forms. Previously there was a lack of validation on the "next"
parameter, which would allow someone to supply a malicious URL in
Horizon that can cause an automatic redirect to the provided malicious
URL.


Patches
~~~
- - https://review.opendev.org/758843 (Stein)
- - https://review.opendev.org/758841 (Train)


Credits
~~~
- - Pritam Singh from Red Hat (CVE-2020-29565)


References
~~
- - https://launchpad.net/bugs/1865026
- - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29565

Bug#976867: [Pkg-rust-maintainers] Bug#976867: RUSTSEC-2020-0077: memmap: memmap is unmaintained

[Sylvestre Ledru]

Hello,

Le 08/12/2020 à 21:00, Salvatore Bonaccorso a écrit :

Source: rust-memmap
Version: 0.7.0-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

See

https://rustsec.org/advisories/RUSTSEC-2020-0077.html
https://github.com/danburkert/memmap-rs/issues/90

so rust-memmap should be started to be replaced with maintained
alternatives.

Could you please explain why you set the severity as important?
AFAIK, there isn't a security exploit. Not in the binary shipping in Debian 
either.

The fact that it is unmaintained upstream isn't a blocker on the Debian side 
AFAIK.

Thanks
Sylvestre

Bug#946205: jsunit: autopkgtest times out without the right version of thunderbird

[Paul Gevers]

Hi,

On Thu, 5 Dec 2019 12:21:51 +0100 Paul Gevers  wrote:
> If the situation doesn't change in a week or two I may blacklist this
> package on the ci.debian.net infrastructure. If that happens I will
> remove the blacklist once this bug is fixed. If needed, please ping
> me to try any uploads you make that should fix the issue if you are
> unsure and don't want to close this bug until verified.

We are hit by this again. I have added jsunit to our blocklist.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976871: RUSTSEC-2020-0080: miow: `miow` invalidly assumes the memory layout of std::net::SocketAddr

[Salvatore Bonaccorso]

Source: rust-miow
Version: 0.3.1-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/yoshuawuyts/miow/issues/38
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

See https://rustsec.org/advisories/RUSTSEC-2020-0080.html and
https://github.com/yoshuawuyts/miow/issues/38 for details.

Regards,
Salvatore

Bug#976870: RUSTSEC-2020-0078: net2: `net2` invalidly assumes the memory layout of std::net::SocketAddr

[Salvatore Bonaccorso]

Source: rust-net2
Version: 0.2.33-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/deprecrated/net2-rs/issues/105
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

See https://rustsec.org/advisories/RUSTSEC-2020-0078.html and
https://github.com/deprecrated/net2-rs/issues/105 for details.

Regards,
Salvatore

Bug#976101: systemd: Offline update installation in systemd (via gnome-update) doesn't cleanly unmount filesystem

[Michael Biebl]

Am 08.12.20 um 20:39 schrieb Josh Jones:

Amazing, that has taught me something very useful!

shutdown-log.txt attached and error is visible!



Thanks.
So from a quick glance it seems fwupd keeps your / busy and prevents it 
from being remounted ro.



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953679 looks related

If you don't have a system/BIOS vendor supported by fwupd, you might 
consider purging the package to verify that the problem is solved.




Michael

Bug#976869: RUSTSEC-2020-0073: image: Mutable reference with immutable provenance

[Salvatore Bonaccorso]

Source: rust-image
Version: 0.22.1-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/image-rs/image/issues/1357
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

See https://rustsec.org/advisories/RUSTSEC-2020-0073.html and
https://github.com/image-rs/image/issues/1357 .

Regards,
Salvatore

Bug#976867: RUSTSEC-2020-0077: memmap: memmap is unmaintained

[Salvatore Bonaccorso]

Source: rust-memmap
Version: 0.7.0-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

See

https://rustsec.org/advisories/RUSTSEC-2020-0077.html
https://github.com/danburkert/memmap-rs/issues/90

so rust-memmap should be started to be replaced with maintained
alternatives.

Regards,
Salvatore

Bug#976866: osmo-sgsn: possible null pointer dereferences

[Steve Langasek]

Package: osmo-sgsn
Version: 1.3.0-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear maintainers,

The osmo-sgsn package is failing to bulid from source on s390x in Ubuntu,
because the compiler detects that certain pointer dereferences may be acting
on a null pointer:

gprs_subscriber.c: In function ‘gprs_subscr_get_or_create_by_mmctx’:
gprs_subscriber.c:849:17: error: potential null pointer dereference 
[-Werror=null-dereference]
  849 |   subscr->flags |= GPRS_SUBSCRIBER_FIRST_CONTACT;
  | ^~
gprs_subscriber.c:850:17: error: potential null pointer dereference 
[-Werror=null-dereference]
  850 |   subscr->flags &= ~GPRS_SUBSCRIBER_ENABLE_PURGE;

  (https://launchpad.net/ubuntu/+source/osmo-sgsn/1.3.0-3/+build/20177923)

I haven't looked into why this build failure doesn't happen on other archs,
or why it wasn't seen on s390x in Debian; but I've confirmed that the
compiler's errors are correct.  The attached patch avoids the possible
null-pointer dereferences and lets the package build.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru osmo-sgsn-1.3.0/debian/patches/no-null-pointer-derefence.patch 
osmo-sgsn-1.3.0/debian/patches/no-null-pointer-derefence.patch
--- osmo-sgsn-1.3.0/debian/patches/no-null-pointer-derefence.patch  
1969-12-31 16:00:00.0 -0800
+++ osmo-sgsn-1.3.0/debian/patches/no-null-pointer-derefence.patch  
2020-12-08 11:48:04.0 -0800
@@ -0,0 +1,36 @@
+Description: avoid possible null dereferences
+ Detected by the compiler on Ubuntu s390x
+Author: Steve Langasek 
+Last-Update: 2020-12-08
+
+Index: osmo-sgsn-1.3.0/src/gprs/gprs_subscriber.c
+===
+--- osmo-sgsn-1.3.0.orig/src/gprs/gprs_subscriber.c
 osmo-sgsn-1.3.0/src/gprs/gprs_subscriber.c
+@@ -846,6 +846,8 @@
+ 
+   if (!subscr) {
+   subscr = gprs_subscr_get_or_create(mmctx->imsi);
++  if (!subscr)
++  return NULL;
+   subscr->flags |= GPRS_SUBSCRIBER_FIRST_CONTACT;
+   subscr->flags &= ~GPRS_SUBSCRIBER_ENABLE_PURGE;
+   }
+@@ -869,6 +871,8 @@
+   LOGMMCTXP(LOGL_DEBUG, mmctx, "Requesting subscriber data update\n");
+ 
+   subscr = gprs_subscr_get_or_create_by_mmctx(mmctx);
++  if (!subscr)
++  return -EINVAL;
+ 
+   subscr->flags |= GPRS_SUBSCRIBER_UPDATE_LOCATION_PENDING;
+ 
+@@ -894,6 +898,8 @@
+   LOGMMCTXP(LOGL_DEBUG, mmctx, "Requesting subscriber authentication 
info\n");
+ 
+   subscr = gprs_subscr_get_or_create_by_mmctx(mmctx);
++  if (!subscr)
++  return -EINVAL;
+ 
+   subscr->flags |= GPRS_SUBSCRIBER_UPDATE_AUTH_INFO_PENDING;
+ 
diff -Nru osmo-sgsn-1.3.0/debian/patches/series 
osmo-sgsn-1.3.0/debian/patches/series
--- osmo-sgsn-1.3.0/debian/patches/series   2020-08-09 10:28:26.0 
-0700
+++ osmo-sgsn-1.3.0/debian/patches/series   2020-12-08 11:31:57.0 
-0800
@@ -1,3 +1,4 @@
 0001-Spelling-fixes.patch
 0002-Compare-with-ENOTSUP-to-fix-build-on-mipsel-mips64el.patch
 gcc10.patch
+no-null-pointer-derefence.patch

Bug#976402: Proposed official virtual packages - todo and todo.txt

[Dave Steele]

Please update the Authoritative List of Virtual Package Names to
include "todo" and "todo.txt".

Discussion of the change is documented in [#976402].

[#976402]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976402


Suggested content:

# Miscellaneous

virtualPackages:
  - name: todo
description: a command-line task management utility
  - name: todo.txt
description: task management based on a standard free-form text format

Bug#976757: [Android-tools-devel] Bug#976757: fastboot: Dependency missing

[Hans-Christoph Steiner]

You need to keep all the versions matching for the Android Tools 
packcages, e.g. 8.1.0+r23.  When the fastboot update comes, they'll all 
work again.  Or you can go back to 8.1.0+r23 for all the packages.

Bug#976138: fix in git

[rosea.grammostola]

It's reported to me that it is fixed in git.

https://sourceforge.net/p/qmidiarp/code/ci/master/tree/

Bug#976101: systemd: Offline update installation in systemd (via gnome-update) doesn't cleanly unmount filesystem

[Josh Jones]

Amazing, that has taught me something very useful!

shutdown-log.txt attached and error is visible!

Josh

On Sun, 2020-12-06 at 21:36 +0100, Michael Biebl wrote:
> Am Sonntag, den 06.12.2020, 19:28 +0100 schrieb Michael Biebl:
> > Am 06.12.20 um 17:04 schrieb Josh Jones:
> > > It is the root filesystem which is failing to be remounted read-
> > > only -
> > > this is a simple setup with only one filesystem for the whole
> > > system.
> > > 
> > > It seems to be happening right at the very very end of the
> > > shutdown
> > > sequence - I have attached a picture of the error; quality is
> > > poor
> > > because I had to capture it from video footage. Is there any way
> > > to
> > > even have anything saved to disk so late in the sequence?
> > 
> > With the shutdown hook described in README.Debian and 
> > https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
> > (install the hook as /lib/systemd/system-shutdown/debug.sh without
> > the 
> > /usr prefix) you can gather logs right until the end
> > 
> > 
> 
> Copy the attached script to /lib/systemd/system-shutdown/, make it
> executable with chmod +x, then add 
> systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
> to the kernel command line and after the reboot, attach the file
> /shutdown-log.txt to this bug report.
> 
> Michael
[0.00] Linux version 4.19.0-13-amd64 (debian-ker...@lists.debian.org) 
(gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-amd64 
root=UUID=7900bc19-0f2b-463a-b20c-fca3956fd844 ro quiet splash nomodeset
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1fff] usable
[0.00] BIOS-e820: [mem 0x2000-0x201f] reserved
[0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable
[0.00] BIOS-e820: [mem 0x40004000-0x40004fff] reserved
[0.00] BIOS-e820: [mem 0x40005000-0xc8c37fff] usable
[0.00] BIOS-e820: [mem 0xc8c38000-0xc97d1fff] reserved
[0.00] BIOS-e820: [mem 0xc97d2000-0xc985efff] usable
[0.00] BIOS-e820: [mem 0xc985f000-0xc98f] ACPI NVS
[0.00] BIOS-e820: [mem 0xc990-0xca0a2fff] reserved
[0.00] BIOS-e820: [mem 0xca0a3000-0xca15cfff] type 20
[0.00] BIOS-e820: [mem 0xca15d000-0xca15dfff] usable
[0.00] BIOS-e820: [mem 0xca15e000-0xca1a0fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xca1a1000-0xcabecfff] usable
[0.00] BIOS-e820: [mem 0xcabed000-0xcaff1fff] reserved
[0.00] BIOS-e820: [mem 0xcaff2000-0xcaff] usable
[0.00] BIOS-e820: [mem 0xcb80-0xcf9f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00042f5f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by American Megatrends
[0.00] efi:  ACPI=0xc98f  ACPI 2.0=0xc98f  SMBIOS=0xf04c0  
MPS=0xfd560 
[0.00] secureboot: Secure boot could not be determined (mode 0)
[0.00] SMBIOS 2.7 present.
[0.00] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Extreme6, 
BIOS P2.80 07/01/2013
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 3400.112 MHz processor
[0.001358] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.001359] e820: remove [mem 0x000a-0x000f] usable
[0.001366] last_pfn = 0x42f600 max_arch_pfn = 0x4
[0.001369] MTRR default type: uncachable
[0.001370] MTRR fixed ranges enabled:
[0.001370]   0-9 write-back
[0.001371]   A-B uncachable
[0.001371]   C-C write-protect
[0.001372]   D-D uncachable
[   

Bug#936020: /var/lib/dpkg/info/sympa.prerm: 33: [: =: unexpected operator upon removal

[Stefan Hornburg (Racke)]

On 12/8/20 6:23 PM, Chris Halls wrote:
> reassign 936020 dbconfig-common
> 
> tags 936020 + patch
> 
> thanks
> 
> 
> Hello
> 
> On Thu, 29 Aug 2019 12:36:50 +0200 Olivier Berger 
>  wrote:
> 
>> >> /var/lib/dpkg/info/sympa.prerm: 33: [: =: unexpected operator
> 
> This comes from dbconfig-common, not directly from sympa itself.
> 
> The problem happens if there is no database configured when the prerm script 
> is invoked. I was able to trigger this on
> another package by installing without a database (question 
> dbconfig-install=false), and then running dpkg-reconfigure on
> the package.
> 
> Patched attached to add the missing quotes.
> 
> Thanks
> 
> Chris
> 

Hello Chris,

thanks a lot for the patch!

Regards
Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#942176: libsane: Canon LiDE 220 works up to 1200 dpi only

[Jörg Frings-Fürst]

tags 942176 + moreinfo
thanks



Hello Philipp,

please can you check if the bug still exists in the current version? 


CU
Jörg 
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#947072: upgrade to buster breaks Epson V33/V330 installation

[Jörg Frings-Fürst]

Hello,

since the last post this bug is fixed and can closed.

CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#976180: RFS: libzc/0.4.3-1 -- Command line tool for the libzc library

[Niels Thykier]

Marc Ferland:
> On Sun, Dec 6, 2020 at 6:24 AM Niels Thykier  wrote:
> 
>> Niels Thykier:
>>> [...]
>>>
>>> Thanks, I have uploaded it to unstable.
>>>
>>> ~Niels
>>>
>>
>> Hi Marc,
>>
>> Because this libzc renamed a binary, the upload had to go through NEW.
>> This in turn implied that I had to do a binary upload and the upload
>> will not migrate to testing without a new source-only upload.
>>
>> I can either do that "no change version bump" NMU with your permission
>> or alternatively you can provide me with another update to sponsor (if
>> you have any pending changes or want to wait a bit).  In the latter
>> case, please keep the freeze deadlines in mind[1].
>>
>> Go ahead and make the "no change version bump".
> 
> Thanks,
> 
> Marc
> 

Ok. :) Turns out we could just solve with a binNMU because there was no
arch:all package, so I have arranged for that solution instead. :)

~Niels

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[Andreas Beckmann]

On 12/7/20 4:24 PM, jim_p wrote:
> About the "nvidia-blacklists-nouveau.conf". I had to use nouveau some months
> ago too (for like 1 hour at most, thankfully) and that file was removed when I
> purged some nvidia package. I have no idea why it is not removed anymore. A
> file with the same name but under a different path exists in nvidia-
> legacy-340xx-kernel-support.

Is nvidia-blacklists-nouveau.conf a symlink (managed by the package) or
a real file (managed by the local admin)?

Disabling the nvidia driver can be done with
  update-glx --config glx
and then selecting mesa-diverted. That should disable all the modprobe
configuration bits that are managed by the packaging.

> However, the patch does not work, probably because it conflicts with another
> patch. It does work with no issues on another distro that uses the same kernel
> version and the has the same kernel parameter disabled. It also works when it
> is applied to the "source" of the driver (tested on a virtual machine by a
> friend of mine).

The magic from archlinux is not the kernel-5.9 patch (a similar patch is
already part of the Debian package) but the recently added
kernel-5.7.patch. That essentially copies some bits of kernel source
into the driver to bring back the two missing functions (and their
dependencies).


Andreas

Bug#976852: Subject: ITP: node-iterall -- utilities for using JavaScript Iterables

[Abraham Raji]

Package: wnpp
Severity: wishlist
Owner: Abraham Raji 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name    : node-iterall
  Version : 1.2.2
  Upstream Author : Lee Byron  (http://leebyron.com/)
* URL : https://github.com/leebyron/iterall
* License : Expat
  Programming Lang: JavaScript
  Description : utilities for using JavaScript Iterables
iterall provides a few crucial utilities for implementing and working with
Iterables, Async Iterables and Array-likes in all JavaScript environments,
even old versions of Internet Explorer, in a tiny library weighing well
under 1KB when minified and gzipped.
.
Node.js is an event-based server-side JavaScript engine.

This module is a dependency for a version of graphql that is used by 
gitlab. I will package and maintain this module with the help Debian
JS Team.

Abraham Raji
-- 
Mea navis aëricumbens anguillis abundat.

Bug#976853: ITP: node-iterall -- utilities for using JavaScript Iterables

[Abraham Raji]

Package: wnpp
Severity: wishlist
Owner: Abraham Raji 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name    : node-iterall
  Version : 1.2.2
  Upstream Author : Lee Byron  (http://leebyron.com/)
* URL : https://github.com/leebyron/iterall
* License : Expat
  Programming Lang: JavaScript
  Description : utilities for using JavaScript Iterables
iterall provides a few crucial utilities for implementing and working with
Iterables, Async Iterables and Array-likes in all JavaScript environments,
even old versions of Internet Explorer, in a tiny library weighing well
under 1KB when minified and gzipped.
.
Node.js is an event-based server-side JavaScript engine.

This module is a dependency for a version of graphql that is used by 
gitlab. I will package and maintain this module with the help Debian
JS Team.

Abraham Raji
-- 
Mea navis aëricumbens anguillis abundat.

Bug#970113: Network scanning fails without proper permissions

[Jörg Frings-Fürst]

fixed 970113 1.0.29-1~experimental1
thanks

Hello,

this bug is fixed since 1.0.29-1~experimental1.

So I close this bug.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#976864: openssh-client: fails to parse quoted setting tokens

[Donovan Keohane]

Package: openssh-client
Version: 1:8.4p1-2~bpo10+1
Severity: normal

Dear Maintainer,

A coworker of mine has stumbled upon a strange inconsistency with ssh
parsing ssh_config.

* What led up to the situation?

An upgrade was performed from v7.9p1-10+deb10u3 to v8.4p1-2~bpo10+1.
Running ssh afterwards failed with the following error:

/etc/ssh/ssh_config line 218: unsupported option

Which references this line of the configuration:

AddKeysToAgent="no"

* What exactly did you do (or not do) that was effective (or
* ineffective)?

Removing the surrounding quotes from the 'no' token.

* What was the outcome of this action?

This allowed the file to be parsed properly, and ssh to work without
issue.

* What outcome did you expect instead?

We expected that the quoted format be accepted.