Bug#960448: openldap: Dynamically generate contact email

[Ryan Tandy]

Control: tag -1 pending

Fixed in git. Testing would be appreciated.

Bug#961313: pyspread: Fix example in package's tutorial?

[Kingsley G. Morse Jr.]

Package: pyspread
Version: 1.99.2-2
Severity: normal

Dear Andreas,

Thanks for pyspread.

I installed version 1.99.2-2.

I tried an example in its tutorial.

pyspread->Help->Tutorial says

"Select the top-left cell and type: python 1 + 5 * 2"

but when I type

python 1 + 5 * 2

in cell [0, 0, 0], pyspread complains with

"invalid syntax (, line1)"

I expected to see

11

So, I checked the documentation on line at

https://pyspread.gitlab.io/tutorial.html

It suggests typing

1 + 5 * 2

(no "python " ).

It works!

Yay!

Maybe the tutorial in debian's package should be
more like the Quick Start Tutorial online at

https://pyspread.gitlab.io/tutorial.html

Thanks,
Kingsley








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

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

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


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

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

Versions of packages pyspread depends on:
ii  python3  3.7.5-1
ii  python3-numpy1:1.16.5-1
ii  python3-pyqt55.14.1+dfsg-2
ii  python3-pyqt5.qtsvg  5.14.1+dfsg-2
pn  python3:any  

Versions of packages pyspread recommends:
ii  python3-enchant 3.0.1-1
ii  python3-matplotlib  3.0.2-2

pyspread suggests no packages.

-- no debconf information

Bug#961294: Allow derivatives to define parent project fields

[Russ Allbery]

Simon Quigley  writes:

> I recently had a discussion in a Lintian merge request[1] where I
> submitted code solidifying existing behavior in the Ubuntu Desktop and
> Lubuntu teams. As I stated there, it is common practice in those teams
> (and I am sure it exists in others as well) to specify a
> `XS-Debian-Vcs-Browser` and/or `XS-Debian-Vcs-Git` field to point to
> Salsa.

> The rationale for this is to allow packaging changes to flow back
> upstream to Debian when Ubuntu's packaging repository is in a different
> location (when Ubuntu has a permanent downstream delta but continues to
> rebase that delta on top of Debian's changes).

> I would like to solidify this existing practice by modifying Debian
> Policy, amending 5.6.26 to allow usage of -Vcs-Browser and
> -Vcs-.

I'm not sure I understand why you want to make this change to Debian
Policy.  Isn't this a matter for Ubuntu policy?  The new fields wouldn't
be in the package in Debian (because they wouldn't be meaningful there).

> I would also like to use this as an opportunity to deprecate
> `Original-Maintainer` in favor of `Debian-Maintainer` and allow for
> `Debian-Uploaders` as well.

Similarly this seems to be entirely a question for Ubuntu (and Lintian, of
course).

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

Bug#892308: Same problem on buster, kmail 5.9.3

[Josep Guerrero]

Hi,

I've found the same bug on two different Debian buster systems running kmail 
5.9.3, both of them upgraded from stretch, jessie, etc. In both of them a 
small square, similar to the screenshots provided by the original poster and 
showing what looks like a piece of some other window (web browser, terminal, 
etc.), appears at the bottom left of the list of messages. This square behaves 
as if it was part of the kmail window, moving with it and being repainted if 
covered by another window. The square seems to have no effect, other than the 
cosmetic.

Regards,

Josep

Bug#954290: kexec doesn't do reboots on systemd install?

[Vasudev Kamath]

Vasudev Kamath  writes:

> In our setup of Debian 9 we noticed many kernel panic which never crash
> dumped so was searching if there is something wrong in our setup and
> came across this bug. While looking at systemd I noticed there is a
> service called systemd-kexec.service which is disabled by default. Is
> this needs to be enabled for kexec to work correctly with systemd?
>
> If this service is needed may be should be enabled on installing
> kexec-tools?

May be I misunderstood relation between kdump-tools and kexec-tools. If
so please ignore above message :-). Was actually looking at [1] which
gave me a feeling that something is missing in my setup and wrote above
mail

[1] https://wiki.archlinux.org/index.php/Kdump

Cheers,
Vasudev

Bug#961312: savelog.8: minor formatting changes to the manual

[Bjarni Ingi Gislason]

Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is savelog.8

Test nr. 2:

Enable and fix warnings from 'test-groff'.


Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z

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

Input file is ./savelog.8

:71 (macro IR): only 1 argument, but more are expected



Test nr. 16:

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

71:.IR "file"

#

Test nr. 36:

Wrong distance between sentences or protect the indicator.

a) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) and "info groff".

 The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.


107:Save cycle versions of the logfile (default: 7). The
126:For xz no strength option is set, and xz decides on the default based on 
the total amount of physical RAM. Note that xz can use a very large amount of 
memory for the higher compression levels.
145:instead of . to roll files

#

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.

savelog.8: line 8   length 92
[\-J] [\-1\ .\|.\ \-9] [\-C] [\-d] [\-l] [\-r rolldir] [\-n] [\-q] [\-D 
dateformat] file ...

savelog.8: line 126 length 192
For xz no strength option is set, and xz decides on the default based on the 
total amount of physical RAM. Note that xz can use a very large amount of 
memory for the higher compression levels.


#

Test nr. 42:

Remove superfluous quotation marks (") from the argument of a
single-font macro.

54:.I "file"

#

Test nr. 59:

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line

145:instead of . to roll files

#

  Print constants in bold, not italic (e.g., "file.1")

#

  Add ".sp 1" to empty lines.

#

  Patch:

--- savelog.8   2019-12-07 02:13:44.0 +
+++ savelog.8.new   2020-05-23 02:21:53.0 +
@@ -5,7 +5,9 @@ savelog \- save a log file
 .SH SYNOPSIS
 .B savelog
 [\-m mode] [\-u user] [\-g group] [\-t] [\-p] [\-c cycle] [\-l] [\-j]
-[\-J] [\-1\ .\|.\ \-9] [\-C] [\-d] [\-l] [\-r rolldir] [\-n] [\-q] [\-D 
dateformat] file ...
+[\-J] [\-1\ .\|.\ \-9] [\-C] [\-d] [\-l] [\-r rolldir] [\-n] [\-q]
+[\-D dateformat] file ...
+.
 .SH DESCRIPTION
 The
 .B savelog
@@ -14,9 +16,9 @@ of
 .I file
 are named:
 .RS
-
-.IR "file" "." "" "" ""
-
+.sp 1
+.IR file "."  "" 
+.sp 1
 .RE
 where
 .I 
@@ -29,49 +31,49 @@ have
 opened for I/O.  Only
 .I cycle
 versions of the file are kept.
-
+.sp 1
 If the file does not exist and
 .B \-t
 was given, it will be created.
-
+.sp 1
 For files that do exist and have lengths greater than zero, the following
 actions are performed:
-
+.sp 1
 .IP 1)
 Version numbered files are cycled.  Version
-.IR "file" "." "2"
+.IB file \&.2
 is moved to version
-.IR "file" "." "3",
+.IB file \&.3 \fR,
 version
-.IR "file" "." "1"
+.IB file \&.1
 is moved to version
-.IR "file" "." "2",
+.IB file \&.2 \fR,
 and so on.  Finally version
-.IR "file" "." "0"
+.IB file \&.0
 is moved to version
-.IR "file" "." "1",
+.IB file \&.1 \fR,
 and version
-.I "file"
+.I file
 is deleted.  Both
 compressed names and uncompressed names are cycled, regardless of
 .BR \-l .
 Missing version files are ignored.
-
+.
 .IP 2)
 The new
-.IR "file" "." "1"
+.IB file \&.1
 is compressed unless the
 .B \-l
 flag was given.  It is changed subject to the
 .BR "\-m" ", " "\-u" ", and " "\-g"
 flags.
-
+.
 .IP 3)
 The main
-.IR "file"
+.I file
 is moved to
-.IR "file" "." "0".
-
+.IB file .0 \fR.
+.
 .IP 4)
 If the
 .BR "\-m" ", " "\-u" ", " "\-g" ",  " "\-t" ", or " "\-p"
@@ -81,14 +83,14 @@ is created subject to the given flags.
 .B \-p
 flag, the file is created with the same owner, group, and permissions as
 before.
-
+.
 .IP 5)
 The new
-.IR "file" "." "0"
+.IB file \&.0
 is changed subject to the
 .BR "\-m" ", " "\-u" ", and " "\-g"
 flags.
-
+.
 .SH OPTIONS
 .TP
 .B "\-m mode"
@@ -104,7 +106,8 @@ chgrp log files to group, implies
 .B \-t
 .TP
 .B "\-c cycle"
-Save cycle versions of the logfile (default: 7). The
+Save cycle versions of the logfile (default: 7).
+The
 .I cycle
 count must be at least 2.
 .TP
@@ -122,8 +125,12 @@ compress with bzip2 instead of gzip
 .TP
 .B \-J
 compress with xz instead of gzip
-
-For xz no strength option is set, and xz decides on the default based on the 
total amount of physical RAM. Note that xz can use a very large amount of 
memory for the higher compression levels.
+.sp 1
+For xz no strength option is set,
+and xz decides on the default based on the total amount of physical

Bug#960448: openldap: Dynamically generate contact email

[Ryan Tandy]

Control: tag -1 - patch

On Tue, May 12, 2020 at 02:36:39PM -0300, Andreas Hasenack wrote:

-+WHOWHERE="Debian OpenLDAP Maintainers 
"
++WHOWHERE="$(grep ^Maintainer: debian/control | sed 's,Maintainer: ,,')"


Now I remember that I actually did try this initially.

The mkversion script is called from different parts of the build tree 
(by recursive make) and doesn't have easy access to $(top_srcdir).


The patch you've suggested just leaves WHOWHERE empty.

Bug#813111: Greetings and compliment of the Day.Have a happy day,

[Mrs.Aisha]

Greetings and compliment of the Day.

 May i  use this medium to open a mutual communication with you seeking
your acceptance towards investing in your country under your management as
my partner, My name is Aisha  Gaddafi and presently living in Oman, i am a
Widow and single Mother with three Children, the only biological Daughter
of late Libyan President (Late Colonel Muammar Gaddafi) and presently i am
under political asylum protection by the Oman Government.

I have funds worth "Twenty Seven Million Five Hundred Thousand United State
Dollars" -$27.500.000.00 US Dollars which i want to entrust on you for
investment project in your country.If you are willing to handle this
project on my behalf, kindly reply urgent to enable me provide you more
details to start the transfer process. is my intention to compensate you
with 30% of the total money for your services and the balance shall be my
capital in your establishment.

I shall appreciate your urgent response through my email address below:
aishamuammargaddaf...@gmail.com)Sorry for my pictures i will enclose it in
my next mail and more about me when i hear from you okay.


Best Regards
Have a happy day,
Mrs Aisha Gaddafi.

Bug#961314: RFP: python3-s2sphere -- Python implementation of a part of the C++ S2 geometry library

[Christoph Anton Mitterer]

Package: wnpp
Severity: wishlist

* Package name: python3-s2sphere
  Version : 0.2.5
  Upstream Author : s...@sidewalklabs.com
* URL : https://github.com/sidewalklabs/s2sphere
* License : MIT
  Programming Lang: Python
  Description : Python implementation of a part of the C++ S2 geometry 
library

S2 is a library for spherical geometry that aims to have
the same robustness, flexibility, and performance as the very
best planar geometry libraries.

Bug#954290: kexec doesn't do reboots on systemd install?

[Vasudev Kamath]

In our setup of Debian 9 we noticed many kernel panic which never crash
dumped so was searching if there is something wrong in our setup and
came across this bug. While looking at systemd I noticed there is a
service called systemd-kexec.service which is disabled by default. Is
this needs to be enabled for kexec to work correctly with systemd?

If this service is needed may be should be enabled on installing
kexec-tools? 

Cheers,
Vasudev

Bug#961254: libpam-mklocaluser: stop enforcing logout on initial login

[Petter Reinholdtsen]

[Mike Gabriel]
> Attached is a patch that drops the enforcement of the re-login and
> manipulates the HOME env var after the local POSIX user account has been
> fully prepared by libpam-mklocaluser.

Nice.  Not quite sure why I originally concluded that something was
caching the home directory path, nor what was caching it, so be careful.
The patch could use a comment explaining the background and constraints.

I do not see anything wrong with the patch, and assuming it has been
tested, feel free to upload it when it suits you. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl

[intrigeri]

Hi,

Niko Tyni (2020-05-21):
> So IMO we should either to package Graphics::ColorNames::HTML even though
> it's deprecated, or drop Color::Calc from Debian.

> libcolor-calc-perl has just one reverse dependency AFAICS:
> libcgi-application-plugin-authentication-perl.

I took a quick look.

At runtime, Color::Calc optionally enhances
libcgi-application-plugin-authentication-perl: it allows providing one
base color and letting the module derive other colors from it — as
opposed to sticking with the default colors, or specifying every color
one wants to use.

At build time, it seems libcgi-application-plugin-authentication-perl
should build just fine if Color::Calc is not available: the
corresponding tests should be skipped. So that reverse
build-dependency is probably not, in itself, a blocker for removing
Color::Calc from Debian.

libcolor-calc-perl's popcon is low and steadily decreasing since 10 years.

Bug#961256: sra-toolkit: srapath is a broken symlink

[Adrian Bunk]

Package: sra-toolkit
Version: 2.10.6+dfsg-3
Severity: serious
Control: affects -1 src:sra-sdk

$ file /usr/bin/srapath*
/usr/bin/srapath: broken symbolic link to sratools.2.10.6
/usr/bin/srapath-orig.2.10.6: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=20f0f36fab86a1389d442e83d4a4040eec1bfd92, for GNU/Linux 3.2.0, 
stripped
$


This is also the cause of the autopkgtest failure.

Bug#944965: [Piuparts-devel] Bug#944965: debsums: Script accesses internal dpkg database

[Andreas Beckmann]

On 22/05/2020 03.10, Axel Beckert wrote:
> I though see one problem with this: IIRC, the piuparts guys sometimes
> use debsums as backport on stable.
> 
> Cc'ing them if this is still the case and if they see any issues if a
> debsums upload in the not-so-far future would depend on a very recent
> dpkg version. (IIRC last time they needed a debsums backport, this was
> because we fixed bugs they wanted to be fixed in their setups as soon
> as they were found and fixed.)

That was for the introduction of the --ignore-obsolete option which
allowed us to get rid of many false positives (and finally make debsums
errors fail the piuparts test). We don't need any newer debsums than that.

Andreas

Bug#961263: nvidia-cuda-dev: File collision

[Tristan Seligmann]

Package: nvidia-cuda-dev
Version: 10.1.168-10
Severity: important

dpkg: error processing archive 
/var/cache/apt/archives/nvidia-cuda-dev_10.1.168-10_amd64.deb (--unpack):
 trying to overwrite '/usr/include/ansidecl.h', which is also in package 
binutils-dev 2.34-8

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

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

Bug#912596: cpufrequtils: cpufreq-info only shows 31 CPUs

[Witold Baryluk]

Package: linux
Followup-For: Bug #912596

Appears to be fixed somewhere before kernel 5.2.17.

No issues on:

$ uname -a
Linux debian 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-09-26) x86_64 GNU/Linux
$

Package:

ii  linux-image-5.2.0-3-amd64   5.2.17-1
  amd64Linux 5.2 for 64-bit PCs (signed)


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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

[intrigeri]

Hi,

intrig...@debian.org (2019-07-26):
> Therefore, at the pkg-perl BoF today at DebConf, after pondering other
> options such as orphaning this package, we decided that we don't want
> this package to be included in Bullseye (at least, maintained under
> the Perl team umbrella) unless someone else steps up and becomes its
> upstream maintainer. [...]

> libparse-debianchangelog-perl has quite a few reverse-dependencies, [...]

10 months later, we've reached the point when there's 1 single
reverse dependency left in sid: customdeb, whose maintainer promptly
agreed it can be removed at the same time as libparse-debianchangelog-perl.
All other previous reverse dependencies were ported to something else
(most often libdpkg-perl) and nobody volunteered to adopt it upstream.

Thanks a lot to everyone who participated in making this happen :)

In testing there's another reverse-dependency: aptitude, which has
been ported away from libparse-debianchangelog-perl in 0.8.13-1.

So, once aptitude >= 0.8.13-1 has migrated to testing, I think it'll
be time to ensure libparse-debianchangelog-perl itself is removed from
testing, which was the goal of the whole operation.

But:

> Note that libparse-debianchangelog-perl is on the list of key
> packages¹ so this RC bug won't trigger the autoremoval machinery for
> it, nor for any of its reverse dependencies.
>
> [1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi

libparse-debianchangelog-perl is on the list of key packages because
it's installed on many machines ("popcon"). This will prevent the
autoremoval machinery from removing it from testing.

So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to
ask (presumably the release team) for libparse-debianchangelog-perl to
lose its "key package" status, so the autoremoval machinery can remove
it from testing due to this very RC bug.

Cheers!

Bug#960283: Not in backports

[Viktor Csiky]

Hello

This fix still didn't surface in backports.

Please add it to backports, otherwise (I guess unlike testing) there is 
no feasible means for anyone using backports to fix the whole npm bunch, 
except disabling backports, purging and reinstalling (the older one).


Best,
Victor

Bug#961261: obs-studio: -V is ignored in pypy3compile

[Witold Baryluk]

Package: obs-studio
Version: 24.0.3+dfsg1-1
Severity: minor

Dear Maintainer,



Setting up obs-studio (25.0.3+dfsg1-2) ...
-V is ignored in pypy3compile



Thanks,
Witold



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages obs-studio depends on:
ii  libavcodec58 7:4.1.4-1+b3
ii  libavformat587:4.1.4-1+b3
ii  libavutil56  7:4.1.4-1+b3
ii  libc62.29-2
ii  libcurl3-gnutls  7.66.0-1
ii  libgcc-s1 [libgcc1]  10.1.0-1
ii  libgcc1  1:9.2.1-8
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-5.1
ii  libobs0  24.0.3+dfsg1-1
ii  libpython3.7 3.7.5~rc1-2
ii  libqt5core5a 5.11.3+dfsg1-4
ii  libqt5gui5   5.11.3+dfsg1-4
ii  libqt5svg5   5.11.3-3
ii  libqt5widgets5   5.11.3+dfsg1-4
ii  libqt5x11extras5 5.11.3-2
ii  libstdc++6   9.2.1-8
ii  obs-plugins  24.0.3+dfsg1-1

obs-studio recommends no packages.

obs-studio suggests no packages.

-- no debconf information

Bug#961245: mercurial-common: trying to overwrite '/usr/lib/python2.7/dist-packages/hgext/git/__init__.py', which is also in package mercurial-git 0.8.12-1.2

[Jakub Wilk]

* Axel Beckert , 2020-05-22, 00:22:

dpkg: error processing archive 
/var/cache/apt/archives/mercurial-common_5.4-1_all.deb (--unpack):
trying to overwrite '/usr/lib/python2.7/dist-packages/hgext/git/__init__.py', 
which is also in package mercurial-git 0.8.12-1.2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/mercurial-common_5.4-1_all.deb


Note that there's no such conflict upstream, because hg-git installs the 
module as "hggit" (not in the "hgext" namespace).


This mess is my fault. When I packaged hg-git in 2009, it was so 
immature it didn't even have installation scripts. Instead their README 
said:


Clone this repository somewhere and make the 'extensions' section in 
your `~/.hgrc` file look something like this:


   [extensions]
   hgext.bookmarks =
   hgext.hg-git = [path-to]/hg-git


I decided to install it as a public module "hgext.git", without even 
talking to upstream. In retrospect, it was a terrible idea. :-(


Ideally this should be fixed by renaming the hg-git's module back to 
what upstream uses. But of course this is going to break all hg-git 
users' configurations. :-/


--
Jakub Wilk

Bug#961028: hplip: No scanner found: SANE cannot load the hpaio backend

[Jeffrey Ratcliffe]

Package: hplip
Followup-For: Bug #961028

   * What led up to the situation?

Upgrade to 3.20.5+dfsg0-2

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

scanimage -L

   * What was the outcome of this action?

No scanners found

   * What outcome did you expect instead?

device `hpaio:/usb/Officejet_6500_E709a?serial=MY01C3X12W05G3' is a Hewlett-
Packard Officejet_6500_E709a all-in-one
default device is `hpaio:/usb/Officejet_6500_E709a?serial=MY01C3X12W05G3'

which is what I get again, having downgraded to 3.20.3+dfsg0-2

As it says, this is with an OfficeJet 6500



-- Package-specific info:

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 hplip depends on:
ii  adduser3.118
ii  cups   2.3.3-1
hi  hplip-data 3.20.3+dfsg0-2
ii  libc6  2.30-8
ii  libcups2   2.3.3-1
ii  libdbus-1-31.12.16-2
hi  libhpmud0  3.20.3+dfsg0-2
ii  libpython3.8   3.8.3-1
ii  libsane1.0.27-3.2+b1
hi  libsane-hpaio  3.20.3+dfsg0-2
ii  lsb-base   11.1.0
hi  printer-driver-hpcups  3.20.3+dfsg0-2
ii  python33.8.2-3
ii  python3-dbus   1.2.16-2
ii  python3-gi 3.36.0-3
ii  python3-pexpect4.6.0-3
ii  python3-pil7.0.0-4+b1
ii  python3-reportlab  3.5.34-1
ii  wget   1.20.3-1+b2
ii  xz-utils   5.2.4-1+b1

Versions of packages hplip recommends:
ii  avahi-daemon  0.8-1
ii  policykit-1   0.105-26
hi  printer-driver-postscript-hp  3.20.3+dfsg0-2
ii  sane-utils1.0.27-3.2+b1

Versions of packages hplip suggests:
pn  hplip-doc  
pn  hplip-gui  
pn  python3-notify2
ii  system-config-printer  1.5.12-1

-- no debconf information

Bug#961029: Request for new mailing list: debian-ai

[Mo Zhou]

Control: retitle -1 Request for new mailing list: debian-ai

Thanks for the various feedbacks. As pointed out by lamby, the
"debian-mlhwaccl" may be quite hard to search. Meanwhile, the name can
be overlength if we expand that abbreviation.

So I'm proposing to use a new list name: debian-ai
instead of the old: debian-mlhwaccl

Name: debian-ai
Short-Desc: Artificial Intelligence Software Development in Debian
Long-Desc: Development of artificial intelligence software, such as machine
 learning, deep learning, compilers and hardware acceleration software stacks.
 The topics for this list may include any one of the following (but not
 limited):
  * Mahcine Learning: sklearn, xgboost, AutoML, ...
  * Deep Learning: tensorflow, pytorch, mxnet, cntk, ...
  * Computer Vision: opencv, skimage, ...
  * Computational Linguistics: nltk, spacy, ...
  * Hardware Acceleration: CUDA, ROCm, OpenCL, SYCL, SIMD
  * Compiler: LLVM (for MLIR, SPIR-V, SYCL), GCC (gcc-offload-nvptx)
 And sometimes the topics in this list may be complex intersections of
 the mentioned keywords.
Category: development
Subscription-Policy: open
Post-Policy: open
Web-Archive: yes

Bug#958344: Update bleachbit to 4.0.0

[Witold Baryluk]

Package: bleachbit
Version: 2.2-3
Followup-For: Bug #958344

Yes please. 4.0.0 resolved many bugs, and uses Python 3 exclusively, so
that is quite important too.

Thanks,
Witold

Bug#961258: gdebi: -V is ignored in pypy3compile on install

[Witold Baryluk]

Package: gdebi
Version: 0.9.5.7+nmu3
Severity: minor

Dear Maintainer,



Setting up gdebi (0.9.5.7+nmu3) ...
-V is ignored in pypy3compile



Thanks.



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdebi depends on:
ii  gdebi-core0.9.5.7+nmu3
ii  gir1.2-gtk-3.03.24.12-1
ii  gir1.2-vte-2.91   0.58.2-1
ii  gnome-icon-theme  3.12.0-3
ii  policykit-1   0.105-26
ii  python3   3.7.5-1
ii  python3-gi3.34.0-1

Versions of packages gdebi recommends:
pn  libgtk2-perl  
ii  lintian   2.29.0
ii  shared-mime-info  1.10-1

gdebi suggests no packages.

-- no debconf information

Bug#933131: customdeb: depends on libparse-debianchangelog-perl that has no upstream maintainer

[intrigeri]

Control: severity -1 serious

Hi Joachim,

Joachim Breitner (2019-07-27):
> I don't think customdeb is used by anyone (certainly not by me for
> many years), and may be removed together with
> libparse-debianchangelog-perl, unless someone wants to take over
> the package.

Thank you for providing this very helpful information,
and sorry for not replying sooner.

10 months later, we've finally reached the point when customdeb is the
only reverse-dependency of libparse-debianchangelog-perl in sid, so
I'm making this bug RC. AFAICT, this should make the autoremoval
machinery remove customdeb from testing in a few weeks.

(It's not clear to me whether/when we want to remove
libparse-debianchangelog-perl from sid altogether, so for now I'm
focusing on Bullseye.)

Cheers!

Bug#961261: obs-studio: -V is ignored in pypy3compile

[Sebastian Ramacher]

Control: reassign -1 dh-python 4.20200315

On 2020-05-22 07:55:37 +, Witold Baryluk wrote:
> Package: obs-studio
> Version: 24.0.3+dfsg1-1
> Severity: minor
> 
> Dear Maintainer,
> 
> 
> 
> Setting up obs-studio (25.0.3+dfsg1-2) ...
> -V is ignored in pypy3compile

This code is generated by dh_python3, reassigning accordingly.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#961257: live-build: lb config --distribution testing, leads to failure during lb build

[Witold Baryluk]

Package: live-build
Version: 1:20191221
Followup-For: Bug #961257

I just realized that live-build version in testing and sid (package
version 1:20191221 ), doesnt't have files for --distribution bullseye
either.

Making a symlink bullseye -> squeeze in
/usr/share/live/build/data/debian-cd did help resolve the issue for me,
and --distribution bullseye looks to be working. Same could be made by
default for 'testing'.

Bug#961264: RFS: osmose-emulator/1.5-1 -- Sega Master System and Game Gear console emulator

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "osmose-emulator"

 * Package name: osmose-emulator
   Version : 1.5-1
   Upstream Author : Bruno Vedder 
 * URL : https://gitlab.com/coringao/osmose-emulator/wikis
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/games-team/osmose-emulator
   Section : games

It builds those binary packages:

  osmose-emulator - Sega Master System and Game Gear console emulator

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

  https://mentors.debian.net/package/osmose-emulator

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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/osmose-emulator/osmose-emulator_1.5-1.dsc

Changes since the last upload:

   * New upstream release.
 + Implemented the feature to switch the menu bar. (Thanks Leandro Ramos).
   * Added debian/docs.
   * debian/control:
 + Switch to debhelper-compat to 13.
 + Bumped Standards-Version to 4.5.0.
 + Set Rules-Requires-Root to no.
 + Enhanced long description.
   * debian/copyright:
 + Added copyright information for contact.
 + Copyright updated for current years (2020).
   * Update debian/upstream/metadata years (2020).
   * Added autopkgtest.
   * debian/osmose-emulator.desktop enhanced.
   * debian/rules: Removed DEB_LDFLAGS_MAINT_APPEND. Fixed upstream.

Regards,

--
  Carlos Donizete Froes [a.k.a coringao]

Bug#936336: coz-profiler: Python2 removal in sid/bullseye

[Witold Baryluk]

Package: coz-profiler
Version: 0.1.0-2
Followup-For: Bug #936336

Any updates on bringing coz-profiler to newer version and back to
testing? Upstream is at 0.2.1 and doesn't use Python 2 anymore.

Bug#961142: snapshot.debian.org: python3 migration

[Baptiste BEAUPLAT]

Hi,

On Wed, 20 May 2020 18:54:03 +0200 Baptiste BEAUPLAT 
wrote:
> As discussed previously with pabs and weasel, I'm interested in taking
> on the python 3 migration for snapshot.

I've converted the DB upgrade script to python3.

The source is available here:

https://salsa.debian.org/lyknode/snapshot/-/tree/py3/db-upgrade-script

> Technically, I propose we use salsa to work our way on that migration:

If you are OK with this workflow, I'll need the following on the
snapshot project:

- A 'python3' branch to open MR against
- the MR and CI features enabled
- at least a reporter level access to be able to open MR (salsa account
name is 'lyknode')

Best,
-- 
Baptiste BEAUPLAT - lyknode



signature.asc
Description: OpenPGP digital signature

Bug#931831: cups: http://localhost:631/ is served with HTTP Content-Type: text/plain

[Witold Baryluk]

Package: cups
Version: 2.3.3-1
Followup-For: Bug #931831

Dear Maintainer,

I discovered that it is a recent regression.

The Content-Type is correct with package version cups 2.3.0-5, but it is
incorrect in package version cups 2.3.3-1.



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups depends on:
ii  cups-client2.3.3-1
ii  cups-common2.3.3-1
ii  cups-core-drivers  2.3.3-1
ii  cups-daemon2.3.3-1
ii  cups-filters   1.25.11-1
ii  cups-ppdc  2.3.0-5
ii  cups-server-common 2.3.3-1
ii  debconf [debconf-2.0]  1.5.73
ii  ghostscript9.27~dfsg-3.1
ii  libavahi-client3   0.7-4+b1
ii  libavahi-common3   0.7-4+b1
ii  libc6  2.29-2
ii  libcups2   2.3.3-1
ii  libgcc-s1  10.1.0-1
ii  libstdc++6 9.2.1-8
ii  libusb-1.0-0   2:1.0.23-1
ii  poppler-utils  0.71.0-6
ii  procps 2:3.3.15-2+b1

Versions of packages cups recommends:
ii  avahi-daemon  0.7-4+b1
ii  colord1.4.3-4

Versions of packages cups suggests:
ii  cups-bsd 2.3.3-1
pn  cups-pdf 
ii  foomatic-db  20190913-1
pn  smbclient
ii  udev 242-7

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true

Bug#961257: live-build: lb config --distribution testing, leads to failure during lb build

[Witold Baryluk]

Package: live-build
Version: 1:20190311
Severity: normal

lb config --distribution testing 

is accepted, and most of the lb config goes fine, until very very end
(after building squashfs image, but just before iso is built):


grep: /usr/share/live/build/data/debian-cd/testing/udeb_exclude: No such file 
or directory
grep: /usr/share/live/build/data/debian-cd/testing/exclude-udebs: No such file 
or directory
grep: /usr/share/live/build/data/debian-cd/testing/exclude-udebs-amd64: No such 
file or directory

...

Reading state information... Done
The following packages will be REMOVED:
  isolinux*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 216 kB disk space will be freed.
(Reading database ... 436375 files and directories currently installed.)
Removing isolinux (3:6.04~git20190206.bf6db5b4+dfsg1-2) ...
[2020-05-22 06:57:03] lb binary_disk 
P: Begin installing disk information...
cp: cannot stat 
'/usr/share/live/build/data/debian-cd/testing/amd64_netinst_udeb_include': No 
such file or directory
P: Begin unmounting filesystems...



Using --distribution buster does work.

Would be nice to detect that earlier if possible, or specify this in the
lb_config(1) manual in more details.




-- Package-specific info:

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages live-build depends on:
ii  debootstrap  1.0.116

Versions of packages live-build recommends:
ii  apt-utils   1.8.4
ii  bzip2   1.0.8-2
ii  cpio2.12+dfsg-9+b1
ii  file1:5.37-6
ii  live-boot-doc   1:20190614
ii  live-config-doc 5.20190519
ii  live-manual-html [live-manual]  2:20151217.1
ii  wget1.20.3-1+b1
ii  xz-utils5.2.4-1+b1

Versions of packages live-build suggests:
ii  e2fsprogs  1.45.4-1
ii  mtd-utils  1:2.1.1-1
ii  parted 3.3-1

-- no debconf information

Bug#961260: SyntaxWarning: "is" with a literal

[Witold Baryluk]

Package: variety
Version: 0.7.2-2
Severity: normal

Dear Maintainer,

Setting up variety (0.8.3-1) ...
/usr/lib/python3/dist-packages/variety/VarietyWindow.py:725: SyntaxWarning: 
"is" with a literal. Did you mean "=="?
  elif favs_op is "favorite":


Looks to be fixed upstream in master branch, not in any release version yet:

https://github.com/varietywalls/variety/commit/c42bc726976add30886e6e5ec6cce02e071674b0
https://github.com/varietywalls/variety/pull/306



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages variety depends on:
ii  gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-1
ii  gir1.2-gexiv2-0.10   0.10.9-1
ii  gir1.2-glib-2.0  1.62.0-2
ii  gir1.2-gtk-3.0   3.24.12-1
ii  gir1.2-notify-0.70.7.8-1
ii  gir1.2-pango-1.0 1.42.4-7
ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2
ii  python3  3.7.5-1
ii  python3-bs4  4.8.0-2
ii  python3-cairo1.16.2-1+b1
ii  python3-configobj5.0.6-3
ii  python3-dbus 1.2.12-1
ii  python3-gi   3.34.0-1
ii  python3-gi-cairo 3.34.0-1
ii  python3-lxml 4.4.1-1
ii  python3-pil  6.2.0-1
ii  python3-pkg-resources41.2.0-1
ii  python3-requests 2.21.0-1

Versions of packages variety recommends:
ii  gir1.2-appindicator3-0.1 0.4.92-7
ii  gir1.2-ayatanaappindicator3-0.1  0.5.3-4
ii  python3-httplib2 0.11.3-2

Versions of packages variety suggests:
pn  feh | nitrogen  
pn  gnome-shell-extension-appindicator  

-- no debconf information

Bug#960892: another fix

[Martin Quinson]

Control: -1 fixed-upstream
Thanks

On Fri, May 22, 2020 at 02:35:34AM +0200, Axel Beckert wrote:
> Hi Martin.
> 
> Martin Quinson wrote:
> > I gave another try to this fix, and the current git version of po4a
> > manages to build aptitude even with the recent patch removed. 
> > 
> > Could you please give it a try, just to ensure that I didn't mess up
> > my verification?
> 
> Can confirm. Thanks for caring!

Thanks for this test. I'm happy that this bug is gone now. 

I will release a new upstream version on Sunday. I'm just giving a few
days to the translators to update their work since the fix introduced
some strings, and since you have a temporarily fix in aptitude.

Have a good one,
Mt.

-- 
Walking on water and developing software from a specification are easy
if both are frozen.


signature.asc
Description: PGP signature

Bug#961255: blueman: Resource temporarily unavailable when connecting headphones

[Emilian Nowak]

Package: blueman
Version: 2.0.8-1
Severity: normal

Dear Maintainer,

When I try to connect my headphones I get message like this.
1. I'm not sure if this should be displayed for user. What typical user can
do with it? 
2. How to solve it? I can connect those headphones using
bluedevil-wizard (another package), but I cannot do it with blueman.



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

Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8
(charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked
to /bin/dash Init: systemd (via /run/systemd/system)

Versions of packages blueman depends on:
ii  bluez5.50-1.2~deb10u1
ii  bluez-obexd  5.50-1.2~deb10u1
ii  dbus 1.12.16-1
ii  dbus-x11 [dbus-session-bus]  1.12.16-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-appindicator3-0.1 0.4.92-4
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-gtk-3.0   3.22.11-1
ii  gir1.2-notify-0.70.7.7-4
ii  gir1.2-pango-1.0 1.42.4-7~deb10u1
ii  gnome-icon-theme 3.12.0-3
ii  libbluetooth35.43-2+deb9u1
ii  libc62.28-10
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libpulse-mainloop-glib0  12.2-4+deb10u1
ii  libpython3.7 3.7.3-2
ii  librsvg2-common  2.44.10-2.1
ii  notification-daemon  3.20.0-1+b1
ii  python3  3.7.3-1
ii  python3-cairo1.16.2-1+b1
ii  python3-dbus 1.2.8-3
ii  python3-gi   3.30.4-1
ii  python3-gi-cairo 3.30.4-1

Versions of packages blueman recommends:
ii  policykit-1  0.105-18
ii  pulseaudio-module-bluetooth  12.2-4+deb10u1

blueman suggests no packages.

-- no debconf information

Bug#862658: Eye of mate not showing images >= 12 megapixel

[Witold Baryluk]

Package: eom
Followup-For: Bug #862658

I belive the issue is fixed in recent versions of eom.


I can't reproduce the issue in eom 1.22.2-1 . I tested with 1x1
images (jpeg) in it, and it works fine and very fast.

I did not test in 1.24.x


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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages eom depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  eom-common   1.22.2-1
ii  gir1.2-eom-1.0   1.22.2-1
ii  libatk1.0-0  2.34.1-1
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libexempi8   2.5.1-1
ii  libexif120.6.21-5.1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-1
ii  libgirepository-1.0-11.62.0-2
ii  libgl1   1.1.0-1+b1
ii  libgl1-mesa-glx  19.2.1-1
ii  libglib2.0-0 2.62.2-1
ii  libgtk-3-0   3.24.12-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  libmate-desktop-2-17 1.22.2-1
ii  libpeas-1.0-01.22.0-4
ii  librsvg2-2   2.44.14-1
ii  librsvg2-common  2.44.14-1
ii  libx11-6 2:1.6.8-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  mate-desktop-common  1.22.2-1
ii  shared-mime-info 1.10-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

eom recommends no packages.

eom suggests no packages.

-- no debconf information

Bug#956188: dstat: SynctaxWarning: str is not callable

[Witold Baryluk]

Package: dstat
Followup-For: Bug #956188

This is easy to fix (there was even a pull request upstream month ago to
do it), but upstream project is discontinued:

https://github.com/dstat-real/dstat/issues/170


I guess, dstat should be removed from Debian.

Bug#958710: ITP: nss-tls -- encrypted glibc name resolving library which uses DNS-over-HTTPS (DoH)

[Petter Reinholdtsen]

Hi,

Any news on getting nss-tls into Debian?
-- 
Happy hacking
Petter Reinholdtsen

Bug#961262: ITP: ruby-valid-email -- ActiveModel Validation for email

[Pirate Praveen]

Package: wnpp
Severity: wishlist

https://rubygems.org/gems/valid_email required for gitlab 13.0.0

Bug#961266: apt 2.1.3 ignores held dependencies and breaks dpkg

[Tomas Janousek]

Package: apt
Version: 2.1.4
Severity: normal

Since apt 2.1.3, a hold on git no longer prevents other git packages from
being upgraded even though they explicitly depend on git being upgraded as
well:

# dpkg --get-selections | grep 'git.*hold'
git hold
git-doc hold

# apt-cache show git-cvs=1:2.26.2-1 | grep Depends
Depends: git (>> 1:2.26.2), git (<< 1:2.26.2-.), cvsps, libdbd-sqlite3-perl

# LC_ALL=C apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
[...]
   git (1:2.25.1-1 => 1:2.26.2-1)
   git-doc (1:2.25.1-1 => 1:2.26.2-1)
   git-man (1:2.25.1-1 => 1:2.26.2-1)
[...]
The following packages will be upgraded:
   git-cvs (1:2.25.1-1 => 1:2.26.2-1)
   git-email (1:2.25.1-1 => 1:2.26.2-1)
   git-svn (1:2.25.1-1 => 1:2.26.2-1)
   gitk (1:2.25.1-1 => 1:2.26.2-1)
4 upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
Need to get 0 B/3755 kB of archives.
After this operation, 45.1 kB of additional disk space will be used.
Do you want to continue? [Y/n] n

This results in dpkg failing the upgrade as it then correctly detects the
dependencies are not satisfied. Manual repair using snapshot.debian.org is
necessary.

Downgrading apt and libapt-pkg6.0 to 2.1.2 fixes this.

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "false";
APT::Install-Suggests "false";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-.*-5\.4\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-.*-5\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-.*-5\.4\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-.*-5\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-.*-5\.4\.0-4-amd64$";
APT::NeverAutoRemove:: "^gnumach-.*-5\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-5\.4\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-modules-5\.6\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-5\.4\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-5\.6\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Update::Post-Invoke "";
APT::Update::Post-Invoke:: "[ ! -x /usr/bin/debtags ] || debtags update || 
true";
APT::Default-Release "testing";
APT::Get "";
APT::Get::Show-Versions "true";
APT::Get::AutomaticRemove "true";
APT::Periodic "";
APT::Periodic::Enable "0";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "false";
APT::Compressor::zstd::Cost "60";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";

Bug#961272: apt: inconsistent pinning behaviour

[Julian Andres Klode]

On Fri, May 22, 2020 at 12:49:25PM +0200, Julian Andres Klode wrote:
> Control: tag -1 moreinfo
> 
> On Fri, May 22, 2020 at 12:19:54PM +0200, Sergio Gelato wrote:
> > Package: apt
> > Version: 1.8.2.1
> > 
> > I'm trying to pin some packages (nvidia stuff) the upgrade of which is best
> > followed by an immediate reboot, so that I can upgrade the rest without
> > waiting for a reboot window. I came up with the attached preferences
> > configuration (based on the list of packages apt-get would otherwise try to
> > upgrade on this system), and while it's definitely having some effect it
> > seems that "apt-get upgrade" still wants to upgrade some of the pinned
> > packages. I see no reason (neither good nor bad-but-documented) for this,
> > so I call it a bug.
> 
> You have pinned all versions of these packages to the same priority - 10,
> including the installed version. I'm wondering more why the other
> packages are kept back, I'd expect them to be upgraded too.
> 
> What does policy say for them?

FWIW, as you want to emulate hold, the correct approach to do
that is to pin the installed version high:

Package: ...
Pin: release a=now
Pin-Priority: 1001

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#960283: [Pkg-javascript-devel] Bug#960283: Not in backports

[Xavier]

Le 22/05/2020 à 09:56, Viktor Csiky a écrit :
> Hello
> 
> This fix still didn't surface in backports.
> 
> Please add it to backports, otherwise (I guess unlike testing) there is
> no feasible means for anyone using backports to fix the whole npm bunch,
> except disabling backports, purging and reinstalling (the older one).

Hi,

I pushed node-dot-prop in backports. Since this package is new in
backports, wait 2-3 days to get it

Cheers,
Xavier


 Forwarder mail 
From: Debian FTP Masters 
Subject: node-dot-prop_5.2.0-1~bpo10+1_amd64.changes is NEW

binary:node-dot-prop is NEW.
binary:node-dot-prop is NEW.
source:node-dot-prop is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

Bug#961276: Messages received from blocked accounts

[Enrico Zini]

Package: gajim
Version: 1.1.2-2
Severity: important

Hello,

today at 12:46 I received a SPIM with an invitation followed by a
message. I denied the invitation, and blocked the account using "Manage
Contact → Block". I closed the chat window with the spam message.

At 13:37, that chat window reopened with a second message.

I'm attaching two small screenshots of what my roster looks like and
what's in the chat window.

It looks like the blocked status of the account is not taking effect.


Enrico


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

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

Versions of packages gajim depends on:
ii  gir1.2-gtk-3.0   3.24.5-1
ii  python3  3.7.3-1
ii  python3-cssutils 1.0.2-2
ii  python3-gi   3.30.4-1
ii  python3-gi-cairo 3.30.4-1
ii  python3-idna 2.6-1
ii  python3-keyring  17.1.1-1
ii  python3-nbxmpp   0.6.10-1
ii  python3-openssl  19.0.0-1
ii  python3-precis-i18n  1.0.0-1

Versions of packages gajim recommends:
ii  alsa-utils1.1.8-2
ii  aspell-en [aspell-dictionary] 2018.04.16-0-1
ii  ca-certificates   20190110
ii  dbus  1.12.16-1
ii  fonts-noto-color-emoji0~20180810-1
ii  gajim-omemo   2.6.27-1
ii  gajim-pgp 1.2.24-1
ii  gir1.2-farstream-0.2  0.2.8-4.1
ii  gir1.2-geoclue-2.02.5.2-1
ii  gir1.2-gspell-1   1.6.1-2
ii  gir1.2-gst-plugins-base-1.0   1.14.4-2
ii  gir1.2-gstreamer-1.0  1.14.4-1
ii  gir1.2-gupnpigd-1.0   0.2.5-3
ii  gir1.2-secret-1   0.18.7-1
ii  gstreamer1.0-plugins-ugly 1.14.4-1
ii  lxqt-notificationd [notification-daemon]  0.14.1-1
ii  notification-daemon   3.20.0-4
ii  pulseaudio-utils  12.2-4+deb10u1
ii  python3-crypto2.6.1-9+b1
ii  python3-dbus  1.2.8-3
ii  python3-gnupg 0.4.4-1
ii  python3-pil   5.4.1-2+deb10u1
ii  xfce4-notifyd [notification-daemon]   0.4.3-1

Versions of packages gajim suggests:
ii  avahi-daemon  0.7-4+b1
ii  libxss1   1:1.2.3-1
pn  nautilus-sendto   
ii  python3-kerberos  1.1.14-2
ii  python3-pycurl7.43.0.2-0.1

-- no debconf information

Bug#872215: sosreport: fdisk dependency needed

[Adrian Bunk]

Control: severity -1 important

On Tue, Aug 15, 2017 at 10:14:35AM +0200, andr...@fatal.se wrote:
>...
> quick analysis suggested you might want to add a dependency (and/or
> build-dependency if you use it at build-time, eg. tests).
> 
> Please use the backwards-compatible way of specifying the dependency
> as suggested in the debian-devel-announce mail:
> 
> fdisk | util-linux (<< 2.29.2-3~)
>...

Similar to #887181 this is a plugin dependency, in both cases Recommends 
would likely be the best solution.

cu
Adrian

Bug#961272: apt: inconsistent pinning behaviour

[Sergio Gelato]

* Julian Andres Klode [2020-05-22 12:51:20 +0200]:
> > You have pinned all versions of these packages to the same priority - 10,
> > including the installed version. I'm wondering more why the other
> > packages are kept back, I'd expect them to be upgraded too.

Since they want to be upgraded to the version from backports, I assume they
depend on newer versions of some libraries.

> > What does policy say for them?

Apart from the different package name, the same as for the ones that were
going to be upgraded.

> FWIW, as you want to emulate hold, the correct approach to do
> that is to pin the installed version high:
> 
> Package: ...
> Pin: release a=now
> Pin-Priority: 1001

Thank you for the suggestion. I don't see any mention of "a=now" in
the apt_preferences(5) man page for buster.

Bug#961265: [homeserver] /usr/bin/docker: logs are flooded with systemd[1]: run-docker-runtime\x2drunc....mount: Succeeded.

[Hendrik Friedel]

Package: docker-ce-cli
Version: 5:19.03.8~3-0~debian-buster
Severity: normal
File: /usr/bin/docker
Tags: upstream

Dear Maintainer,

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

My logs are spammed by docker:
May 21 23:46:20 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.cryHiX.mount:
 Succeeded.
May 21 23:46:51 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.dU5ZsQ.mount:
 Succeeded.
May 21 23:47:52 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.uFcPMJ.mount:
 Succeeded.
May 21 23:48:22 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.M9hxSJ.mount:
 Succeeded.
May 21 23:48:52 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.Sz55uO.mount:
 Succeeded.
May 21 23:49:23 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.hVo3dH.mount:
 Succeeded.
May 21 23:49:53 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.R41jcK.mount:
 Succeeded.
May 21 23:50:33 homeserver systemd[1]: smartmontools.service: Got notification 
message from PID 810941, but reception only permitted for main PID which is 
currently not known
May 21 23:50:34 homeserver smartd[810941]: Device: 
/dev/disk/by-id/ata-KINGSTON_SMS200S3120G_50026B72690068A9 [SAT], SMART Usage 
Attribute: 189 Airflow_Temperature_Cel changed from 29 to 28
May 21 23:50:34 homeserver smartd[810941]: Device: 
/dev/disk/by-id/ata-KINGSTON_SMS200S3120G_50026B72690068A9 [SAT], SMART Usage 
Attribute: 194 Temperature_Celsius changed from 29 to 28
May 21 23:50:49 homeserver systemd[1]: smartmontools.service: Got notification 
message from PID 810941, but reception only permitted for main PID which is 
currently not known
May 21 23:51:24 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.uMw8YD.mount:
 Succeeded.
May 21 23:51:34 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-d9d74a027540fd2b5213c597e29f8096a180c9b642e14fa8e60fc1d5416dc704-runc.2m2TEJ.mount:
 Succeeded.
May 21 23:53:26 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.QMCRyz.mount:
 Succeeded.
May 21 23:54:26 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.rkJbbA.mount:
 Succeeded.
May 21 23:54:57 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.B2ZnEu.mount:
 Succeeded.
May 21 23:55:58 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.LTdzym.mount:
 Succeeded.
May 21 23:55:58 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.b4MwVo.mount:
 Succeeded.
May 21 23:56:58 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.m9M3yx.mount:
 Succeeded.
May 21 23:57:29 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.prbwqo.mount:
 Succeeded.
May 21 23:58:30 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-a0c7a5c631b7b477952378192ffafaa6e375f8df846d799a1c084abf093c6e12-runc.z2Bcck.mount:
 Succeeded.
May 21 23:59:30 homeserver systemd[1]: 
run-docker-runtime\x2drunc-moby-8f1af265b5efb864678aeb633fb1a07f8f48772c1d34e1ee77b03550f3f23c72-runc.RoaNNp.mount:
 Succeeded.


https://github.com/docker/for-linux/issues/679


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


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

Kernel: Linux 5.6.11 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages docker-ce-cli depends on:
ii  libc6  2.28-10

docker-ce-cli recommends no packages.

docker-ce-cli suggests no packages.

-- no debconf information

Bug#961146: systemd-logind sometimes ignores a systemd-inhibit lock

[Vincent Lefevre]

Control: forwarded -1 https://github.com/systemd/systemd/issues/15887

On 2020-05-22 06:08:02 +0200, Michael Biebl wrote:
> I can't reproduce the issue with those instructions.
> Must be something specific to your hardware / software configuration.
> 
> To further debug this yourself, you might try running logind manually.
> Stop the running instance, then run
> SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-logind

The running instance cannot be stopped as it is automatically
restarted. I had to add "Environment=SYSTEMD_LOG_LEVEL=debug"
to the [Service] section as explained here:

  https://lists.freedesktop.org/archives/systemd-devel/2013-March/010004.html

> Maybe you find any clues what's going on your system.

I've reported the bug upstream with debug information. I've also
attached the logs to this message.

But systemd-logind still does not explain *why* it is suspending
the system. Before the VT change, I can see that systemd-logind
takes the inhibitor into account ("Refusing suspend operation,
handle-lid-switch is inhibited"). And just after the VT change,
it suspends the system.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
May 22 10:44:03 zira systemd-logind[792]: VT changed to 1
May 22 10:44:08 zira login[32071]: pam_unix(login:auth): Couldn't open 
/etc/securetty: No such file or directory
May 22 10:44:12 zira login[32071]: pam_unix(login:auth): Couldn't open 
/etc/securetty: No such file or directory
May 22 10:44:12 zira login[32071]: pam_unix(login:session): session opened for 
user vinc17 by LOGIN(uid=0)
May 22 10:44:12 zira systemd-logind[792]: Got message type=method_call 
sender=:1.135 destination=org.freedesktop.login1 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=444 
reply_cookie=0 signature=s error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Got message type=method_return 
sender=org.freedesktop.DBus destination=:1.18 path=n/a interface=n/a member=n/a 
cookie=46 reply_cookie=444 signature=u error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=445 
reply_cookie=0 signature=s error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Got message type=method_return 
sender=org.freedesktop.DBus destination=:1.18 path=n/a interface=n/a member=n/a 
cookie=47 reply_cookie=445 signature=u error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Unable to connect to 
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
May 22 10:44:12 zira systemd-logind[792]: n/a: varlink: setting state 
idle-client
May 22 10:44:12 zira systemd-logind[792]: 
/run/systemd/userdb/io.systemd.DynamicUser: Sending message: 
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":1000,"service":"io.systemd.DynamicUser"}}
May 22 10:44:12 zira systemd-logind[792]: 
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client 
→ awaiting-reply
May 22 10:44:12 zira systemd-logind[792]: 
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message: 
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
May 22 10:44:12 zira systemd-logind[792]: 
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state 
awaiting-reply → processing-reply
May 22 10:44:12 zira systemd-logind[792]: Got lookup error: 
io.systemd.UserDatabase.NoRecordFound
May 22 10:44:12 zira systemd-logind[792]: 
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state 
processing-reply → idle-client
May 22 10:44:12 zira systemd-logind[792]: Starting services for new user vinc17.
May 22 10:44:12 zira systemd-logind[792]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=446 
reply_cookie=0 signature=ss error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Got message type=method_return 
sender=:1.0 destination=:1.18 path=n/a interface=n/a member=n/a cookie=1546 
reply_cookie=446 signature=o error-name=n/a error-message=n/a
May 22 10:44:12 zira systemd-logind[792]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=UserNew cookie=447 
reply_cookie=0 signature=uo error-name=n/a error-message=n/a
May 22 10:44:12 

Bug#911415: flex: yyinput() return value is backward incompatible

[Manoj Srivastava]

On 12:19 Thursday, 21 May 2020 +0200, Bill Allombert wrote
 > On Wed, May 20, 2020 at 10:03:08PM -0700, Manoj Srivastava wrote:
 > > While it is true that the change was incompatible wwith what we
 > >  had befire, the change was made almost four and a half years ago. I
 > >  suspect we have gotten used to it now; and changing it back would just
 > >  cause issues.
 > 
 > Is the new behaviour documented now ?
 > This is needed to use yyinput() properly.

See below. The yyinput usage is demonstrated in an example in
 the info node about generating C++ scanners.


> The commit message does give any rationale or information about this.
 > 
 > > I guess this is the new normal?
 > 
 > Do you mean that sacarstically ?

What make you think that? After 4.5 years of this being the
 default, stating that yyinput returning NULL is normal seems like a
 statement of fact.

Manoj

In Node: 18 Generating C++ Scanners
===
   Here is an example of a simple C++ scanner:

  // An example of using the flex C++ scanner class.
 
 %{
 #include 
 using namespace std;
 int mylineno = 0;
 %}
 
 %option noyywrap c++
 
 string  \"[^\n"]+\"
 
 ws  [ \t]+
 
 alpha   [A-Za-z]
 dig [0-9]
 name({alpha}|{dig}|\$)({alpha}|{dig}|[_.\-/$])*
 num1[-+]?{dig}+\.?([eE][-+]?{dig}+)?
 num2[-+]?{dig}*\.{dig}+([eE][-+]?{dig}+)?
 number  {num1}|{num2}
 
 %%
 
 {ws}/* skip blanks and tabs */
 
 "/*"{
 int c;
 
 while((c = yyinput()) != 0)
 {
 if(c == '\n')
 ++mylineno;
 
 else if(c == '*')
 {
 if((c = yyinput()) == '/')
 break;
 else
 unput(c);
 }
 }
 }
 
 {number}  cout << "number " << YYText() << '\n';
 
 \nmylineno++;
 
 {name}cout << "name " << YYText() << '\n';
 
 {string}  cout << "string " << YYText() << '\n';
 
 %%
 
// This include is required if main() is an another source file.
//#include 
 
 int main( int /* argc */, char** /* argv */ )
 {
 FlexLexer* lexer = new yyFlexLexer;
 while(lexer->yylex() != 0)
 ;
 return 0;
 }

--
Two wrights don't make a rong, they make an airplane.  Or bicycles.
Manoj Srivastava  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C

Bug#961271: libapt-pkg-doc: Please automatically upload libapt-pkg-doc contents to apt-team.pages.debian.net

[Michael Schaller]

Package: libapt-pkg-doc
Severity: normal

Dear Maintainer,

Currently the python-apt-doc contents is automatically uploaded to 
https://apt-team.pages.debian.net/python-apt.

Could this also be setup for libapt-pkg-doc to make the libapt-pkg 
documentation more accessible?

Best,

Michael Schaller

Bug#961270: RM: pdns-recursor/4.0.4-1+deb9u4

[Holger Levsen]

On Fri, May 22, 2020 at 12:01:43PM +0200, Chris Hofstaedtler wrote:
> please remove pdns-recursor with the next/last point release of stretch.
> Security support has ended upstream, and it'd be better if people
> wouldn't run DNS servers that have known security bugs (and we are
> unable to backport those).

FYI,

 debian-security-support (2020.05.22) unstable; urgency=medium
 .
   * Add pdns-recursor to security-support-ended.deb9 as explained in
 DSA-4691-1.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#961272: apt: inconsistent pinning behaviour

[Julian Andres Klode]

Control: tag -1 moreinfo

On Fri, May 22, 2020 at 12:19:54PM +0200, Sergio Gelato wrote:
> Package: apt
> Version: 1.8.2.1
> 
> I'm trying to pin some packages (nvidia stuff) the upgrade of which is best
> followed by an immediate reboot, so that I can upgrade the rest without
> waiting for a reboot window. I came up with the attached preferences
> configuration (based on the list of packages apt-get would otherwise try to
> upgrade on this system), and while it's definitely having some effect it
> seems that "apt-get upgrade" still wants to upgrade some of the pinned
> packages. I see no reason (neither good nor bad-but-documented) for this,
> so I call it a bug.

You have pinned all versions of these packages to the same priority - 10,
including the installed version. I'm wondering more why the other
packages are kept back, I'd expect them to be upgraded too.

What does policy say for them?

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#961229: libnfc: New upstream version: 1.7.2

[Ludovic Rousseau]

On Thu, 21 May 2020 18:37:38 +0200 Ludovic Rousseau  wrote:
> Package: libnfc
> Severity: normal
> 
> Hello,
> 
> A new upstream version of libnfc is now available (after 5 years).
> https://github.com/nfc-tools/libnfc/releases/tag/libnfc-1.7.2
> 
> Maybe it is a good time to package it.

Note that the ABI has changed.
A new version 1.8.0 is planned to change the library soname.

See https://github.com/nfc-tools/libnfc/issues/596

Bye

Bug#960534: Acknowledgement (transition: KDEPIM and KDE Frameworks)

[Sandro Knauß]

Hey,

I forgot about the the auto-kdav transition that is also part of KDEPIM & KDE 
Frameworks transition. That means that auto-kdav is automatically solved 
together with kdepim 20.04 transition.

hefee



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

Bug#961274: python3-tk tries to delete python3.7/tinker libdir

[Witold Baryluk]

Package: python3-tk
Version: 3.8.3-2
Severity: normal

Dear Maintainer,

Unpacking python3-tk:amd64 (3.8.3-2) over (3.8.2-2) ...
dpkg: warning: unable to delete old directory '/usr/lib/python3.7/tkinter': 
Directory not empty



Regards,
Witold

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

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

Versions of packages python3-tk depends on:
ii  blt   2.5.3+dfsg-4+b1
ii  libc6 2.30-8
ii  libtcl8.6 8.6.10+dfsg-1
ii  libtk8.6  8.6.10-1
ii  python3   3.8.2-3
ii  tk8.6-blt2.5  2.5.3+dfsg-4+b1

python3-tk recommends no packages.

Versions of packages python3-tk suggests:
pn  python3-tk-dbg  
ii  tix 8.4.3-10+b1

-- no debconf information

Bug#961277: Please do not depends on dbus-x11 without alternative

[Laurent Bigonville]

Package: terminator
Version: 1.92-2
Severity: normal

Hello,

dbus-x11 has been added about a year ago to the dependencies (see bug
#918149) without an alternative.

This is not OK as dbus-x11 is only needed in case there is not an
already existing dbus user bus running.

The proper dependency should be something like: "default-dbus-session-bus | 
dbus-session-bus"
instead, default-dbus-session-bussee this mail from 2016: 
https://lists.debian.org/debian-devel/2016/08/msg00554.html

Please switch to the recommended dependency.

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)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.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: refpolicy

Versions of packages terminator depends on:
ii  dbus-x11   1.13.14-1
ii  gir1.2-glib-2.01.64.1-1
ii  gir1.2-gtk-3.0 3.24.20-1
ii  gir1.2-pango-1.0   1.44.7-4
ii  gir1.2-vte-2.910.60.2-1
ii  python33.8.2-3
ii  python3-cairo  1.16.2-3
ii  python3-configobj  5.0.6-4
ii  python3-dbus   1.2.16-2
ii  python3-gi 3.36.0-3
ii  python3-gi-cairo   3.36.0-3
ii  python3-psutil 5.7.0-1

Versions of packages terminator recommends:
ii  gir1.2-keybinder-3.0  0.3.2-1+b1
ii  gir1.2-notify-0.7 0.7.9-1
ii  xdg-utils 1.1.3-2

terminator suggests no packages.

-- no debconf information

Bug#961279: Experimental version needs to be ported to mozjs68

[Laurent Bigonville]

Package: policykit-1
Version: 0.116-2
Severity: serious
Tags: experimental

Hello,

policykit-1 0.116 from experimental needs to be ported to mozjs68 now
that mozjs60 is gone from the archive.

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)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.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: refpolicy

Versions of packages policykit-1 depends on:
ii  adduser  3.118
ii  dbus 1.13.14-1
ii  libc62.30-8
ii  libexpat12.2.9-1
ii  libgcc-s1 [libgcc1]  10.1.0-2
ii  libglib2.0-0 2.64.2-1
ii  libmozjs-60-060.8.0-2
ii  libpam-systemd [logind]  245.5-3
ii  libpam0g 1.3.1-5
ii  libpolkit-agent-1-0  0.116-2
ii  libpolkit-gobject-1-00.116-2
ii  libstdc++6   10.1.0-2
ii  libsystemd0  245.5-3

policykit-1 recommends no packages.

policykit-1 suggests no packages.

Versions of packages policykit-1 is related to:
pn  elogind 
pn  libpam-elogind  
ii  libpam-systemd  245.5-3
ii  systemd 245.5-3

-- Configuration Files:
/etc/polkit-1/rules.d/40-debian-sudo.rules [Errno 13] Permission non accordée: 
'/etc/polkit-1/rules.d/40-debian-sudo.rules'
/etc/polkit-1/rules.d/50-default.rules [Errno 13] Permission non accordée: 
'/etc/polkit-1/rules.d/50-default.rules'

-- no debconf information

Bug#961254: libpam-mklocaluser: stop enforcing logout on initial login

[Mike Gabriel]

Package: libpam-mklocaluser
Version: 0.17
Severity: important

The libpam-mklocaluser package is a core component of Debian Edu  
roaming workstations. It creates a local POSIX user account for users  
that exist e.g. in an LDAP database. The libpam-mklocaluser makes it  
possible to prep a machine for a user in a way that makes it possible  
to take the machine off-site.


The libpam-mklocaluser package especially modifies the user's home  
directory when creating this local POSIX user account. Whatever HOME  
path people have in LDAP, on the roaming workstation, all users are  
shoved into /home/.


Over years, however, there has been a design flaw in the tool which I  
could solve last night by reading the pam_python.so code.


The design flaw has been: The current version of libpam-mklocaluser  
enforces a session logout when users do their initial login into a  
machine. Thus, in class room situations, all students have to login  
twice into a notebook/tablet before they can actually use their  
computers. This takes a way 5 minutes of the class's lesson and could  
be avoided.


Attached is a patch that drops the enforcement of the re-login and  
manipulates the HOME env var after the local POSIX user account has  
been fully prepared by libpam-mklocaluser.


I'd love to see this issue solved in Debian buster, too.

This implicitly fixes Debian bug #760496.

Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

diff --git a/debian/pam-python.py b/debian/pam-python.py
index fad6362..4780de1 100755
--- a/debian/pam-python.py
+++ b/debian/pam-python.py
@@ -147,14 +147,8 @@ def check_and_create_localuser(pamh, user):
   # FIXME Should be rewritten in python, I guess
   runcmd(pamh, "if [ -d /etc/mklocaluser.d ]; then ORIGHOMEDIR='%s' 
USER='%s' /bin/run-parts /etc/mklocaluser.d ; fi" % (homedir, user))
 
-  # Let the user know what is going on
-  msg = pamh.Message(pamh.PAM_TEXT_INFO,
- "Local user created in /home/, please log in again to 
start using it.")
-  pamh.conversation(msg)
-
-  # Throw out user, as the log process cached the home directory
-  # and need to be restarted.
-  return pamh.PAM_TRY_AGAIN
+  pamh.env['HOME'] = "/home/%s" % user
+
 except Exception as e:
   syslog.syslog("Failure while creating local user: %s " % (e))
   pass


pgpbXnk9cHRxa.pgp
Description: Digitale PGP-Signatur

Bug#961272: apt: inconsistent pinning behaviour

[Sergio Gelato]

Package: apt
Version: 1.8.2.1

I'm trying to pin some packages (nvidia stuff) the upgrade of which is best
followed by an immediate reboot, so that I can upgrade the rest without
waiting for a reboot window. I came up with the attached preferences
configuration (based on the list of packages apt-get would otherwise try to
upgrade on this system), and while it's definitely having some effect it
seems that "apt-get upgrade" still wants to upgrade some of the pinned
packages. I see no reason (neither good nor bad-but-documented) for this,
so I call it a bug.

(Aside about the use case: I've tried to use "apt-mark hold" instead,
and that works, but puppet doesn't like package holds not implied by
its own manifest and reacts by running "apt-get install", which fails
noisily. I'm still looking for a reasonably painless solution.)

Here is what "apt-get upgrade" prints out:

# apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libegl-nvidia0 libegl-nvidia0:i386 libegl1-nvidia libegl1-nvidia:i386
  libgl1-nvidia-glx libgl1-nvidia-glx:i386 libgles-nvidia1
  libgles-nvidia1:i386 libgles-nvidia2 libgles-nvidia2:i386 libnvidia-cfg1
  libnvidia-eglcore libnvidia-eglcore:i386 libnvidia-glcore
  libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386
  libnvidia-ml1 nvidia-alternative nvidia-driver nvidia-driver-bin
  nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd:i386
  nvidia-driver-libs-nonglvnd-i386:i386 nvidia-kernel-dkms
  nvidia-kernel-support nvidia-nonglvnd-vulkan-icd
  nvidia-nonglvnd-vulkan-icd:i386 nvidia-vdpau-driver
  xserver-xorg-video-nvidia
The following packages will be upgraded:
  nvidia-legacy-check nvidia-nonglvnd-vulkan-common
2 upgraded, 0 newly installed, 0 to remove and 30 not upgraded.
Need to get 430 kB of archives.
After this operation, 22.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

Additional information:

# apt-cache policy nvidia-legacy-check
nvidia-legacy-check:
  Installed: 418.74-1
  Candidate: 440.82-1~bpo10+1
  Version table:
 440.82-1~bpo10+1 10
100 http://deb.debian.org/debian buster-backports/non-free amd64 
Packages
 418.113-1 10
500 http://deb.debian.org/debian buster/non-free amd64 Packages
 *** 418.74-1 10
100 /var/lib/dpkg/status

(and likewise for nvidia-nonglvnd-vulkan-common, nvidia-driver, etc.)
Package:
libegl-nvidia0
libegl-nvidia0:i386
libegl1-nvidia
libegl1-nvidia:i386
libgl1-nvidia-glx
libgl1-nvidia-glx:i386
libgles-nvidia1
libgles-nvidia1:i386
libgles-nvidia2
libgles-nvidia2:i386
libnvidia-cfg1
libnvidia-eglcore
libnvidia-eglcore:i386
libnvidia-glcore
libnvidia-glcore:i386
libnvidia-glvkspirv
libnvidia-glvkspirv:i386
libnvidia-ml1
nvidia-alternative
nvidia-driver
nvidia-driver-bin
nvidia-driver-libs-nonglvnd
nvidia-driver-libs-nonglvnd:i386
nvidia-driver-libs-nonglvnd-i386:i386
nvidia-kernel-dkms
nvidia-kernel-support
nvidia-legacy-check
nvidia-nonglvnd-vulkan-common
nvidia-nonglvnd-vulkan-icd
nvidia-nonglvnd-vulkan-icd:i386
nvidia-vdpau-driver
xserver-xorg-video-nvidia
Pin: version *
Pin-Priority: 10

Bug#961272: Acknowledgement (apt: inconsistent pinning behaviour)

[Sergio Gelato]

control: severity -1 wishlist

I've now seen the error of my ways. Downgrading the severity to "wishlist"
since it appears to work as documented but not in the way I'd find most
useful (and since there doesn't seem to be an "invalid" tag).

My mistake was to specify the same positive priority for all versions of the
pinned packages. This downgrades the priority of the installed version as well.
The reason some packages were still not upgraded in the example shown is that
the pinning allowed versions from backports to be considered, and some of these
were then held back due to their own dependencies.

What I'd like to have is a way to lower the priority of versions other than
the one currently installed, without having to explicitly configure a version
pattern. Yes, setting a hold on the package (or a negative pin priority)
covers most of the associated use cases. Most but maybe not all?

Bug#961225: shotwell: No video thumbails

[Jörg Frings-Fürst]

Hello Loris,

thank you for spending your time helping to make Debian better with
this bug report. 

Am Donnerstag, den 21.05.2020, 18:06 +0200 schrieb loris:
> Package: shotwell
> Version: 0.30.8-1
> Severity: normal
> 
> Dear Maintainer,
> 
> importing video and/or photos, Shotwell shows me only photo
> thumbnails (video thumbnails are not visible).
> Inside Shotwell thumbnail directory  '~/.cache/shotwell/thumbs', all
> jpg video thumbnails are generated but with the same identical
> standard image; it doesn't show me the real video content.
> I have removed 'thumbs' directory inside  '~/.cache/shotwell/' and I
> have launched Shotwell again: it recreate thumbnails inside thumbs
> directory but with same problem described above.
> 

This is a long known problem at shotwell. The possible fix is described
in /usr/share/doc/shotwell/README.Debian.

So I close this bug.

> On my old Pentium4 Fujitsu Siemens I am using xfce 4.14 as desktop
> environment.
> [...]

CU
Jörg

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

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

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


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

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


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



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

Bug#961231: sane: No scanners identified on HP officejet Pro 8610 (all-in-one)

[Jörg Frings-Fürst]

reassign 961231 libsane
tags 961231 + moreinfo
thanks

Hello Loris,


thank you for spending your time helping to make Debian better with
this bug report. 

I think there is a problem in sane-backends. Therefore I move this bug
report there.

Am Donnerstag, den 21.05.2020, 19:16 +0200 schrieb loris:
> Package: sane
> Version: 1.0.14-15
> Severity: normal
> 
> Dear Maintainer,
> 
> I have an HP Officejet Pro 8610 (all-in-one); after last upgrading I
> am not able to use my scanner: the printer works perfectly but
> launching xsane  I get an error message: 'no device has been found'.
> As my printer is connected to router I try to connect it to my pc
> with usb cable:
> 
> With command '~$ sane-find-scanner' I get the the following output:
> 'found USB scanner (vendor=0x03f0 [HP], product=0x7112 [HP Officejet
> Pro 8610]) at libusb:005:011'
> 
> With command '~$ scanimage -L' I get the the following output:
> No scanners were identified
> 
> Connecting a pen-drive to printer usb port and using the printer
> touch panel I am able to scan a document and save it to pen-drive.
> 
> On my old Pentium4 Fujitsu Siemens I am using xfce 4.14 as desktop
> environment,
> [...]

Please add a file "/lib/udev/rules.d/99-libsane.rules", put the context


ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"

in it, reboot and check it again.

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

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

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


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

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


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



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

Bug#933934: unmount bash completion complains about "awk: line 18: function gensub never defined"

[Étienne Mollier]

Étienne Mollier, on 2020-05-21 18:34:03 +0200:
> The patch is now forwarded upstream; CI is ongoing, hopefully I
> haven't broke anything in the process:
> 
>   https://github.com/karelzak/util-linux/pull/1045
> 
> Will see how the issue evolves...

Looks like it will make it to a next upstream release I guess.
:)

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
Help find cures against the Covid-19 !  Give CPU cycles:
  * Rosetta@home: https://boinc.bakerlab.org/rosetta/
  * Folding@home: https://foldingathome.org/


signature.asc
Description: PGP signature

Bug#961267: Regression: usb quirks: 3x slower seq reads on 090c:1000 Silicon Motion based flash drives

[Atanas]

Package: src:linux
Version: 4.19.118-2
Severity: normal
Tags: upstream

Dear Maintainer,

   * What led up to the situation?

Applying the latest Debian stable updates.

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

Nothing.

   * What was the outcome of this action?

3-4 times slower sequential read performance.

That is on 3 different USB3 sticks all using the above mentioned controller 
ID:
- Samsung Flash Drive FIT, 32GB and 64GB - seq reads down from 150+ to 
under 50 MB/s
- Intenso High Speed Line, 64GB - seq reads down from 300+ to under 100 MB/s

   * What outcome did you expect instead?

Same as it was before the update, 150-300 MB/s.

Tracked this down to the following commit: 
https://lkml.org/lkml/2020/3/10/422
Debian changelog: - usb: storage: Add quirk for Samsung Fit flash

   * Workaround:

Removing the quirk (e.g. setting "options usb_storage quirks=090c:1000:"
in /etc/modprobe.d) restores the previous performance levels.


-- Package-specific info:
** Version:
Linux version 4.19.0-9-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.118-2 (2020-04-29)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-amd64 
root=UUID=03da06a4-cb81-421b-a877-cf1afd5ef4b1 ro quiet splash

** Not tainted

** Kernel log:
[6.367047] Bluetooth: HCI socket layer initialized
[6.367052] Bluetooth: L2CAP socket layer initialized
[6.367059] Bluetooth: SCO socket layer initialized
[6.380684] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[6.391471] usbcore: registered new interface driver btusb
[6.417648] Bluetooth: hci0: read Intel version: 370810011003110e32
[6.417650] Bluetooth: hci0: Intel device is already patched. patch num: 32
[6.422478] uvcvideo: Found UVC 1.00 device USB2.0 HD UVC WebCam (0bda:57cb)
[6.453552] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[6.453556] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[6.453560] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[6.453562] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[6.453564] snd_hda_codec_realtek hdaudioC0D0:inputs:
[6.453568] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[6.453571] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[6.453574] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[6.458180] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 
7265, REV=0x210
[6.481453] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[6.487486] dell_smbios: Unable to run on non-Dell system
[6.487659] iwlwifi :01:00.0: base HW address: 18:5e:0f:0f:0c:3a
[6.491916] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not 
initialized!
[6.491919] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not 
initialized!
[6.491921] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not 
initialized!
[6.492023] input: USB2.0 HD UVC WebCam: USB2.0 HD as 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input9
[6.492128] usbcore: registered new interface driver uvcvideo
[6.492129] USB Video Class driver (1.1.1)
[6.520296] snd_hda_codec_realtek hdaudioC0D0: Failed to find dell wmi 
symbol dell_micmute_led_set
[6.545924] intel_rapl: Found RAPL domain package
[6.545928] intel_rapl: Found RAPL domain core
[6.545930] intel_rapl: Found RAPL domain uncore
[6.545931] intel_rapl: Found RAPL domain dram
[6.560851] Adding 3684032k swap on /dev/sda10.  Priority:-2 extents:1 
across:3684032k SSFS
[6.572637] XFS (sda5): Mounting V5 Filesystem
[6.576186] XFS (sda8): Mounting V5 Filesystem
[6.595142] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[6.596374] thermal thermal_zone9: failed to read out thermal zone (-61)
[6.603067] XFS (sda8): Ending clean mount
[6.603264] XFS (sda5): Ending clean mount
[6.611653] iwlwifi :01:00.0 wlp1s0: renamed from wlan0
[6.649801] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input10
[6.649919] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input11
[6.650033] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input12
[6.650136] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[6.650237] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[6.650340] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input15
[6.767539] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need 

Bug#933934: unmount bash completion complains about "awk: line 18: function gensub never defined"

[Chris Hofstaedtler]

* Étienne Mollier  [200522 11:57]:
> Étienne Mollier, on 2020-05-21 18:34:03 +0200:
> > The patch is now forwarded upstream; CI is ongoing, hopefully I
> > haven't broke anything in the process:
> > 
> > https://github.com/karelzak/util-linux/pull/1045
> > 
> > Will see how the issue evolves...
> 
> Looks like it will make it to a next upstream release I guess.
> :)

Awesome!

Thanks for following up on this, everyone.

Chris

Bug#960727: errors during upgrade

[Witold Baryluk]

Package: python3-lib2to3
Version: 3.8.3-2
Followup-For: Bug #960727

Yep, still there, even when trying to update from recent version.

It is refering to python3.7 for some reasons.

Preparing to unpack .../159-python3-lib2to3_3.8.3-2_all.deb ...
Unpacking python3-lib2to3 (3.8.3-2) over (3.8.2-2) ...
...
Setting up python3-lib2to3 (3.8.3-2) ...
find: ‘/usr/lib/python3.7/lib2to3’: No such file or directory
find: ‘/usr/lib/python3.7/lib2to3’: No such file or directory
...


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

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

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

python3-lib2to3 recommends no packages.

python3-lib2to3 suggests no packages.

-- no debconf information

Bug#961275: buster-pu: package jameica/2.8.4+dfsg-1

[Jochen Sprickerhof]

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

Hi SRMs,

I would like to update jameica in buster to allow use of SynTax, a
jameica plugin not packaged in Debian. The attached patch adds
mckoisqldb.jar to the classpath, as done by upstream and was only
removed in debian/patches by accident. The dependency to
libmckoisqldb-java is already fulfilled through jameica ->
libjameica-datasource-java -> libmckoisqldb-java and only added to make
it explicit.
Due to the dependency already present and just adding an extra jar, I
don't expect side effects. This has also been tested in unstable and
testing.

The original problem was reported by a PureOS user via mail, so there is
no corresponding bug in the BTS, but I can create one if you want me to.

Cheers Jochen

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 36a0e90c15bef9fa07e7b6e35c73a3c7d32b5352 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Thu, 14 May 2020 14:09:40 +0200
Subject: [PATCH] Add mckoisqldb to classpath

This is needed for SynTAX and was accidentally removed in
debian/patches/0001-*.patch.
---
 debian/changelog  |  8 
 debian/control|  1 +
 ...0005-Add-mckoisqldb.jar-to-classpath.patch | 20 +++
 debian/patches/series |  1 +
 4 files changed, 30 insertions(+)
 create mode 100644 debian/patches/0005-Add-mckoisqldb.jar-to-classpath.patch

diff --git a/debian/changelog b/debian/changelog
index 6835661..95cb534 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+jameica (2.8.4+dfsg-1+deb10u1) buster; urgency=medium
+
+  * Add mckoisqldb to classpath.
+This is needed for SynTAX and was accidentally removed in
+debian/patches/0001-*.patch.
+
+ -- Jochen Sprickerhof   Thu, 14 May 2020 14:18:17 +0200
+
 jameica (2.8.4+dfsg-1) unstable; urgency=medium
 
   * New upstream version 2.8.4+dfsg
diff --git a/debian/control b/debian/control
index 6a719de..9919475 100644
--- a/debian/control
+++ b/debian/control
@@ -48,6 +48,7 @@ Depends:
  libjameica-util-java,
  libjaxb-api-java,
  libjaxb-java,
+ libmckoisqldb-java,
  libmariadb-java,
  libnanoxml2-java,
  libpaperclips-java,
diff --git a/debian/patches/0005-Add-mckoisqldb.jar-to-classpath.patch 
b/debian/patches/0005-Add-mckoisqldb.jar-to-classpath.patch
new file mode 100644
index 000..5628849
--- /dev/null
+++ b/debian/patches/0005-Add-mckoisqldb.jar-to-classpath.patch
@@ -0,0 +1,20 @@
+From: Jochen Sprickerhof 
+Date: Thu, 14 May 2020 14:04:46 +0200
+Subject: Add mckoisqldb.jar to classpath
+
+---
+ build/build.properties | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/build/build.properties b/build/build.properties
+index 27ed9b5..4383191 100644
+--- a/build/build.properties
 b/build/build.properties
+@@ -43,6 +43,7 @@ define.commonlibs   = /usr/share/java/bcpkix.jar 
\
+   /usr/share/java/velocity.jar \
+   /usr/share/java/oro.jar \
+   /usr/share/java/h2.jar \
++  /usr/share/java/mckoisqldb.jar \
+   /usr/share/java/mariadb-java-client.jar \
+   img \
+   lang \
diff --git a/debian/patches/series b/debian/patches/series
index 6fc9ea3..d628900 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@
 0002-Adopt-build.xml.patch
 0003-Adopt-jameica-executable.patch
 0004-mariadb.patch
+0005-Add-mckoisqldb.jar-to-classpath.patch
-- 
2.27.0.rc0

Bug#961269: thunderbird: DENIED operation="mkdir" name=/run/user/ /dconf requested_mask="c"

[xiscu]

Package: apparmor
Version: 2.13.4-1+b1
Severity: minor

Dear Maintainer,
I'm getting apparmor DENIED audit messages on the logs concerning thunderbird:

 audit[24604]: AVC apparmor="DENIED" operation="mkdir" profile="thunderbird" 
name="/run/user/1000/dconf/" pid=24604 comm="thunderbird" requested_mask="c" 
denied_mask="c" fsuid=1000 ouid=1000
 audit: type=1400 audit(1590141596.662:242): apparmor="DENIED" 
operation="mkdir" profile="thunderbird" name="/run/user/1000/dconf/" pid=24604 
comm="thunderbird" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

I keep showing the logs with:

> journalctl -l

and then I start thunderbird

Thanks in advance!
xiscu

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

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

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libc6  2.30-8
ii  lsb-base   11.1.0
ii  python33.8.2-3

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles-extra  1.27
ii  apparmor-utils   2.13.4-1+b1

-- debconf information:
  apparmor/homedirs:

Bug#961270: RM: pdns-recursor/4.0.4-1+deb9u4

[Chris Hofstaedtler]

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

Dear (old-)Stable Release Managers,

please remove pdns-recursor with the next/last point release of stretch.
Security support has ended upstream, and it'd be better if people
wouldn't run DNS servers that have known security bugs (and we are
unable to backport those).

DSA-4691-1 echoes this.

Thanks,
Chris

Bug#958899: dbab: /etc/init.d/dbab stop does not stop

[Kevin Ryde]

reopen 958899
thanks

Alas, with version 1.5.01-1, and init-system-helpers 1.57,

/etc/init.d/dbab stop

still does not stop the running server.

It looks like when /etc/init.d/dbab sources /lib/init/init-d-script,
that one ends with "exit", so the intended dbab-init-d-script never
runs.  Supposing I guess the intention rightly :).  In any case
/lib/init/init-d-script doesn't seem to work to stop a perl daemon.

As a suggestion, I wouldn't be a hurry to use /lib/init/init-d-script.
For a straightforward start/stop, start-stop-daemon does all you need.

Bug#961259: dbab: daemon start/stop on install/remove

[Kevin Ryde]

Package: dbab
Version: 1.5.01-1
Severity: normal

Under the standard "init", on first installing the dbab package, the
dbab-svr daemon is not started.  And on a remove or purge, it is not
stopped (that's after a fix to /etc/init.d/dbab so stop works).

Letting dh_installinit put code into postinst etc has done the right
thing for me in a package of my own, for under init at least.


-- System Information:
Debian Release: bullseye/sid
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dbab depends on:
ii  curl  7.67.0-2
ii  dnsmasq   2.80-1.1
ii  dnsutils  1:9.11.5.P4+dfsg-5.1+b1
ii  perl  5.30.0-9

Bug#961278: ip route json output invalid in Buster (fixed upstream)

[Oskar Berggren]

Package: iproute2
Version: 4.20.0-2
Tags: patch

ip route in Buster generates an invalid JSON if the route type has to
be printed,
eg. when detailed mode is active, or the type is different that unicast:

$ ip -d -j -p route show
[ {"unicast",
"dst": "192.168.122.0/24",
"dev": "virbr0",
"protocol": "kernel",
"scope": "link",
"prefsrc": "192.168.122.1",
"flags": [ "linkdown" ]
} ]

$ ip -j -p route show
[ {"unreachable",
"dst": "192.168.23.0/24",
"flags": [ ]
},{"prohibit",
"dst": "192.168.24.0/24",
"flags": [ ]
},{"blackhole",
"dst": "192.168.25.0/24",
"flags": [ ]
} ]

Fix it by printing the route type as the "type" attribute:

$ ip -d -j -p route show
[ {
"type": "unicast",
"dst": "default",
"gateway": "192.168.85.1",
"dev": "wlp3s0",
"protocol": "dhcp",
"scope": "global",
"metric": 600,
"flags": [ ]
} ]


Small upstream fix is available since March 2019:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=073661773872709518d35d4d093f3a715281f21d

This bug renders the json output in Debian Buster unusable which is a
bad problem for my system that wants to parse it.

Best regards,
Oskar

Bug#961229: libnfc: New upstream version: 1.7.2

[Ludovic Rousseau]

retitle 961229 libnfc: New upstream version: 1.8.0
thank

On Fri, 22 May 2020 13:39:28 +0200 Ludovic Rousseau  
wrote:
> On Thu, 21 May 2020 18:37:38 +0200 Ludovic Rousseau  
> wrote:
> > Package: libnfc
> > Severity: normal
> > 
> > Hello,
> > 
> > A new upstream version of libnfc is now available (after 5 years).
> > https://github.com/nfc-tools/libnfc/releases/tag/libnfc-1.7.2
> > 
> > Maybe it is a good time to package it.
> 
> Note that the ABI has changed.
> A new version 1.8.0 is planned to change the library soname.
> 
> See https://github.com/nfc-tools/libnfc/issues/596

Version 1.8.0 is now available.
https://github.com/nfc-tools/libnfc/releases/tag/libnfc-1.8.0

Bye

Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.

[Helmut Grohne]

Control: clone -1 -2
Control: reassign -2 src:guile-3.0

On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> While bootstrap testing unstable, I noticed that guile-2.2 fails to
> build from source (natively). A build now ends quicky:
> 
> | dpkg-buildpackage: info: source package guile-2.2
> | dpkg-buildpackage: info: source version 2.2.7+1-5
> | dpkg-buildpackage: info: source distribution unstable
> | dpkg-buildpackage: info: source changed by Rob Browning 
> 
> |  dpkg-source --before-build .
> | dpkg-buildpackage: info: host architecture amd64
> |  fakeroot debian/rules clean
> | /bin/bash: ${\#x}: bad substitution
> | debian/rules:70: *** ERROR: alternatives priority expects min version < 
> 1000.  Stop.
> | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
> 
> This only happens since make-dfsg/4.3-1, but I think the bug here
> ultimately is with guile-2.2. The relevant code from debian/rules is:
> 
> | ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo ok;))
> |   $(error ERROR: alternatives priority expects min version < 1000)
> | endif
> 
> It is surprising that this didn't fail with earlier versions of make.
> The shell substitution is clearly wrong. It is unclear what it is
> supposed to achieve. In any case, deleting these lines makes the build
> proceed.

guile-3.0 also has this exact same bug.

Helmut

Bug#961281: qgis-providers: crssync in postinst: free(): invalid pointer SIGABRT

[Marcel Partap]

Package: qgis-providers
Version: 3.10.5+dfsg-2+b1
Severity: normal

So the postinst script calls crssync which breaks:

free(): invalid pointer

Program received signal SIGABRT, Aborted.

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x750bd55b in __GI_abort () at abort.c:79
#2  0x75116008 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x75222f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x7511d3aa in malloc_printerr (str=str@entry=0x752210e0
"free(): invalid pointer") at malloc.c:5339
#4  0x7511ed9c in _int_free (av=, p=,
have_lock=0) at malloc.c:4173
#5  0x74bb757c in osgeo::proj::common::UnitOfMeasure::~UnitOfMeasure()
() at /lib/x86_64-linux-gnu/libproj.so.19
#6  0x750d6426 in __cxa_finalize (d=0x7fffed9b9000) at
cxa_finalize.c:83
#7  0x7fffed79cd93 in  () at /lib/x86_64-linux-gnu/libproj.so.15
#8  0x7fffe740 in  ()
#9  0x77fe36f3 in _dl_fini () at dl-fini.c:138



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

Kernel: Linux 5.5.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qgis-providers depends on:
ii  dpkg  1.19.7
ii  libc6 2.30-4
ii  libexpat1 2.2.9-1
ii  libgcc-s1 10.1.0-1
ii  libgdal26 3.0.4+dfsg-1+b6
ii  libhdf5-103-1 1.10.6+repack-2
ii  libnetcdf18   1:4.7.4-1
ii  libpq512.0-1+b1
ii  libqca-qt5-2  2.2.1-2
ii  libqca-qt5-2-plugins  2.2.1-2
ii  libqgis-core3.10.53.10.5+dfsg-2+b1
ii  libqgis-gui3.10.5 3.10.5+dfsg-2+b1
ii  libqscintilla2-qt5-15 2.11.2+dfsg-6+b1
ii  libqt5core5a [qtbase-abi-5-12-5]  5.12.5+dfsg-2
ii  libqt5gui55.12.5+dfsg-2
ii  libqt5network55.12.5+dfsg-2
ii  libqt5sql55.12.5+dfsg-2
ii  libqt5sql5-sqlite 5.12.5+dfsg-2
ii  libqt5webkit5 5.212.0~alpha3-5
ii  libqt5widgets55.12.5+dfsg-2
ii  libqt5xml55.12.5+dfsg-2
ii  libspatialite74.3.0a-6+b1
ii  libsqlite3-0  3.31.1-4
ii  libstdc++69.2.1-18
ii  libxml2   2.9.4+dfsg1-7+b3
ii  qgis-providers-common 3.10.5+dfsg-2

qgis-providers recommends no packages.

qgis-providers suggests no packages.

-- no debconf information

Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

[Florian Bruhin]

Hey,

Upstream here - no idea what's happening there I'm afraid. I'm guessing you'll
have similar issues with other Qt/QtWebEngine applications as well though, I
doubt this is qutebrowser-specific. Can you try with e.g. Falkon as well?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#926343: RFP into ITP for #92643 - libaxc packaging

[Henry-Nicolas Tourneur]

Dear,

Evangelos and myself are going to work on packaging libaxc via the 
Debian On Mobile team.
This package is a pre-requisite for purple-lurch which we would like to 
add into Debian as well, so that OMEMO would work with Chatty 
(currently in NEW).


Best regards,

Henry-Nicolas Tourneur
Matrix id: @hntourne:matrix.nilux.be

Bug#961285: theme-d-gnome: Failed to migrate to testing for too long

[Boyuan Yang]

Source: theme-d-gnome
Version: 0.9.0-1
Severity: serious
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: tommi.hoynalan...@iki.fi alteh...@debian.org


Dear maintainer(s),

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

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

Currently your package only needs another source-only upload to be able
tomigrate to Testing; please refer to 
https://wiki.debian.org/SourceOnlyUpload
to see how to make a source-only upload. Let me know if you need any
help in package sponsorship.

Regards,
Boyuan Yang

[1] 
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html


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

Bug#910108: RFP: git-bug -- Distributed bug tracker embedded in Git

[Yaroslav Halchenko]

I would have loved to see this one in debian as well!  May be someone
from Debian Go Team could have paved the way 

On Tue, 02 Oct 2018, Antoine Beaupre wrote:

> Package: wnpp
> Severity: wishlist

> * Package name: git-bug
>   Version : 0.3.0
>   Upstream Author : Michael Muré 
> * URL : https://github.com/MichaelMure/git-bug
> * License : GPL-3+
>   Programming Lang: Golang
>   Description : Distributed bug tracker embedded in Git

> git-bug is a distributed bug tracker embedded in git. It uses git's
> internal storage so no files are added in your project.

> As you would do with commits and branches, you can push your bugs to
> the same git remote you are already using to collaborate with other
> people.

> ==

> I've been maintaining bugs-everywhere (BE) in Debian for a while now,
> which accomplishes a similar goal, but with bugs stored in branches
> (or in files? i forgot). In any case, BE is unmaintained now and this
> looks like a promising alternative, particularly with future two-way
> integration with upstream bugtrackers (e.g. GitHub import for now).

> It probably has (too many) golang dependencies that need to be bundled
> and all that usual stuff.

> Golang team maintenance, most likely. Documented here to share it with
> the Debian community and make sure there's no work duplicated.

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#959865: New version fixes this issue

[Martina Ferrari]

Hi,

I was just trying this extension after moving from firefox-esr to
firefox/sid, and noticed it did not work.

But if I install the latest version from
https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ it works
again, so packaging a new version should fix this.

-- 
Martina Ferrari (Tina)

Bug#961122: 1.5.0.87+dfsg1-1 is out of the way already

[Julien Puydt]

Hi,

I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the 20th
of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march, and
unstable had it since the 4th of march.

Isn't the problem history already?

JP

Bug#960271: Status on bug 960271 - 'BITS_PER_LONG' wrongly used

[Lukas Straub]

Hello Everyone,
When will this fix be released?

Regards,
Lukas Straub


pgpiQp_Q0hiTt.pgp
Description: OpenPGP digital signature

Bug#912846: grub2: stop depending on ttf-dejavu-core

[Fabian Greffrath]

Control: reassign -1 grub2
Control: found -1 2.04-7
Control: retitle -1 please migrate to fonts-dejavu-core
Control: tags -1 =patch


I am reassigning this bug back again to the grub2 package.

The ttf-dejavu-core package has been a transitional package for 7 years
(!) now and its removal is going to happen with the next package
upload, which will be anytime soon. Please adjust your package's build-
dependencies to fonts-dejavu-core and add the corresponding search path
to configure.ac. I have already prepared a patch for the latter.

Thanks,

 - Fabian

From a696233f623e9c2b480aa3ad10aed537c2890af6 Mon Sep 17 00:00:00 2001
From: Fabian Greffrath 
Date: Tue, 19 May 2020 12:19:26 +0200
Subject: [PATCH] add /u/s/fonts/truetype/dejavu to the DejaVu fonts search
 paths

---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index b2576b0..41b8758 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1669,7 +1669,7 @@ fi
 
 if test x"$starfield_excuse" = x; then
for ext in pcf pcf.gz bdf bdf.gz ttf ttf.gz; do
- for dir in . /usr/src /usr/share/fonts/X11/misc /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/dejavu /usr/share/fonts/truetype; do
+ for dir in . /usr/src /usr/share/fonts/X11/misc /usr/share/fonts/truetype/dejavu /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/dejavu /usr/share/fonts/truetype; do
 if test -f "$dir/DejaVuSans.$ext"; then
   DJVU_FONT_SOURCE="$dir/DejaVuSans.$ext"
   break 2
-- 
2.26.2



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

Bug#930085: reportbug gtk gui crashes

[Nis Martensen]

control: merge 709862 930085
control: tags 709862 patch

> >   Traceback (most recent call last):
> > File "/usr/bin/reportbug", line 2285, in 
> >   main()
> > File "/usr/bin/reportbug", line 1115, in main
> >   return iface.user_interface()
> > File "/usr/bin/reportbug", line 1728, in user_interface
> >   latest_first=self.options.latest_first)
> > File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 
> > 1763, in func
> >   args, kwargs = op.sync_pre_operation(*args, **kwargs)
> >   TypeError: cannot unpack non-iterable NoneType object
> 
> 
> > -- System Information:
> > Distributor ID: Kali
> > Description:Kali GNU/Linux Rolling
> 
> The crash is very likely caused by a system administration error. Please see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892270

Anyway reportbug should not crash, not even on non-Debian systems. This
has been reported multiple times already; merging this bug with a
previous instance.

This can be fixed with a small change:
https://salsa.debian.org/reportbug-team/reportbug/-/merge_requests/60

Bug#961282: Support both MariaDB and MySQL on test_mysql.sh

[Sergio Durigan Junior]

Source: libdbi-drivers
Version: 0.9.0-9
Tags: patch
Usertags: origin-ubuntu ubuntu-patch

Hi there,

I would like to propose a patch to implement support for using MySQL
when running the test_mysql.sh script.  Even though Debian uses MariaDB
as its default database, we still ship MySQL and some users might prefer
it.

The Ubuntu libdbi-drivers package carries a similar version of this
patch, but with the opposite problem: because Ubuntu's default database
is MySQL, the patch doesn't support MariaDB.  I am working towards
having a single version of the patch which can work with both databases.

This patch does not change the current behaviour of the script: it still
works normally with MariaDB.  I also tested building libdbi-drivers
using MySQL, and the package now builds fine (it was failing before).

I'm providing a debdiff attached to this message, without a changelog
entry.

Thanks a lot for considering this!

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

diff -Nru libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch
--- libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch	1969-12-31 19:00:00.0 -0500
+++ libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch	2020-05-15 15:37:26.0 -0400
@@ -0,0 +1,56 @@
+Description: Fix build errors with MySQL 8.0
+ The mysql_install_db script has been removed, and replaced with
+ the --initialize options for mysqld.
+ Also add -uroot to mysqladmin calls so package can be built without
+ root.
+Author: Lars Tangvald 
+Forwarded: no
+Last-Update: 2019-07-16
+
+Index: libdbi-drivers-0.9.0/tests/test_mysql.sh
+===
+--- libdbi-drivers-0.9.0.orig/tests/test_mysql.sh	2020-05-22 00:06:19.128004409 -0400
 libdbi-drivers-0.9.0/tests/test_mysql.sh	2020-05-22 00:07:58.055128289 -0400
+@@ -36,8 +36,23 @@
+ B=`basename "$MYTMPDIR"`
+ ABSMYTMPDIR="`cd \"$D\" 2>/dev/null && pwd || echo \"$D\"`/$B"
+ 
+-# --force is needed because buildd's can't resolve their own hostnames to ips
+-mysql_install_db --no-defaults --datadir=${ABSMYTMPDIR} --force --skip-name-resolve --user=${ME}
++if $MYMYSQLD --help 2>&1 | grep -q MariaDB 2>&1 > /dev/null; then
++is_mariadb=yes
++else
++is_mariadb=no
++fi
++
++if [ $is_mariadb = "yes" ]; then
++# --force is needed because buildd's can't resolve their own hostnames to ips
++mysql_install_db --no-defaults --datadir=${ABSMYTMPDIR} --force --skip-name-resolve --user=${ME}
++$MYMYSQLD --no-defaults --skip-grant --user=${ME} --socket=${ABSMYTMPDIR}/mysql.sock --datadir=${ABSMYTMPDIR} --skip-networking &
++else
++$MYMYSQLD --no-defaults --initialize-insecure --user=${ME} --datadir=${ABSMYTMPDIR}
++$MYMYSQLD --no-defaults --skip-grant --user=${ME} --socket=${ABSMYTMPDIR}/mysql.sock --datadir=${ABSMYTMPDIR} --skip-networking &
++fi
++
++
++$MYMYSQLD --no-defaults --initialize-insecure --user=${ME} --datadir=${ABSMYTMPDIR}
+ $MYMYSQLD --no-defaults --skip-grant --user=${ME} --socket=${ABSMYTMPDIR}/mysql.sock --datadir=${ABSMYTMPDIR} --skip-networking &
+ 
+ # mysqld needs some time to come up to speed. This avoids irritating error messages from the subsequent loop
+@@ -49,7 +64,7 @@
+ 
+ echo -n pinging mysqld.
+ attempts=0
+-while ! mysqladmin --socket=${ABSMYTMPDIR}/mysql.sock ping ; do
++while ! mysqladmin -uroot --socket=${ABSMYTMPDIR}/mysql.sock ping ; do
+ 	sleep 3
+ 	attempts=$((attempts+1))
+ 	if [ ${attempts} -gt 10 ] ; then
+@@ -71,6 +86,6 @@
+ 
+ ecode=$?
+ 
+-mysqladmin --socket=${ABSMYTMPDIR}/mysql.sock shutdown
++mysqladmin -uroot --socket=${ABSMYTMPDIR}/mysql.sock shutdown
+ rm -rf ${ABSMYTMPDIR}
+ exit ${ecode}
diff -Nru libdbi-drivers-0.9.0/debian/patches/series libdbi-drivers-0.9.0/debian/patches/series
--- libdbi-drivers-0.9.0/debian/patches/series	2020-02-28 12:08:27.0 -0500
+++ libdbi-drivers-0.9.0/debian/patches/series	2020-05-15 15:37:26.0 -0400
@@ -8,3 +8,4 @@
 pgsql_precision.patch
 test_exception_failure.patch
 test_mariadb_date_tz.patch
+fix-mysql-test.patch
diff -Nru libdbi-drivers-0.9.0/debian/test_mysql.sh libdbi-drivers-0.9.0/debian/test_mysql.sh
--- libdbi-drivers-0.9.0/debian/test_mysql.sh	2020-02-08 03:47:26.0 -0500
+++ libdbi-drivers-0.9.0/debian/test_mysql.sh	2020-05-15 15:37:26.0 -0400
@@ -26,9 +26,21 @@
 MYTEMP_DIR=`mktemp -d`
 ME=`whoami`
 
-# --force is needed because buildd's can't resolve their own hostnames to ips
-mysql_install_db --no-defaults --datadir=${MYTEMP_DIR} --force --skip-name-resolve --user=${ME}
-/usr/sbin/mysqld --no-defaults --skip-grant --user=${ME} --socket=${MYTEMP_DIR}/mysql.sock --datadir=${MYTEMP_DIR} --skip-networking &
+# Check if we're running under MariaDB or MySQL.
+if /usr/bin/mysqladmin 2>&1 | grep -q MariaDB 2>&1 > /dev/null; then
+is_mariadb=yes
+else
+is_mariadb=no
+fi
+
+if [ 

Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries

[Boyuan Yang]

Control: reopen -1
Control: found -1 0.9.0-1
Control: tags -1 +bullseye +sid -pending
Control: forcemerge 960584 961285
X-Debbugs-CC: elb...@debian.org

This bug is actually not fixed. Reopening and tagging accordingly. Let
me know if you have any questions or need any help.

-- 
Regards,
Boyuan Yang


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

Bug#926344: RFP into ITP for #926344 - libomemo packaging

[Henry-Nicolas Tourneur]

Dear,

Evangelos and myself are going to work on packaging libomemo via the 
Debian On Mobile team.
This package is a pre-requisite for purple-lurch which we would like to 
add into Debian as well, so that OMEMO would work with Chatty 
(currently in NEW).


Best regards,

Henry-Nicolas Tourneur
Matrix id: @hntourne:matrix.nilux.be

Bug#912846: grub2: stop depending on ttf-dejavu-core

[Colin Watson]

On Fri, May 22, 2020 at 04:30:16PM +0200, Fabian Greffrath wrote:
> The ttf-dejavu-core package has been a transitional package for 7 years
> (!) now and its removal is going to happen with the next package
> upload, which will be anytime soon. Please adjust your package's build-
> dependencies to fonts-dejavu-core and add the corresponding search path
> to configure.ac. I have already prepared a patch for the latter.

Hi - thanks for the patch.  I expect I can apply this, but could you
please also send it upstream (grub-de...@gnu.org)?  I don't see a reason
it couldn't be applied there, and it would make ongoing maintenance
easier.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#961269: thunderbird: DENIED operation="mkdir" name=/run/user/ /dconf requested_mask="c"

[Vincas Dargis]

Control: reassign -1 thunderbird

Reassigning to thunderbird, as it ships it's AppArmor profile itself.

We have this rule there:

owner /run/user/[0-9]*/dconf/user rw,

But it it does not handle the case when parent dir is missing. It does not reproduce in my KDE 
desktop. Maybe you use some minimal desktop where Thunderbird is the first that deals with that 
dconf stuff?


Anyhow, we should update thunderbird profile.

Bug#961269: thunderbird: DENIED operation="mkdir" name=/run/user/ /dconf requested_mask="c"

[Vincas Dargis]

xiscu, could you please create `/etc/apparmor.d/local/usr.bin.thunderbird` file 
with this rule:

owner /run/user/[0-9]*/dconf/ w,

After that, restart AppArmor with `sudo systemctl restart apparmor`. Then, try starting Thunderbird 
again, and see if that error is gone?

Bug#961231: sane: No scanners identified on HP officejet Pro 8610 (all-in-one)

[Jörg Frings-Fürst]

Hello Loris,


I found that your scanner isn't supported by sane-backends.

You have update hplip. So I think your bug is located there.

Please file
a new bug again hplip.

Bug closed.

CU
Jörg

Am Freitag, den 22.05.2020, 14:46 +0200 schrieb Jörg Frings-
Fürst:
> reassign 961231 libsane
> tags 961231 + moreinfo
> thanks
> 
> Hello Loris,
> 
> 
> thank you for spending your time helping to make Debian better with
> this bug report. 
> 
> I think there is a problem in sane-backends. Therefore I move this
> bug
> report there.
> 
> Am Donnerstag, den 21.05.2020, 19:16 +0200 schrieb loris:
> > Package: sane
> > Version: 1.0.14-15
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I have an HP Officejet Pro 8610 (all-in-one); after last upgrading
> > I
> > am not able to use my scanner: the printer works perfectly but
> > launching xsane  I get an error message: 'no device has been
> > found'.
> > As my printer is connected to router I try to connect it to my pc
> > with usb cable:
> > 
> > With command '~$ sane-find-scanner' I get the the following output:
> > 'found USB scanner (vendor=0x03f0 [HP], product=0x7112 [HP
> > Officejet
> > Pro 8610]) at libusb:005:011'
> > 
> > With command '~$ scanimage -L' I get the the following output:
> > No scanners were identified
> > 
> > Connecting a pen-drive to printer usb port and using the printer
> > touch panel I am able to scan a document and save it to pen-drive.
> > 
> > On my old Pentium4 Fujitsu Siemens I am using xfce 4.14 as desktop
> > environment,
> > [...]
> 
> Please add a file "/lib/udev/rules.d/99-libsane.rules", put the
> context
> 
> 
> ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw
> $env{DEVNAME}"
> 
> in it, reboot and check it again.
> 
> CU 
> Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

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

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


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

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


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



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

Bug#961283: libhttp-tiny-perl: Don't release with bullseye

[Dominic Hargreaves]

Package: libhttp-tiny-perl
Version: 0.076-1
Severity: serious
Justification: maintainer

libhttp-tiny-perl at this version should not be released with
bullseye, since perl contains the same version.

Bug#961284: nix: FTBFS on armel and mipsel

[Boyuan Yang]

Source: nix
Version: 2.3.4+dfsg3-1
Severity: normal
X-Debbugs-CC: t...@debian.org

Dear Debian nix package maintainer,

Congratulations on getting nix into Debian!

As you can see from the buildd log, the package currently FTBFS on
armel and mipsel: https://buildd.debian.org/status/package.php?p=nix

===
g++ -std=c++17 -o /<>/src/libutil/libnixutil.so -shared
-L/usr/lib/arm-linux-gnueabi -Wl,-z,relro -Wl,-z,now -L/usr/lib/arm-
linux-gnueabi -Wl,-z,relro -Wl,-z,now -Wl,--no-copy-dt-needed-entries
src/libutil/affinity.o src/libutil/archive.o src/libutil/args.o
src/libutil/compression.o src/libutil/config.o src/libutil/hash.o
src/libutil/json.o src/libutil/logging.o src/libutil/serialise.o
src/libutil/thread-pool.o src/libutil/util.o src/libutil/xml-writer.o
-llzma -lbz2 -pthread -lcrypto -lbrotlienc -lbrotlidec -L/usr/lib/arm-
linux-gnueabi -lboost_context -Wl,-z,defs -Wl,-soname=libnixutil.so   
/usr/bin/ld: src/libutil/logging.o: in function
`std::__atomic_base::fetch_add(unsigned long long,
std::memory_order)':
/usr/include/c++/9/bits/atomic_base.h:541: undefined reference to
`__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[1]: *** [mk/lib.mk:104: src/libutil/libnixutil.so] Error 1


I'm not familiar with nix and/or gcc so unfortunately I cannot provide
any suggestion.

-- 
Regards,
Boyuan Yang


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

Bug#961239: [Python-modules-team] Bug#961239: python-django-registration: Not compatible with Django 3.x

[Emmanuel Arias]

Hi,

This bugs seems to be fixed now on python3-django-registration 2.2-4

That is already on experimental.

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El jue., 21 de may. de 2020 a la(s) 18:15, Chris Lamb
(la...@debian.org) escribió:
>
> Source: python-django-registration
> Version: 2.2-3
> Severity: normal
> User: python-modules-t...@lists.alioth.debian.org
> Usertags: django-3.x
> Control: affects -1 mini-buildd
>
> Dear maintainer,
>
> The version of Django experimental is currently 3.0.6-1. I have built
> the 153 reverse-dependencies in unstable against this version and 114
> of these build & pass their testsuite successfully. For more
> information, see:
>
> http://bugs.debian.org/960890
>
> Please use the above bug report for queries or questions regarding
> Django 3.x that are not specific to this particular package in order
> to reduce duplicated work across all of the bugs.
>
> Whilst python-django-registration itself builds from source, it causes
> other packages (eg. mini-buildd) to FTBFS.
>
> Here is the FTBFS from mini-buildd:
>
>   […]
>
> File 
> "/home/lamby/temp/cdt.20200517004829.Xc0msV8pPb.ags.lamby-debian-experimental.python3-mini-buildd/mini-buildd-1.1.31/src/mini_buildd/django_settings.py",
>  line 168, in pseudo_configure
>   django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in 
> setup
>   apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 114, 
> in populate
>   app_config.import_models()
> File "/usr/lib/python3/dist-packages/django/apps/config.py", line 211, in 
> import_models
>   self.models_module = import_module(models_module_name)
> File "/usr/lib/python3.8/importlib/__init__.py", line 127, in 
> import_module
>   return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1014, in _gcd_import
> File "", line 991, in _find_and_load
> File "", line 975, in _find_and_load_unlocked
> File "", line 671, in _load_unlocked
> File "", line 783, in exec_module
> File "", line 219, in 
> _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/registration/models.py", line 23, in 
> 
>   from django.utils.encoding import python_2_unicode_compatible
>   ImportError: cannot import name 'python_2_unicode_compatible' from 
> 'django.utils.encoding' 
> (/usr/lib/python3/dist-packages/django/utils/encoding.py)
>
>   make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20200517004829.Xc0msV8pPb.ags.lamby-debian-experimental.python3-mini-buildd/mini-buildd-1.1.31'
>   make: *** [debian/rules:4: build] Error 2
>   dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
>
>   […]
>
> The full build log is attached.
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Bug#912846: grub2: stop depending on ttf-dejavu-core

[Steve McIntyre]

On Fri, May 22, 2020 at 03:59:55PM +0100, Colin Watson wrote:
>On Fri, May 22, 2020 at 04:30:16PM +0200, Fabian Greffrath wrote:
>> The ttf-dejavu-core package has been a transitional package for 7 years
>> (!) now and its removal is going to happen with the next package
>> upload, which will be anytime soon. Please adjust your package's build-
>> dependencies to fonts-dejavu-core and add the corresponding search path
>> to configure.ac. I have already prepared a patch for the latter.
>
>Hi - thanks for the patch.  I expect I can apply this, but could you
>please also send it upstream (grub-de...@gnu.org)?  I don't see a reason
>it couldn't be applied there, and it would make ongoing maintenance
>easier.

Ah, I've just taken the change and pushed to git...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer

Bug#961215: blueman-manager no longer starts because blueman-applet.service not found

[Michael Stone]

More specifically, refer to systemd.unit(5) and you'll find that 
/lib/systemd/user is not defined.

Bug#961215: blueman-manager no longer starts because blueman-applet.service not found

[Michael Stone]

On Sat, May 23, 2020 at 02:08:47AM +0200, Tomasz Nitecki wrote:

Hey,

This issue seems to be caused by changes made in #950520 [1].

I've described the problem in more detail in that bug report [1]. To cut
long story short, this bug (#961215) seems to be affecting non /usr
merged systems.


Yeah, the "fix" was obviously incorrect.

Bug#961308: add-shell.8: Minor reformatting of the manual's source

[Bjarni Ingi Gislason]

Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is add-shell.8

Test nr. 21:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes the "\/" part.

  Or

add the italic corrections.
[1] man-pages(7)

10:copies \fI/etc/shells\fR to \fI/etc/shells.tmp\fR, adds the given shells to
12:back to \fI/etc/shells\fR.

#

  Reformat some sentences.



  Use ".sp 1" instead of an empty line.



  Patch:

--- add-shell.8 2019-12-07 02:13:44.0 +
+++ add-shell.8.new 2020-05-23 00:21:13.0 +
@@ -7,10 +7,15 @@ add-shell \- add shells to the list of v
 .RI [ shellname ...]
 .SH DESCRIPTION
 .B add-shell
-copies \fI/etc/shells\fR to \fI/etc/shells.tmp\fR, adds the given shells to
-this file if they are not already present, and copies this temporary file
-back to \fI/etc/shells\fR.
-
+copies
+.I /etc/shells
+to
+.IR /etc/shells.tmp ,
+adds the given shells to this file
+if they are not already present,
+and copies this temporary file back to
+.IR /etc/shells .
+.sp 1
 The shells must be provided by their full pathnames.
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR shells (5)


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

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

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason

Bug#961309: installkernel.8: minor reformatting of the manual's source

[Bjarni Ingi Gislason]

Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is installkernel.8

chk_man: Next line: execute mandoc -T lint installkernel.8

mandoc: installkernel.8:16:19: STYLE: whitespace at end of input line
mandoc: installkernel.8:7:2: WARNING: skipping paragraph macro: PP after SH

###

  Reformat sentences.

#

  Patch:

--- installkernel.8 2019-12-07 02:13:44.0 +
+++ installkernel.8.new 2020-05-23 00:40:44.0 +
@@ -4,22 +4,26 @@ installkernel \- install a new kernel im
 .SH SYNOPSIS
 .BI "installkernel " "version zImage System.map [directory]"
 .SH DESCRIPTION
-.PP
 .B installkernel
 installs a new kernel image onto the system from the Linux source
-tree.  It is called by the Linux kernel makefiles when
+tree.
+It is called by the Linux kernel makefiles when
 .B make install
 is invoked there.
 .P
 The new kernel is installed into
 .IR {directory}/vmlinuz-{version} .
-If a symbolic link 
+If a symbolic link
 .I {directory}/vmlinuz
-already exists, it is refreshed by making a link from
+already exists,
+it is refreshed by making a link from
 .I {directory}/vmlinuz
-to the new kernel, and the previously installed kernel is available as
+to the new kernel,
+and the previously installed kernel is available as
 .IR {directory}/vmlinuz.old .
 .SH BUGS
-installkernel resides in /sbin only because the Linux kernel makefiles
-call it from there.  It should really be in /usr/sbin.  It isn't
-needed to boot a system.
+.B installkernel
+resides in /sbin only because the Linux kernel makefiles call it from
+there.
+It should really be in /usr/sbin.
+It isn't needed to boot a system.



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

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

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason

Bug#961146: systemd-logind sometimes ignores a systemd-inhibit lock

[Vincent Lefevre]

On 2020-05-22 23:53:58 +0200, Michael Biebl wrote:
> This is strange. Something is triggering the start of systemd-logind

What do you mean by "start of systemd-logind"?

On my machine, systemd-logind is started early at boot time and
never quits.

> (via D-Bus most likely). My educated guess is, that it is actually this
> process, which triggers the suspend, not logind itself.

But if the lid is not closed when I change the VT, the system
is not suspended.

And if I'm on a VT that is different from the one where
systemd-inhibit has been run and I close the lid, the system
is suspended.

> Remember when I initially said, that logind provides the mechanism and
> the policy is supposed to be proved by something else (usually the
> desktop environment).

A part of the policy is in logind, isn't it? I mean that
/etc/systemd/logind.conf has an option "HandleLidSwitch",
which I haven't modify, so that it is the default "suspend".
The suspend is just supposed to be blocked by an inhibitor,
which is also part of logind.

Note also that when I did the test, there was no desktop environment,
no X server, just 2 VTs involved. Which part of the system is in
charge of the VTs, then?

If I understand correctly, the suspend is done via the call of
manager_handle_action() in "login/logind-action.c". It would
be interesting to know the values of m and inhibit_key. But
according to what is logged, it seems that the call can only
be done via

manager_handle_action(manager, INHIBIT_HANDLE_LID_SWITCH, 
handle_action, manager->lid_switch_ignore_inhibited, is_edge);

in button_lid_switch_handle_action(); otherwise I would have
got another message before "Suspending...". So inhibit_key
would have the expected value. But I'm wondering about
manager; if it is not constant, this seems to be wrong
(as the inhibitors are associated with it).

Then, concerning button_lid_switch_handle_action(), there are
2 calls:

1. From button_recheck(), and it seems that this is what is called
   when I change the VT while the lid is already closed.

2. From button_dispatch(). The button_lid_switch_handle_action()
   call is preceded by "Lid closed.", which is what I get when
   I close the lid. And if I'm on a "wrong" VT, the system will
   be suspended.

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

Bug#961310: remove-shell.8: reformat the manual's source

[Bjarni Ingi Gislason]

Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is remove-shell.8

Test nr. 21:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes the "\/" part.

  Or

add the italic corrections.
[1] man-pages(7)

10:operates on the temporary files \fI/etc/shells.tmp\fR and
11:\fI/etc/shells.tmp2\fR to remove the given shells from the list of valid
12:login shells, and copy the result back to \fI/etc/shells\fR.

#

  Reformat sentences.



  Patch:

--- remove-shell.8  2019-12-07 02:13:44.0 +
+++ remove-shell.8.new  2020-05-23 01:02:47.0 +
@@ -2,13 +2,17 @@
 .SH NAME
 remove-shell \- remove shells from the list of valid login shells
 .SH SYNOPSIS
-.B  remove-shell
-.I  shellname
+.B remove-shell
+.I shellname
 .RI [ shellname ...]
 .SH DESCRIPTION
 .B remove-shell
-operates on the temporary files \fI/etc/shells.tmp\fR and
-\fI/etc/shells.tmp2\fR to remove the given shells from the list of valid
-login shells, and copy the result back to \fI/etc/shells\fR.
-.SH "SEE ALSO"
+operates on the temporary files
+.I /etc/shells.tmp
+and
+.I /etc/shells.tmp2
+to remove the given shells from the list of valid login shells,
+and copy the result back to
+.IR /etc/shells .
+.SH SEE ALSO
 .BR shells (5)



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

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

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason