Bug#908363: opensc FTBFS on 32bit

[Adrian Bunk]

Source: opensc
Version: 0.19.0~rc1-1
Severity: serious
Tags: ftbfs

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

...
card-gids.c: In function 'gids_delete_container_num':
card-gids.c:1480:42: error: '%02X' directive output may be truncated writing 
between 2 and 7 bytes into a region of size 4 [-Werror=format-truncation=]
  snprintf(ch_tmp, sizeof(ch_tmp), "3FFFB0%02X",containernum + 
GIDS_FIRST_KEY_IDENTIFIER);
  ^~~~
card-gids.c:1480:35: note: directive argument in the range [129, 49941608]
  snprintf(ch_tmp, sizeof(ch_tmp), "3FFFB0%02X",containernum + 
GIDS_FIRST_KEY_IDENTIFIER);
   ^~~~
...

Bug#907896: tracker-miners FTBFS in autopkgtest with latest glib2.0

[Tim]

This test failure seems to be specific to the schroot environment. I
cannot reproduce outside of a schroot.

Glib mime-type detection is failing, as its unable to locate/open the
test file, when calling get_content_type().

Bug#908362: VMs fail to start with "Kernel does not provide mount namespace: Permission denied"

[Michael Biebl]

Package: libvirt-daemon-system
Version: 4.6.0-2
Severity: grave

Hi,

with the kernel update to 4.18, I'm no longer able to start any VMs via
libvirt/virt-manager. I get the following error:

Error starting domain: internal error: child reported: Kernel does not provide 
mount namespace: Permission denied

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
self._backend.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1080, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: child reported: Kernel does not provide mount 
namespace: Permission denied

If I disable AppArmor, I can successfully start the VMs.
Since AppArmor is enabled by default, I think the RC severity is
justified.
I've CCed the AppArmor maintainers, as I'm not sure if this is a bug in
this package or apparmor. Please reassign if necessary.

Regards,
Michael


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

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

Versions of packages libvirt-daemon-system depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.69
ii  firewalld  0.6.1-2
ii  gettext-base   0.19.8.1-7
ii  iptables   1.6.2-1.1
ii  libacl12.2.52-3+b1
ii  libapparmor1   2.13-8
ii  libaudit1  1:2.8.4-2
ii  libblkid1  2.32.1-0.1
ii  libc6  2.27-6
ii  libcap-ng0 0.7.9-1
ii  libdbus-1-31.12.10-1
ii  libdevmapper1.02.1 2:1.02.145-4.1
ii  libgnutls303.5.19-1
ii  libnl-3-2003.4.0-1
ii  libnl-route-3-200  3.4.0-1
ii  libnuma1   2.0.12-1
ii  libselinux12.8-1+b1
ii  libvirt-clients4.6.0-2
ii  libvirt-daemon 4.6.0-2
ii  libvirt0   4.6.0-2
ii  libxml22.9.4+dfsg1-7+b1
ii  libyajl2   2.1.0-2+b3
ii  logrotate  3.14.0-4
ii  lsb-base   9.20170808
ii  policykit-10.105-21

Versions of packages libvirt-daemon-system recommends:
ii  bridge-utils 1.5-16
ii  dmidecode3.1-2
ii  dnsmasq-base [dnsmasq-base]  2.79-1
ii  ebtables 2.0.10.4-5
ii  iproute2 4.18.0-2
ii  parted   3.2-21+b1

Versions of packages libvirt-daemon-system suggests:
ii  apparmor2.13-8
pn  auditd  
ii  nfs-common  1:1.3.4-2.2
pn  open-iscsi  
pn  pm-utils
pn  radvd   
ii  systemd 239-8
pn  systemtap   
pn  zfsutils

-- Configuration Files:
/etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-arp.xml'
/etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-dhcp-server.xml'
/etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-dhcp.xml'
/etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
/etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-ipv4.xml'
/etc/libvirt/nwfilter/clean-traffic-gateway.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml'
/etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/clean-traffic.xml'
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-arp-spoofing.xml'
/etc/libvirt/nwfilter/no-ip-multicast.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-ip-multicast.xml'
/etc/libvirt/nwfilter/no-ip-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-mac-broadcast.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-mac-broadcast.xml'
/etc/libvirt/nwfilter/no-mac-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-mac-spoofing.xml'

Bug#908360: emacs-non-dfsg: No binary packages produced

[David Bremner]

Source: emacs-non-dfsg
Version: 25.2+1-3
Severity: grave
Justification: renders package unusable

Hi Rob;

To quote lintian:

   Please either perform a regular binary upload or (after checking the
   license) add XS-Autobuild: yes into the header part of debian/control
   and get the package added to the "autobuild" whitelist.
   
   Refer to Debian Developer's Reference section 5.10.5 (Marking non-free
   packages as auto-buildable) for details.

Let me know if there's something I can do to help.

d




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

Bug#907403: marked as done (opam-installer: missing Replaces: opam-docs (<< 2.0.0))

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 23:49:47 +
with message-id 
and subject line Bug#907403: fixed in opam 2.0.0-3
has caused the Debian Bug report #907403,
regarding opam-installer: missing Replaces: opam-docs (<< 2.0.0)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opam-installer
Version: 2.0.0-1
Severity: serious

Unpacking opam-installer (2.0.0-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-KfKgI6/4-opam-installer_2.0.0-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/opam-installer.1.gz', which is also 
in package opam-docs 1.2.2-7
--- End Message ---
--- Begin Message ---
Source: opam
Source-Version: 2.0.0-3

We believe that the bug you reported is fixed in the latest version of
opam, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Braud-Santoni  (supplier of updated opam 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 08 Sep 2018 02:04:24 +0200
Source: opam
Binary: opam opam-docs opam-installer
Architecture: source amd64 all
Version: 2.0.0-3
Distribution: unstable
Urgency: high
Maintainer: Debian OCaml Maintainers 
Changed-By: Nicolas Braud-Santoni 
Description:
 opam   - package manager for OCaml
 opam-docs  - package manager for OCaml (documentation)
 opam-installer - Utility handling (un)installation of Opam .install files
Closes: 907403
Changes:
 opam (2.0.0-3) unstable; urgency=high
 .
   * debian/control
 + Fix typo in Breaks+Replaces for opam-installer (Closes: #907403)
 + Fix typo in the Description of opam-installer
Checksums-Sha1:
 b0a590fafd0bad7a5e46c8ae6184b865a356966a 2565 opam_2.0.0-3.dsc
 f6807a38bd9bbeff4c100370cafbdf388df0d3ac 6848 opam_2.0.0-3.debian.tar.xz
 9eaf81e45dacb3f93c2aa4644a7758c262197944 450496 opam-dbgsym_2.0.0-3_amd64.deb
 ddcb1171a7e32cd192e4ce164d6b05436693e2d0 371008 opam-docs_2.0.0-3_all.deb
 37811232a78ea4fbac8140dac6f879c939926d7e 228000 
opam-installer-dbgsym_2.0.0-3_amd64.deb
 4426ace47c75cc90d11c084c24c4ef4d39da47c2 864176 
opam-installer_2.0.0-3_amd64.deb
 3b4f65dccd6a6738fbfd0f66089fef06c5b31849 11561 opam_2.0.0-3_amd64.buildinfo
 13f127ac38b6375f0a805cf1b4d06c8caaeacd4b 1632020 opam_2.0.0-3_amd64.deb
Checksums-Sha256:
 28f384ff672d2bc891167dc3e5f0cfcd393cadbd91317ef8c759480d6be86e26 2565 
opam_2.0.0-3.dsc
 569c84af3792bb3c0532bbfd2cffa4bff243db0f45d838680dc013b10c39279b 6848 
opam_2.0.0-3.debian.tar.xz
 881a10ee20ff951a76df2ce911136092283319b53ef00374bcec846c7d8d4ea4 450496 
opam-dbgsym_2.0.0-3_amd64.deb
 199d1a490f5db93fcaa6891ed321311320c85a1b0277f680bfc45ba4fe793d18 371008 
opam-docs_2.0.0-3_all.deb
 7a5b1782e3fe4c4cc0db1d7172f758492c0451efbf28b27e6fbb6995c3291a5e 228000 
opam-installer-dbgsym_2.0.0-3_amd64.deb
 bf37e10e854659eba096e64c280d98a14c859df3164263731bdd4dac16648f1a 864176 
opam-installer_2.0.0-3_amd64.deb
 befc245208f167d3fdab6489996e5c064ecf6f94af659529885a731d19c33d5d 11561 
opam_2.0.0-3_amd64.buildinfo
 cd9a5a194a1cadfe392c48eb28aebd042fcd7c86ef6e748af8b4daaf33af27cc 1632020 
opam_2.0.0-3_amd64.deb
Files:
 e4713e48c0aa2aa07055691bb1e9c2ab 2565 ocaml optional opam_2.0.0-3.dsc
 b73e8d9da13d18ec968be84cf4129fcf 6848 ocaml optional opam_2.0.0-3.debian.tar.xz
 7ef8604f31331dbf21a61a13d1eeb9e4 450496 debug optional 
opam-dbgsym_2.0.0-3_amd64.deb
 0a03a334c924726689c8b087324abb48 371008 doc optional opam-docs_2.0.0-3_all.deb
 0df21e1e2c09702e87f63733f0cf6727 228000 debug optional 
opam-installer-dbgsym_2.0.0-3_amd64.deb
 4a27d0fa61e7582b7210e620fc22c4bf 864176 ocaml optional 
opam-installer_2.0.0-3_amd64.deb
 fd0b54e95296ea8506bdf04e67200cd8 11561 ocaml optional 
opam_2.0.0-3_amd64.buildinfo
 8567057eefa9786dff272dee34f9d914 1632020 ocaml optional opam_2.0.0-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE/IeFmw45V03XKU7GPfRgADmhQMQFAluUXFMRHG1laGRpQGRl
Ymlhbi5vcmcACgkQPfRgADmhQMRAuQ//U4jNvSHumP4tc/Io6dGPQS8GxVcjLGK1
+Sqj0yLXuj5Mwd/KkxRZOSJztm2+2hfXqjSkeuFSV2eEdFUKVBL8Ksby+NgYH+eJ

Bug#907931: marked as done (rygel FTBFS with vala 0.42.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 23:19:19 +
with message-id 
and subject line Bug#907931: fixed in rygel 0.36.2-1
has caused the Debian Bug report #907931,
regarding rygel FTBFS with vala 0.42.0-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rygel
Version: 0.36.1-1
Severity: serious
Tags: ftbfs

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

...
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac -H rygel-core.h -C 
--library=rygel-core-2.6 --gir=Rygel-2.6.gir 
--vapidir=/build/1st/rygel-0.36.1/src/librygel-core --pkg gupnp-1.0 --pkg 
gee-0.8 --pkg gssdp-1.0 --pkg gio-2.0 --pkg gmodule-2.0 --pkg posix 
--vapidir=/build/1st/rygel-0.36.1/src/librygel-core --pkg rygel-build-config
--enable-deprecated --target-glib=2.40  -C rygel-connection-manager.vala 
rygel-basic-management.vala rygel-basic-management-test.vala 
rygel-basic-management-test-ping.vala rygel-basic-management-test-nslookup.vala 
rygel-basic-management-test-traceroute.vala rygel-description-file.vala 
rygel-dlna-profile.vala rygel-energy-management.vala rygel-root-device.vala 
rygel-root-device-factory.vala rygel-dbus-interface.vala rygel-log-handler.vala 
rygel-meta-config.vala rygel-plugin-loader.vala 
rygel-recursive-module-loader.vala rygel-plugin.vala rygel-resource-info.vala 
rygel-media-device.vala rygel-configuration.vala rygel-base-configuration.vala 
rygel-cmdline-config.vala rygel-environment-config.vala rygel-user-config.vala 
rygel-state-machine.vala rygel-v1-hacks.vala rygel-icon-info.vala 
rygel-xml-utils.vala rygel-plugin-information.vala
rygel-basic-management-test-ping.vala:71.5-71.28: error: Property 
`Rygel.BasicManagementTestPing.repeat_count' with custom `get' accessor and/or 
`set' mutator cannot have `default' value
public uint repeat_count {

rygel-basic-management-test-ping.vala:119.5-119.35: error: Property 
`Rygel.BasicManagementTestPing.interval_time_out' with custom `get' accessor 
and/or `set' mutator cannot have `default' value
public uint32 interval_time_out {
^^^
rygel-basic-management-test-ping.vala:87.5-87.31: error: Property 
`Rygel.BasicManagementTestPing.data_block_size' with custom `get' accessor 
and/or `set' mutator cannot have `default' value
public uint data_block_size {
^^^
rygel-basic-management-test-ping.vala:103.5-103.20: error: Property 
`Rygel.BasicManagementTestPing.dscp' with custom `get' accessor and/or `set' 
mutator cannot have `default' value
public uint dscp {

rygel-basic-management-test-nslookup.vala:158.5-158.33: error: Property 
`Rygel.BasicManagementTestNSLookup.interval_time_out' with custom `get' 
accessor and/or `set' mutator cannot have `default' value
public uint interval_time_out {
^
rygel-basic-management-test-nslookup.vala:171.5-171.27: error: Property 
`Rygel.BasicManagementTestNSLookup.repetitions' with custom `get' accessor 
and/or `set' mutator cannot have `default' value
public uint repetitions {
^^^
rygel-basic-management-test-traceroute.vala:106.5-106.29: error: Property 
`Rygel.BasicManagementTestTraceroute.max_hop_count' with custom `get' accessor 
and/or `set' mutator cannot have `default' value
public uint max_hop_count {
^
rygel-basic-management-test-traceroute.vala:74.5-74.31: error: Property 
`Rygel.BasicManagementTestTraceroute.wait_time_out' with custom `get' accessor 
and/or `set' mutator cannot have `default' value
public uint32 wait_time_out {
^^^
rygel-basic-management-test-traceroute.vala:122.5-122.20: error: Property 
`Rygel.BasicManagementTestTraceroute.dscp' with custom `get' accessor and/or 
`set' mutator cannot have `default' value
public uint dscp {

rygel-basic-management-test-traceroute.vala:90.5-90.31: error: Property 
`Rygel.BasicManagementTestTraceroute.data_block_size' with custom `get' 
accessor and/or `set' mutator cannot have `default' value
public uint data_block_size {
^^^
rygel-dbus-interface.vala:29.5-29.33: warning: DBus methods are recommended to 
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract void shutdown () throws IOError;
^
Compilation failed: 10 error(s), 1 warning(s)
make[4]: 

Bug#907988: rubber must specify the encoding when opening files

[Hilmar Preuße]

On 04.09.2018 22:49, Adrian Bunk wrote:

Hi Adrian,

> Package: rubber
> Version: 1.5-1
> Severity: serious
> Control: affects -1 src:why3
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/why3.html
> 
I've uploaded 1.5-2 here [1]. Do you have the chance to test if it
solves the problem?

Thanks!
  Hilmar

[1] https://freeshell.de/~hille42/rubber/
-- 
sigfault
#206401 http://counter.li.org

Bug#904139: marked as done (stockfish FTBFS on armel, mips, mipsel, m68k, powerpc, powerpcspe, sh4: undefined reference to `__atomic_store_8')

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 20:36:16 +
with message-id 
and subject line Bug#904139: fixed in stockfish 9-2
has caused the Debian Bug report #904139,
regarding stockfish FTBFS on armel, mips, mipsel, m68k, powerpc, powerpcspe, 
sh4: undefined reference to `__atomic_store_8'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
904139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stockfish
Version: 9-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

stockfish fails to build from source on armel, mips, mipsel, m68k,
powerpc, powerpcspe and sh4. A build log from mips ends with:

| g++ -o stockfish benchmark.o bitbase.o bitboard.o endgame.o evaluate.o main.o 
material.o misc.o movegen.o movepick.o pawns.o position.o psqt.o search.o 
thread.o timeman.o tt.o uci.o uc
| ioption.o syzygy/tbprobe.o -Wl,-z,relro  -Wl,--no-as-needed -lpthread -g -O2 
-fdebug-prefix-map=/home/helmutg/stockfish-9=. -fstack-protector-strong 
-Wformat -Werror=format-security -W
| all -Wcast-qual -fno-exceptions -std=c++11  -pedantic -Wextra -Wshadow 
-DNDEBUG -O3 -DNO_PREFETCH -flto  -Wl,--no-as-needed -lpthread -g -O2 
-fdebug-prefix-map=/home/helmutg/stockfish-
| 9=. -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wcast-qual -fno-exceptions -std=c++11  -pedantic -Wextra -Wshadow -DNDEBUG -O3 
-DNO_PREFETCH -flto -Wall -Wcast-qua
| l -fno-exceptions -std=c++11  -pedantic -Wextra -Wshadow -DNDEBUG -O3 
-DNO_PREFETCH -flto -lgcov -Wl,--no-as-needed -lpthread -g -O2 
-fdebug-prefix-map=/home/helmutg/stockfish-9=. -fst
| ack-protector-strong -Wformat -Werror=format-security -Wall -Wcast-qual 
-fno-exceptions -std=c++11  -pedantic -Wextra -Wshadow -DNDEBUG -O3 
-DNO_PREFETCH -flto -Wall -Wcast-qual -fno-e
| xceptions -std=c++11  -pedantic -Wextra -Wshadow -DNDEBUG -O3 -DNO_PREFETCH 
-flto -Wall -Wcast-qual -fno-exceptions -std=c++11 -fprofile-generate -pedantic 
-Wextra -Wshadow -DNDEBUG -O
| 3 -DNO_PREFETCH -flto
| /usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 127
| /tmp/ccNba2xu.ltrans0.ltrans.o: in function `TimeManagement::elapsed() const 
[clone .isra.66] [clone .constprop.25]':
| /usr/include/c++/8/bits/basic_string.tcc:(.text+0xcd0c): undefined reference 
to `__atomic_load_8'
| /usr/bin/ld: /usr/include/c++/8/bits/basic_string.tcc:(.text+0xcd20): 
undefined reference to `__atomic_load_8'
| /usr/bin/ld: /tmp/ccNba2xu.ltrans0.ltrans.o: in function `Value (anonymous 
namespace)::search<((anonymous namespace)::NodeType)1>(Position&, 
Search::Stack*, Value, Value, Depth, bool, bool) [clone .constprop.7]':
| /usr/include/c++/8/bits/basic_string.tcc:(.text+0x13ad0): undefined reference 
to `__atomic_fetch_add_8'
| /usr/bin/ld: /usr/include/c++/8/bits/basic_string.tcc:(.text+0x13ae4): 
undefined reference to `__atomic_fetch_add_8'
| /usr/bin/ld: /usr/bin/ld: DWARF error: offset (262144) greater than or equal 
to .debug_str size (29238)
| /usr/bin/ld: DWARF error: mangled line number section (bad file number)
| /usr/bin/ld: DWARF error: could not find abbrev number 8986
| /tmp/ccNba2xu.ltrans3.ltrans.o: in function 
`ThreadPool::start_thinking(Position&, std::unique_ptr >, std::default_delete > > >&, Search::LimitsType const&, bool)':
| tt.cpp:(.text+0xb500): undefined reference to `__atomic_store_8'
| /usr/bin/ld: tt.cpp:(.text+0xb51c): undefined reference to `__atomic_store_8'
| /usr/bin/ld: tt.cpp:(.text+0xb4dc): undefined reference to `__atomic_store_8'
| /usr/bin/ld: tt.cpp:(.text+0xb518): undefined reference to `__atomic_store_8'
| /usr/bin/ld: /tmp/ccNba2xu.ltrans3.ltrans.o: in function `UCI::loop(int, 
char**)':
| tt.cpp:(.text+0xff1c): undefined reference to `__atomic_load_8'
| /usr/bin/ld: tt.cpp:(.text+0xff30): undefined reference to `__atomic_load_8'
| /usr/bin/ld: /usr/bin/ld: DWARF error: invalid abstract instance DIE ref
| /tmp/ccNba2xu.ltrans4.ltrans.o: in function `Value (anonymous 
namespace)::search<((anonymous namespace)::NodeType)0>(Position&, 
Search::Stack*, Value, Value, Depth, bool, bool) [clone .lto_priv.214]':
| search.cpp:(.text+0xf2b4): undefined reference to `__atomic_fetch_add_8'
| /usr/bin/ld: search.cpp:(.text+0xf2c8): undefined reference to 
`__atomic_fetch_add_8'
| /usr/bin/ld: /usr/bin/ld: DWARF error: invalid abstract instance DIE ref
| /tmp/ccNba2xu.ltrans5.ltrans.o: in function `UCI::pv[abi:cxx11](Position 
const&, Depth, Value, Value)':
| position.cpp:(.text+0x4b00): undefined reference to `__atomic_load_8'
| /usr/bin/ld: 

Bug#875202: [taurus] Future Qt4 removal from Buster

[Gudjon I. Gudjonsson]

Hi

There is a new package in Debian 
https://tracker.debian.org/pkg/pyqt-qwt

that builds on the Qt5 version of Qwt6. 
It should not be difficult to upgrade the package from
PyQwt5 to PyQt-Qwt.

Regards
Gudjon

Bug#908210: marked as done (arc-theme FTBFS with gtk+3.0 3.24)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 20:34:13 +
with message-id 
and subject line Bug#908210: fixed in arc-theme 20180715-1
has caused the Debian Bug report #908210,
regarding arc-theme FTBFS with gtk+3.0 3.24
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
908210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arc-theme
Version: 20180114-1
Severity: serious
Tags: ftbfs

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

...
checking pkg-config is at least version 0.9.0... yes
configure: error: Invalid GNOME version: 3.24


In a related note, when the package is that dependeny
on the specific GTK+ version used it might also require
stricter runtime dependencies.
--- End Message ---
--- Begin Message ---
Source: arc-theme
Source-Version: 20180715-1

We believe that the bug you reported is fixed in the latest version of
arc-theme, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Mohammed  (supplier of updated arc-theme package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 7 Sep 2018 12:16:50 +0100
Source: arc-theme
Binary: arc-theme
Architecture: source
Version: 20180715-1
Distribution: unstable
Urgency: medium
Maintainer: David Mohammed 
Changed-By: David Mohammed 
Description:
 arc-theme  - Flat theme with transparent elements
Closes: 908210
Changes:
 arc-theme (20180715-1) unstable; urgency=medium
 .
   * New upstream version 20180715
   * patch 0001-Prepare-for-GNOME-3.30-and-Gtk-3.24-99-100.patch
 - build for GTK+3.24 (Closes: #908210)
   * Packaging Changes
 - control: Bump Standards-Version; rules made more verbose
 - control: Revise build-dependencies to reflect upstream changes
 - control: Add GTK+ runtime dependency to reflect addition of
   3.24 patch addition
 - control: Update runtime dependency to reflect new updated GNOME
   package name
Checksums-Sha1:
 2d3cb7caa9e97715cf01d859b7a48e96452c6443 2212 arc-theme_20180715-1.dsc
 8941fa7a449e31be8e94995a3fd5348071012474 221476 arc-theme_20180715.orig.tar.xz
 17732acdad151da62ac78d5cb0961855cfb5eccd 833 arc-theme_20180715.orig.tar.xz.asc
 cf0d8fb92bf6d3c47bf49842bb71ba987846d31d 29876 
arc-theme_20180715-1.debian.tar.xz
 30629caba50892f4ce32cf73433039c6e9875393 9173 
arc-theme_20180715-1_source.buildinfo
Checksums-Sha256:
 f9e6d1b434b5b509448a6c029dc5d4792df2b0e7e71fa858bbcf42d54b5317aa 2212 
arc-theme_20180715-1.dsc
 a8119f6afa91628a73d8d6d68a953522b8ebe1efee303f9bc15d1ba4b5108f35 221476 
arc-theme_20180715.orig.tar.xz
 859527473d168299ffed8a56412f3623fa3f9f40d2503ea50db8c872dfded3d2 833 
arc-theme_20180715.orig.tar.xz.asc
 0558bff31b41682a35a6c2244ca6a21f47ab955a63c9ba3aa9929a4af061c4e9 29876 
arc-theme_20180715-1.debian.tar.xz
 5e8269a7037be5a8ee954b6ead9df046c5d0078d17b0b91c6bec43f0818848af 9173 
arc-theme_20180715-1_source.buildinfo
Files:
 8a1df9a18dce0b724dfb683a18e6b8ef 2212 misc optional arc-theme_20180715-1.dsc
 aa117d52425dc1f9558bfa102f5c1404 221476 misc optional 
arc-theme_20180715.orig.tar.xz
 88d8602179d437a993b76acbe7806893 833 misc optional 
arc-theme_20180715.orig.tar.xz.asc
 d1cd38e631461dbd2676120a7cdc8464 29876 misc optional 
arc-theme_20180715-1.debian.tar.xz
 46594ff2c02dbfe1f7ab76d82c79b706 9173 misc optional 
arc-theme_20180715-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAluULmEACgkQweDZLphv
fH5zSxAA8AF89jI+/ooWAu3yBEns1aQqn4+HWMTgGkr/GvK/1AfM8QHHwjHwJIVJ
VO9UPOghM3KlkYljHGcJ+cFjvqcqI8CjCj4oLWXmH2398e9GwWArxs4KyrIq1u29
pabJOUZGhHTNjY9Jyk/enXxGVH2nTLL+XJmdt915RJbnS10uYQAhKxDe/RSOB5HL
hoBxK6SZT1K947DgrjUqwPGxpX353scxzgMhREtOKvUJEooFrcjzQcpBleAu14P7
wt7BBIW/qbsuHfnp7rApKwn5IeiMi3hMqRS9ghMqs5LDjaCS4Iv85QFL2bSjGQBI
OxlI32ZIOOyp07wVDB2axjR4PBHdwVd7HwlivEu4xwEtLqPYEzuek0/SRCOVhYmZ
ZANdqHmjpGyjELqpm9heTc8gHSbD9sGhZYCWXp9YH5kT7zO0EYUB/3mp337f5CTy
f5BkGgsOrsYHu595TSGS13KSiJp7P8EZQ7X+zcMIAljc+Q2S+IwycsD0M5cVP7Md
faKSGW7SfSp8Y9F3eBdX7HdC71dMWnSheQGAYhvAzvYWwPal7dMgjXBbHE13aS7Q

Bug#891994: epigrass: Depends on Qt4-only python-qwt5-qt4

[Gudjon I. Gudjonsson]

Hi

There is a new package in Debian 
https://tracker.debian.org/pkg/pyqt-qwt

that builds on the Qt5 version of Qwt6. 
It should not be difficult to upgrade the package from
PyQwt5 to PyQt-Qwt.

Since Python2 is also becoming obsolete in Debian, PyQt-Qwt is
only compiled for Python3 in Debian

Regards
Gudjon

Processed: severity of 907637 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 907637 serious
Bug #907637 [src:linux] bonding with virtio NICs does not work any more
Severity set to 'serious' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
907637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906852: thunderbird fix is WIP

[Adam Borowski]

> XUL addons are no longer supported.
>
> If it is confirmed that this package works with thunderbird 60,
> it might be an option to change the dependency to only thunderbird.

Currently, it does not -- but there's work that claims to run on quantum
thunderbirds:
https://github.com/CubicF/FireTray/pull/1

So it's premature to remove this package yet.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ What Would Jesus Do, MUD/MMORPG edition:
⣾⠁⢰⠒⠀⣿⡁ • multiplay with an admin char to benefit your mortal [Mt3:16-17]
⢿⡄⠘⠷⠚⠋⠀ • abuse item cloning bugs [Mt14:17-20, Mt15:34-37]
⠈⠳⣄ • use glitches to walk on water [Mt14:25-26]

Processed (with 1 error): your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 907197 908034
Bug #907197 {Done: Carsten Schoenert } [thunderbird] 
thunderbird 60 - although thunderbird-l10n-it is installed, the language is 
always English
Unable to merge bugs because:
severity of #908034 is 'serious' not 'important'
Failed to merge 907197: Did not alter merged bugs.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
907197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907197
908034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907167: marked as done (rust-sha2-asm FTBFS)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 17:35:30 +
with message-id 
and subject line Bug#907167: fixed in rust-sha2-asm 0.5.1-2
has caused the Debian Bug report #907167,
regarding rust-sha2-asm FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sha2-asm
Version: 0.5.1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-sha2-asm.html

...
cargo:rustc-link-lib=static=sha512
cargo:rustc-link-search=native=/build/1st/rust-sha2-asm-0.5.1/target/x86_64-unknown-linux-gnu/debug/build/sha2-asm-cfd20d882e83d3cd/out
 Running `rustc --crate-name sha2_asm src/lib.rs --crate-type lib 
--emit=dep-info,link -C debuginfo=2 -C metadata=7072e9ac2ed4af31 -C 
extra-filename=-7072e9ac2ed4af31 --out-dir 
/build/1st/rust-sha2-asm-0.5.1/target/x86_64-unknown-linux-gnu/debug/deps 
--target x86_64-unknown-linux-gnu -C 
incremental=/build/1st/rust-sha2-asm-0.5.1/target/x86_64-unknown-linux-gnu/debug/incremental
 -L 
dependency=/build/1st/rust-sha2-asm-0.5.1/target/x86_64-unknown-linux-gnu/debug/deps
 -L dependency=/build/1st/rust-sha2-asm-0.5.1/target/debug/deps -C 
linker=x86_64-linux-gnu-gcc -C debuginfo=2 --cap-lints warn -C 
link-arg=-Wl,-z,relro -L 
native=/build/1st/rust-sha2-asm-0.5.1/target/x86_64-unknown-linux-gnu/debug/build/sha2-asm-cfd20d882e83d3cd/out
 -L 
native=/build/1st/rust-sha2-asm-0.5.1/target/x86_64-unknown-linux-gnu/debug/build/sha2-asm-cfd20d882e83d3cd/out
 -l static=sha256 -l static=sha512`
Finished dev [unoptimized + debuginfo] target(s) in 3.60s
/usr/share/cargo/dh-cargo-built-using: abort: could not determine 
source-distribution conditions of 
build/sha2-asm-cfd20d882e83d3cd/out/libsha256.a.
You must patch build.rs of sha2-asm to output 
'println!("dh-cargo:deb-built-using=sha256=$s={}", 
env::var("CARGO_MANIFEST_DIR").unwrap());' where:
- $s is 1 if the license(s) of the included static libs require source 
distribution alongside binaries, otherwise 0
dh_auto_test: env CARGO_CHANNEL=debug /usr/share/cargo/dh-cargo-built-using 
returned exit code 1
make: *** [debian/rules:3: build] Error 1
--- End Message ---
--- Begin Message ---
Source: rust-sha2-asm
Source-Version: 0.5.1-2

We believe that the bug you reported is fixed in the latest version of
rust-sha2-asm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
kpcyrd  (supplier of updated rust-sha2-asm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 08 Sep 2018 19:11:44 +0200
Source: rust-sha2-asm
Binary: librust-sha2-asm-dev
Architecture: source
Version: 0.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: kpcyrd 
Description:
 librust-sha2-asm-dev - Assembly implementation of SHA-2 compression functions 
- Rust sou
Closes: 907167
Changes:
 rust-sha2-asm (0.5.1-2) unstable; urgency=medium
 .
   * Package sha2-asm 0.5.1 from crates.io using debcargo 2.2.6
 (Closes: #907167)
Checksums-Sha1:
 1037f1f6ce95e78c7bb9513bad1a50e40c51438d 2079 rust-sha2-asm_0.5.1-2.dsc
 94d934e669c5086f565898eba613ce3de7f73741 2824 
rust-sha2-asm_0.5.1-2.debian.tar.xz
 20b9863b7d1f381359a15f7b45003eaa3c568521 6691 
rust-sha2-asm_0.5.1-2_amd64.buildinfo
Checksums-Sha256:
 beda1ef9b5960b280addc07942eea6e4a43ee5464e35ed54356168158b085e5c 2079 
rust-sha2-asm_0.5.1-2.dsc
 d097f0c2d15baffafa4da1861b4092eac7aa0fd91c4a754ecec60d2d6540b666 2824 
rust-sha2-asm_0.5.1-2.debian.tar.xz
 eecf40c532a2fafd7c428b1ddd38af2f1a1989bde774d659e0776cffc00dce76 6691 
rust-sha2-asm_0.5.1-2_amd64.buildinfo
Files:
 2470b0f78b200e59c7c5f75e9908aa32 2079 rust optional rust-sha2-asm_0.5.1-2.dsc
 af256c0792c58b20c5df11859087c3af 2824 rust optional 
rust-sha2-asm_0.5.1-2.debian.tar.xz
 33c32bdb184a265cdba337c3d7237d15 6691 rust optional 
rust-sha2-asm_0.5.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAluUAywACgkQfmUo2nUv

Bug#908068: [Pkg-privacy-maintainers] Bug#908068: torbrowser-launcher fails with torbrowser 8.0

[gregor herrmann]

On Sun, 09 Sep 2018 00:22:18 +0900, Roger Shimizu wrote:

> > Today torbrowser 8.0 was released, and after updating it (from
> > torbrowser 7.x, started with torbrowser-launcher), the new version
> > doesn't start:
> 
> thanks for your report!
> have you tried experimental version [1]? It's working in my
> environment without any patch or hack.

Quoting my original bug report:

| Same for the version in experimental (0.3.0~dev-1~exp3).


But it looks like the necessary patches are already upstream, so this
should be sorted out soon.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bettina Wegner: s dremlen fejgel ofj di zwajgn


signature.asc
Description: Digital Signature

Bug#907150: marked as done (sailcut: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup'))

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 16:50:16 +
with message-id 
and subject line Bug#907150: fixed in sailcut 1.4.1-2
has caused the Debian Bug report #907150,
regarding sailcut: FTBFS in buster/sid (invalid use of incomplete type 'class 
QButtonGroup')
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sailcut
Version: 1.4.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --list-missing
   dh_update_autotools_config -i -O--parallel -O--list-missing
   dh_auto_configure -i -O--parallel -O--list-missing
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 -i -O--parallel -O--list-missing
make -j1
make[1]: Entering directory '/<>'
cd src/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile 
/<>/src/src.pro '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 ) && make -f Makefile 
/usr/bin/fig2dev
/usr/bin/xsltproc
make[2]: Entering directory '/<>/src'
/usr/lib/qt5/bin/lrelease ts/sailcut_de.ts -qm ../share/sailcut/sailcut_de.qm

[... snipped ...]

/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:
formhull.cpp:101:76: note:   candidate expects 3 arguments, 4 provided
 connect( actionViewDef, SIGNAL( triggered() ), this, SLOT( slotDef() ) );
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmainwindow.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMainWindow:1,
 from formmain.h:23,
 from formhull.h:23,
 from formhull.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 

Bug#881894: [Pkg-mozext-maintainers] Bug#881894: xul-ext-cookie-monster: dead upstream, broken in FF57

[Sean Whitton]

Hello,

On Sat 08 Sep 2018 at 03:09PM +0800, Paul Wise wrote:

> On Thu, 16 Nov 2017 06:21:56 +0100 Christoph Anton Mitterer wrote:
>
>> Package: xul-ext-cookie-monster
>>
>> Seems this addon is dead upstream (at least:
>> https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/
>> says "This add-on has been removed by its author.").
>>
>> Also it won't work with FF >57 anymore.
>
> There are a couple of alternatives that could be packaged:
>
> https://github.com/Cookie-AutoDelete/Cookie-AutoDelete

I've had good experience with this previously, so I filed an RFP
(#908285) yesterday.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: forcibly merging 906837 908311

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 906837 908311
Bug #906837 {Done: Adrian Bunk } [xul-ext-ublock-origin] 
xul-ext-ublock-origin no longer works with firefox-esr 60
Bug #908311 [xul-ext-ublock-origin] After Firefox 60 upgrade, xul-ext* packages 
have become unusable on Stretch
Severity set to 'serious' from 'grave'
Marked Bug as done
Marked as fixed in versions ublock-origin/1.16.6+dfsg-1.
Merged 906837 908311
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906837
908311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908337: cubemap FTBFS on 32bit

[Adrian Bunk]

Source: cubemap
Version: 1.4.0-1
Severity: serious
Tags: ftbfs

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

...
server.cpp: In member function 'void Server::process_client(Client*)':
server.cpp:676:16: error: conversion from '_Deque_iterator' to non-scalar type 
'_Deque_iterator' 
requested
 lower_bound(stream->suitable_starting_points.begin(),
 ~~~^~
  stream->suitable_starting_points.end(),
  ~~~
  stream->bytes_received - stream->prebuffering_bytes);
  
server.cpp:679:26: error: no match for 'operator==' (operand types are 
'std::deque::const_iterator' {aka 'std::_Deque_iterator'} and 'std::deque::iterator' {aka 'std::_Deque_iterator'})
if (starting_point_it == stream->suitable_starting_points.end()) {
~~^
In file included from /usr/include/c++/8/utility:70,
 from /usr/include/c++/8/algorithm:60,
 from server.cpp:17:
/usr/include/c++/8/bits/stl_pair.h:443:5: note: candidate: 'template constexpr bool std::operator==(const std::pair<_T1, _T2>&, const 
std::pair<_T1, _T2>&)'
 operator==(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
 ^~~~
...

Processed: libeigen3-dev: wrong prototype in unsupported/Eigen/src/IterativeSolvers/DGMRES.h

[Debian Bug Tracking System]

Processing control commands:

> block 907162 by -1
Bug #907162 [src:step] step: FTBFS in buster/sid (invalid use of incomplete 
type 'class QItemSelectionModel')
907162 was not blocked by any bugs.
907162 was not blocking any bugs.
Added blocking bug(s) of 907162: 908336

-- 
907162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907162
908336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908298: libgdk-pixbuf2.0-0: FTBFS on i386: Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be a Meson build directory.

[Iain Lane]

On Sat, Sep 08, 2018 at 09:19:46AM +0200, Sven Joachim wrote:
> > | Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does 
> > not seem to be a Meson build directory.
> > | make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1
> > `
> >
> > Will send a patch as soon as I have the bug number.
> 
> Here it is, tested in an i386 sbuild chroot. :-)

Thanks Sven! I actually didn't know about this problem (obviously, or I
wouldn't have made the upload like that), good to learn something. :-)

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Bug#908068: [Pkg-privacy-maintainers] Bug#908068: torbrowser-launcher fails with torbrowser 8.0

[Roger Shimizu]

On Thu, Sep 6, 2018 at 4:41 AM, gregor herrmann  wrote:
> Package: torbrowser-launcher
> Version: 0.2.9-3
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> User: pkg-apparmor-t...@lists.alioth.debian.org
> Usertags: buggy-profile
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Today torbrowser 8.0 was released, and after updating it (from
> torbrowser 7.x, started with torbrowser-launcher), the new version
> doesn't start:

thanks for your report!
have you tried experimental version [1]? It's working in my
environment without any patch or hack.

[1] https://wiki.debian.org/TorBrowser#Debian_.22experimental.22

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#895640: marked as done (openstack-trove FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 15:19:40 +
with message-id 
and subject line Bug#895640: fixed in openstack-trove 1:10.0.0-1
has caused the Debian Bug report #895640,
regarding openstack-trove FTBFS: test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
895640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openstack-trove
Version: 1:9.0.0-1
Severity: serious

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

...
==
FAIL: trove.tests.unittests.backup.test_backup_models.BackupORMTest.test_delete
trove.tests.unittests.backup.test_backup_models.BackupORMTest.test_delete
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1193, 
in _execute_context
context)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 507, 
in do_execute
cursor.execute(statement, parameters)
sqlite3.OperationalError: table agent_heartbeats already exists

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-9.0.0/trove/tests/unittests/backup/test_backup_models.py",
 line 275, in setUp
util.init_db()
  File "/build/1st/openstack-trove-9.0.0/trove/tests/unittests/util/util.py", 
line 31, in init_db
db_api.db_sync(CONF)
  File "/build/1st/openstack-trove-9.0.0/trove/db/sqlalchemy/api.py", line 108, 
in db_sync
migration.db_sync(options, version, repo_path)
  File "/build/1st/openstack-trove-9.0.0/trove/db/sqlalchemy/migration.py", 
line 106, in db_sync
upgrade(options, version=version, repo_path=repo_path)
  File "/build/1st/openstack-trove-9.0.0/trove/db/sqlalchemy/migration.py", 
line 64, in upgrade
return versioning_api.upgrade(sql_connection, repo_path, version)
  File "/usr/lib/python3/dist-packages/migrate/versioning/api.py", line 186, in 
upgrade
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
  File "", line 2, in _migrate
  File "/usr/lib/python3/dist-packages/migrate/versioning/util/__init__.py", 
line 167, in with_engine
return f(*a, **kw)
  File "/usr/lib/python3/dist-packages/migrate/versioning/api.py", line 366, in 
_migrate
schema.runchange(ver, change, changeset.step)
  File "/usr/lib/python3/dist-packages/migrate/versioning/schema.py", line 93, 
in runchange
change.run(self.engine, step)
  File "/usr/lib/python3/dist-packages/migrate/versioning/script/py.py", line 
148, in run
script_func(engine)
  File 
"/build/1st/openstack-trove-9.0.0/trove/db/sqlalchemy/migrate_repo/versions/005_heartbeat.py",
 line 37, in upgrade
create_tables([agent_heartbeats])
  File 
"/build/1st/openstack-trove-9.0.0/trove/db/sqlalchemy/migrate_repo/schema.py", 
line 69, in create_tables
table.create()
  File "/usr/lib/python3/dist-packages/sqlalchemy/sql/schema.py", line 778, in 
create
checkfirst=checkfirst)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1940, 
in _run_visitor
conn._run_visitor(visitorcallable, element, **kwargs)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1549, 
in _run_visitor
**kwargs).traverse_single(element)
  File "/usr/lib/python3/dist-packages/sqlalchemy/sql/visitors.py", line 121, 
in traverse_single
return meth(obj, **kw)
  File "/usr/lib/python3/dist-packages/sqlalchemy/sql/ddl.py", line 791, in 
visit_table
include_foreign_key_constraints=include_foreign_key_constraints
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 948, in 
execute
return meth(self, multiparams, params)
  File "/usr/lib/python3/dist-packages/sqlalchemy/sql/ddl.py", line 68, in 
_execute_on_connection
return connection._execute_ddl(self, multiparams, params)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1009, 
in _execute_ddl
compiled
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1200, 
in _execute_context
context)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1413, 
in _handle_dbapi_exception
exc_info
  File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 203, in 
raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File 

Bug#895640: Bug #895640 in openstack-trove marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #895640 in openstack-trove reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/services/openstack-trove/commit/70c923a1851976f02d5d5c9c8f9331538fad820d


d/changelog:
- Fixes FTBFS: test failures (Closes: #895640).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895640

Processed: Bug #895640 in openstack-trove marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895640 [src:openstack-trove] openstack-trove FTBFS: test failures
Added tag(s) pending.

-- 
895640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908294: hamlib: FTBFS (Syntax error: "then" unexpected)

[Enrico Rossi]

tags 908294 + fixed pending confirmed
stop

Hi Santiago,

it is strange why we were able to build it without catch the error, see
buildd logs.
Anyway you are right and I have fixed it on salsa.

Thanks for reporting.

-- 
GPG key: 4096R/5E0195FAF2133176 2010-10-19 Enrico Rossi 

Bug#900821: linux-image-4.9.0-6-amd64: apache reads wrong data over cifs filesystems served by samba

[Salvatore Bonaccorso]

Hi Santiago,

On Wed, Aug 29, 2018 at 12:03:31PM +0200, Santiago Garcia Mantinan wrote:
> Hi!
> 
> I have rechecked everything again.
> 
> Salvatore, I'm testing on an up to date buster running kernel 4.17.17-1 and
> I still see the kernel warning messages and the downloads are breaking and 
> wget
> still shows this king of messages:
> 2018-08-29 13:45:31 (122 MB/s) - Read error at byte 1056768/6538880 (Bad 
> address). Retrying.

Please disregard my comment about not able to beeing reproducible with
newer kernels. I potentially did an error in my testenvironment for
it, I would properly need to retest.

Salvatore

Bug#907150: Thanks for the patch!

[Jeremy Lainé]

Thanks for the patch I will prepare an upload.

Cheers,
Jeremy

Processed: Re: Bug#908294: hamlib: FTBFS (Syntax error: "then" unexpected)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 908294 + fixed pending confirmed
Bug #908294 [src:hamlib] hamlib: FTBFS (Syntax error: "then" unexpected)
Added tag(s) confirmed and fixed.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
908294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908294: Bug #908294 in hamlib marked as pending

[Enrico Rossi]

Control: tag -1 pending

Hello,

Bug #908294 in hamlib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/debian-hamradio-team/hamlib/commit/ec1209aaa38a383bdf3ef6329ea52f500e9d244e


Fix FTBFS uncatched syntax error

  * and revert the modification to delete the duplicate
lua test file. (Closes: #908294)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908294

Processed: Bug #908294 in hamlib marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908294 [src:hamlib] hamlib: FTBFS (Syntax error: "then" unexpected)
Added tag(s) pending.

-- 
908294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: google-android-ndk-installer: Superseded by google-android-installers?

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 849390 src:google-android-installers
Bug #849390 [src:google-android-ndk-installer] google-android-ndk-installer: 
Superseded by google-android-installers?
Added indication that 849390 affects src:google-android-installers
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
849390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 908323 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=127071

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 908323 https://rt.cpan.org/Ticket/Display.html?id=127071
Bug #908323 [src:libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=127071'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908323: libgtk3-perl: FTBFS: t/overrides.t failure

[gregor herrmann]

Control: tag -1 + confirmed upstream

On Sat, 08 Sep 2018 15:03:13 +0300, Niko Tyni wrote:

> I'm guessing this regressed with gdk-pixbuf 2.38.0+dfsg-1 or so, but I
> haven't verified that (and the ci.debian.net machinery doesn't seem to
> have pinpointed it yet either.)

Sounds plausible; the changelog mentions
"Generate separate introspection data for GdkPixdata API"
and there's now a
/usr/lib/x86_64-linux-gnu/girepository-1.0/GdkPixdata-2.0.typelib
besides the old
/usr/lib/x86_64-linux-gnu/girepository-1.0/GdkPixbuf-2.0.typelib

I tried with

#v+
--- a/lib/Gtk3.pm
+++ b/lib/Gtk3.pm
@@ -60,6 +60,7 @@
   Gtk-3.0   | Gtk3
   Gdk-3.0   | Gtk3::Gdk
   GdkPixbuf-2.0 | Gtk3::Gdk
+  GdkPixdata-2.0| Gtk3::Gdk
   Pango-1.0 | Pango
 
 =cut
@@ -84,6 +85,10 @@
 my $_GDK_PIXBUF_VERSION = '2.0';
 my $_GDK_PIXBUF_PACKAGE = 'Gtk3::Gdk';
 
+my $_GDK_PIXDATA_BASENAME = 'GdkPixdata';
+my $_GDK_PIXDATA_VERSION = '2.0';
+my $_GDK_PIXDATA_PACKAGE = 'Gtk3::Gdk';
+
 my $_PANGO_BASENAME = 'Pango';
 my $_PANGO_VERSION = '1.0';
 my $_PANGO_PACKAGE = 'Pango';
@@ -472,6 +477,11 @@
 flatten_array_ref_return_for => 
\@_GDK_PIXBUF_FLATTEN_ARRAY_REF_RETURN_FOR);
 
   Glib::Object::Introspection->setup (
+basename => $_GDK_PIXDATA_BASENAME,
+version => $_GDK_PIXDATA_VERSION,
+package => $_GDK_PIXDATA_PACKAGE);
+
+  Glib::Object::Introspection->setup (
 basename => $_PANGO_BASENAME,
 version => $_PANGO_VERSION,
 package => $_PANGO_PACKAGE);
#v-

but then the tests failed differently, with:

Gtk3::Gdk::Pixbuf::new_from_inline: passed too few parameters (expected 4, got 
3) at t/overrides.t line 762.
# Looks like your test exited with 255 just after 162.


so this needs a bit more (and more background knowledge).


Cheers,
gregor


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Michael Penn: Whole Truth


signature.asc
Description: Digital Signature

Processed: Re: Bug#908323: libgtk3-perl: FTBFS: t/overrides.t failure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed upstream
Bug #908323 [src:libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Added tag(s) upstream and confirmed.

-- 
908323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907988: rubber must specify the encoding when opening files

[Samuel Hym]

Le 07 septembre 2018 à 12h24, Emmanuel Fleury disait :

> Hi all,
> 
> I just reported this bug to the rubber dev-team. Waiting for the next
> bug-fix, I suggested the following fix:
[…]

This patch does indeed solve my problem, namely #907937, thanks!

But #907988 is unfortunately more general: there are other file
readings done assuming the locale encoding.

Best regards,
Samuel

Processed: forcibly merging 907988 907937

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 907988 907937
Bug #907988 [rubber] rubber must specify the encoding when opening files
Bug #907937 [rubber] rubber: generate UnicodeDecodeError if .log is not valid 
in locale encoding
Added indication that 907937 affects src:why3
Merged 907937 907988
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
907937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907937
907988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 907937 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 907937 serious
Bug #907937 [rubber] rubber: generate UnicodeDecodeError if .log is not valid 
in locale encoding
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
907937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): merging 907988 907937

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 907988 907937
Bug #907988 [rubber] rubber must specify the encoding when opening files
Unable to merge bugs because:
affects of #907937 is '' not 'src:why3'
Failed to merge 907988: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
907937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907937
907988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906470: grub2: FTBFS (test grub_cmd_set_date fails)

[Santiago Vila]

There is a patch to disable the test completely here:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26936#24

Thanks.

Processed: curl: CVE-2018-14618: NTLM password overflow via integer overflow

[Debian Bug Tracking System]

Processing control commands:

> found -1 7.52.1-1
Bug #908327 [src:curl] curl: CVE-2018-14618: NTLM password overflow via integer 
overflow
Marked as found in versions curl/7.52.1-1.
> fixed -1 7.52.1-5+deb9u7
Bug #908327 [src:curl] curl: CVE-2018-14618: NTLM password overflow via integer 
overflow
Marked as fixed in versions curl/7.52.1-5+deb9u7.

-- 
908327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908327: curl: CVE-2018-14618: NTLM password overflow via integer overflow

[Salvatore Bonaccorso]

Source: curl
Version: 7.61.0-1
Severity: serious
Tags: security upstream
Justification: otherwise regression from stable for security fix
Forwarded: https://github.com/curl/curl/issues/2756
Control: found -1 7.52.1-1
Control: fixed -1 7.52.1-5+deb9u7

Hi,

The following vulnerability was published for curl. Justification for
the severity, is that it would otherwise imply a regression from
stable for a security fix.

CVE-2018-14618[0]:
| curl before version 7.61.1 is vulnerable to a buffer overrun in the
| NTLM authentication code. The internal function
| Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two
| (SUM) to figure out how large temporary storage area to allocate from
| the heap. The length value is then subsequently used to iterate over
| the password and generate output into the allocated storage buffer. On
| systems with a 32 bit size_t, the math to calculate SUM triggers an
| integer overflow when the password length exceeds 2GB (2^31 bytes).
| This integer overflow usually causes a very small buffer to actually
| get allocated instead of the intended very huge one, making the use of
| that buffer end up in a heap buffer overflow. (This bug is almost
| identical to CVE-2017-8816.)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-14618
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14618
[1] https://curl.haxx.se/docs/CVE-2018-14618.html
[2] https://github.com/curl/curl/issues/2756
[3] https://github.com/curl/curl/commit/57d299a499155d4b327e341c6024e293b0418243

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: Re: Bug#906470: grub2: FTBFS (test grub_cmd_set_date fails)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 906470 grub2: FTBFS (test grub_cmd_set_date fails)
Bug #906470 [src:grub2] grub2: FTBFS in buster/sid (failing tests)
Changed Bug title to 'grub2: FTBFS (test grub_cmd_set_date fails)' from 'grub2: 
FTBFS in buster/sid (failing tests)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906470: grub2: FTBFS (test grub_cmd_set_date fails)

[Santiago Vila]

retitle 906470 grub2: FTBFS (test grub_cmd_set_date fails)
thanks

On Sat, 18 Aug 2018, Colin Watson wrote:

> On Fri, Aug 17, 2018 at 07:21:13PM +, Santiago Vila wrote:
> > FAIL: grub_cmd_set_date
> > ===
> > 
> > qemu-system-i386: -fw_cfg name=etc/sercon-port,string=0: warning: 
> > externally provided fw_cfg item names should be prefixed with "opt/"
> > Killed
> > Test failed: 2018-08-14 00:00:37 Tuesday
> 
> Is this consistently reproducible?  I think I've seen this locally on
> occasion, but it's always gone away when I tried to debug it.

Hi.

I seems this is a known issue, it was discovered by Guix people last year:

http://lists.gnu.org/archive/html/bug-grub/2017-06/msg00012.html

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26936

For some people, it seems to fail randomly. In some of my
autobuilders, it always fail.

I would just disable the test and close the bug in Debian.

But if you still want to debug it, I could still offer a test machine
where it happens all the time.

Thanks.

Processed: found 908324 in 4.2.0-2+deb8u3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 908324 4.2.0-2+deb8u3
Bug #908324 {Done: Salvatore Bonaccorso } [src:kamailio] 
kamailo: CVE-2018-16657
Marked as found in versions kamailio/4.2.0-2+deb8u3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907229: marked as done (kdesvn: FTBFS with Qt 5.11)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 12:18:59 +
with message-id 
and subject line Bug#907229: fixed in kdesvn 2.0.0-5
has caused the Debian Bug report #907229,
regarding kdesvn: FTBFS with Qt 5.11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
907229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 908324 4.4.4-2+deb9u3
Bug #908324 {Done: Salvatore Bonaccorso } [src:kamailio] 
kamailo: CVE-2018-16657
The source 'kamailio' and version '4.4.4-2+deb9u3' do not appear to match any 
binary packages
Ignoring request to alter fixed versions of bug #908324 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 908324 in 4.4.4-2+deb9u3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 908324 4.4.4-2+deb9u3
Bug #908324 {Done: Salvatore Bonaccorso } [src:kamailio] 
kamailo: CVE-2018-16657
The source 'kamailio' and version '4.4.4-2+deb9u3' do not appear to match any 
binary packages
Marked as fixed in versions kamailio/4.4.4-2+deb9u3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908324: reassign 908324 to src:kamailio, found 908324 in 4.4.4-2, closing 908324 ...

[Salvatore Bonaccorso]

reassign 908324 src:kamailio 
found 908324 4.4.4-2
close 908324 5.1.4-1
fixed 9083245 4.4.4-2+deb9u3
thanks

Bug#908324: kamailo: CVE-2018-16657

[Chris Lamb]

Hi security team,

> kamailo: CVE-2018-16657

Would you like me to prepare a stretch-security debdiff for
this issue?


Regards,

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

Processed (with 1 error): reassign 908324 to src:kamailio, found 908324 in 4.4.4-2, closing 908324 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 908324 src:kamailio
Bug #908324 [kamailo] kamailo: CVE-2018-16657
Warning: Unknown package 'kamailo'
Bug reassigned from package 'kamailo' to 'src:kamailio'.
No longer marked as found in versions 4.2.0-2+deb8u3.
Ignoring request to alter fixed versions of bug #908324 to the same values 
previously set
> found 908324 4.4.4-2
Bug #908324 [src:kamailio] kamailo: CVE-2018-16657
Marked as found in versions kamailio/4.4.4-2.
> close 908324 5.1.4-1
Bug #908324 [src:kamailio] kamailo: CVE-2018-16657
Marked as fixed in versions kamailio/5.1.4-1.
Bug #908324 [src:kamailio] kamailo: CVE-2018-16657
Marked Bug as done
> fixed 9083245 4.4.4-2+deb9u3
Failed to add fixed on 9083245: Unable to read any bugs successfully.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908324: kamailo: CVE-2018-16657

[Chris Lamb]

Package: kamailo
Version: 4.2.0-2+deb8u3
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for kamailo.

CVE-2018-16657[0]:
| In Kamailio before 5.0.7 and 5.1.x before 5.1.4, a crafted SIP message
| with an invalid Via header causes a segmentation fault and crashes
| Kamailio. The reason is missing input validation in the
| crcitt_string_array core function for calculating a CRC hash for To
| tags. (An additional error is present in the check_via_address core
| function: this function also misses input validation.) This could
| result in denial of service and potentially the execution of arbitrary
| code.

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

For further information see:

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


Regards,

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

Bug#908323: libgtk3-perl: FTBFS: t/overrides.t failure

[Niko Tyni]

Source: libgtk3-perl
Version: 0.034-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Control: block 902557 with -1

As noticed by the autopkgtest checks on ci.debian.net, this package fails
its test suite on current sid, making it also fail to build from source.

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/libg/libgtk3-perl/953602/log.gz

  Undefined subroutine ::Gdk::PIXDATA_HEADER_LENGTH called at 
/<>/blib/lib/Gtk3.pm line 2119.
  # Looks like your test exited with 255 just after 162.

  [...]

  Test Summary Report
  ---
  t/overrides.t(Wstat: 65280 Tests: 162 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 233 tests but ran 162.
  Files=22, Tests=843,  5 wallclock secs ( 0.18 usr  0.03 sys +  4.58 cusr  
0.46 csys =  5.25 CPU)
  Result: FAIL
 
I'm guessing this regressed with gdk-pixbuf 2.38.0+dfsg-1 or so, but I
haven't verified that (and the ci.debian.net machinery doesn't seem to
have pinpointed it yet either.)
-- 
Niko Tyni   nt...@debian.org

Bug#908237: marked as done (libnumbertext-tools: "spellout" looks for data in the wrong place)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 12:03:59 +
with message-id 
and subject line Bug#908237: fixed in libnumbertext 1.0-3
has caused the Debian Bug report #908237,
regarding libnumbertext-tools: "spellout" looks for data in the wrong place
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
908237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnumbertext-tools
Version: 1.0-2
Severity: normal

$ dpkg -L libnumbertext-tools
[...]
/usr/lib/libnumbertext/spellout

The tool is meant to be invoked by the end user, but is not
located in a directory in $PATH. I would expect it to go in
/usr/bin (and have a corresponding man page in
/usr/share/man/man1).

Also:

$ /usr/lib/libnumbertext/spellout -l en 101
spellout: missing language module

Using "strace", we see:

$ strace -e file /usr/lib/libnumbertext/spellout -l en 101
[...]
openat(AT_FDCWD, "en.sor", O_RDONLY)= -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "en.sor", O_RDONLY)= -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/numbertext/en.sor", O_RDONLY) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/usr/share/numbertext/en.sor", O_RDONLY) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "data/en.sor", O_RDONLY) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "data/en.sor", O_RDONLY) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "data/en.sor", O_RDONLY) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "data/en.sor", O_RDONLY) = -1 ENOENT (No such file or 
directory)

It looks first in "en.sor" in the current directory, which is a
security vulnerability (for instance when run in /tmp where some
attacker could have planted a malicious "en.sor" file).

And then in "/usr/share/numbertext" while "libnumbertext-data"
installs those files in "/usr/share/libnumbertext" instead.

A work around is to run:

$ /usr/lib/libnumbertext/spellout -l /usr/share/libnumbertext/en 101
one hundred one

Though it doesn't work for en-GB for which you'd need:

$ (cd /usr/share/libnumbertext && /usr/lib/libnumbertext/spellout -l en-GB 101)
one hundred and one

(but again looking in the current directory is a bad idea, so I'd expect that
one to stop working in a future version).

$ /usr/lib/libnumbertext/spellout -l /usr/share/libnumbertext/en-GB 101
one hundred one

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

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

Versions of packages libnumbertext-tools depends on:
ii  libc62.27-5
ii  libgcc1  1:8.2.0-4
ii  libnumbertext-1.0-0  1.0-2
ii  libstdc++6   8.2.0-4

libnumbertext-tools recommends no packages.

libnumbertext-tools suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: libnumbertext
Source-Version: 1.0-3

We believe that the bug you reported is fixed in the latest version of
libnumbertext, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libnumbertext package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 08 Sep 2018 11:22:31 +
Source: libnumbertext
Binary: libnumbertext-dev libnumbertext-1.0-0 libnumbertext-data 
libnumbertext-tools libnumbertext-java libreoffice-numbertext
Architecture: source
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Description:
 libnumbertext-1.0-0 - Number to number name and money text conversion 

Processed: libgtk3-perl: FTBFS: t/overrides.t failure

[Debian Bug Tracking System]

Processing control commands:

> block 902557 with -1
Bug #902557 [release.debian.org] transition: Perl 5.28
902557 was blocked by: 904737 904735 902674 895959 897724 904740 902771 862678 
899021 900832 904727 901082 902556 905838 907015 904914 905913 901085 897790 
900232 629405
902557 was not blocking any bugs.
Added blocking bug(s) of 902557: 908323

-- 
902557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902557
908323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 908237 to libnumbertext-tools: "spellout" looks for data in the wrong place

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 908237 libnumbertext-tools: "spellout" looks for data in the wrong 
> place
Bug #908237 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Changed Bug title to 'libnumbertext-tools: "spellout" looks for data in the 
wrong place' from 'libnumbertext-tools: "spellout" is not in $PATH and looks 
for data in the wrong places'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#908237: libnumbertext-tools: "spellout" is not in $PATH and looks for data in the wrong places

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 908237 - moreinfo
Bug #908237 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Removed tag(s) moreinfo.
> tag 908237 - unreproducible
Bug #908237 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Removed tag(s) unreproducible.
> clone 908237 -1 -2
Bug #908237 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Bug 908237 cloned as bugs 908321-908322
> severity -1 wishlist
Bug #908321 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Severity set to 'wishlist' from 'normal'
> tag -1 + wontfix
Bug #908321 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Added tag(s) wontfix.
> tag -1 - pending
Bug #908321 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Removed tag(s) pending.
> severity -2 normal
Bug #908322 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Ignoring request to change severity of Bug 908322 to the same value.
> tag -2 - pending
Bug #908322 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Removed tag(s) pending.
> retitle -2 should not search for data files in .
Bug #908322 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Changed Bug title to 'should not search for data files in .' from 
'libnumbertext-tools: "spellout" is not in $PATH and looks for data in the 
wrong places'.
> severity 908237 grave
Bug #908237 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Severity set to 'grave' from 'normal'
> forwarded 908237 https://github.com/Numbertext/libnumbertext/pull/36
Bug #908237 [libnumbertext-tools] libnumbertext-tools: "spellout" is not in 
$PATH and looks for data in the wrong places
Set Bug forwarded-to-address to 
'https://github.com/Numbertext/libnumbertext/pull/36'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908237
908321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908321
908322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 907229 is not forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notforwarded 907229
Bug #907229 [src:kdesvn] kdesvn: FTBFS with Qt 5.11
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
907229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#902557: transition: Perl 5.28

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 907015
Bug #902557 [release.debian.org] transition: Perl 5.28
902557 was blocked by: 905838 904740 904727 895959 904737 902771 902556 900232 
899021 629405 900832 901085 902674 897724 904735 862678 904914 901082 897790 
905913
902557 was not blocking any bugs.
Added blocking bug(s) of 902557: 907015

-- 
902557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907494: hgsvn: package is missing most of its files

[Nick Smallbone]

Hi,

On Tue, 28 Aug 2018, at 9:56 PM, Vincent Danjean wrote:
>   I do not use it anymore and, as the upstream website changed,
> I just see I'm several version late.
> 
> 
>   I will try to update/redo this package. Any help is welcome.

I had a go at fixing the packaging, but discovered that the latest upstream 
version isn't compatible with current versions of Mercurial and Subversion. 
Unfortunately it doesn't look to be maintained any more.

Nick

Bug#908317: postfixadmin: 'public' directory missing

[Jakob Butler]

Package: postfixadmin
Version: 3.2-1
Severity: grave
Justification: renders package unusable

Hello,

The new 3.2 release of postfixadmin has rearranged the files considerably, and
most files relevant for the web interface are now in the 'public' directory.
This directory, however, seems to be missing in the Debian package...

Best regards,
Jakob Butler

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

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

Versions of packages postfixadmin depends on:
ii  apache2 [httpd] 2.4.34-1
ii  dbconfig-common 2.0.9
ii  debconf 1.5.69
ii  default-mysql-client1.0.4
ii  libapache2-mod-php  1:7.2+62
ii  libapache2-mod-php7.2 [libapache2-mod-php]  7.2.9-1
ii  php 1:7.2+62
ii  php-imap1:7.2+62
ii  php-mbstring1:7.2+62
ii  php-mysql   1:7.2+62
ii  php7.2 [php]7.2.9-1
ii  php7.2-imap [php-imap]  7.2.9-1
ii  php7.2-mbstring [php-mbstring]  7.2.9-1
ii  php7.2-mysql [php-mysqlnd]  7.2.9-1
ii  wwwconfig-common0.3.0

Versions of packages postfixadmin recommends:
ii  dovecot-core1:2.3.2.1-1
pn  mariadb-server  
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.35-1
ii  php7.2-cli [php-cli]7.2.9-1
ii  postfix-mysql   3.3.0-1+b1
ii  zendframework   1.12.20+dfsg-1

postfixadmin suggests no packages.

-- debconf information:
  postfixadmin/passwords-do-not-match:
  postfixadmin/db/dbname: postfixadmin
  postfixadmin/db/app-user: postfixadmin@localhost
* postfixadmin/dbconfig-install: true
  postfixadmin/install-error: abort
  postfixadmin/dbconfig-reinstall: false
  postfixadmin/upgrade-backup: true
  postfixadmin/dbconfig-remove: true
  postfixadmin/remote/newhost:
  postfixadmin/remove-error: abort
* postfixadmin/database-type: mysql
* postfixadmin/mysql/admin-user: root
  postfixadmin/internal/skip-preseed: false
  postfixadmin/upgrade-error: abort
  postfixadmin/internal/reconfiguring: false
  postfixadmin/mysql/method: Unix socket
  postfixadmin/dbconfig-upgrade: true
  postfixadmin/remote/port:
  postfixadmin/purge: false
  postfixadmin/remote/host: localhost
  postfixadmin/missing-db-package-error: abort

Bug#907493: [SECURITY] [DSA 4288-1] ghostscript security update

[Moritz Mühlenhoff]

On Sat, Sep 08, 2018 at 07:10:59AM +0200, Paul Gevers wrote:
> Dear security team,
> 
> On 09/07/18 23:23, Moritz Muehlenhoff wrote:
> > Package: ghostscript
> > CVE ID : CVE-2018-15908 CVE-2018-15910 CVE-2018-15911
> >  CVE-2018-16511 CVE-2018-16513 CVE-2018-16539
> >  CVE-2018-16540 CVE-2018-16541 CVE-2018-16542
> >  CVE-2018-16543 CVE-2018-16585
> 
> The latest upload of ghostscript to unstable, which as far as I know
> only tried to fix some of these CVE's, caused the autopkgtest of
> multiple packages to start timing out (bug 907493). Were you aware of
> that and have you done any testing to verify that this isn't an issue
> for the stable upload?
> 
> If so, that would be an interesting data point for the bug. If not, you
> may be facing the same regression in stretch. I have the wild hunch that
> this is related to the openssl upstream bump in unstable, but nobody has
> verified that yet. If stretch is no not seeing this regression that
> would mean there may also be a path to fix testing/buster until we
> figure out what needs fixing in ghostscript.

This probably needs upstream commit 150c8f69646b854a99f35f27edaae012eb2e900f,
which I've applied for the stable-security update, but is not yet in sid.

Cheers,
Moritz

Bug#908311: After Firefox 60 upgrade, xul-ext* packages have become unusable on Stretch

[Julien Aubin]

Package: xul-ext-ublock-origin
Version: 1.10.4+dfsg-1
Severity: grave
Justification: renders package unusable

Firefox has been updated to version 60esr on stable, removing support for XUL
extensions.

However those extensions like Ublock Origin have not been upgraded accordingly
to the WebExt format, rendering them completely useless.

Could you please upgrade them asap on stable ?

Thanks a lot.



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

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

Versions of packages xul-ext-ublock-origin depends on:
ii  firefox-esr60.2.0esr-1~deb9u2
ii  fonts-font-awesome 4.7.0~dfsg-1
ii  icedove1:52.9.1-1~deb9u1
ii  iceweasel  60.2.0esr-1~deb9u2
ii  thunderbird [icedove]  1:52.9.1-1~deb9u1

xul-ext-ublock-origin recommends no packages.

xul-ext-ublock-origin suggests no packages.

-- no debconf information

Processed: Re: Bug#907150: sailcut: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup')

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #907150 [src:sailcut] sailcut: FTBFS in buster/sid (invalid use of 
incomplete type 'class QButtonGroup')
Added tag(s) patch.

-- 
907150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907150: sailcut: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup')

[Juhani Numminen]

Control: tags -1 +patch

Dear maintainer,

Fedora has a patch to fix Qt 5.11 compatibility by adding the needed includes.
(I haven't tested it.)

https://src.fedoraproject.org/rpms/sailcut/c/e1a4eb5719cc0f39e529534f51e75a12e336aa61

Juhani

Bug#908298: marked as done (libgdk-pixbuf2.0-0: FTBFS on i386: Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be a Meson build directory.)

[Debian Bug Tracking System]

Your message dated Sat, 08 Sep 2018 09:18:56 +
with message-id 
and subject line Bug#908298: fixed in gdk-pixbuf 2.38.0+dfsg-3
has caused the Debian Bug report #908298,
regarding libgdk-pixbuf2.0-0: FTBFS on i386: Directory 
$'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be 
a Meson build directory.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
908298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdk-pixbuf
Version: 2.38.0+dfsg-2
Severity: serious
Tags: ftbfs

The attempt to fix the test timeouts on slow arches in 2.38.0+dfsg-2 has
introduced a new FTBFS problem on i386[1]:

,
|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>/gdk-pixbuf-2.38.0+dfsg'
| # on slow arches the "slow" tests take longer than the timeout allowed
| # by upstream; allow even more time (-t is a multipiler)
| meson test -C /<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu -t 5
| Only ninja backend is supported to rebuild tests before running them.
| Meson test encountered an error:
| 
| Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not 
seem to be a Meson build directory.
| make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1
`

Will send a patch as soon as I have the bug number.


1. 
https://buildd.debian.org/status/fetch.php?pkg=gdk-pixbuf=i386=2.38.0%2Bdfsg-2=1536340844=0
--- End Message ---
--- Begin Message ---
Source: gdk-pixbuf
Source-Version: 2.38.0+dfsg-3

We believe that the bug you reported is fixed in the latest version of
gdk-pixbuf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated gdk-pixbuf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Sep 2018 10:54:08 +0200
Source: gdk-pixbuf
Binary: libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common 
libgdk-pixbuf2.0-dev libgdk-pixbuf2.0-doc libgdk-pixbuf2.0-0-udeb 
gir1.2-gdkpixbuf-2.0
Architecture: source
Version: 2.38.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gir1.2-gdkpixbuf-2.0 - GDK Pixbuf library - GObject-Introspection
 libgdk-pixbuf2.0-0 - GDK Pixbuf library
 libgdk-pixbuf2.0-0-udeb - GDK Pixbuf library - minimal runtime (udeb)
 libgdk-pixbuf2.0-bin - GDK Pixbuf library (thumbnailer)
 libgdk-pixbuf2.0-common - GDK Pixbuf library - data files
 libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files)
 libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation)
Closes: 908298
Changes:
 gdk-pixbuf (2.38.0+dfsg-3) unstable; urgency=medium
 .
   [ Sven Joachim ]
   * Fix FTBFS on any-i386 (Closes: #908298)
Checksums-Sha1:
 0b1ce3017387571fbcbd3ba839a94f995691da3a 2928 gdk-pixbuf_2.38.0+dfsg-3.dsc
 02b8f2eb65ae9a9bcc795db77b2422d5f144fc3b 16372 
gdk-pixbuf_2.38.0+dfsg-3.debian.tar.xz
 ec43c3a81f578f5b43c7009ca7b7a23f63def919 11428 
gdk-pixbuf_2.38.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 30ff24530f4883cc998f38a2741da1d21ce41fbd7b81e030bce1b11f883d31b1 2928 
gdk-pixbuf_2.38.0+dfsg-3.dsc
 7ed28acb46f55d6948cf55ea6b0da666abe93c9d1cd340f61e6e38514cda5610 16372 
gdk-pixbuf_2.38.0+dfsg-3.debian.tar.xz
 81de6b640858032c1b9e2458f927832cbb104dd4e1cc9e8001d2b8e77e98c187 11428 
gdk-pixbuf_2.38.0+dfsg-3_amd64.buildinfo
Files:
 e0dcb20b4323e3ac220bf555a1e46227 2928 libs optional 
gdk-pixbuf_2.38.0+dfsg-3.dsc
 a1a09cfef51dd7e448fde0f36c6f7f99 16372 libs optional 
gdk-pixbuf_2.38.0+dfsg-3.debian.tar.xz
 24bbf36584d2c97789aee4460e4a203f 11428 libs optional 
gdk-pixbuf_2.38.0+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAluTj6MRHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwZy7w/7Bnsy1nOQUeDoM6MMitBI1yJSB8L7Rbf7
K/7qx28Qum+7nFQDaHgDNAJCuHmcpqi9Zy4VVsALOortrHMzMPwCO+sBZ44itkEm
LsQ9MXCP1bfS6gJduTm8Tt1vhWB1ZQWRrNsA7RnOPYfqgK8J/bb34aKaQtBZOCX5
VgN99QcMEQhFozY29oiboT9Dj4v/xI/tQpvt1niUHeUAwUKxmHLzhc82xKEf53Nc
TW5IZ6SGTuDvuqhnwp6S6HcO8I3DTTDJ0L1a2U9O8g5TJBfC16X9DSXZN7xoXSkN

Processed: ghostscript: CVE-2018-16585

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 9.20~dfsg-3.2+deb9u3
Bug #908305 [src:ghostscript] ghostscript: CVE-2018-16585
Marked as fixed in versions ghostscript/9.20~dfsg-3.2+deb9u3.

-- 
908305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908305: ghostscript: CVE-2018-16585

[Salvatore Bonaccorso]

Source: ghostscript
Version: 9.20~dfsg-3.2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699663
Control: fixed -1 9.20~dfsg-3.2+deb9u3

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-16585[0]:
| An issue was discovered in Artifex Ghostscript before 9.24. The
| .setdistillerkeys PostScript command is accepted even though it is not
| intended for use during document processing (e.g., after the startup
| phase). This leads to memory corruption, allowing remote attackers able
| to supply crafted PostScript to crash the interpreter or possibly have
| unspecified other impact.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16585
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16585
[1] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=1497d65039885a52b598b137dd8622bd4672f9be
[2] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=971472c83a345a16dac9f90f91258bb22dd77f22
[3] https://bugs.ghostscript.com/show_bug.cgi?id=699663

Please adjust the affected versions in the BTS as needed.

Regards,
Salvtore

Bug#908298: Bug #908298 in gdk-pixbuf marked as pending

[Andreas Henriksson]

Control: tag -1 pending

Hello,

Bug #908298 in gdk-pixbuf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gdk-pixbuf/commit/8edcee3d520416976f9748210958af41dc0e7471


Fix FTBFS on any-i386

The build directory is named after $(DEB_HOST_GNU_TYPE) rather than
$(DEB_HOST_MULTIARCH), and on any-i386 those are different.

Closes: #908298



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908298

Bug#908300: ghostscript: Regression from a054156d425b4dbdaaa9fda4b5f1182b27598c2b commit ("Fix handling of pre-SAFER opened files")

[Salvatore Bonaccorso]

hi,

On Sat, Sep 08, 2018 at 10:52:36AM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Sat, Sep 08, 2018 at 10:17:10AM +0200, Salvatore Bonaccorso wrote:
> > (which might require
> > http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5b5536fa88a9e885032bc0df3852c3439399a5c
> > as well).
> 
> Scratch that, thas is just a fix for a further issue, namely
> CVE-2018-16543 (and will fill a separate bug for it).

Filled as #908303.

Regards,
Salvatore

Processed: Bug #908298 in gdk-pixbuf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908298 [src:gdk-pixbuf] libgdk-pixbuf2.0-0: FTBFS on i386: Directory 
$'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be 
a Meson build directory.
Added tag(s) pending.

-- 
908298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908300: ghostscript: Regression from a054156d425b4dbdaaa9fda4b5f1182b27598c2b commit ("Fix handling of pre-SAFER opened files")

[Salvatore Bonaccorso]

Hi,

On Sat, Sep 08, 2018 at 10:17:10AM +0200, Salvatore Bonaccorso wrote:
> (which might require
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5b5536fa88a9e885032bc0df3852c3439399a5c
> as well).

Scratch that, thas is just a fix for a further issue, namely
CVE-2018-16543 (and will fill a separate bug for it).

Regards,
Salvatore

Processed: ghostscript: CVE-2018-16543

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 9.20~dfsg-3.2+deb9u4
Bug #908303 [src:ghostscript] ghostscript: CVE-2018-16543
Marked as fixed in versions ghostscript/9.20~dfsg-3.2+deb9u4.

-- 
908303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908303: ghostscript: CVE-2018-16543

[Salvatore Bonaccorso]

Source: ghostscript
Version: 9.20~dfsg-3.2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699670
Control: fixed -1 9.20~dfsg-3.2+deb9u4

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-16543[0]:
| In Artifex Ghostscript before 9.24, gssetresolution and gsgetresolution
| allow attackers to have an unspecified impact.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16543
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16543
[1] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=5b5536fa88a9e885032bc0df3852c3439399a5c0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#908304: ghostscript: CVE-2018-16510

[Salvatore Bonaccorso]

Source: ghostscript
Version: 9.22~dfsg-3
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699671

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-16510[0]:
| An issue was discovered in Artifex Ghostscript before 9.24. Incorrect
| exec stack handling in the "CS" and "SC" PDF primitives could be used
| by remote attackers able to supply crafted PDFs to crash the
| interpreter or possibly have unspecified other impact.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16510
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16510
[1] https://bugs.ghostscript.com/show_bug.cgi?id=699671
[2] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=ea735ba37dc0fd5f5622d031830b9a559dec1cc9

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#908300: ghostscript: Regression from a054156d425b4dbdaaa9fda4b5f1182b27598c2b commit ("Fix handling of pre-SAFER opened files")

[Salvatore Bonaccorso]

Source: ghostscript
Version: 9.22~dfsg-3
Severity: serious
Tags: patch upstream
Justification: regression

Hi

It was reported a regression while testing the security update, which
resulted in the increment to +deb9u4, which included the fix. The
regression was spotted while
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a054156d425b4dbdaaa9fda4b5f1182b27598c2b;hp=0d3901189f245232f0161addf215d7268c4d05a3
is applied:

https://github.com/apple/cups/issues/5392

There is an upstream fix for it:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=150c8f69646b854a99f35f27edaae012eb2e900f

(which might require
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5b5536fa88a9e885032bc0df3852c3439399a5c
as well).

Regards,
Salvatore

Bug#881904: xul-ext-useragentswitcher: does not work with modern versions of Firefox

[Paul Wise]

On Thu, 16 Nov 2017 01:05:32 -0800 Ian Bruce wrote:

> Please replace it with one of the following:
> 
> https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher-revived/
> https://addons.mozilla.org/en-US/firefox/addon/custom-user-agent-revived/

I note that both of these are *very* different to the existing plugin
so I suggest that the upstream author be pinged about their update.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#853992: xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions

[Paul Wise]

Control: forwarded -1 
https://github.com/RequestPolicyContinued/requestpolicy/issues/704
Control: tags -1 + fixed-upstream # partially

On Fri, 3 Feb 2017 03:00:02 +0530 shirish शिरीष wrote:

> First of all thank you for taking care of xul-ext-requestpolicy for so
> long. Was just browsing today and saw that 1.0beta12.4 was introduced
> few months back. The only addition according to the changelog
> https://github.com/RequestPolicyContinued/requestpolicy/blob/dev-1.0/ChangeLog.md
> 
> is being compatible with WebExtensions which Mozilla is going to come
> up in the next few releases.

This has now happened and upstream has partially fixed this,
status is at the listedURL above.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Processed (with 1 error): Re: xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://github.com/RequestPolicyContinued/requestpolicy/issues/704
Bug #853992 [xul-ext-requestpolicy] xul-ext-requestpolicy: update requestpolicy 
to 1.0 beta12.4 - compatibility with web extensions
Set Bug forwarded-to-address to 
'https://github.com/RequestPolicyContinued/requestpolicy/issues/704'.
> tags -1 + fixed-upstream # partially
Unknown tag/s: #, partially.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #853992 [xul-ext-requestpolicy] xul-ext-requestpolicy: update requestpolicy 
to 1.0 beta12.4 - compatibility with web extensions
Added tag(s) fixed-upstream.

-- 
853992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906864: xul-ext-perspectives no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 21:18:04 +0300 Adrian Bunk wrote:

> Package: xul-ext-perspectives
> 
> XUL addons are no longer supported.

Mozilla are still discussing if WebExtensions or NSS extensions are
going to be allowed to access and modify TLS validation results:

https://bugzilla.mozilla.org/show_bug.cgi?id=1489080
https://bugzilla.mozilla.org/show_bug.cgi?id=1435951

I think this plugin should just be removed from Debian for now.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#906865: xul-ext-refcontrol no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 21:19:52 +0300 Adrian Bunk wrote:

> Package: xul-ext-refcontrol
> 
> XUL addons are no longer supported.

I think it should be removed from Debian in favour of this:

https://addons.mozilla.org/en-US/firefox/addon/referer-modifier/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#906862: xul-ext-openinbrowser no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 21:15:00 +0300 Adrian Bunk wrote:

> Package: xul-ext-openinbrowser
> 
> XUL addons are no longer supported.

I think it should be removed from Debian in favour of this:

https://github.com/Rob--W/open-in-browser

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Processed: tagging 882287, bug 882287 is forwarded to https://github.com/hackademix/noscript/

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 882287 + fixed-upstream
Bug #882287 [xul-ext-noscript] xul-ext-noscript: new upstream version 
(WebExtensions)
Added tag(s) fixed-upstream.
> forwarded 882287 https://github.com/hackademix/noscript/
Bug #882287 [xul-ext-noscript] xul-ext-noscript: new upstream version 
(WebExtensions)
Set Bug forwarded-to-address to 'https://github.com/hackademix/noscript/'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
882287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#769441: Does not work with Iceweasel 33

[Paul Wise]

On Thu, 13 Nov 2014 18:33:24 +0200 Arto Jantunen wrote:

> Package: xul-ext-monkeysphere
> 
> Starting with Iceweasel 33 the monkeysphere extension no longer works. No
> error messages are shown, but a cert that validates fine with msva-query-agent
> is not accepted by Iceweasel.

In addition, since Firefox 57, XUL extensions are no longer supported
and Mozilla are still discussing if WebExtensions or NSS extensions are
going to be allowed to access and modify TLS validation results:

https://bugzilla.mozilla.org/show_bug.cgi?id=1489080
https://bugzilla.mozilla.org/show_bug.cgi?id=1435951

I think this plugin should just be removed from Debian for now.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#906858: xul-ext-livehttpheaders no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 21:10:27 +0300 Adrian Bunk wrote:

> Package: xul-ext-livehttpheaders
> 
> XUL addons are no longer supported.

The native Firefox developer tools are almost a replacement,
so I think this package can just be removed from Debian.

The only missing thing is the headers tab in the page info dialog
but it is not possible to provide a WebExtension that does this.

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#906831: xul-ext-iceweasel-branding no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 19:10:39 +0300 Adrian Bunk wrote:

> Package: xul-ext-iceweasel-branding
> 
> XUL addons are no longer supported.

Apparently Parabola has kept their package working (untested):

https://notabug.org/desktopd/iceweasel-branding/issues/3
https://git.parabola.nu/packages/iceweasel-branding.git/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#827174: xul-ext-https-finder is broken

[Paul Wise]

On Mon, 13 Jun 2016 12:49:06 +0200 Jakub Wilk wrote:

> HTTPS Finder does not seem to find any HTTPS pages.
> To reproduce, go to . This site has a valid HTTPS 
> version, but HTTPS Finder doesn't find it.

I think it should be removed from Debian in favour of one of these:

https://mybrowseraddon.com/smart-https.html
https://github.com/Rob--W/https-by-default
https://github.com/EFForg/https-everywhere

The last one is already packaged in Debian but the option to find https
versions of websites has a slightly suboptimal UI discussed here:

https://github.com/EFForg/https-everywhere/issues/16488

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Processed: Re: Bug#908298: libgdk-pixbuf2.0-0: FTBFS on i386: Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be a Meson build directory.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #908298 [src:gdk-pixbuf] libgdk-pixbuf2.0-0: FTBFS on i386: Directory 
$'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be 
a Meson build directory.
Added tag(s) patch.

-- 
908298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908298: libgdk-pixbuf2.0-0: FTBFS on i386: Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be a Meson build directory.

[Sven Joachim]

Control: tags -1 + patch

On 2018-09-08 09:10 +0200, Sven Joachim wrote:

> Source: gdk-pixbuf
> Version: 2.38.0+dfsg-2
> Severity: serious
> Tags: ftbfs
>
> The attempt to fix the test timeouts on slow arches in 2.38.0+dfsg-2 has
> introduced a new FTBFS problem on i386[1]:
>
> ,
> |debian/rules override_dh_auto_test
> | make[1]: Entering directory '/<>/gdk-pixbuf-2.38.0+dfsg'
> | # on slow arches the "slow" tests take longer than the timeout allowed
> | # by upstream; allow even more time (-t is a multipiler)
> | meson test -C /<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu -t 5
> | Only ninja backend is supported to rebuild tests before running them.
> | Meson test encountered an error:
> | 
> | Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does 
> not seem to be a Meson build directory.
> | make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1
> `
>
> Will send a patch as soon as I have the bug number.

Here it is, tested in an i386 sbuild chroot. :-)

>From 8d9f4796631dadb3bb7942ce1d1602940366bca3 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Sat, 8 Sep 2018 09:15:54 +0200
Subject: [PATCH] Fix FTBFS on any-i386

The build directory is named after $(DEB_HOST_GNU_TYPE) rather than
$(DEB_HOST_MULTIARCH), and on any-i386 those are different.

Closes: #908298
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 88301a7c..dd9dac7a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,7 +23,7 @@ infiles := \
 override_dh_auto_test:
 	# on slow arches the "slow" tests take longer than the timeout allowed
 	# by upstream; allow even more time (-t is a multipiler)
-	meson test -C $(CURDIR)/obj-$(DEB_HOST_MULTIARCH) -t 5
+	meson test -C $(CURDIR)/obj-$(DEB_HOST_GNU_TYPE) -t 5
 
 override_dh_install:
 	find $(CURDIR)/debian/tmp -name *.la -print -delete
-- 
2.19.0.rc2

Bug#906841: xul-ext-firebug no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 20:01:17 +0300 Adrian Bunk wrote:

> Package: xul-ext-firebug
> 
> XUL addons are no longer supported.

The native Firefox developer tools were written to replace Firebug
so I think this package can just be removed from Debian.

https://getfirebug.com/
https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#906859: xul-ext-dom-inspector no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 21:11:16 +0300 Adrian Bunk wrote:

> Package: xul-ext-dom-inspector
> 
> XUL addons are no longer supported.

The native Firefox developer tools are almost a replacement,
so I think this package can just be removed from Debian.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#908298: libgdk-pixbuf2.0-0: FTBFS on i386: Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not seem to be a Meson build directory.

[Sven Joachim]

Source: gdk-pixbuf
Version: 2.38.0+dfsg-2
Severity: serious
Tags: ftbfs

The attempt to fix the test timeouts on slow arches in 2.38.0+dfsg-2 has
introduced a new FTBFS problem on i386[1]:

,
|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>/gdk-pixbuf-2.38.0+dfsg'
| # on slow arches the "slow" tests take longer than the timeout allowed
| # by upstream; allow even more time (-t is a multipiler)
| meson test -C /<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu -t 5
| Only ninja backend is supported to rebuild tests before running them.
| Meson test encountered an error:
| 
| Directory $'/<>/gdk-pixbuf-2.38.0+dfsg/obj-i386-linux-gnu' does not 
seem to be a Meson build directory.
| make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1
`

Will send a patch as soon as I have the bug number.


1. 
https://buildd.debian.org/status/fetch.php?pkg=gdk-pixbuf=i386=2.38.0%2Bdfsg-2=1536340844=0

Bug#881894: xul-ext-cookie-monster: dead upstream, broken in FF57

[Paul Wise]

On Thu, 16 Nov 2017 06:21:56 +0100 Christoph Anton Mitterer wrote:

> Package: xul-ext-cookie-monster
> 
> Seems this addon is dead upstream (at least:
> https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/
> says "This add-on has been removed by its author.").
> 
> Also it won't work with FF >57 anymore.

There are a couple of alternatives that could be packaged:

https://github.com/Cookie-AutoDelete/Cookie-AutoDelete
https://github.com/gorhill/uMatrix

Source:

https://anarc.at/software/desktop/firefox/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#908297: libindicate FTBFS with glib 2.58

[Adrian Bunk]

Source: libindicate
Version: 0.6.92-6
Severity: serious
Tags: ftbfs

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

...
/build/1st/libindicate-0.6.92/./libindicate/server.c: In function 
'indicate_server_class_init':
/build/1st/libindicate-0.6.92/./libindicate/server.c:230:2: error: 
'g_type_class_add_private' is deprecated [-Werror=deprecated-declarations]
  g_type_class_add_private (class, sizeof (IndicateServerPrivate));
  ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /build/1st/libindicate-0.6.92/./libindicate/server.h:34,
 from /build/1st/libindicate-0.6.92/./libindicate/server.c:30:
/usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here
 void g_type_class_add_private   (gpointerg_class,
  ^~~~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:732: libindicate_la-server.lo] Error 1

Bug#908279: lua-torch-image: FTBFS (TH.h: No such file or directory)

[Juhani Numminen]

On Fri, 07 Sep 2018 21:01:31 + Santiago Vila  wrote:

> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> [...]

> libtool --silent --tag=CC --mode=compile cc -c -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr//include/lua5.1 -I/<> -I/<>/generic 
> -I/usr/include/TH/ -DHAVE_JPEG_MEM_SRC -DHAVE_JPEG_MEM_DEST -Wall -Wextra -o 
> /<>/5.1-torch-image/ppm.lo ppm.c 
> X/<>/5.1-torch-image/ppm.lo
> libtool: warning: libobj name '/<>/5.1-torch-image/ppm.lo' may 
> not contain shell special characters.
> ppm.c:2:10: fatal error: TH.h: No such file or directory
>  #include 

It looks like lua-torch-torch7 moved TH.h from /usr/include/TH to 
/usr/include/lua5.1/TH,
which caused lua-torch-image to FTBFS.

https://salsa.debian.org/science-team/lua-torch-torch7/commit/0f19b6da6ad5f9f30de24ff6ca49897d46b95f29


Juhani

Processed: tagging 899309, bug 899309 is forwarded to https://github.com/sarahavilov/autofillforms-e10s

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 899309 + fixed-upstream
Bug #899309 [src:autofill-forms] autofill-forms: Replace it with non legacy 
autofillforms-e10 to be compatible with ff 60.
Added tag(s) fixed-upstream.
> forwarded 899309 https://github.com/sarahavilov/autofillforms-e10s
Bug #899309 [src:autofill-forms] autofill-forms: Replace it with non legacy 
autofillforms-e10 to be compatible with ff 60.
Set Bug forwarded-to-address to 
'https://github.com/sarahavilov/autofillforms-e10s'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
899309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906870: xul-ext-certificatepatrol no longer works with firefox-esr 60

[Paul Wise]

On Tue, 21 Aug 2018 21:31:45 +0300 Adrian Bunk wrote:

> Package: xul-ext-certificatepatrol
> Severity: serious
> 
> XUL addons are no longer supported.

Mozilla are still discussing if WebExtensions or NSS extensions are
going to be allowed to access and modify TLS validation results:

https://bugzilla.mozilla.org/show_bug.cgi?id=1489080
https://bugzilla.mozilla.org/show_bug.cgi?id=1435951

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#908294: hamlib: FTBFS (Syntax error: "then" unexpected)

[Santiago Vila]

Package: src:hamlib
Version: 3.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster using dpkg-buildpackage -A
but it failed:


[...]

   debian/rules override_dh_auto_install-indep
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
mkdir -p /<>/debian/tmp/usr/share/doc/hamlib
cp -r /<>/build-indep/doc/html \
/<>/debian/tmp/usr/share/doc/hamlib/
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh_install
lts=/<>/debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua \
if [ -f "$lts" ]; then \
rm -f $lts; \
fi
/bin/sh: 2: Syntax error: "then" unexpected
make[1]: *** [debian/rules:105: override_dh_install] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:18: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Looking at the code:

override_dh_install:
dh_install
lts=$(CURDIR)/debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua \
if [ -f "$$lts" ]; then \
rm -f $$lts; \
fi

it seems there is a missing ";" at the end of lts= line.

However, if you want to remove a file unconditionally no matter what, I wonder
why don't you do this instead:

--- a/debian/rules
+++ b/debian/rules
@@ -102,10 +102,7 @@ override_dh_auto_install-indep:
 
 override_dh_install:
dh_install
-   lts=$(CURDIR)/debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua \
-   if [ -f "$$lts" ]; then \
-   rm -f $$lts; \
-   fi
+   rm -f debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua
 
 override_dh_auto_clean:
dh_auto_clean


Or maybe it would be even better to use "dh_install -Xexcluded_file" in a 
single line.

Thanks.