Bug#915694: [Pkg-clamav-devel] Bug#915694: RFS: clamav-unofficial-sigs/5.6.2

[Brent Clark]

Good day Scott.

As per your request, its done.

Please can your check.
Regards
Brent

On 2018/12/07 15:52, Scott Kitterman wrote:

Yes.  You'll need to do that.

Scott K

On Friday, December 07, 2018 10:25:40 AM Brent Clark wrote:

Good day Scott and Paul

Thanks so much for looking at my RFS.

Sorry for not communicating that in the changelog.
Do you guys want that in the changelog?

Regards
Brent

On 2018/12/07 09:18, Paul Wise wrote:

On Fri, Dec 7, 2018 at 3:12 PM Scott Kitterman wrote:

This package currently has Paul Wise listed as a co-maintainer, but
you've
removed him.  Did you coordinate that with him?  In any case, the change
needs to be documented in debian/changelog.


He did, see the bug closed in debian/changelog.

Bug#916100: Please updated Italian PO translation for the package deborphan

[Alessandro De Zorzi]

Package: deborphan
Severity: wishlist

Updated italian translation.

cheers
Alessandro


-- 
http://escalibur.eu
il tuo diario di arrampicata on-line: è divertente!
# Italian translation of deborphan.
# Copyright (C) 2008 THE deborphan'S COPYRIGHT HOLDER
# This file is distributed under the same license as the deborphan package.
# Alessandro De Zorzi , 2008.
#
msgid ""
msgstr ""
"Project-Id-Version: 1.7.28\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-25 17:33+\n"
"PO-Revision-Date: 2018-12-10 08:35+0100\n"
"Last-Translator: Alessandro De Zorzi \n"
"Language-Team: debian-l10n-ital...@lists.debian.org\n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: src/exit.c:52
#, c-format
msgid ""
"\n"
"The following options are available:\n"
msgstr ""
"\n"
"Sono disponibili le seguenti opzioni:\n"

#: src/exit.c:55
#, c-format
msgid "-hThis help.\n"
msgstr "-hQuesto help.\n"

#: src/exit.c:58
#, c-format
msgid "-f FILE   Use FILE as statusfile.\n"
msgstr "-f FILE   Usa FILE come \"statusfile\".\n"

#: src/exit.c:61
#, c-format
msgid "-vVersion information.\n"
msgstr "-vInformazioni sulla versione.\n"

#: src/exit.c:65
#, c-format
msgid "-dShow dependencies for packages that have them.\n"
msgstr "-dVisualizza i pacchetti che dipendono da.\n"

#: src/exit.c:68
#, c-format
msgid "-PShow priority of packages found.\n"
msgstr "-PMostra la priorità dei pacchetti trovati.\n"

#: src/exit.c:71
#, c-format
msgid "-sShow the sections the packages are in.\n"
msgstr ""
"-sMostra le sezioni alle quali il pacchetto\n"
"appartiene.\n"

#: src/exit.c:73
#, c-format
msgid "--no-show-section   Do not show sections.\n"
msgstr "--no-show-section   Non mostra le sezioni.\n"

#: src/exit.c:76
#, c-format
msgid "-zShow installed size of packages found.\n"
msgstr "-zMostra la dimensione su disco dei pacchetti trovati.\n"

#: src/exit.c:80
#, c-format
msgid "-aCompare all packages, not just libs.\n"
msgstr "-aConfronta tutti i pacchetti, non solo le librerie.\n"

#: src/exit.c:83
#, c-format
msgid "-e LIST   Work as if packages in LIST were not installed.\n"
msgstr "-e LIST   Come se i pacchetti in LIST non fossero installati.\n"

#: src/exit.c:86
#, c-format
msgid "-HIgnore hold flags.\n"
msgstr "-HIgnora il flag \"hold\".\n"

#: src/exit.c:89
#, c-format
msgid "Disable checks for `recommends'.\n"
msgstr "Disabilita check per `raccomanda'.\n"

#: src/exit.c:91
#, c-format
msgid "Disable checks for `suggests'.\n"
msgstr "Disabilita check per `suggerisce'.\n"

#: src/exit.c:94
#, c-format
msgid "-nDisable checks for `recommends' and `suggests'.\n"
msgstr "-nDisabilita check per `raccomanda' e `suggerisce'.\n"

#: src/exit.c:97
#, c-format
msgid "-p PRIOR  Select only packages with priority >= PRIOR.\n"
msgstr "-p PRIOR  Seleziona solo i pacchetti con priorità >= PRIOR.\n"

#: src/exit.c:100
#, c-format
msgid "--find-config   Find \"orphaned\" configuration files.\n"
msgstr "--find-config\t\tCerca file di configurazione \"orfani\".\n"

#: src/exit.c:104
msgid "--libdevel  Also search in section \"libdevel\".\n"
msgstr ""
"--libdevel  Cerca anche nella sezione libdevel.\n"

#: src/exit.c:108
#, c-format
msgid "-A PKGS.. Never report PKGS.\n"
msgstr "-A PKGS.. Non elenca i PKGS.\n"

#: src/exit.c:111
#, c-format
msgid "-k FILE   Use FILE to get/store info about kept packages.\n"
msgstr "-k FILE   Usa FILE per gestire l'elenco dei pacchetti kept\n"

#: src/exit.c:114
#, c-format
msgid "-LList the packages that are never reported.\n"
msgstr "-LMostra i pacchetti che sono esclusi dalla ricerca.\n"

#: src/exit.c:117
#, c-format
msgid "-R PKGS.. Remove PKGS from the \"keep\" file.\n"
msgstr "-R PKGS.. Elimina PKGS dal file \"keep\".\n"

#: src/exit.c:120
#, c-format
msgid "-ZRemove all packages from the \"keep\" file.\n"
msgstr "-ZElimina tutti i pacchetti dal file keep.\n"

#: src/exit.c:124
#, c-format
msgid "--df-keep   Read debfoster's \"keepers\" file.\n"
msgstr "--df-keep   Legge il file \"keepers\" di debfoster.\n"

#: src/exit.c:126
#, c-format
msgid "--no-df-keepDo not read debfoster's \"keepers\" file.\n"
msgstr "--no-df-keepIgnora il file \"keepers\" di debfoster.\n"

#: src/exit.c:132
#, c-format
msgid "--guess-common  Try to report common packages.\n"
msgstr ""
"--guess-common  Tenta di elencare i pacchetti \"common\".\n"

#: src/exit.c:133
#, c-format
msgid "--guess-dataTry to report data packages.\n"
msgstr "--guess-dataTenta di elencare i pacchetti \"data\".\n"

#: src/exit.c:135
#, c-format
msgid "--guess-debug   Try to report debugging 

Bug#912285: mtools: New upstream release

[Chris Lamb]

Chris Lamb wrote:

> Ping? 4.0.22 was just released.

And now 4.0.23! :)


Regards,

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

Bug#916099: RFS: biometric-authentication/0.9.61-2 [RC]

[handsome_feng]

Package: sponsorship-requests
Severity: important

  Dear mentors,

  I am looking for a sponsor for my package "biometric-authentication"

 * Package name: biometric-authentication
   Version : 0.9.61-2
   Upstream Author : Jiang Linxuan (droiing) 
 * URL : https://github.com/ukui/biometric-authentication
 * License : LGPL-3.0
   Section : admin

  It builds those binary packages:

biometric-auth - Biometric Authentication Service
biometric-driver-community-multidevice - Biometric Authentication   Driver
(community multidevice)
biometric-utils - Biometric authentication utils
libbiometric-dev - Biometric Identification DRIVER API - development files
libbiometric0 - Biometric Identification library

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

  https://mentors.debian.net/package/biometric-authentication


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

dget -x https://mentors.debian.net/debian/pool/main/b/biometric-
authentication/biometric-authentication_0.9.61-2.dsc

  More information about biometric-authentication can be obtained from
https://github.com/ukui/biometric-authentication

  Changes since the last upload:

* Change the configuration file to the configuration template file
- Rename biometric-drivers.conf to biometric-drivers.conf.template
- The default configuration template file is installed to
  /usr/share/biometric-auth/
  (Closes: #914764)

  Regards,
   handsome_feng



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

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

Bug#915299: Bug #915299: xfburn: Segfault when adding files to project

[Wojciech Muła]

Hi Bernhard!

Thank you very much for looking at this issue.
The outdated versions of libs are the most likely
cause of segfault, so I propose to close the bug.

I'll back to this when I do whole-system upgrade.

BTW, the gdb backtrace I posted are the only lines
printed by gdb. :)

best regards
Wojciech


W dniu 2018-12-05 11:27:05 użytkownik Bernhard Übelacker 
 napisał:
> Hello Wojciech Muła,
> I am just trying to reproduce the crash inside a minimal
> buster amd64 qemu VM.
> 
> Unfortunately I was not able to reproduce and found most of
> the listed versions are already outdated in testing.
> 
> Is there a reason, why your debian unstable installation
> is not receiving updates?
> 
> Another point would be, you copied just the first frame of
> gdb's bt output, but there should have been more lines following?
> 
> And such a backtrace would be even better if the matching dbgsym
> packages are installed like described in [1]. In your example that
> would be at least xfburn-dbgsym libglib2.0-0-dbgsym.
> (But I guess if you currently do not install updates on purpose
> that would pull in new versions of the libraries.)
> 
> Kind regards,
> Bernhard
> 
> 
> [1] https://wiki.debian.org/HowToGetABacktrace
> 
> 
> # dpkg -S /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> libglib2.0-0:amd64: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> 

Bug#882141: Problem still happening even after upgrade

[Scott Kitterman]

On Tue, 06 Nov 2018 19:47:34 -0500 Scott Kitterman  
wrote:
> Would someone who is still having this problem please try the attached 
> configure-instance.sh in place of the installed version in /usr/lib/postfix?
> 
> This one avoids postmulti in every case and might actually work, but I have
> a hard time testing it.
> 
> Scott K

OK, tested it as best I could and we'll see if it works.

Scott K

Bug#916098: ITP: kubetail -- Aggregate logs from multiple Kubernetes pods into one stream

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: ChangZhuo Chen (陳昌倬) 

* Package name: kubetail
  Version : 1.6.5
  Upstream Author : Johan Haleby, et al.
* URL : https://github.com/johanhaleby/kubetail
* License : Apache 2.0
  Programming Lang: bash
  Description : Aggregate logs from multiple Kubernetes pods into one stream

 Bash script that enables you to aggregate (tail/follow) logs from
 multiple Kubernetes pods into one stream. This is the same as running
 "kubectl logs -f " but for multiple pods.



-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#916087: lintian: "exec failed: Text file busy" when running tests by tag

[Felix Lechner]

Chris,

> I think your recent commits have introduced a regression in the test
> harness:

I am stumped. If you urgently require the tag functionality (I know
you use it often), please reverse !88 and !82, in that order. I do
have a better fix on the way, however, and would appreciate a day to
make sure it is error-free.

Bug#916097: RFP: node-gulp-print -- gulp plugin that prints names of files

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-gulp-print
  Version : 5.0.0
  Upstream Author : Alex Gorbatchev 
* URL : https://notabug.org/makenotabuggreatagain/gulp-print
* License : MIT
  Programming Lang: javascript
  Description : gulp plugin that prints names of files

This is a very basic gulp plugin that prints names of files. 
It's useful as a debugging tool to see which files are moving 
through the pipe or as a status printout.

It is a dependency of node-semantic-ui ( #915062 )

Bug#916096: smplayer FTCBFS: uses the build architecture qmake

[Helmut Grohne]

Source: smplayer
Version: 18.5.0~ds1-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

smplayer fails to cross build from source, because it uses the build
architecture qmake. The attached patch makes it use a cross qmake for
cross compilation. Furthermore, it needs to Build-Depends:
qt5-qmake:native in order to use lrelease. Please consider applying the
patch.

Helmut
diff --minimal -Nru smplayer-18.5.0~ds1/debian/changelog 
smplayer-18.5.0~ds1/debian/changelog
--- smplayer-18.5.0~ds1/debian/changelog2018-06-19 19:58:18.0 
+0200
+++ smplayer-18.5.0~ds1/debian/changelog2018-12-10 05:58:23.0 
+0100
@@ -1,3 +1,12 @@
+smplayer (18.5.0~ds1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass a cross qmake along.
++ Missing Build-Depends: qt5-qmake:native for lrelease.
+
+ -- Helmut Grohne   Mon, 10 Dec 2018 05:58:23 +0100
+
 smplayer (18.5.0~ds1-2) unstable; urgency=medium
 
   * Disable downloading potentially insecure javascript from youtube.com
diff --minimal -Nru smplayer-18.5.0~ds1/debian/control 
smplayer-18.5.0~ds1/debian/control
--- smplayer-18.5.0~ds1/debian/control  2018-06-19 19:58:18.0 +0200
+++ smplayer-18.5.0~ds1/debian/control  2018-12-10 05:58:21.0 +0100
@@ -10,6 +10,7 @@
  qtbase5-dev (>= 5.1),
  qtbase5-private-dev,
  qt5-qmake,
+ qt5-qmake:native,
  qtscript5-dev,
  qttools5-dev-tools,
  zlib1g-dev
diff --minimal -Nru smplayer-18.5.0~ds1/debian/rules 
smplayer-18.5.0~ds1/debian/rules
--- smplayer-18.5.0~ds1/debian/rules2018-06-19 19:58:18.0 +0200
+++ smplayer-18.5.0~ds1/debian/rules2018-12-10 05:58:06.0 +0100
@@ -6,8 +6,15 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+include /usr/share/dpkg/architecture.mk
+
+ifeq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+QMAKE=qmake
+else
+QMAKE=$(DEB_HOST_GNU_TYPE)-qmake
+endif
 QMAKE_OPTS = DEFINES+=NO_DEBUG_ON_CONSOLE DEFINES-=MPLAYER2_SUPPORT
-MAKE_OPTS  = PREFIX=/usr QMAKE=qmake LRELEASE=lrelease 
QMAKE_OPTS="$(QMAKE_OPTS)"
+MAKE_OPTS  = PREFIX=/usr QMAKE=$(QMAKE) LRELEASE=lrelease 
QMAKE_OPTS="$(QMAKE_OPTS)"
 
 
 %:

Bug#915074: Sponsor my "PK2 (Pekka Kana 2)" package

[Carlos Donizete Froes]

Hi Tobias,

> As you are recorded as upstream:
> Why did you fork from https://github.com/danilolc/pk2?

No, this project has been extracted from the official developer site[1].

[1] http://pistegamez.net/PK2

Where it was being modified, correcting bugs and implementing some solutions
where mentioned about the SDL and SDL2 library ported by Samuli Tuomola[2] and
Danilo Lemos[3].

[2] https://github.com/stt/pk2

[3] https://github.com/danilolc/pk2

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - 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#915136: Follow-up

[Pirate Praveen]

Control: severity -1 important 

On Wed, 5 Dec 2018 13:16:29 +0100 
=?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?=  
wrote:
> There's any new data about this bug?

Since I can't reproduce it in multiple systems, I'm reducing the severity. Did 
you try 11.4.9?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#906536: Fwd: Re: Cave Story in Debian and Ubuntu Linux Officially

[Carlos Donizete Froes]

Hi,

Follow what I said with the game developer. I'm waiting for an answer
for this case.

Thanks!

 Original Message 
Subject: Re: Cave Story in Debian and Ubuntu Linux Officially
Date: 05-12-2018 01:14
From: Pixel 
To: Carlos Donizete Froes 

I tell it, too.
Thank you.

2018年12月4日(火) 23:21 Carlos Donizete Froes :
>
> Hi Pixel,
>
> Please show Nicalis the comments on the Debian bugs:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894865
>
> Thank you!
>
>
> On 04-12-2018 06:20, Pixel wrote:
> > I'll ask Nicalis about it.
> > 2018年12月1日(土) 15:25 Carlos Donizete Froes :
> >>
> >> Hi,
> >>
> >> I would like to upload the Cave Story game to the Debian GNU/Linux 
> >> project[1].
> >>
> >> [1] https://gitlab.com/coringao/cavestory-nx
> >>
> >> Does the game's author have a license that allows us to contribute to 
> >> distribute
> >> the files or could add a warning with this permission[2]?
> >>
> >> [2] https://www.cavestory.org/download/cave-story.php
> >>
> >> Thanks!

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

Bug#912063: preliminary building package

[Jeffrey Cliff]

the abovementioned repository has a preliminary building package now
hopefully this helps
Jeff Cliff

Bug#916095: lintian: False positive: license-problem-gfdl-invariants

[Dmitry Bogatov]

Package: lintian
Version: 2.5.116
Severity: normal

Dear Maintainer, here is excerpt from cflow.texi (GNU cflow 1.5)

Published by the Free Software Foundation,
51 Franklin Street, Fifth Floor
Boston, MA 02110-1301, USA

Copyright @copyright{} 2005, 2010, 2014-2016 Sergey Poznyakoff

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover and Back-Cover texts.  A copy of 
the license is included in the section entitled ``GNU Free 
Documentation 
License''.

It have neither cover texts, nor invariant sections, but still flagged
by lintian as error.

Bug#916094: RFP: node-gulp-notify -- send messages based on Vinyl Files or Errors using node-notifier

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-gulp-notify
  Version : 3.2.0
  Upstream Author : Mikael Brevik 
* URL : https://notabug.org/makenotabuggreatagain/gulp-notify/
* License : MIT
  Programming Lang: javascript
  Description : send messages based on Vinyl Files or Errors using 
node-notifier

Can also specify custom notifier an be used as a jshint reporter.

node-gulp-notify is a prerequisite of node-semantic-ui ( #915062 )

Bug#910479: hpanel: Sometimes busy and unresponsive

[Paul Szabo]

This problem seems to be solved by using the patch below.

Cheers, Paul
-- 
Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia
Description: Avoid busy
  Seems hpanel is sometimes busy and non-responsive:
https://bugs.debian.org/910479
  Maybe because we sometimes delete task twice, and/or re-use
  variable after it has been (deleted and) free-d, and/or
  because we delete task only to be re-added straight away.
  Do not do those things, respect dontdel setting.

Author: Paul Szabo 

Bug-Debian: https://bugs.debian.org/910479
Forwarded: no
Last-Update: 2018-11-25

--- hpanel-0.3.2.orig/hpanel.c
+++ hpanel-0.3.2/hpanel.c
@@ -938,30 +938,27 @@
 	list = tb.task_list;
 	while (list)
 	{
 		list->focused = (focus_win == list->win);
 		next = list->next;
 
 		if (!new_desk)
 			for (i = num - 1; i >= 0; i--)
 if (list->win == win[i])
 	goto dontdel;
 		del_task (list->win);
 dontdel:
-	
-	
-	if (tb.my_desktop != find_desktop (list->win) || is_hidden (list->win)) 
-		del_task( list->win);
 
-	
+/*	if (tb.my_desktop != find_desktop (list->win) || is_hidden (list->win)) */
+/*		del_task( list->win); */
 
 		list = next;
 	}
 
 	/* add any new windows */
 	for (i = 0; i < num; i++)
 	{
 		if (!find_task (win[i]))
 			add_task (win[i], (win[i] == focus_win));
 	}
 
 	XFree (win);

Bug#916093: netinst amd64-i386.iso buster dvd fails to find kernel for Mac Pro 1,1 with i386 target

[David George Henderson III]

Package: d-i.debian.org
Severity: important

The dvd is dated 12/3/2018. Its the dvd that mounts with the volume
label: /debian-testing-amd64-i386-netinst.iso

Installing for the i386 target on a Mac Pro 1,1 produces the error message:

"No installable kernel was found in the defined APT sources."

What I have done to get around this bug is to install a previous release, then 
perform dist-upgrade

Bug#916092: nullmailer: architecture specific test failures

[David Bremner]

Package: nullmailer
Version: 1:2.2-1
Severity: serious
Tags: upstream
Justification: ftbfs

nullmailer 2.2 should not transition to testing until we figure out what is 
going on with the test 

   Testing auth permanent failure with smtp

which seems to fail or hang on various architectures (but not amd64).

It seems possible replicate the hang on plummer (ppc64el
porterbox). This is a bit puzzling because on the pps64el buildd it
actually failed relatively quickly, rather than hanging until killed.

The test is using some tcp sockets on localhost according to netstat,
the connection is ESTABLISHED, but that's all I know at this point.


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

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

Versions of packages nullmailer depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.27-8
ii  libgnutls303.5.19-1+b1
ii  libstdc++6 8.2.0-9
ii  lsb-base   10.2018112800

nullmailer recommends no packages.

nullmailer suggests no packages.

-- debconf information excluded

Bug#915496: kio-gdrive: missing translations [was Bug#915242: RFS: kio-gdrive/1.2.5-1]

[Nicholas D Steeves]

Alternatively I could diff the existing orig tarball against the one
upstream intended for release, carry it as a temporary quilt patch,
and that could become 1.2.5-2.


signature.asc
Description: PGP signature

Bug#915537: MongoDB SSPL v1 license and the DFSG

[Hideki Yamane]

Hi,

On Wed, 05 Dec 2018 04:44:39 -0500 "Chris Lamb "  wrote:
> As you have discovered, it is difficult to point towards a clear-cut
> violation of the DFSG that we could all agree on due to both legal and
> language fuzziness. However, even if we could, there is always a
> slight tendency to treat the DFSG (and the Open Source Definition more
> generally) as a of narrowly-interpretable checklist.
> 
> However, the SSPL is clearly not in the sprit of the DFSG, yet alone
> complimentary to the Debian's goals of promoting software or user
> freedom.

 Could you explain it a bit more, please? Why SSPL doesn't meet our
 goal? I don't complain about this judge but more detailed explanation
 with some examples is better, IMHO.


-- 
Hideki Yamane 

Bug#915287: Bug#900160 closed by Dimitri John Ledkov (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.2)

[Dimitri John Ledkov]

close 915287 1.0.7-4.2
thanks

On Thu, 6 Dec 2018 14:05:22 +0100 Sebastian Andrzej Siewior
 wrote:
> On 2018-12-06 12:42:50 [+0100], gregor herrmann wrote:
> > On Wed, 05 Dec 2018 13:57:05 +, Debian Bug Tracking System wrote:
> >
> > >  ruby-eventmachine (1.0.7-4.2) unstable; urgency=medium
> > >  .
> > >* Non-maintainer upload.
> > >* Revert below upload and build with OpenSSL 1.1+.
> > >* Add a patch to clamp SSL version to TLS1.2, and allow using small
> > >  keys, as the rest of the codebase is not ready for TLS1.3. (Closes:
> > >  #900160)
> >
> > I guess this should have closes the cloned #915287 and not the
> > original #900160?
>
> I think so, too.
>

Yes!

Hopefully, I got my control commands right!

Bug#916091: ITP: python3-stringcase -- Python library to Convert string cases between camel case, pascal case, snake case etc…

[Jade McCormick]

Package: wnpp
Severity: wishlist
Owner: Jade McCormick 

* Package name: python3-stringcase
  Version : 1.2.0
  Upstream Author : Taka Okunishi (https://github.com/okunishinishi)
* URL : https://pypi.org/project/stringcase/
* License : MIT
  Programming Lang: Python
  Description : Python library to Convert string cases between camel case, 
pascal case, snake case etc...

This python library provides many methods to convert between various
case forms (camel case, pascal case, etc) and is useful to provide
consistency in casing - fewer bugs, etc.

I use this package for casing system names (i_am_a_name) for web
applications (I am a name).

I need a sponsor for this package.

Bug#916012:

[J. Smith]

See https://debbugs.gnu.org/30045 and similar.
    

Bug#915808: Current dtb for raspberry pi 3b doesn't allow wifi to be used

[Stefan Wahren]

Hi Santiago,

Am 07.12.18 um 00:16 schrieb Santiago Garcia Mantinan:
> Package: src:linux
> Version: 4.18.20-2
> Severity: normal
> Tags: patch
>
> Hi!
>
> After kernel 4.17 the dtb for raspberry pi 3 b is not ok and thus the wifi
> is not found and cannot be used.
>
> Looking at the differences from 4.17 to 4.18 I have discovered that if you
> revert this single patch affecting only the pi3b model the wifi is
> discovered and works again.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/bcm2837-rpi-3-b.dts?id=b1b8f45b3130dbd8704e5ea0d82b49b1d929498e
>
> I have tested this both on Linus kernel 4.20-rc5 and on Debian 4.19.5 as
> currently on experimental, on both reverting this patch makes the wifi work
> again.
>
>
this issue has already been reported here:

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

The proper fix has been applied to linux-next:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20181206=e25b6783c7b1bb79103d4617336879423f86b05e

The fix should be applied to 4.19 and 4.20 soon.

Regards
Stefan

Bug#916089: printf and echo no not output after escaped null character

[-=}\*/{=-]

Package: dash
Version: 0.5.8-2.4

problem: null chars and after are not printed or echoed...

$ printf %b '\eE\00a' | wc -m
2
$ echo -n '\eE\00a' | wc -m
2

current bad work around, includes leaking printf formatting :(

$ printf '\eE\00a' | wc -m
4

it does work in bash...

# echo -en '\eE\00a' | wc -m
4
# printf %b '\eE\00a' | wc -m
4
# printf '\eE\00a' | wc -m
4

if this is not a bug, and is the supposed (unexpected) behavior,
what then would be the correct way of printing nulls?

ps: if possible, please notify me upon correction is available in stable.

Bug#847642: ‘uglifyjs(1)’ manual page has sections with incorrect content

[Ben Finney]

Control: reopen -1

> The command ‘uglifyjs’ has a manual page ‘uglifyjs(1)’ that does not
> helpfully describe the command:
> 
> NAME
>uglify-js - manual page for uglify-js 2.7.5

This is still the case; the manual page (now for version 2.8.29) does
not contain a useful ‘NAME’ section. The ‘DESCRIPTION’ section also
does not contain the command description.

NAME
   uglify-js - manual page for uglify-js 2.8.29

DESCRIPTION
   bin/uglifyjs input1.js [input2.js ...] [options] Use a single
   dash to read input from the standard input.

   NOTE: by default there is no mangling/compression. […]

The summary of options belongs not in the ‘DESCRIPTION’ section, but
in the ‘SYNOPSIS’ section. This frees the ‘DESCRIPTION’ section to
properly describe the behaviour of the command for a new user.

I am re-opening this bug report, with the original request unresolved:

> The manual page should have the sections described ‘man-pages(7)’ §
> “Sections within a manual page”, with the content as described in that
> document.

-- 
 \  “[Entrenched media corporations will] maintain the status quo, |
  `\   or die trying. Either is better than actually WORKING for a |
_o__)  living.” —ringsnake.livejournal.com, 2007-11-12 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#916051: ITP: birdtray -- system tray notifications for Thunderbird

[Marek Mosiewicz]

W dniu 09.12.2018, nie o godzinie 19∶08 +0100, użytkownik Adam Borowski
napisał:
> On Sun, Dec 09, 2018 at 06:26:53PM +0100, Marek Mosiewicz wrote:
> > W dniu 09.12.2018, nie o godzinie 18∶08 +0100, użytkownik Adam
> > Borowski
> > napisał:
> > > * Package name: birdtray
> > > * URL : https://github.com/gyunaev/birdtray
> > >   Description : system tray notifications for Thunderbird
> > > Birdtray provides systray notifications for Thunderbird.  It
> > > displays
> > > the count of unread mail, hides the Thunderbird window when not
> > > in use,
> > > and restores it on clicking the tray icon.  It also provides a
> > > context
> > > menu with commands such as starting composing a new mail.
> > > .
> > > It is a nasty hack -- an external process looking at
> > > Thunderbird's
> > > insides, it suffers from problems like noticing new mails only
> > > after a
> > > delay, having to restart Thunderbird just to hide its window, etc
> > > --
> > > you'd want to use an extension like firetray instead -- but, it
> > > is
> > > likely that support for Thunderbird extensions will be dropped
> > > soon,
> > > possibly by the time you read these words.
> > Is it not simpler and much more effective to communicate with
> > Thunderbird via XPCOM ?
> 
> That's part of XUL -- if that's gone, so goes XPCOM.  Both are gone
> from
> Firefox since 57+, but have so far been retained in
> Thunderbird.  Alas,
> upstream is deliberating whether to drop or not -- with signs
> randomly
> pointing to droppage or not.  I don't know anything about Mozilla's
> internal
> politics (I'm only blindly packaging something I need), but as I
> understand
> it is a serious effort for the Thunderbird team to keep XUL after
> sabotage
> done by Mozilla's quantumization -- and as undermanned as they are,
> it's
> pretty likely they'll need to drop despite their wishes.
> 
> According to birdtray's upstream, the next best way to communicate is
> accessing Mork (.msf) files.
> 
> I guess the upstream could explain more.  And yeah, it's better when
> a
> packager knows something about the stuff he's packaging so if someone
> with a
> clue would be willing to help, it'd be deeply appreciated.
I took look into birdtray on github https://github.com/gyunaev/birdtray
/blob/master/src/modelnewemails.cpp and it seems to use Qt which seems
to unreasonable in this case as Thunderbird AFAIK uses GTK https://supp
ort.mozilla.org/pl/questions/1124868 and Qt would be bit unnecessery
dependency.


I do not know, maybe DBus is still option.https://utcc.utoronto.ca/~cks
/space/blog/unix/FirefoxDBusRemoteControl?showcomments 
There was plugin which used DBus from inside Thunderbird as internal
extension https://github.com/tanwald/gnome-shell-extension-thunderbird-
integration/blob/master/thunderbird-
integration%40tanwald.net/extension.js . But maybe this DBus event
still exists and can be communiated from separate process.

Ahoy ! 
> 
> 
> Meow!

Bug#916088: dpo-tools/1.3-1 [QA]

[Paulo Henrique de Lima Santana]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: mike.gabr...@das-netzwerkteam.de

Hi, 

Please **don't sponsor and upload** this package because my AM (Mike Gabriel)
will review it for me.

 * Package name: dpo-tools
   Version : 1.3-1
   Upstream Author : Debian Brazilian Localization Team 

 * URL : https://salsa.debian.org/l10n-br-team/dpo-tools
 * License : GPL-3+
   Section : utils

It builds this binary package:

  dpo-tools - set of scripts that can aid in the translation of podebconf files

To access further information about these packages, please visit the
following URL:

https://mentors.debian.net/sponsors/rfs-howto/dpo-tools

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dpo-tools/dpo-tools_1.3-1.dsc

More information about dpo-tools can be obtained from
https://salsa.debian.org/l10n-br-team/dpo-tools

Best regards,

-- 
Paulo Henrique de Lima Santana (phls) 
Curitiba - Brasil 
Debian Maintainer
Diretor do Instituto para Conservação de Tecnologias Livres
Membro da Comunidade Curitiba Livre
Site: http://www.phls.com.br 
GNU/Linux user: 228719  GPG ID: 0443C450

Organizador da DebConf19 - Conferência Mundial de Desenvolvedores(as) Debian
Curitiba - 21 a 28 de julho de 2019
http://debconf19.debconf.org


pgpftf7oveCDU.pgp
Description: PGP signature

Bug#899204: bug continues to happen

[Anmar Oueja]

Subject: gnome-logs: bug continues to happen
Followup-For: Bug #899204
Package: gnome-logs
Version: 3.30.0-1

Dear Maintainer,

Gnome-logs continues to exhibit the same behaviour as outlined in this bug.

   * What led up to the situation?

launching the application from either command line or through
gnome-shell. Using a non-root account of course.

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

tried launching the application as usual. I am presented with two
buttons "ignore" or "help" and a message saying "Unable to read system
logs". Clicking on any of the items in the left pane, after pressing
ignore or help causes a segementation fault as follows:

** (gnome-logs:13399): WARNING **: 17:53:28.491: Error retrieving the
sender timestamps: Cannot assign requested address

   * What was the outcome of this action?

Segementation fault with the following message :
** (gnome-logs:13399): WARNING **: 17:53:28.491: Error retrieving the
sender timestamps: Cannot assign requested address

   * What outcome did you expect instead?

View the logs of the system

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

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

Versions of packages gnome-logs depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-1
ii  gsettings-desktop-schemas3.28.1-1
ii  libc62.27-8
ii  libglib2.0-0 2.58.1-2
ii  libgtk-3-0   3.24.1-2
ii  libpango-1.0-0   1.42.4-4
ii  libsystemd0  239-13

gnome-logs recommends no packages.

gnome-logs suggests no packages.

-- no debconf information

Bug#916023: lintian: Please check if architecture could be "all" instead of "any"

[Chris Lamb]

tags 916023 + moreinfo
thanks

Hi Dmitry,

> please add check, that binary package could have "Architecture: all"
> instead of "any".

Hm, is this not the (experimental):

  https://lintian.debian.org/tags/package-contains-no-arch-dependent-files.html

… tag? :)


Best wishes,

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

Bug#916060: tuxmath: Starts and immediately closes

[Bernhard Übelacker]

Dear Maintainer,
I just tried to reproduce and collect some more information,
used a minimal buster amd64 qemu VM.

This issue seems to be more located in libt4k-common0.
It uses "rsvg_handle_get_desc(file_handle)" to retrieve
a char pointer to the description and tries to convert that
into an integer by sscanf [1].

Unfortunately seems librsvg-2.42 [2] the last release that
supported that way of operation. 
librsvg removed that functionality in commit [3].

Therefore in current version just a null pointer [4] is returned
by rsvg_handle_get_desc that leads to the crash in load_svg_sprite:


(gdb) bt
#0  __rawmemchr_sse2 () at ../sysdeps/x86_64/multiarch/../rawmemchr.S:37
#1  0x7febe0ac3342 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffd7b8ad720, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0) at strops.c:41
#2  0x7febe0ab624d in _IO_vsscanf (string=0x0, format=0x7febe0c35c62 "%d", 
args=args@entry=0x7ffd7b8ad850) at iovsscanf.c:40
#3  0x7febe0ab03f4 in __sscanf (s=, 
format=format@entry=0x7febe0c35c62 "%d") at sscanf.c:32
#4  0x7febe0c2c3c9 in load_svg_sprite (file_name=, 
width=width@entry=-1, height=height@entry=-1) at t4k_loaders.c:217
#5  0x7febe0c2d52b in load_sprite (name=name@entry=0x55b6034762a1 
"comets/comet", mode=mode@entry=4, w=w@entry=-1, h=h@entry=-1, 
proportional=proportional@entry=false) at t4k_loaders.c:714
#6  0x7febe0c2d978 in T4K_LoadScaledSprite (name=name@entry=0x55b6034762a1 
"comets/comet", mode=mode@entry=4, width=width@entry=-1, 
height=height@entry=-1) at t4k_loaders.c:651
#7  0x7febe0c2d98c in T4K_LoadSprite (name=name@entry=0x55b6034762a1 
"comets/comet", mode=mode@entry=4) at t4k_loaders.c:646
#8  0x55b60345b961 in load_image_data () at fileops_media.c:213
#9  0x55b603448962 in load_data_files () at setup.c:759
#10 0x55b6034497c5 in setup (argc=1, argv=0x7ffd7b8ae758) at setup.c:139
#11 0x55b603447be9 in main (argc=, argv=) at 
tuxmath.c:40


Kind regards,
Bernhard


[1] https://github.com/tux4kids/t4kcommon/blob/master/src/t4k_loaders.c#L228
[2] 
https://gitlab.gnome.org/GNOME/librsvg/blob/librsvg-2.42/librsvg/rsvg-handle.c#L772
[3] 
https://gitlab.gnome.org/GNOME/librsvg/commit/1006c2001d4775b6d5b20d5f77c5aea9ac280fcb
[4] 
https://gitlab.gnome.org/GNOME/librsvg/blob/master/librsvg/rsvg-handle.c#L1007

# buster amd64 qemu VM

apt update
apt dist-upgrade

apt install mc psmisc devscripts dpkg-dev systemd-coredump strace gdb 
xserver-xorg lightdm openbox tuxmath tuxmath-dbgsym libt4k-common0-dbgsym 
librsvg2-2-dbgsym
apt build-dep t4kcommon


systemctl start lightdm





mkdir libt4k-common0/orig -p
cdlibt4k-common0/orig
apt source libt4k-common0
cd ../..

mkdir librsvg2-2/orig -p
cdlibrsvg2-2/orig
apt source librsvg2-2
cd ../..









export LANG=C
export DISPLAY=:0
tuxmath





root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Sun 2018-12-09 22:02:02 CET8201  1000  1000  11 present   
/usr/lib/tuxmath/tuxmath
root@debian:~# coredumpctl gdb 8201
   PID: 8201 (tuxmath)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Sun 2018-12-09 22:02:02 CET (28s ago)
  Command Line: tuxmath
Executable: /usr/lib/tuxmath/tuxmath
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: b8debb360de74c7698ecca6a9e56eac5
Machine ID: 32f43b50ac8c4b21941bc0b02f8e7811
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.tuxmath.1000.b8debb360de74c7698ecca6a9e56eac5.8201.154438932200.lz4
   Message: Process 8201 (tuxmath) of user 1000 dumped core.

Stack trace of thread 8201:
#0  0x7febe0ad67af __rawmemchr_sse2 (libc.so.6)
#1  0x7febe0ac3342 _IO_str_init_static_internal (libc.so.6)
#2  0x7febe0ab624d _IO_vsscanf (libc.so.6)
#3  0x7febe0ab03f4 __sscanf (libc.so.6)
#4  0x7febe0c2c3c9 load_svg_sprite (libt4k_common.so.0)
#5  0x7febe0c2d52b load_sprite (libt4k_common.so.0)
#6  0x55b60345b961 n/a (tuxmath)
#7  0x55b603448962 n/a (tuxmath)
#8  0x55b6034497c5 n/a (tuxmath)
#9  0x55b603447be9 main (tuxmath)
#10 0x7febe0a67b17 __libc_start_main (libc.so.6)
#11 0x55b603447c2a n/a (tuxmath)

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 

Bug#915881: Ubuntu's custom build flags are overridden by Debian's

[Guillem Jover]

Hi!

On Fri, 2018-12-07 at 15:05:39 +, Iain Lane wrote:
> Package: libdpkg-perl
> Version: 1.19.1
> Severity: normal
> Tags: patch

> In Ubuntu we recently got a version of dpkg including
> d5374bc618310917557daa9c9ac2f4930515a0b2 for the first time, and I
> noticed that our ppc64el -O3 build flag wasn't being used - -O2 was
> being passed instead.
> 
> See the attached commit for my proposed fix - please let me know what
> you think. There are other valid approaches such as having Debian.pm
> check the value doesn't contain `-g -O\d' before appending it.

On Fri, 2018-12-07 at 11:02:49 -0700, Adam Conrad wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * scripts/Dpkg/Vendor/Ubuntu.pm: Instead of running the Debian hooks after
> the Ubuntu buildflags are set up, run them first, and then strip/prepend
> the bits we need to change. This fixes compiler optimisation on ppc64el.
> 
> This is vaguely similar to Laney's patch, but produces more pleasant output,
> and is also what I uploaded to Ubuntu just now to solve the problem.

Right, sorry for missing this! And thanks for the patches. As I
mentioned to Adam on IRC, I went with a solution I think should be
more future proof, and in addition also added a unit test to detect
similar failures in the future, see the attached patch, which is
queued for merging.

Iain: Should your mail address really be @debian or perhaps it should
have been either @canonical or @ubuntu instead? For better © tracking.

Thanks,
Guillem
From eb27f9167602a4ca18d409164f0500f3977e1b8d Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sat, 8 Dec 2018 00:28:57 +0100
Subject: [PATCH] Dpkg::Vendor::Ubuntu: Fix buildflags override after default
 setting move

The default buildflags got moved from the Dpkg::BuildFlags module to
the Dpkg::Vendor::Debian, but this module was not addapted to match.

Instead of running the Debian hooks after the Ubuntu buildflags are set
up, run them first, and then modify/prepend the bits we need to change.
This fixes compiler optimization on ppc64el, and makes setting it more
future proof.

Co-Author: Iain Lane 
Co-Author: Adam Conrad 
Fixes: commit d5374bc618310917557daa9c9ac2f4930515a0b2
Closes: #915881
---
 scripts/Dpkg/Vendor/Ubuntu.pm  | 12 ---
 scripts/Makefile.am|  1 +
 scripts/t/Dpkg_BuildFlags_Ubuntu.t | 57 ++
 3 files changed, 65 insertions(+), 5 deletions(-)
 create mode 100644 scripts/t/Dpkg_BuildFlags_Ubuntu.t

diff --git a/scripts/Dpkg/Vendor/Ubuntu.pm b/scripts/Dpkg/Vendor/Ubuntu.pm
index eb2dffefe..e6335c204 100644
--- a/scripts/Dpkg/Vendor/Ubuntu.pm
+++ b/scripts/Dpkg/Vendor/Ubuntu.pm
@@ -98,6 +98,9 @@ sub run_hook {
 } elsif ($hook eq 'update-buildflags') {
 	my $flags = shift @params;
 
+# Run the Debian hook to add hardening flags
+$self->SUPER::run_hook($hook, $flags);
+
 require Dpkg::BuildOptions;
 
 	my $build_opts = Dpkg::BuildOptions->new();
@@ -109,15 +112,14 @@ sub run_hook {
 if (Dpkg::Arch::debarch_eq($arch, 'ppc64el')) {
 		for my $flag (qw(CFLAGS CXXFLAGS OBJCFLAGS OBJCXXFLAGS GCJFLAGS
 		 FFLAGS FCFLAGS)) {
-		$flags->set($flag, '-g -O3', 'vendor');
+my $value = $flags->get($flag);
+$value =~ s/-O[0-9]/-O3/;
+$flags->set($flag, $value);
 		}
 	}
 	}
 	# Per https://wiki.ubuntu.com/DistCompilerFlags
-	$flags->set('LDFLAGS', '-Wl,-Bsymbolic-functions', 'vendor');
-
-	# Run the Debian hook to add hardening flags
-	$self->SUPER::run_hook($hook, $flags);
+$flags->prepend('LDFLAGS', '-Wl,-Bsymbolic-functions');
 } else {
 return $self->SUPER::run_hook($hook, @params);
 }
diff --git a/scripts/Makefile.am b/scripts/Makefile.am
index d7bd8d2f7..31df4d8df 100644
--- a/scripts/Makefile.am
+++ b/scripts/Makefile.am
@@ -219,6 +219,7 @@ test_scripts = \
 	t/Dpkg_Shlibs_Cppfilt.t \
 	t/Dpkg_Shlibs.t \
 	t/Dpkg_BuildFlags.t \
+	t/Dpkg_BuildFlags_Ubuntu.t \
 	t/Dpkg_BuildOptions.t \
 	t/Dpkg_BuildProfiles.t \
 	t/Dpkg_Build_Env.t \
diff --git a/scripts/t/Dpkg_BuildFlags_Ubuntu.t b/scripts/t/Dpkg_BuildFlags_Ubuntu.t
new file mode 100644
index 0..3cfdb268f
--- /dev/null
+++ b/scripts/t/Dpkg_BuildFlags_Ubuntu.t
@@ -0,0 +1,57 @@
+#!/usr/bin/perl
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see .
+
+use 

Bug#916056: dpkg-dev: dpkg-mergechangelogs strips vim modelines etc

[Guillem Jover]

Hi!

On Sun, 2018-12-09 at 18:16:52 +0100, Chris Lamb wrote:
> Package: dpkg
> Version: 1.19.2
> Severity: normal

> The dpkg-mergechangelogs utility strips vim modelines (etc). I
> discovered this in lintian which has a trailing "vim: et" at the end
> of the file.
> 
> This is, of course, caused by:
> 
>   } elsif (m/^vim:/io) {
> last; # skip Vim modelines at end of file
> 
> … in "scripts/Dpkg/Changelog/Debian.pm". I'm not sure what can be done
> about this however without introducing a special mode/option to the
> parsing code, however.

This was documented as the expected outcome in the man page, but it
seems indeed suboptimal. I guess the attached patch should make things
better. :)

Thanks,
Guillem
From 6dcbfb6a4df3e20102b6f3ff3fa977e031db2d1f Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sun, 9 Dec 2018 23:06:29 +0100
Subject: [PATCH] Dpkg::Changelog::Debian: Preserve modelines at EOF

We should keep these and considere them as pseudo-EOF markers, and stop
processsing once seen.

[la...@debian.org:
 - Partial test cases for dpkg-mergechangelogs functional tests. ]

Closes: #916056
---
 man/deb-changelog.man | 10 +-
 man/dpkg-mergechangelogs.man  |  4 ++--
 scripts/Dpkg/Changelog/Debian.pm  |  8 ++--
 scripts/Makefile.am   |  1 +
 scripts/t/Dpkg_Changelog.t|  8 ++--
 scripts/t/Dpkg_Changelog/stop-modeline| 13 +
 scripts/t/merge_changelogs/ch-a   |  2 ++
 scripts/t/merge_changelogs/ch-b   |  2 ++
 scripts/t/merge_changelogs/ch-merged  |  2 ++
 scripts/t/merge_changelogs/ch-merged-basic|  2 ++
 scripts/t/merge_changelogs/ch-merged-pr   |  2 ++
 scripts/t/merge_changelogs/ch-merged-pr-basic |  2 ++
 scripts/t/merge_changelogs/ch-old |  2 ++
 13 files changed, 47 insertions(+), 11 deletions(-)
 create mode 100644 scripts/t/Dpkg_Changelog/stop-modeline

diff --git a/man/deb-changelog.man b/man/deb-changelog.man
index 6aaa5d2cf..93dffbed1 100644
--- a/man/deb-changelog.man
+++ b/man/deb-changelog.man
@@ -142,12 +142,12 @@ The maintainer details and the date must be separated by exactly two
 spaces.
 .PP
 Any line that consists entirely (i.e., no leading whitespace) of \fB#\fP
-or \fB/* */\fP style comments, RCS keywords, Vim modelines or Emacs local
-variables should be ignored.
+or \fB/* */\fP style comments, RCS keywords.
 .PP
-Ancient changelog entries with other formats at the end of the file should
-be accepted and preserved on output, but their contents might be otherwise
-ignored and parsing stopped at that point.
+Vim modelines or Emacs local variables, and ancient changelog entries with
+other formats at the end of the file should be accepted and preserved on
+output, but their contents might be otherwise ignored and parsing stopped
+at that point.
 .PP
 The entire changelog must be encoded in UTF-8.
 .SH FILES
diff --git a/man/dpkg-mergechangelogs.man b/man/dpkg-mergechangelogs.man
index 9cda23ef0..4d6159c02 100644
--- a/man/dpkg-mergechangelogs.man
+++ b/man/dpkg-mergechangelogs.man
@@ -75,8 +75,8 @@ The accepted values are: \fB0\fP and \fB1\fP (default).
 .SH LIMITATIONS
 .P
 Anything that is not parsed by Dpkg::Changelog is lost during the merge.
-This might include stuff like Vim modelines, Emacs variables, comments
-which were not supposed to be there, etc.
+This might include stuff like comments which were not supposed to be
+there, etc.
 .
 .SH INTEGRATION WITH GIT
 .P
diff --git a/scripts/Dpkg/Changelog/Debian.pm b/scripts/Dpkg/Changelog/Debian.pm
index a44ac666c..937acb5e0 100644
--- a/scripts/Dpkg/Changelog/Debian.pm
+++ b/scripts/Dpkg/Changelog/Debian.pm
@@ -162,9 +162,13 @@ sub parse {
 	$expect= START_CHANGES;
 	@blanklines = ();
 	} elsif (m/^(?:;;\s*)?Local variables:/io) {
-	last; # skip Emacs variables at end of file
+# Save any trailing Emacs variables at end of file.
+$self->set_unparsed_tail("$_\n" . (file_slurp($fh) // ''));
+last;
 	} elsif (m/^vim:/io) {
-	last; # skip Vim modelines at end of file
+# Save any trailing Vim modelines at end of file.
+$self->set_unparsed_tail("$_\n" . (file_slurp($fh) // ''));
+last;
 	} elsif (m/^\$\w+:.*\$/o) {
 	next; # skip stuff that look like a RCS keyword
 	} elsif (m/^\# /o) {
diff --git a/scripts/Makefile.am b/scripts/Makefile.am
index 31df4d8df..65867b6b2 100644
--- a/scripts/Makefile.am
+++ b/scripts/Makefile.am
@@ -312,6 +312,7 @@ test_data = \
 	t/Dpkg_Changelog/misplaced-tz \
 	t/Dpkg_Changelog/regressions \
 	t/Dpkg_Changelog/shadow \
+	t/Dpkg_Changelog/stop-modeline \
 	t/Dpkg_Changelog/unreleased \
 	t/Dpkg_Checksums/empty \
 	t/Dpkg_Checksums/data-1 \
diff --git a/scripts/t/Dpkg_Changelog.t b/scripts/t/Dpkg_Changelog.t
index 8aa1bfc45..f487ff560 100644
--- a/scripts/t/Dpkg_Changelog.t
+++ b/scripts/t/Dpkg_Changelog.t
@@ -16,7 

Bug#916056: dpkg-dev: dpkg-mergechangelogs strips vim modelines etc

[Chris Lamb]

Dear Guillem,

> This was documented as the expected outcome in the man page, but it
> seems indeed suboptimal.

… I also did not somehow manage to scroll/read that far!

> + # Save any trailing Emacs variables at end of file.
> + $self->set_unparsed_tail("$_\n" . (file_slurp($fh) // ''));

Ah, of course we can save it there; no need for a special mode. Good
shout, and looking forward to this landing!


Best wishes,

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

Bug#916087: lintian: "exec failed: Text file busy" when running tests by tag

[Felix Lechner]

This is confirmed. I saw it earlier and thought it was fixed. Will be
back shortly.

Bug#916021: lintian: Please check for references to build directory

[Chris Lamb]

tags 916021 + moreinfo
thanks

[Adding rb-gene...@lists.reproducible-builds.org to CC]

> please add check, that files in binary packages do not refer to build
> directory. See (#915511) for example.

This seems like it would have quite the overlap with reproducible
builds in that we are essentially checking for this already there.

Also related is the fairly new "uses-dpkg-database-directly" tag that
essentially looks for instances of "/var/lib/dpkg":

  https://lintian.debian.org/tags/uses-dpkg-database-directly.html
 
> I believe the following strings should raise warning:
> 
>  /build/{name}
>  /build/{name}-{version}

Unfortunately, these are surely buildd-specific and, for example,
would not catch problem on my local setup (/tmp/buildd as it
happens…).

I think a somewhat more reliable approach would be called for here.
Suggestions welcome.

>  $PWD

Do you mean the literal string "$PWD"? If so, there is surely nothing
errant with a script in /usr/bin along the lines of:

  #!/bin/sh
  
  echo "$PWD"


Regards,

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

Bug#916016: qbittorrent: No search plugins available

[Mark Caglienzi]

This is the python3 package I have installed in my system (if it's useful):

$ dpkg -l python3 | grep ^ii
ii  python33.6.7-1  amd64interactive high-level 
object-oriented language
(default python3 version)


Then I installed also qbittorrent-dbg and ran qbittorrent under gdb, trying to 
get more
informations, but I didn't:

$ gdb qbittorrent
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 qbittorrent...Reading symbols from /usr/lib/debug/.build-
id/6d/150b4e78fe6cdf604d079d0ed2822596ef5ca7.debug...done.
done.
(gdb) run
Starting program: /usr/bin/qbittorrent 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x711d1700 (LWP 6737)]
[New Thread 0x7fffeac42700 (LWP 6738)]
[New Thread 0x7fffea441700 (LWP 6739)]
[New Thread 0x7fffe9bd9700 (LWP 6740)]
[New Thread 0x7fffe9399700 (LWP 6741)]
[New Thread 0x7fffe8b98700 (LWP 6742)]
[New Thread 0x7fffd37fe700 (LWP 6744)]
[New Thread 0x7fffd3fff700 (LWP 6743)]
[New Thread 0x7fffcaffd700 (LWP 6745)]
[New Thread 0x7fffd2ffd700 (LWP 6746)]
[New Thread 0x7fffd27fc700 (LWP 6747)]
[New Thread 0x7fffd1df7700 (LWP 6748)]
[New Thread 0x7fffd15f6700 (LWP 6749)]
[New Thread 0x7fffd0df5700 (LWP 6750)]
[Detaching after fork from child process 6751]
[Detaching after fork from child process 6752]
Could not parse Nova search engine capabilities, msg:  
Error:  
QProcess: Destroyed while process ("python3") is still running.
[New Thread 0x7fffcbfff700 (LWP 6793)]
[New Thread 0x7fffcb7fe700 (LWP 6794)]
[New Thread 0x7fffca7fc700 (LWP 6795)]
[New Thread 0x7fffc9ffb700 (LWP 6796)]
[New Thread 0x7fffc97fa700 (LWP 6797)]
[New Thread 0x7fffc8ff9700 (LWP 6798)]
[New Thread 0x7fffa3fff700 (LWP 6799)]
[New Thread 0x7fffa37fe700 (LWP 6800)]
[New Thread 0x7fffa2ffd700 (LWP 6801)]
[New Thread 0x7fffa27fc700 (LWP 6802)]
[New Thread 0x7fffa1ffb700 (LWP 6803)]
[New Thread 0x7fffa17fa700 (LWP 6804)]
[New Thread 0x7fffa0ff9700 (LWP 6805)]
[New Thread 0x7fff7700 (LWP 6806)]
[New Thread 0x7fff7f7fe700 (LWP 6807)]
[New Thread 0x7fff7effd700 (LWP 6808)]
[New Thread 0x7fff7e7fc700 (LWP 6809)]
[New Thread 0x7fff7dffb700 (LWP 6810)]
[New Thread 0x7fff7d7fa700 (LWP 6811)]



Kind regards,
Mark


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

Bug#916087: lintian: "exec failed: Text file busy" when running tests by tag

[Chris Lamb]

Package: lintian
Version: 2.5.116
Severity: important
X-Debbugs-CC: Felix Lechner 

Hi Felix,

I think your recent commits have introduced a regression in the test
harness:

  $ debian/rules runtests onlyrun=legacy-maintainer-scripts
   running tests 
  mkdir -p "/home/lamby/git/debian/lintian/lintian/debian/test-out"
  t/runtests -k -j 9 t "/home/lamby/git/debian/lintian/lintian/debian/test-out" 
legacy-maintainer-scripts
  
ENV[PATH]=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/lamby/.bashhub/bin
  pass tests::legacy-maintainer-scripts

  $ debian/rules runtests onlyrun=tag:uses-dpkg-database-directly
   running tests 
  mkdir -p "/home/lamby/git/debian/lintian/lintian/debian/test-out"
  t/runtests -k -j 9 t "/home/lamby/git/debian/lintian/lintian/debian/test-out" 
tag:uses-dpkg-database-directly
  
ENV[PATH]=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/lamby/.bashhub/bin
  error tests::scripts-maintainer-general: exec failed: Text file busy at 
/home/lamby/git/debian/lintian/lintian/lib/Lintian/Command.pm line 274.
   at /home/lamby/git/debian/lintian/lintian/lib/Lintian/Command.pm line 274.
   at t/runtests line 482.

  pass tests::files-uses-dpkg-database-directly
  pass tests::legacy-maintainer-scripts

  Failed tests (1)
  tests::scripts-maintainer-general
  make: *** [debian/rules:51: runtests] Error 1


ie. Only when running tests by tag name, even if it's the same test.


Regards,

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

Bug#904500: [Pkg-mailman-hackers] Bug#904500: mailman3-web: OpenID account connection fails (requires ?next=)

[Pierre-Elliott Bécue]

Le mercredi 25 juillet 2018 à 07:38:01-0500, Stephen Paul Weber a écrit :
> > >   Verifying return_to arguments: Parameter next not in return_to URL
> > 
> > Do you have a python traceback in the log?
> 
> Unfortunately, no.  The above message is all that appears in the log.  The
> webpage says
> 
> > Social Network Login Failure
> > 
> > An error occurred while attempting to login via your social network
> > account.
> 
> So I assume something in the app is catching the exception and only logging
> the message, not the traceback, before rendering this page.

This was a bug from django-allauth.

It's fixed upstream, I'll consider backporting django-allauth soon.

Cheers.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#916017: pax FTBFS with glibc 2.28

[Thorsten Glaser]

Hi Adrian,

>Tags: ftbfs
>
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pax.html
>
>...
>cpio.c: In function 'vcpio_wr':
>pax.h:261:18: warning: implicit declaration of function 'major' 
>[-Wimplicit-function-declaration]
> #define MAJOR(x) major(x)
>  ^

Thanks, I guess it will need ,
I’ll take care of it in the next couple of days.

bye,
//mirabilos
-- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2

Bug#916086: /usr/share/doc/openbox/build.html: suggests using non-existent kdetrayproxy

[Braun Gábor]

Package: openbox
Version: 3.6.1-7
Severity: normal
File: /usr/share/doc/openbox/build.html

Dear Maintainer,

In /usr/share/doc/openbox/build.html Section "If you run the KDE desktop 
environment"
claims that Openbox includes kdetrayproxy but there is no such executable
even with the package openbox-kde-session installed:

$ kdetrayproxy
bash: kdetrayproxy: parancs nem található

(That's a command not found error.)

Best wishes,

Gábor

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

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

Versions of packages openbox depends on:
ii  libc6 2.27-8
ii  libglib2.0-0  2.58.1-2
ii  libice6   2:1.0.9-2
ii  libobrender32v5   3.6.1-7
ii  libobt2v5 3.6.1-7
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-5
ii  libx11-6  2:1.6.7-1
ii  libxau6   1:1.0.8-1+b2
ii  libxcursor1   1:1.1.15-2
ii  libxext6  2:1.3.3-1+b2
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-1
ii  libxrandr22:1.5.1-1

Versions of packages openbox recommends:
ii  obconf1:2.0.4+git20150213-2
ii  obsession 20140608-2+b1
ii  openbox-menu  0.8.0+hg20161009-1
ii  scrot 0.8-19

Versions of packages openbox suggests:
ii  fonts-dejavu   2.37-1
ii  libxml2-dev2.9.4+dfsg1-7+b2
pn  openbox-gnome-session  
ii  openbox-kde-session3.6.1-7
ii  python 2.7.15-3
pn  tint2  

-- no debconf information

Bug#864440: xclip: Please package new upstream version 0.13

[Boyuan Yang]

X-Debbugs-CC: gh...@debian.org

Hi Alessandro,

On Thu, 08 Jun 2017 18:38:55 +0200 "W. Martin Borgert" <
deba...@debian.org> wrote:
> Package: xclip
> Version: 0.12+svn84-4
> Severity: wishlist
> 
> Upstream moved to github and published a new version:
> https://github.com/astrand/xclip/releases/tag/0.13
> "This release features several new features and bugfixes
> done over the last 6 years. See ChangeLog for details."
> I looks like the only Debian patch can be dropped then.

The new upstream release seems to be around for quite a few years. I'm
wondering if you could make another upload before Buster release with
new upstream version or make another upload without new upstream
release to deal with existing bugs since xclip hasn't seen any upload
for 4 years. Please let me know if NMU is okay to fix some obvious
problems (Vcs-*, Homepage, etc).

Thanks,
Boyuan Yang


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

Bug#904808: libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults

[Rene Luria]

Hello,Here is a patch trying to address that, as suggested by Simon McVittie in https://github.com/stevegrubb/libcap-ng/issues/5and Carlos O'Donell at https://sourceware.org/bugzilla/show_bug.cgi?id=13502Using the package built with this patch also fixes this bug:https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no=915642Sincerly,René

libcap-ng.patch
Description: Binary data

Bug#916084: bison-doc: Examples don't contain Makefiles

[Askar Safin]

Package: bison-doc
Version: 1:3.2.2-1
Severity: normal

/usr/share/doc/bison-doc/examples doesn't contain Makefiles, READMEs and other 
such information, which may be of interest for user. It should contain all 
info, which is installed by upstream package by "make install". Relevant thread 
starts here: http://lists.gnu.org/archive/html/bug-bison/2018-12/msg00015.html

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

Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

bison-doc depends on no packages.

bison-doc recommends no packages.

Versions of packages bison-doc suggests:
pn  doc-base  

-- no debconf information

Bug#916085: libpodofo: CVE-2018-19532

[Salvatore Bonaccorso]

Source: libpodofo
Version: 0.9.6+dfsg-3
Severity: important
Tags: security upstream
Forwarded: https://sourceforge.net/p/podofo/tickets/32/

Hi,

The following vulnerability was published for libpodofo.

CVE-2018-19532[0]:
| A NULL pointer dereference vulnerability exists in the function
| PdfTranslator::setTarget() in pdftranslator.cpp of PoDoFo 0.9.6, while
| creating the PdfXObject, as demonstrated by podofoimpose. It allows an
| attacker to cause Denial of Service.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-19532
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19532
[1] https://sourceforge.net/p/podofo/tickets/32/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#916083: cairo: CVE-2018-18064: Out of bound memset in libcairo result in stack buffer overflow

[Salvatore Bonaccorso]

Source: cairo
Version: 1.14.8-1
Severity: important
Tags: security upstream
Forwarded: https://gitlab.freedesktop.org/cairo/cairo/issues/341

Hi,

The following vulnerability was published for cairo.

CVE-2018-18064[0]:
| cairo through 1.15.14 has an out-of-bounds stack-memory write during
| processing of a crafted document by WebKitGTK+ because of the
| interaction between cairo-rectangular-scan-converter.c (the generate
| and render_rows functions) and cairo-image-compositor.c (the
| _cairo_image_spans_and_zero function).

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-18064
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18064
[1] https://gitlab.freedesktop.org/cairo/cairo/issues/341

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#856393: lxcfs: error message from the kernel: cgroup: new mount options do not match the existing superblock, will be ignored

[Pierre-Elliott Bécue]

Le mardi 28 février 2017 à 15:44:07+0100, Laurent Bonnaud a écrit :
> Package: lxcfs
> Version: 2.0.6-1
> Severity: normal
> 
> 
> Dear Maintainer,
> 
> as soon as I start lxcfs I get the following error message in the kernel logs:
> 
> cgroup: new mount options do not match the existing superblock, will be 
> ignored

Hi Laurent,

I'm sorry nobody gave you any feedback on your bug.

I've made an upload of lxc 3 in unstable. Could you run some tests with it
and tell me if you get the same issue?

Cheers,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#916082: fr.po: French debconf templates translation

[Jean-Philippe MENGUAL]

Package: fr.po
Version: N/A
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

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

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

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


Please find attached the french debconf templates translation, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
#
# Translation of cltl debconf templates to French
# Copyright (C) 2004, 2018 Debian French l10n team 

# This file is distributed under the same license as the wireshark package.
#
# Translators:
# Eric Madesclair , 2004
# Jean-Philippe MENGUAL , 2018
msgid ""
msgstr ""
"Project-Id-Version: cltl\n"
"Report-Msgid-Bugs-To: c...@packages.debian.org\n"
"POT-Creation-Date: 2016-11-29 07:23+0100\n"
"PO-Revision-Date: 2018-11-25 08:32+0100\n"
"Last-Translator: Jean-Philippe MENGUAL \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Download the cltl book from the Internet?"
msgstr "Faut-il télécharger le livre depuis Internet ?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"You don't have the file /root/tmp/cltl_ht.tar.gz. You may want to download "
"this file from internet now and proceed with the installation afterward."
msgstr ""
"Le fichier /root/tmp/cltl_ht.tar.gz n'est pas présent sur votre système. "
"Vous pouvez télécharger maintenant ce fichier depuis Internet et l'installer "
"plus tard."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Unable to download. Try again?"
msgstr "Téléchargement impossible, voulez-vous réessayer ?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"An error occurred during the download of book from the Internet. You may now "
"request to try the download again."
msgstr ""
"Une erreur s'est produite pendant le téléchargement du livre depuis "
"Internet. Vous pouvez recommencer le téléchargement maintenant."

#~ msgid "Aborting."
#~ msgstr "Le téléchargement est abandonné"

#~ msgid ""
#~ "The download of the cltl book from internet failed. You can try "
#~ "reinstalling the file another time."
#~ msgstr ""
#~ "Le téléchargement du livre depuis Internet a échoué. Vous pourrez essayer "
#~ "de le réinstaller plus tard."

Bug#916081: exiv2: CVE-2018-16336

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.25-4
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/400
Control: found -1 0.26-1

Hi,

The following vulnerability was published for exiv2.

CVE-2018-16336[0]:
| Exiv2::Internal::PngChunk::parseTXTChunk in Exiv2 v0.26 allows remote
| attackers to cause a denial of service (heap-based buffer over-read)
| via a crafted image file, a different vulnerability than
| CVE-2018-10999.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16336
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16336
[1] https://github.com/Exiv2/exiv2/issues/400
[2] 
https://github.com/Exiv2/exiv2/commit/35b3e596edacd2437c2c5d3dd2b5c9502626163d

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#915913: autopkgtest: please document what the syntax of the Features field is

[Paul Gevers]

Hi Josch,

On 07-12-2018 23:11, Johannes 'josch' Schauer wrote:
> then further below under "defined features" it says:
> 
>> test-name
>> Set an explicit test name for the log heading and the ``summary`` file
>> for a ``Test-Command:`` inline test. When not given, these are
>> enumerated like ``command1``.
> 
> But this does not explain the syntax of how a test name is actually
> specified. Does one just write it in the Features field? Or is it
> test-name:thename or does one have to quote something?

I totally agree with you. I have been staring at that line last week
when I wanted to use it. The correct syntax is:
Features: test-name=blablabla

> My use case: I have a test that uses Test-Command but the output becomes
> hard to understand if tests are just named command1, command2 and so
> forth. Thus I want to give them meaningful names.

That is indeed exactly why we have this feature.

> Unfortunately under "Test-Command" it also says "This is mutually
> exclusive with the ``Tests:`` field". Is there a practical reason why
> these fields are mutually exclusive? Naively, I would've expected, that
> when Test-Command is given, then it doesn't look for a script but
> instead executes the command but that it anyways takes the test name
> from the "Tests" field. It seems unnecessarily complicated to require
> the test-name feature thing.

Well, the practical reason is that this feature was added way later than
the original code and there are sanity checks in place. I guess that
Martin didn't consider your proposal and just left the old code in place.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#911437: gitlab-ci-multi-runner: FTBFS with golang-github-prometheus-client-golang/0.9.0-1

[Dmitry Smirnov]

On Tuesday, 20 November 2018 5:26:02 AM AEDT Andreas Henriksson wrote:
> It seems you've forgot to push upstream/pristine-tar branches
> and tags when you did the last update/upload of the package.
> Could you please push them?

Done. FYI I did not forget to push - I was working in haste and just did not 
import orig.tar at a time: maintaining those useless branches always take 
precious time from something more important...


> I'm attaching a patch to fix the FTBFS bug that seems to have
> just gotten this package removed from testing.

Thank you very much for your help. It is very nice that you've managed to 
find solution to this problem.

-- 
Best wishes,
 Dmitry Smirnov.

---

Journalism is printing what someone else does not want printed: everything
else is public relations.
-- George Orwell


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

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Adrian Nuta]

Hi, git repo is at https://github.com/manticoresoftware/manticoresearch.

Right now I have debhelper (>= 11), but previous used debhelper-compat (=
11), same message.

Bug#916080: ITP: libjs-jquery-center -- jQuery plugin that centralizes DOM element

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: libjs-jquery-center
  Version : 1.1.1
  Upstream Author : Ben Lin
* URL : https://github.com/dreamerslab/jquery.center/
* License : Expat
  Programming Lang: Javascript
  Description : jQuery plugin that centralizes DOM element

 This simple plugin helps you centralize your DOM element against their
 parent element or the window. You can also specify the top of the DOM
 element by passing customized settings. This plugin only works for
 absolute elements.
 .
 This jQuery extension is needed by upcoming OpenBoard upload.

Bug#916079: hyperic-sigar FTBFS with glibc 2.28

[Adrian Bunk]

Source: hyperic-sigar
Version: 1.6.4+dfsg-2.1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hyperic-sigar.html

...
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1148:22: error: 
called object 'major' is not a function or function pointer
   [cc]  #define ST_MAJOR(sb) major((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1237:23: note: 
in expansion of macro 'ST_MAJOR'
   [cc]  if ((major == ST_MAJOR(sb)) &&
   [cc]^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1232:23: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1149:22: error: 
called object 'minor' is not a function or function pointer
   [cc]  #define ST_MINOR(sb) minor((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1238:24: note: 
in expansion of macro 'ST_MINOR'
   [cc]  ((minor == ST_MINOR(sb)) || (minor == 0)))
   [cc] ^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1232:30: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1149:22: error: 
called object 'minor' is not a function or function pointer
   [cc]  #define ST_MINOR(sb) minor((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1289:26: note: 
in expansion of macro 'ST_MINOR'
   [cc]  if (minor == ST_MINOR(sb)) {
   [cc]   ^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1232:30: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]   ^
   [cc] /build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c: In 
function 'get_iostat_procp':
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1148:22: error: 
called object 'major' is not a function or function pointer
   [cc]  #define ST_MAJOR(sb) major((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1340:23: note: 
in expansion of macro 'ST_MAJOR'
   [cc]  if ((major == ST_MAJOR(sb)) && (minor == ST_MINOR(sb))) {
   [cc]^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1335:23: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1149:22: error: 
called object 'minor' is not a function or function pointer
   [cc]  #define ST_MINOR(sb) minor((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1340:50: note: 
in expansion of macro 'ST_MINOR'
   [cc]  if ((major == ST_MAJOR(sb)) && (minor == ST_MINOR(sb))) {
   [cc]   ^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1335:30: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]   ^

Bug#916078: varnishd: make default cc_command reproducible

[Helmut Grohne]

Package: varnish
Version: 6.1.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

varnish embeds the detected compiler and build flags into the varnishd
binary for the variable cc_command. Given that the default build flags
include -fdebug-prefix-map, this embeds the varnish's build path and
makes varnish unreproducible. Also using "gcc" is not what varnish
wants: When installed for a foreign architecture, the created objects
will fail to load. varnish must use a triplet-prefixed compiler here.
The latter happens to break cross compilation. Please consider applying
the attached patch to get a correct and reproducible default for
cc_command.

Helmut
diff --minimal -Nru varnish-6.1.1/debian/changelog 
varnish-6.1.1/debian/changelog
--- varnish-6.1.1/debian/changelog  2018-12-01 13:44:50.0 +0100
+++ varnish-6.1.1/debian/changelog  2018-12-09 21:02:45.0 +0100
@@ -1,3 +1,10 @@
+varnish (6.1.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Make cc_command reproducible. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 09 Dec 2018 21:02:45 +0100
+
 varnish (6.1.1-1) unstable; urgency=medium
 
   * Imported new upstream version 6.1.1
diff --minimal -Nru varnish-6.1.1/debian/rules varnish-6.1.1/debian/rules
--- varnish-6.1.1/debian/rules  2018-12-01 13:44:50.0 +0100
+++ varnish-6.1.1/debian/rules  2018-12-09 21:02:45.0 +0100
@@ -4,16 +4,12 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/architecture.mk
 include /usr/share/dpkg/buildflags.mk
 
 # List of architectures where jemalloc is not available
 DISABLE_JEMALLOC_ARCH_LIST := hppa m68k
 
-# Explicitly initialize a variable to select architecture, unless it has been
-# defined before.  This is compared against the DISABLE_*_LIST variables later
-# in this makefile
-DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
-
 # Set local state dir for FHS
 LOCAL_CONFIGURE_FLAGS = --localstatedir=/var/lib
 
@@ -39,6 +35,13 @@
 # https://github.com/varnishcache/varnish-cache/issues/1875
 CFLAGS += -fexcess-precision=standard
 
+# Disable reproducible cflags as embedding them in to the binary makes the
+# build unreproducible.
+export VCC_CC=exec \
+   $(DEB_HOST_GNU_TYPE)-gcc \
+   $(shell DEB_BUILD_MAINT_OPTIONS="$(DEB_BUILD_MAINT_OPTIONS) 
reproducible=-all" dpkg-buildflags --get CFLAGS) \
+   -Werror -Wno-error=unused-result -pthread -fpic -shared -Wl,-x -o %o %s
+
 # Main build rule, leave everything to debhelper
 %:
dh $@

Bug#801342:

[Rodolfo Sanchez]

Tengo dudas ,una de ella es cuanto es el impuesto y la otra se paga cuando
se esté entregando

Bug#915243: GTK 3 systray icons don't redraw transparent parts

[Roland Hieber]

reassign 915243 libgtk-3-0 3.23.1-1
notfound 915243 3.22.30-2
forwarded 915243 https://gitlab.gnome.org/GNOME/gtk/issues/1280
thanks

On Sun, Dec 02, 2018 at 09:46:00AM +0100, Uli Schlachter wrote:
> Hi,
> 
> On 02.12.18 02:30, Roland Hieber wrote:
> > since a recent apt-get upgrade, followed by a restart of X, the systray
> > icons in my awesome with default configuration look strange and it seems
> > like the transparent parts are no longer redrawn with the background
> > color, but previously drawn items stay there, and only the opaque parts
> > of the icons are drawn over them. I don't know if this is awesome's
> > fault, it could also be a problem in an underlying library, so feel free
> > to assign to some other package.
> 
> GTK+ broke their systray icons (perhaps only in non-composited
> environments; I'm not entirely sure). As far as I know, version 3.24 is
> affected.
> 
> This bug was introduced in
> https://gitlab.gnome.org/GNOME/gtk/commit/01d1bc3c75fd0eff5665f5b9c690c5e1e6c65f13.
> 
> Links to a couple of upstream bugs (and patches):
> 
> https://github.com/awesomeWM/awesome/issues/1720
> (Ignore the people talking about Qt for this; Qt also broke their icons
> ages ago)
>
> https://github.com/awesomeWM/awesome/issues/2449
> (This talks about GTK 3.24 being affected)
> 
> https://github.com/i3/i3/issues/3335
> 
> https://github.com/TomaszGasior/gtk3-mushrooms/issues/12
> 
> https://gitlab.gnome.org/GNOME/gtk/issues/1280
> 
> https://gitlab.gnome.org/GNOME/gtk/merge_requests/391/diffs
> 
> (Sadly this merge request is inactive for about a month now...)

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

On Sun, 9 Dec 2018 20:35:02 +0100
Markus Koschany  wrote:

>Hello Andreas,
>
>
>Am 09.12.18 um 16:07 schrieb Andreas Ronnquist:
>> tags 916037 + patch
>> thanks
>> 
>> Patch attached to fix this build error (Which I am the cause of).  
>
>Please feel free to upload your fix as needed. Since all packages are
>team-maintained and you are a member of the team and know why the
>packages FTBFS, it makes absolutely sense that you handle the uploads
>too.
>

You are right - I'll take care of the uploads. Not doing it is because
I got unsure if I should do it, because I don't want to disturb some
Vcs-migration to salsa - All three of the packages have still SVN in the
Vcs-* fields, and one of them in addition even has a (non-gbp) git
repository on Salsa.

But with that message, I'll take care of it. (Oh, how simple everything
would be if everything was just gbp, and be done with it) :)

/Andreas
mailingli...@gusnan.se
gus...@debian.org


pgpOtpwwdgy6y.pgp
Description: OpenPGP digital signatur

Bug#915639: Apologies for shibboleth-resolver FTBFS

[Sam Hartman]

Hi.

I am not sure how I managed to produce the binary package for amd64.  I
*thought* that I used sbuild in a clean sid chroot to do so, but it's
quite clear from trying to reproduce that that I failed.  I'm somewhat
baffled because my work flow makes it hard for something not coming out
of sbuild with a clean chroot to end up in the right place to be
uploaded, but it's certainly the case that the dsc I uploaded simply
does not work.

I regret that the package was so broken and that I managed not to catch
it.  I did intend to avoid the obvious failure of building on my host
system, and I thought I had a work flow that was not vulnerable to
screwing that up.
Anyway, apologies that you had to waste your time on my error.

Bug#916077: virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae

[Andreas Beckmann]

Package: virtualbox-dkms
Version: 5.2.22-dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + virtualbox-guest-additions-iso

Hi,

virtualbox-dkms fails to build a module for 4.18.0-3-686,
4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case
it matters). There are no problems bulding for 4.18.0-3-amd64.
The (attached) make.log starts with:


DKMS make.log for virtualbox-5.2.22 for kernel 4.18.0-3-686 (i686)
Sun Dec  9 20:00:18 UTC 2018
make: Entering directory '/usr/src/linux-headers-4.18.0-3-686'
make[4]: dpkg-architecture: Command not found
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvSem.o
In file included from 
/var/lib/dkms/virtualbox/5.2.22/build/include/VBox/types.h:30:0,
 from 
/var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/../SUPDrvInternal.h:35,
 from 
/var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:280:9: error: 
unknown type name '__uint128_t'
 typedef __uint128_t uint128_t;
 ^~~
/var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:299:9: error: 
unknown type name '__int128_t'
 typedef __int128_t int128_t;
 ^~


Andreas


make.log.gz
Description: application/gzip

Bug#916076: kamoso: segmentation fault in GStreamer opening hamburger menu

[John Scott]

Package: kamoso
Version: 18.04.0-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I'm unable to dig into the code and narrow down the issue at the
moment, but filing the bug nonetheless should others run into it
or have input.

With or without a webcam, trying to open the menu in the top-left
corner makes Kamoso crash on my system. Here's a backtrace I got.

[New Thread 0x7ffeca7ce700 (LWP 7958)]
[New Thread 0x7ffebe449700 (LWP 7959)]

Thread 45 "imagefreeze22:s" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff728e0700 (LWP 7950)]
0x7fffc8a2915c in gst_radioactv_transform_frame (vfilter=0x55b5c8d0 
[GstRadioacTV], in_frame=, out_frame=) at 
gstradioac.c:399
399 gstradioac.c: No such file or directory.

#0  0x7fffc8a2915c in gst_radioactv_transform_frame (vfilter=0x55b5c8d0 
[GstRadioacTV], in_frame=, out_frame=) at 
gstradioac.c:399
#1  0x7fffe4070e53 in gst_video_filter_transform (trans=0x55b5c8d0 
[GstRadioacTV], inbuf=, outbuf=0x7fffe802c2f0) at 
gstvideofilter.c:272
#2  0x7fffd3bcb609 in default_generate_output (trans=0x55b5c8d0 
[GstRadioacTV], outbuf=0x7fff728dfa60) at gstbasetransform.c:2132
#3  0x7fffd3bcacd6 in gst_base_transform_chain (pad=, 
parent=0x55b5c8d0 [GstRadioacTV], buffer=) at 
gstbasetransform.c:2285
#4  0x77975c3a in gst_pad_chain_data_unchecked (data=0x7fffc0106eb0, 
type=4112, pad=0x7fffe801d140 [GstPad]) at gstpad.c:4322
#5  0x77975c3a in gst_pad_push_data (pad=pad@entry=0x7fffe801cef0 
[GstPad], type=type@entry=4112, data=data@entry=0x7fffc0106eb0) at gstpad.c:4578
#6  0x7797ded2 in gst_pad_push (pad=0x7fffe801cef0 [GstPad], 
buffer=0x7fffc0106eb0) at gstpad.c:4697
#7  0x7fffd3bcadfd in gst_base_transform_chain (pad=, 
parent=0x55c4a2d0 [GstVideoConvert], buffer=) at 
gstbasetransform.c:2321
#8  0x77975c3a in gst_pad_chain_data_unchecked (data=0x7fffe802c1e0, 
type=4112, pad=0x7fffe801cca0 [GstPad]) at gstpad.c:4322
#9  0x77975c3a in gst_pad_push_data (pad=pad@entry=0x7fffe801ca50 
[GstPad], type=type@entry=4112, data=data@entry=0x7fffe802c1e0) at gstpad.c:4578
#10 0x7797ded2 in gst_pad_push (pad=0x7fffe801ca50 [GstPad], 
buffer=buffer@entry=0x7fffe802c1e0) at gstpad.c:4697
#11 0x7fffd06a9b69 in gst_image_freeze_src_loop (pad=0x7fffe801ca50 
[GstPad]) at gstimagefreeze.c:799
#12 0x779aaf41 in gst_task_func (task=0x7fffc00e15f0 [GstTask]) at 
gsttask.c:332
#13 0x77858ad3 in g_thread_pool_thread_proxy (data=) at 
../../../../glib/gthreadpool.c:307
#14 0x77858135 in g_thread_proxy (data=0x7fff9c0bf1e0) at 
../../../../glib/gthread.c:784
#15 0x75292f2a in start_thread (arg=0x7fff728e0700) at 
pthread_create.c:463
#16 0x75babedf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

It might not be relevant, but messages like these are visible on the
command-line too.

error: no element "frei0r-filter-cartoon"
error: no element "frei0r-filter-twolay0r"
error: no element "frei0r-filter-distort0r"

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

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

Versions of packages kamoso depends on:
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  gstreamer1.0-x  1.14.4-1
ii  kio 5.51.0-1
ii  libc6   2.27-8
ii  libgcc1 1:8.2.0-9
ii  libglib2.0-02.58.1-2
ii  libgstreamer-plugins-base1.0-0  1.14.4-1
ii  libgstreamer1.0-0   1.14.4-1
ii  libkf5configcore5   5.51.0-1
ii  libkf5configgui55.51.0-1
ii  libkf5coreaddons5   5.51.0-1
ii  libkf5i18n5 5.51.0-1
ii  libkf5itemviews55.51.0-1
ii  libkf5kiocore5  5.51.0-1
ii  libkf5kiofilewidgets5   5.51.0-1
ii  libkf5kiowidgets5   5.51.0-1
ii  libqt5core5a5.11.2+dfsg-7
ii  libqt5gui5  5.11.2+dfsg-7
ii  libqt5qml5  5.11.2-3
ii  libqt5quick55.11.2-3
ii  libqt5widgets5  5.11.2+dfsg-7
ii  libstdc++6  8.2.0-9
ii  qml-module-org-kde-purpose  5.51.0-1

kamoso recommends no packages.

kamoso suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAXEkn09uX7g8Tv8W3qerYfa4vJcFAlwNdQ0ACgkQ3qerYfa4
vJfirwgAi6UmOQUV0NFURoyZAYeN4wB/cT0kIKkeheBD8aKmkeA6YciEVIovG1Cj
+N5Muy/Q8BWcq3qlWjm5RQuaL7gTNSkUJgFWvmAVyxba2ytRbAfkHzpB5iYY0qrx
DmlOQcx+SwNq9BPRxqJ8r4aYuvj5RYkcN5DamYqMgaTSCfcE272y2nC+RLlL7ank

Bug#916075: policykit-1: autopkgtest regression

[Paul Gevers]

Source: policykit-1
Version: 0.105-23
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of policykit-1 the autopkgtest of policykit-1 fails
in testing when that autopkgtest is run with the binary packages of
policykit-1 from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
policykit-1from testing0.105-23
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the
same error can be found in the python-dbusmock regression due to this
update.

Currently this regression is NOT contributing to the delay of the
migration to testing [1] because of the urgency. Can you please
investigate the situation and fix it? If needed, please change the bug's
severity.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/policykit-1/1474415/log.gz

autopkgtest [04:38:19]: test cli-root: [---
TEST: pkaction
No action with action id unknown.action
TEST: pkcheck

** (process:1436): CRITICAL **: 04:38:19.446:
polkit_unix_process_set_property: assertion 'val != -1' failed

** (process:1439): CRITICAL **: 04:38:19.453:
polkit_unix_process_set_property: assertion 'val != -1' failed
autopkgtest [04:38:19]: test cli-root: ---]
autopkgtest [04:38:19]: test cli-root:  - - - - - - - - - - results - -
- - - - - - - -
cli-root FAIL stderr:



signature.asc
Description: OpenPGP digital signature

Bug#916073: devscripts: Reportbug includes sensitive ~/.devscripts

[Adam D. Barratt]

On Sun, 2018-12-09 at 19:45 +, Dmitry Bogatov wrote:
> by default reportbug(1) includes content of ~/.devscripts when
> reporting
> bugs in devscripts. Problem is that it can contain sensitive
> information (at least SALSA_TOKEN, maybe something more).

The only other setting which previously existed that could contain
sensitive information is BTS_SMTP_AUTH, and the bugscript already
filters that out; it can / should simply also do so for SALSA_TOKEN.

Regards,

Adam

Bug#916074: pcc: useless without libpcc-dev

[Sven Joachim]

Package: pcc
Version: 1.2.0~DEVEL+20181202-1
Severity: serious
Control: block -1 by 915633

Without libpcc-dev, pcc cannot compile any but the most trivial C
programs (e.g. #including  causes the preprocessor to complain
about a missing stddef.h) and cannot link any C program because ld fails
to find crtbegin.o.

For this reason I think that libpcc-dev should be bumped from Recommends
to Depends.  Of course this requires pcc-libs to be uploaded to unstable
and to be built on all (release) architectures where pcc is currently
available.  The initial upload to experimental FTBFS everywhere except
on amd64 (see #915633).


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

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

Versions of packages pcc depends on:
ii  libc6  2.28-2

Versions of packages pcc recommends:
ii  libpcc-dev  1.2.0~DEVEL+20180604-1

pcc suggests no packages.

-- no debconf information

Bug#916073: devscripts: Reportbug includes sensitive ~/.devscripts

[Dmitry Bogatov]

Package: devscripts
Version: 2.18.11
Severity: important
Justification: potential sensitive information leak

Dear Maintainer,

by default reportbug(1) includes content of ~/.devscripts when reporting
bugs in devscripts. Problem is that it can contain sensitive
information (at least SALSA_TOKEN, maybe something more).

Since salsa(1) is only in experimental, and such changes would not
introduce major breakage, I suggest:

 * discourage/prohibit storing sensitive information in ~/.devscripts
 * read SALSA_TOKEN from environment
 * remove/discourage --token option, since this way token is exposed
   to anybody, who can invoke ps(1).

-- Package-specific info:

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

--- ~/.devscripts ---
SALSA_TOKEN=$(pass access/git/salsa.debian.org/kaction | awk 'NR == 2 { print 
$2 }')

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages devscripts depends on:
ii  dpkg-dev  1.19.2
ii  fakeroot  1.23-1
ii  file  1:5.34-2
ii  gnupg 2.2.11-1
ii  gnupg22.2.11-1
ii  gpgv  2.2.11-1
ii  libc6 2.28-2
ii  libfile-homedir-perl  1.004-1
ii  libfile-which-perl1.22-1
ii  libipc-run-perl   20180523.0-1
ii  libmoo-perl   2.003004-2
ii  libwww-perl   6.36-1
ii  patchutils0.3.4-2
ii  perl  5.28.1-3
ii  python3   3.7.1-2
ii  sensible-utils0.0.12
ii  wdiff 1.2.2-2+b1

Versions of packages devscripts recommends:
ii  apt 1.8.0~alpha2
pn  at  
ii  curl7.62.0-1
ii  dctrl-tools 2.24-3
pn  debian-keyring  
ii  dput1.0.2
ii  equivs  2.2.0
ii  libdistro-info-perl 0.20
ii  libdpkg-perl1.19.2
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.048-1
ii  libgitlab-api-v4-perl   0.13-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.07-2
pn  libsoap-lite-perl   
ii  libstring-shellquote-perl   1.04-1
ii  libtry-tiny-perl0.30-1
ii  liburi-perl 1.74-1
pn  licensecheck
ii  lintian 2.5.116
ii  man-db  2.8.4-3
ii  patch   2.7.6-3
ii  python3-apt 1.7.0
ii  python3-debian  0.1.33
ii  python3-magic   2:0.4.15-2
ii  python3-requests2.20.0-2
ii  python3-unidiff 0.5.4-1
ii  python3-xdg 0.25-4
ii  strace  4.21-1
ii  unzip   6.0-21
ii  wget1.19.5-2
ii  xz-utils5.2.2-1.3

Versions of packages devscripts suggests:
pn  adequate 
pn  autopkgtest  
pn  bls-standalone   
ii  bsd-mailx [mailx]8.1.2-0.20180807cvs-1
ii  build-essential  12.5
pn  check-all-the-things 
pn  cvs-buildpackage 
pn  devscripts-el
ii  diffoscope   107
pn  disorderfs   
pn  dose-extra   
pn  duck 
ii  faketime 0.9.7-3
pn  gnuplot  
pn  how-can-i-help   
pn  libauthen-sasl-perl  
pn  libdbd-pg-perl   
ii  libfile-desktopentry-perl0.22-1
pn  libnet-smtps-perl
pn  libterm-size-perl
pn  libtimedate-perl 
pn  libyaml-syck-perl
ii  mozilla-devscripts   0.53
ii  mutt 1.10.1-2
ii  openssh-client [ssh-client]  1:7.9p1-4
pn  piuparts 
pn  postgresql-client
ii  quilt0.65-3
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
ii  w3m  0.5.3-36+b1

-- no debconf information

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Markus Koschany]

Hello Andreas,


Am 09.12.18 um 16:07 schrieb Andreas Ronnquist:
> tags 916037 + patch
> thanks
> 
> Patch attached to fix this build error (Which I am the cause of).

Please feel free to upload your fix as needed. Since all packages are
team-maintained and you are a member of the team and know why the
packages FTBFS, it makes absolutely sense that you handle the uploads too.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#916072: mark python-chardet Multi-Arch: foreign

[Helmut Grohne]

Package: python-chardet
Version: 3.0.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:nagios-plugins-contrib

python-chardet cannot be used to satisfy cross build dependencies (e.g.
for nagios-plugins-contrib via python-debian). In general, Architecture:
all packages can never satisfy cross Build-Depends unless marked
Multi-Arch: foreign. In this case, such a marking is not entirely
correct, but "good enough". Python's byte compilation is architecture
dependent, so python-chardet will only have bytecompiled files for the
main python interpreter and not for foreign embedded interpreters. Still
that's good enough for using python-chardet. That seems like a fair
compromise given that very few packages use an embedded interpreter and
even fewer people install them for foreign architectures.
python-chardet's dependencies are already annotated :any or marked
Multi-Arch: foreign, so that part is fine. The same reasoning holds for
python3-debian. Please consider applying the attached patch.

Helmut
diff --minimal -Nru chardet-3.0.4/debian/changelog 
chardet-3.0.4/debian/changelog
--- chardet-3.0.4/debian/changelog  2017-06-18 23:51:08.0 +0200
+++ chardet-3.0.4/debian/changelog  2018-12-09 20:25:51.0 +0100
@@ -1,3 +1,10 @@
+chardet (3.0.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark all packages Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 09 Dec 2018 20:25:51 +0100
+
 chardet (3.0.4-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru chardet-3.0.4/debian/control chardet-3.0.4/debian/control
--- chardet-3.0.4/debian/control2017-06-18 23:51:08.0 +0200
+++ chardet-3.0.4/debian/control2018-12-09 20:25:49.0 +0100
@@ -25,6 +25,7 @@
 
 Package: python-chardet
 Architecture: all
+Multi-Arch: foreign
 Depends:
  ${python:Depends},
  ${misc:Depends},
@@ -51,6 +52,7 @@
 
 Package: python3-chardet
 Architecture: all
+Multi-Arch: foreign
 Depends:
  ${python3:Depends},
  ${misc:Depends},

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[2018-12-07 16:39] Adrian Nuta 
> Switched to quilt, but I don't understand why mentor lintian says "No
> compatibility level set!"

Can you please remind, where are git sources of your package?

I could be that mentor lintian is old and does not recognize

Build-Depends: debhelper-compat (= 11)

Bug#916071: ros-geometry2: autopkgtest regression

[Paul Gevers]

Source: ros-geometry2
Version: 0.6.5-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of ros-geometry2 the autopkgtest of ros-geometry2
fails in testing when that autopkgtest is run with the binary packages
of ros-geometry2 from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
ros-geometry2  from testing0.6.5-1
all others from testingfrom testing

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

Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.

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

Paul

[1] https://qa.debian.org/excuses.php?package=ros-geometry2

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ros-geometry2/1474426/log.gz

autopkgtest [04:51:47]: test python3-tf2-geometry-msgs: python3 -c
'import tf2_geometry_msgs'
autopkgtest [04:51:47]: test python3-tf2-geometry-msgs:
[---
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/tf2_geometry_msgs/__init__.py",
line 1, in 
from .tf2_geometry_msgs import *
  File
"/usr/lib/python3/dist-packages/tf2_geometry_msgs/tf2_geometry_msgs.py",
line 32, in 
import rospy
ModuleNotFoundError: No module named 'rospy'
autopkgtest [04:51:47]: test python3-tf2-geometry-msgs:
---]



signature.asc
Description: OpenPGP digital signature

Bug#845924: marked as done (Atanks fails to compile on kFreeBSD)

[Markus Koschany]

Control: reopen -1

Now the build also fails because of

error: 'HOME_DIR' was not declared in this scope

I don't know how one can reliably set the HOME_DIR variable on GNU/Hurd
and kFreeBSD, so I leave this task to someone else.



signature.asc
Description: OpenPGP digital signature

Bug#915907: rclone: autopkgtest regression: missing versioned dependency?

[Paul Gevers]

On Fri, 7 Dec 2018 21:16:40 +0100 Paul Gevers  wrote:
> With a recent upload of rclone the autopkgtest of rclone fails in
> testing when that autopkgtest is run with the binary packages of rclone
> from unstable.

I wonder if this isn't just pointing at a missing versioned depends on
golang-github-okzk-sdnotify as updating that package in testing also
makes the (older) version of rclone in testing fail, while rclone passes
in unstable.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#913371: gnat-gps fails to build on 32-bit kernels, address space exhaustion.

[Nicolas Boulenguez]

Package: src:gnat-gps
Followup-For: Bug #913371

gnat-gps/18 now fails to build on armhf, while 18-3 was succeeding on
the same architecture.

After investigation, the only successful builds of gnat-gps/18 on 32
bits architectures so far (armhf i386 powerpc) were registered with a
32 bits chroot on a 64 bits machine.

I suggest the following architecture list, with only 64 bits
architectures, but any better idea is welcome.

amd64 arm64 mips64el ppc64el s390x alpha ia64 kfreebsd-amd64 ppc64
riscv64 sparc64

Bug#916070: rootskel FTBFS with glibc 2.28

[Adrian Bunk]

Source: rootskel
Version: 1.125
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rootskel.html

...
gcc -Os -Wall get-real-console-linux.c -o get-real-console-linux
get-real-console-linux.c: In function 'main':
get-real-console-linux.c:30:23: warning: implicit declaration of function 
'major' [-Wimplicit-function-declaration]
 printf("%d:%d\n", major(dev), minor(dev));
   ^
get-real-console-linux.c:30:35: warning: implicit declaration of function 
'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration]
 printf("%d:%d\n", major(dev), minor(dev));
   ^
   mknod
/usr/bin/ld: /tmp/cc8kbEaP.o: in function `main':
get-real-console-linux.c:(.text.startup+0x62): undefined reference to `minor'
/usr/bin/ld: get-real-console-linux.c:(.text.startup+0x6f): undefined reference 
to `major'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:24: get-real-console-linux] Error 1

Bug#916069: transition: rocksdb

[GCS]

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

Hi RMs,

Minor transition of RocksDB 5.15.10 (Sid) -> 5.17.2 (experimental).
The only affected package is balboa which builds correctly with the
new version as well.

Thanks,
Laszlo/GCS

Bug#916068: Package: installation-reports

[Filippo Sidoti]

Package: installation-reports



Boot method: Stretch x64 DVD-1 on external USB DVD Drive

Image version: debian-9.5.0-amd64-DVD-1.iso

Date: November 10, 2018



Machine: Acer Aspire V15 Nitro Black Edition

Processor: i7-6700HQ

Memory: 16 GB

Partitions: 

root@filippo-VN7-592G:/# df -Tl

Filesystem Type 1K-blocks  Used Available Use% Mounted
on

udev   devtmpfs   8134936 0   8134936   0% /dev

tmpfs  tmpfs  1629328  9696   1619632   1% /run

/dev/sda7  ext4  65531436   8846488  53313124  15% /

tmpfs  tmpfs  8146624 4   8146620   1% /dev/shm

tmpfs  tmpfs 5120 4  5116   1%
/run/lock

tmpfs  tmpfs  8146624 0   8146624   0%
/sys/fs/cgroup

/dev/sda1  vfat 98304 56822 41482  58%
/boot/efi

/dev/sdb1  fuseblk  976761540 431768984 544992556  45%
/media/filippo/InternalHDD

tmpfs  tmpfs  162932448   1629276   1%
/run/user/1000



Output of lspci -knn (or lspci -nn):

root@filippo-VN7-592G:/# lspci -knn

00:00.0 Host bridge [0600]: Intel Corporation Skylake Host
Bridge/DRAM
Registers [8086:1910] (rev 07)

Subsystem: Acer Incorporated [ALI] Skylake Host Bridge/DRAM
Registers [1025:1039]

Kernel driver in use: skl_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe
Controller
(x16) [8086:1901] (rev 07)

Kernel driver in use: pcieport

Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation HD
Graphics
530 [8086:191b] (rev 06)

Subsystem: Acer Incorporated [ALI] HD Graphics 530 [1025:1039]

Kernel driver in use: i915

Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H
USB
3.0 xHCI Controller [8086:a12f] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H USB 3.0 xHCI
Controller [1025:1039]

Kernel driver in use: xhci_hcd

Kernel modules: xhci_pci

00:15.0 Signal processing controller [1180]: Intel Corporation
Sunrise
Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H Serial IO
I2C Controller [1025:1039]

Kernel driver in use: intel-lpss

Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation
Sunrise
Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H Serial IO
I2C Controller [1025:1039]

Kernel driver in use: intel-lpss

Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Sunrise
Point-H CSME HECI #1 [8086:a13a] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H CSME HECI
[1025:1039]

Kernel driver in use: mei_me

Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H
SATA
Controller [AHCI mode] [8086:a103] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H SATA
Controller [AHCI mode] [1025:1039]

Kernel driver in use: ahci

Kernel modules: ahci

00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI
Express Root Port #3 [8086:a112] (rev f1)

Kernel driver in use: pcieport

Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI
Express Root Port #4 [8086:a113] (rev f1)

Kernel driver in use: pcieport

Kernel modules: shpchp

00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI
Express Root Port #5 [8086:a114] (rev f1)

Kernel driver in use: pcieport

Kernel modules: shpchp

00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC
Controller [8086:a14e] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H LPC
Controller [1025:1039]

00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H 
PMC
[8086:a121] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H PMC
[1025:1039]

00:1f.3 Multimedia audio controller [0401]: Intel Corporation
Sunrise
Point-H HD Audio [8086:a170] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H HD Audio
[1025:1039]

Kernel driver in use: snd_hda_intel

Kernel modules: snd_hda_intel

00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus
[8086:a123] (rev 31)

Subsystem: Acer Incorporated [ALI] Sunrise Point-H SMBus
[1025:1039]

Kernel driver in use: i801_smbus

Kernel modules: i2c_i801

01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce
GTX
960M] [10de:139b] (rev a2)

Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M]
[1025:1039]

Kernel driver in use: nouveau

Kernel modules: nouveau

06:00.0 Network 

Bug#916066: csound regression: zir opcode appears entirely broken; hangs instrument

[Sam Hartman]

package: csound
version: 1:6.12.2~dfsg-1

I was experiencing strange failures with orchestras with csound 6.12 and
eventually I've tracked it down to the zir opcode to read a value from
zk-space at i-time.

It's fairly basic: the zir.csd from the csound examples fails to print
out anything  in the instrument that runs zir.
Based on what I've seen the instrument hangs (or aborts without a note
aborted message).

This is bad because it doesn't look like there's any way to read a
zk-value at I time without that opcode.
I guess you could play reinit games, but ugh.

Interestingly, Debian doesn't seem to be shipping zir.csd or really most
of the examples.
We used to, as I got them somewhere, and they're really useful.
I'm not seeing any license problems, so it would be cool if we either
shipped them or documented why not.
Anyway for completeness I'm attaching zir.csd.

This works on stretch.


; Select audio/midi flags here according to platform
; Audio out   Audio in
-odac   -iadc;;;RT audio I/O
; For Non-realtime ouput leave only the line below:
; -o zir.wav -W ;;; for file output any platform



; Initialize the global variables.
sr = 44100
kr = 4410
ksmps = 10
nchnls = 1

; Initialize the ZAK space.
; Create 1 a-rate variable and 1 k-rate variable.
zakinit 1, 1

; Instrument #1 -- a simple instrument.
instr 1
  ; Set the zk variable #1 to 32.594.
  ziw 32.594, 1
endin

; Instrument #2 -- prints out zk variable #1.
instr 2
  ; Read the zk variable #1 at i-rate.
  i1 zir 1

  ; Print out the value of zk variable #1.
  print i1
endin





; Play Instrument #1 for one second.
i 1 0 1
; Play Instrument #2 for one second.
i 2 0 1
e

Bug#916064: ext4magic FTBFS with glibc 2.28

[Adrian Bunk]

Source: ext4magic
Version: 0.3.2-10
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ext4magic.html

...
recover.c: In function 'recover_file':
recover.c:478:35: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
retval = mknod(helpname, type ,makedev(major, minor));
   ^~~
...
libtool: link: gcc -O2 -g -D_FILE_OFFSET_BITS=64 -g -O2 
-ffile-prefix-map=/build/1st/ext4magic-0.3.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ext4magic 
ext4magic-block.o ext4magic-dir_list.o ext4magic-ext4magic.o 
ext4magic-extent_db.o ext4magic-file_type.o ext4magic-hard_link_stack.o 
ext4magic-imap_search.o ext4magic-inode.o ext4magic-journal.o 
ext4magic-lookup_local.o ext4magic-magic_block_scan.o ext4magic-recover.o 
ext4magic-ring_buf.o ext4magic-util.o  -le2p -luuid -lblkid -lz -lbz2 -lmagic 
-lext2fs
/usr/bin/ld: ext4magic-recover.o: in function `recover_file':
./src/recover.c:478: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:449: ext4magic] Error 1

Bug#916067: fuse-umfuse-ext2 FTBFS with glibc 2.28

[Adrian Bunk]

Source: fuse-umfuse-ext2
Version: 0.4-1.1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fuse-umfuse-ext2.html

...
op_create.c: In function 'old_valid_dev':
op_create.c:45:9: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  return major(dev) < 256 && minor(dev) < 256;
 ^
op_create.c:45:29: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
  return major(dev) < 256 && minor(dev) < 256;
 ^
 mknod
op_create.c: In function 'new_encode_dev':
op_create.c:55:19: error: called object 'major' is not a function or function 
pointer
  unsigned major = major(dev);
   ^
op_create.c:55:11: note: declared here
  unsigned major = major(dev);
   ^
op_create.c:56:19: error: called object 'minor' is not a function or function 
pointer
  unsigned minor = minor(dev);
   ^
op_create.c:56:11: note: declared here
  unsigned minor = minor(dev);
   ^
make[3]: *** [Makefile:1014: umfuseext2_la-op_create.lo] Error 1

Bug#916065: fdutils FTBFS with glibc 2.28

[Adrian Bunk]

Source: fdutils
Version: 5.5-20060227-7
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fdutils.html

...
driveprm.c: In function 'getdrivenum':
driveprm.c:143:6: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  major(buf->st_rdev) != FLOPPY_MAJOR) {
  ^
driveprm.c:148:8: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
  num = minor( buf->st_rdev );
^
...
gcc -Wl,-z,relro -o getfdprm getfdprm.o -L. -lfdutils 
/usr/bin/ld: ./libfdutils.a(driveprm.o): in function `getdrivenum':
./src/driveprm.c:143: undefined reference to `major'
/usr/bin/ld: ./src/driveprm.c:148: undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:102: getfdprm] Error 1

Bug#916063: minify: output from ‘--version’ does not match upstream version

[Ben Finney]

Package: minify
Version: 2.3.5-2
Severity: normal

The ‘minify’ program does not correctly report its version.

=
$ minify --version
minify version master
=

For ‘minify’ version “2.3.5-2”, the output should show the upstream
version string:

=
$ minify --version
minify version 2.3.5
=

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

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

Versions of packages minify depends on:
ii  libc6  2.27-8

minify recommends no packages.

minify suggests no packages.

-- no debconf information

-- 
 \ “Sittin' on the fence, that's a dangerous course / You can even |
  `\   catch a bullet from the peace-keeping force” —Dire Straits, |
_o__)   _Once Upon A Time In The West_ |
Ben Finney 


signature.asc
Description: PGP signature

Bug#916062: cowdancer FTBFS with glibc 2.28

[Adrian Bunk]

Source: cowdancer
Version: 0.87
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cowdancer.html

...
qemuarch.c: In function 'qemu_create_arch_serialdevice':
qemuarch.c:60:16: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   consoledev = makedev(204, 64);
^~~
...
./qemuarch.c:60: undefined reference to `makedev'
/usr/bin/ld: ./qemuarch.c:62: undefined reference to `makedev'
/usr/bin/ld: qemubuilder-qemuarch.o: in function `qemu_create_arch_devices':
./qemuarch.c:85: undefined reference to `makedev'
/usr/bin/ld: ./qemuarch.c:87: undefined reference to `makedev'
/usr/bin/ld: ./qemuarch.c:89: undefined reference to `makedev'
/usr/bin/ld: qemubuilder-qemuarch.o:./qemuarch.c:91: more undefined references 
to `makedev' follow
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:996: qemubuilder] Error 1

Bug#916061: diod FTBFS with glibc 2.28

[Adrian Bunk]

Source: diod
Version: 1.0.24-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diod.html

...
ops.c: In function 'diod_mknod':
ops.c:808:38: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
 if (mknod (path_s (npath), mode, makedev (major, minor)) < 0
  ^~~
gcc -Wall -g -O2 -ffile-prefix-map=/build/1st/diod-1.0.24=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o diod 
diod.o ops.o exp.o ioctx.o fid.o xattr.o ../libdiod/libdiod.a 
../libnpclient/libnpclient.a ../libnpfs/libnpfs.a ../liblsd/liblsd.a -lwrap 
-lpthread -llua5.1  -lm -ldl -lmunge -lcap
/usr/bin/ld: ops.o: in function `diod_mknod':
./diod/ops.c:808: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:460: diod] Error 1

Bug#896811: stretch-pu: package icinga2/2.6.0-2+deb9u1

[Felix Geyer]

Hi Julien,

On 03.12.18 08:16, Julien Cristau wrote:

Looks fine to upload, go ahead.


Thanks, uploaded.

Cheers,
Felix

Bug#916051: ITP: birdtray -- system tray notifications for Thunderbird

[Adam Borowski]

On Sun, Dec 09, 2018 at 06:26:53PM +0100, Marek Mosiewicz wrote:
> W dniu 09.12.2018, nie o godzinie 18∶08 +0100, użytkownik Adam Borowski
> napisał:
> > * Package name: birdtray
> > * URL : https://github.com/gyunaev/birdtray

> >   Description : system tray notifications for Thunderbird

> > Birdtray provides systray notifications for Thunderbird.  It displays
> > the count of unread mail, hides the Thunderbird window when not in use,
> > and restores it on clicking the tray icon.  It also provides a context
> > menu with commands such as starting composing a new mail.
> > .
> > It is a nasty hack -- an external process looking at Thunderbird's
> > insides, it suffers from problems like noticing new mails only after a
> > delay, having to restart Thunderbird just to hide its window, etc --
> > you'd want to use an extension like firetray instead -- but, it is
> > likely that support for Thunderbird extensions will be dropped soon,
> > possibly by the time you read these words.

> Is it not simpler and much more effective to communicate with
> Thunderbird via XPCOM ?

That's part of XUL -- if that's gone, so goes XPCOM.  Both are gone from
Firefox since 57+, but have so far been retained in Thunderbird.  Alas,
upstream is deliberating whether to drop or not -- with signs randomly
pointing to droppage or not.  I don't know anything about Mozilla's internal
politics (I'm only blindly packaging something I need), but as I understand
it is a serious effort for the Thunderbird team to keep XUL after sabotage
done by Mozilla's quantumization -- and as undermanned as they are, it's
pretty likely they'll need to drop despite their wishes.

According to birdtray's upstream, the next best way to communicate is
accessing Mork (.msf) files.

I guess the upstream could explain more.  And yeah, it's better when a
packager knows something about the stuff he's packaging so if someone with a
clue would be willing to help, it'd be deeply appreciated.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.

Bug#916060: tuxmath: Starts and immediately closes

[Vangelis Skarmoutsos]

Package: tuxmath
Version: 2.0.3-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to start Tuxmath, it looks like it starts and immediately (msec)
closes.

When run from terminal it shows:

$ tuxmath
Initializing Tux4Kids-Common 0.1.1
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

(process:16281): librsvg-WARNING **: 19:54:36.690: element id="#default" does
not exist
Σφάλμα κατάτμησης (segmentation fault)



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

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

Versions of packages tuxmath depends on:
ii  libc62.27-8
ii  libsdl-image1.2  1.2.12-10
ii  libsdl-mixer1.2  1.2.12-15
ii  libsdl-net1.21.2.8-6
ii  libsdl1.2debian  1.2.15+dfsg2-4
ii  libt4k-common0   0.1.1-4
ii  tuxmath-data 2.0.3-4

tuxmath recommends no packages.

tuxmath suggests no packages.

-- no debconf information

Bug#916051: ITP: birdtray -- system tray notifications for Thunderbird

[Marek Mosiewicz]

W dniu 09.12.2018, nie o godzinie 18∶08 +0100, użytkownik Adam Borowski
napisał:
> Package: wnpp
> Severity: wishlist
> Owner: Adam Borowski 
> 
> * Package name: birdtray
>   Version : 1.4
>   Upstream Author : George Yunaev
> * URL : https://github.com/gyunaev/birdtray
> * License : GPL3
>   Programming Lang: C++, QT5
>   Description : system tray notifications for Thunderbird
>  Birdtray provides systray notifications for Thunderbird.  It
> displays the
>  count of unread mail, hides the Thunderbird window when not in use,
> and
>  restores it on clicking the tray icon.  It also provides a context
> menu
>  with commands such as starting composing a new mail.
>  .
>  It is a nasty hack -- an external process looking at Thunderbird's
>  insides, it suffers from problems like noticing new mails only after
> a
>  delay, having to restart Thunderbird just to hide its window, etc --
>  you'd want to use an extension like firetray instead -- but, it is
>  likely that support for Thunderbird extensions will be dropped soon,
>  possibly by the time you read these words.
Is it not simpler and much more effective to communicate with
Thunderbird via XPCOM ?
> 

Bug#916059: flatpak: Installing for user fails: open(O_TMPFILE): No Permission

[Maria]

Package: flatpak
Version: 1.0.6-1
Severity: normal

Dear Maintainer,

installing a flatpak as a user fails:

$ flatpak --user install flathub org.gnome.Platform/x86_64/3.26
Installing in user:
org.gnome.Platform/x86_64/3.26  flathub d01b14e467c2
org.freedesktop.Platform.VAAPI.Intel/x86_64/1.6 flathub 82006efc71d3
org.freedesktop.Platform.ffmpeg/x86_64/1.6  flathub d757f762489e
org.gnome.Platform.Locale/x86_64/3.26   flathub e730b2c2e992
Is this ok [y/n]: y
Installing for user: org.gnome.Platform/x86_64/3.26 from flathub
Fehler: Failed to installieren org.gnome.Platform/x86_64/3.26: open(O_TMPFILE):
Keine Berechtigung [No Permission]


If you have any questions I'll try to provide more information.
Thanks for your work and support!



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

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

Versions of packages flatpak depends on:
ii  bubblewrap 0.3.1-2
ii  libappstream-glib8 0.7.12-1
ii  libarchive13   3.2.2-5
ii  libc6  2.27-8
ii  libglib2.0-0   2.58.1-2
ii  libgpgme11 1.12.0-4
ii  libjson-glib-1.0-0 1.4.4-1
ii  libostree-1-1  2018.9.1-1
ii  libpolkit-gobject-1-0  0.105-22
ii  libseccomp22.3.3-3
ii  libsoup2.4-1   2.64.1-3
ii  libxau61:1.0.8-1+b2
ii  libxml22.9.4+dfsg1-7+b2
ii  xdg-desktop-portal 1.0.3-1

Versions of packages flatpak recommends:
ii  desktop-file-utils   0.23-4
ii  gtk-update-icon-cache3.24.1-2
ii  hicolor-icon-theme   0.17-2
ii  libpam-systemd   239-13
ii  p11-kit  0.23.14-2
ii  policykit-1  0.105-22
ii  shared-mime-info 1.10-1
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.0.2-2

Versions of packages flatpak suggests:
ii  avahi-daemon  0.7-4+b1

-- no debconf information

Bug#916058: chromium: Widevine not working in chromium 71

[Felix Geyer]

Package: chromium
Version: 71.0.3578.80-1
Tags: patch

Hi,

In chromium 71 the widevine adapter stopped working.

The widevine_cdm_version.h include seems to be hidden behind
#ifs that are only enabled when the Widevine CDM is bundled.

Attached is a debdiff that fixes this (adapted from the Arch Linux package).

Cheers,
Felix
--- a/debian/patches/fixes/widevine-revision.patch
+++ b/debian/patches/fixes/widevine-revision.patch
@@ -10,3 +10,14 @@
 +#define WIDEVINE_CDM_VERSION_STRING "undefined"
  
  #endif  // WIDEVINE_CDM_VERSION_H_
+--- a/chrome/common/chrome_content_client.cc
 b/chrome/common/chrome_content_client.cc
+@@ -99,7 +99,7 @@
+ // Registers Widevine CDM if Widevine is enabled, the Widevine CDM is
+ // bundled and not a component. When the Widevine CDM is a component, it is
+ // registered in widevine_cdm_component_installer.cc.
+-#if BUILDFLAG(BUNDLE_WIDEVINE_CDM) && 
!BUILDFLAG(ENABLE_WIDEVINE_CDM_COMPONENT)
++#if BUILDFLAG(ENABLE_WIDEVINE) && !BUILDFLAG(ENABLE_WIDEVINE_CDM_COMPONENT)
+ #define REGISTER_BUNDLED_WIDEVINE_CDM
+ #include "third_party/widevine/cdm/widevine_cdm_common.h"  // nogncheck
+ // TODO(crbug.com/663554): Needed for WIDEVINE_CDM_VERSION_STRING. Support

Bug#916056: dpkg-dev: dpkg-mergechangelogs strips vim modelines etc

[Chris Lamb]

Package: dpkg
Version: 1.19.2
Severity: normal

Hi,

The dpkg-mergechangelogs utility strips vim modelines (etc). I
discovered this in lintian which has a trailing "vim: et" at the end
of the file.

This is, of course, caused by:

  } elsif (m/^vim:/io) {
last; # skip Vim modelines at end of file

… in "scripts/Dpkg/Changelog/Debian.pm". I'm not sure what can be done
about this however without introducing a special mode/option to the
parsing code, however.

Thoughts?

§

A simple testcase for this issue is:

  --- a/scripts/t/merge_changelogs/c]h-a
  +++ b/scripts/t/merge_changelogs/ch-a
  @@ -90,3 +90,5 @@ test (1.0-1) unstable; urgency=low
 * Initial release. (Closes: #XX)
   
-- Raphaël Hertzog   Sun, 18 Apr 2010 17:37:46 +0200
  +
  +vim: et
  diff --git a/scripts/t/merge_changelogs/ch-b b/scripts/t/merge_changelogs/ch-b
  index 9eb7869..a74145f 100644
  --- a/scripts/t/merge_changelogs/ch-b
  +++ b/scripts/t/merge_changelogs/ch-b
  @@ -85,3 +85,5 @@ test (1.0-1) unstable; urgency=low
 * Initial release. (Closes: #XX)
   
-- Raphaël Hertzog   Sun, 18 Apr 2010 17:37:46 +0200
  +
  +vim: et
  diff --git a/scripts/t/merge_changelogs/ch-old 
b/scripts/t/merge_changelogs/ch-old
  index 12ee224..5ff7dd3 100644
  --- a/scripts/t/merge_changelogs/ch-old
  +++ b/scripts/t/merge_changelogs/ch-old
  @@ -83,3 +83,5 @@ test (1.0-1) unstable; urgency=low
 * Initial release. (Closes: #XX)
   
-- Raphaël Hertzog   Sun, 18 Apr 2010 17:37:46 +0200
  +
  +vim: et


Regards,

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

Bug#916057: intel-media-driver FTBFS on i386

[Adrian Bunk]

Source: intel-media-driver
Version: 18.3.0+dfsg1-1
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=intel-media-driver=i386=18.3.0%2Bdfsg1-1=1543883953=0

...
In file included from 
/<>/intel-media-driver-18.3.0+dfsg1/media_driver/linux/ult/libdrm_mock/mos_bufmgr_api_mock.c:32:
/usr/include/string.h:26:10: fatal error: bits/libc-header-start.h: No such 
file or directory
 #include 
  ^~
compilation terminated.
make[3]: *** 
[media_driver/linux/ult/libdrm_mock/CMakeFiles/drm_mock.dir/build.make:66: 
media_driver/linux/ult/libdrm_mock/CMakeFiles/drm_mock.dir/mos_bufmgr_api_mock.c.o]
 Error 1

Bug#916055: prometheus-node-exporter pulls disks out of standby every 15 minutes

[Etienne Dechamps]

Package: prometheus-node-exporter
Version: 0.16.0+ds-2
Severity: normal

Release 0.16.0+ds-2 of prometheus-node-exporter introduces a
regression in which, as long as the package is installed in the
machine, drives that are in stand by mode (i.e. spun down) will be
woken up every 15 minutes.

This is unsurprising because this release introduces a new scheduled
job that runs smartmon.sh every 15 minutes, and smartmon.sh will
happily wake up hard drives to check on them (it does not pass the
--nocheck=standby option to smartctl).

The clean fix would be to make smartmon.sh pass the --nocheck=standby
option to smartctl.

A more immediate workaround is to disable the feature entirely:

# systemctl disable prometheus-node-exporter-smartmon.timer

Bug#916053: ocfs2-tools FTBFS with glibc 2.28

[Adrian Bunk]

Source: ocfs2-tools
Version: 1.8.5-6
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocfs2-tools.html

...
In file included from o2cb_abi.c:52:
../include/ocfs2/ocfs2.h:222:2: error: unknown type name 'loff_t'
  loff_t d_off; /* Offset of structure in the file */
  ^~
make[2]: *** [../Postamble.make:40: o2cb_abi.o] Error 1

Bug#916054: procmeter3 FTBFS with glibc 2.28

[Adrian Bunk]

Source: procmeter3
Version: 3.6-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/procmeter3.html

...
longrun.c:41:24: error: unknown type name 'loff_t'; did you mean 'off_t'?
 static void read_cpuid(loff_t address, int *eax, int *ebx, int *ecx, int *edx) 
{
^~

Bug#916051: ITP: birdtray -- system tray notifications for Thunderbird

[Adam Borowski]

Package: wnpp
Severity: wishlist
Owner: Adam Borowski 

* Package name: birdtray
  Version : 1.4
  Upstream Author : George Yunaev
* URL : https://github.com/gyunaev/birdtray
* License : GPL3
  Programming Lang: C++, QT5
  Description : system tray notifications for Thunderbird
 Birdtray provides systray notifications for Thunderbird.  It displays the
 count of unread mail, hides the Thunderbird window when not in use, and
 restores it on clicking the tray icon.  It also provides a context menu
 with commands such as starting composing a new mail.
 .
 It is a nasty hack -- an external process looking at Thunderbird's
 insides, it suffers from problems like noticing new mails only after a
 delay, having to restart Thunderbird just to hide its window, etc --
 you'd want to use an extension like firetray instead -- but, it is
 likely that support for Thunderbird extensions will be dropped soon,
 possibly by the time you read these words.

Bug#916052: alsa-oss FTBFS with glibc 2.28

[Adrian Bunk]

Source: alsa-oss
Version: 1.1.6-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html

...
In file included from alsa-oss.c:736:
stdioemu.c:40:10: fatal error: libio.h: No such file or directory
 #include 
  ^
compilation terminated.
make[2]: *** [Makefile:517: alsa-oss.lo] Error 1

Bug#799626: RFP: beancount -- command line double-entry bookkeeping system

[Stefano Zacchiroli]

On Sun, Dec 09, 2018 at 05:23:35PM +0200, Martin Michlmayr wrote:
> Is the delay because of the test failures mentioned by Zack?

The main current issue is that several tests, at least when run under
sbuild/cowbuilder, enters infinite loops stat()-ing forever
"/PKG-INFO". I have been unable to find the cause, but it's somewhat
specific to the Debian build environment in conjunction with pytest.

In addition to that there are some test failures too, but they look easy
to fix (and the patches should probably be sent upstream for
integration).

I don't see myself having more time than I already devoted to this in
time for the next freeze. But if you're up to tackling this, I can
provide more info, e.g., I've a list of the affected tests, in case it
might help finding a pattern. The *general* pattern is that tests that
exec() stuff are impacted, but it's not specific enough (at least for
me) to pinpoint the issue.

Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Bug#916050: kdoctools FTCBFS: KF5::meinproc5: not found

[Helmut Grohne]

Source: kdoctools
Version: 5.51.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

kdoctools fails to cross build from source, because it fails to find
"KF5::meinproc5". That's supposed to be an imported location from a
prior built. Indeed meinproc5 resides in kdoctools5 on $PATH, so
Build-Depending on that package fixes this issue.

Unfortunately, it continues to fail in a different way: Running
docbookl10nhelper fails with an exec format error. Unfortunately, this
tool is not packaged anywhere and cannot be fixed with a dependency. I
cannot offer a solution for this one.

Please consider applying the attached patch anyway and close this bug
when doing so.

Helmut
diff --minimal -Nru kdoctools-5.51.0/debian/changelog 
kdoctools-5.51.0/debian/changelog
--- kdoctools-5.51.0/debian/changelog   2018-11-07 17:16:46.0 +0100
+++ kdoctools-5.51.0/debian/changelog   2018-12-07 17:23:18.0 +0100
@@ -1,3 +1,11 @@
+kdoctools (5.51.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Address FTCBFS: Build-Depends: kdoctools5  for meinproc5.
+(Closes: #-1)
+
+ -- Helmut Grohne   Fri, 07 Dec 2018 17:23:18 +0100
+
 kdoctools (5.51.0-1) unstable; urgency=medium
 
   * New upstream release (5.50.0).
diff --minimal -Nru kdoctools-5.51.0/debian/control 
kdoctools-5.51.0/debian/control
--- kdoctools-5.51.0/debian/control 2018-11-07 17:16:46.0 +0100
+++ kdoctools-5.51.0/debian/control 2018-12-07 17:23:18.0 +0100
@@ -14,6 +14,7 @@
libxml2-dev,
libxml2-utils,
libxslt1-dev,
+   kdoctools5 ,
pkg-kde-tools (>= 0.15.15ubuntu1~),
qtbase5-dev (>= 5.8.0~),
 Standards-Version: 4.1.4

Bug#916044: [git-buildpackage/master] Fix "was build" typos

[Chris Lamb]

tag 916044 pending
thanks

Date:   Sun Dec 9 17:52:22 2018 +0100
Author: Chris Lamb 
Commit ID: 9dc9f5eeb4087e9699f833081a6f59db8ca100b1
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=9dc9f5eeb4087e9699f833081a6f59db8ca100b1
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=9dc9f5eeb4087e9699f833081a6f59db8ca100b1

Fix "was build" typos

Closes: #916044

  

Bug#916048: nwchem FTBFS with glibc 2.28

[Adrian Bunk]

Source: nwchem
Version: 6.8+47+gitdf6c956-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nwchem.html

...
util_fadvise.c: In function 'util_fadvise':
util_fadvise.c:47:5: error: unknown type name 'loff_t'; did you mean 'off_t'?
 loff_t offset = 0;
 ^~
 off_t
util_fadvise.c:48:5: error: unknown type name 'loff_t'; did you mean 'off_t'?
 loff_t length = fd_stat.st_size;
 ^~
 off_t
make[3]: *** [../config/makefile.h:2699: 
/build/1st/nwchem-6.8+47+gitdf6c956/lib/LINUX64/libnwcutil.a(util_fadvise.o)] 
Error 1