Bug#923215: split into several binary packages

[Ralf Treinen]

Source: ssreflect
Version: 1.7.0+dfsg-1 
Severity: wishlist

This is a big package, it should be split into several binary packages
along the the line of the opam packaging of mathcomp.

Bug#871285: libxmmsclient++4v5: requires rebuild against GCC 7 and symbols/shlibs bump

[Emanuele Rocca]

On 07/08 03:47, jcowg...@debian.org wrote:
> - If your package does not provide a symbols file, add a dh_makeshlibs
>   override so that tight enough dependencies are generated.
> 
>   Using libebml as an example (debian/rules):
>   + override_dh_makeshlibs:
>   +   # For new symbols when compiled with GCC 7
>   +   dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
> 
>   Where "1.3.4-2" is the version this bug was fixed in.

Done, NMU diff attached.
diff -Nru xmms2-0.8+dfsg/debian/changelog xmms2-0.8+dfsg/debian/changelog
--- xmms2-0.8+dfsg/debian/changelog	2017-11-16 13:54:03.0 +0100
+++ xmms2-0.8+dfsg/debian/changelog	2019-02-25 08:12:48.0 +0100
@@ -1,3 +1,11 @@
+xmms2 (0.8+dfsg-18.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Build using GCC 8 and tighten dependency on the shared library. Closes:
+#871285
+
+ -- Emanuele Rocca   Mon, 25 Feb 2019 08:12:48 +0100
+
 xmms2 (0.8+dfsg-18.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xmms2-0.8+dfsg/debian/rules xmms2-0.8+dfsg/debian/rules
--- xmms2-0.8+dfsg/debian/rules	2017-01-02 21:45:31.0 +0100
+++ xmms2-0.8+dfsg/debian/rules	2019-02-25 08:12:48.0 +0100
@@ -67,3 +67,7 @@
 
 override_dh_install:
 	dh_install --fail-missing
+
+override_dh_makeshlibs:
+	# For new symbols when compiled with GCC >= 7
+	dh_makeshlibs -V'libxmmsclient++4v5 (>= 0.8+dfsg-18.2~)'

Bug#923209: RFS: heaptrack/1.1.0+20180922.gitf752536-3.1 [NMU]

[Chris Lamb]

Hi Nicholas,

> heaptrack (1.1.0+20180922.gitf752536-3.1) unstable; urgency=medium
> 
>   * Non-maintainer upload.
>   * Update description to make heaptrack more discoverable to users.
> (Closes: #915241)
> 
>  -- Nicholas D Steeves   Sun, 24 Feb 2019 19:44:03 -0700

Whilst I agree about the poor visibility I don't think this
warrants a non-maintainer upload (or even a "normal"-level
severity…) especially during a freeze so I will not be sponsoring
this upload. Apologies.


Best wishes,

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

Bug#859224: netkit-ftp-ssl: diff for NMU 0.17.34+0.2-4.1

[Christoph Biedl]

Sebastian Andrzej Siewior wrote...

> > +Build-Depends: debhelper (>= 10~), libeditline-dev, libncurses5-dev, 
> > libssl1.0-dev | libssl-dev (<< 1.1.0~), cmake
> 
> you need to drop libssl1.0-dev from here and simply depend on
> libssl-dev.

Thanks for checking and the heads-up, noted.

Christoph


signature.asc
Description: PGP signature

Bug#919975: [Pkg-mailman-hackers] Bug#919975: mailman3-web: whoosh python2 and python3 databases are not compatible

[Sampo Sorsa]

On Friday, February 22, 2019 9:35 PM, Jonas Meurer  
wrote:

> I don't think it's worth the trouble anymore. The python3 django
> packages have been in buster and stretch-backports for a while now, and
> probably nobody will ever run into this again.
>
> Would you agree with closing this bugreport, Sampo and PEB?

Closing is okay to me, this report has likely served its purpose by now.

Bug#762081: Update for 1.8.3-2+b1

[GCS]

Hi Markus,

On Sun, Feb 24, 2019 at 7:09 PM markus  wrote:
> with rdesktop 1.8.3-2+b1 on Debian 9.8 this problem seems to be solved.
 Did you try the Stretch security update, the 1.8.4-1~deb9u1 version
of rdesktop? If yes, was it slow?

Regards,
Laszlo/GCS

Bug#923214: g++-mingw-w64: Internal compiler error when include qfloat16.h, Qt5.12.

[Kyuma Ohta]

Package: g++-mingw-w64
Version: 8.2.0-21+21.1
Severity: important

Dear Maintainer,

When building software with Qt, internal compiler error happend useally.
---
In file included from
/usr/local/i586-mingw-msvc/5.12/mingw_82x/include/QtCore/qendian.h:44,
 from
/usr/local/i586-mingw-msvc/5.12/mingw_82x/include/QtCore/QtEndian:1,
 from
/home/whatisthis/src/common_source_project-fm7/source/src/vm/../common.h:138,
 from
/home/whatisthis/src/common_source_project-fm7/source/src/vm/../emu.h:26,
 from
/home/whatisthis/src/common_source_project-fm7/source/src/vm/device.h:15,
 from
/home/whatisthis/src/common_source_project-fm7/source/src/vm/z80.h:14,
 from
/home/whatisthis/src/common_source_project-fm7/source/src/vm/315-5124.cpp:11:
/usr/local/i586-mingw-msvc/5.12/mingw_82x/include/QtCore/qfloat16.h:79:54:internal
 compiler error: in make_rtl_for_nonlocal_decl, at
cp/decl.c:6590 Q_CORE_EXPORT static const quint32 mantissatable[];
   ^
   0x7f33c577f09a
__libc_start_main
../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See  for instructions.
make[2]: *** [vm/common_vm/CMakeFiles/vm_common_vm.dir/build.make:64:
vm/common_vm/CMakeFiles/vm_common_vm.dir/home/whatisthis/src/common_source_project-fm7/source/src/vm/315-5124.cpp.obj]
Error 1
make[1]: *** [CMakeFiles/Makefile2:91:
vm/common_vm/CMakeFiles/vm_common_vm.dir/all] Error 2

I built from https://github.com/Artanejp/common_source_project_fm7 
with Qt5.12,*BUT* same issue happens at building Qt5.12.1 with this
toolchain.

This issue has *not* happend 8.2.0-17 and before version,only this
version.

Regards,
Ohta.


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

Kernel: Linux 4.20.11-homebrew-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ja_JP.UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to ja_JP.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages g++-mingw-w64 depends on:
ii  g++-mingw-w64-i6868.2.0-21+21.1
ii  g++-mingw-w64-x86-64  8.2.0-21+21.1

g++-mingw-w64 recommends no packages.

g++-mingw-w64 suggests no packages.

-- no debconf information

Bug#923213: squid: Please disable the "Test apparmor" autopkgtest

[intrigeri]

Source: squid
Severity: normal
Version: 4.6-1

Hi,

it seems that test_zz_apparmor only passed on Debian previously
because it implicitly relied on a bug in apparmor_parser,
which used to return 0 if called on a non-existent profile.

This bug was fixed in apparmor 2.13.2-8, which broke squid's
autopkgtests:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/squid/1998185/log.gz

The corresponding code is:

# Verify it is syntactically correct
ret, report = cmd(['apparmor_parser', '-p', self.aa_abs_profile])
expected = 0
result = 'Got exit code %d, expected %d\n' % (ret, expected)
self.assertEquals(ret, expected, result + report)

… and the parser now returns exit code 2, because
/etc/apparmor.d/usr.sbin.squid does not exist. Previously the test
would happily pretend that there's a syntactically correct AppArmor
profile, while there's no such profile at all.

If I got it right, on Debian we don't ship
/etc/apparmor.d/usr.sbin.squid, so none of the tests in the
test_zz_apparmor function are meaningful in this context.
So I think this entire test case should be skipped on Debian.

Cheers,
-- 
intrigeri

Bug#922644: mariadb-server-10.3: Unable to reinstall

[Janusz S. Bień]

On Mon, Feb 18 2019 at 20:41 +01, Janusz S. Bień wrote:

[...]

> -- Configuration Files:
> /etc/mysql/mariadb.conf.d/50-server.cnf changed:
> [server]
> [mysqld]
> user  = mysql
> pid-file  = /var/run/mysqld/mysqld.pid
> socket= /var/run/mysqld/mysqld.sock
> port  = 3306
> basedir   = /usr
> datadir   = /var/lib/mysql
> tmpdir= /tmp
> lc-messages-dir   = /usr/share/mysql
> skip-external-locking
> % bind-address= 192.168.1.11
^^^

The silly typo was the culprit.

The credit for spotting it goes to Stephen Worthington:

http://lists.mythtv.org/pipermail/mythtv-users/2019-February/399639.html

Best regards

Janusz

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

Bug#921327: grml2usb doesn't recognize a fat16 filesytem

[Elimar Riesebieter]

* Michael Prokop  [2019-02-20 15:47 +0100]:

> * Elimar Riesebieter [Mon Feb 04, 2019 at 10:32:49AM +0100]:
> 
> > root@pippin>pts/0 ~ # mkfs.vfat -F 16 -v /dev/sdf2
> > mkfs.fat 4.1 (2017-01-24)
> > /dev/sdf2 has 64 heads and 32 sectors per track,
> > hidden sectors 0x3800800;
> > logical sector size is 512,
> > using 0xf8 media descriptor, with 2097152 sectors;
> > drive number 0x80;
> > filesystem has 2 16-bit FATs and 32 sectors per cluster.
> > FAT size is 256 sectors, and provides 65518 clusters.
> > There are 32 reserved sectors.
> > Root directory contains 512 slots and uses 32 sectors.
> > Volume ID is 5c940374, no volume label.
> 
> > root@pippin>pts/0 ~ # grml2usb --bootoptions=%lang=de 
> > --bootoptions=%persistence grml64-full_2018.12.iso /dev/sdf2
> > Executing grml2usb version 0.16.2
> > Execution failed: Partition /dev/sdf2 does not contain a FAT16 filesystem. 
> > (Use --fat16 or run mkfs.vfat /dev/sdf2)
> 
> > /dev/sdf2 is a partition on a stick. I tried both gpt and msdos
> > partitiontables, though.
> 
> Can you please provide the output of:
> 
>   blkid -s TYPE -o value /dev/sdf2
> 
> ? This should output "vfat", if not then you'll get the error
> message you're quoting.

The output is vfat. Running grml2usb gives 

Executing grml2usb version 0.16.3
Execution failed: Partition /dev/sdf2 does not contain a FAT16 filesystem. (Use 
--fat16 or run mkfs.vfat /dev/sdf2)

> I assume you're using mkfs.vfat from dosfstools 4.1-2 (your output
> looks similar to what I get on current buster)?

Yes it is from dosfstools 4.1-2

Thanks
Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.


signature.asc
Description: PGP signature

Bug#922815: insserv FATAL while updating as mountkernfs has to be enabled to use service udev

[shirish शिरीष]

Reply at bottom :-

On 24/02/2019, Dmitry Bogatov  wrote:



> Interesting, you seems somehow got mountkernfs.sh script removed from
> runlevel S.
>
> Can you please invoke as root
>
>   # update-rc.d mountkernfs.sh enable S
>
> and then retry your upgrade.

When I try the command you shared, it says -

root@debian:~# update-rc.d mountkernfs.sh enable S
update-rc.d: error: cannot find a LSB script for mountkernfs.sh

> --
> Note, that I send and fetch email in batch, once every 24 hours.
>  If matter is urgent, try https://t.me/kaction
>
> --
>

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#923212: g++-6: ifstream operator >> may throw when exceptions() == 0

[John Jowett]

Package: g++-6
Version: 6.3.0-18+deb9u1
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 ***
Lead up: I was testing a program to see whether a user could screw it up.  The
answer was YES, for

I tried opening and reading a directory instead of a file using
std::ifstream.open() and operator >>.

Outcome:

The directory was opened sucessfully (rdstate()==0).
On reading a character using operator >> an error of type
std::ios_base::failure >> was thrown, with
what() == "basic_filebuf::underflow error reading the file: iostream error".
Prior to the read the stream had exceptions() == 0.


Expectation:

The prescribed behaviour (www.cplusplus.com) for ifsteam operator >> is:

Basic guarantee: if an exception is thrown, the object is in a valid state.
It throws an exception of member type failure if the resulting error state flag
is not goodbit and member exceptions was set to throw for that state.
Any exception thrown by an internal operation is caught and handled by the
function, setting badbit. If badbit was set on the last call to exceptions, the
function rethrows the caught exception.

I interpret this to mean that operator >> will not throw unless you tell it to
by setting the exception mask to non-zero (the mask being 0 by default.)
Consequently I expected badbit to be set for the stream, and no exception to be
thrown.

I submit a source file and session log demonstrating the fault.



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

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

Versions of packages g++-6 depends on:
ii  gcc-66.3.0-18+deb9u1
ii  gcc-6-base   6.3.0-18+deb9u1
ii  libc62.24-11+deb9u3
ii  libgmp10 2:6.1.2+dfsg-1
ii  libisl15 0.18-1
ii  libmpc3  1.0.3-1+b2
ii  libmpfr4 3.1.5-1
ii  libstdc++-6-dev  6.3.0-18+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

g++-6 recommends no packages.

Versions of packages g++-6 suggests:
pn  g++-6-multilib
ii  gcc-6-doc 6.3.0-1
pn  libstdc++6-6-dbg  
#include 
#include 
#include 

int main(int argc, char** argv)
{
using std::cout; using std::endl;

if (argc != 2) {
cout << "Program requires 1 argument (file name)" << endl;
return 1;
}


char s;
std::ifstream ifl;

cout << std::hex;

cout << "Opening file\n"
<< "Exception mask on open: " << ifl.exceptions() << 
endl;
try {
ifl.open(argv[1]);
}

catch(const std::ios_base::failure& e)
{
cout << "std::ios_base::failure exception thrown on open: \n";
cout << e.what() << '\n';
cout << "state after exception: " << ifl.rdstate() << endl; 

return 1;
}

catch(const std::exception& e)
{
cout << "std::exception thrown on open:\n" << e.what() << endl;
cout << e.what() << '\n';
cout << "state after exception: " << ifl.rdstate() << endl; 
return 1;
}

catch(...)
{
cout << "Other exception thrown" << endl;
cout << "state after exception: " << ifl.rdstate() << endl; 
return 1;   
}

cout << "No exceptions thrown\n";
cout << "State after opening: " << ifl.rdstate() << endl;

if (!ifl.good() ) {
cout << "Error opening file" << endl;
return 0;
}



cout << "Reading file\n"
<< "Exception mask on read: " << ifl.exceptions() << 
endl;

try {
ifl >> s;
}

catch(const std::ios_base::failure& e)
{
cout << "std::ios_base::failure exception thrown on read: \n";
cout << e.what() << '\n';
cout << "state after exception: " << ifl.rdstate() << endl; 

return 1;
}

catch(const std::exception& e)
{
cout << "std::exception thrown on read:\n" << e.what() << endl;
cout << e.what() << '\n';
cout << "state after exception: " << ifl.rdstate() << endl; 
return 1;
}

catch(...)
{
cout << "Other exception thrown 

Bug#923211: libpomegranate-clojure: maven-repo version is wrong (1.1.0-SNAPSHOT)

[Elana Hashman]

Package: libpomegranate-clojure
Version: 1.1.0-1
Severity: normal
Control: block 900299 by -1

Apparently I got the wrong upstream commit when tagging the release
because this is what's showing up in the maven repo for
libpomegranate-clojure_1.1.0-1:

ehashman@corn-syrup:~$ ls /usr/share/maven-repo/com/cemerick/pomegranate/
1.1.0-SNAPSHOT  debian

This doesn't appear to be breaking anything because most Clojure
libraries depend on the "debian" version release, but Leiningen wants to
reference 1.1.0 directly and can't currently resolve it.

I'll just upload a 1.1.0+really release...


signature.asc
Description: PGP signature

Bug#900299: leiningen-clojure: depends on openjdk-8

[Elana Hashman]

On Sat, Feb 23, 2019 at 06:34:53PM -0500, Elana Hashman wrote:
> So this weekend I am going to look into changing the build to more
> closely match upstream, now that we've bootstrapped a working
> Leiningen into the archive. This would involve building Leiningen with
> a previous version of itself, as upstream does.

I believe I have this working now, see latest commits on salsa[*].

I think I still have some tidying to do before this will work properly
in a clean build environment, and the fix depends on an unreleased
change in pomegranate (the 1.1.0 in the archive is showing up as
1.1.0-SNAPSHOT >_<), but I should have this uploaded by EOW.

Note that Leiningen is still a lot slower and has different behaviour on
jdk11, and users will likely prefer to run it on jdk8, but they can
override the default Java by exporting JAVA_CMD fwiw. I might include a
note of this in release news.

- e

[*]: 
https://salsa.debian.org/clojure-team/leiningen-clojure/compare/e6ec5bdee239a1fb86c0f7dcfa2e091c09712002...master


signature.asc
Description: PGP signature

Bug#923210: bash-completion: postinst and postrm generate find warnings

[Daniel Lewart]

Package: bash-completion
Version: 1:2.8-5
Severity: minor
Tags: patch

Gabriel, et al,

Both "apt install bash-completion" and "apt purge bash-completion"
generate the following warning:
find: '/etc/bash_completion.d/': No such file or directory

The cause is that postinst and postrm assume that
/etc/bash_completion.d exists.

Patch is attached.

Thank you!
Daniel Lewart
diff -ru a/debian/postinst b/debian/postinst
--- a/debian/postinst   2018-12-21 19:23:09.0 -0600
+++ b/debian/postinst   2019-02-24 00:00:00.0 -0600
@@ -4,19 +4,21 @@
 
 case "$1" in
 configure)
-# let's remove old bash-completion conffiles
-for f in $(find /etc/bash_completion.d/ -type f -name "*.dpkg-*"); do
-dpkg-maintscript-helper rm_conffile ${f%.dpkg-*} 1:1.3-1 -- "$@"
-done
+if [ -d /etc/bash_completion.d ]; then
+# let's remove old bash-completion conffiles
+for f in $(find /etc/bash_completion.d/ -type f -name "*.dpkg-*"); 
do
+dpkg-maintscript-helper rm_conffile ${f%.dpkg-*} 1:1.3-1 -- 
"$@"
+done
 
-if dpkg --compare-versions "$2" le "1:2.1-3"; then
-if [ -d /etc/bash_completion.d/helpers ]; then
-rmdir --ignore-fail-on-non-empty 
/etc/bash_completion.d/helpers 2>/dev/null
+if dpkg --compare-versions "$2" le "1:2.1-3"; then
+if [ -d /etc/bash_completion.d/helpers ]; then
+rmdir --ignore-fail-on-non-empty 
/etc/bash_completion.d/helpers 2>/dev/null
+fi
+# disabled from Ubuntu, third party packages might have 
installed things here
+#if [ -d /etc/bash_completion.d ]; then
+#rmdir --ignore-fail-on-non-empty /etc/bash_completion.d 
2>/dev/null
+#fi
 fi
-# disabled from Ubuntu, third party packages might have installed 
things here
-#if [ -d /etc/bash_completion.d ]; then
-#rmdir --ignore-fail-on-non-empty /etc/bash_completion.d 
2>/dev/null
-#fi
 fi
;;
 abort-upgrade|abort-remove|abort-deconfigure)
diff -ru a/debian/postrm b/debian/postrm
--- a/debian/postrm 2018-12-21 19:23:09.0 -0600
+++ b/debian/postrm 2019-02-24 00:00:00.0 -0600
@@ -5,10 +5,12 @@
 case "$1" in
 purge)
rm -f /etc/bash_completion
-# let's remove old bash-completion conffiles
-for f in $(find /etc/bash_completion.d/ -type f -name "*.dpkg-*"); do
-dpkg-maintscript-helper rm_conffile ${f%.dpkg-*} 1:1.3-1 -- "$@"
-done
+   if [ -d /etc/bash_completion.d ]; then
+# let's remove old bash-completion conffiles
+for f in $(find /etc/bash_completion.d/ -type f -name "*.dpkg-*"); 
do
+dpkg-maintscript-helper rm_conffile ${f%.dpkg-*} 1:1.3-1 -- 
"$@"
+done
+   fi
;;
 remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
;;

Bug#923209: RFS: heaptrack/1.1.0+20180922.gitf752536-3.1 [NMU]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an NMU of "heaptrack", to fix its poor 
discoverability.

It builds these binary packages:

  heaptrack - heap memory profiler for Linux
  heaptrack-gui - heap memory profiler for Linux
  libheaptrack - heap memory profiler for Linux

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/h/heaptrack/heaptrack_1.1.0+20180922.gitf752536-3.1.dsc

More information about heaptrack can be obtained from 
https://github.com/KDE/heaptrack.

Changes since the last upload:

heaptrack (1.1.0+20180922.gitf752536-3.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Update description to make heaptrack more discoverable to users.
(Closes: #915241)

 -- Nicholas D Steeves   Sun, 24 Feb 2019 19:44:03 -0700

heaptrack (1.1.0+20180922.gitf752536-3) unstable; urgency=medium


I've updated the description for all three bin:packages, and I believe
you will agree that the following diff fragment represents a
significant improvement, and justifies the NMU (apt search keyword
will find heaptrack):

-Description: Heap memory profiler for Linux
- Heap memory usage profiler. It uses LD_PRELOAD to track all
- calls to the core memory allocation functions and logs these
- occurrences. Additionally, backtraces are obtained and logged.
+Description: heap memory profiler for Linux
+ Heap memory usage profiler. It uses LD_PRELOAD to track all calls
+ to the core memory allocation functions and logs these occurrences.
+ Additionally, backtraces are obtained and logged. It can also
+ generate a historigram of allocation sizes over the number of
+ calls. Heaptrack measures the following:
  .
- The package contains command line tools.
+   * Heap memory consumption (like Massif).
+   * Number of calls to allocation functions (like callgrind).
+   * Total amount of memory allocated, ignoring deallocations.
+   * Leaked memory (like memcheck).
+ .
+ Heaptrack is notable for it's ability to attach to running processes,
+ for consuming substantially less memory than Valgrind, and for not
+ reducing an application's interactivity as much as Valgrind does.
+ Heaptrack is useful for debugging memory leaks and memory ballooning.
+ .
+ The package contains the command line tools.


Regards,
Nicholas

Bug#770124: RFP: webext-tosdr -- toolbar icon to inform about your rights

[Ben Finney]

Control: retitle -1 Bug#770124: RFP: webext-tosdr -- toolbar icon to inform 
about your rights

Now that Firefox in Debian is not compatible with XUL for its add-ons,
the earlier request for a XUL extension is superseded by an add-on
built with WebExtensions. The current upstream for this is now:

Upstream author: ToS;DR Initiative 
URL: https://github.com/tosdr/browser-extensions
License: AGPL-3+

-- 
 \   “… correct code is great, code that crashes could use |
  `\   improvement, but incorrect code that doesn’t crash is a |
_o__)horrible nightmare.” —Chris Smith, 2008-08-22 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#915241: heaptrack -- resolve poor discoverability

[Nicholas D Steeves]

On Sun, Feb 24, 2019 at 07:38:12PM -0700, Nicholas D Steeves wrote:
> Control: retitle -1 heaptrack -- resolve poor discoverability
> 
> On Sat, Dec 01, 2018 at 07:38:05PM -0500, Nicholas D Steeves wrote:
> > Package: src:heaptrack
> > Severity: normal
> > 
> > https://salsa.debian.org/science-team/heaptrack/merge_requests/1
> > 
> > This MR merges Anton's work from experimental and enhances the
> > description to make heaptrack discoverable via keyword search, plus
> > adds a couple of extremely brief comparisons with Valgrind.
> > 
> > When I was debugging a dbus+kde memory ballooning/memleak issue, I was
> > not able to find heaptrack with a keyword search, so packaged
> > memleax. Having now discovered heaptrack via the memleax bugtracker
> > (yes, really!) I believe the best path forward is to make heaptrack
> > discoverable and scrap my work on memleax.
> > 
> > Thank you for considering this MR,
> > Nicholas
> 
> It has been almost three months without a reply, so to address
> Heaptrack's discoverability issue I plan an NMU delayed + x days to
> 2019-03-01 of the proposed updates to the description, without merging
> the commits from experimental.  I will file a new MR to make
> integrating the NMU easier.
> 
> Memleax has been abandoned upstream and I have filed a RoM NPOASR at
> #923206, and Heaptrack now appears to be the only software in Debian
> that can debug memleaks in an already-running process.
> 
> Respectfully,
> Nicholas

New MR filed here:

  https://salsa.debian.org/science-team/heaptrack/merge_requests/2


signature.asc
Description: PGP signature

Bug#923208: libengine-pkcs11-openssl: libengines-pkcs11-openssl is installing to the wrong engine directory on x86

[james.bottom...@hansenpartnership.com]

Package: libengine-pkcs11-openssl
Version: 0.4.9-3
Severity: grave
Justification: renders package unusable

The problem is this:

bedivere:~# dpkg -L libengine-pkcs11-openssl |grep engines
/usr/lib/i686-linux-gnu/engines-1.1
/usr/lib/i686-linux-gnu/engines-1.1/pkcs11.la
/usr/lib/i686-linux-gnu/engines-1.1/pkcs11.so
/usr/lib/i686-linux-gnu/engines-1.1/libpkcs11.so

But if you look at where the openssl engines dir actually is

bedivere:~# dpkg -L libssl1.1 |grep engines
/usr/lib/i386-linux-gnu/engines-1.1
/usr/lib/i386-linux-gnu/engines-1.1/afalg.so
/usr/lib/i386-linux-gnu/engines-1.1/capi.so
/usr/lib/i386-linux-gnu/engines-1.1/padlock.so

The result being the pkcs11 engine is unusable leading to errors like this:

[  221s] invalid engine "pkcs11"
[  221s] 4145891072:error:25066067:DSO support routines:dlfcn_load:could not 
load the shared 
library:../crypto/dso/dso_dlfcn.c:117:filename(/usr/lib/i386-linux-gnu/engines-1.1/pkcs11.so):
 /usr/lib/i386-linux-gnu/engines-1.1/pkcs11.so: cannot open shared object file: 
No such file or directory

This looks to be caused by an incorrect override to the --enginesdir
configure flag in the debian/rules file of libp11:

---
ENGINES_DIR := /usr/lib/$(DEB_HOST_GNU_TYPE)/engines-$(OPENSSL_VERSION)

%:
dh $@

override_dh_auto_configure:
dh_auto_configure -- \
--with-enginesdir=$(ENGINES_DIR)

---

I think the libcrypto pkgconf file just works, so there's no need for the
override.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-2-686 (SMP w/1 CPU core)
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)
LSM: AppArmor: enabled

Versions of packages libengine-pkcs11-openssl depends on:
ii  libc6  2.28-6
ii  libssl1.1  1.1.1a-1
ii  p11-kit0.23.14-2

libengine-pkcs11-openssl recommends no packages.

libengine-pkcs11-openssl suggests no packages.

-- no debconf information

Bug#915241: heaptrack -- resolve poor discoverability

[Nicholas D Steeves]

Control: retitle -1 heaptrack -- resolve poor discoverability

On Sat, Dec 01, 2018 at 07:38:05PM -0500, Nicholas D Steeves wrote:
> Package: src:heaptrack
> Severity: normal
> 
> https://salsa.debian.org/science-team/heaptrack/merge_requests/1
> 
> This MR merges Anton's work from experimental and enhances the
> description to make heaptrack discoverable via keyword search, plus
> adds a couple of extremely brief comparisons with Valgrind.
> 
> When I was debugging a dbus+kde memory ballooning/memleak issue, I was
> not able to find heaptrack with a keyword search, so packaged
> memleax. Having now discovered heaptrack via the memleax bugtracker
> (yes, really!) I believe the best path forward is to make heaptrack
> discoverable and scrap my work on memleax.
> 
> Thank you for considering this MR,
> Nicholas

It has been almost three months without a reply, so to address
Heaptrack's discoverability issue I plan an NMU delayed + x days to
2019-03-01 of the proposed updates to the description, without merging
the commits from experimental.  I will file a new MR to make
integrating the NMU easier.

Memleax has been abandoned upstream and I have filed a RoM NPOASR at
#923206, and Heaptrack now appears to be the only software in Debian
that can debug memleaks in an already-running process.

Respectfully,
Nicholas


signature.asc
Description: PGP signature

Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used

[Norbert Preining]

Hi,

On Mon, 25 Feb 2019, Thorsten Glaser wrote:
> > https://github.com/debian-tex/texlive-nonbin
> 
> OK, will do so. I’ll give people a bit to review,

I already updated the git repo with your change, thanks.

> And if you have something else related to TeX you
> need uploaded quickly, ping me.

Beeh, there are lot of things, in particular the sleep patch for texdoc
to make it work with xdg-open and compressed documents.

If you want I can prepare a set of packages with the changes that hang
around (blacklist one file, add recommends, fix texdoc, fix tabu)
and sign it, you check the sig, re-sign it and upload.

But honestly, why do I need to beg for uploading ... feeling 

Bug#923207: lxsession has false dependency on systemd

[Joshua]

Package: lxsession
Version: 0.5.3-2
Severity: serious
Tags: newcomer
Justification: Policy 7.2

lxsession declares a false dependency on systemd. "Depends: This declares an 
absolute dependency
The Depends field should be used if the depended-on package is required for the 
depending package to provide a significant amount of functionality."

I am running on a system with systemd present on the disk but completely 
nonfunctional. No lxsession functionality is broken.

Perhaps you think lxsession depends on systemd because some lower-level 
dependencies depend on it (like pulseaudio...) I have been manually
addressing lower-level dependencies one by one until none remain. Their own 
declarations catch stuff directly; lxsession doesn't need to.

More packages, same issue: lxde lxde-core openbox-lxde-session task-lxde-desktop


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

Kernel: Linux 4.19.0-2-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)
LSM: AppArmor: enabled

Versions of packages lxsession depends on:
ii  laptop-detect  0.16
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-7
ii  libcairo2  1.16.0-2
ii  libfontconfig1 2.13.1-2
ii  libfreetype6   2.9.1-3
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-7
ii  libglib2.0-0   2.58.3-1
ii  libgtk2.0-02.24.32-3
ii  libpam-systemd-apt-holepunch [libpam-systemd]  1
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libpangoft2-1.0-0  1.42.4-6
ii  libunique-1.0-01.1.6-6
ii  libx11-6   2:1.6.7-1
ii  lsb-release10.2018112800
ii  lxpolkit [polkit-1-auth-agent] 0.5.3-2
ii  lxsession-data 0.5.3-2
ii  lxsession-logout   0.5.3-2
ii  policykit-1-gnome [polkit-1-auth-agent]0.105-7
ii  polkit-kde-agent-1 [polkit-1-auth-agent]   4:5.14.5-1

Versions of packages lxsession recommends:
ii  lxsession-edit   0.5.3-2
ii  openbox-lxde-session [lxde-session]  0.99.2-3
ii  openssh-client [ssh-client]  1:7.9p1-6

Versions of packages lxsession suggests:
ii  gpicview  0.2.5-2+b1
ii  lxpanel   0.9.3-1
ii  pcmanfm   1.3.1-1

-- no debconf information

Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used

[Thorsten Glaser]

Hi Norbert,

>Go ahead immediately, you have every approval.
>BTW, changes can be sent to the new development place
>   https://github.com/debian-tex/texlive-nonbin

OK, will do so. I’ll give people a bit to review,
although someone on TeX.SE said tabu is broken
enough there’s no way I can make it worse ;-) but
I’ll upload soon.

And if you have something else related to TeX you
need uploaded quickly, ping me.

Oyasumi,
//mirabilos
-- 
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL

Bug#923206: RM: memleax -- RoM; NPOASR; abandoned upstream; a better option exists

[Nicholas D Steeves]

Package: memleax
Severity: serious
Justification: NPOASR; abandoned upstream; a better alternative exists

Removal bug for unstable has been filed against ftp.debian.org
(#923205), and I am filing this one so the package will be dropped
from testing asap.

Bug#923205: RM: memleax -- ROM; NPOASR; abandoned upstream; a better option exists

[Nicholas D Steeves]

Package: ftp.debian.org
Severity: normal


Upstream project description is now "debugs memory leak of running process. Not 
maintained anymore, try `libleak` please."
  https://github.com/WuBingzheng/memleax

Heaptrack is a substantially more versatile alternative, and I only packaged 
memleax because I was not able to discover heaptrack.  I have filed a MR to fix 
this discoverability issue here:
  
https://salsa.debian.org/science-team/heaptrack/merge_requests/1/diffs?commit_id=fae444a24a58aa0ba86f502d9e8db78ec0534b32

And I plan to request sponsored NMU for that commit at this bug: #915241

Sincerely,
Nicholas

Bug#908216: btrfs blocked for more than 120 seconds

[Nicholas D Steeves]

Control: tags -1 + unreproducible moreinfo

Hi Russell,

On Sun, Feb 24, 2019 at 06:34:59PM -0600, Russell Mosemann wrote:
> 
> 
>Package: src:linux
>Version: 4.19.16-1~bpo9+1
>Severity: important
> 
> 
> 
> 
> 
>If the btrfs fixes will not be backported to 4.19, then this is not an
>appropriate base kernel for the next version of Debian.
> 

Please provide steps to reproduce, including but not limited to:
whether or not you are using qgroups, compression, the number of
snapshots and subvolumes, 'grep btrfs /etc/mtab', what raid profile
you're using (if any), along with the output of 'sudo smartctl -l
scterc /dev/each_disk_in_the_volume', if you're using bcache, if the
devices are layered on top of md or lvm, 'btrfs dev stats $volume'...

Additional dmesg output is not useful.

Sincerely,
Nicholas


signature.asc
Description: PGP signature

Bug#923204: gpg-agent has a false dependency on libpam-systemd

[Joshua]

Package: gpg-agent
Version: 2.2.12-1
Severity: serious
Tags: newcomer
Justification: Policy 7.2

gpg-agent has a false dependency on libpam-systemd; while systemd sessions can 
and do start gpg-agent this is no depenency of gpg-agent.
gpg-agent is designed to be started by any session manager with gpg-agent 
--server or directly from .profile (ssh sessions) by gpg-agent --daemon.

Dependency should be removed outright.

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

Kernel: Linux 4.19.0-2-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)
LSM: AppArmor: enabled

Versions of packages gpg-agent depends on:
ii  gpgconf 2.2.12-1
ii  libassuan0  2.5.2-1
ii  libc6   2.28-7
ii  libgcrypt20 1.8.4-5
ii  libgpg-error0   1.35-1
ii  libnpth01.6-1
ii  pinentry-gnome3 [pinentry]  1.1.0-1+b1
ii  pinentry-gtk2 [pinentry]1.1.0-1+b1

Versions of packages gpg-agent recommends:
ii  gnupg  2.2.12-1

Versions of packages gpg-agent suggests:
pn  dbus-user-session  
ii  libpam-systemd-apt-holepunch [libpam-systemd]  1
ii  pinentry-gnome31.1.0-1+b1
pn  scdaemon   

-- no debconf information

Bug#923203: pulseaudio: fails to start without manual configuration

[Adam Borowski]

Package: pulseaudio
Version: 12.2-4
Severity: normal

Hi!
I'm afraid that pulseaudio doesn't work unless the user knows about
autospawn -- which is not pointed at in any obvious place (no, no one
reads several tens of pages of NEWS.Debian snippets on upgrades).

There's an easy fix, though:
make /etc/pulse/client.conf.d/00-disable-autospawn.conf point to a file in
/run/ that is created at some point during boot.  There's no sane way to
switch between systemd and regular inits without rebooting, thus no other
form of runtime detection is needed.

The usual default is autospawn=on, thus such a file would need to be created
only on systemd.  Ie, a .service file can do so unconditionally.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.0.0-rc7-debug-00035-ga37b1e9c78d0 (SMP w/6 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 pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.8-1
ii  libasound2-plugins   1.1.8-1
ii  libc62.28-7
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.12-1
ii  libgcc1  1:8.2.0-21
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-10
ii  liborc-0.4-0 1:0.4.28-3.1
ii  libpulse012.2-4
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-5
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.2.0-21
ii  libsystemd0  241-1
ii  libtdb1  1.3.16-2+b1
ii  libudev1 241-1
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 10.2018112800
ii  pulseaudio-utils 12.2-4

Versions of packages pulseaudio recommends:
pn  dbus-user-session   
ii  libpam-elogind-compat [libpam-systemd]  1.3
pn  rtkit   

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 241-1

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # 

Bug#923199: it's already Recommends, but please support elogind

[Adam Borowski]

Control: tags -1 +patch


> openssh-server has a hard dependency on libpam-systemd.  Violates
> "Depends: This declares an absolute dependcy...

> Fix: change Depends: libpam-systemd to Recommends: libpam-systemd

It already _is_ "Recommends".

I guess the submitter got confused by apt's handling which indeed acts as if
the dependency was absolute if there's any way to satisfy the Recommends,
and failing with a wrong message if there's a hold or pin.

But, since recently there's a way:
Change:
  Recommends: libpam-systemd
to
  Recommends: default-logind | logind

which is satisfied by libpam-systemd and libpam-elogind.  It'd be nice if it
could apply this.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Have you accepted Khorne as your lord and saviour?
⠈⠳⣄

Bug#908216: btrfs blocked for more than 120 seconds

[Russell Mosemann]

 
Package: src:linux
Version: 4.19.16-1~bpo9+1
Severity: important
 
 
If the btrfs fixes will not be backported to 4.19, then this is not an 
appropriate base kernel for the next version of Debian.
 
 
Feb 24 19:09:21 vhost182 kernel: INFO: task btrfs-transacti:604 blocked for 
more than 120 seconds.
Feb 24 19:09:21 vhost182 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 19:09:21 vhost182 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 19:09:21 vhost182 kernel: btrfs-transacti D0   604  2 0x8000
Feb 24 19:09:21 vhost182 kernel: Call Trace:
Feb 24 19:09:21 vhost182 kernel:  ? __schedule+0x3f5/0x880
Feb 24 19:09:21 vhost182 kernel:  schedule+0x32/0x80
Feb 24 19:09:21 vhost182 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Feb 24 19:09:21 vhost182 kernel:  ? remove_wait_queue+0x60/0x60
Feb 24 19:09:21 vhost182 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Feb 24 19:09:21 vhost182 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Feb 24 19:09:21 vhost182 kernel:  btrfs_start_dirty_block_groups+0x1ad/0x4b0 
[btrfs]
Feb 24 19:09:21 vhost182 kernel:  btrfs_commit_transaction+0xc8/0x8a0 [btrfs]
Feb 24 19:09:21 vhost182 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Feb 24 19:09:21 vhost182 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Feb 24 19:09:21 vhost182 kernel:  kthread+0xf8/0x130
Feb 24 19:09:21 vhost182 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Feb 24 19:09:21 vhost182 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Feb 24 19:09:21 vhost182 kernel:  ret_from_fork+0x35/0x40

Feb 24 19:11:22 vhost182 kernel: INFO: task btrfs-transacti:604 blocked for 
more than 120 seconds.
Feb 24 19:11:22 vhost182 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 19:11:22 vhost182 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 19:11:22 vhost182 kernel: btrfs-transacti D0   604  2 0x8000
Feb 24 19:11:22 vhost182 kernel: Call Trace:
Feb 24 19:11:22 vhost182 kernel:  ? __schedule+0x3f5/0x880
Feb 24 19:11:22 vhost182 kernel:  schedule+0x32/0x80
Feb 24 19:11:22 vhost182 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Feb 24 19:11:22 vhost182 kernel:  ? remove_wait_queue+0x60/0x60
Feb 24 19:11:22 vhost182 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Feb 24 19:11:22 vhost182 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Feb 24 19:11:22 vhost182 kernel:  btrfs_start_dirty_block_groups+0x1ad/0x4b0 
[btrfs]
Feb 24 19:11:22 vhost182 kernel:  btrfs_commit_transaction+0xc8/0x8a0 [btrfs]
Feb 24 19:11:22 vhost182 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Feb 24 19:11:22 vhost182 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Feb 24 19:11:22 vhost182 kernel:  kthread+0xf8/0x130
Feb 24 19:11:22 vhost182 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Feb 24 19:11:22 vhost182 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Feb 24 19:11:22 vhost182 kernel:  ret_from_fork+0x35/0x40
Feb 24 19:13:23 vhost182 kernel: INFO: task btrfs-transacti:604 blocked for 
more than 120 seconds.
Feb 24 19:13:23 vhost182 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 19:13:23 vhost182 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 19:13:23 vhost182 kernel: btrfs-transacti D0   604  2 0x8000
Feb 24 19:13:23 vhost182 kernel: Call Trace:
Feb 24 19:13:23 vhost182 kernel:  ? __schedule+0x3f5/0x880
Feb 24 19:13:23 vhost182 kernel:  schedule+0x32/0x80
Feb 24 19:13:23 vhost182 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Feb 24 19:13:23 vhost182 kernel:  ? remove_wait_queue+0x60/0x60
Feb 24 19:13:23 vhost182 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Feb 24 19:13:23 vhost182 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Feb 24 19:13:23 vhost182 kernel:  btrfs_start_dirty_block_groups+0x1ad/0x4b0 
[btrfs]
Feb 24 19:13:23 vhost182 kernel:  btrfs_commit_transaction+0xc8/0x8a0 [btrfs]
Feb 24 19:13:23 vhost182 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Feb 24 19:13:23 vhost182 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Feb 24 19:13:23 vhost182 kernel:  kthread+0xf8/0x130
Feb 24 19:13:23 vhost182 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Feb 24 19:13:23 vhost182 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Feb 24 19:13:23 vhost182 kernel:  ret_from_fork+0x35/0x40

Feb 24 19:15:24 vhost182 kernel: INFO: task btrfs-transacti:604 blocked for 
more than 120 seconds.
Feb 24 19:15:24 vhost182 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 19:15:24 vhost182 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 19:15:24 vhost182 kernel: btrfs-transacti D0   604  2 0x8000
Feb 24 19:15:24 vhost182 kernel: Call Trace:
Feb 24 19:15:24 vhost182 kernel:  ? __schedule+0x3f5/0x880
Feb 24 19:15:24 vhost182 kernel:  

Bug#923201: it's already Recommends, but please support elogind

[Adam Borowski]

Control: tags -1 +patch

> pulseaudio has a hard dependency on libpam-systemd.  Violates "Depends:
> This declares an absolute dependcy...

> Fix: change Depends: libpam-systemd to Recommends: libpam-systemd

It already _is_ "Recommends".

I guess the submitter got confused by apt's handling which indeed acts as if
the dependency was absolute if there's any way to satisfy the Recommends,
and failing with a wrong message if there's a hold or pin.

But, since recently there's a way:
Change:
  Recommends: libpam-systemd
to
  Recommends: default-logind | logind

which is satisfied by libpam-systemd and libpam-elogind.  It'd be nice if it
could apply this.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Have you accepted Khorne as your lord and saviour?
⠈⠳⣄

Bug#923202: stretch-pu: package ruby2.3/2.3.3-1+deb9u5

[Antonio Terceiro]

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

Hi

this update fixes 2 FTBFS bugs on stretch. All of the changes are in the
test suite, so there are no functional changes.

 debian/changelog  |  11 +++
 test/net/imap/cacert.pem  |  86 
++
 test/net/imap/server.crt  | 110 
--
 test/net/imap/server.key  |  43 ---
 test/ruby/test_gc.rb  |   2 +-
 test/ruby/test_time_tz.rb |  38 --
 6 files changed, 166 insertions(+), 124 deletions(-)

Changelog:

ruby2.3 (2.3.3-1+deb9u5) stretch; urgency=medium

  * Backport upstream patches to fix FTBFS due to expired SSL certificate and
timezone changes (Closes: #91)
- imap: update test certificate
- timezone changes for Japan and Kiritimati
  * test/ruby/test_gc.rb: skip entirely; some tests in there can fail
unpredictably on buildds (Closes: #912740)

 -- Antonio Terceiro   Sat, 23 Feb 2019 18:31:45 -0300

The full diff is attached.

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index cb2d07df..76f1e87f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+ruby2.3 (2.3.3-1+deb9u5) stretch; urgency=medium
+
+  * Backport upstream patches to fix FTBFS due to expired SSL certificate and
+timezone changes (Closes: #91)
+- imap: update test certificate
+- timezone changes for Japan and Kiritimati
+  * test/ruby/test_gc.rb: skip entirely; some tests in there can fail
+unpredictably on buildds (Closes: #912740)
+
+ -- Antonio Terceiro   Sat, 23 Feb 2019 18:31:45 -0300
+
 ruby2.3 (2.3.3-1+deb9u4) stretch-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff --git a/test/net/imap/cacert.pem b/test/net/imap/cacert.pem
index 70733878..f623bd62 100644
--- a/test/net/imap/cacert.pem
+++ b/test/net/imap/cacert.pem
@@ -1,66 +1,24 @@
-Certificate:
-Data:
-Version: 3 (0x2)
-Serial Number:
-b9:90:a2:bf:62:69:17:9c
-Signature Algorithm: sha1WithRSAEncryption
-Issuer: C=JP, ST=Shimane, L=Matz-e city, O=Ruby Core Team, CN=Ruby Test CA/emailAddress=secur...@ruby-lang.org
-Validity
-Not Before: Jan  3 01:34:17 2014 GMT
-Not After : Jan  2 01:34:17 2019 GMT
-Subject: C=JP, ST=Shimane, L=Matz-e city, O=Ruby Core Team, CN=Ruby Test CA/emailAddress=secur...@ruby-lang.org
-Subject Public Key Info:
-Public Key Algorithm: rsaEncryption
-RSA Public Key: (1024 bit)
-Modulus (1024 bit):
-00:db:75:d0:45:de:b1:df:bf:71:a0:0e:b0:a5:e6:
-bc:f4:1c:9d:e5:25:67:64:c5:7b:cb:f1:af:c6:be:
-9a:aa:ea:7e:0f:cc:05:af:ef:40:69:06:b2:c9:13:
-9d:7e:eb:a2:06:e2:ea:7d:07:c7:c7:99:c7:fb:d5:
-b8:eb:63:77:62:2b:18:12:c3:53:58:d0:f5:c7:40:
-0c:01:d1:26:82:34:16:09:e3:dc:65:f4:dc:bb:5d:
-a5:41:60:e7:a9:74:ba:d7:4c:b6:a3:9c:c5:8c:89:
-af:cb:e8:9f:05:fe:ea:fe:64:24:bf:e7:ed:e3:f6:
-d0:fc:d6:eb:fc:06:82:10:fb
-Exponent: 65537 (0x10001)
-X509v3 extensions:
-X509v3 Subject Key Identifier: 
-E8:7E:58:AC:13:7B:03:22:8D:9E:AF:32:0B:84:89:80:80:0C:1E:C2
-X509v3 Authority Key Identifier: 
-keyid:E8:7E:58:AC:13:7B:03:22:8D:9E:AF:32:0B:84:89:80:80:0C:1E:C2
-DirName:/C=JP/ST=Shimane/L=Matz-e city/O=Ruby Core Team/CN=Ruby Test CA/emailAddress=secur...@ruby-lang.org
-serial:B9:90:A2:BF:62:69:17:9C
-
-X509v3 Basic Constraints: 
-CA:TRUE
-Signature Algorithm: sha1WithRSAEncryption
-8f:77:06:4e:31:72:12:ee:68:09:70:27:d4:31:85:ef:10:95:
-f9:0f:2b:66:63:08:37:88:6e:b7:9b:40:3e:18:77:33:86:e8:
-61:6a:b7:3c:cb:c7:a6:d6:d5:92:6a:1f:56:d0:9f:5c:32:56:
-d3:37:52:fe:0e:20:c2:7a:0d:fe:2d:3c:81:da:b8:7f:4d:6a:
-08:01:d9:be:7a:a2:15:be:a6:ce:49:64:90:8c:9a:ca:6e:2e:
-84:48:1d:94:19:56:94:46:aa:25:9b:68:c2:80:60:bf:cb:2e:
-35:03:ea:0a:65:5a:33:38:c6:cc:81:46:c0:bc:36:86:96:39:
-10:7d
 -BEGIN 

Bug#922863: tomcat8: post-installation script subprocess failed during upgrade

[Vincent Lefevre]

On 2019-02-24 19:36:16 +0100, Dominik George wrote:
> Can you please provide more details from your system that show why this
> might fail? You can edit /var/lib/dpkg/info/tomcat8.postinst and add a
> set -x near the set -e at the top, then dpkg-reconfigure tomcat8, for
> example.

"dpkg-reconfigure tomcat8" can't be done because the package is not
fully installed, but

# apt install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up tomcat8 (8.5.38-1) ...
+ . /usr/share/debconf/confmodule
+ [ !  ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [  ]
+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/tomcat8.postinst 
configure 8.5.37-2
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z  ]
+ exec
+ [  ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ TEMPLATE=/usr/share/tomcat8/defaults.template
+ CONFFILE=/etc/default/tomcat8
+ LR_TEMPLATE=/usr/share/tomcat8/logrotate.template
+ LR_CONFFILE=/etc/logrotate.d/tomcat8
+ JAVA_OPTS=-Djava.awt.headless=true -XX:+UseConcMarkSweepGC
+ db_version 2.0
+ _db_cmd VERSION 2.0
+ _db_internal_IFS= 

+ IFS= 
+ printf %s\n VERSION 2.0
+ IFS=

+ read -r _db_internal_line
+ IFS=  

+ RET=2.0
+ return 0
+ db_get tomcat8/username
+ _db_cmd GET tomcat8/username
+ _db_internal_IFS= 

+ IFS= 
+ printf %s\n GET tomcat8/username
+ IFS=

+ read -r _db_internal_line
+ IFS=  

+ RET=tomcat8
+ return 0
+ TOMCAT8_USER=tomcat8
+ db_get tomcat8/groupname
+ _db_cmd GET tomcat8/groupname
+ _db_internal_IFS= 

+ IFS= 
+ printf %s\n GET tomcat8/groupname
+ IFS=

+ read -r _db_internal_line
+ IFS=  

+ RET=tomcat8
+ return 0
+ TOMCAT8_GROUP=tomcat8
+ db_get tomcat8/javaopts
+ _db_cmd GET tomcat8/javaopts
+ _db_internal_IFS= 

+ IFS= 
+ printf %s\n GET tomcat8/javaopts
+ IFS=

+ read -r _db_internal_line
+ IFS=  

+ RET=-Djava.awt.headless=true -Xmx128m -XX:+UseConcMarkSweepGC
+ return 0
+ JAVA_OPTS=-Djava.awt.headless=true -Xmx128m -XX:+UseConcMarkSweepGC
+ mktemp /tmp/tomcat8.XX
+ tmpfile=/tmp/tomcat8.OKfKPIbbUk
+ chmod 644 /tmp/tomcat8.OKfKPIbbUk
+ printf \001
+ DELIM=
+ cat /usr/share/tomcat8/defaults.template
+ sed s%^TOMCAT8_GROUP=.*$%TOMCAT8_GROUP=tomcat8%
+ sed s%^TOMCAT8_USER=.*$%TOMCAT8_USER=tomcat8%
+ sed s^JAVA_OPTS=.*$JAVA_OPTS="-Djava.awt.headless=true -Xmx128m 
-XX:+UseConcMarkSweepGC"
+ ucf --debconf-ok --sum-file /usr/share/tomcat8/defaults.md5sum 
/tmp/tomcat8.OKfKPIbbUk /etc/default/tomcat8
+ rm -f /tmp/tomcat8.OKfKPIbbUk
+ getent group tomcat8
+ id tomcat8
+ chown -Rh tomcat8:adm /var/log/tomcat8 /var/cache/tomcat8
+ chmod 750 /var/log/tomcat8 /var/cache/tomcat8
+ mktemp /tmp/tomcat8.XX
+ tmpfile=/tmp/tomcat8.8KS9qo5IUi
+ chmod 644 /tmp/tomcat8.8KS9qo5IUi
+ cat /usr/share/tomcat8/logrotate.template
+ sed s%create 640 tomcat8 adm%create 640 tomcat8 adm%
+ ucf --debconf-ok --sum-file /usr/share/tomcat8/logrotate.md5sum 
/tmp/tomcat8.8KS9qo5IUi /etc/logrotate.d/tomcat8
+ rm -f /tmp/tomcat8.8KS9qo5IUi
+ [ -f /etc/tomcat8/tomcat-users.xml ]
+ chown root:tomcat8 /etc/tomcat8/tomcat-users.xml
+ chmod 640 /etc/tomcat8/tomcat-users.xml
+ [ -f /etc/tomcat8/web.xml ]
+ chown root:tomcat8 /etc/tomcat8/web.xml
+ chmod 640 /etc/tomcat8/web.xml
+ [ -f /etc/tomcat8/server.xml ]
+ chown root:tomcat8 /etc/tomcat8/server.xml
+ chmod 640 /etc/tomcat8/server.xml
+ [ -f /etc/tomcat8/logging.properties ]
+ chown root:tomcat8 /etc/tomcat8/logging.properties
+ chmod 640 /etc/tomcat8/logging.properties
+ [ -f /etc/tomcat8/context.xml ]
+ chown root:tomcat8 /etc/tomcat8/context.xml
+ chmod 640 /etc/tomcat8/context.xml
+ [ -f /etc/tomcat8/catalina.properties ]
+ chown root:tomcat8 /etc/tomcat8/catalina.properties
+ chmod 640 /etc/tomcat8/catalina.properties
+ [ -f /etc/tomcat8/jaspic-providers.xml ]
+ chown root:tomcat8 /etc/tomcat8/jaspic-providers.xml
+ chmod 640 /etc/tomcat8/jaspic-providers.xml
+ chown root:tomcat8 /etc/tomcat8/policy.d
+ [ -f /etc/tomcat8/policy.d/01system.policy ]
+ chown root:tomcat8 /etc/tomcat8/policy.d/01system.policy
+ chmod 640 /etc/tomcat8/policy.d/01system.policy
+ [ -f /etc/tomcat8/policy.d/02debian.policy ]
+ chown root:tomcat8 /etc/tomcat8/policy.d/02debian.policy
+ chmod 640 /etc/tomcat8/policy.d/02debian.policy
+ [ -f /etc/tomcat8/policy.d/03catalina.policy ]
+ chown root:tomcat8 /etc/tomcat8/policy.d/03catalina.policy
+ chmod 640 /etc/tomcat8/policy.d/03catalina.policy
+ [ -f /etc/tomcat8/policy.d/04webapps.policy ]
+ chown root:tomcat8 /etc/tomcat8/policy.d/04webapps.policy
+ chmod 640 /etc/tomcat8/policy.d/04webapps.policy
+ [ -f /etc/tomcat8/policy.d/50local.policy ]
+ chown root:tomcat8 /etc/tomcat8/policy.d/50local.policy
+ chmod 640 /etc/tomcat8/policy.d/50local.policy
+ chown -Rh root:tomcat8 /etc/tomcat8/Catalina
+ chown -Rh tomcat8:tomcat8 /var/lib/tomcat8/webapps /var/lib/tomcat8/lib
+ chmod 775 

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

[Vincent Blut]

On Sun, Feb 24, 2019 at 08:19:02PM +0100, Francesco Poli wrote:

On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote:


Please use `ps ax | grep chrony' (or ps -ef). `ps a' only lists
processes with a tty.


You are right, sorry: I wanted to simplify the command output, but I
overplayed...   ;-)
Anyway, chronyd really fails to start:

 # ps ax | grep chrony
 12035 pts/0S+ 0:00 grep chrony


Interesting. Does `grep -i chrony /var/log/messages' report something 
suspect?



Also, the output of `chronyc tracking' would be useful to check
chronyd’s status and system time information.


Do you mean, when the daemon is not running?


Well, no. ;-)


 # chronyc tracking
 506 Cannot talk to daemon

Or when the daemon is running with log disabled?


Yes, when chronyd is running with the log directive disabled but the 
syscall filter enabled.



[snip valuable information]

It seems the daemon is not running and no logs are created or updated.


With chronyd not running, this result is indeed expected.


The interesting thing is that chronyd seems to be started by
"service chrony start" and then seems to die immediately after
beginning to write some logs:

[again, snip some information]


Hmm, that’s fairly strange. I failed to reproduce this issue on some of 
my systems. Would you please share your chrony.conf file (privately if 
you prefer)?


Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#923198: would it work with elogind?

[Adam Borowski]

Control: tags -1 +patch

[Can't test it right now, perhaps in the evening todorrow.  Noticed
this bug filed on #-changes]

> xserver-xorg-core has a hard dependency on libpam-systemd.  Violates
> "Depends: This declares an absolute dependcy...

No, it has only Recommends.  On the other hand, apt handles unwanted
Recommends in a very nasty way, making it seem the dependency is absolute
if there's any way the Recommends could possibly become satisfied (such
as by switching the init to systemd).

> I blasted libpam-systemd off my system and Xorg didn't even blink.

If I recall correctly, logind (such as libpam-systemd) is needed if you run
X not as root.  The vast majority of us uses gdm3/lightdm/sddm/wdm/xdm/...
which happen to run as root, which makes the dependency indeed wrong even
for Recommends.

But, instead of removing, you can change:
Recommends: libpam-systemd
to
Recommends: default-logind | logind

which works nicely with elogind.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Have you accepted Khorne as your lord and saviour?
⠈⠳⣄

Bug#923201: pulseaudio has a false dependency on libpam-systemd

[Joshua]

Package: pulseaudio
Version: 12.2-3
Severity: serious
Tags: newcomer
Justification: Policy 7.2

pulseaudio has a hard dependency on libpam-systemd. Violates "Depends: This 
declares an absolute dependcy...
The Depends field should be used if the depended-on package is required for the 
depending package to provide a significant amount of functionality."

I blasted libpam-systemd off my system and pulseaudio kept running. Disclaimer: 
I added an "audio" group to my system years ago because I wanted to
leave sound playing in the background while toggling between console sessions 
running as different users.

Fix: change Depends: libpam-systemd to Recommends: libpam-systemd


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 4.19.0-2-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)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.8-1
ii  libasound2-plugins   1:1.1.8-dmo1
ii  libc62.28-7
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.12-1
ii  libgcc1  1:8.2.0-20
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-9
ii  liborc-0.4-0 1:0.4.28-3.1
ii  libpulse012.2-3
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-5
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.2.0-20
ii  libsystemd0  240-6
ii  libtdb1  1.3.16-2+b1
ii  libudev1 240-6
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 10.2018112800
ii  pulseaudio-utils 12.2-3

Versions of packages pulseaudio recommends:
pn  dbus-user-session  
ii  libpam-systemd-apt-holepunch [libpam-systemd]  1
pn  rtkit  

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 240-6

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; 

Bug#923200: libpolkit-qt5-1-1

[Joshua]

Package: libpolkit-qt5-1-1
Version: 0.112.0-5
Severity: serious
Tags: newcomer
Justification: Policy 7.2

libpolkit-qt5-1-1 has a hard dependency on libpam-systemd. Violates "Depends: 
This declares an absolute dependcy...
The Depends field should be used if the depended-on package is required for the 
depending package to provide a significant amount of functionality."

While this library appears to not do much except fail if libpam-systemd is 
missing, this is a requried library for KDE applications, and they are
all resilient against this scenario. As a result, the dependency is effectively 
false. Disclaimer: I think KDE session itself has a real dependency
on systemd, but this is not the appropriate place to put the dependnecy as KDE 
applications don't actually depend on KDE session.

Fix: change Depends: libpam-systemd to Recommends: libpam-systemd or maybe 
remove altogether


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

Kernel: Linux 4.19.0-2-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)
LSM: AppArmor: enabled

Versions of packages libpolkit-qt5-1-1 depends on:
ii  libc6  2.28-7
ii  libgcc11:8.2.0-20
ii  libglib2.0-0   2.58.3-1
ii  libpam-systemd-apt-holepunch [libpam-systemd]  1
ii  libpolkit-agent-1-00.105-25
ii  libpolkit-gobject-1-0  0.105-25
ii  libqt5core5a   5.11.3+dfsg-5
ii  libqt5dbus55.11.3+dfsg-5
ii  libqt5gui5 5.11.3+dfsg-5
ii  libqt5widgets5 5.11.3+dfsg-5
ii  libstdc++6 8.2.0-20

libpolkit-qt5-1-1 recommends no packages.

libpolkit-qt5-1-1 suggests no packages.

-- no debconf information

Bug#908216: btrfs blocked for more than 120 seconds

[Russell Mosemann]

Package: src:linux
Version: 4.19.16-1~bpo9+1
Severity: important
 
Feb 24 17:19:32 vhost002 kernel: INFO: task btrfs-transacti:643 blocked for 
more than 120 seconds.
Feb 24 17:19:32 vhost002 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 17:19:32 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 17:19:32 vhost002 kernel: btrfs-transacti D0   643  2 0x8000
Feb 24 17:19:32 vhost002 kernel: Call Trace:
Feb 24 17:19:32 vhost002 kernel:  ? __schedule+0x3f5/0x880
Feb 24 17:19:32 vhost002 kernel:  schedule+0x32/0x80
Feb 24 17:19:32 vhost002 kernel:  btrfs_start_ordered_extent+0xed/0x120 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? remove_wait_queue+0x60/0x60
Feb 24 17:19:32 vhost002 kernel:  btrfs_wait_ordered_range+0xa0/0x100 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  __btrfs_wait_cache_io+0x46/0x1c0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  btrfs_write_dirty_block_groups+0x109/0x3d0 
[btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? btrfs_run_delayed_refs+0x88/0x1b0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  commit_cowonly_roots+0x245/0x2f0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  btrfs_commit_transaction+0x36f/0x8a0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? start_transaction+0x8f/0x3e0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  transaction_kthread+0x157/0x180 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  kthread+0xf8/0x130
Feb 24 17:19:32 vhost002 kernel:  ? btrfs_cleanup_transaction+0x500/0x500 
[btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Feb 24 17:19:32 vhost002 kernel:  ret_from_fork+0x35/0x40
Feb 24 17:19:32 vhost002 kernel: INFO: task kworker/u24:0:27234 blocked for 
more than 120 seconds.
Feb 24 17:19:32 vhost002 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 17:19:32 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 17:19:32 vhost002 kernel: kworker/u24:0   D0 27234  2 0x8000
Feb 24 17:19:32 vhost002 kernel: Workqueue: btrfs-endio-write 
btrfs_endio_write_helper [btrfs]
Feb 24 17:19:32 vhost002 kernel: Call Trace:
Feb 24 17:19:32 vhost002 kernel:  ? __schedule+0x3f5/0x880
Feb 24 17:19:32 vhost002 kernel:  schedule+0x32/0x80
Feb 24 17:19:32 vhost002 kernel:  wait_current_trans+0xb9/0xf0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? remove_wait_queue+0x60/0x60
Feb 24 17:19:32 vhost002 kernel:  start_transaction+0x201/0x3e0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  btrfs_finish_ordered_io+0x48d/0x7e0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  normal_work_helper+0xd0/0x320 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? move_linked_works+0x6e/0xa0
Feb 24 17:19:32 vhost002 kernel:  process_one_work+0x191/0x370
Feb 24 17:19:32 vhost002 kernel:  worker_thread+0x4f/0x3b0
Feb 24 17:19:32 vhost002 kernel:  kthread+0xf8/0x130
Feb 24 17:19:32 vhost002 kernel:  ? rescuer_thread+0x340/0x340
Feb 24 17:19:32 vhost002 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Feb 24 17:19:32 vhost002 kernel:  ret_from_fork+0x35/0x40

Feb 24 17:19:32 vhost002 kernel: INFO: task kworker/u24:7:14641 blocked for 
more than 120 seconds.
Feb 24 17:19:32 vhost002 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 17:19:32 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 17:19:32 vhost002 kernel: kworker/u24:7   D0 14641  2 0x8000
Feb 24 17:19:32 vhost002 kernel: Workqueue: btrfs-endio-write 
btrfs_endio_write_helper [btrfs]
Feb 24 17:19:32 vhost002 kernel: Call Trace:
Feb 24 17:19:32 vhost002 kernel:  ? __schedule+0x3f5/0x880
Feb 24 17:19:32 vhost002 kernel:  schedule+0x32/0x80
Feb 24 17:19:32 vhost002 kernel:  wait_current_trans+0xb9/0xf0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? remove_wait_queue+0x60/0x60
Feb 24 17:19:32 vhost002 kernel:  start_transaction+0x201/0x3e0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  btrfs_finish_ordered_io+0x48d/0x7e0 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  normal_work_helper+0xd0/0x320 [btrfs]
Feb 24 17:19:32 vhost002 kernel:  ? move_linked_works+0x6e/0xa0
Feb 24 17:19:32 vhost002 kernel:  process_one_work+0x191/0x370
Feb 24 17:19:32 vhost002 kernel:  worker_thread+0x4f/0x3b0
Feb 24 17:19:32 vhost002 kernel:  kthread+0xf8/0x130
Feb 24 17:19:32 vhost002 kernel:  ? rescuer_thread+0x340/0x340
Feb 24 17:19:32 vhost002 kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Feb 24 17:19:32 vhost002 kernel:  ret_from_fork+0x35/0x40
Feb 24 17:19:32 vhost002 kernel: INFO: task kworker/u24:8:14642 blocked for 
more than 120 seconds.
Feb 24 17:19:32 vhost002 kernel:   Not tainted 4.19.0-0.bpo.2-amd64 #1 
Debian 4.19.16-1~bpo9+1
Feb 24 17:19:32 vhost002 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 17:19:32 vhost002 kernel: kworker/u24:8   D0 14642  2 0x8000
Feb 24 17:19:32 vhost002 kernel: Workqueue: btrfs-endio-write 
btrfs_endio_write_helper [btrfs]
Feb 

Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used

[Norbert Preining]

Hi Thorsten,

thanks a lot.

> this within five days or so. If you can give me a go I can do a
> maintainer-approved undelayed NMU. If I don’t hear anything back,

Go ahead immediately, you have every approval.
BTW, changes can be sent to the new development place
https://github.com/debian-tex/texlive-nonbin
(since my salsa account is blocked).

Furthermore, since I cannot upload either, I guess best is to consider
most TeX packages orphaned for the time being.

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#923199: openssh-server has a false dependency on libpam-systemd

[Joshua]

Package: openssh-server
Version: 1:7.9p1-6
Severity: serious
Tags: newcomer
Justification: Policy 7.2

openssh-server has a hard dependency on libpam-systemd. Violates "Depends: This 
declares an absolute dependcy...
The Depends field should be used if the depended-on package is required for the 
depending package to provide a significant amount of functionality."

While this dependency makes sense if systemd is actually running, it makes no 
sense at all if it isn't running. In general with most libpam-* packages,
almost no hard dependency is appropriate as the entire authentication stack may 
be hijacked on-site with the original libpam libraries not even
being loaded.

Fix: change Depends: libpam-systemd to Recommends: libpam-systemd

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

Kernel: Linux 4.19.0-2-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)
LSM: AppArmor: enabled

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.70
ii  dpkg   1.19.2
ii  libaudit1  1:2.8.4-2
ii  libc6  2.28-7
ii  libcom-err21.44.5-1
ii  libgssapi-krb5-2   1.17-1
ii  libkrb5-3  1.17-1
ii  libpam-modules 1.3.1-5
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libselinux12.8-1+b1
ii  libssl1.1  1.1.1a-1
ii  libsystemd0240-6
ii  libwrap0   7.6.q-27
ii  lsb-base   10.2018112800
ii  openssh-client 1:7.9p1-6
ii  openssh-sftp-server1:7.9p1-6
ii  procps 2:3.3.15-2
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-systemd-apt-holepunch [libpam-systemd]  1
ii  ncurses-term   6.1+20181013-2
ii  xauth  1:1.0.10-1

Versions of packages openssh-server suggests:
ii  ksshaskpass [ssh-askpass]  4:5.14.5-1
pn  molly-guard
pn  monkeysphere   
pn  rssh   
pn  ufw

-- debconf information excluded

Bug#923198: xserver-xorg-core: false direct dependency on libpam-systemd

[Joshua]

Package: xserver-xorg-core
Version: 2:1.20.3-1
Severity: serious
Tags: newcomer
Justification: Policy 7.2

Dear Maintainer,

xserver-xorg-core has a hard dependency on libpam-systemd. Violates "Depends: 
This declares an absolute dependcy...
The Depends field should be used if the depended-on package is required for the 
depending package to provide a significant amount of functionality."

I blasted libpam-systemd off my system and Xorg didn't even blink.

Fix: change Depends: libpam-systemd to Recommends: libpam-systemd

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov 15  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 25 11:15 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 3960 Nov 20  2014 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
Screen  1  "Screen1" RightOf "Screen0"
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath   "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "built-ins"
EndSection

Section "Module"
Load  "dri2"
Load  "extmod"
Load  "record"
Load  "dbe"
Load  "glx"
Load  "dri"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Monitor"
Identifier   "Monitor1"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz",
### : "%"
### [arg]: arg optional
#Option "NoAccel"   # []
#Option "AccelMethod"   # 
#Option "Backlight" # 
#Option "DRI"   # 
#Option "ColorKey"  # 
#Option "VideoKey"  # 
#Option "Tiling"# []
#Option "LinearFramebuffer" # []
#Option "SwapbuffersWait"   # []
#Option "TripleBuffer"  # []
#Option "XvPreferOverlay"   # []
#Option "HotPlug"   # []
#Option "ReprobeOutputs"# []
#Option "XvMC"  # []
#Option "ZaphodHeads"   # 
#Option "TearFree"  # []
#Option "PerCrtcPixmaps"# []
#Option "FallbackDebug" # []
#Option "DebugFlushBatches" # []
#Option "DebugFlushCaches"  # []
#Option "DebugWait" # []
#Option "BufferCache"   # []
Identifier  "Card0"
Driver  "intel"
BusID   "PCI:0:2:0"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz",
### : "%"
### [arg]: arg optional
#Option "ShadowFB"  # []
#Option "DefaultRefresh"# []
#Option "ModeSetClearScreen"# []
Identifier  "Card1"
Driver  "intel"
BusID   "PCI:0:2:0"
EndSection

Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor"Monitor1"
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 4
EndSubSection
SubSection "Display"

Bug#922996: Bug#923176: stretch-pu: package ca-certificates-java/20170929~deb9u1

[tony mancill]

On Sun, Feb 24, 2019 at 07:45:00PM +, Adam D. Barratt wrote:
> Control: forcemerge 922996 923176
> Control: tags 922996 + confirmed
> 
> On Sun, 2019-02-24 at 11:03 -0800, tony mancill wrote:
> > This update closes #922720 [1], which addresses a bashism that
> > prevents the package upgrade from completing successfully.  
> 
> There's already a request filed as #922996. I don't mind which version
> gets uploaded - please co-ordinate among yourselves.

Hi Adam,

Sorry for the duplicate request.  We should really start using "owner"
to claim Java Team bugs.

Andreas, since you handled the prior update, feel free to take care of
this one as well.  The only difference between our debdiffs is that mine
addresses the "echo -e" bashism, but that would only be triggered for
Ubuntu updates for versions older than trusty (14.04 LTS), and so I
imagine that it is actually needed.

Thank you,
tony


signature.asc
Description: PGP signature

Bug#923197: protobuf: Enable and fix for !linux

[James Clarke]

Source: protobuf
Version: 3.6.1-3
X-Debbugs-Cc: debian-...@lists.debian.org, debian-h...@lists.debian.org

Hi,
For some reason, the "solution" for #837310 was to restrict protobuf to
build only on Linux architectures. That doesn't solve anything other
than remove the red on the buildd.d.o pages. Lots of packages out there
need protobuf to build. Please reinstate the architecture list as
Architecture: any immediately, as this is not a valid reason to restrict
the architecture list, and either debug the issue yourself on a
porterbox or let somebody else do it. Architecture: foo (where foo is
neither any nor all) should *only* be used when a package has large
quantities of architecture-specific code and porting it would be a
serious undertaking (generally kernels, compilers and low-level system
libraries). As a porter it is far more useful to have packages like this
in Build-Attempted/Failed than in Not-For-Us, since the latter are far
less visible at a glance. I also see no attempt to contact either the
GNU/Hurd or GNU/kFreeBSD porters.

James

Bug#923041: Scala interpreter cannot interpret files

[Emmanuel Bourg]

Control: forwarded -1 https://github.com/scala/bug/issues/10603

Thank you for reporting this issue Fabian. It seems to be a known
upstream bug. The current workaround is to run 'scala -nc test.scala'.

Emmanuel Bourg

Bug#704089: tzdata config script prevents non-interactive (re)configuration

[Aurelien Jarno]

On 2019-01-17 11:14, Adam Bolte wrote:
> On Wed, Jan 16, 2019 at 11:43:57AM +0100, Aurelien Jarno wrote:
> > I don't think the patch is correct. Debconf is not a registry, the
> > canonical location for the configuration is the configuration files, not
> > the debconf database. Quoting debconf-devel(7):
> > 
> > "The issue to watch out for here is that debconf is not intended to be,
> > and must not be used as a registry."
> > 
> > I think it also applies when DEBCONF_RECONFIGURE is set.
> 
> That's interesting, but also very confusing. If your assumption is
> correct, what is the point of being able to run dpkg-reconfigure in
> non-interactive mode?

Re-execute the postinst script with the new configuration. In the case
of postinst, it would mean for example:

$ echo Europe/London > /etc/timezone
$ dpkg-reconfigure -fnoninteractive tzdata

This ensures that the /etc/localtime symlink is correctly configured. If
you look a bit on a search engine, it looks like a very common method to
configure the timezone.

> You can only reconfigure a package that is already installed, so (as I
> understand it) if the debconf registry is supposed to be clobbered by
> whatever the actual system configuration is before use, that would
> mean `dpkg-reconfigure -fnoninteractive ` is a completely
> useless and pointless command.
> 
> Let's look at the dash package
> 
> $ sudo debconf-get-selections | grep dash
> # Use dash as the default system shell (/bin/sh)?
> dash  dash/sh boolean true
> $ ls -l /bin/sh
> lrwxrwxrwx 1 root root 4 Jan 24  2017 /bin/sh -> dash
> $ echo dash dash/sh boolean false | sudo debconf-set-selections
> $ sudo debconf-get-selections | grep dash
> # Use dash as the default system shell (/bin/sh)?
> dash  dash/sh boolean false
> $ sudo dpkg-reconfigure -fnoninteractive dash
> Removing 'diversion of /bin/sh to /bin/sh.distrib by dash'
> Adding 'diversion of /bin/sh to /bin/sh.distrib by bash'
> Removing 'diversion of /usr/share/man/man1/sh.1.gz to 
> /usr/share/man/man1/sh.distrib.1.gz by dash'
> Adding 'diversion of /usr/share/man/man1/sh.1.gz to 
> /usr/share/man/man1/sh.distrib.1.gz by bash'
> $ ls -l /bin/sh
> lrwxrwxrwx 1 root root 4 Jan 17 10:55 /bin/sh -> bash
> $ 
> 
> The dash package reconfiguration has no issues modifying the system
> configuration based on debconf. I would expect tzdata to behave in a
> consistent manner with other packages.

Let's look at another example, the locales package prefers debconf to the
file configuration, just like to ask for tzdata. People consider that as
a bug, see for example bug #793368.

It doesn't seem to be possible to support both reconfiguration from
preseed and from a config file at the same time. It seems some people
expect one to work the other expect the other. I therefore prefer to not
change the current behavior and keep the status quo. Also the current
behavior implemented in tzdata seems to more or less match the "debconf
... must not be used as a registry".

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#923195: RM: multiple [kfreebsd-amd64 kfreebsd-i386 hurd-i386] -- RoQA; Unbuildable, out of date, no rdepends

[Sebastian Andrzej Siewior]

Package: ftp.debian.org
Severity: normal

As part of the of the openssl1.0 removal, I'm asking for the removal of
the following packages:

dak rm -p -R -n -B bitcoin -a kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|bitcoin-tx | 0.12.1-0.1 | kfreebsd-amd64, kfreebsd-i386
|libbitcoinconsensus-dev | 0.12.1-0.1 | kfreebsd-amd64, kfreebsd-i386
|libbitcoinconsensus0 | 0.12.1-0.1 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Debian Bitcoin Packaging Team 


dak rm -p -R -n -B caml-crush -a hurd-i386

|Checking reverse dependencies...
|No dependency problem found.
|
|Will remove the following packages from unstable:
|
|caml-crush-clients | 1.0.7-1+b1 | hurd-i386
|caml-crush-server | 1.0.7-1+b1 | hurd-i386
|
|Maintainer: Thomas Calderon 

dak rm -p -R -n -B crtmpserver -a kfreebsd-amd64,kfreebsd-i386

|Checking reverse dependencies...
|No dependency problem found.
|
|Will remove the following packages from unstable:
|
|crtmpserver | 1.0~dfsg-5.3 | kfreebsd-amd64, kfreebsd-i386
|crtmpserver-apps | 1.0~dfsg-5.3 | kfreebsd-amd64, kfreebsd-i386
|crtmpserver-dev | 1.0~dfsg-5.3 | kfreebsd-amd64, kfreebsd-i386
|crtmpserver-libs | 1.0~dfsg-5.3 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Debian Multimedia Maintainers 


dak rm -p -R -n -B encfs -a kfreebsd-amd64,kfreebsd-i386

|Checking reverse dependencies...
|No dependency problem found.
|
|Will remove the following packages from unstable:
|
| encfs | 1.8.1-3+b2 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Eduard Bloch 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B freeradius -a hurd-i386,kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|freeradius | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|freeradius-dbg | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|freeradius-iodbc | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|freeradius-krb5 | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|freeradius-ldap | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|freeradius-mysql | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|freeradius-postgresql | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|freeradius-utils | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|libfreeradius-dev | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|libfreeradius2 | 2.2.8+dfsg-0.1+b3 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Josip Rodin 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B goldencheetah -a kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|goldencheetah |3.3.0-3 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: KURASHIKI Satoru 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B httping -a hurd-i386

|Will remove the following packages from unstable:
|
|   httping |   2.4-1+b1 | hurd-i386
|
|Maintainer: Abhijith PA 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B ifstat -a kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|ifstat |1.1-8.1 | kfreebsd-amd64, kfreebsd-i386
|libifstat-dev |1.1-8.1 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Goswin von Brederlow 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B monit -a hurd-i386

|Will remove the following packages from unstable:
|
| monit | 1:5.17.1-2 | hurd-i386
|
|Maintainer: Sergey B Kirpichev 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B mosh -a kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|  mosh |1.2.6-1 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Keith Winstein 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B mumble -a kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|mumble |   1.2.16-2 | kfreebsd-amd64, kfreebsd-i386
|mumble-dbg |   1.2.16-2 | kfreebsd-amd64, kfreebsd-i386
|mumble-server |   1.2.16-2 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Christopher Knadle 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B radsecproxy -a hurd-i386,kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|radsecproxy |1.6.9-1 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Faidon Liambotis 
|
|Checking reverse dependencies...
|No dependency problem found.

dak rm -p -R -n -B rsyncrypto -a hurd-i386

|Will remove the following packages from unstable:
|
|rsyncrypto | 1.12-2 | hurd-i386
|
|Maintainer: Shachar Shemesh 
|
|dak rm -p -R -n -B urweb -a kfreebsd-amd64
|
|Checking reverse dependencies...
|No dependency problem found.
|
|Will remove the following packages from unstable:
|
|liburweb-cgi0 | 

Bug#923196: RM: pexif -- ROM; no longer used anywhere in Debian

[Marcelo Jorge Vieira]

Package: ftp.debian.org
Severity: normal

Hi,

As subject says, please drop pexif from unstable, as it is no
longer used anywhere in Debian.


Cheers,


-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com


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

Bug#923194: RM: multiple [kfreebsd-amd64 kfreebsd-i386 hurd-i386] -- RoQA; Unbuildable, out of date, rdepends

[Sebastian Andrzej Siewior]

Package: ftp.debian.org
Severity: normal

As part of the of the openssl1.0 removal, I'm asking for the removal of
the following packages.
A newer version of those packages was built on other architectures but
not on kfreebsd-* and or hurd-i386. Some of those broken dependencies
are arch ALL (like node).
I can split this request in multiple bugs if requested.

dak rm -p -R -n -B gfarm -a hurd-i386

|Will remove the following packages from unstable:
|
|gfarm-client | 2.6.7+dfsg-1 | hurd-i386
|  gfmd | 2.6.7+dfsg-1 | hurd-i386
|  gfsd | 2.6.7+dfsg-1 | hurd-i386
|libgfarm-dev | 2.6.7+dfsg-1 | hurd-i386
| libgfarm1 | 2.6.7+dfsg-1 | hurd-i386
|
|Maintainer: Dmitry Smirnov 
|
|Checking reverse dependencies...
|# Broken Build-Depends:
|gfarm2fs: libgfarm-dev (>= 2.7.11~)
|
|Dependency problem found.

But gfarm2fs is not built on hurd-i386 as far as I can tell.

dak rm -p -R -n -B gst-plugins-bad1.0 -a hurd-i386,kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|gir1.2-gst-plugins-bad-1.0 | 1.8.3-1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|gstreamer1.0-plugins-bad | 1.8.3-1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|gstreamer1.0-plugins-bad-dbg | 1.8.3-1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|libgstreamer-plugins-bad1.0-0 | 1.8.3-1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|libgstreamer-plugins-bad1.0-dev | 1.8.3-1+b3 | hurd-i386, kfreebsd-amd64, 
kfreebsd-i386
|
|Maintainer: Maintainers of GStreamer packages 

|
|Checking reverse dependencies...
|# Broken Depends:
|betaradio: betaradio [hurd-i386]
|buzztrax: buzztrax
|cheese: libcheese8
|gnome-keysign: gnome-keysign
|gnome-twitch: gnome-twitch-player-backend-gstreamer-cairo [kfreebsd-amd64 
kfreebsd-i386]
|  gnome-twitch-player-backend-gstreamer-clutter [kfreebsd-amd64 
kfreebsd-i386]
|  gnome-twitch-player-backend-gstreamer-opengl [kfreebsd-amd64 
kfreebsd-i386]
|gnome-video-effects: gnome-video-effects
| gnome-video-effects-frei0r
|knowthelist: knowthelist [hurd-i386]
|pithos: pithos
|pitivi: pitivi
|playitslowly: playitslowly
|radiotray: radiotray
|vagalume: vagalume
|voctomix: voctomix-core
|  voctomix-gui
|
|# Broken Build-Depends:
|aravis: gstreamer1.0-plugins-bad
|cheese: libgstreamer-plugins-bad1.0-dev (>= 1.4)
|gnome-dvb-daemon: gstreamer1.0-plugins-bad
|  libgstreamer-plugins-bad1.0-dev (>= 1.4)
|grilo-plugins: gstreamer1.0-plugins-bad
|gstreamer-vaapi: libgstreamer-plugins-bad1.0-dev (>= 1.14.4)
|
|Dependency problem found.

dak rm -p -R -n -B ipmitool -a hurd-i386

|Will remove the following packages from unstable:
|
|  ipmitool |   1.8.16-3 | hurd-i386
|
|Maintainer: Jörg Frings-Fürst 
|
|Checking reverse dependencies...
|# Broken Depends:
|ceilometer: ceilometer-agent-ipmi
|ironic: ironic-common
|ironic-conductor
|openstack-cluster-installer: openstack-cluster-installer
|openstack-meta-packages: openstack-tempest-ci
|
|Dependency problem found.

dak rm -p -R -n -B kdelibs4support -a kfreebsd-amd64,kfreebsd-i386

|Will remove the following packages from unstable:
|
|libkf5kdelibs4support-dev |   5.37.0-2 | kfreebsd-amd64, kfreebsd-i386
|libkf5kdelibs4support5 |   5.37.0-2 | kfreebsd-amd64, kfreebsd-i386
|libkf5kdelibs4support5-bin |   5.37.0-2 | kfreebsd-amd64, kfreebsd-i386
|
|Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
|
|Checking reverse dependencies...
|# Broken Depends:
|akonadi: libkf5akonadi-dev
|akonadi-calendar: libkf5akonadicalendar5
|digikam: digikam-private-libs
|kalarmcal: libkf5alarmcalendar-dev
|   libkf5alarmcalendar5
|kblog: libkf5blog-dev
|   libkf5blog5
|kcalcore: libkf5calendarcore-dev
|  libkf5calendarcore5
|kcalutils: libkf5calendarutils-dev
|   libkf5calendarutils5
|kde-cli-tools: kde-cli-tools
|kdeplasma-addons: plasma-dataengines-addons
|  plasma-runners-addons
|kgamma5: kgamma5
|kholidays: libkf5holidays-dev
|kio-extras: kio-extras
|kmplayer: kmplayer
|kmplot: kmplot
|kontactinterface: libkf5kontactinterface-dev
|ktnef: libkf5tnef5
|ktuberling: ktuberling
|kwordquiz: kwordquiz
|libkf5calendarsupport: libkf5calendarsupport5
|libkf5eventviews: libkf5eventviews5
|libkf5incidenceeditor: libkf5incidenceeditor5
|libkf5pimcommon: libkf5pimcommon5
|qtcurve: kde-style-qtcurve-qt5
|user-manager: user-manager
|zanshin: zanshin
|
|# Broken Build-Depends:
|akonadi-calendar-tools: libkf5kdelibs4support-dev (>= 5.47.0~)
|audiocd-kio: libkf5kdelibs4support-dev (>= 5.24.0~)
|calligra: libkf5kdelibs4support-dev (>= 5.7.0)
|dolphin: libkf5kdelibs4support-dev (>= 5.43.0~)
|dolphin-plugins: libkf5kdelibs4support-dev (>= 5.0.0~)
|kalarm: libkf5kdelibs4support-dev (>= 5.47.0~)
|kalzium: libkf5kdelibs4support-dev
|kde-cli-tools: libkf5kdelibs4support-dev (>= 5.16.0~)
|kdepim-runtime: libkf5kdelibs4support-dev (>= 5.47.0~)
|kdeplasma-addons: libkf5kdelibs4support-dev (>= 5.42.0~)
|kfind: libkf5kdelibs4support-dev (>= 5.19.0)
|kgamma5: libkf5kdelibs4support-dev

Bug#923193: RM: pyvows -- ROM; no longer used anywhere in Debian

[Marcelo Jorge Vieira]

Package: ftp.debian.org
Severity: normal

Hi,

As subject says, please drop pyvows from unstable, as it is no
longer used anywhere in Debian.


Cheers,


-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com


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

Bug#923192: RM: tornado-pyvows -- ROM; no longer used anywhere in Debian

[Marcelo Jorge Vieira]

Package: ftp.debian.org
Severity: normal

Hi,

As subject says, please drop tornado-pyvows from unstable, as it is no
longer used anywhere in Debian.


Cheers,


-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com


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

Bug#923191: munin-plugins-c: open_files can't cope with very large max files

[Marc Donges]

Package: munin-plugins-c
Version: 0.0.11-1
Severity: normal

Dear Maintainer,

the open_files plugin seems not to be able to cope with very large
values for max files. On two of my machines it returns 0 as warning and
critical thresholds for the number of open files. I believe this is
because it does not handle the value for max files correctly.

Actual output:
root@nephthys:~# munin-run open_files 
used.value 11008
max.value -1

root@nephthys:~# munin-run open_files config
graph_title File table usage
graph_args --base 1000 -l 0
graph_vlabel number of open files
graph_category system
graph_info This graph monitors the Linux open files table.
used.label open files
used.info The number of currently open files.
max.label max open files
max.info The maximum supported number of open files. Tune by modifying 
/proc/sys/fs/file-nr.
used.warning 0
used.critical 0

Because the current value for open files used.value is larger than the
threshold of used.critical 0, munin alerts this.

As the config output suggests, I looked at the kernel configuration:

root@nephthys:~# cat /proc/sys/fs/file-nr 
11136   0   18446744073709551615

The value for max_files is the largest unsigned 64bit integer and would
be -1 if incorrectly interpreted as signed. As the standard perl
equivalent for open_files calculates the warning and critical values
from the max value, I assume this step fails.

Expected output:

The output would be fine if it were the same as the perl plugin's:

root@nephthys:~# munin-run open_files 
used.value 11424
max.value 18446744073709551615

root@nephthys:~# munin-run open_files config
graph_title File table usage
graph_args --base 1000 -l 0
graph_vlabel number of open files
graph_category system
graph_info This graph monitors the Linux open files table.
used.label open files
used.info The number of currently open files.
used.warning 16971004547812788224
used.critical 18077809192235360256
max.label max open files
max.info The maximum supported number of open files. Tune by modifying 
/proc/sys/fs/file-max.

An alternative would be to simply not output warning and critical levels
when the max value is so huge.

Kind regards
Marc


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (745, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages munin-plugins-c depends on:
ii  libc6  2.28-7

munin-plugins-c recommends no packages.

munin-plugins-c suggests no packages.

-- no debconf information

Bug#923152: vim-addon-manager: Please don't rely on Etc.getlogin()

[James McCoy]

On Sun, Feb 24, 2019 at 03:41:48PM +0100, David Rabel wrote:
> in Line 202 (parse_cmdline) you call Etc.getlogin and Etc.getpwnam, but this
> fails under certain circumstances. For example when called by a daemon.
> We (vim-lastplace) use vim-addon-manager in our maintainer scripts, so this 
> can
> lead to errors with automatic updates:

FWIW, since you're already enabling the addon by default in the
maintainer scripts, I'd suggest switching to dh-vim-addon.  You won't
need the maintainer scripts anymore.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#923190: ghdl: Allow building against LLVM 8

[Logan Rosen]

Package: ghdl
Version: 0.35+git20181129+dfsg-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

Please allow building against LLVM 8 in the configure file. We've done
this in Ubuntu, and it builds successfully. We needed to make this
change because LLVM 8 is now default in our development release, and it
likely will change soon for Debian as well with the final release out
shortly.

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

  * Allow building against LLVM 8, which was recently made default in Ubuntu.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-15-generic (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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8 
ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8
--- ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8  1969-12-31 
19:00:00.0 -0500
+++ ghdl-0.35+git20181129+dfsg/debian/patches/allow-llvm-8  2019-02-22 
22:17:32.0 -0500
@@ -0,0 +1,10 @@
+--- a/configure
 b/configure
+@@ -238,6 +238,7 @@
+check_version 5.0 $llvm_version ||
+check_version 6.0 $llvm_version ||
+check_version 7.0 $llvm_version ||
++   check_version 8.0 $llvm_version ||
+false; then
+   echo "Debugging is not enabled with llvm $llvm_version"
+   llvm_be=llvm4-nodebug
diff -Nru ghdl-0.35+git20181129+dfsg/debian/patches/series 
ghdl-0.35+git20181129+dfsg/debian/patches/series
--- ghdl-0.35+git20181129+dfsg/debian/patches/series2018-12-11 
16:37:29.0 -0500
+++ ghdl-0.35+git20181129+dfsg/debian/patches/series2019-02-22 
22:16:56.0 -0500
@@ -3,3 +3,4 @@
 modify-install-paths
 adjust-compile-flags
 extend-ghdl-manpage
+allow-llvm-8

Bug#922153: ncurses-base: for screen and variants, please change smacs and rmacs to \E(0 and \E(B respectively

[Vincent Lefevre]

On 2019-02-23 21:17:38 -0500, Thomas Dickey wrote:
> On Sun, Feb 24, 2019 at 01:56:06AM +0100, Vincent Lefevre wrote:
> > No, "tput enacs" returns an error in Linux consoles, and has no effect
> > there. For instance, in xterm:
> 
> not so (see screenshot).

This is not what I obtain:

zira:~> env | grep '^TERM'
TERM=linux
zira:~> infocmp
#   Reconstructed via infocmp from file: /home/vinc17/.terminfo/l/linux
[...]

The infocmp(1) man page says:

FILES
   /etc/terminfo   Compiled terminal description database.

This doesn't look right.

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

Bug#922804: makehuman: FTBFS (Could not import extension sphinx.ext.pngmath)

[Muammar El Khatib]

Hi,

On Sun, Feb 24, 2019 at 2:45 PM Andreas Tille  wrote:
>
> Hi,
>
> I plan to fix this in a NMU once I've importet the packaging to Salsa.
>
> Kind regards
>
> Andreas.
>
> --
> http://fam-tille.de


I really appreciate this. I don't have much time recently to work on
it. But I don't want to leave Debian :S I hope I can work more when I
get more stable with my job.

Best,

-- 
Muammar El Khatib.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Bug#898768: gnome-twitch: Segfault everytime you try to watch a stream

[Jaycee Santos]

Package: gnome-twitch
Version: 0.3.1-1
Followup-For: Bug #898768

Dear Maintainer,

This bug is still present in Debian stretch (as of version 9.8).
Because of this, gnome-twitch is _still_ unusable in stable.

Is it possible to bring the patch to stable?

Thank you for your time!

Jaycee



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

Kernel: Linux 4.9.0-8-amd64 (SMP w/16 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 gnome-twitch depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libc62.24-11+deb9u4
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libjson-glib-1.0-0   1.2.6-1
ii  libpeas-1.0-01.20.0-1+b1
ii  libsoup2.4-1 2.56.0-2+deb9u2
ii  libwebkit2gtk-4.0-37 2.18.6-1~deb9u1
ii  libx11-6 2:1.6.4-3+deb9u1

Versions of packages gnome-twitch recommends:
ii  gnome-twitch-player-backend-gstreamer-cairo  0.3.1-1

gnome-twitch suggests no packages.

-- no debconf information
[22:43:32] Message - GNOME-Twitch : {GtApp} Startup
[22:43:32] Message - GNOME-Twitch : {GtApp} Loading chat settings
[22:43:32] Message - GNOME-Twitch : {GtApp} Activate
[22:43:38] Message - GNOME-Twitch : {GtPlayer} Can't open channel, no backend 
loaded
libdc1394 error: Failed to initialize libdc1394
[22:43:41] Message - GNOME-Twitch : {GtPlayer} Loaded player backend 'GStreamer 
Cairo player backend'
[22:43:41] Message - GNOME-Twitch : {GtPlayerBackendGstreamerCairo} Init
[22:43:41] Warning - GNOME-Twitch : cannot set NULL uri
[22:43:41] Message - GNOME-Twitch : {GtPlayer} Opening stream 'overwatchleague' 
with quality 'source'
[22:43:41] Warning - GNOME-Twitch : {GtTwitch} Received unsuccessful response 
from url 'http://api.twitch.tv/api/channels/overwatchleague/access_token' with 
code '400' and body '{"error":"Bad Request","status":400,"message":"Requests 
must be made over SSL"}'
[22:43:41] Warning - GNOME-Twitch : {GtTwitch} Error getting stream access 
token for channel='overwatchleague'
[22:43:41] Critical - GNOME-Twitch : gt_twitch_all_streams: assertion 'token != 
NULL' failed
[22:43:41] Warning - GNOME-Twitch : {GtPlayer} Error opening stream
[22:43:42] Message - GNOME-Twitch : {GtIrc} Connecting with nick='', 
host='irc.chat.twitch.tv' and port='80'
[22:43:42] Message - GNOME-Twitch : {GtIrc} Joining with 
channel='#overwatchleague'

Bug#923102: RFS: xsoldier/1:1.8-6 [ITA] -- shoot 'em up game with the "not shooting" bonus

[Adam Borowski]

On Sun, Feb 24, 2019 at 08:37:53AM +0100, Sebastien CHAVAUX wrote:
> I would like to adopt the xsoldier package, considering that it does not
> change much or little and requires little in consequence.
> I am looking for a sponsor for my package "xsoldier"

> * Package name: xsoldier
>   Version : 1:1.8-6

> Changes since the last upload:
> 
> xsoldier (1:1.8-6) unstable; urgency=medium
> 
>   * New maintainer. (Closes: #738879)
> 
>  -- Sebastien CHAVAUX   Sun, 24 Feb 2019 07:41:00 +0100

Would you have any changes other than to stake a claim?  It's pretty
pointless to make an upload only to change the Maintainer field.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Have you accepted Khorne as your lord and saviour?
⠈⠳⣄

Bug#922804: makehuman: FTBFS (Could not import extension sphinx.ext.pngmath)

[Andreas Tille]

Hi,

I plan to fix this in a NMU once I've importet the packaging to Salsa.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#919646: Decrease severity of bug, commit prokect to Salsa

[Andreas Tille]

Control: tags -1 moreinfo
Control: severity -1 normal

As far as I can read in the bug log the issue can not be reproduced any
more.  Thus for the moment I'll decrease the severity of the bug to
avoid that the package will be removed from testing for no good reason.

In the bug log it was also mentioned that the packaging should be moved
to Salsa.  As Adrian I'm also doing QA work only and will definitely not
join any packaging team.  However, since I plan to fix #922804 (should
be pretty easy as I'm guessing from experience with other packages) I'd
like to do this in Git.  To do so I volunteer to create the Git
repository in

https://salsa.debian.org/debian/makehuman

I'll upload with this in Vcs fields set - except if you stop me from
doing so.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#896080: [pkg-apparmor] Improve samba/AppArmor integration

[Christian Boltz]

Hello,

I agree that local/ isn't the perfect place. That said...

Am Sonntag, 24. Februar 2019, 20:42:55 CET schrieb Mathieu Parent:
> Le dimanche 24 février 2019, intrigeri  a écrit:
> > intrigeri:
> >> So I'll add this:
> >>#include if exists /etc/apparmor.d/samba/smbd-shares
> > 
> > I mean:
> >#include if exists 
> 
> I'm OK with this path and understand your rationale. However, I try to
> avoid distribution divergence. 

We had a similar discussion upstream quite a while (years?) ago, but 
didn't reach an agreement on which path to use.

I'm not sure if I like your samba/... path - it's not bad on itsself, 
but it opens a can of worms. Let's assume for a moment that more 
programs auto-generate profile sniplets. Do we really want to have one 
directory for each of them (always holding a single file)? I'm afraid 
that might produce an interesting forest in /etc/apparmor.d/...

Counter-proposal: What about  /etc/apparmor.d/autogenerated/$whatever  ? 
That directory could be used by multiple programs.

> Christian: any chance that the
> opensuse path changes too?

We'll have to migrate existing users (and therefore probably have to 
support both paths in the samba profile for a while). 
That makes things more interesting[tm], but won't stop me from keeping 
the path in sync ;-)


Another note: update-apparmor-samba-profile does

test -e "$profilesniplet" || silentexit "apparmor profile snippet 
 not available"

which means you _have to_ ship a (possibly empty) sniplet to ensure the 
script works.

The alternative would be to change that test to something like

test -d "/etc/apparmor.d/autogenerated" || silentexit "directory for
  autogenerated profile sniplets doesn't exist"


Regards,

Christian Boltz
-- 
> Das ist wieder so ein schöner Popcorn-Thread, zu dem ich
> meinen Senf dazu geben will:
Popcorn mit Senf :-)
[> Jens Nixdorf und Rainer Koenig in suse-linux]


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

Bug#923189: clearsilver-dev: Typo in package description

[Thomas Vincent]

Package: clearsilver-dev
Severity: minor

Dear Maintainer,

I noticed a typo in the long description of clearsilver-dev. Indeed, in the 
last paragraph, "deverlopers" should be spelled "developers".

Thanks a lot for your work on clearsilver!
Cheers,
Thomas


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

Kernel: Linux 4.19.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
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 clearsilver-dev depends on:
ii  libc6-dev  2.24-11+deb9u4

clearsilver-dev recommends no packages.

clearsilver-dev suggests no packages.

Bug#410419: confile prompts should use debconf

[Guillem Jover]

Control: retitle -1 dpkg: conffile prompts should use debconf

Hi!

I was asked by Julian Andres Klode on IRC about the status of this,
so let's update the bug too.

On Sat, 2007-02-10 at 15:16:30 -, peter green wrote:
> in situations where a user cannot interact directly with dpkg
> (debian-installer is one example of this though conffile prompts
> shouldn't normally happen there) conffile prompts currently result
> in a hung installation process, this is not a good thing.
> 
> since debconf seems to be the preffered method of communicating with
> the user and already has mechanisms in place to allow for situations
> like D-I and for completely non-interactive installs it would seem
> more sensible to use it.

A fresh installation that produces conffile prompts seems like a bug
to me, and not something that should be worked around. Also fully
non-interactive installations can already be achieved with the desired
selection of --force-conf* options. But in any case, for GUIs and
similar this is still desirable.

There was some work done by Sean Finney some time ago. AFAIR there was
also review of those patches on the mailing list but the comments there
were never addressed.

The patches can be found in
.

I don't even remember anything about the state of that branch, but
from a quick skim, these are some of the quick problems I see:

  - diff printing is not handled via debconf. Although that is
something I find to be atrocious UI every time I get confronted
with configuration file prompts from ucf-using packages. :/
  - The debconf usage should be configurable I think.
  - Shell spawning would need to be handled somehow too, as GUIs might
unhappy with dpkg spawning it by itself.
  - The code does not seem to integrate greatly with debconf, and looks
a bit bolted on.
  - The code does not use the proper dpkg APIs.
  - The code does not follow the dpkg coding style.

I can probably rebase the patches now and fix some of these issues,
but some others will require a bit more thought.

Thanks,
Guillem

Bug#923188: xdm: file /etc/X11/xdm/Xsession has many newlines before #!

[Joshua]

Package: xdm
Version: 1:1.1.11-3
Severity: important

Dear Maintainer,

   * What led up to the situation?

Trying to use xdm for the first time in a decade after sddm destroyed itself

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

Xdm logged me in to some crazy session rather than my normal kde; tried to 
figure out what was wrong; found /etc/X11/xdm/Xsession broken


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

Kernel: Linux 4.19.0-2-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)
LSM: AppArmor: enabled

Versions of packages xdm depends on:
ii  cpp4:8.2.0-2
ii  debconf [debconf-2.0]  1.5.70
ii  libc6  2.28-7
ii  libpam0g   1.3.1-5
ii  libselinux12.8-1+b1
ii  libx11-6   2:1.6.7-1
ii  libxau61:1.0.8-1+b2
ii  libxaw72:1.0.13-1+b2
ii  libxdmcp6  1:1.1.2-3
ii  libxext6   2:1.3.3-1+b2
ii  libxft22.3.2-2
ii  libxinerama1   2:1.1.4-2
ii  libxmu62:1.1.2-2
ii  libxpm41:3.5.12-1
ii  libxrender11:0.9.10-1
ii  libxt6 1:1.1.5-1
ii  lsb-base   10.2018112800
ii  procps 2:3.3.15-2
ii  x11-utils  7.7+4
ii  x11-xserver-utils  7.7+8

xdm recommends no packages.

xdm suggests no packages.

-- debconf information excluded

Bug#922479: nvidia-legacy-340xx-kernel-dkms unknown symbols, kernel 4.20.x

[S R Wright]

This really needs to be fixed, at this point legacy NVIDIA graphics 
cards (such as my NVIDIA Corporation GT216M [NVS 5100M]) cannot use the 
legacy driver going past kernel 4.19.


The workaround of course is just to just use nouveau,  which at least 
*is* operational in 4.20.x but which also seems more like capitulation 
than a solution.


-- sRw

Bug#910069: linux-image-4.18.0-1-amd64: NVME quirk needed for Intel 760p + Thinkpad T480

[Chris Chiappa]

Doh, I had checked for firmware when I first ran into the problem and
never checked again.  Indeed, having upgraded the firmware, the
command line workaround no longer seems necessary, feel free to close
the bug.  Thanks!

On Sun, Feb 10, 2019 at 04:36:09PM +, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Tue, 02 Oct 2018 05:44:23 -0400 Chris Chiappa  
> wrote:
> [...]
> > # nvme id-ctrl /dev/nvme0 
> > NVME Identify Controller:
> > vid   : 0x8086
> > ssvid : 0x8086
> > sn: BTHH82260487512D
> > mn: INTEL SSDPEKKW512G8 
> > fr: 001C
> [...]
> 
> According to the release notes for the Intel SSD Firmware Update Tool
> 
> there is a firmware update (version 004C) and the description suggests
> it may address this problem.
> 
> Please upgrade the firmware (but make sure you have a backup of the
> drive) and check whether that fixes the problem.
> 
> Ben.
> 
> -- 
> Ben Hutchings
> The world is coming to an end.Please log off.
> 

Bug#921757: Can reproduce

[Hilko Bengen]

Santiago,

thanks for the follow-up. Your logfile with a more context looks a bit
different that what I got and gives a hint.

The "Use of uninitialized value" warnings suggest a race condition in
runcmd. Calling waitpid in a signal handler certainly has a smell to it.

I'll investigate further as time permits.

Cheers,
-Hilko

Bug#897674: p7zip-rar: CVE-2018-10115

[Raphael Kubo da Costa]

I was recently looking at this CVE and CVE 2018 10115.patch.

According to upstream 7-zip [1], this bug was fixed in version 18.05. In 
the upstream release announcement, someone asked about variables like 
_errorMode that were introduced earlier to deal with CVE-2018-5996 [2] 
and how they had been removed from this release.


The 7-Zip maintainer replied it was intentional and both CVEs should be 
fixed with that code. I've diff'ed 18.03 and 18.05, and _errorMode is 
either commented out or removed in the code, while the existing 
CVE_2018_10115.patch still has them in addition to the _solidAllowed 
stuff. I just package p7zip so I don't know much about how its 
implementation works, but I figured it'd be a better idea to make the 
CVE-2018-10115 patch more similar to what upstream had.


This new version is attached and follows what 18.05 upstream does.

[1] https://www.7-zip.org/history.txt
[2] 
https://sourceforge.net/p/sevenzip/discussion/45797/thread/adc65bfa/#8b13
--- CPP/7zip/Compress/Rar1Decoder.cpp.orig	2019-02-24 20:16:23.682521000 +0100
+++ CPP/7zip/Compress/Rar1Decoder.cpp	2019-02-24 22:02:59.461303000 +0100
@@ -29,7 +29,7 @@
 };
 */
 
-CDecoder::CDecoder(): m_IsSolid(false), _errorMode(false) { }
+CDecoder::CDecoder(): _isSolid(false), _solidAllowed(false) { }
 
 void CDecoder::InitStructures()
 {
@@ -345,7 +345,7 @@
 
 void CDecoder::InitData()
 {
-  if (!m_IsSolid)
+  if (!_isSolid)
   {
 AvrPlcB = AvrLn1 = AvrLn2 = AvrLn3 = NumHuf = Buf60 = 0;
 AvrPlc = 0x3500;
@@ -391,6 +391,11 @@
   if (inSize == NULL || outSize == NULL)
 return E_INVALIDARG;
 
+  if (_isSolid && !_solidAllowed)
+return S_FALSE;
+
+  _solidAllowed = false;
+
   if (!m_OutWindowStream.Create(kHistorySize))
 return E_OUTOFMEMORY;
   if (!m_InBitStream.Create(1 << 20))
@@ -398,22 +403,18 @@
 
   m_UnpackSize = (Int64)*outSize;
   m_OutWindowStream.SetStream(outStream);
-  m_OutWindowStream.Init(m_IsSolid);
+  m_OutWindowStream.Init(_isSolid);
   m_InBitStream.SetStream(inStream);
   m_InBitStream.Init();
 
   // CCoderReleaser coderReleaser(this);
   InitData();
-  if (!m_IsSolid)
+  if (!_isSolid)
   {
-_errorMode = false;
 InitStructures();
 InitHuff();
   }
 
-  if (_errorMode)
-return S_FALSE;
-
   if (m_UnpackSize > 0)
   {
 GetFlagsBuf();
@@ -475,6 +476,7 @@
   }
   if (m_UnpackSize < 0)
 return S_FALSE;
+  _solidAllowed = true;
   return m_OutWindowStream.Flush();
 }
 
@@ -482,16 +484,16 @@
 const UInt64 *inSize, const UInt64 *outSize, ICompressProgressInfo *progress)
 {
   try { return CodeReal(inStream, outStream, inSize, outSize, progress); }
-  catch(const CInBufferException ) { _errorMode = true; return e.ErrorCode; }
-  catch(const CLzOutWindowException ) { _errorMode = true; return e.ErrorCode; }
-  catch(...) { _errorMode = true; return S_FALSE; }
+  catch(const CInBufferException ) { return e.ErrorCode; }
+  catch(const CLzOutWindowException ) { return e.ErrorCode; }
+  catch(...) { return S_FALSE; }
 }
 
 STDMETHODIMP CDecoder::SetDecoderProperties2(const Byte *data, UInt32 size)
 {
   if (size < 1)
 return E_INVALIDARG;
-  m_IsSolid = ((data[0] & 1) != 0);
+  _isSolid = ((data[0] & 1) != 0);
   return S_OK;
 }
 
--- CPP/7zip/Compress/Rar1Decoder.h.orig	2019-02-24 20:16:23.683118000 +0100
+++ CPP/7zip/Compress/Rar1Decoder.h	2019-02-24 22:01:21.915855000 +0100
@@ -38,8 +38,8 @@
   UInt32 LastLength;
 
   Int64 m_UnpackSize;
-  bool m_IsSolid;
-  bool _errorMode;
+  bool _isSolid;
+  bool _solidAllowed;
 
   UInt32 ReadBits(int numBits);
   HRESULT CopyBlock(UInt32 distance, UInt32 len);
--- CPP/7zip/Compress/Rar2Decoder.cpp.orig	2019-02-24 20:16:23.683974000 +0100
+++ CPP/7zip/Compress/Rar2Decoder.cpp	2019-02-24 20:16:23.691384000 +0100
@@ -80,7 +80,8 @@
 static const UInt32 kWindowReservSize = (1 << 22) + 256;
 
 CDecoder::CDecoder():
-  m_IsSolid(false),
+  _isSolid(false),
+  _solidAllowed(false),
   m_TablesOK(false)
 {
 }
@@ -320,6 +321,10 @@
   if (inSize == NULL || outSize == NULL)
 return E_INVALIDARG;
 
+  if (_isSolid && !_solidAllowed)
+return S_FALSE;
+  _solidAllowed = false;
+
   if (!m_OutWindowStream.Create(kHistorySize))
 return E_OUTOFMEMORY;
   if (!m_InBitStream.Create(1 << 20))
@@ -330,12 +335,12 @@
   UInt64 pos = 0, unPackSize = *outSize;
   
   m_OutWindowStream.SetStream(outStream);
-  m_OutWindowStream.Init(m_IsSolid);
+  m_OutWindowStream.Init(_isSolid);
   m_InBitStream.SetStream(inStream);
   m_InBitStream.Init();
 
   // CCoderReleaser coderReleaser(this);
-  if (!m_IsSolid)
+  if (!_isSolid)
   {
 InitStructures();
 if (unPackSize == 0)
@@ -343,6 +348,7 @@
   if (m_InBitStream.GetProcessedSize() + 2 <= m_PackSize) // test it: probably incorrect;
 if (!ReadTables())
   return S_FALSE;
+  _solidAllowed = true;
   return S_OK;
 }
 if (!ReadTables())
@@ -386,6 +392,9 @@
 
   if (!ReadLastTables())
 return S_FALSE;
+
+  _solidAllowed = true;
+
   return 

Bug#923187: ITP: golang-github-golang-freetype -- The Freetype font rasterizer in the Go programming language.

[Felix Yan]

Package: wnpp
Severity: wishlist
Owner: Felix Yan 

* Package name: golang-github-golang-freetype
  Version : release+git20170609.e2365df-1
  Upstream Author : The Freetype-Go Authors
* URL : https://github.com/golang/freetype
* License : GPL-2+ or FTL
  Programming Lang: Go
  Description : The Freetype font rasterizer in the Go programming language.
 See the reference (https://github.com/golang/freetype) for more info.

This package is in the dependency tree of Deepin Desktop Environment's go 
backend.

Bug#923186: anarchism: Typo in section F4

[David Calman]

Package: anarchism
Version: 15.1-9
Severity: important

Dear Maintainer,

> What led up to the situation?
I navigated to file:///usr/share/doc/anarchism/html/secF4.html

> What exactly did you do (or not do) that was effective (or ineffective)?
I attempted to read the document.

> What was the outcome of this action?
I got confused a bit by this: "The inequalities property can generate
can have a serious on individual freedom (see Section F.3)

> What outcome did you expect instead?
I expected there to be a word between "serious" and "on".
Something like "adverse effect", "effect", or "impact".

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

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

Versions of packages anarchism depends on:
ii  xdg-utils  1.1.1-1+deb9u1

anarchism recommends no packages.

Versions of packages anarchism suggests:
ii  firefox-esr [www-browser]60.5.1esr-1~deb9u1
pn  fortune-anarchism
ii  sugar-browse-activity [www-browser]  200+20170502-1
ii  w3m [www-browser]0.5.3-34+deb9u1
ii  yelp 3.22.0-1

-- no debconf information

Bug#919115: linux-image-4.19.0-0.bpo.1-amd64-unsigned: Graphical glitches (lightdm and cinnamon) after upgrading linux (RadeonRX540)

[N G]

Just upgraded to firmware-amd-graphics-20190114/stretch-backports and 
nothing changed, therefore lightdm might be working with testing branch 
because of lightdm's version or something unrelated to linux itself 
(maybe mesa?), still, it used to work correctly with stretch until linux 
4.18.20 (at least the lightdm thing because I had hdmi issues).  After 
4.19 I've been having to rely on 'amdgpu.dc=0' to avoid graphical 
glitches, but amdgpu.dc=1 to get audio through HDMI.

Wallpaper glitches are gone, but cinnamon's lockscreen is still bugged, 
stuck and freezed just like lightdm's 'black screen' (if switching from 
tty to lightdm/lockscreen it refreshes once but it doesn't refreshes in 
real time so you can't see any typing or menus/dialogs working, although 
they're working, just not graphically)  'amdgpu.dc=0' still a workaround 
fortunately.  Worth remembering that with debian unstable it refreshes 
every 5 seconds (only lockscreen, lightdm just works like I said).

I have these graphical glitches only with debian.


Ever since kernel 4.16 I have lot of weird things going on with amdgpu 
(Acer laptop with AMD A12-9720P RADEON R7 RADEON RX540) (all distros).  
Fortunately debian it's still the most reliable distro IME.

If anyone it's interested in improving support for this laptop, there 
are a few important bugs in bugzilla.kernel, and bugs.freedesktop 
regarding AMD A12-9720P RADEON R7 RADEON RX540. A lot of work it's 
needed to get this laptop working with debian, since this laptop won't 
even boot properly with kernel 4.9 from stable.

Bug#922402: Bug #922402 in lintian marked as pending

[Chris Lamb]

Hi Roberto,

> It looks like perhaps libraries files shipped in libgcc1 also need to be
> added to the whitelist.

Thanks. Added in:

  
https://salsa.debian.org/lintian/lintian/commit/f9c245df6d9285a6c220cf87c6e76437f7089e33

I needed to add "gcc" manually in:

  
https://salsa.debian.org/lintian/lintian/commit/544e738ebcd12dc12dfdd3832c40acdf6050e451

:)


Regards,

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

Bug#922402: Bug #922402 in lintian marked as pending

[Chris Lamb]

Hi Roberto,

> It looks like perhaps libraries files shipped in libgcc1 also need to be
> added to the whitelist.

Thanks. Added in:

  
https://salsa.debian.org/lintian/lintian/commit/f9c245df6d9285a6c220cf87c6e76437f7089e33

I needed to add "gcc" manually in:


 
> 
> Regards,
> 
> -Roberto
> 
> -- 
> Roberto C. Sánchez


Regards,

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

Bug#923051: Acknowledgement (screen doesn't clear the screen for certain UTF8 characters)

[Bruce Momjian,,,]

I have seen the problem again, this time using the VXConnectbot SSH
client on Android, so I think this eliminates the ssh client as the
cause.

Again, it happens when using 'screen' and mutt's built-in pager, and
again when having a UTF8 emoji in the email content.  I do not get the
failure if I do not use screen.

In this case the emoji is on the third page of the email display, and
characters from the second email page appear, and again control-L fixes
it.  

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +

Bug#923164: leiningen-clojure: FTBFS (Could not resolve dependencies for project leiningen-core:leiningen-core:jar:2.8.1)

[Elana Hashman]

On Sun, Feb 24, 2019 at 04:31:08PM +, Santiago Vila wrote:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] ---< leiningen-core:leiningen-core 
> >
> [INFO] Building leiningen-core 2.8.1
> [INFO] [ jar 
> ]-
> [WARNING] The POM for bultitude:bultitude:jar:debian is missing, no 
> dependency information available
> [WARNING] The POM for org.clojure:clojure:jar:debian is missing, no 
> dependency information available

Not sure why this is failing to pick up Clojure, but bultitude's
namespace changed in the maven repo in the 0.3.0 release (so that
explains why that's not found).

While this would be relatively easy to submit a targeted patch for, due
to lein's other RC bug #900299 (which needs a new upstream version of
Leiningen to fix) I will fix this indirectly via that bug instead.

- e


signature.asc
Description: PGP signature

Bug#923185: FTBS: javadoc: error - The code being documented uses packages in the unnamed module

[Sjoerd Simons]

Source: isorelax
Version: 2004-11
Severity: serious

Hey,

Rebuilding isorelax fails to build with:
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.

The reproducible build logs show a similar error:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/isorelax_2004-11.rbuild.log.gz

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'proposed-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.19.0-2-amd64 (SMP w/32 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#923181: Please add support for reporting mouse button presses to console programs which support mouse tracking

[Bill Allombert]

On Sun, Feb 24, 2019 at 07:35:20PM +, Daniel Abrecht wrote:
> Package: consolation
> Version: 0.0.6-2
> Severity: wishlist
> Tags: patch
> 
> Some programs support mouse tracking to allow users to click on things
> inside the terminal. For example, it is possible to click on options in
> `dialog`. gpm did support this, but had issues with touch screens. It
> would be great if `consolation` could add support for this. I've
> attached a patch for adding that functionality.
> 
> A good way to test this is using `vttest`. Just select the following in
> `vttest`:
> 
> `11. Test non-VT100 (e.g., VT220, XTERM) terminals`
> `8. Test XTERM special features`
> `5. Mouse features`
> `4. Normal Mouse Tracking`
> 
> After that, you can click anywhere in the terminal. It should display
> the button number at the location in the terminal a click occurred, and
> a star where the mouse button has been released.
> diff -Nru consolation-0.0.6/src/selection.c consolation-0.0.7/src/selection.c
> --- consolation-0.0.6/src/selection.c 2017-06-18 16:54:17.0 +
> +++ consolation-0.0.7/src/selection.c 2019-02-24 17:44:31.0 +
> @@ -67,6 +67,12 @@
>  }
>  
>  void
> +report_pointer(int x, int y, enum current_button button)
> +{
> +  linux_selection(x, y, x, y, TIOCL_SELMOUSEREPORT + ((button+3) % 4) );
> +}
> +

Hello Daniel,

Thanks for your patch, it looks great! Could you explain me how this
syscall work and where it is documented ?

All I have is console_ioctl(4):

   TIOCLINUX, subcode=7
argp points to a char  which  is  set  to  the  value  of the  kernel
variable report_mouse.  (Since Linux 1.1.33.)

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#923184: [pre-approval] unblock: qgis/3.4.5+dfsg-1

[Bas Couwenberg]

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

Because the 2.18 LTR is EOL with the release of QGIS 3.4.5 having the
latter in buster is probably better than leaving the qgis package at the
last 2.18.x release (2.18.28).

QGIS 3.4 is the new LTR and switches to Qt5 and Python 3, as such
the changes since the version in testing are quite large and cannot be
considered "small, targeted fixes".

While users of the qgis package are unlikely to use the version of the
package available in stable, and more likely using the latest LTR from
backports, I think having 3.4.5 in buster is better for users upgrading
from stretch than leaving them with the EOL 2.18.28 release until the
package is updated in buster-backports.

Would you approve of moving QGIS 3.4.5 from experimental to unstable and
allowing it to migrate to tesing for inclusion in buster?

Or should we keep it experimental until after the release, and make the
newer LTRs available in buster-backports when it hits testing?

Kind Regards,

Bas

Bug#922973: iptables-save -- Table `raw' does not exist

[Arturo Borrero Gonzalez]

On Fri, 22 Feb 2019 at 15:15, Bastian Blank  wrote:
>
> Package: iptables
> Version: 1.8.2-3
> Severity: important
>
> iptables-save fails with an error to stdout if a given built-in table
> does not exist.
>
> | % sudo iptables-save -t filter; echo $?
> | Table `filter' does not exist
> | 1
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1673609 for more
> information.
>

Thanks,

will upload a fix soon. Hopefully in time for the Debian Buster release.

Bug#923183: ITP: golang-github-ruudk-golang-pdf417 -- Port of pdf417-php by ihabunek in Golang

[Felix Yan]

Package: wnpp
Severity: wishlist
Owner: Felix Yan 

* Package name: golang-github-ruudk-golang-pdf417
  Version : 0.0~git20181029.1af4ab5-1
  Upstream Author : Ruud Kamphuis
* URL : https://github.com/ruudk/golang-pdf417
* License : Expat
  Programming Lang: Go
  Description : Port of pdf417-php by ihabunek in Golang

 PDF417 barcodes in Golang
 .
 This library encodes data to a PixelGrid that can be used to display the
 barcode.  You can use the PixelGrid to draw the barcode on anything.

This package is in the dependency tree of Deepin Desktop Environment's go 
backend.

Bug#923182: FTBS: javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in file:///usr/share/doc/default-jdk/api/ are in named modules.

[Sjoerd Simons]

Source: icu4j
Version: 62.1-1
Severity: serious

Hey,

Rebuilding icu4j sees to FTBS with:
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in file:///usr/share/doc/default-jdk/api/ are in named 
modules.

The reproducible builds log is showing the same eror:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/icu4j_62.1-1.rbuild.log.gz

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'proposed-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.19.0-2-amd64 (SMP w/32 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#923091: base-installer: Allow installing w/o the broken merged-usr-via-symlinks

[Holger Wansing]

Hi,

Cyril Brulebois  wrote:
> 
> If that were to be implemented: the question must not be asked in a
> normal installation, I think it shouldn't be translatable (at least at
> first) so that it doesn't put more burden on l10n people (coordinator
> and translators) for an expert-only option. Cc-ing Holger for input.

I'm unable to completely follow this whole 'merged-usr' thing, but to me
personally it seems like a somewhat controversial issue, which may see some
more discussion and changings.

So I tend to follow Kibi's proposal to keep the strings untranslateable for 
now, to allow everything to settle down, and make them translatable within 
the Buster+1 development cycle.

Filing a separate bugreport for this untranslatable -> translatable change
will be the best way, to make sure we don't forget about this.


So long
Holger


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

Bug#919442: If you want to keep python-dmidecode in Buster you should at least send a mail to the bug report

[Andreas Tille]

Hi Sandro,

I hope this mail gives you sufficient time to sort this bug out.

Hope this helps

   Andreas.

-- 
http://fam-tille.de

Bug#922555: [Android-tools-devel] Bug#922555: android-sdk: should allow openjdk-8-jdk-headless

[seamlik]

> This means that even if I wish to use openjdk 8, openjdk 11 is pulled in
> and made default instead.

It depends on "default-jdk-headless (>= 2:1.8)", which means JDK8 satisfies as 
well. If your system has it installed already, installing "andriod-sdk" will 
not install JDK11.

In fact I believe a JDK shouldn't be a dependency at all. Only a JRE is needed 
to run the tools, and the child packages already depends on a JRE.



signature.asc
Description: OpenPGP digital signature

Bug#896080: Improve samba/AppArmor integration

[intrigeri]

Mathieu Parent:
> Thanks intrigeri for providing a solution!

Uploaded in apparmor 2.13.2-8, by the way.
It would be great if you could test if it works for you.

> I'm OK with this path and understand your rationale. However, I try to
> avoid distribution divergence.

Sure. Happy we're talking about it now, so there's a chance we pick
a solution that works for everybody :)

Cheers,
-- 
intrigeri

Bug#923181: Please add support for reporting mouse button presses to console programs which support mouse tracking

[Daniel Abrecht]

Package: consolation
Version: 0.0.6-2
Severity: wishlist
Tags: patch

Some programs support mouse tracking to allow users to click on things
inside the terminal. For example, it is possible to click on options in
`dialog`. gpm did support this, but had issues with touch screens. It
would be great if `consolation` could add support for this. I've
attached a patch for adding that functionality.

A good way to test this is using `vttest`. Just select the following in
`vttest`:

`11. Test non-VT100 (e.g., VT220, XTERM) terminals`
`8. Test XTERM special features`
`5. Mouse features`
`4. Normal Mouse Tracking`

After that, you can click anywhere in the terminal. It should display
the button number at the location in the terminal a click occurred, and
a star where the mouse button has been released.
diff -Nru consolation-0.0.6/debian/changelog consolation-0.0.7/debian/changelog
--- consolation-0.0.6/debian/changelog  2018-01-27 21:26:05.0 +
+++ consolation-0.0.7/debian/changelog  2019-02-24 15:10:24.0 +
@@ -1,3 +1,10 @@
+consolation (0.0.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Report mouse position to console programs
+
+ -- Daniel Patrick Abrecht   Sun, 24 Feb 2019 15:10:24 
+
+
 consolation (0.0.6-2) unstable; urgency=medium
 
   * New upstream release
diff -Nru consolation-0.0.6/src/action.c consolation-0.0.7/src/action.c
--- consolation-0.0.6/src/action.c  2017-06-18 16:54:17.0 +
+++ consolation-0.0.7/src/action.c  2019-02-24 17:44:31.0 +
@@ -19,6 +19,7 @@
 
 static double xx=1, yy=1, x0=-1, y0=-1, x1=-1, y1=-1;
 static int mode = 0;
+static enum current_button button = BUTTON_RELEASED;
 
 void
 set_pointer(double x, double y)
@@ -64,6 +65,8 @@
 void
 press_left_button(void)
 {
+  button = BUTTON_LEFT;
+  report_pointer((int)xx,(int)yy,button);
   if ((int)x1==(int)xx && (int)y1==(int)yy)
   {
 mode = (mode+1)%3;
@@ -80,6 +83,8 @@
 void
 release_left_button(void)
 {
+  button = BUTTON_RELEASED;
+  report_pointer((int)xx,(int)yy,button);
   x0=-1; y0=-1;
 }
 
@@ -92,11 +97,20 @@
 void
 press_right_button(void)
 {
+  button = BUTTON_RIGHT;
+  report_pointer((int)xx,(int)yy,button);
   if (x1>=0 && y1>=0)
 select_region((int)xx,(int)yy,(int)x1,(int)y1);
 }
 
 void
+release_right_button(void)
+{
+  button = BUTTON_RELEASED;
+  report_pointer((int)xx,(int)yy,button);
+}
+
+void
 vertical_axis(double v)
 {
   if (v)
diff -Nru consolation-0.0.6/src/consolation.h 
consolation-0.0.7/src/consolation.h
--- consolation-0.0.6/src/consolation.h 2018-01-06 21:06:00.0 +
+++ consolation-0.0.7/src/consolation.h 2019-02-24 17:44:33.0 +
@@ -19,6 +19,13 @@
 
 extern int nodaemon;
 
+enum current_button {
+  BUTTON_RELEASED,
+  BUTTON_LEFT,
+  BUTTON_MIDDLE,
+  BUTTON_RIGHT
+};
+
 /* global state */
 
 extern unsigned int screen_width;
@@ -27,6 +34,7 @@
 /* selection.c */
 
 void set_screen_size(void);
+void report_pointer(int x, int y, enum current_button button);
 void draw_pointer(int x, int y);
 void select_region(int x, int y, int x2, int y2);
 void select_words(int x, int y, int x2, int y2);
@@ -43,6 +51,7 @@
 void release_left_button(void);
 void press_middle_button(void);
 void press_right_button(void);
+void release_right_button(void);
 void vertical_axis(double v);
 
 /* input.c */
diff -Nru consolation-0.0.6/src/input.c consolation-0.0.7/src/input.c
--- consolation-0.0.6/src/input.c   2018-01-26 17:50:05.0 +
+++ consolation-0.0.7/src/input.c   2019-02-24 17:44:31.0 +
@@ -96,6 +96,8 @@
   case BTN_RIGHT:
 if (state==LIBINPUT_BUTTON_STATE_PRESSED)
   press_right_button();
+else
+  release_right_button();
 break;
   }
 }
diff -Nru consolation-0.0.6/src/selection.c consolation-0.0.7/src/selection.c
--- consolation-0.0.6/src/selection.c   2017-06-18 16:54:17.0 +
+++ consolation-0.0.7/src/selection.c   2019-02-24 17:44:31.0 +
@@ -67,6 +67,12 @@
 }
 
 void
+report_pointer(int x, int y, enum current_button button)
+{
+  linux_selection(x, y, x, y, TIOCL_SELMOUSEREPORT + ((button+3) % 4) );
+}
+
+void
 draw_pointer(int x, int y)
 {
   linux_selection(x, y, x, y, TIOCL_SELPOINTER);


signature.asc
Description: OpenPGP digital signature

Bug#922996: Bug#923176: stretch-pu: package ca-certificates-java/20170929~deb9u1

[Adam D. Barratt]

Control: forcemerge 922996 923176
Control: tags 922996 + confirmed

On Sun, 2019-02-24 at 11:03 -0800, tony mancill wrote:
> This update closes #922720 [1], which addresses a bashism that
> prevents the package upgrade from completing successfully.  

There's already a request filed as #922996. I don't mind which version
gets uploaded - please co-ordinate among yourselves.

Regards,

Adam

Bug#896080: Improve samba/AppArmor integration

[Mathieu Parent]

Thanks intrigeri for providing a solution!

Le dimanche 24 février 2019, intrigeri  a écrit :
> intrigeri:
>> So I'll add this:
>
>>#include if exists /etc/apparmor.d/samba/smbd-shares
>
> I mean:
>
>#include if exists 

I'm OK with this path and understand your rationale. However, I try to
avoid distribution divergence. Christian: any chance that the opensuse path
changes too?

Regards

Mathieu

-- 
Mathieu

Bug#893244: jruby FTBFS with openjdk-9

[Markus Koschany]

JRuby is a mess. I guess we "just" need to package the latest upstream
release to fix the FTBFS bugs. Nobody felt like doing that in the past
twelve months, so I think it is unrealistic to believe we can make it
happen within one week. Of course if the release team can be convinced
to accept a new upstream release there might be additional time left.


In case a new upstream release or a similar patch won't happen in time,
here is the list of reverse-dependencies:

reverse-depends -b jruby

Reverse-Build-Depends-Indep
===
* libspring-java
* mustache-java

Reverse-Build-Depends
=
* jruby-maven-plugins
* jruby-openssl
* libfreemarker-java
* ruby-psych
* yecht

I presume every package with "ruby" would be expendable. The rest needs
a closer look but I hope jruby is always optional.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#923178: transcend FTCBFS: builds for the build architecture

[Helmut Grohne]

Source: transcend
Version: 0.3.dfsg2-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

transcend fails to cross build from source, because it builds for the
build architecture. dh_auto_build passes cross tools for the makefile
buildsystem, but not for the autoconf buildsystem as it expects
./configure to take care of that. transcend's configure doesn't do that,
so for using this feature, we need to force the makefile build system.
Then transcend uses a non-standard compiler name GXX, so we need to
rename the variable. The attached patch implements that and makes
transcend cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru transcend-0.3.dfsg2/debian/changelog 
transcend-0.3.dfsg2/debian/changelog
--- transcend-0.3.dfsg2/debian/changelog2013-06-01 11:46:43.0 
+0200
+++ transcend-0.3.dfsg2/debian/changelog2019-02-24 20:19:53.0 
+0100
@@ -1,3 +1,10 @@
+transcend (0.3.dfsg2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 20:19:53 +0100
+
 transcend (0.3.dfsg2-3) unstable; urgency=low
 
   * Add patch to build with portaduio19. (Closes: #594014).
diff --minimal -Nru transcend-0.3.dfsg2/debian/rules 
transcend-0.3.dfsg2/debian/rules
--- transcend-0.3.dfsg2/debian/rules2013-06-01 11:46:43.0 +0200
+++ transcend-0.3.dfsg2/debian/rules2019-02-24 20:19:53.0 +0100
@@ -16,7 +16,8 @@
mkdir -p 32x32
convert -scale 32x32 transcend.png 32x32/transcend.png
convert 32x32/transcend.png 32x32/transcend.xpm
-   $(MAKE) -C Transcend/game \
+   dh_auto_build --buildsystem=makefile --sourcedirectory=Transcend/game 
-- \
+   GXX='$$(CXX)' \
OPTIMIZE_FLAG="$(CPPFLAGS) $(CXXFLAGS) \
-DLEVELS_DIR=\\\"/usr/share/games/transcend/levels\\\"" 
\
PLATFORM_LINK_FLAGS="$(LDFLAGS) -lGL -lglut -lGLU -lportaudio 
-lpthread"

Bug#923179: systemd breaks python-dbusmock autopkgtest

[Paul Gevers]

Source: systemd, python-dbusmock
Control: found -1 systemd/241-1
Control: found -1 python-dbusmock/0.18.1-2
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of systemd the autopkgtest of python-dbusmock fails
in testing when that autopkgtest is run with the binary packages of
systemd from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
systemdfrom testing241-1
python-dbusmockfrom testing0.18.1-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of systemd to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? If needed, please change the
bug's severity.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/1994233/log.gz

==
FAIL: test_empty (__main__.TestLogind)
--
Traceback (most recent call last):
  File "test_logind.py", line 57, in test_empty
self.assertEqual(out, '')
AssertionError: 'No sessions.\n' != ''
- No sessions.



signature.asc
Description: OpenPGP digital signature

Bug#914632: RFC: proposed fix for CVE-2018-19518 in uw-imap

[Magnus Holmgren]

söndag 30 december 2018 kl. 09:38:57 CET skrev  Salvatore Bonaccorso:
> There is an alternative approach wich was raised by Magnus in the
> respective bug: https://bugs.debian.org/914632#12 (and see followup
> from Moritz).

So, is it OK to upload this (assuming there's no code out there that actually 
uses SET_RSHPATH or SET_SSHPATH)?

(By no longer defining RSHPATH, rshpath doesn't get set by the following code 
and tcp_aopen() will return NIL without doing anything.

#ifdef RSHPATH  /* rsh path defined yet? */
  if (!rshpath) rshpath = cpystr (RSHPATH);
#endif

)

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer commit e644cfbd0aac25ef320912e58e0d37cb715b2b88
Author: Magnus Holmgren 
Date:   Sun Jan 13 21:07:41 2019 +0100

[CVE-2018-19518] 2013_disable_rsh.patch (new): Disable access to IMAP 
mailboxes through running imapd over rsh (Closes: #914632).

diff --git a/debian/changelog b/debian/changelog
index b6960d1..cc7b885 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+uw-imap (8:2007f~dfsg-5+deb9u1) stretch-security; urgency=high
+
+  * [CVE-2018-19518] 2013_disable_rsh.patch (new): Disable access to IMAP
+mailboxes through running imapd over rsh, and therefore ssh (Closes:
+#914632). Code using the library can enable it with tcp_parameters()
+after making sure that the IMAP server name is sanitized.
+
+ -- Magnus Holmgren   Sun, 24 Feb 2019 19:45:23 +0100
+
 uw-imap (8:2007f~dfsg-5) unstable; urgency=low
 
   * 1006_openssl1.1_autoverify.patch (new): Use new features for
diff --git a/debian/patches/2013_disable_rsh.patch 
b/debian/patches/2013_disable_rsh.patch
new file mode 100644
index 000..7a68644
--- /dev/null
+++ b/debian/patches/2013_disable_rsh.patch
@@ -0,0 +1,11 @@
+--- a/src/osdep/unix/Makefile
 b/src/osdep/unix/Makefile
+@@ -985,7 +985,7 @@ onceenv:
+-DMD5ENABLE=\"$(MD5PWD)\" -DMAILSPOOL=\"$(MAILSPOOL)\" \
+-DANONYMOUSHOME=\"$(MAILSPOOL)/anonymous\" \
+-DACTIVEFILE=\"$(ACTIVEFILE)\" -DNEWSSPOOL=\"$(NEWSSPOOL)\" \
+-   -DRSHPATH=\"$(RSHPATH)\" -DLOCKPGM=\"$(LOCKPGM)\" \
++   -DLOCKPGM=\"$(LOCKPGM)\" \
+-DLOCKPGM1=\"$(LOCKPGM1)\" -DLOCKPGM2=\"$(LOCKPGM2)\" \
+-DLOCKPGM3=\"$(LOCKPGM3)\" > OSCFLAGS
+   echo $(BASELDFLAGS) $(EXTRALDFLAGS) > LDFLAGS
diff --git a/debian/patches/series b/debian/patches/series
index ced3fcc..80d69e8 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -9,3 +9,4 @@
 2012_krb5_multidev.patch
 1005_poll.patch
 1006_openssl1.1_autoverify.patch
+2013_disable_rsh.patch


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

Bug#887140: libjogl2-java FTBFS on architectures that use zero (timeout)

[Markus Koschany]

libjogl2-java still FTBFS on armel, mips64el and mipsel. I don't know
why the build process requires so much time on these platforms excluding
mips64el which never built before. On mips the build succeeded after six
hours.

I don't believe that mips and arm architectures are really supported by
upstream. We had to add several patches to change the build system and I
doubt there are many users on arm[el] and mips[el] that need
libjogl2-java. So as a workaround we could request the removal of binary
packages from those architectures and simply stop building them. If
someone has a better idea, please let us know, otherwise I will go ahead
with this plan.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

[Francesco Poli]

On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote:

> On Sun, Feb 24, 2019 at 05:05:58PM +0100, Francesco Poli wrote:
> >On Sun, 24 Feb 2019 16:25:19 +0100 Vincent Blut wrote:
> >
> >[...]
> >> On Sun, Feb 24, 2019 at 12:59:21PM +0100, Francesco Poli (wintermute)
> >> wrote:
> >[...]
> >> >Everything seems to be fine, but:
> >> >
> >> >  $ ps a | grep chrony
> >> >  10686 pts/1S+ 0:00 grep chrony
> >> >
> >> >the daemon is not running!
> >>
> >> Could you please provide the output of `grep -i chrony /var/log/syslog'?
> >
> >The lines added when doing
> >
> >  # service chrony start
> >
> >are:
> >
> >  Feb 24 16:53:39 HOST chronyd[11063]: chronyd version 3.4 starting (+CMDMON 
> > +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 
> > -DEBUG)
> >  Feb 24 16:53:39 HOST chronyd[11063]: Frequency -63.017 +/- 0.053 ppm read 
> > from /var/lib/chrony/chrony.drift
> >  Feb 24 16:53:39 HOST chronyd[11063]: Loaded seccomp filter
> >
> >But, once again, chrony is not running:
> >
> >  # ps a | grep chrony
> >  11086 pts/0S+ 0:00 grep chrony
>
> Please use `ps ax | grep chrony' (or ps -ef). `ps a' only lists
> processes with a tty.

You are right, sorry: I wanted to simplify the command output, but I
overplayed...   ;-)
Anyway, chronyd really fails to start:

  # ps ax | grep chrony
  12035 pts/0S+ 0:00 grep chrony

> Also, the output of `chronyc tracking' would be useful to check
> chronyd’s status and system time information.

Do you mean, when the daemon is not running?

  # chronyc tracking
  506 Cannot talk to daemon

Or when the daemon is running with log disabled?
Or when the daemon is running with system call filter disabled?

[...]
> >Needless to say, the logs were written by chronyd, when running with
> >the '-F 0' option...
>
> Ok, so please reenable the syscall filter

Done:

  # grep OPT /etc/default/chrony
   DAEMON_OPTS="-F 0"
  DAEMON_OPTS="-F -1"
  # grep 'mailonchange\|^log' /etc/chrony/chrony.conf
  log tracking measurements statistics
  logdir /var/log/chrony
   mailonchange root@localhost 4.0

> and run the following commands (as root):
>
> # mv /var/log/chrony/measurements.log /var/log/chrony/measurements1.log
> # chronyc cyclelogs
>
> wait a few seconds and tell me if a new “measurements.log” file is
> created.

  # ls -altrF /var/log/chrony/
  total 76
  drwxr-xr-x  2 _chrony _chrony  4096 Feb 24 10:31 ./
  drwxr-xr-x 10 rootroot 4096 Feb 24 11:09 ../
  -rw-r--r--  1 _chrony _chrony 18720 Feb 24 19:57 statistics.log
  -rw-r--r--  1 _chrony _chrony 25756 Feb 24 19:57 measurements.log
  -rw-r--r--  1 _chrony _chrony  9768 Feb 24 20:00 tracking.log
  # mv /var/log/chrony/measurements.log /var/log/chrony/measurements1.log
  # ls -altrF /var/log/chrony/
  total 76
  drwxr-xr-x 10 rootroot 4096 Feb 24 11:09 ../
  -rw-r--r--  1 _chrony _chrony 18720 Feb 24 19:57 statistics.log
  -rw-r--r--  1 _chrony _chrony 25756 Feb 24 19:57 measurements1.log
  -rw-r--r--  1 _chrony _chrony  9768 Feb 24 20:00 tracking.log
  drwxr-xr-x  2 _chrony _chrony  4096 Feb 24 20:10 ./
  # chronyc cyclelogs
  506 Cannot talk to daemon
  # sleep 10
  # ls -altrF /var/log/chrony/
  total 76
  drwxr-xr-x 10 rootroot 4096 Feb 24 11:09 ../
  -rw-r--r--  1 _chrony _chrony 18720 Feb 24 19:57 statistics.log
  -rw-r--r--  1 _chrony _chrony 25756 Feb 24 19:57 measurements1.log
  -rw-r--r--  1 _chrony _chrony  9768 Feb 24 20:00 tracking.log
  drwxr-xr-x  2 _chrony _chrony  4096 Feb 24 20:10 ./


It seems the daemon is not running and no logs are created or updated.

The interesting thing is that chronyd seems to be started by
"service chrony start" and then seems to die immediately after
beginning to write some logs:

  # mv /var/log/chrony/* /root/
  # ls -altrF /var/log/chrony/
  total 8
  drwxr-xr-x 10 rootroot4096 Feb 24 11:09 ../
  drwxr-xr-x  2 _chrony _chrony 4096 Feb 24 20:14 ./
  # ps ax | grep chrony
  12097 pts/0S+ 0:00 grep chrony
  # service chrony restart
  [ ok ] Stopping time daemon: chronyd.
  [ ok ] Starting time daemon: chronyd.
  # ps ax | grep chrony
  12166 pts/0S+ 0:00 grep chrony
  # chronyc tracking
  506 Cannot talk to daemon
  # ls -altrF /var/log/chrony/
  total 12
  drwxr-xr-x 10 rootroot4096 Feb 24 11:09 ../
  -rw-r--r--  1 _chrony _chrony  528 Feb 24 20:15 tracking.log
  -rw-r--r--  1 _chrony _chrony0 Feb 24 20:15 measurements.log
  drwxr-xr-x  2 _chrony _chrony 4096 Feb 24 20:15 ./
  # cat /var/log/chrony/tracking.log
  
===
 Date (UTC) Time IP Address   St   Freq ppm   Skew ppm Offset L Co  
Offset sd Rem. corr. Root delay Root disp. Max. error
  
===
  2019-02-24 19:15:15 0.0.0.0  0-63.127  0.106  0.000e+00 

Bug#923177: Firmware load failure - clean up

[Brian Holaday]

Package: firmware-atheros
Version: 20190114-1~bpo9+2
Severity: important

Firmware: Qualcomm Atheros QCA9377 802.11ac

Issue:
Installing the wireless driver works just fine : bluetooth seems to need a
restart each time I connect my headphones each time. The main issue I am
seeing is that I show several errors with missing firmware on
startup/shutdown. There are a few times where the key is never removed but
the system shuts down anyhow.

Log from gnome-logs:
ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
ath10k_pci :02:00.0: firmware: failed to load
ath10k/cal-pci-:02:00.0.bin (-2)
ath10k_pci :02:00.0: firmware: failed to load
ath10k/pre-cal-pci-:02:00.0.bin (-2)

Bug#923072: RM: why/2.40-3+b1 from testing

[Paul Gevers]

Control: reassign -1 release.debian.org
Control: tags -1 pending

On 24-02-2019 19:56, Ralf Treinen wrote:
> Hi Paul,
> 
> On Sun, Feb 24, 2019 at 07:41:37PM +0100, Paul Gevers wrote:
>> Control: reassign -1 ftp.debian.org
>> Control: retitle -1 RM: why -- ROM; Dependency why3 too new in unstable
>>
>> Hi Ralf
>>
>> Removals are normally requested from unstable. Once removed there, they
>> automatically are removed from testing.
>>
>> On 23-02-2019 21:26, Ralf Treinen wrote:
>>> why depends on why3. However, the version of why in testing, as well as
>>> the newest version of why published by ustream, need a version of why3
>>> <= 0/88.3 which is older than the version of why3 that we have in
>>> testing or in unstable.
>> 
>> Is why it should be removed from unstable for sure.
> 
> I think that would be premature. I first want to check with upstream
> whether they intend to update why to support the latest version of
> why3. If that happens then it certainly will be too late for buster
> but we still would like to update the why package in that case.

Thanks for explaining this.

elbrus@respighi:~$ dak rm --no-action --suite=testing why
Will remove the following packages from testing:

libwhy-coq | 2.40-3 | all
   why | 2.40-3 | source
   why |  2.40-3+b1 | amd64, arm64, armhf, i386, ppc64el, s390x

Maintainer: Debian OCaml Maintainers 

--- Reason ---

Ok. Will add the removal hint.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#923175: rust-getopts: Please upload 0.2.18

[Reiner Herrmann]

Source: rust-getopts
Version: 0.2.17-1
Severity: wishlist

Dear maintainer,

I noticed that rust-getopts 0.2.18-1 is already available in git [0]
for several months, but has not been uploaded yet.
This version [1] has a new feature (Matches::opt_get(_default)) that would
be nice to have.
Can you please upload it to unstable (preferrably so that it still
reaches buster)?

Kind regards,
  Reiner

[0] 
https://salsa.debian.org/rust-team/debcargo-conf/tree/master/src/getopts/debian
[1] https://github.com/rust-lang-nursery/getopts/releases/tag/v0.2.18


signature.asc
Description: PGP signature

Bug#923072: RM: why/2.40-3+b1 from testing

[Ralf Treinen]

Hi Paul,

On Sun, Feb 24, 2019 at 07:41:37PM +0100, Paul Gevers wrote:
> Control: reassign -1 ftp.debian.org
> Control: retitle -1 RM: why -- ROM; Dependency why3 too new in unstable
> 
> Hi Ralf
> 
> Removals are normally requested from unstable. Once removed there, they
> automatically are removed from testing.
> 
> On 23-02-2019 21:26, Ralf Treinen wrote:
> > why depends on why3. However, the version of why in testing, as well as
> > the newest version of why published by ustream, need a version of why3
> > <= 0/88.3 which is older than the version of why3 that we have in
> > testing or in unstable.
> 
> Is why it should be removed from unstable for sure.

I think that would be premature. I first want to check with upstream
whether they intend to update why to support the latest version of
why3. If that happens then it certainly will be too late for buster
but we still would like to update the why package in that case.

-Ralf.

Bug#923176: stretch-pu: package ca-certificates-java/20170929~deb9u1

[tony mancill]

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

This update closes #922720 [1], which addresses a bashism that prevents
the package upgrade from completing successfully.  

The debdiff for the proposed update is attached.

Thank you,
tony

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922720
diff -Nru ca-certificates-java-20170929~deb9u1/debian/changelog 
ca-certificates-java-20170929~deb9u2/debian/changelog
--- ca-certificates-java-20170929~deb9u1/debian/changelog   2019-02-11 
04:14:23.0 -0800
+++ ca-certificates-java-20170929~deb9u2/debian/changelog   2019-02-24 
09:55:04.0 -0800
@@ -1,3 +1,10 @@
+ca-certificates-java (20170929~deb9u2) stretch; urgency=medium
+
+  * Team upload.
+  * Address bashisms in postinst and jks-keystore (Closes: #922720)
+
+ -- tony mancill   Sun, 24 Feb 2019 09:55:04 -0800
+
 ca-certificates-java (20170929~deb9u1) stretch; urgency=medium
 
   * Rebuild for stretch.
diff -Nru ca-certificates-java-20170929~deb9u1/debian/jks-keystore.hook.in 
ca-certificates-java-20170929~deb9u2/debian/jks-keystore.hook.in
--- ca-certificates-java-20170929~deb9u1/debian/jks-keystore.hook.in
2019-02-11 04:14:23.0 -0800
+++ ca-certificates-java-20170929~deb9u2/debian/jks-keystore.hook.in
2019-02-24 09:55:04.0 -0800
@@ -53,7 +53,7 @@
 # the jre is not yet configured, but jvm.cfg is needed to run it
 temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
 mkdir -p /etc/${jvm%-$arch}
-if [ "$arch" == "armhf" ]; then
+if [ "$arch" = "armhf" ]; then
 printf -- "-client KNOWN\n-server ALIASED_TO -client\n" > $temp_jvm_cfg
 else
 printf -- "-server KNOWN\n" > $temp_jvm_cfg
diff -Nru ca-certificates-java-20170929~deb9u1/debian/postinst.in 
ca-certificates-java-20170929~deb9u2/debian/postinst.in
--- ca-certificates-java-20170929~deb9u1/debian/postinst.in 2019-02-11 
04:14:23.0 -0800
+++ ca-certificates-java-20170929~deb9u2/debian/postinst.in 2019-02-24 
09:55:04.0 -0800
@@ -52,7 +52,7 @@
 
 # Forcibly remove diginotar cert (LP: #920758)
 if [ -n "$FIXOLD" ]; then
-echo -e "-diginotar_root_ca\n-diginotar_root_ca_pem" | \
+printf "-diginotar_root_ca\n-diginotar_root_ca_pem\n" | \
 java -Xmx64m -jar $JAR -storepass "$storepass"
 fi
 
@@ -100,7 +100,7 @@
 # the jre is not yet configured, but jvm.cfg is needed to run 
it
 temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
 mkdir -p /etc/${jvm%-$arch}
-if [ "$arch" == "armhf" ]; then
+if [ "$arch" = "armhf" ]; then
printf -- "-client KNOWN\n-server ALIASED_TO -client\n" 
> $temp_jvm_cfg
 else
printf -- "-server KNOWN\n" > $temp_jvm_cfg


signature.asc
Description: PGP signature

Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used

[Thorsten Glaser]

retitle 920459 tabu: breaks with color and/or xcolor when spread or negative X 
coefficients are used
found 920459 2018.20190131-1
forwarded 920459 https://github.com/tabu-fixed/tabu/pull/14
tags 920459 + patch
thanks

Hi Norbert,

please find attached a patch that fixes tabu when either color or
xcolor are used in a document and tabu is used with either stretch
(instead of to) or negative X column coëfficients. I’ve also for‐
warded this upstream.

I would appreciate a quick review, as this is blocking multiple
other packages and release-critical, and would prefer to upload
this within five days or so. If you can give me a go I can do a
maintainer-approved undelayed NMU. If I don’t hear anything back,
I intend to do a regular delayed NMU in five days. I’ve tested
this by rebuilding src:bliss twice, once without once with this
patch applied, failing the former but passing the latter.

Thanks,
//mirabilos
-- 
[17:15:07] Lukas Degener: Kleines Asterix-Latinum für Softwaretechniker:
   veni, vidi, fixi(t) ;-)diff -Nru texlive-extra-2018.20190131/debian/changelog 
texlive-extra-2018.20190131/debian/changelog
--- texlive-extra-2018.20190131/debian/changelog2019-01-31 
04:55:18.0 +0100
+++ texlive-extra-2018.20190131/debian/changelog2019-02-24 
17:47:26.0 +0100
@@ -1,3 +1,10 @@
+texlive-extra (2018.20190131-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Patch tabu to fix multiple FTBFS in other packages (Closes: #920459)
+
+ -- Thorsten Glaser   Sun, 24 Feb 2019 17:47:26 +0100
+
 texlive-extra (2018.20190131-1) unstable; urgency=medium
 
   * new upstream checkout
diff -Nru texlive-extra-2018.20190131/debian/patches/fix-tabu-920459 
texlive-extra-2018.20190131/debian/patches/fix-tabu-920459
--- texlive-extra-2018.20190131/debian/patches/fix-tabu-920459  1970-01-01 
01:00:00.0 +0100
+++ texlive-extra-2018.20190131/debian/patches/fix-tabu-920459  2019-02-24 
17:47:21.0 +0100
@@ -0,0 +1,23 @@
+# DP: see #920459 and https://github.com/tabu-fixed/tabu/issues/1
+# DP: forwarded as https://github.com/tabu-fixed/tabu/pull/14
+
+--- a/texmf-dist/source/latex/tabu/tabu.dtx
 b/texmf-dist/source/latex/tabu/tabu.dtx
+@@ -6099,6 +6099,7 @@ morekeywords=[7]{yellow},
+ \ifdim \tabu@temp\p@>\z@ \ifdim \tabu@temp\tabucolX<\tabu@target
+ \tabu@target=\tabu@temp\tabucolX 
\fi\fi
+ \setbox\tabu@box  \hbox \bgroup
++\color@begingroup%
+ \begin{varwidth}\tabu@target
+ \let\FV@ListProcessLine \tabu@FV@ListProcessLine  % \hbox to 
natural width...
+ \narrowragged \arraybackslash \parfillskip \@flushglue
+--- a/texmf-dist/tex/latex/tabu/tabu.sty
 b/texmf-dist/tex/latex/tabu/tabu.sty
+@@ -1663,6 +1663,7 @@
+ \ifdim \tabu@temp\p@>\z@ \ifdim \tabu@temp\tabucolX<\tabu@target
+ \tabu@target=\tabu@temp\tabucolX 
\fi\fi
+ \setbox\tabu@box  \hbox \bgroup
++\color@begingroup%
+ \begin{varwidth}\tabu@target
+ \let\FV@ListProcessLine \tabu@FV@ListProcessLine  % \hbox to 
natural width...
+ \narrowragged \arraybackslash \parfillskip \@flushglue
diff -Nru texlive-extra-2018.20190131/debian/patches/series 
texlive-extra-2018.20190131/debian/patches/series
--- texlive-extra-2018.20190131/debian/patches/series   2018-12-11 
04:24:38.0 +0100
+++ texlive-extra-2018.20190131/debian/patches/series   2019-02-24 
17:44:44.0 +0100
@@ -4,3 +4,4 @@
 tmp-dir-for-pdfjam
 sympytex-path
 fix-gbrief-multiple
+fix-tabu-920459

Bug#915559: Heads up on the inactivity.

[Per Sandberg]

Dear maintainer

This bug is probably very the root-cause to the following bug chain:

ThisBug#915559: coreutils: Use renameat2 from glibc instead of syscall
  Leading to: Bug#921924: fakechroot: mv(1) cannot be used inside fakechroot
    Leading to: Bug#922572: debootstrap variant fakeroot fails due to dash 
diversion.

And maybe a heap load of others so is it possible to get it fixed.


/Regards
/P