Bug#911514: closing 911514

[Alexandre Rossi]

close 911514 5.0.0.2801-2~bpo9+1
thanks

Processed: closing 911514

[Debian Bug Tracking System]

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

> close 911514 5.0.0.2801-2~bpo9+1
Bug #911514 [davmail] davmail: fails to install: wrong update-rc.d usage
Marked as fixed in versions davmail/5.0.0.2801-2~bpo9+1.
Bug #911514 [davmail] davmail: fails to install: wrong update-rc.d usage
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#918769: ocaml-migrate-parsetree FTBFS:dh_install fails

[Ralf Treinen]

Source: ocaml-migrate-parsetree
Version: 1.2.0-1
Severity: serious
Tags: ftbfs

ocaml-migrate-parsetree fails to build on sid using debhelper version 12
(12 is the version of the debhelper package, I haven't touched the DH
compat level) :

dh_install: libmigrate-parsetree-ocamlbuild-ocaml missing files: 
usr/doc/ocaml-migrate-parsetree-ocamlbuild/{CHANGES.md,README.md,LICENSE.md}
dh_install: missing files, aborting
make: *** [debian/rules:8: binary] Error 25

-Ralf.

Bug#918768: opencolorio FTBFS with yaml-cpp 0.6.2

[Adrian Bunk]

Source: opencolorio
Version: 1.1.0~dfsg0-3
Severity: serious
Tags: ftbfs

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

...
/usr/bin/c++ -fPIC -g -O2 
-ffile-prefix-map=/build/1st/opencolorio-1.1.0~dfsg0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wshadow -Wconversion -Wcast-qual -Wformat=2 -Wl,-z,relro -shared 
-Wl,-soname,libOpenColorIO.so.1 -o libOpenColorIO.so.1.1.0 
CMakeFiles/OpenColorIO.dir/AllocationOp.cpp.o 
CMakeFiles/OpenColorIO.dir/AllocationTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/Baker.cpp.o 
CMakeFiles/OpenColorIO.dir/CDLTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/Caching.cpp.o 
CMakeFiles/OpenColorIO.dir/ColorSpace.cpp.o 
CMakeFiles/OpenColorIO.dir/ColorSpaceTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/Config.cpp.o 
CMakeFiles/OpenColorIO.dir/Context.cpp.o 
CMakeFiles/OpenColorIO.dir/Display.cpp.o 
CMakeFiles/OpenColorIO.dir/DisplayTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/Exception.cpp.o 
CMakeFiles/OpenColorIO.dir/ExponentOps.cpp.o 
CMakeFiles/OpenColorIO.dir/ExponentTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormat3DL.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatCC.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatCCC.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatCDL.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatCSP.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatHDL.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatIridasCube.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatIridasItx.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatIridasLook.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatPandora.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatSpi1D.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatSpi3D.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatSpiMtx.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatTruelight.cpp.o 
CMakeFiles/OpenColorIO.dir/FileFormatVF.cpp.o 
CMakeFiles/OpenColorIO.dir/FileTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/GpuShaderDesc.cpp.o 
CMakeFiles/OpenColorIO.dir/GpuShaderUtils.cpp.o 
CMakeFiles/OpenColorIO.dir/GroupTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/HashUtils.cpp.o 
CMakeFiles/OpenColorIO.dir/ImageDesc.cpp.o 
CMakeFiles/OpenColorIO.dir/ImagePacking.cpp.o 
CMakeFiles/OpenColorIO.dir/LogOps.cpp.o 
CMakeFiles/OpenColorIO.dir/LogTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/Logging.cpp.o CMakeFiles/OpenColorIO.dir/Look.cpp.o 
CMakeFiles/OpenColorIO.dir/LookParse.cpp.o 
CMakeFiles/OpenColorIO.dir/LookTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/Lut1DOp.cpp.o 
CMakeFiles/OpenColorIO.dir/Lut3DOp.cpp.o 
CMakeFiles/OpenColorIO.dir/MathUtils.cpp.o 
CMakeFiles/OpenColorIO.dir/MatrixOps.cpp.o 
CMakeFiles/OpenColorIO.dir/MatrixTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/NoOps.cpp.o 
CMakeFiles/OpenColorIO.dir/OCIOYaml.cpp.o CMakeFiles/OpenColorIO.dir/Op.cpp.o 
CMakeFiles/OpenColorIO.dir/OpOptimizers.cpp.o 
CMakeFiles/OpenColorIO.dir/ParseUtils.cpp.o 
CMakeFiles/OpenColorIO.dir/PathUtils.cpp.o 
CMakeFiles/OpenColorIO.dir/Platform.cpp.o 
CMakeFiles/OpenColorIO.dir/Processor.cpp.o 
CMakeFiles/OpenColorIO.dir/ScanlineHelper.cpp.o 
CMakeFiles/OpenColorIO.dir/Transform.cpp.o 
CMakeFiles/OpenColorIO.dir/TruelightOp.cpp.o 
CMakeFiles/OpenColorIO.dir/TruelightTransform.cpp.o 
CMakeFiles/OpenColorIO.dir/UnitTest.cpp.o 
CMakeFiles/OpenColorIO.dir/md5/md5.cpp.o 
CMakeFiles/OpenColorIO.dir/pystring/pystring.cpp.o -ltinyxml -lyaml-cpp 
/usr/bin/ld: CMakeFiles/OpenColorIO.dir/OCIOYaml.cpp.o: in function 
`YAML::BadSubscript::BadSubscript()':
/usr/include/yaml-cpp/exceptions.h:122: undefined reference to `vtable for 
YAML::Exception'
/usr/bin/ld: CMakeFiles/OpenColorIO.dir/OCIOYaml.cpp.o: relocation 
R_X86_64_PC32 against undefined hidden symbol `_ZTVN4YAML9ExceptionE' can not 
be used when making a shared object
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[3]: *** [src/core/CMakeFiles/OpenColorIO.dir/build.make:1004: 
src/core/libOpenColorIO.so.1.1.0] Error 1


The Ubuntu diff seems to contain a fix.

Bug#918767: rivet FTBFS with yaml-cpp 0.6.2

[Adrian Bunk]

Source: rivet
Version: 1.8.3-2
Severity: serious
Tags: ftbfs patch

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

...
In file included from /usr/include/c++/8/array:35,
 from /usr/include/yaml-cpp/node/convert.h:10,
 from /usr/include/yaml-cpp/yaml.h:18,
 from AnalysisInfo.cc:7:
/usr/include/c++/8/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support must 
be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support \


Fix attached.
Description: Don't force a lower C++ standard with -ansi
 This causes FTBFS with yaml-cpp 0.6.2.
Author: Adrian Bunk 

--- rivet-1.8.3.orig/configure.ac
+++ rivet-1.8.3/configure.ac
@@ -316,7 +316,6 @@ AM_CPPFLAGS="$AM_CPPFLAGS -I\$(BOOSTINCP
 AM_CPPFLAGS="$AM_CPPFLAGS -I\$(HEPMCINCPATH)"
 AM_CPPFLAGS="$AM_CPPFLAGS -I\$(FASTJETINCPATH)"
 AC_CEDAR_CHECKCXXFLAG([-pedantic], [AM_CXXFLAGS="$AM_CXXFLAGS -pedantic"])
-AC_CEDAR_CHECKCXXFLAG([-ansi], [AM_CXXFLAGS="$AM_CXXFLAGS -ansi"])
 AC_CEDAR_CHECKCXXFLAG([-Wall], [AM_CXXFLAGS="$AM_CXXFLAGS -Wall"])
 AC_CEDAR_CHECKCXXFLAG([-Wno-long-long], [AM_CXXFLAGS="$AM_CXXFLAGS 
-Wno-long-long"])
 AC_CEDAR_CHECKCXXFLAG([-Wno-format], [AM_CXXFLAGS="$AM_CXXFLAGS -Wno-format"])

Processed: Bug #917715 in openconnect marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917715 [src:openconnect] openconnect: FTBFS: dh_auto_test: make -j2 check 
VERBOSE=1 returned exit code 2
Added tag(s) pending.

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

Bug#917715: Bug #917715 in openconnect marked as pending

[Mike Miller]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/openconnect/commit/44cb37cd3f82e52b09306fa8298bb7e952341724


Update Build-Depends on ocserv (>= 0.12.1-2) to fix failing unit tests

Closes: #917715

Signed-off-by: Mike Miller 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917715

Bug#918569: Could not find 'activerecord' (~> 4.2) - did find: [activerecord-5.2.0]

[Pirate Praveen]

On Mon, 07 Jan 2019 22:39:41 +0100 t...@schleuder.org wrote:
> 
> Upstream (aka us) is working on switching to activerecord 5.2:
> https://0xacab.org/schleuder/schleuder/issues/372

Hi paz,

Would it be possible to upload a release candidate/dev version right now
to help with rails transition? You can update it to stable version as
per your current schedule.

Thanks
Praveen



signature.asc
Description: OpenPGP digital signature

Processed: forcibly merging 913789 913765

[Debian Bug Tracking System]

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

> forcemerge 913789 913765
Bug #913789 [wnpp] O: leafpad -- GTK+ based simple text editor
Bug #913765 [wnpp] O: leafpad -- GTK+ based simple text editor
Severity set to 'serious' from 'normal'
Merged 913765 913789
> thanks
Stopping processing here.

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

Bug#899632: marked as done (oss4: Invalid maintainer address pkg-oss4-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 9 Jan 2019 08:51:32 +0200
with message-id <20190109065132.GG13260@localhost>
and subject line Fixed in 4.2-build2017-1
has caused the Debian Bug report #899632,
regarding oss4: Invalid maintainer address 
pkg-oss4-maintain...@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.)


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

Dear uploader of oss4,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package oss4 since the list address
pkg-oss4-maintain...@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
pkg-oss4-maintain...@lists.alioth.debian.org is 1.

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 ---
Version: 4.2-build2017-1

oss4 (4.2-build2017-1) unstable; urgency=low
...
  * Set myself as maintainer until an oss4 team is reassembled.
...
 -- Samuel Thibault   Tue, 08 Jan 2019 23:51:07 +0100


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Axel Beckert]

Package: udev
Version: 240-2
Severity: critical
Justification: Breaks whole system

Hi,

I have no idea why this is happening, but several packages use "udevadm
control --reload-rules" in their postinst (e.g. fuse) and if that's run,
all process except init are instantly killed (reproducibly; the gettys
seem to be respawned by init then, so I can login locally again) and
since sshd is killed, too, the system is usually no more accessible from
remote (hence the severity "critical") despite still responding to ping
replies.

There's nothing in dmesg. And corekeeper didn't catch any core either.

Some more details which might be helpful:

* The udev daemon itself also vanishes and this happens independently of
  the udev daemon being running or not (i.e. "service udev start" before
  calling udevadm doesn't prevent this from happening).

* The other two udevadm command from fuse's postinst don't seem to
  trigger this:

  udevadm test --action -p  $(udevadm info -q path -n /dev/fuse)

* It first happened when I install linux-image-4.20-trunk-amd64 from
  experimental about a week ago or so. Since I was away from home until
  yesterday evening, I could only recently start to debug this.

Here's an strace of that command:

execve("/sbin/udevadm", ["udevadm", "control", "--reload-rules"], 
0x7ffd60743730 /* 39 vars */) = 0
brk(NULL)   = 0x561a4e851000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=446764, ...}) = 0
mmap(NULL, 446764, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f52728ca000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260A\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1824496, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f52728c8000
mmap(NULL, 1837056, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5272707000
mprotect(0x7f5272729000, 1658880, PROT_NONE) = 0
mmap(0x7f5272729000, 1343488, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7f5272729000
mmap(0x7f5272871000, 311296, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x16a000) = 0x7f5272871000
mmap(0x7f52728be000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b6000) = 0x7f52728be000
mmap(0x7f52728c4000, 14336, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f52728c4000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libkmod.so.2", O_RDONLY|O_CLOEXEC) 
= 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0206\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=100400, ...}) = 0
mmap(NULL, 102472, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f52726ed000
mprotect(0x7f52726f, 86016, PROT_NONE) = 0
mmap(0x7f52726f, 61440, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f52726f
mmap(0x7f52726ff000, 20480, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x12000) = 0x7f52726ff000
mmap(0x7f5272705000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7f5272705000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libacl.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\37\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=35488, ...}) = 0
mmap(NULL, 2130592, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f52724e4000
mprotect(0x7f52724eb000, 2097152, PROT_NONE) = 0
mmap(0x7f52726eb000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x7000) = 0x7f52726eb000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libblkid.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\257\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=343008, ...}) = 0
mmap(NULL, 345896, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f527248f000
mprotect(0x7f5272499000, 282624, PROT_NONE) = 0
mmap(0x7f5272499000, 212992, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7f5272499000
mmap(0x7f52724cd000, 65536, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x3e000) = 0x7f52724cd000
mmap(0x7f52724de000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4e000) = 

Processed: found 907414 in 3.3.7+dfsg-3

[Debian Bug Tracking System]

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

> found 907414 3.3.7+dfsg-3
Bug #907414 {Done: Xavier Guimard } [twitter-bootstrap3] 
twitter-bootstrap3: CVE-2018-14040 CVE-2018-14041 CVE-2018-14042
There is no source info for the package 'twitter-bootstrap3' at version 
'3.3.7+dfsg-3' with architecture ''
Unable to make a source version for version '3.3.7+dfsg-3'
Marked as found in versions 3.3.7+dfsg-3.
> thanks
Stopping processing here.

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

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

[Jeremy Bicha]

linsmith is now the last package keeping several libgnome libraries in
Debian Unstable. [1]

We'd like to remove those libraries soon, but I am willing to wait a
bit longer for someone to port linsmith to gtk3.

Note that the Debian Release Team requires your package to reach
Testing by February 12 to be included in the Buster release. [2]

[1] gnome-vfs, libbonobo, libbonoboui, libgnome, libgnome, libgnomeui, orbit2
[2] https://release.debian.org/buster/freeze_policy.html

Thanks,
Jeremy Bicha

Bug#917492: fam: FTBFS ('minor' was not declared in this scope)

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/19_glibc_2.28.patch: Fix FTBFS with glibc 2.28.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.18.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
only in patch2:
unchanged:
--- fam-2.7.0.orig/debian/patches/19_glibc_2.28.patch
+++ fam-2.7.0/debian/patches/19_glibc_2.28.patch
@@ -0,0 +1,17 @@
+## Description: Fix FTBFS against glibc 2.28
+## Origin/Author: Logan Rosen 
+## Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917492
+diff -Nur -x '*.orig' -x '*~' fam-2.7.0/build-tree/fam-2.7.0/src/DNotify.c++ 
fam-2.7.0.new/build-tree/fam-2.7.0/src/DNotify.c++
+--- fam-2.7.0/src/DNotify.c++  2019-01-08 23:35:20.513574095 -0500
 fam-2.7.0/src/DNotify.c++  2019-01-08 23:36:37.568605429 -0500
+@@ -36,6 +36,10 @@
+ #include 
+ #include 
+ 
++#ifdef __GNU_LIBRARY__
++#include 
++#endif
++
+ #include "DNotify.h"
+ 
+ #include "Interest.h"

Processed: Re: fam: FTBFS ('minor' was not declared in this scope)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #917492 [src:fam] fam: FTBFS ('minor' was not declared in this scope)
Added tag(s) patch.

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

Bug#917857: NMU diff for aufs 4.19+20181217-0.1

[Ben Hutchings]

On Tue, 2019-01-08 at 13:08 +0100, Jan Luca Naumann wrote:
> Hey,
> 
> thank you for the upload and your work. I am sorry that I did not manage
> to upload the new version due to too much other workload.

There's nothing to be sorry about.  I usually check that out-of-tree
module packages are up-to-date as we approach the freeze.  This time I
took the time to update some of them too.

> I have seen that your delete the dependency on linux-kbuild. I have
> added it to avoid transition of the aufs-packages to testing before the
> linux package is available in the requested version. One time there was
> the problem that the aufs-package already migrated but the linux package
> had some RC-bug.

That's a good point, which perhaps should have been recorded in the git
commit log or the changelog, so that I didn't think it was a mistake.
:-)  To expand on what I wrote in the changelog:

- In order to use aufs-dkms, it's necessary to install a linux-headers
  package for a suitable kernel version.
- If that linux-headers package is one built by Debian, it already
  depends on linux-kbuild-4.19.
- However, if it's a custom package built using "make deb-pkg", it
  includes all the kbuild scripts and other tools.  Then there's no
  need to install linux-kbuild-4.19 at all.

But I suppose the extra dependency doesn't matter that much.  You're
the maintainer and should of course add it back if you still think it's
justified.

It's unfortunate that backwards-compatibility for aufs is maintained
through separate git branches rather than conditional code.  None of
the other out-of-tree modules packaged for Debian seem to be like this.
I wonder if it would be possible to support multiple kernel versions
like this:

- When preparing the source package, run a script to generate diffs
  from the latest upstream branch to each older branch that's still
  maintained, and add those under the debian directory.
- When building the binary packages, include the diffs in aufs-dkms.
- When building under dkms, start by applying the appropriate diff for
  the target kernel version.  (You might need to copy-and-patch, as I'm
  not sure whether dkms will unpack the source again when building for
  a different version.)

I haven't spent a whole lot of time thinking about this, so this might
well be impractical.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug




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

Bug#851087: marked as done (cfengine2: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:16:48 +
with message-id 
and subject line Bug#918745: Removed package(s) from unstable
has caused the Debian Bug report #851087,
regarding cfengine2: Please migrate to openssl1.1 in buster
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.)


-- 
851087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfengine2
Version: 2.2.10-5
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/cfengine2_2.2.10-5_amd64-20160529-1410

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.2.10-7+rm

Dear submitter,

as the package cfengine2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/918745

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#915804: marked as done (Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:16:48 +
with message-id 
and subject line Bug#918745: Removed package(s) from unstable
has caused the Debian Bug report #915804,
regarding Should this package be removed?
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.)


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

This is replaced by src:cfengine2 and stretch has both cfengine2 and cfengine3,
so users can migrate within a stable release to 3.

The current version is also RC-buggy for a long time and blocks the removal
of OpenSSL 1.0.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 2.2.10-7+rm

Dear submitter,

as the package cfengine2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/918745

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#911285: marked as done (Current version is incompatible with Thunderbird 60)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:12:17 +
with message-id 
and subject line Bug#918693: Removed package(s) from unstable
has caused the Debian Bug report #911285,
regarding Current version is incompatible with Thunderbird 60
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.)


-- 
911285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-gcontactsync
Version: 2.0.13-1
Severity: grave

The version of gcontactsync in unstable is incompatible with the Thunderbird
version in unstable.

A new upstream version exists, that should be compatible.


Cheers,

Bastian


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

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

Versions of packages xul-ext-gcontactsync depends on:
ii  thunderbird  1:60.2.1-1

xul-ext-gcontactsync recommends no packages.

xul-ext-gcontactsync suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0.13-1+rm

Dear submitter,

as the package gcontactsync has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/918693

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#790601: marked as done (revelation: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:10:14 +
with message-id 
and subject line Bug#917210: Removed package(s) from unstable
has caused the Debian Bug report #790601,
regarding revelation: depends on python-gnome2 which is deprecated
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.)


-- 
790601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: revelation
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

revelation depends on python-gnome2, which is long deprecated and
going to be removed from the archive. revelation should be ported
away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove python-gnome2 this cycle.

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.4.14-3+rm

Dear submitter,

as the package revelation has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/917210

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#884986: marked as done (gnome-python: Do not release with Buster)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:10:52 +
with message-id 
and subject line Bug#917918: Removed package(s) from unstable
has caused the Debian Bug report #884986,
regarding gnome-python: Do not release with Buster
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.)


-- 
884986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-python
Severity: serious
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

python2-gnome is long deprecated and unmaintained. We should not
release Debian 10 "Buster" with it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

As of today, there are only 2 reverse-depends in Testing, guake (
#845949 ) and rapid-photo-downloader ( #790600 ) and those are already
marked for auto-removal soon. gnome-python won't be auto-removed
because of popcon.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.28.1+dfsg-1.2+rm

Dear submitter,

as the package gnome-python has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/917918

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#884988: marked as done (pyorbit: Do not release with Buster)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:11:25 +
with message-id 
and subject line Bug#917919: Removed package(s) from unstable
has caused the Debian Bug report #884988,
regarding pyorbit: Do not release with Buster
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.)


-- 
884988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyorbit
Severity: serious
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python pygorbit

We should not release Debian 10 "Buster" with pygorbit.

pyorbit is only in Debian because it is needed by gnome-python but
gnome-python will be removed soon. See https://bugs.debian.org/884986

pyorbit will not be autoremoved because of popcon.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.24.0-7.2+rm

Dear submitter,

as the package pyorbit has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/917919

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#820231: marked as done (ttf-marvosym: Consider to remove your package)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 04:09:29 +
with message-id 
and subject line Bug#881704: Removed package(s) from unstable
has caused the Debian Bug report #820231,
regarding ttf-marvosym: Consider to remove your package
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.)


-- 
820231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ttf-marvosym
Version: 0.1+dfsg-2
Severity: minor

http://www.martinvogel.de/blog/index.php?/archives/131-Marvosym.ttf.html

This is the blog of Martin Vogel, the author of the marvosym fonts. In this
entry he basically states that the fonts he created are obsoleted and
superseded by the Unicode meanwhile. The fonts are not used anymore even by
himself.
Consider to remove your package from Debian.



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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.1+dfsg-3+rm

Dear submitter,

as the package ttf-marvosym has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881704

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#884476: marked as done (derivations FTBFS with poppler 0.61.1)

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 03:19:43 +
with message-id 
and subject line Bug#884476: fixed in derivations 0.56.20180123.1-2
has caused the Debian Bug report #884476,
regarding derivations FTBFS with poppler 0.61.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.)


-- 
884476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: derivations
Version: 0.53.20120414-2
Severity: serious
Tags: buster sid

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

...
update_catalog.cc: In function 'int {anonymous}::copy_but(Dict*, Dict*, const 
set&)':
update_catalog.cc:39:33: error: no matching function for call to 
'Dict::getValNF(int&, Object*)'
   src ->getValNF( i  ,  );
 ^
In file included from /usr/include/poppler/Object.h:342:0,
 from /usr/include/poppler/XRef.h:42,
 from /usr/include/poppler/PDFDoc.h:49,
 from PDF_rep.h:6,
 from update_catalog.cc:12:
/usr/include/poppler/Dict.h:85:10: note: candidate: Object Dict::getValNF(int) 
const
   Object getValNF(int i) const;
  ^~~~
--- End Message ---
--- Begin Message ---
Source: derivations
Source-Version: 0.56.20180123.1-2

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

Debian distribution maintenance software
pp.
Thaddeus H. Black  (supplier of updated derivations package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Jan 2019 01:00:00 +
Source: derivations
Binary: derivations
Architecture: source all
Version: 0.56.20180123.1-2
Distribution: unstable
Urgency: low
Maintainer: Thaddeus H. Black 
Changed-By: Thaddeus H. Black 
Description:
 derivations - book: Derivations of Applied Mathematics
Closes: 884476
Changes:
 derivations (0.56.20180123.1-2) unstable; urgency=low
 .
   * Reconfigured and rebuilt for upload to Debian sid.
   * Conformed to Standards-Version 4.3.0.
   * Conformed btool/ to sid's Poppler, version 0.69 (closes: #884476).
 Required at least this version of Poppler to build.
Checksums-Sha1:
 73aae3262b4d6ceb6ed7fbe3ef6e7089dd942f92 1982 derivations_0.56.20180123.1-2.dsc
 1f7ae80f8a49c87964485a0b40ee7a9179171098 470008 
derivations_0.56.20180123.1.orig.tar.xz
 0def421b9d1ddfba65c3ac3be98b80ac02167c35 31380 
derivations_0.56.20180123.1-2.debian.tar.xz
 1dec28fa89760c13839d793dfa3d17f90c7bff63 3150008 
derivations_0.56.20180123.1-2_all.deb
 272ee9b1d2f1710bc5dd178620033f951323efe5 8860 
derivations_0.56.20180123.1-2_amd64.buildinfo
Checksums-Sha256:
 d5ef7bbca9b2e63e9425a36fe71762dd08b261effd100f4f4013f3a1c7d2c050 1982 
derivations_0.56.20180123.1-2.dsc
 ffd5c2cc825cec90a2c56001d2aafa2b497a2512bb532e528989c9e6c830afb5 470008 
derivations_0.56.20180123.1.orig.tar.xz
 739b7e6239576e1995b07c88a8bfaafeb46789d7f540ef797308bffd3f37a5b5 31380 
derivations_0.56.20180123.1-2.debian.tar.xz
 cc3b0d19027531ff89e25ae9932a9c76b3b88c2999352587ad350af9eafd5dfd 3150008 
derivations_0.56.20180123.1-2_all.deb
 b13cbcc1470a09e74ae2878eb8e0b2d1fe9315e5eeb4905f3a3d798db9d22ed3 8860 
derivations_0.56.20180123.1-2_amd64.buildinfo
Files:
 3daa3946ad5757f1585761eca4712acd 1982 doc optional 
derivations_0.56.20180123.1-2.dsc
 00e5e426f62273b6754fde172adbba42 470008 doc optional 
derivations_0.56.20180123.1.orig.tar.xz
 27d8a4c676820c5414f93e0553c18b93 31380 doc optional 
derivations_0.56.20180123.1-2.debian.tar.xz
 cd67e2323e39376eb1333fc8a9f2c88a 3150008 doc optional 
derivations_0.56.20180123.1-2_all.deb
 392cce698cc89a5422aebf9a52679902 8860 doc optional 
derivations_0.56.20180123.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEM1APDU+pwMhnuF4GcGMmQy2FIrwFAlwyu7gPHHRoYkBkZWJp
YW4ub3JnAAoJEHBjJkMthSK8dAcQAOuVeaj8Ai2lfTNRy4Xmja9uTpOQGQReaIJa
5qkJzU3H5U+EjWs5TxI3EohjBh+Q+plwbaNEOmOwF095moreQq0D1yk2pn1+AZlm
q9/0FyQ9BJOsnlgbk0uPt2oBNMwtrWuZYZDedKKfaRmEWLuOJbIa3DDeY5YOTsbG
+GxkomabMKXf8zh0expCcKawzXcdLw/e68XGbYxHRtbJnvy1cu8ZRCMsLuVU3p5f

Processed: Bug #917708 in gnome-settings-daemon marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917708 [src:gnome-settings-daemon] gnome-settings-daemon: FTBFS: 
dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 
ninja test returned exit code 1
Ignoring request to alter tags of bug #917708 to the same tags previously set

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

Bug#917708: Bug #917708 in gnome-settings-daemon marked as pending

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #917708 in gnome-settings-daemon reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gnome-settings-daemon/commit/aec00958e71bb04eb0d885afa5dd4a98f67dc625


Cherry-pick color-tests-allow-Goldstar-and-LG-as-vendor-name.patch:

- Fix tests with systemd 240

Closes: #917708


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917708

Bug#914112: marked as done (galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)')

[Debian Bug Tracking System]

Your message dated Wed, 09 Jan 2019 00:49:10 +
with message-id 
and subject line Bug#914112: fixed in galera-3 25.3.25-1
has caused the Debian Bug report #914112,
regarding galera-3 FTBFS: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
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.)


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

https://buildd.debian.org/status/package.php?p=galera-3=sid

...
galera/src/ist.cpp: In constructor 
'galera::ist::Receiver::Receiver(gu::Config&, galera::TrxHandle::SlavePool&, 
const char*)':
galera/src/ist.cpp:108:25: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
 ready_(false)
 ^
In file included from /usr/include/asio/ssl/context.hpp:755,
 from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/impl/context.ipp:62:1: note: candidate: 
'asio::ssl::context::context(asio::ssl::context_base::method)'
 context::context(context::method m)
 ^~~
/usr/include/asio/ssl/impl/context.ipp:62:1: note:   candidate expects 1 
argument, 2 provided
In file included from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/context.hpp:35:7: note: candidate: 
'asio::ssl::context::context(const asio::ssl::context&)'
 class context
   ^~~
/usr/include/asio/ssl/context.hpp:35:7: note:   candidate expects 1 argument, 2 
provided
galera/src/ist.cpp: In constructor 'galera::ist::Sender::Sender(const 
gu::Config&, gcache::GCache&, const string&, int)':
galera/src/ist.cpp:637:22: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
 use_ssl_   (false)
  ^
In file included from /usr/include/asio/ssl/context.hpp:755,
 from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/impl/context.ipp:62:1: note: candidate: 
'asio::ssl::context::context(asio::ssl::context_base::method)'
 context::context(context::method m)
 ^~~
/usr/include/asio/ssl/impl/context.ipp:62:1: note:   candidate expects 1 
argument, 2 provided
In file included from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/context.hpp:35:7: note: candidate: 
'asio::ssl::context::context(const asio::ssl::context&)'
 class context
   ^~~
/usr/include/asio/ssl/context.hpp:35:7: note:   candidate expects 1 argument, 2 
provided
In file included from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
galerautils/src/gu_asio.hpp: In instantiation of 'void gu::set_fd_options(S&) 
[with S = asio::basic_socket_acceptor]':
galera/src/ist.cpp:317:37:   required from here
galerautils/src/gu_asio.hpp:197:26: error: 'class 
asio::basic_socket_acceptor' has no member named 'native'
 if (fcntl(socket.native(), F_SETFD, flags) == -1)
   ~~~^~
galerautils/src/gu_asio.hpp: In instantiation of 'void gu::set_fd_options(S&) 
[with S = asio::basic_socket]':
galera/src/ist.cpp:366:57:   required from here
galerautils/src/gu_asio.hpp:197:26: error: 'class 
asio::basic_socket' has no member named 'native'
galerautils/src/gu_asio.hpp: In instantiation of 'void gu::set_fd_options(S&) 
[with S = asio::basic_stream_socket]':
galera/src/ist.cpp:372:38:   required from here
galerautils/src/gu_asio.hpp:197:26: error: 'class 
asio::basic_stream_socket' has no member named 'native'
galera/src/ist.cpp: In constructor 
'galera::ist::Receiver::Receiver(gu::Config&, galera::TrxHandle::SlavePool&, 
const char*)':
galera/src/ist.cpp:108:25: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
 ready_(false)
 ^
In file included from /usr/include/asio/ssl/context.hpp:755,
 

Bug#918751: python-shade: FTBFS in sid

[Santiago Vila]

I said:

> I tried to build this package in buster but it failed:
Sorry for this typo, I meant sid of course.

Bug#918751: python-shade: FTBFS in sid

[Santiago Vila]

Package: src:python-shade
Version: 1.30.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2 --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_shade/build/shade
creating /<>/.pybuild/cpython2_2.7_shade/build/shade/tests

[... snipped ...]

b'"id": "v2.0",'
b'"links": ['
b'  {'
b'"href": "https://identity.example.com/v2.0/;,'
b'"rel": "self"'
b'  },'
b'  {'
b'"href": "http://docs.openstack.org/;,'
b'"type": "text/html",'
b'"rel": "describedby"'
b'  }'
b']'
b'  }'
b']'
b'  }'
b'}'
b''
b'2019-01-09 00:07:23,806 shade.task_manager   Manager 
_test_cloud_:RegionOne ran task 
object-store.PUT.shade.tests.unit.test_object.TestObjectUploads.test_object_segment_retry_failure-2.02
 in 0.966373920441s'
b'2019-01-09 00:07:23,826 keystoneauth.identity.v3.baseMaking 
authentication request to https://identity.example.com/v3/auth/tokens'
b'2019-01-09 00:07:23,943 keystoneauth.identity.v3.base{"token": 
{"methods": ["password"], "roles": [{"id": "9fe2ff9ee4384b1894a90878d3e92bab", 
"name": "_member_"}, {"id": "37071fc082e14c2284c32a2761f71c63", "name": 
"swiftoperator"}], "expires_at": "-12-31T23:59:59Z", "project": {"domain": 
{"id": "default", "name": "default"}, "id": "1c36b64c840a42cd9e9b931a369337f0", 
"name": "Default Project"}, "catalog": [{"endpoints": [{"interface": "public", 
"url": "https://compute.example.com/v2.1/;, "region": "RegionOne", "id": 
"32466f357f3545248c47471ca51b0d3a"}], "type": "compute", "name": "nova"}, 
{"endpoints": [{"interface": "public", "url": 
"https://volume.example.com/v2/1c36b64c840a42cd9e9b931a369337f0;, "region": 
"RegionOne", "id": "1e875ca2225b408bbf3520a1b8e1a537"}], "type": "volumev2", 
"name": "cinderv2"}, {"endpoints": [{"interface": "public", "url": 
"https://image.example.com;, "region": "RegionOne", "id": 
"5a64de3c4a614d8d8f8d1ba3dee5f45f"}], "type": "image", "name": "g
 lance"}, {"endpoints": [{"interface": "public", "url": 
"https://volume.example.com/v1/1c36b64c840a42cd9e9b931a369337f0;, "region": 
"RegionOne", "id": "3d15fdfc7d424f3c8923324417e1a3d1"}], "type": "volume", 
"name": "cinder"}, {"endpoints_links": [], "endpoints": [{"interface": 
"public", "url": "https://identity.example.com;, "region": "RegionOne", "id": 
"4deb4d0504a044a395d4480741ba628c"}, {"interface": "admin", "url": 
"https://identity.example.com;, "region": "RegionOne", "id": 
"012322eeedcd459edabb4933021112bc"}], "type": "identity", "name": "keystone"}, 
{"endpoints_links": [], "endpoints": [{"interface": "public", "url": 
"https://network.example.com;, "region": "RegionOne", "id": 
"4deb4d0504a044a395d4480741ba628d"}], "type": "network", "name": "neutron"}, 
{"endpoints_links": [], "endpoints": [{"interface": "public", "url": 
"https://container-infra.example.com/v1;, "region": "RegionOne", "id": 
"4deb4d0504a044a395d4480741ba628e"}], "type": "container-infra", "name": 
"magnum"}, {"end
 points_links": [], "endpoints": [{"interface": "public", "url": 
"https://object-store.example.com/v1/1c36b64c840a42cd9e9b931a369337f0;, 
"region": "RegionOne", "id": "4deb4d0504a044a395d4480741ba628c"}], "type": 
"object-store", "name": "swift"}, {"endpoints_links": [], "endpoints": 
[{"interface": "public", "url": "https://bare-metal.example.com/;, "region": 
"RegionOne", "id": "652f0612744042bfbb8a8bb2c777a16d"}], "type": "baremetal", 
"name": "ironic"}, {"endpoints_links": [], "endpoints": [{"interface": 
"public", "url": 
"https://orchestration.example.com/v1/1c36b64c840a42cd9e9b931a369337f0;, 
"region": "RegionOne", "id": "4deb4d0504a044a395d4480741ba628c"}], "type": 
"orchestration", "name": "heat"}, {"endpoints_links": [], "endpoints": 
[{"interface": "public", "url": "https://dns.example.com;, "region": 
"RegionOne", "id": "10c76ffd2b744a67950ed1365190d352"}], "type": "dns", "name": 
"designate"}], "user": {"domain": {"id": "default", "name": "default"}, "id": 
"c17534835f8f42bf98fc367e0
 bf35e09", "name": "mordred"}, "audit_ids": ["Rvn7eHkiSeOwucBIPaKdYA"], 
"issued_at": "2016-12-17T14:25:05.00Z"}}'
b'2019-01-09 00:07:24,016 shade.task_manager   Manager 
defaults: running task baremetal.GET.nodes'
b'2019-01-09 00:07:24,063 keystoneauth.session REQ: curl -g -i 
-X GET 

Bug#829255: marked as done (oss4-dkms: Fails to build for 4.6.0-1-amd64)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 23:20:46 +
with message-id 
and subject line Bug#827674: fixed in oss4 4.2-build2017-1
has caused the Debian Bug report #827674,
regarding oss4-dkms: Fails to build for 4.6.0-1-amd64
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.)


-- 
827674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: oss4-dkms
Version: 4.2-build2010-5
Severity: serious

Dear Maintainer,

the oss4 modules fail to build for the current sid kernel (4.6.0-1) on amd64:

In file included from 
/var/lib/dkms/oss4/4.2-build2010/build/drivers/oss_ali5455module.c:21:0:
/var/lib/dkms/oss4/4.2-build2010/build/drivers/module.inc:52:13: error: 
initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
[...]
/usr/src/linux-headers-4.6.0-1-common/scripts/Makefile.build:296: recipe for 
target '/var/lib/dkms/oss4/4.2-build2010/build/drivers/oss_ali5455module.o' 
failed

Best,
Chris


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: oss4
Source-Version: 4.2-build2017-1

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated oss4 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: Tue, 08 Jan 2019 23:51:07 +0100
Source: oss4
Binary: oss4-base oss4-gtk oss4-dkms oss4-source oss4-dev liboss4-salsa2 
liboss4-salsa-dev liboss4-salsa-asound2
Architecture: source amd64 all
Version: 4.2-build2017-1
Distribution: unstable
Urgency: low
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 liboss4-salsa-asound2 - OSS to Alsa compatibility library - binary 
compatibility symlink
 liboss4-salsa-dev - OSS to Alsa compatibility library -- development files
 liboss4-salsa2 - OSS to Alsa compatibility library
 oss4-base  - Open Sound System - base package
 oss4-dev   - Open Sound System - development files
 oss4-dkms  - Open Sound System - DKMS module sources
 oss4-gtk   - Open Sound System - simple GTK2-based mixer control
 oss4-source - Open Sound System - drivers sources
Closes: 620627 827674 834993 916005
Changes:
 oss4 (4.2-build2017-1) unstable; urgency=low
 .
   [ Sébastien Noel ]
   * New upstream release.
 .
   [ Samuel Thibault ]
   * New upstream release. (Closes: #827674)
   * control: Bump Standards-Version to 3.9.8 (no change).
   * 30oss4-pm, oss4-dkms.postinst: invoke-rc.d is now essential.
   * Use https URL
   * 503_glibc_2.28.patch: Fix build against glibc 2.28 (Closes: #916005)
   * 501_linux_version.patch: Drop, fixed upstream.
   * debian/include-alsa/alsa/mixer.h: Fix
 snd_mixer_selem_set_playback_volume_range prototype (Closes: #620627).
   * debian/include-alsa/alsa/version.h: Bump alsa version accordingly.
   * Set myself as maintainer until an oss4 team is reassembled.
   * rules: Drop spurious .o upstream files.
 .
   [ Reiner Herrmann ]
   * Reproducible build fixes (Closes: #834993)
   * Use system txt2man in upstream build script (build.sh), which supports
 SOURCE_DATE_EPOCH.
   * Use SOURCE_DATE_EPOCH for the generated build-id.
   * Sort files in modules tarball, fix permissions and timestamps.
   * Fix ordering issues in some other places.
Checksums-Sha1:
 b7f542f32acfce33d23d6c9d28e35bd9f33ca51e 2526 oss4_4.2-build2017-1.dsc
 6cb267e35ecb7bf84554f8c09ea7d2fe8ae174f3 1856756 
oss4_4.2-build2017.orig.tar.bz2
 7f75f24523d791198857caaff083c71bf4c4fa92 67896 
oss4_4.2-build2017-1.debian.tar.xz
 ddc024a3927cbe278f9f9498e0c97b9886564ad6 8288 
liboss4-salsa-asound2_4.2-build2017-1_amd64.deb
 e7b59d791a36e0b54518054418578176a6571f40 9872 
liboss4-salsa2-dbgsym_4.2-build2017-1_amd64.deb
 

Bug#827674: marked as done (Build of oss4-dkms fails)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 23:20:46 +
with message-id 
and subject line Bug#827674: fixed in oss4 4.2-build2017-1
has caused the Debian Bug report #827674,
regarding Build of oss4-dkms fails
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.)


-- 
827674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: oss4-dkms
Version: 4.2-build2010-5
Severity: important

Today I tried dkms after long time. But the essential package oss4-dkms
did fail with the attached log.

It seems to be not related to dkms as a build with module-assistant does
fail too.

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

Kernel: Linux 4.5.7 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages oss4-dkms depends on:
pn  dkms  
ii  dpkg-dev  1.18.7+ket1
ii  libc6-dev [libc-dev]  2.22-11
ii  oss4-base 4.2-build2010-5

Versions of packages oss4-dkms recommends:
pn  linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic  

oss4-dkms suggests no packages.

-- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
DKMS make.log for oss4-4.2-build2010 for kernel 4.6.0-1-686-pae (i686)
So 19. Jun 15:04:33 CET 2016
make: Verzeichnis »/usr/src/linux-headers-4.6.0-1-686-pae« wird betreten
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o
/var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.c: In function 
'oss_cmn_err':
/var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.c:697:1: warning: the 
frame size of 1028 bytes is larger than 1024 bytes [-Wframe-larger-than=]
 }
 ^
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/os_linux.o
/var/lib/dkms/oss4/4.2-build2010/build/core/os_linux.c: In function 
'osdev_create_201601311609':
/var/lib/dkms/oss4/4.2-build2010/build/core/os_linux.c:162:10: warning: 
assignment discards 'const' qualifier from pointer target type 
[-Wdiscarded-qualifiers]
  devpath = oss_pci_read_devpath (osdev->dip);
  ^
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_ac97.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_audio_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_audiofmt.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_grc3.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_spdif.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_default_timer.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_midi_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_midi_mapper.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_midi_parser.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_midi_queue.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_midi_timers.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_midi_stubs.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_mixer_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core_options.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core_services.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_memblk.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_remux.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_sndstat.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_uart401.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/vmix_core.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/vmix_input.o
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/vmix_output.o
  LD [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/osscore.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  /var/lib/dkms/oss4/4.2-build2010/build/core/osscore.mod.o
  LD [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/osscore.ko
make: Verzeichnis »/usr/src/linux-headers-4.6.0-1-686-pae« wird verlassen
make: Verzeichnis »/var/lib/dkms/oss4/4.2-build2010/build/drivers« wird betreten
echo "static const struct modversion_info versions[]" >> osscore_symbols.inc
echo " __attribute__((used))" >> osscore_symbols.inc
echo "__attribute__((section(\"__versions\"))) = {" >> osscore_symbols.inc
sed -e "s:^:{:" -e "s:\t:, \":" -e "s:\t\(.\)*:\"},:" < Module.symvers 

Bug#916005: marked as done (oss4 FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 23:20:46 +
with message-id 
and subject line Bug#916005: fixed in oss4 4.2-build2017-1
has caused the Debian Bug report #916005,
regarding oss4 FTBFS with glibc 2.28
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.)


-- 
916005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oss4
Version: 4.2-build2010-5
Severity: serious
Tags: ftbfs

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

...
ossdetect.c: In function 'create_devlinks':
ossdetect.c:564:31: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   if (mknod (dev, node_m, makedev (major, minor)) == -1)
   ^~~
cc -O -s -o ../../../target/sbin/ossdetect ./ossdetect.o   
/usr/bin/ld: ./ossdetect.o: in function `main':
ossdetect.c:(.text+0xf2c): undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:34: ../../../target/sbin/ossdetect] Error 1
--- End Message ---
--- Begin Message ---
Source: oss4
Source-Version: 4.2-build2017-1

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated oss4 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: Tue, 08 Jan 2019 23:51:07 +0100
Source: oss4
Binary: oss4-base oss4-gtk oss4-dkms oss4-source oss4-dev liboss4-salsa2 
liboss4-salsa-dev liboss4-salsa-asound2
Architecture: source amd64 all
Version: 4.2-build2017-1
Distribution: unstable
Urgency: low
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 liboss4-salsa-asound2 - OSS to Alsa compatibility library - binary 
compatibility symlink
 liboss4-salsa-dev - OSS to Alsa compatibility library -- development files
 liboss4-salsa2 - OSS to Alsa compatibility library
 oss4-base  - Open Sound System - base package
 oss4-dev   - Open Sound System - development files
 oss4-dkms  - Open Sound System - DKMS module sources
 oss4-gtk   - Open Sound System - simple GTK2-based mixer control
 oss4-source - Open Sound System - drivers sources
Closes: 620627 827674 834993 916005
Changes:
 oss4 (4.2-build2017-1) unstable; urgency=low
 .
   [ Sébastien Noel ]
   * New upstream release.
 .
   [ Samuel Thibault ]
   * New upstream release. (Closes: #827674)
   * control: Bump Standards-Version to 3.9.8 (no change).
   * 30oss4-pm, oss4-dkms.postinst: invoke-rc.d is now essential.
   * Use https URL
   * 503_glibc_2.28.patch: Fix build against glibc 2.28 (Closes: #916005)
   * 501_linux_version.patch: Drop, fixed upstream.
   * debian/include-alsa/alsa/mixer.h: Fix
 snd_mixer_selem_set_playback_volume_range prototype (Closes: #620627).
   * debian/include-alsa/alsa/version.h: Bump alsa version accordingly.
   * Set myself as maintainer until an oss4 team is reassembled.
   * rules: Drop spurious .o upstream files.
 .
   [ Reiner Herrmann ]
   * Reproducible build fixes (Closes: #834993)
   * Use system txt2man in upstream build script (build.sh), which supports
 SOURCE_DATE_EPOCH.
   * Use SOURCE_DATE_EPOCH for the generated build-id.
   * Sort files in modules tarball, fix permissions and timestamps.
   * Fix ordering issues in some other places.
Checksums-Sha1:
 b7f542f32acfce33d23d6c9d28e35bd9f33ca51e 2526 oss4_4.2-build2017-1.dsc
 6cb267e35ecb7bf84554f8c09ea7d2fe8ae174f3 1856756 
oss4_4.2-build2017.orig.tar.bz2
 7f75f24523d791198857caaff083c71bf4c4fa92 67896 
oss4_4.2-build2017-1.debian.tar.xz
 ddc024a3927cbe278f9f9498e0c97b9886564ad6 8288 
liboss4-salsa-asound2_4.2-build2017-1_amd64.deb
 e7b59d791a36e0b54518054418578176a6571f40 9872 
liboss4-salsa2-dbgsym_4.2-build2017-1_amd64.deb
 2ea040986c477add8191ff279614cbc35fba4208 43680 
liboss4-salsa2_4.2-build2017-1_amd64.deb
 2ec744cdad4123fd8ffb664c99d356653c0200d8 534020 
oss4-base_4.2-build2017-1_amd64.deb
 586a0589c67dd795ca7ff64c4ff121d046bdc442 28692 oss4-dev_4.2-build2017-1_all.deb
 

Processed: tagging 918741

[Debian Bug Tracking System]

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

> tags 918741 + buster sid
Bug #918741 [src:fakechroot] Build-Depends on deprecated libjemalloc SONAME 
directly
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 918742

[Debian Bug Tracking System]

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

> tags 918742 + buster sid
Bug #918742 [src:fakechroot] Initialization loop/deadlock when used with 
jemalloc
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#918746: Should this package be removed?

[Moritz Muehlenhoff]

Source: pam-ssh-agent-auth
Severity: serious

Should pam-ssh-agent-auth be removed from the archive?

It seems dead upstream, the last commits are from March 2014, it's broken
with OpenSSL 1.1 and was removed from testing more than a year ago. It's
also one of the few remaining packages blocking the removal of OpenSSL 1.0.

Cheers,
Moritz
  

Bug#915804: Should this package be removed?

[Moritz Mühlenhoff]

On Wed, Dec 19, 2018 at 11:56:47PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote:
> > Source: cfengine2
> > Severity: serious
> > 
> > This is replaced by src:cfengine2 and stretch has both cfengine2 and 
> > cfengine3,
> > so users can migrate within a stable release to 3.
> > 
> > The current version is also RC-buggy for a long time and blocks the removal
> > of OpenSSL 1.0.
> 
> cfengine2 is like a decade old. I found nothing in their blog. Only the
> convert tool:
>   https://cfengine.com/company/blog-detail/cfengine-2-conversion-tool/

No objections to my bug for a month, so I went ahead and filed a removal
bug.

Cheers,
Moritz

Bug#918742: Initialization loop/deadlock when used with jemalloc

[Faidon Liambotis]

Package: src:fakechroot
Version: 2.19-3
Severity: serious

Hi again,

So jemalloc 5.1.0-2 was recently uploaded to unstable. The build
currently fails due to the explicit dependency on libjemalloc1 (cf.
#918741), but as soon as this gets fixed, another issue is uncovered:

While building this package, the jemalloc test deadlocks, and the build
hangs. This can be easily reproduced as follows:
  apt install libfakechroot libjemalloc2
  LD_PRELOAD="libjemalloc.so.2 libfakechroot.so" /bin/true
  

The test isn't spurious but an actual issue. One could do:
  fakechroot 
...and still hit this bug.

The bug is effectively the same as #872669, which I had previously
resolved by disabling jemalloc's --enable-prof. This option was
re-enabled in 5.x (I forgot about that bug :/) and...  I'd like to keep
it that way, so I tried to troubleshoot this further.

It looks like there's a preloading loop between those libraries that
results in deadlocking. Effectively, during its initialization
(malloc_init) jemalloc tries to initialize libgcc's unwind code
(_Unwind_Backtrace), which in turn calls dl_iterate_phdr, which is
captured by libfakechroot, which calls dlsym()/dlerror(), which tries to
allocate memory back again, which deadlocks jemalloc.

The backtrace is (note how #6 and #20 are the same):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
#1  0x7fd764008704 in __GI___pthread_mutex_lock (mutex=0x7fd7647a0500 
) at ../nptl/pthread_mutex_lock.c:80
#2  0x7fd76475f0dc in malloc_mutex_lock_final (mutex=0x7fd7647a04c0 
) at include/jemalloc/internal/mutex.h:141
#3  je_malloc_mutex_lock_slow (mutex=mutex@entry=0x7fd7647a04c0 ) at 
src/mutex.c:84
#4  0x7fd76470e244 in malloc_mutex_lock (mutex=0x7fd7647a04c0 , 
tsdn=0x0) at include/jemalloc/internal/mutex.h:205
#5  malloc_init_hard () at src/jemalloc.c:1506
#6  0x7fd76471524d in malloc_init () at src/jemalloc.c:217
#7  imalloc (dopts=, sopts=) at 
src/jemalloc.c:1986
#8  calloc (num=num@entry=1, size=size@entry=32) at src/jemalloc.c:2138
#9  0x7fd763ff8a25 in _dlerror_run (operate=operate@entry=0x7fd763ff8390 
, args=args@entry=0x7ffdd14ddfa0) at dlerror.c:141
#10 0x7fd763ff840f in __dlsym (handle=, name=) at dlsym.c:70
#11 0x7fd7644f49b4 in ?? () from 
/usr/lib/x86_64-linux-gnu/fakechroot/libfakechroot.so
#12 0x7fd7644edffc in dl_iterate_phdr () from 
/usr/lib/x86_64-linux-gnu/fakechroot/libfakechroot.so
#13 0x7fd763ff02a1 in _Unwind_Find_FDE (pc=0x7fd763fee867 
<_Unwind_Backtrace+55>, bases=bases@entry=0x7ffdd14de368) at 
../../../src/libgcc/unwind-dw2-fde-dip.c:469
#14 0x7fd763fec983 in uw_frame_state_for 
(context=context@entry=0x7ffdd14de2c0, fs=fs@entry=0x7ffdd14de110) at 
../../../src/libgcc/unwind-dw2.c:1257
#15 0x7fd763fedb60 in uw_init_context_1 (context=0x7ffdd14de2c0, 
outer_cfa=0x7ffdd14de570, outer_ra=0x7fd76476a878 )
at ../../../src/libgcc/unwind-dw2.c:1586
#16 0x7fd763fee868 in _Unwind_Backtrace (trace=trace@entry=0x7fd76475fdb0 
, trace_argument=trace_argument@entry=0x0)
at ../../../src/libgcc/unwind.inc:295
#17 0x7fd76476a878 in je_prof_boot2 (tsd=tsd@entry=0x7fd763fd7740) at 
src/prof.c:2392
#18 0x7fd76470e308 in malloc_init_hard () at src/jemalloc.c:1538
#19 malloc_init_hard () at src/jemalloc.c:1500
#20 0x7fd764710a85 in malloc_init () at src/jemalloc.c:217

I don't think it's a bug on either library per se. I was wondering if
you had any insight on how we could address this in fakechroot somehow
rather than in jemalloc, as that doesn't look to be easy without
disabling the profiling feature.

Regards,
Faidon

Bug#918740: marked as done (rdkit: baseline violation on amd64/i386 and FTBFS everywhere else)

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 23:19:50 +0100
with message-id <20190108221950.gm19...@nighthawk.caipicrew.dd-dns.de>
and subject line Re: [Debichem-devel] Bug#918740: rdkit: baseline violation on 
amd64/i386 and FTBFS everywhere else
has caused the Debian Bug report #918740,
regarding rdkit: baseline violation on amd64/i386 and FTBFS everywhere else
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.)


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

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

...
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation 
-Wno-stringop-truncation -g -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 
-fdebug-prefix-map=/<>/rdkit-201803.4+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/local/include -I/<>/rdkit-201803.4+dfsg/Code 
-DRDKITVER='"007300"'   -DUSE_BUILTIN_POPCOUNT -mpopcnt -I. 
-I/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit 
-I/usr/include/postgresql/11/server -I/usr/include/postgresql/internal  
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  
-I/usr/include/mit-krb5 -fPIC -c -o rdkit_io.o 
/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit/rdkit_io.c
gcc: error: unrecognized command line option '-mpopcnt'
make[2]: *** [/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit/Makefile:101: 
rdkit_io.o] Error 1


Due to Code/PgSQL/rdkit/Makefile:
POPCOUNTFLAGS=-DUSE_BUILTIN_POPCOUNT -mpopcnt
--- End Message ---
--- Begin Message ---
On Tue, Jan 08, 2019 at 11:37:38PM +0200, Adrian Bunk wrote:
> Source: rdkit
> Version: 201803.4+dfsg-2
> Severity: serious
> Tags: ftbfs
> 
> gcc: error: unrecognized command line option '-mpopcnt'
> make[2]: *** 
> [/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit/Makefile:101: rdkit_io.o] 
> Error 1

Fixed in -3.


Michael--- End Message ---

Bug#918467: lxpanel: Weather plugin uses obsolete APIs, does not work.

[Andriy Grytsenko]

Yes, Yahoo unfortunately ended free service at January 3.

New API requires registering the application and has unknown restrictions
which probably will lead the weather plugin to DoS situation, because if
developer registers API to get a key then that limitation will be applied
to each user of that API so may be soon exceeded.

Abother issue that new Yahoo API requires digital signature for each
request which in turn will involve libssl with all their restrictions.

Unfortunately all weather providers now made their API available via some
kind of registration. We can force each user to register but that will be
pretty inconvenient for users. Another approach is to register some token
for LXDE developers public e-mail but if (for example) 50 users will
use the plugin and we set update time once in two hours, that will make
50/120=4000 requests per minute, which exceeds number for any free
subscription which definitely makes the plugin unusable at all, so this
approach is not a way to go. Thus I have no idea what else to do except
to remove the plugin from distribution.

Bug#918741: Build-Depends on deprecated libjemalloc SONAME directly

[Faidon Liambotis]

Package: src:fakechroot
Version: 2.19-3
Severity: serious

Hi,

I uploaded jemalloc 5.1.0-2 to unstable the other day. It involves a new
ABI and SONAME and thus a transition from libjemalloc1 -> libjemalloc2.

I noticed that your package Build-Depends directly on libjemalloc1, and
thus this package will start FTBFSing once libjemalloc1 gets removed
from the archive.

It seems like the B-D is there because the test suite includes a test
for jemalloc (which is great!), and specifically the binary library
which it's LD_PRELOADing, hence the dependency on the binary package.

Rather than s/libjemalloc1/libjemalloc2/, I would recommend to B-D on
"libjemalloc-dev" like a regular source package, and then modify the
test suite to search for the symlink "libjemalloc.so" (e.g.
/usr/lib/x86_64-linux-gnu/libjemalloc.so). This would make it future
proof for future ABI/SONAME bumps.

Apologies for filing this after the transition has already started -- as
a B-D on the binary package is unsual, it didn't occur to me to
grep-dctrl for that beforehand.

Regards,
Faidon

Bug#917075: marked as done (mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 22:43:01 +0100
with message-id <0196760c-c34b-cbdf-c60b-859d1fc74...@debian.org>
and subject line Re: mariadb-10.3: libmariadb3 causes removal of 
default-libmysqlclient-dev
has caused the Debian Bug report #917075,
regarding mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev
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.)


-- 
917075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.3
Version: 1:10.3.11-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:gdal

Dear Maintainer,

libmariadb3 (1:10.3.11-1) conflicts with libmariadbclient18 (<< 10.2.0)
which causes default-libmysqlclient-dev to be removed.

When building gdal in unstable now, MySQL support is disabled because
libmariadbclient-dev cannot be installed:

 The following packages have unmet dependencies:
  libmariadbclient-dev : Depends: libmariadbclient18 (= 1:10.1.37-3) but it is 
not going to be installed
 The following actions will resolve these dependencies:

  Install the following packages:  
 1) libmariadb-dev [1:10.3.11-1 (unstable)]
 2) libmariadb3 [1:10.3.11-1 (unstable)]   
 3) mariadb-common [1:10.3.11-1 (unstable)]
 4) mysql-common [5.8+1.0.4 (unstable)]

  Keep the following packages at their current version:
 5) libmariadbclient-dev [Not Installed]   

Please fix the incompatibility with the default-* packages.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
On Sat, 5 Jan 2019 13:36:40 +0100 Sebastiaan Couwenberg
 wrote:
> You can also close this issue as it was fixed by the mysql-defaults
> changes mentioned previously.

I just tested rebuilding all mariadb rdepends in a sid pbuilder
environment and did not encounter any installability problems.
Closing this now.


Andreas--- End Message ---

Bug#918740: rdkit: baseline violation on amd64/i386 and FTBFS everywhere else

[Adrian Bunk]

Source: rdkit
Version: 201803.4+dfsg-2
Severity: serious
Tags: ftbfs

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

...
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation 
-Wno-stringop-truncation -g -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 
-fdebug-prefix-map=/<>/rdkit-201803.4+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/local/include -I/<>/rdkit-201803.4+dfsg/Code 
-DRDKITVER='"007300"'   -DUSE_BUILTIN_POPCOUNT -mpopcnt -I. 
-I/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit 
-I/usr/include/postgresql/11/server -I/usr/include/postgresql/internal  
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  
-I/usr/include/mit-krb5 -fPIC -c -o rdkit_io.o 
/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit/rdkit_io.c
gcc: error: unrecognized command line option '-mpopcnt'
make[2]: *** [/<>/rdkit-201803.4+dfsg/Code/PgSQL/rdkit/Makefile:101: 
rdkit_io.o] Error 1


Due to Code/PgSQL/rdkit/Makefile:
POPCOUNTFLAGS=-DUSE_BUILTIN_POPCOUNT -mpopcnt

Processed: tagging 916005

[Debian Bug Tracking System]

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

> tags 916005 + pending
Bug #916005 [src:oss4] oss4 FTBFS with glibc 2.28
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#918739: node-duplexer2 FTBFS with nodejs 10.15.0

[Adrian Bunk]

Source: node-duplexer2
Version: 0.1.4-1
Severity: serious
Tags: ftbfs buster sid

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

...
mocha -R tap
1..14
ok 1 duplexer2 should interact with the writable stream properly for writing
ok 2 duplexer2 should interact with the readable stream properly for reading
ok 3 duplexer2 should end the writable stream, causing it to finish
ok 4 duplexer2 should finish when the writable stream finishes
ok 5 duplexer2 should end when the readable stream ends
ok 6 duplexer2 should bubble errors from the writable stream when no behaviour 
is specified
ok 7 duplexer2 should bubble errors from the readable stream when no behaviour 
is specified
ok 8 duplexer2 should bubble errors from the writable stream when bubbleErrors 
is true
ok 9 duplexer2 should bubble errors from the readable stream when bubbleErrors 
is true
ok 10 duplexer2 should not bubble errors from the writable stream when 
bubbleErrors is false
ok 11 duplexer2 should not bubble errors from the readable stream when 
bubbleErrors is false
ok 12 duplexer2 should work with streams1
ok 13 duplexer2 should export the DuplexWrapper constructor
not ok 14 duplexer2 should not force flowing-mode
  AssertionError [ERR_ASSERTION]: false == null
  at Context. (test/tests.js:195:12)
  at callFnAsync (/usr/lib/nodejs/mocha/lib/runnable.js:377:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:324:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5)
# tests 14
# pass 13
# fail 1
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

Processed: Bug #917633 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917633 [udev] udisk2 post-installation fails in chrooted environments
Added tag(s) pending.

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

Bug#917633: Bug #917633 in systemd marked as pending

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #917633 in systemd 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/systemd-team/systemd/commit/b89ae41a352f37f60918fb65efd6f7c71503ff5e


udevadm: Refuse to run trigger, control, settle and monitor commands in chroot

Closes: #917633


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917633

Processed: found 917925 in 2013.08.08-5

[Debian Bug Tracking System]

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

> found 917925 2013.08.08-5
Bug #917925 [device3dfx-source] Module fails to load on Linux 4.3 or later
Marked as found in versions device3dfx/2013.08.08-5.
> thanks
Stopping processing here.

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

Processed: reassign 917633 to udev, found 917633 in 240-1

[Debian Bug Tracking System]

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

> reassign 917633 udev
Bug #917633 [udisks2] udisk2 post-installation fails in chrooted environments
Bug reassigned from package 'udisks2' to 'udev'.
No longer marked as found in versions udisks2/2.8.1-3.
Ignoring request to alter fixed versions of bug #917633 to the same values 
previously set
> found 917633 240-1
Bug #917633 [udev] udisk2 post-installation fails in chrooted environments
Marked as found in versions systemd/240-1.
> thanks
Stopping processing here.

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

Bug#918713: marked as done (libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 21:04:29 +
with message-id 
and subject line Bug#918713: fixed in openmpi 3.1.3-9
has caused the Debian Bug report #918713,
regarding libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined 
symbol: OPAL_MCA_PMIX2X_PMIx_Get_version
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.)


-- 
918713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi3
Version: 3.1.3-8
Severity: serious
Justification: Policy 8.6

openmpi 3.1.3-8 is triggering test failure on a wide range of client
packages, including combblas, dolfin and family, petsc and family,
superlu-dist.

dolfin and petsc (etc) leave a record of the fault,

e.g. petsc
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/petsc/1662208/log.gz

  run SNES testex19
  Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI 
process
  See http://www.mcs.anl.gov/petsc/documentation/faq.html
  [ci-1546915814:12491] mca_base_component_repository_open: unable to open 
mca_pmix_pmix2x: 
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix2x.so: undefined 
symbol: OPAL_MCA_PMIX2X_PMIx_Get_version (ignored)
  [ci-1546915814:12491] [[63830,0],0] ORTE_ERROR_LOG: Not found in file 
ess_hnp_module.c at line 325
  --
  It looks like orte_init failed for some reason; your parallel process is
  likely to abort.  There are many reasons that a parallel process can
  fail during orte_init; some of which are due to configuration or
  environment problems.  This failure appears to be an internal failure;
  here's some additional information (which may only be relevant to an
  Open MPI developer):
  
opal_pmix_base_select failed
--> Returned value Not found (-13) instead of ORTE_SUCCESS


hypre and scotch are unaffected.



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

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

Versions of packages libopenmpi3 depends on:
ii  libc62.28-4
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libfabric1   1.6.1-5
ii  libgcc1  1:8.2.0-13
ii  libgfortran5 8.2.0-13
ii  libhwloc-plugins 2.0.0-1
ii  libhwloc51.11.12-1
ii  libibverbs1  21.0-1
ii  libnl-3-200  3.4.0-1
ii  libnl-route-3-2003.4.0-1
ii  libpmix2 3.1.0~rc2-2
ii  libpsm-infinipath1   3.3+20.604758e7-6
ii  libpsm2-211.2.68-4
ii  libquadmath0 8.2.0-13
ii  libstdc++6   8.2.0-13
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages libopenmpi3 recommends:
ii  openmpi-bin  3.1.3-7

libopenmpi3 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 3.1.3-9

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi 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: Tue, 08 Jan 2019 19:20:33 +
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc
Architecture: source amd64 all
Version: 3.1.3-9
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi3 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 

Bug#918738: libodb-api-dev is not installable due to typo in the dependencies

[Adrian Bunk]

Package: libodb-api-dev
Version: 0.18.1-3
Severity: serious

The following packages have unmet dependencies:
 libodb-api-dev : Depends: ibodb-api-bin (= 0.18.1-3) but it is not installable

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> user tails-...@boum.org
Setting user to tails-...@boum.org (was ulr...@debian.org).
> tag 917633 + for-buster
Unknown tag/s: for-buster.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #917633 [udisks2] udisk2 post-installation fails in chrooted environments
Requested to add no tags; doing nothing.
>
End of message, stopping processing here.

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

Bug#917633: Also blocks migration of tails-installer

[Ulrike Uhlig]

Hello!

this issue currently also blocks the migration of tails-installer,
shortly before the freeze.

Cheers!
u.

Bug#917697: marked as done (ocaml-visitors: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0))

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 21:35:21 +0100
with message-id <20190108203521.ba7cz6tgqr7ke...@xanadu.blop.info>
and subject line Closing unreproducible FTBFS bug
has caused the Debian Bug report #917697,
regarding ocaml-visitors: FTBFS: build-dependency not installable: 
libppx-deriving-ocaml-dev (>= 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.)


-- 
917697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-visitors
Version: 20180306-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-ocaml (>= 0.9~), ocaml-nox (>= 
> 4.02.2), libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= 
> 4.0), texlive-latex-base, latexmk, lmodern, texlive-fonts-recommended, 
> texlive-latex-extra, ocp-indent
> Filtered Build-Depends: debhelper (>= 11), dh-ocaml (>= 0.9~), ocaml-nox (>= 
> 4.02.2), libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= 
> 4.0), texlive-latex-base, latexmk, lmodern, texlive-fonts-recommended, 
> texlive-latex-extra, ocp-indent
> dpkg-deb: building package 'sbuild-build-depends-ocaml-visitors-dummy' in 
> '/<>/resolver-k7rZ5R/apt_archive/sbuild-build-depends-ocaml-visitors-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-ocaml-visitors-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-k7rZ5R/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-k7rZ5R/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-k7rZ5R/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-k7rZ5R/apt_archive ./ Sources [613 B]
> Get:5 copy:/<>/resolver-k7rZ5R/apt_archive ./ Packages [687 B]
> Fetched 2263 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install ocaml-visitors build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-ocaml-visitors-dummy : Depends: 
> libppx-deriving-ocaml-dev (>= 4.0) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/ocaml-visitors_20180306-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

I cannot reproduce this failures after fixing a problem in the build
environment (build user without a shell). Either this was the cause of
the failure (and the bug can be closed), or something else changed
elsewhere and prevents the failure (and the bug can be closed as well).

Lucas--- End Message ---

Bug#917718: marked as done (libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 21:21:33 +0100
with message-id <20190108202133.rhndoayl3ozgs...@xanadu.blop.info>
and subject line Re: libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 
returned exit  code 2
has caused the Debian Bug report #917718,
regarding libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit 
code 2
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.)


-- 
917718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libuv1
Version: 1.24.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> 1..343
> ok 1 - platform_output
> # Output from process `platform_output`:
> # uv_get_process_title: /<>/test/.libs/run-tests
> # uv_cwd: /<>
> # uv_resident_set_memory: 1069056
> # uv_uptime: 7932.00
> # uv_getrusage:
> #   user: 0 sec 0 microsec
> #   system: 0 sec 0 microsec
> #   page faults: 0
> #   maximum resident set size: 1044
> # uv_cpu_info:
> #   model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
> #   speed: 2500
> #   times.sys: 6262800
> #   times.user: 60641700
> #   times.idle: 10290400
> #   times.irq: 0
> #   times.nice: 0
> #   model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
> #   speed: 2500
> #   times.sys: 6210200
> #   times.user: 59260500
> #   times.idle: 11656300
> #   times.irq: 0
> #   times.nice: 0
> # uv_interface_addresses:
> #   name: lo
> #   internal: 1
> #   physical address: 00:00:00:00:00:00
> #   address: 127.0.0.1
> #   netmask: 255.0.0.0
> #   name: eth0
> #   internal: 0
> #   physical address: 06:c0:2d:38:cd:2c
> #   address: 172.31.2.71
> #   netmask: 255.255.240.0
> #   name: lo
> #   internal: 1
> #   physical address: 00:00:00:00:00:00
> #   address: ::1
> #   netmask: :::::::
> #   name: eth0
> #   internal: 0
> #   physical address: 06:c0:2d:38:cd:2c
> #   address: fe80::4c0:2dff:fe38:cd2c
> #   netmask: :::::
> # uv_os_get_passwd:
> #   euid: 1001
> #   gid: 1001
> #   username: user42
> #   shell: 
> #   home directory: /home/user42
> # uv_os_getpid: 14358
> # uv_os_getppid: 14344
> ok 2 - active
> ok 3 - async
> ok 4 - async_null_cb
> ok 5 - async_ref
> ok 6 - barrier_1
> ok 7 - barrier_2
> ok 8 - barrier_3
> ok 9 - barrier_serial_thread
> ok 10 - barrier_serial_thread_single
> ok 11 - callback_stack
> ok 12 - check_ref
> ok 13 - close_fd
> ok 14 - close_order
> ok 15 - closed_fd_events
> ok 16 - condvar_1
> ok 17 - condvar_2
> ok 18 - condvar_3
> ok 19 - condvar_4
> ok 20 - condvar_5
> ok 21 - connect_unspecified
> ok 22 - connection_fail
> ok 23 - connection_fail_doesnt_auto_close
> ok 24 - cwd_and_chdir
> ok 25 - default_loop_close
> ok 26 - delayed_accept
> ok 27 - dlerror
> ok 28 - eintr_handling
> ok 29 - embed
> ok 30 - emfile
> ok 31 - env_vars
> ok 32 - error_message
> ok 33 - fork_fs_events_child
> ok 34 - fork_fs_events_child_dir
> ok 35 - fork_fs_events_file_parent_child
> ok 36 - fork_signal_to_child
> ok 37 - fork_signal_to_child_closed
> ok 38 - fork_socketpair
> ok 39 - fork_socketpair_started
> ok 40 - fork_threadpool_queue_work_simple
> ok 41 - fork_timer
> ok 42 - fs_access
> ok 43 - fs_async_dir
> ok 44 - fs_async_sendfile
> ok 45 - fs_chmod
> ok 46 - fs_chown
> ok 47 - fs_copyfile
> ok 48 - fs_event_close_in_callback
> ok 49 - fs_event_close_with_pending_event
> ok 50 - fs_event_error_reporting
> ok 51 - fs_event_getpath
> ok 52 - fs_event_immediate_close
> ok 53 - fs_event_no_callback_after_close
> ok 54 - fs_event_no_callback_on_close
> ok 55 - fs_event_ref
> ok 56 - fs_event_start_and_close
> ok 57 - fs_event_watch_dir
> ok 58 - fs_event_watch_dir_recursive # SKIP Recursive directory watching not 
> supported on this platform.
> ok 59 - fs_event_watch_file
> ok 60 - fs_event_watch_file_current_dir
> ok 61 - fs_event_watch_file_exact_path
> ok 62 - fs_event_watch_file_twice
> ok 63 - fs_event_watch_invalid_path
> ok 64 - fs_file_async
> ok 65 - fs_file_loop
> ok 66 - fs_file_nametoolong
> ok 67 - fs_file_noent
> ok 68 - fs_file_open_append
> ok 69 - fs_file_pos_after_op_with_offset
> ok 70 - fs_file_sync
> ok 71 - fs_file_write_null_buffer
> ok 72 - fs_fstat
> ok 73 - fs_futime
> ok 74 - fs_mkdtemp
> ok 75 - fs_null_req
> ok 76 - fs_open_dir
> ok 77 - fs_partial_read
> ok 78 - fs_partial_write
> ok 79 - fs_poll
> ok 80 - fs_poll_getpath
> ok 81 - fs_poll_ref
> ok 82 - 

Bug#917679: marked as done (caffe: FTBFS: dh_auto_test: cd caffe_cpu_build && make -j2 test runtest pytest LD_LIBRARY_PATH=/<>/caffe-1.0.0\+git20180821.99bd997/caffe_cpu_build/lib/ ARGS\+=-j

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 21:30:47 +0100
with message-id <20190108203047.w25kxobvzp4jc...@xanadu.blop.info>
and subject line Re: Bug#917679: caffe: FTBFS: dh_auto_test: cd caffe_cpu_build 
&& make -j2 test runtest pytest 
LD_LIBRARY_PATH=/<>/caffe-1.0.0\+git20180821.99bd997/caffe_cpu_build/lib/
 ARGS\+=-j2 returned exit code 2
has caused the Debian Bug report #917679,
regarding caffe: FTBFS: dh_auto_test: cd caffe_cpu_build && make -j2 test 
runtest pytest 
LD_LIBRARY_PATH=/<>/caffe-1.0.0\+git20180821.99bd997/caffe_cpu_build/lib/
 ARGS\+=-j2 returned exit code 2
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.)


-- 
917679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffe
Version: 1.0.0+git20180821.99bd997-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory 
> '/<>/caffe-1.0.0+git20180821.99bd997/caffe_cpu_build'
> cd /<>/caffe-1.0.0+git20180821.99bd997/python && python3 -m 
> unittest discover -s caffe/test
> EE
> ==
> ERROR: test_coord_map (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: test_coord_map
> Traceback (most recent call last):
>   File "/usr/lib/python3.7/unittest/loader.py", line 434, in _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3.7/unittest/loader.py", line 375, in 
> _get_module_from_name
> __import__(name)
>   File 
> "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/test/test_coord_map.py",
>  line 6, in 
> import caffe
>   File 
> "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/__init__.py", 
> line 1, in 
> from .pycaffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, 
> RMSPropSolver, AdaDeltaSolver, AdamSolver, NCCL, Timer
>   File 
> "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/pycaffe.py", line 
> 15, in 
> import caffe.io
>   File "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/io.py", 
> line 2, in 
> import skimage.io
>   File "/usr/lib/python3/dist-packages/skimage/__init__.py", line 167, in 
> 
> from .util.dtype import (img_as_float32,
>   File "/usr/lib/python3/dist-packages/skimage/util/__init__.py", line 8, in 
> 
> from .arraycrop import crop
>   File "/usr/lib/python3/dist-packages/skimage/util/arraycrop.py", line 8, in 
> 
> from numpy.lib.arraypad import _validate_lengths
> ImportError: cannot import name '_validate_lengths' from 'numpy.lib.arraypad' 
> (/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
> 
> 
> ==
> ERROR: test_draw (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: test_draw
> Traceback (most recent call last):
>   File "/usr/lib/python3.7/unittest/loader.py", line 434, in _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3.7/unittest/loader.py", line 375, in 
> _get_module_from_name
> __import__(name)
>   File 
> "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/test/test_draw.py",
>  line 6, in 
> import caffe.draw
>   File 
> "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/__init__.py", 
> line 1, in 
> from .pycaffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, 
> RMSPropSolver, AdaDeltaSolver, AdamSolver, NCCL, Timer
>   File 
> "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/pycaffe.py", line 
> 15, in 
> import caffe.io
>   File "/<>/caffe-1.0.0+git20180821.99bd997/python/caffe/io.py", 
> line 2, in 
> import skimage.io
>   File "/usr/lib/python3/dist-packages/skimage/__init__.py", line 176, in 
> 
> from .util.lookfor import lookfor
>   File "/usr/lib/python3/dist-packages/skimage/util/__init__.py", line 8, in 
> 
> from .arraycrop import crop
>   File "/usr/lib/python3/dist-packages/skimage/util/arraycrop.py", line 8, in 
> 
> from numpy.lib.arraypad import _validate_lengths
> ImportError: cannot import name '_validate_lengths' from 'numpy.lib.arraypad' 
> (/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
> 
> 
> ==
> ERROR: test_io (unittest.loader._FailedTest)
> 

Processed: Re: Bug#917633: udisk2 post-installation fails in chrooted environments

[Debian Bug Tracking System]

Processing control commands:

> affects 917633 src:ltsp
Bug #917633 [udisks2] udisk2 post-installation fails in chrooted environments
Added indication that 917633 affects src:ltsp

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

Bug#918733: googletest FTBFS on mips/mipsel: out of memory

[Adrian Bunk]

Source: googletest
Version: 1.8.1-2
Severity: serious
Tags: ftbfs patch

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

...
as: out of memory allocating 4072 bytes after a total of 543838208 bytes
/tmp/ccnTRJ3H.s: Assembler messages:
/tmp/ccnTRJ3H.s: Fatal error: can't close 
CMakeFiles/gmock-matchers_test.dir/test/gmock-matchers_test.cc.o: memory 
exhausted
make[3]: *** [googlemock/CMakeFiles/gmock-matchers_test.dir/build.make:66: 
googlemock/CMakeFiles/gmock-matchers_test.dir/test/gmock-matchers_test.cc.o] 
Error 1


Fix:

--- debian/rules.old2019-01-08 12:16:26.188970969 +
+++ debian/rules2019-01-08 12:16:43.685280431 +
@@ -9,11 +9,11 @@
 ifeq ($(DEB_HOST_ARCH),hppa)
 CXXFLAGS += -mlong-calls
 else ifeq ($(DEB_BUILD_ARCH), mips)
-CXXFLAGS += -mxgot
+CXXFLAGS += -mxgot -g1
 else ifeq ($(DEB_BUILD_ARCH), mips64el)
 CXXFLAGS += -mxgot
 else ifeq ($(DEB_BUILD_ARCH), mipsel)
-CXXFLAGS += -mxgot
+CXXFLAGS += -mxgot -g1
 endif
 
 export CXXFLAGS

Bug#917633: udisk2 post-installation fails in chrooted environments

[Vagrant Cascadian]

Control: affects 917633 src:ltsp

Also blocking migration for ltsp:

  https://piuparts.debian.org/sid/fail/ltsp-server-standalone_5.18.12-1.log

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[Otto Kekäläinen]

For the records of this bug report and people following it, there are a lot
of discussions going on in both
https://github.com/perl5-dbi/DBD-mysql/issues/275 and
https://github.com/MariaDB/mariadb-connector-c/pull/95

I will now import MariaDB 10.3.12 into
https://salsa.debian.org/mariadb-team/mariadb-10.3 but postpone uploading
it for now in case the issues above might produce something that we can
backport and patch upon the mariadb-10.3 packaging in Debian to help fix
the issue in Debian. Personally I cannot follow all the details in the
Github issues above, so please let me know if something actionable on my
side emerges (e.g. patches as mentioned).

Bug#917704: marked as done (ppx-deriving-yojson: FTBFS: build-dependency not installable: libppx-deriving-ocaml-dev (>= 4.0))

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 21:17:08 +0100
with message-id <20190108201708.ga15...@seneca.home.org>
and subject line Re: ppx-deriving-yojson: FTBFS: build-dependency not 
installable: libppx-deriving-ocaml-dev (>= 4.0)
has caused the Debian Bug report #917704,
regarding ppx-deriving-yojson: FTBFS: build-dependency not installable: 
libppx-deriving-ocaml-dev (>= 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.)


-- 
917704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ppx-deriving-yojson
Version: 3.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-ocaml, ocaml-nox (>= 4.02), 
> libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= 4.0)
> Filtered Build-Depends: debhelper (>= 11), dh-ocaml, ocaml-nox (>= 4.02), 
> libfindlib-ocaml, cppo, ocamlbuild, libppx-deriving-ocaml-dev (>= 4.0)
> dpkg-deb: building package 'sbuild-build-depends-ppx-deriving-yojson-dummy' 
> in 
> '/<>/resolver-so827s/apt_archive/sbuild-build-depends-ppx-deriving-yojson-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-ppx-deriving-yojson-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-so827s/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-so827s/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-so827s/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-so827s/apt_archive ./ Sources [546 B]
> Get:5 copy:/<>/resolver-so827s/apt_archive ./ Packages [627 B]
> Fetched 2136 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install ppx-deriving-yojson build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  sbuild-build-depends-ppx-deriving-yojson-dummy : Depends: 
> libppx-deriving-ocaml-dev (>= 4.0) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/ppx-deriving-yojson_3.1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
This has been resolved by the recent upload of ppx-deriving 4.2.1-3.

-Ralf.--- End Message ---

Bug#917745: cross-toolchain-base: FTBFS: applying patches fails

[Paul Gevers]

user debian...@lists.debian.org
usertags needs-update
thanks

Hi all,

On Sat, 29 Dec 2018 23:46:40 +0100 Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> >  debian/rules build
> > linux: 4.19.12-1 / 4.18.20-2cross2
> > glibc: 2.28-4 / 2.28-2cross2
> > 
> > old linux version: 4.18.20-2 / 2
> > old glibc version: 2.28-2 / 2
> > 
> > new linux version: 4.19.12-1cross1
> > new glibc version: 2.28-4cross1
> > START stamp-dir/init-glibc
> > rm -rf glibc-2.28
> > tar -x -f  /usr/src/glibc/glibc-2.28.tar.xz
> > cp -a /usr/src/glibc/debian/ glibc-2.28
> > cd glibc-2.28 ; \
> > QUILT_PATCHES=/<>/debian/patches/glibc/debian quilt --quiltrc 
> > /dev/null push -a && \
> > rm -rf .pc/
> > Applying patch dpkg-shlibs.patch
> > patching file debian/rules.d/debhelper.mk
> > 
> > Applying patch local-kill-locales.patch
> > patching file debian/rules
> > patching file localedata/SUPPORTED
> > 
> > Applying patch glibc-build-tools.diff
> > patching file debian/rules
> > 
> > Applying patch gcc-8-armel.diff
> > patching file debian/sysdeps/armel.mk
> > Hunk #1 FAILED at 1.
> > 1 out of 1 hunk FAILED -- rejects in file debian/sysdeps/armel.mk
> > Patch gcc-8-armel.diff does not apply (enforce with -f)
> > make: *** [debian/rules:436: stamp-dir/init-glibc] Error 1

I hope you are aware that the same issue is currently blocking the
latest version of glibc from migrating to testing as the autopkgtest of
cross-toolchain-base fails on the same error:

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cross-toolchain-base/1663556/log.gz

autopkgtest [05:36:03]: test build: [---
Testing cross builds on amd64 ...
+ CROSS_ARCHS=ppc64el DEB_BUILD_OPTIONS=parallel=2 dpkg-buildpackage -d
-b --no-sign
dpkg-buildpackage: info: source package cross-toolchain-base
dpkg-buildpackage: info: source version 30
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Matthias Klose 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
linux: 4.19.12-1 / 4.18.20-2cross2
glibc: 2.28-4 / 2.28-2cross2

old linux version: 4.18.20-2 / 2
old glibc version: 2.28-2 / 2

new linux version: 4.19.12-1cross1
new glibc version: 2.28-4cross1
rm -rf linux-source-*
rm -rf glibc-*
rm -rf gcc
rm -rf binutils-*
rm -rf debian/tmp.ppc64el
rm -f debian/files debian/no-packages
rm -f debian/cross-compile
find debian -name '*~' | xargs -r rm -f
rm -f *.*deb *.changes *.buildinfo
rm -rf repackfiles tmp tmp-* debian/tmp.*
rm -rf stamp-dir/
mkdir stamp-dir/
dh_clean
 debian/rules build
linux: 4.19.12-1 / 4.18.20-2cross2
glibc: 2.28-4 / 2.28-2cross2

old linux version: 4.18.20-2 / 2
old glibc version: 2.28-2 / 2

new linux version: 4.19.12-1cross1
new glibc version: 2.28-4cross1
START stamp-dir/init-glibc
rm -rf glibc-2.28
tar -x -f  /usr/src/glibc/glibc-2.28.tar.xz
cp -a /usr/src/glibc/debian/ glibc-2.28
cd glibc-2.28 ; \
QUILT_PATCHES=/tmp/autopkgtest-lxc.3kye5ugg/downtmp/build.o4e/src/debian/patches/glibc/debian
quilt --quiltrc /dev/null push -a && \
rm -rf .pc/
Applying patch dpkg-shlibs.patch
patching file debian/rules.d/debhelper.mk

Applying patch local-kill-locales.patch
patching file debian/rules
patching file localedata/SUPPORTED

Applying patch glibc-build-tools.diff
patching file debian/rules

Applying patch gcc-8-armel.diff
patching file debian/sysdeps/armel.mk
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file debian/sysdeps/armel.mk
Patch gcc-8-armel.diff does not apply (enforce with -f)
make: *** [debian/rules:436: stamp-dir/init-glibc] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2
autopkgtest [05:36:10]: test build: ---]

Paul



signature.asc
Description: OpenPGP digital signature

Bug#917829: python-intbitset: FTBFS when built with dpkg-buildpackage -A

[Adrian Bunk]

On Sun, Dec 30, 2018 at 07:52:26PM +, Santiago Vila wrote:
>...
> In case it helps, this stopped working in buster sometime between 2018-12-11 
> and 2018-12-23
>...

The Python3 default change 3.6 -> 3.7 migrated on 2018-12-19 to buster.

> Thanks.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#918676: marked as done (r-cran-worrms: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Tue, 8 Jan 2019 21:38:16 +0200
with message-id 

and subject line Re: Bug#918676: r-cran-worrms: autopkgtest regression
has caused the Debian Bug report #918676,
regarding r-cran-worrms: autopkgtest regression
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.)


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

Source: r-cran-worrms
Version: 0.3.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since 2019-01-01, r-cran-worrms fails its autopkgtests with the 
following error:


> library("testthat")
> test_check("worrms")
Loading required package: worrms
Loading required namespace: jsonlite
-- 1. Failure: wm_records_date - works (@test-wm_records_date.R#4) 


all(grepl(format(Sys.Date(), "%Y"), aa$modified)) isn't true.

== testthat results 
===

OK: 161 SKIPPED: 28 FAILED: 1
1. Failure: wm_records_date - works (@test-wm_records_date.R#4)

Error: testthat unit tests failed
Execution halted
autopkgtest [19:26:06]: test run-unit-test: ---]
autopkgtest [19:26:06]: test run-unit-test:  - - - - - - - - - - results 
- - - - - - - - - -

run-unit-testFAIL non-zero exit status 1


The test passes if the system date is set back to 2018.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-worrms/unstable/amd64/
--- End Message ---
--- Begin Message ---
Version: 0.3.2+dfsg-1

On Tue, 8 Jan 2019 at 13:59, Andreas Tille  wrote:
> I've just uploaded r-cran-worrms_0.3.2+dfsg-1 right before I realised
> this bug.  Since I'm running autopkgtest pbuilder hook and did not
> realised any problem I guess this is fixed with this version.  Can
> you confirm this?

Confirmed [1] :

0.3.2+dfsg-1 2019-01-08 15:49:00 UTC r-cran-worrms/0.3.2+dfsg-1 0h 1m 2s pass


[1] https://ci.debian.net/packages/r/r-cran-worrms/testing/amd64/--- End Message ---

Bug#918157: marked as done (libpmix2 seems broken on 32 bits architectures)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 19:40:11 +
with message-id 
and subject line Bug#918157: fixed in pmix 3.1.0~rc2-3
has caused the Debian Bug report #918157,
regarding libpmix2 seems broken on 32 bits architectures
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.)


-- 
918157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmpi
Version: 3.1.3-7
Severity: grave
Justification: renders package unusable on 32 bits architectures

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

The last med-fichier upload FTBFS on 32 bits architectures[1] with this error:

Launching filterBlockOfentities with 2 processes
- --
At least one pair of MPI processes are unable to reach each other for
MPI communications.  This means that no Open MPI device has indicated
that it can be used to communicate between these processes.  This is
an error; Open MPI requires that all MPI processes be able to reach
each other.  This error can sometimes be the result of forgetting to
specify the "self" BTL.

  Process 1 ([[5346,1],1]) is on host: x86-grnet-01
  Process 2 ([[5346,1],0]) is on host: x86-grnet-01
  BTLs attempted: vader tcp self

Your MPI job is now going to abort; sorry.
- --
- --
MPI_INIT has failed because at least one MPI process is unreachable
from another.  This *usually* means that an underlying communication
plugin -- such as a BTL or an MTL -- has either not loaded or not
allowed itself to be used.  Your MPI job will now abort.

You may wish to try to narrow down the problem;

 * Check the output of ompi_info to see which BTL/MTL plugins are
   available.
 * Run your application with MPI_THREAD_SINGLE.
 * Set the MCA parameter btl_base_verbose to 100 (or mtl_base_verbose,
   if using MTL-based communications) to see exactly which
   communication plugins were considered and/or discarded.
- --
[x86-grnet-01:30926] *** An error occurred in MPI_Init
[x86-grnet-01:30926] *** reported by process [350355457,1]
[x86-grnet-01:30926] *** on a NULL communicator
[x86-grnet-01:30926] *** Unknown error
[x86-grnet-01:30926] *** MPI_ERRORS_ARE_FATAL (processes in this communicator 
will now abort,
[x86-grnet-01:30926] ***and potentially your MPI job)
Can't launch filterBlockOfentities with 2 processes
FAIL: filterBlockOfentities.sh

[1] 
https://buildd.debian.org/status/fetch.php?pkg=med-fichier=i386=4.0.0%2Brepack-5=1546462702=0

The changes from the previous upload (4.0.0+repack-3) which built fine can't
be related to this issue:
   * Drop debian/source/lintian-overrides; these lintian tags were removed
 in 2012
   * libmedc?11: Breaks / Replaces libmedc?1v5 (= 4.0.0+repack-1)
 (Closes: #917788)

I suspect this is related to the recent upload of openmpi 3.1.3-7.

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlwuf9sACgkQ7+hsbH/+
z4PMRwgArkC6kXa7ZFOQnthw6TZCen5UZInSpOyWIY2B4ywT7sSD6RSn2JNsolG9
QP6L6+rgnakiPHcY2OcwKvjWZ5tSnmbhXbFN5p5JcgKI2xrM+BwpDYwlD1FOyOpx
1FlXJPdiUz1vrr8ybbjmwNIjHWux7KTCN2i17oa7VWNsOVehAhgWisgLmt9+IqiQ
biAfr5Qw9/OMh3C3uJqtQesXzWLOrLGQN6u8pMFn61W1LLMl54lA4QfWrUHVZexh
8K4hN5MwzHmCRQF2OApkXMBcVrt+Ppzo4jZEavetII6ZtLMcchUQbavF0ZjdOl3l
E+lI0uLXSBOKRtw+0TaQI3S3nslLUA==
=KpJH
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 3.1.0~rc2-3

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated pmix package)

(This message was generated automatically at their 

Bug#918336: marked as done (axmail binary missing)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 19:34:44 +
with message-id 
and subject line Bug#918336: fixed in axmail 2.9-2
has caused the Debian Bug report #918336,
regarding axmail binary missing
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.)


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

The axmail package lost /usr/sbin/axmail and various other files in
the last upload.

(Spotted by the multiarch hinter which suggested that the package
could be converted to Arch:all.)

Christoph
--- End Message ---
--- Begin Message ---
Source: axmail
Source-Version: 2.9-2

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

Debian distribution maintenance software
pp.
Dave Hibberd  (supplier of updated axmail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Jan 2019 22:27:18 +
Source: axmail
Binary: axmail
Architecture: source amd64
Version: 2.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Dave Hibberd 
Description:
 axmail - Mail user agent for ax.25 users, accessed via a node frontend
Closes: 918336
Changes:
 axmail (2.9-2) unstable; urgency=medium
 .
   * Fixed the makefile edit that removed the binary (Closes: #918336)
 - patches/install_locations changed
 - patches/install_dir_creation refreshed
 .
   * Improved lintian tidiness
 - patches/spelling updated with new spelling updates
 - debian/control had some whitespace removed
Checksums-Sha1:
 c7b24f6e7e0c9c110fe91a592bf3aec1a3bdf1aa 1540 axmail_2.9-2.dsc
 049aaac8fe7a36c2ee6d8df66d7ae3f70dfbb689 4032 axmail_2.9-2.debian.tar.xz
 770e75b64459dcd757f65f5a99b43881ed29eb5d 4857 axmail_2.9-2_amd64.buildinfo
 b2a18e835372e87388967c8635d464595a72d33f 37384 axmail_2.9-2_amd64.deb
Checksums-Sha256:
 f0189b92470c0153ba653b6cd5ad5abc6dbd6236a08151540ef749230ca055f2 1540 
axmail_2.9-2.dsc
 4bff53ec41f7c2e20c765aa356a9cbe6f35b36cfe94a8cca5b2b59c669de8d27 4032 
axmail_2.9-2.debian.tar.xz
 aeec0866f31c4efb7b9ec57c11272b14dcb7c32366949c947832a304a94dc276 4857 
axmail_2.9-2_amd64.buildinfo
 077dacf15b035f9656dc76f8179129fb0efebbf89d3b1778c1d48edb078a6fef 37384 
axmail_2.9-2_amd64.deb
Files:
 2fe69b144928acc308805848e5add9fa 1540 hamradio optional axmail_2.9-2.dsc
 1901440dd5c129cd25adb5f909978056 4032 hamradio optional 
axmail_2.9-2.debian.tar.xz
 c2b4b032c2bceec393a0524939734766 4857 hamradio optional 
axmail_2.9-2_amd64.buildinfo
 68020b2a2ae488e45f587f91edfbed4c 37384 hamradio optional axmail_2.9-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEXk9UUZPolpyKWbgKA6H7ehkEdxsFAlw0+BYACgkQA6H7ehkE
dxsS0QgAjqExkzHlvNxeGbbF3HMg4afcVOIa5vMNv5IWVxm42Yu7lcAcGUzowbFG
QQ9jErKoTpQ7uc8M1Hg4+KRZ8xm4Fume5UMzoSVr7lri3z22MXUUtE1QmoorR+t4
3HudsJQVqhPU5f4yAcdIDpUtPMWyt6tRG6NsJDjJctqPeKW2+k7wCLzo437IS1hC
GRQVJ1BDPXph+qoMALDPj3ubXOAfQyY36przCnDked/6rzhrkyfGAAa9vybshaGx
Vnzi6Bma9xWHyoF8NglzcIaqxTnIcojZVXSNROmSwDaXn9FK7i1fHks05vBp/c6w
gGB0dsO3xPdwvIKmtO4+eauf7XaGfQ==
=L44q
-END PGP SIGNATURE End Message ---

Bug#918685: marked as done (graphite2: FTBFS with test failures: awamicmp[123])

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 18:49:59 +
with message-id 
and subject line Bug#918685: fixed in graphite2 1.3.13-4
has caused the Debian Bug report #918685,
regarding graphite2: FTBFS with test failures: awamicmp[123]
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.)


-- 
918685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graphite2
Version: 1.3.13-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

graphite2/experimental FTBFS on all architectures:

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


The following tests FAILED:
 75 - awamicmp1 (Failed)
 76 - awamicmp2 (Failed)
 77 - awamicmp3 (Failed)
Errors while running CTest


Andreas


graphite2_1.3.13-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: graphite2
Source-Version: 1.3.13-4

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated graphite2 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: Tue, 08 Jan 2019 19:00:01 +0100
Source: graphite2
Binary: libgraphite2-3 libgraphite2-dev libgraphite2-doc libgraphite2-utils 
python3-graphite2
Architecture: source
Version: 1.3.13-4
Distribution: experimental
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Description:
 libgraphite2-3 - Font rendering engine for Complex Scripts -- library
 libgraphite2-dev - Development files for libgraphite2
 libgraphite2-doc - Documentation for libgraphite2
 libgraphite2-utils - Font rendering engine for Complex Scripts -- utilities
 python3-graphite2 - Python bindings for libgraphite2
Closes: 918685
Changes:
 graphite2 (1.3.13-4) experimental; urgency=medium
 .
   * revert upstream 49fce465ae4ee921f81e9fb8270177c16849a3e9 (awamicmp1,2,3
 test json updates) to work around test failures (closes: #918685)
Checksums-Sha1:
 418f7e78d39c4d832de18d28af05b81a9faa15bc 2542 graphite2_1.3.13-4.dsc
 7c55e285ae22ef0f3d95e822e098b99f82b05458 16820 graphite2_1.3.13-4.debian.tar.xz
 39851d8d8a7207ea8f1283b5e69062d65fcea799 10994 
graphite2_1.3.13-4_source.buildinfo
Checksums-Sha256:
 a4ccb0880d023198a012771b861f38d208dc7a1a5d141ed365ce5e4b1477997d 2542 
graphite2_1.3.13-4.dsc
 0ecabd31ec82896d4b1dc6617168d77d265cf6dbe2713ff79308fca69217a782 16820 
graphite2_1.3.13-4.debian.tar.xz
 5a895617f2dc49b9c8d68f70d92e5ad3b059937a4804d0f96512f8082f3c65a4 10994 
graphite2_1.3.13-4_source.buildinfo
Files:
 3cb607c00ecce33655c3238c332fceb2 2542 libs optional graphite2_1.3.13-4.dsc
 7ddae693a9c5c6ae51a2f47461a2 16820 libs optional 
graphite2_1.3.13-4.debian.tar.xz
 556a05e8cc5982375592e6ffceba811c 10994 libs optional 
graphite2_1.3.13-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAlw07RAACgkQCqBFcdA+
PnC1ZQ/6AnCs3QHVhNpqyGYgEVQK5Xh38dXNQCPN+p7bGKZktOnMGdITLxiS9ZfR
uCZ1sqa/YyUADmCareYsGPhsqGPhIq4l65id5hwrh97+dgJWjlxNr480diZic64B
THcEOJcrw9QnuTNIEQIMgaUz9X0WN5s9me74q2nN3/RoQ0UadSKKhe2oBR1eMnj0
80zPYs0LwZFg+BaHGFBjrj56GK7RmX+sd5i1YRSU7oDeAk9FFDILt6Qri0RuhPAD
mRpwc+qOQj+aP6RuDHJFuNZJ2hm4OdChO69oMfGJt67Jniy/Vc+yiJ3IUM9Fq2Bo
m5K4Cxk3SchCfyeRgxqmxcVj1zCRiZjK9ENv2EujiS3vKDjHsg7qaNjnqoDly1YO
GpejB8F5I2yNyX/Kc9Wf4rEcUhYPkbvgIBstwBCKJNSXR29WQZUG7NQnVTyV7Euv
+Koawlue6xlkSaLTjJe4QF3Wbw+Un4c9+vMgy14f81zOoD7kBH8C7T6sAhhr5ooN
jEBj5jE0rDNVDkyd8czqlnS+Kkyc/Kp9sQOSXzF4s+crOJV31blGg1wB2fdt3eTG
S1HBeqsihEhKJi7CcCTH4JvPHyKKLNEyQaEnb1GWLre2GKOhnmBibalu1Y37RlAK
pK9xv8wtFVDfXxB34EHOacspn5VV4yJ9TFq6p/DISdpIRci8xTk=
=4FNS
-END PGP SIGNATURE End Message ---

Bug#864432: marked as done (funcoeszz: depends on a transitional package lynx-cur)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 18:49:31 +
with message-id 
and subject line Bug#864432: fixed in funcoeszz 15.5-1.1
has caused the Debian Bug report #864432,
regarding funcoeszz: depends on a transitional package lynx-cur
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.)


-- 
864432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: funcoeszz
Version: 15.5-1

lynx-cur is a transitional dummy package in testing and unstable,
and lynx is the real package.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (450, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

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

Versions of packages funcoeszz depends on:
ii  lynx-cur  2.8.9dev11-1

funcoeszz recommends no packages.

funcoeszz suggests no packages.

-- no debconf information

-- 
Michał Politowski
Talking has been known to lead to communication if practiced carelessly.
--- End Message ---
--- Begin Message ---
Source: funcoeszz
Source-Version: 15.5-1.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated funcoeszz 
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: Tue, 08 Jan 2019 16:31:13 -0200
Source: funcoeszz
Binary: funcoeszz
Architecture: source
Version: 15.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Eder Diego de Lima Marques 
Changed-By: Joao Eriberto Mota Filho 
Description:
 funcoeszz  - script with 170+ useful mini applications
Closes: 864432
Changes:
 funcoeszz (15.5-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: changed from lynx-cur to lynx in Depends field.
 (Closes: #864432)
Checksums-Sha1:
 918b39ad521c8144a62040fed1aec1ed8e861c3b 1691 funcoeszz_15.5-1.1.dsc
 e85c2f35072e5ef1cb740b75319ff0e5bd28b441 2676 funcoeszz_15.5-1.1.debian.tar.xz
 160b1282384e90a3a30846ae1c22d8eba231090e 4935 
funcoeszz_15.5-1.1_source.buildinfo
Checksums-Sha256:
 6ed7856fee1ad2255c5ab0597382d66b38aac027cd3390dd449ec7f6930e6c4e 1691 
funcoeszz_15.5-1.1.dsc
 063f5348b12e424fc9f237765e22f69f49b6c1dd500e7c8c0bb7ea5aac6e3e59 2676 
funcoeszz_15.5-1.1.debian.tar.xz
 f41cfc932af029d2f4f8bfc478c91c72abd8eae435a88abae2a6091a954a3ba2 4935 
funcoeszz_15.5-1.1_source.buildinfo
Files:
 e109ae4b3fc948534804678893acc43a 1691 misc optional funcoeszz_15.5-1.1.dsc
 02e8234f901cc3c125c624de6d9afd3a 2676 misc optional 
funcoeszz_15.5-1.1.debian.tar.xz
 b1efdb53e8193c1d6c4e4ebbc57d6818 4935 misc optional 
funcoeszz_15.5-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlw07eIACgkQ3mO5xwTr
6e+G5g/+Opt9+/XEwUpW/GLSeSl2LomVqRNRhn4HytxFlsWDolrhdPA3ksD26Tou
B/NclauCb2Ph+8LD4mm8g9SVUpJj+JHX50c8UFWNdc3jxiG/dXTURJWjw3D+TUz/
okVU6jGS/7UphTvG/AfHdDE0UkethkrRqlBlN4ilmqhqvAXDUhEug7Bdia4a7TlI
JAiEaa27GK7NvizUFLajrhHxJtQsq/lFUmp+n5Y5lnsJk9WOIv3QBq5W2w4VqbcV
wFIFUeAjW4OXe+XTqfVvqbqpQEzVSzmuCs8P7Qq/olgewNYYs7AmNoZN1CfyHip9
0Lv/jdMhuLG3j/wI+T3lm+sxeh561OkDXEYWchbJIRKWkJGMpi4Ox4MzcZmoYOyd
cE8JrlnuIZWbTh2jkLoxjT0Te5VeoF9/bRL3SUY15NbuKJqih/MIqgmFuylqY7QP
O9vbRRUIzSveDi4rKqLjQ7dmU3rKKsuoJYUlYehZoNZJIiDw/C+L4KL1F48T8E4L
LlddQolGZX0MaOZtnKYfLveyEfMquJJWtML/PGjlZ+qdCDKLYHzyZZxfo8jHoxt7
+LYrxYUsbC77g/rN4rAwzcdTD1pomcbTB3dFSfMK5PTMhGoOLJD3q9Vnum58FqvU
JzWpGhkwmyFG8EWYLHBLcW8zswqKCgQroYRPk8B2c+c/nEIfMlg=
=wuaU
-END PGP SIGNATURE End Message ---

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[Georg Richter]

Hi Otto,

it doesn't make sense to zero a pointer, if the container (or speaking of
C: structure) is freed afterwards. The documentation clearly states, that a
handle (which was previously freed by mysql_close() ) needs to be
initialized again.

The pull request fixes the perl test case, but it didn't fix perl itself,
which still abuses internal members of the connector, which are considered
to be opaque. (And being opaque is the goal for next major release).

/Georg


On Mon, Jan 7, 2019 at 8:40 PM Otto Kekäläinen  wrote:

> Hello!
>
> gregor herrmann  kirjoitti pe 4. tammikuuta 2019 klo
> 1.23:
>
>> On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote:
>>
>> > Just checking: are you Georg or Gregor currently working on this
>> > issue, and do you have any estimate when we could expect either a
>> > patch to MariaDB Connector C or a new upload of DBD-mysql so this
>> > issue would be resolved?
>>
>> I had a look at DBD::mysql and DBD::MariaDB but without any success.
>> I hope that someone with a better understanding than me from the
>> Debian perl Group can try and find a solution.
>>
>> I've now pinged the upstream issue at:
>> https://github.com/perl5-dbi/DBD-mysql/issues/275
>
>
> Thanks Gregor for working with upstreams to fix this. Nice Eric Herman was
> also involved ;)
>
> Georg Richter, I hope you can review
> https://github.com/MariaDB/mariadb-connector-c/pull/95 shortly, thanks!
>
>
>>

-- 
Georg Richter, Senior Software Engineer
MariaDB Corporation Ab

Bug#918685: Bug #918685 in graphite2 marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #918685 in graphite2 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/libreoffice-team/graphite2/commit/ec2bd84a2fe513efa6f038f68b7b318e1a7375e0


revert upstream 49fce465ae4ee921f81e9fb8270177c16849a3e9 (awamicmp1,2,3 test 
json updates) to work around test failures (closes: #918685)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918685

Processed: Bug #918685 in graphite2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918685 [src:graphite2] graphite2: FTBFS with test failures: awamicmp[123]
Added tag(s) pending.

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

Bug#894202: marked as done (rdkit FTBFS on 32bit: test hang)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 18:00:16 +
with message-id 
and subject line Bug#894202: fixed in rdkit 201803.4+dfsg-2
has caused the Debian Bug report #894202,
regarding rdkit FTBFS on 32bit: test hang
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.)


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

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/rdkit-201709.3+dfsg'
cp -r rdkit obj-*/
find /<>/rdkit-201709.3+dfsg -name rdchem.so
/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu/rdkit/Chem/rdchem.so
#export RDBASE=/<>/rdkit-201709.3+dfsg 
PYTHONPATH=/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu/ 
LD_LIBRARY_PATH="/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu//lib:"
RDBASE=/<>/rdkit-201709.3+dfsg 
PYTHONPATH=/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu/:/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu//rdkit/Chem/
 LD_LIBRARY_PATH="/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu//lib:" 
dh_auto_test
cd obj-i686-linux-gnu && make -j4 -O test ARGS\+=-j4
E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---
Source: rdkit
Source-Version: 201803.4+dfsg-2

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated rdkit 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: Tue, 08 Jan 2019 17:03:28 +0100
Source: rdkit
Binary: python-rdkit rdkit-doc rdkit-data librdkit1 librdkit-dev 
postgresql-11-rdkit
Architecture: source amd64 all
Version: 201803.4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 librdkit-dev - Collection of cheminformatics and machine-learning software 
(deve
 librdkit1  - Collection of cheminformatics and machine-learning software (shar
 postgresql-11-rdkit - Collection of cheminformatics and machine-learning 
software (Post
 python-rdkit - Collection of cheminformatics and machine-learning software
 rdkit-data - Collection of cheminformatics and machine-learning software (data
 rdkit-doc  - Collection of cheminformatics and machine-learning software (docu
Closes: 894202
Changes:
 rdkit (201803.4+dfsg-2) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Point Vcs fields to Salsa
 .
   [ Michael Banck ]
   * debian/patches/disable_hanging_test.patch: New patch, removes the
 testEnumeration test, which makes 32-bit architectures hang
 (Closes: #894202).
Checksums-Sha1:
 dfe921dd8f50eac8760f6a37864f3a310ded2b0a 2721 rdkit_201803.4+dfsg-2.dsc
 067bca04b883b3ef00af6b842dc91fdef29aadd8 13044 
rdkit_201803.4+dfsg-2.debian.tar.xz
 36cb6553a5bcb11420c4616257a7a3d2edc7bb9c 281676 
librdkit-dev_201803.4+dfsg-2_amd64.deb
 71e541e8ab0a4ef2ce12dc11aa50293a1b2db508 61718224 
librdkit1-dbgsym_201803.4+dfsg-2_amd64.deb
 9739dd71df0a8dc16ff1f66568a58a1ed3c7df33 2500420 
librdkit1_201803.4+dfsg-2_amd64.deb
 47f88051cf6b2964f463f411ba1f2faeba13254f 957016 
postgresql-11-rdkit-dbgsym_201803.4+dfsg-2_amd64.deb
 3c40abd0a58f4ce49f0be77649a15662912384ce 398640 
postgresql-11-rdkit_201803.4+dfsg-2_amd64.deb
 814beb4e51f3e8b4ece377c1441fe6af4fe0b548 43908796 
python-rdkit-dbgsym_201803.4+dfsg-2_amd64.deb
 d6abafc097800986b88a67eb64e0b06b3d5ebb52 3807272 
python-rdkit_201803.4+dfsg-2_amd64.deb
 c8f30162d04ae8ea8c58327d2288e75655f06027 6760292 
rdkit-data_201803.4+dfsg-2_all.deb
 07b5208919d2a4f92b1fa149eda32a7b7431116c 5890288 
rdkit-doc_201803.4+dfsg-2_all.deb
 7749dbfa23999d9a736f97a0fb568c6f762c976d 15630 
rdkit_201803.4+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 1c3dfd723aeb4c1d6ab4c43f22839d6dbda987e88cf040eff0bc1db6c5964af5 2721 
rdkit_201803.4+dfsg-2.dsc
 bfcc2a0e4685bff801140c03b7c2f5b0e31cd5283dbcfbf53e33bd4731024128 13044 
rdkit_201803.4+dfsg-2.debian.tar.xz
 e6d3c0eef54f1bceaa78a29d7a2fe272fa708f653479e03976f3e548b9f6e891 

Processed: bug 918685 is forwarded to https://github.com/silnrsi/graphite/issues/49

[Debian Bug Tracking System]

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

> forwarded 918685 https://github.com/silnrsi/graphite/issues/49
Bug #918685 [src:graphite2] graphite2: FTBFS with test failures: awamicmp[123]
Set Bug forwarded-to-address to 'https://github.com/silnrsi/graphite/issues/49'.
> thanks
Stopping processing here.

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

Processed: fixed 915679 in 1.2.0~DEVEL+20181202-1

[Debian Bug Tracking System]

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

> fixed 915679 1.2.0~DEVEL+20181202-1
Bug #915679 {Done: Yangfl } [pcc] pcc: broken symlinks on 
i386: /usr/bin/x86_64-linux-gnu-p* -> x86_64-linux-gnu-pcc
Marked as fixed in versions pcc/1.2.0~DEVEL+20181202-1.
> thanks
Stopping processing here.

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

Processed: tagging 917686

[Debian Bug Tracking System]

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

> tags 917686 + help
Bug #917686 [src:lightproof] lightproof: FTBFS: "zipfile is empty" with python 
3.7 ("Key Error")
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: Bug #894202 in rdkit marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #894202 [src:rdkit] rdkit FTBFS on 32bit: test hang
Added tag(s) pending.

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

Bug#894202: Bug #894202 in rdkit marked as pending

[Michael Banck]

Control: tag -1 pending

Hello,

Bug #894202 in rdkit 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/debichem-team/rdkit/commit/aa0d8bb34b21038d01bdcc4c2121423ae4bfb457


* debian/patches/disable_hanging_test.patch: New patch, removes the
testEnumeration test, which makes 32-bit architectures hang
(Closes: #894202).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/894202

Bug#918648: watcher: FTBFS (autobuilder hangs)

[Thomas Goirand]

On 1/8/19 3:20 PM, Adrian Bunk wrote:
> On Tue, Jan 08, 2019 at 02:38:47PM +0100, Santiago Vila wrote:
>> ...
>> I see you have downgraded this from serious, but Release Policy says
>> packages must build without failure. Could you please tell me
>> in which sense this:
>>
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/watcher.html
>>
>> is not a failure?

I never contested that it fails in reproducible-builds.org, I wrote it
builds for me on my environment which isn't tweaked like the one from
reproducible-builds.org.

Also, I would appreciate if you do not play BTS-ping-pong. Since I
haven't reproduced the build failure locally, I'm declaring that it
doesn't build *in certain environment*, which isn't a general FTBFS.
Therefore, I'm considering this not an RC bug. Ultimately, this is up to
me to decide, and if you want to override, then you must go to a higher
authority (like the tech ctte or the release team). Also, the severity
that I'm setting has nothing to do with my will to fix it, so there's no
reason to get mad at it.

> This error in reproducible looks pretty different (it is also not a hang)
> from what you reported.

Very much!

> In any case it would be good if the package would be uploaded source-only,
> since this would have made it easy to see whether it also fails on the
> buildds.

Has the issue that the package has to go through NEW again if it fails
been fixed?

Cheers,

Thomas Goirand (zigo)

Processed: severity 918648 important

[Debian Bug Tracking System]

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

> severity 918648 important
Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#917726: globus-gass-copy: FTBFS: tests failed

[Lucas Nussbaum]

On 08/01/19 at 10:16 +0100, Mattias Ellert wrote:
> mån 2019-01-07 klockan 09:20 +0100 skrev Lucas Nussbaum:
> > Hi,
> > 
> > On 07/01/19 at 08:28 +0100, Mattias Ellert wrote:
> > > Hi!
> > > 
> > > The globus-gass-copy package and dependent packaged have now been
> > > tagged for autoremoval due to this RC bug. So I need to resolve this
> > > with some urgency.
> > > 
> > > Since I did not receive any reply to my previous comment I need to
> > > resolve this without the additional feedback I requested.
> > > 
> > > I will close this as "not a bug" since I believe the failure to be due
> > > to a misconfiguration of the rebuild test build server, and not a real
> > > bug (see the above mentioned comment for details).
> > > 
> > > If this is not satisfactory, please feel welcome to reopen the bug and
> > > provide additional information about why you believe the bug report is
> > > valid.
> > > 
> > >   Mattias
> > 
> > Well, I'm not sure about this bug.
> > 
> > It seems that it fails to build with '!' in /etc/shadow, with '*' in
> > /etc/shadow, and even with a password in /etc/shadow. I don't know if
> > sbuild is doing something strange, but it doesn't look like it.
> > 
> > Also, this is (AFAIK) the only package failing because of this.
> > 
> > Lucas
> 
> Checking the code of the server binary used during the test, what is
> checked by the server to ensure logins are not enabled is:
> 
> 1. That a shell is defined for the user and that this shell exists
> 2. That the defined shell is a regular file
> 3. That the defined shell has executable permissions.

Ah! thanks! I can confirm that after setting a shell, it builds fine.

I'll go through the other failures to detect misfiled bugs.

Lucas


signature.asc
Description: PGP signature

Bug#918715: arptables: fails to remove if iptables haven't been installed

[Adam Borowski]

Package: arptables
Version: 0.0.4+snapshot20181021-1
Severity: serious

Hi!
I'm afraid that the new prerm fails badly when there's no iptables, preventing
the package from getting removed:

Removing arptables (0.0.4+snapshot20181021-1) ...
dpkg-query: no packages found matching iptables
dpkg: error processing package arptables (--purge):
 installed arptables package pre-removal script subprocess returned error exit 
status 1
Errors were encountered while processing:
 arptables

Once iptables have been installed, they're now known to dpkg, even after
subsequent purging.  In such case, arptables removes successfully.


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

Kernel: Linux 5.0.0-rc1-debug-00035-gdce22716f1b4 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages arptables depends on:
ii  libc6  2.28-4

arptables recommends no packages.

arptables suggests no packages.

-- no debconf information

Bug#918713: libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version

[Drew Parsons]

Package: libopenmpi3
Version: 3.1.3-8
Severity: serious
Justification: Policy 8.6

openmpi 3.1.3-8 is triggering test failure on a wide range of client
packages, including combblas, dolfin and family, petsc and family,
superlu-dist.

dolfin and petsc (etc) leave a record of the fault,

e.g. petsc
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/petsc/1662208/log.gz

  run SNES testex19
  Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI 
process
  See http://www.mcs.anl.gov/petsc/documentation/faq.html
  [ci-1546915814:12491] mca_base_component_repository_open: unable to open 
mca_pmix_pmix2x: 
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix2x.so: undefined 
symbol: OPAL_MCA_PMIX2X_PMIx_Get_version (ignored)
  [ci-1546915814:12491] [[63830,0],0] ORTE_ERROR_LOG: Not found in file 
ess_hnp_module.c at line 325
  --
  It looks like orte_init failed for some reason; your parallel process is
  likely to abort.  There are many reasons that a parallel process can
  fail during orte_init; some of which are due to configuration or
  environment problems.  This failure appears to be an internal failure;
  here's some additional information (which may only be relevant to an
  Open MPI developer):
  
opal_pmix_base_select failed
--> Returned value Not found (-13) instead of ORTE_SUCCESS


hypre and scotch are unaffected.



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

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

Versions of packages libopenmpi3 depends on:
ii  libc62.28-4
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libfabric1   1.6.1-5
ii  libgcc1  1:8.2.0-13
ii  libgfortran5 8.2.0-13
ii  libhwloc-plugins 2.0.0-1
ii  libhwloc51.11.12-1
ii  libibverbs1  21.0-1
ii  libnl-3-200  3.4.0-1
ii  libnl-route-3-2003.4.0-1
ii  libpmix2 3.1.0~rc2-2
ii  libpsm-infinipath1   3.3+20.604758e7-6
ii  libpsm2-211.2.68-4
ii  libquadmath0 8.2.0-13
ii  libstdc++6   8.2.0-13
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages libopenmpi3 recommends:
ii  openmpi-bin  3.1.3-7

libopenmpi3 suggests no packages.

-- no debconf information

Bug#918575: marked as done (abyss FTBFS on 32bit big endian: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 16:04:01 +
with message-id 
and subject line Bug#918575: fixed in abyss 2.1.5-2
has caused the Debian Bug report #918575,
regarding abyss FTBFS on 32bit big endian: test failures
to be marked as done.

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

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


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

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

...

FAIL: common_kmer
=

Running main() from gtest_main.cc
[==] Running 1 test from 1 test case.
[--] Global test environment set-up.
[--] 1 test from Kmer
[ RUN  ] Kmer.canonicalize
Common/KmerTest.cpp:18: Failure
Value of: kmer
  Actual: AGGC
Expected: canonical
Which is: ATGC
Common/KmerTest.cpp:30: Failure
Value of: kmer
  Actual: TTCGG
Expected: oddLengthCanonical
Which is: CGAGC
[  FAILED  ] Kmer.canonicalize (0 ms)
[--] 1 test from Kmer (1 ms total)

[--] Global test environment tear-down
[==] 1 test from 1 test case ran. (1 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Kmer.canonicalize

 1 FAILED TEST
FAIL common_kmer (exit status: 1)

FAIL: BloomFilter
=

Running main() from gtest_main.cc
[==] Running 8 tests from 2 test cases.
[--] Global test environment set-up.
[--] 6 tests from BloomFilter
[ RUN  ] BloomFilter.base
Konnector/BloomFilter.cc:30: Failure
Value of: x[b]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:31: Failure
Value of: x[Bloom::hash(b) % x.size()]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:34: Failure
Value of: x[c]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:35: Failure
Value of: x[Bloom::hash(c) % x.size()]
  Actual: false
Expected: true
[  FAILED  ] BloomFilter.base (0 ms)
[ RUN  ] BloomFilter.serialization
Konnector/BloomFilter.cc:55: Failure
Value of: origBloom[b]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:56: Failure
Value of: origBloom[c]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:73: Failure
Value of: copyBloom[b]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:74: Failure
Value of: copyBloom[c]
  Actual: false
Expected: true
[  FAILED  ] BloomFilter.serialization (1 ms)
[ RUN  ] BloomFilter.union_
Konnector/BloomFilter.cc:92: Failure
Value of: bloom2[b]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:109: Failure
Value of: unionBloom[b]
  Actual: false
Expected: true
[  FAILED  ] BloomFilter.union_ (0 ms)
[ RUN  ] BloomFilter.intersect
Konnector/BloomFilter.cc:132: Failure
Value of: bloom2[b]
  Actual: false
Expected: true
[  FAILED  ] BloomFilter.intersect (0 ms)
[ RUN  ] BloomFilter.windowSerialization
[   OK ] BloomFilter.windowSerialization (0 ms)
[ RUN  ] BloomFilter.windowUnion
[   OK ] BloomFilter.windowUnion (0 ms)
[--] 6 tests from BloomFilter (1 ms total)

[--] 2 tests from CascadingBloomFilter
[ RUN  ] CascadingBloomFilter.base
Konnector/BloomFilter.cc:178: Failure
Value of: 2U
  Actual: 2
Expected: x.popcount()
Which is: 1
Konnector/BloomFilter.cc:179: Failure
Value of: x[b]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:180: Failure
Value of: x[Bloom::hash(b) % x.size()]
  Actual: false
Expected: true
Konnector/BloomFilter.cc:182: Failure
Value of: 3U
  Actual: 3
Expected: x.popcount()
Which is: 1
Konnector/BloomFilter.cc:183: Failure
Value of: x[c]
  Actual: false
Expected: true
[  FAILED  ] CascadingBloomFilter.base (1 ms)
[ RUN  ] CascadingBloomFilter.window
[   OK ] CascadingBloomFilter.window (0 ms)
[--] 2 tests from CascadingBloomFilter (1 ms total)

[--] Global test environment tear-down
[==] 8 tests from 2 test cases ran. (2 ms total)
[  PASSED  ] 3 tests.
[  FAILED  ] 5 tests, listed below:
[  FAILED  ] BloomFilter.base
[  FAILED  ] BloomFilter.serialization
[  FAILED  ] BloomFilter.union_
[  FAILED  ] BloomFilter.intersect
[  FAILED  ] CascadingBloomFilter.base

 5 FAILED TESTS
FAIL BloomFilter (exit status: 1)

FAIL: Konnector_DBGBloomAlgorithms
==

Running main() from gtest_main.cc
[==] Running 8 tests from 2 test cases.
[--] Global test environment set-up.
[--] 4 tests from GetStartKmerPosTest
[ RUN  ] GetStartKmerPosTest.FullReadMatch
[   OK ] GetStartKmerPosTest.FullReadMatch (0 ms)
[ RUN  ] GetStartKmerPosTest.FullReadMismatch
[   OK ] 

Bug#911507: offlineimap: fails to load imaplib2

[Ilias Tsitsimpis]

Hi,

On Sun, Oct 21, 2018 at 08:50AM, Hans-Joachim wrote:
> Dear Maintainer,
> 
> calling offlineimap stops reporting
> 
> Error while trying to import system imaplib2: name '__revision__' is not 
> defined
> Traceback (most recent call last):
>   File "/usr/bin/offlineimap", line 20, in 
> from offlineimap import OfflineImap
>   File "/usr/share/offlineimap/offlineimap/__init__.py", line 20, in 
> from offlineimap.init import OfflineImap
>   File "/usr/share/offlineimap/offlineimap/init.py", line 29, in 
> import offlineimap.virtual_imaplib2 as imaplib
>   File "/usr/share/offlineimap/offlineimap/virtual_imaplib2.py", line 43, in 
> 
> from offlineimap.bundled_imaplib2 import *
> ImportError: No module named bundled_imaplib2
> 
> looks like to be related to the 'new' python-imaplib2 (2.57-5)

First of all, sorry for the late reply. Unfortunately I cannot reproduce
this on my machine. Could you please provide the versions of offlineimap
and python-imaplib2 you are using? I am asking because you said that the
'new' python-imaplib2 (2.57-5) is at fault, but the following
suggests you are using python-imaplib2 2.55-1+deb9u1 from stable:

> Versions of packages offlineimap depends on:
> ii  python   2.7.13-2
> ii  python-imaplib2  2.55-1+deb9u1
> ii  python-six   1.10.0-3

Best,

-- 
Ilias

Processed: Re: Bug#918648: watcher: FTBFS (autobuilder hangs)

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs)
Bug 918648 cloned as bug 918712
> retitle -2 watcher FTBFS in some timezones
Bug #918712 [src:watcher] watcher: FTBFS (autobuilder hangs)
Changed Bug title to 'watcher FTBFS in some timezones' from 'watcher: FTBFS 
(autobuilder hangs)'.
> severity -1 serious
Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs)
Severity set to 'serious' from 'important'

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

Bug#913346: libsane1: Cannot update libsane1

[John Paul Adrian Glaubitz]

Control: severity -1 normal

On 1/8/19 4:26 PM, John Paul Adrian Glaubitz wrote:
> It's not serious for Debian since the package never entered testing in
> the first place.

Adjusting severity accordingly.

Please don't set the severity to serious unless providing a reference to
the corresponding chapter in the Debian Policy.

Thanks,
Adrian

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

Processed: Re: libsane1: Cannot update libsane1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #913346 [sane-backends] libsane1: Cannot update libsane1
Severity set to 'normal' from 'serious'

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

Bug#913346: libsane1: Cannot update libsane1

[John Paul Adrian Glaubitz]

Hello!

On 1/3/19 11:51 PM, Jeremy Bicha wrote:
> This issue is more serious for Ubuntu which will need to keep a
> libsane1 transitional package around until after 20.04 LTS.

It's not serious for Debian since the package never entered testing in
the first place.

> I've prepared an NMU for sane-backends (versioned as 1.0.27-3.2) and
> uploaded it to DELAYED/15. Please feel free to tell me if I
> should delay it longer.

I disagree with change as this particular version of sane never left
unstable. Please don't add kludges to support something which is not
supported in the first place.

Adrian

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

Bug#914986: marked as done (webkit2gtk: FTBFS on i386: ENABLE_SAMPLING_PROFILER conflicts with ENABLE_C_LOOP)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 15:21:46 +
with message-id 
and subject line Bug#914986: fixed in webkit2gtk 2.23.2-1
has caused the Debian Bug report #914986,
regarding webkit2gtk: FTBFS on i386: ENABLE_SAMPLING_PROFILER conflicts with 
ENABLE_C_LOOP
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.)


-- 
914986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webkit2gtk
Version: 2.23.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

webkit2gtk/experimental FTBFS on i386:

https://buildd.debian.org/status/fetch.php?pkg=webkit2gtk=i386=2.23.1-1=1543020644=0

[...]
-- Checking for module 'gl'
--   Found gl, version 18.2.5
-- Found OpenGL: /usr/include  
-- Looking for include file GL/glx.h
-- Looking for include file GL/glx.h - found
-- Checking for module 'glesv2'
--   Found glesv2, version 18.2.5
-- Found OpenGLES2: /usr/include  
CMake Error at Source/cmake/WebKitFeatures.cmake:252 (message):
  ENABLE_SAMPLING_PROFILER conflicts with ENABLE_C_LOOP.  You must disable
  one or the other.
Call Stack (most recent call first):
  Source/cmake/WebKitFeatures.cmake:260 (_WEBKIT_OPTION_ENFORCE_CONFLICTS)
  Source/cmake/WebKitFeatures.cmake:285 (_WEBKIT_OPTION_ENFORCE_ALL_CONFLICTS)
  Source/cmake/OptionsGTK.cmake:162 (WEBKIT_OPTION_END)
  Source/cmake/WebKitCommon.cmake:59 (include)
  CMakeLists.txt:163 (include)


-- Configuring incomplete, errors occurred!
[...]


There are different failures on other architectures.


Andreas
--- End Message ---
--- Begin Message ---
Source: webkit2gtk
Source-Version: 2.23.2-1

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

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated webkit2gtk 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: Tue, 08 Jan 2019 16:55:02 +0200
Source: webkit2gtk
Binary: libjavascriptcoregtk-4.0-18 libjavascriptcoregtk-4.0-dev 
libjavascriptcoregtk-4.0-bin gir1.2-javascriptcoregtk-4.0 libwebkit2gtk-4.0-37 
libwebkit2gtk-4.0-dev libwebkit2gtk-4.0-doc gir1.2-webkit2-4.0 
libwebkit2gtk-4.0-37-gtk2 webkit2gtk-driver
Architecture: source
Version: 2.23.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian WebKit Maintainers 

Changed-By: Alberto Garcia 
Description:
 gir1.2-javascriptcoregtk-4.0 - JavaScript engine library from WebKitGTK+ - 
GObject introspection
 gir1.2-webkit2-4.0 - Web content engine library for GTK+ - GObject 
introspection data
 libjavascriptcoregtk-4.0-18 - JavaScript engine library from WebKitGTK+
 libjavascriptcoregtk-4.0-bin - JavaScript engine library from WebKitGTK+ - 
command-line interpre
 libjavascriptcoregtk-4.0-dev - JavaScript engine library from WebKitGTK+ - 
development files
 libwebkit2gtk-4.0-37 - Web content engine library for GTK+
 libwebkit2gtk-4.0-37-gtk2 - Web content engine library for GTK+ - GTK+2 plugin 
process
 libwebkit2gtk-4.0-dev - Web content engine library for GTK+ - development files
 libwebkit2gtk-4.0-doc - Web content engine library for GTK+ - documentation
 webkit2gtk-driver - WebKitGTK+ WebDriver support
Closes: 914986
Changes:
 webkit2gtk (2.23.2-1) experimental; urgency=medium
 .
   * New upstream development release (Closes: #914986).
   * debian/patches/build-minibrowser.patch,
 debian/patches/detect-jit.patch,
 debian/patches/fix-ftbfs-armel.patch:
 + Remove these patches, they are now upstream.
   * debian/patches/detect-woff.patch,
 debian/patches/fix-ftbfs-m68k.patch,
 debian/patches/fix-ftbfs-x32.patch:
 + Refresh these patches.
   * debian/source/lintian-overrides:
 + Update source-is-missing overrides.
   * debian/patches/missing-gtkdoc-files.patch:
 + Upstream forgot to add Tools/gtkdoc to the tarball.
   * debian/rules:
 + Make Tools/gtkdoc/generate-gtkdoc executable.
   * debian/control:
 + Update Standards-Version to 4.3.0 (no changes).
Checksums-Sha1:
 

Bug#918669: marked as done (waitress FTBFS: An error happened in rendering the page api. Reason: TemplateNotFound())

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 15:21:07 +
with message-id 
and subject line Bug#918669: fixed in waitress 1.2.0~b2-2
has caused the Debian Bug report #918669,
regarding waitress FTBFS: An error happened in rendering the page api. Reason: 
TemplateNotFound()
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=waitress=all=1.2.0~b2-1=1546883794=0

...
sphinx-build -b html -d _build/doctrees  -N -D html_last_updated_fmt="January 
07, 2019" . _build/html
Running Sphinx v1.7.9
loading pickled environment... not yet created
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 12 source files that are out of date
updating environment: 12 added, 0 changed, 0 removed
reading sources... [  8%] api
reading sources... [ 16%] arguments
reading sources... [ 25%] design
reading sources... [ 33%] differences
reading sources... [ 41%] filewrapper
reading sources... [ 50%] glossary
reading sources... [ 58%] index
reading sources... [ 66%] logging
reading sources... [ 75%] reverse-proxy
reading sources... [ 83%] runner
reading sources... [ 91%] socket-activation
reading sources... [100%] usage

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  8%] api

Theme error:
An error happened in rendering the page api.
Reason: TemplateNotFound()
make[2]: *** [Makefile:30: html] Error 2
--- End Message ---
--- Begin Message ---
Source: waitress
Source-Version: 1.2.0~b2-2

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated waitress 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: Tue, 08 Jan 2019 15:54:08 +0100
Source: waitress
Binary: python-waitress python3-waitress python-waitress-doc
Architecture: all source
Version: 1.2.0~b2-2
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 918669
Description: 
 python3-waitress - production-quality pure-Python WSGI server (Python 3)
 python-waitress-doc - production-quality pure-Python WSGI server 
(documentation)
 python-waitress - production-quality pure-Python WSGI server
Changes:
 waitress (1.2.0~b2-2) unstable; urgency=medium
 .
   * Unbreak docco build (Closes: #918669).
Checksums-Sha1: 
 dbadde37b5dddf804b4680023f7ea89d80b3a2e3 1957 waitress_1.2.0~b2-2.dsc
 8788237e85e0c87557f45a93fc26d1c9212ccef3 4352 waitress_1.2.0~b2-2.debian.tar.xz
 158fc20e61e49d844f9f8234db0f4d3a115610e5 53220 
python-waitress-doc_1.2.0~b2-2_all.deb
 70a94afeaac35f59094299f693a91ba552cc1e7d 76712 
python-waitress_1.2.0~b2-2_all.deb
 c548d46c0fa9f380768c3ebc43b899efb31decdf 76724 
python3-waitress_1.2.0~b2-2_all.deb
 4cc6479b0010dad3eba7d4d3455a941d1d396d93 7561 
waitress_1.2.0~b2-2_amd64.buildinfo
Checksums-Sha256: 
 db1c9a4edae7d6b0362ba8a711d9c04f9c9224cbe03d8710ce43b0f79f0ecb9b 1957 
waitress_1.2.0~b2-2.dsc
 445d2b5a3596b5bdc25f70c685ef8707622cf1ac24b5add6722f2a38a305eb2d 4352 
waitress_1.2.0~b2-2.debian.tar.xz
 b8e8b1a1ca8aea7b9827c1cad6927d830d9bc2c47f963f82e2f47bfc4d7db6e5 53220 
python-waitress-doc_1.2.0~b2-2_all.deb
 e3a3d20a56db4328fb93b8bbceb0ba64eaf01f225a691e8b3b544d1ffa1898b4 76712 
python-waitress_1.2.0~b2-2_all.deb
 66ebeb2908b28c1f86145d8eb49cc5aea728541dc53d5d88ce8a7f93dc6def68 76724 
python3-waitress_1.2.0~b2-2_all.deb
 7bc62dbd9529c6cfb9c4610aa335c3f6635e4943b70cf3ab1215bde434a123f0 7561 
waitress_1.2.0~b2-2_amd64.buildinfo
Files: 
 98652a03776f418d605a2bba06136e51 1957 python optional waitress_1.2.0~b2-2.dsc
 00eb680246dcb2b8252e68dfa3db2347 4352 python optional 
waitress_1.2.0~b2-2.debian.tar.xz
 

Bug#916074: marked as done (pcc: useless without libpcc-dev)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 15:20:43 +
with message-id 
and subject line Bug#916074: fixed in pcc 1.2.0~DEVEL+20181216-1
has caused the Debian Bug report #916074,
regarding pcc: useless without libpcc-dev
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.)


-- 
916074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcc
Version: 1.2.0~DEVEL+20181202-1
Severity: serious
Control: block -1 by 915633

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

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


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

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

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

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

pcc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pcc
Source-Version: 1.2.0~DEVEL+20181216-1

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated pcc 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: Mon, 07 Jan 2019 22:57:07 +0800
Source: pcc
Binary: pcc
Architecture: source
Version: 1.2.0~DEVEL+20181216-1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl 
Changed-By: Yangfl 
Description:
 pcc- Portable C Compiler
Closes: 916074
Changes:
 pcc (1.2.0~DEVEL+20181216-1) unstable; urgency=medium
 .
   * New upstream release
   * Remove arthictures other than i386/amd64, due to lack of maintaince
   * Move libpcc-dev dep level from Recommends to Depends (Closes: #916074)
   * Bump Standards-Version to 4.3.0
   * Bump debhelper compat to 12
Checksums-Sha1:
 78accdf8973adfdfe6aedbc62c4c7e8ca9ee43db 1889 pcc_1.2.0~DEVEL+20181216-1.dsc
 dbafeede018f5ff2f862c7408bb2b61b64f0a15c 943418 
pcc_1.2.0~DEVEL+20181216.orig.tar.gz
 2e4c8ad3952e05931f02591190e162e267330cbc 6860 
pcc_1.2.0~DEVEL+20181216-1.debian.tar.xz
 9851a5c08f2116b6fc557979887bcb68942528a2 5713 
pcc_1.2.0~DEVEL+20181216-1_amd64.buildinfo
Checksums-Sha256:
 8af02edb7e75ad171afd459d29b499709dfc266585f0a2a9dd51bd11890dcc38 1889 
pcc_1.2.0~DEVEL+20181216-1.dsc
 e3f73a456c048dc2bd3fbbb0fa94242616562a902c1be835c9255d5e1ec0bb2b 943418 
pcc_1.2.0~DEVEL+20181216.orig.tar.gz
 23c2e75f9f484b7a7590e4c469df5254f996065efb4db469c6df6d332ef9cffd 6860 
pcc_1.2.0~DEVEL+20181216-1.debian.tar.xz
 aaec4856f808c364d4a0cb3a512c3d8ccd4e225b69c58e67b5fb7f527f73fbd5 5713 
pcc_1.2.0~DEVEL+20181216-1_amd64.buildinfo
Files:
 8c13cf454738133d2eeeab51a6bc502e 1889 devel optional 
pcc_1.2.0~DEVEL+20181216-1.dsc
 cd2cc50bdb6de5ecb057259805807899 943418 devel optional 
pcc_1.2.0~DEVEL+20181216.orig.tar.gz
 badc9f89fe31937ecf630949a1cea5f2 6860 devel optional 
pcc_1.2.0~DEVEL+20181216-1.debian.tar.xz
 c2d3da13004c72ab3a0467dc73f51b51 5713 devel optional 
pcc_1.2.0~DEVEL+20181216-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlw0t1IACgkQwpPntGGC
Ws4GYhAAls111ZH82F+o6CGwWAZR2nwv46SGDe5X1yZ1shk/Map5JhErI3jqKAH2
5F2Emag9Pju0mnL7PbscdMt5gLgQrhiX7jhKX9cC7d3AR9aeNdiCse6ozMWuJO+J
FMHW551Si/DrGVZZ5FhTk0A/lBB/nG2TUpK+1oaGrqTRmFsQMnN+weUZ2Le3OpJz

Bug#918642: marked as done (imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in))

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 15:19:34 +
with message-id 
and subject line Bug#918642: fixed in imagemagick 8:6.9.10.23+dfsg-2
has caused the Debian Bug report #918642,
regarding imagemagick: identify 6.9.10-23 doesn't convert units (pixels per 
cm/in)
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.)


-- 
918642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick
Version: 8:6.9.10.23+dfsg-1
Severity: serious
Tags: upstream

Dear Maintainer,

After the upgrade from 6.9.10.14 to 6.9.10.23, I noticed that the
autopkgtests for the package ruby-mini-magick is failing due to one test
about checking units to show the size of the image in cm and inches.

I could isolate the problem by running the `identify` command on a test
image (rgb.png in the spec/fixtures directory of the ruby-mini-magick
source package).

Running:
identify -verbose -units PixelsPerInch rgb.png > output_in.txt
identify -verbose -units PixelsPerCentimeter rgb.png > output_cm.txt
diff -u output_in.txt output_cm.txt

gives me the following with 8:6.9.10-14 from testing:

--- /tmp/output_cm.txt  2019-01-07 22:32:49.257702663 +0100
+++ /tmp/output_in.txt  2019-01-07 22:32:40.457055525 +0100
@@ -3,9 +3,9 @@
   Mime type: image/png
   Class: PseudoClass
   Geometry: 16x12+0+0
-  Resolution: 118.11x118.11
-  Print size: 0.135467x0.1016
-  Units: PixelsPerCentimeter
+  Resolution: 300x300
+  Print size: 0.053x0.04
+  Units: PixelsPerInch
   Colorspace: sRGB
   Type: Palette
   Base type: Undefined
@@ -118,12 +118,11 @@
 signature: 0d23f0078b8f89ca473e67bb38773cb94fd8ec5591e4207e83ff95cb27a6a0dd
   Artifacts:
 filename: rgb.png
-units: PixelsPerCentimeter
+units: PixelsPerInch
 verbose: true
   Tainted: False
   Filesize: 359B
   Number pixels: 192
-  Pixels per second: 19200B
-  User time: 0.010u
-  Elapsed time: 0:01.010
+  User time: 0.000u
+  Elapsed time: 0:01.000
   Version: ImageMagick 6.9.10-14 Q16 x86_64 20181023 https://imagemagick.org

whereas it gives the following with 8:6.9.10-23 (with a suffix -23 to
the text files).

--- /tmp/output_cm-23.txt   2019-01-07 22:34:38.136761722 +0100
+++ /tmp/output_in-23.txt   2019-01-07 22:34:45.201163917 +0100
@@ -5,7 +5,7 @@
   Geometry: 16x12+0+0
   Resolution: 118.11x118.11
   Print size: 0.135467x0.1016
-  Units: PixelsPerCentimeter
+  Units: PixelsPerInch
   Colorspace: sRGB
   Type: Palette
   Base type: Undefined
@@ -118,7 +118,7 @@
 signature: 0d23f0078b8f89ca473e67bb38773cb94fd8ec5591e4207e83ff95cb27a6a0dd
   Artifacts:
 filename: rgb.png
-units: PixelsPerCentimeter
+units: PixelsPerInch
 verbose: true
   Tainted: False
   Filesize: 359B

Maybe it was induced by this change?
https://github.com/ImageMagick/ImageMagick6/commit/8c7648a1adf7bba35594074f191affd3ff3263bb

Attaching the reference image and the full output files.

I am setting severity serious, as it breaks the testsuite of
ruby-mini-magick and provides wrong data when identifying images.

Thank you in advance

Cédric



-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
compare:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
convert:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
composite:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
conjure:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
display:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
identify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
import:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
mogrify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
montage:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
stream:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org

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

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

Versions of packages imagemagick depends on:
ii  imagemagick-6.q16  8:6.9.10.23+dfsg-1

imagemagick recommends no packages.

Processed: jemalloc: third time's the charm?

[Debian Bug Tracking System]

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

> close 897076 5.0.1-1
Bug #897076 [src:jemalloc] libjemalloc1: Version 3.6.0-11(unstable) error 
: Error in munmap(): Invalid argument
Bug #843926 [src:jemalloc] jemalloc uses a hard coded page size detected during 
build
Ignoring request to alter fixed versions of bug #897076 to the same values 
previously set
Ignoring request to alter fixed versions of bug #843926 to the same values 
previously set
Bug #897076 [src:jemalloc] libjemalloc1: Version 3.6.0-11(unstable) error 
: Error in munmap(): Invalid argument
Bug #843926 [src:jemalloc] jemalloc uses a hard coded page size detected during 
build
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: notfound 834298 in 3.17.1-3

[Debian Bug Tracking System]

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

> notfound 834298 3.17.1-3
Bug #834298 {Done: Mark Brown } [nis] nis: Can't ypbind
No longer marked as found in versions nis/3.17.1-3.
> thanks
Stopping processing here.

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

Bug#918641: marked as done (pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava)

[Debian Bug Tracking System]

Your message dated Tue, 08 Jan 2019 14:44:06 +
with message-id 
and subject line Bug#918641: fixed in fava 1.9-3
has caused the Debian Bug report #918641,
regarding pkg_resources.DistributionNotFound: The 'cheroot' distribution was 
not found and is required by fava
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.)


-- 
918641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fava
Version: 1.9-3
Severity: serious

As per subject, running fava fails with the following traceback:

  Traceback (most recent call last):
File "/usr/bin/fava", line 6, in 
  from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3126, 
in 
  @_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3110, 
in _call_aside
  f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3139, 
in _initialize_master_working_set
  working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 581, 
in _build_master
  ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 898, 
in require
  needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 784, 
in resolve
  raise DistributionNotFound(req, requirers)
  pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found 
and is required by fava

this should ideally be fixed by having cheroot ship an egg-info dir, but it's
being filed against fava for now to avoid testing migration.

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

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

Versions of packages python3-fava depends on:
ii  python3  3.7.1-3
ii  python3-babel2.6.0+dfsg.1-1
ii  python3-beancount2.1.3+hg20181225-3
ii  python3-click6.7+git20180829-1
ii  python3-flask1.0.2-3
ii  python3-flask-babel  0.11.2-2
ii  python3-jinja2   2.10-1
ii  python3-markdown22.3.7-1
ii  python3-ply  3.11-3
ii  python3-simplejson   3.15.0-1+b1

python3-fava recommends no packages.

python3-fava suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fava
Source-Version: 1.9-3

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

Debian distribution maintenance software
pp.
Stefano Zacchiroli  (supplier of updated fava 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: Tue, 08 Jan 2019 14:43:10 +0100
Source: fava
Binary: python3-fava
Architecture: source all
Version: 1.9-3
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Stefano Zacchiroli 
Description:
 python3-fava - Web interface for the double-entry accounting tool Beancount
Closes: 918641
Changes:
 fava (1.9-3) unstable; urgency=medium
 .
   * compat: bump debhelper level to 12
   * control: add missing build-dep on cheroot
   * control: depend on the minimum cheroot version that ships egg-info
 (Closes: #918641)
   * drop python3-fava.pyremove, because fava.help is needed as a module
Checksums-Sha1:
 8e06e7037034a099a80ea5b13fd59d5cab200198 2194 fava_1.9-3.dsc
 e4fd40828431f7b81c1693e38cdfa0e386a02d2d 2876 fava_1.9-3.debian.tar.xz
 f247ea8fccecc14d9e33828e4c9b7f95287a4bba 7625 fava_1.9-3_amd64.buildinfo
 418e579be5a04fb2628c76448a09e089c691124e 470504 python3-fava_1.9-3_all.deb
Checksums-Sha256:
 bc2ce301e02a8c3ff272e4c5a6313410db9bdc89cf895b0a9dd8e3d68e766117 2194 
fava_1.9-3.dsc
 

Bug#910856: sollya: test fails on most architectures

[Jerome BENOIT]

Thanks Adrian !
-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386

[Balint Reczey]

Hi Bastien,

On Mon, Jan 7, 2019 at 11:17 PM Bastien ROUCARIES
 wrote:
>
> Hi,
>
> I have uploaded a newer version fixing the problem. Could you ask
> release team a rebuild.

Thanks!
I filed #918706 for the rebuilds, please follow up on it if needed.

>
> BTW could you get a glimpse at ruby-mini-magick ? It seems choked

I see this is being resolved in #918642, thanks!

Cheers,
Balint


>
> Bastien
>
> On Sat, Jan 5, 2019 at 4:08 PM Balint Reczey
>  wrote:
> >
> > Hi Bastien,
> >
> > On Fri, Jan 4, 2019 at 8:41 PM Balint Reczey
> >  wrote:
> > >
> > > Hi,
> > >
> > > On Thu, Dec 20, 2018 at 6:46 AM Bastien ROUCARIES
> > >  wrote:
> > > >
> > > > On Wed, Dec 19, 2018 at 12:09 PM Balint Reczey
> > > >  wrote:
> > > > >
> > > > > Package: imagemagick
> > > > > Version: 8:6.9.10.14+dfsg-1
> > > > > Severity: grave
> > > > > Control: forwareded -1 
> > > > > https://github.com/ImageMagick/ImageMagick6/issues/31
> > > > > Control: tags -1 upstream fixed-upstream
> > > > > Control: affects -1 ruby-rmagick
> > > > >
> > > > > Hi,
> > > > >
> > > > > The ABI broke in 6.9.10-11 due to changing MagickDoubleType to double
> > > > > from long double.
> > > > > This breaks ruby-rmagick and possibly other reverse dependencies, thus
> > > > > after fixing imagemagick please check if some reverse dependencies
> > > > > need to be rebuilt. The fix will be available in the .18 upstream
> > > > > release.
> > > >
> > > > Exact, this will need a so bump I suppose...
> > >
> > > Since the ABI broke only in unstable and testing and only affected
> > > i386 and possibly a few rare arches not in Ubuntu I'd say a few
> > > rebuilds would suffice. Upstream did not do a major ABI bump either
> > > and released the fix.
> >
> > I have uploaded an NMU to DELAYED/5 with the attached fix, which is
> > already included in Ubuntu.
> > This will enter the archive before the transition freeze thus Buster
> > will be fixed even if no upload is made to imagemagick in the next
> > week, but feel free to override it an upload a better fix like a full
> > new upstream release.
> >
> > Cheers,
> > Balint
> >
> > >
> > > Cheers,
> > > Balint
> > >
> > > >
> > > > Bastien
> > > >
> > > >
> > > >
> > > > >
> > > > > Cheers,
> > > > > Balint
> > > > >
> > > > > --
> > > > > Balint Reczey
> > > > > Ubuntu & Debian Developer
> > > > >
> > >
> > >
> > >
> > > --
> > > Balint Reczey
> > > Ubuntu & Debian Developer
> >
> >
> >
> > --
> > Balint Reczey
> > Ubuntu & Debian Developer



--
Balint Reczey
Ubuntu & Debian Developer

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

[Markus Koschany]

Control: severity -1 important

Hi,

I have reverted the change and uploaded the old 2.14.6 version of
jackrabbit again. This will ensure that davmail also continues to work
in Ubuntu and other distributions that sync packages directly from
unstable. As I previously wrote davmail should be updated to a supported
version of jackrabbit-webdav in the future, so this issue might become
RC again.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #917174 [davmail] davmail: FTBFS with libjackrabbit-java 2.18.0
Severity set to 'important' from 'serious'

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

Bug#905674: parallel: move to nonfree

[Ævar Arnfjörð Bjarmason]

Package: parallel
Followup-For: Bug #905674

Dear Maintainer,

In fixing #905674 you've completely removed the 'parallel --citation'
option from the package, which seems like overreach.

Yes the default notification is spammy and I think Debian should
remove it, it's not scalable that every program in Debian have some
click-through like this, but completely removing the "how do I cite
this program?" functionality the author wants in there seems like
overreach.

I'd like to suggest an alternate approach. Drop the
remove-overreaching-citation-request.patch patch and just ship this
config as part of the package:

$ cat /etc/parallel/config 
# Quiet the citation message
--will-cite

This is what I do in my own in-house build of parallel (for RHEL).

You may still (reading the previous discussion) want to carry some
patch to remove the "If you pay 1 EUR you should feel free to use
GNU Parallel without citing" part of the message.


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

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

Versions of packages parallel depends on:
ii  perl 5.28.1-3
ii  procps   2:3.3.15-2
ii  sysstat  12.0.1-1+b1

parallel recommends no packages.

parallel suggests no packages.

-- no debconf information

Processed: Re-mark bugs as found/fixed with their right versions

[Debian Bug Tracking System]

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

> found 897076 3.6.0-3
Bug #897076 {Done: Faidon Liambotis } [src:jemalloc] 
libjemalloc1: Version 3.6.0-11(unstable) error : Error in munmap(): 
Invalid argument
Bug #843926 {Done: Faidon Liambotis } [src:jemalloc] 
jemalloc uses a hard coded page size detected during build
Marked as found in versions jemalloc/3.6.0-3 and reopened.
Marked as found in versions jemalloc/3.6.0-3 and reopened.
> fixed 897076 5.0.1-1
Bug #897076 [src:jemalloc] libjemalloc1: Version 3.6.0-11(unstable) error 
: Error in munmap(): Invalid argument
Bug #843926 [src:jemalloc] jemalloc uses a hard coded page size detected during 
build
Marked as fixed in versions jemalloc/5.0.1-1.
Marked as fixed in versions jemalloc/5.0.1-1.
> thanks
Stopping processing here.

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