Bug#972033: pandas ftbfs with python3.9 as supported python version

2020-10-11 Thread Rebecca N. Palmer
There's a 1.1.3 package in Salsa, but it hasn't been tested.  (With 
python3-all-dev from experimental, it fails because numpy doesn't have a 
3.9 build yet.)




Bug#971418: jhbuild: Missing dependency on python3-distuils

2020-10-11 Thread Guillem Jover
Control: reopen -1

On Wed, 2020-09-30 at 10:40:53 +0100, Chris Lamb wrote:
> Package: jhbuild
> Version: 3.38.0-1
> Severity: serious
> Tags: patch

> This package is missing a binary dependency on python3-distutils:

> diff --git a/debian/control b/debian/control
> index e7a8882..7d18b97 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -22,7 +22,8 @@ Package: jhbuild
>  Architecture: all
>  Depends: ${shlibs:Depends},
>   ${misc:Depends},
> - ${python3:Depends}
> + ${python3:Depends},
> +  python3-distuils,

There's a typo here «distuils» instead of «distu_t_ils», which makes
the package uninstallable now.

Thanks,
Guillem



Bug#971347: transition: mumps

2020-10-11 Thread Drew Parsons
I uploaded petsc 3.13.6+dfsg1-1 (one of mumps' reverse dependencies) to 
unstable in order to clear the way for PETSc 3.14 in experimental.


It built "successfully" against the old mumps on armel and mipsel but 
the openmpi inconsistency causes dolfin to FTBFS on these failing 
arches.


I think petsc 3.13.6+dfsg1-1 needs to be marked again for binNMU 
"Rebuild against MUMPS 5.3.3" on armel, mipsel (i.e. versioned binNMU).


Drew



Bug#972069: slepc64-dev: enable ARPACK support in 64-bit build

2020-10-11 Thread Drew Parsons
Package: slepc64-dev
Version: 3.14.0+dfsg1-1
Severity: normal
Control: block -1 by 972068

ARPACK support was disabled in slepc 3.14.0+dfsg1-1 since ARPACK
cannot be used with 64-bit integers. This is because a 64-bit build of
libarpack2-dev is not yet available.

Bug#972068 has been filed to request a 64-bit build of arpack.
Once this is done it will be possible to reinstate ARPACK support in
slepc64.  It may require ILP64 support in other components of the
numerical library stack (e.g. openmpi, see Bug#961108)


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

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

Versions of packages slepc64-dev depends on:
ii  libslepc64-complex-dev  3.14.0+dfsg1-1
ii  libslepc64-complex3.14-dev  3.14.0+dfsg1-1
ii  libslepc64-real-dev 3.14.0+dfsg1-1
ii  libslepc64-real3.14-dev 3.14.0+dfsg1-1

slepc64-dev recommends no packages.

slepc64-dev suggests no packages.

-- no debconf information



Bug#972068: arpack: provide 64-bit (ILP64) build

2020-10-11 Thread Drew Parsons
Source: arpack
Version: 3.7.0-3
Severity: wishlist
Control: affects -1 src:slepc

We have started providing 64-bit (ILP64) variants of our numerical
libraries, which enables computation of vastly larger, more complex
systems.

The blas libraries provide ILP64 builds as libblas64-dev, etc.

mumps and petsc,slepc provide libmumps64-dev, petsc64-dev,
slepc64-dev. But these builds enable 64-bit indexing of matrices, not
full ILP64. For full 64-bit support they will require 64-bit support
in lower level libraries (openmpi, arpack, etc).

ARPACK support is currently removed from the slepc 64-bit build (new
version 3.14) since current ARPACK cannot be used with 64-bit integers.

I'm filing this Bug to request a 64-bit variant of arpack be built.

This would be an extra set of packages (e.g. libarpack2-64-dev,
libarpack2-64) providing libarpack64.so (or libarpack-64.so) alongside
libarpack.so (i.e. coinstallable).  It would be built against
libblas64-dev instead of libblas-dev.

slepc64-dev would then be able to reinstate ARPACK support in the
64-bit build (once the full numerical library stack is ILP64-enabled).


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

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



Bug#971975: lintian: Warn about four-letter weekday abbreviations in debian/changelog entry signatures (should be three-letter)

2020-10-11 Thread Guillem Jover
Hi!

On Sat, 2020-10-10 at 23:44:19 +0200, Axel Beckert wrote:
> Package: lintian
> Version: 2.97.0
> Severity: wishlist

> https://bugs.debian.org/971974, which is about the following two
> debian/changelog entry signatures over which aptitude-changelog-parser
> respectively Dpkg::Changelog::Parse tripped (X-Debbugs-Cc'ing Guillem
> for that—JFYI, probably not be a libdpkg-perl bug), made me thinking if
> such case should be better reported by Lintian:
> 
>  -- John Hasler   Thur, 29 May 2003 20:30:00 -0500
>  -- John Hasler   Thur, 7 Nov 2002 8:00:00 -0600

Yeah these are bogus changelog entries, and libdpkg-perl rightfully
complains.

> Funnily only weekdays beginning with a "T" show up: "Tues" and
> "Thur". Also the leading second space before the single-digit day is
> consistently missing (although that one actually isn't specified in RFC
> 822 and the the Debian Policy does not mention it either, so it is
> probably ok).

The various parts can be separated by an arbitrary number of spaces,
of course lintian could complain about lack of consistency here.

Thanks,
Guillem



Bug#969965: [Pkg-kbd-devel] Bug#969965: text installer: unable to switch keyboard layouts - libkeymap.so.1 missing

2020-10-11 Thread Holger Wansing
Hi,

Andreas Henriksson  wrote:
> Hello Holger,
> 
> On Tue, Oct 06, 2020 at 11:25:06PM +, Holger Wansing wrote:
> > Hi,
> > 
> > Am Dienstag, 6. Oktober 2020 schrieb Andreas Henriksson: 
> > > Could you please test rebuilding kbd with --enable-libkeymap to
> > > --disable-libkeymap in debian/rules?
> > 
> > sbuild fails when I try it like that.
> > A build log is attached.
> > Debugging this is somewhat out of my skills, sorry.
> 
> I've uploaded a new version that implements the above suggestion
> and would very much appreciate if you could test and give feedback
> on where we ended up when you have chance to do so.

I built a debian-installer image locally here and tested switching 
several keymaps there, and it looks as it works correctly now!

Thanks

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#971914: wordpress: Log Out redirects to "http://wp-login.php/?loggedout=true" (missing hostname)

2020-10-11 Thread Craig Small
Hi Chuck,
  Thanks for your bug report.  I have found that the latest version of
WordPress doesn't have this issue but in Debian 10 WordPress version 5.0.10
it does.

On a new vm I downloaded the latest version of WordPress from the wordpress
> site, extracted it to /var/www/wordpress, changed the apache config to
> point to that directory and there was no log out issue.
>
That would be expected, the Debian package of version 5.5.1 doesn't have
this problem either.


> On a new vm I downloaded the same version as in stable (5.0.10), extracted
> it to /var/www/wordpress, changed the apache config to point to that
> directory and there was no log out issue.
>
Ah, that now sounds like there is something not quite right with the
validation patch I have in at [1]

In fact, I don't need this patch anymore as it is already there and the
duplicate validation will make it not work too well as you have found.

 - Craig

1:
https://salsa.debian.org/debian/wordpress/-/blob/buster/debian/patches/cs45974_url_valid_redirect


Bug#971292: samba: Switch to python3-pycryptodome

2020-10-11 Thread Andrew Bartlett
On Mon, 2020-09-28 at 23:29 +0200, Sebastian Ramacher wrote:
> Source: samba
> Version: 2:4.12.5+dfsg-3
> Severity: important
> Tags: sid bullseye
> Usertags: pycrypto
> 
> Dear maintainer,
> 
> samba currently Build-Depends or Depends on python3-crypto from
> PyCrypto. This project is no longer maintained and PyCryptodome
> (https://www.pycryptodome.org/en/latest/) provides a drop in
> replacement. Please switch to python3-pycryptodome. I'd like to
> remove python-crypto before the release of bullseye.

Any references to Samba 4.12 requiring python3-crypto are in error,
thankfully Samba 4.12 removed that requirement.

https://bugzilla.samba.org/show_bug.cgi?id=14255

Andrew Bartlett
-- 
Andrew Bartlett   https://samba.org/~abartlet/
Authentication Developer, Samba Team  https://samba.org
Samba Developer, Catalyst IT  
https://catalyst.net.nz/services/samba



Bug#971943: task-laptop: Add tlp and thermald

2020-10-11 Thread Ben Hutchings
On Sat, 2020-10-10 at 11:44 +0200, Frank wrote:
> Package: task-laptop
> Version: 3.53
> Severity: wishlist
> 
> Dear Maintainer,
> 
> I wish that the package tlp (to save powers) and thermald (to control the
> temperature) is included in task-laptop, which are quite useful for laptops.

Power-saving modes are (unfortunately) a major source of bugs in
hardware, firmware, and drivers.  For that reason we should be cautious
about enabling them.  Currently device power-saving policies are mostly
set by kernel drivers, and where they enable a power-saving mode by
default they also tend to have long lists of workarounds for buggy
devices.

I don't think a task should include programs that override our kernel's
defaults, as tlp appears to do.  If we decide those defaults are bad
then I think we should fix them in our kernel.

As for thermald, I understand that it is important for some newer
laptops.  Does it quietly do nothing on other models?

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.




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


Bug#972065: python3-plac: New upstram release 1.2.0

2020-10-11 Thread Gabriel Filion
Package: python3-plac
Version: 0.9.6-1
Severity: normal

Hello,

The plac library has see some releases since the current version that's in the
debian archive was released.

Version 1.2.0 is currently available:

https://pypi.org/project/plac/#files

Version 0.9.6 was released in 2016:

https://pypi.org/project/plac/#history

The list of changes that happened does not seem very huge, but there's been
some feature additions and bug fixes:

https://github.com/micheles/plac/blob/master/CHANGES.md

upstream now also has a LICENSE.txt file to make it more explicit that the
code is under 2-clause BSD.


cheers!


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

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

Versions of packages python3-plac depends on:
ii  python3  3.8.2-3

python3-plac recommends no packages.

python3-plac suggests no packages.

-- no debconf information



Bug#972066: mirror submission for mirror.anigil.com

2020-10-11 Thread Lim Si Woo
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirror.anigil.com
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Lim Si Woo 
Country: KR Korea, Republic of
Location: Seo-gu, Gwangju




Trace Url: http://mirror.anigil.com/debian/project/trace/
Trace Url: http://mirror.anigil.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.anigil.com/debian/project/trace/mirror.anigil.com



Bug#972063: paracode.1: fix some formatting issues in the manual

2020-10-11 Thread Bjarni Ingi Gislason
Package: unicode
Version: 2.7-1
Severity: minor
Tags: patch

Dear Maintainer,

  remove space at end of lines.

Fix warnings from test-groff.

Reduce space between words or start the sentence on a
new line.

Change a two-fonts macro to an one-font macro for a
single argument.

Change a HYPHEN-MINUS (code 0x55, 2D) to a dash
(minus) if it matches " -[:alpha:]" or \[aq]-[:alpha:] (for options).

Split long lines (> 80).

See man-pages(7) for guidelines.

###

  Details:

Input file is paracode.1

Output from "mandoc  -T lint paracode.1"
mandoc: paracode.1:7:19: STYLE: whitespace at end of input line
mandoc: paracode.1:32:79: STYLE: whitespace at end of input line

#

Test nr. 2:

Enable and fix warnings from 'test-groff'.

[ "test-groff" is a developmental version of "groff" ]

Output from test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z :
:26 (macro BI): only 1 argument, but more are expected
troff: backtrace: file '':32

#

Test nr. 12:

Reduce space between words.

44:paracode -t cherokee  output
46:paracode -r -t mirror  output

#

Test nr. 16:

Use the correct macro for the font change of a single argument.

26:.BI \-\-tables
65:.BI \-r

#

Test nr. 25:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

7:.RI [ -t tables ] 
42:paracode -t cyrillic+greek+cherokee
44:paracode -t cherokee  output
46:paracode -r -t mirror  output
67:Display text in reverse order after conversion, best used together with -t 
mirror.

#

Test nr. 37:

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

paracode.1: line 14 length 82
\fBparacode\fP exploits the full power of the Unicode standard to convert the 
text

paracode.1: line 15 length 84
into visually similar stream of glyphs, while using completely different 
codepoints.

paracode.1: line 16 length 81
It is an excellent didactic tool demonstrating the principles and advanced use 
of

paracode.1: line 67 length 82
Display text in reverse order after conversion, best used together with -t 
mirror.


#

Test nr. 63:

Name of a manual is set in bold, the section in roman.

70:iconv(1)

###

Patch:

--- paracode.1  2020-10-11 21:30:00.0 +
+++ paracode.1.new  2020-10-11 22:00:50.0 +
@@ -4,7 +4,8 @@
 paracode \- command line Unicode conversion tool
 .SH SYNOPSIS
 .B paracode
-.RI [ -t tables ] 
+.RB [ \-t
+.IR tables ]
 string
 .SH DESCRIPTION
 This manual page documents the
@@ -12,40 +13,38 @@ This manual page documents the
 command.
 .PP
 \fBparacode\fP exploits the full power of the Unicode standard to convert the 
text
-into visually similar stream of glyphs, while using completely different 
codepoints.
+into visually similar stream of glyphs,
+while using completely different codepoints.
 It is an excellent didactic tool demonstrating the principles and advanced use 
of
 the Unicode standard.
 .PP
 \fBparacode\fP is a command line tool working as
 a filter, reading standard input in UTF-8 encoding and writing to
 standard output.
-
+.
 .SH OPTIONS
 .TP
 .BI \-t tables
-.BI \-\-tables
+.B \-\-tables
 
 Use given list of conversion tables, separated by a plus sign.
 
 Special name 'all' selects all the tables.
 
-Note that selecting 'other', 'cyrillic_plus' and 'cherokee' tables (and 'all') 
+Note that selecting 'other', 'cyrillic_plus' and 'cherokee' tables (and 'all')
 makes use of rather esoteric characters, and not all fonts contain them.
 
-
 Special table 'mirror' uses quite different character substitution,
 is not selected automatically with 'all' and does not work well
 with anything except plain ascii alphabetical characters.
 
 Example:
 
-paracode -t cyrillic+greek+cherokee
-
-paracode -t cherokee  output
-
-paracode -r -t mirror  output
+paracode \-t cyrillic+greek+cherokee
 
+paracode \-t cherokee output
 
+paracode \-r \-t mirror output
 
 Possible tables are:
 
@@ -60,16 +59,16 @@ other
 cherokee
 
 all
-
+.
 .TP
-.BI \-r
-
-Display text in reverse order after conversion, best used together with -t 
mirror.
+.B \-r
 
+Display text in reverse order after conversion,
+best used together with \-t mirror.
+.
 .SH SEE ALSO
-iconv(1)
-
-
+.BR iconv (1)
+.
 .SH AUTHOR
 Radovan Garab\('ik 
 
-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.10-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages unicode depends on:
ii  python3  3.8.2-3

Versions of packages unicode recommends:
ii  unicode-data  13.0.0-2

unicode suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#972062: openjfx: Make OpenJFX visible to Java programs by default

2020-10-11 Thread Leandro Doctors
Package: openjfx
Version: 11.0.7+0-5
Severity: normal
X-Debbugs-Cc: ldoct...@gmail.com

Dear Maintainer,

Could you please make sure OpenJFX is added to the Java path when installed,
and removed when uninstalled? Otherwise, applications that require OpenJFX
cannot run...

Thanks!



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

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

Versions of packages openjfx depends on:
ii  libopenjfx-java  11.0.7+0-2

Versions of packages openjfx recommends:
ii  openjfx-source  11.0.7+0-5

openjfx suggests no packages.

-- no debconf information



Bug#971418: jhbuild: Missing dependency on python3-distuils

2020-10-11 Thread Jeremy Bicha
On Sun, Oct 11, 2020, 19:15 Guillem Jover  wrote:

>
> There's a typo here «distuils» instead of «distu_t_ils», which makes
> the package uninstallable now.
>

Yes, already fixed. :-)

Thanks,
Jeremy Bicha

>


Bug#972067: RFP: onionscan -- tool for investigating the Dark Web

2020-10-11 Thread Francois Marier
Package: wnpp
Severity: wishlist

* Package name: onionscan
  Version : 0.2
  Upstream Author : Sarah Jamie Lewis 
* URL : https://onionscan.org/
* License : MIT
  Programming Lang: Go
  Description : tool for investigating the Dark Web

OnionScan is a free and open source tool for investigating the Dark Web. It
has two primary goals:
.
- We want to help operators of hidden services find and fix operational
  security issues with their services. We want to help them detect
  misconfigurations and we want to inspire a new generation of anonymity
  engineering projects to help make the world a more private place.
.
- Secondly we want to help researchers and investigators monitor and track
  Dark Web sites. In fact we want to make this as easy as possible. Not
  because we agree with the goals and motives of every investigation force
  out there - most often we don't. But by making these kinds of
  investigations easy, we hope to create a powerful incentive for new
  anonymity technology (see goal #1)

-- 
https://fmarier.org/



Bug#969648: python3.9 Re: dask, pandas 1.1

2020-10-11 Thread Rebecca N. Palmer

Control: block 972033 by 969650

This is now the only bug blocking pandas 1.1.  Is there something wrong 
with the above fix, or have you just not had time to try it?


Upgrading dask to a newer upstream version is also an option, but I 
haven't checked if it would break anything else.


Python 3.9 breaks current pandas (#972033), and fixing this may involve 
upgrading to pandas 1.1.




Bug#971806: python-hdf5storage's autopkg tests fail in unstable

2020-10-11 Thread Drew Parsons
Source: python-hdf5storage
Followup-For: Bug #971806

Must have been a temporary package inconsistency?

All tests are passing now.



Bug#972043: libreoffice: 1:6.1.5-1 -> 1:7.0.2-1 upgrade fails

2020-10-11 Thread Rene Engelhard
Hi,

Am 11.10.20 um 21:12 schrieb Jessica Clarke:
>> Preparing to unpack .../09-libreoffice-common_1%3a7.0.2-1_all.deb ...
>> dpkg-maintscript-helper: error: file 
>> '/usr/lib/libreoffice/share/registry/math.xcd' not owned by package 
>> 'libreoffice-common:all'
>> dpkg-maintscript-helper: error: directory 
>> '/usr/lib/libreoffice/share/registry' contains files not owned by package 
>> libreoffice-common:all, cannot switch to symlink
>> dpkg: error processing archive 
>> /tmp/apt-dpkg-install-yFAjDA/09-libreoffice-common_1%3a7.0.2-1_all.deb 
>> (--unpack):
>>  new libreoffice-common package pre-installation script subprocess returned 
>> error exit status 1
>> [...]
>> debian:~ jrtc27% sudo dpkg -S /usr/lib/libreoffice/share/registry/math.xcd
>> libreoffice-math: /usr/lib/libreoffice/share/registry/math.xcd

Sigh. I hate this dpkg bullshit.

(And so far for testing this in experimental first.)


The upgrade worked before this symlink was added due to #969653 (and
upstream not hounouring their own config) before I added this symlink. :(

Looks like I need a Conflicts: against pre-7.0 packages containing stuff
in /usr/lib/libreoffice/share/registry ...


Regards,


Rene



Bug#972038: Update gpaste to 3.36.4

2020-10-11 Thread Jérémy Lal
Hi !

Le dim. 11 oct. 2020 à 19:24, Amr Ibrahim  a
écrit :

> Package: gpaste
>
> Please update gpaste to 3.36.4.
>
> https://github.com/Keruspe/GPaste/blob/gpaste-3.36/NEWS
>
> NEW in 3.36.4 (03/10/2020)
> =
>
> - gnome-shell extension cosmetic updates
>

I don't understand the question.
gnome 3.38 is in debian, i'm going to update gpaste to 3.38.x branch.

Jérémy


Bug#726137: DVD remains locked when requested to switch DVDs during Package Scan

2020-10-11 Thread Mike Stanton
I have seen the same problem. It is because the driver for the DVD locks the 
DVD when processing the files and does not unlock it when it asks for the 
volume to be swapped. The workaround is to use a paper clip to manually release 
the media tray for the DVD/CD device.  It is a small hole in the case near the 
DVD Eject button.  Barring that if the device is an External device, cycling 
power on the device will release it. When you put the new media into the tray, 
it will recover the loss of power condition after you issue the next I/O 
request by answering the Swap message.  It appears this message has been out 
there a long time

Michael Stanton
GEOSPAN Corporation
6901 E. Fish Lake Road
Suite 156
Maple Grove, MN  55369
763-493-9320 X5003
651-270-3191 (mobile)
www.geospan.com




Bug#972047: unicode.1: trim trailing whitespace, fix usage of font macros and usage of '-' for options

2020-10-11 Thread Bjarni Ingi Gislason
Package: unicode
Version: 2.7-1
Severity: minor
Tags: patch

Dear Maintainer,

  Summary:

Remove space at end of lines.

Fix warnings from test-groff.

Change a two-fonts macro to an one-font macro for a
single argument.

Split a single argument into two for a two-font macro.

Change a HYPHEN-MINUS (code 0x55, 2D) to a dash
(minus, '\-')
if it matches " -[:alpha:]" or \[aq]-[:alpha:] (for options).



Input file is unicode.1

Output from "mandoc  -T lint unicode.1":

mandoc: unicode.1:7:17: STYLE: whitespace at end of input line
mandoc: unicode.1:18:9: STYLE: whitespace at end of input line
mandoc: unicode.1:19:14: STYLE: whitespace at end of input line
mandoc: unicode.1:27:7: STYLE: whitespace at end of input line
mandoc: unicode.1:29:27: STYLE: whitespace at end of input line
mandoc: unicode.1:35:7: STYLE: whitespace at end of input line
mandoc: unicode.1:37:23: STYLE: whitespace at end of input line
mandoc: unicode.1:43:7: STYLE: whitespace at end of input line
mandoc: unicode.1:45:22: STYLE: whitespace at end of input line
mandoc: unicode.1:51:7: STYLE: whitespace at end of input line
mandoc: unicode.1:53:22: STYLE: whitespace at end of input line
mandoc: unicode.1:59:7: STYLE: whitespace at end of input line
mandoc: unicode.1:67:7: STYLE: whitespace at end of input line
mandoc: unicode.1:124:20: STYLE: whitespace at end of input line
mandoc: unicode.1:167:69: STYLE: whitespace at end of input line
mandoc: unicode.1:194:46: STYLE: whitespace at end of input line
mandoc: unicode.1:200:21: STYLE: whitespace at end of input line

###


Test nr. 2:

Enable and fix warnings from 'test-groff'.


[ "test-groff" is a developmental version of "groff" ]

Input file is ./unicode.1

Output from test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -rIN=4m -t -w w -z :

:18 (macro BI): only 1 argument, but more are expected
:19 (macro BI): only 1 argument, but more are expected
:24 (macro BI): only 1 argument, but more are expected
:25 (macro BI): only 1 argument, but more are expected
:32 (macro BI): only 1 argument, but more are expected
:33 (macro BI): only 1 argument, but more are expected
:40 (macro BI): only 1 argument, but more are expected
:41 (macro BI): only 1 argument, but more are expected
:48 (macro BI): only 1 argument, but more are expected
:49 (macro BI): only 1 argument, but more are expected
:56 (macro BI): only 1 argument, but more are expected
:57 (macro BI): only 1 argument, but more are expected
:72 (macro BI): only 1 argument, but more are expected
:73 (macro BI): only 1 argument, but more are expected
:80 (macro BI): only 1 argument, but more are expected
:81 (macro BI): only 1 argument, but more are expected
:86 (macro BI): only 1 argument, but more are expected
:87 (macro BI): only 1 argument, but more are expected
:95 (macro BI): only 1 argument, but more are expected
:96 (macro BI): only 1 argument, but more are expected
:104 (macro BI): only 1 argument, but more are expected
:105 (macro BI): only 1 argument, but more are expected
:110 (macro BI): only 1 argument, but more are expected
:111 (macro BI): only 1 argument, but more are expected
:127 (macro BI): only 1 argument, but more are expected
:129 (macro BI): only 1 argument, but more are expected
:132 (macro BI): only 1 argument, but more are expected
:133 (macro BI): only 1 argument, but more are expected
:138 (macro BI): only 1 argument, but more are expected
:139 (macro BI): only 1 argument, but more are expected
:144 (macro BI): only 1 argument, but more are expected
:145 (macro BI): only 1 argument, but more are expected
:150 (macro BI): only 1 argument, but more are expected
:155 (macro BI): only 1 argument, but more are expected
:161 (macro BI): only 1 argument, but more are expected

#

Test nr. 13:

Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-

204:Use --fromcp to query codepoints from other encodings:
206:\fBunicode\fP --fromcp cp1250 -d 200
209:\fBunicode\fP --fromcp big5 -x aff3
213:\fBunicode\fP --fromcp utf-8 -x c599c3adc5a5

#

Test nr. 25:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

177:\fBunicode\fP -r face

#

Patch:

--- unicode.1   2020-10-11 02:22:43.0 +
+++ unicode.1.new   2020-10-11 02:40:33.0 +
@@ -4,7 +4,7 @@
 unicode \- command line unicode database query tool
 .SH SYNOPSIS
 .B unicode
-.RI [ options ] 
+.RI [ options ]
 string
 .SH DESCRIPTION
 This manual page documents the
@@ -15,76 +15,76 @@ command.
 
 .SH OPTIONS
 .TP
-.BI \-h 
-.BI \-\-help 
+.B \-h
+.B \-\-help
 
 Show help and exit.
 
 .TP
-.BI \-x
-.BI \-\-hexadecimal
+.B \-x
+.B \-\-hexadecimal
 
-Assume 
+Assume
 .I string
-to be a hexadecimal number 
+to be a hexadecimal number
 
 .TP
-.BI \-d
-.BI \-\-decimal
+.B \-d
+.B \-\-decimal
 
-Assume 
+Assume
 .I string
-to be a decimal number 
+to be a decimal number
 
 .TP
-.BI \-o
-.BI \-\-octal
+.B \-o
+.B \-\-octal
 
-Assume 
+Assume
 .I string
-to be an octal number 
+to be an octal number
 
 

Bug#972048: ssh-add: Could not open a connection to your authentication agent.

2020-10-11 Thread Francois Marier
Package: openssh-client
Version: 1:8.3p1-1
Severity: normal

I'm not sure ssh-add is at fault here, but I don't know how to debug this
any further.

For the past 2-3 days, I've been unable to use ssh-add to add pubkeys to my
ssh agent.

It fails with gnome-keyring-daemon:

  $ gnome-keyring-daemon
  SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  $ ls  -l /run/user/1000/keyring/
  total 0
  srwxr-xr-x 1 francois francois 0 11 oct 13:47 control=
  srwxr-xr-x 1 francois francois 0 11 oct 13:47 pkcs11=
  srwxr-xr-x 1 francois francois 0 11 oct 13:47 ssh=
  $ ssh-add
  Could not open a connection to your authentication agent.

and also with ssh-agent:

  $ ssh-agent 
  SSH_AUTH_SOCK=/tmp/ssh-vlTg2Dg8kttR/agent.9854; export SSH_AUTH_SOCK;
  SSH_AGENT_PID=9855; export SSH_AGENT_PID;
  echo Agent pid 9855;
  $ ls -l /tmp/ssh-vlTg2Dg8kttR/
  total 0
  srw--- 1 francois francois 0 11 oct 13:49 agent.9854=
  $ ssh-add
  Could not open a connection to your authentication agent.

Francois

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (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 openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.20.5
ii  libc6 2.31-4
ii  libedit2  3.1-20191231-1
ii  libfido2-11.5.0-2
ii  libgssapi-krb5-2  1.17-10
ii  libselinux1   3.1-2
ii  libssl1.1 1.1.1h-1
ii  passwd1:4.8.1-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.10-1

Versions of packages openssh-client suggests:
pn  keychain 
pn  libpam-ssh   
pn  monkeysphere 
ii  ssh-askpass  1:1.2.4.1-10+b1
ii  ssh-askpass-gnome [ssh-askpass]  1:8.3p1-1

-- no debconf information

-- 
https://fmarier.org/



Bug#600700: base-passwd: sudo group's documented semantics don't match the sudo package

2020-10-11 Thread Henrik Ahlgren
I still feel sudo is such an important group, that it would be good if
users-and-groups.txt would be further improved to more clearly document
that this group is what allows users to not only run commands with sudo
and pkexec, but also execute various other polkit-1 actions like
install software with packagekit. So it is now actually a rather badly
named generic "administrator" group. (Some other distros apparently use
other group names, like wheel for Arch.)



Bug#972049: Stop building on non-linux architectures

2020-10-11 Thread Laurent Bigonville
Source: apparmor
Version: 2.13-3
Severity: wishlist

Hello,

To me building apparmor on non-linux architectures makes little sense as
AFAIK it requires the Linux.

Moreover, since 2.13-3 apparmor is not building on non-linux
architectures and is wasting precious CPU cycles.

Could you change the packages that are arch:any to arch:linux-any?

Kind regards,

Laurent Bigonville

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

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

-- debconf information:
  apparmor/homedirs:



Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-11 Thread Richard B. Kreckel

On 11.10.20 19:28, Helmut Grohne wrote:

If you are interested in figuring out why this happens, all the better,
I guess you should pass --anything-failed-commands=%SBUILD_SHELL to
sbuild and examine config.log.


Before I dig into this, could you, please, try applying the attached 
patch and check if it works?


(It's a little bit a stab in the dark, just reverting the last changes 
made there. After all, it should've worked before.)


  -richy.
--
Richard B. Kreckel

diff --git a/m4/intparam.m4 b/m4/intparam.m4
index 3c990d7..7d81424 100644
--- a/m4/intparam.m4
+++ b/m4/intparam.m4
@@ -113,7 +113,7 @@ AC_DEFUN([CL_INTPARAM_CROSS],
 echo "#error \"Integer types long long and unsigned long long have different sizes!!\""
   fi
 fi
-AC_TRY_COMPILE([#include ], [static_assert(sizeof(char*) <= sizeof(intptr_t), "");],
+AC_TRY_COMPILE([#include ], [typedef int verify[2*(sizeof(char*)<=sizeof (intptr_t))-1];],
   [], [echo "#error \"Type char * does not fit into an intptr_t!!\""])
 _AC_COMPUTE_INT([sizeof (char *)], [pointer_size])
 pointer_bitsize=`expr $pointer_size '*' $char_bitsize`
@@ -290,7 +290,7 @@ AC_DEFUN([CL_INTPARAM_ALIGNOF],
 #else
 # define alignof(type)  offsetof (struct { char slot1; type slot2; }, slot2)
 #endif
-], [static_assert(alignof($1) == $n, "");],
+], [typedef int verify[2*(alignof($1) == $n) - 1];],
   [$2=$n; break;]
   [if test $n = 0; then $2=; break; fi])
 n=`expr $n '*' 2`


Bug#972033: pandas ftbfs with python3.9 as supported python version

2020-10-11 Thread Rebecca N. Palmer

Control: merge -1 972015
Control: found -1 1.0.5+dfsg-3
Control: forwarded -1 https://github.com/pandas-dev/pandas/issues/36296
Control: tags -1 fixed-upstream

pandas 1.1.3 may fix this, but moving to 1.1.x triggers #969648.



Bug#972051: CVE-2020-15866

2020-10-11 Thread Moritz Muehlenhoff
Package: mruby
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2020-15866:
https://github.com/mruby/mruby/issues/5042
https://github.com/mruby/mruby/commit/6334949ba69363cb909a57d6871895bd6d98bb6b
  



Bug#972050: CVE-2020-11939 CVE-2020-11940 CVE-2020-15471 CVE-2020-15472 CVE-2020-15473 CVE-2020-15474 CVE-2020-15475 CVE-2020-15476

2020-10-11 Thread Moritz Muehlenhoff
Source: ndpi
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

CVE-2020-15476
 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21780
 https://github.com/ntop/nDPI/commit/b69177be2fbe01c2442239a61832c44e40136c05
  
CVE-2020-15475
 https://github.com/ntop/nDPI/commit/6a9f5e4f7c3fd5ddab3e6727b071904d76773952
 
CVE-2020-15474
 https://github.com/ntop/nDPI/commit/23594f036536468072198a57c59b6e9d63caf6ce

CVE-2020-15473
 https://github.com/ntop/nDPI/commit/8e7b1ea7a136cc4e4aa9880072ec2d69900a825e
 
CVE-2020-15472
 https://github.com/ntop/nDPI/commit/b7e666e465f138ae48ab81976726e67deed12701
 
CVE-2020-15471
 https://github.com/ntop/nDPI/commit/61066fb106efa6d3d95b67e47b662de208b2b622
 
CVE-2020-11940
 https://github.com/ntop/nDPI/commit/3bbb0cd3296023f6f922c71d21a1c374d2b0a435
 https://securitylab.github.com/advisories/GHSL-2020-051_052-ntop-ndpi
  
CVE-2020-11939
 https://github.com/ntop/nDPI/commit/7ce478a58b4dd29a8d1e6f4e9df2f778613d9202
 https://securitylab.github.com/advisories/GHSL-2020-051_052-ntop-ndpi 



Bug#971778: [debian-mysql] Bug#971778: Bug#971778: Bug#971778: mariadb-client-core-10.5: mariadb-embedded is missing

2020-10-11 Thread Otto Kekäläinen
Control: tags -1 wontfix

Thanks, good to know you solved it for yourself.

I am leaving the bug report open for potential new commenters, but
tagging it as wontfix for now.



Bug#972048: Work-around

2020-10-11 Thread Francois Marier
reassign 972048 gnome-keyring
thanks

I've just realized two things:

1. The way to start ssh-agent isn't just "ssh-agent", it's actually

eval "$(ssh-agent)"

(https://unix.stackexchange.com/questions/48863/ssh-add-complains-could-not-open-a-connection-to-your-authentication-agent/48868#48868)

2. gnome-keyring-daemon is actually working, it's just no longer setting the
   SSH_AUTH_SOCK environment variable for some reason. I was able to work
   around this issue by adding this to my ~/.bashrc:

export SSH_AUTH_SOCK=/run/user/$(id -u)/keyring/ssh

(https://warlord0blog.wordpress.com/2020/01/29/gnome-keyring-and-ssh-agent/)

So I guess this might be from a recent GNOME change.

Francois

-- 
https://fmarier.org/



Bug#972053: CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165 CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629 CVE-2019-20630 CVE-2019-20631 CVE-2019-20632 CVE-2020-11558 CVE-2020

2020-10-11 Thread Moritz Muehlenhoff
Package: gpac
Version: 0.5.2-426-gc5ad4e4+dfsg5-5
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

CVE-2019-20161:
https://github.com/gpac/gpac/issues/1320
https://github.com/gpac/gpac/commit/7a09732d4978586e6284e84caa9c301b2fa5e956

CVE-2019-20162:
https://github.com/gpac/gpac/issues/1327
https://github.com/gpac/gpac/commit/3c0ba42546c8148c51169c3908e845c308746c77

CVE-2019-20163:
https://github.com/gpac/gpac/issues/1335
https://github.com/gpac/gpac/commit/5250afecbc770c8f26829e9566d5b226a3c5fa80 
(chunk #4)

CVE-2019-20165:
https://github.com/gpac/gpac/issues/1338
https://github.com/gpac/gpac/commit/5250afecbc770c8f26829e9566d5b226a3c5fa80 
(chunk #1)

CVE-2019-20170:
https://github.com/gpac/gpac/issues/1328
https://github.com/gpac/gpac/commit/16856430287cc10f495eb241910b4dc45b193e03

CVE-2019-20171:
https://github.com/gpac/gpac/issues/1337
https://github.com/gpac/gpac/commit/72cdc5048dead86bb1df7d21e0b9975e49cf2d97
https://github.com/gpac/gpac/commit/2bcca3f1d4605100bb27d3ed7be25b53cddbc75c

CVE-2019-20208:
https://github.com/gpac/gpac/issues/1348
https://github.com/gpac/gpac/commit/bcfcb3e90476692fe0d2bb532ea8deeb2a77580e 
(chunk #1)

CVE-2019-20628:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/commit/98b727637e32d1d4824101d8947e2dbd573d4fc8
https://github.com/gpac/gpac/issues/1269

CVE-2019-20629:
https://github.com/gpac/gpac/commit/2320eb73afba753b39b7147be91f7be7afc0eeb7
https://github.com/gpac/gpac/issues/1264

CVE-2019-20630:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1268

CVE-2019-20631:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1270

CVE-2019-20632:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1271

CVE-2020-11558:
https://github.com/gpac/gpac/commit/6063b1a011c3f80cee25daade18154e15e4c058c
https://github.com/gpac/gpac/issues/1440

CVE-2020-6630:
https://github.com/gpac/gpac/issues/1377
https://github.com/gpac/gpac/commit/c7e46e948ebe2d4a532539c7e714cdf655b84521

CVE-2020-6631:
https://github.com/gpac/gpac/issues/1378
https://github.com/gpac/gpac/commit/c7e46e948ebe2d4a532539c7e714cdf655b84521
  
While individual commits refs are listed above, this should really be fixed
via a new upstream release for bullseye, after all the current base version
is from 2015



Bug#929520: [debian-mysql] Bug#929520: Problem starting mariadb

2020-10-11 Thread Otto Kekäläinen
Control: tags -1 moreinfo

Hello!

If somebody wants to continue working on this issue, please submit
Merge Requests at https://salsa.debian.org/mariadb-team/mariadb-10.5

I promise to review them quickly.

If we don't get any contributions on this topic, I might end up
closing the issue in the coming months.



Bug#972052: base-files: cups does not run as cupsys:lp

2020-10-11 Thread Henrik Ahlgren
Package: cups-daemon
Version: 2.2.10-6+deb10u3
Severity: normal

The cupsys group was added to users-and-groups in 2005 (#290237). I
don't remember if cups used to run as such user back then, but now it
(very unfortunately) runs as root, and no such user is present in
the system. This is at least the case for the default cups-daemon
package. Please drop this user from the document.



Bug#866983: [debian-mysql] Bug#866983: mariadb spins at 100% forever during postinst

2020-10-11 Thread Otto Kekäläinen
Control: tags -1 moreinfo

Hello!

If somebody wants to continue working on this issue, please submit
Merge Requests at https://salsa.debian.org/mariadb-team/mariadb-10.5

I promise to review them quickly.

If we don't get any contributions on this topic, I might end up
closing the issue in the coming months.



Bug#962902: [debian-mysql] Bug#962902: server does not start

2020-10-11 Thread Otto Kekäläinen
Control: tags -1 moreinfo

Hello!

If somebody wants to continue working on this issue, please submit
Merge Requests at https://salsa.debian.org/mariadb-team/mariadb-10.5

I promise to review them quickly.

If we don't get any contributions on this topic, I might end up
closing the issue in the coming months.



Bug#925385: [debian-mysql] Bug#925385: /usr/bin/mysql: Poor MariaDB performance

2020-10-11 Thread Otto Kekäläinen
Control: tags -1 moreinfo

Hello!

If somebody wants to continue working on this issue, please submit
Merge Requests at https://salsa.debian.org/mariadb-team/mariadb-10.5

I promise to review them quickly.

If we don't get any contributions on this topic, I might end up
closing the issue in the coming months.



Bug#917872: Automatically uninstall/reinstall Mroonga plugin on upgrade

2020-10-11 Thread Otto Kekäläinen
Hello!

If somebody wants to continue working on this newcomer friendly tagged
bug report, please submit Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5
I promise to review them quickly.



Bug#972052: base-passwd: cups does not run as cupsys:lp

2020-10-11 Thread Henrik Ahlgren
reassign 972052 base-passwd
retitle 972052 base-passwd: cups does not run as cupsys:lp
thanks

My bad, wrong package.



Bug#972054: mariadb-10.5: FTBFS on hppa: test main.index_intersect fails

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23921
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source does build, and tests pass when this test is skipped
User: debian-h...@lists.debian.org
Usertags: hppa

The test main.index_intersect fails, but has been bypassed with an
entry in debian/unstable-tests.hppa in mariadb-10.5 (in Debian) and
reported to upstream, where you can find more details.

This bug is filed mainly to keep track of this exception in Debian builds.

If there are any hppa experts in Debian who could look into this, and
report their findings directly upstream at jira.mariadb.org so that an
improved test (or underlying code fix) can be produced, it would be
appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at
https://github.com/mariadb/server
- Debian-only fixes are welcome as Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5



Bug#972055: mariadb-10.5: FTBFS on alpha: test repair_symlink-5543 fails

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23920
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source does build, and tests pass when this test is skipped
User: debian-al...@lists.debian.org
Usertags: alpha

The test repair_symlink-5543 fails, but has been bypassed with an
entry in debian/unstable-tests.alpha in mariadb-10.5 (in Debian) and
reported to upstream, where you can find more details.

This bug is filed mainly to keep track of this exception in Debian builds.

If there are any alpha experts in Debian who could look into this, and
report their findings directly upstream at jira.mariadb.org so that an
improved test (or underlying code fix) can be produced, it would be
appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at
https://github.com/mariadb/server
- Debian-only fixes are welcome as Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5



Bug#972056: mariadb-10.5: FTBFS on powerpc: test main.grant_kill fails

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23915
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source does build, and tests pass when this test is skipped
User: debian-powe...@lists.debian.org
Usertags: powerpc

The test main.grant_kill fails, but has been bypassed with an entry in
debian/unstable-tests.powerpc in mariadb-10.5 (in Debian) and reported
to upstream, where you can find more details.

This bug is filed mainly to keep track of this exception in Debian builds.

If there are any powerpc experts in Debian who could look into this,
and report their findings directly upstream at jira.mariadb.org so
that an improved test (or underlying code fix) can be produced, it
would be appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at
https://github.com/mariadb/server
- Debian-only fixes are welcome as Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5



Bug#513964: base-passwd: please add netdev and powerdev groups to group.master

2020-10-11 Thread Henrik Ahlgren
Is the netdev group really obsolete? It seems to me that at least
network-manager, wpasupplicant and avahi-daemon rely on it (for
dbus.1/polkit-1). All packages add the group in .postinst.

Like with most of these old groups, the name is not optimal: it does
not really deal with "devices". Only /dev/rfkill is owned by that
group, and it has ACL set by (I believe) systemd-logind for the active
session user.

Please consider at least documenting the purpose of this group in
users-and-groups.txt.



Bug#971986: $wgRedirectOnLogin ignored

2020-10-11 Thread Kunal Mehta

tags 971986 fixed-upstream pending
thanks

This was fixed upstream in 
 which should 
be included in the next maintenance/security release.


-- Kunal

On 10/11/20 12:38 AM, Alain Knaff wrote:

Package: mediawiki
Version: 1:1.31.10-1~deb10u1

Hi,

The localSettings variable $wgRedirectOnLogin is ignored, apparently 
because the showReturnToPage function forgot to declare it global. This 
results in an unsightly warning in the web server log:


[Sun Oct 11 09:29:12.186114 2020] [proxy_fcgi:error] [pid 14121:tid 
139621415540480] [client 80.90.57.94:38882] AH01071: Got error 'PHP 
message: PHP Notice:  Undefined variable: wgRedirectOnLogin in 
/usr/share/mediawiki/includes/specials/helpers/LoginHelper.php on line 
68', referer: https://wiki.lll.lu/Special:UserLogin?returnto=HomePage



Adding the following to the top of the showReturnToPage in 
/usr/share/mediawiki/includes/specials/helpers/LoginHelper.php fixes the 
issue:

   global $wgRedirectOnLogin;


Thanks,

Alain





Bug#726137: Info received (DVD remains locked when requested to switch DVDs during Package Scan)

2020-10-11 Thread Mike Stanton
It also appears that every time it goes through a package install there is a 
mount message for the DVD Generated which requires a remount of the DVD media 
because it thinks the medisa CHANGED. This can add up to a lot of mount 
messages if you are doing a fresh install. The error happened during 
installations on two  machines, with two different DVD Readers. After a remount 
it appears multiple packages are being loaded so I can only presume that there 
are multiple package requests being submitted behind one mount request.

-Original Message-
From: Debian Bug Tracking System  
Sent: Sunday, October 11, 2020 3:27 PM
To: Mike Stanton 
Subject: Bug#726137: Info received (DVD remains locked when requested to switch 
DVDs during Package Scan)

Thank you for the additional information you have supplied regarding this Bug 
report.

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 Install System Team 

If you wish to submit further information on this problem, please send it to 
726...@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.

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


Bug#972057: mariadb-10.5: FTBFS on m68k: test suite fails to start

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23922
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source does build, but tests don't run and binaries are
unvalidated
User: debian-...@lists.debian.org
Usertags: m68k, 68k

As part of the MariaDB build there is a test suite that runs directly
after the build has finished, and validates that the binaries run at
least all the basic stuff as expected.

On amd64 the build log looks like this:

*
Source: 
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=amd64=1%3A10.5.5-3=1602231226=0
*
RULES.override_dh_auto_test
dh_testdir
# Skip unstable tests if such are defined for arch
cp mysql-test/unstable-tests debian/mysql-test-unstable-tests.orig
[ ! -f debian/unstable-tests.amd64 ] || cat
debian/unstable-tests.amd64 >> mysql-test/unstable-tests
# Run testsuite
# Don't use --mem here as official Debian builders and most Docker
systems don't have a large mem device available and
# would fail with errors on lack of disk space.
cd builddir/mysql-test && \
./mtr --force --testcase-timeout=120 --suite-timeout=540 \
  --retry=3 --parallel=4 --skip-rpl --suite=main \
--skip-test-list=unstable-tests
Logging: /<>/mysql-test/mysql-test-run.pl  --force
--testcase-timeout=120 --suite-timeout=540 --retry=3 --parallel=4
--skip-rpl --suite=main --skip-test-list=unstable-tests
vardir: /<>/builddir/mysql-test/var
Removing old var directory...
Creating var directory '/<>/builddir/mysql-test/var'...
Checking supported features...
MariaDB Version 10.5.5-MariaDB-3
 - SSL connections supported
Using suites: main
Collecting tests...
Installing system database...
*

However, on m68k builds the log just says:

*
Source: 
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=m68k=1%3A10.5.5-3=1602368619=0
*
RULES.override_dh_auto_test
dh_testdir
# Skip unstable tests if such are defined for arch
cp mysql-test/unstable-tests debian/mysql-test-unstable-tests.orig
[ ! -f debian/unstable-tests.m68k ] || cat debian/unstable-tests.m68k
>> mysql-test/unstable-tests
# Run testsuite
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
   dh_testroot -a -O--fail-missing
   dh_prep -a -O--fail-missing
rm -f -- debian/libmariadb-dev.substvars
debian/libmariadb-dev-compat.substvars debian/libmariadb3.substvars
debian/libmariadbd19.substvars debian/libmariadbd-dev.substvars
debian/mariadb-client-core-10.5.substvars
debian/mariadb-client-10.5.substvars
debian/mariadb-server-core-10.5.substvars
debian/mariadb-server-10.5.substvars debian/mariadb-backup.substvars
debian/mariadb-plugin-connect.substvars
debian/mariadb-plugin-s3.substvars
debian/mariadb-plugin-oqgraph.substvars
debian/mariadb-plugin-spider.substvars
debian/mariadb-plugin-gssapi-server.substvars
debian/mariadb-plugin-gssapi-client.substvars
debian/mariadb-plugin-cracklib-password-check.substvars
debian/mariadb-test.substvars
rm -fr -- debian/.debhelper/generated/libmariadb-dev/
debian/libmariadb-dev/ debian/tmp/
debian/.debhelper/generated/libmariadb-dev-compat/
debian/libmariadb-dev-compat/ debian/.debhelper/generated/libmariadb3/
debian/libmariadb3/ debian/.debhelper/generated/libmariadbd19/
debian/libmariadbd19/ debian/.debhelper/generated/libmariadbd-dev/
debian/libmariadbd-dev/
debian/.debhelper/generated/mariadb-client-core-10.5/
debian/mariadb-client-core-10.5/
debian/.debhelper/generated/mariadb-client-10.5/
debian/mariadb-client-10.5/
debian/.debhelper/generated/mariadb-server-core-10.5/
debian/mariadb-server-core-10.5/
debian/.debhelper/generated/mariadb-server-10.5/
debian/mariadb-server-10.5/
debian/.debhelper/generated/mariadb-backup/ debian/mariadb-backup/
debian/.debhelper/generated/mariadb-plugin-connect/
debian/mariadb-plugin-connect/
debian/.debhelper/generated/mariadb-plugin-s3/
debian/mariadb-plugin-s3/
debian/.debhelper/generated/mariadb-plugin-oqgraph/
debian/mariadb-plugin-oqgraph/
debian/.debhelper/generated/mariadb-plugin-spider/
debian/mariadb-plugin-spider/
debian/.debhelper/generated/mariadb-plugin-gssapi-server/
debian/mariadb-plugin-gssapi-server/
debian/.debhelper/generated/mariadb-plugin-gssapi-client/
debian/mariadb-plugin-gssapi-client/
debian/.debhelper/generated/mariadb-plugin-cracklib-password-check/
debian/mariadb-plugin-cracklib-password-check/
debian/.debhelper/generated/mariadb-test/ debian/mariadb-test/
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
RULES.override_dh_auto_install
dh_testdir
dh_testroot
*

The test suite is not starting at all!


If there are any m68k experts in Debian who could look into this, and
report their findings directly upstream at jira.mariadb.org so that an
improved test (or underlying code fix) can be produced, it would be
appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at

Bug#972058: libtickit-perl autopkgtest failure.

2020-10-11 Thread peter green

Package: libtickit-perl
Version: 0.71-1
Severity: serious

The libtickit-perl autopkgtest is failing on the unstable->testing migration 
tests (the plain unstable tests are not
up to date enough to be useful). On i386 and amd64 this failure is a regression 
(on the other architectures where
autopkgtest runs the tests also fail in plain testing, so it's "not a 
regression"). This is preventing the libtickit transition from fully completing in
testing.

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtickit-perl/7392469/log.gz
t/81tickit-io.t ... 
Use of uninitialized value in subroutine entry at /usr/lib/x86_64-linux-gnu/perl5/5.30/Tickit/Term.pm line 117.

Cannot construct Tickit::Term - No such file or directory at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Tickit.pm line 142.
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 

<--snip-->

Test Summary Report
---
t/81tickit-io.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=31, Tests=746,  3 wallclock secs ( 0.16 usr  0.03 sys +  2.16 cusr  0.33 
csys =  2.68 CPU)
Result: FAIL
autopkgtest [14:09:34]: test autodep8-perl-build-deps: ---]
autopkgtest [14:09:34]: test autodep8-perl-build-deps:  - - - - - - - - - - 
results - - - - - - - - - -
autodep8-perl-build-deps FAIL non-zero exit status 1




Bug#972061: mariadb-10.5: FTBFS on alpha: test main.alter_table_mdev539_maria fails

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23922
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source does build, and tests pass when this test is skipped
User: debian-al...@lists.debian.org
Usertags: alpha

The test main.alter_table_mdev539_maria fails, but has been bypassed
with an entry in debian/unstable-tests.alpha in mariadb-10.5 (in
Debian) and reported to upstream, where you can find more details.

This bug is filed mainly to keep track of this exception in Debian builds.

If there are any alpha experts in Debian who could look into this, and
report their findings directly upstream at jira.mariadb.org so that an
improved test (or underlying code fix) can be produced, it would be
appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at
https://github.com/mariadb/server
- Debian-only fixes are welcome as Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5



Bug#972060: mariadb-10.5: FTBFS on hppa: test repair_symlink-5543 fails

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23920
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source does build, and tests pass when this test is skipped
User: debian-h...@lists.debian.org
Usertags: hppa

The test repair_symlink-5543 fails, but has been bypassed with an
entry in debian/unstable-tests.hppa in mariadb-10.5 (in Debian) and
reported to upstream, where you can find more details.

This bug is filed mainly to keep track of this exception in Debian builds.

If there are any hppa experts in Debian who could look into this, and
report their findings directly upstream at jira.mariadb.org so that an
improved test (or underlying code fix) can be produced, it would be
appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at
https://github.com/mariadb/server
- Debian-only fixes are welcome as Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5



Bug#972059: mariadb-10.5: FTBFS on sparc64: test after build shows binaries faulty, segfaults/timeouts

2020-10-11 Thread Otto Kekäläinen
Source: mariadb-10.5
Version: 1:10.5.5-3
Forwarded: https://jira.mariadb.org/browse/MDEV-23916
Tags: upstream, confirmed, help, ftbfs
Severity: normal
Justification: source did not build work before, so nothing regressed,
and this is an unofficial arch in Debian
User: debian-sp...@lists.debian.org
Usertags: sparc64, sparc

The test suite that is run immediately after the sparc64 build fails
as the binaries timeout or segfault. This has been reported to
upstream, where you can find more details.

This bug is filed mainly to keep track of this exception in Debian builds.

If there are any sparc64 experts in Debian who could look into this,
and report their findings directly upstream at jira.mariadb.org so
that an improved test (or underlying code fix) can be produced, it
would be appreciated.

If you have a patch:
- Universal fixes are welcome directly upstream at
https://github.com/mariadb/server
- Debian-only fixes are welcome as Merge Requests at
https://salsa.debian.org/mariadb-team/mariadb-10.5



Bug#963675: Info received (Further details)

2020-10-11 Thread Rob Moss
Dear Maintainer,

This bug appears to have been resolved in r-bioc-rhdf5 2.32.3+dfsg-1. It
may be related to https://github.com/grimbough/rhdf5/issues/71, but I don't
know for sure.

All the best,
Rob

On Wed, 12 Aug 2020 at 21:47, Rob Moss  wrote:

> I was able to build the source package on my computer and install it, but
> I still receive the same error message when trying to load compound
> datasets. Any advice or suggestions would be greatly appreciated.
>
> All the best,
> Rob
>
> On Fri, 17 Jul 2020 at 12:21, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for the additional information you have supplied regarding
>> this Bug report.
>>
>> 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 R Packages Maintainers 
>>
>> If you wish to submit further information on this problem, please
>> send it to 963...@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.
>>
>> --
>> 963675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963675
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>


Bug#971984: installation-reports: installation report

2020-10-11 Thread Geert Stappers
Control: tag -1 moreinfo


On Sun, Oct 11, 2020 at 01:42:17AM -0400, WK Burke wrote:
> Package: installation-reports
> 
> Boot method: usb
> Image version: debian 10.0 iso
> 
> Machine: Dell Inspiron 15-3567
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [ ]
> Detect network card:[ ]
> Configure network:  [ ]
> Detect CD:  [ ]
> Load installer modules: [ ]
> Clock/timezone setup:   [ ]
> User/password setup:[ ]
> Detect hard drives: [ ]
> Partition hard drives:  [ ]
> Install base system:[ ]
> Install tasks:  [ ]
> Install boot loader:[ ]
> Overall install:[ ]
> 
> Comments/Problems:
> 
>and ideas you had during the initial install.>
> 
> 
> 
> 
> 
> ==
> Installer lsb-release:
> ==
> DISTRIB_ID=Debian
> DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
> DISTRIB_RELEASE="10 (buster) - installer build 20190702"
> X_INSTALLATION_MEDIUM=cdrom
> 
> uname -a: Linux zues 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) 
> x86_64 GNU/Linux



Please tell more about the installation success.

And that includes a message like "the install went just fine"   :-)




Regards
Geert Stappers
-- 
Silence is hard to parse



Bug#971777: linux-image-5.8.0-1-arm64: Enable NXP Layerscape PCIe Controller Support

2020-10-11 Thread Salvatore Bonaccorso
Source: linux
Source-Version: 5.9~rc6-1~exp1

Hi Matt,

On Sun, Oct 11, 2020 at 01:33:53PM +1100, Matt McBride wrote:
> 
> 
> On Sun, Oct 11, 2020, at 6:27 AM, Salvatore Bonaccorso wrote:
> > 
> > Is this correct? CONFIG_PCIE_LAYERSCAPE does not seem available as
> > option.
> > 
> > Regards,
> > Salvatore
> > 
> My apologies - I am getting mixed up between different projects I'm
> working with at the moment (kernel and U-Boot).

Ack, thanks for confirming!

> The snippet I have from my mainline kernel tree is:
> 
> > #
> > # DesignWare PCI Core Support
> > #
> > CONFIG_PCIE_DW=y
> > CONFIG_PCIE_DW_HOST=y
> > # CONFIG_PCIE_DW_PLAT_HOST is not set
> > CONFIG_PCI_LAYERSCAPE=y
> > CONFIG_PCI_HISI=y
> > CONFIG_PCIE_KIRIN=y
> > # CONFIG_PCI_MESON is not set
> > # CONFIG_PCIE_AL is not set
> > # end of DesignWare PCI Core Support
> 
> CONFIG_PCI_LAYERSCAPE=y should be all required, PCIE_DW and _DW_HOST
> are selected automatically when PCI_LAYERSCAPE is selected.

So we have enabled this recently, for the experimental upload based on
5.9~rc6 but it has not yet landed for unstable.

So it should be present in unstable once we move v5.9.y for unstable.

Regards,
Salvatore



Bug#971988: rails: CVE-2020-8264

2020-10-11 Thread Salvatore Bonaccorso
Source: rails
Version: 2:6.0.3.3+dfsg-1
Severity: normal
Tags: security upstream fixed-upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rails.

CVE-2020-8264[0]:
| Possible XSS Vulnerability in Action Pack in Development Mode

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-8264
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8264
[1] 
https://groups.google.com/g/rubyonrails-security/c/yQzUVfv42jk/m/oJWw-xhNAQAJ

Regards,
Salvatore



Bug#971989: unblock: thunderbird/1:78.3.2-1

2020-10-11 Thread Carsten Schoenert
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package thunderbird

The automatic migration testing for Thunderbird is containing some tests
for the packages jsunit and enigmail which currently prevents the
automatic migration of the thunderbird package to testing because the
tests are failing.

The enigmail package needs to be available in at least version 2.2 to
give a useful user experience. Thunderbird has included a version
requirement on enigmail that 2.2 is required.
This requirement can't get fulfilled currently in Debian unstable or
testing because the maintainers of the Enigmail package didn't prepared
and upoaded until now a new version.
There is s wishlist bug for updating enigmail to the most recent
version since a few weeks.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970111

The jsunit package is now also outdated and must fail against the
current Thunderbird versions.

So far I've no feedback from the enigmail maintainers, they got involved
within the communication with the security team while the upload of
thunderbird for stable/security got prepared.

The currently also reported uninstallability for the package
webext-exteditor/2.0.4-1 is intended as this version isn't working with
Thunderbird >= 78.

So I'd like to suggest to remove (if this is possible) the auto
migration testing of enigmail and jsunit against thunderbird. At least
please allow the migration of the Thunderbird related packages into
testing. I'm condidering removal requests for enigmail and jsunit in
testing.

Regards
Carsten

unblock thunderbird/1:78.3.2-1

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

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



Bug#971985: $validFooterLinks flattened without checking it is non-empty

2020-10-11 Thread Alain Knaff

Package: mediawiki
Version: 1:1.31.10-1~deb10u1

Hi,

In /usr/share/mediawiki/includes/skins/BaseTemplate.php after line 601, 
the $validFooterLinks is "flattened" without checking that it is non-empty.


This results in an unsightly warning in the web server log:

[Sun Oct 11 09:19:03.631271 2020] [proxy_fcgi:error] [pid 27294:tid 
139621082044160] [client 114.119.136.128:13642] AH01071: Got error 'PHP 
message: PHP Warning:  array_merge() expects at least 1 parameter, 0 
given in /usr/share/mediawiki/includes/skins/BaseTemplate.php on line 
603PHP message: PHP Warning:  count(): Parameter must be an array or an 
object that implements Countable in 
/usr/share/mediawiki/skins/MonoBook/includes/MonoBookTemplate.php on 
line 527'


Bracketing the infringing code with count() as follows fixes the issue:

if(count($validFooterLinks) > 0) {
$validFooterLinks = call_user_func_array(
'array_merge',
array_values( $validFooterLinks )
);
}

(i.e. don't flatten the array if it is empty)

Thanks,

Alain



Bug#971986: $wgRedirectOnLogin ignored

2020-10-11 Thread Alain Knaff

Package: mediawiki
Version: 1:1.31.10-1~deb10u1

Hi,

The localSettings variable $wgRedirectOnLogin is ignored, apparently 
because the showReturnToPage function forgot to declare it global. This 
results in an unsightly warning in the web server log:


[Sun Oct 11 09:29:12.186114 2020] [proxy_fcgi:error] [pid 14121:tid 
139621415540480] [client 80.90.57.94:38882] AH01071: Got error 'PHP 
message: PHP Notice:  Undefined variable: wgRedirectOnLogin in 
/usr/share/mediawiki/includes/specials/helpers/LoginHelper.php on line 
68', referer: https://wiki.lll.lu/Special:UserLogin?returnto=HomePage



Adding the following to the top of the showReturnToPage in 
/usr/share/mediawiki/includes/specials/helpers/LoginHelper.php fixes the 
issue:

  global $wgRedirectOnLogin;


Thanks,

Alain



Bug#971987: libdbus-1-3: gvfsd-dnssd crashed with segfault

2020-10-11 Thread pior...@gmail.com
Package: libdbus-1-3
Version: 1.12.20-0+deb10u1
Severity: normal

Dear Maintainer,

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

Just noticed segfault in my dmesg log. There is nothing unusual apart from 
that. System continues to run as normal.
I have Debian 10 Buster with backports enabled, kernel tained by Virtualbox and 
Nvidia GPU driver, but apart from that my system is normal.

Full errror in dmesg:
[Sun Oct 11 06:34:12 2020] gvfsd-dnssd[58109]: segfault at 9 ip 
7f14f016b08a sp 7ffde4bb9930 error 4 in 
libdbus-1.so.3.19.13[7f14f0148000+2e000]
[Sun Oct 11 06:34:12 2020] Code: d2 4c 8d 2c d5 00 00 00 00 4c 8b 34 d0 4d 85 
f6 75 18 eb 4c 0f 1f 40 00 48 89 df 41 ff d7 85 c0 74 16 4d 8b 36 4d 85 f6 74 
36 <49> 8b 76 08 4d 85 ff 75 e5 48 39 f3 75 ea 4d 85 e4 74 08 4c 03 6d


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

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

Versions of packages libdbus-1-3 depends on:
ii  libc62.28-10
ii  libsystemd0  246.6-1~bpo10+1

Versions of packages libdbus-1-3 recommends:
ii  dbus  1.12.20-0+deb10u1

libdbus-1-3 suggests no packages.

-- no debconf information



Bug#971518: [Pkg-net-snmp-devel] Bug#971518: libsnmp30: Depends on missing package

2020-10-11 Thread Craig Small
Hi Michael,
  I'm not sure what you have done here.

libsnmp30 5.7.3+dfsg-5+deb10u1 is the current version in stable and depends
on libperl5.28 [1]
libperl5.28 is in stable [2]

libperl5.30 is not in stable, but it is in testing/unstable [3]

If you are using stable, then libsnmp30 will pull in libperl5.28
If you were using testing then, you should be using libsnmp40 not libsnmp30
and libsnmp40 depends on libperl5.30.

I cannot really see where you have a setup where you:
* have libsnmp30
* don't have libsnmp40
* don't have libperl5.28

Maybe just installing libsnmp40 will fix things?

- Craig

1: https://packages.debian.org/buster/libsnmp30
2: https://packages.debian.org/buster/libperl5.28
3: https://packages.debian.org/search?keywords=libperl5.30

On Thu, 1 Oct 2020 at 16:24, Michael Rasmussen  wrote:

> Package: libsnmp30
> Version: 5.7.3+dfsg-5+b2
> Severity: serious
> Justification: Policy 7.2
>
> Dear Maintainer,
>
> sudo apt install libsnmp30
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  libsnmp30 : Depends: libperl5.28 (>= 5.28.0) but it is not installable
> E: Unable to correct problems, you have held broken packages.
>
> apt policy libperl5.28
> libperl5.28:
>   Installed: (none)
>   Candidate: (none)
>   Version table:
>
> dpkg --get-selections |grep libperl5
> libperl5.30:amd64   install
> libperl5.30:i386install
>
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (500, 'unstable-debug')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_DK.UTF-8
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages libsnmp30 depends on:
> ii  libc6 2.31-3
> ii  libpci3   1:3.7.0-3
> ii  libperl5.30   5.30.3-4
> ii  libsensors5   1:3.6.0-2
> ii  libsnmp-base  5.9+dfsg-3
> ii  libssl1.1 1.1.1g-1
> ii  libwrap0  7.6.q-30
>
> libsnmp30 recommends no packages.
>
> libsnmp30 suggests no packages.
>
> -- no debconf information
>
> 
>
> This mail was virus scanned and spam checked before delivery.
> This mail is also DKIM signed. See header dkim-signature.
>
> ___
> Pkg-net-snmp-devel mailing list
> pkg-net-snmp-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-net-snmp-devel


Bug#969965: [Pkg-kbd-devel] Bug#969965: text installer: unable to switch keyboard layouts - libkeymap.so.1 missing

2020-10-11 Thread Andreas Henriksson
Hello Holger,

On Tue, Oct 06, 2020 at 11:25:06PM +, Holger Wansing wrote:
> Hi,
> 
> Am Dienstag, 6. Oktober 2020 schrieb Andreas Henriksson: 
> > Could you please test rebuilding kbd with --enable-libkeymap to
> > --disable-libkeymap in debian/rules?
> 
> sbuild fails when I try it like that.
> A build log is attached.
> Debugging this is somewhat out of my skills, sorry.

I've uploaded a new version that implements the above suggestion
and would very much appreciate if you could test and give feedback
on where we ended up when you have chance to do so.

Regards,
Andreas Henriksson



Bug#971993: openvpn: OpenVPN's man page suggests to run the daemon as nobody.nogroup

2020-10-11 Thread dirdi
Package: openvpn
Version: 2.5~rc2-1
Severity: normal
Tags: upstream security
X-Debbugs-Cc: deb...@dirdi.name, Debian Security Team 

OpenVPN's man page suggests to run the daemon as nobody.nogroup. This is
a bad habit since other daemons that also run as nobody.nogroup could
interfere with the OpenVPN daemon. Instead OpenVPN should add a dedicated 
system user during installation:
> adduser --quiet --system --group --home /nonexistent --no-create-home 
> Debian-openvpn

The advice to the user should then be to run the daemon as 
Debian-openvpn.Debian-openvpn instead of
nobody.nogroup. Therefore the man page should be patched:
- This option can be combined with --user nobody to allow restarts triggered by 
the SIGUSR1 signal.
+ This option can be combined with --user Debian-openvpn to allow restarts 
triggered by the SIGUSR1 signal.

... and:
- By  setting user to nobody or somebody similarly unprivileged, the hostile 
party would be limited in what damage they could cause.
+ By  setting user to Debian-openvpn, the hostile party would be limited in 
what damage they could cause.

... as well as the following sample configuration files:
/usr/share/doc/openvpn/examples/sample-config-files/client.conf
/usr/share/doc/openvpn/examples/sample-config-files/server.conf
/usr/share/doc/openvpn/examples/sample-config-files/tls-home.conf
/usr/share/doc/openvpn/examples/sample-config-files/tls-home.conf
/usr/share/doc/openvpn/examples/sample-config-files/tls-office.conf
/usr/share/doc/openvpn/examples/sample-config-files/tls-office.conf
/usr/share/doc/openvpn/examples/sample-config-files/xinetd-client-config
/usr/share/doc/openvpn/examples/sample-config-files/xinetd-server-config


Upstream bugreport: https://community.openvpn.net/openvpn/ticket/1335

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

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

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  iproute2   5.8.0-1
ii  libc6  2.31-3
ii  liblz4-1   1.9.2-2
ii  liblzo2-2  2.10-2
ii  libpam0g   1.3.1-5
ii  libpkcs11-helper1  1.26-1+b1
ii  libssl1.1  1.1.1g-1
ii  libsystemd0246.6-1
ii  lsb-base   11.1.0

Versions of packages openvpn recommends:
ii  easy-rsa  3.0.6-1

Versions of packages openvpn suggests:
ii  openssl   1.1.1g-1
pn  openvpn-systemd-resolved  
pn  resolvconf

-- debconf information excluded



Bug#901499: #901499 ITP: php-yubitwee -- YubiKey OTP Validator library

2020-10-11 Thread Joost van Baal-Ilić
I won't package this software for Debian, and I don't think anybody should:
upsteam says:

"the correct thing to be doing is using U2F, so do not use this library if
you are writing new software, please investigate U2F as that will be more
secure than using the proprietary YubiCo solution for verifying hardware
tokens!"

(at https://git.tuxed.net/fkooman/php-yubitwee/about/ ).

Bye,

Joost



Bug#971997: libxrdesktop-0.15-0 also needs Breaks+Replaces: libxrdesktop-0.13-0

2020-10-11 Thread Adrian Bunk
Package: libxrdesktop-0.15-0
Version: 0.15.1-4
Severity: serious

libxrdesktop-0.13-0 was in unstable/testing and buster-backports,
in buster-backports it is even still as cruft.

Unpacking libxrdesktop-0.15-0:amd64 (0.15.1-4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-qhhvoQ/223-libxrdesktop-0.15-0_0.15.1-4_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/glib-2.0/schemas/org.xrdesktop.gschema.xml', 
which is also in package libxrdesktop-0.13-0:amd64 0.13.2-1

Please add Breaks+Replaces: libxrdesktop-0.13-0,
similar to what is already done for libxrdesktop-0.14-0.



Bug#971998: libbinio: watchfile broken, should point to github as upstream moved there

2020-10-11 Thread Tobias Frost
Source: libbinio
Version: 1.5+dfsg-0.1
Severity: wishlist

Currently the watch file is pointing to 
https://sourceforge.net/projects/libbinio/files/libbinio/,
which is outdated and only has 1.4
The project seems to have to moved to github, where the 1.5 is available.
github: https://github.com/adplug/libbinio

-- 
tobi



Bug#972000: phpmyadmin: CVE-2020-26935

2020-10-11 Thread Salvatore Bonaccorso
Source: phpmyadmin
Version: 4:4.9.5+dfsg1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for phpmyadmin.

CVE-2020-26935[0]:
| An issue was discovered in SearchController in phpMyAdmin before 4.9.6
| and 5.x before 5.0.3. A SQL injection vulnerability was discovered in
| how phpMyAdmin processes SQL statements in the search feature. An
| attacker could use this flaw to inject malicious SQL in to a query.


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-26935
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26935
[1] https://www.phpmyadmin.net/security/PMASA-2020-6/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#970524: (no subject)

2020-10-11 Thread Angel Abad
Hi! I have the same problem with wokkel package.

Thanks!



Bug#971990: ITP: rpcsvc-proto -- RPC protocol compiler and definitions

2020-10-11 Thread Aurelien Jarno
Package: wnpp
Severity: wishlist
Owner: Aurelien Jarno 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-gl...@lists.debian.org

* Package name: rpcsvc-proto
  Version : 1.4.2
  Upstream Author : Thorsten Kukuk 
* URL : https://github.com/thkukuk/rpcsvc-proto
* License : BSD-3-clause
  Programming Lang: C
  Description : RPC protocol compiler and definitions

rpcgen is a tool that generates C code to implement an RPC protocol. The input
to rpcgen is a language similar to C known as RPC Language (Remote Procedure
Call Language).

This package also includes several rpcsvc header files and RPC protocol
definitions from SunRPC sources that were previously shipped by glibc.


The glibc SunRPC implementation has been removed in glibc version 2.32.
It is replaced by rpcsvc-proto and libtirpc, which also brings new
features (IPv6, Kerberos support, etc.). This package will be maintained
within the glibc team.



Bug#971962: vlc: VAAPI playback doesn't work

2020-10-11 Thread Sebastian Ramacher
Control: reassign -1 src:mesa 20.1.9-1

On 2020-10-10 18:16:58 +0200, Tino Mettler wrote:
> Package: vlc
> Version: 3.0.11.1-2+b1
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> playback using VAAPI doesn't work on my system with the amdgpu driver.
> 
> This results in high CPU usage and stuttering video e.g. with 4k 60FPS HEVC
> even on a brand new AMD Ryzen 5 (6 Cores/12 Threads).  I tried mpv and
> playback using VAAPI works with smooth video and very low CPU usage.
> 
> There are reports that this may be a Mesa issue.
> 
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/1193
> 
> However, I tried to build Mesa with a fix applied and it still didn't work. 
> So I open this bug and hope to see a coordinated fix for this issue, be it
> in Mesa or in VLC.

The fix on mesa's side was reverted, so I'm not sure why you are
reporting this against vlc. Reassigning to mesa.

Cheers

> 
> Regards,
> Tino
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.9.0-rc8 (SMP w/12 CPU threads)
> Kernel taint flags: TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages vlc depends on:
> ii  vlc-bin  3.0.11.1-2+b1
> ii  vlc-plugin-base  3.0.11.1-2+b1
> ii  vlc-plugin-qt3.0.11.1-2+b1
> ii  vlc-plugin-video-output  3.0.11.1-2+b1
> 
> Versions of packages vlc recommends:
> pn  vlc-l10n   
> pn  vlc-plugin-access-extra
> pn  vlc-plugin-notify  
> pn  vlc-plugin-samba   
> pn  vlc-plugin-skins2  
> pn  vlc-plugin-video-splitter  
> pn  vlc-plugin-visualization   
> 
> Versions of packages vlc suggests:
> pn  vlc-plugin-fluidsynth  
> pn  vlc-plugin-jack
> pn  vlc-plugin-svg 
> 
> Versions of packages libvlc-bin depends on:
> ii  libc62.31-3
> ii  libvlc5  3.0.11.1-2+b1
> 
> Versions of packages libvlc5 depends on:
> ii  libc62.31-3
> ii  libvlccore9  3.0.11.1-2+b1
> 
> Versions of packages libvlc5 recommends:
> ii  libvlc-bin  3.0.11.1-2+b1
> 
> Versions of packages libvlccore8 depends on:
> ii  libc62.31-3
> ii  libdbus-1-3  1.12.20-1
> ii  libidn11 1.33-2.4
> 
> Versions of packages libvlccore8 recommends:
> pn  libproxy-tools  
> 
> Versions of packages vlc-bin depends on:
> ii  libc6   2.31-3
> ii  libvlc-bin  3.0.11.1-2+b1
> ii  libvlc5 3.0.11.1-2+b1
> 
> Versions of packages vlc-plugin-base depends on:
> ii  liba52-0.7.4 0.7.4-20
> ii  libarchive13 3.4.3-2
> ii  libaribb24-0 1.0.3-dmo2

We don't support dmo packages. So this is usally a wontfix.

> ii  libasound2   1.2.3.2-1
> ii  libass9  2:0.14.0-dmo2
> ii  libavahi-client3 0.8-3
> ii  libavahi-common3 0.8-3
> ii  libavc1394-0 0.5.4-5
> ii  libavcodec58 10:4.3.1-dmo3
> ii  libavformat5810:4.3.1-dmo3
> ii  libavutil56  10:4.3.1-dmo3
> ii  libbasicusageenvironment12:2020.08.19-dmo1
> ii  libbluray2   2:1.2.0-dmo3
> ii  libc62.31-3
> ii  libcairo21.16.0-4
> ii  libcddb2 1.3.2-6+b1
> ii  libchromaprint1  1:1.5.0-dmo1
> ii  libdav1d41:0.7.1-dmo1
> ii  libdbus-1-3  1.12.20-1
> ii  libdc1394-25 2.2.6-3
> ii  libdca0  1:0.0.7-dmo1
> ii  libdvbpsi10  1:1.3.3-dmo1
> ii  libdvdnav4   6.1.0-1+b1
> ii  libdvdread8  6.1.1-2
> ii  libebml5 1:1.4.0-dmo1
> ii  libfaad2 2.9.2-1
> ii  libflac8 1.3.3-1
> ii  libfontconfig1   2.13.1-4.2
> ii  libfreetype6 2.10.2+dfsg-3
> ii  libfribidi0  1.0.8-2
> ii  libgcc-s110.2.0-13
> ii  libgcrypt20  1.8.6-2
> ii  libglib2.0-0 2.66.0-2
> ii  libgnutls30  3.6.15-4
> ii  libgpg-error01.38-2
> ii  libgroupsock82:2020.08.19-dmo1
> ii  libharfbuzz0b2.6.7-1
> pn  libixml10

Your installation seems to be broken.

> ii  libjpeg62-turbo  1:2.0.5-1.1
> ii  libkate1 0.4.1-11
> ii  liblirc-client0

Bug#971991: trying to use proxy raises exception

2020-10-11 Thread Nis Martensen
Package: python3-debianbts
Version: 3.0.2~bpo10+1
Severity: normal
X-Debbugs-Cc: nis.marten...@web.de

Proxy support in python3-debianbts does not work. The underlying reason
may be a bug in pysimplesoap:

>>> import debianbts
>>> debianbts.set_soap_proxy('http://192.168.12.34:3128')
>>> debianbts.get_bugs('reportbug')
Calling get_bugs with positional arguments is deprecated, please use keyword 
arguments instead.
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 427, in 
get_bugs
soap_client = _build_soap_client()
  File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 522, in 
_build_soap_client
return SoapClient(**_soap_client_kwargs)
  File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 140, in 
__init__
self.http = Http(timeout=timeout, cacert=cacert, proxy=proxy, 
sessions=sessions)
  File "/usr/lib/python3/dist-packages/pysimplesoap/transport.py", line 92, in 
__init__
import socks
ModuleNotFoundError: No module named 'socks'
>>>


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

Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU threads)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.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 python3-debianbts depends on:
ii  python3   3.7.3-1
ii  python3-pysimplesoap  1.16.2-1

python3-debianbts recommends no packages.

python3-debianbts suggests no packages.

-- no debconf information



Bug#971987: libdbus-1-3: gvfsd-dnssd crashed with segfault

2020-10-11 Thread Simon McVittie
Control: reassign -1 gvfs-backends 1.38.1-5
Control: tags -1 + moreinfo

On Sun, 11 Oct 2020 at 09:04:18 +0100, pior...@gmail.com wrote:
> [Sun Oct 11 06:34:12 2020] gvfsd-dnssd[58109]: segfault at 9 ip 
> 7f14f016b08a sp 7ffde4bb9930 error 4 in 
> libdbus-1.so.3.19.13[7f14f0148000+2e000]

This does not *necessarily* indicate a bug in libdbus-1-3; it *might*
be a bug in libdbus-1-3, but it could equally well be gvfsd-dnssd (or
some other library used by gvfsd-dnssd) passing an invalid pointer to a
function in libdbus-1-3. I would guess it's most likely to be something
to do with Avahi.

It's often better to report crashes as a bug in whatever program
is crashing, in this case gvfsd-dnssd in the gvfs-backends package,
and let the maintainer of that component reassign it if appropriate:
that gives us more information about the packages and dependencies
involved. Please send the output of "reportbug --template gvfs-backends"
to this bug address to confirm what the versions of its dependencies are.

If this crash does not happen again, there is probably nothing we can
do about it: there isn't really enough information in this crash report
to know where the bug is, much less to fix it.

If it happens repeatedly, installing the systemd-coredump package is the
easiest way to get more information about a crash in a background program.
Please see  for
more details.

Thanks,
smcv



Bug#956106: shorewall: unable to insert jump to DOCKER-ISOLATION-STAGE-1 rule in FORWARD chain

2020-10-11 Thread Dr. Robert Suna
Package: shorewall
Version: 5.2.3.2-1
Followup-For: Bug #956106

If docker is running and shorewall is restarted, then on next docker container 
start troubles rises due to deleted iptable chain:

# docker-compose up -d
Creating network "tranm_default" with the default driver
ERROR: unable to insert jump to DOCKER-ISOLATION-STAGE-1 rule in FORWARD chain: 
 (iptables failed: iptables --wait -I FORWARD -j DOCKER-ISOLATION-STAGE-1: 
iptables v1.8.2 (nf_tables): Chain 'DOCKER-ISOLATION-STAGE-1' does not exist
Try `iptables -h' or 'iptables --help' for more information.
 (exit status 2))

This isuue seems to be fixed in shorewall release 5.2.3.7 (copy from release 
notes)

1)  When DOCKER=Yes, if both the DOCKER-ISOLATE and
DOCKER-ISOLATE-STAGE-1 existed then the DOCKER-ISOLATE-STAGE-*
chains were not preserved through shorewall state changes.
That has been corrected so that both chains are preserved if
present.

pls. upgrade the debian package to a more actual version. At time of writing 
shorewall is already at version 5.2.8

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

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

Versions of packages shorewall depends on:
ii  bc 1.07.1-2+b1
ii  debconf [debconf-2.0]  1.5.71
ii  iproute2   4.20.0-2
ii  iptables   1.8.2-4
ii  lsb-base   10.2019051400
ii  perl   5.28.1-6+deb10u1
ii  shorewall-core 5.2.3.2-1

Versions of packages shorewall recommends:
pn  libnetfilter-cthelper0  

Versions of packages shorewall suggests:
ii  make   4.2.1-1.2
pn  shorewall-doc  

-- Configuration Files:
/etc/shorewall/conntrack [Errno 13] Keine Berechtigung: 
'/etc/shorewall/conntrack'
/etc/shorewall/params [Errno 13] Keine Berechtigung: '/etc/shorewall/params'

-- debconf information excluded



Bug#971992: libntirpc3.3: symbols declares dependency on non-available package libntirpc3 (>= 3.3)

2020-10-11 Thread Aurelien Jarno
Package: libntirpc3.3
Version: 3.3-1
Severity: serious

Dear maintainer,

In the latest upload, the library package has been renamed from
libntirpc3 to libntirpc3.3. However the symbols file hasn't been
adjusted properly, it still relates to libntirpc3:

| libntirpc.so.3.3 libntirpc3 #MINVER#

This is cause the following lintian warning:

| W: libntirpc3.3: symbols-declares-dependency-on-other-package libntirpc3 
#MINVER#

But most importantly all packages built against it are now uninstallable
as they depends on libntirpc3 (>= 3.3), which doesn't exist. See for
example the binaries produced by nfs-ganesha.

Regards,
Aurelien



Bug#971987: (no subject)

2020-10-11 Thread pior...@gmail.com
Thanks for your reply.


systemd-coredump installed.

This is output of reportbug:

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

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

Versions of packages gvfs-backends depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gvfs 1.38.1-5
ii  gvfs-common  1.38.1-5
ii  gvfs-daemons 1.38.1-5
ii  gvfs-libs1.38.1-5
ii  libarchive13 3.3.3-4+deb10u1
ii  libavahi-client3 0.7-4+b1
ii  libavahi-common3 0.7-4+b1
ii  libavahi-glib1   0.7-4+b1
ii  libc62.28-10
ii  libcdio-cdda210.2+0.94+2-4
ii  libcdio-paranoia210.2+0.94+2-4
ii  libcdio182.0.0-2
ii  libgcrypt20  1.8.4-5
ii  libgdata22   0.17.9-3
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgoa-1.0-0b3.30.1-2
ii  libgphoto2-6 2.5.22-3
ii  libgphoto2-port122.5.22-3
ii  libgudev-1.0-0   232-2
ii  libimobiledevice61.2.1~git20181030.92c5462-2
ii  libmtp9  1.1.16-2
ii  libnfs12 3.0.0-2
ii  libplist32.0.1~git20190104.3f96731-1
ii  libpolkit-gobject-1-00.105-25
ii  libsmbclient 2:4.9.5+dfsg-5+deb10u1
ii  libsoup2.4-1 2.64.2-2
ii  libusb-1.0-0 2:1.0.22-2
ii  libxml2  2.9.4+dfsg1-7+b3
ii  psmisc   23.2-1

Versions of packages gvfs-backends recommends:
ii  gnome-keyring  3.28.2-5

Versions of packages gvfs-backends suggests:
pn  bluez-obexd   
pn  samba-common  

-- no debconf information



Bug#971994: dmarc-cat: doesn't work with xml.gz files

2020-10-11 Thread Dimitris

Package: dmarc-cat
Version: 0.12.0-1
Severity: normal


hey,
thanks for packaging this for debian

one thing i noticed, it doesn't work with xml.gz files, as stated by 
upstream 
(https://github.com/keltia/dmarc-cat/issues/2#issuecomment-458082174)


$ dmarc-cat -v /tmp/mail.ru\!stinpriza.org\!1602288000\!1602374400.xml.gz
2020/10/11 14:31:49 Analyzing 
/tmp/mail.ru!stinpriza.org!1602288000!1602374400.xml.gz
2020/10/11 14:31:49 Error: file 
/tmp/mail.ru!stinpriza.org!1602288000!1602374400.xml.gz:: unmarshall: 
XML syntax error on line 1: illegal character code U+001F


$ dmarc-cat -D /tmp/mail.ru\!stinpriza.org\!1602288000\!1602374400.xml.gz
2020/10/11 14:34:43 debug mode
2020/10/11 14:34:43 Analyzing 
/tmp/mail.ru!stinpriza.org!1602288000!1602374400.xml.gz
2020/10/11 14:34:43 
file=/tmp/mail.ru!stinpriza.org!1602288000!1602374400.xml.gz
2020/10/11 14:34:43 
file=/tmp/mail.ru!stinpriza.org!1602288000!1602374400.xml.gz

2020/10/11 14:34:43 HandleSingleFile
2020/10/11 14:34:43 typ=1
2020/10/11 14:34:43 a={Name:"-", r:(*os.File)(0xc10058)}
2020/10/11 14:34:43 xml=[]byte{0x1f, 0x8b, 0x8, 0x8, 0xe2, 0x3e, 0x82, 
0x5f, 0x2, 0xff, 0x6d, 0x61, 0x69, 0x6c, 0x2e, 0x72, 0x75, 0x21, 0x73, 
0x74, 0x69, 0x6e, 0x70, 0x72, 0x69, 0x7a, 0x61, 0x2e, 0x6f, 0x72, 0x67, 
0x21, 0x31, 0x36, 0x30, 0x32, 0x32, 0x38, 0x38, 0x30, 0x30, 0x30, 0x21, 
0x31, 0x36, 0x30, 0x32, 0x33, 0x37, 0x34, 0x34, 0x30, 0x30, 0x2e, 0x78, 
0x6d, 0x6c, 0x0, 0x75, 0x53, 0x4b, 0x72, 0xa3, 0x30, 0x10, 0xdd, 0xcf, 
0x29, 0xb2, 0xf3, 0x2a, 0x8, 0x8, 0xb6, 0x49, 0xaa, 0xa3, 0xe4, 0x2, 
0xd9, 0xcc, 0x5, 0x54, 0xb2, 0x68, 0x8c, 0x2a, 0x20, 0xa9, 0xf4, 0x49, 
0x9c, 0x9c, 0x7e, 0x5a, 0x60, 0x3c, 0xce, 0xb8, 0x66, 0x43, 0x77, 0x3f, 
0xfa, 0xf3, 0x5e, 0x4b, 0x82, 0x97, 0xd3, 0x34, 0xde, 0x7d, 0xa0, 0xf, 
0xda, 0x9a, 0xe7, 0x4d, 0x55, 0x94, 0x9b, 0x3b, 0x34, 0xca, 0x76, 0xda, 
0x1c, 0x9f, 0x37, 0x29, 0xf6, 0xf7, 0xed, 0xe6, 0x85, 0xff, 0x82, 0x1e, 
0xb1, 0x3b, 0x48, 0xf5, 0xce, 0xc1, 0xa3, 0xb3, 0x3e, 0x8a, 0x9, 0xa3, 
0xec, 0x64, 0x94, 0x1c, 0xac, 0x3f, 0xa, 0x23, 0x27, 0xe4, 0x6f, 0x52, 
0x8f, 0xc5, 0xef, 0x4, 0xec, 0x82, 0x0, 0x4e, 0x84, 0xf1, 0x6e, 0x92, 
0x5e, 0x89, 0x90, 0x5c, 0xae, 0x7c, 0x55, 0xd6, 0xbb, 0x22, 0xe3, 0x85, 
0xa7, 0xdc, 0x25, 0x3, 0xf0, 0x14, 0xbd, 0x14, 0xca, 0x9a, 0x28, 0x55, 
0x14, 0xda, 0xf4, 0x96, 0xf, 0x31, 0xba, 0x27, 0xc6, 0x6, 0x1c, 0x2f, 
0xe9, 0x2c, 0xdb, 0xfb, 0x8c, 0x50, 0xe1, 0x6d, 0xc5, 0xca, 0x4d, 0x77, 
0x7c, 0xbb, 0xab, 0x1f, 0xab, 0xb6, 0x7e, 0x6c, 0xca, 0xed, 0x7e, 0x57, 
0xd6, 0x6d, 0xb9, 0xdb, 0x57, 0x64, 0xeb, 0xb6, 0x2d, 0xcb, 0x12, 0xd8, 
0xdf, 0x44, 0x20, 0x11, 0x28, 0xbc, 0x34, 0x47, 0xa2, 0x7b, 0xc0, 0xa3, 
0x36, 0xfc, 0x3a, 0x71, 0x41, 0x0, 0x4d, 0x37, 0xc3, 0xf, 0xfb, 0xa6, 
0xc9, 0x70, 0x8e, 0x81, 0x5d, 0x97, 0xb2, 0x9b, 0xbd, 0x38, 0x3b, 0x6a, 
0xf5, 0x25, 0x5c, 0x3a, 0x8c, 0x3a, 0xc, 0x98, 0x47, 0x59, 0xe2, 0x6f, 
0x78, 0x88, 0xda, 0x38, 0xaf, 0xbf, 0x65, 0x41, 0x8b, 0xa2, 0x2e, 0xb, 
0xa, 0xb2, 0x7b, 0xd7, 0x13, 0xf7, 0xc0, 0x16, 0x7, 0x64, 0x70, 0xfd, 
0x1c, 0x66, 0xb, 0x8e, 0x1b, 0x6b, 0x10, 0x98, 0xe3, 0x10, 0x56, 0x9f, 
0x1c, 0x70, 0x2a, 0xf2, 0x2a, 0x53, 0xca, 0xe, 0x7d, 0x6f, 0x86, 0x7a, 
0xa4, 0x85, 0x67, 0x6b, 0x3f, 0xa9, 0xd4, 0x26, 0xaf, 0x50, 0x68, 0xc7, 
0xab, 0xa6, 0x2d, 0xea, 0x6d, 0x55, 0x34, 0xdb, 0xa2, 0xad, 0xa8, 0xd5, 
0xe5, 0x7, 0x28, 0x9b, 0x4c, 0xe4, 0x35, 0xb0, 0xc5, 0x59, 0x75, 0xe0, 
0x87, 0x1c, 0x13, 0x9, 0xce, 0x3a, 0x74, 0x70, 0x36, 0xe8, 0x48, 0x57, 
0xe6, 0xcc, 0xe4, 0x1a, 0x81, 0x99, 0x7e, 0x4f, 0x27, 0x45, 0xf8, 0xac, 
0x24, 0xb, 0x58, 0xe2, 0x59, 0xa, 0xbb, 0xed, 0xc8, 0x66, 0x76, 0xba, 
0x43, 0x13, 0x75, 0xaf, 0xe9, 0x36, 0x72, 0x18, 0x50, 0x76, 0xe8, 0x45, 
0xef, 0xed, 0xc4, 0x95, 0x54, 0xb6, 0xb7, 0x46, 0x9f, 0x8a, 0x7f, 0x76, 
0x77, 0x9d, 0x4, 0xec, 0x47, 0xbd, 0x4c, 0x71, 0x10, 0x1e, 0x43, 0x1a, 
0x63, 0x58, 0x28, 0xac, 0xfb, 0xff, 0x6f, 0xb7, 0xf5, 0x24, 0x82, 0xb2, 
0xe, 0xf9, 0x94, 0xbb, 0x12, 0xe5, 0x39, 0x80, 0xa5, 0xd3, 0x59, 0xee, 
0x39, 0x58, 0xf5, 0xfc, 0x1c, 0xc5, 0xd6, 0x8d, 0xb3, 0xcb, 0xa3, 0xf9, 
0x3, 0xc8, 0x56, 0x3d, 0xa0, 0x66, 0x3, 0x0, 0x0}
2020/10/11 14:34:43 Error: file 
/tmp/mail.ru!stinpriza.org!1602288000!1602374400.xml.gz:: unmarshall: 
XML syntax error on line 1: illegal character code U+001F



when gunzipped, it reads xml file fine :

$ dmarc-cat /tmp/mail.ru\!stinpriza.org\!1602288000\!1602374400.xml
dmarc-cat 0.12.0,parallel/j4 by Ollivier Robert

Reporting by: Mail.Ru — dmarc_supp...@corp.mail.ru
From 2020-10-10 03:00:00 +0300 EEST to 2020-10-11 03:00:00 +0300 EEST

Domain: stinpriza.org
.
.


no such problem with zip files.

thanks,
d.


-- System Information:
Distributor ID:Devuan
Description:Devuan GNU/Linux 4 (chimaera/ceres)
Release:testing/unstable
Codename:n/a
Architecture: x86_64

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled


Bug#971995: python-greenlet ftbfs with python3-defaults (python3.9) from experimental

2020-10-11 Thread Emmanuel Arias
Package: src:python-greenlet
Version: 0.4.15-4.2
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9


Python 3.9 doesn't define _Py_DEC_REFTOTAL anymore [0]

A patch for upstream already was merged [1].

Please, consider new upstream release.

[0]
https://github.com/python/cpython/commit/49932fec62c616ec88da52642339d83ae719e924
[1] https://github.com/python-greenlet/greenlet/pull/161/files

-

Part of build:


[...]
building 'greenlet' extension
creating build
creating build/temp.linux-x86_64-3.9
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG
-g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
-Werror=format-security -g -fwrapv -O2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/python3.9 -c greenlet.c -o
build/temp.linux-x86_64-3.9/greenlet.o
greenlet.c: In function ‘g_initialstub’:
greenlet.c:823:4: warning: ‘PyEval_CallObjectWithKeywords’ is deprecated
[-Wdeprecated-declarations]
  823 |result = PyEval_CallObjectWithKeywords(
  |^~
In file included from /usr/include/python3.9/Python.h:145,
 from greenlet.h:8,
 from greenlet.c:5:
/usr/include/python3.9/ceval.h:17:43: note: declared here
   17 | Py_DEPRECATED(3.9) PyAPI_FUNC(PyObject *)
PyEval_CallObjectWithKeywords(
  |
^
greenlet.c: In function ‘green_dealloc’:
greenlet.c:1046:4: error: ‘_Py_DEC_REFTOTAL’ undeclared (first use in
this function); did you mean ‘_Py_DECREF’?
 1046 |_Py_DEC_REFTOTAL;
  |^~~~
  |_Py_DECREF
greenlet.c:1046:4: note: each undeclared identifier is reported only
once for each function it appears in
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
make[1]: *** [debian/rules:24: build-python3.9] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2

Build finished at 2020-10-11T09:31:29Z


0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#971999: phpmyadmin: CVE-2020-26934

2020-10-11 Thread Salvatore Bonaccorso
Source: phpmyadmin
Version: 4:4.9.5+dfsg1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for phpmyadmin.

CVE-2020-26934[0]:
| phpMyAdmin before 4.9.6 and 5.x before 5.0.3 allows XSS through the
| transformation feature via a crafted link.


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-26934
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26934
[1] https://www.phpmyadmin.net/security/PMASA-2020-5/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-11 Thread Richard B. Kreckel

On 10.10.20 07:04, Helmut Grohne wrote:

Source: cln
Version: 1.3.6-4
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

cln fails to cross build from source, because it checks for the size of
intptr_t without including . It thus fails detecting a size
and errors out. Please add the required include. I'm attaching a patch
for that.


Thank you! Your patch has been upstreamed.


I fear this is not the only issue. For instance on ppc64el, the build
times out during configure. I haven't figured out why yet. Can you just
fix the missing include and close this bug when doing so?


I would love to know at which point configure gets stuck.

  -richy.
--
Richard B. Kreckel




Bug#972003: RFA: privacybadger - Privacy Badger automatically learns to block invisible trackers

2020-10-11 Thread Markus Koschany
Package: wnpp
Severity: normal
X-Debbugs-Cc: jsc...@posteo.net, mes...@debian.org

I hereby officially request a new maintainer for privacybadger. The
upstream maintainer of privacybadger has asked for regular updates in
stable distributions but I am personally not interested to update this
Firefox addon on a regular basis in stable. [1] John (CCed) seemed to be
interested though. Also in CC is Michael who is the co-maintainer of
privacybadger. I intend to request the removal of privacybadger from
stable in two weeks and if there is nobody who wants to maintain the
addon in the future, I will also ask for its removal from Debian
before we freeze for Debian 11.

Markus

[1] 
https://alioth-lists.debian.net/pipermail/pkg-mozext-maintainers/2020-August/008652.html



Bug#972002: vde-wirefilter: Package short description probably wrong

2020-10-11 Thread Beatrice Torracca
Source: vde2
Severity: minor

Hi,

the vde-wirefilter package short description now reads "Virtual
Distributed Ethernet. Plug command.". I suspect that is the wrong
description since it is the same of the vde-plug package where it
seems more appropriate.

The same thing goes for the package vde-switch which has the same
short description.

Sorry if I am wasting your time with a wrong bug report.

Thanks,

beatrice



Bug#972001: buster-pu: package tzdata/2020b-0+deb10u1

2020-10-11 Thread Aurelien Jarno
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: debian-gl...@lists.debian.org

Dear stable release team,

I've uploaded tzdata/2020b-0+deb10u1 to buster. There is no urgency to
get it through stable-updates and it can wait for the next stable point
release. Here is the corresponding changelog:

tzdata (2020b-0+deb10u1) buster; urgency=medium

  * New upstream version, affecting the following past and future
timestamps:
- Revised predictions for Morocco's changes starting in 2023.
- Macquarie Island has stayed in sync with Tasmania since 2011.
- Casey, Antarctica is at +08 in winter and +11 in summer since 2018.
  * Restore the pacificnew and systemv files that have been removed
upstream. The corresponding timezones have been removed from the
bullseye/sid package, with the switch to the new names handle by the
maintainer scripts. However we do not want to transition to the new
names in a stable release.
  * Update debian/upstream/signing-key.asc.

 -- Aurelien Jarno   Sun, 11 Oct 2020 15:36:25 +0200

Thanks for considering.

Regards,
Aurelien



Bug#956602: any possibility to drop the dependency on librestbed?

2020-10-11 Thread Alexandre Viau
On 2020-10-04 6:43 a.m., Francesco Poli wrote:
> What about persuading the upstream developers of librestbed to
> re-license the library under more uncontroversially DFSG-free terms
> (GNU GPL or more permissive)?
> 
> Do you think there is any chance of success?

I don't intend to spend any energy on this, but feel free to try :)

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature


Bug#972039: ITP: cbor2 - Concise Binary Object Representation library for Python

2020-10-11 Thread Bastian Germann
Package: wnpp
Severity: wishlist
Owner: Bastian Germann 

* Package name: cbor2
  Version : 5.2.0
  Upstream Author : Alex Grönholm 
* URL : https://github.com/agronholm/cbor2
* License : Expat
  Programming Lang: Python
  Description : Concise Binary Object Representation library

This library provides encoding and decoding for the Concise Binary
Object Representation (CBOR, RFC 7049) serialization format.
There is already python-cbor in the archive, however its upstream is not
available anymore and is therefore obviously unmaintained. cbor2 is a
good replacement.

 Features:
  * Simple api like json or pickle modules.
  * Support many CBOR tags with stdlib objects.
  * Generic tag decoding.
  * Shared value references including cyclic references.
  * Optional C module backend.
  * Extensible tagged value handling.
  * Command-line diagnostic tool, converting CBOR file or stream to JSON
  * Thorough test suite.



Bug#971642: logidee-tools: Fails to build w/ latest TeX Live checkout

2020-10-11 Thread Hilmar Preuße

Am 05.10.2020 um 20:15 teilte Hilmar Preuße mit:

Am 05.10.2020 um 10:31 teilte Raphael Hertzog mit:

On Sun, 04 Oct 2020, Hilmar Preusse wrote:


Hi Raphael,

I'm able to reproduce the issue here in a Debian unstable 
installation and I could fix it by loading the longtable LaTeX

package in the cls file.


Care to share the patch?

Attached is the updated LaTeX class file an the updated topmost 
Makefile.generic .


The LaTeX class file does not need to be updated after latest 
texlive-lang upload: it was a bug in french package. The Makefile 
however still needs to be replaced, else the gs run will fail.


Hilmar
--
#206401 http://counter.li.org



OpenPGP_signature
Description: OpenPGP digital signature


Bug#972033: pandas ftbfs with python3.9 as supported python version

2020-10-11 Thread Matthias Klose
On 10/11/20 8:26 PM, Rebecca N. Palmer wrote:
> There's a 1.1.3 package in Salsa, but it hasn't been tested.  (With
> python3-all-dev from experimental, it fails because numpy doesn't have a 3.9
> build yet.)

please see for those builds in a groovy chroot:
https://launchpad.net/~pythoneers/+archive/ubuntu/python3.9/
https://launchpad.net/~pythoneers/+archive/ubuntu/python3.9-fixes/



Bug#971939: cln FTCBFS: missing #include for intptr_t

2020-10-11 Thread Helmut Grohne
On Sun, Oct 11, 2020 at 12:27:03PM +0200, Richard B. Kreckel wrote:
> Thank you! Your patch has been upstreamed.

Great! This is not urgent from my pov, just close the Debian bug with
the new upstream upload.

> > I fear this is not the only issue. For instance on ppc64el, the build
> > times out during configure. I haven't figured out why yet. Can you just
> > fix the missing include and close this bug when doing so?
> 
> I would love to know at which point configure gets stuck.

You can get an overview at http://crossqa.debian.net/src/cln. The
failure mode is architecture-dependent:

This bug:
 * arm64
 * armel
 * armhf
 * mips64el
 * mipsel
 * s390x

Build timeout while generating intparam.h on ppc64el:
 * http://crossqa.debian.net/build/cln_1.3.6-4_ppc64el_20200107193158.log
 * http://crossqa.debian.net/build/cln_1.3.6-3_ppc64el_20200106155133.log
 * http://crossqa.debian.net/build/cln_1.3.6-1_ppc64el_20191207104527.log

If you are interested in figuring out why this happens, all the better,
I guess you should pass --anything-failed-commands=%SBUILD_SHELL to
sbuild and examine config.log.

Helmut



Bug#972041: android-platform-external-libunwind uses an internal interface of p7zip-full

2020-10-11 Thread Helmut Grohne
Source: android-platform-external-libunwind
Version: 10.0.0+r36-3
Severity: serious
Justficiation: uses an internal shared library

android-platform-external-libunwind uses /usr/lib/p7zip/7z.so, which is
an internal aspect of p7zip-full and not meant for consumption by
packages. Please stop using it.

If you really need this library, please ask the p7zip maintainer to
split the library off into a separate shared library package with an
soname.

Helmut



Bug#972040: jq FTBFS everywhere: dh_missing fails

2020-10-11 Thread Helmut Grohne
Source: jq
Version: 1.6-2
Severity: serious
Tags: ftbfs

jq fails to build from source on the buildds for any architecture. Here
is an example failure:

|dh_missing -a
| dh_missing: warning: usr/lib/x86_64-linux-gnu/libjq.la exists in debian/tmp 
but is not installed to anywhere
| dh_missing: warning: usr/share/doc/jq/AUTHORS exists in debian/tmp but is not 
installed to anywhere (related file: "AUTHORS")
| dh_missing: warning: usr/share/doc/jq/README exists in debian/tmp but is not 
installed to anywhere (related file: "README")
| dh_missing: error: missing files, aborting
| 
|  While detecting missing files, dh_missing noted some files with a similar 
name to those
|  that were missing.  This error /might/ be resolved by replacing references 
to the
|  missing files with the similarly named ones that dh_missing found - assuming 
the content
|  is identical.
| 
|  As an example, you might want to replace:
|   * AUTHORS
|  with:
|   * usr/share/doc/jq/AUTHORS
|  in a file in debian/ or as argument to one of the dh_* tools called from 
debian/rules.
|  (Note it is possible the paths are not used verbatim but instead directories
|  containing or globs matching them are used instead)
| 
|  Alternatively, add the missing file to debian/not-installed if it cannot and 
should not
|  be used.
| 
|  The following debhelper tools have reported what they installed (with files 
per package)
|   * dh_install: jq (2), libjq-dev (3), libjq1 (2)
|   * dh_installdocs: jq (2), libjq-dev (0), libjq1 (0)
|   * dh_installman: jq (0), libjq-dev (0), libjq1 (0)
|  If the missing files are installed by another tool, please file a bug 
against it.
|  When filing the report, if the tool is not part of debhelper itself, please 
reference the
|  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for 
debhelper (10.6.3+).
|(in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
|  Be sure to test with dpkg-buildpackage -A/-B as the results may vary when 
only a subset is built
|  If the omission is intentional or no other helper can take care of this 
consider adding the
|  paths to debian/not-installed.
| 
|  Remember to be careful with paths containing "x86_64-linux-gnu", where you 
might need to
|  use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
|  to ensure it works on all architectures (see #961104).
| make: *** [debian/rules:24: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Helmut



Bug#972042: pg-partman: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv'

2020-10-11 Thread Aurelien Jarno
Source: pg-partman
Version: 4.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-Cc: debian...@lists.debian.org

Dear maintainer,

With the latest upload of pg-partman the autopkgtest fails on amd64,
arm64, armhf and i386. Here are the links to the test logs:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pg-partman/7390131/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/p/pg-partman/7420102/log.gz
https://ci.debian.net/data/autopkgtest/testing/armhf/p/pg-partman/7386229/log.gz
https://ci.debian.net/data/autopkgtest/testing/i386/p/pg-partman/7391211/log.gz

Regards,
Aurelien



Bug#971518: [Pkg-net-snmp-devel] Bug#971518: libsnmp30: Depends on missing package

2020-10-11 Thread Michael Rasmussen
On Sun, 11 Oct 2020 18:15:10 +1100
Craig Small  wrote:

> 
> I cannot really see where you have a setup where you:
> * have libsnmp30
> * don't have libsnmp40
> * don't have libperl5.28
> 
> Maybe just installing libsnmp40 will fix things?
> 
I can't explain what has happen but it turned out that libsnmp40 was
installed so fixing it was simply apt purge libsnmp30.
But I am still puzzled why I ever has been seeing this problem since
removing libsnmp30 showed that no packages had a dependency to
libsnmp30 so why did installing libsnmp40 not remove libsnmp30?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
https://pgp.key-server.io/pks/lookup?search=0xD3C9A00E
mir  datanom  net
https://pgp.key-server.io/pks/lookup?search=0xE501F51C
mir  miras  org
https://pgp.key-server.io/pks/lookup?search=0xE3E80917
--
/usr/games/fortune -es says:
Because I don't need to worry about finances I can ignore Microsoft
and take over the (computing) world from the grassroots.
-- Linus Torvalds


pgp48FHwKjeIZ.pgp
Description: OpenPGP digital signature


Bug#972043: libreoffice: 1:6.1.5-1 -> 1:7.0.2-1 upgrade fails

2020-10-11 Thread Jessica Clarke
Source: libreoffice
Version: 1:7.0.2-1
Severity: serious

I came to upgrade an old VM and was faced with:

> Preparing to unpack .../09-libreoffice-common_1%3a7.0.2-1_all.deb ...
> dpkg-maintscript-helper: error: file 
> '/usr/lib/libreoffice/share/registry/math.xcd' not owned by package 
> 'libreoffice-common:all'
> dpkg-maintscript-helper: error: directory 
> '/usr/lib/libreoffice/share/registry' contains files not owned by package 
> libreoffice-common:all, cannot switch to symlink
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-yFAjDA/09-libreoffice-common_1%3a7.0.2-1_all.deb 
> (--unpack):
>  new libreoffice-common package pre-installation script subprocess returned 
> error exit status 1
> rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
> directory
> rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
> ...
> debian:~ jrtc27% sudo dpkg -S /usr/lib/libreoffice/share/registry/math.xcd
> libreoffice-math: /usr/lib/libreoffice/share/registry/math.xcd

I have 1:6.1.5-1 installed and was upgrading to 1:7.0.2-1.

Jess



Bug#972046: postgresql-q3c: autopkgtest regression: pg_buildext: error: unsupported action 'virtualenv'

2020-10-11 Thread Aurelien Jarno
Source: postgresql-q3c
Version: 2.0.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-Cc: debian...@lists.debian.org

Dear maintainer,

With the latest upload of postgresql-q3c the autopkgtest fails on amd64,
arm64, armhf and i386. Here are the links to the test logs:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-q3c/7387133/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/p/postgresql-q3c/7419138/log.gz
https://ci.debian.net/data/autopkgtest/testing/armhf/p/postgresql-q3c/7387303/log.gz
https://ci.debian.net/data/autopkgtest/testing/i386/p/postgresql-q3c/7387403/log.gz

Regards,
Aurelien



Bug#972045: postgresql-plproxy: autopkgtest regression: make: Makefile: No such file or directory

2020-10-11 Thread Aurelien Jarno
Source: postgresql-plproxy
Version: 2.10.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-Cc: debian...@lists.debian.org

Dear maintainer,

With the latest upload of postgresql-plproxy the autopkgtest fails on
amd64, arm64, armhf and i386. Here are the links to the test logs:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-plproxy/7402709/log.gz
https://ci.debian.net/data/autopkgtest/testing/arm64/p/postgresql-plproxy/7402263/log.gz
https://ci.debian.net/data/autopkgtest/testing/armhf/p/postgresql-plproxy/7404174/log.gz
https://ci.debian.net/data/autopkgtest/testing/i386/p/postgresql-plproxy/7402338/log.gz

Regards,
Aurelien



Bug#971054: winedbg --gdb does not work with 32-bit WINEPREFIX

2020-10-11 Thread Bernhard Übelacker
Dear Maintainer,
tried to have a look at it and found that this might be caused by
the wine binary being pointed to by Debians alternatives system.

Therefore winedbg does not find the loader shared object of the target
process and cannot map it (elf_read_wine_loader_dbg_info).
That module would be marked as "" and 'winedbg --gdb'
relies on finding that in function mod_loader_cb.
If it cannot be found windbg exits directly after dbg_get_debuggee_info [1],
unfortunately without any message.

This can be worked around by setting the path before like in [2].

Because upstream changed winedbg since 5.6 to not rely on knowing the loader,
I guess a "debianized" wine package from that version upwards should also
not show this issue. [3]

Kind regards,
Bernhard


[1]
Breakpoint 7, mod_loader_cb (mod_name=, base=, ctx=) at 
winedbg.c:429
429 if (!strcmp(mod_name, ""))
1: x/i $pc
=> 0x7fa056f4 :   mov$0xe,%ecx
(rr) bt
#0  mod_loader_cb (mod_name=, base=, ctx=) at winedbg.c:429
#1  0x7f978bc5 in enum_modW64_64 (name=0x139ef8, base=2141257728, 
user=0x32f140) at module.c:805
#2  0x7f97aa79 in SymEnumerateModulesW64 (hProcess=, 
EnumModulesCallback=, UserContext=) at 
module.c:838
#3  0x7f97ab66 in SymEnumerateModules64 (hProcess=0x2c, 
EnumModulesCallback=0x7fa056d0 , UserContext=0x32f294) at 
module.c:817
#4  0x7fa06284 in dbg_get_debuggee_info (hProcess=, imh_mod=) 
at winedbg.c:452
#5  0x7f9f5724 in gdb_remote (flags=, port=) at 
gdbproxy.c:1930
#6  0x7f9f7cc3 in gdb_main (argc=, argv=) at 
gdbproxy.c:2110
#7  0x7f9e75e1 in main () from 
/usr/lib/wine/../i386-linux-gnu/wine/winedbg.exe.so
#8  0x7fa0c8cd in __wine_spec_exe_entry (peb=) at exe_entry.c:64
#9  0x7b454882 in call_process_entry () from 
/usr/lib/wine/../i386-linux-gnu/wine/kernel32.dll.so
#10 0x7b454cfc in start_process (entry=, peb=) at 
process.c:153
#11 0x7b45488e in __wine_start_process () from 
/usr/lib/wine/../i386-linux-gnu/wine/kernel32.dll.so
#12 0x in ?? ()


[2]
export PATH=/usr/lib/wine:$PATH
wine winedbg --gdb notepad


[3]
https://source.winehq.org/git/wine.git/patch/86ed5e563dc75bc5dae30f9647eefa63efb132d5

# Bullseye/testing i386 qemu VM 2020-10-11


apt update
apt dist-upgrade


apt install systemd-coredump mc htop fakeroot quilt lightdm xserver-xorg 
openbox xterm sshfs libcapnp-dev gdb wine wine32-dbgsym libwine-dbgsym
apt build-dep wine

reboot


echo 1 > /proc/sys/kernel/perf_event_paranoid
# prebuilt rr:
mkdir -p /home/bernhard/data/entwicklung/2020/rr/2020-10-09
sshfs -o allow_other,uid=1000,gid=1000 
bernhard@192.168.178.25:/home/bernhard/data/entwicklung/2020/rr/2020-10-09 
/home/bernhard/data/entwicklung/2020/rr/2020-10-09




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



export DISPLAY=:0
export WINEPREFIX=~/.wine32
wine wineboot

wine winedbg --gdb notepad.exe







$ WINEDEBUG=+process 
/home/bernhard/data/entwicklung/2020/rr/2020-10-09/obj_i686/bin/rr wine winedbg 
--gdb notepad.exe
rr: Saving execution to trace directory `/home/benutzer/.local/share/rr/wine-4'.
...


benutzer@debian:~$ 
/home/bernhard/data/entwicklung/2020/rr/2020-10-09/obj_i686/bin/rr ps 
/home/benutzer/.local/share/rr/wine-4
PID PPIDEXITCMD
7243--  0   wine winedbg --gdb notepad.exe
724572430   /usr/lib/wine/wineserver
72467245-9  (forked without exec)
724772430   (forked without exec)
724872470   /usr/lib/wine/wine C:\windows\system32\wineboot.exe 
--init
724972480   (forked without exec)
725072490   /usr/lib/wine/wine 
C:\windows\system32\winemenubuilder.exe -a -r
725172480   (forked without exec)
72527251-9  /usr/lib/wine/wine C:\windows\system32\services.exe
725472520   (forked without exec)
72557254-9  /usr/lib/wine/wine C:\windows\system32\plugplay.exe
725672500   (forked without exec)
725772560   /usr/lib/wine/wine C:\windows\system32\explorer.exe 
/desktop
726372520   (forked without exec)
72647263-9  /usr/lib/wine/wine C:\windows\system32\winedevice.exe
727572520   (forked without exec)
72767275-9  /usr/lib/wine/wine C:\windows\system32\winedevice.exe
728272430   (forked without exec)
72837282-9  /usr/lib/wine/wine notepad.exe


benutzer@debian:~$ 
/home/bernhard/data/entwicklung/2020/rr/2020-10-09/obj_i686/bin/rr wine winedbg 
--gdb notepad.exe
rr: Saving execution to trace directory `/home/benutzer/.local/share/rr/wine-0'.
002c:002d: create process 'C:\windows\system32\notepad.exe'/0x1106b0 
@0x7fa19e50 (0<0>)
002c:002d: create thread I @0x7fa19e50
benutzer@debian:~$

002c:002d: create thread I @0x7fa19e50

Program received signal SIGKILL, Killed.
0x700e in ?? ()
1: x/i $pc
=> 0x700e:  ret
(rr) bt
#0  0x700e in ?? ()
#1  0xb7f06ef1 in _raw_syscall () at 

Bug#971054: Fwd: Bug#971054: winedbg --gdb does not work with 32-bit WINEPREFIX

2020-10-11 Thread Bill Blough
Hi Bernhard,

Thanks very much for investigating this!

I can confirm that adjusting the PATH works around the issue for me.

Best regards,
Bill



Bug#971866: buster-pu: package okular/4:17.12.2-2.2+deb10u1

2020-10-11 Thread Moritz Mühlenhoff
On Sun, Oct 11, 2020 at 03:29:22PM +0100, Adam D. Barratt wrote:
> On Sat, 2020-10-10 at 13:42 +0200, Moritz Mühlenhoff wrote:
> > On Sat, Oct 10, 2020 at 09:40:05AM +0100, Adam D. Barratt wrote:
> > > Control: tags -1 + confirmed
> > > 
> > > On Thu, 2020-10-08 at 21:15 +0200, Moritz Muehlenhoff wrote:
> > > > Low severity fix for Okular, which doesn't warrant a DSA.
> > > > I've tested with the reproducerand a number of other PDF
> > > > files that everything works as expected.
> > > > 
> > > 
> > > Please go ahead.
> > 
> > Uploaded.
> 
> It looks like that didn't work out. The queued log has:
> 
> Oct 11 11:54:35 Deleted stray file 
> /okular-dbgsym_17.12.2-2.2+deb10u1_amd64.deb
> Oct 11 11:54:35 Deleted stray file 
> /libokular5core8-dbgsym_17.12.2-2.2+deb10u1_amd64.deb
> Oct 11 11:54:35 Deleted stray file 
> /libokular5core8_17.12.2-2.2+deb10u1_amd64.deb
> Oct 11 11:54:35 Deleted stray file /okular_17.12.2-2.2+deb10u1.dsc
> Oct 11 11:54:35 Deleted stray file /okular_17.12.2-2.2+deb10u1.debian.tar.xz

Meh, should be fixed now.

Cheers,
Moritz



Bug#972034: Multiple security issues affecting intellij-community-idea?

2020-10-11 Thread Moritz Muehlenhoff
Source: intellij-community-idea
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

There's multiple securities for JetBrains, but it's not really obvious
whether they affect libraries src:intellij-community-idea or only
parts not packaged, can you please check so that we can update the
Security Tracker accordingly?

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7914
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7905
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7904
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11690
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9873
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9872
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9823
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9186
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18361
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14954
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10104
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10103

Cheers,
Moritz



Bug#972037: CVE-2020-26570

2020-10-11 Thread Moritz Muehlenhoff
Package: opensc
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26570

Cheers,
Moritz



Bug#972036: CVE-2020-26571

2020-10-11 Thread Moritz Muehlenhoff
Package: opensc
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26571

Cheers,
Moritz



Bug#972035: CVE-2020-26572

2020-10-11 Thread Moritz Muehlenhoff
Package: opensc
Version: CVE-2020-26572
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26572

Cheers,
Moritz



Bug#971996: gnocchi-common: Default install of gnocchi-common fails "No 'gnocchi.indexer' driver found, looking for 'sqlite'"

2020-10-11 Thread Russell Coker
Package: gnocchi-common
Version: 4.3.1-3
Severity: important

I first installed mariadb-server and mariadb-client on a test VM.  I then ran
"apt install gnocchi-common" selected MySQL and no keystone, then the
/var/lib/dpkg/info/gnocchi-common.postinst gave the following error:
2020-10-11 12:56:35,415 [6782] WARNING  stevedore.named: Could not load sqlite
2020-10-11 12:56:35,424 [6782] ERRORgnocchi.utils: Unable to initialize 
indexer driver
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 333, in 
call
result = fn(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/gnocchi/indexer/__init__.py", line 107, 
in get_driver
split.scheme).driver
  File "/usr/lib/python3/dist-packages/stevedore/driver.py", line 61, in 
__init__
warn_on_missing_entrypoint=warn_on_missing_entrypoint
  File "/usr/lib/python3/dist-packages/stevedore/named.py", line 89, in 
__init__
self._init_plugins(extensions)
  File "/usr/lib/python3/dist-packages/stevedore/driver.py", line 113, in 
_init_plugins
(self.namespace, name))
stevedore.exception.NoMatches: No 'gnocchi.indexer' driver found, looking for 
'sqlite'

It repeated that error many times and did not progress.  I tried installing 
sqlite3 and
python-sqlite but that made no difference.

Is there a missing dependency on some other sqlite related package?

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages gnocchi-common depends on:
ii  adduser3.118
ii  dbconfig-common2.0.11+deb10u1
ii  debconf [debconf-2.0]  1.5.71
ii  python3-gnocchi4.3.1-3

gnocchi-common recommends no packages.

gnocchi-common suggests no packages.

-- debconf information:
  gnocchi-common/app-password-confirm: (password omitted)
  gnocchi-common/pgsql/admin-pass: (password omitted)
  gnocchi/ksat-admin-password: (password omitted)
  gnocchi-common/mysql/app-pass: (password omitted)
  gnocchi/ksat-service-password: (password omitted)
  gnocchi-common/mysql/admin-pass: (password omitted)
  gnocchi-common/password-confirm: (password omitted)
  gnocchi-common/pgsql/app-pass: (password omitted)
  gnocchi-common/upgrade-backup: true
  gnocchi-common/pgsql/no-empty-passwords:
  gnocchi-common/dbconfig-reinstall: false
  gnocchi-common/install-error: abort
  gnocchi/ksat-admin-project-name: admin
  gnocchi-common/pgsql/authmethod-user: password
  gnocchi-common/mysql/method: Unix socket
  gnocchi/ksat-service-username:
* gnocchi-common/dbconfig-install: true
  gnocchi/ksat-public-url: http://localhost:5000
  gnocchi-common/internal/skip-preseed: false
  gnocchi-common/upgrade-error: abort
* gnocchi/configure_ksat: false
  gnocchi-common/pgsql/manualconf:
  gnocchi/ksat-service-project-name: service
* gnocchi-common/database-type: mysql
* gnocchi/configure_db: true
  gnocchi-common/db/app-user: gnocchi-common@localhost
  gnocchi-common/missing-db-package-error: abort
  gnocchi-common/pgsql/authmethod-admin: ident
  gnocchi/ksat-region: regionOne
  gnocchi-common/remote/port:
  gnocchi/ksat-admin-username: admin
  gnocchi-common/remove-error: abort
  gnocchi-common/db/basepath:
  gnocchi-common/passwords-do-not-match:
  gnocchi-common/purge: false
  gnocchi-common/db/dbname: gnocchidb
  gnocchi-common/remote/newhost:
  gnocchi-common/pgsql/method: TCP/IP
  gnocchi/ksat-admin-url: http://localhost:35357
  gnocchi-common/dbconfig-remove: true
  gnocchi-common/internal/reconfiguring: false
  gnocchi-common/remote/host: localhost
  gnocchi-common/pgsql/changeconf: false
* gnocchi-common/mysql/admin-user: root
  gnocchi/ksat-create-service-user: true
  gnocchi-common/dbconfig-upgrade: true
  gnocchi-common/pgsql/admin-user: postgres



  1   2   >