Bug#923034: FreeRADIUS status

[Niels Thykier]

Alan DeKok:
>   We've been looking for a new Debian maintainer for a while.
> 
>   What, exactly, is in "bad shape" about this package?  If there are issues, 
> we can work towards fixing them.
> 
>   The software is widely used by many tens of thousands of sites.  I hope 
> it's not going to be removed from Debian.
> 
>   I'll note that Debian also packages "livingston-radius", which hasn't had 
> any source changes in 20 years.  There's no mailing list, no support, and it 
> doesn't implement any of the modern RADIUS standards.
> 
>   Including that package does a disservice to people who install it, and then 
> realize it's next to useless.
> 

Hi,

I am CC'ing Michael on your reply as I am not sure he is subscribed to
the bug (it is not the default for Debian bugs) and he is probably
better at answering this given his prior work with the package.

Thanks,
~Niels

Bug#923103: flang-7: flang hangs building pnetcdf.f90

[Alastair McKinstry]

Package: flang-7
Version: 20181226-2
Severity: normal

Dear Maintainer,

With OpenMPI built with flang, pnetcdf builds hang:

alastair@debian:~/deb-packages/pnetcdf/pnetcdf-1.11.0/build-static/src/binding/f90$
 /usr/bin/mpif90.openmpi --verbose -O0 -I. -I../../../../src/binding/f90   -c 
pnetcdf.f90 -o pnetcdf.o
clang version 7.0.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.4.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
 "/usr/bin/flang1" pnetcdf.f90 -opt 0 -terse 1 -inform warn -nohpf -nostatic 
-inform warn -x 19 0x40 -quad -x 68 0x1 -x 59 4 -x 15 2 -x 49 0x44 -x 
51 0x20 -x 57 0x4c -x 58 0x1 -x 124 0x1000 -tp px -x 57 0xfb -x 58 
0x78031040 -x 47 0x08 -x 48 4608 -x 49 0x100 -stdinc 
/usr/bin/../include:/usr/local/include:/usr/lib/clang/7.0.1/include:/usr/include/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/fortran/flang-7:/include:/usr/include
 -def unix -def __unix -def __unix__ -def linux -def __linux -def __linux__ 
-def __NO_MATH_INLINES -def __LP64__ -def __LONG_MAX__=9223372036854775807L 
-def __SIZE_TYPE__=unsigned long int -def __PTRDIFF_TYPE__=long int -def 
__x86_64 -def __x86_64__ -def __amd_64__amd64__ -def __k8 -def __k8__ -def 
__THROW= -def __extension__= -def __PGLLVM__ -freeform -idir . -idir 
../../../../src/binding/f90 -idir /usr/lib/x86_64-linux-gnu/openmpi/include 
-idir /usr/lib/x86_64-linux-gnu/openmpi/lib -vect 48 -x 54 1 -x 70 0x4000 
-y 163 0xc000 -x 189 0x10 -stbfile pnetcdf-e9f8a6.stb -modexport 
pnetcdf-e9f8a6.cmod -modindex pnetcdf-e9f8a6.cmdx -output pnetcdf-e9f8a6.ilm
^C




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

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

Versions of packages flang-7 depends on:
ii  libc6 2.28-7
ii  libflang-dev  20181226-2
ii  libflang0d-7  20181226-2
ii  libgcc1   1:8.2.0-21
ii  libllvm7  1:7.0.1-6
ii  libstdc++68.2.0-21

flang-7 recommends no packages.

flang-7 suggests no packages.

-- no debconf information

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

[Sebastien CHAVAUX]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I would like to adopt the xsoldier package, considering that it does not 
change much or little and requires little in consequence.

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

* Package name: xsoldier
  Version : 1:1.8-6
  Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstream's web site]
* License : [fill in]
  Section : games

It builds those binary packages:

  xsoldier - shoot 'em up game with the "not shooting" bonus

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/x/xsoldier/xsoldier_1.8-6.dsc


Changes since the last upload:


xsoldier (1:1.8-6) unstable; urgency=medium

  * New maintainer. (Closes: #738879)

 -- Sebastien CHAVAUX   Sun, 24 Feb 2019 07:41:00 +0100

Bug#923101: xcape FTCBFS: upstream Makefile hard codes build architecture pkg-config

[Helmut Grohne]

Source: xcape
Version: 1.2-2
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

xcape fails to cross build from source, because the upstream Makefile
hard codes the build architecture pkg-config. After making it
substitutable, dh_auto_build substitutes it and xcape cross builds
successfully. Please consider applying the attached patch.

Helmut
--- xcape-1.2.orig/Makefile
+++ xcape-1.2/Makefile
@@ -4,9 +4,10 @@
 
 TARGET := xcape
 
+PKG_CONFIG ?= pkg-config
 CFLAGS += -Wall
-CFLAGS += `pkg-config --cflags xtst x11`
-LDFLAGS += `pkg-config --libs xtst x11`
+CFLAGS += `$(PKG_CONFIG) --cflags xtst x11`
+LDFLAGS += `$(PKG_CONFIG) --libs xtst x11`
 LDFLAGS += -pthread
 
 all: $(TARGET)

Bug#923100: dares FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: dares
Version: 0.6.5+repack-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

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

Helmut
diff --minimal -Nru dares-0.6.5+repack/debian/changelog 
dares-0.6.5+repack/debian/changelog
--- dares-0.6.5+repack/debian/changelog 2018-05-23 07:51:16.0 +0200
+++ dares-0.6.5+repack/debian/changelog 2019-02-24 08:29:28.0 +0100
@@ -1,3 +1,10 @@
+dares (0.6.5+repack-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 08:29:28 +0100
+
 dares (0.6.5+repack-1) unstable; urgency=medium
 
   * d/control: Move Vcs-* to salsa.d.o.
diff --minimal -Nru dares-0.6.5+repack/debian/rules 
dares-0.6.5+repack/debian/rules
--- dares-0.6.5+repack/debian/rules 2018-05-23 07:51:16.0 +0200
+++ dares-0.6.5+repack/debian/rules 2019-02-24 08:29:27.0 +0100
@@ -4,7 +4,7 @@
dh $@
 
 override_dh_auto_build:
-   $(MAKE) ncurses
+   dh_auto_build -- ncurses
 
 override_dh_auto_clean:
-[ ! -f frontend/ncurses/Makefile ] || $(MAKE) -C frontend/ncurses clean

Bug#923099: luakit FTCBFS: multiple reasons

[Helmut Grohne]

Source: luakit
Version: 2017.08.10-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

luakit fails to cross build from source. The immediate failure is
failing make clean. The Makefile checks dependencies using (the wrong)
pkg-config during each invocation. Making pkg-config substitutable is
the first step and providing the PKG_CONFIG variable for all targets
(not just during dh_auto_build) is the second. Then, documentation
generation fails as it fails to find (a native) lua-filesystem. The
build dependency needs to be annotated with :native. The attached patch
makes luakit cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru luakit-2017.08.10/debian/changelog 
luakit-2017.08.10/debian/changelog
--- luakit-2017.08.10/debian/changelog  2019-01-06 11:25:03.0 +0100
+++ luakit-2017.08.10/debian/changelog  2019-02-24 08:01:48.0 +0100
@@ -1,3 +1,13 @@
+luakit (2017.08.10-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ cross.patch: Make pkg-config substitutable.
++ Export PKG_CONFIG for all targets.
++ Build-Depends: require a native lua-filesystem for docs.
+
+ -- Helmut Grohne   Sun, 24 Feb 2019 08:01:48 +0100
+
 luakit (2017.08.10-1) unstable; urgency=medium
 
   * New upstream version 2017.08.10
diff --minimal -Nru luakit-2017.08.10/debian/control 
luakit-2017.08.10/debian/control
--- luakit-2017.08.10/debian/control2019-01-06 11:25:03.0 +0100
+++ luakit-2017.08.10/debian/control2019-02-24 08:01:48.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Markus Demleitner 
 Standards-Version: 4.3.0
-Build-Depends: debhelper (>=9), help2man, libluajit-5.1-dev, libsqlite3-dev, 
libunique-dev, libgtk-3-dev, libwebkit2gtk-4.0-dev, luajit, lua-filesystem
+Build-Depends: debhelper (>=9), help2man, libluajit-5.1-dev, libsqlite3-dev, 
libunique-dev, libgtk-3-dev, libwebkit2gtk-4.0-dev, luajit, 
lua-filesystem:native
 Homepage: http://luakit.org/
 Vcs-Git: https://salsa.debian.org/debian/luakit.git
 Vcs-Browser: https://salsa.debian.org/debian/luakit
diff --minimal -Nru luakit-2017.08.10/debian/patches/cross.patch 
luakit-2017.08.10/debian/patches/cross.patch
--- luakit-2017.08.10/debian/patches/cross.patch1970-01-01 
01:00:00.0 +0100
+++ luakit-2017.08.10/debian/patches/cross.patch2019-02-24 
08:01:45.0 +0100
@@ -0,0 +1,38 @@
+--- luakit-2017.08.10.orig/config.mk
 luakit-2017.08.10/config.mk
+@@ -5,6 +5,7 @@
+ CFLAGS += -std=gnu99 -ggdb -W -Wall -Wextra -Werror=unused-result
+ LDFLAGS+=
+ CPPFLAGS   +=
++PKG_CONFIG ?= pkg-config
+ 
+ # Get current luakit version.
+ VERSION?= $(shell ./build-utils/getversion.sh)
+@@ -64,7 +65,7 @@
+ # Search for Lua package name if not forced by user.
+ ifeq ($(LUA_PKG_NAME),)
+ LUA_PKG_NAME = $(shell sh -c '(for name in $(LUA_PKG_NAMES); do \
+- pkg-config --exists $$name && echo $$name; done) | head -n 1')
++ $(PKG_CONFIG) --exists $$name && echo $$name; done) | head -n 1')
+ endif
+ 
+ # === Lua binary name detection =
+@@ -102,15 +103,15 @@
+ endif
+ 
+ # Check user has correct packages installed (and found by pkg-config).
+-PKGS_OK := $(shell pkg-config --print-errors --exists $(PKGS) && echo 1)
++PKGS_OK := $(shell $(PKG_CONFIG) --print-errors --exists $(PKGS) && echo 1)
+ ifneq ($(PKGS_OK),1)
+ $(error Cannot find required package(s\) to build luakit. Please \
+ check you have the above packages installed and try again)
+ endif
+ 
+ # Add pkg-config options to compile flags.
+-CFLAGS  += $(shell pkg-config --cflags $(PKGS))
++CFLAGS  += $(shell $(PKG_CONFIG) --cflags $(PKGS))
+ CFLAGS  += -I./
+ 
+ # Add pkg-config options to linker flags.
+-LDFLAGS += $(shell pkg-config --libs $(PKGS))
++LDFLAGS += $(shell $(PKG_CONFIG) --libs $(PKGS))
diff --minimal -Nru luakit-2017.08.10/debian/patches/series 
luakit-2017.08.10/debian/patches/series
--- luakit-2017.08.10/debian/patches/series 2019-01-06 11:25:03.0 
+0100
+++ luakit-2017.08.10/debian/patches/series 2019-02-24 08:01:20.0 
+0100
@@ -1,2 +1,3 @@
 0001-lintian-placating-makefile-changes.patch
 0002-Fix-a-few-defaults.patch
+cross.patch
diff --minimal -Nru luakit-2017.08.10/debian/rules 
luakit-2017.08.10/debian/rules
--- luakit-2017.08.10/debian/rules  2019-01-06 11:25:03.0 +0100
+++ luakit-2017.08.10/debian/rules  2019-02-24 08:01:48.0 +0100
@@ -1,4 +1,6 @@
 #!/usr/bin/make -f
+include /usr/share/dpkg/buildtools.mk
+export PKG_CONFIG ?= pkg-config
 export DH_VERBOSE = 1
 export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic -fstack-protector-strong 
-Wformat -Werror=format-security
 export DEB_CPPFLAGS_MAINT_APPEND  = -Wdate-time -D_FORTIFY_SOURCE=2

Bug#923098: libklibc-dev: missing clock_gettime

[Thorsten Glaser]

Package: libklibc-dev
Version: 2.0.6-1
Severity: wishlist
Tags: upstream

Hi,

clock_gettime(2) support (with at least CLOCK_REALTIME (although I guess
gettimeofday(2) is the same just with less precision) and CLOCK_MONOTONIC)
would be nice for something I’m working on.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libklibc-dev depends on:
ii  libklibc2.0.6-1
ii  linux-libc-dev  4.19.20-1

libklibc-dev recommends no packages.

libklibc-dev suggests no packages.

-- no debconf information

Bug#923082: can't disable systemd-resolved

[Martin Pitt]

Control: tag -1 moreinfo

Hello Toni,

Toni [2019-02-23 23:05 +]:
> I can't disable systemd-resolved, which prevents me from running my own
> DNS setup:

systemd-resolved.service is not enabled by default in Debian. If you enabled
it, what prevents you from disabling it again? (systemctl disable
systemd-resolved).

> # systemctl disable --now systemd-resolved.service
> # lsof -i udp@0.0.0.0:53  
> COMMAND   PID   USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
> systemd 1   root  177u  IPv4   10583  0t0  UDP localhost:domain 
> dnsmasq 13861 nobody5u  IPv4 5159825  0t0  UDP 192.168.122.1:domain 
> #
> 
> Since it runs inside PID 1, I cannot even kill it.

resolved doesn't run in pid 1 (that would be a really bad architecture!). This
just means that pid 1 connected to localhost's name server to resolve a name
(i. e. a DNS client). A better command to find out which processes are
*listening* on UDP ports is "ss -ulpen", or for port 53 specifically,
"ss -ulpen 'sport = 53'".

Martin

Bug#923097: transition to Breezy

[Jelmer Vernooij]

Source: bzr
Severity: important

After buster has been released, I'm planning to replace Bazaar in the archive
with Breezy (www.breezy-vcs.org).

Breezy is a friendly fork of Bazaar. Unlike Bazaar it is actively maintained,
and available for Python 3. Breezy's command line is backwards compatible with
Bazaar. Its API is not compatible, but it should be fairly easy to port plugins
and other 3rd party users of the API to Breezy.

Breezy also bundles a number of plugins that were external in Bazaar and
packaged separately. Relevant for Debian: grep, stats, email, fastimport, git
and part of bzrtools.

I'm filing this bug to track the transition work.

Bugs that would be resolved by a migration to Breezy:

control: block 883146 by -1
control: block 531128 by -1
control: block 612987 by -1
control: block 763116 by -1
control: block 741335 by -1
control: block 520974 by -1
control: block 563741 by -1



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

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

Bug#922305: latexindent: please add dependency with liblog-log4perl-perl

[Norbert Preining]

I have added the recommends to the git repo on github.
Updated packages will soon be available at
https://www.preining.info/debian/tex
(deb and deb-src source, see https://www.preining.info/debian/)

Norbert

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

Bug#922305: latexindent: please add dependency with liblog-log4perl-perl

[Norbert Preining]

On Thu, 21 Feb 2019, Yukiharu YABUKI wrote:
> It seems for me that your proposal is good for apt users. But I and 
> some people would like to use aptitude. Yes, I knew that Debian project

I also use aptitude, and it *does* install recommends AFAIR...

Norbert

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

Bug#921030: Fails to import the ansible module since its migration to Python 3

[Samuel Henrique]

I'm working on this: https://salsa.debian.org/debian/ansible-lint

I think i'm close to an upload now, there's only some problems with .js
sources.

Anyone please feel free to help.

-- 
Samuel Henrique 

Bug#923096: consider porting to Breezy

[Jelmer Vernooij]

Package: git-remote-bzr
Severity: normal

Dear Maintainer,

bzr has long been dormant upstream. It will be replaced in
Debian (in buster+1) with Breezy (www.breezy-vcs.org), which is actively 
maintained and
has a Python 3 port. Breezy has a command-line that is backwards compatible with
Bazaar.

Please consider porting git-remote-bzr to the 'breezy' Python module
instead of using Bazaar's 'bzrlib'. Most of the porting process should
be a matter of running s/bzrlib/breezy/ on your code.

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

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

Versions of packages git-remote-bzr depends on:
ii  git1:2.20.1-2
ii  python 2.7.15-4
ii  python-bzrlib  2.7.0+bzr6622-15

git-remote-bzr recommends no packages.

Versions of packages git-remote-bzr suggests:
pn  bzr  
pn  git-doc  

Bug#923095: RM: python-pymca5 [kfreebsd-amd64 kfreebsd-i386] -- RoQA; Out of date, depends on obsolete libs

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Out of date and still depends on obsolete Qt4.

Bug#923094: RM: python-fabio [kfreebsd-amd64] -- RoQA; Out of date, depends on obsolete libs

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Out of date and depends on obsolete Qt4 libs.

Bug#923093: RM: picard [kfreebsd-amd64 kfreebsd-i386] -- RoQA; Old version blocks Qt5 transition

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

Picard version 2 is Qt5.  Obsolete binaries on kfreebsd depend on obsolete
Qt4 libs.

Bug#923092: RM: veusz-helpers-dbg [hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- RoQA; Cruft package in need of removal

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

NBS and (pointlessly) keeping old source/arch all version in the archive.

Scott K

Bug#903092: [RSVP] php-elisp: permission to relicense contributions required from past contributors

[Nicholas D Steeves]

Hi Francesco,

Thank you for your reply, and sorry for the delay in my own.  Reply
follows inline.

On Sat, Feb 02, 2019 at 10:18:39AM +0100, Francesco Poli wrote:
> On Fri, 1 Feb 2019 16:46:07 -0700 Nicholas D Steeves wrote:
> 
> > Dear Ola, Pontus, and Debian Legal team,
> 
> Hello!
> 
> > 
> > It seems Thierry is MIA, and will not be confirming permission to
> > relicense his contributions to d/changelog and d/control.  Please let
> > me know if the following blocks moving to GPL-3+ debian/* and a
> > machine-readable format: 1.0 debian/copyright.  At this point I
> > suspect it does, but I am erring on the side of caution.
> 
> Do I understand correctly that the content of php-elisp/debian/* is
> currently licensed under the terms of the GNU GPL v2 or later?
> 
> If this is the case, since GPL-3+ is compatible with GPL-2+, what's
> wrong in keeping Thierry's contributions under GPL-2+, while the
> remainder of debian/* is migrated to GPL-3+ ?
> The effective resulting licensing status for debian/* would still be
> GPL-3+, although the debian/copyright file would be slightly less
> simple, but, oh well, I guess you could live with that...
> Or am I missing anything important?
> 
> I hope this helps.
> Bye!
> 

Yes, that does help, thank you.  And yes, an extra stanza and license
in d/copyright is nothing compared to doing a manual copyright check
of an old package not in VCS, without the help of 'git blame'.

Please see the last paragraph of my last message in this thread for a
proposal that would save everyone time working through stuff like this.


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#903092: [RSVP] php-elisp: permission to relicense contributions required from past contributors

[Nicholas D Steeves]

Hi Giacomo!

Thank you for your reply, and sorry for the delay in my own.

On Sat, Feb 02, 2019 at 10:54:32AM +, Giacomo wrote:
> I'm one of the old contributors: years ago I did the port from PHP4 to PHP5.
>

Wow, thank you for that work upstream :-)

> To be honest I can't recall if my contribution was done under GPLv2 or GPLv3 
> (or if it included the "or later" option), but I guess it was GPLv2+ as GPLv3 
> was yet to come.
> 
> In any case why restrict the license to GPLv3+ that is incompatible with 
> GPLv2 while the current license is compatible with both GPLv3 and GPLv2?
> 
> 
> Is there any strategic advantage for users' freedom I miss?
> 
> If not, I think that the php-mode would benefit to stay GPLv2+.
> 

I agree, and also prefer GPLv2+ for similar reasons.  I don't remember
when it happened off the top of my head, but FYI upstream changed
maintainers and relicensed to GPLv3+.

  https://github.com/emacs-php/php-mode/issues/387
  https://github.com/ejmr/php-mode

Getting confirmation of copyright for debian/changelog for
contributors who are long gone is an annoying issue when moving to
copyright-format 1.0...  In this case, luckily, Ola is still around to
answer the question of what debian/* packaging was originally intended
to be licensed as!  :-)

It would be nice if there was an official statement from debian-legal,
codified somewhere, saying that  1) for a package that does not use
machine-readable copyright-format 1.0  2) when the original packager is
able to confirm the license of debian/*,  3) then all subsequent
contributions to debian/changelog fall under that license.  I doubt
I'm the only contributor who was mentored to be strict about these
things, and then ended up taking up a bunch of people's time for
paperwork...


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#485330: Non-unified patches and dpkg source format ‘3.0 (quilt)’.

[Charles Plessy]

Le Sun, Feb 24, 2019 at 02:28:39AM +0100, Guillem Jover a écrit :
> 
> Having a single format (well including git formatted patches as
> extensions to the unified format) looks like a rather good property
> to me. And given that we have survived until now w/o the need for
> context diffs, and that it's pretty trivial to convert formats, I'm
> just going to mark this as wontfix and close it.

Hi Guillem and Raphaël,

indeed, I have not encountered upstreams issuing context diffs anymore
since I filled this bug...

Have a nice Sunday,

-- 
Charles

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

[Thomas Dickey]

On Sun, Feb 24, 2019 at 01:56:06AM +0100, Vincent Lefevre wrote:
> No, "tput enacs" returns an error in Linux consoles, and has no effect
> there. For instance, in xterm:

not so (see screenshot).

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#923001: error message on start

[Michael Gilbert]

control: severity -1 serious

Increasing severity since policy 10.7.3 is violated:

"Obsolete configuration files without local changes should be removed
by the package during upgrade."

The file in /etc/chromium.d is obsolete.

Best wishes,
Mike

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

[Guillem Jover]

Package: base-installer
Version: 1.187
Severity: wishlist

Hi!

The current base-installer uses the default debootstrap settings
which end up unconditionally installing systems with the
merged-usr-via-symlinks deployment method which is broken by design,
please see:

  

I'm aware the original request to change the debootstrap default got
unfortunately moved to the tech-ctte. :(

But regardless of that outcome I'd like to request to have a way to
install using debootstrap's --no-merged-usr option, to not have to
install from stretch and then upgrade to buster, or having to drop into
a shell and do manual stuff from within the installer.

In addition it would be also nice if that option was passed whenever
/usr is not on its own partition, because then the properties from
the merged-/usr concept are not relevant anymore, but we get all the
downsides of the broken deployment method.

If this was to be applied for buster, I'd be happy to provide patches.

Otherwise I guess I might need to end up looking to generate
alternative netinst somewhere else or something. :(

Thanks,
Guillem

Bug#923090: reportbug: Please add information about systems tainted due to merged-usr-via-symlinks

[Guillem Jover]

Package: reportbug
Version: 7.5.2
Severity: wishlist

Hi!

The merged-/usr deployment method of using directory symlinks, instead
of properly moving the files or symlinking the contents of these
directories is broken by design.

Please see .

I'd appreciate if you could add information on filed bugs about such
tainted systems. For dpkg I added the following bug-script:

  ,---
  #!/bin/sh

  set -e

  for d in /bin /sbin /lib /lib32 /libo32 /libx32 /lib64; do
if [ "$(readlink $d)" = "usr$d" ]; then
  echo "System tainted due to merged-usr-via-symlinks." >&3
  break
fi
  done
  `---

Thanks,
Guillem

Bug#923089: pod2html: rev should be rel

[積丹尼 Dan Jacobson]

Package: perl
Version: 5.28.1-4
Severity: minor
File: /usr/bin/pod2html

$ pod2html /dev/null| tidy -eq
line 7 column 1 - Warning:  lacks "rel" attribute

So
mailto:root@localhost; /> should be
mailto:root@localhost; />

P.S.,
https://metacpan.org/pod/Pod::Html "Issues" leads to
https://rt.perl.org/ which doesn't have a "new bug" button, hence I
submit via Debian.

Oh and by the way the hardwired doctype in pod::html kind of dated
already... best to use HTML5 (thus without DTD dependency.)

Bug#923001: error message on start

[Michael Gilbert]

control: notforwarded -1
control: reassign -1 chromium-ublock-origin

On Sat, Feb 23, 2019 at 8:31 PM W. Martin Borgert wrote:
> But the culprit was chromium-ublock-origin which was only
> uninstalled, but not purged. After purging
> chromium-ublock-origin, the message is gone.

chromium-ublock-origin is now a transitional package.  It should clean
up its conffiles in /etc/chromium.d when removed.

Best wishes,
Mike

Bug#923088: make upstream link https

[積丹尼 Dan Jacobson]

Package: libssh2-1
Version: 1.8.0-2
Severity: minor
File: /usr/share/doc/libssh2-1/copyright

Say
< Source: http://libssh2.org/
> Source: https://libssh2.org/

Else it seems kind of funny not using https when discussing this package :-)

Bug#923001: error message on start

[W. Martin Borgert]

On 2019-02-23 18:21, Michael Gilbert wrote:
> It likely relates to the GNOME shell extension, though it may not.  I
> am not able to reproduce with a default install. Would you mind trying
> with it removed?

chrome-gnome-shell was installed, indeed — I only searched for
packages starting with webext-.

But the culprit was chromium-ublock-origin which was only
uninstalled, but not purged. After purging
chromium-ublock-origin, the message is gone.

It would be nice, if chromium could be a little bit more
verbose with this dialog :)

Cheers & thanks for the help!

Bug#923087: gbp-dch: fails to enumerate commits when log.showSignature is true in git config

[Gabriel Filion]

I've formatted a patch for upstream that fixes this behaviour. See file
attached
From 42582015feef85b760932c05e802e2f65418a19c Mon Sep 17 00:00:00 2001
From: Gabriel Filion 
Date: Sat, 23 Feb 2019 20:03:41 -0500
Subject: [PATCH] Disable PGP signatures when retrieving list of commits

gbp dch errors out with the following output if the "log.showSignature"
git config is enabled:

$ gbp dch --verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/master']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'log', '--pretty=format:%H', '-1', '--', 'debian/changelog']
gbp:info: Changelog last touched at 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST'
gbp:debug: ['git', 'log', '--pretty=format:%H', 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD', '--no-merges', '--']
fatal: bad revision 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD'
gbp:error: Error getting commits gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD

This is caused by gbp dch receiving unexpected output for the PGP
signatures and trying to use this unexpected output.

To avoid any surprises, let's disable signatures being output when we
list commits.

Also, when collecting a shortlog-like output from commit objects, the
same unexpected PGP signature output is sprayed all over the changelog.
We'll avoid this by also disable showing signatures when showing each
commit's first line.
---
 gbp/git/repository.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gbp/git/repository.py b/gbp/git/repository.py
index a44c71e1..dfc8e556 100644
--- a/gbp/git/repository.py
+++ b/gbp/git/repository.py
@@ -1613,7 +1613,7 @@ class GitRepository(object):
  merge commit
 @type first_parent: C{bool}
 """
-args = GitArgs('--pretty=format:%H')
+args = GitArgs('--pretty=format:%H', '--no-show-signature')
 args.add_true(num, '-%d' % num)
 args.add_true(first_parent, '--first-parent')
 if since:
@@ -1694,7 +1694,7 @@ class GitRepository(object):
 commit_sha1 = self.rev_parse("%s^0" % commitish)
 args = GitArgs('--pretty=format:%an%x00%ae%x00%ad%x00%cn%x00%ce%x00%cd%x00%s%x00%f%x00%b%x00',
'-z', '--date=raw', '--no-renames', '--name-status',
-   commit_sha1)
+   '--no-show-signature', commit_sha1)
 out, err, ret = self._git_inout('show', args.args)
 if ret:
 raise GitRepositoryError("Unable to retrieve commit info for %s"
-- 
2.20.1



signature.asc
Description: OpenPGP digital signature

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

[Vincent Lefevre]

On 2019-02-23 17:37:19 -0500, Thomas Dickey wrote:
> On Tue, Feb 12, 2019 at 06:48:19PM +0100, Vincent Lefevre wrote:
> > Package: ncurses-base
> > Version: 6.1+20181013-2
> > Severity: wishlist
> > 
> > terminfo description of screen and variants have:
> > 
> >   smacs=^N
> >   rmacs=^O
> > 
> > One issue is that these sequences are not recognized by "less -R".
> 
> ...a wishlist item for "less".

I had reported the issue more than 12 years ago, in 2006:

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

> > A workaround would be to change them to:
> > 
> >   smacs=\E(0
> >   rmacs=\E(B
> > 
> > as in various other terminfo descriptions (e.g., xterm).
> > 
> > This seems to work even in the Linux consoles (virtual terminals),
> > which do not support \E(0 and \E(B, i.e. it appears that GNU Screen
> 
> hmm - see "infocmp linux".  We've discussed this before, by the way.
> 
> > does the translation for the real terminal.
> > 
> > Thus I suggest such a change, if there are no drawbacks.
> > 
> > Note: this was also suggested in
> > 
> >   https://savannah.gnu.org/bugs/?23646
> 
> not exactly - the last comment there points out that enacs has to be sent.

No, "tput enacs" returns an error in Linux consoles, and has no effect
there. For instance, in xterm:

$ echo "`tput smacs`mq`tput rmacs`> foo" > z

(i.e. this uses the \E(0 and \E(B escape sequences).

If I cat z directly in a Linux console, I get

mq> foo

but if I cat z in a GNU Screen running in a Linux console, I get

└─> foo

This means that using

  smacs=\E(0
  rmacs=\E(B

in a screen terminfo should be OK.

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

Bug#923087: gbp-dch: fails to enumerate commits when log.showSignature is true in git config

[Gabriel Filion]

Package: git-buildpackage
Version: 0.9.13
Severity: normal

Hi,

I'm having difficulty running gbp dch. I get the following output (with
--verbose set):

pkg-smokeping$ gbp dch --verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'symbolic-ref', 'HEAD']
gbp:debug: ['git', 'show-ref', 'refs/heads/master']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'tag', '-l', 'debian/2.7.3-2']
gbp:debug: ['git', 'log', '--pretty=format:%H', '-1', '--', 'debian/changelog']
gbp:info: Changelog last touched at 'gpg: Signature made Fri 01 Feb 2019 
03:56:19 PM EST'
gbp:debug: ['git', 'log', '--pretty=format:%H', 'gpg: Signature made Fri 01 Feb 
2019 03:56:19 PM EST..HEAD', '--no-merges', '--']
fatal: bad revision 'gpg: Signature made Fri 01 Feb 2019 03:56:19 PM EST..HEAD'
gbp:error: Error getting commits gpg: Signature made Fri 01 Feb 2019 03:56:19 
PM EST..HEAD

It's trying to get a commit that is actually a PGP signature.

I have found that this is caused by the fact that I have configured git
to always show PGP signatures. In order to replicate, you can configure
this option with:

git config log.showSignature true

If this option is disabled, then gbp dch works correctly.

I believe that a simple fix for this issue would be to force-disable the
option when calling git log: simply adding --no-show-signature to the
arguments should do the trick. This way, gbp dch would avoid receiving
the unexpected PGP signature output.

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.19.2
ii  git1:2.20.1-2
ii  man-db 2.8.5-2
ii  python33.7.2-1
ii  python3-dateutil   2.7.3-3
ii  python3-pkg-resources  40.8.0-1
ii  sensible-utils 0.0.12

Versions of packages git-buildpackage recommends:
ii  cowbuilder0.88
ii  pbuilder  0.230.1
ii  pristine-tar  1.46
ii  python3-requests  2.21.0-1
ii  sbuild0.78.1-1

Versions of packages git-buildpackage suggests:
ii  python3-notify2  0.3-3
ii  sudo 1.8.27-1
ii  unzip6.0-22

-- no debconf information

Bug#922420: got an unexpected keyword argument 'bg'

[Ben Finney]

Control: tags -1 + moreinfo

On 17-Feb-2019, Ben Finney wrote:

> So maybe, though upstream has not described any change to this effect,
> the bug has been fixed? Can you try again with version “1.4-1”, now in
> Debian?

This would need to be tested before deciding whether this bug is fixed
in the new version.

-- 
 \   “Don't you try to outweird me, I get stranger things than you |
  `\  free with my breakfast cereal.” —Zaphod Beeblebrox, _The |
_o__)Restaurant At The End Of The Universe_, Douglas Adams |
Ben Finney 

signature.asc
Description: PGP signature

Bug#923086: fwknop 2.6.10 is available

[Francois Marier]

Source: fwknop
Version: 2.6.9-2
Severity: wishlist

A new upstream version is available:

  https://github.com/mrash/fwknop/releases/tag/2.6.10

Francois

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

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

Bug#911533: gandi-cli: missing dependencies

[Ben Finney]

Control: clone -1 -2
Control: retitle -1 gandi-cli: Python dependencies not declared
Control: summary -1 ‘dh_python3’ is failing to expand ${python3:Depends} for 
the binary package.
Control: outlook -1 0
Control: fixed -1 gandi-cli/1.4-1
Control: close -1
Control: retitle -2 gandi-cli: Show ‘dh_python3’ where to find install 
requirements

The workaround is to explicitly declare the package dependencies,
because ‘dh_python3’ fails to do so.

A better solution is to have ‘dh_python3’ correctly find the package
install requirements list, as built by Setuptools.

On 13-Nov-2018, Michele Orrù wrote:

> one can see that at least the packages python3-ipy, python3-click,
> and python3-yaml are missing.

With release “1.4-1” the declared dependencies are:

Depends: python3-setuptools, python3-yaml, python3-click, python3-requests, 
python3-ipy, python3

https://tracker.debian.org/media/packages/g/gandi-cli/control-1.4-1>

This addresses the problem reported originally in this bug report.

-- 
 \  “I don't like country music, but I don't mean to denigrate |
  `\  those who do. And for the people who like country music, |
_o__)denigrate means ‘put down’.” —Bob Newhart |
Ben Finney 

signature.asc
Description: PGP signature

Bug#922667: beep: Error: could not open any device

[GSR]

Package: beep
Followup-For: Bug #922667

Before it worked fine via sound card speakers as normal user, now not
even root can get beeps. I understand the user perms setup part being
not done yet, but not why root fails too (the only difference is if it
prints "Error: Could not open any device" or not).

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

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

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

beep recommends no packages.

beep suggests no packages.

-- no debconf information

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

[Elana Hashman]

On Tue, Jan 22, 2019 at 05:39:46PM -0800, Phil Hagelberg wrote:
> 
> It looks like it's been fixed in newer versions of Clojure, but we
> haven't bumped that in Leiningen yet.

Note that this has been fixed upstream in the 2.9.0 release. I've been
trying to upgrade Leiningen in Debian to this new release but the jar is
not working properly with the current build strategy; it's slow and
can't seem to find clojure.main on any JVM.

I've had no luck trying to pin down where the bug is and the complexity
of the build is not helping. So this weekend I am going to look into
changing the build to more closely match upstream, now that we've
bootstrapped a working Leiningen into the archive. This would involve
building Leiningen with a previous version of itself, as upstream does.
(In Debian, we currently build the leiningen-core jar using Maven and
then attempt to build the entire Leiningen codebase with that.)

- e


signature.asc
Description: PGP signature

Bug#921761: sssd: FTBFS (failing tests)

[Dominik George]

Fedora project seems to know how to fix this, but I cannot get my head
wrapped around how the hell you find out how they did it…

 https://bugzilla.redhat.com/show_bug.cgi?id=1645912

-nik


signature.asc
Description: PGP signature

Bug#923028: fails to access microphone

[Michael Gilbert]

control: severity -1 minor
control: forwarded -1 http://crbug.com/835767

On Sat, Feb 23, 2019 at 4:21 AM W. Martin Borgert wrote:
> When I access a meet jitsi site, e.g.
> https://meet.jit.si/ChromiumFailsToAccessMyMicrophone
> Chromium asks whether I allow access to camera and microphone.
> When I allow, I get the error message
> "Fails to access your microphone" from Jitsi.

This is a known upstream bug.

Best wishes,
Mike

Bug#682369: firefox-esr disobeys "until I close Firefox" cookie setting

[Robert Munyer]

Control: found -1 60.5.1esr-1~deb9u1
Control: retitle -1 firefox-esr disobeys "until I close Firefox" "cookies and 
site data" setting

To reproduce in version 60.5.1esr-1~deb9u1, currently in Debian stable:

Open Firefox ESR.

Configure Firefox thus:
  ≡
Preferences
  Privacy & Security
Browser Privacy
  Cookies and Site Data
Accept cookies and site data from websites (recommended)
  Keep until: I close Firefox

Browse to https://www.meetup.com .

Close Firefox.

After the preceding steps, meetup.com "cookies and site data" must not exist.
To see that meetup.com data still exist, continue with the following steps:

Open Firefox ESR.

View cookies and site data:
  ≡
Preferences
  Privacy & Security
Browser Privacy
  Cookies and Site Data
Manage Data...

Bug#923083: postfix: Empty smtp_tls_CApath by default

[Kurt Roeckx]

Package: postfix
Version: 3.3.2-1

Hi,

It seems that by default smtp_tls_CApath is not set, which means
by default postfix can't check that certificates are valid. Please
set the default to /etc/certs/ssl, and add a Depends or Recommends
on ca-certificates.


Kurt

Bug#921761: sssd: FTBFS (failing tests)

[Dominik George]

The error returned in line 193 of test_copy_ccache.c is "Matching credential 
not found".


signature.asc
Description: PGP signature

Bug#923001: error message on start

[Michael Gilbert]

On Sat, Feb 23, 2019 at 1:58 PM W. Martin Borgert wrote:
> Still, under chrome://extensions/, I see three extensions:
>
>  - Chromium PDF Viewer
>  - CryptoTokenExtension
>  - GNOME Shell integration

It likely relates to the GNOME shell extension, though it may not.  I
am not able to reproduce with a default install. Would you mind trying
with it removed?

Best wishes,
Mike

Bug#923081: privacy invasion due to automatic fallback to Cloudflare

[Toni]

Package: systemd
Version: 240-6
Severity: important
Tags: upstream



Hi,

I was looking into upstream's changes for the release in unstable to
decide, whether or not I should report the problem with stopping
systemd-resolved, and found this:


---
resolved: use Cloudflare public DNS server as a default fallback alon…

…gside Google one

Cloudflare public DNS service is currently the fastest one according to
https://www.dnsperf.com/#!dns-resolvers. Why not improve the experience for
systemd users using this as a default fallback nameserver?
---

(Commit #def3c7c)

That falls imho under unpleasant surprises. We pretend to be conscious
of privacy etc, then underhandedly hand our DNS queries to Google and
Cloudflare if something goes wrong (misconfigured router? broken other
DNS server?), instead of having the query fail and let the user take a
decision.


Cheers,
Toni




-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.13.2-7
ii  libaudit11:2.8.4-2
ii  libblkid12.33.1-0.1
ii  libc62.28-7
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-1
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.6-2
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-3
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.1.8-4
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  240-6
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.12-1
ii  libpam-systemd  240-6

Versions of packages systemd suggests:
ii  policykit-10.105-25
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133
ii  udev 240-6

-- Configuration Files:
/etc/systemd/resolved.conf changed [not included]

-- no debconf information

Bug#921637: [DRE-maint] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method

[Georg Faerber]

Control: tags + confirmed pending

On 19-02-23 20:24:15, brian m. carlson wrote:
> It would be great if we could get this patch into buster. [...]

Upload, including the patch, upcoming in the next days.

Cheers,
Georg


signature.asc
Description: Digital signature

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

[Thomas Dickey]

On Tue, Feb 12, 2019 at 06:48:19PM +0100, Vincent Lefevre wrote:
> Package: ncurses-base
> Version: 6.1+20181013-2
> Severity: wishlist
> 
> terminfo description of screen and variants have:
> 
>   smacs=^N
>   rmacs=^O
> 
> One issue is that these sequences are not recognized by "less -R".

...a wishlist item for "less".

> A workaround would be to change them to:
> 
>   smacs=\E(0
>   rmacs=\E(B
> 
> as in various other terminfo descriptions (e.g., xterm).
> 
> This seems to work even in the Linux consoles (virtual terminals),
> which do not support \E(0 and \E(B, i.e. it appears that GNU Screen

hmm - see "infocmp linux".  We've discussed this before, by the way.

> does the translation for the real terminal.
> 
> Thus I suggest such a change, if there are no drawbacks.
> 
> Note: this was also suggested in
> 
>   https://savannah.gnu.org/bugs/?23646

not exactly - the last comment there points out that enacs has to be sent.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#695894: libvorbisidec-dev: please include pkgconfig

[Petter Reinholdtsen]

[Florian Schlichting]
> I can lend a hand if you indicate the direction into which you want this
> to go...

I lack the spare time required to look at this.  Feel free to do what
you believe is most sensible.  I am happy to see NMUs, I am on the
LowNMU list.  I have not heard from Martin for quite a while. :(

There was a proposal to move the xiph packages into the debian
multimedia team, but I do not know what came out of it.

-- 
Happy hacking
Petter Reinholdtsen

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

[Roberto C . Sánchez]

On Sat, Feb 23, 2019 at 12:59:17PM -0800, Russ Allbery wrote:
> Roberto C. Sánchez  writes:
> 
> > Here is the line from the pkg-config file:
> 
> > Libs: -L${libdir} -lbson-static-1.0  -lpthread -lgcc -lgcc_s -lc -lgcc
> > -lgcc_s /usr/lib/x86_64-linux-gnu/librt.so
> > /usr/lib/x86_64-linux-gnu/libm.so
> 
> For whatever it's worth, I personally would consider editing all of that
> out in the Debian packaging unless you're explicitly trying to support
> -nostdlib builds with that library.  The linker will add the correct
> version of that rune automatically by default, and providing it via
> pkg-config can sometimes cause issues if the handling of those libraries
> changes in the future.
> 
Russ,

That is very helpful indeed.  I will check with upstream to see if
-nostdlib support is the intent and will adjust the pkg-config script
accordingly.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Bug#906258: stretch-pu: package yubico-piv-tool/1.4.2-2

[Julien Cristau]

On 2/23/19 7:56 PM, Nicolas Braud-Santoni wrote:
> On Sat, Feb 23, 2019 at 02:27:04PM +0100, Nicolas Braud-Santoni wrote:
>> On Fri, Feb 15, 2019 at 04:55:58PM +0100, Nicolas Braud-Santoni wrote:
>>> On Wed, Feb 13, 2019 at 03:34:50PM +0100, Nicolas Braud-Santoni wrote:
 I assume I can't just dput this, as it already exists in stable-new.
 Could you reject the existing package first, and I will reupload?
>>>
>>> Uploaded a new revision at the request of jcristau.
>>
>> Ping?
> 
> Nevermind, ftpmaster rejected the upload:
> 
They did not; I did, as I told you in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906258#69

> On Sat, Feb 23, 2019 at 05:47:07PM +, Debian FTP Masters wrote:
>> yubico-piv-tool - inappropriate changelog entry
> 
> 
> Dear ftpmasters, could you clarify in which way the changelog entry is
> inappropriate, and what would be an appropriate changelog entry?
> 
An appropriate changelog entry is one that describes the changes made to
the package.  For example, "Remove cruft that was included in the source
package by mistake" would be one way to describe the changes in your upload.

Cheers,
Julien

Bug#923039: RFS: dayon/1.7.1 ITP -- a cross platform remote assistance tool

[Adam Borowski]

On Sat, Feb 23, 2019 at 02:05:37PM +0100, Fensterkitt Computer Support wrote:
> Package name    : dayon
> Version : 1.7.1
> Upstream Author : Reto Glante, i...@fensterkitt.ch

> It builds those binary packages:
> dayon_1.7.1_all.deb (which includes both, the assistant and the assisted
> app, written in Java)
> 
> https://github.com/RetGal/Dayon/releases/download/v1.7.1/dayon_1.7.1_all.deb

Hi!
You'd need to submit the source package; .deb is only the product of
building.


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

Bug#923080: chromium: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)

[Paul Menzel]

Package: chromium
Version: 72.0.3626.109-1
Severity: wishlist

Dear Debian folks,


Decoding videos on the GPU using VA-API does not seem to work after bugs 
reports #856255 [1] and #919762 [2] were fixed.


The messages below are shown during start.

```
$ chromium
libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)
[28239:28239:0223/215051.751645:ERROR:vaapi_wrapper.cc(324)] 
vaInitialize failed: unknown libva error
[28239:28239:0223/215051.795078:ERROR:sandbox_linux.cc(364)] 
InitializeSandbox() called with multiple threads in process gpu-process.

libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
```

VA-API is installed properly though.

```
$ vainfo
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.4 (libva 2.4.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.3.0
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264MultiviewHigh  : VAEntrypointVLD
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointVLD
```

So it looks like, some piece is still missing for working VA-API support.


Kind regards,

Paul


[1]: https://bugs.debian.org/856255
[2]: https://bugs.debian.org/919762

Bug#923079: tcl8.6-dev: tcl.pc pkgconfig file not packaged

[Manuel Bilderbeek]

Package: tcl8.6-dev
Version: 8.6.9+dfsg-1
Severity: important

Dear Maintainer,

It looks like nowadays pkg-config is the (de-facto) standard for finding
packages. Unlike most other dev packages and unlike other distros, the Debian
dev package of Tcl does not include the tcl.pc file.

Please add it to the dev package of Tcl. Thanks!

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

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

Versions of packages tcl8.6-dev depends on:
ii  dpkg-dev1.19.2
ii  libtcl8.6   8.6.9+dfsg-1
ii  tcl8.6  8.6.9+dfsg-1
ii  zlib1g-dev  1:1.2.11.dfsg-1

tcl8.6-dev recommends no packages.

Versions of packages tcl8.6-dev suggests:
pn  tcl8.6-doc  

-- no debconf information

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

[Russ Allbery]

Roberto C. Sánchez  writes:

> Here is the line from the pkg-config file:

> Libs: -L${libdir} -lbson-static-1.0  -lpthread -lgcc -lgcc_s -lc -lgcc
> -lgcc_s /usr/lib/x86_64-linux-gnu/librt.so
> /usr/lib/x86_64-linux-gnu/libm.so

For whatever it's worth, I personally would consider editing all of that
out in the Debian packaging unless you're explicitly trying to support
-nostdlib builds with that library.  The linker will add the correct
version of that rune automatically by default, and providing it via
pkg-config can sometimes cause issues if the handling of those libraries
changes in the future.

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

Bug#918804: python3-yaml: Please mark as "Multi-Arch: allowed"

[Elrond]

tags 918804 - moreinfo
tags 918804 + help
thanks

I think, moreinfo is misleading here.
I think, help is better. It means: You're asking for help
by other (Debian) developers.

That said:

What's needed to continue?
Which help do you need?
Do we need to explain something better?


Cheers

Elrond

Bug#922862: Please add a test for packages that are shipping a cron script/config file and not a .timer

[Russ Allbery]

Laurent Bigonville  writes:

> So my idea was, we can either force the installation of anacron again (I
> wonder if we shouldn't do that for buster anyway) or we go forward and
> we move to use systemd timers instead of cron (which allows proper
> process tracking just like any other service).

No objections to adding an experimental tag to track this, but just to
warn (mostly for the record in the bug): converting a cron job to a
systemd timer is not trivial, nor is providing the logic that ensures the
job then doesn't run twice (since the cron job can't be removed because
the host may not be using systemd).  We don't have good helpers for this
yet, so it requires some careful thought to make this work properly.

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

Bug#847440: [Resolvconf-devel] Bug#847440: pending

[Thomas Hood]

I will orphan the package if I can't meet my self-imposed deadline. I'll
also RFA it again, although that didn't attract any interest on previous
occasions.

Please feel free to do a QA NMU.

Regards,
Thomas




Op vr 22 feb. 2019 08:58 schreef Bernhard Schmidt :

> Hi Thomas,
>
> having no time or motivation to work on a package is not a shame, but
> could you please properly orphan the package then (or give us the
> permission to do so if you don't want to read up on the procedure)? I'd
> like to at least do a QA upload for Buster with the git repository
> migrated to Salsa and #847440 fixed.
>
> I don't want to maintain it either (barely using it), but having it
> officially orphaned would lower the bar for NMUs.
>
> Best Regards,
> Bernhard
>

Bug#922915: initscripts: Please do not enable tmpfs-based shm on Hurd

[Samuel Thibault]

Dmitry Bogatov, le sam. 23 févr. 2019 20:07:42 +, a ecrit:
> [2019-02-21 21:33] Samuel Thibault 
> > Hello,
> >
> > Please do not enable tmpfs-based shm by default on the Hurd yet, the
> > tmpfs implementation is not ready for that yet and triggers runtime
> > issues.
> >
> > The attached patch makes the default per-kernel, could you apply it?
> 
> Well, yes; but I'd like not to keep it indefinitely. Please add comment
> with apporiate number of hurd bug.

Here it is.

Samuel
---
 debian/src/initscripts/lib/init/tmpfs.sh |   10 +-
 1 file changed, 9 insertions(+), 1 deletion(-)

--- a/debian/src/initscripts/lib/init/tmpfs.sh
+++ b/debian/src/initscripts/lib/init/tmpfs.sh
@@ -85,8 +85,17 @@ need_overflow_tmp ()
 # values here.
 
 RAMLOCK=yes
+KERNEL="$(uname -s)"
 # These might be overridden by /etc/default/rcS
-if [ -z "$RAMSHM" ]; then RAMSHM=yes; fi
+case "$KERNEL" in
+   GNU)
+   # tmpfs can not be used for shm yet, see #923078
+   if [ -z "$RAMSHM" ]; then RAMSHM=no; fi
+   ;;
+   *)
+   if [ -z "$RAMSHM" ]; then RAMSHM=yes; fi
+   ;;
+esac
 if [ -z "$RAMTMP" ]; then RAMTMP=no; fi
 
 TMPFS_SIZE=20%VM

Bug#923078: hurd: tmpfs not ready for shm support yet

[Samuel Thibault]

Package: hurd
Version: 1:0.9.git20181030-4
Severity: important
Tags: upstream

tmpfs currently crashes if one does:

- open a file
- mmap it
- close the file
- unlink the file
- dereference the map

because the map doesn't keep a reference, and thus the memory object is
gone.

See in hurd/tmpfs/node.c's diskfs_free_node, DT_REG case:

case DT_REG:
  if (np->dn->u.reg.memobj != MACH_PORT_NULL) {
/* XXX GNU Mach will terminate the object, and thus existing mappings
 * will get SIGBUS.  */
vm_deallocate (mach_task_self (), np->dn->u.reg.memref, 4096);
mach_port_deallocate (mach_task_self (), np->dn->u.reg.memobj);
  } 
  break;

Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20190109-486-dbg/Hurd-0.9
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages hurd depends on:
ii  hurd-libs0.3  1:0.9.git20181030-4
ii  libblkid1 2.33.1-0.1
ii  libbz2-1.01.0.6-9
ii  libc0.3   2.28-7
ii  libdaemon00.14-7
ii  libgcrypt20   1.8.4-5
ii  liblwip0  2.0.3-3
ii  libncursesw6  6.1+20181013-2
ii  libtinfo6 6.1+20181013-2
ii  libx11-6  2:1.6.7-1
ii  lsb-base  10.2018112800
ii  netdde0.0.20150828-5
ii  sysv-rc   2.93-8
ii  xkb-data  2.26-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages hurd recommends:
ii  bf-utf-source  0.08

Versions of packages hurd suggests:
ii  hurd-doc  1:0.9.git20181030-4

-- Configuration Files:
/etc/hurd/rc changed [not included]

-- no debconf information

-- 
Samuel Thibault 

Bug#923077: pyzor: crashes on certain emails

[nijel]

Package: pyzor
Version: 1:1.0.0-3
Severity: normal

Dear Maintainer,

some tested emails make pyzor crash. I haven't collected the problematic
email, but I can probably do that as there is about one in a hour going
to my mail server and spamassasin complains with "internal error, python
traceback seen in response". If you have hints how to save the processed
email in that case, it would help.

The pyzor crashes with:

Traceback (most recent call last):
 File "/usr/bin/pyzor", line 408, in 
   main()
 File "/usr/bin/pyzor", line 152, in main
   if not dispatch(client, servers, config):
 File "/usr/bin/pyzor", line 237, in check
   for digested in get_input_handler(style):
 File "/usr/bin/pyzor", line 174, in _get_input_msg
   msg = email.message_from_file(sys.stdin)
 File "/usr/lib/python3.7/email/__init__.py", line 54, in message_from_file
   return Parser(*args, **kws).parse(fp)
 File "/usr/lib/python3.7/email/parser.py", line 54, in parse
   data = fp.read(8192)
 File "/usr/lib/python3.7/codecs.py", line 322, in decode
   (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 1041: 
invalid start byte

Michal

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

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

Versions of packages pyzor depends on:
ii  python3  3.7.2-1

pyzor recommends no packages.

Versions of packages pyzor suggests:
pn  pyzor-doc  

-- no debconf information

Bug#682369: firefox-esr disobeys "until I close Firefox" cookie setting

[Robert Munyer]

Sven Joachim wrote:

> Basically that's the way session restore works, and I have
> always seen this as a feature rather than a bug, although
> that is certainly debatable.  Some upstream discussions:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=443354
> https://bugzilla.mozilla.org/show_bug.cgi?id=529644
> https://bugzilla.mozilla.org/show_bug.cgi?id=530594
> https://bugzilla.mozilla.org/show_bug.cgi?id=1286748

Sure, it's nice for some people, and in some situations.

But in this situation, Firefox is clearly retaining data
which the user has _explicitly_commanded_it_not_to_retain_.

Covertly disobeying the user's direct command is definitely,
not debatably, wrong.

I used the word "covertly" because Firefox accepts the user's
command, with no indication that it intends to disobey it.

In fact, the user generally doesn't know that the command has
been disobeyed, until after illegitimately retained data have
been exfiltrated to a server somewhere, which can't be undone.

Bug#923076: [INTL:da] Danish translation of the debconf templates ocsinventory-agent

[Joe Dalton]

Package: ocsinventory-agent
Severity: wishlist
Tags: l10n patch

Please include the attached Danish ocsinventory-agent debconf po file.

joe@debianbuster:~/over/debian/ocsinventory-agent$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 10 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923075: [INTL:da] Danish translation of the debconf templates webalizer

[Joe Dalton]

Package: webalizer
Severity: wishlist
Tags: l10n patch

Please include the attached Danish webalizer debconf po file.

joe@debianbuster:~/over/debian/webalizer$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 13 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#921637: [pkg-go] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method

[brian m. carlson]

On Sat, Feb 16, 2019 at 09:55:16PM -0500, Andrew Janke wrote:
> I've confirmed this is the https://github.com/apjanke/ronn-ng/issues/24 bug
> in ronn-ng.
> 
> It looks liike an easy fix and I have pushed a ronn-ng 0.8.1.beta.1
> gem/release with the fix. Are you able to test against a prerelease gem?
> 
> I've tested locally and it fixed the problem for git-lfs man generation.
> I've also added an ordered-list example to Ronn-NG's internal test suite.

It would be great if we could get this patch into buster. I realize that
a new version may not be possible, but applying a patch to fix an FTBFS
might be.

As an upstream Git LFS maintainer, I'm already seeing people trying to
build git-lfs packages on buster and (in Ubuntu) disco and failing to do
so because of this bug. It will be difficult for us to build our own
packages on buster if this isn't fixed.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#923073: screen: chdir does not do tilde substitution

[Thorsten Glaser]

Package: screen
Version: 4.6.2-3
Severity: minor

^A:chdir ~/foo/bar does not work.

^A:source ~/.screenrc-foo does work since recently, so it got
fixed in at least some other place in the source, the fix now
“only” needs to be applied everywhere else pathnames are used.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages screen depends on:
ii  libc6 2.28-7
ii  libpam0g  1.3.1-5
ii  libtinfo6 6.1+20181013-2
ii  libutempter0  1.1.6-3

screen recommends no packages.

Versions of packages screen suggests:
pn  byobu | screenie | iselect  
pn  ncurses-term

-- Configuration Files:
/etc/screenrc changed:
startup_message off
deflogin on
vbell on
vbell_msg "   Suddenly, your kitten starts purring!!  "
termcap  facit|vt100|xterm|xterm-xfree86 LP:G0
terminfo facit|vt100|xterm|xterm-xfree86 LP:G0
termcap  ansi-nt am@:hs@
terminfo ansi-nt am@:hs@
termcap  vt100 dl=5\E[M
terminfo vt100 dl=5\E[M
termcap  facit al=\E[L\E[K:AL@:dl@:DL@:cs=\E[%i%d;%dr:ic@
terminfo facit al=\E[L\E[K:AL@:dl@:DL@:cs=\E[%i%p1%d;%p2%dr:ic@
termcap  sun 
'up=^K:AL=\E[%dL:DL=\E[%dM:UP=\E[%dA:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:IC=\E[%d@:WS=1000\E[8;%d;%dt'
terminfo sun 
'up=^K:AL=\E[%p1%dL:DL=\E[%p1%dM:UP=\E[%p1%dA:DO=\E[%p1%dB:LE=\E[%p1%dD:RI=\E[%p1%dC:IC=\E[%p1%d@:WS=\E[8;%p1%d;%p2%dt$<1000>'
termcap  xterm|xterm-xfree86|fptwist hs@:cs=\E[%i%d;%dr:im=\E[4h:ei=\E[4l
terminfo xterm|xterm-xfree86|fptwist hs@:cs=\E[%i%p1%d;%p2%dr:im=\E[4h:ei=\E[4l
termcap  xterm|xterm-xfree86 'is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;4;6l'
terminfo xterm|xterm-xfree86 'is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;4;6l'
termcap  hp700 
'Z0=\E[?3h:Z1=\E[?3l:hs:ts=\E[62"p\E[0$~\E[2$~\E[1$}:fs=\E[0}\E[61"p:ds=\E[62"p\E[1$~\E[61"p:ic@'
terminfo hp700 
'Z0=\E[?3h:Z1=\E[?3l:hs:ts=\E[62"p\E[0$~\E[2$~\E[1$}:fs=\E[0}\E[61"p:ds=\E[62"p\E[1$~\E[61"p:ic@'
termcap wy75-42 nx:xo:Z0=\E[?3h\E[31h:Z1=\E[?3l\E[31h
terminfo wy75-42 nx:xo:Z0=\E[?3h\E[31h:Z1=\E[?3l\E[31h
bind ^k
bind ^\
bind \\ quit
bind K kill
bind I login on
bind O login off
bind } history
bind > bumpright
bind < bumpleft
bind = collapse
bind -c dashkey - select -
bind -c dashkey 0 select 10
bind -c dashkey 1 select 11
bind -c dashkey 2 select 12
bind -c dashkey 3 select 13
bind -c dashkey 4 select 14
bind -c dashkey 5 select 15
bind -c dashkey 6 select 16
bind -c dashkey 7 select 17
bind -c dashkey 8 select 18
bind -c dashkey 9 select 19
bind - command -c dashkey
bind u digraph 'U+'
defnonblock 120
term screen
shell "-${SHELL}"
shelltitle -
nethack on
defscrollback 4096
defutf8 on
setenv LC_CTYPE en_US.UTF-8
escape ^Aa
hardstatus alwayslastline "%{wm}A %{kr} %H %{ky} %l %{kg} %D %Y-%m-%d %0c %{=b 
by} %01L=%=%-w%50L>[%n%f %t]%+w%-1< "


-- no debconf information

Bug#923074: [INTL:da] Danish translation of the debconf templates x2goserver

[Joe Dalton]

Package: x2goserver
Severity: wishlist
Tags: l10n patch

Please include the attached Danish x2goserver debconf po file.

joe@debianbuster:~/over/debian/x2goserver$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 18 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

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

[Ralf Treinen]

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

Hi,

please remove src:why from testing.

why depends on why3. However, the version of why in testing, as well as
the newest version of why published by ustream, need a version of why3
<= 0/88.3 which is older than the version of why3 that we have in
testing or in unstable. This makes why unusable [1]. For this reason
I think that why should not be distributed with buster, please remove
it from testing.

The current why in testing delays the migration of coq and friends
(I hope we get one day all the blockers of coq out of the way!)

Thanks -Ralf.

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

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

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

Bug#923050: RFS: pk2/1.2.1-1 [ITP] -- 2D Oldschool platform game where you control a rooster

[Carlos Donizete Froes]

Hi Feri,

> Is the g++ dependency of the main game binary intentional?

The intention I had when adding g++ as dependency on the d/control, because 
strangely in the 'armel'
architecture, the game did not compile in my tests. But I can withdraw without 
problems. :)

> I built the game for stretch, it went OK (after reducing the debhelper
> compatibility level to 11, but that isn't a problem).  The game starts,
> but I'm unable to select a map: the presented list is empty, though
> strace shows it finds the /usr/share/games/pk2/data/episodes directory.
> 
> Also, it tries to create the config directory in
> /usr/share/games/pk2/data, which fails with permission denied.

Great observation, I will be correcting this problem and making a new version 
immediately.

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀  2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Bug#918827: I'll apply the patch and NMU

[Andreas Tille]

Hi,

since this package is about to be removed I'll apply the patch and NMU soon.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#916594: [Pkg-mozext-maintainers] Bug#916594: Bug#916594: Bug#916594: Bug#916594: webext-umatrix: Can not load configuration from backup

[Antoine Beaupré]

On 2019-02-23 20:04:00, Ximin Luo wrote:
> Antoine Beaupré:
>> [..]
>> To reproduce the problem, I do the following:
>> 
>>  1. uninstall ("remove" in the addons menu) uMatrix
>>  2. quit Firefox
>>  3. apt install webext-umatrix
>
> Did you do the workaround for 919557 that I mentioned?

I did and, as I said earlier, it had no effect.

a.

-- 
What this country needs is more unemployed politicians.
- Angela Davis

Bug#902618: why: needs porting to why3 version 1.0.0

[Ralf Treinen]

The current version of why in debian, 2.40, as well as the newest
available upstream version 2.41, need a version of why3 that is
older than the version of why3 that we have in unstable or in
testing (see the table in [1]). As a consequence I think that
why should not be distributed with buster.

[1] http://krakatoa.lri.fr/

Bug#922264: pkg-perl-autopkgtest: use "skippable" and "superficial" restrictions

[Xavier]

Le 23/02/2019 à 18:32, gregor herrmann a écrit :
> On Sat, 16 Feb 2019 19:52:06 +0200, Niko Tyni wrote:
> 
>> I agree with the intention here. The only non-superficial test of the
>> current ones is indeed the 'smoke' test.
> 
> Cool, thanks.
>  
>> However, I have an "architectural" concern.
> 
> […]
> 
> Makes sense. Maybe material for the next sprint?
>  
>> Please don't consider this a blocker or veto for the proposed
>> implementation. It's a clear improvement and does not make
>> it any harder to simplify the architecture later.
> 
> Ok, so I guess we can merge this change?
> Xavier, I seem to remember that this has to go into autodep8 first or
> something like that?

Hello,

Right, pushed
(https://salsa.debian.org/ci-team/autodep8/merge_requests/13). We have
to wait for autodep8 release with with MR merged before accepting
pkg-perl-tools MR, else autopkgtest will fail.

Cheers,
Xavier

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

[Andreas Ronnquist]

On Sat, 23 Feb 2019 20:34:41 +0100
"jEsuSdA 8)"  wrote:

>El 23/2/19 a las 19:05, Andreas Ronnquist escribió:
>> On Sat, 23 Feb 2019 01:36:27 +0100 jEsuSdA 
>> wrote:  
>>> Dear Maintainer,
>>>
>>> Geeqie crashes when trying to editing archive preferences.
>>>
>>> Once you try to ADD new archive filter, geeqie crashes.
>>>  
>> 
- 8< -
>
>For help, type "help".
>Type "apropos word" to search for commands related to "word"...
>Reading symbols from geeqie...(no debugging symbols found)...done.
>(gdb) start
>Function "main" not defined.
>Make breakpoint pending on future shared library load? (y or [n]) n
>Starting program: /usr/bin/geeqie
>[Thread debugging using libthread_db enabled]
>Using host libthread_db library
>"/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7160e700
>(LWP 11622)] [New Thread 0x70e0d700 (LWP 11623)]
>[Detaching after fork from child process 11624]
>[Detaching after fork from child process 11626]
>[Detaching after fork from child process 11628]
>[Detaching after fork from child process 11630]
>[New Thread 0x7fffe9671700 (LWP 11632)]
>[New Thread 0x7fffe8e70700 (LWP 11633)]
>[Detaching after fork from child process 11634]
>[Detaching after fork from child process 11636]
>[Detaching after fork from child process 11638]
>[Detaching after fork from child process 11640]
>[Thread 0x7fffe8e70700 (LWP 11633) exited]
>
>Thread 1 "geeqie" received signal SIGSEGV, Segmentation fault.
>0x5565a432 in ?? ()
>

That doesn't tell me much - please install debug symbols for geeqie -
see

https://wiki.debian.org/AutomaticDebugPackages

and add the testing-debug repo - after this install the geeqie-dbgsym
package and please do a backtrace in gdb (the command bt full in gdb)
after the segmentation fault.

thanks
/Andreas
gus...@debian.org

Bug#922915: initscripts: Please do not enable tmpfs-based shm on Hurd

[Dmitry Bogatov]

[2019-02-21 21:33] Samuel Thibault 
> Hello,
>
> Please do not enable tmpfs-based shm by default on the Hurd yet, the
> tmpfs implementation is not ready for that yet and triggers runtime
> issues.
>
> The attached patch makes the default per-kernel, could you apply it?

Well, yes; but I'd like not to keep it indefinitely. Please add comment
with apporiate number of hurd bug.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#567071: what is the purpose of fstab-decode

[Dmitry Bogatov]

control: tags -1 +fixed-upstream

[2019-02-21 15:08] Jesse Smith 
> I agree, the manual page for fstab-decode is vague, at best. I will add
> a paragraph explaining what it does. The updated manual page will be
> included in sysvinit-2.94.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#905244: fstab-decode.8: Some formatting fixes in the manual

[Dmitry Bogatov]

Jesse, what do you think?

[2018-08-02 01:07] Bjarni Ingi Gislason 
> Package: sysvinit-utils
> Version: 2.88dsf-59.10
> Severity: minor
> Tags: patch
>
>   Summary:
>
> Separate an ellipsis from the preceding string with a space.
>
> Add a missing italic correction or use a macro.
>
> Make a '"' being an argument to a macro
>
> 
>
>   Details:
>
> Input file is fstab-decode.8
>
> Test nr. 10:
>
> Separate an ellipsis from the preceding string with a space
> character, if it does not mean a continuation of it.
>
> See a manual of style about the difference between "abc..." and
> "abc ...".
>
> 25:\fB fstab-decode\fR \fICOMMAND\fR [\fIARGUMENT\fR]...
>
> #
>
>
> Test nr. 21:
>
> Use a macro to change to the italic font, instead of \fI [1], if
> possible.
> The macros have the italic corrections, but "\c" removes them.
>
>   Or
>
> add the italic corrections.
> [1] man-pages(7) [package "manpages"]
>
> 25:\fB fstab-decode\fR \fICOMMAND\fR [\fIARGUMENT\fR]...
> 29:decodes escapes in the specified \fIARGUMENT\fRs
> 30:and uses them to run \fICOMMAND\fR.
> 41:Otherwise it exits with the status returned by \fICOMMAND\fR.
>
> #
>
>   Make a quotation mark (") to be an argument to a macro.
>
>   This fixes bug #567071
>
> ###
>
>   Patch:
>
> --- fstab-decode.82017-09-08 19:18:37.0 +
> +++ fstab-decode.8.new2018-08-01 23:51:30.0 +
> @@ -22,11 +22,11 @@
>  fstab-decode \- run a command with fstab-encoded arguments
>  
>  .SH SYNOPSIS
> -\fB fstab-decode\fR \fICOMMAND\fR [\fIARGUMENT\fR]...
> +\fB fstab-decode\fR \fICOMMAND\fR [\,\fIARGUMENT\fR \&.\|.\|.\&]
>  
>  .SH DESCRIPTION
>  .B fstab-decode
> -decodes escapes in the specified \fIARGUMENT\fRs
> +decodes escapes in the specified \fIARGUMENT\/\fRs
>  and uses them to run \fICOMMAND\fR.
>  The argument escaping uses the same rules as path escaping in
>  \fB/etc/fstab\fR,
> @@ -42,4 +42,4 @@ Otherwise it exits with the status retur
>  
>  .SH EXAMPLES
>  
> -.B fstab-decode umount $(awk '$3 == "vfat" { print $2 }' /etc/fstab)
> +.B fstab-decode umount $(awk '$3 == """vfat""" { print $2 }' /etc/fstab)
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
> 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.17.8-3 (SMP w/2 CPU cores)
> Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
> LANGUAGE=is_IS.iso88591 (charmap=IS
> O-8859-1)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages sysvinit-utils depends on:
> ii  init-system-helpers  1.51
> ii  libc62.27-5
> ii  util-linux   2.32-0.1
>
> sysvinit-utils recommends no packages.
>
> sysvinit-utils suggests no packages.
>
> -- no debconf information
>
> -- 
> Bjarni I. Gislason
>
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#843419: init-d-script: please provide a way to not use the --name option of start-stop-daemon

[Dmitry Bogatov]

control: tags -1 +moreinfo

[2016-11-06 16:04] Ferenc Wágner 
> Package: sysvinit-utils
> Version: 2.88dsf-59
> Severity: wishlist
>
> Dear Maintainer,
>
> start-stop-daemon --name=name-longer-than-15-characters fails on Linux,
> because of the 15-character limit on process names.  Other kernels have
> similar but different limits, see the conditionals starting at
> https://anonscm.debian.org/cgit/dpkg/dpkg.git/tree/utils/start-stop-daemon.c#n134
> Looks like executable names longer than 14 characters are incompatible
> with the --name option.  (15 works, but can be mistaken for truncated
> longer names.)  Currently the only solution is overriding do_start_cmd()
> and do_stop_cmd().  Please proide an easier one.

Sorry, I do not understand. You, as init script writer, choose value of
argument to $NAME. Why can't you limit it to required length?
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#916594: [Pkg-mozext-maintainers] Bug#916594: Bug#916594: Bug#916594: Bug#916594: webext-umatrix: Can not load configuration from backup

[Ximin Luo]

Antoine Beaupré:
> [..]
> To reproduce the problem, I do the following:
> 
>  1. uninstall ("remove" in the addons menu) uMatrix
>  2. quit Firefox
>  3. apt install webext-umatrix

Did you do the workaround for 919557 that I mentioned?

>  4. start firefox
>  5. disable and enable the uMatrix extension (otherwise the preferences
> do not show up)
>  6. go in the preferences
>  7. try to import the backup (seem to work but has no effect)
>  8. try to import the "export" (no effect)
> 


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

Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A

[Hans van Kranenburg]

Hi Santiago,

First of all, apologies because the tone in my previous message
yesterday may sound a bit hostile. I was tired and happy that we had a
productive day yesterday, getting ~30 bts closed and an upload with a
lot of fixes done, I just did my own rebuild for stretch-backports, and
then the report that it ftbfs came in, and I was too quick with thinking
"no way, I just built it!". :)

Thanks for your report.

On 2/23/19 7:04 AM, Santiago Vila wrote:
> On Sat, Feb 23, 2019 at 01:15:49AM +0100, Hans van Kranenburg wrote:
> 
>> Can you please help me by formulating a clear problem / question and if
>> possible some expected things that you would like to have as a result?
> 
> Sure. This is a packaging bug in debian/rules. Packages must build for the
> end user with plain "dpkg-buildpackage" but also in the official
> autobuilders by doing "dpkg-buildpackage -A" (to generate arch-all
> packages) or "dpkg-buildpackage -B" (to generate arch-indep packages).

I can indeed reproduce the error by doing dpkg-buildpackage -A:

 >8 
dh_missing --fail-missing
dh_missing: etc/bash_completion.d/xl.sh exists in debian/tmp but is not
installed to anywhere
 >8 

This file is installed into the xen-utils-common package as
/usr/share/bash-completion/completions/xl. From
debian/xen-utils-common.install:

 >8 
#! /usr/bin/dh-exec --with=install

[...]

etc/bash_completion.d/xl.sh => usr/share/bash-completion/completions/xl
 >8 

> Either of those failing is a FTBFS bug, hence the serious severity.
> 
> To reproduce the problem, please try building the package with 
> "dpkg-buildpackage -A", which is exactly what the arch:all
> autobuilder would do if the package was uploaded in source-only form.
> 
> The hint of splitting dh_foo into dh_foo-arch and dh_foo-indep usually
> works for packages that use dh and have this bug, i.e. for packages
> which build ok when built with plain "dpkg-buildpackage" but not with
> "dpkg-buildpackage -A" or "dpkg-buildpackage -B".

All of this seems to be related to the dh-exec usage for putting files
in the xen-utils-common package with a different name. This is the first
time this package is using dh-exec.

If I change the following, dpkg-buildpackage -A completes:

 >8 
diff --git a/debian/xen-utils-common.install
b/debian/xen-utils-common.install
index 60642c9a9c..e83dc0740b 100755
--- a/debian/xen-utils-common.install
+++ b/debian/xen-utils-common.install
@@ -2,7 +2,7 @@

 etc/xen/scripts
 etc/xen/xl*
-etc/bash_completion.d/xl.sh => usr/share/bash-completion/completions/xl
+etc/bash_completion.d/xl.sh usr/share/bash-completion/completions

 etc/default/xendomains
 etc/default/xencommons => /etc/default/xen
 >8 

Interestingly, 'etc/default/xencommons => /etc/default/xen' does not
result in a similar error?

I also found this one, which seems to be related:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831786

Do you have an idea / suggestion how we can deal with this?

Hans

Bug#887988: conflicts are not appropriate

[Bastian Blank]

Control: reopen -1
Control: found -1 0.3.1-1

Conflicts are no appropriate tool to handle conflicts files.  Please fix
that properly.

Bastian

-- 
Change is the essential process of all existence.
-- Spock, "Let That Be Your Last Battlefield", stardate 5730.2

Bug#875135: qgis: Qt5 version available

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 1/14/19 12:25 PM, Bas Couwenberg wrote:
> On 2019-01-14 11:37, Scott Kitterman wrote:
>> qgis is the last package that depends on the Qt4 version of
>> QScintilla2.  It
>> would be nice to be able to drop that for Buster.
>>
>> I notice that qgis 3.4.3 is available as a Qt5 based LTS release.  It
>> would be
>> great to see this in Buster.
> 
> To quote myself in #913065:
> 
> "
>  The qgis package in Debian tracks the LTR releases (in the upstream LTR
>  repo), which doesn't have 3.4 yet.
> 
>  See:
> https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule
> 
> 
>  The 3.4.5 [release] is after the soft-freeze so we may not be able to
> get it into
>  buster, it will find its way into buster-backports eventually.
> "
> 
> Since QGIS 3.4 switches to Qt5 and Python 3, this change is quite
> invasive, we don't have Python 3 support in GRASS yet, so the
> integration in QGIS will likely be broken.

QGIS 3.4.5 has been uploaded to experimental, but will have to pass the
NEW queue.

I forgot to close this issue in the changelog, so I'll have to do that
manually after it's accepted.

Once it is, I'll talk to the release team via an unblock to see if we
can get it into buster before the release, assuming it's accepted in
time for that.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

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

[jEsuSdA 8)]

El 23/2/19 a las 19:05, Andreas Ronnquist escribió:

On Sat, 23 Feb 2019 01:36:27 +0100 jEsuSdA  wrote:

Dear Maintainer,

Geeqie crashes when trying to editing archive preferences.

Once you try to ADD new archive filter, geeqie crashes.



In addition to what I wrote above - Could you please try upgrading your
packages to what is present in testing? I can see see from the version
dependency information in the bug report that some of your packages are
not even up to date with versioning in testing. This might very well
affect package behaviour - and I cannot support some arbitrary mix of
stable with testing (Which your APT policy seem to suggest).

/Andreas
gus...@debian.org



After updating all deps the crash still happening.

Here the debug info:


jesusda@lucas in ~
$ → geeqie

(geeqie:13417): Gtk-CRITICAL **: 20:33:53.539: 
IA__gtk_font_button_set_font_name: assertion 'fontname != NULL' failed


(geeqie:13417): Gtk-CRITICAL **: 20:33:53.548: 
IA__gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL 
(tree_model)' failed

Violación de segmento





jesusda@lucas in ~
$ → gdb geeqie
GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from geeqie...(no debugging symbols found)...done.
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n
Starting program: /usr/bin/geeqie
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7160e700 (LWP 11622)]
[New Thread 0x70e0d700 (LWP 11623)]
[Detaching after fork from child process 11624]
[Detaching after fork from child process 11626]
[Detaching after fork from child process 11628]
[Detaching after fork from child process 11630]
[New Thread 0x7fffe9671700 (LWP 11632)]
[New Thread 0x7fffe8e70700 (LWP 11633)]
[Detaching after fork from child process 11634]
[Detaching after fork from child process 11636]
[Detaching after fork from child process 11638]
[Detaching after fork from child process 11640]
[Thread 0x7fffe8e70700 (LWP 11633) exited]

Thread 1 "geeqie" received signal SIGSEGV, Segmentation fault.
0x5565a432 in ?? ()






Tnanks! ;)

Bug#922261: python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath)

[Carsten Schoenert]

Hi,

On Wed, Feb 13, 2019 at 08:16:36PM +, Santiago Vila wrote:
...
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees   source build/html
> Running Sphinx v1.8.3
> 
> Extension error:
> Could not import extension sphinx.ext.pngmath (exception: No module named 
> pngmath)
> make[2]: *** [Makefile:40: html] Error 2
> make[2]: Leaving directory '/<>/docs'
> make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:13: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 

the fix is rather trivial. The file docs/source/conf.py neededs to be
modified as sphinx.ext.pngmath is now been dropped in favour of
sphinx.ext.imgmath.

Please see attached patch for applying on top the packagig branch.

Regards
Carsten
>From 376ce69f5f4748fd077b13e84243078f86a172b4 Mon Sep 17 00:00:00 2001
From: Carsten Schoenert 
Date: Sat, 23 Feb 2019 20:08:41 +0100
Subject: [PATCH] adding a patch queue to fix FTBFS

added patch:
0001-Fix-FTBFS-with-sphinx-1.8.patch
---
 .../0001-Fix-FTBFS-with-sphinx-1.8.patch  | 23 +++
 debian/patches/series |  1 +
 2 files changed, 24 insertions(+)
 create mode 100644 debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch
 create mode 100644 debian/patches/series

diff --git a/debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch b/debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch
new file mode 100644
index 000..4c3787e
--- /dev/null
+++ b/debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch
@@ -0,0 +1,23 @@
+From: Carsten Schoenert 
+Date: Sat, 23 Feb 2019 19:50:52 +0100
+Subject: Fix-FTBFS-with-sphinx-1.8
+
+sphinx.ext.pngmath has been removed in favor of sphinx.ext.imgmath.
+replace the former with the latter in docs/source/conf.py.
+---
+ docs/source/conf.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/docs/source/conf.py b/docs/source/conf.py
+index 8ec8ee0..c0c7dd5 100644
+--- a/docs/source/conf.py
 b/docs/source/conf.py
+@@ -17,7 +17,7 @@ version = sunlight.__version__
+ # Add any Sphinx extension module names here, as strings. They can be extensions
+ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+ extensions = ['sphinx.ext.autodoc', 'sphinx.ext.intersphinx',
+-'sphinx.ext.todo', 'sphinx.ext.coverage', 'sphinx.ext.pngmath',
++'sphinx.ext.todo', 'sphinx.ext.coverage', 'sphinx.ext.imgmath',
+ 'sphinx.ext.ifconfig', 'sphinx.ext.viewcode']
+ 
+ # Add any paths that contain templates here, relative to this directory.
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..4ef579c
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+0001-Fix-FTBFS-with-sphinx-1.8.patch
-- 
2.20.1

Bug#923050: RFS: pk2/1.2.1-1 [ITP] -- 2D Oldschool platform game where you control a rooster

[wferi]

Hi,

Is the g++ dependency of the main game binary intentional?

I built the game for stretch, it went OK (after reducing the debhelper
compatibility level to 11, but that isn't a problem).  The game starts,
but I'm unable to select a map: the presented list is empty, though
strace shows it finds the /usr/share/games/pk2/data/episodes directory.

Also, it tries to create the config directory in
/usr/share/games/pk2/data, which fails with permission denied.
-- 
Regards,
Feri

Bug#923071: command-not-found issues a warning when /etc/apt/sources.list does not exist

[Nicolas Braud-Santoni]

Package: command-not-found
Version: 18.04.5-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

On my system, /etc/apt/sources.list does not exist (I exclusively use
sources.list.d), causing command-not-found to issue a warning on every run:

> $ command-not-found cowsay
> WARNING:root:could not open file '/etc/apt/sources.list'
> 
> Command 'cowsay' is available in '/usr/games/cowsay'
> cowsay: command not found


Maybe command-not-found should only issue a warning when failing to read
a file due to permissions issues?


Best,

  nicoo

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

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

Versions of packages command-not-found depends on:
ii  apt-file 3.2.2
ii  lsb-release  10.2018112800
ii  python3  3.7.2-1
ii  python3-apt  1.8.3

command-not-found recommends no packages.

Versions of packages command-not-found suggests:
pn  snapd  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlxxoUIRHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MunWQ/+MCdOlUcAgGm1smTWZGwpMqC/aVfWjaZQ
/ic6Vji3I1rCC/V6y9F14QoxG8TT25J3Y8VMAKrq/JFBsKORUToeVcyL8iMch9rU
xP/t1U6K/Cft+sxP1hEFB42ttclUIqSebGazp+WXzSfM/vgjoSRWbexD4+++Nmxr
YyvPC4cNFiclxkddcovyB4UiE/2/2AjL2dIDegN4ALvs0PimM36cfUnTANYwS0gb
seLNQhdP9TJS+vYmhU+YbcHDA3GG9Hm6nDHZ8E+/lGVWpHMvk9z07qDwH7rPnfwL
AlChhGDDjEkciP3b5EB5M24rweX6snvj7dvVkyiyaigK8NDMCx5706/IUVlGRxid
GNdCu64NSLvX6yCl0TiEcDXx6SHYt9U9uk/UYhwFcpfJz91Fb0edBX7FFzLlZ9S6
zIy06xRaMrUrVSTOHc8peZMsae+JoDOcH5J7D6E4Y+TC046hkGln8z5ZbYZjTRBY
Mdc7SiekV+bN81pqsASx+3AtKllz4eV1Q0JPKMOMsJoM+II4T+LHgyCjRHyb+5Cs
vD0cW33cCndoc/x62zkPwBLto3v/S0ccAilnignUf6C2a9NA0ULRAV/TJHPGOxpb
VOdwJxGLbZ/9zHxqKyDeP2GUI2H00gVL8C0XvaaHcaXprRBcThil8t5dvd1det1e
yTQs3ptygXg=
=VdbD
-END PGP SIGNATURE-

Bug#923034: FreeRADIUS status

[Alan DeKok]

  We've been looking for a new Debian maintainer for a while.

  What, exactly, is in "bad shape" about this package?  If there are issues, we 
can work towards fixing them.

  The software is widely used by many tens of thousands of sites.  I hope it's 
not going to be removed from Debian.

  I'll note that Debian also packages "livingston-radius", which hasn't had any 
source changes in 20 years.  There's no mailing list, no support, and it 
doesn't implement any of the modern RADIUS standards.

  Including that package does a disservice to people who install it, and then 
realize it's next to useless.

Bug#923070: eom: can't handle wrong file extensions

[Adam Borowski]

Package: eom
Version: 1.20.2-1+b1
Severity: wishlist

Hi!
Unlike most other programs, eom insists that a file ending in ".jpeg" is
indeed a JPEG, one ending in ".png" is indeed a PNG, etc.  That's the
"proper" way, right.  Alas, with eom's "competition" being more forgiving,
most people don't know the difference and thus mislabelling is rampant.

I see JPEG<->PNG confusion pretty often, and every single time I saw a
webp image (not yet supported by eom), it had a .jpg or .jpeg extension.

Thus, could you please either:
* give the proper image type in error message (rather than just "file is
  corrupted")
* just display the image, without any remark
* mention the error but display the image


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages eom depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  eom-common   1.20.2-1
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-7
ii  libcairo-gobject21.16.0-3
ii  libcairo21.16.0-3
ii  libdbus-1-3  1.12.12-1
ii  libdbus-glib-1-2 0.110-4
ii  libexempi8   2.5.0-2
ii  libexif120.6.21-5.1
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libgirepository-1.0-11.58.3-2
ii  libgl1   1.1.0-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  libmate-desktop-2-17 1.20.4-2
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpeas-1.0-01.22.0-4
ii  librsvg2-2   2.44.10-1
ii  librsvg2-common  2.44.10-1
ii  libstartup-notification0 0.12-6
ii  libx11-6 2:1.6.7-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  mate-desktop-common  1.20.4-2
ii  shared-mime-info 1.10-1
ii  zlib1g   1:1.2.11.dfsg-1

eom recommends no packages.

eom suggests no packages.

-- no debconf information

Bug#920584: fixed in plastex 1.0.0-1

[Andreas Tille]

Hi Stuart,

CCing the old bug report to have some public record of our conversation.

On Sat, Feb 23, 2019 at 10:49:24AM +1100, Stuart Prescott wrote:
> Please reread 
> 
>   https://release.debian.org/buster/freeze_policy.html
> 
> Particularly the bit about "small targeted fixes".

I admit I was aware that I was violating that part.  I was hunting for
packages with testing removal warning and stumbled upon de-facto
orphaned plastex.  Version 1.0.0 which is also quite aged seemed like a
candidate where this upgrade does not harm.  Its a real pity that I was
wrong with my estimation and I agree that I should not have done this.
 
> On Friday, 22 February 2019 13:20:03 AEDT Andreas Tille wrote:
> > Source: plastex
> > Source-Version: 1.0.0-1
> [...]
> 
> We're in the freeze, why are you uploading new upstream releases without 
> looking very carefully at the changes they bring and checking that they do 
> not 
> break rdeps? pyxplot now FTBFS with this version of plastex :(

After we now agreed that I did a mistake which I regret what do you
think is the best option to fix it.  I see:

   1. Revert the version bump by adding an epoch.
   2. Adapt pyxplot to new version
   3. Go with the docs that do not need plastex which seems to
  be fragile anyway and since it is not ported to Python3 will
  be droped with Buster+1 anyway.  Looking at popcon[1] the usage
  of the docs is not impressive and its available online as well
   4. Any other suggestion?

Please decide what would be your prefered choice and I'll help
implementing it.

Sorry for the trouble

 Andreas.


[1] 
https://qa.debian.org/popcon-graph.php?packages=pyxplot+pyxplot-doc_vote=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1

-- 
http://fam-tille.de

Bug#923069: eom: please support webp images

[Adam Borowski]

Package: eom
Version: 1.20.2-1+b1
Severity: wishlist

Hi!
I'm afraid that a lot of webpages these days serve images as webp, either as
runtime-chosen alternatives (to support MSIE) or even as the only version.

EOM can't display those.


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

Kernel: Linux 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages eom depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  eom-common   1.20.2-1
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-7
ii  libcairo-gobject21.16.0-3
ii  libcairo21.16.0-3
ii  libdbus-1-3  1.12.12-1
ii  libdbus-glib-1-2 0.110-4
ii  libexempi8   2.5.0-2
ii  libexif120.6.21-5.1
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libgirepository-1.0-11.58.3-2
ii  libgl1   1.1.0-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  libmate-desktop-2-17 1.20.4-2
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpeas-1.0-01.22.0-4
ii  librsvg2-2   2.44.10-1
ii  librsvg2-common  2.44.10-1
ii  libstartup-notification0 0.12-6
ii  libx11-6 2:1.6.7-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  mate-desktop-common  1.20.4-2
ii  shared-mime-info 1.10-1
ii  zlib1g   1:1.2.11.dfsg-1

eom recommends no packages.

eom suggests no packages.

-- no debconf information

Bug#916594: [Pkg-mozext-maintainers] Bug#916594: Bug#916594: Bug#916594: webext-umatrix: Can not load configuration from backup

[Antoine Beaupré]

On 2019-02-23 19:11:00, Ximin Luo wrote:
> Control: tags -1 + moreinfo unreproducible
>
> Antoine Beaupré:
>> [..]
>> 
>>> Actually I just tried the latest version and restore seems to be working 
>>> correctly. I must have been confused when dealing with all these multiple 
>>> bug reports or something. Please re-open if it doesn't work for you. Note 
>>> that you might need to work around bug 919557 first - either by using 
>>> firefox-esr, or doing `sudo rm /usr/share/webext/umatrix/lib/punycode.js && 
>>> sudo cp /usr/share/javascript/punycode/punycode.js 
>>> /usr/share/webext/umatrix/lib/punycode.js`.
>> 
>> Are you sure this is the same bug?
>> 
>> Here if I follow those instructions in buster with 1.3.16, the bug still
>> occurs, so I don't believe this is strictly related to #919557.
>
> I can't reproduce it. Can you give more details?

I'm not sure how, but let's see.

I've got Firefox ESR 60.5 runnin in Debian buster:

firefox-esr:
  Installé : 60.5.0esr-1
  Candidat : 60.5.0esr-1
 Table de version :
 60.5.1esr-1 501
  1 https://deb.debian.org/debian sid/main amd64 Packages
 *** 60.5.0esr-1 502
500 https://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
firefox:
  Installé : (aucun)
  Candidat : 65.0.1-1
 Table de version :
 65.0.1-1 1
  1 https://deb.debian.org/debian sid/main amd64 Packages

I have uMatrix 1.3.16 running from addons.mozilla.org with a lengthy
list of rules. It works correctly: export/import work, so does
backup/restore.

I have a somewhat heavily customized Firefox configuration as well, but
I'm not sure which specific config could affect the debian package (as
opposed to the app).

To reproduce the problem, I do the following:

 1. uninstall ("remove" in the addons menu) uMatrix
 2. quit Firefox
 3. apt install webext-umatrix
 4. start firefox
 5. disable and enable the uMatrix extension (otherwise the preferences
do not show up)
 6. go in the preferences
 7. try to import the backup (seem to work but has no effect)
 8. try to import the "export" (no effect)

Let me know if you need more information.

A.

-- 
Never underestimate the bandwidth of a station wagon full of tapes
hurtling down the highway.
- Andrew S. Tanenbaum, "Computer Networks"

Bug#923068: pinentry-gtk2 takes more than twenty seconds to appear

[fc]

Package: pinentry-gtk2
Version: 1.1.0-1+b1
Severity: important

When pinentry-gtk2 is started, the input window appears after more than
twenty seconds. For comparison pinentry-gnome3 and pinentry-qt appear in less 
than two
seconds for the same request.

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

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

Versions of packages pinentry-gtk2 depends on:
ii  libassuan0 2.5.2-1
ii  libc6  2.28-6
ii  libglib2.0-0   2.58.3-1
ii  libgpg-error0  1.35-1
ii  libgtk2.0-02.24.32-3
ii  libncursesw6   6.1+20181013-1
ii  libsecret-1-0  0.18.7-1
ii  libtinfo6  6.1+20181013-1

pinentry-gtk2 recommends no packages.

Versions of packages pinentry-gtk2 suggests:
pn  pinentry-doc  

-- no debconf information

Bug#916594: [Pkg-mozext-maintainers] Bug#916594: Bug#916594: Bug#916594: webext-umatrix: Can not load configuration from backup

[Ximin Luo]

Control: tags -1 + moreinfo unreproducible

Antoine Beaupré:
> [..]
> 
>> Actually I just tried the latest version and restore seems to be working 
>> correctly. I must have been confused when dealing with all these multiple 
>> bug reports or something. Please re-open if it doesn't work for you. Note 
>> that you might need to work around bug 919557 first - either by using 
>> firefox-esr, or doing `sudo rm /usr/share/webext/umatrix/lib/punycode.js && 
>> sudo cp /usr/share/javascript/punycode/punycode.js 
>> /usr/share/webext/umatrix/lib/punycode.js`.
> 
> Are you sure this is the same bug?
> 
> Here if I follow those instructions in buster with 1.3.16, the bug still
> occurs, so I don't believe this is strictly related to #919557.
> 

I can't reproduce it. Can you give more details?

X

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

Bug#923067: libc0.1: missing UTIME_OMIT for utimensat(2) and futimens(2)

[Thorsten Glaser]

Package: libc0.1
Version: 2.25-2
Severity: normal

glibc on Debian GNU/kFreeBSD is missing UTIME_OMIT, making src:pax
FTBFS. While I could work around this by using the older functions,
https://www.freebsd.org/cgi/man.cgi?query=utimensat indicates that
the FreeBSD kernel has gained native support for that in 10.3, which
incidentally is the version in Debian.

So, please add that to the headers, then give-back src:pax on both
kfreebsd architectures.

Thanks!

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

Kernel: kFreeBSD 10.3-0-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libc0.1 depends on:
ii  libgcc1  1:8.2.0-21

libc0.1 recommends no packages.

Versions of packages libc0.1 suggests:
ii  debconf [debconf-2.0]  1.5.70
pn  glibc-doc  
ii  libc-l10n  2.25-2
ii  locales2.25-2

-- debconf information:
  glibc/disable-screensaver:
  glibc/restart-services:
  glibc/kernel-too-old:
  glibc/kernel-not-supported:
* libraries/restart-without-asking: false
  glibc/upgrade: true
  glibc/restart-failed:

Bug#923066: [INTL:da] Danish translation of the debconf templates postfix

[Joe Dalton]

Package: postfix
Severity: wishlist
Tags: l10n patch

Please include the attached Danish postfix debconf po file.

joe@debianbuster:~/over/debian/postfix$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 76 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923065: [INTL:da] Danish translation of the debconf templates mysql-5.7

[Joe Dalton]

Package: mysql-5.7
Severity: wishlist
Tags: l10n patch

Please include the attached Danish mysql-5.7 debconf po file.

joe@debianbuster:~/over/debian/mysql-5.7$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 19 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#906258: stretch-pu: package yubico-piv-tool/1.4.2-2

[Nicolas Braud-Santoni]

On Sat, Feb 23, 2019 at 02:27:04PM +0100, Nicolas Braud-Santoni wrote:
> On Fri, Feb 15, 2019 at 04:55:58PM +0100, Nicolas Braud-Santoni wrote:
> > On Wed, Feb 13, 2019 at 03:34:50PM +0100, Nicolas Braud-Santoni wrote:
> > > I assume I can't just dput this, as it already exists in stable-new.
> > > Could you reject the existing package first, and I will reupload?
> > 
> > Uploaded a new revision at the request of jcristau.
> 
> Ping?

Nevermind, ftpmaster rejected the upload:

On Sat, Feb 23, 2019 at 05:47:07PM +, Debian FTP Masters wrote:
> yubico-piv-tool - inappropriate changelog entry


Dear ftpmasters, could you clarify in which way the changelog entry is
inappropriate, and what would be an appropriate changelog entry?


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#923001: error message on start

[W. Martin Borgert]

(I write this mainly to document the bug.
It's certainly not worth to invest much time on it.)

On 2019-02-23 12:18, Michael Gilbert wrote:
> This seems related to this upstream issue.  Buggy extensions can cause
> this.  You could try removing extensions one at a time to determine
> which one causes this.

I don't think I have any extensions installed:

$ dpkg --get-selections webext-\*
$

Still, under chrome://extensions/, I see three extensions:

 - Chromium PDF Viewer
 - CryptoTokenExtension
 - GNOME Shell integration

The first two have a "Remove" button, but pressing such a button
does not have any other effect than flashing the button. It does
not remove the extension.

As I wrote before, I experience this is with a newly created
user account, so there shouldn't be any messed config.

Bug#923064: [INTL:da] Danish translation of the debconf templates wireshark

[Joe Dalton]

Package: wireshark
Severity: wishlist
Tags: l10n patch

Please include the attached Danish wireshark debconf po file.

joe@debianbuster:~/over/debian/wireshark$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 16 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#376925: initramfs-tools: init should say 'Will now load...'!

[Ben Hutchings]

Control: severity -1 wishlist
Control: tag -1 wontfix

On Thu, 21 Feb 2019 17:54:57 + Dmitry Bogatov  wrote:
> 
> control: reassign -1 initramfs-tools
> 
> Not sure, whether this issue is still present in initramfs-tools, but
> initscripts /do/ say 'Will now', so bug do not apply to initscripts.
> Reassigning.

This message no longer appears when the "quiet" parameter is present
(default behaviour when using GRUB).  I don't intend to remove it
completely.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates




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

Bug#923063: [INTL:da] Danish translation of the debconf templates apt-listchanges

[Joe Dalton]

Package: apt-listchanges
Severity: wishlist
Tags: l10n patch

Please include the attached Danish apt-listchanges debconf po file.

joe@debianbuster:~/over/debian/apt-listchanges$ msgfmt --statistics -c -v -o 
/dev/null da.po
da.po: 38 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#923062: libpam-ccreds misbuilds during cross: build/host confusion for libdir

[Helmut Grohne]

Source: libpam-ccreds
Version: 10-7
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libpam-ccreds successfully cross builds a broken package. It uses the
build architecture libdir when it should be using the host architecture
one. The attached patch fixes that. Please consider applying it.

Helmut
diff --minimal -Nru libpam-ccreds-10/debian/changelog 
libpam-ccreds-10/debian/changelog
--- libpam-ccreds-10/debian/changelog   2018-11-02 12:52:36.0 +0100
+++ libpam-ccreds-10/debian/changelog   2019-02-23 19:41:00.0 +0100
@@ -1,3 +1,10 @@
+libpam-ccreds (10-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build/host confusion in libdir. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 23 Feb 2019 19:41:00 +0100
+
 libpam-ccreds (10-7) unstable; urgency=medium
 
   [ Guido Günther ]
diff --minimal -Nru libpam-ccreds-10/debian/rules libpam-ccreds-10/debian/rules
--- libpam-ccreds-10/debian/rules   2018-11-02 12:32:11.0 +0100
+++ libpam-ccreds-10/debian/rules   2019-02-23 19:40:57.0 +0100
@@ -1,9 +1,10 @@
 #!/usr/bin/make -f
 
+include /usr/share/dpkg/architecture.mk
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 DEB_CONFIGURE_EXTRA_ARGS := \
-   --libdir=/lib/$(DEB_BUILD_GNU_TYPE) \
+   --libdir=/lib/$(DEB_HOST_GNU_TYPE) \
--sbindir=/sbin \
--enable-gcrypt \
$(NULL)

Bug#923061: [INTL:da] Danish translation of the debconf templates tzdata

[Joe Dalton]

Package: tzdata
Severity: wishlist
Tags: l10n patch

Please include the attached Danish tzdata debconf po file.

joe@debianbuster:~/over/debian/tzdata$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 476 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip