Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

[Andreas Tille]

Hi,

On Tue, Feb 26, 2019 at 03:13:39PM +0800, Drew Parsons wrote:
> On 2019-02-26 14:54, Andreas Tille wrote:
> > 
> > I just pushed
> > +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium
> ...
> > to Git.  Is there any reason not to upload this and simply fix #883619.
> > Looks like a pretty low hanging fruit to fix an RC bug and save the
> > package for Buster that I can not imagine nobody else would have
> > harvested it.
> 
> It's only downstream dependency is colmap. If colmap is happy with the new
> version then it sounds like a good idea to upload it, especially if it fixes
> an RC bug.

I mean: There is no *effective* change since the Build-Depends we set is
fullfilled anyway by the existing packages.  Its just that it is
explicitly declared in the package metadata.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#923226: Compiling shader doesn't work - game doesn't work

[Simon McVittie]

Control: reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1
Control: tags -1 + moreinfo

On Mon, 25 Feb 2019 at 09:31:51 +0100, Julien Puydt wrote:
> openarena doesn't work anymore because it doesn't manage to compile its
> shaders.

This is almost certainly a problem with the ioquake3 engine rather than
the OpenArena game, so I'm reassigning it.

> Trying to load "renderer_opengl2_x86_64.so" from "/usr/lib/ioquake3"...
...
> Trying to get an OpenGL 3.2 core context
> SDL_GL_CreateContext failed: Could not create GL context: GLXBadFBConfig

Does the opengl1 renderer work? (See /usr/share/doc/ioquake3/NEWS.Debian.gz)

If not, does an older version of ioquake3 from snapshot.debian.org work?

Unfortunately ioquake3 does not have the ability to fall back from one
renderer module to another if the default doesn't work.

> GL_RENDERER: Mesa DRI Intel(R) Ironlake Mobile 

Ironlake is an Intel graphics generation from 2010, so it's entirely
possible that the opengl2 renderer requires newer hardware than that.

smcv

Bug#923068: [pkg-gnupg-maint] Bug#923068: pinentry-gtk2 takes more than twenty seconds to appear

[Daniel Kahn Gillmor]

Control: tags 923068 + moreinfo

Hi fc--

On Sat 2019-02-23 20:16:03 +0100, fc wrote:
> When pinentry-gtk2 is started, the input window appears after more
> than twenty seconds. For comparison pinentry-gnome3 and pinentry-qt
> appear in less than two seconds for the same request.

Can you take a look at https://bugs.debian.org/800032 to see whether
anything there looks like it might be a functioning workaround for you?

also, it's not clear to me whether you've tried pinentry-gtk2 directly,
or whether you're measuring a delay from the use of (for example) gpg or
gpgsm, via gpg-agent.

to test pinentry-gtk2 on its own, i'd recommend doing the following from
a terminal:

echo getpin | pinentry-gtk-2

This should prompt you (immediately!) for a passphrase, and then echo
that passphrase to stdout.  for example:

0 dkg@alice:~$ echo getpin | pinentry-gtk-2 
OK Pleased to meet you
D abvc
OK
0 dkg@alice:~$

Does that cause the delay for you?  If not, what steps *do* cause the
delay?

Regards,

 --dkg

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

[intrigeri]

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

> I prefer testing the parent directory.

BTW: s/sniplet/snippet/ I think :)

Cheers,
-- 
intrigeri

Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

[Drew Parsons]

On 2019-02-26 14:54, Andreas Tille wrote:


I just pushed
+ceres-solver (1.14.0-4) UNRELEASED; urgency=medium

...

to Git.  Is there any reason not to upload this and simply fix #883619.
Looks like a pretty low hanging fruit to fix an RC bug and save the
package for Buster that I can not imagine nobody else would have
harvested it.


It's only downstream dependency is colmap. If colmap is happy with the 
new version then it sounds like a good idea to upload it, especially if 
it fixes an RC bug.


Drew

Bug#923277: libaio1: failed to load wifi firmware after libaio1 update

[Lorenzo Crippa]

Hi,

the issue seems to be fixed with the latest version (0.3.112-3)

thanks a lot!

Bug#923312: gnome-terminal ignores system ulimits

[Harald Dunkel]

Package: gnome-terminal
Version: 3.22.2-1

My /etc/security/limits.d/local.conf says

* soft nofile 4096
* hard nofile 16584
root soft nofile 4096
root hard nofile 16584

But within gnome-terminal I just get

% egrep ^Limit\|open /proc/$$/limits
Limit Soft Limit   Hard Limit   
Units
Max open files1024 4096 
files

Using other terminal emulators (xterm, xfce4-terminal) there
is no such problem.

This breaks my apps. gnome-terminal and gnome-terminal-server
should resepct the ulimits initially set via pam_limits.so at
login time and inherited from the calling process.


Regards
Harri

Bug#923311: steam: Client crash

[Moshe Piekarski]

Package: steam
Version: 1.0.0.59-4
Severity: important

Dear Maintainer,

On aproximatly 60% of attempts to login to steam using the client system 
freezes (Ctrl+Alt+Fx doesn't work, Sysrq appears to have no affect, and the 
xterm with journalctl -f running shows nothing).
This seems to be more common when my system has been running for a while.

Thank you for your time.

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

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

Versions of packages steam depends on:
ii  debconf [debconf-2.0]  1.5.70
ii  libc6  2.28-7
ii  libgl1-mesa-dri18.3.2-1
ii  libgl1-mesa-glx18.3.2-1
ii  libgpg-error0  1.35-1
ii  libstdc++6 8.2.0-20
ii  libudev1   240-6
ii  libx11-6   2:1.6.7-1
ii  libxcb-dri3-0  1.13.1-2
ii  libxinerama1   2:1.1.4-2
ii  xz-utils   5.2.4-1

Versions of packages steam recommends:
ii  ca-certificates  20190110
ii  fontconfig   2.13.1-2
ii  fonts-liberation 1:1.07.4-9
ii  libxss1  1:1.2.3-1
ii  mesa-vulkan-drivers  18.3.2-1
ii  steam-devices1.0.0.59-4
ii  xterm [x-terminal-emulator]  343-1

Versions of packages steam suggests:
pn  nvidia-driver-libs-i386  
pn  nvidia-vulkan-icd

Versions of packages steam is related to:
ii  libc6   2.28-7
ii  libgl1  1.1.0-1
ii  libgl1-mesa-dri 18.3.2-1
ii  libglx-mesa0 [libglx-vendor]18.3.2-1
ii  libglx-nvidia0 [libglx-vendor]  390.87-8
ii  libxcb-dri3-0   1.13.1-2
pn  nvidia-driver   
pn  nvidia-driver-libs  
pn  nvidia-driver-libs-i386 

-- debconf information:
* steam/license:
* steam/need-nvidia-i386:
  steam/purge:
* steam/question: I AGREE

Bug#923310: ITS: ninja-build

[Mo Zhou]

Source: ninja-build
X-Debbugs-CC: fge...@debian.org

Hi Felix,

The last upload for ninja-build dates back to more than 1 year ago.
The package looks quite old since it has an ancient std-ver.

I intend to help update the package and import the latest upstream
version 1.9.0 then upload it to unstable, does that sound good to you?
This could be either an ITS or an NMU, at your preference.

I wanted to fix [1] but clearly we cannot do that at this stage.

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

Bug#868355: Shouldn't bug #868355 be closed since we now have ceres-solver (1.14.0-3)

[Andreas Tille]

Hi,

this bug is requesting binNMU for ceres-solver_1.12.0+dfsg0-1 but currently
wie have

$ rmadison ceres-solver
ceres-solver | 1.12.0+dfsg0-1 | stable | source
ceres-solver | 1.12.0+dfsg0-1 | stable-debug   | source
ceres-solver | 1.14.0-3   | testing| source
ceres-solver | 1.14.0-3   | unstable   | source
ceres-solver | 1.14.0-3   | unstable-debug | source


>From my point of view this bug is irrelevant and should be closed.

Am I missing something?

Kind regards

   Andreas.


-- 
http://fam-tille.de

Bug#903982: Patch for #903982

[Andrius Merkys]

control: tags 903982 + patch

Hello,

please find attached a patch to fix this issue. An alternative
suggestion would be to repack the source to exclude XQLParser/Parser.pm.

Best,
Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

diff -Nru libxml-xql-perl-0.68/debian/changelog 
libxml-xql-perl-0.68/debian/changelog
--- libxml-xql-perl-0.68/debian/changelog   2018-07-18 11:18:52.0 
-0400
+++ libxml-xql-perl-0.68/debian/changelog   2019-02-26 01:48:47.0 
-0500
@@ -3,8 +3,9 @@
   * debian/copyright: updating format specification.
   * debian/copyright: updating the format.
   * Bumping compat level to 11.
+  * debian/rules: force-regenerating XML::XQL::Parser (Closes: #903982)
 
- -- Andrius Merkys   Wed, 18 Jul 2018 17:18:52 +0200
+ -- Andrius Merkys   Tue, 26 Feb 2019 01:48:47 -0500
 
 libxml-xql-perl (0.68-7) unstable; urgency=medium
 
diff -Nru libxml-xql-perl-0.68/debian/rules libxml-xql-perl-0.68/debian/rules
--- libxml-xql-perl-0.68/debian/rules   2018-07-18 11:18:52.0 -0400
+++ libxml-xql-perl-0.68/debian/rules   2019-02-26 01:47:24.0 -0500
@@ -6,6 +6,10 @@
 %:
dh $@
 
+override_dh_auto_build:
+   mv XQLParser/Parser.pm debian
+   dh_auto_build
+
 override_dh_auto_install:
dh_auto_install
$(RM) -r $(CURDIR)/debian/libxml-xql-perl/usr/bin
@@ -13,3 +17,7 @@
 override_dh_installexamples:
dh_installexamples
sed -i '1s|^#!.*perl.*$$|#!/usr/bin/perl -w|' 
$(TMP)/usr/share/doc/$(PACKAGE)/examples/*
+
+override_dh_auto_clean:
+   dh_auto_clean
+   -test -e debian/Parser.pm && mv debian/Parser.pm XQLParser

Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

[Andreas Tille]

Hi,

I just pushed


diff --git a/debian/changelog b/debian/changelog
index db364aa..a10efd1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ceres-solver (1.14.0-4) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Bump versioned Build-Depends: libeigen3-dev (>= 3.3.4)
+Closes: #883619
+
+ -- Andreas Tille   Tue, 26 Feb 2019 07:50:37 +0100
+
 ceres-solver (1.14.0-3) unstable; urgency=medium
 
   * Updated years in debian/copyright
diff --git a/debian/control b/debian/control
index da66ec7..108192c 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11~),
libatlas-base-dev,
libgoogle-glog-dev,
libgflags-dev,
-   libeigen3-dev (>= 3.2.1),
+   libeigen3-dev (>= 3.3.4),
libsuitesparse-dev (>= 1:4.4.3),
python,
python3-sphinx,


to Git.  Is there any reason not to upload this and simply fix #883619.
Looks like a pretty low hanging fruit to fix an RC bug and save the
package for Buster that I can not imagine nobody else would have
harvested it.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#923273: [pkg-apparmor] Bug#923273: apparmor: nvidia_modprobe named profile is shipped in complain mode

[intrigeri]

> After latest upgrade I've discovered via `aa-status` that new named profile 
> `nvidia_modrpobe` is loaded in complain mode:

Good catch!

That's because debian/rules does this:

# set all profiles in apparmor-profiles to complain mode
cd $(CURDIR)/debian/tmp && sh 
$(CURDIR)/debian/put-all-profiles-in-complain-mode.sh

… which unfortunately, now that the apparmor binary package ships its
first profile (previously it only shipped abstractions), sets it to
complain mode.

I'll try to prepare a fix ASAP unless you tell me you're on it.

Bug#923309: cacti-spine_1.1.37-2~bpo9+1 fails to run under non-root user

[Paul Allen]

Package: cacti-spine
Version: 1.1.37-1~bpo9+1
Severity: normal

Dear Maintainer,


   * What led up to the situation?
Upgrading from cacti-spine_1.1.37-1~bpo9+1 to 
cacti-spine_1.1.37-2~bpo9+1 caused execution of cacti-spine for non-root users 
to break, even with setuid bits set for either just user or all.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Attempted to set setuid bits on /usr/sbin/spine to permit execution by 
non-root users (eg, cacti). Attempted to debug by running "/usr/sbnin/spine 
-H=180 -R -S -V=5" and "/usr/sbin/spine -h" as both root and cacti users.
   * What was the outcome of this action?
/usr/sbin/spine would fail silently when executed by cacti user but 
would run successfully when executed by root user. Example: 
cacti@mon1:~# /usr/sbin/spine -H=180 -R -S -V=5
cacti@mon1:~#
cacti@mon1:~# /usr/sbin/spine -h
cacti@mon1:~#

   * What outcome did you expect instead?
Expected spine to execute successfully for non-root cacti user once 
setuid bit(s) were set.

Re-installing cacti-spine_1.1.37-2~bpo9+1 had no effect, Removing and re-adding 
setuid bits had no effect. Once I rolled the package back to 
cacti-spine_1.1.37-1~bpo9+1 and set the setuid bit for the user it started 
executing successfully again for the no-root cacti user with no other changes 
necessary.



-- 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-6-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 cacti-spine depends on:
ii  cacti  1.1.38+ds1-1~bpo9+1
ii  dbconfig-no-thanks 2.0.11~bpo9+1
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u4
ii  libmariadbclient18 10.1.37-0+deb9u1
ii  libsnmp30  5.7.3+dfsg-1.7+deb9u1
ii  ucf3.0036

cacti-spine recommends no packages.

Versions of packages cacti-spine suggests:
ii  snmp-mibs-downloader  1.1+nmu1

-- no debconf information

Bug#923308: ITP: libnfsidmap-regex -- Plugin to map regex NFSv4 names to and from ids

[Gürkan Myczko]

Package: wnpp
Severity: wishlist

* Package name: libnfsidmap-regex
  Version : 1.0
  Upstream Authors: Stefan Walter 
David Härdeman 
The Regents of the University of Michigan
Andy Adamson 
* URL : https://github.com/isginf/libnfsidmap-regex
* License : BSD-3-clause
  Description : Plugin to map regex NFSv4 names to and from ids
 The regex plugin parses NFSv4 user and groups names using regex to 
extract the
 local user or group. NFSv4 names are created by adding constant strings 
before

 and after the local user and group names.

Package is availabe at http://phd-sid.ethz.ch/debian/libnfsidmap-regex/

Bug#923307: coquelicot: Uploading file fails

[Joseph Nuthalapati]

Package: coquelicot
Version: 0.9.6-1.1
Severity: serious

On Debian testing (Buster), uploading files to Coquelicot results in a
500 error. This error makes the primary function of Coquelicot -
uploading and sharing files, unusable.

Please see the attached error log for the corresponding errors in the
log file.

-- 
Regards,
Joseph Nuthalapati
10.0.2.2 - - [26/Feb/2019:05:38:15 +] "POST /coquelicot/authenticate HTTP/1.1" 200 2 0.0010
E, [2019-02-26T05:38:32.731272 #4169] ERROR -- : app error: undefined method `rewind' for # (NoMethodError)
E, [2019-02-26T05:38:32.731427 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/multipart.rb:45:in `extract_multipart'
E, [2019-02-26T05:38:32.731461 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/request.rb:472:in `parse_multipart'
E, [2019-02-26T05:38:32.731481 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/request.rb:335:in `POST'
E, [2019-02-26T05:38:32.731501 #4169] ERROR -- : (erb):225:in `pretty'
E, [2019-02-26T05:38:32.731522 #4169] ERROR -- : /usr/lib/ruby/2.5.0/erb.rb:876:in `eval'
E, [2019-02-26T05:38:32.731542 #4169] ERROR -- : /usr/lib/ruby/2.5.0/erb.rb:876:in `result'
E, [2019-02-26T05:38:32.731561 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:82:in `pretty'
E, [2019-02-26T05:38:32.731580 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:31:in `rescue in call'
E, [2019-02-26T05:38:32.731600 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:21:in `call'
E, [2019-02-26T05:38:32.731621 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:194:in `call'
E, [2019-02-26T05:38:32.731641 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1957:in `call'
E, [2019-02-26T05:38:32.731661 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/upr/input_wrapper.rb:48:in `call'
E, [2019-02-26T05:38:32.731681 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/xss_header.rb:18:in `call'
E, [2019-02-26T05:38:32.731695 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/path_traversal.rb:16:in `call'
E, [2019-02-26T05:38:32.731707 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/json_csrf.rb:26:in `call'
E, [2019-02-26T05:38:32.731719 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call'
E, [2019-02-26T05:38:32.731732 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call'
E, [2019-02-26T05:38:32.731750 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/frame_options.rb:31:in `call'
E, [2019-02-26T05:38:32.731772 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:232:in `context'
E, [2019-02-26T05:38:32.731794 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:226:in `call'
E, [2019-02-26T05:38:32.731817 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/null_logger.rb:9:in `call'
E, [2019-02-26T05:38:32.731833 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/head.rb:12:in `call'
E, [2019-02-26T05:38:32.731845 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:194:in `call'
E, [2019-02-26T05:38:32.731857 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1957:in `call'
E, [2019-02-26T05:38:32.731869 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1502:in `block in call'
E, [2019-02-26T05:38:32.731887 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1729:in `synchronize'
E, [2019-02-26T05:38:32.731909 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1502:in `call'
E, [2019-02-26T05:38:32.731930 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:68:in `block in call'
E, [2019-02-26T05:38:32.731953 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:53:in `each'
E, [2019-02-26T05:38:32.731969 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:53:in `call'
E, [2019-02-26T05:38:32.731981 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/common_logger.rb:33:in `call'
E, [2019-02-26T05:38:32.731993 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:231:in `call'
E, [2019-02-26T05:38:32.732007 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/chunked.rb:54:in `call'
E, [2019-02-26T05:38:32.732029 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/content_length.rb:15:in `call'
E, [2019-02-26T05:38:32.732051 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rainbows/process_client.rb:43:in `process_loop'
E, [2019-02-26T05:38:32.732073 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rainbows/thread_spawn.rb:36:in `block (3 levels) in accept_loop'



signature.asc
Description: OpenPGP digital signature

Bug#923305: libgtk-3: Selection mode no longer shows checkboxes

[Mohammed Sadiq]

Package: libgtk-3-bin
Version: 3.24.5-1
Severity: important
File: libgtk-3

After update to gtk3 version 3.24.5 selection mode in gtk applications
no longer shows checkboxes.  For example, this affects packages like
bijiben (with some notes, press check button) and gnome-clocks (in world-clocks,
press check button with some clocks).

-- 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_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgtk-3-bin depends on:
ii  gtk-update-icon-cache  3.24.5-1
ii  libc6  2.28-7
ii  libcairo2  1.16.0-2
ii  libglib2.0-0   2.58.3-1
ii  libgtk-3-0 3.24.5-1
ii  libgtk-3-common3.24.5-1

libgtk-3-bin recommends no packages.

libgtk-3-bin suggests no packages.

-- no debconf information

Bug#923306: unblock: kazam/1.4.5-2.1

[Nicolas Braud-Santoni]

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

Please unblock package kazam.

It's a popular option for screen capture (both screenshots and video), and we
don't seem to have alternatives for it in the archive, that work out-of-the-box.
(That was the reason I used it in the first place.)


I performed a NMU early this month, to solve the bug that got it removed from
testing:

  $ debdiff kazam_1.4.5-2.dsc /opt/deb/buildarea/kazam_1.4.5-2.1.dsc 
  diff -Nru kazam-1.4.5/debian/changelog kazam-1.4.5/debian/changelog
  --- kazam-1.4.5/debian/changelog2015-10-13 03:33:29.0 +0200
  +++ kazam-1.4.5/debian/changelog2019-02-08 12:24:25.0 +0100
  @@ -1,3 +1,11 @@
  +kazam (1.4.5-2.1) unstable; urgency=high
  +
  +  * Non-maintainer upload.
  +  * Patch after configuration API change (Closes: #916416)
  +  * debian/control: Add missing build dependency on dh-python
  +
  + -- Nicolas Braud-Santoni   Fri, 08 Feb 2019 12:24:25 +0100
  +
   kazam (1.4.5-2) unstable; urgency=medium
   
 * configparser_api_changes.patch: Update for changes
  diff -Nru kazam-1.4.5/debian/control kazam-1.4.5/debian/control
  --- kazam-1.4.5/debian/control  2015-10-13 03:32:51.0 +0200
  +++ kazam-1.4.5/debian/control  2019-02-08 12:24:25.0 +0100
  @@ -3,6 +3,7 @@
   Priority: optional
   Maintainer: Andrew Starr-Bochicchio 
   Build-Depends: debhelper (>= 9),
  +   dh-python,
  gettext,
  intltool,
  python3-all (>= 3.2),
  diff -Nru kazam-1.4.5/debian/patches/fix-configuration-handling.patch 
kazam-1.4.5/debian/patches/fix-configuration-handling.patch
  --- kazam-1.4.5/debian/patches/fix-configuration-handling.patch 1970-01-01 
01:00:00.0 +0100
  +++ kazam-1.4.5/debian/patches/fix-configuration-handling.patch 2019-02-08 
12:24:25.0 +0100
  @@ -0,0 +1,51 @@
  +Subject: Fix configuration handling
  +
  +Origin: vendor
  +Bug: https://bugs.debian.org/916416
  +Forwarded: https://github.com/hzbd/kazam/pull/21
  +From: Sergey Spitsyn 
  +Reviewed-by: Nicolas Braud-Santoni 
  +Last-Update: 2019-02-07
  +Applied-Upstream: no
  +
  +---
  + kazam/backend/config.py | 11 ---
  + 1 file changed, 4 insertions(+), 7 deletions(-)
  +
  +diff --git a/kazam/backend/config.py b/kazam/backend/config.py
  +index 64b5117..2274435 100644
  +--- a/kazam/backend/config.py
   b/kazam/backend/config.py
  +@@ -73,7 +73,7 @@ class KazamConfig(ConfigParser):
  + CONFIGFILE = os.path.join(CONFIGDIR, "kazam.conf")
  + 
  + def __init__(self):
  +-ConfigParser.__init__(self, self.DEFAULTS[0]['keys'])
  ++super().__init__(self)
  + if not os.path.isdir(self.CONFIGDIR):
  + os.makedirs(self.CONFIGDIR)
  + if not os.path.isfile(self.CONFIGFILE):
  +@@ -98,10 +98,9 @@ class KazamConfig(ConfigParser):
  + if d_key == key:
  + return d_section["keys"][key]
  + 
  +-def get(self, section, key, raw=True, fallback=None):
  ++def get(self, section, key, **kwargs):
  + try:
  +-return super(KazamConfig, self).get(section,
  +- key, raw=True, fallback=fallback)
  ++return super(KazamConfig, self).get(section, key, **kwargs)
  + except NoSectionError:
  + default = self.find_default(section, key)
  + self.set(section, key, default)
  +@@ -123,9 +122,7 @@ class KazamConfig(ConfigParser):
  + def set(self, section, option, value):
  + # If the section referred to doesn't exist (rare case),
  + # then create it
  +-if not self.has_section(section):
  +-self.add_section(section)
  +-ConfigParser.set(self, section, option, str(value))
  ++super().set(section, option, str(value))
  + 
  + def write(self):
  + file_ = open(self.CONFIGFILE, "w")
  diff -Nru kazam-1.4.5/debian/patches/series kazam-1.4.5/debian/patches/series
  --- kazam-1.4.5/debian/patches/series   2015-10-13 03:23:18.0 +0200
  +++ kazam-1.4.5/debian/patches/series   2019-02-08 12:24:25.0 +0100
  @@ -1 +1,2 @@
   configparser_api_changes.patch
  +fix-configuration-handling.patch


Best,

  nicoo


unblock kazam/1.4.5-2.1

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

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

Bug#923304: texlive-pstricks: plain tex fails with Undefined control sequence on \scantokens after input of pstricks.

[P V Mathew]

Package: texlive-pstricks
Version: 2018.20190131-2
Severity: important

Dear Maintainer,

   * What led up to the situation?
Input of pstricks fails with plain tex.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Trying to compile plain tex file containing \input pstricks
fails.
   * What was the outcome of this action?
Undefined contorl sequence. First two lines which reads
! Undefined control sequence.
\pgfkeyssetevalue ...gfkeys@temptoks =\scantokens

   * What outcome did you expect instead?
   Expected a clean compile.

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


-- Package-specific info:
##
minimal input file
\input pstricks
\bye

##
other files

This is TeX, Version 3.14159265 (TeX Live 2019/dev/Debian) (preloaded 
format=tex)
(./test.tex (/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks.tex
(/usr/share/texlive/texmf-dist/tex/generic/pstricks/pstricks-tex.def
we are running tex and have to make it etex and latex compatible ...
) (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/pst-xkey.tex
2005/11/25 v1.6 PSTricks specialization of xkeyval (HA)
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex))
2014/12/03 v2.7a key=value parser (HA)
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvtxhdr.tex
2005/02/22 v1.1 xkeyval TeX header (HA
(/usr/share/texlive/texmf-dist/tex/generic/pstricks/pst-fp.tex
`pst-fp' v0.05, 2010/01/17 (hv))
(/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common-lists.t
ex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfkeys.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfkeysfiltered.code.t
ex)) (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgffor.code.tex
Loading pgffor.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmath.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathcalc.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathutil.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathparser.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.code.tex
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.basic.code
.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.trigonomet
ric.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.random.cod
e.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.comparison
.code.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.base.code.
tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.round.code
.tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.misc.code.
tex)
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfunctions.integerari
thmetics.code.tex)))
(/usr/share/texlive/texmf-dist/tex/generic/pgf/math/pgfmathfloat.code.tex
! Undefined control sequence.
\pgfkeyssetevalue ...gfkeys@temptoks =\scantokens 
  \expandafter {\expandafter...

\pgfkeys@ifcsname ...\fi \ifpgfkeys@csname@test #2
  \else #3\fi 
\pgfkeys@ifcsname ...gfkeys@csname@test #2\else #3
  \fi 
\pgfkeys@ifcsname ...gfkeys@csname@test #2\else #3
  \fi 
\pgfkeys@unpack ...pgfeov \else \pgfkeys@case@one 
  \fi \fi 
\pgfkeys@@normal ...pgfkeysnovalue =\pgfkeys@stop 
  \pgfkeys@parse 
...
l.1089 }

? The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

? OK, entering \batchmode
##
 List of ls-R files

-rw-rw-r-- 1 root staff 5226 Feb 21 09:26 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 1200 Feb 26 11:01 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep  2 18:02 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 31 09:23 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 31 09:23 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 1101 Sep 11 11:29 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 31 09:23 /usr/share/texmf/web2c/fmtutil.cnf -> 

Bug#923303: ITP: mlv-app -- Magic Lantern Video processing

[Gürkan Myczko]

Package: wnpp
Severity: wishlist

* Package name: mlv-app
  Version : 1.5
  Upstream Authors: Ilia Sibiryakov, github:masc4ii, github:bouncyball
* URL : https://github.com/ilia3101/MLV-App
* License : GPL-3
  Description : Magic Lantern Video processing
 Kind of Lightroom, but for Magic Lantern MLV videos. You will need a
 Canon camera and the Magic Lantern auto loadable firmware extension
 to generate the format to process with this software.

Package is availabe at http://phd-sid.ethz.ch/debian/mlv-app/

For reference: https://magiclantern.fm/
There's also CHDK (for compact cameras of canon), but the ML is the real 
thing (see dual iso stuff)

Bug#921268: [mumble] Mumble's Audio Tuning Wizard doesn't play test samples/sounds, TTS is possibly also broken

[Chris Knadle]

forwarded 921268 https://github.com/mumble-voip/mumble/pull/3611
tags 921268 = fixed-upstream
thanks

This bug was caused by an error in the audio sample path:

https://github.com/mumble-voip/mumble/commit/c49301b0cb2689657953aca0b874f5eecfac4566

As this is something that can be given a targeted fix I'll see if I can get a
package with the fix uploaded before the full freeze.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us



signature.asc
Description: OpenPGP digital signature

Bug#782642: moc: when resized moc displays "terminal's too smal" when it's not

[Elimar Riesebieter]

Control: tags -1 unreproducible

* Elimar Riesebieter  [2019-02-16 13:13 +0100]:

> Hi Sébastien, 
> 
> * Sébastien Poher  [2015-04-15 16:08 +0200]:
> 
> > Package: moc
> > Version: 1:2.5.0-1
> > Severity: minor
> > Tags: patch
> > 
> > Dear Maintainer,
> > 
> > *** Reporter, please consider answering these questions, where appropriate 
> > ***
> > 
> >* What led up to the situation?
> > When moc is resized, for example when using a tilling window manager, it
> > dislays "terminal's too small" while the terminal size is still big enough 
> > to
> > display moc correctly.
> > I think that the threshold of lines and columns size is too high so I 
> > changed
> > them. With this values I got the "terminal's too small" mention only when it
> > gets really too small.
> 
> Could you please test version 1:2.6.0~svn-r2994-3. Upstream fixedd
> some "terminal is too small" issues, though.

Can't reproduce anymore. Closing this bug as there is no response
from the reporter.

Elimar
-- 
  Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)


signature.asc
Description: PGP signature

Bug#922690: mirror submission for mirror.sitsa.com.ar

[Franco E. Lazos - SiTSA Telecomunicaciones]

Hi,

Sorry for the inconvenience, here in English:

/*
Package: mirrors

Submission-Type: new
Site: mirror.sitsa.com.ar

Comment: Welcome to the mirror of the center, of the center of the country!

If you are in Argentina, it is possible that this mirror is useful according to 
our location and connectivity.
It is time to contribute to the Debian GNU / Linux community for its technical 
excellence and, among other purposes, because they are always attentive to the 
needs and expectations that arise.

The SiTSA Telecomunicaciones Team.-
*/

Best Regards,

P.S: currently, 1 Gbps is available for this mirror. Mirror's directories 
available: /debian, /debian-cd.

Franco E. Lazos
Departamento Técnico
SiTSA – Telecomunicaciones
Entre Rios 1435 – (X5900AGI) – Villa María – CBA-ARG
Fijo (54 353) 453-1146 | INT 107
Móvil (54 351) 248-2514
e-Mail franco.la...@sitsa.com.ar 
Website www.sitsa.com.ar  / www.trackmaster.com.ar
 
P Proteja el medio ambiente, no imprima este mail sino es necesario.
 
ATTORNEY - CLIENT PRIVILEGED INFORMATION
 
Este mensaje es privado y confidencial, y está dirigido exclusivamente  a su(s) 
destinatario(s). Si usted ha recibido este mensaje por error,  debe abstenerse 
de distribuirlo, copiarlo o usarlo en cualquier sentido. 
Asimismo, le agradecemos comunicarlo al remitente y borrar el mensaje y 
cualquier documento adjunto
 
This email and any files transmitted with it are confidential and  intended 
solely for the use of the individual or entity to whom they are  addressed.
Please notify the sender immediately by e-mail if you have received this e-mail 
by mistake and delete this e-mail from your system.

> El 25 feb. 2019, a las 06:25, Peter Palfrader  escribió:
> 
> On Tue, 19 Feb 2019, NOC SiTSA Telecomunicaciones wrote:
> 
>> Package: mirrors
> 
>> Submission-Type: new
>> Site: mirror.sitsa.com.ar
> 
>> Comment: ¡Bienvenido a la réplica del centro, del centro del país!
>> 
>> Si se encuentra en Argentina en general, es posible que esta réplica sea 
>> útil de acuerdo con nuestra ubicación y conectividad.
>> Es hora de contribuir a la comunidad Debian GNU / Linux por su excelencia 
>> técnica y, entre otros propósitos, porque siempre están atentos a las 
>> necesidades y expectativas que surgen.
>> 
>> El equipo de SiTSA Telecomunicaciones.-
> 
> Um, english please?
> 
> -- 
>|  .''`.   ** Debian **
>  Peter Palfrader   | : :' :  The  universal
> https://www.palfrader.org/ | `. `'  Operating System
>|   `-https://www.debian.org/

Bug#923302: libapache2-mod-gnutls: GnuTLSCache=dbm fails later restart of apache2

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2019-02-26 05:06:17)
> I experienced on multiple hosts that upgrading to the new
> libapache2-mod-gnutls went fine (I guess it simply reloaded apache2),
> but that a later server restart would fail.
> 
> Running "a2enmod socache_dbm" made apache2 work again.
> 
> Debian-shipped config enables GnuTLSCache, using dbm.
> Release 0.9.0 has GnuTLSSessionTickets enabled by default,
> which seems to make GnuTLSCache unneeded for most common use cases
> (exceptions being non-SNI needs and a pool of coordinated servers).
> 
> Seems most sensible to remove or comment out the GnuTLSCache and
> GnuTLSCacheTimeout lines.

Ahh, cache and ticket is not mutually exclusive.

Then maybe a better default setup is to keep cache enabled
but change it to use shmcb as that is already used for 
GnuTLSOCSPStapling which is enabled by default.

So something like this:

  GnuTLSCache shmcb:cache/gnutls_cache(65536)

(or maybe a full path? What is the root of above relative path?)

Also, to ensure that shmcb module is loaded (was on my systems but not 
sure if that is always the case), add this as topmost line to 
debian/gnutls.load:

  # Depends: socache_shmcb


If there is reason to stay with current dbm by default,
I recommend to consider instead adding this to debian/gnutls.load:

  # Depends: socache_dbm


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#908216: btrfs blocked for more than 120 seconds

[Nicholas D Steeves]

Control: tags -1 -unreproducible

Hi Russell,

Thank you for providing more info.  Now I see where you're running
into known limitations with btrfs (all versions).  Reply follows inline.

BTW, you're not using SMR and/or USB disks, right?

On Mon, Feb 25, 2019 at 12:33:51PM -0600, Russell Mosemann wrote:
>Steps to reproduce
> 
>Simply copying a file into the file system can cause things to lock up. In
>this case, the files will usually be thin-provisioned qcow2 disks for kvm
>vm's. There is no detailed formula to force the lockup to occur, but it
>happens regularly, sometimes multiple times in one day.
>

Have you read https://wiki.debian.org/Btrfs ?  Specifically "COW on
COW: Don't do it!" ?  If you did read it, maybe the document needs to
be more firm about this...  eg: "take care to use raw images" should
be "under no circumstances use non-raw images".  P.S. Yes, I know that
page would benefit from a reorganisation...  Sorry about it's current
state.

>Files are often copied from a master by reference (cp --reflink), one per
>day to perform a daily backup for up to 45 days. Removing older files is a
>painfully slow process, even though there are only 45 files in the
>directory. Doing a scrub is almost a sure way to lock up the system,
>especially if a copy or delete operation is in progress. On two systems,
>crashes occur with 4.18 and 4.19 but not 4.17. On the other systems that
>crash, it does not seem to matter if it is 4.17, 4.18 or 4.19.
>

It might be that >4.17 fixed some corner-case corruption issue, for
example by adding an additional check during each step of a backref
walk, and that this makes the timeout more frequent and severe. eg:
4.17 works because it is less strict.

By the way, is it your VM host that locks up, or your VM guests?  Do[es]
they[it] recover if you leave it alone for many hours?  I didn't see
any oopses or panics in your kernel logs.

Reflinked file are like snapshots, any I/O on a file must walk every branch
of the backref tree that is relevant to a file.  For more info see:
  https://btrfs.wiki.kernel.org/index.php/Resolving_Extent_Backrefs

As the tree grows and becomes more complex, a COW fs will get slower.
You've hit the >120sec threshold, due to one or more of the issues
discussed in this email.  eg: a scrub, even during a file copy/delete
should never cause this timeout.  I haven't experienced one since
linux-4.4.x or 4.9.x...

To get a figure that will provide a sense of scale to how many
operations it takes to do anything other than reflink or snapshot you
can consult the output of:

  filefrag each_live_copy_vm_image

I expect the number of extends will exceed tens of thousands.  BTW,
you can use btrfsmaintenance to periodically defrag the source (and
only the source) images.  Note that this will break reflinks between
SOURCE and each of the 45 REFLINKED-COPIES, but not between
REFLINK-COPY1 and REFLINK-COPY2.  Defragging weekly strikes a nice
balance between lost space efficiency (due to fewer shared references
between today's backup and yesterday's) and avoiding the performance
issue you've encountered.  Mounting with autodefrag is the least space
efficient.  (P.S. Also, I don't trust autodefrag)

IIRC btrfs-debug-tree can accurately count references.

>Unless otherwise indicated
> 
>using qgroups:No
>

Whew, thank you for not! :-)  Qgroups make this kind of issue worse.

>using compression:Yes, compress-force=zstd
>

If userspace CPU usage is already high then compression may introduce
additional latency and contribute to the >120sec warning.

>number of snapshots:  Zero
>

But 45 reflinked copies per VM.

>number of subvolumes: top level subvolume only
>

I believe it was Chris Murphy who wrote (on linux-btrfs) about how
segmenting different functions/datasets into different
non-hierarchically structured (eg: flat layout) subvolumes reduces
lock contention during backref walks.  This is a performance tuning
tip that needs to be investigated and integrated into the wiki
article.  Eg:

   _id:5 top-level_   <-either unmounted, or   
  /| | |   \mounted somewhere like
 / | | |\   /.btrfs-admin, /.volume, etc.
/  | | | \
host_rootfs   VM0   VM1   VM2   data_shared_between_VMs

>raid profile: None
> 
>using bcache: No
>

Thanks.

>layered on md or lvm: No
>

But layered on hardware raid?

>vhost002
> 
># grep btrfs /etc/mtab
>/dev/sdc1 /usr/local/data/datastore2 btrfs
>rw,noatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0
> 

[1] Thank you for using noatime.  Please explain this configuration.
eg: does each VM have three virtual disks (containing btrfs volumes),
backed by qcow2 images, backed by a btrfs volume on the VM host?  I
thought you were using qcow2 images, but this looks like passthrough
of some kind.

If the 

Bug#923302: libapache2-mod-gnutls: GnuTLSCache=dbm fails later restart of apache2

[Jonas Smedegaard]

Package: libapache2-mod-gnutls
Version: 0.9.0-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I experienced on multiple hosts that upgrading to the new
libapache2-mod-gnutls went fine (I guess it simply reloaded apache2),
but that a later server restart would fail.

Running "a2enmod socache_dbm" made apache2 work again.

Debian-shipped config enables GnuTLSCache, using dbm.
Release 0.9.0 has GnuTLSSessionTickets enabled by default,
which seems to make GnuTLSCache unneeded for most common use cases
(exceptions being non-SNI needs and a pool of coordinated servers).

Seems most sensible to remove or comment out the GnuTLSCache and
GnuTLSCacheTimeout lines.



While at it, I suggest adding this, commented out,
for those prioritizing strong security over Wondows XP compatibility:

  GnuTLSPriorities PFS:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:%SERVER_PRECEDENCE

(possibly %SERVER_PRECEDENCE is implied by PFS)


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlx0uzYACgkQLHwxRsGg
ASEhyg/9E+VpnZlbVx/4oZ94n0l5QJa/5RhCmtO68wz0F0SMN5uqhosLwdDjn5DZ
18P09r2m8zH2ckKVTlv0iy1p4ukko0em/htGUxph+zEmQfFVai67qPyWmAXBMDsW
djgnvNeJ2Qtmn0uV0gESqzXxrBu4jr9Ojz3i2jEmg1B70z5IvvOzi7osZaOs7dgA
nsNiBHcIVnipurqEU9hSZCl9s+S6QiNEYLtDSg0tCMf0dwi4POVuwfAiaRK1Yoid
m/i0Igeh27NpwHKP6kVF2iiJxDimxUjOhx7WXUY4U4gddLtv1dA+1VLRJGrffDEp
P96fD4rnFzKMapEaA2tHdxaRWFmwLZ1HNXFcKIG3aZbQN+J7a4lYOwkE7HFCka7J
XYIdNfNhRSrbTg1RZtoo53QOsLxkE9iGItLIkb49hVPSzq1j/APSOQlcc7RcceXm
rvqoutlaatBZEQFcP5gTPqWKzZCDvmbqWS1qKqlLBk6owOa+m5445ZTj1KcBjply
RKGhyAsWapTulSrzC4ev2ToUl8Ye8m1j6QHjG08IxfrsitmerZ8j7L8Va+T3yNH3
/91f7PcsEdIswuvE20R42OFG/8rMfz2yTjc2LvuXwRC26uQk6lfrYeqK58swvjFk
TgPdaIWA1TT54L0HHtN53wwRlNfKsQyFivSlwTH08VKOrfZDtmY=
=pYFj
-END PGP SIGNATURE-

Bug#922952: ITP: simdjson -- Parsing gigabytes of JSON per second

[Mo Zhou]

Actually I think we can close the bug if this upstream problem is solved.
https://github.com/lemire/simdjson/issues/34

On Fri, Feb 22, 2019 at 08:43:15PM -0500, Sam Hartman wrote:
> I don't know about official policy, but I think you could make your bug
> not RC by detecting whether the current system can support the package
> in some reasonable wail and failing more gracefully than with SIGILL.
> 
> It's not a requirement that all packages work on all systems.
> Open-vm-tools doesn't do squat if you aren't running on top of vmware;
> pcscd is remarkably useless without a smartcard reader; etc.
> I think it ought to be fine to have a package that is only useful with
> some given hardware provided that  you're reasonable about detecting
> requirements, and that  you don't place stronger requirements than are
> actulaly needed by your package.
> 
> --Sam

Bug#923301: [firefox-esr] Screenshot function blocked by fingerpriting resist

[Synthea]

Package: firefox-esr
Version: 60.5.1esr-1~deb9u1
Severity: normal

How to reproduce:
- Set in about: config "privacy.resistFingerprinting;true" and
"extensions.screenshots.disabled;false"
- Try to capture a screenshot by pressing "take a screenshot" from the
three dots menu
- The canvas block will stop the capture and asks if you want to enable
canvas on this page
This seems related to 
https://bugzilla.mozilla.org/show_bug.cgi?id=1412418
https://github.com/mozilla-services/screenshots/issues/3691
https://github.com/uBlockOrigin/uBlock-issues/issues/32
Please bump the esr release to the next one (if there is) asap

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

Debian Release: 9.8
  500 stable-updates  deb.debian.org 
  500 stable  security.debian.org 
  500 stable  repo.skype.com 
  500 stable  dl.google.com 
  500 stable  deb.debian.org 
  500 newstable   deb.i2p2.de 
  100 stretch-backports deb.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
libasound2  (>= 1.0.16) | 
libatk1.0-0 (>= 1.12.4) | 
libc6 (>= 2.18) | 
libcairo-gobject2   (>= 1.10.0) | 
libcairo2   (>= 1.10.0) | 
libdbus-1-3 (>= 1.9.14) | 
libdbus-glib-1-2  (>= 0.78) | 
libffi6  (>= 3.0.4) | 
libfontconfig1(>= 2.11) | 
libfreetype6 (>= 2.2.1) | 
libgcc1  (>= 1:4.2) | 
libgdk-pixbuf2.0-0  (>= 2.22.0) | 
libglib2.0-0(>= 2.31.8) | 
libgtk-3-0   (>= 3.0.0) | 
libjsoncpp1  (>= 1.7.4) | 
libpango-1.0-0  (>= 1.14.0) | 
libstartup-notification0   (>= 0.8) | 
libstdc++6   (>= 6) | 
libvpx4  (>= 1.6.0) | 
libx11-6| 
libx11-xcb1 | 
libxcb-shm0 | 
libxcb1 | 
libxcomposite1 (>= 1:0.3-1) | 
libxdamage1  (>= 1:1.1) | 
libxext6| 
libxfixes3  | 
libxrender1 | 
libxt6  | 
zlib1g   (>= 1:1.2.3.4) | 
fontconfig  | 
procps  | 
debianutils   (>= 1.16) | 


Recommends  (Version) | Installed
=-+-===
libavcodec58  | 
 OR libavcodec-extra58| 
 OR libavcodec57  | 
 OR libavcodec-extra57| 7:3.2.12-1~deb9u1
 OR libavcodec56  | 
 OR libavcodec-extra56| 
 OR libavcodec55  | 
 OR libavcodec-extra55| 
 OR libavcodec54  | 
 OR libavcodec-extra54| 
 OR libavcodec53  | 
 OR libavcodec-extra53| 


Suggests  (Version) | Installed
===-+-===
fonts-stix  | 1.1.1-4
 OR otf-stix| 
fonts-lmodern   | 2.004.5-3
libgssapi-krb5-2| 
 OR libkrb53| 
libcanberra0| 
libgtk2.0-0 | 
pulseaudio  | 



--- Output from package bug script ---


-- Addons package information

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

Bug#922371: mirror listing update for ftp.tku.edu.tw

[Wisely]

Hi,

Thanks for your good suggestion.
I'll do the things right. ^^





TKU-OIS  Network Management Section  Chang, Wei-ting
Tel: (02)2621-5656 ext.2628  FAX: (02)2620-9893
E-Mail: wis...@mail.tku.edu.tw


-Original Message-
From: Peter Palfrader  
Sent: Monday, February 25, 2019 5:30 PM
To: wisely chang ; 922371-d...@bugs.debian.org
Subject: Re: Bug#922371: mirror listing update for ftp.tku.edu.tw

On Fri, 15 Feb 2019, wisely chang wrote:

> Package: mirrors
> Severity: minor
> User: mirr...@packages.debian.org
> Usertags: mirror-list
> 
> Submission-Type: update
> Site: ftp.tku.edu.tw
> Type: leaf
> Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 
> kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el 
> s390x
> Archive-http: /debian/
> Archive-rsync: debian/
> Maintainer: wisely chang 
> Country: TW Taiwan
> Comment: I lost the push rsync from upstream,but it's back.Please bring me
in again,thanks.


ftp.tw.debian.org is not a good *name* for your upstream.

We recommend mirrors do not use service aliases such as ftp..debian.org
(only http is guaranteed to be available at ftp..d.o sites).  Maybe
change your config to sync from the site currently backing the
ftp..debian.org service you sync from?
(opensource.nchc.org.tw)

Also, you might want to work on monitoring your mirror for being up-to-date.

Re-added your mirror, thanks for running the service.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#923221: ITP: libpam-fingerprint -- Pluggable Authentication Module for fingerprint authentication

[Paul Wise]

On Mon, Feb 25, 2019 at 7:14 PM Philipp Meisberger wrote:

> Poorly libpam-fprintd is not suitable as libfprint0 seems to support
> ZhianTec fingerprint sensors. libpam-fingerprint is especially for those
> sensors. I see it would be more precise to use "Pluggable Authentication
> Module for ZhianTec fingerprint sensors" as description and name the
> package "libpam-fingerprint-zfm".

Is it feasible to merge the two projects upstream? It seems like
having two different fingerprint sensor stacks and have the user
manually decide which one they want and then install it is a bit of a
suboptimal experience. It would be nicer if there were one stack that
supported all the fingerprint sensors available on the market.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#923300: ITP: golang-github-openshift-imagebuilder -- Builds Dockerfile using the Docker client

[Reinhard Tartler]

Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler 

* Package name: golang-github-openshift-imagebuilder
  Version : 1.0+git20190212.3682349-1
  Upstream Author : OpenShift
* URL : https://github.com/openshift/imagebuilder
* License : Apache-2.0
  Programming Lang: Go
  Description : Builds Dockerfile using the Docker client

 This library supports using the Dockerfile syntax to build OCI & Docker
 compatible images, without invoking a container build command such
 as buildah bud or docker build. It is intended to give clients more
 control over how they build container images, including: • Instead
 of building one layer per line, run all instructions in the same
 container• Set HostConfig settings like network and memory controls
 that are not available when running container builds• Mount external
 files into the build that are not persisted as part of the final image
 (i.e. "secrets")• If there are no RUN commands in the Dockerfile, the
 container is created and committed, but never started.  The final image
 should be 99.9% compatible with regular container builds, but bugs are
 always possible.


This is a build dependency of the buildah tool.

A particular challenge with this package is that it vendors in an old
version of the "docker" library. This has been reported by one of the
maintainers of the buildah project as 
https://github.com/openshift/imagebuilder/issues/116

Upstream doesn't appear to be willing to upgrade to a new version (quote from
the bug above "[...] I really don't want to [...]". Looking at how this package
is using the vendored library, it seems openshift/imagebuilder is using a
rather specific subset of the docker code, some of which possibly shouldn't
have been exposed in the first place. Therefore, I'm inclined to follow
upstream and vendor this library. My question here is what is the best way of
implementing this. I could update the Files-Excluded field in debian/copyright
to exclude all entries but openshift/imagebuilder, and use mk-origtargz to
strip the tarball. That would, however, lead to a *very* elaborate
Files-Excluded field. I wonder whether it wouldn't be actually be more
appropriate to create a tarbal with the vendored library and ship it in the
debian/ subdirectory. Has anyone else encountered this issue and/or could point
to other packages solving the same or a similar issue?

Cheers,
-rt

Bug#923299: /lib/systemd/system/tomcat9.service: tomcat9 fails to run; "Failed to set up mount namespacing" in system log

[Felicia]

Package: tomcat9
Version: 9.0.16-2
Severity: important
File: /lib/systemd/system/tomcat9.service

Dear Maintainer,

A fresh install of tomcat9 results in the daemon failing to run with a cryptic 
error in syslog:

   tomcat9.service: Failed to set up mount namespacing: No such file or 
directory

The problem is caused from this line in the tomcat9 systemd unit file 
/lib/systemd/system/tomcat9.service:
ReadWritePaths=/var/lib/solr/

Commenting out that line and doing:
   systemctl daemon-reload
   systemctl restart tomcat9.service

enables tomcat9 to run.

Perhaps tomcat9 is expecting the solr-tomcat package to be installed (which it 
is not on my system)?

This bug at systemd github is related:
Misleading error message when ReadWritePaths doesn't exist #10972
https://github.com/systemd/systemd/issues/10972




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

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

Versions of packages tomcat9 depends on:
ii  lsb-base10.2018112800
ii  systemd 241-1
ii  tomcat9-common  9.0.16-2
ii  ucf 3.0038+nmu1

Versions of packages tomcat9 recommends:
ii  libtcnative-1  1.2.21-1

Versions of packages tomcat9 suggests:
ii  tomcat9-admin 9.0.16-2
pn  tomcat9-docs  
ii  tomcat9-examples  9.0.16-2
pn  tomcat9-user  

-- Configuration Files:
/etc/tomcat9/policy.d/01system.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/01system.policy'
/etc/tomcat9/policy.d/02debian.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/02debian.policy'
/etc/tomcat9/policy.d/03catalina.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/03catalina.policy'
/etc/tomcat9/policy.d/04webapps.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/04webapps.policy'
/etc/tomcat9/policy.d/50local.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/50local.policy'

-- no debconf information

Bug#923204: [pkg-gnupg-maint] Bug#923204: Bug#923204: gpg-agent has a false dependency on libpam-systemd

[Daniel Kahn Gillmor]

On Mon 2019-02-25 13:33:57 +0100, Werner Koch wrote:
> On Sun, 24 Feb 2019 16:56, joshud...@gmail.com said:
>
>> gpg-agent --server or directly from .profile (ssh sessions) by
>> gpg-agent --daemon.
>
> FWIW, actually gpg-agent is started on-demand from all tools requiring
> it.  To explicitly start it "gpgconf --launch agent" can and should be
> used.

On systems where you actually care about all processes terminating when
you log out (which is most well-managed systems), you want something
that can automatically spawn and reap per-user daemons as they're needed
by the user.

Users of GNU/Linux systems with systemd as the process supervisor can
rely on libpam-systemd to manage user sessions successfully.  That way,
when you log out, your agent actually goes away, any secrets currently
unlocked are flushed, and your overall session (and all related
processes) terminates correctly.  This allows things like automated
unmounting of relevant filesystems, flushing of in-kernel keys, etc.

There are many other possible ways to manage per-user daemons on other
systems, but if you're already using systemd, it makes no sense to have
each daemon re-invent that wheel (and potentially fail to clean up at
the end of the session, as Werner's suggestion above does).  That's why
gpg-agent Suggests: libpam-systemd.

If you want to propose better integration with any system or session
managers that can be used in Debian (whether systemd or otherwise), i'm
all ears -- please submit those changes to the BTS as specific
improvements so that we can review them and make things better for users
of those systems.

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#923277: libaio1: failed to load wifi firmware after libaio1 update

[Guillem Jover]

Control: tag -1 moreinfo

Hi!

On Mon, 2019-02-25 at 20:21:01 +0100, definetti wrote:
> Package: libaio1
> Version: 0.3.111-1
> Severity: important

> after updating libaio1 to version 0.3.112-1 the system does not detect the
> wireless network card after reboot. Dmesg shows the following error:
> 
> failed to load ath10k/pre-cal-pci-:02:00.0.bin

I'm not even sure how that happens, as I see no package related to
wireless or network setup using libaio1 directly?

> reverting to 0.3.111-1 fixes the issue

Are you sure you didn't boot into a different kernel or similar?

Otherwise, do you have some local software that makes use of libaio1? Or
are you perhaps using dracut, lvm, multipath-tools, tgt? (I don't see
anything else boot related referencing libaio1.

Barring that, I don't know, as a wild guess, could you try upgrading
to 0.3.112-1, and manually moving /usr/lib/x86_64-linux-gnu/libaio.so.1*
into /lib/x86_64-linux-gnu/, and see whether that fixes your issue?

(I'm also assuming you do not have a split /usr w/o using an initramfs.)

Thanks,
Guillem

Bug#921959: openbsd-inetd: buffer overflow in tftpd caused by wrong path

[Bernhard Übelacker]

Control: reopen 921959
Control: reassign 921959 tftpd 0.17-22 


Hello Everyone,
I hope it is ok to reopen and reassign this report to package tftpd,
which I assume Alison Chaiken has installed, based on the addresses
in the supplied backtrace.

I assume this is the result of some implicit "Object Size Checking"
used by the compiler in "__strcpy_chk",
while in tftpd.c:624 is just a "strcpy" [1].

In the backtrace the parameter destlen has just a value of 0.
And [2] shows in that case we divert into the error path.

Unfortunately I cannot find the last amd64 build logs from the
developer information page, but the i386 log shows following
warning [3] since 0.17-22.
The log contains one more such warning.

So it looks like the compiler could not determine the available
memory in the pointer tp->th_msg.
This may be related to the -D_FORTIFY_SOURCE=2 that was not showing up
in the build log for 0.17-21.

Attached file contains some more details.

Kind regards,
Bernhard



[1]
(gdb) list tftpd.c:607,631
607 static void
608 nak(int error)
609 {
610 register struct tftphdr *tp;
611 int length;
612 register struct errmsg *pe;
613
614 tp = (struct tftphdr *)buf;
615 tp->th_opcode = htons((u_short)ERROR);
616 tp->th_code = htons((u_short)error);
617 for (pe = errmsgs; pe->e_code >= 0; pe++)
618 if (pe->e_code == error)
619 break;
620 if (pe->e_code < 0) {
621 pe->e_msg = strerror(error - 100);
622 tp->th_code = EUNDEF;   /* set 'undef' errorcode */
623 }
624 strcpy(tp->th_msg, pe->e_msg);  
  <
625 length = strlen(pe->e_msg);
626 tp->th_msg[length] = '\0';
627 length += 5;
628 if (sendto(peer, buf, length, 0, (struct sockaddr *), 
fromlen) != length)
629 syslog(LOG_ERR, "nak: %m\n");
630 }




[2]
(gdb) list strcpy_chk.c:30
25  char *
26  __strcpy_chk (char *dest, const char *src, size_t destlen)
27  {
28size_t len = strlen (src);
29if (len >= destlen)
30  __chk_fail ();  
31
32return memcpy (dest, src, len + 1);
33  }




[3]
https://buildd.debian.org/status/fetch.php?pkg=netkit-tftp=i386=0.17-22=1544734969=0

...
cd /<>/obj-i686-linux-gnu/tftp && /usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -o 
CMakeFiles/tftp.dir/tftpsubs.c.o   -c /<>/tftp/tftpsubs.c
...
In file included from /usr/include/string.h:494,
 from /<>/tftpd/tftpd.c:66:
In function 'strcpy',
inlined from 'nak' at /<>/tftpd/tftpd.c:624:2:
/usr/include/i386-linux-gnu/bits/string_fortified.h:90:10: warning: 
'__builtin___strcpy_chk' writing 1 or more bytes into a region of size 0 
overflows the destination [-Wstringop-overflow=]
   return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
  ^~
...


# Buster amd64 qemu VM 2019-02-25

apt update
apt dist-upgrade

apt install gdb 


#


apt install atftpd atftpd-dbgsym
gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'b main' -ex run -ex 
'disassemble main' --args /usr/sbin/in.tftpd
Reading symbols from /usr/sbin/in.tftpd...Reading symbols from 
/usr/lib/debug/.build-id/4a/f9379ec9fd666c9dd97dad57bf0c652b5664fe.debug...done.
...
Dump of assembler code for function main:
...
-> no line with offset 7a2
apt remove --purge atftpd atftpd-dbgsym


apt install tftp-hpa tftp-hpa-dbg
gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'b main' -ex run -ex 
'disassemble main' --args /usr/sbin/in.tftpd
Reading symbols from /usr/sbin/in.tftpd...Reading symbols from 
/usr/lib/debug/.build-id/d1/27b4ec61c7068d74fcc0a7c63d79180efc8416.debug...done.
...
Dump of assembler code for function main:
...
-> no line with offset 7a2
apt remove --purge tftp-hpa tftp-hpa-dbg


apt install tftpd tftpd-dbgsym
gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'b main' -ex run -ex 
'disassemble main' --args /usr/sbin/in.tftpd
Reading symbols from /usr/sbin/in.tftpd...Reading symbols from 
/usr/lib/debug/.build-id/71/ec94654597b3b11d2d01a17ce776065786a694.debug...done.
...
Dump of assembler code for function main:
...
   0x679d <+1149>:  callq  0x68d0 
   0x67a2 <+1154>:  mov$0x1,%edi
...
apt remove --purge tftpd tftpd-dbgsym


--> So assuming Alison Chaiken used package "tftpd" --> src:netkit-tftp


#


apt install dpkg-dev devscripts


mkdir /tmp/source/netkit-tftp/orig -p
cd/tmp/source/netkit-tftp/orig
apt source netkit-tftp
cd


mkdir /tmp/source/libc6/orig -p
cd/tmp/source/libc6/orig
apt source libc6
cd

Bug#922647: systemd --user no longer running

[Felipe Sateler]

On Mon, Feb 25, 2019 at 3:12 PM Eduard Bloch  wrote:

> Control: reassign -1 systemd
>
> Hallo,
> * Felipe Sateler [Thu, Feb 21 2019, 10:32:29AM]:
> >On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch <[1]e...@gmx.de> wrote:
> >  Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]: XIO:  fatal IO
> error
> >  11 (Resource temporarily unavailable) on X server ":0"
> >  Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]:   after 3713
> >  requests (3713 known processed) with 0 events remaining.
> >  Feb 08 20:38:51 zombie systemd[2391]: run-rpc_pipefs.mount:
> Succeeded.
> >  Feb 08 20:38:51 zombie systemd[1]: Stopping User Manager for UID
> 500...
> >
> >This is suspiciously close to the previous messages, which suggest the
> >ones left out are still relevant (ie, why did systemd decide to stop
> your
> >user manager).
>
> That were all recent log messages it did create in the last days before
> the problem has started. The system is rebooted regularly... so I guess
> there is a natural reason for stopping it?
>

Please post full logs. If you don't know what you are looking for, then
your editing might remove important information. Please do the following:
start from a fresh boot, wait until the user manager has exited, and then
get the full boot log with `sudo journalctl -b`, and attach that fully.



> Anyhow, in the meantime I made some more experiments, forcing "systemd
> --user" with XDG_RUNTIME_DIR set and observing what has happened or is
> happening.


This is strange. You don't have XDG_RUNTIME_DIR set automatically?



> Really weird things. I upgraded systemd to the latest sid
> version and it's still adding up. Immediately after login in lightdm, I
> can check the pstree and I see an active "systemd --user" process there and
> a few services started from there, like gpg agent but that's only about
> a half of what I would expect, especially "pulseaudio" is not started.
> When I run journalctl --unit user@500.service -b0 at that moment, it
> displays "No entries".
>
> When I check the same a couple of minutes later, the "systemd --user"
> process and the whole process subtree are gone. Vanished without any
> trace (when checking with journalctl --unit, as above) and still getting
> "no entries".
>
> Now I check the main log at the time where the weird process mass
> extinction happened, and see something like the following.
>
> Feb 25 18:48:06 zombie NetworkManager[958]:   [1551116886.6200]
> agent-manager: req[0x563871361240, :1.76/org.freedesktop.nm-applet/500]:
> agent registered
> Feb 25 18:48:15 zombie systemd[1]: NetworkManager-dispatcher.service:
> Succeeded.
> Feb 25 18:48:15 zombie systemd[1]: Stopping User Manager for UID 160...
>

This is not your uid, so this is not relevant to us.

>
> Anyhow, I have enough of this.
>

I get that you are frustrated, but please vent elsewhere. Reading this
doesn't precisely make me want to spend mi little debian time debugging
this issue.

-- 

Saludos,
Felipe Sateler

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

[Daniel Abrecht]

On 24/02/2019 20.27, Bill Allombert wrote:
>>  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.)
> 

There is no documentation explicitly mentioning TIOCL_SELMOUSEREPORT in
sel_mode for TIOCLINUX, subcode=2 (TIOCL_SETSEL), but console_codes(4)
describes how it works in section "Mouse tracking" to some extent:
> The mouse tracking facility is intended to return xterm(1)-compatible
> mouse status reports.  Because the console driver has no way to know
> the device or type of the mouse, these reports are returned in
> the console input stream only when the virtual terminal driver
> receives a mouse update ioctl.  These ioctls must be generated by a
> mouse-aware user-mode application such as the gpm(8) daemon.
> ...

I've looked at the kernel code, and this seams to be the only way the
mouse position can be reported by the kernel. Another thing not
mentioned by the docs is, that the kernel only reports the mouse
position if report_mouse was enabled.

console_codes(4) also describes the possible values of report_mouse:
> ESC [ ? 9 h
>   X10 Mouse Reporting (default off): Set reporting mode to 1 (or reset
>   to 0)—see below.
> ESC [ ? 1000 h
>   X11 Mouse Reporting (default off): Set reporting mode to 2 (or reset
>   to 0)—see below.

I guess in X10 compatibility mode, sending the mouse releases isn't
completely correct, but it shouldn't really matter, if any application
still uses that, it'll probably just ignore it. I could add a check for
it if you want.

The reason I have set BUTTON_RELEASED=0 in my current_button enum and
not to 3 is mainly just a habit, I like to be able to initialize things
with all 0 and have them in some sort of neutral or default state.



signature.asc
Description: OpenPGP digital signature

Bug#923298: chromium: file overlap with chromium-sandbox without Conficts and/or Replaces

[G. Branden Robinson]

Package: chromium
Version: 72.0.3626.96-1~deb9u1
Severity: grave
Justification: renders package unusable

I have been tracking testing for several months.

This looks to me like a missing or insufficiently versioned Replaces
declaration, but I did not dig deeply into this except to check the BTS
to see if it had bitten anyone else.  To my surprise, it looks like it
has not.

# apt install chromium-sandbox
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  chromium-sandbox
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 137 kB of archives.
After this operation, 851 kB of additional disk space will be used.
Get:1 http://ftp.au.debian.org/debian buster/main amd64 chromium-sandbox amd64 
72.0.3626.53-1 [137 kB]
Fetched 137 kB in 1s (179 kB/s)  
Selecting previously unselected package chromium-sandbox.
(Reading database ... 351969 files and directories currently installed.)
Preparing to unpack .../chromium-sandbox_72.0.3626.53-1_amd64.deb ...
Unpacking chromium-sandbox (72.0.3626.53-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/chromium-sandbox_72.0.3626.53-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/chromium/chrome-sandbox', which is also in 
package chromium 72.0.3626.96-1~deb9u1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/chromium-sandbox_72.0.3626.53-1_amd64.deb

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.8-1
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.2.0-21
ii  libatspi2.0-02.30.0-7
ii  libavcodec57 7:3.2.12-1~deb9u1
ii  libavformat577:3.2.12-1~deb9u1
ii  libavutil55  7:3.2.12-1~deb9u1
ii  libc62.28-7
ii  libcairo21.16.0-2
ii  libcups2 2.2.10-3
ii  libdbus-1-3  1.12.12-1
ii  libdrm2  2.4.97-1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.2.0-21
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.3-1
ii  libgtk2.0-0  2.24.32-3
ii  libicu57 57.1-6+deb9u2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1
ii  libopenjp2-7 2.3.0-1.1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpangoft2-1.0-01.42.4-6
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.36-5
ii  libpulse012.2-4
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.2.0-21
ii  libvpx4  1.6.1-3+deb9u1
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux2  0.5.2-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+4
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-9
ii  libgl1-mesa-dri   18.3.2-1

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#923297: src:netkit-ntalk: Build system transition, amend

[Christoph Biedl]

Package: src:netkit-ntalk
Version: 0.17-16
Severity: important

Dear Maintainer,

amendmend to #911154:

While fixing the remaining netkit-derived packages I developed a few
more tools to detect regressions introduced in the build system switch
to cmake, especially with regard to constants defined during build.

Upon re-checking my older submissions, I discovered some defects that
should see a fix. Please consider applying the patch below.

Regards,

Christoph

PS: There are three more packages with differences:
netkit-rsh
netkit-rwall
netkit-rwho
But at a first glance it seems no harm is done there.


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

Kernel: Linux 4.19.21 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect



signature.asc
Description: PGP signature

Bug#873520: lintian: Check for bad-distribution in debian/changelog too

[Chris Lamb]

tag 873520 - wontfix
thanks

Chris Lamb wrote:

> (Is there some way we can detect the cowbuilder use-case? I do not use
> that tool so don't know what the true situation is there.)

Ping on this?


Regards,

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

Bug#893244: Accepted jruby 9.1.17.0-1 (source) into unstable

[Andrej Shadura]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Feb 2019 21:38:40 +0100
Source: jruby
Binary: jruby
Architecture: source
Version: 9.1.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andrej Shadura 
Description:
 jruby  - 100% pure-Java implementation of Ruby
Changes:
 jruby (9.1.17.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Refresh patches.
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Move source package lintian overrides to debian/source.
   * Update Vcs-* to point to Salsa.
   * Use debhelper compat level 12.
   * Bump Standards-Version to 4.3.0.
   * Depend on libmodulator-java.
   * Use javax.annotation.processing.Generated from Java SE 9.
   * Disable a part of the SkinnyMethodAdapter test.
Checksums-Sha1:
 bf5484f6bb929fc2f1d8a0704256f7a4adb50936 2815 jruby_9.1.17.0-1.dsc
 3b1c96fa63efdd22070742d8a8e17a3afe3bd42a 8574514 jruby_9.1.17.0.orig.tar.gz
 db6e054eb07a24e3d0137b7a21295027fe97adf0 78396 jruby_9.1.17.0-1.debian.tar.xz
Checksums-Sha256:
 1552f4bd7585c6b7b6480b2cda2dd10ad4f7af0a52b57fb37309ad8eb6094556 2815 
jruby_9.1.17.0-1.dsc
 b66d7c14f85075afdabb5ebf5950804c5a5d5c1d05ab833f580f04ee709b5773 8574514 
jruby_9.1.17.0.orig.tar.gz
 845163de6803198e2d53caa61ff7baec73bc993706e449b6a32e6f6418ea56a4 78396 
jruby_9.1.17.0-1.debian.tar.xz
Files:
 148d4ffb85271810326b7e92c7931c00 2815 ruby optional jruby_9.1.17.0-1.dsc
 38fe13908af7fe67d32f0c62f4d42746 8574514 ruby optional 
jruby_9.1.17.0.orig.tar.gz
 eeebf31e4011b1f3b653a477cf294896 78396 ruby optional 
jruby_9.1.17.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlx0U2oACgkQXkCM2RzY
OdJqJAf/Wg20BYa4795WmV/hBjytWfby9sv5BA7EXNrXRANlcQHbcCy+wfk89/nw
S2qp2qrduCGbJZ3U46F5ax7S1QG8Rdg89f4BdTbgmVy5vzuJZidd83JfQbYSYP5g
2KTj0AfqlzTUN8Kd3OPPEHNgb9pvw/TG0FWux2dHqBUSRB8Rhdo4JOG/Esua4C6b
lMczq8ziQyyHr3XitNyspq53LxzStR2eazm3iBxz2uJx3F8swhHoMDfvJpyMNcp4
AhQqseuEO9wAklsHKHNQnqK3kCGg8Q78EaOUMtiyD+pWzzBxeAtPEmXgIIDAeqDF
jNXHqTefPVl+pi8a0GE0rVqVsILq5w==
=JikQ
-END PGP SIGNATURE-

Bug#923284: Seemingly miscompiles with jdk-11

[Emmanuel Bourg]

Thank you for the report Sjoerd. What error did you get when compiling
gradle with the rebuilt bsh?

Emmanuel Bourg

Bug#804552: Pandas documentation package is empty

[Rebecca N. Palmer]

The build log ( 
https://launchpadlibrarian.net/412630196/buildlog_ubuntu-disco-amd64.pandas_0.23.3-1fakesync1ubuntu3_BUILDING.txt.gz 
) suggests this is due to passing a PYTHONPATH to the just-built 
python-pandas, but not -lib or python3-, causing a failed import.


However, the obvious way to fix this does *not* stop -doc being 
near-empty, so it may not be the only problem.


--- pandas-0.23.3/debian/rules  2018-07-28 05:39:32.0 +0100
+++ pandas-0.23.3/debian/rules  2018-07-28 05:39:32.0 +0100
@@ -141,10 +141,7 @@
 ifneq (,$(findstring -a,$(DH_INTERNAL_OPTIONS)))
: # not building documentation in -a
 else
-   : # not building documentation ATM since requires ipython 0.11
-   export PYTHONPATH=`/bin/ls -d 
$$PWD/$(PACKAGE2_ROOT_DIR)/usr/lib/python$(PYVER)/*`; \

-   export MPLCONFIGDIR=$(CURDIR)/build HOME=$(CURDIR)/build; \
-cd doc; LC_ALL=C python make.py html
+   cd doc && 
PYTHONPATH=$(CURDIR)/$(PACKAGE3_ROOT_DIR)-lib/usr/lib/python3/dist-packages:$(CURDIR)/$(PACKAGE3_ROOT_DIR)/usr/lib/python3/dist-packages 
MPLCONFIGDIR=$(CURDIR)/build HOME=$(CURDIR)/build LC_ALL=C python3 
make.py html

 endif
 endif
: # Use jquery from Debian package, so prune shipped one

Bug#923295: src:jruby-joni: tests fail with invalid character property name

[Andrej Shadura]

Package: src:jruby-joni
Version: 2.1.25-1
Severity: normal
Tags: upstream ftbfs
Forwarded: https://github.com/jruby/joni/issues/40

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

As you already know, jruby-joni fails build-time tests in the current
unstable:

SEVERE ERROR: invalid character property name 

Pattern: [/\A\X\z/] Str: [" ??"] Encoding: [UTF-8] Option: [] Syntax: [TEST]
org.jcodings.exception.CharacterPropertyException: invalid character 
property name 
at 
org.jruby.jcodings/org.jcodings.unicode.UnicodeEncoding.propertyNameToCType(UnicodeEncoding.java:99)
at 
org.jruby.joni/org.joni.Parser$GraphemeNames.nameToCtype(Parser.java:954)
at 
org.jruby.joni/org.joni.Parser.parseExtendedGraphemeCluster(Parser.java:1082)
at org.jruby.joni/org.joni.Parser.parseExp(Parser.java:792)
at org.jruby.joni/org.joni.Parser.parseBranch(Parser.java:1529)
at org.jruby.joni/org.joni.Parser.parseSubExp(Parser.java:1546)
at org.jruby.joni/org.joni.Parser.parseRegexp(Parser.java:1579)
at org.jruby.joni/org.joni.Analyser.compile(Analyser.java:78)
at org.jruby.joni/org.joni.Regex.(Regex.java:155)
at org.jruby.joni/org.joni.Regex.(Regex.java:134)
at org.jruby.joni/org.joni.test.Test.xx(Test.java:113)
at org.jruby.joni/org.joni.test.Test.xx(Test.java:99)
at org.jruby.joni/org.joni.test.Test.x2(Test.java:185)
at org.jruby.joni/org.joni.test.TestU8.test(TestU8.java:139)
at org.jruby.joni/org.joni.test.Test.testRegexp(Test.java:256)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

This bug has already been reported upstream, but I though it would be
good to track it in Debian too.

- -- 
Cheers,
  Andrej

-BEGIN PGP SIGNATURE-

iQFIBAEBCAAyFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlx0buAUHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQXkCM2RzYOdKfRwf9Hvf7jFWyZ112COLnHuLjLoyQtHr2
b8+mcWLYGwzW09xIxQoIzbGIypNYfXpeaArhraN1FsJnAT4AEJ9Aq88Vz0URKFzV
Bd1rD5dGgtUMDAwIyk8cRPJk8PniQLuxK3XfGoyrpO/gTLRJ6J4qbIjDO3UEpcCM
hnPFBS3fT6T5zOTRS1eXhdfCQD37rSIM/YYk0y4FMA78BC1rau1ffkvsXhOJdJwZ
N4Y+lepNQxusE0QX1Uf+ucNNQzP3I9VCbA5FCWoauwQ6r25p4kxONP4Di/m+RWXV
LKn0h0sYyYigRdcqEW2QVoa510WLekCX3uEQUILiuqTvnpZWoNHJtdFOgA==
=/0PO
-END PGP SIGNATURE-

Bug#923296: linux-image-4.19.0-2-amd64: BTRFS transaction aborted during multiple parallel rm -rf

[Hazel Victoria Campbell]

Package: src:linux
Version: 4.19.16-1
Severity: normal

Dear Maintainer,

While removing a lot of files, (dirvish-cronjob -> dirvish-expire -> rm), BTRFS
bugs out. The relevant section of dmesg follows. The only taint is nvidia.

I don't think dirvish is relevant except that dirvish-expire runs rm on a lot
of hardlinked files. It looks like dirvish-expire calls multiple rm -rf jobs in
parallel, or at least there were multiple rm's left running after the bug. It's
possible due to ctrl-c interrupting dirvish-expire and then restarting it
multiple rm -rf were running *for the same files*. I smell a race condition.
CPU is i7-3770K so 8 processors.

The filesystem was left in a usable state, though read-only. btrfs-check
revealed:

Opening filesystem to check...
Checking filesystem on /dev/mapper/backups3
UUID: 2b571560-1b7c-42af-8dd8-c1bd33de3b76
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
unresolved ref dir 154198790 index 75995 namelen 84 name
api.launchpad.net,1.0,bugs,1201429-application,json,621249424e663ff813b146a2a20a1bC3
filetype 0 errors 3, no dir item, no dir index
unresolved ref dir 154198790 index 75995 namelen 84 name
api.launchpad.net,1.0,bugs,1201429-application,json,621249424e663ff813b146a2a20a1bc3
filetype 1 errors 4, no inode ref
ERROR: errors found in fs roots
found 1684332290048 bytes used, error(s) found
total csum bytes: 1602195336
total tree bytes: 43169284096
total fs tree bytes: 39250362368
total extent tree bytes: 1959067648
btree space waste bytes: 9671228983
file data blocks allocated: 1641163005952
 referenced 2764812832768



[ 1782.723094] BTRFS info (device dm-8): failed to delete reference to
api.launchpad.net,1.0,bugs,1201429-application,json,621249424e663ff813b146a2a20a1bc3,
inode 6868044 parent 154198790
[ 1782.723097] [ cut here ]
[ 1782.723098] BTRFS: Transaction aborted (error -2)
[ 1782.723143] WARNING: CPU: 7 PID: 13532 at fs/btrfs/inode.c:3976
__btrfs_unlink_inode.cold.87+0x57/0x146 [btrfs]
[ 1782.723144] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs
fuse tun snd_hrtimer nf_tables snd_seq nvidia_uvm(POE) nfnetlink snd_seq_device
binfmt_misc nls_ascii nls_cp437 vfat fat ext4 crc16 mbcache jbd2 fscrypto ecb
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp
snd_hda_codec_via snd_hda_codec_generic kvm_intel snd_hda_intel kvm irqbypass
snd_hda_codec intel_cstate intel_uncore snd_hda_core intel_rapl_perf efi_pstore
snd_hwdep snd_pcm snd_timer mei_me pcspkr iTCO_wdt serio_raw efivars sg
iTCO_vendor_support snd mei soundcore ie31200_edac evdev pcc_cpufreq
nvidia_drm(POE) drm_kms_helper drm nvidia_modeset(POE) nvidia(POE) ipmi_devintf
ipmi_msghandler msr it87 hwmon_vid coretemp loop parport_pc ppdev lp parport
efivarfs ip_tables x_tables autofs4 btrfs zstd_decompress
[ 1782.723177]  zstd_compress xxhash algif_skcipher af_alg ses enclosure
scsi_transport_sas dm_crypt dm_mod raid10 raid456 async_raid6_recov
async_memcpy async_pq async_xor async_tx xor uas usb_storage raid6_pq libcrc32c
crc32c_generic raid0 multipath linear hid_logitech_hidpp hid_logitech_dj
hid_generic usbhid hid raid1 md_mod sr_mod cdrom sd_mod crct10dif_pclmul
crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc xhci_pci mxm_wmi aesni_intel
ehci_pci xhci_hcd ahci libahci ehci_hcd aes_x86_64 crypto_simd libata cryptd
scsi_mod i2c_i801 glue_helper usbcore alx lpc_ich mdio usb_common fan thermal
video wmi button
[ 1782.723206] CPU: 7 PID: 13532 Comm: rm Tainted: P   OE
4.19.0-2-amd64 #1 Debian 4.19.16-1
[ 1782.723207] Hardware name: Gigabyte Technology Co., Ltd. To be filled by
O.E.M./Z77X-UD3H, BIOS F17 08/22/2012
[ 1782.723223] RIP: 0010:__btrfs_unlink_inode.cold.87+0x57/0x146 [btrfs]
[ 1782.723224] Code: ba a8 08 17 00 00 02 44 8b 5d 80 72 23 41 83 fb fb 0f 84
d1 00 00 00 44 89 de 48 c7 c7 98 55 53 c0 44 89 5d a4 e8 0f fc 55 e4 <0f> 0b 44
8b 5d a4 48 8b 7d a8 44 89 d9 ba 88 0f 00 00 44 89 5d a4
[ 1782.723226] RSP: 0018:ad4d0e9bfdb0 EFLAGS: 00010282
[ 1782.723228] RAX:  RBX: 920f9d4e7430 RCX:
0006
[ 1782.723229] RDX: 0007 RSI: 0096 RDI:
9212febd66a0
[ 1782.723230] RBP: ad4d0e9bfe30 R08: 0444 R09:
0007
[ 1782.723231] R10:  R11: 0001 R12:
920f807e35a0
[ 1782.723232] R13: 920f2cdbc850 R14: 9212f1321000 R15:
0930e306
[ 1782.723234] FS:  7f22df820540() GS:9212febc()
knlGS:
[ 1782.723235] CS:  0010 DS:  ES:  CR0: 80050033
[ 1782.723237] CR2: 55b57a8b49a8 CR3: 000317498002 CR4:
001606e0
[ 1782.723238] Call Trace:
[ 1782.723256]  btrfs_unlink_inode+0x17/0x50 [btrfs]
[ 1782.723270]  btrfs_unlink+0x8c/0xd0 [btrfs]
[ 1782.723275]  vfs_unlink+0x109/0x1a0
[ 1782.723277]  do_unlinkat+0x239/0x320
[ 1782.723280]  do_syscall_64+0x53/0x100
[ 1782.723283]  

Bug#910493: [Pkg-privacy-maintainers] Bug#910493: Bug#910493: Handle transition from MAT to MAT2

[Georg Faerber]

Hi all,

On 19-02-22 23:26:45, Jonas Meurer wrote:
> I skimmed through the patch and it looks good to me. I also did some
> rough testing and at least with my test files it worked as expected.
> 
> I merged jvoisin's changes into the d/0.7.0-2 branch.

Thanks a lot for your inputs, reviews and changes -- highly appreciated.

I've got some serious issues currently with my keyboard, which makes
working at my PC quite a pain, but I'll take care of the upload in time
to ensure -2 will migrate before the full freeze on March 12th.

My current plan looks like the following:

- Let -1 migrate to testing, which should happen on Thursday, February
  28th.

  This is to ensure a minimal diff between testing and unstable, in case
  the migration of -2 gets delayed for whatever reason, -2 won't
  therefore migrate before the full freeze, and we need to ask for an
  freeze exception. AFAIK, minimal diffs have a higher chance to be
  accepted than bigger ones.

- I'll upload -2 either tomorrow or the day after via the delayed queue,
  or on Thursday. In any case, -2 should migrate on March 10th, if all
  goes well. I'm on travel, so can't pinpoint a specific time now, but
  be assured that the upload is upcoming.

- I plan to pull in three upstream bug fixes as well, see [1], [2] and [3].

In case you have any objections, please shout.

Thanks again,
cheers,
Georg


[1] 
https://0xacab.org/jvoisin/mat2/commit/c757a9b7ef3122ea19105ca47a323e81469da594
[2] 
https://0xacab.org/jvoisin/mat2/commit/524bae597209d775828bd176f6c00dd243f47c75
[3] 
https://0xacab.org/jvoisin/mat2/commit/545dccc3527fcdf851b30b072ae6c7222b711777


signature.asc
Description: Digital signature

Bug#923294: RM: ejs.js -- ROM; duplication of node-ejs

[Xavier Guimard]

Package: ftp.debian.org
Severity: normal

Hi all,

1. ejs.js provides libjs-ejs (used by nobody) and node-ejs which is also
   provided by src:node-ejs
2. src:node-ejs is up-to-date while src:ejs.js isn't (old github repo)
3. the only reverse dependency of node-ejs is node-nodeunit which
   requires ≥2.5.2 while ejs.js provides version 1.0.0

So I think it's safe to remove src:ejs.js from both testing and
unstable.

Cheers,
Xavier

Bug#923292: kmail randomly crashes when closing windows

[Juha Jäykkä]

Package: kmail
Version: 4:18.08.3-1
Severity: normal

Dear Maintainer,

I do not like the "message preview pane", so I open each message in a separate 
window
to read them. Sometimes, and as far as I can tell, at random, kmail will crash 
with a
SIGSEGV when such message window OR compose message window is closed. It does 
not
matter what causes the window to close, even sending a message sometimes causes 
a
crash.

Cheers,
Juha

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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.3-4
ii  kdepim-runtime   4:18.08.3-1
ii  kio  5.54.1-1
ii  libc62.28-7
ii  libgcc1  1:8.2.0-21
ii  libgpgmepp6  1.12.0-6
ii  libkf5akonadiagentbase5  4:18.08.3-4
ii  libkf5akonadicontact54:18.08.3-1
ii  libkf5akonadicore5abi2   4:18.08.3-4
ii  libkf5akonadimime5   4:18.08.3-1
ii  libkf5akonadisearch-bin  4:18.08.3-1
ii  libkf5akonadisearch-plugins  4:18.08.3-1
ii  libkf5akonadisearchdebug54:18.08.3-1
ii  libkf5akonadisearchpim5  4:18.08.3-1
ii  libkf5akonadiwidgets5abi14:18.08.3-4
ii  libkf5bookmarks5 5.54.0-1
ii  libkf5calendarcore5abi2  4:18.08.3-1
ii  libkf5calendarutils5 4:18.08.3-2
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5contacts5  4:18.08.3-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5followupreminder5  4:18.08.3-2
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5gravatar5abi2  4:18.08.3-1
ii  libkf5guiaddons5 5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5identitymanagement518.08.3-2
ii  libkf5itemmodels55.54.0-1
ii  libkf5itemviews5 5.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiofilewidgets55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5ksieveui5  4:18.08.3-2
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5libkdepimakonadi5  4:18.08.3-2
ii  libkf5libkleo5   4:18.08.3-2
ii  libkf5mailcommon5abi24:18.08.3-2
ii  libkf5mailtransport5 18.08.3-2
ii  libkf5mailtransportakonadi5  18.08.3-2
ii  libkf5messagecomposer5abi1   4:18.08.3-1
ii  libkf5messagecore5abi1   4:18.08.3-1
ii  libkf5messagelist5abi1   4:18.08.3-1
ii  libkf5messageviewer5abi1 4:18.08.3-1
ii  libkf5mime5abi1  18.08.3-1
ii  libkf5mimetreeparser5abi14:18.08.3-1
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5sendlater5 4:18.08.3-2
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5sonnetui5  5.54.0-1
ii  libkf5templateparser54:18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5tnef5  4:18.08.3-1
ii  libkf5wallet-bin 5.54.0-1
ii  libkf5wallet55.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-1
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5windowsystem5  5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqgpgme7   1.12.0-6
ii  libqt5core5a 5.11.3+dfsg-5
ii  libqt5dbus5  5.11.3+dfsg-5
ii  libqt5gui5   5.11.3+dfsg-5
ii  libqt5network5   5.11.3+dfsg-5
ii  libqt5widgets5   5.11.3+dfsg-5
ii  libqt5xml5   5.11.3+dfsg-5
ii  libstdc++6   8.2.0-21

Versions of packages kmail recommends:
ii  accountwizard   4:18.08.3-1
ii  gnupg   2.2.12-1
ii  kdepim-addons   18.08.3-1
ii  kdepim-themeeditors 4:18.08.3-1
ii  mbox-importer   4:18.08.3-1
ii  pim-data-exporter   4:18.08.3-1
ii  pim-sieve-editor

Bug#923293: kmail: mailbox contents displayed wrong

[Juha Jäykkä]

Package: kmail
Version: 4:18.08.3-1
Severity: normal

Dear Maintainer,

kmail will often show mailbox contents wrong: it will show the correct number 
of unread
messages in the folders pane, but the actual messages displayed do not show all 
those
unread messages (presumably not all read messages are shown either but not 
sure).

Checking the akonadi status from akonadiconsole shows all the messages, 
including the ones
kmail does not show, so kmail somehow gets out of sync with akonadi.

This can be worked around by restarting kmail, but given the frequency that 
this happens,
several times a day, it makes kmail's usability quite abysmal.

Cheers,
Juha

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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.3-4
ii  kdepim-runtime   4:18.08.3-1
ii  kio  5.54.1-1
ii  libc62.28-7
ii  libgcc1  1:8.2.0-21
ii  libgpgmepp6  1.12.0-6
ii  libkf5akonadiagentbase5  4:18.08.3-4
ii  libkf5akonadicontact54:18.08.3-1
ii  libkf5akonadicore5abi2   4:18.08.3-4
ii  libkf5akonadimime5   4:18.08.3-1
ii  libkf5akonadisearch-bin  4:18.08.3-1
ii  libkf5akonadisearch-plugins  4:18.08.3-1
ii  libkf5akonadisearchdebug54:18.08.3-1
ii  libkf5akonadisearchpim5  4:18.08.3-1
ii  libkf5akonadiwidgets5abi14:18.08.3-4
ii  libkf5bookmarks5 5.54.0-1
ii  libkf5calendarcore5abi2  4:18.08.3-1
ii  libkf5calendarutils5 4:18.08.3-2
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5contacts5  4:18.08.3-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5followupreminder5  4:18.08.3-2
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5gravatar5abi2  4:18.08.3-1
ii  libkf5guiaddons5 5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5identitymanagement518.08.3-2
ii  libkf5itemmodels55.54.0-1
ii  libkf5itemviews5 5.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiofilewidgets55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5ksieveui5  4:18.08.3-2
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5libkdepimakonadi5  4:18.08.3-2
ii  libkf5libkleo5   4:18.08.3-2
ii  libkf5mailcommon5abi24:18.08.3-2
ii  libkf5mailtransport5 18.08.3-2
ii  libkf5mailtransportakonadi5  18.08.3-2
ii  libkf5messagecomposer5abi1   4:18.08.3-1
ii  libkf5messagecore5abi1   4:18.08.3-1
ii  libkf5messagelist5abi1   4:18.08.3-1
ii  libkf5messageviewer5abi1 4:18.08.3-1
ii  libkf5mime5abi1  18.08.3-1
ii  libkf5mimetreeparser5abi14:18.08.3-1
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5sendlater5 4:18.08.3-2
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5sonnetui5  5.54.0-1
ii  libkf5templateparser54:18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5tnef5  4:18.08.3-1
ii  libkf5wallet-bin 5.54.0-1
ii  libkf5wallet55.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-1
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5windowsystem5  5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqgpgme7   1.12.0-6
ii  libqt5core5a 5.11.3+dfsg-5
ii  libqt5dbus5  5.11.3+dfsg-5
ii  libqt5gui5   5.11.3+dfsg-5
ii  libqt5network5   5.11.3+dfsg-5
ii  libqt5widgets5   5.11.3+dfsg-5
ii  libqt5xml5   5.11.3+dfsg-5
ii  libstdc++6   8.2.0-21

Versions of packages kmail recommends:
ii  accountwizard   4:18.08.3-1
ii  gnupg   

Bug#923291: kmail: syncing inbox(es) never finishes

[Juha Jäykkä]

Package: kmail
Version: 4:18.08.3-1
Severity: normal

Dear Maintainer,

Very often, almost as often as not, syncing an imap inbox never finishes. It 
will 
get stuck at any progress level, from 0% to 100% (yes, it even gets stuck at
100%). This happens with at least google's imap servers as well as three 
different
dovecot servers.

Steps to reprocude: start kmail, let it run for a while, checking inboxes either
manually or letting the automatic interval check do it for you. In less than 15
minutes at least one of the inboxes gets stuck.

Sometimes normal operation can only be recovered by manually restarting the 
stuck
agent, but sometimes only restarting the whole akonadi sorts it out.

This makes kmail unusable for me due to the frequency of restarts: often I need 
to
restart aknoadi between each two emails I read. Assuming this is not 
widespread, 
because if this is, the bug should be RC.

Cheers,
Juha

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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.3-4
ii  kdepim-runtime   4:18.08.3-1
ii  kio  5.54.1-1
ii  libc62.28-7
ii  libgcc1  1:8.2.0-21
ii  libgpgmepp6  1.12.0-6
ii  libkf5akonadiagentbase5  4:18.08.3-4
ii  libkf5akonadicontact54:18.08.3-1
ii  libkf5akonadicore5abi2   4:18.08.3-4
ii  libkf5akonadimime5   4:18.08.3-1
ii  libkf5akonadisearch-bin  4:18.08.3-1
ii  libkf5akonadisearch-plugins  4:18.08.3-1
ii  libkf5akonadisearchdebug54:18.08.3-1
ii  libkf5akonadisearchpim5  4:18.08.3-1
ii  libkf5akonadiwidgets5abi14:18.08.3-4
ii  libkf5bookmarks5 5.54.0-1
ii  libkf5calendarcore5abi2  4:18.08.3-1
ii  libkf5calendarutils5 4:18.08.3-2
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5contacts5  4:18.08.3-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5followupreminder5  4:18.08.3-2
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5gravatar5abi2  4:18.08.3-1
ii  libkf5guiaddons5 5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5identitymanagement518.08.3-2
ii  libkf5itemmodels55.54.0-1
ii  libkf5itemviews5 5.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiofilewidgets55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5ksieveui5  4:18.08.3-2
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5libkdepimakonadi5  4:18.08.3-2
ii  libkf5libkleo5   4:18.08.3-2
ii  libkf5mailcommon5abi24:18.08.3-2
ii  libkf5mailtransport5 18.08.3-2
ii  libkf5mailtransportakonadi5  18.08.3-2
ii  libkf5messagecomposer5abi1   4:18.08.3-1
ii  libkf5messagecore5abi1   4:18.08.3-1
ii  libkf5messagelist5abi1   4:18.08.3-1
ii  libkf5messageviewer5abi1 4:18.08.3-1
ii  libkf5mime5abi1  18.08.3-1
ii  libkf5mimetreeparser5abi14:18.08.3-1
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5sendlater5 4:18.08.3-2
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5sonnetui5  5.54.0-1
ii  libkf5templateparser54:18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5tnef5  4:18.08.3-1
ii  libkf5wallet-bin 5.54.0-1
ii  libkf5wallet55.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-1
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5windowsystem5  5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqgpgme7   1.12.0-6
ii  libqt5core5a 5.11.3+dfsg-5
ii  libqt5dbus5  5.11.3+dfsg-5
ii  libqt5gui5   5.11.3+dfsg-5
ii  libqt5network5   5.11.3+dfsg-5
ii  

Bug#923287: firefox: Open with/Save as dialog slow to respond

[Alexandre Lymberopoulos]

Package: firefox
Version: 65.0.1-1
Severity: normal

Dear Maintainer,

Once Firefox opens the Save As or Open With window to take action on a
given file it hangs with almost all the window rendered (not the
buttons). After a few seconds the buttons are drawn but not
responsible.

A few more second and the we are able to download or open the file. It
happens on this computer (home) and also in my work.

I may provide any information upon your resquest.

Thanks in advance,
Alexandre

-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libasound21.1.8-1
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-7
ii  libcairo-gobject2 1.16.0-2
ii  libcairo2 1.16.0-2
ii  libdbus-1-3   1.12.12-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-20
ii  libgdk-pixbuf2.0-02.38.0+dfsg-7
ii  libglib2.0-0  2.58.3-1
ii  libgtk-3-03.24.5-1
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.42-1
ii  libpango-1.0-01.42.4-6
ii  libsqlite3-0  3.26.0+fossilbc891ac6b-2
ii  libstartup-notification0  0.12-6
ii  libstdc++68.2.0-20
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec58  7:4.1-1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-5
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.17-1
ii  libgtk2.0-02.24.32-3
ii  pulseaudio 12.2-3

-- no debconf information

Bug#923289: Cannot install libgdk-pixbuf2.0-0 inside an armhf chroot

[Christopher Obbard]

Package: libgdk-pixbuf2.0-0
Version: 2.38.0+dfsg-7


installing the package under an armhf chroot on amd64 results in the
following error, the package is not configured properly and leads to
icons missing from the desktop environment.


> Setting up libgdk-pixbuf2.0-0:armhf (2.38.0+dfsg-7) ...
>
> (process:21627): GLib-ERROR **: 20:50:46.361: getauxval () failed: No such 
> file or directory
> qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
> Trace/breakpoint trap

The fix was to run the following commands (not in chroot -- on the
real hardware):

$ apt-get --reinstall install libgdk-pixbuf2.0-0
$ update-mime-database /usr/share/mime

Note this previously worked about ~6 months ago.

Cheers!

Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl

[Emanuele Rocca]

On 25/02 03:29, Sandro Tosi wrote:
> Emanuele, pytest-localserver has been orphaned, so you can go ahead
> and upload it if you want

Done.

> (and i dont think it's appropriate anymore to use the DPMT git repo, i
> guess you can move it to the debian/ namespace)

Also done, thanks Sandro.

Bug#923290: ddpo: Please distinguish reproduible state between sid/testing

[Guillem Jover]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: ddpo
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi!

The reproducible build state is currently only provided for «testing»,
because «sid» contains additional checks that are deemed would annoy
maintainers.

I've been aware of this in the past, but was still caught off guard
when checking my DDPO page and seeing that inetutils was still marked
as non-reproducible, even though the tests for sid said it was. And
thought there was some stale data going on.


I think it would be ideal if the reproducible states was shown
explicitly for both testing and sid, even though for now the sid
column would just print a sigil for N/A data (‘-’? with an alt text
mentioning the suite), this would make the information immediately
obvious. Also I think that in the future the reproducible people
might want to expose the state for sid too, at which point the N/A
marker can just be switched to provide the actual state.

Thanks,
Guillem

Bug#923288: kmail does not exit

[Juha Jäykkä]

Package: kmail
Version: 4:18.08.3-1
Severity: normal

Dear Maintainer,

kmail randomly refuses to exit. Upon closing the window or choosing to quit 
from 
the menu, the window disappears, but the process lingers and will not exit until
given a TERM or KILL. Trying to start a new copy does nothing (presumably 
because
the old copy is still alive).

Cheers,
Juha

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

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

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


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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.3-4
ii  kdepim-runtime   4:18.08.3-1
ii  kio  5.54.1-1
ii  libc62.28-7
ii  libgcc1  1:8.2.0-21
ii  libgpgmepp6  1.12.0-6
ii  libkf5akonadiagentbase5  4:18.08.3-4
ii  libkf5akonadicontact54:18.08.3-1
ii  libkf5akonadicore5abi2   4:18.08.3-4
ii  libkf5akonadimime5   4:18.08.3-1
ii  libkf5akonadisearch-bin  4:18.08.3-1
ii  libkf5akonadisearch-plugins  4:18.08.3-1
ii  libkf5akonadisearchdebug54:18.08.3-1
ii  libkf5akonadisearchpim5  4:18.08.3-1
ii  libkf5akonadiwidgets5abi14:18.08.3-4
ii  libkf5bookmarks5 5.54.0-1
ii  libkf5calendarcore5abi2  4:18.08.3-1
ii  libkf5calendarutils5 4:18.08.3-2
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1
ii  libkf5configgui5 5.54.0-1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5contacts5  4:18.08.3-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5followupreminder5  4:18.08.3-2
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5gravatar5abi2  4:18.08.3-1
ii  libkf5guiaddons5 5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5identitymanagement518.08.3-2
ii  libkf5itemmodels55.54.0-1
ii  libkf5itemviews5 5.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiofilewidgets55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5ksieveui5  4:18.08.3-2
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5libkdepimakonadi5  4:18.08.3-2
ii  libkf5libkleo5   4:18.08.3-2
ii  libkf5mailcommon5abi24:18.08.3-2
ii  libkf5mailtransport5 18.08.3-2
ii  libkf5mailtransportakonadi5  18.08.3-2
ii  libkf5messagecomposer5abi1   4:18.08.3-1
ii  libkf5messagecore5abi1   4:18.08.3-1
ii  libkf5messagelist5abi1   4:18.08.3-1
ii  libkf5messageviewer5abi1 4:18.08.3-1
ii  libkf5mime5abi1  18.08.3-1
ii  libkf5mimetreeparser5abi14:18.08.3-1
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5sendlater5 4:18.08.3-2
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5sonnetui5  5.54.0-1
ii  libkf5templateparser54:18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5tnef5  4:18.08.3-1
ii  libkf5wallet-bin 5.54.0-1
ii  libkf5wallet55.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-1
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5windowsystem5  5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqgpgme7   1.12.0-6
ii  libqt5core5a 5.11.3+dfsg-5
ii  libqt5dbus5  5.11.3+dfsg-5
ii  libqt5gui5   5.11.3+dfsg-5
ii  libqt5network5   5.11.3+dfsg-5
ii  libqt5widgets5   5.11.3+dfsg-5
ii  libqt5xml5   5.11.3+dfsg-5
ii  libstdc++6   8.2.0-21

Versions of packages kmail recommends:
ii  accountwizard   4:18.08.3-1

Bug#923286: scp: 'protocol error: filename does not match request' even though it does match

[Ansgar Burchardt]

Package: openssh-client
Version: 1:7.9p1-6
Severity: normal

The file "This is a [file].txt" (w/o quotes) exists on `remote`.

The following does no longer work:

   $ scp remote:'./"This is a [file].txt"' blubb
   protocol error: filename does not match request

These however do still work:

   $ scp remote:'"This is a [file].txt"' blubb
   $ scp remote:'./This\ is\ a\ \[file\].txt' blubb
   $ scp remote:'This\ is\ a\ \[file\].txt' blubb

Extended globs (from zsh) now only work sometimes as well:

   $ scp daikoku:'./This\ is\ a\ \[file\].txt(.)' blubb
   protocol error: filename does not match request
   $ scp daikoku:'This\ is\ a\ \[file\].txt(.)' blubb

Ansgar

-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)

Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.19.2
ii  libc6 2.28-7
ii  libedit2  3.1-20181209-1
ii  libgssapi-krb5-2  1.17-1
ii  libselinux1   2.8-1+b1
ii  libssl1.1 1.1.1a-1
ii  passwd1:4.5-1.1
ii  zlib1g1:1.2.11.dfsg-1

Bug#922993: RFS: popout3d/1.5.0-1

[Bart Martens]

It's there now. With version 1.5.0. Shouldn't that be 1.5.0-1?
https://mentors.debian.net/package/popout3d

Bug#910035:

[Jeffrey Cliff]

I'd like to get my feet wet in maintaining a package, and this seems like
the perfect package to start with, since it's small & I've been using it
for years.  While I'm not really sure where to start I took a look at the
source code and it seemed to mostly make sense.  I made a patch that fixes
the outstanding bug using the contribution of the person who reported it.
I'm not a DD but I am interested in helping out here.
Jeff Cliff

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

[Francesco Poli]

On Mon, 25 Feb 2019 01:22:40 +0100 Vincent Blut wrote:

> 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?

Nothing is added to /var/log/messages when chrony fails to start.

> 
> >> 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. ;-)

Obviously!  ;-)

> >
> >  # 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.

  # ps ax | grep chrony
  15534 ?S  0:00 /usr/sbin/chronyd -F -1
  15535 ?S  0:00 /usr/sbin/chronyd -F -1
  15557 pts/1S+ 0:00 grep chrony
  # chronyc tracking
  Reference ID:  (.z.tld)
  Stratum : 4
  Ref time (UTC)  : Mon Feb 25 20:50:10 2019
  System time : 0.3 seconds slow of NTP time
  Last offset : +0.52817 seconds
  RMS offset  : 0.52817 seconds
  Frequency   : 62.991 ppm slow
  Residual freq   : +12.282 ppm
  Skew: 0.023 ppm
  Root delay  : 0.047111727 seconds
  Root dispersion : 0.002364162 seconds
  Update interval : 2.0 seconds
  Leap status : Normal

[...]
> >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)?

I think there's nothing really special in it.
I've attached it.


There's another important thing that I should mention.
Today I have upgraded chrony on another box and the system call filter
works fine there (with mailonchange disabled, but with log *enabled*).

So I tried to think about the differences between the box where it
fails, and the box where it works.

The first difference is the architecture:
 • the box where it fails is i386
 • the box where it works is amd64
However, I suspect that chrony level of abstraction is high enough to
make this difference immaterial... Or am I wrong?

The second difference is the init system and might be more relevant:
 • the box where it fails runs with sysvinit as PID 1
 • the box where it works runs with systemd as PID 1

I cannot think about other potentially relevant differences, but, of
course, feel free to ask, in case you have any idea...


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


chrony.conf.gz
Description: application/gzip


pgpVYLFirsBBY.pgp
Description: PGP signature

Bug#923285: libslang2: Consider moving library within /lib/*/ to /usr/lib/*/

[Boyuan Yang]

Package: libslang2
Severity: minor
X-Debbugs-CC: only...@debian.org

I'm wondering if we could move the default installation location of libslang2
from /lib/*/ to /usr/lib/*/. That seems to suit the target of usrmerge [1].

--
Regards,
Boyuan Yang

[1] https://wiki.debian.org/UsrMerge


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

Bug#888229: better formatted patch

[Jeffrey Cliff]

TIL about quilt headers.  Looks like this one matches all the other cows:
Description: add a fox 'cow'
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888229#5
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888229



--- /dev/null
+++ b/cows/fox.cow
@@ -0,0 +1,18 @@
+$the_cow = <
+  <.._=/  \\=_. >
+ {`\\()/`}`\\ 
+ {  }  \\
+ |{}\\   
+ \\ '--'   .- \\  
+ |-  /\\ 
+ | | | | | ;
+ | | |.;.,..__ |
+   .-"";` `|
+  /|   /
+  `-../,..---'`
+EOC
--- a/debian/copyright
+++ b/debian/copyright
@@ -31,6 +31,10 @@
 Copyright: 1999 Geordan Rosario 
 License: COWSAY
 
+Files: cows/fox.cow
+Copyright: 2019 Hansen Wu 
+License: COWSAY
+
 Files: cows/gnu.cow cows/suse.cow
 Copyright: 2006 Gerfried Fuchs 
 License: WTFPL-2

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Hi,

>> It turns out that setting disable_ipv6=0 is not enough to regain working 
>> IPv6:
>> Now the RAs from the router arrive at the client, but when the client sends a
>> neighbor discovery, it never makes its way to the router, so the client 
>> cannot
>> actually communicate via IPv6. I can see the ND packages on vnet2 on the 
>> host,
>> but not on virbr1 (which vnet2 is attached to). Again this is something that
>> worked just fine before the update.
>>
>> I have no idea what is preventing the ND packages to be forwarded by the 
>> bridge.
>> I always thought bridges are just switches operating on layer 2, but it seems
>> that's as from the truth...
> 
> Can you check if downgrading the kernel helps?

I downgraded back to 4.18, which definitely used to work. No change in behavior.
Seems like it was a libvirt/firewalld upgrade that broke it.

; Ralf

Bug#888229: patch for above 'cow'

[Jeffrey Cliff]

made a patch that appears to implement the above 'cow'
hopefully this helps
Jeff Cliff
--- /dev/null
+++ b/cows/fox.cow
@@ -0,0 +1,18 @@
+$the_cow = <
+  <.._=/  \\=_. >
+ {`\\()/`}`\\ 
+ {  }  \\
+ |{}\\   
+ \\ '--'   .- \\  
+ |-  /\\ 
+ | | | | | ;
+ | | |.;.,..__ |
+   .-"";` `|
+  /|   /
+  `-../,..---'`
+EOC
--- a/debian/copyright
+++ b/debian/copyright
@@ -31,6 +31,10 @@
 Copyright: 1999 Geordan Rosario 
 License: COWSAY
 
+Files: cows/fox.cow
+Copyright: 2019 Hansen Wu 
+License: COWSAY
+
 Files: cows/gnu.cow cows/suse.cow
 Copyright: 2006 Gerfried Fuchs 
 License: WTFPL-2

Bug#923284: Seemingly miscompiles with jdk-11

[Sjoerd Simons]

Source: bsh
Version: 2.0b4-19
Severity: serious

When building bsh with openjdk-11 it seems that afterwards building packages
using it fails e.g. after rebuilding bsh gradle fails to build.

Attached is a dockerfile which nicely shows the issue

-- 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
FROM debian:buster

RUN apt-get update && \
apt-get install -y --no-install-recommends vim-tiny

RUN cat /etc/apt/sources.list | sed 's,^deb,deb-src,g' > 
/etc/apt/sources.list.d/s.list

RUN apt-get update && \
apt-get install -y build-essential devscripts

RUN apt-get update && \
apt-get build-dep -y bsh gradle

# builds fine
RUN apt-get source gradle  && \
cd gradle* && \
debuild -uc -us

# Rebuild bsh
RUN apt-get source bsh  && \
cd bsh* && \
debuild -uc -us && \
cd .. && \
dpkg -i libbsh-java*.deb

# fail :/
RUN apt-get source gradle  && \
cd gradle* && \
debuild -uc -us

Bug#912832: thunderbird: debian/rules relies on dpkg-parsechangelog

[Carsten Schoenert]

Hello intrigeri,

On Sun, Nov 04, 2018 at 09:02:13AM +0100, intrig...@debian.org wrote:
> Issue initially spotted by debian-rules-parses-dpkg-parsechangelog.
> We're not exactly parsing the output of dpkg-parsechangelog here but
> still, we can drop the duplicate BUILD_DATE variable: this avoids
> doing duplicate work and more importantly, as the Lintian
> documentation explains, using $SOURCE_DATE_EPOCH has a number of other
> advantages over using dpkg-parsechangelog.
> 
> I've built the package with the attached (git format-)patch applied
> and verified that it works as intended, i.e. the maximum mtime of
> files in /usr/share/xul-ext/calendar-google-provider and
> /usr/share/lightning equals $SOURCE_DATE_EPOCH.

mhh, somehow I must have overseen this report in the passt weeks ...

I just applied your patch, will get included within the next ESR round.

Regards
Carsten

Bug#910462: inspircd: New upstream release 2.0.26

[Christoph Biedl]

Christoph Biedl wrote...

> time has passed, and unfortunately it's too late now to salvage
> inspircd in time to bring it into buster. So I'd like to to a regular
> upload, adding myself as an uploader.
> 
> I'd highly appreciate your short ACK on this. debdiff on debian/
> attached.

Given the small time frame left, I've prepared an upload, will be sent
to DELAYED/3 in a few moments.

Full list of changes:

* new upstream version
* addd myself to uploaders
* fixed debian/watch so release candidates are ignored
* changed /var/run to /run in inspircd.tmpfile
* added SuccessExitStatus= to inspircd.service so "stop" does not
  end in a "failed" unit status

Updated debdiff attached.

Cheers,

Christoph
diff -Nru inspircd-2.0.24/debian/changelog inspircd-2.0.27/debian/changelog
--- inspircd-2.0.24/debian/changelog2018-06-17 21:06:10.0 +0200
+++ inspircd-2.0.27/debian/changelog2019-02-25 21:28:51.0 +0100
@@ -1,3 +1,10 @@
+inspircd (2.0.27-1) unstable; urgency=medium
+
+  * New upstream version 2.0.27 (Closes: #910462)
+  * Add myself to uploaders
+
+ -- Christoph Biedl   Mon, 25 Feb 2019 
21:28:51 +0100
+
 inspircd (2.0.24-1.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru inspircd-2.0.24/debian/control inspircd-2.0.27/debian/control
--- inspircd-2.0.24/debian/control  2018-06-17 21:06:10.0 +0200
+++ inspircd-2.0.27/debian/control  2019-02-25 21:28:43.0 +0100
@@ -2,7 +2,9 @@
 Section: net
 Priority: optional
 Maintainer: inspircd packagers 
-Uploaders: Guillaume Delacour 
+Uploaders:
+ Guillaume Delacour ,
+ Christoph Biedl ,
 Build-Depends: debhelper (>= 9.0.0), perl, libgnutls28-dev, pkg-config,
libldap2-dev, libpcre3-dev, default-libmysqlclient-dev, 
libpq-dev,
libsqlite3-dev, zlib1g-dev, libgeoip-dev,
diff -Nru inspircd-2.0.24/debian/inspircd.service 
inspircd-2.0.27/debian/inspircd.service
--- inspircd-2.0.24/debian/inspircd.service 2018-04-07 10:00:42.0 
+0200
+++ inspircd-2.0.27/debian/inspircd.service 2019-02-25 21:28:44.0 
+0100
@@ -5,6 +5,7 @@
 [Service]
 User=irc
 ExecStart=/usr/sbin/inspircd --logfile /var/log/inspircd.log --config 
/etc/inspircd/inspircd.conf --nofork
+SuccessExitStatus=15
 
 [Install]
 WantedBy=multi-user.target
diff -Nru inspircd-2.0.24/debian/inspircd.tmpfile 
inspircd-2.0.27/debian/inspircd.tmpfile
--- inspircd-2.0.24/debian/inspircd.tmpfile 2018-04-07 10:00:42.0 
+0200
+++ inspircd-2.0.27/debian/inspircd.tmpfile 2019-02-25 21:28:44.0 
+0100
@@ -1,2 +1,2 @@
-f /var/run/inspircd.pid 0644 irc irc
+f /run/inspircd.pid 0644 irc irc
 f /var/log/inspircd.log 0640 irc adm
diff -Nru inspircd-2.0.24/debian/patches/01_dpkg-buildflags_support.diff 
inspircd-2.0.27/debian/patches/01_dpkg-buildflags_support.diff
--- inspircd-2.0.24/debian/patches/01_dpkg-buildflags_support.diff  
2018-04-07 10:00:42.0 +0200
+++ inspircd-2.0.27/debian/patches/01_dpkg-buildflags_support.diff  
2019-02-23 13:22:28.0 +0100
@@ -19,7 +19,7 @@
  CORELDFLAGS = -rdynamic -L. $(LDFLAGS)
  PICLDFLAGS = -fPIC -shared -rdynamic $(LDFLAGS)
  BASE = "$(DESTDIR)@BASE_DIR@"
-@@ -132,7 +133,7 @@ CXXFLAGS += -Iinclude
+@@ -139,7 +140,7 @@ CXXFLAGS += -Iinclude
  @ENDIF
  
  @DO_EXPORT RUNCC RUNLD CXXFLAGS LDLIBS PICLDFLAGS VERBOSE SOCKETENGINE 
CORELDFLAGS
@@ -32,7 +32,7 @@
 ===
 --- inspircd-2.0.16.orig/make/unit-cc.pl
 +++ inspircd-2.0.16/make/unit-cc.pl
-@@ -79,6 +79,10 @@ sub do_static_link {
+@@ -95,6 +95,10 @@ sub do_static_link {
  }
  
  sub do_core_link {
@@ -43,7 +43,7 @@
my $execstr = "$ENV{RUNLD} -o $out $ENV{CORELDFLAGS} @_ $ENV{LDLIBS}";
print "$execstr\n" if $verbose;
exec $execstr;
-@@ -98,6 +102,7 @@ sub do_compile {
+@@ -114,6 +118,7 @@
my $binary = $ENV{RUNCC};
if ($do_compile) {
$flags = $ENV{CXXFLAGS};
diff -Nru inspircd-2.0.24/debian/patches/04_reproducible_builds.diff 
inspircd-2.0.27/debian/patches/04_reproducible_builds.diff
--- inspircd-2.0.24/debian/patches/04_reproducible_builds.diff  2018-04-07 
10:00:42.0 +0200
+++ inspircd-2.0.27/debian/patches/04_reproducible_builds.diff  2019-02-23 
13:22:28.0 +0100
@@ -10,7 +10,7 @@
 ===
 --- inspircd.orig/src/inspircd.cpp
 +++ inspircd/src/inspircd.cpp
-@@ -511,7 +511,7 @@ InspIRCd::InspIRCd(int argc, char** argv
+@@ -518,7 +518,7 @@ InspIRCd::InspIRCd(int argc, char** argv
}
}
  
@@ -23,7 +23,7 @@
 ===
 --- inspircd.orig/src/users.cpp
 +++ inspircd/src/users.cpp
-@@ -785,7 +785,8 @@ void LocalUser::FullConnect()
+@@ -786,7 +786,8 @@ void LocalUser::FullConnect()
this->WriteServ("NOTICE Auth :Welcome to 
\002%s\002!",ServerInstance->Config->Network.c_str());

Bug#923258: pbuilder-satisfydepends-apt: fails to consider libpam-systemd installed sometimes

[Mattia Rizzolo]

Control: reassign -1 apt 1.8.0~rc3

On Mon, Feb 25, 2019 at 04:14:03PM +0100, Thorsten Glaser wrote:
> Package: pbuilder
> Version: 0.230.1
> Severity: normal
> 
> This is a really weird bug.
> 
> I’m in a sid/amd64 chroot with sysvinit installed (basically, upgraded
> from, I think, a lenny/amd64 chroot to sid then kept updated all the
> time). There are no held packages inside the chroot, no APT pinning,
> etc. (I can tar it up, should that be needed.)

One reason I like the apt resolver is that any bug is not my bug!

We just pass all the job to apt, without even doing as much as parsing
the Build-Depends field :)

So, reassigning, let the deities help you!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#923283: dovecot-sieve: panic in i_stream_concat_close: assertion failed: (cstream->cur_input == cstream->input[cstream->cur_idx])

[Graham Cobb]

Package: dovecot-sieve
Version: 1:2.3.4.1-1
Severity: normal

When processing a particular type of notification email, I consistently get the
following sieve crash during execution of /usr/lib/dovecot/dovecot-lda.
(note, extracted from mail.log and reformatted a little for readability)

Feb 25 19:22:46 black dovecot: lda(cobb)<7721>: Panic: 
file istream-concat.c:
line 25 (i_stream_concat_close): assertion failed: (cstream->cur_input == 
cstream->input[cstream->cur_idx])
Feb 25 19:22:46 black dovecot: lda(cobb)<7721>: Error: 
Raw backtrace:
 /usr/lib/dovecot/libdovecot.so.0(+0xdad0b) [0x7faa1caead0b] ->
 /usr/lib/dovecot/libdovecot.so.0(+0xdad71) [0x7faa1caead71] ->
 /usr/lib/dovecot/libdovecot.so.0(+0x4a19f) [0x7faa1ca5a19f] ->
 /usr/lib/dovecot/libdovecot.so.0(+0x4c185) [0x7faa1ca5c185] ->
 /usr/lib/dovecot/libdovecot.so.0(io_stream_unref+0x27) [0x7faa1caf3a07] ->
 /usr/lib/dovecot/libdovecot.so.0(i_stream_unref+0x1d) [0x7faa1caf697d] ->
 /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_close+0x69) 
[0x7faa1cc76b79] ->
 /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x24) [0x7faa1cbf9ed4] 
->
 /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x13) [0x7faa1cbf9f43] ->
 /usr/lib/dovecot/dovecot-lda(main+0x756) [0x5626a8ac6dd6] ->
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7faa1c81c09b] ->
 /usr/lib/dovecot/dovecot-lda(_start+0x2a) [0x5626a8ac747a]

I can reproduce the crash consistently with a particular type of message being
delivered to a particular account with a fairly large set of sieve scripts.
I have managed to reduce the message to a small test message but I have not been
able to reproduce the crash with a significantly simpler script.

The actual line in the sieve script being executed at the time of the crash is 
the first line of
the following (the test would not be satisfied on this message):

  if body :raw :contains "://docs.google.com" {
addheader "X-GRC-SIEVE-Message" "Deleted by Google Docs low 
tolerance filter";
fileinto "${spam_medium}";
stop;
}

If I comment out that test, or even just remove the ":raw" clause, the script 
executes.
However a small script just containing that test does not crash.

I would rather not attach the full scripts to this report, but can provide them 
to the
maintainer if required.

The test message to reproduce the crash is:

>From ...@xxx.com  Thu Feb 21 23:33:46 2019
Delivered-To: x...@.uk.net
Return-Path: 
X-Original-To: xxwhois_grcxxx@localhost
Delivered-To: x...@.uk.net
To: xx...@.com
Subject: 
xxx
From: xx xx - xxx xxx 
Content-Type: text/plain; charset=utf-8
Message-Id: <20190221232525.e87682ed2...@xxx.com>
Date: Thu, 21 Feb 2019 23:25:25 + (GMT)

Test message



-- Package-specific info:

dovecot configuration
-
# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 ()
# OS: Linux 4.19.0-2-amd64 x86_64 Debian buster/sid 
# Hostname: black.home.cobb.me.uk
log_timestamp = "%Y-%m-%d %H:%M:%S "
login_trusted_networks = 192.168.0.0/16 127.0.0.1
mail_location = maildir:~/dovecot:INDEX=/var/indexes/%u
mail_max_userip_connections = 50
mail_privileged_group = mail
maildir_stat_dirs = yes
namespace {
  hidden = yes
  inbox = no
  list = children
  location = mbox:~/mail
  prefix = "#mbox/"
  separator = /
  type = private
}
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
  separator = /
}
passdb {
  driver = pam
}
passdb {
  args = scheme=SSHA512 username_format=%n /etc/dovecot/users
  driver = passwd-file
}
plugin {
  sieve = file:~/sieve;active=~/.dovecot.sieve
  sieve_extensions = +editheader +vnd.dovecot.debug
}
postmaster_address = postmas...@cobb.uk.net
protocols = " imap"
service imap {
  process_limit = 100
}
service pop3 {
  process_limit = 100
}
ssl_cert = 
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.3.4.1-1
pn  dovecot-ldap   
pn  dovecot-lmtpd  
pn  dovecot-managesieved   
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.3.4.1-1
pn  dovecot-sqlite 

-- no debconf information

Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl

[Sandro Tosi]

Emanuele, pytest-localserver has been orphaned, so you can go ahead
and upload it if you want (and i dont think it's appropriate anymore
to use the DPMT git repo, i guess you can move it to the debian/
namespace)

On Mon, Feb 25, 2019 at 3:21 PM Emanuele Rocca  wrote:
>
> tag 911836 patch
> tag 911836 pending
> thanks
>
> Fix pushed to salsa:
> https://salsa.debian.org/python-team/modules/pytest-localserver/merge_requests/1/diffs?commit_id=bad8a656ec5383c5b8a1d1e52f75e7afbe7c8c1b
>


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#923131:

[Michael Hudson-Doyle]

Do you have tzdata installed?

I'm not sure why you'd do this vs just taking the source from golang.org/dl
to be honest.

Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl

[Emanuele Rocca]

tag 911836 patch
tag 911836 pending
thanks

Fix pushed to salsa:
https://salsa.debian.org/python-team/modules/pytest-localserver/merge_requests/1/diffs?commit_id=bad8a656ec5383c5b8a1d1e52f75e7afbe7c8c1b

Bug#923281: batctl FTCBFS: fails cleaning due to wrong pkg-config

[Helmut Grohne]

Source: batctl
Version: 2019.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

batctl fails to cross build from source, because all make targets
require a working pkg-config, but only dh_auto_build substitutes ones.
Exporting a suitable PKG_CONFIG makes batctl cross buildable. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru batctl-2019.0/debian/changelog 
batctl-2019.0/debian/changelog
--- batctl-2019.0/debian/changelog  2019-02-01 22:32:44.0 +0100
+++ batctl-2019.0/debian/changelog  2019-02-25 20:54:09.0 +0100
@@ -1,3 +1,10 @@
+batctl (2019.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Provide a PKG_CONFIG for all make targets. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 25 Feb 2019 20:54:09 +0100
+
 batctl (2019.0-1) unstable; urgency=medium
 
   * New Upstream Version
diff --minimal -Nru batctl-2019.0/debian/rules batctl-2019.0/debian/rules
--- batctl-2019.0/debian/rules  2019-02-01 20:49:18.0 +0100
+++ batctl-2019.0/debian/rules  2019-02-25 20:54:08.0 +0100
@@ -1,8 +1,10 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+-include /usr/share/dpkg/buildtools.mk
 include /usr/share/dpkg/pkg-info.mk
 
+export PKG_CONFIG ?= pkg-config
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 export DEB_CFLAGS_MAINT_APPEND = -fdata-sections -ffunction-sections -flto
 export DEB_CPPFLAGS_MAINT_APPEND = -D_FILE_OFFSET_BITS=64

Bug#923282: freezegun breaks cached-property autopkgtest

[Paul Gevers]

Source: freezegun, cached-property
Control: found -1 freezegun/0.3.11-0.1
Control: found -1 cached-property/1.5.1-2
Severity: important
X-Debbugs-CC: debian...@lists.debian.org, naturesha...@debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers, Dominik,

With a recent upload of freezegun the autopkgtest of cached-property
fails in testing when that autopkgtest is run with the binary packages
of freezegun from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
freezegun  from testing0.3.11-0.1
cached-propertyfrom testing1.5.1-2
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 freezegun 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

[1] https://qa.debian.org/excuses.php?package=freezegun

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cached-property/2001918/log.gz

==
FAIL: test_threads_ttl_expiry
(tests.test_cached_property.TestCachedPropertyWithTTL)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.kwqe3o55/downtmp/autopkgtest_tmp/tests/test_cached_property.py",
line 207, in test_threads_ttl_expiry
self.assert_cached(check, 2 * num_threads)
  File
"/tmp/autopkgtest-lxc.kwqe3o55/downtmp/autopkgtest_tmp/tests/test_cached_property.py",
line 69, in assert_cached
self.assertEqual(check.add_cached, expected)
AssertionError: 6 != 10



signature.asc
Description: OpenPGP digital signature

Bug#920621: texlive-base: breaks build of forthcoming doxygen 1.8.15

[Hilmar Preuße]

severity 920621 serious
forwarded 920621 https://github.com/tabu-fixed/tabu/pull/14
forcemerge 920621 920459
stop

Am 27.01.2019 um 15:37 teilte Paolo Greppi mit:


I am preparing the next relase of doxygen (1.8.15).

Last week it built fine with texlive-base 2018.20181214-1.
I tried today with 2018.20190126-1 and it fails.

You can see the trace of the successful build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680
and of the failed build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/115667

I attach the files necessary to reproduce (I took the files in
doxygen/debian/build at the end of the failed build and blanked a few to reduce
the size of the attachment).


This one was missedd in the "big bug collection". Should be solved now.

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

Bug#923280: tstools FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: tstools
Version: 1.11-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

tstools fails to cross build from source, because it does not pass cross
tools to make. The easiest way of fixing that - using dh_auto_build -
makes tstools cross buildable. Please consider applying the attached
patch.

Helmut
diff -u tstools-1.11/debian/changelog tstools-1.11/debian/changelog
--- tstools-1.11/debian/changelog
+++ tstools-1.11/debian/changelog
@@ -1,3 +1,10 @@
+tstools (1.11-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 25 Feb 2019 20:47:41 +0100
+
 tstools (1.11-1) unstable; urgency=low
 
   * Initial release (Closes: #505304)
diff -u tstools-1.11/debian/rules tstools-1.11/debian/rules
--- tstools-1.11/debian/rules
+++ tstools-1.11/debian/rules
@@ -22,7 +22,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE)
+   dh_auto_build
#docbook-to-man debian/tstools.sgml > tstools.1
 
touch $@

Bug#923279: purity FTCBFS: upstream Makefile hard codes "cc"

[Helmut Grohne]

Source: purity
Version: 1-20
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

purity fails to cross build from source, because the upstream Makefile
hard codes plain "cc". After making it substitutable, purity cross
builds successfully. Please consider applying the attached patch.

Helmut
--- purity-1.orig/Makefile
+++ purity-1/Makefile
@@ -20,7 +20,7 @@
 LIBS =
 
 purity: pt.c pt.h
-	cc $(CFLAGS) -DLIBDIR=\"$(LIBDIR)\" -o purity pt.c $(LIBS)
+	$(CC) $(CFLAGS) -DLIBDIR=\"$(LIBDIR)\" -o purity pt.c $(LIBS)
 
 clean:
 	rm -f purity *.o

Bug#923278: open-infrastructure-compute-tools: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 
 
Package: open-infrastructure-compute-tools 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of open-
infrastructure-compute-tools debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing
list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert


nl.po.gz
Description: application/gzip

Bug#921757: delayed NMU, patch

[Hilko Bengen]

control: tag -1 pending

Dear maintainer,

I have been able to reproduce the issue described by Santiago Vila on a
machine provided by him. I have also been able to use that machine to
produce two patches (different from what I provided above) that fix the
issue.

I have just NMU'd os-autoinst/4.5.1527308405.8b586d5-4.1 to DELAYED/5;
please feel free to reschedule or cancel my upload as you see fit. The
patches based on the current state of the debian/sid branch of the git
repository at salsa.debian.org
(180b0e19dfed3d2c7352144674844fa67b33f9d9) are attached to this mail.

Cheers,
-Hilko
>From 2baa6f6ab0ef62ef9b9ff4214f5470b323e84c6d Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Mon, 25 Feb 2019 20:00:01 +0100
Subject: [PATCH 1/2] Add patch to avoid race condition in osutils::runcmd
 (Cloese: #921757)

---
 ...6-Eliminate-race-condition-in-runcmd.patch | 45 +++
 ...eck-module-files-that-start-with-a-d.patch | 28 
 debian/patches/series |  2 +
 3 files changed, 75 insertions(+)
 create mode 100644 debian/patches/0006-Eliminate-race-condition-in-runcmd.patch
 create mode 100644 debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch

diff --git a/debian/patches/0006-Eliminate-race-condition-in-runcmd.patch b/debian/patches/0006-Eliminate-race-condition-in-runcmd.patch
new file mode 100644
index ..c4d3e9bd
--- /dev/null
+++ b/debian/patches/0006-Eliminate-race-condition-in-runcmd.patch
@@ -0,0 +1,45 @@
+From: Hilko Bengen 
+Date: Mon, 25 Feb 2019 09:47:35 +0100
+Subject: Eliminate race condition in runcmd
+
+---
+ osutils.pm | 16 ++--
+ 1 file changed, 6 insertions(+), 10 deletions(-)
+
+diff --git a/osutils.pm b/osutils.pm
+index b06a042..05423c3 100644
+--- a/osutils.pm
 b/osutils.pm
+@@ -93,19 +93,10 @@ sub quote {
+ # Open a process to run external program and check its return status
+ sub runcmd {
+ diag "running " . join(' ', @_);
+-my ($pid, $status);
+-
+-local $SIG{CHLD} = sub {
+-local ($!, $?);
+-while ((my $child = waitpid(-1, WNOHANG)) > 0) {
+-diag "runcmd pid $pid returned $child";
+-$status = $?;
+-}
+-};
+ 
+ my ($wtr, $rdr, $err);
+ $err = gensym;
+-$pid = open3($wtr, $rdr, $err, @_);
++my $pid = open3($wtr, $rdr, $err, @_);
+ die "couldn't open: $!" unless defined $pid;
+ close($wtr) or die "couldn't close fh: $!";
+ 
+@@ -125,6 +116,11 @@ sub runcmd {
+ close($rdr) or die "couldn't close fh: $!";
+ close($err) or die "couldn't close fh: $!";
+ 
++my $status;
++waitpid $pid, 0;
++$status = $?;
++diag "runcmd pid $pid returned $status";
++
+ my $exit_code = $status >> 8;
+ die "runcmd failed with exit code $exit_code" unless ($exit_code == 0);
+ return $exit_code;
diff --git a/debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch b/debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
new file mode 100644
index ..3d90d791
--- /dev/null
+++ b/debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
@@ -0,0 +1,28 @@
+From: Hilko Bengen 
+Date: Mon, 25 Feb 2019 20:21:55 +0100
+Subject: Do not syntax-check module files that start with a dot (such as .pc)
+
+---
+ t/00-compile-check-all.t | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/t/00-compile-check-all.t b/t/00-compile-check-all.t
+index 41896f7..f344853 100755
+--- a/t/00-compile-check-all.t
 b/t/00-compile-check-all.t
+@@ -36,6 +36,7 @@ my $test = Test::Compile->new();
+ my @files = $test->all_pm_files(".");
+ 
+ for my $file (@files) {
++next if ($file =~ /^[.]/);
+ next if ($file =~ /main.pm/);
+ $file =~ s,^\./,,;
+ $test->ok($test->pm_file_compiles($file), "Compile test for $file");
+@@ -43,6 +44,7 @@ for my $file (@files) {
+ 
+ @files = ('isotovideo', $test->all_pl_files("."));
+ for my $file (@files) {
++next if ($file =~ /^[.]/);
+ $test->ok($test->pl_file_compiles($file), "Compile test for $file");
+ }
+ $test->done_testing();
diff --git a/debian/patches/series b/debian/patches/series
index 9d5b44ef..23094b11 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,5 @@
 0003-adjust-to-avoid-ocr-test-failure.patch
 0004-avoid-make-check-doc-failure.patch
 0005-set-perl-path.patch
+0006-Eliminate-race-condition-in-runcmd.patch
+0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
-- 
2.20.1

>From 29c142a3ef51b12a7cf846a159c8a1a1797bad09 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Mon, 25 Feb 2019 20:02:15 +0100
Subject: [PATCH 2/2] release

---
 debian/changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index a4357aad..c55467d0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+os-autoinst (4.5.1527308405.8b586d5-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Add 

Bug#831273: Updated package on Salsa

[Francois Marier]

The updated package I am working on is here:

  https://salsa.debian.org/debian/fwknop

Francois

-- 
https://fmarier.org/

Bug#908203: opam: Should not depend on aspcud any more

[Anil Madhavapeddy]

On Sun, 9 Sep 2018 10:44:14 +0200 Ralf Jung  wrote:
> Hi Mehdi,
> 
> > On 2018-09-07 12:42, Ralf Jung wrote:
> >> Package: opam
> >> Version: 2.0.0-2
> >> Severity: normal
> >>
> >> Dear Maintainer,
> >>
> >> Quoting from https://opam.ocaml.org/doc/2.0/External_solvers.html:
> >>
> >>> As of 2.0.0, opam comes with a CUDF solver built-in by default, so unless 
> >>> you
> >>> have specifically compiled without it, you shouldn't have to be worried 
> >>> about
> >>> installing an external solver.
> >>
> >> So, aspcud should at best be a recommendation, not a dependency.  Likely, 
> >> it
> >> should just be a suggestions; the internal solver is used by default even 
> >> when
> >> aspcud is installed.
> >>
> > 
> > If I am not mistaken, the built-in solver is not enabled in the Debian 
> > package
> > because we are missing ocaml-mccs to make it work. So, for now, the 
> > dependency
> > is still needed.
> 
> Oh... that's a bummer, because using the new built-in solver is one of the
> biggest reasons to update to opam 2 for me. :/  aspcud keeps computing really
> strange solutions in some cases I frequently run into.
> 

Dear Debian opam maintainers,

It's really great to see opam 2.0.3 in Debian testing now! I just wanted
to highlight the importance of using the builtin mccs solver in order
to get a working opam installation on Debian Buster however.

Right now, the opam repository seems to fail badly when using the
aspcud solver out of the box:

"""
$ docker run -it debian:testing
# apt update
# apt install -y opam
# opam init -ya
[WARNING] Running as root is not recommended
[NOTE] Will configure from built-in defaults.
Checking for available remotes: rsync and local, git, mercurial, darcs. Perfect!

<><> Fetching repository information ><><><><><><><><><><><><><><><><><><><><><>
[default] Initialised

User configuration:
  ~/.profile is already up-to-date.
[NOTE] Make sure that ~/.profile is well sourced in your ~/.bashrc.


<><> Creating initial switch (ocaml-system>=4.02.3) <><><><><><><><><><><><><><>
[ERROR] Solver failed: "/usr/bin/aspcud 
/tmp/opam-xxx-4710/solver-in-4710-548b09 
/tmp/opam-xxx-4710/solver-out-4710-8b8a2d

-count(removed),-sum(request,version-lag),-count(down),-sum(solution,version-lag),-count(changed)"
 exited with code 1 "ERROR:
grounder returned with non-zero exit status"
"""

I've CCed Louis Gesbert in case he can shed any light on how to
make aspcud work more reliably, but I strongly suspect that we've
been testing the builtin mccs for so long that it's become the only
solver in the opam 2.0.x branch capable of actually working with
the current opam-repository.

regards,
Anil

Bug#923277: libaio1: failed to load wifi firmware after libaio1 update

[definetti]

Package: libaio1
Version: 0.3.111-1
Severity: important

Dear Maintainer,

after updating libaio1 to version 0.3.112-1 the system does not detect the
wireless network card after reboot. Dmesg shows the following error:

failed to load ath10k/pre-cal-pci-:02:00.0.bin

reverting to 0.3.111-1 fixes the issue



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

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages libaio1 depends on:
ii  libc6  2.28-7

libaio1 recommends no packages.

libaio1 suggests no packages.

-- no debconf information

Bug#923276: RM: sysbench [armel armhf mips mips64el mipsel s390x alpha hppa hurd-i386 ia64 m68k powerpc sh4 sparc64 x32] -- ROM; Does not build on all architectures it has previously built

[James Clarke]

On Mon, Feb 25, 2019 at 07:31:39PM +0100, Andreas Tille wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Hi,
>
> please remove sysbench for the said architectures to enable its
> migration to testing.

Whilst cleaning up cruft is fine, that's not going to help you migrate
to testing when you Build-Depend on libck-dev and Depend on libck0, both
coming from src:ck which hasn't been in testing for 360 days; see
#906697.

James

Bug#922699: caja: Caja crash when copying paste

[Frédéric MASSOT]

Hi,

To complete the bug report, caja crashes only if the folder contains 
files, if the folder is empty caja does not crash.



Regards.
--
==
|  FRÉDÉRIC MASSOT   |
| http://www.juliana-multimedia.com  |
|   mailto:frede...@juliana-multimedia.com   |
| +33.(0)2.97.54.77.94  +33.(0)6.67.19.95.69 |
===Debian=GNU/Linux===

Bug#922993: RFS: popout3d

[Bart Martens]

It's not at mentors at this time. Can you upload it there?

Bug#923276: RM: sysbench [armel armhf mips mips64el mipsel s390x alpha hppa hurd-i386 ia64 m68k powerpc sh4 sparc64 x32] -- ROM; Does not build on all architectures it has previously built

[Andreas Tille]

Package: ftp.debian.org
Severity: normal

Hi,

please remove sysbench for the said architectures to enable its
migration to testing.

Thanks for your work as ftpmaster

 Andreas.

Bug#785480: working and updates need, please package or i can provide help

[PICCORO McKAY Lenz]

hi i already are working with rtpengine and i need debian up to date
with that, see in salsa that package are not updated, i point that:

since commit 
https://github.com/BelledonneCommunications/bcg729/commit/6e1214ca493267e238ffd3bc318e36b9bd293255#diff-b2094bc23bdb408eb801f23e2a635a1e
medistream plugin are integrated and not build as separate object. so
if you interes i provide this diff deb attached to help and build this
important piece for rtpengine

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
diff --git a/debian/changelog b/debian/changelog
index ffc4cda..d70e736 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,14 @@
 bcg729 (1.0.4-1) UNRELEASED; urgency=medium
 
   [ Felix Lechner ]
-  * Ship .la file for mediastreamer plugin
   * Use proper multiarch path in rules
   * Change transport in watch file to plain http for PET3
   * Pointed Vcs: fields in control to debian repo, not upstream
 
+  [ PICCORO Lenz McKAY ]
+  * added patch automake autoreconf to bypass missing files
+  * remove plugin due are not integrated since 1.0.4 release
+
   [ Victor Seva ]
   * update debian/watch
   * New upstream version 1.0.4
diff --git a/debian/control b/debian/control
index 018da40..84af243 100644
--- a/debian/control
+++ b/debian/control
@@ -66,30 +66,3 @@ Description: Debug symbols for the ITU G.729 compatible audio codec
  .
  This package contains the debugging symbols.
 
-Package: mediastreamer-plugin-g729
-Architecture: any
-Multi-Arch: same
-Pre-Depends:
- ${misc:Pre-Depends},
-Depends:
- ${misc:Depends},
- ${shlibs:Depends},
-Description: Mediastreamer plugin for G.729 compatible audio codec
- Mediastreamer plugin for Belledonne's open source implementation
- of the ITU G729 Annex A speech codec. Mediastreamer is Linphone's
- media processing engine.
-
-Package: mediastreamer-plugin-g729-dbg
-Architecture: any
-Multi-Arch: same
-Section: debug
-Priority: extra
-Depends:
- mediastreamer-plugin-g729 (= ${binary:Version}),
- ${misc:Depends},
-Description: Debug symbols for the G.729 mediastreamer plugin
- Mediastreamer plugin for Belledonne's open source implementation
- of the ITU G729 Annex A speech codec. Mediastreamer is Linphone's
- media processing engine.
- .
- This package contains the debugging symbols.
diff --git a/debian/mediastreamer-plugin-g729-dbg.lintian-overrides b/debian/mediastreamer-plugin-g729-dbg.lintian-overrides
deleted file mode 100644
index 34269c2..000
--- a/debian/mediastreamer-plugin-g729-dbg.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# High-level upstream changelog is kept in NEWS; debhelper skips empty ChangeLog
-mediastreamer-plugin-g729-dbg binary: no-upstream-changelog
diff --git a/debian/mediastreamer-plugin-g729.install b/debian/mediastreamer-plugin-g729.install
deleted file mode 100644
index c8cec70..000
--- a/debian/mediastreamer-plugin-g729.install
+++ /dev/null
@@ -1,2 +0,0 @@
-usr/lib/*/mediastreamer/plugins/*.la
-usr/lib/*/mediastreamer/plugins/*.so
diff --git a/debian/mediastreamer-plugin-g729.lintian-overrides b/debian/mediastreamer-plugin-g729.lintian-overrides
deleted file mode 100644
index 86cc8cb..000
--- a/debian/mediastreamer-plugin-g729.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# High-level upstream changelog is kept in NEWS; debhelper skips empty ChangeLog
-mediastreamer-plugin-g729 binary: no-upstream-changelog
diff --git a/debian/patches/series b/debian/patches/series
index ba1e99f..5fc8977 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 enable-subdir-objects.patch
 
+02-readme-reconf.patch
diff --git a/debian/rules b/debian/rules
index 8cfb28c..1992419 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,7 +2,7 @@
 # -*- makefile -*-
 
 # Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
+export DH_VERBOSE=1
 
 # Uncomment this to change the hardening options
 #export DEB_BUILD_MAINT_OPTIONS = hardening=+all
@@ -15,12 +15,11 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 		--buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-static --disable-tests
+	dh_auto_configure -- --enable-static --disable-tests --libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
 
 override_dh_auto_install:
 	dh_auto_install --destdir=debian/tmp
-	sed -i "/dependency_libs/ s/'.*'/''/" "$(CURDIR)"/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/mediastreamer/plugins/msbcg729.la
+	sed -i "/dependency_libs/ s/'.*'/''/" "$(CURDIR)"/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.la
 
 override_dh_strip:
 	dh_strip -plibbcg729-0 --dbg-package=libbcg729-0-dbg
-	dh_strip -pmediastreamer-plugin-g729 --dbg-package=mediastreamer-plugin-g729-dbg

Bug#921599: python-mysqldb: always connects to localhost ignoring host entry in option file

[Faustin Lammler]

Hi Peter,
could you have a look at
https://github.com/MariaDB/mariadb-connector-c/pull/101 and check if it
looks good to you (it seems to be pretty similar patch).

Faustin

Bug#923275: Thunderbird: OK button in edit contact dialogue does not work

[Carsten Schoenert]

Hi,

Am 25.02.19 um 19:28 schrieb Heinrich Schuchardt:
> When editing a contact clicking the 'OK' button of the 'New contact' 
> form has no effect. In earlier releases this led to storing the
> contact.>
> The same problem occurs when editing an existing contact.

I can't reproduce this here, not by editing a new contact nor by edit an
existing one. Any extensions running that can conflicting your desired
actions? Have you tried to work in save mode?

-- 
Regards
Carsten Schoenert

Bug#833706: this is not solved

[Alex Brett]

On Fri, 22 Feb 2019 07:36:37 +0100 spambox  wrote:
> i stumbled on the same bug in a PXE based installation on vmware
> 
> the console displays a segfault and "error 4 in libc-2.23.so"

>From your screenshot it looks like Ubuntu you are installing - we hit this 
>exact issue with Ubuntu 16.04 (Xenial), when using the original netboot image. 
>It seems there is some sort of conflict between that and the latest libc6-udeb 
>package the installer retrieves (from xenial-updates).

Using the latest netboot image from xenial-updates resolved things for us, so 
I'd suggest ensuring whatever you're using to boot the installer is up to date.

Alex

Bug#908216: btrfs blocked for more than 120 seconds

[Russell Mosemann]

Steps to reproduce

Simply copying a file into the file system can cause things to lock up. In this 
case, the files will usually be thin-provisioned qcow2 disks for kvm vm's. 
There is no detailed formula to force the lockup to occur, but it happens 
regularly, sometimes multiple times in one day.
 
Files are often copied from a master by reference (cp --reflink), one per day 
to perform a daily backup for up to 45 days. Removing older files is a 
painfully slow process, even though there are only 45 files in the directory. 
Doing a scrub is almost a sure way to lock up the system, especially if a copy 
or delete operation is in progress. On two systems, crashes occur with 4.18 and 
4.19 but not 4.17. On the other systems that crash, it does not seem to matter 
if it is 4.17, 4.18 or 4.19.
 
Unless otherwise indicated
using qgroups:No

using compression:Yes, compress-force=zstd
number of snapshots:  Zero
number of subvolumes: top level subvolume only
raid profile: None
using bcache: No
layered on md or lvm: No
 
 
vhost002
# grep btrfs /etc/mtab
/dev/sdc1 /usr/local/data/datastore2 btrfs 
rw,noatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0
 
# smartctl -l scterc /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.2-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
   Read: Disabled
  Write: Disabled

 
# btrfs dev stats /usr/local/data/datastore2
[/dev/sdc1].write_io_errs   0
[/dev/sdc1].read_io_errs0
[/dev/sdc1].flush_io_errs   0
[/dev/sdc1].corruption_errs 0
[/dev/sdc1].generation_errs 0

 
 
vhost003
# grep btrfs /etc/mtab
/dev/sdb4 /usr/local/data/datastore2 btrfs 
rw,relatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0

 
(RAID controller)
# smartctl -l scterc /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.17.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org


# btrfs dev stats /usr/local/data/datastore2
[/dev/sdb4].write_io_errs   0
[/dev/sdb4].read_io_errs0
[/dev/sdb4].flush_io_errs   0
[/dev/sdb4].corruption_errs 0
[/dev/sdb4].generation_errs 0

 
 
vhost004
# grep btrfs /etc/mtab
/dev/sdb4 /usr/local/data/datastore2 btrfs 
rw,relatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0

 
(RAID controller)
# smartctl -l scterc /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.17.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, [ www.smartmontools.org 
]( http://www.smartmontools.org )

 
# btrfs dev stats /usr/local/data/datastore2
[/dev/sdb4].write_io_errs   0
[/dev/sdb4].read_io_errs0
[/dev/sdb4].flush_io_errs   0
[/dev/sdb4].corruption_errs 0
[/dev/sdb4].generation_errs 0

 
 
vhost031
# grep btrfs /etc/mtab
/dev/sdc1 /usr/local/data/datastore2 btrfs 
rw,relatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0

 
# smartctl -l scterc /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.2-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
   Read: Disabled
  Write: Disabled

 
# btrfs dev stats /usr/local/data/datastore2
[/dev/sdc1].write_io_errs   0
[/dev/sdc1].read_io_errs0
[/dev/sdc1].flush_io_errs   0
[/dev/sdc1].corruption_errs 0
[/dev/sdc1].generation_errs 0

 
 
vhost032
# grep btrfs /etc/mtab
/dev/sdc1 /usr/local/data/datastore2 btrfs 
rw,relatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0

 
# smartctl -l scterc /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.2-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
   Read: Disabled
  Write: Disabled

 
# btrfs dev stats /usr/local/data/datastore2
[/dev/sdc1].write_io_errs   0
[/dev/sdc1].read_io_errs0
[/dev/sdc1].flush_io_errs   0
[/dev/sdc1].corruption_errs 0
[/dev/sdc1].generation_errs 0

 
 
vhost182
# grep btrfs /etc/mtab
/dev/sdc1 /usr/local/data/datastore2 btrfs 
rw,noatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0
 
# smartctl -l scterc /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.2-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
   Read: Disabled
  Write: Disabled
 
# btrfs dev stats /usr/local/data/datastore2
[/dev/sdc1].write_io_errs   0
[/dev/sdc1].read_io_errs0
[/dev/sdc1].flush_io_errs   0
[/dev/sdc1].corruption_errs 0
[/dev/sdc1].generation_errs 0

 
 
vhost241
# grep btrfs /etc/mtab
/dev/sdc1 /usr/local/data/datastore2 btrfs 
rw,relatime,compress-force=zstd,space_cache,subvolid=5,subvol=/ 0 0

 
# smartctl -l scterc /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.17.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, 

Bug#921599: python-mysqldb: always connects to localhost ignoring host entry in option file

[Peter Pentchev]

On Mon, Feb 25, 2019 at 01:27:58PM -0500, Faustin Lammler wrote:
> Hi Peter,
> could you have a look at
> https://github.com/MariaDB/mariadb-connector-c/pull/101 and check if it
> looks good to you (it seems to be pretty similar patch).

Hi,

Yes, I saw a reference to this pull request in the JIRA issue that you
linked to yesterday, but I couldn't look at it then. I took a look at
it now and it seems like it could do the trick.

Thanks for filing the issue and for following up, and keep up
the great work!

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#923179: systemd breaks python-dbusmock autopkgtest

[Paul Gevers]

Control: reassign -1 python-dbusmock 0.18.1-2
Control: fixed -1 0.18.2-1

Hi Martin,

On 24-02-2019 22:41, Martin Pitt wrote:
> Right, I already noticed that, fixed it upstream, and did a new release:

Oops, sorry. Normally I check this, but somehow I forgot to do so in
this case.

> So what's left to do is to re-run systemd 241's tests against the unstable
> version of python-dbusmock.

This will happen automatically once python-dbusmock migrates (in the
next britney run).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#893244: jruby FTBFS with openjdk-9

[Miguel Landaeta]

Hi Markus,

On Sun, Feb 24, 2019 at 08:39:48PM +0100, Markus Koschany wrote:
> 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.

I agree, jruby is a mess, mostly because of me since I didn't have
almost any time during this release cycle to work on it.

I think jruby should be dropped from buster and a new libspring-java
upload should be prepared shortly, to disable jruby support in it.

It's not realistic to think that a new upstream release for jruby can
be prepared in a week and that will work to be well supported during
the next stable release life cycle.

Cheers,
Miguel.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: PGP signature

Bug#923018: geeqie: Segfault on create new archive filters

[jEsuSdA 8)]

El 25/2/19 a las 19:13, Andreas Ronnquist escribió:

Thanks!

I might have found the cause - there's a check in the code for the word
"Filter", which I can see is "Filtro" in your Spanish version -
In my system (which I run in Swedish), the string is also "Filter"
just like in English, so I don't run into the problem.

Could you please try to run geeqie in English like so:

LC_ALL=C geeqie

and report back if you run into the problem or not.



That's it!

Running it in English does not crashes Geeqie.

;)

Thanks a lot, Andreas!!

Bug#923275: Thunderbird: OK button in edit contact dialogue does not work

[Heinrich Schuchardt]

Package: thunderbird
Version: 1:60.5.0-3
Severity: normal

When editing a contact clicking the 'OK' button of the 'New contact'
form has no
effect. In earlier releases this led to storing the contact.

The same problem occurs when editing an existing contact.

Best regards

Heinrich Schuchardt

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, armhf, 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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-6
ii  libcairo-gobject2 1.16.0-2
ii  libcairo2 1.16.0-2
ii  libdbus-1-3   1.12.12-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-20
ii  libgdk-pixbuf2.0-02.38.0+dfsg-7
ii  libglib2.0-0  2.58.3-1
ii  libgtk-3-03.24.5-1
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.7-0 1.7.0-2
ii  libicu63  63.1-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.42-1
ii  libpango-1.0-01.42.4-6
ii  libsqlite3-0  3.26.0+fossilbc891ac6b-2
ii  libstartup-notification0  0.12-6
ii  libstdc++68.2.0-20
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.2-1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-de-de [hunspell-dictionary] 20161207-7
ii  hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1
ii  hunspell-fr-classical [hunspell-dictionary]  1:6.3-2
ii  lightning1:60.5.0-3

Versions of packages thunderbird suggests:
ii  apparmor  2.13.2-7
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.17-1

-- no debconf information

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

[Felipe Sateler]

On Sun, Feb 24, 2019 at 9:54 PM Adam Borowski  wrote:

> 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).
>

Right, this should be at least on README.Debian.


>
> 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.
>

Ah, interesting idea. Could you come up with a patch for this? This would
have a nice benefit of shipping less conffiles.

I think this would be required to implement the logind alternative depends:
without systemd --user or autospawn, pa would not be started.

-- 

Saludos,
Felipe Sateler

Bug#923018: geeqie: Segfault on create new archive filters

[Andreas Ronnquist]

On Mon, 25 Feb 2019 18:35:57 +0100 "jEsuSdA 8)" 
wrote:
> El 23/2/19 a las 21:09, Andreas Ronnquist escribió:
> > 
> > That doesn't tell me much - please install debug symbols for geeqie
> > - see
> > 
> > https://wiki.debian.org/AutomaticDebugPackages
> > 
> > and add the testing-debug repo - after this install the
> > geeqie-dbgsym package and please do a backtrace in gdb (the command
> > bt full in gdb) after the segmentation fault.
> > 
> > thanks
> > /Andreas
> > gus...@debian.org
> > 
> 
> Hi again!
> 
> This is the output:
> 
> 
- 8< -

Thanks! 

I might have found the cause - there's a check in the code for the word
"Filter", which I can see is "Filtro" in your Spanish version -
In my system (which I run in Swedish), the string is also "Filter"
just like in English, so I don't run into the problem.

Could you please try to run geeqie in English like so:

LC_ALL=C geeqie

and report back if you run into the problem or not.

Regards
/Andreas
gus...@debian.org

Bug#922647: systemd --user no longer running

[Eduard Bloch]

Control: reassign -1 systemd

Hallo,
* Felipe Sateler [Thu, Feb 21 2019, 10:32:29AM]:
>On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch <[1]e...@gmx.de> wrote:
>  Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]: XIO:  fatal IO error
>  11 (Resource temporarily unavailable) on X server ":0"
>  Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]:       after 3713
>  requests (3713 known processed) with 0 events remaining.
>  Feb 08 20:38:51 zombie systemd[2391]: run-rpc_pipefs.mount: Succeeded.
>  Feb 08 20:38:51 zombie systemd[1]: Stopping User Manager for UID 500...
> 
>This is suspiciously close to the previous messages, which suggest the
>ones left out are still relevant (ie, why did systemd decide to stop your
>user manager).

That were all recent log messages it did create in the last days before
the problem has started. The system is rebooted regularly... so I guess
there is a natural reason for stopping it?

Anyhow, in the meantime I made some more experiments, forcing "systemd
--user" with XDG_RUNTIME_DIR set and observing what has happened or is
happening. Really weird things. I upgraded systemd to the latest sid
version and it's still adding up. Immediately after login in lightdm, I
can check the pstree and I see an active "systemd --user" process there and
a few services started from there, like gpg agent but that's only about
a half of what I would expect, especially "pulseaudio" is not started.
When I run journalctl --unit user@500.service -b0 at that moment, it
displays "No entries".

When I check the same a couple of minutes later, the "systemd --user"
process and the whole process subtree are gone. Vanished without any
trace (when checking with journalctl --unit, as above) and still getting
"no entries".

Now I check the main log at the time where the weird process mass
extinction happened, and see something like the following.

Feb 25 18:48:06 zombie NetworkManager[958]:   [1551116886.6200] 
agent-manager: req[0x563871361240, :1.76/org.freedesktop.nm-applet/500]: agent 
registered
Feb 25 18:48:15 zombie systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Feb 25 18:48:15 zombie systemd[1]: Stopping User Manager for UID 160...
Feb 25 18:48:15 zombie systemd[1567]: Stopping Virtual filesystem service...
Feb 25 18:48:15 zombie systemd[1567]: Stopped target Default.
Feb 25 18:48:15 zombie systemd[1567]: Stopping Accessibility services bus...
Feb 25 18:48:15 zombie systemd[1567]: Stopping D-Bus User Message Bus...
Feb 25 18:48:15 zombie systemd[1567]: gvfs-daemon.service: Main process exited, 
code=killed, status=15/TERM
Feb 25 18:48:15 zombie systemd[1567]: dbus.service: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Stopped D-Bus User Message Bus.
Feb 25 18:48:15 zombie systemd[1567]: at-spi-dbus-bus.service: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Stopped Accessibility services bus.
Feb 25 18:48:15 zombie systemd[1]: run-user-160-gvfs.mount: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: run-user-160-gvfs.mount: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: gvfs-daemon.service: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Stopped Virtual filesystem service.
Feb 25 18:48:15 zombie systemd[1567]: Stopped target Basic System.
Feb 25 18:48:15 zombie systemd[1567]: Stopped target Sockets.
Feb 25 18:48:15 zombie systemd[1567]: pulseaudio.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed Sound System.
Feb 25 18:48:15 zombie systemd[1567]: gpg-agent-ssh.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed GnuPG cryptographic agent 
(ssh-agent emulation).
Feb 25 18:48:15 zombie systemd[1567]: gpg-agent-browser.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed GnuPG cryptographic agent and 
passphrase cache (access for web browsers).
Feb 25 18:48:15 zombie systemd[1567]: gpg-agent.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed GnuPG cryptographic agent and 
passphrase cache.
Feb 25 18:48:15 zombie systemd[1567]: dirmngr.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed GnuPG network certificate 
management daemon.
Feb 25 18:48:15 zombie systemd[1567]: gpg-agent-extra.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed GnuPG cryptographic agent and 
passphrase cache (restricted).
Feb 25 18:48:15 zombie systemd[1567]: dbus.socket: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Closed D-Bus User Message Bus Socket.
Feb 25 18:48:15 zombie systemd[1567]: Stopped target Paths.
Feb 25 18:48:15 zombie systemd[1567]: Reached target Shutdown.
Feb 25 18:48:15 zombie systemd[1567]: systemd-exit.service: Succeeded.
Feb 25 18:48:15 zombie systemd[1567]: Started Exit the Session.
Feb 25 18:48:15 zombie systemd[1567]: Reached target Exit the Session.
Feb 25 18:48:15 zombie systemd[1567]: Stopped target Timers.
Feb 25 18:48:15 zombie systemd[1568]: pam_unix(systemd-user:session): session 
closed for user lightdm
Feb 25 18:48:15 zombie systemd[1]: user@160.service: Succeeded.

Bug#923274: bfm FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: bfm
Version: 0.6.4-6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

bfm fails to cross build from source. The upstream build system hard
codes the build architecture pkg-config. The debian packaging does not
pass cross tools to make. Using dh_auto_build fixes the latter. It also
uses the build architecture strip during make install, which breaks
generation of a -dbgsym package beyond breaking cross compilation. The
attached patch fixes all of that. Please consider applying it.

Helmut
diff --minimal -Nru bfm-0.6.4/debian/changelog bfm-0.6.4/debian/changelog
--- bfm-0.6.4/debian/changelog  2014-05-19 03:58:34.0 +0200
+++ bfm-0.6.4/debian/changelog  2019-02-25 19:02:26.0 +0100
@@ -1,3 +1,13 @@
+bfm (0.6.4-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes #-1)
++ cross.patch: Make pkg-config substitutable.
++ Let dh_auto_build pass cross tools to make.
++ Defer all stripping to dh_strip.
+
+ -- Helmut Grohne   Mon, 25 Feb 2019 19:02:26 +0100
+
 bfm (0.6.4-6) unstable; urgency=low
 
   * Switched the source format from 1.0 to 3.0 (quilt)
diff --minimal -Nru bfm-0.6.4/debian/patches/cross.patch 
bfm-0.6.4/debian/patches/cross.patch
--- bfm-0.6.4/debian/patches/cross.patch1970-01-01 01:00:00.0 
+0100
+++ bfm-0.6.4/debian/patches/cross.patch2019-02-25 19:01:21.0 
+0100
@@ -0,0 +1,14 @@
+--- bfm-0.6.4.orig/Makefile
 bfm-0.6.4/Makefile
+@@ -29,8 +29,9 @@
+ GTK_CFLAGS = $(shell gtk-config --cflags)
+ GTK_LIBS = -lX11 $(shell gtk-config --libs)
+ 
+-GTK2_CFLAGS = $(shell pkg-config gtk+-2.0 --cflags)
+-GTK2_LIBS = -lX11 $(shell pkg-config gtk+-2.0 --libs)
++PKG_CONFIG ?= pkg-config
++GTK2_CFLAGS = $(shell $(PKG_CONFIG) gtk+-2.0 --cflags)
++GTK2_LIBS = -lX11 $(shell $(PKG_CONFIG) gtk+-2.0 --libs)
+ 
+ LIBS += -lm
+ 
diff --minimal -Nru bfm-0.6.4/debian/patches/series 
bfm-0.6.4/debian/patches/series
--- bfm-0.6.4/debian/patches/series 2014-05-19 03:29:29.0 +0200
+++ bfm-0.6.4/debian/patches/series 2019-02-25 19:00:59.0 +0100
@@ -1 +1,2 @@
 quilt
+cross.patch
diff --minimal -Nru bfm-0.6.4/debian/rules bfm-0.6.4/debian/rules
--- bfm-0.6.4/debian/rules  2014-05-19 03:27:35.0 +0200
+++ bfm-0.6.4/debian/rules  2019-02-25 19:02:21.0 +0100
@@ -3,11 +3,6 @@
 # Uncomment this to turn on verbose mode. 
 #export DH_VERBOSE=1
 
-# These are used for cross-compiling and for saving the configure script
-# from having to guess our platform (since we know it already)
-DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-
 CFLAGS = -Wall -g
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -18,12 +13,6 @@
 ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
 CFLAGS += -g
 endif
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-INSTALL_PROGRAM += -s
-   STRIP_PROGRAM = strip
-else
-STRIP_PROGRAM = true
-endif
 
 
 configure: configure-stamp
@@ -36,8 +25,8 @@
 build-indep: build-stamp
 build-stamp:
dh_testdir
-   $(MAKE) PREFIX=/usr STRIP=$(STRIP_PROGRAM) bubblefishymon
-   $(MAKE) PREFIX=/usr STRIP=$(STRIP_PROGRAM) gkrellm
+   dh_auto_build -- PREFIX=/usr STRIP=true bubblefishymon
+   dh_auto_build -- PREFIX=/usr STRIP=true gkrellm
touch build-stamp
 
 clean:

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

[Sebastien CHAVAUX]

As said, I added Jelmer's work:



Format: 1.8
Date: Mon, 25 Feb 2019 18:30:35 +0100
Source: xsoldier
Binary: xsoldier
Architecture: source
Version: 1:1.8-6
Distribution: unstable
Urgency: medium
Maintainer: Sebastien CHAVAUX 
Changed-By: Sebastien CHAVAUX 
Description:
 xsoldier   - shoot 'em up game with the "not shooting" bonus
Closes: 738879
Changes:
 xsoldier (1:1.8-6) unstable; urgency=medium
 .
   [ Sebastien CHAVAUX ]
   * New maintainer. (Closes: #738879)
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.


cordially

Le 24/02/2019 à 23:44, Adam Borowski a écrit :

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!