Bug#960701: [Pkg-nagios-devel] Bug#960701: php-icinga: Uncaught ErrorException \Icinga\Web\ViewStream::stream_set_option is not implemented!

[Stephane Bortzmeyer]

On Fri, May 15, 2020 at 06:44:56PM +0200,
 Sebastiaan Couwenberg  wrote 
 a message of 16 lines which said:

> icingaweb2 (2.8.0~rc1-1~exp1) works fine on my unstable test VM.

Tested and it works. So, the sid version is broken but the
experimental one works. Thanks.

> You need icingaweb 2.8.0 from experimental for php7.4 support, and you
> need to upgrade all icingaweb2 packages from experimental, not only
> php-icinga.

Fair enough. But may be php-icinga should depend on icingaweb2 >= 2.8
in that case, no?

Bug#960720: [Pkg-javascript-devel] Bug#960720: node-co: autopkgtest regression: no such file or directory, open 'LICENSE'

[Xavier]

Control: tags -1 + moreinfo

Le 15/05/2020 à 22:10, Paul Gevers a écrit :
> Source: node-co
> Version: 4.6.0-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> With a recent upload of node-co the autopkgtest of node-co fails in
> testing when that autopkgtest is run with the binary packages of node-co
> from unstable. It passes when run with only packages from testing. In
> tabular form:
> 
>passfail
> node-cofrom testing4.6.0-2
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=node-co
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-co/5444788/log.gz
> 
>   39 passing (803ms)
>   4 failing
> 
>   1) co(* -> yield [])
>should aggregate several thunks:
>  Error: ENOENT: no such file or directory, open 'LICENSE'
> 
> 
>   2) co(* -> yield {})
>should aggregate several thunks:
>  Error: ENOENT: no such file or directory, open 'LICENSE'
> 
> 
>   3) co() recursion
>should aggregate arrays within arrays:
>  Error: ENOENT: no such file or directory, open 'LICENSE'
> 
> 
>   4) co() recursion
>should aggregate objects within objects:
>  Error: ENOENT: no such file or directory, open 'LICENSE'

Hi,

I'm unable to reproduce this issue locally using autopkgtest lxc and
schroot. The "LICENSE" file is explicitly set in
debian/tests/pkg-js/test and I did the test with the same pkg-js-tools.

So maybe the problem is in debci machines. Retry launched

Processed: Re: [Pkg-javascript-devel] Bug#960720: node-co: autopkgtest regression: no such file or directory, open 'LICENSE'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #960720 [src:node-co] node-co: autopkgtest regression: no such file or 
directory, open 'LICENSE'
Added tag(s) moreinfo.

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

Bug#960326: json-c: CVE-2020-12762

[Salvatore Bonaccorso]

Hi,

On Fri, May 15, 2020 at 10:19:42PM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Mon, May 11, 2020 at 09:55:12PM +0200, Salvatore Bonaccorso wrote:
> > Source: json-c
> > Version: 0.13.1+dfsg-7
> > Severity: important
> > Tags: security upstream
> > Forwarded: https://github.com/json-c/json-c/pull/592
> > 
> > Hi,
> > 
> > The following vulnerability was published for json-c.
> > 
> > CVE-2020-12762[0]:
> > | json-c through 0.14 has an integer overflow and out-of-bounds write
> > | via a large JSON file, as demonstrated by printbuf_memappend.
> 
> The upstream fix introduces a regression, see in particular
> https://github.com/json-c/json-c/issues/599 .
> 
> FWIW, Ubuntu has as well reverted the fix, pending further
> investigation as per https://usn.ubuntu.com/4360-2/ 

Backports for other branches (as squashed commits for all those
needed):

https://github.com/json-c/json-c/pull/608

Regards,
Salvatore

Bug#958840: kmer: autopkgtest regression: No module named 'localAlignerInterface'

[Andreas Tille]

Hi Antoni,

since you once dived into this which was interrupted when Salsa was
offline:  Would you be able to finish this?

That would be really helpful.

Kind regards

  Andreas.

On Tue, Apr 28, 2020 at 08:43:55PM +0200, Andreas Tille wrote:
> On Tue, Apr 28, 2020 at 04:43:30PM +, Antoni Villalonga wrote:
> > 
> > I think I've faced that problem and fixed.
> > Fix should be included into '2to3.patch'
> > 
> > I think the relevant part is:
> > 
> > --- a/atac-driver/chainer/localalign/localAlignerInterfacemodule.C
> > +++ b/atac-driver/chainer/localalign/localAlignerInterfacemodule.C
> > @@ -227,8 +227,17 @@
> >  };
> >  
> >  
> > +static struct PyModuleDef cModMethods =
> > +{
> > +PyModuleDef_HEAD_INIT,
> > +"localAlignerInterface",  /* name of module */
> > +"",  /* module documentation, may be NULL */
> > +-1,  /* size of per-interpreter state of the module, or -1 if 
> > the module keeps state in global variables. */
> > +registration_table
> > +};
> > +
> >  extern "C"
> > -void initlocalAlignerInterface() {
> > -  Py_InitModule("localAlignerInterface", registration_table);
> > +void PyInit_localAlignerInterface() {
> > +  PyModule_Create(&cModMethods);
> >  }
> 
> Thanks.  Looks promising.
>  
> > Sorry I can't access salsa due to a maintenance, also can't test autopkgtest
> > for testing for the same reason.
> 
> Salsa and other hosts seem to be back now.
>  
> > It worked fine for sid some days ago.
> 
> Kind regards and thanks a lot for your contribution
> 
>   Andreas. 
> 
> -- 
> http://fam-tille.de
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Processed: tagging 960410

[Debian Bug Tracking System]

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

> tags 960410 + pending
Bug #960410 [src:libexplain] libexplain FTBFS with bison 3.6.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Sat, 16 May 2020 02:44:28 +0200
with message-id <5cc01e86-27a4-4928-513d-b8080524c...@debian.org>
and subject line Re: Bison 3.6.1 generates (internal) tokentype and (yyerror) 
function with same name: _error
has caused the Debian Bug report #960608,
regarding bison: generates (internal) tokentype and (yyerror) function with 
same name: _error
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.)


-- 
960608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On 15/05/2020 07.10, Akim Demaille wrote:
> I don't understand why this is done this way.

I don't know how old that code is ... ;-)

> The grammar file should use
> %define api.prefix {acl_grammar_}, or the build system should pass

That works fine.

Thanks, and sorry for the noise.


Andreas--- End Message ---

Bug#960688: fwupd: missing Breaks: fwupdate (<< 12-7)

[Andreas Beckmann]

On 15/05/2020 20.54, mario.limoncie...@dell.com wrote:
> Hopefully that illustrates the timeline.  As fwupdate is a transition package 
> now,
> I don't know that it makes sense to add the Breaks now, please advise.

Nothing forces the transitional fwupdate to be installed, thus the
package relationships allow some kind of partial upgrade: the
combination of fwupdate/buster and fwupd/bullseye to be installed at the
same time, which creates the mess. The Breaks will fix this - either
fwupdate from buster gets removed or upgraded to the transitional
package in bullseye if fwupd from bullseye is being installed.

Andreas

PS: Yes, I am searching for corner cases where things may go wrong.

Bug#960688: fwupd: missing Breaks: fwupdate (<< 12-7)

[Mario.Limonciello]

Let me elaborate the timeline.

* Originally fwupdate contained /usr/bin/fwupdate.
* It was merged into fwupd and fwupdate went into maintenance only mode.
* In Debian we made fwupdate a transition package with nothing in it.
This is when the Replaces got put into place.

* Because it was a transition package, there is a chance that a user already
removed /var/lib/fwupdate and so a request was put in for fwupd to clean that 
up.

* Later, a compatibility binary /usr/bin/fwupdate was added into fwupd.
This performs similar actions as the old fwupdate provided /usr/bin/fwupdate.

Hopefully that illustrates the timeline.  As fwupdate is a transition package 
now,
I don't know that it makes sense to add the Breaks now, please advise.


> -Original Message-
> From: Andreas Beckmann 
> Sent: Friday, May 15, 2020 7:28 AM
> To: Debian Bug Tracking System
> Subject: Bug#960688: fwupd: missing Breaks: fwupdate (<< 12-7)
> 
> 
> [EXTERNAL EMAIL]
> 
> Package: fwupd
> Version: 1.3.9-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 fwupdate/stable
>   # (1)
>   apt-get install fwupd
>   apt-get remove fwupd
>   # (2)
> 
> The list of installed files at points (1) and (2) should be identical,
> but the following files have disappeared:
> 
>   /usr/bin/fwupdate
>   /usr/share/man/man1/fwupdate.1.gz
>   /var/lib/fwupdate/
> 
> 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 fwupd package has the following relationships with fwupdate:
> 
>   Conflicts: n/a
>   Breaks:n/a
>   Replaces:  fwupdate (<< 12-7)
>   Provides:  fwupdate
> 
> >From the attached log (scroll to the bottom...):
> 
> 0m32.0s ERROR: FAIL: After purging files have disappeared:
>   /usr/bin/fwupdate  owned by: fwupd
>   /usr/share/man/man1/fwupdate.1.gz  owned by: fwupd
>   /var/lib/fwupdate/ owned by: fwupdate
> 
> 0m32.0s ERROR: FAIL: After purging files have been modified:
>   /var/lib/dpkg/info/fwupdate.list   not owned
> 
> 
> cheers,
> 
> Andreas

Bug#925754: Fwd: Fixed in newer release of libopenshot / libopenshot-audio

[John Scott]

On Sat, 25 Apr 2020 21:40:14 -0400 FeRD  wrote:
> If Debian maintains JUCE as a distro package, and it would be a compatible
> alternative to our JUCE-based "libopenshot-audio", I don't see any reason we
> can't add an option to libopenshot's CMake configuration that tells it to
> just
> use those libs, completely replacing libopenshot-audio ? which would
> become entirely superfluous in that scenario.
> 
> This is the perfect time to do it, too, as I've been gutting and reworking
> large parts
> of libopenshot's build system recently ? sticking in a "USE_SYSTEM_JUCE"
> option would be no trouble at all.
> 
> Is there an importable CMake configuration for the distro JUCE package, by
> any chance, or should I put together a find module as well?

That would be terrific. The version of JUCE that you updated is almost the same 
version as the Debian package, so I expect that would work well.

There doesn't appear to be a CMake module. If you would create one or add an 
option to specify the path, that'd be the cleanest solution.

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

Bug#936804: knockpy - python3

[Scott Talbert]

Hi,

Looks like someone did a patch to port knockpy to Python 3:
https://github.com/guelfoweb/knock/pull/71

Regards,
Scott

Bug#960726: firefox: connection failure to most https websites

[Vincent Lefevre]

Package: firefox
Version: 76.0.1-1
Severity: grave
Justification: renders package unusable

The connection to many https websites fails, e.g.

https://www.google.com/

  Secure Connection Failed

  An error occurred during a connection to www.google.com. The OCSP
  server experienced an internal error.

  Error code: SEC_ERROR_OCSP_SERVER_ERROR

(no issue with firefox-esr). Ditto for https://www.mpfr.org/ and others.

https://support.mozilla.org/1/firefox/76.0.1/Linux/en-US/connection-not-secure

  Secure Connection Failed

  The page you are trying to view cannot be shown because the
  authenticity of the received data could not be verified.

or the SEC_ERROR_OCSP_SERVER_ERROR error like above.

-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils 4.9.1
ii  fontconfig  2.13.1-4.2
ii  libatk1.0-0 2.36.0-2
ii  libc6   2.30-8
ii  libcairo-gobject2   1.16.0-4
ii  libcairo2   1.16.0-4
ii  libdbus-1-3 1.12.16-2
ii  libdbus-glib-1-20.110-5
ii  libevent-2.1-7  2.1.11-stable-1
ii  libffi7 3.3-4
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.1-2
ii  libgcc-s1   10.1.0-1
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-4
ii  libglib2.0-02.64.2-1
ii  libgtk-3-0  3.24.20-1
ii  libnspr42:4.25-1
ii  libnss3 2:3.52-1
ii  libpango-1.0-0  1.44.7-4
ii  libstdc++6  10.1.0-1
ii  libvpx6 1.8.2-1
ii  libx11-62:1.6.9-2+b1
ii  libx11-xcb1 2:1.6.9-2+b1
ii  libxcb-shm0 1.14-2
ii  libxcb1 1.14-2
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.3-1+b2
ii  libxfixes3  1:5.0.3-2
ii  libxrender1 1:0.9.10-1
ii  libxt6  1:1.1.5-1+b3
ii  procps  2:3.3.16-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.2.2-1+b1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-6
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.17-7
ii  libgtk2.0-02.24.32-4
ii  pulseaudio 13.0-5

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#953205: Possibly fixed in Testing

[Soren Stoutner]

With the updates in Testing as of 5/15/20, this appears to no longer be 
an issue (probably because of some updated dependency). Now it is the 
opposite:  if `require "uri/generic"` is commented out, an error is 
produced.  If it is not commented out, updates to Redmine work correctly.


--
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net

Bug#960405: marked as done (mscgen crashes after libgd3 upload)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 21:03:42 +
with message-id 
and subject line Bug#960405: fixed in mscgen 0.20-14
has caused the Debian Bug report #960405,
regarding mscgen crashes after libgd3 upload
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.)


-- 
960405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mscgen
Version: 0.20-13
Severity: serious
Tags: ftbfs

https://ci.debian.net/packages/m/mscgen/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mscgen.html

...
FAIL: renderercheck.sh
==

testinput0.msc
testinput1.msc
testinput10.msc
testinput11.msc
testinput12.msc
testinput13.msc
testinput14.msc
testinput15.msc
testinput16.msc
testinput17.msc
realloc(): invalid next size
../../test/renderercheck.sh: line 28: 15670 Aborted $VALGRIND 
$top_builddir/src/mscgen -T png -i $srcdir/$F -o $F.png
FAIL renderercheck.sh (exit status: 134)


Testsuite summary for mscgen 0.20

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to michael.mcternan.2...@cs.bris.ac.uk

make[4]: *** [Makefile:495: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: mscgen
Source-Version: 0.20-14
Done: Niels Thykier 

We believe that the bug you reported is fixed in the latest version of
mscgen, 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.
Niels Thykier  (supplier of updated mscgen 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 20:46:30 +
Source: mscgen
Architecture: source
Version: 0.20-14
Distribution: unstable
Urgency: medium
Maintainer: Niels Thykier 
Changed-By: Niels Thykier 
Closes: 960405
Changes:
 mscgen (0.20-14) unstable; urgency=medium
 .
   * Apply patch from Steve Langasek to avoid using negative
 widths for text sizes in PNG files, which lead to crashes.
 (Closes: #960405)
   * Add patch to give more height to PNG text.  The original
 rendering no longer gave adequate space between lines or
 the entity the text was a part of.
   * Remove -Wl,--as-needed as linker flag since it is now the
 default.
Checksums-Sha1:
 4ce633ec604a5785d998132ccd63e92dfbbc3287 1893 mscgen_0.20-14.dsc
 48287680b435663362fe0ac29d393dcd6e9e6a3e 7276 mscgen_0.20-14.debian.tar.xz
 2f65975f1453fbfd373d739bca9f12295eef9ef8 6607 mscgen_0.20-14_source.buildinfo
Checksums-Sha256:
 795f57034f2e221e93877474eec945ea9ccb1bbd378dfa2ea3217764f835f5b1 1893 
mscgen_0.20-14.dsc
 4569d576c6f5fb247964064cc5a633edd09e0d5bbd8a1dcb534876301d79300c 7276 
mscgen_0.20-14.debian.tar.xz
 981fa640ddd9e1b6bac27ef70ef95c489cb2439e761458fd47809b95e9c78e6c 6607 
mscgen_0.20-14_source.buildinfo
Files:
 e4e7089592dd1609102a6a7a4b572573 1893 devel optional mscgen_0.20-14.dsc
 495b758b4042bd177c6f1240761895e2 7276 devel optional 
mscgen_0.20-14.debian.tar.xz
 35bca124d9e2180983879f170440c80c 6607 devel optional 
mscgen_0.20-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAl6+/+QSHG5pZWxzQHRo
eWtpZXIubmV0AAoJEKZbeNvmfHqsDwsP/jbbBd30/z4+LLrRM5Q2B6v7iGZDfvpl
XROACwsInyfGs9Ten1NsskRNOTrbALAmjs/Di5ZO7nF37mb9euSW89pN/iSDihd6
990NKR9XqXEsD/nRf5A9tZ9NRoiWOZaOZoKdEu2Yjt+dqfPnu0jg5HEpqzsV2XWY
YbOQwVvLgqcRwpRKKMfw5snVuKd9y3mFZPT6jkBQJBlGELESU1CqpOfyGWRZFSfv
YmMHRtz5MnjgTct8A9eIutIAlz8v22/Y39Lkwqd43R5QUAwfX1obQakosQt5G3PS
tsFEmRRmfl3ocBHSUg7MkNftxS1yfNCD9LR97NPwLghez0hL2adbc7q6C2WXKCr4
O3byEHUuNsVw0w+yHEyWhATiLut2LVaNNGyTXNfxi5YuGibp8pIJOAU8BrJuyKkQ
qbKKoo9gElfQSzxLoH20eeajPKvV5WulAWmAEWJ9NmvUWPS9Cpjewks/zDdJwqVR
rqRcV58pFdX8O57nN6LxyfnUXIoQT2x4YOBtyLLU+5Sw9e706ncVskU8zYFP7WH/
vC2rHIRDb+Sbpu2QiNqi0RgC/9HdbDnKS4w9H3E

Bug#960105: node-redis: autopkgtest regressions against Redis 6.x

[Chris Lamb]

reassign 960721 node-redis
forcemerge 960105 960721
thanks

Hi,

I already filed this and it was actually fixed in 3.0.2-2:

 node-redis (3.0.2-2) unstable; urgency=medium

   * Disable error tests incompatible with redis ≥ 6 (Closes: #960105)

... hence merging. Thanks for filing these issues.


Best wishes,

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

Processed: Re: node-redis: autopkgtest regressions against Redis 6.x

[Debian Bug Tracking System]

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

> reassign 960721 node-redis
Bug #960721 [src:redis, src:node-redis] redis breaks node-redis autopkgtest: 
6/655
Bug reassigned from package 'src:redis, src:node-redis' to 'node-redis'.
No longer marked as found in versions node-redis/3.0.2-1 and redis/5:6.0.0-2.
Ignoring request to alter fixed versions of bug #960721 to the same values 
previously set
> forcemerge 960105 960721
Bug #960105 {Done: Xavier Guimard } [node-redis] node-redis: 
autopkgtest regressions against Redis 6.x
Bug #960105 {Done: Xavier Guimard } [node-redis] node-redis: 
autopkgtest regressions against Redis 6.x
Added tag(s) sid and bullseye.
Bug #960721 [node-redis] redis breaks node-redis autopkgtest: 6/655
Set Bug forwarded-to-address to 
'https://github.com/NodeRedis/node-redis/issues/1516'.
Marked Bug as done
Added indication that 960721 affects src:redis
Marked as fixed in versions node-redis/3.0.2-2.
Marked as found in versions node-redis/3.0.2-1.
Merged 960105 960721
> thanks
Stopping processing here.

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

Processed: redis breaks node-redis autopkgtest: 6/655

[Debian Bug Tracking System]

Processing control commands:

> found -1 redis/5:6.0.0-2
Bug #960721 [src:redis, src:node-redis] redis breaks node-redis autopkgtest: 
6/655
Marked as found in versions redis/5:6.0.0-2.
> found -1 node-redis/3.0.2-1
Bug #960721 [src:redis, src:node-redis] redis breaks node-redis autopkgtest: 
6/655
Marked as found in versions node-redis/3.0.2-1.

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

Bug#958408: etherape: crashes with "critical: read_all() failed on control socket"

[rghetta]

On 15/05/20 15:22, Patrick Matthäi wrote:

@rghetta:
Do you want to merge it?

Patch merged. Thanks to all for your nice work.
I've cut a new release, 0.9.19

Ciao,
R

Bug#960721: redis breaks node-redis autopkgtest: 6/655

[Paul Gevers]

Source: redis, node-redis
Control: found -1 redis/5:6.0.0-2
Control: found -1 node-redis/3.0.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
redis  from testing5:6.0.0-2
node-redis from testing3.0.2-1
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-redis/5438964/log.gz

  649 passing (19s)
  6 failing

  1) publish/subscribe
   using options: detect_buffers: true;
 using IPv4
   fail for other commands while in pub sub mode
 return error if only pub sub commands are allowed:

  Uncaught AssertionError [ERR_ASSERTION]: The expression evaluated
to a falsy value:

  assert(/^ERR only \(P\)SUBSCRIBE \/ \(P\)UNSUBSCRIBE/.test(err.message))

  + expected - actual

  -false
  +true

  at
/tmp/autopkgtest-lxc.sefvg_kj/downtmp/autopkgtest_tmp/smokepiVdFl/test/pubsub.spec.js:590:25
  at Object.callbackOrEmit [as callback_or_emit]
(/usr/share/nodejs/redis/lib/utils.js:89:9)
  at RedisClient.return_error (/usr/share/nodejs/redis/index.js:641:11)
  at JavascriptRedisParser.returnError
(/usr/share/nodejs/redis/index.js:141:18)
  at JavascriptRedisParser.execute
(/usr/share/nodejs/redis-parser/lib/parser.js:572:12)
  at Socket. (/usr/share/nodejs/redis/index.js:218:27)
  at addChunk (_stream_readable.js:288:12)
  at readableAddChunk (_stream_readable.js:269:11)
  at Socket.Readable.push (_stream_readable.js:224:10)
  at TCP.onStreamRead [as onread]
(internal/stream_base_commons.js:94:17)

  2) publish/subscribe
   using options: detect_buffers: true;
 using IPv4
   fail for other commands while in pub sub mode
 return error if only pub sub commands are allowed:
 Error: done() called multiple times
  at multiple (/usr/share/nodejs/mocha/lib/runnable.js:314:26)
  at done (/usr/share/nodejs/mocha/lib/runnable.js:326:14)
  at /usr/share/nodejs/mocha/lib/runnable.js:443:7
  at Object.callbackOrEmit [as callback_or_emit]
(/usr/share/nodejs/redis/lib/utils.js:89:9)
  at Command.callback
(/usr/share/nodejs/redis/lib/individualCommands.js:93:15)
  at RedisClient.flush_and_error
(/usr/share/nodejs/redis/index.js:309:29)
  at RedisClient.connection_gone
(/usr/share/nodejs/redis/index.js:532:14)
  at Socket. (/usr/share/nodejs/redis/index.js:230:14)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)

  3) publish/subscribe
   using options: detect_buffers: true;
 using IPv4
   fail for other commands while in pub sub mode
 emit error if only pub sub commands are allowed without
callback:

  Uncaught AssertionError [ERR_ASSERTION]: The expression evaluated
to a falsy value:

  assert(/^ERR only \(P\)SUBSCRIBE \/ \(P\)UNSUBSCRIBE/.test(err.message))

  + expected - actual

  -false
  +true

  at RedisClient. (test/pubsub.spec.js:600:25)
  at Object.callbackOrEmit [as callback_or_emit]
(/usr/share/nodejs/redis/lib/utils.js:91:14)
  at RedisClient.return_error (/usr/share/nodejs/redis/index.js:641:11)
  at JavascriptRedisParser.returnError
(/usr/share/nodejs/redis/index.js:141:18)
  at JavascriptRedisParser.execute
(/usr/share/nodejs/redis-parser/lib/parser.js:572:12)
  at Socket. (/usr/share/nodejs/redis/index.js:218:27)
  at addChunk (_stream_readable.js:288:12)
  at readableAddChunk (_stream_readable.js:269:11)
  at Socket.Readable.push (_stream_readable.js:224:10)
  at TCP.onStreamRead [as onread]
(internal/stream_base_commons.js:94:17)

  4) publish/subscribe
   using options: detect_buffers: false;
 using IPv4
   fail for other commands while in pub sub mode
 return error if only pub sub commands are allowed:

  Uncaught AssertionError [ERR_ASSERTION]: The expression evaluated
to a falsy value:

  assert(/^ERR only \(P\)SUBSCRIBE \/ \(P\)UNSUBSCRIBE/.test(err.message))

  + expected - actual

  -fa

Bug#960326: json-c: CVE-2020-12762

[Salvatore Bonaccorso]

Hi,

On Mon, May 11, 2020 at 09:55:12PM +0200, Salvatore Bonaccorso wrote:
> Source: json-c
> Version: 0.13.1+dfsg-7
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/json-c/json-c/pull/592
> 
> Hi,
> 
> The following vulnerability was published for json-c.
> 
> CVE-2020-12762[0]:
> | json-c through 0.14 has an integer overflow and out-of-bounds write
> | via a large JSON file, as demonstrated by printbuf_memappend.

The upstream fix introduces a regression, see in particular
https://github.com/json-c/json-c/issues/599 .

FWIW, Ubuntu has as well reverted the fix, pending further
investigation as per https://usn.ubuntu.com/4360-2/ 

Regards,
Salvatore

Bug#960720: node-co: autopkgtest regression: no such file or directory, open 'LICENSE'

[Paul Gevers]

Source: node-co
Version: 4.6.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
node-cofrom testing4.6.0-2
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-co/5444788/log.gz

  39 passing (803ms)
  4 failing

  1) co(* -> yield [])
   should aggregate several thunks:
 Error: ENOENT: no such file or directory, open 'LICENSE'


  2) co(* -> yield {})
   should aggregate several thunks:
 Error: ENOENT: no such file or directory, open 'LICENSE'


  3) co() recursion
   should aggregate arrays within arrays:
 Error: ENOENT: no such file or directory, open 'LICENSE'


  4) co() recursion
   should aggregate objects within objects:
 Error: ENOENT: no such file or directory, open 'LICENSE'



signature.asc
Description: OpenPGP digital signature

Bug#960719: python-django-netfields: autopkgtest failure: No module named 'django_netfields'

[Paul Gevers]

Source: python-django-netfields
Version: 1.2.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. I copied some
of the output at the bottom of this report. Can you please investigate
the situation and fix it?

You're using autodep8 to trigger the test, but it seems your package
naming and Python module name aren't aligned for autodep8. autodep8
recently acquired a new feature that enables you to tell autode8 what
the real module name is that should be tested [1].

The release team has announced [2] that failing autopkgtest are now
considered RC in testing.

Paul

[1]
https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES
[2] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-netfields/5494902/log.gz

autopkgtest [17:13:47]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -c "import django_netfields; print(django_netfields)" ;
done
autopkgtest [17:13:47]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'django_netfields'
autopkgtest [17:13:47]: test autodep8-python3: ---]



signature.asc
Description: OpenPGP digital signature

Bug#960405: mscgen crashes after libgd3 upload

[Steve Langasek]

Package: mscgen
Version: 0.20-13
Followup-For: Bug #960405
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

Hi Niels,

This autopkgtest regression hit us also in Ubuntu, and I dug into it and
found mscgen was blindly subtracting 1 from the "width" returned by libgd
for the text bounding box; so if gd returned a bounding box of width 0,
mscgen would blithely return -1 instead and things would go sideways.

The attached patch handles this case and avoids returning a width of
(unsigned int)-1, though I have my doubts about the correctness of the
original code trying to fix up the bounding box width as well.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru mscgen-0.20/debian/patches/series mscgen-0.20/debian/patches/series
--- mscgen-0.20/debian/patches/series   2013-12-29 04:43:25.0 -0800
+++ mscgen-0.20/debian/patches/series   2020-05-15 12:28:20.0 -0700
@@ -1 +1,2 @@
 language.y-parse-param.patch
+width-never-less-than-zero.patch
diff -Nru mscgen-0.20/debian/patches/width-never-less-than-zero.patch 
mscgen-0.20/debian/patches/width-never-less-than-zero.patch
--- mscgen-0.20/debian/patches/width-never-less-than-zero.patch 1969-12-31 
16:00:00.0 -0800
+++ mscgen-0.20/debian/patches/width-never-less-than-zero.patch 2020-05-15 
12:31:31.0 -0700
@@ -0,0 +1,23 @@
+Description: don't make width < 0 with an off-by-one fix-up
+ gdoTextWidth() tries to correct an off-by-one error in the calculated width
+ of a text bounding box; but doesn't account for the possibility that the
+ bounding box has a size of zero (which is the case in latest libgd for
+ zero-width text).  Account for this so we aren't accidentally returning
+ -1 where we mean 0.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/960405
+Last-Update: 2020-05-15
+
+Index: mscgen-0.20/src/gd_out.c
+===
+--- mscgen-0.20.orig/src/gd_out.c
 mscgen-0.20/src/gd_out.c
+@@ -212,7 +212,7 @@
+  *  the right of the last character for the fixed width
+  *  font.
+  */
+-return rect[2] - 1;
++return rect[2] ? rect[2] - 1 : 0;
+ #endif
+ }
+ 

Bug#960718: slirp4netns: autopkgtest failure: 5/7 tests

[Paul Gevers]

Source: slirp4netns
Version: 0.4.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. I copied some
of the output at the bottom of this report. Can you please investigate
the situation and fix it?

The release team has announced [1] that failing autopkgtest are now
considered RC in testing.

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/s/slirp4netns/5495522/log.gz

autopkgtest [17:55:40]: test make-check: [---
+ make check
make  check-TESTS
make[1]: Entering directory
'/tmp/autopkgtest-lxc.s0_sz0m_/downtmp/build.yCj/src'
make[2]: Entering directory
'/tmp/autopkgtest-lxc.s0_sz0m_/downtmp/build.yCj/src'
FAIL: tests/test-slirp4netns.sh
FAIL: tests/test-slirp4netns-configure.sh
PASS: tests/test-slirp4netns-exit-fd.sh
PASS: tests/test-slirp4netns-ready-fd.sh
FAIL: tests/test-slirp4netns-api-socket.sh
FAIL: tests/test-slirp4netns-disable-host-loopback.sh
FAIL: tests/test-slirp4netns-cidr.sh

Testsuite summary for slirp4netns 0.4.3

# TOTAL: 7
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  5
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to https://github.com/rootless-containers/slirp4netns/issues

make[2]: *** [Makefile:1605: test-suite.log] Error 1
make[2]: Leaving directory
'/tmp/autopkgtest-lxc.s0_sz0m_/downtmp/build.yCj/src'
make[1]: *** [Makefile:1713: check-TESTS] Error 2
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.s0_sz0m_/downtmp/build.yCj/src'
make: *** [Makefile:1967: check-am] Error 2
autopkgtest [18:00:23]: test make-check: ---]



signature.asc
Description: OpenPGP digital signature

Bug#960294: [Debian-med-packaging] Bug#960294: closed by Debian FTP Masters (reply to Etienne Mollier ) (Bug#960294: fixed in tigr-glimmer

[Étienne Mollier]

Hi Helmut,

Helmut Grohne, on 2020-05-15 08:02:04 +0200:
> Given that the previous fix of the bug was incomplete, I'd like to
> confirm that with this fix, it really fails instantly. Also verbose
> build logs help a lot. Thank you for bearing with me.

You're welcome, glad to read it does the job.  :)
Thank you for the confirmation!

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/

Bug#960126: marked as done (FTBFS: No cached version of :osmosis-core-0.47.2: available for offline mode.)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 19:33:39 +
with message-id 
and subject line Bug#960126: fixed in mapsforge 0.13.0+dfsg.1-3
has caused the Debian Bug report #960126,
regarding FTBFS: No cached version of :osmosis-core-0.47.2: available for 
offline mode.
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.)


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

Source: mapsforge
Version: 0.13.0+dfsg.1-2
Severity: serious
Tags: ftbfs

Dear Maintainer,

mapsforge 0.13.0+dfsg.1-2 currently fails to build:
All input files are considered out-of-date for incremental task 
':mapsforge-map:compileJava'.

Compiling with JDK Java compiler API.
:mapsforge-poi:compileJava (Thread[Task worker for ':' Thread 
10,5,main]) completed. Took 0.717 secs.
:mapsforge-map:compileJava (Thread[Task worker for ':' Thread 3,5,main]) 
completed. Took 2.081 secs.


FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration 
':mapsforge-map-writer:compileClasspath'.

Could not resolve :osmosis-core-0.47.2:.

  Required by:
  project :mapsforge-map-writer
   > No cached version of :osmosis-core-0.47.2: available for offline 
mode.
   > No cached version of :osmosis-core-0.47.2: available for offline 
mode.
   > No cached version of :osmosis-core-0.47.2: available for offline 
mode.


For more details see 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mapsforge.html


I suppose it fails to find the osmosis jars now that it has been
updated to 0.48.0-1.


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

Kernel: Linux 5.6.0-1-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: mapsforge
Source-Version: 0.13.0+dfsg.1-3
Done: Ying-Chun Liu (PaulLiu) 

We believe that the bug you reported is fixed in the latest version of
mapsforge, 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.
Ying-Chun Liu (PaulLiu)  (supplier of updated mapsforge 
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: Sat, 16 May 2020 02:26:11 +0800
Source: mapsforge
Architecture: source
Version: 0.13.0+dfsg.1-3
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 960126
Changes:
 mapsforge (0.13.0+dfsg.1-3) unstable; urgency=low
 .
   * Build against osmosis (>= 0.48.0) (Closes: #960126)
Checksums-Sha1:
 838b9b4261dc70531d1eb62644411d64cb3b8205 2161 mapsforge_0.13.0+dfsg.1-3.dsc
 0e59f531909a2ee7846a3e846db32eb8966cdbc6 5448 
mapsforge_0.13.0+dfsg.1-3.debian.tar.xz
 7ff5045d8c9086a687a1b63cc301ae4c987513c0 18967 
mapsforge_0.13.0+dfsg.1-3_source.buildinfo
Checksums-Sha256:
 d9d24a7fcbf05d1d074bf08e65808658b3c0513f88e5b27076bf53a6a19a89d9 2161 
mapsforge_0.13.0+dfsg.1-3.dsc
 843a1d18b2090faab097fa3fd011ff745ea3670cffc92461a8972a04b524 5448 
mapsforge_0.13.0+dfsg.1-3.debian.tar.xz
 bcd3c1a83c5caf1c2411d206e8211852fba4c92d8f8e71a43c0f8216aef97a8d 18967 
mapsforge_0.13.0+dfsg.1-3_source.buildinfo
Files:
 1164bebeec2e9cb420010ed5f1cc2d1b 2161 java optional 
mapsforge_0.13.0+dfsg.1-3.dsc
 bd82efd6c545d0379dfc0530d469ada6 5448 java optional 
mapsforge_0.13.0+dfsg.1-3.debian.tar.xz
 97623ce070bc92f644c087974e9d6170 18967 java optional 
mapsforge_0.13.0+dfsg.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAl6+6pUTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiIhoD/9amQMm6+h1AEJiReO7A22mFEcD9x8q
tKXlvTc8Fb/13h+mSEP1kll0O4NNzU5/qAT4iIU1RI7/q08Pp0elW4Yc0ejhc/Qa
0TcNqTZGiVk8VkSy03hTQ4VQUpIJ3QXWL6qcgrNvEC+1j1ffiz6JL09qfYsNoHsi
dYykvl5uuf0acumjd3YEjKfHTigPJEukfv3GFJNGPY2qC6hEV84E6/W498/7Fq5j
/cn9TZF+6f1ZtgfjnqeGLY8R

Bug#960717: openbox-menu: autopkgtest failure: openbox-menu: command not found

[Paul Gevers]

Source: openbox-menu
Version: 0.8.0+hg20161009-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. I copied some
of the output at the bottom of this report. Can you please investigate
the situation and fix it?

The release team has announced [1] that failing autopkgtest are now
considered RC in testing.

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openbox-menu/5496002/log.gz

autopkgtest [18:11:12]: test simple: [---
/tmp/autopkgtest-lxc.26cuvgvn/downtmp/build.6jr/src/debian/tests/simple:
line 3: openbox-menu: command not found
autopkgtest [18:11:13]: test simple: ---]



signature.asc
Description: OpenPGP digital signature

Bug#960715: cunit: autopkgtest failure: gcc: not found

[Paul Gevers]

Source: cunit
Version: 2.1-3-dfsg-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. I copied some
of the output at the bottom of this report. Can you please investigate
the situation and fix it? You seem to be missing a test dependency.

The release team has announced [1] that failing autopkgtest are now
considered RC in testing.

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cunit/5496014/log.gz


autopkgtest [18:13:13]: test test.sh: [---
/tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 7:
gcc: not found
/tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 8:
/tmp/autopkgtest-lxc.k5r5ej6m/downtmp/autopkgtest_tmp/test: not found
/tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 7:
gcc: not found
/tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 8:
/tmp/autopkgtest-lxc.k5r5ej6m/downtmp/autopkgtest_tmp/test: not found
autopkgtest [18:13:13]: test test.sh: ---]



signature.asc
Description: OpenPGP digital signature

Bug#959594: marked as done (debian-astro: FTBFS: (process:15337): WARNING **: 05:04:51.697: Unable to create profile directory (Permission denied) (13))

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 19:18:29 +
with message-id 
and subject line Bug#959594: fixed in debian-astro 2.2
has caused the Debian Bug report #959594,
regarding debian-astro: FTBFS: (process:15337): WARNING **: 05:04:51.697: 
Unable to create profile directory (Permission denied) (13)
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.)


-- 
959594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-astro
Version: 2.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):
>  debian/rules build
> dh build
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config
>dh_auto_configure
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> inkscape -z Debian-Astro-logo.svg --export-width=25 
> --export-png=Debian-Astro-logo-25x39.png
> 
> ** (process:15337): WARNING **: 05:04:51.697: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> make[1]: *** [debian/rules:8: build_logos] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/debian-astro_2.1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated debian-astro 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 20:49:33 +0200
Source: debian-astro
Architecture: source
Version: 2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 959594
Changes:
 debian-astro (2.2) unstable; urgency=medium
 .
   * Add supersmoother, gatspy, sep, keras, theano, pybdsf, pyerfa to python3
   * Add source-extractor as new name for sextractor
   * Add libcdf-healpix-java, cassis, jsofa to java
   * Remove more Python-2 packages
   * Add pybdsf to radioastronomy
   * Fix theli WNPP number
   * Remove crush: RFP closed
   * Update inkscape call for new inkscape version (Closes: #959594)
   * Push Standards-Version to 4.5.0. No changes needed
   * Push compat to 13. Replace d/compat by debhelper-compat build dep
   * Reformat d/control according to 'cme fix dpkg'
Checksums-Sha1:
 0d074988e651663c8c76fdf1de85624ed51f7e2c 3052 debian-astro_2.2.dsc
 953abba595d089d3f8f75dff782973143cdbde32 43192 debian-astro_2.2.tar.xz
Checksums-Sha256:
 2e766b3582e7b3f5eb47f1b3d772d4ae859bde7b5a375dfccfff52f7f75f3105 3052 
debian-astro_2.2.dsc
 4c5e39f5febc879138e915717e6c7d9e632142fae485955498160ada85989544 43192 
debian-astro_2.2.tar.xz
Files:
 8e9da2637a28bac3d741357fab9a7b11 3052 science optional debian-astro_2.2.dsc
 6675902cc2c3305e50673ad8c231e0d5 43192 science optional debian-astro_2.2.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl6+5wgACgkQcRWv0HcQ
3Pf0xhAApHewi4whZ/jCoVEbwXAZ9jAcVRyTwnsOmSmJaYR4WK5MdUicKrJWCixy
HlBT5rK0ByEKsnOqRh3gn1m+rP7Om8PJGgENehrnU06+Efl6phw0MqkBR33JOO5V
Z1vTpwwlffn0qGKkxaZfNnOQIpPO09eqeNVOSGRCnr7eQi+GPzFkx0jJX4dsvH79
En+ilpEDZAFGHCwB4xE7Pv+mzEXAgQW0q94C+aM3YEDsp6XUIiYLfWWhyUPUzsgu
xcR56e4TUDYQkDhvmA5sxvVAJXKpUgjLGvbyVWrRHtGGwLiyJcsbHOy+VEz+T398
8/4wZJ1sPR2Hs4mVMfHCtKvu9US/b/ame9juSg9

Bug#960714: libkeduvocdocument: autopkgtest failure: kdeinit5: not found

[Paul Gevers]

Source: libkeduvocdocument
Version: 4:17.08.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. I copied some
of the output at the bottom of this report. Can you please investigate
the situation and fix it? You seem to be missing a test dependency.

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

Paul

[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkeduvocdocument/5496019/log.gz

autopkgtest [18:12:57]: test testsuite: [---
debian/tests/testsuite.xsession: 4: kdeinit5: not found
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
debian/tests/testsuite.xsession: 1: kdeinit5_shutdown: not found
autopkgtest [18:12:58]: test testsuite: ---]



signature.asc
Description: OpenPGP digital signature

Bug#960206: olive-editor: does not start due to OpenColorIO error

[bartosz]

On 2020-05-15 16:25, Adrian Bunk wrote:

On Sun, May 10, 2020 at 06:00:04PM +0200, Bartosz Fenski wrote:

Package: olive-editor
Version: 20200210-1
Severity: grave

After fresh install olive doesn't start at all

fenio@udebian:~$ olive-editor
Using Qt version: 5.12.5
[OpenColorIO Info]: Color management disabled. (Specify the $OCIO 
environment variable to enable.)
terminate called after throwing an instance of 
'OpenColorIO::v1::Exception'
  what():  Error: Loading the OCIO profile failed. The specified file 
does not appear to be an OCIO configuration.

Aborted
...


Does it work after upgrading libyaml-cpp0.6 to 0.6.3-7?


Well now it works but I'm not the one to confirm that this upgrade fixed 
it.

But it happened yesterday on my laptop so it could fix it ;)

regards
Bartosz Fenski

Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

[Tianon Gravi]

On Tue, 5 May 2020 at 10:55, Tianon Gravi  wrote:
> I was definitely over my head with this one, so I reached out to the
> Hy community and was pointed to https://bugs.python.org/issue39562,
> which does seem quite related from my own limited understanding, so
> this might technically be a bug in the Python package?
>
> I'm including the Debian Python list on CC to hopefully see if someone
> there can provide some assistance figuring out what's necessary here.
> O:)

Looking at results from ci.debian.net[1], our autopkgtests failed on
2020-05-07 and passed today (2020-05-15).  Comparing the logs, it
appears the difference is that the last failing build was against
python3.8 version 3.8.3~rc1-1, and the successful build from today was
against python3.8 version 3.8.3-1 (lending credence to the thought it
was probably a Python bug, and that it's now fixed).

[1]: https://ci.debian.net/packages/h/hy/

Can you re-test and verify that we no longer FTBFS in your testing? O:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#960054: marked as done (src:reactphp-socket: fails to migrate to testing for too long: arch:all uploaded)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 18:04:26 +
with message-id 
and subject line Bug#960054: fixed in reactphp-socket 1.4.0-1
has caused the Debian Bug report #960054,
regarding src:reactphp-socket: fails to migrate to testing for too long: 
arch:all uploaded
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.)


-- 
960054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reactphp-socket
Version: 1.1.0-1
Severity: serious
Control: close -1 1.3.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:reactphp-socket 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=reactphp-socket




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: reactphp-socket
Source-Version: 1.4.0-1
Done: Thorsten Glaser 

We believe that the bug you reported is fixed in the latest version of
reactphp-socket, 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.
Thorsten Glaser  (supplier of updated reactphp-socket 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: SHA384

Format: 1.8
Date: Fri, 15 May 2020 19:48:17 +0200
Source: reactphp-socket
Architecture: source
Version: 1.4.0-1
Distribution: unstable
Urgency: low
Maintainer: Teckids Debian Task Force 
Changed-By: Thorsten Glaser 
Closes: 960054
Changes:
 reactphp-socket (1.4.0-1) unstable; urgency=low
 .
   * (Closes: #960054)
   * New upstream release
   * Bump debhelper
   * d/p/fix_deps.patch: redo for new version
   * Update lintian overrides; add UMEGAYA and R³:no
Checksums-Sha1:
 ead99607355e2651b0daa7ba6fd1e4506f07697d 2068 reactphp-socket_1.4.0-1.dsc
 20b0edb57f9a3f6a5e13573bbed4a9d213340b5c 35117 
reactphp-socket_1.4.0.orig.tar.gz
 1385c3dd81ddd0eb26ca87c352b670913469eca4 3168 
reactphp-socket_1.4.0-1.debian.tar.xz
Checksums-Sha256:
 6551faa55ecc548e7ced44078bde6da4d9d6829f4f8c023969723360c84bac77 2068 
reactphp-socket_1.4.0-1.dsc
 37c25ac33bcfd11acdbc5c3baba47542c24b3e1030d16a62aedf78ddf419492a 35117 
reactphp-socket_1.4.0.orig.tar.gz
 4ffebfb11c7949b8362e213ff84936f3daae508d9c77842124e12af8b057f3c7 3168 
reactphp-socket_1.4.0-1.debian.tar.xz
Files:
 b1b25244b5d628ae61b2cd4a4ae77434 2068 php optional reactphp-socket_1.4.0-1.dsc
 303062a6bc3c589619edf10a6d4c9100 35117 php optional 
reactphp-socket_1.4.0.orig.tar.gz
 0e1d97decdbd27c116d141d569915ff1 3168 php optional 
reactphp-socket_1.4.0-1.debian.tar.xz

--

Bug#960712: src:pychess: fails to migrate to testing for too long: maintainer built arch:all

[Paul Gevers]

Source: pychess
Version: 0.12.2-1
Severity: serious
Control: close -1 1.0.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:pychess 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=pychess




signature.asc
Description: OpenPGP digital signature

Processed: src:pychess: fails to migrate to testing for too long: maintainer built arch:all

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0.0-1
Bug #960712 [src:pychess] src:pychess: fails to migrate to testing for too 
long: maintainer built arch:all
Marked as fixed in versions pychess/1.0.0-1.
Bug #960712 [src:pychess] src:pychess: fails to migrate to testing for too 
long: maintainer built arch:all
Marked Bug as done

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

Bug#960405: mscgen: FTBFS and debci failure

[Niels Thykier]

Control: reassign -1 mscgen,libgd3
Control: affects -1 mscgen
control: retitle -1 mscgen crashes after libgd3 upload

On Tue, 12 May 2020 13:16:59 +0300 Adrian Bunk  wrote:
> Source: mscgen
> Version: 0.20-13
> Severity: serious
> Tags: ftbfs
> 
> https://ci.debian.net/packages/m/mscgen/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mscgen.html
> 
> [...]

This started after libgd3 was uploaded to unstable.  Related #959591

~Niels

Processed: Re: mscgen: FTBFS and debci failure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 mscgen,libgd3
Bug #960405 [src:mscgen] mscgen: FTBFS and debci failure
Bug reassigned from package 'src:mscgen' to 'mscgen,libgd3'.
No longer marked as found in versions mscgen/0.20-13.
Ignoring request to alter fixed versions of bug #960405 to the same values 
previously set
> affects -1 mscgen
Bug #960405 [mscgen,libgd3] mscgen: FTBFS and debci failure
Added indication that 960405 affects mscgen
> retitle -1 mscgen crashes after libgd3 upload
Bug #960405 [mscgen,libgd3] mscgen: FTBFS and debci failure
Changed Bug title to 'mscgen crashes after libgd3 upload' from 'mscgen: FTBFS 
and debci failure'.

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

Bug#960689: marked as done (liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 2.4.0-7))

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 17:33:44 +
with message-id 
and subject line Bug#960689: fixed in lunar-date 2.4.0-8
has caused the Debian Bug report #960689,
regarding liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 
2.4.0-7)
to be marked as done.

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

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


-- 
960689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblunar-date-dev
Version: 2.4.0-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../liblunar-date-dev_2.4.0-7_amd64.deb ...
  Unpacking liblunar-date-dev:amd64 (2.4.0-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gir-1.0/LunarDate-2.0.gir', which is also in 
package gir1.2-lunar-date-2.0 2.4.0-5
  Errors were encountered while processing:
   /var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb


cheers,

Andreas


gir1.2-lunar-date-2.0=2.4.0-5_liblunar-date-dev=2.4.0-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lunar-date
Source-Version: 2.4.0-8
Done: xiao sheng wen 

We believe that the bug you reported is fixed in the latest version of
lunar-date, 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.
xiao sheng wen  (supplier of updated lunar-date 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 22:06:09 +0800
Source: lunar-date
Architecture: source
Version: 2.4.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Chinese Team 
Changed-By: xiao sheng wen 
Closes: 960689
Changes:
 lunar-date (2.4.0-8) unstable; urgency=medium
 .
   [ 肖盛文 ]
   * Fix for piuparts fails to upgrade from testing, closes: #960689
Checksums-Sha1:
 c63b38e60299a0f55abb6b65d4c86b5fc6eafb90 2403 lunar-date_2.4.0-8.dsc
 75fe33350fdfb7d790f77ebcfb47ee8f17ac2a42 3980 lunar-date_2.4.0-8.debian.tar.xz
Checksums-Sha256:
 58811407ab7be638919e56fdd45b412bbdb780edc33ecf1654d848f11ce3cb63 2403 
lunar-date_2.4.0-8.dsc
 2631f776ce9933f0345b74972c19bac079a244869fc8b4335deae7540933b310 3980 
lunar-date_2.4.0-8.debian.tar.xz
Files:
 6e68c43baea95c1e5c7de2369cf86f9b 2403 libs optional lunar-date_2.4.0-8.dsc
 32d14bdde1d98d6e50bd0e58db0a3ee0 3980 libs optional 
lunar-date_2.4.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl6+0PkACgkQM1X01jtY
Icy5DhAAtGKcLdAECcvEsKFdC9+WrhoVGasdv8xjch68VmS2Ejzs4d5aMYOQOPQS
qNFcL30Qxobe/4jaVs60wHbwQjbT1JcPCUaUx5IZeYoCjKFZYT6dCoXzK5npmHRa
x4aal66jcncnWtFyBp0PfjgxuzhwR9bwwVdrsLF8ZX/rsRpzfYG1rrPvJ6QlqJ0h
t2J4M4RQ7IgMwQl3jPLhGz/roe5QwhPLzoQp4LkWrDDflSdmgW3owe2av5ioebfV
C0npUj2CyyG3zGqmcGKpkryhLmIy6vN90v7v804H6cBVTfNzDsf/VD+VwTFodowL
+eIlGCQMIpDdntTUh7JgbiK0ig2qRkhb2hg2QWQIhxhur789mfNwr0lOEl1bEBsQ
M1gGnEUGe3JidoqeurV09jlJTeV7D/ZjJIFWhOrNCyp/A3KqjNMxdkOoSZ7kMrrZ
0cf39JMSm3Pq/oeE7nm0UHkchyKdS2Qn1eGuvJJq3ku3/WwWRbmaTsrPrU+sV+zc
+YAivlLxZQbkpsBwVxJidEgz/zwDwoQtMexm47Kc+BLiXz9qOR6/wDkGpttE+Z9J
Z8TRcA7jyr7v9ysO626dKdeSdkiw9H8ptjCXulZ1W3D8l0Eg99TpFDxoSpSVHdfE
yR9eZ6n8xuVNw6jgTZ4XPafFUD0FSiQQOGSHYd5VCHJ0RVIKD7I=
=vRDF
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> # version not uploaded yet
> notfixed 960689 lunar-date/2.4.0-8
Bug #960689 [liblunar-date-dev] liblunar-date-dev: missing Breaks+Replaces: 
gir1.2-lunar-date-2.0 (<< 2.4.0-7)
The source lunar-date and version 2.4.0-8 do not appear to match any binary 
packages
No longer marked as fixed in versions lunar-date/2.4.0-8.
> tags 960689 - fixed
Bug #960689 [liblunar-date-dev] liblunar-date-dev: missing Breaks+Replaces: 
gir1.2-lunar-date-2.0 (<< 2.4.0-7)
Removed tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#960294: closed by Debian FTP Masters (reply to Etienne Mollier ) (Bug#960294: fixed in tigr-glimmer 3.02b-5)

[Helmut Grohne]

On Thu, May 14, 2020 at 07:09:06AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:tigr-glimmer package:
> 
> #960294: tigr-glimmer does not trap errors from make

Given that the previous fix of the bug was incomplete, I'd like to
confirm that with this fix, it really fails instantly. Also verbose
build logs help a lot. Thank you for bearing with me.

Helmut

Bug#956903: clang-tidy-6.0: Depends on cruft package python-yaml

[Scott Kitterman]

NMU diff to drop the clang-tidy-6.0 binary as discussed.  I'll upload this 
shortly.

Scott Kdiff -Nru llvm-toolchain-6.0-6.0.1/debian/changelog llvm-toolchain-6.0-6.0.1/debian/changelog
--- llvm-toolchain-6.0-6.0.1/debian/changelog	2020-03-23 06:59:23.0 -0400
+++ llvm-toolchain-6.0-6.0.1/debian/changelog	2020-05-15 12:25:16.0 -0400
@@ -1,3 +1,12 @@
+llvm-toolchain-6.0 (1:6.0.1-14.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Maintainer agreed NMU to drop clang-tidy-6.0 since it is not needed to
+support ghc, the only remaining llvm-6.0 user, and allows progress on
+python2 removal (Closes: #956903)
+
+ -- Scott Kitterman   Fri, 15 May 2020 12:25:16 -0400
+
 llvm-toolchain-6.0 (1:6.0.1-14) unstable; urgency=medium
 
   * debian/patches/947f9692440836dcb8d88b74b69dd379d85974ce.patch:
diff -Nru llvm-toolchain-6.0-6.0.1/debian/control llvm-toolchain-6.0-6.0.1/debian/control
--- llvm-toolchain-6.0-6.0.1/debian/control	2020-03-22 13:28:44.0 -0400
+++ llvm-toolchain-6.0-6.0.1/debian/control	2020-05-15 12:25:13.0 -0400
@@ -69,19 +69,6 @@
  .
  This package also provides vim and emacs plugins.
 
-Package: clang-tidy-6.0
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, python2,
- libllvm6.0 (= ${binary:Version}), libclang-common-6.0-dev,
- clang-tools-6.0, python-yaml
-Replaces: clang-modernize-6.0, clang-6.0 (<< 1:6.0~svn250696-1)
-Breaks: clang-modernize-6.0, clang-6.0 (<< 1:6.0~svn250696-1)
-Description: clang-based C++ linter tool
- Provide an extensible framework for diagnosing and fixing typical programming
- errors, like style violations, interface misuse, or bugs that can be deduced
- via static analysis. clang-tidy is modular and provides a convenient interface
- for writing new checks.
-
 Package: libclang1-6.0
 Section: libs
 Architecture: any
diff -Nru llvm-toolchain-6.0-6.0.1/debian/rules llvm-toolchain-6.0-6.0.1/debian/rules
--- llvm-toolchain-6.0-6.0.1/debian/rules	2020-03-22 17:03:20.0 -0400
+++ llvm-toolchain-6.0-6.0.1/debian/rules	2020-05-15 12:25:13.0 -0400
@@ -519,6 +519,12 @@
 	rm -rf $(CURDIR)/debian/tmp/usr/lib/llvm-$(LLVM_VERSION)/lib/cmake/polly/*.cmake
 endif
 endif
+	# clang-tidy no longer built
+	rm -rf $(CURDIR)/debian/tmp/usr/bin/clang-tidy-6.0
+	rm -rf $(CURDIR)/debian/tmp/usr/lib/llvm-6.0/bin/clang-tidy
+	rm -rf $(CURDIR)/debian/tmp/usr/lib/llvm-6.0/share/clang/run-clang-tidy.py
+	rm -rf $(CURDIR)/debian/tmp/usr/lib/llvm-6.0/share/clang/clang-tidy-diff.py
+
 	dh_install --fail-missing
 
 override_dh_installdeb:


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

Processed: Re: [Pkg-nagios-devel] Bug#960701: php-icinga: Uncaught ErrorException \Icinga\Web\ViewStream::stream_set_option is not implemented!

[Debian Bug Tracking System]

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

> fixed 960701 icingaweb2/2.8.0~rc1-1~exp1
Bug #960701 [php-icinga] php-icinga: Uncaught ErrorException 
\Icinga\Web\ViewStream::stream_set_option is not implemented!
Marked as fixed in versions icingaweb2/2.8.0~rc1-1~exp1.
> thanks
Stopping processing here.

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

Bug#960701: marked as done (php-icinga: Uncaught ErrorException \Icinga\Web\ViewStream::stream_set_option is not implemented!)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 18:44:56 +0200
with message-id <25b69a34-270c-bd2f-dfd7-653c4c8d3...@xs4all.nl>
and subject line Re: [Pkg-nagios-devel] Bug#960701: php-icinga: Uncaught 
ErrorException \Icinga\Web\ViewStream::stream_set_option is not implemented!
has caused the Debian Bug report #960701,
regarding php-icinga: Uncaught ErrorException 
\Icinga\Web\ViewStream::stream_set_option is not implemented!
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.)


-- 
960701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-icinga
Version: 2.7.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

I had a working Icinga Web setup. nginx as a frontend, redirecting to
Icinga:

location ~ ^/icingaweb2/index\.php(.*)$ {
fastcgi_pass unix:/var/run/php/php-fpm.sock;
  fastcgi_index index.php;
include fastcgi_params;
  fastcgi_param SCRIPT_FILENAME /usr/share/icingaweb2/public/index.php;
fastcgi_param ICINGAWEB_CONFIGDIR /etc/icingaweb2;
  fastcgi_param REMOTE_USER $remote_user;
  }

location ~ ^/icingaweb2(.+)? {
  alias /usr/share/icingaweb2/public;
index index.php;
  try_files $1 $uri $uri/ /icingaweb2/index.php$is_args$args;
  }
}


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

I just upgraded my "sid" machine. Trying to access the Icinga Web page
of my installation no longer works.

   * What was the outcome of this action?

In the browser (Firefox), just this message:

Fatal error: Uncaught ErrorException: Uncaught ErrorException: include(): 
\Icinga\Web\ViewStream::stream_set_option is not implemented! in 
/usr/share/php/Icinga/Web/View.php:262 Stack trace: #0 
/usr/share/php/Icinga/Web/View.php(262): 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}() #1 
/usr/share/php/Icinga/Web/View.php(262): include() #2 
/usr/share/icingaweb2/library/vendor/Zend/View/Abstract.php(877): 
Icinga\Web\View->_run() #3 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/Helper/ViewRenderer.php(904):
 Zend_View_Abstract->render() #4 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/Helper/ViewRenderer.php(925):
 Zend_Controller_Action_Helper_ViewRenderer->renderScript() #5 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/Helper/ViewRenderer.php(964):
 Zend_Controller_Action_Helper_ViewRenderer->render() #6 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/HelperBroker.php(272):
 Zend_Controller_Action_Helper_ViewRenderer->postDispatch() #7 /usr/share/icin 
in /usr/share/icingaweb2/library/vendor/Zend/Controller/Plugin/Broker.php on 
line 259

   * What outcome did you expect instead?

Ordinary Icinga Web page.


I also tried with the package in experimental,
php-icinga_2.8.0~rc1-1~exp2_all.deb. I got a different problem: the
CSS does not load and nginx logs:

2020/05/15 14:33:17 [error] 21559#21559: *65 FastCGI sent in stderr: "PHP 
message: PHP Fatal error:  Uncaught ErrorException: file_get_contents(): 
Filename cannot be empty in /usr/share/php/Icinga/Web/LessCompiler.php:172
Stack trace:
#0 [internal function]: 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}()
#1 /usr/share/php/Icinga/Web/LessCompiler.php(172): file_get_contents()
#2 /usr/share/php/Icinga/Web/StyleSheet.php(172): 
Icinga\Web\LessCompiler->render()
#3 /usr/share/php/Icinga/Web/StyleSheet.php(210): 
Icinga\Web\StyleSheet->render()
#4 /usr/share/php/Icinga/Application/webrouter.php(61): 
Icinga\Web\StyleSheet::send()
#5 /usr/share/icingaweb2/public/index.php(4): require_once('/usr/share/php/...')
#6 {main}
  thrown in /usr/share/php/Icinga/Web/LessCompiler.php on line 172" while 
reading response header from upstream, client: 192.168.2.1, server: _, request: 
"GET /icingaweb2/css/icinga.min.css HTTP/2.0", upstream: 
"fastcgi://unix:/var/run/php/php-fpm.sock:", host: "icinga2.nic.example", 
referrer: "https://icinga2.nic.example/icingaweb2/dashboard";
2020/05/15 14:33:17 [error] 21559#21559: *65 FastCGI sent in stderr: "PHP 
message: PHP Fatal error:  Uncaught ErrorException: 
file_get_contents(/usr/share/icingaweb2/public/js/icinga/behavior/modal.js): 
failed to open stream: No such file or directory in 
/usr/share/php/Icinga/Web/JavaScript.php:126
Stack trace:
#0 [internal function]: 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}()
#1 /usr/share/php/Icinga/Web/JavaScript.php(126): file_get_contents

Bug#960151: marked as done (petsc: FTBFS during arch:all build: petscrules: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 16:35:58 +
with message-id 
and subject line Bug#960151: fixed in petsc 3.13.1+dfsg1-1
has caused the Debian Bug report #960151,
regarding petsc: FTBFS during arch:all build: petscrules: No such file or 
directory
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.)


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

Hi,

petsc/experimental FTBFS during the arch:all build (on amd64):

Completed test examples
make[2]: Leaving directory '/build/petsc-3.13.0+dfsg2'
make[2]: Entering directory '/build/petsc-3.13.0+dfsg2'
/build/petsc-3.13.0+dfsg2/lib/petsc/conf/rules:788: 
/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscrules: No 
such file or directory
make[3]: *** No rule to make target 
'/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscrules'.  
Stop.
gmakefile:5: x86_64-linux-gnu-real/lib/petsc/conf/petscvariables: No such file 
or directory
make[2]: *** [GNUmakefile:17: 
/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/include/petscconf.h] Error 2
make[2]: *** Waiting for unfinished jobs
/build/petsc-3.13.0+dfsg2/lib/petsc/conf/rules:788: 
/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscrules: No 
such file or directory
make[3]: *** No rule to make target 
'/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscrules'.  
Stop.
make[2]: *** [GNUmakefile:17: 
/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscvariables] 
Error 2
/build/petsc-3.13.0+dfsg2/lib/petsc/conf/rules:788: 
/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscrules: No 
such file or directory
make[3]: *** No rule to make target 
'/build/petsc-3.13.0+dfsg2/x86_64-linux-gnu-real/lib/petsc/conf/petscrules'.  
Stop.
make[2]: *** [GNUmakefile:17: 
x86_64-linux-gnu-real/lib/petsc/conf/petscvariables] Error 2
make[2]: Leaving directory '/build/petsc-3.13.0+dfsg2'
make[1]: *** [debian/rules:265: override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/petsc-3.13.0+dfsg2'
make: *** [debian/rules:136: build-indep] Error 2


Andreas


petsc_3.13.0+dfsg2-1_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: petsc
Source-Version: 3.13.1+dfsg1-1
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
petsc, 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.
Drew Parsons  (supplier of updated petsc 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: Fri, 15 May 2020 18:54:18 +0800
Source: petsc
Architecture: source
Version: 3.13.1+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 960151
Changes:
 petsc (3.13.1+dfsg1-1) experimental; urgency=medium
 .
   * New upstream release.
   * only run tests for arch-any builds. Closes: #960151.
   * apply lintian overrides to let matlab scripts remain executable,
 and test scripts remain not executable.
   * set ts/tutorials/hybrid/run.sh executable in examples package.
Checksums-Sha1:
 6def4e5fde91f921d64ffb333a481eeac11cfd27 3412 petsc_3.13.1+dfsg1-1.dsc
 8a6693c9677481537186020df260f13a117ab047 17068412 
petsc_3.13.1+dfsg1.orig.tar.xz
 759a3f81d36c895818d1a707809df0fe8739b34d 43868 
petsc_3.13.1+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 f0cbee8c13d554f35605df8fc8736648e1a6c592d43facce83679bc9f58e3d67 3412 
petsc_3.13.1+dfsg1-1.dsc
 fbd1425ac5707ca2a7a463acdd9eee4094b8d20aae845d0f930a0d90d125b753 17068412 
petsc_3.13.1+dfsg1.orig.tar.xz
 e543f587636c2fd1375482e82ccca27c735c52b5a1f1ffbd28d864cfb1feeaec 43868 
petsc_3.13.1+dfsg1-1.debian.tar.xz
Files:
 8bc5efc20154e56c2e9ff351396bf5a2 3412 devel optional petsc_3.13.1+dfsg1-1.dsc
 f5da6a0fdee94de512501186e661fb23 17068412 devel optional 
petsc_3.13.1+dfsg1.orig.tar.xz
 ba278cea86853a7b5d0a28b

Bug#960615: marked as done (libbssolv-perl: Build-Depends on cruft package libsolv0-dev and FTBFS with libsolv-dev 0.7.11-1)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 16:05:10 +
with message-id 
and subject line Bug#960615: fixed in libbssolv-perl 0.17-2
has caused the Debian Bug report #960615,
regarding libbssolv-perl: Build-Depends on cruft package libsolv0-dev and FTBFS 
with libsolv-dev 0.7.11-1
to be marked as done.

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

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


-- 
960615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: libbssolv-perl
Source-Version: 0.17-2
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libbssolv-perl, 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.
gregor herrmann  (supplier of updated libbssolv-perl 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 17:45:57 +0200
Source: libbssolv-perl
Architecture: source
Version: 0.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 960615
Changes:
 libbssolv-perl (0.17-2) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depends: replace libsolv0-dev with libsolv-dev.
 Thanks to Daniel Schepler for the bug report.
 (Closes: #960615)
   * Drop 2001_libsolv-dev-installs-to-multiarch-dest.patch which is not
 needed anymore wit LibSolv 7.
Checksums-Sha1:
 9177c8aa6f999359675f830eedf4a5a7d18e4c41 2329 libbssolv-perl_0.17-2.dsc
 a08fcdd0e009ec3466b1fd9cd250eb61db021626 3040 
libbssolv-perl_0.17-2.debian.tar.xz
Checksums-Sha256:
 62f5dcf4a7e34de4a92187baa8787da17b3b77b65487c5dcf3e9efa8ab9f792b 2329 
libbssolv-perl_0.17-2.dsc
 147b39301670e1820d492002b6fd6f9bebaf3785c7ce68fdaa96c97ac84259ed 3040 
libbssolv-perl_0.17-2.debian.tar.xz
Files:
 0c0373f98096ebdb2ff236dabfc302ab 2329 perl optional libbssolv-perl_0.17-2.dsc
 ee0896c50378d8938921538f9f063f66 3040 perl optional 
libbssolv-perl_0.17-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl6+udVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZs1xAAgmqM2BvDD4dExbEfAhc3MiIPYolTyQz0qiiOrusC8WecJ/TEydWXudHj
EdJWa1NA8ksXOh/6HZXFfK46Hsefygn+s6ajNCgRqY+iUh1HbFv9ONCngLlpaIsj
dOy60vMkxQB4TzdsgJQ0E88vOCdudKxv+ruLODY/sz35sXR9C42CBXBUUBUG959y
y87Yaeq4Yv7+4rmmEU43oMkepLBfQ1PnUNCYwc1zPiJROrBWvHmq1o52DJ9swUi6
ZT9nRW6Y0nw9fv/kjt2TY0KGYTzq/rzwf+Xt3C08omx68EdVBATthgeFiNEu9aMm
APBgYR4TyWNcBCKoCz6obfpj5zKWUOsiY0DM/MN7sFjpiuBBkGSEXxcx0tLazFlH
aIBF3ofpl7cYXqZDx53DCZibcRo8aOH8sFjCRbiYhoaji/KKUZGjc1VFhB9A8eVu
XcZINyBr9PU6Pz7makcw5SeUPeGdjI9hCUjNby8YeI2TJM7nV3YqXoYE0eO1HQgv
hjCREMNO3gvyWYbDPXa75ljhFVBu/5xK2kkQyvdT0CvDiQW/7jHBFHFRA+fQIQbp
o3gylU35YN/+xYzW3CF9hnMaNCm3+vlCIjC+Ah8niUfBD8z//1VPS1P59UHDBMwB
Z/ss5uKDfC/H8RvJxj9vYEn9nSZRoDhnDrDz0OIANzcFyyxcfmw=
=YBgo
-END PGP SIGNATURE End Message ---

Bug#960458: marked as done (libreswan: CVE-2020-1763)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 16:02:16 +
with message-id 
and subject line Bug#960458: fixed in libreswan 3.27-6+deb10u1
has caused the Debian Bug report #960458,
regarding libreswan: CVE-2020-1763
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.)


-- 
960458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libreswan
Version: 3.29-2
Severity: important
Tags: security upstream
Control: found -1 3.27-6

Hi,

The following vulnerability was published for libreswan.

CVE-2020-1763[0]:
| An out-of-bounds buffer read flaw was found in the pluto daemon of
| libreswan from versions 3.27 till 3.31 where, an unauthenticated
| attacker could use this flaw to crash libreswan by sending specially-
| crafted IKEv1 Informational Exchange packets. The daemon respawns
| after the crash.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-1763
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1763
[1] https://libreswan.org/security/CVE-2020-1763/CVE-2020-1763.txt

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libreswan
Source-Version: 3.27-6+deb10u1
Done: Salvatore Bonaccorso 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 13 May 2020 05:33:51 +0200
Source: libreswan
Architecture: source
Version: 3.27-6+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Daniel Kahn Gillmor 
Changed-By: Salvatore Bonaccorso 
Closes: 960458
Changes:
 libreswan (3.27-6+deb10u1) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * DoS attack via malicious IKEv1 informational exchange message
 (CVE-2020-1763) (Closes: #960458)
Checksums-Sha1: 
 6b268a226761104a440491749596bcd865d480fe 2765 libreswan_3.27-6+deb10u1.dsc
 c2e4b418ea286168bb022620a6af6a70cecffd14 3720103 libreswan_3.27.orig.tar.gz
 ed4c52832275d5e3dafaeb445b88dfa01ce17806 801 libreswan_3.27.orig.tar.gz.asc
 577d27df6434544b6b8067a9a2432266ca4d6974 19072 
libreswan_3.27-6+deb10u1.debian.tar.xz
Checksums-Sha256: 
 f7305127d20f4cadd5dcbd898df1c375e8dd1c5d44dfc9d889e7c24c9fad011c 2765 
libreswan_3.27-6+deb10u1.dsc
 ead07dd701116094b483dc57e54e2a5ee9a06d3982bb142260bcbf3d1faf7b82 3720103 
libreswan_3.27.orig.tar.gz
 1c5d751bcea35f0fa90a5abd214634dbc04e086fa92286e7b3e5574c97a33d3d 801 
libreswan_3.27.orig.tar.gz.asc
 b259466f07f986be3161a1707f297de003e5fae37e55f99155cec7f18a6a788a 19072 
libreswan_3.27-6+deb10u1.debian.tar.xz
Files: 
 1fd22c26c89427f1f2b00bb59155c575 2765 net optional libreswan_3.27-6+deb10u1.dsc
 a53f0545628cf3b5ccfc72a999388eb8 3720103 net optional 
libreswan_3.27.orig.tar.gz
 8811894df384062ebbe9d8f42a458e77 801 net optional 
libreswan_3.27.orig.tar.gz.asc
 45c6c4ddc7879cf1f874e265eee3ce90 19072 net optional 
libreswan_3.27-6+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl67btRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EId8P/jF2iiQgPiE6hPI90nyW6o5xizrSI/2y
rk0ogSvimHWU47IYAhXXAXzCUTsvrXaP9y03MKwigy6n7SuaBPXp2hWttIXWYF2+
iEuWPUaUOcTj8zwG0PIZW0eyR7pbt3pU7adsZYgKsZehOrvVctVmHoxRhqLwIAQY
794+ZZzwSIPsXRTL+yQUzMAbmxdIfBuxhHCMORu+7Skf50Nyi9JKzgPNMTnWTBjD
V9OCALUMoiXUegw9+8c4DbCbeyboNLimcEmYbYMSpbis56kjiYs8/xESocRMEQVF
hRotFaA7/1OGCodC6yYs+4hvJAmZG7251r2YjuUh8RUP4MyNC5s+xNmbWkGxg5BQ
+3lURv5HPbKC7xZQ3v4bkkbwC7INKb8sin6ZQftNVCw2jAIHDFrkIEQBnYN7/pnq
TIFsNIG+JSvMZJxVOo+41lxqmvhM8n9YVEu6LLee9He0dstcuYXAdzzar3rLxJSp
77SMB8Vg7SU+1yT+hl3wSk4/FC8S7uhQOYJXKssHaHNOkagxawOC201zh+f

Processed: Bug#960615 marked as pending in libbssolv-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #960615 [src:libbssolv-perl] libbssolv-perl: Build-Depends on cruft package 
libsolv0-dev and FTBFS with libsolv-dev 0.7.11-1
Added tag(s) pending.

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

Bug#960615: marked as pending in libbssolv-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libbssolv-perl/-/commit/37906c5bc2c357cc7e696e1426af791e943c5f0c


Build-Depends: replace libsolv0-dev with libsolv-dev.

Thanks: Daniel Schepler for the bug report.
Closes: #960615


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/960615

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

[gregor herrmann]

Control: retitle -1 libbssolv-perl: Build-Depends on cruft package libsolv0-dev 
and FTBFS with libsolv-dev 0.7.11-1
Control: tag -1 + upstream confirmed

On Thu, 14 May 2020 10:05:29 -0700, Daniel Schepler wrote:

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

(Actually libsolv-dev.)

And it fails to build with libsolv-dev 0.7.11-1:

   dh_auto_build
make -j4
make[1]: Entering directory '/build/libbssolv-perl-0.17'
Running Mkbootstrap for BSSolv ()
"/usr/bin/perl" "/usr/share/perl/5.30/ExtUtils/xsubpp"  -typemap 
'/usr/share/perl/5.30/ExtUtils/typemap' -typemap '/build/
chmod 644 "BSSolv.bs"
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- BSSolv.bs 
blib/arch/auto/BSSolv/BSSolv.bs 644
cp BSSolv.pm blib/lib/BSSolv.pm
mv BSSolv.xsc BSSolv.c
x86_64-linux-gnu-gcc -c  -I/usr/include/`dpkg-architecture 
-qDEB_BUILD_MULTIARCH`/solv -D_REENTRANT -D_GNU_SOURCE -DDEBIAN
BSSolv.xs:18:10: fatal error: solvversion.h: No such file or directory
   18 | #include "solvversion.h"
  |  ^~~
compilation terminated.
make[1]: *** [Makefile:334: BSSolv.o] Error 1
make[1]: Leaving directory '/build/libbssolv-perl-0.17'
dh_auto_build: error: make -j4 returned exit code 2
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Aha, this looks like it's caused by 
debian/patches/2001_libsolv-dev-installs-to-multiarch-dest.patch.

Indeed, disabling the patch makes the build and the tests succeed.

Cheers,
gregor, uploading shortly

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Josh With: My father is a husbandman


signature.asc
Description: Digital Signature

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

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libbssolv-perl: Build-Depends on cruft package libsolv0-dev and 
> FTBFS with libsolv-dev 0.7.11-1
Bug #960615 [src:libbssolv-perl] libbssolv-perl: Build-Depends on cruft package 
libsolv0-dev
Changed Bug title to 'libbssolv-perl: Build-Depends on cruft package 
libsolv0-dev and FTBFS with libsolv-dev 0.7.11-1' from 'libbssolv-perl: 
Build-Depends on cruft package libsolv0-dev'.
> tag -1 + upstream confirmed
Bug #960615 [src:libbssolv-perl] libbssolv-perl: Build-Depends on cruft package 
libsolv0-dev and FTBFS with libsolv-dev 0.7.11-1
Added tag(s) upstream and confirmed.

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

Bug#960573: marked as done (python3-yt: h5py.File requires access mode to be specified)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 15:34:55 +
with message-id 
and subject line Bug#960573: fixed in yt 3.6.0-3
has caused the Debian Bug report #960573,
regarding python3-yt: h5py.File requires access mode to be specified
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.)


-- 
960573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-yt
Version: 3.6.0-2
Severity: normal

h5py is changing upstream to require the mode ('r', 'w', etc) to be
specified when h5py.File is used.  The Debian version of h5py has
already applied the upstream commits making this mandatory.

This affects yt in TestImageArray.test_image_array_hdf5 and test_h5_io,
specifically write_hdf5 in yt/units/yt_array.py line 965

They seem to be write tests so probably you want h5py.File(filename, 'w')



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

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

Versions of packages python3-yt depends on:
ii  libc6   2.30-8
ii  libgomp110.1.0-1
ii  libjs-jquery3.5.1+dfsg-3
pn  libjs-leaflet   
ii  python3 3.8.2-3
ii  python3-h5py2.10.0-8
ii  python3-ipython 7.14.0-1
ii  python3-matplotlib  3.2.1-1+b1
ii  python3-numpy [python3-numpy-abi9]  1:1.18.4-1
ii  python3-pkg-resources   46.1.3-1
ii  python3-sympy   1.5.1-2.1

python3-yt recommends no packages.

Versions of packages python3-yt suggests:
ii  python3-astropy  4.0.1+post1-1
pn  python3-pyx  
ii  python3-scipy1.4.1-2
--- End Message ---
--- Begin Message ---
Source: yt
Source-Version: 3.6.0-3
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
yt, 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.
Ole Streicher  (supplier of updated yt 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 16:54:47 +0200
Source: yt
Architecture: source
Version: 3.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 960573
Changes:
 yt (3.6.0-3) unstable; urgency=medium
 .
   * Add mode argument to h5py.File (Closes: #960573)
   * Push dh compat level to 13
Checksums-Sha1:
 a3c22464001bcc302023a321588a86f290595020 2213 yt_3.6.0-3.dsc
 dca28f60758a2e1898d78ff50a3f71d63020dbd2 10624 yt_3.6.0-3.debian.tar.xz
Checksums-Sha256:
 c15dfee5636e4cc487f022cdf346b7be19206d691793f5a7c0c47657608e1211 2213 
yt_3.6.0-3.dsc
 a4d7786a7cc3075c0ef763c9f3dbfd256450f3eddca4ea047c3b0946a3ee4d0b 10624 
yt_3.6.0-3.debian.tar.xz
Files:
 f8c74f6079525f1045e38855260b77f8 2213 python optional yt_3.6.0-3.dsc
 6e1989ebd5c2507be41315c5818cb7c5 10624 python optional yt_3.6.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl6+sc8ACgkQcRWv0HcQ
3PdQMRAAkn1c1AbM5PDsJZtfnbyP4r5O73K6MFKRQU11PaEMS+FuHPzjlVGzcgvj
oAs262qulDdsQ6OtSZ9oG9VWQrQbJ/oSgskocdewEkJIS5dll7FrIo2NHM+XqTfh
XxvkNbsIBfuAfWygTbxsFsfCWoMWH+29e//we6695T4VcrYy1hAJJaPbta4NY2RO
8JqfVI+KMX++XOsJv9WeiwCXUiyCGAjse3fnsYOY5LxZCE+KuDjO9NhX9qSqiqc1
qpQPnlzOGWJEgalvOkxesKbtTqiSi1Ymfv3kwF4FxMKPKMR3cs+hR3JXTbqPDpnx
4XX6DzUCszIwT9/xn9qwD5GU9QOm4qyKioxxEJsCe6qkjQDpT2rO8Uq/3sGRQRTd
F9lCgaTOIRlLA8mxmQPO7ZM2FK4eSAcUxDO821qKS2bKJAXf6gJAM1RJrfD2Qg0i
WwVodbX/icuTwTAGaIJYfX/dcAikDKiUa4ie164+wAlfcwpIeSeD+mZ4ZnVuVTmW
4fuEcQww6wza9EOm1lmPHdc6ssc57w+5Coxxbtb2QGI4Kd+Pe3fMzKAaonwlbbcO
nPqbuUZYEGmsLZPDrs0Rhivtzpz90r5joGpCBr3TKHT2nTR3jbvxtye8K1mwx/0H
M5pGWbNN+jrCHjrTgbbxrhTcqb0vGBAZyI/xqTAiz+JT6fmLkgY=
=SNmx
-END PGP SIGNATURE

Bug#960703: mrpt: FTBFS on amd64: test failures

[Sebastian Ramacher]

Source: mrpt
Version: 1:2.0.3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

mrpt failed to build on the amd64 buildd:
https://buildd.debian.org/status/fetch.php?pkg=mrpt&arch=amd64&ver=1%3A2.0.3-2&stamp=1589545331&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#960326: // after this bug fix json processing broken on 16.04,18.04 and 20.04

[gjakop]

Hi,
today many people using our program faced with strange crashes and problems.
Digging into it we found that it's because json upgrade
Following is simple program built using "g++ main.cpp -ljson-c"

#include 
#include 

int main() {

const char* json =
R"({"SyncResponse":{"status":"success","StreamCheckerMode":false,"UniqueVisitors":false,"RoutesHash":"","Routes":[],"IpRanges":[],"ServerAuthorizationProperties":{"ServerAuthPropertiesHash":""},"CamerasHash":"","Cameras":[],"StreamsHash":"","Streams":[],"RtmpSettings":{"hash":"1589511271996","interfaces":[{"ip":"172.16.3.100","port":1935,"ssl":false}],"login":"","password":"","duration":6,"chunk_count":4,"hls_part_duration":1000,"dash_template":"NUMBER","generate_icecast_metadata":true,"protocols":["HLS","RTMP","MPEG2TS","ICECAST","DASH","RTSP","SLDP"],"apps":[{"app":"local","login":"root","password":"psw","duration":6,"chunk_count":4,"hls_part_duration":1000,"dash_template":"TIME","generate_icecast_metadata":true,"protocols":["HLS","RTMP","MPEG2TS","ICECAST","DASH","RTSP","SLDP"]}],"abr":[]},"RtspSettings":{"hash":"1589502370997","interfaces":[]},"IcecastSettings":{"hash":"1589502373053","interfaces":[]},"LivePullSettings":{"hash":"1589502491133","streams":[]},"RtmpPublishSettings":{"hash":"1589502499024","settings":[]},"RtspPublishSettings":{"hash":"1589502497581","settings":[]},"ManagedTasks":
{"hash":"0", "tasks": []},"HlsDRMSettings": {"hash":"0", "url":"",
"key":"", "KeyServerSettings":
{}},"HttpOriginApps":{"hash":"0","apps":[]},"Aliases":{"hash":"0","settings":[]},"DataSlicesInfo":{"hash":"1","data_slices":[{"id":"54118","tz":0}]},"UDPSenderSettings":{"hash":"0","settings":[]},"PayPerPublishSettings":{"hash":"0","url":"","auth_group_interval":500,"apps":[]},"DvrSettings":{"hash":"1589502502894","settings":[]},"UserAgentGroupSettings":{"hash":"0","settings":[]},"RefererGroupSettings":{"hash":"0","settings":[]},"VideoEncodersInfo":{"hash":"0","encoders":[]},"AudioEncodersInfo":{"hash":"0","encoders":[]},"StreamOverrideSettings":{"hash":"0","settings":[]},"IcecastStreamSettings":
{"hash":"1589502513135","settings":
[]},"AuthHandlerSettings":{"hash":""},"ServerSettings":{"MaxCacheSize":64,"MaxFileCacheSize":4096,"LogMode":"debug"}}})";
json_object *rules = json_tokener_parse(json);
if(!rules) {
return -1;
}
printf("json parsed\n");
json_object_put(rules);

return 0;
}

if I run it when latest "libjson-c3:amd64
0.12.1-1.3ubuntu0.1" installed on my ubuntu 18.04 I get crash with
"lh_table_new: calloc failed" message
but if I downgrade to previous libjson-c3:amd64 0.12.1-1.3
it works fine

Processed: Re: Bug#960206: olive-editor: does not start due to OpenColorIO error

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libyaml-cpp0.6
Bug #960206 [olive-editor] olive-editor: does not start due to OpenColorIO error
Bug reassigned from package 'olive-editor' to 'libyaml-cpp0.6'.
No longer marked as found in versions olive-editor/20200210-1.
Ignoring request to alter fixed versions of bug #960206 to the same values 
previously set
> forcemerge 959201 -1
Bug #959201 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] jami-daemon: dring does not start due to a symbol lookup error
Bug #959556 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined 
reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
Bug #959586 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: 
undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
Bug #959596 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] blender: FTBFS: subprocess.CalledProcessError: Command 
'['/<>/obj-x86_64-linux-gnu/bin/blender', '--help']' returned 
non-zero exit status 127.
Bug #959657 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] olive-editor: Does not start: symbol lookup error
Bug #959657 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] olive-editor: Does not start: symbol lookup error
Removed indication that 959657 affects olive-editor, src:openimageio, 
src:olive-editor, src:blender, blender, jami-daemon, and libopencolorio1v5
Added indication that 959657 affects 
src:olive-editor,src:blender,libopencolorio1v5,jami-daemon,blender,src:openimageio,olive-editor
Removed indication that 959201 affects blender, libopencolorio1v5, jami-daemon, 
src:openimageio, olive-editor, src:blender, and src:olive-editor
Added indication that 959201 affects 
src:olive-editor,src:blender,libopencolorio1v5,jami-daemon,blender,src:openimageio,olive-editor
Removed indication that 959556 affects blender, libopencolorio1v5, jami-daemon, 
olive-editor, src:openimageio, src:blender, and src:olive-editor
Added indication that 959556 affects 
src:olive-editor,src:blender,libopencolorio1v5,jami-daemon,blender,src:openimageio,olive-editor
Removed indication that 959586 affects blender, jami-daemon, libopencolorio1v5, 
src:openimageio, olive-editor, src:olive-editor, and src:blender
Added indication that 959586 affects 
src:olive-editor,src:blender,libopencolorio1v5,jami-daemon,blender,src:openimageio,olive-editor
Removed indication that 959596 affects blender, jami-daemon, libopencolorio1v5, 
olive-editor, src:openimageio, src:olive-editor, and src:blender
Added indication that 959596 affects 
src:olive-editor,src:blender,libopencolorio1v5,jami-daemon,blender,src:openimageio,olive-editor
Bug #960206 [libyaml-cpp0.6] olive-editor: does not start due to OpenColorIO 
error
Set Bug forwarded-to-address to 'https://github.com/jbeder/yaml-cpp/issues/789'.
Marked Bug as done
Added indication that 960206 affects 
src:olive-editor,src:blender,libopencolorio1v5,jami-daemon,blender,src:openimageio,olive-editor
Marked as fixed in versions yaml-cpp/0.6.3-7.
Marked as found in versions yaml-cpp/0.6.3-1 and yaml-cpp/0.6.3-4.
Added tag(s) confirmed, upstream, sid, ftbfs, and bullseye.
Bug #959556 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined 
reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
Bug #959586 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: 
undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
Bug #959596 {Done: Gianfranco Costamagna } 
[libyaml-cpp0.6] blender: FTBFS: subprocess.CalledProcessError: Command 
'['/<>/obj-x86_64-linux-gnu/bin/blender', '--help']' returned 
non-zero exit status 127.
Merged 959201 959556 959586 959596 959657 960206

-- 
959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201
959556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959556
959586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959586
959596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959596
959657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959657
960206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#960206: olive-editor: does not start due to OpenColorIO error

[Adrian Bunk]

Control: reassign -1 libyaml-cpp0.6
Control: forcemerge 959201 -1

On Fri, May 15, 2020 at 04:33:13PM +0200, bart...@fenski.pl wrote:
> On 2020-05-15 16:25, Adrian Bunk wrote:
> > On Sun, May 10, 2020 at 06:00:04PM +0200, Bartosz Fenski wrote:
> > > Package: olive-editor
> > > Version: 20200210-1
> > > Severity: grave
> > > 
> > > After fresh install olive doesn't start at all
> > > 
> > > fenio@udebian:~$ olive-editor
> > > Using Qt version: 5.12.5
> > > [OpenColorIO Info]: Color management disabled. (Specify the $OCIO
> > > environment variable to enable.)
> > > terminate called after throwing an instance of
> > > 'OpenColorIO::v1::Exception'
> > >   what():  Error: Loading the OCIO profile failed. The specified
> > > file does not appear to be an OCIO configuration.
> > > Aborted
> > > ...
> > 
> > Does it work after upgrading libyaml-cpp0.6 to 0.6.3-7?
> 
> Well now it works but I'm not the one to confirm that this upgrade fixed it.
> But it happened yesterday on my laptop so it could fix it ;)

Thanks, this is sufficient to confirm that it was this bug.

> regards
> Bartosz Fenski

cu
Adrian

Processed: fixed 960689 2.4.0-8

[Debian Bug Tracking System]

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

> tags 960689 + fixed pending
Bug #960689 [liblunar-date-dev] liblunar-date-dev: missing Breaks+Replaces: 
gir1.2-lunar-date-2.0 (<< 2.4.0-7)
Added tag(s) pending and fixed.
> fixed 960689 2.4.0-8
Bug #960689 [liblunar-date-dev] liblunar-date-dev: missing Breaks+Replaces: 
gir1.2-lunar-date-2.0 (<< 2.4.0-7)
There is no source info for the package 'liblunar-date-dev' at version 
'2.4.0-8' with architecture ''
Unable to make a source version for version '2.4.0-8'
Marked as fixed in versions 2.4.0-8.
> --
Stopping processing here.

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

Bug#960701: php-icinga: Uncaught ErrorException \Icinga\Web\ViewStream::stream_set_option is not implemented!

[Stephane Bortzmeyer]

Package: php-icinga
Version: 2.7.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

I had a working Icinga Web setup. nginx as a frontend, redirecting to
Icinga:

location ~ ^/icingaweb2/index\.php(.*)$ {
fastcgi_pass unix:/var/run/php/php-fpm.sock;
  fastcgi_index index.php;
include fastcgi_params;
  fastcgi_param SCRIPT_FILENAME /usr/share/icingaweb2/public/index.php;
fastcgi_param ICINGAWEB_CONFIGDIR /etc/icingaweb2;
  fastcgi_param REMOTE_USER $remote_user;
  }

location ~ ^/icingaweb2(.+)? {
  alias /usr/share/icingaweb2/public;
index index.php;
  try_files $1 $uri $uri/ /icingaweb2/index.php$is_args$args;
  }
}


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

I just upgraded my "sid" machine. Trying to access the Icinga Web page
of my installation no longer works.

   * What was the outcome of this action?

In the browser (Firefox), just this message:

Fatal error: Uncaught ErrorException: Uncaught ErrorException: include(): 
\Icinga\Web\ViewStream::stream_set_option is not implemented! in 
/usr/share/php/Icinga/Web/View.php:262 Stack trace: #0 
/usr/share/php/Icinga/Web/View.php(262): 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}() #1 
/usr/share/php/Icinga/Web/View.php(262): include() #2 
/usr/share/icingaweb2/library/vendor/Zend/View/Abstract.php(877): 
Icinga\Web\View->_run() #3 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/Helper/ViewRenderer.php(904):
 Zend_View_Abstract->render() #4 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/Helper/ViewRenderer.php(925):
 Zend_Controller_Action_Helper_ViewRenderer->renderScript() #5 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/Helper/ViewRenderer.php(964):
 Zend_Controller_Action_Helper_ViewRenderer->render() #6 
/usr/share/icingaweb2/library/vendor/Zend/Controller/Action/HelperBroker.php(272):
 Zend_Controller_Action_Helper_ViewRenderer->postDispatch() #7 /usr/share/icin 
in /usr/share/icingaweb2/library/vendor/Zend/Controller/Plugin/Broker.php on 
line 259

   * What outcome did you expect instead?

Ordinary Icinga Web page.


I also tried with the package in experimental,
php-icinga_2.8.0~rc1-1~exp2_all.deb. I got a different problem: the
CSS does not load and nginx logs:

2020/05/15 14:33:17 [error] 21559#21559: *65 FastCGI sent in stderr: "PHP 
message: PHP Fatal error:  Uncaught ErrorException: file_get_contents(): 
Filename cannot be empty in /usr/share/php/Icinga/Web/LessCompiler.php:172
Stack trace:
#0 [internal function]: 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}()
#1 /usr/share/php/Icinga/Web/LessCompiler.php(172): file_get_contents()
#2 /usr/share/php/Icinga/Web/StyleSheet.php(172): 
Icinga\Web\LessCompiler->render()
#3 /usr/share/php/Icinga/Web/StyleSheet.php(210): 
Icinga\Web\StyleSheet->render()
#4 /usr/share/php/Icinga/Application/webrouter.php(61): 
Icinga\Web\StyleSheet::send()
#5 /usr/share/icingaweb2/public/index.php(4): require_once('/usr/share/php/...')
#6 {main}
  thrown in /usr/share/php/Icinga/Web/LessCompiler.php on line 172" while 
reading response header from upstream, client: 192.168.2.1, server: _, request: 
"GET /icingaweb2/css/icinga.min.css HTTP/2.0", upstream: 
"fastcgi://unix:/var/run/php/php-fpm.sock:", host: "icinga2.nic.example", 
referrer: "https://icinga2.nic.example/icingaweb2/dashboard";
2020/05/15 14:33:17 [error] 21559#21559: *65 FastCGI sent in stderr: "PHP 
message: PHP Fatal error:  Uncaught ErrorException: 
file_get_contents(/usr/share/icingaweb2/public/js/icinga/behavior/modal.js): 
failed to open stream: No such file or directory in 
/usr/share/php/Icinga/Web/JavaScript.php:126
Stack trace:
#0 [internal function]: 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}()
#1 /usr/share/php/Icinga/Web/JavaScript.php(126): file_get_contents()
#2 /usr/share/php/Icinga/Web/JavaScript.php(50): Icinga\Web\JavaScript::send()
#3 /usr/share/php/Icinga/Application/webrouter.php(69): 
Icinga\Web\JavaScript::sendMinified()
#4 /usr/share/icingaweb2/public/index.php(4): require_once('/usr/share/php/...')
#5 {main}
  thrown in /usr/share/php/Icinga/Web/JavaScript.php on line 126" while reading 
response header from upstream, client: 192.168.2.1, server: _, request: "GET 
/icingaweb2/js/icinga.min.js HTTP/2.0", upstream: 
"fastcgi://unix:/var/run/php/php-fpm.sock:", host: "icinga2.nic.example", 
referrer: "https://icinga2.nic.example/icingaweb2/dashboard";


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.4.199-a890a5a94ebb621f8f1720c24d12fef1-0 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages 

Processed: Re: Bug#960689: liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 2.4.0-7)

[Debian Bug Tracking System]

Processing control commands:

> fixed 960689 lunar-date/2.4.0-8
Bug #960689 [liblunar-date-dev] liblunar-date-dev: missing Breaks+Replaces: 
gir1.2-lunar-date-2.0 (<< 2.4.0-7)
The source lunar-date and version 2.4.0-8 do not appear to match any binary 
packages
Marked as fixed in versions lunar-date/2.4.0-8; no longer marked as fixed in 
versions lunar-date/2.4.0-8.

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

Processed: Re: Bug#960689: liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 2.4.0-7)

[Debian Bug Tracking System]

Processing control commands:

> fixed 960689 lunar-date/2.4.0-8
Bug #960689 [liblunar-date-dev] liblunar-date-dev: missing Breaks+Replaces: 
gir1.2-lunar-date-2.0 (<< 2.4.0-7)
The source lunar-date and version 2.4.0-8 do not appear to match any binary 
packages
Marked as fixed in versions lunar-date/2.4.0-8.

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

Bug#960689: liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 2.4.0-7)

[atzlinux 肖盛文]

control: fixed 960689 lunar-date/2.4.0-8

control: tags 960689 + fixed pending


Thanks for report this bug.


It's this change import this bug:

  * fix lintian: gir-section-not-libdevel
    move LunarDate-2.0.gir from gir1.2-lunar-date-2.0 to liblunar-date-dev

I'd uploaded the new verison to mentors.

https://mentors.debian.net/package/lunar-date


在 2020/5/15 下午8:33, Andreas Beckmann 写道:

> Package: liblunar-date-dev
> Version: 2.4.0-7
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>
> From the attached log (scroll to the bottom...):
>
>   Preparing to unpack .../liblunar-date-dev_2.4.0-7_amd64.deb ...
>   Unpacking liblunar-date-dev:amd64 (2.4.0-7) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb (--unpack):
>trying to overwrite '/usr/share/gir-1.0/LunarDate-2.0.gir', which is also 
> in package gir1.2-lunar-date-2.0 2.4.0-5
>   Errors were encountered while processing:
>/var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb
>
>
> cheers,
>
> Andreas

-- 
肖盛文 Faris Xiao
微信：atzlinux
ＱＱ：909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统：https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature

Bug#960206: olive-editor: does not start due to OpenColorIO error

[Adrian Bunk]

On Sun, May 10, 2020 at 06:00:04PM +0200, Bartosz Fenski wrote:
> Package: olive-editor
> Version: 20200210-1
> Severity: grave
> 
> After fresh install olive doesn't start at all
> 
> fenio@udebian:~$ olive-editor
> Using Qt version: 5.12.5
> [OpenColorIO Info]: Color management disabled. (Specify the $OCIO environment 
> variable to enable.)
> terminate called after throwing an instance of 'OpenColorIO::v1::Exception'
>   what():  Error: Loading the OCIO profile failed. The specified file does 
> not appear to be an OCIO configuration.
> Aborted
>...

Does it work after upgrading libyaml-cpp0.6 to 0.6.3-7?

cu
Adrian

Processed: tagging 936557

[Debian Bug Tracking System]

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

> tags 936557 + upstream
Bug #936557 [src:freeorion] freeorion: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#958408: etherape: crashes with "critical: read_all() failed on control socket"

[Patrick Matthäi]

Hi,

Am 28.04.2020 um 00:08 schrieb Bernhard Übelacker:
> Dear Maintainer,
> I could reproduce the issue on i386 and tried to collect
> some more information.
>
> It crashes with the backtrace below.
>
> The crash seems to be caused by using the wrong data type
> in the calls to variadic functions goo_canvas_ellipse_new
> and goo_canvas_polyline_new.
>
> The modifications below made it work at i386 too.
> (Just changing integer to floating point values).
> Tested it just shortly.
>
>
>
> (gdb) bt
> #0  __strchr_sse2_bsf () at 
> ../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S:60
> #1  0xb73243ce in g_param_spec_pool_lookup (pool=0x136e260, param_name=0x1 
> , owner_type=26014064, 
> walk_ancestors=1) at ../../../gobject/gparam.c:1071
> #2  0xb731fbce in g_object_set_valist (object=, 
> first_property_name=, var_args=0xbfb6a0b4 "") at 
> ../../../gobject/gobject.c:2289
> #3  0xb7f6e4be in goo_canvas_ellipse_new (parent=0x1685848, center_x=0, 
> center_y=0, radius_x=0, radius_y=0) at goocanvasellipse.c:214
> #4  0x0044feea in check_new_node (canvas=0x1650380, node=0x14b1600) at 
> diagram.c:935
> #5  diagram_update_nodes (canvas=0x1650380) at diagram.c:541
> #6  update_diagram (canvas=0x1650380) at diagram.c:735
> #7  0x00450828 in update_diagram_callback (data=0x0) at diagram.c:1910
> #8  0xb7076a51 in g_timeout_dispatch (source=0x14793c0, callback=0x450810 
> , user_data=0x0) at ../../../glib/gmain.c:4667
> #9  0xb7075e65 in g_main_dispatch (context=0x13b1fd0) at 
> ../../../glib/gmain.c:3182
> #10 g_main_context_dispatch (context=0x13b1fd0) at ../../../glib/gmain.c:3847
> #11 0xb7076269 in g_main_context_iterate (context=0x13b1fd0, 
> block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
> ../../../glib/gmain.c:3920
> #12 0xb7076609 in g_main_loop_run (loop=0x1478ea0) at 
> ../../../glib/gmain.c:4116
> #13 0xb799139e in gtk_main () at ../../../../gtk/gtkmain.c:1323
> #14 0x0044049e in main (argc=, argv=) at 
> main.c:316
>
>
>
>
>
> --- etherape-0.9.18.orig/src/diagram.c
> +++ etherape-0.9.18/src/diagram.c
> @@ -939,7 +939,7 @@ static gint check_new_node(node_t * node
>  0.0,
>  "fill-color", "white",
>  "stroke-color", "black",
> -"line-width", 0,
> +"line-width", 0.0,
>   "visibility", GOO_CANVAS_ITEM_INVISIBLE,
>   NULL);
>addref_canvas_obj(G_OBJECT(new_canvas_node->node_item));
> @@ -1480,16 +1480,16 @@ static gint check_new_link(link_id_t * l
>/* set the lines position using groups positions */
>new_canvas_link->src_item =
>  goo_canvas_polyline_new(rootgroup, TRUE, 2,
> -0,0,
> -1,1,
> +0.0,0.0,
> +1.0,1.0,
>  "fill-color", "tan",
>  NULL);
>g_object_ref(G_OBJECT (new_canvas_link->src_item));
>  
>new_canvas_link->dst_item =
>  goo_canvas_polyline_new(rootgroup, TRUE, 2,
> -0,0,
> -1,1,
> +0.0,0.0,
> +1.0,1.0,
>  "fill-color", "tan",
>  NULL);
>g_object_ref(G_OBJECT (new_canvas_link->dst_item));
>
>
>
>
>
>
>
> PS.: Could not install etherape on a multiarch amd64/i386 system because
>  it tells it depends on non-existing etherape-data:i386.

Thanks for your patch. I have tested it on my amd64 machine, where I
didn't had problems. Anyway it also builds fine with your patch and I
have uploaded it.

@rghetta:
Do you want to merge it?

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: https://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

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

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/KhronosGroup/SPIRV-Tools/issues/3214
Bug #956510 [spirv-tools] spirv-tools: change to shared libraries breaks 
dpkg-shlibdeps during the build of reverse dependencies
Set Bug forwarded-to-address to 
'https://github.com/KhronosGroup/SPIRV-Tools/issues/3214'.

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

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

[Simon McVittie]

Control: forwarded -1 https://github.com/KhronosGroup/SPIRV-Tools/issues/3214

On Fri, 15 May 2020 at 10:16:33 +0200, Sebastian Ramacher wrote:
> On 2020-05-14 17:18:38 +0100, Simon McVittie wrote:
> > Are these libraries intended to be a public API, or are they intended to be
> > a private implementation detail of the CLI tools?
> 
> They are intended to be public.

In that case I think the necessary steps are:

- wait for upstream to set an official SONAME
  - someone from Collabora can propose a PR if upstream say it would be
helpful, or if that seems to be necessary to unblock the upstream issue

- change the Debian package to be built like a Policy §8 shared library:
  - libspirv-tools-dev
  - libspirv-tools0
  - possibly also libspirv-tools-link0, etc., depending whether upstream
say the SONAMEs are meant to go up in lockstep or separately
(the safe/conservative option is one binary package per shared library)
  - again, someone from Collabora can propose patches for this if necessary
  - the upstream action needs to happen first, to avoid Debian producing an
ABI that is incompatible with upstream

- NEW queue processing

Thanks,
smcv

Bug#960689: liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 2.4.0-7)

[Andreas Beckmann]

Package: liblunar-date-dev
Version: 2.4.0-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../liblunar-date-dev_2.4.0-7_amd64.deb ...
  Unpacking liblunar-date-dev:amd64 (2.4.0-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gir-1.0/LunarDate-2.0.gir', which is also in 
package gir1.2-lunar-date-2.0 2.4.0-5
  Errors were encountered while processing:
   /var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb


cheers,

Andreas


gir1.2-lunar-date-2.0=2.4.0-5_liblunar-date-dev=2.4.0-7.log.gz
Description: application/gzip

Bug#960688: fwupd: missing Breaks: fwupdate (<< 12-7)

[Andreas Beckmann]

Package: fwupd
Version: 1.3.9-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 fwupdate/stable
  # (1)
  apt-get install fwupd
  apt-get remove fwupd
  # (2)

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

  /usr/bin/fwupdate
  /usr/share/man/man1/fwupdate.1.gz
  /var/lib/fwupdate/

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 fwupd package has the following relationships with fwupdate:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  fwupdate (<< 12-7)
  Provides:  fwupdate

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

0m32.0s ERROR: FAIL: After purging files have disappeared:
  /usr/bin/fwupdate  owned by: fwupd
  /usr/share/man/man1/fwupdate.1.gz  owned by: fwupd
  /var/lib/fwupdate/ owned by: fwupdate

0m32.0s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/fwupdate.list   not owned


cheers,

Andreas


fwupdate=12-4_fwupd=1.3.9-4.log.gz
Description: application/gzip

Bug#937400: pycaml: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Sun, Apr 05, 2020 at 09:35:14AM +0200, Stéphane Glondu wrote:
> Le 04/04/2020 à 20:21, Moritz Mühlenhoff a écrit :
> >>> pycaml is deprecated in favour of pyml (in NEW). The only reverse
> >>> dependency, coccinelle, is supposed to switch to pyml. Once it's done,
> >>> we can remove pycaml.
> >>
> >> pyml is now in testing.
> >>
> >> Emmanuel Arias (in CC) has shown interest in adopting coccinelle (#886679).
> >>
> >> Emmanuel, what is the status of packaging a new version of coccinelle?
> > 
> > A new version of coccinelle has been uploaded, so let's remove pycaml now?
> 
> I see no objection.

I've just filed an RM bug.

Cheers,
Moritz

Bug#960680: ruby-actionpack-page-caching: CVE-2020-8159

[Salvatore Bonaccorso]

Source: ruby-actionpack-page-caching
Version: 1.1.0-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for ruby-actionpack-page-caching.

CVE-2020-8159[0]:
| There is a vulnerability in actionpack_page-caching gem < v1.2.1
| that allows an attacker to write arbitrary files to a web server,
| potentially resulting in remote code execution if the attacker can
| write unescaped ERB to a view.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-8159
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8159
[1] https://groups.google.com/forum/#!topic/rubyonrails-security/CFRVkEytdP8

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 11:18:27 +
with message-id 
and subject line Bug#960598: fixed in fontconfig 2.13.1-4.2
has caused the Debian Bug report #960598,
regarding libfontconfig-doc: missing Breaks: libfontconfig1-dev (<< 2.13.1-3)
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.)


-- 
960598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.1-4.2
Done: Julien Cristau 

We believe that the bug you reported is fixed in the latest version of
fontconfig, 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.
Julien Cristau  (supplier of updated fontconfig 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 12:55:02 +0200
Source: fontconfig
Architecture: source
Version: 2.13.1-4.2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Julien Cristau 
Closes: 960598
Changes:
 fontconfig (2.13.1-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Hopefully this otherwise dummy upload lets us work around bug #960679.
   * Add missing Breaks for the -doc package split (closes: #960598)
Checksums-Sha1:
 1abbc74107a24d5c7fd7b6ea56740abaefd8fb0d 2716 fontconfig_2.13.1-4.2.dsc
 48f32f66d2523a7bb13b46e1c25c27e60355bd3e 55124 
fontconfig_2.13.1-4.2.debian.tar.xz
Checksums-Sha256:
 d22e6441f0aa03b569d886fbb3227330dd2305e7aa10513e177ced28b8b52d63 2716 
fontconfig_2.13.1-4.2.dsc
 f1ec69a2a0affd86189d3b75ced77b30bbcbc3a6fc0508490e570d4786464b58 55124 
fontconfig_2.13.1-4.2.debian.tar.xz
Files:
 8d35a492f7ebcfdb4374d6b49e90b61

Bug#960653: marked as done (/usr/lib/python3.7/tkinter/__pycache__/ not deleted)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 11:18:36 +
with message-id 
and subject line Bug#960653: fixed in python3-stdlib-extensions 3.8.3-2
has caused the Debian Bug report #960653,
regarding /usr/lib/python3.7/tkinter/__pycache__/ not deleted
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.)


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

Hello,

When updating today, dpkg complained about the /usr/lib/python3.7
directory not being empty:

Dépaquetage de python3-distutils (3.8.3-1) sur (3.8.2-2) ...
dpkg: avertissement: impossible de supprimer l'ancien répertoire  « 
/usr/lib/python3.7 » : Le dossier n'est pas vide

Looking at the context of /usr/lib/python3.7 I found that there was
still /usr/lib/python3.7/tkinter/__pycache__/ containing .pyc files in
it.

The .pyc and the pycache directory should be deleted when python3-tk was
moved from 3.7 to 3.8.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages python3-tk depends on:
ii  blt   2.5.3+dfsg-4+b1
ii  libc6 2.30-8
ii  libtcl8.6 8.6.10+dfsg-1
ii  libtk8.6  8.6.10-1
ii  python3   3.8.2-3
ii  tk8.6-blt2.5  2.5.3+dfsg-4+b1

python3-tk recommends no packages.

Versions of packages python3-tk suggests:
pn  python3-tk-dbg  
ii  tix 8.4.3-10+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python3-stdlib-extensions
Source-Version: 3.8.3-2
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python3-stdlib-extensions, 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.
Matthias Klose  (supplier of updated python3-stdlib-extensions 
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: Fri, 15 May 2020 12:55:52 +0200
Source: python3-stdlib-extensions
Architecture: source
Version: 3.8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 960653
Changes:
 python3-stdlib-extensions (3.8.3-2) unstable; urgency=medium
 .
   * Remove bytecode files for 3.7 on upgrade. Closes: #960653.
   * Bump debhelper version.
Checksums-Sha1:
 d046870b7ab5e6d6cc9c6ee8edaa514f4457fde9 2450 
python3-stdlib-extensions_3.8.3-2.dsc
 f17c009b2e42a7e63cd4c3cc8362f1985150f578 17384 
python3-stdlib-extensions_3.8.3-2.debian.tar.xz
 29ba0ab962ef85300f429258a08820ac0e1d2718 7726 
python3-stdlib-extensions_3.8.3-2_source.buildinfo
Checksums-Sha256:
 86bc8a0c0514d2394f1b366d8577ba2e5d28677c08999213a6943f07dc0182a8 2450 
python3-stdlib-extensions_3.8.3-2.dsc
 680b5637a7afc45ffa63e6b3a419d4029bb8e3f311529eeb94287e24a0db40c2 17384 
python3-stdlib-extensions_3.8.3-2.debian.tar.xz
 4818261c7208cefd1acae24da795b4bfc523c7c38a313bec4a60d6aba21a48d5 7726 
python3-stdlib-extensions_3.8.3-2_source.buildinfo
Files:
 c233a39d97144d88206b1ec8e5ac13e6 2450 python optional 
python3-stdlib-extensions_3.8.3-2.dsc
 a4b6d1aa6fe3f29a8b45972ebb71a64d 17384 python optional 
python3-stdlib-extensions_3.8.3-2.debian.tar.xz
 80cee2151e862afa1e8bbe68e756f659 7726 python optional 
python3-stdlib-extensions_3.8.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl6+d8kQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9Xl3D/42yCMSbobsJ0tpOWp63N9HLCZ6x3dpl80L
5HRL2WCRCFWYPg1nHAJdPHiLrf7+GamUFiwdLNxcmUEwFKTP0ihX88S1CPwTlhda
rcdbdfZG+koG3SWQGPFMxLti0P5L83p8P+aT/Z2EKfjR3OuJhKHNl6lzBM+WhMGg
+BXN1CXenN/AYqyp2zxrN9LgmvgZU8W/2

Bug#960598: fontconfig: diff for NMU version 2.13.1-4.2

[Julien Cristau]

Control: tags 960598 + patch
Control: tags 960598 + pending

Dear maintainer,

I've prepared an NMU for fontconfig (versioned as 2.13.1-4.2) and
uploaded it to DELAYED/0.  (The -4.1 NMU ran into bug #960679 so I need
to do a new upload anyway, figured I'd fix this while at it.)

Also at
https://salsa.debian.org/freedesktop-team/fontconfig/-/merge_requests/7

Cheers,
Julien
diff -Nru fontconfig-2.13.1/debian/changelog fontconfig-2.13.1/debian/changelog
--- fontconfig-2.13.1/debian/changelog	2020-05-13 12:21:13.0 +0200
+++ fontconfig-2.13.1/debian/changelog	2020-05-15 12:55:02.0 +0200
@@ -1,3 +1,11 @@
+fontconfig (2.13.1-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Hopefully this otherwise dummy upload lets us work around bug #960679.
+  * Add missing Breaks for the -doc package split (closes: #960598)
+
+ -- Julien Cristau   Fri, 15 May 2020 12:55:02 +0200
+
 fontconfig (2.13.1-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fontconfig-2.13.1/debian/control fontconfig-2.13.1/debian/control
--- fontconfig-2.13.1/debian/control	2020-05-13 12:15:26.0 +0200
+++ fontconfig-2.13.1/debian/control	2020-05-15 12:55:02.0 +0200
@@ -134,6 +134,7 @@
 Build-Profiles: 
 Depends: ${misc:Depends}
 Replaces: libfontconfig1-dev (<< 2.13.1-3)
+Breaks: libfontconfig1-dev (<< 2.13.1-3)
 Description: generic font configuration library - documentation
  Fontconfig is a font configuration and customization library, which
  does not depend on the X Window System. It is designed to locate

Processed: fontconfig: diff for NMU version 2.13.1-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 960598 + patch
Bug #960598 [libfontconfig-doc] libfontconfig-doc: missing Breaks: 
libfontconfig1-dev (<< 2.13.1-3)
Added tag(s) patch.
> tags 960598 + pending
Bug #960598 [libfontconfig-doc] libfontconfig-doc: missing Breaks: 
libfontconfig1-dev (<< 2.13.1-3)
Added tag(s) pending.

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

Bug#960679: fontconfig: strict dependency of arch:any libfontconfig1 on arch:all fontconfig-config going wrong

[Julien Cristau]

Source: fontconfig
Version: 2.13.1-2
Severity: serious

libfontconfig1 Depends on fontconfig-config (>= ${source:Version})

If the arch:amd64 buildd is faster than the arch:all one, as happened
with 2.13.1-4.1, the new libfontconfig1 becomes uninstallable, and,
because fontconfig indirectly build-depends on libfontconfig1, that
situation can't fix itself.

One way around that is to make fontconfig-config arch:any; there may be
other solutions.

Cheers,
Julien

Processed: plume-creator: diff for NMU version 0.66+dfsg1-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 887534 + patch
Bug #887534 [src:plume-creator] plume-creator FTBFS with libquazip5-headers 
0.7.3-3
Ignoring request to alter tags of bug #887534 to the same tags previously set
> tags 887534 + pending
Bug #887534 [src:plume-creator] plume-creator FTBFS with libquazip5-headers 
0.7.3-3
Ignoring request to alter tags of bug #887534 to the same tags previously set
> tags 889273 + patch
Bug #889273 [plume-creator-dbg] plume-creator-dbg is empty
Ignoring request to alter tags of bug #889273 to the same tags previously set
> tags 889273 + pending
Bug #889273 [plume-creator-dbg] plume-creator-dbg is empty
Ignoring request to alter tags of bug #889273 to the same tags previously set

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

Bug#887534: plume-creator: diff for NMU version 0.66+dfsg1-3.2

[Sudip Mukherjee]

Control: tags 887534 + patch
Control: tags 887534 + pending
Control: tags 889273 + patch
Control: tags 889273 + pending

Dear maintainer,

I've prepared an NMU for plume-creator (versioned as 0.66+dfsg1-3.2) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru plume-creator-0.66+dfsg1/debian/changelog 
plume-creator-0.66+dfsg1/debian/changelog
--- plume-creator-0.66+dfsg1/debian/changelog   2016-01-13 20:53:03.0 
+
+++ plume-creator-0.66+dfsg1/debian/changelog   2020-05-15 11:05:14.0 
+0100
@@ -1,3 +1,11 @@
+plume-creator (0.66+dfsg1-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. (Closes: #887534)
+  * Add debug symbols. (Closes: #889273)
+
+ -- Sudip Mukherjee   Fri, 15 May 2020 11:05:14 
+0100
+
 plume-creator (0.66+dfsg1-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru plume-creator-0.66+dfsg1/debian/patches/fix_ftbfs.patch 
plume-creator-0.66+dfsg1/debian/patches/fix_ftbfs.patch
--- plume-creator-0.66+dfsg1/debian/patches/fix_ftbfs.patch 1970-01-01 
01:00:00.0 +0100
+++ plume-creator-0.66+dfsg1/debian/patches/fix_ftbfs.patch 2020-04-24 
21:01:58.0 +0100
@@ -0,0 +1,16 @@
+Description: Fix FTBFS
+ Include the file as done by upstream.
+
+ Origin: 
https://github.com/jacquetc/plume-creator-legacy/blob/develop/src/newProjectWizard/selectpage.cpp#L3
+
+---
+
+--- plume-creator-0.66+dfsg1.orig/src/newProjectWizard/selectpage.cpp
 plume-creator-0.66+dfsg1/src/newProjectWizard/selectpage.cpp
+@@ -1,5 +1,6 @@
+ #include "selectpage.h"
+ #include "ui_selectpage.h"
++#include 
+ 
+ SelectPage::SelectPage(QWidget *parent) :
+ QWizardPage(parent),
diff -Nru plume-creator-0.66+dfsg1/debian/patches/series 
plume-creator-0.66+dfsg1/debian/patches/series
--- plume-creator-0.66+dfsg1/debian/patches/series  2016-01-13 
20:53:03.0 +
+++ plume-creator-0.66+dfsg1/debian/patches/series  2020-05-15 
10:11:10.0 +0100
@@ -3,5 +3,5 @@
 remove-SlimUpdater.patch
 translations-es.patch
 built-in-Qt5.patch
-
 desktop.patch
+fix_ftbfs.patch
diff -Nru plume-creator-0.66+dfsg1/debian/rules 
plume-creator-0.66+dfsg1/debian/rules
--- plume-creator-0.66+dfsg1/debian/rules   2016-01-13 20:53:03.0 
+
+++ plume-creator-0.66+dfsg1/debian/rules   2020-05-15 11:04:55.0 
+0100
@@ -16,7 +16,7 @@
CFLAGS="$(CFLAGS) $(CPPFLAGS)" \
CXXFLAGS="$(CXXFLAGS) $(CPPFLAGS)" \
LFLAGS="$(LDFLAGS) $(LDFLAGS2)" \
-   qmake -makefile plume-creator.pro
+   qmake -makefile "CONFIG+=debug" plume-creator.pro
touch $@
 
 build-stamp: config

Processed: plume-creator: diff for NMU version 0.66+dfsg1-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 887534 + patch
Bug #887534 [src:plume-creator] plume-creator FTBFS with libquazip5-headers 
0.7.3-3
Added tag(s) patch.
> tags 887534 + pending
Bug #887534 [src:plume-creator] plume-creator FTBFS with libquazip5-headers 
0.7.3-3
Added tag(s) pending.
> tags 889273 + patch
Bug #889273 [plume-creator-dbg] plume-creator-dbg is empty
Added tag(s) patch.
> tags 889273 + pending
Bug #889273 [plume-creator-dbg] plume-creator-dbg is empty
Added tag(s) pending.

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

Processed: forcibly merging 960660 960658

[Debian Bug Tracking System]

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

> forcemerge 960660 960658
Bug #960660 [src:cyrus-imapd] cyrus-imapd: Test failure on armhf (at least on 
armv8)
Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch
Unset Bug forwarded-to-address
Unset Bug forwarded-to-address
Bug #960660 [src:cyrus-imapd] cyrus-imapd: Test failure on armhf (at least on 
armv8)
Marked as found in versions cyrus-imapd/3.2.0-3.
Bug #960659 [src:cyrus-imapd] cyrus-imapd: Test failure on big endian
Merged 960658 960659 960660
> thanks
Stopping processing here.

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

Processed: xf86-video-omap: diff for NMU version 0.4.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 956886 + patch
Bug #956886 [src:xf86-video-omap] xf86-video-omap FTBFS with gcc 9
Added tag(s) patch.
> tags 956886 + pending
Bug #956886 [src:xf86-video-omap] xf86-video-omap FTBFS with gcc 9
Added tag(s) pending.

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

Bug#956886: xf86-video-omap: diff for NMU version 0.4.5-1.1

[Adrian Bunk]

Control: tags 956886 + patch
Control: tags 956886 + pending

Dear maintainer,

I've prepared an NMU for xf86-video-omap (versioned as 0.4.5-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru xf86-video-omap-0.4.5/debian/changelog xf86-video-omap-0.4.5/debian/changelog
--- xf86-video-omap-0.4.5/debian/changelog	2016-11-24 23:59:22.0 +0200
+++ xf86-video-omap-0.4.5/debian/changelog	2020-05-15 13:24:48.0 +0300
@@ -1,3 +1,10 @@
+xf86-video-omap (0.4.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix a NULL dereference found by gcc 9. (Closes: #956886)
+
+ -- Adrian Bunk   Fri, 15 May 2020 13:24:48 +0300
+
 xf86-video-omap (0.4.5-1) unstable; urgency=medium
 
   * New upstream release (Closes: #845331)
diff -Nru xf86-video-omap-0.4.5/debian/patches/null-dereference.patch xf86-video-omap-0.4.5/debian/patches/null-dereference.patch
--- xf86-video-omap-0.4.5/debian/patches/null-dereference.patch	1970-01-01 02:00:00.0 +0200
+++ xf86-video-omap-0.4.5/debian/patches/null-dereference.patch	2020-05-15 13:24:48.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix a NULL dereference found by gcc 9
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/956886
+
+--- xf86-video-omap-0.4.5.orig/src/omap_driver.c
 xf86-video-omap-0.4.5/src/omap_driver.c
+@@ -542,7 +542,7 @@ OMAPPreInit(ScrnInfoPtr pScrn, int flags
+ 	}
+ 
+ 	if (!pScrn->chipset) {
+-		ERROR_MSG("Unknown chipset: %s", pScrn->chipset);
++		ERROR_MSG("Unknown chipset");
+ 		goto fail;
+ 	}
+ 
diff -Nru xf86-video-omap-0.4.5/debian/patches/series xf86-video-omap-0.4.5/debian/patches/series
--- xf86-video-omap-0.4.5/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ xf86-video-omap-0.4.5/debian/patches/series	2020-05-15 13:24:35.0 +0300
@@ -0,0 +1 @@
+null-dereference.patch

Processed: Move where the bug was

[Debian Bug Tracking System]

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

> reassign 949991 src:haskell-hledger-lib 1.14.1-1
Bug #949991 {Done: Gianfranco Costamagna } 
[src:haskell-hledger] haskell-hledger ftbfs on s390x
Bug reassigned from package 'src:haskell-hledger' to 'src:haskell-hledger-lib'.
No longer marked as found in versions haskell-hledger/1.14.2-1.
No longer marked as fixed in versions haskell-hledger-lib/1.14.1-2.
Bug #949991 {Done: Gianfranco Costamagna } 
[src:haskell-hledger-lib] haskell-hledger ftbfs on s390x
Marked as found in versions haskell-hledger-lib/1.14.1-1.
> fixed 949991 1.14.1-2
Bug #949991 {Done: Gianfranco Costamagna } 
[src:haskell-hledger-lib] haskell-hledger ftbfs on s390x
Marked as fixed in versions haskell-hledger-lib/1.14.1-2.
> thanks
Stopping processing here.

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

Bug#960662: spyne: unsatisfiable dependency on pyparsing

[Bastian Germann]

The same goes for python-pyparsing which is another non-existent dependency.

Bug#959587: marked as done (python-biopython: FTBFS: AssertionError: False is not true)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 10:18:48 +
with message-id 
and subject line Bug#959587: fixed in python-biopython 1.76+dfsg-2
has caused the Debian Bug report #959587,
regarding python-biopython: FTBFS: AssertionError: False is not true
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.)


-- 
959587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biopython
Version: 1.76+dfsg-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 '/<>'
> mkdir -p Tests_avoid
> for avoid in  PAML_tools EmbossPhylipNew MSAProbs_tool NACCESS_tool 
> PopGen_GenePop PopGen_GenePop_EasyController XXmotif_tool PDB_ResidueDepth 
> mmtf mmtf_online  BioSQL_MySQLdb BioSQL_psycopg2   \
>   ; do \
> mv Tests/test_${avoid}.py Tests_avoid ; \
> done
> # For the doc package we need a clean testsuite without all the remaining 
> files.  So keep a clean copy here
> mkdir -p debian/tmp_tests
> cp -a Tests debian/tmp_tests
> # remove duplicated file
> rm -f debian/tmp_tests/Tests/Quality/example.fastq.gz
> # We also keep the tests we need to avoid for later inspection
> cp -a Tests_avoid debian/tmp_tests
> # in the Debian package dialign it is not needed to set DIALIGN2_DIR but the 
> test is verifying this dir
> # to run the EMBOSS test test_Emboss also requires to have the environment 
> variable EMBOSS_ROOT set
> LC_ALL=C.UTF-8 dh_auto_test -- --test --system=custom \
>   --test-args='set -e; \
>  mkdir -p {build_dir}/home; \
>  mkdir -p {build_dir}/Doc/examples; \
>  cp -a Doc/Tutorial.tex {build_dir}/Doc; \
>  cp -a Doc/Tutorial {build_dir}/Doc; \
>  cp -a Doc/examples {build_dir}/Doc; \
>  cp -a Tests {build_dir}; \
>  cd {build_dir}/Tests; \
>  env DIALIGN2_DIR=/usr/share/dialign 
> EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py 
> --offline'
>   pybuild --test -i python{version} -p 3.8 --test --system=custom 
> "--test-args=set -e; \\\
>  mkdir -p {build_dir}/home; \\\
>  mkdir -p {build_dir}/Doc/examples; \\\
>  cp -a Doc/Tutorial.tex {build_dir}/Doc; \\\
>  cp -a Doc/Tutorial {build_dir}/Doc; \\\
>  cp -a Doc/examples {build_dir}/Doc; \\\
>  cp -a Tests {build_dir}; \\\
>  cd {build_dir}/Tests; \\\
>  env DIALIGN2_DIR=/usr/share/dialign 
> EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter} run_tests.py 
> --offline"
> I: pybuild base:217: set -e; \
>  mkdir -p 
> /<>/.pybuild/cpython3_3.8/build/home; \
>  mkdir -p 
> /<>/.pybuild/cpython3_3.8/build/Doc/examples; \
>  cp -a Doc/Tutorial.tex 
> /<>/.pybuild/cpython3_3.8/build/Doc; \
>  cp -a Doc/Tutorial 
> /<>/.pybuild/cpython3_3.8/build/Doc; \
>  cp -a Doc/examples 
> /<>/.pybuild/cpython3_3.8/build/Doc; \
>  cp -a Tests 
> /<>/.pybuild/cpython3_3.8/build; \
>  cd 
> /<>/.pybuild/cpython3_3.8/build/Tests; \
>  env DIALIGN2_DIR=/usr/share/dialign 
> EMBOSS_ROOT=/usr/lib/emboss 
> HOME=/<>/.pybuild/cpython3_3.8/build/home python3.8 run_tests.py 
> --offline
> x_order_2: colinear!
> x_order_2: colinear!
> test_Ace ... ok
> test_Affy ... ok
> test_AlignIO ... ok
> test_AlignIO_ClustalIO ... ok
> test_AlignIO_EmbossIO ... ok
> test_AlignIO_FastaIO ... ok
> test_AlignIO_MauveIO ... ok
> test_AlignIO_PhylipIO ... ok
> test_AlignIO_convert ... ok
> test_AlignInfo ... ok
> test_Application ... ok
> test_BWA_tool ... ok
> test_BioSQL_MySQLdb_online ... skipping. internet not available
> test_BioSQL_mysql_connector ... skipping. BioSQL test configuration file 
> biosql.ini missing (see biosql.ini.sample)
> test_BioSQL_mysql_connector_online ... skipping. internet not available
> test_BioSQL_psycopg2_online ... skipping. internet not available
> test_BioSQL_sqlite3 ... ok
> test_Bi

Bug#958408: marked as done (etherape: crashes with "critical: read_all() failed on control socket")

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 10:18:31 +
with message-id 
and subject line Bug#958408: fixed in etherape 0.9.18-3
has caused the Debian Bug report #958408,
regarding etherape: crashes with "critical: read_all() failed on control socket"
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.)


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

Dear Maintainer,

starting etherape with 'sudo /usr/bin/etherape -n -i wlp2s0', I get:

EtherApe-INFO: 17:31:05.960: Protokoll sctp nicht unterstützt
EtherApe-INFO: 17:31:05.961: Protokoll ddp nicht unterstützt
EtherApe-INFO: 17:31:05.961: Protokoll ddp nicht unterstützt
EtherApe-INFO: 17:31:05.962: Protokoll ddp nicht unterstützt
EtherApe-INFO: 17:31:05.962: Protokoll ddp nicht unterstützt
EtherApe-INFO: 17:31:06.255: Ergebnis von get_interface: »«
EtherApe-INFO: 17:31:06.261: Verfügbare Schnittstellen für die Erfassung: 
usbmon5 usbmon4 usbmon3 usbmon2 usbmon1 nfqueue nflog lo any wlp2s0 enp1s0
EtherApe-INFO: 17:31:06.294: Verweistyp ist Ethernet
EtherApe-INFO: 17:31:06.296: Diagramm gestartet
EtherApe-INFO: 17:31:09.865: Neuer Knoten: IP: 10.0.1.4. Anzahl der Knoten 1
EtherApe-INFO: 17:31:09.866: Neuer Knoten: IP: 51.15.185.201. Anzahl der Knoten 
2
unexpected EOF in read_all()
critical: read_all() failed on control socket
Speicherzugriffsfehler

/var/log/syslog shows:

Apr 21 17:31:06 debian kernel: [38534.252175] device wlp2s0 entered promiscuous 
mode
Apr 21 17:31:06 debian dbus-daemon[378]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.80' (uid=0 
pid=27621 comm="/usr/bin/etherape -n -i wlp2s0 ")
Apr 21 17:31:06 debian systemd[1]: Starting Hostname Service...
Apr 21 17:31:06 debian dbus-daemon[378]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Apr 21 17:31:06 debian systemd[1]: Started Hostname Service.
Apr 21 17:31:10 debian kernel: [38538.022726] etherape[27621]: segfault at 0 ip 
b6de3756 sp bfc87d18 error 4 in libc-2.28.so[b6ca1000+14e000]
Apr 21 17:31:10 debian kernel: [38538.022758] Code: 66 90 66 90 57 8b 4c 24 08 
66 0f 6e 4c 24 0c 66 0f ef d2 89 cf 66 0f 60 c9 66 0f 60 c9 83 e1 0f 66 0f 70 
c9 00 74 4d 83 e7 f0 <66> 0f 6f 07 66 0f 74 d0 66 0f 74 c1 66 0f d7 d2 66 0f d7 
c0 d3 fa
Apr 21 17:31:10 debian kernel: [38538.047907] device wlp2s0 left promiscuous 
mode
Apr 21 17:31:37 debian systemd[1]: systemd-hostnamed.service: Succeeded.

What I have done so far:

reinstalling

 - etherape (0.9.18-1)
 - etherape-data (0.9.18-1)
 - libgoocanvas-2.0-9 (2.0.4-1)
 - libgoocanvas-2.0-common (2.0.4-1)
 - libc6 (2.28-10)
 - libc6-dev (2.28-10)

But no success! (In Debian Jessie I've used etherape for many years without 
problems)

-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-8-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages etherape depends on:
ii  etherape-data0.9.18-1
ii  libatk1.0-0  2.30.0-2
ii  libc-ares2   1.14.0-1
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libfribidi0  1.0.5-3.1+deb10u1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgoocanvas-2.0-9   2.0.4-1
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libpangocairo-1.0-0  1.42.4-7~deb10u1
ii  libpcap0.8   1.8.1-6
ii  libpopt0 1.16-12

etherape recommends no packages.

etherape suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: etherape
Source-Version: 0.9.18-3
Done: =?utf-8?q?Patrick_Matth=C3=A4i?= 

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated etherape package)

(Th

Bug#960663: marked as done (softhsm2: crash/lockdown in openconnect due to atexit use)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 10:06:33 +
with message-id 
and subject line Bug#960663: fixed in softhsm2 2.6.1-2
has caused the Debian Bug report #960663,
regarding softhsm2: crash/lockdown in openconnect due to atexit use
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.)


-- 
960663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: softhsm2
Version: 2.6.1-1
Severity: serious
Justification: causes test failure and FTBFS on reverse dependency
Forwarded: https://github.com/opendnssec/SoftHSMv2/issues/548

Dear Maintainer(s),

As highlighted by Debian CI, the new version of softhsm2 causes a
breakage in src:openconnect - a test hangs and never completes.

It seems the root cause is the registration of atexit() handlers.

Upstream issue and 2 PRs to fix it:

https://github.com/opendnssec/SoftHSMv2/issues/548
https://github.com/opendnssec/SoftHSMv2/pull/550
https://github.com/opendnssec/SoftHSMv2/pull/551

In the meanwhile, I'll disable the unit test in openconnect so that I
can upload a new version - there's a security issue to fix, and softhsm
is only a sub-functionality of the package.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: softhsm2
Source-Version: 2.6.1-2
Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 

We believe that the bug you reported is fixed in the latest version of
softhsm2, 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.
Ondřej Surý  (supplier of updated softhsm2 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 11:41:43 +0200
Source: softhsm2
Architecture: source
Version: 2.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 942419 960663
Changes:
 softhsm2 (2.6.1-2) unstable; urgency=medium
 .
   * Explicitly enable ECC and EDDSA curves (Closes: #942419)
   * Fix Use after free on ENGINE_finish(rdrand_engine) (Closes: #960663)
Checksums-Sha1:
 e89b28e5d8c8cc54072e363586f8e91d40a815d3 2398 softhsm2_2.6.1-2.dsc
 a846e54c6b75e0c9ac72494091560854ffc66386 10640 softhsm2_2.6.1-2.debian.tar.xz
 90ed0c36dad9baef19ea25afe270c417ab0c9450 8026 softhsm2_2.6.1-2_amd64.buildinfo
Checksums-Sha256:
 a37271cfd60bd5b21cedde736986924dbc646558721f9d053be2d75f43cea5c4 2398 
softhsm2_2.6.1-2.dsc
 6c19550bcc501edac6f1c06636619fffdd11a5bf10f89e32300576281ad335e9 10640 
softhsm2_2.6.1-2.debian.tar.xz
 353788901279da8c82534ebbfd40ce4402d708f7d401d0e8d8e4a51a7031110c 8026 
softhsm2_2.6.1-2_amd64.buildinfo
Files:
 f75e4ca369f773244eccfc58297ad666 2398 admin optional softhsm2_2.6.1-2.dsc
 7a2a4badf9ecdb9451ea4064a5b3f491 10640 admin optional 
softhsm2_2.6.1-2.debian.tar.xz
 0b11dd1e3d519cedbf81112176dc2a58 8026 admin optional 
softhsm2_2.6.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAl6+ZKBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcKlfxAAsn4sWotRgxcQA8z3fR2MIUcJwkgPSIyyTL7y1SPhT5YcDizGZNTxUuNH
a0thPeM4TomuRRRKAipMLuhv+U4s6OjZuR23n02SnouIt/26tCtPEvgmjJpkPIYO
4k0XHUF34Z21JdbpTTGlhNa74DbFaDjsORm4qTiNWSibF9P42WfrzS1wAgmAi0Gj
Yc0kaEEYDdWLVkRq7l/jZZrtDrl+LrA61DMOLTItAVi2FCsawUBsVW6kYqPs3kIS
EQ1QAd9rurAA4ZZbm+8pUdh9ufVGHouLacac2EFCZwj+1MWJbyAsFukaqcS5QL1W
ogt0a0y0IbJVFSJea6JPys0d8bhKY0sXxvUryUh+loG4Lrup0rgmeu9FIZvza50i
BCb5mBaX2VmF1kc7gIVNXDpSJhWS4OgBNLZ9MBLoxiibqDYRsNxouDl2oBOi1Es7
fbPpaGJbVYUNcERYGM8P93n5L/PMJFT4u66kZPdYsQjvOr8Kiy1EraMtDXCBZTUf
Mb+kroHHK6eYCANebr3Dg6hip4eoF2sGD48JbApTDW/3m7Ylb7QexEuGAijRq66L
OSBRvM++OjoGCyT2kWEUmoNwg1FQd+CcY9nWmlwu8WwABrjml+r6pRvrIQk3NjvY
C6S+zsoeermVEOAKe7MEhGK6j8kAQbxMiEhTuBkzPdVr99A5iJk=
=/xZP
-END PGP SIGNATURE End Message ---

Bug#960660: cyrus-imapd: Test failure on armhf (at least on armv8)

[Adrian Bunk]

On Fri, May 15, 2020 at 12:03:16PM +0300, Adrian Bunk wrote:
>...
> "Bus error" usually means unaligned access somewhere in C code,
> and this is a more of a problem when running on armv8 than
> on armv7 (some buildds are armv7, some are armv8 like this one).

Confirmed on the porterboxes:
- tests pass on an armhf chroot on abel (armv7)
- test fails on an armhf chroot on amdahl (armv8)

Backtrace of the bus error:
#0  crc32_slice8 (prev=, data=0xf4eba75d, 
length=) at lib/crc32.c:638
#1  0xf7c3074a in crc32 (length=, data=, 
prev=) at lib/crc32.c:744
#2  crc32_iovec (iov=iov@entry=0xffeeabac, iovcnt=iovcnt@entry=3)
at lib/crc32.c:759
#3  0xf7c23492 in write_record (db=db@entry=0x1879ba8, 
record=record@entry=0xffeeabe8, key=0x189fe30 "aden.ado.ahabfirm", 
val=val@entry=0xf4eba75d ) at lib/cyrusdb_twoskip.c:796
#4  0xf7c235b4 in append_record (db=db@entry=0x1879ba8, 
record=record@entry=0xffeeabe8, key=, 
val=val@entry=0xf4eba75d ) at lib/cyrusdb_twoskip.c:839
#5  0xf7c2391e in store_here (db=db@entry=0x1879ba8, 
val=val@entry=0xf4eba75d , vallen=vallen@entry=21) at lib/cyrusdb_twoskip.c:1149
#6  0xf7c24a7e in skipwrite (force=0, datalen=21, 
data=0xf4eba75d , 
keylen=13, key=, db=0x1879ba8) at lib/cyrusdb_twoskip.c:1709
#7  mystore (db=0x1879ba8, key=, keylen=13, 
data=0xf4eba75d , 
datalen=datalen@entry=21, tidptr=, tidptr@entry=0xffeeada0, 
force=force@entry=0) at lib/cyrusdb_twoskip.c:1834
#8  0xf7c24ae8 in copy_cb (rock=0xffeead9c, key=, 
keylen=, val=, vallen=21)
at lib/cyrusdb_twoskip.c:1862
#9  0xf7c240ac in myforeach (db=db@entry=0x1879998, prefix=prefix@entry=0x0, 
prefixlen=prefixlen@entry=0, goodp=goodp@entry=0x0, 
cb=0xf7c24ad1 , rock=rock@entry=0xffeead9c, 
tidptr=, tidptr@entry=0x1879b94)
at lib/cyrusdb_twoskip.c:1626
#10 0xf7c246a4 in mycheckpoint (db=db@entry=0x1879998)
at lib/cyrusdb_twoskip.c:1890
#11 0xf7c248de in mycommit (db=0x1879998, tid=0x189ae60)
at lib/cyrusdb_twoskip.c:1768
#12 0x005aabfc in test_many () at ./cunit/aaa-db.testc:1542
#13 0x00597ab0 in __cunit_wrap_test (name=, 
fn=0x5aaa45 ) at cunit/unit.c:153
#14 0x00598cca in __cunit_test_many () at cunit/aaa-db.testc-cunit.c:169
#15 0xf798cda2 in run_single_test (pTest=pTest@entry=0x18733d8, 
pRunSummary=0xf79a4178 ) at TestRun.c:991
#16 0xf798cf8c in run_single_suite (pSuite=pSuite@entry=0x1873198, 
pRunSummary=0xf79a4178 ) at TestRun.c:876
#17 0xf798d2de in CU_run_all_tests () at TestRun.c:367
#18 0x00597078 in run_tests () at cunit/unit.c:331
#19 main (argc=, argv=) at cunit/unit.c:457


cu
Adrian

Bug#960663: softhsm2: crash/lockdown in openconnect due to atexit use

[Luca Boccassi]

On Fri, 2020-05-15 at 11:42 +0200, Ondřej Surý wrote:
> Hi Luca,
> 
> I'll upload fixed version in a minute.
> 
> Ondrej

Hi,

Note that the second PR is still pending, and the first one was not
100% correct - please don't rush it on my account, I have a simple
workaround for my unit tests, so I'm not blocked.

Thanks!

> On Fri, 15 May 2020 at 11:21, Luca Boccassi  wrote:
> 
> > Package: softhsm2
> > Version: 2.6.1-1
> > Severity: serious
> > Justification: causes test failure and FTBFS on reverse dependency
> > Forwarded: https://github.com/opendnssec/SoftHSMv2/issues/548
> > 
> > Dear Maintainer(s),
> > 
> > As highlighted by Debian CI, the new version of softhsm2 causes a
> > breakage in src:openconnect - a test hangs and never completes.
> > 
> > It seems the root cause is the registration of atexit() handlers.
> > 
> > Upstream issue and 2 PRs to fix it:
> > 
> > https://github.com/opendnssec/SoftHSMv2/issues/548
> > https://github.com/opendnssec/SoftHSMv2/pull/550
> > https://github.com/opendnssec/SoftHSMv2/pull/551
> > 
> > In the meanwhile, I'll disable the unit test in openconnect so that
> > I
> > can upload a new version - there's a security issue to fix, and
> > softhsm
> > is only a sub-functionality of the package.
> > 
> > --
> > Kind regards,
> > Luca Boccassi
> > 
-- 
Kind regards,
Luca Boccassi


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

Bug#960663: softhsm2: crash/lockdown in openconnect due to atexit use

[Ondřej Surý]

Hi Luca,

I'll upload fixed version in a minute.

Ondrej

On Fri, 15 May 2020 at 11:21, Luca Boccassi  wrote:

> Package: softhsm2
> Version: 2.6.1-1
> Severity: serious
> Justification: causes test failure and FTBFS on reverse dependency
> Forwarded: https://github.com/opendnssec/SoftHSMv2/issues/548
>
> Dear Maintainer(s),
>
> As highlighted by Debian CI, the new version of softhsm2 causes a
> breakage in src:openconnect - a test hangs and never completes.
>
> It seems the root cause is the registration of atexit() handlers.
>
> Upstream issue and 2 PRs to fix it:
>
> https://github.com/opendnssec/SoftHSMv2/issues/548
> https://github.com/opendnssec/SoftHSMv2/pull/550
> https://github.com/opendnssec/SoftHSMv2/pull/551
>
> In the meanwhile, I'll disable the unit test in openconnect so that I
> can upload a new version - there's a security issue to fix, and softhsm
> is only a sub-functionality of the package.
>
> --
> Kind regards,
> Luca Boccassi
>

Bug#960663: softhsm2: crash/lockdown in openconnect due to atexit use

[Luca Boccassi]

Package: softhsm2
Version: 2.6.1-1
Severity: serious
Justification: causes test failure and FTBFS on reverse dependency
Forwarded: https://github.com/opendnssec/SoftHSMv2/issues/548

Dear Maintainer(s),

As highlighted by Debian CI, the new version of softhsm2 causes a
breakage in src:openconnect - a test hangs and never completes.

It seems the root cause is the registration of atexit() handlers.

Upstream issue and 2 PRs to fix it:

https://github.com/opendnssec/SoftHSMv2/issues/548
https://github.com/opendnssec/SoftHSMv2/pull/550
https://github.com/opendnssec/SoftHSMv2/pull/551

In the meanwhile, I'll disable the unit test in openconnect so that I
can upload a new version - there's a security issue to fix, and softhsm
is only a sub-functionality of the package.

-- 
Kind regards,
Luca Boccassi


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

Bug#960662: spyne: unsatisfiable dependency on lxml

[Bastian Germann]

Package: python-spyne
Version: 2.12.11-1
Severity: grave
Tags: sid bullseye

python-spyne has a dependency on python-lxml which is gone because of
the py2removal effort. So python-spyne does not install in unstable anymore.

You could drop the python-lxml dependency because it is actually not a
mandatory requirement. But most people use spyne with XML based
protocols, so the far better option is to upgrade to Python 3 as
discussed in #938554.

Processed: forcibly merging 960658 960659

[Debian Bug Tracking System]

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

> forcemerge 960658 960659
Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch
Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch
Marked as found in versions cyrus-imapd/3.2.0-2.
Added tag(s) ftbfs.
Bug #960659 [src:cyrus-imapd] cyrus-imapd: Test failure on big endian
Set Bug forwarded-to-address to 
'https://github.com/cyrusimap/cyrus-imapd/issues/3040'.
Marked as found in versions cyrus-imapd/3.2.0-3.
Merged 960658 960659
> thanks
Stopping processing here.

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

Bug#960660: cyrus-imapd: Test failure on armhf (at least on armv8)

[Adrian Bunk]

Source: cyrus-imapd
Version: 3.2.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd&arch=armhf&ver=3.2.0-2&stamp=1589273502&raw=0

...
make  check-local
make[4]: Entering directory '/<>'
Running unit tests


 CUnit - A unit testing framework for C - Version 2.1-3
 http://cunit.sourceforge.net/


Suite: aaa-db
  Test: openclose ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: multiopen ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: opentwo ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: readwrite ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: multirw ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: readwrite_zerolen ...[backend=skiplist] [backend=flat] 
[backend=twoskip] [backend=zeroskip] passed
  Test: readwrite_null ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: abort ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: delete ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: mboxlist ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: foreach ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: foreach_changes ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: binary_keys ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: binary_data ...[backend=skiplist] [backend=flat] [backend=twoskip] 
[backend=zeroskip] passed
  Test: many ...[backend=skiplist] [backend=flat] [backend=twoskip] /bin/bash: 
line 10: 22859 Bus error   $vg ./unit $f
make[4]: *** [Makefile:8290: check-local] Error 135


"Bus error" usually means unaligned access somewhere in C code,
and this is a more of a problem when running on armv8 than
on armv7 (some buildds are armv7, some are armv8 like this one).

Bug#960659: cyrus-imapd: Test failure on big endian

[Adrian Bunk]

Source: cyrus-imapd
Version: 3.2.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cyrus-imapd&ver=3.2.0-2

...
make  check-local
make[4]: Entering directory '/<>'
Running unit tests


 CUnit - A unit testing framework for C - Version 2.1-3
 http://cunit.sourceforge.net/


Suite: aaa-db
  Test: openclose ...[backend=skiplist] timeout: Unknown command ''
make[4]: *** [Makefile:8290: check-local] Error 141


Same failure on all big endian architectures
(except m68k that builds with nocheck).

If this is not easily fixable one possible way forward would
be to let the test just fail, file a bug against ftp.debian.org
for removal of the s390x binaries, and lower the severity of
this bug.

Processed: src:cyrus-imapd: test fails on all big endian arch

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/cyrusimap/cyrus-imapd/issues/3040
Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch
Set Bug forwarded-to-address to 
'https://github.com/cyrusimap/cyrus-imapd/issues/3040'.

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

Bug#960658: src:cyrus-imapd: test fails on all big endian arch

[Xavier Guimard]

Package: src:cyrus-imapd
Version: 3.2.0-3
Severity: serious
Control: forwarded -1 https://github.com/cyrusimap/cyrus-imapd/issues/3040

Test fails on all big endian arch

Bug#954070: marked as done (fdroidserver: Incorrect Litecoin address validation)

[Debian Bug Tracking System]

Your message dated Fri, 15 May 2020 08:21:34 +
with message-id 
and subject line Bug#954070: fixed in fdroidserver 1.1.7-1
has caused the Debian Bug report #954070,
regarding fdroidserver: Incorrect Litecoin address validation
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.)


-- 
954070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fdroidserver
Version: 1.1.4-1~deb10u1
Severity: normal

Hello,

When using fdroid on the latest fdroiddata repository, I get this error:
CRITICAL: 'MTuf45ZvxhMWWo4v8YBbFDTLsFcGtpcPNT' is not a valid Litecoin address
in com.readrops.app. Regex pattern: ^L[a-zA-Z0-9]{33}$

But this Litecoin address is valid.

This has already been fixed upstream:
https://gitlab.com/fdroid/fdroidserver/-/merge_requests/644

Regards,



-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fdroidserver depends on:
ii  androguard   3.3.3-1
ii  default-jdk-headless 2:1.11-71
ii  openjdk-11-jdk-headless  11.0.6+10-1~deb10u1
ii  python3  3.7.3-1
ii  python3-clint0.5.1-1
ii  python3-defusedxml   0.5.0-2
ii  python3-git  2.1.11-1
ii  python3-libcloud 2.4.0-1
ii  python3-mwclient 0.8.7-1
ii  python3-paramiko 2.6.0-1~bpo10+1
ii  python3-pil  5.4.1-2+deb10u1
ii  python3-pyasn1   0.4.2-3
ii  python3-pyasn1-modules   0.2.1-0.2
ii  python3-qrcode   6.1-1
ii  python3-requests 2.21.0-1
ii  python3-ruamel.yaml  0.15.34-1+b1
ii  python3-vagrant  0.5.15-2
ii  python3-yaml 3.13-2
ii  rsync3.1.3-6

Versions of packages fdroidserver recommends:
ii  android-sdk 25.0.0+11+deb10u1
ii  apksigner   0.8-2
ii  git 1:2.20.1-2+deb10u1
ii  gnupg   2.2.12-1+deb10u1
ii  opensc  0.19.0-1
ii  openssh-client  1:7.9p1-10+deb10u2
pn  s3cmd   
ii  wget1.20.1-1.1
ii  zipalign1:8.1.0+r23-2

Versions of packages fdroidserver suggests:
ii  gradle   4.4.1-6
pn  qemu-kvm 
ii  vagrant  2.2.3+dfsg-1
pn  vagrant-cachier  
ii  vagrant-libvirt  0.0.45-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fdroidserver
Source-Version: 1.1.7-1
Done: Hans-Christoph Steiner 

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated fdroidserver 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: Fri, 15 May 2020 09:37:56 +0200
Source: fdroidserver
Architecture: source
Version: 1.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Hans-Christoph Steiner 
Changed-By: Hans-Christoph Steiner 
Closes: 954070
Changes:
 fdroidserver (1.1.7-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #954070)
   * Remove "Recommends" test, ci.debian.net do not support binfmt_misc:
 https://salsa.debian.org/ci-team/debian-ci-config/-/issues/1
Checksums-Sha1:
 2ce6b7f112f604b697c0ab64ecba8d18f08c4ed9 2015 fdroidserver_1.1.7-1.dsc
 0d053332974feb0d3e2e59ab9e7574496be8ea92 4125658 fdroidserver_1.1.7.orig.tar.gz
 fe1cbce4b0e507d8b24df9bab9f3b5b288061007 488 fdroidserver_1.1.7.orig.tar.gz.asc
 40aca50293552a9079bb417ba83f0d4c62f493a0 17616 
fdroidserver_1.1.7-1.debian.tar.xz
 ea0ad8410789a2a29ccf31920551ba03acd26530 5738 
fdroidserver_1.1.7-1_source.buildinfo
Checksums-Sha256:
 1de01877426677be7afce63a86dcf2c5e04df50631da330715c0b60de6b3e3c4 2015 
fdroidserver_1.1.7-1.dsc
 6b58b102

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

[Sebastian Ramacher]

Hi Simon

On 2020-05-14 17:18:38 +0100, Simon McVittie wrote:
> 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?

They are intended to be public. From upstream's README:

| The library contains all of the
| implementation details, and is used in the standalone tools whilst also
| enabling integration into other code bases directly.

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

According to upstream's README, at least the API should be stable:

| The interfaces have stabilized: We don't anticipate making a breaking
| change for existing features.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#960656: sdpb: FTBFS on mipsel

[Sebastian Ramacher]

Source: sdpb
Version: 1.0-3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

sdpb failed to build on mipsel while rebuilding for the tinyxml2
transition:
https://buildd.debian.org/status/fetch.php?pkg=sdpb&arch=mipsel&ver=1.0-3%2Bb5&stamp=1589492907&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#959587: marked as pending in python-biopython

[Dylan Aïssi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/python-biopython/-/commit/5cd5d8d28352dc1e9206bd2e9b891eb2bc590fd6


Add upstream patch to fix tests with new NCBI BLAST DB v5 (Closes: #959587)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/959587

Processed: Bug#959587 marked as pending in python-biopython

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #959587 [src:python-biopython] python-biopython: FTBFS: AssertionError: 
False is not true
Added tag(s) pending.

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