Bug#934947: libgtk-3-0: Emoji chooser is not working

[Timur Irikovich Davletshin]

Package: libgtk-3-0
Version: 3.24.5-1
Severity: normal

Dear Maintainer,

1. Run Gedit
2. Right click in the text edit area
3. Choose "Insert Emoji"
4. Categories are inactive, search via name gives no results.

Regards,

Timur.



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

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

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme   3.30.1-1
ii  hicolor-icon-theme   0.17-2
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcolord2   1.4.3-4
ii  libcups2 2.2.10-6
ii  libepoxy01.5.3-0.1
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2
ii  libgtk-3-common  3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libjson-glib-1.0-0   1.4.4-2
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libpangocairo-1.0-0  1.42.4-7~deb10u1
ii  libpangoft2-1.0-01.42.4-7~deb10u1
ii  librest-0.7-00.8.1-1
ii  libsoup2.4-1 2.64.2-2
ii  libwayland-client0   1.16.0-1
ii  libwayland-cursor0   1.16.0-1
ii  libwayland-egl1  1.16.0-1
ii  libx11-6 2:1.6.7-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxinerama1 2:1.1.4-2
ii  libxkbcommon00.8.2-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  shared-mime-info 1.10-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.24.5-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.38.1-5
ii  librsvg2-common  2.44.10-2.1

Versions of packages libgtk-3-0 is related to:
pn  appmenu-gtk3-module   
pn  fcitx-frontend-gtk3   
pn  gcin-gtk3-immodule
pn  gtk-vector-screenshot 
pn  gtk3-engines-xfce 
pn  gtk3-im-libthai   
pn  hime-gtk3-immodule
pn  ibus-gtk3 
pn  imhangul-gtk3 
ii  libcanberra-gtk3-module   0.30-7
pn  libcaribou-gtk3-module
pn  libgtk3-nocsd0
pn  maliit-inputcontext-gtk3  
pn  packagekit-gtk3-module
pn  scim-gtk-immodule 
pn  topmenu-gtk3  
pn  uim-gtk3  
pn  uim-gtk3-immodule 

-- no debconf information

Bug#932461: compress not working with xarchiver

[Maxim Svobonas]

Package: pcmanfm
Version: 1.3.1-1
Followup-For: Bug #932461

Using LXQt here, but pcmanfm instead of pcmanfm-qt
I tried removing xarchiver and apt auto-installed ark for me.
Since then pcmanfm fails to compress silently.
Tried dpkg-reconfigure pcmanfm and even rebooted.
Is there any workaround without recompiling?

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

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

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

Versions of packages pcmanfm recommends:
ii  gnome-icon-theme  3.12.0-3
ii  gvfs-backends 1.38.1-5
ii  gvfs-fuse 1.38.1-5
ii  lxqt-policykit [polkit-1-auth-agent]  0.14.1-1
ii  oxygen-icon-theme 5:5.54.0-1

pcmanfm suggests no packages.

-- no debconf information

Bug#931444: ncdu: progress dialog: for dirs with many files, total items can almost overlap size

[Eugene V. Lyubimkin]

Control: forwarded -1 https://code.blicky.net/yorhel/ncdu/issues/135


Hello Paul,

Paul Wise kirjoitti 5.7.2019 klo 8.32:
> For directories that have many subdirectories and many files, in the
> ncdu progress dialog the total items count can encroach on and almost
> overlap the total size count:
> 
>Total items: 20161797size: 123.4 GiB
> 
> [...]

Thank you for the report, it's now forwarded upstream.


Regards,
-- 
Eugene V. Lyubimkin aka JackYF
C++ GNU/Linux userspace developer, Debian Developer

Bug#863293: Bug#863255: Please rename/provide libjs-jquery-atwho

[Ben Finney]

On 14-Aug-2019, Pirate Praveen wrote:

> Since there is no response for over 3 months for the merge request, I'm
> planning to do an NMU.

I'm confused; this bug report (bug#863255) is closed as resolved.

What would you propose in an NMU? Can you please open a new bug report
instead?

-- 
 \  “And if I laugh at any mortal thing, / 'Tis that I may not |
  `\   weep.” —“Lord” George Gordon Noel Byron, _Don Juan_ |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#863293: Bug#863255: Please rename/provide libjs-jquery-atwho

[Ben Finney]

On 16-Aug-2019, Ben Finney wrote:

> I am back involved in Debian packaging again. Can you instead make a
> merge request at the Salsa repository
> https://salsa.debian.org/debian/pkg-jquery-at.js/>
> and show me what you're planning?

Is the change you're asking for represented in this merge request
https://salsa.debian.org/debian/pkg-jquery-at.js/merge_requests/1/>?

-- 
 \ “I believe our future depends powerfully on how well we |
  `\ understand this cosmos, in which we float like a mote of dust |
_o__) in the morning sky.” —Carl Sagan, _Cosmos_, 1980 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#934945: startpar: insserv attemps to write to /etc/.boot.* even with -p option

[Dmitry Bogatov]

Package: startpar
Affects: inserv
Version: 1.20.0-2
Severity: important
Tags: upstream help

Folks, we have serious regression. Not sure, whether it is bug in
startpar test suite, which invokes `insserv' with `-p', but without
`-i', or it is regression in `insserv'.

Either way, insserv does not migrate to testing, and it is very bad.

https://ci.debian.net/data/autopkgtest/testing/amd64/s/startpar/2743262/log.gz


pgpyDa9Gc_zgl.pgp
Description: PGP signature

Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Dmitry Bogatov]

[2019-08-15 17:59] Paride Legovini 
> Dmitry Bogatov wrote on 06/08/2019:
> > So, please:
> > 
> >  * drop --as-needed
> >  * fix spelling
> >  * finalize changelog (dch -r)
>
> Done.

Uploaded. Tagged. Permissions granted.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#934946: irqbalance: cleanup debian/rules for downstream distros

[Dmitry Bogatov]

Package: irqbalance
Version: 1.5.0-4
Severity: wishlist
Tags: patch

From 20847346b88d621a2c4e86c07ed929ce0496b460 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Fri, 16 Aug 2019 10:08:08 +
Subject: [PATCH] Move code to link with libsystemd into separate file

This change makes `debian/rules' simplier and cleaner, and
makes live of downstream distributions easier.
---
 debian/config/systemd.mk | 3 +++
 debian/rules | 7 ++-
 2 files changed, 5 insertions(+), 5 deletions(-)
 create mode 100644 debian/config/systemd.mk

diff --git a/debian/config/systemd.mk b/debian/config/systemd.mk
new file mode 100644
index 000..d291743
--- /dev/null
+++ b/debian/config/systemd.mk
@@ -0,0 +1,3 @@
+ifeq (linux,$(DEB_HOST_ARCH_OS))
+   confflags += --with-systemd
+endif
diff --git a/debian/rules b/debian/rules
index 37a1513..d5c3a2a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
+include debian/config/systemd.mk
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
@@ -11,11 +12,7 @@ TMP = $(CURDIR)/debian/$(PACKAGE)
dh $@ --with autoreconf,runit
 
 override_dh_auto_configure:
-ifeq (linux,$(DEB_HOST_ARCH_OS))
-   dh_auto_configure -- --with-systemd
-else
-   dh_auto_configure
-endif
+   dh_auto_configure -- $(confflags)
 
 override_dh_install:
dh_install
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.


pgp_vA1ZvoIjG.pgp
Description: PGP signature

Bug#934920: lua-luaossl: FTBFS on x32 (sysctl unsupported on x32 kernel)

[Laurence Parry]

> Erk. Why would they ship a header that errors instead of no file at all?

It seems the idea of not shipping it was proposed but dismissed:
https://libc-alpha.sourceware.narkive.com/NmybqkkT/patch-add-x32-dummy-sysctl#post5

As I parse this: attempting to use sysctl on x32 is a clear error, it
doesn't exist. glibc wants to fail on compile, not runtime - and it
also doesn't want the developer missing the fact that sysctl is no
longer being used, hence the code paths are different; otherwise, you
might have decided to rely on randomization via sysctl and thought
that was fine for all x86 Linux ABIs, including x32. The way to do
that is to #error on include.

The "slightly annoying" result is that we need an x32-specific define
to prevent sysctl.h being included on x32. I suggested config.guess.h
because that seems to block any future use (notwithstanding the idea
that there *shouldn't* be any future use...).

--
Laurence "GreenReaper" Parry

Bug#934920: lua-luaossl: FTBFS on x32 (sysctl unsupported on x32 kernel)

[Daurnimator]

On Sat, 17 Aug 2019 at 12:08, Laurence Parry  wrote:
>
> > > Perhaps adding && !(__X86_64__ && __ILP32__) in there as well would fix 
> > > it?
> >
> > That check is for sys/sysctl.h, if that file still exists on X32 then
> > it's not the right macro to fix.
> > A better fix would be around HAVE_DECL_RANDOM_UUID in config.h.guess.
> > ...
> > A suitable fix would be to pass `-DHAVE_DECL_RANDOM_UUID=0` on X32.
>
> It exists, but accessing it triggers a preprocessor #error saying it
> doesn't work on x32:
> https://github.com/lattera/glibc/blob/master/sysdeps/unix/sysv/linux/x86/bits/sysctl.h

Erk. Why would they ship a header that errors instead of no file at all?

Bug#934920: lua-luaossl: FTBFS on x32 (sysctl unsupported on x32 kernel)

[Laurence Parry]

> > Perhaps adding && !(__X86_64__ && __ILP32__) in there as well would fix it?
>
> That check is for sys/sysctl.h, if that file still exists on X32 then
> it's not the right macro to fix.
> A better fix would be around HAVE_DECL_RANDOM_UUID in config.h.guess.
> ...
> A suitable fix would be to pass `-DHAVE_DECL_RANDOM_UUID=0` on X32.

It exists, but accessing it triggers a preprocessor #error saying it
doesn't work on x32:
https://github.com/lattera/glibc/blob/master/sysdeps/unix/sysv/linux/x86/bits/sysctl.h

If I'm reading it right, the sys/sysctl.h test in config.guess.h will
pass, because it uses __has_include. It will define HAVE_SYS_SYSCTL_H,
which is used in src/openssl.c:

#if HAVE_SYS_SYSCTL_H
#include  /* CTL_KERN KERN_RANDOM RANDOM_UUID sysctl(2) */
#endif

and then as I understand it, it will break at the preprocessor stage,
before it gets to:
#if HAVE_SYS_SYSCTL_H && HAVE_DECL_RANDOM_UUID

This is where it came up before (didn't see it in archived bugs
because the package was renamed):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831333

--
Laurence "GreenReaper" Parry

Bug#934944: RM: pythontracer -- ROM; Dead upstream

[TANIGUCHI Takaki]

Package: ftp.debian.org
Severity: normal

Please remove pythontracer from the archive.
Upstream is dead and low popcon.

Bug#932499: tigervnc-standalone-server: crashes on any exception on arm64

[Kevin Otte]

I confirm the LD_PRELOAD workaround works for me.

I also note that this package is not built against libunwind8 on mips or
s390x. I think arm64 should be added to this list.

Bug#934434: Missing bullets on items

[積丹尼 Dan Jacobson]

> "TK" == Tatsuya Kinoshita  writes:
TK> It depends on your fonts configuration.
Well that is too big a risk to take.
TK> Workaround: (setq w3m-use-symbol nil)
Thanks, that worked.
TK> Is it safe to disable w3m-use-symbol by default?
Whatever it is, only expert users should be using it by manual setting,
that way nobody risks missing bullets.

Bug#927920: Plymouth 0.9.4-1.1 Prevents Login Under Kernel 4.19.0-4 on ASUS ET2322

[Kurt Meyer]

This bug can be closed. A Plymouth upgrade fixed the issue or there may not 
have even been an issue. I experienced the same or similar issue later, 
including under Debian Stable, and just recently discovered that pressing the 
right menu button on the ASUS ET2322 AIO monitor displays the login screen.

Bug#934943: partman-basicfilesystems: Ability to set reserved for root space in blocks count

[Yury Vidineev]

Package: partman-basicfilesystems
Version: 148
Severity: wishlist
Tags: d-i

Dear Maintainer,

If I understand right now partman-basicfilesystems has an option 
reserved_for_root that is do something like tune2fs -m
It would be nice to have an option reserved_for_root_blocks that will do 
tune2fs -r

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

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

Bug#934724: Kernel Upgrade to 5.2.0-2 Appears to Break WiFi Using Broadcom BCM4352 Adapter

[Kurt Meyer]

You can close this. There is no bug. Evidently, the post install script either 
didn't, or failed to, update the kernel to include the wireless module. Steps I 
took to resolve the issue:

1. Install the module-assistant package:

sudo apt install module-assistant

2. From the command line, run:

sudo m-a prepare

3. From the command line, run:

sudo apt reinstall broadcom-sta-dkms

Bug#934920: lua-luaossl: FTBFS on x32 (sysctl unsupported on x32 kernel)

[Daurnimator]

On Sat, 17 Aug 2019 at 02:12, Laurence Parry  wrote:
>
> Package: lua-luaossl
> Version: 20161208-3
> Tags: ftbfs
> User: debian-...@lists.debian.org
> Usertags: x32
>
> lua-luaoss fails to build from source on x32 because:
>
> In file included from /usr/include/x86_64-linux-gnux32/sys/sysctl.h:63:0,
>  from src/openssl.c:9089:
> /usr/include/x86_64-linux-gnux32/bits/sysctl.h:19:3: error: #error
> "sysctl system call is unsupported in x32 kernel"
>  # error "sysctl system call is unsupported in x32 kernel"
> https://buildd.debian.org/status/fetch.php?pkg=lua-luaossl=x32=20161214-1=1489921871=0
>
> In config.h.guess I see:
>
> #ifndef HAVE_SYS_SYSCTL_H
> #define HAVE_SYS_SYSCTL_H ag_test_include(, (BSD || __GLIBC__))
> #endif
>
> Perhaps adding && !(__X86_64__ && __ILP32__) in there as well would fix it?

That check is for sys/sysctl.h, if that file still exists on X32 then
it's not the right macro to fix.
A better fix would be around HAVE_DECL_RANDOM_UUID in config.h.guess.

> Or there might be a better solution, like pre-defining HAVE_RANDOM_UUID 0
> (or HAVE_DECL_RANDOM_UUID in the current version)

A suitable fix would be to pass `-DHAVE_DECL_RANDOM_UUID=0` on X32.

Note that RANDOM_UUID is an enum not a macro.

> There was an attempt to remove sysctl(), but it was restored here for
> older kernels:
> https://github.com/wahern/luaossl/commit/7d6202bfa85e8f0bf90590a9381757f15e296a33
> Calls to sysctl remain in the current version .

See the related PR: https://github.com/wahern/luaossl/pull/61

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

[Chris Lamb]

Chris Lamb wrote:

> Patch attached that works for me on my Dell XPS 13

Antoine, does the patch attached to:

  https://bugs.debian.org/830726#43

… also work for you? If so, I will go ahead and upload.


Best wishes,

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

Bug#934942: Deal with

[積丹尼 Dan Jacobson]

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

$ w3m 
https://www.hpe.com/us/en/insights/articles/password-policy-recommendations-heres-what-you-need-to-know-1908.html
Go to first link "Skip to main content"
I.e.,
https://www.hpe.com/us/en/insights/articles/password-policy-recommendations-heres-what-you-need-to-know-1908.html#content
Lynx can do it.
w3m can't.
That's because it is in 

Bug#934941: python-bumps: Please drop unused (build,test) dependency on python{3,}-sklearn

[Steve Langasek]

Package: python-bumps
Version: 0.7.11-2
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

As part of an effort to accelerate the removal of python-pandas from Ubuntu,
I've identified that python-bumps has a build and test dependency on
python{3,}-sklearn that is unused and makes no difference to the build and
test results.  I've therefore uploaded the attached patch to Ubuntu, which
facilitates us removing python-sklearn (a reverse-dependency of
python-pandas) without having to first drop pytho-bumps, which itself has
reverse-dependencies.

Since the build-dependency is unused, I think this would also be a
reasonable change to make in Debian, and would somewhat simplify the
dependency graph for python2 removal, so I'm submitting it for your
consideration.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru python-bumps-0.7.11/debian/control python-bumps-0.7.11/debian/control
--- python-bumps-0.7.11/debian/control  2018-12-25 23:35:44.0 -0800
+++ python-bumps-0.7.11/debian/control  2019-08-16 15:38:00.0 -0700
@@ -19,7 +19,6 @@
  python-setuptools,
  python-pyparsing (>= 1.5.2),
  python-six,
- python-sklearn,
  python-typing,
  python-wxgtk3.0,
  python3-all,
@@ -31,7 +30,6 @@
  python3-setuptools,
  python3-pyparsing (>= 1.5.2),
  python3-six,
- python3-sklearn,
  python3-sphinx,
  python3-wxgtk4.0,
  librandom123-dev,
diff -Nru python-bumps-0.7.11/debian/tests/control 
python-bumps-0.7.11/debian/tests/control
--- python-bumps-0.7.11/debian/tests/control2018-07-10 08:08:15.0 
-0700
+++ python-bumps-0.7.11/debian/tests/control2019-08-16 15:38:00.0 
-0700
@@ -4,7 +4,6 @@
  python-all,
  python-bumps,
  python-nose,
- python-sklearn,
  python-wxgtk3.0
 
 Tests: python3-bumps
@@ -12,5 +11,4 @@
 Depends:
  python3-all,
  python3-bumps,
- python3-nose,
- python3-sklearn
+ python3-nose

Bug#934791: libgtk-3-0: complains when attempting to register already registered client

[brian m. carlson]

On 2019-08-15 at 07:34:00, Simon McVittie wrote:
> Control: tags -1 + moreinfo
> 
> On Wed, 14 Aug 2019 at 23:48:09 +, brian m. carlson wrote:
> > GTK+ produces the following warning when attempting to register a client
> > with the session manager and the client is already registered:
> > 
> >   (caja:3729): Gtk-WARNING **: 02:59:57.229: Failed to register client: 
> > GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
> > client
> 
> Under what circumstances does this occur? I see the program in question
> is caja. What desktop environment is this in, and how can this bug be
> reproduced?

This is in MATE with a typical mate-session startup. This message gets
logged to ~/.xsession-errors, and it's trivially reproducible by running
"killall caja". I believe I've seen it before when running from the
command line, but I can't seem to reproduce that now.

I unfortunately don't have a fresh session to test against, and MATE
isn't likely to run nicely in a Docker container, which is my usual test
environment for bugs.

> (I assume it's either GNOME, one of the various GNOME forks, or XFCE,
> based on the D-Bus APIs used in the function that contains that warning.)
> 
> I don't know the session manager API well enough to know immediately
> whether this message indicates a bug in the session manager, the
> application, GTK, or something else.

I see this much like reporting an ENOENT with unlink(2): what you wanted
has already been done, so barring some specific circumstance where you
know it will be a problem, there's no reason to report an error.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#934940: Depends: misses libscalar-list-utils-perl

[Andreas Ley]

Package: libtemplate-perl
Version: 2.24-1.2+b3
Severity: minor

Dear Maintainer,

IMHO debian/control Depends: line misses libscalar-list-utils-perl since 
Template/Service.pm contains "use Scalar::Util 'blessed';"

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

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=de_DE.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 libtemplate-perl depends on:
ii  libappconfig-perl   1.66-2
ii  libc6   2.24-11+deb9u4
ii  perl5.24.1-3+deb9u5
ii  perl-base [perlapi-5.24.1]  5.24.1-3+deb9u5

libtemplate-perl recommends no packages.

Versions of packages libtemplate-perl suggests:
pn  libtemplate-perl-doc 
pn  libtemplate-plugin-gd-perl   
pn  libtemplate-plugin-xml-perl  

-- no debconf information

Bug#925994: closed by Patrick Matthäi (reply to pmatth...@debian.org) (Re: Bug#925994: maybe not present in latest version)

[Chrisu Jaehnl]

Unfortunately I cannot close this bug for me.

I got kdenlive 19.04.3-3 minutes ago and tried to create a new project: frozen.
kill - restart,
I tried to open an existing project: frozen.
kill.

Then I took the app-image:
kdenlive-19.04.3b-x86_64.appimage

and that works fine at all.

My system is debian testing/unstable and up to date. I have no idea where to 
start searching.
And sorry for the wrong tagging "a11y", after posting I saw it was wrong.

First I thought about a dependency-problem with audio. But as seen today it 
must be something different, because kdenlive dies after either trying to 
create a new project or opening an existing project.

best reagards, still using kdenlive,
Chrisu


On Mon, Aug 12, 2019 at 12:18:08PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the kdenlive package:
> 
> #925994: kdenlive freezes after doing anything
> 
> It has been closed by Patrick Matthäi  (reply to 
> pmatth...@debian.org).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Patrick Matthäi 
>  (reply to pmatth...@debian.org) by
> replying to this email.
> 
> 
> -- 
> 925994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925994
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> From: Patrick Matthäi 
> To: Thorsten , 925994-d...@bugs.debian.org
> Subject: Re: Bug#925994: maybe not present in latest version
> Date: Mon, 12 Aug 2019 14:13:57 +0200
> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
>  Thunderbird/60.8.0
> 
> 
> Am 10.08.2019 um 15:02 schrieb Thorsten:
> > Hej team,
> >
> > I also had same issues with kdenlive being unusable a few weeks back:
> > dropping any clip on the timeline crashed kdenlive. From gut-feeling, no
> > further investigation though, it might had also something to do with
> > audio or another playback related issue.
> >
> > Now, after upgrade to latest 19.04.3-3 and potentially related upgrades
> > in dependend packages *it seems to work again*.
> >
> > This bug may be resolved now. Can the initial reporter confirm? It is
> > definitely NOT tag:a11y.
> >
> > cheers,
> > Thorsten
> 
> Hey,
> 
> many thanks for your feedback :)
> 
> -- 
> /*
> Mit freundlichem Gruß / With kind regards,
>  Patrick Matthäi
>  GNU/Linux Debian Developer
> 
>   Blog: http://www.linux-dev.org/
> E-Mail: pmatth...@debian.org
> patr...@linux-dev.org
> */

> From: Christian Jähnl 
> To: Debian Bug Tracking System 
> Subject: kdenlive freezes after doing anything
> Date: Sat, 30 Mar 2019 00:06:27 +0100
> X-Mailer: reportbug 7.5.2
> 
> Package: kdenlive
> Version: 18.12.3-1
> Severity: important
> Tags: a11y
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> I installed kdenlive 18.12.3-1.
> I opened an existing project and clicked in the timeline --> frozen.
> killing kdenlive - new start
> I added a clip and clicked "play" (worked), draged the clip to the timeline, 
> clicked "play" --> frozen.
> killing kdenlive
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I downloaded the App "kdenlive-18.12.1b-x86_64.appimage", chmod +x --> it 
> worked.
> 
> The last app that worked was: kdenlive-18.08.3-x86_64.AppImage , all other 
> apps between 18.08... and 18.12.1b...  had the same behaviour as the 
> installed version
> 
>* What was the outcome of this action?
> 
> After starting the installed kdenlive from terminal this was the output after 
> "New project --> 30 fps --> ok --> add a clip --> play --> drag to timeline 
> --> play --> stop --> click on a different place in the timeline --> play --> 
> frozen"
> 
> **
> chrisu@zat:~$ kdenlive
> No LADSPA plugins were found!
> 
> Check your LADSPA_PATH environment variable.
> Empty filename passed to function
> Loading effects from  "/usr/share/kdenlive/effects"
> qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 11991, 
> resource id: 62914946, major code: 130 (Unknown), minor code: 3
> qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12023, 
> resource id: 62914946, major code: 130 (Unknown), minor code: 3
> qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12026, 
> resource id: 62914946, major code: 130 (Unknown), minor code: 3
> [swscaler @ 0x7fa0485b6480] Warning: data is not aligned! This can lead to a 
> speed loss
> qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21195, 
> resource id: 62914946, major code: 130 (Unknown), minor code: 3
> qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21227, 
> resource id: 62914946, major code: 130 (Unknown), minor code: 3
> qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21230, 
> resource id: 62914946, major code: 130 (Unknown), minor code: 3
> 

Bug#923352: RPM maintainer volunteer

[Brett D]

Hello,

I would like to commit to being the maintainer of the rpm package.
I am new to Debian, but I understand the very basics of package
maintenance, UNIX-like infrastructure, and C development.
Please let me know what further actions need be taken; I suppose that upon
preliminary approval, I would then have to find a team to sponsor me in
maintaining this package.

Thank you,
Brett Dispoto

Bug#934826: buster-pu: package console-setup/1.193~deb10u1

[Cyril Brulebois]

Adam D. Barratt  (2019-08-16):
> Control: tags -1 + confirmed
> 
> On Thu, 2019-08-15 at 16:22 +0200, Cyril Brulebois wrote:
> > I'd like to get #924657 fixed in buster. A Perl change triggered a
> > bunch of brokenness in translations, and I haven't been able to
> > review the fix before the release. I've done that now, as documented
> > in:
> >   https://bugs.debian.org/924657#49
> 
> Please go ahead; thanks.

Thanks, uploaded.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#934827: buster-pu: package apt-setup/1:0.151~deb10u1

[Cyril Brulebois]

Adam D. Barratt  (2019-08-16):
> Control: tags -1 + confirmed
> 
> On Thu, 2019-08-15 at 17:01 +0200, Cyril Brulebois wrote:
> > I'd like to get apt-setup updated in buster to fix preeeding apt keys
> > (#851774). This update was kindly tested by Moritz by fetching the
> > updated udebs from unstable, on buster systems:
> >   https://bugs.debian.org/851774#108
> 
> Please go ahead; thanks.

Thanks, uploaded.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#925687: fswatch: ftbfs with GCC-9

[Alf Gaida]

hahaha - good joke:

The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

Bug#892264: Hy 0.17.0

[Tianon Gravi]

On Tue, 4 Jun 2019 at 16:59, Tianon Gravi  wrote:
> I've updated Git with what I think is finally successful packaging of
> a newer Hy version (0.17.0 ATM).  It requires updated "python-astor"
> (I tested 0.8.0) and "python-rply" (I tested 0.7.7), which I don't
> have time to chase down properly right now.

Hi Tristan!  To this end (getting Hy 0.17.0 in the archive) I've
updated Git for "python-rply" to 0.7.7 (from 0.7.4), but I wanted to
reach out before uploading to check whether you're OK with this
version bump?

(You're the human listed in Maintainer/Uploaders :D)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#934938: [cargo-docs] missing files

[Ximin Luo]

Hi, it will be non-trivial to fix this bug and I personally am unlikely to have 
time for it. You will need to:

1. vendor mdbook as well as cargo. This will involve editing the debian scripts 
in debian/make_orig_multi.sh, something that involves calling `cargo vendor` 
for the src/doc directory.
2. patch mdbook in the same way that we do so in the Debian rustc package, to 
make it not generate links to online javascript and other resources, but 
instead load them locally.
3. build mdbook during the cargo build
4. call mdbook to build the cargo doc

jnq...@gmail.com:
> Package: cargo-doc
> Version: 0.37.0-3
> 
> This package surely is intended to bundle the docs as available here,
> is it not?: https://doc.rust-lang.org/cargo/index.html
> 
> if I browse through the contents of /usr/share/doc/cargo-doc, there's
> nothing useful at all, unlike /usr/share/doc/rust-doc/ from `rust-
> doc`...
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#934034: Bug#934775: stretch-pu: package monkeysphere/0.41-1+deb9u1

[Chris Lamb]

tags 934034 + pending
thanks

[Adding 934...@bugs.debian.org to CC, tagging original bug as pending; not this 
pu...]

Hi Adam,

> >   monkeysphere (0.41-1+deb9u1) stretch; urgency=medium
> >   
> > * Prevent a FTBFS by updating the tests to accommodate an updated GnuPG 
> > in
> >   stretch now producing a different output. (Closes: #934034)
> 
> Please go ahead; thanks.

Thanks:

$ dput monkeysphere_0.41-1+deb9u1_amd64.changes
Uploading monkeysphere_0.41-1+deb9u1.dsc
Uploading monkeysphere_0.41-1+deb9u1.debian.tar.xz
Uploading agent-transfer-dbgsym_0.41-1+deb9u1_amd64.deb
Uploading agent-transfer_0.41-1+deb9u1_amd64.deb
Uploading monkeysphere_0.41-1+deb9u1_all.deb
Uploading monkeysphere_0.41-1+deb9u1_amd64.buildinfo
Uploading monkeysphere_0.41-1+deb9u1_amd64.changes

$ echo $?
0


Best wishes,

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

Bug#934901: marked as done (Please switch to Python 3 or remove your package from Sid/Bullseye)

[Gerber van der Graaf]

Hello,
The PyGpiv package is not maintained anymore from upsream. So I think
it's a good idea to remove python-gpiv from Sid. As I'm not a DD, I
cannot do this by myself.

Sincerely, Gerber van der Graaf


On Fri, 2019-08-16 at 17:33 +, Debian Bug Tracking System wrote:
> Your message dated Fri, 16 Aug 2019 17:31:53 +
> with message-id 
> and subject line Bug#934832: Removed package(s) from unstable
> has caused the Debian Bug report #934901,
> regarding Please switch to Python 3 or remove your package from
> Sid/Bullseye
> to be marked as done.
> 
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
> 
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
> 
> 

Bug#934939: RFS: xlog/2.0.17-1

[Ervin Hegedüs]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "xlog"

 * Package name: xlog
   Version : 2.0.17-1
   Upstream Author : Andy Stewart KB1OIQ 
 * URL : http://savannah.nongnu.org/projects/xlog
 * License : GPL
   Section : hamradio

It builds those binary packages:

  xlog - GTK+ Logging program for Hamradio Operators
  xlog-data - data for xlog, a GTK+ Logging program for Hamradio
  Operators

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/x/xlog/xlog_2.0.17-1.dsc

More information about xlog can be obtained from
http://savannah.nongnu.org/projects/xlog

Changes since the last upload:
  * Team upload.
  * New upstream release (Closes: #925864).
  * Bump Standards-Version to 4.4.0.


Regards,
 Ervin Hegedüs

Bug#934937: man-db: Refers to undocumented(7) which has gone

[Robert Luberda]

Package: man-db
Version: 2.8.6.1-1
Severity: minor

The undocumented(7) man page was removed 3 years ago:

  manpages (4.04-2) unstable; urgency=medium
  
... strip other changelog entries ...

* Remove obsolete manpage undocumented.7.
  This manpage was provided in order to comply with an ancient
  policy version. The manpage is no longer needed since Nov 2002.
  Closes: #506653, LP:#426359
  
   -- Dr. Tobias Quathamer   Mon, 15 Feb 2016 14:02:08 +0100


but man-db stil refers to it:

  robert@vox:/tmp$ /usr/bin/man -L C 8 test
  No manual entry for test in section 8
  See 'man 7 undocumented' for help when manual pages are not available.



Regards,
robert

PS. It looks like  ancient bug #32019 ('man-db: Move undocumented(7) from 
manpages to
 man-db') might be no longer relevant.


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

Kernel: Linux 4.19.37-vox (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages man-db depends on:
ii  bsdmainutils   11.1.2+b1
ii  debconf [debconf-2.0]  1.5.73
ii  dpkg   1.19.7
ii  groff-base 1.22.4-3
ii  libc6  2.28-10
ii  libgdbm6   1.18.1-4+b1
ii  libpipeline1   1.5.1-2
ii  libseccomp22.4.1-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

man-db recommends no packages.

Versions of packages man-db suggests:
pn  apparmor   
ii  chromium [www-browser] 76.0.3809.100-1
ii  elinks [www-browser]   0.13~20190125-3
ii  firefox-esr [www-browser]  60.8.0esr-1
ii  groff  1.22.4-3
ii  less   487-0.1+b1
ii  links [www-browser]2.19-2
ii  lynx [www-browser] 2.9.0dev.2-1

-- debconf information excluded

Bug#934938: [cargo-docs] missing files

[jnqnfe]

Package: cargo-doc
Version: 0.37.0-3

This package surely is intended to bundle the docs as available here,
is it not?: https://doc.rust-lang.org/cargo/index.html

if I browse through the contents of /usr/share/doc/cargo-doc, there's
nothing useful at all, unlike /usr/share/doc/rust-doc/ from `rust-
doc`...

Bug#932578: PATCH

[sam penny]

The release notes for PILlow 6.1 
(https://pillow.readthedocs.io/en/stable/releasenotes/6.0.0.html#backwards-incompatible-changes)
 indicate that Image.VERSION has been dropped in favour of using 
Image.__version__. VERSION was fossilised at '1.1.7' 9 years ago to avoid 
confusing legacy users of the original PIL library.

The only usage of this attribute is to check to see if the version is 1.1.7 
(which it hasn't been for some time) in order to work around a bug. The 
relevant code is

## BEGIN CODE

if Image.VERSION == '1.1.7':

    def split(image):
    """Work around for bug in Pil 1.1.7

    :param image: input image
    :type image: PIL image object
    :returns: the different color bands of the image (eg R, G, B)
    :rtype: tuple
    """
    image.load()
    return image.split()
else:

    def split(image):
    """Work around for bug in Pil 1.1.7

    :param image: input image
    :type image: PIL image object
    :returns: the different color bands of the image (eg R, G, B)
    :rtype: tuple
    """
    return image.split()

## END CODE

Given that the workaround is long irrelevant, we should probably just define 
split() according to the else clause. The docstring should also probably be 
updated.

The safer alternative is to replace the condition of the if statement with

if hasattr(Image, 'VERSION') and Image.VERSION == '1.1.7':

which works for me and seems like it should work for anyone else, too, even if 
they're using the long abandoned original PIL library, though I don't fancy 
testing that.

## BEGIN PATCH
--- bin/imtools.py    2018-08-07 13:51:47.0 +0100
+++ bin/imtools.py  2019-08-16 22:05:05.018603503 +0100
@@ -620,7 +620,7 @@
 has_alpha(image)


-if Image.VERSION == '1.1.7':
+if hasattr(Image, '"VERSION') and Image.VERSION == '1.1.7':

 def split(image):
 """Work around for bug in Pil 1.1.7
## END PATCH

Bug#934936: The Window Extends Beyond the Display

[mason1920]

Package: libreoffice
Version: 1:6.3.0-2
Severity: minor

Dear Maintainer,

I have two displays joined side by side.

Maximizing the start center or any other LibreOffice component/package on 
either screen cause a 1 pixel bar to appear on the adjacent screen with 
equivalent height and position as the window. This doesn't occur with any other 
applications.

I expect LibreOffice to not go beyond the monitor it's maximized in.

Bug#934500: dh-runit: permissions of supervise directory

[Lorenz]

Il giorno mer 14 ago 2019 alle ore 21:22 Dmitry Bogatov 
ha scritto:

>Yes, I go this way.

Ok.
in commit d07519ae you already create /run/runit/supervise directory,
but the directory for the appendant log of 'foo' service will be
/run/runit/log/supervise/foo
or
/run/runit/supervise/foo.log ?

Lorenzo

Bug#934935: Should docbook2odf be removed?

[Moritz Muehlenhoff]

Package: docbook2odf
Severity: serious

Should docbook2odf be removed?

It's unmaintained (last maintainer upload in 2007), last upload in 2010
and has been dropped from testing for three years now.

Cheers,
Moritz

Bug#784885: [dput-ng-maint] Bug#784885: dcut: "dm" subcommand do not work

[Tari]

Hi

To fix the key error for missing valid commands I added some checks. Would that 
solve the bug? Or should we check if the host is ftp-master when dm is supplied?

./dput/command.py in invoke_dcut()

 command.validate(args)

+if 'ftp-master' not in profile['name'] and 'dm' in command.cmd_name:
+   raise DcutError("Use DM command with ftp-master")
+
 if args.passive:
 force_passive_ftp_upload(profile)

Best
Tari
diff -Nru dput-ng-1.28/dput/command.py dput-ng-1.28+1/dput/command.py
--- dput-ng-1.28/dput/command.py	2018-08-25 10:39:16.0 +0200
+++ dput-ng-1.28+1/dput/command.py	2019-08-14 22:37:16.0 +0200
@@ -75,6 +75,10 @@
 
 def load_commands(profile):
 commands = []
+
+if not 'valid_commands' in profile:
+return []
+
 for command in profile['valid_commands']:
 logger.debug("importing command: %s" % (command))
 try:
@@ -196,8 +200,13 @@
 if args.simulate:
 logger.warning("Not uploading for real - dry run")
 
-command = args.command
-assert(issubclass(type(command), AbstractCommand))
+command = None
+if hasattr(args,'command'):
+command = args.command
+
+if not command:
+   raise DcutError("No commands given")
+
 command.validate(args)
 
 if args.passive:
diff -Nru dput-ng-1.28/dput/profile.py dput-ng-1.28+1/dput/profile.py
--- dput-ng-1.28/dput/profile.py	2018-02-22 10:00:33.0 +0100
+++ dput-ng-1.28+1/dput/profile.py	2019-08-14 22:37:16.0 +0200
@@ -197,8 +197,8 @@
 return config.get_config(host)
 
 if host is not None:
-raise DputConfigurationError("Error, was given host, "
- "but we don't know about it.")
+raise DputConfigurationError("Was given host, "
+ "but not found in the profile/config.")
 
 for block in configs:
 try:

Bug#933970: unzip 6.0-21+deb9u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 933970 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: unzip
Version: 6.0-21+deb9u2

Explanation: fix incorrect parsing of 64-bit values in fileio.c; fix zip-bomb 
issues [CVE-2019-13232]

Bug#934311: ncbi-tools6 6.1.20170106+dfsg1-0+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 934311 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: ncbi-tools6
Version: 6.1.20170106+dfsg1-0+deb10u1

Explanation: repackage without non-free data/UniVec.*

Bug#933828: ncbi-tools6 6.1.20170106+dfsg1-0+deb9u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 933828 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: ncbi-tools6
Version: 6.1.20170106+dfsg1-0+deb9u1

Explanation: repackage without non-free data/UniVec.*

Bug#934934: buster-pu: package piuparts/1.0.0+deb10u1

[Holger Levsen]

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

Hi,

We'd like to update piuparts with the following changes in buster, fixing a
bunch of rather important bugs (as well as one trivial wishlist bug and a 
trivial normal bug), including one for buster=stable (which missed the buster
relase because 1.0.1 was not accepted).

 piuparts (1.0.0+deb10u1) buster; urgency=medium
 .
   * Happy 26th birthday, Debian! And many thanks to all the contributors!
 .
   [ Andreas Beckmann ]
   * piuparts.py:
 - Run pre_remove scripts before computing packages to be removed.
 - Fix spurious failure to remove packages with names ending with '+'.
 - Add '--max-command-output-size' option to allow overriding the default
   of 8 MB for debugging runs.
   * piuparts-slave.py:
 - Generate separate tarball names for --merged-usr chroots.
   * detect_well_known_errors.py:
 - process untestable logs.
   * Makefile: use gzip -n for reproducibility.
   * piuparts.conf, distros.conf: Update for buster release.
   * custom-scripts: some updates for buster. If custom-scripts are used, it's
 probably better to use piuparts from bpo.
 .
   [ Holger Levsen ]
   * Cherry-picking the above.

The diffstat to 1.0.0 in buster is:

$ debdiff piuparts_1.0.0.dsc piuparts_1.0.0+deb10u1.dsc | diffstat
 .gitignore|3 +
 Makefile  |8 ++--
 conf/distros.conf |8 ++--
 custom-scripts/scripts/post_distupgrade_exceptions|1 
 custom-scripts/scripts/post_setup_minimize|2 -
 custom-scripts/scripts/pre_distupgrade_zz_database-server |7 ++--
 debian/.gitignore |5 ++
 debian/changelog  |   24 ++
 instances/piuparts.conf-template.pejacevic|4 --
 instances/piuparts.conf.anbe  |7 
 master-bin/detect_well_known_errors.py|2 -
 piuparts-slave.py |3 +
 piuparts.1.txt|4 ++
 piuparts.py   |   22 
 piupartslib/conf.py   |6 ++-
 15 files changed, 73 insertions(+), 33 deletions(-)

The full diff is attached.

Thanks for your work on buster!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
diff -Nru piuparts-1.0.0/conf/distros.conf piuparts-1.0.0+deb10u1/conf/distros.conf
--- piuparts-1.0.0/conf/distros.conf	2019-05-04 21:37:32.0 +0200
+++ piuparts-1.0.0+deb10u1/conf/distros.conf	2019-08-16 15:05:52.0 +0200
@@ -176,19 +176,19 @@
 
 # alias
 [oldoldstable]
-distribution = wheezy
+distribution = jessie
 
 # alias
 [oldstable]
-distribution = jessie
+distribution = stretch
 
 # alias
 [stable]
-distribution = stretch
+distribution = buster
 
 # alias
 [testing]
-distribution = buster
+distribution = bullseye
 
 
 # It's also possible to have "virtual" entries by setting uri to
diff -Nru piuparts-1.0.0/custom-scripts/scripts/post_distupgrade_exceptions piuparts-1.0.0+deb10u1/custom-scripts/scripts/post_distupgrade_exceptions
--- piuparts-1.0.0/custom-scripts/scripts/post_distupgrade_exceptions	2019-05-04 21:37:32.0 +0200
+++ piuparts-1.0.0+deb10u1/custom-scripts/scripts/post_distupgrade_exceptions	2019-08-16 15:21:58.0 +0200
@@ -100,7 +100,6 @@
 fi
 
 if [ "$PIUPARTS_DISTRIBUTION" = "buster" ] || \
-	[ "$PIUPARTS_DISTRIBUTION" = "sid" -a "$PIUPARTS_DISTRIBUTION_PREV" = "stretch" ]; then
 
 	# libc-bin only upgrades pristine /etc/nsswitch.conf
 	if grep -q '^passwd:.*compat' /etc/nsswitch.conf ; then
diff -Nru piuparts-1.0.0/custom-scripts/scripts/post_setup_minimize piuparts-1.0.0+deb10u1/custom-scripts/scripts/post_setup_minimize
--- piuparts-1.0.0/custom-scripts/scripts/post_setup_minimize	2018-04-22 04:30:08.0 +0200
+++ piuparts-1.0.0+deb10u1/custom-scripts/scripts/post_setup_minimize	2019-08-16 15:05:52.0 +0200
@@ -8,7 +8,7 @@
 		jessie)
 			dpkg --purge gcc-4.8-base
 			;;
-		sid|stretch)
+		stretch)
 			dpkg --purge lsb-base tzdata
 			;;
 	esac
diff -Nru piuparts-1.0.0/custom-scripts/scripts/pre_distupgrade_zz_database-server piuparts-1.0.0+deb10u1/custom-scripts/scripts/pre_distupgrade_zz_database-server
--- piuparts-1.0.0/custom-scripts/scripts/pre_distupgrade_zz_database-server	2019-05-04 21:37:32.0 +0200
+++ piuparts-1.0.0+deb10u1/custom-scripts/scripts/pre_distupgrade_zz_database-server	2019-08-16 15:21:58.0 +0200
@@ -56,7 +56,7 @@
 		CANDIDATES="$CANDIDATES 

Bug#934827: buster-pu: package apt-setup/1:0.151~deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2019-08-15 at 17:01 +0200, Cyril Brulebois wrote:
> I'd like to get apt-setup updated in buster to fix preeeding apt keys
> (#851774). This update was kindly tested by Moritz by fetching the
> updated udebs from unstable, on buster systems:
>   https://bugs.debian.org/851774#108

Please go ahead; thanks.

Regards,

Adam

Bug#934775: stretch-pu: package monkeysphere/0.41-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2019-08-14 at 10:21 -0700, Chris Lamb wrote:
>   monkeysphere (0.41-1+deb9u1) stretch; urgency=medium
>   
> * Prevent a FTBFS by updating the tests to accommodate an updated
> GnuPG in
>   stretch now producing a different output. (Closes: #934034)

Please go ahead; thanks.

Regards,

Adam

Bug#934826: buster-pu: package console-setup/1.193~deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2019-08-15 at 16:22 +0200, Cyril Brulebois wrote:
> I'd like to get #924657 fixed in buster. A Perl change triggered a
> bunch of brokenness in translations, and I haven't been able to
> review the fix before the release. I've done that now, as documented
> in:
>   https://bugs.debian.org/924657#49

Please go ahead; thanks.

Regards,

Adam

Bug#933125: buster-pu: package systemd/241-5+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote:
> I'd like to make a stable upload for systemd, fixing the following
> issues:
[...]
> 241-5+deb10u1 is identical to 241-7 which has been uploaded to
> unstable/bullseye and we haven't received any regression reports so
> far.

In that case, feel free to make it -7~deb10u1, with the appropriate
changelog wrangling, if that would be preferable.

Regards,

Adam

Bug#933263: stretch-pu: package freetype/2.6.3-3.2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed d-i

On Fri, 2019-08-16 at 18:04 +1000, Hugh McMaster wrote:
> On Sun, 4 Aug 2019 at 11:13 am, Hugh McMaster wrote:
> > Control: retitle -1 stretch-pu: package freetype/2.6.3-3.2+deb9u1
> > 
> > Updated debdiff, now with correct update version.
> > 
> 
> Just following up on this. I’m guessing it needs a d-i ack as well?

That's correct, yes.

Regards,

Adam

Bug#929871: RM: simpleid/0.8.1-15

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Sun, 2019-06-02 at 17:26 +0900, Hideki Yamane wrote:
>  As Bug#929575, simpleid 0.8.1-15 doesn't work with PHP7.x that is
> shipped
>  with Debian9 "stretch" and Debian10 "buster", so I propose we'll
> remove it.
>  And, for testing package was removed (#929832) but stable package
> still
>  remains.

This bug was tagged "stretch", but mentions buster and stable. Where
exactly are you trying to request removal from?

(If the answer is both stretch and buster, note that that is two
removals and thus requires two removal request bugs.)

Regards,

Adam

Bug#876566: printfilters-ppd: Depends of no longer available package (mpage)

[Tari]

Hi

What should we do here with the from Debian removed package? We could at least 
move the mpage from depend to recommend to fix the issue with install and 
build. See diff below for that small change. But as Jeremy Bicha said on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876571, also recommending a 
no-longer-builtin package would be a bug. Removing everything related to mpage?

Can I help making needed changes?

Best
Taridiff -u printfilters-ppd-2.13/debian/control printfilters-ppd-2.13-1/debian/control
--- printfilters-ppd-2.13/debian/control
+++ printfilters-ppd-2.13-1/debian/control
@@ -7,8 +7,8 @@

Package: printfilters-ppd
Architecture: any
-Depends: transfig, mpage, perl (>= 5.005), libprintsys, ppdfilt, file, ${shlibs:Depends}, ${misc:Depends}
-Recommends: enscript, lprng | lpr-ppd, ghostscript, smbclient
+Depends: transfig, perl (>= 5.005), libprintsys, ppdfilt, file, ${shlibs:Depends}, ${misc:Depends}
+Recommends: enscript, mpage, lprng | lpr-ppd, ghostscript, smbclient
Suggests: dvips, netpbm, libjpeg-progs|libjpeg-gif, libtiff-tools, recode, djtools, bzip2
Conflicts: apsfilter, magicfilter
Description: filters from the GNUlpr printing system

Bug#858071: Patch applied to fix the bug

[Michael Rasmussen]

Hi Stephen,

Applied patch fixes the bug. I am puzzled Why this fixes the bug?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
I don't want a pickle,
I just wanna ride on my motorsickle.
And I don't want to die,
I just want to ride on my motorcy.
Cle.
-- Arlo Guthrie
--- window.py	2019-08-16 21:45:54.750223538 +0200
+++ /tmp/window.py	2019-08-16 21:46:25.190283579 +0200
@@ -236,7 +236,7 @@
 	tree.set_headers_visible(False)
 	tree.set_show_expanders(False)
 	tree.set_level_indentation(20)
-	# tree.set_fixed_height_mode(True)
+	tree.set_fixed_height_mode(True)
 	tree.set_enable_tree_lines(True)
 	tree.set_reorderable(False)
 	tree.set_enable_search(False)


pgpdQL0zll8ln.pgp
Description: OpenPGP digital signature

Bug#934932: presentty (build-)depends on cruft package.

[peter green]

Package: presentty
Version: 0.2.0-1
Severity: serious
Tags: bullseye, sid

Presentty (build-)depends on the python-pbr binary package which is no longer 
built by the corresponding source package.

There is a bug report questioning whether said dependency is really necessary ( 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780009 ) , but even if it is 
not and removing it works as a short term fix, you really need to think about 
migrating to python3 if your package is going to stay around in the long term.

Bug#934933: backports-friendly build-depends

[Daniel Baumann]

Package: kdenlive
Version: 19.08.0-1
Severity: wishlist

Hi,

kdenlive FTBFS with mlt << 6.10 which is the case for buster. It would
be nice if you could update the build-depends to require 6.10 to ease
backports.

Regards,
Daniel

Bug#934931: planet-venus: depends on cruft package

[peter green]

Package: planet-venus
Version: 0~git9de2109-4.2
Severity: serious
Tags: bullseye, sid

planet-venus depends on python-portalocker which is no longer built by the 
portalocker source package.

If you want your package to stay around you probably need to migrate to python 
3.

Bug#934925: remove debian/patches/unbundle-sip.patch to provide wx.siplib ?

[Scott Talbert]

On Fri, 16 Aug 2019, Yaroslav Halchenko wrote:


Newer upstream version of fsleyes uses wx.siplib
(ref: https://github.com/pauldmccarthy/fsleyes/issues/29)
build of which is apparently  stripped away from the package in Debian:
https://salsa.debian.org/freewx-team/wxpython4.0/blob/master/debian/patches/unbundle-sip.patch
with the name suggeting that it would have its own package but I failed to find 
it:

> apt-cache search python wx sip
>

so I guess it never saw a life.

Unfortunately patch also doesn't provide any other details/hints on why
unbundling was needed and how was it handled.  So I wondered if just it could
be built/shipped along?


wx.siplib is unbundled for multiple reasons:

1) It is Debian policy to not use bundled code, see [1].

2) The wxPython distribution doesn't include all of the source code for 
sip, so it's not possible to build it.  The upstream build process for 
wxPython downloads a precompiled binary from the internet which is not 
allowed in 
Debian.



As far as how to address this I can think of a few options:

1) You can patch fsleyes to use the public sip module (provided by the 
python3-sip package) instead of the wx.siplib module.  In other words, you 
would 'import sip' instead of 'import wx.siplib'.


2) I could try to look into providing some sort of wx.siplib wrapper 
around the public sip module.


Scott

[1] 
https://www.debian.org/doc/debian-policy/ch-source.html#convenience-copies-of-code

Bug#934206: buster-pu: package golang-github-docker-docker-credential-helpers/0.6.1-2+deb10u1

[Adam D. Barratt]

On Sat, 2019-08-10 at 15:38 +0700, Arnaud Rebillout wrote:
> On 8/10/19 2:07 PM, Shengjing Zhu wrote:
> > On Sat, Aug 10, 2019 at 2:56 PM Shengjing Zhu 
> > wrote:
> > > On Fri, Aug 9, 2019 at 10:09 PM Arnaud Rebillout
> > >  wrote:
> > > > On 8/9/19 5:15 PM, Adam D. Barratt wrote:
> > > > > The module apparently has three reverse build-dependencies:
> > > > > 
> > > > > amazon-ecr-credential-helper:
> > > > > golang-github-docker-docker-credential-helpers-dev
> > > > > docker-pycreds: golang-docker-credential-helpers
> > > > > docker.io: golang-github-docker-docker-credential-helpers-dev 
> > > > > (>= 0.6.1~)
> > > > > 
> > > > > Would this update imply any of those needing to be rebuilt?
> > > > > If so, is
> > > > > that the end of the tree, or do we end up down a rabbit hole
> > > > > of Go
> > > > > libraries?
[...]
> > > I think checking Built-Using is the right answer (for buster).
> > > 
> > > For src:golang-github-docker-docker-credential-helpers, the
> > > following
> > > packages need rebuild:
> > > 
> > > src:amazon-ecr-credential-helper
> > > 
[...]
> > > The pkg:docker.io maybe is affected, but I'm not sure.
> > src:golang-github-docker-docker-credential-helpers is embedded, but
> > it's not shown in the Built-Using field of pkg:docker.io.
> > 
> > This could be either a bug in docker.io or dh-golang.
> 
> 
> This is due to this dh-golang bug AFAIK: https://bugs.debian.org/9085
> 52

So is the conclusion there that docker.io is or is not actually
affected?

Regards,

Adam

Bug#934897: rdesktop: 1.8.6 crashes after login in Windows XP, rdp_recv(), unexpected stream overrun, 1.8.4 works

[Bernhard Übelacker]

Control: tags -1 + upstream


Dear Maintainer,
I tried to get some information to this issue.

The error is given within this backtrace [1].

This is also present in the upstream git 1.8.x branch.

A git bisect points to upstream commit 82fce18.
However that commit seems to just add some checks to
not overrun some receive buffers. So it looks like
that overrun is since a longer time included but
got not detected.

Therefore might it be, that Windows XP just sends
packets with this byte less?
Attached patch checks if the end of the receive buffer
is already reached and just if not "extracts" the
"userid", which is not used at all later (as far as I see).
A package with this patch seemed to work like intended,
but maybe upstream can confirm this patch.

Upstream master seems to have moved some logic
in 1a82d41, so the line in question looks like
requesting now two bytes as "pduSource".

There is upstream issue [2] that seems about this issue.
It got closed because of unreproducibility, I am going to
comment there and point to this information.

Kind regards,
Bernhard


[1]
(gdb) bt
#0  _rdp_protocol_error (file=0x4517d8 "rdp.c", line=140, func=0x452068 
<__func__.19872> "rdp_recv", message=0x450373 "unexpected stream overrun", 
s=0x474ba0 ) at rdp.c:1870
#1  0x004285f9 in rdp_recv (type=type@entry=0xb023 "") at rdp.c:140
#2  0x00428c72 in rdp_loop (deactivated=, 
ext_disc_reason=) at rdp.c:1777
#3  0x0042c157 in rdp_main_loop (deactivated=0xb128, 
ext_disc_reason=0xb12c) at rdp.c:1758
#4  0x004066a8 in main (argc=, argv=) at 
rdesktop.c:1191


[2] https://github.com/rdesktop/rdesktop/issues/342


# Stretch/oldstable i386 qemu VM 2019-08-16


apt update
apt dist-upgrade


apt install systemd-coredump xserver-xorg lightdm openbox xterm net-tools gdb 
fakeroot mc git rdesktop
# no rdesktop-dbgsym or rdesktop-dbg available ?
apt build-dep rdesktop



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


# ssh -p -R "127.0.0.1:3389:127.0.254.67:3389" benutzer@$LOCALIP
# RDP from a different VM


export DISPLAY=:0
rdesktop localhost




###



benutzer@debian:~$ rdesktop localhost
Autoselected keyboard map de
WARNING: Remote desktop does not support colour depth 24; falling back to 16
ERROR: rdp.c:140: rdp_recv(), unexpected stream overrun 03 00 00 1e 02 f0 
80 68 00 01 03 eb 70 10 08 00 ...hp...
0010 33 00 9a c6 db b8 94 e6 77 7e 04 00 16 00   3...w~

benutzer@debian:~$ dpkg -l | grep -i rdesktop
ii  rdesktop  1.8.6-2~deb9u1 i386 
RDP client for Windows NT/2000 Terminal Server and Windows Servers
benutzer@debian:~$ uname -a
Linux debian 4.9.0-9-686-pae #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) i686 
GNU/Linux



###



https://snapshot.debian.org/archive/debian/20190614T214545Z/pool/main/r/rdesktop/rdesktop_1.8.6-2_i386.deb

LANG=C dpkg -i /home/benutzer/rdesktop_1.8.6-2_i386.deb
 rdesktop depends on libc6 (>= 2.28); however:
  Version of libc6:i386 on system is 2.24-11+deb9u4.



###


https://snapshot.debian.org/archive/debian/20190610T152147Z/pool/main/r/rdesktop/rdesktop_1.8.6-1_i386.deb

root@debian:~# LANG=C dpkg -i /home/benutzer/rdesktop_1.8.6-1_i386.deb 
 rdesktop depends on libc6 (>= 2.28); however:
  Version of libc6:i386 on system is 2.24-11+deb9u4.



###



https://snapshot.debian.org/archive/debian-security/20190218T212704Z/pool/updates/main/r/rdesktop/rdesktop_1.8.4-1%7Edeb9u1_i386.deb

benutzer@debian:~$ rdesktop localhost
Autoselected keyboard map de
WARNING: Remote desktop does not support colour depth 24; falling back to 16
-> works


###


./parse.h:61:#define s_remaining(s) (size_t)((s)->end - (s)->p)
./parse.h:62:#define s_check_rem(s,n)   (((s)->p <= (s)->end) && ((size_t)n <= 
s_remaining(s)))
./parse.h:68:#define s_assert_r(s,n){ if (!s_check_rem(s, n)) 
rdp_protocol_error( "unexpected stream overrun", s); }
./parse.h:116:#define in_uint8s(s,n){ s_assert_r(s, n); (s)->p += 
n; }
./rdp.c:140:in_uint8s(rdp_s, 2);/* userid */

--> in_uint8s(rdp_s, 2);/* userid */
--> { s_assert_r(rdp_s, 2); (rdp_s)->p += 2; }
--> { { if (!s_check_rem(rdp_s, 2)) rdp_protocol_error( "unexpected stream 
overrun", rdp_s); }; (rdp_s)->p += 2; }
--> { { if (!(((rdp_s)->p <= (rdp_s)->end) && ((size_t)2 <= 
s_remaining(rdp_s rdp_protocol_error( "unexpected stream overrun", rdp_s); 
}; (rdp_s)->p += 2; }
--> { { if (!(((rdp_s)->p <= (rdp_s)->end) && ((size_t)2 <= 
(size_t)((rdp_s)->end - (rdp_s)->p rdp_protocol_error( "unexpected stream 
overrun", rdp_s); }; (rdp_s)->p += 2; }

--> {
  {
if (!(   ((rdp_s)->p <= (rdp_s)->end) &&  ((size_t)2 <= 
(size_t)((rdp_s)->end - (rdp_s)->p))   ))
  rdp_protocol_error( "unexpected stream overrun", rdp_s); 
  };
  (rdp_s)->p += 2;
}



cd /home/benutzer/source/rdesktop/
cp orig try1 -a
cd 

Bug#922170: nmu: Four packages for golang

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Tue, 2019-02-12 at 22:28 +0100, Moritz Muehlenhoff wrote:
> These packages need to be rebuilt to pick up the recent golang DSA:
> 
> nmu acmetool_0.0.58-5 . ANY . stretch . -m "rebuilt against current
> golang"
> nmu chasquid_0.01+git20161124.6479138-2 . ANY . stretch . -m "rebuilt
> against current golang"
> nmu heartbleeder_0.1.1-5 . ANY . stretch . -m "rebuilt against
> current golang"
> nmu mongo-tools_3.2.11-1 . ANY . stretch . -m "rebuilt against
> current golang"

As we previously discussed on IRC, the golang updates are stuck in
oldstable-new due to missing builds on the security side. The buildd
chroots for p-u don't pull in packages from the security archive, so
scheduling these will need to wait until we can get the packages into
opu.

Regards,

Adam

Bug#934930: python-novnc: depends on cruft package.

[peter green]

Package: python-novnc
Version: 1:1.0.0-1
Severity: serious
Tags: bullseye, sid

The python-novnc package depends on the python-oslo.config binary package which 
is no longer built by the corresponding source package.

As far as I can tell if you want to keep novnc around you will need to migrate 
novnc to use python3-novnc rather than python-novnc, then drop python-novnc.

Bug#934256: transition: ros-rosconsole

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Thu, Aug 08, 2019 at 09:14:28PM +0200, Jochen Sprickerhof wrote:
> I would like to transition to the new rosconsole ABI. Changes where
> minimal so I don't expect any problems and I'm maintaining all
> downstream packages anyway.

Feel free to go ahead with this too, once poco has transitioned (might be
tonight, if I've got the hints right...)

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#934929: Please consider updating to version 4

[Ole Streicher]

Package: src:plotly
Version: 3.6.1+dfsg1-2
Severity: wishlist

Hi Josue,

the last version of the "poliastro" package (0.13.0) depends on plotly
>=4.0. I would like to update that package ASAP; so could I ask you to
upload an updated version of plotly (4.1 is current version)?

Best regards

Ole

Bug#934926: [Pkg-zsh-devel] Bug#934926: overridding of default fpath causes uncessary complexity and pain for software providing zsh completions

[Daniel Shahaf]

Joey Hess wrote on Fri, 16 Aug 2019 18:35 +00:00:
> By default zsh loads completions from /usr/share/zsh/site-functions
> and while the name of that is perhaps not great, as it's not
> site-specific[1], it's a standard location. Debian has overridden this,
> so zsh does not look there, but instead in
> /usr/share/zsh/vendor-functions and /usr/share/zsh/vendor-completions
...
> The rationalle for the change in #620452 seems too weak to justify this
> added complexity. zsh could at least continue looking in the default
> location as well as whatever other locations Debian wants to patch in.

Let's see:

$ /usr/bin/zsh -fc 'print -rl $fpath' | head -3 # that's the Debian 
package, 5.7.1-1
/usr/local/share/zsh/site-functions
/usr/share/zsh/vendor-functions
/usr/share/zsh/vendor-completions
$ /srv/zsh/bin/zsh -fc 'print -rl $fpath' | head -3 # that's zsh compiled from 
upstream with --prefix=/srv/zsh
/usr/local/share/zsh/site-functions
/srv/zsh/share/zsh/site-functions
/srv/zsh/share/zsh/5.6.2-test-2/functions
$ 

So /usr/local/share/zsh/site-functions is still there for stuff installed
by the administrator, and vendor-functions and vendor-completions are
added in there for stuff provided by other Debian packages.  Are you
just asking to re-add ${PREFIX:-/usr}/share/zsh/site-functions there,
presumably between the first and second elements?

On the one hand, it _would_ be consistent with upstream, but on the
other hand, nobody should be putting anything in a site-functions
directory under /usr/share (admins should be putting their
customizations in /usr/local/share; other Debian packages should be
putting their stuff in vendor-functions or vendor-completions).  I don't
have a strong opinion on this, so I'll defer to others to make the call.

I suppose that if we add this, we should also add
${PREFIX}/share/zsh/${ZSH_VERSION}/functions, shouldn't we?

Cheers,

Daniel

Bug#903013: 1.15 is out and fixes more bracket warnings

[John Eikenberry]

If you get chance to update it to 1.14, you may want to consider going to 1.15
as it is out and only a small change.

Thanks.

-- 

John Eikenberry
[ j...@zhar.net - http://zhar.net ]

"Perfection is attained, not when no more can be added, but when no more
 can be removed." -- Antoine de Saint-Exupery

Bug#933829: win32-loader: Checksums need to be updated for new stable release, download fails to validate Release file.

[Paul Gevers]

clone 933829 -2
reassign -2 release.debian.org
retitle -2 buster-pu: package win32-loader/0.9.3+deb10u1
user release.debian@packages.debian.org
usertags pu
thanks

Let's hope I got that right.

On 16-08-2019 08:55, Didier 'OdyX' Raboud wrote:
> debian-boot@ / debian-release@: can I upload src:win32-loader in source only 
> with the following diff?

Mail like this tends to get processed late on our side. I cloned this
question as a bug, such that it shows up in the right place, hopefully.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#682342: Latest patch successfully tested

[Nishanth Aravamudan]

On 15.08.2019 [17:08:39 +0200], Cyril Brulebois wrote:
> Hi,
> 
> Nishanth Aravamudan  (2019-08-14):
> > We are able to reproduce this issue at will in Ubuntu Bionic's
> > installer (not identical to Debian's, but code-wise in this path the
> > same).  While quite a while after the last update from Philipp, we
> > tested the patch (netcfg_dhcp_domain.patch) after updating it to avoid
> > a compilation issue, we found it did fix the problem for us.
> > 
> > I am not sure if I can get Debian into our infrastructure to test
> > explicitly, but I will work on it; at the same time,  the code change
> > seems straightforward.
> 
> Thanks for your feedback. Care to share the fixed version? :)

D'oh! I'm sorry, I thought I did. The patch we tested was:

diff -Naur a/dhcp.c b/dhcp.c
--- a/dhcp.c2017-10-10 14:01:42.0 +
+++ b/dhcp.c2019-08-14 01:04:58.339325357 +
@@ -590,7 +590,7 @@
 preseed_hostname_from_fqdn(client, buf);
 }
 
-if (netcfg_get_hostname (client, "netcfg/get_hostname", 
hostname, 1)) {
+if (netcfg_get_hostname (client, "netcfg/get_hostname", 
hostname, !have_domain)) {
 /*
  * Going back to POLL wouldn't make much sense.
  * However, it does make sense to go to the retry
diff -Naur a/netcfg-common.c b/netcfg-common.c
--- a/netcfg-common.c   2017-10-10 14:04:08.0 +
+++ b/netcfg-common.c   2019-08-13 20:01:13.606510273 +
@@ -1060,14 +1060,24 @@
 continue;
 }
 
-if (accept_domain && (s = strchr(hostname, '.'))) {
-di_info("Detected we have an FQDN; splitting and setting domain");
-if (s[1] == '\0') { /* "somehostname." <- . should be ignored */
+if ((s = strchr(hostname, '.'))) {
+di_info("Detected an FQDN in hostname");
+if (s[1] == '\0') {
+/* "somehostname." <- . should be ignored */
 *s = '\0';
-} else { /* assume we have a valid domain name given */
-strncpy(domain, s + 1, MAXHOSTNAMELEN);
-debconf_set(client, "netcfg/get_domain", domain);
-have_domain = 1;
+di_info("Stripped trailing dot from hostname");
+} else {
+/* assume that the domain is valid and copy it if
+ * accept_domain is set; just use the hostname if
+ * it is unset
+ */
+if (accept_domain) {
+strncpy(domain, s + 1, MAXHOSTNAMELEN);
+   di_info("Setting domain to %s", domain);
+debconf_set(client, "netcfg/get_domain", domain);
+have_domain = 1;
+}
+/* strip the domain from the hostname */
 *s = '\0';
 }
 }

> I'm a little reluctant to blindly merging this patch (originally
> labeled “untested”) without a go from its author. Philipp, should
> I go ahead?

Totally understood! I just wanted to make sure to revive this issue, as
I'd also like to get it fixed in Ubuntu! Like I said, I will do my best
to test and reproduce the fix with stock Debian.

-Nish

Bug#934899: lintian tries and fail to unpack non ar archives

[Felix Lechner]

Hi,

According to 'git bisect' I introduced this bug when I provided a
defective implementation of `safe_qx` based on IO::Async in commit
39cd0295by, and unwittingly fixed it in commit 0d8ed5fa. The fix was
committed a few hours before the bug was filed. It was just-in-time
development!

The earlier version of 'safe_qx' raised an exception when 'ar'
returned with an error in `collection/ar-info` here :

https://salsa.debian.org/lintian/lintian/blob/master/collection/ar-info#L67

Now the error is ignored again, in a brittle way, by parsing the
output and adding to the list of archives presumably non-sensical
entries that are discarded later. My preference would be to apply the
merge request on top of it.

I am just not sure that the /^current ar archive/ regex is broad
enough. Any ideas?

Kind regards
Felix

Bug#926701: [tlbuild] Bug#926701: dvisvgm binary fails to link on GNU Hurd

[Hector Oron]

Hello,

  JFYI, a give back (package rebuild from failed state) has been triggered per 
IRC request:

Day changed to 16 Aug 2019
12:08 < gnu_srs1> (11:51:02 PM) srs: Can somebody gb texlive-bin 
2019.20190605.51237-2 on
  hurd-i386. It built fine locally.


signature.asc
Description: PGP signature

Bug#934927: transition: libgit2

[Jongmin Kim]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: block -1 by 931697
Control: block -1 by 931695
Control: block -1 by 931693

Hello release team!

I'd like to request a transition slot for libgit2.

libgit2 0.28 is in experimental and ready to start the transition from
0.27 in unstable.

I've rebuilt the relevant reverse-build-dependencies from unstable. The
following succeed and can be binNMU'd directly:

  calligra cargo fritzing gall geany-plugins gitg gnuastro horizon-eda
  libgit2-glib ktexteditor kup-backup rust-libgit2-sys

The following packages have fixed versions in experimental:

  * python-pygit2
  * ruby-rugged

The following fail, but probably just need to be bumped to the latest
upstream version:

  * golang-gopkg-libgit2-git2go.v27 (#931697)
  * libgit-raw-perl (#931695)

The following fail, and probably need more invasive changes such as
upgrading to the new API:

  * julia (#931693)

Thank you!

Ben file:

title = "libgit2";
is_affected = .depends ~ "libgit2-27" | .depends ~ "libgit2-28";
is_good = .depends ~ "libgit2-28";
is_bad = .depends ~ "libgit2-27";

Bug#934926: overridding of default fpath causes uncessary complexity and pain for software providing zsh completions

[Joey Hess]

Package: zsh
Version: 5.7.1-1
Severity: normal

By default zsh loads completions from /usr/share/zsh/site-functions
and while the name of that is perhaps not great, as it's not
site-specific[1], it's a standard location. Debian has overridden this,
so zsh does not look there, but instead in
/usr/share/zsh/vendor-functions and /usr/share/zsh/vendor-completions

This means that, as a developer of software that has zsh completions,
I first had to learn that the Debian location, which I had made my
software's Makefile install to, is non-standard (which took a while
since I use Debian everywhere). Then I had to grapple with the question
of how to deal with this inconsistency; should I try to probe if it's a
Debian system or what?

For me this involved looking at how several other Debian packages that
ship files in /usr/share/zsh/vendor-completions got them there. I
learned that few upstream software packages bother to probe for the
correct location, the one I found that does probe does so in a way that
would not work if building the software with zsh not installed. I
concluded a build system option and documentation was the sanest
approach for my software. The Debian package of my software will need
to use that in its debian/rules.

The rationalle for the change in #620452 seems too weak to justify this
added complexity. zsh could at least continue looking in the default
location as well as whatever other locations Debian wants to patch in.

-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   Architecture Description
+++-=-=--===
ii  borgbackup1.1.10-2  amd64deduplicating and compressing 
backup program
ii  curl  7.65.1-1  amd64command line tool for 
transferring data with URL syntax
ii  git-annex 7.20190129-3  amd64manage files with git, without 
checking their contents into git
ii  meson 0.51.1-1  all  high-productivity build system
ii  mpv   0.29.1-1  amd64video player based on 
MPlayer/mplayer2
ii  ninja-build   1.9.0-2   amd64small build system closest in 
spirit to Make
ii  pulseaudio12.2-4amd64PulseAudio sound server
ii  restic0.9.4+ds-2+b1 amd64backup program with multiple 
revisions, encryption and more
ii  systemd   241-7 amd64system and service manager
ii  systemd-container 241-7 amd64systemd container/nspawn tools
ii  torsocks  2.3.0-2   amd64use SOCKS-friendly 
applications with Tor
ii  udev  241-7 amd64/dev/ and hotplug management 
daemon
ii  vlc-bin   3.0.7.1-3 amd64binaries from VLC
ii  youtube-dl2019.07.02-1  all  downloader of videos from 
YouTube and other sites

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER, 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 zsh depends on:
ii  libc6   2.28-10
ii  libcap2 1:2.25-2
ii  libtinfo6   6.1+20190713-1
ii  zsh-common  5.7.1-1

Versions of packages zsh recommends:
ii  libc6 2.28-10
ii  libncursesw6  6.1+20190713-1
ii  libpcre3  2:8.39-12

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information

-- 
see shy jo

[1] per the FHS, the actually site-specific directory is
/usr/local/share/zsh/site-functions, which zsh also looks in


signature.asc
Description: PGP signature

Bug#928640: tiger: This makes the cronjob fail noisily every hour on my laptop

[Günter Frenz]

Hi,

Am Fri, 16 Aug 2019 09:46:51 -0700 kam folgendes bei mir an:

> On 2019-08-16 at 13:27:38, Günter Frenz wrote:
> > On Tue, 13 Aug 2019 23:13:38 -0700 Francois Marier
> >  wrote:  
> > >   /usr/sbin/tigercron: 127: /usr/lib/tiger/systems/default/config:
> > > expot: not found --ERROR-- [init001e] Don't have required command
> > > DIFF.  
> > 
> > on my system the proposed patch removes only the first line of the
> > hourly error-mail from cron. The script still complains about not
> > finding DIFF. /usr/bin/diff exists and is working as expected,
> > there is a second path to find it via the /bin symlink as
> > /bin/diff. I'm also running unstable on my system, just with German
> > localization.  
> 
> That second line can be fixed by adding a symlink in
> /usr/lib/tiger/systems/Linux/. See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930340.

thanks, seems to work.

Günter

-- 
---
Günter Frenz
Börschgasse 16a, D-51143 Köln
(h) gu...@guefz.de, gu...@freenet.de
(w) f...@gso-koeln.de
---




pgpA2ZEfni8tB.pgp
Description: Digitale Signatur von OpenPGP

Bug#928146: reported on freedesktop too

[Tuxicoman]

I have update to Linux 5.2 kernel from unstable and the problem is
solved !

I played several days without any crash.

I think it would be nice to backport the fix into Debian 10 standard
kernel as otherwise it not possible to play 3D games with AMD cards
without OS hang.

I'm available to test any kernel build for Debian 10 if necessary.

Or put a notice so that people know they should install the linux 5.2
backported kernel once available.

Bug#925343: a patch exists in upstream iptables git master

[Adel Belhouane]

Hello,

I made a patch to address this specific issue, it's currently in iptables'
git master (so probably for a future iptables 1.8.4). I guess it should 
probably be backported to any 1.8.x-y version.

https://git.netfilter.org/iptables/commit/?id=d76475ce1c30f6c3e3f3ca85964bdfc4425acb81

regards,
Adel Belhouane.

Bug#719692: Make run-parts useful for running hook scripts

[Clint Adams]

On Thu, Aug 15, 2019 at 09:24:46PM +, Dmitry Bogatov wrote:
> I want this feature too. Dear maintainer, are you interested? Will you
> accept patch?

Sure.  Would you read all of stdin into memory or would you
do something else?

Bug#934325: Separate tag-related bug reports from other functionality issues

[Chris Lamb]

Felix Lechner wrote:

> > I would thus be a -0 on adding more ways of classifiying bugs
> 
> No worries, please disregard the suggestion.
> 
> Here is another hypothetical: What if we separated each check into its
> own package (and let the 'lintian' package handle the overall
> infrastructure)? That way we could sort the bugs according to check,
> and someone working on one bug may easily see (and solve) related
> issues.

Perhaps I'm misunderstanding the suggestion here but I likely did not
explain the status quo ante correctly; we were attempting to use BTS
usertags separate the bugs for each check but this was not only a
bunch of busywork it was invariably always incorrect and did not provide
any real benefit for the most common usecases.

Splitting out each check into its own package would have exactly this
same effect that we moved away from, but would actually be more
restrictive. Just as one example, it would not cleanly allow a "null"
tag for potential checks that don't currently fit anywhere…

Further to this, it would unnecessarily really rather complicate the
packaging of Lintian itself in a technical sense (eg. lots of small
packages with a single Perl module needing to be upgraded in lockstep)
as well as "socially" (eg. requiring NEW visits for each new check
module).


Regards,

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

Bug#934805: lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service)

[Chris Lamb]

tags 934805 + patch
thanks

Hi Simon,

> - do not emit package-supports-alternative-init-but-no-init.d-script for
>   foo@.service at all, on the basis that the feature does not exist in
>   LSB init, so feature parity is not implementable

Indeed, we must have neglected these so-called "instanced" unit files
when implementing this.

I think a simple patch here would be:

diff --git a/checks/init.d.pm b/checks/init.d.pm
index 1850df31a..3f35c3c1a 100644
--- a/checks/init.d.pm
+++ b/checks/init.d.pm
@@ -513,7 +513,7 @@ sub check_missing_script {
 my ($info) = @_;
 for my $file ($info->sorted_index) {
 if (   $file =~ m,etc/sv/([^/]+)/run$,
-or $file =~ m,lib/systemd/system/(.*)\.service,) {
+or $file =~ m,lib/systemd/system/(.*)(?!@)\.service,) {
 
 my $service = $1;
 tag 
'package-supports-alternative-init-but-no-init.d-script',$file

Thoughts?


Regards,

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

Bug#920365: mariadb_config: improve cross compilation support

[Sergei Golubchik]

Hi, Helmut!

So, there's nothing for us (upstream) to do here?
pkg-config just works and you already have the script?

Regards,
Sergei

On Aug 16, Helmut Grohne wrote:
> Hi Sergei,
> 
> On Fri, Aug 16, 2019 at 05:41:14PM +0200, Sergei Golubchik wrote:
> > Ok. Two thoughts. First, libmariadb comes with mariadb.pc pkg-config
> > file. Does it have all you need to build? If not, we can, perhaps, add
> > missing info to it.
> 
> The pkg-config part works great for cross compilation. There is nothing
> you need to change here. It really just works. The problem is that not
> everything uses pkg-config. Some downstreams prefer using mariadb_config
> or more commonly mysql_config. Deprecating mysql_config and telling
> everyone to use pkg-config could be part of a long-term solution and
> I've done that to some packages (e.g. collectd, courier-authlib,
> lighttpd, rsyslog, sphinxsearch, ulogd2), but that's a lot of effort to
> get there.
> 
> One package that is particularly hard to convert to using pkg-config is
> mysql-connector-c++. See
> https://sources.debian.org/src/mysql-connector-c++/1.1.12-4/FindMySQL.cmake/.
> Please try converting this to pkg-config.
> 
> > Second, binary mariadb_config does nothing else but printing a set
> > of string. If there's no other choice, we could consider providing a
> > shell script with the same functionality too.
> 
> Exactly. The script I attached to the bug submission converts
> mariadb_config into a shell script that behaves exactly the same. You
> point it at mariadb_config and you get back a shell script that
> behaves exactly the same way. The major difference here is that the
> shell script will work for cross compiling downstreams that happen to
> not use pkg-config.
> 
> Helmut

Bug#934925: remove debian/patches/unbundle-sip.patch to provide wx.siplib ?

[Yaroslav Halchenko]

Source: wxpython4.0
Version: 4.0.6+dfsg-1
Severity: normal

Newer upstream version of fsleyes uses wx.siplib
(ref: https://github.com/pauldmccarthy/fsleyes/issues/29)
build of which is apparently  stripped away from the package in Debian:
https://salsa.debian.org/freewx-team/wxpython4.0/blob/master/debian/patches/unbundle-sip.patch
with the name suggeting that it would have its own package but I failed to find 
it:

> apt-cache search python wx sip
>

so I guess it never saw a life.

Unfortunately patch also doesn't provide any other details/hints on why
unbundling was needed and how was it handled.  So I wondered if just it could
be built/shipped along?

Thanks in advance

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

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

Bug#934912: printrun: depends on cruft package.

[Rock Storm]

On Fri, Aug 16, 2019 at 02:36:27PM +0100, peter green wrote:
> printrun depends on python-cairosvg which is no longer built by the cairosvg 
> source package.
>
> If you want your package to stay around you probably need to migrate to 
> python 3.

Hi, thanks for reporting. The new version of Printrun, which uses python
3, is already prepared. It will hopefully be uploaded soon.

Cheers,

--
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD

Bug#928640: tiger: This makes the cronjob fail noisily every hour on my laptop

[Francois Marier]

On 2019-08-16 at 13:27:38, Günter Frenz wrote:
> On Tue, 13 Aug 2019 23:13:38 -0700 Francois Marier
>  wrote:
> >   /usr/sbin/tigercron: 127: /usr/lib/tiger/systems/default/config:
> > expot: not found --ERROR-- [init001e] Don't have required command
> > DIFF.
> 
> on my system the proposed patch removes only the first line of the
> hourly error-mail from cron. The script still complains about not
> finding DIFF. /usr/bin/diff exists and is working as expected, there is
> a second path to find it via the /bin symlink as /bin/diff. I'm also
> running unstable on my system, just with German localization.

That second line can be fixed by adding a symlink in
/usr/lib/tiger/systems/Linux/. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930340.

Francois

-- 
https://fmarier.org/

Bug#934924: python-oslo.middleware: unbuildable in testing

[Esa Peuha]

Source: python-oslo.middleware
Version: 3.37.1-2

Currently python-oslo.middleware is unbuildable in testing because
three of its build-dependencies (python-hacking, python-oslotest,
python-stestr) have been removed. Please remove these and other
python 2 build-dependencies.

Bug#920365: mariadb_config: improve cross compilation support

[Helmut Grohne]

Hi Sergei,

On Fri, Aug 16, 2019 at 05:41:14PM +0200, Sergei Golubchik wrote:
> Ok. Two thoughts. First, libmariadb comes with mariadb.pc pkg-config
> file. Does it have all you need to build? If not, we can, perhaps, add
> missing info to it.

The pkg-config part works great for cross compilation. There is nothing
you need to change here. It really just works. The problem is that not
everything uses pkg-config. Some downstreams prefer using mariadb_config
or more commonly mysql_config. Deprecating mysql_config and telling
everyone to use pkg-config could be part of a long-term solution and
I've done that to some packages (e.g. collectd, courier-authlib,
lighttpd, rsyslog, sphinxsearch, ulogd2), but that's a lot of effort to
get there.

One package that is particularly hard to convert to using pkg-config is
mysql-connector-c++. See
https://sources.debian.org/src/mysql-connector-c++/1.1.12-4/FindMySQL.cmake/.
Please try converting this to pkg-config.

> Second, binary mariadb_config does nothing else but printing a set of
> string. If there's no other choice, we could consider providing a shell
> script with the same functionality too.

Exactly. The script I attached to the bug submission converts
mariadb_config into a shell script that behaves exactly the same. You
point it at mariadb_config and you get back a shell script that behaves
exactly the same way. The major difference here is that the shell script
will work for cross compiling downstreams that happen to not use
pkg-config.

Helmut

Bug#934923: clevis: [dracut-initqueue] cryptsetup: command not found

[David Heise]

Package: clevis
Version: 11-2
Severity: important

Dear Maintainer,

I am trying to use the tpm2 luks binding to non-interactively unlock a
partition during boot.

During `dracut-initqueue` on boot I get an error in `clevis-luks-askpass`
saying that
`cryptsetup` cannot be found on lines 52 and 67. This is despite `cryptsetup`
clearly
being placed in `usr/sbin/cryptsetup` during `dracut -f`.

```
$ sudo lsinitramfs /boot/initramfs-5.0.0-25-generic.img | grep cryptsetup
usr/lib/systemd/system-generators/systemd-cryptsetup-generator
usr/lib/systemd/system/cryptsetup.target
usr/lib/systemd/system/sysinit.target.wants/cryptsetup.target
usr/lib/systemd/systemd-cryptsetup
usr/lib/x86_64-linux-gnu/libcryptsetup.so
usr/lib/x86_64-linux-gnu/libcryptsetup.so.12
usr/lib/x86_64-linux-gnu/libcryptsetup.so.12.4.0
usr/sbin/cryptsetup
```

This script enumerates the steps to reproduce this bug on a clean Debian 10
installation, using clevis 11-1. I have Debian installed as VMWare Fusion 11.1
guest with
a virtualized TPM and booting UEFI.

```
sudo apt install -y dracut clevis clevis-dracut clevis-udisks2 clevis-luks
clevis-tpm2

# Before continuing, remove `clevis-decrypt-http`
# from `/usr/lib/dracut/modules.d/60clevis/module-setup.sh` line 39
sudo cryptsetup luksDump /dev/sda3
# Clear all key slots except 0
for ks in {1..7}
do
sudo clevis luks unbind -d /dev/sda3 -s $ks
done

sudo tpm2_pcrlist
sudo tpm2_takeownership -c
sudo tpm2_pcrlist
echo "TPM Decryption Success" | sudo clevis encrypt tpm2 '{}' > hi.jwe
sudo clevis decrypt < hi.jwe

sudo clevis luks bind -d /dev/sda3 tpm2 '{}'
sudo cryptsetup luksDump /dev/sda3
sudo dracut -fv --regenerate-all
```

After completing these steps, shut down and then boot.



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

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

Versions of packages clevis depends on:
ii  cracklib-runtime2.9.6-2
ii  curl7.64.0-4
ii  jose10-2
ii  libc6   2.28-10
ii  libjansson4 2.12-1
ii  libjose010-2
ii  libpwquality-tools  1.4.0-3
ii  libssl1.1   1.1.1c-1
ii  luksmeta9-3

Versions of packages clevis recommends:
ii  cryptsetup-bin  2:2.1.0-5

clevis suggests no packages.

-- no debconf information

Bug#934922: clevis: Reference to non-existant clevis-decrypt-http

[David Heise]

Package: clevis
Version: 11-2
Severity: grave
Tags: upstream
Justification: renders package unusable

`src/luks/systemd/dracut/module-setup.sh.in` refers to a component that does
not exist: `clevis-decrypt-http`

https://sources.debian.org/src/clevis/11-2/src/luks/systemd/dracut/module-
setup.sh.in/#L39

This issue has been fixed upstream, but is not reflected in a tagged release:
https://github.com/latchset/clevis/commit/1e344dbf6a60fcd2c60a4b8512be455e112d8398



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

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

Versions of packages clevis depends on:
ii  cracklib-runtime2.9.6-2
ii  curl7.64.0-4
ii  jose10-2
ii  libc6   2.28-10
ii  libjansson4 2.12-1
ii  libjose010-2
ii  libpwquality-tools  1.4.0-3
ii  libssl1.1   1.1.1c-1
ii  luksmeta9-3

Versions of packages clevis recommends:
ii  cryptsetup-bin  2:2.1.0-5

clevis suggests no packages.

-- no debconf information

Bug#934921: openssl: Wrong regular expression in /usr/bin/c_rehash

[Andreas Gryphius]

Package: openssl
Version: 1.1.1c-1
Severity: normal

Dear Maintainer,

the perl script /usr/bin/c_rehash contains a line (#123)

FILE: foreach $fname (grep {/\.(pem)|(crt)|(cer)|(crl)$/} @flist) {

where I think the regex grouping is wrong.
Obviously it is intended to find only files with the listed suffixes.
But it also finds files with "crt" or "cer" just anywhere within the 
filename. For example it would find the file "i_am_not_a_cert_file.pdf"


My suggestion for a propper regex would be

FILE: foreach $fname (grep {/\.(pem|crt|cer|crl)$/} @flist) {

Hope this will be fixed, because I changed it locally on my debian 
stretch machine quite a while ago and stumbled over this again when 
upgrading to buster (file /usr/bin/c_rehash got silently overwritten) .


Thanks, Andreas

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssl depends on:
ii  libc6  2.28-10
ii  libssl1.1  1.1.1c-1

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20190110

-- no debconf information
Report will be sent to Debian Bug Tracking System 

Bug#934753: dropbear-initramfs: please add an autopkgtest

[Guilhem Moulin]

On Fri, 16 Aug 2019 at 14:45:17 +0200, Guilhem Moulin wrote:
> On Wed, 14 Aug 2019 at 14:54:08 +0200, Johannes 'josch' Schauer wrote:
>> when I upgraded my Squeeze box to Jessie, remote unlocking via dropbear
>> in my initramfs stopped working. This is a remote host in a datacenter,
>> so I cannot directly investigate the issue.
> 
> Interesting, once you manage to boot I'd be interested to know the
> reason.

Oh wait, you upgraded from Squeeze to Jessie via Wheezy, right?
Directly upgrading from Squeeze to Jessie is not a supported upgrade
path.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#934920: lua-luaossl: FTBFS on x32 (sysctl unsupported on x32 kernel)

[Laurence Parry]

Package: lua-luaossl
Version: 20161208-3
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: x32

lua-luaoss fails to build from source on x32 because:

In file included from /usr/include/x86_64-linux-gnux32/sys/sysctl.h:63:0,
 from src/openssl.c:9089:
/usr/include/x86_64-linux-gnux32/bits/sysctl.h:19:3: error: #error
"sysctl system call is unsupported in x32 kernel"
 # error "sysctl system call is unsupported in x32 kernel"
https://buildd.debian.org/status/fetch.php?pkg=lua-luaossl=x32=20161214-1=1489921871=0

In config.h.guess I see:

#ifndef HAVE_SYS_SYSCTL_H
#define HAVE_SYS_SYSCTL_H ag_test_include(, (BSD || __GLIBC__))
#endif

Perhaps adding && !(__X86_64__ && __ILP32__) in there as well would fix it?
Or there might be a better solution, like pre-defining HAVE_RANDOM_UUID 0
(or HAVE_DECL_RANDOM_UUID in the current version)

There was an attempt to remove sysctl(), but it was restored here for
older kernels:
https://github.com/wahern/luaossl/commit/7d6202bfa85e8f0bf90590a9381757f15e296a33
Calls to sysctl remain in the current version .

---

Incidentally the distributed version is three years old and there have
been numerous releases since then (the tracker doesn't seem to see
this).
https://github.com/wahern/luaossl/releases

rel-20190612 supports OpenSSL 0.98; rel-20190731 may not, but still
supports jessie (and stretch):
https://github.com/wahern/luaossl/issues/169

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

Bug#934917: gnome-documents: Settings schema 'org.freedesktop.Tracker.Miner.Files' is not installed

[Simon McVittie]

Control: reassign -1 gnome-documents 3.31.92-1

This appears to be really gnome-documents crashing, not gjs. Because this
is an automated crash report, it is missing most of the information that
would be necessary to diagnose and fix the problem.

I'm guessing this is version 3.31.92-1 because you seem to have other
packages from Debian 10.

How can this crash be reproduced? Does it happen when you start
gnome-documents, or when you do some other action?

On Fri, 16 Aug 2019 at 15:15:14 +, giovanni.alberota...@gmail.com wrote:
>  ago 16 17:12:45 hostname gnome-documents[21777]: Settings schema 
> 'org.freedesktop.Tracker.Miner.Files' is not installed

This might indicate that gnome-documents or a library that it uses is
missing a dependency on tracker-extract, or it might indicate that
tracker-extract's GSettings schema should be in a different package.

smcv

Bug#934785: does not include lis.so driver

[Dominique Dumont]

On Friday, 16 August 2019 06:17:48 CEST Adam Di Carlo wrote:
> What's better, to just close this bug or should I upstream it?

There's already a ticket to track the libusb transition issue:
https://github.com/lcdproc/lcdproc/issues/13

I've tagged this BTS ticket as forwarded to this github issue, even if it's 
not exactly the same problem

Harald mentioned that lis driver does not require a dependency on libusb so 
the cleanup should be fairly simple. 

That said, this requires people willing to create a PR and having the HW to 
test. So far, nobody volunteered. Could you have a look there ?

All the best

Dod

Bug#934884: ITP: beanstalkc -- simple beanstalkd client library for Python

[Stéphane Blondon]

Le ven. 16 août 2019 à 10:01, Apollon Oikonomopoulos  a
écrit :

> * Package name: beanstalkc
>   Version : 0.4.0
>   Upstream Author : Andreas Bolka
> * URL : http://www.example.org/


In case of the previous infos comes from debian/control, the URL seems to
be a placeholder and so should be changed to the correct one.

Bug#931483: konsole: Konsole will not launch from mate-panel or from KDE Application Launcher.

[D.J.J. Ring, Jr.]

Maximiliano, konsole is again working!

Close this!

David

On Fri, Aug 16, 2019, 10:37 Maximiliano Curia 
wrote:

> Control: severity -1 important
> Control: tag -1 moreinfo unreproducible
>
> ¡Hola David!
>
> El 2019-07-05 a las 21:19 -0400, David J. Ring escribió:
> > Package: konsole
> > Version: 4:18.04.0-1
> > Severity: grave
> > Justification: renders package unusable
>
> > Dear Maintainer,
>
> > konsole will not launch from mate-panel shortcut or from KDE Application
> menu.
>
> > konsole WILL launch from mate-terminal and will subsequently open both
> new windows and new tabs.
>
> > konsole is unusable because of the problem, but I do not know if the
> problem is konsole or the KDE launcher or mate-panel.
>
> I'm not able to reproduce the issue as reported, can you check running
> konsole
> from a different terminal and see what's kind of errors are you getting
> (it
> might also be useful to check your ~/.xsession-errors)?
>
> Happy hacking,
> --
> A computer scientist is someone who, when told to "Go to Hell,"
> sees the "go to," rather than the destination, as harmful.
> Saludos /\/\ /\ >< `/
>

Bug#920365: mariadb_config: improve cross compilation support

[Sergei Golubchik]

Hi, Helmut!

On Aug 13, Helmut Grohne wrote:
> 
> On Sat, Jan 26, 2019 at 07:37:14PM +0100, Sergei Golubchik wrote:
> > I would say that when cross-compiling mariadb_config should be built
> > for the host architecture.
> 
> That is the status quo, but I guess you're confusing terms here.
> Please refer to man dpkg-architecture for what build/host/target mean.
> 
> > You'll get "Exec format error" if you run'll run it on the target
> > architecture, but that should not be a problem, as you will not need
> > to run mariadb_config on the target architecture. Because
> > mariadb_config is a helper tool to build applications, and you build
> > on the host architecture for the target architecture. You don't need
> > mariadb_config to use libmariadb.
> 
> I'm going to assume that whenever you write "target" you actually mean
> "host" and whenever you write "host" you actually mean "build".
> Otherwise this paragraph doesn't make any sense at all.

Yes, that's what I mean, thanks.
I didn't know debian has a defined terminology for this.

> I kinda agree that you'd want to have mariadb_config for the build
> architecture, but that's not what is currently happening nor is it
> reasonably achievable. Currently, mariadb_config is shipped with
> libmariadb-dev and you need libmariadb-dev for the host architecture
> (for linking it). Thus mariadb_config is a host architecture
> executable and cannot be run.

Ok. Two thoughts. First, libmariadb comes with mariadb.pc pkg-config
file. Does it have all you need to build? If not, we can, perhaps, add
missing info to it.

Second, binary mariadb_config does nothing else but printing a set of
string. If there's no other choice, we could consider providing a shell
script with the same functionality too.

Regards,
Sergei
VP of MariaDB Server Engineering
and secur...@mariadb.org

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

[Chris Lamb]

tags 830726 + patch
thanks

Chris Lamb wrote:

> CVE-2016-10894[0]:
> | xtrlock through 2.10 does not block multitouch events. Consequently,
> | an attacker at a locked screen can send input to (and thus control)
> | various programs such as Chromium via events such as pan scrolling,
> | "pinch and zoom" gestures, or even regular mouse clicks (by depressing
> | the touchpad once and then clicking with a different finger).

Patch attached that works for me on my Dell XPS 13:

  $ xinput --list | head -n4
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN25B5:00 04F3:25B5   id=12   [slave  pointer 
 (2)]
  ⎜   ↳ DELL07E6:00 06CB:76AF Touchpad  id=13   [slave  pointer 
 (2)]

(The second in this list is my multitouch touchscreen device.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
From ceb73c87915ca1e976847c470be4baff3086a507 Mon Sep 17 00:00:00 2001
From: Chris Lamb 
Date: Tue, 13 Aug 2019 13:32:11 -0700
Subject: [PATCH] Attempt to grab multitouch devices which are not intercepted
 via XGrabPointer. (Closes: #830726)

xtrlock did not block multitouch events so an attacker could still input
(and thus control) various programs such as Chromium, etc. via so-called
multitouch events such as pan scrolling, "pinch and zoom" or even being
able to provide regular mouse clicks by depressing the touchpad once and
then clicking with a secondary finger.

Thanks to Antoine Amarilli  for the report.

Signed-off-by: Chris Lamb 
---
 debian/control |  1 +
 debian/rules   |  4 ++--
 xtrlock.c  | 45 +
 3 files changed, 48 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 33582b1..19f88dd 100644
--- a/debian/control
+++ b/debian/control
@@ -6,6 +6,7 @@ Priority: optional
 Build-Depends:
  debhelper-compat (= 12),
  libx11-dev,
+ libxi-dev,
  x11proto-core-dev,
 Vcs-Git: https://salsa.debian.org/debian/xtrlock.git
 Vcs-Browser: https://salsa.debian.org/debian/xtrlock
diff --git a/debian/rules b/debian/rules
index 8c6893c..9b03511 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,7 @@ DPKG_EXPORT_BUILDFLAGS = 1
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 include /usr/share/dpkg/default.mk
 
-CFLAGS += -DSHADOW_PWD
+CFLAGS += -DSHADOW_PWD -DMULTITOUCH
 
 ifeq (,$(findstring ^$(DEB_VERSION_UPSTREAM),^$(shell cut -d'"' -f2 patchlevel.h)))
 $(error (patchlevel.h out of sync with Debian version))
@@ -14,7 +14,7 @@ endif
 	dh $@
 
 override_dh_auto_build:
-	$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) xtrlock.c -o xtrlock -lcrypt -lX11
+	$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) xtrlock.c -o xtrlock -lcrypt -lX11 -lXi
 
 override_dh_fixperms:
 	dh_fixperms -X/usr/bin/xtrlock
diff --git a/xtrlock.c b/xtrlock.c
index 6117c6f..389df08 100644
--- a/xtrlock.c
+++ b/xtrlock.c
@@ -41,6 +41,11 @@
 #include 
 #endif
 
+#ifdef MULTITOUCH
+#include 
+#include 
+#endif
+
 #include "lock.bitmap"
 #include "mask.bitmap"
 #include "patchlevel.h"
@@ -87,6 +92,12 @@ int main(int argc, char **argv){
 #endif
   struct timeval tv;
   int tvt, gs;
+#ifdef MULTITOUCH
+  XIEventMask evmask;
+  XIDeviceInfo *info;
+  int xi_major=2, xi_minor=2, xi_opcode, xi_error, xi_event, xi_ndevices;
+  unsigned char mask[XIMaskLen(XI_LASTEVENT)];
+#endif
 
   while (argc > 1) {
 if ((strcmp(argv[1], "-b") == 0)) {
@@ -132,7 +143,27 @@ int main(int argc, char **argv){
 	program_version);
 exit(1);
   }
+
+#ifdef MULTITOUCH
+  if (!XQueryExtension(display,INAME,_opcode,_event,_error)) {
+fprintf(stderr,"xtrlock (version %s): No X Input extension\n",
+	program_version);
+exit(1);
+  }
   
+  if (XIQueryVersion(display, _major, _minor) != Success||
+xi_major * 10 + xi_minor < 22) {
+fprintf(stderr,"xtrlock (version %s): Need XI 2.2\n",
+	program_version);
+exit(1);
+  }
+
+  evmask.mask = mask;
+  evmask.mask_len = sizeof(mask);
+  memset(mask, 0, sizeof(mask));
+  evmask.deviceid = XIAllMasterDevices;
+#endif
+
   attrib.override_redirect= True;
 
   if (blank) {
@@ -216,6 +247,20 @@ int main(int argc, char **argv){
 exit(1);
   }
 
+#ifdef MULTITOUCH
+  // (Optimistically) attempt to grab multitouch devices which are not
+  // intercepted via XGrabPointer
+  info = XIQueryDevice(display, XIAllDevices, _ndevices);
+  for (int i=0; i < xi_ndevices; i++) {
+XIDeviceInfo *dev = [i];
+for (int j=0; j < dev->num_classes; j++) {
+  if (dev->classes[j]->type == XITouchClass)
+XIGrabDevice(display, dev->deviceid, window, CurrentTime, cursor,
+ GrabModeAsync, GrabModeAsync, False, );
+}
+  }
+#endif
+
   if (fork_after) {
 pid_t pid = fork();
 if (pid < 0) {
-- 
2.23.0.rc1

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

[Chris Lamb]

severity 830726 grave
tags 830726 + security
retitle 830726 xtrlock: CVE-2016-10894: xtrlock does not block multitouch events
thanks

Hi,

The following vulnerability was published for xtrlock.

CVE-2016-10894[0]:
| xtrlock through 2.10 does not block multitouch events. Consequently,
| an attacker at a locked screen can send input to (and thus control)
| various programs such as Chromium via events such as pan scrolling,
| "pinch and zoom" gestures, or even regular mouse clicks (by depressing
| the touchpad once and then clicking with a different finger).

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-10894
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10894


Regards,

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

Bug#934919: omnidb: please make the build reproducible

[Chris Lamb]

Source: omnidb
Version: 2.16.0+ds-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: filesystem
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed
that omnidb could not be built reproducibly.

This is because it generated the "Depends" line via substvars by
iterating over the filesystem which, without an explicit sort, returns
the results in a nondeterministic order:

│ │ │ │  Installed-Size: 30226
│ │ │ │ -Depends: fonts-glewlwyd, fonts-roboto-unhinted, […]
│ │ │ │ +Depends: fonts-roboto-unhinted, fonts-glewlwyd, […]
│ │ │ │  Section: database

Patch attached that enforces an order via sort(1).

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2019-08-16 08:05:20.841896177 -0700
--- b/debian/rules  2019-08-16 08:10:36.883367468 -0700
@@ -13,7 +13,7 @@
 override_dh_install-indep:
dh_install -i
echo "fonts:Depends=" >> debian/omnidb-common.substvars
-   find debian -name '*.eot' -or -name '*.svg' -or -name '*.ttf' -or -name 
'*.woff*' | \
+   find debian -name '*.eot' -or -name '*.svg' -or -name '*.ttf' -or -name 
'*.woff*' | LC_ALL=C sort | \
while read path; do \
file="$${path##*/}" ; \
dpkg -S "*/$$file" | grep '^fonts' | sort | head -1 | 
while read pkg pkgpath; do \
@@ -23,7 +23,7 @@
done \
done
echo "js:Depends=" >> debian/omnidb-common.substvars
-   find debian -regextype egrep -regex '.*/(jq|excanvas).*\.(css|js)$$' | \
+   find debian -regextype egrep -regex '.*/(jq|excanvas).*\.(css|js)$$' | 
LC_ALL=C sort | \
while read path; do \
file="$$(echo $${path##*/} | sed -e 's/-[0-9.]*\././')" 
; \
dpkg -S "*/$$file" | grep '^libjs' | sort | head -1 | 
while read pkg pkgpath; do \

Bug#934918: python-etcd3gw: please make the build reproducible

[Chris Lamb]

Source: python-etcd3gw
Version: 0.2.1-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed
that python-etcd3gw could not be built reproducibly.

This is because one of the function signatures used a non-
deterministic / random default value that was rendered by the
documentation system at build time and thus varied each time.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/0001_reproducible-build.patch  1969-12-31 
16:00:00.0 -0800
--- b/debian/patches/0001_reproducible-build.patch  2019-08-16 
08:12:09.271187454 -0700
@@ -0,0 +1,23 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2019-08-16
+
+--- python-etcd3gw-0.2.1.orig/etcd3gw/client.py
 python-etcd3gw-0.2.1/etcd3gw/client.py
+@@ -115,13 +115,15 @@ class Etcd3Client(object):
+json={"TTL": ttl, "ID": 0})
+ return Lease(int(result['ID']), client=self)
+ 
+-def lock(self, id=str(uuid.uuid4()), ttl=DEFAULT_TIMEOUT):
++def lock(self, id=None, ttl=DEFAULT_TIMEOUT):
+ """Create a Lock object given an ID and timeout
+ 
+ :param id: ID for the lock, creates a new uuid if not provided
+ :param ttl: timeout
+ :return: Lock object
+ """
++if id is None:
++id = str(uuid.uuid4())
+ return Lock(id, ttl=ttl, client=self)
+ 
+ def create(self, key, value):
--- a/debian/patches/series 1969-12-31 16:00:00.0 -0800
--- b/debian/patches/series 2019-08-16 08:12:07.966645878 -0700
@@ -0,0 +1 @@
+0001_reproducible-build.patch

Bug#924573: lcov: Update to latest version 1.14

[Tim Rühsen]

On Thu, 14 Mar 2019 13:45:50 + Marco F  wrote:
> Package: lcov
> Version: 1.13-4
> Severity: normal
> 
> Dear Maintainer,
> 
> could you please update the package to the latest version?
> It includes some bug fixes and other improvements.

Please also include support for gcc 9:
https://github.com/linux-test-project/lcov/commit/75fbae1cfc5027f818a0bb865bf6f96fab3202da

The upstream issue is at
https://github.com/linux-test-project/lcov/issues/58

Thank you !

Regards, Tim



signature.asc
Description: OpenPGP digital signature

Bug#933311: bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: _ZN7leveldb4port5Mutex6UnlockEv

[Antoine Amarilli]

Hi,

I am also affected by this. bitcoin-qt just fails to start with this
error, so it cannot be used at all.

Regards,

-- 
Antoine Amarilli

Bug#858071: bt from using gdb

[Michael Rasmussen]

Hi Stephen,

See attached file for backtrace from gdb.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
Alas, how love can trifle with itself!
-- William Shakespeare, "The Two Gentlemen of Verona"
using: gdb python
run /usr/bin/solaar -d

Thread 1 "python" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) thread apply all bt

Thread 6 (Thread 0x709c7700 (LWP 14876)):
#0  0x77ce7037 in __GI___select (nfds=16, readfds=0x709ba0b0, 
writefds=0x709ba030, exceptfds=0x709b9fb0, timeout=0x709b9fa0) at 
../sysdeps/unix/sysv/linux/select.c:41
#1  0x55714a08 in select_select (self=, args=) at ../Modules/selectmodule.c:267
#2  0x55643baa in call_function (oparg=, 
pp_stack=0x709c6248) at ../Python/ceval.c:4376
#3  0x55643baa in PyEval_EvalFrameEx (f=, 
throwflag=) at ../Python/ceval.c:3013
#4  0x55641656 in PyEval_EvalCodeEx (co=, 
globals=, locals=, args=, 
argcount=, kws=, kwcount=, 
defs=, defcount=, closure=) at 
../Python/ceval.c:3608
#5  0x5564944e in fast_function (nk=0, na=3, n=, 
pp_stack=0x709c6418, func=) at ../Python/ceval.c:4471
#6  0x5564944e in call_function (oparg=, 
pp_stack=0x709c6418) at ../Python/ceval.c:4396
#7  0x5564944e in PyEval_EvalFrameEx (f=, 
throwflag=) at ../Python/ceval.c:3013
#8  0x55641656 in PyEval_EvalCodeEx (co=, 
globals=, locals=, args=, 
argcount=--Type  for more, q to quit, c to continue without 
paging--c
, kws=, kwcount=, defs=, 
defcount=, closure=) at ../Python/ceval.c:3608
#9  0x556499d6 in fast_function (nk=0, na=2, n=, 
pp_stack=0x709c65e8, func=) at ../Python/ceval.c:4471
#10 0x556499d6 in call_function (oparg=, 
pp_stack=0x709c65e8) at ../Python/ceval.c:4396
#11 0x556499d6 in PyEval_EvalFrameEx (f=, 
throwflag=) at ../Python/ceval.c:3013
#12 0x55641656 in PyEval_EvalCodeEx (co=, 
globals=, locals=, args=, 
argcount=, kws=, kwcount=, 
defs=, defcount=, closure=) at 
../Python/ceval.c:3608
#13 0x5564944e in fast_function (nk=0, na=2, n=, 
pp_stack=0x709c67b8, func=) at ../Python/ceval.c:4471
#14 0x5564944e in call_function (oparg=, 
pp_stack=0x709c67b8) at ../Python/ceval.c:4396
#15 0x5564944e in PyEval_EvalFrameEx (f=, 
throwflag=) at ../Python/ceval.c:3013
#16 0x55641656 in PyEval_EvalCodeEx (co=, 
globals=, locals=, args=, 
argcount=, kws=, kwcount=, 
defs=, defcount=, closure=) at 
../Python/ceval.c:3608
#17 0x556499d6 in fast_function (nk=0, na=1, n=, 
pp_stack=0x709c6988, func=) at ../Python/ceval.c:4471
#18 0x556499d6 in call_function (oparg=, 
pp_stack=0x709c6988) at ../Python/ceval.c:4396
#19 0x556499d6 in PyEval_EvalFrameEx (f=, 
throwflag=) at ../Python/ceval.c:3013
#20 0x556491b8 in fast_function (nk=, na=, n=1, pp_stack=0x709c6a98, func=) at 
../Python/ceval.c:4461
#21 0x556491b8 in call_function (oparg=, 
pp_stack=0x709c6a98) at ../Python/ceval.c:4396
#22 0x556491b8 in PyEval_EvalFrameEx (f=, 
throwflag=) at ../Python/ceval.c:3013
#23 0x55641656 in PyEval_EvalCodeEx (co=, 
globals=, locals=, args=, 
argcount=, kws=, kwcount=, 
defs=, defcount=, closure=) at 
../Python/ceval.c:3608
#24 0x5565e2f5 in function_call (func=func@entry=, 
arg=arg@entry=(, maxsize=16, 
all_tasks_done=<_Condition(_Verbose__verbose=False, 
_Condition__lock=, acquire=, 
_Condition__waiters=[], release=) at remote 0x717fecd0>, mutex=, not_full=<_Condition(_Verbose__verbose=False, 
_Condition__lock=, acquire=, 
_Condition__waiters=[], release=) at remote 0x717fea10>, 
not_empty=<_Condition(_Verbose__verbose=False, _Condition__lock=, acquire=) at ../Objects/funcobject.c:523
#25 0x55676b14 in PyObject_Call (kw=, 
arg=(, maxsize=16, 
all_tasks_done=<_Condition(_Verbose__verbose=False, 
_Condition__lock=, acquire=, 
_Condition__waiters=[], release=) at remote 0x717fecd0>, mutex=, not_full=<_Condition(_Verbose__verbose=False, 
_Condition__lock=, acquire=, 
_Condition__waiters=[], release=) at remote 0x717fea10>, 
not_empty=<_Condition(_Verbose__verbose=False, _Condition__lock=, acquire=) at 
../Objects/abstract.c:2544
#26 0x55676b14 in instancemethod_call (func=, func@entry=, 
arg=(, maxsize=16, 
all_tasks_done=<_Condition(_Verbose__verbose=False, 
_Condition__lock=, acquire=, 
_Condition__waiters=[], release=) at remote 0x717fecd0>, mutex=, not_full=<_Condition(_Verbose__verbose=False, 
_Condition__lock=, acquire=, 

Bug#934916: libss7: FTBFS on x32 (time_t sprintf format mismatch)

[Laurence Parry]

Package: libss7-2.0
Version: 2.0.0-2
Tags: ftbfs
Usertags: x32
Priority: minor

libss7 2.0 fails to build on x32 because it assumes time_t is of type
long int when it can be long long int (64-bit, on a system with a
32-bit long).

gcc -g -O2 -fdebug-prefix-map=/<>=.
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g
-Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -fPIC -O2  -MD
-MT ss7.o -MF .ss7.o.d -MP -c -o ss7.o ss7.c
ss7.c: In function 'ss7_show_linkset':
ss7.c:654:21: error: format '%li' expects argument of type 'long int',
but argument 3 has type 'long long int' [-Werror=format=]
  sprintf(p, "(%lis)%c",
ss7->ss7_sched[ss7->links[i]->mtp3_timer[x]].when.tv_sec - time(NULL),
   ~~^
~
   %lli

A patch for this might go along the lines of:

+#if defined __x86_64__ && defined __ILP32__
+  sprintf(p, "(%llis)%c",
ss7->ss7_sched[ss7->links[i]->mtp3_timer[x]].when.tv_sec - time(NULL),
+#else
  sprintf(p, "(%lis)%c",
ss7->ss7_sched[ss7->links[i]->mtp3_timer[x]].when.tv_sec - time(NULL),
+#endif

or it might be more appropriate to use strftime(), or cast to long
long int unconditionally (though this pulls it in where not needed on
x86 32-bit).

Minor priority because it's only mentioned as an binary dependency for
asterisk-dahdi (which currently compiles without it), and there it
only:

  * Depend on libss7 and newer libpri (1.4.7) for latest chan_dahdi abilities.

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