Processed: reassign 936011 to src:pytimechart, forcibly merging 936011 939185

[Debian Bug Tracking System]

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

> reassign 936011 src:pytimechart
Bug #936011 [pytimechart] pytimechart: should this package be removed?
Bug reassigned from package 'pytimechart' to 'src:pytimechart'.
Ignoring request to alter found versions of bug #936011 to the same values 
previously set
Ignoring request to alter fixed versions of bug #936011 to the same values 
previously set
> forcemerge 936011 939185
Bug #936011 [src:pytimechart] pytimechart: should this package be removed?
Bug #936011 [src:pytimechart] pytimechart: should this package be removed?
Marked as found in versions pytimechart/1.0.0~rc1-3.3.
Added tag(s) bullseye and sid.
Bug #939185 [src:pytimechart] pytimechart: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
Merged 936011 939185
> thanks
Stopping processing here.

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

Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")

[Paul Wise]

On Sun, 7 Jul 2019 20:39:10 +0200 Christoph Berg wrote:

> I and #debian-devel in general were pretty surprised that our "buster"
> systems couldn't properly "apt-get update" anymore today:

I recently had a similar issue with the backports repos:

E: Repository 'https://incoming.debian.org/debian-buildd 
buildd-stretch-backports-sloppy InRelease' changed its default priority for 
apt_preferences(5) from 500 to 100.
E: Repository 'https://cdn-aws.deb.debian.org/debian stretch-backports-sloppy 
InRelease' changed its default priority for apt_preferences(5) from 500 to 100.

This was because those suites got a couple of settings added to their
Release files in the apt repository:

NotAutomatic: yes
ButAutomaticUpgrades: yes

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed (with 1 error): forcibly merging 936011 939185

[Debian Bug Tracking System]

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

> forcemerge 936011 939185
Bug #936011 [pytimechart] pytimechart: should this package be removed?
Unable to merge bugs because:
package of #939185 is 'src:pytimechart' not 'pytimechart'
Failed to forcibly merge 936011: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#929829: [Pkg-javascript-devel] Bug#929829: Bug#929829: Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

[Pirate Praveen]

On 2019, സെപ്റ്റംബർ 1 10:13:24 PM IST, Pirate Praveen 
 wrote:
>
>
>On Sun, Sep 1, 2019 at 9:15 PM, Pirate Praveen 
> wrote:
>> And fancy-log package.json wants chalk ^1.1.1 and we have chalk 2.4.2
>
>> which to me looks like a possible culprit.
>
>This was a false positive, I suspect 
>debian/patches/update-process-nextick-args.patch is not correct.

This is also false. I replaced async-done patch with upstream 1.3.2 release, 
but it still fails with same error message.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: severity of 935749 is serious

[Debian Bug Tracking System]

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

> severity 935749 serious
Bug #935749 [src:ocrmypdf] ocrmypdf: autopkgtest regression: This test may fail 
if Tesseract language packs are missing
Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new 
pikepdf, ghostscript and/or pytest
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#936092: marked as done (gcc-9 patches apply even less)

[Debian Bug Tracking System]

Your message dated Mon, 02 Sep 2019 01:04:13 +
with message-id 
and subject line Bug#936092: fixed in cross-gcc 232
has caused the Debian Bug report #936092,
regarding gcc-9 patches apply even less
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.)


-- 
936092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-gcc
Version: 231
Severity: serious
Tags: patch
Control: block -1 by 928035

On top of #928035, there is another change in gcc-9 that makes the gcc-9
patches no longer apply. The attached patch resolves the relevant hunk.
Please consider uploading a new version that works with the current
gcc-9.

Helmut
--- a/gcc-9/0004-added-multi-arch-specific-install-location-patch.patch
+++ b/gcc-9/0004-added-multi-arch-specific-install-location-patch.patch
@@ -368,9 +388,9 @@
 +  else
 +debian_patches += cross-install-location
 +  endif
- endif
- 
- ifeq ($(DEB_TARGET_ARCH_OS),hurd)
+   ifeq ($(with_m2),yes)
+ debian_patches += cross-install-location-gm2
+   endif
 -- 
 2.17.1

--- End Message ---
--- Begin Message ---
Source: cross-gcc
Source-Version: 232

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

Debian distribution maintenance software
pp.
Dima Kogan  (supplier of updated cross-gcc 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: Sun, 01 Sep 2019 16:13:12 -0700
Source: cross-gcc
Binary: cross-gcc-dev
Architecture: source all
Version: 232
Distribution: unstable
Urgency: medium
Maintainer: Debian Cross-Toolchain Team 
Changed-By: Dima Kogan 
Description:
 cross-gcc-dev - Tools for building cross-compilers and cross-compiler packages
Closes: 928035 936092
Changes:
 cross-gcc (232) unstable; urgency=medium
 .
   * rebuild for 9.2.1-6 (Closes: #928035, #936092)
   * rebuild for 8.3.0-21
Checksums-Sha1:
 744217aac9c52f119c4fea0b0b48f27dc21dd3b1 1641 cross-gcc_232.dsc
 86c543ed399d7faa9226f31aaa051dba247e28ec 32068 cross-gcc_232.tar.xz
 5e608a4a2c72bf1f94ecb6e2fc4fba73e987a86a 37640 cross-gcc-dev_232_all.deb
 2d77d28f43581d4350dca53ddaf6364fb967ea0b 5996 cross-gcc_232_amd64.buildinfo
Checksums-Sha256:
 b6b749ee1b65233aaadd6b7eff0a2b6afde9d2a0d175056bf506329114b73ec6 1641 
cross-gcc_232.dsc
 4b9b88b8ef6a4bc8a50a7322674ecbf699df32711804cb22258f07e1b920 32068 
cross-gcc_232.tar.xz
 b524724b70554f31812e678279965c8251432f2c92f0252e3dea5d7120e5eaa5 37640 
cross-gcc-dev_232_all.deb
 7555840c463a4cb822177d4ab0db4ee82abf14e93ee3dd9554630f5d781e1602 5996 
cross-gcc_232_amd64.buildinfo
Files:
 de0913a49ba53e86f9c2716a017ac2da 1641 devel extra cross-gcc_232.dsc
 63b7e6571cae17d35fbbd1b36cf84d45 32068 devel extra cross-gcc_232.tar.xz
 ee4bcf410e7c9b29322ef47c81708960 37640 devel extra cross-gcc-dev_232_all.deb
 608f913f6ed137c1757a2c68c6308f1d 5996 devel extra cross-gcc_232_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdRwTXcLOAUM4CFTz7WO2ElodFWEFAl1sZI0ACgkQ7WO2Elod
FWEecw/9HSjsAc2i6BQvNFQIp+M1pWBzlReQ74Pro/Wc+bEZtKSAJA/HXjQdrG17
ggM413g6Q2P372owR3qLM0cZ86c3ZjgNWKrQ1nzM+ooDBV6pKl39pmWncg9H38Jp
YsaMfQuflRzeckZTgIJdUCClFu5A2FO1xhVFHM/NUNAj5KFTNfAvTTB0BBo5RLYm
gpOND7eoC+WSGLpNtLU2ZTmzr73oTXazRaFIJwOFLS/AO8tORi/NRfb/PonrwBbg
1cCz1Z9DWR1rz40/wWbmAvCsr0Ahz1WRhT4GZblVpe/kaXy/dFOqfUeeFRkAnEaZ
PfB5ZSvchQ9kbu4ERrUgju4pSu4S5TrGDezNGzbmedFlKNq9FyMc3hBKjQW3oGl2
BtbtdvDOX94XDFYUsf4gvZAjvbvHmZjYA1O8TG4HC8kMJNxIFhsffT0mIRajMN8o
qqwGiY4+5u8r9v3fFDgIY5h3RXABY+OUjwwe/KCqQoo/Q3L7oxvB8v2kCZ/JiZ8x
/MAwznhRFMIuIjxS01Z/LozZCXYdVUrmohzYxP/OQ/ZlcRK9SoqW3iP0lz+B3o5W
uAt1u7WCUzBknvGxQO5F4ADDx+2ply2b++PIeHkYSxtQLsOlI59Xt6zYT0jon7LH
P/VO4DYS5xrXdhxMtpwlhq6kvXlfNaEjmpSrZlESnVHshuiy+g0=
=wvQK
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 935749 -1
Bug #935749 [src:ocrmypdf] ocrmypdf: autopkgtest regression: This test may fail 
if Tesseract language packs are missing
Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new 
pikepdf, ghostscript and/or pytest
Severity set to 'normal' from 'serious'
Removed indication that 939044 affects src:pikepdf, src:ghostscript, and 
src:pytest
Marked as found in versions ocrmypdf/9.0.1+dfsg-1.
Bug #935749 [src:ocrmypdf] ocrmypdf: autopkgtest regression: This test may fail 
if Tesseract language packs are missing
Marked as found in versions ocrmypdf/8.0.1+dfsg-1.
Added tag(s) sid and bullseye.
Merged 935749 939044

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

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

[Sean Whitton]

control: forcemerge 935749 -1

Hello Paul,

On Sat 31 Aug 2019 at 03:25PM +02, Paul Gevers wrote:

> With a recent upload of pikepdf and with a recent upload of ghostscript
> and with a recent upload of pytest (althought that pulls in the others)
> the autopkgtest of ocrmypdf fails in testing when that autopkgtest is
> run with the binary packages of those packages from unstable. It passes
> when run with only packages from testing. In tabular form, e.g.:
>passfail
> pikepdffrom testing1.6.1+dfsg-1
> ocrmypdf   from testing8.0.1+dfsg-1
> all others from testingfrom testing

I think this is a duplicate of #935749.

(Replying to you in case that's a bug in your tools for filing bugs.)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#934905: libaqbanking35: libaqbanking not ready for PSD2, will not work after 14 September 2019

[Felix Geyer]

On 25.08.19 13:33, Felix Geyer wrote:

Hi Micha,

On Mon, 19 Aug 2019 20:19:28 +0200 Micha Lenk  wrote:

Hi Christian,

I understand your bug report and confirm it to be an issue.

Unfortunately I don't have much capacity at the moment to work on an updated package in a timely 
manner. But I do appreciate and support any volunteer's help.


I've tested libaqbaking 5.8.1 in combination with gnucash 3.6 + patch for the 
registration key.
It seems to work fine, at least the unregistered software warning from the log 
is gone.

The only packaging changes are some new entries in the symbols file (diff 
attached).
Do you mind if I NMU 5.8.1 to unstable?


I've uploaded version 5.8.2 to DELAYED/2 now.

Cheers,
Felix

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

[Thorsten Glaser]

Dixi quod…

>branch and testing it; can we please merge it into master and upload
>to unstable once it has been tested (should be no problem, I already

FWIW, it builds and installs (as upgrade) and starts.

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#911571: marked as done (src:haskell-hastache: deprecated and broken)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 19:34:34 +
with message-id 
and subject line Bug#939156: Removed package(s) from unstable
has caused the Debian Bug report #911571,
regarding src:haskell-hastache: deprecated and broken
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.)


-- 
911571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-hastache
Version: 0.6.1-8
Severity: serious

Replacements for hastache are mustache and microstache
--- End Message ---
--- Begin Message ---
Version: 0.6.1-10+rm

Dear submitter,

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

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

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

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

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

Bug#925789: marked as done (nsntrace: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 19:27:32 +
with message-id 
and subject line Bug#939086: Removed package(s) from unstable
has caused the Debian Bug report #925789,
regarding nsntrace: ftbfs with GCC-9
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.)


-- 
925789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nsntrace
Version: 0~20160806-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/nsntrace_0~20160806-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
   dh_auto_build -a -O--parallel
make -j4
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libnl3 -Wall -Wno-missing-braces 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
nsntrace-nsntrace.o `test -f 'nsntrace.c' || echo './'`nsntrace.c
gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libnl3 -Wall -Wno-missing-braces 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o nsntrace-cmd.o 
`test -f 'cmd.c' || echo './'`cmd.c
gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libnl3 -Wall -Wno-missing-braces 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o nsntrace-net.o 
`test -f 'net.c' || echo './'`net.c
gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libnl3 -Wall -Wno-missing-braces 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
nsntrace-capture.o `test -f 'capture.c' || echo './'`capture.c
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -lnl-route-3 -lnl-3 -pthread -Wl,-z,relro -o 
nsntrace  nsntrace-nsntrace.o nsntrace-cmd.o nsntrace-net.o nsntrace-capture.o  
-lpcap 
/usr/bin/ld: nsntrace-net.o: in function `_nsntrace_net_get_nl_socket':
./src/net.c:66: undefined reference to `nl_socket_alloc'
/usr/bin/ld: ./src/net.c:67: undefined reference to `nl_connect'
/usr/bin/ld: nsntrace-net.o: in function `_nsntrace_net_iface_up':
./src/net.c:146: undefined reference to `rtnl_link_alloc_cache'
/usr/bin/ld: ./src/net.c:150: undefined reference to `rtnl_link_get_by_name'
/usr/bin/ld: ./src/net.c:154: undefined reference to `rtnl_addr_alloc'
/usr/bin/ld: ./src/net.c:155: undefined reference to `rtnl_addr_set_link'
/usr/bin/ld: ./src/net.c:156: undefined reference to `rtnl_link_put'
/usr/bin/ld: ./src/net.c:158: undefined reference to `nl_addr_parse'
/usr/bin/ld: ./src/net.c:162: undefined reference to `rtnl_addr_set_local'
/usr/bin/ld: ./src/net.c:165: undefined reference to `nl_addr_put'
/usr/bin/ld: ./src/net.c:167: undefined reference to `rtnl_addr_add'
/usr/bin/ld: ./src/net.c:171: undefined reference to `rtnl_link_alloc'
/usr/bin/ld: ./src/net.c:172: undefined reference to `rtnl_link_set_flags'
/usr/bin/ld: 

Bug#939163: src:python-quantities: License in debian/copyright different than upstream

[Scott Kitterman]

Package: src:python-quantities
Version: 0.12.1-1
Severity: serious
Justification: Policy 2.3

While reviewing your package in the New queue, I noticed that the
license currently in the package is radically different than that in
debian/copyright.  I'm accepting the package anyway, since this is an
existing problem in the archive and not new to this update.  Please fix
when you do your source only upload following New.

See doc/user/license.rst for details.

Scott K

Bug#936049: marked as done (metview: missing libopenmpi-dev dependency?)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 18:38:45 +
with message-id 
and subject line Bug#936049: fixed in odb-api 0.18.1-7
has caused the Debian Bug report #936049,
regarding metview: missing libopenmpi-dev dependency?
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.)


-- 
936049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odb-api
Version: 0.18.1-6
Severity: serious
tags: patch

Hello, looks like for some reasons eckit in Ubuntu fails to see the include 
directory for openmpi, because it simply doesn't exist

adding libopenmpi-dev dependency to odb-api should fix the issue, bringing the 
directory back when cmake tries to find header files
/usr/lib/x86_64-linux-gnu/pkgconfig/odb.pc:ODB_CC=/usr/bin/cc -pthread 
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time 
-D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -I${prefix}/include
/usr/lib/x86_64-linux-gnu/cmake/odb/odb-import.cmake:set(ODB_ENVIRONMENT 
"ODB_ROOT=/usr;ODB_SYSPATH=/usr/include;ODB_BINPATH=/usr/bin;ODB_BEBINPATH=/usr/bin;ODB_FEBINPATH=/usr/bin;ODB_LIBPATH=/usr/lib;ODB_RTABLE_PATH=/usr/share/odb;ODB_SYSDBPATH=/usr/share/odb;ODB_CC=/usr/bin/cc
 -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time 
-D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC 
-I/usr/include;ODB_F90=/usr/bin/gfortran -g -O2 
-fdebug-prefix-map=/build/odb-api=. -fstack-protector-strong -fopenmp -fPIC 
-ffree-line-length-none -I/usr/include -I/usr/module 
-I/usr/odb/module;ODB_COMPILER=/usr/bin/odb98.x -V 
-O3;ODB_COMPILER_FLAGS=/usr/share/odb/odb98.flags;ODB_STATIC_LINKING=1;ODB_LD_SHARED=none;ODB_LD_SHARED_SFX=.so;ODB_IOASSIGN_MAXPROC=32;ODB_IOASSIGN_PARAMS=-r
 1m -w 
1m;ODB_AR=/usr/bin/ar;ODB_GZIP=/bin/gzip;ODB_GUNZIP=/bin/gunzip;ODB_SETUP_SHELL=/bin/sh")

it looks like used and needed


snip of the failing log:

-- The following OPTIONAL packages have not been found:

 * Git
 * fckit (required version >= 0.6.2)
 * transi (required version >= 0.4.4)
 * CGAL
 * gridtools_storage

-- ENABLE_EXPOSE_SUBPACKAGES is On:
-- All packages in the bundle will be installed at the same level into:
--   /usr
-- Configuring done
CMake Error in atlas/src/atlas/CMakeLists.txt:
  Imported target "eckit_mpi" includes non-existent path

"/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in atlas/src/atlas/CMakeLists.txt:
  Imported target "eckit_mpi" includes non-existent path

"/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.


trivial patch here:
https://launchpad.net/ubuntu/+source/odb-api/0.18.1-6ubuntu1

Gianfranco
--- End Message ---
--- Begin Message ---
Source: odb-api
Source-Version: 0.18.1-7

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated odb-api 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, 01 Sep 2019 17:48:13 +0100
Source: odb-api
Architecture: source
Version: 0.18.1-7
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 936049
Changes:
 odb-api (0.18.1-7) unstable; urgency=medium
 .
   * Add libopenmpi-dev runtime dependency, to help cmake find libeckit_mpi 
include
 directories. Closes: #936049
Checksums-Sha1:
 87c4663f92e6b53a38025cc172854e07cf2004c3 2619 

Bug#939160: grub-efi-amd64-signed: not installable, broken dependencies

[Matteo F. Vescovi]

Package: grub-efi-amd64-signed
Version: 1+2.04+2
Severity: grave
Justification: renders package unusable

Hi!

While trying to enable Secure Boot on my laptop installing mandatory
packages, I faced this:

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

 The following packages have unmet dependencies:
  grub-efi-amd64-signed : Depends: grub-common (= 2.04-2) but 2.04-3 is to be 
installed
 E: Unable to correct problems, you have held broken packages.

Thanks for the efforts spent fixing it.

Cheers.


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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 grub-efi-amd64-signed depends on:
ii  grub-common  2.04-3

Versions of packages grub-efi-amd64-signed recommends:
ii  shim-signed  1.33+15+1533136590.3beb971-7

grub-efi-amd64-signed suggests no packages.


signature.asc
Description: PGP signature

Processed: Mark #939022 as pending

[Debian Bug Tracking System]

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

> tags 939022 + pending
Bug #939022 [src:pyresample] pyresample: autopkgtest failure with PROJ 6 (epsg 
data file removed)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

[Sebastiaan Couwenberg]

On 9/1/19 7:44 PM, Antonio Valentino wrote:
> It seems that the problem can be fixed by upgrading pyproj to v2.3.1
> (see [2]).
> I made a quick test with python3-pyproj 2.3.1+ds-1~exp1 (available in
> experimental) and I can confirm that all tests pass now.
> 
> I'm going to add a versioned dependency in pyresample but the upload can
> only happen once pyproj 2.3.1 is available in unstable.

As that was only uploaded today, I'm waiting for more builds to succeed.

Since the autopkgtest failures are likely going to block testing
migration of proj and the rdeps rebuilt for the transition. I'm
considering move proj 6.2.0 & pyproj 2.3.1 to unstable in the next few
days, but I'm first going to wait for the aging of the packages uploaded
during the transition. If the migration doesn't happen then, I'll upload
to unstable.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

[Antonio Valentino]

Hi Sebastiaan,
after the workaround committed in [1], remaining issues are:

==
ERROR: test_create_area_def
(pyresample.test.test_geometry.TestStackedAreaDefinition)
Test create_area_def and the four sub-methods that call it in
AreaDefinition.
--
Traceback (most recent call last):
  File
"/home/antonio/debian/git/pyresample/pyresample/test/test_geometry.py",
line 1657, in test_create_area_def
radius=essentials[1], description=description, units=units,
rotation=45))
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 444, in create_area_def
center = _convert_units(center, 'center', units, p, proj_dict)
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 577, in _convert_units
var = _round_poles(var, units, p)
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 517, in _round_poles
center = p(*center, inverse=True, errcheck=True)
  File "/home/antonio/debian/git/pyresample/pyresample/_spatial_mp.py",
line 157, in __call__
radians=radians, errcheck=errcheck)
  File "/usr/lib/python3/dist-packages/pyproj/proj.py", line 183, in
__call__
self._inv(inx, iny, errcheck=errcheck)
  File "pyproj/_proj.pyx", line 165, in pyproj._proj.Proj._inv
pyproj.exceptions.ProjError: generic error of unknown origin: (Internal
Proj Error: proj_crs_get_sub_crs: Object is not a CompoundCRS)

==
ERROR: test_area_parser_yaml (pyresample.test.test_utils.TestYAMLAreaParser)
Test YAML area parser.
--
Traceback (most recent call last):
  File
"/home/antonio/debian/git/pyresample/pyresample/test/test_utils.py",
line 96, in test_area_parser_yaml
'test_latlong')
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 104, in parse_area_file
return _parse_yaml_area_file(area_file_name, *regions)
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 157, in _parse_yaml_area_file
res.append(create_area_def(**params))
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 444, in create_area_def
center = _convert_units(center, 'center', units, p, proj_dict)
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 577, in _convert_units
var = _round_poles(var, units, p)
  File "/home/antonio/debian/git/pyresample/pyresample/area_config.py",
line 517, in _round_poles
center = p(*center, inverse=True, errcheck=True)
  File "/home/antonio/debian/git/pyresample/pyresample/_spatial_mp.py",
line 157, in __call__
radians=radians, errcheck=errcheck)
  File "/usr/lib/python3/dist-packages/pyproj/proj.py", line 183, in
__call__
self._inv(inx, iny, errcheck=errcheck)
  File "pyproj/_proj.pyx", line 165, in pyproj._proj.Proj._inv
pyproj.exceptions.ProjError: generic error of unknown origin: (Internal
Proj Error: proj_crs_get_sub_crs: Object is not a CompoundCRS)


It seems that the problem can be fixed by upgrading pyproj to v2.3.1
(see [2]).
I made a quick test with python3-pyproj 2.3.1+ds-1~exp1 (available in
experimental) and I can confirm that all tests pass now.

I0m going to add a versioned dependency in pyresample but the upload can
only happen once pyproj 2.3.1 is available in unstable.

There seems to be still some warning regarding proj initialization but
as far as I can understand there is some activity upstream on this front
so I think all details will be fully fixed in the next upstream version
of pyresample.


[1]
https://salsa.debian.org/debian-gis-team/pyresample/commit/55eab16e711ff56bac48aee6920840d8ff6e86f0
[2] https://github.com/pyproj4/pyproj/issues/413


kind regards
antonio

On Sun, 1 Sep 2019 17:48:01 +0200 Antonio Valentino
 wrote:
> Hi Sebastiaan,
> I have a workaround for the basemap issue but there are still a couple
> of tests failing.
> 
> cheers
> antonio
> 
> Il 01/09/19 15:05, Sebastiaan Couwenberg ha scritto:
> > On 8/31/19 7:14 PM, Sebastiaan Couwenberg wrote:
> >>> I'm going to reassign.
> >>
> >> That doesn't seem appropriate, pyresample needs to be updated too. It
> >> does things like this:
> >>
> >>  pyresample/test/test_geometry.py:
> >> projections = {'+init=epsg:3006': 'init: epsg:3006'}
> >>
> >> Note the explicit use of init files, this is not going to work correctly
> >> with PROJ 6.
> > 
> > As sort term workaround may be to skip these tests when
> > /usr/share/proj/epsg doesn't exist (or when /usr/share/proj/proj.db does
> > exist).
> > 
> > Kind Regards,
> > 
> > Bas
> > 
> 
> -- 
> Antonio Valentino
> 
> 

-- 
Antonio Valentino

Processed: Temporarily worked around via redirect

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #923510 [bugs.debian.org] bugs.debian.org: 500 Internal Server Error when 
accessing bugs for 'linux'
Severity set to 'important' from 'serious'

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

Bug#923510: Temporarily worked around via redirect

[Don Armstrong]

Control: severity -1 important

I've fixed this issue in the devel branch, but that required a ton of
other changes, so it is waiting for a new release of Debbugs.

In the meantime, I've put in a rewrite proxy rule to switch this
particular request to the devel branch so it should "work" seamlessly.

I've downgraded the severity because of the workaround, but the
underlying issue will still be present until I release the new version
of Debbugs.


-- 
Don Armstrong  https://www.donarmstrong.com

2: There is no out. There is only in.
  -- "The Prisoner (2009 Miniseries)"

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

[Thorsten Glaser]

Version: 9.0.24-1


Emmanuel,

> What is the issue with the dependency on systemd? I was under the

there is new data related to that:

In bullseye/sid, there’s elogind as desktop/logind alternative that
implements the logind API but does not otherwise try to take over
the system, allowing other inits (sysvinit, openrc, runit, …) to be
used, and it does not carry systemd-sysusers either.

More importantly, elogind Conflicts with systemd (both to ensure it
is not confused for systemd or accidentally installed and because it
implements only a subset necessary for the desktop stuff and network-
manager, which I’ve seen people even use for servers nowadays).

This makes it even more important that tomcat9 can be used without
a dependency on the systemd binary package. I’m updating the sysvinit
branch and testing it; can we please merge it into master and upload
to unstable once it has been tested (should be no problem, I already
tested it before, and the diff to 9.0.24-1 is minimal)?

This would also allow buster-backports to be used without systemd,
which is better than not at all.

Thanks,
//mirabilos
-- 
13:22⎜«neurodamage» mira, what's up man? I have a CVS question for you in #cvs
13:22⎜«neurodamage» since you're so good w. it │ «neurodamage:#cvs» i love you
13:28⎜«neurodamage:#cvs» you're a handy guy to have around for systems stuff ☺
16:06⎜ Thank god I found you =)   20:03│«bioe007:#cvs» mira2k: ty

Bug#929829: [Pkg-javascript-devel] Bug#929829: Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

[Pirate Praveen]

On Sun, Sep 1, 2019 at 9:15 PM, Pirate Praveen 
 wrote:
And fancy-log package.json wants chalk ^1.1.1 and we have chalk 2.4.2 
which to me looks like a possible culprit.


This was a false positive, I suspect 
debian/patches/update-process-nextick-args.patch is not correct.

Bug#925782: Patch for bug 925782

[Joachim Reichel]

tag 925782 + patch
thanks

Hi,

attached is a patch that fixes the FTBFS with g++-9.

Best regards,
  Joachim
Index: mp3check-0.8.7/texception.h
===
--- mp3check-0.8.7.orig/texception.h
+++ mp3check-0.8.7/texception.h
@@ -38,10 +38,10 @@ extern "C" {

 #define TExceptionN(n) public: virtual const char *name()  const { return #n; }
 #define TExceptionM(m) public: virtual const char *message() const { return m; }
-#define TExceptionM1(m,a) public: virtual const char *message() const { char *buf; asprintf(, m, a); return buf; }
-#define TExceptionM2(m,a,b) public: virtual const char *message() const { char *buf; asprintf(, m, a,b); return buf; }
-#define TExceptionM3(m,a,b,c) public: virtual const char *message() const { char *buf; asprintf(, m, a,b,c); return buf; }
-#define TExceptionM4(m,a,b,c,d) public: virtual const char *message() const { char *buf; asprintf(, m, a,b,c,d); return buf; }
+#define TExceptionM1(m,a) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a); return result != -1 ? buf : "asprintf failure"; }
+#define TExceptionM2(m,a,b) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a,b); return result != -1 ? buf : "asprintf failure"; }
+#define TExceptionM3(m,a,b,c) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a,b,c); return result != -1 ? buf : "asprintf failure"; }
+#define TExceptionM4(m,a,b,c,d) public: virtual const char *message() const { char *buf; int result = asprintf(, m, a,b,c,d); return result != -1 ? buf : "asprintf failure"; }

 // base class of all exceptions
 class TException {
Index: mp3check-0.8.7/tstring.cc
===
--- mp3check-0.8.7.orig/tstring.cc
+++ mp3check-0.8.7/tstring.cc
@@ -111,7 +111,7 @@ tstring::Rep *tstring::Rep::clone(size_t
 tstring::Rep *tstring::Rep::create(size_t tmem) {
size_t m = sizeof(Rep) << 1;
while((m - 1 - sizeof(Rep)) < tmem) m <<= 1;
-   Rep *p = new (m - 1 - sizeof(Rep)) Rep;
+   Rep *p = new (/*tag*/ true, m - 1 - sizeof(Rep)) Rep;
p->mem = m - 1 - sizeof(Rep); p->ref = 1; p->vulnerable = false;
return p;
 }
Index: mp3check-0.8.7/tstring.h
===
--- mp3check-0.8.7.orig/tstring.h
+++ mp3check-0.8.7/tstring.h
@@ -71,9 +71,12 @@ class tstring {

   // static methods
   // operator new for this class
-  static void * operator new (size_t size, size_t tmem) {
+  // add a tag parameter to ensure that the signature of the delete operator does not collide with the (void*,size_t) overload
+  static void * operator new (size_t size, bool /*tag*/, size_t tmem) {
 	 return ::operator new (size + tmem + 1);}
-  static void operator delete (void *p, size_t) {
+  static void operator delete (void *p, bool /*tag*/, size_t) {
+	 ::operator delete (p); }
+  static void operator delete (void *p) {
 	 ::operator delete (p); }

   // create a new representation

Processed: Patch for bug 925782

[Debian Bug Tracking System]

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

> tag 925782 + patch
Bug #925782 [src:mp3check] mp3check: ftbfs with GCC-9
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#933667: marked as done (sagemath: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 16:34:30 +
with message-id 
and subject line Bug#932367: fixed in sagemath 8.8-1
has caused the Debian Bug report #932367,
regarding sagemath: FTBFS in 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.)


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

Hello, looks like sagemath is now FTBFS, see e.g. logs at
http://debomatic-amd64.debian.net/distribution#unstable/sagemath/8.6-6build1/buildlog

and
https://launchpad.net/ubuntu/+source/sagemath/8.6-6build1/+build/17348800

not sure what regressed it.

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.8-1

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 01 Sep 2019 16:14:42 +
Source: sagemath
Architecture: source
Version: 8.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Closes: 932367 934171
Changes:
 sagemath (8.8-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #932367, #934171)
   * New (Build-)Depends:
 - libbrial-dev (>= 1.2.5)
 - libbrial-groebner-dev (>= 1.2.5)
 - libec-dev (>= 20190226)
 - maxima-sage (>= 5.42.2)
 - python-cypari2 (>= 2.1)
 - python-gmpy2
 - python-nose
 - python-ppl
 - python-ppl-doc
 - python-scipy (>= 1.2)
 - python-sphinx (>= 1.8.5)
 - sagemath-database-conway-polynomials (>= 0.5-7)
   * Remove patches (applied upstream):
 - u0-version-numpy-1.16-inline-fortran.patch #27061
 - u0-version-sphinx-1.8.patch#26451
 - u0-version-sphinx-1.8-dependency.patch #26949
 - u1-sphinx-1.8-doctest-transform.patch  #27528
 - u2-libgap-symbol-loading.patch #26930
 - d1-disable-post-install-tests.patch
   * Patches with non-trivial modifications:
 - u0-version-sphinx-1.8.patch#26451
 - d0-singular.patch
 - d0-paths.patch
 - d0-libgap-path.patch
 - d1-install-paths.patch
 - d1-sage-cli.patch
 - d1-sage-env.patch
 - dt-version-ipywidgets-6-revert-23177.patch
   * Allow up to 65 failed tests.
Checksums-Sha1:
 c86c89a7e8f0e6863a522821d25d683ea85e0e1e 6731 sagemath_8.8-1.dsc
 77a39ed0e7f0c11167e338b2ee62c6233b7098b0 17534020 sagemath_8.8.orig.tar.xz
 be121a69421e4a2faaf2c91c2d8c96e52d71f9be 76764 sagemath_8.8-1.debian.tar.xz
 f884fc67a8534098eacf6b2d2fe9538ba287a6e3 24138 sagemath_8.8-1_source.buildinfo
Checksums-Sha256:
 5898ab9ad08dc4dc4e6c7ac96cd2aff0f4a55af24287090f26fbfe695fe71824 6731 
sagemath_8.8-1.dsc
 5c56a60a9abb5c2e28e5e0ca6e6f2c72b2b02331ca814875032a50ebf4234cd4 17534020 
sagemath_8.8.orig.tar.xz
 a872af367d38501a19d774d2f0bf336a50e9de8464f7a42967d80e66e965a90e 76764 
sagemath_8.8-1.debian.tar.xz
 b630662193d7e5a9643fea6bdb3c6d12ab618bfc9b2cdf02b51630c47813f0d2 24138 
sagemath_8.8-1_source.buildinfo
Files:
 d99d6151def0223e8aebd91940eea5e1 6731 math optional sagemath_8.8-1.dsc
 cf2ec705c08d5dd2a98866a7f284c8ab 17534020 math optional 
sagemath_8.8.orig.tar.xz
 c2e72cd4aca0732d1c78fc9e103541b6 76764 math optional 
sagemath_8.8-1.debian.tar.xz
 7f1ca876e0935a38f043e1ce981d47a5 24138 math optional 
sagemath_8.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAl1r7wQACgkQjIIWnY7O
zSq5zQ//Yl9Iey3OmybSwqPM2l1zOgvnt5cW9ThvhptF87SDiD/RuUj1t/QEFiya
DDWeQsm17WBDDWfbv9ASsY4dwSMq9PWMaRnXFBZpf2FbLxueMcQVVFLh3z35oDjS
nznPDVwmQkqa7G7QjYgT6Z5mOFgt/ASOGFuiap1cA/5PiCNqS+9+N0eoRZIB7HUe
GFLW/pbmeO/3grUmVfFMJszei6Xgd7X1fwSjJ89s/CkMuRbFcgvrfOb3/AmG3GwN
l1xoxV5vyZs3vwXz3xnwCJ7/aPkmWHltVEeuwupuJAEI4AnaMM4g6U4MIlcSOgTe
CLQaNiMJPtGfnzYcpo0ow9ObMYPr8061/rwwrfSG2SuDRhCFmnLv/2Uw1oX3JFi4
sVzaJlUpO2IMWn/C3Gxsn1LQipNfnIGKUJa3KmGSzO+VEcuZ+ZuSGOlsOTzRZZaA

Bug#933021: marked as done (sagemath ftbfs in unstable (too many test failures))

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 16:34:30 +
with message-id 
and subject line Bug#932367: fixed in sagemath 8.8-1
has caused the Debian Bug report #932367,
regarding sagemath ftbfs in unstable (too many test failures)
to be marked as done.

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

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


-- 
932367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sagemath
Version: 8.6-6
Severity: serious
Tags: sid bullseye

the builds show too many test failures on all architectures.

[...]
otal time for all tests: 5258.7 seconds
cpu time: 13588.0 seconds
cumulative wall time: 19677.1 seconds
make[2]: Entering directory '/<>'
Error: 22979 tests failed, up to 50 failures are tolerated
make[2]: *** [debian/rules:252: had-few-failures] Error 1
make[2]: Leaving directory '/<>'
make[2]: Entering directory '/<>'
Checking number of failed tests to determine whether to rerun tests in series...
No: 22979 tests failed, up to 100 failures are tolerated for rerun
make[2]: *** [debian/rules:265: had-not-too-many-failures] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:289: override_dh_auto_test-arch] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:73: binary-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.8-1

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 01 Sep 2019 16:14:42 +
Source: sagemath
Architecture: source
Version: 8.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Closes: 932367 934171
Changes:
 sagemath (8.8-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #932367, #934171)
   * New (Build-)Depends:
 - libbrial-dev (>= 1.2.5)
 - libbrial-groebner-dev (>= 1.2.5)
 - libec-dev (>= 20190226)
 - maxima-sage (>= 5.42.2)
 - python-cypari2 (>= 2.1)
 - python-gmpy2
 - python-nose
 - python-ppl
 - python-ppl-doc
 - python-scipy (>= 1.2)
 - python-sphinx (>= 1.8.5)
 - sagemath-database-conway-polynomials (>= 0.5-7)
   * Remove patches (applied upstream):
 - u0-version-numpy-1.16-inline-fortran.patch #27061
 - u0-version-sphinx-1.8.patch#26451
 - u0-version-sphinx-1.8-dependency.patch #26949
 - u1-sphinx-1.8-doctest-transform.patch  #27528
 - u2-libgap-symbol-loading.patch #26930
 - d1-disable-post-install-tests.patch
   * Patches with non-trivial modifications:
 - u0-version-sphinx-1.8.patch#26451
 - d0-singular.patch
 - d0-paths.patch
 - d0-libgap-path.patch
 - d1-install-paths.patch
 - d1-sage-cli.patch
 - d1-sage-env.patch
 - dt-version-ipywidgets-6-revert-23177.patch
   * Allow up to 65 failed tests.
Checksums-Sha1:
 c86c89a7e8f0e6863a522821d25d683ea85e0e1e 6731 sagemath_8.8-1.dsc
 77a39ed0e7f0c11167e338b2ee62c6233b7098b0 17534020 sagemath_8.8.orig.tar.xz
 be121a69421e4a2faaf2c91c2d8c96e52d71f9be 76764 sagemath_8.8-1.debian.tar.xz
 f884fc67a8534098eacf6b2d2fe9538ba287a6e3 24138 sagemath_8.8-1_source.buildinfo
Checksums-Sha256:
 5898ab9ad08dc4dc4e6c7ac96cd2aff0f4a55af24287090f26fbfe695fe71824 6731 
sagemath_8.8-1.dsc
 5c56a60a9abb5c2e28e5e0ca6e6f2c72b2b02331ca814875032a50ebf4234cd4 17534020 
sagemath_8.8.orig.tar.xz
 a872af367d38501a19d774d2f0bf336a50e9de8464f7a42967d80e66e965a90e 76764 
sagemath_8.8-1.debian.tar.xz
 b630662193d7e5a9643fea6bdb3c6d12ab618bfc9b2cdf02b51630c47813f0d2 24138 
sagemath_8.8-1_source.buildinfo
Files:
 d99d6151def0223e8aebd91940eea5e1 6731 math optional sagemath_8.8-1.dsc
 cf2ec705c08d5dd2a98866a7f284c8ab 17534020 math optional 
sagemath_8.8.orig.tar.xz
 c2e72cd4aca0732d1c78fc9e103541b6 76764 math optional 
sagemath_8.8-1.debian.tar.xz
 7f1ca876e0935a38f043e1ce981d47a5 24138 math optional 

Bug#932367: marked as done (sagemath: Sage does not start because of a missing symbol in GAP wrapper)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 16:34:30 +
with message-id 
and subject line Bug#932367: fixed in sagemath 8.8-1
has caused the Debian Bug report #932367,
regarding sagemath: Sage does not start because of a missing symbol in GAP 
wrapper
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.)


-- 
932367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sagemath
Version: 8.6-6
Severity: important

Dear Maintainer,

running sagemath (either directly with 'sage' or running a notebook with 
jupyter)
does not work because the kernel crashes. The final error reported by Python is

ImportError: 
/usr/lib/python2.7/dist-packages/sage/libs/gap/element.x86_64-linux-gnu.so: 
undefined symbol: _GAP_SetEnterStackCount

This renders sage unusable because the kernel will not start. Let me know how 
if I can help
by providing more information. I copy the full backtrace below:

Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/sage/repl/ipython_kernel/__main__.py", 
line 3, in 
IPKernelApp.launch_instance(kernel_class=SageKernel)
  File "/usr/lib/python2.7/dist-packages/traitlets/config/application.py", line 
657, in launch_instance
app.initialize(argv)
  File "", line 2, in initialize
  File "/usr/lib/python2.7/dist-packages/traitlets/config/application.py", line 
87, in catch_config_error
return method(app, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/ipykernel/kernelapp.py", line 476, in 
initialize
self.init_kernel()
  File "/usr/lib/python2.7/dist-packages/ipykernel/kernelapp.py", line 387, in 
init_kernel
user_ns=self.user_ns,
  File "/usr/lib/python2.7/dist-packages/traitlets/config/configurable.py", 
line 412, in instance
inst = cls(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/sage/repl/ipython_kernel/kernel.py", 
line 52, in __init__
SageJupyterCustomizations(self.shell)
  File "/usr/lib/python2.7/dist-packages/sage/repl/ipython_extension.py", line 
433, in __init__
import sage.all # until sage's import hell is fixed
  File "/usr/lib/python2.7/dist-packages/sage/all.py", line 102, in 
from sage.modular.allimport *
  File "/usr/lib/python2.7/dist-packages/sage/modular/all.py", line 4, in 

from .quatalg.all import *
  File "/usr/lib/python2.7/dist-packages/sage/modular/quatalg/__init__.py", 
line 4, in 
from . import all
  File "/usr/lib/python2.7/dist-packages/sage/modular/quatalg/all.py", line 3, 
in 
from .brandt import BrandtModule
  File "/usr/lib/python2.7/dist-packages/sage/modular/quatalg/brandt.py", line 
206, in 
from sage.modular.hecke.all import (AmbientHeckeModule, HeckeSubmodule, 
HeckeModuleElement)
  File "/usr/lib/python2.7/dist-packages/sage/modular/hecke/all.py", line 20, 
in 
from .ambient_module import AmbientHeckeModule, is_AmbientHeckeModule
  File "/usr/lib/python2.7/dist-packages/sage/modular/hecke/ambient_module.py", 
line 38, in 
from sage.modular.arithgroup.all import Gamma0 # for Sturm bound
  File "/usr/lib/python2.7/dist-packages/sage/modular/arithgroup/__init__.py", 
line 4, in 
from . import all
  File "/usr/lib/python2.7/dist-packages/sage/modular/arithgroup/all.py", line 
6, in 
from .congroup_generic import is_CongruenceSubgroup, 
CongruenceSubgroup_constructor as CongruenceSubgroup
  File 
"/usr/lib/python2.7/dist-packages/sage/modular/arithgroup/congroup_generic.py", 
line 28, in 
from sage.groups.matrix_gps.all import MatrixGroup
  File "/usr/lib/python2.7/dist-packages/sage/groups/matrix_gps/all.py", line 
13, in 
import sage.groups.matrix_gps.pickling_overrides
  File 
"/usr/lib/python2.7/dist-packages/sage/groups/matrix_gps/pickling_overrides.py",
 line 7, in 
from sage.groups.matrix_gps.finitely_generated import 
FinitelyGeneratedMatrixGroup_gap
  File 
"/usr/lib/python2.7/dist-packages/sage/groups/matrix_gps/finitely_generated.py",
 line 81, in 
from sage.groups.matrix_gps.matrix_group import (
  File 
"/usr/lib/python2.7/dist-packages/sage/groups/matrix_gps/matrix_group.py", line 
61, in 
from sage.groups.libgap_wrapper import ParentLibGAP
  File "sage/libs/gap/element.pxd", line 32, in init sage.groups.libgap_wrapper 
(build/cythonized/sage/groups/libgap_wrapper.c:9846)
cdef class GapElement(RingElement):
ImportError: 

Bug#934171: marked as done (sagemath: FTFBS with libreadline8)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 16:34:30 +
with message-id 
and subject line Bug#934171: fixed in sagemath 8.8-1
has caused the Debian Bug report #934171,
regarding sagemath: FTFBS with libreadline8
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.)


-- 
934171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sagemath
Version: 8.6-6
Severity: serious
Tags: ftbfs
Justification: FTBFS

In a rebuild for the readline transition sagemath fails to build
with the following error:

| Error: 22979 tests failed, up to 50 failures are tolerated

I tried to capture some of the log but it's so vast I gave up waiting
for it to download. You can see the full logs on the buildd page,
https://buildd.debian.org/status/package.php?p=sagemath


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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.8-1

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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, 01 Sep 2019 16:14:42 +
Source: sagemath
Architecture: source
Version: 8.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Closes: 932367 934171
Changes:
 sagemath (8.8-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #932367, #934171)
   * New (Build-)Depends:
 - libbrial-dev (>= 1.2.5)
 - libbrial-groebner-dev (>= 1.2.5)
 - libec-dev (>= 20190226)
 - maxima-sage (>= 5.42.2)
 - python-cypari2 (>= 2.1)
 - python-gmpy2
 - python-nose
 - python-ppl
 - python-ppl-doc
 - python-scipy (>= 1.2)
 - python-sphinx (>= 1.8.5)
 - sagemath-database-conway-polynomials (>= 0.5-7)
   * Remove patches (applied upstream):
 - u0-version-numpy-1.16-inline-fortran.patch #27061
 - u0-version-sphinx-1.8.patch#26451
 - u0-version-sphinx-1.8-dependency.patch #26949
 - u1-sphinx-1.8-doctest-transform.patch  #27528
 - u2-libgap-symbol-loading.patch #26930
 - d1-disable-post-install-tests.patch
   * Patches with non-trivial modifications:
 - u0-version-sphinx-1.8.patch#26451
 - d0-singular.patch
 - d0-paths.patch
 - d0-libgap-path.patch
 - d1-install-paths.patch
 - d1-sage-cli.patch
 - d1-sage-env.patch
 - dt-version-ipywidgets-6-revert-23177.patch
   * Allow up to 65 failed tests.
Checksums-Sha1:
 c86c89a7e8f0e6863a522821d25d683ea85e0e1e 6731 sagemath_8.8-1.dsc
 77a39ed0e7f0c11167e338b2ee62c6233b7098b0 17534020 sagemath_8.8.orig.tar.xz
 be121a69421e4a2faaf2c91c2d8c96e52d71f9be 76764 sagemath_8.8-1.debian.tar.xz
 f884fc67a8534098eacf6b2d2fe9538ba287a6e3 24138 sagemath_8.8-1_source.buildinfo
Checksums-Sha256:
 5898ab9ad08dc4dc4e6c7ac96cd2aff0f4a55af24287090f26fbfe695fe71824 6731 
sagemath_8.8-1.dsc
 5c56a60a9abb5c2e28e5e0ca6e6f2c72b2b02331ca814875032a50ebf4234cd4 17534020 
sagemath_8.8.orig.tar.xz
 a872af367d38501a19d774d2f0bf336a50e9de8464f7a42967d80e66e965a90e 76764 
sagemath_8.8-1.debian.tar.xz
 b630662193d7e5a9643fea6bdb3c6d12ab618bfc9b2cdf02b51630c47813f0d2 24138 
sagemath_8.8-1_source.buildinfo
Files:
 d99d6151def0223e8aebd91940eea5e1 6731 math optional sagemath_8.8-1.dsc
 cf2ec705c08d5dd2a98866a7f284c8ab 17534020 math optional 
sagemath_8.8.orig.tar.xz
 c2e72cd4aca0732d1c78fc9e103541b6 76764 math optional 

Bug#933099: marked as done (sagemath: sage command does not work due to it crashed)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 16:34:30 +
with message-id 
and subject line Bug#932367: fixed in sagemath 8.8-1
has caused the Debian Bug report #932367,
regarding sagemath: sage command does not work due to it crashed
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.)


-- 
932367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sagemath
Version: 8.6-6
Severity: important

Dear Maintainer,

I installed sagemath with aptitude. This is first time to use.(I mean
clean instatation)

I just type "sage". (I am going to call interactive shell). see below



$ sage
┌┐
│ SageMath version 8.6, Release Date: 2019-01-15 │
│ Using Python 2.7.16. Type "help()" for help.   │
└┘

**

Oops, Sage crashed. We do our best to make it stable, but...

A crash report was automatically generated with the following information:
  - A verbatim copy of the crash traceback.
  - A copy of your input history during this session.
  - Data on your current Sage configuration.

It was left in the file named:
'/home/yabuki/.ipython/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will help
them in understanding and correcting the problem.

You can mail it to: sage-support at sage-supp...@googlegroups.com
with the subject 'Sage Crash Report'.

If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-supp...@googlegroups.com < 
/home/yabuki/.ipython/Sage_crash_report.txt

In your email, please also include information about:
- The operating system under which the crash happened: Linux, macOS, Windows,
  other, and which exact version (for example: Ubuntu 16.04.3, macOS 10.13.2,
  Windows 10 Pro), and whether it is 32-bit or 64-bit;
- How Sage was installed: using pip or conda, from GitHub, as part of
  a Docker container, or other, providing more detail if possible;
- How to reproduce the crash: what exact sequence of instructions can one
  input to get the same crash? Ideally, find a minimal yet complete sequence
  of instructions that yields the crash.

To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org

Hit  to quit (your terminal may close):
and attach crash report.



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

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

Versions of packages sagemath depends on:
ii  cysignals-tools   1.8.1+ds-2
ii  cython0.29.2-2
ii  ecl   16.1.3+ds-2
ii  eclib-tools   20190226-2
ii  fflas-ffpack  2.3.2-3
ii  flintqs   1:1.0-3
ii  gap-atlasrep  1.5.1-2
ii  gap-core  4r10p2-2
ii  gap-dev   4r10p2-2
ii  gap-online-help   4r10p2-2
ii  gap-primgrp   3.3.2-1
ii  gap-smallgrp  1.3-1
ii  gap-table-of-marks1.2.7-2
ii  gap-transgrp  2.0.4-1
ii  gfan  0.6.2-2
ii  gmp-ecm   7.0.4+ds-5
ii  ipython   5.8.0-1
ii  iso-codes 4.3-1
ii  jmol  14.6.4+2016.11.05+dfsg1-4
ii  lcalc 1.23+dfsg-11
ii  less  487-0.1+b1
ii  libatlas3-base [liblapack.so.3]   3.10.3-8
ii  libblas3 [libblas.so.3]   3.8.0-2
ii  libbraiding0

Bug#925624: [Debichem-devel] Bug#925624: abinit: ftbfs with GCC-9

[Michael Banck]

Hi,

On Wed, Mar 27, 2019 at 07:43:54PM +, Matthias Klose wrote:
> [...]
> 
> 
> YAML Error found in the stdout of [fast][t29][np=1]
> --- !ERROR
> src_file: inwffil.F90
> src_line: 246
> mpi_rank: 0
> message: |
> Missing data file: t27o_WFK
> ...
> 
> Command   /<>/src/98_main/abinit < 
> /<>/tests/Test_suite/fast_t30/t30.stdin > 
> /<>/tests/Test_suite/fast_t30/t30.stdout 2> 
> /<>/tests/Test_suite/fast_t30/t30.stderr
>  returned exit_code: 139

That looks a bit weird to me, seems to be test suite issues.

FWIW, I get the following FTBFS error on current unstable (while stable
still builds fine):

|gfortran -DHAVE_CONFIG_H -I. -I../..  -I../../src/77_ddb
|-I../../src/77_ddb -I../../src/32_util -I../../src/32_util
|-I../../src/44_abitools -I../../src/44_abitools
|-I../../src/27_toolbox_oop -I../../src/27_toolbox_oop
|-I../../src/44_abitypes_defs -I../../src/44_abitypes_defs
|-I../../src/72_response -I../../src/72_response -I../../src/16_hideleave
|-I../../src/16_hideleave -I../../src/42_parser -I../../src/42_parser
|-I../../src/55_abiutil -I../../src/55_abiutil -I../../src/41_geometry
|-I../../src/41_geometry -I../../src/45_geomoptim
|-I../../src/45_geomoptim -I../../src/12_hide_mpi -I../../src/12_hide_mpi
|-I../../src/10_defs -I../../src/10_defs -I../../src/14_hidewrite
|-I../../src/14_hidewrite -I../../src/57_iovars -I../../src/57_iovars
|-I../../src/28_numeric_noabirule -I../../src/28_numeric_noabirule
|-I../../src/incs -I../../src/incs
|-I/<>/fallbacks/exports/include   -ffree-form
|-J/<>/src/mods  -ffree-line-length-none -g -c -o
|m_polynomial_coeff.o m_polynomial_coeff.F90
|m_polynomial_coeff.F90:2883:67:
|
| 2800 |do icoeff1=icoeff,ncoeff+nstr
|  |2   
|..
| 2883 | &
|index_coeff,list_combination,icoeff1,max_power_strain,&
|  |
|1
|Error: Variable 'icoeff1' at (1) not definable inside loop beginning at
|(2) as INTENT(INOUT) argument to subroutine 'computecombinationfromlist'
|m_polynomial_coeff.F90:2643:26:
|
| 2553 |do icoeff1=icoeff,ncoeff+nstr
|  |2
|..
| 2643 | &
|icoeff1,icoeff_tot,natom,ncoeff,nstr,ncoeff_out,nrpt,nsym,power_disp+1,&
|  |  1
|Error: Variable 'icoeff1' at (1) not definable inside loop beginning at
|(2) as INTENT(INOUT) argument to subroutine 'computenorder'
|make[5]: *** [Makefile:1022: m_polynomial_coeff.o] Error 1

I've forwarded that to https://github.com/abinit/abinit/issues/24
as those subroutine are recursive, and I am not 100% sure what the
intent is. It's a bit weird that those issues turn up only now, I've
seen those errors quoted years ago in other software.


Michael

Bug#929829: [Pkg-javascript-devel] Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

[Pirate Praveen]

On Sun, Sep 1, 2019 at 9:12 PM, Pirate Praveen 
 wrote:

On Sun, 01 Sep 2019 19:29:44 +0500 Pirate Praveen
mailto:prav...@onenetbeyond.org>> wrote:



 > Just extra information: I just found node-postcss also fails the 
same

 > way (to confirm it is indeed a gulp issue).

 Is there a way we can find which file brings this error?



Running the following command in node-postcss master

node-postcss$ node --inspect-brk
/usr/share/nodejs/gulp/node_modules/gulp-cli/bin/gulp.js build

And opening chrome://inspect and clicking "Open dedicated DevTools 
for Node"


Then run script button on top right,

Gives the error is found in this file




And fancy-log package.json wants chalk ^1.1.1 and we have chalk 2.4.2 
which to me looks like a possible culprit.

Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

[Antonio Valentino]

Hi Sebastiaan,
I have a workaround for the basemap issue but there are still a couple
of tests failing.

cheers
antonio

Il 01/09/19 15:05, Sebastiaan Couwenberg ha scritto:
> On 8/31/19 7:14 PM, Sebastiaan Couwenberg wrote:
>>> I'm going to reassign.
>>
>> That doesn't seem appropriate, pyresample needs to be updated too. It
>> does things like this:
>>
>>  pyresample/test/test_geometry.py:
>> projections = {'+init=epsg:3006': 'init: epsg:3006'}
>>
>> Note the explicit use of init files, this is not going to work correctly
>> with PROJ 6.
> 
> As sort term workaround may be to skip these tests when
> /usr/share/proj/epsg doesn't exist (or when /usr/share/proj/proj.db does
> exist).
> 
> Kind Regards,
> 
> Bas
> 

-- 
Antonio Valentino

Bug#929829: [Pkg-javascript-devel] Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

[Pirate Praveen]

On Sun, 01 Sep 2019 19:29:44 +0500 Pirate Praveen
 wrote:
> 
> 
> > Just extra information: I just found node-postcss also fails the same
> > way (to confirm it is indeed a gulp issue).
> 
> Is there a way we can find which file brings this error?
> 

Running the following command in node-postcss master

node-postcss$ node --inspect-brk
/usr/share/nodejs/gulp/node_modules/gulp-cli/bin/gulp.js build

And opening chrome://inspect and clicking "Open dedicated DevTools for Node"

Then run script button on top right,

Gives the error is found in this file
file:///usr/lib/nodejs/fancy-log/index.js:22

Bug#929829: [Pkg-javascript-devel] Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

[Pirate Praveen]

Just extra information: I just found node-postcss also fails the same
way (to confirm it is indeed a gulp issue).


Is there a way we can find which file brings this error?

Bug#939147: gcc-7-source 7.4.0-11 vanished from the archive

[Matthias Klose]

Package: ftp.debian.org
Severity: serious

 gcc-7_7.4.0-12_source.changes REJECTED
 Source-only uploads to NEW are not allowed.
 binary:gcc-7-source is NEW.
 no, it's not

 doko: more info. gcc-7-source is only in stable. stable does not accept 
uploads


 waldi: well, then the question is, why not? other binary-indep packages 
like gcc-7-locales are there. and 7.4.0-11 build log lists gcc-7-source as well

 auto-crufted a week or so ago

there seems to be something wrong ...

Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

[Pirate Praveen]

On Thu, 6 Jun 2019 23:09:26 +0200 Xavier  wrote:
> Le 06/06/2019 à 22:28, Xavier a écrit :
> > Le 06/06/2019 à 09:07, Pirate Praveen a écrit :
> >>
> >>
> >> On 2019, ജൂൺ 6 11:00:16 AM IST, Xavier  wrote:
> >>> My reducejs tool gives a new analysis:
> >>> * downgraded modules to embed
> >>>   - process-nextick-args : 2.0.0 => 1.0.7
> >>
> >> This is handled by a patch.
> >>
> >> https://salsa.debian.org/js-team/node-gulp/blob/master/debian/patches/update-process-nextick-args.patch
> > 
> > Things become worst: gulp-babel-8 depends on babel-core >=7 while
> > babel-7 build-depends on gulp-babel >=8.
> 
> Since gulp-babel is a simple JS (src=dist), I think we could embed it in
> debian/node_modules without installing it.
> 
> 

Just extra information: I just found node-postcss also fails the same
way (to confirm it is indeed a gulp issue).

Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[Dmitry Bogatov]

control: tags -1 +moreinfo

[2019-08-30 16:44] Jean-Marc LACROIX 
> Package: sysvinit
> Version: 2.93-8
> Severity: grave
>
> Dear maintainers,
>
> It seems there is a dependency issue when installing sysvinit-core as 
> indicated in following trace
> [...]
> Package: *systemd*
> Pin: release *
> Pin-Priority: -1

I think problem is here. *systemd* matches `libsystemd0`, and given that
even apt depends on `libsystemd0`, you are unlikely to solve any
dependency.

Please:

 * Try installing something else, like `tor'. I expect you will get
   similar error (`tor' depends on libsystemd0, sigh)
 * Replace `*systemd*' with `systemd' (without wildcard) in your
   apt-pinnings and try installing sysvinit-core again.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Processed: Re: Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #938952 [sysvinit] [debian Buster] [arm64 pinebook] [sysvinit-core] 
libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be 
installed
Added tag(s) moreinfo.

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

Processed: Re: Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #938952 [sysvinit] [debian Buster] [arm64 pinebook] [sysvinit-core] 
libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be 
installed
Ignoring request to alter tags of bug #938952 to the same tags previously set

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

Bug#939129: Charset incorrectly omitted from SORT command

[Remco Wulms]

Package: php-horde-imap-client
Version: 2.29.16-1
Severity: grave


Dear maintainer,

A server uses courier-imap and php-horde-imp to read e-mail. After  
upgrading the server from Stretch to Buster, reading e-mail does not  
work anymore; the mailboxes show no e-mails, and a message "IMAP error  
reported by server." is shown.


Analysis of the IMAP interaction between php-horde-imp and courier-imap shows:

C: 6 UID SORT (ARRIVAL) ALL
S: 6 NO Error in IMAP command received by server.

Command 6 took 0.0002 seconds.


I suspect this problem is caused by the fact that the new courier-imap  
supports UTF-8 IMAP (see [1]) and php-horde-imap-client incorrectly  
does not include the charset (being UTF-8) in the UID SORT command.  
The proper IMAP command should have been:


6 UID SORT (ARRIVAL) UTF-8 ALL

It looks like this defect in php-horde-imap-client has been resolved  
upstream; see [2].


In my opinion, this renders php-horde-imp in Buster pretty much  
unusable. Is there any chance this upstream fix can be applied to  
Buster?



[1]  
https://fossies.org/linux/misc/courier-imap-5.0.8.tar.bz2/courier-imap-5.0.8/libs/imap/ChangeLog?m=t
[2]  
https://github.com/horde/Imap_Client/commit/48c4f50b78e4146c7e9a0756b5c7de77ffbb551d

Processed: reassign 939022 to src:pyresample, found 939022 in pyresample/1.12.3-5, affects 939022

[Debian Bug Tracking System]

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

> reassign 939022 src:pyresample
Bug #939022 [pyresample] pyresample: autopkgtest failure with PROJ 6 (epsg data 
file removed)
Bug reassigned from package 'pyresample' to 'src:pyresample'.
No longer marked as found in versions pyresample/1.12.3-5.
Ignoring request to alter fixed versions of bug #939022 to the same values 
previously set
> found 939022 pyresample/1.12.3-5
Bug #939022 [src:pyresample] pyresample: autopkgtest failure with PROJ 6 (epsg 
data file removed)
Marked as found in versions pyresample/1.12.3-5.
> affects 939022 - pyresample
Bug #939022 [src:pyresample] pyresample: autopkgtest failure with PROJ 6 (epsg 
data file removed)
Removed indication that 939022 affects pyresample
> thanks
Stopping processing here.

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

Processed: basemap: AttributeError: module 'pyproj' has no attribute 'pyproj_datadir'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pyresample
Bug #939128 [src:basemap] basemap: AttributeError: module 'pyproj' has no 
attribute 'pyproj_datadir'
Added indication that 939128 affects src:pyresample

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

Bug#939128: basemap: AttributeError: module 'pyproj' has no attribute 'pyproj_datadir'

[Bas Couwenberg]

Source: basemap
Version: 1.2.0+dfsg-2
Severity: serious
Tags: upstream fixed-upstream
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:pyresample

Dear Maintainer,

With transition to PROJ 6 pyproj was updated to 2.x which no longer
provides the pyproj_datadir attribute.

This is fixed upstream in 1.2.1 via #454:

 
https://github.com/matplotlib/basemap/commit/fa8fc4f91f6ba81d87443b09632b691f2e32e576

Kind Regards,

Bas

Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

[Sebastiaan Couwenberg]

On 8/31/19 7:14 PM, Sebastiaan Couwenberg wrote:
>> I'm going to reassign.
> 
> That doesn't seem appropriate, pyresample needs to be updated too. It
> does things like this:
> 
>  pyresample/test/test_geometry.py:
> projections = {'+init=epsg:3006': 'init: epsg:3006'}
> 
> Note the explicit use of init files, this is not going to work correctly
> with PROJ 6.

As sort term workaround may be to skip these tests when
/usr/share/proj/epsg doesn't exist (or when /usr/share/proj/proj.db does
exist).

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#891233: Bug #891233: kamoso: segmentation fault in kamoso in Debian 9 stable. Buster not affected

[Bernhard Übelacker]

Dear Maintainer,
I guess the actual segmentation fault is fixed since kamoso 3.2.4-1.
Instead it should print this message:

The webcam controller was unable to find or load wrappercamerabinsrc plugin;
please make sure all required gstreamer plugins are installed.

The last question would be, is this sufficient to close the bug,
or does kamoso need a dependency or recommends to
gstreamer1.0-plugins-bad?

Kind regards,
Bernhard

Bug#939119: gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled

[Michael Biebl]

[somehow messed up the CC list, s/pkg-gnome/pkg-systemd/]

Am 01.09.19 um 14:44 schrieb Alan Jenkins:
> On 01/09/2019 12:52, Michael Biebl wrote:
>> On 01.09.19 13:24, Alan Jenkins wrote:
>>> Package: gnustep-base-runtime
>>> Version: 1.26.0-4
>>> Severity: grave
>>> Tags: security
>>> Justification: user security hole
>>>
>>> Dear Maintainer,
>>>
>>> I had "gnustep-base-runtime" installed on my system, probably as a
>>> dependency of "unar".
>>>
>>> When I upgrade from Debian 9 to Debian 10 (and reboot), there is a
>>> network server "gdomap".  I did not see this server on Debian 9.
>>> "gdomap" is not wanted.  It is supposed to be disabled by default
>>> since 2013, i.e. in Debian 8.[1]
>>>
>>> [1] #717773 "/usr/bin/gdomap: please split out gdomap or disable it
>>> by default"
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717773
>>>
>>> The problem is due to this code change:
>>>
>>> "Disable gdomap via defaults-disabled as per Policy 9.3.3.1."
>>> https://salsa.debian.org/gnustep-team/gnustep-base/commit/e0da63fa9e341a38a9a493a615c2c36b8f9d418f
>>>
>>>
>>> Salvatore Bonaccorso analyzed this for me:
>>>
 Install a fresh stretch installation and install gnustep-base-runtime
 in it. gdomap is not started by default, because gdomap init honours
 the ENABLED=no setting in /etc/default/gdomap. Now update the host to
 buster.

 During this update /etc/default/gdomap is updated according to the
 above. Unless the admin has modified it, where then it will be
 noticed and admin asked for a decision. As formerly the init was
 enabled, and the code to handle the ENABLED setting is removed this
 might be the problem. The postinst calls update-rc.d gdomap
 defaults-disabled [...]
>>> "update-rc.d" does not do anything in this case.  The man page says
>>>
 If any files named /etc/rcrunlevel.d/[SK]??name already exist then
 update-rc.d does nothing.  The program was written this way so that
 it will never change an existing configuration, which may have been
 customized by the system administrator.  The program will only
 install links if none are present, i.e., if it appears that the
 service has never been installed before.
>> I guess gnustep-base-runtime explicitly needs to remove the existing
>> /etc/rc?.d/???gdomap symlinks on upgrades in preinst (possibly guarded
>> by a check which reads the old /etc/default/gdomap and tests if
>> ENABLED=NO) so they can be properly re-created (and disabled) by
>> "update-rc.d defaults-disabled"
>>
>> That said, I find the severity vastly exagerated, but that's just me.
> 
> Thanks.  In general I don't know what to do with the severity field
> :-).  I maybe used it once before, and that's it.
> 
> IMO this bug is release-relevant.  Then it should be "serious" or above.
> 
> #717773 points out that "unar" was installed by default, e.g. in Debian
> 7 Desktop. "unar" is not removed on upgrade, even after "apt
> autoremove".  Because "file-roller" still has "Suggests: unar".
> 
> #717773 was tagged "security", but the severity was "normal".  The
> current issue is slightly different to #717773, in the sense that it is
> a regression.
> 
> The above is post-hoc.  At the time, I just noticed that "reportbug
> --mode=standard" didn't offer me the "security" tag if I filed at
> severity "normal".  And gdomap doesn't run as root, so it's not a root
> bug ("critical").

I understand that it is unwanted if gdomap is running after the upgrade
when it wasn't before.
What I fail to see is the attach vector here.
Does a running gdomap service mean, the system is automatically
exploitable remotely? This information is missing.


-- 
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#939119: gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled

[Alan Jenkins]

On 01/09/2019 12:52, Michael Biebl wrote:

On 01.09.19 13:24, Alan Jenkins wrote:

Package: gnustep-base-runtime
Version: 1.26.0-4
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

I had "gnustep-base-runtime" installed on my system, probably as a
dependency of "unar".

When I upgrade from Debian 9 to Debian 10 (and reboot), there is a
network server "gdomap".  I did not see this server on Debian 9.
"gdomap" is not wanted.  It is supposed to be disabled by default
since 2013, i.e. in Debian 8.[1]

[1] #717773 "/usr/bin/gdomap: please split out gdomap or disable it by default"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717773

The problem is due to this code change:

"Disable gdomap via defaults-disabled as per Policy 9.3.3.1."
https://salsa.debian.org/gnustep-team/gnustep-base/commit/e0da63fa9e341a38a9a493a615c2c36b8f9d418f

Salvatore Bonaccorso analyzed this for me:


Install a fresh stretch installation and install gnustep-base-runtime
in it. gdomap is not started by default, because gdomap init honours
the ENABLED=no setting in /etc/default/gdomap. Now update the host to
buster.

During this update /etc/default/gdomap is updated according to the
above. Unless the admin has modified it, where then it will be
noticed and admin asked for a decision. As formerly the init was
enabled, and the code to handle the ENABLED setting is removed this
might be the problem. The postinst calls update-rc.d gdomap
defaults-disabled [...]

"update-rc.d" does not do anything in this case.  The man page says


If any files named /etc/rcrunlevel.d/[SK]??name already exist then
update-rc.d does nothing.  The program was written this way so that
it will never change an existing configuration, which may have been
customized by the system administrator.  The program will only
install links if none are present, i.e., if it appears that the
service has never been installed before.

I guess gnustep-base-runtime explicitly needs to remove the existing
/etc/rc?.d/???gdomap symlinks on upgrades in preinst (possibly guarded
by a check which reads the old /etc/default/gdomap and tests if
ENABLED=NO) so they can be properly re-created (and disabled) by
"update-rc.d defaults-disabled"

That said, I find the severity vastly exagerated, but that's just me.


Thanks.  In general I don't know what to do with the severity field 
:-).  I maybe used it once before, and that's it.


IMO this bug is release-relevant.  Then it should be "serious" or above.

#717773 points out that "unar" was installed by default, e.g. in Debian 
7 Desktop. "unar" is not removed on upgrade, even after "apt 
autoremove".  Because "file-roller" still has "Suggests: unar".


#717773 was tagged "security", but the severity was "normal".  The 
current issue is slightly different to #717773, in the sense that it is 
a regression.


The above is post-hoc.  At the time, I just noticed that "reportbug 
--mode=standard" didn't offer me the "security" tag if I filed at 
severity "normal".  And gdomap doesn't run as root, so it's not a root 
bug ("critical").


Alan

Bug#939119: gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled

[Michael Biebl]

On 01.09.19 13:52, Michael Biebl wrote:
> I guess gnustep-base-runtime explicitly needs to remove the existing
> /etc/rc?.d/???gdomap symlinks on upgrades in preinst (possibly guarded
> by a check which reads the old /etc/default/gdomap and tests if
> ENABLED=NO) so they can be properly re-created (and disabled) by
> "update-rc.d defaults-disabled"

But since /etc/default/gdomap could have been upgraded in the mean time,
not finding ENABLED=NO in /etc/default/gdomap probably also means that
you want to remove the /etc/rc?.d/???gdomap symlinks.

That on the other hand could blow away the changes for a system where
gdomap was explicity enable via "update-rc.d enable gdomap", so you need
to handle that case as well (i.e. don't remove the symlinks if there is
no ENABLED= key but a /etc/rc2.d/S??gdomap symlink)


-- 
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#939119: gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled

[Michael Biebl]

On 01.09.19 13:24, Alan Jenkins wrote:
> Package: gnustep-base-runtime
> Version: 1.26.0-4
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> Dear Maintainer,
> 
> I had "gnustep-base-runtime" installed on my system, probably as a
> dependency of "unar".
> 
> When I upgrade from Debian 9 to Debian 10 (and reboot), there is a
> network server "gdomap".  I did not see this server on Debian 9.
> "gdomap" is not wanted.  It is supposed to be disabled by default
> since 2013, i.e. in Debian 8.[1]
> 
> [1] #717773 "/usr/bin/gdomap: please split out gdomap or disable it by 
> default"
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717773
> 
> The problem is due to this code change:
> 
> "Disable gdomap via defaults-disabled as per Policy 9.3.3.1."
> https://salsa.debian.org/gnustep-team/gnustep-base/commit/e0da63fa9e341a38a9a493a615c2c36b8f9d418f
> 
> Salvatore Bonaccorso analyzed this for me:
> 
>> Install a fresh stretch installation and install gnustep-base-runtime
>> in it. gdomap is not started by default, because gdomap init honours
>> the ENABLED=no setting in /etc/default/gdomap. Now update the host to
>> buster.
>>
>> During this update /etc/default/gdomap is updated according to the
>> above. Unless the admin has modified it, where then it will be
>> noticed and admin asked for a decision. As formerly the init was
>> enabled, and the code to handle the ENABLED setting is removed this
>> might be the problem. The postinst calls update-rc.d gdomap
>> defaults-disabled [...]
> 
> "update-rc.d" does not do anything in this case.  The man page says
> 
>> If any files named /etc/rcrunlevel.d/[SK]??name already exist then
>> update-rc.d does nothing.  The program was written this way so that
>> it will never change an existing configuration, which may have been
>> customized by the system administrator.  The program will only  
>> install links if none are present, i.e., if it appears that the 
>> service has never been installed before.

I guess gnustep-base-runtime explicitly needs to remove the existing
/etc/rc?.d/???gdomap symlinks on upgrades in preinst (possibly guarded
by a check which reads the old /etc/default/gdomap and tests if
ENABLED=NO) so they can be properly re-created (and disabled) by
"update-rc.d defaults-disabled"

That said, I find the severity vastly exagerated, but that's just me.


-- 
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#939119: gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled

[Alan Jenkins]

Package: gnustep-base-runtime
Version: 1.26.0-4
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

I had "gnustep-base-runtime" installed on my system, probably as a
dependency of "unar".

When I upgrade from Debian 9 to Debian 10 (and reboot), there is a
network server "gdomap".  I did not see this server on Debian 9.
"gdomap" is not wanted.  It is supposed to be disabled by default
since 2013, i.e. in Debian 8.[1]

[1] #717773 "/usr/bin/gdomap: please split out gdomap or disable it by default"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717773

The problem is due to this code change:

"Disable gdomap via defaults-disabled as per Policy 9.3.3.1."
https://salsa.debian.org/gnustep-team/gnustep-base/commit/e0da63fa9e341a38a9a493a615c2c36b8f9d418f

Salvatore Bonaccorso analyzed this for me:

> Install a fresh stretch installation and install gnustep-base-runtime
> in it. gdomap is not started by default, because gdomap init honours
> the ENABLED=no setting in /etc/default/gdomap. Now update the host to
> buster.
>
> During this update /etc/default/gdomap is updated according to the
> above. Unless the admin has modified it, where then it will be
> noticed and admin asked for a decision. As formerly the init was
> enabled, and the code to handle the ENABLED setting is removed this
> might be the problem. The postinst calls update-rc.d gdomap
> defaults-disabled [...]

"update-rc.d" does not do anything in this case.  The man page says

> If any files named /etc/rcrunlevel.d/[SK]??name already exist then
> update-rc.d does nothing.  The program was written this way so that
> it will never change an existing configuration, which may have been
> customized by the system administrator.  The program will only  
> install links if none are present, i.e., if it appears that the 
> service has never been installed before.

It is unfortunate that "Policy 9.3.3.1" does not have an explicit
warning about this potential security problem.

So this is a problem with upgrades.  It does not happen on a fresh
install of Debian 10.

Salvatore also suggested

> I think it's best handled though in a bugreport accordngly, and once
> fixed in unstable, to schedule a fix as well via a buster point
> release.

$ sudo netstat -l -p
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State   
PID/Program name
...
udp0  0 0.0.0.0:gdomap  0.0.0.0:*   
57/gdomap

$ ps aux | grep gdomap
nobody  57  0.0  0.0   2736  2052 ?Ss   11:16   0:00 
/usr/bin/gdomap -I /var/run/gdomap.pid -p -j /var/run/gdomap

$ dpkg-query -S gdomap
gnustep-base-runtime: /usr/share/man/man8/gdomap.8.gz
gnustep-base-runtime: /etc/default/gdomap
gnustep-base-runtime: /usr/bin/gdomap
gnustep-base-runtime: /etc/init.d/gdomap


[Report sent from a systemd-nspawn container, which I used to reproduce the 
issue]

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

Kernel: Linux 5.2.9-200.fc30.x86_64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnustep-base-runtime depends on:
ii  gnustep-base-common  1.26.0-4
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libgcc1  1:8.3.0-6
ii  libgnustep-base1.26  1.26.0-4
ii  libobjc4 8.3.0-6
ii  lsb-base 10.2019051400

gnustep-base-runtime recommends no packages.

gnustep-base-runtime suggests no packages.

-- no debconf information

Bug#934457: marked as done (installation in chroot failing with Unknown device "/dev/fuse": No such device)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 11:21:13 +
with message-id 
and subject line Bug#934457: fixed in fuse 2.9.9-2
has caused the Debian Bug report #934457,
regarding installation in chroot failing with Unknown device "/dev/fuse": No 
such device
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.)


-- 
934457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fuse
Severity: grave
X-Debbugs-CC: whonix-de...@whonix.org

Dear maintainer,

The following code from /var/lib/dpkg/info/fuse.postinst is failing.

if [ -e /dev/fuse ]
then
 udevadm test --action -p  $(udevadm info -q path -n /dev/fuse)
> /dev/null 2>&1
fi


+ [ -e /dev/fuse ]
+ udevadm info -q path -n /dev/fuse
Unknown device "/dev/fuse": No such device

Happening inside a Debian buster chroot.

Kind regards,
Patrick
--- End Message ---
--- Begin Message ---
Source: fuse
Source-Version: 2.9.9-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 31 Aug 2019 14:44:22 +
Source: fuse
Architecture: source
Version: 2.9.9-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 934457 935496
Changes:
 fuse (2.9.9-2) unstable; urgency=medium
 .
   * Drop outdated udevadm commands from postinst (closes: #934457, #935496).
   * Remove dh_makeshlibs override.
   * Update Lintian overrides.
   * Update Standards-Version to 4.4.0 .
Checksums-Sha1:
 1a638d67e79d11910ff915a9947de7cba734be9a 2290 fuse_2.9.9-2.dsc
 cd0792e77e1a620beb8f8de63d4d5fccb8f7cc0e 22396 fuse_2.9.9-2.debian.tar.xz
Checksums-Sha256:
 cd84d0d45a342518315a3b336b6810bf6c69c5142015ce4a61634c7f0eb3d179 2290 
fuse_2.9.9-2.dsc
 1b74f2cbf8fc95b3efa7170a12e75a67c9ad8f22bab1bc48edd5017ac56d3fd3 22396 
fuse_2.9.9-2.debian.tar.xz
Files:
 800e84031f5aa6a029611f7212c105a5 2290 utils optional fuse_2.9.9-2.dsc
 6aa633389197480b0823f0b0c0e878e8 22396 utils optional 
fuse_2.9.9-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl1rpJsACgkQ3OMQ54ZM
yL9i9Q//XXT/Q2R5+vjOjcAf297e+RxA+vu5Lx4vjXNt0Hs6U3rZ6i80HVAht7w+
8uZOHVxYw6Pk9N5sscxcNm/rYwCW7dgO+dMTopmfMVvIsICngF1sPa3P6WkGAsZg
deqc4gFNRv2x3qLTWxSac/ISP199RmhvViSxy+VRO7745LxWXyhUDGEN2pY97ULK
qWjiLj2luefWDvfvglCDdk1V9wrzgsqT9jjMQtEaT2dgQAm8pCTAFxOewvo1A7qx
+OZ2hLUxGSMoQLR+yzTTFXNUBnwwGfqEvoc7B3dAPUiS67wBOPxQwULWaPJ986ck
Cgj/hmhxxqRFPPS5AdLFtHKCvST8LTlPfmL5Mj8yRqcWV0vN6MLTlDOptFafoFDP
AMxPQBLpo1mg9HouCCB4XUF08bcEaiMqXrtiygW5jFq4RFBV95ewwgqgyJJ0G9T0
Pk6WYHA1mzXq04XyLxdaFCAw5gmCCG8x9Z5ayw2rWHrTLt9xAoGdQ6AwuN7OtEz6
+i7OUcC/rQhx1qXkla5XiywEnf3Fr8RVCk2hNbqlQfn0hBTjND9pABA+8sNor6/c
nsXcQIe3cY7w2upXqCxIum0FUCoiMOxfC22B63VsS6J4+rehUOnUee1qihQ5xFcF
ptuVXY2Gi9yUVxaZep7GOs66iEKpMzgV85vaJLt5T2OT9g5iYYU=
=kkPt
-END PGP SIGNATURE End Message ---

Bug#935496: marked as done (Fails to install: Invalid action '-p')

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 11:21:13 +
with message-id 
and subject line Bug#935496: fixed in fuse 2.9.9-2
has caused the Debian Bug report #935496,
regarding Fails to install: Invalid action '-p'
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.)


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

Trying to run apt (re)install fuse results in

$ sudo apt install --reinstall fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 72.3 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian sid/main amd64 fuse amd64 2.9.9-1 [72.3 kB]
Fetched 72.3 kB in 0s (219 kB/s)
[master ba9ff87] saving uncommitted changes in /etc prior to apt run
 Author: Michael Biebl 
 1 file changed, 5 insertions(+), 5 deletions(-)
(Reading database ... 389058 files and directories currently installed.)
Preparing to unpack .../fuse_2.9.9-1_amd64.deb ...
Unpacking fuse (2.9.9-1) over (2.9.9-1) ...
Setting up fuse (2.9.9-1) ...
dpkg: error processing package fuse (--configure):
 installed fuse package post-installation script subprocess returned error exit 
status 1
Processing triggers for man-db (2.8.6.1-1) ...
Errors were encountered while processing:
 fuse
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looking at the postinst code, the faulty line is
udevadm test --action -p  $(udevadm info -q path -n /dev/fuse) > /dev/null 2>&1

Running that yields
# udevadm test --action -p /devices/virtual/misc/fuse
Invalid action '-p'



I'm not exactly sure what this code is supposed to achieve.
Since fuse no longer ships its own udev rules, maybe it can be dropped
altogether?

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

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

Versions of packages fuse depends on:
ii  adduser   3.118
ii  libc6 2.28-10
ii  libfuse2  2.9.9-1
ii  mount 2.34-0.1
ii  sed   4.7-1

fuse recommends no packages.

fuse suggests no packages.

-- Configuration Files:
/etc/fuse.conf [Errno 13] Keine Berechtigung: '/etc/fuse.conf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fuse
Source-Version: 2.9.9-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 31 Aug 2019 14:44:22 +
Source: fuse
Architecture: source
Version: 2.9.9-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 934457 935496
Changes:
 fuse (2.9.9-2) unstable; urgency=medium
 .
   * Drop outdated udevadm commands from postinst (closes: #934457, #935496).
   * Remove dh_makeshlibs override.
   * Update Lintian overrides.
   * Update Standards-Version to 4.4.0 .
Checksums-Sha1:
 1a638d67e79d11910ff915a9947de7cba734be9a 2290 fuse_2.9.9-2.dsc
 cd0792e77e1a620beb8f8de63d4d5fccb8f7cc0e 22396 fuse_2.9.9-2.debian.tar.xz
Checksums-Sha256:
 cd84d0d45a342518315a3b336b6810bf6c69c5142015ce4a61634c7f0eb3d179 2290 
fuse_2.9.9-2.dsc
 1b74f2cbf8fc95b3efa7170a12e75a67c9ad8f22bab1bc48edd5017ac56d3fd3 22396 
fuse_2.9.9-2.debian.tar.xz
Files:
 800e84031f5aa6a029611f7212c105a5 2290 utils optional fuse_2.9.9-2.dsc
 6aa633389197480b0823f0b0c0e878e8 22396 utils optional 
fuse_2.9.9-2.debian.tar.xz

-BEGIN PGP 

Bug#935885: marked as done (fuse installtion postinst script syntax error)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 11:21:13 +
with message-id 
and subject line Bug#935496: fixed in fuse 2.9.9-2
has caused the Debian Bug report #935496,
regarding fuse installtion postinst script syntax error
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.)


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

I upgraded from stretch to sid. when the upgrade reached the fuse package
it failed with error:

dpkg: error processing fuse (--configure):
subprocess installed post-installation script returned error exit status 1

So I ran:

sudo vi /var/lib/dpkg/info/fuse.postins

and changed line 34 from:

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

to

udevadm test --action add  $(udevadm info -q path -n /dev/fuse)
--- End Message ---
--- Begin Message ---
Source: fuse
Source-Version: 2.9.9-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 31 Aug 2019 14:44:22 +
Source: fuse
Architecture: source
Version: 2.9.9-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 934457 935496
Changes:
 fuse (2.9.9-2) unstable; urgency=medium
 .
   * Drop outdated udevadm commands from postinst (closes: #934457, #935496).
   * Remove dh_makeshlibs override.
   * Update Lintian overrides.
   * Update Standards-Version to 4.4.0 .
Checksums-Sha1:
 1a638d67e79d11910ff915a9947de7cba734be9a 2290 fuse_2.9.9-2.dsc
 cd0792e77e1a620beb8f8de63d4d5fccb8f7cc0e 22396 fuse_2.9.9-2.debian.tar.xz
Checksums-Sha256:
 cd84d0d45a342518315a3b336b6810bf6c69c5142015ce4a61634c7f0eb3d179 2290 
fuse_2.9.9-2.dsc
 1b74f2cbf8fc95b3efa7170a12e75a67c9ad8f22bab1bc48edd5017ac56d3fd3 22396 
fuse_2.9.9-2.debian.tar.xz
Files:
 800e84031f5aa6a029611f7212c105a5 2290 utils optional fuse_2.9.9-2.dsc
 6aa633389197480b0823f0b0c0e878e8 22396 utils optional 
fuse_2.9.9-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl1rpJsACgkQ3OMQ54ZM
yL9i9Q//XXT/Q2R5+vjOjcAf297e+RxA+vu5Lx4vjXNt0Hs6U3rZ6i80HVAht7w+
8uZOHVxYw6Pk9N5sscxcNm/rYwCW7dgO+dMTopmfMVvIsICngF1sPa3P6WkGAsZg
deqc4gFNRv2x3qLTWxSac/ISP199RmhvViSxy+VRO7745LxWXyhUDGEN2pY97ULK
qWjiLj2luefWDvfvglCDdk1V9wrzgsqT9jjMQtEaT2dgQAm8pCTAFxOewvo1A7qx
+OZ2hLUxGSMoQLR+yzTTFXNUBnwwGfqEvoc7B3dAPUiS67wBOPxQwULWaPJ986ck
Cgj/hmhxxqRFPPS5AdLFtHKCvST8LTlPfmL5Mj8yRqcWV0vN6MLTlDOptFafoFDP
AMxPQBLpo1mg9HouCCB4XUF08bcEaiMqXrtiygW5jFq4RFBV95ewwgqgyJJ0G9T0
Pk6WYHA1mzXq04XyLxdaFCAw5gmCCG8x9Z5ayw2rWHrTLt9xAoGdQ6AwuN7OtEz6
+i7OUcC/rQhx1qXkla5XiywEnf3Fr8RVCk2hNbqlQfn0hBTjND9pABA+8sNor6/c
nsXcQIe3cY7w2upXqCxIum0FUCoiMOxfC22B63VsS6J4+rehUOnUee1qihQ5xFcF
ptuVXY2Gi9yUVxaZep7GOs66iEKpMzgV85vaJLt5T2OT9g5iYYU=
=kkPt
-END PGP SIGNATURE End Message ---

Bug#939101: elogind: elogind 239 in bullseye FTBFS with gcc-9

[Mark Hindley]

On Sun, Sep 01, 2019 at 11:33:55AM +0100, Mark Hindley wrote:
> The issue appears to be the STRING_FOREACH macro and was fixed in
> systemd in v241:

Sorry, that should be FOREACH_STRING macro.

Mark

Processed: Re: Bug#935885: fuse installtion postinst script syntax error

[Debian Bug Tracking System]

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

> merge 935885 935916
Bug #935885 [fuse] fuse installtion postinst script syntax error
Bug #935916 [fuse] Debian testing net installation fails while "configuring 
fuse"
Merged 935885 935916
> tags 935916 = bullseye sid
Bug #935916 [fuse] Debian testing net installation fails while "configuring 
fuse"
Bug #935885 [fuse] fuse installtion postinst script syntax error
Added tag(s) bullseye and sid.
Added tag(s) bullseye and sid.
> severity 935916 serious
Bug #935916 [fuse] Debian testing net installation fails while "configuring 
fuse"
Bug #935885 [fuse] fuse installtion postinst script syntax error
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> merge 935496 935916
Bug #935496 [fuse] Fails to install: Invalid action '-p'
Bug #935885 [fuse] fuse installtion postinst script syntax error
Bug #935916 [fuse] Debian testing net installation fails while "configuring 
fuse"
Merged 935496 935885 935916
> thanks
Stopping processing here.

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

Bug#939101: elogind: elogind 239 in bullseye FTBFS with gcc-9

[Mark Hindley]

Package: elogind
Version: 239.3+20190131-1+debian1
Severity: serious
Control: fixed -1 241.3-1+debian1
Control: block -1 by 934132

Reproducible builds of src:elogind 239.3+20190131-1+debian1 in bullseye
have FTBFS for the last few days. This seems to be related to the
migration of gcc-9 to bullseye.

The issue appears to be the STRING_FOREACH macro and was fixed in
systemd in v241:

 https://github.com/systemd/systemd/issues/11394
 https://bugzilla.opensuse.org/show_bug.cgi?id=1121387#c0

This fix is already included in elogind 241.3-1+debian1 which is in
unstable. However, migration of elogind 241.3-1+debian1 to bullseye is
currently blocked (see #934132). When it is unblocked it should resolve
this issue.

Mark

Processed: elogind: elogind 239 in bullseye FTBFS with gcc-9

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 241.3-1+debian1
Bug #939101 [elogind] elogind: elogind 239 in bullseye FTBFS with gcc-9
Marked as fixed in versions elogind/241.3-1+debian1.
> block -1 by 934132
Bug #939101 [elogind] elogind: elogind 239 in bullseye FTBFS with gcc-9
939101 was not blocked by any bugs.
939101 was not blocking any bugs.
Added blocking bug(s) of 939101: 934132

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

Bug#874867: marked as done ([fbreader] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 09:19:06 +
with message-id 
and subject line Bug#874867: fixed in fbreader 0.12.10dfsg2-4
has caused the Debian Bug report #874867,
regarding [fbreader] Future Qt4 removal from Buster
to be marked as done.

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

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


-- 
874867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fbreader
Version: 0.12.10dfsg2-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: fbreader
Source-Version: 0.12.10dfsg2-4

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

Debian distribution maintenance software
pp.
Eugene V. Lyubimkin  (supplier of updated fbreader 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, 01 Sep 2019 10:59:46 +0200
Source: fbreader
Architecture: source
Version: 0.12.10dfsg2-4
Distribution: unstable
Urgency: medium
Maintainer: Eugene V. Lyubimkin 
Changed-By: Eugene V. Lyubimkin 
Closes: 861770 874867
Changes:
 fbreader (0.12.10dfsg2-4) unstable; urgency=medium
 .
   * debian/control:
 - Drop Qt4 UI (libzlui-qt4), as Qt4 is going away. (Closes: #874867)
   * debian/patches:
 - New patch 0013-fbreader-Makefile-make-linking-order-reproducible, by
   Chris Lamb. (Closes: 861770)
Checksums-Sha1:
 c6ac523c530c557f1bfbf7cd09409ea9d0f70f6c 2304 fbreader_0.12.10dfsg2-4.dsc
 ab2354e7c514a1a43f391c0fbbc9a9716317a34b 22014 fbreader_0.12.10dfsg2-4.diff.gz
 5ebb7cc6c8ecfa16b5f4f0a944bdf74aefc35c31 6426 
fbreader_0.12.10dfsg2-4_source.buildinfo
Checksums-Sha256:
 944203e736d27837d30d925c355548b09d5da933df6d82434ceb0a1fed71df00 2304 
fbreader_0.12.10dfsg2-4.dsc
 2ac7e2e283ccd2dd9fef6a5fcb6bc5e3d3a4f61df9d35391a9aabfcbdd7b38cf 22014 
fbreader_0.12.10dfsg2-4.diff.gz
 037c94a16066123ccedd819c05d5767d69d3317f84e2bb6fae76fda6ae50f9df 6426 
fbreader_0.12.10dfsg2-4_source.buildinfo
Files:
 96938a846426861cda314d66e4ffd3c9 2304 text optional fbreader_0.12.10dfsg2-4.dsc
 c2728d638e9ea3940e6ed0c82f2cba68 22014 text optional 
fbreader_0.12.10dfsg2-4.diff.gz
 cb442b5f46528bd604d5a9e1de70deda 6426 text optional 
fbreader_0.12.10dfsg2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#935577: marked as done (debhelper: dh_makeshlibs confused by --add-udeb (broken in 12.5.3))

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 08:41:04 +
with message-id 
and subject line Bug#935577: fixed in debhelper 12.5.4
has caused the Debian Bug report #935577,
regarding debhelper: dh_makeshlibs confused by --add-udeb (broken in 12.5.3)
to be marked as done.

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

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


-- 
935577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debhelper
Version: 12.5.3
Severity: important

Debhelper 12.5.3 breaks building libgcrypt20 1.8.4-5, the build fails at:
--
(sid)ametzler@argenau:/tmp/GCR/libgcrypt-1.8.4$ fakeroot dh_makeshlibs -V 
'libgcrypt20 (>=1.8.0-0)' --add-udeb=libgcrypt20-udeb
dh_makeshlibs: libgcrypt20-udeb contains SO library libgcrypt (version 20) but 
libgcrypt20-doc does not contain a similar library!?
dh_makeshlibs: Rejecting the generated shlibs file for libgcrypt20-udeb!
dh_makeshlibs: Hint: Either add the missing libraries to libgcrypt20-doc, 
remove them from libgcrypt20-udeb, or
dh_makeshlibs: Hint: (if this difference is expected) pass 
"--add-udeb=libgcrypt20-udeb" to dh_makeshlibs.
dh_makeshlibs: Hint: In the latter case, you *may* also need to combine it with 
"-plibgcrypt20-doc"
dh_makeshlibs: libgcrypt20-udeb contains SO library libgcrypt (version 20) but 
libgcrypt20-dev does not contain a similar library!?
dh_makeshlibs: Rejecting the generated shlibs file for libgcrypt20-udeb!
dh_makeshlibs: Hint: Either add the missing libraries to libgcrypt20-dev, 
remove them from libgcrypt20-udeb, or
dh_makeshlibs: Hint: (if this difference is expected) pass 
"--add-udeb=libgcrypt20-udeb" to dh_makeshlibs.
dh_makeshlibs: Hint: In the latter case, you *may* also need to combine it with 
"-plibgcrypt20-dev"
dh_makeshlibs: libgcrypt20-udeb contains SO library libgcrypt (version 20) but 
libgcrypt-mingw-w64-dev does not contain a similar library!?
dh_makeshlibs: Rejecting the generated shlibs file for libgcrypt20-udeb!
dh_makeshlibs: Hint: Either add the missing libraries to 
libgcrypt-mingw-w64-dev, remove them from libgcrypt20-udeb, or
dh_makeshlibs: Hint: (if this difference is expected) pass 
"--add-udeb=libgcrypt20-udeb" to dh_makeshlibs.
dh_makeshlibs: Hint: In the latter case, you *may* also need to combine it with 
"-plibgcrypt-mingw-w64-dev"
dh_makeshlibs: failing due to earlier errors
--

This was introduced in 12.5.3, all other 12.x versions of debhelper
succeed.  (This is with compat level 11)

I can work around this by removing --add-udeb but this should be a no-op
here.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 12.5.4

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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: Sun, 01 Sep 2019 07:23:05 +
Source: debhelper
Architecture: source
Version: 12.5.4
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Closes: 935577 935780
Changes:
 debhelper (12.5.4) unstable; urgency=medium
 .
   * dh_installxfonts: Remove version in dependency on xfonts-utils
 added to ${misc:Depends}.  The version requirement has been
 satisfied for the past 3-4 releases.
   * dh_makeshlibs: Correct a control check that was only intended
 for automatic udeb detection, which incorrectly also checked
 when --add-udeb was passed.  Thanks to Andreas Metzler for
 reporting the issue.  (Closes: #935577)
   * dh: Fix bug where overrides for dh_dwz, dh_strip, dh_makeshlibs
 or dh_shlibdeps could be triggered via binary-indep in compat
 12 and earlier.  Thanks to Andreas Beckmann for reporting the
 issue.  (Closes: #935780)
Checksums-Sha1:
 65fbc2414e6d3b386b9e37dd06c80d29bc9d0e06 1714 debhelper_12.5.4.dsc

Bug#935780: marked as done (debhelper: adds dh_makeshlibs, dh_shlibdeps to the binary-indep sequence)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 08:41:04 +
with message-id 
and subject line Bug#935780: fixed in debhelper 12.5.4
has caused the Debian Bug report #935780,
regarding debhelper: adds dh_makeshlibs, dh_shlibdeps to the binary-indep 
sequence
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.)


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

Hi,

debhelper 12.5.* breaks the arch:all (only) build of nvidia-cuda-toolkit
(debhelper-compat (= 12)).
The binary-indep now runs the override_dh_makeshlibs (no-op) and
override_dh_shlibdeps (fails) targets, the latter does not expect being
run with no shared library being built.

Compare
https://buildd.debian.org/status/fetch.php?pkg=nvidia-cuda-toolkit=all=10.1.105-3=1565991064=0
(debhelper 12.4) to the attached buildlog using debhelper 12.5.3

I can reproduce similar errors with gdk-pixbuf/experimental during a
binary-indep-only build.


Andreas


nvidia-cuda-toolkit_10.1.105-3_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 12.5.4

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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: Sun, 01 Sep 2019 07:23:05 +
Source: debhelper
Architecture: source
Version: 12.5.4
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Closes: 935577 935780
Changes:
 debhelper (12.5.4) unstable; urgency=medium
 .
   * dh_installxfonts: Remove version in dependency on xfonts-utils
 added to ${misc:Depends}.  The version requirement has been
 satisfied for the past 3-4 releases.
   * dh_makeshlibs: Correct a control check that was only intended
 for automatic udeb detection, which incorrectly also checked
 when --add-udeb was passed.  Thanks to Andreas Metzler for
 reporting the issue.  (Closes: #935577)
   * dh: Fix bug where overrides for dh_dwz, dh_strip, dh_makeshlibs
 or dh_shlibdeps could be triggered via binary-indep in compat
 12 and earlier.  Thanks to Andreas Beckmann for reporting the
 issue.  (Closes: #935780)
Checksums-Sha1:
 65fbc2414e6d3b386b9e37dd06c80d29bc9d0e06 1714 debhelper_12.5.4.dsc
 61c1a8b635a14362171ae5f8bc900efc92a2c938 500788 debhelper_12.5.4.tar.xz
 ae7ffac5597627590bdfd6e0a1a73939165faeb2 4508 debhelper_12.5.4_source.buildinfo
Checksums-Sha256:
 94f3cd69fba7dc32803665cbce5fe2c9668b052c0beebb041d0bc42c00c53e13 1714 
debhelper_12.5.4.dsc
 6f109f78fc7b24b23caf1db56d66712b3f5a0a0964b0d16e610eeb0c1b92896b 500788 
debhelper_12.5.4.tar.xz
 30c3d7f843b74bc315eba44dacef03a4390f0e3fee4410f340dff4ac4a4cd4b7 4508 
debhelper_12.5.4_source.buildinfo
Files:
 e6703228089bdc24472744e60fe88af4 1714 devel optional debhelper_12.5.4.dsc
 8211a6b275fa0c019b02ddb5f5e0a197 500788 devel optional debhelper_12.5.4.tar.xz
 1a48de63e109cef2ab6b31b54b24606c 4508 devel optional 
debhelper_12.5.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAl1rd6ISHG5pZWxzQHRo
eWtpZXIubmV0AAoJEKZbeNvmfHqsZl8QAMBI2vybzrHfCxQfmIaSgdzdhfGLeb8L
71NtVtDUwM6taRTKISdmEjfoYeELPImwPen0Fj30POJy8y/0ZG6e/yUj16ZQyTx4
ctLOpxK5EFKk+Dtzgb/gTfiM012V+k7j2qF88k6Qw95pvNoV1cx8aInakhZEOzO4
HK+bbQvTvCDazL3620Na34rjMUpL6tHeZMVFhtU+dpLhU2VzLli9ezADZQbwgeoO
PGa35IPFPhsPEkIXRx5JXsVFVJ6aMm56zxfpwd9iHJJrtepCA2NsvtLX2L8UVGsG
KfXCseluMr/14TLXK3xwfhPoVbS2e8vN5VszLVrAGwuSB9Rms+IksEIGkZFtf4KT
F7RCf74QyRR8bxfqnzcXkr/U5lGOUw/3uqL5VO6BDKdJ8Pr9hHjY7+5AaIVKq1CX
oj5Q3pUmEppAxtvDdlAnvP1XMHtXd+jQZtpc21N8f5UlXXoMOTdoKwnCyUKeB31v
tO6pZCUvqiB3gKOHfCgecMB3p7R1bXCFliC6DM//HT0mrvMNaHa5uwC4oRDbIW/O
rTgcffxYGVYdEFvms0vnXTWOEdG9k2ttkP8/dKo7JU/XlmPjnJAygtHvoCgf98vu
W3eFXOtn/EnkJ4ldw2a2ThIlLO0x3h1rQX7eBsPS1V07b4J0uj98em82CCMYPj0U
YjMtzCjevsb9
=7245
-END PGP SIGNATURE End Message ---

Processed: severity of 931943 is serious

[Debian Bug Tracking System]

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

> severity 931943 serious
Bug #931943 {Done: Gert Wollny } [src:vtk6] vtk6: FTBFS with 
PROJ 6
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: found 939022 in pyresample/1.12.3-5

[Debian Bug Tracking System]

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

> found 939022 pyresample/1.12.3-5
Bug #939022 [pyresample] pyresample: autopkgtest failure with PROJ 6 (epsg data 
file removed)
Marked as found in versions pyresample/1.12.3-5.
> thanks
Stopping processing here.

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

Processed: reassign 939022

[Debian Bug Tracking System]

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

> reassign 939022 pyresample
Bug #939022 [basemap] pyresample: autopkgtest failure with PROJ 6 (epsg data 
file removed)
Bug reassigned from package 'basemap' to 'pyresample'.
Ignoring request to alter found versions of bug #939022 to the same values 
previously set
Ignoring request to alter fixed versions of bug #939022 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#934293: marked as done (fuse3.postinst fails)

[Debian Bug Tracking System]

Your message dated Sun, 01 Sep 2019 06:49:36 +
with message-id 
and subject line Bug#934293: fixed in fuse3 3.6.2-1
has caused the Debian Bug report #934293,
regarding fuse3.postinst fails
to be marked as done.

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

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


-- 
934293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fuse3
Version: 3.4.1-1
Severity: normal

root@nuc8:/home/roderich# apt install fuse3
...
Setting up fuse3 (3.4.1-1) ...
dpkg: error processing package fuse3 (--configure):
 installed fuse3 package post-installation script subprocess returned error
exit status 1
Errors were encountered while processing:
 fuse3
E: Sub-process /usr/bin/dpkg returned an error code (1)


The problem is line 34 of fuse3.postint, running it by hand gives

root@nuc8:/home/roderich# udevadm test --action -p  $(udevadm info -q path -n
/dev/fuse)
Invalid action '-p'


Cheers, Roderich




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

Kernel: Linux 5.2.7 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fuse3 depends on:
ii  adduser 3.118
ii  libc6   2.28-10
ii  libfuse3-3  3.4.1-1
ii  lsb-base10.2019051400
ii  mount   2.34-0.1
ii  sed 4.7-1

fuse3 recommends no packages.

fuse3 suggests no packages.

-- Configuration Files:
/etc/fuse.conf [Errno 2] No such file or directory: '/etc/fuse.conf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fuse3
Source-Version: 3.6.2-1

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fuse3 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: Sun, 01 Sep 2019 06:15:20 +
Source: fuse3
Architecture: source
Version: 3.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 934293
Changes:
 fuse3 (3.6.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * Drop outdated udevadm commands from postinst (closes: #934293).
   * Remove dh_makeshlibs override.
   * Update Standards-Version to 4.4.0 .
Checksums-Sha1:
 6d5f7f030e85a03265357b054e6eb533bf9b04ee 2327 fuse3_3.6.2-1.dsc
 2bdef7a3f1f9e63fed87559c6e77d27e5f2c2e0c 126 fuse3_3.6.2.orig.tar.xz
 32dff1bd03d43226eb833be6a7897cce00e6aa2f 1012 fuse3_3.6.2.orig.tar.xz.asc
 1761c11fce6ba2ccbfdab8332cfc8fe62d4c8534 16552 fuse3_3.6.2-1.debian.tar.xz
Checksums-Sha256:
 e5b48112d6874035f71a94fa6525b2098987d162e0cfec2916bbc19782fe3269 2327 
fuse3_3.6.2-1.dsc
 f45869427575e1e59ab743a67deb57addbf2cb8f9ce431199dbd40ddab71f281 126 
fuse3_3.6.2.orig.tar.xz
 f4f7d6139ef2ba5de395c34aee50ab1c9eb5b27b77c13155fff5da6db32f9edf 1012 
fuse3_3.6.2.orig.tar.xz.asc
 61db31529bf2e6c10398c8e047a3d322a8cd4545dd15b8ec4c76915398d0cf07 16552 
fuse3_3.6.2-1.debian.tar.xz
Files:
 2a1177ebf29c4ac0989fb8837c7e491b 2327 utils optional fuse3_3.6.2-1.dsc
 1798945aa69434286723ba141c7a 126 utils optional fuse3_3.6.2.orig.tar.xz
 b86f354336e6231029d8939adf9fd91d 1012 utils optional 
fuse3_3.6.2.orig.tar.xz.asc
 c2a1a400e8dd37544e0b6f955ec50c56 16552 utils optional 
fuse3_3.6.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl1rZe0ACgkQ3OMQ54ZM
yL+N5BAAlOmtcc7fp8Kwovqy/IrJ81FK089RgsyxtxHCCCGyOQKre3if+iB4i782
3SmUj/piLsyAolXe1TjWeBtKQi3b0NwR65C7jDyLjpLXsFB9pYs3OHSex7kPQNQk
KFTZfFrqSPw2lDU0tNFbhOz9hABxl7k1flkbdhQXwZCtjB861/4BA4VpImQOQPco
RD6yp3GceY8dgoKpJTZdkmvc0LZgyOgQcU/nEEA5jWpeJJaQ+HGbEccOv+pmFgPZ
evJPYEXC1T2B4D5jYXgeP1U2HNPvJaash3bOIEGG08Oog6TW6eMWwXYTgtOw48uq