Bug#906335: alot bug #906335

[Johannes Schauer]

Control: severity -1 important

Hi Jordan & Santiago,

first, lets make this bug non-RC. I cannot reproduce it, Jordan cannot
reproduce it, the buildd autobuilders cannot reproduce it:

https://buildd.debian.org/status/fetch.php?pkg=alot=all=0.7-2=1534543707=0

And the first build of reproducible cannot reproduce it:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/alot_0.7-2.rbuild.log.gz

But I do see the bug in the second build by the reproducible team:

https://tests.reproducible-builds.org/debian/logs/unstable/amd64/alot_0.7-2.build2.log.gz

Quoting Jordan Justen (2018-08-25 04:51:24)
> Hi. I'm trying to find a solution for this bug. Unfortunately, I can't
> seem to reproduce it on my system when building with sbuild.
> 
> Looking at the build logs on the reprucible-builds server:
> 
> https://tests.reproducible-builds.org/debian/logs/unstable/amd64/alot_0.7-2.build2.log.gz
> 
> It seems like the issues are often related to the tests/crypto_test.py
> tests. But, the error you flagged doesn't quite look the same, since
> it mentions failing to remove a file under /tmp. (Although, it does
> have gpg in the file name.)
> 
> Anyway, I'm wondering if you might have time to try a patch that just
> removes the crypto tests? I made a branch which adds the patch:
> 
> https://salsa.debian.org/python-team/applications/alot.git 906335-ftbfs
> 
> Or, since the issue happens for you with removing
> /tmp/tmprqJ8gE/S.gpg-agent.extra, do you have any ideas about why your /tmp
> could potentially behave differently?

I think this bug needs to be fixed. But I don't think it's very urgent, given
that the autobuilders seems to have had no problem building the package
recently. Maybe the bug can be reproduced by building the package the same way
that the reproducible scripts do it in their second pass?

Santiago, how were you able to reproduce the issue?

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#904286: f2fs-tools: Please package f2fs-tools v1.11.0

[Theodore Y. Ts'o]

I've submitted version 1.11.0-1 of f2fs-tools; it's currently in the
NEW queue.

The git tree for f2fs-tools is in Salsa:

https://salsa.debian.org/debian/f2fs-tools

The branches in the git tree are laid out to be DEP-14 compliant.  The
master branch contains the debian packaging, and there is a gbp.conf
file in the debian directory.  The f2fs-tools_1.11.0.orig.tar.gz was
generated using:

git archive --format tar --prefix f2fs-tools-1.11.0/ v1.11.0 | \
gzip -9n > f2fs-tools_1.11.0.orig.tar.gz

and is stored using pristine-tar in the pristine-tar branch.

The 1.11.0-1 f2fs-tools packages were build using git-buildpackage,
using the command "gbp buildpackage".  I'm using sbuild as my builder
so I have in my ~/.gbp.conf:

[buildpackage]
builder = sbuild -A -s -v -d unstable
export-dir = /tmp/gbp
purge = False

[tag]
sign-tags = True

And I have in my ~/.sbuildrc:

$build_arch_all = 1;
$distribution = 'unstable';
$source_only_changes = 1;

I fixed quite a few packaging issues while I was at it:

f2fs-tools (1.11.0-1) unstable; urgency=medium

  * New upstream release.   (Closes: #904286)
 - add sg_write_buffer for UFS firmware update in Android
 - wanted_sector_size to specify sector size explicitly
 - support fsverity feature bit
 - support lost+found feature
  * Install the library link files in /usr/lib where they belong
  * Replace the libf2fs0 package with libf2fs5 and libf2fs-format4
  * Fixed missing libblkid dependency in the shared library
  * Updated Standards compliance to 4.2.0
  * Added Theodore Ts'o as an uploader for the package

 -- Theodore Y. Ts'o   Fri, 24 Aug 2018 03:32:49 -0400

Cheers,

- Ted

Bug#907236: libinput: New upstream version available 1.11.902

[Hashem Nasarat]

Source: libinput
Version: 1.11.2-1
Severity: normal

Dear Maintainer,

Would you consider packaging libinput 1.11.902?
I believe this is one of the RC releases before 1.12 is released.


Why:

On my own system, I didn't want to wait so I followed the instructions here
and built an updated package:
https://www.debian.org/doc/manuals/maint-guide/update.en.html#newupstream

This fixes a longstanding regression for bluetooth thinkpad keyboards:
https://gitlab.freedesktop.org/libinput/libinput/issues/118


How:

I'd like to share one of the changes necessary to build this version (and
presumably 1.12 when it's released).

Initially I copied the debian directory from 1.11.2-1, but when running
debuild, lintian complained:

dh_missing: usr/share/libinput/30-vendor-aiptek.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-cyborg.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/10-generic-keyboard.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-synaptics.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/10-generic-trackball.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-cyapa.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-lenovo.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-hp.quirks exists in debian/tmp but is 
not installed to anywhere
dh_missing: usr/share/libinput/50-system-google.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/10-generic-lid.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-asus.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-dell.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-logitech.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-ibm.quirks exists in debian/tmp but is 
not installed to anywhere
dh_missing: usr/share/libinput/50-system-apple.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-wacom.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-chicony.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-alps.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/50-system-system76.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-elantech.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-microsoft.quirks exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-razer.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/libinput/30-vendor-huion.quirks exists in debian/tmp but 
is not installed to anywhere
dh_missing: missing files, aborting

I tracked these files down to this commit:
https://gitlab.freedesktop.org/libinput/libinput/commit/5792af9a5f4ae0bc11cd6d070ed643896c157f19


So my suggested change is:

diff --git a/debian/libinput-bin.install b/debian/libinput-bin.install
index b1390933..ba17202a 100644
--- a/debian/libinput-bin.install
+++ b/debian/libinput-bin.install
@@ -1 +1,2 @@
 lib/udev
+usr/share/libinput

Since libinput-bin "includes the udev quirks database and helpers."


With this change, the package builds, installs, and runs perfectly!

Thanks,
Hashem

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

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

Bug#907235: python3-scapy: Please provide package without large 'Recommends'

[Scott Moser]

Package: python3-scapy
Version: 2.4.0-2
Severity: normal

Dear Maintainer,

The current version (2.4.0-2) of python3-scapy has Recommends
 Recommends: tcpdump, ipython3, python3-matplotlib, python3-pyx, graphviz

Version 2.3.3-3 had those as 'Suggests'.  The change on "Recommends by
default" systems such as Ubuntu means that any package that wants to
Depend on scapy gets a huge stack of additional packages installed.

A fresh ubuntu server install means currently adding python3-scapy
will bring in 202 newly installed packages taking 583MB.

Could the Recommends be moved back to Suggests? Alternatively, a
package could be added 'scapy' that included the dependencies while the
python3-scapy would only provide the python library itself.

Thanks,
Scott

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

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

Versions of packages python3-scapy depends on:
ii  python3  3.6.6-1

Versions of packages python3-scapy recommends:
ii  graphviz2.40.1-3
ii  ipython35.5.0-1
pn  python3-matplotlib  
pn  python3-pyx 
ii  tcpdump 4.9.2-3

Versions of packages python3-scapy suggests:
ii  ebtables 2.0.10.4-3.5ubuntu5
pn  gv   
pn  hexer
ii  imagemagick  8:6.9.10.2+dfsg-3ubuntu2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.2+dfsg-3ubuntu2
pn  librsvg2-bin 
ii  python3-crypto   2.6.1-9build1
pn  python3-geoip
ii  sox  14.4.2-3
pn  tcpreplay
pn  wireshark

-- no debconf information

Bug#906901: debian-policy: Perl script shebang requirement is disturbing and inconsistent with rest of policy

[Jonathan Nieder]

Hi Russ,

Russ Allbery wrote:

> I'm looking for seconds for this patch to relax the current requirement
> back to a should.
[...]
> --- a/perl-policy.xml
> +++ b/perl-policy.xml
> @@ -533,7 +533,7 @@ $(MAKE) OPTIMIZE="-O2 -g -Wall"
>Script Magic
>  
>
> -All packaged perl programs must start with
> +All packaged perl programs should start with
>  #!/usr/bin/perl and may append such flags as
>  are required.
>
> diff --git a/policy/ch-files.rst b/policy/ch-files.rst
> index f31a3b4..bc87573 100644
> --- a/policy/ch-files.rst
> +++ b/policy/ch-files.rst
> @@ -186,7 +186,7 @@ All command scripts, including the package maintainer 
> scripts inside the
>  package and used by ``dpkg``, should have a ``#!`` line naming the shell
>  to be used to interpret them.
>  
> -In the case of Perl scripts this must be ``#!/usr/bin/perl``.
> +In the case of Perl scripts this should be ``#!/usr/bin/perl``.
>  
>  When scripts are installed into a directory in the system PATH, the
>  script name should not include an extension such as ``.sh`` or ``.pl``

Seconded.

Thanks,
Jonathan

Bug#906901: debian-policy: Perl script shebang requirement is disturbing and inconsistent with rest of policy

[Russ Allbery]

Dominic Hargreaves  writes:

> Clearly it should not be a must at this point given the deviation:
> though it still looks to me like a must ever since it was added to the
> perl policy, so if it is changed it should be changed in both places.

Hi all,

I'm looking for seconds for this patch to relax the current requirement
back to a should.  After that, I think the next step would be to introduce
automatic fixing of the #! line to debhelper, since that seems relatively
uncontroversial, and then we can reconsider this later after that's had a
chance to propagate through the archive.

--- a/perl-policy.xml
+++ b/perl-policy.xml
@@ -533,7 +533,7 @@ $(MAKE) OPTIMIZE="-O2 -g -Wall"
   Script Magic
 
   
-All packaged perl programs must start with
+All packaged perl programs should start with
 #!/usr/bin/perl and may append such flags as
 are required.
   
diff --git a/policy/ch-files.rst b/policy/ch-files.rst
index f31a3b4..bc87573 100644
--- a/policy/ch-files.rst
+++ b/policy/ch-files.rst
@@ -186,7 +186,7 @@ All command scripts, including the package maintainer 
scripts inside the
 package and used by ``dpkg``, should have a ``#!`` line naming the shell
 to be used to interpret them.
 
-In the case of Perl scripts this must be ``#!/usr/bin/perl``.
+In the case of Perl scripts this should be ``#!/usr/bin/perl``.
 
 When scripts are installed into a directory in the system PATH, the
 script name should not include an extension such as ``.sh`` or ``.pl``

> My personal view is that the rule is the correct one though. Installing
> a different perl for some application specific purpose is not uncommon -
> some people choose to not use the system perl at all when they are
> deploying a perl application - and they should be free to do that by
> putting a different perl in the path. That doesn't mean that they
> suddenly have to worry about parts of the packaged Debian system
> breaking.  I certainly couldn't name every part of Debian that I rely on
> that's written in perl!

Yes, this is my feeling as well.  It's all well and good to say that if
local administrators install their own Perl and things break, they get to
keep both pieces, but this seems unnecessarily fragile.  There are various
ways in which some other Perl could be added earlier in the PATH without
the administrator having any intention whatsoever to supplant system Perl
with it.  Consider, for instance, some local application written using
bleed Perl installed in some non-standard path, some other program that
with the best of intentions prepends the location of that application to
the PATH, and some program that this application happens to run without
even necessarily knowing it's written in Perl.  It seems better to ensure
that this sort of pattern just works.

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

Bug#901461: your mail

[Nick Morrott]

On 22 August 2018 at 20:00, Nick Morrott  wrote:

> I've just pushed the initial packaging to mentors ([1],[2]) for a
> review, if anyone's kind enough to have a look and has some time:

Having repacked the upstream source and respun the salsa repo, please
reclone and/or grab the new source packages from mentors:

  [1] https://mentors.debian.net/package/mu-editor
  [2] 
https://mentors.debian.net/debian/pool/main/m/mu-editor/mu-editor_1.0.0-1.dsc

This update tags the packages for non-free/{python,docs} - the
embedded pre-compiled Micropython firmware for the micro:bit doesn't
leave an alternative AFAICT at the moment).

The packaging would benefit from review and is currently without a
sponsor - I'll post an RFS to debian-python separately,

Thanks,
Nick

Bug#907234: gnupg warns that an email was signed by a key that expired... in 2018

[Alexandre Viau]

On 2018-08-24 09:54 PM, Alexandre Viau wrote:
> It looks like the signature should be accepted and that there should not
> be two entries for 0xDA82830E3CCC3A3A, as they are the same key. Am I
> missing something?

This might be relevant:
 - https://lists.gnupg.org/pipermail/gnupg-users/2004-January/021284.html

[[

> The second key correspond to a previous state of my key (before I
> added the second encryption key 1CF0D39E).
>
> Shouldn't the keyring merge these two keys ?

No, if you have a keyring with a duplicate key, the merge happens on
import.  Since the keys are already there, the way to fix it is:

* export both keys to a file
* delete the keys on the keyring.
* import the keys again.  They will be merged.

Make a backup first, just in case

]]

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#907234: gnupg warns that an email was signed by a key that expired... in 2018

[Alexandre Viau]

On 2018-08-24 09:37 PM, Nicolas Braud-Santoni wrote:
>> $ gpg -k aviau
>> gpg: please do a --check-trustd

So that would be one entry for pub 0xDA82830E3CCC3A3A, and the signature
expires on 2019-07-15:

>> pub   rsa4096/0xDA82830E3CCC3A3A 2014-04-01 [SC] [expires: 2019-07-15]
>>   Key fingerprint = E301 54F5 429F FBB9 B22E  49C2 DA82 830E 3CCC 3A3A
>> uid   [  full  ] Alexandre Viau 
>> uid   [  full  ] Alexandre Viau (ReAzem) 
>> uid   [  full  ] Alexandre Viau 
>>
That would be a second entry for pub 0xDA82830E3CCC3A3A, and the
signature expires on 2020-07-14:

>> pub   rsa4096/0xDA82830E3CCC3A3A 2014-04-01 [SC] [expires: 2020-07-14]
>>   Key fingerprint = E301 54F5 429F FBB9 B22E  49C2 DA82 830E 3CCC 3A3A
>> uid   [  full  ] Alexandre Viau 
>> uid   [  full  ] Alexandre Viau (ReAzem) 
>> uid   [  full  ] Alexandre Viau 

Now the subkeys, that all expire on 2020-07-14

>> sub   rsa4096/0xD8FF317310159602 2016-06-02 [E] [expires: 2020-07-14]
>> sub   rsa4096/0xA760A90DE6594708 2016-07-13 [A] [expires: 2020-07-14]
>> sub   rsa4096/0x8F2B113C6535C5A7 2016-07-15 [S] [expires: 2020-07-14]
It looks like the signature should be accepted and that there should not
be two entries for 0xDA82830E3CCC3A3A, as they are the same key. Am I
missing something?

> Please find attached the mail that exposed the bug.
> I am using neomutt as a mail reader, in cast that's relevant

Did you attach it? It does not appear on the bug page.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#907234: gnupg warns that an email was signed by a key that expired... in 2018

[Nicolas Braud-Santoni]

Package: gnupg
Version: 2.2.9-2
Severity: normal
Tags: upstream

Hi,

I noticed that gnupg reports that a particularly mail was signed by a key
that is expired... since 2019 :

> Problem signature from: Alexandre Viau 
>aka: Alexandre Viau (ReAzem) 
>aka: Alexandre Viau 
>created: Tue 21 Aug 2018 04:23:44 PM BST
> Warning: The key used to create the signature expired at: Mon 15 Jul 2019 
> 10:54:58 PM BST

My current time is set to the correct date, and here is the output of `gpg -k`:

> $ date
> Sat Aug 25 02:32:43 BST 2018
> 
> $ gpg -k aviau
> gpg: please do a --check-trustdb
> pub   rsa4096/0xDA82830E3CCC3A3A 2014-04-01 [SC] [expires: 2019-07-15]
>   Key fingerprint = E301 54F5 429F FBB9 B22E  49C2 DA82 830E 3CCC 3A3A
> uid   [  full  ] Alexandre Viau 
> uid   [  full  ] Alexandre Viau (ReAzem) 
> uid   [  full  ] Alexandre Viau 
> 
> pub   rsa4096/0xDA82830E3CCC3A3A 2014-04-01 [SC] [expires: 2020-07-14]
>   Key fingerprint = E301 54F5 429F FBB9 B22E  49C2 DA82 830E 3CCC 3A3A
> uid   [  full  ] Alexandre Viau 
> uid   [  full  ] Alexandre Viau (ReAzem) 
> uid   [  full  ] Alexandre Viau 
> sub   rsa4096/0xD8FF317310159602 2016-06-02 [E] [expires: 2020-07-14]
> sub   rsa4096/0xA760A90DE6594708 2016-07-13 [A] [expires: 2020-07-14]
> sub   rsa4096/0x8F2B113C6535C5A7 2016-07-15 [S] [expires: 2020-07-14]


Please find attached the mail that exposed the bug.
I am using neomutt as a mail reader, in cast that's relevant.


Best,

  nicoo

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

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

Versions of packages gnupg depends on:
ii  dirmngr 2.2.9-2
ii  gnupg-l10n  2.2.9-2
ii  gnupg-utils 2.2.9-2
ii  gpg 2.2.9-2
ii  gpg-agent   2.2.9-2
ii  gpg-wks-client  2.2.9-2
ii  gpg-wks-server  2.2.9-2
ii  gpgsm   2.2.9-2
ii  gpgv2.2.9-2

gnupg recommends no packages.

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

-- no debconf information

Bug#896666: qemu-system-x86: page allocation failure

[Russell Mosemann]

Package: src:linux
Version: 4.17.0-0.bpo.1
Severity: important

 
Aug 24 19:10:20 vhost004 kernel: qemu-system-x86: page allocation failure: 
order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO)
, nodemask=(null)
Aug 24 19:10:20 vhost004 kernel: qemu-system-x86 cpuset=emulator 
mems_allowed=0-1
Aug 24 19:10:20 vhost004 kernel: CPU: 8 PID: 16164 Comm: qemu-system-x86 
Tainted: G  I   4.17.0-0.bpo.1-amd64 #1 Debian
4.17.8-1~bpo9+1
Aug 24 19:10:20 vhost004 kernel: Hardware name: HP ProLiant DL380 G6, BIOS P62 
08/16/2015
Aug 24 19:10:20 vhost004 kernel: Call Trace:
Aug 24 19:10:20 vhost004 kernel:  dump_stack+0x5c/0x7b
Aug 24 19:10:20 vhost004 kernel:  warn_alloc+0xfc/0x180
Aug 24 19:10:20 vhost004 kernel:  __alloc_pages_slowpath+0xdc6/0xdd0
Aug 24 19:10:20 vhost004 kernel:  __alloc_pages_nodemask+0x212/0x250
Aug 24 19:10:20 vhost004 kernel:  kmalloc_order+0x14/0x40
Aug 24 19:10:20 vhost004 kernel:  kmalloc_order_trace+0x1d/0xa0
Aug 24 19:10:20 vhost004 kernel:  vmx_vm_alloc+0x19/0x20 [kvm_intel]
Aug 24 19:10:20 vhost004 kernel:  kvm_dev_ioctl+0xb0/0x690 [kvm]
Aug 24 19:10:20 vhost004 kernel:  do_vfs_ioctl+0xa2/0x620
Aug 24 19:10:20 vhost004 kernel:  ksys_ioctl+0x70/0x80
Aug 24 19:10:20 vhost004 kernel:  __x64_sys_ioctl+0x16/0x20
Aug 24 19:10:20 vhost004 kernel:  do_syscall_64+0x55/0x110
Aug 24 19:10:20 vhost004 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 24 19:10:20 vhost004 kernel: RIP: 0033:0x7fa30f3f0dd7
Aug 24 19:10:20 vhost004 kernel: RSP: 002b:7ffeaf4d0fa8 EFLAGS: 0246 
ORIG_RAX: 0010
Aug 24 19:10:20 vhost004 kernel: RAX: ffda RBX: ae01 
RCX: 7fa30f3f0dd7
Aug 24 19:10:20 vhost004 kernel: RDX:  RSI: ae01 
RDI: 000b
Aug 24 19:10:20 vhost004 kernel: RBP:  R08: 55ae8718db78 
R09: 0050
Aug 24 19:10:20 vhost004 kernel: R10: 0020 R11: 0246 
R12: 55ae88d219e0
Aug 24 19:10:20 vhost004 kernel: R13: 0002 R14: 0120 
R15: 
Aug 24 19:10:20 vhost004 kernel: Mem-Info:
Aug 24 19:10:20 vhost004 kernel: active_anon:29805 inactive_anon:34573 
isolated_anon:0
  active_file:97637 inactive_file:699754 
isolated_file:0
  unevictable:16667 dirty:44782 writeback:0 
unstable:0
  slab_reclaimable:55885 
slab_unreclaimable:471668
  mapped:26899 shmem:9863 pagetables:6033 
bounce:0
  free:97395 free_pcp:64 free_cma:0
Aug 24 19:10:20 vhost004 kernel: Node 0 active_anon:33640kB 
inactive_anon:52240kB active_file:323468kB inactive_file:1699488kB 
unevictable:65020kB isolated(anon):0kB isolated(file):0kB mapped:93060kB 
dirty:28636kB writeback:0kB shmem:38356kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 22528kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
Aug 24 19:10:20 vhost004 kernel: Node 1 active_anon:85580kB 
inactive_anon:86052kB active_file:67080kB inactive_file:1099528kB 
unevictable:1648kB isolated(anon):0kB isolated(file):0kB mapped:14536kB 
dirty:150492kB writeback:0kB shmem:1096kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
Aug 24 19:10:20 vhost004 kernel: Node 0 DMA free:15892kB min:12kB low:24kB 
high:36kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB 
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
Aug 24 19:10:20 vhost004 kernel: lowmem_reserve[]: 0 3486 48283 48283 48283

Aug 24 19:10:20 vhost004 kernel: Node 0 DMA32 free:200016kB min:3248kB 
low:6816kB high:10384kB active_anon:32744kB inactive_anon:50388kB 
active_file:311988kB inactive_file:1652628kB unevictable:62016kB 
writepending:28356kB present:3643520kB managed:3577952kB mlocked:62016kB 
kernel_stack:2720kB pagetables:9768kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
Aug 24 19:10:20 vhost004 kernel: lowmem_reserve[]: 0 0 44797 44797 44797
Aug 24 19:10:20 vhost004 kernel: Node 0 Normal free:44740kB min:41760kB 
low:87632kB high:133504kB active_anon:896kB inactive_anon:1852kB 
active_file:11480kB inactive_file:46860kB unevictable:3004kB writepending:280kB 
present:46661632kB managed:45872328kB mlocked:3004kB kernel_stack:2088kB 
pagetables:248kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Aug 24 19:10:20 vhost004 kernel: lowmem_reserve[]: 0 0 0 0 0
Aug 24 19:10:20 vhost004 kernel: Node 1 Normal free:128932kB min:45080kB 
low:94596kB high:144112kB active_anon:85276kB inactive_anon:86052kB 
active_file:66776kB inactive_file:1099080kB unevictable:1648kB 
writepending:150492kB present:50331644kB managed:49522936kB mlocked:1648kB 
kernel_stack:5640kB pagetables:14116kB bounce:0kB free_pcp:256kB local_pcp:0kB 
free_cma:0kB
Aug 24 19:10:20 vhost004 kernel: lowmem_reserve[]: 0 0 0 

Bug#891063:

[Chris Waters]

On Fri, Aug 24, 2018 at 6:24 AM Vincent Lefevre  wrote:
>
> On 2018-08-14 10:51:41 -0700, Chris Waters wrote:
> > Vincent Lefevre  writes:
> > > But in any case, the bug needs to be fixed.
> >
> > Yeah, I don't believe this can reasonably be called a bug. Emacs, like
> > a lot of big complex apps, can and does write to various parts of the
> > filesystem when used. There's a good chance that if you check your
> > home directory, you'll find more files owned by root. Files like
> > .emacs.d/recentf or .emacs.d/auto-save-list/* or .emacs-places.
>
> Wrong. The "su" command changes the value of HOME to the home of the
> root user. Thus there are no issues with these files.

Ok, sorry that I can't remember *all* the ways that "su" without a
login option is broken. Even with that, it's still plenty broken, as
you have observed, which is why the man page for su recommends *not
using it without the login option*. There are simply too many things
that can break when you have random environment variables left around
pointing who-knows-where.

Blaming emacs for a problem with su which is documented by the su man
page, though, is simply not reasonable. If you're going to insist on
using su instead of sudo, then it's your job to vet all your
environment variables to make sure you don't get this sort of
well-documented side effect. Which can affect all sorts of
programs--not just emacs.

Bug#905797: psmisc: FTBFS on hurd-i386

[Craig Small]

That's the idea. However there is a killall parsing issue to fix first.

 - Craig

On Sat, 25 Aug. 2018, 09:26 Svante Signell, 
wrote:

> Hi Craig,
>
> Now when you have solved the PATH_MAX problem your way, why not release
> a new version of psmisc?
>
> Thanks!
>
> On Mon, 2018-08-13 at 21:21 +1000, Craig Small wrote:
> > Hi,
> >   I've applied a slightly different fix to this problem, using a
> > combination of asprintf and defining PATH_MAX.
> >
> > https://gitlab.com/psmisc/psmisc/commit/d9ac11f92fdc4e96c818ce9d56e28
> > ef40a508336
> >
> >  -Craig
> >
> >
> >
> > On Fri, 10 Aug 2018 at 06:33 Svante Signell  > > wrote:
> > > Source: psmisc
> > > Version: 23.1-1
> > > Severity: important
> > > Tags: patch
> > > User: debian-h...@lists.debian.org
> > > Usertags: hurd
> > >
> > > Hi,
> > >
> > > Currently the latest version of psmisc fails to build from source
> > > and
> > > is flagged as out-of-date. This is due to usage of PATH_MAX, which
> > > is
> > > not defined on GNU/Hurd. The attached patch solve this problem by
> > > dynamically allocating space for the strings 'fullpath, linkpath
> > > and
> > > buf' in main() of src/pslog.c and freeing it when not needed any
> > > longer.
> > >
> > > Thanks!
> >
> > --
> > Craig Small https://dropbear.xyz/ csmall at :
> > dropbear.xyz
> > Debian GNU/Linuxhttps://www.debian.org/   csmall at :
> > debian.org
> > Mastodon: @smalls...@social.dropbear.xyz Twitter:
> > @smallsees
> > GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50
> > FEA5
>
-- 
Craig Small https://dropbear.xyz/ csmall at : dropbear.xyz
Debian GNU/Linuxhttps://www.debian.org/   csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees
GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#906617: autopkgtest: Please consider defining directory environment variables

[Paul Hardy]

Martin,

Thank you for your thoughtful reply.  Your email ended up in my spam
folder so I did not see it until now.

I am new to autopkgtest, and feel like I got things working with CI
testing in a convoluted way, that there is probably a cleaner
solution.  I looked through everything I could find on Debian, Ubuntu,
and your blog page to sort out an ideal way of using autopkgtest, and
do not think I am there yet...I think there still is some
clarification that could be added to the autopkgtest tutorial.

I DO want to have test scripts in the source tree that are written in
a general enough way to run on more than Debian and even more than
GNU/Linux, rather than writing custom test scripts for debian/tests if
possible.  That was part of my motivation.  My "make installcheck"
target works on many systems, but with Debian I had to avoid using it.
My "test/test-all" script works when invoked by "make installcheck",
when invoked in the source tree directly, and (now) when invoked from
the Debian CI test infrastructure.

This, for example, is my debian/tests/control file for my utfcheck package:[1]

Test-Command: cd test && progloc=`which utfcheck` &&
utfcheck_bindir=`dirname $progloc` ./test-all

I did that because it was only clear that I could find my program in
$PATH, not that I could count on it being available in /usr/bin as per
the FHS.  I thought it might be possible that CI testing could use an
intermediate location in a way I did not know.

My test scripts then invoke "${utfcheck_bindir}/utfcheck"; see for example [2].

If I could just change the control file to be

 Test-Command: make installcheck

That certainly would be simpler and more straightforward, but the test
environment would at least need $prefix to be set to override the
/usr/local default.  As a not-quite-ideal alternative,

 Test-Command: cd test && utfcheck_bindir=/usr/bin ./test-all

would at least be simpler; I just did not know from the autopkgtest
tutorial if it was possible.

That utfcheck package has a Debian bug filed against it.  I want to
fix the bug, but I also am hoping to improve some other things related
to Debian packaging when I do.  CI testing is one such thing.

On Sun, Aug 19, 2018 at 1:52 PM Martin Pitt  wrote:
>
> Hello Paul,
>
> Paul Hardy [2018-08-19  7:44 -0700]:
>> ...
> > By defining a few environment variables (like setting bindir to
> > /usr/bin), it will be more straightforward for people running
> > autopkgtest with Autotools to use a default "make installcheck"
> > target.
>
> Maybe, but I still don't believe this actually makes sense:
>
>  * Defining random variables with generic names like $bindir might also
>influence other tests or packages, which makes them work differently than
>they would in a normal OS install.

My thinking was to confine such environment variables to the GNU
standard directory variables; see [3] in the automake manual.

Note that the default value for $prefix with automake is usually
/usr/local.  With a Debian build, $prefix is set to /usr for final
installation of course.  It was at least $prefix that I was hoping to
have defined in the environment; everything else could fall into place
from that.

>  * autopkgtest is meant to be neutral to the test frame work that you use, as
>there are literally hundreds of them. There is no way it could maintain
>support for these.

And regretfully I do not know enough about that to understand the
implications, so I had to ask.

>  * This is too magic. Test commands should be very explicit and allow the
>developer to reproduce them step by step in a shell.

>
>  * For even `make` to work, you need at least a configured tree, and thus all
>the build dependencies, and most likely even need to build the package.
>autopkgtests should generally avoid that.
>
>  * I don't believe that setting static values for these variables even works
>for all automake projects. If they would, why are they even variables?

Most automake projects might not even implement an "installcheck"
target; it is not mandatory (neither is even a "check" target).  For
those that do, they would likely be working from the $prefix tree to
locate installed files.  I would rather not change the
prefix=/usr/local default, because I would like test scripts and such
work as expected on non-Debian systems also.

> > If we can expect that autopkgtest uses package executables in
> > /usr/bin, package data files in /usr/share/, likewise with
> > other FHS directories, could you update the tutorial page to mention
> > that?  Right now there is just an implication on that page from the
> > sample script that the binary executable will be in a directory in
> > $PATH.
>
> Right, as Debian policy mandates that user-executable programs should be in
> $PATH. So it's generally preferrable to call programs in $PATH without an
> explicit path, to make sure they are actually in the correct place.
> But note that there's also e. g. /sbin, or you might want 

Bug#903289: dh-make-elpa license and contribution

[Sean Whitton]

Hello,

On Mon 20 Aug 2018 at 03:34PM +0500, Lev Lamberov wrote:

> first, I'd like to stress that my motivation is making clear for
> myself several important (from my point of view) points and
> improvement of dh-make-elpa.

Thank you for your interest in working on dh-make-elpa!

> The point I'd like to focus attention to is licensing of dh-make-elpa.
> Currently, it is licensed under GPL-3+. It is based (and I'd say
> heavily based) on dh-make-perl, which is licensed under GPL-2-only.
> I've asked Sean Whitton about it on IRC and got the following answer:
>
> 23:45 < spwhitton> dogsleg: we don't actually derive code from dh-make-perl 
> -- dh-make-perl's code is included as a library.  so I think the licensing is 
> okay.
> 23:45 < spwhitton> dogsleg: there are very small number of lines that are 
> actually copied directly; probably less than copyrightable.

Please ask participants' permission before quoting from IRC channels
into permanently-recorded formats like the Debian BTS (in this case, I
would have given permission).

> I cannot agree with this summing-up. Namely, I cannot understand what
> proportion of code should be to be considered copyrightable.

IANAL, but AIUI, code that is less than ten lines long is not
copyrightable -- the FSF do not require copyright assignment for
contributions to GNU projects that are less than ten lines.

Until reading your e-mail, I thought that the actual code copied from
src:dh-make-perl into src:dh-make-elpa was less than ten lines.  But it
looks like I was wrong about that.

> As it is put in manpages of dh-make-elpa(1), "a great deal of the
> library code used by dh-make-elpa, and its object-oriented structure,
> comes from dh-make-perl(1), written and maintained by the Debian Perl
> Group."
>
> First, it is not clear what constitutes a library here.

What this text means is that dh-make-elpa imports dh-make-perl as a
library.  That code is not contained in src:dh-make-elpa.

> Second, classes from DhMakePerl are in fact used in DhMakeELPA (as
> base classes):
>
> $ rgrep DhMakePerl
> lib/DhMakeELPA/Config.pm:use base 'DhMakePerl::Config';
> lib/DhMakeELPA/Command/Packaging.pm:use base 'DhMakePerl::Command::Packaging';

According to the FSF,[1] the GPLv3 is not compatible with the GPLv2.  So
it looks like I am not allowed to derive classes from DhMakePerl and
license the new classes as GPL-3+.

I've updated d/copyright to license dh-make-elpa under GPL-2 only, since
that's all that is permitted.

> Nevertheless, let's take a look into some code. For example,
> DhMakeELPA.pm. It contains only one subroutine, run, and the
> difference with the same subroutine from DhMakePerl.pm is as follows:
>
> sub run {
>  my ( $class, %c ) = @_;
>
>  unless ( $c{cfg} ) {
> -my $cfg = DhMakeELPA::Config->new;
> +my $cfg = DhMakePerl::Config->new;
>  $cfg->parse_command_line_options;
> +$cfg->parse_config_file;
>  $c{cfg} = $cfg;
>  }
>
>  my $cmd_mod = $c{cfg}->command;
>  $cmd_mod =~ s/-/_/g;
> -require "DhMakeELPA/Command/$cmd_mod.pm";
> +require "DhMakePerl/Command/$cmd_mod.pm";
>
>  $cmd_mod =~ s{/}{::}g;
> -$cmd_mod = "DhMakeELPA::Command::$cmd_mod";
> +$cmd_mod = "DhMakePerl::Command::$cmd_mod";
>
>  my $self = $cmd_mod->new( \%c );
>
>  return $self->execute;
>  }
>
> So, since almost the whole DhMakeELPA.pm is an edited copy of
> DhMakePerl, is this part of code copyrightable? If so, then it should
> come under GPL-2-only umbrella, not GPL-3+.

I don't know if this counts as copyrightable or not.  But the point is
moot, because of the above.

[1]  https://www.gnu.org/licenses/license-list.en.html "Please note that
GPLv3 is not compatible with GPLv2 by itself."

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#829570: webrtc-audio-processing 0.3 is unbuildable on non-linux archs

[Svante Signell]

On Sun, 2016-07-03 at 13:00 -0300, Felipe Sateler wrote:
> Dear Hurd and BSD porters,
> 
> The latest upload of webrtc-audio-processing in unstable does not
> build on non-linux archs. This new version is required by pulseaudio
> 9, so it will not build as well.
> 
> My guess is that the build failures are only due to lack of
> appropriate checks in configure (ie, not any real incompatibility).
> If the porters could prepare such a patch, I'm more than happy to
> apply locally and forward upstream. I currently lack time to try to
> do this myself.

There is a patch for that package available already:
See #829570 from 04 Jul 2016.

Thanks!

Bug#716538: [Mayhem] Bug report on mrtrix: read_ximg crashes with exit status 139

[Yaroslav Halchenko]

Thanks for the report and sorry for the silent.  I can only confirm ATM
that even the most recent in 0.2.x series 0.2.13 is exhibiting the same issue:

$> ./crash.sh
./crash.sh: line 22: 22040 Segmentation fault  env -i MALLOC_CHECK_=0 $GDB 
/usr/lib/mrtrix/bin/read_ximg "`cat $DIR/argv_1.symb`" "`cat $DIR/argv_2.symb`" 
"`cat $DIR/argv_3.symb`" < "$DIR/file___dev__stdin.symb"

btw -- what tool was used to  produce those bundles with the
troubleshooting information etc (I guess it wasn't done manually)

?

On Wed, 10 Jul 2013, Alexandre Rebert wrote:

> Package: mrtrix
> Version: 0.2.10-2
> Severity: normal
> User: may...@forallsecure.com
> Usertags: mayhem

> read_ximg crashes with exit status 139. We confirmed the crash by
> re-running it in a fresh debian unstable installation.

> The attachment [1] contains a testcase (under ./crash) crashing the
> program. It ensures that you can easily reproduce the bug. Additionally,
> under ./crash_info/, we include more information about the crash such as
> a core dump, the dmesg generated by the crash, and its output.

> Regards,
> The Mayhem Team (Alexandre Rebert, Thanassis Avgerinos, Sang Kil Cha, David 
> Brumley, Manuel Egele)
> Cylab, Carnegie Mellon University

> [1] 
> http://www.forallsecure.com/bug-reports/94e4161bb7a57e7125482b1caaa83d8dc1240a2a/full_report

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#905797: psmisc: FTBFS on hurd-i386

[Svante Signell]

Hi Craig,

Now when you have solved the PATH_MAX problem your way, why not release
a new version of psmisc?

Thanks!

On Mon, 2018-08-13 at 21:21 +1000, Craig Small wrote:
> Hi,
>   I've applied a slightly different fix to this problem, using a
> combination of asprintf and defining PATH_MAX.
> 
> https://gitlab.com/psmisc/psmisc/commit/d9ac11f92fdc4e96c818ce9d56e28
> ef40a508336
> 
>  -Craig
> 
> 
> 
> On Fri, 10 Aug 2018 at 06:33 Svante Signell  > wrote:
> > Source: psmisc
> > Version: 23.1-1
> > Severity: important
> > Tags: patch
> > User: debian-h...@lists.debian.org
> > Usertags: hurd
> > 
> > Hi,
> > 
> > Currently the latest version of psmisc fails to build from source
> > and
> > is flagged as out-of-date. This is due to usage of PATH_MAX, which
> > is
> > not defined on GNU/Hurd. The attached patch solve this problem by
> > dynamically allocating space for the strings 'fullpath, linkpath
> > and
> > buf' in main() of src/pslog.c and freeing it when not needed any
> > longer.
> > 
> > Thanks!
> 
> -- 
> Craig Small https://dropbear.xyz/ csmall at :
> dropbear.xyz
> Debian GNU/Linuxhttps://www.debian.org/   csmall at :
> debian.org
> Mastodon: @smalls...@social.dropbear.xyz Twitter:
> @smallsees  
> GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50
> FEA5

Bug#907229: kdesvn: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:kdesvn
Version: 2.0.0-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with kf5
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure --buildsystem=kf5 -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note:   template 
argument deduction/substitution failed:
/<>/src/svnfrontend/blamedisplay.cpp:207:73: note:   candidate 
expects 3 arguments, 4 provided
 connect(ac, SIGNAL(triggered()), this, SLOT(slotShowCurrentCommit()));
 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1,
 from 
/<>/src/ksvnwidgets/../ksvnwidgets/ksvndialog.h:21,
 from /<>/src/svnfrontend/blamedisplay.h:22,
 from /<>/src/svnfrontend/blamedisplay.cpp:20:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType) [with Func1 = const char*; Func2 = const char*]':
/<>/src/svnfrontend/blamedisplay.cpp:207:73:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: error: no type named 
'type' in 'struct std::enable_if'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note:   template 
argument deduction/substitution failed:
/<>/src/svnfrontend/blamedisplay.cpp:207:73: note:   candidate 
expects 3 arguments, 4 provided
 connect(ac, SIGNAL(triggered()), this, SLOT(slotShowCurrentCommit()));
 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1,
 from 
/<>/src/ksvnwidgets/../ksvnwidgets/ksvndialog.h:21,
 from /<>/src/svnfrontend/blamedisplay.h:22,
 from /<>/src/svnfrontend/blamedisplay.cpp:20:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note:   template 

Bug#907227: equalx: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:equalx
Version: 0.7.1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
/usr/bin/qmake -qt5 -makefile -nocache QMAKE_LFLAGS_RELEASE="-Wl,-z,relro" 
QMAKE_CFLAGS_RELEASE="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
QMAKE_CXXFLAGS_RELEASE="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
QMAKE_CPPFLAGS_RELEASE="-Wdate-time -D_FORTIFY_SOURCE=2" PREFIX=/usr/bin
Info: creating stash file /<>/.qmake.stash
Project MESSAGE: Qt version: 5.11.1
WARNING: target.path is not defined: install target not created

make[1]: Leaving directory '/<>'
   dh_auto_build -a -O--parallel
make -j1
make[1]: Entering directory '/<>'
/usr/lib/qt5/bin/uic ui/mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic ui/dialogPreferences.ui -o ui_dialogPreferences.h
/usr/lib/qt5/bin/uic ui/dialogAbout.ui -o ui_dialogAbout.h
/usr/lib/qt5/bin/uic ui/dialogReplace.ui -o ui_dialogReplace.h
/usr/lib/qt5/bin/uic ui/widgetFind.ui -o ui_widgetFind.h
/usr/lib/qt5/bin/uic ui/BookmarksPanel/DialogPreferencesFolder.ui -o 
ui_DialogPreferencesFolder.h
/usr/lib/qt5/bin/uic ui/BookmarksPanel/DialogPreferencesBookmark.ui -o 
ui_DialogPreferencesBookmark.h
/usr/lib/qt5/bin/uic ui/BookmarksPanel/BookmarksWidget.ui -o 
ui_BookmarksWidget.h
/usr/lib/qt5/bin/uic ui/HistoryPanel/HistoryWidget.ui -o ui_HistoryWidget.h
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o File.o src/File.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o main.o src/main.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o MainWindow.o 
src/MainWindow.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o LatexHighlighter.o 
src/LatexHighlighter.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem 

Bug#907230: kmail-account-wizard: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:kmail-account-wizard
Version: 4:17.12.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/<>'
dh_testdir  # [-a]
dh_auto_configure '--buildsystem=kf5' --parallel  # [-a]
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

 static bool disconnect(const QObject *sender, const char *signal,
 ^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:337:17: note:   no known 
conversion for argument 1 from 'QAction*' to 'const QObject*'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:339:17: note: candidate: 
'static bool QObject::disconnect(const QObject*, const QMetaMethod&, const 
QObject*, const QMetaMethod&)'
 static bool disconnect(const QObject *sender, const QMetaMethod ,
 ^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:339:17: note:   no known 
conversion for argument 1 from 'QAction*' to 'const QObject*'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:341:17: note: candidate: 
'bool QObject::disconnect(const char*, const QObject*, const char*) const'
 inline bool disconnect(const char *signal = nullptr,
 ^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:341:17: note:   candidate 
expects 3 arguments, 4 provided
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:344:17: note: candidate: 
'bool QObject::disconnect(const QObject*, const char*) const'
 inline bool disconnect(const QObject *receiver, const char *member = 
nullptr) const
 ^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:344:17: note:   candidate 
expects 2 arguments, 4 provided
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:346:17: note: candidate: 
'static bool QObject::disconnect(const QMetaObject::Connection&)'
 static bool disconnect(const QMetaObject::Connection &);
 ^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:346:17: note:   candidate 
expects 1 argument, 4 provided
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:353:24: note: candidate: 
'template static bool QObject::disconnect(const 
typename QtPrivate::FunctionPointer::Object*, Func1, const typename 
QtPrivate::FunctionPointer::Object*, Func2)'
 static inline bool disconnect(const typename 
QtPrivate::FunctionPointer::Object *sender, Func1 signal,
^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:353:24: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static bool QObject::disconnect(const 
typename QtPrivate::FunctionPointer::Object*, Func1, const typename 
QtPrivate::FunctionPointer::Object*, Func2) [with Func1 = int; Func2 = 
int]':
/<>/src/dialog.cpp:112:77:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:353:24: error: no type named 
'Object' in 'struct QtPrivate::FunctionPointer'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:370:24: note: candidate: 
'template static bool QObject::disconnect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, void**)'
 static inline bool disconnect(const typename 
QtPrivate::FunctionPointer::Object *sender, Func1 signal,
^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:370:24: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static bool QObject::disconnect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, void**) [with 
Func1 = int]':
/<>/src/dialog.cpp:112:77:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:370:24: error: no type named 
'Object' in 'struct QtPrivate::FunctionPointer'
/<>/src/dialog.cpp:113:70: error: incomplete type 'QAction' used 
in nested name specifier
 connect(helpMenu->action(KHelpMenu::menuHelpContents), 
::triggered, this, ::slotOpenHelp);

Bug#907231: ktp-contact-list: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:ktp-contact-list
Version: 17.08.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/<>'
dh_testdir  # [-a]
dh_auto_configure '--buildsystem=kf5' --parallel  # [-a]
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

/<>/main-widget.cpp:478:42: warning: 'QMenu* 
KMainWindow::helpMenu(const QString&, bool)' is deprecated 
[-Wdeprecated-declarations]
 settingsButtonMenu->addMenu(helpMenu());
  ^
In file included from /usr/include/KF5/KXmlGui/kxmlguiwindow.h:33,
 from /usr/include/KF5/KXmlGui/KXmlGuiWindow:1,
 from /<>/main-widget.h:32,
 from /<>/main-widget.cpp:25:
/usr/include/KF5/KXmlGui/kmainwindow.h:191:31: note: declared here
 KXMLGUI_DEPRECATED QMenu *helpMenu(const QString  = QString(),
   ^~~~
[ 70%] Building CXX object 
CMakeFiles/ktp-contactlist.dir/global-presence-chooser.cpp.o
/usr/bin/c++  -DHAVE_KPEOPLE -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB 
-DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/obj-x86_64-linux-gnu/ktp-contactlist_autogen/include 
-isystem /usr/include/KF5/KPeople -isystem /usr/include/KF5 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOCore -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem 
/usr/include/KF5/KConfigCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
 /usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/KCompletion -isystem 
/usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KCMUtils -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml 
-isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KNotifyConfig 
-isystem /usr/include/KF5/KDBusAddons -isystem /usr/include/KF5/KI18n -isystem 
/usr/include/KF5/KIconThemes -isystem /usr/include/KF5/KXmlGui -isystem 
/usr/include/KF5/KNotifications -isystem /usr/include/KF5/KWindowSystem 
-isystem /usr/include/telepathy-qt5 -isystem /usr/include/KF5/KWallet -isystem 
/usr/include/TelepathyLoggerQt -isystem /usr/include/glib-2.0 -isystem 
/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-e
 xceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security 
-Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -fvisibility=hidden 
-fvisibility-inlines-hidden   -fPIC -fexceptions -std=gnu++11 -o 
CMakeFiles/ktp-contactlist.dir/global-presence-chooser.cpp.o -c 
/<>/global-presence-chooser.cpp
[ 73%] Building CXX object 
CMakeFiles/ktp-contactlist.dir/dialogs/remove-contact-dialog.cpp.o
/usr/bin/c++  -DHAVE_KPEOPLE -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB 
-DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/obj-x86_64-linux-gnu/ktp-contactlist_autogen/include 
-isystem /usr/include/KF5/KPeople -isystem /usr/include/KF5 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 

Bug#907226: cutesdr: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:cutesdr
Version: 1.20-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_auto_configure -a
qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
QMAKE_LFLAGS_RELEASE=-Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-z,relro QMAKE_STRIP=: 
PREFIX=/usr
Info: creating stash file /<>/.qmake.stash
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
/usr/lib/qt5/bin/uic unixforms/mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic unixforms/sdrdiscoverdlg.ui -o ui_sdrdiscoverdlg.h
/usr/lib/qt5/bin/uic unixforms/sounddlg.ui -o ui_sounddlg.h
/usr/lib/qt5/bin/uic unixforms/sdrsetupdlg.ui -o ui_sdrsetupdlg.h
/usr/lib/qt5/bin/uic unixforms/ipeditframe.ui -o ui_ipeditframe.h
/usr/lib/qt5/bin/uic unixforms/editnetdlg.ui -o ui_editnetdlg.h
/usr/lib/qt5/bin/uic unixforms/displaydlg.ui -o ui_displaydlg.h
/usr/lib/qt5/bin/uic unixforms/sliderctrl.ui -o ui_sliderctrl.h
/usr/lib/qt5/bin/uic unixforms/demodsetupdlg.ui -o ui_demodsetupdlg.h
/usr/lib/qt5/bin/uic unixforms/testbench.ui -o ui_testbench.h
/usr/lib/qt5/bin/uic unixforms/aboutdlg.ui -o ui_aboutdlg.h
/usr/lib/qt5/bin/uic unixforms/noiseprocdlg.ui -o ui_noiseprocdlg.h
/usr/lib/qt5/bin/uic unixforms/chatdialog.ui -o ui_chatdialog.h
/usr/lib/qt5/bin/uic unixforms/recordsetupdlg.ui -o ui_recordsetupdlg.h
/usr/lib/qt5/bin/uic unixforms/filetxdlg.ui -o ui_filetxdlg.h
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o main.o gui/main.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o sounddlg.o gui/sounddlg.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o sdrsetupdlg.o 
gui/sdrsetupdlg.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 

Bug#907233: qtscrob: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:qtscrob
Version: 0.11+git-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch -Dsrc
   dh_testdir -a -O-Dsrc
   dh_update_autotools_config -a -O-Dsrc
   dh_autoreconf -a -O-Dsrc
   dh_auto_configure -a -O-Dsrc
cd src && qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro 
-Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr
Info: creating stash file /<>/qtscrob-0.11+git/src/.qmake.stash
Project MESSAGE: Qt version used: 5.11.1
   dh_auto_build -a -O-Dsrc
cd src && make -j1
make[1]: Entering directory '/<>/qtscrob-0.11+git/src'
cd lib/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile 
/<>/qtscrob-0.11+git/src/lib/lib.pro 'QMAKE_CFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CXXFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now' 'QMAKE_LFLAGS_DEBUG=-Wl,-z,relro 
-Wl,-z,now' QMAKE_STRIP=: PREFIX=/usr ) && make -f Makefile 
Project MESSAGE: Scrobbler will be installed in /usr

[... snipped ...]

g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_NETWORK_LIB 
-DQT_XML_LIB -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild/.moc -isystem 
/usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
build/.o/moc_libscrobble.o build/.moc/moc_libscrobble.cpp
/usr/lib/qt5/bin/moc -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB --include build/.moc/moc_predefs.h 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/<>/qtscrob-0.11+git/src/lib -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtSql 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/c++/8 
-I/usr/include/x86_64-linux-gnu/c++/8 -I/usr/include/c++/8/backward 
-I/usr/lib/gcc/x86_64-linux-gnu/8/include -I/usr/local/include 
-I/usr/lib/gcc/x86_64-linux-gnu/8/include-fixed -I/usr/include/x86_64-linux-gnu 
-I/usr/include submit.h -o build/.moc/moc_submit.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_NETWORK_LIB 
-DQT_XML_LIB -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild/.moc -isystem 
/usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
build/.o/moc_submit.o build/.moc/moc_submit.cpp
/usr/lib/qt5/bin/moc -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB --include build/.moc/moc_predefs.h 

Bug#907232: pep8-simul: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:pep8-simul
Version: 8.1.3+ds1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_auto_configure -a
qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" 
"QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr
Info: creating stash file /<>/pep8-simul-8.1.3+ds1/.qmake.stash
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>/pep8-simul-8.1.3+ds1'
/usr/lib/qt5/bin/uic mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic sourcecodepane.ui -o ui_sourcecodepane.h
/usr/lib/qt5/bin/uic objectcodepane.ui -o ui_objectcodepane.h
/usr/lib/qt5/bin/uic cpupane.ui -o ui_cpupane.h
/usr/lib/qt5/bin/uic assemblerlistingpane.ui -o ui_assemblerlistingpane.h
/usr/lib/qt5/bin/uic memorytracepane.ui -o ui_memorytracepane.h
/usr/lib/qt5/bin/uic memorydumppane.ui -o ui_memorydumppane.h
/usr/lib/qt5/bin/uic inputpane.ui -o ui_inputpane.h
/usr/lib/qt5/bin/uic outputpane.ui -o ui_outputpane.h
/usr/lib/qt5/bin/uic terminalpane.ui -o ui_terminalpane.h
/usr/lib/qt5/bin/uic redefinemnemonicsdialog.ui -o ui_redefinemnemonicsdialog.h
/usr/lib/qt5/bin/uic byteconverterhex.ui -o ui_byteconverterhex.h
/usr/lib/qt5/bin/uic byteconverterdec.ui -o ui_byteconverterdec.h
/usr/lib/qt5/bin/uic byteconverterchar.ui -o ui_byteconverterchar.h
/usr/lib/qt5/bin/uic byteconverterbin.ui -o ui_byteconverterbin.h
/usr/lib/qt5/bin/uic helpdialog.ui -o ui_helpdialog.h
/usr/lib/qt5/bin/uic listingtracepane.ui -o ui_listingtracepane.h
/usr/lib/qt5/bin/uic aboutpep.ui -o ui_aboutpep.h
/usr/lib/qt5/bin/uic byteconverterinstr.ui -o ui_byteconverterinstr.h
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_WEBENGINEWIDGETS_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
-DQT_WEBENGINECORE_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_WEBCHANNEL_LIB 
-DQT_QML_LIB -DQT_NETWORK_LIB -DQT_POSITIONING_LIB -DQT_CORE_LIB -I. -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebEngineWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebEngineCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebChannel -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPos
 itioning -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem 
/usr/include/libdrm -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
main.o main.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_WEBENGINEWIDGETS_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
-DQT_WEBENGINECORE_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_WEBCHANNEL_LIB 
-DQT_QML_LIB -DQT_NETWORK_LIB -DQT_POSITIONING_LIB -DQT_CORE_LIB -I. -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebEngineWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebEngineCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebChannel -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPos
 itioning -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem 
/usr/include/libdrm -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
mainwindow.o mainwindow.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/pep8-simul-8.1.3+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 

Bug#907228: kaffeine: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:kaffeine
Version: 2.0.15-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with kf5
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure --buildsystem=kf5 -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

[ 36%] Building CXX object src/CMakeFiles/kaffeine.dir/iso-codes.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DKCOREADDONS_LIB 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB 
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src 
-I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src/kaffeine_autogen/include 
-I/<>/include -I/<>/obj-x86_64-linux-gnu -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KXmlGui 
-isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /
 usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigWidgets -isystem 
/usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KI18n -isystem 
/usr/include/KF5/Solid -isystem /usr/include/KF5/KIOCore -isystem 
/usr/include/KF5/KService -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem 
/usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/KCompletion -isystem 
/usr/include/KF5/KBookmarks -isystem /usr/include/KF5/KItemViews -isystem 
/usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KDBusAddons  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x 
-fno-operator-names -fno-exceptions -Wall -Wextra -
 Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith 
-Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla 
-Wdate-time -fvisibility=hidden -fvisibility-inlines-hidden   -fPIC 
-std=gnu++11 -o CMakeFiles/kaffeine.dir/iso-codes.cpp.o -c 
/<>/src/iso-codes.cpp
[ 38%] Building CXX object src/CMakeFiles/kaffeine.dir/dvb/dvbcam_linux.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DKCOREADDONS_LIB 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB 
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src 
-I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src/kaffeine_autogen/include 
-I/<>/include -I/<>/obj-x86_64-linux-gnu -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KXmlGui 
-isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /
 usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigWidgets -isystem 
/usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KI18n -isystem 
/usr/include/KF5/Solid -isystem /usr/include/KF5/KIOCore -isystem 
/usr/include/KF5/KService -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 

Bug#907225: Man pages for glslang

[Brett Johnson]

Package: glslang
Version: 7.8.2853-1
Severity: normal
Tags: patch

Attached is a patch with man pages for spirv-remap and
glslangValidator. That should allow you to remove the
glslang-tools.lintian-overrides file.
diff --git a/debian/changelog b/debian/changelog
index 88cb240d..90b4abc9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,9 @@ glslang (7.8.2853-2) unstable; urgency=medium
   * d/lintian: Add glslang-tools lintian override for binary-without-manpage
   * d/control: Fix Vcs-Git and Vcs-Browser urls
 
+  [ Brett Johnson ]
+  * Add man pages for spirv-remap and glslangValidator
+
  -- Timo Aaltonen   Wed, 22 Aug 2018 23:25:24 +0300
 
 glslang (7.8.2853-1) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 19c0680a..346376cf 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: libdevel
 Priority: optional
 Maintainer: Debian X Strike Force 
 Uploaders: Timo Aaltonen 
-Build-Depends: debhelper (>= 11),
+Build-Depends: debhelper (>= 9),
  cmake,
  spirv-headers,
 Standards-Version: 4.2.0
diff --git a/debian/glslang-tools.manpages b/debian/glslang-tools.manpages
new file mode 100644
index ..2d2df99f
--- /dev/null
+++ b/debian/glslang-tools.manpages
@@ -0,0 +1,2 @@
+debian/man/glslangValidator.1
+debian/man/spirv-remap.1
diff --git a/debian/man/glslangValidator.1 b/debian/man/glslangValidator.1
new file mode 100644
index ..aadaa55e
--- /dev/null
+++ b/debian/man/glslangValidator.1
@@ -0,0 +1,261 @@
+.\" Initially generated by help2man 1.47.4.
+.TH GLSLANGVALIDATOR "1" "December 2017" "glslangValidator"
+.SH NAME
+glslangValidator \- OpenGL (ES) Shading Language Reference Compiler
+.SH SYNOPSIS
+.B glslangValidator
+[\fI\,OPTION\/\fR]... [\fI\,FILE\/\fR]...
+.SH DESCRIPTION
+Glslang is the official reference compiler front end for the OpenGL ES and OpenGL shading languages. It implements a strict interpretation of the specifications for these languages. It is open and free for anyone to use, either from a command line or programmatically. The OpenGL and OpenGL ES working groups are committed to maintaining consistency between the reference compiler and the corresponding shading language specifications.
+
+The purpose of the reference compiler is to identify shader portability issues. If glslang accepts a shader without errors, then all OpenGL and OpenGL ES implementations claiming to support the shader's language version should also accept the shader without errors. Likewise, if glslang reports an error when compiling a shader, all OpenGL and OpenGL ES implementations for that language version should report errors, unless the glslang errors are caused by differences in implementation-defined limits or extension support.
+
+Glslang can also be used to generate SPIR-V from GLSL. But this feature is experimental and non-optimized.
+.SH FILE
+The file extension of \&\fI\,FILE\/\fR results in auto-stage classification:
+.TP
+\&.conf
+to provide a config file that replaces the default configuration (see \fB\-c\fR option below for generating a template)
+.TP
+\&.vert
+for a vertex shader
+.TP
+\&.tesc
+for a tessellation control shader
+.TP
+\&.tese
+for a tessellation evaluation shader
+.TP
+\&.geom
+for a geometry shader
+.TP
+\&.frag
+for a fragment shader
+.TP
+\&.comp
+for a compute shader
+.SH OPTIONS
+.TP
+\fB\-C\fR
+cascading errors; risk crash from accumulation of error recoveries
+.TP
+\fB\-D\fR
+input is HLSL
+.HP
+\fB\-D\fR
+.TP
+\fB\-D\fR
+define a pre\-processor macro
+.TP
+\fB\-E\fR
+print pre\-processed GLSL; cannot be used with \fB\-l\fR; errors will appear on stderr.
+.TP
+\fB\-G[ver]\fR
+create SPIR\-V binary, under OpenGL semantics; turns on \fB\-l\fR; default file name is .spv (\fB\-o\fR overrides this) 'ver', when present, is the version of the input semantics, which will appear in #define GL_SPIRV ver. \fB\-\-client opengl100\fR is the same as \fB\-G100\fR and \fB\-\-target\-env\fR for OpenGL will also imply \fB\-G\fR
+.TP
+\fB\-H\fR
+print human readable form of SPIR\-V; turns on \fB\-V\fR
+.TP
+\fB\-I\fR
+add dir to the include search path; includer's directory is searched first, followed by left\-to\-right order of \fB\-I\fR
+.TP
+\fB\-Od\fR
+disables optimization. May cause illegal SPIR\-V for HLSL.
+.TP
+\fB\-Os\fR
+optimizes SPIR\-V to minimize size.
+.TP
+\fB\-S\fR 
+uses specified stage rather than parsing the file extension choices for  are vert, tesc, tese, geom, frag, or comp
+.TP
+\fB\-U\fR
+undefine a pre\-processor macro
+.TP
+\fB\-V[ver]\fR
+create SPIR\-V binary, under Vulkan semantics; turns on \fB\-l\fR; default file name is .spv (\fB\-o\fR overrides this) 'ver', when present, is the version of the input semantics, which will appear in #define VULKAN ver. \fB\-\-client vulkan100\fR is the same as \fB\-V100\fR and \fB\-\-target\-env\fR for Vulkan will also imply \fB\-V\fR
+.TP
+\fB\-c\fR
+configuration dump; creates the default configuration file (redirect to a .conf file)
+.TP
+\fB\-d\fR

Bug#907224: prometheus-alertmanager: Dummy website should use relative links

[Martin Weinelt]

Package: prometheus-alertmanager
Version: 0.15.1+ds-1~bpo9+1
Severity: minor

Dear Maintainer,

the dummy website provided by the prometheus-alertmanager package has
absolute links set, but the alertmanager website could be reverse-proxied 
in which case the links need to be relative. The links therefore link to 
the wrong URL.


Best regards,

Martin Weinelt

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

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

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


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

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

Versions of packages prometheus-alertmanager depends on:
ii  daemon0.6.4-1+b2
ii  libc6 2.24-11+deb9u3
ii  systemd-sysv  232-25+deb9u4

prometheus-alertmanager recommends no packages.

prometheus-alertmanager suggests no packages.

-- Configuration Files:
/etc/default/prometheus-alertmanager changed [not included]
/etc/prometheus/alertmanager.yml changed [not included]

-- no debconf information

Bug#906981: stunnel4 FTBFS with OpenSSL 1.1.1

[Peter Pentchev]

Control: tags -1 + confirmed upstream

On Thu, Aug 23, 2018 at 05:30:12PM +0300, Adrian Bunk wrote:
> Control: severity -1 serious
> Control: tags -1 ftbfs
> Control: retitle -1 stunnel4 FTBFS with OpenSSL 1.1.1
> 
> On Wed, Aug 22, 2018 at 09:44:35PM +0200, Paul Gevers wrote:
> >...
> > With a recent upload of openssl the autpkgtest of stunnel4 started to
> > fail in testing. I copied some of the output below.
> >...
> 
> This is also a FTBFS:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/stunnel4.html

Hi,

Thanks to everyone for reporting and investigating this.  I've forwarded
it upstream:

  https://www.stunnel.org/pipermail/stunnel-users/2018-August/006118.html

...and I've also made an stunnel4 upload that does not run the upstream
test suite, but only the limited functional testing script that I wrote
earlier for the Debian package.  I'm aware that not closing this bug,
now that it's serious, will not allow this new upload to migrate to
testing, but this is on purpose - what this upload does is merely
a workaround, not a fix; I'll wait for upstream's reply on this.

Thanks again for everyone's efforts, and keep up the great work!

G'luck,
Peter

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


signature.asc
Description: PGP signature

Bug#898935: Tomcat 8 security issues in Stretch

[Markus Koschany]

A security update has been sent to Debian's security team and we expect
that the current open issues in Stretch will be fixed in due time.
Please note that Tomcat 7 in Stretch is not vulnerable to any of those
issues because we only build the servlet API.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#898935: migrate fix to stretch security

[Markus Koschany]

Version: 8.5.32-1

This issue was fixed in 8.5.32-1. I am going to close this bug report now.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#907201: [pkg-cryptsetup-devel] Bug#907201: cryptsetup-initramfs: Asks for disk password twice unless 'debug' is passed to kernel command line

[Matthias Klumpp]

Am Fr., 24. Aug. 2018 um 23:39 Uhr schrieb Guilhem Moulin :
>
> Control: tag -1 moreinfo
>
> On Fri, 24 Aug 2018 at 22:45:40 +0200, Matthias Klumpp wrote:
> > Obviously no Plymouth was shown here. The log looks normal to me.
>
> Ah right, plymouthd isn't started yet when you're dropped into the
> initramfs shell, so you'll need to start it manually:
> `/scripts/init-premount/plymouth`.
>
> Are you able to reproduce this in a Debian system?  I just fired a fresh
> & minimal sid VM with cryptsetup-initramfs 2:2.0.4-2 and plymouth
> 0.9.3-3 and
>
> root@kvm-23941:~# cat /etc/crypttab
> root_crypt UUID=69498061-2e79-48a3-b637-655690cb4d16 none luks
> root@kvm-23941:~# cat /etc/fstab
> /dev/vda1 /boot ext2 defaults 0 2
> UUID=67d6c067-545f-40e5-8f7d-e852e2490f0a none swap sw 0 0
> UUID=9945b9d7-bade-4df5-bd7c-8822a1a37274 / ext4 defaults 0 1
> /dev/sr0 /media/cdrom iso9660 ro,noauto 0 0
> root@kvm-23941:~# cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-4.17.0-3-amd64 
> root=UUID=9945b9d7-bade-4df5-bd7c-8822a1a37274 ro quiet splash
>
> In that VM I only get the plymouth prompt (if I remove ‘splash’ I get a
> single console prompt).
>
> Are you sure the first (dummy) prompt comes from 
> `/scripts/local-top/cryptroot`,
> and not from another initramfs script?  What is being prompted exactly?

I attached screenshots from the two prompts. Your comment got me
thinking though, so I pressed ESC on the first prompt and ended up in
the GRUB menu.
So it looks like the first prompt is from GRUB trying to mount the rootfs...
Now I need to figure out why it does that - that passing "debug" to
the kernel command-line prevents the message from being shown is
weird, but probably also GRUB related.

> Also, your busybox doesn't seem to include fold(1), unlike the one from
> buster.  But that's most likely unrelated.

The busybox setup is more comparable to Ubuntu in PureOS - I need to
look whether we can maybe get rid of that divergence.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#907188: [Pkg-utopia-maintainers] Bug#907188: New version available

[Michael Biebl]

On 8/24/18 16:31, Sebastien Bacher wrote:
> Package: volume-key
> Version: 0.3.10-1
> 
> hey,
> 
> There is a new 0.3.11 version available switch to python3, it would be
> nice to have the update in Debian (and maybe the python binary
> re-enabled now that the code is using python3)

There are some unresolved issues which need to be fixed first.

See my email to the upstream developer:

> Hi Jiri,
> 
> when trying to build volume_key 0.3.11 for debian, the package fails to
> build as we use -Wl,-z,defs to detect underlinking and unresolved symbols:
> 
> libtool: link: gcc -shared  -fPIC -DPIC
> python/.libs/_volume_key_la-volume_key_wrap.o   -Wl,-rpath
> -Wl,/home/michael/debian/build-area/volume-key-0.3.11/lib/.libs
> -L/usr/lib/python3.6/config-3.6m-x86_64-linux-gnu -L/usr/lib
> lib/.libs/libvolume_key.so -lpython3.6m -lpthread -ldl -lutil -lm
> -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4  -g
> -O2 -fstack-protector-strong -Wl,-export-dynamic -Wl,-O1
> -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,defs
> -Wl,--as-needed   -Wl,-soname -Wl,_volume_key.so -o
> python/.libs/_volume_key.so
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Packet_get_format':
> ./python/volume_key_wrap.c:5232: undefined reference to
> `PyString_AsStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Packet_open_unencrypted':
> ./python/volume_key_wrap.c:5326: undefined reference to
> `PyString_AsStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_add_secret':
> ./python/volume_key_wrap.c:4387: undefined reference to
> `PyString_AsStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_create_packet_cleartext':
> ./python/volume_key_wrap.c:4664: undefined reference to
> `PyString_FromStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_create_packet_assymetric':
> ./python/volume_key_wrap.c:4743: undefined reference to
> `PyString_FromStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_create_packet_asymmetric':
> ./python/volume_key_wrap.c:4828: undefined reference to
> `PyString_FromStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_create_packet_assymetric_from_cert_data':
> ./python/volume_key_wrap.c:4894: undefined reference to
> `PyString_AsStringAndSize'
> /usr/bin/ld: ./python/volume_key_wrap.c:4931: undefined reference to
> `PyString_FromStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_create_packet_asymmetric_from_cert_data':
> ./python/volume_key_wrap.c:4997: undefined reference to
> `PyString_AsStringAndSize'
> /usr/bin/ld: ./python/volume_key_wrap.c:5034: undefined reference to
> `PyString_FromStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Volume_create_packet_with_passphrase':
> ./python/volume_key_wrap.c:5111: undefined reference to
> `PyString_FromStringAndSize'
> /usr/bin/ld: python/.libs/_volume_key_la-volume_key_wrap.o: in function
> `_wrap_Packet_open':
> ./python/volume_key_wrap.c:5273: undefined reference to
> `PyString_AsStringAndSize'
> collect2: error: ld returned 1 exit status
> make[3]: *** [Makefile:959: python/_volume_key.la] Error 1
> make[3]: Leaving directory
> '/home/michael/debian/build-area/volume-key-0.3.11'
> make[2]: *** [Makefile:1235: all-recursive] Error 1
> make[2]: Leaving directory
> '/home/michael/debian/build-area/volume-key-0.3.11'
> make[1]: *** [Makefile:746: all] Error 2
> make[1]: Leaving directory
> '/home/michael/debian/build-area/volume-key-0.3.11'
> 
> As I'm no python developer, I searched a bit and found
> https://github.com/google/sentencepiece/issues/25
> which hints at a Python3 related problem, which correlates with the
> switch to Python3 in 0.3.11
> 
> Maybe volume-key needs a similar fix.
> 
> To reproduce the problem, run LDFLAGS=-Wl,-z,defs ./configure && make
> 
> I would have filed an upstream bug report, bug
> https://pagure.io/volume_key/ requires yet another user account.
> Hope you don't mind if I contact you directly.


...

> Am 13.08.2018 um 21:10 schrieb Michael Biebl:
> 
>> ./python/volume_key_wrap.c:5232: undefined reference to
>> `PyString_AsStringAndSize'
> 
> ...
> 
>> As I'm no python developer, I searched a bit and found
>> https://github.com/google/sentencepiece/issues/25
>> which hints at a Python3 related problem, which correlates with the
>> switch to Python3 in 0.3.11
> 
> It looks like this API was removed in python 3.3. At least that's how I
> understand https://bugs.python.org/issue2799




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#907201: [pkg-cryptsetup-devel] Bug#907201: cryptsetup-initramfs: Asks for disk password twice unless 'debug' is passed to kernel command line

[Guilhem Moulin]

Control: tag -1 moreinfo

On Fri, 24 Aug 2018 at 22:45:40 +0200, Matthias Klumpp wrote:
> Obviously no Plymouth was shown here. The log looks normal to me.

Ah right, plymouthd isn't started yet when you're dropped into the
initramfs shell, so you'll need to start it manually:
`/scripts/init-premount/plymouth`.

Are you able to reproduce this in a Debian system?  I just fired a fresh
& minimal sid VM with cryptsetup-initramfs 2:2.0.4-2 and plymouth
0.9.3-3 and

root@kvm-23941:~# cat /etc/crypttab 
root_crypt UUID=69498061-2e79-48a3-b637-655690cb4d16 none luks
root@kvm-23941:~# cat /etc/fstab 
/dev/vda1 /boot ext2 defaults 0 2
UUID=67d6c067-545f-40e5-8f7d-e852e2490f0a none swap sw 0 0
UUID=9945b9d7-bade-4df5-bd7c-8822a1a37274 / ext4 defaults 0 1
/dev/sr0 /media/cdrom iso9660 ro,noauto 0 0
root@kvm-23941:~# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-4.17.0-3-amd64 
root=UUID=9945b9d7-bade-4df5-bd7c-8822a1a37274 ro quiet splash

In that VM I only get the plymouth prompt (if I remove ‘splash’ I get a
single console prompt).

Are you sure the first (dummy) prompt comes from `/scripts/local-top/cryptroot`,
and not from another initramfs script?  What is being prompted exactly?

Also, your busybox doesn't seem to include fold(1), unlike the one from
buster.  But that's most likely unrelated.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#907208: dgit quilt-fixup sometimes runs dpkg-source [and 1 more messages]

[Ian Jackson]

Ian Jackson writes ("dgit quilt-fixup sometimes runs dpkg-source"):
> 2. My xen tree does this too,  git-show-ref output below.
>I'm on dgit/experimental.draft.

This part of this bug report is actually #907206.  That leaves 1.,
which is a design problem.

Ian.

Bug#858159: [installation-guide] Memory requirements for installing Stretch have increased since Jessie

[John Paul Adrian Glaubitz]

On 8/24/18 11:28 PM, Holger Wansing wrote:
> Noone commented on this, so I assume we have a consense here, to leave 
> everything
> as is.
> So closing this bug.

Well, I don't mind that much. All I wanted to say is that a headless
barebone installation works fine with as little as 128 MiB of RAM.

However, the mileage may vary depending on the applications being
used, of course.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#902617: (No Subject)

[Leerink]

Thank you for the feedback. Tested today and the problem seems to be solved 
without the "allow_rgb10_configs=false" setting. Current versions:

   mesa 18.1.6-1
   clutter 1.26.2+dfsg-4
   linux 4.17.0-3

Bug#857891: Bug

[Christian Göttsche]

> Nothing from logrotate in syslog. I have just run logrotate -f /etc/
> logrotate.conf. It did (!) rotate all the logs in /var/log,

Thats good. Did it output anything?

> but neither in syslog nor in syslog.1 do I see anything from logrotate.

At least you should see some message from cron or systemd triggering
logrotate around 9am.

Bug#857573: Processed: Re: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

[Ivo De Decker]

Control: severity -1 important

Hi,

On Thu, May 18, 2017 at 10:32:02AM +0200, Christoph Biedl wrote:
> Michael Biebl wrote...
> 
> > To mark as mountpoint as network mount, there is the _netdev mount
> > option.
> 
> While I can confirm this provides a sane and safe shutdown for a mounted
> AoE-device, this works only if the device was initially mounted using
> that extra option. A later "mount -o remount,_netdev" exits zero but
> does not change /proc/mounts, hence resulting in havoc. If you could
> shed some light on this?

Is there still a bug against ifupdown that needs to stay open? For the issues
in the individual packages (aoe-tools, nbd and the kernel), the cloned bugs
exist.

In any case, I downgraded it, as it seems that things work fine with the
_netdev mount option.

Cheers,

Ivo

Bug#907223: meritous: homepage of meritous should be https://gitlab.com/meritous/meritous/

[shirish शिरीष]

Package: meritous
Version: 1.4-1+b1
Severity: normal

Dear Maintainer,

As gitorious is no longer available, all the content from there has
been mirrored into https://gitlab.com/meritous/meritous/ please use
that as homepage URL.


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

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

Versions of packages meritous depends on:
ii  libc62.27-5
ii  libsdl-image1.2  1.2.12-8
ii  libsdl-mixer1.2  1.2.12-14
ii  libsdl1.2debian  1.2.15+dfsg2-1
ii  meritous-data1.4-1
ii  zlib1g   1:1.2.11.dfsg-1

meritous recommends no packages.

meritous suggests no packages.

-- no debconf information


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

Bug#907222: Preferences: Tracks>Spectrograms panel (only) does not respect GTK theme

[Reuben Thomas]

Package: audacity
Version: 2.2.1-1
Severity: normal

The Debian package seems to be patched to make Audacity work properly with
dark themes (thanks very much!).

Oddly, the Tracks>Spectrograms panel of Preferences still does not work in
this regard: the background comes up white with white text on my
Adwaita-dark–themed GNOME desktop. To be clear, all the other Preferences
panels come up as desired, with dark coloring.

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

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

Versions of packages audacity depends on:
ii  audacity-data   2.2.1-1
ii  libasound2  1.1.3-5ubuntu0.1
ii  libavcodec577:3.4.4-0ubuntu0.18.04.1
ii  libavformat57   7:3.4.4-0ubuntu0.18.04.1
ii  libavutil55 7:3.4.4-0ubuntu0.18.04.1
ii  libc6   2.27-3ubuntu1
ii  libexpat1   2.2.5-3
ii  libflac++6v51.3.2-1
ii  libflac81.3.2-1
ii  libgcc1 1:8-20180414-1ubuntu2
ii  libgdk-pixbuf2.0-0  2.36.11-2
ii  libglib2.0-02.56.1-2ubuntu1
ii  libgtk2.0-0 2.24.32-1ubuntu1
ii  libid3tag0  0.15.1b-13
ii  liblilv-0-0 0.24.2~dfsg0-1
ii  libmad0 0.15.1b-8ubuntu1
ii  libmp3lame0 3.100-2
ii  libogg0 1.3.2-1
ii  libportaudio2   19.6.0-1
ii  libportsmf0v5   0.1~svn20101010-5ubuntu1
ii  libsndfile1 1.0.28-4
ii  libsoundtouch1  1.9.2-3
ii  libsoxr00.1.2-3
ii  libstdc++6  8-20180414-1ubuntu2
ii  libsuil-0-0 0.10.0~dfsg0-1
ii  libtwolame0 0.3.13-3
ii  libvamp-hostsdk3v5  2.7.1~repack0-1
ii  libvorbis0a 1.3.5-4.2
ii  libvorbisenc2   1.3.5-4.2
ii  libvorbisfile3  1.3.5-4.2
ii  libwxbase3.0-0v53.0.4+dfsg-3
ii  libwxgtk3.0-0v5 3.0.4+dfsg-3

audacity recommends no packages.

Versions of packages audacity suggests:
ii  cmt [ladspa-plugin]  1.16-2
ii  ladspa-sdk [ladspa-plugin]   1.13-3ubuntu2
ii  mcp-plugins [ladspa-plugin]  0.4.0-6
ii  swh-plugins [ladspa-plugin]  0.4.17-2

-- no debconf information

Bug#907221: Missing test dep on matplotlib

[Steve Langasek]

Source: python-bayespy
Version: 0.5.17-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic

Dear Ghislain,

python-bayespy 0.5.17-1 consistently fails its autopkgtests in both Debian
and Ubuntu, due to matplotlib being missing from the test environment:

[...]
Test random sampling from the Dirichlet distribution. ... ok
Failure: ModuleNotFoundError (No module named 'matplotlib') ... ERROR

==
ERROR: Failure: ModuleNotFoundError (No module named 'matplotlib')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.7/imp.py", line 244, in load_module
return load_package(name, filename)
  File "/usr/lib/python3.7/imp.py", line 216, in load_package
return _load(spec)
  File "", line 696, in _load
  File "", line 677, in _load_unlocked
  File "", line 728, in exec_module
  File "", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/bayespy/tests/__init__.py", line 8, in 

import bayespy.plot as bpplt
  File "/usr/lib/python3/dist-packages/bayespy/plot.py", line 60, in 
import matplotlib.pyplot as plt
ModuleNotFoundError: No module named 'matplotlib'

--
Ran 124 tests in 11.037s

FAILED (errors=1)
autopkgtest [03:39:56]: test command1: ---]
[...]

  (https://ci.debian.net/packages/p/python-bayespy/unstable/amd64/)

It should be possible to work around this by adding python3-matplotlib as a
manual test dependency, but I notice that there are non-test-related
references to matplotlib within /usr/lib/python3/dist-packages/bayespy; so I
wonder if python3-matplotlib should also be a dependency of python3-bayespy
instead?  (Or at least a Recommends)

Regressed autopkgtests are blockers for inclusion of packages in Ubuntu
releases, and a previous version of python-bayespy had a successful
autopkgtest, so this is currently holding the package out of Ubuntu 18.10. 
However, since the python-bayespy was also removed from the previous Ubuntu
release due to other bugs, I think it's reasonable for us to reset the
baseline and let the package in as-is.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#907201: [pkg-cryptsetup-devel] Bug#907201: cryptsetup-initramfs: Asks for disk password twice unless 'debug' is passed to kernel command line

[Matthias Klumpp]

Am Fr., 24. Aug. 2018 um 19:09 Uhr schrieb Guilhem Moulin :
>
> Hi,
>
> On Fri, 24 Aug 2018 at 18:49:10 +0200, Matthias Klumpp wrote:
> > This issue is really annoying, and I would be glad for any pointers on
> > how to investigate the issue further, as I am no expert on cryptsetup.
>
> See https://wiki.debian.org/CryptsetupDebug to trace
> /scripts/local-top/cryptroot, please attach the log file to this bug
> afterwards :-)

Thank you! The log file is attached to this message.
What I did was:

1) Run the script
2) Get a password prompt
3) Intentionally enter a wrong password
4) Enter the correct password at the second prompt

Obviously no Plymouth was shown here. The log looks normal to me.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/
+ PREREQ=cryptroot-prepare
+ . /scripts/functions
+ [ -f /lib/cryptsetup/functions ]
+ . /lib/cryptsetup/functions
+ [ /scripts/local-top/cryptroot != /scripts/local-top/cryptroot ]
+ [ /scripts/local-top/cryptroot != /scripts/local-top/cryptroot ]
+ [ local-top/cryptroot != /scripts/local-top/cryptroot ]
+ TABFILE=/cryptroot/crypttab
+ export DM_DEFAULT_NAME_MANGLING_MODE=hex
+ mkdir -p /cryptroot
+ grep -qE ^(.*\s)?cryptopts= /proc/cmdline
+ touch -- /cryptroot/crypttab
+ [ -s /cryptroot/crypttab ]
+ mkdir -pm0700 /run/cryptsetup
+ modprobe -q dm_crypt
+ crypttab_foreach_entry setup_mapping
+ local callback=setup_mapping IFS
+ local _CRYPTTAB_NAME _CRYPTTAB_SOURCE _CRYPTTAB_KEY _CRYPTTAB_OPTIONS CRYPTTAB_NAME CRYPTTAB_SOURCE CRYPTTAB_KEY CRYPTTAB_OPTIONS
+ [ -f /cryptroot/crypttab ]
+ IFS= 	 read -r _CRYPTTAB_NAME _CRYPTTAB_SOURCE _CRYPTTAB_KEY _CRYPTTAB_OPTIONS
+ [ luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 != luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 ]
+ [ -z luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 ]
+ printf %b luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ CRYPTTAB_NAME=luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ printf %b UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ CRYPTTAB_SOURCE=UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ printf %b none
+ CRYPTTAB_KEY=none
+ printf %b luks
+ CRYPTTAB_OPTIONS=luks
+ [ -z UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 ]
+ [ -z none ]
+ [ -z luks ]
+ setup_mapping
+ local dev
+ dm_blkdevname luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ local name=luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 dev
+ dmsetup info -c --noheadings -o blkdevname -- luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ dev=
+ return 1
+ crypttab_parse_options --export
+ local quiet=n export=n
+ [ 1 -gt 0 ]
+ export=y
+ shift
+ [ 0 -gt 0 ]
+ local IFS=, x OPTION VALUE
+ unset -v CRYPTTAB_OPTION_cipher CRYPTTAB_OPTION_size CRYPTTAB_OPTION_hash CRYPTTAB_OPTION_offset CRYPTTAB_OPTION_skip CRYPTTAB_OPTION_verify CRYPTTAB_OPTION_readonly CRYPTTAB_OPTION_discard CRYPTTAB_OPTION_plain CRYPTTAB_OPTION_luks CRYPTTAB_OPTION_tcrypt CRYPTTAB_OPTION_veracrypt CRYPTTAB_OPTION_swap CRYPTTAB_OPTION_tmp CRYPTTAB_OPTION_check CRYPTTAB_OPTION_checkargs CRYPTTAB_OPTION_tries CRYPTTAB_OPTION_initramfs CRYPTTAB_OPTION_noearly CRYPTTAB_OPTION_noauto CRYPTTAB_OPTION_loud CRYPTTAB_OPTION_quiet CRYPTTAB_OPTION_keyscript CRYPTTAB_OPTION_keyslot CRYPTTAB_OPTION_header CRYPTTAB_OPTION_tcrypthidden
+ OPTION=luks
+ VALUE=luks
+ [ luks = luks ]
+ unset -v VALUE
+ crypttab_validate_option
+ local o=luks
+ [ -z x ]
+ [ y = y ]
+ export CRYPTTAB_OPTION_luks=yes
+ IFS= 
+ [ n = n ]
+ [ -z x ]
+ [ -z x ]
+ wait_for_source
+ wait_for_udev 10
+ command -v udevadm
+ udevadm settle --timeout=10
+ crypttab_resolve_source
+ [ ! -f UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 ]
+ local dev=UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ resolve_device_spec UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ local spec=UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
+ blkid -l -t UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 -o device
+ spec=/dev/sda2
+ [ -b /dev/sda2 ]
+ printf %s\n /dev/sda2
+ dev=/dev/sda2
+ CRYPTTAB_SOURCE=/dev/sda2
+ return 0
+ export CRYPTTAB_NAME
+ [ -z  ]
+ [ none != none ]
+ [ none != none ]
+ local count=0 maxtries=3 fstype vg rv
+ [ 3 -le 0 ]
+ [ 0 -lt 3 ]
+ [ -z  ]
+ [ none != none ]
+ unlock_mapping
+ local keyfile=-
+ [ -n  ]
+ run_keyscript none 0
+ local keyscriptarg=none CRYPTTAB_TRIED=0 keyscript
+ export CRYPTTAB_NAME CRYPTTAB_SOURCE CRYPTTAB_OPTIONS
+ export CRYPTTAB_TRIED
+ [ -n  ]
+ [ none = none ]
+ keyscript=/lib/cryptsetup/askpass
+ keyscriptarg=Please unlock disk luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6: 
+ exec /lib/cryptsetup/askpass Please unlock disk luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6: 
+ get_crypt_type
+ local type=plain
+ [  = yes ]
+ [  = yes ]
+ [ yes = yes ]
+ type=luks
+ echo luks
+ local type=luks
+ [ luks = luks ]
+ unset -v CRYPTTAB_OPTION_cipher CRYPTTAB_OPTION_size CRYPTTAB_OPTION_hash CRYPTTAB_OPTION_offset CRYPTTAB_OPTION_skip
+ [ luks = plain ]
+ [ luks = tcrypt ]
+ [ luks = tcrypt ]
+ unset -v CRYPTTAB_OPTION_veracrypt CRYPTTAB_OPTION_tcrypthidden
+ [ luks != luks ]
+ /sbin/cryptsetup -T1 --type=luks --key-file=- open -- /dev/sda2 

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

[Antonio Terceiro]

Control: severity -1 important

Hi,

I would like to reinforce the request for a stable update:

- according to the openssl maintainer, this is a security issue and
  should be fixed in stable

- without such fix, bip on stable will soon be unusable to any client
  using a recent enough openssl


signature.asc
Description: PGP signature

Bug#905290: verbiste-el: fix emacsen-common-without-dh-elpa

[Nicholas D Steeves]

Dear Tomasz,

On Thu, Aug 02, 2018 at 11:34:31PM +0800, Tomasz Buchert wrote:
> Package: verbiste-el
> Severity: normal
> 
> Dear Maintainer,
> lintian reports emacsen-common-without-dh-elpa on the verbiste-el package.
> Please fix it.

I've taken care of this bug.  Please merge the following PR:
  https://salsa.debian.org/debian/verbiste/merge_requests/1/

Piuparts look good and I believe that a "dch -r" will add the correct
header above my changes.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#864082: fontconfig: please make the cache files reproducible

[Chris Lamb]

Dear Keith,

> > Gentle ping on this? :) Would love to see this Tails-related work
> > in Debian!
> 
> I was stalling for an upstream release with this patch; it looks like
> that shouldn't be more than a month or two from now. Any particular
> reason for urgency here?

Somewhat; it's currently causing buster-based builds for Tails to be
unreproducible.

This means that the in-depth results are being ignored (hey "it's
already unreproducible!") and thus other issues may pile up, causing
scheduling/fixing issues later on.


Best wishes,

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

Bug#907220: Some caps plugins are crashing

[trebmuh]

Package: caps
Version: 0.9.24-5

This has been tested on a Stretch system from the stable package version 
(0.9.24-4) as well as from a home-made backport of the current 
buster/sid package (0.9.24-5).


The following plugins aren't working :
- C* AmpVTS
- C* Compress
- C* CompressX2
- C* Saturate

When one of these plugins is inserted into Ardour, an audio click is 
happening and the track's meters is going up in the red and stays there.


The attached patch fixes the issue on a debian stretch rebuild.
It hasn't been tried by me so far (hence this report and not a commit to 
the debian salsa repository).


Notes:
1) this patch has been sent to the upstream maintainer
2) I'm copying the patch writer to this bug report, please keep him 
CC'ed for any later message on this thread


Hope that helps.
OlivierDescription: fix crash (bug LZK #487)
Origin: https://github.com/moddevices/caps-lv2/pull/14
Forwarded: don't know
Author: Olivier Humbert 
Reviewed-by: Jean-Pierre Cimalando
Last-Update: 2018-08-23

--- a/dsp/windows.h
+++ b/dsp/windows.h
@@ -157,12 +157,9 @@
 
 	for (double i = -n / 2 + .1; si < n; ++si, i += step)
 	{
-		double k = besseli ((beta * sqrt (1 - pow ((2 * i / (n - 1)), 2 / bb;
-
-		/* can you spell hack */
-		if (!finite (k) || isnan(k))
-			k = 0;
-
+		double a = 1 - pow ((2 * i / (n - 1)), 2);
+		a = (a < 0.0) ? 0.0 : a;
+		double k = besseli ((beta * sqrt (a))) / bb;
 		F (s[si], k);
 	}
 }

Bug#907219: m2crypto: autopkgtest needs update for new version of openssl

[Paul Gevers]

Source: m2crypto
Version: 0.27.0-6
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:openssl
Control: block 907015 by -1

Dear maintainers,

With a recent upload of openssl the autopkgtest of m2crypto started to
fail in testing. I copied some of the output below.

Of course, openssl shouldn't just break your autopkgtest (or even worse,
your package), but the change in openssl was intended and your package
needs to update to the new situation. If needed, please change the bug's
severity.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from openssl should really add
a versioned Breaks on the unfixed version of (one of your) package(s),
hence I added a blocking relation on the openssl bug that tracks that.
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

A quote from the openssl maintainer about the openssl update:
"
This is probably the result of the default openssl.cfg now having:
[system_default_sect]
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=2

Where the SECLEVEL 2 requires a 112 / 2048 bit security level.
"

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=openssl

https://ci.debian.net/data/autopkgtest/testing/amd64/m/m2crypto/874888/log.gz

/usr/lib/python2.7/dist-packages/M2Crypto/httpslib.py:88: error
_ TwistedSSLClientTestCase.test_makefile_timeout_fires
_

self = 

def test_makefile_timeout_fires(self):
# This is convoluted because (openssl s_server -www) starts
# writing the response as soon as it receives the first line of
# the request, so it's possible for it to send the response
# before the request is sent and there would be no timeout.  So,
# let the server spend time reading from an empty pipe
FIFO_NAME = 'test_makefile_timeout_fires_fifo'  # noqa
os.mkfifo('tests/' + FIFO_NAME)
pipe_pid = os.fork()
try:
if pipe_pid == 0:
try:
with open('tests/' + FIFO_NAME, 'w') as f:
time.sleep(sleepTime + 1)
f.write('Content\n')
finally:
os._exit(0)
self.args[self.args.index('-www')] = '-WWW'
pid = self.start_server(self.args)
try:
c = httpslib.HTTPSConnection(srv_host, self.srv_port)
c.putrequest('GET', '/' + FIFO_NAME)
c.putheader('Accept', 'text/html')
c.putheader('Accept', 'text/plain')
>   c.endheaders()

tests/test_ssl.py:988:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python2.7/httplib.py:1038: in endheaders
self._send_output(message_body)
/usr/lib/python2.7/httplib.py:882: in _send_output
self.send(msg)
/usr/lib/python2.7/httplib.py:844: in send
self.connect()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

self = 

def connect(self):
# type: () -> None
error = None
# We ignore the returned sockaddr because SSL.Connection.connect
needs
# a host name.
for (family, _, _, _, _) in \
socket.getaddrinfo(self.host, self.port, 0,
   socket.SOCK_STREAM):
sock = None
try:
sock = SSL.Connection(self.ssl_ctx, family=family)

# set SNI server name since we know it at this point
sock.set_tlsext_host_name(self.host)

if self.session is not None:
sock.set_session(self.session)
sock.connect((self.host, self.port))

self.sock = sock
sock = None
return
except socket.error as e:
# Other exception are probably SSL-related, in that case we
# abort and the exception is forwarded to the caller.
error = e
finally:
if sock is not None:
sock.close()

if error is None:
raise AssertionError("Empty list returned by getaddrinfo")
>   raise error
E   error: [Errno 111] Connection refused

/usr/lib/python2.7/dist-packages/M2Crypto/httpslib.py:88: error
 TwistedSSLClientTestCase.test_timeout
_

self = 

def test_timeout(self):
pid = self.start_server(self.args)
try:
ctx = SSL.Context()
s = SSL.Connection(ctx)
# Just a really small number so we can timeout

Bug#907145: closed by Jeremy Bicha (Re: Bug#907145: gksu: Fails to change PATH according to /ect/sudoers)

[Chris Tillman]

Aha! Thank you. Since it was used in the menu shortcut of "Root Terminal"
for anyone who used the XFCE desktop, perhaps it should be moved to "xfce4"
? They should probably replace the implementation of the menu since they
formerly depended on gksu. I verified after upgrading all packages to
current testing that my menu for "Root Terminal" still references gksu.

On Fri, Aug 24, 2018 at 10:48 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the gksu package:
>
> #907145: gksu: Fails to change PATH according to /ect/sudoers
>
> It has been closed by Jeremy Bicha .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Jeremy Bicha <
> jbi...@debian.org> by
> replying to this email.
>
>
> --
> 907145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907145
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Jeremy Bicha 
> To: toff.till...@gmail.com, 907145-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Fri, 24 Aug 2018 06:44:24 -0400
> Subject: Re: Bug#907145: gksu: Fails to change PATH according to
> /ect/sudoers
> On Fri, Aug 24, 2018 at 6:24 AM Chris Tillman 
> wrote:
> > This showed gksu is not changing the path when calling xfce4-terminal.
>
> gksu was removed from Debian Testing in January and from Unstable 2
> months after that. Therefore, gksu is no longer supported in Testing
> at all.
>
> For your other issues, maybe this explanation will help some:
>
> https://unix.stackexchange.com/questions/460478/debian-su-and-su-path-differences/460769#460769
>
> I am closing this bug because there is nothing we can do in gksu and
> it's not obvious to me whether there is another package to reassign
> this issue to.
>
> Thanks,
> Jeremy Bicha
>
>
> -- Forwarded message --
> From: Chris Tillman 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Fri, 24 Aug 2018 22:21:37 +1200
> Subject: gksu: Fails to change PATH according to /ect/sudoers
> Package: gksu
> Version: 2.0.2-9+b1
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
> I was upgrading the testing distribution after several months using
> aptitude. I
> upgraded about half the packages, but when I went to upgrade the other
> half I
> received errors from dpkg:
>
> Preconfiguring packages ...
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and
> /sbin
> E: Sub-process /usr/bin/dpkg returned an error code (2)
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> I searched online and found the cause of the errors was, as the error
> states,
> the PATH being incorrect. I checked the PATH resulting when I chose "Root
> Terminal" from the menu, and this path did not include the sbin
> directories.
>
> root@ctillman:/home/chris# echo $PATH
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>
> I tried sudo from a regular user terminal window to check the path which
> would
> come up with it:
>
> chris@ctillman:~$ sudo bash -c 'echo $PATH'
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> And then, because gksu starts Root Terminal, I tried the equivalent with
> gksu:
>
> chris@ctillman:~$ gksu "bash -c 'echo $PATH'"
> gksu-run: gksu/bash -c 'echo
>
> |usr|local|bin:|usr|bin:|bin:|usr|local|games:|usr|games'/5044-0-ctillman_TIME11346051
> gksu-run: 1f53968cb8fe3d752131e6a334975c84
>
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>
> This showed gksu is not changing the path when calling xfce4-terminal.
>
> My /etc/sudoers contents:
>
> root@ctillman:~# cat /etc/sudoers
> #
> # This file MUST be edited with the 'visudo' command as root.
> #
> # Please consider adding local content in /etc/sudoers.d/ instead of
> # directly modifying this file.
> #
> # See the man page for details on how to write a sudoers file.
> #
> Defaultsenv_reset
> Defaultsmail_badpass
> Defaults
> secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
>
> # Host alias specification
>
> # User alias specification
>
> # Cmnd alias specification
>
> # User privilege specification
> rootALL=(ALL:ALL) ALL
> chris   ALL=(ALL:ALL) ALL
>
> # Allow members of group sudo to execute any command
> %sudo   ALL=(ALL:ALL) ALL
>
> # See sudoers(5) for more information on "#include" directives:
>
> #includedir /etc/sudoers.d
>
>
>
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: 

Bug#907218: yapf: autopkgtest regression

[Paul Gevers]

Source: yapf
Version: 0.22.0-3
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With the upload of 0.22.0-3 the autopkgtest of your package started to
fail in testing. I copied the output below.

Currently this regression is contributing to the delay of the migration
to testing [1]. Could you please investigate the situation and fix it?
It seems that the first test is just missing a test dependency on
python-nose.

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=yapf

https://ci.debian.net/data/autopkgtest/testing/amd64/y/yapf/874882/log.gz

autopkgtest [04:39:09]: test command1: set -e ; cp -r yapftests
"$AUTOPKGTEST_TMP" ; for py in $(pyversions -r 2>/dev/null) ; do cd
"$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -m nose --exclude
"yapftests.pytree_unwrapper_test.MatchBracketsTest" ; done
autopkgtest [04:39:09]: test command1: [---
Testing with python2.7:
/usr/bin/python2.7: No module named nose
autopkgtest [04:39:10]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#907217: linux-image-4.17.0-3-amd64: crash on suspend/resume with network over bluetooth

[Philipp Marek]

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

Over the last few kernel images (I believe since 4.14 or so, didn't test 
with older kernels) doing suspend/resume with an active bluetooth network 
connection can cause the kernel to do this:

   ACPI: Low-level resume complete
   sysfs group 'byte_queue_limits' not found for kobject 'tx-0'
   ...
   BUG: unable to handle kernel paging request at ba385620
 Call Trace:
  _raw_spin_lock+0x1d/0x20
  klist_next+0x1d/0xd0
  ? __rpm_get_callback+0x80/0x80
  device_for_each_child+0x3e/0x90
  pm_runtime_set_memalloc_noio+0x89/0xa0

which means that the network is dead - no new TCP connections (not even 
local), no WIFI, no loading/unloading modules, etc.
Basically, you can (try to) close your open files, and reboot.

It doesn't happen every time; perhaps some packets need to be actively
transferred at that time?


-- Package-specific info:
** Version:
Linux version 4.17.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-28)) #1 SMP Debian 4.17.17-1 (2018-08-18)

** Command line:
BOOT_IMAGE=/vmlinuz-4.17.0-3-amd64 root=/dev/mapper/n555--vg-root ro 
initrd=/install/initrd.gz quiet

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

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

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

Versions of packages linux-image-4.17.0-3-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.132
ii  kmod25-1
ii  linux-base  4.5

Versions of packages linux-image-4.17.0-3-amd64 recommends:
ii  apparmor 2.13-8
ii  firmware-linux-free  3.4
ii  irqbalance   1.3.0-0.1+b1

Versions of packages linux-image-4.17.0-3-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02+dfsg1-5
pn  linux-doc-4.17  

Versions of packages linux-image-4.17.0-3-amd64 is related to:
ii  firmware-amd-graphics 20180518-1
ii  firmware-atheros  20180518-1
ii  firmware-bnx2 20180518-1
ii  firmware-bnx2x20180518-1
ii  firmware-brcm8021120180518-1
pn  firmware-cavium   
pn  firmware-intel-sound  
ii  firmware-intelwimax   20180518-1
ii  firmware-ipw2x00  20180518-1
ii  firmware-ivtv 20180518-1
ii  firmware-iwlwifi  20180518-1
ii  firmware-libertas 20180518-1
ii  firmware-linux-nonfree20180518-1
ii  firmware-misc-nonfree 20180518-1
ii  firmware-myricom  20180518-1
ii  firmware-netxen   20180518-1
ii  firmware-qlogic   20180518-1
ii  firmware-realtek  20180518-1
ii  firmware-samsung  20180518-1
pn  firmware-siano
ii  firmware-ti-connectivity  20180518-1
pn  xen-hypervisor

-- no debconf information

-- 
Aug 24 17:35:28 n555 kernel: [29457.169632] ACPI: Low-level resume complete
...
Aug 24 17:35:28 n555 kernel: [29458.032279] sysfs group 'byte_queue_limits' not 
found for kobject 'tx-0'
Aug 24 17:35:28 n555 kernel: [29458.032291] WARNING: CPU: 1 PID: 24767 at 
/build/linux-LgHyGB/linux-4.17.17/fs/sysfs/group.c:235 
sysfs_remove_group+0x76/0x80
Aug 24 17:35:28 n555 kernel: [29458.032292] Modules linked in: uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev 
media ctr ccm dm_snapshot dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio uas usb_storage vhost_net vhost macvtap macvlan tap cmac rfcomm 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
overlay xt_comment xt_multiport xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
tun bridge stp ebtable_filter ebtables ip6table_filter ip6_tables appletalk 
devlink iptable_filter ax25 ipx(C) p8023 p8022 psnap llc cpufreq_userspace 
cpufreq_conservative cpufreq_powersave bnep binfmt_misc arc4 intel_rapl btusb 
btrtl btbcm btintel
Aug 24 17:35:28 n555 kernel: [29458.032333]  x86_pkg_temp_thermal 
intel_powerclamp bluetooth kvm_intel drbg ansi_cprng snd_hda_codec_hdmi kvm 
mac80211 ecdh_generic irqbypass intel_cstate snd_hda_codec_realtek 
snd_hda_codec_generic intel_uncore intel_rapl_perf rtsx_pci_ms joydev 
snd_hda_intel serio_raw pcspkr snd_hda_codec wmi_bmof memstick snd_hda_core 
cfg80211 snd_hwdep iTCO_wdt mei_me snd_pcm iTCO_vendor_support sg snd_timer 
shpchp ie31200_edac mei thinkpad_acpi nvram snd soundcore tpm_tis rfkill 
tpm_tis_core battery ac tpm rng_core evdev pcc_cpufreq nfsd fuse 

Bug#907216: ganeti: autopkgtest needs update for new version of openssl

[Paul Gevers]

Source: ganeti
Version: 2.16.0~rc2-4
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:openssl
Control: block 907015 by -1

Dear maintainers,

With a recent upload of openssl the autopkgtest of ganeti started to
fail in testing. I copied the output below.

Of course, openssl shouldn't just break your autopkgtest (or even worse,
your package), but the change in openssl was intended and your package
needs to update to the new situation. If needed, please change the bug's
severity.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from openssl should really add
a versioned Breaks on the unfixed version of (one of your) package(s),
hence I added a blocking relation on the openssl bug that tracks that.
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

A quote from the openssl maintainer about the openssl update:
"
This is probably the result of the default openssl.cfg now having:
[system_default_sect]
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=2

Where the SECLEVEL 2 requires a 112 / 2048 bit security level.
"

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=openssl

https://ci.debian.net/data/autopkgtest/testing/amd64/g/ganeti/874884/log.gz

 2018-08-24 04:43:10.452348 time=0:01:11.326832 [TestClusterInit]
gnt-cluster init
Failure: command execution error:
Could not start daemons, command /usr/lib/ganeti/daemon-util start-all
had exitcode 1 and error Error in the RPC HTTP reply from 'Node
{nodeName = "node1", nodePrimaryIp = "192.0.2.10", nodeSecondaryIp =
"192.0.2.10", nodeMasterCandidate = True, nodeOffline = False,
nodeDrained = False, nodeGroup = "a6f657a0-e169-488e-a845-05bebad2df85",
nodeMasterCapable = True, nodeVmCapable = True, nodeNdparams =
PartialNDParams {ndpOobProgramP = Nothing, ndpSpindleCountP = Nothing,
ndpExclusiveStorageP = Nothing, ndpOvsP = Nothing, ndpOvsNameP =
Nothing, ndpOvsLinkP = Nothing, ndpSshPortP = Nothing, ndpCpuSpeedP =
Nothing}, nodePowered = True, nodeHvStateStatic = GenericContainer
{fromContainer = fromList []}, nodeDiskStateStatic = GenericContainer
{fromContainer = fromList []}, nodeCtime = Fri Aug 24 04:42:06 UTC 2018,
nodeMtime = Fri Aug 24 04:42:06 UTC 2018, nodeUuid =
"079481f6-ded9-407f-995e-82417744f909", nodeSerial = 1, nodeTags =
fromList []}': CurlLayerError "code: CurlSSLCertProblem, explanation:
could not load PEM client certificate, OpenSSL error error:140AB18E:SSL
routines:SSL_CTX_use_certificate:ca md too weak, (no key found, wrong
pass phrase, or wrong file format?)"
No voting RPC result from ["node1"]



signature.asc
Description: OpenPGP digital signature

Bug#907215: python3.6: FTBFS with openssl as tests needs update for new version of openssl

[Paul Gevers]

Source: python3.6
Version: 3.6.6-2
Severity: serious
Tags: ftbfs
X-Debbugs-CC: debian...@lists.debian.org, open...@packages.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:openssl
Control: block 907015 by -1

Dear maintainers,

With a recent upload of openssl the autopkgtest of python3.6 started to
fail in testing. I copied the some of the output below.

Also the latest run on reproducible builds failed (it timed out, but
lots of errors before it did).

Currently this regression is contributing to the delay of the migration
of openssl to testing [1]. Of course, openssl shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in openssl was intended and your package needs to update to the
new situation. If needed, please change the bug's severity.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from openssl should really add
a versioned Breaks on the unfixed version of (one of your) package(s),
hence I added a blocking relation on the openssl bug that tracks that.
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

A quote from the openssl maintainer about the openssl update:
"
This is probably the result of the default openssl.cfg now having:
[system_default_sect]
MinProtocol = TLSv1.2
CipherString = DEFAULT@SECLEVEL=2

Where the SECLEVEL 2 requires a 112 / 2048 bit security level.
"

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=openssl

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.6/874866/log.gz

==
ERROR: test_session_handling (test.test_ssl.ThreadedTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/test/test_ssl.py", line 3579, in
test_session_handling
s.connect((HOST, server.port))
  File "/usr/lib/python3.6/ssl.py", line 1100, in connect
self._real_connect(addr, False)
  File "/usr/lib/python3.6/ssl.py", line 1091, in _real_connect
self.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 1068, in do_handshake
self._sslobj.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ConnectionResetError: [Errno 104] Connection reset by peer

==
FAIL: test_options (test.test_ssl.ContextTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/test/test_ssl.py", line 908, in test_options
self.assertEqual(default, ctx.options)
AssertionError:  !=


==
FAIL: test_default_ciphers (test.test_ssl.ThreadedTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/test/test_ssl.py", line 3088, in
test_default_ciphers
s.connect((HOST, server.port))
AssertionError: OSError not raised

==
FAIL: test_default_ecdh_curve (test.test_ssl.ThreadedTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/test/test_ssl.py", line 3142, in
test_default_ecdh_curve
self.assertIn("ECDH", s.cipher()[0])
AssertionError: 'ECDH' not found in 'TLS_AES_256_GCM_SHA384'

==
FAIL: test_shared_ciphers (test.test_ssl.ThreadedTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/test/test_ssl.py", line 3460, in
test_shared_ciphers
self.fail(name)
AssertionError: TLS_AES_256_GCM_SHA384

--
Ran 125 tests in 1.763s

FAILED (failures=4, errors=8, skipped=8)



signature.asc
Description: OpenPGP digital signature

Bug#828451: netty fix released, netty-tcnative patch accepted

[Kurt Roeckx]

On Mon, May 28, 2018 at 05:59:08PM +0200, Emilio Pozuelo Monfort wrote:
> On Tue, 17 Apr 2018 20:55:00 +0200 Emilio Pozuelo Monfort  
> wrote:
> > On Wed, 24 Jan 2018 11:07:19 + deb...@fau.xxx wrote:
> > > Upstream have accepted both patches. netty 4.1.20 has been released,
> > > which will run against a patched netty-tcnative. There hasn't been a
> > > netty-tcnative release.
> > 
> > There's a new netty-tcnative release, 2.0.8. Is that incompatible with the
> > current version of netty, or why can't we update to that? Sorry, I'm not
> > familiar with netty, just looking at this as I'd like to get rid of 
> > openssl1.0
> > for buster.
> 
> Ping?

Ping

Bug#907072: lintian: verify AppStream metainfo metadata_license matches debian/copyright

[Chris Lamb]

tags 907072 + moreinfo
thanks

Hi dkg,

> The gnupg2 source package version 2.2.9-1 has this mismatch because i
> was sloppy.

So, debian/copyright contains:

   Files: debian/org.gnupg.scdaemon.metainfo.xml
   Copyright: 2017 Daniel Kahn Gillmor 
   Comment: This file is licensed permissively for the sake of AppStream
   License: CC0-1.0

... and debian/org.gnupg.scdaemon.metainfo.xml contains:

   
   
 org.gnupg.scdaemon
 GPL
 scdaemon
 USB SmartCard Readers
 
   
 GnuPG's scdaemon provides access to USB tokens and smartcard
 readers that provide cryptographic functionality (e.g. use of
 protected secret keys).
   
 
   [...]

... which is installed to /usr/share/metainfo via debian/
scdaemon.install.

Thus, whilst we can rely on such metadata files existing in /usr/share/
metainfo/*.xml (or similar) we don't know which file in the source tree
this originated from (and thus it's license).

Ideas?


Regards,

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

Bug#906957: malformed-debian-changelog-version wrongly reported with debian revision 0

[Chris Lamb]

tags 906957 + pending
thanks

Hi,

Applied Felix's MR [0] in Git, pending upload. Bug-closing commit is:

  
https://salsa.debian.org/lintian/lintian/commit/635b6859946608d6ade77eaf306b252b5e7f0d8d

  checks/source-changelog.pm | 12 ++--
  debian/changelog   |  3 +++
  2 files changed, 9 insertions(+), 6 deletions(-)

  [0] https://salsa.debian.org/lintian/lintian/merge_requests/20


Regards,

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

Bug#907042: opam 1.2.0 is deprecated (jessie)

[Nicolas Braud-Santoni]

On Thu, Aug 23, 2018 at 07:39:13PM +0200, Mehdi Dogguy wrote:
> On 2018-08-23 16:53, Nicolas Braud-Santoni wrote:
> > On Thu, Aug 23, 2018 at 03:00:22PM +0200, Mehdi Dogguy wrote:
> > > > It makes opam unusable for jessie users: already initialised ones can't
> > > > install new compilers nor update packages, and with a fresh install opam
> > > > is almost unusable (e.g. [3]).
> > > 
> > > Unfortunately, we won't be able to upgrade Opam to 1.2.2 in Debian
> > > stable.
> 
> fwiw, I meant "oldstable" above.

Yes, I didn't even notice the mistake  :3
(i.e. I understood we were talking about jessie)


> > > I can ask for its removal, or document in this bugreport how to
> > > point their
> > > installation to a frozen working mirror?
> > 
> > Doesn't the release policy allow shipping a new upstream version to
> > *-pu, if
> > there is no other way to get the bug resolved (and after consulting the
> > release
> > team) ?  Or is the issue that there won't be new point releases ?
> 
> I am not sure what the Release Team would accept at this point (Jessie is
> already EOL'ed). So, a sloppy-backport should be enough for oldstable
> users. They can upgrade to stable if necessary.

OK, that's fair enough; I had no idea whether there would be a point
release in the future where we could have that put, or through LTS.

Do you mind if I check with Ben? IIRC he does some LTS work, and I'm seeing
him this weekend (at OMGWTFBBQ).


> Once, 2.0 will be ready in Buster, Stretch users can use from backports.

Yeap, I am very much planning to make a backport.

Speaking of which, the version of opam in the packaging repo should be
good-to-go, it's just blocked on someone sponsoring the upload; I asked
highvoltage to do so, at the end of DebConf, but I guess he isn't very
available currently, so fill free to review & dput if you feel like it.

Worst case, I might get to upload 2.0 by myself within some weeks, at I'm
currently going through the NM process.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#907214: OMEMO-encrypted file is not unencrypted before saving

[Sven Bartscher]

Package: gajim
Version: 1.0.3-1
Severity: normal

Greetings,

I tried to receive a file transferred to me from a Pix Art
Messenger[1] through an OMEMO encryptecd chat. The file was
transferred successfully, but I wasn't able to open it
afterwards. file(1) reported no recognized file type for the file.

[1]: https://jabber.pix-art.de/

When I tried the transfer again, after switching off OMEMO, I was able
to open the file after the transfer. This looks to me as if Gajim
saves the encrypted file as-is without decrypting it, which makes the
received file practically useless.

Please note that I didn't have this problem when sending files from
Gajim to other messengers.

Regards
Sven

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

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

Versions of packages gajim depends on:
ii  gir1.2-gtk-3.03.22.30-2
ii  python3   3.6.5-3
ii  python3-gi3.28.3-1
ii  python3-gi-cairo  3.28.3-1
ii  python3-idna  2.6-1
ii  python3-nbxmpp0.6.6-1
ii  python3-openssl   18.0.0-1
ii  python3-pyasn10.4.2-3

Versions of packages gajim recommends:
ii  alsa-utils   1.1.6-1
ii  aspell-de [aspell-dictionary]20161207-5
ii  aspell-de-1901 [aspell-dictionary]   1:2-33
ii  aspell-en [aspell-dictionary]2017.08.24-0-0.1
ii  ca-certificates  20170717
ii  dbus 1.12.10-1
ii  fonts-noto-color-emoji   0~20180424-2
ii  gajim-omemo  2.6.0-1
ii  gajim-pgp1.2.7-1
ii  gir1.2-farstream-0.2 0.2.8-4
ii  gir1.2-geoclue-2.0   2.4.12-1
ii  gir1.2-gspell-1  1.6.1-1
ii  gir1.2-gst-plugins-base-1.0  1.14.2-1
ii  gir1.2-gstreamer-1.0 1.14.2-2
ii  gir1.2-gupnpigd-1.0  0.2.5-2
ii  gir1.2-secret-1  0.18.6-1
pn  gstreamer0.10-plugins-ugly   
ii  notification-daemon  3.20.0-3
ii  pulseaudio-utils 11.1-5
ii  python3-crypto   2.6.1-9+b1
ii  python3-dbus 1.2.8-2+b1
ii  python3-gnupg0.4.3-1
ii  python3-keyring  13.1.0-1
ii  python3-pil  5.2.0-2
ii  python3-precis-i18n  1.0.0-1
ii  sox  14.4.2-3
ii  xfce4-notifyd [notification-daemon]  0.4.2-1

Versions of packages gajim suggests:
ii  avahi-daemon  0.7-4
ii  libxss1   1:1.2.2-1+b2
pn  nautilus-sendto   
pn  python3-avahi 
pn  python3-gconf 
pn  python3-gnome2
pn  python3-kerberos  
ii  python3-pycurl7.43.0.1-0.2+b1

-- no debconf information

Bug#883434:

[J. Smith]

By experiment, this issue is present since Emacs 23.1.
Perhaps it therefore does not have to hold up the testing migration of Emacs 25.

Bug#903500: python-rstlib-fb: I believe some changes are missing

[Thomas Goirand]

On 08/24/2018 01:38 PM, Christophe Vu-Brugier wrote:
> Hi Thomas,
> 
> On Fri, 24 Aug 2018 12:41:17 +0200, Thomas Goirand wrote :
>> I prefer to package 2.1.fb66, as this is what OpenStack gates on.
> 
> OK. The difference is minor because version 2.1.fb66 and 2.1.fb67 differ
> only by a single commit.
> 
> 
>> Could you explain this?
>> https://salsa.debian.org/cvubrugier-guest/python-rtslib-fb/commit/01763af1f2303d06b127e23a20bb178e1505ac6f
> 
> That's exactly the same as your patch in branch debian/rocky:
> 
>   
> https://salsa.debian.org/openstack-team/python/python-rtslib-fb/commit/14df33e261ee9e840784e8bff4d0e54552795b97
> 
> 
> With your latest changes, I think the package is in good shape. It will
> allow us to upgrade targetcli-fb soon. Thanks!
> 
> Cheers,

FYI, it may take me a few days/weeks more to finish the OpenStack
release and upload it (with rtslib-fb) to Sid. Thanks for your
understanding.

Cheers,

Thomas Goirand (zigo)

Bug#903757: Acknowledgement (gimp: Free Select Tool: Add or Substract selection only after pressing ENTER-Key)

[Reiner]

Dear Maintainer,

the upstream-developer says, that it isn't a bug
(https://gitlab.gnome.org/GNOME/gimp/issues/2028).
So you can close the bug report.

Thanks
Reiner

Bug#893713: debootstrap-udeb: containts too many scripts files (most of them are symlink but...)

[Hideki Yamane]

On Tue, 21 Aug 2018 12:37:00 +0200
Raphael Hertzog  wrote:
> While cleaning up the list of scripts to keep, you decided to drop the
> scripts for all derivatives making it impossible to use the udeb built
> for Debian on any derivative (Kali bug report here:
> https://bugs.kali.org/view.php?id=4921)

 It was not correct assumptions that derivatives use it own udeb
 packages, my apologies.


> So you saved a few kilobytes and made the life harder for others.
> IMO it was the wrong decision.

 It was my mistake, of course, but I DON'T WANT TO MAKE SOMEONE'S LIFE
 ANY HARDER, IT IS NOT INTENDED. People who made wrong decision should
 be blamed as fool? If so, please revert debootstrap before I started 
 to commit to it.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#907213: RFS: klatexformula/4.0.0-4

[Tobias Winchen]

Package: sponsorship-requests
Severity: normal 

Dear mentors,

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

* Package name: klatexformula
   Version : 4.0.0-4
   Upstream Author : Philippe Faist 
* URL :  http://klatexformula.sourceforge.net/
* License : GPL-2+
   Section : tex

  It builds those binary packages:

klatexformula - GUI to easily get an image from a LaTeX formula or 
equation
 libklatexformula4 - Runtime libraries for klatexformula
 libklatexformula4-dev - Runtime libraries for klatexformula, development files

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/k/klatexformula/
klatexformula_4.0.0-4.dsc

  Changes since the last upload:

  [ Tobias Winchen ]
  * Updated to standards version 4.2.0
  * Switched to debhelper compat 11

  [ Juhani Numminen ]
  * Patch to add missing include (Closes: #907000)

  Regards,
   Tobias Winchen

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

Bug#907212: RFS: golang-github-xanzy-go-gitlab/0.0~git20180814.f3bc634-1 [ITP]

[Felix Lechner]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "golang-github-xanzy-go-gitlab"

It is a prerequisite for 'git-lab' (https://bugs.debian.org/898246),
which I packaged as well.


* Package name: golang-github-xanzy-go-gitlab
  Version : 0.0~git20180814.f3bc634-1
  Upstream Author : Sander van Harmelen 
* URL : https://github.com/xanzy/go-gitlab
* License : Apache-2.0
  Section : devel

It builds those binary packages:

  golang-github-xanzy-go-gitlab-dev - Simple and uniform GitLab API for Go

To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/golang-github-xanzy-go-gitlab


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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-xanzy-go-gitlab/golang-github-xanzy-go-gitlab_0.0~git20180814.f3bc634-1.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

  * Initial Debian packaging


  Regards,
   Felix Lechner

Bug#907211: yosys: FTBFS on i386

[Ivo De Decker]

package: yosys
version: 0.7-7
severity: serious

Hi,

The latest upload of yosys seems to FTBFS on i386, preventing migration to
testing:

https://buildd.debian.org/status/package.php?p=yosys

Cheers,

Ivo

Bug#907210: libfastahack: ftbfs on some architectures (symbols)

[Ivo De Decker]

package: libfastahack
version: 0.0+git20160702.bbc645f+dfsg-2
severity: serious

Hi,

The latest upload of libfastahack FTBFS on a number of architectures (it seems
to be related to the symbols):

https://buildd.debian.org/status/package.php?p=libfastahack

Cheers,

Ivo

Bug#907209: RFS: engauge-digitizer/10.9+ds.1-1

[Tobias Winchen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "engauge-digitizer"

 * Package name: engauge-digitizer
   Version : 10.9+ds.1-1
  Upstream Author : Mark Mitchell 
 * URL : https://github.com/markummitchell/engauge6
 * License : GPL-2+
   Section : science

 It builds those binary packages:

engauge-digitizer - interactively extracts numbers from bitmap graphs or 
maps
 engauge-digitizer-doc - engauge-digitizer user manual and tutorial

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

  https://mentors.debian.net/package/engauge-digitizer

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

dget -x https://mentors.debian.net/debian/pool/main/e/engauge-digitizer/
engauge-digitizer_10.9+ds.1-1.dsc

  Changes since the last upload:

  * New upstream release
  * Handle repacking in watch file
  * Update to dh compat 11
  * Updated to standards version 4.2.0


Bests,
   Tobias Winchen

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

Bug#907208: dgit quilt-fixup sometimes runs dpkg-source

[Ian Jackson]

Package: git-debrebase
Version: 6.9

1.  git checkout -B spong
dgit quilt-fixup
   => always runs dpkg-source, not gdr

2. My xen tree does this too,  git-show-ref output below.
   I'm on dgit/experimental.draft.

Ian

6aabb93ad745360200d7a22e38a7e5c3aec40349 
refs/debrebase-last/heads/dgit/experimental.draft
d9ac156e5b6ad973b864f3e2e9af1964ddd8232c 
refs/debrebase-last/heads/dgit/sid.draft
c031dffe0a023e4cc0d2155095c70c9b6f0add0e 
refs/debrebase-last/heads/dgit/stretch-security
608da93bea0e632fd997942690c1cdb9bbbf7311 refs/dgit-badcommit/heads/base
4b7e4bf5db18250d397e7e21c049e827d7fb7564 refs/dgit-badcommit/heads/t
c3e81bfc0ab2109367114a0f471db12ea3a1926b 
refs/dgit-badcommit/remotes/dgit/dgit/sid
f81d7eda8f7c9fe24b28a5684663490afe524c85 
refs/dgit-badcommit/remotes/mariner/old.2016-12-21.rebase
e506772909ff8b5edc7a52d6cd2c7fa6fb216f49 
refs/dgit-badcommit/tags/archive/debian/4.8.0_rc3-1
fa1c710257f1477a85da5a28fcbd794ef987287c 
refs/dgit-badcommit/tags/archive/debian/4.8.0_rc5-1
1e868c397880f5e46fe4686943360a6dd2698ee5 
refs/dgit-fetch/debian-security/dgit-rewrite/map
1e868c397880f5e46fe4686943360a6dd2698ee5 refs/dgit-fetch/debian/dgit-rewrite/map
6aabb93ad745360200d7a22e38a7e5c3aec40349 refs/heads/bar
4389821e110b7e358aacb91d7d6fc5f4725e47b2 refs/heads/base
3db0ad91e3139c906797a9ce22ea0270ecfbf5c0 refs/heads/dgit-test
547439e519c6e07db8e57318ad80d8eabf390134 refs/heads/dgit/experimental
6aabb93ad745360200d7a22e38a7e5c3aec40349 refs/heads/dgit/experimental.draft
94c6e866f5ea7dda3850c5373564fdcc94ea246f refs/heads/dgit/jessie-security
8ae0a50de883404025fa47d658b382b23e451ce3 refs/heads/dgit/sid
f45ede8b9b47779ea9dc17246bc286e97e490fa4 refs/heads/dgit/stretch-security
34b8e1f9ba5cc675e61934400692eefbe2e35ddc refs/heads/dgit/stretch-security.old
3023e86e285f7486e96d20445b8653062b44194a refs/heads/master
2f4973b9cff933774f7c638f1f0894d0d07f6643 refs/heads/t
c9517ee45383271e90f40b7a9773d1e6fefaeca7 refs/heads/xen
006b994b0bf60e8cf9328fbed971c967e8f4a7d9 refs/heads/xen2
1c736dc47511943f2a707c93e25c8c1424573c63 refs/remotes/alioth/debian/jessie
0f4cbe03ba4b19b773bd0c57aef266568b67e40e refs/remotes/alioth/develop
88dd4600308daa7d337949c49b5e95e3e571cbde refs/remotes/alioth/feature/4.5.1_rc2
57e0a490c53a029d0921edde9e1acdc158ac2164 refs/remotes/alioth/feature/bug737613
c617b4af156647ad4d390c4061ca3ee72100f99f refs/remotes/alioth/feature/bug763102
46a8d71bec748f3c6dfb98bf4ba3973a5b3cd951 refs/remotes/alioth/feature/bug764912
fcdd6e3c9596e900748e93ae3be4e6a3dc278f26 refs/remotes/alioth/feature/bug770456
1d629591f9e4726c587436d4b6a4c7fbfa01c568 refs/remotes/alioth/feature/bug805508
fa05482b9559792ed384f823f7e12542c38547e4 refs/remotes/alioth/feature/reportbug
6256576635eecce3b7854c5e0e412e9d4680b8ab refs/remotes/alioth/master
dcd5c8f340f6a536b5444e3caf36d21537ecd6ce refs/remotes/alioth/pristine-tar
b6c60b9ecfa3d62bbd7a1fcacac28666fafac8f4 
refs/remotes/alioth/pristine-tar-feature/4.5.1_rc2
9fafe903bcadf774d3eb5fbef4666166aa876d2d refs/remotes/alioth/upstream-develop
dbbefae5a80974e7b2c273d8a653f9f42884bda5 
refs/remotes/alioth/upstream-feature/4.5.1_rc2
547439e519c6e07db8e57318ad80d8eabf390134 refs/remotes/dgit/dgit/experimental
f1f747efc2bceef92836028980a39471aed78fdc refs/remotes/dgit/dgit/jessie-security
9b0913e2350ec26f82f3155f34ee12b5cd4ab8c8 refs/remotes/dgit/dgit/sid
a914d20cf7eadff187abcb7e285e91ed1c7364c8 refs/remotes/dgit/dgit/stretch-security
006b994b0bf60e8cf9328fbed971c967e8f4a7d9 refs/remotes/dgit/dgit/yakkety
6ca01d7661d4165128987891226a117731adf996 
refs/remotes/iwj-xenbits/wip.jessie-security
b03cee73197f4a37bf2941b9367105187355e638 refs/remotes/mariner/base.new
496673a2ada93c201fbe1cc83146c8bd8e79169d refs/remotes/mariner/base.old
227ecd3f78fcfdfe15b54ca259feb59cff7549bd 
refs/remotes/mariner/bogosity49-see-852545
fe8d7d3469b996b93a0ed0054590f64e5ae6aaaf refs/remotes/mariner/breakwater
06e2747918cfe66650311cdb1a5578d262309bb6 
refs/remotes/mariner/dgit/jessie-security
dbaded8ee20dd714c09bdf7ef52fae994a1e2787 refs/remotes/mariner/dgit/sid
4b81d1570d917e5015461eee1f349a6c1c9a4b58 
refs/remotes/mariner/dgit/sid.obsolete.found.2017-09-05
ec9a665aba0382c33e27b1cbcfca2045427fff1b 
refs/remotes/mariner/dgit/stretch-security
1bec8a30954e277758f92e68c1fcca0bba1555ec refs/remotes/mariner/knorrie/next
7b3c741e0e89ab9fb31585863e75d87aca9cda8a 
refs/remotes/mariner/old.2016-12-21.rebase
f80e4379297cad031217cb95b385795c5ea383d9 
refs/remotes/mariner/pseudo-upstream-4.8
e017133490d35eab64c0a61bfb233162fda4 refs/remotes/mariner/t
2c6029ed76fb5e28e869b33ba285f50b8f5feb7f refs/remotes/mariner/t.compare
f3ce9cf107adf0c828c97a52f203d762c3c26345 refs/remotes/mariner/t.out
6b3aa54b74dc9b61ca296f68df6dfb4dced26dfd 
refs/remotes/mariner/to-delete.2016-12-21.rebase
e1cefedd80f9972854769bfc6e32e23b56cd0712 refs/remotes/mariner/upstream
1bb0ee913b35da4d4e6a86b92beb01aa5f77e5c9 refs/remotes/mariner/wip.879751
ae9bac750380b4751ea7285e0ff89eacc05642e5 refs/remotes/mariner/wip.knorrie

Bug#902567: tasksel: Please remove occurrences of "kdesudo" and coordinate with d-i

[Holger Wansing]

Hi,

Boyuan Yang <073p...@gmail.com> wrote:
> Control: tags -1 + patch
> Control: forwarded -1 
> https://salsa.debian.org/installer-team/tasksel/merge_requests/3
> X-Debbugs-CC: hwans...@mailbox.org
> 
> Dear tasksel maintainers,
> 
> I have prepared a patch (Merge Request) on Debian Salsa to solve this bug.
> Please review it and merge it if you find it acceptable.
> 
> The d-i package (user-setup) is no longer using kdesudo thus this dependency 
> can
> be removed safely.

Anyone objections against this ?

Holger


> 
> --
> Thanks,
> Boyuan Yang
> 
> On Thu, 28 Jun 2018 10:35:42 +0800 Boyuan Yang <073p...@gmail.com> wrote:
> > Source: tasksel
> > Version: 3.44
> > Severity: important
> > X-Debbugs-CC: debian-b...@lists.debian.org
> > 
> > Dear d-i developers and tasksel maintainers,
> > 
> > Package "kdesudo" has been removed in Debian since September 2017.
> > 
> > Tasksel still recommends non-existent "kdesudo" in task-kde-desktop. Please 
> > consider removing this entry from "Recommends: " field.
> > 
> > However, I noticed the following lines in debian/control:
> > 
> > 
> > Package: task-kde-desktop
> > Architecture: all
> > Description: KDE
> >  This task package is used to install the Debian desktop, featuring
> >  the KDE desktop environment, and with other packages
> >  that Debian users
> >  expect to have available on the desktop.
> > Depends: ${misc:Depends}, 
> > task-desktop,
> > kde-standard,
> > sddm,
> > Recommends:
> > [...]
> > 


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#907207: phlipple: build compatibility with -Wl,--as-needed

[Steve Langasek]

Package: phlipple
Version: 0.8.5-3
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Dear maintainers,

The phlipple package is failing to build in Ubuntu, because the linker is
failing to find symbols from libm:

[...]
gcc -Wall -g -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  
-Wl,-Bsymbolic-functions -Wl,-z,relro -lm -o phlipple camera.o engine.o game.o 
gfxconstants.o gradientrenderer.o interpolator.o levels.o main.o mainscreen.o 
osinterface_sdl.o phlipplerootscene.o quad.o quadrenderer.o scenes.o settings.o 
textrenderer.o texture.o vertex.o -lSDL -lvorbisfile -lGLEW -lGLU -lGL   -lGLU 
-lGL -lSDL_mixer -lSDL_image
/usr/bin/ld: engine.o: undefined reference to symbol 'sin@@GLIBC_2.2.5'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:392: phlipple] Error 1
[...]

 (https://launchpad.net/ubuntu/+source/phlipple/0.8.5-3)

I see you have already tried to handle the lack of -lm in the upstream
Makefile by adding it to LDFLAGS in debian/rules.  However, using LDFLAGS
for this doesn't work on Ubuntu because Ubuntu's toolchain uses
-Wl,--as-needed by default, which means that libraries must be listed
/after/ the objects which reference them, or else the linker will discard
them from the final binary as unused.

  https://wiki.ubuntu.com/ToolChain/CompilerFlags#A-Wl.2C--as-needed

Please consider the attached patch as a solution that works for both Debian
and Ubuntu.  It probably needs further enhancement to be suitable for
upstream, since there are non-glibc platforms that don't have libm as a
separate library.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru phlipple-0.8.5/debian/patches/link-libm.patch 
phlipple-0.8.5/debian/patches/link-libm.patch
--- phlipple-0.8.5/debian/patches/link-libm.patch   1969-12-31 
16:00:00.0 -0800
+++ phlipple-0.8.5/debian/patches/link-libm.patch   2018-08-24 
10:33:31.0 -0700
@@ -0,0 +1,17 @@
+Description: Explicitly link against libm
+ phlipple requires sin() which is provided by libm.  Ensure that we link
+ to it, avoiding a build failure.  This won't work on platforms that don't
+ have a separate libm.
+Author: Steve Langasek 
+Last-Modified: 2018-08-24
+
+Index: phlipple-0.8.5/src/Makefile.am
+===
+--- phlipple-0.8.5.orig/src/Makefile.am
 phlipple-0.8.5/src/Makefile.am
+@@ -48,4 +48,4 @@
+   
+ phlipple_LDFLAGS = 
+ 
+-phlipple_LDADD = $(PHLIPPLE_LIBS) $(GL_LIBS) 
++phlipple_LDADD = $(PHLIPPLE_LIBS) $(GL_LIBS) -lm
diff -Nru phlipple-0.8.5/debian/patches/series 
phlipple-0.8.5/debian/patches/series
--- phlipple-0.8.5/debian/patches/series2018-05-20 14:40:34.0 
-0700
+++ phlipple-0.8.5/debian/patches/series2018-08-24 10:33:45.0 
-0700
@@ -1,2 +1,3 @@
 support_us.patch
 desktop-file.patch
+link-libm.patch
diff -Nru phlipple-0.8.5/debian/rules phlipple-0.8.5/debian/rules
--- phlipple-0.8.5/debian/rules 2018-05-20 14:40:34.0 -0700
+++ phlipple-0.8.5/debian/rules 2018-08-24 10:16:28.0 -0700
@@ -2,7 +2,6 @@
 
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
-export DEB_LDFLAGS_MAINT_APPEND = -lm
 
 %:
dh $@

Bug#907206: git-debrebase: error: Patch export produced patch amendments

[Ian Jackson]

Package: git-debrebase
Version: 6.9

zealot:xen> git-debrebase make-patches

git-debrebase: error: Patch export produced patch amendments
(abandoned output commit 665aae927a1bb31fdd54253f0178244c5efb3e69).
Try laundering first.
zealot:xen> git-rev-parse HEAD
6aabb93ad745360200d7a22e38a7e5c3aec40349
zealot:xen>

This can be found at:
  g...@salsa.debian.org:xen-team/debian-xen.git

I think it is confused by the subdirectory.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#857891: Bug

[Christian Göttsche]

Thanks.

> [user@localhost /etc/logrotate.d]$ grep daemon /var/lib/logrotate/status
> "/var/log/daemon.log" 2018-8-24-9:0:0

So logrotate ran between 9am and 10am today on the daemon.log file.
But apparently did not rotate it.

> [user@localhost /etc/logrotate.d]$ sudo journalctl -u logrotate.service
> -- Logs begin at Fri 2018-08-24 19:54:13 MSK, end at Fri 2018-08-24 20:19:39 
> MSK. --
> -- No entries --

As your journald logs do not persist reboots, are there any logrotate
related error messages in /var/log/syslog (maybe something related in
the 9am-10am time-span)?

Bug#907196: gi.repository.IBus fails to Import

[Helmut Grohne]

Control: retitle -1 unnecessary dependency on python3:any
Control: severity -1 wishlist

On Fri, Aug 24, 2018 at 05:35:09PM +0200, Helmut Grohne wrote:
> # apt-get install gir1.2-ibus-1.0:i386 python3-gi

Laurent explained to me that this is not how things are supposed to
work. For using the python override, you must depend on python3-gi of
the same architecture. Of course, that pulls in python3. Everyone else
doesn't need python3 (for e.g. ruby, etc.), so the dependency is useless
and should be removed.

Helmut

Bug#907204: kdepim-runtime: FTBFS in buster/sid (invalid use of incomplete type 'class QTabBar')

[Santiago Vila]

Package: src:kdepim-runtime
Version: 4:17.12.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/<>'
dh_testdir  # [-a]
# Running override target (override_dh_auto_configure)
test -z "`ls debian/*.debhelper.log 2>/dev/null`" || sed -i 
'/^override_dh_auto_configure[[:space:]]/d' debian/*.debhelper.log
/usr/bin/make -f debian/rules override_dh_auto_configure 
DH_INTERNAL_OVERRIDE="dh_auto_configure"  # [-a]
make[2]: Entering directory '/<>'
dh_auto_configure '--buildsystem=kf5' --parallel  -- -DBUILD_TESTING=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DBUILD_TESTING=OFF ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works

[... snipped ...]

cd /<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource && 
/usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic 
-DKDE_UIC_FILE:FILEPATH=/<>/resources/shared/singlefileresource/settingsdialog.ui
 
-DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource/ui_settingsdialog.h
 -DKDE_UIC_BASENAME:STRING=settingsdialog -P 
/usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake
[  6%] Generating ui_singlefileresourceconfigdialog_desktop.h
cd /<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource && 
/usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic 
-DKDE_UIC_FILE:FILEPATH=/<>/resources/shared/singlefileresource/singlefileresourceconfigdialog_desktop.ui
 
-DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource/ui_singlefileresourceconfigdialog_desktop.h
 -DKDE_UIC_BASENAME:STRING=singlefileresourceconfigdialog_desktop -P 
/usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake
[  6%] Generating ui_singlefileresourceconfigdialog.h
cd /<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource && 
/usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic 
-DKDE_UIC_FILE:FILEPATH=/<>/resources/shared/singlefileresource/singlefileresourceconfigdialog.ui
 
-DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource/ui_singlefileresourceconfigdialog.h
 -DKDE_UIC_BASENAME:STRING=singlefileresourceconfigdialog -P 
/usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> 
/<>/resources/shared/singlefileresource 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource 
/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource/CMakeFiles/akonadi-singlefileresource.dir/DependInfo.cmake
 --color=
Scanning dependencies of target akonadi-singlefileresource
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f 
resources/shared/singlefileresource/CMakeFiles/akonadi-singlefileresource.dir/build.make
 
resources/shared/singlefileresource/CMakeFiles/akonadi-singlefileresource.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  7%] Building CXX object 
resources/shared/singlefileresource/CMakeFiles/akonadi-singlefileresource.dir/singlefileresourcebase.cpp.o
cd /<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource && 
/usr/bin/c++  -DHAVE_TEXTTOSPEECH -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB 
-DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT 
-DQT_NO_URL_CAST_FROM_STRING -DQT_USE_FAST_OPERATOR_PLUS 
-DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB 
-DTRANSLATION_DOMAIN=\"akonadi_singlefile_resource\" -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -Dakonadi_singlefileresource_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource 
-I/<>/resources/shared/singlefileresource 
-I/<>/obj-x86_64-linux-gnu/resources/shared/singlefileresource/akonadi-singlefileresource_autogen/include
 -I/<>/resources/folderarchivesettings -isystem 
/usr/include/KF5/KI18n -isystem /usr/include/KF5 -isystem /usr/include/x86_64-l
 inux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/KF5/KCompletion -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 

Bug#907205: psi: FTBFS in buster/sid (no type named 'type' in 'struct std::enable_if')

[Santiago Vila]

Package: src:psi
Version: 1.3-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
qt-qconf
Project name: Psi
Profile: psi.pro
Deps: qt4* buildmodeapp* idn* qca* zlib* qjdns* x11* universal qdbus 
qtmultimedia* webkit growl whiteboarding xss aspell enchant hunspell spell* 
plugins conf* recursiveprl*

'configure' written.
'configure.exe' written.
ls -al
total 464

[... snipped ...]

 from /usr/include/Qca-qt5/QtCrypto/qca.h:36,
 from /usr/include/Qca-qt5/QtCrypto/QtCrypto:1,
 from accountmanagedlg.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note: candidate: 
'template static typename 
std::enable_if<((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2) [with Func1 = const 
char*; Func2 = const char*]':
accountmanagedlg.cpp:115:66:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: error: no type named 
'type' in 'struct std::enable_if'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note:   template 
argument deduction/substitution failed:
accountmanagedlg.cpp:115:66: note:   candidate expects 5 arguments, 3 provided
  connect(d->bg, SIGNAL(buttonClicked(int)), SLOT(bg_clicked(int)));
  ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qiodevice.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdatastream.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/qregion.h:49,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/qevent.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QList:1,
 from /usr/include/Qca-qt5/QtCrypto/qca_core.h:38,
 from /usr/include/Qca-qt5/QtCrypto/qca.h:36,
 from /usr/include/Qca-qt5/QtCrypto/QtCrypto:1,
 from accountmanagedlg.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2) [with Func1 = const 
char*; Func2 = const char*]':
accountmanagedlg.cpp:115:66:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: error: no type named 
'Object' in 'struct QtPrivate::FunctionPointer'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: 

Bug#907203: aufs-tools: recommends 4.17 kernel files though that kernel isn't installed

[Boruch Baum]

Package: aufs-tools
Version: 1:4.9+20170918-2
Severity: normal

Dear Maintainer,

My system does not have kernel 4.17 installed, so you can imagine my
surprise when my first attempt to install 'aufs-tools' included:

  linux-headers-4.17.0-2-amd64
  linux-headers-4.17.0-2-common
  linux-headers-amd64
  linux-kbuild-4.17

Performing the install with option '--no-install-recommends' corrected
that.

Please consider removing those 'recommends', or adjusting them somehow
for the user's particular installed kernel version.

-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 2.0.0 (ascii)
Release:2.0.0
Codename:   ascii
Architecture: x86_64

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

Versions of packages aufs-tools depends on:
ii  libc6  2.27-5

Versions of packages aufs-tools recommends:
pn  aufs-dkms  

aufs-tools suggests no packages.

-- no debconf information





-- 
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0

Bug#906411:

[Tiago Daitx]

The underlying cause seems to be a fix in maven-shared-utils 3.2,
which was uploaded recently. The fix MSHARED-610 [1] seems to have
exposed IOException that were previously being ignored, so surefire
now needs to be updated to handle those.

I have opened a bug report upstream (SUREFIRE-1558 [2]) to let them
know about it.

References:
[1] https://issues.apache.org/jira/browse/MSHARED-610
[2] https://issues.apache.org/jira/browse/SUREFIRE-1558

-- 
Tiago Stürmer Daitx
Software Engineer
tiago.da...@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE

Bug#907202: check_series_has_all_patches malfunctions with subdirs

[Ian Jackson]

Package: git-debrebase
Version: 6.9

The problem is that the memo did not include $recurse as part of the
lookup key.  This could have been serious, but luckily the result is
simply that git-debrebase complains about the directory names, as if
they were unused patches, instead.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#907201: [pkg-cryptsetup-devel] Bug#907201: cryptsetup-initramfs: Asks for disk password twice unless 'debug' is passed to kernel command line

[Guilhem Moulin]

Hi,

On Fri, 24 Aug 2018 at 18:49:10 +0200, Matthias Klumpp wrote:
> This issue is really annoying, and I would be glad for any pointers on
> how to investigate the issue further, as I am no expert on cryptsetup.

See https://wiki.debian.org/CryptsetupDebug to trace
/scripts/local-top/cryptroot, please attach the log file to this bug
afterwards :-)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#907082: orphaning packages

[Tobias Frost]

On Fri, Aug 24, 2018 at 02:50:50PM +0200, Guilhem Moulin wrote:
 
> Alright, waiting for further input from the MIA team then, and meanwhile
> reverting 62f6fd043ec401c516d90a033b60db563c8e735e.

Sorry, can't give input here. Garret wants to become active again;
that is very appreciated from the MIA-team perspective, but it is he now
who needs to follow up…

--
tobi

> Cheers,
> -- 
> Guilhem.




signature.asc
Description: PGP signature

Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1

[Kurt Roeckx]

On Fri, Aug 24, 2018 at 10:27:16AM +, Damyan Ivanov wrote:
> -=| Kurt Roeckx, 23.08.2018 22:32:13 +0200 |=-
> > Note that the SIGPIPE issue is probably a known upstream issue
> > that still needs to be fixed, we're at least still working on a
> > SIGPIPE issue.
> > 
> > But that does not mean that the other issues in libnet-ssleay-perl
> > should not get fixed.
> 
> I tried applying all the patches from the fedora package of 
> Net-SSLeay, and it didn't help much.
> 
> It was mentioned in the upstream ticket that an additional fix is 
> needed on libssl side, see 
> https://bugzilla.redhat.com/show_bug.cgi?id=1615098
> 
> The reproducer from there fails with 1.1.1~~pre9-1 from unstable.
> 
> Does this seem like something that needs to be fixed on the openssl 
> side?

This is something that should get fixed in whatever calls
TLSv1_method(). You should never call that function. It's also
been deprecated.

The problem is that TLSv1_method() only supports TLS 1.0, and the
default config now says that TLS 1.2 is the minimum verison. You
should either use SSLv23_method() or TLS_method(), which support all
protocol versions that are enabled.


Kurt

Bug#907201: cryptsetup-initramfs: Asks for disk password twice unless 'debug' is passed to kernel command line

[Matthias Klumpp]

Package: cryptsetup-initramfs
Version: 2:2.0.4-2
Severity: normal

Hi!
First of all, this bug appears on PureOS and I am currently working on
testing it on Debian as well. However, the issue started to appear at
the time cryptsetup was updated with massive changes in June, so I am
reasonably confident that it has something to do with this bug.

While trying to debug the issue, which originally appeared on a more
complex crypto setup, I have now reduced it to a simpler setup.
The system has a rootfs mounted as / with a LUKS-encrypted disk, as
well as a separate, unencrypted boot partition.

/etc/crypttab contains:
luks-90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6
UUID=90cebda2-1c6b-4ea8-9bac-6c3be8b3ced6 none luks

When booting the system, the very first thing shown to the user is a
bare prompt asking to unlock the root partition. You can enter an
arbitrary password there or the real one or just hit enter, the
outcome is the same: After a while, you get dropped into a proper
Plymouth-based screen which asks you again to enter the password for
the partition.
At this point, you need to supply the real password and the system boots fine.

I tried to debug this issue, and wanted to get more debug information
about what happens in the initramfs. Therefore I added the "debug"
parameter to the kernel command line - as a result the additional
superfluous prompt vanished and I was only asked for the right
password once.

This issue is really annoying, and I would be glad for any pointers on
how to investigate the issue further, as I am no expert on cryptsetup.
Also, adding "debug" fixing the problem makes this issue really
suspicious to me.

Thank you!
Regards,
Matthias

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#907200: ITP: kim-api -- KIM API is an Application Programming Interface for atomistic simulations

[Anton Gladky]

Package: wnpp
Severity: wishlist
Owner: Anton Gladky 

* Package name: kim-api
  Version : 2.0
  Upstream Author : Ryan S. Elliott
* URL : https://openkim.org/kim-api/
* License : COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 
1.0
  Programming Lang: C, C++, Fortran
  Description : KIM API is an Application Programming Interface for 
atomistic simulations

The KIM API is an Application Programming Interface for atomistic simulations.
The API provides a standard for exchanging information between atomistic 
simulation
codes (molecular dynamics, molecular statics, lattice dynamics, Monte Carlo, 
etc.)
and interatomic models (potentials or force fields). It also includes a set of 
library
routines for using the API with bindings for:

  FORTRAN 77, Fortran 90/95, Fortran 2003
  C, C++
Atomistic simulation codes that support the KIM API work seamlessly with the 
KIM-compliant
interatomic models (KIM Models) distributed on this website. The interface is 
computationally
efficient and often requires relatively minor changes to existing codes.

Bug#907199: weboob, Gratuitous sexual references

[Ian Jackson]

Package: release.debian.org
Control: block 906119 by -1

(I sent this as a plain email, after asking on #debian-release what
the best representation in the BTS would be, but I didn't get a useful
reply, so I am resending this as a bug report without any useful
tags.  Sorry for any inconvenience.)

Hi.

Dear Release Team, would you please decide whether
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906119
is, in your opinion, RC ?

(Also, as I imagine this is not so easy, can you please let me know
when I should expect to hear back?)

Marc Dequènes (duck) writes ("Re:  Gratuitous sexual references"):
> Control: tag -1 wontfix
> Control: severity -1 wishlist

As I wrote in my initial mail:

 | If you as maintainer disagree with my assessment, then we should
 | refer the dispute about the bug severity to the Release Team, in
 | accordance with usual practice.

So I am doing that now.

I also wrote:

 | For the avoidance of doubt: if the Release Team feel the project's
 | consensus is not sufficiently clear; or that a removal decision by
 | the Release Team would lack legitimacy, I would quite understand.
 | In that case the right next step would be a General Resolution.  If
 | necessary I will propose and/or sponsor a GR to definitively
 | establish Debian's view that this package is unacceptable.

Marc suggested the TC.  I don't think the TC is appropriate for this
question.

But of course the Release Team could delegate this decision to the TC.
Or, the Release Team might want to informally consult the TC, or other
relevant people in Debian such as the DPL, ftpmaster or the
antiharassment team.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#900912: "AtkWrapper not found" error impacting JOSM on Ubuntu/Mint

[Vincent Privat]

Hello,
The bug is closed so there is nothing to expect from OpenJDK. The solution
must come from Debian or a new bug created.
The Java version which introduced the regression is
10.0.2+13-Ubuntu-1ubuntu0.18.04.1
because it contains the fix to move accessibility.properties in the "conf"
folder. The issue did not occur before because the configuration file
enabling ATK wrapper was not found by openjdk. A few hours after this
version was delivered by Ubuntu we started to receive a dozen of bug
reports, until I delivered a JOSM hotfix mitigating the issue.

Patching openjdk with your try/catch proposal and making the ATK wrapper a
Recommends sounds a good idea.

Don't wait for openjdk guys for an answer: they simply don't care anymore
with desktop technologies.

Cheers,
Vincent

Le ven. 24 août 2018 à 11:47, Samuel Thibault  a
écrit :

> Hello,
>
> Vincent Privat, le mer. 22 août 2018 21:01:16 +0200, a ecrit:
> > Samuel, do you know when the root issue will be fixed in Java ATK
> wrapper?
>
> The root issue is in openjdk, not the wrapper. Openjdk has apparently
> removed the way that was used to load the wrapper, without apparently
> making sure that another way was implemented. I have forwarded the issue
> upstream
>
> http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8204862
>
> but apparently they don't have the issue (I guess they don't actually
> manage to enable the wrapper in the configuration file).
>
> > > > Since today we are spammed by bug reports from Linux Mint and Ubuntu
> when
> > > > people try to launch JOSM with the latest Java update
> > > > (10.0.2+13-Ubuntu-1ubuntu0.18.04.1):
>
> Which version is introducing the issue exactly?  AFAIK it's the whole
> openjdk >= 9 which poses the problem.
>
> > Has it ever been considered that this package is made optional rather
> than a
> > strict dependency of openjdk--jre?
>
> The problem is not the dependency, but what openjdk itself is doing. ATM
> it seems to be insisting on loading the wrapper even when it's not
> available.  I guess catching exceptions around
> src/java.desktop/share/classes/java/awt/Toolkit.java's getDefaultToolkit
> call to loadAssistiveTechnologies, to just print the exception but not
> abort, would allow to make the dependency a Recommends only.
>
> Concerning actually managing to load the wrapper, see the backlog of
> #900912. I have commited to the git repo of java-atk-wrapper what is
> said to be needed for making it loadable with openjdk 9 and later, but
> as I said there, we still seem to be lacking in openjdk a path where the
> wrapper can be put for openjdk to find it. And it's been a month without
> anybody answering.
>
> Samuel
>

Bug#907198: convert-from-gbp and comments in d/p/series

[Ian Jackson]

Package: git-debrebase
Version: 6.9

zealot:xen> git-debrebase convert-from-gbp 733450b39b

git-debrebase: error: patch # repeated in debian/patches/series !

This is a very funny way of looking at things.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#907197: thunderbird 60 - although thunderbird-l10n-it is installed, the language is always English

[luca]

Package: thunderbird
Version: 1:60.0-2
Severity: important


despite thunderbird-l10n-it is installed, the language is always English.

system lang is italian.

workaround set intl.locale.requested = it in about:config

Best, Luca.



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 thunderbird depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-5
ii  libcairo-gobject2 1.15.12-1
ii  libcairo2 1.15.12-1
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-4
ii  libgdk-pixbuf2.0-02.36.12-2
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-2
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.6-0 1.6.2-1+b1
ii  libicu60  60.2-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.19-3
ii  libnss3   2:3.38-1
ii  libpango-1.0-01.42.4-1
ii  libpangocairo-1.0-0   1.42.4-1
ii  libpangoft2-1.0-0 1.42.4-1
ii  libsqlite3-0  3.24.0-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-4
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.6-1
ii  libx11-xcb1   2:1.6.6-1
ii  libxcb-shm0   1.13-3
ii  libxcb1   1.13-3
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1+b1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:6.1.0~rc2-2
ii  hunspell-en-us [hunspell-dictionary]  1:2018.04.16-1
ii  hunspell-it [hunspell-dictionary] 1:6.1.0~rc2-2
ii  lightning 1:60.0-2

Versions of packages thunderbird suggests:
ii  apparmor  2.13-8
ii  fonts-lyx 2.3.0-2
ii  libgssapi-krb5-2  1.16-2

-- no debconf information

Bug#907076: Man page for sbuild-debian-developer-setup in wrong binary package

[Ryan Kavanagh]

Control: tags -1 + patch

Please see the attached patch, which you can apply with:

git am 0001-Move-sbuild-debian-developer-setup-man-page-to-corre.patch

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A
From 9be515da8f7fd377c1f6e0e4be103caeea635002 Mon Sep 17 00:00:00 2001
From: Ryan Kavanagh 
Date: Thu, 23 Aug 2018 15:31:12 -0400
Subject: [PATCH] Move sbuild-debian-developer-setup man page to correct
 package

---
 debian/control   |  4 +++-
 debian/sbuild-debian-developer-setup.install |  1 +
 debian/sbuild.install| 13 -
 3 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 6e551790..c00f44cf 100644
--- a/debian/control
+++ b/debian/control
@@ -77,13 +77,15 @@ Description: Tool for building Debian binary packages from Debian sources
 
 Package: sbuild-debian-developer-setup
 Architecture: all
-Depends: sbuild,
+Depends: sbuild (>= 0.77.0-5),
  schroot,
  apt-cacher-ng | apt-cacher,
  cron | cron-daemon,
  ${misc:Depends},
  ${perl:Depends},
  ${shlibs:Depends}
+Replaces: sbuild (<< 0.77.0-5)
+Breaks: sbuild (<< 0.77.0-5)
 Description: Convenience script to set up an sbuild environment for Debian Developers
  Run "sudo sbuild-debian-developer-setup" to add the current user to the sbuild
  group, create an schroot for building packages for Debian unstable, and create
diff --git a/debian/sbuild-debian-developer-setup.install b/debian/sbuild-debian-developer-setup.install
index 6d2a1699..87306892 100644
--- a/debian/sbuild-debian-developer-setup.install
+++ b/debian/sbuild-debian-developer-setup.install
@@ -1,2 +1,3 @@
 usr/bin/sbuild-debian-developer-setup
 etc/sbuild-debian-developer-setup-update-all etc/cron.daily
+usr/share/man/man1/sbuild-debian-developer-setup.1
diff --git a/debian/sbuild.install b/debian/sbuild.install
index f6df2fb1..dd83bec3 100644
--- a/debian/sbuild.install
+++ b/debian/sbuild.install
@@ -15,7 +15,18 @@ debian/tmp/usr/bin/sbuild-createchroot usr/bin
 debian/tmp/usr/sbin/sbuild-adduser usr/sbin
 debian/tmp/usr/sbin/sbuild-destroychroot   usr/sbin
 debian/tmp/usr/share/doc/sbuildusr/share/doc
-debian/tmp/usr/share/man/man1/sbuild*  usr/share/man/man1
+# sbuild*, but not sbuild-debian-developer-setup
+debian/tmp/usr/share/man/man1/sbuild.1 usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-checkpackages.1 usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-abort.1   usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-shell.1   usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-unhold.1  usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-hold.1usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-update.1  usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-clean.1   usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-apt.1 usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-upgrade.1 usr/share/man/man1
+debian/tmp/usr/share/man/man1/sbuild-distupgrade.1 usr/share/man/man1
 debian/tmp/usr/share/man/man5/sbuild*  usr/share/man/man5
 debian/tmp/usr/share/man/man7/sbuild*  usr/share/man/man7
 debian/tmp/usr/share/man/man8/sbuild*  usr/share/man/man8
-- 
2.18.0



signature.asc
Description: PGP signature

Bug#907196: gi.repository.IBus fails to Import

[Helmut Grohne]

Package: gir1.2-ibus-1.0
Version: 1.5.18-1
Severity: serious

In a fresh sid amd64 chroot, I did:

# dpkg --add-architecture i386
# apt-get update
# apt-get install gir1.2-ibus-1.0:i386 python3-gi

I then tried to use ibus:

$ python3
Python 3.6.6+ (default, Aug 20 2018, 16:21:04)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gi.repository.IBus
Traceback (most recent call last):
  File "", line 888, in _find_spec
AttributeError: 'DynamicImporter' object has no attribute 'find_spec'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 127, in find_module
'introspection typelib not found' % namespace)
ImportError: cannot import name IBus, introspection typelib not found
>>>
$

This is not how it is supposed to work. I guess some kind of dependency
is missing here.

Helmut

Bug#907195: RM: gmod -- RoM; obsolete; unmaintained upstream;

[Pirate Praveen]

Source: node-tar-pack
Severity: wishlist
User: debian...@lists.debian.org
Usertags: proposed-removal

node-tar-pack is affected by rc bug #906451 (it is compatible with
version of node-tar in unstable). The only reverse dependency,
node-pre-gyp no longer depends on it. node-pre-gyp which no longer
depends on node-tar-pack already entered testing.



signature.asc
Description: OpenPGP digital signature

Bug#907194: su: yields breakage without "-", not properly documented

[Vincent Lefevre]

Package: util-linux
Version: 2.32.1-0.1
Severity: important

There's the following bug affecting many users:

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

It has been marked as wontfix with the following comment:


The problem is not "gone" in any sense of the word -- which of the
leaked environment variables do you want libpam-systemd to unset in
su's stead? XDG_RUNTIME_DIR? DBUS_SESSION_BUS_ADDRESS?
DESKTOP_SESSION? MAIL? XDG_CONFIG_DIRS? SSH_AUTH_SOCK? GPG_AGENT_INFO?

The fundamental problem is that it's not at all defined what "su"
without -l actually wants to be: Switching to a different user like a
suid program? Then you need the *entire* environment and not change a
few selected variables like $HOME only. Or be like "login"? Then you
need to clean the env like su -l or sudo. Both of the latter have
well-defined behaviour, whereas the current "su" has no conceptual or
consistent (or safe) behaviour at all.

[...]

AFAICS, the behaviour of "su" without -l either needs to be properly
defined and fixed, or it should be completely deprecated, perhaps
making it do the same thing as -l.


The su(1) man page is not helpful:

For backward compatibility, su defaults to not change the  current
directory and to only set the environment variables HOME and SHELL
(plus USER and LOGNAME if the target user is  not  root).   It  is
recommended  to  always  use  the  --login  option (instead of its
shortcut -) to avoid side effects caused by mixing environments.

First, the default behavior should never be discouraged: if there is
something wrong, then it should be fixed. Note also that backward
compatibility has already been broken by systemd: things that were
possible in the past are no longer possible due to environment
variables like the XDG_* ones.

Instead of recommending --login, it should be fixed to be a bit more
like --login, but without the useless drawbacks. I mean that it should
restrict to environment cleaning (in some direction or the other one).
If the direction is to cleanup everything except some environment
variables, then it should keep at least:
  * the user's locale settings,
  * COLUMNS, LINES (in case they are set),
  * LOGNAME,
  * TERM, TERMCAP and TERMINFO (to avoid a broken terminal),
  * probably TZ too.

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

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

Versions of packages util-linux depends on:
ii  fdisk  2.32.1-0.1
ii  libaudit1  1:2.8.3-1+b1
ii  libblkid1  2.32.1-0.1
ii  libc6  2.27-5
ii  libmount1  2.32.1-0.1
ii  libpam0g   1.1.8-3.8
ii  libselinux12.8-1+b1
ii  libsmartcols1  2.32.1-0.1
ii  libsystemd0239-7
ii  libtinfo6  6.1+20180714-1
ii  libudev1   239-7
ii  libuuid1   2.32.1-0.1
ii  login  1:4.5-1.1
ii  zlib1g 1:1.2.11.dfsg-1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.1-2
ii  kbd 2.0.4-4
ii  util-linux-locales  2.32.1-0.1

-- no debconf information

Bug#906538: Possibly still not fixed

[Matthias Klumpp]

Source: appstream
Source-Version: 0.12.2-2

> Am Fr., 24. Aug. 2018 um 16:02 Uhr schrieb Christoph Berg :
> Re: Matthias Klumpp 2018-08-24 
> 
> > Can you verify the issue is fixed when you upgrade the library?
>
> I'm not seeing any error messages anymore with a fully uptodate buster
> system.

Okay, marking as fixed again.

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#907193: Fails to set SNI

[Ryan Kavanagh]

With feeling this time.
From 52edd12db272e511b13db1092c11d86e9f735e51 Mon Sep 17 00:00:00 2001
From: Ryan Kavanagh 
Date: Fri, 24 Aug 2018 11:02:36 -0400
Subject: [PATCH] Set SNI to server name (Closes: #907193)

---
 debian/patches/series   |  1 +
 debian/patches/set_sni.diff | 20 
 2 files changed, 21 insertions(+)
 create mode 100644 debian/patches/set_sni.diff

diff --git a/debian/patches/series b/debian/patches/series
index 3d95e1a..bc4c443 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 fix-makefile.diff
 #ubuntu-switch-to-SSLv23_client_method-and-use-CTX-options-to-select-protocol.patch
+set_sni.diff
diff --git a/debian/patches/set_sni.diff b/debian/patches/set_sni.diff
new file mode 100644
index 000..dd6f2d8
--- /dev/null
+++ b/debian/patches/set_sni.diff
@@ -0,0 +1,20 @@
+Description: set SNI
+Author: Ryan Kavanagh 
+Origin: Debian
+Bug-Debian: https://bugs.debian.org/907193
+Forwarded: https://github.com/lefcha/imapfilter/pull/185
+Last-Update: 2018-08-24
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: imapfilter/src/socket.c
+===
+--- imapfilter.orig/src/socket.c	2018-08-23 17:38:49.193720987 -0400
 imapfilter/src/socket.c	2018-08-23 17:44:07.043509188 -0400
+@@ -141,6 +141,7 @@
+ 	if (!(ssn->sslconn = SSL_new(ctx)))
+ 		goto fail;
+ 
++	SSL_set_tlsext_host_name(ssn->sslconn, ssn->server);
+ 	SSL_set_fd(ssn->sslconn, ssn->socket);
+ 
+ 	for (;;) {
-- 
2.18.0



signature.asc
Description: PGP signature

Bug#905396: Bug fix needs 2.5

[Xavier]

Hi all,

I didn't find any way to fix CVE-2018-12482 and CVE-2018-12483 without
upgrading ocsinventory-server to 2.5

CVE-2018-14473 will be fixed soon by upstream in a >2.5 version, but it
can't be packaged without libphp-phpmailer update, at least to 6.x.

Cheers,
Xavier



signature.asc
Description: OpenPGP digital signature

Bug#907193: Fails to set SNI

[Ryan Kavanagh]

Control: tags -1 + patch

Please see the attached patch, which you can apply with:

git am 0001-Set-SNI-to-server-name-Closes-907193.patch

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#907193: Fails to set SNI

[Ryan Kavanagh]

Package: imapfilter
Version: 1:2.6.11-1
Severity: normal
Tags: upstream

imapfilter fails to set SNI. This means that imapfilter no longer works
with Gmail's IMAP servers. In particular, Gmail sends a self-signed
certificate, causing imapfilter to preset the following:

Server certificate subject: /OU=No SNI provided; please fix your 
client./CN=invalid2.invalid
Server certificate issuer: /OU=No SNI provided; please fix your 
client./CN=invalid2.invalid
Server certificate serial: 
Server key fingerprint: 90:4A:C8:D5:44:5A:D0:6A:8A:10:FF:CD:8B:11:BE:16
(R)eject, accept (t)emporarily or accept (p)ermanently?

See the following thread on openssl-project for details:

https://mta.openssl.org/pipermail/openssl-project/2018-April/000623.html

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

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

Versions of packages imapfilter depends on:
ii  libc62.27-5
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libpcre3 2:8.39-11
ii  libssl1.11.1.1~~pre9-1

imapfilter recommends no packages.

imapfilter suggests no packages.

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#907192: pre-RFS: tensorflow/1.10.0+dfsg-A1 [ITP] -- debian archve += 1 million lines of code

[Lumin]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: tags -1 +moreinfo
Control: blocks -1 by 906646 894411
Control: blocks 804612 by -1

Hi Mentors and d-Science Team,

**Many thanks** to Aron Xu for his sponsorship with a 512GB-RAM builder.
Without this machine I'll never be able to reach this step, so that
postpone this ITP forever.

key points of this mail in case if you don't want to read the whole mail


 1. able to produce libtensorflow.so now, in a Policy-friendly manner.
 2. any help will be appreciated, especially for CMake.


Details
---

This not a real RFS, but sort of weak request for review/help.
I'm not proficient in CMake so I'm not sure whether I'm doing
the correct choice all the time. Anyway, The good news is that
I'm already able to build libtensorflow.so for Debian experimental,
on both amd64 and ppc64el architectures.

At the time of writing, debomatic-amd64 has nearly finished the build
but failed (maybe not enough memory):
http://debomatic-amd64.debian.net/distribution#experimental/tensorflow/1.10.0+dfsg-A1/buildlog
Note, this buildlog is as big as 107MB.


Here is a list of remaining TODOs for stage A:
---
(The list is copied from README.Debian at
 https://salsa.debian.org/science-team/tensorflow ,
 please lookup README.Debian for the full version)


- [x] prevent the build system from downloading anything.
- [x] deal with all the C/C++ lib dependencies.
- [x] produce libtensorflow.so.1.10 and install it into .deb package.
- [x] ambiguous FFT2D license.

- [ ] build tests files (googletest) and run the tests.
- [ ] make sure nothing from contrib is built. they are not officially 
supported.
- [ ] remove useless parts from cmake build.
- [ ] misc improvements to cmake build. (at least make it easier to read)
- [ ] is the resulting libtensorflow.so.1.10 correct and working?
  - [ ] write autopkgtest with some mini C/C++ programs.
  - [ ] working on amd64?
  - [ ] working on ppc64el?
- [ ] make sure libtensorflow/amd64 is linked against libmkldnn
- [ ] sort out this confusing lintian E
  source-is-missing tensorflow/compiler/aot/codegen_test_o.golden
- [ ] remaining lintian warnings and errors.
- [ ] traverse the 16000+ files in the source tree and complete d/copyright.
  umm.
- [ ] Can't the blob be even smaller?
  -rwxr-xr-x 1 debian debian 3.6G Aug 24 13:53 libtensorflow.so.1.10.0 
(unstripped)
  -rwxr-xr-x 1 debian debian 104M Aug 24 14:00 libtensorflow.so.1.10.0 
(stripped)
- [ ] 16GB RAM + 16GB swap is not enough to avoid triggering OOM killer?
- [ ] get rid of static linking written for stupid windows
  /usr/bin/ld: error: benchmark_model(.debug_info) is too large (0x35a9f359 
bytes)
  /usr/bin/ld: error: benchmark_model(.debug_str) is too large (0x6a545d15 
bytes)
  /usr/bin/ld: error: benchmark_model(.debug_loc) is too large (0x1f5b1950 
bytes)
  make[3]: Leaving directory 
'/<>/tensorflow-1.10.0+dfsg/obj-x86_64-linux-gnu'
  [ 98%] Built target benchmark_model
  /usr/bin/ld: error: compare_graphs(.debug_info) is too large (0x366f36be 
bytes)
  /usr/bin/ld: error: compare_graphs(.debug_str) is too large (0x6a64010e 
bytes)
  /usr/bin/ld: error: compare_graphs(.debug_loc) is too large (0x1fd19fe0 
bytes)
- [ ] how to prevent "make install" from building everything again?

- [ ] upload to experimental.


---
Changes:

tensorflow (1.10.0+dfsg-A1) UNRELEASED; urgency=medium

  * Initial release. (Closes: #804612)
  * Stage A (with Debian revision "A*") indicates that the source
package only produce C and C++ library and development files.

Bug#823293: fusiondirectory-insert-schema fails to add schema to ldap with cn=config configuration

[Mike Gabriel]

Control: close -1

Hi,

this is the maintainer of FusionDirectory in Debian (which is, I must 
admit, a more low prio package of mine...). Sorry for the late reply to 
your question.


On Tue, 03 May 2016 09:30:17 +0300 Ioan Eugen Stan  wrote:
> Package: fusiondirectory
> Version: 1.0.8.2-5+deb8u1
> Severity: important
>
> Dear Maintainer,
>
> I've installed slapd and fusiondirectory on my Debian Jessie server. 
Dusing

> fusiondirectory web setup it complained about missing schema so I ran the
> fusiondirectory-insert-schema to install the schemas in my LDAP server.
>
> 
> $ sudo fusiondirectory-insert-schema
> ! This tool is only intended to be with with a cn=config backend, 
cn=config
> could not be found in the LDAP at 
/usr/sbin/fusiondirectory-insert-schema line

> 242.
> 
>
> I expected the schemas to be imported into LDAP and be available. It 
seems the

> schemas provided by the package are not migrated to LDIF format.
>
> I'm quite new with LDAP so please let me know if and how I can 
provide more

> information.
>
> All versions used are from Debian Jessie + Backports. 
fusiondirectory-setup

> also fails but I will submit another bug.
> I'm reporting this bug from another machine with Debian Stretch.

You need to specify exactly what schema (file) to insert on the command 
line. See the man page of the command


```
  $ man fusiondirectory-insert-schema
```

If you have further questions, please send further questions to 
packa...@lists.fusiondirectory.org or contact the upstream maintainers 
on channel #fusiondirectory on Freenode.


I will close this bug report as your issue is more a 
how-to-use-FD-tools-correctly issue.


Regards,
Mike

Bug#906576: ledgersmb: [INTL:de] updated German debconf translation

[Robert James Clay]

 On 18 Aug 2018 at 13:59, Helge Kreutzmann  wrote:  

> Please find the updated German debconf translation for ledgersmb attached. 


> Please place this file in debian/po/ as de.po for your next upload.  

   

This is to advise that I imported the new version of the de.po file into the
package git repository[1] on 19 August and the update will be included with
the next package release.  

Thanks!  

   

   

   

Robert James Clay, j...@rocasa.us  

[1] https://github.com/ledgersmb/pkg-ledgersmb  

 

Bug#907190: Manpage(s) should have information about inspecting the history

[Ian Jackson]

Package: git-debrebase
Version: 6.9

During a conversation on pkg-xen-devel, it became evident that there
is too little advice on how to examine things when using
git-debrebase.  There's a lot of advice on how to change things, but
little on how to see what they're currently like.  Without this advice
the whole workflow can be a bit disorienting.

I wrote some text in an email to pkg-xen-devel (see below).  I think
something like this should be in some manpage.

Should this be in dgit-maint-debrebase(7) ?  Or git-debrebase(5) ?
Do we need a git-debrebase(7) too ?

Ian.


The normal git commands for viewing subsets of the history can be
used.  Let me make some suggestions:

  History of package in Debian (disregards upstream history)
  gitk --first-parent
  In a laundered branch, the delta queue is at the top.

  History of the packaging (excluding the delta queue)
  gitk :/debian :!/debian/patches

  Just the delta queue (ie, Debian's changes to upstream):
  gitk --first-parent -- :/ :!/debian

  Full history including old versions of the delta queue:
  gitk --date-order
  The "Declare fast forward" commits you see have an older
  history (usually, an older delta queue) as one parent,
  and a newer history as the other.  --date-order makes
  gitk show the delta queues in order.

  Show complete diff since the last upload:
  git diff dgit/dgit/sid..HEAD -- :/ :!/debian/patches
  (Includes changes to upstream files.)

  Show interdiff of patches, if you really want that:
  git debrebase make-patches
  git diff dgit/dgit/sid..HEAD -- debian/patches

  Also of course there is
  git debrebase status

I think some of this information should be in the manpages.
I'll file a bug about that.


-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.