Bug#906505: marked as done (qlandkartegt: FTBFS in buster/sid (unable to find string literal operator))

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:54:52 +
with message-id 
and subject line Bug#906515: Removed package(s) from unstable
has caused the Debian Bug report #906505,
regarding qlandkartegt: FTBFS in buster/sid (unable to find string literal 
operator)
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.)


-- 
906505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qlandkartegt
Version: 1.8.1+ds-8
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/qlandkartegt-1.8.1+ds'
cp -r debian/hicolor/ src/icons/
dh_auto_configure -- -DGPX_EXTENSIONS:BOOL=TRUE \
 -DQK_QT5_PORT=1 \
 -DCMAKE_VERBOSE_MAKEFILE=1
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DGPX_EXTENSIONS:BOOL=TRUE -DQK_QT5_PORT=1 -DCMAKE_VERBOSE_MAKEFILE=1 ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works

[... snipped ...]

[  2%] Linking CXX static library ../../lib/libgetopt.a
cd /<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu/3rdparty/getopt && 
/usr/bin/cmake -P CMakeFiles/getopt.dir/cmake_clean_target.cmake
cd /<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu/3rdparty/getopt && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/getopt.dir/link.txt --verbose=1
/usr/bin/ar qc ../../lib/libgetopt.a  CMakeFiles/getopt.dir/CGetOpt.cpp.o 
CMakeFiles/getopt.dir/moc_CGetOpt.cpp.o
/usr/bin/ranlib ../../lib/libgetopt.a
make[4]: Leaving directory 
'/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu'
[  2%] Built target getopt
make -f 3rdparty/map2gcm/CMakeFiles/map2gcm.dir/build.make 
3rdparty/map2gcm/CMakeFiles/map2gcm.dir/depend
make[4]: Entering directory 
'/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu'
cd /<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu && /usr/bin/cmake 
-E cmake_depends "Unix Makefiles" /<>/qlandkartegt-1.8.1+ds 
/<>/qlandkartegt-1.8.1+ds/3rdparty/map2gcm 
/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu 
/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu/3rdparty/map2gcm 
/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu/3rdparty/map2gcm/CMakeFiles/map2gcm.dir/DependInfo.cmake
 --color=
Scanning dependencies of target map2gcm
make[4]: Leaving directory 
'/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu'
make -f 3rdparty/map2gcm/CMakeFiles/map2gcm.dir/build.make 
3rdparty/map2gcm/CMakeFiles/map2gcm.dir/build
make[4]: Entering directory 
'/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu'
[  2%] Building CXX object 3rdparty/map2gcm/CMakeFiles/map2gcm.dir/main.cpp.o
cd /<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu/3rdparty/map2gcm && 
/usr/bin/c++  -DQK_QT5_PORT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DVER_MAJOR=1 -DVER_MINOR=8 -DVER_STEP=1 
-I/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu/3rdparty/map2gcm 
-I/<>/qlandkartegt-1.8.1+ds/3rdparty/map2gcm 
-I/<>/qlandkartegt-1.8.1+ds/obj-x86_64-linux-gnu 
-I/<>/qlandkartegt-1.8.1+ds/3rdparty/QZip -I/usr/include/gdal 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++  -g -O2 
-fdebug-prefix-map=/<>/qlandkartegt-1.8.1+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fsigned-char   -fPIC -fPIC -std=gnu++11 -o 
CMakeFiles/map2gcm.dir/main.cpp.o -c /<>/qlandkartegt-1.8.1+ds/3rdpa
 rty/map2gcm/main.cpp
/<>/qlandkartegt-1.8.1+ds/3rdparty/map2gcm/main.cpp: In function 'int 
main(int, char**)':
/<>/qlandkartegt-1.8.1+ds/3rdparty/map2gcm/main.cpp:43:46: error: 
unable to find string literal operator 'operator""_MKSTR' with 'const char 
[20]', 'long unsigned int' arguments
 #define VER_STR 
_MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP)
  ^

Bug#889275: marked as done (sipwitch-cgi is empty)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:56:58 +
with message-id 
and subject line Bug#906802: Removed package(s) from unstable
has caused the Debian Bug report #889275,
regarding sipwitch-cgi is empty
to be marked as done.

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

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


-- 
889275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sipwitch-cgi
Version: 1.9.15-3
Severity: grave

$ dpkg -L sipwitch-cgi 
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/sipwitch-cgi
/usr/share/doc/sipwitch-cgi/AUTHORS
/usr/share/doc/sipwitch-cgi/NEWS.gz
/usr/share/doc/sipwitch-cgi/README.gz
/usr/share/doc/sipwitch-cgi/TODO
/usr/share/doc/sipwitch-cgi/buildinfo_amd64.gz
/usr/share/doc/sipwitch-cgi/changelog.Debian.amd64.gz
/usr/share/doc/sipwitch-cgi/changelog.Debian.gz
/usr/share/doc/sipwitch-cgi/changelog.gz
/usr/share/doc/sipwitch-cgi/copyright
$
--- End Message ---
--- Begin Message ---
Version: 1.9.15-3+rm

Dear submitter,

as the package sipwitch 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/906802

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

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:55:46 +
with message-id 
and subject line Bug#906581: Removed package(s) from unstable
has caused the Debian Bug report #900468,
regarding attal: 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.)


-- 
900468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: attal
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal

attal fails to build from source since 2016, and depends on Qt 4 which
is no longer maintained. It was not released with stretch. I think it
might be time for this package to be removed from unstable.

If you agree, please reassign this bug to the archive administrators
with control commands similar to these:

severity xx normal
reassign xx ftp.debian.org
retitle xx RM: attal -- RoQA; FTBFS, depends on obsolete Qt 4, not in 
stretch

Conversely, if you think this package should remain in Debian, please
close this bug, and fix its other RC bugs.

Please note that Games Team svn is no longer used and will soon be archived.
If this package continues to be in Debian, it should be imported into
salsa.debian.org git.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.0~rc2-2+rm

Dear submitter,

as the package attal 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/906581

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

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:56:10 +
with message-id 
and subject line Bug#906582: Removed package(s) from unstable
has caused the Debian Bug report #900479,
regarding attal-themes: 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.)


-- 
900479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: attal-themes
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal
Control: block -1 by 900468

attal fails to build from source since 2016, and depends on Qt 4 which
is no longer maintained. It was not released with stretch. attal-themes
appears to be a data package for attal, so is useless without attal.
It might be time for these packages to be removed from unstable.

If you agree, please reassign this bug to the archive administrators
with control commands similar to these:

severity xx normal
reassign xx ftp.debian.org
retitle xx RM: attal-themes -- RoQA; useless without attal

(This package cannot be removed unless attal is: see #900468.)

Conversely, if you think this package should remain in Debian, please
close this bug, and fix attal's RC bugs.

Please note that Games Team svn is no longer used and will soon be archived.
If this package continues to be in Debian, it should be imported into
salsa.debian.org git.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.0~rc2.dfsg1-1+rm

Dear submitter,

as the package attal-themes 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/906582

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#831094: marked as done (attal: FTBFS with GCC 6: cmath:568:33: error: 'FP_NAN' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:55:46 +
with message-id 
and subject line Bug#906581: Removed package(s) from unstable
has caused the Debian Bug report #831094,
regarding attal: FTBFS with GCC 6: cmath:568:33: error: 'FP_NAN' was not 
declared in this scope
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.)


-- 
831094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: attal
Version: 1.0~rc2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -O2 -O2 -Wall -W -D_REENTRANT -fPIC 
> -DATTAL_VERSION=\"1.0-rc2\" -DWITH_SOUND 
> -DATT_THEMES_DIR=\"/usr/share/games/attal/themes/\" 
> -DATT_TRANSL_DIR=\"/usr/share/games/attal/translations/\" 
> -DATT_DOCS_DIR=\"/usr/share/doc/attal/\" -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
> -I/usr/include/qt4/QtXml -I/usr/include/qt4 -I.. -Imoc -o obj/genericMap.o 
> genericMap.cpp
> In file included from /usr/include/c++/6/math.h:36:0,
>  from genericMap.cpp:31:
> /usr/include/c++/6/cmath: In function 'constexpr int std::fpclassify(float)':
> /usr/include/c++/6/cmath:568:33: error: 'FP_NAN' was not declared in this 
> scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>  ^~
> /usr/include/c++/6/cmath:568:41: error: 'FP_INFINITE' was not declared in 
> this scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>  ^~~
> /usr/include/c++/6/cmath:568:54: error: 'FP_NORMAL' was not declared in this 
> scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>   ^
> /usr/include/c++/6/cmath:569:5: error: 'FP_SUBNORMAL' was not declared in 
> this scope
>  FP_SUBNORMAL, FP_ZERO, __x); }
>  ^~~~
> /usr/include/c++/6/cmath:569:19: error: 'FP_ZERO' was not declared in this 
> scope
>  FP_SUBNORMAL, FP_ZERO, __x); }
>^~~
> /usr/include/c++/6/cmath: In function 'constexpr int std::fpclassify(double)':
> /usr/include/c++/6/cmath:573:33: error: 'FP_NAN' was not declared in this 
> scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>  ^~
> /usr/include/c++/6/cmath:573:41: error: 'FP_INFINITE' was not declared in 
> this scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>  ^~~
> /usr/include/c++/6/cmath:573:54: error: 'FP_NORMAL' was not declared in this 
> scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>   ^
> /usr/include/c++/6/cmath:574:5: error: 'FP_SUBNORMAL' was not declared in 
> this scope
>  FP_SUBNORMAL, FP_ZERO, __x); }
>  ^~~~
> /usr/include/c++/6/cmath:574:19: error: 'FP_ZERO' was not declared in this 
> scope
>  FP_SUBNORMAL, FP_ZERO, __x); }
>^~~
> /usr/include/c++/6/cmath: In function 'constexpr int std::fpclassify(long 
> double)':
> /usr/include/c++/6/cmath:578:33: error: 'FP_NAN' was not declared in this 
> scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>  ^~
> /usr/include/c++/6/cmath:578:41: error: 'FP_INFINITE' was not declared in 
> this scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>  ^~~
> /usr/include/c++/6/cmath:578:54: error: 'FP_NORMAL' was not declared in this 
> scope
>{ return __builtin_fpclassify(FP_NAN, FP_INFINITE, FP_NORMAL,
>   ^
> /usr/include/c++/6/cmath:579:5: error: 'FP_SUBNORMAL' was not declared in 
> this scope
>  FP_SUBNORMAL, FP_ZERO, __x); }
>  ^~~~
> /usr/include/c++/6/cmath:579:19: error: 'FP_ZERO' 

Bug#843012: marked as done (libcsp: CVE-2016-8596 CVE-2016-8597 CVE-2016-8598)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:55:17 +
with message-id 
and subject line Bug#906563: Removed package(s) from unstable
has caused the Debian Bug report #843012,
regarding libcsp: CVE-2016-8596 CVE-2016-8597 CVE-2016-8598
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.)


-- 
843012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcsp
Version: 1.4+fdd49b7+dfsg-3
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerabilities were published for libcsp.

CVE-2016-8596[0]:
| Buffer overflow in the csp_can_process_frame in csp_if_can.c in the
| libcsp library v1.4 and earlier allows hostile components connected to
| the canbus to execute arbitrary code via a long csp packet.

CVE-2016-8597[1]:
| Buffer overflow in the csp_sfp_recv_fp in csp_sfp.c in the libcsp
| library v1.4 and earlier allows hostile components with network access
| to the SFP underlying network layers to execute arbitrary code via
| specially crafted SFP packets.

CVE-2016-8598[2]:
| Buffer overflow in the zmq interface in csp_if_zmqhub.c in the libcsp
| library v1.4 and earlier allows hostile computers connected via a zmq
| interface to execute arbitrary code via a long packet.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8596
[1] https://security-tracker.debian.org/tracker/CVE-2016-8597
[2] https://security-tracker.debian.org/tracker/CVE-2016-8598

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1.4+fdd49b7+dfsg-3+rm

Dear submitter,

as the package libcsp 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/906563

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#896249: marked as done (python-tau: tau fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:44:36 +
with message-id 
and subject line Bug#905956: Removed package(s) from unstable
has caused the Debian Bug report #896249,
regarding python-tau: tau fails to import
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.)


-- 
896249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tau
Version: 2.17.3.1.dfsg-4.2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-tau importing the module tau
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/tau.py", line 42, in 
import pytau
ImportError: /usr/lib/tau/x86_64/lib/libTAU.so: undefined symbol: 
getLinuxHighResolutionTscCounter

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 2.17.3.1.dfsg-4.2+rm

Dear submitter,

as the package tau 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/905956

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#887161: marked as done (llvm-toolchain-3.8: keep out of testing)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:43:06 +
with message-id 
and subject line Bug#873331: Removed package(s) from unstable
has caused the Debian Bug report #887161,
regarding llvm-toolchain-3.8: keep out of testing
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.)


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

We don't want llvm 3.8 in buster. I'm removing it from testing now,
and this bug should prevent it from re-entering testing.

Emilio
--- End Message ---
--- Begin Message ---
Version: 1:3.8.1-27+rm

Dear submitter,

as the package llvm-toolchain-3.8 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/873331

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#871011: marked as done (clang-3.8: incompatible with libstdc++-7-dev)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:43:06 +
with message-id 
and subject line Bug#873331: Removed package(s) from unstable
has caused the Debian Bug report #871011,
regarding clang-3.8: incompatible with libstdc++-7-dev
to be marked as done.

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

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


-- 
871011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-3.8
Version: 1:3.8.1-24
Severity: serious
Tags: sid buster
Control: block 853620 with -1

echo '#include ' | clang++-3.8 -c -x c++ -
In file included from :1:
In file included from 
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/cstdlib:77:
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/bits/std_abs.h:101:3:
 error: unknown type name '__float128'
  __float128
  ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/bits/std_abs.h:102:7:
 error: unknown type name '__float128'
  abs(__float128 __x)
  ^
2 errors generated.


Andreas
--- End Message ---
--- Begin Message ---
Version: 1:3.8.1-27+rm

Dear submitter,

as the package llvm-toolchain-3.8 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/873331

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#859540: marked as done (pavuk: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:43:36 +
with message-id 
and subject line Bug#905861: Removed package(s) from unstable
has caused the Debian Bug report #859540,
regarding pavuk: Please migrate to openssl1.1 in Buster
to be marked as done.

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

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


-- 
859540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pavuk
Version: 0.9.35-6
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Version: 0.9.35-6.1+rm

Dear submitter,

as the package pavuk 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/905861

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#817292: marked as done (bugsx: Removal of dh_desktop)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:44:03 +
with message-id 
and subject line Bug#905863: Removed package(s) from unstable
has caused the Debian Bug report #817292,
regarding bugsx: Removal of dh_desktop
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.)


-- 
817292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bugsx
Severity: important
Tags: dh_desktop-removal

Hi,

The package bugsx is still using dh_desktop according to lintian.
This command was obsoleted in 2009 and has since then done nothing but
print a warning.

 * Please remove all remaining calls to dh_desktop at your
   earliest convenience.

 * I will remove dh_undocumented from debhelper in the first upload
   after 1st of April.


If your package is *also* affected by any of the following debhelper
related deprecations, please consider fixing them at the same time:

 * debhelper compat 4 is deprecated and is expected to be removed
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * If your package does *not* have a debian/compat, please add one with
   the correct compat level.
   - The compat file will be required by 15th of April.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 1.08-12+rm

Dear submitter,

as the package bugsx 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/905863

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#896085: marked as done (tk8.5: Time to remove from Debian)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:39:48 +
with message-id 
and subject line Bug#905799: Removed package(s) from unstable
has caused the Debian Bug report #896085,
regarding tk8.5: Time to remove from Debian
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.)


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

Dear Maintainer,

Tcl/Tk 8.5 has reached its end-of-life, so it's time to remove it from Debian.
Applications which use Tcl/Tk should switch to 8.6 which is available
for a few years already.

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

Kernel: Linux 4.15.0-0.bpo.2-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)

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

Dear submitter,

as the package tk8.5 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/905799

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#899472: marked as done (cipux-rpc-client: Invalid maintainer address cipux-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:38:50 +
with message-id 
and subject line Bug#905444: Removed package(s) from unstable
has caused the Debian Bug report #899472,
regarding cipux-rpc-client: Invalid maintainer address 
cipux-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cipux-rpc-client
Version: 3.4.0.7-2.1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of cipux-rpc-client,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package cipux-rpc-client since the list address
cipux-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
cipux-de...@lists.alioth.debian.org is 10.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.4.0.7-2.1+rm

Dear submitter,

as the package cipux-rpc-client 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/905444

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#831418: marked as done (EOL: not to be released with Stretch)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:34:58 +
with message-id 
and subject line Bug#904565: Removed package(s) from unstable
has caused the Debian Bug report #831418,
regarding EOL: not to be released with Stretch
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.)


-- 
831418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zendframework
Severity: serious
Tags: security sid stretch

Hi,

Upstream recently stated [0] that “Zend Framework 1 reaches its End of
Life (EOL) […] on 28 September 2016.”

0: https://framework.zend.com/blog/2016-06-28-zf1-eol.html

Therefore, we should not release it with Stretch (and we’ll do our best
to support it during Jessie lifetime). Reverse dependencies already had
an important bug report about zendframework removal for Stretch a while
ago.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.12.20+dfsg-1+rm

Dear submitter,

as the package zendframework 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/904565

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#901537: marked as done (ooniprobe: FTBFS: ERROR: test_send_packet_with_answer (ooni.tests.test_txscapy.TestTxScapy))

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:36:25 +
with message-id 
and subject line Bug#905211: Removed package(s) from unstable
has caused the Debian Bug report #901537,
regarding ooniprobe: FTBFS: ERROR: test_send_packet_with_answer 
(ooni.tests.test_txscapy.TestTxScapy)
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.)


-- 
901537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ooniprobe
Version: 2.3.0-1
Severity: serious
Justification: fails to build from source

Hi,

ooniprobe recently started to FTBFS in a minimal current sid pbuilder
environment:

==
ERROR: test_send_packet_with_answer (ooni.tests.test_txscapy.TestTxScapy)
test_send_packet_with_answer
--
TimeoutError:  (test_send_packet_with_answer) still 
running at 120.0 secs

--
Ran 156 tests in 171.430s

FAILED (errors=1, skipped=25)


Andreas


ooniprobe_2.3.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 2.3.0-1+rm

Dear submitter,

as the package ooniprobe 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/905211

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#801935: marked as done (python-django-threadedcomments: Fails to build from source with Django 1.8)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:35:55 +
with message-id 
and subject line Bug#904929: Removed package(s) from unstable
has caused the Debian Bug report #801935,
regarding python-django-threadedcomments: Fails to build from source with 
Django 1.8
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.)


-- 
801935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-threadedcomments
Version: 0.9.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django18 django18-ftbfs

Hello,

while preparing to upload Django 1.8 to unstable, I rebuilt all reverse
build-dependencies of python-django. Among those I noticed that
python-django-threadedcomments fails to build.

Please update your package to work with Django 1.8 as I will upload
it to unstable at the start of November 2015 (and the same time raise
the severity of this bug to serious). Django 1.8.5 is available
in experimental so that you can easily try it out.

The failing build log of your package is available here:
https://people.debian.org/~hertzog/django18-rebuild/python-django-threadedcomments_0.9.0-1

Thank you in advance!
--- End Message ---
--- Begin Message ---
Version: 0.9.0-1+rm

Dear submitter,

as the package python-django-threadedcomments 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/904929

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#896352: marked as done (python-django-threadedcomments: threadedcomments fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:35:55 +
with message-id 
and subject line Bug#904929: Removed package(s) from unstable
has caused the Debian Bug report #896352,
regarding python-django-threadedcomments: threadedcomments fails to import
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.)


-- 
896352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django-threadedcomments
Version: 0.9.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-django-threadedcomments importing the module 
threadedcomments
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/threadedcomments/__init__.py", line 4, 
in 
from threadedcomments.models import ThreadedComment
  File "/usr/lib/python2.7/dist-packages/threadedcomments/models.py", line 2, 
in 
from django.contrib.comments.models import Comment
ImportError: No module named comments.models

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 0.9.0-1+rm

Dear submitter,

as the package python-django-threadedcomments 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/904929

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#755649: marked as done (python-django-threadedcomments: Please ensure it works with Django 1.7)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:35:55 +
with message-id 
and subject line Bug#904929: Removed package(s) from unstable
has caused the Debian Bug report #755649,
regarding python-django-threadedcomments: Please ensure it works with Django 1.7
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.)


-- 
755649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-threadedcomments
Version: 0.9.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package python-django-threadedcomments depends on python-django. As you 
might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
Version: 0.9.0-1+rm

Dear submitter,

as the package python-django-threadedcomments 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/904929

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#909866: marked as done (ooniprobe: (Build-) Depends on vanished package python-txtorcon)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:36:25 +
with message-id 
and subject line Bug#905211: Removed package(s) from unstable
has caused the Debian Bug report #909866,
regarding ooniprobe: (Build-) Depends on vanished package python-txtorcon
to be marked as done.

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

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


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

Hi,

txtorcon has stopped building the Python 2 variant python-txtorcon (on
which ooniprobe depends and build-depends) and only builds
python3-txtorcon.

According to https://github.com/ooni/probe-legacy/blob/master/setup.py,
Ooniprobe only supports Python 2.

And https://github.com/ooni/probe sounds as if the python variant is not
further developed. (No commits since February this year either.) So I
don't expect a port to Python 3 is a suitable solution to this issue.

Moving forward to the next-generation CLI (Go) or desktop variant
(JavaScript) is probably the way to go.

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ooniprobe depends on:
ii  adduser3.118
ii  geoip-database 20180315-1
ii  python 2.7.15-3
ii  python-certifi 2018.8.24-1
ii  python-geoip   1.3.2-1+b4
ii  python-ipaddr  2.2.0-1
ii  python-klein   17.2.0-2
ii  python-openssl 18.0.0-1
ii  python-pkg-resources   40.2.0-1
ii  python-pyasn1  0.4.2-3
ii  python-scapy   2.4.0-2
ii  python-twisted-core18.7.0-2
ii  python-txsocksx1.15.0.2-1
ii  python-txtorcon0.19.3-4
ii  python-yaml3.12-1+b2
ii  python-zope.interface  4.3.2-1+b2
ii  tor0.3.4.8-1

Versions of packages ooniprobe recommends:
ii  python-dumbnet  1.12-8
ii  python-pypcap   1.2.2-1

Versions of packages ooniprobe suggests:
pn  geoip-database-contrib  
pn  obfs4proxy  

-- debconf information:
* ooniprobe/run-cronjob: false
--- End Message ---
--- Begin Message ---
Version: 2.3.0-1+rm

Dear submitter,

as the package ooniprobe 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/905211

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#912397: xserver-xorg-video-amdgpu: Running web browser performance test crashes whole system on AMD RX 460

[Will Brokenbourgh]

Package: xserver-xorg-video-amdgpu
Version: 1.2.0-1+b1
Severity: serious

Dear Maintainer,

When a web browser performance test was performed using the latest git version 
of the surf browser
it appears the 'xserver-xorg-vide-amdgpu' driver crashes the whole system, 
resulting in the 
system usually hanging and the AMD RX 460 video adapter shutting off.  This is 
reproduceable.

How to reproduce:
* Have an AMD RX 460 video card functioning as the primary video adapter
* Clone the latest surf web browser: git clone https://git.suckless.org/surf
* Run `make` on the cloned code (install any missing dependencies then try 
again)
* Run the newly compiled surf browser from the cloned directory: `./surf 
browserbench.org`
* Run the 'MotionMark' performance test on the browserbench.org web page
* When the browser test begins the 'soft orbs/lights' part of the test, the 
screen turns off suddenly, 
   and it appears the system hangs.  3 out of 5 times after the crash the 
computer reboots but there is no video

Special condition:
When the 'firmware-amd-graphics' package is NOT installed, the crash does not 
happen.  I began to submit a 
bug report for that package when 'reportbug' advised me that the bug most 
likely isn't caused by a firmware
package so I canceled.

The same web browser performance test on Firefox and Chrome do not cause a 
crash.  No other crashes have happened 
except for this one specific case when 'surf' is used for the web performance 
test.

Log output:
AFTER the crash the system partition was mounted read-only from another Linux 
distro.  The Xorg.0.log, dmesg, 
kern.log, messages and other logs have absolutely *zero* messages about the 
crash itself.  All of the logs
show the proper startup and functioning of the system but no shut-down-related 
messages.

dmesg has this one error message during startup:
[8.179502] amdgpu :01:00.0: Invalid PCI ROM header signature: expecting 
0xaa55, got 0x

System summary:
* ASUS M5A78L-M PLUS/USB3 motherboard, BIOS 0502
* AMD FX-6300 six-core processor
* ASRock Radeon RX 460 video adapter
* 8 GB RAM

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev e5)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-8-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08)

Xorg X server log files on system:
--
-rw-r--r-- 1 will will 44859 Oct 29 18:09 
/home/will/.local/share/xorg/Xorg.0.log
-rw-r--r-- 1 root root 53007 Oct 30 21:52 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[12.804] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[12.805] X Protocol Version 11, Revision 0
[12.805] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[12.805] Current Operating System: Linux debian 4.9.0-8-amd64 #1 SMP Debian 
4.9.110-3+deb9u6 (2018-10-08) x86_64
[12.805] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 
root=UUID=bed98052-ac8e-4b0a-8505-b58a2a1e36fe ro quiet
[12.805] Build Date: 25 October 2018  10:20:30AM
[12.805] xorg-server 2:1.19.2-1+deb9u4 (https://www.debian.org/support) 
[12.805] Current version of pixman: 0.34.0
[12.805]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[12.805] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[12.805] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 30 21:51:50 
2018
[12.819] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[12.848] (==) No Layout section.  Using the first Screen section.
[12.849] (==) No screen section available. Using defaults.
[12.849] (**) |-->Screen "Default Screen Section" (0)
[12.849] (**) |   |-->Monitor ""
[12.849] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[12.849] (==) Automatically adding devices
[12.850] (==) Automatically enabling devices
[12.850] (==) Automatically adding GPU devices
[12.850] (==) Max clients allowed: 256, resource mask: 0x1f
[12.929] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[12.929]Entry deleted from font path.
[12.936] (==) FontPath set to:
/usr/share/fonts/X11/misc,

Processed: tagging 912391

[Debian Bug Tracking System]

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

> tags 912391 + buster
Bug #912391 [src:segment] segment FTBFS with OpenJDK 11
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#904492: marked as done (python3-async: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:30:30 +
with message-id 
and subject line Bug#904505: Removed package(s) from unstable
has caused the Debian Bug report #904492,
regarding python3-async: fails to install with Python 3.7
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.)


-- 
904492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-async
Version: 0.6.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up python3-async (0.6.2-2) ...
File "/usr/lib/python3/dist-packages/async/test/task.py", line 6
  from async.task import (
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/async/test/test_channel.py", line 7
  from async.channel import (
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/async/test/test_example.py", line 8
  from async.pool import ThreadPool
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/async/test/test_graph.py", line 7
  from async.graph import (
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/async/test/test_performance.py", line 
13
  from async.pool import ThreadPool
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/async/test/test_pool.py", line 18
  from async.pool import (
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/async/test/test_thread.py", line 8
  from async.thread import (
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-async (--configure):
   installed python3-async package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   python3-async


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-async=0.6.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.6.2-2+rm

Dear submitter,

as the package python-async 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/904505

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#834917: marked as done (python-async: FTBFS on single CPU machines)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:30:30 +
with message-id 
and subject line Bug#904505: Removed package(s) from unstable
has caused the Debian Bug report #834917,
regarding python-async: FTBFS on single CPU machines
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.)


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

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

copying async/graph.py -> /<>/.pybuild/pythonX.Y_3.5/build/async
copying async/thread.py -> /<>/.pybuild/pythonX.Y_3.5/build/async
copying async/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/async
creating /<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/task.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/test_graph.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/test_channel.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/test_pool.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/lib.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/test_performance.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/test_thread.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
copying async/test/test_example.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/async/test
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m nose 
...EThreadpool: Starting single task (async = 0) with 0 threads
Threadpool: processed 1000 individual items, with 0 threads, one at a time, in 
0.009996 s ( 100040.643038 items / s )
Threadpool: processed 1000 individual items in chunks of 250, with 0 threads, 
one at a time, in 0.009609 s ( 104069.275240 items / s)
done with everything
Threadpool: starting async dependency test in 0 threads
Dependent Tasks: evaluated 1000 items of 5 dependent in 0.009781 s ( 102237 
items / s )
Dependent Tasks: evaluated 1000 items with read(1) of 5 dependent in 0.042389 s 
( 23590 items / s )
Dependent Tasks: evaluated 1000 items with read(1), min_size=250, of 5 
dependent in 0.011971 s ( 83535 items / s )
Dependent Tasks: evaluated 2 connected pools and 1000 items with read(0), of 9 
dependent tasks in 0.018785 s ( 53233 items / s )
Dependent Tasks: evaluated 2 connected pools and 1000 items with read(1), of 9 
dependent tasks in 0.040263 s ( 24836 items / s )
..
==
ERROR: test_base (async.test.test_performance.TestThreadPoolPerformance)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/async/test/test_performance.py", 
line 30, in test_base
for num_threads in range(0, self.max_threads*2 + 1, self.max_threads // 2):
ValueError: range() step argument must not be zero
 >> begin captured logging << 
root: DEBUG: async: Actual asynchronous operation was disabled as it is slower 
that way
- >> end captured logging << -

--
Ran 6 tests in 0.772s

FAILED (errors=1)
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
  File "/<>/.pybuild/pythonX.Y_2.7/build/async/thread.py", line 
173, in run
  File "/usr/lib/python2.7/Queue.py", line 179, in get
  File "/usr/lib/python2.7/threading.py", line 384, in notify
: 'NoneType' object is not callable
E: pybuild pybuild:274: test: plugin distutils failed with: exit 

Bug#898407: marked as done (flif: CVE-2018-10972)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:22:22 +
with message-id 
and subject line Bug#903600: Removed package(s) from unstable
has caused the Debian Bug report #898407,
regarding flif: CVE-2018-10972
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.)


-- 
898407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flif
Version: 0.3-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/FLIF-hub/FLIF/issues/503

Hi,

The following vulnerability was published for flif.

CVE-2018-10972[0]:
| An issue was discovered in Free Lossless Image Format (FLIF) 0.3. The
| TransformPaletteC::process function in transform/palette_C.hpp allows
| remote attackers to cause a denial of service (heap-based buffer
| overflow) or possibly have unspecified other impact via a crafted file.

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-2018-10972
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10972
[1] https://github.com/FLIF-hub/FLIF/issues/503

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.3-5+rm

Dear submitter,

as the package flif 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/903600

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#821123: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:25:56 +
with message-id 
and subject line Bug#904321: Removed package(s) from unstable
has caused the Debian Bug report #821123,
regarding Useless in Debian
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.)


-- 
821123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: doctrine-sphinx-theme
Version: 0~20130227-1
Severity: serious
Tags: sid stretch

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

I packaged doctrine-sphinx-theme to build doctrine-orm-doc, but we
stopped building it (not DFSG compliant anymore). There is a priori
little point in shipping doctrine-sphinx-theme with the next Debian
stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0~20130227-1+rm

Dear submitter,

as the package doctrine-sphinx-theme 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/904321

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#802050: marked as done (doctrine-sphinx-theme: please migrate to Bootstrap 3.x)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:25:56 +
with message-id 
and subject line Bug#904321: Removed package(s) from unstable
has caused the Debian Bug report #802050,
regarding doctrine-sphinx-theme: please migrate to Bootstrap 3.x
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Twitter Bootstrap 2.x is dead upstream, and the Debian package is
unmaintained.

Please strongly consider to migrate to Bootstrap 3.x, packaged in Debian
as libjs-bootstrap.

I have filed a bugreport upstream regarding this as well:
https://github.com/doctrine/doctrine-sphinx-theme/issues/6

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWIibTAAoJECx8MUbBoAEhSugP/1jRHWEiK+UCORiIUwcLwXAa
b8X9uJuaHEBRaGzdE2sigScKt+XdDC2X60brxqcaY5YHEHsM8X9hO3KtkHLSaTeV
3Uz9B94Fn27XOcDatco4dV1JXL+Od7tX0xf0iOnJPtkCffZUUGmEBIH94aHoUVrc
DFahJP6+GflWC+cGp85D8kT1ncz7yzq3ruLMrGLF3Avt/qK4ox3PtGuPfs1npp1t
6TmHzTbYzE84t4VPEvm60a0gr1HR8bDZ3dDVhl1DFO6OLDAHurzl//nWA/itxSYt
//qF43zo4K4oGCjzuvRbqYTagiYrCk7fejVpw6cD9Dcifr5/LjuLTJIi3lkSyE+A
rNyzB36S7PtVkhLQkZxl4VH5+KJ/6RY8b/MA/NmJaSBftY7AXpxK2kk4dqtovmvL
pBBcw0PbC9GEm7ZCurM0AWuDcTvjJA+hOLMOlGN1o1P8fNHmOKWawV8lp1JOKieB
ZGg1eSR6dtVgc6Fj2b6BTutIR+tkQ9Gu8wLMQiw1RjGMzFrQPrmIxoYslwpcB5aE
r/EmCQ+ButngVeOTSUxJGipPbh4yufXtGU1MmRcMEzSDt02iJb3Igzx3UI1r6y84
DBkU2WgXIAbu5sXwwISyTqhQeVvHm6taPHWXKoHc0/XZM9PNR9lbSebibxA93Zgb
fSbY4Ucass8LVu7pI8YA
=iUBe
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0~20130227-1+rm

Dear submitter,

as the package doctrine-sphinx-theme 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/904321

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#842130: marked as done (Useless in Stretch)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:26:21 +
with message-id 
and subject line Bug#904322: Removed package(s) from unstable
has caused the Debian Bug report #842130,
regarding Useless in Stretch
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.)


-- 
842130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-ie7
Version: 2.1~beta4-2
Severity: serious
Tags: sid stretch
X-Debbugs-CC: s...@packages.debian.org

[ Filed with RC-severity by the maintainer to see it removed from
  testing. ]

libjs-ie7 was packaged as a dependency for spip, but the dependency has
recently been dropped (in version 3.1, now available in Sid and
Stretch). There is little point in keeping libjs-ie7 in Stretch as
nothing uses it anymore.

I intend to ask for removal of this package in a few month. Please do
provide information to this bug report if you disagree with this removal.

Regards

David



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 2.1~beta4-2+rm

Dear submitter,

as the package ie7-js 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/904322

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#898406: marked as done (flif: CVE-2018-10971)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:22:22 +
with message-id 
and subject line Bug#903600: Removed package(s) from unstable
has caused the Debian Bug report #898406,
regarding flif: CVE-2018-10971
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.)


-- 
898406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flif
Version: 0.3-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/FLIF-hub/FLIF/issues/501

Hi,

The following vulnerability was published for flif.

CVE-2018-10971[0]:
| An issue was discovered in Free Lossless Image Format (FLIF) 0.3. The
| Plane function in image/image.hpp allows remote attackers to cause a
| denial of service (attempted excessive memory allocation) via a crafted
| file.

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-2018-10971
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10971
[1] https://github.com/FLIF-hub/FLIF/issues/501

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.3-5+rm

Dear submitter,

as the package flif 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/903600

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#817659: marked as done (rsrce: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:25:30 +
with message-id 
and subject line Bug#904119: Removed package(s) from unstable
has caused the Debian Bug report #817659,
regarding rsrce: Removal of debhelper compat 4
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.)


-- 
817659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rsrce
Severity: important
Usertags: compat-4-removal

Hi,

The package rsrce uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 0.2.2+rm

Dear submitter,

as the package rsrce 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/904119

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

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 05:22:53 +
with message-id 
and subject line Bug#903620: Removed package(s) from unstable
has caused the Debian Bug report #893649,
regarding xvt: 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.)


-- 
893649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xvt
Version: 2.1-20.3
Severity: serious
Justification: QA query

Hi!
I believe that xvt is no longer suitable for inclusion in Debian, and thus
propose its removal.  Not only has it been dead upstream since times
immemorial but also it lacks features so basic it's mind-boggling.

For example, I believed that Windows 3.11's TELNET.EXE was the last terminal
in existence that lacked color support.  Turns out, here we ship xvt, in
2018.  Or, no UTF-8 support is probably worth a RC bug on its own.

More than two decades ago, xvt was superseded by its fork rxvt, which in
turn spawned a multitude of forks on its own.  I for one remember using a
bunch of them on IRIX, when the world was still young...  Those forks have
then died out around the beginning of this millenium, of them only
rxvt-unicode is still struggling along.

As this package is still nominally maintained (well, your last upload was in
2006...), I can't file a RoQA immediately.  Thus, please tell me whether it
should be removed.  If not, please close this bug, otherwise I'll ask for
removal before Buster freeze.


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

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

Versions of packages xvt depends on:
ii  libc6 2.27-2
ii  libx11-6  2:1.6.5-1

xvt recommends no packages.

Versions of packages xvt suggests:
pn  menu  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.1-20.3+rm

Dear submitter,

as the package xvt 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/903620

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: tagging 911507

[Debian Bug Tracking System]

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

> tags 911507 + stretch
Bug #911507 [offlineimap] offlineimap: fails to load imaplib2
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#912395: resteasy3.0 FTBFS with OpenJDK 11

[Adrian Bunk]

Source: resteasy3.0
Version: 3.0.19-4
Severity: serious
Tags: ftbfs

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 6.774 s
[INFO] Finished at: 2018-10-30T15:41:01-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project resteasy-jaxrs: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[5,33]
 package javax.xml.bind.annotation does not exist
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[6,33]
 package javax.xml.bind.annotation does not exist
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[7,33]
 package javax.xml.bind.annotation does not exist
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[16,2]
 cannot find symbol
[ERROR]   symbol: class XmlRootElement
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[17,2]
 cannot find symbol
[ERROR]   symbol: class XmlAccessorType
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[25,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[40,64]
 cannot find symbol
[ERROR]   symbol: class DataSource
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[105,18]
 cannot find symbol
[ERROR]   symbol:   class DataSource
[ERROR]   location: class 
org.jboss.resteasy.plugins.providers.DataSourceProvider
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[170,37]
 cannot find symbol
[ERROR]   symbol:   class DataSource
[ERROR]   location: class 
org.jboss.resteasy.plugins.providers.DataSourceProvider
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[170,11]
 cannot find symbol
[ERROR]   symbol:   class DataSource
[ERROR]   location: class 
org.jboss.resteasy.plugins.providers.DataSourceProvider
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[212,24]
 cannot find symbol
[ERROR]   symbol:   class DataSource
[ERROR]   location: class 
org.jboss.resteasy.plugins.providers.DataSourceProvider
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[43,58]
 cannot find symbol
[ERROR]   symbol:   class DataSource
[ERROR]   location: class 
org.jboss.resteasy.plugins.providers.DataSourceProvider
[ERROR] 
/build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[17,18]
 cannot find symbol
[ERROR]   symbol: variable XmlAccessType
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :resteasy-jaxrs
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/resteasy3.0-3.0.19 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/resteasy3.0-3.0.19/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/resteasy3.0-3.0.19/debian 
-Dmaven.repo.local=/build/1st/resteasy3.0-3.0.19/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#912221: Bug #912221 in jabref marked as pending

[Tony Mancill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/jabref/commit/d2a43a7c05c243f2ef210c4551c9332cda328b92


Add runtime dep on jaxb and update wrapper script for openjdk 11

(Closes: #912221)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912221

Processed: Bug #912221 in jabref marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912221 [jabref] jabref: incompatible with openjdk 11
Added tag(s) pending.

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

Bug#890456: marked as done (pike7.8-gtk: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 03:43:46 +
with message-id 
and subject line Bug#898581: Removed package(s) from unstable
has caused the Debian Bug report #890456,
regarding pike7.8-gtk: Depends on old GNOME libraries
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.)


-- 
890456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pike7.8-gtk
Version: 7.8.866-8
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas libgnomeui libgnome gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

pike7.8-gtk depends on these:

- libgnome-2-0
- libgnomecanvas2-0
- libgnomeui-0
- libgtksourceview2.0-0

As far as I can tell, Pike doesn't offer GTK3 support yet. I think
you're going to need to drop this package.

See also https://bugs.debian.org/885673 for Pike 8.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

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

Dear submitter,

as the package pike7.8 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/898581

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#896311: marked as done (python-django-celery-transactions: djcelery_transactions fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 03:43:14 +
with message-id 
and subject line Bug#897415: Removed package(s) from unstable
has caused the Debian Bug report #896311,
regarding python-django-celery-transactions: djcelery_transactions fails to 
import
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.)


-- 
896311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django-celery-transactions
Version: 0.3.6-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-django-celery-transactions importing the module 
djcelery_transactions
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/djcelery_transactions/__init__.py", 
line 8, in 
from celery.contrib.batches import Batches
ImportError: No module named batches

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 0.3.6-2+rm

Dear submitter,

as the package django-celery-transactions 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/897415

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#897215: marked as done (sikulix: SikuliX 1.1.1 does not support Java 9)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 03:42:45 +
with message-id 
and subject line Bug#897333: Removed package(s) from unstable
has caused the Debian Bug report #897215,
regarding sikulix: SikuliX 1.1.1 does not support Java 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.)


-- 
897215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sikulix
Version: 1.1.1-8
Severity: important

Hi,

see https://github.com/RaiMan/SikuliX-2014/issues/288. Java 9 is the
default in Buster so perhaps this should be RC?

According to https://raiman.github.io/SikuliX1/nightly.html#dailynews,
in SikuliX 1.1.2 most JAVA 9 problems are fixed. Could you please
package it? Thanks in advance!

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

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

Versions of packages sikulix depends on:
ii  antlr3.2   3.2-16
ii  default-jre [java6-runtime]2:1.9-63
ii  jarwrapper 0.63
ii  jruby  9.1.13.0-1
ii  jython 2.7.1+repack-3
ii  libasm-java6.0-1
ii  libcommons-cli-java1.4-1
ii  libguava-java  19.0-1
ii  libjackson2-core-java  2.9.4-1
ii  libjackson2-databind-java  2.9.5-1
ii  libjgoodies-common-java1.8.1-2
ii  libjgoodies-forms-java 1.9.0-3
ii  libjline-java  1.0-2
ii  libjson-simple-java2.3.0-1
ii  libjxgrabkey-java  0.3.2-9
ii  libmac-widgets-java0.10.0+svn416-dfsg1-2
ii  libsikulixapi-java 1.1.1-8
ii  libswing-layout-java   1.0.4-4
ii  libswingx-java 1:1.6.2-3
ii  openjdk-8-jre [java6-runtime]  8u171-b11-1
ii  openjdk-9-jre [java6-runtime]  9.0.4+12-4

sikulix recommends no packages.

sikulix suggests no packages.

-- no debconf information

-- 
intrigeri
--- End Message ---
--- Begin Message ---
Version: 1.1.1-8+rm

Dear submitter,

as the package sikulix 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/897333

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#885461: marked as done (esound: Should not be released with Buster)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 03:42:15 +
with message-id 
and subject line Bug#894269: Removed package(s) from unstable
has caused the Debian Bug report #885461,
regarding esound: Should not be released with Buster
to be marked as done.

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

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


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

This software has been deprecated for many years and the Debian GNOME Team
is targeting its removal for Buster. Bug reports for individual reverse
dependencies has already been filed and can be found via:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=esd-removal
--- End Message ---
--- Begin Message ---
Version: 0.2.41-11+rm

Dear submitter,

as the package esound 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/894269

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#881197: marked as done (django-celery-transactions FTBFS with celery 4.1.0-1)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 03:43:14 +
with message-id 
and subject line Bug#897415: Removed package(s) from unstable
has caused the Debian Bug report #881197,
regarding django-celery-transactions FTBFS with celery 4.1.0-1
to be marked as done.

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

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


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-celery-transactions.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/django-celery-transactions-0.3.6'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="python{version} runtests.py" 
dh_auto_test
I: pybuild base:184: python2.7 runtests.py
Traceback (most recent call last):
  File "runtests.py", line 61, in 
runtests()
  File "runtests.py", line 53, in runtests
django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 85, in 
populate
app_config = AppConfig.create(entry)
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 94, in 
create
module = import_module(entry)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File 
"/build/1st/django-celery-transactions-0.3.6/djcelery_transactions/__init__.py",
 line 8, in 
from celery.contrib.batches import Batches
ImportError: No module named batches
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
runtests.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.3.6-2+rm

Dear submitter,

as the package django-celery-transactions 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/897415

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#896268: marked as done (python3-django-celery-transactions: djcelery_transactions fails to import)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 03:43:14 +
with message-id 
and subject line Bug#897415: Removed package(s) from unstable
has caused the Debian Bug report #896268,
regarding python3-django-celery-transactions: djcelery_transactions fails to 
import
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.)


-- 
896268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-celery-transactions
Version: 0.3.6-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-django-celery-transactions importing the module 
djcelery_transactions
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/djcelery_transactions/__init__.py", line 
8, in 
from celery.contrib.batches import Batches
ModuleNotFoundError: No module named 'celery.contrib.batches'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 0.3.6-2+rm

Dear submitter,

as the package django-celery-transactions 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/897415

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#912394: rsyntaxtextarea FTBFS with OpenJDK 11

[Adrian Bunk]

Source: rsyntaxtextarea
Version: 2.5.0-1
Severity: serious
Tags: ftbfs buster sid

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

...
[javac] 
/build/1st/rsyntaxtextarea-2.5.0/src/org/fife/ui/rsyntaxtextarea/RSyntaxTextArea.java:613:
 error: cannot find symbol
[javac] sm.checkSystemClipboardAccess();
[javac]   ^
[javac]   symbol:   method checkSystemClipboardAccess()
[javac]   location: variable sm of type SecurityManager

Bug#912392: scilab FTBFS with OpenJDK 11

[Adrian Bunk]

Source: scilab
Version: 6.0.1-5
Severity: serious
Tags: ftbfs

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

...
[javac] warning: Supported source version 'RELEASE_6' from annotation 
processor 'org.netbeans.modules.openide.util.NbBundleProcessor' less than 
-source '8'
[javac] warning: Supported source version 'RELEASE_7' from annotation 
processor 'org.netbeans.modules.openide.util.ServiceProviderProcessor' less 
than -source '8'
[javac] warning: Supported source version 'RELEASE_7' from annotation 
processor 'org.netbeans.modules.openide.util.NamedServiceProcessor' less than 
-source '8'
[javac] warning: No processor claimed any of these annotations: 
javax.annotation.Generated
[javac] 
/build/1st/scilab-6.0.1/modules/graphic_objects/src/java/org/scilab/modules/graphic_objects/xmlloader/CSSParser.java:17:
 error: package javax.annotation does not exist
[javac] @javax.annotation.Generated("JFlex")
[javac]  ^
[javac] 1 error
[javac] 4 warnings

BUILD FAILED
/build/1st/scilab-6.0.1/modules/prebuildjava/build.xml:65: The following error 
occurred while executing this line:
/build/1st/scilab-6.0.1/build.incl.xml:111: Compile failed; see the compiler 
error output for details.

Total time: 8 seconds
make[4]: *** [Makefile:757: java] Error 1

Bug#912391: segment FTBFS with OpenJDK 11

[Adrian Bunk]

Source: segment
Version: 1.3.5~svn57+dfsg-1.1
Severity: serious
Tags: ftbfs buter sid

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

...
compile:
[mkdir] Created dir: /build/1st/segment-1.3.5~svn57+dfsg/build/classes
[javac] /build/1st/segment-1.3.5~svn57+dfsg/build.xml:44: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 68 source files to 
/build/1st/segment-1.3.5~svn57+dfsg/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:23:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBContext;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:24:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBException;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:290:
 error: cannot find symbol
[javac] public static JAXBContext getContext(String context) {
[javac]   ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Util
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:305:
 error: cannot find symbol
[javac] public static JAXBContext getContext(String context, 
[javac]   ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Util
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:321:
 error: cannot find symbol
[javac] public static JAXBContext getContext(Class... 
classesToBeBound) {
[javac]   ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Util
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:13:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBContext;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:14:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBException;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:15:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.Marshaller;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:16:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.Unmarshaller;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:30:
 error: cannot find symbol
[javac] private Marshaller marshaller;
[javac] ^
[javac]   symbol:   class Marshaller
[javac]   location: class Bind
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:32:
 error: cannot find symbol
[javac] private Unmarshaller unmarshaller;
[javac] ^
[javac]   symbol:   class Unmarshaller
[javac]   location: class Bind
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:39:
 error: cannot find symbol
[javac] public Bind(JAXBContext context, Schema schema) {
[javac] ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Bind
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/srx/io/bind/Afterbreak.java:11:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlAccessType;
[javac] ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/srx/io/bind/Afterbreak.java:12:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlAccessorType;
[javac] ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/srx/io/bind/Afterbreak.java:13:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlRootElement;
[javac]   

Bug#912393: scala FTBFS with OpenJDK 11

[Adrian Bunk]

Source: scala
Version: 2.11.12-2
Severity: serious
Tags: ftbfs

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

...
locker.reflect:
[mkdir] Created dir: /build/1st/scala-2.11.12/build/locker/classes/reflect
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[locker.reflect] Compiling 158 files to 
/build/1st/scala-2.11.12/build/locker/classes/reflect
[locker.reflect] 
/build/1st/scala-2.11.12/src/reflect/scala/reflect/internal/util/StringOps.scala:48:
 error: missing argument list for method trimTrailingSpace in trait StringOps
[locker.reflect] Unapplied methods are only converted to functions when a 
function type is expected.
[locker.reflect] You can make this conversion explicit by writing 
`trimTrailingSpace _` or `trimTrailingSpace(_)` instead of `trimTrailingSpace`.
[locker.reflect]   def trimAllTrailingSpace(s: String): String = s.lines map 
trimTrailingSpace mkString EOL
[locker.reflect] ^
[locker.reflect] one error found

Bug#912389: snakeyaml FTBFS with OpenJDK 11

[Adrian Bunk]

Source: snakeyaml
Version: 1.21-1
Severity: serious
Tags: ftbfs

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

...
[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.013 s 
<<< FAILURE! - in org.yaml.snakeyaml.generics.ObjectValuesTest
[ERROR] testObjectValuesWithParam(org.yaml.snakeyaml.generics.ObjectValuesTest) 
 Time elapsed: 0.01 s  <<< FAILURE!
junit.framework.AssertionFailedError: class [Ljava.lang.Object; cannot be cast 
to class [Ljava.lang.String; ([Ljava.lang.Object; and [Ljava.lang.String; are 
in module java.base of loader 'bootstrap')
at 
org.yaml.snakeyaml.generics.ObjectValuesTest.testObjectValuesWithParam(ObjectValuesTest.java:93)

Bug#912390: shiro FTBFS with OpenJDK 11

[Adrian Bunk]

Source: shiro
Version: 1.3.2-2
Severity: serious
Tags: ftbfs

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project shiro-guice: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/shiro-1.3.2/support/guice/src/main/java/org/apache/shiro/guice/ShiroModule.java:[26,24]
 package javax.annotation does not exist
[ERROR] 
/build/1st/shiro-1.3.2/support/guice/src/main/java/org/apache/shiro/guice/ShiroModule.java:[65,14]
 cannot find symbol
[ERROR]   symbol: class PreDestroy
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :shiro-guice
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/shiro-1.3.2 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/shiro-1.3.2/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/shiro-1.3.2/debian 
-Dmaven.repo.local=/build/1st/shiro-1.3.2/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#912388: rdp-alignment FTBFS with OpenJDK 11

[Adrian Bunk]

Source: rdp-alignment
Version: 1.2.0-4
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/rdp-alignment-1.2.0'
#Ant is over-complicating things.  Do it the easy way.
jh_build rdp-alignment.jar src
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/commons-cli.jar:/usr/share/java/commons-lang.jar:/usr/share/java/commons-io.jar:/usr/share/java/rdp-readseq.jar:debian/_jh_build.rdp-alignment
 -d debian/_jh_build.rdp-alignment -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
src/edu/msu/cme/rdp/alignment/pairwise/ScoringMatrix.java:27: error: package 
javax.xml.bind.annotation does not exist
import javax.xml.bind.annotation.XmlAccessType;
^
src/edu/msu/cme/rdp/alignment/pairwise/ScoringMatrix.java:28: error: package 
javax.xml.bind.annotation does not exist
import javax.xml.bind.annotation.XmlAccessorType;
^
src/edu/msu/cme/rdp/alignment/pairwise/ScoringMatrix.java:34: error: cannot 
find symbol
@XmlAccessorType(XmlAccessType.FIELD)
 ^
  symbol: class XmlAccessorType
src/edu/msu/cme/rdp/alignment/pairwise/ScoringMatrix.java:34: error: cannot 
find symbol
@XmlAccessorType(XmlAccessType.FIELD)
 ^
  symbol: variable XmlAccessType
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
4 errors
1 warning
make[1]: *** [debian/rules:28: override_dh_auto_build] Error 123

Bug#912386: rdp-readseq FTBFS with OpenJDK 11

[Adrian Bunk]

Source: rdp-readseq
Version: 2.0.2-4
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/rdp-readseq-2.0.2'
jh_build --javacopts="-encoding UTF8" rdp-readseq.jar src
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/commons-cli.jar:/usr/share/java/commons-lang.jar:/usr/share/java/commons-io.jar:debian/_jh_build.rdp-readseq
 -d debian/_jh_build.rdp-readseq -source 1.7 -target 1.7 -encoding UTF8
warning: [options] bootstrap class path not set in conjunction with -source 7
src/edu/msu/cme/rdp/readseq/readers/Sequence.java:11: error: package 
javax.xml.bind.annotation does not exist
import javax.xml.bind.annotation.XmlAttribute;
^
src/edu/msu/cme/rdp/readseq/readers/Sequence.java:12: error: package 
javax.xml.bind.annotation does not exist
import javax.xml.bind.annotation.XmlElement;
^
src/edu/msu/cme/rdp/readseq/readers/Sequence.java:19: error: cannot find symbol
@XmlAttribute
 ^
  symbol:   class XmlAttribute
  location: class Sequence
src/edu/msu/cme/rdp/readseq/readers/Sequence.java:21: error: cannot find symbol
@XmlAttribute
 ^
  symbol:   class XmlAttribute
  location: class Sequence
src/edu/msu/cme/rdp/readseq/readers/Sequence.java:23: error: cannot find symbol
@XmlElement
 ^
  symbol:   class XmlElement
  location: class Sequence
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 errors
1 warning
make[1]: *** [debian/rules:27: override_dh_auto_build] Error 123

Bug#912385: rdp-classifier FTBFS with OpenJDK 11

[Adrian Bunk]

Source: rdp-classifier
Version: 2.10.2-3
Severity: serious
Tags: ftbfs

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

...
junit:
[javac] /build/1st/rdp-classifier-2.10.2/tmp-junit.xml:13: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 18 source files
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 warning
 [echo] Using java version 11.0.1
[junit] Error occurred during initialization of boot layer
[junit] java.lang.module.FindException: Module java.se.ee not found
[junit] Running edu.msu.cme.rdp.classifier.rrnaclassifier.ClassifierTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 
sec

BUILD FAILED
/build/1st/rdp-classifier-2.10.2/tmp-junit.xml:31: Test 
edu.msu.cme.rdp.classifier.rrnaclassifier.ClassifierTest failed (crashed)

Total time: 3 seconds
make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1

Bug#912384: obantoo FTBFS with OpenJDK 11

[Adrian Bunk]

Source: obantoo
Version: 2.1.12+ds1-1
Severity: serious
Tags: ftbfs

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

...
compile:
[mkdir] Created dir: /build/1st/obantoo-2.1.12+ds1/build/bin
[javac] Compiling 154 source files to 
/build/1st/obantoo-2.1.12+ds1/build/bin
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/JUnit/TestUeberweisung.java:19:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBException;
[javac]  ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:13:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBContext;
[javac]  ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:14:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBException;
[javac]  ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:15:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.Marshaller;
[javac]  ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:16:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.Unmarshaller;
[javac]  ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:208:
 error: cannot find symbol
[javac]   SEPAException, JAXBException
[javac]  ^
[javac]   symbol:   class JAXBException
[javac]   location: class Basislastschrift
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:250:
 error: cannot find symbol
[javac]   public void read(File file) throws JAXBException, SEPAException
[javac]  ^
[javac]   symbol:   class JAXBException
[javac]   location: class Basislastschrift
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:13:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlAccessType;
[javac] ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:14:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlAccessorType;
[javac] ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:15:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlElement;
[javac] ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:16:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlType;
[javac] ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:39:
 error: cannot find symbol
[javac] @XmlAccessorType(XmlAccessType.FIELD)
[javac]  ^
[javac]   symbol: class XmlAccessorType
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:40:
 error: cannot find symbol
[javac] @XmlType(name = "CustomerDirectDebitInitiationV02", propOrder = {
[javac]  ^
[javac]   symbol: class XmlType
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/GroupHeaderSDD.java:12:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlAccessType;
[javac] ^
[javac] 
/build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/GroupHeaderSDD.java:13:
 error: package javax.xml.bind.annotation does not exist
[javac] import javax.xml.bind.annotation.XmlAccessorType;
[javac] ^
[javac] 

Bug#912047: nullmailer: FTBFS: Test failure

[gregor herrmann]

On Sat, 27 Oct 2018 13:36:17 -0300, David Bremner wrote:

> > Source: nullmailer
> > Version: 1:2.1-7
> > Severity: serious
> > Tags: ftbfs
> >
> > From my pbuilder build log:
> 
> It's not reproducible in for me sbuild. I guess there's something
> pbuilder specific about this failer. Of course I'd like a fix, but I'll
> need to be convinced it's RC.

I can reproduce the failure, unsurprisingly, as I'm using cowbuilder.

If I'm understanding the tests correctly, the failure is:

Running test /build/nullmailer-2.1/test/tests/protocols...
…
Testing host not found error with smtp.
Result was 5, should be 2.

And this comes from test/tests/protocols:

echo "Testing host not found error with $p."
error 2 protocol $p --host=this.host.can.not.exist 3https://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: Leonard Cohen: You Want It Darker


signature.asc
Description: Digital Signature

Bug#909442: outguess: patch for #909442

[Eriberto]

Em ter, 30 de out de 2018 às 13:03, Frédéric Bonnard
 escreveu:
>
> Tags: patch pending
>
> --
>
> Hi,
>
> it seems there's a race condition that happens when trying to build
> libjpeg.a in directory jpeg-6b-steg (seen with make -j8).
>
> libjpeg.a: ansi2knr $(LIBOBJECTS)
> launches both compilation of ansi2knr and $(LIBOBJECTS) but the latter
> needs ansi2knr before it's compiled. So I make $(LIBOBJECTS) depend on 
> ansi2knr.
>
> Here is a merge request with a patch to fix this.
> https://salsa.debian.org/pkg-security-team/outguess/merge_requests/2
>
> I could reproduce the bug on plummer (ppc64el porterbox) and check the
> fix.
>
> F.

Hi Frédéric,

Thanks a lot for your patch. We have new issues over some
architectures. Please, see here[1].

[1] https://buildd.debian.org/status/package.php?p=outguess=experimental

Regards,

Eriberto

Bug#912383: gnome-commander: Intent to remove from Debian

[Jeremy Bicha]

Source: gnome-commander
Version: 1.4.8-1.1
Severity: serious
Tags: buster sid
X-Debbugs-Cc: ales...@debian.org

gnome-commander was removed from Debian Testing 8 months ago because it
depends on multiple libgnome libraries which the Debian GNOME team is
trying to remove
from Debian.

Therefore, I intend to file a removal bug for gnome-commander very soon.
Please let me know promptly if you agree or object.

It's sad because gnome-commander is being actively developed (last
release was in March). If gnome-commander is removed, it can easily be
added back to Debian once it has been ported to maintained libraries.

See https://bugs.debian.org/891436

Thanks,
Jeremy Bicha

Processed: update gnome-commander libgnome forwarded bug

[Debian Bug Tracking System]

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

> forwarded 891436 https://gitlab.gnome.org/GNOME/gnome-commander/issues/33
Bug #891436 [src:gnome-commander] gnome-commander: build dependency needs 
updating to scour
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-commander/issues/33'.
>
End of message, stopping processing here.

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

Bug#868425: marked as done (gmotionlive: Please drop the (build-)dependency against gnome-vfs)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 01:07:52 +
with message-id 
and subject line Bug#868425: fixed in gmotionlive 1.0-3.1
has caused the Debian Bug report #868425,
regarding gmotionlive: Please drop the (build-)dependency against gnome-vfs
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.)


-- 
868425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmotionlive
Version: 1.0-3
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: gmotionlive
Source-Version: 1.0-3.1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gmotionlive 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, 30 Oct 2018 20:46:33 -0400
Source: gmotionlive
Binary: gmotionlive
Architecture: source
Version: 1.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Maximiliano Curia 
Changed-By: Jeremy Bicha 
Description:
 gmotionlive - Simple multipart/x-mixed-replace viewer
Closes: 868425 886079
Changes:
 gmotionlive (1.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Yavor Doganov ]
   * Add gio_port patch. Closes: #868425, #886079
 .
   [ Jeremy Bicha ]
   * Bump debhelper compat to 11
Checksums-Sha1:
 6dce25a00cd83f65378422ff254a5b43e0daa464 1767 gmotionlive_1.0-3.1.dsc
 bd62e7c8876dd038a29130afea2ea7a5e447c6cd 4052 gmotionlive_1.0-3.1.debian.tar.xz
 388c0b41f5ffee4f240a02c0dc98a3ffccc05959 6853 
gmotionlive_1.0-3.1_source.buildinfo
Checksums-Sha256:
 21ff1704c0b9255e6d4291341892c75bf5ecee810e17f6ef6cf911f28b981c5e 1767 
gmotionlive_1.0-3.1.dsc
 8bf663b3365179cf15fe5c9f40b0bf4c8872f2532712fe407fb24f96743a6756 4052 
gmotionlive_1.0-3.1.debian.tar.xz
 8ad1fe50e0c23cc7d6e1ac77a4a6cb371d343e1c7b185210e40b711052cbdb18 6853 
gmotionlive_1.0-3.1_source.buildinfo
Files:
 f05e3abf4aa10a3ce81202a903285fcc 1767 graphics optional gmotionlive_1.0-3.1.dsc
 b5a13fd7341f2a6df2d5f7a6964036c1 4052 graphics optional 
gmotionlive_1.0-3.1.debian.tar.xz
 672a3db481ceccff8a8b689dc7968aa0 6853 graphics optional 
gmotionlive_1.0-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlvY+44ACgkQ5mx3Wuv+
bH2i9w//SWvERoYZWpTvndt0jrBl+Nf9hvxHT3L4PbHII0yY8i9KtJIhTg2f7zw3
px1NnduH1Yu/h9f5vjbRjICE3aK7qHSEcZKNMnWCNhwa0+O3GXzEHhHbl/5J2Qms
VOSeJDur2MNMY9/2rLvpNiudg1rrh2Ur7M0nn8LBqyW7AxcyKz2cQtFEOd5jvSqI
FJeGeQ0htZswsZunL0ZHGT4NkmwJspa4myncoFdFESD//Q5dCeJNzU5FywCe6DY2
c7Ig8ltiszZvJCwqAObCvt0NsNUVO0/Bk6dTKhrxwBLsTmhnSZUoRNnsZ60Yipmt
JaH3IhxOS2WO3c45bsB/3uqfVkbiq1LQBJdiM0Lz/3uw9eTboJyu48Qvz302YFXB
2z4k8s/W6NQukrY1Aqaq+r/TFp/T9tEAl6NWhr2G/X8PtdfpbVf693VhWSqbD4Bo
EHNFfZdUENIRlrs/mvyBc0p/rGC8hE438tobB/vqPSWdkP71uohYJlf65ctI49bO
DrqJvBTVk6jSB3aAiNGHzRibBVQDAWfYYdjpxa0zZphu59F3MEBExKoaUUPZcpTM
4fYxZ0SZByzTnzVONRpJ8Q+Yf0zZnA1/gvbxl5UmbDlgsIqO7lH+BdfULLeO8SYu
pvXCThiaVCLTBf3/hIw1UBXw87JT65bHAvIzIPiGsT36gYwvTd8=
=sCej
-END PGP SIGNATURE End Message ---

Bug#912382: gresolver: Intent to remove from Debian

[Jeremy Bicha]

Source: gresolver
Version: 0.0.5-6
Severity: serious
Tags: buster sid
X-Debbugs-Cc: ba...@debian.org

gresolver was removed from Debian Testing 9 months ago because it
depends on libgnomeui which the Debian GNOME team is trying to remove
from Debian.

Therefore, I intend to file a removal bug for gresolver very soon.
Please let me know promptly if you agree or object.

See https://bugs.debian.org/885741

Thanks,
Jeremy Bicha

Processed: deferring gtksourceview2 removal until Bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -buster + bullseye + buster-ignore
Bug #911164 [gnome-genius] gnome-genius: Depends on unmaintained gtksourceview2
Removed tag(s) buster.
Bug #911164 [gnome-genius] gnome-genius: Depends on unmaintained gtksourceview2
Added tag(s) bullseye.
Bug #911164 [gnome-genius] gnome-genius: Depends on unmaintained gtksourceview2
Added tag(s) buster-ignore.
> retitle 911165 gtksourceview2: Do not release with Bullseye
Bug #911165 [debian-policy] gtksourceview2: Do not release with Bullseye
Ignoring request to change the title of bug#911165 to the same title

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

Processed: deferring gtksourceview2 removal until Bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -buster + bullseye + buster-ignore
Bug #911167 [src:gwyddion] gwyddion: Depend on gtksourceview2
Removed tag(s) buster.
Bug #911167 [src:gwyddion] gwyddion: Depend on gtksourceview2
Added tag(s) bullseye.
Bug #911167 [src:gwyddion] gwyddion: Depend on gtksourceview2
Added tag(s) buster-ignore.
> retitle 911165 gtksourceview2: Do not release with Bullseye
Bug #911165 [debian-policy] gtksourceview2: Do not release with Bullseye
Ignoring request to change the title of bug#911165 to the same title

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

Processed: deferring gtksourceview2 removal until Bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -buster + bullseye + buster-ignore
Bug #885681 [src:gummi] gummi: Depends on unmaintained gtksourceview2
Removed tag(s) buster.
Bug #885681 [src:gummi] gummi: Depends on unmaintained gtksourceview2
Added tag(s) bullseye.
Bug #885681 [src:gummi] gummi: Depends on unmaintained gtksourceview2
Added tag(s) buster-ignore.
> retitle 911165 gtksourceview2: Do not release with Bullseye
Bug #911165 [debian-policy] debian-policy: drop requirement to ship sysvinit 
init script with same name
Changed Bug title to 'gtksourceview2: Do not release with Bullseye' from 
'debian-policy: drop requirement to ship sysvinit init script with same name'.

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

Processed: deferring gtksourceview2 removal until Bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -buster + bullseye + buster-ignore
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Buster
Removed tag(s) buster.
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Buster
Added tag(s) bullseye.
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Buster
Added tag(s) buster-ignore.
> retitle 911165 gtksourceview2: Do not release with Bullseye
Bug #911165 [debian-policy] gtksourceview2: Do not release with Bullseye
Ignoring request to change the title of bug#911165 to the same title

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

Bug#885681: deferring gtksourceview2 removal until Bullseye

[Jeremy Bicha]

Control: tags -1 -buster + bullseye + buster-ignore
Control: retitle 911165 gtksourceview2: Do not release with Bullseye

Since the maintainers of at least genius and gwyddion are unhappy
about this happening for Buster, let's defer to Bullseye. Buster will
release around the middle of next year and we'll try to remove
gtksourceview2 from Bullseye soon after that.

Thanks,
Jeremy Bicha

Bug#911780: marked as done (psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 23:50:38 +
with message-id 
and subject line Bug#911780: fixed in psk31lx 2.2-1
has caused the Debian Bug report #911780,
regarding psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8
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.)


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

Hi,

lenny had the following binary package (from src:twpsk):

Package: psk31lx
Priority: optional
Section: hamradio
Installed-Size: 148
Maintainer: Joop Stakenborg 
Architecture: i386
Source: twpsk
Version: 2.1+2.2beta1-8
Depends: libc6 (>= 2.7-1), libgcc1 (>= 1:4.2.1), libncurses5 (>= 
5.6+20071006-3), libstdc++6 (>= 4.2.1)
Filename: pool/main/t/twpsk/psk31lx_2.1+2.2beta1-8_i386.deb
Size: 33248
MD5sum: a47956cf6af3d155f797ffc8b4a644b1
SHA1: 3ce698aa6974a1b4b049a7944d1a474e4e3c7b0c
SHA256: 173e0a76cbf0afcbb83f1c0ad4368b816c5acbc8dc459ecccf81a308dd62c674
Description: Soundcard-based ncurses program for operating PSK31
 Psk31lx uses a soundcard to receive and transmit PSK31, an extremely
 narrow band HF-mode. PSK31 is a mode for keyboard QSO's.


while stretch has this one with a lower version number (from src:psk31lx):

Package: psk31lx
Source: psk31lx (2.1-1)
Version: 2.1-1+b1
Installed-Size: 91
Maintainer: Debian Hamradio Maintainers 
Architecture: i386
Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.0), libncurses5 (>= 6), libpulse0 (>= 
0.99.1), libstdc++6 (>= 5), libtinfo5 (>= 6)
Description: PSK31 terminal application with text-based user interface
Homepage: http://wa0eir.bcts.info/psk31lx.html
Description-md5: 55820db20bf58c287b473c1e3b6c6ac7
Tag: hardware::hamradio, hardware::modem, implemented-in::c,
 interface::text-mode, role::program, scope::utility,
 uitoolkit::ncurses, use::chatting
Section: hamradio
Priority: optional
Filename: pool/main/p/psk31lx/psk31lx_2.1-1+b1_i386.deb
Size: 34248
MD5sum: 74882786eba9fdc15634323f36e617d1
SHA256: 8eeeaf4a951c62b424c16e8c76b97e873c2b2b92c8d7d00790c5b6f0cd7d472a


According to
http://snapshot.debian.org/binary/psk31lx/
there is quite a mess of version numbers.

Bumping the source package version to 2.1+really2.1-1 with no further
changes should fix this. This is preferred over adding an epoch.

$ dpkg --compare-versions 2.1+2.2beta1-8 lt 2.1+really2.1-1 && echo lt
lt


Andreas
--- End Message ---
--- Begin Message ---
Source: psk31lx
Source-Version: 2.2-1

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

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

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

Debian distribution maintenance software
pp.
Ervin Hegedus  (supplier of updated psk31lx 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, 29 Oct 2018 20:42:26 +
Source: psk31lx
Binary: psk31lx
Architecture: source
Version: 2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Ervin Hegedus 
Description:
 psk31lx- PSK31 terminal application with text-based user interface
Closes: 911780
Changes:
 psk31lx (2.2-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version (Closes: #911780)
   * Removed desktop-category.patch - upstream contains it
   * Removed man-hyphen.patch - upstream contains it
   * Removed new-fsf-address.patch - upstream contains it
   * Removed typo.patch - upstream contains it
   * Aligned no-double-changelog.patch to new upstream
   * Bump Standards-Version to 4.2.1
   * Removed trailing whitespaces from d/control, d/rules, d/copyright
   * Bump debhelper version to 11.0.0
   * Changed Debian copyright URL to https scheme
Checksums-Sha1:
 d453a4395c387d6e29237763bd68fa5c87f3807b 1795 psk31lx_2.2-1.dsc
 3d8510edc37edda4952ba27d6ea37145b7e7aa7e 158946 psk31lx_2.2.orig.tar.gz
 3999557563c8ad8bdce3d76e8f3a9709151fc8a8 3720 psk31lx_2.2-1.debian.tar.xz
 5a3c790a73977b40e7b58506f0af7dfa399379d0 5518 psk31lx_2.2-1_source.buildinfo
Checksums-Sha256:
 

Processed: Re: Bug#912370: xapian-bindings breaks xapers autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xapian-core
Bug #912370 [src:xapian-bindings, src:xapers] xapian-bindings breaks xapers 
autopkgtest
Bug reassigned from package 'src:xapian-bindings, src:xapers' to 'xapian-core'.
No longer marked as found in versions xapers/0.8.2-1 and 
xapian-bindings/1.4.8-1.
Ignoring request to alter fixed versions of bug #912370 to the same values 
previously set
> found -1 xapian-core/1.4.8-1
Bug #912370 [xapian-core] xapian-bindings breaks xapers autopkgtest
Marked as found in versions xapian-core/1.4.8-1.
> retitle -1 xapian-core: shlibs automatic update rule missing dependency
Bug #912370 [xapian-core] xapian-bindings breaks xapers autopkgtest
Changed Bug title to 'xapian-core: shlibs automatic update rule missing 
dependency' from 'xapian-bindings breaks xapers autopkgtest'.
> severity -1 serious
Bug #912370 [xapian-core] xapian-core: shlibs automatic update rule missing 
dependency
Severity set to 'serious' from 'normal'
> affects -1 xapian-bindings xapers
Bug #912370 [xapian-core] xapian-core: shlibs automatic update rule missing 
dependency
Added indication that 912370 affects xapian-bindings and xapers

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

Processed: severity of 912381 is normal

[Debian Bug Tracking System]

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

> severity 912381 normal
Bug #912381 [src:xen] xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing 
after upgrade from xen-utils-4.8
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8

[Dimitar Angelov]

Package: src:xen
Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
Severity: critical
Justification: breaks the whole system



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

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

Versions of packages xen-utils-4.11 depends on:
ii  libc6 2.27-6
ii  libncurses6   6.1+20181013-1
ii  libtinfo6 6.1+20181013-1
ii  libxenevtchn1 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxengnttab1 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxenmisc4.114.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxenstore3.04.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxentoolcore1   4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxentoollog14.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libyajl2  2.1.0-3
ii  python2.7.15-3
ii  xen-utils-common  4.11.1~pre.20180911.5acdd26fdc+dfsg-5

Versions of packages xen-utils-4.11 recommends:
ii  bridge-utils  1.5-16
ii  grub-xen-host 2.02+dfsg1-6
ii  qemu-system-x86   1:2.12+dfsg-3+b1
ii  xen-hypervisor-4.11-amd64 [xen-hyper  4.11.1~pre.20180911.5acdd26fdc+dfsg-5

Versions of packages xen-utils-4.11 suggests:
pn  ovmf
ii  qemu-utils  1:2.12+dfsg-3+b1
ii  seabios 1.11.1-1

-- no debconf information

Bug#911164: gnome-genius: Depends on unmaintained gtksourceview2

[Felipe Sateler]

On Tue, Oct 16, 2018 at 1:42 PM Jeremy Bicha  wrote:

> Package: gnome-genius
> Version: 1.0.24-2
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs gtksourceview2
> Tags: sid buster
>
> gnome-genius depends on gtksourceview2. The Debian GNOME team is
> trying to remove gtksourceview2 from Debian. Please port to gtk3 and
> gtksourceview4. Otherwise, I guess you can stop building gnome-genius.
>
> I apologize for not filing this bug sooner. I was only looking at
> packages in Testing and this package was removed from Testing earlier
> because of https://bugs.debian.org/790171 (which was fixed).
>
> Because of the late timing of this RC bug in the Buster cycle and
> because there might be a few other packages that won't be ported in
> time, please let me know if you object to gtksourceview2's removal
> from Buster.
>
>
While I sympathize with the desire to get rid of old libraries, I think
this bug comes too late. This bug should have been filed before stretch was
released if the target was buster.

I object to the serious severity, at least for this release cycle.


-- 

Saludos,
Felipe Sateler

Processed: severity of 697119 is important

[Debian Bug Tracking System]

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

> severity 697119 important
Bug #697119 [pulseaudio] pulseaudio: disable flat volumes
Bug #541538 [pulseaudio] pulseaudio: disable flat volumes
Bug #674935 [pulseaudio] pulseaudio: disable flat volumes
Bug #674936 [pulseaudio] pulseaudio: disable flat volumes
Bug #782730 [pulseaudio] pulseaudio: Noise when a short sound is played with 
another song playing
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#912296: marked as done (jboss-modules FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 22:20:53 +
with message-id 
and subject line Bug#912296: fixed in jboss-modules 1.8.6-2
has caused the Debian Bug report #912296,
regarding jboss-modules FTBFS with OpenJDK 11
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.)


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

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 4.708 s
[INFO] Finished at: 2019-12-01T14:56:10-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jboss-modules: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[37,19]
 cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[85,22]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[85,75]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[87,22]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[87,54]
 cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[120,20]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jboss-modules-1.8.6 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jboss-modules-1.8.6/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jboss-modules-1.8.6/debian 
-Dmaven.repo.local=/build/1st/jboss-modules-1.8.6/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Source: jboss-modules
Source-Version: 1.8.6-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated jboss-modules 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, 30 Oct 2018 22:46:04 +0100
Source: jboss-modules
Binary: libjboss-modules-java libjboss-modules-java-doc
Architecture: source
Version: 1.8.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 

Bug#910738: marked as done (mockito: FTBFS with Java 11: IllegalArgumentException invalid source release 1.11)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 21:52:33 +
with message-id 
and subject line Bug#910738: fixed in mockito 1.10.19-4
has caused the Debian Bug report #910738,
regarding mockito: FTBFS with Java 11: IllegalArgumentException invalid source 
release 1.11
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.)


-- 
910738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mockito
Version: 1.10.19-3
Severity: important
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java11

mockito builds with Java 9 and 10 but not with Java 11 (using Gradle 4.4.1).
The build stops on this exception:


java.lang.IllegalArgumentException: error: invalid source release: 1.11
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.error(Arguments.java:907)
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.doProcessArgs(Arguments.java:383)
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.processArgs(Arguments.java:347)
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.init(Arguments.java:246)
at 
jdk.compiler/com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:185)
at 
jdk.compiler/com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:119)
at 
jdk.compiler/com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:68)
at 
org.gradle.api.internal.tasks.compile.JdkJavaCompiler.createCompileTask(JdkJavaCompiler.java:66)
at 
org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:47)
at 
org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:35)
at 
org.gradle.api.internal.tasks.compile.ApiGroovyCompiler$2$1.compile(ApiGroovyCompiler.java:165)
at 
org.gradle.api.internal.tasks.compile.ApiGroovyCompiler.execute(ApiGroovyCompiler.java:175)
at 
org.gradle.api.internal.tasks.compile.ApiGroovyCompiler.execute(ApiGroovyCompiler.java:56)
at 
org.gradle.api.internal.tasks.compile.daemon.AbstractDaemonCompiler$CompilerRunnable.run(AbstractDaemonCompiler.java:87)
at 
org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:36)
at 
org.gradle.workers.internal.WorkerDaemonServer.execute(WorkerDaemonServer.java:46)
at 
org.gradle.workers.internal.WorkerDaemonServer.execute(WorkerDaemonServer.java:30)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 
org.gradle.process.internal.worker.request.WorkerAction.run(WorkerAction.java:100)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:146)
at 
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:128)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
... 3 more
--- End Message ---
--- Begin Message ---
Source: mockito
Source-Version: 1.10.19-4

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated mockito 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 

Processed: Re: Bug#912360: postgresql-client-11: depends on libedit2 is not installed correctly

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 911341
Bug #912360 [postgresql-client-11] postgresql-client-11: depends on libedit2 is 
not installed correctly
912360 was not blocked by any bugs.
912360 was not blocking any bugs.
Added blocking bug(s) of 912360: 911341

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

Bug#912380: endless looping, breaks dpkg

[Eduard Bloch]

Package: man-db
Version: 2.8.4-2+b1
Severity: serious
File: /usr/bin/mandb

Hello,

I am no longer able to install many packages. The man-db hook keeps
running and running for ages.

I have monitored it with strace and it seems to run over the same files
in man1 folder all over again, never ending. See the logs (also
filtered for open* syscalls):

https://www.unix-ag.uni-kl.de/~bloch/misc/wtf_mandb_dead_loop.txt.gz
https://www.unix-ag.uni-kl.de/~bloch/misc/wtf_mandb_dead_loop.strace.log

Best regards,
Eduard.

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

Kernel: Linux 4.19.0-rc8 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages man-db depends on:
ii  bsdmainutils   11.1.2+b1
ii  debconf [debconf-2.0]  1.5.69
ii  dpkg   1.19.2
ii  groff-base 1.22.3-10
ii  libc6  2.27-6
ii  libgdbm6   1.18-2
ii  libpipeline1   1.5.0-1
ii  libseccomp22.3.3-3
ii  zlib1g 1:1.2.11.dfsg-1

man-db recommends no packages.

Versions of packages man-db suggests:
ii  apparmor   2.13-8
ii  chromium [www-browser] 70.0.3538.54-2
ii  elinks [www-browser]   0.12~pre6-13
ii  firefox [www-browser]  62.0.3-1
ii  firefox-esr [www-browser]  60.2.2esr-1
ii  groff  1.22.3-10
ii  less   487-0.1+b1
ii  lynx [www-browser] 2.8.9rel.1-2
ii  qupzilla [www-browser] 2.2.5~dfsg1-1
ii  w3m [www-browser]  0.5.3-36+b1

-- debconf information:
  man-db/build-database: true
  man-db/rebuild-database: true
* man-db/install-setuid: true
  man-db/auto-update: true

-- 
Naja, Garbage Collector eben. Holt den Müll sogar vom Himmel.
   (Heise Trollforum über Java in der Flugzeugsteuerung)

Bug#911514: davmail: fails to install: wrong update-rc.d usage

[Geert Stappers]

On Tue, Oct 30, 2018 at 09:52:59AM +0100, Alexandre Rossi wrote:
> Hi Geert,
> 
> If you have some time to sponsor those uploads, please go on.

E_BUFFERFULL

Processed: affects 912167

[Debian Bug Tracking System]

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

> affects 912167 src:libpgplot-perl
Bug #912167 [src:giza] dpuser FTBFS on arm64: Segmentation fault
Added indication that 912167 affects src:libpgplot-perl
> thanks
Stopping processing here.

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

Processed: severity of 912324 is serious

[Debian Bug Tracking System]

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

> severity 912324 serious
Bug #912324 [bleachbit] BleachBit causing error since updating Firefox to 
Firefox Quantum 60.0 ESR
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#912378: libscout FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libscout
Version: 0.0~git20161124~dcd2a9e-1
Severity: serious
Tags: ftbfs

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

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> error: invalid source release: 1.11

Bug#912377: libxstream-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libxstream-java
Version: 1.4.10-1
Severity: serious
Tags: ftbfs

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 5.633 s
[INFO] Finished at: 2018-10-30T08:20:31-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project xstream: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[13,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[32,24]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[36,15]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[36,50]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[78,9]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[81,34]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[83,34]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] 
/build/1st/libxstream-java-1.4.10/xstream/src/java/com/thoughtworks/xstream/converters/extended/ActivationDataFlavorConverter.java:[85,34]
 cannot find symbol
[ERROR]   symbol:   class ActivationDataFlavor
[ERROR]   location: class 
com.thoughtworks.xstream.converters.extended.ActivationDataFlavorConverter
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :xstream
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/libxstream-java-1.4.10 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/libxstream-java-1.4.10/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/libxstream-java-1.4.10/debian 
-Dmaven.repo.local=/build/1st/libxstream-java-1.4.10/debian/maven-repo 
--batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned 
exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#912272: marked as done (staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .))

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 20:13:22 +
with message-id 
and subject line Bug#912272: fixed in staden-io-lib 1.14.11-1
has caused the Debian Bug report #912272,
regarding staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) 
"README" (tried in .)
to be marked as done.

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

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


-- 
912272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: staden-io-lib
Version: 1.14.9-4
Severity: serious
Tags: ftbfs

staden-io-lib fails to build from source in unstable. This smells a bit
like a debhelper regression, but I'm not sure actually. In any case, it
fails to build reliably.

|dh_installdocs -O--no-parallel
| dh_installdocs: Cannot find (any matches for) "README" (tried in .)
| 
| make: *** [debian/rules:11: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: staden-io-lib
Source-Version: 1.14.11-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated staden-io-lib 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, 29 Oct 2018 20:24:24 +0100
Source: staden-io-lib
Binary: staden-io-lib-utils libstaden-read-dev libstaden-read13 
staden-io-lib-examples
Architecture: source amd64 all
Version: 1.14.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libstaden-read-dev - development files for libstaden-read
 libstaden-read13 - Staden library for reading and writing DNA sequencing 
results
 staden-io-lib-examples - programs for manipulating DNA sequencing files (usage 
examples)
 staden-io-lib-utils - programs for manipulating DNA sequencing files
Closes: 912272
Changes:
 staden-io-lib (1.14.11-1) unstable; urgency=medium
 .
   * New upstream version featuring SOVERSION bump
   * Fix installation of docs
 Closes: #912272
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.2.1
Checksums-Sha1:
 ba5f2a4df290a9f2743bff410f8d1af0cfc95718 2429 staden-io-lib_1.14.11-1.dsc
 a5a8d9042544853d751888c4dbb7f85b2a8a4165 3391926 
staden-io-lib_1.14.11.orig.tar.gz
 aa401e034c8915ff9388b824f83f85d8fa3ae013 9876 
staden-io-lib_1.14.11-1.debian.tar.xz
 3d30e51ab423ebe7c4f9c16eec16e4505667bc0f 360380 
libstaden-read-dev_1.14.11-1_amd64.deb
 c5836d075c6b395c527c99f163402a958c5440ac 713224 
libstaden-read13-dbgsym_1.14.11-1_amd64.deb
 2dd085688a40e3f2b25ec93d85b9e87705e63877 279440 
libstaden-read13_1.14.11-1_amd64.deb
 ccb275998a1bf5e532fa5d16eb81aa466eda31a5 2749764 
staden-io-lib-examples_1.14.11-1_all.deb
 d471c9eb34933648a8247cd9f38a74b8bdaf6c42 403060 
staden-io-lib-utils-dbgsym_1.14.11-1_amd64.deb
 7dda1e0d0a36c3a84d9384a8480c823b36a25e47 165788 
staden-io-lib-utils_1.14.11-1_amd64.deb
 3cf58673421268c25a9ab428af198ee756c0fc36 8064 
staden-io-lib_1.14.11-1_amd64.buildinfo
Checksums-Sha256:
 171d8f760f10676d8a0b09cb49da3ffe299360a4da5c111e255b6cd397723058 2429 
staden-io-lib_1.14.11-1.dsc
 317aebf88f5b5d687e8165a68d2ed142f16dd5436fd530a24dbaa4acb5684051 3391926 
staden-io-lib_1.14.11.orig.tar.gz
 eb6a507be997c6262f14eaf909ff141b29feabafa95bdfb5d0fb40c761465e57 9876 
staden-io-lib_1.14.11-1.debian.tar.xz
 abadcb1dd118f853a918ceabaa99eb08a13026c2f9c8d44d57568a2ea3e7f80f 360380 
libstaden-read-dev_1.14.11-1_amd64.deb
 8205ab829e418defb2ac9f9b5fcf87b02591cd370a7aefe162022b1f9f893f68 713224 
libstaden-read13-dbgsym_1.14.11-1_amd64.deb
 aff67e5ad61062827b8b77e5eb0adb2dec9009cb2d531ad596f6ef8b2a34fe39 279440 
libstaden-read13_1.14.11-1_amd64.deb
 7bb3d57edf7e8f47e4799606266523cc5d8800f14bb8e9faa721f7fbcfdcc6cf 2749764 
staden-io-lib-examples_1.14.11-1_all.deb
 0428244b14ba4a6416ca604245fa6fee8521929cb5e6997ec4d3b3a1685c9003 403060 
staden-io-lib-utils-dbgsym_1.14.11-1_amd64.deb
 

Bug#893149: marked as done (ceph FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 20:11:56 +
with message-id 
and subject line Bug#893149: fixed in ceph 12.2.8+dfsg1-1
has caused the Debian Bug report #893149,
regarding ceph FTBFS with openjdk-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.)


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

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

...
Making all in java
make[4]: Entering directory '/build/1st/ceph-10.2.5/src/java'
export CLASSPATH=java/ ; \
javac -classpath java -source 1.5 -target 1.5 -Xlint:-options 
java/com/ceph/fs/*.java
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[4]: *** [Makefile:647: java/com/ceph/fs/CephMount.class] Error 2
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 12.2.8+dfsg1-1

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated ceph 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, 28 Oct 2018 23:43:10 +0100
Source: ceph
Binary: ceph ceph-base rbd-mirror rbd-nbd ceph-common ceph-mds ceph-mgr 
ceph-mon ceph-osd ceph-fuse rbd-fuse ceph-resource-agents librados2 
librados-dev libradosstriper1 libradosstriper-dev librbd1 librbd-dev libcephfs2 
libcephfs-dev librgw2 librgw-dev radosgw ceph-test python-ceph python3-ceph 
python-rados python3-rados python-rbd python3-rbd python-rgw python3-rgw 
python-cephfs python3-cephfs libcephfs-java libcephfs-jni rados-objclass-dev
Architecture: source amd64 all
Version: 12.2.8+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Maintainers 
Changed-By: Gaudenz Steinlin 
Description:
 ceph   - distributed storage and file system
 ceph-base  - common ceph daemon libraries and management tools
 ceph-common - common utilities to mount and interact with a ceph storage cluste
 ceph-fuse  - FUSE-based client for the Ceph distributed file system
 ceph-mds   - metadata server for the ceph distributed file system
 ceph-mgr   - Manager for the ceph distributed file system
 ceph-mon   - monitor server for the ceph storage system
 ceph-osd   - OSD server for the ceph storage system
 ceph-resource-agents - OCF-compliant resource agents for Ceph
 ceph-test  - Ceph test and benchmarking tools
 libcephfs-dev - Ceph distributed file system client library (development files)
 libcephfs-java - Java library for the Ceph File System
 libcephfs-jni - Java Native Interface library for CephFS Java bindings
 libcephfs2 - Ceph distributed file system client library
 librados-dev - RADOS distributed object store client library (development 
files)
 librados2  - RADOS distributed object store client library
 libradosstriper-dev - RADOS striping interface (development files)
 libradosstriper1 - RADOS striping interface
 librbd-dev - RADOS block device client library (development files)
 librbd1- RADOS block device client library
 librgw-dev - RADOS client library (development files)
 librgw2- RADOS Gateway client library
 python-ceph - Meta-package for Python modules for the Ceph libraries
 python-cephfs - Python libraries for the Ceph libcephfs library
 python-rados - Python libraries for the Ceph librados library
 python-rbd - Python libraries for the Ceph librbd library
 python-rgw - Python 2 libraries for the Ceph librgw library
 python3-ceph - Meta-package for Python 3 modules for the Ceph libraries
 python3-cephfs - Python 3 libraries for the Ceph libcephfs library
 python3-rados - Python 3 libraries for the Ceph librados library
 python3-rbd - Python 3 libraries for the Ceph librbd library
 python3-rgw - Python 3 libraries for the Ceph librgw library
 rados-objclass-dev - RADOS object class development kit.
 radosgw- REST gateway for RADOS distributed object store
 rbd-fuse   - 

Bug#896400: marked as done (python-cephfs: ceph_volume_client fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 20:12:03 +
with message-id 
and subject line Bug#896400: fixed in ceph 12.2.8+dfsg1-1
has caused the Debian Bug report #896400,
regarding python-cephfs: ceph_volume_client fails to import
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.)


-- 
896400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cephfs
Version: 10.2.5-7.2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-cephfs importing the module ceph_volume_client
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/ceph_volume_client.py", line 20, in 

from ceph_argparse import json_command
ImportError: No module named ceph_argparse

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 12.2.8+dfsg1-1

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated ceph 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, 28 Oct 2018 23:43:10 +0100
Source: ceph
Binary: ceph ceph-base rbd-mirror rbd-nbd ceph-common ceph-mds ceph-mgr 
ceph-mon ceph-osd ceph-fuse rbd-fuse ceph-resource-agents librados2 
librados-dev libradosstriper1 libradosstriper-dev librbd1 librbd-dev libcephfs2 
libcephfs-dev librgw2 librgw-dev radosgw ceph-test python-ceph python3-ceph 
python-rados python3-rados python-rbd python3-rbd python-rgw python3-rgw 
python-cephfs python3-cephfs libcephfs-java libcephfs-jni rados-objclass-dev
Architecture: source amd64 all
Version: 12.2.8+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Maintainers 
Changed-By: Gaudenz Steinlin 
Description:
 ceph   - distributed storage and file system
 ceph-base  - common ceph daemon libraries and management tools
 ceph-common - common utilities to mount and interact with a ceph storage cluste
 ceph-fuse  - FUSE-based client for the Ceph distributed file system
 ceph-mds   - metadata server for the ceph distributed file system
 ceph-mgr   - Manager for the ceph distributed file system
 ceph-mon   - monitor server for the ceph storage system
 ceph-osd   - OSD server for the ceph storage system
 ceph-resource-agents - OCF-compliant resource agents for Ceph
 ceph-test  - Ceph test and benchmarking tools
 libcephfs-dev - Ceph distributed file system client library (development files)
 libcephfs-java - Java library for the Ceph File System
 libcephfs-jni - Java Native Interface library for CephFS Java bindings
 libcephfs2 - Ceph distributed file system client library
 librados-dev - RADOS distributed object store client library (development 
files)
 librados2  - RADOS distributed object store client library
 libradosstriper-dev - RADOS striping interface (development files)
 libradosstriper1 - RADOS striping interface
 librbd-dev - RADOS block device client library (development files)
 librbd1- RADOS block device client library
 librgw-dev - RADOS client library (development files)
 librgw2- RADOS Gateway client library
 python-ceph - Meta-package for Python modules for the Ceph libraries
 python-cephfs - Python libraries for the Ceph libcephfs library
 python-rados - Python libraries for the Ceph librados library
 python-rbd - Python libraries for the Ceph librbd library
 python-rgw - Python 2 libraries for the Ceph librgw library
 python3-ceph - Meta-package for Python 3 modules for the Ceph libraries
 

Bug#867465: marked as done (ceph-base: purging ceph-base deletes /etc/ceph/rbdmap owned by ceph-common)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 20:11:38 +
with message-id 
and subject line Bug#867465: fixed in ceph 12.2.8+dfsg1-1
has caused the Debian Bug report #867465,
regarding ceph-base: purging ceph-base deletes /etc/ceph/rbdmap owned by 
ceph-common
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.)


-- 
867465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-base
Version: 10.2.5-7.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by another package.

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

0m44.1s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpmJEFX8', 
'dpkg', '--purge', 'ceph-base']
0m44.1s DUMP: 
  (Reading database ... 7176 files and directories currently installed.)
  Purging configuration files for ceph-base (10.2.5-7.2) ...
0m44.1s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpmJEFX8', 'dpkg', 
'--purge', 'ceph-base']
[...]
0m44.1s INFO: Validating chroot after purge
[...]
0m45.3s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/ceph/rbdmap (from ceph-common package)


cheers,

Andreas


ceph-base_10.2.5-7.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 12.2.8+dfsg1-1

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated ceph 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, 28 Oct 2018 23:43:10 +0100
Source: ceph
Binary: ceph ceph-base rbd-mirror rbd-nbd ceph-common ceph-mds ceph-mgr 
ceph-mon ceph-osd ceph-fuse rbd-fuse ceph-resource-agents librados2 
librados-dev libradosstriper1 libradosstriper-dev librbd1 librbd-dev libcephfs2 
libcephfs-dev librgw2 librgw-dev radosgw ceph-test python-ceph python3-ceph 
python-rados python3-rados python-rbd python3-rbd python-rgw python3-rgw 
python-cephfs python3-cephfs libcephfs-java libcephfs-jni rados-objclass-dev
Architecture: source amd64 all
Version: 12.2.8+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Maintainers 
Changed-By: Gaudenz Steinlin 
Description:
 ceph   - distributed storage and file system
 ceph-base  - common ceph daemon libraries and management tools
 ceph-common - common utilities to mount and interact with a ceph storage cluste
 ceph-fuse  - FUSE-based client for the Ceph distributed file system
 ceph-mds   - metadata server for the ceph distributed file system
 ceph-mgr   - Manager for the ceph distributed file system
 ceph-mon   - monitor server for the ceph storage system
 ceph-osd   - OSD server for the ceph storage system
 ceph-resource-agents - OCF-compliant resource agents for Ceph
 ceph-test  - Ceph test and benchmarking tools
 libcephfs-dev - Ceph distributed file system client library (development files)
 libcephfs-java - Java library for the Ceph File System
 libcephfs-jni - Java Native Interface library for CephFS Java bindings
 libcephfs2 - Ceph distributed file system client library
 librados-dev - RADOS distributed object store client library (development 
files)
 librados2  - RADOS distributed object store client library
 libradosstriper-dev - RADOS striping interface (development files)
 libradosstriper1 - RADOS striping interface
 librbd-dev - RADOS block device client library (development files)
 librbd1- RADOS block device client library
 librgw-dev - RADOS client library (development files)
 librgw2- RADOS Gateway client library
 python-ceph - Meta-package for Python modules for the Ceph libraries
 python-cephfs - Python libraries for the Ceph libcephfs library
 python-rados - Python libraries for the Ceph librados library
 python-rbd - Python libraries for the Ceph librbd library
 python-rgw - Python 2 libraries for the Ceph librgw library
 python3-ceph - Meta-package for Python 3 modules for the 

Bug#912373: libswingx1-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libswingx1-java
Version: 1:1.0-1
Severity: serious
Tags: ftbfs buster sid

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

...
compile:
[mkdir] Created dir: 
/build/1st/libswingx1-java-1.0/swingx-core/build/generated-sources
[javac] /usr/share/maven-ant-helper/maven-build.xml:357: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 396 source files to 
/build/1st/libswingx1-java-1.0/swingx-core/build/classes
[javac] 
/build/1st/libswingx1-java-1.0/src/java/org/jdesktop/swingx/error/ErrorSupport.java:71:
 error: reference to toArray is ambiguous
[javac] return listeners.toArray(null);
[javac] ^
[javac]   both method toArray(IntFunction) in Collection and 
method toArray(T#2[]) in List match
[javac]   where T#1,T#2 are type-variables:
[javac] T#1 extends Object declared in method 
toArray(IntFunction)
[javac] T#2 extends Object declared in method toArray(T#2[])
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error

BUILD FAILED
/build/1st/libswingx1-java-1.0/debian/build.xml:37: The following error 
occurred while executing this line:
/build/1st/libswingx1-java-1.0/debian/build.xml:21: The following error 
occurred while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:357: Compile failed; see the 
compiler error output for details.

Total time: 8 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1

Processed: tagging 912364

[Debian Bug Tracking System]

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

> tags 912364 + buster sid
Bug #912364 [el-get] el-get: not suitable for stable release
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#912372: libswingx-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libswingx-java
Version: 1:1.6.2-3
Severity: serious
Tags: ftbfs

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

...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/libswingx-java-1.6.2/swingx-core/src/main/java/org/jdesktop/swingx/error/ErrorSupport.java:[71,25]
 reference to toArray is ambiguous
  both method toArray(java.util.function.IntFunction) in 
java.util.Collection and method toArray(T[]) in java.util.List match

Bug#912295: marked as done (jboss-jdeparser2 FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 19:35:24 +
with message-id 
and subject line Bug#912295: fixed in jboss-jdeparser2 2.0.2-2
has caused the Debian Bug report #912295,
regarding jboss-jdeparser2 FTBFS with OpenJDK 11
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.)


-- 
912295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jboss-jdeparser2
Version: 2.0.2-1
Severity: serious
Tags: ftbfs buster sid

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3.884 s
[INFO] Finished at: 2018-10-29T07:13:06-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jdeparser: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jboss-jdeparser2-2.0.2/src/main/java/org/jboss/jdeparser/Assertions.java:[21,19]
 cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect
[ERROR] 
/build/1st/jboss-jdeparser2-2.0.2/src/main/java/org/jboss/jdeparser/Assertions.java:[29,20]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.jdeparser.Assertions
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jboss-jdeparser2-2.0.2 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jboss-jdeparser2-2.0.2/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jboss-jdeparser2-2.0.2/debian 
-Dmaven.repo.local=/build/1st/jboss-jdeparser2-2.0.2/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Source: jboss-jdeparser2
Source-Version: 2.0.2-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated jboss-jdeparser2 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, 30 Oct 2018 19:57:40 +0100
Source: jboss-jdeparser2
Binary: libjboss-jdeparser2-java libjboss-jdeparser2-java-doc
Architecture: source
Version: 2.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libjboss-jdeparser2-java - Java source code generating library
 libjboss-jdeparser2-java-doc - Documentation for libjboss-jdeparser2-java
Closes: 912295
Changes:
 jboss-jdeparser2 (2.0.2-2) unstable; urgency=medium
 .
   * Fix FTBFS with Java 11. (Closes: #912295)
Checksums-Sha1:
 a185d53cc374d7148c211f35ea763ee957622425 2359 jboss-jdeparser2_2.0.2-2.dsc
 ba3218b7ead11696e8559f62c6ebb097adba07e2 3552 
jboss-jdeparser2_2.0.2-2.debian.tar.xz
 cb8737b671e141cd2bde9e88cea6d161ea4bdf78 15074 
jboss-jdeparser2_2.0.2-2_amd64.buildinfo
Checksums-Sha256:
 9d165658455bdc0b997484842cb7446df41a9ba8154c2a1acc61f7ae8391b0ef 2359 
jboss-jdeparser2_2.0.2-2.dsc
 83b8c075b679c732e7cc38b82482cdb46df594bf84c14826bbabf71c5ce984bb 3552 
jboss-jdeparser2_2.0.2-2.debian.tar.xz
 

Bug#899616: marked as done (myspell-fa: Invalid maintainer address debian-arabic-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 19:09:43 +
with message-id 
and subject line Bug#899616: fixed in myspell-fa 0.20070816-3.1
has caused the Debian Bug report #899616,
regarding myspell-fa: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:myspell-fa
Version: 0.20070816-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of myspell-fa,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package myspell-fa since the list address
debian-arabic-packa...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-arabic-packa...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: myspell-fa
Source-Version: 0.20070816-3.1

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated myspell-fa 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, 30 Oct 2018 18:33:51 +
Source: myspell-fa
Binary: myspell-fa
Architecture: source
Version: 0.20070816-3.1
Distribution: unstable
Urgency: medium
Maintainer: Lior Kaplan 
Changed-By: intrigeri 
Description:
 myspell-fa - Persian (Farsi) dictionary for myspell
Closes: 899616
Changes:
 myspell-fa (0.20070816-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Set the Maintainer control field to the person listed in the Uploaders
 field who did most of the recent uploads: the team mailing list
 is deprecated (Closes: #899616).
Checksums-Sha1:
 e58320e9b52c261be3fb1c51733278284c8520b0 1880 myspell-fa_0.20070816-3.1.dsc
 5c40ff4ce89ae5fb6786a3623216627f5290ae6a 2520 
myspell-fa_0.20070816-3.1.debian.tar.xz
 f35cf231da7d1f399e78325bf8f7104d2900d020 6078 
myspell-fa_0.20070816-3.1_amd64.buildinfo
Checksums-Sha256:
 3aaefa5d1feec327a2585dd49e9dfdbc29da0bafd5303a26aa5ea6ad45ca 1880 
myspell-fa_0.20070816-3.1.dsc
 89edc5069ad71a75931f966bb975a63b626b9d65d9aca59065f48986ae798232 2520 
myspell-fa_0.20070816-3.1.debian.tar.xz
 a3dfb44ccdc4b101c7e9c8f6d3e6c5664b29c272303c0d8526f31636880ae7fb 6078 
myspell-fa_0.20070816-3.1_amd64.buildinfo
Files:
 29194b191b57621f4b1fe81630fc2a13 

Bug#899539: marked as done (hunspell-ar: Invalid maintainer address debian-arabic-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 19:07:50 +
with message-id 
and subject line Bug#899539: fixed in hunspell-ar 3.2-1.1
has caused the Debian Bug report #899539,
regarding hunspell-ar: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hunspell-ar
Version: 3.2-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of hunspell-ar,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package hunspell-ar since the list address
debian-arabic-packa...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-arabic-packa...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: hunspell-ar
Source-Version: 3.2-1.1

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated hunspell-ar 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, 30 Oct 2018 18:31:07 +
Source: hunspell-ar
Binary: hunspell-ar
Architecture: source
Version: 3.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Lior Kaplan 
Changed-By: intrigeri 
Description:
 hunspell-ar - Arabic dictionary for hunspell
Closes: 899539
Changes:
 hunspell-ar (3.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Set the Maintainer control field to the person listed in the Uploaders
 field who did most of the recent uploads: the team mailing list
 is deprecated (Closes: #899539).
Checksums-Sha1:
 fb5df7fa3af418cfb5b14bc650e5f8d936b11e6b 1832 hunspell-ar_3.2-1.1.dsc
 d5450cebe86a8193501bc363538a015fd0590d80 3420 hunspell-ar_3.2-1.1.debian.tar.xz
 1800a726ef117a2d818fe16c51d80fa4b7c2f520 6032 
hunspell-ar_3.2-1.1_amd64.buildinfo
Checksums-Sha256:
 50bb26fc740e3da2c3c8e05d5a1034f93fc14543cd32bfcef9e930d9138096d7 1832 
hunspell-ar_3.2-1.1.dsc
 0f38b2d0f3c4d485ae772dad3149ed40c07fec8b35a02bb4839258c1e386657f 3420 
hunspell-ar_3.2-1.1.debian.tar.xz
 a8a961232da1234b9e14d5aa0855547a4177d76b92870eccd46e62091a4bed1e 6032 
hunspell-ar_3.2-1.1_amd64.buildinfo
Files:
 c60dc11a0cf5f39d8a8d4d528f303b3a 1832 text optional hunspell-ar_3.2-1.1.dsc
 

Bug#912295: Bug #912295 in jboss-jdeparser2 marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/jboss-jdeparser2/commit/a1a48ba8146777bed0c65c6f76a6157500b5f093


Fix FTBFS with Java 11.

Closes: #912295



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912295

Processed: Bug #912295 in jboss-jdeparser2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912295 [src:jboss-jdeparser2] jboss-jdeparser2 FTBFS with OpenJDK 11
Added tag(s) pending.

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

Bug#899958: Getting ibus-anthy and ibus-pinyin back into testing

[intrigeri]

Osamu Aoki:
> On Sat, Jun 30, 2018 at 12:06:18PM +0200, intrigeri wrote:
>> Hi,
>> 
>> do you plan to fix #899958 and #899538 soon? I could not find updates
>> nor any Git repo on Salsa.

Thanks for fixing these! Glad to see these two packages back in
testing :)

Processed: myspell-fa: diff for NMU version 0.20070816-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 899616 + patch
Bug #899616 [src:myspell-fa] myspell-fa: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) patch.
> tags 899616 + pending
Bug #899616 [src:myspell-fa] myspell-fa: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#899616: myspell-fa: diff for NMU version 0.20070816-3.1

[intrigeri]

Control: tags 899616 + patch
Control: tags 899616 + pending

Dear maintainer,

I've prepared an NMU for myspell-fa (versioned as 0.20070816-3.1) and
uploaded it to sid.

Cheers!

diff -Nru myspell-fa-0.20070816/debian/changelog 
myspell-fa-0.20070816/debian/changelog
--- myspell-fa-0.20070816/debian/changelog  2011-06-09 19:07:50.0 
+0200
+++ myspell-fa-0.20070816/debian/changelog  2018-10-30 19:33:51.0 
+0100
@@ -1,3 +1,12 @@
+myspell-fa (0.20070816-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Set the Maintainer control field to the person listed in the Uploaders
+field who did most of the recent uploads: the team mailing list
+is deprecated (Closes: #899616).
+
+ -- intrigeri   Tue, 30 Oct 2018 18:33:51 +
+
 myspell-fa (0.20070816-3) unstable; urgency=low
 
   * Switch to dpkg-source 3.0 (quilt) format
diff -Nru myspell-fa-0.20070816/debian/control 
myspell-fa-0.20070816/debian/control
--- myspell-fa-0.20070816/debian/control2011-06-09 18:47:14.0 
+0200
+++ myspell-fa-0.20070816/debian/control2018-10-30 19:33:32.0 
+0100
@@ -1,8 +1,8 @@
 Source: myspell-fa
 Section: text
 Priority: optional
-Maintainer: Debian Arabic Packaging Team 

-Uploaders: Alan Baghumian , Lior Kaplan 
+Maintainer: Lior Kaplan 
+Uploaders: Alan Baghumian 
 Build-Depends: debhelper (>> 5.0.0)
 Build-Depends-Indep: dictionaries-common-dev
 Standards-Version: 3.9.2

Bug#899539: hunspell-ar: diff for NMU version 3.2-1.1

[intrigeri]

Control: tags 899539 + patch
Control: tags 899539 + pending

Dear maintainer,

I've prepared an NMU for hunspell-ar (versioned as 3.2-1.1) and
uploaded it to sid.

Cheers!

diff -Nru hunspell-ar-3.2/debian/changelog hunspell-ar-3.2/debian/changelog
--- hunspell-ar-3.2/debian/changelog2012-08-10 16:36:01.0 +0200
+++ hunspell-ar-3.2/debian/changelog2018-10-30 19:31:07.0 +0100
@@ -1,3 +1,12 @@
+hunspell-ar (3.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Set the Maintainer control field to the person listed in the Uploaders
+field who did most of the recent uploads: the team mailing list
+is deprecated (Closes: #899539).
+
+ -- intrigeri   Tue, 30 Oct 2018 18:31:07 +
+
 hunspell-ar (3.2-1) unstable; urgency=low
 
   * New upstream release
diff -Nru hunspell-ar-3.2/debian/control hunspell-ar-3.2/debian/control
--- hunspell-ar-3.2/debian/control  2012-08-10 16:34:11.0 +0200
+++ hunspell-ar-3.2/debian/control  2018-10-30 19:30:57.0 +0100
@@ -1,8 +1,8 @@
 Source: hunspell-ar
 Section: text
 Priority: optional
-Maintainer: Debian Arabic Packaging Team 

-Uploaders: Mohammed Sameer , Lior Kaplan 

+Maintainer: Lior Kaplan 
+Uploaders: Mohammed Sameer 
 Standards-Version: 3.9.3
 Build-Depends: debhelper (>> 5.0.0)
 Build-Depends-Indep: dictionaries-common-dev (>= 0.49.2)

Processed: hunspell-ar: diff for NMU version 3.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 899539 + patch
Bug #899539 [src:hunspell-ar] hunspell-ar: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) patch.
> tags 899539 + pending
Bug #899539 [src:hunspell-ar] hunspell-ar: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#912364: el-get: not suitable for stable release

[David Bremner]

Package: el-get
Version: 3.1-1.1
Severity: serious
Justification: contains severely out of date metadata

I think we're not doing users of Debian any favours by shipping emacs
package metadata that was last updated in 2011.  For this reason I
don't think the package is suitable for Buster in it's current state.
Of course I might be wrong, in which case please feel free to close
the bug with an explanation.


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

Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages el-get depends on:
ii  emacs  46.1
ii  emacs24 [emacsen]  24.5+1-11+deb9u1
ii  emacs25 [emacsen]  25.1+1-4+deb9u1

el-get recommends no packages.

el-get suggests no packages.

Processed: Re: Bug#911632: found 911632 in 2.7.4+reloaded3-6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #911632 [gosa] gosa: fails to install: PHP Fatal error: Uncaught Error: 
Call to undefined function imageCreateFromPng
Severity set to 'important' from 'serious'

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

Bug#911632: found 911632 in 2.7.4+reloaded3-6

[Mike Gabriel]

Control: severity -1 important

Hi Holger,

On  Di 30 Okt 2018 14:28:37 CET, Holger Levsen wrote:


control: reopen -1

On Tue, Oct 30, 2018 at 01:16:18PM +0100, Wolfgang Schweer wrote:
> The build log previously attached to this bug has a 95% ready  
php7.3 stack,
> while php-gd still pulled in php7.2-gd. So, from update-gosa's  
perspective,

> php-gd was missing (because there was no such php7.3-gd package).

php-gd in testing is still version 1:7.2+62 depending on php7.2-gd, so
this might be the problem, regardless that  php7.3-gd (7.3.0~rc2-2)
is already in buster.

> I will close this bug now, it should be gone if you retest today (as
> php7.3-gd has landed in testing/unstable meanwhile and php-gd from
> php-defaults pulls in the correct packages).

It still fails due to the reason above, I guess.


https://jenkins.debian.net/job/chroot-installation_stretch_install_education-main-server_upgrade_to_buster/36/console
also confirmed this bug is still there today, thus reopening.


I reduce severity then. The gosa package itself is not causing this issue.

Please close this bug again, once the jenkins tests work again.

Mike
--

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

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



pgpW5TdVHqK3O.pgp
Description: Digitale PGP-Signatur

Bug#912363: orthanc-imagej FTBFS with OpenJDK 11

[Adrian Bunk]

Source: orthanc-imagej
Version: 1.1+dfsg-3
Severity: serious
Tags: ftbfs

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

...
cd /build/1st/orthanc-imagej-1.1+dfsg && /usr/bin/javac -source 1.6 -target 1.6 
-classpath 
:/usr/share/java/ij.jar:/usr/share/java/json-simple.jar:/build/1st/orthanc-imagej-1.1+dfsg:/build/1st/orthanc-imagej-1.1+dfsg/Build
 -d /build/1st/orthanc-imagej-1.1+dfsg/Build/CMakeFiles/Orthanc_Import.dir 
@/build/1st/orthanc-imagej-1.1+dfsg/Build/CMakeFiles/Orthanc_Import.dir/java_sources
warning: [options] bootstrap class path not set in conjunction with -source 6
warning: [options] source value 6 is obsolete and will be removed in a future 
release
warning: [options] target value 1.6 is obsolete and will be removed in a future 
release
warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/OrthancConnection.java:32: 
error: package javax.xml.bind does not exist
import javax.xml.bind.DatatypeConverter;
 ^
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/SelectImageDialog.java:52: 
error: package javax.xml.bind does not exist
import javax.xml.bind.DatatypeConverter;
 ^
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/OrthancConnection.java:100:
 error: cannot find symbol
return DatatypeConverter.printBase64Binary(auth.getBytes());
   ^
  symbol:   variable DatatypeConverter
  location: class OrthancConnection
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/SelectImageDialog.java:555:
 error: cannot find symbol
  String decoded = new String(DatatypeConverter.parseBase64Binary(s));
  ^
  symbol:   variable DatatypeConverter
  location: class SelectImageDialog
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/SelectImageDialog.java:578:
 error: cannot find symbol
return DatatypeConverter.printBase64Binary(config.getBytes());
   ^
  symbol:   variable DatatypeConverter
  location: class SelectImageDialog
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 errors
4 warnings
make[3]: *** [CMakeFiles/Orthanc_Import.dir/build.make:79: 
CMakeFiles/Orthanc_Import.dir/java_compiled_Orthanc_Import] Error 1

Bug#912350: marked as done (mediathekview FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 17:36:27 +
with message-id 
and subject line Bug#912350: fixed in mediathekview 13.0.6-3
has caused the Debian Bug report #912350,
regarding mediathekview FTBFS with OpenJDK 11
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.)


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

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

...
/build/1st/mediathekview-13.0.6/src/main/java/mediathek/tool/MVTable.java:29: 
error: package javax.activation does not exist
import javax.activation.DataHandler;
   ^
...
/build/1st/mediathekview-13.0.6/src/main/java/mediathek/tool/MVTable.java:880: 
error: cannot find symbol
return new DataHandler(table.getSelectedRow(), 
localObjectFlavor.getMimeType());
   ^
  symbol:   class DataHandler
  location: class MVTable.TableRowTransferHandlerDownload
...
--- End Message ---
--- Begin Message ---
Source: mediathekview
Source-Version: 13.0.6-3

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated mediathekview 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, 30 Oct 2018 17:52:52 +0100
Source: mediathekview
Binary: mediathekview
Architecture: source
Version: 13.0.6-3
Distribution: unstable
Urgency: medium
Maintainer: Markus Koschany 
Changed-By: Markus Koschany 
Description:
 mediathekview - view streams from German public television stations
Closes: 912350
Changes:
 mediathekview (13.0.6-3) unstable; urgency=medium
 .
   * Fix FTBFS with OpenJDK 11.
 - B-D on libactivation-java.
 - Add /usr/share/java/javax.activation.jar to CLASSPATH.
 - Update build.patch and use javax.activation.
 (Closes: #912350)
Checksums-Sha1:
 bc99871558e8bd9440af8817ffb74a454830ea45 2396 mediathekview_13.0.6-3.dsc
 e857140d7206a53437b220e28cc0114f32f88511 17528 
mediathekview_13.0.6-3.debian.tar.xz
 969614e7a38e02b24cdaad6465fe1e0a76ae03a8 18196 
mediathekview_13.0.6-3_amd64.buildinfo
Checksums-Sha256:
 64abca649cf4cfad2cdf4bbfc86a806715115680f5c46c7df8e53c9021207738 2396 
mediathekview_13.0.6-3.dsc
 0d7f16110e0f2039bef1837243d35de13ceabc4665a438944d49f57c07a38ec0 17528 
mediathekview_13.0.6-3.debian.tar.xz
 cbae953d556e431eb7ed4372c50086ab2dca55aa1e2b3c6d01f401b11ded1261 18196 
mediathekview_13.0.6-3_amd64.buildinfo
Files:
 ebd4715eb3ba35a2329f8e3aebbe743d 2396 video optional mediathekview_13.0.6-3.dsc
 43f5de1835f56ecbcf027a687eee8501 17528 video optional 
mediathekview_13.0.6-3.debian.tar.xz
 2d4e4893799a2894dd9508ee4aa2f0aa 18196 video optional 
mediathekview_13.0.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlvYjXBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkPrQP/3Lj3P/Og30Z76QuZFE+bYfpuSxGa5jmHtQC
3JLo9WO5XQ1eg9MIpU8s8VvCyqF6n8/7IfaWVqzTDPM2IjVg1P6q5HkqRVsZGz5c
YNLz0QTvGCdVv7dZk58txmndS8ph+nLemSgzAORUsVlS51hIFiCh9bQije8XU2Ov
r6ckHUtLkm/3ZKNH4YlUXpd/QGeD2bR/9IM5xLxQvWzXrAsZeF4fE5hjTayGTxkN
tl6n/t7QLB8g5J09zzMqK/Ics15+Qk59lB1IvsHss7MIyyKIYduGdsQwaRtmTmm1
iC3GWzSbg+AtGuVnciEZpOxpKxVMlUSxQcwJgtKvbzuk7Q3xexdDjZuRa/9gL/4Z
gJ1KchsyB3KKh05F+N/cizKGEW4IfvEUKg+8hiIZaIIIWedHNqqHBC/cc5KiwkYV
ZaBf8LFvF7QEFI69fjrJlb+2iEw1WGoid8KS7QnHpFuSz5ejUVsd4HBkflEGTTKj
N1m2oMRJdzleMD21tfMUVNUP6LZF43f2dtAPy35s6CKS7wRRE05U+yKoURRAJ3FW
qYS4tXQC0qtqUTTifFywM9OkHTfEV5RYBaCZ0R5W2HsWbIHla1nTaDESIp8zdBxr
Qr6PfTuPiSR5E16n10NEZ/V9NYjRAv6qkZar4KzEpl4todT7MXN2GmsxihAQm/5S
mQHlei4Z
=/hcH
-END PGP SIGNATURE End Message ---

Bug#906837: xul-ext-ublock-origin no longer works with firefox-esr 60

[Markus Koschany]

Am 30.10.18 um 18:25 schrieb Thierry:
> Adrian Bunk  wrote:
> 
>> Package: xul-ext-ublock-origin
>> Version: 1.10.4+dfsg-1
>> Severity: serious
>> Control: fixed -1 1.16.6+dfsg-1
>> Control: close -1
>>
>> XUL addons are no longer supported.
>>
>> This is already fixed in unstable.
> 
> OK, but what is the plan for stable ?
> 
> Best regards,
> Thierry

This was already fixed in stable. You can install the web extension of
ublock origin via stable-proposed-updates or you have to wait until the
next point update.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: fixed 911565 in 1.4.6-3

[Debian Bug Tracking System]

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

> fixed 911565 1.4.6-3
Bug #911565 {Done: Nicolas Mora } [glewlwyd] glewlwyd: 
fails to install, purge, and install again
Marked as fixed in versions glewlwyd/1.4.6-3.
> thanks
Stopping processing here.

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