Bug#966766: marked as done (ola: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Nov 2020 07:49:54 +
with message-id 
and subject line Bug#937186: fixed in ola 0.10.8.nojsmin-1
has caused the Debian Bug report #937186,
regarding ola: Unversioned Python removal in sid/bullseye
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.)


-- 
937186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ola
Version: 0.10.7.nojsmin-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: ola
Source-Version: 0.10.8.nojsmin-1
Done: Wouter Verhelst 

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated ola 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, 23 Nov 2020 09:33:39 +0200
Source: ola
Architecture: source
Version: 0.10.8.nojsmin-1
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Closes: 925793 937186 944927
Changes:
 ola (0.10.8.nojsmin-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes FTBFS with recent protobuf; Closes: #944927
 - Fixes FTBFS with recent gcc; Closes: #925793
   * ola-python: switch to python3, from python2. Closes:
 #937186.
   * ola-rdm-tests: don't build, not yet supported under python3.
 Functionality is not crucial, so disable it for now.
   * Bump debhelper compat level to 12
Checksums-Sha1:
 113ca7067f085b771a50ed17e6ea5bfa6799404e 2450 ola_0.10.8.nojsmin-1.dsc
 fda16045926d58878d580d3f6c760509c4c585dc 2403031 ola_0.10.8.nojsmin.orig.tar.gz
 ee601d8f54cc4f69f0a7430832cf322edb8a0913 31560 
ola_0.10.8.nojsmin-1.debian.tar.xz
 fbfc44b6dc6fba1d109deaafbc85398ef412fdc1 8876 
ola_0.10.8.nojsmin-1_source.buildinfo
Checksums-Sha256:
 773277f2d297646d7837e7dfd93c9f061922f78b12b949cba0256b22e3b620cd 2450 
ola_0.10.8.nojsmin-1.dsc
 2a7f68a5fb8405c740e100651a7f20890852458fe8c668bead75287e1c098379 2403031 
ola_0.10.8.nojsmin.orig.tar.gz
 934e23bc2968bf4d1ccde7ae38ab7d0c49f85878c45297c98e2d78389ccdf93d 31560 
ola_0.10.8.nojsmin-1.debian.tar.xz
 daf47afd9e7374967ddd21563a469984fff23ec267b6fd6a7f5316e174d3abba 8876 
ola_0.10.8.nojsmin-1_source.buildinfo
Files:
 856ce0c94d88483f830919ccca39e859 2450 libs optional ola_0.10.8.nojsmin-1.dsc
 e0b9d6376f3ee1d364314b88f7951329 2403031 libs optional 
ola_0.10.8.nojsmin.orig.tar.gz
 c537043543d3ce322ba2f48d86412687 31560 libs optional 
ola_0.10.8.nojsmin-1.debian.tar.xz
 11b95d54b1805e0a95f41d3be962b911 8876 libs optional 
ola_0.10.8.nojsmin-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEm2n98/DaCUgGYSn3LfxRmVQYEpYFAl+7ZqwSHHdvdXRlckBk
ZWJpYW4ub3JnAAoJEC38UZlUGBKWftEP/A69YQEKU8oWPL42SorCLqCHQEHKxuog
Zt/FzWzZhhxre8BnIJ+C3bNTGRWKo1EAKyBDRKZVLi+5IWEJ+b9f8WERtTdCB7bc
chBtOFN3fJsvlhUeR3YzqTnP5P/vKQHSGQ8OA6S1tixU4wC0Npt8KA2yDTIH6e+K
TJqII2W8lfQiyE7QOC8Iy/UMoeNVp1Z9JBpUcGhuUSH9p9Hjo8kicHoi55dyvmoU

Bug#937186: marked as done (ola: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Nov 2020 07:49:54 +
with message-id 
and subject line Bug#937186: fixed in ola 0.10.8.nojsmin-1
has caused the Debian Bug report #937186,
regarding ola: Python2 removal in sid/bullseye
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.)


-- 
937186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ola
Version: 0.10.7.nojsmin-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:ola

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: ola
Source-Version: 0.10.8.nojsmin-1
Done: Wouter Verhelst 

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated ola 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, 23 Nov 2020 09:33:39 +0200
Source: ola
Architecture: source
Version: 0.10.8.nojsmin-1
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Closes: 925793 937186 944927
Changes:
 ola (0.10.8.nojsmin-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes FTBFS with recent protobuf; Closes: #944927
 - Fixes FTBFS with recent gcc; Closes: #925793
   * ola-python: switch to python3, from python2. Closes:
 #937186.
   * ola-rdm-tests: don't build, not yet supported under python3.
 Functionality is not crucial, so disable it for now.
   * Bump debhelper compat level to 12
Checksums-Sha1:
 113ca7067f085b771a50ed17e6ea5bfa6799404e 2450 ola_0.10.8.nojsmin-1.dsc
 fda16045926d58878d580d3f6c760509c4c585dc 2403031 ola_0.10.8.nojsmin.orig.tar.gz
 ee601d8f54cc4f69f0a7430832cf322edb8a0913 31560 
ola_0.10.8.nojsmin-1.debian.tar.xz
 fbfc44b6dc6fba1d109deaafbc85398ef412fdc1 8876 

Bug#925793: marked as done (ola: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 23 Nov 2020 07:49:54 +
with message-id 
and subject line Bug#925793: fixed in ola 0.10.8.nojsmin-1
has caused the Debian Bug report #925793,
regarding ola: ftbfs with GCC-9
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
  |   ^~~~
In file included from /usr/include/c++/9/memory:80,
 from /usr/include/cppunit/extensions/HelperMacros.h:16,
 from common/web/SchemaTest.cpp:21:
/usr/include/c++/9/bits/unique_ptr.h:53:28: note: declared here
   53 |   template class auto_ptr;
  |^~~~
g++ -DHAVE_CONFIG_H -I.  -I./include -I./include -Wall -Wformat -W 
-fvisibility-inlines-hidden -pthread  -DTEST_SRC_DIR=\".\" 
-DTEST_BUILD_DIR=\".\" -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -I./include 
-I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread -Werror 
-Wno-error=deprecated-declarations -Wno-error=unused-parameter -std=gnu++11 
-Wno-error=deprecated-declarations -pthread -c -o 
libs/acn/E131Tester-DMPAddressTest.o `test -f 'libs/acn/DMPAddressTest.cpp' || 
echo './'`libs/acn/DMPAddressTest.cpp
g++ -DHAVE_CONFIG_H -I.  -I./include -I./include -Wall -Wformat -W 
-fvisibility-inlines-hidden -pthread  -DTEST_SRC_DIR=\".\" 
-DTEST_BUILD_DIR=\".\" -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -I./include 
-I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread -Werror 
-Wno-error=deprecated-declarations -Wno-error=unused-parameter -std=gnu++11 
-Wno-error=deprecated-declarations -pthread -c -o 
libs/acn/E131Tester-DMPInflatorTest.o `test -f 'libs/acn/DMPInflatorTest.cpp' 
|| echo './'`libs/acn/DMPInflatorTest.cpp
g++ -DHAVE_CONFIG_H -I.  -I./include -I./include -Wall -Wformat -W 
-fvisibility-inlines-hidden -pthread  -DTEST_SRC_DIR=\".\" 
-DTEST_BUILD_DIR=\".\" -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -I./include 
-I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread -Werror 
-Wno-error=deprecated-declarations -Wno-error=unused-parameter -std=gnu++11 
-Wno-error=deprecated-declarations -pthread -c -o 
libs/acn/E131Tester-DMPPDUTest.o `test -f 'libs/acn/DMPPDUTest.cpp' || echo 
'./'`libs/acn/DMPPDUTest.cpp
g++ -DHAVE_CONFIG_H -I.  -I./include -I./include -Wall -Wformat -W 
-fvisibility-inlines-hidden -pthread  -DTEST_SRC_DIR=\".\" 
-DTEST_BUILD_DIR=\".\" -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -I./include 
-I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread -Werror 
-Wno-error=deprecated-declarations -Wno-error=unused-parameter -std=gnu++11 
-Wno-error=deprecated-declarations -pthread -c -o 
libs/acn/E131Tester-E131InflatorTest.o `test -f 'libs/acn/E131InflatorTest.cpp' 
|| echo './'`libs/acn/E131InflatorTest.cpp
g++ -DHAVE_CONFIG_H -I.  -I./include -I./include -Wall -Wformat -W 
-fvisibility-inlines-hidden -pthread  -DTEST_SRC_DIR=\".\" 
-DTEST_BUILD_DIR=\".\" -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -I./include 
-I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread 

Processed: Re: merge ftbfs bugs

[Debian Bug Tracking System]

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

> reassign 975512 src:ruby-kubeclient
Bug #975512 [ruby-kubelcient] ruby-kubeclient: ftbfs with Passing 
permitted_classes with the 2nd argument of Psych.safe_load is deprecated
Warning: Unknown package 'ruby-kubelcient'
Bug reassigned from package 'ruby-kubelcient' to 'src:ruby-kubeclient'.
No longer marked as found in versions 4.6.0-1.
Ignoring request to alter fixed versions of bug #975512 to the same values 
previously set
> forcemerge 975512 975176
Bug #975512 [src:ruby-kubeclient] ruby-kubeclient: ftbfs with Passing 
permitted_classes with the 2nd argument of Psych.safe_load is deprecated
Bug #975176 [src:ruby-kubeclient] ruby-kubeclient: FTBFS: ERROR: Test "ruby2.7" 
failed.
Set Bug forwarded-to-address to 
'https://github.com/abonas/kubeclient/issues/483'.
Bug #975512 [src:ruby-kubeclient] ruby-kubeclient: ftbfs with Passing 
permitted_classes with the 2nd argument of Psych.safe_load is deprecated
Marked as found in versions ruby-kubeclient/4.6.0-1.
Added tag(s) sid, bullseye, and ftbfs.
Merged 975176 975512
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: merge ftbfs bugs

[Debian Bug Tracking System]

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

> forcemerge 975512 975176
Bug #975512 [ruby-kubelcient] ruby-kubeclient: ftbfs with Passing 
permitted_classes with the 2nd argument of Psych.safe_load is deprecated
Warning: Unknown package 'ruby-kubelcient'
Unable to merge bugs because:
package of #975176 is 'src:ruby-kubeclient' not 'ruby-kubelcient'
Warning: Unknown package 'ruby-kubelcient'
Failed to forcibly merge 975512: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 1 error): merge ftbfs bugs

[Debian Bug Tracking System]

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

> merge 975512 975176
Bug #975512 [ruby-kubelcient] ruby-kubeclient: ftbfs with Passing 
permitted_classes with the 2nd argument of Psych.safe_load is deprecated
Warning: Unknown package 'ruby-kubelcient'
Unable to merge bugs because:
forwarded of #975176 is '' not 'https://github.com/abonas/kubeclient/issues/483'
package of #975176 is 'src:ruby-kubeclient' not 'ruby-kubelcient'
Warning: Unknown package 'ruby-kubelcient'
Failed to merge 975512: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: ruby-kubeclient: ftbfs with Passing permitted_classes with the 2nd argument of Psych.safe_load is deprecated

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/abonas/kubeclient/issues/483
Bug #975512 [ruby-kubelcient] ruby-kubeclient: ftbfs with Passing 
permitted_classes with the 2nd argument of Psych.safe_load is deprecated
Warning: Unknown package 'ruby-kubelcient'
Set Bug forwarded-to-address to 
'https://github.com/abonas/kubeclient/issues/483'.
Warning: Unknown package 'ruby-kubelcient'

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

Bug#975512: ruby-kubeclient: ftbfs with Passing permitted_classes with the 2nd argument of Psych.safe_load is deprecated

[Pirate Praveen]

Package: ruby-kubelcient
Version: 4.6.0-1
Severity: serious
Control: forwarded -1 https://github.com/abonas/kubeclient/issues/483

ruby-kubeclient started failing debci and ftbfs recently.

TestResourceQuota#test_get_from_json_v1 = 0.01 s = .
KubeclientConfigTest#test_user_token = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = .
KubeclientConfigTest#test_external_nopath_absolute = 0.00 s = .
KubeclientConfigTest#test_gcp_default_auth = 
/tmp/autopkgtest-lxc.0kqlxqvn/downtmp/build.PLE/src/test/test_config.rb:128: 
Passing permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = .
KubeclientConfigTest#test_gcp_default_auth_renew = 
/tmp/autopkgtest-lxc.0kqlxqvn/downtmp/build.PLE/src/test/test_config.rb:137: 
Passing permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = .
KubeclientConfigTest#test_user_exec = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.01 s = .
KubeclientConfigTest#test_user_password = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = .
KubeclientConfigTest#test_user_exec_nopath = 0.00 s = .
KubeclientConfigTest#test_external = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = F
KubeclientConfigTest#test_timestamps = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = .
KubeclientConfigTest#test_allinone = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = F
KubeclientConfigTest#test_allinone_nopath = 0.00 s = F
KubeclientConfigTest#test_nouser = 
/usr/lib/ruby/vendor_ruby/kubeclient/config.rb:33: Passing 
permitted_classes with the 2nd argument of Psych.safe_load is 
deprecated. Use keyword argument like Psych.safe_load(yaml, 
permitted_classes: ...) instead.

0.00 s = .

Finished in 0.631563s, 240.6727 runs/s, 932.6065 assertions/s.

   Failure:
   KubeclientConfigTest#test_external 
[/tmp/autopkgtest-lxc.0kqlxqvn/downtmp/build.PLE/src/test/test_config.rb:199]:

   Expected false to be truthy.

   Failure:
   KubeclientConfigTest#test_allinone 
[/tmp/autopkgtest-lxc.0kqlxqvn/downtmp/build.PLE/src/test/test_config.rb:199]:

   Expected false to be truthy.

   Failure:
   KubeclientConfigTest#test_allinone_nopath 
[/tmp/autopkgtest-lxc.0kqlxqvn/downtmp/build.PLE/src/test/test_config.rb:199]:

   Expected false to be truthy.

Full build log 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-kubeclient/8232365/log.gz


Packages that changed between the success and failure is.

-openssl 1.1.1g-1
+openssl 1.1.1h-1
-ruby-bindata 2.3.5-1
+ruby-bindata 2.4.8-1

diff of all packages (some are nmus) between pass and failure is 
attached.


Forwarded upstream at https://github.com/abonas/kubeclient/issues/483


--- ruby-kubeclient.gem2deb-test-runner-packages.pass	2020-11-23 12:40:37.258566503 +0530
+++ ruby-kubeclient.gem2deb-test-runner-packages	2020-11-23 12:38:37.801909584 +0530
@@ -2,7 +2,7 @@
 gem2deb-test-runner	1.4
 libruby2.7	2.7.2-3
 libyaml-0-2	0.2.2-1
-openssl	1.1.1g-1
+openssl	1.1.1h-1
 publicsuffix	20200729.1725-1
 rake	13.0.1-4
 ruby	1:2.7+1
@@ -10,21 +10,21 @@
 ruby-activesupport	2:6.0.3.4+dfsg-1
 ruby-addressable	2.7.0-1
 ruby-aes-key-wrap	1.0.1-1
-ruby-atomic	1.1.16-3
+ruby-atomic	1.1.16-3+b1
 ruby-attr-required	1.0.0-2
-ruby-bindata	2.3.5-1
+ruby-bindata	2.4.8-1
 ruby-concurrent	1.1.6+dfsg-3
 ruby-crack	0.4.4-1
 ruby-domain-name	0.5.20160216-2
 ruby-faraday	0.17.3-1
-ruby-ffi	1.12.2+dfsg-2+b2
+ruby-ffi	1.12.2+dfsg-2+b3
 ruby-ffi-compiler	1.0.1-4
 ruby-googleauth	0.13.0-3
 ruby-hashdiff	1.0.0-1
 ruby-http	4.4.1-4
 ruby-http-cookie	1.0.3-1
 ruby-http-form-data	2.2.0-1
-ruby-http-parser	1.2.1-4
+ruby-http-parser	1.2.1-4+b1
 ruby-httpclient	2.8.3-2
 ruby-i18n	1.8.5-1
 ruby-json-jwt	1.11.0-1
@@ -61,7 +61,7 @@
 ruby-to-regexp	0.2.1-2
 ruby-tzinfo	1.2.6-1
 ruby-unf	0.1.4-2
-ruby-unf-ext	0.0.7.6-1+b2
+ruby-unf-ext	

Bug#975092: marked as done (python-meshio: autopkgtest regression on armhf and i386: KeyError: 'uint32')

[Debian Bug Tracking System]

Your message dated Mon, 23 Nov 2020 07:03:57 +
with message-id 
and subject line Bug#975092: fixed in python-meshio 4.3.5-2
has caused the Debian Bug report #975092,
regarding python-meshio: autopkgtest regression on armhf and i386: KeyError: 
'uint32'
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.)


-- 
975092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-meshio
Version: 4.3.5-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of python-meshio the autopkgtest of python-meshio
fails in testing when that autopkgtest is run with the binary packages
of python-meshio from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
python-meshiofrom testing4.3.5-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
python-meshio/4.3.5-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=python-meshio

https://ci.debian.net/data/autopkgtest/testing/armhf/p/python-meshio/8257367/log.gz


=== FAILURES
===
 test_xdmf3[XML-mesh4]
_

mesh = 
  Number of points: 9
  Number of cells:
triangle6: 2
data_format = 'XML'

@pytest.mark.parametrize("mesh", test_set_full)
@pytest.mark.parametrize("data_format", ["XML", "Binary", "HDF"])
def test_xdmf3(mesh, data_format):
def write(*args, **kwargs):
return meshio.xdmf.write(*args, data_format=data_format,
**kwargs)

>   helpers.write_read(write, meshio.xdmf.read, mesh, 1.0e-14)

test/test_xdmf.py:42:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
test/helpers.py:347: in write_read
writer(p, input_mesh)
test/test_xdmf.py:40: in write
return meshio.xdmf.write(*args, data_format=data_format, **kwargs)
/usr/lib/python3/dist-packages/meshio/xdmf/main.py:530: in write
XdmfWriter(*args, **kwargs)
/usr/lib/python3/dist-packages/meshio/xdmf/main.py:351: in __init__
self.cells(mesh.cells, grid)
/usr/lib/python3/dist-packages/meshio/xdmf/main.py:431: in cells
data_item.text = self.numpy_to_xml_string(cells[0].data)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

self = 
data = array([[0, 1, 2, 3, 4, 5],
   [1, 6, 2, 8, 7, 4]], dtype=uint32)

def numpy_to_xml_string(self, data):
if self.data_format == "XML":
s = BytesIO()
>   fmt = dtype_to_format_string[data.dtype.name]
E   KeyError: 'uint32'

/usr/lib/python3/dist-packages/meshio/xdmf/main.py:362: KeyError
 test_xdmf3[XML-mesh6]
_

mesh = 
  Number of points: 13
  Number of cells:
quad8: 2
data_format = 'XML'

@pytest.mark.parametrize("mesh", test_set_full)
@pytest.mark.parametrize("data_format", ["XML", "Binary", "HDF"])
def test_xdmf3(mesh, data_format):
def write(*args, **kwargs):
return meshio.xdmf.write(*args, data_format=data_format,
**kwargs)

>   helpers.write_read(write, meshio.xdmf.read, mesh, 1.0e-14)

test/test_xdmf.py:42:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
test/helpers.py:347: in write_read
writer(p, input_mesh)
test/test_xdmf.py:40: in write
return meshio.xdmf.write(*args, data_format=data_format, **kwargs)
/usr/lib/python3/dist-packages/meshio/xdmf/main.py:530: in write
XdmfWriter(*args, **kwargs)
/usr/lib/python3/dist-packages/meshio/xdmf/main.py:351: in __init__
self.cells(mesh.cells, grid)
/usr/lib/python3/dist-packages/meshio/xdmf/main.py:431: in cells
data_item.text = self.numpy_to_xml_string(cells[0].data)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#974428: in.telnetd crashes on running Nessus security scan

[parameswaran krishnamurthy]

Thanks for acknowledging the Bug report and identifying a fix.Like to
know, when netkit-telnet package  deb with the bug fix be
released.Please let me know , in case someone is aware of the release
plan.Thanks in advance.

Bug#975470: python-meshplex: autopkgtest regression on 32 bit archs: TypeError: Cannot cast array data from dtype('int64') to dtype('int32') according to the rule 'safe'

[Drew Parsons]

Control: forwarded 975470 https://github.com/nschloe/meshplex/issues/90

Yeah, issue #90 already raised upstream.

Drew

Processed: Re: Bug#975470: python-meshplex: autopkgtest regression on 32 bit archs: TypeError: Cannot cast array data from dtype('int64') to dtype('int32') according to the rule 'safe'

[Debian Bug Tracking System]

Processing control commands:

> forwarded 975470 https://github.com/nschloe/meshplex/issues/90
Bug #975470 [src:python-meshplex] python-meshplex: autopkgtest regression on 32 
bit archs: TypeError: Cannot cast array data from dtype('int64') to 
dtype('int32') according to the rule 'safe'
Set Bug forwarded-to-address to 'https://github.com/nschloe/meshplex/issues/90'.

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

Bug#975209: marked as done (shadowsocks-v2ray-plugin: FTBFS: src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package "github.com/lucas-clemente/quic-go")

[Debian Bug Tracking System]

Your message dated Mon, 23 Nov 2020 02:48:59 +
with message-id 
and subject line Bug#975209: fixed in golang-v2ray-core 4.31.0+ds-2
has caused the Debian Bug report #975209,
regarding shadowsocks-v2ray-plugin: FTBFS: 
src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package 
"github.com/lucas-clemente/quic-go"
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.)


-- 
975209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shadowsocks-v2ray-plugin
Version: 1.3.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package shadowsocks-v2ray-plugin
> dpkg-buildpackage: info: source version 1.3.1-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Roger Shimizu 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --buildsystem=golang --with=golang
>dh_auto_clean -O--buildsystem=golang
>dh_autoreconf_clean -O--buildsystem=golang
>dh_clean -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building shadowsocks-v2ray-plugin using existing 
> ./shadowsocks-v2ray-plugin_1.3.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building shadowsocks-v2ray-plugin in 
> shadowsocks-v2ray-plugin_1.3.1-3.debian.tar.xz
> dpkg-source: info: building shadowsocks-v2ray-plugin in 
> shadowsocks-v2ray-plugin_1.3.1-3.dsc
>  debian/rules binary
> dh binary --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/shadowsocks/v2ray-plugin
> src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package 
> "github.com/lucas-clemente/quic-go" in any of:
>   /usr/lib/go-1.15/src/github.com/lucas-clemente/quic-go (from $GOROOT)
>   
> /<>/obj-x86_64-linux-gnu/src/github.com/lucas-clemente/quic-go 
> (from $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/shadowsocks/v2ray-plugin returned exit code 1
> make: *** [debian/rules:14: binary] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/11/19/shadowsocks-v2ray-plugin_1.3.1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-v2ray-core
Source-Version: 4.31.0+ds-2
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated golang-v2ray-core 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, 23 Nov 2020 10:16:26 +0900
Source: golang-v2ray-core
Architecture: source
Version: 4.31.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Roger Shimizu 
Closes: 975209
Changes:
 golang-v2ray-core (4.31.0+ds-2) unstable; urgency=medium
 .
   * Upload to unstable.
   * debian/control:
 - golang-v2ray-core-dev depends on
   golang-github-lucas-clemente-quic-go-dev (Closes: #975209)
 .
 golang-v2ray-core (4.31.0+ds-2~exp1) 

Processed: Re: FTBFS: src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package "github.com/lucas-clemente/quic-go"

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 golang-v2ray-core-dev 4.31.0+ds-1~exp1
Bug #975209 [src:shadowsocks-v2ray-plugin] shadowsocks-v2ray-plugin: FTBFS: 
src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package 
"github.com/lucas-clemente/quic-go"
Bug reassigned from package 'src:shadowsocks-v2ray-plugin' to 
'golang-v2ray-core-dev'.
No longer marked as found in versions shadowsocks-v2ray-plugin/1.3.1-3.
Ignoring request to alter fixed versions of bug #975209 to the same values 
previously set
Bug #975209 [golang-v2ray-core-dev] shadowsocks-v2ray-plugin: FTBFS: 
src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package 
"github.com/lucas-clemente/quic-go"
There is no source info for the package 'golang-v2ray-core-dev' at version 
'4.31.0+ds-1~exp1' with architecture ''
Unable to make a source version for version '4.31.0+ds-1~exp1'
Marked as found in versions 4.31.0+ds-1~exp1.

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

Bug#975209: FTBFS: src/v2ray.com/core/transport/internet/quic/conn.go:11:2: cannot find package "github.com/lucas-clemente/quic-go"

[Roger Shimizu]

control: reassign -1 golang-v2ray-core-dev 4.31.0+ds-1~exp1

golang-v2ray-core-dev should depend on golang-github-lucas-clemente-quic-go-dev

Bug#975501: FTBFS: undefined reference to symbol 'SSL_get_verify_callback@@OPENSSL_1_1_0'

[Shengjing Zhu]

Package: dpaste
Version: 0.4.0-1
Severity: serious
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org

Dear Maintainer,

When rebuild your package, it FTBFS

g++ -std=c++17  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++17  
-Wl,-z,relro -Wl,-z,now -o dpaste dpaste-main.o libdpaste.a -lopendht -lnettle 
-lgnutls -largon2 -lhttp_parser -lpthread -lglibmm-2.4 -lgobject-2.0 -lglib-2.0 
-lsigc-2.0 -Llib/x86_64-linux-gnu -lcurlpp -Wl,-z,relro -lcurl -lb64 -lgpgmepp 
-L/usr/lib/x86_64-linux-gnu -lgpgme -lassuan -lgpg-error 
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libopendht.a(http.cpp.o): undefined 
reference to symbol 'SSL_get_verify_callback@@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libssl.so.1.1: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status

Bug#973120: marked as done (netatalk: FTBFS: bufferevent_openssl.c:106:3: error: invalid use of incomplete typedef ‘BIO’ {aka ‘struct bio_st’})

[Debian Bug Tracking System]

Your message dated Mon, 23 Nov 2020 01:18:27 +
with message-id 
and subject line Bug#973120: fixed in netatalk 3.1.12~ds-6
has caused the Debian Bug report #973120,
regarding netatalk: FTBFS: bufferevent_openssl.c:106:3: error: invalid use of 
incomplete typedef ‘BIO’ {aka ‘struct bio_st’}
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.)


-- 
973120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netatalk
Version: 3.1.12~ds-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.  
> -I./compat -I./include -I./include  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -fno-strict-aliasing -pthread -c -o 
> bufferevent_openssl.lo bufferevent_openssl.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./compat -I./include -I./include 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -fno-strict-aliasing -pthread -c 
> bufferevent_openssl.c  -fPIC -DPIC -o .libs/bufferevent_openssl.o
> bufferevent_openssl.c: In function ‘bio_bufferevent_new’:
> bufferevent_openssl.c:106:3: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   106 |  b->init = 0;
>   |   ^~
> bufferevent_openssl.c:107:3: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   107 |  b->num = -1;
>   |   ^~
> bufferevent_openssl.c:108:3: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   108 |  b->ptr = NULL; /* We'll be putting the bufferevent in this field.*/
>   |   ^~
> bufferevent_openssl.c:109:3: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   109 |  b->flags = 0;
>   |   ^~
> bufferevent_openssl.c: In function ‘bio_bufferevent_free’:
> bufferevent_openssl.c:119:7: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   119 |  if (b->shutdown) {
>   |   ^~
> bufferevent_openssl.c:120:8: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   120 |   if (b->init && b->ptr)
>   |^~
> bufferevent_openssl.c:120:19: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   120 |   if (b->init && b->ptr)
>   |   ^~
> bufferevent_openssl.c:121:22: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   121 |bufferevent_free(b->ptr);
>   |  ^~
> bufferevent_openssl.c:122:4: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   122 |   b->init = 0;
>   |^~
> bufferevent_openssl.c:123:4: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   123 |   b->flags = 0;
>   |^~
> bufferevent_openssl.c:124:4: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   124 |   b->ptr = NULL;
>   |^~
> bufferevent_openssl.c: In function ‘bio_bufferevent_read’:
> bufferevent_openssl.c:140:8: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   140 |  if (!b->ptr)
>   |^~
> bufferevent_openssl.c:143:33: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   143 |  input = bufferevent_get_input(b->ptr);
>   | ^~
> bufferevent_openssl.c: In function ‘bio_bufferevent_write’:
> bufferevent_openssl.c:159:31: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   159 |  struct bufferevent *bufev = b->ptr;
>   |   ^~
> bufferevent_openssl.c:165:8: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   165 |  if (!b->ptr)
>   |^~
> bufferevent_openssl.c: In function ‘bio_bufferevent_ctrl’:
> bufferevent_openssl.c:191:31: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   191 |  struct bufferevent *bufev = b->ptr;
>   |   ^~
> bufferevent_openssl.c:196:10: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   196 |   ret = b->shutdown;
>   |  ^~
> bufferevent_openssl.c:199:4: error: invalid use of incomplete typedef ‘BIO’ 
> {aka ‘struct bio_st’}
>   199 |   b->shutdown = 

Processed: Re: Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."

[Debian Bug Tracking System]

Processing control commands:

> found 975490 2020.10+dfsg-1+b1
Bug #975490 [u-boot-sunxi] u-boot-sunxi: Booting the system got stuck after 
"Starting kernel ..."
Marked as found in versions u-boot/2020.10+dfsg-1.

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

Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."

[Vagrant Cascadian]

Control: found 975490 2020.10+dfsg-1+b1

Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."

[Vagrant Cascadian]

Control: version 975490 2020.10+dfsg-1+b1

Thanks for the bug report...

On 2020-11-22, Benedikt Spranger wrote:
> after a fresh install of Debian "bullseye" the first reboot got stuck
> after  "Starting kernel ..."
>
> It turend out that booting the system got always stuck using the a
> "normal" u-boot boot sequence. Using extlinux or FIT-Images is not
> affected.
>
> boot.scr : FAIL
> extlinux : OK
> FIT-Image: OK
>
> Since the Debian Installer provides neither extlinux configuration nor
> build a FIT-Image the system is unusable after the reboot from the
> installer.

Very surprising that extlinux would work but boot.scr would not; they
almost certainly use the same load addresses...

This symptom is sometimes related to the kernel or device tree or
initramfs overwriting the load address of one of the other values.

Can you get to a u-boot prompt and:

  printenv fdt_addr_r kernel_addr_r ramdisk_addr_r


Could you downgrade to the 2020.10+dfsg-1 version from snapshot.debian.org
and see if that has the same issue?


> I got into the same situation during an update on an other system to
> bullseye.

What other board?


> Bootlog:
> ---8<---
> U-Boot SPL 2020.10+dfsg-1+b1 (Nov 19 2020 - 03:18:11 +)
> DRAM: 1024 MiB
> Trying to boot from MMC2
> NOTICE:  BL31: v2.3():
> NOTICE:  BL31: Built : 05:17:48, Oct 18 2020
> NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
> NOTICE:  BL31: Found U-Boot DTB at 0x4093968, model: Olimex
> A64-Olinuxino-eMMC INFO:ARM GICv2 driver initialized
> INFO:Configuring SPC Controller
> INFO:PMIC: Probing AXP803 on RSB
> INFO:PMIC: Enabling DRIVEVBUS
> INFO:PMIC: dcdc1 voltage: 3.300V
> INFO:PMIC: dcdc5 voltage: 1.360V
> INFO:PMIC: dcdc6 voltage: 1.100V
> INFO:PMIC: dldo1 voltage: 3.300V
> INFO:PMIC: dldo2 voltage: 3.300V
> INFO:PMIC: dldo3 voltage: 2.800V
> INFO:PMIC: dldo4 voltage: 3.300V
> INFO:PMIC: fldo1 voltage: 1.200V
> INFO:PMIC: Enabling DC SW
> INFO:BL31: Platform setup done
> INFO:BL31: Initializing runtime services
> INFO:BL31: cortex_a53: CPU workaround for 843419 was applied
> INFO:BL31: cortex_a53: CPU workaround for 855873 was applied
> NOTICE:  PSCI: System suspend is unavailable
> INFO:BL31: Preparing for EL3 exit to normal world
> INFO:Entry point address = 0x4a00
> INFO:SPSR = 0x3c9
> alloc space exhausted
>
>
> U-Boot 2020.10+dfsg-1+b1 (Nov 19 2020 - 03:18:11 +) Allwinner
> Technology
>
> CPU:   Allwinner A64 (SUN50I)
> Model: Olimex A64-Olinuxino-eMMC
> DRAM:  1 GiB
> MMC:   mmc@1c0f000: 0, mmc@1c1: 2, mmc@1c11000: 1
> Loading Environment from FAT... Unable to use mmc 1:1... In:serial
> Out:   serial
> Err:   serial
> Net:   phy interface7
> eth0: ethernet@1c3
> starting USB...
> Bus usb@1c1a000: USB EHCI 1.00
> Bus usb@1c1a400: USB OHCI 1.0
> Bus usb@1c1b000: USB EHCI 1.00
> Bus usb@1c1b400: USB OHCI 1.0
> scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
> scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
> scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
> scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
>scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc1(part 0) is current device
> Scanning mmc 1:1...
> Found U-Boot script /boot.scr
> 2225 bytes read in 2 ms (1.1 MiB/s)
> ## Executing script at 4fc0
> 22744944 bytes read in 1003 ms (21.6 MiB/s)
> 28403 bytes read in 5 ms (5.4 MiB/s)
> 30071341 bytes read in 1326 ms (21.6 MiB/s)
> Booting Debian 5.9.0-2-arm64 from mmc 1:1...
> Moving Image from 0x4008 to 0x4020, end=4185
> ## Flattened Device Tree blob at 4fa0
>Booting using the fdt blob at 0x4fa0
> EHCI failed to shut down host controller.
>Loading Ramdisk to 48352000, end 49fffa2d ... OK
>Loading Device Tree to 48348000, end 48351ef2 ... OK
>
> Starting kernel ...

I wish flash-kernel were more verbose about which files it is
loading... are there other similar variants to this board that require a
different device-tree and is the boot.scr loading the correct one?

Maybe add some debugging into the boot.scr used in /etc/flash-kernel/

I'll test on a few of my systems to see if I can reproduce the issue.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#975219: [Debichem-devel] Bug#975219: elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at tree-nested.c:288

[Florian Weimer]

* Lucas Nussbaum:

> Hi Michael,
>
> On 22/11/20 at 15:32 +0100, Michael Banck wrote:
>> Hi Lucas,
>> 
>> That looks like an ICE, shouldn't that be filed with gfortran?
>
> Usually my logic is: if there's only one similar failure, I file a bug
> against the affected package, rather than against the toolchain package
> or the library, because it might be something very strange with the
> package that is causing the toolchain to misbehave.

ICEs are still consider GCC bugs (by upstream, maybe not by Debian),
as long as they are reproducible and not the result of faulty
hardware.

Processed: bug 975492 is forwarded to https://bugs.scummvm.org/ticket/11969

[Debian Bug Tracking System]

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

> forwarded 975492 https://bugs.scummvm.org/ticket/11969
Bug #975492 [scummvm] scummvm: FTBFS on big-endian platforms
Set Bug forwarded-to-address to 'https://bugs.scummvm.org/ticket/11969'.
> thanks
Stopping processing here.

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

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

[Cristian Ionescu-Idbohrn]

On Sun, 22 Nov 2020, Matteo F. Vescovi wrote:
> On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote:
> 
> [...]
> 
> > IMO, my remarks and comments are all _but_ snide and stupid. The
> > problem here, as I see it, is this maintainer's _arrogant_ attitude.
> 
> Michael, sorry to say, but Cristian is right:
> 
> I see no snide and stupid comments to the bug report and I'm 
> actually affected by this weird behaviour since a week or so, I must 
> admit.

Yes, I'm not alone.  I noticed this odd behaviour months ago but did 
not report it, as I expected that kind of _arrogant_ reaction.

> I'm still digging in to find the culprit (possibly, a particular 
> version of NM or MM that introduced the issue)

For me, it does not appear ModemManager has anything to do with this, 
but I can't rule that out.

> but I need some more tests with alternative setups to fully 
> understand the situation (seems like systems with both Wi-Fi and 
> WWAN are affected).

I can reproduce this in another way too.  My laptop has both a wifi 
and a wired chip.  When I stick in the cable, the same problem occurs: 
I loose the DNS configuration in /etc/resolv.conf.  I can add that 
manually, but that should _not_ be expected.

Another peculiar behaviour is that if I poweroff connected to the wifi 
and startup wired connected, I end up having to disconnect the cable 
and connect it back again to be able to get things (sort of) working 
again.  In both cases (wired/wireless) I rely on the router's DHCP to 
provide the proper DNS configuration.  That may need another bug 
report, if anyone else is able to reproduce.


Cheers,

-- 
Cristian

Bug#971174: marked as done (strophejs: FTBFS: Error: Cannot find module '/usr/lib/nodejs/requirejs/r.js')

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 20:47:53 +
with message-id 
and subject line Bug#971174: fixed in strophejs 1.2.14+dfsg-6
has caused the Debian Bug report #971174,
regarding strophejs: FTBFS: Error: Cannot find module 
'/usr/lib/nodejs/requirejs/r.js'
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.)


-- 
971174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strophejs
Version: 1.2.14+dfsg-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> node /usr/lib/nodejs/requirejs/r.js -o build.js 
> name=/usr/share/nodejs/almond/almond.js insertRequire=strophe-polyfill 
> include=strophe-polyfill out=strophe.min.js
> internal/modules/cjs/loader.js:968
>   throw err;
>   ^
> 
> Error: Cannot find module '/usr/lib/nodejs/requirejs/r.js'
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:965:15)
> at Function.Module._load (internal/modules/cjs/loader.js:841:27)
> at Function.executeUserEntryPoint [as runMain] 
> (internal/modules/run_main.js:71:12)
> at internal/main/run_main_module.js:17:47 {
>   code: 'MODULE_NOT_FOUND',
>   requireStack: []
> }
> make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/strophejs_1.2.14+dfsg-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: strophejs
Source-Version: 1.2.14+dfsg-6
Done: Marcelo Jorge Vieira 

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

Debian distribution maintenance software
pp.
Marcelo Jorge Vieira  (supplier of updated strophejs 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, 22 Nov 2020 16:56:25 -0300
Source: strophejs
Binary: libjs-strophe
Architecture: source all
Version: 1.2.14+dfsg-6
Distribution: unstable
Urgency: high
Maintainer: Debian XMPP Maintainers 
Changed-By: Marcelo Jorge Vieira 
Description:
 libjs-strophe - Library for writing XMPP clients
Closes: 971174
Changes:
 strophejs (1.2.14+dfsg-6) unstable; urgency=high
 .
   * Fixed FTBFS (Closes: #971174)
 - Error: Cannot find module '/usr/lib/nodejs/requirejs/r.js'
   * Fixed duplicate-globbing-patterns (src/polyfills.js)
Checksums-Sha1:
 22be5e1b40f694507a80363b158c3dfe9509708b 2048 strophejs_1.2.14+dfsg-6.dsc
 78da3699ba0c652c195ab43e6a5761ea53a0f615 4284 
strophejs_1.2.14+dfsg-6.debian.tar.xz
 38f273b5ec7f38ca5a98bb67429cc39d2a9f0f34 72916 
libjs-strophe_1.2.14+dfsg-6_all.deb
 310035a8bf4141f2a41f711b3877a98597f80cb9 7886 
strophejs_1.2.14+dfsg-6_amd64.buildinfo
Checksums-Sha256:
 ccc59f5f0c8974da1646bed7dd56789a06ae40bb253c6c963cf50d245a535863 2048 
strophejs_1.2.14+dfsg-6.dsc
 9b0aca5850079c878880fe727b1608145965779436853c813bf1d20a15e16278 4284 
strophejs_1.2.14+dfsg-6.debian.tar.xz
 46ad8a916a71926022016b099b03160fb8efd47f04d34bb3518827d977659372 72916 
libjs-strophe_1.2.14+dfsg-6_all.deb
 a22aefa32847eb7bb1cd23f029b7b2f4aaa7ff6dd23a37a82f98aae279a29973 7886 
strophejs_1.2.14+dfsg-6_amd64.buildinfo
Files:
 d0b6ace3c6e9801c17e503d9f7933796 2048 web optional strophejs_1.2.14+dfsg-6.dsc
 22298c6e24feb562548aaf879e66a519 4284 web optional 
strophejs_1.2.14+dfsg-6.debian.tar.xz
 0127e3acf7ef14ecca60507582302816 72916 web optional 
libjs-strophe_1.2.14+dfsg-6_all.deb
 1e06b2e59634454b7af44ee04f72eac9 7886 web optional 
strophejs_1.2.14+dfsg-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: tagging 968965

[Debian Bug Tracking System]

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

> tags 968965 + pending
Bug #968965 [src:xen] xen: FTBFS in sid
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#975492: scummvm: FTBFS on big-endian platforms

[Stephen Kitt]

Package: scummvm
Version: 2.2.0+dfsg1-1
Severity: serious
Tags: upstream
Justification: ftbfs

Dear Maintainer,

On big-endian platforms, test/engines/ultima/ultima8/misc/memset_n.h
fails because the memset_n functions assume they're running on a
little-endian platform. On a big-endian platform, the value written to
memory will depend on the alignment: if the value is aligned, it will
be written as expected (MSB first), but if it's not aligned, it will
be written in a mixture of little- and big-endian. The tests always
use the host memory order.

Regards,

Stephen


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

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

Versions of packages scummvm depends on:
ii  libasound2   1.1.8-1
ii  libc62.28-10
ii  libfaad2 2.8.8-3
ii  libflac8 1.3.2-3
ii  libfluidsynth1   1.1.11-1
ii  libfreetype6 2.9.1-3+deb10u2
ii  libgcc1  1:8.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libmad0  0.15.1b-10
ii  libmpeg2-4   0.5.1-8
ii  libogg0  1.3.2-1+b1
ii  libpng16-16  1.6.36-6
ii  libsdl2-2.0-02.0.9+dfsg1-1
ii  libsndio7.0  1.5.0-3
ii  libstdc++6   8.3.0-6
ii  libtheora0   1.1.1+dfsg.1-15
ii  libvorbis0a  1.3.6-2
ii  libvorbisfile3   1.3.6-2
ii  scummvm-data 2.0.0+dfsg-2
ii  zlib1g   1:1.2.11.dfsg-1

scummvm recommends no packages.

Versions of packages scummvm suggests:
ii  beneath-a-steel-sky 0.0372-7
ii  drascula1.0+ds3-1
ii  flight-of-the-amazon-queen  1.0.0-8
ii  fluidsynth  1.1.11-1
ii  lure-of-the-temptress   1.1+ds2-3
ii  timidity2.14.0-8

-- no debconf information

Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

[Matteo F. Vescovi]

Hi!

On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote:

[...]

> IMO, my remarks and comments are all _but_ snide and stupid. The
> problem here, as I see it, is this maintainer's _arrogant_ attitude.

Michael, sorry to say, but Cristian is right:

I see no snide and stupid comments to the bug report and I'm actually
affected by this weird behaviour since a week or so, I must admit.

I'm still digging in to find the culprit (possibly, a particular version
of NM or MM that introduced the issue) but I need some more tests with
alternative setups to fully understand the situation (seems like systems
with both Wi-Fi and WWAN are affected).

I'm gonna let you know my findings in the real hope to fix the problem
as soon as possible, as it's quite annoying.

Cheers.

-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#974759: marked as done (insighttoolkit4-python: not installable with python 3.8)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 19:49:20 +
with message-id 
and subject line Bug#974759: fixed in insighttoolkit4 4.13.3withdata-dfsg1-3
has caused the Debian Bug report #974759,
regarding insighttoolkit4-python: not installable with python 3.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.)


-- 
974759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: insighttoolkit4-python
Version: 4.13.2-dfsg1-1
Severity: serious
User: trei...@debian.org
Usertag: edos-unstallable

Hi,

insighttoolkit4-python depends on python3 (< 3.8), the current version
of python3 in sid however is 3.8.6-1. The dependency is generated from
${python3:Depends} so it might be sufficient to recompile the package.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: insighttoolkit4
Source-Version: 4.13.3withdata-dfsg1-3
Done: Gert Wollny 

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated insighttoolkit4 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, 22 Nov 2020 20:28:32 +0100
Source: insighttoolkit4
Architecture: source
Version: 4.13.3withdata-dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Closes: 974759
Changes:
 insighttoolkit4 (4.13.3withdata-dfsg1-3) unstable; urgency=medium
 .
   * source only upload to force rebuild Closes: #974759
Checksums-Sha1:
 061327bad1b051a2ad5f8418d0f0c8e64323c54c 2684 
insighttoolkit4_4.13.3withdata-dfsg1-3.dsc
 eb67b6eae58784c952101dbeb21301c815ddafdf 26696 
insighttoolkit4_4.13.3withdata-dfsg1-3.debian.tar.xz
 786b64102a3d6d8897ad1b108406178582de0024 10240 
insighttoolkit4_4.13.3withdata-dfsg1-3_source.buildinfo
Checksums-Sha256:
 f3d8f06aea618a62fff181fde617254c1cdd13eb373057aa3a35e1dbea13e019 2684 
insighttoolkit4_4.13.3withdata-dfsg1-3.dsc
 774aa0a1d4a6d9ede62a7ad14a1fbc24520292060d89755cec9ed6cd221ca24f 26696 
insighttoolkit4_4.13.3withdata-dfsg1-3.debian.tar.xz
 32a6d52d0e4ad82d51dece0bbbd9a99a263a1177ebdf8552d1643fd3e06387ce 10240 
insighttoolkit4_4.13.3withdata-dfsg1-3_source.buildinfo
Files:
 e9fafdef0ac9a64e103b6567ef160094 2684 science optional 
insighttoolkit4_4.13.3withdata-dfsg1-3.dsc
 3f5da8e544bb465550d8e48c4d46e515 26696 science optional 
insighttoolkit4_4.13.3withdata-dfsg1-3.debian.tar.xz
 b18468ae8f242bba0b348707c6f6a5d8 10240 science optional 
insighttoolkit4_4.13.3withdata-dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAl+6vVAACgkQl/LU/KCf
ME5JqA//Zl9BDV492yzLy/5A1kOo62P2Mpm+1DgHTbPOtR5A3xY/ZL5tfA+rqioJ
2XZrbh5SGghhDXrB1oLJx6Pj2NUkgz0hpzUgjl5JzmvFzkXM9jGpWcC+gC1gGYri
wo8cunpnkBkT7mPsv7r7RyeDAX4bwuGgL1VlwZHQFhzczVYEQfiKKP4vY5Uv25ea
GJdIIji9193LchiV+vmUl8qG0KEKZghRMJ5HGx/H8cpTdNC6DXk04EHFhicw8Fyp
nzVArbytbsyz7Z8F0JHa/pD0+nlFScx/7IWpjUl2wElYSoWEEWN+rCLadT0hhomO
0NHwZd6jGkpKxln4kZMCEdLRMoaP25KZ1hxpKdGSm75LxcSqM00bxEjtIwz/QIG9
16AVyJNz7DEiSNfslEKbSya1hUgpLqF1Jdm+MFg1IamQ7q9WRNX92USTXqlL94TE
VwTPdA/IvYMhFHSMlUyN/ra8z+vBgT/6REVuJG/JZ5nAd6aGX6I6FUKIoRVuZpOz
PQjpLxYa/k0t1YIP7Gmd/UXEASBxrCiLCb0o5PBHmRlgaEwa8wLCe9AiMOomcpfb
gdr7SUnGYIkNPLcJBw3DjqF2s6NVbr37MbJOiLoYJosMGOdfpx8MhUqqPgZSGurr
RapBJ/7gSik4DivRcEWooGmL60kveMJRCwX5TZl2I8/dpQs0gYY=
=ignU
-END PGP SIGNATURE End Message ---

Bug#975463: marked as done (breezy's autopkg tests fail with Python 3.9)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 19:48:37 +
with message-id 
and subject line Bug#975463: fixed in breezy 3.1.0-7
has caused the Debian Bug report #975463,
regarding breezy's autopkg tests fail with Python 3.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.)


-- 
975463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:breezy
Version: 3.1.0-6
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

breezy's autopkg tests fail with Python 3.9:

[...]
AssertionError: not equal:
a = b'Requested to stop gracefully\n'
b = b"brz: ERROR: AttributeError: 'Thread' object has no attribute 'isAlive'\n"
--- End Message ---
--- Begin Message ---
Source: breezy
Source-Version: 3.1.0-7
Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= 

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated breezy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Nov 2020 18:35:25 +
Source: breezy
Architecture: source
Version: 3.1.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Breezy Maintainers 
Changed-By: Jelmer Vernooij 
Closes: 975463
Changes:
 breezy (3.1.0-7) unstable; urgency=medium
 .
   * Add patch 19_is_alive: avoid Thread.isAlive, not available in Python
 3.9. Closes: #975463
   * Add patch 20_urlescape: drop test for exception which isn't raised
 on Python 3.9.
Checksums-Sha1:
 b5a67ef1f2f3ba7b72f69c67b21c4ca36a0da4b8 2691 breezy_3.1.0-7.dsc
 21c817d87cc81b535e00d77556d819a40b157bc5 56964 breezy_3.1.0-7.debian.tar.xz
 4f47bb02a23c34222bf0ff3b9ac057014e5d17b2 10735 breezy_3.1.0-7_amd64.buildinfo
Checksums-Sha256:
 6a1f237d25b237873902262bf92bfe7685bbe3a7867cafa4c83deb981c45fff6 2691 
breezy_3.1.0-7.dsc
 96b4bf8dc4aa2e011cf77cc5d2983b46b3840b7da990e149e12393628ee06c5e 56964 
breezy_3.1.0-7.debian.tar.xz
 9cf88c39eb7d8646c106023054b33c3d99a445f34ec0389e06664756390a1376 10735 
breezy_3.1.0-7_amd64.buildinfo
Files:
 e5586ede1b5dd5fbd57d66e81ed4f144 2691 vcs optional breezy_3.1.0-7.dsc
 0709598116ab823dca7770d727f40598 56964 vcs optional 
breezy_3.1.0-7.debian.tar.xz
 9b1c3c35ad980da34863667528adae5a 10735 vcs optional 
breezy_3.1.0-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl+6u2sACgkQV5wWDUye
I+h3NQ/+L+r8BxS81izFnoNzL4KwEHUmm6JSTxyIG6y9ba0aWQvlhqHE2hhzkTtJ
rCIJ72z6BDESZdrYyorp/dmVRRuKZAT5s1WADtOn1Rh34Mdj1yiEhxn5rpuLzreV
h/htacS7cIcat98nOOaLHrNMsOC1J6lunjas+b5f9yB2PL55NRtIInXKMA/olzJM
Ta+p/rVkQhdWH4CbFc6MObiIssqf2oV5GgFwvpahZJNx6O34J/pHqcPzDHu6dZev
qrMd38aUQaH2lP5/yUSM3PXTudtSAavjwKxPV0KCSPWMW8rUjyqtOD/nIE5B3mqC
qs1QEku6wfLdRtseGYutimIUmLsW1VqPkIkGOJXClJqDyCAlLzL0HhUbos/ubeoK
vhU9UxmX3xTnJpIr84ag6Wp5lOOk1hR/KO6dWNNgxQj8IXZfGag52Tkj4DPK+Cun
sqCGPKf7k2Hhs1dDTbo3eKBC6oz/ST6QLZ4w+nw0mpAwJw0OsRKh+/Gfb4+wJTuG
TU9XG+uG2jbqIhnV8A4KGFuLq4YzgYpY01BAipPUl6ETqVXl9/GJO03mNot25aAw
Pa8zWhL2aig+q4uZAhjulCUiu74rV6wdCBM4WUwm00ULRW7NpBwscR6L6b+V8mHq
kCP9/QYjhinN5EmsAG1osW3UhnSfJ/FGdsENQqV280f898s2zU0=
=bn03
-END PGP SIGNATURE End Message ---

Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."

[Benedikt Spranger]

Package: u-boot-sunxi
Severity: critical

Dear Maintainer,

after a fresh install of Debian "bullseye" the first reboot got stuck
after  "Starting kernel ..."

It turend out that booting the system got always stuck using the a
"normal" u-boot boot sequence. Using extlinux or FIT-Images is not
affected.

boot.scr : FAIL
extlinux : OK
FIT-Image: OK

Since the Debian Installer provides neither extlinux configuration nor
build a FIT-Image the system is unusable after the reboot from the
installer.

I got into the same situation during an update on an other system to
bullseye.

Bootlog:
---8<---
U-Boot SPL 2020.10+dfsg-1+b1 (Nov 19 2020 - 03:18:11 +)
DRAM: 1024 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.3():
NOTICE:  BL31: Built : 05:17:48, Oct 18 2020
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x4093968, model: Olimex
A64-Olinuxino-eMMC INFO:ARM GICv2 driver initialized
INFO:Configuring SPC Controller
INFO:PMIC: Probing AXP803 on RSB
INFO:PMIC: Enabling DRIVEVBUS
INFO:PMIC: dcdc1 voltage: 3.300V
INFO:PMIC: dcdc5 voltage: 1.360V
INFO:PMIC: dcdc6 voltage: 1.100V
INFO:PMIC: dldo1 voltage: 3.300V
INFO:PMIC: dldo2 voltage: 3.300V
INFO:PMIC: dldo3 voltage: 2.800V
INFO:PMIC: dldo4 voltage: 3.300V
INFO:PMIC: fldo1 voltage: 1.200V
INFO:PMIC: Enabling DC SW
INFO:BL31: Platform setup done
INFO:BL31: Initializing runtime services
INFO:BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:BL31: cortex_a53: CPU workaround for 855873 was applied
NOTICE:  PSCI: System suspend is unavailable
INFO:BL31: Preparing for EL3 exit to normal world
INFO:Entry point address = 0x4a00
INFO:SPSR = 0x3c9
alloc space exhausted


U-Boot 2020.10+dfsg-1+b1 (Nov 19 2020 - 03:18:11 +) Allwinner
Technology

CPU:   Allwinner A64 (SUN50I)
Model: Olimex A64-Olinuxino-eMMC
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c1: 2, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1... In:serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c3
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
2225 bytes read in 2 ms (1.1 MiB/s)
## Executing script at 4fc0
22744944 bytes read in 1003 ms (21.6 MiB/s)
28403 bytes read in 5 ms (5.4 MiB/s)
30071341 bytes read in 1326 ms (21.6 MiB/s)
Booting Debian 5.9.0-2-arm64 from mmc 1:1...
Moving Image from 0x4008 to 0x4020, end=4185
## Flattened Device Tree blob at 4fa0
   Booting using the fdt blob at 0x4fa0
EHCI failed to shut down host controller.
   Loading Ramdisk to 48352000, end 49fffa2d ... OK
   Loading Device Tree to 48348000, end 48351ef2 ... OK

Starting kernel ...
---8<---

Regards
Benedikt Spranger

Processed: your mail

[Debian Bug Tracking System]

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

> tags 975455 + pending
Bug #975455 [src:devtodo] devtodo: failing autopkgtests with grep 3.6
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#975460: fontforge: FTBFS on i386 [patch]

[Gianfranco Costamagna]

BTW the macro was DEB_HOST_MULTIARCH, as you already know
G.


On Sun, 22 Nov 2020 19:47:34 +0100 Gianfranco Costamagna 
 wrote:
> looks like fixed already in git:
> https://salsa.debian.org/fonts-team/fontforge/commit/c52b395bda57c305
> 
> Closing.
> 
> G.
> 
> On Sun, 22 Nov 2020 16:23:54 +0100 Gianfranco Costamagna 
>  wrote:
> > Source: fontforge
> > Version: 1:20201107~dfsg-1
> > Severity: serious
> > tags: patch
> > 
> > 
> > Hello, to fix the build failure I think debian/libfontforge4.install should 
> > contain this line:
> > usr/lib/${DEB_BUILD_MULTIARCH}
> > 
> > Full patch:
> > 
> > --- fontforge-20201107~dfsg/debian/changelog2020-11-18 
> > 09:42:18.0 +0100
> > +++ fontforge-20201107~dfsg/debian/changelog2020-11-22 
> > 15:24:41.0 +0100
> > @@ -1,3 +1,9 @@
> > +fontforge (1:20201107~dfsg-1.1) UNRELEASED; urgency=medium
> > +
> > +  * Fix i386 build (Closes: #-1)
> > +
> > + -- Gianfranco Costamagna   Sun, 22 Nov 2020 
> > 15:24:41 +0100
> > +
> >  fontforge (1:20201107~dfsg-1) unstable; urgency=medium
> >  
> >[ Jonas Smedegaard ]
> > diff -Nru fontforge-20201107~dfsg/debian/libfontforge4.install 
> > fontforge-20201107~dfsg/debian/libfontforge4.install
> > --- fontforge-20201107~dfsg/debian/libfontforge4.install2020-11-17 
> > 10:15:18.0 +0100
> > +++ fontforge-20201107~dfsg/debian/libfontforge4.install2020-11-22 
> > 15:24:40.0 +0100
> > @@ -1 +1 @@
> > -usr/lib/${DEB_HOST_GNU_TYPE}
> > +usr/lib/${DEB_BUILD_MULTIARCH}
> > 
> > 
> 
> 

Processed: reopening 975460, tagging 975460

[Debian Bug Tracking System]

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

> reopen 975460
Bug #975460 {Done: Gianfranco Costamagna } 
[src:fontforge] fontforge: FTBFS on i386 [patch]
Bug reopened
Ignoring request to alter fixed versions of bug #975460 to the same values 
previously set
> tags 975460 + pending
Bug #975460 [src:fontforge] fontforge: FTBFS on i386 [patch]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#975488: lammps FTBFS: error: format not a string literal and no format arguments

[Adrian Bunk]

Source: lammps
Version: 20200303+dfsg1-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/lammps.html

...
/usr/bin/c++ -DFFT_FFTW3 -DFFT_FFTW_THREADS -DLAMMPS_GZIP -DLAMMPS_JPEG 
-DLAMMPS_MEMALIGN=64 -DLAMMPS_PNG -DLAMMPS_SMALLBIG -DLAMMPS_VTK 
-DLMP_HAS_NETCDF -DLMP_KIM_CURL -DLMP_MPIIO -DLMP_PYTHON -DLMP_USER_OMP 
-DNC_64BIT_DATA=0x0020 
-DvtkDomainsChemistry_AUTOINIT="1(vtkDomainsChemistryOpenGL2)" 
-DvtkFiltersCore_AUTOINIT="1(vtkFiltersParallelDIY2)" 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL2)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL2)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLICOpenGL2_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingOpenGL2_AUTOINIT="1(vtkRenderingGL2PSOpenGL2)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL2)" 
-I/build/lammps-20200303+dfsg1/src 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python3.9 
-I/usr/include/voro++ -I/usr/include/eigen3 -I/usr/include/vtk-7.1 
-I/usr/include/freetype2 -I/usr/include/python3.8 -I/usr/include/hdf5/openmpi 
-I/usr/include/jsoncpp -I/usr/include/libxml2 -I/usr/include/tcl 
-I/usr/include/kim-api -I/usr/lib/x86_64-linux-gnu/kim-api/mod 
-I/build/lammps-20200303+dfsg1/src/ASPHERE 
-I/build/lammps-20200303+dfsg1/src/BODY 
-I/build/lammps-20200303+dfsg1/src/CLASS2 
-I/build/lammps-20200303+dfsg1/src/COLLOID 
-I/build/lammps-20200303+dfsg1/src/COMPRESS 
-I/build/lammps-20200303+dfsg1/src/CORESHELL 
-I/build/lammps-20200303+dfsg1/src/DIPOLE 
-I/build/lammps-20200303+dfsg1/src/GRANULAR 
-I/build/lammps-20200303+dfsg1/src/KSPACE 
-I/build/lammps-20200303+dfsg1/src/MANYBODY 
-I/build/lammps-20200303+dfsg1/src/MC -I/build/lammps-20200303+dfsg1/src/MISC 
-I/build/lammps-20200303+dfsg1/src/MOLECULE 
-I/build/lammps-20200303+dfsg1/src/PERI 
-I/build/lammps-20200303+dfsg1/src/POEMS -I/build/lammps-20200303+dfsg1/src/QEQ 
-I/build/lammps-20200303+dfsg1/src/REPLICA 
-I/build/lammps-20200303+dfsg1/src/RIGID 
-I/build/lammps-20200303+dfsg1/src/SHOCK 
-I/build/lammps-20200303+dfsg1/src/SNAP -I/build/lammps-20200303+dfsg1/src/SRD 
-I/build/lammps-20200303+dfsg1/src/KIM 
-I/build/lammps-20200303+dfsg1/src/PYTHON 
-I/build/lammps-20200303+dfsg1/src/MPIIO 
-I/build/lammps-20200303+dfsg1/src/VORONOI 
-I/build/lammps-20200303+dfsg1/src/USER-ATC 
-I/build/lammps-20200303+dfsg1/src/USER-AWPMD 
-I/build/lammps-20200303+dfsg1/src/USER-BOCS 
-I/build/lammps-20200303+dfsg1/src/USER-CGDNA 
-I/build/lammps-20200303+dfsg1/src/USER-MESO 
-I/build/lammps-20200303+dfsg1/src/USER-CGSDK 
-I/build/lammps-20200303+dfsg1/src/USER-DIFFRACTION 
-I/build/lammps-20200303+dfsg1/src/USER-DPD 
-I/build/lammps-20200303+dfsg1/src/USER-DRUDE 
-I/build/lammps-20200303+dfsg1/src/USER-EFF 
-I/build/lammps-20200303+dfsg1/src/USER-FEP 
-I/build/lammps-20200303+dfsg1/src/USER-H5MD 
-I/build/lammps-20200303+dfsg1/src/USER-LB 
-I/build/lammps-20200303+dfsg1/src/USER-MANIFOLD 
-I/build/lammps-20200303+dfsg1/src/USER-MEAMC 
-I/build/lammps-20200303+dfsg1/src/USER-MGPT 
-I/build/lammps-20200303+dfsg1/src/USER-MISC 
-I/build/lammps-20200303+dfsg1/src/USER-MOFFF 
-I/build/lammps-20200303+dfsg1/src/USER-MOLFILE 
-I/build/lammps-20200303+dfsg1/src/USER-NETCDF 
-I/build/lammps-20200303+dfsg1/src/USER-PHONON 
-I/build/lammps-20200303+dfsg1/src/USER-QTB 
-I/build/lammps-20200303+dfsg1/src/USER-SMD 
-I/build/lammps-20200303+dfsg1/src/USER-SMTBQ 
-I/build/lammps-20200303+dfsg1/src/USER-SPH 
-I/build/lammps-20200303+dfsg1/src/USER-TALLY 
-I/build/lammps-20200303+dfsg1/src/USER-UEF 
-I/build/lammps-20200303+dfsg1/src/USER-VTK 
-I/build/lammps-20200303+dfsg1/lib/poems -I/usr/include/hdf5/serial 
-I/build/lammps-20200303+dfsg1/src/USER-OMP 
-I/build/lammps-20200303+dfsg1/src/OPT -I/build/lammps-20200303+dfsg1/src/GPU 
-I/build/lammps-20200303+dfsg1/debian/build/styles -g -O2 
-fdebug-prefix-map=/build/lammps-20200303+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -o 
CMakeFiles/poems.dir/build/lammps-20200303+dfsg1/lib/poems/joint.cpp.o -c 
/build/lammps-20200303+dfsg1/lib/poems/joint.cpp
In file included from 
/build/lammps-20200303+dfsg1/lib/awpmd/systems/interact/TCP/wpmd.h:149,
 from 
/build/lammps-20200303+dfsg1/lib/awpmd/systems/interact/TCP/wpmd_split.h:65,
 from 
/build/lammps-20200303+dfsg1/lib/awpmd/systems/interact/TCP/wpmd_split.cpp:1:
/build/lammps-20200303+dfsg1/lib/awpmd/ivutils/include/pairhash.h: In function 
'int fileout(FILE*, const 

Bug#975460: marked as done (fontforge: FTBFS on i386 [patch])

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 19:47:34 +0100
with message-id <3ff0d555-30f1-4f9b-9182-479ae6132...@debian.org>
and subject line Re: fontforge: FTBFS on i386 [patch]
has caused the Debian Bug report #975460,
regarding fontforge: FTBFS on i386 [patch]
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.)


-- 
975460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontforge
Version: 1:20201107~dfsg-1
Severity: serious
tags: patch


Hello, to fix the build failure I think debian/libfontforge4.install should 
contain this line:
usr/lib/${DEB_BUILD_MULTIARCH}

Full patch:

--- fontforge-20201107~dfsg/debian/changelog2020-11-18 09:42:18.0 
+0100
+++ fontforge-20201107~dfsg/debian/changelog2020-11-22 15:24:41.0 
+0100
@@ -1,3 +1,9 @@
+fontforge (1:20201107~dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Fix i386 build (Closes: #-1)
+
+ -- Gianfranco Costamagna   Sun, 22 Nov 2020 
15:24:41 +0100
+
 fontforge (1:20201107~dfsg-1) unstable; urgency=medium
 
   [ Jonas Smedegaard ]
diff -Nru fontforge-20201107~dfsg/debian/libfontforge4.install 
fontforge-20201107~dfsg/debian/libfontforge4.install
--- fontforge-20201107~dfsg/debian/libfontforge4.install2020-11-17 
10:15:18.0 +0100
+++ fontforge-20201107~dfsg/debian/libfontforge4.install2020-11-22 
15:24:40.0 +0100
@@ -1 +1 @@
-usr/lib/${DEB_HOST_GNU_TYPE}
+usr/lib/${DEB_BUILD_MULTIARCH}
--- End Message ---
--- Begin Message ---
looks like fixed already in git:
https://salsa.debian.org/fonts-team/fontforge/commit/c52b395bda57c305

Closing.

G.

On Sun, 22 Nov 2020 16:23:54 +0100 Gianfranco Costamagna 
 wrote:
> Source: fontforge
> Version: 1:20201107~dfsg-1
> Severity: serious
> tags: patch
> 
> 
> Hello, to fix the build failure I think debian/libfontforge4.install should 
> contain this line:
> usr/lib/${DEB_BUILD_MULTIARCH}
> 
> Full patch:
> 
> --- fontforge-20201107~dfsg/debian/changelog  2020-11-18 09:42:18.0 
> +0100
> +++ fontforge-20201107~dfsg/debian/changelog  2020-11-22 15:24:41.0 
> +0100
> @@ -1,3 +1,9 @@
> +fontforge (1:20201107~dfsg-1.1) UNRELEASED; urgency=medium
> +
> +  * Fix i386 build (Closes: #-1)
> +
> + -- Gianfranco Costamagna   Sun, 22 Nov 2020 
> 15:24:41 +0100
> +
>  fontforge (1:20201107~dfsg-1) unstable; urgency=medium
>  
>[ Jonas Smedegaard ]
> diff -Nru fontforge-20201107~dfsg/debian/libfontforge4.install 
> fontforge-20201107~dfsg/debian/libfontforge4.install
> --- fontforge-20201107~dfsg/debian/libfontforge4.install  2020-11-17 
> 10:15:18.0 +0100
> +++ fontforge-20201107~dfsg/debian/libfontforge4.install  2020-11-22 
> 15:24:40.0 +0100
> @@ -1 +1 @@
> -usr/lib/${DEB_HOST_GNU_TYPE}
> +usr/lib/${DEB_BUILD_MULTIARCH}
> 
> --- End Message ---

Bug#974683: marked as done (trafficserver: autopkgtest uses pip to download and install code from the internet)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 18:36:19 +
with message-id 
and subject line Bug#974683: fixed in trafficserver 8.1.0+ds-2
has caused the Debian Bug report #974683,
regarding trafficserver: autopkgtest uses pip to download and install code from 
the internet
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.)


-- 
974683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trafficserver
Version: 8.1.0+ds-1
Severity: serious
Justification: ftp-master autoreject ruling

Hi,

Your package has an autopkgtest, awesome. However, I noticed that it
installs Python code using pip. Running downloaded code from internet is
not allowed in the Debian archive; see the ftp-masters autoreject list [1].

Downloading data seems to be allowed, but please add a needs-internet
restriction in that case.

Also, your test fails once in a while. Please if you keep it after the
above, make it more robust against network issues.

Paul

[1] https://ftp-master.debian.org/REJECT-FAQ.html [Non-Main II]


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

https://ci.debian.net/data/autopkgtest/testing/arm64/t/trafficserver/8149771/log.gz

env-test/bin/pip install autest==1.8.0 hyper requests dnslib httpbin
gunicorn traffic-replay
Collecting autest==1.8.0
  Downloading autest-1.8.0-py3-none-any.whl (138 kB)
Collecting hyper
  Downloading hyper-0.7.0-py2.py3-none-any.whl (269 kB)
Collecting requests
  Downloading requests-2.25.0-py2.py3-none-any.whl (61 kB)
Collecting dnslib
  Downloading dnslib-0.9.14.tar.gz (72 kB)
Collecting httpbin
  Downloading httpbin-0.7.0-py2.py3-none-any.whl (86 kB)
Collecting gunicorn
  Downloading gunicorn-20.0.4-py2.py3-none-any.whl (77 kB)
Collecting traffic-replay
  Downloading traffic_replay-1.0.0-py3-none-any.whl (25 kB)
Collecting future
  Downloading future-0.18.2.tar.gz (829 kB)
Collecting psutil
  Downloading psutil-5.7.3.tar.gz (465 kB)
Collecting colorama
  Downloading colorama-0.4.4-py2.py3-none-any.whl (16 kB)
Collecting h2<3.0,>=2.4
  Downloading h2-2.6.2-py2.py3-none-any.whl (71 kB)
Collecting hyperframe<4.0,>=3.2
  Downloading hyperframe-3.2.0-py2.py3-none-any.whl (13 kB)
Collecting chardet<4,>=3.0.2
  Downloading chardet-3.0.4-py2.py3-none-any.whl (133 kB)
Collecting certifi>=2017.4.17
  Downloading certifi-2020.11.8-py2.py3-none-any.whl (155 kB)
Collecting urllib3<1.27,>=1.21.1
  Downloading urllib3-1.26.2-py2.py3-none-any.whl (136 kB)
Collecting idna<3,>=2.5
  Downloading idna-2.10-py2.py3-none-any.whl (58 kB)
Collecting six
  Downloading six-1.15.0-py2.py3-none-any.whl (10 kB)
Collecting Flask
  Downloading Flask-1.1.2-py2.py3-none-any.whl (94 kB)
Collecting brotlipy
  Downloading brotlipy-0.7.0.tar.gz (413 kB)
ERROR: Command errored out with exit status 1:
 command:
/tmp/autopkgtest-lxc.dz4jb_fv/downtmp/build.51D/src/tests/env-test/bin/python
-c 'import sys, setuptools, tokenize; sys.argv[0] =
'"'"'/tmp/pip-install-aze8omd7/brotlipy/setup.py'"'"';
__file__='"'"'/tmp/pip-install-aze8omd7/brotlipy/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
egg_info --egg-base /tmp/pip-pip-egg-info-7_jpp5o4
 cwd: /tmp/pip-install-aze8omd7/brotlipy/
Complete output (32 lines):
ERROR: Could not find a version that satisfies the requirement
cffi>=1.0.0 (from versions: none)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 8.1.0+ds-2
Done: Jean Baptiste Favre 

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

Debian distribution maintenance software
pp.
Jean Baptiste Favre  (supplier of updated trafficserver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Nov 2020 18:24:18 +0100
Source: 

Processed: reopen, issue not fixed

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #975284 {Done: YOKOTA Hiroshi } [calibre] calibre: 
crashes on start
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions calibre/5.5.0+dfsg-2.

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

Bug#975284: reopen, issue not fixed

[Matthias Klose]

Control: reopen -1

looking at the build log at
https://buildd.debian.org/status/fetch.php?pkg=calibre=amd64=5.5.0%2Bdfsg-2=1606054693=0

[...]
find debian/tmp -type f | xargs sed -i '1 { /^#!.*python/
s_^.*$_#!/usr/bin/python3.9_ }'

why?

[...]
make[1]: Leaving directory '/<>'
   dh_python3 -a -O--buildsystem=makefile
E: dh_python3 dh_python3:176: no package to act on (python3-foo or one with
${python3:Depends} in Depends)

something goes wrong

Depends: libc6 (>= 2.29), libespeak-ng1 (>= 1.50+dfsg), libfontconfig1 (>=
2.12.6), libfreetype6 (>= 2.6), libgcc-s1 (>= 3.0), libglib2.0-0 (>= 2.12.0),
libhunspell-1.7-0, libhyphen0 (>= 2.8.7), libicu67 (>= 67.1-1~), libmtp9 (>=
1.1.5), libpodofo0.9.6 (>= 0.9.6+dfsg), libpython3.9 (>= 3.9.0~b4), libqt5core5a
(>= 5.15.1), libqt5dbus5 (>= 5.12), libqt5gui5 (>= 5.14.1) | libqt5gui5-gles (>=
5.14.1), libqt5widgets5 (>= 5.12), libstdc++6 (>= 5.2), libusb-1.0-0 (>=
2:1.0.9), qtbase-abi-5-15-1, python3-pyqt5.sip, python3

no python3:Depends dependency generated, and the 'python3' dependency is not
good enough

the calibre-bin package needs to end up with a dependency:

 python3 (>= 3.9), python3 (<< 3.10)

Bug#975486: rust-libz-sys: autopkgtest failure: src/zlib/adler32.c: No such file or directory

[Paul Gevers]

Source: rust-libz-sys
Version: 1.1.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package rust-libz-sys, great.
However, it fails. Currently this failure is blocking the migration to
testing [1]. Can you please investigate the situation and fix it?

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=rust-libz-sys

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-libz-sys/7592938/log.gz

 Running
`/tmp/tmp.GylevYz9Se/target/debug/build/libz-sys-4d7f2bd81492bad5/build-script-build`
[libz-sys 1.1.2] cargo:rerun-if-env-changed=LIBZ_SYS_STATIC
[libz-sys 1.1.2] cargo:rerun-if-changed=build.rs
[libz-sys 1.1.2] TARGET = Some("x86_64-unknown-linux-gnu")
[libz-sys 1.1.2] OPT_LEVEL = Some("0")
[libz-sys 1.1.2] HOST = Some("x86_64-unknown-linux-gnu")
[libz-sys 1.1.2] CC_x86_64-unknown-linux-gnu = None
[libz-sys 1.1.2] CC_x86_64_unknown_linux_gnu = None
[libz-sys 1.1.2] HOST_CC = None
[libz-sys 1.1.2] CC = None
[libz-sys 1.1.2] CFLAGS_x86_64-unknown-linux-gnu = None
[libz-sys 1.1.2] CFLAGS_x86_64_unknown_linux_gnu = None
[libz-sys 1.1.2] HOST_CFLAGS = None
[libz-sys 1.1.2] CFLAGS = Some("-g -O2
-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=.
-fstack-protector-strong -Wformat -Werror=format-security")
[libz-sys 1.1.2] CRATE_CC_NO_DEFAULTS = None
[libz-sys 1.1.2] DEBUG = Some("true")
[libz-sys 1.1.2] CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
[libz-sys 1.1.2] running: "cc" "-O0" "-ffunction-sections"
"-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-g"
"-O2" "-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=."
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-I"
"src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE"
"-D_POSIX_SOURCE" "-o"
"/tmp/tmp.GylevYz9Se/target/x86_64-unknown-linux-gnu/debug/build/libz-sys-a4a1831fc0ceaac9/out/build/src/zlib/adler32.o"
"-c" "src/zlib/adler32.c"
[libz-sys 1.1.2] cargo:warning=cc: error: src/zlib/adler32.c: No such
file or directory
[libz-sys 1.1.2] cargo:warning=cc: fatal error: no input files
[libz-sys 1.1.2] cargo:warning=compilation terminated.
[libz-sys 1.1.2] exit code: 1
[libz-sys 1.1.2]
[libz-sys 1.1.2]
[libz-sys 1.1.2] error occurred: Command "cc" "-O0"
"-ffunction-sections" "-fdata-sections" "-fPIC" "-g"
"-fno-omit-frame-pointer" "-m64" "-g" "-O2"
"-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=."
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-I"
"src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE"
"-D_POSIX_SOURCE" "-o"
"/tmp/tmp.GylevYz9Se/target/x86_64-unknown-linux-gnu/debug/build/libz-sys-a4a1831fc0ceaac9/out/build/src/zlib/adler32.o"
"-c" "src/zlib/adler32.c" with args "cc" did not execute successfully
(status code exit code: 1).
[libz-sys 1.1.2]
[libz-sys 1.1.2]
error: failed to run custom build command for `libz-sys v1.1.2
(/usr/share/cargo/registry/libz-sys-1.1.2)`

Caused by:
  process didn't exit successfully:
`/tmp/tmp.GylevYz9Se/target/debug/build/libz-sys-4d7f2bd81492bad5/build-script-build`
(exit code: 1)
--- stdout
cargo:rerun-if-env-changed=LIBZ_SYS_STATIC
cargo:rerun-if-changed=build.rs
TARGET = Some("x86_64-unknown-linux-gnu")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-unknown-linux-gnu")
CC_x86_64-unknown-linux-gnu = None
CC_x86_64_unknown_linux_gnu = None
HOST_CC = None
CC = None
CFLAGS_x86_64-unknown-linux-gnu = None
CFLAGS_x86_64_unknown_linux_gnu = None
HOST_CFLAGS = None
CFLAGS = Some("-g -O2
-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=.
-fstack-protector-strong -Wformat -Werror=format-security")
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g"
"-fno-omit-frame-pointer" "-m64" "-g" "-O2"
"-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=."
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-I"
"src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE"
"-D_POSIX_SOURCE" "-o"
"/tmp/tmp.GylevYz9Se/target/x86_64-unknown-linux-gnu/debug/build/libz-sys-a4a1831fc0ceaac9/out/build/src/zlib/adler32.o"
"-c" "src/zlib/adler32.c"
cargo:warning=cc: error: src/zlib/adler32.c: No such file or directory
cargo:warning=cc: fatal error: no input files
cargo:warning=compilation terminated.
exit code: 1

--- stderr


error occurred: Command "cc" "-O0" "-ffunction-sections"
"-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-g"
"-O2" "-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=."
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-I"
"src/zlib" "-fvisibility=hidden" "-DSTDC" 

Bug#975484: rust-dbus: autopkgtest regression: build failed: expected `str`, found struct `std::ffi::CStr`

[Paul Gevers]

Source: rust-dbus
Version: 0.9.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of rust-dbus the autopkgtest of rust-dbus fails in
testing when that autopkgtest is run with the binary packages of
rust-dbus from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
rust-dbus  from testing0.9.0-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=rust-dbus

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-dbus/8343716/log.gz

 Running `CARGO_MANIFEST_DIR=/usr/share/cargo/registry/dbus-0.9.0
LD_LIBRARY_PATH='/tmp/tmp.mOh7cBiqA2/target/debug/deps:/usr/lib'
CARGO=/usr/bin/cargo CARGO_PKG_VERSION_MINOR=9 CARGO_PKG_VERSION_PATCH=0
CARGO_PKG_DESCRIPTION='Bindings to D-Bus, which is a bus commonly used
on Linux for inter-process communication.' CARGO_PKG_HOMEPAGE=
CARGO_PKG_REPOSITORY='https://github.com/diwic/dbus-rs'
CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION=0.9.0 CARGO_PKG_NAME=dbus
CARGO_PKG_AUTHORS='David Henningsson '
CARGO_PKG_VERSION_PRE= rustc --crate-name dbus --edition=2018 src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi --emit=dep-info,link
-C debuginfo=2 --test --cfg 'feature="no-string-validation"' -C
metadata=78a9c65232eb4ced -C extra-filename=-78a9c65232eb4ced --out-dir
/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/incremental
-L
dependency=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps
-L dependency=/tmp/tmp.mOh7cBiqA2/target/debug/deps --extern
libc=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps/liblibc-4745c4b1773b68fd.rlib
--extern
libdbus_sys=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps/liblibdbus_sys-be39e730af80d440.rlib
--extern
tempfile=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps/libtempfile-d85e26fb23f42f7b.rlib
-C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C
link-arg=-Wl,-z,relro --remap-path-prefix
/usr/share/cargo/registry/dbus-0.9.0=/usr/share/cargo/registry/dbus-0.9.0
-L native=/usr/lib/x86_64-linux-gnu`
error[E0308]: mismatched types
   --> src/strings.rs:230:51
|
230 | assert_eq!(p2, Ok(Path(Cow::Borrowed(unsafe {
CStr::from_ptr(b"##invalid##\0".as_ptr() as *const c_char) };
|
^^ expected
`str`, found struct `std::ffi::CStr`
|
= note: expected reference ``
   found reference `::ffi::CStr`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: could not compile `dbus`.

Caused by:
  process didn't exit successfully:
`CARGO_MANIFEST_DIR=/usr/share/cargo/registry/dbus-0.9.0
LD_LIBRARY_PATH='/tmp/tmp.mOh7cBiqA2/target/debug/deps:/usr/lib'
CARGO=/usr/bin/cargo CARGO_PKG_VERSION_MINOR=9 CARGO_PKG_VERSION_PATCH=0
CARGO_PKG_DESCRIPTION='Bindings to D-Bus, which is a bus commonly used
on Linux for inter-process communication.' CARGO_PKG_HOMEPAGE=
CARGO_PKG_REPOSITORY='https://github.com/diwic/dbus-rs'
CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION=0.9.0 CARGO_PKG_NAME=dbus
CARGO_PKG_AUTHORS='David Henningsson '
CARGO_PKG_VERSION_PRE= rustc --crate-name dbus --edition=2018 src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi --emit=dep-info,link
-C debuginfo=2 --test --cfg 'feature="no-string-validation"' -C
metadata=78a9c65232eb4ced -C extra-filename=-78a9c65232eb4ced --out-dir
/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/incremental
-L
dependency=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps
-L dependency=/tmp/tmp.mOh7cBiqA2/target/debug/deps --extern
libc=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps/liblibc-4745c4b1773b68fd.rlib
--extern
libdbus_sys=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps/liblibdbus_sys-be39e730af80d440.rlib
--extern
tempfile=/tmp/tmp.mOh7cBiqA2/target/x86_64-unknown-linux-gnu/debug/deps/libtempfile-d85e26fb23f42f7b.rlib
-C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C
link-arg=-Wl,-z,relro --remap-path-prefix
/usr/share/cargo/registry/dbus-0.9.0=/usr/share/cargo/registry/dbus-0.9.0
-L native=/usr/lib/x86_64-linux-gnu` (exit code: 1)
warning: build failed, waiting for other jobs to finish...
error: build 

Bug#975476: Acknowledgement (SUM function sometimes includes cells outside the range)

[Ben Hutchings]

Control: severity -1 normal
Control: retitle -1 No error reported for self-referential formula

Sorry, this is actually the result of a typo I couldn't see.  The sum
is of A1:A298, so it does include itself.

But I think it's a bug that self-referential formulae are not detected
as an error.  LibreOffice Calc does report an error for this.

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.




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

Bug#975480: rust-bzip2-sys: autopkgtest failure: crate directory not found: /usr/share/cargo/registry/bzip2-sys-0.1.9+1.0.8

[Paul Gevers]

Source: rust-bzip2-sys
Version: 0.1.9-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package rust-bzip2-sys, great.
However, it fails. Currently this failure is blocking the migration to
testing [1]. Can you please investigate the situation and fix it?

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=rust-bzip2-sys

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-bzip2-sys/7500282/log.gz

autopkgtest [09:47:16]: test librust-bzip2-sys-dev:
/usr/share/cargo/bin/cargo-auto-test bzip2-sys 0.1.9+1.0.8 --all-targets
--no-default-features
autopkgtest [09:47:16]: test librust-bzip2-sys-dev: [---
crate directory not found: /usr/share/cargo/registry/bzip2-sys-0.1.9+1.0.8
autopkgtest [09:47:16]: test librust-bzip2-sys-dev: ---]



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#975476: Acknowledgement (SUM function sometimes includes cells outside the range)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #975476 [gnumeric] SUM function sometimes includes cells outside the range
Severity set to 'normal' from 'serious'
> retitle -1 No error reported for self-referential formula
Bug #975476 [gnumeric] SUM function sometimes includes cells outside the range
Changed Bug title to 'No error reported for self-referential formula' from 'SUM 
function sometimes includes cells outside the range'.

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

Processed: Re: Bug#975455: devtodo: failing autopkgtests with grep 3.6

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #975455 [src:devtodo] devtodo: failing autopkgtests with grep 3.6
Added tag(s) confirmed.

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

Bug#975479: rust-rpassword: autopkgtest regression: thread 'piped_password' panicked

[Paul Gevers]

Source: rust-rpassword
Version: 5.0.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of rust-rpassword the autopkgtest of rust-rpassword
fails in testing when that autopkgtest is run with the binary packages
of rust-rpassword from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
rust-rpassword from testing5.0.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=rust-rpassword

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rpassword/8347228/log.gz

running 1 test
test piped_password ... FAILED

failures:

 piped_password stdout 
stdout:
running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out


thread 'piped_password' panicked at 'assertion failed:
stdout.ends_with("Password: secret\n")', tests/piped.rs:34:5
stack backtrace:
   0: std::panicking::begin_panic
 at /usr/src/rustc-1.47.0/library/std/src/panicking.rs:497
   1: piped::piped_password
 at ./tests/piped.rs:34
   2: piped::piped_password::{{closure}}
 at ./tests/piped.rs:8
   3: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.47.0/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.


failures:
piped_password

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0
filtered out

error: test failed, to rerun pass '--test piped'
autopkgtest [06:11:35]: test librust-rpassword-dev: ---]



signature.asc
Description: OpenPGP digital signature

Bug#975476: SUM function sometimes includes cells outside the range

[Ben Hutchings]

Package: gnumeric
Version: 1.12.48-1+b1
Severity: serious

In certain circumstances, that I haven't yet identified precisely, a
cell containing the SUM function applied to a range of values above
it appears to be recalculated including its own previous value!
This results in the sum increasing on every recalculation.

You should be able to see this in the attached sheet.  A99 contains
the formula =SUM(A1:A98) and is initially shown with a value of 4950.
If you fill in the value 1 in A98, the sum changes to 9901.

Ben.

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

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

Versions of packages gnumeric depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  gnumeric-common1.12.48-1
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.4
ii  libatk1.0-02.36.0-2
ii  libc6  2.31-4
ii  libcairo2  1.16.0-4
ii  libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii  libglib2.0-0   2.66.2-1
ii  libgoffice-0.10-10 0.10.48-1
ii  libgsf-1-114   1.14.47-1
ii  libgtk-3-0 3.24.23-2
ii  libpango-1.0-0 1.46.2-3
ii  libpangocairo-1.0-01.46.2-3
ii  libxml22.9.10+dfsg-6.2
ii  procps 2:3.3.16-5
ii  pxlib1 0.6.8-1+b1
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages gnumeric recommends:
ii  evince3.38.0-2
ii  gnumeric-doc  1.12.48-1
ii  lp-solve  5.5.2.5-2

Versions of packages gnumeric suggests:
ii  fonts-liberation1:1.07.4-11
pn  gnumeric-plugins-extra  
pn  libgsf-1-dev

-- debconf information:
  gnumeric/existing-process-title:
  gnumeric/existing-process: false


sum-bug.gnumeric
Description: application/gzip

Bug#975219: [Debichem-devel] Bug#975219: elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at tree-nested.c:288

[Lucas Nussbaum]

Hi Michael,

On 22/11/20 at 15:32 +0100, Michael Banck wrote:
> Hi Lucas,
> 
> That looks like an ICE, shouldn't that be filed with gfortran?

Usually my logic is: if there's only one similar failure, I file a bug
against the affected package, rather than against the toolchain package
or the library, because it might be something very strange with the
package that is causing the toolchain to misbehave.

(In that case, that was the only ICE; and I also notified doko about it
on IRC)

Lucas

Bug#975474: fonts-inter: source-only upload required for testing transition.

[Tobias Frost]

Package: fonts-inter
Version: 3.15+ds-1
Severity: serious

Hi Gürkan,

just a reminder: You need to do an source-only upload for testing migration.
(Can go together with the fix in #968898)

-- 
tobi


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

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

Bug#975472: xmobar: autopkgtest regression on ppc64el: Not found

[Paul Gevers]

Source: xmobar
Version: 0.36-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of xmobar the autopkgtest of xmobar fails in
testing when that autopkgtest is run with the binary packages of xmobar
from unstable ppc64el. It passes when run with only packages from
testing. In tabular form:

   passfail
xmobar from testing0.36-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. "xprop: error:
No window with name xmobar exists!" isn't new, it appears (once) in old
logs too [2].

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=xmobar
[2]
https://ci.debian.net/data/autopkgtest/testing/ppc64el/x/xmobar/8230792/log.gz


https://ci.debian.net/data/autopkgtest/testing/ppc64el/x/xmobar/8341511/log.gz

autopkgtest [08:26:54]: test command1: [---
Waiting for the X server to become ready.

Looking for the xmobar window.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
.
xprop: error: No window with name xmobar exists!
Not found
autopkgtest [08:27:24]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#975471: sbcl breaks bordeaux-threads autopkgtest on i386 as it makes it time out

[Paul Gevers]

Source: sbcl, bordeaux-threads
Control: found -1 sbcl/2:2.0.10-1
Control: found -1 bordeaux-threads/0.8.8-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update timeout

Dear maintainer(s),

With a recent upload of sbcl the autopkgtest of bordeaux-threads fails
in testing when that autopkgtest is run with the binary packages of sbcl
from unstable on i386. It passes when run with only packages from
testing. In tabular form:

   passfail
sbcl   from testing2:2.0.10-1
bordeaux-threads   from testing0.8.8-2
all others from testingfrom testing

Normally the tests succeeds in minutes, now it times out after 2:48 hours.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/i386/b/bordeaux-threads/8343313/log.gz

; wrote
/tmp/autopkgtest-lxc.eykr8ie3/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/fiveam/src/run-tmpRYWTYMDY.fasl
; compilation finished in 0:00:00.076
; compiling file
"/usr/share/common-lisp/source/bordeaux-threads/test/bordeaux-threads-test.lisp"
(written 07 JUN 2020 09:11:43 PM):
; processing (DEFPACKAGE BORDEAUX-THREADS/TEST ...)
; processing (IN-PACKAGE #:BORDEAUX-THREADS/TEST)
; processing (DEF-SUITE :BORDEAUX-THREADS)
; processing (DEF-FIXTURE USING-LOCK ...)
; processing (IN-SUITE :BORDEAUX-THREADS)
; processing (TEST SHOULD-HAVE-CURRENT-THREAD ...)
; processing (TEST CURRENT-THREAD-IDENTITY ...)
; processing (TEST JOIN-THREAD-RETURN-VALUE ...)
; processing (TEST SHOULD-IDENTIFY-THREADS-CORRECTLY ...)
; processing (TEST SHOULD-RETRIEVE-THREAD-NAME ...)
; processing (TEST INTERRUPT-THREAD ...)
; processing (TEST SHOULD-LOCK-WITHOUT-CONTENTION ...)
; processing (DEFUN SET-EQUAL ...)
; processing (TEST DEFAULT-SPECIAL-BINDINGS ...)
; processing (DEFPARAMETER *SHARED* ...)
; processing (DEFPARAMETER *LOCK* ...)
; processing (TEST SHOULD-HAVE-THREAD-INTERACTION ...)
; processing (DEFPARAMETER *CONDITION-VARIABLE* ...)
; processing (TEST CONDITION-VARIABLE ...)
; processing (TEST CONDITION-WAIT-TIMEOUT ...)
; processing (TEST SEMAPHORE-SIGNAL ...)
; processing (TEST SEMAPHORE-SIGNAL-N-OF-M ...)
; processing (TEST SEMAPHORE-WAIT-TIMEOUT ...)
; processing (TEST SEMAPHORE-TYPED ...)
; processing (TEST WITH-TIMEOUT-RETURN-VALUE ...)
; processing (TEST WITH-TIMEOUT-SIGNALS ...)
; processing (TEST WITH-TIMEOUT-NON-INTERFERENCE ...)

; wrote
/tmp/autopkgtest-lxc.eykr8ie3/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/bordeaux-threads/test/bordeaux-threads-test-tmpW78F18LW.fasl
; compilation finished in 0:00:00.008

Running test suite BORDEAUX-THREADS
 Running test SHOULD-HAVE-CURRENT-THREAD .
 Running test CURRENT-THREAD-IDENTITY .
 Running test JOIN-THREAD-RETURN-VALUE .
 Running test SHOULD-IDENTIFY-THREADS-CORRECTLY ...
 Running test SHOULD-RETRIEVE-THREAD-NAME .
 Running test INTERRUPT-THREAD .
 Running test SHOULD-LOCK-WITHOUT-CONTENTION ..
 Running test DEFAULT-SPECIAL-BINDINGS 
 Running test SHOULD-HAVE-THREAD-INTERACTION .
autopkgtest [02:57:31]: ERROR: timed out on command "su -s /bin/bash
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.eykr8ie3/downtmp/build.GXU/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.eykr8ie3/downtmp/command1-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.eykr8ie3/downtmp/command1-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.eykr8ie3/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.eykr8ie3/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; touch
/tmp/autopkgtest-lxc.eykr8ie3/downtmp/command1-stdout
/tmp/autopkgtest-lxc.eykr8ie3/downtmp/command1-stderr; bash -ec 'sbcl
--script debian/tests/runtests.lisp' 2> >(tee -a
/tmp/autopkgtest-lxc.eykr8ie3/downtmp/command1-stderr >&2) > >(tee -a
/tmp/autopkgtest-lxc.eykr8ie3/downtmp/command1-stdout);" (kind: test)
autopkgtest [02:57:32]: test command1: ---]



signature.asc

Processed: sbcl breaks bordeaux-threads autopkgtest on i386 as it makes it time out

[Debian Bug Tracking System]

Processing control commands:

> found -1 sbcl/2:2.0.10-1
Bug #975471 [src:sbcl, src:bordeaux-threads] sbcl breaks bordeaux-threads 
autopkgtest on i386 as it makes it time out
Marked as found in versions sbcl/2:2.0.10-1.
> found -1 bordeaux-threads/0.8.8-2
Bug #975471 [src:sbcl, src:bordeaux-threads] sbcl breaks bordeaux-threads 
autopkgtest on i386 as it makes it time out
Marked as found in versions bordeaux-threads/0.8.8-2.

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

Bug#975470: python-meshplex: autopkgtest regression on 32 bit archs: TypeError: Cannot cast array data from dtype('int64') to dtype('int32') according to the rule 'safe'

[Paul Gevers]

Source: python-meshplex
Version: 0.15.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of python-meshplex the autopkgtest of
python-meshplex fails in testing when that autopkgtest is run with the
binary packages of python-meshplex from unstable on armhf and i386. It
passes when run with only packages from testing. In tabular form:

   passfail
python-meshplexfrom testing0.15.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Seems like the
(test)code is written for 64 bit architectures.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-meshplex

https://ci.debian.net/data/autopkgtest/testing/armhf/p/python-meshplex/8342685/log.gz

autopkgtest [23:10:36]: test command1: [---
= test session starts
==
platform linux -- Python 3.8.6, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.2ukelk92/downtmp/build.2mK/src
collected 52 items

test/test_curl.py .
[  1%]
test/test_mesh_io.py F
[  3%]
test/test_mesh_line.py .
[  5%]
test/test_mesh_tetra.py ..s
[ 26%]
test/test_mesh_tri.py F.
[ 92%]
test/test_readme.py s
[ 94%]
test/test_subdomain.py ...
[100%]

=== FAILURES
===
__ test_io_2d
__

def test_io_2d():
>   vertices, cells = dmsh.generate(dmsh.Rectangle(0.0, 1.0, 0.0,
1.0), 0.5)

test/test_mesh_io.py:9:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/dmsh/main.py:173: in generate
mesh = distmesh_smoothing(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

mesh = 
edges = array([[ 0,  1],
   [ 0,  4],
   [ 0,  5],
   [ 0,  6],
   [ 1,  5],
   [ 1,  8],
   [ 2,  3],...7],
   [ 6,  9],
   [ 7,  8],
   [ 7,  9],
   [ 7, 10],
   [ 8, 10],
   [ 9, 10]], dtype=int32)
geo = 
num_feature_points = 4
edge_size_function = .edge_size_function at
0xf4f79cd0>
max_steps = 1, tol = 1e-05, verbose = False, show = False, delta_t = 0.2
f_scale = 1.2

def distmesh_smoothing(
mesh,
edges,
geo,
num_feature_points,
edge_size_function,
max_steps,
tol,
verbose,
show,
delta_t,
f_scale,
):
k = 0
# is_boundary_node = mesh.is_boundary_node.copy()
>   pts_old_last_recell = mesh.node_coords.copy()
E   AttributeError: 'MeshTri' object has no attribute 'node_coords'

/usr/lib/python3/dist-packages/dmsh/main.py:207: AttributeError
__ test_unit_triangle[int64]
___

cells_dtype = 

@pytest.mark.parametrize(
"cells_dtype",
[
numpy.int64
# depends on 
# numpy.uint64
],
)
def test_unit_triangle(cells_dtype):
points = numpy.array([[0.0, 0.0], [1.0, 0.0], [0.0, 1.0]])
cells = numpy.array([[0, 1, 2]], dtype=cells_dtype)
mesh = meshplex.MeshTri(points, cells)

tol = 1.0e-14

assert (mesh.local_idx.T == [[1, 2], [2, 0], [0, 1]]).all()
assert mesh.local_idx_inv == [[(0, 2), (1, 1)], [(0, 0), (1,
2)], [(0, 1), (1, 0)]]

# ce_ratios
assert near_equal(mesh.ce_ratios.T, [0.0, 0.5, 0.5], tol)

# control volumes
>   assert near_equal(mesh.control_volumes, [0.25, 0.125, 0.125], tol)

test/test_mesh_tri.py:38:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/meshplex/mesh_tri.py:348: in control_volumes
return self.get_control_volumes()
/usr/lib/python3/dist-packages/meshplex/mesh_tri.py:337: in
get_control_volumes
self._control_volumes = numpy.bincount(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

args = (array([0, 1, 2], dtype=int64),)
kwargs = {'minlength': 3, 'weights': array([0.25 , 0.125, 0.125])}
relevant_args = (array([0, 1, 2], dtype=int64), array([0.25 , 0.125,
0.125]))

>   ???
E   TypeError: Cannot cast array data from dtype('int64') to
dtype('int32') according to the rule 'safe'

<__array_function__ internals>:5: TypeError
=== warnings summary
===
test/test_mesh_tri.py::test_regular_tri_additional_points
  

Bug#975468: ruby-console: autopkgtest regression: error occurred while loading ./spec/console_spec.rb

[Paul Gevers]

Source: ruby-console
Version: 1.10.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of ruby-console the autopkgtest of ruby-console
fails in testing when that autopkgtest is run with the binary packages
of ruby-console from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
ruby-console   from testing1.10.1-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-console

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-console/8347222/log.gz

autopkgtest [06:09:47]: test gem2deb-test-runner: gem2deb-test-runner
--autopkgtest --check-dependencies 2>&1
autopkgtest [06:09:47]: test gem2deb-test-runner: [---

┌──┐
│ Checking Rubygems dependency resolution on ruby2.7
  │
└──┘

GEM_PATH= ruby2.7 -e gem\ \"console\"

┌──┐
│ Run tests for ruby2.7 from debian/ruby-tests.rake
  │
└──┘

mv lib .gem2deb.lib
RUBYLIB=. GEM_PATH= ruby2.7 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.7
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
--pattern ./spec/\*\*/\*_spec.rb --format documentation
/usr/share/rubygems-integration/all/gems/console-1.10.1/lib/console/logger.rb:57:
warning: assigned but unused variable - resolver
  0.0s info: Dear maintainer: [pid=2898] [2020-11-22 06:09:47 +]
   | Once you are done trying to 'optimize' this routine,
and have realized what a terrible mistake that was, please increment the
following counter as a warning to the next guy:
   | total_hours_wasted_here = 42
  0.0s warn: Something didn't work as expected! [pid=2898]
[2020-11-22 06:09:47 +]
  0.0serror: There be the dragons! [pid=2898] [2020-11-22 06:09:47
+]
   |   RuntimeError: Bits have been rotated incorrectly!
   |   →
/tmp/autopkgtest-lxc.67pfihrk/downtmp/build.XDY/src/spec/console/my_module.rb:30
in `test_logger'
   |
/tmp/autopkgtest-lxc.67pfihrk/downtmp/build.XDY/src/spec/console/my_module.rb:37
in `'
   |
/tmp/autopkgtest-lxc.67pfihrk/downtmp/build.XDY/src/spec/console/console_spec.rb:23
in `require_relative'
   |
/tmp/autopkgtest-lxc.67pfihrk/downtmp/build.XDY/src/spec/console/console_spec.rb:23
in `'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103
in `load'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103
in `load_file_handling_errors'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1606
in `block in load_spec_files'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604
in `each'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604
in `load_spec_files'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:102
in `setup'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:86
in `run'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:71
in `run'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:45
in `invoke'
   |
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec:4 in
`'
  0.0s info: MyModule [pid=2898] [2020-11-22 06:09:47 +]
   |   gcc -o stuff.o stuff.c in /tmp/compile
   | export LDFLAGS=-lm
  0.0s info: Object [oid=0x7a8] [pid=2898] [2020-11-22 06:09:47 +]
   | Where would we be without Object.new?

An error occurred while loading ./spec/console_spec.rb. - Did you mean?
rspec ./spec/console/console_spec.rb

Failure/Error: require_relative "../lib/console/version"

LoadError:
  cannot load such file --
/tmp/autopkgtest-lxc.67pfihrk/downtmp/build.XDY/src/lib/console/version

Bug#959638: marked as done (fmtlib: FTBFS: dh_sphinxdoc: error: debian/libfmt-doc/usr/share/doc/libfmt-doc/_static/bootstrap.min.js is missing)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 16:34:37 +
with message-id 
and subject line Bug#959638: fixed in fmtlib 6.1.2+ds-3
has caused the Debian Bug report #959638,
regarding fmtlib: FTBFS: dh_sphinxdoc: error: 
debian/libfmt-doc/usr/share/doc/libfmt-doc/_static/bootstrap.min.js is missing
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.)


-- 
959638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fmtlib
Version: 6.1.2+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> dh_install: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> dh_sphinxdoc
> dh_sphinxdoc: error: 
> debian/libfmt-doc/usr/share/doc/libfmt-doc/_static/bootstrap.min.js is missing
> make[1]: *** [debian/rules:19: override_dh_install] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/fmtlib_6.1.2+ds-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: fmtlib
Source-Version: 6.1.2+ds-3
Done: Shengjing Zhu 

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated fmtlib 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, 22 Nov 2020 23:17:23 +0800
Source: fmtlib
Architecture: source
Version: 6.1.2+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Shengjing Zhu 
Changed-By: Shengjing Zhu 
Closes: 950856 953023 959638 972869
Changes:
 fmtlib (6.1.2+ds-3) unstable; urgency=medium
 .
   * Rework sphinx doc build (Closes: #959638)
   * Adopt package, thanks Eugene V. Lyubimkin (Closes: #972869)
   * Move package source to salsa.d.o (Closes: #950856)
   * Add Multi-Arch hint, thanks Michael R. Crusoe (Closes: #953023)
   * Update new Homepage and source repository
   * Bump debhelper-compat
   * Secure copyright format url
   * Add Rules-Requires-Root
   * Bump Standards-Version
Checksums-Sha1:
 84b22ac51324d7e0119da0fd0c3ae9e560a4 1412 fmtlib_6.1.2+ds-3.dsc
 88a673cb40ae86187eeffa3969e8cae76e45e2c9 15152 fmtlib_6.1.2+ds-3.debian.tar.xz
 ca2e78566fef3f0a261b96e2047c6c552f0ca0ac 2774 
fmtlib_6.1.2+ds-3_source.buildinfo
Checksums-Sha256:
 d4c232ef7dd39d044c08bba235aede3fa4064412884baabfd7cf42134d7998b3 1412 
fmtlib_6.1.2+ds-3.dsc
 f171a0c27dd6fcd11599dc555393023cc9d39f53c4a961134b3d7e2dc1b6fdd4 15152 
fmtlib_6.1.2+ds-3.debian.tar.xz
 32f0b7ff288424c9b99c8a0df923d2de3a6f113d17c4b4efb289558ede3d6961 2774 
fmtlib_6.1.2+ds-3_source.buildinfo
Files:
 198dfab42d9d29e6fd46a2061fa5331c 1412 devel optional fmtlib_6.1.2+ds-3.dsc
 b959380b2e8dfb039f5af0faa9c3a812 15152 devel optional 
fmtlib_6.1.2+ds-3.debian.tar.xz
 8fe7c183e6745ad220df53fc4352d5b5 2774 devel optional 
fmtlib_6.1.2+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX7qQ5xAcemhzakBkZWJp
YW4ub3JnAAoJEMSFSjgY4LAW248A/1Uy5EE5/68FH3vqR/V+k6JbHGqYLXHHy4b2
/krKdEEYAPwK2aigY7M60I6rYAwQ0vv9LW4B2o7KKN0DQyVA81hABg==
=yAo2
-END PGP SIGNATURE End Message ---

Bug#975467: psignifit: autopkgtest failure on !x86: input stream is too big

[Paul Gevers]

Source: psignifit
Version: 2.5.6-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package psignifit, great.
However, it fails on arm64, armhf and ppc64el. Currently this failure is
blocking the migration to testing [1]. Can you please investigate the
situation and fix it?

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/p/psignifit/7994334/log.gz

autopkgtest [21:15:07]: test run-unit-test: [---
Test functionality

input stream is too big
autopkgtest [21:15:07]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature

Bug#966087: marked as done (libreoffice-writer: Cannot save file: General input/output error due to missing librdf0 dependency on 32bit archs)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 16:36:51 +
with message-id 
and subject line Bug#966087: fixed in libreoffice 1:7.1.0~beta1-1
has caused the Debian Bug report #966087,
regarding libreoffice-writer: Cannot save file: General input/output error due 
to missing librdf0 dependency on 32bit archs
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.)


-- 
966087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-writer
Version: 1:7.0.0~rc2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Every time I try to save a document, I get:

Error saving document 
General Error:
General input/outpur error

The document does not save. It happens every time.

This happens on existing and new documents. I deleted 
.config/libreoffice and that made no difference. I reinstalled 
libreoffice amd that made no difference. This appears to have started 
with the upgrade to libreoffice 7.

ods, odf, odg, and odp all save as expected. Only odt does not work.

Thanks

-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 5.7.0-1-686-pae (SMP w/4 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice-writer depends on:
ii  libabw-0.1-1 0.1.3-1
ii  libc62.31-1
ii  libe-book-0.1-1  0.1.3-1+b3
ii  libepubgen-0.1-1 0.1.1-1
ii  libetonyek-0.1-1 0.1.9-3
ii  libgcc-s110.1.0-6
ii  libicu67 67.1-3
ii  libmwaw-0.3-30.3.16-1
ii  libodfgen-0.1-1  0.1.7-1
ii  libreoffice-base-core1:7.0.0~rc2-1
ii  libreoffice-common   1:7.0.0~rc2-1
ii  libreoffice-core 1:7.0.0~rc2-1
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   10.1.0-6
ii  libuno-cppu3 1:7.0.0~rc2-1
ii  libuno-cppuhelpergcc3-3  1:7.0.0~rc2-1
ii  libuno-sal3  1:7.0.0~rc2-1
ii  libuno-salhelpergcc3-3   1:7.0.0~rc2-1
ii  libwpd-0.10-10   0.10.3-1
ii  libwpg-0.3-3 0.3.3-1
ii  libwps-0.4-4 0.4.11-1
ii  libxml2  2.9.10+dfsg-5+b1
ii  ucf  3.0043
ii  uno-libs-private 1:7.0.0~rc2-1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:7.0.0~rc2-1

Versions of packages libreoffice-writer suggests:
ii  default-jre [java8-runtime] 2:1.11-72
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
ii  libreoffice-base1:7.0.0~rc2-1
pn  libreoffice-java-common 
ii  openjdk-11-jre [java8-runtime]  11.0.7+9-1

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.2
ii  fonts-opensymbol2:102.11+LibO7.0.0~rc2-1
ii  libboost-locale1.71.0   1.71.0-6+b2
ii  libc6   2.31-1
ii  libcairo2   1.16.0-4
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1+b1
ii  libclucene-core1v5  2.3.3.4+dfsg-1+b1
ii  libcmis-0.5-5v5 0.5.2-2+b1
ii  libcups22.3.3-1
ii  libcurl3-gnutls 7.68.0-1+b1
ii  libdbus-1-3 1.12.20-1
ii  libdconf1   0.36.0-1
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.4-1
ii  libexpat1   2.2.9-1
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.2+dfsg-3
ii  libgcc-s1   10.1.0-6
ii  libglib2.0-02.64.4-1
ii  libgpgmepp6 1.13.1-9
ii  libgraphite2-3  1.3.14-1
ii  libgstreamer-plugins-base1.0-0  1.16.2-4
ii  libgstreamer1.0-0   1.16.2-2
ii  libharfbuzz-icu02.6.4-1+b1
ii  libharfbuzz0b   2.6.4-1+b1
ii  libhunspell-1.7-0   1.7.0-3
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.9-2
ii  libicu6767.1-3
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  liblcms2-2  2.9-4+b1
ii  libldap-2.4-2   

Processed: Re: Bug#963501: haskell-wl-pprint-terminfo: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #963501 [src:haskell-wl-pprint-terminfo] haskell-wl-pprint-terminfo: 
Removal notice: broken and unmaintained
Bug reassigned from package 'src:haskell-wl-pprint-terminfo' to 
'ftp.debian.org'.
No longer marked as found in versions haskell-wl-pprint-terminfo/3.7.1.4-7.
Ignoring request to alter fixed versions of bug #963501 to the same values 
previously set
> retitle -1 RM: haskell-wl-pprint-terminfo -- ROM; broken and unmaintained
Bug #963501 [ftp.debian.org] haskell-wl-pprint-terminfo: Removal notice: broken 
and unmaintained
Changed Bug title to 'RM: haskell-wl-pprint-terminfo -- ROM; broken and 
unmaintained' from 'haskell-wl-pprint-terminfo: Removal notice: broken and 
unmaintained'.
> severity -1 normal
Bug #963501 [ftp.debian.org] RM: haskell-wl-pprint-terminfo -- ROM; broken and 
unmaintained
Severity set to 'normal' from 'grave'

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

Bug#963501: haskell-wl-pprint-terminfo: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-wl-pprint-terminfo -- ROM; broken and 
unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-wl-pprint-terminfo from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#963499: haskell-wl-pprint-extras: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #963499 [src:haskell-wl-pprint-extras] haskell-wl-pprint-extras: Removal 
notice: broken and unmaintained
Bug reassigned from package 'src:haskell-wl-pprint-extras' to 'ftp.debian.org'.
No longer marked as found in versions haskell-wl-pprint-extras/3.5.0.5-9.
Ignoring request to alter fixed versions of bug #963499 to the same values 
previously set
> retitle -1 RM: haskell-wl-pprint-extras -- ROM; broken and unmaintained
Bug #963499 [ftp.debian.org] haskell-wl-pprint-extras: Removal notice: broken 
and unmaintained
Changed Bug title to 'RM: haskell-wl-pprint-extras -- ROM; broken and 
unmaintained' from 'haskell-wl-pprint-extras: Removal notice: broken and 
unmaintained'.
> severity -1 normal
Bug #963499 [ftp.debian.org] RM: haskell-wl-pprint-extras -- ROM; broken and 
unmaintained
Severity set to 'normal' from 'grave'

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

Bug#963499: haskell-wl-pprint-extras: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-wl-pprint-extras -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-wl-pprint-extras from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Bug#975464: haskell-werewolf: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-werewolf
Version: 1.5.2.0-4
Severity: grave
Justification: renders package unusable

This package seems to be unmaintained (last upload in 2017).
Does not build with GHC 8.8, is not part of Stackage and has no rev
dependencies.

I intend to remove this package.

-- 
Ilias

Processed: Re: Bug#966711: haskell-vector-space-points: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #966711 [src:haskell-vector-space-points] haskell-vector-space-points: 
Removal notice: broken and unmaintained
Bug reassigned from package 'src:haskell-vector-space-points' to 
'ftp.debian.org'.
No longer marked as found in versions haskell-vector-space-points/0.2.1.2-7.
Ignoring request to alter fixed versions of bug #966711 to the same values 
previously set
> retitle -1 RM: haskell-vector-space-points -- ROM; broken and unmaintained
Bug #966711 [ftp.debian.org] haskell-vector-space-points: Removal notice: 
broken and unmaintained
Changed Bug title to 'RM: haskell-vector-space-points -- ROM; broken and 
unmaintained' from 'haskell-vector-space-points: Removal notice: broken and 
unmaintained'.
> severity -1 normal
Bug #966711 [ftp.debian.org] RM: haskell-vector-space-points -- ROM; broken and 
unmaintained
Severity set to 'normal' from 'grave'

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

Bug#966711: haskell-vector-space-points: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-vector-space-points -- ROM; broken and 
unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-vector-space-points from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Bug#975463: breezy's autopkg tests fail with Python 3.9

[Matthias Klose]

Package: src:breezy
Version: 3.1.0-6
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

breezy's autopkg tests fail with Python 3.9:

[...]
AssertionError: not equal:
a = b'Requested to stop gracefully\n'
b = b"brz: ERROR: AttributeError: 'Thread' object has no attribute 'isAlive'\n"

Processed: Re: Bug#963745: haskell-regex-tdfa-text: Removal notice: Deprecated

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #963745 [src:haskell-regex-tdfa-text] haskell-regex-tdfa-text: Removal 
notice: Deprecated
Bug reassigned from package 'src:haskell-regex-tdfa-text' to 'ftp.debian.org'.
No longer marked as found in versions haskell-regex-tdfa-text/1.0.0.3-4.
Ignoring request to alter fixed versions of bug #963745 to the same values 
previously set
> retitle -1 RM: haskell-regex-tdfa-text -- ROM; deprecated
Bug #963745 [ftp.debian.org] haskell-regex-tdfa-text: Removal notice: Deprecated
Changed Bug title to 'RM: haskell-regex-tdfa-text -- ROM; deprecated' from 
'haskell-regex-tdfa-text: Removal notice: Deprecated'.
> severity -1 normal
Bug #963745 [ftp.debian.org] RM: haskell-regex-tdfa-text -- ROM; deprecated
Severity set to 'normal' from 'grave'

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

Bug#963745: haskell-regex-tdfa-text: Removal notice: Deprecated

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-regex-tdfa-text -- ROM; deprecated
Control: severity -1 normal

Hi,

Please remove haskell-regex-tdfa-text from Debian.
It is deprecated and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#902901: FTBFS: Tests fail

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #902901 [src:haskell-polynomial] FTBFS: Tests fail
Bug reassigned from package 'src:haskell-polynomial' to 'ftp.debian.org'.
No longer marked as found in versions haskell-polynomial/0.7.3-3.
Ignoring request to alter fixed versions of bug #902901 to the same values 
previously set
> retitle -1 RM: haskell-polynomial -- ROM; broken and unmaintained
Bug #902901 [ftp.debian.org] FTBFS: Tests fail
Changed Bug title to 'RM: haskell-polynomial -- ROM; broken and unmaintained' 
from 'FTBFS: Tests fail'.
> severity -1 normal
Bug #902901 [ftp.debian.org] RM: haskell-polynomial -- ROM; broken and 
unmaintained
Severity set to 'normal' from 'serious'

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

Bug#902901: FTBFS: Tests fail

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-polynomial -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-polynomial from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#971267: haskell-ncurses: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #971267 [src:haskell-ncurses] haskell-ncurses: Removal notice: broken and 
unmaintained
Bug reassigned from package 'src:haskell-ncurses' to 'ftp.debian.org'.
No longer marked as found in versions haskell-ncurses/0.2.16-4.
Ignoring request to alter fixed versions of bug #971267 to the same values 
previously set
> retitle -1 RM: haskell-ncurses -- ROM; broken and unmaintained
Bug #971267 [ftp.debian.org] haskell-ncurses: Removal notice: broken and 
unmaintained
Changed Bug title to 'RM: haskell-ncurses -- ROM; broken and unmaintained' from 
'haskell-ncurses: Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #971267 [ftp.debian.org] RM: haskell-ncurses -- ROM; broken and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#971267: haskell-ncurses: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-ncurses -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-ncurses from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Bug#962970: haskell-permutation: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-permutation -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-permutation from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#962970: haskell-permutation: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962970 [src:haskell-permutation] haskell-permutation: Removal notice: 
broken and unmaintained
Bug reassigned from package 'src:haskell-permutation' to 'ftp.debian.org'.
No longer marked as found in versions haskell-permutation/0.5.0.5-3.
Ignoring request to alter fixed versions of bug #962970 to the same values 
previously set
> retitle -1 RM: haskell-permutation -- ROM; broken and unmaintained
Bug #962970 [ftp.debian.org] haskell-permutation: Removal notice: broken and 
unmaintained
Changed Bug title to 'RM: haskell-permutation -- ROM; broken and unmaintained' 
from 'haskell-permutation: Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #962970 [ftp.debian.org] RM: haskell-permutation -- ROM; broken and 
unmaintained
Severity set to 'normal' from 'grave'

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

Processed: Re: Bug#962964: haskell-io-choice: Removal notice: broken and obsolete

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962964 [src:haskell-io-choice] haskell-io-choice: Removal notice: broken 
and obsolete
Bug reassigned from package 'src:haskell-io-choice' to 'ftp.debian.org'.
No longer marked as found in versions haskell-io-choice/0.0.7-1.
Ignoring request to alter fixed versions of bug #962964 to the same values 
previously set
> retitle -1 RM: haskell-io-choice -- ROM; broken and obsolete
Bug #962964 [ftp.debian.org] haskell-io-choice: Removal notice: broken and 
obsolete
Changed Bug title to 'RM: haskell-io-choice -- ROM; broken and obsolete' from 
'haskell-io-choice: Removal notice: broken and obsolete'.
> severity -1 normal
Bug #962964 [ftp.debian.org] RM: haskell-io-choice -- ROM; broken and obsolete
Severity set to 'normal' from 'grave'

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

Bug#962964: haskell-io-choice: Removal notice: broken and obsolete

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-io-choice -- ROM; broken and obsolete
Control: severity -1 normal

Hi,

Please remove haskell-io-choice from Debian.
It is obsolete and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#962962: haskell-hstatsd: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962962 [src:haskell-hstatsd] haskell-hstatsd: Removal notice: broken and 
unmaintained
Bug reassigned from package 'src:haskell-hstatsd' to 'ftp.debian.org'.
No longer marked as found in versions haskell-hstatsd/0.1-7.
Ignoring request to alter fixed versions of bug #962962 to the same values 
previously set
> retitle -1 RM: haskell-hstatsd -- ROM; broken and unmaintained
Bug #962962 [ftp.debian.org] haskell-hstatsd: Removal notice: broken and 
unmaintained
Changed Bug title to 'RM: haskell-hstatsd -- ROM; broken and unmaintained' from 
'haskell-hstatsd: Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #962962 [ftp.debian.org] RM: haskell-hstatsd -- ROM; broken and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#962962: haskell-hstatsd: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-hstatsd -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-hstatsd from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#968008: carettah: Removal notice: unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #968008 [carettah] carettah: Removal notice: unmaintained
Bug reassigned from package 'carettah' to 'ftp.debian.org'.
No longer marked as found in versions carettah/0.5.1-2.
Ignoring request to alter fixed versions of bug #968008 to the same values 
previously set
> retitle -1 RM: carettah -- ROM; unmaintained
Bug #968008 [ftp.debian.org] carettah: Removal notice: unmaintained
Changed Bug title to 'RM: carettah -- ROM; unmaintained' from 'carettah: 
Removal notice: unmaintained'.
> severity -1 normal
Bug #968008 [ftp.debian.org] RM: carettah -- ROM; unmaintained
Severity set to 'normal' from 'grave'

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

Bug#968008: carettah: Removal notice: unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: carettah -- ROM; unmaintained
Control: severity -1 normal

Hi,

Please remove carettah from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Bug#975418: marked as done (ostree: FTBFS with test failure on some filesystems: tests/test-pull-summary-sigs.sh: Successful pull with old summary)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 15:36:23 +
with message-id 
and subject line Bug#975418: fixed in ostree 2020.8-2
has caused the Debian Bug report #975418,
regarding ostree: FTBFS with test failure on some filesystems: 
tests/test-pull-summary-sigs.sh: Successful pull with old summary
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.)


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

ostree 2020.8-1 successfully built in my build environment (sbuild on a
qemu VM running Debian 10, with ext4 filesystems) and on mips*el and
various ports architectures, but failed on all non-mips*el release
architectures.

I think this might be filesystem-dependent: the equivalent installed-test
succeeds when run from an empty directory on btrfs, but fails when run
from an empty directory on tmpfs. I'm looking into it, no need to report
it again.

>From the point at which the test fails, it might be to do with timestamp
resolution?

smcv
--- End Message ---
--- Begin Message ---
Source: ostree
Source-Version: 2020.8-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated ostree 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, 22 Nov 2020 13:24:35 +
Source: ostree
Architecture: source
Version: 2020.8-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 975418
Changes:
 ostree (2020.8-2) unstable; urgency=medium
 .
   * d/p/test-pull-summary-sigs-Set-timestamps-to-serve-expected-f.patch:
 Add proposed patch to fix test failures when run on tmpfs
 (Closes: #975418)
Checksums-Sha1:
 7395a586ca7843b15c0da4e3a018bab3d3114b42 3280 ostree_2020.8-2.dsc
 cddb83377aa6bd40d3cd61f7e2f652a9ce994960 26616 ostree_2020.8-2.debian.tar.xz
 e39010c799f26bb4ad5ac33d7b1e03b150760c9b 10269 ostree_2020.8-2_source.buildinfo
Checksums-Sha256:
 6e78c7b1697e087dd2649819cf639ff0e06d7ee99ef234741ea1862a32fe5a09 3280 
ostree_2020.8-2.dsc
 f18bc9bd6559b2c1e15a2a93790207bce9f93d158868164f7896d7d9dfa1a0da 26616 
ostree_2020.8-2.debian.tar.xz
 514af68e960886a2c1c94eaff90164f705efb200371eac6774b5a35f794e2b15 10269 
ostree_2020.8-2_source.buildinfo
Files:
 487bded49d88ad272b7d74b4a397b5e2 3280 admin optional ostree_2020.8-2.dsc
 afd0d16fcb7c263d6079015bdbae58b5 26616 admin optional 
ostree_2020.8-2.debian.tar.xz
 be079033b010674a19d9f806af9226cd 10269 admin optional 
ostree_2020.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl+6ez4ACgkQ4FrhR4+B
TE/q7g/+JhWD8y2TI8ce+oIrOoM0ZCoC50rxSlAQCBlPFAMUpZv/jHW3grKWYxGX
MnCwfvCpspqkZRT7Q+uZQ6pooH6lIfF/pZPv1IdDLn4pvxOR57lR+X63FYJI6OsK
pp2PqFes1tz+jtwPCp/iKZY6k5ikq1EN/ZEEG++Hm3NIbthpTiddqgkoa8PJQgt0
6GtMOTeoV3yLHcj6chW4AcxPtix+Iqlh5h/oZ+ZjJgiN1/SdZR9E3qiUOjCwD2kQ
beHnRparpf6K4AbNq+UAcrPKdVKyfIaU8niZxxesqrvNwh1MyYx3UTpwKkwCICmb
eMdQanOEjlfQ74l27RwrXD7LrFHlSs0+ImzF6THPYR+gHTlyEcOfOPMsROKpo3YP
VmR3A1E45n7rB0UWEYTwPu2sqp/opxxtEpJgNs2FXmMyIJ5k+U6XC5slCAVBueCT
Pm9olpu1bh0yGDpAcx6vekxfslNit+k3QZr91hCI2fCxGk2pptaAGP7s7NX1NzrN
iulv6YIAZOK4N1SVsDAPG04e1qD08y3Xhbiz3Wsc5h10pTRrOYcbmqYajLgOUWXD
jmG6Ud3RHot06/prX/cioy2qQ3K9YjdRNTphS9DbrsNUPCw8eX2iMXCIlehNsgWF
hbdKXvMaZMh2aqeDdthmTBTX90eOhvReimLZz/8J1Vjw6PeQx4A=
=QXd7
-END PGP SIGNATURE End Message ---

Bug#975179: marked as done (kreport: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 15:35:59 +
with message-id 
and subject line Bug#975179: fixed in kreport 3.2.0-2
has caused the Debian Bug report #975179,
regarding kreport: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
975179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kreport
Version: 3.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_missing --fail-missing
> make[1]: Leaving directory '/<>'
>dh_strip
>dh_makeshlibs -Xusr/lib/libkdeinit5_\*
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libkreport3-4/DEBIAN/symbols doesn't match 
> completely debian/libkreport3-4.symbols
> --- debian/libkreport3-4.symbols (libkreport3-4_3.2.0-1_amd64)
> +++ dpkg-gensymbolsLn6r_f 2020-11-19 07:33:08.278861627 +
> @@ -343,9 +343,9 @@
>   _ZN18KReportSectionDataD1Ev@Base 3.1.0
>   _ZN18KReportSectionDataD2Ev@Base 3.1.0
>   
> (optional=templinst)_ZN18QSharedDataPointerIN14KReportElement4DataEE5cloneEv@Base
>  3.0.0
> - _ZN19KReportGroupTracker11qt_metacallEN11QMetaObject4CallEiPPv@Base 3.0.0
> - _ZN19KReportGroupTracker11qt_metacastEPKc@Base 3.0.0
> - _ZN19KReportGroupTracker16staticMetaObjectE@Base 3.0.0
> +#MISSING: 3.2.0-1# 
> _ZN19KReportGroupTracker11qt_metacallEN11QMetaObject4CallEiPPv@Base 3.0.0
> +#MISSING: 3.2.0-1# _ZN19KReportGroupTracker11qt_metacastEPKc@Base 3.0.0
> +#MISSING: 3.2.0-1# _ZN19KReportGroupTracker16staticMetaObjectE@Base 3.0.0
>   _ZN19KReportLabelElementD0Ev@Base 3.0.0
>   _ZN19KReportLabelElementD1Ev@Base 3.0.0
>   _ZN19KReportLabelElementD2Ev@Base 3.0.0
> @@ -691,7 +691,7 @@
>   _ZNK18KReportSectionData6heightEv@Base 3.1.0
>   _ZNK18KReportSectionData7isValidEv@Base 3.1.0
>   _ZNK18KReportSectionData7objectsEv@Base 3.1.0
> - _ZNK19KReportGroupTracker10metaObjectEv@Base 3.0.0
> +#MISSING: 3.2.0-1# _ZNK19KReportGroupTracker10metaObjectEv@Base 3.0.0
>   _ZNK20KReportAsyncItemBase10metaObjectEv@Base 3.0.0
>   _ZNK20KReportAsyncItemBase12realItemDataERK8QVariant@Base 3.1.0
>   _ZNK20KReportPluginManager10metaObjectEv@Base 3.0.0
> @@ -775,7 +775,7 @@
>   _ZTI17KReportDataSource@Base 3.1.0
>   _ZTI18KReportPreRenderer@Base 3.0.0
>   _ZTI18KReportSectionData@Base 3.1.0
> - _ZTI19KReportGroupTracker@Base 3.0.0
> +#MISSING: 3.2.0-1# _ZTI19KReportGroupTracker@Base 3.0.0
>   _ZTI19KReportLabelElement@Base 3.0.0
>   _ZTI19KReportRendererBase@Base 3.0.0
>   _ZTI19KReportScriptSource@Base 3.1.0
> @@ -813,7 +813,7 @@
>   _ZTS17KReportDataSource@Base 3.1.0
>   _ZTS18KReportPreRenderer@Base 3.0.0
>   _ZTS18KReportSectionData@Base 3.1.0
> - _ZTS19KReportGroupTracker@Base 3.0.0
> +#MISSING: 3.2.0-1# _ZTS19KReportGroupTracker@Base 3.0.0
>   _ZTS19KReportLabelElement@Base 3.0.0
>   _ZTS19KReportRendererBase@Base 3.0.0
>   _ZTS19KReportScriptSource@Base 3.1.0
> @@ -850,7 +850,7 @@
>   _ZTV17KReportDataSource@Base 3.1.0
>   _ZTV18KReportPreRenderer@Base 3.0.0
>   _ZTV18KReportSectionData@Base 3.1.0
> - _ZTV19KReportGroupTracker@Base 3.0.0
> +#MISSING: 3.2.0-1# _ZTV19KReportGroupTracker@Base 3.0.0
>   _ZTV19KReportLabelElement@Base 3.0.0
>   _ZTV19KReportRendererBase@Base 3.0.0
>   _ZTV19KReportScriptSource@Base 3.1.0
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:6: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/kreport_3.2.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: kreport
Source-Version: 3.2.0-2
Done: Pino Toscano 

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

Processed: Re: Bug#966708: haskell-ghc-syb-utils: Removal notice: broken and unuseful

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #966708 [src:haskell-ghc-syb-utils] haskell-ghc-syb-utils: Removal notice: 
broken and unuseful
Bug reassigned from package 'src:haskell-ghc-syb-utils' to 'ftp.debian.org'.
No longer marked as found in versions haskell-ghc-syb-utils/0.3.0.0-2.
Ignoring request to alter fixed versions of bug #966708 to the same values 
previously set
> retitle -1 RM: haskell-ghc-syb-utils -- ROM; broken and unuseful
Bug #966708 [ftp.debian.org] haskell-ghc-syb-utils: Removal notice: broken and 
unuseful
Changed Bug title to 'RM: haskell-ghc-syb-utils -- ROM; broken and unuseful' 
from 'haskell-ghc-syb-utils: Removal notice: broken and unuseful'.
> severity -1 normal
Bug #966708 [ftp.debian.org] RM: haskell-ghc-syb-utils -- ROM; broken and 
unuseful
Severity set to 'normal' from 'grave'

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

Bug#966708: haskell-ghc-syb-utils: Removal notice: broken and unuseful

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-ghc-syb-utils -- ROM; broken and unuseful
Control: severity -1 normal

Hi,

Please remove haskell-ghc-syb-utils from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#962961: haskell-gnutls: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962961 [src:haskell-gnutls] haskell-gnutls: Removal notice: broken and 
unmaintained
Bug reassigned from package 'src:haskell-gnutls' to 'ftp.debian.org'.
No longer marked as found in versions haskell-gnutls/0.2-6.
Ignoring request to alter fixed versions of bug #962961 to the same values 
previously set
> retitle -1 RM: haskell-gnutls -- ROM; broken and unmaintained
Bug #962961 [ftp.debian.org] haskell-gnutls: Removal notice: broken and 
unmaintained
Changed Bug title to 'RM: haskell-gnutls -- ROM; broken and unmaintained' from 
'haskell-gnutls: Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #962961 [ftp.debian.org] RM: haskell-gnutls -- ROM; broken and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#962961: haskell-gnutls: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-gnutls -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-gnutls from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#963184: ftphs: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #963184 [src:ftphs] ftphs: Removal notice: broken and unmaintained
Bug reassigned from package 'src:ftphs' to 'ftp.debian.org'.
No longer marked as found in versions ftphs/1.0.9.2-3.
Ignoring request to alter fixed versions of bug #963184 to the same values 
previously set
> retitle -1 RM: ftphs -- ROM; broken and unmaintained
Bug #963184 [ftp.debian.org] ftphs: Removal notice: broken and unmaintained
Changed Bug title to 'RM: ftphs -- ROM; broken and unmaintained' from 'ftphs: 
Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #963184 [ftp.debian.org] RM: ftphs -- ROM; broken and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#963184: ftphs: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: ftphs -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove ftphs from Debian.
It is unmaintained and doesn't work with the latest set of Haskell
libraries.

Thanks,

-- 
Ilias

Processed: Re: Bug#962959: haskell-edison-api: Removal notice: broken and unuseful

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962959 [src:haskell-edison-api] haskell-edison-api: Removal notice: broken 
and unuseful
Bug reassigned from package 'src:haskell-edison-api' to 'ftp.debian.org'.
No longer marked as found in versions haskell-edison-api/1.3.1-5.
Ignoring request to alter fixed versions of bug #962959 to the same values 
previously set
> retitle -1 RM: haskell-edison-api -- ROM; broken and unuseful
Bug #962959 [ftp.debian.org] haskell-edison-api: Removal notice: broken and 
unuseful
Changed Bug title to 'RM: haskell-edison-api -- ROM; broken and unuseful' from 
'haskell-edison-api: Removal notice: broken and unuseful'.
> severity -1 normal
Bug #962959 [ftp.debian.org] RM: haskell-edison-api -- ROM; broken and unuseful
Severity set to 'normal' from 'grave'

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

Bug#962959: haskell-edison-api: Removal notice: broken and unuseful

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-edison-api -- ROM; broken and unuseful
Control: severity -1 normal

Hi,

Please remove haskell-edison-api from Debian.
It is not used in Debian and doesn't work with the latest version of GHC.

Thanks,

-- 
Ilias

Bug#975460: fontforge: FTBFS on i386 [patch]

[Gianfranco Costamagna]

Source: fontforge
Version: 1:20201107~dfsg-1
Severity: serious
tags: patch


Hello, to fix the build failure I think debian/libfontforge4.install should 
contain this line:
usr/lib/${DEB_BUILD_MULTIARCH}

Full patch:

--- fontforge-20201107~dfsg/debian/changelog2020-11-18 09:42:18.0 
+0100
+++ fontforge-20201107~dfsg/debian/changelog2020-11-22 15:24:41.0 
+0100
@@ -1,3 +1,9 @@
+fontforge (1:20201107~dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Fix i386 build (Closes: #-1)
+
+ -- Gianfranco Costamagna   Sun, 22 Nov 2020 
15:24:41 +0100
+
 fontforge (1:20201107~dfsg-1) unstable; urgency=medium
 
   [ Jonas Smedegaard ]
diff -Nru fontforge-20201107~dfsg/debian/libfontforge4.install 
fontforge-20201107~dfsg/debian/libfontforge4.install
--- fontforge-20201107~dfsg/debian/libfontforge4.install2020-11-17 
10:15:18.0 +0100
+++ fontforge-20201107~dfsg/debian/libfontforge4.install2020-11-22 
15:24:40.0 +0100
@@ -1 +1 @@
-usr/lib/${DEB_HOST_GNU_TYPE}
+usr/lib/${DEB_BUILD_MULTIARCH}

Processed: Re: Bug#962958: haskell-edison-core: Removal notice: broken and unuseful

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962958 [src:haskell-edison-core] haskell-edison-core: Removal notice: 
broken and unuseful
Bug reassigned from package 'src:haskell-edison-core' to 'ftp.debian.org'.
No longer marked as found in versions haskell-edison-core/1.3.2.1-3.
Ignoring request to alter fixed versions of bug #962958 to the same values 
previously set
> retitle -1 RM: haskell-edison-core -- ROM; broken and unuseful
Bug #962958 [ftp.debian.org] haskell-edison-core: Removal notice: broken and 
unuseful
Changed Bug title to 'RM: haskell-edison-core -- ROM; broken and unuseful' from 
'haskell-edison-core: Removal notice: broken and unuseful'.
> severity -1 normal
Bug #962958 [ftp.debian.org] RM: haskell-edison-core -- ROM; broken and unuseful
Severity set to 'normal' from 'grave'

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

Processed: Re: lua-http is missing lua-binaryheap dependency

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 974080
Bug #958665 [lua-http] lua-http is missing lua-binaryheap dependency
958665 was not blocked by any bugs.
958665 was not blocking any bugs.
Added blocking bug(s) of 958665: 974080

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

Bug#962958: haskell-edison-core: Removal notice: broken and unuseful

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-edison-core -- ROM; broken and unuseful
Control: severity -1 normal

Hi,

Please remove haskell-edison-core from Debian.
It is not used in Debian, and doesn't work with the latest version of GHC.

Thanks,

-- 
Ilias

Bug#958665: lua-http is missing lua-binaryheap dependency

[Santiago Ruano Rincón]

Control: block -1 by 974080

On Fri, 24 Apr 2020 10:57:40 +0200 Tomas Krizek  wrote:
> Package: lua-http
> Version: 0.3-1
> 
> Upstream lua-http has a dependency on binaryheap >= 0.3.
> See https://github.com/daurnimator/lua-http#dependencies
> 
> The debian package lua-http is missing this dependency, resulting in
> error such as:
> error: /usr/share/lua/5.1/http/cookie.lua:7: module 'binaryheap' not found
> 
> 


signature.asc
Description: PGP signature

Bug#975186: marked as done (kdiagram: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 14:55:58 +
with message-id 
and subject line Bug#975186: fixed in kdiagram 2.7.0-2
has caused the Debian Bug report #975186,
regarding kdiagram: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
975186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kdiagram
Version: 2.7.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_missing --fail-missing
> make[1]: Leaving directory '/<>'
>dh_dwz
>dh_strip
>dh_makeshlibs
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libkchart2/DEBIAN/symbols doesn't match 
> completely debian/libkchart2.symbols
> --- debian/libkchart2.symbols (libkchart2_2.7.0-1_amd64)
> +++ dpkg-gensymbols7tIQ1M 2020-11-19 07:33:51.854485319 +
> @@ -1,8 +1,8 @@
>  libKChart.so.2 libkchart2 #MINVER#
>  * Build-Depends-Package: libkchart-dev
> - _ZN11KChartEnums11qt_metacallEN11QMetaObject4CallEiPPv@Base 2.6.0
> - _ZN11KChartEnums11qt_metacastEPKc@Base 2.6.0
> - _ZN11KChartEnums16staticMetaObjectE@Base 2.6.0
> +#MISSING: 2.7.0-1# 
> _ZN11KChartEnums11qt_metacallEN11QMetaObject4CallEiPPv@Base 2.6.0
> +#MISSING: 2.7.0-1# _ZN11KChartEnums11qt_metacastEPKc@Base 2.6.0
> +#MISSING: 2.7.0-1# _ZN11KChartEnums16staticMetaObjectE@Base 2.6.0
>   _ZN6KChart10BarDiagram10paintEventEP11QPaintEvent@Base 2.6.0
>   _ZN6KChart10BarDiagram11qt_metacallEN11QMetaObject4CallEiPPv@Base 2.6.0
>   _ZN6KChart10BarDiagram11qt_metacastEPKc@Base 2.6.0
> @@ -1277,7 +1277,7 @@
>   _ZN6KChart8TextAreaD0Ev@Base 2.6.0
>   _ZN6KChart8TextAreaD1Ev@Base 2.6.0
>   _ZN6KChart8TextAreaD2Ev@Base 2.6.0
> - _ZNK11KChartEnums10metaObjectEv@Base 2.6.0
> +#MISSING: 2.7.0-1# _ZNK11KChartEnums10metaObjectEv@Base 2.6.0
>   _ZNK6KChart10BarDiagram10metaObjectEv@Base 2.6.0
>   _ZNK6KChart10BarDiagram11orientationEv@Base 2.6.0
>   _ZNK6KChart10BarDiagram13barAttributesERK11QModelIndex@Base 2.6.0
> @@ -1983,7 +1983,7 @@
>   _ZNK6KChart8PositioneqEi@Base 2.6.0
>   _ZNK6KChart8TextArea10metaObjectEv@Base 2.6.0
>   _ZNK6KChart8TextArea12areaGeometryEv@Base 2.6.0
> - _ZTI11KChartEnums@Base 2.6.0
> +#MISSING: 2.7.0-1# _ZTI11KChartEnums@Base 2.6.0
>   _ZTIN6KChart10BarDiagram14BarDiagramTypeE@Base 2.6.0
>   _ZTIN6KChart10BarDiagramE@Base 2.6.0
>   _ZTIN6KChart10PieDiagramE@Base 2.6.0
> @@ -2042,7 +2042,7 @@
>   _ZTIN6KChart7Plotter11PlotterTypeE@Base 2.6.0
>   _ZTIN6KChart7PlotterE@Base 2.6.0
>   _ZTIN6KChart8TextAreaE@Base 2.6.0
> - _ZTS11KChartEnums@Base 2.6.0
> +#MISSING: 2.7.0-1# _ZTS11KChartEnums@Base 2.6.0
>   _ZTSN6KChart10BarDiagram14BarDiagramTypeE@Base 2.6.0
>   _ZTSN6KChart10BarDiagramE@Base 2.6.0
>   _ZTSN6KChart10PieDiagramE@Base 2.6.0
> @@ -2101,7 +2101,7 @@
>   _ZTSN6KChart7Plotter11PlotterTypeE@Base 2.6.0
>   _ZTSN6KChart7PlotterE@Base 2.6.0
>   _ZTSN6KChart8TextAreaE@Base 2.6.0
> - _ZTV11KChartEnums@Base 2.6.0
> +#MISSING: 2.7.0-1# _ZTV11KChartEnums@Base 2.6.0
>   _ZTVN6KChart10BarDiagramE@Base 2.6.0
>   _ZTVN6KChart10PieDiagramE@Base 2.6.0
>   _ZTVN6KChart11LineDiagramE@Base 2.6.0
> dpkg-gensymbols: warning: debian/libkgantt2/DEBIAN/symbols doesn't match 
> completely debian/libkgantt2.symbols
> --- debian/libkgantt2.symbols (libkgantt2_2.7.0-1_amd64)
> +++ dpkg-gensymbolsoViUAh 2020-11-19 07:33:52.102485302 +
> @@ -556,7 +556,7 @@
>   _ZNK6KGantt6Legend7indexAtERK6QPoint@Base 2.6.0
>   _ZNK6KGantt6Legend8drawItemEP8QPainterRK11QModelIndexRK6QPoint@Base 2.6.0
>   _ZNK6KGantt6Legend8sizeHintEv@Base 2.6.0
> - 
> (optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
>  2.6.2
> +#MISSING: 2.7.0-1# 
> (optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
>  2.6.2
>   _ZTIN6KGantt10ProxyModelE@Base 2.6.0
>   _ZTIN6KGantt12AbstractGridE@Base 2.6.0
>   _ZTIN6KGantt12DateTimeGridE@Base 2.6.0
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:6: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/kdiagram_2.7.0-1_unstable.log

A list of current common 

Bug#974108: marked as done (libkf5eventviews: FTBFS with qrand undefined)

[Debian Bug Tracking System]

Your message dated Sun, 22 Nov 2020 14:56:27 +
with message-id 
and subject line Bug#974108: fixed in libkf5eventviews 4:20.08.2-3
has caused the Debian Bug report #974108,
regarding libkf5eventviews: FTBFS with qrand undefined
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.)


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

Hi

some changes in Qt seem to have triggered FTBFS here, as it fails with
/build/libkf5eventviews-20.08.2/src/prefs.cpp: In member function 'void 
EventViews::Prefs::createNewColor(QColor&, int)':
/build/libkf5eventviews-20.08.2/src/prefs.cpp:968:25: error: 'qrand' was not 
declared in this scope; did you mean 'srand'?
  968 | QColor col = QColor(qrand() % 256, qrand() % 256, qrand() % 256);
  | ^
  | srand

qrand is defined in qglobal.h with

/*
  Reentrant versions of basic rand() functions for random number generation
*/
#if QT_DEPRECATED_SINCE(5, 15)
Q_CORE_EXPORT QT_DEPRECATED_VERSION_X_5_15("use QRandomGenerator instead") void 
qsrand(uint seed);
Q_CORE_EXPORT QT_DEPRECATED_VERSION_X_5_15("use QRandomGenerator instead") int 
qrand();
#endif

so it seems that the deprecation has actually disabled the function.

Best

Norbert



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

Kernel: Linux 5.9.6+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libkf5eventviews
Source-Version: 4:20.08.2-3
Done: Pino Toscano 

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated libkf5eventviews package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Nov 2020 15:34:32 +0100
Source: libkf5eventviews
Architecture: source
Version: 4:20.08.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 974108
Changes:
 libkf5eventviews (4:20.08.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Update standards version to 4.5.1, no changes needed.
   * Port stable_abi.patch to QRandomGenerator, so it builds with Qt 5.15.
 (Closes: #974108)
   * Re-export upstream signing key without extra signatures.
Checksums-Sha1:
 4dc877024ca05dfdc94e03fd6e66ab51e7414095 3189 libkf5eventviews_20.08.2-3.dsc
 c1931dbef9921c93742fae1c3a3ddd5726e0d3d5 12652 
libkf5eventviews_20.08.2-3.debian.tar.xz
 7df258882f317e7c7e105265ecc9d8f22cba1c80 16066 
libkf5eventviews_20.08.2-3_source.buildinfo
Checksums-Sha256:
 4f8de3846d0c78a5d9b4f4817d2378882bcbe6349dbc3c874ceb978d2552710e 3189 
libkf5eventviews_20.08.2-3.dsc
 28e17278f98262d280dd5efc14ed30ed4c5a4d2d3a921c74bab79e15637a4589 12652 
libkf5eventviews_20.08.2-3.debian.tar.xz
 9ef35020a80237cbdb9f2d402e3508359c904b2f0f7c583aff38054d259662f3 16066 
libkf5eventviews_20.08.2-3_source.buildinfo
Files:
 2afaf044cbb66eebef5e03c4622c125c 3189 libs optional 
libkf5eventviews_20.08.2-3.dsc
 2930d509385ee334619960ac59e09038 12652 libs optional 
libkf5eventviews_20.08.2-3.debian.tar.xz
 0df7a17d4c0134d59c04e5c020976576 16066 libs optional 
libkf5eventviews_20.08.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl+6dyMACgkQLRkciEOx
P01PsQ//RRURkrrlH7dsZNP5jvafaKJym2qT0dtzfxhlP62bh8HuAKF5vL5heAdD
VRRw+GruWsrNkc76uYS7lhqDeaklT32bYODXAeHQLWyrTTNcO2O0IjpeyYyn12vT

Processed: Re: Bug#964084: haskell-derive: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #964084 [src:haskell-derive] haskell-derive: Removal notice: broken and 
unmaintained
Bug reassigned from package 'src:haskell-derive' to 'ftp.debian.org'.
No longer marked as found in versions haskell-derive/2.6.5-1.
Ignoring request to alter fixed versions of bug #964084 to the same values 
previously set
> retitle -1 RM: haskell-derive -- ROM; broken and unmaintained
Bug #964084 [ftp.debian.org] haskell-derive: Removal notice: broken and 
unmaintained
Changed Bug title to 'RM: haskell-derive -- ROM; broken and unmaintained' from 
'haskell-derive: Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #964084 [ftp.debian.org] RM: haskell-derive -- ROM; broken and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#964084: haskell-derive: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-derive -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-derive from Debian.
It is unmaintained and doesn't work with the latest version of GHC.

Thanks,

-- 
Ilias

Processed: Re: Bug#962955: haskell-crypto-pubkey-openssh: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962955 [src:haskell-crypto-pubkey-openssh] haskell-crypto-pubkey-openssh: 
Removal notice: broken and unmaintained
Bug reassigned from package 'src:haskell-crypto-pubkey-openssh' to 
'ftp.debian.org'.
No longer marked as found in versions haskell-crypto-pubkey-openssh/0.2.7-9.
Ignoring request to alter fixed versions of bug #962955 to the same values 
previously set
> retitle -1 RM: haskell-crypto-pubkey-openssh -- ROM; broken and unmaintained
Bug #962955 [ftp.debian.org] haskell-crypto-pubkey-openssh: Removal notice: 
broken and unmaintained
Changed Bug title to 'RM: haskell-crypto-pubkey-openssh -- ROM; broken and 
unmaintained' from 'haskell-crypto-pubkey-openssh: Removal notice: broken and 
unmaintained'.
> severity -1 normal
Bug #962955 [ftp.debian.org] RM: haskell-crypto-pubkey-openssh -- ROM; broken 
and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#962955: haskell-crypto-pubkey-openssh: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-crypto-pubkey-openssh -- ROM; broken and 
unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-crypto-pubkey-openssh from Debian.
It is unmaintained and doesn't work with the latest version of GHC.

Thanks,

-- 
Ilias

Processed: Re: Bug#962890: haskell-bytestring-show: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #962890 [src:haskell-bytestring-show] haskell-bytestring-show: Removal 
notice: broken and unmaintained
Bug reassigned from package 'src:haskell-bytestring-show' to 'ftp.debian.org'.
No longer marked as found in versions haskell-bytestring-show/0.3.5.6-12.
Ignoring request to alter fixed versions of bug #962890 to the same values 
previously set
> retitle -1 RM: haskell-bytestring-show -- ROM; broken and unmaintained
Bug #962890 [ftp.debian.org] haskell-bytestring-show: Removal notice: broken 
and unmaintained
Changed Bug title to 'RM: haskell-bytestring-show -- ROM; broken and 
unmaintained' from 'haskell-bytestring-show: Removal notice: broken and 
unmaintained'.
> severity -1 normal
Bug #962890 [ftp.debian.org] RM: haskell-bytestring-show -- ROM; broken and 
unmaintained
Severity set to 'normal' from 'grave'

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