Bug#952111: micro crashes consistently with panic: interface conversion: interface {} is float64, not bool

[Pirate Praveen]

Control: forwarded -1 https://github.com/zyedidia/micro/issues/1548

On Wed, 26 Feb 2020 14:17:20 + Alain Ducharme
 wrote:
> This error means that your settings.json config file has been corrupted or is 
> not correctly formatted for the micro version you are using.
> Most likely scenario: you ran micro v2.x.x, which changes the setttings.json 
> format, then tried to go back to using v1.x.x.
> 
> Solution:
> rm ~/.config/micro/settings.json
> Or to start from fresh and wipe all of micro's configuration:
> rm -r ~/.config/micro
> 

I need to use both versions as I share the home directory between buster
and sid. I have opened an issue upstream for better handling of such
cases by possibly versioning the setting.config format and giving better
error message in case of unsupported versions.

Hopefully this issue will go away once micro 2.x is backported to buster.



signature.asc
Description: OpenPGP digital signature

Processed: Re: micro crashes consistently with panic: interface conversion: interface {} is float64, not bool

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/zyedidia/micro/issues/1548
Bug #952111 [micro] micro crashes consistently with panic: interface 
conversion: interface {} is float64, not bool
Set Bug forwarded-to-address to 'https://github.com/zyedidia/micro/issues/1548'.

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

Bug#952782: python-dnspython: Python 2 binary should not be released with bullseye

[Scott Kitterman]

Package: python-dnspython
Version: 1.16.0-1
Severity: serious

As the primary maintianer of dnspython, I don't think it is suitable to
leave with a python2 binary for the bullseye release.

Scott K

Bug#937256: marked as done (ROM: Please remove pbh5tools since it is unmaintained and there is no Python2 port)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:17:03 +
with message-id 
and subject line Bug#937256: Removed package(s) from unstable
has caused the Debian Bug report #937256,
regarding ROM: Please remove pbh5tools since it is unmaintained and there is no 
Python2 port
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.)


-- 
937256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pbh5tools
Version: 0.8.0+git20170929.58d54ff+dfsg-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pbh5tools

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 pbh5tools | 0.8.0+git20170929.58d54ff+dfsg-1 | source, all
python-pbh5tools | 0.8.0+git20170929.58d54ff+dfsg-1 | amd64, arm64, mips64el, 
ppc64el
python-pbh5tools-doc | 0.8.0+git20170929.58d54ff+dfsg-1 | all

--- Reason ---
ROM: Please remove pbh5tools since it is unmaintained and there is no Python2 
port
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 937...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/937256

This message was generated 

Bug#935346: marked as done (puddletag: Qt4 removal from Bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:14:20 +
with message-id 
and subject line Bug#952773: Removed package(s) from unstable
has caused the Debian Bug report #935346,
regarding puddletag: Qt4 removal from Bullseye
to be marked as done.

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

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


-- 
935346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puddletag
Version: 1.2.0-2
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

Hi!

As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
cycle, as announced in [1].

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get removed
from the Debian repositories.

Your package still uses Qt 4, via the Python bindings (PyQt4).

Therefore, please take the time and:

- contact your upstream (if existing) and ask about the state of a Qt 5 /
  PyQt5 port of your application;
- if there are no activities regarding porting, investigate whether there are
  suitable alternatives for your users;
- if there is a Qt 5 port that is not yet packaged, consider packaging it;
- if both the Qt 4 and the Qt 5 versions already coexist in the Debian
  archives, consider removing the Qt 4 version.

Porting from Qt 4 to 5 is much easier than it was to port from Qt 3 to 4.
Please see [2] for the general porting instructions, and [3] for some
Python-specific differences.

The removal is being tracked in [4]. My intention is to bump the severity
of this bug to RC soon, like it is already the case with other Qt 4 removal
bugs.

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
[2]: https://doc.qt.io/qt-5/sourcebreaks.html
[3]: https://www.riverbankcomputing.com/static/Docs/PyQt5/pyqt4_differences.html
[4]: https://wiki.debian.org/Qt4Removal

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.0-2+rm

Dear submitter,

as the package puddletag 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/952773

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#913053: marked as done (src:haskell-cabal-helper: ftbfs)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:11:35 +
with message-id 
and subject line Bug#945011: Removed package(s) from unstable
has caused the Debian Bug report #913053,
regarding src:haskell-cabal-helper: ftbfs
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.)


-- 
913053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-cabal-helper
Version: 0.8.0.2-1
Severity: serious

Someone will need to package cabal-plan to update to a modern version.
--- End Message ---
--- Begin Message ---
Version: 0.8.0.2-2+rm

Dear submitter,

as the package haskell-cabal-helper 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/945011

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#952709: marked as done (libmicrodns: do not release with bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:13:30 +
with message-id 
and subject line Bug#952760: Removed package(s) from unstable
has caused the Debian Bug report #952709,
regarding libmicrodns: do not release with bullseye
to be marked as done.

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

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


-- 
952709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmicrodns
Version: 0.1.0-2
Severity: serious
Tags: sid bullseye

vlc no longer depends on libmicrodns, so there are no reverse
dependencies left. So let's remove it from the archive.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.1.0-2+rm

Dear submitter,

as the package libmicrodns 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/952760

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#914352: marked as done (haskell-hmt: Missing build-dependency on modular-arithmetic)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:10:45 +
with message-id 
and subject line Bug#945007: Removed package(s) from unstable
has caused the Debian Bug report #914352,
regarding haskell-hmt: Missing build-dependency on modular-arithmetic
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.)


-- 
914352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hmt
Version: 0.15
Severity: serious
Justification: fails to build from source

This package has no reverse dependencies and is not on LTS.
Do we want to continue maintaining it? If so, we will have to package
modular-arithmetic.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.16-3+rm

Dear submitter,

as the package haskell-hmt 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/945007

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#874907: marked as done ([hydrogen] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:13:56 +
with message-id 
and subject line Bug#952772: Removed package(s) from unstable
has caused the Debian Bug report #874907,
regarding [hydrogen] Future Qt4 removal from Buster
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.)


-- 
874907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hydrogen
Version: 0.9.7-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 0.9.7-6+rm

Dear submitter,

as the package hydrogen 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/952772

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#905446: marked as done (haskell-hackage-mirror: FTBFS: Module `Control.Monad.Trans.Resource' does not export `monadThrow')

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:12:42 +
with message-id 
and subject line Bug#945935: Removed package(s) from unstable
has caused the Debian Bug report #905446,
regarding haskell-hackage-mirror: FTBFS: Module `Control.Monad.Trans.Resource' 
does not export `monadThrow'
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.)


-- 
905446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hackage-mirror
Version: 0.1.1.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: affects -1 + libghc-hackage-mirror-dev libghc-hackage-mirror-doc 
libghc-hackage-mirror-prof

Hi,

haskell-hackage-mirror FTBFS everywhere:
https://buildd.debian.org/status/package.php?p=haskell-hackage-mirror=unstable


[...]
build_recipe
Running debian/hlibrary.setup build --builddir=dist-ghc
Preprocessing library for hackage-mirror-0.1.1.1..
Building library for hackage-mirror-0.1.1.1..
[1 of 1] Compiling Hackage.Mirror   ( src/Hackage/Mirror.hs, 
dist-ghc/build/Hackage/Mirror.o )

src/Hackage/Mirror.hs:75:7: error:
Module `Control.Monad.Trans.Resource' does not export `monadThrow'
   |
75 |   monadThrow,
   |   ^^

src/Hackage/Mirror.hs:82:38: error:
Module `Data.Conduit' does not export `unwrapResumable'
   |
82 | import Data.Conduit ( Source, yield, unwrapResumable, ($=), ($$) )
   |  ^^^
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Andreas
--- End Message ---
--- Begin Message ---
Version: 0.1.1.1-3+rm

Dear submitter,

as the package haskell-hackage-mirror 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/945935

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#896971: marked as done (FTBFS: needs patching for GHC 8.2)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 03:11:11 +
with message-id 
and subject line Bug#945010: Removed package(s) from unstable
has caused the Debian Bug report #896971,
regarding FTBFS: needs patching for GHC 8.2
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.)


-- 
896971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghc-mod
Version: 5.8.0.0-1
Severity: serious
Forwarded: https://github.com/DanielG/ghc-mod/issues/900

.
--- End Message ---
--- Begin Message ---
Version: 5.8.0.0-2+rm

Dear submitter,

as the package ghc-mod 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/945010

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#874812: [amora-server] Qt4 removal from Debian

[Axel Beckert]

Hi Moritz,

Moritz Mühlenhoff wrote:
> Attached is a quick-and-dirty patch to drop the amora-applet binary
> package, qt4 will soon be removed from unstable.

Thanks for the effort, but in the meanwhile I'm rather think we should
remove amora completely from Debian, at least for now.

Upstream (Cc'ed) tried to migrate to Qt5 about two years ago.
Compiling and running with Qt5 was not the big issue, but getting
Bluetooh working again — and hence core functionality:
https://github.com/amora/amora/issues/86#issuecomment-432001824

Another point is that the main client platform are Nokia Symbian
phones — which are nearly nowhere in use anymore. I still do have such
a phone, but for years the only reason to power it on was to test
amora before uploading. Haven't powered it on since the last upload...

There's IIRC code for a Qt client (Qt 4 I assume, maybe even older)
which AFAIK never was published in any app store though. If I remember
correctly I once got it running on my OpenMoko (i.e. ages ago). Or was
it on the Nokia N900? Can't remeber anymore...

We still can bring it back when the Qt5 port is working properly and
there's a client for modern mobile phones (even if only for less
popular OS like KaiOS/GerdaOS or SailfishOS).

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#948740: marked as done (clanlib: FTBFS with $* is no longer supported as of Perl 5.30 at ../Utilities/webbuilder.pl line 74.)

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 00:34:15 +
with message-id 
and subject line Bug#948740: fixed in clanlib 1.0~svn3827-8
has caused the Debian Bug report #948740,
regarding clanlib: FTBFS with $* is no longer supported as of Perl 5.30 at 
../Utilities/webbuilder.pl line 74.
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.)


-- 
948740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clanlib
Version: 1.0~svn3827-7
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to build in a rebuild I'm performing in current
unstable with the following error:

Making all in Setup
make[2]: Entering directory '/build/clanlib-1.0~svn3827/Setup'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/clanlib-1.0~svn3827/Setup'
Making all in pkgconfig
make[2]: Entering directory '/build/clanlib-1.0~svn3827/pkgconfig'
make[2]: Leaving directory '/build/clanlib-1.0~svn3827/pkgconfig'
Making all in Documentation
make[2]: Entering directory '/build/clanlib-1.0~svn3827/Documentation'
Making all in Tutorial
make[3]: Entering directory '/build/clanlib-1.0~svn3827/Documentation/Tutorial'
Making all in Kavanek
make[4]: Entering directory 
'/build/clanlib-1.0~svn3827/Documentation/Tutorial/Kavanek'
echo 01-Installing.html
echo index.html
01-Installing.html
../../Utilities/xslt.sh  01-Installing.xml  01-Installing.html  ./default.xsl
index.html
../../Utilities/xslt.sh  index.xml  index.html  ./default.xsl
Done
make[4]: Leaving directory 
'/build/clanlib-1.0~svn3827/Documentation/Tutorial/Kavanek'
make[4]: Entering directory '/build/clanlib-1.0~svn3827/Documentation/Tutorial'
../Utilities/webbuilder.pl ./../documentation.theme ./../Tutorial/index.xml
$* is no longer supported as of Perl 5.30 at ../Utilities/webbuilder.pl line 74.
make[4]: *** [Makefile:779: index.html] Error 255
make[4]: Leaving directory '/build/clanlib-1.0~svn3827/Documentation/Tutorial'
make[3]: *** [Makefile:505: all-recursive] Error 1
make[3]: Leaving directory '/build/clanlib-1.0~svn3827/Documentation/Tutorial'
make[2]: *** [Makefile:511: all-recursive] Error 1
make[2]: Leaving directory '/build/clanlib-1.0~svn3827/Documentation'
make[1]: *** [Makefile:478: all-recursive] Error 1
make[1]: Leaving directory '/build/clanlib-1.0~svn3827'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:34: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: clanlib
Source-Version: 1.0~svn3827-8
Done: Markus Koschany 

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated clanlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2020 23:46:18 +0100
Source: clanlib
Architecture: source
Version: 1.0~svn3827-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 886902 911254 948740
Changes:
 clanlib (1.0~svn3827-8) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Markus Koschany ]
   * Use debhelper-compat = 12.
   * Declare compliance with Debian Policy 4.5.0.
   * Use canonical VCS URI.
   * wrap-and-sort -sa
   * Update homepage field and point to Github repository. The old clanlib.org
 website is gone.
   * Add remove-special-variable-perl-5.30.patch.
 Fix FTBFS and remove the occurrences of $* because the special variable $*
 is a fatal error in Perl 5.30. (Closes: #948740)
 .
   [ Helmut Grohne ]
   * Let dh_auto_configure pass a multiarch 

Bug#948740: marked as pending in clanlib

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #948740 in clanlib 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/games-team/clanlib/-/commit/6359d134b61864eb1772c57be95230b19510a3ee


Add remove-special-variable-perl-5.30.patch.

Fix FTBFS and remove the occurrences of $* because the special variable $* is a
fatal error in Perl 5.30.  Not even upstream seemed to know what the code did
back then.

Closes: #948740


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/948740

Processed: Bug#948740 marked as pending in clanlib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948740 [src:clanlib] clanlib: FTBFS with $* is no longer supported as of 
Perl 5.30 at ../Utilities/webbuilder.pl line 74.
Added tag(s) pending.

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

Bug#952751: marked as done (eyes17: missing Breaks+Replaces: python3-expeyes (<< 4.6.1-2))

[Debian Bug Tracking System]

Your message dated Sat, 29 Feb 2020 00:08:09 +
with message-id 
and subject line Bug#952751: fixed in expeyes 4.6.3-1
has caused the Debian Bug report #952751,
regarding eyes17: missing Breaks+Replaces: python3-expeyes (<< 4.6.1-2)
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.)


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

Hi,

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

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

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

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

  Preparing to unpack .../eyes17_4.6.2-1_all.deb ...
  Unpacking eyes17 (4.6.2-1) ...
  dpkg: error processing archive /var/cache/apt/archives/eyes17_4.6.2-1_all.deb 
(--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/eyes17/Peripherals.py', 
which is also in package python3-expeyes 4.4.4+dfsg-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/eyes17_4.6.2-1_all.deb

4.6.1-2 was the version that shuffled the modules around according
to the changelog.


cheers,

Andreas


python3-expeyes=4.4.4+dfsg-4_eyes17=4.6.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: expeyes
Source-Version: 4.6.3-1
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated expeyes 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: Sat, 29 Feb 2020 00:32:11 +0100
Source: expeyes
Architecture: source
Version: 4.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 952751
Changes:
 expeyes (4.6.3-1) unstable; urgency=medium
 .
   * new upstream release. Improved the generation of help HTML files
 for eyes17, to avoid redundent files
   * added a Conflicts: clause. eyes17 -> python3-expeyes (<< 4.6.1-2)
 Closes: #952751
Checksums-Sha1:
 65b796914b90fb9f78a79c872ca71713a2852b51 2479 expeyes_4.6.3-1.dsc
 43347e451b84786ea4538211cf234b1d8f8b389c 44061968 expeyes_4.6.3.orig.tar.xz
 0be9542639fbfb138c56d67243ecee908c47ed60 20800 expeyes_4.6.3-1.debian.tar.xz
 dc3930d89443038157e600330aba56783e3a71f8 13942 expeyes_4.6.3-1_source.buildinfo
Checksums-Sha256:
 153ce24413e1e03b935d3b2a9cb20724368e4b0fd54d12f673eaf5921932d3cb 2479 
expeyes_4.6.3-1.dsc
 c22b6ebc2e7cf0af4c7cb9f5f4b1e67e5db3f5b7bc39cc2e06715984c0f7e191 44061968 
expeyes_4.6.3.orig.tar.xz
 07eca5e19fed7f6f7d00f0969c1ea325d03ac924dccae464502533e5fe7d1857 20800 
expeyes_4.6.3-1.debian.tar.xz
 754af0edf2a74ff19d837ba5d9ccaa94cd50cb682ce62b908946069e89f10a05 13942 
expeyes_4.6.3-1_source.buildinfo
Files:
 59f5ef420da866eabf16e8227b2dea66 2479 science optional expeyes_4.6.3-1.dsc
 a9a7d9c2577657ce3637d9d204f6ea34 44061968 science optional 
expeyes_4.6.3.orig.tar.xz
 a6ffd384cf29024193451001a08df78d 20800 science optional 
expeyes_4.6.3-1.debian.tar.xz
 0548439bb1a9e9bf8f08eab1f5235d7f 13942 science optional 
expeyes_4.6.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl5Zo6wUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjn5mA//UJHvdZfXP8J10gx3mE4/xmVPDawB
dG9RRQ5px4gLZ15LRGHrb+dvBDdYa0RhJp64Qcjzyl5tTOL8ycYGl3gDSQQcAPms
QRkXgmQ/SHnpUJ10/p/UwAppfNHBdd/v9vhx61Y37eaW3ufElLNsSYyMcUzAdWIT
AAnLiFsCYNwZQsEgA8dgfrY5li2YF8KaT83+wl67av9VtO5n8VMPiXyttkrEwKyM

Bug#952478: marked as done (cloudpickle: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 15:00:12 -0800
with message-id 
and subject line Fixed by new upload 1.3.0-1
has caused the Debian Bug report #952478,
regarding cloudpickle: Please make another source-only upload to allow testing 
migration
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.)


-- 
952478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cloudpickle
Version: 1.2.1-2
Severity: serious
Justification: out-of-sync unstable-to-testing
X-Debbugs-CC: di...@ghic.org

Dear cloudpickle maintainer,

The latest upload of your package was not a source-only upload. As a result,
it did not migrate to Testing.

According to
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html ,
packages that are out-of-sync between testing and unstable for more than 60
days are considered as having a Release Critical bug. Your package has been
out-of-sync for 115 days.

Please consider making another source-only upload to allow testing migration
according to https://wiki.debian.org/SourceOnlyUpload . Let me know if you
need any help. Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Package: cloudpickle
Version: 1.3.0-1
thanks

Someone else did the upload but I'm pretty sure they did a source only
upload.


https://tracker.debian.org/news/1104647/accepted-cloudpickle-130-1-source-into-unstable/

Diane


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

Bug#952015: marked as pending in test-kitchen

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #952015 in test-kitchen 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/ruby-team/test-kitchen/-/commit/9e1e5c6c7ed6ee1a7ec25a7f2fcebccf0b0d7224


Fix tests comparing output to stderr

  * d/patches/0017-Fix-stderr-output-tests.patch: Add patch.
- Ignore minitest deprecation warning in output (closes: #952015).
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952015

Processed: Bug#952015 marked as pending in test-kitchen

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952015 [src:test-kitchen] test-kitchen: FTBFS: ERROR: Test "ruby2.5" 
failed.
Added tag(s) pending.

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

Bug#952476: marked as done (cupp: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 23:07:55 +
with message-id 
and subject line Bug#952476: fixed in cupp 0.0+20190501.git986658-5
has caused the Debian Bug report #952476,
regarding cupp: Please make another source-only upload to allow testing 
migration
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.)


-- 
952476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cupp
Version: 0.0+20190501.git986658-4
Severity: serious
Justification: out-of-sync unstable-to-testing

Dear cupp maintainer,

The latest upload of your package was not a source-only upload. As a result,
it did not migrate to Testing.

According to
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html ,
packages that are out-of-sync between testing and unstable for more than 60
days are considered as having a Release Critical bug. Your package has been
out-of-sync for 80 days.

Please consider making another source-only upload to allow testing migration
according to https://wiki.debian.org/SourceOnlyUpload . If you need any help,
please let me know. Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: cupp
Source-Version: 0.0+20190501.git986658-5
Done: Marcio de Souza Oliveira 

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

Debian distribution maintenance software
pp.
Marcio de Souza Oliveira  (supplier of updated cupp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2020 21:52:11 +
Source: cupp
Binary: cupp cupp3
Architecture: source all
Version: 0.0+20190501.git986658-5
Distribution: unstable
Urgency: medium
Maintainer: Marcio de Souza Oliveira 
Changed-By: Marcio de Souza Oliveira 
Description:
 cupp   - generate dictionaries for attacks from personal data
 cupp3  - transitional package
Closes: 952476
Changes:
 cupp (0.0+20190501.git986658-5) unstable; urgency=medium
 .
   * Rebuilds to source-only upload. Thanks Boyuan Yang.
 (Closes: #952476)
   * debian/control:
   - Bumped DH level to 12.
   - Bumped Standards-Version to 4.5.0.
   * debian/tests/control: created to perform a trivial test.
Checksums-Sha1:
 69afd8b95d52992eefd36c206500581db147dcd9 1985 cupp_0.0+20190501.git986658-5.dsc
 5128b5150862803ab3e64b7b281328ee604fd329 3744 
cupp_0.0+20190501.git986658-5.debian.tar.xz
 9c86fb7a6aa003a2654328754f3ea1076bd9f41c 3484 
cupp3_0.0+20190501.git986658-5_all.deb
 949a095a8c62327836100ef1cfbb1c50cb2cdd99 13296 
cupp_0.0+20190501.git986658-5_all.deb
 5c2f703fd76931667731eccac412cd2c2aff842e 7249 
cupp_0.0+20190501.git986658-5_amd64.buildinfo
Checksums-Sha256:
 fa91751382460afcf3ec0bb06b944f1f5ad5c6dc807fadf39b7aa0bd21756297 1985 
cupp_0.0+20190501.git986658-5.dsc
 d4003c797ab9bfac39ce1559f23371a86c23934c3fe54c34ba58cc295676c4a5 3744 
cupp_0.0+20190501.git986658-5.debian.tar.xz
 b2b995e8e9ebd51ca784efbd445ee7a2355b39dd2158c3c776cca97eef3e1059 3484 
cupp3_0.0+20190501.git986658-5_all.deb
 39b4a2a60db53ca48760c30a98b49f1246ce8822b8b84364ca02f0c9c634c6be 13296 
cupp_0.0+20190501.git986658-5_all.deb
 000ed02629b1cb3a4790eef4d64447dd7d5e060fbfeb6834dab6fbcb77eb44bf 7249 
cupp_0.0+20190501.git986658-5_amd64.buildinfo
Files:
 6ad2bcbd7104f7f55eb78445fe24fb00 1985 misc optional 
cupp_0.0+20190501.git986658-5.dsc
 63c1efe3a3940557cdcf63961a1e0d4d 3744 misc optional 
cupp_0.0+20190501.git986658-5.debian.tar.xz
 7216425caa6c85ad193b766b460200cf 3484 oldlibs optional 
cupp3_0.0+20190501.git986658-5_all.deb
 8d35d160ae07304fef8605c951c133c3 13296 misc optional 
cupp_0.0+20190501.git986658-5_all.deb
 8d2cc558ee56acbaeec9906ce9d382bf 7249 misc optional 
cupp_0.0+20190501.git986658-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9rDMyifLF0J67mR23xbSgM2tMFAl5Zl0EACgkQR23xbSgM
2tPonA//dnoI95mj+z31lA+TvC7pu2plfgXTRG22JVOKq0KMXzU7rDFyQ3MFjYR8
MQ9iPY/5dKDT7LAe7xsETkXyCMzt/vmZPZ2hBoDUTetjby/x4L7+PmIQbPUg8hqC

Bug#952693: marked as done (dbusada: unbuildable in unstable: requires experimental libahven)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 22:49:10 +
with message-id 
and subject line Bug#952693: fixed in ahven 2.7-4
has caused the Debian Bug report #952693,
regarding dbusada: unbuildable in unstable: requires experimental libahven
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.)


-- 
952693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbusada,ahven
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: found -1 dbusada/0.5.0-3
Control: found -1 ahven/2.7-2

dbusada_0.5.0-3 in unstable appears to Build-Depend on a package that
only exists in experimental (libahven8-dev, from source package
ahven >= 2.7-3).

This seems to be causing an autopkgtest regression report that prevents
glib2.0 from migrating to testing.

If ahven 2.7-3 is ready for unstable, please upload it; or if not, please
revert the dbusada change.

smcv
--- End Message ---
--- Begin Message ---
Source: ahven
Source-Version: 2.7-4
Done: Nicolas Boulenguez 

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated ahven package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 23:23:59 +0100
Source: ahven
Architecture: source
Version: 2.7-4
Distribution: unstable
Urgency: medium
Maintainer: Reto Buerki 
Changed-By: Nicolas Boulenguez 
Closes: 952693
Changes:
 ahven (2.7-4) unstable; urgency=medium
 .
   * Reupload to unstable for gnat-9 transition. Closes: #952693.
Checksums-Sha1:
 391bda8c7d369b1c0410b830d3fe9b8e27982aee 2191 ahven_2.7-4.dsc
 58e3c96a37e1f688385d8dd88347e963731c5b7d 7820 ahven_2.7-4.debian.tar.xz
 be2f6b1d92c383ede90c52451f06b180186735c4 3769 ahven_2.7-4_source.buildinfo
Checksums-Sha256:
 1dcf62e8172f9b06a6923b909183568b3fd4630fc4acc3c1f861e9fb0207168e 2191 
ahven_2.7-4.dsc
 d4f3d9df4ce7afa80aff9c98ba9370f97eafb338b63b6876e2dcc30e44a63bee 7820 
ahven_2.7-4.debian.tar.xz
 ff4488211e5ae7e8293f33f2cc72276d2ee4a0a5f565c5f6ccfd68a8b89f9551 3769 
ahven_2.7-4_source.buildinfo
Files:
 1c5c5b24c393d91b5537f7a9f6e6968c 2191 libs optional ahven_2.7-4.dsc
 cbf72a4ebdc25f4a317635a7c0d919d7 7820 libs optional ahven_2.7-4.debian.tar.xz
 89c4c03cacc5f7a364a7e77b52495136 3769 libs optional 
ahven_2.7-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl5Zk0MTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jaZnEAC3IHHxgH7K9h6EeFWZjFw9kO65sFK9
yG4mtoZ5Kkggzw5/jVvyTtD258RJKxjDhoGsRPBQrMIOd4G1/J4/wu0DJhEFXdiU
IJ0iV5KSxtFgoGBkGTO9xm3LyIL4+7kHF5QpTwh7Yob7Mb68hxQTHI5iY211sZRz
tdY+3ypVExj7v/V2dUtv5//MIe+ydM2O6zRYq/CtcS32DJBMqOByzMriwCpXF2et
0NBKwSCImkMaulCqKPEByk7HV+DbbNbne5YJLCB+rLLdztE3GwrRMuXZFAwfUbrG
B4SJ518EBkxzCsWODSu1KvgV1IRWOIKr8q0ew56FsUleNhdu1kx3WvDKbtIdPhDG
kGefbk8lDB4Cm3iBvmbZy5YwhlI+ocqng7pNbt/AlFH+np/bcXw8C0I58pvMFOG5
bGFui3d//UXMmIAkXGDG4K6Hqdte5dOyQbTTufNzU/7cFtbkiTQ6f+7khPKbJCIt
nB5kJZWueTfqHJw00dR7QGl88yFjoTJoy5MokCQQhlBE5eSr54VfyMYFrORohg+k
rXFKoAW4bRRD/VeoIcDhllYODYG5q83zYuMjCkrmkpXHsgJHjZ1mF5bg5lAYZ2TK
3geT3GyU66h7buOjTomvQDKO69s4od1mfHEgLJreBmOCse6jqnen6wRGo3TLlET5
ZMbZdiY2XjueYQ==
=+bni
-END PGP SIGNATURE End Message ---

Processed: serious

[Debian Bug Tracking System]

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

> severity 912786 serious
Bug #912786 [src:aspectc++] aspectc++: : Please update to llvm-9
Severity set to 'serious' from 'important'
> severity 947437 serious
Bug #947437 [flang] flang: Please update to llvm-9
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#951916: proftpd-mod-vroot: proftpd cannot load mod_vroot

[Hilmar Preuße]

On 2/23/20 4:27 AM, Nikolai Lusan wrote:

Hi Nikolai,

> Trying to run proftpd with mod_vroot. The following error causes
> hosts using vroot to not be loaded:
> 
I've built a package for proftpd-mod-vroot, which have a dep on
proftpd-abi-1.3.6c [1]. Let me know if it solves your issue, then I'll
trigger a rebuild of the package.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/951916/
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#952031: marked as done (ruby-active-model-serializers: FTBFS: ERROR: Test "ruby2.7" failed.)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 22:09:10 +
with message-id 
and subject line Bug#952031: fixed in ruby-active-model-serializers 0.10.10-1
has caused the Debian Bug report #952031,
regarding ruby-active-model-serializers: FTBFS: ERROR: Test "ruby2.7" 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.)


-- 
952031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-active-model-serializers
Version: 0.10.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/<>/debian/ruby-active-model-serializers/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.7 -w -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/action_controller/adapter_selector_test.rb" 
> "test/action_controller/explicit_serializer_test.rb" 
> "test/action_controller/json/include_test.rb" 
> "test/action_controller/json_api/deserialization_test.rb" 
> "test/action_controller/json_api/errors_test.rb" 
> "test/action_controller/json_api/fields_test.rb" 
> "test/action_controller/json_api/linked_test.rb" 
> "test/action_controller/json_api/transform_test.rb" 
> "test/action_controller/lookup_proc_test.rb" 
> "test/action_controller/namespace_lookup_test.rb" 
> "test/action_controller/serialization_scope_name_test.rb" 
> "test/action_controller/serialization_test.rb" 
> "test/active_model_serializers/adapter_for_test.rb" 
> "test/active_model_serializers/json_pointer_test.rb" 
> "test/active_model_serializers/logging_test.rb" 
> "test/active_model_serializers/model_test.rb" 
> "test/active_model_serializers/test/serializer_test.rb" 
> "test/active_record_test.rb" "test/adapter/attributes_test.rb" 
> "test/adapter/deprecation_test.rb" "test/adapter/json/belongs_to_test.rb" 
> "test/adapter/json/collection_test.rb" "test/adapter/json/has_many_test.rb" 
> "test/adapter/json/transform_test.rb" 
> "test/adapter/json_api/belongs_to_test.rb" 
> "test/adapter/json_api/collection_test.rb" 
> "test/adapter/json_api/errors_test.rb" "test/adapter/json_api/fields_test.rb" 
> "test/adapter/json_api/has_many_explicit_serializer_test.rb" 
> "test/adapter/json_api/has_many_test.rb" 
> "test/adapter/json_api/has_one_test.rb" 
> "test/adapter/json_api/include_data_if_sideloaded_test.rb" 
> "test/adapter/json_api/json_api_test.rb" 
> "test/adapter/json_api/linked_test.rb" "test/adapter/json_api/links_test.rb" 
> "test/adapter/json_api/parse_test.rb" 
> "test/adapter/json_api/relationship_test.rb" 
> "test/adapter/json_api/resource_meta_test.rb" 
> "test/adapter/json_api/toplevel_jsonapi_test.rb" 
> "test/adapter/json_api/transform_test.rb" 
> "test/adapter/json_api/type_test.rb" "test/adapter/json_test.rb" 
> "test/adapter/null_test.rb" "test/adapter/polymorphic_test.rb" 
> "test/adapter_test.rb" "test/array_serializer_test.rb" "test/cache_test.rb" 
> "test/collection_serializer_test.rb" 
> "test/generators/scaffold_controller_generator_test.rb" 
> "test/generators/serializer_generator_test.rb" "test/lint_test.rb" 
> "test/logger_test.rb" "test/poro_test.rb" 
> "test/serializable_resource_test.rb" 
> "test/serializers/association_macros_test.rb" 
> "test/serializers/associations_test.rb" "test/serializers/attribute_test.rb" 
> "test/serializers/attributes_test.rb" 
> "test/serializers/configuration_test.rb" "test/serializers/fieldset_test.rb" 
> "test/serializers/meta_test.rb" "test/serializers/options_test.rb" 
> "test/serializers/read_attribute_for_serialization_test.rb" 
> "test/serializers/reflection_test.rb" "test/serializers/root_test.rb" 
> "test/serializers/serialization_test.rb" 
> "test/serializers/serializer_for_test.rb" 
> "test/serializers/serializer_for_with_namespace_test.rb" -v
> Running without SimpleCov
> 

Bug#952775: Depends on projectm

[Moritz Muehlenhoff]

Package: qmmp-plugin-projectm
Severity: serious

projectm depends on Qt4, which is up for removal. qmmp in turn also depends on
projectm, so please drop the qmmp-plugin-projectm binary package.

Cheers,
Moritz

Bug#874812: [amora-server] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Mon, Jan 20, 2020 at 08:27:41PM +0100, Moritz Mühlenhoff wrote:
> On Thu, Sep 12, 2019 at 11:48:46PM +0200, Axel Beckert wrote:
> > > or we're moving forward with the Qt4 removal.
> > 
> > Just move forward. IIRC amora already has been removed from testing,
> > so it really shouldn't be an issue for the Qt4 removal.
> 
> Quick status update: qt4 is now removed from testing and we're
> planning to remove it from unstable by end of Februrary (along
> with whatever rdeps (currently 15) remain by that date).

Attached is a quick-and-dirty patch to drop the amora-applet binary
package, qt4 will soon be removed from unstable.

Cheers,
Moritz
diff -Naur amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.dirs amora-server-1.2~svn+git2015.04.25/debian/amora-applet.dirs
--- amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.dirs	2015-03-16 20:29:23.0 +0100
+++ amora-server-1.2~svn+git2015.04.25/debian/amora-applet.dirs	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-usr/bin
-usr/share/applications
diff -Naur amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.docs amora-server-1.2~svn+git2015.04.25/debian/amora-applet.docs
--- amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.docs	2015-03-16 20:29:23.0 +0100
+++ amora-server-1.2~svn+git2015.04.25/debian/amora-applet.docs	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-amora-applet/README
-debian/README.source
diff -Naur amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.install amora-server-1.2~svn+git2015.04.25/debian/amora-applet.install
--- amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.install	2015-03-16 20:29:23.0 +0100
+++ amora-server-1.2~svn+git2015.04.25/debian/amora-applet.install	1970-01-01 01:00:00.0 +0100
@@ -1,4 +0,0 @@
-# qmake-qt4's generated install target has the path hardwired. So we
-# do it manually.
-amora-applet/amorad-gui usr/bin
-debian/amorad-gui.desktop usr/share/applications
diff -Naur amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.menu amora-server-1.2~svn+git2015.04.25/debian/amora-applet.menu
--- amora-server-1.2~svn+git2015.04.25.orig/debian/amora-applet.menu	2015-03-16 20:29:23.0 +0100
+++ amora-server-1.2~svn+git2015.04.25/debian/amora-applet.menu	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-?package(amora-applet):needs="X11" section="Applications/Mobile Devices"\
-  title="Amora Daemon (systray applet)" command="/usr/bin/amorad-gui"
diff -Naur amora-server-1.2~svn+git2015.04.25.orig/debian/control amora-server-1.2~svn+git2015.04.25/debian/control
--- amora-server-1.2~svn+git2015.04.25.orig/debian/control	2015-04-26 02:24:42.0 +0200
+++ amora-server-1.2~svn+git2015.04.25/debian/control	2020-02-26 12:52:33.293657036 +0100
@@ -10,12 +10,10 @@
libbluetooth-dev,
libdbus-1-dev,
libimlib2-dev,
-   libqt4-dev,
libtool-bin,
libx11-dev,
libxtst-dev,
-   pkg-config,
-   qt4-qmake
+   pkg-config
 Standards-Version: 3.9.6
 Homepage: https://github.com/amora/amora#readme
 Vcs-Git: git://github.com/amora/amora.git
@@ -48,28 +46,3 @@
  The client has to be installed on the mobile phone and is not
  contained in the package. It can be downloaded from the home page of
  the project.
-
-Package: amora-applet
-Provides: amora-server
-Architecture: any
-Depends: ${misc:Depends},
- ${shlibs:Depends}
-Description: use a bluetooth device as X remote control (systray applet)
- Amora (A mobile remote assistant) is an application that enables you
- to control your desktop using your mobile phone. It uses bluetooth to
- send mouse and keyboard events to the X session. With it, you can
- control your presentations, movies or any other application which
- mainly uses mouse and cursor keys.
- .
- Amora also has a screenshot feature, where you can see a thumbnail of
- the currently focused window on the mobile phone.
- .
- Currently only Symbian Series 60 mobile phones are supported. A Java
- client implementation is under development. A proof of concept client
- for Linux based mobile device like the Nokia Internet Tablets and the
- OpenMoko FreeRunner is available.
- .
- This package contains the Qt-based system tray applet version of the
- daemon running on the to be remote controlled computer. The client
- has to be installed on the mobile phone and is not contained in the
- package. It can be downloaded from the home page of the project.
diff -Naur amora-server-1.2~svn+git2015.04.25.orig/debian/rules amora-server-1.2~svn+git2015.04.25/debian/rules
--- amora-server-1.2~svn+git2015.04.25.orig/debian/rules	2015-03-16 20:29:23.0 +0100
+++ amora-server-1.2~svn+git2015.04.25/debian/rules	2020-02-26 12:52:49.545755336 +0100
@@ -13,8 +13,6 @@
 override_dh_auto_configure:
 	cd amora-cli && autoreconf -f -i
 	dh_auto_configure -D amora-cli
-	# Does qmake-qt4 

Bug#952770: adacontrol: ./src/./src/pfni.adb:228: undefined reference to `thick_queries__full_name_image'

[Sebastian Ramacher]

Source: adacontrol
Version: 1.21r6b-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

adacontrol failed to build on i386:
| /usr/bin/gnatgcc -c -x ada -gnatA -g -O2 -gnatws -gnat12 -gnato -gnatf -g -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -gnatwa 
-gnatec=/tmp/GNAT-TEMP-15.TMP -gnatem=/tmp/GNAT-TEMP-16.TMP 
/<>/src/rules-assignments.adb
| gnatgcc ptree.o -Wl,-z,relro -Wl,-z,now -Wl,--no-undefined b__ptree.o 
/<>/src/binary_map.o /<>/src/generic_file_iterator.o 
/<>/src/options_analyzer.o /<>/src/project_file.o 
/<>/src/implementation_options.o 
/<>/src/project_file-adp.o 
/<>/src/project_file-dummy.o 
/<>/src/project_file-gpr.o 
/<>/src/project_file-factory_full.o 
/<>/src/project_file-factory.o /<>/src/utilities.o 
/<>/src/thick_queries.o /<>/src/a4g_bugs.o 
/<>/src/elements_set.o -L/usr/lib/i386-linux-gnu/ -lgnatcoll 
-lgnatprj -lxmlada_schema -lxmlada_dom -lxmlada_sax -lxmlada_input 
-lxmlada_unicode -lasis -lgnatvsn -g -ldl -L/<>/src/ 
-L/<>/src/ -L/usr/lib/i386-linux-gnu/ada/adalib/asis/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/gnatvsn/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/gnatcoll/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/gnatprj/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/xmlada_schema/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/xmlada_dom/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/xmlada_sax/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/xmlada_input/ 
-L/usr/lib/i386-linux-gnu/ada/adalib/xmlada_unicode/ 
-L/usr/lib/gcc/i686-linux-gnu/9/adalib/ -shared-libgcc -lgnat-9 -lutil -ldl 
-Wl,-rpath-link,/usr/lib/gcc/i686-linux-gnu/9//adalib -o /<>//ptree
| /usr/bin/ld: pfni.o: in function `pfni__print_name':
| ./src/./src/pfni.adb:228: undefined reference to 
`thick_queries__full_name_image'
| /usr/bin/ld: ./src/./src/pfni.adb:263: undefined reference to 
`thick_queries__static_expression_value_image'
| /usr/bin/ld: ./src/./src/pfni.adb:270: undefined reference to 
`thick_queries__discrete_constraining_values'
| /usr/bin/ld: ./src/./src/pfni.adb:273: undefined reference to 
`thick_queries__nil_extended_biggest_int_list'
| /usr/bin/ld: ./src/./src/pfni.adb:273: undefined reference to 
`thick_queries__Oeq'
| /usr/bin/ld: ./src/./src/pfni.adb:273: undefined reference to 
`thick_queries__Oeq'
| /usr/bin/ld: ./src/./src/pfni.adb:279: undefined reference to 
`thick_queries__biggest_int_img'
| /usr/bin/ld: ./src/./src/pfni.adb:286: undefined reference to 
`thick_queries__biggest_int_img'

… and many more linking errors. The full log is available at 
https://buildd.debian.org/status/fetch.php?pkg=adacontrol=i386=1.21r6b-2=1582752946=0

Best
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#952769: isc-dhcp-client: Package "isc-dhcp-client" is not installable in the Debian SID PowerPC Port. Unmet dependencies: "libdns1107" and "libisc1104"

[Hugo Melder]

Package: isc-dhcp-client
Version: 4.4.1-2.1
Severity: grave
Tags: d-i a11y
Justification: renders package unusable



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

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

Versions of packages isc-dhcp-client depends on:
ii  debianutils4.9.1
ii  iproute2   5.5.0-1
ii  libc6  2.29-10
ii  libdns-export1107  1:9.11.14+dfsg-3
ii  libisc-export1104  1:9.11.14+dfsg-3

Versions of packages isc-dhcp-client recommends:
ii  isc-dhcp-common  4.4.1-2.1

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd 
pn  isc-dhcp-client-ddns  
pn  resolvconf

-- no debconf information

Processed: Bug#952031 marked as pending in ruby-active-model-serializers

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952031 [src:ruby-active-model-serializers] ruby-active-model-serializers: 
FTBFS: ERROR: Test "ruby2.7" failed.
Added tag(s) pending.

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

Bug#952031: marked as pending in ruby-active-model-serializers

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #952031 in ruby-active-model-serializers 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/ruby-team/ruby-active-model-serializers/-/commit/86e2905eb40348a97603d112121f08e85f1e2bb7


New patch to fix tests with Ruby 2.7

  * d/patches/fix-tests: Add new patch.
- Fix tests with Ruby 2.7 (closes: #952031).
  * d/patches/series: Add patch fix-tests.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952031

Processed: found 951907 in 2.0-1

[Debian Bug Tracking System]

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

> found 951907 2.0-1
Bug #951907 {Done: Scott Kitterman } [src:python-bleach] 
python-bleach: CVE-2020-6802: mutation XSS vulnerability
Marked as found in versions python-bleach/2.0-1.
> thanks
Stopping processing here.

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

Bug#951907: Suggested Stable Fix

[Salvatore Bonaccorso]

Hi Scott,

On Fri, Feb 28, 2020 at 03:30:01PM -0500, Scott Kitterman wrote:
> On Thursday, February 27, 2020 8:11:32 AM EST Salvatore Bonaccorso wrote:
> > Hi Scott,
> > 
> > On Thu, Feb 27, 2020 at 01:41:44PM +0100, Salvatore Bonaccorso wrote:
> > > Hi,
> > > 
> > > On Thu, Feb 27, 2020 at 01:18:55PM +0100, Salvatore Bonaccorso wrote:
> > > > I think though we mgiht need to revisit the assessment that older
> > > > versions are not affected. Look at the this quick and dirty test
> > > 
> > > > deduced from the testsuite:
> > > So I think versions before are as well vulnerable but a fix will
> > > become not so easy. First back in b07814e0753c ("Extract all html5lib
> > > things into a shim module") in v3.0.0 did split some code from
> > > bleach.sanitizer to bleach.html5lib_shim, and before in 67afdf8ae7d3
> > > ("Prevent HTMLTokenizer from unescaping entities") in v2.1 was quite
> > > refactored.
> > > 
> > > Now I'm not entirely sure how we should fix that for stretch.
> > 
> > Additional point, in earlier version the package depended on html5lib,
> > then the code was vedored out to bleach itself, and then further
> > modified as above. So while it is true one can argue the affected code
> > is not in bleach, the bleach.clean still does not properly sanitize
> > leading to the issue.
> > 
> > It is possibly to hard to actually fix the issue for stretch (and for
> > LTS interest as well in jessie)?
> 
> I don't think so.  I think the lowest risk approach, other than leaving it as 
> is, would be to backport 3.1.1 and use the vendored html5lib.  I gave that a 
> quick try and it doesn't work out of the box.  If that is something the 
> security team would consider, please let me know and I'll spend some time 
> investigating if I can make that work on stretch.

I feared that. Let's not take this risk and ignore the issue for
stretch then, altough it's not optimal. The advisory talks as well of
possible workarounds which might be possible for affected
users/applications for users in stretch.

So will go ahead for the DSA for buster only.

Many thanks for taking time to analyze the situation and reporting
back, much appreciated!

Regards,
Salvatore

Bug#952731: marked as done (xkb-data: Italian keyboard layout not working in some apps)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 20:45:50 +
with message-id 
and subject line Bug#952731: fixed in x11-xkb-utils 7.7+5
has caused the Debian Bug report #952731,
regarding xkb-data: Italian keyboard layout not working in some apps
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.)


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

Dear Maintainer,

Latest version of xkb-data (2.29.1) renders Italian keyboard unusable in some
apps.

In short, in applications like Firefox or Chrome, even if I use an Italian
keyboard, the English layout is activated.

In gedit, gnome-terminal, Libreoffice, reportbug itself and maybe other apps,
Italian keyboard works fine.

Thank you very much in advance,
Domenico




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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: x11-xkb-utils
Source-Version: 7.7+5
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated x11-xkb-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2020 22:13:02 +0200
Source: x11-xkb-utils
Architecture: source
Version: 7.7+5
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 952731
Changes:
 x11-xkb-utils (7.7+5) unstable; urgency=medium
 .
   * control: Use debhelper-compat, bump to 12.
   * setxkbmap 1.3.2.
   * xkbcomp 1.4.3. (Closes: #952731)
   * xkbprint 1.0.5.
   * rules: Use dh_missing.
   * control: Bump policy to 4.5.0.
   * Set source format 1.0.
Checksums-Sha1:
 c704a6da05736f6a3a78252bf4e5024d20b4cdb8 1815 x11-xkb-utils_7.7+5.dsc
 d16cbc9d10659dc83a9970b6c6675047818b7109 1058721 x11-xkb-utils_7.7+5.tar.gz
 3685b669dafc71c5ba5dfdb49df8447d8557ccc0 7089 
x11-xkb-utils_7.7+5_source.buildinfo
Checksums-Sha256:
 4cdfc533112b16a0a0a9ed8a4d779412471824c4b49462bbdd5028d00c9510d4 1815 
x11-xkb-utils_7.7+5.dsc
 5c5343f2e844a6436e5e857fa0a421438afea06348c39b20913c085062524b3d 1058721 
x11-xkb-utils_7.7+5.tar.gz
 d6dca4e69cb819e1fcfde5dba052aa4919f474dc023e59051d0e51fc6be93e15 7089 
x11-xkb-utils_7.7+5_source.buildinfo
Files:
 9a024b2aafa936ebac79165cd3c9ab98 1815 x11 optional x11-xkb-utils_7.7+5.dsc
 473880c66d6ef02d05db605310a3283c 1058721 x11 optional 
x11-xkb-utils_7.7+5.tar.gz
 c59f4b02c5243f1b27c790743b93663e 7089 x11 optional 
x11-xkb-utils_7.7+5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl5ZdHQACgkQy3AxZaiJ
hNw8kA//T0Zwill3ooHZCwByQMWPBXouhe3/9LNIXFPeKhI9eWdgMlnMpGeiPnVj
Iz5E+6qrJQM8dqY3Swfyv/pkh2Q9pta8qTdMn1FfXMI50XVUc3qVSrF9Pnf9mbWi
pp0XQq0rjkJIw+xE9GZp4GNZsHBn+Ykva3fhhehaXTP4UA2LoN4VdeNMYPQlj/Hd
gQpuESIImAYkkdPTc9XbVsAYB1BKiJguwO1CmDGmsPe+rpqzZGvBwqdjhT5L5O57
pM+X2bIM9KIhC3b0AKvC9MjT09Bf5TVn5Z7nJiUVLjQI3EJKpyOgblfm1TU/hP45
OfE38rMYGNcHhDeJmn/Pi/9kO4wSuOEhSUeuf8VpqnRBnDIxwXMrN6cybnxt5eHn
HFIpPQDLjtkdLTphgl3tDvinyD16KPkW7nhFgZoKaKCRIQEE3A71jrnFC0qq7qUi
BxHxcm+zW+jHr/hAy70qC8RMcmjNGhC8Q6sP7Hj4TGWSPS7NaAllYIFnnnhYvJI1
kmK4N+mN6RQW32/4whLQ3e5WojKQ+xnRAJDchIM7ftnjhs1PO+y3Y3xrV6bJP5H3
xymifbHWjfYFJVuZckMcT3qgX1gYC/RC7U3F/P8eL9OeYcbFYXmvznt1/0/pf+UO
BGNMdzUY00DC3tYQozRosL4SLK5zHEqcn4gN8dxGeSaUEdWYd5A=
=45R+
-END PGP SIGNATURE End Message ---

Bug#952314: marked as done (php-masterminds-html5: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 20:45:06 +
with message-id 
and subject line Bug#952314: fixed in php-masterminds-html5 2.7.0+dfsg-3
has caused the Debian Bug report #952314,
regarding php-masterminds-html5: FTBFS: tests 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.)


-- 
952314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-masterminds-html5
Version: 2.7.0+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHPUnit 8.5.2 by Sebastian Bergmann and contributors.
> 
>   Warning - The configuration file did not pass validation!
>   The following problems have been detected:
> 
>   Line 9:
>   - Element 'blacklist': This element is not expected. Expected is ( 
> whitelist ).
> 
>   Test results may not be as expected.
> 
> 
> .R..W...W..R...R...  63 / 170 ( 
> 37%)
> R...R..EE.R..R..R.. 126 / 170 ( 
> 74%)
> .R.R170 / 170 
> (100%)
> 
> Time: 56 ms, Memory: 6.00 MB
> 
> There were 2 errors:
> 
> 1) 
> Masterminds\HTML5\Tests\Parser\TokenizerTest::testTagsWithAttributeAndMissingName
> Trying to access array offset on value of type null
> 
> /<>/test/HTML5/Parser/TokenizerTest.php:29
> /<>/test/HTML5/Parser/TokenizerTest.php:488
> 
> 2) Masterminds\HTML5\Tests\Parser\TokenizerTest::testTagNotClosedAfterTagName
> Trying to access array offset on value of type null
> 
> /<>/test/HTML5/Parser/TokenizerTest.php:29
> /<>/test/HTML5/Parser/TokenizerTest.php:514
> 
> --
> 
> There were 2 warnings:
> 
> 1) Masterminds\HTML5\Tests\Html5Test::testEncodingUtf8
> Using assertContains() with string haystacks is deprecated and will not be 
> supported in PHPUnit 9. Refactor your test to use 
> assertStringContainsString() or assertStringContainsStringIgnoringCase() 
> instead.
> 
> 2) Masterminds\HTML5\Tests\Html5Test::testAttributes
> Using assertContains() with string haystacks is deprecated and will not be 
> supported in PHPUnit 9. Refactor your test to use 
> assertStringContainsString() or assertStringContainsStringIgnoringCase() 
> instead.
> 
> --
> 
> There were 10 risky tests:
> 
> 1) Masterminds\HTML5\Tests\ElementsTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 2) Masterminds\HTML5\Tests\Html5Test::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 3) Masterminds\HTML5\Tests\Parser\CharacterReferenceTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 4) Masterminds\HTML5\Tests\Parser\DOMTreeBuilderTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 5) Masterminds\HTML5\Tests\Parser\ScannerTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 6) Masterminds\HTML5\Tests\Parser\TokenizerTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 7) Masterminds\HTML5\Tests\Parser\TreeBuildingRulesTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 8) Masterminds\HTML5\Tests\Parser\UTF8UtilsTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 9) Masterminds\HTML5\Tests\Serializer\OutputRulesTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> 10) Masterminds\HTML5\Tests\Serializer\TraverserTest::testFoo
> This test did not perform any assertions
> 
> /<>/test/HTML5/TestCase.php:14
> 
> ERRORS!
> Tests: 170, Assertions: 2023, Errors: 2, Warnings: 2, Risky: 10.
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/php-masterminds-html5_2.7.0+dfsg-2_unstable.log

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

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

Bug#951907: Suggested Stable Fix

[Scott Kitterman]

On Thursday, February 27, 2020 8:11:32 AM EST Salvatore Bonaccorso wrote:
> Hi Scott,
> 
> On Thu, Feb 27, 2020 at 01:41:44PM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> > 
> > On Thu, Feb 27, 2020 at 01:18:55PM +0100, Salvatore Bonaccorso wrote:
> > > I think though we mgiht need to revisit the assessment that older
> > > versions are not affected. Look at the this quick and dirty test
> > 
> > > deduced from the testsuite:
> > So I think versions before are as well vulnerable but a fix will
> > become not so easy. First back in b07814e0753c ("Extract all html5lib
> > things into a shim module") in v3.0.0 did split some code from
> > bleach.sanitizer to bleach.html5lib_shim, and before in 67afdf8ae7d3
> > ("Prevent HTMLTokenizer from unescaping entities") in v2.1 was quite
> > refactored.
> > 
> > Now I'm not entirely sure how we should fix that for stretch.
> 
> Additional point, in earlier version the package depended on html5lib,
> then the code was vedored out to bleach itself, and then further
> modified as above. So while it is true one can argue the affected code
> is not in bleach, the bleach.clean still does not properly sanitize
> leading to the issue.
> 
> It is possibly to hard to actually fix the issue for stretch (and for
> LTS interest as well in jessie)?

I don't think so.  I think the lowest risk approach, other than leaving it as 
is, would be to backport 3.1.1 and use the vendored html5lib.  I gave that a 
quick try and it doesn't work out of the box.  If that is something the 
security team would consider, please let me know and I'll spend some time 
investigating if I can make that work on stretch.

Scott K

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

Processed: limit source to php-masterminds-html5, tagging 952314

[Debian Bug Tracking System]

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

> limit source php-masterminds-html5
Limiting to bugs with field 'source' containing at least one of 
'php-masterminds-html5'
Limit currently set to 'source':'php-masterminds-html5'

> tags 952314 + pending
Bug #952314 [src:php-masterminds-html5] php-masterminds-html5: FTBFS: tests 
failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#952251: sympy: FTBFS: make[2]: python: Command not found

[Steve Langasek]

Package: sympy
Followup-For: Bug #952251
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

This should be addressed by fixing the upstream build rules to invoke
python3 instead of python.  Please find attached a patch which has been
uploaded to Ubuntu to fix this failure.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sympy-1.5.1/debian/patches/python3-not-python.patch 
sympy-1.5.1/debian/patches/python3-not-python.patch
--- sympy-1.5.1/debian/patches/python3-not-python.patch 1969-12-31 
16:00:00.0 -0800
+++ sympy-1.5.1/debian/patches/python3-not-python.patch 2020-02-28 
09:23:34.0 -0800
@@ -0,0 +1,17 @@
+Author: Steve Langasek 
+Description: invoke python3 for building, not the deprecated python.
+Last-Update: 2020-02-28
+Bug-Debian: https://bugs.debian.org/952251
+
+Index: sympy-1.5.1/doc/Makefile
+===
+--- sympy-1.5.1.orig/doc/Makefile
 sympy-1.5.1/doc/Makefile
+@@ -1,6 +1,6 @@
+ # Makefile for Sphinx documentation
+ #
+-PYTHON   = python
++PYTHON   = python3
+ RST2HTML = rst2html
+ 
+ # You can set these variables from the command line.
diff -Nru sympy-1.5.1/debian/patches/series sympy-1.5.1/debian/patches/series
--- sympy-1.5.1/debian/patches/series   2020-02-07 09:53:35.0 -0800
+++ sympy-1.5.1/debian/patches/series   2020-02-28 09:23:34.0 -0800
@@ -3,3 +3,4 @@
 03_sphinx_conf.patch
 04_doc_makefile.patch
 05_sphinx_math_dollar.patch
+python3-not-python.patch

Bug#952765: calendarserver: Should be removed from Debian

[Boyuan Yang]

Source: calendarserver
Version: 9.2+dfsg-1
Tags: sid
Severity: serious
X-Debbugs-CC: amaramra...@users.sourceforge.net

Dear calendarserver maintainer,

Unfortunately the upstream of package calendarserver (Apple Inc.) has
terminated the development of this software and had the github source code
repo archived. This is a python2-only software and is affected by python2
removal in Debian.

I guess it's high time for us to remove it from Debian. I will submit a
removal request 7 days later (on March 06, 2020). If you have any doubts,
please let me know ASAP.

-- 
Best Regards,
Boyuan Yang


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

Processed: bug 937256 is not forwarded

[Debian Bug Tracking System]

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

> notforwarded 937256
Bug #937256 [ftp.debian.org] ROM: Please remove pbh5tools since it is 
unmaintained and there is no Python2 port
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Timo Aaltonen]

On 28.2.2020 18.50, Domenico Cufalo wrote:
> This is my output:
> 
> $ gsettings get org.gnome.desktop.input-sources sources
> [('xkb', 'it'), ('xkb', 'gr'), ('xkb', 'de')]
> 
> Obviously the command "setxkbmap it" solves the problem, at least for
> the current session.
> 
> In Italian keyboard, for example, round brackets are above the numbers 8
> and 9, instead of 9 and 0.
> 
> The issue arose after updating the following packages:
> 
> Start-Date: 2020-02-28  00:30:26
> Commandline: apt upgrade
> Requested-By: domenico (1000)
> Upgrade: libqt5test5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
> qt5-gtk-platformtheme:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
> libqt5dbus5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
> libqt5sql5-sqlite:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
> libqt5widgets5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9), xkb-data:amd64
> (2.26-2, 2.29-1), libqt5xml5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
> libqt5printsupport5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
> libqt5concurrent5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5gui5:amd64
> (5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5core5a:amd64 (5.12.5+dfsg-8,
> 5.12.5+dfsg-9), libxml2:amd64 (2.9.10+dfsg-3, 2.9.10+dfsg-4),
> libqt5network5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5sql5:amd64
> (5.12.5+dfsg-8, 5.12.5+dfsg-9)
> End-Date: 2020-02-28  00:30:33
> 
> In the meantime, I think I will downgrade the package...
> 
> Regards,
> Domenico
> 

I'm pretty sure the reason for the failure is that our xkbcomp is too
old, the newer versions ignore errors caused by having keycodes above
255.. and launching Xwayland in weston clearly shows a bunch of errors
from xkbcomp. Our version (1.4.0) is almost 2y old and this was fixed
upstream in 1.4.1 in June 2018.

So I'll update x11-xkb-utils, thanks for the patience..


-- 
t

Bug#948834: closed by Simon McVittie (Re: Bug#948834: glib2.0: FTBFS: gio/tests/gsocketclient-slow.c: Error resolving ?localhost?: Name or service not known)

[Simon McVittie]

On Fri, 28 Feb 2020 at 18:34:53 +0100, Mattia Rizzolo wrote:
> TBH, I haven't spotted any other package failing for this...

With hindsight, dbus is the other one I'm aware of. As discussed on IRC,
I thought that was a pbuilder bug, and it probably *was* a pbuilder bug -
but after fixing the pbuilder bug, if I hadn't already worked around the
FTBFS by using 127.0.0.1, dbus would still have failed in pbuilder for
the same reasons that glib2.0 did.

smcv

Bug#952325: marked as done (php-tijsverkoyen-css-to-inline-styles: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 19:36:06 +
with message-id 
and subject line Bug#952325: fixed in php-tijsverkoyen-css-to-inline-styles 
2.2.2-3
has caused the Debian Bug report #952325,
regarding php-tijsverkoyen-css-to-inline-styles: FTBFS: tests 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.)


-- 
952325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-tijsverkoyen-css-to-inline-styles
Version: 2.2.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap src/autoload.php
> PHPUnit 8.5.2 by Sebastian Bergmann and contributors.
> 
>   Warning - The configuration file did not pass validation!
>   The following problems have been detected:
> 
>   Line 12:
>   - Element 'phpunit', attribute 'syntaxCheck': The attribute 'syntaxCheck' 
> is not allowed.
> 
>   Test results may not be as expected.
> 
> 
> .WF.. 41 / 41 
> (100%)
> 
> Time: 32 ms, Memory: 6.00 MB
> 
> There was 1 warning:
> 
> 1) 
> TijsVerkoyen\CssToInlineStyles\tests\CssToInlineStylesTest::testNoXMLHeaderPresent
> Using assertNotContains() with string haystacks is deprecated and will not be 
> supported in PHPUnit 9. Refactor your test to use 
> assertStringNotContainsString() or 
> assertStringNotContainsStringIgnoringCase() instead.
> 
> --
> 
> There was 1 failure:
> 
> 1) TijsVerkoyen\CssToInlineStyles\tests\CssToInlineStylesTest::testSpecificity
> Failed asserting that two strings are equal.
> --- Expected
> +++ Actual
> @@ @@
>  '\n
> -  '
> +  \n
> +'
> 
> /<>/tests/CssToInlineStylesTest.php:263
> /<>/tests/CssToInlineStylesTest.php:204
> 
> FAILURES!
> Tests: 41, Assertions: 93, Failures: 1, Warnings: 1.
> make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/php-tijsverkoyen-css-to-inline-styles_2.2.2-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: php-tijsverkoyen-css-to-inline-styles
Source-Version: 2.2.2-3
Done: =?utf-8?q?David_Pr=C3=A9vot?= 

We believe that the bug you reported is fixed in the latest version of
php-tijsverkoyen-css-to-inline-styles, 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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated 
php-tijsverkoyen-css-to-inline-styles package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 08:54:40 -1000
Source: php-tijsverkoyen-css-to-inline-styles
Architecture: source
Version: 2.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 952325
Changes:
 php-tijsverkoyen-css-to-inline-styles (2.2.2-3) unstable; urgency=medium
 .
   * Adapt expectation to PHP 7.4 output (Closes: #952325)
   * Set upstream metadata fields: Bug-Submit.
   * Update Standards-Version to 4.5.0
   * Simplify examples layout
Checksums-Sha1:
 0b316eda6707113ff089eba5191030ee668fc01d 2013 
php-tijsverkoyen-css-to-inline-styles_2.2.2-3.dsc
 268271ffe819f72395e93bc1adf562122da1f7f1 5620 
php-tijsverkoyen-css-to-inline-styles_2.2.2-3.debian.tar.xz
 2b66251166558fde94ca5ff5e947255bc8c346bd 7505 
php-tijsverkoyen-css-to-inline-styles_2.2.2-3_amd64.buildinfo
Checksums-Sha256:
 12e1eef92537ebd7193db214a6cf1ccc29bb8a1942bb505fafd9ef95d90b4abc 2013 
php-tijsverkoyen-css-to-inline-styles_2.2.2-3.dsc
 58a8a06f544d0d67e32683dd30be4003d632375faf8bd51d76de79644b1460ee 5620 

Bug#952763: marked as done (One-page print jobs to foo2zjs printers are empty)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 20:23:13 +0100
with message-id <3145090.19poqlc...@odyx.org>
and subject line Re: Bug#952763: One-page print jobs to foo2zjs printers are 
empty
has caused the Debian Bug report #952763,
regarding One-page print jobs to foo2zjs printers are empty
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.)


-- 
952763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups-filters
Version: 1.27.1-1
Severity: serious
Tags: bullseye

1.27.1 is affected by a serious bug, fixed in 1.27.2:

- foomatic-rip: Zero-page-job handling changes made the last
  page of PostScript files not printed, also turning one-page
  jobs into zero-page jobs (Issue #200, Issue #206, Issue
  #208, Pull request #209, Pull request #210, Pull request
  #211).

As maintainer, I'm therefore filing this bug to let the BTS know, and
accelerate the transition of fixed versions.

I'll send the -done immediately when I get the bugnumber.
--- End Message ---
--- Begin Message ---
Version: 1.27.1-2

Le vendredi, 28 février 2020, 20.18:51 h CET Didier 'OdyX' Raboud a écrit :
> Package: cups-filters
> Version: 1.27.1-1
> Severity: serious
> Tags: bullseye
> 
> 1.27.1 is affected by a serious bug, fixed in 1.27.2:
> 
>   - foomatic-rip: Zero-page-job handling changes made the last
> page of PostScript files not printed, also turning one-page
> jobs into zero-page jobs (Issue #200, Issue #206, Issue
> #208, Pull request #209, Pull request #210, Pull request
> #211).

This was fixed simply in 1.27.1-2, better in 1.27.1-3, and is completely fixed 
in upstream's 1.27.2. Marking as such.

Cheers,

OdyX

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

Bug#952763: One-page print jobs to foo2zjs printers are empty

[Didier 'OdyX' Raboud]

Package: cups-filters
Version: 1.27.1-1
Severity: serious
Tags: bullseye

1.27.1 is affected by a serious bug, fixed in 1.27.2:

- foomatic-rip: Zero-page-job handling changes made the last
  page of PostScript files not printed, also turning one-page
  jobs into zero-page jobs (Issue #200, Issue #206, Issue
  #208, Pull request #209, Pull request #210, Pull request
  #211).

As maintainer, I'm therefore filing this bug to let the BTS know, and
accelerate the transition of fixed versions.

I'll send the -done immediately when I get the bugnumber.

Bug#952327: marked as done (php-mikey179-vfsstream: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 19:10:00 +
with message-id 
and subject line Bug#952327: fixed in php-mikey179-vfsstream 1.6.8-2
has caused the Debian Bug report #952327,
regarding php-mikey179-vfsstream: FTBFS: tests 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.)


-- 
952327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-mikey179-vfsstream
Version: 1.6.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --include-path src/main/php
> PHPUnit 8.5.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 7.4.3
> Configuration: /<>/phpunit.xml.dist
> 
>   Warning - The configuration file did not pass validation!
>   The following problems have been detected:
> 
>   Line 16:
>   - Element 'phpunit', attribute 'mapTestClassNameToCoveredClassName': The 
> attribute 'mapTestClassNameToCoveredClassName' is not allowed.
> 
>   Line 18:
>   - Element 'testsuite': The attribute 'name' is required but missing.
> 
>   Line 33:
>   - Element 'log', attribute 'charset': The attribute 'charset' is not 
> allowed.
>   - Element 'log', attribute 'yui': The attribute 'yui' is not allowed.
>   - Element 'log', attribute 'highlight': The attribute 'highlight' is not 
> allowed.
> 
>   Line 35:
>   - Element 'log', attribute 'logIncompleteSkipped': The attribute 
> 'logIncompleteSkipped' is not allowed.
> 
>   Test results may not be as expected.
> 
> Error: No code coverage driver is available
> 
> ..W.FEE  63 / 404 ( 
> 15%)
> ...WW..W..E 126 / 404 ( 
> 31%)
> ...W..WWW.. 189 / 404 ( 
> 46%)
> ..FEFEF.E.EE..EEE.E 252 / 404 ( 
> 62%)
> .E.S...SS...S.. 315 / 404 ( 
> 77%)
> ...EE.F.EEE..R..RF.FFFW 378 / 404 ( 
> 93%)
> WW.SW...WW  404 / 404 
> (100%)
> 
> Time: 4.18 seconds, Memory: 12.00 MB
> 
> There were 30 errors:
> 
> 1) 
> org\bovigo\vfs\PermissionsTestCase::touchOnNonWriteableDirectoryDoesNotCreateFile
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/main/php/org/bovigo/vfs/vfsStreamWrapper.php:380
> /<>/src/main/php/org/bovigo/vfs/vfsStreamWrapper.php:512
> /<>/src/test/php/org/bovigo/vfs/PermissionsTestCase.php:115
> 
> 2) org\bovigo\vfs\UnlinkTestCase::unlinkNonExistingFileTriggersError
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/main/php/org/bovigo/vfs/vfsStreamWrapper.php:742
> /<>/src/test/php/org/bovigo/vfs/UnlinkTestCase.php:53
> 
> 3) 
> org\bovigo\vfs\vfsStreamExLockTestCase::filePutContentsLockShouldReportError
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/test/php/org/bovigo/vfs/vfsStreamExLockTestCase.php:38
> 
> 4) 
> org\bovigo\vfs\vfsStreamWrapperMkDirTestCase::mkDirShouldNotOverwriteExistingDirectories
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/main/php/org/bovigo/vfs/vfsStreamWrapper.php:844
> /<>/src/test/php/org/bovigo/vfs/vfsStreamWrapperDirTestCase.php:211
> 
> 5) 
> org\bovigo\vfs\vfsStreamWrapperMkDirTestCase::mkDirShouldNotOverwriteExistingFiles
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/main/php/org/bovigo/vfs/vfsStreamWrapper.php:844
> /<>/src/test/php/org/bovigo/vfs/vfsStreamWrapperDirTestCase.php:236
> 
> 6) 
> org\bovigo\vfs\vfsStreamWrapperMkDirTestCase::canNotIterateOverNonReadableDirectory
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/test/php/org/bovigo/vfs/vfsStreamWrapperDirTestCase.php:274
> 
> 7) 
> org\bovigo\vfs\vfsStreamWrapperMkDirTestCase::unlinkCanNotRemoveNonEmptyDirectory
> Error: Call to undefined method PHPUnit\Util\ErrorHandler::handleError()
> 
> /<>/src/test/bootstrap.php:39
> /<>/src/main/php/org/bovigo/vfs/vfsStreamWrapper.php:747
> 

Processed: limit source to php-tijsverkoyen-css-to-inline-styles, tagging 952325

[Debian Bug Tracking System]

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

> limit source php-tijsverkoyen-css-to-inline-styles
Limiting to bugs with field 'source' containing at least one of 
'php-tijsverkoyen-css-to-inline-styles'
Limit currently set to 'source':'php-tijsverkoyen-css-to-inline-styles'

> tags 952325 + pending
Bug #952325 [src:php-tijsverkoyen-css-to-inline-styles] 
php-tijsverkoyen-css-to-inline-styles: FTBFS: tests failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#951970: marked as done (gnuplot: FTBFS: configure: error: texdir is not given and there is no kpsexpand, please tell where to install)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 18:49:16 +
with message-id 
and subject line Bug#951970: fixed in gnuplot 5.2.8+dfsg1-2
has caused the Debian Bug report #951970,
regarding gnuplot: FTBFS: configure: error: texdir is not given and there 
is no kpsexpand, please tell where to install
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.)


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

Hi,

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

Relevant part (hopefully):
> checking for dvips... dvips
> checking for troff... troff
> checking for latex2html... latex2html
> checking for kpsexpand... no
> checking for texhash... texhash
> configure: error: texdir is not given and there is no kpsexpand, please 
> tell where to install
> make[1]: *** [debian/rules:46: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/gnuplot_5.2.8+dfsg1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gnuplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2020 19:32:30 +0100
Source: gnuplot
Architecture: source
Version: 5.2.8+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Closes: 951970
Changes:
 gnuplot (5.2.8+dfsg1-2) unstable; urgency=medium
 .
   * [cd85ca9] Set texdir explicitly. (Closes: #951970)
   * [bc20a5d] Set Standards-Version to 4.5.0
   * [dfa649b] Wrap long lines in changelog entries: 5.2.6+dfsg1-2~exp1, 
4.2.2-1,
 4.2~rc4-1, 4.2~rc2-1.
   * [7161164] Set upstream metadata fields: Repository.
Checksums-Sha1:
 8e33cb0bf6d8b7c2f07a1badb889e6d170ee5559 2690 gnuplot_5.2.8+dfsg1-2.dsc
 312d480d4e08372ff5881290636cdbbda86d61b3 29840 
gnuplot_5.2.8+dfsg1-2.debian.tar.xz
 455a0a425c7fb5cf71716c47ca08e30775590e03 10656 
gnuplot_5.2.8+dfsg1-2_source.buildinfo
Checksums-Sha256:
 2a462c79d665b411e7341406b7ca443d860e43d73e41c9e8afca3de8be0dff70 2690 
gnuplot_5.2.8+dfsg1-2.dsc
 3e9f426389d7bb4e210cc813810ca43d6574184dcd7f76344e9a8e185c1da8ce 29840 
gnuplot_5.2.8+dfsg1-2.debian.tar.xz
 5160ead0308b082d5b18c5c78dbc4dfab63613c1c49b7f4fec476d67d2efd64e 10656 
gnuplot_5.2.8+dfsg1-2_source.buildinfo
Files:
 8826fe3792927acd825006f6ed25a986 2690 math optional gnuplot_5.2.8+dfsg1-2.dsc
 8b787c455ea89cc737f9d7bc5ed72080 29840 math optional 
gnuplot_5.2.8+dfsg1-2.debian.tar.xz
 68559e7758092ac8e9d5b90459e02d84 10656 math optional 
gnuplot_5.2.8+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl5ZXQ8ACgkQ0+Fzg8+n
/waVqw//bhG2vmsFaKbGuo6D5OaKlF2vmftM43wRN+eI8c9dCOTPJCPLMawOKzDa
41hH9nWGUUb78Z2Fxr3Vo4ttK/+1tWJD+jOm6UN4SfPe5dE9vH8h0leeJQDMFRsQ
/NIFF46MJwCCeki0RkDsfx7IWfkNL3LmKSfs1o9OGRf7z+eSbZaowU/vA+yGND+o
o4OUIWRKNmlEpl+r2D0cCHfuqP0WXxf3pla6FGk5+MO5aKPV+GwBtW6tanvBN3no
oSY51KmMQrqjoEmqUmo3PX+WV27BdzH2T56WNqOuJig+37zNenit18fyhYm/FmVL
yk+B4eFUYwyDa4rEN+cRy0oAqRccs1gtRXLNs0PcFslTSwD6QqQoSUlyB4sOccQq
2GtDiXJwkbXvCzMw6r70mhDrsITg4o6A/IXXxyQOYLSzyAlQFrF+p8KgVQAowe86
hwvfv0fu1GbD8hwRGDaFQYurY0+V8Nhrx/CfBYGDIy+/3mRJ+aWI5nuN5NMGkAOF
LR93d9P3bIlgi2WiDWP25dYZpw2WJgzgztLxs72wFPueOh0nQFOSR0c09hRVBT2P

Processed: limit source to php-mikey179-vfsstream, tagging 952327

[Debian Bug Tracking System]

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

> limit source php-mikey179-vfsstream
Limiting to bugs with field 'source' containing at least one of 
'php-mikey179-vfsstream'
Limit currently set to 'source':'php-mikey179-vfsstream'

> tags 952327 + pending
Bug #952327 [src:php-mikey179-vfsstream] php-mikey179-vfsstream: FTBFS: tests 
failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#897890: marked as done (yp-tools: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 18:19:47 +
with message-id 
and subject line Bug#897890: fixed in yp-tools 3.3-5.2
has caused the Debian Bug report #897890,
regarding yp-tools: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yp-tools
Version: 3.3-5.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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

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

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/yp-tools_3.3-5.1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -I. -I.. 
-DLOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
-Wbad-function-cast -Wcast-align -Winline -Wnested-externs -Wshadow 
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Werror 
-I/usr/include/tirpc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c ypwhich.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -W -Wall -Wbad-function-cast 
-Wcast-align -Winline -Wnested-externs -Wshadow -Wmissing-declarations 
-Wmissing-prototypes -Wstrict-prototypes -Wundef -Werror -I/usr/include/tirpc 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -o ypwhich ypwhich.o ../lib/libyptools.a 
../lib/libnis.la -ltirpc 
libtool: link: gcc -W -Wall -Wbad-function-cast -Wcast-align -Winline 
-Wnested-externs -Wshadow -Wmissing-declarations -Wmissing-prototypes 
-Wstrict-prototypes -Wundef -Werror -I/usr/include/tirpc -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -o .libs/ypwhich ypwhich.o  
../lib/libyptools.a ../lib/.libs/libnis.so -ltirpc
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -I. -I.. 
-DLOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
-Wbad-function-cast -Wcast-align -Winline -Wnested-externs -Wshadow 
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Werror 
-I/usr/include/tirpc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c ypmatch.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -W -Wall -Wbad-function-cast 
-Wcast-align -Winline -Wnested-externs -Wshadow -Wmissing-declarations 
-Wmissing-prototypes -Wstrict-prototypes -Wundef -Werror -I/usr/include/tirpc 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -o ypmatch ypmatch.o ../lib/libyptools.a 
../lib/libnis.la -ltirpc 
libtool: link: gcc -W -Wall -Wbad-function-cast -Wcast-align -Winline 
-Wnested-externs -Wshadow -Wmissing-declarations -Wmissing-prototypes 
-Wstrict-prototypes -Wundef -Werror -I/usr/include/tirpc -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -o .libs/ypmatch ypmatch.o  
../lib/libyptools.a ../lib/.libs/libnis.so -ltirpc
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -I. -I.. 
-DLOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
-Wbad-function-cast -Wcast-align -Winline -Wnested-externs -Wshadow 
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Werror 
-I/usr/include/tirpc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c ypcat.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -W -Wall -Wbad-function-cast 
-Wcast-align -Winline -Wnested-externs -Wshadow -Wmissing-declarations 

Bug#925854: marked as done (vtgrab: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 18:13:04 +
with message-id 
and subject line Bug#925854: fixed in vtgrab 0.1.8-3.2
has caused the Debian Bug report #925854,
regarding vtgrab: ftbfs with GCC-9
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
/usr/bin/ld: nrvc.c:(.text+0xab0): undefined reference to `wattr_off'
/usr/bin/ld: nrvc.c:(.text+0xac5): undefined reference to `wprintw'
/usr/bin/ld: nrvc.c:(.text+0xae5): undefined reference to `wmove'
/usr/bin/ld: nrvc.c:(.text+0xafa): undefined reference to `wprintw'
/usr/bin/ld: nrvc.c:(.text+0xb14): undefined reference to `wmove'
/usr/bin/ld: nrvc.c:(.text+0xb1e): undefined reference to `doupdate'
/usr/bin/ld: nrvc.c:(.text+0xb77): undefined reference to `wmove'
/usr/bin/ld: nrvc.c:(.text+0xb8c): undefined reference to `wprintw'
/usr/bin/ld: nrvc.c:(.text+0xc20): undefined reference to `wprintw'
/usr/bin/ld: nrvc.c:(.text+0xc33): undefined reference to `wattr_on'
/usr/bin/ld: nrvc.c:(.text+0xc71): undefined reference to `wprintw'
/usr/bin/ld: nrvc.c:(.text+0xc84): undefined reference to `wattr_off'
/usr/bin/ld: nrvc.c:(.text+0xc99): undefined reference to `wprintw'
/usr/bin/ld: nrvc.c:(.text+0xcb9): undefined reference to `wprintw'
/usr/bin/ld: nrvc.o: in function `setup_colours':
nrvc.c:(.text+0xcf5): undefined reference to `start_color'
/usr/bin/ld: nrvc.c:(.text+0xcfb): undefined reference to `COLOR_PAIRS'
/usr/bin/ld: nrvc.o: in function `do_colourmap_setup':
nrvc.c:(.text+0xe2): undefined reference to `init_pair'
/usr/bin/ld: nrvc.o: in function `main':
nrvc.c:(.text.startup+0x1ee): undefined reference to `initscr'
/usr/bin/ld: nrvc.c:(.text.startup+0x1f5): undefined reference to `endwin'
/usr/bin/ld: nrvc.c:(.text.startup+0x1ff): undefined reference to `cbreak'
/usr/bin/ld: nrvc.c:(.text.startup+0x204): undefined reference to `noecho'
/usr/bin/ld: nrvc.c:(.text.startup+0x209): undefined reference to `nonl'
/usr/bin/ld: nrvc.c:(.text.startup+0x210): undefined reference to `stdscr'
/usr/bin/ld: nrvc.c:(.text.startup+0x217): undefined reference to `intrflush'
/usr/bin/ld: nrvc.c:(.text.startup+0x21e): undefined reference to `stdscr'
/usr/bin/ld: nrvc.c:(.text.startup+0x228): undefined reference to `keypad'
/usr/bin/ld: nrvc.c:(.text.startup+0x589): undefined reference to `stdscr'
/usr/bin/ld: nrvc.c:(.text.startup+0x792): undefined reference to `delwin'
/usr/bin/ld: nrvc.c:(.text.startup+0x79c): undefined reference to `curs_set'
/usr/bin/ld: nrvc.c:(.text.startup+0x7a6): undefined reference to `doupdate'
/usr/bin/ld: nrvc.c:(.text.startup+0x932): undefined reference to `delwin'
/usr/bin/ld: nrvc.c:(.text.startup+0x94e): undefined reference to `newwin'
/usr/bin/ld: nrvc.c:(.text.startup+0x96f): undefined reference to `wattr_on'
/usr/bin/ld: nrvc.c:(.text.startup+0x987): undefined reference to `mvwprintw'
/usr/bin/ld: nrvc.c:(.text.startup+0x98e): undefined reference to `curs_set'
/usr/bin/ld: nrvc.c:(.text.startup+0x9c8): undefined reference to `doupdate'

Processed: limit source to pdepend, tagging 952315

[Debian Bug Tracking System]

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

> limit source pdepend
Limiting to bugs with field 'source' containing at least one of 'pdepend'
Limit currently set to 'source':'pdepend'

> tags 952315 + pending
Bug #952315 [src:pdepend] pdepend: FTBFS: tests failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#948834: closed by Simon McVittie (Re: Bug#948834: glib2.0: FTBFS: gio/tests/gsocketclient-slow.c: Error resolving ?localhost?: Name or service not known)

[Mattia Rizzolo]

> On Wed, 26 Feb 2020 at 11:33:29 +, Simon McVittie wrote:
> > The good news is that GLib 2.63.x should fix this, because GLib 2.63.x
> > implements
> > 
> > and hard-codes "localhost" to resolve to 127.0.0.1 and/or ::1 (depending
> > on the requested address family).
> 
> This appears to work on reproducible-builds, so I'm closing this bug
> as fixed in experimental. The first GLib stable release with this in,
> 2.64.0, has just been released, so a fixed version should be on its way
> to unstable fairly soon.

That's great!

> I've opened a separate glibc bug report to query whether this is
> considered to be a glibc bug - I don't think fixing it in every consumer
> of the getaddrinfo() API is something that can scale.

TBH, I haven't spotted any other package failing for this...
I reckon glib2.0 has a much more extensive testuite than most packages
though…

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Domenico Cufalo]

This is my output:

$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'it'), ('xkb', 'gr'), ('xkb', 'de')]

Obviously the command "setxkbmap it" solves the problem, at least for the
current session.

In Italian keyboard, for example, round brackets are above the numbers 8
and 9, instead of 9 and 0.

The issue arose after updating the following packages:

Start-Date: 2020-02-28  00:30:26
Commandline: apt upgrade
Requested-By: domenico (1000)
Upgrade: libqt5test5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
qt5-gtk-platformtheme:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
libqt5dbus5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5sql5-sqlite:amd64
(5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5widgets5:amd64 (5.12.5+dfsg-8,
5.12.5+dfsg-9), xkb-data:amd64 (2.26-2, 2.29-1), libqt5xml5:amd64
(5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5printsupport5:amd64 (5.12.5+dfsg-8,
5.12.5+dfsg-9), libqt5concurrent5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
libqt5gui5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9), libqt5core5a:amd64
(5.12.5+dfsg-8, 5.12.5+dfsg-9), libxml2:amd64 (2.9.10+dfsg-3,
2.9.10+dfsg-4), libqt5network5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9),
libqt5sql5:amd64 (5.12.5+dfsg-8, 5.12.5+dfsg-9)
End-Date: 2020-02-28  00:30:33

In the meantime, I think I will downgrade the package...

Regards,
Domenico

Bug#950772: Patch: swupdate: FTBFS during separate arch/indep builds

[林上智]

Hi Germann,

Iwamatsu-san and I have reviewed and merged the MR today, thank you
for the patch.

Regarding the MR in mtd-utils, I've merged the MR[1] as well.

[1] https://salsa.debian.org/debian/mtd-utils/merge_requests/5

Hi Iwamatsu-san,

Thank you for your branch clean-up today.

I think we need to keep "dfsg" in the version number since we need to
repack the source and remove minified JavaScript objects which
violated DFSG from upstream files.

SZ

Bastian Germann  於 2020年2月24日 週一 下午9:37寫道：
>
> When you take a closer look, please also consider my changes in #911821
> (mtd-utils).

Bug#936630: Re: Bug#936630: gnumed-client: upstream has (unreleased) py3 support

[Karsten Hilbert]

On Wed, Feb 05, 2020 at 11:17:39AM -0500, Scott Talbert wrote:

> BTW, the gnumed website seems to be having some problems.

I'm working on it.

https://www.gnumed.de/

Suitable for the watch file could be

https://www.gnumed.de/downloads/gnumed-versions.txt

or

https://www.gnumed.de/documentation/

or

https://www.gnumed.de/downloads/

Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B

Bug#952104: marked as done (yorick: FTBFS: mpi.h:322:57: error: expected expression before ‘_Static_assert’)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 16:21:36 +
with message-id 
and subject line Bug#952104: fixed in yorick 2.2.04+dfsg1-11
has caused the Debian Bug report #952104,
regarding yorick: FTBFS: mpi.h:322:57: error: expected expression before 
‘_Static_assert’
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/mpy.openmpi'
> /usr/bin/mpicc.openmpi -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -I. -I/<>/mpy.openmpi/../relocate/include 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mpy.o mpy.c
> In file included from mpy.c:11:
> mpy.c: In function ‘mpy_initialize’:
> /usr/lib/x86_64-linux-gnu/openmpi/include/mpi.h:322:57: error: expected 
> expression before ‘_Static_assert’
>   322 | #define THIS_SYMBOL_WAS_REMOVED_IN_MPI30(func, newfunc) 
> _Static_assert(0, #func " was removed in MPI-3.0.  Use " #newfunc " instead.")
>   | ^~
> /usr/lib/x86_64-linux-gnu/openmpi/include/mpi.h:2845:34: note: in expansion 
> of macro ‘THIS_SYMBOL_WAS_REMOVED_IN_MPI30’
>  2845 | #define MPI_Errhandler_set(...)  
> THIS_SYMBOL_WAS_REMOVED_IN_MPI30(MPI_Errhandler_set, MPI_Comm_set_errhandler)
>   |  ^~~~
> mpy.c:169:12: note: in expansion of macro ‘MPI_Errhandler_set’
>   169 | || MPI_Errhandler_set(mpy_world, MPI_ERRORS_RETURN) != 
> MPI_SUCCESS) {
>   |^~
> make[1]: *** [: mpy.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/yorick_2.2.04+dfsg1-10_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: yorick
Source-Version: 2.2.04+dfsg1-11
Done: Thibaut Paumard 

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

Debian distribution maintenance software
pp.
Thibaut Paumard  (supplier of updated yorick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 13:41:53 +0100
Source: yorick
Architecture: source
Version: 2.2.04+dfsg1-11
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Thibaut Paumard 
Closes: 952104
Changes:
 yorick (2.2.04+dfsg1-11) unstable; urgency=low
 .
   * Bug fix: "FTBFS: mpi.h:322:57: error: expected expression before
 ‘_Static_assert’", thanks to Lucas Nussbaum (Closes: #952104).
Checksums-Sha1:
 8f07dc8a2c97d5c6f45e37f716f212edceb54428 3158 yorick_2.2.04+dfsg1-11.dsc
 fd20f982b1887f902c4ee4b9f33c6123ad4ba4e5 36672 
yorick_2.2.04+dfsg1-11.debian.tar.xz
 708790df6425f066baba71f443870acf18cb12d3 13315 
yorick_2.2.04+dfsg1-11_amd64.buildinfo
Checksums-Sha256:
 c2598cbe47d1b2cfc1ae6bdc31b234ce9d2ea7c9ecba9efa8b44059c4693956c 3158 
yorick_2.2.04+dfsg1-11.dsc
 adabb6ec6b214a9e602eb88c56f3a0b21d60b73b2f3594384507fde6bcf68be4 36672 
yorick_2.2.04+dfsg1-11.debian.tar.xz
 3eceee934507dd5d8321b95eea11f345201d3b2d694ae2a8ebbda5d7891b66b4 13315 
yorick_2.2.04+dfsg1-11_amd64.buildinfo
Files:
 a53c115dc6671512ffa64dfc89624e8a 3158 science optional 
yorick_2.2.04+dfsg1-11.dsc
 1614bdd429e3296e23381b241e2a 36672 science optional 
yorick_2.2.04+dfsg1-11.debian.tar.xz
 d86b6ea22673d51711bbc81e80c08bdc 13315 science optional 

Bug#952352: marked as done (prometheus-mailexporter: FTBFS: src/github.com/cherti/mailexporter/mailexporter.go:552:29: undefined: prometheus.Handler)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 16:08:40 +
with message-id 
and subject line Bug#952352: fixed in prometheus-mailexporter 
1.0+git20190716.c60d197-1
has caused the Debian Bug report #952352,
regarding prometheus-mailexporter: FTBFS: 
src/github.com/cherti/mailexporter/mailexporter.go:552:29: undefined: 
prometheus.Handler
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.)


-- 
952352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-mailexporter
Version: 1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/cherti/mailexporter
> internal/race
> runtime/internal/sys
> runtime/internal/atomic
> internal/cpu
> sync/atomic
> runtime/internal/math
> unicode
> internal/bytealg
> unicode/utf8
> math/bits
> internal/testlog
> math
> encoding
> unicode/utf16
> container/list
> runtime
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> runtime/cgo
> vendor/golang.org/x/crypto/internal/subtle
> vendor/golang.org/x/crypto/curve25519
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> reflect
> strings
> bufio
> hash
> crypto/internal/randutil
> time
> internal/syscall/unix
> hash/crc32
> crypto
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> path
> github.com/beorn7/perks/quantile
> github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
> regexp/syntax
> internal/fmtsort
> encoding/binary
> internal/poll
> context
> encoding/base64
> crypto/cipher
> os
> crypto/sha512
> crypto/ed25519/internal/edwards25519
> crypto/aes
> crypto/des
> crypto/md5
> crypto/sha1
> crypto/sha256
> fmt
> encoding/pem
> path/filepath
> vendor/golang.org/x/crypto/internal/chacha20
> net
> vendor/golang.org/x/crypto/poly1305
> io/ioutil
> vendor/golang.org/x/sys/cpu
> github.com/cespare/xxhash
> flag
> encoding/json
> log
> compress/flate
> math/big
> compress/gzip
> encoding/hex
> net/url
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/net/http2/hpack
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> crypto/ecdsa
> vendor/golang.org/x/net/idna
> crypto/x509/pkix
> vendor/golang.org/x/crypto/cryptobyte
> mime
> mime/quotedprintable
> net/http/internal
> github.com/golang/protobuf/proto
> regexp
> github.com/prometheus/procfs/internal/fs
> github.com/prometheus/procfs/internal/util
> runtime/debug
> golang.org/x/sys/unix
> github.com/prometheus/common/model
> gopkg.in/yaml.v2
> crypto/x509
> crypto/tls
> net/textproto
> vendor/golang.org/x/net/http/httpguts
> vendor/golang.org/x/net/http/httpproxy
> mime/multipart
> github.com/prometheus/client_model/go
> github.com/matttproud/golang_protobuf_extensions/pbutil
> github.com/prometheus/client_golang/prometheus/internal
> github.com/prometheus/procfs
> gopkg.in/fsnotify.v1
> net/mail
> net/http/httptrace
> net/smtp
> net/http
> expvar
> github.com/prometheus/common/expfmt
> github.com/prometheus/client_golang/prometheus
> github.com/cherti/mailexporter
> # github.com/cherti/mailexporter
> src/github.com/cherti/mailexporter/mailexporter.go:552:29: undefined: 
> prometheus.Handler
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/cherti/mailexporter returned exit code 2
> make: *** [debian/rules:4: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/prometheus-mailexporter_1.0-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build 

Bug#941537: marked as done (lilypond: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 15:50:33 +
with message-id 
and subject line Bug#941537: fixed in lilypond 2.19.81+really-2.18.2-14
has caused the Debian Bug report #941537,
regarding lilypond: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
941537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lilypond
Version: 2.19.81+really-2.18.2-13
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru lilypond-2.19.81+really-2.18.2/debian/control 
lilypond-2.19.81+really-2.18.2/debian/control
--- lilypond-2.19.81+really-2.18.2/debian/control   2018-05-12 
12:22:39.0 -0700
+++ lilypond-2.19.81+really-2.18.2/debian/control   2019-10-01 
14:16:13.0 -0700
@@ -41,7 +41,7 @@
texi2html,
texinfo,
texlive-fonts-recommended,
-   texlive-generic-recommended,
+   texlive-plain-generic,
texlive-lang-cyrillic,
texlive-latex-base,
texlive-latex-recommended,
--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.19.81+really-2.18.2-14
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated lilypond package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 04:49:18 -0700
Source: lilypond
Architecture: source
Version: 2.19.81+really-2.18.2-14
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: Anthony Fok 
Closes: 941537 945889 948183
Changes:
 lilypond (2.19.81+really-2.18.2-14) unstable; urgency=medium
 .
   [ Adrian Heine ]
   * Replace now-dropped transitional build-dependency
 texlive-generic-recommended with texlive-plain-generic
 (Closes: #941537, #945889)
   * Update debian/watch
   * Override lintian error about interpreter dependency
 "missing-dep-for-interpreter guile" as we bundle our own guile
 .
   [ Anthony Fok ]
   * Bump debhelper dependency to "Build-Depends: debhelper-compat (= 12)"
   * Bump Standards-Version to 4.5.0 (no change)
   * Change debian-branch from "debian" to "debian/sid".
 Also set "pristine-tar = True" in debian/gbp.conf
   * Update debian/watch to use secure https URL
   * Build-Depends on fontconfig for fc-list explicitly
 even though it is installed as an indirect dependency of fontforge
   * Update debian/rules for debhelper compat 12 and later.
 In particular, "dh_install --list-missing" has been removed,
 replaced by dh_missing
   * Adopt upstream patch to fix FTBFS with Ghostscript 9.50
 by using -dNOSAFER to override its new -dSAFER default.
 See 0013-Fix-for-Ghostscript-9.50.patch  (Closes: #948183)
Checksums-Sha1:
 7492e38c0c8c49ef0574849c5debe08618d9e07b 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 b7d71cd1e9162387354bfb5b76153b17df5c0adf 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 82ea15780263b4d88cfa0fd237a5088bb6208bb8 23022 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo
Checksums-Sha256:
 2a3133228563c6ceb5a81a8ecd61e84ce131a233df160f15e5ea0472b7fe9e65 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 93f25186021b83990bdddf1bcd96c3a5b172cf464d3318be3b6dc46d44d3a548 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 

Bug#945889: marked as done (lilypond, build-depends on obsolete package.)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 15:50:33 +
with message-id 
and subject line Bug#941537: fixed in lilypond 2.19.81+really-2.18.2-14
has caused the Debian Bug report #941537,
regarding lilypond, build-depends on obsolete 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.)


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

Package: lilypond
Version: 2.19.81+really-2.18.2-13
Severity: serious
Tags: patch

lilypond build-depends on texlive-generic-recommended, which has been dropped 
by the texlive-base source package. It is still present in unstable as a cruft 
package but is completely gone from testing.

Please update your build-dependency to texlive-plain-generic.
--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.19.81+really-2.18.2-14
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated lilypond package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 04:49:18 -0700
Source: lilypond
Architecture: source
Version: 2.19.81+really-2.18.2-14
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: Anthony Fok 
Closes: 941537 945889 948183
Changes:
 lilypond (2.19.81+really-2.18.2-14) unstable; urgency=medium
 .
   [ Adrian Heine ]
   * Replace now-dropped transitional build-dependency
 texlive-generic-recommended with texlive-plain-generic
 (Closes: #941537, #945889)
   * Update debian/watch
   * Override lintian error about interpreter dependency
 "missing-dep-for-interpreter guile" as we bundle our own guile
 .
   [ Anthony Fok ]
   * Bump debhelper dependency to "Build-Depends: debhelper-compat (= 12)"
   * Bump Standards-Version to 4.5.0 (no change)
   * Change debian-branch from "debian" to "debian/sid".
 Also set "pristine-tar = True" in debian/gbp.conf
   * Update debian/watch to use secure https URL
   * Build-Depends on fontconfig for fc-list explicitly
 even though it is installed as an indirect dependency of fontforge
   * Update debian/rules for debhelper compat 12 and later.
 In particular, "dh_install --list-missing" has been removed,
 replaced by dh_missing
   * Adopt upstream patch to fix FTBFS with Ghostscript 9.50
 by using -dNOSAFER to override its new -dSAFER default.
 See 0013-Fix-for-Ghostscript-9.50.patch  (Closes: #948183)
Checksums-Sha1:
 7492e38c0c8c49ef0574849c5debe08618d9e07b 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 b7d71cd1e9162387354bfb5b76153b17df5c0adf 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 82ea15780263b4d88cfa0fd237a5088bb6208bb8 23022 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo
Checksums-Sha256:
 2a3133228563c6ceb5a81a8ecd61e84ce131a233df160f15e5ea0472b7fe9e65 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 93f25186021b83990bdddf1bcd96c3a5b172cf464d3318be3b6dc46d44d3a548 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 8022f97527c42bc47b15793928e028271a8284771d022c87fbac249f4af0864e 23022 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo
Files:
 be3a28e36e05c7e2f595172ad2cda2e8 4232 tex optional 
lilypond_2.19.81+really-2.18.2-14.dsc
 d501e1020d9b9eeb76fd2bf4b9dc8457 57216 tex optional 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 721ca507d5be7ea96c0268b42d2d692e 23022 tex optional 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl5ZMcMACgkQ6iUAtBLF
ms+PDw//bqGvtgNTvUlww8rARshTp4BfFgwOs0k53U3/4f26tX7TLgbKIVeg5h+a
8740FOBh2umx3K0INhISBhDk0SPAHT5W+X2WZcm3PZ4dDAo7l2oBCWkIKcbR1Hfx
wGZoxaikHzLkc9JBMPMOeVZRwxZ5/fPjBSqourRjfyHUOEVnOFluKv5ljZrv9iyN
ZtiXxjMJqQjbKUh0rsFOcvoH8n0dizIbcdKl1k25ch7oL0b1zyKNvqun5jGU9Vu/
td1KUtvEunw3UwdITe1EyIeAL20XgA3hA4gd/z/A+Xze1P2RqoxVHe8LEgLfzWF4
cdYvx1jxWZ7lx1Cshi2thk0QtULXZtMcNdEuvDSTuR1oiijgaWm2IgPWKrfld7aZ
BOMH4ut0LYlGoj+dv7G3kCbLduE/LGSGeEWmd6BJx/pnnPk32MdAZIourJM1inQu

Bug#941537: marked as done (lilypond: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 15:50:33 +
with message-id 
and subject line Bug#945889: fixed in lilypond 2.19.81+really-2.18.2-14
has caused the Debian Bug report #945889,
regarding lilypond: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
945889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lilypond
Version: 2.19.81+really-2.18.2-13
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Dear maintainers,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru lilypond-2.19.81+really-2.18.2/debian/control 
lilypond-2.19.81+really-2.18.2/debian/control
--- lilypond-2.19.81+really-2.18.2/debian/control   2018-05-12 
12:22:39.0 -0700
+++ lilypond-2.19.81+really-2.18.2/debian/control   2019-10-01 
14:16:13.0 -0700
@@ -41,7 +41,7 @@
texi2html,
texinfo,
texlive-fonts-recommended,
-   texlive-generic-recommended,
+   texlive-plain-generic,
texlive-lang-cyrillic,
texlive-latex-base,
texlive-latex-recommended,
--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.19.81+really-2.18.2-14
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated lilypond package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 04:49:18 -0700
Source: lilypond
Architecture: source
Version: 2.19.81+really-2.18.2-14
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: Anthony Fok 
Closes: 941537 945889 948183
Changes:
 lilypond (2.19.81+really-2.18.2-14) unstable; urgency=medium
 .
   [ Adrian Heine ]
   * Replace now-dropped transitional build-dependency
 texlive-generic-recommended with texlive-plain-generic
 (Closes: #941537, #945889)
   * Update debian/watch
   * Override lintian error about interpreter dependency
 "missing-dep-for-interpreter guile" as we bundle our own guile
 .
   [ Anthony Fok ]
   * Bump debhelper dependency to "Build-Depends: debhelper-compat (= 12)"
   * Bump Standards-Version to 4.5.0 (no change)
   * Change debian-branch from "debian" to "debian/sid".
 Also set "pristine-tar = True" in debian/gbp.conf
   * Update debian/watch to use secure https URL
   * Build-Depends on fontconfig for fc-list explicitly
 even though it is installed as an indirect dependency of fontforge
   * Update debian/rules for debhelper compat 12 and later.
 In particular, "dh_install --list-missing" has been removed,
 replaced by dh_missing
   * Adopt upstream patch to fix FTBFS with Ghostscript 9.50
 by using -dNOSAFER to override its new -dSAFER default.
 See 0013-Fix-for-Ghostscript-9.50.patch  (Closes: #948183)
Checksums-Sha1:
 7492e38c0c8c49ef0574849c5debe08618d9e07b 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 b7d71cd1e9162387354bfb5b76153b17df5c0adf 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 82ea15780263b4d88cfa0fd237a5088bb6208bb8 23022 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo
Checksums-Sha256:
 2a3133228563c6ceb5a81a8ecd61e84ce131a233df160f15e5ea0472b7fe9e65 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 93f25186021b83990bdddf1bcd96c3a5b172cf464d3318be3b6dc46d44d3a548 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 

Bug#945889: marked as done (lilypond, build-depends on obsolete package.)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 15:50:33 +
with message-id 
and subject line Bug#945889: fixed in lilypond 2.19.81+really-2.18.2-14
has caused the Debian Bug report #945889,
regarding lilypond, build-depends on obsolete 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.)


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

Package: lilypond
Version: 2.19.81+really-2.18.2-13
Severity: serious
Tags: patch

lilypond build-depends on texlive-generic-recommended, which has been dropped 
by the texlive-base source package. It is still present in unstable as a cruft 
package but is completely gone from testing.

Please update your build-dependency to texlive-plain-generic.
--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.19.81+really-2.18.2-14
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated lilypond package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Feb 2020 04:49:18 -0700
Source: lilypond
Architecture: source
Version: 2.19.81+really-2.18.2-14
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: Anthony Fok 
Closes: 941537 945889 948183
Changes:
 lilypond (2.19.81+really-2.18.2-14) unstable; urgency=medium
 .
   [ Adrian Heine ]
   * Replace now-dropped transitional build-dependency
 texlive-generic-recommended with texlive-plain-generic
 (Closes: #941537, #945889)
   * Update debian/watch
   * Override lintian error about interpreter dependency
 "missing-dep-for-interpreter guile" as we bundle our own guile
 .
   [ Anthony Fok ]
   * Bump debhelper dependency to "Build-Depends: debhelper-compat (= 12)"
   * Bump Standards-Version to 4.5.0 (no change)
   * Change debian-branch from "debian" to "debian/sid".
 Also set "pristine-tar = True" in debian/gbp.conf
   * Update debian/watch to use secure https URL
   * Build-Depends on fontconfig for fc-list explicitly
 even though it is installed as an indirect dependency of fontforge
   * Update debian/rules for debhelper compat 12 and later.
 In particular, "dh_install --list-missing" has been removed,
 replaced by dh_missing
   * Adopt upstream patch to fix FTBFS with Ghostscript 9.50
 by using -dNOSAFER to override its new -dSAFER default.
 See 0013-Fix-for-Ghostscript-9.50.patch  (Closes: #948183)
Checksums-Sha1:
 7492e38c0c8c49ef0574849c5debe08618d9e07b 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 b7d71cd1e9162387354bfb5b76153b17df5c0adf 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 82ea15780263b4d88cfa0fd237a5088bb6208bb8 23022 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo
Checksums-Sha256:
 2a3133228563c6ceb5a81a8ecd61e84ce131a233df160f15e5ea0472b7fe9e65 4232 
lilypond_2.19.81+really-2.18.2-14.dsc
 93f25186021b83990bdddf1bcd96c3a5b172cf464d3318be3b6dc46d44d3a548 57216 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 8022f97527c42bc47b15793928e028271a8284771d022c87fbac249f4af0864e 23022 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo
Files:
 be3a28e36e05c7e2f595172ad2cda2e8 4232 tex optional 
lilypond_2.19.81+really-2.18.2-14.dsc
 d501e1020d9b9eeb76fd2bf4b9dc8457 57216 tex optional 
lilypond_2.19.81+really-2.18.2-14.debian.tar.xz
 721ca507d5be7ea96c0268b42d2d692e 23022 tex optional 
lilypond_2.19.81+really-2.18.2-14_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl5ZMcMACgkQ6iUAtBLF
ms+PDw//bqGvtgNTvUlww8rARshTp4BfFgwOs0k53U3/4f26tX7TLgbKIVeg5h+a
8740FOBh2umx3K0INhISBhDk0SPAHT5W+X2WZcm3PZ4dDAo7l2oBCWkIKcbR1Hfx
wGZoxaikHzLkc9JBMPMOeVZRwxZ5/fPjBSqourRjfyHUOEVnOFluKv5ljZrv9iyN
ZtiXxjMJqQjbKUh0rsFOcvoH8n0dizIbcdKl1k25ch7oL0b1zyKNvqun5jGU9Vu/
td1KUtvEunw3UwdITe1EyIeAL20XgA3hA4gd/z/A+Xze1P2RqoxVHe8LEgLfzWF4
cdYvx1jxWZ7lx1Cshi2thk0QtULXZtMcNdEuvDSTuR1oiijgaWm2IgPWKrfld7aZ
BOMH4ut0LYlGoj+dv7G3kCbLduE/LGSGeEWmd6BJx/pnnPk32MdAZIourJM1inQu

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Jean-Luc Coulon (f5ibh)]

Le 28/02/2020 à 15:55, Gunnar Hjalmarsson a écrit :
> On 2020-02-28 15:20, Michael Meskes wrote:
>> Anyway, it seems all layouts are not working, for me it's "de". A
>> manual "setxkbmap de" does fix the issue, though.
> 
> That makes me suspect that there is some issue in some GNOME package on
> Debian, which is not present on Ubuntu for some reason.
> 
> @Jean-Luc: Can you please run:
> 
> setxkbmap fr -variant oss
>
> and let us know if that workaround makes a difference for you too.
>

This is overwritten by gnome.

If I enter the connand it works for the session. If I reboot, I've the
keyboard is back to us.

I already tried that before reporting the bug.

--- From an other message 
>
> I see from the gsettings command output that you have two layouts
> enabled, and both those layouts work as expected for me.
>
> Can you please switch to "French (legacy, alt.)" and then back to >
"French (alt.)" and let us know if it makes a difference. Can you also
>check if the "French (legacy, alt.)" layout works as expected.

Nope, it is the same.

J-L

Bug#952753: python3-cassandra-doc: missing Breaks+Replaces: python3-cassandra (<< 3.20)

[Andreas Beckmann]

Package: python3-cassandra-doc
Version: 3.20.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../python3-cassandra-doc_3.20.2-2_all.deb ...
  Unpacking python3-cassandra-doc (3.20.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-cassandra-doc_3.20.2-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python3-cassandra/README.rst.gz', which 
is also in package python3-cassandra 3.16.0-2+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-cassandra-doc_3.20.2-2_all.deb


cheers,

Andreas


python3-cassandra=3.16.0-2+b1_python3-cassandra-doc=3.20.2-2.log.gz
Description: application/gzip

Bug#952751: eyes17: missing Breaks+Replaces: python3-expeyes (<< 4.6.1-2)

[Andreas Beckmann]

Package: eyes17
Version: 4.6.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Preparing to unpack .../eyes17_4.6.2-1_all.deb ...
  Unpacking eyes17 (4.6.2-1) ...
  dpkg: error processing archive /var/cache/apt/archives/eyes17_4.6.2-1_all.deb 
(--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/eyes17/Peripherals.py', 
which is also in package python3-expeyes 4.4.4+dfsg-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/eyes17_4.6.2-1_all.deb

4.6.1-2 was the version that shuffled the modules around according
to the changelog.


cheers,

Andreas


python3-expeyes=4.4.4+dfsg-4_eyes17=4.6.2-1.log.gz
Description: application/gzip

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Gunnar Hjalmarsson]

On 2020-02-28 15:20, Michael Meskes wrote:

Anyway, it seems all layouts are not working, for me it's "de". A
manual "setxkbmap de" does fix the issue, though.


That makes me suspect that there is some issue in some GNOME package on 
Debian, which is not present on Ubuntu for some reason.


@Jean-Luc: Can you please run:

setxkbmap fr -variant oss

and let us know if that workaround makes a difference for you too.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Gunnar Hjalmarsson]

Thanks for additional info, Jean-Luc.

On 2020-02-28 14:14, Jean-Luc Coulon (f5ibh) wrote:

Well, maybe it is difficult to explain as everything is… in French
;)


You can start Settings by pressing + and enter:

env LANGUAGE=en_US gnome-control-center

to get it temporarily in English.


but please see the attached screenshot of what I get from the gnome
preferences.


Just did. Looks good to me.


I suppose "Français(variante)" is "French(alt.)"


It is.


If I use 2.29, I get the same layout from the preferences but the
actual keybord is a us (at least qwerty) layout.


I see from the gsettings command output that you have two layouts 
enabled, and both those layouts work as expected for me.


Can you please switch to "French (legacy, alt.)" and then back to 
"French (alt.)" and let us know if it makes a difference. Can you also 
check if the "French (legacy, alt.)" layout works as expected.


--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Michael Meskes]

> Sorry to hear that, but I wonder if this is actually triggered by
> something else.. at least I'm not able to reproduce it with .fi layout
> on ubuntu focal..

Even if the package is exactly the same I don't see how a "I cannot reproduce
on Ubuntu" is helpful, sorry. There may be any number of packages that make it
work there but not here. 

Anyway, it seems all layouts are not working, for me it's "de". A manual
"setxkbmap de" does fix the issue, though. 

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#952750: python3-jenkinsapi: missing (unversioned) Breaks+Replaces: python-jenkinsapi

[Andreas Beckmann]

Package: python3-jenkinsapi
Version: 0.3.11-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Preparing to unpack .../python3-jenkinsapi_0.3.11-1_all.deb ...
  Unpacking python3-jenkinsapi (0.3.11-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-jenkinsapi_0.3.11-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/jenkins_invoke', which is also in package 
python-jenkinsapi 0.2.30-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-jenkinsapi_0.3.11-1_all.deb

Since the binary package python-jenkinsapi is gone, the
Breaks+Replaces can be unversioned.


cheers,

Andreas


python-jenkinsapi=0.2.30-1_python3-jenkinsapi=0.3.11-1.log.gz
Description: application/gzip

Processed: Re: Bug#945936: haskell-enummapset-th: Removal notice: unused Haskell library

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #945936 [src:haskell-enummapset-th] haskell-enummapset-th: Removal notice: 
unused Haskell library
Bug reassigned from package 'src:haskell-enummapset-th' to 'ftp.debian.org'.
No longer marked as found in versions haskell-enummapset-th/0.6.1.1-5.
Ignoring request to alter fixed versions of bug #945936 to the same values 
previously set
> retitle -1 RM: haskell-enummapset-th -- ROM; unused
Bug #945936 [ftp.debian.org] haskell-enummapset-th: Removal notice: unused 
Haskell library
Changed Bug title to 'RM: haskell-enummapset-th -- ROM; unused' from 
'haskell-enummapset-th: Removal notice: unused Haskell library'.
> severity -1 normal
Bug #945936 [ftp.debian.org] RM: haskell-enummapset-th -- ROM; unused
Severity set to 'normal' from 'serious'

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

Bug#945936: haskell-enummapset-th: Removal notice: unused Haskell library

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-enummapset-th -- ROM; unused
Control: severity -1 normal

Hi,

Please remove haskell-enummapset-th from Debian. This Haskell library
has not been updated since 2016 and does not build with newer GHC (we
use custom patches for this). Also, it is not on Stackage and has no
reverse dependencies.

Thanks,

-- 
Ilias

Bug#945935: haskell-hackage-mirror: Removal notice: unmaintained

[Ilias Tsitsimpis]

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

Hi,

Please remove haskell-hackage-mirror from Debian. This package is no
longer maintained upstream. For more information see:

  https://github.com/fpco/hackage-mirror/blob/master/README.md

Thanks,

-- 
Ilias

Processed: Re: Bug#945935: haskell-hackage-mirror: Removal notice: unmaintained

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed (with 1 error): Re: Bug#945013: haskell-gnuidn: Removal notice: unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #945013 [src:haskell-gnuidn] haskell-gnuidn: Removal notice: unmaintained
Bug reassigned from package 'src:haskell-gnuidn' to 'ftp.debian.org'.
No longer marked as found in versions haskell-gnuidn/0.2.2-9.
Ignoring request to alter fixed versions of bug #945013 to the same values 
previously set
> retitle -1 RM: haskell-gnuidn -- ROM; broken and unmaintained
Bug #945013 [ftp.debian.org] haskell-gnuidn: Removal notice: unmaintained
Changed Bug title to 'RM: haskell-gnuidn -- ROM; broken and unmaintained' from 
'haskell-gnuidn: Removal notice: unmaintained'.
> severity -1 normal
Bug #945013 [ftp.debian.org] RM: haskell-gnuidn -- ROM; broken and unmaintained
Severity set to 'normal' from 'serious'
> block -1 945012
Unknown command or malformed arguments to command.


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

Processed: Re: Bug#945012: haskell-network-protocol-xmpp: Removal notice: unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #945012 [src:haskell-network-protocol-xmpp] haskell-network-protocol-xmpp: 
Removal notice: unmaintained
Bug reassigned from package 'src:haskell-network-protocol-xmpp' to 
'ftp.debian.org'.
No longer marked as found in versions haskell-network-protocol-xmpp/0.4.8-8.
Ignoring request to alter fixed versions of bug #945012 to the same values 
previously set
> retitle -1 RM: haskell-network-protocol-xmpp -- ROM; unused
Bug #945012 [ftp.debian.org] haskell-network-protocol-xmpp: Removal notice: 
unmaintained
Changed Bug title to 'RM: haskell-network-protocol-xmpp -- ROM; unused' from 
'haskell-network-protocol-xmpp: Removal notice: unmaintained'.
> severity -1 normal
Bug #945012 [ftp.debian.org] RM: haskell-network-protocol-xmpp -- ROM; unused
Severity set to 'normal' from 'serious'

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

Bug#945012: haskell-network-protocol-xmpp: Removal notice: unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-network-protocol-xmpp -- ROM; unused
Control: severity -1 normal

Hi,

Please remove haskell-network-protocol-xmpp from Debian. It is unused,
has no reverse dependencies and depends on unmaintained software
(haskell-gnuidn).

Thanks,

-- 
Ilias

Bug#945013: haskell-gnuidn: Removal notice: unmaintained

[Ilias Tsitsimpis]

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

Hi,

Please remove haskell-gnuidn from Debian. This package seems to be
unmaintained upstream[1]. Its last upload was at 2015, and the home
page[2] returns 404.

[1] https://hackage.haskell.org/package/gnuidn
[2] https://john-millikin.com/software/haskell-gnuidn/

It is also not on Stackage and has no reverse dependencies (other than
haskell-network-protocol-xmpp, but see #945012).

Thanks,

-- 
Ilias

Bug#952281: marked as done (node-xterm should include lib/addons (add link to libjs-xterm))

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 13:50:06 +
with message-id 
and subject line Bug#952281: fixed in node-xterm 3.8.1-4
has caused the Debian Bug report #952281,
regarding node-xterm should include lib/addons (add link to libjs-xterm)
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.)


-- 
952281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-xterm
Version: 3.8.1-3
Severity: grave
Justification: unable to use the package in gitlab

webpack command in gitlab fails with xterm/lib/addons not found error. Adding a 
symbolic link to libjs-xterm copy should fix it I think.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
--- Begin Message ---
Source: node-xterm
Source-Version: 3.8.1-4
Done: Pirate Praveen 

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-xterm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2020 18:52:06 +0530
Source: node-xterm
Architecture: source
Version: 3.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Closes: 952281
Changes:
 node-xterm (3.8.1-4) unstable; urgency=medium
 .
   * Team upload
   * Include addons in node-xterm as well (Closes: #952281)
Checksums-Sha1:
 7ca1ee504b034b273fa70277e8cea9e0c907aff1 2163 node-xterm_3.8.1-4.dsc
 0885f93485a82283925cf964d9c5c95f7fc373d7 5180 node-xterm_3.8.1-4.debian.tar.xz
 c04feb04630351c0cd8e5daf0931cf2abeb9f29c 13571 
node-xterm_3.8.1-4_source.buildinfo
Checksums-Sha256:
 353a5f5c0a0c2d6bd1f926236cc36642e93ea14599db7dea5372f2d9c19c9e4b 2163 
node-xterm_3.8.1-4.dsc
 33e080d4c47c0c4fe03f573910822857301d69137e3a05506f1925ac7b42e8be 5180 
node-xterm_3.8.1-4.debian.tar.xz
 8e3fa6932f1d9522bebd8a36a2e7006c9bbf379fe7f8c5ad95d842d174e6d304 13571 
node-xterm_3.8.1-4_source.buildinfo
Files:
 df6a2b8538521b89fdc479ddc7da3fc0 2163 javascript optional 
node-xterm_3.8.1-4.dsc
 965e2bdc2515cc2f333b83fc0502246e 5180 javascript optional 
node-xterm_3.8.1-4.debian.tar.xz
 7f61bbc6ecffaff273342b24aa56eedf 13571 javascript optional 
node-xterm_3.8.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl5ZFUQACgkQj1PgGTsp
S3VmjQ/6AvQ3r6F/x2C5GOt6Mf0KyiIrzLVNf91Z2Y4ubkUsnzcZJBBAjPEdLyVr
Y1Pk+/ZvJwRYagyU6EfgapuKF/oJhOoEexQCzXBKAw+ujU6H06ihufrhbrwfBaUC
75H71tjX8M7IAeA/MIpyarfEmdJyD28KKwGXtH88rlxVykt6ni2l9+oj9c/1PxCH
nJbGyQ4gjS9LBaFBAOAScTEXtD9Trq0oeWUGacv1dTfdzaj0m/aXHI+MO52uPeWp
xR/cgxlKYvwCKvimuwYJd50aakzrTM2jDlr9Fp8A2gWXDiLQ9TgmmgoixtfVZaRt
lpaTu5yXQjfXgGD2iwHYzKFF9tiIS32o4D90r19vQoyBe67pMs6vkIR2mTRxMTSc
B6bwF51jT0I9akL+QM1ie0CLZWynBlZrUN3fGb35OyF+oFs3YspbNv9aXasHq/mZ
0R1OlUQnmyJFxVjYkKztLrFYUTyJBSldmvKiU6TcGAyJ06Km4YDwmtyLNht7K++R
OwNM2q+w6F17aYpuUDuLG7BClGkOnquTzl4+zA+kGJs27ZEFKJ3VAEYC4b5KQuAI
zKJvqHwotcM6WrPly3uIUCs0T3YDfyAsw6kumNUML8Bn4ZaT9B93vDjbjtSDBIdk
TePT95DPwmP6KUb1rQGhksTwgtWil9QvV2KKHjSSAyweP8up6xA=
=J46w
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#945011: haskell-cabal-helper: Removal notice: unused Haskell library

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #945011 [src:haskell-cabal-helper] haskell-cabal-helper: Removal notice: 
unused Haskell library
Bug reassigned from package 'src:haskell-cabal-helper' to 'ftp.debian.org'.
No longer marked as found in versions haskell-cabal-helper/0.8.0.2-1.
Ignoring request to alter fixed versions of bug #945011 to the same values 
previously set
> retitle -1 RM: haskell-cabal-helper -- ROM; unused Haskell library
Bug #945011 [ftp.debian.org] haskell-cabal-helper: Removal notice: unused 
Haskell library
Changed Bug title to 'RM: haskell-cabal-helper -- ROM; unused Haskell library' 
from 'haskell-cabal-helper: Removal notice: unused Haskell library'.
> severity -1 normal
Bug #945011 [ftp.debian.org] RM: haskell-cabal-helper -- ROM; unused Haskell 
library
Severity set to 'normal' from 'serious'

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

Bug#945011: haskell-cabal-helper: Removal notice: unused Haskell library

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-cabal-helper -- ROM; unused Haskell library
Control: severity -1 normal

Hi,

Please remove haskell-cabal-helper from Debian. This Haskell library is
not part of Buster, is not on Stackage and is already ignored on our
package-plan.

Thanks,

-- 
Ilias

Processed: Re: Bug#945010: ghc-mod: Removal notice: unmaintained

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#945010: ghc-mod: Removal notice: unmaintained

[Ilias Tsitsimpis]

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

Hi,

Please remove ghc-mod from Debian. This package is no longer maintained
upstream. For more information see:

https://github.com/DanielG/ghc-mod#legacy

Thanks,

-- 
Ilias

Bug#945007: haskell-hmt: Removal notice: unused Haskell library

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-hmt -- ROM; unused Haskell library
Control: severity -1 normal

Hi,

Please remove haskell-hmt from Debian. This Haskell library is not part
of Buster, has no reverse dependencies, is not on Stackage and is
already ignored on our package-plan.

Thanks,

-- 
Ilias

Processed: Re: Bug#945007: haskell-hmt: Removal notice: unused Haskell library

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #945007 [src:haskell-hmt] haskell-hmt: Removal notice: unused Haskell 
library
Bug reassigned from package 'src:haskell-hmt' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #945007 to the same values 
previously set
Ignoring request to alter fixed versions of bug #945007 to the same values 
previously set
> retitle -1 RM: haskell-hmt -- ROM; unused Haskell library
Bug #945007 [ftp.debian.org] haskell-hmt: Removal notice: unused Haskell library
Changed Bug title to 'RM: haskell-hmt -- ROM; unused Haskell library' from 
'haskell-hmt: Removal notice: unused Haskell library'.
> severity -1 normal
Bug #945007 [ftp.debian.org] RM: haskell-hmt -- ROM; unused Haskell library
Severity set to 'normal' from 'serious'

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

Bug#952747: libbio-alignio-stockholm-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)

[Andreas Beckmann]

Package: libbio-alignio-stockholm-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Preparing to unpack .../libbio-alignio-stockholm-perl_1.7.3-1_all.deb ...
  Unpacking libbio-alignio-stockholm-perl (1.7.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbio-alignio-stockholm-perl_1.7.3-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man3/Bio::AlignIO::stockholm.3pm.gz', 
which is also in package libbio-perl-perl 1.7.2-3
  Errors were encountered while processing:
   /var/cache/apt/archives/libbio-alignio-stockholm-perl_1.7.3-1_all.deb

IIRC, libbio-perl-perl 1.7.3 was the version that got split up.


cheers,

Andreas


libbio-perl-perl=1.7.2-3_libbio-alignio-stockholm-perl=1.7.3-1.log.gz
Description: application/gzip

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Jean-Luc Coulon (f5ibh)]

Hi

Le 28/02/2020 à 13:29, Gunnar Hjalmarsson a écrit :
> I tested on Ubuntu, which has the very same version of xkb-data
> (2.29-1), and both the Italian - it and French (alt.) - fr+oss layouts
> seem to work for me.
> 
> $ gsettings get org.gnome.desktop.input-sources sources
> [('xkb', 'se'), ('xkb', 'us'), ('xkb', 'it'), ('xkb', 'fr+oss')]

> @Domenico and @Jean-Luc: It would be good if you could clarify exactly
> which keyboard layouts were problematic for you, and in which way(s).
Well, maybe it is difficult to explain as everything is… in French ;)
but please see the attached screenshot of what I get from the gnome
preferences.

If I use 2.26, I get the attached layout [Français(variante)] from the
preferences AND it works as exected.

I suppose "Français(variante)" is "French(alt.)"

If I use 2.29, I get the same layout from the preferences but the actual
keybord is a us (at least qwerty) layout.

If I switch from 2.26/2.29 (and restart the window manager), I
repeatedly get the same behaviour (correct with 2.26 et wrong with 2.29).

> Good if you too run the above command and show us the output.
I get the following, with both the version of xkb-data.[('xkb',
'fr+oss'), ('xkb', 'fr+latin9')]
> 
> Btw, @Domenico: Is the "Use the same source for all windows" option
> enabled in Settings?
Yes and BTW, I did nothing but a reboot after upgrading xkb-data.

Bug#951959: marked as done (megaglest: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 13:08:25 +
with message-id 
and subject line Bug#951959: fixed in megaglest 3.13.0-5
has caused the Debian Bug report #951959,
regarding megaglest: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
 undefined reference to `pthread_create'
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.)


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_ce1cd.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
>  undefined reference to `pthread_create'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12:
>  undefined reference to `pthread_detach'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13:
>  undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/megaglest_3.13.0-4_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated megaglest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2020 13:20:51 +0100
Source: megaglest
Architecture: source
Version: 3.13.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 951959
Changes:
 megaglest (3.13.0-5) unstable; urgency=medium
 .
   * Declare compliance with Debian Policy 4.5.0.
   * Add use-sdl2-config.cmake.patch. Fix FTBFS. Mitigate SDL2 bug 951087.
 (Closes: #951959)
Checksums-Sha1:
 8e623357b26cab174e3392df1c8893f38552cc03 2430 megaglest_3.13.0-5.dsc
 c750d8251296f17dc7dce198b5ec4bdabb1c1227 19560 megaglest_3.13.0-5.debian.tar.xz
 e0a8830e27f7a871f4ab09502bcea9ed692c07db 10395 
megaglest_3.13.0-5_source.buildinfo
Checksums-Sha256:
 05d9464eeceea8331df6c320123abebad23fc3528a0f6cb846ecd67a30f57f59 2430 
megaglest_3.13.0-5.dsc
 22cdfc4c3246345c7363e27673aa539f44b8f1560f1d8fee828325f3587c 19560 
megaglest_3.13.0-5.debian.tar.xz
 74541dbc39d41fe144966883c7449bf7ea8dd720508124d2abfd3707937c318c 10395 
megaglest_3.13.0-5_source.buildinfo
Files:
 e0961979d6100309c7b3425b08cbadb9 2430 games optional megaglest_3.13.0-5.dsc
 b644700195cdb9b8e8aba335e61f0794 19560 games optional 
megaglest_3.13.0-5.debian.tar.xz
 ff69b3fb94fc9f032fcdca639c0ffa21 10395 games optional 
megaglest_3.13.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl5ZCqlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hka+QQALh9XsIe0NWrMs0CTGEa+F+VGN0SA7pEnK3e
tfUwXcTzF3dcAqE6igh5zTnzbVcXJG2w8VrGLuL8o4wv1Xyprj4EIPdORMEay9Cf
y0PDK/7RZMqmfB1DXcledJ0yMBFgHMWxQp1+k5caHxm6aPyH1tDZjhQXU3fCv9SY
pVGLHcHKGh6wJV98W17CXt6oqAzM/lcxT8/6x4VvSdeVjRuDWmgcrFBT48LRDk6a
XGGwG55NPsZf/xGcF7iwTqbPkN6FTmoHY49ohujKNrK5VO4qFha1Zr9NwzZzaEbX
ZSTxtzNKTvy4AHZRzh26UdeKyCjs+ETiDshjSv6fG9VNrzffKL7NXijYaWAQ/fiE

Bug#952598: marked as done (gyoto build depends on the removed swig3.0)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 13:08:17 +
with message-id 
and subject line Bug#952598: fixed in gyoto 1.4.3-2
has caused the Debian Bug report #952598,
regarding gyoto build depends on the removed swig3.0
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.)


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

swig3.0 has been replaced with swig4.0,
but in most cases swig is the correct
package to build depend on.
--- End Message ---
--- Begin Message ---
Source: gyoto
Source-Version: 1.4.3-2
Done: Thibaut Paumard 

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

Debian distribution maintenance software
pp.
Thibaut Paumard  (supplier of updated gyoto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Feb 2020 17:25:52 +0100
Source: gyoto
Architecture: source
Version: 1.4.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Maintainers 

Changed-By: Thibaut Paumard 
Closes: 952598
Changes:
 gyoto (1.4.3-2) unstable; urgency=low
 .
   * Bug fix: "gyoto build depends on the removed swig3.0", thanks to
 Adrian Bunk (Closes: #952598).
Checksums-Sha1:
 137554c5efdbca6adc872a7d550e027ccdc485cd 2894 gyoto_1.4.3-2.dsc
 56d0f4eaec4da40e4d56b8c5a01fbe34f792461c 11956 gyoto_1.4.3-2.debian.tar.xz
 50bcaacf21c5c01a07e98cae5a4ae72eded74d4b 16494 gyoto_1.4.3-2_amd64.buildinfo
Checksums-Sha256:
 f95620f91e6dfe73f3e0e5a5072a6770346a47b504bbad354e741026a1487e56 2894 
gyoto_1.4.3-2.dsc
 946fe0d330c51cde4841de12be4a467a3baa65636d50fdebf21bf28ac0262182 11956 
gyoto_1.4.3-2.debian.tar.xz
 4fc76388e5e227ab7758d6cdb4beb68d04044fc685925fc28d7951b6e9a264c1 16494 
gyoto_1.4.3-2_amd64.buildinfo
Files:
 a000e01360dad379962077d10adcd670 2894 science optional gyoto_1.4.3-2.dsc
 a5a971a83bc931cf8e7f57a105ef71ce 11956 science optional 
gyoto_1.4.3-2.debian.tar.xz
 5204bb1712dc249ee9a8a50b9ccb5192 16494 science optional 
gyoto_1.4.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEvK37UrQZmNdNmdmOk5RTSODcKEAFAl5ZDYUTHHRoaWJhdXRA
ZGViaWFuLm9yZwAKCRCTlFNI4NwoQG36EACPL5WfGuntGqWzeXb6TqbybD///vw4
cjhmCl4L0zIWQZlc6h4LBe9DowX3wFeA0uEHH4lUTOQo/EM6g6GqhQ5SIrVGXoI2
ulS39wNvPF7WP+bWjTS8zY8qRLNbkMsLUV5G7ANtXKeFEVMZSXdffeXUP/gyvvfz
ihgplHRdqK5f74u9WHNZC9jxVzzztKkdvd08adbvNzLghwzCbyDq061qhzPcFsSi
2baG9aQsrC17fZMdLkMYtSlodAfdnGsRe+5zdywYgu3pH9g6y6frRjSzvDX7icyh
cqqPY31f8S+DeZipoEhhOKsxvxC8JkQ2oko7VOtfD9kNBs3NEmWVoGzSH1kJmzaQ
M2IU9MK/HiCaCrvPNLvj8looumrLXj7hKoZCELF8ax90wZnI6awUAxigTXnrYRTa
jXBzlqqUQSD+UdtMdfz11pPQMs+Golgls+ECkIOySt5OgPXoDlAm0ZJ5CaFHpGBb
XzF9ZUb8ujR2wJ4WjATzhndXaWmo0w9HdhNJPaqhTD5W3ku/6wzRTT0IU5/K5/rx
GZuBjY5an8fIaK9//7ll0vKEUa5uqNNeDbthSuHVk5oG78Nrh46MQTdvO+J/vpC5
p5dXGu/i+C6Na00r0SPJVmlTumzd67YbvMH5aRI/IZIwlkgEtBmqRJSFxyWpNA8B
8/e0D8yB9JpqOg==
=iD69
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 951894 https://github.com/openpreserve/jpylyzer/issues/165
Bug #951894 [src:jpylyzer] jpylyzer FTBFS: test_get_files failure
Set Bug forwarded-to-address to 
'https://github.com/openpreserve/jpylyzer/issues/165'.
> tags 951894 upstream
Bug #951894 [src:jpylyzer] jpylyzer FTBFS: test_get_files failure
Added tag(s) upstream.
>
End of message, stopping processing here.

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

Bug#951959: marked as pending in megaglest

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #951959 in megaglest 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/games-team/megaglest/-/commit/0e4fd57cb77f2e4855f4aea58aefb5cdef7435f4


Add use-sdl2-config.cmake.patch. Mitigate SDL2 bug 951087.

Closes: #951959


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/951959

Processed: Bug#951959 marked as pending in megaglest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #951959 [src:megaglest] megaglest: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
 undefined reference to `pthread_create'
Added tag(s) pending.

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

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Gunnar Hjalmarsson]

I tested on Ubuntu, which has the very same version of xkb-data 
(2.29-1), and both the Italian - it and French (alt.) - fr+oss layouts 
seem to work for me.


$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'se'), ('xkb', 'us'), ('xkb', 'it'), ('xkb', 'fr+oss')]

@Domenico and @Jean-Luc: It would be good if you could clarify exactly 
which keyboard layouts were problematic for you, and in which way(s). 
Good if you too run the above command and show us the output.


Btw, @Domenico: Is the "Use the same source for all windows" option 
enabled in Settings?


--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Processed: tagging 948942

[Debian Bug Tracking System]

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

> tags 948942 + pending
Bug #948942 [src:pglogical] pglogical: FTBFS: mismatch with the default postgres
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#946995: No sound

[積丹尼 Dan Jacobson]

Well I have given up on webm due to #951451
and will now just download in mp4 format.

Bug#943524: marked as done (python3-stdlib-extensions: FTBFS with ModuleNotFoundError: No module named '_sysconfigdata_d_linux_x86_64-linux-gnu')

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 12:40:08 +0100
with message-id 
and subject line Fixed
has caused the Debian Bug report #943524,
regarding python3-stdlib-extensions: FTBFS with ModuleNotFoundError: No module 
named '_sysconfigdata_d_linux_x86_64-linux-gnu'
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.)


-- 
943524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-stdlib-extensions
Version: 3.8.0~a3-1
Severity: serious

Hi,

python3-stdlib-extensions/experimental FTBFS in an up-to-date
sid/experimental pbuilder environment:

[...]
cd 3.8 && PYTHONPATH=/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib 
python3.8-dbg setup.py build
running build
running build_ext
setup.py:623: DeprecationWarning: invalid escape sequence \s
  archs = re.findall('-arch\s+(\w+)', cflags)
setup.py:4: DeprecationWarning: the imp module is deprecated in favour of 
importlib; see the module's documentation for alternative uses
  import sys, os, imp, re, optparse
setup.py:787: DeprecationWarning: SO is deprecated, use EXT_SUFFIX
  so_ext = sysconfig.get_config_var("SO")
Traceback (most recent call last):
  File "setup.py", line 877, in 
main()
  File "setup.py", line 849, in main
setup(# PyPI Metadata (PEP 301)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/core.py", 
line 148, in setup
dist.run_commands()
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/dist.py", 
line 966, in run_commands
self.run_command(cmd)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/dist.py", 
line 985, in run_command
cmd_obj.run()
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/command/build.py", 
line 135, in run
self.run_command(cmd_name)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/cmd.py", 
line 313, in run_command
self.distribution.run_command(command)
  File "/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/dist.py", 
line 985, in run_command
cmd_obj.run()
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/command/build_ext.py",
 line 310, in run
customize_compiler(self.compiler)
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/sysconfig.py", 
line 197, in customize_compiler
get_config_vars('CC', 'CXX', 'CFLAGS',
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/sysconfig.py", 
line 501, in get_config_vars
func()
  File 
"/build/python3-stdlib-extensions-3.8.0~a3/3.8/Lib/distutils/sysconfig.py", 
line 461, in _init_posix
_temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
ModuleNotFoundError: No module named '_sysconfigdata_d_linux_x86_64-linux-gnu'
make: *** [debian/rules:60: dbg-stamp-py3.8] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas


python3-stdlib-extensions_3.8.0~a3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.8.0-1--- End Message ---

Bug#952731: xkb-data: Italian keyboard layout not working in some apps

[Timo Aaltonen]

On 28.2.2020 10.35, Domenico Cufalo wrote:
> Package: xkb-data
> Version: 2.29-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Latest version of xkb-data (2.29.1) renders Italian keyboard unusable in some
> apps.
> 
> In short, in applications like Firefox or Chrome, even if I use an Italian
> keyboard, the English layout is activated.
> 
> In gedit, gnome-terminal, Libreoffice, reportbug itself and maybe other apps,
> Italian keyboard works fine.
> 
> Thank you very much in advance,
> Domenico

Sorry to hear that, but I wonder if this is actually triggered by
something else.. at least I'm not able to reproduce it with .fi layout
on ubuntu focal..



-- 
t

Bug#952742: mumble: start locks sound for all application (even the client itself)

[lemmel]

Package: mumble
Version: 1.3.0+dfsg-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

fresh dist-upgrade (this day 02/28/20) brought up a mumble that lock all sound
on the host, the mumble client itself producing no sound.

I did all kind of setup with the mumble client (OSS, ALSA, etc), but it did
nothing.

Don't really know the reason as pulseaudo is kind of a magic thing to me, but I
did retrieve several versions of the mumble client and saw that the current git
code work correctly.

Here is the summary of my builds (all extracted from the Git repository) and
tests :
- git clone https://github.com/mumble-voip/mumble.git mumble
  cd mumble
  git checkout tags/1.3.0
  git submodule init
  git submodule update
  ===> FAILED

- git clone --single-branch --branch 1.3.x  https://github.com/mumble-
voip/mumble.git
  cd mumble
  git submodule init
  git submodule update
  ===> FAILED

- git clone https://github.com/mumble-voip/mumble.git
  cd mumble
  git submodule init
  git submodule update
  ===> SUCCESS

So it may suggest that the current devel version fixes something about its
sound management.

PS : system informations
- 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux
- libc6  : amd64 2.29-10
- mumble : 1.3.0+dfsg-1+b1
- gcc -v : gcc version 9.2.1 20200224 (Debian 9.2.1-30)
- Qt : 5.12.5
- pulseaudio : 13.0-5



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

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

Versions of packages mumble depends on:
ii  libasound21.2.1.2-2
ii  libavahi-compat-libdnssd1 0.7-5
ii  libc6 2.29-10
ii  libgcc-s1 [libgcc1]   10-20200222-1
ii  libgcc1   1:10-20200222-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2+b1
ii  libprotobuf17 3.6.1.3-2+b2
ii  libpulse0 13.0-5
ii  libqt5core5a  5.12.5+dfsg-9
ii  libqt5dbus5   5.12.5+dfsg-9
ii  libqt5gui55.12.5+dfsg-9
ii  libqt5network55.12.5+dfsg-9
ii  libqt5sql55.12.5+dfsg-9
ii  libqt5sql5-sqlite 5.12.5+dfsg-9
ii  libqt5svg55.12.5-2
ii  libqt5widgets55.12.5+dfsg-9
ii  libqt5xml55.12.5+dfsg-9
ii  libsndfile1   1.0.28-7
ii  libspeechd2   0.9.1-4
ii  libspeex1 1.2~rc1.2-1.1
ii  libspeexdsp1  1.2~rc1.2-1.1
ii  libssl1.1 1.1.1d-2
ii  libstdc++610-20200222-1
ii  libx11-6  2:1.6.9-2
ii  libxi62:1.7.9-1
ii  lsb-release   11.1.0

mumble recommends no packages.

Versions of packages mumble suggests:
pn  mumble-server  
ii  speech-dispatcher  0.9.1-4

-- no debconf information

Bug#952741: [RFH] FTBFS: Tests sometimes get stuck and the build gets forcefully terminated

[Daniel Leidert]

Source: puma
Version: 4.3.1-1
Severity: serious
Tags: experimental
Usertags: ftbfs-experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The build of puma in experimental failed for several architectures. On amd64 it
gets stuck for no obvious reason and must be killed forcefully after some time.
The issue is also reproducible locally and on salsa.d.o, although it did not
appear during the team sprint in Paris. Then the tests went fine and fast.

The situation does not improve with the latest release 4.3.2. Disabling
test_integration_cluster.rb doesn't help either, so it is not related to these
tests.

I need help to examine the cause.

JFTR: For some other architestures there are other isses.

Regards, Daniel

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

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5Y8DwACgkQS80FZ8KW
0F3K9A/8DwzmXLk6L0WymvxGFqO2HAV4Dz2QGkhmMPDB9b4dRq9vPK2n08+Y+nhi
hxRbsR8Vt6nhr4a0LWVqMLZm2lxnVB5KwRMTl38/9E4CSw/PnU1HIl13YwTOeSCT
zJZ/3QuFSNUr4Ea+FTgf2Bchv1lphQddflL18kqV+GW86ptFD96ABQ27QpULmPzn
xJxNLc2g3qQUUxyxevg++ajs4Xc54vdu22wU0xqlkA8yTtpIHpkkDgRS86IrObDi
WmDq5aatxgaEQSKqSLcVpKk3ayVXZTYVMpA1Qz0I1qGkIqL4VgdF2ghE/8tUUTLQ
UOMre/zPSNnOl47LT88a4FvzycL1zoUTwaqsIyYEPhfyqHjEqqq/5BgUbD230frJ
1J7sseWGogVO/fG8YJhxU2o/pg7Pl/BAXvVlpcLU6dMnBPt765Mq71gcRCoyFP0Z
KciKO58CwWCiOSu+pBN5YwUtdFvnxpXh1CammKxgGjlnUbFaIxHfJeEUviE8COeD
qK2PSDObOKGWW0bjcNskfExMum09sYR6r20HuYvHVNgTf2Qp9vlVUL8AEsnfNV1D
K6v6xihE2c7ndZtj0G0tzqWve2fnNQsrtF+2Ec0maOHEDqFyNC3Jxtv5f3scSZeF
Un2T4H3IKq0bkBbHmFd8RU6mILiD1Kf9Nr0VcTbtOgcA6VLEzXQ=
=P92Z
-END PGP SIGNATURE-

Bug#952731: xkb-data: Same for fr layout, reverting to 2.26-2 fixes the problem

[Jean-Luc Coulon (f5ibh)]

Package: xkb-data
Followup-For: Bug #952731


Hi,

fr [fr (variant) under gnome] stops also to work after upgrading xkb-data.
Reverting to 2.26-2 fixes the problem.

Regards

Jean-Luc

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

Kernel: Linux 5.6.0-rc3-i7-0.1 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#948834: marked as done (glib2.0: FTBFS: gio/tests/gsocketclient-slow.c: Error resolving ?localhost?: Name or service not known)

[Debian Bug Tracking System]

Your message dated Fri, 28 Feb 2020 10:12:41 +
with message-id <20200228101241.ga206...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#948834: glib2.0: FTBFS: 
gio/tests/gsocketclient-slow.c: Error resolving ?localhost?: Name or service 
not known
has caused the Debian Bug report #948834,
regarding glib2.0: FTBFS: gio/tests/gsocketclient-slow.c: Error resolving 
?localhost?: Name or service not known
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.)


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

Dear maintainer,

your package failed to rebuild in a standard sid chroot.

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

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

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

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

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


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End 

Processed: Bug#952019 marked as pending in ruby-json-schema

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952019 [src:ruby-json-schema] ruby-json-schema: FTBFS: ERROR: Test 
"ruby2.7" failed.
Added tag(s) pending.

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