Bug#960608: Bison 3.6.1 generates (internal) tokentype and (yyerror) function with same name: _error

[Akim Demaille]

Hi!

> Le 14 mai 2020 à 18:47, Chuan-kai Lin  a écrit :
> 
> Hi Akim,
> 
> I am forwarding a bug report that the libexplain and the fhist Debian
> packages fail to build with Bison 3.6.1.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960608
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libexplain.html
> 
> I have also attached the build log with this email.  Can you look into
> this issue and see if it is a bug in Bison?  Thanks!

In the log file you sent, I see:

> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/build/1st/libexplain-1.4.D001=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wextra -Wl,--as-needed -I. -c 
> libexplain/acl_get_file_or_die.c -o libexplain/acl_get_file_or_die.o 
> >/dev/null 2>&1
> bison -y -d  libexplain/acl_grammar.y
> libexplain/acl_grammar.y:62.16-18: warning: POSIX yacc reserves %type to 
> nonterminals [-Wyacc]
>62 | %type  TAG
>   |^~~
> libexplain/acl_grammar.y:63.19-24: warning: POSIX yacc reserves %type to 
> nonterminals [-Wyacc]
>63 | %type  NUMBER
>   |   ^~
> libexplain/acl_grammar.y:66.18-22: warning: POSIX yacc reserves %type to 
> nonterminals [-Wyacc]
>66 | %type  PERMS
>   |  ^
> libexplain/acl_grammar.y:68.17-20: warning: POSIX yacc reserves %type to 
> nonterminals [-Wyacc]
>68 | %type  NAME
>   | ^~~~
> sed -e 's/[yY][yY]/acl_grammar_/g' -e '//d' -e \
>   '//d' -e '//d' y.tab.c > \
>   libexplain/acl_grammar.yacc.c
> sed -e 's/[yY][yY]/acl_grammar_/g' -e \
>   's/Y_TAB_H/libexplain_acl_grammar_YACC_H/g' y.tab.h > \
>   libexplain/acl_grammar.yacc.h

The last two lines are not coming from Bison, and they are smashing
both YYerror and yyerror to acl_grammar_error.  So of course, it fails.

I don't understand why this is done this way.  The grammar file should use
%define api.prefix {acl_grammar_}, or the build system should pass
-Dapi.prefix={acl_grammar_}, or the sed sequence should be less crude.
I would go for

s/yy/acl_grammar_/g; s/YY/ACL_GRAMMAR_/g;

But if this is not ok, and the package still wants to smash yy and YY
to the same string, you could *prepend* this to the sed grammar:

s/YYerror/yyerror_token/g;

so that yyerror becomes acl_grammar_error, and YYerror become
acl_grammar_error_token.  But of course next time we introduce another
symbol which differs by the case of the prefix, the problem will
be back.

Cheers!

Bug#959798: [Pkg-javascript-devel] Bug#959798: libjs-webrtc-adapter ftbfs with node-grunt-babel 8.0 (using babel 7.4) in experimental

[Pirate Praveen]

On Thu, May 14, 2020 at 5:30 pm, Jonas Smedegaard  
wrote:

No, fails.

The package now checks unit tests during build, and switching to 
Babel 7

causes one of those to fail:

not ok 69 Log suppression "before each" hook for "does not call 
console.log by default"

  Cannot find module ./utils


I think it is a bug in node-browserify-lite (that is cannot handle code 
generated by babel 7). I can see utils.js is present in dist but it did 
not get bundled correctly. I could get the tests to pass when using 
webpack instead of browserify-lite.


With debian/webpack.config.js,

'use strict';
var path = require('path');
var config = {
 target: 'node',
 resolve: {
modules: ['/usr/share/nodejs', '/usr/lib/nodejs'],
 },
 resolveLoader: {
modules: ['/usr/share/nodejs'],
 },
 output: {
   libraryTarget: 'umd'
 },
 module: { rules: [ { use: [ 'babel-loader' ] } ] }
}
module.exports = config;

and calling webpack --config debian/webpack.config.js -n adapter -f umd 
dist/adapter_core5.js -o out/adapter.js


has passing tests. I have pushed my rough changes in babel7 branch. I 
don't use babel-loader here (just copied an old configuration), may be 
you can use babel-loader and pass src/js directly to webpack instead of 
babeljs.

Bug#960143: sagetex: FTBFS in unstable

[Norbert Preining]

Hi John,

> There are strange discrepancies in the tar files and one upload was
> rejected. I will retry.

I manually built a package and worked around the checksum discrepancies,
package is now accepted into unstable.

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#960143: marked as done (sagetex: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 03:18:31 +
with message-id 
and subject line Bug#960143: fixed in sagetex 3.4+ds-2
has caused the Debian Bug report #960143,
regarding sagetex: 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.)


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

Hi Maintainer

Sagetex currently FTBFS in unstable [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sagetex.html


kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 tcrm1000
mkdir: cannot create directory '././nonexistent': Permission denied
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600;
nonstopmode; input tcrm1000
This is METAFONT, Version 2.7182818 (TeX Live 2020/Debian) (preloaded base=mf)

(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/tcrm1000.mf
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exbase.mf)
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/tcrm.mf
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txsymb.mf
 Ok (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exaccess.mf
 Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txpseudo.mf
 Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txaccent.mf
 Ok [0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [27] [29])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txgen.mf
 Ok [100] [109] [98] [99] [108])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txsymbol.mf
 Ok [13] [18] [21] [22] [23] [24] [25] [26] [28] [31] [32] [36] [39] [44]
[45] [46] [42] [47] [60] [61] [62] [77] [79] [87] [110] [91] [93] [94] [95]
[96] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135] [136] [137]
[138] [139] [140] [141] [142] [143] [144] [145] [146] [147] [148] [149]
[150] [151] [152] [153] [154] [155] [156] [157] [158] [159] [160] [161]
[162] [163] [164] [165] [166] [167] [168] [169] [171] [172] [173] [174]
[175] [177] [176] [180] [181] [182] [183] [184] [187] [191] [214] [246])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txromod.mf
 Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txrsuper.mf
 Ok [185] [178] [179] [170] [186])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txrfract.mf
 Ok [188] [189] [190]) ) ) )
(some charht values had to be adjusted by as much as 0.06943pt)
Font metrics written on tcrm1000.tfm.
Output written on tcrm1000.600gf (128 characters, 23548 bytes).
Transcript written on tcrm1000.log.
mktexpk: /tmp/texfonts/pk/ljfour/jknappen/ec/tcrm1000.600pk:
successfully generated.
make[2]: Leaving directory '/build/1st/sagetex-3.4+ds'
/usr/bin/make example.pdf TEXOPTS="-interaction batchmode"
TEXINPUTS=".:_build/DEBIAN/usr/share/texmf/tex/latex/sagetex:_build/:"
PYTHONPATH=_build/DEBIAN/usr/lib/python3.8/dist-packages
VPATH=_build/DEBIAN/usr/share/texmf/tex/latex/sagetex:_build/DEBIAN/usr/lib/python3.8/dist-packages
DOT_SAGE=/build/1st/sagetex-3.4+ds/_test/DOT_SAGE
MPLCONFIGDIR=/build/1st/sagetex-3.4+ds/_test/MPLCONFIGDIR
MAXIMA_USERDIR=/build/1st/sagetex-3.4+ds/_test/MAXIMA_USERDIR
make[2]: Entering directory '/build/1st/sagetex-3.4+ds'
pdflatex -interaction batchmode example.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
make[2]: *** [Makefile:21: example.pdf] Error 1
make[2]: Leaving directory '/build/1st/sagetex-3.4+ds'
make[1]: *** [debian/rules:59: override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/1st/sagetex-3.4+ds'
make: *** [debian/rules:28: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: sagetex
Source-Version: 3.4+ds-2
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated sagetex package)

(This message was gen

Bug#960143: sagetex: FTBFS in unstable

[Norbert Preining]

> > Uploading in the a few minutes, after the binary build succeeded.
> 
> Just a ping in case you've moved on

There are strange discrepancies in the tar files and one upload was
rejected. I will retry.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#960143: sagetex: FTBFS in unstable

[John Scott]

On Mon, 11 May 2020 19:57:52 +0900 Norbert Preining  
wrote:
> Uploading in the a few minutes, after the binary build succeeded.

Just a ping in case you've moved on

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

Processed: linphone: Build-Depends on obsolete package python-pystache

[Debian Bug Tracking System]

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

> severity 943162 serious
Bug #943162 [src:linphone] linphone: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#960609: Cannot install dh-python from Sid

[Kyle Edwards]

On Thu, 2020-05-14 at 17:14 +0200, Matthias Klose wrote:
> most likely a broken mirror.

Thanks for the insight. Whom should I contact to get this fixed?

Bug#936465: Remove python-ecryptfs?

[Scott Talbert]

Does it make sense to just remove the python-ecrpyptfs bindings?  They 
don't seem to have any reverse dependencies and popcon is very low.


Thanks,
Scott

Bug#960458: libreswan: CVE-2020-1763

[Salvatore Bonaccorso]

Hi

Merge request for debian/master at
https://salsa.debian.org/debian/libreswan/-/merge_requests/2/diffs

Regards,
Salvatore

Processed: Re: Bug#960466: fonts-mathematica: does not download

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #960466 [fonts-mathematica] fonts-mathematica: does not download
Severity set to 'grave' from 'important'
> found -1 20
Bug #960466 [fonts-mathematica] fonts-mathematica: does not download
Marked as found in versions mathematica-fonts/20.

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

Bug#936146: archivemail - Python 3 porting

[Scott Talbert]

archivemail seems to be a good candidate to RM due to dead upstream. 
However, it still has a relatively high popcon, so people seem to be using 
it.


I'm willing to take a stab at porting to Python 3 if anyone is available 
to test it?  The port effort doesn't look that bad at first glance, but I 
don't use this package.


Scott

Bug#959650: marked as done (node-autoprefixer: FTBFS: Cannot read property 'bindings' of null)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 21:19:21 +0200
with message-id <108ac9d7-9a4a-af73-b5c1-cd2b01c22...@debian.org>
and subject line Version 9 is in testing now
has caused the Debian Bug report #959650,
regarding node-autoprefixer: FTBFS: Cannot read property 'bindings' of null
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.)


-- 
959650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-autoprefixer
Version: 8.6.5+repack-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> gulp
> [05:06:33] Local gulp not found in /<>
> [05:06:33] Try running: npm install gulp
> [05:06:33] Using globally installed gulp
> [05:06:33] Using gulpfile /<>/gulpfile.js
> [05:06:33] Starting 'default'...
> [05:06:33] Starting 'build'...
> [05:06:33] Starting 'build:lib'...
> [05:06:34] 'build:lib' errored after 415 ms
> [05:06:34] TypeError in plugin "gulp-babel"
> Message:
> Cannot read property 'bindings' of null
> [05:06:34] 'build' errored after 416 ms
> [05:06:34] 'default' errored after 418 ms
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/05/01/node-autoprefixer_8.6.5+repack-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 16696--- End Message ---

Bug#955695: 1.5.2 has different error

[Hans-Christoph Steiner]

I'm trying to build Manas Kashyap's 1.5.2 update, and got a different
error.  And gradle/wrapper/gradle-wrapper.properties says gradle 5.2.1,
so it looks like they might have added some new gradle tricks

Included projects: [root project 'com.ibm.wala', project
':com.ibm.wala-repository', project ':com.ibm.wala.cast', project
':com.ibm.wala.cast.java', project ':com.ibm.wala.cast.test', project
':com.ibm.wala.core', project ':com.ibm.wala.dalvik', project
':com.ibm.wala.scandroid', project ':com.ibm.wala.shrike', project
':com.ibm.wala.tests.ide_feature', project
':com.ibm.wala.tests_feature', project ':com.ibm.wala.util', project
':com.ibm.wala_feature', project ':com.ibm.wala.cast.test:smoke_main',
project ':com.ibm.wala.cast.test:xlator_test', project
':com.ibm.wala.cast:cast']
Keep-alive timer started
Adding Debian repository to project 'com.ibm.wala'
Adding Debian repository to project 'com.ibm.wala-repository'
Adding Debian repository to project 'com.ibm.wala.cast'
Adding Debian repository to project 'com.ibm.wala.cast.java'
Adding Debian repository to project 'com.ibm.wala.cast.test'
Adding Debian repository to project 'com.ibm.wala.core'
Adding Debian repository to project 'com.ibm.wala.dalvik'
Adding Debian repository to project 'com.ibm.wala.scandroid'
Adding Debian repository to project 'com.ibm.wala.shrike'
Adding Debian repository to project 'com.ibm.wala.tests.ide_feature'
Adding Debian repository to project 'com.ibm.wala.tests_feature'
Adding Debian repository to project 'com.ibm.wala.util'
Adding Debian repository to project 'com.ibm.wala_feature'
Adding Debian repository to project 'smoke_main'
Adding Debian repository to project 'xlator_test'
Adding Debian repository to project 'cast'
Evaluating root project 'com.ibm.wala' using build file
'/build/wala-1.5.2/build.gradle'.
Compiling build file '/build/wala-1.5.2/build.gradle' using
SubsetScriptTransformer.
Compiling build file '/build/wala-1.5.2/build.gradle' using
BuildScriptTransformer.

FAILURE: Build failed with an exception.

* Where:
Build file '/build/wala-1.5.2/build.gradle' line: 35

* What went wrong:
A problem occurred evaluating root project 'com.ibm.wala'.
> Could not find method named() for arguments [test] on task set of type
org.gradle.api.internal.tasks.DefaultTaskContainer.

Bug#937166: marked as done (nuitka: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 19:03:33 +
with message-id 
and subject line Bug#937166: fixed in nuitka 0.6.8+ds-1
has caused the Debian Bug report #937166,
regarding nuitka: 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.)


-- 
937166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nuitka
Version: 0.6.1.1+ds-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.  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:nuitka

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: nuitka
Source-Version: 0.6.8+ds-1
Done: Kay Hayen 

We believe that the bug you reported is fixed in the latest version of
nuitka, 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.
Kay Hayen  (supplier of updated nuitka 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, 11 May 2020 16:41:34 +0200
Source: nuitka
Binary: nuitka
Architecture: source all
Version: 0.6.8+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Kay Hayen 
Changed-By: Kay Hayen 
Description:
 nuitka - Python compiler with full language support and CPython compatibil
Closes: 937166
Changes:
 nuitka (0.6.8+ds-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   * Changed dependencies to prefer Debian 11 packages.
 (Closes: #937166).
Checksums-Sha1:
 0a1bacaecf4c056c442e9f7ee1fbf45c6da0d064 2307 nuitka_0.6.8+ds-1.dsc
 93438f91a3239b818f6dbba0183b7909ef86a6da 1127367 nuitka_0.6.8+ds.orig.tar.gz
 5ab1e13e7ce8b7dc1ccc552259c23e5368ade067 11548 nuitka_0.6.8+ds-1.debian.tar.xz
 9b8039a9a811f7bcb1a073ba578e4aa00105cdf3 925188 nuitka_0.6.8+ds-1_all.deb
 ec7847e8b7961998b22128bc8d4591ab8db5b00b 8040 nuitka_0.6.8+ds-1_amd64.buildinfo
Checksums-Sha256:
 bc644e4662dcedb278da4bd8380f18b41015861aea20b1406e1686f2e7f48861 2307 
nuitka_0.6.

Bug#960609: Cannot install dh-python from Sid

[Kyle Edwards]

Package: python3-all
Severity: serious

When attempting to install python3-all:

$ apt-get update
$ apt-get install dh-python

I get the following error:

The following packages have unmet dependencies:
 python3-all : Depends: python3-distutils (>= 3.8.2-1~) but it is not
installable
E: Unable to correct problems, you have held broken packages.

Bug#960623: boost1.67 should build depend on libicu-dev (<< 64)

[Adrian Bunk]

Source: boost1.67
Version: 1.67.0-17
Severity: serious
Control: block 960193 by -1

Changing the icu version changes the libboost_regex ABI.

The libboost-regex*-icu* provides untangle icu transitions from boost
transitions, but reverse dependencies of libboost-regex1.67.0 in buster
depend on libboost-regex1.67.0 not libboost-regex1.67.0-icu63.

A build dependency on libicu-dev (<< 64) would prevent accidental
recompilation with a more recent icu, avoiding problems if people
would install the rebuilt libboost-regex1.67.0 on buster.

If wanted I can NMU this change.

Processed: boost1.67 should build depend on libicu-dev (<< 64)

[Debian Bug Tracking System]

Processing control commands:

> block 960193 by -1
Bug #960193 [release.debian.org] transition: icu
960193 was blocked by: 955114 960263 960237 960239 960236 960241 959756 960374
960193 was not blocking any bugs.
Added blocking bug(s) of 960193: 960623

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

Processed: reassign 960573 to src:yt

[Debian Bug Tracking System]

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

> reassign 960573 src:yt 3.6.0-2
Bug #960573 [src:python3-yt] python3-yt: h5py.File requires access mode to be 
specified
Warning: Unknown package 'src:python3-yt'
Bug reassigned from package 'src:python3-yt' to 'src:yt'.
No longer marked as found in versions python3-yt/3.6.0-2.
Ignoring request to alter fixed versions of bug #960573 to the same values 
previously set
Bug #960573 [src:yt] python3-yt: h5py.File requires access mode to be specified
Marked as found in versions yt/3.6.0-2.
> thanks
Stopping processing here.

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

Bug#956020: mydumper: diff for NMU version 0.9.5-1.2

[Adrian Bunk]

Control: tags 956020 + patch
Control: tags 956020 + pending

Dear maintainer,

I've prepared an NMU for mydumper (versioned as 0.9.5-1.2) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru mydumper-0.9.5/debian/changelog mydumper-0.9.5/debian/changelog
--- mydumper-0.9.5/debian/changelog	2020-03-14 22:15:00.0 +0200
+++ mydumper-0.9.5/debian/changelog	2020-05-08 20:14:50.0 +0300
@@ -1,3 +1,10 @@
+mydumper (0.9.5-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Link mydumper against libm. (Closes: #956020)
+
+ -- Adrian Bunk   Fri, 08 May 2020 20:14:50 +0300
+
 mydumper (0.9.5-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mydumper-0.9.5/debian/patches/0001-Link-mydumper-against-libm.patch mydumper-0.9.5/debian/patches/0001-Link-mydumper-against-libm.patch
--- mydumper-0.9.5/debian/patches/0001-Link-mydumper-against-libm.patch	1970-01-01 02:00:00.0 +0200
+++ mydumper-0.9.5/debian/patches/0001-Link-mydumper-against-libm.patch	2020-05-08 20:14:50.0 +0300
@@ -0,0 +1,26 @@
+From 47b179ace22a2b4f4e5a3e783d6a79cc44a65708 Mon Sep 17 00:00:00 2001
+From: Adrian Bunk 
+Date: Fri, 8 May 2020 20:12:57 +0300
+Subject: Link mydumper against libm
+
+This is required due to mydumper.c using ceil().
+---
+ CMakeLists.txt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index ca9591f..ea4bb85 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -37,7 +37,7 @@ if (WITH_BINLOG)
+ else (WITH_BINLOG)
+   add_executable(mydumper mydumper.c server_detect.c g_unix_signal.c connection.c getPassword.c)
+ endif (WITH_BINLOG)
+-target_link_libraries(mydumper ${MYSQL_LIBRARIES} ${GLIB2_LIBRARIES} ${GTHREAD2_LIBRARIES} ${PCRE_PCRE_LIBRARY} ${ZLIB_LIBRARIES} stdc++)
++target_link_libraries(mydumper ${MYSQL_LIBRARIES} ${GLIB2_LIBRARIES} ${GTHREAD2_LIBRARIES} ${PCRE_PCRE_LIBRARY} ${ZLIB_LIBRARIES} stdc++ m)
+ 
+ 
+ add_executable(myloader myloader.c connection.c getPassword.c)
+-- 
+2.20.1
+
diff -Nru mydumper-0.9.5/debian/patches/series mydumper-0.9.5/debian/patches/series
--- mydumper-0.9.5/debian/patches/series	2018-12-19 11:17:53.0 +0200
+++ mydumper-0.9.5/debian/patches/series	2020-05-08 20:14:50.0 +0300
@@ -1,3 +1,4 @@
 0001-manpage-whatis-description.patch
 0002-dont-install-documentation-source.patch
 0005-fix-cmake-define-ssl
+0001-Link-mydumper-against-libm.patch

Processed: mydumper: diff for NMU version 0.9.5-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 956020 + patch
Bug #956020 [mydumper] mydumper FTBFS on armel/armhf/mips/mipsel , needs to 
link against libm.
Added tag(s) patch.
> tags 956020 + pending
Bug #956020 [mydumper] mydumper FTBFS on armel/armhf/mips/mipsel , needs to 
link against libm.
Added tag(s) pending.

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

Processed: Re: Bug#960573: python3-yt: h5py.File requires access mode to be specified

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:python3-yt 3.6.0-2
Bug #960573 [python3-yt] python3-yt: h5py.File requires access mode to be 
specified
Bug reassigned from package 'python3-yt' to 'src:python3-yt'.
Warning: Unknown package 'src:python3-yt'
Warning: Unknown package 'src:python3-yt'
No longer marked as found in versions yt/3.6.0-2.
Warning: Unknown package 'src:python3-yt'
Warning: Unknown package 'src:python3-yt'
Ignoring request to alter fixed versions of bug #960573 to the same values 
previously set
Warning: Unknown package 'src:python3-yt'
Bug #960573 [src:python3-yt] python3-yt: h5py.File requires access mode to be 
specified
Warning: Unknown package 'src:python3-yt'
The source 'python3-yt' and version '3.6.0-2' do not appear to match any binary 
packages
Marked as found in versions python3-yt/3.6.0-2.
Warning: Unknown package 'src:python3-yt'
> severity -1 serious
Bug #960573 [src:python3-yt] python3-yt: h5py.File requires access mode to be 
specified
Warning: Unknown package 'src:python3-yt'
Severity set to 'serious' from 'normal'
Warning: Unknown package 'src:python3-yt'
> tags -1 ftbfs
Bug #960573 [src:python3-yt] python3-yt: h5py.File requires access mode to be 
specified
Warning: Unknown package 'src:python3-yt'
Added tag(s) ftbfs.
Warning: Unknown package 'src:python3-yt'

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

debian-bugs-rc@lists.debian.org

[Victor Hugo Sánchez Gracida]

https://drive.google.com/file/d/10LwSnTSEk4fe6OrS8cl3kpiyLeLSzQLQ/view?usp=drivesdk

Enviado desde Outlook Mobile

Bug#960619: libzypp1702: Depends on cruft package libsolv0

[Daniel Schepler]

Package: libzypp1702
Version: 17.7.0-1+b1
Severity: serious

The current build of libzypp1702 (17.7.0-1+b1 on amd64) Depends on
libsolv0, while the current version of src:libsolv builds only
libsolv1.

This also cannot be resolved with a new binNMU: src:libzypp
Build-Depends on libsolv0-dev, while the current version of
src:libsolv builds only libsolv1-dev.
-- 
Daniel Schepler

Processed: [bts-link] source package upnp-router-control

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package upnp-router-control
> # 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 #947805 (http://bugs.debian.org/947805)
> # Bug title: Please port to gupnp/gssdp 1.2
> #  * https://bugs.launchpad.net/bugs/1857942
> #  * remote status changed: Confirmed -> Fix-Committed
> #  * closed upstream
> tags 947805 + fixed-upstream
Bug #947805 [upnp-router-control] Please port to gupnp/gssdp 1.2
Added tag(s) fixed-upstream.
> usertags 947805 - status-Confirmed
Usertags were: status-Confirmed.
Usertags are now: .
> usertags 947805 + status-Fix-Committed
There were no usertags set.
Usertags are now: status-Fix-Committed.
> thanks
Stopping processing here.

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

Bug#960615: libbssolv-perl: Build-Depends on cruft package libsolv0-dev

[Daniel Schepler]

Source: libbssolv-perl
Version: 0.17-1
Severity: serious

The source package libbssolv-perl Build-Depends on libsolv0-dev,
whereas the current version of src:libsolv builds only libsolv1-dev.
-- 
Daniel Schepler

Bug#960608: Bison 3.6.1 generates (internal) tokentype and (yyerror) function with same name: _error

[Chuan-kai Lin]

Hi Akim,

I am forwarding a bug report that the libexplain and the fhist Debian
packages fail to build with Bison 3.6.1.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960608
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libexplain.html

I have also attached the build log with this email.  Can you look into
this issue and see if it is a bug in Bison?  Thanks!

Here is the explanation from Andreas Beckmann, who reported the bug:

At least two packages FTBFS with the latest bison with some yyerror related
error message. I had a short look into the libexplain failure and found the
following:

In libexplain/acl_grammar.yacc.c (generated from libexplain/acl_grammar.y),
these bits are new in 3.6.1 (they were not generated by 3.5.3):

...
  enum acl_grammar_tokentype
  {
acl_grammar_EMPTY = -2,
acl_grammar_EOF = 0, /* "end of file"  */
acl_grammar_error = 256, /* error  */
acl_grammar_UNDEF = 257, /* "invalid token"  */
...
  };
...
#define acl_grammar_EOF 0
#define acl_grammar_error 256
#define acl_grammar_UNDEF 257
...

and acl_grammar_error clashes with the existing (generated by 3.6.1 and
3.5.3, in acl_grammar.y this is yyerror())

...
static void
acl_grammar_error(const char *text)
{
...
}

which causes this error during compilation:

y.tab.c:152:27: error: expected identifier or '(' before numeric constant
libexplain/acl_grammar.y:128:1: note: in expansion of macro 'acl_grammar_error'
  128 | yyerror(const char *text)
  | ^
libexplain/acl_grammar.y: In function 'acl_grammar_errorf':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:155:5: note: in expansion of macro 'acl_grammar_error'
  155 | yyerror(buf);
  | ^
libexplain/acl_grammar.y: In function 'acl_grammar_parse':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:470:13: note: in expansion of macro 'acl_grammar_error'
  470 | yyerror
  | ^~~
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1720:7: note: in expansion of macro 'acl_grammar_error'
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1831:3: note: in expansion of macro 'acl_grammar_error'
At top level:
libexplain/acl_grammar.y:105:1: warning: 'result_append' defined but
not used [-Wunused-function]
  105 | result_append(const char *text)
  | ^

This does not look like it is an error in libexplain.
Mon May 11 13:28:49 UTC 2020  I: starting to build libexplain/unstable/amd64 on 
jenkins on '2020-05-11 13:28'
Mon May 11 13:28:49 UTC 2020  I: The jenkins build log is/was available at 
https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_14/12752/console.log
Mon May 11 13:28:49 UTC 2020  I: Downloading source for 
unstable/libexplain=1.4.D001-9
--2020-05-11 13:28:50--  
http://deb.debian.org/debian/pool/main/libe/libexplain/libexplain_1.4.D001-9.dsc
Connecting to 78.137.99.97:3128... connected.
Proxy request sent, awaiting response... 200 OK
Length: 2184 (2.1K)
Saving to: ‘libexplain_1.4.D001-9.dsc’

 0K ..100%  190M=0s

2020-05-11 13:28:50 (190 MB/s) - ‘libexplain_1.4.D001-9.dsc’ saved [2184/2184]

Mon May 11 13:28:50 UTC 2020  I: libexplain_1.4.D001-9.dsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 3.0 (quilt)
Source: libexplain
Binary: explain, libexplain-doc, libexplain51, libexplain-dev
Architecture: any all
Version: 1.4.D001-9
Maintainer: Debian QA Group 
Homepage: http://libexplain.sourceforge.net/
Standards-Version: 4.4.0
Vcs-Browser: https://salsa.debian.org/debian/libexplain
Vcs-Git: https://salsa.debian.org/debian/libexplain.git
Build-Depends: bison, debhelper-compat (= 12), ghostscript, groff, libacl1-dev, 
libcap-dev [linux-any], libtool-bin, linux-libc-dev [linux-any], lsof 
[linux-any], netbase
Package-List:
 explain deb devel optional arch=any
 libexplain-dev deb libdevel optional arch=any
 libexplain-doc deb doc optional arch=all
 libexplain51 deb libs optional arch=any
Checksums-Sha1:
 e191e1e7f066f8cefca8d05c846c3a38931d8410 4770006 
libexplain_1.4.D001.orig.tar.gz
 051e4be36c618b454657db790a7a7920704ee513 43992 
libexplain_1.4.D001-9.debian.tar.xz
Checksums-Sha256:
 28863b65eccc74934e237cac41364cb3c1802c36c9e2318ed0417460fee83f80 4770006 
libexplain_1.4.D001.orig.tar.gz
 4ac59e45f82811b8fd0cf519149d224467f25ea212f161a5ac004241f502d543 43992 
libexplain_1.4.D001-9.debian.tar.xz
Files:
 8fabd3de196bde3ca941cd27c029ff8b 4770006 libexplain_1.4.D001.orig.tar.gz
 078b819d14486f28ebab03884dc6b658 43992 libexplain_1.4.D001-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl1yplIACgkQwpPntGGC
Ws6jGg//ZreHxsvjOCNmKJ3RTjNwNEop3ml1HcRdd0YBVLB28zwOLTB6nAaxip6t
n/btsbm6azsLSRZd5c5WGN9rUPd9S9IZ1Kfln6lVZ3a6m6vg

Bug#960608: marked as forwarded (bison: generates (internal) tokentype and (yyerror) function with same name: _error)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 09:47:46 -0700
with message-id 

has caused the   report #960608,
regarding bison: generates (internal) tokentype and (yyerror) function with 
same name: _error
to be marked as having been forwarded to the upstream software
author(s) bug-bi...@gnu.org

(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.)


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

I am forwarding a bug report that the libexplain and the fhist Debian
packages fail to build with Bison 3.6.1.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960608
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libexplain.html

I have also attached the build log with this email.  Can you look into
this issue and see if it is a bug in Bison?  Thanks!

Here is the explanation from Andreas Beckmann, who reported the bug:

At least two packages FTBFS with the latest bison with some yyerror related
error message. I had a short look into the libexplain failure and found the
following:

In libexplain/acl_grammar.yacc.c (generated from libexplain/acl_grammar.y),
these bits are new in 3.6.1 (they were not generated by 3.5.3):

...
  enum acl_grammar_tokentype
  {
acl_grammar_EMPTY = -2,
acl_grammar_EOF = 0, /* "end of file"  */
acl_grammar_error = 256, /* error  */
acl_grammar_UNDEF = 257, /* "invalid token"  */
...
  };
...
#define acl_grammar_EOF 0
#define acl_grammar_error 256
#define acl_grammar_UNDEF 257
...

and acl_grammar_error clashes with the existing (generated by 3.6.1 and
3.5.3, in acl_grammar.y this is yyerror())

...
static void
acl_grammar_error(const char *text)
{
...
}

which causes this error during compilation:

y.tab.c:152:27: error: expected identifier or '(' before numeric constant
libexplain/acl_grammar.y:128:1: note: in expansion of macro 'acl_grammar_error'
  128 | yyerror(const char *text)
  | ^
libexplain/acl_grammar.y: In function 'acl_grammar_errorf':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:155:5: note: in expansion of macro 'acl_grammar_error'
  155 | yyerror(buf);
  | ^
libexplain/acl_grammar.y: In function 'acl_grammar_parse':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:470:13: note: in expansion of macro 'acl_grammar_error'
  470 | yyerror
  | ^~~
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1720:7: note: in expansion of macro 'acl_grammar_error'
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1831:3: note: in expansion of macro 'acl_grammar_error'
At top level:
libexplain/acl_grammar.y:105:1: warning: 'result_append' defined but
not used [-Wunused-function]
  105 | result_append(const char *text)
  | ^

This does not look like it is an error in libexplain.
Mon May 11 13:28:49 UTC 2020  I: starting to build libexplain/unstable/amd64 on 
jenkins on '2020-05-11 13:28'
Mon May 11 13:28:49 UTC 2020  I: The jenkins build log is/was available at 
https://jenkins.debian.net/userContent/reproducible/debian/build_service/amd64_14/12752/console.log
Mon May 11 13:28:49 UTC 2020  I: Downloading source for 
unstable/libexplain=1.4.D001-9
--2020-05-11 13:28:50--  
http://deb.debian.org/debian/pool/main/libe/libexplain/libexplain_1.4.D001-9.dsc
Connecting to 78.137.99.97:3128... connected.
Proxy request sent, awaiting response... 200 OK
Length: 2184 (2.1K)
Saving to: ‘libexplain_1.4.D001-9.dsc’

 0K ..100%  190M=0s

2020-05-11 13:28:50 (190 MB/s) - ‘libexplain_1.4.D001-9.dsc’ saved [2184/2184]

Mon May 11 13:28:50 UTC 2020  I: libexplain_1.4.D001-9.dsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 3.0 (quilt)
Source: libexplain
Binary: explain, libexplain-doc, libexplain51, libexplain-dev
Architecture: any all
Version: 1.4.D001-9
Maintainer: Debian QA Group 
Homepage: http://libexplain.sourceforge.net/
Standards-Version: 4.4.0
Vcs-Browser: https://salsa.debian.org/debian/libexplain
Vcs-Git: https://salsa.debian.org/debian/libexplain.git
Build-Depends: bison, debhelper-compat (= 12), ghostscript, groff, libacl1-dev, 
libcap-dev [linux-any], libtool-bin, linux-libc-dev [linux-any], lsof 
[linux-any], netbase
Package-List:
 explain deb devel optional arch=any
 libexplain-dev deb libdevel optional arch=any
 libexplain-doc deb doc optional arch=all
 libexplain51 deb libs optional arch=any
Checksums-Sha1:
 e191e1e7f066f8cefca8d05c846c3a38931d8410 4770006 
libexplain_1.4.D001.orig.tar.gz
 051e4be36c618b454657d

Bug#960614: normaliz: version `LIBEANTIC_0_1_2' not found

[Doug Torrance]

Package: normaliz
Version: 3.8.3+ds-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I am getting the following error message when running normaliz:

$ normaliz
normaliz: /usr/lib/x86_64-linux-gnu/libeanticxx.so.0: version 
`LIBEANTICXX_0_1_2' not found (required by normaliz)
normaliz: /usr/lib/x86_64-linux-gnu/libeantic.so.0: version `LIBEANTIC_0_1_2' 
not found (required by normaliz)
normaliz: /usr/lib/x86_64-linux-gnu/libeantic.so.0: version `LIBEANTIC_0_1_2' 
not found (required by /usr/lib/x86_64-linux-gnu/libnormaliz.so.3)
normaliz: /usr/lib/x86_64-linux-gnu/libeanticxx.so.0: version 
`LIBEANTICXX_0_1_2' not found (required by 
/usr/lib/x86_64-linux-gnu/libnormaliz.so.3)

This is also being reported by Debian Continuous Integration, e.g.:
https://ci.debian.net/data/autopkgtest/testing/amd64/n/normaliz/5446108/log.gz

This appears to be due to the recent upload of e-antic 0.1.5 to sid.

Bug#956510: spirv-tools: change to shared libraries breaks dpkg-shlibdeps during the build of reverse dependencies

[Simon McVittie]

On Sun, 12 Apr 2020 at 11:04:38 +0200, Sebastian Ramacher wrote:
> libplacebo now manually links the libraries from spirv-tools
> (libSPIRV-Tools and libSPIRV-Tools-opt) to work-around #951988 and
> #955431. Since the switch to shared libraries, however, dpkg-shlibdeps
> is unable to produce the correct dependencies when linking those
> libraries.

Are these libraries intended to be a public API, or are they intended to be
a private implementation detail of the CLI tools?

If they're a private implementation detail, then libplacebo shouldn't be
linked to them, and they should either be statically linked into the
various CLI tools, or installed to a private directory with a RUNPATH
so that the CLI tools will find them (like the way /usr/bin/sudo links
to the private library libsudo_util.so.0).

If they're considered to be public libraries, then there are two options,
depending how stable they are:

If their API/ABI are totally unmanaged, then they should probably be
provided as static-only, with libplacebo binNMU'd to pick up new versions.

Or, if their API/ABI are managed, then they should have proper SONAMEs
(see upstream issues, as previously mentioned), and they should be
packaged like shared libraries, with a runtime library package per shared
library (or a single runtime library package if the upstream developer
guarantees that their SONAMEs all change in lockstep, like libglib2.0-0),
and one or more -dev packages. (See Policy §8 for details.)

smcv

Processed: reassign 959798 to src:libjs-webrtc-adapter, forcibly merging 959798 960264

[Debian Bug Tracking System]

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

> reassign 959798 src:libjs-webrtc-adapter
Bug #959798 [libjs-webrtc-adapter] libjs-webrtc-adapter: Build with babel 
version 7
Bug reassigned from package 'libjs-webrtc-adapter' to 
'src:libjs-webrtc-adapter'.
No longer marked as found in versions libjs-webrtc-adapter/7.5.1~ds-1.
Ignoring request to alter fixed versions of bug #959798 to the same values 
previously set
> forcemerge 959798 960264
Bug #959798 [src:libjs-webrtc-adapter] libjs-webrtc-adapter: Build with babel 
version 7
Bug #960264 [src:libjs-webrtc-adapter] libjs-webrtc-adapter: Please remove 
dependency to node-babel-preset-env
Severity set to 'serious' from 'important'
Added tag(s) help.
Merged 959798 960264
> thanks
Stopping processing here.

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

Processed: retitle 959798 to libjs-webrtc-adapter: Build with babel version 7, tagging 959798

[Debian Bug Tracking System]

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

> retitle 959798 libjs-webrtc-adapter: Build with babel version 7
Bug #959798 [libjs-webrtc-adapter] libjs-webrtc-adapter: ftbfs with 
node-grunt-babel 8.1
Changed Bug title to 'libjs-webrtc-adapter: Build with babel version 7' from 
'libjs-webrtc-adapter: ftbfs with node-grunt-babel 8.1'.
> tags 959798 + help
Bug #959798 [libjs-webrtc-adapter] libjs-webrtc-adapter: Build with babel 
version 7
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 959798 960264

[Debian Bug Tracking System]

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

> forcemerge 959798 960264
Bug #959798 [libjs-webrtc-adapter] libjs-webrtc-adapter: ftbfs with 
node-grunt-babel 8.1
Unable to merge bugs because:
package of #960264 is 'src:libjs-webrtc-adapter' not 'libjs-webrtc-adapter'
Failed to forcibly merge 959798: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#960603: marked as done (google-android-installers binaries rejected)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 15:33:38 +
with message-id 
and subject line Bug#960603: fixed in google-android-installers 1472023576+nmu5
has caused the Debian Bug report #960603,
regarding google-android-installers binaries rejected
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.)


-- 
960603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-android-installers
Version: 1472023576+nmu4
Severity: grave
Tags: ftbfs

bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/google-android-installers_1472023576+nmu4_all.changes.reason

Version check failed:
Your upload included the binary package google-android-platform-21-installer, 
version 21+r02+nmu3, for all,
however testing already has version 21+r02+nmu3.
Uploads to unstable must have a higher version than present in testing.
bunk@coccia:~$


See debian/rules and #915657.
--- End Message ---
--- Begin Message ---
Source: google-android-installers
Source-Version: 1472023576+nmu5
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated google-android-installers 
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, 15 May 2020 00:00:31 +0900
Source: google-android-installers
Architecture: source
Version: 1472023576+nmu5
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Roger Shimizu 
Closes: 960603
Changes:
 google-android-installers (1472023576+nmu5) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/rules: Bump up binary package version (Closes: #960603).
Checksums-Sha1:
 5d7b85cce801475e06a70c230dbc50c87fb09724 5356 
google-android-installers_1472023576+nmu5.dsc
 1baf597886d68bc0bc703f52f0087a8730cfaba3 17276 
google-android-installers_1472023576+nmu5.tar.xz
 2d6151fc738f7f546b170d2b2c43ad0edb763f1a 6495 
google-android-installers_1472023576+nmu5_source.buildinfo
Checksums-Sha256:
 003fdf0ceceb280344fdbe48d52087aab5a7b48a0b55d251741cc1bdf38c6ab7 5356 
google-android-installers_1472023576+nmu5.dsc
 56152a96e94434157715c47af47b14176fd18eb73beacf130818f86d943916ec 17276 
google-android-installers_1472023576+nmu5.tar.xz
 85aa18121c62f9d2c9b69e1373ab2e445abbffa818e4589e3039580c411ea741 6495 
google-android-installers_1472023576+nmu5_source.buildinfo
Files:
 911fa2ca3fbd90fb410f1b2102d3d4eb 5356 contrib/devel optional 
google-android-installers_1472023576+nmu5.dsc
 a8516541abd4e96c3c7b38108dc4e491 17276 contrib/devel optional 
google-android-installers_1472023576+nmu5.tar.xz
 2faa8a3165f7dbe6aa90ac9507332e12 6495 contrib/devel optional 
google-android-installers_1472023576+nmu5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl69Y0IQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qBzvD/9T8f5doFGaKPX8C57mrMWahY4siixk6jZ3
6vap56+9XUAWhNXDWfOW0ZI1zlZl7N4dIkd8jzjrAR1Ro57dF8r1POJlDzdTyNpV
BDaxY/4b/QmRUlv+D0sSoU4U/Q7CG0JT//lOYRDzGciX0/V/mv5p9aQW/Pn8vmlj
QzPX2xbnKrsT15T2b25xvpPcB9O4AaviviyWf3caJcOip4gAAMr+r+WCiYWNI1Hq
05ZeO60aTgm+fYhVuums9WrVK9YP6ULACNoIEflE5XM8jvovhmSNFyDwqH6dFvjf
zt5naF+HE+sPkZ8F5jJJ9JOdyzhfpAIQBY9AUc5Y5TxXEh2KffxZYpuAQAh2uJV5
QrWK9rx8AFUk7+bSNTOYXnnbRnsluM8mholzUAfl3zm6yKuHN+W2h9oSWGp6ILE4
orGgTLU9kxvHAD6y1Oyn5eRzSinT37zaQMGQKnbf6T4de5x3DJsvG66uy+C+eADA
mIZAerhyG5FY5vTBPTtHzBaaeI8b30ntAIZ70flJdsGg7Q1K5WS6Y/iMFKQSg3s+
hSOnq46sEwKbAAsfd7pBiiKenEEglgc605y5kSI6M0wG3YtGfyr1DpsNrtnnbwB4
yCdejjarj9/0gyZR39dm3wScLBQZl6P3ERQzVrVCamdvf8ajtkAIvrTCCPEoUfWk
HaIiXV76ww==
=Xd+u
-END PGP SIGNATURE End Message ---

Processed: tagging 959798

[Debian Bug Tracking System]

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

> tags 959798 - patch
Bug #959798 [libjs-webrtc-adapter] libjs-webrtc-adapter: ftbfs with 
node-grunt-babel 8.1
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#959798: [Pkg-javascript-devel] Bug#959798: libjs-webrtc-adapter ftbfs with node-grunt-babel 8.0 (using babel 7.4) in experimental

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2020-05-14 17:03:31)
> Quoting Jonas Smedegaard (2020-05-14 16:48:37)
> > Quoting Pirate Praveen (2020-05-14 14:18:20)
> > > On Thu, May 14, 2020 at 1:12 pm, Jonas Smedegaard  
> > > wrote:
> > > > Quoting Pirate Praveen (2020-05-05 15:11:31)
> > > >>  I'm planning to upload node-grunt-babel 8.0 in unstable (it is in 
> > > >>  experimental currently). I have fixed all the reverse build 
> > > >>  dependencies and this is the only remaining blocker. I have fixed 
> > > >>  this package in babel7 branch of salsa.
> > > > 
> > > > I doubt the patch was actually tested - I was unable to reproduce a 
> > > > succesful build.
> > > > 
> > > 
> > > It built fine for me, attaching sbuild log.
> > 
> > Thanks, that was (not enough, but) very helpful: autopkgtest still fails 
> > for me, and I would appreciate if you could test if you agree that it 
> > fails for you as well.
> > 
> > Turns out there are two issues here:
> > 
> > With Babel 6, "babeljs --out-dir dist src/foo.js src/deeper/bar.js" 
> > creates dist/deeper/bar.js, where with Babel 7 that command instead 
> > creates dist/bar.js - your latest patch changes to an alternative form 
> > "babeljs --out-dir dist src" which works. Thanks for that!
> > 
> > Another issue (also experienced with your earlier gulp patch) is that 
> > the _content_ produced by Babel 6 works with the (arguably crude and 
> > unsupported) autopkgtest, but with Babel 7 it fails like this:
> > 
> > Error: Cannot find module ./utils
> > at modRequire (/usr/share/javascript/webrtc-adapter/adapter.js:10:22)
> > at Object.1 (/usr/share/javascript/webrtc-adapter/adapter.js:40:37)
> > at req (/usr/share/javascript/webrtc-adapter/adapter.js:6:22)
> > at modRequire (/usr/share/javascript/webrtc-adapter/adapter.js:11:14)
> > at Object.0../adapter_factory.js 
> > (/usr/share/javascript/webrtc-adapter/adapter.js:26:24)
> > at req (/usr/share/javascript/webrtc-adapter/adapter.js:6:22)
> > at 0../adapter_factory.js 
> > (/usr/share/javascript/webrtc-adapter/adapter.js:2:20)
> > at Object. 
> > (/usr/share/javascript/webrtc-adapter/adapter.js:14:3)
> > at Module._compile (internal/modules/cjs/loader.js:778:30)
> > at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> > 
> > 
> > The generated code is also suspicously much much smaller.
> > 
> > This pattern works with Babel 6:
> > 
> >   babeljs --cwd src/deeper --out-dir dist src/foo.js src/deeper/bar.js
> > 
> > ...but there is no "cwd" command-line option with Babel 7, it seems.
> 
> Weird: --cwd doesn't work with Babel 6 either, not sure what worked 
> before.
> 
> Seems "--source-root src/js/index.js" is the equivalent of gulp "cwd" 
> option.  Works with Babel 6 - trying now with Babel 7...

No, fails.

The package now checks unit tests during build, and switching to Babel 7 
causes one of those to fail:

not ok 69 Log suppression "before each" hook for "does not call console.log by 
default"
  Cannot find module ./utils
  Error: Cannot find module ./utils
  at modRequire (out/adapter.js:10:22)
  at Object.1 (out/adapter.js:40:37)
  at req (out/adapter.js:6:22)
  at modRequire (out/adapter.js:11:14)
  at Object.0../adapter_factory.js (out/adapter.js:26:24)
  at req (out/adapter.js:6:22)
  at 0../adapter_factory.js (out/adapter.js:2:20)
  at Object. (out/adapter.js:14:3)
  at Module._compile (internal/modules/cjs/loader.js:778:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
  at Module.load (internal/modules/cjs/loader.js:653:32)
  at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
  at Function.Module._load (internal/modules/cjs/loader.js:585:3)
  at Module.require (internal/modules/cjs/loader.js:692:17)
  at require (internal/modules/cjs/helpers.js:25:18)
  at Context.beforeEach (test/unit/logSuppression.js:27:5)
  at callFn (/usr/share/nodejs/mocha/lib/runnable.js:395:21)
  at Hook.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:382:7)
  at next (/usr/share/nodejs/mocha/lib/runner.js:384:10)
  at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:428:5)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: found 959223 in 1.5.3+dfsg1-4, tagging 960131, found 959180 in 4.0.4-6.1

[Debian Bug Tracking System]

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

> found 959223 1.5.3+dfsg1-4
Bug #959223 {Done: Boyuan Yang } [src:librime] fcitx won't 
start anymore
Marked as found in versions librime/1.5.3+dfsg1-4.
> tags 960131 + experimental
Bug #960131 [src:swi-prolog] swi-prolog: flaky autopkgtest: test set "file" ... 
aborted
Added tag(s) experimental.
> found 959180 4.0.4-6.1
Bug #959180 [mitmproxy] mitmproxy: Support for tornado 6
Marked as found in versions mitmproxy/4.0.4-6.1.
> thanks
Stopping processing here.

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

Bug#960603: google-android-installers binaries rejected

[Roger Shimizu]

Dear Adrian,

Thanks for your hint!

On Thu, May 14, 2020 at 11:50 PM Adrian Bunk  wrote:
>
> On Thu, May 14, 2020 at 11:16:47PM +0900, Roger Shimizu wrote:
> > On Thu, May 14, 2020 at 10:27 PM Adrian Bunk  wrote:
> > >
> > > Source: google-android-installers
> > > Version: 1472023576+nmu4
> > > Severity: grave
> > > Tags: ftbfs
> > >
> > > bunk@coccia:~$ cat 
> > > /srv/ftp-master.debian.org/queue/reject/google-android-installers_1472023576+nmu4_all.changes.reason
> > >
> > > Version check failed:
> > > Your upload included the binary package 
> > > google-android-platform-21-installer, version 21+r02+nmu3, for all,
> > > however testing already has version 21+r02+nmu3.
> >
> > It's weird since I cannot find 21+r02+nmu3 in tracker:
> > * https://tracker.debian.org/pkg/google-android-installers
>
> Tracker lists source package versions, not binary package versions.
>
> Source packages and binary packages can have different versions.
> The most common example are binNMUs.
>
> > maybe other src package also produce this binary pkg?
>
> No, the versions for the binary packages are defined in
> debian/rules.
>
> "apt-cache show" says:
>
> Package: google-android-platform-23-installer
> Source: google-android-installers (1472023576+nmu3)
> Version: 23+r03+nmu3
>
> Package: google-android-platform-24-installer
> Source: google-android-installers (1472023576+nmu3)
> Version: 24+r02+nmu3

Now I understood it.
And it actually the same as #915657, previous NMU.

Sorry for not checking it for the first place.
Bow!
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#942876: openjdk-11-jre-dcevm: Doesn't start up anymore after updating openjdk-11-jre

[Ruedi Steinmann]

> The issue has been forwarded upstream:
>
> https://github.com/HotswapProjects/openjdk-jdk11u-dcevm/issues/6

According to upstream the issue is fixed now.

Bug#960609: marked as done (Cannot install python3-all from Sid)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 17:14:11 +0200
with message-id 
and subject line Re: Bug#960609: Cannot install dh-python from Sid
has caused the Debian Bug report #960609,
regarding Cannot install python3-all from 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.)


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

When attempting to install python3-all:

$ apt-get update
$ apt-get install dh-python

I get the following error:

The following packages have unmet dependencies:
 python3-all : Depends: python3-distutils (>= 3.8.2-1~) but it is not
installable
E: Unable to correct problems, you have held broken packages.
--- End Message ---
--- Begin Message ---
On 5/14/20 4:47 PM, Kyle Edwards wrote:
> Package: python3-all
> Severity: serious
> 
> When attempting to install python3-all:
> 
> $ apt-get update
> $ apt-get install dh-python
> 
> I get the following error:
> 
> The following packages have unmet dependencies:
>  python3-all : Depends: python3-distutils (>= 3.8.2-1~) but it is not
> installable
> E: Unable to correct problems, you have held broken packages.
> 

Package: python3-distutils
Source: python3-stdlib-extensions
Version: 3.8.2-2

most likely a broken mirror.--- End Message ---

Bug#959798: [Pkg-javascript-devel] Bug#959798: libjs-webrtc-adapter ftbfs with node-grunt-babel 8.0 (using babel 7.4) in experimental

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2020-05-14 16:48:37)
> Quoting Pirate Praveen (2020-05-14 14:18:20)
> > On Thu, May 14, 2020 at 1:12 pm, Jonas Smedegaard  
> > wrote:
> > > Quoting Pirate Praveen (2020-05-05 15:11:31)
> > >>  I'm planning to upload node-grunt-babel 8.0 in unstable (it is in 
> > >>  experimental currently). I have fixed all the reverse build 
> > >>  dependencies and this is the only remaining blocker. I have fixed 
> > >>  this package in babel7 branch of salsa.
> > > 
> > > I doubt the patch was actually tested - I was unable to reproduce a 
> > > succesful build.
> > > 
> > 
> > It built fine for me, attaching sbuild log.
> 
> Thanks, that was (not enough, but) very helpful: autopkgtest still fails 
> for me, and I would appreciate if you could test if you agree that it 
> fails for you as well.
> 
> Turns out there are two issues here:
> 
> With Babel 6, "babeljs --out-dir dist src/foo.js src/deeper/bar.js" 
> creates dist/deeper/bar.js, where with Babel 7 that command instead 
> creates dist/bar.js - your latest patch changes to an alternative form 
> "babeljs --out-dir dist src" which works. Thanks for that!
> 
> Another issue (also experienced with your earlier gulp patch) is that 
> the _content_ produced by Babel 6 works with the (arguably crude and 
> unsupported) autopkgtest, but with Babel 7 it fails like this:
> 
> Error: Cannot find module ./utils
> at modRequire (/usr/share/javascript/webrtc-adapter/adapter.js:10:22)
> at Object.1 (/usr/share/javascript/webrtc-adapter/adapter.js:40:37)
> at req (/usr/share/javascript/webrtc-adapter/adapter.js:6:22)
> at modRequire (/usr/share/javascript/webrtc-adapter/adapter.js:11:14)
> at Object.0../adapter_factory.js 
> (/usr/share/javascript/webrtc-adapter/adapter.js:26:24)
> at req (/usr/share/javascript/webrtc-adapter/adapter.js:6:22)
> at 0../adapter_factory.js 
> (/usr/share/javascript/webrtc-adapter/adapter.js:2:20)
> at Object. 
> (/usr/share/javascript/webrtc-adapter/adapter.js:14:3)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> 
> 
> The generated code is also suspicously much much smaller.
> 
> This pattern works with Babel 6:
> 
>   babeljs --cwd src/deeper --out-dir dist src/foo.js src/deeper/bar.js
> 
> ...but there is no "cwd" command-line option with Babel 7, it seems.

Weird: --cwd doesn't work with Babel 6 either, not sure what worked 
before.

Seems "--source-root src/js/index.js" is the equivalent of gulp "cwd" 
option.  Works with Babel 6 - trying now with Babel 7...


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: your mail

[Debian Bug Tracking System]

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

> severity 960609 critical
Bug #960609 [python3-all] Cannot install python3-all from Sid
Severity set to 'critical' from 'serious'
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 960609 Cannot install python3-all from Sid
Bug #960609 [python3-all] Cannot install dh-python from Sid
Changed Bug title to 'Cannot install python3-all from Sid' from 'Cannot install 
dh-python from Sid'.
>
End of message, stopping processing here.

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

Bug#960604: marked as done (google-android-build-tools-installer i386 binary rejected)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 14:49:22 +
with message-id 
and subject line Bug#960604: fixed in google-android-build-tools-installer 
23.0.3+r1
has caused the Debian Bug report #960604,
regarding google-android-build-tools-installer i386 binary rejected
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.)


-- 
960604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-android-build-tools-installer
Version: 23.0.3+1
Severity: grave
Tags: ftbfs

bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/google-android-build-tools-installer_23.0.3+1_i386.changes.reason

Version check failed:
Your upload included the binary package google-android-build-tools-installer, 
version 23.0.3+1, for i386,
however testing already has version 23.0.3+b1.
Uploads to unstable must have a higher version than present in testing.
bunk@coccia:~$
--- End Message ---
--- Begin Message ---
Source: google-android-build-tools-installer
Source-Version: 23.0.3+r1
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated 
google-android-build-tools-installer 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: Thu, 14 May 2020 23:20:00 +0900
Source: google-android-build-tools-installer
Architecture: source
Version: 23.0.3+r1
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Roger Shimizu 
Closes: 960604
Changes:
 google-android-build-tools-installer (23.0.3+r1) unstable; urgency=medium
 .
   * Team upload.
   * Bump up verion by using +r1 as suffix, since there's already +b1
 in archive (Closes: #960604).
   * Add debian/.gitlab-ci.yml
Checksums-Sha1:
 037a0e863c99ee82d5e9517b10fb062967285ffd 1985 
google-android-build-tools-installer_23.0.3+r1.dsc
 ea35eca397a71ff9b7b2ae0829be24b117d43f26 6612 
google-android-build-tools-installer_23.0.3+r1.tar.xz
 25f74fff873491e466fda1e16a27e66b938180dd 5387 
google-android-build-tools-installer_23.0.3+r1_source.buildinfo
Checksums-Sha256:
 95bd174a5c38d2e16dafa38ba2c2cc123207a7d21b00c12edc7aeccd21fc1ae8 1985 
google-android-build-tools-installer_23.0.3+r1.dsc
 a61c18b31a93556742e1c969b1b4069b6d54cc75afe344f319b183381dcc8ee6 6612 
google-android-build-tools-installer_23.0.3+r1.tar.xz
 89d182bae0c41954698b487725e0991a945dbaa55575cd7525358aa76eeb78f1 5387 
google-android-build-tools-installer_23.0.3+r1_source.buildinfo
Files:
 bd292a57d05a5b48bbff332a89f2e865 1985 contrib/devel optional 
google-android-build-tools-installer_23.0.3+r1.dsc
 e40b781d8ed11f802a08a560a7048822 6612 contrib/devel optional 
google-android-build-tools-installer_23.0.3+r1.tar.xz
 abcbc28dae040cb09a4431f4ee4e83e4 5387 contrib/devel optional 
google-android-build-tools-installer_23.0.3+r1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl69WFoQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qG0bEACi4ZpGOBlnXDtENiBd7/GdzsnxuFZAZ1XM
ujhrYy17Iu8UYRMPT4c4Qz3jRWFsbQtIWgdOxPO2jY89j++xmFuzuwouJ8w9v6r+
5KIXRXZ0YVYkF5VuvXYNYqNmi6OvN/M+6aTYZ+7+BPqLgF4Ct6lLQ39Xs+9qKmqa
HzheqhT4YHVtjSBxYuLnupcSiJMfMi2j+Y5ITdfQeKfu7Fk0PSL8J+7f79RhSSxH
3h1u1UNn7ouv09t1nGupPHGBfbzqAFGo5dB6RiRd4gUA7zb6xIEx7kBUyR+Ga5BO
evUzDEFhCLmd90gUIkNMvGZiSu6TlDX//RfdoVW0oPA0vNskjL2z10luqQfWapt7
k++6pYQGOWvykk9X6gW/8wzCFSlzUWQsmlKxY2mWPss8j2g3FD98EWMkRx/CWbHd
Lk3jstq0FAgI7d0UrL9QBaNyVxJiFxNUEh1jlU/MM/keY8uzakR0NEet4VvcboYK
5w27w3fdzhuZceYJTAYJe42oAuOtCCj73wtMUo1J/6gEYO4t9AhI6FzAEY5HOf6D
wQm24VwsjKVQJI+gvGE9VNmAVF9A5BvH4v+6Cl3vKfLUIRlThvirvVynJ36o23v3
YE6oHjpWaeuJhuOL1TNNnykOIFlCGmRauhUaVsmk/qLTx2Pavy6GlsyxLKF7PSmM
2kmAqipyLQ==
=b5S5
-END PGP SIGNATURE End Message ---

Bug#960603: google-android-installers binaries rejected

[Adrian Bunk]

On Thu, May 14, 2020 at 11:16:47PM +0900, Roger Shimizu wrote:
> On Thu, May 14, 2020 at 10:27 PM Adrian Bunk  wrote:
> >
> > Source: google-android-installers
> > Version: 1472023576+nmu4
> > Severity: grave
> > Tags: ftbfs
> >
> > bunk@coccia:~$ cat 
> > /srv/ftp-master.debian.org/queue/reject/google-android-installers_1472023576+nmu4_all.changes.reason
> >
> > Version check failed:
> > Your upload included the binary package 
> > google-android-platform-21-installer, version 21+r02+nmu3, for all,
> > however testing already has version 21+r02+nmu3.
> 
> It's weird since I cannot find 21+r02+nmu3 in tracker:
> * https://tracker.debian.org/pkg/google-android-installers

Tracker lists source package versions, not binary package versions.

Source packages and binary packages can have different versions.
The most common example are binNMUs.

> maybe other src package also produce this binary pkg?

No, the versions for the binary packages are defined in
debian/rules.

"apt-cache show" says:

Package: google-android-platform-23-installer
Source: google-android-installers (1472023576+nmu3)
Version: 23+r03+nmu3

Package: google-android-platform-24-installer
Source: google-android-installers (1472023576+nmu3)
Version: 24+r02+nmu3

cu
Adrian

Bug#959798: [Pkg-javascript-devel] Bug#959798: libjs-webrtc-adapter ftbfs with node-grunt-babel 8.0 (using babel 7.4) in experimental

[Jonas Smedegaard]

Quoting Pirate Praveen (2020-05-14 14:18:20)
> On Thu, May 14, 2020 at 1:12 pm, Jonas Smedegaard  
> wrote:
> > Quoting Pirate Praveen (2020-05-05 15:11:31)
> >>  I'm planning to upload node-grunt-babel 8.0 in unstable (it is in 
> >>  experimental currently). I have fixed all the reverse build 
> >>  dependencies and this is the only remaining blocker. I have fixed 
> >>  this package in babel7 branch of salsa.
> > 
> > I doubt the patch was actually tested - I was unable to reproduce a 
> > succesful build.
> > 
> 
> It built fine for me, attaching sbuild log.

Thanks, that was (not enough, but) very helpful: autopkgtest still fails 
for me, and I would appreciate if you could test if you agree that it 
fails for you as well.

Turns out there are two issues here:

With Babel 6, "babeljs --out-dir dist src/foo.js src/deeper/bar.js" 
creates dist/deeper/bar.js, where with Babel 7 that command instead 
creates dist/bar.js - your latest patch changes to an alternative form 
"babeljs --out-dir dist src" which works. Thanks for that!

Another issue (also experienced with your earlier gulp patch) is that 
the _content_ produced by Babel 6 works with the (arguably crude and 
unsupported) autopkgtest, but with Babel 7 it fails like this:

Error: Cannot find module ./utils
at modRequire (/usr/share/javascript/webrtc-adapter/adapter.js:10:22)
at Object.1 (/usr/share/javascript/webrtc-adapter/adapter.js:40:37)
at req (/usr/share/javascript/webrtc-adapter/adapter.js:6:22)
at modRequire (/usr/share/javascript/webrtc-adapter/adapter.js:11:14)
at Object.0../adapter_factory.js 
(/usr/share/javascript/webrtc-adapter/adapter.js:26:24)
at req (/usr/share/javascript/webrtc-adapter/adapter.js:6:22)
at 0../adapter_factory.js 
(/usr/share/javascript/webrtc-adapter/adapter.js:2:20)
at Object. (/usr/share/javascript/webrtc-adapter/adapter.js:14:3)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)


The generated code is also suspicously much much smaller.

This pattern works with Babel 6:

  babeljs --cwd src/deeper --out-dir dist src/foo.js src/deeper/bar.js

...but there is no "cwd" command-line option with Babel 7, it seems.


-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#960608: bison: generates (internal) tokentype and (yyerror) function with same name: _error

[Andreas Beckmann]

Package: bison
Version: 2:3.6.1+dfsg-2
Severity: serious
Control: block 960410 with -1
Control: block 960371 with -1

At least two packages FTBFS with the latest bison with some yyerror related
error message. I had a short look into the libexplain failure and found the
following:

In libexplain/acl_grammar.yacc.c (generated from libexplain/acl_grammar.y),
these bits are new in 3.6.1 (they were not generated by 3.5.3):

...
  enum acl_grammar_tokentype
  {
acl_grammar_EMPTY = -2,
acl_grammar_EOF = 0, /* "end of file"  */
acl_grammar_error = 256, /* error  */
acl_grammar_UNDEF = 257, /* "invalid token"  */
...
  };
...
#define acl_grammar_EOF 0
#define acl_grammar_error 256
#define acl_grammar_UNDEF 257
...

and acl_grammar_error clashes with the existing (generated by 3.6.1 and
3.5.3, in acl_grammar.y this is yyerror())

...
static void
acl_grammar_error(const char *text)
{
...
}

which causes this error during compilation:

y.tab.c:152:27: error: expected identifier or '(' before numeric constant
libexplain/acl_grammar.y:128:1: note: in expansion of macro 'acl_grammar_error'
  128 | yyerror(const char *text)
  | ^
libexplain/acl_grammar.y: In function 'acl_grammar_errorf':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:155:5: note: in expansion of macro 'acl_grammar_error'
  155 | yyerror(buf);
  | ^
libexplain/acl_grammar.y: In function 'acl_grammar_parse':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:470:13: note: in expansion of macro 'acl_grammar_error'
  470 | yyerror
  | ^~~  
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1720:7: note: in expansion of macro 'acl_grammar_error'
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1831:3: note: in expansion of macro 'acl_grammar_error'
At top level:
libexplain/acl_grammar.y:105:1: warning: 'result_append' defined but not used 
[-Wunused-function]
  105 | result_append(const char *text)
  | ^


This does not look like it is an error in libexplain.


Andreas

Processed: bison: generates (internal) tokentype and (yyerror) function with same name: _error

[Debian Bug Tracking System]

Processing control commands:

> block 960410 with -1
Bug #960410 [src:libexplain] libexplain FTBFS with bison 3.6.1
960410 was not blocked by any bugs.
960410 was not blocking any bugs.
Added blocking bug(s) of 960410: 960608
> block 960371 with -1
Bug #960371 [src:fhist] fhist FTBFS with bison 3.6.1
960371 was not blocked by any bugs.
960371 was not blocking any bugs.
Added blocking bug(s) of 960371: 960608

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

Bug#960603: google-android-installers binaries rejected

[Roger Shimizu]

On Thu, May 14, 2020 at 10:27 PM Adrian Bunk  wrote:
>
> Source: google-android-installers
> Version: 1472023576+nmu4
> Severity: grave
> Tags: ftbfs
>
> bunk@coccia:~$ cat 
> /srv/ftp-master.debian.org/queue/reject/google-android-installers_1472023576+nmu4_all.changes.reason
>
> Version check failed:
> Your upload included the binary package google-android-platform-21-installer, 
> version 21+r02+nmu3, for all,
> however testing already has version 21+r02+nmu3.

It's weird since I cannot find 21+r02+nmu3 in tracker:
* https://tracker.debian.org/pkg/google-android-installers

maybe other src package also produce this binary pkg?
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#934840: marked as done (gcc-defaults: Build takes forever in stretch)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 15:30:05 +0200
with message-id 
and subject line gcj is long gone, closing this issue
has caused the Debian Bug report #934840,
regarding gcc-defaults: Build takes forever in stretch
to be marked as done.

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

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


-- 
934840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-defaults
Version: 1.168
Fixed: 1.181
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch and this is what happened:


[...]
 debian/rules build-indep
dh_testdir
rm -rf build
mkdir -p build
sed 's/@gcc_suffix@//' debian/generate-cacerts.pl.in \
> debian/generate-cacerts.pl
cd build && perl ../debian/generate-cacerts.pl \
/etc/ssl/certs/ca-certificates.crt
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
keytool error: java.security.cert.CertificateException
keytool error: java.security.cert.CertificateException
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "main" java.lang.OutOfMemoryError
   <>
GC Warning: Repeated allocation of very large block (appr. size 671092736):
May lead to memory leak and poor performance.
Exception in thread "m

Bug#960604: google-android-build-tools-installer i386 binary rejected

[Adrian Bunk]

Source: google-android-build-tools-installer
Version: 23.0.3+1
Severity: grave
Tags: ftbfs

bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/google-android-build-tools-installer_23.0.3+1_i386.changes.reason

Version check failed:
Your upload included the binary package google-android-build-tools-installer, 
version 23.0.3+1, for i386,
however testing already has version 23.0.3+b1.
Uploads to unstable must have a higher version than present in testing.
bunk@coccia:~$

Bug#960603: google-android-installers binaries rejected

[Adrian Bunk]

Source: google-android-installers
Version: 1472023576+nmu4
Severity: grave
Tags: ftbfs

bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/google-android-installers_1472023576+nmu4_all.changes.reason

Version check failed:
Your upload included the binary package google-android-platform-21-installer, 
version 21+r02+nmu3, for all,
however testing already has version 21+r02+nmu3.
Uploads to unstable must have a higher version than present in testing.
bunk@coccia:~$


See debian/rules and #915657.

Bug#960598: libfontconfig-doc: missing Breaks: libfontconfig1-dev (<< 2.13.1-3)

[Andreas Beckmann]

Package: libfontconfig-doc
Version: 2.13.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libfontconfig1-dev/stable
  # (1)
  apt-get install libfontconfig-doc
  apt-get remove libfontconfig-doc
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/doc-base/fontconfig-devel
  /usr/share/man/man3/FcAtomicCreate.3.gz
  /usr/share/man/man3/FcAtomicDeleteNew.3.gz
  /usr/share/man/man3/FcAtomicDestroy.3.gz
...
  /usr/share/man/man3/FcWeightFromOpenTypeDouble.3.gz
  /usr/share/man/man3/FcWeightToOpenType.3.gz
  /usr/share/man/man3/FcWeightToOpenTypeDouble.3.gz

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The libfontconfig-doc package has the following relationships with 
libfontconfig1-dev:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libfontconfig1-dev (<< 2.13.1-3)

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

0m16.4s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/libfontconfig1-dev:amd64.list expected(root, root, - 100644, 
25846, None) != found(root, root, - 100644, 16768, None)
0m16.4s ERROR: FAIL: After purging files have disappeared:
  /usr/share/doc-base/fontconfig-devel   owned by: libfontconfig-doc
  /usr/share/man/man3/FcAtomicCreate.3.gzowned by: libfontconfig-doc
  /usr/share/man/man3/FcAtomicDeleteNew.3.gz owned by: libfontconfig-doc
...
  /usr/share/man/man3/FcWeightToOpenType.3.gzowned by: libfontconfig-doc
  /usr/share/man/man3/FcWeightToOpenTypeDouble.3.gz  owned by: 
libfontconfig-doc

0m16.4s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libfontconfig1-dev:amd64.list   not owned


cheers,

Andreas


libfontconfig1-dev=2.13.1-2_libfontconfig-doc=2.13.1-4.log.gz
Description: application/gzip

Bug#959798: [Pkg-javascript-devel] Bug#959798: libjs-webrtc-adapter ftbfs with node-grunt-babel 8.0 (using babel 7.4) in experimental

[Pirate Praveen]

On Thu, May 14, 2020 at 1:12 pm, Jonas Smedegaard  
wrote:

retitle -1 libjs-webrtc-adapter: Build with babel version 7
tags -1 +help -patch

Quoting Pirate Praveen (2020-05-05 15:11:31)

 I'm planning to upload node-grunt-babel 8.0 in unstable (it is in
 experimental currently). I have fixed all the reverse build
 dependencies and this is the only remaining blocker. I have fixed 
this

 package in babel7 branch of salsa.


I doubt the patch was actually tested - I was unable to reproduce a
succesful build.



It built fine for me, attaching sbuild log.


I have now simplified the package to use node-babel-cli directly, so
that the failure can be examined more directly.

It seems the issue is that Babel 6 compiles subdirectories into
subdirectories, whereas Babel 7 compiles everything _flatly_ into
--out-dir.

Help solving this is much appreciated.


This patch fixes the build,

diff --git a/debian/control b/debian/control
index f4bcaae4..27320b90 100644
--- a/debian/control
+++ b/debian/control
@@ -7,8 +7,7 @@ Uploaders:
Build-Depends:
 brotli,
 debhelper-compat (= 12),
- node-babel-cli,
- node-babel-preset-env,
+ node-babel7,
 node-browserify-lite,
 node-rtcpeerconnection-shim,
 node-sdp,
diff --git a/debian/rules b/debian/rules
index 0cb988ba..66b2fad5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,8 +27,7 @@ override_dh_auto_build: $(patsubst 
%,debian/js/%.min.js.gz,$(STEMS))


# build browser libraries
dist/adapter_core5.js: src/js/adapter_core5.js
-   cd src/js && babeljs --no-babelrc --presets=env --out-dir 
../../dist \

-   -- '*.js' '**/*.js'
+   babeljs --no-babelrc --presets=@babel/env src/js -d dist
dist_x/adapter_core5.js: dist/adapter_core5.js
   cp --force --archive dist dist_x
   rm dist_x/edge/edge_shim.js


sbuild (Debian sbuild) 0.79.1 (22 April 2020) on mahishi

+==+
| libjs-webrtc-adapter 7.5.1~ds-1 (amd64)  Thu, 14 May 2020 12:14:42 + |
+==+

Package: libjs-webrtc-adapter
Version: 7.5.1~ds-1
Source Version: 7.5.1~ds-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-c5aca3ee-5e63-44fc-9395-eddd20151cbd'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/libjs-webrtc-adapter-TngbvY/resolver-3D4WmP' with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://deb.debian.org/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/home/pravi/forge/js-team/libjs-webrtc-adapter_7.5.1~ds-1.dsc exists in 
/home/pravi/forge/js-team; copying to chroot
I: NOTICE: Log filtering will replace 
'build/libjs-webrtc-adapter-TngbvY/libjs-webrtc-adapter-7.5.1~ds' with 
'<>'
I: NOTICE: Log filtering will replace 'build/libjs-webrtc-adapter-TngbvY' with 
'<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: brotli, debhelper-compat (= 12), grunt, 
node-browserify-lite, node-grunt-babel (>= 8.0~), node-rtcpeerconnection-shim, 
node-sdp, pigz, uglifyjs (>= 3), build-essential, fakeroot
Filtered Build-Depends: brotli, debhelper-compat (= 12), grunt, 
node-browserify-lite, node-grunt-babel (>= 8.0~), node-rtcpeerconnection-shim, 
node-sdp, pigz, uglifyjs (>= 3), build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [446 B]
Get:5 copy:/<>/apt_archive ./ Packages [527 B]
Fetched 1930 B in 0s (156 kB/s)
Reading package lists...
Reading package lists...

Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:

Bug#960294: Pushing verbose mode

[Andreas Tille]

Hi Étienne,

On Thu, May 14, 2020 at 01:41:42PM +0200, Étienne Mollier wrote:
> Andreas Tille, on 2020-05-14 08:43:08 +0200:
> > I took the freedom to just upload as is since chances are good that
> > Helmut does just to do "simply nothing" which is better than forcing him
> > to test and send a response.  Hope this strategy is successfull.
> 
> My apologies, I was rather unsure if either it was preferable to
> keep trying uploading and closing the bug again and again, or
> make sure that the patch was actually addressing the problem
> first.

There is no need to apologize.  There is no right or wrong between your
careful approach and mine which is a bit more pushing.  I'd love to get
things from my table (and potentially from other peoples table as well).

> So, many thanks for your message, as it helps me seeing
> that the first approach can be a perfectly valid option as well,
> even preferred in many situations actually I guess.

I agree that there are situations where I'd also follow your careful
approach.
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#960294: Pushing verbose mode

[Étienne Mollier]

Hi Andreas,

Andreas Tille, on 2020-05-14 08:43:08 +0200:
> I took the freedom to just upload as is since chances are good that
> Helmut does just to do "simply nothing" which is better than forcing him
> to test and send a response.  Hope this strategy is successfull.

My apologies, I was rather unsure if either it was preferable to
keep trying uploading and closing the bug again and again, or
make sure that the patch was actually addressing the problem
first.  So, many thanks for your message, as it helps me seeing
that the first approach can be a perfectly valid option as well,
even preferred in many situations actually I guess.

> Étienne, thanks a lot for your work

You're welcome, thank you for the upload,
Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
Help find cures against the Covid-19 !  Give CPU cycles:
  * Rosetta@home: https://boinc.bakerlab.org/rosetta/
  * Folding@home: https://foldingathome.org/


signature.asc
Description: PGP signature

Bug#960391: fixed in experimental

[Hanno Stock]

I have asked debalance to upload 1.7.0 to experimental. autopkgtests in
a VM run fine (module is built).

Bug#959798: [Pkg-javascript-devel] Bug#959798: libjs-webrtc-adapter ftbfs with node-grunt-babel 8.0 (using babel 7.4) in experimental

[Jonas Smedegaard]

retitle -1 libjs-webrtc-adapter: Build with babel version 7
tags -1 +help -patch

Quoting Pirate Praveen (2020-05-05 15:11:31)
> I'm planning to upload node-grunt-babel 8.0 in unstable (it is in 
> experimental currently). I have fixed all the reverse build 
> dependencies and this is the only remaining blocker. I have fixed this 
> package in babel7 branch of salsa.

I doubt the patch was actually tested - I was unable to reproduce a 
succesful build.

I have now simplified the package to use node-babel-cli directly, so 
that the failure can be examined more directly.

It seems the issue is that Babel 6 compiles subdirectories into 
subdirectories, whereas Babel 7 compiles everything _flatly_ into 
--out-dir.

Help solving this is much appreciated.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#959587: Info received (Bug#959587: python-biopython: FTBFS: AssertionError: False is not true)

[Peter Cock]

The small patch on this pull request ought to solve the immediate Debian
testing issue for biopython:

https://github.com/biopython/biopython/pull/2890

Peter


On Wed, May 6, 2020 at 3:06 PM Debian Bug Tracking System <
ow...@bugs.debian.org> 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):
>  Debian Med Packaging Team 
>
> If you wish to submit further information on this problem, please
> send it to 959...@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.
>
> --
> 959587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959587
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Processed: Re: lirc: Fails to install due to missing /etc/lirc/lirc_options.conf

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932779 [lirc] lirc: Fails to install due to missing 
/etc/lirc/lirc_options.conf
Added tag(s) pending.

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

Bug#932779: lirc: Fails to install due to missing /etc/lirc/lirc_options.conf

[Andreas Beckmann]

Control: tag -1 pending

On 10/05/2020 01.02, Andreas Beckmann wrote:
> I'm offering to NMU that.

Just uploaded to DELAYED/10.


Andreas

Processed: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.9.0-1
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing 
for too long: self-build arch/all binaries
Marked as fixed in versions theme-d-gnome/0.9.0-1.
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing 
for too long: self-build arch/all binaries
Marked Bug as done

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

Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries

[Paul Gevers]

Source: theme-d-gnome
Version: 0.8.2-1
Severity: serious
Control: close -1 0.9.0-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:theme-d-gnome
in its current version in unstable has been trying to migrate for 60
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=theme-d-gnome




signature.asc
Description: OpenPGP digital signature

Bug#960577: python-sievelib FTBFS with python3-pip 20.1

[Adrian Bunk]

Source: python-sievelib
Version: 1.1.1-3.1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-sievelib

...
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 40, in 
INSTALL_REQUIRES = get_requirements(path.join(HERE, "requirements.txt"))
  File "setup.py", line 33, in get_requirements
if req.match_markers():
AttributeError: 'ParsedRequirement' object has no attribute 'match_markers'
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
python3.8 setup.py clean 
dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.8 
returned exit code 13
make: *** [debian/rules:15: clean] Error 25

Bug#960576: pyfg FTBFS with python3-pip 20.1

[Adrian Bunk]

Source: pyfg
Version: 0.50-2
Severity: serious
Tags: ftbfs

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

...
   dh_auto_clean -O--buildsystem=pybuild
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
I: pybuild base:217: python3.8 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 16, in 
reqs = [str(ir.req) for ir in install_reqs]
  File "setup.py", line 16, in 
reqs = [str(ir.req) for ir in install_reqs]
AttributeError: 'ParsedRequirement' object has no attribute 'req'
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
python3.8 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.8 returned exit 
code 13
make: *** [debian/rules:5: clean] Error 25

Processed: severity of 960283 is grave, affects 960283

[Debian Bug Tracking System]

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

> severity 960283 grave
Bug #960283 [node-dot-prop] npm says 'pathArray is not defined' when I try to 
use it from buster-backports
Severity set to 'grave' from 'normal'
> affects 960283 npm
Bug #960283 [node-dot-prop] npm says 'pathArray is not defined' when I try to 
use it from buster-backports
Added indication that 960283 affects npm
> thanks
Stopping processing here.

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

Bug#813985: closing 813985

[Jochen Sprickerhof]

close 813985 1.2.1-1
thanks

Processed: severity of 959180 is serious

[Debian Bug Tracking System]

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

> # Tornado 6 is now in unstable
> severity 959180 serious
Bug #959180 [mitmproxy] mitmproxy: Support for tornado 6
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: closing 955644

[Debian Bug Tracking System]

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

> close 955644
Bug #955644 [src:pynwb] pynwb: FTBFS: ERROR: tests.unit.test_retinotopy 
(unittest.loader._FailedTest)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 813985

[Debian Bug Tracking System]

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

> close 813985 1.2.1-1
Bug #813985 [src:python-tasklib] python-tasklib: FTBFS: TypeError: execv() arg 
2 must contain only strings
Marked as fixed in versions python-tasklib/1.2.1-1.
Bug #813985 [src:python-tasklib] python-tasklib: FTBFS: TypeError: execv() arg 
2 must contain only strings
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#960294: marked as done (tigr-glimmer does not trap errors from make)

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 07:05:41 +
with message-id 
and subject line Bug#960294: fixed in tigr-glimmer 3.02b-5
has caused the Debian Bug report #960294,
regarding tigr-glimmer does not trap errors from make
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.)


-- 
960294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tigr-glimmer
Version: 3.02b-3
Tags: upstream
Severity: serious
Justification: policy 4.6

The upstream makefiles of tigr-glimmer do not trap errors from commands
run via make. Doing so is a policy section 4.6 violation and thus
deserves rc severity. Particular occasions:

 * src/c_make.gen macro dosubdirs around line 416: Runs a sub make
   without trapping its error code. Consider adding "set -e" to the
   start.
 * src/c_make.gen %.o:%.c rule around line 315: Runs the C compiler
   without trapping its error code. Consider adding "set -e" to the
   start.

This is not a theoretical issue. In case of a compilation failure (as
happens when attempting to cross build tigr-glimmer), make continues the
dh_auto_build is considered successful despite not having built the
required objects. As such this issue can cause undetectable misbuilds
even when building natively.

Helmut
--- End Message ---
--- Begin Message ---
Source: tigr-glimmer
Source-Version: 3.02b-5
Done: Etienne Mollier 

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

Debian distribution maintenance software
pp.
Etienne Mollier  (supplier of updated tigr-glimmer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 13 May 2020 22:19:56 +0200
Source: tigr-glimmer
Architecture: source
Version: 3.02b-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Etienne Mollier 
Closes: 960294
Changes:
 tigr-glimmer (3.02b-5) unstable; urgency=medium
 .
   * Team upload.
   * Reinforce Makefile error checking and increase verbosity; initial version
 for 3.02b-4 missed at least one point at linking time.  Closes: #960294
Checksums-Sha1:
 57e72f77807c60fca5f94658df31e4a598c0 2060 tigr-glimmer_3.02b-5.dsc
 69ad0825e3f5620d96802e0de1288bea04c3339e 20212 
tigr-glimmer_3.02b-5.debian.tar.xz
 8f81c35ef1043c709c0a39391f23a7f0603cde63 5652 
tigr-glimmer_3.02b-5_amd64.buildinfo
Checksums-Sha256:
 49a1acca5321ca1382d967ba638d36ae8415324134d301e89dc5a6c1e043b1be 2060 
tigr-glimmer_3.02b-5.dsc
 5781e3cfe06ab4fd639813b6de9014b91becdb9dd2ff4a97b0d6bf3c817a83e9 20212 
tigr-glimmer_3.02b-5.debian.tar.xz
 eaa9bf180be1c0acca1c1f9311006d9eb54b702d372f6b8751eb2e295bcde79d 5652 
tigr-glimmer_3.02b-5_amd64.buildinfo
Files:
 ea8384870b571900fd83a3445117f98c 2060 science optional tigr-glimmer_3.02b-5.dsc
 ecacd45fca39436ae36feb90da416c9e 20212 science optional 
tigr-glimmer_3.02b-5.debian.tar.xz
 51c8d6a907f4be0807b27e9e76a5e224 5652 science optional 
tigr-glimmer_3.02b-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl686AERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFDVg//cKeCF+qUvMlngo7pDDcouKCPXbmsctJm
0ihDwpGIgO2LYrkt3K0rgZne6GLebGwtkoFgjjVJcPhTYAX7qQuvjQT6nkFB7341
4gpRXpSOQnI1KxOJFlCGQvs8YI+IfvWoIhpJYedjMGUC6dy+oZF9sJnhdOWYPDv9
J1qZIJ8Q6RBXlIaypSBjUh80O2yyEk8pGSDKeIIeRVkwTFxkrNLnidEAewXNVNDr
VN1OjiSm1ZZkP7iSF45Bd1RLv/OmNNSlVysjTn7XCwaUv3Ax8OgwTk6RTZAD8MCq
58ToG+j8zZJNOPqlGkl868f7zixGd5mRMO3XAl+iI5C4GbgIbpYxAfGP19fUDyUM
woV9ZhGKrg03P7qGQIHjqSIl+q6XLj4/nHQ08vEyqEfSV5RuekhHpXraWZ4Jy+nb
Bj1LigI6hA75U22pf7ktS96NCH6R9oUmigCxnez/K+Zip6+vs2b6Om6CE4fZaOJH
sYwkDyju/nW/ZAiab8wtIs+Lnsqzlh5m/eNpaDRbmVK9WamCgkaN3ESyDP5BnzQr
cR1whsVDQn+WI8ggrV5JFQbRCWCP7BEF/tOUMOQ4Q+MoJuf+5oU78gi6PLTplQ/C
SW1OEOpdDfmb+I+vpdXuWy5gzpzIB5QjhIMXvwRHFty6PlvNyH1xeKt2buu+XbyU
0IlDMr/rSrI=
=VRVl
-END PGP SIGNATURE End Message ---

Bug#951984: marked as done (tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: "MPI_Address was removed in MPI-3.0. Use MPI_Get_address instead.")

[Debian Bug Tracking System]

Your message dated Thu, 14 May 2020 07:05:48 +
with message-id 
and subject line Bug#951984: fixed in tree-puzzle 5.3~rc16+dfsg-1
has caused the Debian Bug report #951984,
regarding tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: 
"MPI_Address was removed in MPI-3.0.  Use MPI_Get_address instead."
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.)


-- 
951984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tree-puzzle
Version: 5.2-11
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now sgamma.o sml1.o 
> sml2.o smlparam.o smodel1.o smodel2.o spuzzle1.o spuzzle2.o spstep.o sutil.o 
> sconsensus.o streesort.o streetest.o  -lsprng -lm  -o puzzle
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./gamma.c && mv 
> gamma.o pgamma.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./ml1.c && mv 
> ml1.o pml1.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./ml2.c && mv 
> ml2.o pml2.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./mlparam.c && 
> mv mlparam.o pmlparam.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./model1.c && 
> mv model1.o pmodel1.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./model2.c && 
> mv model2.o pmodel2.o
> /usr/bin/mpicc -DPARALLEL -DHAVE_CONFIG_H -I. -I.. -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -c ./puzzle1.c && 
> mv puzzle1.o ppuzzle1.o
> ./puzzle1.c: In function ‘readallquarts’:
> ./puzzle1.c:294:3: warning: ignoring return value of ‘fscanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   294 |   fscanf(ifp, "TREE-PUZZLE\n");
>   |   ^~~~
> ./puzzle1.c:295:3: warning: ignoring return value of ‘fscanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   295 |   fscanf(ifp, "%s\n\n", dummyversion);
>   |   ^~~
> ./puzzle1.c:297:3: warning: ignoring return value of ‘fscanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   297 |   fscanf(ifp, "species: %d\n",   &dummynspec);
>   |   ^~~
> ./puzzle1.c:298:3: warning: ignoring return value of ‘fscanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   298 |   fscanf(ifp, "quartets: %lu\n", &dummynquart);
>   |   ^~~~
> ./puzzle1.c:299:3: warning: ignoring return value of ‘fscanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   299 |   fscanf(ifp, "bytes: %lu\n\n",  &dummyblocklen);
>   |   ^~
> ./puzzle1.c:322:6: warning: ignoring return value of ‘fscanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   322 |  fscanf(ifp, "%s\n", dummyname);
>   |  ^~
> ./puzzle1.c:335:3: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   335 |   fread(&(quartetinfo[0]), sizeof(char), blocklen, ifp);
>   |   ^
> ./puzzle1.c: In function ‘setoptions’:
> ./puzzle1.c:718:8: warning: ignoring return value of ‘scanf’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   718 |scanf("%d", &locroot);
>   |^
>