Bug#948846: marked as done (sparkleshare: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 08:42:04 +0100
with message-id 

and subject line Re: Bug#948846: sparkleshare: Python2 removal in sid/bullseye
has caused the Debian Bug report #948846,
regarding sparkleshare: 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.)


-- 
948846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sparkleshare
Version: 3.28+git20190525+cf446c0-1
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, in details:

(binary:sparkleshare)Recommends->python
(binary:sparkleshare)Recommends->python-nautilus

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 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 ---
Version: 3.28+git20190525+cf446c0-1

On Mon, 13 Jan 2020 at 23:45, Sandro Tosi  wrote:
>
> Source: sparkleshare
> Version: 3.28+git20190525+cf446c0-1
> 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, in details:
>
> (binary:sparkleshare)Recommends->python
> (binary:sparkleshare)Recommends->python-nautilus
>
> 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

Bug#948849: marked as done (diamond-aligner: missing Breaks+Replaces: diamond)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 07:19:11 +
with message-id 
and subject line Bug#948849: fixed in diamond-aligner 0.9.29+dfsg-4
has caused the Debian Bug report #948849,
regarding diamond-aligner: missing Breaks+Replaces: diamond
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.)


-- 
948849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diamond-aligner
Version: 0.9.29+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../diamond-aligner_0.9.29+dfsg-2_amd64.deb ...
  Unpacking diamond-aligner (0.9.29+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/diamond-aligner_0.9.29+dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/diamond', which is also in package diamond 
4.0.515-5
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/diamond-aligner_0.9.29+dfsg-2_amd64.deb

The diamond package which shipped /usr/bin/diamond in buster no longer
exists in bullseye and sid, thus diamond-aligner is free to take over
the command name, but it needs to ensure that the obsolete package
gets removed.


cheers,

Andreas


diamond=4.0.515-5_diamond-aligner=0.9.29+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: diamond-aligner
Source-Version: 0.9.29+dfsg-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated diamond-aligner package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 08:03:08 +0100
Source: diamond-aligner
Architecture: source
Version: 0.9.29+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 948849
Changes:
 diamond-aligner (0.9.29+dfsg-4) unstable; urgency=medium
 .
   * Breaks+Replaces: diamond
 Closes: #948849
Checksums-Sha1:
 f9df0d93636ad2a4e59bcdd5994e5d48c023196c 2076 diamond-aligner_0.9.29+dfsg-4.dsc
 1c2cd655c9ce7bfde206274fd0ebe4d44dd9dcf5 7580 
diamond-aligner_0.9.29+dfsg-4.debian.tar.xz
 9d9e0425edb4c9fd5905de8e99517adbe1f85231 6888 
diamond-aligner_0.9.29+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 110784c7939fccb90c3fc6cc1f0d133758816b7970db3837027ee2a5fe5a882c 2076 
diamond-aligner_0.9.29+dfsg-4.dsc
 aa7434472e71fa9c2d4f476b4573eeae9406c9918877db6654a5adfabfcd28c3 7580 
diamond-aligner_0.9.29+dfsg-4.debian.tar.xz
 a0936a27dd31e33988c48958a7b90f80a0134fd7586f08e08794f46091acc7fc 6888 
diamond-aligner_0.9.29+dfsg-4_amd64.buildinfo
Files:
 f7e59c373b7a10830603e5798cac25ae 2076 science optional 
diamond-aligner_0.9.29+dfsg-4.dsc
 205582a4ec0b6fee23d893cdb86e7094 7580 science optional 
diamond-aligner_0.9.29+dfsg-4.debian.tar.xz
 0ce4522132c570691dacc0ef3a5a4c40 6888 science optional 
diamond-aligner_0.9.29+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl4daJURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGYEg/7BbG6ArpjSq0e27hhBObaXZVoTN31kclO
aiCh0wyMNuoeFd26BmNmxqnpqawnzb0BB2h27eLPYzzw8D94g71OmulaL1Snovi/
8kFbCZ61puJwCtYzxiI6ijmmzWHYevzbkkYYaVvRIU15g8wdq12vycLIFa9Tn6Jy
BRtrz5f6twEbtrCmX8JYNxc0a5T0bqo5iFel9YOeZwvm+HB5npH3cKJdUskcwbQa
yY1AU50VUYTfVagHL84oPW3gcFY8gWkjorR9fHLiSPPEOXybviFxhGJSPVgq0EmS
BE4zFWgf65+/2T6G+CyhIdrA0SSqtwsNvy+Z5KJ4qSEcd1qVnAo3rm6xPjuPvjOT
At

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 947004
Bug #947004 {Done: Dylan Aïssi } [r-bioc-s4vectors] Tests 
segfaults (since the r-base-core update?)
'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 r-bioc-s4vectors/0.24.1-2.
>
End of message, stopping processing here.

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

Bug#948763: z3: cannot be built on buildds

[Helmut Grohne]

Hi Ximin,

On Mon, Jan 13, 2020 at 08:00:03PM +, Ximin Luo wrote:
> FWIW, when I tried things locally with sbuild, changing dh-python:all to 
> simply dh-python whilst retaining the other annotations *did not work*, 
> regardless of how it's "supposed" to work. That is why I added the extra :all.

This might be a problem with your build environment. Can we move this
part of the z3 bug tracker onto debian-cr...@lists.debian.org? Can you
follow up there with an email describing your steps and including the
full build log that fails when you skip the :all on dh-python? We better
understand what's going on here before bothering the z3 maintainers
further.

I'm not opposed to fixing z3. Just slow down. Understand the issues
involved. Ximin usually is exceptionally fast at fixing cross build
issues in the rust ecosystem, but sometimes an extra round of discussion
helps.

Please keep in mind that these annotations can be harmful. For instance
if you annotate a package :native in 20 other packages and then notice
that you should have marked the annotated package "Multi-Arch: foreign",
you'll observe that you make those 20 other packages FTBFS natively by
adding "Multi-Arch: foreign". We should use these annotations sparingly
and always prefer using Multi-Arch: something if possible. And that's
not always possible.

Helmut

Bug#915209: Info received (perl: FTBFS in the year 2020: cpan/Time-Local/t/Local.t failure)

[Dean Hamstead]

The attached patch is for 5.24.1 old-stable and is derived from 
https://rt.cpan.org/Public/Bug/Display.html?id=124787


Offered under the same license as perl

Perhaps it will help someone



On 2020-01-13 15:15, Debian Bug Tracking System wrote:

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Niko Tyni 

If you wish to submit further information on this problem, please
send it to 915...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.Index: perl-5.24.1/cpan/Time-Local/t/Local.t
===
--- perl-5.24.1.orig/cpan/Time-Local/t/Local.t
+++ perl-5.24.1/cpan/Time-Local/t/Local.t
@@ -91,7 +91,7 @@ for (@time, @neg_time) {
 
 # Test timelocal()
 {
-my $year_in = $year < 70 ? $year + 1900 : $year;
+my $year_in = $year + 1900;
 my $time = timelocal($sec,$min,$hour,$mday,$mon,$year_in);
 
 my($s,$m,$h,$D,$M,$Y) = localtime($time);
@@ -107,7 +107,7 @@ for (@time, @neg_time) {
 
 # Test timegm()
 {
-my $year_in = $year < 70 ? $year + 1900 : $year;
+my $year_in = $year + 1900;
 my $time = timegm($sec,$min,$hour,$mday,$mon,$year_in);
 
 my($s,$m,$h,$D,$M,$Y) = gmtime($time);
@@ -125,7 +125,6 @@ for (@time, @neg_time) {
 
 for (@bad_time) {
 my($year, $mon, $mday, $hour, $min, $sec) = @$_;
-$year -= 1900;
 $mon--;
 
 eval { timegm($sec,$min,$hour,$mday,$mon,$year) };
@@ -134,14 +133,14 @@ for (@bad_time) {
 }
 
 {
-is(timelocal(0,0,1,1,0,90) - timelocal(0,0,0,1,0,90), 3600,
+is(timelocal(0,0,1,1,0,1990) - timelocal(0,0,0,1,0,1990), 3600,
'one hour difference between two calls to timelocal');
 
-is(timelocal(1,2,3,1,0,100) - timelocal(1,2,3,31,11,99), 24 * 3600,
+is(timelocal(1,2,3,1,0,2000) - timelocal(1,2,3,31,11,1999), 24 * 3600,
'one day difference between two calls to timelocal');
 
 # Diff beween Jan 1, 1980 and Mar 1, 1980 = (31 + 29 = 60 days)
-is(timegm(0,0,0, 1, 2, 80) - timegm(0,0,0, 1, 0, 80), 60 * 24 * 3600,
+is(timegm(0,0,0, 1, 2, 1980) - timegm(0,0,0, 1, 0, 1980), 60 * 24 * 3600,
'60 day difference between two calls to timegm');
 }
 

Bug#925708: marked as done (grok: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 04:05:55 +
with message-id 
and subject line Bug#925708: fixed in grok 1.20110708.1-4.4
has caused the Debian Bug report #925708,
regarding grok: 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.)


-- 
925708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grok
Version: 1.20110708.1-4.3
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/grok_1.20110708.1-4.3_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.

[...]
./predicates.c:73: undefined reference to `pcre_compile'
/usr/bin/ld: grok_program.o: in function `grok_collection_init':
./grok_program.c:25: undefined reference to `event_init'
/usr/bin/ld: ./grok_program.c:29: undefined reference to `event_set'
/usr/bin/ld: ./grok_program.c:30: undefined reference to `event_add'
/usr/bin/ld: grok_program.o: in function `grok_collection_check_end_state':
./grok_program.c:59: undefined reference to `event_base_loopexit'
/usr/bin/ld: ./grok_program.c:59: undefined reference to `event_base_loopexit'
/usr/bin/ld: grok_program.o: in function `_collection_sigchld':
./grok_program.c:159: undefined reference to `event_once'
/usr/bin/ld: grok_program.o: in function `grok_collection_loop':
./grok_program.c:168: undefined reference to `event_base_dispatch'
/usr/bin/ld: grok_input.o: in function `_program_file_buferror':
./grok_input.c:204: undefined reference to `event_once'
/usr/bin/ld: grok_input.o: in function `_program_process_stdout_read':
./grok_input.c:134: undefined reference to `bufferevent_get_input'
/usr/bin/ld: ./grok_input.c:134: undefined reference to `evbuffer_readline'
/usr/bin/ld: grok_input.o: in function `_program_file_repair_event':
./grok_input.c:267: undefined reference to `event_once'
/usr/bin/ld: grok_input.o: in function `grok_input_eof_handler':
./grok_input.c:341: undefined reference to `event_once'
/usr/bin/ld: ./grok_input.c:346: undefined reference to `bufferevent_disable'
/usr/bin/ld: ./grok_input.c:331: undefined reference to `bufferevent_disable'
/usr/bin/ld: grok_input.o: in function `grok_program_add_input_process':
./grok_input.c:66: undefined reference to `bufferevent_new'
/usr/bin/ld: ./grok_input.c:68: undefined reference to `bufferevent_enable'
/usr/bin/ld: ./grok_input.c:79: undefined reference to `event_once'
/usr/bin/ld: ./grok_input.c:73: undefined reference to `bufferevent_new'
/usr/bin/ld: ./grok_input.c:75: undefined reference to `bufferevent_enable'
/usr/bin/ld: grok_input.o: in function `grok_program_add_input_file':
./grok_input.c:120: undefined reference to `bufferevent_new'
/usr/bin/ld: ./grok_input.c:122: undefined reference to `bufferevent_enable'
/usr/bin/ld: ./grok_input.c:124: undefined reference to `event_once'
/usr/bin/ld: grok_input.o: in function `_program_file_read_real':
./grok_input.c:308: undefined reference to `event_once'
/usr/bin/ld: grok_matchconf.o: in function `grok_matchconfig_init':
./grok_matchconf.c:23: undefined reference to `tclistnew'
/usr/bin/ld: grok_matchconf.o: in function `grok_matchconfig_close':
./grok_matchconf.c:63: undefined reference to `tclistval'
/usr/bin/ld: ./grok_matchconf.c:61: undefined reference to `tclistnum'
/usr/bin/ld: ./grok_matchconf.c

Bug#948832: marked as done (git: Fix for test failures with python2)

[Debian Bug Tracking System]

Your message dated Tue, 14 Jan 2020 03:34:29 +
with message-id 
and subject line Bug#948832: fixed in git 1:2.25.0-1
has caused the Debian Bug report #948832,
regarding git: Fix for test failures with python2
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.)


-- 
948832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git
Version: 1:2.24.0-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

With the impending removal of /usr/bin/python and the python package in
favor of /usr/bin/python2 (shipped by 'python2'), git will start to fail to
build due to trying to invoke /usr/bin/python in the testsuite.

The attached patch fixes the build failure in Ubuntu, where python has
already been dropped in favor of python2.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru git-2.24.0/debian/control git-2.24.0/debian/control
--- git-2.24.0/debian/control   2019-11-13 03:50:30.0 -0800
+++ git-2.24.0/debian/control   2020-01-13 07:04:49.0 -0800
@@ -7,7 +7,7 @@
  libpcre2-dev | libpcre3-dev,
  libcurl4-gnutls-dev, libexpat1-dev,
  subversion, libsvn-perl, libyaml-perl,
- tcl, python,
+ tcl, python2,
  libhttp-date-perl | libtime-parsedate-perl,
  libcgi-pm-perl,
  liberror-perl,
diff -Nru git-2.24.0/debian/rules git-2.24.0/debian/rules
--- git-2.24.0/debian/rules 2019-11-13 03:50:30.0 -0800
+++ git-2.24.0/debian/rules 2020-01-13 07:04:49.0 -0800
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+export PYTHON_PATH=/usr/bin/python2
 CC =gcc
 CPPFLAGS :=$(shell dpkg-buildflags --get CPPFLAGS)
 CFLAGS :=-Wall $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS)
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.25.0-1

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

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated git package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 02:58:47 +
Source: git
Architecture: source
Version: 1:2.25.0-1
Distribution: unstable
Urgency: low
Maintainer: Gerrit Pape 
Changed-By: Jonathan Nieder 
Closes: 948832
Changes:
 git (1:2.25.0-1) unstable; urgency=low
 .
   * new upstream release (see RelNotes/2.25.0.txt).
   * build against Python 3 (thx Steve Langasek, closes: #948832).
Checksums-Sha1:
 8bde8b68da62f45dcda51a03ce6e8b7df5a3cf59 2892 git_2.25.0-1.dsc
 6ea4b553fbdd9112777902f2f6754439bdc20167 5873532 git_2.25.0.orig.tar.xz
 00703cbc6b75537d86fe4daaa8e64bbbf150a61f 636616 git_2.25.0-1.debian.tar.xz
 c209e69e9dfddaf0a2d1009fd61adbaee2e5cd5d 11862 git_2.25.0-1_amd64.buildinfo
Checksums-Sha256:
 cbf53ce06288ccb2f3a28289d13b60357c2351ae44de23d9ff4256b906ed9433 2892 
git_2.25.0-1.dsc
 c060291a3ffb43d7c99f4aa5c4d37d3751cf6bca683e7344ea407ea504d9a8d0 5873532 
git_2.25.0.orig.tar.xz
 9423dfad358f1ba353df70120024799482743a10d0b2c47228afc2326e1423b9 636616 
git_2.25.0-1.debian.tar.xz
 9251468f1349a04fbfb404f0c814a30e01a8b3d376b4a8def0070628ffdc74a2 11862 
git_2.25.0-1_amd64.buildinfo
Files:
 2e5456dab13616d237e8705369d941c2 2892 vcs optional git_2.25.0-1.dsc
 eab5cdee7c478c0804346d8835e314c9 5873532 vcs optional git_2.25.0.orig.tar.xz
 72d764c75969df5edd044e4bdf36b6da 636616 vcs optional git_2.25.0-1.debian.tar.xz
 21de3aa43b3eb34ba6c2a7860b016819 11862 vcs optional 
git_2.25.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEUh5Y8X6W1xKqD/EC38Zx7rMz+iUFAl4dMuETHGpybmllZGVy
QGdtYWlsLmNvbQAKCRDfxnHuszP6JYwyEACSp7jr8so8aoZxe9QUnrsSmstaDytr
XNz5E3rOqhEwkRAvNHEv0LlgnRwyHa7PPUuuXHVD79p2yI638JCzsEIq/WGuBnBR
Iy2iQmMOAwqK+zVMq54z/CCNGu5F0Wc9sfXMbsEg6BdKnheB9t82qJrHDNCGiTv0
Da1CrV6giK

Bug#925629: aghermann: ftbfs with GCC-9

[andrei zavada]

Gentlemen,

This is the original author of aghermann. First of all, thanks for
take good care of it. My circumstances have changed quite a bit since
I did my last release -- an age ago. In professional capacity, in 2010
I have turned to Erlang and, since around 2014, my proficiency in C++
has been in steady decline. These days, even as I am looking at this
40k LOC of my own code with a faint sense of some grand achievement, I
find myself totally incapable of carrying on with it. Please consider
this as a letter of retirement.

The other day I wanted to cherry-pick Andreas's changes
(https://salsa.debian.org/med-team/aghermann/commit/3cf06970a18219a327fc79a3580d94959ffd7a9a)
into my repo, but it being a mix of useful gtk3 deprecations and a lot
more, along with massive move/rename, I gave up. But all of them were
good.

I am aware of at least one recent paper where the slow-wave sleep
model as used in aghermann is revived and applied in very much the
same way: https://dx.doi.org/10.1093%2Fsleep%2Fzsy079. (It comes from
the lab of Vlad Viazovsky, who happens to be my old acquaintance, even
though we don't keep in touch.) This has largely vindicated my effort,
and it is my hope it can make your maintainership of it in Debian
worth your time.

Again, thanks a lot, and cheers!
Andrei

On Mon, 13 Jan 2020 at 18:35, Andreas Tille  wrote:
>
> Thanks a lot for the very helpful comments, Andreas.
>
> On Mon, Jan 13, 2020 at 07:20:24AM -0800, Matthew Fernandez wrote:
> > > I need to admit that I understand so less from all the gcc issues you
> > > tried to explain - I do not even have any idea what C++ attributes are.
> > > I simply cared for that Debian bug since nobody else did. :-(
> > > So I feel really incompetent to discuss this with gcc maintainers but
> > > I'd welcome if you bring it up there.
> >
> > GCC attributes like the __attribute__ example here are a mechanism for 
> > annotating C/C++ code with things not covered by the ISO standards, but 
> > supported by compiler extensions. Attributes can be applied to many things 
> > including variables and functions, and the function attributes are 
> > documented at https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html 
> > . These days 
> > Clang also understands many of the GCC attributes.
> >
> > The particular one in question here is telling the compiler that the lambda 
> > function being defined has similar behavior to the libc printf function. 
> > The integer parameters say a printf format string appears as the second 
> > argument and the first varargs parameter is the third argument. This looks 
> > off by one, but I think the captured local (&L) counts as the first 
> > parameter. The only thing the compiler uses this attribute for is to detect 
> > calls to this lambda with incorrect arguments and emit warnings for them.
> >
> > The C++11 standard brought in a more commonly supported way of declaring 
> > attributes using square brackets. Unfortunately the standard does not 
> > support many common attributes and you still need to use a “gnu::” prefix 
> > to access the GCC-specific attributes. Hence, “[[gnu::format(printf, 2, 
> > 3)]]” being the C++11 equivalent of this.
> >
> > >> If you need to bypass this urgently, I would recommend deleting the 
> > >> attribute as that particular one is only used to aid the compiler in 
> > >> creating warnings.
> > >
> > > Hmmm, as I said my patch[1] works and I just have the gut feeling (as I
> > > said I have no competence!) that this might be better than to delete the
> > > attribute.  If not would you mind sending an alternative patch which is
> > > better in your opinion?
> >
> > Lambda functions, which are already being used in this code, are a C++11 
> > feature as are this style of attributes. So I imagine it would be 
> > acceptable to upstream to take your patch. Having said that, when I did 
> > this in my experiment code above the compiler warned that it was ignoring 
> > this attribute as it thought it was being applied to the trailing “int”.
> >
> > I re-read the GCC issue and realized I’d misread Jonathan Wakely’s 
> > comments. The issue is actually still open and Jonathan was just noting 
> > that r265787 introduced the bug, not fixed it. So I think what we’re seeing 
> > is consistent with the GCC maintainers’ view.
> >
> > I would suggest proposing your patch upstream. Although its primary purpose 
> > is working around a compiler bug, it’s also an objective improvement in 
> > modernizing the code base.
> >
> > > Thanks again
> > >
> > >   Andreas.
> > >
> > >
> > >>  [0]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90333 
> > >> 
> > >
> > > [1] 
> > > https://salsa.debian.org/med-team/aghermann/blob/master/debian/patches/workaround_gcc-9_issue.patch
> > >  
> > > 

Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye

[Drew Parsons]

On 2020-01-14 02:13, Sandro Tosi wrote:

>It's just that there is no extra effort required in this case.
>python3-scipy does indeed need the effort taken, but once that effort
>is
>done, it's no more effort to apply the same fix to python-scipy.  So
>yes, please do focus on fixing python3-scipy! :)

Yes, maybe so, but delaying the python2-rm blocks other work and thus 
delays and complicates getting that major effort completed.  Let's 
not.


exactly, i really dont understand what's the value of fixing something
that's gonna be removed anyway.

I think i'm just gonna wait a couple more days and then file a RM


Fair enough then.  I'm out-voted :)

Bug#948859: coccinelle: Package is uninstallable

[Benjamin Poirier]

Source: coccinelle
Version: 1.0.4.deb-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The coccinelle package has been uninstallable for many weeks in unstable:

root@f3:~# apt install coccinelle
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 coccinelle : Depends: libpcre-ocaml-2h5n2 but it is not installable
  Depends: ocaml-base-nox-4.05.0 but it is not installable
E: Unable to correct problems, you have held broken packages.

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

Kernel: Linux 5.4.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: 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 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: found 948756 in 1.13-1.1, tagging 948756, notfound 948777 in viking, found 948777 in 1.7-1 ...

[Debian Bug Tracking System]

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

> found 948756 1.13-1.1
Bug #948756 [src:scgi] scgi: should this package be removed?
Marked as found in versions scgi/1.13-1.1.
> tags 948756 + sid bullseye
Bug #948756 [src:scgi] scgi: should this package be removed?
Added tag(s) bullseye and sid.
> notfound 948777 viking
Bug #948777 [src:viking] viking: FTBFS error: incompatible types when 
initializing type 'time_t'
The source 'viking' and version 'viking' do not appear to match any binary 
packages
No longer marked as found in versions viking/viking.
> found 948777 1.7-1
Bug #948777 [src:viking] viking: FTBFS error: incompatible types when 
initializing type 'time_t'
Marked as found in versions viking/1.7-1.
> tags 948777 + sid bullseye
Bug #948777 [src:viking] viking: FTBFS error: incompatible types when 
initializing type 'time_t'
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: Re: gfortran-9 causes libcgns FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944127 {Done: Gilles Filippini } [src:libcgns] gfortran-9 
causes libcgns FTBFS on ppc64el
Added tag(s) pending.

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

Bug#944127: gfortran-9 causes libcgns FTBFS on ppc64el

[Andreas Beckmann]

Followup-For: Bug #944127
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948857


Andreas

Bug#940485: git-lfs: FTBFS: tests fail

[Stephen Gelman]

Ah good catch, thanks for that!

On Mon, Jan 13, 2020 at 5:45 PM Andreas Beckmann  wrote:
>
> Followup-For: Bug #940485
> Control: tag -1 pending
>
> buster-pu request: https://bugs.debian.org/948854
>
>
> Andreas
>

Bug#940485: git-lfs: FTBFS: tests fail

[Andreas Beckmann]

Followup-For: Bug #940485
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948854


Andreas

Processed: Re: git-lfs: FTBFS: tests fail

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #940485 {Done: Stephen Gelman } [git-lfs] git-lfs: 
FTBFS: tests fail
Added tag(s) pending.

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

Processed: py2removal bugs severity updates - 2020-01-13 23:36:04.606558+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # sparkleshare is an application, has low popcon (93 < 300), and has 0 
> external rdeps or not in testing
> severity 948846 serious
Bug #948846 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # hgsubversion is an application, has low popcon (59 < 300), and has 0 
> external rdeps or not in testing
> severity 948847 serious
Bug #948847 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#948763: marked as done (cannot migrate to testing)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 23:20:52 +
with message-id 
and subject line Bug#948763: fixed in z3 4.8.7-4
has caused the Debian Bug report #948763,
regarding cannot migrate to testing
to be marked as done.

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

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


-- 
948763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: z3
Version: 4.8.7-3
Severity: serious

z3 cannot be built on buildds, because its Build-Depends cannot be
satisfied on buildds. Failing to build on buildds is a serious problem.

| Build-Depends: debhelper-compat (= 12),
|dh-python:all, python3:native, cmake,

dh-python:all is broken. This is why dose-builddebcheck rejects your
package. dh-python is Multi-Arch: foreign and does not need any
annotation.

python3:native is correct in principle. The python ecosystem more
commonly uses python3:any though. dh-python parses the Build-Depends and
I'm not sure that the dh-python parser understands :native today. I
suggest that you prefer :any for python interpreter dependencies in
general.

|javahelper:all [!hppa !hurd-i386 !m68k !sh4],

Just like python:all this is broken. We don't support cross building
java stuff yet. If you want to get there, get in touch with
debian-cr...@lists.debian.org. This needs more work on the lower layers.

If you want to cross build z3 without the java bindings, please use the
 build profile.

|default-jdk:native [!hppa !hurd-i386 !m68k !sh4]

This can work, but when you switch the development kit to native, you
need to explicitly depend on the runtime environment for the host
architecture. That'd be default-jre-headless without :native.
Unfortunately, doing so presently produces a conflict.

Helmut
--- End Message ---
--- Begin Message ---
Source: z3
Source-Version: 4.8.7-4

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

Debian distribution maintenance software
pp.
Fabian Wolff  (supplier of updated z3 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, 13 Jan 2020 22:55:52 +0100
Source: z3
Architecture: source
Version: 4.8.7-4
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Fabian Wolff 
Closes: 948763
Changes:
 z3 (4.8.7-4) unstable; urgency=medium
 .
   * Remove all :all and :native annotations from the build dependencies in
 debian/control (Closes: #948763).
Checksums-Sha1:
 fda15b4cb8c96fc05bae9815c1b9172b27f6b5a5 2545 z3_4.8.7-4.dsc
 236b748b34905138dbb5ca2462a1b915cf9ce784 10008 z3_4.8.7-4.debian.tar.xz
 82b3e4647ed6a3f1bc3a35ed776a9e910f982981 12909 z3_4.8.7-4_amd64.buildinfo
Checksums-Sha256:
 d8e4880a01c5a5b4f566e41aab794bbee785120aa112ab3a673d1034fde77c2e 2545 
z3_4.8.7-4.dsc
 ce9f3960b1ac480dc0e3ca5a54e9d6d8de32efd6b62f9e6114e927bb5da4b7cc 10008 
z3_4.8.7-4.debian.tar.xz
 a51c66982a953fb1e42a40334754082698f844487f84a218962aa70b2d191d96 12909 
z3_4.8.7-4_amd64.buildinfo
Files:
 445d279b6226524822998d6b6c143c58 2545 science optional z3_4.8.7-4.dsc
 869a74f13349dfcb4c89b49fe48b639e 10008 science optional 
z3_4.8.7-4.debian.tar.xz
 8045b623d23d4220999d975204229e36 12909 science optional 
z3_4.8.7-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEGKeQdgwAi1CfzfenilOItk1pK0kFAl4c92IACgkQilOItk1p
K0lFZA//d0SYhYAy6dKutXSDU1XtCvlokgkT5/A38kdscgVVnDPzG9VW7TazqPfT
fX25smXV13twvSCQ6PpQi/yBNu/IIXg70XWePBClFcS+q164EbDVg8kkCogJcQsp
SjL43h0odaJv6qg2syqiccukvKMgPAinY9rW27KOd11BZV8Y8Y5xUYgkr4oKPHNn
dVlrsFUyUtmYILMGor35E1X1oP0ZDIpKCicjdWVJd/ytlN74XHToE6gX6yPX/hj3
T4uHCZbP8hu8tkLhhMg7XdrWFX9ido1M1WaFkLGk1NFHI/LMT6EK6m14dQ24TVkL
hfO4Rl/Me0o34QwVGIXt1GbHuXrXaiV+oqRhhe9tbljqO8zRU4+vMC3GIacrSohx
Woxg56K7dZx03l7dzgQyqBnItI6y5tXS4fYmXv6DVmDAa5PwxCUoIQxOwe9DOjjd
3MQxBF4pzLGFObWM9OxryI8M3VMhq04HWXMu5X6uZ3pffiabQhjpCgXJxiaBUWqG
6VX2l+//AIHsb3wd/bQtwc+7Yjh/HCA2335TyOo9Z3d0/MgHjL5hv2bd2N3gv26/
A2xzo5mimh9CFVvagVVsa8Nth+ZC6oP2eWihcPc5EjKuoEeyclbkbIyy8j6uj1Vk
lfyEM+EcM8MRo1DIWhz7BBFuQFZmMUCoaHOZPmPAaekGIptaO1U=
=XjAO
-END PGP SIGNATURE--

Bug#933057: csh: bsd-csh eval command always dies with segmentation fault

[Andreas Beckmann]

Followup-For: Bug #933057
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948850


Andreas

Processed: Re: csh: bsd-csh eval command always dies with segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933057 {Done: Alastair McKinstry } [csh] csh: 
bsd-csh eval command always dies with segmentation fault
Added tag(s) pending.

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

Bug#948783: marked as done (gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 22:54:24 +
with message-id 
and subject line Bug#948783: fixed in gambas3 3.14.2-2
has caused the Debian Bug report #948783,
regarding gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this 
function)
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.)


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

Dear maintainer,

your package failed to rebuild in a standard sid chroot

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/postgresql/ 
-I/usr/include/postgresql/12/server/ 
-I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2 
-pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os -g 
-O2 -ffile-prefix-map=/build/1st/gambas3-3.13.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c main.c  -fPIC -DPIC -o 
.libs/gb_db_postgresql_la-main.o
main.c: In function 'conv_type':
main.c:338:8: error: 'ABSTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  338 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:338:8: note: each undeclared identifier is reported only once for each 
function it appears in
main.c:339:8: error: 'RELTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  339 |   case RELTIMEOID:
  |^~
  |TIMEOID
main.c: In function 'conv_data':
main.c:421:8: error: 'ABSTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  421 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:422:8: error: 'RELTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  422 |   case RELTIMEOID:
  |^~
  |TIMEOID
make[5]: *** [Makefile:496: gb_db_postgresql_la-main.lo] Error 1
make[5]: Leaving directory '/build/1st/gambas3-3.13.0/gb.db.postgresql/src'
make[4]: *** [Makefile:438: all-recursive] Error 1
make[4]: Leaving directory '/build/1st/gambas3-3.13.0/gb.db.postgresql'
make[3]: *** [Makefile:370: all] Error 2
make[3]: Leaving directory '/build/1st/gambas3-3.13.0/gb.db.postgresql'
make[2]: *** [Makefile:437: all-recursive] Error 1
make[2]: Leaving directory '/build/1st/gambas3-3.13.0'
make[1]: *** [Makefile:378: all] Error 2
make[1]: Leaving directory '/build/1st/gambas3-3.13.0'
dh_auto_build: make -j16 returned exit code 2
make: *** [debian/rules:9: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gambas3
Source-Version: 3.14.2-2

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated gambas3 
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, 13 Jan 2020 23:10:27 +0100
Source: gambas3
Architecture: source
Version: 3.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Gambas Team 
Changed-By: Bastian Germann 
Closes: 948783
Changes:
 gambas3 (3.14.2-2) unstable; urgency=medium
 .
   * Source-only reupload (Closes: #948783)
Checksums-Sha1:
 2a4e0071f89a020fd163a09f6bf1d4ec58c8ec4f 9956 gambas3_3.14.2-2.dsc
 c79126f4540c7e6f75d2bac272e55a00047c2596 27744 gambas3_3.14.2-2.debian.tar.xz
 7a92b728387549e6c832dc18f014531cac5a04ea 23895 
gambas3_3.14.2-2_source.buildinfo
Checksums-Sha256:
 e46e32c8c5da2dd8c20eda442d8a209f5f8d069a8ee611ba42f0e0ca191024a6 9956 
gambas3_3.14.2-2.dsc
 7eb8d9007c482d3bff9d7a6a6dc60dbb20bab43fc8457d48

Bug#948529: marked as done (looking-glass ftbfs with binutils 2.33.50)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 22:54:43 +
with message-id 
and subject line Bug#948529: fixed in looking-glass 0+b1-2
has caused the Debian Bug report #948529,
regarding looking-glass ftbfs with binutils 2.33.50
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.)


-- 
948529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:looking-glass
Version: 0+b1-1
Severity: serious
Tags: sid bullseye

Please fix that, plus link with the static library and add a Built-Using: tag.


[...]
/<>/looking-glass-0+b1/common/src/crash.linux.c: In function
‘lookup_address’:
/<>/looking-glass-0+b1/common/src/crash.linux.c:101:8: error: implicit
declaration of function ‘bfd_get_section_flags’; did you mean
‘bfd_set_section_flags’? [-Werror=implicit-function-declaration]
  101 |   if ((bfd_get_section_flags(crash.fd, crash.section) & SEC_ALLOC) == 0)
  |^
  |bfd_set_section_flags
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors
make[3]: *** [common/CMakeFiles/lg_common.dir/build.make:105:
common/CMakeFiles/lg_common.dir/src/crash.linux.c.o] Error 1
make[3]: *** Waiting for unfinished jobs
--- End Message ---
--- Begin Message ---
Source: looking-glass
Source-Version: 0+b1-2

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

Debian distribution maintenance software
pp.
Lennart Weller  (supplier of updated looking-glass 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, 13 Jan 2020 00:31:47 +0100
Source: looking-glass
Binary: looking-glass-client looking-glass-client-dbgsym
Architecture: source amd64
Version: 0+b1-2
Distribution: unstable
Urgency: medium
Maintainer: Lennart Weller 
Changed-By: Lennart Weller 
Description:
 looking-glass-client - Low latency KVM FrameRelay implementation for VGA 
Passthrough
Closes: 948529
Changes:
 looking-glass (0+b1-2) unstable; urgency=medium
 .
   * Fix FTBFS Bug with binutils 2.33 (Closes: #948529)
Checksums-Sha1:
 e3f2c274a395d162d028adc8ac82d7ea5f00139a 2038 looking-glass_0+b1-2.dsc
 3854631c9d6b6b2884917d9bd7b7698d5b2f663f 5660 
looking-glass_0+b1-2.debian.tar.xz
 aaf7e0064697bdadf8b3dd1b0ebca6f6a1e780d8 213508 
looking-glass-client-dbgsym_0+b1-2_amd64.deb
 37fc0da305d9c0d16608d4bc3a80a7b90904a078 66692 
looking-glass-client_0+b1-2_amd64.deb
 9bda243f00ba383d1f1a7027eaba8b8d0f52e668 12121 
looking-glass_0+b1-2_amd64.buildinfo
Checksums-Sha256:
 531ec0b6a8a78b413f11283b242620647a5fe758965cf30808bd9bbc6b88b8d4 2038 
looking-glass_0+b1-2.dsc
 3def2aabeb5640a46eee610de56c968febad2a73e6055c7df470cff34875311d 5660 
looking-glass_0+b1-2.debian.tar.xz
 84c4c5b1744d7741b06790bb2f956e777bd1b03bb38c1a1ada8fe6bd3fb9bf7f 213508 
looking-glass-client-dbgsym_0+b1-2_amd64.deb
 56f8ea54854cf6788bd21e4ecd1b46efa2317a9ce0e135cdec8887d6ece5d630 66692 
looking-glass-client_0+b1-2_amd64.deb
 3d9c3f860a4190106945ee6e3caf29994f4b27a40575d1cc612286c58ae89fc7 12121 
looking-glass_0+b1-2_amd64.buildinfo
Files:
 ca8c7f2549245d619ca335ae0542b020 2038 net optional looking-glass_0+b1-2.dsc
 eb889727f53d4ae92dc839fae6e6082e 5660 net optional 
looking-glass_0+b1-2.debian.tar.xz
 88978d3ab1e94ad8c2f64c2703ea42ad 213508 debug optional 
looking-glass-client-dbgsym_0+b1-2_amd64.deb
 6e6ad5e831bc7b10923244155d0efebb 66692 net optional 
looking-glass-client_0+b1-2_amd64.deb
 859b73e0099e97f49da48cf3132c72f7 12121 net optional 
looking-glass_0+b1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJBBAEBCgArFiEERF1NBzmGgbU+WCnwLH/PgPT3bEMFAl4c8AANHGxod0ByaW5n
MC5kZQAKCRAsf8+A9PdsQ6r8D/9KAP6pMAFG0soiRCdIS5G86ECaUGabCttsXRlr
c/a0tlA19DDeaVLzsztH/+cf3b8gVQJmu+dOvqOX7xy1RmrrM+ik7/otFwmh6+Tp
p0wSAlMqmxso4Ci4qCkjEnwokpZGomJevvKl+27a8NitMyXzU0d1i+5CwEP+0rUc
Vpun8lIQ5I5OcPUEz4AioifFlimKKeUmhVe7gKZFtD83qI+qNCOt/QGPawM9ekeZ
2yQhFKwZUuJNcndi5oGlE1e4eFumXSX1VyFAAbyQOKGWQ10PtWIEKwaO9nADRnUW
6n1E+TfaNk+xelO2MsXVVnh1Kb3JAiW+GJF+LiudLC8Rg3e56kRcZlezx1L79mKu
vP86cC1iX8LrM4h21rf+fzNn4eB

Bug#948849: diamond-aligner: missing Breaks+Replaces: diamond

[Andreas Beckmann]

Package: diamond-aligner
Version: 0.9.29+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../diamond-aligner_0.9.29+dfsg-2_amd64.deb ...
  Unpacking diamond-aligner (0.9.29+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/diamond-aligner_0.9.29+dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/diamond', which is also in package diamond 
4.0.515-5
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/diamond-aligner_0.9.29+dfsg-2_amd64.deb

The diamond package which shipped /usr/bin/diamond in buster no longer
exists in bullseye and sid, thus diamond-aligner is free to take over
the command name, but it needs to ensure that the obsolete package
gets removed.


cheers,

Andreas


diamond=4.0.515-5_diamond-aligner=0.9.29+dfsg-2.log.gz
Description: application/gzip

Processed: Re: Bug#948840: systemd: FTBFS: meson.build:1036:8: ERROR: Could not generate cargs for libiptc:

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libip4tc-dev 1.8.4-1
Bug #948840 [src:systemd] systemd: FTBFS: meson.build:1036:8: ERROR: Could not 
generate cargs for libiptc:
Bug reassigned from package 'src:systemd' to 'libip4tc-dev'.
No longer marked as found in versions systemd/244-3.
Ignoring request to alter fixed versions of bug #948840 to the same values 
previously set
Bug #948840 [libip4tc-dev] systemd: FTBFS: meson.build:1036:8: ERROR: Could not 
generate cargs for libiptc:
Marked as found in versions iptables/1.8.4-1.
> forcemerge 947176 -1
Bug #947176 [libip4tc-dev] libiptc.pc non-functional
Bug #947176 [libip4tc-dev] libiptc.pc non-functional
Added tag(s) ftbfs.
Bug #948840 [libip4tc-dev] systemd: FTBFS: meson.build:1036:8: ERROR: Could not 
generate cargs for libiptc:
Added indication that 948840 affects src:systemd
Merged 947176 948840

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

Bug#948840: systemd: FTBFS: meson.build:1036:8: ERROR: Could not generate cargs for libiptc:

[Michael Biebl]

Control: reassign -1 libip4tc-dev 1.8.4-1
Control: forcemerge 947176 -1

Hi Mattia,

this is duplicate of #947176, so merging accordingly.



signature.asc
Description: OpenPGP digital signature

Bug#948845: python-pastescript-doc: missing Breaks+Replaces: python-pastescript

[Andreas Beckmann]

Package: python-pastescript-doc
Version: 2.0.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../python-pastescript-doc_2.0.2-3_all.deb ...
  Unpacking python-pastescript-doc (2.0.2-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pastescript-doc_2.0.2-3_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/paster.1.gz', which is also in 
package python-pastescript 2.0.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pastescript-doc_2.0.2-3_all.deb

Was it intentional to move the manpage from python-pastescript
to python-pastescript-doc instead of python3-pastescript?


cheers,

Andreas


python-pastescript=2.0.2-2_python-pastescript-doc=2.0.2-3.log.gz
Description: application/gzip

Bug#947441: marked as done (libignition-cmake2-dev: file conflicts with libignition-cmake-dev: /usr/share/ignition/ignition-cmake0/doxygen/*)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 22:05:31 +
with message-id 
and subject line Bug#947441: fixed in ignition-cmake2 2.1.1+dfsg-3
has caused the Debian Bug report #947441,
regarding libignition-cmake2-dev: file conflicts with libignition-cmake-dev: 
/usr/share/ignition/ignition-cmake0/doxygen/*
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.)


-- 
947441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libignition-cmake2-dev
Version: 2.1.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libignition-cmake2-dev_2.1.1+dfsg-2_amd64.deb ...
  Unpacking libignition-cmake2-dev:amd64 (2.1.1+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libignition-cmake2-dev_2.1.1+dfsg-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/ignition/ignition-cmake0/doxygen/doxygen.css', which is also in 
package libignition-cmake-dev:amd64 0.6.1-1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libignition-cmake2-dev_2.1.1+dfsg-2_amd64.deb

The following files are shipped by both packages:

  usr/share/ignition/ignition-cmake0/doxygen/doxygen.css
  usr/share/ignition/ignition-cmake0/doxygen/dynsections.js
  usr/share/ignition/ignition-cmake0/doxygen/google_material_icons.css
  usr/share/ignition/ignition-cmake0/doxygen/ignition_logo.svg
  usr/share/ignition/ignition-cmake0/doxygen/ignition_logo_white.svg
  usr/share/ignition/ignition-cmake0/doxygen/material.deep_orange-blue.min.css
  usr/share/ignition/ignition-cmake0/doxygen/material.js

You either need to move them to a different location or add
Breaks+Replaces.


cheers,

Andreas


libignition-cmake-dev=0.6.1-1+b1_libignition-cmake2-dev=2.1.1+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ignition-cmake2
Source-Version: 2.1.1+dfsg-3

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated 
ignition-cmake2 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: Fri, 10 Jan 2020 15:52:30 +
Source: ignition-cmake2
Architecture: source
Version: 2.1.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Closes: 947441
Changes:
 ignition-cmake2 (2.1.1+dfsg-3) unstable; urgency=medium
 .
   * Fix install file. Closes: #947441
Checksums-Sha1:
 1275d2b878d6cbcaa304058fcd55fa0072f93a1a 1892 ignition-cmake2_2.1.1+dfsg-3.dsc
 22e68606a2f375747db0079ff2a8ee521da53910 68256 
ignition-cmake2_2.1.1+dfsg-3.debian.tar.xz
 c3aa8ca786470d2108f6ebe2adaf1e809ada84ab 7091 
ignition-cmake2_2.1.1+dfsg-3_source.buildinfo
Checksums-Sha256:
 9b10b7c599c537cda78dbef74785cad3e0370f0d79e7d9d3d2e67c0f839457b8 1892 
ignition-cmake2_2.1.1+dfsg-3.dsc
 46907e6f67b71dfbca4dff7d8cf2937163c33c5ea5bf6a13c3bce9d788f14f44 68256 
ignition-cmake2_2.1.1+dfsg-3.debian.tar.xz
 f5095f6b404e8f7c5f821a076560b05bf894a4674a70602f286f0a7157cedaaa 7091 
ignition-cmake2_2.1.1+dfsg-3_source.buildinfo
Files:
 105a8333fe5d96c2c807b25d8e67b41d 1892 science optional 
ignition-cmake2_2.1.1+dfsg-3.dsc
 15e68e84f2509f6c96b98afd637ddbcd 68256 science optional 
ignition-cmake2_2.1.1+dfsg-3.debian.tar.xz
 def20a54d8260196c63cc40984eb934c 7091 science optional 
ignition-cmake2_2.1.1+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFOBAEBCgA4FiEEoIFhu+wcwGOWFFkDXpRsCQr/BCcFAl4c5LYaHGpyaXZlcm9A
b3NyZm91bmRhdGlvbi5vcmcACgkQXpRsCQr/BCfcLgf/WLyGwFTy29cKp9Pe54N

Bug#948763: z3: cannot be built on buildds

[Ximin Luo]

Helmut Grohne:
> Control: retitle -1 cannot migrate to testing
> 
> Hi Fabian,
> 
> On Mon, Jan 13, 2020 at 04:27:15PM +0100, Fabian Wolff wrote:
>> On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne  wrote:
>>> Source: z3
>>> Version: 4.8.7-3
>>> Severity: serious
>>>
>>> z3 cannot be built on buildds, because its Build-Depends cannot be
>>> satisfied on buildds. Failing to build on buildds is a serious problem.
>>
>> It builds now on all but three architectures, including, in particular, all
>> release architectures.
> 
> Oh, I'm wrong here. It did build. But the dependency issue prevents it
> from migrating to testing. So you want to fix that anyway.
> 

Why is testing migration prevented, when the builds completed fine? Why is 
there a "dependency issue" when clearly the dependencies were satisfied?

>> Thanks for your suggestions, but I'm not very familiar with how Multi-Arch
>> annotations should be used; I just accepted a patch to make the z3 package
>> more cross-build friendly (see #948109).
> 
> That bug is not at all about cross building nor multi-arch. It seems you
> (and your contributors) are conflating multiple issues. Things become
> much easier once you start separating them.
> 
>> Can you give me a patch where you set the build dependency annotations in a
>> sound way that also works for cross-building? Otherwise, I would have to
>> simply remove all annotations again in order to fix this bug (but clearly,
>> that would not be the most desirable solution).
> 
> No. The expectation that every package can be cross built is misguided.
> z3 uses java stuff, which is an unsolved problem. Therefore you cannot
> make z3's dependencies cross-satisfiable at this time. If you want to do
> so anyway, be prepared to invest quite some work.
> 
> For this reason, reverting the annotations is not the worst of options.
> 

The sbuild command-line I gave near the end of #948109 works perfectly fine to 
cross-compile java bindings and the files have the correct binary format (for 
the foreign architecture).

Granted, I didn't actually run the bindings, but I don't see why they wouldn't 
work.

I can understand that, based on what your expectations are of the current tool 
chain you believe it shouldn't work, but *I actually tried it empirically and 
it works*.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#948841: openpyxl fails almost all its tests

[Matthias Klose]

Package: src:openpyxl
Version: 2.4.9-1
Severity: serious
Tags: sid bullseye

openpyxl fails almost all its tests, when building in unstable:

[...]
LC_ALL=C.UTF-8 python2.7 /usr/bin/py.test openpyxl
= test session starts ==
platform linux2 -- Python 2.7.17, pytest-4.6.8, py-1.8.0, pluggy-0.13.0
rootdir: /<>, inifile: pytest.ini
collected 1829 items

openpyxl/cell/tests/test_cell.py EEE [  2%]
EEE  [  4%]
openpyxl/cell/tests/test_read_only.py    [  5%]
openpyxl/cell/tests/test_text.py [  6%]
openpyxl/chart/tests/test_area_chart.py E[  6%]
openpyxl/chart/tests/test_axis.py EEE[  7%]
openpyxl/chart/tests/test_bar_chart.py EE[  7%]
openpyxl/chart/tests/test_bubble_chart.py EE [  7%]
openpyxl/chart/tests/test_chart.py EE[  8%]
openpyxl/chart/tests/test_chartspace.py  [  9%]
openpyxl/chart/tests/test_data_source.py [ 10%]
openpyxl/chart/tests/test_error_bar.py EE[ 10%]
openpyxl/chart/tests/test_label.py   [ 10%]
openpyxl/chart/tests/test_layout.py EEE  [ 10%]
openpyxl/chart/tests/test_legend.py  [ 10%]
openpyxl/chart/tests/test_line_chart.py  [ 10%]
openpyxl/chart/tests/test_marker.py  [ 11%]
openpyxl/chart/tests/test_picture.py EE  [ 11%]
openpyxl/chart/tests/test_pie_chart.py E [ 11%]
openpyxl/chart/tests/test_print.py   [ 12%]
openpyxl/chart/tests/test_radar_chart.py EE  [ 12%]
openpyxl/chart/tests/test_reader.py E[ 12%]
openpyxl/chart/tests/test_reference.py   [ 12%]
openpyxl/chart/tests/test_scatter_chart.py EE[ 12%]
openpyxl/chart/tests/test_series.py E[ 13%]
openpyxl/chart/tests/test_series_factory.py EEE  [ 13%]
openpyxl/chart/tests/test_shapes.py EE   [ 13%]
openpyxl/chart/tests/test_stock_chart.py EE  [ 14%]
openpyxl/chart/tests/test_surface_chart.py   [ 14%]
openpyxl/chart/tests/test_text.py EE [ 14%]
openpyxl/chart/tests/test_title.py EEE   [ 14%]
openpyxl/chart/tests/test_trendline.py   [ 14%]
openpyxl/chart/tests/test_updown_bars.py EE  [ 15%]
openpyxl/chartsheet/tests/test_chartsheet.py [ 15%]
openpyxl/chartsheet/tests/test_custom.py [ 15%]
openpyxl/chartsheet/tests/test_properties.py EE  [ 15%]
openpyxl/chartsheet/tests/test_protection.py EEE [ 15%]
openpyxl/chartsheet/tests/test_publish.py    [ 16%]
openpyxl/chartsheet/tests/test_relation.py   [ 16%]
openpyxl/chartsheet/tests/test_views.py  [ 16%]
openpyxl/comments/tests/test_author.py EE[ 16%]
openpyxl/comments/tests/test_comment.py  [ 16%]
openpyxl/comments/tests/test_comment_reader.py EEE   [ 16%]
openpyxl/comments/tests/test_comment_sheet.py EE [ 17%]
openpyxl/comments/tests/test_shape_writer.py EEE [ 17%]
openpyxl/compat/tests/test_compat.py [ 18%]
openpyxl/descriptors/tests/test_base.py  [ 19%]
 [ 20%]
openpyxl/descriptors/tests/test_excel.py EE  [ 22%]
openpyxl/descriptors/tests/test_namespace.py EEE [ 22%]
openpyxl/descriptors/tests/test_nested.py E  [ 23%]
openpyxl/descriptors/tests/test_sequence.py EEE  [ 24%]
openpyxl/descriptors/tests/test_serialisable.py  [ 25%]
openpyxl/develop/tests/test_classify.py EEE  [ 25%]
openpyxl/drawing/tests/test_color.py EE  [ 26%]
openpyxl/drawing/tests/test_descriptors.py E [ 26%]
openpyxl/drawing/tests/test_drawing.py E [ 26%]
openpyxl/drawing/tests/test_fil

Bug#947162: marked as done (curry-frontend: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 21:49:23 +
with message-id 
and subject line Bug#947162: fixed in curry-frontend 1.0.4-3
has caused the Debian Bug report #947162,
regarding curry-frontend: FTBFS in sid
to be marked as done.

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

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


-- 
947162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: curry-frontend
Version: 1.0.4-2
Severity: serious

Hello, your package FTBFS everywhere, due to new curry and ghc refusing to 
create an empty documentation package...

Can you please have a look?

thanks

G.
--- End Message ---
--- Begin Message ---
Source: curry-frontend
Source-Version: 1.0.4-3

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated curry-frontend 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: Thu, 02 Jan 2020 13:40:52 +0100
Source: curry-frontend
Architecture: source
Version: 1.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Curry Maintainers 

Changed-By: Mike Gabriel 
Closes: 947162
Changes:
 curry-frontend (1.0.4-3) unstable; urgency=medium
 .
   * debian/control:
 + Bump Standards-Version: to 4.4.1. No changes needed.
 + Update B-Ds: Add file-embed.
 + Drop B-D devscripts. This originally was intended to be
   dpkg-dev (not devscripts). The required dpkg-dev version
   is available in Debian since wheezy.
   * debian/patches:
 + Add  bump-to-new-1-0-4-tag.patch. Upstream moved 1.0.4 tag in
   upstream Git. Chasing after them... (Closes: #947162).
 + Add 0001_remove-implicit-prelude-import-from-AST.patch.
 + Add 0002_export-AST-unqualified.patch.
 + Add 0003_keep-SpanInfos-for-local-idents-in-SyntaxCheck.patch.
   * debian/README.source:
 + Document tag movings on the upstream Git repository.
   * debian/rules:
 + Disable tests for now. In Debian, tests fail. Upstream states
   that all tests succeed. This solution is not ideal.
Checksums-Sha1:
 dcc533cb135baedf3c45c2d4b7ef5ed05962fe3e 3274 curry-frontend_1.0.4-3.dsc
 f4354bcf5981a216b96bd8c0d0a5b44c742ff868 28636 
curry-frontend_1.0.4-3.debian.tar.xz
 5d4b11a7c13139d99e4812531a5424cb73632952 7556 
curry-frontend_1.0.4-3_source.buildinfo
Checksums-Sha256:
 03a9f2da15c154ddf3f465df9334ffc02c66dfa984ee501b8e6c5a28d58002c2 3274 
curry-frontend_1.0.4-3.dsc
 311195888c546420c949ebd4aa4e18275682eb7255d45e82245a11879b62027a 28636 
curry-frontend_1.0.4-3.debian.tar.xz
 40f1ef49270468612c2d25358392a1f9e70c584a0bd6333fc8e4a354d6f34242 7556 
curry-frontend_1.0.4-3_source.buildinfo
Files:
 fb6457e9fd61b2ee88f906fda0328979 3274 haskell optional 
curry-frontend_1.0.4-3.dsc
 f85f8eefc0ff12c27b1713082c4f93f7 28636 haskell optional 
curry-frontend_1.0.4-3.debian.tar.xz
 5ca0333a1c60f63351706032c8f43bdb 7556 haskell optional 
curry-frontend_1.0.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl4c34kVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxg1kP/1x9YtpmoEe9SCm9u/pRJm//YJtn
txX1ZZJv/uRKqQDPpDtow30qBTETEhkcQmVK1MvIR3TWpzeM5c9UE51n6sDvW8DF
MM2p8wi6wwmEQf4UeL5XrrP8OdLoj/UMqJMr/nXYcpNjaHCCA3sv3MpfdE+ISoLU
Wli1VgqeLV2kXv2PsM4AjJc3xWZ20vR2Q2s1BJkqOXgHrjqI06pAfDNJN84cjUuT
sWPMho9m/6sWoNKFHJICzP8Nm4SJd1Rm2tHg8kheVo+pCNZHfj8V/lcgEGP9B9TC
cxxgzfb16uGj1mMdp/qkcqJi+wLfJboAXfwf2+4y85i0Rd8MFusWJX95Dmsg6yc9
OAyUj6doxIJJmwMk6V/flwi0fPiGbhn72DQI1hcKGf7oeIaOniwJY9ljaR9kFnLn
HLn6NRUPSKU72oKSFTInQgCbdcZf7Zvu+3dUTjQvXuy1iY2BosZmiq0BVb4mx4yO
bjRYjSbla37yL2fN5nlBtUFQN+iYJF4a119fYbWkNqUHPCpZTbfTnu0b7nu1e25e
6lM6mzcOSS1qDhEx/QLOYwpX/PML/9PBczk5ejKbG2l7GzZUb4AJEK/+nowAFgdv
Zr4DbGd6JsYyusCoqWap7lj/6k2XKIOlqi/ks8+T5oOebiXGpyrX0iFkzS7apBlO
G3iMMdO0I//my55m
=R8Sb
-END PGP SIGNATURE End Message ---

Bug#948840: systemd: FTBFS: meson.build:1036:8: ERROR: Could not generate cargs for libiptc:

[Mattia Rizzolo]

Source: systemd
Version: 244-3
Severity: serious
Tags: ftbfs

Dear maintainer,
your package failed to rebuild in a standard sid chroot:

Run-time dependency libmicrohttpd found: YES 0.9.66
Run-time dependency libcryptsetup found: YES 2.2.2
Run-time dependency libcurl found: YES 7.67.0
Run-time dependency libidn2 found: YES 2.2.0
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency libiptc found: NO

meson.build:1036:8: ERROR: Could not generate cargs for libiptc:
Package libip6tc was not found in the pkg-config search path.
Perhaps you should add the directory containing `libip6tc.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libip6tc', required by 'libiptc', not found


A full log can be found at 
/build/1st/systemd-244/build-deb/meson-logs/meson-log.txt
cd build-deb && tail -v -n \+0 meson-logs/meson-log.txt


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#948801: refcard: FTBFS: pdfjoin: Command not found

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #948801 [src:refcard] refcard: FTBFS: pdfjoin: Command not found
Added tag(s) pending.

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

Bug#948801: refcard: FTBFS: pdfjoin: Command not found

[Holger Wansing]

Control: tags -1 + pending


Mattia Rizzolo  wrote:
> Source: refcard
> Version: 10.5
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer,
> 
> during a rebuild in a standard sid chroot, your package failed to build:
[...]
> pdfjoin --vanilla --fitpaper true --outfile refcard-en-lt.s.pdf.x.pdf 
> refcard-en-lt.s.pdf empty.pdf empty.pdf
> make[2]: pdfjoin: Command not found
> make[2]: *** [Makefile:64: refcard-en-lt.t.pdf] Error 127
> make[2]: *** Waiting for unfinished jobs

Fixed in git.
Tagging this bug as pending.


Thanks
Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Processed: yt not compatible to sympy 1.5 yet

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 sympy/1.5-1
Bug #948459 [src:sympy, src:yt] sympy breaks yt autopkgtest: FAIL: Create units 
with strings and check attributes.
No longer marked as found in versions sympy/1.5-1.
> tags -1 patch
Bug #948459 [src:sympy, src:yt] sympy breaks yt autopkgtest: FAIL: Create units 
with strings and check attributes.
Added tag(s) patch.

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

Bug#948459: yt not compatible to sympy 1.5 yet

[Ole Streicher]

Control: notfound -1 sympy/1.5-1
Control: tags -1 patch

A patch is available at https://github.com/yt-project/yt/pull/2407

Bug#948837: python-vispy ftbfs in unstable

[Matthias Klose]

Package: src:python-vispy
Version: 0.6.1-2
Severity: serious
Tags: sid bullseye

python-vispy ftbfs in unstable:

[...]
running build_ext
building 'vispy.visuals.text._sdf_cpu' extension
creating build/temp.linux-x86_64-3.7
creating build/temp.linux-x86_64-3.7/vispy
creating build/temp.linux-x86_64-3.7/vispy/visuals
creating build/temp.linux-x86_64-3.7/vispy/visuals/text
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include
-I/usr/include/python3.7m -c vispy/visuals/text/_sdf_cpu.c -o
build/temp.linux-x86_64-3.7/vispy/visuals/text/_sdf_cpu.o
In file included from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1830,
 from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
 from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
 from vispy/visuals/text/_sdf_cpu.c:617:
/usr/lib/python3/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2:
warning: #warning "Using deprecated NumPy API, disable it with " "#define
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
   17 | #warning "Using deprecated NumPy API, disable it with " \
  |  ^~~
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-z,relro -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
build/temp.linux-x86_64-3.7/vispy/visuals/text/_sdf_cpu.o -o
/<>/.pybuild/cpython3_3.7_vispy/build/vispy/visuals/text/_sdf_cpu.cpython-37m-x86_64-linux-gnu.so
PYTHONPATH=`pybuild --print {build_dir}` make -C doc html
make[2]: Entering directory '/<>/doc'
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v1.8.5

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/config.py", line 368, in
eval_config_file
execfile_(filename, namespace)
  File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in
execfile_
exec_(code, _globals)
  File "/<>/doc/conf.py", line 18, in 
import vispy
ModuleNotFoundError: No module named 'vispy'

make[2]: *** [Makefile:36: html] Error 2
make[2]: Leaving directory '/<>/doc'
make[1]: *** [debian/rules:17: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build] Error 2

Bug#948836: gnome-dictionary: FTBFS: failed test

[Mattia Rizzolo]

Source: gnome-dictionary
Version: 3.26.1-5
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot:



1/2 validate-desktopOK   0.02 s

--- command ---
/usr/bin/desktop-file-validate org.gnome.Dictionary.desktop
---

2/2 validate-appdataFAIL 0.04 s (exit status 1)

--- command ---
/usr/bin/appstream-util validate --nonet org.gnome.Dictionary.appdata.xml
--- stdout ---
org.gnome.Dictionary.appdata.xml: FAILED:
• tag-missing   :  required [use 
https://odrs.gnome.org/oars]
--- stderr ---

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.019: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.019: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.020: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.

(appstream-util:64452): dconf-CRITICAL **: 02:43:24.021: unable to create 
directory '/nonexistent/first-build/.cache/dconf': Permission denied.  dconf 
will not work properly.
Validation of files failed
---


Ok:1
Expected Fail: 0
Fail:  1
Unexpected Pass:   0
Skipped:   0
Timeout:   0
dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=15 
ninja test returned exit code 1
make: *** [debian/rules:7: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#948834: glib2.0: FTBFS: test failure

[Mattia Rizzolo]

Source: glib2.0
Version: 2.62.4-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot.

GLib-Message: 17:05:23.993: test_mapping: ok
GLib-Message: 17:05:23.993: test_private: ok
GLib-Message: 17:05:23.995: test_child_private: child spawned
GLib-Message: 17:05:23.997: test_child_private: received first child signal
GLib-Message: 17:05:23.997: test_child_private: received parent signal
GLib-Message: 17:05:23.997: test_child_private: received second child signal
GLib-Message: 17:05:23.997: test_child_private: ok
Starting 8 threads for concurrent GSlice usage...
gcfbbcgcchbfbheedegecdehddbebgbhbhfhhddcehcddebdbdeddgeehhffeefaahgdcgchegccfchbbfffdcccbbfecffcfeeabfbbbebfefaaacgeaaa
Thread 1: 48935 blocks freed, 1036 blocks not freed
Thread 2: 41412 blocks freed, 8421 blocks not freed
Thread 3: 44923 blocks freed, 5101 blocks not freed
Thread 4: 38710 blocks freed, 11527 blocks not freed
Thread 5: 45664 blocks freed, 4028 blocks not freed
Thread 6: 44076 blocks freed, 5763 blocks not freed
Thread 7: 44433 blocks freed, 5715 blocks not freed
Thread 8: 39611 blocks freed, 10645 blocks not freed
Add same-priority sources: 37
Remove in random order: 69
Add different-priority sources: 72
Remove in random order: 102
Add sources from threads: 375
Remove sources from threads: 145

128/261 glib:gio / filter-streams   OK   0.03 s 
...
173/261 glib:gio / unix-mounts  OK   0.03 s
174/261 glib:gio / unix-streams OK   1.03 s
175/261 glib:gio / g-file-info-filesystem-readonly  OK   0.01 s
176/261 glib:gio / gschema-compile  OK   1.04 s
177/261 glib:gio / trashOK   0.02 s
178/261 glib:gio / gsocketclient-slow   FAIL 0.02 s (killed by 
signal 6 SIGABRT)
179/261 glib:gio / appinfo  OK   0.04 s
180/261 glib:gio / desktop-app-info OK   1.25 s
181/261 glib:gio / mimeapps OK   0.08 s
182/261 glib:gio+slow / actions OK  45.86 s
183/261 glib:gio / gdbus-auth   OK   0.04 s
...
253/261 glib:glib+slow / threadpool-testOK  36.22 s # random seed: 
R02S5bad22ae13d35ce4da94f42a9d17de2f
# random seed: R02S7fae02546c7f4d8fe222d409000c398b
# random seed: R02S33571a694045528b0fb3c38aa2be4b03
# random seed: R02Se322952d806f2dbb5ce87d070e1a8045
Children: 3 Iters: 1
Children: 3 Iters: 1
Children: 3 Iters: 1
Children: 3 Iters: 1
Elapsed user: 115
Elapsed system: 216
Elapsed total: 331
total / iteration: 0.0110333
# random seed: R02Sc353539a86c9df7d32340b67a8afc668

254/261 glib:glib / type-test   OK   0.02 s
255/261 glib:glib / unicode-caseconvOK   0.02 s
256/261 glib:glib / unicode-encodingOK   0.02 s
257/261 glib:glib / module-test-library OK   0.02 s
258/261 glib:glib / module-test-plugin  OK   0.03 s
259/261 glib:glib / cxx-testOK   0.03 s
260/261 glib:glib / timeloopOK   3.53 s
261/261 glib:glib / iochannel-test  OK   0.02 s

Ok:  260
Expected Fail: 0
Fail:  1
Unexpected Pass:   0
Skipped:   0
Timeout:   0

make[1]: *** [debian/rules:131: override_dh_auto_test-arch] Error 1
make[1]: Leaving directory '/build/1st/glib2.0-2.62.4'
make: *** [debian/rules:21: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#948832: git: Fix for test failures with python2

[Steve Langasek]

Package: git
Version: 1:2.24.0-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

With the impending removal of /usr/bin/python and the python package in
favor of /usr/bin/python2 (shipped by 'python2'), git will start to fail to
build due to trying to invoke /usr/bin/python in the testsuite.

The attached patch fixes the build failure in Ubuntu, where python has
already been dropped in favor of python2.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru git-2.24.0/debian/control git-2.24.0/debian/control
--- git-2.24.0/debian/control   2019-11-13 03:50:30.0 -0800
+++ git-2.24.0/debian/control   2020-01-13 07:04:49.0 -0800
@@ -7,7 +7,7 @@
  libpcre2-dev | libpcre3-dev,
  libcurl4-gnutls-dev, libexpat1-dev,
  subversion, libsvn-perl, libyaml-perl,
- tcl, python,
+ tcl, python2,
  libhttp-date-perl | libtime-parsedate-perl,
  libcgi-pm-perl,
  liberror-perl,
diff -Nru git-2.24.0/debian/rules git-2.24.0/debian/rules
--- git-2.24.0/debian/rules 2019-11-13 03:50:30.0 -0800
+++ git-2.24.0/debian/rules 2020-01-13 07:04:49.0 -0800
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+export PYTHON_PATH=/usr/bin/python2
 CC =gcc
 CPPFLAGS :=$(shell dpkg-buildflags --get CPPFLAGS)
 CFLAGS :=-Wall $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS)

Bug#948828: marked as done (python-whoosh ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 15:39:25 -0500
with message-id 

and subject line Re: [Python-modules-team] Bug#948828: python-whoosh ftbfs in 
unstable
has caused the Debian Bug report #948828,
regarding python-whoosh ftbfs in unstable
to be marked as done.

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

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


-- 
948828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-whoosh
Version: 2.7.4+git6-g9134ad92-4
Severity: serious
Tags: sid bullseye

python-whoosh ftbfs in unstable:

[...]
The HTML pages are in docs/build/html.
make[1]: Leaving directory '/<>/python-whoosh-2.7.4+git6-g9134ad92'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd
/<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
python2.7 -m pytest tests
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/pytest.py", line 102, in 
raise SystemExit(pytest.main())
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 63,
in main
config = _prepareconfig(args, plugins)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 207,
in _prepareconfig
pluginmanager=pluginmanager, args=args
  File "/usr/lib/python2.7/dist-packages/pluggy/hooks.py", line 286, in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 92, in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 86, in 

firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 203, in 
_multicall
gen.send(outcome)
  File "/usr/lib/python2.7/dist-packages/_pytest/helpconfig.py", line 94, in
pytest_cmdline_parse
config = outcome.get_result()
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 81, in 
get_result
_reraise(*ex)  # noqa
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 187, in 
_multicall
res = hook_impl.function(*args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 687,
in pytest_cmdline_parse
self.parse(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 895,
in parse
self._preparse(args, addopts=addopts)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 829,
in _preparse
self._initini(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 760,
in _initini
config=self,
  File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py", line 127,
in determine_setup
rootdir, inifile, inicfg = getcfg([ancestor], config=config)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py", line 51,
in getcfg
pytrace=False,
  File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 119, in fail
raise Failed(msg=msg, pytrace=pytrace)
builtins.Failed: [pytest] section in setup.cfg files is no longer supported,
change to [tool:pytest] instead.
E: pybuild pybuild:342: test: plugin distutils failed with: exit code=1: cd
/<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:5: build] Error 255
--- End Message ---
--- Begin Message ---
Version: 2.7.4+git6-g9134ad92-5

On Mon, Jan 13, 2020 at 3:06 PM Matthias Klose  wrote:
>
> Package: src:python-whoosh
> Version: 2.7.4+git6-g9134ad92-4
> Severity: serious
> Tags: sid bullseye
>
> python-whoosh ftbfs in unstable:

fixed already

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Bug#948831: git-buildpackage: FTBFS: ImportError: No module named cachecontrol

[Mattia Rizzolo]

Source: git-buildpackage
Version: 0.9.17
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in standard sid chroot:

make[3]: Entering directory '/build/1st/git-buildpackage-0.9.17'
mkdir -p build
pydoctor -v --config=.pydoctor.cfg
Traceback (most recent call last):
  File "/usr/bin/pydoctor", line 10, in 
from pydoctor.driver import main
  File "/usr/lib/python2.7/dist-packages/pydoctor/driver.py", line 5, in 

from pydoctor import model, zopeinterface
  File "/usr/lib/python2.7/dist-packages/pydoctor/model.py", line 19, in 

from pydoctor.sphinx import SphinxInventory
  File "/usr/lib/python2.7/dist-packages/pydoctor/sphinx.py", line 10, in 

from cachecontrol import CacheControl
ImportError: No module named cachecontrol
make[3]: *** [Makefile:29: apidocs] Error 1
make[3]: Leaving directory '/build/1st/git-buildpackage-0.9.17'
make[2]: *** [Makefile:25: docs] Error 2
make[2]: Leaving directory '/build/1st/git-buildpackage-0.9.17'
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/1st/git-buildpackage-0.9.17'
make: *** [debian/rules:18: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#948803: gcc-9: collect2: fatal error: ld terminated with signal 4 [Illegal instruction]

[Matthias Klose]

Control: reassign -1 binutils

On 13.01.20 17:53, Bas Couwenberg wrote:
> Source: gcc-9
> Version: 9.2.1-22
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: affects -1 src:gdal
> 
> Dear Maintainer,
> 
> gdal FTBFS on arm64 due ton illegal instruction. From its config.log:
> 
>  configure:3908: gcc -g -O2 
> -fdebug-prefix-map=/home/sebastic/tmp/debian/gdal-3.0.3+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
>  collect2: fatal error: ld terminated with signal 4 [Illegal instruction]
that's the linker.

Bug#948828: python-whoosh ftbfs in unstable

[Matthias Klose]

Package: src:python-whoosh
Version: 2.7.4+git6-g9134ad92-4
Severity: serious
Tags: sid bullseye

python-whoosh ftbfs in unstable:

[...]
The HTML pages are in docs/build/html.
make[1]: Leaving directory '/<>/python-whoosh-2.7.4+git6-g9134ad92'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd
/<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
python2.7 -m pytest tests
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/pytest.py", line 102, in 
raise SystemExit(pytest.main())
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 63,
in main
config = _prepareconfig(args, plugins)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 207,
in _prepareconfig
pluginmanager=pluginmanager, args=args
  File "/usr/lib/python2.7/dist-packages/pluggy/hooks.py", line 286, in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 92, in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 86, in 

firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 203, in 
_multicall
gen.send(outcome)
  File "/usr/lib/python2.7/dist-packages/_pytest/helpconfig.py", line 94, in
pytest_cmdline_parse
config = outcome.get_result()
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 81, in 
get_result
_reraise(*ex)  # noqa
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 187, in 
_multicall
res = hook_impl.function(*args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 687,
in pytest_cmdline_parse
self.parse(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 895,
in parse
self._preparse(args, addopts=addopts)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 829,
in _preparse
self._initini(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 760,
in _initini
config=self,
  File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py", line 127,
in determine_setup
rootdir, inifile, inicfg = getcfg([ancestor], config=config)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py", line 51,
in getcfg
pytrace=False,
  File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 119, in fail
raise Failed(msg=msg, pytrace=pytrace)
builtins.Failed: [pytest] section in setup.cfg files is no longer supported,
change to [tool:pytest] instead.
E: pybuild pybuild:342: test: plugin distutils failed with: exit code=1: cd
/<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:5: build] Error 255

Processed: Re: z3: cannot be built on buildds

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 cannot migrate to testing
Bug #948763 [src:z3] z3: cannot be built on buildds
Changed Bug title to 'cannot migrate to testing' from 'z3: cannot be built on 
buildds'.

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

Bug#948763: z3: cannot be built on buildds

[Ximin Luo]

Fabian Wolff:
> On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne  wrote:
>> Source: z3
>> Version: 4.8.7-3
>> Severity: serious
>>
>> z3 cannot be built on buildds, because its Build-Depends cannot be
>> satisfied on buildds. Failing to build on buildds is a serious problem.
> 
> It builds now on all but three architectures, including, in particular, all
> release architectures.
> 
>> [...]
> 
> Thanks for your suggestions, but I'm not very familiar with how Multi-Arch
> annotations should be used; I just accepted a patch to make the z3 package
> more cross-build friendly (see #948109).
> 

I tested this myself and also it's now working on buildds, so I don't see what 
the problem is here. Can we just close this bug report and mark it as `notfound 
-1 $version`?

FWIW, when I tried things locally with sbuild, changing dh-python:all to simply 
dh-python whilst retaining the other annotations *did not work*, regardless of 
how it's "supposed" to work. That is why I added the extra :all.

> Can you give me a patch where you set the build dependency annotations in a
> sound way that also works for cross-building? Otherwise, I would have to
> simply remove all annotations again in order to fix this bug (but clearly,
> that would not be the most desirable solution).
> 
> I would also be happy to use the nojava build profile that you suggested,
> but again, I'm not familiar with this technique, and from what I've heard,
> there are still some problems e. g. with using "dh-sequence-javahelper
>  ". But if somebody gave me a patch, I'd be happy to apply it.
> 
> Thanks for your help!
> Fabian
> 

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#948827: kwindowsystem FTBFS: The XFixes library could not be found.

[Helmut Grohne]

Source: kwindowsystem
Version: 5.62.0-2
Severity: serious
Tags: ftbfs

kwindowsystem fails to build in unstable. The relevant message seems to
be:

| CMake Error at src/CMakeLists.txt:40 (message):
|   The XFixes library could not be found.  Please install the development
|   package for it.
| 
| 
| -- Configuring incomplete, errors occurred!

Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/kwindowsystem_5.62.0-2.rbuild.log.gz
Also seen on crossqa since at least three weeks, but less than seven
weeks:
http://crossqa.debian.net/build/kwindowsystem_5.62.0-2_armhf_20191221224841.log

It seems that for some reason libxfixes-dev is no longer part of the
installation set of the Build-Depends.

Helmut

Processed: Re: brightd does not fade

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #934140 {Done: Andrej Shadura } [brightd] brightd does 
not fade
Added tag(s) pending.

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

Bug#948763: z3: cannot be built on buildds

[Helmut Grohne]

Control: retitle -1 cannot migrate to testing

Hi Fabian,

On Mon, Jan 13, 2020 at 04:27:15PM +0100, Fabian Wolff wrote:
> On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne  wrote:
> > Source: z3
> > Version: 4.8.7-3
> > Severity: serious
> > 
> > z3 cannot be built on buildds, because its Build-Depends cannot be
> > satisfied on buildds. Failing to build on buildds is a serious problem.
> 
> It builds now on all but three architectures, including, in particular, all
> release architectures.

Oh, I'm wrong here. It did build. But the dependency issue prevents it
from migrating to testing. So you want to fix that anyway.

> Thanks for your suggestions, but I'm not very familiar with how Multi-Arch
> annotations should be used; I just accepted a patch to make the z3 package
> more cross-build friendly (see #948109).

That bug is not at all about cross building nor multi-arch. It seems you
(and your contributors) are conflating multiple issues. Things become
much easier once you start separating them.

> Can you give me a patch where you set the build dependency annotations in a
> sound way that also works for cross-building? Otherwise, I would have to
> simply remove all annotations again in order to fix this bug (but clearly,
> that would not be the most desirable solution).

No. The expectation that every package can be cross built is misguided.
z3 uses java stuff, which is an unsolved problem. Therefore you cannot
make z3's dependencies cross-satisfiable at this time. If you want to do
so anyway, be prepared to invest quite some work.

For this reason, reverting the annotations is not the worst of options.

> I would also be happy to use the nojava build profile that you suggested,
> but again, I'm not familiar with this technique, and from what I've heard,
> there are still some problems e. g. with using "dh-sequence-javahelper
>  ". But if somebody gave me a patch, I'd be happy to apply it.

That seems like a sensible path forward, but I lack the domain-specific
knowledge about z3 to do that. This situation has happened before (e.g.
with texlive maintainer Norbert Preining): He lacked knowledge of
multi-arch and I lacked knowledge about texlive. We started discussing
things and learned from one another. In that process we figured out how
to make multi-arch work for parts of texlive. What I'm trying to say is:
I cannot give you a patch. We can only get there together and I'm happy
to help.

If we want to move forward with , I have a few questions. If
you intend to answer them, please clone a new bug for that. This bug is
about fixing the wrong Build-Depends annotations.

Why is the libz3-java package "Architecture: any" (long list actually)
instead of "Architecture: all"? Many lib*-java packages are
"Architecture: all" instead, so I'd like to understand the reason.

Why is the libz3-java package "Multi-Arch: foreign"? It seems to depend
on libz3-jni, which is "Multi-Arch: same". Such a setup seems wrong as
both seem to be libraries. As a dependency on libz3-java would be
expected to provide the jni components for the requested architecture,
but this is not the case here. Possibly, the "Multi-Arch: foreign" is
wrong here. In that case, "Architecture: any" does make sense as
"Architecture: all" cannot propagate an architecture-constraint. (This
is also known as the multi-arch-interpreter-problem.)

Why are libz3-java and libz3-jni separate packages? Why not merge them
into one? In which situations would you install one, but not the other?

When we talk about multi-arch or build profiles, we need to have a good
understanding of what the relevant interfaces of packages are. My
questions aim at clarifying that.

Helmut

Bug#934140: brightd does not fade

[Andreas Beckmann]

Followup-For: Bug #934140
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948826


Andreas

Bug#948824: opensmtpd: Installation fails with "post-installation script subprocess returned error exit status 1"

[Jernej Jakob]

Package: opensmtpd
Version: 6.0.3p1-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed opensmtpd but its installation failed. I found an archived
bug report that matches my error exactly:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770939

DEBCONF_DEBUG=developer dpkg --configure --pending
Setting up opensmtpd (6.0.3p1-5) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is opensmtpd
debconf (developer): starting /var/lib/dpkg/info/opensmtpd.config
configure 
debconf (developer): <-- FGET opensmtpd/mailname seen
debconf (developer): --> 0 false
dpkg: error processing package opensmtpd (--configure):
 installed opensmtpd package post-installation script subprocess
 returned error exit status 1
 Errors were encountered while processing:
  opensmtpd

Regards,
Jernej

-- System Information:
Debian Release: 10.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: mipsel (mips)

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

Versions of packages opensmtpd depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71
ii  ed 1.15-1
ii  libasr01.0.2-2
ii  libc6  2.28-10
ii  libdb5.3   5.3.28+dfsg1-0.5
ii  libevent-2.1-6 2.1.8-stable-4
ii  libpam0g   1.3.1-5
ii  libssl1.1  1.1.1d-0+deb10u2
ii  lsb-base   10.2019051400
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages opensmtpd recommends:
pn  opensmtpd-extras  

Versions of packages opensmtpd suggests:
ii  ca-certificates  20190110

-- debconf information:
  opensmtpd/root_address:
  opensmtpd/mailname:

Bug#948822: python-pint ftbfs in unstable (failing test)

[Matthias Klose]

Package: src:python-pint
Version: 0.9-2
Severity: serious
Tags: sid bullseye

test_unitcontainer_repr (pint.testsuite.test_util.TestUnitsContainer) ... ok

==
ERROR: test_nonnumeric_magnitudes
(pint.testsuite.test_quantity.TestQuantityToCompact)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_pint/build/pint/testsuite/test_quantity.py",
line 419, in test_nonnumeric_magnitudes
self.assertRaises(RuntimeError, self.compareQuantity_compact(x,x))
  File "/usr/lib/python3.8/unittest/case.py", line 816, in assertRaises
return context.handle('assertRaises', args, kwargs)
  File "/usr/lib/python3.8/unittest/case.py", line 202, in handle
callable_obj(*args, **kwargs)
TypeError: 'NoneType' object is not callable

--
Ran 802 tests in 16.590s

FAILED (SKIP=17, errors=1)
E: pybuild pybuild:342: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8_pint/build; python3.8 -m nose -v
dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.8 3.7"
returned exit code 13
make: *** [debian/rules:6: build] Error 255

Bug#948821: geis: FTBFS: dh: unable to load addon python3

[Mattia Rizzolo]

Source: geis
Version: 2.2.17-1.2
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot:

dpkg-buildpackage: info: source package geis
dpkg-buildpackage: info: source version 2.2.17-1.2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Mattia Rizzolo 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python3,autoreconf --parallel
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains:
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 
/usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/shar
e/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
(eval 10) line 1.
BEGIN failed--compilation aborted at (eval 10) line 1.

make: *** [debian/rules:4: clean] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#938263: marked as done (python-whoosh: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 18:34:59 +
with message-id 
and subject line Bug#938263: fixed in python-whoosh 2.7.4+git6-g9134ad92-5
has caused the Debian Bug report #938263,
regarding python-whoosh: 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.)


-- 
938263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-whoosh
Version: 2.7.4+git6-g9134ad92-4
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:python-whoosh

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: python-whoosh
Source-Version: 2.7.4+git6-g9134ad92-5

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-whoosh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Jan 2020 13:10:26 -0500
Source: python-whoosh
Architecture: source
Version: 2.7.4+git6-g9134ad92-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938263 948426
Changes:
 python-whoosh (2.7.4+git6-g9134ad92-5) unstable; urgency=medium
 .
   [ Emmanuel Arias ]
   * Team upload.
   * Apply patch to use [tool:pytest] instead of [pytest] section. (Closes: 
#948426)
   * Remove Python 2 support. (Closes: #938263)
   * d/gitlab-ci.yml: enable Salsa CI.
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.1.
Checksums-Sha1:
 da3636d8d4ca4fb086b6829ac7615c7ad0701339 2321 
python-whoosh_2.7.4+git6-g9134ad92-5.dsc
 038ac074dd6966e2c5518a088990a13aeb8274c7 10324 
python-whoosh_2.7.4+git6-g9134ad92-5.debian.tar.xz
 4a3a0942d3d152c5d5fa17938c19333172fa2ed0 6362 
python-whoo

Bug#948426: marked as done (python-whoosh ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 18:35:00 +
with message-id 
and subject line Bug#948426: fixed in python-whoosh 2.7.4+git6-g9134ad92-5
has caused the Debian Bug report #948426,
regarding python-whoosh ftbfs in unstable
to be marked as done.

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

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


-- 
948426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-whoosh
Version: 2.7.4+git6-g9134ad92-4
Severity: serious
Tags: sid bullseye

python-whoosh ftbfs in unstable, with the recent pytest:

[...]
The HTML pages are in docs/build/html.
make[1]: Leaving directory '/<>/python-whoosh-2.7.4+git6-g9134ad92'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd
/<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
python2.7 -m pytest tests
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/pytest.py", line 102, in 
raise SystemExit(pytest.main())
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 63,
in main
config = _prepareconfig(args, plugins)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 207,
in _prepareconfig
pluginmanager=pluginmanager, args=args
  File "/usr/lib/python2.7/dist-packages/pluggy/hooks.py", line 286, in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 92, in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python2.7/dist-packages/pluggy/manager.py", line 86, in 

firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 203, in 
_multicall
gen.send(outcome)
  File "/usr/lib/python2.7/dist-packages/_pytest/helpconfig.py", line 94, in
pytest_cmdline_parse
config = outcome.get_result()
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 81, in 
get_result
_reraise(*ex)  # noqa
  File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 187, in 
_multicall
res = hook_impl.function(*args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 687,
in pytest_cmdline_parse
self.parse(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 895,
in parse
self._preparse(args, addopts=addopts)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 829,
in _preparse
self._initini(args)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/__init__.py", line 760,
in _initini
config=self,
  File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py", line 127,
in determine_setup
rootdir, inifile, inicfg = getcfg([ancestor], config=config)
  File "/usr/lib/python2.7/dist-packages/_pytest/config/findpaths.py", line 51,
in getcfg
pytrace=False,
  File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 119, in fail
raise Failed(msg=msg, pytrace=pytrace)
builtins.Failed: [pytest] section in setup.cfg files is no longer supported,
change to [tool:pytest] instead.
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/python-whoosh-2.7.4+git6-g9134ad92/.pybuild/cpython2_2.7_whoosh/build;
python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:5: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: python-whoosh
Source-Version: 2.7.4+git6-g9134ad92-5

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-whoosh package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administ

Bug#938157: [Python-modules-team] Bug#938157: Bug#938157: Bug#938157: python-scipy: Python2 removal in sid/bullseye

[Sandro Tosi]

> >It's just that there is no extra effort required in this case.
> >python3-scipy does indeed need the effort taken, but once that effort
> >is
> >done, it's no more effort to apply the same fix to python-scipy.  So
> >yes, please do focus on fixing python3-scipy! :)
>
> Yes, maybe so, but delaying the python2-rm blocks other work and thus delays 
> and complicates getting that major effort completed.  Let's not.

exactly, i really dont understand what's the value of fixing something
that's gonna be removed anyway.

I think i'm just gonna wait a couple more days and then file a RM

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#932351: gnubg: Crashes on launch

[Russ Allbery]

Andreas Beckmann  writes:

> Followup-For: Bug #932351
> Control: tag -1 pending

> buster-pu request: https://bugs.debian.org/948796

Oh, thank you!  I was going to get to that and then didn't.  Much
appreciated and let me know if I can help in any way.

-- 
Russ Allbery (r...@debian.org)  

Bug#948713: marked as pending in python-pygraphviz

[Sandro Tosi]

i've actually  decided to fix it like this:
https://salsa.debian.org/python-team/modules/python-pygraphviz/commit/6003146ad077ad2310c7d897c08344557b6fd3e2
(uploaded just now)

On Mon, Jan 13, 2020 at 12:55 PM Anton Gladky  wrote:
>
> Hello Sandro,
>
> thank you for your upload. I have cancelled my NMU.
>
> Best regards
>
> Anton



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Processed: reassign 948818 to initramfs-tools, forcibly merging 948257 948818

[Debian Bug Tracking System]

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

> reassign 948818 initramfs-tools
Bug #948818 [src:linux] depmod: lookup_builtin_file() could not open builtin 
file
Bug reassigned from package 'src:linux' to 'initramfs-tools'.
No longer marked as found in versions linux/5.4.8-1.
Ignoring request to alter fixed versions of bug #948818 to the same values 
previously set
> forcemerge 948257 948818
Bug #948257 [initramfs-tools] depmod: ERROR: ../libkmod/libkmod.c:515 
lookup_builtin_file() could not open builtin file 
'/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Bug #948301 [initramfs-tools] libkmod2: update-initramfs fails in 
lookup_builtin_file()
Bug #948327 [initramfs-tools] depmod: ERROR: ../libkmod/libkmod.c:515 
lookup_builtin_file() could not open builtin file
Bug #948357 [initramfs-tools] thousands of identical lookup_builtin_file 
warnings
Bug #948818 [initramfs-tools] depmod: lookup_builtin_file() could not open 
builtin file
Severity set to 'serious' from 'normal'
Added indication that 948818 affects kmod
Marked as found in versions initramfs-tools/0.135.
Bug #948301 [initramfs-tools] libkmod2: update-initramfs fails in 
lookup_builtin_file()
Marked as found in versions initramfs-tools/0.135.
Ignoring request to alter found versions of bug #948257 to the same values 
previously set
Marked as found in versions initramfs-tools/0.135.
Marked as found in versions initramfs-tools/0.135.
Bug #948327 [initramfs-tools] depmod: ERROR: ../libkmod/libkmod.c:515 
lookup_builtin_file() could not open builtin file
Bug #948357 [initramfs-tools] thousands of identical lookup_builtin_file 
warnings
Merged 948257 948301 948327 948357 948818
> thanks
Stopping processing here.

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

Bug#948713: marked as pending in python-pygraphviz

[Anton Gladky]

Hello Sandro,

thank you for your upload. I have cancelled my NMU.

Best regards

Anton

Bug#875180: [scribus] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Mon, Jan 13, 2020 at 05:29:59PM +0100, Mattia Rizzolo wrote:
> On Thu, Jan 09, 2020 at 10:50:09PM +0100, Moritz Mühlenhoff wrote:
> > Has there been further development?
> 
> Alas, things went way over the original timeline.  Scribus 1.6 actually
> seems to me to be more further aways from a release than it was last
> August.
> 
> > But if a 1.6 release is very close, it's also an option to ask FTP
> > masters to force-remove qt4 despite rendering scribus uninstallable.
> 
> I just wrote to upstream; if they don't stop me, I'll go ahead and
> package 1.5, which is not considered "production ready", but really
> nobody can notice how it isn't :)
> 
> Either way, expect something to happen in 1-2 weeks.

Thanks for the update!

Cheers,
Moritz

Processed: [bts-link] source package src:openalpr

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:openalpr
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #922588 (http://bugs.debian.org/922588)
> # Bug title: FTBFS against opencv 4.0.1 (exp)
> #  * https://github.com/openalpr/openalpr/issues/817
> #  * remote status changed: (?) -> open
> usertags 922588 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #937191 (http://bugs.debian.org/937191)
> # Bug title: openalpr: Python2 removal in sid/bullseye
> #  * https://github.com/openalpr/openalpr/issues/223
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 937191 + fixed-upstream
Bug #937191 [src:openalpr] openalpr: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> usertags 937191 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#947176: [pkg-netfilter-team] Bug#947176: libiptc.pc non-functional

[Alberto Molina Coballes]

On Mon, Jan 13, 2020 at 10:56:58AM +0100, Arturo Borrero Gonzalez wrote:
> On 1/11/20 12:04 PM, Michael Biebl wrote:
> > Hi Arturo
> > 
> > On Sun, 22 Dec 2019 15:06:02 +0100 Michael Biebl  wrote:
> >>
> >> 1/ Have a single libiptc-dev package which contains all development files
> >> 2/ Have a libip6tc-dev package which contains all development files
> >> related to libip6tc, have a libip4tc-dev package which contains all
> >> development files related to libip4tc and have libiptc-dev (convenience)
> >> package which contains libiptc.pc and depends on both libip6tc-dev and 
> >> libip4tc-dev
> >>
> > 
> > Have you decided how you want to proceed from here?
> > Would welcome your feedback.
> > 
> 
> Option 2) is probably the way to go.
> 
> I didn't have time to get to this yet. Perhaps @alberto have some spare 
> cycles?
>

Yes, I can handle this bug (hopefully next week)

Alberto

Bug#925629: marked as done (aghermann: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 17:04:13 +
with message-id 
and subject line Bug#925629: fixed in aghermann 1.1.2-3
has caused the Debian Bug report #925629,
regarding aghermann: 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.)


-- 
925629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aghermann
Version: 1.1.2-2
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/aghermann_1.1.2-2_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.

[...]
 from rk1968/rk1968-profiles.cc:17:
../../src/common/alg.hh:132:44: warning: 'pure' attribute on function returning 
'void' [-Wattributes]
  132 | ensure_within( T& v, const T& l, const T& h)
  |^
../../src/common/alg.hh: In function 'std::valarray 
agh::alg::to_vad(const std::valarray&)':
../../src/common/alg.hh:169:20: warning: moving a local object in a return 
statement prevents copy elision [-Wpessimizing-move]
  169 | return move(ret);
  |^
../../src/common/alg.hh:169:20: note: remove 'std::move' call
In file included from ../../src/libmetrics/all.hh:16,
 from ../../src/aghermann/expdesign/recording.hh:19,
 from ../../src/aghermann/expdesign/profile.hh:16,
 from ../../src/aghermann/model/achermann.hh:24,
 from ../../src/aghermann/expdesign/expdesign.hh:27,
 from rk1968/rk1968-profiles.cc:17:
../../src/libmetrics/psd.hh: In member function 'std::valarray 
metrics::psd::CProfile::course(double, double) const':
../../src/libmetrics/psd.hh:152:36: warning: moving a local object in a return 
statement prevents copy elision [-Wpessimizing-move]
  152 | return move(acc);
  |^
../../src/libmetrics/psd.hh:152:36: note: remove 'std::move' call
In file included from ../../src/libmetrics/all.hh:16,
 from ../../src/aghermann/expdesign/recording.hh:19,
 from rk1968/rk1968.cc:29:
../../src/libmetrics/psd.hh: In member function 'std::valarray 
metrics::psd::CProfile::course(double, double) const':
../../src/libmetrics/psd.hh:152:36: warning: moving a local object in a return 
statement prevents copy elision [-Wpessimizing-move]
  152 | return move(acc);
  |^
../../src/libmetrics/psd.hh:152:36: note: remove 'std::move' call
In file included from ../../src/libsigproc/sigproc.hh:28,
 from rk1968/rk1968.hh:23,
 from rk1968/rk1968-profiles.cc:19:
../../src/libsigproc/exstrom.hh: In function 'std::valarray 
exstrom::ccof_bwlp(unsigned int)':
../../src/libsigproc/exstrom.hh:326:20: warning: moving a local object in a 
return statement prevents copy elision [-Wpessimizing-move]
  326 | return move(ccof);
  |^~
../../src/libsigproc/exstrom.hh:326:20: note: remove 'std::move' call
../../src/libsigproc/exstrom.hh: In function 'std::valarray 
exstrom::ccof_bwhp(unsigned int)':
../../src/libsigproc/exstrom.hh:345:20: warning: moving a local object in a 
return statement prevents cop

Processed: gcc-9: collect2: fatal error: ld terminated with signal 4 [Illegal instruction]

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gdal
Bug #948803 [src:gcc-9] gcc-9: collect2: fatal error: ld terminated with signal 
4 [Illegal instruction]
Added indication that 948803 affects src:gdal

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

Bug#948803: gcc-9: collect2: fatal error: ld terminated with signal 4 [Illegal instruction]

[Bas Couwenberg]

Source: gcc-9
Version: 9.2.1-22
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:gdal

Dear Maintainer,

gdal FTBFS on arm64 due ton illegal instruction. From its config.log:

 configure:3908: gcc -g -O2 
-fdebug-prefix-map=/home/sebastic/tmp/debian/gdal-3.0.3+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
 collect2: fatal error: ld terminated with signal 4 [Illegal instruction]
 compilation terminated.
 configure:3912: $? = 1
 configure:3950: result: no
 configure: failed program was:
 | /* confdefs.h */
 | #define PACKAGE_NAME ""
 | #define PACKAGE_TARNAME ""
 | #define PACKAGE_VERSION ""
 | #define PACKAGE_STRING ""
 | #define PACKAGE_BUGREPORT ""
 | #define PACKAGE_URL ""
 | /* end confdefs.h.  */
 | 
 | int
 | main ()
 | {
 | 
 |   ;
 |   return 0;
 | }
 configure:3955: error: in `/home/sebastic/tmp/debian/gdal-3.0.3+dfsg':
 configure:3957: error: C compiler cannot create executables

The latest gcc-9 upload is not available on arm64 & armhf because it FTBFS 
there, which may be related.

Kind Regards,

Bas

Bug#925629: aghermann: ftbfs with GCC-9

[Andreas Tille]

Thanks a lot for the very helpful comments, Andreas.

On Mon, Jan 13, 2020 at 07:20:24AM -0800, Matthew Fernandez wrote:
> > I need to admit that I understand so less from all the gcc issues you
> > tried to explain - I do not even have any idea what C++ attributes are.
> > I simply cared for that Debian bug since nobody else did. :-(
> > So I feel really incompetent to discuss this with gcc maintainers but
> > I'd welcome if you bring it up there.
> 
> GCC attributes like the __attribute__ example here are a mechanism for 
> annotating C/C++ code with things not covered by the ISO standards, but 
> supported by compiler extensions. Attributes can be applied to many things 
> including variables and functions, and the function attributes are documented 
> at https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html 
> . These days 
> Clang also understands many of the GCC attributes.
> 
> The particular one in question here is telling the compiler that the lambda 
> function being defined has similar behavior to the libc printf function. The 
> integer parameters say a printf format string appears as the second argument 
> and the first varargs parameter is the third argument. This looks off by one, 
> but I think the captured local (&L) counts as the first parameter. The only 
> thing the compiler uses this attribute for is to detect calls to this lambda 
> with incorrect arguments and emit warnings for them.
> 
> The C++11 standard brought in a more commonly supported way of declaring 
> attributes using square brackets. Unfortunately the standard does not support 
> many common attributes and you still need to use a “gnu::” prefix to access 
> the GCC-specific attributes. Hence, “[[gnu::format(printf, 2, 3)]]” being the 
> C++11 equivalent of this.
> 
> >> If you need to bypass this urgently, I would recommend deleting the 
> >> attribute as that particular one is only used to aid the compiler in 
> >> creating warnings.
> > 
> > Hmmm, as I said my patch[1] works and I just have the gut feeling (as I
> > said I have no competence!) that this might be better than to delete the
> > attribute.  If not would you mind sending an alternative patch which is
> > better in your opinion?
> 
> Lambda functions, which are already being used in this code, are a C++11 
> feature as are this style of attributes. So I imagine it would be acceptable 
> to upstream to take your patch. Having said that, when I did this in my 
> experiment code above the compiler warned that it was ignoring this attribute 
> as it thought it was being applied to the trailing “int”.
> 
> I re-read the GCC issue and realized I’d misread Jonathan Wakely’s comments. 
> The issue is actually still open and Jonathan was just noting that r265787 
> introduced the bug, not fixed it. So I think what we’re seeing is consistent 
> with the GCC maintainers’ view.
> 
> I would suggest proposing your patch upstream. Although its primary purpose 
> is working around a compiler bug, it’s also an objective improvement in 
> modernizing the code base.
> 
> > Thanks again
> > 
> >   Andreas.
> > 
> > 
> >>  [0]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90333 
> >> 
> > 
> > [1] 
> > https://salsa.debian.org/med-team/aghermann/blob/master/debian/patches/workaround_gcc-9_issue.patch
> >  
> > 
> > 
> > -- 
> > http://fam-tille.de 

> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Processed: affects 877507

[Debian Bug Tracking System]

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

> affects 877507 - libppx-sexp-conv-ocaml
Bug #877507 [src:ppx-core] ppx-core FTBFS: E: Cannot find external tool 
'ocamlbuild'
Removed indication that 877507 affects libppx-sexp-conv-ocaml
> thanks
Stopping processing here.

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

Bug#875180: [scribus] Future Qt4 removal from Buster

[Mattia Rizzolo]

On Thu, Jan 09, 2020 at 10:50:09PM +0100, Moritz Mühlenhoff wrote:
> Has there been further development?

Alas, things went way over the original timeline.  Scribus 1.6 actually
seems to me to be more further aways from a release than it was last
August.

> But if a 1.6 release is very close, it's also an option to ask FTP
> masters to force-remove qt4 despite rendering scribus uninstallable.

I just wrote to upstream; if they don't stop me, I'll go ahead and
package 1.5, which is not considered "production ready", but really
nobody can notice how it isn't :)

Either way, expect something to happen in 1-2 weeks.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: affects 877507

[Debian Bug Tracking System]

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

> affects 877507 - ppx-sexp-conv
Bug #877507 [src:ppx-core] ppx-core FTBFS: E: Cannot find external tool 
'ocamlbuild'
Removed indication that 877507 affects 
> thanks
Stopping processing here.

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

Bug#948801: refcard: FTBFS: pdfjoin: Command not found

[Mattia Rizzolo]

Source: refcard
Version: 10.5
Severity: serious
Tags: ftbfs

Dear maintainer,

during a rebuild in a standard sid chroot, your package failed to build:

===
xsltproc --nonet --novalid fo.xsl refcard-vi.dbk > refcard-vi-a4.fo
xsltproc --nonet --novalid fo.xsl refcard-zh_CN.dbk > refcard-zh_CN-a4.fo
xsltproc --nonet --novalid fo.xsl refcard-zh_TW.dbk > refcard-zh_TW-a4.fo
Making portrait pages on USletter paper (99mmx210mm)
Build refcard-nl.dbk.pdf
Making portrait pages on USletter paper (99mmx210mm)
Build the listings...
Build the listings...
Making portrait pages on USletter paper (99mmx210mm)
XSLT stylesheets DocBook - LaTeX 2e (0.3.10)
===
Making portrait pages on USletter paper (99mmx210mm)
pdfjoin --vanilla --fitpaper true --outfile refcard-en-lt.s.pdf.x.pdf 
refcard-en-lt.s.pdf empty.pdf empty.pdf
make[2]: pdfjoin: Command not found
make[2]: *** [Makefile:64: refcard-en-lt.t.pdf] Error 127
make[2]: *** Waiting for unfinished jobs


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: py2removal bugs severity updates - 2020-01-13 15:36:00.141844+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-whoosh is a module and has 0 external rdeps or not in testing
> severity 938263 serious
Bug #938263 [src:python-whoosh] python-whoosh: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#948763: z3: cannot be built on buildds

[Fabian Wolff]

On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne  wrote:
> Source: z3
> Version: 4.8.7-3
> Severity: serious
> 
> z3 cannot be built on buildds, because its Build-Depends cannot be
> satisfied on buildds. Failing to build on buildds is a serious problem.

It builds now on all but three architectures, including, in particular, all
release architectures.

> [...]

Thanks for your suggestions, but I'm not very familiar with how Multi-Arch
annotations should be used; I just accepted a patch to make the z3 package
more cross-build friendly (see #948109).

Can you give me a patch where you set the build dependency annotations in a
sound way that also works for cross-building? Otherwise, I would have to
simply remove all annotations again in order to fix this bug (but clearly,
that would not be the most desirable solution).

I would also be happy to use the nojava build profile that you suggested,
but again, I'm not familiar with this technique, and from what I've heard,
there are still some problems e. g. with using "dh-sequence-javahelper
 ". But if somebody gave me a patch, I'd be happy to apply it.

Thanks for your help!
Fabian

Bug#925629: aghermann: ftbfs with GCC-9

[Matthew Fernandez]

Sorry, I didn’t have much context for the original issue and was probably too 
terse in my responses. Some more elaboration inline below.

> On Jan 13, 2020, at 01:14, Andreas Tille  wrote:
> 
> On Sun, Jan 12, 2020 at 02:08:56PM -0800, Matthew Fernandez wrote:
>> 
>>> On Jan 12, 2020, at 12:49, Andreas Tille  wrote:
>>> 
>>> Hi,
>>> 
>>> I'm wondering how this bug
>>> 
>>> 
>>> rk1968/rk1968.cc: In lambda function:
>>> rk1968/rk1968.cc:237:103: error: expected '{' before '->' token
>>> 237 | auto make_error_return = [&L] ( const char* fmt, ...) 
>>> __attribute__ ((format (printf, 2, 3))) -> int
>>> |   
>>> ^~
>>> 
>>> 
>>> with gcc 9 can be fixed in aghermann.  Any help would be appreciated.
>> 
>> Turning this into a C++11 attribute ([[gnu::format(printf, 2, 3)]]) makes 
>> the parse error go away, but -Wattributes still indicates GCC is ignoring it.
> 
> I admit I do not understand your "but -Wattributes ...".  I can confirm
> that this patch[1] builds the package successfully.

-Wattributes is a flag to GCC to enable warnings about attributes. What I did 
to experiment was extract the code you’d quoted into an isolated context:

$ cat - >test.cc  < int
  {
return 0;
  }
}
EOT
$ g++ -std=c++11 -c -Wattributes test.cc

>> You might need to bump that GCC issue with some evidence that the bug still 
>> exists and see what the maintainers say.
> 
> I need to admit that I understand so less from all the gcc issues you
> tried to explain - I do not even have any idea what C++ attributes are.
> I simply cared for that Debian bug since nobody else did. :-(
> So I feel really incompetent to discuss this with gcc maintainers but
> I'd welcome if you bring it up there.

GCC attributes like the __attribute__ example here are a mechanism for 
annotating C/C++ code with things not covered by the ISO standards, but 
supported by compiler extensions. Attributes can be applied to many things 
including variables and functions, and the function attributes are documented 
at https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html 
. These days Clang 
also understands many of the GCC attributes.

The particular one in question here is telling the compiler that the lambda 
function being defined has similar behavior to the libc printf function. The 
integer parameters say a printf format string appears as the second argument 
and the first varargs parameter is the third argument. This looks off by one, 
but I think the captured local (&L) counts as the first parameter. The only 
thing the compiler uses this attribute for is to detect calls to this lambda 
with incorrect arguments and emit warnings for them.

The C++11 standard brought in a more commonly supported way of declaring 
attributes using square brackets. Unfortunately the standard does not support 
many common attributes and you still need to use a “gnu::” prefix to access the 
GCC-specific attributes. Hence, “[[gnu::format(printf, 2, 3)]]” being the C++11 
equivalent of this.

>> If you need to bypass this urgently, I would recommend deleting the 
>> attribute as that particular one is only used to aid the compiler in 
>> creating warnings.
> 
> Hmmm, as I said my patch[1] works and I just have the gut feeling (as I
> said I have no competence!) that this might be better than to delete the
> attribute.  If not would you mind sending an alternative patch which is
> better in your opinion?

Lambda functions, which are already being used in this code, are a C++11 
feature as are this style of attributes. So I imagine it would be acceptable to 
upstream to take your patch. Having said that, when I did this in my experiment 
code above the compiler warned that it was ignoring this attribute as it 
thought it was being applied to the trailing “int”.

I re-read the GCC issue and realized I’d misread Jonathan Wakely’s comments. 
The issue is actually still open and Jonathan was just noting that r265787 
introduced the bug, not fixed it. So I think what we’re seeing is consistent 
with the GCC maintainers’ view.

I would suggest proposing your patch upstream. Although its primary purpose is 
working around a compiler bug, it’s also an objective improvement in 
modernizing the code base.

> Thanks again
> 
>   Andreas.
> 
> 
>>  [0]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90333 
>> 
> 
> [1] 
> https://salsa.debian.org/med-team/aghermann/blob/master/debian/patches/workaround_gcc-9_issue.patch
>  
> 
> 
> -- 
> http://fam-tille.de 

Bug#945920: Random Chromium crashes

[Jaap Joris Vens]

Hi all,

The status so far is that we have a patch that solves the problem by
re-enabling [tracing][1], but the reason that tracing was disabled in the
first place is because it depends on minified javascript. You can recompile
chromium yourself but this is not a permanent solution.

It seems that nobody has started the effort of trying to write a new patch
that removes the tracing functionality from the upstream source code, or to
find the bug and fix the way it's removed now.

Dear maintainer, could you please chime in and let us know how we could
help?

Greetings,
JJ

[1]: https://www.chromium.org/developers/how-tos/trace-event-profiling-tool

On Mon, Jan 13, 2020 at 09:52:36AM -0500, Джонатан Вашингтон wrote:

Dear package maintainer(s),

In case it is useful information, this issue affects me as well, and
has for several weeks.  Chromium is usable for only a few minutes
before it crashes with a backtrace almost identical to those already
shared.  It does not seem to matter how many or what kind of pages are
open, or whether the browser is actively being used / receiving window
manager focus or not.

Please let me know if there is anything I can do to help identify the
problem or test a fix.

--
Jonathan

--
To unsubscribe, send mail to 945920-unsubscr...@bugs.debian.org.

Bug#948527: marked as done (gtkboard: Always hang up after selecting a game.)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 14:54:29 +
with message-id 
and subject line Bug#948527: fixed in gtkboard 0.11pre0+cvs.2003.11.02-10
has caused the Debian Bug report #948527,
regarding gtkboard: Always hang up after selecting a game.
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.)


-- 
948527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtkboard
Version: 0.11pre0+cvs.2003.11.02-9+b1
Severity: grave
Tags: patch

Dear Maintainer,

 The gtkboard always hangs up after selecting a game in Game menu.
It causes gtkboard completely useless.
 And when it hangs up,the following message is shown in stdin, 
  ' *** stack smashing detected ***:  terminated '

 I report this problem, and I attach the patch to fix this problem.
 In my Debian box, this patch works well.

 Would you release a newer package applied to this patch?

FYI:
  The root cause of this problem is the buffer overflow in
channel_process_input() in src/engine.c. The channel_process_input()
invokes g_io_channel_read; however, the type of the last argument of
g_io_channel should be 'gsize(unsigned long)',but it is 'int'. 

  It causes an overflow in the stack, and 'stack smashing' kills the
forked process. Then the parent process, which handles GUI, keeps
waiting for the response of the killed process forever, and it looks
hanging up.

 Additionally, I happen to find a possibility of 1 bytes of buffer
overflow. The linbuf in channel_process_input() has 4096bytes, but
there is a possibility that '\0' puts in 4097th. This patch fixes it
also.

 Finally, this problem comes from upstream. However, the site of
upstream says maintenance is over. So, I haven't reported upstream.
See. http://gtkboard.sourceforge.net/

Regards,
--
 Takahide Nojima

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

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

Versions of packages gtkboard depends on:
ii  libatk1.0-0  2.34.1-1
ii  libc62.29-8
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.10.1-2
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-2
ii  libglib2.0-0 2.62.4-1
ii  libgtk2.0-0  2.24.32-4
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libpangoft2-1.0-01.42.4-8
ii  libsdl-mixer1.2  1.2.12-16+b1
ii  libsdl1.2debian  1.2.15+dfsg2-5

gtkboard recommends no packages.

gtkboard suggests no packages.

-- no debconf information
diff -u -N -r a/debian/changelog b/debian/changelog
--- a/debian/changelog	2018-07-29 19:02:29.0 +0900
+++ b/debian/changelog	2020-01-10 04:19:52.749057611 +0900
@@ -1,3 +1,13 @@
+gtkboard (0.11pre0+cvs.2003.11.02-10) UNRELEASED; urgency=medium
+
+  * Fix stack overflow in engine.c.
+It has 2 overflows.
+  -The 'linebuf' have 4096 bytes,but '\0' puts in 4097th.
+  -The last argument of g_io_channel_read should be 
+   'unsigned long' not 'int'.
+
+ -- Takahide Nojima   Mon, 06 Jan 2020 02:01:42 +0900
+
 gtkboard (0.11pre0+cvs.2003.11.02-9) unstable; urgency=medium
 
   * recent list crash bug fix, thanks to Nelson Benítez León (closes: #820595)
diff -u -N -r a/debian/patches/fixed-stack-smash.patch b/debian/patches/fixed-stack-smash.patch
--- a/debian/patches/fixed-stack-smash.patch	1970-01-01 09:00:00.0 +0900
+++ b/debian/patches/fixed-stack-smash.patch	2020-01-10 03:09:20.792565886 +0900
@@ -0,0 +1,15 @@
+--- a/src/engine.c
 b/src/engine.c
+@@ -345,10 +345,10 @@
+ 
+ static gboolean channel_process_input ()
+ {
+-	static char linebuf[4096];
++	static char linebuf[4096+1];
+ 	char *linep = linebuf;
+ 	char *line;
+-	int bytes_read;
++	gsize bytes_read;
+ #if GLIB_MAJOR_VERSION > 1
+ 	// we need to call this again because we will get new events before returning
+ 	// from this function
diff -u -N -r a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series	2018-07-29 19:02:29.0 +0900
+++ b/debian/patches/series	2020-01-06 02:07:43.243615139 +0900
@@ -1 +1,2 @@
 debian-changes
+fixed-stack-smash.patch
--- End Message ---
--- Begin Message ---
Source: gtkboard
Source-Version: 0.11pre0+cvs.2003.11.02-10

We believe that the bug you 

Bug#945920: Random Chromium crashes

[Джонатан Вашингтон]

Dear package maintainer(s),

In case it is useful information, this issue affects me as well, and
has for several weeks.  Chromium is usable for only a few minutes
before it crashes with a backtrace almost identical to those already
shared.  It does not seem to matter how many or what kind of pages are
open, or whether the browser is actively being used / receiving window
manager focus or not.

Please let me know if there is anything I can do to help identify the
problem or test a fix.

--
Jonathan

Bug#948421: marked as done (python-irc ftbfs with current pytest)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 14:55:07 +
with message-id 
and subject line Bug#948421: fixed in python-irc 8.5.3+dfsg-5
has caused the Debian Bug report #948421,
regarding python-irc ftbfs with current pytest
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.)


-- 
948421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-irc
Version: 8.5.3+dfsg-4
Severity: serious
Tags: sid bullseye

[...]
builtins.Failed: [pytest] section in setup.cfg files is no longer supported,
change to [tool:pytest] instead.
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/python-irc-8.5.3+dfsg/.pybuild/cpython2_2.7_irc/build; python2.7
-m pytest -k "not test_version"
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:21: build] Error 255


There is a new upstream version 18.0.0 available.
--- End Message ---
--- Begin Message ---
Source: python-irc
Source-Version: 8.5.3+dfsg-5

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

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-irc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 00:47:15 +1100
Source: python-irc
Architecture: source
Version: 8.5.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 937845 948421
Changes:
 python-irc (8.5.3+dfsg-5) unstable; urgency=medium
 .
   * The “Hiroshi Tanaka” release.
 .
   [ Ben Finney ]
   * Use current HTTPS URL for copyright format declaration.
   * Declare conformance to “Standards-Version: 4.4.1”.
   * Declare Debhelper compatibility level 12.
   * debian/compat:
 * Remove obsolescent configuration file.
   * Remove redundant dependency on ‘debhelper’.
 The ‘debhelper-compat’ dependency brings the correct packages.
   * Update copyright years for Debian packaging work.
   * Release Debian packaging work under terms of GPLv3.
   * Update copyright years for upstream work.
   * Update URL for homepage of upstream project.
   * Update VCS URLs for Debian packaging.
   * Describe current source package management in ‘README.source’.
   * Update years of publication in Debian package copyright notices.
   * Record upstream metadata in a DEP-12 format document.
   * Don't build the Python 2 binary package.
 Closes: bug#937845.
   * Remove Python 2 build dependencies.
   * Update patch for removal of ‘hgtools’ support.
   * Add patch to correct obsolete name for tool configuration section.
 Closes: bug#948421.
   * Move Git-BuildPackage specific option to its configuration file.
   * Specify the current compression for the upstream source tarball.
   * debian/source/options:
 * Remove empty configuration file.
   * Specify the package build system does not require root privilege.
 .
   [ Ondřej Nový ]
   * Remove specification of minimum Python versions.
 These are now satisfied by all currently supported Debian releases.
   * Use HTTPS URL for PyPI redirector.
Checksums-Sha1:
 5325f7eef3b8009a4ec23195f99e50686596fac0 1988 python-irc_8.5.3+dfsg-5.dsc
 b0e743490d25c1b36638eb01139360498ac65291 7460 
python-irc_8.5.3+dfsg-5.debian.tar.xz
 fe8a9bf50650bbf27acab6fac329f98460b89e39 6850 
python-irc_8.5.3+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 9b05ee13721cb5fac127aee52251b6cd549b2f36908123e90558ef592a1df430 1988 
python-irc_8.5.3+dfsg-5.dsc
 6f90a1d92fc6a807084132a1bdb2480e73a358ca0bed7601a8e9abca578e2d85 7460 
python-irc_8.5.3+dfsg-5.debian.tar.xz
 1e37d07fab71c354dbbaaec2fc55b185da635a63eb3ae750c346c40c2604e6f6 6850 
python-irc_8.5.3+dfsg-5_amd64.buildinfo
Files:
 220992f47c4b6d0308f3285c6070bae2 1988 python optional 
python-irc_8.5.3+dfsg-5.dsc
 cfa00f321b1f4630c164ecf634adaf8a 7460 python optional 
python-irc_8.5.3+dfsg-5.debian.tar.xz
 84e5ead4cb388394ecc61385afca4232 6850 python optional 
python-irc_8.5.3+dfsg-5_amd64.buildinfo

-BEGIN PGP SIG

Bug#937845: marked as done (python-irc: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 14:55:07 +
with message-id 
and subject line Bug#937845: fixed in python-irc 8.5.3+dfsg-5
has caused the Debian Bug report #937845,
regarding python-irc: 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.)


-- 
937845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-irc
Version: 8.5.3+dfsg-4
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:python-irc

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: python-irc
Source-Version: 8.5.3+dfsg-5

We believe that the bug you reported is fixed in the latest version of
python-irc, 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.
Ben Finney  (supplier of updated python-irc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Jan 2020 00:47:15 +1100
Source: python-irc
Architecture: source
Version: 8.5.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 937845 948421
Changes:
 python-irc (8.5.3+dfsg-5) unstable; urgency=medium
 .
   * The “Hiroshi Tanaka” release.
 .
   [ Ben Finney ]
   * Use current HTTPS URL for copyright format declaration.
   * Declare conformance to “Standards-Version: 4.4.1”.
   * Declare Debhelper compatibility level 12.
   * debian/compat:
 * Remove obsolescent configuration file.
   * Remove redundant dependency on ‘debhelper’.
 The ‘debhelper-compat’ dependency brings the correct packages.
   * Update copyright years for Debian packaging work.
   * Release Debian packaging work under terms of GPLv3.
   * Update copyright years for upstream work.
   * Update URL for homepage of upstream project.
   * Update VCS URLs for Debian packaging.
   * Describe current source p

Bug#947109: marked as done (sunpy: FTBFS with Python 3.8)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 13:49:35 +
with message-id 
and subject line Bug#947109: fixed in sunpy 1.1.0-1
has caused the Debian Bug report #947109,
regarding sunpy: FTBFS 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.)


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

Hi Maintainer

A recent rebuild of sunpy with Python 3.8 failed [1].
I've copied what I hope is the relevant part of the log below.

A patch is available from Ubuntu [2].

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=sunpy
[2] 
https://launchpadlibrarian.net/448213313/sunpy_1.0.3-2_1.0.3-2ubuntu2.diff.gz


_ test_sysinfo _

def test_sysinfo():
output = sunpy.util.get_sys_dict()
assert isinstance(output, dict)
>   sunpy.system_info()

sunpy/util/tests/test_sysinfo.py:7:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

def system_info():
"""
Takes dictionary from sys_info() and prints the contents in an
attractive
fashion.
"""
sys_prop = get_sys_dict()

# title
print("==")
print("SunPy Installation Information")
print("==\n")

# general properties
print("###")
print("General")
print("###")
# OS and architecture information

for sys_info in ['Time', 'System', 'Processor', 'Arch', 'SunPy']:
print('{} : {}'.format(sys_info, sys_prop[sys_info]))

if sys_prop['System'] == "Linux":
>   distro = " ".join(platform.linux_distribution())
E   AttributeError: module 'platform' has no attribute
'linux_distribution'

sunpy/util/sysinfo.py:121: AttributeError
--- End Message ---
--- Begin Message ---
Source: sunpy
Source-Version: 1.1.0-1

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated sunpy 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, 13 Jan 2020 13:18:02 +0100
Source: sunpy
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 947109
Changes:
 sunpy (1.1.0-1) unstable; urgency=low
 .
   * New upstream version 1.1.0. Closes: #947109
   * Rediff patches. Remove xfail mark for test fixed upstream
   * Push Standards-Version to 4.4.1. No changes needed
   * Call pytest in CI test
   * Fix Python version for requiring importlib_resources
Checksums-Sha1:
 5ea10a815d3e1d520c6c12c7634843f7a24fd194 2668 sunpy_1.1.0-1.dsc
 a264004ea7cf6824f13cfc4f65038629298036a3 7973210 sunpy_1.1.0.orig.tar.gz
 66fc75b229675b87cf266e16ba69ce3ac2f5f1c5 6136 sunpy_1.1.0-1.debian.tar.xz
Checksums-Sha256:
 4115fadbdb39a94bae7882a44fa0022bb6ccc2aa9db9d39083e63ebad3135dcb 2668 
sunpy_1.1.0-1.dsc
 19bf613eac361a7845869ad567bac5e274f5eafca9673eeb0b3e779e0788c0cc 7973210 
sunpy_1.1.0.orig.tar.gz
 4f620d6f3c577df35563f5d9be104e7e6659929536f26b90df8a862ef1a69b15 6136 
sunpy_1.1.0-1.debian.tar.xz
Files:
 afdaa9c204c22575f46eec491da5babd 2668 python optional sunpy_1.1.0-1.dsc
 e082e916663f03f2540562324ddc909f 7973210 python optional 
sunpy_1.1.0.orig.tar.gz
 30c7b8d219d99b446e8eda8394d26934 6136 python optional 
sunpy_1.1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl4ccqUACgkQcRWv0HcQ
3PdtkhAArAn6wQeH0WDtMUXoWC1BiIUAKcrFBT58JVsBHpYAoxCu1YqwewYNjKfx
zvsxeLAIjqXnO2fFFF3mr4TJBGuVKiXnGE7l3fhg7WVi1muOhxgRuETrFfQ+AFYx
Hzfer5wKa10QnfJhh9qHavQWKnxrq5LQgR/RnPpWViO0DF8Lc/E9BzIfU9nHzG3a
6e+RheQRazSub85+vbb6hV2Au4XRyhbfwIn24cPdJrUUEFIBndjWfcqSAxzGHfjI
TjYz0Zj8WbBPM9GRlB/EdShqkwa0sF8FbGpXx0bt2BcuzfwcHENAKTYQSrmhu+OM
XjiAA1FmvmHbksakY0eG8RyaJ3nrgPnepNBYVHU4mEHZCmES

Bug#948790: marked as done (gambas3 ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 14:28:46 +0100
with message-id <216807c4-9c2f-0a6b-de40-056e93199...@debian.org>
and subject line Re: gambas3 ftbfs in unstable
has caused the Debian Bug report #948790,
regarding gambas3 ftbfs in unstable
to be marked as done.

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

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


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

[...]
Making all in src
make[5]: Entering directory '/<>/gb.db.postgresql/src'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
-I/usr/include/postgresql/ -I/usr/include/postgresql/12/server/
-I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2
-pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o gb_db_postgresql_la-main.lo `test -f 'main.c' ||
echo './'`main.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/postgresql/
-I/usr/include/postgresql/12/server/
-I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2
-pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c main.c  -fPIC -DPIC -o 
.libs/gb_db_postgresql_la-main.o
main.c: In function ‘conv_type’:
main.c:338:8: error: ‘ABSTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  338 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:338:8: note: each undeclared identifier is reported only once for each
function it appears in
main.c:339:8: error: ‘RELTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  339 |   case RELTIMEOID:
  |^~
  |TIMEOID
main.c: In function ‘conv_data’:
main.c:421:8: error: ‘ABSTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  421 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:422:8: error: ‘RELTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  422 |   case RELTIMEOID:
  |^~
  |TIMEOID
make[5]: *** [Makefile:496: gb_db_postgresql_la-main.lo] Error 1
make[5]: Leaving directory '/<>/gb.db.postgresql/src'
make[4]: *** [Makefile:438: all-recursive] Error 1
make[4]: Leaving directory '/<>/gb.db.postgresql'
make[3]: *** [Makefile:370: all] Error 2
make[3]: Leaving directory '/<>/gb.db.postgresql'
make[2]: *** [Makefile:437: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:378: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:9: build] Error 255
--- End Message ---
--- Begin Message ---
I uploaded a fixed version in sid some minutes ago!

Closing!

G.

On Mon, 13 Jan 2020 11:43:04 +0100 Matthias Klose  wrote:
> Package: src:gambas3
> Version: 3.13.0-1
> Severity: serious
> Tags: sid bullseye
> 
> [...]
> Making all in src
> make[5]: Entering directory '/<>/gb.db.postgresql/src'
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
> -I/usr/include/postgresql/ -I/usr/include/postgresql/12/server/
> -I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2
> -pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os 
> -g
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c -o gb_db_postgresql_la-main.lo `test -f 'main.c' ||
> echo './'`main.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/postgresql/
> -I/usr/include/postgresql/12/server/
> -I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2
> -pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os 
> -g
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c main.c  -fPIC -DPIC -o 
> .libs/gb_db_postgresql_la-main.o
> main.c: In function ‘conv_type’:
> main.c:338:8: error: ‘ABSTIMEOID’ undeclared (first use in this function); did
> you mean ‘TIMEOID’?
>   338 |   case ABSTIMEOID:
>   |^~
>   |TIMEOID
> main.c:338:8: note: each undeclared identifier is reported only once for each
> function it appears in
> main.c:339:8: error: ‘RELTIMEOID’ undeclared (first use in this function); did
> you mean ‘TIMEOID’?
>   339 |   case RELTIMEOID:
>   | 

Processed: Re: gnubg: Crashes on launch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932351 {Done: Russ Allbery } [gnubg] gnubg: Crashes on 
launch
Added tag(s) pending.

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

Bug#932351: gnubg: Crashes on launch

[Andreas Beckmann]

Followup-For: Bug #932351
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948796


Andreas

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

[Bjørn Mork]

Pierrick CHANTEUX  writes:

> This bug resulted in complete system breakage and I couldn't boot
> anymore (systemd failing to load Kernel modules). I can guarantee that
> this isn't only cosmetic.
>
> I believe this isn't related to initramfs-tools, because downgrading
> kmod and libkmod2 from version 26+20191223-1 to version 26-3 fixes the
> issue. Initramfs now build (and run) correctly.

IMHO this is probably an unrelated bug in the same kmod upgrade.  You
should report it as such, which the full log output and a subject
decribing the issue instead of the bogus error message.

The logspam caused by the lookup_builtin_file() bug makes it hard to
spot real errors, but hopefully there is some clue to your problem there
too.



Bjørn

Bug#948549: pgadmin3: Segfault when trying toi start query tool

[Christoph Berg]

Re: To Erwin Brandstetter 2020-01-10 <20200110140734.ge30...@msg.df7cb.de>
> I can revert to the old wxgtk package on the older distributions, but
> maybe we have to accept that pgadmin3 is dead now and ultimately
> remove it from unstable.

I just updated the pgadmin3 packages on apt.pg.o to use
libwxgtk3.0-dev again instead of libwxgtk3.0-gtk3-dev on anything but
unstable and bullseye.

Christoph

Bug#936099: marked as done (rust-num-traits: test failure on i386)

[Debian Bug Tracking System]

Your message dated Mon, 13 Jan 2020 11:34:44 +
with message-id 
and subject line Bug#936099: fixed in rust-num-traits 0.2.11-1
has caused the Debian Bug report #936099,
regarding rust-num-traits: test failure on i386
to be marked as done.

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

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


-- 
936099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-num-traits
Version: 0.2.8-1
Severity: serious
Forwarded: https://github.com/rust-num/num-traits/issues/124

Hello, looks like enabling the testsuite resulted in a failure on i386 
architecture.
Could you please have a look?
thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: rust-num-traits
Source-Version: 0.2.11-1

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

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

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated rust-num-traits 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Jan 2020 09:05:19 +0100
Source: rust-num-traits
Architecture: source
Version: 0.2.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Andrej Shadura 
Closes: 936099
Changes:
 rust-num-traits (0.2.11-1) unstable; urgency=medium
 .
   * Team upload.
   * Package num-traits 0.2.11 from crates.io using debcargo 2.4.0
 Closes: #936099
   * Temporarily disable libm.
Checksums-Sha1:
 b86e3400e5b4a89e626d5bf11e937f50d547c9c1 1887 rust-num-traits_0.2.11-1.dsc
 5bd014769824d9418acfba2af5c2bb2cb867420c 42000 
rust-num-traits_0.2.11.orig.tar.gz
 e0df32be3442af52231c36d8833b7cceae11e3c6 2724 
rust-num-traits_0.2.11-1.debian.tar.xz
 f37f0cd9fa3ce4e2de62fa814be89204bfc9ec66 8098 
rust-num-traits_0.2.11-1_source.buildinfo
Checksums-Sha256:
 68ebc01f04a0b69e8d0b3bfd9f39a811bd22b63485af80fcb404de2c8323dd5c 1887 
rust-num-traits_0.2.11-1.dsc
 c62be47e61d1842b9170f0fdeec8eba98e60e90e5446449a0545e5152acd7096 42000 
rust-num-traits_0.2.11.orig.tar.gz
 dd55339f5129fa90c82f1edd80230d0f4e08cd006aece3dc0896eff13b2b9a95 2724 
rust-num-traits_0.2.11-1.debian.tar.xz
 a63ff84f0eebed57e15f16e51a93f9ae9bb93901c26647306f8efcc07de6f331 8098 
rust-num-traits_0.2.11-1_source.buildinfo
Files:
 c45c0604f85dbf38d1bfa4e91a62b31b 1887 rust optional 
rust-num-traits_0.2.11-1.dsc
 c3df6ec550943c6ccd356272db8eb202 42000 rust optional 
rust-num-traits_0.2.11.orig.tar.gz
 400afc472e248fef2d1fced552035e75 2724 rust optional 
rust-num-traits_0.2.11-1.debian.tar.xz
 8d4668bb77847558b5df5f655d98d589 8098 rust optional 
rust-num-traits_0.2.11-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl4cU6AACgkQXkCM2RzY
OdJdNwf/ReQAxhkxIL/BzyvLId3FfrqNldV/QySSB6daWulFr89GRzCwyS9d45E6
E8ZgehnNK1vvb0g27m09f6MROIHFFbtzUptw7kWBjHyuPvr/PL5tPBRGmfUPdY+a
UcfEkMm9Uyim1OOzwQQob98RUjtPdt6gzNgVo1lQuy5fMOfmA8FSO98kXgxR9mXY
FmmyU/VOfiZNgG7O63hDaDENkIiy4o7CtgxkFcpH4XQ7Yw22UdWKY81UUmldNTic
BtX6DQcsAR8FpcQ/f9xHPV/aCIoPka50i8hY2tw7se0iZD3H9Jp6gsghL3G32VH8
W2EsCLKDK/O5avZqsWqZ6GT8uU0UOA==
=43Po
-END PGP SIGNATURE End Message ---

Bug#948789: racket ftbfs at least on armhf, and doesn't migrate

[David Bremner]

Matthias Klose  writes:

> Package: src:racket
> Version: 7.5+dfsg2-1
> Severity: serious
> Tags: sid bullseye
>
> racket ftbfs at least on armhf, and doesn't migrate:
>

Yup, thanks for filing. I had a look at it, but I didn't get very far. I
also didn't get any response on #debian-arm (which is obviously not the
most official way to ask for help).

d

Processed: tagging 948789

[Debian Bug Tracking System]

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

> tags 948789 + help
Bug #948789 [src:racket] racket ftbfs at least on armhf, and doesn't migrate
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#907008: mod-gnutls FTBFS: FAIL: test-16_view-status.bash

[Andreas Beckmann]

Followup-For: Bug #907008

Hi,

I tried backporting the fix to stretch (which is trivial), but the
testsuite fails with 4 more failures on stretch:

FAIL: test-18_client_verification_wrong_cert.bash
FAIL: test-23_TLS_reverse_proxy_mismatched_priorities.bash
FAIL: test-22_TLS_reverse_proxy_crl_revoke.bash
FAIL: test-21_TLS_reverse_proxy_wrong_cert.bash


Andreas

Bug#948790: gambas3 ftbfs in unstable

[Bastian Germann]

duplicate of #948783

Bug#948790: gambas3 ftbfs in unstable

[Matthias Klose]

Package: src:gambas3
Version: 3.13.0-1
Severity: serious
Tags: sid bullseye

[...]
Making all in src
make[5]: Entering directory '/<>/gb.db.postgresql/src'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
-I/usr/include/postgresql/ -I/usr/include/postgresql/12/server/
-I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2
-pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o gb_db_postgresql_la-main.lo `test -f 'main.c' ||
echo './'`main.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/postgresql/
-I/usr/include/postgresql/12/server/
-I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2
-pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c main.c  -fPIC -DPIC -o 
.libs/gb_db_postgresql_la-main.o
main.c: In function ‘conv_type’:
main.c:338:8: error: ‘ABSTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  338 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:338:8: note: each undeclared identifier is reported only once for each
function it appears in
main.c:339:8: error: ‘RELTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  339 |   case RELTIMEOID:
  |^~
  |TIMEOID
main.c: In function ‘conv_data’:
main.c:421:8: error: ‘ABSTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  421 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:422:8: error: ‘RELTIMEOID’ undeclared (first use in this function); did
you mean ‘TIMEOID’?
  422 |   case RELTIMEOID:
  |^~
  |TIMEOID
make[5]: *** [Makefile:496: gb_db_postgresql_la-main.lo] Error 1
make[5]: Leaving directory '/<>/gb.db.postgresql/src'
make[4]: *** [Makefile:438: all-recursive] Error 1
make[4]: Leaving directory '/<>/gb.db.postgresql'
make[3]: *** [Makefile:370: all] Error 2
make[3]: Leaving directory '/<>/gb.db.postgresql'
make[2]: *** [Makefile:437: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:378: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:9: build] Error 255

Bug#948789: racket ftbfs at least on armhf, and doesn't migrate

[Matthias Klose]

Package: src:racket
Version: 7.5+dfsg2-1
Severity: serious
Tags: sid bullseye

racket ftbfs at least on armhf, and doesn't migrate:

[...]
make[6]: Leaving directory '/<>/build/racket'
/usr/bin/make cstartup
make[6]: Entering directory '/<>/build/racket'
/usr/bin/make cstartup_`./racketcgc -cu
/<>/src/racket/src/startup-select.rkt`
make[7]: Entering directory '/<>/build/racket'
./racketcgc -cu /<>/src/racket/src/compile-startup.rkt cstartup.inc
cstartup.zo /<>/src/racket/src/startup.inc
/<>/src/racket/src/schvers.h
make[7]: *** [Makefile:329: cstartup_bytecode] Illegal instruction
make[7]: Leaving directory '/<>/build/racket'
make[6]: *** [Makefile:325: cstartup] Error 2

Bug#942634: apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX)

[Andreas Beckmann]

Followup-For: Bug #942634
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948786


Andreas

Processed: Re: apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #942634 {Done: Eduard Bloch } [apt-cacher-ng] 
apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX)
Added tag(s) pending.

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

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

[Pierrick CHANTEUX]

Hello,

This bug resulted in complete system breakage and I couldn't boot
anymore (systemd failing to load Kernel modules). I can guarantee that
this isn't only cosmetic.

I believe this isn't related to initramfs-tools, because downgrading
kmod and libkmod2 from version 26+20191223-1 to version 26-3 fixes the
issue. Initramfs now build (and run) correctly.

Regards,
-- 
Pierrick CHANTEUX

Bug#948783: gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function)

[Mattia Rizzolo]

On Mon, Jan 13, 2020 at 11:04:05AM +0100, Bastian Germann wrote:
> I fixed the problem upstream and have already prepared a package
> containing that upstream version: #947174. Unfortunately, it introduces
> a new binary package so that it has to pass throught NEW. As a DM I
> cannot upload it there myself but if you like you can do it.

ACK.
I'm quite very busy these days so I can't help you out with this, but
I'm sure Gianfranco may help here, since he has been uploading all the
recent versions himself ^^

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#948783: gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function)

[Bastian Germann]

I fixed the problem upstream and have already prepared a package
containing that upstream version: #947174. Unfortunately, it introduces
a new binary package so that it has to pass throught NEW. As a DM I
cannot upload it there myself but if you like you can do it.

Processed: severity of 948460 is normal, tagging 948460

[Debian Bug Tracking System]

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

> severity 948460 normal
Bug #948460 [xserver-xorg-video-nvidia-legacy-340xx] 
xserver-xorg-video-nvidia-legacy-340xx: Xorg won't start with 
xserver-xorg-video-nvidia-legacy-340xx on testing/Bullseye
Severity set to 'normal' from 'grave'
> tags 948460 + moreinfo unreproducible
Bug #948460 [xserver-xorg-video-nvidia-legacy-340xx] 
xserver-xorg-video-nvidia-legacy-340xx: Xorg won't start with 
xserver-xorg-video-nvidia-legacy-340xx on testing/Bullseye
Added tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

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

Bug#947176: [pkg-netfilter-team] Bug#947176: libiptc.pc non-functional

[Arturo Borrero Gonzalez]

On 1/11/20 12:04 PM, Michael Biebl wrote:
> Hi Arturo
> 
> On Sun, 22 Dec 2019 15:06:02 +0100 Michael Biebl  wrote:
>>
>> 1/ Have a single libiptc-dev package which contains all development files
>> 2/ Have a libip6tc-dev package which contains all development files
>> related to libip6tc, have a libip4tc-dev package which contains all
>> development files related to libip4tc and have libiptc-dev (convenience)
>> package which contains libiptc.pc and depends on both libip6tc-dev and 
>> libip4tc-dev
>>
> 
> Have you decided how you want to proceed from here?
> Would welcome your feedback.
> 

Option 2) is probably the way to go.

I didn't have time to get to this yet. Perhaps @alberto have some spare cycles?

regards.

Bug#948783: gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function)

[Mattia Rizzolo]

Source: gambas3
Version: 3.13.0-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/postgresql/ 
-I/usr/include/postgresql/12/server/ 
-I/usr/include/postgresql/12/server/catalog/ -Wdate-time -D_FORTIFY_SOURCE=2 
-pipe -Wall -Wno-unused-value -fsigned-char -fvisibility=hidden -g -ggdb -Os -g 
-O2 -ffile-prefix-map=/build/1st/gambas3-3.13.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c main.c  -fPIC -DPIC -o 
.libs/gb_db_postgresql_la-main.o
main.c: In function 'conv_type':
main.c:338:8: error: 'ABSTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  338 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:338:8: note: each undeclared identifier is reported only once for each 
function it appears in
main.c:339:8: error: 'RELTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  339 |   case RELTIMEOID:
  |^~
  |TIMEOID
main.c: In function 'conv_data':
main.c:421:8: error: 'ABSTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  421 |   case ABSTIMEOID:
  |^~
  |TIMEOID
main.c:422:8: error: 'RELTIMEOID' undeclared (first use in this function); did 
you mean 'TIMEOID'?
  422 |   case RELTIMEOID:
  |^~
  |TIMEOID
make[5]: *** [Makefile:496: gb_db_postgresql_la-main.lo] Error 1
make[5]: Leaving directory '/build/1st/gambas3-3.13.0/gb.db.postgresql/src'
make[4]: *** [Makefile:438: all-recursive] Error 1
make[4]: Leaving directory '/build/1st/gambas3-3.13.0/gb.db.postgresql'
make[3]: *** [Makefile:370: all] Error 2
make[3]: Leaving directory '/build/1st/gambas3-3.13.0/gb.db.postgresql'
make[2]: *** [Makefile:437: all-recursive] Error 1
make[2]: Leaving directory '/build/1st/gambas3-3.13.0'
make[1]: *** [Makefile:378: all] Error 2
make[1]: Leaving directory '/build/1st/gambas3-3.13.0'
dh_auto_build: make -j16 returned exit code 2
make: *** [debian/rules:9: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#933334: fixed in ugene 33.0+dfsg-1

[Andreas Tille]

Hi Santiago,

On Mon, Jan 13, 2020 at 12:33:15AM +0100, Santiago Vila wrote:
> I don't think this is fixed.

So please feel free to reopen this bug.
 
> Could you please send me a public ssh key of yours, so that
> I can give you access to a machine where this failure
> happens (in buster) and you can see it for yourself?
> 
> I tried many times in many different machines, and
> "dpkg-buildpackage -B" always fail.

I need to try buster.  Its not true for a stretch machine I had easy
access to and for sure its no problem in sid - otherwise I would not
have uploaded.

I can try under buster later.  I admit if I would send you my sshkey
this would possibly open the false hope that I would focus on this issue
in the near future.  We have *lots* of open RC bugs directly affecting
our users more than this package in non-free.  So my preferences are
somewhere else, sorry about this.

I'd love if someone from the team would spent some time into the
issue, thought.

Thanks a lot for your effort in any case

Andreas.

-- 
http://fam-tille.de