Bug#941857: marked as done (Z3 4.8.4 contains cache bugs and should not be packaged)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 08:19:22 +0200
with message-id 
and subject line fixed
has caused the Debian Bug report #941857,
regarding Z3 4.8.4 contains cache bugs and should not be packaged
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.)


-- 
941857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: z3
Version: 4.8.4-1
Severity: serious
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer.
It is good to see Z3 4.8.4 finally being packaged in Debian!

As i have personally just encountered, that version contains some bugs,
that result in incorrect modelling, which effectively renders the whole
library unusable. Upstream developer, Nuno Lopes, notes:
> https://github.com/AliveToolkit/alive2/issues/122
> https://github.com/AliveToolkit/alive2/issues/123#issuecomment-538761842
> BTW, it's important to have a recent Z3 so you can get the counterexample
> above. I fixed a bug a while ago in Z3's model cache (I don't remember which
> release it integrated).

I have manually rebuilt z3-4.8.6 from salsa and `sudo dpkg -i` it.
That resolved the bugs i was observing.

I personally consider these bugs to be fatal to the package,
as in it would be better to unpackage said package version.
Given that 4.8.6 is ready to be packaged thanks to the work of
Fabian Wolff, it may be good to proceed with that.

Roman.

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

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

Versions of packages z3 depends on:
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-8
ii  libstdc++6  9.2.1-8

z3 recommends no packages.

z3 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAl2aIgcACgkQCDw+u0oW
ieDzoA//XwAtgmtGsnsK6siLKlGmpnDw3kMrNVwNx7HgBAyBc87q/ag0OuoZ5HdY
iEi302NPH84dAcF8xLK0XgrPAMiBYHnm5AerRzVV7hiZ9x1nbBrW9Ueo4pItBZKv
vf38PQpXdiMf7oXyn9vaarmAJXpOM/aenfjqit+8gBz1c0UobdIDNhY2/ZZ3xEG7
Ca3xFzqVvIwCJRuGiFwqr1zlP1opvEkLaTZ2N77/9bkYArAs36vJfISSyUpMztLJ
6nvFNKhROLUrEVIQzr97QojjWC57PLVpiYkGuLriDKkCi5gSLcVLzgTevh2aNKkW
dEZCoWjEFyMRi1HXqorgBZSoOKqI850rAtx58EE9MA7eiu+rHrHSuezFSGYPKI8W
RQoMBMXiTBPDZ7cKG6QvQ2J3ITscwqE6Oc0w3VYpK57eGjdQ8hWCRJagdBpEyzTv
/xfJHOisTFMwz7SH179EuavnYvS2I0IWcHuS0/pHkra0P4cweaQ4tw0qrQhbdJsu
GEh98u6/qHO0A2vIi+0/Q5b1I5h6ViwDlipv7o57q60+hSqKzanzdchg3vg/A65S
MuoJM7WoD7OkxBUThiFgHSjJCjMGGhF/XWLLseKOmM7FHQgZVhmnEDZPgqKqnDnS
kGQsa0tpt6w1IJfvFUWpnZfUNLS119ncphLrW0h7tL7K2WfICHA=
=SmuQ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

fixed 941857 4.8.6-1
thanks--- End Message ---

Processed: fixed

[Debian Bug Tracking System]

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

> fixed 941857 4.8.6-1
Bug #941857 [z3] Z3 4.8.4 contains cache bugs and should not be packaged
Marked as fixed in versions z3/4.8.6-1.
> thanks
Stopping processing here.

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

Bug#942135: Bug#891877: Have either synaptic removed or have it rebuilt with libgtk3-perl in it recommends.

[Michael Vogt]

On Sun, Oct 13, 2019 at 05:58:30AM +0200, intrigeri wrote:
> Hi,
Hi,

> shirish शिरीष:
> > Dunno if this is the right place to discuss it or not. Integri asked
> > hence sharing.
[..]
> AFAICT:
> 
>  - The synaptic codebase does not use libgtk2-perl directly.
>  - This Recommends is historically in place so that the user
>can benefit from debconf's GNOME frontend.
>  - debconf's GNOME frontend has been ported to libgtk3-perl 1.5 years
>ago (first released in 1.5.66):
>https://salsa.debian.org/pkg-debconf/debconf/commit/0250616b
> 
> Hence, the current "Recommends: libgtk2-perl" has been useless
> for a year an a half. With libgtk2-perl being phased out,
> this Recommends is now a more serious problem. On top of that,
> a suitable dependency on libgtk3-perl is missing.
> 
> Jeremy Bicha filed #891877 a while ago, requesting that Synaptic's
> dependencies are updated accordingly. I believe the actions Jeremy
> suggested on #891877 will solve the problem shirish is raising here,
> improve the life of Synaptic's users, and make it clearer what is the
> status of libgtk2-perl in the archive.
> 
> Thoughts?
> 
> (Oh my, so many words for a bug that can be fixed by s/2/3/ in one
> single place :)

Thanks for looking into this and sorry that this slipped my radar. I
updated the dependency in git and depending on urgency can do an
upload very soon - I guess we want one quickly?

Cheers,
 Michael

Bug#935042: Program phones home by default

[Birger Schacht]

Hi,

On 10/13/19 11:16 PM, Robie Basak wrote:
> On Sun, Oct 13, 2019 at 11:02:45PM +0200, Birger Schacht wrote:
>> The problem is that the package will be removed from unstable in a
>> couple of days because of this bug report. 3 month is sometimes not that
>> much time to fix a bug or even comment on a bug report. And the release
>> of bullseye is not even in sight. I or someone else could do an NMU, but
>> the package will be removed from the archive before that can happen.
> 
> It sounds like you would like to change Debian's process for handling
> serious bugs then, rather than having any particular issue with this bug
> specifically? That might be a discussion better had on the debian-devel@
> list.

No, thats definitly not what I want. I simply think that filing an RC
bug for something thats easily fixed and not violating policy is
escalating too quickly. As I said, I'm happy to do an NMU, I just don't
have timd to do that right away, but if the package is gone from Debian
by then I wont bother.

cheers,
Birger

Bug#942229: marked as done (llvm-toolchain-9: Fails to compile on i386)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 07:43:28 +0200
with message-id <9215076f-27a1-37c5-00ab-9fef31bd2...@debian.org>
and subject line Re: llvm-toolchain-9: Fails to compile on i386
has caused the Debian Bug report #942229,
regarding llvm-toolchain-9: Fails to compile on i386
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.)


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

Trying to build the i386 llvm-9 packages in a chroot by typing "debuild" fails 
with:

make[5]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make -f tools/clang/CMakeFiles/stage2.dir/build.make 
tools/clang/CMakeFiles/stage2.dir/build
make[5]: Entering directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
[100%] Performing configure step for 'stage2'
cd 
/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/tools/clang/stage2-bins 
&& /usr/bin/cmake -DCMAKE_INSTALL_PREFIX=/usr/lib/llvm-9 "-DCMAKE_CXX_FLAGS= 
-fuse-ld=gold -fPIC -Wno-unused-command-line-argument 
-Wno-unknown-warning-option" "-DCMAKE_C_FLAGS= -fuse-ld=gold -fPIC 
-Wno-unused-command-line-argument -Wno-unknown-warning-option" 
-DCMAKE_INSTALL_PREFIX=/usr/lib/llvm-9 -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=RelWithDebInfo "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO=-O2 
-DNDEBUG -g1" -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_INSTALL_UTILS=ON 
-DLLVM_VERSION_SUFFIX= -DLLVM_ENABLE_SPHINX=ON -DSPHINX_WARNINGS_AS_ERRORS=OFF 
-DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_ENABLE_RTTI=ON -DLLVM_ENABLE_FFI=ON 
-DLIBCLANG_LIBRARY_VERSION=1 -DENABLE_LINKER_BUILD_ID=ON 
-DPOLLY_BUNDLED_JSONCPP=OFF -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=AVR 
-DLLVM_USE_PERF=yes -DLLVM_ENABLE_ASSERTIONS=OFF 
-DLLVM_BINUTILS_INCDIR=/usr/include -DLLVM_HOST_TRIPLE=x86_64-pc-linux-gnu 
-DLLVM_COMPILER_CHECKED=ON -DCOMPILER_RT_BUILD_BUILTINS=ON 
-DLIBOMP_LIBFLAGS=-latomic "-DCMAKE_SHARED_LINKER_FLAGS=-latomic -Wl,-z,defs 
-Wl,-z,nodelete -flto=thin" -DPYTHON_EXECUTABLE=/usr/bin/python3 
-DPACKAGE_VERSION=9.0.0 -DLLVM_VERSION_MAJOR=9 -DLLVM_VERSION_MINOR=0 
-DLLVM_VERSION_PATCH=0 -DCLANG_VERSION_MAJOR=9 -DCLANG_VERSION_MINOR=0 
-DCLANG_VERSION_PATCHLEVEL=0 -DLLVM_VERSION_SUFFIX= 
-DLLVM_BINUTILS_INCDIR=/usr/include -DCLANG_REPOSITORY_STRING= 
-DCMAKE_MAKE_PROGRAM=/usr/bin/make -DLLVM_ENABLE_PROJECTS= -DCLANG_STAGE=stage2 
-DCMAKE_CXX_COMPILER=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/clang++
 
-DCMAKE_C_COMPILER=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/clang
 
-DCMAKE_ASM_COMPILER=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/clang
 -DCMAKE_ASM_COMPILER_ID=Clang -DCMAKE_VERBOSE_MAKEFILE=On 
-DCMAKE_AR=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/llvm-ar
 
-DCMAKE_RANLIB=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/llvm-ranlib
 "-GUnix Makefiles" /usr/local/src/test/stage/llvm-toolchain-9-9
Re-run cmake no build system arguments
-- Could NOT find Z3: Found unsuitable version "0.0.0", but required is at 
least "4.7.1" (found Z3_LIBRARIES-NOTFOUND)
CMake Error at cmake/config-ix.cmake:320 (message):
  libffi includes are not found.
Call Stack (most recent call first):
  CMakeLists.txt:618 (include)


-- Configuring incomplete, errors occurred!
See also 
"/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/tools/clang/stage2-bins/CMakeFiles/CMakeOutput.log".
See also 
"/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/tools/clang/stage2-bins/CMakeFiles/CMakeError.log".
make[5]: *** [tools/clang/CMakeFiles/stage2.dir/build.make:109: 
tools/clang/stage2-stamps/stage2-configure] Error 1
make[5]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[4]: *** [CMakeFiles/Makefile2:46011: 
tools/clang/CMakeFiles/stage2.dir/all] Error 2
make[4]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[3]: *** [CMakeFiles/Makefile2:46018: 
tools/clang/CMakeFiles/stage2.dir/rule] Error 2
make[3]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[2]: *** [Makefile:14060: stage2] Error 2
make[2]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[1]: *** [debian/rules:430: debian-full-build] Error 2
make[1]: Leaving directory '/usr/local/src/test/stage/llvm-toolchain-9-9'
make: *** [debian/rules:271: binary] Error 2
dpkg-buildpackage: error: debian/rules binary 

Processed: Raise py2removal severities

[Debian Bug Tracking System]

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

> severity 936189 serious
Bug #936189 [src:bcfg2] bcfg2: Python2 removal in sid/bullseye
Ignoring request to change severity of Bug 936189 to the same value.
> severity 937068 serious
Bug #937068 [src:moosic] moosic: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#942252: lintian: No vendor given at /<>/lib/Lintian/Maintainer.pm line 33

[Sebastian Ramacher]

On 2019-10-13 14:32:01, Felix Lechner wrote:
> Hi Sebastian,
> 
> On Sun, Oct 13, 2019 at 12:15 PM Chris Lamb  wrote:
> >
> > Thanks. Unfortunately, I don't quite know why this is happening. (The
> > tests on Salsa appear to pass right now.)
> 
> Some test scripts appear to load old profiles. They are presumably
> located in the installed location /usr/share/lintian. The errors
> depend on the version difference between what is installed and what is
> under test. That is probably why the reported bug does not show up in
> Gitlab (anymore).
> 
> Could you please cherry-pick this commit?
> https://salsa.debian.org/lintian/lintian/commit/33508343d8fde77a3d5db22863ff358dbf7a915f
> 
> This commit does two things: (1) It unambiguously uses only one
> include path when finding profiles, and (2) makes sure a profile is
> loaded in the test pod-synopsis.t that fails in your bug report.
> 
> I cannot test the proposed fix locally (the error does not appear
> here). Which version Lintian do you have installed?

Please check the build log. I don't have any other info. I was only
reporting the build failure from the buildds.

Cheers

> 
> Kind regards,
> Felix Lechner

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#935745: marked as done (RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon; last upload in 2015)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:01:52 +
with message-id 
and subject line Bug#935745: Removed package(s) from unstable
has caused the Debian Bug report #935745,
regarding RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon; 
last upload in 2015
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.)


-- 
935745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pushy
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello,
i'm looking at python-pushy as it depends on python-paramiko; one of bullseye
goals is to remove python2 and python-pushy

* is dead upstream
* last upload was in 2015, and NMU (one of the only 2 uploads)
* python2-only
* low popcon

If i dont hear anything back in 10 days, I'll file a RM bug for this package.

Regards,
Sandro


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

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

Versions of packages python-pushy depends on:
ii  python   2.7.16-1
ii  python-paramiko  2.6.0-1

python-pushy recommends no packages.

python-pushy suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-pushy |  0.5.1-1.1 | source
python-pushy | 0.5.1-1.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; python2 only; dead upstream; low popcon; last upload in 2015
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 935...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/935745

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#933438: marked as done (spek: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:02:23 +
with message-id 
and subject line Bug#941338: Removed package(s) from unstable
has caused the Debian Bug report #933438,
regarding spek: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 0.8.2-4+rm

Dear submitter,

as the package spek 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/941338

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

Processed: reassign 935745 to ftp.debian.org ...

[Debian Bug Tracking System]

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

> reassign 935745 ftp.debian.org
Bug #935745 [python-pushy] python-pushy: should this package be removed?
Bug reassigned from package 'python-pushy' to 'ftp.debian.org'.
No longer marked as found in versions python-pushy/0.5.1-1.1.
Ignoring request to alter fixed versions of bug #935745 to the same values 
previously set
> retitle 935745 RM: python-pushy -- RoQA; python2 only; dead upstream; low 
> popcon; last upload in 2015
Bug #935745 [ftp.debian.org] python-pushy: should this package be removed?
Changed Bug title to 'RM: python-pushy -- RoQA; python2 only; dead upstream; 
low popcon; last upload in 2015' from 'python-pushy: should this package be 
removed?'.
> thanks
Stopping processing here.

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

Bug#942287: python3-exif: package name should be python3-exifread

[Sandro Tosi]

Package: python3-exif
Version: 2.2.0-3
Severity: serious

Hello,
since this package installs a module called `exifread` the binary package name
should be python3-exifread not python3-exif.

Since it violates the policy, severity is set to serious.

Regards,
Sandro

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

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

Versions of packages python3-exif depends on:
ii  python3  3.7.3-1

python3-exif recommends no packages.

python3-exif suggests no packages.

-- no debconf information

Bug#942284: [Pkg-net-snmp-devel] Bug#942284: libsnmp-perl: perl module SNMP broken

[Craig Small]

On Mon, 14 Oct 2019 at 09:30, gregor herrmann  wrote:

> libsnmp-perl is broken.
>
Ouch, I don't use the module (or Perl much for that matter) but that's very
broken. No idea what's going on but it worries me that
netsnmp_ds_get_boolean is the first function in that module which means a
coincidence or all functions are not available.

 - Craig

Bug#942284: libsnmp-perl: perl module SNMP broken

[gregor herrmann]

Package: libsnmp-perl
Version: 5.8+dfsg-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As noticed by some autopkgtest and build failures, e.g.
https://buildd.debian.org/status/package.php?p=libsnmp-info-perl
libsnmp-perl is broken.

Minimal test case:

% perl -MSNMP -e1
Can't load 
'/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/NetSNMP/default_store/default_store.so'
 for module NetSNMP::default_store: 
/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/NetSNMP/default_store/default_store.so:
 undefined symbol: netsnmp_ds_get_boolean at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
 at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 19.
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm 
line 19.
BEGIN failed--compilation aborted at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 19.
Compilation failed in require.
BEGIN failed--compilation aborted.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jpM5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaq7BAAtaqI2DGml2AO2vgRqnQKlygINGZg9bhbN23LAT1WfSI1VESQjfzeWAPe
ImJN99DUeySKDmEm0jlykz5k/XZZFipxA1pLPNVbRKOPis+lZSZyCODR8s/TdoIS
VYtyxXHBPe+D8JkjHB5tBzHJ9NAfj55vtYLm4WyH5Ztt5RUtXXO6ctvXJkhNrZz8
XMFaA6R7+8nhFOxoGULhmxHFhU3v7EaeE9gsj0HD6e4urQdpjob8c779jDGT6N4y
cstfong8ohEe+Ew/otVsFmPGm3HviwPo2qrCVvdXIYQZr4+uTdZtttoQ17N5AyNn
CLdxxERT6c4TJyqnQyeeUA6tL4MjLwqgAJGGLcNF3iOaftI04qFpzb+uPUGMZ+CB
YI9Lv7ev3eMuRh1vKkN16B+q9kUnNo7J/jS+1rm3QLNMTGbGuilIFgy5BiSURl7s
uKLVC8YJOOlW2J+24FPe42p+WURsMZLr74laUav9IbLHldy9iinC/teAFf7PXzrK
3lo/eD/nELgagLX4YQovjol28yDwnfyTgvvVrWfEmZF9bdcIsdrsF9ZekQI4Hvmu
x4TFr+bjPKa/kaGrTtMiGXDErvkJPALnYY/hDFY19HWHKTXkgVwUt2g2sk2B3oKh
VM1bk+8QnxKHaBmnz2epqXZGORZtVQ1TDl6WQw/ptdq7IRSA/w0=
=G+aH
-END PGP SIGNATURE-

Bug#942252: lintian: No vendor given at /<>/lib/Lintian/Maintainer.pm line 33

[Felix Lechner]

Hi Sebastian,

On Sun, Oct 13, 2019 at 12:15 PM Chris Lamb  wrote:
>
> Thanks. Unfortunately, I don't quite know why this is happening. (The
> tests on Salsa appear to pass right now.)

Some test scripts appear to load old profiles. They are presumably
located in the installed location /usr/share/lintian. The errors
depend on the version difference between what is installed and what is
under test. That is probably why the reported bug does not show up in
Gitlab (anymore).

Could you please cherry-pick this commit?
https://salsa.debian.org/lintian/lintian/commit/33508343d8fde77a3d5db22863ff358dbf7a915f

This commit does two things: (1) It unambiguously uses only one
include path when finding profiles, and (2) makes sure a profile is
loaded in the test pod-synopsis.t that fails in your bug report.

I cannot test the proposed fix locally (the error does not appear
here). Which version Lintian do you have installed?

Kind regards,
Felix Lechner

Bug#931255: Orphaning php-horde*

[Mathieu Parent]

Hello,

FYI, I'm orphaning php-horde-* packages. See:

https://bugs.debian.org/942282

Regards
-- 
Mathieu Parent

Bug#935042: Program phones home by default

[Robie Basak]

On Sun, Oct 13, 2019 at 11:02:45PM +0200, Birger Schacht wrote:
> The problem is that the package will be removed from unstable in a
> couple of days because of this bug report. 3 month is sometimes not that
> much time to fix a bug or even comment on a bug report. And the release
> of bullseye is not even in sight. I or someone else could do an NMU, but
> the package will be removed from the archive before that can happen.

It sounds like you would like to change Debian's process for handling
serious bugs then, rather than having any particular issue with this bug
specifically? That might be a discussion better had on the debian-devel@
list.


signature.asc
Description: PGP signature

Bug#942281: libapache2-mod-ruid2 package missing

[Ali Laraaj]

Package: libapache2-mod-ruid2
Version: 0.9.8-3
Severity: grave

The package libapache2-mod-ruid2 is completely missing from Debian 10

(Buster) repositories, what's the problem why is it missing ?

It's available in previous releases and the the unstable release (SID)

but not Buster

jessie (httpd): 0.9.8-3
Binary packages: libapache2-mod-ruid2
stretch (httpd): 0.9.8-3
Binary packages: libapache2-mod-ruid2
sid (httpd): 0.9.8-3
Binary packages: libapache2-mod-ruid2

Bug#935042: Program phones home by default

[Birger Schacht]

Hi,

On 10/13/19 10:02 PM, Robie Basak wrote:
> On Sun, Oct 13, 2019 at 05:23:40PM +0200, Birger Schacht wrote:
>> Robie, could you please point out the part of the Debian policy that
>> this package is violating?
> 
> I cannot. I believe that this issue is such a clear violation of
> Debian's philosophy that it has never been necessary to document it
> formally as policy.

Thanks for the clarification!

> 
> However you seem to have missed out the latter part of the definition of
> "serious" in your quote. Here's the full definition:
> 
> serious is a severe violation of Debian policy (roughly, it
> violates a "must" or "required" directive), or, in the package
> maintainer's or release manager's opinion, makes the package
> unsuitable for release.

I haven't missed out the part about the "package maintainers or the
release manager's opinion", but I didn't consider it relevant to this
bug report because its neither nor is setting this level of seriousness.

> I think it's quite clear that this issue makes the package unsuitable
> for release. If the package maintainer disagrees and thinks that it's OK
> to release Debian with this bug outstanding, they may change it.
> 
> Are you suggesting that "serious" is not justified? Nobody seems to have
> doubted that so far. If the package maintainer wants to reduce the
> severity of this bug by relying on policy not mentioning this type of
> matter, then I'm fairly confident that this will result in policy being
> amended in the end anyway.

The problem is that the package will be removed from unstable in a
couple of days because of this bug report. 3 month is sometimes not that
much time to fix a bug or even comment on a bug report. And the release
of bullseye is not even in sight. I or someone else could do an NMU, but
the package will be removed from the archive before that can happen.

cheers,
Birger
PS: please don't mistake me asking for clarification as a sign that I
don't consider this being a privacy leak, on the contrary.

Bug#935042: Privacy Breach is not in policy

[Marcos Fouces]

Hello

Similar issues were discussed in: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726998

You could also find that Lintian folks uses several levels of error
tags to describe this problem, for instance:

* 
https://lintian.debian.org/tags/privacy-breach-statistics-website.html.
It is considered as "serious"

* https://lintian.debian.org/tags/privacy-breach-generic.html. It is
considered as "important"

Both tags are related to the present issue.

AFAIK, there is nothing in Debian Policy about this but it is plain
common sense to avoid this kind of privacy breaches.

Greetings, 

Marcos

Bug#938962: Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is avail

[Bastian Blank]

On Sun, Oct 13, 2019 at 07:20:35PM +0530, Ritesh Raj Sarraf wrote:
> It is maintained. It is just that the latest upload is blocked by DBug:
> #938962

No, it is not maintained.  It depends on packages not longer in the
archive.

Regards,
Bastian

-- 
Bones: "The man's DEAD, Jim!"

Bug#935042: Program phones home by default

[Robie Basak]

On Sun, Oct 13, 2019 at 05:23:40PM +0200, Birger Schacht wrote:
> Robie, could you please point out the part of the Debian policy that
> this package is violating?

I cannot. I believe that this issue is such a clear violation of
Debian's philosophy that it has never been necessary to document it
formally as policy.

However you seem to have missed out the latter part of the definition of
"serious" in your quote. Here's the full definition:

serious is a severe violation of Debian policy (roughly, it
violates a "must" or "required" directive), or, in the package
maintainer's or release manager's opinion, makes the package
unsuitable for release.

I think it's quite clear that this issue makes the package unsuitable
for release. If the package maintainer disagrees and thinks that it's OK
to release Debian with this bug outstanding, they may change it.

Are you suggesting that "serious" is not justified? Nobody seems to have
doubted that so far. If the package maintainer wants to reduce the
severity of this bug by relying on policy not mentioning this type of
matter, then I'm fairly confident that this will result in policy being
amended in the end anyway.


signature.asc
Description: PGP signature

Bug#940547: marked as done (python-cryptography: Testsuite fails with OpenSSL 1.1.1d)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:47:34 +
with message-id 
and subject line Bug#940547: fixed in python-cryptography 1.7.1-3+deb9u2
has caused the Debian Bug report #940547,
regarding python-cryptography: Testsuite fails with OpenSSL 1.1.1d
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.)


-- 
940547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cryptography
Version: 2.6.1-3
Severity: serious

The upload of latest openssl 1.1.1d triggert three testsuite failures in
python-cryptography [0]

- _ test_buffer_protocol_alternate_modes[mode5] 
__

|mode = 
|backend = 
|
|@pytest.mark.parametrize(
|"mode",
|[
|modes.CBC(bytearray(b"\x00" * 16)),
|modes.CTR(bytearray(b"\x00" * 16)),
|modes.OFB(bytearray(b"\x00" * 16)),
|modes.CFB(bytearray(b"\x00" * 16)),
|modes.CFB8(bytearray(b"\x00" * 16)),
|modes.XTS(bytearray(b"\x00" * 16)),
|]
|)
|@pytest.mark.requires_backend_interface(interface=CipherBackend)
|def test_buffer_protocol_alternate_modes(mode, backend):
|data = bytearray(b"sixteen_byte_msg")
|cipher = base.Cipher(
|algorithms.AES(bytearray(b"\x00" * 32)), mode, backend
|)
|>   enc = cipher.encryptor()
|
|tests/hazmat/primitives/test_aes.py:495: 
|_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base.py:121:
 in encryptor
|self.algorithm, self.mode
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:295:
 in create_symmetric_encryption_ctx
|return _CipherContext(self, cipher, mode, _CipherContext._ENCRYPT)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py:116:
 in __init__
|self._backend.openssl_assert(res != 0)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:125:
 in openssl_assert
|return binding._openssl_assert(self._lib, ok)

This is due to commit 2a5f63c9a61be ("Allow AES XTS decryption using duplicate
keys.").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2a5f63c9a61be

- _ TestDH.test_dh_parameters_supported 
__

|self = 
|backend = 
|
|def test_dh_parameters_supported(self, backend):
|assert backend.dh_parameters_supported(23, 5)
|>   assert not backend.dh_parameters_supported(23, 18)
|E   assert not True
|E+  where True = >(23, 18)
|E+where > = .dh_parameters_supported
|
|tests/hazmat/primitives/test_dh.py:161: AssertionError

This is due to commit ddd16c2fe988e ("Change DH parameters to generate the
order q subgroup instead of 2q").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddd16c2fe988e

- _ TestECDSACertificate.test_load_ecdsa_no_named_curve 
__

|self = 
|backend = 
|
|def test_load_ecdsa_no_named_curve(self, backend):
|_skip_curve_unsupported(backend, ec.SECP256R1())
|cert = _load_cert(
|os.path.join("x509", "custom", "ec_no_named_curve.pem"),
|x509.load_pem_x509_certificate,
|backend
|)
|with pytest.raises(NotImplementedError):
|>   cert.public_key()
|E   Failed: DID NOT RAISE 
|
|tests/x509/test_x509.py:3722: Failed

This is due to commit 9a43a733801bd ("[ec] Match built-in curves on
EC_GROUP_new_from_ecparameters").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a43a733801bd


The first two changes in OpenSSL have been made on purporse and I'm not
sure about the last one.
Could someone please comment?

[0] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cryptography/2969575/log.gz

Sebastian
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 1.7.1-3+deb9u2

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
python-cryptography package)

(This message was 

Bug#934519: marked as done (fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:47:32 +
with message-id 
and subject line Bug#934519: fixed in fence-agents 4.0.25-1+deb9u2
has caused the Debian Bug report #934519,
regarding fence-agents: FTBFS in stretch/buster/sid (ImportError: No module 
named pywsman)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with python2 --with autoreconf
   dh_testdir -a
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I make -I m4
configure.ac:70: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from...

[... snipped ...]

xsltproc ../../fence/agents/lib/fence2wiki.xsl apc_snmp/.fence_apc_snmp.8.tmp | 
grep -v ' apc_snmp/fence_apc_snmp.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ifmib/fence_ifmib -o metadata > 
ifmib/.fence_ifmib.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ifmib/.fence_ifmib.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ifmib/.fence_ifmib.8.tmp > 
ifmib/fence_ifmib.8
ifmib/.fence_ifmib.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ifmib/.fence_ifmib.8.tmp | grep 
-v ' ifmib/fence_ifmib.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ibmblade/fence_ibmblade -o metadata > 
ibmblade/.fence_ibmblade.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ibmblade/.fence_ibmblade.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ibmblade/.fence_ibmblade.8.tmp > 
ibmblade/fence_ibmblade.8
ibmblade/.fence_ibmblade.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ibmblade/.fence_ibmblade.8.tmp | 
grep -v ' ibmblade/fence_ibmblade.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python bladecenter/fence_bladecenter -o metadata > 
bladecenter/.fence_bladecenter.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
bladecenter/.fence_bladecenter.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl 
bladecenter/.fence_bladecenter.8.tmp > bladecenter/fence_bladecenter.8
bladecenter/.fence_bladecenter.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl 
bladecenter/.fence_bladecenter.8.tmp | grep -v ' 
bladecenter/fence_bladecenter.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python rhevm/fence_rhevm -o metadata > 
rhevm/.fence_rhevm.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
rhevm/.fence_rhevm.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl rhevm/.fence_rhevm.8.tmp > 
rhevm/fence_rhevm.8
rhevm/.fence_rhevm.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl rhevm/.fence_rhevm.8.tmp | grep 
-v ' rhevm/fence_rhevm.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ilo/fence_ilo -o metadata > ilo/.fence_ilo.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ilo/.fence_ilo.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ilo/.fence_ilo.8.tmp > 
ilo/fence_ilo.8
ilo/.fence_ilo.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ilo/.fence_ilo.8.tmp | grep -v 
' ilo/fence_ilo.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python alom/fence_alom -o metadata > alom/.fence_alom.8.tmp && 
\
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
alom/.fence_alom.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl alom/.fence_alom.8.tmp > 
alom/fence_alom.8
alom/.fence_alom.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl alom/.fence_alom.8.tmp | grep

Processed: golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 golang-github-hashicorp-go-retryablehttp/0.6.2-1
Bug #942279 [src:golang-github-hashicorp-go-retryablehttp, 
src:golang-github-circonus-labs-circonus-gometrics] 
golang-github-hashicorp-go-retryablehttp breaks 
golang-github-circonus-labs-circonus-gometrics autopkgtest
Marked as found in versions golang-github-hashicorp-go-retryablehttp/0.6.2-1.
> found -1 golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Bug #942279 [src:golang-github-hashicorp-go-retryablehttp, 
src:golang-github-circonus-labs-circonus-gometrics] 
golang-github-hashicorp-go-retryablehttp breaks 
golang-github-circonus-labs-circonus-gometrics autopkgtest
Marked as found in versions 
golang-github-circonus-labs-circonus-gometrics/2.0.0-1.

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

Bug#942279: golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest

[Paul Gevers]

Source: golang-github-hashicorp-go-retryablehttp, 
golang-github-circonus-labs-circonus-gometrics
Control: found -1 golang-github-hashicorp-go-retryablehttp/0.6.2-1
Control: found -1 golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of golang-github-hashicorp-go-retryablehttp the
autopkgtest of golang-github-circonus-labs-circonus-gometrics fails in
testing when that autopkgtest is run with the binary packages of
golang-github-hashicorp-go-retryablehttp from unstable. It passes when
run with only packages from testing. In tabular form:
pass fail
golang-github-hashicorp-go-retryablehttpfrom testing 0.6.2-1
golang-github-circonus-labs-circonus-gometrics  from testing 2.0.0-1
all others  from testing from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of
golang-github-hashicorp-go-retryablehttp to testing [1]. Due to the
nature of this issue, I filed this bug report against both packages. Can
you please investigate the situation and reassign the bug to the right
package?

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

Paul

[1]
https://qa.debian.org/excuses.php?package=golang-github-hashicorp-go-retryablehttp

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-circonus-labs-circonus-gometrics/3160364/log.gz

# github.com/circonus-labs/circonus-gometrics
src/github.com/circonus-labs/circonus-gometrics/submit.go:133:24: cannot
use func literal (type func(*log.Logger, *http.Request, int)) as type
retryablehttp.RequestLogHook in assignment
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.ikh1z671/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.ikh1z671/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-v -p 2 github.com/circonus-labs/circonus-gometrics
github.com/circonus-labs/circonus-gometrics/api
github.com/circonus-labs/circonus-gometrics/api/config
github.com/circonus-labs/circonus-gometrics/checkmgr returned exit code 2
make: *** [debian/rules:4: build] Error 255



signature.asc
Description: OpenPGP digital signature

Bug#941487: marked as done (gconf: autopkgtest fails with libglib2.0-0 (>= 2.62))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:34:47 +
with message-id 
and subject line Bug#941487: fixed in gconf 3.2.6-6
has caused the Debian Bug report #941487,
regarding gconf: autopkgtest fails with libglib2.0-0 (>= 2.62)
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.)


-- 
941487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf
Version: 3.2.6-5
Severity: serious
Justification: https://release.debian.org/bullseye/rc_policy.txt §6a
Tags: patch
Forwarded: https://gitlab.gnome.org/Archive/gconf/merge_requests/1

With the recent upload of GLib 2.62 to unstable, gconf's autopkgtest has
started failing:

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gconf/3045304/log.gz
> /usr/include/gconf/2/gconf/gconf-value.h:139:3: error: ‘GTime’ is deprecated: 
> Use 'GDateTime' instead [-Werror=deprecated-declarations]
>   139 |   GTime  mod_time; /* time of the modification */
>   |   ^
> /usr/include/gconf/2/gconf/gconf-value.h:144:1: error: ‘GTime’ is deprecated: 
> Use 'GDateTime' instead [-Werror=deprecated-declarations]
>   144 | GTime   gconf_meta_info_mod_time (GConfMetaInfo *gcmi);
>   | ^
> /usr/include/gconf/2/gconf/gconf-value.h:153:46: error: ‘GTime’ is 
> deprecated: Use 'GDateTime' instead [-Werror=deprecated-declarations]
>   153 |  GTime  mod_time);
>   |  ^
> cc1: all warnings being treated as errors

GTime is a gint32 (not a time_t, although it happens to be equivalent on
older 32-bit architectures) counting seconds since the beginning of 1970.
As such it is not Y2038-safe.

The deprecation warnings can be disabled for code that depends on
gconf by wrapping a block with the G_GNUC_BEGIN_IGNORE_DEPRECATIONS
and G_GNUC_END_IGNORE_DEPRECATIONS macros, as was done in Ubuntu patch
3.2.6-5ubuntu3: https://gitlab.gnome.org/Archive/gconf/merge_requests/1

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: gconf
Source-Version: 3.2.6-6

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gconf 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, 13 Oct 2019 21:41:05 +0300
Source: gconf
Architecture: source
Version: 3.2.6-6
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Closes: 935801 936589 941487
Changes:
 gconf (3.2.6-6) unstable; urgency=medium
 .
   * Add patch from Iain Lane for GLib 2.62 deprecations
 in gconf-value.h. (Closes: #935801, #941487)
   * Add Python 3 changes from Ubuntu. (Closes: #936589)
   * Add patch from Chow Loong Jin to initialize dbus threads before
 doing anything. This fixes crashes in multithreaded applications
 that don't use libdbus directly. (LP: #1048341)
Checksums-Sha1:
 66d3cb20ffd9acf1c55c2a2a50d1f9586c4928f2 2641 gconf_3.2.6-6.dsc
 1531a460d43f6396ef9a15833c98d456d257f207 30276 gconf_3.2.6-6.debian.tar.xz
Checksums-Sha256:
 692527c66299e07d408321cb01c847cfc09ebc736f90bcd30c0b92e16be416b0 2641 
gconf_3.2.6-6.dsc
 45e0b6452f7c84b96af978f3f89be49a894e7557ba69dc3f8987d78212527354 30276 
gconf_3.2.6-6.debian.tar.xz
Files:
 22caa60dbcf00eec83188d9e971ddb74 2641 libs optional gconf_3.2.6-6.dsc
 4dac0dc8c4b5daae327edc84075c2406 30276 libs optional 
gconf_3.2.6-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl2jdxoACgkQiNJCh6LY
mLGD8hAAsLqcMmS0YjsJEurLOvRaGxAnjjvxUiXGRRZKJubioGXg3sY2K/RLTCKD
2ahEcxZf7IxYsfAnpsLjRbEuTeUSpuX8Zk7SQlgM6YzwuCr4pbkVBKyUh/3Y+4zt
xlEZKTEwKzkKfMJkzMBcsuuMI4WKBFvgeAcTHtHUELvXFRi1akIKSqwRcpg6SLGx
+m9PpVxcGq+7gARhv8t29zdBlYoUL6e95zH5eCckLVElCWxLGQwo7v9h3afQqKO/
Zg8iO4GuLXt+Xw3hRJfgvxYD70AeDOfMD6g5ptPvh+JIXIyHHSOq8X7wXT2sttms
SlSe72g2vLhleYVtPxlnHxYnRC68cIUejvOxjj2KRH1lsF7QttX7Ejahn9b7O90c
Qki6RLxehm/hzQhzXCL0u0S+6Y1NFbZ52ajK8xsCvPjOjIEUnZbm7zAiLxN6fHnj
OPKGzypyfaSijcBNP2H9J9

Bug#942193: dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed.

[Kurt Kremitzki]

Hi Matthias,

On Saturday, October 12, 2019 12:34:30 PM CDT Matthias Klose wrote:
> Control: tags -1 + moreinfo
> Control: severity -1 grave
> 
> please could you attach the binary, or put it somewhere on the web?
> 

Sorry, which binary are you referring to?

Here are a few links in the meantime that might help, buildd logs for the 
i386/s390x/mipsel failures:

https://buildd.debian.org/status/fetch.php?
pkg=freecad&arch=i386&ver=0.18.3%2Bdfsg1-3&stamp=1568751036&raw=0

https://buildd.debian.org/status/fetch.php?
pkg=freecad&arch=mipsel&ver=0.18.3%2Bdfsg1-3&stamp=1568784049&raw=0

https://buildd.debian.org/status/fetch.php?
pkg=freecad&arch=s390x&ver=0.18.3%2Bdfsg1-3&stamp=1569764936&raw=0

Bug#885265: Bug#936299: chirp: Python2 removal in sid/bullseye

[Chris Knadle]

There has been some discussion about #936299 on the upstream mailing list, and
there have been a few upstream commits starting to port the code to Python3.

http://intrepid.danplanet.com/pipermail/chirp_devel/2019-August/005580.html

  -- Chris, KB2IQN

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#933163: marked as done (cyrus-imapd: Data loss possible when upgrading to buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:08 +
with message-id 
and subject line Bug#933163: fixed in cyrus-imapd 3.0.8-6+deb10u1
has caused the Debian Bug report #933163,
regarding cyrus-imapd: Data loss possible when upgrading to 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.)


-- 
933163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-imapd
Version: 3.0.8-6
Severity: grave
Tags: upstream

Dear Maintainer,

After upgrading a cyrus-imapd system from 2.4.17 (jessie-era) to 3.0.8 (buster),
I discovered many missing messages.  It appears that index records with MODSEQ 
set
to zero (e.g., records for messages which predated the addition of the MODSEQ 
field)
are being ignored.  The data is still there, but not served to IMAP clients.
Unfortunately, if the 3.0.8 cyrus "reconstruct" is executed to naively try to 
fix
the missing messages, those index records (and the metadata they contain, e.g.,
seen flags) are lost for good!  I tagged this report as "grave" because of the
potential for irreversible data loss.

There may be a one-line fix for this; I have filed an upstream bug report with 
more
details:

https://github.com/cyrusimap/cyrus-imapd/issues/2839

Fortunately, I have backups of the original cyrus.index files and didn't 
permanently
lose any state, but I don't know of any way to safely upgrade to v3.x.x until 
this
issue is fixed.

-m

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

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

Versions of packages cyrus-imapd depends on:
ii  cyrus-common  3.0.8-6
ii  dpkg  1.19.7
ii  libc6 2.28-10
ii  libcom-err2   1.44.5-1
ii  libsasl2-22.1.27+dfsg-1
ii  libssl1.1 1.1.1c-1
ii  libwrap0  7.6.q-28
ii  zlib1g1:1.2.11.dfsg-1

cyrus-imapd recommends no packages.

cyrus-imapd suggests no packages.

-- Configuration Files:
/etc/pam.d/imap changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 3.0.8-6+deb10u1

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated cyrus-imapd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Oct 2019 22:38:07 +0200
Source: cyrus-imapd
Architecture: source
Version: 3.0.8-6+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Cyrus Team 
Changed-By: Xavier Guimard 
Closes: 933163
Changes:
 cyrus-imapd (3.0.8-6+deb10u1) buster; urgency=medium
 .
   * Add patch to fix data loss on upgrade from versions ≤ 3.0.0
 (Closes: #933163)
Checksums-Sha1: 
 eee2d59d23825ee71f1477a15222e2d6bcab8c82 3157 cyrus-imapd_3.0.8-6+deb10u1.dsc
 8840295493f852b67b5a43b55c6ddbae5c9e4394 92656 
cyrus-imapd_3.0.8-6+deb10u1.debian.tar.xz
Checksums-Sha256: 
 721162a79c90c30c83cf47b2b9b3108e90d26b7cc615c37bcc5fcf36da8679f3 3157 
cyrus-imapd_3.0.8-6+deb10u1.dsc
 22b2d09a61d6b3094cd88d69154c01054ca93989f5fda3f21240207fa8fc0d12 92656 
cyrus-imapd_3.0.8-6+deb10u1.debian.tar.xz
Files: 
 ac66f5f95ec2c76cf0dd131ee39215d7 3157 mail optional 
cyrus-imapd_3.0.8-6+deb10u1.dsc
 b789355c52e3c74e2212f827b44d696e 92656 mail optional 
cyrus-imapd_3.0.8-6+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl2hed8ACgkQ9tdMp8mZ
7umKmQ/2PuCXjT84Dk67hkPqxzQRh9hC8KJ/DC64Pp3l91A54baRMOV8eE/AaNvv
XRloTd/eEaQtGqG9a82huuGioBU1Qi+7ZoEFTfv9QCuXHCicBQiABjJHQzHyGB4J
hbRosB/BNdOcIi+78B8ZqHBm0TYdEpCQka1xBmN04gvF5uqDasCTxOU8OVa9iE6H
KdBdiS/QJ9GJjo1zDScH9WOS8Nhhy3XblahXrjoD6ii25kOYt2d+UwuWJd8+ET9v
MvspBray1z1IUWQDxHZR84bY92hmj8n6ZM2+U3zPCZzOrsmXZgUbhXgJjgQJLnJI
MbQhPx0I0b8BviDviYMhbWO115gF0vKFVZIxcOS

Bug#941955: marked as done (memory leaks in open-vm-tools)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:11 +
with message-id 
and subject line Bug#941955: fixed in open-vm-tools 2:10.3.10-1+deb10u2
has caused the Debian Bug report #941955,
regarding memory leaks in open-vm-tools
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.)


-- 
941955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-vm-tools
Version: 10.3.10-1

We have discovered a few memory leaks in open-vm-tools, related to the vix 
plugin. We have created a branch for 10.3.10 on github that includes fixes: 
https://github.com/vmware/open-vm-tools/tree/stable-10.3.10-vix-memory-leaks

Thanks,
Oliver



--- End Message ---
--- Begin Message ---
Source: open-vm-tools
Source-Version: 2:10.3.10-1+deb10u2

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated open-vm-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 09 Oct 2019 14:18:48 +0200
Source: open-vm-tools
Architecture: source
Version: 2:10.3.10-1+deb10u2
Distribution: buster
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Closes: 941955
Changes:
 open-vm-tools (2:10.3.10-1+deb10u2) buster; urgency=medium
 .
   * [d512626] Fix memory leaks and error handling.
 From the upstream stable-10.3.10-vix-memory-leaks branch:
 commit 26b9edbeb79d1c67b9ae73a0c97c48999c1fb503
 Fix leaks in ListAliases and ListMappedAliases
 commit 7b874f37f970aab2adddb063a8363594f47abf70
 End VGAuth impersonation in the case of error.
 commit 015db4c06a8be65eb96cf62421e8b5366993452f
 Fix memory leaks in 'vix' tools plugin.
 Thanks to Oliver Kurth (Closes: #941955)
Checksums-Sha1:
 127afba950e69bab13f666c629a0e3113830e230 2358 
open-vm-tools_10.3.10-1+deb10u2.dsc
 3582f48a5e94a7256863ff68e418ef6c070f868a 30036 
open-vm-tools_10.3.10-1+deb10u2.debian.tar.xz
 64f3f695c8618e35ff64d1f72501865fb29eb781 16418 
open-vm-tools_10.3.10-1+deb10u2_source.buildinfo
Checksums-Sha256:
 b0de338a12bd51cc883447df9f21ac81abe84b13e74f453a606c5102b27b0cac 2358 
open-vm-tools_10.3.10-1+deb10u2.dsc
 088e3a8505e56f051dfb61c28754bbb3a7f335e6fc647195900f3e30f8948d82 30036 
open-vm-tools_10.3.10-1+deb10u2.debian.tar.xz
 91bedc37768d1cf1748a23070ec3f9068402452257d69ef63f43d623adde2592 16418 
open-vm-tools_10.3.10-1+deb10u2_source.buildinfo
Files:
 9121cdb8d5cba0eaa78e791dc372555f 2358 admin extra 
open-vm-tools_10.3.10-1+deb10u2.dsc
 8116615cd2a06d75730846c7a73fa915 30036 admin extra 
open-vm-tools_10.3.10-1+deb10u2.debian.tar.xz
 ab0173c62641400457bb9925ebe77d8f 16418 admin extra 
open-vm-tools_10.3.10-1+deb10u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl2iLgwACgkQ6zYXGm/5
Q1/lWg/+MDLyDxMSqSjZKnKIKwW9OWYhdFTyNojoKA1upB45YfBOSLypECB+Y4OB
zcCbtUI6Q/TY8kUPjvIW3tCy4quRG5Tbvpp5KvG/THHVp1ezM94hDZBjH2v1RxF3
MHN0BFrMZOF5/jj3b4YcKdgD59RFoBGkiry0tPPseUr9hWFStC2aUrftiB8l3WQu
ItDsAC9TEE6Wabyy4ytyx5PjRC9Oc23PZgncnzUReUK81hDsLIRFCCZXiErEO6o8
i52Pk93MLjB9lm1bm3eRlovbhXux0megQDE2oPt/K7m8goAjkRZJj6kjAWFm7W1V
Ihxqo6VGSaNxNo/BQpZEWFkTAIlQxm7eKwc7AmaNS8pnQRV8jr/L2rxkYqA0JkuR
qxg8zqMANF5wbH2xoMXdmBjSWKEgCBwWZxzDOW7s34trzzQQ0SCFkEexaeq+0CN+
+LyeLSGK8zxDnzVRu6DrO1t+8qpx2AjOSKH9dOzjdUSmjesA7E1QNTjgBcQx5UGG
lkwDS8BF6NhiYTR0uk85gScZ2MrK+sllmGNJexWF2hFxlf7eGx4vASfL2yachZq9
QGF9kmikYQ8YKUD50+vwYy/Q1GKgzMJVCEE8v1NgAo0ABtcMdzIlmXaNTYPKk+og
NzK/2xrccgDzO0Gre2zF69TGtZ3GLFpp/9wcrUhNJkFtoXpuCc8=
=FFSf
-END PGP SIGNATURE End Message ---

Bug#939877: marked as done (rpcbind: Does not receive any broadcast queries resulting in complete breakage of NIS)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:23 +
with message-id 
and subject line Bug#939877: fixed in rpcbind 1.2.5-0.3+deb10u1
has caused the Debian Bug report #939877,
regarding rpcbind: Does not receive any broadcast queries resulting in complete 
breakage of NIS
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.)


-- 
939877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpcbind
Version: 1.2.5-0.3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After an upgrade to buster rpcbind no longer receives any broadcast queries. 
Unicast works.

This is verified via strace - it has occasional netlink messages, but any of 
the broadcast
traffic to port 111 never hit it.

As a result clients can no longer find a nis server which has been upgraded to 
buster. 

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

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

Versions of packages rpcbind depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libsystemd0  241-7~deb10u1
ii  libtirpc31.1.4-0.4
ii  libwrap0 7.6.q-28
ii  lsb-base 10.2019051400

rpcbind recommends no packages.

rpcbind suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 1.2.5-0.3+deb10u1

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated rpcbind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Sep 2019 12:19:21 -0600
Source: rpcbind
Architecture: source
Version: 1.2.5-0.3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 939877
Changes:
 rpcbind (1.2.5-0.3+deb10u1) buster; urgency=medium
 .
   * Add 00-rmt-calls.patch (Closes: #939877):
 + Add command line option to enable remote calls at runtime
 + Refresh debian/patches
   * debian/control: Update maintainer information
   * Add debian/README.debian explaining remote calls activation for
 Debian systems
   * Add debian/NEWS
Checksums-Sha1:
 e854744d050d76f3f8fbdd74eb92a251d8265995 1851 rpcbind_1.2.5-0.3+deb10u1.dsc
 99e7676ac0df6befdf4408f6bac2b029e355c970 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 dedc3c21829083670a1f47b6381b23b82c41f8b7 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Checksums-Sha256:
 c881586a2b2e56c4985fe1f9a33f17271e43360e2ef8dc5def3f6e725432cf82 1851 
rpcbind_1.2.5-0.3+deb10u1.dsc
 daa8e74c875a6caa3824fe90e7bcfa8472f1aae65dfe073789a681e15eb82487 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 41e382be8e6bbf4215f5081b4af13bb68bd96c62bd4de4faf5af0bfdc83832cc 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Files:
 254f5874fbcb8304ac7de7302e97c303 1851 net optional 
rpcbind_1.2.5-0.3+deb10u1.dsc
 bf1e40e72af2954b09596f3979480d6f 11240 net optional 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 5578d189d15034b7198127677dddebda 6062 net optional 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl2h6OURHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+BDQ/8C/AN6tfzuIqOuuy1986R1qRtBn0lg3j+
jzreJ31qIZLyCBuNrEhAXJAB4hZBzbg4N7YlgOobQP6RxTjVMOHbrokMdwXjxH+t
rWfigfu5hYJMtak7QMLgFHH6xJjxTKMDrvFlEkMtYg5jvuaQTNyKm4IOkkeIzbRc
0cJoTFZP++C2A1s5rFJ86XGf0FjZe8ijGeVMKU12xqPBr/j6bBDgJ1inYsCbozNZ
Vwa5xoyh/Jb5SEJfnIsJY02srfF9646J5uiO9em44j4eyI9dXYY4nay9Mt0XxFtG
dh/cgIxu045TVRgZSfgkg9f1U/QfHGZaoOSk4YgrMFqW/vQDE6H81OusxuHFA85r
L1hDK87dczOQNyPcU6i0b9dnGoF8lhYhJePwe9xFzHafqzd8oHyDx1xMSjhwspuq
uEBmGujQhimzq6zGfe8AgeGMaCdAxXn9mwd/flMI0UuA7SdyhMn8RLaECS8qM8dz
kaaJ

Bug#934519: marked as done (fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:09 +
with message-id 
and subject line Bug#934519: fixed in fence-agents 4.3.3-2+deb10u1
has caused the Debian Bug report #934519,
regarding fence-agents: FTBFS in stretch/buster/sid (ImportError: No module 
named pywsman)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with python2 --with autoreconf
   dh_testdir -a
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I make -I m4
configure.ac:70: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from...

[... snipped ...]

xsltproc ../../fence/agents/lib/fence2wiki.xsl apc_snmp/.fence_apc_snmp.8.tmp | 
grep -v ' apc_snmp/fence_apc_snmp.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ifmib/fence_ifmib -o metadata > 
ifmib/.fence_ifmib.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ifmib/.fence_ifmib.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ifmib/.fence_ifmib.8.tmp > 
ifmib/fence_ifmib.8
ifmib/.fence_ifmib.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ifmib/.fence_ifmib.8.tmp | grep 
-v ' ifmib/fence_ifmib.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ibmblade/fence_ibmblade -o metadata > 
ibmblade/.fence_ibmblade.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ibmblade/.fence_ibmblade.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ibmblade/.fence_ibmblade.8.tmp > 
ibmblade/fence_ibmblade.8
ibmblade/.fence_ibmblade.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ibmblade/.fence_ibmblade.8.tmp | 
grep -v ' ibmblade/fence_ibmblade.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python bladecenter/fence_bladecenter -o metadata > 
bladecenter/.fence_bladecenter.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
bladecenter/.fence_bladecenter.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl 
bladecenter/.fence_bladecenter.8.tmp > bladecenter/fence_bladecenter.8
bladecenter/.fence_bladecenter.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl 
bladecenter/.fence_bladecenter.8.tmp | grep -v ' 
bladecenter/fence_bladecenter.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python rhevm/fence_rhevm -o metadata > 
rhevm/.fence_rhevm.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
rhevm/.fence_rhevm.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl rhevm/.fence_rhevm.8.tmp > 
rhevm/fence_rhevm.8
rhevm/.fence_rhevm.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl rhevm/.fence_rhevm.8.tmp | grep 
-v ' rhevm/fence_rhevm.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ilo/fence_ilo -o metadata > ilo/.fence_ilo.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ilo/.fence_ilo.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ilo/.fence_ilo.8.tmp > 
ilo/fence_ilo.8
ilo/.fence_ilo.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ilo/.fence_ilo.8.tmp | grep -v 
' ilo/fence_ilo.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python alom/fence_alom -o metadata > alom/.fence_alom.8.tmp && 
\
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
alom/.fence_alom.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl alom/.fence_alom.8.tmp > 
alom/fence_alom.8
alom/.fence_alom.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl alom/.fence_alom.8.tmp | grep

Bug#940547: marked as done (python-cryptography: Testsuite fails with OpenSSL 1.1.1d)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:22 +
with message-id 
and subject line Bug#940547: fixed in python-cryptography 2.6.1-3+deb10u1
has caused the Debian Bug report #940547,
regarding python-cryptography: Testsuite fails with OpenSSL 1.1.1d
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.)


-- 
940547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cryptography
Version: 2.6.1-3
Severity: serious

The upload of latest openssl 1.1.1d triggert three testsuite failures in
python-cryptography [0]

- _ test_buffer_protocol_alternate_modes[mode5] 
__

|mode = 
|backend = 
|
|@pytest.mark.parametrize(
|"mode",
|[
|modes.CBC(bytearray(b"\x00" * 16)),
|modes.CTR(bytearray(b"\x00" * 16)),
|modes.OFB(bytearray(b"\x00" * 16)),
|modes.CFB(bytearray(b"\x00" * 16)),
|modes.CFB8(bytearray(b"\x00" * 16)),
|modes.XTS(bytearray(b"\x00" * 16)),
|]
|)
|@pytest.mark.requires_backend_interface(interface=CipherBackend)
|def test_buffer_protocol_alternate_modes(mode, backend):
|data = bytearray(b"sixteen_byte_msg")
|cipher = base.Cipher(
|algorithms.AES(bytearray(b"\x00" * 32)), mode, backend
|)
|>   enc = cipher.encryptor()
|
|tests/hazmat/primitives/test_aes.py:495: 
|_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base.py:121:
 in encryptor
|self.algorithm, self.mode
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:295:
 in create_symmetric_encryption_ctx
|return _CipherContext(self, cipher, mode, _CipherContext._ENCRYPT)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py:116:
 in __init__
|self._backend.openssl_assert(res != 0)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:125:
 in openssl_assert
|return binding._openssl_assert(self._lib, ok)

This is due to commit 2a5f63c9a61be ("Allow AES XTS decryption using duplicate
keys.").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2a5f63c9a61be

- _ TestDH.test_dh_parameters_supported 
__

|self = 
|backend = 
|
|def test_dh_parameters_supported(self, backend):
|assert backend.dh_parameters_supported(23, 5)
|>   assert not backend.dh_parameters_supported(23, 18)
|E   assert not True
|E+  where True = >(23, 18)
|E+where > = .dh_parameters_supported
|
|tests/hazmat/primitives/test_dh.py:161: AssertionError

This is due to commit ddd16c2fe988e ("Change DH parameters to generate the
order q subgroup instead of 2q").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddd16c2fe988e

- _ TestECDSACertificate.test_load_ecdsa_no_named_curve 
__

|self = 
|backend = 
|
|def test_load_ecdsa_no_named_curve(self, backend):
|_skip_curve_unsupported(backend, ec.SECP256R1())
|cert = _load_cert(
|os.path.join("x509", "custom", "ec_no_named_curve.pem"),
|x509.load_pem_x509_certificate,
|backend
|)
|with pytest.raises(NotImplementedError):
|>   cert.public_key()
|E   Failed: DID NOT RAISE 
|
|tests/x509/test_x509.py:3722: Failed

This is due to commit 9a43a733801bd ("[ec] Match built-in curves on
EC_GROUP_new_from_ecparameters").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a43a733801bd


The first two changes in OpenSSL have been made on purporse and I'm not
sure about the last one.
Could someone please comment?

[0] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cryptography/2969575/log.gz

Sebastian
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 2.6.1-3+deb10u1

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
python-cryptography package)

(This message wa

Bug#935492: marked as done (rpcbind: Broadcast requests broken)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:23 +
with message-id 
and subject line Bug#939877: fixed in rpcbind 1.2.5-0.3+deb10u1
has caused the Debian Bug report #939877,
regarding rpcbind: Broadcast requests 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.)


-- 
939877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpcbind
Version: 1.2.5-0.3
Severity: important

I upgraded my NIS server to buster and found that it stopped
answering requests to NIS clients.  It turns out that rpcbind
no longer responds to broadcast requests coming in on port 111.

This is due to an upstream change:

https://sourceforge.net/p/libtirpc/mailman/message/36377522/

Fortunately it is easy to fix it by enabling it at build time
with --enable-rmtcalls.

Could you please do that and also inform upstream that people
do use this feature?

Thanks,
--
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 1.2.5-0.3+deb10u1

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated rpcbind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Sep 2019 12:19:21 -0600
Source: rpcbind
Architecture: source
Version: 1.2.5-0.3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 939877
Changes:
 rpcbind (1.2.5-0.3+deb10u1) buster; urgency=medium
 .
   * Add 00-rmt-calls.patch (Closes: #939877):
 + Add command line option to enable remote calls at runtime
 + Refresh debian/patches
   * debian/control: Update maintainer information
   * Add debian/README.debian explaining remote calls activation for
 Debian systems
   * Add debian/NEWS
Checksums-Sha1:
 e854744d050d76f3f8fbdd74eb92a251d8265995 1851 rpcbind_1.2.5-0.3+deb10u1.dsc
 99e7676ac0df6befdf4408f6bac2b029e355c970 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 dedc3c21829083670a1f47b6381b23b82c41f8b7 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Checksums-Sha256:
 c881586a2b2e56c4985fe1f9a33f17271e43360e2ef8dc5def3f6e725432cf82 1851 
rpcbind_1.2.5-0.3+deb10u1.dsc
 daa8e74c875a6caa3824fe90e7bcfa8472f1aae65dfe073789a681e15eb82487 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 41e382be8e6bbf4215f5081b4af13bb68bd96c62bd4de4faf5af0bfdc83832cc 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Files:
 254f5874fbcb8304ac7de7302e97c303 1851 net optional 
rpcbind_1.2.5-0.3+deb10u1.dsc
 bf1e40e72af2954b09596f3979480d6f 11240 net optional 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 5578d189d15034b7198127677dddebda 6062 net optional 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl2h6OURHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+BDQ/8C/AN6tfzuIqOuuy1986R1qRtBn0lg3j+
jzreJ31qIZLyCBuNrEhAXJAB4hZBzbg4N7YlgOobQP6RxTjVMOHbrokMdwXjxH+t
rWfigfu5hYJMtak7QMLgFHH6xJjxTKMDrvFlEkMtYg5jvuaQTNyKm4IOkkeIzbRc
0cJoTFZP++C2A1s5rFJ86XGf0FjZe8ijGeVMKU12xqPBr/j6bBDgJ1inYsCbozNZ
Vwa5xoyh/Jb5SEJfnIsJY02srfF9646J5uiO9em44j4eyI9dXYY4nay9Mt0XxFtG
dh/cgIxu045TVRgZSfgkg9f1U/QfHGZaoOSk4YgrMFqW/vQDE6H81OusxuHFA85r
L1hDK87dczOQNyPcU6i0b9dnGoF8lhYhJePwe9xFzHafqzd8oHyDx1xMSjhwspuq
uEBmGujQhimzq6zGfe8AgeGMaCdAxXn9mwd/flMI0UuA7SdyhMn8RLaECS8qM8dz
kaaJ1zxyZFO2eas19jSBakRy6vOmvhC0yYnpInIpsX4Nl4AyxQb42tRpAwKZ7YkW
rPcepBjQEiZjnASzT3dQeSjvQHlR3sZoSIFQ7xV3oYUY+zQCY4TfFucJLRL2FS47
R/dyq+OW/GzWbw7RyHo/MiuW9lBsfoJDT7ymJat3lYEDrygU3t6rFTgzKWuUw+rj
iNuDZlzwVbk=
=xlGy
-END PGP SIGNATURE End Message ---

Bug#942252: lintian: No vendor given at /<>/lib/Lintian/Maintainer.pm line 33

[Chris Lamb]

retitle 942252 lintian: No vendor given at 
/<>/lib/Lintian/Maintainer.pm line 33
thanks

Sebastian Ramacher wrote:

> https://buildd.debian.org/status/fetch.php?pkg=lintian&arch=all&ver=2.26.0&stamp=1570670200&raw=0

Thanks. Unfortunately, I don't quite know why this is happening. (The
tests on Salsa appear to pass right now.)

t/scripts/pod-coverage.t ... ok
#   Failed test '/<>/lib/Lintian/Maintainer.pm'
#   at t/scripts/pod-synopsis.t line 18.
# No vendor given at /<>/lib/Lintian/Maintainer.pm line 33.
# Compilation failed in require at 
/<>/lib/Lintian/Maintainer.pm line 43.
# BEGIN failed--compilation aborted at 
/<>/lib/Lintian/Maintainer.pm line 43.
t/scripts/pod.t  ok
# Looks like you failed 1 test of 66.


Best wishes,

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

Processed: Re: Bug#942252: lintian: No vendor given at /<>/lib/Lintian/Maintainer.pm line 33

[Debian Bug Tracking System]

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

> retitle 942252 lintian: No vendor given at 
> /<>/lib/Lintian/Maintainer.pm line 33
Bug #942252 [src:lintian] lintian: t/scripts/pod-synopsis.t: (Wstat: 256 Tests: 
66 Failed: 1)
Changed Bug title to 'lintian: No vendor given at 
/<>/lib/Lintian/Maintainer.pm line 33' from 'lintian: 
t/scripts/pod-synopsis.t: (Wstat: 256 Tests: 66 Failed: 1)'.
> thanks
Stopping processing here.

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

Bug#940069: marked as done (gr-limesdr: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:22 +
with message-id 
and subject line Bug#940069: fixed in gr-limesdr 2.0.0-27-gca01a64-2
has caused the Debian Bug report #940069,
regarding gr-limesdr: FTBFS in unstable
to be marked as done.

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

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


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

Package: gr-limesdr
Version: 0.9~beta-1+b2
Severity: serious
Tags: bullseye, sid

gr-limesdr failed to build with the following errors when an attempt was made 
to binnmu it for the new gnuradio.


-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
CMake Error at 
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
   Could NOT find MPLIB (missing: MPLIBXX_LIBRARY MPLIB_LIBRARY
   MPLIB_INCLUDE_DIR)
Call Stack (most recent call first):
   /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
   /usr/lib/x86_64-linux-gnu/cmake/gnuradio/FindMPLIB.cmake:26 
(find_package_handle_standard_args)
   /usr/share/cmake-3.13/Modules/CMakeFindDependencyMacro.cmake:48 
(find_package)
   /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake:26 
(find_dependency)
   CMakeLists.txt:130 (find_package)


--- End Message ---
--- Begin Message ---
Source: gr-limesdr
Source-Version: 2.0.0-27-gca01a64-2

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated gr-limesdr 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, 13 Oct 2019 20:51:15 +0200
Source: gr-limesdr
Architecture: source
Version: 2.0.0-27-gca01a64-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 915597 936662 940069
Changes:
 gr-limesdr (2.0.0-27-gca01a64-2) experimental; urgency=medium
 .
   * Add B-D python3-six, the doxygen docs need it.
 .
 gr-limesdr (2.0.0-27-gca01a64-1) experimental; urgency=medium
 .
   [ A. Maitland Bottoms ]
   * New upstream tag v2.0.0
   * Update homepage (Closes: #915597)
 .
   [ Christoph Berg ]
   * New upstream version 2.0.0-27-gca01a64 with support for gnuradio 3.8.
   * Set package name to libgnuradio-limesdr3.0.0.
   * Add liborc-0.4-dev and libgmp-dev build-dependencies. (Closes: #940069)
   * Add debian/gitlab-ci.yml.
   * Move to Section: hamradio.
   * Add ${python3:Depends} dependency. (Closes: #936662)
   * Update copyright after upstream source was restructured.
Checksums-Sha1:
 1ffae1063c98e5ecc5933172f105c9354a095bd8 2342 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 16c3c9ba846ac664c1bd73812d7287e487c852ed 3664 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz
Checksums-Sha256:
 06270c3994f78ebb49760b1052e28e333d987f7529d5dcc6a2fa0114fbe3e100 2342 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 bab77b043c3b8a1e18de74bf916b54f0b033784c815bd3e106aa8645bf74b60b 3664 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz
Files:
 9ecf1a24517af05f70236127f96ebbc8 2342 hamradio optional 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 82877935459cf4b8af1fa894464d3495 3664 hamradio optional 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl2jct0ACgkQTFprqxLS
p64tIg//QJw0UmxWI84aGLTTEndnKnNO9uWtxnClzlmkbsRn5OV2eOdxk35aNg0g
YnKdgMR6puRkV/GwXvtCtMGfjLuaRthC5G1k2boIz3jvL9PvdSKgujuz2HnQ92zP
fRiH/H4i+LUj7QiQLOrphYbm2i1r8hS27bPn2WqJWHyFA/EAKVW02umHwzHS7w5n
MB5LxLjOTqR9jBOyFJ8kRtyP5OBPLz4vzryi7zN1jibyurvYUd5iIsMMAQEss2r0
AT2kF0s9LHO1jYW3Ks+oUY2F+oCPjIEKs50uGByk5MACi0/9P4G1EpZNaS1sGUI7
8GfGWFZYn2MQFfmsJLf5zWSTdZPUcuaylH3KwDzkG80G0jmN4wibCK3NedIExA1P
Lp7LCntHr0C1f9X0e2ofzwN/1nObtV2QaRJ/lrjyHG7AQXiDiF4xg13bIsKm8Dzg
yTd8TS3jW70WMMFSt4HwrITLKFq1v1ySnS1dPLF3BQECTxRI0E+o/GePe3spLRNr
a5yIaz3Oowv+meOYCA12B0jSWJ2rW6cLj/Aal1BRlk5ikFWAlnOE0f2pw01TTxwH
O5iQCaLavSH6wbdOtUtbvnayTZIQnj/FpDte8vLgU9C1OJSdTzLTnnNHxI2akTTW
myBjkvEd4+voLqHCDrO0z9ETJGTzimKxVW5J4tToS+MgdZjLvy8=
=fjLq
-END PGP S

Processed: retitle 940069 to gr-limesdr: FTBFS in unstable

[Debian Bug Tracking System]

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

> retitle 940069 gr-limesdr: FTBFS in unstable
Bug #940069 [gr-limesdr] gr-limsdr FTBFS in unstable.
Changed Bug title to 'gr-limesdr: FTBFS in unstable' from 'gr-limsdr FTBFS in 
unstable.'.
> thanks
Stopping processing here.

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

Bug#906578: [makehuman] Future Qt4 removal

[Boyuan Yang]

Looks like makehuman upstream is working on the Qt5 version but it hasn't
finished yet. There's only alpha versions at 
https://github.com/makehumancommunity/makehuman . I guess we should move on
and have it removed if upstream is acting that slowly.

Muammar: if you have any other thoughts, please let us know now. Otherwise a
removal before 2020 should be reasonable.

Regards,
Boyuan Yang

在 2019-10-11五的 23:14 +0200，Moritz Mühlenhoff写道：
> Hi,
> there hasn't been any followup on this bug since over a year and we're now
> moving
> forward with the Qt4 removal, are there immediate plans to port makehuman to
> Qt5 or
> should we remove it from the archive?
> 
> Cheers,
> Moritz


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

Bug#942276: libmessage-passing-perl: test failure

[gregor herrmann]

Source: libmessage-passing-perl
Version: 0.116-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on 
https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmessage-passing-perl/3150247/log.gz
we have a test failure which also happens at build time and makes the
package FTBFS:

t/configfile.t .. 
ok 1 - use Message::Passing;
Can't locate object method "_options_prog_name" via package "Message::Passing" 
at /usr/share/perl5/MooX/Options/Role.pm line 348.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 25 just after 1.
Dubious, test returned 25 (wstat 6400, 0x1900)
All 1 subtests passed 


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jWdFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgapGA//UnAloNglGDbKd6YCFqojZkoe690l2Nxkiv9g2Y1vnGxVD+X8kU3jaWb8
btnYiy2j5IUG6hfZkrK8beDaB9zozu3/UOg/QgARYI+n2WXnqhufNqS7XRBrmg6e
RupIB5Yi/c3lmPzzW2rNG7QyjudvjeoncNX05uxGK98tS7Rv9cGyVOLB3AHBnxPD
/WkQPtJu0myhOF0SrQMZ2mzbw5+JQlXAUNs3bi20mDP6YG5ISJB108cOnFe6lfRt
OX8Gwl0ZeHLeoVrbqo9wOVtDxU4qtFJH4v6hItM7271NpFv76PDEpdhIGi1xsTx3
51uH/lLvfSuKV5xKCb2RevgG8q5JCqzXoqtov0JOtu7eO8kGCCOOLAUvlDtjyW7i
zZlxj/Z2IhPUwvG1xitMGMu2/t37jXfRxoSTW532RlHrMf2UqOxlv9wgY/ygexwT
arzWOvGX5fFfiHuyULYiP7Fxis/5KttCd2wnICe+I8u9dVURlFWRSUDnoQ1PC9my
fw8KNF7/J9a+LkrHsb3rFwEVzDy8sizAimYnJyuz63SeEzBnnavEuFLLsmf6Bqdw
akeXO28zlwN3PC8RlkrOmPzZPH+F1wuC+L6SzTH2A97fG8eKlogkczs8UXSA5PsI
IEynKsJPZSbEUz/tRNJUPuE5v63vLK2scganIuXGwMoj+KDOeGE=
=Yfoi
-END PGP SIGNATURE-

Bug#942275: libmoox-options-perl: test failure

[gregor herrmann]

On Sun, 13 Oct 2019 19:01:19 +0200, gregor herrmann wrote:

> Currently this only happens in unstable, and I haven't yet seen why.

Maybe yesterday's upload of libnamespace-autoclean-perl?


Cheers,
gregor
-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Peter Ratzenbeck: Bonnie Bessie Logan


signature.asc
Description: Digital Signature

Bug#942275: libmoox-options-perl: test failure

[gregor herrmann]

Source: libmoox-options-perl
Version: 4.103-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, libmoox-options-perl has a test
failure which also makes the package FTBFS:

https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmoox-options-perl/3150674/log.gz

t/16-namespace_clean.t .. 
ok 1 - TestNamespaceClean is a package
Can't locate object method "__" via package "TestNamespaceClean" at 
/usr/share/perl5/MooX/Options/Role.pm line 352.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed 


Currently this only happens in unstable, and I haven't yet seen why.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jWF9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYIqw//XGnU4dpmTGHf/zNwzGrxbtXxwtCws0FycziVOMyibaHrsSnfWo1z4q9x
S2l9SRolRx6QdzS0iXdege9Ay0tqAvE+ae6lGkHsb6zg8fe1oGGkh8B35TMx6U0j
jhjjtJU0iruB0mMr783TKH/4kWlAOfTprq6C0MPbiJ5WBm3v+sCe2JArfKIJhcW6
GheUF+lH2zsXR9u6AcZK5uOlxo/Bjawak6akbxbNfPxxcpOWKmUz9V1h8iaElim6
qqgiAJRXMDty0+tNP3tYYK4ta4cwUzj2cGevfBIBlNYhUMsK7sRlLjO2Rb6e22mU
wwr5HGcEjkr1o//h7wZ1bYU/yK5GDtrw0lnbluG9qHu1cO0kIYF0Cut8wTWisw9q
aPYau5b6xE+70swsRiArrA3UPrmWKgUK2lRhZC1MVzpakFT01uaINwaMyCL606bG
jB4/g7+BbKmLCyTSOx0uWaRIG5KgtFQTm8Dm7agjQdsLVMTmOXzRQi7saP0slHCT
ak80F2h4LY3PtlNWK9+T1RBHkC0FaZxOqWVEVUVXC+U4kSQzF8F5ir8NwiDPKr1E
+kYXOdecvcKw1nC+SKQIJLrAt2ibTjogd33v5QXIjRNd+/lHtZeHANV5m5TeNqWK
uNEo2qrVys+d2RAWBjvboxJgtW7K24cMnUTYIw6C9kc2UJc7/K4=
=vx9q
-END PGP SIGNATURE-

Bug#935042: Program phones home by default

[Birger Schacht]

Hi,

On 8/18/19 3:21 PM, Robie Basak wrote:
> Package: lynis
> Version: 2.6.2-1
> Severity: serious

https://www.debian.org/Bugs/Developer#severities says:
> serious is a severe violation of Debian policy (roughly, it violates a
> "must" or "required" directive)"

Robie, could you please point out the part of the Debian policy that
this package is violating?

thanks,
Birger

Bug#942270: task-spanish depends on removed manpages-es

[Moritz Muehlenhoff]

Source: tasksel
Severity: grave

task-spanish depends on manpages-es, which has been removed from the archive.

Cheers,
Moritz

Bug#942039: marked as done (loggerhead: not co-installable with loggerhead-breezy)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:32:28 +
with message-id <20191013153228.ga...@jelmer.uk>
and subject line Resolved
has caused the Debian Bug report #942039,
regarding loggerhead: not co-installable with loggerhead-breezy
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.)


-- 
942039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: loggerhead
Version: 1.19~bzr494-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package loggerhead-breezy.
  Preparing to unpack .../loggerhead-breezy_1.20~bzr551+dfsg-1_all.deb ...
  Unpacking loggerhead-breezy (1.20~bzr551+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/loggerhead-breezy_1.20~bzr551+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/loggerhead-serve', which is also in package 
loggerhead 1.19~bzr494-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/loggerhead-breezy_1.20~bzr551+dfsg-1_all.deb

loggerhead is the newer package, uploaded a few days ago, while the last
loggerhead-breezy upload was nearly a year ago.

cheers,

Andreas


loggerhead=1.19~bzr494-1_loggerhead-breezy=1.20~bzr551+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
loggerhead-breezy has been removed from Debian, resolving this bug.--- End Message ---

Processed: ossim: FTBFS with GEOS 3.8.0 (error: no matching function for call)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ossimlabs/ossim/issues/243
Bug #942269 [src:ossim] ossim: FTBFS with GEOS 3.8.0 (error: no matching 
function for call)
Set Bug forwarded-to-address to 'https://github.com/ossimlabs/ossim/issues/243'.

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

Bug#942269: ossim: FTBFS with GEOS 3.8.0 (error: no matching function for call)

[Bas Couwenberg]

Source: ossim
Version: 2.9.1-1
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so
Control: forwarded -1 https://github.com/ossimlabs/ossim/issues/243

Dear Maintainer,

Your package FTBFS with GEOS 3.8.0:

 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp: In member function 'void 
OssimPolyArea2dPrivate::setGeometry(const ossimPolygon&, const 
std::vector&)':
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:152:64: error: no matching 
function for call to 
'geos::geom::GeometryFactory::createPolygon(geos::geom::LinearRing*&, 
std::vector*&)'
   152 |  m_geometry = geomFactory()->createPolygon(shell, holes);
   |^
 ...
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:778:109: error: no matching 
function for call to 
'geos::geom::GeometryFactory::createMultiPolygon(std::vector&)
 const'
   778 |
m_privateData->setGeometry(m_privateData->m_geometry->getFactory()->createMultiPolygon(values));
   |
 ^
 ...
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp: In member function 'bool 
ossimPolyArea2d::loadState(const ossimKeywordlist&, const char*)':
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:848:64: error: no matching 
function for call to 
'OssimPolyArea2dPrivate::setGeometry(std::unique_ptr)'
   848 | m_privateData->setGeometry(reader.read(wkt.c_str()));
   |^

Kind Regards,

Bas

Bug#933445: marked as done (sandboxgamemaker: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:42 +
with message-id 
and subject line Bug#942186: Removed package(s) from unstable
has caused the Debian Bug report #933445,
regarding sandboxgamemaker: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 2.8.2+dfsg-1+rm

Dear submitter,

as the package sandboxgamemaker 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/942186

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#933408: marked as done (usbprog: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:15:38 +
with message-id 
and subject line Bug#941180: Removed package(s) from unstable
has caused the Debian Bug report #933408,
regarding usbprog: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 0.2.0-2.2+rm

Dear submitter,

as the package usbprog 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/941180

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#875219: marked as done ([unixodbc-gui-qt] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:18:08 +
with message-id 
and subject line Bug#942264: Removed package(s) from unstable
has caused the Debian Bug report #875219,
regarding [unixodbc-gui-qt] 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.)


-- 
875219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unixodbc-gui-qt
Version: 2.3.0-4
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 ---
Version: 2.3.0-4+rm

Dear submitter,

as the package unixodbc-gui-qt 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/942264

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#934248: marked as done (Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:15:09 +
with message-id 
and subject line Bug#941153: Removed package(s) from unstable
has caused the Debian Bug report #934248,
regarding Should this package be removed?
to be marked as done.

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

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


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

The last release of manpages-es was in 2005 and the last upload in 2011.

As already pointed out in #860177, the translations are consequentially
very outdated, I did some random sampling and e.g

- For a basic command like mkdir(1) in Spanish only documents three of
the current seven options in the English manpages

- proc(5) documents the state of Linux 2.4.17

>From my PoV such extremely outdated documentation probably does more harm
than good?

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 1.55-10+rm

Dear submitter,

as the package manpages-es 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/941153

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#875172: marked as done ([rlplot] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:17:21 +
with message-id 
and subject line Bug#942263: Removed package(s) from unstable
has caused the Debian Bug report #875172,
regarding [rlplot] 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.)


-- 
875172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rlplot
Version: 1.5-3
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 ---
Version: 1.5-4+rm

Dear submitter,

as the package rlplot 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/942263

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#933411: marked as done (fwknop-gui: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:13 +
with message-id 
and subject line Bug#941240: Removed package(s) from unstable
has caused the Debian Bug report #933411,
regarding fwknop-gui: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


-- 
933411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwknop-gui
Severity: normal

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 1.3+dfsg-1+rm

Dear submitter,

as the package fwknop-gui 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/941240

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#764896: marked as done (sandboxgamemaker: sandbox_unix fails to start, "cannot find core textures")

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:42 +
with message-id 
and subject line Bug#942186: Removed package(s) from unstable
has caused the Debian Bug report #764896,
regarding sandboxgamemaker: sandbox_unix fails to start, "cannot find core 
textures"
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.)


-- 
764896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sandboxgamemaker
Version: 2.8.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Installed package `sandboxgamemaker` via aptitude. 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Invoked `sandbox-unix` from terminal (menu item not generated).

   * What was the outcome of this action?
Console output follows:

andyman@warthog:~$ sandbox_unix 
Using home directory: /home/andyman/.platinumarts/
init: sdl
init: net
init: game
init: video: mode
init: video: misc
init: gl
Renderer: Gallium 0.4 on AMD ARUBA (X.Org)
Driver: 3.0 Mesa 10.2.6
Rendering using the OpenGL GLSL shader path.
could not load texture data/notexture
could not find core textures

   * What outcome did you expect instead?

Expected to launch Sandbox. I inspected the files installed by the package:

andyman@warthog:~$ dpkg -L sandboxgamemaker 
/.
/usr
/usr/games
/usr/games/sandbox_unix
/usr/lib
/usr/lib/sandboxgamemaker
/usr/lib/sandboxgamemaker/sandbox_client_ssp
/usr/lib/sandboxgamemaker/sandbox_client_rpg
/usr/lib/sandboxgamemaker/sandbox_client_movie
/usr/lib/sandboxgamemaker/sandbox_server_movie
/usr/lib/sandboxgamemaker/sandbox_client_krs
/usr/lib/sandboxgamemaker/sandbox_server_fps
/usr/lib/sandboxgamemaker/sandboxgamemaker_glauncher
/usr/lib/sandboxgamemaker/sandbox_client_fps
/usr/share
/usr/share/sandboxgamemaker
/usr/share/sandboxgamemaker/server-init.cfg
/usr/share/applications
/usr/share/applications/sandboxgamemaker.desktop
/usr/share/doc
/usr/share/doc/sandboxgamemaker
/usr/share/doc/sandboxgamemaker/copyright
/usr/share/doc/sandboxgamemaker/changelog.gz
/usr/share/doc/sandboxgamemaker/README.Debian.gz
/usr/share/doc/sandboxgamemaker/changelog.Debian.gz
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/sandboxgamemaker
/usr/share/man
/usr/share/man/man6
/usr/share/man/man6/sandbox_unix.6.gz
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/48x48
/usr/share/icons/hicolor/48x48/apps
/usr/share/icons/hicolor/48x48/apps/sandboxgamemaker.png
/usr/share/icons/hicolor/128x128
/usr/share/icons/hicolor/128x128/apps
/usr/share/icons/hicolor/128x128/apps/sandboxgamemaker.png
/usr/share/pixmaps
/usr/share/pixmaps/sandboxgamemaker.xpm
/usr/share/menu
/usr/share/menu/sandboxgamemaker

None of these files appears to contain texture data.
I don't find a directory called "data" anywhere.

I read the README.Debian file but found no reference to a data/ directory.
Neither did I find anything indicating that I need to download more stuff.
Am I missing something? In a package like this I'd be unsurprised to find that 
DFSG requires that assets be acquired separately from the package; is this the 
case?

Thanks for packaging this program. I look forward to playing with it once I can 
get it working.
I'd also be interested in helping with maintenance if you want assistance.


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

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sandboxgamemaker depends on:
ii  libc6 2.19-11
ii  libenet7  1.3.12+ds-2
ii  libgcc1   1:4.9.1-16
ii  libgl1-mesa-glx [libgl1]  10.2.6-1
ii  libsdl-image1.2   1.2.12-5+b3
ii  libsdl-mixer1.2   1.2.12-11+b1
ii  libsdl1.2debian   1.2.15-10
ii  libstdc++64.9.1-16
ii  libwxbase3.0-03.0.1-3
ii  libwxgtk3.0-0 3.0.1-3
ii  libx11-6  2:1.6.2-3
ii  zlib1g1:1.2.8.dfsg-2

Versions of packages sandboxgamemaker recommends:
ii  libsmpeg0  0.4.5+cvs20030824-7.1
pn  mikmod 
ii  timidity   2.13.2-40.2

sandboxgamemaker suggests no packages.

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

Dear submitt

Bug#938962: Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is avail

[Ritesh Raj Sarraf]

Hi.

On Sun, 2019-10-06 at 18:18 +0100, Ben Hutchings wrote:
> On Sun, 2019-10-06 at 15:35 +, Scott Kitterman wrote:
> > The reason it's still there is in the cruft report:
> 
> Sorry, I didn't realise that was something I could look up.
> 
> >   - broken Build-Depends:
> > user-mode-linux: linux-source-4.19
> > 
> > Is user-mode-linux maintained?  This seems to come up somewhat
> > regularly.

It is maintained. It is just that the latest upload is blocked by DBug:
#938962


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#875219: Should we file a removal bug?

[Moritz Mühlenhoff]

On Tue, Sep 17, 2019 at 12:06:20PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi! We have seen no activity in this bug, should we file a removal bug?
> 
> Cheers, Lisandro.

I've filed a removal bug now.

Cheers,
Moritz

Bug#875172: [rlplot] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Sep 29, 2019 at 10:41:07PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 11:09:19PM +0200, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Source: rlplot
> > Version: 1.5-3
> > 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
> 
> rlplot is dead upstream, does anyone intend to port it themselves? Otherwise
> let's remove it, we're moving forward with the Qt4 removal.

I've filed a removal bug now.

Cheers,
Moritz

Bug#931880: marked as done (slurm-llnl: CVE-2019-12838)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 10:00:35 +
with message-id 
and subject line Bug#931880: fixed in slurm-llnl 19.05.3.2-1
has caused the Debian Bug report #931880,
regarding slurm-llnl: CVE-2019-12838
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.)


-- 
931880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-llnl
Version: 18.08.6.2-1
Severity: grave
Tags: security upstream
Control: found -1 18.08.5.2-1 
Control: found -1 16.05.9-1+deb9u4
Control: found -1 16.05.9-1

Hi,

The following vulnerability was published for slurm-llnl. I'm filling
it with an RC severity to be on safe side, but if you have more
information available and think the RC severity is not warranted
please feel free to then downgrade.

CVE-2019-12838[0]:
| SchedMD Slurm 17.11.x, 18.08.0 through 18.08.7, and 19.05.0 allows SQL
| Injection.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-12838
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12838
[1] https://lists.schedmd.com/pipermail/slurm-announce/2019/25.html

Please adjust the affected versions in the BTS as needed. [1] say that
whilest only 19.05 and 18.08 releases are patched previous releases
were affected as well.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: slurm-llnl
Source-Version: 19.05.3.2-1

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

Debian distribution maintenance software
pp.
Gennaro Oliva  (supplier of updated slurm-llnl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Oct 2019 18:18:52 +0200
Source: slurm-llnl
Binary: libpam-slurm libpam-slurm-adopt libpmi0 libpmi0-dbgsym libpmi0-dev 
libpmi2-0 libpmi2-0-dbgsym libpmi2-0-dev libslurm-dev libslurm-perl libslurm34 
libslurm34-dbgsym libslurmdb-perl slurm-client slurm-client-dbgsym 
slurm-client-emulator slurm-wlm slurm-wlm-basic-plugins 
slurm-wlm-basic-plugins-dbgsym slurm-wlm-basic-plugins-dev slurm-wlm-doc 
slurm-wlm-emulator slurm-wlm-torque slurmctld slurmctld-dbgsym slurmd 
slurmd-dbgsym slurmdbd slurmdbd-dbgsym sview
Architecture: source amd64 all
Version: 19.05.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Description:
 libpam-slurm - PAM module to authenticate using the SLURM resource manager
 libpam-slurm-adopt - PAM module to authenticate users running a SLURM job and 
track th
 libpmi0- SLURM PMI library implementation
 libpmi0-dev - SLURM PMI library implementation development files
 libpmi2-0  - SLURM PMI2 library implementation
 libpmi2-0-dev - SLURM PMI2 library implementation development files
 libslurm-dev - SLURM development files
 libslurm-perl - Perl API for SLURM
 libslurm34 - Runtime library files for SLURM
 libslurmdb-perl - Perl API for the SLURM database
 slurm-client - SLURM client side commands
 slurm-client-emulator - SLURM client side commands for the emulator
 slurm-wlm  - Simple Linux Utility for Resource Management
 slurm-wlm-basic-plugins - SLURM basic plugins
 slurm-wlm-basic-plugins-dev - SLURM basic plugins development files
 slurm-wlm-doc - SLURM documentation
 slurm-wlm-emulator - SLURM emulator
 slurm-wlm-torque - Torque compatibility wrappers for SLURM
 slurmctld  - SLURM central management daemon
 slurmd - SLURM compute node daemon
 slurmdbd   - Secure enterprise-wide interface to a database for SLURM
 sview  - GUI to view and modify SLURM state
Closes: 931880
Changes:
 slurm-llnl (19.05.3.2-1) unstable; urgency=medium
 .
   * New upstream release fixes CVE-2019-12838 (Closes: #931880)
   * Remove libslurmdb packages as it was merged into libslurm
   * Bump standard version to 4.4.1 (no changes)
   * Update d/copyright
   * Sync configurators with upstream
   * Refresh patches
   * Increase libslurm version to 34
  

Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: Bug#941432: Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

[Alexandre Rossi]

Le 13 octobre 2019 01:04:46 GMT+02:00, "Pierre-Elliott Bécue"  
a écrit :
>Le jeudi 03 octobre 2019 à 11:50:48+0200, Jonas Smedegaard a écrit :
>> Quoting Alexandre Rossi (2019-10-02 15:04:54)
>> > > > > > Do you have plans/solutions regarding this issue? Is it
>possible 
>> > > > > > to drop uwsgi-core dependency on libmatheval1?
>> > > > > 
>> > > > > It should be as simple as not building the matheval plugin
>which is 
>> > > > > not critical to uwsgi. Should I go on with this?
>> > > > 
>> > > > Yeah, I just wasn't sure that it'd be an acceptable solution
>for you.
>> > > > 
>> > > > But it's perfectly fine with me. :)
>> > > 
>> > > Well, I would say "tolerable" rather than "acceptable" - it is a
>real 
>> > > annoyance since it will directly remove features now offered in
>uwsgi.
>> > 
>> > upstream says in 1.9.20 changelog:
>> > 
>> > The matheval support has been removed, while a generic
>“matheval” plugin
>> > (for internal routing) is available (but not compiled in by
>default).
>> > See below for the new way for making “math” in config files.
>> > 
>> > > @Alexandre: Make sure to add a NEWS entry warning users of the
>removal 
>> > > of matheval - ideally enumerating explicitly all uwsgi options
>which has 
>> > > disappeared and may silently wreak havoc on local systems.
>> > > 
>> > > Also, better check e.g. with codesearch.debian.net if any
>packages rely 
>> > > on matheval-related uwsgi config options, and if so alert them
>with 
>> > > bugreports.
>> > 
>> > Search on "uwsgi matheval" or "uwsgi math" yields no result.
>> 
>> Ah well, seems you got better knowledge here than me, Alex :-)
>
>Thanks for taking the time to answer.
>
>Do you require some assistance regarding a new upload of uwsgi? I'm
>eager to dedicate some time to it if you can't do so. :)

I have a patch but I have not been able to test it yet because the py2 removal 
makes the package FTBS... I'm close to fix it though. I'll post an update here 
by wednesday.

Alex

Bug#925627: marked as done (adplug: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 10:00:13 +
with message-id 
and subject line Bug#925627: fixed in adplug 2.3.1+dfsg-1
has caused the Debian Bug report #925627,
regarding adplug: 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.)


-- 
925627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:adplug
Version: 2.2.1+dfsg3-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/adplug_2.2.1+dfsg3-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.

[...]
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DPACKAGE_NAME=\"adplug\" 
-DPACKAGE_TARNAME=\"adplug\" -DPACKAGE_VERSION=\"2.2.1\" 
-DPACKAGE_STRING=\"adplug\ 2.2.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"adplug\" -DVERSION=\"2.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBSTDC__=1 -DHAVE_GETOPT_H=1 
-I.  -Dstricmp=strcasecmp -I/usr/include/libbinio   -g -O2 -c -o dro.lo dro.cpp
libtool: compile:  g++ -DPACKAGE_NAME=\"adplug\" -DPACKAGE_TARNAME=\"adplug\" 
-DPACKAGE_VERSION=\"2.2.1\" "-DPACKAGE_STRING=\"adplug 2.2.1\"" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"adplug\" 
-DVERSION=\"2.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
-DLT_OBJDIR=\".libs/\" -DHAVE_LIBSTDC__=1 -DHAVE_GETOPT_H=1 -I. 
-Dstricmp=strcasecmp -I/usr/include/libbinio -g -O2 -c dro.cpp  -fPIC -DPIC -o 
.libs/dro.o
libtool: compile:  g++ -DPACKAGE_NAME=\"adplug\" -DPACKAGE_TARNAME=\"adplug\" 
-DPACKAGE_VERSION=\"2.2.1\" "-DPACKAGE_STRING=\"adplug 2.2.1\"" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"adplug\" 
-DVERSION=\"2.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
-DLT_OBJDIR=\".libs/\" -DHAVE_LIBSTDC__=1 -DHAVE_GETOPT_H=1 -I. 
-Dstricmp=strcasecmp -I/usr/include/libbinio -g -O2 -c dro.cpp -o dro.o 
>/dev/null 2>&1
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DPACKAGE_NAME=\"adplug\" 
-DPACKAGE_TARNAME=\"adplug\" -DPACKAGE_VERSION=\"2.2.1\" 
-DPACKAGE_STRING=\"adplug\ 2.2.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"adplug\" -DVERSION=\"2.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBSTDC__=1 -DHAVE_GETOPT_H=1 
-I.  -Dstricmp=strcasecmp -I/usr/include/libbinio   -g -O2 -c -o lds.lo lds.cpp
libtool: compile:  g++ -DPACKAGE_NAME=\"adplug\" -DPACKAGE_TARNAME=\"adplug\" 
-DPACKAGE_VERSION=\"2.2.1\" "-DPACKAGE_STRING=\"adplug 2.2.1\"" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"adplug\" 
-DVERSION=\"2.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAV

Bug#942252: lintian: t/scripts/pod-synopsis.t: (Wstat: 256 Tests: 66 Failed: 1)

[Sebastian Ramacher]

Source: lintian
Version: 2.26.0
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

lintian 2.26.0 failed to build on the arch all buildd:

| Test Summary Report
| ---
| t/scripts/pod-synopsis.t  
  (Wstat: 256 Tests: 66 Failed: 1)
|   Failed test:  29
|   Non-zero exit status: 1
| Files=1017, Tests=35989, 654 wallclock secs ( 8.61 usr  5.30 sys + 2139.84 
cusr 389.91 csys = 2543.66 CPU)
| Result: FAIL

| make[1]: *** [debian/rules:50: runtests] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:120: binary-indep] Error 2
| dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


See
https://buildd.debian.org/status/fetch.php?pkg=lintian&arch=all&ver=2.26.0&stamp=1570670200&raw=0
for the full build log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#941917: nginx: FTBFS on several architectures: luajit.h: No such file or directory

[Christos Trochalakis]

On Mon, Oct 07, 2019 at 06:16:48PM +0300, Niko Tyni wrote:

This package failed to build from source on arm64, mips64el, ppc64el
and s390x, but earlier versions built there successfully in the past.

This is preventing 1.16.1-1 testing migration and is a blocker for
the ongoing Perl 5.30 transition.

See https://buildd.debian.org/status/package.php?p=nginx&suite=unstable

From the arm64 log:

 cc -c -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -DNDK_SET_VAR -I src/core -I src/event -I src/event/modules -I src/os/unix -I 
src/http/modules/perl -I /<>/debian/modules/http-ndk/objs -I objs/addon/ndk -I /<>/debian/modules/http-ndk/src -I 
/<>/debian/modules/http-ndk/objs -I objs/addon/ndk -I /<>/debian/modules/nchan/src -I 
/<>/debian/modules/http-lua/src/api -I /usr/include/lua5.1 -I /<>/debian/modules/rtmp -I /usr/include/libxml2 -I objs -I src/http -I 
src/http/modules -I src/http/v2 -I /<>/debian/modules/http-ndk/src -I src/mail -I src/stream \
-o objs/addon/src/ngx_http_lua_log.o \
/<>/debian/modules/http-lua/src/ngx_http_lua_log.c
 In file included from 
/<>/debian/modules/http-lua/src/ngx_http_lua_script.h:11,
  from 
/<>/debian/modules/http-lua/src/ngx_http_lua_script.c:13:
 /<>/debian/modules/http-lua/src/ngx_http_lua_common.h:20:10: 
fatal error: luajit.h: No such file or directory
20 | #include 
   |  ^~
 compilation terminated.
 make[3]: *** [objs/Makefile:2443: objs/addon/src/ngx_http_lua_script.o] Error 1



Sorry for the long delay. I uploaded 1.16.1-2 yesterday which downgrades
http-lua to v0.0.13, the last working version, to unblock the perl
transition.

Copying from the http-lua's README (master, not yet released v0.0.16):
https://github.com/openresty/lua-nginx-module


Since version v0.10.16 of this module, the standard Lua interpreter
(also known as "PUC-Rio Lua") is not supported anymore.


So I am working on a patch that skips building the module for non luajit
archs.

Bug#941124: marked as done (elixir-lang (autopkgtest) fails with new erlang)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 07:19:34 +
with message-id 
and subject line Bug#941124: fixed in elixir-lang 1.9.1.dfsg-1.1
has caused the Debian Bug report #941124,
regarding elixir-lang (autopkgtest) fails with new erlang
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.)


-- 
941124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu elixir-lang_1.9.1.dfsg-1 . ANY . unstable . -m "Rebuild against erlang 22.1"

Hi release team!

Apparently, elixir-land needs to be rebuilt against newer erlang 22.1.
Currently, it doesn't pass autopkgtest (see [1] for details).

There were some internal changes in Erlang re module (regular expressions) which
triggered the test failure. After a simple rebuild all tests pass again.

[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/e/elixir-lang/3018464/log.gz

-- System Information:
Debian Release: 10.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'oldoldstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: elixir-lang
Source-Version: 1.9.1.dfsg-1.1

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated elixir-lang 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, 13 Oct 2019 09:39:24 +0300
Source: elixir-lang
Architecture: source
Version: 1.9.1.dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Evgeny Golyshev 
Changed-By: Sergei Golovan 
Closes: 941124
Changes:
 elixir-lang (1.9.1.dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add a dependency of the elixir binary package on erlang-pcre-
 virtual package to prevent installation when PCRE in Erlang changes,
 invalidating precompiled regexes (closes: #941124).
   * Move to ${erlang:Depends} substitution variable to calculate the
 dependencies automatically.
Checksums-Sha1:
 1c8fd8b15c7f2518349f7b8bde9f76114a3a5626 2157 elixir-lang_1.9.1.dfsg-1.1.dsc
 8d4b4474145d72ea68393b86de3c489de780b2c7 7044 
elixir-lang_1.9.1.dfsg-1.1.debian.tar.xz
 8a17e4c21b29c930340d0e19b7e5fe88fef81e5f 11013 
elixir-lang_1.9.1.dfsg-1.1_amd64.buildinfo
Checksums-Sha256:
 3425265e68894bbd77000c12b4e8eec8fb7048bb292e212384064bf305b45004 2157 
elixir-lang_1.9.1.dfsg-1.1.dsc
 bbc612ceae126f7efe87484a52f18dca8af004f4659a53027a0dffc9acc2f005 7044 
elixir-lang_1.9.1.dfsg-1.1.debian.tar.xz
 0919649ebc862cbf9aeeccf12ae9c26aed01e39b97caef2462c00139ea583c09 11013 
elixir-lang_1.9.1.dfsg-1.1_amd64.buildinfo
Files:
 dce20fd9891c3ea191e8db19cec8599c 2157 interpreters optional 
elixir-lang_1.9.1.dfsg-1.1.dsc
 1213a0fa14da043f58a6c40472c484a4 7044 interpreters optional 
elixir-lang_1.9.1.dfsg-1.1.debian.tar.xz
 4ece7e210a4ed05a2bb4261037f49b99 11013 interpreters optional 
elixir-lang_1.9.1.dfsg-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAl2iy88ACgkQTyrk60tj
54esyQ/+K1ltcFn9lJytV1YlzQ6T/+fjzJIYrxuj+G81F8uk4a2YQ1esEdls+R3u
/Zb/96S96kYelU5ixRwnO5B/ZzW3a/1vROBZ58KLnWbhiSg+EZZTv8YoErJ5r3cX
oEvj1rxzmhGeTVICt2lCuaFvzt/oGjAPUz+XfZ+24+6yoGs5ydXhHlt6aScuF/g9
OssIaqOJdjICo2w6Mw3nOXz1WfXL5TQwilWJedCY3EACRIvPmHB8nADWq6SnU5Rv
/vi1xGkcAi52Fn8sthqkjsaWUeQUuy5Tlqd1JNgzJX/az2dDd8BckCsLveftBK3M
k824BduYBUxaaDaKGSw26e1JpBciUfydVJbioPQ0vSTn6YaRRaDZXf5t2QOEUUue
KbqkeGevvDwL92ZbEte2ihIepK9tWmDhaBtB+ESUPcfvKVCixWqKp0IA5872GCEx
jzzPomdW5hCT4bskvT6oa1u3qXXmqlWK2OjlpNGfHxpz5jXzBabfHqROmHM/x7pl
MYPuAwtf2TKYEVXN1jbbK0IBVMyqh0fKqn1FSKeDiAGxEQC6SBMaf7mBJaOQMZSx
bg