Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

[Diane Trout]

On Wed, 2019-01-16 at 08:55 +0100, Axel Beckert wrote:
> 
> 
> # summary of how this script can be called:
> #*  `configure' 
> [...]
> case "$1" in
> configure)
> # configure the control channel if run for the first time
> if [ -z "$2" ]; then
> dnssec-trigger-control-setup
> fi
> ;;
> 
> So as I read it, dnssec-trigger-control-setup is only called if there
> was no previously configured version installed and is hence never
> called when upgrading the package and hence never removes, the too
> small old keys on upgrade.
> 

I'm tired enough I wanted to double check the logic of a solution
before trying to implement it.

the check to remove too small keys should probably be moved out of
dnssec-trigger-control-setup and into the postinst script.

Then the "if [ -z "$2" ]" conditional in the post should be replaced
with checking for the existence of the keys instead of the package
version number to decide if the control-setup script is called.


Something like

configure)
debian_remove_small_keys $SERVER
debian_remove_small_keys $CONTROL
if [ \! -e /etc/dnssec-trigger/dnssec_trigger_control.key ]; then
dnssec-trigger-control-setup
fi

How's that sound to you?

Diane
  

Processed: Re: julia: baseline violation on armhf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #919183 [src:julia] julia: baseline violation on armhf
Severity set to 'important' from 'serious'

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

Bug#919183: julia: baseline violation on armhf

[M. Zhou]

control: severity -1 important


This is not baseline violation. julia -C 
"armv7-a;armv7-a,neon;armv7-a,neon,vfp4"
compiles 3 branches of code, and the optimal branch will be selected
during runtime. The SIGILL raised during build on the buildd stems from
LLVM's incorrect CPU detection.


Here is a proof with QEMU emulated ARM Cortex-a7:


(sid_armhf-dchroot)lumin@abel:~$ julia
Invalid ARM instruction at 0xad4253d0: 0xf2800050

signal (4): Illegal instruction
in expression starting at no file:0
__init__ at ./sysinfo.jl:92
jl_apply_generic at /usr/bin/../lib/arm-linux-gnueabihf/libjulia.so.1 (unknown 
line)
unknown function (ip: 0xb6d7e006)
unknown function (ip: 0xb6d6e43a)
julia_init__threading at /usr/bin/../lib/arm-linux-gnueabihf/libjulia.so.1 
(unknown line)
unknown function (ip: 0x44df2c)
__libc_start_main at /lib/arm-linux-gnueabihf/libc.so.6 (unknown line)
unknown function (ip: 0x44dfc4)
Allocations: 3006 (Pool: 3002; Big: 4); GC: 0
Illegal instruction
(sid_armhf-dchroot)lumin@abel:~$ qemu-arm -cpu cortex-a7 julia
Error while loading julia: Permission denied
(sid_armhf-dchroot)lumin@abel:~$ qemu-arm -cpu cortex-a7 /usr/bin/julia
   _
   _   _ _(_)_ |  Documentation: https://docs.julialang.org
  (_) | (_) (_)|
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.0.3
 _/ |\__'_|_|_|\__'_|  |  Debian ⛬  julia/1.0.3+dfsg-1
|__/   |

julia>

Bug#919500: golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494)

[Arnaud Rebillout]

  Dear Go team,

I pushed a fix on Salsa, can you please review and upload these changes?
Thanks!

Regards,

  Arnaud

Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

[Ben Finney]

Control: tags -1 + confirmed

On 04-Oct-2018, Helmut Grohne wrote:

> At least the vast majority of failures is due to a similar 
> socket.gaierror.

I confirm that this behaviour is reproducible in a new SBuild chroot, 
created with ‘sbuild-debian-developer-setup’ (version “0.78.0-2”).

The behaviour is not specific to SBuild chroot though. It also occurs 
when running the test suite in a normal development environment.

I suspect there's something changed with the ‘httpretty’ testing 
library; either that, or something changed in recent Python 3 
versions.

-- 
 \ “A man must consider what a rich realm he abdicates when he |
  `\   becomes a conformist.” —Ralph Waldo Emerson |
_o__)  |
Ben Finney 

Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #910295 [src:dput] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name 
or service not known
Added tag(s) confirmed.

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

Bug#912633: Possible conflict betwwen courier-imap and courier-imap-ssl?

[Erik de Castro Lopo]

Hi all,

I have just run into this same issue and its a bit of a pain.

One thing I notivce however is that I have:
  
  # dpkg -l | grep courier-imap
  ii  courier-imap  5.0.5+1.0.5-1 amd64   Courier mail server - IMAP 
server
  ii  courier-imap-ssl  4.18.1+0.78.0-2   all Courier mail server - IMAP 
over TLS [transitional]

I also notice thatt these two are compiled from different source packages:

  # apt-cache show courier-imap
  Package: courier-imap
  Source: courier (1.0.5-1)
  Version: 5.0.5+1.0.5-1

  # apt-cache show courier-imap-ssl
  Package: courier-imap-ssl
  Source: courier (0.78.0-2)
  Version: 4.18.1+0.78.0-2

I also know that courier-imap-ssl depends on courier-imap but I wonder if
the fact they are compiled from different versions of the source package
is relevant.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#918391: marked as done (ruby-spring FTBFS with rails 5.2.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Jan 2019 02:46:01 +
with message-id 
and subject line Bug#918391: fixed in ruby-spring 2.0.2-1
has caused the Debian Bug report #918391,
regarding ruby-spring FTBFS with rails 5.2.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.)


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

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

...
/usr/lib/ruby/vendor_ruby/bundler/resolver.rb:289:in `block in 
verify_gemfile_dependencies_are_found!': Could not find gem 'activesupport (~> 
4.2.0)' in any of the gem sources listed in your Gemfile. (Bundler::GemNotFound)
...
--- End Message ---
--- Begin Message ---
Source: ruby-spring
Source-Version: 2.0.2-1

We believe that the bug you reported is fixed in the latest version of
ruby-spring, 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.
Cédric Boutillier  (supplier of updated ruby-spring 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: Thu, 17 Jan 2019 01:56:09 +0100
Source: ruby-spring
Binary: ruby-spring
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-spring - Rails application preloader
Closes: 918391
Changes:
 ruby-spring (2.0.2-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Remove myself from Uploaders:
 .
   [ Cédric Boutillier ]
   * New upstream version 2.0.2
 + support for rails 5 (Closes: #918391)
   * Use salsa.debian.org in Vcs-* fields
   * Bump Standards-Version to 4.3.0 (no changes needed)
   * Bump debhelper compatibility level to 11
   * Refresh dont-assume-rubygems.patch
   * Add myself as an upload temporarily
   * Remove unused patches
   * Add no-bump.patch and hardcode_version.patch to fix autopkgtest
Checksums-Sha1:
 e72790a48112c2df8edf28cb392b1abccadf30a7 1697 ruby-spring_2.0.2-1.dsc
 efc1cc88b532d0f2a7cd522f2e6cda7ccd74 43318 ruby-spring_2.0.2.orig.tar.gz
 3bbab9de8bb5769d6f080599a31b0894b0b302f4 3192 ruby-spring_2.0.2-1.debian.tar.xz
 5aafde5f3729a9276ec36b8604dcea69f82a7312 14861 
ruby-spring_2.0.2-1_source.buildinfo
Checksums-Sha256:
 2f95e70f9b1a4fb904724c9489e41f0168c38868c93ee58c1e84990da1f0d672 1697 
ruby-spring_2.0.2-1.dsc
 fd743dd6110fb03693f89b0aeadf720702f9a28be470f3d73540767048b922db 43318 
ruby-spring_2.0.2.orig.tar.gz
 645a719d75e94c22d408c0ce103fda723d2f1197697b9fcd7bbfb9ac8cdfb219 3192 
ruby-spring_2.0.2-1.debian.tar.xz
 0af7df8699ed343e9178e5b482fcb89eef5bffe1083782e7615039a3539f3289 14861 
ruby-spring_2.0.2-1_source.buildinfo
Files:
 31192afa5bd09717eed720e045977c6f 1697 ruby optional ruby-spring_2.0.2-1.dsc
 82d21a90e364bc1984e6b8d4c383a411 43318 ruby optional 
ruby-spring_2.0.2.orig.tar.gz
 dc97a8099f4959d50b83734248c22fd9 3192 ruby optional 
ruby-spring_2.0.2-1.debian.tar.xz
 b4ef2d1e81916100e6d96097b1cc6a60 14861 ruby optional 
ruby-spring_2.0.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlw/3YEACgkQia+CtznN
IXoMKgf/fYehArJYkLxu7noaJ4QEXkhiraDnWn2rmWHT8RkHBG+pDAzvU+dwk4Sj
kOCwwuBwjCy+LDBh8cJM3Izmmu5v+fAZceKwp6Pr8ar5P4C7N5nBtAvQ2EuJmuTc
eubSiuwAYZzk/14pSWpPzPcPOxerI2TmYcYhZCM9OblBLOY9scvdAuaXqv0dnUkE
ntCBaPmnwAA67xu5q+Q2iLtms7yH0GUfevJTqEBuXHjQe9QqTAlGcbgoGYLjIB+4
BLZ7RrHg/uU6kXsocQl7c9xD9ZQaVAF30HblwtKjV1/X9ijnIt/cp78HKUltNRHX
VRQ7LgUnWNyrZM+9Woz0SHeavYOsaQ==
=n5yI
-END PGP SIGNATURE End Message ---

Bug#919523: marked as done (libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 17 Jan 2019 02:44:46 +
with message-id 
and subject line Bug#919523: fixed in libmodule-install-readmefrompod-perl 
0.30-2
has caused the Debian Bug report #919523,
regarding libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests)
to be marked as done.

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

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


-- 
919523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmodule-install-readmefrompod-perl
Version: 0.30-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
I can run 'make' good
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Module::Install::ReadmeFromPod
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cp lib/Module/Install/ReadmeFromPod.pm blib/lib/Module/Install/ReadmeFromPod.pm
Manifying 1 pod document
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 
'blib/arch')" t/*.t
# Testing Module::Install::ReadmeFromPod 0.30, Perl 5.028001, /usr/bin/perl
t/00_compile.t ... 
1..1
ok 1 - use Module::Install::ReadmeFromPod;
ok
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# include /<>/dist/pOKZQrzH2U/inc/Module/Install.pm
# include inc/Module/Install/Metadata.pm
# include inc/Module/Install/Base.pm
# include inc/Module/Install/ReadmeFromPod.pm
# readme_from README.pm to txt
# readme_from README.pm to htm
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# readme_from README.pm to man
# readme_from README.pm to md
# include inc/Module/Install/WriteAll.pm
# include inc/Module/Install/Makefile.pm
# include inc/Module/Install/Win32.pm
# include inc/Module/Install/Can.pm
# include inc/Module/Install/Fetch.pm
# Generating a Unix-style Makefile
# Writing Makefile for Foo::Bar
# Writing MYMETA.yml and MYMETA.json
# Writing META.yml
# make[2]: Entering directory '/<>/dist/pOKZQrzH2U'
# rm -f \
#   Bar.bso Bar.def \
#   Bar.exp Bar.x \
#blib/arch/auto/Foo/Bar/extralibs.all \
#   blib/arch/auto/Foo/Bar/extralibs.ld Makefile.aperl \
#   *.a *.o \
#   *perl.core MYMETA.json \
#   MYMETA.yml blibdirs.ts \
#   core core.*perl.*.? \
#   core.[0-9] core.[0-9][0-9] \
#   core.[0-9][0-9][0-9] core.[0-9][0-9][0-9][0-9] \
#   core.[0-9][0-9][0-9][0-9][0-9] libBar.def \
#   mon.out perl \
#   perl perl.exe \
#   perlmain.c pm_to_blib \
#   pm_to_blib.ts so_locations \
#   tmon.out 
# rm -rf \
#   blib 
# mv Makefile Makefile.old > /dev/null 2>&1
# rm -f \
#   Makefile Makefile.old 
# rm -rf \
#   Foo-Bar-0.01 MYMETA.yml 
# rm -f Foo-Bar-0.01.tar.gz
# rm -f MANIFEST.bak _build
# "/usr/bin/perl" "-Iinc" "-Ilib" "-MModule::Install::Admin" -e "remove_meta()"
# rm -rf inc
# "/usr/bin/perl" "-Iinc" "-MExtUtils::Manifest=fullcheck" -e fullcheck
# Problem opening MANIFEST: No such file or directory at 
/usr/share/perl/5.28/ExtUtils/Manifest.pm line 349.
# Problem opening MANIFEST: No such file or directory at 
/usr/share/perl/5.28/ExtUtils/Manifest.pm line 349.
# Not in MANIFEST: Makefile.PL
# Not in MANIFEST: README
# Not in MANIFEST: README.1
# Not in MANIFEST: README.htm
# Not in MANIFEST: README.md
# Not in MANIFEST: README.pm
# make[2]: Leaving directory '/<>/dist/pOKZQrzH2U'
t/01_dist.t .. 
1..13
ok 1 - Exists: 'inc/Module/Install/ReadmeFromPod.pm'
ok 2 - There is a README file
ok 3 - There is a README.htm file
ok 4 - There is a README.md file
ok 5 - There is a README.1 file
ok 6 - README contains only unix newlines
ok 7 - README.htm contains only unix newlines
ok 8 - README.md contains only unix newlines
ok 9 - README.1 contains only 

Bug#919523: Bug #919523 in libmodule-install-readmefrompod-perl marked as pending

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #919523 in libmodule-install-readmefrompod-perl 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/perl-team/modules/packages/libmodule-install-readmefrompod-perl/commit/3fafad886e0d6610d5da4d8ef3610760326d6371


Add patch 1001 to avoid bogusly testing if PDF file contains only unix 
newlines. Closes: Bug#919523. Thanks to Santiago Vila.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919523

Processed: Bug #919523 in libmodule-install-readmefrompod-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919523 [src:libmodule-install-readmefrompod-perl] 
libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests)
Added tag(s) pending.

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

Bug#919397: marked as done (apcalc FTBFS on 32bit big endian)

[Debian Bug Tracking System]

Your message dated Thu, 17 Jan 2019 01:49:21 +
with message-id 
and subject line Bug#919397: fixed in apcalc 2.12.7.2-2
has caused the Debian Bug report #919397,
regarding apcalc FTBFS on 32bit big endian
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.)


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

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

...
In file included from qmath.h:32,
 from cmath.h:32,
 from value.h:33,
 from calc.h:33,
 from file.c:39:
file.c: In function 'filepos2z':
zmath.h:85:46: error: incompatible types when assigning to type 'HALF' {aka 
'long unsigned int'} from type 'FILEPOS' {aka 'struct _G_fpos_t'}
 #define SWAP_HALF_IN_B32(dest, src) (*(dest) = *(src))
  ^
fposval.h:15:42: note: in expansion of macro 'SWAP_HALF_IN_B32'
 #define SWAP_HALF_IN_FILEPOS(dest, src)  SWAP_HALF_IN_B32(dest, src)
  ^~~~
file.c:1370:2: note: in expansion of macro 'SWAP_HALF_IN_FILEPOS'
  SWAP_HALF_IN_FILEPOS(ret.v, );
  ^~~~
make[1]: *** [Makefile:2364: file.o] Error 1
--- End Message ---
--- Begin Message ---
Source: apcalc
Source-Version: 2.12.7.2-2

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

Debian distribution maintenance software
pp.
Martin Buck  (supplier of updated apcalc 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: Mon, 14 Jan 2019 00:50:42 +0100
Source: apcalc
Binary: apcalc apcalc-common apcalc-dev
Architecture: source all i386
Version: 2.12.7.2-2
Distribution: unstable
Urgency: low
Maintainer: Martin Buck 
Changed-By: Martin Buck 
Description:
 apcalc - Arbitrary precision calculator (original name: calc)
 apcalc-common - Arbitrary precision calculator (common files)
 apcalc-dev - Library for arbitrary precision arithmetic
Closes: 919397
Changes:
 apcalc (2.12.7.2-2) unstable; urgency=low
 .
   * Re-enable filepos patch, still required on mips to avoid FTBFS.
 Closes: #919397
   * Properly honor CPPFLAGS and LDFLAGS, also for intermediate binaries.
 Avoids dpkg-buildflags-missing build log checker warning.
Checksums-Sha1:
 b06685dd0ae46c1b7f26d841b559d0f5cb155608 1923 apcalc_2.12.7.2-2.dsc
 93f2b556daf230c0f624d9276e964e78587faf02 13156 apcalc_2.12.7.2-2.debian.tar.xz
 a401ef5db587e854b230de6a7add7e366700f09e 569184 
apcalc-common_2.12.7.2-2_all.deb
 0ef737211394505343f28a222c50a9959eb6e35b 741212 
apcalc-dbgsym_2.12.7.2-2_i386.deb
 10807247c6a0a9d2fe3ef101421948fe9c313931 540216 apcalc-dev_2.12.7.2-2_i386.deb
 81849318ffd52c7d56d97a2d4cb1b96626359c76 6112 apcalc_2.12.7.2-2_i386.buildinfo
 457d64dc4fbdcc0e379557fa734ebb7ba6181f34 333604 apcalc_2.12.7.2-2_i386.deb
Checksums-Sha256:
 f049f1534b02998b18831af6f41523450e6433ce66db08d9458201c2f9b2a46d 1923 
apcalc_2.12.7.2-2.dsc
 3cd34d323f1cc1362cd9cbc1e2e6dde87c919276bc1248fb3422ccc67575f112 13156 
apcalc_2.12.7.2-2.debian.tar.xz
 573e52457820e574bc6a0ae7929ac33a362d76b55903a4ccbf92ff23d6bd1bd0 569184 
apcalc-common_2.12.7.2-2_all.deb
 0811388e1683e525f53e83fa9a2ca1e5e42bb1225ce91e7ece7c068e2ae6d06b 741212 
apcalc-dbgsym_2.12.7.2-2_i386.deb
 49052ea0945c178b17689f95a4834082acaed1b5b84afbe7d171b2cd7cc02a9c 540216 
apcalc-dev_2.12.7.2-2_i386.deb
 af8f429e3ea89bd95bf59eac6172e83f4002e17636480d128d1346132325bca9 6112 
apcalc_2.12.7.2-2_i386.buildinfo
 b7967fd8366f4bec248663aa8b4a07520cb67c08aa677a28156abf8ec79fbb9c 333604 
apcalc_2.12.7.2-2_i386.deb
Files:
 a8ad010ff86db29ba571f318499c084c 1923 math optional apcalc_2.12.7.2-2.dsc
 899fb382cb49257d773e9a9da5a11895 13156 math optional 
apcalc_2.12.7.2-2.debian.tar.xz
 186d499255e142011696e88683536703 569184 math optional 
apcalc-common_2.12.7.2-2_all.deb
 d9987fc48998c59719433e3403c20dd6 741212 debug optional 
apcalc-dbgsym_2.12.7.2-2_i386.deb
 

Bug#919371: mono won't migrate to testing, still b-d on gcc-5

[Jo Shields]

OK, I have a status update on this.

* I can't get a minimal patch set against mono-2018-06 branch (Mono
5.16) which builds the entire release to completion on s390x on versions
of gcc with PIC/PIE by default (Debian gcc-6 or later)
* I picked the version I uploaded, on the basis that it is part of the
`vs` packaging branch on mono-project.com, which mirrors what last went
into a stable release of Visual Studio for Mac (and hopefully should
have something resembling a vendor support story)
* I _can_ get a minimal patch set against mono-2018-08 (Mono 5.18)
* 5.18 Should not cause any major changes at a packaging level, compared
to 5.16 (i.e. it should not go into binary NEW)
* 5.18 is considered "stable" by the Mono runtime team, but not yet by
the Visual Studio for Mac team (the standalone runtime doesn't get QA
before releases, only as part of a larger VSMac release cycle)
* 5.18 might totally break on other architectures! There is no MIPS
testing upstream, so mipsel might be broken on any given release
(upstream builds for i386, armel, armhf, arm64, amd64, and ppc64el)

I don't want to preempt any product announcements, but 5.18 may ship
significantly faster than originally planned, meaning investing too much
time in fixing up 5.16 this week may be wasted, compared to 5.18 closer
to *mumble mumble*. I'll discuss with relevant stakeholders tomorrow.

On 15/01/2019 07:37, Jo Shields wrote:
> Thanks for the tracking bug. I spotted this last night and am working on 
> zelenka to convince the damn thing to build - it's something to do with PIE, 
> and only shows up as a problem with the Runtime crashing in the literal last 
> 30 seconds of the build step 
> 
> Sent from my iPhone
> 
>> On 15 Jan 2019, at 05:45, Matthias Klose  wrote:
>>
>> Package: src:mono
>> Version: 5.16.0.220+dfsg3-2
>> Severity: serious
>> Tags: sid buster
>>
>> mono won't migrate to testing, still b-d on gcc-5 on s390x.
>>
> 

Bug#919341: Bug#919458: lintian: add tag for empty executables

[Chris Lamb]

tags 919458 + pending
thanks

Hi Emilio,

> Could we add a lintian tag for empty executables, particularly in PATH? Then 
> we
> could turn that into an autoreject (after analysing the results when
> lintian.debian.org is updated) and help prevent this kind of brokenness in the
> future.

Note that this would have been picked up by:

  https://lintian.debian.org/tags/executable-not-elf-or-script.html

… but a stronger/louder message is indeed warranted here.


Regards,

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

Bug#919529: marked as done (CVE-2019-6256)

[Debian Bug Tracking System]

Your message dated Thu, 17 Jan 2019 00:01:38 +0100
with message-id <20190116230138.gb12...@ramacher.at>
and subject line Re: Bug#919529: CVE-2019-6256
has caused the Debian Bug report #919529,
regarding CVE-2019-6256
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.)


-- 
919529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblivemedia
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 2018.11.26-1

On 2019-01-17 00:00:13, Sebastian Ramacher wrote:
> Control: found -1 2016.11.28-1
> 
> On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote:
> > Source: liblivemedia
> > Severity: grave
> > Tags: security
> > 
> > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256
> > 
> > Cheers,
> > Moritz
> 
> Not sure if I'm missing something, but the PoC does not seem to work on
> buster/sid. On stretch I get segfaults, but only if I abort the PoC. So 
> marking
> as found in stable and closing for sid.

The actual mail to close the bug for sid.
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#919527: [Pkg-libvirt-maintainers] Bug#919527: Missing dependency against python3-distutils

[Laurent Bigonville]

Le 16/01/19 à 23:38, Guido Günther a écrit :

On Wed, Jan 16, 2019 at 11:08:21PM +0100, Laurent Bigonville wrote:

Package: virtinst
Version: 1:2.0.0-2
Severity: serious

Hi,

The regression tests are currently failing because the virtinst is
missing a dependency against python3-distutils:

autopkgtest [04:39:33]: test help.sh:  - - - - - - - - - - stderr - - - - - - - 
- - -
Traceback (most recent call last):
   File "/usr/share/virt-manager/virt-convert", line 19, in 
 from virtconv import VirtConverter
   File "/usr/share/virt-manager/virtconv/__init__.py", line 10, in 
 from virtconv.formats import VirtConverter
   File "/usr/share/virt-manager/virtconv/formats.py", line 10, in 
 from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils.spawn'

https://ci.debian.net/data/autopkgtest/testing/amd64/v/virt-manager/1712093/log.gz

Could you please add the needed dependency?

Already fixed in git.
Do you think you could do a new upload as well so the package can 
migrate to testing?

Bug#919529: CVE-2019-6256

[Sebastian Ramacher]

Control: found -1 2016.11.28-1

On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote:
> Source: liblivemedia
> Severity: grave
> Tags: security
> 
> Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256
> 
> Cheers,
> Moritz

Not sure if I'm missing something, but the PoC does not seem to work on
buster/sid. On stretch I get segfaults, but only if I abort the PoC. So marking
as found in stable and closing for sid.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#919529: CVE-2019-6256

[Debian Bug Tracking System]

Processing control commands:

> found -1 2016.11.28-1
Bug #919529 [src:liblivemedia] CVE-2019-6256
Marked as found in versions liblivemedia/2016.11.28-1.

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

Bug#918627: node-cacache FTBFS with nodejs 10.15.0

[Xavier]

Update to 11.3.2 fixes partially failing build. Last problem is in
node-readable-stream

Bug#919527: [Pkg-libvirt-maintainers] Bug#919527: Missing dependency against python3-distutils

[Guido Günther]

On Wed, Jan 16, 2019 at 11:08:21PM +0100, Laurent Bigonville wrote:
> Package: virtinst
> Version: 1:2.0.0-2
> Severity: serious
> 
> Hi,
> 
> The regression tests are currently failing because the virtinst is
> missing a dependency against python3-distutils:
> 
> autopkgtest [04:39:33]: test help.sh:  - - - - - - - - - - stderr - - - - - - 
> - - - -
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virt-convert", line 19, in 
> from virtconv import VirtConverter
>   File "/usr/share/virt-manager/virtconv/__init__.py", line 10, in 
> from virtconv.formats import VirtConverter
>   File "/usr/share/virt-manager/virtconv/formats.py", line 10, in 
> from distutils.spawn import find_executable
> ModuleNotFoundError: No module named 'distutils.spawn'
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/v/virt-manager/1712093/log.gz
> 
> Could you please add the needed dependency?

Already fixed in git.
 -- Guido

Processed: please remove Depends on common-lisp-controller

[Debian Bug Tracking System]

Processing control commands:

> block 913649 by -1
Bug #913649 [common-lisp-controller] should not ship with buster
913649 was blocked by: 911526 914700 915507 911527 914701
913649 was not blocking any bugs.
Added blocking bug(s) of 913649: 919530

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

Processed: tagging 919527

[Debian Bug Tracking System]

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

> tags 919527 + pending
Bug #919527 [virtinst] Missing dependency against python3-distutils
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#919530: please remove Depends on common-lisp-controller

[Sébastien Villemot]

Package: cl-awk
Version: 1-4
Severity: serious
Tags: patch sid buster
Control: block 913649 by -1

Dear Maintainer,

Please drop the Depends on common-lisp-controller. This package is obsolete,
and will not ship with Buster. It has been superseded by ASDF, which is shipped
by all Common Lisp implementations in Debian.

Dropping the dependency and the postinst and prerm scripts should be enough.
ASDF is able to locate the files where they are installed (i.e. under
/usr/share/common-lisp/).

Best,

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

Bug#919529: CVE-2019-6256

[Moritz Muehlenhoff]

Source: liblivemedia
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256

Cheers,
Moritz

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

[Séverin Lemaignan]

Hi Andreas,

Sorry for the delay.
Yes, I'm absoluetly fine with the maintenance between transfered to 
Debian science. That's were it belongs, and I do not have the time 
currently to properly care for the package anyway. Please proceed!


Thanks!
Severin

On 16/01/2019 16:06, Andreas Tille wrote:

Hi again,

since #918567 is RC critical there is some urgency to get this fixed.
If I do not hear from you until Saturday I will assume you are fine
with dlib in Debian Science team maintenance.

Kind regards

Andreas.

On Tue, Jan 15, 2019 at 11:36:14AM +0100, Andreas Tille wrote:

Hi Séverin,

I stumbled upon dlib since I maintain some rdepends (plastimatch) of
this lib and due to #918567 I've got a warning about testing removal.
Since machine learning is definitely a topic that is covered by
Debian Science I'd consider it really appropriate to maintain this
software inside the Debian Science team, which means the repository
would be moved to

 https://salsa.debian.org/science-team/dlib

and the maintainer would be set to

 Debian Science Maintainers 


while your ID would be added as Uploader.  Would this course of action
be OK for you?

Kind regards

Andreas.

--
http://fam-tille.de

Bug#919527: Missing dependency against python3-distutils

[Laurent Bigonville]

Package: virtinst
Version: 1:2.0.0-2
Severity: serious

Hi,

The regression tests are currently failing because the virtinst is
missing a dependency against python3-distutils:

autopkgtest [04:39:33]: test help.sh:  - - - - - - - - - - stderr - - - - - - - 
- - -
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-convert", line 19, in 
from virtconv import VirtConverter
  File "/usr/share/virt-manager/virtconv/__init__.py", line 10, in 
from virtconv.formats import VirtConverter
  File "/usr/share/virt-manager/virtconv/formats.py", line 10, in 
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils.spawn'

https://ci.debian.net/data/autopkgtest/testing/amd64/v/virt-manager/1712093/log.gz

Could you please add the needed dependency?

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages virtinst depends on:
ii  e2fsprogs 1.44.5-1
ii  genisoimage   9:1.1.11-3+b2
ii  gir1.2-libosinfo-1.0  1.2.0-1
ii  python3   3.7.1-3
ii  python3-gi3.30.4-1
ii  python3-libvirt   4.10.0-1
ii  python3-libxml2   2.9.4+dfsg1-7+b3
ii  python3-requests  2.20.0-2

Versions of packages virtinst recommends:
ii  qemu-utils   1:3.1+dfsg-2+b1
ii  virt-viewer  7.0-1

virtinst suggests no packages.

-- no debconf information

Processed: fixed 918628 in 2.0.0-4

[Debian Bug Tracking System]

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

> fixed 918628 2.0.0-4
Bug #918628 {Done: Xavier } [src:node-stream-splicer] 
node-stream-splicer FTBFS with nodejs 10.15.0
Marked as fixed in versions node-stream-splicer/2.0.0-4.
> thanks
Stopping processing here.

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

Bug#919524: node-groove: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance()')

[Santiago Vila]

Package: src:node-groove
Version: 2.5.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
node-gyp configure build
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@10.15.0 | linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/usr/share/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/<>/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/share/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/include/nodejs/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/usr/include/nodejs',
gyp info spawn args   '-Dnode_gyp_dir=/usr/share/node-gyp',
gyp info spawn args   
'-Dnode_lib_file=/usr/include/nodejs/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/<>',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[2]: Entering directory '/<>/build'
  CXX(target) Release/obj.target/groove/src/groove.o
In file included from ../src/groove.cc:2:
../../../../usr/lib/nodejs/nan/nan.h: In function 'void 
Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
../../../../usr/lib/nodejs/nan/nan.h:2232:62: warning: cast between 
incompatible function types from 'void (*)(uv_work_t*)' {aka 'void 
(*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} 
[-Wcast-function-type]
 , reinterpret_cast(AsyncExecuteComplete)
  ^
../src/groove.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE 
SetLogging(Nan::NAN_METHOD_ARGS_TYPE)':
../src/groove.cc:21:45: warning: 'double v8::Value::NumberValue() const' is 
deprecated: Use maybe version [-Wdeprecated-declarations]
 groove_set_logging(info[0]->NumberValue());
 ^
In file included from /usr/include/nodejs/deps/v8/include/v8.h:26,
 from /usr/include/nodejs/src/node.h:63,
 from ../src/groove.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:2475:45: note: declared here
   V8_DEPRECATED("Use maybe version", double NumberValue() const);
 ^~~
/usr/include/nodejs/deps/v8/include/v8config.h:324:3: note: in definition of 
macro 'V8_DEPRECATED'
   declarator __attribute__((deprecated(message)))
   ^~
In file included from ../src/groove.cc:1:
../src/groove.cc: At global scope:
/usr/include/nodejs/src/node.h:570:43: warning: cast between incompatible 
function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka 
'void (*)(v8::Local)'} to 'node::addon_register_func' {aka 'void 
(*)(v8::Local, v8::Local, void*)'} [-Wcast-function-type]
   (node::addon_register_func) (regfunc),  \
   ^
/usr/include/nodejs/src/node.h:604:3: note: in expansion of macro 
'NODE_MODULE_X'
   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
   ^
../src/groove.cc:101:1: note: in expansion of macro 'NODE_MODULE'
 NODE_MODULE(groove, Initialize)
 ^~~
In file included from /usr/include/nodejs/src/node.h:63,
 from ../src/groove.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nodejs/src/node_object_wrap.h:85:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between 
incompatible function types from 
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nan_object_wrap.h:66:61:   

Bug#919523: libmodule-install-readmefrompod-perl: FTBFS in sid (failing tests)

[Santiago Vila]

Package: src:libmodule-install-readmefrompod-perl
Version: 0.30-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
I can run 'make' good
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Module::Install::ReadmeFromPod
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cp lib/Module/Install/ReadmeFromPod.pm blib/lib/Module/Install/ReadmeFromPod.pm
Manifying 1 pod document
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 
'blib/arch')" t/*.t
# Testing Module::Install::ReadmeFromPod 0.30, Perl 5.028001, /usr/bin/perl
t/00_compile.t ... 
1..1
ok 1 - use Module::Install::ReadmeFromPod;
ok
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# include /<>/dist/pOKZQrzH2U/inc/Module/Install.pm
# include inc/Module/Install/Metadata.pm
# include inc/Module/Install/Base.pm
# include inc/Module/Install/ReadmeFromPod.pm
# readme_from README.pm to txt
# readme_from README.pm to htm
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# readme_from README.pm to man
# readme_from README.pm to md
# include inc/Module/Install/WriteAll.pm
# include inc/Module/Install/Makefile.pm
# include inc/Module/Install/Win32.pm
# include inc/Module/Install/Can.pm
# include inc/Module/Install/Fetch.pm
# Generating a Unix-style Makefile
# Writing Makefile for Foo::Bar
# Writing MYMETA.yml and MYMETA.json
# Writing META.yml
# make[2]: Entering directory '/<>/dist/pOKZQrzH2U'
# rm -f \
#   Bar.bso Bar.def \
#   Bar.exp Bar.x \
#blib/arch/auto/Foo/Bar/extralibs.all \
#   blib/arch/auto/Foo/Bar/extralibs.ld Makefile.aperl \
#   *.a *.o \
#   *perl.core MYMETA.json \
#   MYMETA.yml blibdirs.ts \
#   core core.*perl.*.? \
#   core.[0-9] core.[0-9][0-9] \
#   core.[0-9][0-9][0-9] core.[0-9][0-9][0-9][0-9] \
#   core.[0-9][0-9][0-9][0-9][0-9] libBar.def \
#   mon.out perl \
#   perl perl.exe \
#   perlmain.c pm_to_blib \
#   pm_to_blib.ts so_locations \
#   tmon.out 
# rm -rf \
#   blib 
# mv Makefile Makefile.old > /dev/null 2>&1
# rm -f \
#   Makefile Makefile.old 
# rm -rf \
#   Foo-Bar-0.01 MYMETA.yml 
# rm -f Foo-Bar-0.01.tar.gz
# rm -f MANIFEST.bak _build
# "/usr/bin/perl" "-Iinc" "-Ilib" "-MModule::Install::Admin" -e "remove_meta()"
# rm -rf inc
# "/usr/bin/perl" "-Iinc" "-MExtUtils::Manifest=fullcheck" -e fullcheck
# Problem opening MANIFEST: No such file or directory at 
/usr/share/perl/5.28/ExtUtils/Manifest.pm line 349.
# Problem opening MANIFEST: No such file or directory at 
/usr/share/perl/5.28/ExtUtils/Manifest.pm line 349.
# Not in MANIFEST: Makefile.PL
# Not in MANIFEST: README
# Not in MANIFEST: README.1
# Not in MANIFEST: README.htm
# Not in MANIFEST: README.md
# Not in MANIFEST: README.pm
# make[2]: Leaving directory '/<>/dist/pOKZQrzH2U'
t/01_dist.t .. 
1..13
ok 1 - Exists: 'inc/Module/Install/ReadmeFromPod.pm'
ok 2 - There is a README file
ok 3 - There is a README.htm file
ok 4 - There is a README.md file
ok 5 - There is a README.1 file
ok 6 - README contains only unix newlines
ok 7 - README.htm contains only unix newlines
ok 8 - README.md contains only unix newlines
ok 9 - README.1 contains only unix newlines
ok 10 - There is a README file
ok 11 - There is a README.htm file
ok 12 - There is a README.md file
ok 13 - There is a README.1 file
ok
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# include /<>/dist/rxpKpJcKFL/inc/Module/Install.pm
# include inc/Module/Install/Metadata.pm
# include inc/Module/Install/Base.pm
# include inc/Module/Install/ReadmeFromPod.pm
# readme_from README.pm to text
# include inc/Module/Install/Makefile.pm
# readme_from README.pm to html
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# Subroutine Module::Install::ReadmeFromPod::io redefined at 
/usr/share/perl5/IO/All/Base.pm line 24.
# readme_from README.pm to md
# readme_from README.pm to man
# include inc/Module/Install/WriteAll.pm
# include 

Bug#918628: marked as done (node-stream-splicer FTBFS with nodejs 10.15.0)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 22:41:48 +0100
with message-id 
and subject line Already fixed
has caused the Debian Bug report #918628,
regarding node-stream-splicer FTBFS with nodejs 10.15.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.)


-- 
918628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-stream-splicer
Version: 2.0.0-3
Severity: serious
Tags: ftbfs

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

...
  76 passing (3m)
  3 failing

  1) test/nested.js should be equivalent:
 Error: should be equivalent
  at Error: should be equivalent
  at at Test.assert [as _assert] 
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at at Test.tapeDeepEqual (/usr/lib/nodejs/tape/lib/test.js:432:10)
  at at Test.bound [as deepEqual] 
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at at test/nested.js:29:11
  at at ConcatStream. 
(/usr/lib/nodejs/concat-stream/index.js:37:43)
  at at finishMaybe (_stream_writable.js:641:14)
  at at endWritable (_stream_writable.js:649:3)
  at at ConcatStream.Writable.end (_stream_writable.js:589:5)

  2) test/nested_middle.js should be equivalent:
 Error: should be equivalent
  at Error: should be equivalent
  at at Test.assert [as _assert] 
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at at Test.tapeDeepEqual (/usr/lib/nodejs/tape/lib/test.js:432:10)
  at at Test.bound [as deepEqual] 
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at at test/nested_middle.js:35:11
  at at ConcatStream. 
(/usr/lib/nodejs/concat-stream/index.js:37:43)
  at at finishMaybe (_stream_writable.js:641:14)
  at at endWritable (_stream_writable.js:649:3)
  at at ConcatStream.Writable.end (_stream_writable.js:589:5)

  3) test/pop.js should be equivalent:
 Error: should be equivalent
  at Error: should be equivalent
  at at Test.assert [as _assert] 
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at at Test.tapeDeepEqual (/usr/lib/nodejs/tape/lib/test.js:432:10)
  at at Test.bound [as deepEqual] 
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at at test/pop.js:38:11
  at at ConcatStream. 
(/usr/lib/nodejs/concat-stream/index.js:37:43)
  at at finishMaybe (_stream_writable.js:641:14)
  at at endWritable (_stream_writable.js:649:3)
  at at ConcatStream.Writable.end (_stream_writable.js:589:5)

make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.0.0-4

Already fixed in version 2.0.0-4--- End Message ---

Bug#916807: marked as done (haskell-mode: FTBFS with Emacs 26.1: tests fail)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 21:34:37 +
with message-id 
and subject line Bug#916807: fixed in haskell-mode 16.1-6
has caused the Debian Bug report #916807,
regarding haskell-mode: FTBFS with Emacs 26.1: tests fail
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.)


-- 
916807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-mode
Version: 0.4-1
Severity: important
User: debian-emac...@lists.debian.org
Usertags: emacs26-ftbfs
Tags: ftbfs

Dear maintainer,

This package fails to build against Emacs 26.1, currently in
experimental.  It does not fail against Emacs 25.2, currently in sid.
Full log attached.

Ran 513 tests, 509 results as expected, 4 unexpected (2018-12-18 13:48:40+)
123 expected failures

4 unexpected results:
   FAILED  haskell-cabal-compute-checksum-1
   FAILED  haskell-cabal-compute-next-prev-section-1
   FAILED  haskell-cabal-enum-targets-1
   FAILED  haskell-cabal-get-field-1

This bug will likely become RC before the upcoming transitions freeze,
as we expect to ship Emacs 26.1 in buster.

-- 
Sean Whitton


haskell-mode_i386-2018-12-18T13:47:24Z.build
Description: Binary data


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: haskell-mode
Source-Version: 16.1-6

We believe that the bug you reported is fixed in the latest version of
haskell-mode, 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.
Thomas Koch  (supplier of updated haskell-mode 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: Wed, 16 Jan 2019 19:39:52 +
Source: haskell-mode
Binary: elpa-haskell-mode haskell-mode
Architecture: source all
Version: 16.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Thomas Koch 
Description:
 elpa-haskell-mode - major mode for editing Haskell in Emacs
 haskell-mode - transitional package
Closes: 916807
Changes:
 haskell-mode (16.1-6) unstable; urgency=medium
 .
   * revert errounous change of upstream files in packaging branch
   * fix failing tests for emacs 26.1 (Closes: 916807)
Checksums-Sha1:
 dab91838e8d1b16783696ca1b38e27186eac6d2a 2163 haskell-mode_16.1-6.dsc
 a79e405b004191af9717cd54ebbd0fef5e54f25a 6800 haskell-mode_16.1-6.debian.tar.xz
 4310f88a180509064bc473cf691c566e57efdc79 181252 
elpa-haskell-mode_16.1-6_all.deb
 f5e482ba322c6b057cf53a3b8eb2cf273b160df9 5896 haskell-mode_16.1-6_all.deb
 bb79970e1ca99448bb69a94badfb2248db931cad 8106 
haskell-mode_16.1-6_amd64.buildinfo
Checksums-Sha256:
 a7065fd436c575329c57f43431bc7e86084ea6fe084c4aa1d048037f940031e2 2163 
haskell-mode_16.1-6.dsc
 2fd83fc644ce8e072f11bdf5942e6e9baf5cd10a4df63b2ad0a9b93429200238 6800 
haskell-mode_16.1-6.debian.tar.xz
 a154a68bc68b824e15e8240410828a0e062cdac4c046db345596983f14147242 181252 
elpa-haskell-mode_16.1-6_all.deb
 e569addc95b6432a8f48f961e9e1c9014dc82359d9d0c156f2e3e97986464ecf 5896 
haskell-mode_16.1-6_all.deb
 f17abc7d63238ee2c18417394846c7d8292ca1db945f7d1277a7f88553e21a29 8106 
haskell-mode_16.1-6_amd64.buildinfo
Files:
 c3b3d96bc8c9d94f3d7be4ea2145bddc 2163 lisp optional haskell-mode_16.1-6.dsc
 ad1d8288caf792a2467f5b0f3abb1171 6800 lisp optional 
haskell-mode_16.1-6.debian.tar.xz
 c59de2984c2f6c351dcef2dad183852c 181252 lisp optional 
elpa-haskell-mode_16.1-6_all.deb
 c3cf9ef9e56352c49640838a2d059a14 5896 oldlibs optional 
haskell-mode_16.1-6_all.deb
 2c3183984ac308103a8684d8c4f69543 8106 lisp optional 
haskell-mode_16.1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdgQCBVl/ppbxMTvKB/xIkQQrploFAlw/nJYACgkQB/xIkQQr
plpeXA//bTNJ0dbVyA2ih15zIlQS5Eivi7L1OCBvW2adMgRJw0Oc8Z57hR+MzldC
2+/qswJsXbU8j7Jm3LPBFEbl4x9QjTVAWxcg3fnBnkDujYY20rfVX6CkTgZ0Rose
VOOnmQAp8ApN+WJQoZIqinIwAGDIz356+M1XnwIKzV2jgbO5YgAkzSxmIDKwSxU0
JnD2XvY89Sqna2k2OIHxjfbjgNpejuvNOH+OBz3mWbO3wTsvQ+JBVsFSoEPjA2da
5AoDvdxkQv8ROt7/fETed/y4MQwwgHuBD5R3cy4NM2k/TLSpA3rHlMpzzrGyz1CQ
Ob7h2IcOEHcr48XETF+S5Bbf/LTVnPMvOt4oaPjBn4F1e114DIb9LzRD2nIgK0lk

Bug#919192: marked as done (node-opencv: FTBFS in sid (no matching function for call to 'v8::Function::NewInstance(int, v8::Local [3])'))

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 21:20:11 +
with message-id 
and subject line Bug#919192: fixed in node-opencv 6.0.0+git20180416.cfc96ba0-1
has caused the Debian Bug report #919192,
regarding node-opencv: FTBFS in sid (no matching function for call to 
'v8::Function::NewInstance(int, v8::Local [3])')
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.)


-- 
919192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-opencv
Version: 6.0.0-2
Severity: serious
Tags: ftbfs

Hello Mattia.

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


[...]
 debian/rules build-arch
dh build-arch --with nodejs
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
find /<> -name '*.xml' -exec chmod a-x {} \;
find /<> -name '*.html' -exec chmod a-x {} \;
find /<> -name '*.gyp' -exec chmod a-x {} \;
find /<> -name '*.md' -exec chmod a-x {} \;
find /<> -name '*.png' -exec chmod a-x {} \;
find /<> -name '*.jpg' -exec chmod a-x {} \;
find /<> -name '*.h' -exec chmod a-x {} \;
chmod a-x examples/make-example-files.sh

[... snipped ...]

../src/Matrix.cc:2633:69: warning: 'v8::Local v8::Value::ToObject() 
const' is deprecated: Use maybe version [-Wdeprecated-declarations]
   Matrix *other = Nan::ObjectWrap::Unwrap(info[0]->ToObject());
 ^
In file included from ../src/OpenCV.h:14,
 from ../src/Contours.h:1,
 from ../src/Matrix.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:10046:15: note: declared here
 Local Value::ToObject() const {
   ^
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nodejs/src/node_object_wrap.h:85:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between 
incompatible function types from 
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nan_object_wrap.h:66:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between 
incompatible function types from 
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
make[2]: *** [opencv.target.mk:122: Release/obj.target/opencv/src/Matrix.o] 
Error 1
make[2]: Leaving directory '/<>/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit 
(/usr/share/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit 
(internal/child_process.js:240:12)
gyp ERR! System Linux 4.9.0-8-amd64
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "build" 
"--module=/<>/build/opencv/v6.0.0/Release/node-v64-linux-x64/opencv.node"
 "--module_name=opencv" 
"--module_path=/<>/build/opencv/v6.0.0/Release/node-v64-linux-x64" 
"--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /<>
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp build 
--module=/<>/build/opencv/v6.0.0/Release/node-v64-linux-x64/opencv.node
 --module_name=opencv 
--module_path=/<>/build/opencv/v6.0.0/Release/node-v64-linux-x64 
--napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack at ChildProcess. 
(/usr/lib/nodejs/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:962:16)
node-pre-gyp ERR! stack at 

Bug#911878: closing 911878

[Laurent Bigonville]

close 911878 
thanks

Hello,

The package is now building fine on all release architectures

Closing

Processed: closing 911878

[Debian Bug Tracking System]

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

> close 911878
Bug #911878 [src:libosinfo] libosinfo FTBFS: tests fail: 
ERROR:test-isodetect.c:406:test_one: assertion failed (shortid == 
info->shortid): ("win10" == "win8")
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Bug #919192 in node-opencv marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919192 [src:node-opencv] node-opencv: FTBFS in sid (no matching function 
for call to 'v8::Function::NewInstance(int, v8::Local [3])')
Added tag(s) pending.

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

Bug#919192: Bug #919192 in node-opencv marked as pending

[Ying-Chun Liu]

Control: tag -1 pending

Hello,

Bug #919192 in node-opencv 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/js-team/node-opencv/commit/1dc7bad3ac35ea9cafce6219ce10c74dbd3c7695


Import Debian changes 6.0.0+git20180416.cfc96ba0-1

node-opencv (6.0.0+git20180416.cfc96ba0-1) unstable; urgency=low

  * Use upstream git repo.
- Support node 10 (Closes: #919192)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919192

Processed: merge 919219 and 919235

[Debian Bug Tracking System]

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

> severity 919219 serious
Bug #919219 [abcm2ps] abcm2ps: fails to build from scratch because debhelper 
detects the ninja build system
Severity set to 'serious' from 'important'
> merge 919219 919235
Bug #919219 [abcm2ps] abcm2ps: fails to build from scratch because debhelper 
detects the ninja build system
Bug #919235 [abcm2ps] abcm2ps: FTBFS because debhelper uses ninja build system 
instead of autoconf
Merged 919219 919235
> thanks
Stopping processing here.

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

Bug#906215: marked as done (foolscap autopkgtest needs update for new version of twisted)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 20:48:37 +
with message-id 
and subject line Bug#906215: fixed in foolscap 0.13.1-2
has caused the Debian Bug report #906215,
regarding foolscap autopkgtest needs update for new version of twisted
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.)


-- 
906215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foolscap
Version: 0.13.1-1
X-Debbugs-CC: debian...@lists.debian.org, twis...@packages.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:twisted

Dear maintainers,

With a recent upload of twisted the autpkgtest of foolscap started to
fail in testing. I copied the output below.

Currently this regression is contributing to the delay of the migration
of twisted to testing [1]. Could you please investigate the situation?
Looking at the error message, there doesn't seem to be a real issue
other than that the reference needs updating to the new output, but of
course I could be wrong.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/f/foolscap/819833/log.gz

===
[SKIPPED]
new-style classes still broken

foolscap.test.test_banana.ThereAndBackAgain.test_boundMethod_newstyle
foolscap.test.test_banana.ThereAndBackAgain.test_classMethod_newstyle
foolscap.test.test_banana.ThereAndBackAgain.test_class_newstyle
foolscap.test.test_banana.ThereAndBackAgain.test_instance_newstyle
===
[FAIL]
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py",
line 1418, in _inlineCallbacks
result = g.send(result)
  File "/usr/lib/python2.7/dist-packages/foolscap/test/test_info.py",
line 151, in testListener
% self._portnum)
  File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py",
line 432, in assertEqual
super(_Assertions, self).assertEqual(first, second, msg)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
twisted.trial.unittest.FailTest: "Listener on IPv4Address(type='TCP',
host='127.0.0.1', port=40243)" != "Listener on IPv4Address(TCP,
'127.0.0.1', 40243)"

foolscap.test.test_info.Connect.testListener



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: foolscap
Source-Version: 0.13.1-2

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated foolscap 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, 13 Feb 2018 10:16:15 +0100
Source: foolscap
Binary: python-foolscap
Architecture: source
Version: 0.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-foolscap - object-capability-based RPC system for Twisted Python
Closes: 906215 911271
Changes:
 foolscap (0.13.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * Convert git repository from git-dpm to gbp layout
 .
   [ Julian Taylor ]
   * skip-broken-test.patch: skip a probably broken test
   * twisted-18.7-compat.patch: adapt test to new twisted output
 Thanks to Balint Reczey for the patches, Closes: #906215
   * Remove the optional dependency on txtorcon as it does not provide a
 python2 package anymore, Closes: #911271

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Different55]

Alright, not entirely sure if I did this right but I followed Debian's Building 
Tutorial to download and build wpa_supplicant with the changes you linked. One 
exception, I use wpa_supplicant through NetworkManager and could not work out 
where I needed to create a wpa_supplicant.conf, so I changed the one line in 
config.c to:

{ INT(no_oper_classes_ie), 1 },

which I'm hoping makes the default "on" instead of "off." Sadly doesn't appear 
to have made a difference, although it didn't make anything worse either.

Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my 
desktop this morning and had the same problems with a Qualcomm Atheros AR9462 
Wireless Adapter.

On Tuesday, January 15, 2019 11:53 AM, Ben Greear  
wrote:

> You might try adding this patch and disabling the oper-class IE:
>
> http://lists.infradead.org/pipermail/hostap/2018-August/038792.html
>
> I'd be curious to know if it fixes the problem.
>
> Thanks,
> Ben
>
> On 1/14/19 4:35 PM, Different55 wrote:
>
> > On Monday, January 14, 2019 10:37 AM, Ben Greear gree...@candelatech.com 
> > wrote:
> >
> > > What is the model number of your home AP?
> > > Thanks,
> > > Ben
> >
> > It is a Comtrend VR-3033
>
> --
>
> Ben Greear gree...@candelatech.com
> Candela Technologies Inc http://www.candelatech.com

Bug#911271: marked as done (foolscap: (Build) Depends on non existing python-txtorcon)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 20:48:38 +
with message-id 
and subject line Bug#911271: fixed in foolscap 0.13.1-2
has caused the Debian Bug report #911271,
regarding foolscap: (Build) Depends on non existing python-txtorcon
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.)


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

txtorcon does not build the Python2 variant (python-txtorcon) since its
last upload, only the python3 one (python3-txtorcon) remains.

As of now the package can't be built due to missing packages.

Sebastian
--- End Message ---
--- Begin Message ---
Source: foolscap
Source-Version: 0.13.1-2

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated foolscap 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, 13 Feb 2018 10:16:15 +0100
Source: foolscap
Binary: python-foolscap
Architecture: source
Version: 0.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-foolscap - object-capability-based RPC system for Twisted Python
Closes: 906215 911271
Changes:
 foolscap (0.13.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
   * Convert git repository from git-dpm to gbp layout
 .
   [ Julian Taylor ]
   * skip-broken-test.patch: skip a probably broken test
   * twisted-18.7-compat.patch: adapt test to new twisted output
 Thanks to Balint Reczey for the patches, Closes: #906215
   * Remove the optional dependency on txtorcon as it does not provide a
 python2 package anymore, Closes: #911271
Checksums-Sha1:
 593afe58083a5f214e61819878071aec789fbb7a 2319 foolscap_0.13.1-2.dsc
 44c4fe1132d122160d88d5efff5fbb8e9739ce83 8104 foolscap_0.13.1-2.debian.tar.xz
 715226b3e9880c8c43c3cb16f2962a109da4fe93 5274 
foolscap_0.13.1-2_source.buildinfo
Checksums-Sha256:
 838d3d5a2957af0823386d6c75e971b66a4a4e12292aecc79c19af8f6acc38d2 2319 
foolscap_0.13.1-2.dsc
 6a87de738bdf889840d38f1155b806f64a3f9cb905305c240484cc14af8b8cfe 8104 
foolscap_0.13.1-2.debian.tar.xz
 0ea1fc2c5bf88635d02a058e0361db6d1e73cfd6bf6ebf1b251f9849372dfbcb 5274 
foolscap_0.13.1-2_source.buildinfo
Files:
 737abc8aa9512c4b767945e4c85cd006 2319 python optional foolscap_0.13.1-2.dsc
 10be4b96a3c724a3d669500d0f167a6d 8104 python optional 
foolscap_0.13.1-2.debian.tar.xz
 fcf7ba273bb4c98a1d13792f07001b2d 5274 python optional 
foolscap_0.13.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEi3e6SDkbPOUcIpUxMsxKrAKHVv8FAlw/kR4ACgkQMsxKrAKH
Vv8FzxAAuOns5ZZDsIg20wEucZKllpvf2Vi2A/L3x0Y+BE1ZboJ3HmmasN8z4dDw
mZicJT1v49QFldt5FpoD6sxOx2LOjIvAI8tZt2++3za7EeoMYYawv+tmCnG3hTaB
TqdsVInON9Cq7hSQlENTPFCjIkgiLm/sH8IltbLK35gSStUyEyOrurkclWDUhjvN
NagPo+DpAXUqJYRw0s3uqGO6zoCUsiaJEAZxvFTirzgQSBQeQIVuN95qU5n7eID+
dpXLj0OrTBfJvVE53RP00FiizhNatIOqoKVkQQm6BTBeNxnJl9CQ84jkzIZVHob3
ZNky3zJKSgWsMKBftGG67B5oYuKDDKAJTEAq3IXsvZGZCOdZMV/eej+qYivK/TR7
nywd6HBmnRFnWVpB4hHtbsuRF9+yhihvXegEXmFG5ewVCRa2ytKkkvb0l1yNF8/a
uPvX5cQ/c8Ovn0OcY//Eq1vKuO9Blv/kP/2eA2MPSH9pOMM9/jTy0lhH0RqvWVU8
8+YPRn8F/COFEjF5+lfj9pErbQ6NEVzcQtd2SLjRCI4Qp03EX3aj/YwtIA/B+D8i
5UJpIVDV4dIlZLGGab6Ta88bfVblh+Ya7f76h2eCkSW1fS6LdXj06097Q/ebKMw7
yt0HM07sVMsvuonJN5KMKjBjyABHAtOVVSO5toD0tvrjmAV5L1I=
=5hr5
-END PGP SIGNATURE End Message ---

Bug#919516: ruby2.5 ftbfs in testing/unstable: certificate verify failed (certificate has expired)

[Matthias Klose]

Package: src:ruby2.5
Version: 2.5.3-3
Severity: serious
Tags: sid buster

[...]
 13) Error:
TestNetHTTPS#test_get:
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate
verify failed (certificate has expired)
/home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in 
`connect_nonblock'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in 
`ssl_socket_connect'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:981:in `connect'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:920:in `do_start'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:909:in `start'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1455:in `request'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1365:in `request_get'
/home/packages/tmp/ruby2.5-2.5.3/test/net/http/test_https.rb:44:in 
`test_get'

 14) Error:
TestNetHTTPS#test_post:
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate
verify failed (certificate has expired)
/home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in 
`connect_nonblock'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in 
`ssl_socket_connect'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:981:in `connect'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:920:in `do_start'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:909:in `start'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1455:in `request'
/home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1409:in `request_post'
/home/packages/tmp/ruby2.5-2.5.3/test/net/http/test_https.rb:58:in 
`test_post'

Finished tests in 289.841475s, 59.8914 tests/s, 7810.6041 assertions/s.
17359 tests, 2263837 assertions, 5 failures, 9 errors, 19 skips

ruby -v: ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux-gnu]
make[2]: *** [uncommon.mk:698: yes-test-almost] Error 14
make[2]: Leaving directory '/home/packages/tmp/ruby2.5-2.5.3'
make[1]: *** [debian/rules:81: override_dh_auto_test-arch] Error 2
make[1]: Leaving directory '/home/packages/tmp/ruby2.5-2.5.3'
make: *** [debian/rules:59: build] Error 2

Processed: found 919513 in 1.1.2+dfsg1-6

[Debian Bug Tracking System]

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

> found 919513 1.1.2+dfsg1-6
Bug #919513 [src:ntpsec] CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445
Marked as found in versions ntpsec/1.1.2+dfsg1-6.
> thanks
Stopping processing here.

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

Bug#917199: marked as done (pyside2 should build without patchelf also on mips+mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 19:34:51 +
with message-id 
and subject line Bug#917199: fixed in pyside2 5.11.2-3
has caused the Debian Bug report #917199,
regarding pyside2 should build without patchelf also on mips+mipsel
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.)


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

Package: pivy
Version: 0.6.4-1
Severity: serious

pivy cannot be built on mips/mipsel because of a depedency on pyside2 which is 
not built on mips/mipsel pyside2 is not being built on those architectures due 
to a dependency on patchelf. patchelf is not currently building on mips* due to 
a testsuite failure.

mips64el also looks like it will become a problem going forward as patchelf is 
not currently available there (but was at the time pyside2 was last built).

Possible solutions (in roughly descending order of preference):

1. Fix the patchelf testsuite failures.
2. Break the dependency chain (only possible if the functionality in question 
is optional, I have not researched that).
3. Request removal of the mips* binaries for pivy and reverse dependencies of 
pivy (if-any).
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.11.2-3

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated pyside2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Jan 2019 16:30:16 +0100
Source: pyside2
Binary: python-pyside2-doc libpyside2-5.11 libpyside2-py3-5.11 libpyside2-dev 
python-pyside2.qtcore python3-pyside2.qtcore shiboken2 libshiboken2-5.11 
libshiboken2-py3-5.11 libshiboken2-dev shiboken2-doc pyside2-tools 
python-pyside2uic python3-pyside2uic python-pyside2.qtwidgets 
python3-pyside2.qtwidgets python-pyside2.qt3drender python3-pyside2.qt3drender 
python-pyside2.qtquick python3-pyside2.qtquick python-pyside2.qtpositioning 
python3-pyside2.qtpositioning python-pyside2.qtx11extras 
python3-pyside2.qtx11extras python-pyside2.qtqml python3-pyside2.qtqml 
python-pyside2.qtwebenginecore python3-pyside2.qtwebenginecore 
python-pyside2.qttexttospeech python3-pyside2.qttexttospeech 
python-pyside2.qthelp python3-pyside2.qthelp python-pyside2.qtscripttools 
python3-pyside2.qtscripttools python-pyside2.qtnetwork 
python3-pyside2.qtnetwork python-pyside2.qtmultimediawidgets 
python3-pyside2.qtmultimediawidgets python-pyside2.qtlocation 
python3-pyside2.qtlocation
 python-pyside2.qt3dlogic python3-pyside2.qt3dlogic python-pyside2.qtsensors 
python3-pyside2.qtsensors python-pyside2.qtmultimedia 
python3-pyside2.qtmultimedia python-pyside2.qtscript python3-pyside2.qtscript 
python-pyside2.qtwebchannel python3-pyside2.qtwebchannel 
python-pyside2.qtprintsupport python3-pyside2.qtprintsupport 
python-pyside2.qtquickwidgets python3-pyside2.qtquickwidgets 
python-pyside2.qt3dinput python3-pyside2.qt3dinput python-pyside2.qtxml 
python3-pyside2.qtxml python-pyside2.qttest python3-pyside2.qttest 
python-pyside2.qtwebenginewidgets python3-pyside2.qtwebenginewidgets 
python-pyside2.qtconcurrent python3-pyside2.qtconcurrent 
python-pyside2.qtxmlpatterns python3-pyside2.qtxmlpatterns 
python-pyside2.qtcharts python3-pyside2.qtcharts python-pyside2.qtuitools 
python3-pyside2.qtuitools python-pyside2.qtopengl python3-pyside2.qtopengl 
python-pyside2.qt3dcore python3-pyside2.qt3dcore python-pyside2.qtsql 
python3-pyside2.qtsql python-pyside2.qtgui
 python3-pyside2.qtgui python-pyside2.qtsvg python3-pyside2.qtsvg 
python-pyside2.qtwebsockets
 python3-pyside2.qtwebsockets
Architecture: source
Version: 5.11.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Sebastien Delafond 
Description:
 libpyside2-5.11 - Python 2 bindings for Qt5 (base files)
 libpyside2-dev - Python bindings for Qt5 (development files)
 libpyside2-py3-5.11 - Python 3 bindings for Qt5 (base files)
 libshiboken2-5.11 - CPython 

Bug#919513: CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445

[Richard Laager]

Thanks for letting me know. I was planning to package 1.1.3 in the next couple 
of days, but I was not aware there were CVEs fixed in this release. I will try 
to do a package release today.

-- 
Richard

> On Jan 16, 2019, at 13:21, Moritz Muehlenhoff  wrote:
> 
> Source: ntpsec
> Severity: grave
> Tags: security
> 
> Please see
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6442
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6443
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6444
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6445
> 
> Cheers,
>Moritz

Bug#919513: CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445

[Moritz Muehlenhoff]

Source: ntpsec
Severity: grave
Tags: security

Please see
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6442
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6443
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6444
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6445

Cheers,
Moritz

Bug#919213: marked as done (irqbalance: endless loop during configure, system reaches maximum of open files)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 20:10:53 +0100
with message-id <20190116191051.gu10...@sym.noone.org>
and subject line Re: irqbalance: endless loop during configure, system reaches 
maximum of open files
has caused the Debian Bug report #919213,
regarding irqbalance: endless loop during configure, system reaches maximum of 
open files
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.)


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

On one of my systems (not the one I'm writing the report on), a
Raspberry Pi 2 with Debian Sid armhf and sysvinit, the terminal which I
ran the upgrade in, looked like this (excerpt):

Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults
Executing /usr/sbin/update-rc.d irqbalance enable
Synchronizing state for irqbalance.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d irqbalance defaults

htop looked like this (excerpt):

 root   20   0  179M  1576  1404 S  0.3  0.2  3:10.99 | +- aptitude -u
 root   20   0 10336 0 0 S  0.0  0.0  0:00.71 |+- dpkg 
--status-fd 70 --configure --pending
 root   20   0 17832   748   140 S  0.0  0.1  0:17.01 ||  +- perl 
-w /usr/share/debconf/frontend /var/lib/dpkg/info/irqbalance.postinst configure 
1.5.0-0.1
 root   20   0  1468 0 0 S  0.0  0.0  0:00.01 ||  |  +- sh 
/var/lib/dpkg/info/irqbalance.postinst configure 1.5.0-0.1
 root   20   0  7136 4 0 S  0.0  0.0  0:00.06 ||  | +- 
perl /usr/sbin/update-rc.d irqbalance enable
 root   20   0  5296 0 0 S  0.0  0.0  0:00.00 ||  |
+- systemctl --quiet enable irqbalance
 root   20   0  7136 4 0 

Processed: severity of 919498 is important

[Debian Bug Tracking System]

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

> severity 919498 important
Bug #919498 [src:linux] linux-image-4.19.0-1-amd64: Fails to boot. Inactive 
(initramfs) prompt.'Gave up waiting for suspend/resume device'
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Andreas Beckmann]

On 2019-01-16 15:28, Alastair McKinstry wrote:
> Matching changes should probably be made for mpich, the other mpi
> alternative.

Done, pushed to branch anbe/alternatives
This time, not even build-tested :-)

I also added the Breaks against the versions predating mpi-$MULTIARCH
including the current version of lam.
See branch anbe/alternatives in both repositories.

> (There is a third MPI alternative in Debian, lam, which also needs work,

... which surprisingly installs without error in a sid chroot with both
libmpich-dev and libopenmpi-dev installed ...

Setting up lam4-dev (7.1.4-3.1) ...
update-alternatives: renaming mpi link from /usr/bin/mpicc to
/usr/include/mpi
update-alternatives: using
/usr/share/man/man3/MPI_Comm_set_name_lam4-dev.3.gz to provide
/usr/share/man/man3/MPI_Comm_set_name.3.gz (MPI_Comm_set_name.3.gz) in
auto mode

But I don't really want to try how quickly I can run into corrupted
alternatives this way, so let's better block it completely. If you think
that this should be fixed in lam for buster, file a RC bug.


Andreas

Bug#918268: bugs-everywhere build depends on monotone that is currently not in buster

[Antoine Beaupre]

On Fri, Jan 04, 2019 at 10:19:17PM +0200, Adrian Bunk wrote:
> Source: bugs-everywhere
> Version: 1.1.1-4
> Severity: serious
> Tags: ftbfs
> Control: block -1 by 888612 889556
> 
> bugs-everywhere build depends on monotone that is currently
> not in buster due to #888612 and #889556.

I'm tempted to let this one go: I'm not using bugs-everywhere (BE) at
all anymore and there are more interesting alternatives (like
git-bug[1] and many others.

BE is mostly abandoned at this point, without any upstream. The
homepage[2] is still up but the upstream git repo refered there is on
gitorious, which died as well recently. There's another repo on
GitLab[3] but that hasn't seen an update in over a year.

So I would suggest just removing this from Debian, unless someone
protests... In fact, I would orphan the package (if not remove it from
unstable) if I was the maintainer instead of just an uploader...

A.

 [1]: https://github.com/MichaelMure/git-bug
 [2]: http://bugseverywhere.org/
 [3]: https://gitlab.com/bugseverywhere/bugseverywhere/

-- 
The value of a college education is not the learning of many facts but
the training of the mind to think.
   - Albert Einstein


signature.asc
Description: PGP signature

Bug#919418: kuttypy: FTBFS in sid (pyuic5: Command not found)

[Georges Khaznadar]

Dear Santiago,

thank you for the bug report. I shall fix it today; besides, the author
has published the first stable version yesterday, so the bug fix will
come with the new release.

Best regards,   Georges.

Santiago Vila a écrit :
> Package: src:kuttypy
> Version: 0.1-1
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in sid but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with python3
>dh_update_autotools_config -i
>dh_autoreconf -i
>dh_auto_configure -i
>dh_auto_build -i
>   make -j1 "INSTALL=install --strip-program=true"
> make[1]: Entering directory '/<>'
> ?. Using QT Version: PyQt5 pyuic5 pyrcc5 pylupdate5 3
> for d in utilities; do make PYUIC=pyuic5 PYRCC=pyrcc5 PYLUPDATE=pylupdate5 
> PY_VERSION=3 -C $d all; done
> make[2]: Entering directory '/<>/utilities'
> for d in templates; do make -C $d all; done
> make[3]: Entering directory '/<>/utilities/templates'
> PYRCC=pyrcc5
> pyuic5 --from-import dio.ui -o ui_dio.py
> make[3]: pyuic5: Command not found
> make[3]: *** [Makefile:26: ui_dio.py] Error 127
> make[3]: Leaving directory '/<>/utilities/templates'
> make[2]: *** [Makefile:6: recursive_all] Error 2
> make[2]: Leaving directory '/<>/utilities'
> make[1]: *** [Makefile:31: recursive_all] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_build: make -j1 "INSTALL=install --strip-program=true" returned exit 
> code 2
> make: *** [debian/rules:4: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 
> 
> The build was made in my autobuilder with "dpkg-buildpackage -A"
> but it also fails here:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kuttypy.html
> 
> If this is really a bug in one of the build-depends, please use reassign and 
> affects,
> so that this is still visible in the BTS web page for this package.
> 
> Thanks.

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#918162: marked as done (Broken with Thunderbird 60)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 18:20:20 +
with message-id 
and subject line Bug#918162: fixed in xul-ext-exteditor 1.0.3-1
has caused the Debian Bug report #918162,
regarding Broken 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.)


-- 
918162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-exteditor
Version: 1.0.2-2
Severity: grave

The plugin is broken with Thunderbird 60 in stretch and sid, after installation
it's disabled and only prints "External Editor is incompatible with Thunderbird 
60.4".

TB 60 was uploaded to stretch over two months ago (and three months ago to 
sid), given
that noone filed a bug so far, it makes me wonder whether this package is used
at all...

Cheers,
  Moritz
  
--- End Message ---
--- Begin Message ---
Source: xul-ext-exteditor
Source-Version: 1.0.3-1

We believe that the bug you reported is fixed in the latest version of
xul-ext-exteditor, 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.
W. Martin Borgert  (supplier of updated xul-ext-exteditor 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Jan 2019 17:59:14 +
Source: xul-ext-exteditor
Binary: xul-ext-exteditor
Architecture: source all
Version: 1.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: W. Martin Borgert 
Description:
 xul-ext-exteditor - edit Icedove messages in an external editor
Closes: 918162
Changes:
 xul-ext-exteditor (1.0.3-1) unstable; urgency=medium
 .
   * New upstream version, compatible with Thunderbird 60 (Closes: #918162)
Checksums-Sha1:
 5981fc1188e1c11796289d3f89f746d8c2c01d5d 2055 xul-ext-exteditor_1.0.3-1.dsc
 3213424d6a7d72a20c487cee845ba60ada6400a5 62800 
xul-ext-exteditor_1.0.3.orig.tar.gz
 25908365e51e792ad00e39499e32d9d3bb635c7f 8008 
xul-ext-exteditor_1.0.3-1.debian.tar.xz
 47768efb973e974bda58b7b8733cf5536fea92da 63616 
xul-ext-exteditor_1.0.3-1_all.deb
 7ab92025b903fb3b358461c8a65db7809cc3c7cd 7091 
xul-ext-exteditor_1.0.3-1_amd64.buildinfo
Checksums-Sha256:
 8360c5e099b9ba513bff3df9b1215d75a4bd296944dd36f2a9762f66483192ac 2055 
xul-ext-exteditor_1.0.3-1.dsc
 3a0e33deef916b21ac8ab7fa6126375c25c06ffd0cb98812a4663b0835bada59 62800 
xul-ext-exteditor_1.0.3.orig.tar.gz
 44b60c8bc031309c153da052f3b1e5c389e8ac49db296f7f05fa0378601e8434 8008 
xul-ext-exteditor_1.0.3-1.debian.tar.xz
 ccc17a3461e9dc32fb72177b44df9bf66b20d524385530deec06e4e084ba9d60 63616 
xul-ext-exteditor_1.0.3-1_all.deb
 aacc1530dc799097318542c9d43e96272080ca24219f85fc03d266b0cb7bfe60 7091 
xul-ext-exteditor_1.0.3-1_amd64.buildinfo
Files:
 5e2e8ccc25766f3846dc756b10bfd4dd 2055 mail optional 
xul-ext-exteditor_1.0.3-1.dsc
 9a41efb920cafaaaef1350d9966fc0f6 62800 mail optional 
xul-ext-exteditor_1.0.3.orig.tar.gz
 ef94c4c1597f83bb4302418252c27d3d 8008 mail optional 
xul-ext-exteditor_1.0.3-1.debian.tar.xz
 ab4119028debd432c14801e8a2766ac1 63616 mail optional 
xul-ext-exteditor_1.0.3-1_all.deb
 f6a81ff784b9f30c6ecd5890e28e4a46 7091 mail optional 
xul-ext-exteditor_1.0.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAlw/cfIACgkQ4+Chwoa5
Y+piIRAAoOeqcfzJt1jsAbEuIDV5QprknEW1qQZTRSEzszxNe2jwBb4AnCa0LWb0
ETf/1MMZ2qKCqfwkAV586CtOorPCE+wB2kqJaUMaa+hP3mxnWaY4LAoMIaWA9Igw
QTM0fh5nNS5qTXyYAFYzvtZJUo1ZGnw9V1FODj5/np9e4Dz5ETQ2wqxZ7xmvzgJg
PpuRJHyD1HK7dvWDE5O75Id23dxKai7RJGzC6gvem6WjjSt/VecEdQ87oIrq5YKw
IGKnk9/4InG4FGg3RA9F7EBMRFiovwM3V7bp+/VqrQ79igxc3HH6krvVolR+BikD
grJDEYUZiwykDXuxH8FoT8rzc+U/x/xZoEJQgrRFJ5sCc3s+jkmWKEYVpujrwybc
L9/iBXI4IawLZbNaibBhfSqAqlqAHQpyO8yauMSbyvzCSwdcHSGG9Uj9e16MFNAq
dlepkG3bXoj62514yJYXGA0DU6cgFCW7GhDVK7ZoLh9tq1+gcleecgePgOA+YauV
X6xlWNQ7exV1gCSloHU9sZ8nUeSi1N+bv5zjDD5q5T8UNDun0sRpZTGSBhBXb5Rz
HpDDte9xjFj+bPAPrhC4Tm8rDhibne9fqvgAtjdCsjjtxG+Op9I4R7MtXP0J5hbK
g+O+qfLUgYn08haZUi8hAm5QR+aJdQVIU7riGJXPkejmNT1CFIU=
=vT64
-END PGP SIGNATURE End Message ---

Bug#919500: golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494)

[Adrian Bunk]

Source: golang-github-grpc-ecosystem-grpc-gateway
Version: 1.6.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=golang-github-grpc-ecosystem-grpc-gateway

...
# github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor
src/github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor/services.go:146:49:
 opts.ResponseBody undefined (type *annotations.HttpRule has no field or method 
ResponseBody)
...

Bug#900447: Build against freerdp2

[Fabián Rodríguez]

Package: src:guacamole-server

Version: 0.9.9-2
Followup-For: Bug #900447

I've asked upstream to clarify if Guacamole v 1.0.0 now supports FreeRDP
v2, last update there was in September:

https://issues.apache.org/jira/browse/GUACAMOLE-249

If not, then I'd agree dropping only RDP would help, at least enabling
publishing a new version in Debian as it's nearing feature/release
freeze in ~1 month.

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Alastair McKinstry]

On 16/01/2019 14:01, Alastair McKinstry wrote:


On 16/01/2019 13:49, Andreas Beckmann wrote:

On 2019-01-16 13:58, Alastair McKinstry wrote:

Hi

Would you happen to know syntax for piuparts to enable an upgrade test
from stretch to a new (local) version?

the command line for the normal stretch2{buster,sid} test can be derived
from corresponding log file, you may have to adjust paths etc.

and then its just these three extra:
--bindmount /tmp/openmpi --testdebs-repo /tmp/openmpi
--distupgrade-to-testdebs

with some set of .debs and a Packages file in /tmp/openmpi (or anywhere
else)

I'm trying to debug and need to see whats failing in the preinst 
script.
So I've a local 3.1.3-10 version with 'set -x' in the scripts, but 
can't

seem to do a stretch-> this upgrade, without putting it in sid or
experimental.

I finally got curious and looked into this last night ... I've
completely overhauled your maintainer scripts and just pushed them to a
branch anbe/alternatives
I hope I understood what your intentions were for the preinst and
reimplemented them in a more readable way. I needed some time to
understand what type of corruption you meant until I found the broken
mpi alternative status file posted by (forgot his name). Because that
code was primarily triggering on "no alternative installed".
I haven't done extensive tests, but it passes the upgrade from 
stretch :-)

Thanks, I'll review them.


Thanks,  this looks good.

I'll upload with these changes.

Matching changes should probably be made for mpich, the other mpi 
alternative.


(There is a third MPI alternative in Debian, lam, which also needs work, 
but i've heard nothing from its maintainer,


and the upstream is dead).



PPPS: all that was missing was a single '|| true'



--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
 believing the innocent had everything to fear, mostly from the guilty but in 
the longer term
 even more from those who say things like “The innocent have nothing to fear.”
 - T. Pratchett, Snuff

Bug#919333: marked as done (schroedinger-coordgenlibs: FTBFS in sid (Can't exec "cmake": No such file or directory))

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 17:36:45 +
with message-id 
and subject line Bug#919333: fixed in schroedinger-coordgenlibs 1.1-2
has caused the Debian Bug report #919333,
regarding schroedinger-coordgenlibs: FTBFS in sid (Can't exec "cmake": No such 
file or directory)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
install -d obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
Can't exec "cmake": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 475.
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. failed to execute: No child 
processes
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 2
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The above build was made in my autobuilder with "dpkg-buildpackage -B"
but it does also fail here:

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: schroedinger-coordgenlibs
Source-Version: 1.1-2

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated 
schroedinger-coordgenlibs 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: Wed, 16 Jan 2019 18:19:12 +0100
Source: schroedinger-coordgenlibs
Binary: libschroedinger-coordgenlibs-dev libschroedinger-coordgenlibs1
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Michael Banck 
Description:
 libschroedinger-coordgenlibs-dev - 2D coordinate generation for chemical 
compounds - header files
 libschroedinger-coordgenlibs1 - 2D coordinate generation for chemical compounds
Closes: 919333
Changes:
 schroedinger-coordgenlibs (1.1-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/control (Build-Depends): Added cmake and libboost-dev (Closes:
 #919333).
Checksums-Sha1:
 f2dc601630642a2a7c6cffbd794e044177595ac1 2255 
schroedinger-coordgenlibs_1.1-2.dsc
 21c44a37c2bfca0dc1f6771f63ce028eeac3427e 3088 
schroedinger-coordgenlibs_1.1-2.debian.tar.xz
 c2a1b595ad2bbea59a0529115644f8f10c5d0313 5628 

Bug#919498: linux-image-4.19.0-1-amd64: Fails to boot. Inactive (initramfs) prompt.'Gave up waiting for suspend/resume device'

[vidal gerard]

Package: src:linux
Version: 4.19.13-1
Severity: critical
Justification: breaks the whole system

System boots properly on kernel 4.18 but fails to boot with any versions
(buster sid) of 4.19.

It seems specific to this DELL computer as another laptop DELL is working
properly with 4.19. i did a complete reinstall of the system on a formatted
partition.
detailed actions already taken
https://www.linuxquestions.org/questions/debian-26/cannot-boot-
kernel-4-4-19-buster-on-dell-precision-tower-5810-4-4-18-ok-4175645718/




-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: Precision Tower 5810
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A29
board_vendor: Dell Inc.
board_name: 0HHV7N
board_version: A00

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D DMI2 [8086:6f00] (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [1028:0617]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 1 [8086:6f02] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 1 [8086:6f03] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 2 [8086:6f04] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 3 [8086:6f08] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.1 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 3 [8086:6f09] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.2 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 3 [8086:6f0a] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.3 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 3 [8086:6f0b] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon 
E3 v4/Xeon D Map/VTd_Misc/System Management [8086:6f28] (rev 01)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

[Hugo Lefeuvre]

Hi Andreas,

> since #918567 is RC critical there is some urgency to get this fixed.
> If I do not hear from you until Saturday I will assume you are fine
> with dlib in Debian Science team maintenance.

Sorry for missing your previous e-mail. Personal life is taking me away
from Debian right now. Not good during the freeze. :/

Of course I would be glad to maintain this package under the Debian Science
Team umbrella. Feel free to upload.

Thanks a lot for taking care of this issue.

Best Regards,
 Hugo

-- 
Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


signature.asc
Description: PGP signature

Bug#919476: swi-prolog stopped building on s390x

[Lev Lamberov]

Hi Matthias,

this bug is closed now, but I'd still like to clarify a bit on the
topic.

First of all, 8.0.0 release of SWI-Prolog is a new stable release. It
will receive only security updates. Previous stable release, 7.6.4 (the
last revision of stable branch 7.6.0), was released in Jan 2018. It will
not be supported anymore. And branch 8.0.0 is claimed by upstream to be
much more stable than 7.6.0.

Second, when it comes to s390x I'd like to stress that SWI-Prolog cannot
be built on it because it build-depends on libunwind, which is not built
for s390x since some time ago. Old binaries on s390x was removed, and
now swi-prolog don't list s390x as a target architecture (s390x is not
listed as a target architecture for libunwind either).

Third, about rdeps. Problems arose for ppl and logol. Problems for logol
were resolved, but the problem of ppl is more complicated. The last
release of ppl was in Feb 2016, and I don't think they closely track
SWI-Prolog releases.

Regards,
Lev

Bug#892277: marked as done (bridge-utils: hotplugging interferes with ifupdown resulting in unpredictable behavior)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 15:55:57 +
with message-id 
and subject line Bug#892277: fixed in bridge-utils 1.6-1
has caused the Debian Bug report #892277,
regarding bridge-utils: hotplugging interferes with ifupdown resulting in 
unpredictable behavior
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.)


-- 
892277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.5-11
Severity: serious

TL;DR: If you're using bridges, bonds and VLANs together, set 
   BRIDGE_HOTPLUG=no in /etc/default/bridge-utils.

Dear Maintainer,

There are some rather serious race conditions arising from the fact that 
bridge-utils handles udev events triggered by ifupdown actions and  
messes with the state of various interfaces while ifupdown is still 
running. To illustrate why this is happening, take the following e/n/i 
configuration as an example:

auto bond0
iface bond0 inet manual
  bond-slaves eth0 eth1
  bond-mode   active-backup
  bond-miimon 100
  up ip link set $IFACE mtu 9000

auto dmz
iface dmz inet manual
  bridge_ports  bond0.200
  bridge_fd   0
  bridge_stp  off
  bridge_maxwait  0
  up ip link set $IFACE up

This straightforward configuration worked fine in Jessie, but produces 
unexpected results on boot since Stretch, which - among others - 
include:

 - not setting the bond mode to active-backup, but to round-robin
 - creating bond0.200 with MTU 1500 instead of 9000

We have been hit by the above issues on production systems dist-upgraded 
to Stretch, and it all comes down to the races introduced by the 
bridge-utils hotplug support (which is now enabled by default).

So, what is actually happening is the following:

 1. On boot, networking.service calls `ifup --allow=auto -a`. This 
starts off by creating bond0. As soon as the ifenslave hooks create 
the interface, a udev "add" event for bond0 is triggered, *while 
ifup is still configuring bond0*.

 2. /lib/udev/bridge-network-interface is called, with $INTERFACE set to 
bond0. The script will run `ifquery --list --allow auto` and will 
look for any interface containing bond0 or bond0.* in its 
bridge_ports, matching "dmz" in our case. It will then go on to:
 a) create_vlan_port: this will run `ip link set bond0 up` and then 
create the vlan sub-interface on bond0
 b) call `ifup dmz` once the vlan port has been created

All of the above - for all we know - happen while `ifup -a` is 
*still* configuring bond0 on its own.

Step 2 is especially troublesome for the following reasons:

 i) create_vlan_port messes with the interface state while ifup is still 
configuring it. Bonding interfaces - for instance - need to be down 
to have their mode configured, and create_vlan_port explicitly sets 
the bond interface up. This causes the bond interface to potentially 
come up with the default mode (round-robin), making the system 
unreachable in case e.g. 802.3ad was requested.

 ii) create_vlan_port creates the VLAN sub-interface while the 
 underlying device is still being configured. This means that the 
 VLAN interface may be inherit the wrong MTU value, if ifup has not 
 yet set the parent interface's MTU to the desired value at the time 
 the VLAN interface is created.

 iii) dmz is brought up whenever bond0 is brought up, although this has 
  not been necessarily requested.

 iv) dmz is configured twice (once because of `ifup -a` and once because 
 of bridge-utils setting it up).

Note that high-cpu-count SMP systems seem more prone to the races i) and 
ii).

To be completely honest, I don't know what the hotplugging code is 
trying to achieve here, especially when it comes to short-circuiting 
ifupdown's internals. At a bare minimum, it should neither bring up 
"auto" interfaces that happen to be down, nor touch any interface while 
ifup might be still configuring it.

Regards,
Apollon

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

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

Versions of packages bridge-utils depends on:
ii  

Bug#892784: Works

[Thomas Goirand]

Hi Ivo,

After rescheduling the build, it looks like it worked there.

Cheers,

Thomas Goirand (zigo)

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

[Andreas Tille]

Hi again,

since #918567 is RC critical there is some urgency to get this fixed.
If I do not hear from you until Saturday I will assume you are fine
with dlib in Debian Science team maintenance.

Kind regards

   Andreas.

On Tue, Jan 15, 2019 at 11:36:14AM +0100, Andreas Tille wrote:
> Hi Séverin,
> 
> I stumbled upon dlib since I maintain some rdepends (plastimatch) of
> this lib and due to #918567 I've got a warning about testing removal.
> Since machine learning is definitely a topic that is covered by
> Debian Science I'd consider it really appropriate to maintain this
> software inside the Debian Science team, which means the repository
> would be moved to
> 
> https://salsa.debian.org/science-team/dlib
> 
> and the maintainer would be set to
> 
> Debian Science Maintainers 
> 
> 
> while your ID would be added as Uploader.  Would this course of action
> be OK for you?
> 
> Kind regards
> 
>Andreas.
> 
> -- 
> http://fam-tille.de
> 
> 

-- 
http://fam-tille.de

Bug#919486: Please support Debian Buster

[Laurent Bigonville]

Package: osinfo-db
Version: 0.20181120-1
Severity: serious

Hi,

Please support debian buster before the final release is made.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Processed: Re: irqbalance: endless loop during configure, system reaches maximum of open files

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #919213 [irqbalance] irqbalance: endless loop during configure, system 
reaches maximum of open files
Added tag(s) moreinfo.

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

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

[Axel Beckert]

Control: tag -1 + moreinfo

Hi Felipe,

Felipe Sateler wrote:
> On Sun, 13 Jan 2019 18:10:57 +0100 Axel Beckert  wrote:
> > On one of my systems (not the one I'm writing the report on), a
> > Raspberry Pi 2 with Debian Sid armhf and sysvinit,
 

> What are the versions of init-system-helpers

1.56+nmu1 since 19th of December 2018 acoording to the aptitude log.

> and systemd?

None, it's running sysvinit.

> Since version 1.56, we use systemctl to enable links (which seems the case
> with your log), but for some reason SYSTEMCTL_SKIP_SYSV environment
> variable appears to not be respected.

Thanks for that hint!

In /usr/sbin/update-rc.d:139 ff. $SYSTEMCTL_SKIP_SYSV is only used if
/bin/systemctl exists. /bin/systemctl shouldn't exist on that system,
but to my surprise, it does and it's rather old:

# ls -l /bin/systemctl
-rwxr-xr-x 1 root root 366476 May 26  2015 /bin/systemctl
# file /bin/systemctl
/bin/systemctl: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), 
dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, 
BuildID[sha1]=79551781262e12c906bc81e955088820a84cfda1, stripped

So this is either a bug back from the time where I migrated that box
from systemd to sysvinit or the initial Raspberry Pi SD card image
used for that installation was already unclear with regards to that
program.

Will try to figure that out. I very likely still have that image.
Until it's clear if that's a local issue or a bug in some package,
please ignore that package. Will either reassign or close the bug
appropriately later.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

[Felipe Sateler]

On Sun, 13 Jan 2019 18:10:57 +0100 Axel Beckert  wrote:
> Package: irqbalance
> Version: 1.5.0-2
> Severity: serious
>
> On one of my systems (not the one I'm writing the report on), a
> Raspberry Pi 2 with Debian Sid armhf and sysvinit, the terminal which I
> ran the upgrade in, looked like this (excerpt):
>
> Synchronizing state for irqbalance.service with sysvinit using
update-rc.d...
> Executing /usr/sbin/update-rc.d irqbalance defaults
> Executing /usr/sbin/update-rc.d irqbalance enable
> Synchronizing state for irqbalance.service with sysvinit using
update-rc.d...
> Executing /usr/sbin/update-rc.d irqbalance defaults
> Executing /usr/sbin/update-rc.d irqbalance enable
> Synchronizing state for irqbalance.service with sysvinit using
update-rc.d...


What are the versions of init-system-helpers and systemd?

Since version 1.56, we use systemctl to enable links (which seems the case
with your log), but for some reason SYSTEMCTL_SKIP_SYSV environment
variable appears to not be respected.

Saludos

Bug#900447: Build against freerdp2

[Fabián Rodríguez]

I've asked upstream to clarify if Guacamole v 1.0.0 now supports FreeRDP
v2, last update there was in September:

https://issues.apache.org/jira/browse/GUACAMOLE-249

The answer for now is "no", so I agree dropping only RDP for now would
help, at least enabling publishing a new version in Debian as it's
nearing feature/release freeze in ~1 month.

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Andreas Beckmann]

On 2019-01-16 15:28, Alastair McKinstry wrote:
> Matching changes should probably be made for mpich, the other mpi
> alternative.

looks quite straight-forward, I'll take a look.

I think both mpich,libmpich-dev and openmpi-bin,libopenmpi-dev should
have versioned Breaks against each other to denote the point where the
mpi-MULTIARCH alternatives were introduced. Since we are forcefully
removing all old mpi alternatives in this case, we should break the
corresponding other packages that provided them.

Can you dig out the versions when this was added?


Andreas

Bug#919409: marked as done (scikit-learn: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 15:00:29 +
with message-id 
and subject line Bug#919409: fixed in scikit-learn 0.20.1+dfsg-3
has caused the Debian Bug report #919409,
regarding scikit-learn: binary-any FTBFS
to be marked as done.

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

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


-- 
919409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-learn
Version: 0.20.1+dfsg-2
Severity: serious
Tags: ftbfs
Control: block 907806 by -1

https://buildd.debian.org/status/package.php?p=scikit-learn=sid

...
python3.7 -m sphinx -j 4 -D mathjax_path=MathJax.js -b html -d _build/doctrees  
  . _build/html/stable
/usr/bin/python3.7: No module named sphinx
make[1]: *** [Makefile:47: html] Error 1


Seems some package(s) have to move from Build-Depends-Indep
to Build-Depends.
--- End Message ---
--- Begin Message ---
Source: scikit-learn
Source-Version: 0.20.1+dfsg-3

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated scikit-learn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Jan 2019 14:57:47 +0100
Source: scikit-learn
Binary: python-sklearn python-sklearn-lib python3-sklearn python3-sklearn-lib 
python-sklearn-doc
Architecture: source
Version: 0.20.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Mattia Rizzolo 
Description:
 python-sklearn - Python modules for machine learning and data mining - Python 2
 python-sklearn-doc - documentation and examples for scikit-learn
 python-sklearn-lib - low-level implementations and bindings for scikit-learn
 python3-sklearn - Python modules for machine learning and data mining - Python 
3
 python3-sklearn-lib - low-level implementations and bindings for scikit-learn 
- Python
Closes: 919409
Changes:
 scikit-learn (0.20.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Stuart Prescott ]
   * Update Standards-Version to 4.3.0 (no changes required).
   * Move source.lintian-overrides to new location.
   * Fix short descriptions for Python modules packages to not be identical.
   * Fix location of documentation in doc-base file.
 .
   [ Mattia Rizzolo ]
   * Fix FTBFS of the binary-arch targets.  Closes: 919409
Checksums-Sha1:
 1f673b0eed0a76a1d25228b579a17946ee74b396 3371 scikit-learn_0.20.1+dfsg-3.dsc
 9b5c174c9bb28b313de8b5a4eae23fcca0a6c031 2 
scikit-learn_0.20.1+dfsg-3.debian.tar.xz
 59bc2a55945d87954cdb610e656752ea12c57b58 7658 
scikit-learn_0.20.1+dfsg-3_source.buildinfo
Checksums-Sha256:
 7c5742f2c568dc523da0aeefd28a9c4788d1072b74e869bfca207c73dddcc807 3371 
scikit-learn_0.20.1+dfsg-3.dsc
 6200c57a873a4bd284bddefbcd85773d4d18f536cc5c55813692ecaede14ca3e 2 
scikit-learn_0.20.1+dfsg-3.debian.tar.xz
 a53130c2758527a2a6a5408bb159e23808514ea914541f9aeef0718a67fe45cd 7658 
scikit-learn_0.20.1+dfsg-3_source.buildinfo
Files:
 0af5f273fbf84e9c7fb855c7615664a3 3371 python optional 
scikit-learn_0.20.1+dfsg-3.dsc
 423b311cbf884ca445614dabd0cb6d65 2 python optional 
scikit-learn_0.20.1+dfsg-3.debian.tar.xz
 7af9c2edf4d9ec45b2444e2580393678 7658 python optional 
scikit-learn_0.20.1+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlw/OIwSHG1hdHRpYUBk
ZWJpYW4ub3JnAAoJEAgWueGMdiut5xcP/RA4yR9WtGz6n2KAbD5TY75mlBZHzIeP
C3okpcd1H5QH73HiCsKNnGr+Ug7JgDQM7aUYrzKTk8epUcMEhHW5YjDc1EoAeV0D
yAgTz8os9Q0y8jFrTiP3SrlB/jbfdaKSy6nOOoramaXcDJtt3VJdrlRuMkcdtRWU
oBfmtQ2IVTpcVhf2lGPcFwW4CvCZIEqJDfxIgaEC6CN/cKttYy3Xxy9A1GWvv2dY
KRhtDITz0RnPPjlPNOiIdcoqY8x0r029hMRgwIbVHIBY9vcL5WqbHtJgpwXNRJjZ
XDAHyFZ3n7QKFbwK7ZQ52+eWCG0MNzGZzKnCEVwjO8/xXTCrHbikRyxTqCndHWTB
IEEjGtEdltAmEw5XGAWmSbi9dBQ2mlSHT8pct1XTfj+ycFFxDgpuYXyWEB4LaN2l
dbbMp0waOZT1A0hu8wKDaZN20SG4Vxyz7XMxoLYpQwtaFZ5yTKlX3ZvynMI8XWvq
K1smUiuEpN3kiZapHCdtCrb7iaWchBH8Oxvt7/wI0OoasR55H5w0OBWBhw0UTrhd
wggs1T+9nvY91onesT3WncbsZIUQ/dgUlIYB2H1hWzDCqcc57ScqdBMQM2+sB7gS

Bug#906373: marked as done (lasagne: FTBFS in buster/sid (Could not import extension numpydoc))

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 14:58:59 +
with message-id 
and subject line Bug#906373: fixed in lasagne 0.1+git20181019.a61b76f-1
has caused the Debian Bug report #906373,
regarding lasagne: FTBFS in buster/sid (Could not import extension numpydoc)
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.)


-- 
906373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lasagne
Version: 0.1+git20180322.37ca134-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,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -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.6 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 
/<>/lasagne-0.1+git20180322.37ca134/.pybuild/cpython2_2.7_lasagne/build/lasagne

[... snipped ...]

byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/cuda_convnet.py
 to cuda_convnet.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/merge.py
 to merge.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/corrmm.py
 to corrmm.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/embedding.py
 to embedding.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/local.py
 to local.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/conv.py
 to conv.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/normalization.py
 to normalization.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/pool.py
 to pool.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/shape.py
 to shape.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/dnn.py
 to dnn.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/helper.py
 to helper.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/recurrent.py
 to recurrent.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/special.py
 to special.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/noise.py
 to noise.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/dense.py
 to dense.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/base.py
 to base.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/layers/input.py
 to input.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/theano_extensions/conv.py
 to conv.cpython-36.pyc
byte-compiling 
/<>/lasagne-0.1+git20180322.37ca134/debian/python3-lasagne/usr/lib/python3.6/dist-packages/lasagne/theano_extensions/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 

Bug#918943: marked as done (waagent: FTBFS in sid (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 15:01:04 +
with message-id 
and subject line Bug#918943: fixed in waagent 2.2.34-2
has caused the Debian Bug report #918943,
regarding waagent: FTBFS in sid (failing tests)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,systemd --buildsystem pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7/build/azurelinuxagent
copying azurelinuxagent/agent.py -> 
/<>/.pybuild/cpython3_3.7/build/azurelinuxagent
copying azurelinuxagent/__init__.py -> 
/<>/.pybuild/cpython3_3.7/build/azurelinuxagent
creating /<>/.pybuild/cpython3_3.7/build/azurelinuxagent/distro

[... snipped ...]

  File 
"/<>/.pybuild/cpython3_3.7/build/tests/common/test_cgroups.py", 
line 128, in exercise_telemetry_instantiation
self.assertIn('cpu', test_cgroup.cgroups)
AssertionError: 'cpu' not found in {}

==
FAIL: test_telemetry_instantiation_as_normal_user_with_limits 
(tests.common.test_cgroups.TestCGroups)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/mock.py", line 1195, in patched
return func(*args, **keywargs)
  File 
"/<>/.pybuild/cpython3_3.7/build/tests/common/test_cgroups.py", 
line 193, in test_telemetry_instantiation_as_normal_user_with_limits
self.exercise_telemetry_instantiation(cg)
  File 
"/<>/.pybuild/cpython3_3.7/build/tests/common/test_cgroups.py", 
line 128, in exercise_telemetry_instantiation
self.assertIn('cpu', test_cgroup.cgroups)
AssertionError: 'cpu' not found in {}

--
Ran 462 tests in 46.231s

FAILED (failures=4, errors=50, skipped=5, expected failures=1)
RESPONSE: message
RESULT: [HTTP Failed] [status: reason] message
PRESENT: True
RESPONSE: b'message'
RESULT: [HTTP Failed] [status: reason] b'message'
PRESENT: True
RESPONSE: €message€
RESULT: [HTTP Failed] [status: reason] message
PRESENT: True
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.525243 ERROR Daemon Command: [ls /not-exists], return code: 
[2], result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
2019/01/10 16:43:59.533425 ERROR Daemon Command: [ls \u6211], return code: [2], 
result: []
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7/build; python3.7 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:8: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


This is just how the build ended in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Dmitry Bogatov]

control: tags -1 +confirmed

[2019-01-14 19:56] Celejar 
> ~# dpkg-reconfigure git-daemon-run
> Service git-daemon already added.
> warning: git-daemon: unable to open supervise/ok: file does not exist
> 
> > If I'm lucky then that will get it working.  I'll try to reproduce it
> > here and set the right dependencies.
> 
> Sorry :/
> 
> Again, thanks for the help. I'm likely doing something basic wrong, so
> thanks for bearing with me.

Dear submitter, you are not doing wrong. It is actually bug. To
workaround it it /right now/:

# mkdir /var/lib/supervise/git-daemon

If you have running 'runsvdir /etc/service' process (due
runit-{init,sysv,systemd}, for example), things should be fine.

Dear git maintainer, you could plug this bug by adding
`/var/lib/supervise/git-daemon' into `debian/git-daemon-run.dirs'.

But I wish to discuss proper solution. After discussing issue of runit
scripts, debian-devel@ consensus was that runit scripts should be part
of main package, `git-daemon' in this particular case.

So, should I propose you patch (in 7 days), that merges
bin:git-daemon-run into bin:git-daemon, would you be able to review and
apply/upload it before hard freeze?

Processed: Re: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +confirmed
Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: 
unable to open supervise/ok: file does not exist'
Added tag(s) confirmed.

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

Processed: severity of 864113 is serious, affects 919066

[Debian Bug Tracking System]

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

> severity 864113 serious
Bug #864113 [src:libgnome-keyring] libgnome-keyring: Please stop 
Build-Depending on libgcrypt11-dev transition package
Severity set to 'serious' from 'normal'
> affects 919066 + xastir
Bug #919066 {Done: Dave Hibberd } [xastir-data] 
xastir-data: missing Breaks+Replaces: xastir (<< 2.1.0-2)
Added indication that 919066 affects xastir
> thanks
Stopping processing here.

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

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Andreas Beckmann]

On 2019-01-16 15:01, Alastair McKinstry wrote:
>> Once we have reached a clean state (with 3.1.3-10 installed), there
>> should be no need to rerun the preinst cleanup operations for every
>> subsequent upgrade?
> 
> Unfortunately, experience is that we'll see people upgrading from random
> old sid versions to the 3.1.3-10.

I was not talking about removing the code (right now). But that we don't
need to run it again for upgrading from (hypothetical) 3.1.3-11 to 3.1.3-13.
It of course will be run when upgrading from 3.0.8-15 to 3.1.3-12.
And it will be run on initial install, too, since other providers can be
involved.

Andreas

Processed: Re: Bug#919461: ssreflect ftbfs in unstable

[Debian Bug Tracking System]

Processing control commands:

> retitle 919461 ssreflect FTBFS in unstable due to missing ssrmatching
Bug #919461 [src:ssreflect] ssreflect ftbfs in unstable
Changed Bug title to 'ssreflect FTBFS in unstable due to missing ssrmatching' 
from 'ssreflect ftbfs in unstable'.
> owner 919461 !
Bug #919461 [src:ssreflect] ssreflect FTBFS in unstable due to missing 
ssrmatching
Owner recorded as Benjamin Barenblat .

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

Bug#919461: ssreflect ftbfs in unstable

[Benjamin Barenblat]

Control: retitle 919461 ssreflect FTBFS in unstable due to missing ssrmatching
Control: owner 919461 !

That’s my fault. In my most recent Coq upload, I disabled ssrmatching
and a couple of other plugins due to license concerns [1]. Those have
now been resolved upstream [2]. I’m going to backport the changes to
8.8.2 and do another upload in the next few days, after which this bug
should go away.

[1] 
https://salsa.debian.org/ocaml-team/coq/commit/4181269ff800d58e60b886d0aaa289a9cd0d
[2] https://github.com/coq/coq/commit/a92e4fbe88e16c312fe57a6f00ccba94322ee111

Processed: Merge bugs

[Debian Bug Tracking System]

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

> merge 919472 918563
Bug #919472 [src:camomile] camomile ftbfs on ppc64el
Bug #918563 [src:camomile] camomile FTBFS on ppc64{,el}: camomilelocaledef got 
signal SEGV
Added tag(s) buster and sid.
Bug #919472 [src:camomile] camomile ftbfs on ppc64el
Added tag(s) ftbfs.
Merged 918563 919472
> thanks
Stopping processing here.

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

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Alastair McKinstry]

On 16/01/2019 13:49, Andreas Beckmann wrote:

On 2019-01-16 13:58, Alastair McKinstry wrote:

Hi

Would you happen to know syntax for piuparts to enable an upgrade test
from stretch to a new (local) version?

the command line for the normal stretch2{buster,sid} test can be derived
from corresponding log file, you may have to adjust paths etc.

and then its just these three extra:
--bindmount /tmp/openmpi --testdebs-repo /tmp/openmpi
--distupgrade-to-testdebs

with some set of .debs and a Packages file in /tmp/openmpi (or anywhere
else)


I'm trying to debug and need to see whats failing in the preinst script.
So I've a local 3.1.3-10 version with 'set -x' in the scripts, but can't
seem to do a stretch-> this upgrade, without putting it in sid or
experimental.

I finally got curious and looked into this last night ... I've
completely overhauled your maintainer scripts and just pushed them to a
branch anbe/alternatives
I hope I understood what your intentions were for the preinst and
reimplemented them in a more readable way. I needed some time to
understand what type of corruption you meant until I found the broken
mpi alternative status file posted by (forgot his name). Because that
code was primarily triggering on "no alternative installed".
I haven't done extensive tests, but it passes the upgrade from stretch :-)

Thanks, I'll review them.

Once we have reached a clean state (with 3.1.3-10 installed), there
should be no need to rerun the preinst cleanup operations for every
subsequent upgrade?


Unfortunately, experience is that we'll see people upgrading from random 
old sid versions to the 3.1.3-10.


(Problems in the upgrade scripts before were reported for multiple sid 
releases. Just because the code is gone from sid doesn't mean we won't 
get reports :-( )


I'm expecting to leave the preinst cleanup operations in the buster 
release version, then delete them.



As I just write this, I think you may want to run ldconfig (which
activates the corresponding trigger in glibc) after you add/remove
alternatives that involve shared libraries.

That should be happening automatically; the triggers will be added in 
the #DEBHELPER# section, no ?

Andreas

PS: feel free to repost to the corresponding bug

PPS: That's a pretty easy alternatives cleanup and setup, compared the
the nvidia and glx alternatives (which involves diversions) and the mess
I had to recover from when I initially took over the
nvidia-graphics-drivers maintenance. And I did upgrade tests from every
single ancient nvidia-graphics-drivers version available from
snapshot.d.o ... that's how I got involved with piuparts :-)

PPPS: all that was missing was a single '|| true'


--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
 believing the innocent had everything to fear, mostly from the guilty but in 
the longer term
 even more from those who say things like “The innocent have nothing to fear.”
 - T. Pratchett, Snuff

Bug#919472: camomile ftbfs on ppc64el

[Kyle Robbertze]

merge 918563 -1
thanks

I am waiting on porter box access from DSA so that I can debug this
issue. I think it is related to 918562 [1], but need to test that.

[1] https://bugs.debian.org/918562

Cheers
Kyle

Processed: Re: Bug#919462: coq ftbfs on some release architectures

[Debian Bug Tracking System]

Processing control commands:

> retitle 919462 coq FTBFS on architectures without native OCaml backends
Bug #919462 [src:coq] coq ftbfs on some release architectures
Changed Bug title to 'coq FTBFS on architectures without native OCaml backends' 
from 'coq ftbfs on some release architectures'.
> owner 919462 !
Bug #919462 [src:coq] coq FTBFS on architectures without native OCaml backends
Owner recorded as Benjamin Barenblat .

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

Bug#919476: marked as done (swi-prolog stopped building on s390x)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 15:58:08 +0200
with message-id <20190116135808.GA13395@localhost>
and subject line Re: Bug#919476: swi-prolog stopped building on s390x
has caused the Debian Bug report #919476,
regarding swi-prolog stopped building on s390x
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.)


-- 
919476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:swi-prolog
Version: 8.0.0+dfsg-1
Severity: serious
Tags: sid buster

swi-prolog stopped building on s390x, blocking the migration to testing.  Now
there are a few rdeps ...  is it really appropriate to do this update when
Debian is frozen?
--- End Message ---
--- Begin Message ---
On Wed, Jan 16, 2019 at 01:28:12PM +0100, Matthias Klose wrote:
> Package: src:swi-prolog
> Version: 8.0.0+dfsg-1
> Severity: serious
> Tags: sid buster
> 
> swi-prolog stopped building on s390x, blocking the migration to testing.  Now
> there are a few rdeps ...  is it really appropriate to do this update when
> Debian is frozen?

This change was long ago, and the stale s390x binaries were removed from 
unstable last year.

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

Processed: your mail

[Debian Bug Tracking System]

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

> Found 914517 linux-image-4.19.0-1-amd64-unsigned
Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset 
is set
The source 'linux' and version 'linux-image-4.19.0-1-amd64-unsigned' do not 
appear to match any binary packages
Marked as found in versions linux/linux-image-4.19.0-1-amd64-unsigned.
> Thanks
Stopping processing here.

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

Bug#919462: coq ftbfs on some release architectures

[Benjamin Barenblat]

Control: retitle 919462 coq FTBFS on architectures without native OCaml backends
Control: owner 919462 !

Coq actually does build, but the test suite fails because I messed up
plugin loading on architectures that don’t have ocamlopt. Upstream
handles both native and bytecode worlds by installing the same file in
two different places; I found this unpalatable and just removed one of
the copies [1]. I didn’t realize at the time that the bytecode world
needed that file. I’ll look into fixing this in the next couple of days.


[1] 
https://salsa.debian.org/ocaml-team/coq/commit/6fabd6380fd08b6e3defdfceb137b47d4db858a3#1823cfdb97f631de92d185f9a7ef6c1f58bc9147

Processed: affects 918380

[Debian Bug Tracking System]

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

> affects 918380 src:libweb-api-perl
Bug #918380 [src:libmail-chimp3-perl] FTBFS: test failures with new Web::API
Added indication that 918380 affects src:libweb-api-perl
> thanks
Stopping processing here.

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

Bug#919481: guile-2.0 ftbfs on ppc64el

[Matthias Klose]

Package: src:guile-2.0
Version: 2.0.13+1-5
Severity: serious
Tags: sid buster

guile-2.0 ftbfs on ppc64el (checked on plummer):

[...]
Running bytevectors.test
FAIL: bytevectors.test: 2.8 Operations on IEEE-754 Representations:
bytevector-ieee-single-{ref,set!} [unaligned] (compile)
[...]
Running i18n.test
UNRESOLVED: i18n.test: text collation (Czech): string-localelocale-string: French: integer
FAIL: i18n.test: number->locale-string: French: fraction
FAIL: i18n.test: number->locale-string: French: fraction, 1 digit
FAIL: i18n.test: format ~h: French: 12345.5678
FAIL: i18n.test: monetary-amount->locale-string: French: integer
FAIL: i18n.test: monetary-amount->locale-string: French: fraction
[...]
FAIL: check-guile
==
1 of 1 test failed
Please report to bug-gu...@gnu.org
==
make[4]: *** [Makefile:1938: check-TESTS] Error 1
make[4]: Leaving directory '/home/doko/guile-2.0-2.0.13+1'
make[3]: *** [Makefile:2223: check-am] Error 2
make[3]: Leaving directory '/home/doko/guile-2.0-2.0.13+1'
make[2]: *** [Makefile:1838: check-recursive] Error 1
make[2]: Leaving directory '/home/doko/guile-2.0-2.0.13+1'
make[1]: *** [Makefile:2225: check] Error 2
make[1]: Leaving directory '/home/doko/guile-2.0-2.0.13+1'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:99: build-arch] Error 2

Bug#918974: marked as done (fuse-zip ftbfs on mipsel, and unbuildable on armel)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 12:49:12 +
with message-id 
and subject line Bug#918974: fixed in fuse-zip 0.5.0-1
has caused the Debian Bug report #918974,
regarding fuse-zip ftbfs on mipsel, and unbuildable on armel
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.)


-- 
918974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fuse-zip
Version: 0.4.5-1
Severity: serious
Tags: sid buster

fuse-zip ftbfs on mipsel, and unbuildable on armel.  The package doesn't add
testing with the missing builds.
--- End Message ---
--- Begin Message ---
Source: fuse-zip
Source-Version: 0.5.0-1

We believe that the bug you reported is fixed in the latest version of
fuse-zip, 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.
Matthew Harm Bekkema  (supplier of updated fuse-zip 
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, 12 Jan 2019 16:31:31 +1100
Source: fuse-zip
Binary: fuse-zip
Architecture: source amd64
Version: 0.5.0-1
Distribution: unstable
Urgency: low
Maintainer: Matthew Harm Bekkema 
Changed-By: Matthew Harm Bekkema 
Description:
 fuse-zip   - ZIP archive mounter based on FUSE
Closes: 918974
Changes:
 fuse-zip (0.5.0-1) unstable; urgency=low
 .
   * New upstream release
   * Bump standards
   * Bump debhelper-compat to 12
   * Disable valgrind (Closes: #918974)
Checksums-Sha1:
 0b0f38500cb3c50aab9c420dfe31f4aa429f97f8 1900 fuse-zip_0.5.0-1.dsc
 d138b2f071449abeaec61112ce7ffd154d7851fd 696208 fuse-zip_0.5.0.orig.tar.gz
 5e5b4ab1747975688cb757e3468797274f1a5237 3288 fuse-zip_0.5.0-1.debian.tar.xz
 9fd7f14e429ffb4e1f01b2c60614f2b9f47782c6 201228 
fuse-zip-dbgsym_0.5.0-1_amd64.deb
 bec74d635020d31ee8dfe7d782f8caf9321a0c33 5909 fuse-zip_0.5.0-1_amd64.buildinfo
 759e63a7f4a5ba7ca8e00c74205ac6e34425233d 31188 fuse-zip_0.5.0-1_amd64.deb
Checksums-Sha256:
 cf416ee882c20ed533c9167bacaccc060391fe09380e72b328296c05431c668c 1900 
fuse-zip_0.5.0-1.dsc
 5667fa1425937dfffcd8eeeacd44395b70213bed99dcac038f3f1f9cb7651267 696208 
fuse-zip_0.5.0.orig.tar.gz
 7c79e335daf6dc94d7cb927927107eccba150e840ab98356302b1fdae8f13a7f 3288 
fuse-zip_0.5.0-1.debian.tar.xz
 4f6cae2d8c21fece9cd42b55546049da36ff7767a43b97086eac1e4c0fec39a5 201228 
fuse-zip-dbgsym_0.5.0-1_amd64.deb
 0f2bd5bcb2b5b6daff77d1d7502e15ac8de58cb49bf00427249c9cb95215957e 5909 
fuse-zip_0.5.0-1_amd64.buildinfo
 ac76e64172a03a9f757ee044ba4642b6304a65597d8fb2c79731d7c04400efa7 31188 
fuse-zip_0.5.0-1_amd64.deb
Files:
 c88e1366fc3ae87e0c41cb21bd6415d1 1900 utils optional fuse-zip_0.5.0-1.dsc
 81995a2e60ccfb496663801ce622d8de 696208 utils optional 
fuse-zip_0.5.0.orig.tar.gz
 d0fb1857de46b399f9d1a4120eb5540d 3288 utils optional 
fuse-zip_0.5.0-1.debian.tar.xz
 1cbe5b6b8b1297712f922af8c6fcf137 201228 debug optional 
fuse-zip-dbgsym_0.5.0-1_amd64.deb
 62e0ff4daaa43cac0023b6c12ef46dde 5909 utils optional 
fuse-zip_0.5.0-1_amd64.buildinfo
 3434ef1c87e566062fb0cf67b6da32dc 31188 utils optional 
fuse-zip_0.5.0-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlw/I04ACgkQq1PlA1ho
d6ZR6RAAhXN/80z/5ywRKYrXnoF9MWc4mUUM3wLvNsQ/HynuxtHobjS3r298Wiap
XiTHr6tRK/g0xzzKsS9iBIp4tMxQ3hIHj5/0/AvoIUBau7xHaCZx76dFCOVPLfOZ
PvK/wHshWNabhQYAP6kuY+iuwmwg4lMqYjhM3feXyjfCNj+G99L0K9OfUdKyCRIu
BY1HPz0yQcKOgEfIIwyb6KnVUkkD153G4aNBHdg6Nwmv0urIhvXKdijXoaPY4nnN
qRaTSR7/7J6oxM98sqpjr5FJpXOB9ANUkR3Dc/2nUtOaLtCJnkAIsNNdfs7CJLe3
joN2bCdxsg6yuVx2chbYG8YyUJ/wzZnIldimI9KgYUlZvY37dfxhCbMWodTY+d9w
WVVpcQWRC5YgKZwzQjZIW+ZPjQcHKiJXV3kO9nWM+JcIrrWh8I+7Yd4af/mUjdKV
bYvTJJJurljsFERKJOVBMwq5nO2YkjE95KiSPUbmusBxU14d38u5TrIOkK99OIDd
nd+1G8hj68lZ+tJ9G5JPs4rEK4wXeRviYJ2Dggsk2pppv8Qdqs2eEsvuYp5DAi4N
3ljk+1XqDrPDpbkvEDVXHSVQkkOH182JD9CGXHQFlhcPYgv9TNGydNIMbn6uE8yu
A9oBIEaEWauXaANlbTj5fC78u0je8W11aSU3sLM73LtavFjKeQ8=
=g2gA
-END PGP SIGNATURE End Message ---

Bug#919470: argonaut: Non-working maintainer address

[Mike Gabriel]

Hi Scott,

On  Mi 16 Jan 2019 12:47:47 CET, Scott Kitterman wrote:


Package: argonaut
Version: 1.2-2
Severity: serious
Justification: Policy 3.3

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  packa...@lists.fusiondirectory.org
retry timeout exceeded

Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;packa...@lists.fusiondirectory.org
Status: 5.0.0

argonaut_1.2.3-1_source.changes uploaded successfully to localhost
along with the files:
  argonaut_1.2.3-1.dsc
  argonaut_1.2.3.orig.tar.gz
  argonaut_1.2.3.orig.tar.gz.asc
  argonaut_1.2.3-1.debian.tar.xz
  argonaut_1.2.3-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

A working maintainer address is required.  Please either change the
maintainer address or get this one fixed.

Scott K


We possibly should switch over to a team mail address on tracker.d.o [1] here.

@Benoit: comments? Feedback?

Mike

[1] https://tracker.debian.org/teams/
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp2cg3xRH2KA.pgp
Description: Digitale PGP-Signatur

Bug#910731: kaddressbook: crashes at startup

[Bernhard Übelacker]

Hello Francesco,
I missed that, sorry about that.


On Mon, 26 Nov 2018 15:22:39 +0100 =?utf-8?Q?Francesco_Potort=C3=AC?= 
 wrote:
> >can you still observe the crash, or got it fixed by updates
> >in mid October? (Like mentioned in #910581)
> 
> It does not crash any more, ...

So the initial issue could be seen as resolved.


> ...but it shows an error message at startup:
> 
> The Akonadi personal information management service is not running.
> This application cannot be used without it. [Start]
> 
> If I press the [Start] button, apparently nothing happens.
> 
> When I launch kaddressbook from a terminal, I see this error message:
> 
> org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to 
> D-Bus auto-launch
> 
> appearing twice after startup, and once more each time I press the
> [Start] button.
> 
> I suppose this means that kaddressbook should depend on akonadi-server.
> 
> After installing akonadi-server and launching kaddressbook I see a
> message telling something about setup, then a new error screen with
> message:
> 
> Cannot connect to the Personal Information management service.  There
> are no Akonadi Agents available.  Please verify your KDE PIM
> Installation.  [Details...]
> 
> On the terminal, I see these messages:
> 
> Connecting to deprecated signal 
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> akonadi.collectionattributetable   OK
> akonadi.collectionmimetyperelation OK
> akonadi.collectionpimitemrelation  OK
> akonadi.collectiontableOK
> akonadi.flagtable  OK
> akonadi.mimetypetable  OK
> akonadi.parttable  OK
> akonadi.parttypetable  OK
> akonadi.pimitemflagrelationOK
> akonadi.pimitemtable   OK
> akonadi.pimitemtagrelation OK
> akonadi.relationtable  OK
> akonadi.relationtypetable  OK
> akonadi.resourcetable  OK
> akonadi.schemaversiontable OK
> akonadi.tagattributetable  OK
> akonadi.tagremoteidresourcerelationtable   OK
> akonadi.tagtable   OK
> akonadi.tagtypetable   OK
> Connecting to deprecated signal 
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> org.kde.pim.akonadicore: ""
> org.kde.pim.akonadicore: Job error:  "" for collection: QVector() 
> 
> Pressing the [Details...] button produces no apparent effect.
> 
> After killing and restarting kaddressbook, the initial setup message
> does not appear any more, while the error message screen is still
> there.  Again, pressing the [Details...] button has no visible effect.
> No messages are produced on the terminal
> 

This error seems not directly related to the crash and
would have maybe deserved its own bug report, as it may be a
problem in a different package.

Nevertheless, I cannot reproduce this error
in a fresh Buster amd64 VM.
Instead I get the error described in #910902, that can
be worked around by just creating the missing directory.

Therefore I am sorry and need to ask again if you
still observe this error?

Kind regards,
Bernhard


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



signature.asc
Description: OpenPGP digital signature

Bug#919477: acl2 ftbfs on armel, armhf, arm64 and ppc64el

[Matthias Klose]

Package: src:acl2
Version: 8.0dfsg-1
Severity: serious
Tags: sid buster

acl2 ftbfs on armel, armhf, arm64 and ppc64el.

https://buildd.debian.org/status/fetch.php?pkg=acl2=armel=8.0dfsg-1=1515868416=0

and checked that it ftbfs on plummer (ppc64el).

Bug#919476: swi-prolog stopped building on s390x

[Matthias Klose]

Package: src:swi-prolog
Version: 8.0.0+dfsg-1
Severity: serious
Tags: sid buster

swi-prolog stopped building on s390x, blocking the migration to testing.  Now
there are a few rdeps ...  is it really appropriate to do this update when
Debian is frozen?

Bug#893227: libbluray FTBFS with openjdk-9

[Reinhard Tartler]

Hi Petri,

I'm following up on a question that Sebatian (CC'ed) asked on the mailing
list last march [1].
The issue is that Debian intends to drop openjdk-8 in favor of openjdk-11,
and we as package
maintainers of libbluray are asked to look into this transition. Your
response back then
was that there are non-trivial changes to the code necessary to make this
work.

Looking at the commit history, it seems that there have been some changes
wrt java
compatibility, mostly by you. I wonder whether you'd expect libbluray to
work with
openjdk-11. If not, is this something on your roadmap, or do you consider
this a
stretch goal for the forseeable future?

Please let me know what your thoughts on this issue are..

Best,
-rt

[1]
https://mailman.videolan.org/pipermail/libbluray-devel/2018-March/002890.html

On Sat, Mar 17, 2018 at 9:15 AM Adrian Bunk  wrote:

> Source: libbluray
> Version: 1:1.0.2-2
> Severity: serious
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbluray.html
>
> ...
>
> compile:
> [javac] /build/1st/libbluray-1.0.2/src/libbluray/bdj/build.xml:24:
> warning: 'includeantruntime' was not set, defaulting to
> build.sysclasspath=last; set to false for repeatable builds
> [javac] Using javac -source 1.4 is no longer supported, switching to
> 1.6
> [javac] Using javac -target 1.4 is no longer supported, switching to
> 1.6
> [javac] Compiling 664 source files to
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/build
> [javac] warning: [options] bootstrap class path not set in conjunction
> with -source 1.6
> [javac] warning: [options] source value 1.6 is obsolete and will be
> removed in a future release
> [javac] warning: [options] target value 1.6 is obsolete and will be
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete
> options, use -Xlint:-options.
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java-j2se/java/awt/peer/BDFramePeer.java:176:
> error: package sun.awt.CausedFocusEvent does not exist
> [javac] public boolean requestFocus(Component c, boolean a,
> boolean b, long l, sun.awt.CausedFocusEvent.Cause d) {
> [javac]
> ^
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/blurayx/s3d/ti/StereoscopicCodingType.java:37:
> warning: non-varargs call of varargs method with inexact argument type for
> last parameter;
> [javac] type =
> (CodingType)constructor.newInstance(new String[] { "MPEG4_MVC_VIDEO" });
> [javac]
> ^
> [javac]   cast to Object for a varargs call
> [javac]   cast to Object[] for a non-varargs call and to suppress this
> warning
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/blurayx/uhd/ti/UHDCodingType.java:38:
> warning: non-varargs call of varargs method with inexact argument type for
> last parameter;
> [javac] type =
> (CodingType)constructor.newInstance(new String[] { "HEVC_VIDEO" });
> [javac]
> ^
> [javac]   cast to Object for a varargs call
> [javac]   cast to Object[] for a non-varargs call and to suppress this
> warning
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:81:
> warning: [removal] classDepth(String) in SecurityManager has been
> deprecated and marked for removal
> [javac] if
> (classDepth("javax.crypto.JceSecurityManager") < 3) {
> [javac] ^
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:88:
> warning: [removal] classDepth(String) in SecurityManager has been
> deprecated and marked for removal
> [javac] if (classDepth("org.videolan.Libbluray") == 3)
> {
> [javac] ^
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:97:
> warning: [removal] classDepth(String) in SecurityManager has been
> deprecated and marked for removal
> [javac] if (classDepth("sun.awt.AWTAutoShutdown") > 0) {
> [javac] ^
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:222:
> warning: [removal] checkSystemClipboardAccess() in SecurityManager has been
> deprecated and marked for removal
> [javac] public void checkSystemClipboardAccess() {
> [javac] ^
> [javac]
> /build/1st/libbluray-1.0.2/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21:
> error: BDFileSystemImpl is not abstract and does not override abstract
> method getNameMax(String) in FileSystem
> [javac] class BDFileSystemImpl extends BDFileSystem {
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe 

Bug#919473: zapping: Settings schema 'net.sf.Zapping.plugins.teletext' does not contain a key named 'method'

[Jakub Wilk]

Package: zapping
Version: 0.10~cvs6-15
Severity: grave

zapping doesn't start:

  $ zapping

  (zapping:3191): dbind-WARNING **: 13:01:17.865: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files

  (zapping:3191): GLib-GIO-ERROR **: 13:01:18.527: Settings schema 
'net.sf.Zapping.plugins.teletext' does not contain a key named 'method'
  Trace/breakpoint trap


-- System Information:
Architecture: i386

Versions of packages zapping depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  libc62.28-5
ii  libcairo21.16.0-2
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.2-3
ii  libgtk-3-0   3.24.3-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblirc-client0  0.10.1-5
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpng16-16  1.6.36-3
ii  libpython2.7 2.7.15-5
ii  libx11-6 2:1.6.7-1
ii  libxext6 2:1.3.3-1+b2
ii  libxinerama1 2:1.1.4-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxmu6  2:1.1.2-2
ii  libxv1   2:1.0.11-1
ii  libxxf86dga1 2:1.1.4-1+b3
ii  libxxf86vm1  1:1.1.4-1+b2
ii  libzvbi0 0.2.35-15

Versions of packages zapping recommends:
pn  gconf2  

--
Jakub Wilk

Bug#919472: camomile ftbfs on ppc64el

[Matthias Klose]

Package: src:camomile
Version: 1.0.1-1
Severity: serious
Tags: sid buster

checked on the ppc64el porter box:

[...]
   dh_ocamlinit -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/doko/camomile-1.0.1'
ocaml configure.ml --share=/home/doko/camomile-1.0.1/debian/tmp/usr/share
make[1]: Leaving directory '/home/doko/camomile-1.0.1'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/doko/camomile-1.0.1'
[ -f debian/autoreconf.before ] || dh_autoreconf
jbuilder build
File "Camomile/jbuild", line 4, characters 0-96:
4 | (rule (with-stdout-to installConfig.ml
5 |(echo "let share_dir = \"/usr/share/camomile\"")))
Warning: File installConfig.ml is both generated by a rule and present in the
source tree.
As a result, the rule is currently ignored, however this will become an error in
the future.
To keep the current behavior and get rid of this warning, add a field (fallback)
to the rule.
   ocamlyacc Camomile/internal/uReStrParser.{ml,mli}
4 shift/reduce conflicts.
camomilelocaledef Camomile/locales/ar.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/az.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/div.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/el.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/fa.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/gu.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/he.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/hi__DIRECT.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/hi.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ka.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/kk.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/kn.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ky.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/mn.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/mr.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/pa.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/sa.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ja.mar
Warning : strength option is not supported
camomilelocaledef Camomile/locales/syr.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/te.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ta.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/tt.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/th.mar
Warning : file loading is not supported.
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ur.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/uz.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/vi.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/zh__PINYIN.mar (got signal SEGV)
(cd _build/default/Camomile && tools/camomilelocaledef.exe --file
locales/zh__PINYIN.txt locales)
make[1]: *** [debian/rules:52: override_dh_auto_build] Error 1
make[1]: Leaving directory '/home/doko/camomile-1.0.1'
make: *** [debian/rules:42: build-arch] Error 2

Bug#919470: argonaut: Non-working maintainer address

[Scott Kitterman]

Package: argonaut
Version: 1.2-2
Severity: serious
Justification: Policy 3.3

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  packa...@lists.fusiondirectory.org
retry timeout exceeded

Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;packa...@lists.fusiondirectory.org
Status: 5.0.0

argonaut_1.2.3-1_source.changes uploaded successfully to localhost
along with the files:
  argonaut_1.2.3-1.dsc
  argonaut_1.2.3.orig.tar.gz
  argonaut_1.2.3.orig.tar.gz.asc
  argonaut_1.2.3-1.debian.tar.xz
  argonaut_1.2.3-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

A working maintainer address is required.  Please either change the
maintainer address or get this one fixed.

Scott K

Bug#918436: marked as done (node-groove: FTBFS (ld: cannot find -lnode))

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 11:40:52 +
with message-id 
and subject line Bug#918436: fixed in node-groove 2.5.1-1
has caused the Debian Bug report #918436,
regarding node-groove: FTBFS (ld: cannot find -lnode)
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.)


-- 
918436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-groove
Version: 2.5.0-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with nodejs
   dh_update_autotools_config -a
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
node-gyp configure build
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@8.11.2 | linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/usr/share/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',

[... snipped ...]

../src/encoder.cc:339:39: warning: 'void node::FatalException(const 
v8::TryCatch&)' is deprecated: Use FatalException(isolate, ...) 
[-Wdeprecated-declarations]
 node::FatalException(try_catch);
   ^
In file included from /usr/include/nodejs/src/node_buffer.h:25,
 from ../src/encoder.cc:1:
/usr/include/nodejs/src/node.h:338:29: note: declared here
 inline void FatalException(const v8::TryCatch& try_catch) {
 ^~
/usr/include/nodejs/src/node.h:87:42: note: in definition of macro 
'NODE_DEPRECATED'
 __attribute__((deprecated(message))) declarator
  ^~
../src/encoder.cc: In static member function 'static 
Nan::NAN_METHOD_RETURN_TYPE GNEncoder::Detach(Nan::NAN_METHOD_ARGS_TYPE)':
../src/encoder.cc:367:31: warning: cast between incompatible function types 
from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' 
{aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
 (uv_after_work_cb)DetachAfter);
   ^~~
In file included from /usr/include/nodejs/src/node.h:63,
 from /usr/include/nodejs/src/node_buffer.h:25,
 from ../src/encoder.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nodejs/src/node_object_wrap.h:85:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9253:16: warning: cast between 
incompatible function types from 
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void 
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, 
v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename 
v8::WeakCallbackInfo::Callback = void (*)(const 
v8::WeakCallbackInfo&)]':
/usr/include/nan_object_wrap.h:66:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9253:16: warning: cast between 
incompatible function types from 
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const 
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
  SOLINK_MODULE(target) Release/obj.target/groove.node
/usr/bin/ld: cannot find -lnode
collect2: error: ld returned 1 exit status
make[2]: *** [groove.target.mk:141: Release/obj.target/groove.node] Error 1
make[2]: Leaving directory '/<>/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit 
(/usr/share/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit 
(internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.0-8-amd64
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /<>
gyp ERR! node -v v8.11.2
gyp ERR! 

Bug#919419: yatex: hangs while installing along xemacs21

[Satoru KURASHIKI]

hi,

On Wed, Jan 16, 2019 at 4:18 AM Andreas Beckmann  wrote:
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
>
> If yatex is installed in a piuparts chroot that has already xemacs21
> installed, the installation will hand infinitely (until it is killed
> by a timeout). All processes are idle, there does not seem to be a busy
> loop involved:
>
> root  9236 32750  0 18:28 pts/000:00:00 /usr/bin/dpkg 
> --force-unsafe-io --status-fd 19 --configure --pending
> root 11033  9236  0 18:28 pts/000:00:00 /bin/sh 
> /var/lib/dpkg/info/yatex.postinst configure
> root 11035 11033  0 18:28 pts/000:00:00 /usr/bin/perl -w 
> /usr/lib/emacsen-common/emacs-package-install --postinst yatex
> root 11057 11035  0 18:28 pts/000:00:00 [emacs-package-i] 
> root 11148 11035  0 18:28 pts/000:00:00 /bin/bash -e 
> /usr/lib/emacsen-common/packages/install/yatex xemacs21
> root 11151 11148  0 18:28 pts/000:00:00 /bin/bash -e 
> /usr/lib/emacsen-common/packages/install/yatex xemacs21
> root 11152 11151  0 18:28 pts/000:00:00 xemacs21 -batch -no-site-file 
> -no-init-file -l ./lp.el -e bcf-and-exit comment.el yatex.el yatexadd.el 
> yatexgen.el yatexenv.el yatexlib.el yatexprc.el yatexmth.el yatexhks.el 
> yatexhlp.el yatexm-o.el yatexsec.el yatexhie.el yahtml.el yatexpkg.el
> root 11153 11151  0 18:28 pts/000:00:00 gzip -9qf

My local chroot doesn't reproduce this behavior, so I don't grab the
problem for now.
(chroot -> apt install xemacs21 -> apt install yatex -> apt finiched
successfully)

Anyway, I don't want be bothered by xemacs, I'll consider to exclude
(or maybe conflict) xemacs21 from its dependency.

regards,
-- 
KURASHIKI Satoru

Bug#869896: marked as done (backports.ssl-match-hostname should be removed for buster)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 11:34:24 +0100
with message-id 
and subject line Let's keep the package for Buster
has caused the Debian Bug report #869896,
regarding backports.ssl-match-hostname should be removed for 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.)


-- 
869896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:backports.ssl-match-hostname
Version: 3.5.0.1-1
Severity: important
Tags: sid buster

The python3 and python2 versions already have that fix (and had it in stretch
too).  This package should  be removed for the buster release.
--- End Message ---
--- Begin Message ---
Hi,

In the python-docker, the dependency was removed, then re-added because
it just broke. so it doesn't look like we can get rid of this package.

To me, it looks like we must keep the package for Buster, and then
remove it completely from Debian after Buster is released, together with
the Python 2 removal. Therefore, I'm closing this bug to allow the
package to migrate to Buster.

If I'm mistaking, please let me know, then there's still time until the
Buster freeze to fix things.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#919421: marked as done (src:g810-led: FTBFS when /usr/bin/systemd-run isn't available)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 12:25:32 +0200
with message-id <20190116102531.GG32397@localhost>
and subject line Fixed in 0.3.1-2
has caused the Debian Bug report #919421,
regarding src:g810-led: FTBFS when /usr/bin/systemd-run isn't available
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.)


-- 
919421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:g810-led
Version: 0.3.1-1
Severity: serious
Justification: ftbfs

Dear Maintainer,

g810-led FTBFS when /usr/bin/systemd-run isn't available.

Regards,

The Maintainer


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

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

g810-led (0.3.1-2) unstable; urgency=medium

  * Avoid failing the build when systemd isn’t installed.
...
 -- Stephen Kitt   Tue, 15 Jan 2019 23:16:52 +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#918288: marked as done (nipype build depends on python-nipy that is currently not in buster)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 12:15:55 +0200
with message-id <20190116101555.GF32397@localhost>
and subject line python-nipy is back in buster
has caused the Debian Bug report #918288,
regarding nipype build depends on python-nipy that is currently not 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.)


-- 
918288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nipype
Version: 1.1.3-1
Severity: serious
Tags: ftbfs
Control: block -1 by 906388

nipype build depends on python-nipy that is currently
not in buster due to #906388.
--- End Message ---
--- Begin Message ---
python-nipy is back in buster.

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#869896: Not to be removed from buster: let's close this bug?

[Thomas Goirand]

Hi Felipe,

I really would like to have this bug fixed quickly, as we're dangerously
approaching the freeze, and some of my key (OpenStack) packages are in
danger here.

So, Felipe, do I understand well that this bug can be closed without any
further action? Or is there anything that shall be done?

I'd very much would like to help, and I do have the time to work on
this, as long as we agree on what to do. So please let me know your
thoughts ASAP.

Cheers,

Thomas Goirand (zigo)