Bug#902961: mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests

[Jason Duerstock]

I suspect the "right" solution to this is to define the "base" and
"mask" variables in ComputeRandomAllocationAddress() based on what
works for each architecture, but my enthusiasm for gathering that
information was pretty low at the time I ran into this, and hasn't
gone up much since then.
On Tue, Jul 3, 2018 at 7:54 PM Simon McVittie  wrote:
>
> Source: mozjs52
> Version: 52.3.1-8
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> (X-Debbugs-Cc to contributors to #897178, to which this seems related,
> and #902197)
>
> After fixing #902197, the mozjs52 build-time tests failed on the amd64
> Debian porterbox barriere. Specifically, the smoke-test in debian/test.sh
> that's run before trying the actual test suite:
>
> "$SRCDIR/js/src/js" -e 'print("Hello, world")'
>
> fails, with js exiting 1.
>
> Running it under gdb reveals that this is because
> ReserveProcessExecutableMemory() in js/src/jit/ProcessExecutableMemory.cpp
> fails during startup, causing JS_Init() to fail. js helpfully has no
> diagnostics at all for this, it just silently exits with EXIT_FAILURE.
> (Ignore the first implementation of ReserveProcessExecutableMemory(),
> which is for Windows; the Unix implementation is around line 300.)
>
> That function gets a random address, and passes it as the first argument
> of mmap(., 1 gigabyte, PROT_NONE, MAP_PRIVATE | MAP_ANON, -1, 0) on
> 64-bit machines, or the same but with 128M instead of 1G on 32-bit.
> This now seems to be failing and returning NULL.
>
> I was surprised to find that on the same machine, if I install gjs (a
> GNOME wrapper around mozjs) and the slightly older mozjs 52.3.1-7 that it
> depends on, gjs-console -c 'print("hello")' works OK. (We don't package
> mozjs' own command-line tool 'js' any more, so no precompiled copy is
> available.) The changes between 52.3.1-7 and what I'm compiling all seem
> to be specific to non-amd64 architectures, so maybe this is about the
> environment in which mozjs was built, rather than the source code used?
>
> A hack that works to avoid this is to retry the mmap() without the address
> hint, like in Jason Duerstock's debian/patches/ia64-support.patch,
> but for non-IA64 architectures as well; see attached. I suspect this
> might be the wrong solution, but perhaps it points someone who knows
> this better than I do in the direction of a better solution...
>
> This also makes me wonder whether the failure addressed by
> ia64-support.patch was in fact a generic issue with newer $something
> (kernel? compiler? dpkg-buildflags?), which happened to only be seen
> by ia64 porters because everyone else was compiling and testing mozjs52
> with an older $something?
>
> smcv

Bug#900533: Bug still exists

[Jiri Palecek]

On 7/6/18 9:59 PM, Salvo Tomaselli wrote:

Chromium works for me, both testing and unstable.


Yes, but the others are complaining about the version in stable-security 
(which is a embarrassing, letting such an annoying bug slip through to 
security updates).


Regards

    Jiri Palecek

Bug#902943: marked as done (cryptsetup-initramfs: regression: LV holding LUKS device isn't activated at initramfs stage)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jul 2018 01:49:44 +
with message-id 
and subject line Bug#902943: fixed in cryptsetup 2:2.0.3-5
has caused the Debian Bug report #902943,
regarding cryptsetup-initramfs: regression: LV holding LUKS device isn't 
activated at initramfs stage
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.)


-- 
902943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup-initramfs
Version: 2:2.0.3-4
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   After system upgrade the system is not bootable anymore due the
   initramfs is unable to find the "source" for the rootfs and boot
   hangs.
   Before the upgrade this worked seamlessly for a long time, UUID of FS
   did not change recently.

   When breaking into initramfs (kernel argument 'break'), I am able to
   activate the LVM logical volume manually with 'lvm lvchange -a y linux'.
   Resuming the boot after that works, i.e. the passphrase is asked and
   boot continues after successful decryption.

   Please let me know if I should provide more detailed debug
   information.

   Regards,
   doak


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/linux-debian_crypt ro quiet

-- /etc/crypttab
linux-debian_crypt UUID=979d71b4-f9a9-45cb-b72e-6c81754ab504 none luks

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/linux-debian_crypt /   ext4errors=remount-ro 0  
 1
# /boot was on /dev/sda5 during installation
UUID=42edef9b-e7dc-4ceb-a5e1-05d958d6ea6f /boot ext4 defaults 0 2
/SWAP   noneswapdefaults0   0

-- lsmod
Module  Size  Used by
ctr16384  6
ccm20480  9
cmac   16384  0
rfcomm 86016  0
fuse  118784  3
ipt_MASQUERADE 16384  1
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
nf_conntrack_netlink49152  0
nfnetlink  16384  2 nf_conntrack_netlink
xfrm_user  45056  1
xfrm_algo  16384  1 xfrm_user
iptable_nat16384  1
nf_conntrack_ipv4  16384  3
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
nf_nat_ipv416384  1 iptable_nat
xt_addrtype16384  2
xt_conntrack   16384  1
nf_nat 36864  2 nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack  151552  7 
nf_conntrack_ipv4,ipt_MASQUERADE,nf_conntrack_netlink,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
libcrc32c  16384  2 nf_conntrack,nf_nat
br_netfilter   24576  0
bridge184320  1 br_netfilter
stp16384  1 bridge
llc16384  2 bridge,stp
bnep   24576  2
overlay   102400  0
ebtable_filter 16384  0
ebtables   36864  1 ebtable_filter
devlink61440  0
ip6table_filter16384  0
ip6_tables 32768  1 ip6table_filter
iptable_filter 16384  1
snd_hda_codec_hdmi 57344  1
binfmt_misc20480  1
intel_rapl 24576  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 180224  0
uvcvideo  106496  0
arc4   16384  2
kvm   704512  1 kvm_intel
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_v4l2 28672  1 uvcvideo
videobuf2_common   49152  2 uvcvideo,videobuf2_v4l2
irqbypass  16384  1 kvm
iTCO_wdt   16384  0
cdc_mbim   16384  0
wmi_bmof   16384  0
btusb  53248  0
iwlmvm290816  0
iTCO_vendor_support16384  1 iTCO_wdt
videodev  204800  3 uvcvideo,videobuf2_common,videobuf2_v4l2
mac80211  802816  1 iwlmvm
cdc_wdm24576  1 cdc_mbim
btrtl  16384  1 btusb
intel_cstate   16384  0
btbcm  16384  1 btusb
media  45056  2 uvcvideo,videodev
cdc_ncm40960  1 cdc_mbim
btintel24576  1 btusb
intel_uncore  131072  0
usbnet 49152  2 cdc_mbim,cdc_ncm
iwlwifi   225280  1 iwlmvm
i915

Bug#902466: marked as done (golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jul 2018 01:49:51 +
with message-id 
and subject line Bug#902466: fixed in 
golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-3
has caused the Debian Bug report #902466,
regarding golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid 
(failing tests)
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.)


-- 
902466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-grpc-ecosystem-go-grpc-prometheus
Version: 1.1+git20170826.0dafe0d-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d'
cd 
obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto
 && \
GOPATH=obj-x86_64-linux-gnu make 
make[2]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d/obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto'
PATH="obj-x86_64-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 protoc \
  -I. \
-Iobj-x86_64-linux-gnu/src \

[... snipped ...]

=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsStarted
--- FAIL: TestServerInterceptorSuite (0.08s)
--- PASS: TestServerInterceptorSuite/TestRegisterPresetsStuff (0.02s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHandled (0.01s)
server_test.go:218: 
Error Trace:server_test.go:218
Error:  Not equal: 
expected: 1
actual  : 0
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHandled
Messages:   grpc_server_handled_total should be 
incremented for PingList FailedPrecondition
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHistograms 
(0.01s)
server_test.go:186: 
Error Trace:server_test.go:186
Error:  Not equal: 
expected: 2
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList OK
server_test.go:193: 
Error Trace:server_test.go:193
Error:  Not equal: 
expected: 4
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList FailedPrecondition
--- PASS: TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts 
(0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsStarted (0.00s)
server_test.go:168: 
Error Trace:server_test.go:168
Error:  Not equal: 
expected: 6
actual  : 5
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsStarted
Messages:   grpc_server_started_total should be 
incremented for PingList
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHandled (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHistograms (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsStarted (0.01s)
server_test.go:86: stopped grpc.Server at: 127.0.0.1:33315
FAIL
FAILgithub.com/grpc-ecosystem/go-grpc-prometheus0.124s
?   github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto [no 
test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 

Bug#903146: libgit2-glib: compatibility with libgit2 0.27 in experimental

[Steve Langasek]

Package: libgit2-glib
Version: 0.26.2-1
Severity: serious
Tags: patch experimental
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Dear maintainers,

libgit2-glib fails to build against libgit2 0.27, which is currently in
experimental, due to an API change:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I. -pthread -I/usr/in
clude/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include -DGIT
_SSH=1 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -We
rror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werr
or=format-security -Werror=format=2 -Werror=missing-include-dirs -Werror=return-
type -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=
. -fstack-protector-strong -Wformat -Werror=format-security -c ggit-cred.c  -fPI
C -DPIC -o .libs/ggit-cred.o
ggit-config.c: In function ‘ggit_config_add_file’:
ggit-config.c:298:36: warning: passing argument 4 of ‘git_config_add_file_ondisk
’ makes pointer from integer without a cast [-Wint-conversion]
force);
^
In file included from /usr/include/git2.h:22:0,
 from ggit-config.h:26,
 from ggit-config.c:21:
/usr/include/git2/config.h:208:17: note: expected ‘const git_repository * {aka c
onst struct git_repository *}’ but argument is of type ‘gboolean {aka int}’
 GIT_EXTERN(int) git_config_add_file_ondisk(
 ^~
ggit-config.c:295:8: error: too few arguments to function ‘git_config_add_file_o
ndisk’
  ret = git_config_add_file_ondisk (_ggit_native_get (config),
^~
In file included from /usr/include/git2.h:22:0,
 from ggit-config.h:26,
 from ggit-config.c:21:
/usr/include/git2/config.h:208:17: note: declared here
 GIT_EXTERN(int) git_config_add_file_ondisk(
 ^~
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I.. -I.. -I. -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include -DGIT_SSH=1 -Wall 
-Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes 
-Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
-Werror=format-security -Werror=format=2 -Werror=missing-include-dirs 
-Werror=return-type   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o ggit-cred-plaintext.lo ggit-cred-plaintext.c
Makefile:780: recipe for target 'ggit-config.lo' failed
make[4]: *** [ggit-config.lo] Error 1

  
https://launchpad.net/ubuntu/+source/libgit2-glib/0.26.2-1build1/+build/15063247

Please find attached a one-line patch that fixes libgit2-glib for
compatibility with the new libgit2.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libgit2-glib-0.26.2/debian/patches/libgit2-0.27-compat.patch 
libgit2-glib-0.26.2/debian/patches/libgit2-0.27-compat.patch
--- libgit2-glib-0.26.2/debian/patches/libgit2-0.27-compat.patch
1969-12-31 16:00:00.0 -0800
+++ libgit2-glib-0.26.2/debian/patches/libgit2-0.27-compat.patch
2018-07-06 17:24:47.0 -0700
@@ -0,0 +1,19 @@
+Description: Compatibility with libgit2 0.27
+ git_config_add_file_ondisk() now takes an additional (optional) 'repo'
+ argument.  Fix the build failure.
+Author: Steve Langasek 
+Forwarded: no
+Last-Update: 2018-07-07
+
+Index: libgit2-glib-0.26.2/libgit2-glib/ggit-config.c
+===
+--- libgit2-glib-0.26.2.orig/libgit2-glib/ggit-config.c
 libgit2-glib-0.26.2/libgit2-glib/ggit-config.c
+@@ -295,6 +295,7 @@
+   ret = git_config_add_file_ondisk (_ggit_native_get (config),
+ path,
+ (git_config_level_t)level,
++NULL,
+ force);
+   g_free (path);
+ 
diff -Nru libgit2-glib-0.26.2/debian/patches/series 
libgit2-glib-0.26.2/debian/patches/series
--- libgit2-glib-0.26.2/debian/patches/series   1969-12-31 16:00:00.0 
-0800
+++ libgit2-glib-0.26.2/debian/patches/series   2018-07-06 17:23:15.0 
-0700
@@ -0,0 +1 @@
+libgit2-0.27-compat.patch

Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-2

[Dmitry Smirnov]

On Saturday, 7 July 2018 3:30:10 AM AEST Santiago Vila wrote:
> I assume this will be frustrating for you as maintainer, but believe
> me that it's also frustrating for me as reporter.

Strangely enough I feel more puzzled than frustrated...


> I've built today version 1.2.0-2 ten times in four different autobuilders,
> and it failed ten times.
>
> I would say that whatever you did to solve this problem is not working.

I've changed timeout that influenced outcome of failing test for me.
First I've reproduced the problem by running tests continuously in loop and 
I've found that if fails after some repetitions usually within range of 
2...16. After adjusting timeout I could not reproduce the problem at all.

Maybe it is failing in your autobuilders for different reason...


> I see that the issue was already in github:
> 
> https://github.com/grpc-ecosystem/go-grpc-prometheus/pull/44

That looks completely unrelated to me. Yesterday I've opened a new ticket for 
this very problem:

 https://github.com/grpc-ecosystem/go-grpc-prometheus/issues/56


> May I suggest that you just disable the failing tests until they are
> fixed upstream?

Of course.

-- 
All the best,
 Dmitry Smirnov.

---

Honesty is a gift we can give to others. It is also a source of power and
an engine of simplicity. Knowing that we will attempt to tell the truth,
whatever the circumstances, leaves us with little to prepare for. We can
simply be ourselves.
-- Sam Harris



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

Bug#903145: python3-gevent: Package fails to install in a Python3.7 environment

[Pierre-Elliott Bécue]

Package: python3-gevent
Version: 1.2.2-2
Severity: grave
Tags: upstream buster sid
Justification: renders package unusable

Dear maintainer,

python3-gevent fails to install properly in a Python3.7 environment.

The reason is the reservation of async keyword by Python3.7

Example:

"""
Setting up python3-gevent (1.2.2-2) ...
  File "/usr/lib/python3/dist-packages/gevent/libev/corecffi.py", line 601
def async(self, ref=True, priority=None):
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/gevent/threadpool.py", line 281
self.async = hub.loop.async()
 ^
SyntaxError: invalid syntax

dpkg: error processing package python3-gevent (--configure):
 installed python3-gevent package post-installation script subprocess returned 
error exit status 1
"""

You can see that this impacts also dependencies, such as
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pytest-httpbin/535939/log.gz

Cheers!

-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (990, 'stable'), (99, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages python3-gevent depends on:
ii  libc6 2.24-11+deb9u3
ii  python3   3.5.3-1
pn  python3-greenlet  

python3-gevent recommends no packages.

Versions of packages python3-gevent suggests:
pn  python-gevent-doc   
pn  python3-gevent-dbg  
pn  python3-openssl 

-- 
Pierre-Elliott Bécue

Bug#899688: marked as done (sbuild: Invalid maintainer address buildd-tools-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 23:49:24 +
with message-id 
and subject line Bug#899688: fixed in sbuild 0.77.0-1
has caused the Debian Bug report #899688,
regarding sbuild: Invalid maintainer address 
buildd-tools-de...@lists.alioth.debian.org
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.)


-- 
899688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sbuild
Version: 0.76.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sbuild,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sbuild since the list address
buildd-tools-de...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
buildd-tools-de...@lists.alioth.debian.org is 2.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sbuild
Source-Version: 0.77.0-1

We believe that the bug you reported is fixed in the latest version of
sbuild, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer  (supplier of updated sbuild 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: Fri, 06 Jul 2018 23:11:45 +0200
Source: sbuild
Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd
Architecture: source
Version: 0.77.0-1
Distribution: unstable
Urgency: medium
Maintainer: sbuild maintainers 
Changed-By: Johannes 'josch' Schauer 
Description:
 buildd - Daemon for automatically building Debian binary packages from Deb
 libsbuild-perl - Library for building Debian binary packages from Debian 
sources
 sbuild - Tool for building Debian binary packages from Debian sources
 sbuild-debian-developer-setup - Convenience script to set up an sbuild 
environment for Debian Dev
Closes: 837188 858899 861762 863718 865432 866006 866402 867180 868657 870451 
871968 882057 886257 888710 891588 891590 893228 898946 899688 900916 901167 
901360 901372 901725 901727 901730
Changes:
 sbuild (0.77.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control: move "exim4 | mail-transport-agent" from Recommends to
 Suggests (closes: #863718)
   * Set maintainer address to sbu...@packages.debian.org (closes: #899688)
   * lib/Sbuild/Build.pm: filter out foreign essential and multiarch foreign
 packages before passing them to dose3 (closes: #865432)
   * man/sbuild.1.in: pre- and post-build-commands are 

Bug#903124: libevent-rpc-perl: FTBFS in stretch (sbuild hangs, expired SSL certificate?)

[gregor herrmann]

On Fri, 06 Jul 2018 15:54:56 +0200, Santiago Vila wrote:

> On Fri, Jul 06, 2018 at 03:29:11PM +0200, gregor herrmann wrote:
> > If we want to fix this in stretch, we probably have to just update
> > t/ssl/. Or skip t/04.cnct-auth-ssl-verifypeer-wrongca.t (and maybe
> > also t/04.cnct-auth-ssl-verifypeer.t).
> Debian is like Las Vegas: "Packages in stretch must be buildable in stretch",
> so yes, I definitely think we want to fix this in stretch.

Well said :)
 
> Note: There is a point release planned for Saturday, July 14th, and
> new uploads for stretch-proposed-updates will be frozen this weekend.

JFTR: I won't have time this weekend, but I hoe someone else from the
perl team can handle this issue.


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: Ry Cooder: Paris, Texas


signature.asc
Description: Digital Signature

Bug#903138: Unmet dependencies

[Sebastian Ramacher]

Control: tags -1 + moreinfo unreproducible

On 2018-07-06 23:34:58, Jörg Frings-Fürst wrote:
> Package: src:vlc
> Version: 3.0.3-1+b1
> Severity: grave
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hello,
> 
> on apt-get upgrade I get
> 
> 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  vlc-bin : Depends: libvlc-bin (= 3.0.3-1+b1) but 3.0.3-2 is to be installed
>  vlc-plugin-base : Depends: vlc-data (= 3.0.3-1) but 3.0.3-2 is to be 
> installed
>  vlc-plugin-skins2 : Depends: vlc-plugin-qt (= 3.0.3-2) but 3.0.3-1+b1 is to 
> be
> installed
> E: Broken packages

I cannot reproduce this issue. vlc installs fine. Do you have any held packages
or something pinned so that libplacebo5 cannot be installed? That's the only
real change from 3.0.3-1+b1 to 3.0.3-2.

Cheers

> 
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.16.0-2-amd64 (SMP w/6 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 vlc depends on:
> ii  vlc-bin  3.0.3-1+b1
> ii  vlc-plugin-base  3.0.3-1+b1
> ii  vlc-plugin-qt3.0.3-1+b1
> ii  vlc-plugin-video-output  3.0.3-1+b1
> 
> Versions of packages vlc recommends:
> ii  vlc-l10n   3.0.3-1
> ii  vlc-plugin-notify  3.0.3-1+b1
> ii  vlc-plugin-samba   3.0.3-1+b1
> ii  vlc-plugin-skins2  3.0.3-1+b1
> ii  vlc-plugin-video-splitter  3.0.3-1+b1
> ii  vlc-plugin-visualization   3.0.3-1+b1
> 
> vlc suggests no packages.
> 
> Versions of packages libvlc-bin depends on:
> ii  libc62.27-3
> ii  libvlc5  3.0.3-1+b1
> 
> Versions of packages libvlc5 depends on:
> ii  libc62.27-3
> ii  libvlccore9  3.0.3-1+b1
> 
> Versions of packages libvlc5 recommends:
> ii  libvlc-bin  3.0.3-1+b1
> 
> Versions of packages vlc-bin depends on:
> ii  libc6   2.27-3
> ii  libvlc-bin  3.0.3-1+b1
> ii  libvlc5 3.0.3-1+b1
> 
> Versions of packages vlc-plugin-base depends on:
> ii  liba52-0.7.4 0.7.4-19
> ii  libarchive13 3.2.2-4
> ii  libaribb24-0 1.0.3-2
> ii  libasound2   1.1.6-1
> ii  libass9  1:0.14.0-2
> ii  libavahi-client3 0.7-4
> ii  libavahi-common3 0.7-4
> ii  libavc1394-0 0.5.4-5
> ii  libavcodec57 7:3.4.2-2+b2
> ii  libavformat577:3.4.2-2+b2
> ii  libavutil55  7:3.4.2-2+b2
> ii  libbasicusageenvironment12018.04.25-2
> ii  libbluray2   1:1.0.2-3
> ii  libc62.27-3
> ii  libcairo21.15.10-3
> ii  libcddb2 1.3.2-6
> ii  libchromaprint1  1.4.3-2
> ii  libcrystalhd31:0.0~git20110715.fdd2f19-13
> ii  libdbus-1-3  1.12.8-3
> ii  libdc1394-22 2.2.5-1
> ii  libdca0  0.0.6-1
> ii  libdvbpsi10  1.3.2-1
> ii  libdvdnav4   6.0.0-1
> ii  libdvdread4  6.0.0-1
> ii  libebml4v5   1.3.6-2
> ii  libfaad2 2.8.8-1
> ii  libflac8 1.3.2-3
> ii  libfontconfig1   2.13.0-5
> ii  libfreetype6 2.8.1-2
> ii  libfribidi0  0.19.7-3
> ii  libgcc1  1:8.1.0-9
> ii  libgcrypt20  1.8.3-1
> ii  libglib2.0-0 2.56.1-2
> ii  libgnutls30  3.5.18-1
> ii  libgpg-error01.31-1
> ii  libgroupsock82018.04.25-2
> ii  libharfbuzz0b1.8.1-1
> ii  libjpeg62-turbo  1:1.5.2-2+b1
> ii  libkate1 0.4.1-8
> ii  liblirc-client0  0.10.0-2+b1
> ii  liblivemedia62   2018.04.25-2
> ii  liblua5.2-0  5.2.4-1.1+b2
> ii  libmad0  0.15.1b-9
> ii  

Processed: Re: Bug#903138: Unmet dependencies

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo unreproducible
Bug #903138 [src:vlc] Unmet dependencies
Added tag(s) moreinfo and unreproducible.

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

Bug#903138: Unmet dependencies

[Jörg Frings-Fürst]

Package: src:vlc
Version: 3.0.3-1+b1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

on apt-get upgrade I get


Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 vlc-bin : Depends: libvlc-bin (= 3.0.3-1+b1) but 3.0.3-2 is to be installed
 vlc-plugin-base : Depends: vlc-data (= 3.0.3-1) but 3.0.3-2 is to be installed
 vlc-plugin-skins2 : Depends: vlc-plugin-qt (= 3.0.3-2) but 3.0.3-1+b1 is to be
installed
E: Broken packages



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/6 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 vlc depends on:
ii  vlc-bin  3.0.3-1+b1
ii  vlc-plugin-base  3.0.3-1+b1
ii  vlc-plugin-qt3.0.3-1+b1
ii  vlc-plugin-video-output  3.0.3-1+b1

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.3-1
ii  vlc-plugin-notify  3.0.3-1+b1
ii  vlc-plugin-samba   3.0.3-1+b1
ii  vlc-plugin-skins2  3.0.3-1+b1
ii  vlc-plugin-video-splitter  3.0.3-1+b1
ii  vlc-plugin-visualization   3.0.3-1+b1

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.27-3
ii  libvlc5  3.0.3-1+b1

Versions of packages libvlc5 depends on:
ii  libc62.27-3
ii  libvlccore9  3.0.3-1+b1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.3-1+b1

Versions of packages vlc-bin depends on:
ii  libc6   2.27-3
ii  libvlc-bin  3.0.3-1+b1
ii  libvlc5 3.0.3-1+b1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-19
ii  libarchive13 3.2.2-4
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.1.6-1
ii  libass9  1:0.14.0-2
ii  libavahi-client3 0.7-4
ii  libavahi-common3 0.7-4
ii  libavc1394-0 0.5.4-5
ii  libavcodec57 7:3.4.2-2+b2
ii  libavformat577:3.4.2-2+b2
ii  libavutil55  7:3.4.2-2+b2
ii  libbasicusageenvironment12018.04.25-2
ii  libbluray2   1:1.0.2-3
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcddb2 1.3.2-6
ii  libchromaprint1  1.4.3-2
ii  libcrystalhd31:0.0~git20110715.fdd2f19-13
ii  libdbus-1-3  1.12.8-3
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.6-1
ii  libdvbpsi10  1.3.2-1
ii  libdvdnav4   6.0.0-1
ii  libdvdread4  6.0.0-1
ii  libebml4v5   1.3.6-2
ii  libfaad2 2.8.8-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libfribidi0  0.19.7-3
ii  libgcc1  1:8.1.0-9
ii  libgcrypt20  1.8.3-1
ii  libglib2.0-0 2.56.1-2
ii  libgnutls30  3.5.18-1
ii  libgpg-error01.31-1
ii  libgroupsock82018.04.25-2
ii  libharfbuzz0b1.8.1-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libkate1 0.4.1-8
ii  liblirc-client0  0.10.0-2+b1
ii  liblivemedia62   2018.04.25-2
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libmad0  0.15.1b-9
ii  libmatroska6v5   1.4.9-1
ii  libmicrodns0 0.0.10-1
ii  libmpcdec6   2:0.1~r495-1+b2
ii  libmpeg2-4   0.5.1-8
ii  libmpg123-0  1.25.10-2
ii  libmtp9  1.1.13-1
ii  libncursesw6 6.1+20180210-4
ii  libnfs11 2.0.0-1~exp1
ii  libogg0  1.3.2-1+b1
ii  libopenmpt-modplug1  0.3.10-1
ii  libopus0 

Bug#902117: [Debian-ha-maintainers] Bug#902117: corosync-qdevice will not daemonize/run

[Jason Gauthier]

On Fri, Jul 6, 2018 at 10:20 AM Valentin Vidic  wrote:
>
> On Fri, Jun 22, 2018 at 09:46:36AM -0400, Jason Gauthier wrote:
> > corosync-qdevice is a daemon that runs on each cluster node that help
> > provide a voting subsystem that utilizes corosync-qnet outside the
> > cluster.
> >
> > After installing the packages from debian stretch, and configuring the
> > application, it does not run.  One can use -d and -f to troubleshoot
> > issues, and even in this situation no data is logged to the console,
> > or any syslog messages generated.  The application immediately fails.
>
> corosync-qdevice is configured in corosync.conf, can you share the
> quorum block from there?
>
> If this is not configured I get the following error:
>
> Jul  6 16:08:08 node1 corosync-qdevice[2778]: Can't read quorum.device.model 
> cmap key.
>
> But with a correct configuration it starts fine for me.
>

Interesting.  Let me make some notes.  First, on a 3rd node, I ran
corosync-qnetd, and if not setup then it gives you a nice bulleted
list to complete a certificate based set up.  I did that, and
corosync-qnetd is launched and active on a 3rd node.

Now, it's entirely possible that I do have a configuration issue
causing corosync-qdevice to not start.  However, the real issue is
that corosync-qdevice does not log anything to stdout when run with
"-f -d"  (foreground, debug).

So, if there is a configuration problem I cannot troubleshoot it.  If
I understand the issue correctly, this has something to do with libqb
and (perhaps) the way that it is built.

I grabbed the source code for corosync-qdevice and when I replaced the
logging functionality with a simple varargs based function I was able
to get some output and troubleshoot a little further.

Let me demonstrate:
root@alpha:/home/jgauthier# corosync-qdevice -f -d
root@alpha:/home/jgauthier#

This should result in some form of output.  (This would be a great
test as for you as well)

Now, all that aside, my quorum block looks like this:

quorum {
# Enable and configure quorum subsystem (default: off)
# see also corosync.conf.5 and votequorum.5
#  two_node: 1
provider: corosync_votequorum
expected_votes: 3
device {
votes: 1
model: net
net {
  host: delta
  }
}

delta is the host for corosync-qnetd.

Jason

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Sean Whitton]

Hello,

On Fri, Jul 06 2018, Eugen Dedu wrote:

> I confirm that the commit on salsa above makes ublock origin working
> with my firefox.

Thank you both for taking the time to test!

I can't upload the fix because it looks like there are missing source
problems:

E: ublock-origin source: source-is-missing src/js/hntrie.js line length is 
1357 characters (>512)
E: ublock-origin source: source-is-missing 
src/lib/codemirror/lib/codemirror.js line length is 1953 characters (>512)

I think the latter is a false positive, but unfortunately I do not have
time to dig into this.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#900533: Bug still exists

[Salvo Tomaselli]

Chromium works for me, both testing and unstable.

Il 06 Lug 2018 09:42, "Marco Fleckinger"  ha
scritto:

> As mentioned the bug still exists in chromium 67.0.3396.87 from the Debian
> Repo. I setup a totally fresh VM for this purpose running stretch.
>
> There I downloaded the source and compiled following the instructions at
> [1]. Upstream Chromium 69 worked fine so I tried to compile the exact same
> version as installed by APT on my notebook 67.0.3396.87 including [2] into
> my workflow.
>
> The 67.0.3396.87 version from upstream didn't have the issue. For testing
> I used a plain mp3 served by python's SimpleHTTPServer:
>
>   python -m SimpleHTTPServer
>
> First I always had the sandbox issue, I could start the upstream-versions
> only with --no-sandbox. Afterwards I tried to also compile the sandbox and
> start chromium using the wrapper. But this should not be relevant here
>
> Then I found out that the error also occurs when I used the Debian Package
> on my dedicated VM. After runnig it via CLI I also got this Error Message:
>
> [2693:2708:0705/212253.877035:ERROR:render_media_log.cc(30)] MediaEvent:
> MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
> [2693:2693:0705/212253.877203:ERROR:render_media_log.cc(30)] MediaEvent:
> PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
>
> [1] https://github.com/chromium/chromium/blob/master/docs/README.md
> [2] https://www.chromium.org/developers/how-tos/get-the-code/
> working-with-release-branches
> [3] https://unix.stackexchange.com/questions/68832/what-does-the
> -chromium-option-no-sandbox-mean#answer-105126
>
> Marco
>
> --
> To unsubscribe, send mail to 900533-unsubscr...@bugs.debian.org.
>

Bug#900533: Bug still exists

[Salvo Tomaselli]

Chromium works for me, both testing and unstable.

Il 06 Lug 2018 09:42, "Marco Fleckinger"  ha
scritto:

> As mentioned the bug still exists in chromium 67.0.3396.87 from the Debian
> Repo. I setup a totally fresh VM for this purpose running stretch.
>
> There I downloaded the source and compiled following the instructions at
> [1]. Upstream Chromium 69 worked fine so I tried to compile the exact same
> version as installed by APT on my notebook 67.0.3396.87 including [2] into
> my workflow.
>
> The 67.0.3396.87 version from upstream didn't have the issue. For testing
> I used a plain mp3 served by python's SimpleHTTPServer:
>
>   python -m SimpleHTTPServer
>
> First I always had the sandbox issue, I could start the upstream-versions
> only with --no-sandbox. Afterwards I tried to also compile the sandbox and
> start chromium using the wrapper. But this should not be relevant here
>
> Then I found out that the error also occurs when I used the Debian Package
> on my dedicated VM. After runnig it via CLI I also got this Error Message:
>
> [2693:2708:0705/212253.877035:ERROR:render_media_log.cc(30)] MediaEvent:
> MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
> [2693:2693:0705/212253.877203:ERROR:render_media_log.cc(30)] MediaEvent:
> PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
>
> [1] https://github.com/chromium/chromium/blob/master/docs/README.md
> [2] https://www.chromium.org/developers/how-tos/get-the-code/
> working-with-release-branches
> [3] https://unix.stackexchange.com/questions/68832/what-does-the
> -chromium-option-no-sandbox-mean#answer-105126
>
> Marco
>
> --
> To unsubscribe, send mail to 900533-unsubscr...@bugs.debian.org.
>

Bug#903133: marked as done (debhelper: unable to build get-flash-videos)

[Debian Bug Tracking System]

Your message dated Fri, 6 Jul 2018 20:35:47 +0200
with message-id <20180706183547.zlktcgs5y5ewbik4@nuc>
and subject line Re: Bug#903133: debhelper: unable to build get-flash-videos
has caused the Debian Bug report #903133,
regarding debhelper: unable to build get-flash-videos
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.)


-- 
903133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.3.5
Severity: serious

Hello Niels.

I am still unable to build some packages with this version of debhelper.

For example, I got this in get-flash-videos_1.25.99-1, a package which
used to build ok in the past:

Installing 
/<>/debian/get-flash-videos/usr/share/man/man1/get_flash_videos.1p
Installing /<>/debian/get-flash-videos/usr/bin/get_flash_videos
make[1]: Leaving directory '/<>'
   dh_installdocs -i
   dh_installdocs: Cannot find (any matches for) "README" (tried in .)
   
   debian/rules:22: recipe for target 'binary-indep' failed
   make: *** [binary-indep] Error 2
   dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A", in case it matters.


As before, please confirm if this is a bug in debhelper or maybe I
should reassign it to the get-flash-videos package.

Thanks.
--- End Message ---
--- Begin Message ---
On Fri, Jul 06, 2018 at 06:20:00PM +, Niels Thykier wrote:

> At first glance, this looks like the deliberate change to restore the
> level of checks that were done in debhelper in stable.  Please see:
> 
>  * #902355
>  * #902767 #10
> 
> (the original behaviour was to fail on non-globs that matched nothing
> but silently accept globs that matched nothing and the given cases seems
> to both fail on non-globs)
> 
> > [...]
> > 
> > The build was made with "dpkg-buildpackage -A", in case it matters.
> > 
> > 
> > As before, please confirm if this is a bug in debhelper or maybe I
> > should reassign it to the get-flash-videos package.
> > 
> > Thanks.
> > 
> 
> As implied by the above, I would say this is a bug in get-flash-videos
> and asciidoc.

And more to come...

Thanks a lot, I'll file individual bugs instead (I prefer not to reassign this 
one).--- End Message ---

Bug#903133: debhelper: unable to build get-flash-videos

[Niels Thykier]

Control: tags -1 moreinfo

Santiago Vila:
> Package: debhelper
> Version: 11.3.5
> Severity: serious
> 
> Hello Niels.
> 

Hi,

> I am still unable to build some packages with this version of debhelper.
> 
> For example, I got this in get-flash-videos_1.25.99-1, a package which
> used to build ok in the past:
> 
> Installing 
> /<>/debian/get-flash-videos/usr/share/man/man1/get_flash_videos.1p
> Installing /<>/debian/get-flash-videos/usr/bin/get_flash_videos
> make[1]: Leaving directory '/<>'
>dh_installdocs -i
>dh_installdocs: Cannot find (any matches for) "README" (tried in .)
>  

At first glance, this looks like the deliberate change to restore the
level of checks that were done in debhelper in stable.  Please see:

 * #902355
 * #902767 #10

(the original behaviour was to fail on non-globs that matched nothing
but silently accept globs that matched nothing and the given cases seems
to both fail on non-globs)

> [...]
> 
> The build was made with "dpkg-buildpackage -A", in case it matters.
> 
> 
> As before, please confirm if this is a bug in debhelper or maybe I
> should reassign it to the get-flash-videos package.
> 
> Thanks.
> 

As implied by the above, I would say this is a bug in get-flash-videos
and asciidoc.

Thanks,
~Niels

Processed: Re: Bug#903133: debhelper: unable to build get-flash-videos

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #903133 [debhelper] debhelper: unable to build get-flash-videos
Added tag(s) moreinfo.

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

Bug#902290: Too abrupt removal of configuration option in stable update

[Hans van Kranenburg]

Hi Sebastian,

On 07/04/2018 10:21 PM, Sebastian Andrzej Siewior wrote:
> 
> On 2018-07-04 14:06:54 [+0200], To Hans van Kranenburg wrote:
>> On 2018-06-24 17:12:19 [+0200], Hans van Kranenburg wrote:
>>> My mailserver logs now contain 'ERROR: Parse error at line 74: Unknown
>>> option StatsHostID', and when that's removed, it reports the next option
>>> that is removed, 'StatsPEDisabled', and so on.
>> …
>>> Or, alternatively when throwing newer versions in stable, they have to
>>> be closely inspected to detect options that are removed and get patches
>>> like you did for #826406.
>>
>> I'm sorry. I've seen the removal of options and I didn't think about
>> this. If handle the config file with debconf then the option should
>> vanish automaticaly. However if you edit the file manually then user's
>> input is required and if nothing happens then clamav will abort.
>>
>> I intend to address this to for deb9 and document this behaviour so I
>> will remember it next time. I have to figure out who is in charge of
>> deb8 and I *think* it is LTS by now.

Thanks!

I'll be upgrading this part of my infra to Stretch RSN, and also will
have a look at the config we write with puppet now, to see if I can
throw out as much as possible. But still, I'd like unattended to also
keep taking care of clamav updates in the future yes.

> so I added a fix [0] to the Stretch branch for this. It would be nice if
> you could have a look on the Stretch package in case something else is
> missing :)

Looks good. It would of course be even better if upstream did something
like this, but I suspect there's a bit of a "you should always just run
latest" culture at clamav, also given the fact that you have to ship new
versions as security updates.

> With this change you should see something like
> | Jul 04 22:14:08 deb9amd64 clamd[8720]: WARNING: Ignoring deprecated option 
> StatsTimeout at line 88
> | Jul 04 22:14:08 deb9amd64 clamd[8720]: WARNING: Ignoring deprecated option 
> StatsPEDisabled at line 89
> 
> and move on.

\o/

> Now Jessie. It would be nice if the LTS team could pick it up. On the
> other hand the point-release exposed the problem and everyone had to
> deal with it…

-- 
Hans van Kranenburg

Bug#902709: diffoscope: test failures everywhere

[Mattia Rizzolo]

On Fri, Jul 6, 2018 at 7:50 PM Chris Lamb  wrote:
> > I'll take care of it once I can debug the other 4 errors (tbh, I didn't
> > try to reproduce them locally).
>
> Did you manage to get to this?

I tried to reproduce them locally (also jenkins doesn't hit them), but
failed to and after some tries my allocated time finished.

> Are we even still seeing them? :-)

Alas yes, see the failures in
https://salsa.debian.org/reproducible-builds/diffoscope/pipelines/12501
(I believe you also receive emails for those?)

But as I said I'm totally unable to reproduce them, so I'm thinking
tomorrow to fix up some other things and release nonetheless,
hopefully somebody can look at GitLab CI at another time.

-- 
regards,
Mattia Rizzolo

GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo

Bug#900533: Bug still exists in Chromium 67.0.3396.87

[Robert.K.]

I can confirm the same. YouTube works, but many other sites with audio and
or video that worked before does not.

$ chromium --version
Chromium 67.0.3396.87 built on Debian 9.4, running on Debian 9.4

$ chromium "https://www.dailymotion.com/video/x6nlrix;
ATTENTION: default value of option force_s3tc_enable overridden by
environment.
[4:128:0706/195034.954738:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195034.954952:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN

Pressing the play button on the page:
[4:128:0706/195128.624626:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195128.625194:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN

$ chromium "https://hpr.dogphilosophy.net/test/;
ATTENTION: default value of option force_s3tc_enable overridden by
environment.
[4:96:0706/195227.133129:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.133447:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[4:96:0706/195227.149896:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.150103:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[4:96:0706/195227.162579:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.180222:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[4:96:0706/195227.215345:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.215853:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[4:96:0706/195227.234175:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.234419:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[4:96:0706/195227.252414:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.252619:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[4:96:0706/195227.274421:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[4:4:0706/195227.276481:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN

Best regards,
Robert

Bug#902709: diffoscope: test failures everywhere

[Chris Lamb]

Hi Mattia,

> I'll take care of it once I can debug the other 4 errors (tbh, I didn't
> try to reproduce them locally).

Did you manage to get to this? Are we even still seeing them? :-)


Regards,

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 897390 = moreinfo
Bug #897390 [xwayland] xwayland: Segmentation fault loading GNOME 3
Added tag(s) moreinfo; removed tag(s) patch.
> tags 898553 = patch
Bug #898553 [grub-legacy] grub-legacy 0.97-73 segfaults
Added tag(s) patch.
> quit
Stopping processing here.

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

Processed: Re: grub-legacy 0.97-73 segfaults

[Debian Bug Tracking System]

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

> tags 897390 = patch
Bug #897390 [xwayland] xwayland: Segmentation fault loading GNOME 3
Added tag(s) patch; removed tag(s) moreinfo.
> quit
Stopping processing here.

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

Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-2

[Santiago Vila]

found 902466 1.2.0-2
thanks

Hello Dmitry.

I assume this will be frustrating for you as maintainer, but believe
me that it's also frustrating for me as reporter.

I've built today version 1.2.0-2 ten times in four different autobuilders,
and it failed ten times. Build logs available here:

https://people.debian.org/~sanvila/build-logs/golang-github-grpc-ecosystem-go-grpc-prometheus/

Additionally, it still fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/golang-github-grpc-ecosystem-go-grpc-prometheus_1.2.0-2.rbuild.log.gz

I would say that whatever you did to solve this problem is not working.

I see that the issue was already in github:

https://github.com/grpc-ecosystem/go-grpc-prometheus/pull/44


May I suggest that you just disable the failing tests until they are
fixed upstream?

Thanks.

Processed: Re: Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-2

[Debian Bug Tracking System]

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

> found 902466 1.2.0-2
Bug #902466 {Done: Dmitry Smirnov } 
[src:golang-github-grpc-ecosystem-go-grpc-prometheus] 
golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing 
tests)
Marked as found in versions 
golang-github-grpc-ecosystem-go-grpc-prometheus/1.2.0-2; no longer marked as 
fixed in versions golang-github-grpc-ecosystem-go-grpc-prometheus/1.2.0-2 and 
reopened.
> thanks
Stopping processing here.

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

Bug#899998: Problem solved with latest package

[Jaap Keuter]

Hi,

Just installed the new package and rebooted the machine. Now I have a working
Xserver with latest (testing) kernel.

Linux janus 4.16.0-2-amd64 #1 SMP Debian 4.16.16-2 (2018-06-22) x86_64 GNU/Linux

Package: nvidia-legacy-340xx-kernel-dkms
Status: install ok installed
Priority: optional
Section: non-free/kernel
Installed-Size: 15355
Maintainer: Debian NVIDIA Maintainers 
Architecture: amd64
Multi-Arch: foreign
Source: nvidia-graphics-drivers-legacy-340xx
Version: 340.107-2


The only remaining reports in /var/log/messages are:
Jul  6 18:37:26 janus kernel: [   40.595166] resource sanity check: requesting
[mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem
0x000d-0x000d window]
Jul  6 18:37:26 janus kernel: [   40.595293] caller _nv000788rm+0xe4/0x1c0
[nvidia] mapping multiple BARs


Thanks for the support,
Jaap

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Daniel Baumann]

On 07/06/2018 04:19 PM, Sean Whitton wrote:
>> would you mind the fix?

(i ment 'woudl you mind uploading the fix', sorry for the typo)

> That is a fix for a different bug.  I didn't upload it because this bug
> is still present, making the package useless.  Or is this bug no longer
> reproducible?

the mentioned commit makes the package work again with firefox, fixing
#899365.

Regards,
Daniel

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Eugen Dedu]

On 06/07/18 16:19, Sean Whitton wrote:

Hello Daniel,

On Fri, Jul 06 2018, Daniel Baumann wrote:


I've looked at the git repository on salsa, and your last commit:

https://salsa.debian.org/daniel-guest/ublock-origin/commit/0b9e4452552ce6243ae088a7880ef4d67c82d5f8

fixes this for sid (provided one has fonts-font-awesome 4.x which got
recently re-uploaded; it works flawlessly but doesn't display icons in
the popup when using fonts-font-awesome 5.x).

would you mind the fix?


That is a fix for a different bug.  I didn't upload it because this bug
is still present, making the package useless.  Or is this bug no longer
reproducible?


I confirm that the commit on salsa above makes ublock origin working 
with my firefox.


--
Eugen

Bug#903133: debhelper: unable to build get-flash-videos

[Santiago Vila]

Other packages affected:


asciidoc_8.6.10-2:

make[1]: Leaving directory '/<>'
   dh_installdocs -i
   dh_installdocs: Cannot find (any matches for) "README" (tried in .)
   
   debian/rules:7: recipe for target 'binary-indep' failed
   make: *** [binary-indep] Error 2
   dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


ruby-sham-rack_1.4.1-1:

   dh_installdocs -i -O--buildsystem=ruby
   dh_installdocs: Cannot find (any matches for) "README.markdown" (tried in .)

debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep
subprocess returned exit status 2


Thanks.

Bug#869994: marked as done (sql-ledger: Can't locate bin/mozilla/login.pl in @INC)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 16:04:26 +
with message-id 
and subject line Bug#869994: fixed in sql-ledger 3.2.6-1
has caused the Debian Bug report #869994,
regarding sql-ledger: Can't locate bin/mozilla/login.pl in @INC
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.)


-- 
869994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl
Version: 5.26.0-4
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

The perl 5.26 update on 26th July disabled the file /etc/perl/sitecustomize.pl
.
There were no problems with perl 5.24.

I can no longer access my postgressql database using any web browser for the
sql-ledger 3.2.4 package.
I just get the Internal Server Error - "The server encountered an internal
error or misconfiguration and was unable to complete your request"
Previous remedies included disabling the only line of command in the
sitecustomize.pl file

I have tried re-enabling the sitecustomize.pl file, followed by restarting the
apache2 and postgresql services (separate commands)  each time after making the
code in the file active or disabled. On all occasions the browser shows the
Internal Server Error message.

I can access postgres using the terminal (command line) and using pgAdmin3,
phpPgAdmin.
Apache2 works as I can access other packages through localhost.

When trying to open my postgres database using my web browser (epiphany-
browser) and see the Internal Server Error - I attach below the relevant part
of the apache2/error.log for this action -


[Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] End
of script output before headers: admin.pl
[Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
119.: /usr/local/sql-ledger/login.pl
[Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] End
of script output before headers: login.pl

Looking at the above error text, my system (testing with daily updates) does
not have /usr/local/share/perl nor /usr/local/lib/site_perl.
I created a soft link to /usr/share/perl in /usr/local/share - restarted
apache2 & postgresql services = problem not fixed.

There is no directory site_perl on my system, so I cannot create the
appropriate link.


I trust the above is helpful to identify the problem with the @INC feature
Please accept my apologies for any expected information normally submitted with
a bug report (my first time)
If you require any other information, please let me know

Neil




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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 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)

Versions of packages perl depends on:
ii  dpkg   1.18.24
ii  libperl5.265.26.0-4
ii  perl-base  5.26.0-4
ii  perl-modules-5.26  5.26.0-4

Versions of packages perl recommends:
ii  netbase  5.4
ii  rename   0.20-4

Versions of packages perl suggests:
ii  libterm-readline-gnu-perl   1.35-1+b2
ii  libterm-readline-perl-perl  1.0303-1
ii  make4.1-9.1
ii  perl-doc5.26.0-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sql-ledger
Source-Version: 3.2.6-1

We believe that the bug you reported is fixed in the latest version of
sql-ledger, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert James Clay  (supplier of updated sql-ledger 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)

Bug#903133: debhelper: unable to build get-flash-videos

[Santiago Vila]

Package: debhelper
Version: 11.3.5
Severity: serious

Hello Niels.

I am still unable to build some packages with this version of debhelper.

For example, I got this in get-flash-videos_1.25.99-1, a package which
used to build ok in the past:

Installing 
/<>/debian/get-flash-videos/usr/share/man/man1/get_flash_videos.1p
Installing /<>/debian/get-flash-videos/usr/bin/get_flash_videos
make[1]: Leaving directory '/<>'
   dh_installdocs -i
   dh_installdocs: Cannot find (any matches for) "README" (tried in .)
   
   debian/rules:22: recipe for target 'binary-indep' failed
   make: *** [binary-indep] Error 2
   dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A", in case it matters.


As before, please confirm if this is a bug in debhelper or maybe I
should reassign it to the get-flash-videos package.

Thanks.

Processed: unicode-data: unicode-data 11 causes FTBFS in unstable

[Debian Bug Tracking System]

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

> affects 903129 fonttools
Bug #903129 [src:unicode-data] unicode-data: unicode-data 11 causes FTBFS in 
unstable
Added indication that 903129 affects fonttools
> thanks
Stopping processing here.

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

Bug#903118: [Pkg-rust-maintainers] Bug#903118: rustc: FTBFS in stretch (no cargo executable found)

[Ximin Luo]

Santiago Vila:
> [..]
> Exception: no cargo executable found at `/usr/bin/cargo`
> debian/rules:216: recipe for target 'override_dh_auto_build-indep' failed
> make[1]: *** [override_dh_auto_build-indep] Error 1
> make[1]: Leaving directory '/<>/rustc-1.24.1+dfsg1'
> debian/rules:143: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 
> 
> I did "dpkg-buildpackage -A" but apparently it also fails with 
> "dpkg-buildpackage -B"
> in every other architecture:
> 

Moritz,

The easiest way to fix all of the above would be to re-introduce the 
cargo/rustc self-Build-Depends but add a [!amd64] architecture-specific 
annotation to it. Then an arch:all build and the other-architecture builds will 
simply be not performed due to "missing build-deps".

This is what `d/rules source_orig-dl` suggests and I should have been more 
strict about it when reviewing your earlier patch, sorry.

If you need to bootstrap other architectures you can cross-compile them using 
`sbuild --host=$foreign-arch` although this was broken in upstream 1.25 [1] but 
may work on 1.24.

X

[1] https://github.com/rust-lang/rust/issues/49677

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

Processed: unicode-data: unicode-data 11 causes FTBFS in unstable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 gucharmap libxmlada utf8proc wine wine-development
Bug #903129 [src:unicode-data] unicode-data: unicode-data 11 causes FTBFS in 
unstable
Added indication that 903129 affects gucharmap, libxmlada, utf8proc, wine, and 
wine-development

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

Bug#903129: unicode-data: unicode-data 11 causes FTBFS in unstable

[Graham Inggs]

Source: unicode-data
Version: 11.0.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 gucharmap libxmlada utf8proc wine wine-development

Hi Maintainer

The recent upload of unicode-data 11 causes several packages to FTBFS in 
unstable.  This bug is to prevent the migration of unicode-data to 
testing until its reverse build-dependencies have had a chance to adapt.


Regards
Graham

Bug#902290: marked as done (Too abrupt removal of configuration option in stable update)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 14:32:09 +
with message-id 
and subject line Bug#902290: fixed in clamav 0.100.0+dfsg-0+deb9u2
has caused the Debian Bug report #902290,
regarding Too abrupt removal of configuration option in stable update
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.)


-- 
902290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav-daemon
Version: 0.100.0+dfsg-0+deb8u1
Severity: serious

Hi,

"Tonight on 'It's the Mind', we examine the phenomenon of deja vu. That
strange feeling we sometimes get that we've lived through something
before, that what is happening now has already happened. Tonight on
'It's the Mind' we examine the phenomenon of deja vu, that strange
feeling we sometimes get that we've ... (looks puzzled for a moment)
Anyway, tonight on 'It's the Mind' we examine the phenomenon of deja vu,
that strange..." (Monty Python)

I had a deja vu today. See #826406. The stable update of clamav
installed by unattended last night again broke production mail servers.

My mailserver logs now contain 'ERROR: Parse error at line 74: Unknown
option StatsHostID', and when that's removed, it reports the next option
that is removed, 'StatsPEDisabled', and so on.

Clamav really has to change handling removed configuration parameters
into warnings or something, instead of refusing to start at all. The
current behaviour just makes no sense.

Or, alternatively when throwing newer versions in stable, they have to
be closely inspected to detect options that are removed and get patches
like you did for #826406.

I will as well inspect the config file I use to see if I can get rid of
options that have default value or are not critical, to lower the risk
of this happening again.

Thanks,

-- 
Hans van Kranenburg
--- End Message ---
--- Begin Message ---
Source: clamav
Source-Version: 0.100.0+dfsg-0+deb9u2

We believe that the bug you reported is fixed in the latest version of
clamav, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated clamav 
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: Wed, 04 Jul 2018 23:14:43 +0200
Source: clamav
Binary: clamav-base clamav-docs clamav libclamav-dev libclamav7 clamav-daemon 
clamdscan clamav-testfiles clamav-freshclam clamav-milter
Architecture: source
Version: 0.100.0+dfsg-0+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Description:
 clamav - anti-virus utility for Unix - command-line interface
 clamav-base - anti-virus utility for Unix - base package
 clamav-daemon - anti-virus utility for Unix - scanner daemon
 clamav-docs - anti-virus utility for Unix - documentation
 clamav-freshclam - anti-virus utility for Unix - virus database update utility
 clamav-milter - anti-virus utility for Unix - sendmail integration
 clamav-testfiles - anti-virus utility for Unix - test files
 clamdscan  - anti-virus utility for Unix - scanner client
 libclamav-dev - anti-virus utility for Unix - development files
 libclamav7 - anti-virus utility for Unix - library
Closes: 902290
Changes:
 clamav (0.100.0+dfsg-0+deb9u2) stretch; urgency=medium
 .
   * Don't fail on recently removed config options (Closes: #902290).
Checksums-Sha1:
 0dec8872b4757af7dc68d1353f6c35c3fc00b817 3067 clamav_0.100.0+dfsg-0+deb9u2.dsc
 a11c9078278b4ddad70c7119adb7927263912555 217640 
clamav_0.100.0+dfsg-0+deb9u2.debian.tar.xz
 b2a35dc5f60c775603daa01da9c5e779bcb30ee5 6815 
clamav_0.100.0+dfsg-0+deb9u2_source.buildinfo
Checksums-Sha256:
 34eb6cdb8a618da644342861af739850e09699a3d882f20bf38bf8e779527eea 3067 
clamav_0.100.0+dfsg-0+deb9u2.dsc
 e0ba0c67d1f68d157ce9413568c5ee51924f8fdd5b2d2e00e7166f4453edf179 217640 
clamav_0.100.0+dfsg-0+deb9u2.debian.tar.xz
 b9efba9ba8e8935680f4107c909573a06cc16172e28ed5223a6a2236244595ea 6815 
clamav_0.100.0+dfsg-0+deb9u2_source.buildinfo
Files:
 b149cbc9a9e69e157304322410df1877 3067 utils optional 

Bug#897523: marked as done (check-postgres: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 14:32:09 +
with message-id 
and subject line Bug#897523: fixed in check-postgres 2.22.0-2+deb9u1
has caused the Debian Bug report #897523,
regarding check-postgres: FTBFS: tests failed
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.)


-- 
897523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: check-postgres
Version: 2.23.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00_basic.t ... ok
> t/00_release.t . skipped: Test skipped unless environment 
> variable RELEASE_TESTING is set
> t/00_signature.t ... skipped: Test skipped unless environment 
> variable RELEASE_TESTING is set
> t/00_test_tester.t . skipped: Test skipped unless environment 
> variable RELEASE_TESTING is set
> t/01_validate_range.t .. ok
> # Creating database in directory "test_database_check_postgres"
> Creating new symlink socket at /tmp/cptesting_socket
> t/02_autovac_freeze.t .. ok
> t/02_backends.t  ok
> t/02_bloat.t ... ok
> t/02_checkpoint.t .. ok
> t/02_cluster_id.t .. ok
> t/02_commitratio.t . ok
> t/02_connection.t .. ok
> t/02_custom_query.t  ok
> t/02_database_size.t ... ok
> t/02_dbstats.t . ok
> t/02_disabled_triggers.t ... ok
> t/02_disk_space.t .. ok
> t/02_fsm_pages.t ... ok
> t/02_fsm_relations.t ... ok
> t/02_hitratio.t  ok
> t/02_last_analyze.t  ok
> t/02_last_vacuum.t . ok
> t/02_listener.t  ok
> t/02_locks.t ... ok
> t/02_logfile.t . ok
> t/02_new_version_bc.t .. skipped: Skipped because environment variable 
> SKIP_NETWORK_TESTS is set
> t/02_new_version_box.t . skipped: Skipped because environment variable 
> SKIP_NETWORK_TESTS is set
> t/02_new_version_cp.t .. skipped: Skipped because environment variable 
> SKIP_NETWORK_TESTS is set
> t/02_new_version_pg.t .. skipped: Skipped because environment variable 
> SKIP_NETWORK_TESTS is set
> t/02_new_version_tnm.t . skipped: Skipped because environment variable 
> SKIP_NETWORK_TESTS is set
> NOTICE:  schema "pgagent" does not exist, skipping
> NOTICE:  drop cascades to 4 other objects
> DETAIL:  drop cascades to table pgagent.pga_job
> drop cascades to table pgagent.pga_jobstep
> drop cascades to table pgagent.pga_joblog
> drop cascades to table pgagent.pga_jobsteplog
> t/02_pgagent_jobs.t  ok
> t/02_pgbouncer_checksum.t .. ok
> t/02_prepared_txns.t ... ok
> t/02_query_runtime.t ... ok
> t/02_query_time.t .. ok
> t/02_relation_size.t ... ok
> t/02_replicate_row.t ... ok
> # Connected as 5432:/tmp/cptesting_socket:postgres
> t/02_replication_slots.t ... ok
> # Creating database in directory "test_database_check_postgres2"
> Creating new symlink socket at /tmp/cptesting_socket2
> # Creating database in directory "test_database_check_postgres3"
> Creating new symlink socket at /tmp/cptesting_socket3
> NOTICE:  language "plperlu" does not exist, skipping
> 
> #   Failed test 'Action 'same_schema' reports index 'unique' differences'
> #   at t/02_same_schema.t line 621.
> #   'POSTGRES_SAME_SCHEMA CRITICAL: DB "postgres" 
> (hosts:/tmp/cptesting_socket,/tmp/cptesting_socket2) Databases were 
> different. Items not matched: 1 | time=0.28s 
> # DB 1: dbservice= port=5432 host=/tmp/cptesting_socket dbname=postgres 
> user=check_postgres_testing 
> # DB 1: PG version: 10.3
> # DB 1: Total objects: 21
> # DB 2: dbservice= port=5432 host=/tmp/cptesting_socket2 dbname=postgres 
> user=check_postgres_testing 
> # DB 2: PG version: 10.3
> # DB 2: Total objects: 21
> # Index "public.valen":
> #  "indexdef" is different:
> # Database 1: CREATE INDEX valen ON public.gkar USING btree (garibaldi)
> # Database 2: CREATE UNIQUE INDEX valen ON public.gkar USING btree 
> (garibaldi)
> #  "indisunique" is different:
> # Database 1: f
> # Database 2: t
> #  
> # '
> # doesn't match '(?^s:^POSTGRES_SAME_SCHEMA CRITICAL.*Items not matched: 
> 1 .*
> # \s*Index "public.valen":

Bug#902117: [Debian-ha-maintainers] Bug#902117: corosync-qdevice will not daemonize/run

[Valentin Vidic]

On Fri, Jun 22, 2018 at 09:46:36AM -0400, Jason Gauthier wrote:
> corosync-qdevice is a daemon that runs on each cluster node that help
> provide a voting subsystem that utilizes corosync-qnet outside the
> cluster.
> 
> After installing the packages from debian stretch, and configuring the
> application, it does not run.  One can use -d and -f to troubleshoot
> issues, and even in this situation no data is logged to the console,
> or any syslog messages generated.  The application immediately fails.

corosync-qdevice is configured in corosync.conf, can you share the
quorum block from there?

If this is not configured I get the following error:

Jul  6 16:08:08 node1 corosync-qdevice[2778]: Can't read quorum.device.model 
cmap key.

But with a correct configuration it starts fine for me.

-- 
Valentin

Processed: Re: abinit: FTBFS on mips64el: test failures

[Debian Bug Tracking System]

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

> found 883974 8.0.8-1
Bug #883974 [src:abinit] abinit: FTBFS on mips64el: test failures
Marked as found in versions abinit/8.0.8-1.
> thanks
Stopping processing here.

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

Bug#883974: abinit: FTBFS on mips64el: test failures

[Santiago Vila]

found 883974 8.0.8-1
thanks

On Sat, 9 Dec 2017, Andreas Beckmann wrote:

> Source: abinit
> Version: 8.0.8-4
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> abinit FTBFS on mips64el:
> 
> https://buildd.debian.org/status/fetch.php?pkg=abinit=mips64el=8.0.8-4=1511985974=0

The same error happens now in stretch on amd64:

https://tests.reproducible-builds.org/debian/rbuild/stretch/amd64/abinit_8.0.8-1.rbuild.log.gz

Thanks.

Processed: limit source to haskell-raaz, tagging 903111

[Debian Bug Tracking System]

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

> limit source haskell-raaz
Limiting to bugs with field 'source' containing at least one of 'haskell-raaz'
Limit currently set to 'source':'haskell-raaz'

> tags 903111 + pending
Bug #903111 [haskell-raaz] haskell-raaz FTBFS in buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Sean Whitton]

Hello Daniel,

On Fri, Jul 06 2018, Daniel Baumann wrote:

> I've looked at the git repository on salsa, and your last commit:
>
> https://salsa.debian.org/daniel-guest/ublock-origin/commit/0b9e4452552ce6243ae088a7880ef4d67c82d5f8
>
> fixes this for sid (provided one has fonts-font-awesome 4.x which got
> recently re-uploaded; it works flawlessly but doesn't display icons in
> the popup when using fonts-font-awesome 5.x).
>
> would you mind the fix?

That is a fix for a different bug.  I didn't upload it because this bug
is still present, making the package useless.  Or is this bug no longer
reproducible?

-- 
Sean Whitton

Bug#903124: libevent-rpc-perl: FTBFS in stretch (sbuild hangs, expired SSL certificate?)

[Santiago Vila]

On Fri, Jul 06, 2018 at 03:29:11PM +0200, gregor herrmann wrote:

> So the bug only affects 1.08-2 in stable and is caused by the expired
> certificate(s) in the package itself.
> 
> If we want to fix this in stretch, we probably have to just update
> t/ssl/. Or skip t/04.cnct-auth-ssl-verifypeer-wrongca.t (and maybe
> also t/04.cnct-auth-ssl-verifypeer.t).

Debian is like Las Vegas: "Packages in stretch must be buildable in stretch",
so yes, I definitely think we want to fix this in stretch.

Note: There is a point release planned for Saturday, July 14th, and
new uploads for stretch-proposed-updates will be frozen this weekend.

Thanks.

Bug#903064: curvedns FTBFS: update Build-Depends: ruby-ronn -> ronn

[Stéphane Neveu]

Hi,

Thanks for the report, the control file is updated.
Cheers.
Le jeu. 5 juil. 2018 à 20:45, Helmut Grohne  a écrit :
>
> Package: curvedns
> Version: 0.87-4
> Severity: serious
>
> Since ronn got split out of ruby-ronn, curvedns fails to build from
> source. It was not possible to have ruby-ronn temporarily depend on
> ronn, because that would have created a dependency cycle. Please update
> Build-Depends and replace ruby-ronn with ronn as curvedns uses the
> command line tool.
>
> Helmut
>
>

Bug#903076: brutespray FTBFS: update Build-Depends: ruby-ronn -> ronn

[Stéphane Neveu]

Hi Helmut,

Thanks for the report, the control file is updated.
Cheers.
Le jeu. 5 juil. 2018 à 20:46, Helmut Grohne  a écrit :
>
> Source: brutespray
> Version: 1.6.0-1
> Severity: serious
>
> Since ronn got split out of ruby-ronn, brutespray fails to build from
> source. It was not possible to have ruby-ronn temporarily depend on
> ronn, because that would have created a dependency cycle. Please update
> Build-Depends and replace ruby-ronn with ronn as brutespray uses the
> command line tool.
>
> Helmut
>
>

Bug#902992: live-build broken due subversion recommends

[Luca Boccassi]

Control: severity -1 minor

On Fri, 2018-07-06 at 08:59 -0400, PICCORO McKAY Lenz wrote:
> pufff you dont understand! i called with "--apt-recommends false"
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com

Then the problem is not with "recommends", given they are not
installed.

What is _exactly_ the problem, and how do you reproduce it? Are you
sure you didn't set conflicting dependencies?

> 2018-07-05 8:00 GMT-04:00 Luca Boccassi :
> > On Wed, 4 Jul 2018 12:04:54 -0400 PICCORO McKAY Lenz  > gmai
> > l.com> wrote:
> > > Package: live-build
> > > Version: 1:20171207
> > > Severity: grave
> > > 
> > > we need a mechanish to avoid bad or abuse of recommends in apt,
> > > this
> > > problem avoit the automatization of the process
> > > 
> > > if we list the package subversion-tools, that recomends exim4
> > > over
> > 
> > any
> > > other, take preference to a specific package
> > > 
> > > root@pc-desk-w32:/vnx/osposos/debianlive8# aptitude why exim4
> > > i   subversion-tools Recomienda exim4 | mail-transport-agent
> > > 
> > > so then process end with this:
> > > 
> > > The following packages have unmet dependencies:
> > >  courier-mta : Conflicts: mail-transport-agent
> > >  exim4-config : Conflicts: courier-mta but 0.76.3-5 is to be
> > 
> > installed
> > >  exim4-daemon-light : Conflicts: mail-transport-agent
> > > 
> > > and lb build fails, with a only solution to make interactive
> > > shell
> > 
> > and
> > > avoiting automatization of the process
> > > 
> > > we need the mechanish due we cannot track all packages that abuse
> > > or
> > > are bad mantained due policy violations!
> > > 
> > > Lenz McKAY Gerardo (PICCORO)
> > > http://qgqlochekone.blogspot.com
> > 
> > There's already an option, call lb config with "--apt-recommends
> > false"
> > and recommends will not be installed.
> > 
> > --
> > Kind regards,
> > Luca Boccassi
> 
> 

-- 
Kind regards,
Luca Boccassi

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

Processed: Re: Bug#902992: live-build broken due subversion recommends

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #902992 [live-build] live-build broken due subversion recommends
Severity set to 'minor' from 'grave'

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

Bug#873088: marked as done (git-annex: remote code execution via crafted SSH URLs (CVE-2017-12976))

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 13:32:09 +
with message-id 
and subject line Bug#873088: fixed in git-annex 6.20170101-1+deb9u2
has caused the Debian Bug report #873088,
regarding git-annex: remote code execution via crafted SSH URLs (CVE-2017-12976)
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.)


-- 
873088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-annex
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for git-annex.

CVE-2017-12976[0]:
| git-annex before 6.20170818 allows remote attackers to execute
| arbitrary commands via an ssh URL with an initial dash character in the
| hostname, as demonstrated by an ssh://-eProxyCommand= URL, a related
| issue to CVE-2017-9800, CVE-2017-12836, CVE-2017-1000116, and
| CVE-2017-1000117.

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-2017-12976
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12976

Please adjust the affected versions in the BTS as needed.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: git-annex
Source-Version: 6.20170101-1+deb9u2

We believe that the bug you reported is fixed in the latest version of
git-annex, 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 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated git-annex 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, 22 Jun 2018 16:42:37 +0100
Source: git-annex
Binary: git-annex
Architecture: source
Version: 6.20170101-1+deb9u2
Distribution: stretch
Urgency: high
Maintainer: Richard Hartmann 
Changed-By: Sean Whitton 
Description:
 git-annex  - manage files with git, without checking their contents into git
Closes: 873088
Changes:
 git-annex (6.20170101-1+deb9u2) stretch; urgency=high
 .
   [ Joey Hess ]
   * CVE-2018-10857:
 - Added annex.security.allowed-url-schemes setting, which defaults
   to only allowing http, https, and ftp URLs. Note especially that file:/
   is no longer enabled by default.
 - Removed annex.web-download-command, since its interface does not allow
   supporting annex.security.allowed-url-schemes across redirects.
   If you used this setting, you may want to instead use annex.web-options
   to pass options to curl.
 - git-annex will refuse to download content from the web, to prevent
   accidental exposure of data on private webservers on localhost and the
   LAN. This can be overridden with the
   annex.security.allowed-http-addresses setting.
   (The S3, glacier, and webdav special remotes are still allowed to
   download from the web.)
   * CVE-2018-10857 and CVE-2018-10859:
 - Refuse to download content, that cannot be verified with a hash,
   from encrypted special remotes (for CVE-2018-10859),
   and from all external special remotes (for CVE-2018-10857).
   In particular, URL and WORM keys stored on such remotes won't
   be downloaded. If this affects your files, you can run
   `git-annex migrate` on the affected files, to convert them
   to use a hash.
 - Added annex.security.allow-unverified-downloads, which can override
   the above.
 .
 git-annex (6.20170101-1+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2017-12976: git-annex before 6.20170818 allows remote attackers to
 execute arbitrary commands via an ssh URL with an initial dash
 character in the hostname, as demonstrated by an ssh://-eProxyCommand=
 URL (Closes: #873088)
Checksums-Sha1:
 440c1251fbe20dbf443c6df5fe751ca44aab2887 5240 git-annex_6.20170101-1+deb9u2.dsc
 2645dcd551cc00c03a293187953445c506d17cd4 88536 
git-annex_6.20170101-1+deb9u2.debian.tar.xz
Checksums-Sha256:
 

Processed: Re: Bug#903124: libevent-rpc-perl: FTBFS in stretch (sbuild hangs, expired SSL certificate?)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed stretch
Bug #903124 [src:libevent-rpc-perl] libevent-rpc-perl: FTBFS in stretch (sbuild 
hangs, expired SSL certificate?)
Added tag(s) stretch and confirmed.
> fixed -1 1.09-1
Bug #903124 [src:libevent-rpc-perl] libevent-rpc-perl: FTBFS in stretch (sbuild 
hangs, expired SSL certificate?)
Marked as fixed in versions libevent-rpc-perl/1.09-1.
> retitle -1 libevent-rpc-perl: 1.08-2 FTBFS: expired SSL certificate
Bug #903124 [src:libevent-rpc-perl] libevent-rpc-perl: FTBFS in stretch (sbuild 
hangs, expired SSL certificate?)
Changed Bug title to 'libevent-rpc-perl: 1.08-2 FTBFS: expired SSL certificate' 
from 'libevent-rpc-perl: FTBFS in stretch (sbuild hangs, expired SSL 
certificate?)'.

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

Bug#903124: libevent-rpc-perl: FTBFS in stretch (sbuild hangs, expired SSL certificate?)

[gregor herrmann]

Control: tag -1 + confirmed stretch
Control: fixed -1 1.09-1
Control: retitle -1 libevent-rpc-perl: 1.08-2 FTBFS: expired SSL certificate

On Fri, 06 Jul 2018 12:57:43 +, Santiago Vila wrote:

> Package: src:libevent-rpc-perl
> Version: 1.08-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in stretch + security + stretch-proposed-updates
> but it failed:

> Can't open SSL connection to localhost:27816: SSL connect attempt failed 
> error:1416F086:SSL routines:tls_process_server_certificate:certificate verify 
> failed at t/04.cnct-auth-ssl-verifypeer-wrongca.t line 57.
> # Looks like you planned 5 tests but ran 2.
> # Looks like your test exited with 255 just after 2.
> E: Build killed with signal TERM after 60 minutes of inactivity
> 

Thanks for your bug report.

I can confirm the problem, 1.08-2 fails in a stable chroot (and also
in an unstable chroot). 1.09-1 passes in stable (and unstable), and
the upstream changelog for 1.09 says:

+Bugfixes:
+- SSL tests failed due to expired CA certificate.
+  Just created new certificates with 30 year
+  expiration and put a gen.sh script inside to
+  easily generate new certificates after that
+  period ;)

and the certs in /t/ssl/ are indeed renewed.


So the bug only affects 1.08-2 in stable and is caused by the expired
certificate(s) in the package itself.

If we want to fix this in stretch, we probably have to just update
t/ssl/. Or skip t/04.cnct-auth-ssl-verifypeer-wrongca.t (and maybe
also t/04.cnct-auth-ssl-verifypeer.t).


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: Supertramp: Some Things Never Change


signature.asc
Description: Digital Signature

Bug#903125: exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>)

[Santiago Vila]

Package: src:exec-maven-plugin
Version: 1.1.1+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch + security + stretch-proposed-updates
but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh 
/<>/exec-maven-plugin-1.1.1+dfsg/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibmaven-exec-plugin-java --debian-build --keep-pom-version 
--maven-repo=/<>/exec-maven-plugin-1.1.1+dfsg/debian/maven-repo  
--build-no-docs
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to check 
if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi

[... snipped ...]

testOverrides(org.codehaus.mojo.exec.ExecMojoTest)  Time elapsed: 0.043 sec  
<<< FAILURE!
junit.framework.ComparisonFailure: expected:<[mvn] -f pom.xml> but was:<['mvn'] 
-f pom.xml>
at junit.framework.Assert.assertEquals(Assert.java:81)
at junit.framework.Assert.assertEquals(Assert.java:87)
at org.codehaus.mojo.exec.ExecMojoTest.checkMojo(ExecMojoTest.java:371)
at 
org.codehaus.mojo.exec.ExecMojoTest.testOverrides(ExecMojoTest.java:331)

testOverrides3(org.codehaus.mojo.exec.ExecMojoTest)  Time elapsed: 0.035 sec  
<<< FAILURE!
junit.framework.ComparisonFailure: expected:<[mvn] --version> but was:<['mvn'] 
--version>
at junit.framework.Assert.assertEquals(Assert.java:81)
at junit.framework.Assert.assertEquals(Assert.java:87)
at org.codehaus.mojo.exec.ExecMojoTest.checkMojo(ExecMojoTest.java:371)
at 
org.codehaus.mojo.exec.ExecMojoTest.testOverrides3(ExecMojoTest.java:340)

Running org.codehaus.mojo.exec.ExecJavaMojoTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.241 sec - in 
org.codehaus.mojo.exec.ExecJavaMojoTest

Results :

Failed tests: 
  org.codehaus.mojo.exec.ExecMojoTest#testRunOK ComparisonFailure 
expected:<[mvn...
  org.codehaus.mojo.exec.ExecMojoTest#testRunFailure ComparisonFailure 
expected:...
  org.codehaus.mojo.exec.ExecMojoTest#testRunError ComparisonFailure 
expected:<[...
  org.codehaus.mojo.exec.ExecMojoTest#testOverrides ComparisonFailure 
expected:<...
  org.codehaus.mojo.exec.ExecMojoTest#testOverrides3 ComparisonFailure 
expected:...

Tests run: 14, Failures: 5, Errors: 0, Skipped: 0

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.291 s
[INFO] Finished at: 2018-07-06T13:15:30+00:00
[INFO] Final Memory: 19M/90M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project exec-maven-plugin: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/<>/exec-maven-plugin-1.1.1+dfsg/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
/usr/share/cdbs/1/class/maven.mk:127: recipe for target 
'debian/stamp-maven-check' failed
make: *** [debian/stamp-maven-check] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made with "dpkg-buildpackage -A" but I guess that's not
relevant at all in this case.

Apparently some build-dependency in security or stretch-proposed-updates
changed behaviour in a way that makes the tests to break, but I'm not
sure a reassign would be a good thing here.

Thanks.

Bug#903105: marked as done (nlopt: FTBFS with to octave 4.4.0)

[Debian Bug Tracking System]

Your message dated Fri, 6 Jul 2018 15:11:36 +0200
with message-id <20180706131136.ju2bedyodbskt...@an3as.eu>
and subject line Re: Bug#903105: nlopt: FTBFS with to octave 4.4.0
has caused the Debian Bug report #903105,
regarding nlopt: FTBFS with to octave 4.4.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.)


-- 
903105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nlopt
Severity: serious
Justification: FTBFS

Hi,

when I team uploaded nlopt on Tue, 29 May 2018 it was building fine.  At 
2018-06-09
octave 4.4.0-3 was uploaded to unstable.  When I build today the build fails 
with

...
/build/nlopt-2.4.2+dfsg/octave/nlopt_optimize-oct.cc:82:36: error: 'class 
octave_function' has no member named 'do_multi_index_op'; did you mean 
'do_index_op'?
   octave_value_list res = data->f->do_multi_index_op(gradient ? 2 : 1, args);
^
do_index_op
...

I wonder whether there is some upgrade path for this API change in octave.

Kind regards

   Andreas.



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

Kernel: Linux 4.9.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Fri, Jul 06, 2018 at 02:00:07PM +0200, Sébastien Villemot wrote:
> 
> I team-uploaded nlopt 2.4.2+dfsg-6 on 2018-06-11 with the relevant fixes, and
> it built fine against Octave 4.4. So I don't really understand your problem.
> Which version are you trying to build?

Agh, the git repository where I forgot to git pull ...

Closing the bug - sorry for the noise

  Andreas.


-- 
http://fam-tille.de--- End Message ---

Bug#902992: live-build broken due subversion recommends

[PICCORO McKAY Lenz]

pufff you dont understand! i called with "--apt-recommends false"
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com


2018-07-05 8:00 GMT-04:00 Luca Boccassi :
> On Wed, 4 Jul 2018 12:04:54 -0400 PICCORO McKAY Lenz  l.com> wrote:
>> Package: live-build
>> Version: 1:20171207
>> Severity: grave
>>
>> we need a mechanish to avoid bad or abuse of recommends in apt, this
>> problem avoit the automatization of the process
>>
>> if we list the package subversion-tools, that recomends exim4 over
> any
>> other, take preference to a specific package
>>
>> root@pc-desk-w32:/vnx/osposos/debianlive8# aptitude why exim4
>> i   subversion-tools Recomienda exim4 | mail-transport-agent
>>
>> so then process end with this:
>>
>> The following packages have unmet dependencies:
>>  courier-mta : Conflicts: mail-transport-agent
>>  exim4-config : Conflicts: courier-mta but 0.76.3-5 is to be
> installed
>>  exim4-daemon-light : Conflicts: mail-transport-agent
>>
>> and lb build fails, with a only solution to make interactive shell
> and
>> avoiting automatization of the process
>>
>> we need the mechanish due we cannot track all packages that abuse or
>> are bad mantained due policy violations!
>>
>> Lenz McKAY Gerardo (PICCORO)
>> http://qgqlochekone.blogspot.com
>
> There's already an option, call lb config with "--apt-recommends false"
> and recommends will not be installed.
>
> --
> Kind regards,
> Luca Boccassi

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Eugen Dedu]

On 06/07/18 14:26, Daniel Baumann wrote:

Hi Sean,

I've looked at the git repository on salsa, and your last commit:

https://salsa.debian.org/daniel-guest/ublock-origin/commit/0b9e4452552ce6243ae088a7880ef4d67c82d5f8

fixes this for sid (provided one has fonts-font-awesome 4.x which got
recently re-uploaded; it works flawlessly but doesn't display icons in
the popup when using fonts-font-awesome 5.x).

would you mind the fix?


What a beautiful day!  Finally, an Internet without ads again!  Thank 
you for the information!


(It did not worked after restarting firefox, no icon in the firefox's 
toolbar, I had to disable and enable the plugin too.)


--
Eugen

Bug#903124: libevent-rpc-perl: FTBFS in stretch (sbuild hangs, expired SSL certificate?)

[Santiago Vila]

Package: src:libevent-rpc-perl
Version: 1.08-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch + security + stretch-proposed-updates
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Event::RPC
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cp lib/Event/RPC/Message.pm blib/lib/Event/RPC/Message.pm
cp lib/Event/RPC/Loop/AnyEvent.pm blib/lib/Event/RPC/Loop/AnyEvent.pm
cp lib/Event/RPC/LogConnection.pm blib/lib/Event/RPC/LogConnection.pm
cp lib/Event/RPC/Connection.pm blib/lib/Event/RPC/Connection.pm
cp lib/Event/RPC/Loop/Event.pm blib/lib/Event/RPC/Loop/Event.pm
cp lib/Event/RPC/Message/SerialiserBase.pm 
blib/lib/Event/RPC/Message/SerialiserBase.pm
cp lib/Event/RPC/Logger.pm blib/lib/Event/RPC/Logger.pm
cp lib/Event/RPC/AuthPasswdHash.pm blib/lib/Event/RPC/AuthPasswdHash.pm
cp lib/Event/RPC/Message/Negotiate.pm blib/lib/Event/RPC/Message/Negotiate.pm
cp lib/Event/RPC/Message/CBOR.pm blib/lib/Event/RPC/Message/CBOR.pm
cp lib/Event/RPC/Message/JSON.pm blib/lib/Event/RPC/Message/JSON.pm
cp lib/Event/RPC/Server.pm blib/lib/Event/RPC/Server.pm
cp lib/Event/RPC.pm blib/lib/Event/RPC.pm
cp lib/Event/RPC/Loop/Glib.pm blib/lib/Event/RPC/Loop/Glib.pm
cp lib/Event/RPC/Loop.pm blib/lib/Event/RPC/Loop.pm
cp lib/Event/RPC/Message/Storable.pm blib/lib/Event/RPC/Message/Storable.pm
cp lib/Event/RPC/Client.pm blib/lib/Event/RPC/Client.pm
cp lib/Event/RPC/Message/Sereal.pm blib/lib/Event/RPC/Message/Sereal.pm
Manifying 17 pod documents
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
*Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
t/01.use.t ... 
1..2
ok 1 - use Event::RPC::Server;
ok 2 - use Event::RPC::Client;
ok
t/02.cnct.t .. 
1..5
ok 1 - use Event::RPC::Client;
ok 2 - connected
ok 3 - object created via RPC
ok 4 - client disconnected
ok 5 - stop server
ok
t/03.cnct-auth.t . 
1..6
ok 1 - use Event::RPC::Client;
ok 2 - connection failed with wrong pw
ok 3 - connected
ok 4 - object created via RPC
ok 5 - client disconnected
ok 6 - server stopped
ok
t/04.cnct-auth-ssl-verifypeer-noca.t . 
1..4
ok 1 - use Event::RPC::Client;
ok 2 - ssl connection failed due to unsigned server key
ok 3 - killing server process at PID 25781
ok 4 - server stopped
ok
Can't open SSL connection to localhost:27816: SSL connect attempt failed 
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify 
failed at t/04.cnct-auth-ssl-verifypeer-wrongca.t line 57.
# Looks like you planned 5 tests but ran 2.
# Looks like your test exited with 255 just after 2.
E: Build killed with signal TERM after 60 minutes of inactivity


A similar error happens here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libevent-rpc-perl.html

Waiting time is different in this case ("pbuilder was killed by timeout after 
24h")
but the end result is the same.

If this is really a bug in one of the build-depends and you have to
use "reassign", please use "affects" as well, so that this is still
visible in the BTS page for this package.

Thanks.

Bug#900629: marked as done (debian-edu-install: breaks installation of samba)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 12:49:35 +
with message-id 
and subject line Bug#900629: fixed in debian-edu-config 2.10.29
has caused the Debian Bug report #900629,
regarding debian-edu-install: breaks installation of samba
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.)


-- 
900629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-install
Version: 2.10.9
Severity: serious

Hi,

https://jenkins.debian.net/job/chroot-installation_sid_install_education-workstation/1236//console
breaks as follows:

first:

Setting up debian-edu-install (2.10.9) ...
error: /var/lib/dpkg/info/debian-edu-install.postinst: Unable to read
from /etc/debian-edu/config.
info: Loading defaults from /usr/lib/debian-edu-install/defaults.common
info: Got profile ''
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults

and then, second:

Setting up samba-common-bin (2:4.8.2+dfsg-1) ...
Checking smb.conf
WARNING: The "syslog" option is deprecated
netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
ERROR: Invalid smb.conf
dpkg: error processing package samba-common-bin (--configure):
 installed samba-common-bin package post-installation script subprocess
 returned error exit status 255


-- 
cheers,
Holger


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 2.10.29

We believe that the bug you reported is fixed in the latest version of
debian-edu-config, 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 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated debian-edu-config 
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, 06 Jul 2018 12:40:08 +
Source: debian-edu-config
Binary: debian-edu-config
Architecture: source
Version: 2.10.29
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Description:
 debian-edu-config - Configuration files for Skolelinux systems
Closes: 900629
Changes:
 debian-edu-config (2.10.29) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * Generate NetBIOS compliant hostname; this allows one to keep the hostname
 in case the MATE desktop is configured to use file sharing via Samba.
 Same applies if a roaming workstation is configured to connect to an
 active directory DC (via tools/setup-ad-client).
 Instead of e.g. 'auto-mac-11-22-33-44-55-66', now 'am-112233445566' is
 generated. (Closes: #900629).
Checksums-Sha1:
 1b4d87644b59d37ceac637c28c7f05be859910cb 1870 debian-edu-config_2.10.29.dsc
 5e78d69d47e95d9f70eb5be842a71d7a2646bdf1 338764 
debian-edu-config_2.10.29.tar.xz
 c48ceaeb7f451b2dbdfb7b45c9b4e2206c8a7957 5390 
debian-edu-config_2.10.29_source.buildinfo
Checksums-Sha256:
 3cf16085150f64958bd8f77d792635481b9b5f09e7a39813f57be3fdc1442969 1870 
debian-edu-config_2.10.29.dsc
 002e5d8eb60aa5e9d74f300def9268ff59f224a9ee5ef4ce3c3a397a84aa5355 338764 
debian-edu-config_2.10.29.tar.xz
 4e2233530ba3d463ee025975464d430e97066c1d6f3fdde482fc18dd5973cb09 5390 
debian-edu-config_2.10.29_source.buildinfo
Files:
 c4fd0a863524874389c514456124d5f5 1870 misc optional 
debian-edu-config_2.10.29.dsc
 98aa00ee9f743790d1f339e38de0dc58 338764 misc optional 
debian-edu-config_2.10.29.tar.xz
 1e6ac2295520d7e693a407056b8c5c7b 5390 misc optional 
debian-edu-config_2.10.29_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAls/Y3gACgkQCRq4Vgaa
qhwlrw//XCQsN933msJVEozoLQc4d5MNj36hwqB1p8MeJgH3NvNZZ/1aBeU4iUji
geebFrwAXEU8GnZNdYjjPlwvjjQ2LAVPn0OcLDpevI4ivUffn8FyX3mRq6pTbgwc
R2jaVV5Pj9UmXpAweHzyuoM3MBPTpS6h8kwW46yWFdVeUVmBRs6/va8SGtntw2MG
1KN0joKwE86vBhWH9Wf1iae7xMumy2Z3vS4UOCSKKAXsjm7sZ/OVNwtUjZkuM8kz
5Xosxfb8s1qZfmg6ZyOLfNM+NKKPzOnVWLOK0ns9TSAoOo/QGcCONanMe0YKiGSS
t5DgSxPD8VyJE9F+P0Fi+k+arUbJ0FREX9zgHmgpXJs6nj93p6jFM85o10bk7PNB
ypqjxxk3g/8o7ANya250/MC/nWV4JyK7LVFgpeSMnn5dKB+91HCQQaFMgcONIIxd

Bug#902941: marked as done (libuv1 1.21 broke ABI without SONAME bump)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 12:34:39 +
with message-id 
and subject line Bug#902941: fixed in libuv1 1.21.0-2
has caused the Debian Bug report #902941,
regarding libuv1 1.21 broke ABI without SONAME bump
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.)


-- 
902941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libuv1, lua-luv
Version: libuv1/1.21.0-1
Version: lua-luv/1.9.1-0-2
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of libuv1 the autopkgtest of lua-luv started to
fail in unstable and testing. I have copied the error below.

Currently this regression is delaying the migration of libuv1 to testing
by 13 days. Could you please investigate the situation and resolve which
package needs to be fixed and assign it?

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

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-luv/550804/log.gz

ok 9 fs - fs.scandir
  ./tests/test-fs.lua:83: UNKNOWN FS TYPE 29

  stack traceback:
[C]: in function 'assert'
./tests/test-fs.lua:83: in function 'fn'
./lib/tap.lua:53: in function <./lib/tap.lua:42>
[C]: in function 'xpcall'
./lib/tap.lua:42: in function 'run'
./lib/tap.lua:136: in function 'tap'
tests/run.lua:35: in main chunk
[C]: ?
not ok 10 fs - fs.realpath



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libuv1
Source-Version: 1.21.0-2

We believe that the bug you reported is fixed in the latest version of
libuv1, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated libuv1 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, 06 Jul 2018 13:57:44 +0200
Source: libuv1
Binary: libuv1-dev libuv1
Architecture: source
Version: 1.21.0-2
Distribution: unstable
Urgency: medium
Maintainer: Dominique Dumont 
Changed-By: Dominique Dumont 
Description:
 libuv1 - asynchronous event notification library - runtime library
 libuv1-dev - asynchronous event notification library - development files
Closes: 902941
Changes:
 libuv1 (1.21.0-2) unstable; urgency=medium
 .
   * tests/control: add dep on libc-dev
   * patch wrong enum order.
 Thanks to Felipe Sateler for the analysis (Closes: 902941)
Checksums-Sha1:
 ea0f77f96ed6d04e34b09d1ceed7a13747649ff3 2040 libuv1_1.21.0-2.dsc
 34b09d8845603fca6e8e45a3167266181169781d 16076 libuv1_1.21.0-2.debian.tar.xz
 d92e64f7e240d78d96a69400ec7653f7b89c19af 5501 libuv1_1.21.0-2_source.buildinfo
Checksums-Sha256:
 0bff822df382e41b0c55ee11f3ed8cade2f4f97dbddfc4089f565b35e4e85cfa 2040 
libuv1_1.21.0-2.dsc
 83ab6e771da1e97dad76cd1a7a6ef80146ce60deaf45b70e98b9cd091edfeb44 16076 
libuv1_1.21.0-2.debian.tar.xz
 4e2563d4c8c4108f185feb06c8e38549883b51b0caa858000f106aae26fc803b 5501 
libuv1_1.21.0-2_source.buildinfo
Files:
 6c4b513dbd1c6dac004dd1346843466c 2040 libs optional libuv1_1.21.0-2.dsc
 31bb1778925017bcd22c84206251eb18 16076 libs optional 
libuv1_1.21.0-2.debian.tar.xz
 01379e5cacf89eda0c6153862568db16 5501 libs optional 
libuv1_1.21.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAls/XwAACgkQwx9P2Umr
K2yu8w/+MKIYfpYnCq+Q50asAPqg5y261tKBgaKpxVqwQ1ktPxJEKtwCgYv5f2nJ
5WI7ev8MUJwKvq+gmjDXAojaFF4l+5K/GwkWvO1ODs39/WkNaQtAku5lMPmNDbph
VyDvQcA3Eubwi5UnTkMjCprm0qfkQhzesqQiZ1JpFNjCYzQwzjmdwIGDWdQCIbuN
gIYfZRPNg5fk+2mEr8aiDRK3x1wa2eurIkUfPQZWmGMLSRmiF7xDMkqHyHujG0FE
udGA65/mOkmomP2foWukvWTI5XyXZ1L5ZVmxJATB9wg98+qPJJFlm2slJDsxtR5a
UlfodF/252Dh+aB3Ht4dm42G2oAb3cI8GjIPl4xVhAXbPwmkP6FJCZWsmgHTz82G
Qq3yUksTKR1PohcLYnHBNh4RqznyTjVTaHZ5XWbSX3/fBG0rT5h2fTJVU84AhbaU
7aDJ8vv8Q8lQuqQd1EfldNwjRkJAcg061cRbQ8+7xuPhFrOva3RmHku+jzANbEJB
DebYjRW5RcX6+Oo/06rTJLn61+CojYEC19Poh8LjdYlOElu1fB9kwLQJC2MysKpM
9f491wgUR2lXzuvuk5B15rJ1sOGuNj+gajRBLBGIJSUQmszoiOI8ghc2QYSrCanW

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Daniel Baumann]

Hi Sean,

I've looked at the git repository on salsa, and your last commit:

https://salsa.debian.org/daniel-guest/ublock-origin/commit/0b9e4452552ce6243ae088a7880ef4d67c82d5f8

fixes this for sid (provided one has fonts-font-awesome 4.x which got
recently re-uploaded; it works flawlessly but doesn't display icons in
the popup when using fonts-font-awesome 5.x).

would you mind the fix?

Regards,
Daniel

Bug#903121: xserver-xorg-video-nvidia: blank screen, CPU fan goes to max and the systems freezes

[Richard Levitte]

Package: xserver-xorg-video-nvidia
Version: 390.67-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

it seems that a recent upgrade of nvidia-kernel-dkms and related packages broke 
my system.
I cannot say what package this issue actually belongs with (help appreciated).

With kernel version 4.9.0, I have a different issue, the modules are not 
loadable, the reported
error is "unknown rela relocatable: 4" (as I understand it, there's a 
relocation entry type
that 4.9.0 doesn't understand).  So fine, I upgrade to the latest kernel, 
4.16.0, and this is
when I get a screen that goes blank and a CPU fan that goes to max, and nothing 
else seems to
happen.  I also tried with the kernel 4.17.0, same result.  The included 
Xorg.0.log is from
the run with the latter, but it's exactly the same with 4.16.0.

All in all, that makes my laptop pretty much unusable.

The laptop is a Lenovo Y500, with a GeForce GT 650M (GK107).

Cheers,
Richard

-- Package-specific info:
uname -a:
Linux lapdog 4.17.0-1-amd64 #1 SMP Debian 4.17.3-1 (2018-07-02) x86_64 GNU/Linux

/proc/version:
Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-24)) #1 SMP Debian 4.17.3-1 (2018-07-02)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.67  Fri Jun  1 04:04:27 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-24) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107M [GeForce GT 
650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GK107M [GeForce GT 650M] [17aa:3972]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107M [GeForce GT 
650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GK107M [GeForce GT 650M] [17aa:3972]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw 1 root video 226,   0 Jul  6 13:40 /dev/dri/card0
crw-rw 1 root video 226,   1 Jul  6 13:40 /dev/dri/card1
crw-rw 1 root video 226, 128 Jul  6 13:40 /dev/dri/renderD128
crw-rw 1 root video 226, 129 Jul  6 13:40 /dev/dri/renderD129

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Jul  6 13:40 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jul  6 13:40 pci-:01:00.0-render -> ../renderD128
lrwxrwxrwx 1 root root  8 Jul  6 13:40 pci-:02:00.0-card -> ../card1
lrwxrwxrwx 1 root root 13 Jul  6 13:40 pci-:02:00.0-render -> ../renderD129
video:x:44:levitte,charlie,kin,twilight,pokio

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jul  2 13:23 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Jul  2 13:22 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Jul  2 13:23 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   51 Jul  2 13:23 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 Jul  2 13:22 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jul  2 13:22 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jul  2 13:23 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   48 Jul  2 13:23 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jul  2 13:23 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jul  2 13:23 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 Jul  2 13:22 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 Jul  2 13:22 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 Jul  2 13:23 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 

Bug#903105: nlopt: FTBFS with to octave 4.4.0

[Sébastien Villemot]

On Fri, Jul 06, 2018 at 09:59:46AM +0200, Andreas Tille wrote:
> Package: nlopt
> Severity: serious
> Justification: FTBFS
> 
> Hi,
> 
> when I team uploaded nlopt on Tue, 29 May 2018 it was building fine.  At 
> 2018-06-09
> octave 4.4.0-3 was uploaded to unstable.  When I build today the build fails 
> with
> 
> ...
> /build/nlopt-2.4.2+dfsg/octave/nlopt_optimize-oct.cc:82:36: error: 'class 
> octave_function' has no member named 'do_multi_index_op'; did you mean 
> 'do_index_op'?
>octave_value_list res = data->f->do_multi_index_op(gradient ? 2 : 1, args);
> ^
> do_index_op
> ...
> 
> I wonder whether there is some upgrade path for this API change in octave.

I team-uploaded nlopt 2.4.2+dfsg-6 on 2018-06-11 with the relevant fixes, and
it built fine against Octave 4.4. So I don't really understand your problem.
Which version are you trying to build?

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#877151: marked as done (cfflib FTBFS: ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all())

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 11:49:10 +
with message-id 
and subject line Bug#877151: fixed in cfflib 2.0.5-3
has caused the Debian Bug report #877151,
regarding cfflib FTBFS: ValueError: The truth value of an array with more than 
one element is ambiguous. Use a.any() or a.all()
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.)


-- 
877151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfflib
Version: 2.0.5-2
Severity: serious

Some recent change in unstable makes cfflib FTBFS:

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

...
I: Running cfflib unittests using python2.7
.E.
==
ERROR: cfflib.tests.test_cfflib.test_cdata
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/cfflib-2.0.5/debian/python-cfflib/usr/lib/python2.7/dist-packages/cfflib/tests/test_cfflib.py",
 line 402, in test_cdata
assert_not_equal(d.data, None)
  File "/usr/lib/python2.7/unittest/case.py", line 519, in assertNotEqual
if not first != second:
ValueError: The truth value of an array with more than one element is 
ambiguous. Use a.any() or a.all()
 >> begin captured stdout << -
Load object: 
/build/1st/cfflib-2.0.5/debian/python-cfflib/usr/lib/python2.7/dist-packages/cfflib/tests/data/CData/mydata.npy
Succeed.

- >> end captured stdout << --

--
Ran 11 tests in 0.127s

FAILED (errors=1)
debian/rules:18: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: cfflib
Source-Version: 2.0.5-3

We believe that the bug you reported is fixed in the latest version of
cfflib, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated cfflib 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: Fri, 06 Jul 2018 13:35:08 +0200
Source: cfflib
Binary: python-cfflib
Architecture: source
Version: 2.0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-cfflib - Multi-modal connectome and metadata management and integration
Closes: 877151 896309
Changes:
 cfflib (2.0.5-3) unstable; urgency=medium
 .
   * Take over into Debian Med team
   * cme fix dpkg-control
   * debhelper 11
   * Simplify d/rules
   * Work around issue in test suite
 Closes: #877151, #896309
   * Secure URI in watch file
Checksums-Sha1:
 d4175b2a932bbe4a020b96735c17d9273f737d52 2008 cfflib_2.0.5-3.dsc
 9e4d2bd7518aac0daff3ff404dcd671d2f526dc9 3524 cfflib_2.0.5-3.debian.tar.xz
Checksums-Sha256:
 2547af99fb263951c1e31a05e29fd16cd8b88109714db4c99e9cdb48ac4cdbbe 2008 
cfflib_2.0.5-3.dsc
 6304e8d9b1a0e1dcfcf43b5e7aa357fbf106e38f23489b8ca70a4bebaceb8949 3524 
cfflib_2.0.5-3.debian.tar.xz
Files:
 e5f4c40909ee1ce880849b6701953521 2008 python optional cfflib_2.0.5-3.dsc
 28a3d7ecf8aabbb64049e167ebc9cd9a 3524 python optional 
cfflib_2.0.5-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAls/VIQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF5Nw//Y21aoUxIWFgkT0gMUjFK5ohVjboilZX5
OMeKMyBioj3WpkbKjrqEmCZyZMzypRYwwoHAU4+pLTy6dH6UakbCqd2FPFNX+DLd
QdNG7QkWSTcLtNTKkLroX5ph/Wx9D/O21I2SkT9MkhpUOUe+oTvRFVJubMejbL1F
5aI61aEWTihH3aEBiOgAC7Mv+VZXpFdo2L9a6dA+Luo2jZTLBY8J8ry3ipJgC62O
Zy5M9fPR8TwHEVfsjWe9M82AE/jI87T58Bop/fH6bincyFso3R2oB+ujtuf6YnCN
P5IVevKaFQld7P/nYpE3AycFiQiyz0UWOTny4+TiZbLod6x5nks2VK8HPHoevYfE
XienKVbgnOXrRpi/4caWE62baknwIpOTWVmdMDMa2n6gewqbar6CrFAmz8X9eeo4
cdA1fKmzl6pmA2o28bRBjECFisd2jpXrCfoqrlAJVQdT4YMiyuRYJLg/S2cgWvoA

Bug#903118: rustc: FTBFS in stretch (no cargo executable found)

[Santiago Vila]

Package: src:rustc
Version: 1.24.1+dfsg1-1~deb9u1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
/bin/sh: 1: rustc: not found
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/rustc-1.24.1+dfsg1'
/bin/sh: 1: rustc: not found
m4  -DDEB_BUILD_RUST_TYPE="x86_64-unknown-linux-gnu" \
-DDEB_HOST_RUST_TYPE="x86_64-unknown-linux-gnu" \
-DDEB_TARGET_RUST_TYPE="x86_64-unknown-linux-gnu" \
-DRELEASE_CHANNEL="stable" \
-DBUILD_DOCS="true" \
-DMAKE_OPTIMISATIONS="true" \
-DLLVM_DESTDIR="" \
-DLLVM_VERSION="4.0" \
-DRUST_DESTDIR="" \
"debian/config.toml.in" > "debian/config.toml"
if false || [ 0 != 0 ]; \
  then sed -i -e '/^rustc = /d' -e '/^cargo = /d' "debian/config.toml"; fi
# Work around armhf issue: https://github.com/rust-lang/rust/issues/45854
[ amd64 != armhf -a \
  amd64 != armel ] || sed -i -e '/^debuginfo-only-std = /d' "debian/config.toml"
# fail the build if we have any instances of OLD_LLVM_VERSION in debian, except 
for debian/changelog
! grep --color=always -i 'll...\?3\.9' --exclude=changelog -R debian
:
if [ -d stage0 ]; then mkdir -p build && ln -sfT ../stage0 build/cache; fi
# work around #842634
if test $(grep "127.0.0.1\s*localhost" /etc/hosts | wc -l) -gt 1; then \
  debian/ensure-patch -N debian/patches/d-host-duplicates.patch; fi
# We patched mdbook so have to rm the checksums
debian/prune-checksums src/vendor/mdbook/.cargo-checksum.json
# Unfortunately upstream uses a duplicate copy of libbacktrace and wants to
# compile it again for rust-installer, see #43449
ln -rsf src/libbacktrace -t src/vendor/backtrace-sys/src/
debian/prune-checksums src/vendor/backtrace-sys/.cargo-checksum.json
# Link against system liblzma, see 
https://github.com/alexcrichton/xz2-rs/issues/16
echo 'fn main() { println!("cargo:rustc-link-lib=lzma"); }' > 
src/vendor/lzma-sys/build.rs
debian/prune-checksums src/vendor/lzma-sys/.cargo-checksum.json
# We excluded some embedded libraries in d/copyright
debian/prune-checksums src/vendor/dbghelp-sys/.cargo-checksum.json
# We patched this for sparc64 support
debian/prune-checksums src/vendor/cc/.cargo-checksum.json
# We don't run ./configure because we use debian/config.toml directly
ln -sf debian/config.toml config.toml
make[1]: Leaving directory '/<>/rustc-1.24.1+dfsg1'
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>/rustc-1.24.1+dfsg1'
/bin/sh: 1: rustc: not found
/usr/bin/make -C src/rt/hoedown src/html_blocks.c
make[2]: Entering directory '/<>/rustc-1.24.1+dfsg1/src/rt/hoedown'
gperf -I -L ANSI-C -N hoedown_find_block_tag -c -C -E -S 1 --ignore-case -m100 
html_block_names.gperf > src/html_blocks.c
make[2]: Leaving directory '/<>/rustc-1.24.1+dfsg1/src/rt/hoedown'
sed -i -e 's/^docs = false/docs = true/' debian/config.toml
RUST_BACKTRACE=1 ./x.py doc --config debian/config.toml -v --on-fail env
Traceback (most recent call last):
  File "./x.py", line 20, in 
bootstrap.main()
  File "/<>/rustc-1.24.1+dfsg1/src/bootstrap/bootstrap.py", line 755, 
in main
bootstrap()
  File "/<>/rustc-1.24.1+dfsg1/src/bootstrap/bootstrap.py", line 735, 
in bootstrap
build.build_bootstrap()
  File "/<>/rustc-1.24.1+dfsg1/src/bootstrap/bootstrap.py", line 615, 
in build_bootstrap
self.cargo()))
Exception: no cargo executable found at `/usr/bin/cargo`
debian/rules:216: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>/rustc-1.24.1+dfsg1'
debian/rules:143: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I did "dpkg-buildpackage -A" but apparently it also fails with 
"dpkg-buildpackage -B"
in every other architecture:

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

Thanks.

Bug#896309: marked as done (python-cfflib: cfflib fails to import)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 11:49:10 +
with message-id 
and subject line Bug#896309: fixed in cfflib 2.0.5-3
has caused the Debian Bug report #896309,
regarding python-cfflib: cfflib fails to import
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.)


-- 
896309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cfflib
Version: 2.0.5-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-cfflib importing the module cfflib
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/cfflib/__init__.py", line 2, in 

from loadsave import *
  File "/usr/lib/python2.7/dist-packages/cfflib/loadsave.py", line 6, in 

import cfflib2 as cf
  File "/usr/lib/python2.7/dist-packages/cfflib/cfflib2.py", line 10, in 

from util import *
  File "/usr/lib/python2.7/dist-packages/cfflib/util.py", line 18, in 
raise ImportError("Failed to import nibabel from any known place")
ImportError: Failed to import nibabel from any known place

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: cfflib
Source-Version: 2.0.5-3

We believe that the bug you reported is fixed in the latest version of
cfflib, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated cfflib 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: Fri, 06 Jul 2018 13:35:08 +0200
Source: cfflib
Binary: python-cfflib
Architecture: source
Version: 2.0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-cfflib - Multi-modal connectome and metadata management and integration
Closes: 877151 896309
Changes:
 cfflib (2.0.5-3) unstable; urgency=medium
 .
   * Take over into Debian Med team
   * cme fix dpkg-control
   * debhelper 11
   * Simplify d/rules
   * Work around issue in test suite
 Closes: #877151, #896309
   * Secure URI in watch file
Checksums-Sha1:
 d4175b2a932bbe4a020b96735c17d9273f737d52 2008 cfflib_2.0.5-3.dsc
 9e4d2bd7518aac0daff3ff404dcd671d2f526dc9 3524 cfflib_2.0.5-3.debian.tar.xz
Checksums-Sha256:
 2547af99fb263951c1e31a05e29fd16cd8b88109714db4c99e9cdb48ac4cdbbe 2008 
cfflib_2.0.5-3.dsc
 6304e8d9b1a0e1dcfcf43b5e7aa357fbf106e38f23489b8ca70a4bebaceb8949 3524 
cfflib_2.0.5-3.debian.tar.xz
Files:
 e5f4c40909ee1ce880849b6701953521 2008 python optional cfflib_2.0.5-3.dsc
 28a3d7ecf8aabbb64049e167ebc9cd9a 3524 python optional 
cfflib_2.0.5-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAls/VIQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF5Nw//Y21aoUxIWFgkT0gMUjFK5ohVjboilZX5
OMeKMyBioj3WpkbKjrqEmCZyZMzypRYwwoHAU4+pLTy6dH6UakbCqd2FPFNX+DLd
QdNG7QkWSTcLtNTKkLroX5ph/Wx9D/O21I2SkT9MkhpUOUe+oTvRFVJubMejbL1F
5aI61aEWTihH3aEBiOgAC7Mv+VZXpFdo2L9a6dA+Luo2jZTLBY8J8ry3ipJgC62O
Zy5M9fPR8TwHEVfsjWe9M82AE/jI87T58Bop/fH6bincyFso3R2oB+ujtuf6YnCN
P5IVevKaFQld7P/nYpE3AycFiQiyz0UWOTny4+TiZbLod6x5nks2VK8HPHoevYfE
XienKVbgnOXrRpi/4caWE62baknwIpOTWVmdMDMa2n6gewqbar6CrFAmz8X9eeo4
cdA1fKmzl6pmA2o28bRBjECFisd2jpXrCfoqrlAJVQdT4YMiyuRYJLg/S2cgWvoA
Mr8hmY9OIhBO7cxE03z3epionXxz5L8XYtIYRWDTE8Vy27fYu9mKfee0PDeRhUpj
rC7jU90JJRz/0NRWKi8LkqloE+PMYsAmwaUs4HWtHO7MyUEPNgjmcrwEKikUcDvQ
BAZ0iGr77tcDGEfHabcTQMwXUcDMJKO0K06jH0rYw3vmSot8EaHfH97ALgVya3W+
lqOeBEVWBJo=
=meYB
-END PGP SIGNATURE End Message ---

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Sean Whitton]

Hello,

On Fri, Jul 06 2018, Daniel Baumann wrote:

> any progress/eta on this? unfortunatly, ublock-origin still doesn't
> work with firefox, unless installing the upstream extension from
> addons.mozilla.org.

I'm afraid not.

The package is looking for a new maintainer: https://bugs.debian.org/877041

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#902161: marked as done (gatb-core: "dpkg-buildpackage -B" FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 11:04:02 +
with message-id 
and subject line Bug#902161: fixed in gatb-core 1.4.1+dfsg-2
has caused the Debian Bug report #902161,
regarding gatb-core: "dpkg-buildpackage -B" 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.)


-- 
902161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gatb-core
Version: 1.4.1+dfsg-1
Severity: serious

"dpkg-buildpackage -B" as is done on the buildds
FTBFS everywhere (also on amd64):

https://buildd.debian.org/status/package.php?p=gatb-core=sid

...
install -d -m 755 debian/libgatbcore-dev/usr
mv debian/tmp/usr/include debian/libgatbcore-dev/usr
mkdir -p debian/gatb-core/usr/lib/gatb-core
mv debian/gatb-core-testdata/usr/share/doc/gatb-core/test/gatb-core-cppunit 
debian/gatb-core/usr/lib/gatb-core
mv: cannot stat 
'debian/gatb-core-testdata/usr/share/doc/gatb-core/test/gatb-core-cppunit': No 
such file or directory
debian/rules:13: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
--- End Message ---
--- Begin Message ---
Source: gatb-core
Source-Version: 1.4.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
gatb-core, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gatb-core 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: Fri, 06 Jul 2018 12:01:54 +0200
Source: gatb-core
Binary: gatb-core libgatbcore0 libgatbcore-dev gatb-core-testdata
Architecture: source
Version: 1.4.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 gatb-core  - Genome Analysis Toolbox with de-Bruijn graph
 gatb-core-testdata - Genome Analysis Toolbox with de-Bruijn graph (test data)
 libgatbcore-dev - development library of the Genome Analysis Toolbox
 libgatbcore0 - dynamic library of the Genome Analysis Toolbox
Closes: 902161
Changes:
 gatb-core (1.4.1+dfsg-2) unstable; urgency=medium
 .
   * Install cmake files
   * Fix binary only build
 Closes: #902161
Checksums-Sha1:
 99a65f3b359a633b74eeafcd81c9a3a1026336f5 2312 gatb-core_1.4.1+dfsg-2.dsc
 479263a32f8713938e384894dc4a345520f19ad2 19220 
gatb-core_1.4.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 f3ae7cd1f7506bed9e9ef0edf7a2ab5c9f6b7b72964bc653f8b2a599ec76ced8 2312 
gatb-core_1.4.1+dfsg-2.dsc
 2e421d4df19a4ed517356529aebffe4dddea8a5d041159af55755bfcd3399d9c 19220 
gatb-core_1.4.1+dfsg-2.debian.tar.xz
Files:
 72291be74cb4e5a4e14caa3c76821784 2312 science optional 
gatb-core_1.4.1+dfsg-2.dsc
 88aa7d1c836faef262ee1821df97ddaa 19220 science optional 
gatb-core_1.4.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAls/R64RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHPmw/+OxUFTtN9oH4D9eRLsM94pMYOiQxVnzGf
9EeFVig4aGonzLu3f1xny36a8aosOGidtF/64S/AqGvejyrjpagWcTkW/LZuATB2
xn13WC4+8WCrDkBNGAclVuumZXYQeCA+ZFMg0mdJ8ngOzVQxjsH3UE2hfGL072of
at83M4RFi1qQw36/59r4v+2N8pa1B/xIU58FAVJXb/MUzgDm5kZ6J7x6YA9vTcQL
r+pW+Lgl86B2sKMSoi62+wRCZRtqEVz0CK9ZuT/vkd3uBj062TEOUqDrMRwEDXf6
jMJjlFJ/4MLfqLXRiq2F7dlaYa8PtuWFtldiLlccpVxciC+S8ph7DkagbzxCKKb2
7hrOMunx3DfQfbiAe337Lt/1J973SslyrsmXSOJ0gK5IPyq4ocbMMGfwephuMmG0
gErjCr9fSfmAqxsMLjI8cdPVQdfMNbXhyjpbIgTa0LJIs5irqbwQpatzm8ee9l0e
TnHjwZtExiSvPSgNZXD+kdn7PagxkiHehiu3UxBlvgLYCjXGv6CVX+a11VVR7LeI
RdEEER4TGE8Ufv6bFl8/p5Vf/AM9393PPRfPb2Kb8VbKhlrQrjUER8P9dypTCqwp
/S/GBBGhn6nVofBWQ2tLPM/pUGO79S8WaADsUQuk2Sy+b1NlLv1mGtNnRGF4tXmV
6XoSgj2egs0=
=mt6K
-END PGP SIGNATURE End Message ---

Bug#899365: webext-ublock-origin: webext package does not work in Firefox

[Daniel Baumann]

Hi,

any progress/eta on this? unfortunatly, ublock-origin still doesn't work
with firefox, unless installing the upstream extension from
addons.mozilla.org.

Regards,
Daniel

Bug#902117: corosync-qdevice will not daemonize/run

[Ferenc Wágner]

Hi Jason,

Thanks for the report.  I've been pretty busy with other tasks, but I'll
check this out as soon as possible, your report isn't forgotten.  I ask
for you patience till then.
-- 
Regards,
Feri

Bug#902466: marked as done (golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 10:49:03 +
with message-id 
and subject line Bug#902466: fixed in 
golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-2
has caused the Debian Bug report #902466,
regarding golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid 
(failing tests)
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.)


-- 
902466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-grpc-ecosystem-go-grpc-prometheus
Version: 1.1+git20170826.0dafe0d-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d'
cd 
obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto
 && \
GOPATH=obj-x86_64-linux-gnu make 
make[2]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d/obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto'
PATH="obj-x86_64-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 protoc \
  -I. \
-Iobj-x86_64-linux-gnu/src \

[... snipped ...]

=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsStarted
--- FAIL: TestServerInterceptorSuite (0.08s)
--- PASS: TestServerInterceptorSuite/TestRegisterPresetsStuff (0.02s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHandled (0.01s)
server_test.go:218: 
Error Trace:server_test.go:218
Error:  Not equal: 
expected: 1
actual  : 0
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHandled
Messages:   grpc_server_handled_total should be 
incremented for PingList FailedPrecondition
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHistograms 
(0.01s)
server_test.go:186: 
Error Trace:server_test.go:186
Error:  Not equal: 
expected: 2
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList OK
server_test.go:193: 
Error Trace:server_test.go:193
Error:  Not equal: 
expected: 4
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList FailedPrecondition
--- PASS: TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts 
(0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsStarted (0.00s)
server_test.go:168: 
Error Trace:server_test.go:168
Error:  Not equal: 
expected: 6
actual  : 5
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsStarted
Messages:   grpc_server_started_total should be 
incremented for PingList
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHandled (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHistograms (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsStarted (0.01s)
server_test.go:86: stopped grpc.Server at: 127.0.0.1:33315
FAIL
FAILgithub.com/grpc-ecosystem/go-grpc-prometheus0.124s
?   github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto [no 
test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 

Bug#902466: Bug #902466 in golang-github-grpc-ecosystem-go-grpc-prometheus marked as pending

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #902466 in golang-github-grpc-ecosystem-go-grpc-prometheus 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/go-team/packages/golang-github-grpc-ecosystem-go-grpc-prometheus/commit/5d0468e299f9fe323ad9c5f718e99aa03ce10fb0


New patch to fix unreliable test (Closes: #902466) + changelog summary.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902466

Processed: Bug #902466 in golang-github-grpc-ecosystem-go-grpc-prometheus marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902466 [src:golang-github-grpc-ecosystem-go-grpc-prometheus] 
golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing 
tests)
Added tag(s) pending.

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

Bug#902592: marked as done (spades ftbfs with new nlopt in unstable)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 10:37:33 +
with message-id 
and subject line Bug#902592: fixed in spades 3.11.1+dfsg-2
has caused the Debian Bug report #902592,
regarding spades ftbfs with new nlopt in unstable
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.)


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

Package: src:spades
Version: 3.11.1+dfsg-1
Severity: serious
Tags: sid buster

spades ftbfs with the new nlopt in unstable:

[ 49%] Building CXX object 
common/modules/coverage_model/CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o
cd /<>/spades-3.11.1+dfsg/build_spades/common/modules/coverage_model 
&& /usr/bin/c++  -DJEMALLOC_NO_DEMANGLE -DUSE_GLIBCXX_PARALLEL=1 
-I/<>/spades-3.11.1+dfsg/build_spades/common/modules/coverage_model 
-I/<>/spades-3.11.1+dfsg/src/common/modules/coverage_model 
-I/<>/spades-3.11.1+dfsg/src/include 
-I/<>/spades-3.11.1+dfsg/build_spades/include 
-I/<>/spades-3.11.1+dfsg/src 
-I/<>/spades-3.11.1+dfsg/src/common -isystem 
/<>/spades-3.11.1+dfsg/src/../ext/include  -g -O2 
-fdebug-prefix-map=/<>/spades-3.11.1+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp 
-std=c++11 -O2 -g -DNDEBUG   -UNDEBUG -Wno-deprecated -g3 -O2 -Wall -Wextra 
-Wconversion -Wno-sign-conversion -Wno-long-long -Wwrite-strings -o 
CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o -c 
/<>/spades-3.11.1+dfsg/src/common/modules/coverage_model/kmer_coverage_model.cpp
/<>/spades-3.11.1+dfsg/src/common/modules/coverage_model/kmer_coverage_model.cpp:21:10: 
fatal error: nlopt.hpp: No such file or directory

 #include 
  ^~~
compilation terminated.
common/modules/coverage_model/CMakeFiles/coverage_model.dir/build.make:62: 
recipe for target 
'common/modules/coverage_model/CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o' 
failed
make[4]: *** 
[common/modules/coverage_model/CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o] 
Error 1

make[4]: Leaving directory '/<>/spades-3.11.1+dfsg/build_spades'
CMakeFiles/Makefile2:1310: recipe for target 
'common/modules/coverage_model/CMakeFiles/coverage_model.dir/all' failed
make[3]: *** [common/modules/coverage_model/CMakeFiles/coverage_model.dir/all] 
Error 2

make[3]: Leaving directory '/<>/spades-3.11.1+dfsg/build_spades'
Makefile:151: recipe for target 'all' failed
make[2]: *** [all] Error 2
--- End Message ---
--- Begin Message ---
Source: spades
Source-Version: 3.11.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
spades, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated spades 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: Fri, 06 Jul 2018 10:54:09 +0200
Source: spades
Binary: spades
Architecture: source
Version: 3.11.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 spades - genome assembler for single-cell and isolates data sets
Closes: 902592
Changes:
 spades (3.11.1+dfsg-2) unstable; urgency=medium
 .
   * Build-Depends: libnlopt-cxx-dev
 Closes: #902592
   * d/rules:
  + filter nocheck,$(DEB_BUILD_OPTIONS)
  + do not parse d/changelog
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.4
Checksums-Sha1:
 735aece29f47350cb359cedb88bbf0e01cfde4b0 2353 spades_3.11.1+dfsg-2.dsc
 9a1e3863e3da4d19f873415d80c63827dff25001 19780 
spades_3.11.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 6ac351aabfce9955e6ca5eb536649a6f88dfb08279acc32ea51b7c90bf8643e1 2353 
spades_3.11.1+dfsg-2.dsc
 dacbabb487bed24692e11a44f656f9e9eaee5a3e297ae600cc3468c001c78a23 19780 
spades_3.11.1+dfsg-2.debian.tar.xz
Files:
 d30ed52f5eb999b37562b2ab387ea1b9 2353 science optional spades_3.11.1+dfsg-2.dsc
 82d020e9205a3bb65698dc552de60fea 19780 science optional 
spades_3.11.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: tagging 902466

[Debian Bug Tracking System]

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

> tags 902466 + upstream
Bug #902466 [src:golang-github-grpc-ecosystem-go-grpc-prometheus] 
golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing 
tests)
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#895604: marked as done (php-symfony-polyfill: FTBFS and Debci failure with phpunit 7.0.3-1)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 10:10:10 +
with message-id 
and subject line Bug#895604: fixed in php-symfony-polyfill 1.8.0-1
has caused the Debian Bug report #895604,
regarding php-symfony-polyfill: FTBFS and Debci failure with phpunit 7.0.3-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.)


-- 
895604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-symfony-polyfill
Version: 1.7.0-1
Severity: serious

https://ci.debian.net/packages/p/php-symfony-polyfill/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-symfony-polyfill.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-symfony-polyfill-1.7.0'
phpunit --bootstrap debian/autoload.php
PHP Fatal error:  Declaration of Symfony\Polyfill\Util\TestListener::setUp() 
must be compatible with PHPUnit\Framework\TestSuite::setUp(): void in 
/build/1st/php-symfony-polyfill-1.7.0/src/Util/TestListener.php on line 28
make[1]: *** [debian/rules:61: override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-symfony-polyfill
Source-Version: 1.8.0-1

We believe that the bug you reported is fixed in the latest version of
php-symfony-polyfill, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-symfony-polyfill 
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: Thu, 05 Jul 2018 11:01:36 -1000
Source: php-symfony-polyfill
Binary: php-symfony-polyfill php-symfony-polyfill-apcu 
php-symfony-polyfill-ctype php-symfony-polyfill-iconv 
php-symfony-polyfill-intl-grapheme php-symfony-polyfill-intl-icu 
php-symfony-polyfill-intl-normalizer php-symfony-polyfill-mbstring 
php-symfony-polyfill-php54 php-symfony-polyfill-php55 
php-symfony-polyfill-php56 php-symfony-polyfill-php70 
php-symfony-polyfill-php71 php-symfony-polyfill-php72 
php-symfony-polyfill-php73 php-symfony-polyfill-util php-symfony-polyfill-xml
Architecture: source all
Version: 1.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 php-symfony-polyfill -
 php-symfony-polyfill-apcu -
 php-symfony-polyfill-ctype -
 php-symfony-polyfill-iconv -
 php-symfony-polyfill-intl-grapheme -
 php-symfony-polyfill-intl-icu -
 php-symfony-polyfill-intl-normalizer -
 php-symfony-polyfill-mbstring -
 php-symfony-polyfill-php54 -
 php-symfony-polyfill-php55 -
 php-symfony-polyfill-php56 -
 php-symfony-polyfill-php70 -
 php-symfony-polyfill-php71 -
 php-symfony-polyfill-php72 -
 php-symfony-polyfill-php73 -
 php-symfony-polyfill-util -
 php-symfony-polyfill-xml -
Closes: 895604
Changes:
 php-symfony-polyfill (1.8.0-1) unstable; urgency=medium
 .
   [ David Prévot ]
   * Fix Vcs-* URLs
   * Update homemade autoload to new dependencies
   * Add new php-symfony-polyfill-ctype component
   * Add new php-symfony-polyfill-php73 component
   * Update Standards-Version to 4.1.5
   * Update for PHPUnit 7.2 (Closes: 895604)
 .
   [ Gabriel Caruso ]
   * Add is_countable under PHP 7.3
 .
   [ BackEndTea ]
   * Add the cytpe polyfill
Checksums-Sha1:
 387c5d50044a5b80405ddbe5eb85ce47767bbaa3 3291 php-symfony-polyfill_1.8.0-1.dsc
 5190082fb37e3ff1246baa2e087028f2f2ed53d3 930868 
php-symfony-polyfill_1.8.0.orig.tar.gz
 dfd2a55f9d63f4009e7184b7d000610d79d88df9 7008 
php-symfony-polyfill_1.8.0-1.debian.tar.xz
 b6f73746def25710b1c460fcd208b1951ce157ad 6416 
php-symfony-polyfill-apcu_1.8.0-1_all.deb
 a94179f4ed0f35bad35ab8f9c54cefeb52c01ed0 6708 
php-symfony-polyfill-ctype_1.8.0-1_all.deb
 418e4c4ce9321401f9f0a15723e4f303d2f3912b 125036 
php-symfony-polyfill-iconv_1.8.0-1_all.deb
 02d52776f72861d86a75e06cacfb68de4cd8017f 8000 
php-symfony-polyfill-intl-grapheme_1.8.0-1_all.deb
 fab5c7a6b095d75e57ae0c993e9ca0d41fe692f2 5612 
php-symfony-polyfill-intl-icu_1.8.0-1_all.deb
 2d7616c806fa8a48a45d8eae3a854093ac0f90dc 24956 
php-symfony-polyfill-intl-normalizer_1.8.0-1_all.deb
 

Processed: bug 902466 is forwarded to https://github.com/grpc-ecosystem/go-grpc-prometheus/issues/56

[Debian Bug Tracking System]

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

> forwarded 902466 
> https://github.com/grpc-ecosystem/go-grpc-prometheus/issues/56
Bug #902466 [src:golang-github-grpc-ecosystem-go-grpc-prometheus] 
golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing 
tests)
Set Bug forwarded-to-address to 
'https://github.com/grpc-ecosystem/go-grpc-prometheus/issues/56'.
> thanks
Stopping processing here.

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

Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-1

[Dmitry Smirnov]

On Friday, 6 July 2018 7:32:48 PM AEST Santiago Vila wrote:
> The same error happens in reproducible builds:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/golang-git
> hub-grpc-ecosystem-go-grpc-prometheus.html
> 
> I'm reopening this bug because the error is the same.

Fair enough, but I've built it several times and could not reproduce...

-- 
All the best,
 Dmitry Smirnov.

---


Truth never damages a cause that is just.
-- Mahatma Gandhi


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

Bug#903111: haskell-raaz FTBFS in buster

[peter green]

Package: haskell-raaz
Severity: serious
Version: 0.2.0-2

haskell-raaz recently failed to build in raspbian buster with


dh_installexamples -plibghc-raaz-dev
dh_installexamples: Cannot find (any matches for) "bin/Command/Checksum.lhs" 
(tried in .)


The reproducible builds tests on amd64, armhf and arm64 (but strangely not 
i386) also show the same failure, so this doesn't appear to be raspbian 
specific.


I do not know if this also affects sid, the tests on reproducible builds are 
all showing successful on sid, but they are much less recent than the tests on 
buster that failed.

Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-1

[Santiago Vila]

found 902466 1.2.0-1
thanks

Dear maintainer:

This is from my autobuilder today, building the package in buster:


=== RUN   TestServerInterceptorSuite
=== RUN   TestServerInterceptorSuite/TestRegisterPresetsStuff
=== RUN   TestServerInterceptorSuite/TestStreamingIncrementsHandled
=== RUN   TestServerInterceptorSuite/TestStreamingIncrementsHistograms
=== RUN   TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts
=== RUN   TestServerInterceptorSuite/TestStreamingIncrementsStarted
=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsHandled
=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsHistograms
=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsStarted
--- FAIL: TestServerInterceptorSuite (0.06s)
--- PASS: TestServerInterceptorSuite/TestRegisterPresetsStuff (0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHandled (0.01s)
server_test.go:219: 
Error Trace:server_test.go:219
Error:  Not equal: 
expected: 1
actual  : 0
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHandled
Messages:   grpc_server_handled_total should be 
incremented for PingList FailedPrecondition
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHistograms 
(0.01s)
server_test.go:194: 
Error Trace:server_test.go:194
Error:  Not equal: 
expected: 4
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList FailedPrecondition
--- PASS: TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts 
(0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsStarted (0.00s)
server_test.go:169: 
Error Trace:server_test.go:169
Error:  Not equal: 
expected: 6
actual  : 5
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsStarted
Messages:   grpc_server_started_total should be 
incremented for PingList
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHandled (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHistograms (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsStarted (0.01s)
server_test.go:87: stopped grpc.Server at: 127.0.0.1:35841
FAIL
FAILgithub.com/grpc-ecosystem/go-grpc-prometheus0.095s
?   
github.com/grpc-ecosystem/go-grpc-prometheus/examples/grpc-server-with-prometheus/client
[no test files]
?   
github.com/grpc-ecosystem/go-grpc-prometheus/examples/grpc-server-with-prometheus/protobuf
  [no test files]
?   
github.com/grpc-ecosystem/go-grpc-prometheus/examples/grpc-server-with-prometheus/server
[no test files]
?   github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto [no 
test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/grpc-ecosystem/go-grpc-prometheus 
github.com/grpc-ecosystem/go-grpc-prometheus/examples/grpc-server-with-prometheus/client
 
github.com/grpc-ecosystem/go-grpc-prometheus/examples/grpc-server-with-prometheus/protobuf
 
github.com/grpc-ecosystem/go-grpc-prometheus/examples/grpc-server-with-prometheus/server
 github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto returned exit 
code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The same error happens in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/golang-github-grpc-ecosystem-go-grpc-prometheus.html

I'm reopening this bug because the error is the same.

Please consider source-only uploads (dpkg-buildpackage -S).

Thanks.

Processed: Re: Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-1

[Debian Bug Tracking System]

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

> found 902466 1.2.0-1
Bug #902466 {Done: Dmitry Smirnov } 
[src:golang-github-grpc-ecosystem-go-grpc-prometheus] 
golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing 
tests)
Marked as found in versions 
golang-github-grpc-ecosystem-go-grpc-prometheus/1.2.0-1; no longer marked as 
fixed in versions golang-github-grpc-ecosystem-go-grpc-prometheus/1.2.0-1 and 
reopened.
> thanks
Stopping processing here.

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

Bug#903105: nlopt: FTBFS with to octave 4.4.0

[Andreas Tille]

Control: tags -1 help

No idea whether Debian Octave Group
 is read by a human beeing.  To
be sure Sébastien was always in CC.

Kind regards

 Andreas.

On Fri, Jul 06, 2018 at 09:59:46AM +0200, Andreas Tille wrote:
> Package: nlopt
> Severity: serious
> Justification: FTBFS
> 
> Hi,
> 
> when I team uploaded nlopt on Tue, 29 May 2018 it was building fine.  At 
> 2018-06-09
> octave 4.4.0-3 was uploaded to unstable.  When I build today the build fails 
> with
> 
> ...
> /build/nlopt-2.4.2+dfsg/octave/nlopt_optimize-oct.cc:82:36: error: 'class 
> octave_function' has no member named 'do_multi_index_op'; did you mean 
> 'do_index_op'?
>octave_value_list res = data->f->do_multi_index_op(gradient ? 2 : 1, args);
> ^
> do_index_op
> ...
> 
> I wonder whether there is some upgrade path for this API change in octave.
> 
> Kind regards
> 
>Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#903105: nlopt: FTBFS with to octave 4.4.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #903105 [nlopt] nlopt: FTBFS with to octave 4.4.0
Added tag(s) help.

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

Bug#900825: marked as done (Test suite failing)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 08:18:13 +
with message-id 
and subject line Bug#900825: fixed in cider 0.17.0+dfsg-1
has caused the Debian Bug report #900825,
regarding Test suite failing
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.)


-- 
900825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cider
Version: 0.16.0+dfsg-2
Severity: important
Control: block -1 by 899124

The test suite is failing:

Traceback (most recent call last):
  (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
(setq...
  (unwind-protect (progn (setq major-mode (quote cider-repl-mode)) (setq 
cid...
  (progn (setq major-mode (quote cider-repl-mode)) (setq cider-repl-type 
"cl...
  (let ((cider-connections (cons (current-buffer) cider-connections)) (b 
(cu...
  (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-buffer 
...
  (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
(cloj...
  (unwind-protect (progn (clojurex-mode) (buttercup-expect (function 
(lambda...
  (progn (clojurex-mode) (buttercup-expect (function (lambda nil (quote 
(cid...
  (clojurex-mode)
error: (void-function clojurex-mode)


Ran 263 specs, 1 failed, in 2.4 seconds.

I believe that the new upstream version of CIDER will fix this -- the
latest clojure-mode does not contain clojurex-mode.

However, uploading cider is blocked by #899124.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cider
Source-Version: 0.17.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
cider, 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 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated cider 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, 06 Jul 2018 08:36:11 +0100
Source: cider
Binary: cider-doc elpa-cider
Architecture: source
Version: 0.17.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Sean Whitton 
Description:
 cider-doc  - Clojure IDE for Emacs - documentation
 elpa-cider - Clojure IDE for Emacs
Closes: 900825 901564
Changes:
 cider (0.17.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #900825, #901564).
   * Flip long descriptions of binary packages, which were somehow the
 wrong way around.
   * Update debian/cider-doc.linktrees as search javascript in bin:mkdocs
 has moved.
Checksums-Sha1:
 210a02863d6d9050e88a2776c486724d243c7ef8 2262 cider_0.17.0+dfsg-1.dsc
 80bc183e6b7a5c690fa5d476ab11aa067cfcb74c 3892828 cider_0.17.0+dfsg.orig.tar.xz
 fa6f0ae165dfb0bf25faa3dc53f26f4904ae08f1 6884 cider_0.17.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
 d3ac563e34ceb795159d0317b3b3f8cf2aa8690f90872866f81bbf2c25495537 2262 
cider_0.17.0+dfsg-1.dsc
 4b367355c0aaa7b6eb972ebc577147b405eee828c5e51ab845780ee9954a3f98 3892828 
cider_0.17.0+dfsg.orig.tar.xz
 51e812d654538e5f40fc2c5c23e13433918be505c640b08ccd542d40ad828ab9 6884 
cider_0.17.0+dfsg-1.debian.tar.xz
Files:
 f9409df88e82e922b6318fa770c8e51b 2262 lisp optional cider_0.17.0+dfsg-1.dsc
 0603b01cf6f82c97fb15c1a10ffaf473 3892828 lisp optional 
cider_0.17.0+dfsg.orig.tar.xz
 2570682432f8c9e169f021ce1a28badf 6884 lisp optional 
cider_0.17.0+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAls/HDoACgkQaVt65L8G
YkBfHQ/9Hgd8iAGJbWmYDgiPIYeRfQ5OAYQfY23scR/sht5Fp2fxe0e/+mrFeETH
bLMuUXG8NX0XsLj7pbQQQc1agcjWOJ/guIdcAj3tCfApmq9gcwDI5X8GSQe9xgAB
AUDq+RMwrOuAnlvL63IuzZ9aDahp0ybB3wT+NbX24F4nA7VWsP9yFj1d0xFIwN+w
AIk7t1czM2bESrwbrQVssJXA2sPkScIEbhQydUFLsWL0L6jeNGuT0xjE4nQJENYT
rgtnKtTk7lrAC8OaEb1v5Clf8UarTfmL//qlsbVeodQ6dDgAuu3mr6oXezg1Y2Nj
iXBX88H1UrGJdAmQnfyp73SPUIb9CXJq05cD8hyrcreK1KBu1izW00wB78TvOEsD
CsL5u6UtD80Rp6siK4guXgs9RY50Rw8rxFSWHijNjsDPyGDXkoeBOHDsdERM9j4Y
60oq81plaorcH5y+RUmy+Dz1forZw08YVoNldXJhrn/VbC2ID6ySc5efQjhQ3aX4
M4c1yg6VEfAoXMTsMX6yOn8OgnRV64FZeanPLrXgX3amLpuE/yBtIYCLtagtiuUA

Bug#903105: nlopt: FTBFS with to octave 4.4.0

[Andreas Tille]

Package: nlopt
Severity: serious
Justification: FTBFS

Hi,

when I team uploaded nlopt on Tue, 29 May 2018 it was building fine.  At 
2018-06-09
octave 4.4.0-3 was uploaded to unstable.  When I build today the build fails 
with

...
/build/nlopt-2.4.2+dfsg/octave/nlopt_optimize-oct.cc:82:36: error: 'class 
octave_function' has no member named 'do_multi_index_op'; did you mean 
'do_index_op'?
   octave_value_list res = data->f->do_multi_index_op(gradient ? 2 : 1, args);
^
do_index_op
...

I wonder whether there is some upgrade path for this API change in octave.

Kind regards

   Andreas.



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

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

Bug#903043: [debian-mysql] Bug#903043: percona-xtrabackup 2.2.3-2.1 Unsupported server version: 10.1.26-MariaDB-0+deb9u1

[Christian Saller]

Hi,

encryption or compression is not in use.

The issue could be solved by updating the innobackupex script:

diff innobackupex innobackupex.new -c
*** innobackupex    2018-07-06 09:26:17.531367905 +0200
--- innobackupex.new    2018-07-06 09:26:02.835301191 +0200
***
*** 4618,4624 
   # MySQL/Percona Server 5.6
   $var_version =~ m/5\.6\.\d/ ||
   # MariaDB 10.0
!  $var_version =~ m/10\.0\.\d/
  )) {

  die "Unsupported server version: '$var_version' " .
--- 4618,4626 
   # MySQL/Percona Server 5.6
   $var_version =~ m/5\.6\.\d/ ||
   # MariaDB 10.0
!  $var_version =~ m/10\.0\.\d/ ||
!  # MariaDB 10.1
!  $var_version =~ m/10\.1\.\d/
  )) {

  die "Unsupported server version: '$var_version' " .


smime.p7s
Description: S/MIME cryptographic signature

Bug#900533: Bug still exists

[Marco Fleckinger]

As mentioned the bug still exists in chromium 67.0.3396.87 from the 
Debian Repo. I setup a totally fresh VM for this purpose running stretch.


There I downloaded the source and compiled following the instructions at 
[1]. Upstream Chromium 69 worked fine so I tried to compile the exact 
same version as installed by APT on my notebook 67.0.3396.87 including 
[2] into my workflow.


The 67.0.3396.87 version from upstream didn't have the issue. For 
testing I used a plain mp3 served by python's SimpleHTTPServer:


  python -m SimpleHTTPServer

First I always had the sandbox issue, I could start the 
upstream-versions only with --no-sandbox. Afterwards I tried to also 
compile the sandbox and start chromium using the wrapper. But this 
should not be relevant here


Then I found out that the error also occurs when I used the Debian 
Package on my dedicated VM. After runnig it via CLI I also got this 
Error Message:


[2693:2708:0705/212253.877035:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[2693:2693:0705/212253.877203:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN


[1] https://github.com/chromium/chromium/blob/master/docs/README.md
[2] 
https://www.chromium.org/developers/how-tos/get-the-code/working-with-release-branches
[3] 
https://unix.stackexchange.com/questions/68832/what-does-the-chromium-option-no-sandbox-mean#answer-105126


Marco

Processed: severity of 900825 is serious

[Debian Bug Tracking System]

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

> severity 900825 serious
Bug #900825 [src:cider] Test suite failing
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#903058: marked as done (git-lfs FTBFS: update Build-Depends: ruby-ronn -> ronn)

[Debian Bug Tracking System]

Your message dated Fri, 06 Jul 2018 07:04:49 +
with message-id 
and subject line Bug#903058: fixed in git-lfs 2.4.2-2
has caused the Debian Bug report #903058,
regarding git-lfs FTBFS: update Build-Depends: ruby-ronn -> ronn
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.)


-- 
903058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-lfs
Version: 2.4.2-1
Severity: serious

Since ronn got split out of ruby-ronn, git-lfs fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn as git-lfs uses the
command line tool.

Helmut
--- End Message ---
--- Begin Message ---
Source: git-lfs
Source-Version: 2.4.2-2

We believe that the bug you reported is fixed in the latest version of
git-lfs, 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 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Gelman  (supplier of updated git-lfs 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, 06 Jul 2018 06:43:15 +
Source: git-lfs
Binary: git-lfs
Architecture: source
Version: 2.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Stephen Gelman 
Description:
 git-lfs- Git Large File Support
Closes: 901963 903058
Changes:
 git-lfs (2.4.2-2) unstable; urgency=medium
 .
   * Change dependency from ruby-ronn to ronn to match ronn package changes
 (Closes: #903058)
   * Fix built-in help commands to work properly (Closes: #901963)
Checksums-Sha1:
 a1d14b1fa875e5c3325f6ef8260410470f9041a4 2440 git-lfs_2.4.2-2.dsc
 9a30d67acebaa20be986f8f8f9a097683d9afa8d 3744 git-lfs_2.4.2-2.debian.tar.xz
 fe016eec761372f88ac3b78d5ba3f78254c38008 14394 git-lfs_2.4.2-2_amd64.buildinfo
Checksums-Sha256:
 a2cb138c4010a4df5ee3fa11c97cdeb77c518828d609f190c9746f02021024b4 2440 
git-lfs_2.4.2-2.dsc
 5872c60b93604cbd17a68bba5e9356b746fedaf7fb6ebf56c68da93ac598950c 3744 
git-lfs_2.4.2-2.debian.tar.xz
 046574152987d1d83dbbb8cac0b94f46911e01938c90d470213ed79fd8d4843c 14394 
git-lfs_2.4.2-2_amd64.buildinfo
Files:
 b403f93a04e187f8a735b87c93f6a908 2440 vcs optional git-lfs_2.4.2-2.dsc
 56c75325ebfe5e15986d1d4e0f8a9077 3744 vcs optional 
git-lfs_2.4.2-2.debian.tar.xz
 a2aa39ff1ab142da845a012cf461f548 14394 vcs optional 
git-lfs_2.4.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPwDop1BN06KlsbfijqM4hED8f1wFAls/ET4ACgkQjqM4hED8
f1w7tA//c0Cc1D0hn1p+PlYfnp/T3M4QVuseSj6FRnawDw/oji/gngcyerB3FY3K
H+BYhgUKQSjlNJYGeW3ZQrKBSQ/QFUbFX/BoMaRa6H2ewHYSCnGTwsNDUWDrBuhT
Tajdi27IJ0cWMMKLy640GF1/5dN8kmhSW/Hjw02TaxvK6QcD3ngn1hasp6x0KjDv
xNsC+x0RkU9hg0bxSCzTZCRrGk6y6X5Q+poos8GMwnMmLS99aQ6xP8VeVDVGowBe
GnlZxNVZ+Ecwk2lXoEzGMgrAOJFNRbGubieSF7euqtiIhNk/F6SLX4/qGjhr3Wxw
iWsN56sLnZJO8wIvBUUg8zs42iFxZtnt+1flQ+LsfWMFu5nEIscyGeQR7YYIAlVb
p24d3aN126qECXqPIui39zmGBQIjWV2JaQRGKle2nfnHV2q/Sco4Fer2V3BzwQMy
MvIeSdCJzERMP6ovtfISO87cT78WCDT707mRNgDc5vUOV069TqRICNrJGRlNqruX
6QGZubP0HlZ+L+DOisxmbWdX+YeVa1ih57ZlhGqH6UX8VAgQ6CeaiUjswRn56PTo
SxhfsEnDGI9C0steGMI8BGhVU0UuJa3bdr2CZb4PgDKksINUp1nrbjFO/3THrjzJ
PjPEybz79yZMXXjSycrGAhbXgq2QgBb1SpwS0poqtrJsluGEfnw=
=6R7b
-END PGP SIGNATURE End Message ---