Bug#931522: apt: does not provide a means to check whether updates are available from a script

[Svetlana Tkachenko]

Package: apt
Version: 1.8.2
Severity: wishlist

Dear Maintainer,

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

I wanted to check whether or not updates are available from my script written
in bash.

I found that aptitude can tell the number of packages which are available
for upgrade using

 aptitude search '~U' | wc -l

But for apt there is no reliable way to do the same, it outputs a warning that
its output is not meant to be parsed by scripts.

Please provide a commandline utility that tells '0' if no updates are 
available, and
'1' if some updates are available.

I would not mind having the same functionality available in C, but I found no
mention of it on the https://wiki.debian.org/Apt page.

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


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (no /etc/apt/preferences.d/* present) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/elastic-6.x.list present, but not submitted) --


-- (/etc/apt/sources.list.d/elastic-6.x.list~ present, but not submitted) --


-- (/etc/apt/sources.list.d/google-chrome.list present, but not submitted) --


-- (/etc/apt/sources.list.d/jitsi-stable.list present, but not submitted) --


-- (/etc/apt/sources.list.d/matrix-org.list present, but not submitted) --


-- (/etc/apt/sources.list.d/matrix-org.list~ present, but not submitted) --


-- (/etc/apt/sources.list.d/parsoid.list present, but not submitted) --


-- (/etc/apt/sources.list.d/parsoid.list~ present, but not submitted) --


-- (/etc/apt/sources.list.d/ring-nightly-main.list present, but not submitted) 
--


-- (/etc/apt/sources.list.d/ring-nightly-main.list~ present, but not submitted) 
--


-- (/etc/apt/sources.list.d/skype-stable.list present, but not submitted) --


-- (/etc/apt/sources.list.d/webmin.list present, but not submitted) --


-- (/etc/apt/sources.list.d/x2go.list present, but not submitted) --


-- (/etc/apt/sources.list.d/yarn.list present, but not submitted) --


-- (/etc/apt/sources.list.d/yarn.list~ present, but not submitted) --


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

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt depends on:
ii  adduser 3.118
ii  debian-archive-keyring  2019.1
ii  gpgv2.2.12-1
ii  libapt-pkg5.0   1.8.2
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libgnutls30 3.6.7-4
ii  libseccomp2 2.3.3-4
ii  libstdc++6  8.3.0-6

Versions of packages apt recommends:
ii  ca-certificates  20190110

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.8.11-7
ii  dpkg-dev1.19.7
ii  gnupg   2.2.12-1
ii  gnupg2  2.2.12-1
ii  powermgmt-base  1.34
ii  synaptic0.84.6

-- no debconf information

Bug#930666: Please document consensus on use of dh sequencer

[Russ Allbery]

Here is an updated patch incorporating Sean's wording changes as well as
other changes discussed elsewhere on the thread.  This reverts most of my
unrelated informative changes for clarity (they can be discussed or made
separately) and drops the sample dh makefile in favor of just referencing
the debhelper documentation.  It does keep some minor wording and
formatting fixes in the first two paragraphs.

This also removes the word "new" from the discussion of using another
packaging helper as an example, to make it a bit more obvious that the
cdbs maintainer using cdbs is one of the expected exceptions.

diff --git a/policy/ch-source.rst b/policy/ch-source.rst
index ee9270d..93beb4a 100644
--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -259,13 +259,33 @@ files, sockets or setuid or setgid files.. [#]_
 Main building script: ``debian/rules``
 --
 
-This file must be an executable makefile, and contains the
-package-specific recipes for compiling the package and building binary
-package(s) from the source.
-
-It must start with the line ``#!/usr/bin/make -f``, so that it can be
-invoked by saying its name rather than invoking ``make`` explicitly.
-That is, invoking either of ``make -f debian/rules args...`` or 
``./debian/rules args...`` must result in identical behavior.
+This file must be an executable makefile.  It contains the
+package-specific recipes for compiling the source (if required) and
+constructing one or more binary packages.
+
+``debian/rules`` must start with the line ``#!/usr/bin/make -f``, so that
+it can be invoked by saying its name rather than invoking ``make``
+explicitly.  That is, invoking either of ``make -f debian/rules args...``
+or ``./debian/rules args...`` must result in identical behavior.
+
+The recommended way to implement the build process of a Debian package, in
+the absence of a good reason to use a different approach, is the ``dh``
+tool.  This includes the contents of the ``debian/rules`` building script.
+``dh`` is the most common packaging helper tool in Debian.  Using it will
+usually save effort in complying with the rules in this document, because
+``dh`` will automatically implement many of them without requiring
+explicit instructions.
+
+There are sometimes good reasons to use a different approach.  For
+example, the standard tools for packaging software written in some
+languages may use another tool; some rarer packaging patterns, such as
+multiple builds of the same software with different options, are easier to
+express with other tools; and a packager working on a different packaging
+helper might want to use their tool.  The recommendation to use ``dh``
+does not always apply, and use of ``dh`` is not required.
+
+For more information about how to use ``dh``, see the documentation in the
+debhelper package, most notably the dh(1) manual page.
 
 The following targets are required and must be implemented by
 ``debian/rules``: ``clean``, ``binary``, ``binary-arch``,

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

Bug#929729: lintian: \n in filenames cause "md5sum: ...: No such file or directory"

[Felix Lechner]

Hi Chris,

On Sat, Jul 6, 2019 at 7:21 PM Chris Lamb  wrote:
>
> The following "fixes" it:
>
> diff --git a/collection/md5sums b/collection/md5sums
> index 970eb0656..e8006ab10 100755
> --- a/collection/md5sums
> +++ b/collection/md5sums
> @@ -53,7 +53,8 @@ sub collect {
>
>  foreach my $file ($info->sorted_index) {
>  next unless $file->is_file;
> +$file =~ s,\\n,\n,g;
>  printf {$opts{pipe_in}} "%s\0", $file;
>  }
>
>  close($opts{pipe_in});
> diff --git a/lib/Lintian/Path.pm b/lib/Lintian/Path.pm
> index 108a18ede..fb8048ed5 100644
> --- a/lib/Lintian/Path.pm
> +++ b/lib/Lintian/Path.pm
> @@ -643,6 +643,7 @@ sub open {
>  $layer //= '';
>  my $opener = sub {
>  use autodie qw(open);
> +$_[0] =~ s,\\n,\n,g;
>  open(my $fd, "<${layer}", $_[0]);
>  return $fd;
>  };
>
> … but this is clearly hacking around the problem and is likely
> incomplete. Storing the newline literally in the internal structure
> breaks other things that I can't immediately see/fix.

I agree. I rewrote the collections using IO::Async (coming once buster
is out) and can look at the newline issue over the next few days, if
you are okay with that.

Kind regards,
Felix

Bug#865792:

[Dave Steele]

> I like your patch, but it doesn't apply anymore (apologies it took so
> long to review) - would you please re-base it against the current
> master? thanks!

My apologies as well. I missed this message. I've rebased the
patch. I haven't looked closely at the code recently, but the merge
was clean enough, it runs cleanly with my mua (gnome-gmail)
and does not introduce new test failures.
From 6066867522181da0efdc0968e35af4a7df856dca Mon Sep 17 00:00:00 2001
From: David Steele 
Date: Sat, 6 Jul 2019 15:45:21 -0400
Subject: [PATCH] Add support for a custom mua command

The "mua" option allowed a custom mua command to be defined, but it
was only permitted for the list of 5 supported muas. This patch allows
an arbitrary mua command string to be defined.

The defined mua is set to default, and is added to the list of available
MUAs.

This also adds a 'mua-version' option, which specifies the mua
command-line argument for 'no action', which is used in utils.mua_exists(),
as an 'are you there?" check. This only applies to custom muas. The option
defaults to "--version".

As a side effect, the overloaded definition of 'mua' in utils, where
it could either be a string or a Mua object, depending on user options,
is eliminated.
---
 bin/reportbug|  14 +++---
 conf/reportbug.conf  |   9 +++-
 man/reportbug.1  |   9 +++-
 man/reportbug.conf.5 |  12 -
 reportbug/utils.py   | 111 ++-
 test/test_utils.py   |  29 ++-
 6 files changed, 96 insertions(+), 88 deletions(-)

diff --git a/bin/reportbug b/bin/reportbug
index 2baca08..766b590 100755
--- a/bin/reportbug
+++ b/bin/reportbug
@@ -800,7 +800,8 @@ def main():
 editor='', offline=False, verify=True, check_uid=True,
 testmode=False, attachments=[], keyid='', body=None,
 bodyfile=None, smtptls=False, smtpuser='', smtppasswd='',
-paranoid=False, mbox_reader_cmd=None)
+paranoid=False, mbox_reader_cmd=None,
+mua_version="--version")
 
 # Convention: consider `option.foo' names read-only; they always contain
 # the original value as determined by the cascade of command-line options
@@ -868,6 +869,8 @@ def main():
   dest='bugnumber', help='specify a bug number to look for')
 parser.add_option('--mua', dest='mua',
   help='send the report using the specified mail user agent')
+parser.add_option('--mua-version', dest='mua_version',
+  help='an mua option that results in no action (to verify mua is available)')
 parser.add_option('--mta', dest='mta', help='send the report using the '
 'specified mail transport agent')
 parser.add_option('--list-cc', action='append', dest='listcc',
@@ -1062,17 +1065,14 @@ def main():
 ewrite("The directory %s does not exist; exiting.\n" % options.draftpath)
 sys.exit(1)
 
-if options.mua and not options.template:
-if not utils.mua_is_supported(options.mua):
-ewrite("Specified mail user agent is not supported; exiting.\n")
-sys.exit(1)
+if isinstance(options.mua, str):
+options.mua = utils.mua_create(options.mua, options.mua_version)
 
+if options.mua and not options.template:
 if not utils.mua_exists(options.mua):
 ewrite("Selected mail user agent cannot be found; exiting.\n")
 sys.exit(1)
 
-options.mua = utils.mua_name(options.mua)
-
 # try to import the specified UI, but only if template
 # is not set (it's useful only in 'text' UI).
 if options.interface and not options.template:
diff --git a/conf/reportbug.conf b/conf/reportbug.conf
index f4f67b2..c69e89e 100644
--- a/conf/reportbug.conf
+++ b/conf/reportbug.conf
@@ -19,9 +19,16 @@ submit
 # mh
 # nmh
 
-# You can also use 'mua'; it takes an argument like that to --mua
+# You can also use 'mua'; it takes an argument like that to --mua.
+# '%s' is replaced with the path to the message file. It is appended if
+# not present.
 # mua 'mutt'
 
+# If you use the 'mua' option, you can also specify an mua option that
+# causes the mua to exit without action. This is used to verify that the
+# mua is present and available. It defaults to "--version".
+# mua_version '--version'
+
 # Additional headers to add:
 # header "X-Debbugs-CC: debian...@lists.debian.org"
 # header "X-Silly-Header: I haven't edited my /etc/reportbug.conf"
diff --git a/man/reportbug.1 b/man/reportbug.1
index 6bf2d2d..da0b656 100644
--- a/man/reportbug.1
+++ b/man/reportbug.1
@@ -294,7 +294,14 @@ Specify an alternate \fIMTA\fP, instead of \fB/usr/sbin/sendmail\fP
 .B \-\-mua=MUA
 Instead of spawning an editor to revise the bug report, use the
 specified \fIMUA\fP (mail user agent) to edit and send
-it. \fB--mutt\fP and \fB--nmh\fP options are processed.
+it. The string \fI%s\fP is replaced with 

Bug#931521: debian-handbook: apt section references testing/updates instead of testing-security

[Paul Wise]

Package: debian-handbook
Severity: normal

The debian-handbook apt section references testing/updates but with
bullseye that suite has been renamed to testing-security. Please update
the debian-handbook apt section.

./en-US/06_apt.xml:# Security updates
./en-US/06_apt.xml:deb http://security.debian.org/ stable/updates main contrib 
non-free
./en-US/06_apt.xml:deb http://security.debian.org/ testing/updates main contrib 
non-free
./en-US/06_apt.xml:deb-src http://security.debian.org/ stable/updates main 
contrib non-free
./en-US/06_apt.xml:deb-src http://security.debian.org/ testing/updates main 
contrib non-free
./en-US/06_apt.xml:

https://codesearch.debian.net/search?q=testing%2Fupdates+package%3Adebian-handbook

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#931520: harden-doc: before-compromise section references testing/updates instead of testing-security

[Paul Wise]

Package: harden-doc
Severity: normal

The harden-doc before-compromise section references testing/updates but
with bullseye that suite has been renamed to testing-security. Please
update the harden-doc before-compromise section.

./de-DE/old_de/before-compromise.sgml:
./de-DE/old_de/before-compromise.sgml:deb http://security.debian.org 
testing/updates main contrib non-free
./de-DE/old_de/before-compromise.sgml:deb-src  http://security.debian.org 
testing/updates main contrib non-free
./de-DE/old_de/before-compromise.sgml:
./de-DE/old_de/before-compromise.sgml:Binary file (standard input) matches
./it-IT/it_old/before-compromise.sgml:
./it-IT/it_old/before-compromise.sgml:deb http://security.debian.org 
testing/updates main contrib non-free
./it-IT/it_old/before-compromise.sgml:# Questa riga permette di scaricare anche 
pacchetti in formato sorgente
./it-IT/it_old/before-compromise.sgml:deb-src  http://security.debian.org 
testing/updates main contrib non-free
./it-IT/it_old/before-compromise.sgml:
./en-US/10_before-compromise.xml:
./en-US/10_before-compromise.xml:deb http://security.debian.org 
testing/updates main contrib non-free
./en-US/10_before-compromise.xml:# This line makes it possible to donwload 
source packages too
./en-US/10_before-compromise.xml:deb-src  http://security.debian.org 
testing/updates main contrib non-free
./en-US/10_before-compromise.xml:

https://codesearch.debian.net/search?q=testing%2Fupdates+package%3Aharden-doc

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#931519: wajig: upgradesecurity references testing/updates instead of testing-security

[Paul Wise]

Package: wajig
Severity: normal

The wajig upgradesecurity command references testing/updates but with
bullseye that suite has been renamed to testing-security. Please update
the wajig upgradesecurity command.

src/commands.py-def upgradesecurity(args):
src/commands.py-"""Do a security upgrade"""
src/commands.py-sources_list = tempfile.mkstemp(".security", "wajig.", 
"/tmp")[1]
src/commands.py-sources_file = open(sources_list, "w")
src/commands.py-# check dist
src/commands.py-sources_file.write("deb http://security.debian.org/ " +\
src/commands.py:   "testing/updates main contrib 
non-free\n")
src/commands.py-sources_file.close()

https://codesearch.debian.net/search?q=testing%2Fupdates+package%3Awajig

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#931518: madison-lite: example mirror config references testing/updates instead of testing-security

[Paul Wise]

Package: madison-lite
Severity: normal

The example mirror config references testing/updates but with bullseye
that suite has been renamed to testing-security. Please update the
example mirror config.

   suite stable/non-US dists/stable-non-US main contrib non-free
   suite stable/updates dists/stable-security main contrib non-free
   suite testing/updates dists/testing-security main contrib non-free
   # Uncomment the following lines if you are mirroring Ubuntu index files as
   # well.

https://codesearch.debian.net/search?q=testing%2Fupdates+package%3Amadison-lite

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#931517: apt-offline: manual page reference testing/updates instead of testing-security

[Paul Wise]

Package: apt-offline
Severity: normal

The manual page references testing/updates but with bullseye that suite
has been renamed to testing-security. Please update the manual page.

  deb http://security.debian.org testing/updates main contrib

  (Security Updates for Debian Testing)

https://manpages.debian.org/unstable/apt-offline/apt-offline.8.en.html#EXAMPLES

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#931516: tracker.debian.org: fixtures reference testing/updates instead of testing-security

[Paul Wise]

Package: tracker.debian.org
Severity: normal

The fixtures reference testing/updates but with bullseye that suite has
been renamed to testing-security. The fixtures in the code need to be
updated and then updated on the live server. I've no idea how to do the
latter, which is why I'm filing this issue.

$ git grep -C5 testing/updates
distro_tracker/core/fixtures/debian-repositories.xml-
distro_tracker/core/fixtures/debian-repositories.xml-Debian Testing Security
distro_tracker/core/fixtures/debian-repositories.xml-test-sec
distro_tracker/core/fixtures/debian-repositories.xml-http://security.debian.org
distro_tracker/core/fixtures/debian-repositories.xml-http://security.debian.org/
distro_tracker/core/fixtures/debian-repositories.xml:testing/updates
distro_tracker/core/fixtures/debian-repositories.xml-buster/updates
distro_tracker/core/fixtures/debian-repositories.xml-main contrib non-free
distro_tracker/core/fixtures/debian-repositories.xml-False
distro_tracker/core/fixtures/debian-repositories.xml-False
distro_tracker/core/fixtures/debian-repositories.xml-False

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#929729: lintian: \n in filenames cause "md5sum: ...: No such file or directory"

[Chris Lamb]

Chris Lamb wrote:

> However, I can reproduce with your previously attached .deb:
> 
> $ lintian ~/Downloads/newline_1_all.deb 2>&1 | head -n2
> md5sum: 'usr/share/newline/\n/etc/issue': No such file or directory
> command failed with error code 123 at 
> /home/lamby/git/debian/lintian/lintian/lib/Lintian/Command.pm line 344.

The following "fixes" it:

diff --git a/collection/md5sums b/collection/md5sums
index 970eb0656..e8006ab10 100755
--- a/collection/md5sums
+++ b/collection/md5sums
@@ -53,7 +53,8 @@ sub collect {
 
 foreach my $file ($info->sorted_index) {
 next unless $file->is_file;
+$file =~ s,\\n,\n,g;
 printf {$opts{pipe_in}} "%s\0", $file;
 }
 
 close($opts{pipe_in});
diff --git a/lib/Lintian/Path.pm b/lib/Lintian/Path.pm
index 108a18ede..fb8048ed5 100644
--- a/lib/Lintian/Path.pm
+++ b/lib/Lintian/Path.pm
@@ -643,6 +643,7 @@ sub open {
 $layer //= '';
 my $opener = sub {
 use autodie qw(open);
+$_[0] =~ s,\\n,\n,g;
 open(my $fd, "<${layer}", $_[0]);
 return $fd;
 };

… but this is clearly hacking around the problem and is likely
incomplete. Storing the newline literally in the internal structure
breaks other things that I can't immediately see/fix.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#929729: lintian: \n in filenames cause "md5sum: ...: No such file or directory"

[Chris Lamb]

Hi Jakub,

> Newlines in filenames make Lintian very unhappy:

[..]

Curiously, I can't seem to reproduce this when rebuilding the .deb
from your Git repository and dpkg 1.19.7:

$ dpkg-buildpackage --version | head -n1
Debian dpkg-buildpackage version 1.19.7.

$ dpkg-buildpackage -uc -us
[…]

$ lintian ../newline_1_all.deb
E: newline: no-copyright-file
E: newline: extended-description-is-empty

$ echo $?
1

> The source package for this deb is here:
> https://github.com/jwilk/newline.deb
> You will probably need very old dpkg (<< 1.18.1) to build it; see 
> #929727.

Looks like this was fixed in 1.19.7, ie. my current version.

However, I can reproduce with your previously attached .deb:

$ lintian ~/Downloads/newline_1_all.deb 2>&1 | head -n2
md5sum: 'usr/share/newline/\n/etc/issue': No such file or directory
command failed with error code 123 at 
/home/lamby/git/debian/lintian/lintian/lib/Lintian/Command.pm line 344.
 

Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#931515: zfs-linux: update depends for stretch

[Chris Zubrzycki]

Source: zfs-linux
Version: 0.8.1-1
Severity: important

Dear Maintainer,

I am building the experimental version on Stretch and there are a couple
of depends that need updating. The conflict on ols insserv is not
needed, nor is a newer version available on stretch. The circular
depends has been fixed upstream and is included in the debian 0.8
package.

The second is there is a depend on python3-distutils, but those files
are part of the python3 standard library package in stetch. This is also
not available as a backport, but can be easiy fixed with changing the
depends to python3-distutils | libpython3-stdlib (<3.6.4)

I know that Buster's release is today but there are still
systems that are using stretch for one reason or another, and these 2
changes do not affect building on buster or sid.

Thank you! I look forward to not needing to patching locally :-)



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

Kernel: Linux 4.19.0-0.bpo.5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#928822: raqm: clean after build deletes docs/html/* which is not regenerated

[أحمد المحمودي]

On Sun, May 12, 2019 at 02:25:41PM +0200, Andreas Beckmann wrote:
> On 2019-05-12 04:38, أحمد المحمودي wrote:
> > I checked the diff between upstream sources 0.5.0 (the one in testing) & 
> > 0.6.0, and I don't see any significant difference in Makefiles or docs/ 
> > to cause this. It might something in experimental's toolchain ?
> 
> This is probably reproducible in sid as well, I just run this test on
> experimental only.
---end quoted text---

I just tried to double-build version 0.5.0 on unstable, and it also 
failed, yet, if I understand correctly, it used to double-build before.
Hence, this must be due to some change in the toolchain.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#931216: less: Ctrl-C has no effect with -c (--clear-screen) and process substitution

[Vincent Lefevre]

On 2019-06-29 03:33:25 +0200, Vincent Lefevre wrote:
> I'm currently using the attached patch.

There's a small display problem with it: after typing [End] while the
command produces no output, then Ctrl-C, I get only the first line of
the file (after spurious "~" lines).

That said, the default behavior in this case can be regarded as buggy
too: one also gets the beginning of the file, while I would expect to
get either the current position or, better, the current end of the
file.

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

Bug#931514: thin-provisioning-tools: modules added by initramfs hooks aren't sufficient to activate a cached volume

[Jiri Palecek]

Package: thin-provisioning-tools
Version: 0.7.6-2.1
Severity: normal
File: /usr/share/initramfs-tools/hooks/thin-provisioning-tools

Dear Maintainer,

package thin-provisioning-tools conveniently provides initramfs hooks to
add files to initrd allowing to boot from a cached lv. More
specifically, this hook contains a line

manual_add_modules dm-cache

However, this is not sufficient to boot. It fails at boot time saying
there's no root filesystem -- vgchange -ay fails with message about a
failure to initialize caching policy.

The problem is that dm-cache needs to have a dm-cache-smq (or
dm-cache-something-else) with it. This module should be added to that
line in the hook.

Regards
Jiri Palecek


-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.18.0-3-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ 
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thin-provisioning-tools depends on:
ii  libaio1 0.3.112-3
ii  libc6   2.28-10
ii  libexpat1   2.2.6-2
ii  libgcc1 1:9.1.0-4
ii  libstdc++6  9.1.0-4

thin-provisioning-tools recommends no packages.

thin-provisioning-tools suggests no packages.

-- no debconf information

Bug#931511: Oops, maybe should act like in the first place

[積丹尼 Dan Jacobson]

Oops, maybe  should act like  in the first place,
https://stackoverflow.com/questions/3558119/are-non-void-self-closing-tags-valid-in-html5

Bug#931513: ITP: erlang-bbmustache -- Binary pattern match Based Mustache template engine for Erlang/OTP

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 

* Package name: erlang-bbmustache
  Version : 1.6.1
  Upstream Author : Hinagiku Soranoba 
* URL : https://github.com/soranoba/bbmustache
* License : Expat
  Programming Lang: Erlang
  Description : Binary pattern match Based Mustache template engine for 
Erlang/OTP

erlang-bbmustache is binary pattern match based mustache template engine for
Erlang/OTP. This does't use a regular expression of Erlang/OTP, and support
maps and associative arrays.

Bug#931511: Empty OL / LI rendering

[積丹尼 Dan Jacobson]

X-Debbugs-Cc: yama...@jpl.org
Package: w3m
Version: 0.5.3-37
Severity: minor

Shouldn't  be treated the same as ?
Lynx renders this better.

Title: OL TEST


  
  

  
A=1

  
B=1
  
  
B=2
  

  
  
A=2

  
B=3
  
  
B=4
  

  
  
A=3

  
B=5
  
  
B=6
  

  
  
A=4

  
  




A=5

  
  
  
  
  
A=6

  
  
A=7








  
  
A=8

  

  

Bug#931512: OL / LI rendering

[積丹尼 Dan Jacobson]

Package: lynx
Version: 2.9.0dev.1-1
Severity: minor

It seems lynx renders this better than other browsers, but still
   4. A=4
   5.
   A=5
should look the same.

Title: OL TEST


  
  

  
A=1

  
B=1
  
  
B=2
  

  
  
A=2

  
B=3
  
  
B=4
  

  
  
A=3

  
B=5
  
  
B=6
  

  
  
A=4

  
  




A=5

  
  
  
  
  
A=6

  
  
A=7








  
  
A=8

  

  

Bug#925134: grub-efi-amd64-signed: doesn't mount cryptodisk

[Felix Defrance]

Hi Mark and all,

I'm in the same situation. So what do we do ?

Thx

On Thu, 4 Jul 2019 18:34:01 +0200 Mark Caglienzi
 wrote:

> Hi all,
> is this bug relevant yet?
>
> I have a buster laptop (so no VM, but real hardware, and no fresh
> install) with encrypted disk, and I blocked the upgrade of grub since
> March because of the fear to not be able to boot it after the upgrade of
> grub.
>
> I am still with 2.02+dfsg1-12 because of this.
>
> The severity is critical (and if the bug is confirmed, I understand
> that's *critical*), but I don't understand if I can upgrade or not.
>
> I don't see "movement" in the thread since some months, and the bug just
> "lies here".
>
> Thanks in advance,
> Mark
>

-- 
Félix Defrance
PGP: 0x46A603D10F04DC57




signature.asc
Description: OpenPGP digital signature

Bug#931510: gdebi asks for root passwort for installing simple packages; seems an error.

[rich]

Package: gdebi
Version: 0.9.5.7+nmu1
Severity: important

Dear Maintainer,

*** 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: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-9-amd64 (SMP w/12 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdebi depends on:
ii  gdebi-core0.9.5.7+nmu1
ii  gir1.2-gtk-3.03.22.11-1
ii  gir1.2-vte-2.91   0.46.1-1
ii  gksu  2.0.2-9+b1
ii  gnome-icon-theme  3.12.0-2
ii  python3   3.5.3-1
ii  python3-gi3.22.0-2

Versions of packages gdebi recommends:
ii  libgtk2-perl  2:1.2499-1
ii  lintian   2.5.50.4
ii  shared-mime-info  1.8-1+deb9u1

gdebi suggests no packages.

-- no debconf information

Bug#931509: /usr/bin/git-deborig: git-deborig prints error message to stdout

[Ian Jackson]

Package: devscripts
Version: 2.19.5~bpo9+1
Severity: normal
File: /usr/bin/git-deborig

zealot:example> git-deborig --just-print | sed 's/^/stdout: /'; echo 
${PIPESTATUS[*]}
stdout: upstream/1.0
stdout: ../example_1.0.orig.tar.xz
stdout: git -c 'tar.tar.xz.command=xz -c' archive '--prefix=example-1.0/' -o 
../example_1.0.orig.tar.xz upstream/1.0
0 0
zealot:example> git-tag UPSTREAM-1.0 upstream/1.0
zealot:example> git-tag -d upstream/1.0
Deleted tag 'upstream/1.0' (was 5f40faf)
zealot:example> git-deborig --just-print | sed 's/^/stdout: /'; echo 
${PIPESTATUS[*]}
stdout: couldn't find any of the following tags: 1.0, v1.0, upstream/1.0
stdout: tell me a tag or branch head to make an orig.tar from: git deborig 
--just-print COMMITTISH
1 0
zealot:example>

Expected behaviour would be to print the error message to stderr and
nothing to stdout.

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBSIGN_KEYID=0x48B50D39
GREP_EXCUSES_AUTOPKGTESTS=1

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

Kernel: Linux 4.19.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages devscripts depends on:
ii  dpkg-dev  1.18.25
ii  fakeroot  1.21-3.1
ii  file  1:5.30-1+deb9u2
ii  gnupg 2.1.18-8~deb9u4
ii  gnupg22.1.18-8~deb9u4
ii  gpgv  2.1.18-8~deb9u4
ii  libc6 2.24-11+deb9u4
ii  libfile-homedir-perl  1.00-1
ii  libfile-which-perl1.21-1
ii  libipc-run-perl   0.94-1+deb9u1
ii  libmoo-perl   2.002005-1
ii  libwww-perl   6.15-1
ii  patchutils0.3.4-2
ii  perl  5.24.1-3+deb9u5
ii  python3   3.5.3-1
ii  sensible-utils0.0.9+deb9u1
ii  wdiff 1.2.2-2

Versions of packages devscripts recommends:
ii  apt 1.4.9
ii  at  3.1.20-3
ii  curl7.52.1-5+deb9u9
ii  dctrl-tools 2.24-2+b1
ii  debian-keyring  2017.05.28
ii  dput0.12.1
ii  dupload 2.8.4
pn  equivs  
pn  libdistro-info-perl 
ii  libdpkg-perl1.18.25
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.047-1
pn  libgitlab-api-v4-perl   
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.20-1
ii  libstring-shellquote-perl   1.03-1.2
ii  libtry-tiny-perl0.28-1
ii  liburi-perl 1.71-1
pn  licensecheck
ii  lintian 2.12.0~bpo9+1
ii  man-db  2.7.6.1-2
ii  patch   2.7.5-1+deb9u1
ii  python3-apt 1.4.0~beta3
ii  python3-debian  0.1.30
pn  python3-magic   
ii  python3-requests2.12.4-1
ii  python3-unidiff 0.5.2-1
ii  python3-xdg 0.25-4
ii  strace  4.15-2
ii  unzip   6.0-21+deb9u1
ii  wget1.18-5+deb9u3
ii  xz-utils5.2.2-1.2+b1

Versions of packages devscripts suggests:
pn  adequate   
ii  autopkgtest4.4
pn  bls-standalone 
ii  build-essential12.3
pn  check-all-the-things   
pn  cvs-buildpackage   
ii  debhelper  12.1.1~bpo9+1
ii  devscripts-el  36.3+nmu1
pn  diffoscope 
pn  disorderfs 
pn  dose-extra 
pn  duck   
ii  faketime   0.9.6-7+b1
ii  gnuplot5.0.5+dfsg1-6+deb9u1
pn  how-can-i-help 
ii  libauthen-sasl-perl2.1600-1
ii  libdbd-pg-perl 3.5.3-1+b2
ii  libfile-desktopentry-perl  0.22-1
pn  libnet-smtps-perl  
pn  libterm-size-perl  
ii  libtimedate-perl   2.3000-2
ii  libyaml-syck-perl  1.29-1+b2
ii  mailutils [mailx]  1:3.1.1-1
pn  mozilla-devscripts 
pn  mutt   
ii  openssh-client [ssh-client]1:7.4p1-10+deb9u6
pn  piuparts   
ii  postgresql-client  9.6+181+deb9u2
ii  postgresql-client-9.6 

Bug#931508: gnome-shell: cannot lock the session nor hibernate

[Axel Stammler]

Package: gnome-shell
Version: 3.30.2-9
Severity: normal

Dear Maintainer,

The menu does not show the button to lock the screen, all shortcuts for that 
are ignored,
too.

Hibernation is likewise impossible.

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evolution-data-server3.30.5-1
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.30.0-7
ii  gir1.2-freedesktop   1.58.3-2
ii  gir1.2-gcr-3 3.28.1-1
ii  gir1.2-gdesktopenums-3.0 3.28.1-1
ii  gir1.2-gdm-1.0   3.30.2-3
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomebluetooth-1.03.28.2-3
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gweather-3.0  3.28.2-2
ii  gir1.2-ibus-1.0  1.5.19-4
ii  gir1.2-mutter-3  3.30.2-7
ii  gir1.2-nm-1.01.14.6-2
ii  gir1.2-nma-1.0   1.8.20-1.1
ii  gir1.2-pango-1.0 1.42.4-6
ii  gir1.2-polkit-1.00.105-25
ii  gir1.2-rsvg-2.0  2.44.10-2.1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.10-1
ii  gjs  1.54.3-1
ii  gnome-backgrounds3.30.0-1
ii  gnome-settings-daemon3.30.2-3
ii  gnome-shell-common   3.30.2-9
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libcanberra0 0.30-7
ii  libcroco30.6.12-3
ii  libecal-1.2-19   3.30.5-1
ii  libedataserver-1.2-233.30.5-1
ii  libgcr-base-3-1  3.28.1-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgirepository-1.0-11.58.3-2
ii  libgjs0g 1.54.3-1
ii  libglib2.0-0 2.58.3-2
ii  libglib2.0-bin   2.58.3-2
ii  libgstreamer1.0-01.14.4-1
ii  libgtk-3-0   3.24.5-1
ii  libical3 3.0.4-3
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-3-03.30.2-7
ii  libnm0   1.14.6-2
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpolkit-agent-1-0  0.105-25
ii  libpolkit-gobject-1-00.105-25
ii  libpulse-mainloop-glib0  12.2-4
ii  libpulse012.2-4
ii  libsecret-1-00.18.7-1
ii  libstartup-notification0 0.12-6
ii  libsystemd0  241-5
ii  libx11-6 2:1.6.7-1
ii  libxfixes3   1:5.0.3-1
ii  mutter   3.30.2-7
ii  python3  3.7.3-1

Versions of packages gnome-shell recommends:
ii  bolt  0.7-2
ii  chrome-gnome-shell10.1-5
ii  gdm3  3.30.2-3
ii  gkbd-capplet  3.26.1-1
ii  gnome-control-center  1:3.30.3-1
ii  gnome-user-docs   3.30.2-1
ii  iio-sensor-proxy  2.4-2
ii  switcheroo-control1.2-2
ii  unzip 6.0-23

Versions of packages gnome-shell suggests:
pn  gir1.2-telepathyglib-0.12   
pn  gir1.2-telepathylogger-0.2  

-- no debconf information

Bug#931507: kernel-wedge: HDA sound board detection takes 60s in d-i

[Samuel Thibault]

Package: kernel-wedge
Version: 2.99
Severity: serious
Tags: a11y
Justification: prevents blind people from using d-i

We have had (late, unfortunately) reports that HDA-based audio hardware
does not get detected. Actually it does, but only after 60s of delay,
which is way too long for the espeakup script.

What happens is in snd_hdac_i915_init, which tries to load the i915
module, which is not included in d-i, and waits for 60s to get it loaded
and bound to it. The delay was "only" 10s in 4.19.12, but apparently
increased to 60s in 4.19.37.

So I guess we should just ship the i915 module in d-i, either manually
in the existing sound-modules*-di package, or in a separate package and
make sound-modules*-di depend on it. It's a big 3M module, but it would
be shipped only in the gtk images anyway.

It'd definitely be so much useful to have this change uploaded in time
for 10.1.

Samuel

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), 
(500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.1.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kernel-wedge depends on:
ii  debhelper  12.1.1
ii  make   4.2.1-1.2

kernel-wedge recommends no packages.

kernel-wedge suggests no packages.

-- 
Samuel
* c is away : cuisine; bouffe
 oh, moi je fais plutôt cuisine & bouffe en fait :)
 oui c'est vrai, certains font cuisine && bouffe (juste au cas où... ;-))
 ( cuisine && bouffe ) || restau
 voire ((cuisine && bouffe) || restau) & apéritif
 -+- #ens-mim -+-

Bug#931506: linux-base: "are are" in man 1 perf

[Ivan Kharpalev]

Package: linux-base
Version: 4.6
Severity: minor
Tags: patch

Errors in man 1 perf. See patch in the end of the report.

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

Kernel: Linux 4.9.0-7-amd64 (SMP w/8 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 /bin/dash
Init: unable to detect

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0]  1.5.72

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
  linux-base/removing-title:
  linux-base/removing-running-kernel: true

--- a/man/perf.1
+++ b/man/perf.1
@@ -6,8 +6,8 @@ perf \- performance analysis tools for Linux
 \fBperf\fR [\fB\-\-version\fR] [\fB\-\-help\fR] \fICOMMAND\fR [\fIARGS\fR]
 .SH DESCRIPTION
 .LP
-Performance counters for Linux are are a new kernel\-based subsystem
-that provide a framework for all things performance analysis.  It
+Performance counters for Linux are a new kernel\-based subsystem
+that provide a framework for performance analysis.  It
 covers hardware level (CPU/PMU, Performance Monitoring Unit) features
 and software features (software counters, tracepoints) as well.
 .LP

Bug#931505: bind9: Problem with apparmor profile, so Bind9 refused to start

[JP P]

Package: bind9
Version: 1:9.11.5.P4+dfsg-5.1
Severity: normal

Dear Maintainer,

I upgraded one system to Buster and Bind9 refused to start blocked by
apparmor :
audit: type=1400 audit(1562447210.397:15): apparmor="DENIED"
operation="open" profile="/usr/sbin/named"
name="/home/jpprr/DEVSUBV/dns_slave/named.conf" pid=4481
comm="isc-worker" requested_mask="r" denied_mask="r" fsuid=120
ouid=120
All files are in a user's directory to be managed through a versionnning
system.
I will correct the profile to authorize the directory for reading.

Regards

JP P

*** 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: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages bind9 depends on:
ii  adduser3.118
ii  bind9utils 1:9.11.5.P4+dfsg-5.1
ii  debconf [debconf-2.0]  1.5.71
ii  dns-root-data  2019031302
ii  libbind9-161   1:9.11.5.P4+dfsg-5.1
ii  libc6  2.28-10
ii  libcap21:2.25-2
ii  libcom-err21.44.5-1
ii  libdns1104 1:9.11.5.P4+dfsg-5.1
ii  libfstrm0  0.4.0-1
ii  libgeoip1  1.6.12-1
ii  libgssapi-krb5-2   1.17-3
ii  libisc1100 1:9.11.5.P4+dfsg-5.1
ii  libisccc1611:9.11.5.P4+dfsg-5.1
ii  libisccfg163   1:9.11.5.P4+dfsg-5.1
ii  libjson-c3 0.12.1+ds-2
ii  libk5crypto3   1.17-3
ii  libkrb5-3  1.17-3
ii  liblmdb0   0.9.22-1
ii  liblwres1611:9.11.5.P4+dfsg-5.1
ii  libprotobuf-c1 1.3.1-1+b1
ii  libssl1.1  1.1.1c-1
ii  libxml22.9.4+dfsg1-7+b3
ii  lsb-base   10.2019051400
ii  net-tools  1.60+git20180626.aebd88e-1
ii  netbase5.6

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind9-doc   
ii  dnsutils1:9.11.5.P4+dfsg-5.1
pn  resolvconf  
pn  ufw 

-- Configuration Files:
/etc/bind/db.127 changed:
;
; BIND reverse data file for local loopback interface
;
$TTL604800
@   IN  SOA localhost. root.localhost. (
  1 ; Serial
 604800 ; Refresh
  86400 ; Retry
2419200 ; Expire
 604800 )   ; Negative Cache TTL
;
@   IN  NS  localhost.
1.0.0   IN  PTR localhost.
localhost INCNAME   k400l.

/etc/bind/named.conf changed:
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind/README.Debian for information on the 
// structure of BIND configuration files in Debian for BIND versions 8.2.1 
// and later, *BEFORE* you customize this configuration file.
//
key DHCP_UPDATER {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret "EHILtJCarFnCtpxuzxnmwQ==";
};
key DHCP_UPDATEB {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret "EHILtJCarFnCtpxuzxnmwQ==";
};
include "/etc/bind/named.conf.local";
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
// add entries for other zones below here
zone "jpp.fr" {
file "/etc/bind/db.jpp.fr";
include "/etc/bind/named.master";
};
zone "2.168.192.in-addr.arpa" {
file "/etc/bind/db.192.168.2";
include "/etc/bind/named.master";
};
zone "jpp1.fr" {
file "/etc/bind/db.jpp1.fr";
include "/etc/bind/named.master";
};
zone "1.168.192.in-addr.arpa" {
file "/etc/bind/db.192.168.1";
include "/etc/bind/named.master";
};
zone "jpp2.fr" {
file "/etc/bind/db.jpp2.fr";
include "/etc/bind/named.master";
 };
zone "3.168.192.in-addr.arpa" {
file "/etc/bind/db.192.168.3";
include "/etc/bind/named.master";
};
zone "jpp6.fr" {
file "/etc/bind/db.jpp6.fr";
include "/etc/bind/named.master";
};
zone "2.0.0.0.0.0.c.f.ip6.arpa" {
file "/etc/bind/db.jpp6.fr.rev";
include 

Bug#930897: xautolock silently fails if locker exits non-zero

[Owen Heisler]

In the third paragraph on the previous message, it should be

"the zero exit code indicates the command was received"

Bug#931504: pcmanfm: Cannot see remote network shares. probably samba problem

[Trevor Harris]

Package: pcmanfm
Version: 1.3.1-1+rpt7
Severity: normal

Dear Maintainer,

*** 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:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Architecture: armv7l

Kernel: Linux 4.19.50-v7l+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pcmanfm depends on:
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10+rpi1
ii  libcairo21.16.0-4+rpt1
ii  libfm-gtk4   1.3.1-1+rpt5
ii  libfm4   1.3.1-1+rpt5
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2
ii  libgtk2.0-0  2.24.32-3+rpt1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpangoft2-1.0-01.42.4-6
ii  libx11-6 2:1.6.7-1
ii  shared-mime-info 1.10-1

Versions of packages pcmanfm recommends:
ii  gnome-icon-theme3.12.0-3
ii  gvfs-backends   1.38.1-5
ii  gvfs-fuse   1.38.1-5
ii  lxde-icon-theme 0.5.1-2
ii  lxpolkit [polkit-1-auth-agent]  0.5.4-1+rpt1
ii  rpd-icons   0.18

pcmanfm suggests no packages.

cannot display remote network shares with the network option. I understand
that this is due to samba. The version of Samba in Buster is 2.4.9.5 but I
understand that this is fixed in 2.4.10. See

https://unix.stackexchange.com/questions/453944/samba-network-discovery-fails-through-file-managers-but-works-with-smbtree

Thanks


-- no debconf information


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Bug#931503: protobuf: FTBFS on x32 due to versioned glibc symbols in ruby gem native extension

[Laurence Parry]

Package: protobuf
Version: 3.5.2-1
Tags: ftbfs upstream
Usertags: x32
Severity: important
Justification: Fails to build from source (previously built
successfully for x32)
X-Debbugs-CC: debian-am...@lists.debian.org

Dear maintainer,

ruby-google-protobuf does not link under the x32 ABI, and seems to
block other components of protobuf:
https://buildd.debian.org/status/package.php?p=protobuf=sid

protobuf assumes that glibc 2.2.5 memcpy symbols will be available #if
defined(__x86-64__); however, x32 also defines this, but was not
supported prior to 2.16.

The current build log displays the issue:
https://buildd.debian.org/status/fetch.php?pkg=protobuf=x32=3.6.1.3-2=145463=0

gcc -shared -o protobuf_c.so defs.o encode_decode.o map.o message.o
protobuf.o repeated_field.o storage.o upb.o wrap_memcpy.o -L.
-L/usr/lib/x86_64-linux-gnux32 -L. -Wl,-z,relro -Wl,-z,now
-fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-wrap,memcpy
-Wl,-z,relro -Wl,-z,now -Wl,--compress-debug-sections=zlib
-lruby-2.5  -lpthread -lgmp -ldl -lcrypt -lm   -lc
/usr/bin/ld: protobuf_c.so: no symbol version section for versioned
symbol `memcpy@GLIBC_2.2.5'
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:260: protobuf_c.so] Error 1
make[2]: Leaving directory
'/<>/debian/ruby-google-protobuf/usr/lib/x86_64-linux-gnux32/rubygems-integration/2.5.0/gems/google-protobuf-3.6.1/ext/google/protobuf_c'
ERROR:  Error installing /tmp/d20190417-571-uvvnmj/google-protobuf-3.6.1.gem:
ERROR: Failed to build gem native extension.

I believe this may be due to a fix to preserve compatibility for
CentOS 6 and Debian 7:
https://github.com/protocolbuffers/protobuf/issues/2783
https://github.com/protocolbuffers/protobuf/pull/2831/commits/a7e05be8ec2e0873efa2e69c23ec8d3f67d52e2d

This makes sense as the issue started after moving to 3.5 (which also
broke support for alpha - both are stuck at 3.0.0-9.2, for different
reasons).

The Ruby protobuf extension demands memcpy symbols from glibc 2.2.5
(from 2002), the first to support x86-64/Linux. From the relevant
source file:
https://chromium.googlesource.com/external/github.com/google/protobuf/+/HEAD/ruby/ext/google/protobuf_c/wrap_memcpy.c

// On x86-64 Linux with glibc, we link against the 2.2.5 version of memcpy so
// that we avoid depending on the 2.14 version of the symbol. This way,
// distributions that are using pre-2.14 versions of glibc can successfully use
// the gem we distribute
(https://github.com/protocolbuffers/protobuf/issues/2783).
//
// This wrapper is enabled by passing the linker flags -Wl,-wrap,memcpy in
// extconf.rb.

x32 was first supported from glibc 2.16 (from 2012):
https://sourceware.org/glibc/wiki/x32
I'm guessing it doesn't have those symbols (and can't be affected by
the problem with pre-2.14).

--

Per https://wiki.debian.org/X32Port#Detecting_X32
One solution seems to be to change the file upstream:
#if defined(__x86_64__) && defined(__GNU_LIBRARY__)
to:
#if defined(__x86_64__) && !defined(__ILP32__) && defined(__GNU_LIBRARY__)

because x32 has __ILP32__ while regular x86-64 has __LP64__ instead.

Alternatively it might be suitable to patch extconf.rb on x32, or drop
the wrapper entirely on Debian (Centos 6 is still in maintenance
support through November 30th, 2020).

--

This bug may also apply to gRPC which has a substantially similar
wrapper, enabled via patch:
https://github.com/grpc/grpc/blob/debian/sid/src/core/lib/support/wrap_memcpy.c
https://sources.debian.org/patches/grpc/1.16.1-1/add-wrap-memcpy-flags.diff/

Any failure is currently hidden as it is BD-Uninstallable due to a
lack of a recent protobuf-compiler:
https://buildd.debian.org/status/package.php?p=grpc=sid
but it may be revealed if this is fixed without a corresponding change.

gRPC also appears to lacks this define restricting the above fix to glibc:
https://chromium.googlesource.com/external/github.com/google/protobuf/+/ea5ef14aa01701f686c52de4e724f66101c8e163%5E%21/

Best regards,
-- 
Laurence "GreenReaper" Parry
https://www.greenreaper.co.uk/

Bug#931502: console-setup: Console-setup configuration during d-i in lowmem mode makes graphical characters bogus

[Samuel Thibault]

Package: console-setup
Version: 1.191
Severity: normal

Hello,

While trying to install Debian 10.0 with less than 400M, and thus
in lowmem mode, the output gets bogus right after console-setup
configuration inside the target system, as can be seen in the attached
snapshot.

This does not happen in non-lowmem mode, because we use bterm in that
case.

This can be reproduced most easily both on amd64 and i386 by passing
lowmem=1 as a kernel parameter, and proceeding with the install up to
and including the base system installation. console-setup gets installed
and configured just after kernel installation, that's when the output
gets bogus as attached.

Samuel

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), 
(1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.1.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages console-setup depends on:
ii  console-setup-linux 1.191
ii  debconf 1.5.71
ii  keyboard-configuration  1.191
ii  xkb-data2.26-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.28-10
ii  lsb-base  10.2019051400

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.71
ii  liblocale-gettext-perl  1.07-3+b4

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.56+nmu1
ii  initscripts 2.93-8
ii  kbd 2.0.4-4
ii  keyboard-configuration  1.191

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:3.30.3-1
ii  kbd   2.0.4-4
ii  systemd   241-5

-- debconf information:
  console-setup/framebuffer_only:
* keyboard-configuration/store_defaults_in_debconf_db: true
* console-setup/codesetcode: Lat15
  console-setup/guess_font:
  console-setup/use_system_font:
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/unsupported_config_options: true
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/other:
* keyboard-configuration/layout:
* console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/model: PC genèric de 105 tecles (intl.)
* keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/variantcode: oss,
* keyboard-configuration/unsupported_options: true
* console-setup/fontface47: TerminusBold
* keyboard-configuration/unsupported_layout: true
* keyboard-configuration/variant: Français - Français (variante obsolète)
* keyboard-configuration/layoutcode: fr,brai
* keyboard-configuration/modelcode: pc105
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
* keyboard-configuration/compose: Left Logo key
* console-setup/fontsize: 16x32
* keyboard-configuration/altgr: The default for the keyboard layout
* console-setup/fontsize-text47: 16x32 (uniquement tampon vidéo (« framebuffer 
»))
* console-setup/fontsize-fb47: 16x32 (uniquement tampon vidéo (« framebuffer »))
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/switch: No temporary switch
* console-setup/charmap47: UTF-8
* keyboard-configuration/ctrl_alt_bksp: true
* keyboard-configuration/optionscode: 
compose:lwin,nbsp:level3n,grp:shift_caps_toggle,grp_led:scroll,terminate:ctrl_alt_bksp,kpdl:kposs

-- 
Samuel
Tu as lu les docs. Tu es devenu un informaticien. Que tu le veuilles
ou non. Lire la doc, c'est le Premier et Unique Commandement de
l'informaticien.
-+- TP in: Guide du Linuxien pervers - "L'évangile selon St Thomas"

Bug#924445: I finally figured this one out

[Joshua Hudson]

pulseaudio exits by default when there's nothing connected to it.
However I have this line in ~/.pulse/default.pa

load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1

So if the next program trying to use it is one of the programs  trying
to use it over TCP, it doesn't work.

Bug#931501: DDPO: please say "UTC" after time data

[Adam Borowski]

Package: qa.debian.org
Severity: wishlist

Hi!
Some places that list datetimes show explicit timezones (like the generation
timestamp at the bottom), some don't (eg. deferred-until).  This is
confusing as a good majority of web pages these days use web browser's time
zone (obviously uncool with Tor...).  Thus, it would be nice if the "UTC" or
whatever other time zone is used would be explicitly mentioned in all cases.


Meow!
-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-rc7-00033-g2bf15134b691 (SMP w/64 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#612993: Converted debian-faq to DocBook

[Joost van Baal-Ilić]

Hi Tobias,

On Sat, Jul 06, 2019 at 06:13:11PM +0200, Dr. Tobias Quathamer wrote:
> I've worked during the last week on the conversion of debian-faq to
> DocBook. Now it's going rather smoothly, so I've pushed my commits to
> the git repository.
> 
> I've taken great care to convert most of the translated strings
> automatically to the new DocBook markup syntax, so that e.g. the French
> translation with ~960 strings has only about 25 untranslated or fuzzy
> strings. So it should be a rather small amount of work for the translators.
> 
> So far, the generation of .txt, .html, and .pdf works quite well. The
> next steps would be to convert debian/rules, so that the package
> building works again.

Awesome!  Thanks a lot for this work.

I hope I can have a look at it soonish.

(But first I hope I can finally tackle doc-debian issue
https://bugs.debian.org/922929  )

Bye,

Joost

Bug#931467: reportbug-gtk: Crashes after setting package name

[Nis Martensen]

On 05 Jul 2019 David  wrote:

-- System Information:
Distributor ID: PureOS
Description:PureOS
Release:8
Codename:   green


Thank you for the report, but this is probably specific to PureOS or a 
system administration error. The problem does not exist in Debian. 
Please see

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

Bug#656369: smokeping: slave mode has fewer dependencies

[Gabriel Filion]

Hello Simon,

On Wed, 18 Jan 2012 19:21:26 + Simon Wilcox
 wrote:
> Smokeping has the ability to run in a master/slave configuration.
> 
> In the slave configuration data is sent to a master server and a local
> apache installation is not required.
> 
> We want to install smokeping on devices that should not have apache
> installed, to use as slaves to a master server but we can't do this with
> the current dependency chain.
> 
> May I request that the smokeping package is divided into two, with a
> data collector package separate from a web-UI package. Or possibly that
> you consider a separate smokeping-slave package that would leave the
> current smokeping package untouched.
> 
> I know that we could roll our own package or install outside of the
> package system altogether so perhaps you may wish to re-grade this
> ticket to a wishlist request rather than a bug but I've filed it as such
> since we can't use the package for our use case at this time.
> 
> Thank you for the time and effort you give to the Debian project and for
> taking the time to consider this bug.

This bug report has been open forever.

I've taken a look at this and I believe that the state of the package
has changed in a way that could permit installing smokeping without apache:

apache2 is currently a "Recommends" for smokeping (it has been at least
since the version that was in jessie).

so you can install the package using this to avoid apache:

apt install --no-install-recommends smokeping

Note that in that case you might need to manually install some
additional packages if you need them: dnsutils, echoping and
libsocket6-perl are also recommends and won't be installed because of
the option.

I believe that using this option, you can create an install of smokeping
for using it with the "slave" mode without having apache on the same
machine.

Cheers!



signature.asc
Description: OpenPGP digital signature

Bug#931491: iputils: FTBFS in sid (missing dependency on setcap)

[Noah Meyerhans]

There's a bug in upstream's build system that causes the build to fail
if setcap is unavailable, even if its usage is disabled via the
NO_SETCAP_OR_SUID configuration. I'll work with upstream to get this
fixed.

Bug#931500: linux-image-4.19.0-5-amd64: kernel deadlock with autofs

[Anton Ivanov]

Package: src:linux
Version: 4.19.37-5
Severity: normal
File: linux-image-4.19.0-5-amd64

Dear Maintainer,

An attempt to mount an nfs mount via autofs when it is being unmounted 
sometimes results in a deadlock.

This is  easier to reproduce with nfsv3. It is more difficult but still 
possible with nfs4.

I have been unable to reproduce it on any CPU with lower number of 
threads/cores than Ryzen 5 1600 (6/12). It is reliably reproducible on any 6 
core 12 thread or higher Ryzen.

It is not easy to trigger - usually takes up to 1-2 days of regular 
mount/unmounts at the normal autofs 5 min unmount interval to do that. It may 
sometimes happen in less than 30 minutes. In my case the culprit were system 
stats scripts executed every 5 minutes from cron. Raising the autofs timeout to 
600s eliminated the deadlocks.

The deadlock is usually hard and it is impossible to use Alt-SysRQ. The only 
time I managed to obtain a trace it was as follows:
Jun 28 12:56:01 sleer kernel: [101497.077162] rcu: INFO: rcu_sched 
self-detected stall on CPU
Jun 28 12:56:01 sleer kernel: [101497.077172] rcu: #0118-...!: (5250 ticks this 
GP) idle=6fa/1/0x4002 softirq=514095/514095 fqs=175 
Jun 28 12:56:01 sleer kernel: [101497.077174] rcu: #011 (t=5250 jiffies 
g=2596081 q=15)
Jun 28 12:56:01 sleer kernel: [101497.077179] rcu: rcu_sched kthread starved 
for 4900 jiffies! g2596081 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=7
Jun 28 12:56:01 sleer kernel: [101497.077180] rcu: RCU grace-period kthread 
stack dump:
Jun 28 12:56:01 sleer kernel: [101497.077182] rcu_sched   R  running task   
 010  2 0x8000
Jun 28 12:56:01 sleer kernel: [101497.077185] Call Trace:
Jun 28 12:56:01 sleer kernel: [101497.077192]  ? __schedule+0x2a2/0x870
Jun 28 12:56:01 sleer kernel: [101497.077194]  schedule+0x28/0x80
Jun 28 12:56:01 sleer kernel: [101497.077196]  schedule_timeout+0x16b/0x390
Jun 28 12:56:01 sleer kernel: [101497.077200]  ? 
__next_timer_interrupt+0xc0/0xc0
Jun 28 12:56:01 sleer kernel: [101497.077203]  rcu_gp_kthread+0x40d/0x850
Jun 28 12:56:01 sleer kernel: [101497.077205]  ? call_rcu_sched+0x20/0x20
Jun 28 12:56:01 sleer kernel: [101497.077207]  kthread+0x112/0x130
Jun 28 12:56:01 sleer kernel: [101497.077209]  ? kthread_bind+0x30/0x30
Jun 28 12:56:01 sleer kernel: [101497.077211]  ret_from_fork+0x1f/0x40
Jun 28 12:56:01 sleer kernel: [101497.077213] NMI backtrace for cpu 8
Jun 28 12:56:01 sleer kernel: [101497.077215] CPU: 8 PID: 21552 Comm: 
localStorage DB Tainted: GE 4.19.0-5-amd64 #1 Debian 4.19.37-5
Jun 28 12:56:01 sleer kernel: [101497.077216] Hardware name: System 
manufacturer System Product Name/PRIME B450M-A, BIOS 0604 12/07/2018
Jun 28 12:56:01 sleer kernel: [101497.077217] Call Trace:
Jun 28 12:56:01 sleer kernel: [101497.077218]  
Jun 28 12:56:01 sleer kernel: [101497.077220]  dump_stack+0x5c/0x80
Jun 28 12:56:01 sleer kernel: [101497.077223]  
nmi_cpu_backtrace.cold.4+0x13/0x50
Jun 28 12:56:01 sleer kernel: [101497.077225]  ? 
lapic_can_unplug_cpu.cold.29+0x3b/0x3b
Jun 28 12:56:01 sleer kernel: [101497.077227]  
nmi_trigger_cpumask_backtrace+0xf9/0xfb
Jun 28 12:56:01 sleer kernel: [101497.077229]  rcu_dump_cpu_stacks+0x9b/0xcb
Jun 28 12:56:01 sleer kernel: [101497.077231]  
rcu_check_callbacks.cold.80+0x1db/0x338
Jun 28 12:56:01 sleer kernel: [101497.077234]  ? tick_sched_do_timer+0x60/0x60
Jun 28 12:56:01 sleer kernel: [101497.077236]  update_process_times+0x28/0x60
Jun 28 12:56:01 sleer kernel: [101497.077238]  tick_sched_handle+0x22/0x60
Jun 28 12:56:01 sleer kernel: [101497.077240]  tick_sched_timer+0x37/0x70
Jun 28 12:56:01 sleer kernel: [101497.077241]  __hrtimer_run_queues+0x100/0x280
Jun 28 12:56:01 sleer kernel: [101497.077243]  hrtimer_interrupt+0x100/0x220
Jun 28 12:56:01 sleer kernel: [101497.077245]  ? handle_irq_event+0x47/0x5c
Jun 28 12:56:01 sleer kernel: [101497.077247]  
smp_apic_timer_interrupt+0x6a/0x140
Jun 28 12:56:01 sleer kernel: [101497.077248]  apic_timer_interrupt+0xf/0x20
Jun 28 12:56:01 sleer kernel: [101497.077249]  
Jun 28 12:56:01 sleer kernel: [101497.077251] RIP: 
0010:smp_call_function_many+0x1f8/0x250
Jun 28 12:56:01 sleer kernel: [101497.077253] Code: c7 e8 0c c4 5e 00 3b 05 1a 
86 01 01 0f 83 8c fe ff ff 48 63 d0 48 8b 0b 48 03 0c d5 00 b7 8c a4 8b 51 18 
83 e2 01 74 0a f3 90 <8b> 51 18 83 e2 01 75 f6 eb c8 48 c7 c2 60 e3 b2 a4 4c 89 
fe 89 df
Jun 28 12:56:01 sleer kernel: [101497.077254] RSP: 0018:b93dc9cd3bb8 
EFLAGS: 0202 ORIG_RAX: ff13
Jun 28 12:56:01 sleer kernel: [101497.077256] RAX:  RBX: 
9309fec22c00 RCX: 9309fea27000
Jun 28 12:56:01 sleer kernel: [101497.077256] RDX: 0001 RSI: 
 RDI: 9309fec22c08
Jun 28 12:56:01 sleer kernel: [101497.077257] RBP: 9309fec22c08 R08: 
0004 R09: 9309fec22c48
Jun 28 12:56:01 sleer kernel: [101497.077258] R10: 9309fec22c08 R11: 
0008 R12: a3a6ca90
Jun 28 12:56:01 sleer kernel: 

Bug#931499: Is sourcing /usr/share/initramfs-tools/scripts/functions forbidden in hook scripts?

[Guenther Brunthaler]

I just noticed that the line in Debian 9

"$quiet" = "y"

was explicitly changed into

"${quiet?}" = "y"

in Debian 10, so I wonder whether this was really a regression by
mistake, or rather a deliberate way to break all existing hook scripts
which source /usr/share/initramfs-tools/scripts/functions because they
must not do this for some reason.

If this should be the case, that fact should be mentioned in the man
page of initramfs-tools.

The man page currently does not explicitly suggest sourcing this shell
snippet, but it does not advise against it either.

And it worked fine in Debian 9.

Now many of my hook scripts are broken because of this regression in
Debian 10.

I fixed the problem for now with the following kludge:

---
$ cat /etc/initramfs-tools/conf.d/quiet-fix-tifgasefdz3c41npwum8msjt7
# Without this file, every initramfs hook which uses one of the log_*
# functions will fail with the message "quiet: parameter not set".
#
# This effect was introduced by upgrading from Debian "stretch" to "buster".

: ${quiet:=n}
export quiet
---

but of course this is not a clean solution.

Bug#931499: initramfs hook scripts which use log_* functions die

[Guenther Brunthaler]

Package: initramfs-tools-core
Version: 0.133

initramfs hook scripts which source

. /usr/share/initramfs-tools/scripts/functions

and then later use one of the log_*() functions such as

log_begin_msg "Installing terminfo entries: $tinfos"

will make the hook script fail with the message "quiet: parameter not
set", which will make the invoking "update-initramfs" also fail as a
consequence.

The reason is simple: The script contains a parameter expansion

$ grep -F 'quiet?' /usr/share/initramfs-tools/scripts/functions
if [ "${quiet?}" = "y" ]; then return; fi

which will fail if "$quiet" is not defined at all at this place. This
can easily be tested as follows:

$ (set +e; unset quiet; echo "${quiet?}"; echo "RC: $?")
-bash: quiet: parameter not set

Note that this failure was so severe that the whole subshell terminated
even though "set -e" has been disabled!

The easiest way to make to problem go away would be to set the variable
if it is not defined, because this works:

$ (set +e; : ${quiet:=}; echo "${quiet?}"; echo "RC: $?")
RC: 0

It would suffice to add a line

: ${quiet:=}

or maybe better

: ${quiet:=n}

somewhere outside of any function to the file
/usr/share/initramfs-tools/scripts/functions.

I am using Debian 10 on branch "buster"
on branch ascii
with kernel
Linux 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64
GNU/Linux

Bug#929515: smokeping: CSS and js files not found

[Gabriel Filion]

Hi Keith,

I'm terribly sorry for the time it took to respond to your bug report.

On Sat, 25 May 2019 10:09:27 +0100 Keith Edmunds 
wrote:
> Package: smokeping
> Version: 2.7.3-2
> Severity: important
> 
> System was upgraded from Stretch to Buster, with smokeping working on Stretch.
> 
> After the upgrade, it's evident from the display that there is a CSS problem.
> 
> Chrome devtools reports:
> 
> GET http://ws.midnighthax.com/cgi-bin/css/smokeping-screen.css 
> net::ERR_ABORTED 404 (Not Found)

When I install smokeping on a vanilla buster VM I see that the CSS files
come from this kind of URL (e.g. there's no "cgi-bin" in the path):

http://192.168.121.33/smokeping/css/smokeping-screen.css

If you use "View source" on the web page, can you paste the lines around
the top where the page points to smokeping-screen.css and
smokeping-print.css

On my end, it looks like this:






Lastly, this might be "too late" since your bug report was sent so long
ago.. but maybe running a force refresh on the page (ctrl-f5 on firefox)
could clear up the lack of css files.

I've just tested installing smokeping on a vanilla stretch VM, then
upgrading to buster, and (other than systemd being unhappy about the
already running instance) I can see the CSS just fine..

maybe one possibility is if there was a manual change to the file
/etc/apache2/conf-available/smokeping.conf



signature.asc
Description: OpenPGP digital signature

Bug#867299: upstream

[Chris Zubrzycki]

This is/was an upstream bug it should likely be closed. It’s also from code 
many years out of date now.

Bug#581960: tex4ht: wrong charset in htlatex output

[Hilmar Preuße]

On 06.07.19 18:55, Janusz S. Bień wrote:
> On Wed, Jul 03 2019 at 23:50 +02, Hilmar Preuße wrote:

Hi Janusz,

>> Just to make we sure we understand you correctly: currently the char
>> encoding is set to iso-8859-1
> 
> That's wrong, you cannot encode Polish in iso-8859-1.
> 
>> and the web page looks OK.
> 
> That's true - I don't know why.
> 
> The validator at https://www.freeformatter.com/html-validator.html finds
> 6 issue, two of them relating to encoding.
> 
Thanks for the response! I've learned in the past days that the tex4ht
people are quite responsive, hence I'll nevertheless will submit a bug
@upstream.

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



signature.asc
Description: OpenPGP digital signature

Bug#931498: gmpc-plugins: Some plugins are disabled

[Martin Tharby Jones]

Package: gmpc-plugins
Version: 11.8.16-3
Severity: important

Dear Maintainer,

I want to use the gmpc-albumview plugin but it is not built as part of the
stable release. I checked at https://gmpclient.org/plugins and it is still
listed.

I downloaded the source from the link
(http://download.sarine.nl/Programs/gmpc/0.20.0/gmpc-albumview-0.20.0.tar.gz)
on https://gmpc.fandom.com/wiki/GMPC_PLUGIN_ALBUMVIEW.

This fails to build due to following error:

[...]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gmpc
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/freetype2 -I/usr/include/libmpd-1.0/
-DPIXMAP_DATA_DIR=\"/usr/share/gmpc-albumview/icons\" -g -O2 -MT
albumviewplugin_la-plugin.lo -MD -MP -MF .deps/albumviewplugin_la-plugin.Tpo -c
plugin.c  -fPIC -DPIC -o .libs/albumviewplugin_la-plugin.o
In file included from /usr/include/string.h:630:0,
 from /usr/include/glib-2.0/glib/gi18n-lib.h:24,
 from plugin.c:3:
/usr/include/libmpd-1.0/libmpd/libmpd-internal.h:210:10: error: expected
identifier or ‘(’ before ‘__extension__’
 char *   strndup (const char *s, size_t n);
  ^
plugin.c: In function ‘load_list_itterate’:
[...]

This unhelpful message is caused by the redeclaration of strndup(), it is also
declared in string.h.

The declaration in libmpd-internal.h is protected by #ifndef but HAVE_STRNDUP
is not defined in config.h

#ifndef HAVE_STRNDUP
char *  strndup (const char *s, size_t
n);
#endif

Adding #define HAVE_STRNDUP to config.h gives me a useable build but I don't
know enough about autotools so I had to make the addition manually. The problem
seems to be associated with older versions of the C library not providing
strndup().

Several other plugins were disabled as a workaround to fix Debian Bug report
#807735 so a proper fix for this should work for them also. A workaround like
this should have reduced the severity of this bug not closed it!

Yours

Martin



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

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gmpc-plugins depends on:
ii  gmpc 11.8.16-10
ii  libatk1.0-0  2.22.0-1
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavahi-glib1   0.6.32-2
ii  libc62.24-11+deb9u4
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  libdbus-glib-1-2 0.108-2
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libmpd1  0.20.0-2~deb9u1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2

gmpc-plugins recommends no packages.

gmpc-plugins suggests no packages.

-- no debconf information

Bug#926457: RFP: supysonic -- multimedia streaming server

[Louis-Philippe Véronneau]

My packaging efforts can be found here:

https://salsa.debian.org/python-team/applications/supysonic

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



signature.asc
Description: OpenPGP digital signature

Bug#925444: smokeping: --pid-dir doesn't worj as expected

[Gabriel Filion]

Hi again Bertrand,

On Tue, 2 Apr 2019 10:46:38 -0400 Gabriel Filion 
wrote:
> On 2019-03-26 3:26 p.m., BERTRAND Joël wrote:
> >> Did you recently upgrade smokeping? if so what version were you
> >> using before? (maybe check your dpkg logs for signs of upgrade of
> >> the smokeping package)
> > Yes, I have.
> > 
> > -> 2019-03-17 03:26:38 upgrade smokeping:all 2.7.2-3 2.7.3-2

If this bug is still affecting your install, could you paste the
contents of the file /lib/systemd/system/smokeping.service ?

also, which version of systemd are you running?

Normally there should be a line like the following that tells systemd to
create the /run/somkeping directory:

RuntimeDirectory=smokeping



signature.asc
Description: OpenPGP digital signature

Bug#581960: tex4ht: wrong charset in htlatex output

[Janusz S. Bień]

On Wed, Jul 03 2019 at 23:50 +02, Hilmar Preuße wrote:
> On 17.05.10 13:54, jsb...@mimuw.edu.pl wrote:
>
> Hi Janusz,
>
>> Please have a look at the attached example.
>> 
>> This is a regression, it work correctly several years ago...
>> 
> Just to make we sure we understand you correctly: currently the char
> encoding is set to iso-8859-1

That's wrong, you cannot encode Polish in iso-8859-1.

> and the web page looks OK.

That's true - I don't know why.

The validator at https://www.freeformatter.com/html-validator.html finds
6 issue, two of them relating to encoding.

> Is therefore the bug solved?

No, but I can live with it.

Best regards

Janusz 
-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#498552: texlive-base: texlive-pictures should not contain curve

[Hilmar Preuße]

On 11.09.08 05:00, Géraud Meyer wrote:

Hi Norbert,

> The debian package texlive-pictures contains a latex package named curve
> that helps make a curriculum vitae. It should not be in texlive-pictures
> but probably in the same package that contains the latex resume package
> (currently it is texlive-latex-extra).
> 
We speak about

/usr/share/texlive/texmf-dist/tex/latex/curve/curve.cls

and

/usr/share/doc/texlive-doc/latex/curve/

Could yo coordinate the move w/ upstream? Thanks!

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



signature.asc
Description: OpenPGP digital signature

Bug#931491: iputils: FTBFS in sid (missing dependency on setcap)

[Noah Meyerhans]

On Sat, Jul 06, 2019 at 01:31:08PM +0200, Gianfranco Costamagna wrote:
> 
> Hello, looks like the new version does search for *bin/setcap tool, and fails 
> to build if missing.
> 

Hm. Seems libcap2-bin is present in my pbuilder environment as a result
of being a dependency of packages like iproute2.

I think the better thing to do would be to disable execution of the
build-aux/setcap-setuid.sh script at build time, since we don't need the
capabilities assigned during the build.

Thanks for this report...

Bug#612993: Converted debian-faq to DocBook

[Dr. Tobias Quathamer]

control: tag -1 pending

Hi Joost,

I've worked during the last week on the conversion of debian-faq to
DocBook. Now it's going rather smoothly, so I've pushed my commits to
the git repository.

I've taken great care to convert most of the translated strings
automatically to the new DocBook markup syntax, so that e.g. the French
translation with ~960 strings has only about 25 untranslated or fuzzy
strings. So it should be a rather small amount of work for the translators.

So far, the generation of .txt, .html, and .pdf works quite well. The
next steps would be to convert debian/rules, so that the package
building works again.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#931497: Font-lock-mode off by default in Debian

[積丹尼 Dan Jacobson]

Package: emacs-gtk
Version: 1:26.1+1-3.2
File: /usr/bin/emacs-gtk
X-Debbugs-Cc: Eli Zaretskii , 36...@debbugs.gnu.org

> "EZ" == Eli Zaretskii  writes:
>> $ emacs -q -Q index.html etc.
>> All just black and white.
>> Have to do M-x font-lock-mode
>> so see any colors, here with Debian's 26.1.

EZ> Then I suggest that you take this up with the downstream Emacs package
EZ> maintainers for Debian, because Emacs built from sources here doesn't
EZ> have that problem.

OK. Sending report to Debian.

Bug#931496: redmine: Missing in Debian Buster

[Charlemagne Lasse]

Source: redmine
Severity: normal
Tags: buster

I've just updated my server to Debian buster and then noticed that my
redmine was gone. Problem is that it was removed from Debian testing
https://tracker.debian.org/news/1027921/redmine-removed-from-testing/
(when Buster was still equal to testing)

Please provide an buster-backports upload to allow other admins to
upgrade their servers without ending up without redmine or with a
broken redmine installation.

Bug#867590: networkd removes statically set default route when RA expires

[jkhsjdhjs]

Hello,

I experienced the same or a very similar bug nearly two years ago on a 
gentoo server. I reported it to systemd upstream, it is tracked here: 
https://github.com/systemd/systemd/issues/7354


Today, yuwata created a pull request which attempts to fix the problem: 
https://github.com/systemd/systemd/pull/12971


Unfortunately I don't have said gentoo server anymore, thus I can't test 
the PR either.


Best Regards,

Leon

Bug#931238: hot armor: please drop "Version: " header

[Clint Adams]

On Fri, Jun 28, 2019 at 05:38:36PM -0400, Daniel Kahn Gillmor wrote:
> "hot armor" currently adds a comment line to its enarmored content:
> 
> Version: hot 0.21.3
> 
> Best practices these days omits indicators of what particular OpenPGP
> implementation is in use.   Please do not emit it by default!

Should rfc4880bis deprecate this?

Bug#931495: vdr: sort order in OSD recordings list is broken

[Timo Weingärtner]

Package: vdr
Version: 2.2.0-6+b1
Severity: normal

Dear Maintainer,

after upgrading the machine to buster (holding vdr (and xine) packages back to
stretch's versions) the sort order in the recordings menu is broken.

Sort order now is (leading % seems to be ignored as it should be):
B… < 1… < C… < 8… < A… < D… < E… < F…
Sc… < Sa…

Upgrading the vdr packages to buster did not help.

Re-generating locales (dpkg-reconfigure locales) did not help.

I can't reproduce this with ls, using all the available locales (via
LC_ALL).

vdr-plugin-live is not affected.


Regards
Timo

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

Kernel: Linux 4.19.0-5-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vdr depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10
ii  libcap21:2.25-2
ii  libfontconfig1 2.13.1-2
ii  libfreetype6   2.9.1-3
ii  libgcc11:8.3.0-6
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libstdc++6 8.3.0-6
ii  libsystemd0241-5
ii  lsb-base   10.2019051400

Versions of packages vdr recommends:
ii  lirc 0.10.1-5.2
pn  ttf-bitstream-vera | fonts-freefont-ttf  

Versions of packages vdr suggests:
pn  vdr-plugin-dvbsddevice  

-- Configuration Files:
/etc/vdr/command-hooks/reccmds.custom.conf changed:
Werbung markieren: /usr/bin/markad -b nice

/etc/vdr/conf.d/00-vdr.conf changed:
[vdr]
--video=/var/lib/video
--config=/var/lib/vdr
--lib=/usr/lib/vdr/plugins
--record=/usr/lib/vdr/vdr-recordingaction
--epgfile=/var/cache/vdr/epg.data
--user=vdr
--grab=/tmp
--port=6419
--watchdog=60
--lirc

/etc/vdr/diseqc.conf changed:
1 2 3 4:
S19.2E  11700 V  9750  [E0 10 38 F0]
S19.2E  9 V 10600  [E0 10 38 F1]
S19.2E  11700 H  9750  [E0 10 38 F2]
S19.2E  9 H 10600  [E0 10 38 F3]
S13.0E  11700 V  9750  [E0 10 38 F4]
S13.0E  9 V 10600  [E0 10 38 F5]
S13.0E  11700 H  9750  [E0 10 38 F6]
S13.0E  9 H 10600  [E0 10 38 F7]

/etc/vdr/keymacros.conf changed:
Red Timers
Green   Recordings
Yellow  Schedule
BlueInfo
User0   @osdteletext
User1   @femon
User2   @xineliboutput


-- debconf information:
* vdr/select_dvb_card: Satellite
* vdr/create_video_dir: false

Bug#926193: still not working with the actual kernel in buster

[Klaumi Klingsporn]

Hi folks,

as I read on bits.debian.org that buster will be released
today I think it's time to tell you that this bug is still
NOT gone with the actual kernel in buster
(linux-image 4.19.37-5).

If buster is released with this kernel it will still not
work on my laptop (Acer Travelmate B117), which is sad
because I actually don't want to use the outdated
linux-image-4.19.0-2 forever.

The bug had got the tag 'fixed upstream' which might be
true, but it's still NOT fixed in the Debian-package in
buster. Why is it so hard to apply a revert-drm-i915 patch
to the kernel as other distributions did. As attachment you
find the patch that the fedora-folks applied to their
kernel in march 19.

Klaumi

---
Klaus-Michael Klingsporn
phone: +49-30-9445363
mail: klaumi...@gmx.de
web: www.klaumikli.de

From e90ac616e4b1d49ec9092086b0e10108df12157d Mon Sep 17 00:00:00 2001
From: Fedora Kernel Team 
Date: Tue, 5 Mar 2019 12:56:35 -0600
Subject: [PATCH] Revert drm/i915/fbdev: Actually configure untiled displays

---
 drivers/gpu/drm/i915/intel_fbdev.c | 12 +---
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_fbdev.c b/drivers/gpu/drm/i915/intel_fbdev.c
index e0c02a9..9e2e998 100644
--- a/drivers/gpu/drm/i915/intel_fbdev.c
+++ b/drivers/gpu/drm/i915/intel_fbdev.c
@@ -336,8 +336,8 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
 bool *enabled, int width, int height)
 {
 	struct drm_i915_private *dev_priv = to_i915(fb_helper->dev);
+	unsigned long conn_configured, conn_seq, mask;
 	unsigned int count = min(fb_helper->connector_count, BITS_PER_LONG);
-	unsigned long conn_configured, conn_seq;
 	int i, j;
 	bool *save_enabled;
 	bool fallback = true, ret = true;
@@ -355,9 +355,10 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
 		drm_modeset_backoff();

 	memcpy(save_enabled, enabled, count);
-	conn_seq = GENMASK(count - 1, 0);
+	mask = GENMASK(count - 1, 0);
 	conn_configured = 0;
 retry:
+	conn_seq = conn_configured;
 	for (i = 0; i < count; i++) {
 		struct drm_fb_helper_connector *fb_conn;
 		struct drm_connector *connector;
@@ -370,8 +371,7 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
 		if (conn_configured & BIT(i))
 			continue;

-		/* First pass, only consider tiled connectors */
-		if (conn_seq == GENMASK(count - 1, 0) && !connector->has_tile)
+		if (conn_seq == 0 && !connector->has_tile)
 			continue;

 		if (connector->status == connector_status_connected)
@@ -475,10 +475,8 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
 		conn_configured |= BIT(i);
 	}

-	if (conn_configured != conn_seq) { /* repeat until no more are found */
-		conn_seq = conn_configured;
+	if ((conn_configured & mask) != mask && conn_configured != conn_seq)
 		goto retry;
-	}

 	/*
 	 * If the BIOS didn't enable everything it could, fall back to have the
--
2.20.1

Bug#931494: ITP: r-bioc-lpsymphony -- Symphony integer linear programming solver in GNU R

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-bioc-lpsymphony -- Symphony integer linear programming solver 
in GNU R
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-bioc-lpsymphony
  Version : 1.12.0
  Upstream Author : Vladislav Kim,
* URL : https://bioconductor.org/packages/lpsymphony/
* License : EPL-1.0
  Programming Lang: GNU R
  Description : Symphony integer linear programming solver in GNU R
 This package was derived from Rsymphony_0.1-17 from CRAN. These packages
 provide an R interface to SYMPHONY, an open-source linear programming
 solver written in C++. The main difference between this package and
 Rsymphony is that it includes the solver source code (SYMPHONY version
 5.6), while Rsymphony expects to find header and library files on the
 users' system. Thus the intention of lpsymphony is to provide an easy to
 install interface to SYMPHONY.

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

Bug#839404: NMU ongoing in deferred queue

[Gianfranco Costamagna]

Hello, I uploaded the following debdiff in deferred/5, fixing the two above 
bugs.

thanks

G.
diff -Nru lshw-02.18.85/debian/changelog lshw-02.18.85/debian/changelog
--- lshw-02.18.85/debian/changelog  2019-07-03 11:15:12.0 +0200
+++ lshw-02.18.85/debian/changelog  2019-07-06 14:36:53.0 +0200
@@ -1,3 +1,21 @@
+lshw (02.18.85-0.3) unstable; urgency=medium
+
+  [ Gianfranco Costamagna ]
+  * Upload to unstable
+  * Refresh FTCBFS patch to make it apply on the new release.
+
+  [ Helmut Grohne ]
+  * Non-maintainer upload.
+  * Fix FTCBFS: Closes: #839404.
++ Pass triplet-prefixed CC and CXX to make.
++ cross.patch: Make pkg-config substitutable.
++ Use triplet-prefixed pkg-config.
+
+  [ Steve Langasek ]
+  * fix -version wrongly passed during build procedure (Closes: #849697)
+
+ -- Gianfranco Costamagna   Sat, 06 Jul 2019 
14:36:53 +0200
+
 lshw (02.18.85-0.2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru lshw-02.18.85/debian/patches/cross.patch 
lshw-02.18.85/debian/patches/cross.patch
--- lshw-02.18.85/debian/patches/cross.patch1970-01-01 01:00:00.0 
+0100
+++ lshw-02.18.85/debian/patches/cross.patch2019-07-06 14:36:53.0 
+0200
@@ -0,0 +1,66 @@
+From: Helmut Grohne 
+Subject: make pkg-config subtitutable
+
+--- lshw-02.18.85.orig/src/Makefile
 lshw-02.18.85/src/Makefile
+@@ -21,14 +21,15 @@ export SQLITE
+ export ZLIB
+ 
+ CXX?=$(CROSS_COMPILE)c++
++PKG_CONFIG ?= pkg-config
+ INCLUDES=-I./core/
+ DEFINES=-DPREFIX=\"$(PREFIX)\" -DSBINDIR=\"$(SBINDIR)\" 
-DMANDIR=\"$(MANDIR)\" -DDATADIR=\"$(DATADIR)\" -DVERSION=\"$(VERSION)\"
+ CXXFLAGS=$(CXX_DEB_FLAGS) $(INCLUDES) $(DEFINES)
+ ifeq ($(SQLITE), 1)
+-  CXXFLAGS+= -DSQLITE $(shell pkg-config --cflags sqlite3)
++  CXXFLAGS+= -DSQLITE $(shell $(PKG_CONFIG) --cflags sqlite3)
+ endif
+ ifeq ($(ZLIB), 1)
+-  CXXFLAGS+= -DZLIB $(shell pkg-config --cflags zlib)
++  CXXFLAGS+= -DZLIB $(shell $(PKG_CONFIG) --cflags zlib)
+ endif
+ LDFLAGS+=-L./core/
+ ifneq ($(shell $(LD) --help 2| grep -- --as-needed), )
+@@ -37,10 +38,10 @@ endif
+ LDSTATIC=-static
+ LIBS+=-llshw -lresolv
+ ifeq ($(SQLITE), 1)
+-  LIBS+= $(shell pkg-config --libs sqlite3)
++  LIBS+= $(shell $(PKG_CONFIG) --libs sqlite3)
+ endif
+ ifeq ($(ZLIB), 1)
+-  LIBS+= $(shell pkg-config --libs zlib)
++  LIBS+= $(shell $(PKG_CONFIG) --libs zlib)
+ endif
+ 
+ export CXXFLAGS
+--- lshw-02.18.85.orig/src/gui/Makefile
 lshw-02.18.85/src/gui/Makefile
+@@ -1,22 +1,23 @@
+ PACKAGENAME?=lshw
+ 
+ CXX?=$(CROSS_COMPILE)c++
++PKG_CONFIG ?= pkg-config
+ CC?=$(CROSS_COMPILE)cc
+ STRIP?=strip
+ OBJCOPY?=objcopy
+ 
+ DEFINES=-DPREFIX=\"$(PREFIX)\" -DSBINDIR=\"$(SBINDIR)\" 
-DMANDIR=\"$(MANDIR)\" -DDATADIR=\"$(DATADIR)\"
+-GTKINCLUDES=$(shell pkg-config gtk+-2.0 --cflags)
++GTKINCLUDES=$(shell $(PKG_CONFIG) gtk+-2.0 --cflags)
+ INCLUDES=-I../core $(GTKINCLUDES)
+ CXXFLAGS=$(CXX_DEB_FLAGS) $(INCLUDES) $(DEFINES)
+ ifeq ($(SQLITE), 1)
+-  CXXFLAGS+= -DSQLITE $(shell pkg-config --cflags sqlite3)
++  CXXFLAGS+= -DSQLITE $(shell $(PKG_CONFIG) --cflags sqlite3)
+ endif
+ CFLAGS=$(CXXFLAGS) $(DEFINES)
+-GTKLIBS=$(shell pkg-config gtk+-2.0 gmodule-2.0 --libs)
++GTKLIBS=$(shell $(PKG_CONFIG) gtk+-2.0 gmodule-2.0 --libs)
+ LIBS+=-L../core -llshw -lresolv $(GTKLIBS)
+ ifeq ($(SQLITE), 1)
+-  LIBS+= $(shell pkg-config --libs sqlite3)
++  LIBS+= $(shell $(PKG_CONFIG) --libs sqlite3)
+ endif
+ LDFLAGS=
+ ifneq ($(shell $(LD) --help 2| grep -- --as-needed), )
diff -Nru lshw-02.18.85/debian/patches/series 
lshw-02.18.85/debian/patches/series
--- lshw-02.18.85/debian/patches/series 2019-07-03 11:15:12.0 +0200
+++ lshw-02.18.85/debian/patches/series 2019-07-06 14:36:53.0 +0200
@@ -8,3 +8,4 @@
 privacy.patch
 spelling-error.patch
 add-missing-ethlink-standards.patch
+cross.patch
diff -Nru lshw-02.18.85/debian/rules lshw-02.18.85/debian/rules
--- lshw-02.18.85/debian/rules  2019-07-03 11:15:12.0 +0200
+++ lshw-02.18.85/debian/rules  2019-07-06 14:36:53.0 +0200
@@ -3,6 +3,15 @@
 UPSTREAM_GIT = https://github.com/lyonel/lshw
 -include /usr/share/openstack-pkg-tools/pkgos.make
 
+include /usr/share/dpkg/architecture.mk
+ifeq ($(origin CC),default)
+CC = $(DEB_HOST_GNU_TYPE)-gcc
+endif
+ifeq ($(origin CXX),default)
+CXX = $(DEB_HOST_GNU_TYPE)-g++
+endif
+export PKG_CONFIG = $(DEB_HOST_GNU_TYPE)-pkg-config
+
 CXX_DEB_FLAGS = -Wall -g
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -35,8 +44,8 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE) -C $(srcdir) core
-   $(MAKE) -C $(srcdir) gui
+   $(MAKE) -C $(srcdir) VERSION=$(uver) core CC="$(CC)" CXX="$(CXX)"
+   $(MAKE) -C $(srcdir) gui CC="$(CC)" CXX="$(CXX)"
#/usr/bin/docbook-to-man debian/lshw.sgml > lshw.1
touch build-stamp
 
@@ -57,8 +66,8 @@
dh_installdirs
 
# Add here commands to install the package into debian/lshw.
-   $(MAKE) -C $(srcdir) 

Bug#931493: [plasma-desktop] remove rotating effect of notification icon in system tray when copying

[Jiri Kanicky]

Package: plasma-desktop
Version: 4:5.13.5-1+b1
Severity: normal

--- Please enter the report below this line. ---

Can someone please completely remove the rotating effect of notification
icon in system tray? Every time I copy something it takes 30% of the CPU
and my fans start spinning as crazy. I don't even understand how feature
like that can even pass testing.

Thank you.



--- System information. ---
Architecture:
Kernel: Linux 4.19.0-5-amd64

Debian Release: 10.0
500 xenial updates.signal.org
500 unstable debian.mirror.serversaustralia.com.au
500 stable repo.vivaldi.com
500 stable repo.skype.com
500 stable repo.nordvpn.com
500 stable linux.teamviewer.com
500 stable dl.google.com
500 jessie packagecloud.io

--- Package information. ---
Depends (Version) | Installed
=-+-==

breeze (>= 4:5.13) | 4:5.13.4-1
kactivitymanagerd (>= 5.13) | 5.13.5-1
kde-cli-tools (>= 4:5.13) | 4:5.13.5-1
kded5 | 5.54.0-1
kio | 5.51.0-1
oxygen-sounds (>= 4:5.13) | 4:5.13.4-1
plasma-desktop-data (= 4:5.13.5-1) | 4:5.13.5-1
plasma-framework | 5.51.0-1
plasma-integration (>= 5.13) | 5.13.5-1+b1
plasma-workspace (>= 4:5.13) | 4:5.13.5-1+b1
polkit-kde-agent-1 (>= 4:5.13) | 4:5.13.4-1
qml-module-org-kde-draganddrop | 5.51.0-2
qml-module-org-kde-kcoreaddons | 5.51.0-2
qml-module-org-kde-kquickcontrols | 5.51.0-2
qml-module-org-kde-kquickcontrolsaddons | 5.51.0-2
qml-module-org-kde-kwindowsystem | 5.51.0-2
qml-module-org-kde-solid | 5.54.0-1
qml-module-qt-labs-folderlistmodel | 5.11.3-4
qml-module-qt-labs-settings | 5.11.3-4
kpackagetool5 | 5.51.0-1
libappstreamqt2 | 0.12.7-1
libc6 (>= 2.15) |
libcanberra0 (>= 0.2) |
libfontconfig1 (>= 2.12.6) |
libfreetype6 (>= 2.2.1) |
libgcc1 (>= 1:3.0) |
libkf5activities5 (>= 5.21.0) |
libkf5activitiesstats1 (>= 5.35.0) |
libkf5archive5 (>= 4.96.0) |
libkf5auth5 (>= 4.96.0) |
libkf5baloo5 (>= 5.15.0) |
libkf5codecs5 (>= 4.96.0) |
libkf5completion5 (>= 4.97.0) |
libkf5configcore5 (>= 5.24.0) |
libkf5configgui5 (>= 5.25.0) |
libkf5configwidgets5 (>= 5.23.0) |
libkf5coreaddons5 (>= 5.16.0) |
libkf5dbusaddons5 (>= 4.99.0) |
libkf5declarative5 (>= 4.96.0) |
libkf5emoticons-bin |
libkf5emoticons5 (>= 4.96.0) |
libkf5globalaccel-bin |
libkf5globalaccel5 (>= 5.10.0) |
libkf5guiaddons5 (>= 4.96.0) |
libkf5i18n5 (>= 5.0.0) |
libkf5iconthemes5 (>= 5.0.0) |
libkf5itemmodels5 (>= 5.14.0) |
libkf5itemviews5 (>= 4.96.0) |
libkf5jobwidgets5 (>= 4.96.0) |
libkf5kcmutils5 (>= 4.96.0) |
libkf5kdelibs4support5 (>= 4.99.0) |
libkf5kiocore5 (>= 5.44.0) |
libkf5kiofilewidgets5 (>= 5.41.0) |
libkf5kiowidgets5 (>= 5.35.0) |
libkf5newstuff5 (>= 5.27.0) |
libkf5notifications5 (>= 5.3.0+git20141030.0311) |
libkf5notifyconfig5 (>= 5.24.0) |
libkf5package5 (>= 5.5.0+git) |
libkf5parts5 (>= 4.96.0) |
libkf5people5 |
libkf5peoplewidgets5 |
libkf5plasma5 (>= 5.41.0) |
libkf5plasmaquick5 (>= 4.98.0) |
libkf5quickaddons5 (>= 5.8.0+git20150324.0130+15.04) |
libkf5runner5 (>= 5.24.0) |
libkf5service-bin |
libkf5service5 (>= 5.2.0+git20140930) |
libkf5solid5 (>= 4.97.0) |
libkf5sonnetui5 (>= 4.96.0) |
libkf5wallet-bin |
libkf5wallet5 (>= 4.96.0) |
libkf5widgetsaddons5 (>= 4.96.0) |
libkf5windowsystem5 (>= 5.25.0) |
libkf5xmlgui5 (>= 4.98.0) |
libkfontinst5 |
libkfontinstui5 |
libkworkspace5-5 (>= 4:5.8.1) |
libphonon4qt5-4 (>= 4:4.8.0) |
libpulse-mainloop-glib0 (>= 0.99.1) |
libpulse0 (>= 0.99.1) |
libqt5concurrent5 (>= 5.10.0~) |
libqt5core5a (>= 5.11.0~rc1) |
libqt5dbus5 (>= 5.10.0~) |
libqt5gui5 (>= 5.10.0~) |
libqt5network5 (>= 5.10.0~) |
libqt5printsupport5 (>= 5.10.0~) |
libqt5qml5 (>= 5.1.0) |
libqt5quick5 (>= 5.7.0) |
libqt5quickwidgets5 (>= 5.4.0) |
libqt5sql5 (>= 5.10.0~) |
libqt5svg5 (>= 5.6.0~beta) |
libqt5widgets5 (>= 5.11.0~rc1) |
libqt5x11extras5 (>= 5.6.0) |
libqt5xml5 (>= 5.10.0~) |
libscim8v5 (>= 1.4) |
libstdc++6 (>= 5.2) |
libtaskmanager6 (>= 4:5.12.0) |
libx11-6 (>= 2:1.2.99.901) |
libx11-xcb1 |
libxcb-image0 (>= 0.2) |
libxcb-record0 |
libxcb-xkb1 |
libxcb1 |
libxcursor1 (>> 1.1.2) |
libxfixes3 |
libxft2 (>> 2.1.1) |
libxi6 (>= 2:1.2.99.4) |
libxkbfile1 |
phonon4qt5 |


Recommends (Version) | Installed
-+-=
bluedevil (>= 4:5.13) | 4:5.14.5-1
breeze-gtk-theme (>= 5.13) | 5.14.5-1
fonts-hack | 3.003-2
fonts-noto | 20181227-1
kde-config-gtk-style (>= 4:5.13) | 4:5.14.5-1
kde-config-screenlocker (>= 5.13) | 5.13.5-1
kde-config-sddm (>= 4:5.13) | 4:5.14.5-1
kde-style-oxygen-qt5 (>= 4:5.13) | 4:5.14.5-1
kgamma5 (>= 5.13) | 5.14.5-1
khelpcenter | 4:18.04.0-1
khotkeys (>= 4:5.13) | 4:5.14.5-1
kinfocenter (>= 4:5.13) | 4:5.13.4-1
kio-extras | 4:18.08.3-1
kmenuedit (>= 4:5.13) | 4:5.14.5-1
kscreen (>= 4:5.13) | 4:5.13.5-1
ksshaskpass (>= 4:5.13) | 4:5.14.5-1
ksysguard (>= 4:5.13) | 4:5.14.3-1
kwin-x11 (>= 4:5.13) | 4:5.13.5-1+b1
OR kwin |
kwrited (>= 4:5.13) | 4:5.14.5-1
libpam-kwallet5 (>= 5.13) | 5.14.5-1
plasma-discover (>= 5.13) | 5.10.5-2
plasma-pa (>= 

Bug#931363: Fails to create output PDF (permission denied)

[Brian Potkin]

On Sat 06 Jul 2019 at 12:29:18 +0300, Martin-Éric Racine wrote:

> I made further tests on Stretch. My current packages:
> 
> $ dpkg -l | grep -e ghostscript -e cups-pdf | awk '{print $2, $3}'
> ghostscript 9.26a~dfsg-0+deb9u3
> printer-driver-cups-pdf 2.6.1-22
> 
> Test 1: print an UTF-8 text file from Gedit.  Works.
> 
> Test 2: print an ODF document from LibreOffice. Works.
> 
> Test 3: print an HTML document from Firefox-ESR. Works.
> 
> This bug thus seems to occur rather randomly.  For the record, I
> indeed encountered a "permission denied" error when I tried printing
> to PDF the other day, but I no longer remember from which application
> I did. I probably pressed CTRL-P in whichever application I was using
> at that moment.

>From everything that has been said, the filtering system appears to be
doing its job correctly. This can be confirmed (as root) with

cupsfilter -p  -m printer/foo -e  > out.pdf

I wonder whether apparmor is involved? The journal is a place to look.

Chheers,

Brian.

Bug#641354: texlive-font-utils: should suggest lcdf-typetools

[Hilmar Preuße]

tags 641354 + pending
stop

On 12.09.11 21:44, Sebastian Harl wrote:

> font2afm requires cfftot1 (when converting OTF to AFM), which is
> available in the package lcdf-typetools. It would be nice if this could
> be documented by suggesting lcdf-typetools.
> 
Fixed in git, tag pending.

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#931492: verilator: please honour CFLAGS and CXXFLAGS to build

[Gianfranco Costamagna]

Source: verilator
Version: 4.016-2
Severity: serious
Tags: patch experimental

Hello, looks like the new dwz from experimental makes verilator FTBFS, see:
https://bugs.launchpad.net/ubuntu/+source/dwz/+bug/1835398

reason is: debug flags are not injected to every package that is built, and the 
new dwz in experimental
fails to compress them.

the attached patch fixes the build failure (that is showing only in 
experimental, for now)

thanks for accepting, I sent it by email also upstream some minutes ago.

G.
Description: Honour system flags, this makes debug flags being injected correctly
Author: Gianfranco Costamagna 
Last-Update: 2019-07-06

--- verilator-4.016.orig/configure.ac
+++ verilator-4.016/configure.ac
@@ -91,10 +91,10 @@ AC_SUBST(CFG_WITH_PREC11)
 AC_MSG_RESULT($CFG_WITH_PREC11)
 
 # Compiler flags
-CFLAGS=-I${includedir}
-CPPFLAGS=-I${includedir}
-CXXFLAGS=-I${includedir}
-LDFLAGS=-L${libdir}
+CFLAGS+=" -I${includedir}"
+CPPFLAGS+=" -I${includedir}"
+CXXFLAGS+=" -I${includedir}"
+LDFLAGS+=" -L${libdir}"
 
 # Checks for programs.
 AC_PROG_CC
--- verilator-4.016.orig/src/Makefile_obj.in
+++ verilator-4.016/src/Makefile_obj.in
@@ -60,6 +60,8 @@ pkgdatadir = @pkgdatadir@
 CFG_WITH_CCWARN = @CFG_WITH_CCWARN@
 CFG_WITH_DEFENV = @CFG_WITH_DEFENV@
 CPPFLAGS += @CPPFLAGS@
+CFLAGS += @CFLAGS@
+CXXFLAGS += @CXXFLAGS@
 LDFLAGS += @LDFLAGS@
 EXEEXT = @EXEEXT@
 CFG_CXXFLAGS_SRC = @CFG_CXXFLAGS_SRC@
@@ -135,7 +137,7 @@ VLCOVGEN = $(srcdir)/vlcovgen
 all: make_info $(TGT)
 
 make_info:
-	@echo "  Compile flags: " $(CXX) ${CPPFLAGS}
+	@echo "  Compile flags: " $(CXX) ${CFLAGS} ${CXXFLAGS} ${CPPFLAGS}
 
 clean mostlyclean distclean maintainer-clean::
 	-rm -f *.o *.d perlxsi.c *_gen_*
@@ -280,21 +282,21 @@ V3Number_test: V3Number_test.o
 	$(PERL) $(ASTGEN) -I$(srcdir) $*.cpp
 
 %.o:	%.cpp
-	$(OBJCACHE) ${CXX} ${CPPFLAGSWALL} -c $<
+	$(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSWALL} -c $<
 %.o:	%.c
-	$(OBJCACHE) ${CC}  ${CPPFLAGSWALL} -c $<
+	$(OBJCACHE) ${CC}  ${CFLAGS} ${CPPFLAGSWALL} -c $<
 
 V3ParseLex.o:	V3ParseLex.cpp V3Lexer.yy.cpp V3ParseBison.c
-	$(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+	$(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
 
 V3ParseGrammar.o:	V3ParseGrammar.cpp V3ParseBison.c
-	$(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+	$(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
 
 V3ParseImp.o:	V3ParseImp.cpp V3ParseBison.c
-	$(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+	$(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
 
 V3PreProc.o:	V3PreProc.cpp V3PreLex.yy.cpp
-	$(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+	$(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
 
  Generated files
 

Bug#931491: iputils: FTBFS in sid (missing dependency on setcap)

[Gianfranco Costamagna]

Source: iputils
Version: 3:20190515-1
Severity: serious
Tags: patch

Hello, looks like the new version does search for *bin/setcap tool, and fails 
to build if missing.

Please add it to build dependencies if possible

--- iputils-20190515/debian/control 2019-07-06 00:49:21.0 +0200
+++ iputils-20190515/debian/control 2019-07-06 13:27:11.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Noah Meyerhans 
 Standards-Version: 4.3.0
 Build-Depends: debhelper (>= 10), xsltproc, docbook-xsl,
- docbook-xsl-ns, libcap-dev,
+ docbook-xsl-ns, libcap-dev, libcap2-bin,
   libgcrypt-dev, libidn11-dev, bash (>= 3), meson
 Vcs-Git: https://salsa.debian.org/debian/iputils.git
 Vcs-Browser: https://salsa.debian.org/debian/iputils


thanks

G.

Bug#930869: Asked to try and mediate this bug.

[Adam Borowski]

Control: severity -1 wishlist
Control: tags -1 +moreinfo

On Sun, Jun 30, 2019 at 11:26:01AM -0400, Sam Hartman wrote:
> Unfortunately, to do that, I'm going to need to ask at least one
> question that Adam is already asked.
[...]

Michael: if you have trouble naming either any particular problem, or a
viable replacement for this package, I assume there are none.  If that's
incorrect, please provide more info before bumping the severity again.

The only remaining actionable part of this bug are the hacks ("quirks")
for buggy machines.  Having researched the package a bit more, I see that
they talk to real-mode display BIOS -- such machines generally stopped
being manufactured roughly at the time pm-utils became unmaintained
upstream, thus I wonder whether that particular part of the code can be
said to "do more more harm then good".  I'd wary before pulling the quirks
from under potentially working hardware.

But, I have no way to check that: none of 5 laptops I have even _has_ a
real-mode BIOS (three because of being non-x86, two because of level 3
UEFI without CSM).  And for my non-laptops, which range from a 2004 box to
this year's stuff, pm-utils work perfectly without quirks.

So there are two questions:
* are pm-utils useful on non-quirk hardware?
  • my answer is a strong "yes"
* should code for legacy hardware be kept if it can't be tested?
  • this part I can't answer


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ According to recent spams, "all my email accounts are owned
⢿⡄⠘⠷⠚⠋  by a hacker".  So what's the problem?
⠈⠳⣄

Bug#931490: should not be removed from Buster (important for visually impaired users))

[Mika Hanhijärvi]

Package: revelation
Version: 0.4.14-3
Severity: grave
Tags: ipv6

Hello

I am sorry that I report this so close to Buster release but I just noticeed
that in the Debian Buster release notes it is said that Revelation is removed
from the Buster. Release notes suggests that passwords can be exported from
Revelation and then imported to keepass2 password manager. Unfortunately that
is not an option if you are blind or other visually impaired user like I am.
Keepass2 password manager is not accessible with the Orca screen reader. So it
is not accessible if you are visually impaired. I am still using Debian
Stretch, but this problem most likeyly applies to Buster too. I have tried
every graphical password manager I can find in Debian Stretch and Revelation
isthe only graphical password managerwhich is accessible with the Orca screen
reader. None of the other graphical password managers are accessible with the
Orca screen reader. So Revelation is really the only accessible graphical
password manager for the visually impaired users.

So now if Revelation password manager is is not in Buster then suddenly
visually impaired users have no way to store their passwords and no way to
access passwords already stored in Revelation.

This is not ok, it is not ok to remove Revelation from Debian when there is no
other accessible password manger and no way to use keepass2 because it is not
accessible with Orca screen reader.

Please include Revelation in Buster.



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

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages revelation depends on:
ii  gconf2 3.2.6-4+b1
ii  gnome-extra-icons  1.1-3
ii  gnome-icon-theme   3.12.0-2
ii  python 2.7.13-2
ii  python-cracklib2.9.2-5
ii  python-crypto  2.6.1-7
ii  python-dbus1.2.4-1+b1
ii  python-gnome2  2.28.1+dfsg-1.2
ii  python-gobject 3.22.0-2
ii  python-gtk22.24.0-5.1
ii  shared-mime-info   1.8-1+deb9u1

revelation recommends no packages.

revelation suggests no packages.

-- no debconf information

Bug#931489: pastebinit

[bob mcgeeney]

Package: pastebinit 
Version: 1.5.2

When I type:

cat backup/Apt-faq | pastebinit 
I get this:

/usr/bin/pastebinit:42: DeprecationWarning: dist() and
linux_distribution() functions are deprecated in Python 3.5
  release = platform.linux_distribution()[0].lower()
/usr/bin/pastebinit:413: DeprecationWarning: pasteURLopener style of
invoking requests is deprecated. Use newer urlopen functions/methods
  url_opener = pasteURLopener()


I am using Debian Buster
Linux debian 4.19.0-5-amd64
libc6:amd64 2.28-10

Bug#904660: opensips FTBFS with json-c 0.13.1

[Gianfranco Costamagna]

control: tags -1 patch

On Thu, 26 Jul 2018 18:28:20 +0800 Nicolas Braud-Santoni 
 wrote:
> Source: opensips
> Version: 2.2.2-3
> Severity: important
> Control: block 904418 by -1
> Control: tag -1 + upstream
> 
> Hi,
> 
> I requested a transition slot for json-c (see #904418) and as part of the
> preparation I am rebuilding all its reverse dependencies, including opensips.
> 
> opensips fails to build because it tries to include a private header
> (json_object_private.h) which is not installed anymore. I am attaching the 
> build
> log here for your convenience.
> 
> 

hello, looks like Ubuntu did upload an upstream patch for this issue:
http://launchpadlibrarian.net/431597307/opensips_2.2.2-3build7_2.2.2-3ubuntu1.diff.gz

G.

Bug#931363: Fails to create output PDF (permission denied)

[Martin-Éric Racine]

I made further tests on Stretch. My current packages:

$ dpkg -l | grep -e ghostscript -e cups-pdf | awk '{print $2, $3}'
ghostscript 9.26a~dfsg-0+deb9u3
printer-driver-cups-pdf 2.6.1-22

Test 1: print an UTF-8 text file from Gedit.  Works.

Test 2: print an ODF document from LibreOffice. Works.

Test 3: print an HTML document from Firefox-ESR. Works.

This bug thus seems to occur rather randomly.  For the record, I
indeed encountered a "permission denied" error when I tried printing
to PDF the other day, but I no longer remember from which application
I did. I probably pressed CTRL-P in whichever application I was using
at that moment.

Martin-Éric




ke 3. heinäk. 2019 klo 15.39 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ke 3. heinäk. 2019 klo 14.51 martin f krafft (madd...@debian.org) kirjoitti:
> >
> > I straced gs run directly (as user "nobody"), as well as gs run from
> > cupsd. After replacing all hex addresses with 0xdeadbeef, the two
> > traces are nigh identical, except cupsd seems to close FDs 0–2, so
> > that when run from cupsd, the first FD used is 0, whereas it's 3
> > otherwise.
> >
> > Apart from that, I see absolutely no difference in the syscalls
> > until one of the fails to write the output file.
> >
> > Straces attached. Go ahead load them in vimdiff!
>
> Thanks. Let's see if we can figure out what causes this.
>
> Volker: please see the whole thread at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931363
>
> Thanks!
> Martin-Éric

Bug#931346: [PATCH] Add additional resolutions for 16:9 displays: 1600x900 and 2560x1440

[Uwe Kleine-König]

Control: tag -1 + patch
Control: forwarded -1 
https://mail.coreboot.org/hyperkitty/list/seab...@seabios.org/thread/BTTYP2LBOXN6RGATJEQPAXO244ZYHYPM/


signature.asc
Description: PGP signature

Bug#600766: notes2bib depends on texlive-latex3 features

[Hilmar Preuße]

On 20.10.10 00:27, Vincent Fourmond wrote:

Hi Vincent,

>   As advertised in the notes2bib documentation, notes2bib depends on
> LaTeX3 features, so I guess texlive-bibtex-extra should at least
> Recommend: texlive-latex3.
> 
>   Failure to have texlive-latex3 installed results in the following error:
> 
> [...]
> (/usr/share/texmf-texlive/tex/latex/notes2bib/notes2bib.sty
> 
> ! LaTeX Error: File `xparse.sty' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
> 
>   Once texlive-latex3 is installed, everything runs fine.
> 
Current situation ist that

hille@amd64-sid:~$ apt-file search xparse.sty
texlive-latex-recommended:
/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty

So one just have to install t-l-recommended. I guess this is OK or do we
need to add a suggestion to texlive-bibtex-extra?

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



signature.asc
Description: OpenPGP digital signature

Bug#425460: texlive-fonts-recommended: mtmi.tfm missing

[Hilmar Preuße]

On 21.05.07 22:05, Rik Snel wrote:

Hi all,

> this package used to include mtmi.tfm, mtsy.tfm, rmtmi.tfm and mtex.tfm 
> (in stable it does). These files are needed to get mathtime in pain TeX 
> with the mathtime macro's at: 
> http://www.ctan.org/tex-archive/macros/plain/contrib/mathtime/
> 
> Is see nothing in the changelog about the removal...
> 
Current situation is that mathtime has been completely removed from
Debian (and eventually replaced by something else): "apt-file search
mathtime" gives no useable result.

Hence I tend to close this bug. You may open a wishlist bug "please
re-include" mathtime, but due to the license situation described in this
bug we probably won't do that.

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



signature.asc
Description: OpenPGP digital signature

Bug#931488: jackd2: CVE-2019-13351

[Salvatore Bonaccorso]

Source: jackd2
Version: 1.9.12~dfsg-2
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for jackd2.

CVE-2019-13351[0]:
| posix/JackSocket.cpp in libjack in JACK2 1.9.1 through 1.9.12 (as
| distributed with alsa-plugins 1.1.7 and later) has a "double file
| descriptor close" issue during a failed connection attempt when jackd2
| is not running. Exploitation success depends on multithreaded timing
| of that double close, which can result in unintended information
| disclosure, crashes, or file corruption due to having the wrong file
| associated with the file descriptor.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-13351
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13351
[1] https://github.com/jackaudio/jack2/pull/480

Regards,
Salvatore

Bug#931487: libgcab-1.0-0: corrupts extracted data

[Stephen Kitt]

Package: libgcab-1.0-0
Version: 1.2-2
Severity: normal
Tags: patch

Dear Maintainer,

libgcab has an overflow bug which causes corruption when extracting
files; see https://gitlab.gnome.org/GNOME/gcab/issues/12 for details
and an example.

https://gitlab.gnome.org/GNOME/gcab/commit/5619f4cd2ca3108c8dea17ba656b5ce44a60ca29
fixes this.

Regards,

Stephen


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

Kernel: Linux 4.9.0-9-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgcab-1.0-0 depends on:
ii  libc6 2.24-11+deb9u4
ii  libglib2.0-0  2.50.3-2
ii  zlib1g1:1.2.8.dfsg-5

libgcab-1.0-0 recommends no packages.

libgcab-1.0-0 suggests no packages.

-- no debconf information
commit 5619f4cd2ca3108c8dea17ba656b5ce44a60ca29
Author: Marc-André Lureau 
Date:   Fri Jan 11 19:42:40 2019 +0400

Revert "decomp: fix gcc warning strict-overflow"

The warning doesn't happen with current build-sys.

The overlapping behaviour is undefined with memcpy. memmove doesn't
have the same semantic either than the loop. Let's revert!

Fixes:
https://gitlab.gnome.org/GNOME/gcab/issues/12

This reverts commit e48074952743f53d8ac529d4debc421e7e0f6937.

Signed-off-by: Marc-André Lureau 

diff --git a/libgcab/decomp.c b/libgcab/decomp.c
index 64d97f8..0c2b184 100644
--- a/libgcab/decomp.c
+++ b/libgcab/decomp.c
@@ -1015,9 +1015,7 @@ int LZXfdi_decomp(int inlen, int outlen, fdi_decomp_state 
*decomp_state) {
 window_posn += match_length;
 
 /* copy match data - no worries about destination wraps */
-memcpy(rundest, runsrc, match_length);
-rundest += match_length;
-runsrc += match_length;
+while (match_length-- > 0) *rundest++ = *runsrc++;
   }
 }
 break;
@@ -1106,9 +1104,7 @@ int LZXfdi_decomp(int inlen, int outlen, fdi_decomp_state 
*decomp_state) {
 window_posn += match_length;
 
 /* copy match data - no worries about destination wraps */
-memcpy(rundest, runsrc, match_length);
-rundest += match_length;
-runsrc += match_length;
+while (match_length-- > 0) *rundest++ = *runsrc++;
   }
 }
 break;

Bug#931486: xautolock man page -secure description is incorrect

[Owen Heisler]

Package: xautolock
Version: 1:2.2-5.1+b1

The xautolock(1) man page has an incorrect description for the 
"-secure" option. It describes the "-secure" option as ignoring the 
"-enable", "-disable", "-toggle", and "-exit" options.


According to the usage output from `xautolock -h`, the "-secure" 
option also ignores "-locknow", "-unlocknow", and "-restart" options.


The xautolock(1) man page should be updated to provide the full list 
of ignored options.


Thanks

Bug#726252: makeinfo fail to process vera

[Hilmar Preuße]

reassign 726252 src:vera
notforwarded 726252
stop

On 13.10.13 23:07, Bill Allombert wrote:

Hi,

> makeinfo fails to process vera:
> 
The vera.texi reads:

"Version 7.7 (Texinfo release 1.21a) is a bug fix release.
V.E.R.A. would not compile correctly with recent versions
of @file{makeinfo}.

This is still partly true to the nested structure of the
Top node: The convenient multicolumn letter listing is not
a menu section, which newer versions of @file{makeinfo} bleat
about. It is perfectly safe to ignore those errors for now.

Please use

@code{makeinfo --force vera.texi}

to compile the info file(s). They will work as expected."

According to my understanding we look @ a bug in vera and a wanted
change in makeinfo. I could confirm that vera builds fine even if your
patch 01_texinfo_node_menu.diff has not been applied, when using --force.

Reassigning back to vera. If you think this is not correct, call back.

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



signature.asc
Description: OpenPGP digital signature

Bug#929931: [Pkg-samba-maint] Bug#929931: CTDB: Debian Enablement (focus: NFS HA)

[Rafael David Tinoco]

Fix for this is at the following merge request:

https://salsa.debian.org/samba-team/samba/merge_requests/25

Bug#931138: ctdb: DEB_HOST_ARCH_CPU initialization through dpkg-architecture

[Rafael David Tinoco]

The fix for this has been proposed into:

https://salsa.debian.org/samba-team/samba/merge_requests/25