Processed: Re: Bug#918206: pandas: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #918206 [src:pandas] pandas: autopkgtest fails with python-numpy 
(1:1.16.0~rc1-3)
Severity set to 'serious' from 'normal'
> tags -1 + ftbfs
Bug #918206 [src:pandas] pandas: autopkgtest fails with python-numpy 
(1:1.16.0~rc1-3)
Added tag(s) ftbfs.

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

Bug#920900: libicu-dev: Command icu-config disappeared from libicu-dev

[Juhani Numminen]

On Wed, 30 Jan 2019 13:41:32 +0100 Vlastimil Zima  
wrote:
> Package: libicu-dev
> Version: 63.1-6
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> after upgrading libicu-dev, I can't install PyICU using pip, due to an error:
> 
> FileNotFoundError: [Errno 2] No such file or directory: 'icu-config': 
> 'icu-config'
> 
> I found no replacement of the icu-config, hence I assume the file disappeared 
> by an accident.
> 
> When I downgrade libicu-dev back to 60.2-6, it works.

Hi,

I'm not the maintainer but here's some further information.

That is already reported as a bug in PyICU:
https://github.com/ovalhub/pyicu/issues/92

It appears the removal of icu-config is due to it being deprecated upstream, 
and not
working with Debian's multi-arch system. So its disappearance is not an 
accident.
https://bugs.debian.org/898820

Quoting from http://userguide.icu-project.org/howtouseicu
"The recommended way to use ICU in Makefiles is to use the pkg-config files 
[...]
This is preferred over the deprecated icu-config script."


Regards,
Juhani

Bug#920858: twitter-bootstrap4: contains generated code not included as source

[Xavier]

Le 30/01/2019 à 23:47, Jonas Smedegaard a écrit :
> Quoting Xavier (2019-01-30 22:54:53)
>> Le 30/01/2019 à 22:34, Jonas Smedegaard a écrit :
>>> Quoting Xavier (2019-01-30 22:26:57)
 Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
> Source package contains below  several files embedding code 
> from external project fileOverview Kickass, without source 
> included.
> 
> Just a clarification: Name of external project is Popper.js: 
> "fileOverview" is just a marker, and "Kickass" is first word of 
> Popper.js short description.
> 
> 
 I succeed to build source, but this needs:
>>> [snip]
>>>
>>> This bugreport tracks twitter-bootstrap4 violating Policy in 
>>> shipping code without source.
>>>
>>> For discussing packaging of that source in a separate package, 
>>> please file an ITP bugreport (or an RFP bugreport if you don't 
>>> intent on doing the work yourself), and let's discuss packaging 
>>> issues there.
> 
>> Also is it OK if I remove dist/bootstrap.bundle.* in Files-Excluded ?
> 
> Sorry, I don't understand your question.
> 
> What do you mean by "also"?  Did I miss some previous conversation that 
> this is an addition of?
> 
> Are you asking if it is ok to violate Debian Policy here?  Or is your 
> question a different one? Please try rephrase...

That's not what I said. Anyway Jérémy found a way to patch this "grave
policy violation". In the same way, should you open a similar bug to any
of the packages which embeds bootstrap?

Processed: tagging 917041

[Debian Bug Tracking System]

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

> tags 917041 + pending
Bug #917041 [src:golang-github-influxdata-influxql] 
golang-github-influxdata-influxql: Outdated version produces empty results for 
some queries
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#919658: marked as done (ocaml-gettext ftbfs (comomile module not found))

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 06:34:23 +
with message-id 
and subject line Bug#919658: fixed in camomile 1.0.1-2
has caused the Debian Bug report #919658,
regarding ocaml-gettext ftbfs (comomile module not found)
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.)


-- 
919658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocaml-gettext
Version: 0.3.7-1
Severity: serious
Tags: sid buster

[...]
checking for ocamlyacc.opt... no
checking for ocamlfind... ocamlfind
checking for camlp4... camlp4
checking for camlp4o... camlp4o
checking for camlp4of... camlp4of
checking for ocamlmklib... ocamlmklib
checking for ocamldoc... ocamldoc
checking for xsltproc... xsltproc
checking for xmllint... no
checking for html XSL... 
/usr/share/xml/docbook/stylesheet/nwalsh/xhtml/chunk.xsl
checking for manpages XSL...
/usr/share/xml/docbook/stylesheet/nwalsh/manpages/docbook.xsl
checking for module fileutils... /usr/lib/ocaml/fileutils
checking for module camomile... no
configure: error: Cannot build libgettext-camomile-ocaml.
make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools] 
Error 1
--- End Message ---
--- Begin Message ---
Source: camomile
Source-Version: 1.0.1-2

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated camomile package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Jan 2019 12:28:38 +0200
Source: camomile
Binary: libcamomile-ocaml-data libcamomile-ocaml-dev
Architecture: source all amd64
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Kyle Robbertze 
Description:
 libcamomile-ocaml-data - Unicode data for OCaml
 libcamomile-ocaml-dev - Unicode library for OCaml
Closes: 918562 918563 919658 919837
Changes:
 camomile (1.0.1-2) unstable; urgency=medium
 .
   * Use dune package instead of jbuilder
   * Remove broken symlinks (Closes: #919837)
   * Drop zh__PINYIN locale (Closes: #918562, #918563)
   * Install files in the correct location (Closes: #919658)
   * Bump Standards-Version to 4.3.0 (no change)
Checksums-Sha1:
 bce2d5af0ae51dafe63550d2754ec64927abd780 2226 camomile_1.0.1-2.dsc
 49e9c942b85c16daa9b6873f1e9b471348bf82ea 59632 camomile_1.0.1-2.debian.tar.xz
 727f20605d2cb8265d2362d97a5233c2835f996c 6357 camomile_1.0.1-2_amd64.buildinfo
 1e37a2a750726b8302d3bc94c5975b6671913dce 1626964 
libcamomile-ocaml-data_1.0.1-2_all.deb
 eb250052c23d7b5b09fd4bd54365b05ec7b7921c 1958400 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb
Checksums-Sha256:
 5ca86c92c02074bfe7800967131d4bed53d3d0772f9f5460afa9b14c72d48aca 2226 
camomile_1.0.1-2.dsc
 a1b08bd73decf1f57eecafe3ee5955dcae959af45e160d3001f3362f81f726bb 59632 
camomile_1.0.1-2.debian.tar.xz
 c1a189401f33f02126f6abe598234bd768fe9784aae7663492d82359fd0de415 6357 
camomile_1.0.1-2_amd64.buildinfo
 1dde6a898e89d0d3d2e99d8a335c670d12af5155d63b51cbef0413d571cafc0a 1626964 
libcamomile-ocaml-data_1.0.1-2_all.deb
 be58d51eac5baa65284ee8d7c9f08be898b9159f1be5ec33d7f126c87e618626 1958400 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb
Files:
 e00ce1abde5019180a4cb6f90f76ff0f 2226 ocaml optional camomile_1.0.1-2.dsc
 3a719802daa65a55c0c0686966837230 59632 ocaml optional 
camomile_1.0.1-2.debian.tar.xz
 11886cc17504fcae7a47dec6a34f0173 6357 ocaml optional 
camomile_1.0.1-2_amd64.buildinfo
 ca4bbebb75e004e051facbf11e3fbfdf 1626964 ocaml optional 
libcamomile-ocaml-data_1.0.1-2_all.deb
 8453e8b822d8437ca534f1634d164a6c 1958400 ocaml optional 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEiuvsv142+SACr85uZK6O8aoGRHQFAlxSkn8VHGtyb2JiZXJ0
emVAZ21haWwuY29tAAoJEGSujvGqBkR00OgP/2rJEvSXGBV18tYv7ISfaFn9f7T3
2imbxDf2BOCdTjT1v+wuxqz7wuV3ULHdBJk2PyJuyvDFB+Fb/zjDRT6LTnbCz3Ww
Y9U/wNZNdd+dyDpjmpCEyuxzVsyrvbeytBjERcKUTalW170aRkZReex5jqJXMBUx
NKMUWzEL/fU74RfUc7gvgT/Q4WLqR4kAE6XkyIJfZazvb9Htp2pclBNWMY5g0P7x
g8s93iY6ZpR1ibouZ10JmEoOmnH9hh6

Bug#918562: marked as done (camomile FTBFS on ocaml bytecode architectures: Fatal error: exception Stack overflow)

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 06:34:23 +
with message-id 
and subject line Bug#918562: fixed in camomile 1.0.1-2
has caused the Debian Bug report #918562,
regarding camomile FTBFS on ocaml bytecode architectures: Fatal error: 
exception Stack overflow
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.)


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

https://buildd.debian.org/status/package.php?p=camomile

...
camomilelocaledef Camomile/locales/zh__PINYIN.mar (exit 2)
(cd _build/default/Camomile && tools/camomilelocaledef.exe --file 
locales/zh__PINYIN.txt locales)
Fatal error: exception Stack overflow
make[1]: *** [debian/rules:52: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: camomile
Source-Version: 1.0.1-2

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated camomile package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Jan 2019 12:28:38 +0200
Source: camomile
Binary: libcamomile-ocaml-data libcamomile-ocaml-dev
Architecture: source all amd64
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Kyle Robbertze 
Description:
 libcamomile-ocaml-data - Unicode data for OCaml
 libcamomile-ocaml-dev - Unicode library for OCaml
Closes: 918562 918563 919658 919837
Changes:
 camomile (1.0.1-2) unstable; urgency=medium
 .
   * Use dune package instead of jbuilder
   * Remove broken symlinks (Closes: #919837)
   * Drop zh__PINYIN locale (Closes: #918562, #918563)
   * Install files in the correct location (Closes: #919658)
   * Bump Standards-Version to 4.3.0 (no change)
Checksums-Sha1:
 bce2d5af0ae51dafe63550d2754ec64927abd780 2226 camomile_1.0.1-2.dsc
 49e9c942b85c16daa9b6873f1e9b471348bf82ea 59632 camomile_1.0.1-2.debian.tar.xz
 727f20605d2cb8265d2362d97a5233c2835f996c 6357 camomile_1.0.1-2_amd64.buildinfo
 1e37a2a750726b8302d3bc94c5975b6671913dce 1626964 
libcamomile-ocaml-data_1.0.1-2_all.deb
 eb250052c23d7b5b09fd4bd54365b05ec7b7921c 1958400 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb
Checksums-Sha256:
 5ca86c92c02074bfe7800967131d4bed53d3d0772f9f5460afa9b14c72d48aca 2226 
camomile_1.0.1-2.dsc
 a1b08bd73decf1f57eecafe3ee5955dcae959af45e160d3001f3362f81f726bb 59632 
camomile_1.0.1-2.debian.tar.xz
 c1a189401f33f02126f6abe598234bd768fe9784aae7663492d82359fd0de415 6357 
camomile_1.0.1-2_amd64.buildinfo
 1dde6a898e89d0d3d2e99d8a335c670d12af5155d63b51cbef0413d571cafc0a 1626964 
libcamomile-ocaml-data_1.0.1-2_all.deb
 be58d51eac5baa65284ee8d7c9f08be898b9159f1be5ec33d7f126c87e618626 1958400 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb
Files:
 e00ce1abde5019180a4cb6f90f76ff0f 2226 ocaml optional camomile_1.0.1-2.dsc
 3a719802daa65a55c0c0686966837230 59632 ocaml optional 
camomile_1.0.1-2.debian.tar.xz
 11886cc17504fcae7a47dec6a34f0173 6357 ocaml optional 
camomile_1.0.1-2_amd64.buildinfo
 ca4bbebb75e004e051facbf11e3fbfdf 1626964 ocaml optional 
libcamomile-ocaml-data_1.0.1-2_all.deb
 8453e8b822d8437ca534f1634d164a6c 1958400 ocaml optional 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEiuvsv142+SACr85uZK6O8aoGRHQFAlxSkn8VHGtyb2JiZXJ0
emVAZ21haWwuY29tAAoJEGSujvGqBkR00OgP/2rJEvSXGBV18tYv7ISfaFn9f7T3
2imbxDf2BOCdTjT1v+wuxqz7wuV3ULHdBJk2PyJuyvDFB+Fb/zjDRT6LTnbCz3Ww
Y9U/wNZNdd+dyDpjmpCEyuxzVsyrvbeytBjERcKUTalW170aRkZReex5jqJXMBUx
NKMUWzEL/fU74RfUc7gvgT/Q4WLqR4kAE6XkyIJfZazvb9Htp2pclBNWMY5g0P7x
g8s93iY6ZpR1ibouZ10JmEoOmnH9hh6bHMxyeWYepFzJ325V3dE7h6LML/dTrioy
1/vVUvMXf40CrmUjFCPzUAVgI0JnzO2K48LtRyD3BME1YDzvNYwXmGP/x3OMtVwS
jPWtOTETA9CKCAJ56m8ZRcrDwMRnRDoZUtKSrJ1LSALfhvHcp2jgPJS9GJEBnqrg
H5+luLbPZ8LrbaeYNHVV8OC5WN/jFpKZXScX4jn1UjqR2lbXzRH//1Vwf4mSH6Wl
+9tC+tUMstt36PejdcXTL8vL7m5x0htiQbCe5VFGjbhabPEULkHIJp0El2sYijL8
LRARnjjuHuBRh5jhXZQ6gQtT601Wdp6JdDM+0P/WxWDQrRG6W4Vx3BDUqnq/TNvi
Scb4Zdv6OLg

Bug#918563: marked as done (camomile FTBFS on ppc64{,el}: camomilelocaledef got signal SEGV)

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 06:34:23 +
with message-id 
and subject line Bug#918563: fixed in camomile 1.0.1-2
has caused the Debian Bug report #918563,
regarding camomile FTBFS on ppc64{,el}: camomilelocaledef got signal SEGV
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.)


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

https://buildd.debian.org/status/package.php?p=camomile

...
camomilelocaledef Camomile/locales/zh__PINYIN.mar (got signal SEGV)
(cd _build/default/Camomile && tools/camomilelocaledef.exe --file 
locales/zh__PINYIN.txt locales)
make[1]: *** [debian/rules:52: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: camomile
Source-Version: 1.0.1-2

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated camomile package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Jan 2019 12:28:38 +0200
Source: camomile
Binary: libcamomile-ocaml-data libcamomile-ocaml-dev
Architecture: source all amd64
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Kyle Robbertze 
Description:
 libcamomile-ocaml-data - Unicode data for OCaml
 libcamomile-ocaml-dev - Unicode library for OCaml
Closes: 918562 918563 919658 919837
Changes:
 camomile (1.0.1-2) unstable; urgency=medium
 .
   * Use dune package instead of jbuilder
   * Remove broken symlinks (Closes: #919837)
   * Drop zh__PINYIN locale (Closes: #918562, #918563)
   * Install files in the correct location (Closes: #919658)
   * Bump Standards-Version to 4.3.0 (no change)
Checksums-Sha1:
 bce2d5af0ae51dafe63550d2754ec64927abd780 2226 camomile_1.0.1-2.dsc
 49e9c942b85c16daa9b6873f1e9b471348bf82ea 59632 camomile_1.0.1-2.debian.tar.xz
 727f20605d2cb8265d2362d97a5233c2835f996c 6357 camomile_1.0.1-2_amd64.buildinfo
 1e37a2a750726b8302d3bc94c5975b6671913dce 1626964 
libcamomile-ocaml-data_1.0.1-2_all.deb
 eb250052c23d7b5b09fd4bd54365b05ec7b7921c 1958400 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb
Checksums-Sha256:
 5ca86c92c02074bfe7800967131d4bed53d3d0772f9f5460afa9b14c72d48aca 2226 
camomile_1.0.1-2.dsc
 a1b08bd73decf1f57eecafe3ee5955dcae959af45e160d3001f3362f81f726bb 59632 
camomile_1.0.1-2.debian.tar.xz
 c1a189401f33f02126f6abe598234bd768fe9784aae7663492d82359fd0de415 6357 
camomile_1.0.1-2_amd64.buildinfo
 1dde6a898e89d0d3d2e99d8a335c670d12af5155d63b51cbef0413d571cafc0a 1626964 
libcamomile-ocaml-data_1.0.1-2_all.deb
 be58d51eac5baa65284ee8d7c9f08be898b9159f1be5ec33d7f126c87e618626 1958400 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb
Files:
 e00ce1abde5019180a4cb6f90f76ff0f 2226 ocaml optional camomile_1.0.1-2.dsc
 3a719802daa65a55c0c0686966837230 59632 ocaml optional 
camomile_1.0.1-2.debian.tar.xz
 11886cc17504fcae7a47dec6a34f0173 6357 ocaml optional 
camomile_1.0.1-2_amd64.buildinfo
 ca4bbebb75e004e051facbf11e3fbfdf 1626964 ocaml optional 
libcamomile-ocaml-data_1.0.1-2_all.deb
 8453e8b822d8437ca534f1634d164a6c 1958400 ocaml optional 
libcamomile-ocaml-dev_1.0.1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEiuvsv142+SACr85uZK6O8aoGRHQFAlxSkn8VHGtyb2JiZXJ0
emVAZ21haWwuY29tAAoJEGSujvGqBkR00OgP/2rJEvSXGBV18tYv7ISfaFn9f7T3
2imbxDf2BOCdTjT1v+wuxqz7wuV3ULHdBJk2PyJuyvDFB+Fb/zjDRT6LTnbCz3Ww
Y9U/wNZNdd+dyDpjmpCEyuxzVsyrvbeytBjERcKUTalW170aRkZReex5jqJXMBUx
NKMUWzEL/fU74RfUc7gvgT/Q4WLqR4kAE6XkyIJfZazvb9Htp2pclBNWMY5g0P7x
g8s93iY6ZpR1ibouZ10JmEoOmnH9hh6bHMxyeWYepFzJ325V3dE7h6LML/dTrioy
1/vVUvMXf40CrmUjFCPzUAVgI0JnzO2K48LtRyD3BME1YDzvNYwXmGP/x3OMtVwS
jPWtOTETA9CKCAJ56m8ZRcrDwMRnRDoZUtKSrJ1LSALfhvHcp2jgPJS9GJEBnqrg
H5+luLbPZ8LrbaeYNHVV8OC5WN/jFpKZXScX4jn1UjqR2lbXzRH//1Vwf4mSH6Wl
+9tC+tUMstt36PejdcXTL8vL7m5x0htiQbCe5VFGjbhabPEULkHIJp0El2sYijL8
LRARnjjuHuBRh5jhXZQ6gQtT601Wdp6JdDM+0P/WxWDQrRG6W4Vx3BDUqnq/TNvi
Scb4Zdv6OLglAMkOmscoivFcU0BMXT6KHilMgvr0qrC8TqGtdJm2kxCtFTV9aIj

Bug#919472: marked as done (camomile ftbfs on ppc64el)

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 06:34:23 +
with message-id 
and subject line Bug#918563: fixed in camomile 1.0.1-2
has caused the Debian Bug report #918563,
regarding camomile ftbfs on ppc64el
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.)


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

checked on the ppc64el porter box:

[...]
   dh_ocamlinit -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/doko/camomile-1.0.1'
ocaml configure.ml --share=/home/doko/camomile-1.0.1/debian/tmp/usr/share
make[1]: Leaving directory '/home/doko/camomile-1.0.1'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/doko/camomile-1.0.1'
[ -f debian/autoreconf.before ] || dh_autoreconf
jbuilder build
File "Camomile/jbuild", line 4, characters 0-96:
4 | (rule (with-stdout-to installConfig.ml
5 |(echo "let share_dir = \"/usr/share/camomile\"")))
Warning: File installConfig.ml is both generated by a rule and present in the
source tree.
As a result, the rule is currently ignored, however this will become an error in
the future.
To keep the current behavior and get rid of this warning, add a field (fallback)
to the rule.
   ocamlyacc Camomile/internal/uReStrParser.{ml,mli}
4 shift/reduce conflicts.
camomilelocaledef Camomile/locales/ar.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/az.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/div.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/el.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/fa.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/gu.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/he.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/hi__DIRECT.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/hi.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ka.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/kk.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/kn.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ky.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/mn.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/mr.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/pa.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/sa.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ja.mar
Warning : strength option is not supported
camomilelocaledef Camomile/locales/syr.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/te.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ta.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/tt.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/th.mar
Warning : file loading is not supported.
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/ur.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/uz.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/vi.mar
Warning : normalization option is not supported
camomilelocaledef Camomile/locales/zh__PINYIN.mar (got signal SEGV)
(cd _build/default/Camomile && tools/camomilelocaledef.exe --file
locales/zh__PINYIN.txt locales)
make[1]: *** [debian/rules:52: override_dh_auto_build] Error 1
make[1]: Leaving directory '/home/doko/camomile-1.0.1'
make: *** [debian/rules:42: build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: camomile
Source-Version: 1.0.1-2

We believe that the bug you reported is fixed in the latest version of
camomile, 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 918...@bugs.debian.org,
and the maintaine

Bug#917714: marked as done (lizzie: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiMo

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 05:50:43 +
with message-id 
and subject line Bug#917657: fixed in lizzie 0.6+dfsg1-2
has caused the Debian Bug report #917657,
regarding lizzie: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java 
-noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
-Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
-Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
--batch-mode test returned exit code 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.)


-- 
917657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lizzie
Version: 0.6+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/lizzie-0.6+dfsg1'
> HOME=/<>/lizzie-0.6+dfsg1/debian/runtest xvfb-run -a dh_auto_test
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
> -Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
> --batch-mode test
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< featurecat:lizzie 
> >--
> [INFO] Building lizzie 0.6
> [INFO] [ jar 
> ]-
> [WARNING] The artifact org.json:json:jar:debian-latest has been relocated to 
> org.json:json:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> lizzie ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 7 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ lizzie ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ lizzie ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /<>/lizzie-0.6+dfsg1/src/test/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ 
> lizzie ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ lizzie ---
> [INFO] 
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running featurecat.lizzie.rules.SGFParserTest
> Creating config file /home/user42/.config/leela-zero/lizzie-config.txt
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.072 
> s <<< FAILURE! - in featurecat.lizzie.rules.SGFParserTest
> [ERROR] run(featurecat.lizzie.rules.SGFParserTest)  Time elapsed: 0.03 s  <<< 
> ERROR!
> java.io.IOException: No such file or directory
>   at featurecat.lizzie.rules.SGFParserTest.run(SGFParserTest.java:24)
> 
> [INFO] Running featurecat.lizzie.analysis.MoveDataTest
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 
> s - in featurecat.lizzie.analysis.MoveDataTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [ERROR] Errors: 
> [ERROR]   SGFParserTest.run:24 ? IO No such file or directory
> [INFO] 
> [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> [INFO] 
> [INFO] 
> 

Bug#917657: marked as done (lizzie: FTBFS (autobuilder hangs))

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 05:50:43 +
with message-id 
and subject line Bug#917657: fixed in lizzie 0.6+dfsg1-2
has caused the Debian Bug report #917657,
regarding lizzie: FTBFS (autobuilder hangs)
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.)


-- 
917657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lizzie
Version: 0.6+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -pliblizzie-java --debian-build --keep-pom-version 
--maven-repo=/<>/lizzie-0.6\+dfsg1/debian/maven-repo
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
-Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...

[... snipped ...]

at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at 
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at 
featurecat.lizzie.gui.BoardRenderer.drawBranch(BoardRenderer.java:369)
at featurecat.lizzie.gui.BoardRenderer.draw(BoardRenderer.java:101)
at featurecat.lizzie.gui.LizzieFrame.paint(LizzieFrame.java:642)
at 
java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:876)
at 
java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:848)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at 
java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:848)
at 
java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:823)
at 
java.desktop/javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:772)
at 
java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1890)
at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDom

Bug#917657: marked as done (lizzie: FTBFS (autobuilder hangs))

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 05:50:43 +
with message-id 
and subject line Bug#917714: fixed in lizzie 0.6+dfsg1-2
has caused the Debian Bug report #917714,
regarding lizzie: FTBFS (autobuilder hangs)
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.)


-- 
917714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lizzie
Version: 0.6+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -pliblizzie-java --debian-build --keep-pom-version 
--maven-repo=/<>/lizzie-0.6\+dfsg1/debian/maven-repo
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
-Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...

[... snipped ...]

at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at 
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at 
featurecat.lizzie.gui.BoardRenderer.drawBranch(BoardRenderer.java:369)
at featurecat.lizzie.gui.BoardRenderer.draw(BoardRenderer.java:101)
at featurecat.lizzie.gui.LizzieFrame.paint(LizzieFrame.java:642)
at 
java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:876)
at 
java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:848)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at 
java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:848)
at 
java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:823)
at 
java.desktop/javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:772)
at 
java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1890)
at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDom

Bug#917714: marked as done (lizzie: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiMo

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 05:50:43 +
with message-id 
and subject line Bug#917714: fixed in lizzie 0.6+dfsg1-2
has caused the Debian Bug report #917714,
regarding lizzie: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java 
-noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
-Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
-Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
--batch-mode test returned exit code 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.)


-- 
917714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lizzie
Version: 0.6+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/lizzie-0.6+dfsg1'
> HOME=/<>/lizzie-0.6+dfsg1/debian/runtest xvfb-run -a dh_auto_test
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
> -Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
> --batch-mode test
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< featurecat:lizzie 
> >--
> [INFO] Building lizzie 0.6
> [INFO] [ jar 
> ]-
> [WARNING] The artifact org.json:json:jar:debian-latest has been relocated to 
> org.json:json:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> lizzie ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 7 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ lizzie ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ lizzie ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /<>/lizzie-0.6+dfsg1/src/test/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ 
> lizzie ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ lizzie ---
> [INFO] 
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running featurecat.lizzie.rules.SGFParserTest
> Creating config file /home/user42/.config/leela-zero/lizzie-config.txt
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.072 
> s <<< FAILURE! - in featurecat.lizzie.rules.SGFParserTest
> [ERROR] run(featurecat.lizzie.rules.SGFParserTest)  Time elapsed: 0.03 s  <<< 
> ERROR!
> java.io.IOException: No such file or directory
>   at featurecat.lizzie.rules.SGFParserTest.run(SGFParserTest.java:24)
> 
> [INFO] Running featurecat.lizzie.analysis.MoveDataTest
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 
> s - in featurecat.lizzie.analysis.MoveDataTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [ERROR] Errors: 
> [ERROR]   SGFParserTest.run:24 ? IO No such file or directory
> [INFO] 
> [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> [INFO] 
> [INFO] 
> 

Processed: user debian...@lists.debian.org, usertagging 908694, usertagging 900787, affects 900787 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 908694 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 900787 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 900787 + xserver-xorg-video-nvidia-legacy-304xx
Bug #900787 [src:nvidia-graphics-drivers-legacy-304xx] 
nvidia-graphics-drivers-legacy-304xx: does not support Xorg Xserver 1.20
Added indication that 900787 affects xserver-xorg-video-nvidia-legacy-304xx
> found 900787 304.137-6
Bug #900787 [src:nvidia-graphics-drivers-legacy-304xx] 
nvidia-graphics-drivers-legacy-304xx: does not support Xorg Xserver 1.20
Marked as found in versions nvidia-graphics-drivers-legacy-304xx/304.137-6.
> thanks
Stopping processing here.

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

Bug#915426: git breaks git-remote-hg autopkgtest

[Jonathan Nieder]

Hi again,

On 25 January 2019, Jonathan McCrohan wrote:

> I am happy to work on fixing up the FTBFS, but
> because I am not a DD, I would need a sponsor to upload for me.

I'm happy to sponsor an upload, especially if this is a first step
toward team maintenance with Jonas (who I can speak from experience in
saying is a very pleasant person to collaborate with) and that upload
removes me from Uploaders.  It's the least I can do. :)

If you run into any trouble, just ask.

Thanks,
Jonathan

Bug#888903: jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify

[Jérémy Lal]

Package: node-js-beautify
Version: 1.7.5+dfsg-1
Followup-For: Bug #888903

Hi,

i find it funny that no one even tried to solve this bug:
both packages (python-jsbeautifier, node-js-beautify)
have the same upstream !
The solution here is to provide two dpkg-alternative to
/usr/bin/js-beautify.

It's blocking postcss, it would be nice to quickly fix this.

Jérémy

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
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 node-js-beautify depends on:
ii  node-config-chain  1.1.11-1
ii  node-mkdirp0.5.1-1
ii  node-nopt  3.0.6-3
ii  nodejs 10.15.1~dfsg-1

node-js-beautify recommends no packages.

node-js-beautify suggests no packages.

Bug#920834: marked as done (mlucas: FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Thu, 31 Jan 2019 00:09:29 +
with message-id 
and subject line Bug#920834: fixed in mlucas 17.1-2
has caused the Debian Bug report #920834,
regarding mlucas: FTBFS on i386
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0

...
gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize -floop-nest-optimize 
-fomit-frame-pointer -g -g3 -fstack-protector-strong -fstack-clash-protection 
-mmitigate-rop -fwrapv -m32 -msse2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,-z,now -o mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o 
src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o 
src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o 
src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o 
src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o 
src/mlucas_sse2-get_fp_rnd_const.o src/mlucas_sse2-get_preferred_fft_radix.o 
src/mlucas_sse2-imul_macro.o src/mlucas_sse2-mers_mod_square.o 
src/mlucas_sse2-mi64.o src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o 
src/mlucas_sse2-radix1008_ditN_cy_dif1.o 
src/mlucas_sse2-radix1024_ditN_cy_dif1.o 
src/mlucas_sse2-radix104_ditN_cy_dif1.o src/mlucas_sse2-radix10_ditN_cy_dif1.o 
src/mlucas_sse2-radix112_ditN_cy_dif1.o src/mlucas_sse2-radix11_ditN_cy_dif1.o 
src/mlucas_sse2-radix120_ditN_cy_dif1.o src/mlucas_sse2-radix128_ditN_cy_dif1.o 
src/mlucas_sse2-radix12_ditN_cy_dif1.o src/mlucas_sse2-radix13_ditN_cy_dif1.o 
src/mlucas_sse2-radix144_ditN_cy_dif1.o src/mlucas_sse2-radix14_ditN_cy_dif1.o 
src/mlucas_sse2-radix15_ditN_cy_dif1.o src/mlucas_sse2-radix160_ditN_cy_dif1.o 
src/mlucas_sse2-radix16_dif_dit_pass.o src/mlucas_sse2-radix16_ditN_cy_dif1.o 
src/mlucas_sse2-radix16_dyadic_square.o src/mlucas_sse2-radix16_pairFFT_mul.o 
src/mlucas_sse2-radix16_wrapper_ini.o src/mlucas_sse2-radix16_wrapper_square.o 
src/mlucas_sse2-radix176_ditN_cy_dif1.o src/mlucas_sse2-radix18_ditN_cy_dif1.o 
src/mlucas_sse2-radix192_ditN_cy_dif1.o src/mlucas_sse2-radix208_ditN_cy_dif1.o 
src/mlucas_sse2-radix20_ditN_cy_dif1.o src/mlucas_sse2-radix224_ditN_cy_dif1.o 
src/mlucas_sse2-radix22_ditN_cy_dif1.o src/mlucas_sse2-radix240_ditN_cy_dif1.o 
src/mlucas_sse2-radix24_ditN_cy_dif1.o src/mlucas_sse2-radix256_ditN_cy_dif1.o 
src/mlucas_sse2-radix26_ditN_cy_dif1.o src/mlucas_sse2-radix288_ditN_cy_dif1.o 
src/mlucas_sse2-radix28_ditN_cy_dif1.o src/mlucas_sse2-radix30_ditN_cy_dif1.o 
src/mlucas_sse2-radix31_ditN_cy_dif1.o src/mlucas_sse2-radix32_dif_dit_pass.o 
src/mlucas_sse2-radix32_ditN_cy_dif1.o src/mlucas_sse2-radix32_dyadic_square.o 
src/mlucas_sse2-radix32_wrapper_ini.o src/mlucas_sse2-radix32_wrapper_square.o 
src/mlucas_sse2-radix36_ditN_cy_dif1.o src/mlucas_sse2-radix4032_ditN_cy_dif1.o 
src/mlucas_sse2-radix40_ditN_cy_dif1.o src/mlucas_sse2-radix44_ditN_cy_dif1.o 
src/mlucas_sse2-radix48_ditN_cy_dif1.o src/mlucas_sse2-radix512_ditN_cy_dif1.o 
src/mlucas_sse2-radix52_ditN_cy_dif1.o src/mlucas_sse2-radix56_ditN_cy_dif1.o 
src/mlucas_sse2-radix5_ditN_cy_dif1.o src/mlucas_sse2-radix60_ditN_cy_dif1.o 
src/mlucas_sse2-radix63_ditN_cy_dif1.o src/mlucas_sse2-radix64_ditN_cy_dif1.o 
src/mlucas_sse2-radix6_ditN_cy_dif1.o src/mlucas_sse2-radix72_ditN_cy_dif1.o 
src/mlucas_sse2-radix768_ditN_cy_dif1.o src/mlucas_sse2-radix7_ditN_cy_dif1.o 
src/mlucas_sse2-radix80_ditN_cy_dif1.o src/mlucas_sse2-radix88_ditN_cy_dif1.o 
src/mlucas_sse2-radix8_dif_dit_pass.o src/mlucas_sse2-radix8_ditN_cy_dif1.o 
src/mlucas_sse2-radix960_ditN_cy_dif1.o src/mlucas_sse2-radix96_ditN_cy_dif1.o 
src/mlucas_sse2-radix992_ditN_cy_dif1.o src/mlucas_sse2-radix9_ditN_cy_dif1.o 
src/mlucas_sse2-rng_isaac.o src/mlucas_sse2-test_fft_radix.o 
src/mlucas_sse2-threadpool.o src/mlucas_sse2-twopmodq.o 
src/mlucas_sse2-twopmodq100.o src/mlucas_sse2-twopmodq128.o 
src/mlucas_sse2-twopmodq128_96.o src/mlucas_sse2-twopmodq160.o 
src/mlucas_sse2-twopmodq192.o src/mlucas_sse2-twopmodq256.o 
src/mlucas_sse2-twopmodq64_test.o src/mlucas_sse2-twopmodq80.o 
src/mlucas_sse2-twopmodq96.o src/mlucas_sse2-types.o src/mlucas_sse2-util.o  
-lm 
/usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 222
/tmp/ccxqWoW9.ltrans26.ltrans.o: in function `radix16_dyadic_square':
:(.text+0x1213e): undefined reference to 
`SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13'

Bug#920609: marked as done (lynkeos.app: Does not start; assertion failure)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 23:34:43 +
with message-id 
and subject line Bug#920609: fixed in lynkeos.app 3.1+dfsg1-1
has caused the Debian Bug report #920609,
regarding lynkeos.app: Does not start; assertion failure
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.)


-- 
920609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lynkeos.app
Version: 2.10+dfsg1-3+b2
Severity: grave

$ Lynkeos
2019-01-27 14:04:19.881 Lynkeos[10492:10492] styleoffsets ... guessing offsets
2019-01-27 14:04:19.882 Lynkeos[10492:10492] styleoffsets ... guessing offsets
2019-01-27 14:04:20.852 Lynkeos[10492:10492] Selected non-scalable font.
2019-01-27 14:04:20.999 Lynkeos[10492:10492] File NSData.m: 253. In 
readContentsOfFile Open ((null)) attempt failed - bad path
2019-01-27 14:04:21.000 Lynkeos[10492:10492] Could not convert cursor bitmap 
data
Lynkeos: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && 
old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
Прекъснат

(gdb) bt
#0  0x7544d85b in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
#1  0x75438535 in __GI_abort () at abort.c:79
#2  0x75495c98 in __malloc_assert 
(assertion=assertion@entry=0x7559c230 "(old_top == initial_top (av) && 
old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x755983b0 "malloc.c", line=line@entry=2385, 
function=function@entry=0x7559c940 <__PRETTY_FUNCTION__.12981> "sysmalloc") 
at malloc.c:298
#3  0x7549809f in sysmalloc (nb=nb@entry=64, av=av@entry=0x755d1c40 
) at malloc.c:2382
#4  0x754994e9 in _int_malloc (av=av@entry=0x755d1c40 , 
bytes=bytes@entry=48) at malloc.c:4133
#5  0x7549a603 in __GI___libc_malloc (bytes=48) at malloc.c:3049
#6  0x756033b9 in objc_malloc (size=size@entry=48) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/memory.c:95
#7  0x7560492f in sarray_lazy_copy (oarr=0x5582a100) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/sarray.c:489
#8  0x75605c59 in __objc_prepare_dtable_for_class 
(cls=cls@entry=0x556a5220 <_OBJC_MetaClass_MyImageAnalyzerPrefs>) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/sendmsg.c:1095
#9  0x75605a88 in __objc_install_dtable_for_class (cls=0x556a5220 
<_OBJC_MetaClass_MyImageAnalyzerPrefs>) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/sendmsg.c:1012
#10 0x75605a88 in __objc_install_dtable_for_class (cls=0x556a5220 
<_OBJC_MetaClass_MyImageAnalyzerPrefs>) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/sendmsg.c:981
#11 0x75606dd4 in get_implementation (sel=, 
class=, receiver=) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/sendmsg.c:260
#12 0x75606dd4 in objc_msg_lookup 
(receiver=receiver@entry=0x556a4fa0 <_OBJC_Class_MyImageAnalyzerPrefs>, 
op=op@entry=0x556deb90 <_OBJC_SELECTOR_TABLE+1968>) at 
/build/gcc-8-oQsZX8/gcc-8-8.2.0/src/libobjc/sendmsg.c:450
#13 0x5563391f in -[MyPluginsController(Private) 
processPreferencesClass:] (self=0x581d2a80, _cmd=, 
theClass=0x556a4fa0 <_OBJC_Class_MyImageAnalyzerPrefs>) at 
./GNUstep/../Sources/MyPluginsController.m:330
#14 0x55633ab8 in -[MyPluginsController(Private) retrieveClasses] 
(self=0x581d2a80, _cmd=) at 
./GNUstep/../Sources/MyPluginsController.m:389
#15 0x55632fba in -[MyPluginsController init] (self=0x581d2a80, 
_cmd=) at ./GNUstep/../Sources/MyPluginsController.m:542
#16 0x55632c54 in +[MyPluginsController defaultPluginController] 
(self=0x556df440 <_OBJC_Class_MyPluginsController>, _cmd=0x556f0100 
<_OBJC_SELECTOR_TABLE+1664>) at ./GNUstep/../Sources/MyPluginsController.m:521
#17 0x5563c942 in -[MyUserPrefsController 
toolbarSelectableItemIdentifiers:] (self=, _cmd=, 
toolbar=) at ./GNUstep/../Sources/MyUserPrefsController.m:99
#18 0x75fb1533 in -[NSToolbar _build] (self=0x581c6c50, 
_cmd=) at NSToolbar.m:1041
#19 0x5563cfad in -[MyUserPrefsController init] (self=0x581cba40, 
_cmd=) at ./GNUstep/../Sources/MyUserPrefsController.m:75
#20 0x76021a7d in -[NSCustomObject nibInstantiate] 
(self=0x57a26a60, _cmd=) at GSNibLoading.m:1009
#21 0x76052bb1 in -[GSXibLoader awake:inContainer:withContext:] 
(self=, _cmd=, rootObjects=, 
objects=0x56f963f0, context=) at GSXibLoa

Bug#918802: marked as done (python-gmpy2: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath')

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 23:04:41 +
with message-id 
and subject line Bug#918802: fixed in python-gmpy2 2.1.0~a4-1
has caused the Debian Bug report #918802,
regarding python-gmpy2: FTBFS with Sphinx 1.8: No module named 
'sphinx.ext.pngmath'
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.)


-- 
918802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gmpy2
Version: 2.0.8-3
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.8

Dear Maintainer,

python-gmpy2 fails to build with Sphinx 1.8, currently available in
experimental:

  make[2]: Entering directory '/<>/docs'
  sphinx-build -b man -d _build/doctrees  -D today="July 23, 2018" . _build/man
  Running Sphinx v1.8.3

  Extension error:
  Could not import extension sphinx.ext.pngmath (exception: No module named 
'sphinx.ext.pngmath')
  make[2]: *** [Makefile:112: man] Error 2

The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1]
in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which
also has SVG support in addition to PNG.

Upstream gmpy has already updated [3] their conf.py file.

[1]: https://github.com/sphinx-doc/sphinx/pull/4702
[2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html
[3]: https://github.com/aleaxit/gmpy/commit/c35c1f3319fcf95e

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-gmpy2
Source-Version: 2.1.0~a4-1

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

Debian distribution maintenance software
pp.
Martin Kelly  (supplier of updated python-gmpy2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Jan 2019 18:33:02 -0800
Source: python-gmpy2
Binary: python-gmpy2 python-gmpy2-common python-gmpy2-dbgsym python-gmpy2-doc 
python3-gmpy2 python3-gmpy2-dbgsym
Architecture: source all amd64
Version: 2.1.0~a4-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Kelly 
Changed-By: Martin Kelly 
Description:
 python-gmpy2 - interfaces GMP to Python 2 for fast, unbound-precision 
computatio
 python-gmpy2-common - common files for python-gmpy2
 python-gmpy2-doc - documentation for python-gmpy2
 python3-gmpy2 - interfaces GMP to Python 3 for fast, unbound-precision 
computatio
Closes: 918802
Changes:
 python-gmpy2 (2.1.0~a4-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
 .
   [ Martin Kelly ]
   * Update to 2.1.0~a4 (Closes: #918802).
   * Fix a variety of Lintian warnings.
Checksums-Sha1:
 3fe3f25132ae20a57692ef673ef466f6dce28294 2423 python-gmpy2_2.1.0~a4-1.dsc
 e9fce01adf59ca47d8b7720e2d3a35c059a4dff2 236435 
python-gmpy2_2.1.0~a4.orig.tar.gz
 85e56099c7f75cb611d5f98a140bd4e5674da622 4552 
python-gmpy2_2.1.0~a4-1.debian.tar.xz
 30b22fb6e7b5e25cf6e6dd7763cc84b69479f5fd 30464 
python-gmpy2-common_2.1.0~a4-1_all.deb
 b74378efb60d73b1ff8a70bca9a3a7e82fb56afc 357024 
python-gmpy2-dbgsym_2.1.0~a4-1_amd64.deb
 ce137279cf23f7ff07ac0bc4dbce0b01035052fc 59932 
python-gmpy2-doc_2.1.0~a4-1_all.deb
 f9abd50a2471b93df518c933e2688eedda2f9591 9487 
python-gmpy2_2.1.0~a4-1_amd64.buildinfo
 2fb178c3ff2ff230b0f752ec1eeb50bf5dcd15d5 143716 
python-gmpy2_2.1.0~a4-1_amd64.deb
 21071337e0e3f1165192115822a6d27659e2bc55 383128 
python3-gmpy2-dbgsym_2.1.0~a4-1_amd64.deb
 49fc10dcb6e97bfbf0071b570c085904d2c2df6b 140392 
python3-gmpy2_2.1.0~a4-1_amd64.deb
Checksums-Sha256:
 01caae8524d29febc374c7bc48c9faf27732706ccc5c8a0079a65fecab087e31 2423 
python-gmpy2_2.1.0~a4-1.dsc
 7822b3336ee022b64edd66695375bd06dfc8586a52450128c0a3cd0d9cb4b857 236435 
python-gmpy2_2.1.0~a4.orig.tar.gz
 cf2597dd5bac1faaef66b186aebe356539348ba4291088f7dafca5d82478559b 4552 
python-gmpy2_2.1.0~a4-1.debian.tar.xz
 c3ae55285f6b2d0ef2c7ad77c5dfd3bfaaa7b181b06dc53240a31e4023309226 30464 
python-gmpy2-common_2.1.0~a4-1_all.deb
 e009c5cdc61da775f58b5dfbfe2106a930e0b7a93f40b7baa8a3cbde4aa6d210 3

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Felipe Sateler]

On Wed, Jan 30, 2019 at 7:47 PM Axel Beckert  wrote:

> Hi Felipe,
>
> a short reply with that information I can gather without much effort:
>
> Felipe Sateler wrote:
> > > But we also had reports where this happend
> > > with systemd, so this doesn't seem to be depend on the init system (at
> > > most at the init system's default features) and hence also the package
> > > cgroupfs-mount can't be held guilty for this.
> >
> > Can you point me at one? (sorry, I'm late to this bug and currently
> ENOTIME
> > to read the entire backlog). It seems this should not happen on systemd
> > systems, because systemd properly isolates udev to its own cgroup when
> > starting.
>
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918764#122


Ah, thanks. That example is running with systemd as pid1, but not running
udev as a systemd-managed daemon. This is good, because it means the
diagnosis has not been refuted.

-- 

Saludos,
Felipe Sateler

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Axel Beckert]

Hi Felipe,

a short reply with that information I can gather without much effort:

Felipe Sateler wrote:
> > But we also had reports where this happend
> > with systemd, so this doesn't seem to be depend on the init system (at
> > most at the init system's default features) and hence also the package
> > cgroupfs-mount can't be held guilty for this.
> 
> Can you point me at one? (sorry, I'm late to this bug and currently ENOTIME
> to read the entire backlog). It seems this should not happen on systemd
> systems, because systemd properly isolates udev to its own cgroup when
> starting.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918764#122

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#920858: [Pkg-javascript-devel] Bug#920858: twitter-bootstrap4: contains generated code not included as source

[Jonas Smedegaard]

Quoting Xavier (2019-01-30 22:54:53)
> Le 30/01/2019 à 22:34, Jonas Smedegaard a écrit :
> > Quoting Xavier (2019-01-30 22:26:57)
> >> Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
> >>> Source package contains below  several files embedding code 
> >>> from external project fileOverview Kickass, without source 
> >>> included.

Just a clarification: Name of external project is Popper.js: 
"fileOverview" is just a marker, and "Kickass" is first word of 
Popper.js short description.


> >> I succeed to build source, but this needs:
> > [snip]
> > 
> > This bugreport tracks twitter-bootstrap4 violating Policy in 
> > shipping code without source.
> > 
> > For discussing packaging of that source in a separate package, 
> > please file an ITP bugreport (or an RFP bugreport if you don't 
> > intent on doing the work yourself), and let's discuss packaging 
> > issues there.

> Also is it OK if I remove dist/bootstrap.bundle.* in Files-Excluded ?

Sorry, I don't understand your question.

What do you mean by "also"?  Did I miss some previous conversation that 
this is an addition of?

Are you asking if it is ok to violate Debian Policy here?  Or is your 
question a different one? Please try rephrase...


> Note that "fileOverview Kickass" is provided by popper.js

It seems it _is_ Popper.js - see above.


 - Jonas

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

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


signature.asc
Description: signature

Processed: block 920876 with 907297

[Debian Bug Tracking System]

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

> block 920876 with 907297
Bug #920876 [xfce4-notes] xfce4-notes: Not functioning
920876 was not blocked by any bugs.
920876 was not blocking any bugs.
Added blocking bug(s) of 920876: 907297
> thanks
Stopping processing here.

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

Bug#920941: marked as done (libvncserver: CVE-2018-20748 CVE-2018-20749 CVE-2018-20750)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 22:04:35 +
with message-id 
and subject line Bug#920941: fixed in libvncserver 0.9.11+dfsg-1.3
has caused the Debian Bug report #920941,
regarding libvncserver: CVE-2018-20748 CVE-2018-20749 CVE-2018-20750
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.)


-- 
920941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvncserver
Version: 0.9.11+dfsg-1.2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for libvncserver, stretch
is not affected by those CVEs as no inocomplete fix was ever applied
there yet in a released version. When issuing the DSA we should make
sure to include the complete fixes for CVE-2018-20019 and
CVE-2018-15127. Details in [3].

CVE-2018-20748[0]:
Incomplete fix for CVE-2018-20019

CVE-2018-20749[1]:
Incomplete fix for CVE-2018-15127

CVE-2018-20750[2]:
Incomplete fix for CVE-2018-15127

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-20748
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20748
[1] https://security-tracker.debian.org/tracker/CVE-2018-20749
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20749
[2] https://security-tracker.debian.org/tracker/CVE-2018-20750
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20750
[3] https://github.com/LibVNC/libvncserver/issues/273#issuecomment-459040241

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libvncserver
Source-Version: 0.9.11+dfsg-1.3

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libvncserver 
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, 30 Jan 2019 22:39:15 +0100
Source: libvncserver
Binary: libvncclient1 libvncclient1-dbg libvncserver-config libvncserver-dev 
libvncserver1 libvncserver1-dbg
Architecture: source
Version: 0.9.11+dfsg-1.3
Distribution: unstable
Urgency: medium
Maintainer: Peter Spiess-Knafl 
Changed-By: Salvatore Bonaccorso 
Closes: 920941
Description: 
 libvncclient1 - API to write one's own VNC server - client library
 libvncclient1-dbg - debugging symbols for libvncclient
 libvncserver-config - API to write one's own VNC server - library utility
 libvncserver-dev - API to write one's own VNC server - development files
 libvncserver1 - API to write one's own VNC server
 libvncserver1-dbg - debugging symbols for libvncserver
Changes:
 libvncserver (0.9.11+dfsg-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * LibVNCClient: ignore server-sent cut text longer than 1MB (CVE-2018-20748)
 (Closes: #920941)
   * LibVNCClient: ignore server-sent reason strings longer than 1MB
 (CVE-2018-20748) (Closes: #920941)
   * LibVNCClient: fail on server-sent desktop name lengths longer than 1MB
 (CVE-2018-20748) (Closes: #920941)
   * LibVNCClient: remove now-useless cast (CVE-2018-20748) (Closes: #920941)
   * Error out in rfbProcessFileTransferReadBuffer if length can not be
 allocated (CVE-2018-20749) (Closes: #920941)
   * Limit lenght to INT_MAX bytes in rfbProcessFileTransferReadBuffer()
 (CVE-2018-20750) (Closes: #920941)
Checksums-Sha1: 
 1283eac81fef47ad3c3459d2ca21aa66eacbbe92 2561 libvncserver_0.9.11+dfsg-1.3.dsc
 00a01dbd9737965ad9d3e045a241c5712ab15ece 21212 
libvncserver_0.9.11+dfsg-1.3.debian.tar.xz
Checksums-Sha256: 
 f3f01f4d3e5dbc6eae9b067c5972de27b027f4457c5fb62b9bf9bd4c078479fb 2561 
libvncserver_0.9.11+dfsg-1.3.dsc
 fcbb00848a548f15e151b293639cd1576591d894b7101682c659f36cf78e8bf7 21212 
libvncserver_0.9.11+dfsg-1.3.debian.tar.xz
Files: 
 8f6fae2c32e0b79d54fb4ccd40b7bea0 2561 libs optional 
libvncserver_0.9.11+dfsg-1.3.dsc
 b6cc75c50051e2efd0d4620cd9f2d5a9 21212 libs 

Processed: libvncserver: diff for NMU version 0.9.11+dfsg-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 920941 + patch
Bug #920941 [src:libvncserver] libvncserver: CVE-2018-20748 CVE-2018-20749 
CVE-2018-20750
Added tag(s) patch.

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

Bug#920941: libvncserver: diff for NMU version 0.9.11+dfsg-1.3

[Salvatore Bonaccorso]

Control: tags 920941 + patch

Hi Peter,

I've prepared an NMU for libvncserver (versioned as 0.9.11+dfsg-1.3). The diff
is attached to this message. I did upload this time without delay
given the fixes were needed from the previous fixes (incomplete fixes
for CVEs).

I have pushed as well the changes to the packaging repository on
salsa.

it is a bit short on time, but it might maybe possible to still upload
new upstream version in time for buster?

Regards,
Salvatore
diff -Nru libvncserver-0.9.11+dfsg/debian/changelog libvncserver-0.9.11+dfsg/debian/changelog
--- libvncserver-0.9.11+dfsg/debian/changelog	2019-01-02 16:26:53.0 +0100
+++ libvncserver-0.9.11+dfsg/debian/changelog	2019-01-30 22:39:15.0 +0100
@@ -1,3 +1,20 @@
+libvncserver (0.9.11+dfsg-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * LibVNCClient: ignore server-sent cut text longer than 1MB (CVE-2018-20748)
+(Closes: #920941)
+  * LibVNCClient: ignore server-sent reason strings longer than 1MB
+(CVE-2018-20748) (Closes: #920941)
+  * LibVNCClient: fail on server-sent desktop name lengths longer than 1MB
+(CVE-2018-20748) (Closes: #920941)
+  * LibVNCClient: remove now-useless cast (CVE-2018-20748) (Closes: #920941)
+  * Error out in rfbProcessFileTransferReadBuffer if length can not be
+allocated (CVE-2018-20749) (Closes: #920941)
+  * Limit lenght to INT_MAX bytes in rfbProcessFileTransferReadBuffer()
+(CVE-2018-20750) (Closes: #920941)
+
+ -- Salvatore Bonaccorso   Wed, 30 Jan 2019 22:39:15 +0100
+
 libvncserver (0.9.11+dfsg-1.2) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0001-LibVNCClient-ignore-server-sent-cut-text-longer-than.patch libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0001-LibVNCClient-ignore-server-sent-cut-text-longer-than.patch
--- libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0001-LibVNCClient-ignore-server-sent-cut-text-longer-than.patch	1970-01-01 01:00:00.0 +0100
+++ libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0001-LibVNCClient-ignore-server-sent-cut-text-longer-than.patch	2019-01-30 22:39:15.0 +0100
@@ -0,0 +1,32 @@
+From: Christian Beier 
+Date: Sat, 29 Dec 2018 14:16:58 +0100
+Subject: LibVNCClient: ignore server-sent cut text longer than 1MB
+Origin: https://github.com/LibVNC/libvncserver/commit/c5ba3fee85a7ecbbca1df5ffd46d32b92757bc2a
+Bug-Debian: https://bugs.debian.org/920941
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-20748
+
+This is in line with how LibVNCServer does it
+(28afb6c537dc82ba04d5f245b15ca7205c6dbb9c) and fixes part of #273.
+---
+ libvncclient/rfbproto.c | 5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/libvncclient/rfbproto.c b/libvncclient/rfbproto.c
+index 4541e0d53ad3..8792dbf67c48 100644
+--- a/libvncclient/rfbproto.c
 b/libvncclient/rfbproto.c
+@@ -2217,6 +2217,11 @@ HandleRFBServerMessage(rfbClient* client)
+ 
+ msg.sct.length = rfbClientSwap32IfLE(msg.sct.length);
+ 
++if (msg.sct.length > 1<<20) {
++	rfbClientErr("Ignoring too big cut text length sent by server: %u B > 1 MB\n", (unsigned int)msg.sct.length);
++	return FALSE;
++}  
++
+ buffer = malloc((uint64_t)msg.sct.length+1);
+ 
+ if (!ReadFromRFBServer(client, buffer, msg.sct.length)) {
+-- 
+2.20.1
+
diff -Nru libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0002-LibVNCClient-ignore-server-sent-reason-strings-longe.patch libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0002-LibVNCClient-ignore-server-sent-reason-strings-longe.patch
--- libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0002-LibVNCClient-ignore-server-sent-reason-strings-longe.patch	1970-01-01 01:00:00.0 +0100
+++ libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-20748/0002-LibVNCClient-ignore-server-sent-reason-strings-longe.patch	2019-01-30 22:39:15.0 +0100
@@ -0,0 +1,88 @@
+From: Christian Beier 
+Date: Sat, 29 Dec 2018 14:40:53 +0100
+Subject: LibVNCClient: ignore server-sent reason strings longer than 1MB
+Origin: https://github.com/LibVNC/libvncserver/commit/e34bcbb759ca5bef85809967a268fdf214c1ad2c
+Bug-Debian: https://bugs.debian.org/920941
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-20748
+
+Fixes #273
+---
+ libvncclient/rfbproto.c | 45 +++--
+ 1 file changed, 21 insertions(+), 24 deletions(-)
+
+diff --git a/libvncclient/rfbproto.c b/libvncclient/rfbproto.c
+index 8792dbf67c48..ba7d70a71575 100644
+--- a/libvncclient/rfbproto.c
 b/libvncclient/rfbproto.c
+@@ -412,11 +412,29 @@ rfbBool ConnectToRFBRepeater(rfbClient* client,const char *repeaterHost, int rep
+ extern void rfbClientEncryptBytes(unsigned char* bytes, char* passwd);
+ extern void rfbClientEncryptBytes2(unsigned char *where, const int length, unsigned char *key);
+ 
++static void
++ReadReason(rfbClient* client)
++{
++uint32_t reasonLen;
++char *reason

Bug#920858: [Pkg-javascript-devel] Bug#920858: twitter-bootstrap4: contains generated code not included as source

[Xavier]

Le 30/01/2019 à 22:34, Jonas Smedegaard a écrit :
> Quoting Xavier (2019-01-30 22:26:57)
>> Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
>>> Source: twitter-bootstrap4
>>> Version: 4.2.1+dfsg1-1
>>> Severity: serious
>>> Justification: Policy 2.1
>>>
>>> Source package contains below  several files embedding code from
>>> external project fileOverview Kickass, without source included.
>>>
>>> Thanks to Xavier for noticing (although only as comment in copyright
>>> file).
>>>
>>>
>>>  - Jonas
>>
>> I succeed to build source, but this needs:
> [snip]
> 
> This bugreport tracks twitter-bootstrap4 violating Policy in shipping 
> code without source.
> 
> For discussing packaging of that source in a separate package, please 
> file an ITP bugreport (or an RFP bugreport if you don't intent on doing 
> the work yourself), and let's discuss packaging issues there.
> 
> 
>  - Jonas

Also is it OK if I remove dist/bootstrap.bundle.* in Files-Excluded ?

Note that "fileOverview Kickass" is provided by popper.js

Bug#920858: [Pkg-javascript-devel] Bug#920858: twitter-bootstrap4: contains generated code not included as source

[Jonas Smedegaard]

Quoting Xavier (2019-01-30 22:26:57)
> Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
> > Source: twitter-bootstrap4
> > Version: 4.2.1+dfsg1-1
> > Severity: serious
> > Justification: Policy 2.1
> > 
> > Source package contains below  several files embedding code from
> > external project fileOverview Kickass, without source included.
> > 
> > Thanks to Xavier for noticing (although only as comment in copyright
> > file).
> > 
> > 
> >  - Jonas
> 
> I succeed to build source, but this needs:
[snip]

This bugreport tracks twitter-bootstrap4 violating Policy in shipping 
code without source.

For discussing packaging of that source in a separate package, please 
file an ITP bugreport (or an RFP bugreport if you don't intent on doing 
the work yourself), and let's discuss packaging issues there.


 - Jonas

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

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


signature.asc
Description: signature

Bug#920858: [Pkg-javascript-devel] Bug#920858: twitter-bootstrap4: contains generated code not included as source

[Xavier]

Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
> Source: twitter-bootstrap4
> Version: 4.2.1+dfsg1-1
> Severity: serious
> Justification: Policy 2.1
> 
> Source package contains below  several files embedding code from
> external project fileOverview Kickass, without source included.
> 
> Thanks to Xavier for noticing (although only as comment in copyright
> file).
> 
> 
>  - Jonas

I succeed to build source, but this needs:
 - to upgrade: rollup-plugin-babel, browserslist
 - to package or upgrade at least (I reduced this list to the minimum
possible): node-releases, rollup-plugin-babel, trim-right, @babel/core
@babel/generator @babel/helper-annotate-as-pure
@babel/helper-builder-binary-assignment-operator-visitor
@babel/helper-call-delegate @babel/helper-define-map
@babel/helper-explode-assignable-expression @babel/helper-function-name
@babel/helper-get-function-arity @babel/helper-hoist-variables
@babel/helper-member-expression-to-functions
@babel/helper-module-imports @babel/helper-module-transforms
@babel/helper-optimise-call-expression @babel/helper-plugin-utils
@babel/helper-regex @babel/helper-remap-async-to-generator
@babel/helper-replace-supers @babel/helpers @babel/helper-simple-access
@babel/helper-split-export-declaration @babel/helper-wrap-function
@babel/highlight @babel/parser
@babel/plugin-proposal-async-generator-functions
@babel/plugin-proposal-json-strings
@babel/plugin-proposal-object-rest-spread
@babel/plugin-proposal-optional-catch-binding
@babel/plugin-proposal-unicode-property-regex
@babel/plugin-syntax-async-generators @babel/plugin-syntax-json-strings
@babel/plugin-syntax-object-rest-spread
@babel/plugin-syntax-optional-catch-binding
@babel/plugin-transform-arrow-functions
@babel/plugin-transform-async-to-generator
@babel/plugin-transform-block-scoped-functions
@babel/plugin-transform-block-scoping @babel/plugin-transform-classes
@babel/plugin-transform-computed-properties
@babel/plugin-transform-destructuring
@babel/plugin-transform-dotall-regex
@babel/plugin-transform-duplicate-keys
@babel/plugin-transform-exponentiation-operator
@babel/plugin-transform-for-of @babel/plugin-transform-function-name
@babel/plugin-transform-literals @babel/plugin-transform-modules-amd
@babel/plugin-transform-modules-commonjs
@babel/plugin-transform-modules-systemjs
@babel/plugin-transform-modules-umd @babel/plugin-transform-new-target
@babel/plugin-transform-object-super @babel/plugin-transform-parameters
@babel/plugin-transform-regenerator
@babel/plugin-transform-shorthand-properties
@babel/plugin-transform-spread @babel/plugin-transform-sticky-regex
@babel/plugin-transform-template-literals
@babel/plugin-transform-typeof-symbol
@babel/plugin-transform-unicode-regex @babel/preset-env @babel/template
@babel/traverse @babel/types

However, generated code is readable, not minified and contains some
comments, perhaps not enough. So I think it's not a significant DFSG break.

I won't package all of them so if we consider than using generated
dist/* files is a policy break, I think that twitter-bootstrap4 can't be
released in buster.

Another crazy alternative: embeds that (4,8 Mo) ! I won't do it.

Bug#907297: breeze-gtk-theme: Breaks xfce4-notes (invalid string constant in "/usr/share/themes/Breeze/gtk-2.0/widgets/styles")

[Maximiliano Curia]

Control: severity -1 normal
Control: tag -1 + unreproducible

¡Hola Dmitry!

El 2018-08-26 a las 15:53 +1000, Dmitry Smirnov escribió:

Package: breeze-gtk-theme
Version: 5.13.4-1
Severity: normal
Control: affects -1 xfce4-notes



breeze-gtk-theme breaks xfce4-notes:




$ xfce4-notes
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:7: error: invalid string constant 
"notebook", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:2: error: invalid string constant 
"scrollbar", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:4: error: invalid string constant 
"entry", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:4: error: invalid string constant 
"entry", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:1: error: invalid string constant 
"default", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:1: error: invalid string constant 
"default", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:8: error: invalid string constant 
"range", expected valid string constant
^C




I could only use xfce4-notes after uninstalling "breeze-gtk-theme"...


I couldn't reproduce the issue, executing xfce4-notes shows no errors in the 
termianl and it seems to be working fine, this of course, while using the 
breeze theme.


Thus setting the severity back to normal, and tagging the issue as 
unreproducible. Is there anything special about your setup that could somehow 
caused that the other files in /usr/share/themes/Breeze/gtk-2.0/widgets/ 
directory could not be loaded? A limit on the number of open files, perhaps?


Happy hacking,
--
"Brilliant opportunities are cleverly disguised as insolvable problems."
-- Gardener's Philosophy

"The reverse is also true." -- Corollary
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: Re: Bug#907297: breeze-gtk-theme: Breaks xfce4-notes (invalid string constant in "/usr/share/themes/Breeze/gtk-2.0/widgets/styles")

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #907297 [breeze-gtk-theme] breeze-gtk-theme: Breaks xfce4-notes (invalid 
string constant in "/usr/share/themes/Breeze/gtk-2.0/widgets/styles")
Severity set to 'normal' from 'serious'
> tag -1 + unreproducible
Bug #907297 [breeze-gtk-theme] breeze-gtk-theme: Breaks xfce4-notes (invalid 
string constant in "/usr/share/themes/Breeze/gtk-2.0/widgets/styles")
Added tag(s) unreproducible.

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

Bug#920927: [Pkg-zfsonlinux-devel] Bug#920927: zfs-dkms: module FTBFS for i386 kernel

[Andreas Beckmann]

On 2019-01-30 20:12, Petter Reinholdtsen wrote:
> 
> [Andreas Beckmann]
>> zfs-dkms does not build a kernel module for e.g. the 4.19.0-2-686 i386
>> kernel. This happened in a i386 chroot on a amd64 host, but this should
>> not really be a problem, since this setup works fine for other
>> packages.
> 
> Are you sure this isn't intentional?  It is strongly recommended not to
> use ZFS on 32 bit architectures, if I recall correctly.

"intentional" would have been to fail with a clear error message during
the configure step (optionally recommending an override option), not
after successfully compiling tons of source files to fail in some crypto
code with a dubious error message:
  #error Assembler code is only available for x86 and AMD64 systems
I didn't even try it on a non-x86 platform :-)

This looks rather like completely "untested".


Andreas

Bug#920762: marked as done (spice: CVE-2019-3813: Off-by-one error in array access in spice/server/memslot.c)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 21:05:00 +
with message-id 
and subject line Bug#920762: fixed in spice 0.14.0-1.3
has caused the Debian Bug report #920762,
regarding spice: CVE-2019-3813: Off-by-one error in array access in 
spice/server/memslot.c
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.)


-- 
920762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spice
Version: 0.14.0-1.2
Severity: grave
Tags: security upstream
Control: found -1 0.12.8-2.1+deb9u2
Control: found -1 0.12.8-2.1
Control: fixed -1 0.12.8-2.1+deb9u3

Hi,

The following vulnerability was published for spice.

CVE-2019-3813[0]:
Off-by-one error in array access in spice/server/memslot.c

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-2019-3813
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3813
[1] https://www.openwall.com/lists/oss-security/2019/01/28/2

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: spice
Source-Version: 0.14.0-1.3

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated spice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Jan 2019 13:04:44 +0100
Source: spice
Binary: libspice-server-dev libspice-server1 libspice-server1-dbgsym
Architecture: source
Version: 0.14.0-1.3
Distribution: unstable
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Salvatore Bonaccorso 
Closes: 920762
Description: 
 libspice-server-dev - Header files and development documentation for 
spice-server
 libspice-server1 - Implements the server side of the SPICE protocol
Changes:
 spice (0.14.0-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * memslot: Fix off-by-one error in group/slot boundary check (CVE-2019-3813)
 (Closes: #920762)
Checksums-Sha1: 
 df63aa51c7effe26d46a1ca019e0820279cdb8fc 2810 spice_0.14.0-1.3.dsc
 bcb74fbe6526135af0cbb6118712cc9c301f56bd 20036 spice_0.14.0-1.3.debian.tar.xz
Checksums-Sha256: 
 7b1cc9ea00c8eb21ea1b72bd5fc45e3c6f5735a147bcfa95d1882ed7dbe7c403 2810 
spice_0.14.0-1.3.dsc
 5ebffa2e91b0a155e4a7389f874761181eb61c6af0c51137c92f11ac7b54170b 20036 
spice_0.14.0-1.3.debian.tar.xz
Files: 
 71094a47fb030c92d7caa563e3b87c92 2810 misc optional spice_0.14.0-1.3.dsc
 39416f9bc1eda7e30e8fcd9f73ee87ae 20036 misc optional 
spice_0.14.0-1.3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxPZ5lfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EqWMP/jlRXB2J97r0FtU39HZ5UT0UDDaja+gx
sDNU0LAzQdCObY3tiH0TtduVjYY36mUhRdGt7cX58B+0dafH00aZ7OZ4qY4PeLOL
VYpkmkE39U8glICaVJXmW+nRvGAgLw0SfZ0O4QWSP+RvIu8VPLyfxDyyGJi2abp9
vFLohy6cBzSHBkq0VKnJLq2eluypD7xbKlHcqhkgXnklQRJhBA8GQ6YvMjpFGiOV
XVmr5R8K3G+Vpgc++Q1Lq1tEw3pHxribnthjzyJrxq/wki4wyx1z1LYM+7t+jMA/
iQs6UlMAnrc1ynjxRKB7VfzbIwnuBFVhZSE3PVdRFRMIfzEqqW1pTm7+nxTekRGU
WIw1I4v+4l7vk2kN8OKkUFw0z8Wr/W8WuB0T/iK86K72WAayycU/1LWvPp+WvCaG
WAV2O/v8+eQmc0YUGcyxPa8gcPQtOcylFGlI89vgEOmGpQ50zVZgtBfqMfC0+bd6
j4A7EtqWHoHwXLd2ArGfS7duPIhlW8070J+v4ckybL9D2/qJipmBFWmiXAbyZBh+
euspJ8vLARmbP7g3Qm4buqbzQUMgHudSmm34dUYD1L5AapWeFRyP4U5zz0SBqIgO
zzC5jlD9NOZLTDoHDaOmrE5pN/DrgzzjDA8EAVCoLlymVB6sST3dYWb9MbcgayJx
b160kFnAjw4G
=u0LA
-END PGP SIGNATURE End Message ---

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Felipe Sateler]

On Tue, Jan 29, 2019 at 9:39 PM Axel Beckert  wrote:

>
> Then I uninstalled not all of them at once but each of them one by
> one. And the one after whose purging
>
> # service udev restart
> # udevadm control --reload-rules
>
> didn't kill my processes anymore was cgroupfs-mount.
>
> So for some reason this killing only seems to happen on my box if
> cgroupfs-mount is installed. Then again, this is only necessary if
> systemd is not installed.


Thanks everyone for the detailed debugging. This appears to be the culprit:
udev tries to detect if running under systemd, and if so will kill its
entire cgroup (to cleanup leftover processes). Looks like cgroupfs-mount is
fooling udev into thinking it is running under systemd.

Could someone attach gdb to udev, break on the function `on_post`, trigger
the bug, and report what does `manager->cgroup` contain?



> But we also had reports where this happend
> with systemd, so this doesn't seem to be depend on the init system (at
> most at the init system's default features) and hence also the package
> cgroupfs-mount can't be held guilty for this.
>

Can you point me at one? (sorry, I'm late to this bug and currently ENOTIME
to read the entire backlog). It seems this should not happen on systemd
systems, because systemd properly isolates udev to its own cgroup when
starting.


>
> Which IMHO again leaves either src:systemd or src:linux as rc-buggy
> package.
>

I think something like this might be sufficient to work around the bug in
sysvinit systems:

% git diff
diff --git a/src/udev/udevd.c b/src/udev/udevd.c
index fb8724ea87..a03b65a773 100644
--- a/src/udev/udevd.c
+++ b/src/udev/udevd.c
@@ -1814,7 +1814,7 @@ static int run(int argc, char *argv[]) {

 dev_setup(NULL, UID_INVALID, GID_INVALID);

-if (getppid() == 1) {
+if (getppid() == 1 && sd_booted()) {
 /* get our own cgroup, we regularly kill everything udev
has left behind
we only do this on systemd systems, and only if we are
directly spawned
by PID1. otherwise we are not guaranteed to have a
dedicated cgroup */


-- 

Saludos,
Felipe Sateler

Bug#919901: marked as done (corosync-qnetd: fails to upgrade from 'stretch': certutil: Could not set password for the slot)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 21:04:22 +
with message-id 
and subject line Bug#919901: fixed in corosync-qdevice 3.0.0-2
has caused the Debian Bug report #919901,
regarding corosync-qnetd: fails to upgrade from 'stretch': certutil: Could not 
set password for the slot
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up corosync-qnetd (3.0.0-1) ...
  password file contains no data
  Invalid password.
  certutil: Could not set password for the slot: SEC_ERROR_INVALID_ARGS: 
security library: invalid arguments.
  dpkg: error processing package corosync-qnetd (--configure):
   installed corosync-qnetd package post-installation script subprocess 
returned error exit status 255
  Processing triggers for libc-bin (2.28-5) ...
  Errors were encountered while processing:
   corosync-qnetd


cheers,

Andreas


corosync-qnetd_3.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: corosync-qdevice
Source-Version: 3.0.0-2

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated corosync-qdevice 
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, 30 Jan 2019 21:34:53 +0100
Source: corosync-qdevice
Binary: corosync-qdevice corosync-qnetd
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 corosync-qdevice - cluster engine quorum device daemon
 corosync-qnetd - cluster engine quorum device network daemon
Closes: 919901
Changes:
 corosync-qdevice (3.0.0-2) unstable; urgency=medium
 .
   * [ee08d93] Fix cert database upgrade (Closes: #919901)
   * [631309b] Add autopkgtests
   * [d03ebb2] Add myself to Uploaders
Checksums-Sha1:
 98fb160da1631dbc3014308a332579b54ffac012 2275 corosync-qdevice_3.0.0-2.dsc
 84e56b26d064848866cf876348e532622d0dce17 9200 
corosync-qdevice_3.0.0-2.debian.tar.xz
 a7a8cbf90bd6394af5f48f85179e526ccb89c660 5993 
corosync-qdevice_3.0.0-2_source.buildinfo
Checksums-Sha256:
 2fd960b152585805bf000e0fa21b248879d07538408ac76a87381b0d8d007fc0 2275 
corosync-qdevice_3.0.0-2.dsc
 002e294e81b33aa99b63e2eb6e980edc9d1f7c198a04707582488fcaf84078d8 9200 
corosync-qdevice_3.0.0-2.debian.tar.xz
 8a57647c16ab4bbcb33c7a4371b8f9fabc520e51758893131e35f533650c60ae 5993 
corosync-qdevice_3.0.0-2_source.buildinfo
Files:
 eb9388abc450722ffb3220d58ba8816a 2275 admin optional 
corosync-qdevice_3.0.0-2.dsc
 34e2c45a148275653f4bbae655a2705c 9200 admin optional 
corosync-qdevice_3.0.0-2.debian.tar.xz
 40e0e29ddbc73ea03b96619a5f56c6bf 5993 admin optional 
corosync-qdevice_3.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExaW53cM9k/u2PWfIMofYmpfNqHsFAlxSDioSHHZ2aWRpY0Bk
ZWJpYW4ub3JnAAoJEDKH2JqXzah70Q8P/03g/qhSNqGlP2zczMXlcaXiooZ5aQF6
ygSLAErZsdkPeOJqugxYginrZBBef1zTCG+Ad9v0HtZWVjWExORTUvW1wSMr+q1N
0POZIFf0gmXyV2EJt0lZmYZ0u25pD2kmeROF9WKQ101bB5nh8VO708UoN3IRKYnn
mW575AA6r+hUmsxlmMSMJ0Qw44EYRziKKVz4kL7awAbrCOmzDNhthLjWv5viKIXO
y0LydpCKqbxzmvHVC/FbL+dBEF8bP7+sRarexs/osQtr9oyEVhGjIWDOuc//Dfwi
uW2cBniB4wgO0OYtLlJN6fk3QDzYxDn9IQ6hgG+2snmRphn+hSU64FV8+ONLkYSg
COc2KJFulyPBQiVEKUIFBCTI9rrp3UdNn6uJkpk+JUeUMCNl0Qlw1Xf6OjMzRtmL
T3/lpKB/CoNR4N3t7IUL3qVlweZAeYoV5QuCJAraDWlsY6/aEVtmAvRfnJ3a4mwl
A6qftHh9sK8N0P/ez6+2ktYJDWP+wFGQGLzPgeHP+EE3kSJcNCS16ULYZ7BJrwTJ
oPaSuW3io50gBaFCvAyUN0EWzHI5LrhiE/v+CaN1xYSQUX/jvfM7frYfJtchX0pC
FQ/+qUL/zLSHiwkDf6WZEA6U33teCkwdN1kWMI3OyStBRr+QmqP19lVesRqtNTGF
C+tzbQX85MZG
=DxQz
-END PGP SIGNATURE End Message ---

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Beniamino Galvani]

On Mon, Jan 28, 2019 at 10:36:16AM +0100, Andrej Shadura wrote:
> On Wed, 16 Jan 2019 at 21:51, Different55  wrote:
> >
> > Alright, not entirely sure if I did this right but I followed Debian's 
> > Building Tutorial to download and build wpa_supplicant with the changes you 
> > linked. One exception, I use wpa_supplicant through NetworkManager and 
> > could not work out where I needed to create a wpa_supplicant.conf, so I 
> > changed the one line in config.c to:
> >
> > { INT(no_oper_classes_ie), 1 },
> >
> > which I'm hoping makes the default "on" instead of "off." Sadly doesn't 
> > appear to have made a difference, although it didn't make anything worse 
> > either.
> >
> > Tiny mostly-uninteresting side note, I gave wpa_supplicant 2.7 a try on my 
> > desktop this morning and had the same problems with a Qualcomm Atheros 
> > AR9462 Wireless Adapter.
> 
> Forwarding Different55’s message from the Debian bug here:
> 
> Sure thing! Sadly doesn't seem to make a difference. I've included
> another log, this time starting from the time wpa_supplicant was
> brought back up to a little bit after I got the popup that the
> connection had failed.

Hi,

> ...
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7273] 
> device (wls8): state change: need-auth -> prepare (reason 'none', 
> sys-iface-state: 'managed')
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7281] 
> device (wls8): state change: prepare -> config (reason 'none', 
> sys-iface-state: 'managed')
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7286] 
> device (wls8): Activation: (wifi) connection 'Depeche Modem' has security, 
> and secrets exist.  No new secrets needed.
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7286] 
> Config: added 'ssid' value 'Depeche Modem'
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7287] 
> Config: added 'scan_ssid' value '1'
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7287] 
> Config: added 'bgscan' value 'simple:30:-80:86400'
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7287] 
> Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7287] 
> Config: added 'psk' value ''

Here NetworkManager enables optional PMF:

> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7287] 
> Config: added 'ieee80211w' value '1'
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7841] 
> device (wls8): supplicant interface state: ready -> disconnected
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.7942] 
> device (wls8): supplicant interface state: disconnected -> inactive
> Jan 27 21:32:01 Empanada NetworkManager[582]:   [1548646321.8001] 
> device (wls8): supplicant interface state: inactive -> scanning
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: SME: Trying to 
> authenticate with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
> Jan 27 21:32:02 Empanada kernel: wls8: authenticate with xx:xx:xx:xx:xx:xx
> Jan 27 21:32:02 Empanada NetworkManager[582]:   [1548646322.8513] 
> device (wls8): supplicant interface state: scanning -> authenticating
> Jan 27 21:32:02 Empanada kernel: wls8: send auth to xx:xx:xx:xx:xx:xx (try 
> 1/3)
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: Trying to associate 
> with xx:xx:xx:xx:xx:xx (SSID='Depeche Modem' freq=2442 MHz)
> Jan 27 21:32:02 Empanada NetworkManager[582]:   [1548646322.8562] 
> device (wls8): supplicant interface state: authenticating -> associating
> Jan 27 21:32:02 Empanada kernel: wls8: authenticated
> Jan 27 21:32:02 Empanada kernel: wls8: associate with xx:xx:xx:xx:xx:xx (try 
> 1/3)
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: Associated with 
> xx:xx:xx:xx:xx:xx
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: 
> CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
> Jan 27 21:32:02 Empanada kernel: wls8: RX AssocResp from xx:xx:xx:xx:xx:xx 
> (capab=0x411 status=0 aid=6)
> Jan 27 21:32:02 Empanada kernel: wls8: associated
> Jan 27 21:32:02 Empanada NetworkManager[582]:   [1548646322.8693] 
> device (wls8): supplicant interface state: associating -> associated
> Jan 27 21:32:02 Empanada NetworkManager[582]:   [1548646322.8756] 
> device (wls8): supplicant interface state: associated -> 4-way handshake
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: WPA: Key negotiation 
> completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
> Jan 27 21:32:02 Empanada kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wls8: link 
> becomes ready
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: CTRL-EVENT-CONNECTED - 
> Connection to xx:xx:xx:xx:xx:xx completed [id=0 id_str=]
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: WPA: Failed to 
> configure IGTK to the driver
> Jan 27 21:32:02 Empanada wpa_supplicant[10450]: wls8: RSN: Failed to 
> configure IGTK

Could you please configure a more verbose debug level and paste the
lines related 

Processed: Re: Bug#920834: mlucas: FTBFS on i386

[Debian Bug Tracking System]

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

> # I am changing the title since I think the i386 baseline is in fact not
> # violated.
> retitle 920834 mlucas: FTBFS on i386
Bug #920834 [src:mlucas] mlucas: FTBFS and baseline vioiation on i386
Changed Bug title to 'mlucas: FTBFS on i386' from 'mlucas: FTBFS and baseline 
vioiation on i386'.
> thanks
Stopping processing here.

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

Bug#920954: ptunnel-ng: Incomplete debian/copyright?

[Chris Lamb]

Source: ptunnel-ng
Version: 1.32-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Thorsten Alteholz , 
ftpmas...@debian.org

Hi,

I just ACCEPTed ptunnel-ng from NEW but noticed it was missing 
attribution in debian/copyright for at least src/win32/*.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. Thanks!


Regards,

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

Bug#920953: ruby-haml-rails FTBFS: invalid byte sequence in US-ASCII (ArgumentError)

[Adrian Bunk]

Source: ruby-haml-rails
Version: 1.0.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-haml-rails&arch=all&ver=1.0.0-1&stamp=1548295203&raw=0

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

Invalid gemspec in [haml-rails.gemspec]: No such file or directory - git
/usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:145:in `gsub!': invalid byte 
sequence in US-ASCII (ArgumentError)
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:145:in `block in 
load_modified_gemspec'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:144:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:144:in 
`load_modified_gemspec'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:121:in `load_gemspec'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:34:in `block in 
initialize'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `initialize'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in `new'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in 
`do_check_dependencies'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:67:in `run_tests'
from /usr/bin/gem2deb-test-runner:61:in `'
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-haml-rails 
returned exit code 1
make: *** [debian/rules:18: binary-indep] Error 1

Bug#892656: marked as done (node-define-property: FTBFS and Debci failure)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 20:44:53 +
with message-id 
and subject line Bug#892656: fixed in node-define-property 2.0.2-1
has caused the Debian Bug report #892656,
regarding node-define-property: FTBFS and Debci failure
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.)


-- 
892656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-define-property
Version: 1.0.0-1
Severity: serious

Some recent change in unstable makes node-define-property FTBFS and Debci fail:

https://ci.debian.net/packages/n/node-define-property/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-define-property.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-define-property.html

...
  3 passing (13ms)
  1 failing

  1) define
   should define a property with accessor descriptors::

  AssertionError [ERR_ASSERTION]: 'bar' == 'baz'
  + expected - actual

  -bar
  +baz
  
  at Context. (test.js:40:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:7: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-define-property
Source-Version: 2.0.2-1

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

Debian distribution maintenance software
pp.
Paolo Greppi  (supplier of updated node-define-property 
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, 30 Jan 2019 19:12:59 +0100
Source: node-define-property
Binary: node-define-property
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paolo Greppi 
Closes: 892656
Description: 
 node-define-property - Define property on an object
Changes:
 node-define-property (2.0.2-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * Embed is-accessor-descriptor 1.0.0, is-data-descriptor 1.0.0 and
 is-descriptor 1.0.2 instead of relying on packaged versions.
 Closes: #892656
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Update packaging:
 - Bump dh compat to 11
 - Bump std-ver to 4.3.0
 - Fix nodejs binary
Checksums-Sha1: 
 5981fdd9a6af11bc086d83aa0e8002dc4bd874e6 3163 node-define-property_2.0.2-1.dsc
 169c2f6d3df1f992618072365c9b0ea1f6878656 3250 
node-define-property_2.0.2.orig-is-accessor-descriptor.tar.gz
 d84876321d0e7add03990406ad36ba9268c7 3230 
node-define-property_2.0.2.orig-is-data-descriptor.tar.gz
 3b159746a66604b04f8c81524ba365c5f14d86ec 2995 
node-define-property_2.0.2.orig-is-descriptor.tar.gz
 54b4eb9b2347af39f38fb7d7a22a105b206c90a4 6567 
node-define-property_2.0.2.orig.tar.gz
 12d9ee4a2ecef82762fcf2b5e8da4739c370a63d 2944 
node-define-property_2.0.2-1.debian.tar.xz
Checksums-Sha256: 
 11a072c32544ac5d665db3def4ff10690f55d3a3c0d876a6ee43d1912d273d1d 3163 
node-define-property_2.0.2-1.dsc
 14f7ea5a61dbaf00843ea03e55f20e3daf0db2bf1efe8aee3bde60d080a6cba3 3250 
node-define-property_2.0.2.orig-is-accessor-descriptor.tar.gz
 28c25461e29798d16795eadabe11cc5ced4904f9ca1761bc0463e403759ca12c 3230 
node-define-property_2.0.2.orig-is-data-descriptor.tar.gz
 fe5ee7a359c2ae4ec7c12a075d903150c23365bf55c0c471b8d34fade96c6ead 2995 
node-define-property_2.0.2.orig-is-descriptor.tar.gz
 6c0ddbccfd175e7496506c7e5473bce47614e17c6c859563eef797a6e567c1ec 6567 
node-define-property_2.0.2.orig.tar.gz
 9e622510cee736de20b2196d4a6d0c833cdfca148432fdae0c53daaa8fb841e3 2944 
node-define-property_2.0.2-1.debia

Bug#920934: marked as done (golang-golang-x-tools: /usr/bin/forward is already provided by the qmail package)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 20:43:07 +
with message-id 
and subject line Bug#920934: fixed in golang-golang-x-tools 
1:0.0~git20190125.d66bd3c+ds-4
has caused the Debian Bug report #920934,
regarding golang-golang-x-tools: /usr/bin/forward is already provided by the 
qmail package
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.)


-- 
920934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-golang-x-tools
Version: 1:0.0~git20190125.d66bd3c+ds-3
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package golang-golang-x-tools.

   Preparing to unpack 
.../golang-golang-x-tools_1%3a0.0~git20190125.d66bd3c+ds-3_amd64.deb ...

 Unpacking golang-golang-x-tools 
(1:0.0~git20190125.d66bd3c+ds-3) ...

 dpkg: error processing archive 
/var/cache/apt/archives/golang-golang-x-tools_1%3a0.0~git20190125.d66bd3c+ds-3_amd64.deb
 (--unpack):
   trying to overwrite '/usr/bin/forward', which is also in package 
qmail 1.06-6+b1 
   Errors were 
encountered while processing:   

  
/var/cache/apt/archives/golang-golang-x-tools_1%3a0.0~git20190125.d66bd3c+ds-3_amd64.deb

  

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/forward


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


qmail=1.06-6+b1_golang-golang-x-tools=1:0.0~git20190125.d66bd3c+ds-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-golang-x-tools
Source-Version: 1:0.0~git20190125.d66bd3c+ds-4

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-golang-x-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Jan 2019 20:18:31 +
Source: golang-golang-x-tools
Binary: golang-go.tools golang-go.tools-dev golang-golang-x-tools 
golang-golang-x-tools-dev
Architecture: source all amd64
Version: 1:0.0~git20190125.d66bd3c+ds-4
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packag

Bug#920834: mlucas: FTBFS on i386

[Alex Vong]

# I am changing the title since I think the i386 baseline is in fact not
# violated.

retitle 920834 mlucas: FTBFS on i386
thanks

Alex Vong  writes:

> Hello Adrian Bunk,
>
> I figure out what's the problem. There's a typo in upstream src:
>
> s/SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13/SSE2_RADIX16_CALC_TWIDDLES_1_2_4_8_13/g
>
> should fix the problem.
>
> I'll upload a new version to mentor, ask for sponsorship again and see
> how everything goes.
>
> Cheers,
> Alex
>
> Alex Vong  writes:
>
>> Dear Adrian Bunk,
>>
>> Regarding FTBFS, I've commented it at .
>>
>> Regarding baseline vioiation on i386, the autotool build system builds 2
>> versions of the binary: generic-c and SSE2, and install it to
>> libexecdir. Then the wrapper script selects the right binary at
>> run-time. Does this approach satifies the current policy?
>>
>> Cheers,
>> Alex
>>
>> Adrian Bunk  writes:
>>
>>> Source: mlucas
>>> Version: 17.1-1
>>> Severity: serious
>>> Tags: ftbfs
>>>
>>> https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0
>>>
>>> ...
>>> gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize
>>> -floop-nest-optimize -fomit-frame-pointer -g -g3
>>> -fstack-protector-strong -fstack-clash-protection -mmitigate-rop
>>> -fwrapv -m32 -msse2
>>> -fdebug-prefix-map=/<>=. -fstack-protector-strong
>>> -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o
>>> mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o
>>> src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o
>>> src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o
>>> src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o
>>> src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o
>>> src/mlucas_sse2-get_fp_rnd_const.o
>>> src/mlucas_sse2-get_preferred_fft_radix.o src/mlucas_sse2-imul_macro.o
>>> src/mlucas_sse2-mers_mod_square.o src/mlucas_sse2-mi64.o
>>> src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o
>>> src/mlucas_sse2-radix1008_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix1024_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix104_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix10_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix112_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix11_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix120_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix128_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix12_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix13_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix144_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix14_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix15_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix160_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix16_dif_dit_pass.o
>>> src/mlucas_sse2-radix16_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix16_dyadic_square.o
>>> src/mlucas_sse2-radix16_pairFFT_mul.o
>>> src/mlucas_sse2-radix16_wrapper_ini.o
>>> src/mlucas_sse2-radix16_wrapper_square.o
>>> src/mlucas_sse2-radix176_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix18_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix192_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix208_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix20_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix224_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix22_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix240_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix24_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix256_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix26_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix288_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix28_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix30_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix31_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix32_dif_dit_pass.o
>>> src/mlucas_sse2-radix32_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix32_dyadic_square.o
>>> src/mlucas_sse2-radix32_wrapper_ini.o
>>> src/mlucas_sse2-radix32_wrapper_square.o
>>> src/mlucas_sse2-radix36_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix4032_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix40_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix44_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix48_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix512_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix52_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix56_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix5_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix60_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix63_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix64_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix6_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix72_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix768_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix7_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix80_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix88_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix8_dif_dit_pass.o
>>> src/mlucas_sse2-radix8_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix960_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix96_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix992_ditN_cy_dif1.o
>>> src/mlucas_sse2-radix9_ditN_cy_dif1.o src/mlucas_sse2-rng_isaac.o
>>> src/mlucas_sse2-test_fft_radix.o src/mlucas_sse2-threadpool.o
>>> src/mlucas_sse2-twopmodq.o src/mlucas_sse2-twopmodq100.o
>>> src/mlucas_sse2-twopmodq128.o src/mlucas_sse2-twopmodq128_96.o
>>> src/mlucas_sse2-

Processed: Bug #916286 in traverso marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916286 [src:traverso] traverso: baseline violation on i386
Ignoring request to alter tags of bug #916286 to the same tags previously set

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

Bug#916286: Bug #916286 in traverso marked as pending

[Dmitry Eremin-Solenikov]

Control: tag -1 pending

Hello,

Bug #916286 in traverso 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/multimedia-team/traverso/commit/4c1f132b778c3f9197f66de5fd374c1913f2d948


d/rules: fix baseline CPU instructions violation

Closes: #916286
Signed-off-by: Dmitry Eremin-Solenikov 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916286

Bug#919555: Bug#919766: FTBFS-es

[Barak A. Pearlmutter]

Thanks, that was very kind of you. Much appreciated. I'm in the
process of preparing to upload.
But next time feel free to just NMU, 0 day, tell me after, I totally don't mind!
(This goes for any of my packages.)

Cheers,

--Barak.

Bug#920849: marked as done (libsbml5-dev: broken symlink: /usr/lib/libsbml.so -> libsbml.so.5)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 19:34:48 +
with message-id 
and subject line Bug#920849: fixed in libsbml 5.17.2+dfsg-3
has caused the Debian Bug report #920849,
regarding libsbml5-dev: broken symlink: /usr/lib/libsbml.so -> libsbml.so.5
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.)


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m27.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/libsbml.so -> libsbml.so.5 (libsbml5-dev)


Has the package been multiarchified recently?


cheers,

Andreas


libsbml5-dev_5.17.2+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.17.2+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libsbml 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, 30 Jan 2019 19:17:03 +0100
Source: libsbml
Architecture: source
Version: 5.17.2+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 920849
Changes:
 libsbml (5.17.2+dfsg-3) unstable; urgency=medium
 .
   * Fix link in development package
 Closes: #920849
Checksums-Sha1:
 a38fc941820cdb907177c42c8e55604dabe4e99e 2939 libsbml_5.17.2+dfsg-3.dsc
 5da1d5ccad3993b5295be075b49c7c36d357b8b2 27872 
libsbml_5.17.2+dfsg-3.debian.tar.xz
 ca37c344080525e5aa7053f858f7609498524cc0 32497 
libsbml_5.17.2+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 ba6e88e27666e5341e64ae0884e6b67611f02f3fef59bbbed207839930bf059f 2939 
libsbml_5.17.2+dfsg-3.dsc
 a17c56a84cfcb637b21c69c0e9eb26fb41f012696551c4411ef7ed0583cffcaf 27872 
libsbml_5.17.2+dfsg-3.debian.tar.xz
 c2304fa435f5e296cb3e2d8010c1fa96c4556334518776589bb75afd46d78818 32497 
libsbml_5.17.2+dfsg-3_amd64.buildinfo
Files:
 aa92683f5eefb69bba039109a45ee5d2 2939 science optional 
libsbml_5.17.2+dfsg-3.dsc
 fca38513ea4d9fde46a07e05679f299b 27872 science optional 
libsbml_5.17.2+dfsg-3.debian.tar.xz
 0c244deb78f067a1f5f100beaf81253c 32497 science optional 
libsbml_5.17.2+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxR+E4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEw/w/9E1tNqLE1XvMoXeeW0DKgm7JM1aF6ndJc
jr7Oki55uo3hjYcPJplO/DV4s8DcW54NxxU/MXglmlrGW+p/e46BTUsC7rgdX8Pw
eWqdX+AzlzV7qCsBRsEQOKMKWu81H7L3MQO6LjfnIgCrtDx/Y40GAy38o/886NGI
C1lnwoW8NWlp/xeIwB+0DIPHP/PQoRVD6owXhwVHJQ5g2iaq6xP058gbMtYlh2s4
HYs+lMCjmfyEgKwrSNxy7Kw13ZcVXCFEz8WOVh5U/C9mIOxWAjSdnSlVvuaHmHpB
dynvzyKSP7Bklj9ol60x+WSOSpEPMoChudVJodzKj44XOf2YAhZ2ZFuIgNjkd01Q
lgVVsq+yqX1QFy9VKyw1+W+9O/lpLjCi7z/Vxc+OmkUaz7VHgFlZ8nS5Xvl0fXMd
Mb180IpZOwGEDVvQQO4OSJs58TIodcHAO8VibnbdMhOkjbBN9KCkzxx9ui2sG0+S
EmAF7eUNg8XU6hTOPjLVL6ghsVC/Qmc1yAoNjrETw9bUsGOd8FlQ9yQQ1A8tYM3D
gGqoVQm+u2BrkyDpHjblOQ2yYW9WJWtIjsExE9xsMzG9scsaMOF9V88S2wleKLIg
al6aUnjZq8d4wqtZh3EFv0r4kH0I5sqQJ0NHC9Jzbwc5O6epeZq5xrnMyQ2fimOM
tHt8jE13/QI=
=pAHK
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 918619 https://github.com/go-errors/errors/issues/21
Bug #918619 [src:golang-github-go-errors-errors] golang-github-go-errors-errors 
FTBFS with Go 1.11
Set Bug forwarded-to-address to 'https://github.com/go-errors/errors/issues/21'.
> thanks
Stopping processing here.

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

Bug#920862: xorg: Input doesn't work on LTSP clients while X is running, works otherwise

[Lasse Flygenring-Harrsen]

Oh, allright. Then I know where to look. Thanks.

On Wed, Jan 30, 2019, 18:12 Michel Dänzer  On 2019-01-30 10:34 a.m., Michel Dänzer wrote:
> > On 2019-01-29 10:39 p.m., Lasse Flygenring-Harrsen wrote:
> >> Package: xorg
> >> Version: 1:7.7+19
> >> Severity: critical
> >> Justification: breaks the whole system
> >>
> >> Dear Maintainer,
> >>
> >> I have been running a Fat-client LTSP (pxe network booted clients
> getting their software from NBD on a server) system at the school were i
> work
> >> for a couple of months, however recently input stopped working an all
> >> physical hardware, the system boots fine and the Displaymanager (LDM in
> >> my case) works fine except for the fact that keyboard and mouse input
> >> doesn't work. I have managed to get to a shell on the machines and in
> >> text mode TTY's keyboard input works fine and i have confirmed that
> >> both mouse and keyboard is being detected with lsusb. I also tried
> >> starting KDE with startkde, and X seems to work fine there as well
> except
> >> for the lack of keyboard input, same with xinit and xterm. I have also
> tried PS/2 input on the
> >> machines with the same results. The weirdest
> >> thing however is that virtual machines that boot from the same server do
> >> work, both with KVM and VirtualBox that are configured to simulate USB
> inputs. I have
> >> included the contents of /var/log/Xorg.0.log from one of the affected
> >> physical computers below. The problem seems to affect both the stable
> >> and testing branch, I have tried reinstallintg with both. With the same
> >> results.
> >>
> >> [...]
> >>
> >> [  1357.201] (II) config/udev: Adding input device Logitech USB Optical
> Mouse (/dev/input/mouse0)
> >> [  1357.201] (II) No input driver specified, ignoring this device.
> >> [  1357.201] (II) This device may have been added with another device
> file.
> >> [  1357.201] (II) config/udev: Adding input device ImPS/2 Logitech
> Wheel Mouse (/dev/input/mouse1)
> >> [  1357.202] (II) No input driver specified, ignoring this device.
> >> [  1357.202] (II) This device may have been added with another device
> file.
> >> [  1361.133] (II) Server terminated successfully (0). Closing log file.
> >
> > Looks like there are no input drivers that Xorg can use. Is either
> > xserver-xorg-input-libinput or xserver-xorg-input-evdev installed?
>
> Actually, I misinterpreted that.
>
> Your system seems to only have /dev/input/mouse* devices, but the
> xserver-xorg-input-libinput/evdev drivers only work with
> /dev/input/event*. This isn't an X bug but probably some kind of issue
> between the kernel and udev.
>
>
> --
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
>

Bug#920927: [Pkg-zfsonlinux-devel] Bug#920927: zfs-dkms: module FTBFS for i386 kernel

[Petter Reinholdtsen]

[Andreas Beckmann]
> zfs-dkms does not build a kernel module for e.g. the 4.19.0-2-686 i386
> kernel. This happened in a i386 chroot on a amd64 host, but this should
> not really be a problem, since this setup works fine for other
> packages.

Are you sure this isn't intentional?  It is strongly recommended not to
use ZFS on 32 bit architectures, if I recall correctly.

-- 
Happy hacking
Petter Reinholdtsen

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Andrej Shadura]

On Wed, 30 Jan 2019 at 19:57, Kurt Meyer  wrote:
>
> wpasupplicant v2:2.7+git20190128+0c1e29f-1 seems to have fixed the issue 
> here.  I'm using a Broadcom BCM4352 Wi-Fi card.

Wow, that’s very good to hear! Diff, have it fixed it for you? Thanks
in advance for testing.

-- 
Cheers,
  Andrej

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Kurt Meyer]

wpasupplicant v2:2.7+git20190128+0c1e29f-1 seems to have fixed the issue
here.  I'm using a Broadcom BCM4352 Wi-Fi card.

Bug#920941: libvncserver: CVE-2018-20748 CVE-2018-20749 CVE-2018-20750

[Salvatore Bonaccorso]

Source: libvncserver
Version: 0.9.11+dfsg-1.2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for libvncserver, stretch
is not affected by those CVEs as no inocomplete fix was ever applied
there yet in a released version. When issuing the DSA we should make
sure to include the complete fixes for CVE-2018-20019 and
CVE-2018-15127. Details in [3].

CVE-2018-20748[0]:
Incomplete fix for CVE-2018-20019

CVE-2018-20749[1]:
Incomplete fix for CVE-2018-15127

CVE-2018-20750[2]:
Incomplete fix for CVE-2018-15127

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-20748
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20748
[1] https://security-tracker.debian.org/tracker/CVE-2018-20749
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20749
[2] https://security-tracker.debian.org/tracker/CVE-2018-20750
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20750
[3] https://github.com/LibVNC/libvncserver/issues/273#issuecomment-459040241

Regards,
Salvatore

Bug#920882: Confirmation of Fix in libpmix2 3.1.2-2

[Ron Lovell]

My MPI issues were resolved by 3.1.2-2.
Great work, guys.
-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#920821: marked as done (gcc-8: regression: ICE while compiling Trilinos)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 17:40:59 +
with message-id 
and subject line Bug#920821: fixed in gcc-8 8.2.0-16
has caused the Debian Bug report #920821,
regarding gcc-8: regression: ICE while compiling Trilinos
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.)


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

Source: gcc-8
Version: 8.2.0-15
Severity: serious
Affects: src:trilinos
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88995

Hi Maintainer

Trilinos FTBFS with an ICE with gcc-8 8.2.0-15 (8.2.0-14 was fine).

Confirmed on reproducible builds [1].

In file included from 
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/serial/TestSerial_SharedAlloc.cpp:45:
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/TestSharedAlloc.hpp: 
In instantiation of 'void Test::test_shared_alloc() [with MemorySpace = 
Kokkos::HostSpace; ExecutionSpace = Kokkos::Serial]':
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/serial/TestSerial_SharedAlloc.cpp:52:58: 
  required from here
/build/1st/trilinos-12.12.1/packages/kokkos/core/unit_test/TestSharedAlloc.hpp:129:57: 
internal compiler error: in lookup_template_class_1, at cp/pt.c:9459
   RecordFull * rec = RecordFull::allocate( s, name, size * ( i + 1 
) );

 ^~~~
Matthias suggested this looks like upstream #88995.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/trilinos.html
--- End Message ---
--- Begin Message ---
Source: gcc-8
Source-Version: 8.2.0-16

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Jan 2019 18:21:01 +0100
Source: gcc-8
Architecture: source
Version: 8.2.0-16
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 920821
Changes:
 gcc-8 (8.2.0-16) unstable; urgency=medium
 .
   * Update to SVN 20190130 (r268398) from the gcc-8-branch.
 - Fix PR tree-optimization/86865, PR tree-optimization/86865,
   PR target/88948, PR c++/86740, PR c++/87075,
   PR fortran/56386, PR fortran/58906, PR fortran/77385, PR fortran/80260,
   PR fortran/82077, PR fortran/87336.
   * Revert the fix for PR c++/86610, causing PR c++/88995. Closes: #920821.
Checksums-Sha1:
 40546ccfa5b7cfc3630dbfe953f99987c0dbc0ce 32425 gcc-8_8.2.0-16.dsc
 8966d1d98f2631f1bf2144f697f9c393cf98d3eb 4699754 gcc-8_8.2.0-16.diff.gz
 1a0c20aec0164c0f7c765a705aab18d510f00f13 10787 gcc-8_8.2.0-16_source.buildinfo
Checksums-Sha256:
 40879cd64b697d539b000f086ad02c252544e6cf217a9afe85d5f248c5f35900 32425 
gcc-8_8.2.0-16.dsc
 194d6e0f738d068fe6d1f07d29fb59178eaabd5575bf05e87c64873e2568327c 4699754 
gcc-8_8.2.0-16.diff.gz
 25b69165704371444ba6b2e5011593789c994e40da6b90160c5d7b098f8e4cc6 10787 
gcc-8_8.2.0-16_source.buildinfo
Files:
 28a8229ea4d6cd77fb0c63cf9c5242c7 32425 devel optional gcc-8_8.2.0-16.dsc
 66213d21e5dbcf8aab43d4a378214585 4699754 devel optional gcc-8_8.2.0-16.diff.gz
 197c22cfa6c7e17334667e65993dd2ed 10787 devel optional 
gcc-8_8.2.0-16_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlxR3cUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9eAvD/9HovIeV1Ao/yIPW4Bce1mcl9AW9yFrSNCb
nc6Id7Syi3B5WHN5V68S1GvaNQrRXGBpHLDb5rkiCQaKMWiz1aL1+1Ins8grXVNs
0LmQDaadGr9iJdg5pYCl2olDoeW/xbIwfG6vL529dIsWmj6p5vb3BCIQ+7qcjHo6
ulYQgN/7Q7w6yuF1FcE7Wb0DqhwZfCNwkqi3Scqz+qMXp7H/XEpTsgQ4blYwxstj
G5Y+AGFj/2CDnrnNr1Ug0IqxD600ECz9rpCD5gPxAUq9H6lCjKEV+JeGL+o8QffN
LoRbO4guiw3Z7cwO6Wf8wcoIxIv0R6J8Hum54gbMfusdCRpHN+izH9oYoM+J/n1E
yWQnHv2lLtiRSYMEA+AdoGZG0p/mM3fl4ypFAG/XoL6aPYKVhzQdXo2cT9k3YEw0
bmUNiwsH34+Wbi7mfUqnHkL/A2i8fBDL6ejpSBE/svxQ3gIx8A0DUP32xvD1I6cu
zZfNA4pdIGapw2fJIuEZR6yCH4i7vUvW+vo6MWf61tDhkEFifqh2F2

Bug#920935: docker.io: ships /usr/bin/containerd-shim, already provided by containerd

[Andreas Beckmann]

Package: docker.io
Version: 18.09.1+dfsg1-4
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package docker.io.

   Preparing to unpack 
.../17-docker.io_18.09.1+dfsg1-4_amd64.deb ...  

 Unpacking docker.io (18.09.1+dfsg1-4) ...  


  dpkg: error processing archive 
/tmp/apt-dpkg-install-QxThIQ/17-docker.io_18.09.1+dfsg1-4_amd64.deb (--unpack): 

   trying to overwrite '/usr/bin/containerd-shim', which is 
also in package containerd 0.2.3+git20170126.85.aa8187d~ds1-2   
   
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

 Errors were encountered 
while processing:   

  
/tmp/apt-dpkg-install-QxThIQ/17-docker.io_18.09.1+dfsg1-4_amd64.deb 

  

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/containerd-shim


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


containerd=0.2.3+git20170126.85.aa8187d~ds1-2_docker.io=18.09.1+dfsg1-4.log.gz
Description: application/gzip

Bug#919058: itstool bug bisection

[Lars Skovlund]

BTW, the pull request at https://github.com/itstool/itstool/pull/18 looks 
interesting.
A quick test of the copyNode fix therein seems to at least allow itstool to 
complete
(in a loop that ran 100 times). It may not apply cleanly any longer, haven't 
tried.

/Lars

Bug#920862: xorg: Input doesn't work on LTSP clients while X is running, works otherwise

[Michel Dänzer]

On 2019-01-30 10:34 a.m., Michel Dänzer wrote:
> On 2019-01-29 10:39 p.m., Lasse Flygenring-Harrsen wrote:
>> Package: xorg
>> Version: 1:7.7+19
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Dear Maintainer,
>>
>> I have been running a Fat-client LTSP (pxe network booted clients getting 
>> their software from NBD on a server) system at the school were i work
>> for a couple of months, however recently input stopped working an all
>> physical hardware, the system boots fine and the Displaymanager (LDM in
>> my case) works fine except for the fact that keyboard and mouse input
>> doesn't work. I have managed to get to a shell on the machines and in
>> text mode TTY's keyboard input works fine and i have confirmed that
>> both mouse and keyboard is being detected with lsusb. I also tried
>> starting KDE with startkde, and X seems to work fine there as well except
>> for the lack of keyboard input, same with xinit and xterm. I have also tried 
>> PS/2 input on the
>> machines with the same results. The weirdest
>> thing however is that virtual machines that boot from the same server do
>> work, both with KVM and VirtualBox that are configured to simulate USB 
>> inputs. I have
>> included the contents of /var/log/Xorg.0.log from one of the affected
>> physical computers below. The problem seems to affect both the stable
>> and testing branch, I have tried reinstallintg with both. With the same
>> results.  
>>
>> [...]
>>
>> [  1357.201] (II) config/udev: Adding input device Logitech USB Optical 
>> Mouse (/dev/input/mouse0)
>> [  1357.201] (II) No input driver specified, ignoring this device.
>> [  1357.201] (II) This device may have been added with another device file.
>> [  1357.201] (II) config/udev: Adding input device ImPS/2 Logitech Wheel 
>> Mouse (/dev/input/mouse1)
>> [  1357.202] (II) No input driver specified, ignoring this device.
>> [  1357.202] (II) This device may have been added with another device file.
>> [  1361.133] (II) Server terminated successfully (0). Closing log file.
> 
> Looks like there are no input drivers that Xorg can use. Is either
> xserver-xorg-input-libinput or xserver-xorg-input-evdev installed?

Actually, I misinterpreted that.

Your system seems to only have /dev/input/mouse* devices, but the
xserver-xorg-input-libinput/evdev drivers only work with
/dev/input/event*. This isn't an X bug but probably some kind of issue
between the kernel and udev.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#920934: golang-golang-x-tools: /usr/bin/forward is already provided by the qmail package

[Andreas Beckmann]

Package: golang-golang-x-tools
Version: 1:0.0~git20190125.d66bd3c+ds-3
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package golang-golang-x-tools.

   Preparing to unpack 
.../golang-golang-x-tools_1%3a0.0~git20190125.d66bd3c+ds-3_amd64.deb ...

 Unpacking golang-golang-x-tools 
(1:0.0~git20190125.d66bd3c+ds-3) ...

 dpkg: error processing archive 
/var/cache/apt/archives/golang-golang-x-tools_1%3a0.0~git20190125.d66bd3c+ds-3_amd64.deb
 (--unpack):
   trying to overwrite '/usr/bin/forward', which is also in package 
qmail 1.06-6+b1 
   Errors were 
encountered while processing:   

  
/var/cache/apt/archives/golang-golang-x-tools_1%3a0.0~git20190125.d66bd3c+ds-3_amd64.deb

  

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/forward


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


qmail=1.06-6+b1_golang-golang-x-tools=1:0.0~git20190125.d66bd3c+ds-3.log.gz
Description: application/gzip

Bug#918014: apache2: Segfault in mod_filter only wehen started by systemd

[Xavier]

Hello Dominik,

did you check if it works now after libpcap-ng release ?

Cheers,
Xavier

Bug#920933: mariadb-10.3: CVE-2019-2510 CVE-2019-2537

[Salvatore Bonaccorso]

Source: mariadb-10.3
Version: 1:10.3.12-2
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for mariadb-10.3, they
are listed as to be fixed in 10.3.13[2].

CVE-2019-2510[0]:
| Vulnerability in the MySQL Server component of Oracle MySQL
| (subcomponent: InnoDB). Supported versions that are affected are
| 5.7.24 and prior and 8.0.13 and prior. Easily exploitable
| vulnerability allows high privileged attacker with network access via
| multiple protocols to compromise MySQL Server. Successful attacks of
| this vulnerability can result in unauthorized ability to cause a hang
| or frequently repeatable crash (complete DOS) of MySQL Server. CVSS
| 3.0 Base Score 4.9 (Availability impacts). CVSS Vector:
| (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

CVE-2019-2537[1]:
| Vulnerability in the MySQL Server component of Oracle MySQL
| (subcomponent: Server: DDL). Supported versions that are affected are
| 5.6.42 and prior, 5.7.24 and prior and 8.0.13 and prior. Easily
| exploitable vulnerability allows high privileged attacker with network
| access via multiple protocols to compromise MySQL Server. Successful
| attacks of this vulnerability can result in unauthorized ability to
| cause a hang or frequently repeatable crash (complete DOS) of MySQL
| Server. CVSS 3.0 Base Score 4.9 (Availability impacts). CVSS Vector:
| (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-2510
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2510
[1] https://security-tracker.debian.org/tracker/CVE-2019-2537
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2537
[2] https://mariadb.com/kb/en/library/mariadb-10313-release-notes/

Regards,
Salvatore

Bug#920927: zfs-dkms: module FTBFS for i386 kernel

[Andreas Beckmann]

Package: zfs-dkms
Version: 0.7.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts  

 
Control: affects -1 + zfsutils-linux

Hi,

zfs-dkms does not build a kernel module for e.g. the 4.19.0-2-686 i386
kernel. This happened in a i386 chroot on a amd64 host, but this should
not really be a problem, since this setup works fine for other packages.


# MAKEFLAGS="j1 V=1" dpkg --configure --pending 
Setting up zfs-dkms (0.7.12-2) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Removing old zfs-0.7.12 DKMS files...

--
Deleting module version: 0.7.12
completely from the DKMS tree.
--
Done.
Loading new zfs-0.7.12 DKMS files...
It is likely that 4.9.0-8-amd64 belongs to a chroot's host
Building for 4.19.0-2-686
Building initial module for 4.19.0-2-686
Error! Bad return status for module build on kernel: 4.19.0-2-686 (x86_64)
Consult /var/lib/dkms/zfs/0.7.12/build/make.log for more information.
dpkg: error processing package zfs-dkms (--configure):
 installed zfs-dkms package post-installation script subprocess returned error 
exit status 10
Errors were encountered while processing:
 zfs-dkms


Looking at make.log, it fails here:

   gcc-8 
-Wp,-MD,/var/lib/dkms/zfs/0.7.12/build/module/icp/asm-x86_64/aes/.aeskey.o.d  
-nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/8/include 
-I/usr/src/linux-headers-4.19.0-2-common/arch/x86/include 
-I./arch/x86/include/generated  
-I/usr/src/linux-headers-4.19.0-2-common/include -I./include 
-I/usr/src/linux-headers-4.19.0-2-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-4.19.0-2-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-4.19.0-2-common/include/linux/kconfig.h -include 
/usr/src/linux-headers-4.19.0-2-common/include/linux/compiler_types.h  
-I/var/lib/dkms/zfs/0.7.12/build/module/icp 
-I/var/lib/dkms/zfs/0.7.12/build/module/icp -D__KERNEL__ -Wall -Wundef 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common 
-fshort-wchar -Werror-implicit-function-declaration -Wno-format-security 
-std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow 
-mno-avx -m32 -msoft-float -mregparm=3 -freg-struct-return -fno-pic 
-mpreferred-stack-boundary=2 -march=geode -mtune=generic -Wa,-mtune=generic32 
-ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 
-DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 
-DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 
-DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables 
-mindirect-branch=thunk-extern -mindirect-branch-register 
-fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation 
-Wno-format-overflow -Wno-int-in-bool-context -O2 
--param=allow-store-data-races=0 -Wframe-larger-than=1024 
-fstack-protector-strong -Wno-unused-but-set-variable 
-Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls 
-fno-var-tracking-assignments -g -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY 
-Wdeclaration-after-statement -Wno-pointer-sign -Wno-stringop-truncation 
-fno-strict-overflow -fno-merge-all-constants -fmerge-constants 
-fno-stack-check -fconserve-stack -Werror=implicit-int 
-Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types 
-Werror=designated-init 
-fmacro-prefix-map=/usr/src/linux-headers-4.19.0-2-common/= 
-Wno-packed-not-aligned  -I/var/lib/dkms/zfs/0.7.12/build/module/icp/include 
-include /var/lib/dkms/spl/0.7.12/4.19.0-2-686/x86_64/spl_config.h -include 
/var/lib/dkms/zfs/0.7.12/build/zfs_config.h  
-I/var/lib/dkms/zfs/0.7.12/build/include  -I/usr/src/spl-0.7.12/include  
-I/usr/src/spl-0.7.12 -include 
/var/lib/dkms/spl/0.7.12/4.19.0-2-686/x86_64/spl_config.h -include 
/var/lib/dkms/zfs/0.7.12/build/zfs_config.h  
-I/var/lib/dkms/zfs/0.7.12/build/include  -I/usr/src/spl-0.7.12/include  
-I/usr/src/spl-0.7.12 -std=gnu99 -Wno-declaration-after-statement 
-Wno-unused-but-set-variable -Wno-bool-compare -DHAVE_SPL -D_KERNEL 
-DTEXT_DOMAIN=\"zfs-linux-kernel\" -DNDEBUG  -DMODULE  
-DKBUILD_BASENAME='"aeskey"' -DKBUILD_MODNAME='"icp"' -c -o 
/var/lib/dkms/zfs/0.7.12/build/module/icp/asm-x86_64/aes/.tmp_aeskey.o 
/var/lib/dkms/zfs/0.7.12/build/module/icp/asm-x86_64/aes/aeskey.c
 
In file included from 
/var/lib/dkms/zfs/0.7.12/build/module/icp/asm-x86_64/aes/aeskey.c:29:
/var/lib/dkms/zfs/0.7.12/build/module/icp/asm-x86_64/aes/aesopt.h:219:2: error: 
#error Assembler code is only available for x86 and AMD64 systems
 #error Assem

Processed: zfs-dkms: module FTBFS for i386 kernel

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + zfsutils-linux
Bug #920927 [zfs-dkms] zfs-dkms: module FTBFS for i386 kernel
Added indication that 920927 affects zfsutils-linux

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

Processed: FTBFS-es

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch upstream pending
Bug #919766 [src:libemf] libemf FTBFS on big endian: FAIL: docheck2
Added tag(s) patch and pending.

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

Bug#919555: FTBFS-es

[Balint Reczey]

Control: tags -1 + patch upstream pending

Hi,

I have prepared the fixes in Salsa [1], please upload them or I'll
upload them as an NMU in a few days.

Cheers,
Balint

[1] https://salsa.debian.org/debian/libemf/commits/master
-- 
Balint Reczey
Ubuntu & Debian Developer

Processed: FTBFS-es

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch upstream pending
Bug #919555 [src:libemf] libemf FTBFS on arm64: #error Unknown CPU architecture!
Added tag(s) pending and patch.

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

Processed: reassign 919058 to itstool

[Debian Bug Tracking System]

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

> reassign 919058 itstool 2.0.4-1
Bug #919058 [src:itstool] mate-utils: frequent parallel FTBFS
Bug #920408 [src:itstool] mate-utils: Dependency problem
Bug reassigned from package 'src:itstool' to 'itstool'.
Bug reassigned from package 'src:itstool' to 'itstool'.
Ignoring request to alter found versions of bug #919058 to the same values 
previously set
Ignoring request to alter found versions of bug #920408 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919058 to the same values 
previously set
Ignoring request to alter fixed versions of bug #920408 to the same values 
previously set
Bug #919058 [itstool] mate-utils: frequent parallel FTBFS
Bug #920408 [itstool] mate-utils: Dependency problem
Marked as found in versions itstool/2.0.4-1.
Marked as found in versions itstool/2.0.4-1.
> thanks
Stopping processing here.

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

Processed: affects 919058

[Debian Bug Tracking System]

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

> affects 919058 src:mate-utils
Bug #919058 [itstool] mate-utils: frequent parallel FTBFS
Bug #920408 [itstool] mate-utils: Dependency problem
Added indication that 919058 affects src:mate-utils
Added indication that 920408 affects src:mate-utils
> thanks
Stopping processing here.

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

Bug#920901: colmap: FTBFS in Unstable

[Adrian Bunk]

On Wed, Jan 30, 2019 at 08:51:33AM -0500, Scott Kitterman wrote:
> Package: colmap
> Version: 3.5-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> According to https://buildd.debian.org/status/package.php?p=colmap the package
> is FTBFS on all archs.
>...

Yes, see #883619.

> Scott K

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#920834: mlucas: FTBFS and baseline vioiation on i386

[Alex Vong]

Hello Adrian Bunk,

I figure out what's the problem. There's a typo in upstream src:

s/SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13/SSE2_RADIX16_CALC_TWIDDLES_1_2_4_8_13/g

should fix the problem.

I'll upload a new version to mentor, ask for sponsorship again and see
how everything goes.

Cheers,
Alex

Alex Vong  writes:

> Dear Adrian Bunk,
>
> Regarding FTBFS, I've commented it at .
>
> Regarding baseline vioiation on i386, the autotool build system builds 2
> versions of the binary: generic-c and SSE2, and install it to
> libexecdir. Then the wrapper script selects the right binary at
> run-time. Does this approach satifies the current policy?
>
> Cheers,
> Alex
>
> Adrian Bunk  writes:
>
>> Source: mlucas
>> Version: 17.1-1
>> Severity: serious
>> Tags: ftbfs
>>
>> https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0
>>
>> ...
>> gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize
>> -floop-nest-optimize -fomit-frame-pointer -g -g3
>> -fstack-protector-strong -fstack-clash-protection -mmitigate-rop
>> -fwrapv -m32 -msse2
>> -fdebug-prefix-map=/<>=. -fstack-protector-strong
>> -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o
>> mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o
>> src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o
>> src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o
>> src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o
>> src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o
>> src/mlucas_sse2-get_fp_rnd_const.o
>> src/mlucas_sse2-get_preferred_fft_radix.o src/mlucas_sse2-imul_macro.o
>> src/mlucas_sse2-mers_mod_square.o src/mlucas_sse2-mi64.o
>> src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o
>> src/mlucas_sse2-radix1008_ditN_cy_dif1.o
>> src/mlucas_sse2-radix1024_ditN_cy_dif1.o
>> src/mlucas_sse2-radix104_ditN_cy_dif1.o
>> src/mlucas_sse2-radix10_ditN_cy_dif1.o
>> src/mlucas_sse2-radix112_ditN_cy_dif1.o
>> src/mlucas_sse2-radix11_ditN_cy_dif1.o
>> src/mlucas_sse2-radix120_ditN_cy_dif1.o
>> src/mlucas_sse2-radix128_ditN_cy_dif1.o
>> src/mlucas_sse2-radix12_ditN_cy_dif1.o
>> src/mlucas_sse2-radix13_ditN_cy_dif1.o
>> src/mlucas_sse2-radix144_ditN_cy_dif1.o
>> src/mlucas_sse2-radix14_ditN_cy_dif1.o
>> src/mlucas_sse2-radix15_ditN_cy_dif1.o
>> src/mlucas_sse2-radix160_ditN_cy_dif1.o
>> src/mlucas_sse2-radix16_dif_dit_pass.o
>> src/mlucas_sse2-radix16_ditN_cy_dif1.o
>> src/mlucas_sse2-radix16_dyadic_square.o
>> src/mlucas_sse2-radix16_pairFFT_mul.o
>> src/mlucas_sse2-radix16_wrapper_ini.o
>> src/mlucas_sse2-radix16_wrapper_square.o
>> src/mlucas_sse2-radix176_ditN_cy_dif1.o
>> src/mlucas_sse2-radix18_ditN_cy_dif1.o
>> src/mlucas_sse2-radix192_ditN_cy_dif1.o
>> src/mlucas_sse2-radix208_ditN_cy_dif1.o
>> src/mlucas_sse2-radix20_ditN_cy_dif1.o
>> src/mlucas_sse2-radix224_ditN_cy_dif1.o
>> src/mlucas_sse2-radix22_ditN_cy_dif1.o
>> src/mlucas_sse2-radix240_ditN_cy_dif1.o
>> src/mlucas_sse2-radix24_ditN_cy_dif1.o
>> src/mlucas_sse2-radix256_ditN_cy_dif1.o
>> src/mlucas_sse2-radix26_ditN_cy_dif1.o
>> src/mlucas_sse2-radix288_ditN_cy_dif1.o
>> src/mlucas_sse2-radix28_ditN_cy_dif1.o
>> src/mlucas_sse2-radix30_ditN_cy_dif1.o
>> src/mlucas_sse2-radix31_ditN_cy_dif1.o
>> src/mlucas_sse2-radix32_dif_dit_pass.o
>> src/mlucas_sse2-radix32_ditN_cy_dif1.o
>> src/mlucas_sse2-radix32_dyadic_square.o
>> src/mlucas_sse2-radix32_wrapper_ini.o
>> src/mlucas_sse2-radix32_wrapper_square.o
>> src/mlucas_sse2-radix36_ditN_cy_dif1.o
>> src/mlucas_sse2-radix4032_ditN_cy_dif1.o
>> src/mlucas_sse2-radix40_ditN_cy_dif1.o
>> src/mlucas_sse2-radix44_ditN_cy_dif1.o
>> src/mlucas_sse2-radix48_ditN_cy_dif1.o
>> src/mlucas_sse2-radix512_ditN_cy_dif1.o
>> src/mlucas_sse2-radix52_ditN_cy_dif1.o
>> src/mlucas_sse2-radix56_ditN_cy_dif1.o
>> src/mlucas_sse2-radix5_ditN_cy_dif1.o
>> src/mlucas_sse2-radix60_ditN_cy_dif1.o
>> src/mlucas_sse2-radix63_ditN_cy_dif1.o
>> src/mlucas_sse2-radix64_ditN_cy_dif1.o
>> src/mlucas_sse2-radix6_ditN_cy_dif1.o
>> src/mlucas_sse2-radix72_ditN_cy_dif1.o
>> src/mlucas_sse2-radix768_ditN_cy_dif1.o
>> src/mlucas_sse2-radix7_ditN_cy_dif1.o
>> src/mlucas_sse2-radix80_ditN_cy_dif1.o
>> src/mlucas_sse2-radix88_ditN_cy_dif1.o
>> src/mlucas_sse2-radix8_dif_dit_pass.o
>> src/mlucas_sse2-radix8_ditN_cy_dif1.o
>> src/mlucas_sse2-radix960_ditN_cy_dif1.o
>> src/mlucas_sse2-radix96_ditN_cy_dif1.o
>> src/mlucas_sse2-radix992_ditN_cy_dif1.o
>> src/mlucas_sse2-radix9_ditN_cy_dif1.o src/mlucas_sse2-rng_isaac.o
>> src/mlucas_sse2-test_fft_radix.o src/mlucas_sse2-threadpool.o
>> src/mlucas_sse2-twopmodq.o src/mlucas_sse2-twopmodq100.o
>> src/mlucas_sse2-twopmodq128.o src/mlucas_sse2-twopmodq128_96.o
>> src/mlucas_sse2-twopmodq160.o src/mlucas_sse2-twopmodq192.o
>> src/mlucas_sse2-twopmodq256.o src/mlucas_sse2-twopmodq64_test.o
>> src/mlucas_sse2-twopmodq80.o src/mlucas_sse2-twopmodq96.o
>> src/mlucas_sse2-types.o src/mlucas_sse2-util.o -lm
>> /usr/bin/ld: /usr/bin/ld: DWARF error: could not fin

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Lorenz]

Hi,

Il giorno mer 30 gen 2019 alle ore 11:26 Axel Beckert  ha
scritto:

> >His "Actually I'm wrong on this" mail
> >(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918764#127) was
> >(and actually still is) confusing me.
>

I'm wrong on the claim that, for example, i can crash a VT session by
executing a 'udevadm' command from the graphic session, or vice versa.
To be more clear, when you read message #122 just ignore those lines:

> ..Final Bonus Weirdness:
> if you start udevd in background in the VT session, then go to the
graphic
> session and prompt a udevadm command from there, it's the VT session that
get crashed.

The rest of the message. i.e. how to trigger the bug and the commit that
introduces this bug in Debian's systemd still holds true to me.


> >But some of the details from his first mail which were not cited in
> >his "Actually I'm wrong on this" mail (mainly "This was introduced in
> >commit e803efca") tell me that this _is_ actually a bug in the udev
> >package.
>

That commit triggered the bug in Debian, but the bug itself was already in
the code
since at least systemd v232-15.
According to my experiments, the culprit is the following:

>when udevd is run in background and it's not detached with it's own
'--daemon' option,
>then a udevadm command is enough to kill everything.

It does not make any sense to me, but that's it.

Regards,
Lorenz

Processed: closing 920882

[Debian Bug Tracking System]

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

> close 920882 3.1.2-2
Bug #920882 [libpmix2] libpmix2: unable to open mca_pmix_ext2x: libpmix.so.2: 
No such file or directory
Marked as fixed in versions pmix/3.1.2-2.
Bug #920882 [libpmix2] libpmix2: unable to open mca_pmix_ext2x: libpmix.so.2: 
No such file or directory
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#920882: closing 920882

[Salvatore Bonaccorso]

close 920882 3.1.2-2
thanks

Bug#784871: ppa not working anymore on buster

[Erwan David]

Alas, the ppa is ubuntu-centric and for info do not work anymore on 
buster.
(Fail update installation: No module named 'sip'
Can't import Qt modules: Qt and/or PyQt is probably not installed correctly...)

-- 
Erwan

Processed: found 920209 in 25.3.23-1

[Debian Bug Tracking System]

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

> # build failed once the same way also with this version
> found 920209 25.3.23-1
Bug #920209 [src:galera-3] galera-3: FTBFS on mipsel
Marked as found in versions galera-3/25.3.23-1.
> thanks
Stopping processing here.

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

Bug#796536: Maybe latest criu 3.11 is now ready for stable release?

[Salvatore Bonaccorso]

Hi,

Thanks for the ping.

On Wed, Jan 30, 2019 at 02:45:35PM +0200, UAB "Bona Mens" paslaugos wrote:
> Hi,
> 
> You reported critical bug 4 years ago, when latest criu release was 1.6
> Since 2015 lots of criu versions with lots bugfixes were released.
> Latest criu version is 3.11
> 
> Maybe now criu 3.11 is ready for stable release?

Although the pace has been reduced a bit, part of the orginal
reasoning still holds I think.

Secondly the packaging itself needs improvement before I would
consider it proper enough to be included in a stable release.

Regards,
Salvatore

Bug#919058: itstool bug bisection

[Mike Gabriel]

Control: forwarded -1 https://github.com/itstool/itstool/issues/36

On  Mi 30 Jan 2019 14:56:03 CET, Mike Gabriel wrote:


Control: reassign -1 src:itstool

Hi Lars,

On  Mi 30 Jan 2019 13:16:16 CET, Lars Skovlund wrote:

I have bisected the problem in the itstool git tree, as detailed on  
this github issue:


https://github.com/itstool/itstool/issues/36

Trying an earlier itstool version was suggested on another Mate bug report:

https://github.com/mate-desktop/mate-utils/issues/210

So what's next? reassign this bug to itstool?

/Lars


@Lars: Awesome work! Thanks!

@itstool maintainer: please undo/revert/fix arbitrary segfaults  
introduced by this upstream commit:

https://github.com/itstool/itstool/commit/d3adf0264ee2b6fd28b7eff7dec33501d6e75a7c

Mike


Setting "forwarded" field to the correct upstream bug.

Mike
--

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

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



pgpSYpXLk3TCV.pgp
Description: Digitale PGP-Signatur

Processed: Re: Bug#919058: itstool bug bisection

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/itstool/itstool/issues/36
Bug #919058 [src:itstool] mate-utils: frequent parallel FTBFS
Bug #920408 [src:itstool] mate-utils: Dependency problem
Changed Bug forwarded-to-address to 
'https://github.com/itstool/itstool/issues/36' from 
'https://github.com/mate-desktop/mate-utils/issues/211'.
Changed Bug forwarded-to-address to 
'https://github.com/itstool/itstool/issues/36' from 
'https://github.com/mate-desktop/mate-utils/issues/211'.

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

Processed: Re: Bug#919058: itstool bug bisection

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:itstool
Bug #919058 [src:mate-utils] mate-utils: frequent parallel FTBFS
Bug #920408 [src:mate-utils] mate-utils: Dependency problem
Bug reassigned from package 'src:mate-utils' to 'src:itstool'.
Bug reassigned from package 'src:mate-utils' to 'src:itstool'.
No longer marked as found in versions mate-utils/1.20.2-1.
No longer marked as found in versions mate-utils/1.20.2-1.
Ignoring request to alter fixed versions of bug #919058 to the same values 
previously set
Ignoring request to alter fixed versions of bug #920408 to the same values 
previously set

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

Bug#919058: itstool bug bisection

[Mike Gabriel]

Control: reassign -1 src:itstool

Hi Lars,

On  Mi 30 Jan 2019 13:16:16 CET, Lars Skovlund wrote:

I have bisected the problem in the itstool git tree, as detailed on  
this github issue:


https://github.com/itstool/itstool/issues/36

Trying an earlier itstool version was suggested on another Mate bug report:

https://github.com/mate-desktop/mate-utils/issues/210

So what's next? reassign this bug to itstool?

/Lars


@Lars: Awesome work! Thanks!

@itstool maintainer: please undo/revert/fix arbitrary segfaults  
introduced by this upstream commit:

https://github.com/itstool/itstool/commit/d3adf0264ee2b6fd28b7eff7dec33501d6e75a7c

Mike
--

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

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



pgpfEoXijDolW.pgp
Description: Digitale PGP-Signatur

Bug#920901: colmap: FTBFS in Unstable

[Scott Kitterman]

Package: colmap
Version: 3.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

According to https://buildd.debian.org/status/package.php?p=colmap the package
is FTBFS on all archs.  Experimental apparently builds, but unstable is
blocking the completion of the glew transition.

Scott K

Bug#910939: marked as done (dds: Fails to build on i386)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 13:34:03 +
with message-id 
and subject line Bug#910939: fixed in dds 2.9.0-6
has caused the Debian Bug report #910939,
regarding dds: Fails to build on i386
to be marked as done.

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

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


-- 
910939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dds
Version: 2.9.0-5
Severity: serious
Tags: ftbfs

dds fails to build on i386, in the build test stage:

https://buildd.debian.org/status/package.php?p=dds

Build log excerpt


debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
ln -sf ../src/libdds.so.0 examples/libdds.so
/usr/bin/make -C examples -f Makefiles/Makefile_linux DealerPar
make[2]: Entering directory '/<>/examples'
g++ -O3 -flto -fopenmp -Wshadow -Wsign-conversion -pedantic -Wall
-Wextra -Wcast-align -Wcast-qual -Wctor-dtor-privacy
-Wdisabled-optimization -Winit-self -Wlogical-op
-Wmissing-declarations -Wmissing-include-dirs -Wnoexcept
-Wold-style-cast -Woverloaded-virtual -Wredundant-decls -Wsign-promo
-Wstrict-null-sentinel -Wstrict-overflow=1 -Wswitch-default -Wundef
-Werror -Wno-unused -Wno-unknown-pragmas -Wno-long-long -Wno-format -c
hands.cpp -o hands.o
g++ -O3 -flto -fopenmp -Wshadow -Wsign-conversion -pedantic -Wall
-Wextra -Wcast-align -Wcast-qual -Wctor-dtor-privacy
-Wdisabled-optimization -Winit-self -Wlogical-op
-Wmissing-declarations -Wmissing-include-dirs -Wnoexcept
-Wold-style-cast -Woverloaded-virtual -Wredundant-decls -Wsign-promo
-Wstrict-null-sentinel -Wstrict-overflow=1 -Wswitch-default -Wundef
-Werror -Wno-unused -Wno-unknown-pragmas -Wno-long-long -Wno-format -c
DealerPar.cpp -o DealerPar.o
g++ -O3 -flto -fopenmp -Wshadow -Wsign-conversion -pedantic -Wall
-Wextra -Wcast-align -Wcast-qual -Wctor-dtor-privacy
-Wdisabled-optimization -Winit-self -Wlogical-op
-Wmissing-declarations -Wmissing-include-dirs -Wnoexcept
-Wold-style-cast -Woverloaded-virtual -Wredundant-decls -Wsign-promo
-Wstrict-null-sentinel -Wstrict-overflow=1 -Wswitch-default -Wundef
-Werror -Wno-unused -Wno-unknown-pragmas -Wno-long-long -Wno-format
hands.o DealerPar.o -L. -ldds -o DealerPar
make[2]: Leaving directory '/<>/examples'
LD_LIBRARY_PATH=src examples/DealerPar
terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_default_append
Aborted


Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: dds
Source-Version: 2.9.0-6

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated dds package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Jan 2019 14:21:50 +0100
Source: dds
Architecture: source
Version: 2.9.0-6
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg 
Changed-By: Christoph Berg 
Closes: 910939
Changes:
 dds (2.9.0-6) unstable; urgency=medium
 .
   * Pass CFLAGS to examples Makefile as well.
   * Fix compiler warning when used without -flto.
   * Ignore symbol mismatches on non-amd64.
   * Add newly appeared C++ symbols.
   * Ignore test failure on i386; tenace, our main reverse dependency, is not
 affected by the problem. (Closes: #910939)
Checksums-Sha1:
 8fbbca55e64bbc1e7ebbcf9134bae2ddf05323c0 1926 dds_2.9.0-6.dsc
 3fdc03b704ee92ca7b96d993d3b22372bea01cef 9808 dds_2.9.0-6.debian.tar.xz
Checksums-Sha256:
 10c99df881b1721487365b7c4ec5f36da8d885dac3ea1983ee550b6627b4a283 1926 
dds_2.9.0-6.dsc
 d57d2545e7ad1ef2c2ec8ec885da78104854dcf47f982855022d48c111802b02 9808 
dds_2.9.0-6.debian.tar.xz
Files:
 47939472d72655a3c29556620e3f8a3e 1926 games optional dds_2.9.0-6.dsc
 d1355472c7949cf5ddbcfbed8fd1c3cc 9808 games optional dds_2.9.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlxRpZIACgkQTFprqxLS
p65g9w//VzTBXhrrHX28jSCsnYOd9WWbrZ0rLK43kudMiVNK6VJGLiusV2ArxAvB
f5U8gWzI1E97l5v8SmJIUYfWQ8V4F4y5HkkB570/gSmNPtaH8doPL4COOjhfEwe2
SGMERLPB8nD85wCLzUYCy/ptmpmFptFqOJvd

Bug#912450: marked as done (python-nanomsg FTBFS with nanomsg 1.1.5)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 13:27:12 +
with message-id 
and subject line Bug#920879: Removed package(s) from unstable
has caused the Debian Bug report #912450,
regarding python-nanomsg FTBFS with nanomsg 1.1.5
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.)


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

https://buildd.debian.org/status/package.php?p=python-nanomsg&suite=sid

...
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test 
running test
running egg_info
creating nanomsg.egg-info
writing nanomsg.egg-info/PKG-INFO
writing top-level names to nanomsg.egg-info/top_level.txt
writing dependency_links to nanomsg.egg-info/dependency_links.txt
writing manifest file 'nanomsg.egg-info/SOURCES.txt'
reading manifest file 'nanomsg.egg-info/SOURCES.txt'
writing manifest file 'nanomsg.egg-info/SOURCES.txt'
running build_ext
building '_nanomsg_cpy' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c _nanomsg_cpy/wrapper.c -o 
build/temp.linux-amd64-2.7/_nanomsg_cpy/wrapper.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-amd64-2.7/_nanomsg_cpy/wrapper.o -lnanomsg -o 
/<>/_nanomsg_cpy.so -Wl,-z,now
test_subscribe_works (tests.test_pubsub.TestPubSubSockets) ... ok
test_send_recv (tests.test_pair.TestPairSockets) ... ok
test_send_recv_large_message (tests.test_pair.TestPairSockets) ... ok
test_send_recv_with_embeded_nulls (tests.test_pair.TestPairSockets) ... ok
test_bind (tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_connect (tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_get_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... FAIL
test_is_open_is_false_when_closed 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_is_open_is_true_when_open 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_set_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... FAIL

==
FAIL: test_get_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods)
--
Traceback (most recent call last):
  File "/<>/tests/test_general_socket_methods.py", line 56, in 
test_get_int_option
self.assertEqual(LINGER_DEFAULT_VALUE, actual)
AssertionError: 1000 != 0

==
FAIL: test_set_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods)
--
Traceback (most recent call last):
  File "/<>/tests/test_general_socket_methods.py", line 51, in 
test_set_int_option
self.assertEqual(expected, actual)
AssertionError: 500 != 0

--
Ran 10 tests in 0.024s

FAILED (failures=2)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build-arch] Error 25
--- End Message ---
--- Begin Message ---
Version: 1.0-2+rm

Dear submitter,

as the package python-nanomsg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/920879

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...

Bug#919007: Needs to be updated for libexempi8

[Scott Kitterman]

On Fri, 11 Jan 2019 17:42:37 +0100 Michael Biebl  wrote:
> Source: python-xmp-toolkit
> Version: 2.0.1+git20140309.5437b0a-5
> Severity: serious
> 
> Hi,
> 
> libexempi bumped its soname from 3 → 8.
> The transition is tracked at
> https://release.debian.org/transitions/html/auto-exempi.html
> and via #918687.
> 
> I tried updating the package with the attached patch, but this triggers
> test-suite failures (see build.log).
> 
> Unfortunately I don't know enough Python to fix this myself.

I took your patch and also took the latest upstream git snapshot and it still 
failed.  There have been no upstream commits in a year and a half and the 
package is orphaned in Debian.  I would recommend you file for removal from 
unstable.

Scott K

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

Bug#910879: Unreproducible

[Lisandro Damián Nicanor Pérez Meyer]

tag 910879 unreproducible moreinfo
severity 910879 important
thanks

Hi Eric!

So far the only report due to this was yours, and none of us could reproduce 
it, so I'm marking the bug accordingly and also changing the severity.

Can you still reproduce this issue?

By the way, critical is perhaps too much for this bug, had it been found 
everywhere.

Kinds regards, Lisandro.

-- 
El futuro es WIN95 A no ser que hagamos algo a tiempo.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: Unreproducible

[Debian Bug Tracking System]

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

> tag 910879 unreproducible moreinfo
Bug #910879 [print-manager] print-manager: Prevent to start a kde session for 
all users
Added tag(s) unreproducible and moreinfo.
> severity 910879 important
Bug #910879 [print-manager] print-manager: Prevent to start a kde session for 
all users
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#796536: Maybe latest criu 3.11 is now ready for stable release?

[UAB "Bona Mens" paslaugos]

Hi,

You reported critical bug 4 years ago, when latest criu release was 1.6
Since 2015 lots of criu versions with lots bugfixes were released.
Latest criu version is 3.11

Maybe now criu 3.11 is ready for stable release?

-- 

IT paslaugos įmonėms, prekyba kompiuteriais su Linux OS:
UAB „Bona Mens“  - http://bonamens.lt  http://tinklas.eu/prekyba
Tel.: +370-614-53085
Laisva programinė įranga verslui ir namams:http://baltix.lthttp://openoffice.lt

Bug#920900: libicu-dev: Command icu-config disappeared from libicu-dev

[Vlastimil Zima]

Package: libicu-dev
Version: 63.1-6
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading libicu-dev, I can't install PyICU using pip, due to an error:

FileNotFoundError: [Errno 2] No such file or directory: 'icu-config': 
'icu-config'

I found no replacement of the icu-config, hence I assume the file disappeared 
by an accident.

When I downgrade libicu-dev back to 60.2-6, it works.


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

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

Versions of packages libicu-dev depends on:
ii  icu-devtools  63.1-6
ii  libc6-dev [libc-dev]  2.28-5
ii  libicu63  63.1-6

libicu-dev recommends no packages.

Versions of packages libicu-dev suggests:
pn  icu-doc  

-- no debconf information

Bug#920597: Last docker.io update - not start

[Dominique Dumont]

On Wednesday, 30 January 2019 11:45:33 CET Arnaud Rebillout wrote:
> Could it be a matter of `systemctl restart docker`, or something like
> that?

spot on !

docker is working fine after a restart.

Thanks for the hint.

Dod

Bug#920791: New libglm-dev

[b...@debian.org]

Hi!

On 29/01/2019 21:53, Guus Sliepen wrote:
> retitle 920791 FTBFS on all non-SIMD architectures
> forwarded 920791 https://github.com/g-truc/glm/issues/865
> thanks
>
> On Tue, Jan 29, 2019 at 07:50:44AM +0100, Guus Sliepen wrote:
>
>> I cannot reproduce it either, but according to the logs it looks like it
>> might be some #defines not working properly on some architectures.
> The issue is that the new version of GLM conditionally adds constexpr to
> some member functions where that would cause a compiler error. It so
> happens that constexpr is not used on any architecture with SIMD
> instructions supported by GLM, which are amd64 and arm64 as far as I can
> tell.


Hmm, i386 fails as well:

https://buildd.debian.org/status/fetch.php?pkg=freedink&arch=i386&ver=109.4-3&stamp=1548774599&raw=0

Also, that's reproducible on a local sid-i386 pbuilder.

- Sylvain

Bug#919058: itstool bug bisection

[Lars Skovlund]

I have bisected the problem in the itstool git tree, as detailed on this github 
issue:

https://github.com/itstool/itstool/issues/36

Trying an earlier itstool version was suggested on another Mate bug report:

https://github.com/mate-desktop/mate-utils/issues/210

So what's next? reassign this bug to itstool?

/Lars

Bug#920894: Bug#918329: apriltag ftbfs on release architectures

[Matthias Klose]

The README even says:

Install
===

The default installation will place headers in /usr/local/include and
shared library in /usr/local/lib. It also installs a pkg-config script
into /usr/local/lib/pkgconfig. Be aware that there are some larger tag families
which may take a long time to build. If you do not want to use these tag
families then you can speed up the installation by deleting the files
tagCircle49h12.c, tagCircle49h12.h, tagCustom48h12.c, tagCustom48h12.h,
tagStandard52h13.c, and tagStandard52h13.h before installing.

Processed: user debian...@lists.debian.org, usertagging 919978, affects 919978, unarchiving 623703 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 919978 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 919978 + diaspora-installer-mysql
Bug #919978 [diaspora-installer] diaspora-installer package fails to install
Added indication that 919978 affects diaspora-installer-mysql
> unarchive 623703
Bug #623703 {Done: Fabrizio Regalli } 
[firmware-b43-lpphy-installer] [firmware-b43-lpphy-installer] Firmware file not 
found (404 error)
Unarchived Bug 623703
> usertags 623703 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 623703 1:015-14.1
Bug #623703 {Done: Fabrizio Regalli } 
[firmware-b43-lpphy-installer] [firmware-b43-lpphy-installer] Firmware file not 
found (404 error)
Marked as found in versions b43-fwcutter/1:015-14.1 and reopened.
> found 623703 firmware-b43-lpphy-installer/4.174.64.19-4
Bug #623703 [firmware-b43-lpphy-installer] [firmware-b43-lpphy-installer] 
Firmware file not found (404 error)
The source firmware-b43-lpphy-installer and version 4.174.64.19-4 do not appear 
to match any binary packages
Marked as found in versions firmware-b43-lpphy-installer/4.174.64.19-4.
> close 623703
Bug #623703 [firmware-b43-lpphy-installer] [firmware-b43-lpphy-installer] 
Firmware file not found (404 error)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#920828: marked as done (elpa-lsp-ui: fails to install: ERROR: install script from elpa-lsp-ui package failed)

[Debian Bug Tracking System]

Your message dated Wed, 30 Jan 2019 11:34:52 +
with message-id 
and subject line Bug#920828: fixed in emacs-lsp-ui 6.0-2
has caused the Debian Bug report #920828,
regarding elpa-lsp-ui: fails to install: ERROR: install script from elpa-lsp-ui 
package failed
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.)


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

Hi,

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

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

  Setting up emacs-gtk (1:26.1+1-3) ...
  update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs 
(emacs) in auto mode
  update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) 
in auto mode
  tsort: -: input contains a loop:
  tsort: elpa-dash
  tsort: emacsen-common
  tsort: -: input contains a loop:
  tsort: elpa-s
  tsort: emacsen-common
  Install elpa-dash for emacs
  install/dash-2.14.1: Handling install of emacsen flavor emacs
  install/dash-2.14.1: byte-compiling for emacs
  Install elpa-s for emacs
  install/s-1.12.0: Handling install of emacsen flavor emacs
  install/s-1.12.0: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-spinner for emacs
  install/spinner-1.7.3: Handling install of emacsen flavor emacs
  install/spinner-1.7.3: byte-compiling for emacs
  Install elpa-f for emacs
  install/f-0.20.0: Handling install of emacsen flavor emacs
  install/f-0.20.0: byte-compiling for emacs
  Install elpa-ht for emacs
  install/ht-2.2: Handling install of emacsen flavor emacs
  install/ht-2.2: byte-compiling for emacs
  Install elpa-dash-functional for emacs
  install/dash-functional-1.2.0: Handling install of emacsen flavor emacs
  install/dash-functional-1.2.0: byte-compiling for emacs
  Install elpa-lsp-mode for emacs
  install/lsp-mode-6.0: Handling install of emacsen flavor emacs
  install/lsp-mode-6.0: byte-compiling for emacs
  Setting up emacs (1:26.1+1-3) ...
  Setting up elpa-markdown-mode (2.3+154-2) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-markdown-mode for emacs
  install/markdown-mode-2.3snapshot154: Handling install of emacsen flavor emacs
  install/markdown-mode-2.3snapshot154: byte-compiling for emacs
  Setting up elpa-lsp-ui (6.0-1) ...
  Install elpa-f for emacs
  install/f-0.20.0: Handling install of emacsen flavor emacs
  install/f-0.20.0: byte-compiling for emacs
  Install elpa-ht for emacs
  install/ht-2.2: Handling install of emacsen flavor emacs
  install/ht-2.2: byte-compiling for emacs
  Install elpa-spinner for emacs
  install/spinner-1.7.3: Handling install of emacsen flavor emacs
  install/spinner-1.7.3: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-markdown-mode for emacs
  install/markdown-mode-2.3snapshot154: Handling install of emacsen flavor emacs
  install/markdown-mode-2.3snapshot154: byte-compiling for emacs
  Install elpa-dash for emacs
  install/dash-2.14.1: Handling install of emacsen flavor emacs
  install/dash-2.14.1: byte-compiling for emacs
  Install elpa-dash-functional for emacs
  install/dash-functional-1.2.0: Handling install of emacsen flavor emacs
  install/dash-functional-1.2.0: byte-compiling for emacs
  Install elpa-lsp-mode for emacs
  install/lsp-mode-6.0: Handling install of emacsen flavor emacs
  install/lsp-mode-6.0: byte-compiling for emacs
  Install elpa-lsp-ui for emacs
  install/lsp-ui-6.0: Handling install of emacsen flavor emacs
  install/lsp-ui-6.0: byte-compiling for emacs
  
  In toplevel form:
  lsp-ui-doc.el:179:1:Warning: Unused lexical argument `include-deleted-frame'
  
  In toplevel form:
  lsp-ui-flycheck.el:30:1:Error: Cannot open load file: No such file or 
directory, flycheck
  
  In lsp-ui-sideline-mode:
  lsp-ui-sideline.el:493:29:Warning: assignment to free variable
  `flycheck-display-errors-function'
  
  In end of data:
  lsp-ui-sideline.el:501:1:Warning: the following functions are not known to be
  defined: flycheck-overlay-errors-in, flycheck-error-format-message-and-id,
  flycheck-error-level
  ERROR: install script from elpa-lsp-ui package failed
  dpkg:

Processed: severity of 920876 is serious

[Debian Bug Tracking System]

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

> severity 920876 serious
Bug #920876 [xfce4-notes] xfce4-notes: Not functioning
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: fix bug severities

[Debian Bug Tracking System]

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

> severity 920894 serious
Bug #920894 [src:apriltag] apriltag ftbfs on release architectures
Severity set to 'serious' from 'important'
> severity 918329 important
Bug #918329 [gcc-8] apriltag ftbfs on release architectures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#918329: apriltag ftbfs on release architectures

[Matthias Klose]

it's the new apriltag 0.10 version adding these files, so just work around it by
lowering the optimization.  yes, it's memory and compile time hog, but also
present in GCC 7.

Processed: reassign apriltag issue again

[Debian Bug Tracking System]

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

> clone 918329 -1
Bug #918329 [gcc-8] apriltag ftbfs on release architectures
Bug 918329 cloned as bug 920894
> reassign -1 src:apriltag
Bug #920894 [gcc-8] apriltag ftbfs on release architectures
Bug reassigned from package 'gcc-8' to 'src:apriltag'.
Ignoring request to alter found versions of bug #920894 to the same values 
previously set
Ignoring request to alter fixed versions of bug #920894 to the same values 
previously set
> forwarded 918329 https://gcc.gnu.org/PR89115
Bug #918329 [gcc-8] apriltag ftbfs on release architectures
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR89115'.
> tags 918329 + upstream
Bug #918329 [gcc-8] apriltag ftbfs on release architectures
Added tag(s) upstream.
> severity -1 important
Bug #920894 [src:apriltag] apriltag ftbfs on release architectures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: reopening 920822

[Debian Bug Tracking System]

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

> reopen 920822
Bug #920822 {Done: Alastair McKinstry } [src:phpmyadmin] 
phpmyadmin: CVE-2019-6798: PMASA-2019-2
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pmix/3.1.2-2.
> thanks
Stopping processing here.

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

Bug#920597: Last docker.io update - not start

[Arnaud Rebillout]

> On Wednesday, 30 January 2019 7:59:24 PM AEDT Dominique Dumont wrote:
>> But docker fails to start with:
>> $ docker run -ti alpine sh
>> docker: Error response from daemon: failed to start shim: exec:
>> "docker-containerd-shim": executable file not found in $PATH: unknown.

I can run `docker run -ti alpine sh` successfully with 18.09.1+dfsg1-4.
I don't have any `docker-containerd-shim` binary installed anywhere,
docker doesn't seem to need it and uses `containerd-shim` as expected:

  $ ls -l /usr/bin/containerd-shim
   -rwxr-xr-x 1 root root 5981528 Jan 28 06:16 /usr/bin/containerd-shim

Could it be a matter of `systemctl restart docker`, or something like
that? Or is there anything special in your setup that I should know,
that could help me reproduce the issue?

Bug#920597: Last docker.io update - not start

[Dmitry Smirnov]

On Wednesday, 30 January 2019 7:59:24 PM AEDT Dominique Dumont wrote:
> But docker fails to start with:
> $ docker run -ti alpine sh
> docker: Error response from daemon: failed to start shim: exec:
> "docker-containerd-shim": executable file not found in $PATH: unknown.

Ahh, what a mess... I'll have another look. I could start containers 
successfully on 18.09.1+dfsg1-4 but perhaps there is another place where 
"docker-containerd-shim" is hard-coded...

-- 
All the best,
 Dmitry Smirnov.

---


There is no such thing as public opinion. There is only published opinion.
-- Winston Churchill


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

Processed: Re: Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Severity set to 'critical' from 'important'
> found -1 239-8
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Marked as found in versions systemd/239-8.

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