Bug#906623: heimdal: FTBFS in buster/sid (hcrypto/engine.h: No such file or directory)

[Brian May]

Santiago Vila  writes:

> make[3]: Entering directory '/<>/heimdal-7.5.0+dfsg/lib/hcrypto'
>   CC   test_rand.o
> In file included from test_rand.c:42:
> rand.h:46:10: fatal error: hcrypto/engine.h: No such file or directory
>  #include 
>   ^~
> compilation terminated.
> make[3]: *** [Makefile:2060: test_rand.o] Error 1
> make[3]: Leaving directory '/<>/heimdal-7.5.0+dfsg/lib/hcrypto'
> make[2]: *** [Makefile:565: all-recursive] Error 1
> make[2]: Leaving directory '/<>/heimdal-7.5.0+dfsg/lib'
> make[1]: *** [Makefile:613: all-recursive] Error 1
> make[1]: Leaving directory '/<>/heimdal-7.5.0+dfsg'
> dh_auto_build: make -j1 returned exit code 2
> make: *** [debian/rules:7: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 

I simply cannot reproduce this error.

Are you sure you didn't accidentally delete the supplied
./lib/hcrypto/engine.h file?

Regards
-- 
Brian May 

Bug#907528: synergy: low grade TLS certificate generation, now unusable in unstable

[duck]

Package: synergy
Version: 1.8.8-stable+dfsg.1-1.1
Severity: grave
Tags: security


Quack,

With recent openssl upgrade (1.1.0h-4 -> 1.1.1~~pre9-1) the client fails 
to connect with error routines:SSL_CTX_use_certificate:ee key too small.


The following script is used to generate the key: 
/usr/share/synergy/gen_ssl_pem.sh
This script creates a 1024 bits RSA key, which is too small to be 
secure.

This means it is security issue in all Debian suites.

Regards.

--
Marc Dequènes

Bug#907488: gitlab: post-inst fails: Could not find gem 'rugged (~> 0.26.0)'

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 28 10:43:53 PM IST, Pikrass  wrote:
>Package: gitlab
>Version: 10.6.5+dfsg-2
>Severity: serious
>
>Dear Maintainer,
>
>The post-inst script consistently fails for me with unstable's current
>gitlab package. I tested this with two systems (one buster/sid and one
>sid).


It is a known issue, the version in unstable is broken. It is fixed in 
experimental. I'm waiting for protobuf and grpc versions in experimental to 
reach unstable. Also new gitlab versions are stuck in NEW because of 
gitlab-common binary package was added.

If you want a working version, use people.debian.org/~praveen/gitlab until we 
fix this situation.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#907522: pango1.0: different results on i386 when pango is built with meson

[Jeremy Bicha]

Source: pango1.0
Version: 1.42.4-2
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/pango/issues/287
X-Debbugs-CC: seb...@debian.org

Let's keep this package from migrating to testing until this issue is fixed.

See the GNOME bug for more details.

I uploaded this with meson now because I forgot that the bug only
affected i386 (I only checked the amd64 autopkgtest this time before
uploading), and because pango in git master has dropped autotools
support so there is pressure for us to be ready for meson.

Thanks,
Jeremy Bicha

Processed: your mail

[Debian Bug Tracking System]

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

> block 907239 by 907520
Bug #907239 [src:ldc] ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 
64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit 
long double
907239 was not blocked by any bugs.
907239 was blocking: 904275
Added blocking bug(s) of 907239: 907520
>
End of message, stopping processing here.

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

Bug#907358: ncbi-vdb: fix broken library on i386

[Steve Langasek]

On Tue, Aug 28, 2018 at 09:38:50PM +0200, Andreas Tille wrote:
> > Also, this broken library package would have been detectable at build time
> > if you were building with -Wl,-z,defs in LDFLAGS, as that would have
> > prevented ever generating a shared library with missing symbols.  That's a
> > good idea to do anyway, but in particular it would mean that if you didn't
> > want to support i386 anymore, you could just add this to build flags and not
> > have to worry about changing the architecture list explicitly.

> So I did but was running into new problems which are caused by the hand
> craftet build system (yes, I tried to convince upstream to use some of
> the usual candidates but failed :-((( ).  I was able to add some missing
> libs in pbuilder chroot but whatever trick I try[1] the build system
> always constructs a different command line than I tested inside the
> pbuilder chroot.

> Do you have any idea to stop this insane messing up with library options?

> [1] 
> https://salsa.debian.org/med-team/ncbi-vdb/blob/master/debian/patches/fix_linking.patch

Failure I see in a local build is:

Try to add extra libs to LDFLAGS ... unfortunately this fails as well
CMD=gcc -shared -o 
/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libkdf5.so.2.9.2 
-Wl,-soname,libkdf5.so.2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-Wl,-z,defs -Wl,--as-needed -g-ghdf5dir.pic.o hdf5file.pic.o 
hdf5arrayfile.pic.o 
-L/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib 
-L/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/ilib -lhdf5_serial 
-lz -lmbedx509 -lmbedtls -lmbedcrypto -Wl,-Bstatic -Wl,-whole-archive -lklib 
-lkfs -Wl,-no-whole-archive -Wl,-Bdynamic -lbz2 -ldl -lpthread -lm -lkproc 
-lkfs -lkdb -lkns -lkfg
gcc -shared -o 
/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libkdf5.so.2.9.2 
-Wl,-soname,libkdf5.so.2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-Wl,-z,defs -Wl,--as-needed -g-ghdf5dir.pic.o hdf5file.pic.o 
hdf5arrayfile.pic.o 
-L/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib 
-L/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/ilib -lhdf5_serial 
-lz -lmbedx509 -lmbedtls -lmbedcrypto -Wl,-Bstatic -Wl,-whole-archive -lklib 
-lkfs -Wl,-no-whole-archive -Wl,-Bdynamic -lbz2 -ldl -lpthread -lm
/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/ilib/libklib.a(hashfile.pic.o):
 In function `map_calloc':
/tmp/ncbi-vdb/libs/klib/hashfile.c:288: undefined reference to `KLockAcquire'
/tmp/ncbi-vdb/libs/klib/hashfile.c:321: undefined reference to `KLockUnlock'
/tmp/ncbi-vdb/libs/klib/hashfile.c:328: undefined reference to `KLockUnlock'
[...]

When using -Wl,--as-needed, each object needs to be listed on the
commandline /after/ those objects that use it.

A correct commandline would be:

gcc -shared -o 
/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libkdf5.so.2.9.2 
-Wl,-soname,libkdf5.so.2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-Wl,-z,defs -Wl,--as-needed -g-ghdf5dir.pic.o hdf5file.pic.o 
hdf5arrayfile.pic.o 
-L/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib 
-L/tmp/ncbi-vdb/debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/ilib -lhdf5_serial 
-lz -Wl,-Bstatic -Wl,-whole-archive -lklib -lkfs -Wl,-no-whole-archive 
-Wl,-Bdynamic -lbz2 -ldl -lpthread -lm -lkfs -lkq -lkproc -lkdb -lkns -lkfg 
-lksproc -lmbedx509 -lmbedtls -lmbedcrypto -lz

So this seems to be sufficient:

CMD="$CMD -lkfs -lkq -lkproc -lkdb -lkns -lkfg -lksproc -lmbedx509 
-lmbedtls -lmbedcrypto -lz"

Though there is another similar error when trying to link libdiagnose.so
later.

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


signature.asc
Description: PGP signature

Processed: tagging 902220

[Debian Bug Tracking System]

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

> tags 902220 + buster sid
Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed (with 1 error): Correct the found/fixed versions and severity

[Debian Bug Tracking System]

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

> bts tags 902220 buster sid
Unknown command or malformed arguments to command.
> severity 902220 serious
Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev
Severity set to 'serious' from 'normal'
> fixed 902220 1:2.2+git20170823-7
Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev
Marked as fixed in versions aspectc++/1:2.2+git20170823-7.
> found 902220 1:2.2+git20170823-8
Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev
Marked as found in versions aspectc++/1:2.2+git20170823-8.
> thanks
Stopping processing here.

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

Processed: block 907015 with 907518

[Debian Bug Tracking System]

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

> block 907015 with 907518
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 898804 900982 898800 907022 900156 897643 900153 907339 
907055 907491 906997 907340 907033 897652 900157 897651 907219 907118 907427 
898805 895959 900158 900159 907135 898807 891665 907215 900154 906955 907031 
898802 907278 907216 906981 907049 898801 891625 907028 907079 907168 898803 
900152 900160 900161 897658
907015 was not blocking any bugs.
Added blocking bug(s) of 907015: 907518
> thanks
Stopping processing here.

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

Bug#906972: marked as done (aspectc++: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 23:34:25 +
with message-id 
and subject line Bug#906972: fixed in aspectc++ 1:2.2+git20170823-8
has caused the Debian Bug report #906972,
regarding aspectc++: FTBFS in buster/sid
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.)


-- 
906972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aspectc++
Version: 1:2.2+git20170823-7
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]

dh_testdir
dh_testroot
dh_clean build-*stamp binary-*stamp puma.config
# cleaning up source directories:
/usr/bin/make -s -C Puma cleanall
Making tests clean...
Making parser clean...
Making annotator clean...
Making macronames clean...
Making sync clean...
Making ccparser clean...
Making cparser clean...
Making docs clean...
Making completely clean...
# The clang frontend adds additional tests that need cleaning
# so far, no tests are excluded by using the Clang frontend
/usr/bin/make -s -C AspectC++ cleanall FRONTEND=Clang 
LLVMCONF=/usr/bin/llvm-config-4.0
config/clang.mk:5: *** FRONTEND is 'Clang', but LLVMCONF 
(/usr/bin/llvm-config-4.0) is not found.  Stop.
make: *** [debian/rules:92: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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: aspectc++
Source-Version: 1:2.2+git20170823-8

We believe that the bug you reported is fixed in the latest version of
aspectc++, 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.
Reinhard Tartler  (supplier of updated aspectc++ 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: Sun, 26 Aug 2018 10:17:28 -0400
Source: aspectc++
Binary: aspectc++ libpuma-dev libpuma-doc
Architecture: source
Version: 1:2.2+git20170823-8
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Description:
 aspectc++  - aspect-oriented programming extension for C++
 libpuma-dev - C/C++/AspectC++ Scanner and Parsers
 libpuma-doc - C/C++/AspectC++ Scanner and Parsers
Closes: 902220 906972
Changes:
 aspectc++ (1:2.2+git20170823-8) unstable; urgency=medium
 .
   * Revert "Build depend on llvm-dev (Closes: #902220)" (Closes: #906972)
Checksums-Sha1:
 cbef77a8d9e67ca4091afe05220a7470f86a6d3c 2318 aspectc++_2.2+git20170823-8.dsc
 66c8e9ed4bbb1bdb222325393a1efb55263faee2 14768 
aspectc++_2.2+git20170823-8.debian.tar.xz
Checksums-Sha256:
 fd52dd67263b3d1e2db44901eb33dd4a772c97766393a6a88c60c9d6bb355da8 2318 
aspectc++_2.2+git20170823-8.dsc
 8d799dc1dbd47683a3fbc8b5be0095f833a6cf40b74ef7e01acc680b53f76a31 14768 
aspectc++_2.2+git20170823-8.debian.tar.xz
Files:
 b8d0c24c1b00740ba97fa10599e3962c 2318 devel optional 
aspectc++_2.2+git20170823-8.dsc
 168f44c04fa593d463cb0e5ac6ca0d25 14768 devel optional 
aspectc++_2.2+git20170823-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEE6n5rckvJ+/LRcetya3IL6cXPbZ4FAluF2G8UHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQa3IL6cXPbZ5EAQ/9G2f/u9Ox43NhzZfp/lVXk0ePWJhf
w2tDuKuIAd/kn2DxwwdeLGcJZjsI89CGaaV1pQweVE8GNrj6qT4fbtcnIUjgKhUn
XqkdxP69Nc/Lw9bMPmiFaTk2vcFh3EkhWBHl4XA0ab3BRRVL9WCD1j5Tc2xkEr8l
397M1DJiyiLxX/UZBDH4/bYCoWYRQcqa5ghXXGfaqlPEqcP/gr1NW24NDifKlYXN
R6bdKbaXEzCFrmRn+mMirUngU3Kl5/ulR7hrt2EiyzJyZF/s7TMT0Bhp5g4mk+OH
ZNPrQOtNE1E5/xswNsWSIPDzvr6xOkls+K41K6xu115aeoN7pRgAhPBpwMv+pzXS
KkC8HF3sK4MlRv7MoofXDe021fieik9tKkNYUUgmGKzlNJH7FRPboDPvW+osl8o1
xiz

Processed: bug 906977 is forwarded to https://cgit.kde.org/parley.git/commit/?id=f57328e, tagging 906977

[Debian Bug Tracking System]

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

> forwarded 906977 https://cgit.kde.org/parley.git/commit/?id=f57328e
Bug #906977 [src:parley] parley: FTBFS in buster/sid ('QItemSelection' does not 
name a type)
Set Bug forwarded-to-address to 
'https://cgit.kde.org/parley.git/commit/?id=f57328e'.
> tags 906977 + patch fixed-upstream
Bug #906977 [src:parley] parley: FTBFS in buster/sid ('QItemSelection' does not 
name a type)
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 906971 is forwarded to https://cgit.kde.org/apper.git/commit/?id=d8960ea, tagging 906971

[Debian Bug Tracking System]

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

> forwarded 906971 https://cgit.kde.org/apper.git/commit/?id=d8960ea
Bug #906971 [src:apper] apper: FTBFS in buster/sid (invalid use of incomplete 
type 'class QButtonGroup')
Set Bug forwarded-to-address to 
'https://cgit.kde.org/apper.git/commit/?id=d8960ea'.
> tags 906971 + patch fixed-upstream
Bug #906971 [src:apper] apper: FTBFS in buster/sid (invalid use of incomplete 
type 'class QButtonGroup')
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.

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

Processed: ghostscript breaks cups autopkgtest: test times out

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #907493 [src:ghostscript, src:cups] ghostscript breaks cups autopkgtest: 
test times out
Severity set to 'serious' from 'normal'
> found -1 ghostscript/9.22~dfsg-3
Bug #907493 [src:ghostscript, src:cups] ghostscript breaks cups autopkgtest: 
test times out
Marked as found in versions ghostscript/9.22~dfsg-3.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 907505 https://github.com/logrotate/logrotate/issues/225
Bug #907505 [logrotate] /bin/gzip: error while loading shared libraries: cannot 
restore segment prot after reloc
Set Bug forwarded-to-address to 
'https://github.com/logrotate/logrotate/issues/225'.
>
End of message, stopping processing here.

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

Bug#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

[Felipe Sateler]

On Sat, Aug 11, 2018 at 9:54 AM Meinolf Gödde  wrote:

> The problem is back again. So i hope it helps.
>

The log file is empty :(.


Anyway, are you using MATE? Another bug with the same symptoms seems to be
caused by the mate volume manager (see bug #906622).

Saludos
-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#907505: /bin/gzip: error while loading shared libraries: cannot restore segment prot after reloc

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #907505 [logrotate] /bin/gzip: error while loading shared libraries: cannot 
restore segment prot after reloc
Severity set to 'grave' from 'normal'
> tags -1 pending
Bug #907505 [logrotate] /bin/gzip: error while loading shared libraries: cannot 
restore segment prot after reloc
Added tag(s) pending.

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

Processed: Re: debootstrap - fails in docker environment

[Debian Bug Tracking System]

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

> tags 905165 +moreinfo
Bug #905165 [debootstrap] debootstrap - fails in docker environment
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#907157: cura-engine: FTBFS in buster/sid (Error copying directory)

[Juhani Numminen]

Dear maintainer,

Applying this patch might fix the FTBFS. I haven't tried myself yet.

https://github.com/Ultimaker/CuraEngine/commit/5aad55bf67e52ce5bdb27a3925af8a4cab441b38#diff-af3b638bc2a3e6c650974192a53c7291


Cheers,
Juhani

Processed: block 907015 with 907278

[Debian Bug Tracking System]

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

> block 907015 with 907278
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 900153 907340 900156 907033 900982 907168 895959 897658 
898805 900160 898801 907427 907215 907049 897651 900157 898804 900152 900158 
897643 907135 898802 907055 907022 907339 891665 898803 891625 898800 900161 
906997 907031 898807 907079 900159 906981 897652 907216 907219 906955 907491 
907028 907118 900154
907015 was not blocking any bugs.
Added blocking bug(s) of 907015: 907278
> thanks
Stopping processing here.

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

Processed: severity of 907278 is serious

[Debian Bug Tracking System]

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

> severity 907278 serious
Bug #907278 [python-httplib2] [python-httplib2] Certificate verification fails 
without apparent reason for some CAs
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: block 907491 with 907278

[Debian Bug Tracking System]

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

> block 907491 with 907278
Bug #907491 [goobook] goobook fails to authenticate
907491 was not blocked by any bugs.
907491 was blocking: 907015
Added blocking bug(s) of 907491: 907278
> thanks
Stopping processing here.

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

Processed: severity of 867666 is serious

[Debian Bug Tracking System]

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

> severity 867666 serious
Bug #867666 [libcurlpp-dev] libcurlpp-dev should depend on libcurl-dev
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#907491: goobook fails to authenticate

[Kurt Roeckx]

This is most likely caused by google sending invalid certificates
if you talk TLS 1.3 but don't send the SNI extention. See
https://wiki.openssl.org/index.php/TLS1.3#Server_Name_Indication

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

[Vincent Danjean]

  Hi,

Le 28/08/2018 à 18:51, Nick Smallbone a écrit :
> Package: hgsvn
> Version: 0.1.8-1.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After installing hgsvn, I tried to run hgimportsvn but was greeted
> with:
> 
> % hgimportsvn
> zsh: command not found: hgimportsvn
> 
> A closer look reveals that the package does not actually install
> hgsvn. For some reason, it only includes the manpages and
> documentation. Here is the output of dpkg -L hgsvn - notice the empty
> /usr/bin directory:

Whaou! The package is in this state since several years
(as this is the version currently in stretch), since 2015-08-22
exactly (upload of the NMU version). And this is the first
bug report.

  I do not use it anymore and, as the upstream website changed,
I just see I'm several version late.


  I will try to update/redo this package. Any help is welcome.

  Regards,
Vincent

-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#906375: libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types)

[Jochen Sprickerhof]

Hi,

I looked into this, but haven't found an easy solution.

* Santiago Vila  [2018-08-17 11:20]:

[ERROR] 
/<>/src/main/java/com/itextpdf/text/pdf/security/MakeXmlSignature.java:[443,22]
 method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be 
applied to given types;
 required: 
org.apache.jcp.xml.dsig.internal.dom.XmlWriter,java.lang.String,javax.xml.crypto.XMLCryptoContext
 found: 
org.w3c.dom.Node,org.w3c.dom.Node,java.lang.String,javax.xml.crypto.dsig.dom.DOMSignContext
 reason: actual and formal argument lists differ in length


The problem is that libitext5-java is using an internal API of 
libxml-security-java here which was reworked in version 2. Discussion 
and patch can be found here:


https://issues.apache.org/jira/browse/SANTUARIO-349

Problem is that it introduces a new class Marshaller, used to generate 
the same result as needed by libitext5-java but it's not public, so we 
can't access it easily.


Itext has moved on to version 7 in the meantime, not use the internal 
API, as far as I've seen. But it has a different API itself, so we would 
have to port all depending packages to it (which are figtree, hibiscus 
and umlet).


I'm not sure if I will find time for this soon, so help would be very 
welcome here.


As a quick fix we could probably hack around the visibility modifiers of 
Marshaller, but I guess that would be rather ugly. Just mentioning it 
for completeness.


* Andreas Tille  [2018-08-25 17:44]:

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.itextpdf:itextpdf:5.5.13: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it 
before. and 'parent.relativePath' points at no local POM @ line 5, column 11
[FATAL] Non-resolvable parent POM for com.itextpdf:itext-pdfa:5.5.13: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it 
before. and 'parent.relativePath' points at no local POM @ line 5, column 11
[FATAL] Non-resolvable parent POM for com.itextpdf:itext-xtra:5.5.13: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it 
before. and 'parent.relativePath' points at no local POM @ line 5, column 11
[FATAL] Non-resolvable parent POM for com.itextpdf.tool:xmlworker:5.5.13: 
Cannot access central (https://repo.maven.apache.org/maven2) in offline mode 
and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded 
from it before. and 'parent.relativePath' points at no local POM @ line 5, 
column 11
@
[ERROR] The build could not read 4 projects -> [Help 1]


I've looked into this as well and have some patches to make it work up 
to the same error this bug is about. If you still want to have them, I 
can send a pull request.


Cheers Jochen


signature.asc
Description: PGP signature

Processed: Re: Bug#907358: ncbi-vdb: fix broken library on i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #907358 [ncbi-vdb] ncbi-vdb: fix broken library on i386
Added tag(s) help.

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

Bug#907358: ncbi-vdb: fix broken library on i386

[Andreas Tille]

Control: tags -1 help

Hi Steve,

On Sun, Aug 26, 2018 at 03:04:40PM -0700, Steve Langasek wrote:
> Package: ncbi-vdb
> Version: 2.9.1-1+dfsg-1
> Severity: grave
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu cosmic ubuntu-patch
> 
> Dear Andreas,
> 
> The libncbi-vdb2 library is broken on i386, because while it has managed to
> build, it has unresolvable references:
> ...
> It would also be perfectly reasonable to drop i386 as a supported
> architecture for ncbi-vdb if you prefer; but I suggest you then make sure to
> actually do this, rather than shipping a broken library package on i386.

Thanks to your patch I decided to leave i386 for the moment but its
definitely a candidate for removal.

> Also, this broken library package would have been detectable at build time
> if you were building with -Wl,-z,defs in LDFLAGS, as that would have
> prevented ever generating a shared library with missing symbols.  That's a
> good idea to do anyway, but in particular it would mean that if you didn't
> want to support i386 anymore, you could just add this to build flags and not
> have to worry about changing the architecture list explicitly.

So I did but was running into new problems which are caused by the hand
craftet build system (yes, I tried to convince upstream to use some of
the usual candidates but failed :-((( ).  I was able to add some missing
libs in pbuilder chroot but whatever trick I try[1] the build system
always constructs a different command line than I tested inside the
pbuilder chroot.

Do you have any idea to stop this insane messing up with library options?


[1] 
https://salsa.debian.org/med-team/ncbi-vdb/blob/master/debian/patches/fix_linking.patch

-- 
http://fam-tille.de

Processed: found 907491 in 1.9-3

[Debian Bug Tracking System]

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

> found 907491 1.9-3
Bug #907491 [goobook] goobook fails to authenticate
Marked as found in versions goobook/1.9-3.
> thanks
Stopping processing here.

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

Processed: block 907015 with 907491

[Debian Bug Tracking System]

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

> block 907015 with 907491
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 900152 906997 897651 907340 900153 898800 907219 907215 
897643 891625 898801 900160 900154 900982 907055 898805 900161 907339 906981 
907031 900159 895959 898807 898802 900158 897652 906955 897658 907028 907216 
907135 900156 898803 900157 907022 891665 907118 907427 907168 907049 907033 
907079 898804
907015 was not blocking any bugs.
Added blocking bug(s) of 907015: 907491
> thanks
Stopping processing here.

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

Processed: affects 907486

[Debian Bug Tracking System]

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

> affects 907486 libpam-systemd
Bug #907486 [systemd-shim] libpam-systemd: Depends: systemd-shim (>= 10-4~) but 
it is not going to be installed
Bug #903295 [systemd-shim] libpam-systemd: Depends: systemd-shim (>= 10-4~) but 
it is not going to be installed
Added indication that 907486 affects libpam-systemd
Added indication that 903295 affects libpam-systemd
> thanks
Stopping processing here.

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

Bug#907496: libcurlpp0: Always fails with "No URL set!"

[Ted Percival]

Package: libcurlpp0
Version: 0.8.1-2+b1
Severity: grave
Justification: renders package unusable

libcurlpp0 appears to always fail with a "No URL set!" error message.
I only tested the "Easy" API.

For example even the first example in its repo

doesn't work:

$ g++ -Wall example00.cpp `curlpp-config --cflags --libs` `curl-config --cflags 
--libs`
$ ./a.out 
No URL set!

I recompiled libcurlpp using both 7 & 8[1] and when linking the example program 
to
the new build it works fine (both static & dynamic libs). So I'm not sure where
the problem lies but even after reinstalling the Debian package I could only get
it to work with my local libcurlpp.

[1] GCC package versions:
g++-7: 7.3.0-28
g++-8: 4:8.2.0-1

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

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

Versions of packages libcurlpp0 depends on:
ii  libc6   2.27-5
ii  libcurl47.61.0-1
ii  libgcc1 1:8.2.0-4
ii  libstdc++6  8.2.0-4

libcurlpp0 recommends no packages.

libcurlpp0 suggests no packages.

-- no debconf information

Processed: severity of 907118 is serious

[Debian Bug Tracking System]

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

> severity 907118 serious
Bug #907118 [bip] error:141a318a:ssl routines:tls_process_ske_dhe:dh key too 
small
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

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

[Nick Smallbone]

Package: hgsvn
Version: 0.1.8-1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing hgsvn, I tried to run hgimportsvn but was greeted
with:

% hgimportsvn
zsh: command not found: hgimportsvn

A closer look reveals that the package does not actually install
hgsvn. For some reason, it only includes the manpages and
documentation. Here is the output of dpkg -L hgsvn - notice the empty
/usr/bin directory:

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/hgsvn
/usr/share/doc/hgsvn/changelog.Debian.gz
/usr/share/doc/hgsvn/buildinfo_all.gz
/usr/share/doc/hgsvn/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/hgimportsvn.1.gz
/usr/share/man/man1/hgpushsvn.1.gz
/usr/share/man/man1/hgpullsvn.1.gz
/usr/bin

Nick

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

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

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


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

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

Versions of packages hgsvn depends on:
ii  mercurial 4.0-1+deb9u1
ii  python2.7.13-2
ii  python-pkg-resources  33.1.1-1
ii  subversion1.9.5-1+deb9u2

hgsvn recommends no packages.

hgsvn suggests no packages.

-- no debconf information

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

[Michael Biebl]

On 8/28/18 19:59, Felipe Sateler wrote:
> On Tue, Aug 28, 2018, 14:00 Robbie Harwood  > wrote:

> This would make systemd-shim unusable.
> 
> 
> Indeed. See bugs #901404 and #901405 for things that need to be fixed in
> 10-4. Systemd-shim is currently broken, and is not working in its
> current form. 

Aside from those two bugs there is also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 which needs to
be addressed before systemd-shim is functional again.

Unfortunately we don't really have anyone still caring for the sysvinit
related bits in Debian.
So for, it has been mostly the systemd team which kept sysvinit on life
support, but we no longer have the time  for that.

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



signature.asc
Description: OpenPGP digital signature

Bug#882557: signon-ui FTBFS on amd64: SignOnUiTest::testRequestWithIndicator() Received signal 11

[Santiago Vila]

On Fri, 24 Nov 2017, Adrian Bunk wrote:

> Source: signon-ui
> Version: 0.17+15.10.20150810-2
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes signon-ui FTBFS on amd64:
> 
> https://tests.reproducible-builds.org/debian/history/signon-ui.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/signon-ui.html

This is very strange. I can't reproduce this anymore in buster.

If the reason for this is some buggy build-dependency which is now fixed,
such build-dependency (whatever it is) probably entered testing
between 2018-08-13 and 2018-08-24 (according to my build logs).

Thanks.

Processed: Re: Bug#907489: sambamba FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #907489 [src:sambamba] sambamba FTBFS
Added tag(s) help.

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

Bug#907489: sambamba FTBFS

[Andreas Tille]

Control: tags -1 help

Hi Matthias,

do you have any idea?  Its most probably connected to the
libbiod bug.

Kind regards

 Andreas.

On Tue, Aug 28, 2018 at 08:32:32PM +0300, Adrian Bunk wrote:
> Source: sambamba
> Version: 0.6.7-2
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sambamba.html
> 
> ...
> [5/74] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
> -release -wi   -of 'sambamba@exe/sambamba_sort.d.o' -c ../sambamba/sort.d
> FAILED: sambamba@exe/sambamba_sort.d.o 
> ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g -release 
> -wi   -of 'sambamba@exe/sambamba_sort.d.o' -c ../sambamba/sort.d
> /usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1845): Error: 
> read-modify-write operations are not allowed for `shared` variables. Use 
> `core.atomic.atomicOp!"+="(s, e)` instead.
> /usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1871): Error: 
> read-modify-write operations are not allowed for `shared` variables. Use 
> `core.atomic.atomicOp!"*="(e, f)` instead.
> ../sambamba/sort.d(427): Error: template instance 
> `std.numeric.normalize!(shared(float)[])` error instantiating
> ../sambamba/sort.d(265):instantiated from here: 
> `mergeSortedChunks!(compareReadNames)`
> ../sambamba/sort.d(445): Error: forward reference to inferred return type of 
> function call `function (ulong j)
> {
> return (lazy float progress)
> {
> atomicStore(merging_progress[j], progress);
> synchronized(bar) {
> bar.update(dotProduct(merging_progress, weights));
> }
> }
> ;
> }
> (i)`
> ../sambamba/sort.d(267): Error: template instance 
> `sambamba.sort.Sorter.mergeSortedChunks!(mixedCompareReadNames)` error 
> instantiating
> ../sambamba/sort.d(269): Error: template instance 
> `sambamba.sort.Sorter.mergeSortedChunks!(compareCoordinatesAndStrand)` error 
> instantiating
> [6/74] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
> -release -wi   -of 'sambamba@exe/sambamba_merge.d.o' -c ../sambamba/merge.d
> FAILED: sambamba@exe/sambamba_merge.d.o 
> ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g -release 
> -wi   -of 'sambamba@exe/sambamba_merge.d.o' -c ../sambamba/merge.d
> /usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1845): Error: 
> read-modify-write operations are not allowed for `shared` variables. Use 
> `core.atomic.atomicOp!"+="(s, e)` instead.
> /usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1871): Error: 
> read-modify-write operations are not allowed for `shared` variables. Use 
> `core.atomic.atomicOp!"*="(e, f)` instead.
> ../sambamba/merge.d(407): Error: template instance 
> `std.numeric.normalize!(shared(float)[])` error instantiating
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#907491: goobook fails to authenticate

[Sergio Mendoza]

Package: goobook
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm running debian unstable.  I have not been able to work properly with
goobook and can't find a solution for it.  It requires immediate assitance.
This is happening in all computers I have with Debian (quite a few):

sergio@izta:~$ goobook dquery sergio
Traceback (most recent call last):
  File "/usr/bin/goobook", line 11, in 
load_entry_point('goobook==1.9', 'console_scripts', 'goobook')()
  File "/usr/share/goobook/goobook/application.py", line 94, in main
args.func(config, args)
  File "/usr/share/goobook/goobook/application.py", line 130, in
do_query_details
goobk = GooBook(config)
  File "/usr/share/goobook/goobook/goobook.py", line 59, in __init__
self.cache.load()
  File "/usr/share/goobook/goobook/goobook.py", line 257, in load
self.update()
  File "/usr/share/goobook/goobook/goobook.py", line 264, in update
self.contacts = list(self._parse_contacts(gc.fetch_contacts()))
  File "/usr/share/goobook/goobook/goobook.py", line 395, in fetch_contacts
res = self._get(query)
  File "/usr/share/goobook/goobook/goobook.py", line 371, in _get
connection_type=httplib2.HTTPSConnectionWithTimeout)
  File "/usr/local/lib/python2.7/dist-packages/oauth2client/client.py", line
562, in new_request
redirections, connection_type)
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line
1608, in request
(response, content) = self._request(conn, authority, uri, request_uri,
method, body, headers, redirections, cachekey)
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line
1350, in _request
(response, content) = self._conn_request(conn, request_uri, method, body,
headers)
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line
1272, in _conn_request
conn.connect()
  File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line
1059, in connect
raise SSLHandshakeError(e)
httplib2.SSLHandshakeError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
failed (_ssl.c:726)

>

Cheers,

Sergio



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

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

Versions of packages goobook depends on:
ii  python2.7.15-3
ii  python-gdata  2.0.18+dfsg1-2
ii  python-httplib2   0.9.2+dfsg-1
ii  python-oauth2client   4.1.2-3
ii  python-pkg-resources  39.2.0-1
ii  python-setuptools 39.2.0-1
ii  python-simplejson 3.15.0-1+b1

goobook recommends no packages.

Versions of packages goobook suggests:
ii  python-keyring  13.1.0-1

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

[Michael Biebl]

Control: reassign -1 systemd-shim
Control: forcemerge 903295 -1

On 8/28/18 18:56, Robbie Harwood wrote:
> Package: libpam-systemd
> Version: 238-5
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> (This bug has been reported also against systemd-shim:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 )
> 
> libpam-systemd requires systemd-shim version >=10-4~.  No such version exists.
> 
> This would make systemd-shim unusable.
> 

sytemd-shim is currently unusable, that's why there is such a versioned
dependency. Someone needs to make a 10-4 upload for systemd-shim which
fixes the package.
Re-assigning to systemd-shim, since there is nothing that can be done
about this in libpam-systemd.


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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd-shim
Bug #907486 [libpam-systemd] libpam-systemd: Depends: systemd-shim (>= 10-4~) 
but it is not going to be installed
Bug reassigned from package 'libpam-systemd' to 'systemd-shim'.
No longer marked as found in versions systemd/238-5.
Ignoring request to alter fixed versions of bug #907486 to the same values 
previously set
> forcemerge 903295 -1
Bug #903295 [systemd-shim] libpam-systemd: Depends: systemd-shim (>= 10-4~) but 
it is not going to be installed
Bug #907486 [systemd-shim] libpam-systemd: Depends: systemd-shim (>= 10-4~) but 
it is not going to be installed
Marked as found in versions systemd-shim/10-3.
Added tag(s) buster and sid.
Merged 903295 907486

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

Processed (with 1 error): Re: Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 903295 -1
Bug #903295 [systemd-shim] libpam-systemd: Depends: systemd-shim (>= 10-4~) but 
it is not going to be installed
Unable to merge bugs because:
package of #907486 is 'libpam-systemd' not 'systemd-shim'
Failed to forcibly merge 903295: Did not alter merged bugs.


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

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

[Felipe Sateler]

Control: forcemerge 903295 -1

On Tue, Aug 28, 2018, 14:00 Robbie Harwood  wrote:

> Package: libpam-systemd
> Version: 238-5
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> (This bug has been reported also against systemd-shim:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 )
>

Merging with that report, since it is systemd-shim that needs fixing. There
is no need to file additional reports.



> libpam-systemd requires systemd-shim version >=10-4~.  No such version
> exists.
>
> This would make systemd-shim unusable.
>

Indeed. See bugs #901404 and #901405 for things that need to be fixed in
10-4. Systemd-shim is currently broken, and is not working in its current
form.

Saludos

Bug#902470: Status?

[olivier sallou]

Cool, thanks

Le mar. 28 août 2018 à 18:46, Alexandre Viau  a écrit :

> On Sat, 25 Aug 2018 19:44:12 +0200 olivier sallou 
> wrote:
> > Hi,
> > My packages have been removed from testing due to this bug.
> > Can we remove failing test and lower bug severity waiting for upstream
> fix?
>
> I have uploaded a fix.
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>

Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop

[william l-k]

Package: gnome-shell
Version: 3.28.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,


After a recent power failure lasting multiple hours, the battery backup on my
laptop ran out of power and the system shut down. Once power was restored and I
restarted the machine, I booted into a minimal GUI with black background and
x-cursor. Without gnome controls, I was unable to get a terminal from the
minimal session, so I switched to another tty. From there I was able to
troubleshoot.

None of the following solved the problem:

rebooting
update/upgrade then rebooting
merging last lvm-snapshot of the root directory
alt +f2 and then r
sudo systemctl restart gdm
killall -HUP gnome-shell
sudo systemctl restart gdm

>From GDM controls:
trying default x11 and gnome

Trying alternate kernel


The portion of the log near the times of start attempts had sections like
these:


Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Power.desktop
Aug 28 10:13:07 Username dbus-daemon[603]: [system] Activating via systemd:
service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostna
Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.XSettings.desktop
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not
connect: Connection refused
Aug 28 10:13:07 Username unknown[8630]: Cannot open display:
Aug 28 10:13:07 Username dbus-daemon[8532]: [session uid=1000 pid=8532]
Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.se
Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not
connect: Connection refused
Aug 28 10:13:07 Username unknown[8635]: Cannot open display:
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
Aug 28 10:13:07 Username org.gnome.SettingsDaemon.Mouse.desktop[8606]: Unable
to init server: Could not connect: Connection refused
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' respawning too quickly
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' respawning too qui
Aug 28 10:13:07 Username systemd[1]: Starting Time & Date Service...
Aug 28 10:13:07 Username org.gnome.SettingsDaemon.MediaKeys.desktop[8609]:
Cannot open display:
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
Aug 28 10:13:07 Username unknown[8638]: cannot open display:
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' respawning too quic
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]:
WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Wacom.desktop
Aug 28 10:13:07 Username org.gnome.SettingsDaemon.Power.desktop[8613]: Cannot
open display:
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.Power.desktop' respawning too quickly
Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Clipboard.desktop
Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Keyboard.desktop
Aug 28 10:13:07 Username org.gnome.SettingsDaemon.XSettings.desktop[8614]

Bug#907489: sambamba FTBFS

[Adrian Bunk]

Source: sambamba
Version: 0.6.7-2
Severity: serious
Tags: ftbfs

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

...
[5/74] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
-release -wi   -of 'sambamba@exe/sambamba_sort.d.o' -c ../sambamba/sort.d
FAILED: sambamba@exe/sambamba_sort.d.o 
ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g -release -wi  
 -of 'sambamba@exe/sambamba_sort.d.o' -c ../sambamba/sort.d
/usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1845): Error: 
read-modify-write operations are not allowed for `shared` variables. Use 
`core.atomic.atomicOp!"+="(s, e)` instead.
/usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1871): Error: 
read-modify-write operations are not allowed for `shared` variables. Use 
`core.atomic.atomicOp!"*="(e, f)` instead.
../sambamba/sort.d(427): Error: template instance 
`std.numeric.normalize!(shared(float)[])` error instantiating
../sambamba/sort.d(265):instantiated from here: 
`mergeSortedChunks!(compareReadNames)`
../sambamba/sort.d(445): Error: forward reference to inferred return type of 
function call `function (ulong j)
{
return (lazy float progress)
{
atomicStore(merging_progress[j], progress);
synchronized(bar) {
bar.update(dotProduct(merging_progress, weights));
}
}
;
}
(i)`
../sambamba/sort.d(267): Error: template instance 
`sambamba.sort.Sorter.mergeSortedChunks!(mixedCompareReadNames)` error 
instantiating
../sambamba/sort.d(269): Error: template instance 
`sambamba.sort.Sorter.mergeSortedChunks!(compareCoordinatesAndStrand)` error 
instantiating
[6/74] ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g 
-release -wi   -of 'sambamba@exe/sambamba_merge.d.o' -c ../sambamba/merge.d
FAILED: sambamba@exe/sambamba_merge.d.o 
ldc2 -Isambamba@exe -I. -I.. -I/usr/include/d -enable-color -O -g -release -wi  
 -of 'sambamba@exe/sambamba_merge.d.o' -c ../sambamba/merge.d
/usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1845): Error: 
read-modify-write operations are not allowed for `shared` variables. Use 
`core.atomic.atomicOp!"+="(s, e)` instead.
/usr/lib/ldc/x86_64-linux-gnu/include/d/std/numeric.d(1871): Error: 
read-modify-write operations are not allowed for `shared` variables. Use 
`core.atomic.atomicOp!"*="(e, f)` instead.
../sambamba/merge.d(407): Error: template instance 
`std.numeric.normalize!(shared(float)[])` error instantiating

Bug#907488: gitlab: post-inst fails: Could not find gem 'rugged (~> 0.26.0)'

[Pikrass]

Package: gitlab
Version: 10.6.5+dfsg-2
Severity: serious

Dear Maintainer,

The post-inst script consistently fails for me with unstable's current
gitlab package. I tested this with two systems (one buster/sid and one
sid).

Installation log follows.

8<--

Setting up gitlab (10.6.5+dfsg-2) ...
Creating/updating git user account...
Making git owner of /var/lib/gitlab...
Could not find gem 'rugged (~> 0.26.0)' in any of the gem sources listed
in your Gemfile.
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned
 error exit status 1
 Errors were encountered while processing:
  gitlab

>8--

I think the problem comes from the dependency on ruby-rugged, which is
pinned to ">= 0.26~".
The package in buster and sid is at version 0.27.4+ds-1.
The Gemfile, however, pins it to "~> 0.26.0", meaning that versions 0.27
and superior aren't acceptable.


Kind regards,
Pikrass.


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

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

Versions of packages gitlab depends on:
ii  adduser3.117
ii  asciidoctor1.5.7.1-1
ii  bc 1.07.1-2+b1
ii  bundler1.16.1-3
ii  dbconfig-pgsql 2.0.9
ii  debconf [debconf-2.0]  1.5.69
ii  exim4-daemon-heavy [mail-transport-agent]  4.91-6
ii  git1:2.18.0-1
ii  gitlab-shell   7.1.2+dfsg-2
ii  gitlab-workhorse   4.3.1+debian-1
ii  lsb-base   9.20170808
ii  nginx  1.13.12-1
ii  nginx-full [nginx] 1.13.12-1
ii  nodejs 8.11.2~dfsg-1
ii  npm5.8.0+ds-2
ii  openssh-client 1:7.7p1-4
ii  postgresql-client  10+193
ii  postgresql-client-10 [postgresql-client]   10.5-1
ii  postgresql-contrib 10+193
ii  rake   12.3.1-3
ii  redis-server   5:4.0.11-2
ii  ruby   1:2.5.1
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   5.0.0-2
ii  ruby-addressable   2.5.2-1
ii  ruby-akismet   2.0.0-1
ii  ruby-allocations   1.0.3-1+b4
ii  ruby-arel  6.0.4-1
ii  ruby-asana 0.6.0-1
ii  ruby-asciidoctor-plantuml  0.0.8-1
ii  ruby-asset-sync2.4.0-1
ii  ruby-attr-encrypted3.1.0-1
ii  ruby-babosa1.0.2-2
ii  ruby-base320.3.2-3
ii  ruby-batch-loader  1.2.1-1
ii  ruby-bcrypt-pbkdf  1.0.0-1+b2
ii  ruby-bootstrap-form2.7.0-1
ii  ruby-bootstrap-sass3.3.5.1-5.1
ii  ruby-browser   2.2.0-2
ii  ruby-carrierwave   1.2.2-1
ii  ruby-charlock-holmes   0.7.5-1+b2
ii  ruby-chronic   0.10.2-3
ii  ruby-chronic-duration  0.10.6-1
ii  ruby-commonmarker  0.17.9-1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise4.4.3-1
ii  ruby-devise-two-factor 3.0.0-2
ii  ruby-diffy 3.2.1-1
ii  ruby-doorkeeper4.4.2-1
ii  ruby-doorkeeper-openid-connect 1.3.0-1
ii  ruby-dropzonejs-rails  0.7.1-1
ii  ruby-email-reply-trimmer   0.1.6-1
ii  ruby-escape-utils  1.2.1-1+b1
ii  ruby-excon 0.60.0-1
ii  ruby-faraday   0.13.1-2
ii  ruby-fast-blank1.0.0-1+b1
ii  ruby-flipper   0.13.0-3
pn  ruby-flipper-active-record 
pn  ruby-flipper-active-support-cache-st

Bug#902470: marked as done (influxdb-python: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 17:05:16 +
with message-id 
and subject line Bug#902470: fixed in influxdb-python 5.2.0-1
has caused the Debian Bug report #902470,
regarding influxdb-python: FTBFS in buster/sid (failing tests)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.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 /<>/.pybuild/cpython2_2.7_influxdb/build/influxdb

[... snipped ...]

SKIP: Skipping server test (INFLUXDB_PYTHON_SKIP_SERVER_TESTS)
test_create_database 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_admin 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_blank_password 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_blank_username 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_database 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_user 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_user_nonexisting 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_fresh_server_no_db 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_get_list_users 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_get_list_users_empty 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_grant_privilege 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_grant_privilege_invalid 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_invalid_port_fails 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_query_fail 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_query_fail_ignore_errors 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_admin_privileges 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_privilege 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_privilege_invalid 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
SKIP: Skipping server test (INFLUXDB_PYTHON_SKIP_SERVER_TESTS)
Ensure precision is preserved when casting floats into strings. ... ok
test_make_lines (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_make_lines_unicode (influxdb.tests.test_line_protocol.TestLineProtocol) 
... ok
test_quote_ident (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_quote_literal (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_string_val_newline (influxdb.tests.test_line_protocol.TestLineProtocol) 
... ok
test_timezone (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok

==
FAIL: test_write_points_from_dataframe_with_numeric_precision 
(influxdb.tests.dataframe_client_test.TestDataFrameClient)
--
Traceback (most recent call last

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

[Robbie Harwood]

Package: libpam-systemd
Version: 238-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

(This bug has been reported also against systemd-shim:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 )

libpam-systemd requires systemd-shim version >=10-4~.  No such version exists.

This would make systemd-shim unusable.

root@hpsiddie:/home/manul# apt-get dist-upgrade -d sysvinit-core+ 
libpam-systemd+
Reading package lists... Done
Building dependency tree   
Reading state information... Done
sysvinit-core is already the newest version (2.88dsf-59.10).
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpam-systemd : Depends: systemd-shim (>= 10-4~) but it is not going to 
be installed or
   systemd-sysv but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused 
by held packages.

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

Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libpam-systemd depends on:
ii  dbus1.12.10-1
ii  libc6   2.27-5
ii  libpam-runtime  1.1.8-3.8
ii  libpam0g1.1.8-3.8
ii  systemd 238-5
ii  systemd-shim10-3

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information

Bug#902470: Status?

[Alexandre Viau]

On Sat, 25 Aug 2018 19:44:12 +0200 olivier sallou 
wrote:
> Hi,
> My packages have been removed from testing due to this bug.
> Can we remove failing test and lower bug severity waiting for upstream fix?

I have uploaded a fix.

Cheers,

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



signature.asc
Description: OpenPGP digital signature

Bug#907168: pytest-httpbin FTBFS with OpenSSL 1.1.1

[Kurt Roeckx]

On Tue, Aug 28, 2018 at 03:33:11PM +0200, Pierre-Elliott Bécue wrote:
> Le samedi 25 août 2018 à 20:34:35+0200, Kurt Roeckx a écrit :
> > This is caused by a Debian change to require a 2048 bit key by
> > default instead of a 1024 bit key. Since this is just for a test,
> > you can either just replace the certificates with larger keys,
> > or lower the security level for the test from 2 to 1. I suggest
> > you just create a new certificates.
> 
> Dear Kurt,
> 
> This would imply to do a Debian patch in upstream's source.
> 
> Do you think it's the best solution?

Upstream should fix this too. I suggest you talk to upstream and
then just apply the fix in Debian if they've fixed it.


Kurt

Bug#907483: marked as done (grub-efi-*-signed-template: `Built-Using` must refer to source packages)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 15:39:51 +
with message-id 
and subject line Bug#907483: fixed in grub2 2.02+dfsg1-6
has caused the Debian Bug report #907483,
regarding grub-efi-*-signed-template: `Built-Using` must refer to source 
packages
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.)


-- 
907483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-efi-amd64-signed-template
Version: 2.02+dfsg1-5
Severity: serious

The `Built-Using` field of the source template refers to binary
packages instead of source packages.  This makes dak reject the upload
of the signed packages:

+---
| grub-efi-amd64-signed_1+2.02+dfsg1+5_amd64.deb: Built-Using refers to 
non-existing source package grub-efi-amd64-bin (= 2.02+dfsg1-5)
+---[ grub-efi-amd64-signed_1+2.02+dfsg1+5_amd64.changes.reason ]

(same for ia32/i386 and arm64)

Ansgar
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.02+dfsg1-6

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated grub2 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, 28 Aug 2018 16:17:21 +0100
Source: grub2
Binary: grub2 grub-linuxbios grub-efi grub-common grub2-common grub-emu 
grub-emu-dbg grub-pc-bin grub-pc-dbg grub-pc grub-rescue-pc grub-coreboot-bin 
grub-coreboot-dbg grub-coreboot grub-efi-ia32-bin grub-efi-ia32-dbg 
grub-efi-ia32 grub-efi-ia32-signed-template grub-efi-amd64-bin 
grub-efi-amd64-dbg grub-efi-amd64 grub-efi-amd64-signed-template 
grub-efi-ia64-bin grub-efi-ia64-dbg grub-efi-ia64 grub-efi-arm-bin 
grub-efi-arm-dbg grub-efi-arm grub-efi-arm64-bin grub-efi-arm64-dbg 
grub-efi-arm64 grub-efi-arm64-signed-template grub-ieee1275-bin 
grub-ieee1275-dbg grub-ieee1275 grub-firmware-qemu grub-uboot-bin 
grub-uboot-dbg grub-uboot grub-xen-bin grub-xen-dbg grub-xen grub-xen-host 
grub-yeeloong-bin grub-yeeloong-dbg grub-yeeloong grub-theme-starfield 
grub-mount-udeb
Architecture: source
Version: 2.02+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: GRUB Maintainers 
Changed-By: Colin Watson 
Description:
 grub-common - GRand Unified Bootloader (common files)
 grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot version)
 grub-coreboot-bin - GRand Unified Bootloader, version 2 (Coreboot binaries)
 grub-coreboot-dbg - GRand Unified Bootloader, version 2 (Coreboot debug files)
 grub-efi   - GRand Unified Bootloader, version 2 (dummy package)
 grub-efi-amd64 - GRand Unified Bootloader, version 2 (EFI-AMD64 version)
 grub-efi-amd64-bin - GRand Unified Bootloader, version 2 (EFI-AMD64 binaries)
 grub-efi-amd64-dbg - GRand Unified Bootloader, version 2 (EFI-AMD64 debug 
files)
 grub-efi-amd64-signed-template - GRand Unified Bootloader, version 2 
(EFI-AMD64 signing template)
 grub-efi-arm - GRand Unified Bootloader, version 2 (ARM UEFI version)
 grub-efi-arm-bin - GRand Unified Bootloader, version 2 (ARM UEFI binaries)
 grub-efi-arm-dbg - GRand Unified Bootloader, version 2 (ARM UEFI debug files)
 grub-efi-arm64 - GRand Unified Bootloader, version 2 (ARM64 UEFI version)
 grub-efi-arm64-bin - GRand Unified Bootloader, version 2 (ARM64 UEFI binaries)
 grub-efi-arm64-dbg - GRand Unified Bootloader, version 2 (ARM64 UEFI debug 
files)
 grub-efi-arm64-signed-template - GRand Unified Bootloader, version 2 (ARM64 
UEFI signing template)
 grub-efi-ia32 - GRand Unified Bootloader, version 2 (EFI-IA32 version)
 grub-efi-ia32-bin - GRand Unified Bootloader, version 2 (EFI-IA32 binaries)
 grub-efi-ia32-dbg - GRand Unified Bootloader, version 2 (EFI-IA32 debug files)
 grub-efi-ia32-signed-template - GRand Unified Bootloader, version 2 (EFI-IA32 
signing template)
 grub-efi-ia64 - GRand Unified Bootloader, version 2 (IA64 version)
 grub-efi-ia64-bin - GRand Unified Bootloader, version 2 (IA64 binaries)
 grub-efi-ia64-dbg - GRand Unified Bootloader, version 2 (IA64 debug files)
 grub-emu   - GRand Unified Bootlo

Bug#903295: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed: A stopgap, probably incorrect solution

[Sabahattin Gucukoglu]

I went for an exceedingly dirty solution but one not requiring a build 
environment: unpack the systemd-shim 10-3 deb archive, the control archive 
inside, and then modify the control file.  Carefully pack it back up with tar 
and ar, then install it with dpkg -i.

I *do* hope this will get fixed. Only one package that I need depends on 
systemd via policykit, namely BRLTTY, and the polkit support is completely 
optional if you are not using brlapi.

The servers will never get systemd, of course. This is just a VM with a pure 
textmode environment. I have wondered whether I shouldn’t just bite the bullet, 
only I can’t justify it. This is not change-aversion but self-respect. Systemd 
offers nothing I can’t do better with daemontools/runit/monit. I hope this bug 
is just a bug and not a feature …



smime.p7s
Description: S/MIME cryptographic signature

Bug#907483: grub-efi-*-signed-template: `Built-Using` must refer to source packages

[Ansgar Burchardt]

Package: grub-efi-amd64-signed-template
Version: 2.02+dfsg1-5
Severity: serious

The `Built-Using` field of the source template refers to binary
packages instead of source packages.  This makes dak reject the upload
of the signed packages:

+---
| grub-efi-amd64-signed_1+2.02+dfsg1+5_amd64.deb: Built-Using refers to 
non-existing source package grub-efi-amd64-bin (= 2.02+dfsg1-5)
+---[ grub-efi-amd64-signed_1+2.02+dfsg1+5_amd64.changes.reason ]

(same for ia32/i386 and arm64)

Ansgar

Bug#906347: marked as done (disruptor: FTBFS in buster/sid (error: diamond operator is not supported in -source 6))

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 14:40:49 +
with message-id 
and subject line Bug#906347: fixed in disruptor 3.4.2-2
has caused the Debian Bug report #906347,
regarding disruptor: FTBFS in buster/sid (error: diamond operator is not 
supported in -source 6)
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.)


-- 
906347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:disruptor
Version: 3.4.2-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 --buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cp debian/pom.xml .
dh_auto_configure
mh_patchpoms -plibdisruptor-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
make[1]: Leaving directory '/<>'
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)

[... snipped ...]

[INFO] [parsing started 
SimpleFileObject[/<>/src/main/java/com/lmax/disruptor/EventPoller.java]]
[INFO] [parsing completed 0ms]
[INFO] [parsing started 
SimpleFileObject[/<>/src/main/java/com/lmax/disruptor/SleepingWaitStrategy.java]]
[INFO] [parsing completed 4ms]
[INFO] [total 303ms]
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/EventHandlerGroup.java:[60,37]
 error: diamond operator is not supported in -source 6
  (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/ConsumerRepository.java:[30,28]
 error: diamond operator is not supported in -source 6
  (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/BasicExecutor.java:[14,68]
 error: diamond operator is not supported in -source 6
  (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/WorkerPool.java:[61,50] 
error: diamond operator is not supported in -source 6
  (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/Disruptor.java:[63,84] 
error: diamond operator is not supported in -source 6
  (use -source 7 or higher to enable diamond operator)
[INFO] 5 errors 
[INFO] -
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1.887 s
[INFO] Finished at: 2018-08-15T06:31:21Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project disruptor: Compilation failure: Compilation failure: 
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/EventHandlerGroup.java:[60,37]
 error: diamond operator is not supported in -source 6
[ERROR]   (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/ConsumerRepository.java:[30,28]
 error: diamond operator is not supported in -source 6
[ERROR]   (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/dsl/BasicExecutor.java:[14,68]
 error: diamond operator is not supported in -source 6
[ERROR]   (use -source 7 or higher to enable diamond operator)
[ERROR] 
/<>/src/main/java/com/lmax/disruptor/WorkerPool.java

Bug#907001: marked as done (mina2: FTBFS in buster/sid (Plugin org.apache.xbean:maven-xbean-plugin:4.1 or one of its dependencies could not be resolved))

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 14:43:28 +
with message-id 
and subject line Bug#907001: fixed in mina2 2.0.16-3
has caused the Debian Bug report #907001,
regarding mina2: FTBFS in buster/sid (Plugin 
org.apache.xbean:maven-xbean-plugin:4.1 or one of its dependencies could not be 
resolved)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibmina2-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- -f src/pom.xml package javadoc:aggregate
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode -f 
src/pom.xml package javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

[... snipped ...]

[INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ 
mina-integration-beans ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 3 source files to 
/<>/src/mina-integration-beans/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.21.0:test (default-test) @ 
mina-integration-beans ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-bundle-plugin:3.5.0:bundle (default-bundle) @ 
mina-integration-beans ---
[INFO] 
[INFO] ---< org.apache.mina:mina-integration-xbean >---
[INFO] Building Apache MINA XBean Integration 2.0.16  [6/8]
[INFO] [ jar ]-
[WARNING] The POM for org.apache.xbean:maven-xbean-plugin:jar:4.1 is missing, 
no dependency information available
[INFO] 
[INFO] 
[INFO] Skipping Apache MINA
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache MINA 2.0.16 . SUCCESS [  0.006 s]
[INFO] Apache MINA Core ... SUCCESS [  8.557 s]
[INFO] Apache MINA APR Transport .. SUCCESS [  0.391 s]
[INFO] Apache MINA Compression Filter . SUCCESS [  0.302 s]
[INFO] Apache MINA JavaBeans Integration .. SUCCESS [  0.386 s]
[INFO] Apache MINA XBean Integration .. FAILURE [  0.001 s]
[INFO] Apache MINA OGNL Integration ... SKIPPED
[INFO] Apache MINA JMX Integration 2.0.16 . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 11.217 s
[INFO] Finished at: 2018-08-22T20:29:25Z
[INFO] 
[ERROR] Plugin org.apache.xbean:maven-xbean-plugin:4.1 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.ap

Bug#907480: altos FTBFS with gcc-arm-none-eabi 15:7-2018-q2

[Adrian Bunk]

Source: altos
Version: 1.8.6-1
Severity: serious
Tags: ftbfs

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

...
  CC  fox1ihu-altos-flash-1.8.6.elf
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: 
fox1ihu-altos-flash-1.8.6.elf section `.textram' will not fit in region `rom'
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: region `rom' 
overflowed by 18 bytes
collect2: error: ld returned 1 exit status
make[4]: *** [../../stm/Makefile-flash.defs:74: fox1ihu-altos-flash-1.8.6.elf] 
Error 1

Bug#906980: marked as done (kmer: autopkgtest fails with segfault in testing/unstable while it passes in stable)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 14:10:47 +
with message-id 
and subject line Bug#906980: fixed in kmer 0~20150903+r2013-6
has caused the Debian Bug report #906980,
regarding kmer: autopkgtest fails with segfault in testing/unstable while it 
passes in stable
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.)


-- 
906980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmer
Version: 0~20150903+r2013-4
Severity: serious
Justification: reproducibility


An autopkgtest fails with segfault in testing and unstable [1].

```
/usr/bin/../lib/atac/bin/statsGenerator -a 
/tmp/autopkgtest-lxc.epng5fx9/downtmp/autopkgtest_tmp/results/EcolivsSent.atac
-p 
/tmp/autopkgtest-lxc.epng5fx9/downtmp/autopkgtest_tmp/results/stats/EcolivsSent
-g A > 
/tmp/autopkgtest-lxc.epng5fx9/downtmp/autopkgtest_tmp/results/stats/EcolivsSent.stats

Segmentation fault
Failed to ganerate statistics.
```

Notably, that building and testing in stable were successful (I tested
it in clean chroot). JFI, I tried installing an older version of gcc on
testing, the one that is used in stable (4:6.3.0-4), and this eliminated
the segfault.

[1] https://ci.debian.net/packages/k/kmer/

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: kmer
Source-Version: 0~20150903+r2013-6

We believe that the bug you reported is fixed in the latest version of
kmer, 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.
Liubov Chuprikova  (supplier of updated kmer 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, 27 Aug 2018 11:37:43 +0200
Source: kmer
Binary: kmer libkmer-dev meryl libmeryl-dev leaff sim4db atac kmer-examples
Architecture: source amd64 all
Version: 0~20150903+r2013-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Liubov Chuprikova 
Description:
 atac   - genome assembly-to-assembly comparison
 kmer   - suite of tools for DNA sequence analysis
 kmer-examples - sample data for kmer suite of tools for DNA sequence analysis
 leaff  - biological sequence library utilities and applications
 libkmer-dev - suite of tools for DNA sequence analysis (development lib)
 libmeryl-dev - in- and out-of-core kmer counting and utilities (development 
lib)
 meryl  - in- and out-of-core kmer counting and utilities
 sim4db - batch spliced alignment of cDNA sequences to a target genome
Closes: 906980
Changes:
 kmer (0~20150903+r2013-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Liubov Chuprikova ]
   * Add autopkgtest.
   * Standards-Version: 4.2.1
   * Add a patch to fix wrong evaluation order in an expression
 Closes: #906980
 .
   [ Andreas Tille ]
   * Provide test data in new package kmer-examples to avoid duplication of
 data in two packages
Checksums-Sha1:
 b8f0fe678fe28a74a377efe932c742f3ec1956cb 2381 kmer_0~20150903+r2013-6.dsc
 23e7bc043be64fd4b405d4101e79e1775271749a 2368944 
kmer_0~20150903+r2013-6.debian.tar.xz
 30be24fabbf7cd9f5baa46ca33c62f2e280f6d9d 4188004 
atac-dbgsym_0~20150903+r2013-6_amd64.deb
 0978d34b58b839ebeac8105893368777e2ed9b44 388400 
atac_0~20150903+r2013-6_amd64.deb
 ea319feb4772fe0dfbd0d289c552755d1e7c646e 2352458 
kmer-examples_0~20150903+r2013-6_all.deb
 ba6b528d7db112f5f76ae3bc41ac1a9e0c138ba8 5148 kmer_0~20150903+r2013-6_all.deb
 1548df1ccd99db1934f455c5befd76d129f1d0fe 9792 
kmer_0~20150903+r2013-6_amd64.buildinfo
 6047d385c29c6297b27d57d2b4dfb252c105cdb2 216002 
leaff-dbgsym_0~20150903+r2013-6_amd64.deb
 1367b9e8dcc69194e7e1bc5431fe2978c73cfc7d 68788 
leaff_0~20150903+r2013-6_amd64.deb
 2d3efcb8fd4a4570c0cb3cebb550ce99acf7f41e 202206 

Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression

[Matthias Klumpp]

Am Di., 28. Aug. 2018 um 10:40 Uhr schrieb Andreas Tille :
>
> On Tue, Aug 28, 2018 at 10:12:32AM +0300, Adrian Bunk wrote:
> > Source: libbiod
> > Version: 0.1.0-5
> > Severity: serious
> > Tags: ftbfs
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbiod.html
> >
> > ...
> > [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color 
> > -O -g -release -wi -relocation-model=pic   -of 
> > 'biod@sha/bio_maf_reader.d.o' -c ../bio/maf/reader.d
> > FAILED: biod@sha/bio_maf_reader.d.o
> > ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g 
> > -release -wi -relocation-model=pic   -of 'biod@sha/bio_maf_reader.d.o' -c 
> > ../bio/maf/reader.d
> > ../bio/maf/reader.d(40): Deprecation: struct `std.stdio.File.ByLine!(char, 
> > char).ByLine` is deprecated - Use .byLine
> > ../bio/maf/reader.d(53): Error: cannot implicitly convert expression 
> > `this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, char)` 
> > to `ByLine!(char, char)`
> > ../bio/maf/reader.d(53):`this._lines = 
> > this._f.byLine(cast(Flag)true, '\x0a')` is the first assignment of 
> > `this._lines` therefore it represents its initialization
> > ../bio/maf/reader.d(53):`opAssign` methods are not used for 
> > initialization, but for subsequent assignments
> > [

Looks like an upstream issue - have you filed a bug there already?

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

Bug#907168: pytest-httpbin FTBFS with OpenSSL 1.1.1

[Pierre-Elliott Bécue]

Le samedi 25 août 2018 à 20:34:35+0200, Kurt Roeckx a écrit :
> This is caused by a Debian change to require a 2048 bit key by
> default instead of a 1024 bit key. Since this is just for a test,
> you can either just replace the certificates with larger keys,
> or lower the security level for the test from 2 to 1. I suggest
> you just create a new certificates.

Dear Kurt,

This would imply to do a Debian patch in upstream's source.

Do you think it's the best solution?

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Processed: Fix the version information

[Debian Bug Tracking System]

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

> found 903718 0.2.1-1
Bug #903718 [gplaycli] gplaycli currently unusable in 
stable/backport/testing/unstable
Marked as found in versions gplaycli/0.2.1-1.
> fixed 903718 3.23+ds-1
Bug #903718 [gplaycli] gplaycli currently unusable in 
stable/backport/testing/unstable
Marked as fixed in versions gplaycli/3.23+ds-1.
> thanks
Stopping processing here.

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

Bug#907358: ncbi-vdb: fix broken library on i386

[Adrian Bunk]

On Sun, Aug 26, 2018 at 03:04:40PM -0700, Steve Langasek wrote:
>...
> It would also be perfectly reasonable to drop i386 as a supported
> architecture for ncbi-vdb if you prefer; but I suggest you then make sure to
> actually do this, rather than shipping a broken library package on i386.
>...

Additionally, there is a baseline violation on i386:
https://sources.debian.org/src/ncbi-vdb/2.9.1-1+dfsg-1/debian/patches/add_-msse2.patch/

The userbase of this package on i386 is likely zero, so setting 
  Architecture: amd64
would IMHO be the best way forward.

> Cheers,

cu
Adrian

-- 

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

Bug#893817: salt-common: fails to install with Python 3.7

[Nicolas Braud-Santoni]

tag 904654 + upstream fixed-upstream
forward 904654 https://github.com/saltstack/salt/issues/48556

tag 893817 - fixed-upstream
forward 893817 https://github.com/saltstack/salt-jenkins/issues/995
thanks


Hi,

Just updating the bugs metadata  ;)

#904654 is fixed in upstream's 2018.3.3, to be released soon,
but #893817 still isn't fixed under Python 3  :(


Best,

  nicoo

On Fri, Aug 24, 2018 at 03:08:24PM +0200, Daniel Dehennin wrote:
> Hello.
> 
> I think the best thing to do is to update to the latest version
> 
> https://github.com/saltstack/salt/issues/48556
> 
> Regards.
> -- 
> Daniel Dehennin
> Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
> Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF




signature.asc
Description: PGP signature

Processed (with 2 errors): Re: salt-common: fails to install with Python 3.7

[Debian Bug Tracking System]

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

> tag 904654 + upstream fixed-upstream
Bug #904654 [salt-common] salt-common: fails to install with Python 3.7
Added tag(s) fixed-upstream and upstream.
> forward 904654 https://github.com/saltstack/salt/issues/48556
Unknown command or malformed arguments to command.
> tag 893817 - fixed-upstream
Bug #893817 [salt-minion] salt-minion does not start: AttributeError: type 
object 'IOLoop' has no attribute 'initialized'
Removed tag(s) fixed-upstream.
> forward 893817 https://github.com/saltstack/salt-jenkins/issues/995
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#907470: fprint-demo FTBFS: error: dereferencing pointer to incomplete type 'struct fp_minutia'

[Adrian Bunk]

Source: fprint-demo
Version: 20080303git-6
Severity: serious
Tags: buster sid ftbfs

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

...
verify.c: In function 'plot_minutiae':
verify.c:239:29: error: dereferencing pointer to incomplete type 'struct 
fp_minutia'
   size_t pixel_offset = (min->y * width) + min->x;
 ^~

Bug#907248: marked as done (libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts / replaces)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 10:35:21 +
with message-id 
and subject line Bug#907248: fixed in pmix 3.0.1-2
has caused the Debian Bug report #907248,
regarding libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable 
conflicts / replaces
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.)


-- 
907248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi3,libpmix2
Severity: grave
Control: found -1 libopenmpi3/3.1.1.real-7
Control: found -1 libpmix2/3.0.1-1

Hi,

Attempting to upgrade libopenmpi3 to 3.1.1.real-7 after libpmix2 has
already been upgraded to 3.0.1-1 results in this error:

> Preparing to unpack .../libopenmpi3_3.1.1.real-7_amd64.deb ...
> Unpacking libopenmpi3:amd64 (3.1.1.real-7) over (3.1.1.real-4+b1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libopenmpi3_3.1.1.real-7_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libpmix.so.2', which is also 
> in package libpmix2:amd64 3.0.1-1
> Errors were encountered while processing:
>  /var/cache/apt/archives/libopenmpi3_3.1.1.real-7_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Both libopenmpi3 and libpmix2 ship libpmix.so.2, but the replaces
relation in libopenmpi3 only applies to libpmix2 (<< 3.0.0-2).
Presumably the same error would occur if libpmix2 is upgraded after
libopenmpi3.

I've filed the bug against both packages, but please reassign it to the
one that needs fixing.

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 3.0.1-2

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

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

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

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

(This message was generated automatically at their 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, 28 Aug 2018 10:35:18 +0100
Source: pmix
Binary: libpmix-dev libpmi-pmix-dev libpmi1-pmix libpmi2-pmix libpmix2
Architecture: source amd64
Version: 3.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libpmi-pmix-dev - Development files for the PMI library (OpenMPI )
 libpmi1-pmix - OpenMPI implementation of the PMI v1 library
 libpmi2-pmix - OpenMPI implementation of the PMI v2 library
 libpmix-dev - Development files for the PMI Exascale library
 libpmix2   - Process Management Interface (Exascale) library
Closes: 907248
Changes:
 pmix (3.0.1-2) unstable; urgency=medium
 .
   * Add Breaks / Replaces on libopenmpi3 ( << 3.1.2) as it ships a pmix.so
 we ship. Closes: #907248
Checksums-Sha1:
 6f935cc320e6231bcbfab8a0ebc5566ebcdcf356 2140 pmix_3.0.1-2.dsc
 8387ca8f45fe4e542862093edc7ace17e9d3b61e 7240 pmix_3.0.1-2.debian.tar.xz
 645cc652d575926b2ed7cf7dca4959d7498744ee 453996 
libpmi-pmix-dev_3.0.1-2_amd64.deb
 90034ae928b906363ecd813365d3a84409065b16 1499412 
libpmi1-pmix-dbgsym_3.0.1-2_amd64.deb
 fe86cb69f761d9a9d2b9cf59867f3bae52a8c15f 277940 libpmi1-pmix_3.0.1-2_amd64.deb
 08e2fb853cb1286e72ae73923e9ac57f8b5f9382 1505196 
libpmi2-pmix-dbgsym_3.0.1-2_amd64.deb
 1313f4609d8a94e3127b18e50bd9482050b052e3 281152 libpmi2-pmix_3.0.1-2_amd64.deb
 97832014deedd98181072171f3e01932e8a24125 520240 libpmix-dev_3.0.1-2_amd64.deb
 c92d27ce493c2b7ad32025bc08ae687836915c50 2476396 
libpmix2-dbgsym_3.0.1-2_amd64.deb
 f69d52958c93deec1587e5466fe01da91ce8f966 409592 libpmix2_3.0.1-2_amd64.deb
 afccaa5a191f98e78748236fd32c4300d5394691 7945 pmix_3.0.1-2_amd64.buildinfo
Checksums-Sha256:
 877090475de0839171a61286b6fcb77747c44730abc23234b02bf1444af42f64 2140 
pmix_3.0.1-2.dsc
 23738d6fc1f5eb13a73ce1a1258a140c51c38ecef6c47c6f3a737bd1d2b980d1 7240 
pmix_3.0.1-2.debian.tar.xz
 cb13972ac5edb64c31f99c673a62f697b05e45f5a81270b2f639834b0fdc72d6 453996 
libpmi-pmix-dev_3.0.1-2_amd64.deb
 290bfa4b13b5daa29b15d1cbc9766c4639a7e75dc9049442ace29a56e30aca5e 1499412 
libpmi1-pmix-dbgsym_3.0.1-2_amd64.deb
 a3e06c3b28d0e6333567be78ee72c94db0616c5fcbce4a6a60c4b3bbf6aebc

Bug#906511: marked as done (trinity: FTBFS in buster/sid (linux/irda.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 10:35:31 +
with message-id 
and subject line Bug#906511: fixed in trinity 1.8-5
has caused the Debian Bug report #906511,
regarding trinity: FTBFS in buster/sid (linux/irda.h: 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.)


-- 
906511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trinity
Version: 1.8-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
   dh_update_autotools_config -a
   dh_auto_configure -a
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
[*] Checking system headers.
[*] Checking ipv6 headers ... [OK]
[*] Checking if pppox can use pppol2tpin6.. [YES]
[*] Checking if pppox can use pppol2tv3.. [YES]
[*] Checking if pppox can use pptp.. [YES]
[*] Checking if llc can use LLC_OPT_PKTINFO.. [YES]
[*] Checking if glibc headers provide termios2.. [NO]
[*] Checking if glibc headers provide nvme ioctls.. [YES]
[*] Checking if bpf_attr can use map_flags.. [YES]

[... snipped ...]

cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
ioctls/vsock.o -c ioctls/vsock.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
ioctls/vt.o -c ioctls/vt.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
ioctls/watchdog.o -c ioctls/watchdog.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
mm/fault-read.o -c mm/fault-read.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
mm/fault-write.o -c mm/fault-write.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include config.h 
-Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement 
-Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
-Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes 
-fsigned-char -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o 
mm/maps-initial.o -c mm/maps-initial.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werro

Bug#815348: marked as done (nwchem: FTBFS on s390x: testsuite timeout)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 13:35:36 +0300
with message-id <20180828103536.GA3214@localhost>
and subject line nwchem now builds on s390x
has caused the Debian Bug report #815348,
regarding nwchem: FTBFS on s390x: testsuite timeout
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.)


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

Hi,

nwchem FTBFS on mips and s390x:

https://buildd.debian.org/status/fetch.php?pkg=nwchem&arch=mips&ver=6.6%2Br27746-2&stamp=1455562255
https://buildd.debian.org/status/fetch.php?pkg=nwchem&arch=s390x&ver=6.6%2Br27746-2&stamp=1455470907

The testsquite gets killed after running for a long time without output.


Andreas
--- End Message ---
--- Begin Message ---
nwchem now builds on s390x:
https://buildd.debian.org/status/logs.php?pkg=nwchem&arch=s390x

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: affects 907466

[Debian Bug Tracking System]

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

> affects 907466 gnome-software
Bug #907466 [iso-codes] Package doesn't ship xml files anymore
Added indication that 907466 affects gnome-software
> thanks
Stopping processing here.

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

Bug#907466: Package doesn't ship xml files anymore

[Laurent Bigonville]

Package: iso-codes
Version: 4.0-1
Severity: serious

Hi,

Since 4.0-1, iso-codes package is not shipping the xml files anymore:

   * New upstream version 4.0
 - This new release does no longer include the XML data files.
   Please use the JSON data files from now on.

This causes at least one other package to break (gnome-software)

Could you please check the package that are actually using the xml files
and help them to transition to the JSON ones?

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.17.0-3-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

iso-codes depends on no packages.

iso-codes recommends no packages.

Versions of packages iso-codes suggests:
pn  isoquery  

-- no debconf information

Bug#906168: marked as done (pyside2 build depends on libclang-4.0-dev/llvm-4.0-dev which is scheduled for removal)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 09:51:20 +
with message-id 
and subject line Bug#906168: fixed in pyside2 5.11.0-4
has caused the Debian Bug report #906168,
regarding pyside2 build depends on libclang-4.0-dev/llvm-4.0-dev which is 
scheduled for removal
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.)


-- 
906168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyside2
Version: 5.11.0-3
Severity: serious
Control: block 893401 by -1

llvm-toolchain-4.0 is scheduled for removal, see #893401.
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.11.0-4

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 906...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sophie Brun  (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: Mon, 27 Aug 2018 12:53:29 +0200
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.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Sophie Brun 
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 bindings generator for C++ libraries (Python2 
shared libr
 libshiboken2-dev - CPython bindings generator for C++ libraries (development 
files)
 libshiboken2-py3-5.11 - CPython bindings generator for C++ libraries (Python3 
shared libr
 pyside2-tools - development tools for PySide2 (uic, rcc, lupdate)
 python-pyside2-doc - Python bindings for Qt5 (common documentation)
 python-pyside2.qt3dcore - Python bindings for Qt5 3DCore module (Python 2)
 python-pyside2.qt3dinput - Python bindings for Qt5 3DInput module (Python 2)
 python-pyside2.qt3dlogic - Python bindings for Qt5 3DLogic module (Python 2)
 python-pyside2.qt3drender - Python 

Processed: closing 906489

[Debian Bug Tracking System]

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

> close 906489 1.26.0-1
Bug #906489 [src:lightdm] lightdm: FTBFS in buster/sid (dh_makeshlibs fails)
Marked as fixed in versions lightdm/1.26.0-1.
Bug #906489 [src:lightdm] lightdm: FTBFS in buster/sid (dh_makeshlibs fails)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#906489: closing 906489

[Yves-Alexis Perez]

close 906489 1.26.0-1
thanks

Bug#907460: kdepim-runtime: /usr/bin/akonadi_imap_resource keeps crashing preventing kmail to work

[Eric Valette]

Package: kdepim-runtime
Version: 4:18.07.90-1
Severity: grave
Justification: renders package unusable

I manged to install expetimental kdepim today but when starting
kmail I cannot acces to my ipmap account on exhange server (works
with TB on same machine).

I keep having crash traces in my out when started from konsole:

terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: Wrong payload type (requested: 
sp(0); present: sp(2))
ProtocolException thrown:Timeout while waiting for 
dataorg.kde.pim.akonadicontrol: ProcessControl: Application 
"/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' 
crashed! 1 restarts left.


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

Kernel: Linux 4.14.67 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kdepim-runtime depends on:
ii  akonadi-server   4:18.07.90-1
ii  kio  5.49.0-1
ii  kio-ldap 18.07.90-1
ii  kio-sieve4:18.07.90-1
ii  libc62.27-5
ii  libgcc1  1:8.2.0-4
ii  libkf5akonadiagentbase5  4:18.07.90-1
ii  libkf5akonadicalendar5abi1   4:18.07.90-1
ii  libkf5akonadicontact54:18.07.90-1
ii  libkf5akonadicore5abi2   4:18.07.90-1
ii  libkf5akonadimime5   4:18.07.90-1
ii  libkf5akonadinotes5  4:18.07.90-1
ii  libkf5akonadiwidgets5abi14:18.07.90-1
ii  libkf5alarmcalendar5abi1 4:18.07.90-1
ii  libkf5calendarcore5abi2  4:18.07.90-1
ii  libkf5codecs55.49.0-1
ii  libkf5completion55.49.0-1
ii  libkf5configcore55.49.0-1
ii  libkf5configgui5 5.49.0-1
ii  libkf5configwidgets5 5.49.0-1
ii  libkf5contacts5  4:18.07.90-1
ii  libkf5coreaddons55.49.0-1
ii  libkf5dbusaddons55.49.0-1
ii  libkf5i18n5  5.49.0-1
ii  libkf5identitymanagement518.07.90-1
ii  libkf5imap5  18.07.90-1
ii  libkf5itemmodels55.49.0-1
ii  libkf5jobwidgets55.49.0-1
ii  libkf5kdelibs4support5   5.49.0-1
ii  libkf5kiocore5   5.49.0-1
ii  libkf5kiowidgets55.49.0-1
ii  libkf5mailtransport5 18.07.90-2
ii  libkf5mailtransportakonadi5  18.07.90-2
ii  libkf5mbox5  18.07.90-1
ii  libkf5mime5abi1  18.07.90-1
ii  libkf5notifications5 5.49.0-1
ii  libkf5notifyconfig5  5.49.0-1
ii  libkf5service-bin5.49.0-1
ii  libkf5service5   5.49.0-1
ii  libkf5textwidgets5   5.49.0-1
ii  libkf5wallet-bin 5.49.0-1
ii  libkf5wallet55.49.0-1
ii  libkf5widgetsaddons5 5.49.0-1
ii  libkf5windowsystem5  5.49.0-1
ii  libkf5xmlgui55.49.0-1
ii  libkolabxml1v5   1.1.6-3+b1
ii  libkpimgapicalendar5 18.07.90-1
ii  libkpimgapicontacts5 18.07.90-1
ii  libkpimgapicore5abi1 18.07.90-1
ii  libkpimgapitasks518.07.90-1
ii  libkpimkdav5abi2 18.07.90-1
ii  libqt5core5a 5.11.1+dfsg-7
ii  libqt5dbus5  5.11.1+dfsg-7
ii  libqt5gui5   5.11.1+dfsg-7
ii  libqt5network5   5.11.1+dfsg-7
ii  libqt5texttospeech5  5.11.1-2
ii  libqt5webenginecore5 5.11.1+dfsg-5
ii  libqt5webenginewidgets5  5.11.1+dfsg-5
ii  libqt5widgets5   5.11.1+dfsg-7
ii  libqt5xml5   5.11.1+dfsg-7
ii  libsasl2-2   2.1.27~101-g0780600+dfsg-3.1
ii  libstdc++6   8.2.0-4

kdepim-runtime recommends no packages.

kdepim-runtime suggests no packages.

-- no debconf information

Bug#907420: marked as done (rt4-standalone is empty)

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 09:56:42 +0100
with message-id <20180828085642.w2gc62lccglbf...@urchin.earth.li>
and subject line Re: [request-tracker-maintainers] Bug#907420: rt4-standalone 
is empty
has caused the Debian Bug report #907420,
regarding rt4-standalone is empty
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.)


-- 
907420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rt4-standalone
Version: 4.4.1-3
Severity: serious

$ dpkg -L rt4-standalone
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/rt4-standalone
/usr/share/doc/rt4-standalone/NEWS.Debian.gz
/usr/share/doc/rt4-standalone/changelog.Debian.gz
/usr/share/doc/rt4-standalone/copyright
$
--- End Message ---
--- Begin Message ---
On Mon, Aug 27, 2018 at 10:22:25PM +0300, Adrian Bunk wrote:
> Package: rt4-standalone
> Version: 4.4.1-3
> Severity: serious
> 
> $ dpkg -L rt4-standalone
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/rt4-standalone
> /usr/share/doc/rt4-standalone/NEWS.Debian.gz
> /usr/share/doc/rt4-standalone/changelog.Debian.gz
> /usr/share/doc/rt4-standalone/copyright
> $

This is intentional: the package is akin to rt4-apache2, which is mainly
package dependencies with a small amount of configuration. This
mechanism is used to allow the systems administrator to select the
appropriate dependencies depending on their intended configuration.

Dominic.--- End Message ---

Processed: Re: Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #907451 [src:libbiod] libbiod FTBFS: Error: cannot implicitly convert 
expression
Added tag(s) help.

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

Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression

[Andreas Tille]

Control: tags -1 help

Hi Matthias,

can you help with this?

Kind regards

Andreas.

On Tue, Aug 28, 2018 at 10:12:32AM +0300, Adrian Bunk wrote:
> Source: libbiod
> Version: 0.1.0-5
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbiod.html
> 
> ...
> [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O 
> -g -release -wi -relocation-model=pic   -of 'biod@sha/bio_maf_reader.d.o' -c 
> ../bio/maf/reader.d
> FAILED: biod@sha/bio_maf_reader.d.o 
> ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of 'biod@sha/bio_maf_reader.d.o' -c 
> ../bio/maf/reader.d
> ../bio/maf/reader.d(40): Deprecation: struct `std.stdio.File.ByLine!(char, 
> char).ByLine` is deprecated - Use .byLine
> ../bio/maf/reader.d(53): Error: cannot implicitly convert expression 
> `this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, char)` to 
> `ByLine!(char, char)`
> ../bio/maf/reader.d(53):`this._lines = this._f.byLine(cast(Flag)true, 
> '\x0a')` is the first assignment of `this._lines` therefore it represents its 
> initialization
> ../bio/maf/reader.d(53):`opAssign` methods are not used for 
> initialization, but for subsequent assignments
> [

-- 
http://fam-tille.de

Bug#906339: marked as done (bochs: FTBFS in buster/sid (section overlap at linking time))

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 08:34:59 +
with message-id 
and subject line Bug#906339: fixed in bochs 2.6.9+dfsg-2
has caused the Debian Bug report #906339,
regarding bochs: FTBFS in buster/sid (section overlap at linking time)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh_testdir
libtoolize -c
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './compile'
libtoolize: copying file './config.guess'
libtoolize: copying file './config.sub'
libtoolize: copying file './depcomp'
libtoolize: copying file './install-sh'
libtoolize: copying file './missing'
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in 'libltdl/m4'.
libtoolize: copying file 'libltdl/m4/libtool.m4'
libtoolize: copying file 'libltdl/m4/ltargz.m4'

[... snipped ...]


acpi-dsdt.dsl.i625: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0C)

acpi-dsdt.dsl.i628: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0D)

acpi-dsdt.dsl.i631: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0E)

acpi-dsdt.dsl.i634: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0F)


Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180629
Copyright (c) 2000 - 2018 Intel Corporation

ASL Input: acpi-dsdt.dsl.i - 639 lines, 29236 bytes, 707 keywords
AML Output:acpi-dsdt.aml - 7585 bytes, 253 named objects, 454 executable 
opcodes
Hex Dump:  acpi-dsdt.hex - 71586 bytes

Compilation complete. 0 Errors, 51 Warnings, 10 Remarks, 494 Optimizations, 93 
Constants Folded
rm acpi-dsdt.dsl.i
sed -i -e's/^unsigned/const 
unsigned/;s/ACPI-DSDT_HEX/ACPI_DSDT_HEX/g;s/acpi-dsdt_aml_code/AmlCode/g' 
acpi-dsdt.hex
gcc -m32 -fno-stack-protector -O2 -Wall -c -o rombios32.o rombios32.c
rombios32.c: In function 'setup_mtrr':
rombios32.c:502:23: warning: variable 'wc' set but not used 
[-Wunused-but-set-variable]
 int i, vcnt, fix, wc;
   ^~
rombios32.c: In function 'smbios_init':
rombios32.c:2285:30: warning: '%d' directive output may be truncated writing 
between 1 and 6 bytes into a region of size 3 [-Wformat-truncation=]
 snprintf(start, 8, "DIMM %d", instance);
  ^~
rombios32.c:2285:24: note: directive argument in the range [0, 131071]
 snprintf(start, 8, "DIMM %d", instance);
^
rombios32.c:2285:5: note: 'snprintf' output between 7 and 12 bytes into a 
destination of size 8
 snprintf(start, 8, "DIMM %d", instance);
 ^~~
ld -o rombios32.out -T ./rombios32.ld rombios32start.o rombios32.o
ld: section .note.gnu.property LMA [000e4d58,000e4d73] overlaps 
section .data LMA [000e4d58,000e4d63]
ld: section .got.plt LMA [000e4d64,000e4d6f] overlaps section 
.note.gnu.property LMA [000e4d58,000e4d73]
make[1]: *** [Makefile:113: rombios32.out] Error 1
make[1]: Leaving directory '/<>/bochs-2.6.9+dfsg/bios'
make: *** [debian/rules:142: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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: bochs
Source-Version: 2.6.9+dfsg-2

We believe that the bug you reported is fixed in the latest version of
bochs, 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 

Bug#907161: marked as done (qtractor: FTBFS in buster/sid (incomplete type 'QAction' used in nested name specifier))

[Debian Bug Tracking System]

Your message dated Tue, 28 Aug 2018 08:37:03 +
with message-id 
and subject line Bug#907161: fixed in qtractor 0.9.1-2
has caused the Debian Bug report #907161,
regarding qtractor: FTBFS in buster/sid (incomplete type 'QAction' used in 
nested name specifier)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--enable-lilv \
--enable-suil
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --enable-lilv 
--enable-suil
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking

[... snipped ...]

qtractorLv2Plugin.cpp:5071:3: note: in expansion of macro 'LILV_FOREACH'
   LILV_FOREACH(scale_points, iter, points) {
   ^~~~
g++ -c -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -msse -mfpmath=sse -ffast-math -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/alsa -I/usr/include/lilv-0 
-I/usr/include/sratom-0 -I/usr/include/sord-0 -I/usr/include/serd-0 
-I/usr/include/suil-0 -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -O2 -Wall -W -D_REENTRANT 
-fPIC -DQT_NO_DEBUG -DQT_X11EXTRAS_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_XML_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 
-Ivestige 
 -Ilv2 -isystem /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -isystem /usr/include/libdrm 
-I.ui -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
.obj/qtractorMessageBox.o qtractorMessageBox.cpp
g++ -c -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -msse -mfpmath=sse -ffast-math -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/alsa -I/usr/include/lilv-0 
-I/usr/include/sratom-0 -I/usr/include/sord-0 -I/usr/include/serd-0 
-I/usr/include/suil-0 -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -O2 -Wall -W -D_REENTRANT 
-fPIC -DQT_NO_DEBUG -DQT_X11EXTRAS_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_XML_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 
-Ivestige 
 -Ilv2 -isystem /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -isystem /usr/include/libdrm 
-I.ui -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
.obj/qtractorMessageList.o qtractorMessageList.cpp
g++ -c -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -m

Bug#906999: docker.io: FTBFS in buster/sid (too many arguments in call to activation.TLSListeners)

[Dmitry Smirnov]

On Thursday, 23 August 2018 10:06:38 PM AEST Santiago Vila wrote:
> IMHO, it would be better to upload 18.06 for unstable, as it fixes at
> least one RC bug (this one).

That's exactly what we are trying to achieve and the problem you've found is 
because we needed to have all dependencies in "unstable" to prepare for that 
upload.

However it is equally important to be sure that new release of Docker works 
as expected. It won't help anyone if we fix build error but introduce run-
time error.

It might be safe to upload Docker to "unstable" now but I didn't have time  
to test it properly and now when minor update 18.06.01 is out we probably 
need to divert our efforts to prepare it for "unstable"...

-- 
Cheers,
 Dmitry Smirnov.

---

Without doubt you are not sane.
-- Tage Danielsson


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

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

[Debian Bug Tracking System]

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

--
Ran 125 tests in 1.763s

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



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python3.6
Source-Version: 3.6.6-3

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.6 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, 28 Aug 2018 11:10:57 +0200
Source: python3.6
Binary: python3.6 python3.6-venv libpython3.6-stdlib python3.6-minimal 
libpython3.6-minimal libpython3.6 python3.6-examples python3.6-dev 
libpython3.6-dev libpython3.6-testsuite idle-python3.6 python3.6-doc 
python3.6-dbg libpython3.6-dbg
Architecture: source
Version: 3.6.6-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 idle-python3.6 - IDE for Python (v3.6) using Tkinter
 libpython3.6 - Shared Python runtime library (version 3.6)
 libpython3.6-dbg - Debug Build of the Python Interpreter (version 3.6)
 libpython3.6-dev - Header files and a static library for Python (v3.6)
 libpython3.6-minimal - Minimal subset of the Python language (version 3.6)
 libpython3.6-stdlib - Interactive high-level object-oriented language 
(standard library
 libpython3.6-testsuite - Testsuite for the Python standard library (v3.6)
 python3.6  - Interactive high-level object-oriented language (version 3.6)
 python3.6-dbg - Debug Build of the Python Interpreter (version 3.6)
 python3.6-dev - Header files and a static library for Python (v3.6)
 python3.6-doc - Documentation for the high-level object-oriented language 
Python
 python3.6-examples - Examples for the Python language (v3.6)
 python3.6-minimal - Minimal subset of the Python language (version 3.6)
 python3.6-venv - Interactive high-level object-oriented language (pyvenv 
binary, v
Closes: 907215
Changes:
 python3.6 (3.6.6-3) unstable; urgency=medium
 .
   * Update to 20180828 from the 3.6 branch.
   * Disable running some tests which are not ready for Debian's OpenSSL
 defaults (test_{asyncio,ftplib,httplib,imaplib,nntplib,poplib,ssl}).
 Closes: #907215.
Checksums-Sha1:
 ff629ab79eb6b1133cd9beaca38dafc8c5f96014 3420 python3.6_3.6.6-3.dsc
 87caa3bb9ef390ee5804150fa183ff7773d92a93 375880 python3.6_3.6.6-3.debian.tar.xz
 cd58c63f2885ea08b5e858e3c7bbca2fd823bb0d 9414 
python3.6_3.6.6-3_source.buildinfo
Checksums-Sha256:
 7cefff44d0cf90a8faeab92b3b816f8389fd14611eefa659e8d40fc5e6152051 3420 
python3.6_3.6.6-3.dsc
 0e39f06118f4cc69f21dd4d803d9f5a004bef2ba3325903e8604e372395ed335 375880 
python3.6_3.6.6-3.debian.tar.xz
 7cb6b80db3993baefa54942801c2657dcf99ac2f5c194f029278d896655f3db3 9414 
python3.6_3.6.6-3_source.buildinfo
Files:
 101b648aa4a6f508f26be9ca01ae0fc5 3420 python optional python3.6_3.6.6-3.dsc
 5ccebd1275202643498f0d5985c8ffc3 375880 python optional 
python3.6_3.6.6-3.debian.tar.xz
 eed8fa035126434d9622e09d56dab706 9414 python optional 
python3.6_3.6.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAluE9ZoQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9eQ/D/wI+QUJP2VpZorkqRUR0l71Usa6QbUB7Ti5
zyhINu/DGFHgXqRCvqA7tmsUdOKugInR/bgqkIJsBnlEUdrPETCDYkOqSe0AYXSy
0rbUMoZ6rUEJClWTDi3pUPDmuWQ4q7aD6zo9G4HgCnk3eYoATJYSV9l8maixjhVJ
/NP6dGgbrvvirkKN5yMax8pnXlTiOXaDk6bI/BkTf9QOYspdcvQ5P75eEsClaDr3
cXEPx3qG/E2YOFnXh7GXqZd/idbXVPdjf7StUUR62ja0fSgtyhHDaf73YYgnSPA4
x4Xw/0Tj0J4vdIYqiFCZrBsSaOVefhUemy5OPmXAzumyo9F7zqQAANgJs0YvK2tX
IJzdeZADN0t3t/+SrT3iQ54FDOF02b5uvr16dSFXWXtKdLkICXWpy6AkHMRnzSbd
e4tLnRNegL9AKlUW6x995UlFpWc79AzHI58+TfjGWJoniWTF2BHQ03gfyah5wTVf
wcba17crClcGaoO4kzpVYqHffusWI2qYP+V8yP5AuI985l8b5reJCMXxfT7WIm7r
O188ButyowObk28mUy1MrhQ4FlaP0V6f1WWZctWrAB0rOE0qgs94d3OPxDJDPkAJ
3AUx5+Z1fiWJUdHRxHW7Y2fVMKav/4PZ72L28S6pAzlQDsDDSTJ5iDRzMGiFjusN
dBx+FUBbMQ==
=zOno
-END PGP SIGNATURE End Message ---

Bug#907453: irda-utils: No IrDA support in the buster kernel

[Adrian Bunk]

Package: irda-utils
Version: 0.9.18-15
Severity: serious
Tags: buster sid

The upstream kernel dropped IrDA support,
shipping irda-utils in buster might therefore
not make sense.

Bug#906860: xul-ext-mozvoikko no longer works with firefox-esr 60

[Timo Jyrinki]

Unfortunately upstream has removed the API that makes it possible to add
external spellcheckers, and the upstream selected library for
spellchecking is unable to properly support a language with a structure
of Finnish.

Currently there is no other option than to live without spell-checking
support in Mozilla products, and eg copy-paste to and back from a text
editor for spell checking. Or use a full Voikko library compiled into
Javascript with dependencies like at
https://www.puimula.org/htp/testing/js-libvoikko/js-libvoikko-demo.html

-Timo

Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression

[Adrian Bunk]

Source: libbiod
Version: 0.1.0-5
Severity: serious
Tags: ftbfs

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

...
[30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g 
-release -wi -relocation-model=pic   -of 'biod@sha/bio_maf_reader.d.o' -c 
../bio/maf/reader.d
FAILED: biod@sha/bio_maf_reader.d.o 
ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g -release 
-wi -relocation-model=pic   -of 'biod@sha/bio_maf_reader.d.o' -c 
../bio/maf/reader.d
../bio/maf/reader.d(40): Deprecation: struct `std.stdio.File.ByLine!(char, 
char).ByLine` is deprecated - Use .byLine
../bio/maf/reader.d(53): Error: cannot implicitly convert expression 
`this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, char)` to 
`ByLine!(char, char)`
../bio/maf/reader.d(53):`this._lines = this._f.byLine(cast(Flag)true, 
'\x0a')` is the first assignment of `this._lines` therefore it represents its 
initialization
../bio/maf/reader.d(53):`opAssign` methods are not used for 
initialization, but for subsequent assignments
[

Processed: Re: Bug#907422 closed by Scott Kitterman (Re: [Python-modules-team] Bug#907422: python-yaml-dbg is empty)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #907422 {Done: Scott Kitterman } [python-yaml-dbg] 
python-yaml-dbg is empty
Bug reopened
Ignoring request to alter fixed versions of bug #907422 to the same values 
previously set

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

Bug#907422: closed by Scott Kitterman (Re: [Python-modules-team] Bug#907422: python-yaml-dbg is empty)

[Adrian Bunk]

Control: reopen -1

> Date: Mon, 27 Aug 2018 23:33:04 +
> From: Scott Kitterman 
> To: 907422-d...@bugs.debian.org
> Subject: Re: [Python-modules-team] Bug#907422: python-yaml-dbg is empty
> 
> The dbgsym packages aren't sufficient for Python packages which need to 
> depend on the debug version of the interpreter.  It may seem bogus to you, 
> but it's not.

I am well aware of this fact.
But having both is bogus.

And as I wrote in my bug report, the fact that python{,3}-yaml-dbgsym 
are built seems to be the bogus part here.

It is a bug that python-yaml-dbg is empty.

Even more considering the fact that 3.12-1 does have contents,
but the binNMU 3.12-1+b2 is empty.

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