Bug#975856: marked as done (debmake-doc: FTBFS: dh: error: Please specify the compatibility level in debian/compat)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 06:33:23 +
with message-id 
and subject line Bug#975856: fixed in debmake-doc 1.15-1
has caused the Debian Bug report #975856,
regarding debmake-doc: FTBFS: dh: error: Please specify the compatibility level 
in debian/compat
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.)


-- 
975856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debmake-doc
Version: 1.14-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/debhello-0.0-pkg4'
> mkdir -p /<>/debhello-0.0-pkg1/test
> mkdir -p /<>/debhello-0.0-pkg2/test
> mkdir -p /<>/debhello-0.0-pkg3/test
> echo /<>/debhello-0.0-pkg1 > 
> /<>/debhello-0.0-pkg1/next.dir
> echo /<>/debhello-0.0-pkg2 > 
> /<>/debhello-0.0-pkg2/next.dir
> echo /<>/debhello-0.0-pkg3 > 
> /<>/debhello-0.0-pkg3/next.dir
> echo debhello-0.0 > /<>/debhello-0.0-pkg1/project
> echo debhello-0.0 > /<>/debhello-0.0-pkg3/project
> mkdir -p /<>/debhello-0.0-pkg4/test
> for i in  step000  step101  step102  step200  step201  step202  step203  
> step204  step299  step301  step302  step303  step309  step400  step499  
> step500  step600  step700  step701  step702 ; do \
> cd $(cat /<>/debhello-0.0-pkg1/next.dir) >/dev/null ; \
> script -e -q -c /<>/debhello-0.0-pkg1/$i.cmd 
> /<>/debhello-0.0-pkg1/$i.log ; \
> ERR=$? ; \
> cat /<>/debhello-0.0-pkg1/$i.log | col -b -x | \
> grep -v -e '^Script started on' | \
> grep -v -e '^Script done on' | \
> sed -r 's/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g' | \
> sed -e 's#/<>/debhello-0.0-pkg1/test#/path/to#g' | \
> sed -e 
> 's/\(^.\).*$/\1.../'
>  > /<>/debhello-0.0-pkg1/$i.slog ; \
> if [ x$ERR != x0 ]; then exit 1 ; fi ; \
> done
> echo debhello-0.0 > /<>/debhello-0.0-pkg2/project
> for i in  step000  step101  step102  step200  step201  step202  step203  
> step204  step299  step301  step302  step303  step304  step305  step306  
> step309  step400  step499  step500  step600  step700  step701  step702 ; do \
> cd $(cat /<>/debhello-0.0-pkg3/next.dir) >/dev/null ; \
> script -e -q -c /<>/debhello-0.0-pkg3/$i.cmd 
> /<>/debhello-0.0-pkg3/$i.log ; \
> ERR=$? ; \
> cat /<>/debhello-0.0-pkg3/$i.log | col -b -x | \
> grep -v -e '^Script started on' | \
> grep -v -e '^Script done on' | \
> sed -r 's/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g' | \
> sed -e 's#/<>/debhello-0.0-pkg3/test#/path/to#g' | \
> sed -e 
> 's/\(^.\).*$/\1.../'
>  > /<>/debhello-0.0-pkg3/$i.slog ; \
> if [ x$ERR != x0 ]; then exit 1 ; fi ; \
> done
> for i in  step000  step101  step102  step120  step200  step201  step202  
> step203  step204  step299  step301  step302  step303  step304  step308  
> step309  step400  step499  step500  step600  step700  step701  step702 ; do \
> cd $(cat /<>/debhello-0.0-pkg2/next.dir) >/dev/null ; \
> script -e -q -c /<>/debhello-0.0-pkg2/$i.cmd 
> /<>/debhello-0.0-pkg2/$i.log ; \
> ERR=$? ; \
> cat /<>/debhello-0.0-pkg2/$i.log | col -b -x | \
> grep -v -e '^Script started on' | \
> grep -v -e '^Script done on' | \
> sed -r 's/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g' | \
> sed -e 's#/<>/debhello-0.0-pkg2/test#/path/to#g' | \
> sed -e 
> 's/\(^.\).*$/\1.../'
>  > /<>/debhello-0.0-pkg2/$i.slog ; \
> if [ x$ERR != x0 ]; then exit 1 ; fi ; \
> done
> echo /<>/debhello-0.0-pkg4 > 
> /<>/debhello-0.0-pkg4/next.dir
> echo debhello-0.0 > /<>/debhello-0.0-pkg4/project
> for i in  step000  step101  step102  step200  step201  step202  step203  
> step204  step299  step300  step301  step302  step303  step309  step310  
> step340  step350  step351  step400  step499  step500  step600  step700  
> step701  step702 ; do \
> cd $(cat /<>/debhello-0.0-pkg4/next.dir) >/dev/null ; \
> script -e -q -c /<>/debhello-0.0-pkg4/$i.cmd 
> /<>/debhello-0.0-pkg4/$i.log ; \
> ERR=$? ; \
> cat /<>/debhello-0.0-pkg4/$i.log | col -b -x | \
> grep -v -e '^Script started on' | \
> grep -v -e '^Script done on' | \
> sed -r 's/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g' | \
> sed -e 's#/<>/debhello-0.0-pkg4/test#/path/to#g' | \
> sed -e 
> 's/\(^.\).*$/\1.../'
>  > /<>/debhello-

Bug#936604: FYI: Python 3 migration of distributuion

[Osamu Aoki]

Hi,

It's a fork with a new upstream with some issues.  (Not supported by
the old upstream)

Anyway, I switched out from getmail to other MUA.

No one seems to take over this package maintenance.

So please remove this package.  I am not going to package the new
getmail6.

Regards,

Osamu


On Wed, 2020-10-21 at 22:41 +0200, Moritz Mühlenhoff wrote:
> On Tue, Nov 19, 2019 at 10:43:49PM +0900, Osamu Aoki wrote:
> > On Sun, Nov 17, 2019 at 02:28:44PM +0900, Osamu Aoki wrote:
> > > Hi,
> > > 
> > > On Wed, Nov 13, 2019 at 11:11:43AM -0600, Charles Cazabon wrote:
> > > > Osamu Aoki  wrote:
> > > > > 
> > > > > Currently, getmail is a candidate for removal from the
> > > > > upcoming Debian
> > > > > release if it is not updated to support python 3 by someone
> > > > > (not
> > > > > necessary by upstream).
> > > > 
> > > > Thanks for the update, Osamu.  I have actually been playing
> > > > with a prototype
> > > > refactoring of getmail to not just support but require a recent
> > > > Python 3.x
> > > > version.  Such a project would give me the opportunity to
> > > > remove a lot of
> > > > historical cruft and backwards-compatibility code that getmail
> > > > has accumulated
> > > > over 20+ years.
> > > 
> > > That's great.  (I thought you rejected idea to move to 3.0.)
> > > 
> > > I tried to do it around getmail 5.5 days.  (I didn't finish it)
> > 
> > 
> > FYI: I found this repo
> > https://gitlab.com/dkg/getmail/commits/python3
> > I think this is better work than my local work.
> 
> Hi Osamu,
> given that a Py3-compatible version is now available as src:getmail6,
> let's go ahead and remove getmail?
> 
> Cheers,
>     Moritz    

Bug#977170: python3-unrardll needs a manual upload to drop Python 3.8 support

[Adrian Bunk]

Package: python3-unrardll
Version: 0.1.4-1
Severity: serious

Sources+binaries might be easier than a manual binNMU.

Bug#938443: marked as done (scid: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 23:34:50 +
with message-id 
and subject line Bug#938443: fixed in scid 1:4.7.0+dfsg1-2
has caused the Debian Bug report #938443,
regarding scid: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: scid
Source-Version: 1:4.7.0+dfsg1-2
Done: josg...@jglopez.name (=?utf-8?q?Jose_G=2E_L=C3=B3pez?=)

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

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

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

Debian distribution maintenance software
pp.
Jose G. López  (supplier of updated scid 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, 11 Dec 2020 18:27:27 +0100
Source: scid
Architecture: source
Version: 1:4.7.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Jose G. López 
Changed-By: Jose G. López 
Closes: 938443
Changes:
 scid (1:4.7.0+dfsg1-2) unstable; urgency=medium
 .
   * Use dh_python3 to calculate Python 3 dependencies
 as Python 2 will be removed from Debian. (Closes: #938443)
   * debian/control:
 - Build-depend on python3.
 - Upgrade to debhelper compat 13.
 - Bump to Standards-Version 4.5.1. No changes required.
   * debian/patches:
 - 03_pngfix-python3.patch. Import patch to make pgnfix work
   with Python 3.
   * debian/rules:
 - Add python3 to dh's --with option.
   * Rename TODO.debian to be included when installing.
Checksums-Sha1:
 a7185c0b1b95696cee8476e294730f8c3e9f4e99 1973 scid_4.7.0+dfsg1-2.dsc
 80f7d2b916537c6e35a9b3d884bcecef6de785fd 19000 scid_4.7.0+dfsg1-2.debian.tar

Processed: Re: vtk7 FTBFS with freetype 2.10.4

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 7.1.1+dfsg2-6
Bug #976976 [src:vtk7] vtk7 FTBFS with freetype 2.10.4
The source 'vtk7' and version '7.1.1+dfsg2-6' do not appear to match any binary 
packages
Marked as fixed in versions vtk7/7.1.1+dfsg2-6.
> close -1
Bug #976976 [src:vtk7] vtk7 FTBFS with freetype 2.10.4
Marked Bug as done

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

Bug#976976: vtk7 FTBFS with freetype 2.10.4

[Gianfranco Costamagna]

control: fixed -1 7.1.1+dfsg2-6
control: close -1
On Wed, 09 Dec 2020 16:22:48 +0200 Adrian Bunk  wrote:
> Source: vtk7
> Version: 7.1.1+dfsg2-4
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/package.php?p=vtk7
> 
> ...
> /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:277:1: error: 
> expected constructor, destructor, or type conversion before 
> ‘vtkFreeTypeToolsFaceRequester’
>   277 | vtkFreeTypeToolsFaceRequester(FTC_FaceID face_id,
>   | ^
> [ 49%] Building CXX object 
> Filters/Sources/CMakeFiles/vtkFiltersSourcesJava.dir/vtkGraphToPolyDataJava.cxx.o
> cd /<>/debian/build/Filters/Sources && /usr/bin/mpic++ 
> -DVTK_IN_VTK -DvtkFiltersSourcesJava_EXPORTS 
> -I/<>/debian/build/Filters/Sources 
> -I/<>/Filters/Sources 
> -I/<>/debian/build/Common/ComputationalGeometry 
> -I/<>/Common/ComputationalGeometry 
> -I/<>/debian/build/Common/Core -I/<>/Common/Core 
> -I/<>/debian/build/Utilities/KWIML 
> -I/<>/Utilities/KWIML 
> -I/<>/debian/build/Utilities/KWSys 
> -I/<>/Utilities/KWSys 
> -I/<>/debian/build/Common/DataModel 
> -I/<>/Common/DataModel 
> -I/<>/debian/build/Common/Math -I/<>/Common/Math 
> -I/<>/debian/build/Common/Misc -I/<>/Common/Misc 
> -I/<>/debian/build/Common/System 
> -I/<>/Common/System 
> -I/<>/debian/build/Common/Transforms 
> -I/<>/Common/Transforms 
> -I/<>/debian/build/Common/ExecutionModel 
> -I/<>/Common/ExecutionModel 
> -I/<>/debian/build/Filters/Core -I/<>/Filters/Core 
> -I/<>/debian/build/Filters/General 
> -I/<>/Filters/General 
> -I/<>/debian/build/Wrapping/Java 
> -I/<>/Wrapping/Java -I/usr/lib/jvm/default-java/include 
> -I/usr/lib/jvm/default-java/include/linux -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -o 
> CMakeFiles/vtkFiltersSourcesJava.dir/vtkGraphToPolyDataJava.cxx.o -c 
> /<>/debian/build/Filters/Sources/vtkGraphToPolyDataJava.cxx
> /<>/Rendering/FreeType/vtkFreeTypeTools.cxx: In member function 
> ‘virtual FT_Error vtkFreeTypeTools::CreateFTCManager()’:
> /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:1132:26: error: 
> ‘vtkFreeTypeToolsFaceRequester’ was not declared in this scope; did you mean 
> ‘vtkFreeTypeToolsCleanupCounter’?
>  1132 |  vtkFreeTypeToolsFaceRequester,
>   |  ^
>   |  vtkFreeTypeToolsCleanupCounter
> ...

Bug#977090: marked as done (The 1.3.7a original tarball includes IETF RFCs documents)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 22:00:21 +
with message-id 
and subject line Bug#977090: fixed in proftpd-dfsg 1.3.7a+dfsg-1
has caused the Debian Bug report #977090,
regarding The 1.3.7a original tarball includes IETF RFCs documents
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.)


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

Source: proftpd-dfsg
Version: 1.3.7a-1
Severity: serious
Justification: Policy 2.2.1

As in subject, the RFCs need to be stripped before uploading a new upstream
tarball, because not compliant to DFSG. That step was missed at the time of
upload.

--
Francesco P. Lovergine
--- End Message ---
--- Begin Message ---
Source: proftpd-dfsg
Source-Version: 1.3.7a+dfsg-1
Done: Francesco Paolo Lovergine 

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-dfsg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2020 22:02:18 +0100
Source: proftpd-dfsg
Binary: proftpd-basic proftpd-basic-dbgsym proftpd-dev proftpd-doc 
proftpd-mod-crypto proftpd-mod-crypto-dbgsym proftpd-mod-geoip 
proftpd-mod-geoip-dbgsym proftpd-mod-ldap proftpd-mod-ldap-dbgsym 
proftpd-mod-mysql proftpd-mod-mysql-dbgsym proftpd-mod-odbc 
proftpd-mod-odbc-dbgsym proftpd-mod-pgsql proftpd-mod-pgsql-dbgsym 
proftpd-mod-snmp proftpd-mod-snmp-dbgsym proftpd-mod-sqlite 
proftpd-mod-sqlite-dbgsym proftpd-mod-wrap proftpd-mod-wrap-dbgsym
Architecture: source amd64 all
Version: 1.3.7a+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-basic - Versatile, virtual-hosting FTP daemon - binaries
 proftpd-dev - Versatile, virtual-hosting FTP daemon - development files
 proftpd-doc - Versatile, virtual-hosting FTP daemon - documentation
 proftpd-mod-crypto - Versatile, virtual-hosting FTP daemon - SNMP module
 proftpd-mod-geoip - Versatile, virtual-hosting FTP daemon - GeoIP module
 proftpd-mod-ldap - Versatile, virtual-hosting FTP daemon - LDAP module
 proftpd-mod-mysql - Versatile, virtual-hosting FTP daemon - MySQL module
 proftpd-mod-odbc - Versatile, virtual-hosting FTP daemon - ODBC module
 proftpd-mod-pgsql - Versatile, virtual-hosting FTP daemon - PostgreSQL module
 proftpd-mod-snmp - Versatile, virtual-hosting FTP daemon - SNMP module
 proftpd-mod-sqlite - Versatile, virtual-hosting FTP daemon - SQLite3 module
 proftpd-mod-wrap - Versatile, virtual-hosting FTP daemon - SNMP module
Closes: 977090
Changes:
 proftpd-dfsg (1.3.7a+dfsg-1) unstable; urgency=medium
 .
   * Re-uploaded without the upstream distributed IETF RFC docs.
 (closes: #977090)
Checksums-Sha1:
 a7249572b27f5f75e17114ad90e81d565b591996 3052 proftpd-dfsg_1.3.7a+dfsg-1.dsc
 e6a02a44166bd36548a5132c41f3fb4270b33c95 20276614 
proftpd-dfsg_1.3.7a+dfsg.orig.tar.gz
 2783b17dc0d277318a809d07e274d35f78e01bb5 76320 
proftpd-dfsg_1.3.7a+dfsg-1.debian.tar.xz
 15b927154dd9017dece21effe458edd098b0c2d2 2519320 
proftpd-basic-dbgsym_1.3.7a+dfsg-1_amd64.deb
 931758a11132137ce29814067594ac6488eadb6e 2512276 
proftpd-basic_1.3.7a+dfsg-1_amd64.deb
 7e616934f520ee6873836d113e6c4ff7d18d 2930752 
proftpd-dev_1.3.7a+dfsg-1_amd64.deb
 f32aa907b78434bbca53b686c8291c6099634f75 14191 
proftpd-dfsg_1.3.7a+dfsg-1_amd64.buildinfo
 5dd616807d319658dc29911c0c7f161bd47d03c3 1697720 
proftpd-doc_1.3.7a+dfsg-1_all.deb
 36e51cffd29c21e525844612a553acb3ea5d9c2c 774504 
proftpd-mod-crypto-dbgsym_1.3.7a+dfsg-1_amd64.deb
 7a5cf682ab7173bbd4d30b91214cfdbc41a7d8cf 753960 
proftpd-mod-crypto_1.3.7a+dfsg-1_amd64.deb
 46e9781c5f2ab7cf400d06684e2bc7340b114602 25996 
proftpd-mod-geoip-dbgsym_1.3.7a+dfsg-1_amd64.deb
 6cda170891f0792ddedda2cf9a10ae1bf82b1342 501532 
proftpd-mod-geoip_1.3.7a+dfsg-1_amd64.deb
 ab9de38d13fc02174d66af835861f7c43923efb6 50936 
proftpd-mod-ldap-dbgsym_1.3.7a+dfsg-1_amd64.deb
 aab476176eba9ae8172aa69c

Bug#970747: marked as done (liblinphone-dev: should depend on liblinphone++10)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 22:00:11 +
with message-id 
and subject line Bug#970747: fixed in linphone 4.4.15-1
has caused the Debian Bug report #970747,
regarding liblinphone-dev: should depend on liblinphone++10
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.)


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

Package: liblinphone-dev
Version: 4.4.0-1
Severity: serious

While building linphone-desktop, I hit the following build error:


CMake Error at /usr/share/LinphoneCxx/cmake/LinphoneCxxTargets.cmake:70 
(message):

 The imported target "linphone++" references the file

"/usr/lib/x86_64-linux-gnu/liblinphone++.so.10"

 but this file does not exist.  Possible reasons include:

 * The file was deleted, renamed, or moved to another location.

 * An install or uninstall procedure did not complete successfully.

 * The installation package was faulty and contained

"/usr/share/LinphoneCxx/cmake/LinphoneCxxTargets.cmake"

 but not all the files it references.

Call Stack (most recent call first):
 /usr/share/LinphoneCxx/cmake/LinphoneCxxConfig.cmake:33 (include)
 CMakeLists.txt:165 (find_package)



dilinger@e7470:/home/dev/linphone-desktop-4.2.2$ dpkg -S 
/usr/lib/x86_64-linux-gnu/liblinphone*so

liblinphone-dev: /usr/lib/x86_64-linux-gnu/liblinphone++.so
liblinphone-dev: /usr/lib/x86_64-linux-gnu/liblinphone.so

dilinger@e7470:/home/dev/linphone-desktop-4.2.2$ ls -lh 
/usr/lib/x86_64-linux-gnu/liblinphone*so
lrwxrwxrwx 1 root root 19 Aug 31 19:03 
/usr/lib/x86_64-linux-gnu/liblinphone++.so -> liblinphone++.so.10
lrwxrwxrwx 1 root root 17 Aug 31 19:03 
/usr/lib/x86_64-linux-gnu/liblinphone.so -> liblinphone.so.10


dilinger@e7470:/home/dev/linphone-desktop-4.2.2$ ls -lh 
/usr/lib/x86_64-linux-gnu/liblinphone*so.10
-rw-r--r-- 1 root root 3.6M Aug 31 19:03 
/usr/lib/x86_64-linux-gnu/liblinphone.so.10



As you can see, liblinphone++.so.10 is missing. It seems like
liblinphone-dev should depend on both liblinphone10 AND
liblinphone++10, but right now it only depends on
liblinphone10.
--- End Message ---
--- Begin Message ---
Source: linphone
Source-Version: 4.4.15-1
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated linphone package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Dec 2020 12:04:23 +0100
Source: linphone
Binary: liblinphone++10 liblinphone++10-dbgsym liblinphone-dev liblinphone10 
liblinphone10-dbgsym linphone-cli linphone-cli-dbgsym linphone-common 
linphone-nogtk
Architecture: source amd64 all
Version: 4.4.15-1
Distribution: experimental
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Description:
 liblinphone++10 - Linphone's shared library part (supporting the SIP protocol)
 liblinphone-dev - Linphone web phone's library - development files
 liblinphone10 - Linphone's shared library part (supporting the SIP protocol)
 linphone-cli - SIP softphone - console-only client
 linphone-common - Shared components of the linphone SIP softphone
 linphone-nogtk - SIP softphone - console-only client (transitional package)
Closes: 970747
Changes:
 linphone (4.4.15-1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream version 4.4.15
   * Rename linphone-nogtk to linphone-cli (there is no gtk version anymore),
 add transitional package
   * Add some dependencies to liblinphone-dev (Closes: #970747)
   * Bump to debhelper-compat 12
   * Adjust Vcs-* for subproject
   * Bump SV to 4.5.1.0, no changes
   * Bump libbctoolbox-dev build-dep
   * Install linphone-daemon and belr grammar
Checksums-Sha1:
 f202649bb835726e9ec7855ee8cb66a40b509cee 2753 linphone_4.4.15-1.dsc
 d959536fa9ed1e3f36c7232ef3945b225ec17194 20499034 linphone_4.4.15.orig.tar.gz
 c5e9d262b0ecc9c48c228bd5b062725cc12c5665 131888 linphone_4.4.15-1.debian.tar.xz
 205e318a97e69944fec7a8d9021b9cab36d735f6 1881640

Bug#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/

[Andreas Henriksson]

Hello Lucas Nussbaum,

On Sat, Dec 05, 2020 at 02:23:54PM +0100, Lucas Nussbaum wrote:
> Source: golang-github-shirou-gopsutil
> Version: 2.19.11-3
> Severity: serious
> Justification: FTBFS on arm64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201205 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on arm64 (I don't know if it also fails on amd64).
[...]
> > === RUN   TestCpuInfo
> > cpu_test.go:90: could not get CPU Info: 
> > {"cpu":0,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"0","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > cpu_test.go:90: could not get CPU Info: 
> > {"cpu":1,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"1","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > cpu_test.go:90: could not get CPU Info: 
> > {"cpu":2,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"2","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > cpu_test.go:90: could not get CPU Info: 
> > {"cpu":3,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"3","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > --- FAIL: TestCpuInfo (0.00s)
[...]
> > FAIL
> > FAILgithub.com/shirou/gopsutil/cpu  0.047s
[...]
> > FAIL
> > dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 
> > github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu 
> > github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker 
> > github.com/shirou/gopsutil/host github.com/shirou/gopsutil/internal/common 
> > github.com/shirou/gopsutil/load github.com/shirou/gopsutil/mem 
> > github.com/shirou/gopsutil/net github.com/shirou/gopsutil/process returned 
> > exit code 1
> 
> The full build log is available from:
>
> http://qa-logs.debian.net/2020/12/05/golang-github-shirou-gopsutil_2.19.11-3_unstable.log
[...]

With the above log I will, without ever looking deeper at the problem,
claim that gopsutil parsing of /proc/cpuinfo does not work on your
architecture of choice.

I've briefly dug into this package in the past[1] and unless my memory
serves me wrong my conclusion was that gopsutil's assumptions about
/proc is not intended to be portable between architectures at all.
On the other hand /proc looking wildly different between architectures
on linux is kind of a problem that each architecture that is not the
most popular one is setting themselves up for problems with. Not even
using the same syntax in /proc/cpuinfo (or even using same keywords
as used on mainstream archs, but give them a different meaning!).

I would personally expect that porters steps up if they want a
particular piece of software ported to their arch, but I doubt that will
happen. I also very much doubt anyone else will port to a wide range of
architectures, or even a single one - plus maintain it.

I can thus suggest one "solution":
Disable the testsuite on !amd64 and just let it build without actually
ever having a chance of working except possibly by chance.
(We all did this for so many years while kfreebsd was still a testing
migration blocker, so it's not like my suggestion is a new idea.)

HTH.

Regards,
Andreas Henriksson


[1]: https://github.com/shirou/gopsutil/pull/269

Bug#976291: marked as done (rails: please drop Build-Depends on qunit-selenium)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 21:49:41 +
with message-id 
and subject line Bug#976291: fixed in rails 2:6.0.3.4+dfsg-2
has caused the Debian Bug report #976291,
regarding rails: please drop Build-Depends on qunit-selenium
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.)


-- 
976291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rails
Version: 2:6.0.3.4+dfsg-1
Severity: serious
Justification: removal of chromium

Dear rails maintainers,

I love tests. As one of the maintainers of the ci.debian.net
infrastructure, I really do. However, with my Release Team member hat
on, I'm asking you to stop Build-Depending on qunit-selenium which you
need to run your build time tests.

The reason I'm asking is that we want to remove chromium from bullseye
because it's currently in a bad shape and qunit-selenium Depends on it,
so has to go too.

Paul



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rails
Source-Version: 2:6.0.3.4+dfsg-2
Done: Utkarsh Gupta 

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated rails 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, 12 Dec 2020 02:42:08 +0530
Source: rails
Architecture: source
Version: 2:6.0.3.4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Utkarsh Gupta 
Closes: 974065 976291
Changes:
 rails (2:6.0.3.4+dfsg-2) unstable; urgency=medium
 .
   [ Pirate Praveen ]
   * Allow build with "nocheck" build profile to skip selenium
 dependency. (Closes: #974065)
 - Thanks, Sven Mueller, for the patch.
   * Drop build dependency on qunit-selenium. (Closes: #976291)
 - We do not have tests enabled that need qunit-selenium.
 .
   [ Utkarsh Gupta ]
   * Fix d/control spacing issue.
   * Remove unnecessary version guards.
 + cme fix dpkg to the resuce.
   * Bump debhelper-compat to 13.
   * Re-format d/gbp.conf.
 - To help properly branch out stuff.
Checksums-Sha1:
 ce1148d7d44256c271f4400a9ac41b4f7db552f8 4856 rails_6.0.3.4+dfsg-2.dsc
 bcfcaf7d3d1c6eb6d6dfffaa58392c9346e78b6b 97452 
rails_6.0.3.4+dfsg-2.debian.tar.xz
 70c81cd9d3228ef2ea1604d663e344332bcc7008 34234 
rails_6.0.3.4+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 0f37d8fb9bd8b6c5498591dbb793c8f98670df5ede55fb6117a296c41def0d0c 4856 
rails_6.0.3.4+dfsg-2.dsc
 ef1035ea8a8fecaf474f3b1aeddb9212136990b618fe79488585a6a35720c99f 97452 
rails_6.0.3.4+dfsg-2.debian.tar.xz
 016a9a3af6183c136162966869f8c91a1441fd56d302455bb2adf5f8f2e17214 34234 
rails_6.0.3.4+dfsg-2_amd64.buildinfo
Files:
 6d39689ade46ddfac23b58cb36c0dc53 4856 ruby optional rails_6.0.3.4+dfsg-2.dsc
 1cb74cf10cfecc608ee8cdfcaeb2af81 97452 ruby optional 
rails_6.0.3.4+dfsg-2.debian.tar.xz
 51e5eb013723e2b0400687bdbbc2e4e3 34234 ruby optional 
rails_6.0.3.4+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl/T44oTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlrXBEACNyhQIW+SOMcO8J8q98JJYC+BgloC6
pJ6lmjl66SDTaTFD2MsGP12Ef3gsPH6pdEXrXgQbKt6pozgmOA9nzPmQvYobDkmf
huA2ByvsV7nGSVymjAYBVgUjfdNt6R0Rrj0SYAH9KAP6y7juprYqDZAIdoKBULKm
nWrLrD2AhdzZTEt040yZlxx5d4/5dSd1xW1xGDPacXTFVIEJkivfIRIUyT8103F7
BN4ruLUz7FdNdzmxiojdK9YrcthWCTKDLoKUosXIdWWZef/fsQS55KqZj3h1CzCF
i7xNc+0RkGOPdyfxzIJYRzPMvfimc8A/329mNuxDhASzn9o04yacH+U5eQvR3ZTw
RibZI6kgHTkZ0TDe99UxV1ep7SGIRRRYajJJoZ2Njq2UpKCKYPvXFjf6b1R1IZJH
LoMkPIhrqREUKMBBpHcXetVuE4f6qMY5r7Thy1OdXJZ3raww3caBZ0Dn9KSUzjWa
CQmauGtyHfsGmXk6LzNsl1xPPmy+f9PsNna2h+Aavlmq5gQlFGNWev7z4HVNTuX+
FZ+Lp02mbd10VemR9pgwnhCPzdgcosS/pfNncPxkhltUyg/Y54j3VNPuacaPqaYf
vXqbi/SPer/V4hj8/S0MKZhwucw4brgK/oeeCNjzK57SHSE+ExaLwWUuTeDchEQx
9X7WKePC6bopbg==
=gq4d
-END PGP SIGNATURE End Message ---

Processed: severity of 976982 is important

[Debian Bug Tracking System]

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

> severity 976982 important
Bug #976982 [telegram-desktop] telegram-desktop: Segmentation fault at start on 
Wayland GNOME
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

[Matteo F. Vescovi]

Hi Nicholas!

Sorry for the late reply.

On 2020-12-09 at 22:06 (+03), Nicholas Guriev wrote:
> I daresay the bug you reported relates to screensaver integration that
> revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does
> not work for you, it could be something else. Can you please describe
> the crash more comprehensive and attach logs and terminal output of
> telegram-desktop to identify the issue?
>
>  [1]: https://bugs.debian.org/976894

My first test is about launching simply telegram-desktop on a terminal;
this is what I get:

= = = = = >8 = = = = =
$ telegram-desktop
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
error: : cannot open
error: : cannot open
error: : cannot open
The X11 connection broke (error 2). Did the X11 server die?
Segmentation fault (core dumped)
= = = = = >8 = = = = =

If I try to export the variable you referred in your reply, I get:

= = = = = >8 = = = = =
$ QT_QPA_PLATFORM=wayland telegram-desktop 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, 
vnc, xcb.

Aborted (core dumped)
= = = = = >8 = = = = =

Feel free to ping me to gather more information about this behavior
while running on Wayland.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#976291: rails: please drop Build-Depends on qunit-selenium

[Utkarsh Gupta]

Hello,

On Fri, Dec 11, 2020 at 2:52 PM Pirate Praveen  wrote:
> On Wed, 2 Dec 2020 22:11:27 +0100 Paul Gevers  wrote:
>  > I love tests. As one of the maintainers of the ci.debian.net
>  > infrastructure, I really do. However, with my Release Team member hat
>  > on, I'm asking you to stop Build-Depending on qunit-selenium which you
>  > need to run your build time tests.
>  >
>  > The reason I'm asking is that we want to remove chromium from bullseye
>  > because it's currently in a bad shape and qunit-selenium Depends on it,
>  > so has to go too.
>
> This is now applied in the git repo. Utkarsh wanted to make some more
> changes before the upload.

Alrighty, so it seems that it's time to say goodbye to chromium o/


- u

Bug#975135: marked as done (vtk6: FTBFS: vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 21:21:00 +
with message-id 
and subject line Bug#975135: fixed in vtk6 6.3.0+dfsg2-7
has caused the Debian Bug report #975135,
regarding vtk6: FTBFS: vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate 
‘QPainterPath path’ has incomplete type and cannot be defined
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.)


-- 
975135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtk6
Version: 6.3.0+dfsg2-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/debian/build'
> [ 85%] Building CXX object 
> GUISupport/QtOpenGL/CMakeFiles/vtkGUISupportQtOpenGL.dir/QVTKGraphicsItem.cxx.o
> cd /<>/debian/build/GUISupport/QtOpenGL && /usr/bin/mpic++ 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB 
> -DVTK_IN_VTK -DvtkGUISupportQtOpenGL_EXPORTS 
> -I/<>/debian/build/GUISupport/Qt 
> -I/<>/GUISupport/Qt 
> -I/<>/debian/build/Common/ExecutionModel 
> -I/<>/Common/ExecutionModel 
> -I/<>/debian/build/Common/DataModel 
> -I/<>/Common/DataModel 
> -I/<>/debian/build/Common/Math -I/<>/Common/Math 
> -I/<>/debian/build/Common/Core -I/<>/Common/Core 
> -I/<>/debian/build/Utilities/KWSys 
> -I/<>/Utilities/KWSys 
> -I/<>/debian/build/Common/Misc -I/<>/Common/Misc 
> -I/<>/debian/build/Common/System 
> -I/<>/Common/System 
> -I/<>/debian/build/Common/Transforms 
> -I/<>/Common/Transforms 
> -I/<>/debian/build/Filters/Extraction 
> -I/<>/Filters/Extraction 
> -I/<>/debian/build/Filters/Core -I/<>/Filters/Core 
> -I/<>/debian/build/Filters/General 
> -I/<>/Filters/General 
> -I/<>/debian/build/Common/ComputationalGeometry 
> -I/<>/Common/ComputationalGeometry 
> -I/<>/debian/build/Filters/Statistics 
> -I/<>/Filters/Statistics 
> -I/<>/debian/build/Imaging/Fourier 
> -I/<>/Imaging/Fourier 
> -I/<>/debian/build/Imaging/Core -I/<>/Imaging/Core 
> -I/<>/debian/build/ThirdParty/alglib 
> -I/<>/ThirdParty/alglib 
> -I/<>/debian/build/Interaction/Style 
> -I/<>/Interaction/Style 
> -I/<>/debian/build/Filters/Sources 
> -I/<>/Filters/Sources 
> -I/<>/debian/build/Rendering/Core 
> -I/<>/Rendering/Core 
> -I/<>/debian/build/Common/Color -I/<>/Common/Color 
> -I/<>/debian/build/Filters/Geometry 
> -I/<>/Filters/Geometry 
> -I/<>/debian/build/Rendering/OpenGL 
> -I/<>/Rendering/OpenGL 
> -I/<>/debian/build/Imaging/Hybrid 
> -I/<>/Imaging/Hybrid -I/<>/debian/build/IO/Image 
> -I/<>/IO/Image 
> -I/<>/debian/build/Utilities/DICOMParser 
> -I/<>/Utilities/DICOMParser 
> -I/<>/debian/build/IO/Core -I/<>/IO/Core 
> -I/<>/debian/build/ThirdParty/zlib 
> -I/<>/ThirdParty/zlib 
> -I/<>/debian/build/Utilities/MetaIO/vtkmetaio 
> -I/<>/debian/build/Utilities/MetaIO 
> -I/<>/Utilities/MetaIO 
> -I/<>/debian/build/ThirdParty/jpeg 
> -I/<>/ThirdParty/jpeg 
> -I/<>/debian/build/ThirdParty/png 
> -I/<>/ThirdParty/png 
> -I/<>/debian/build/ThirdParty/tiff 
> -I/<>/ThirdParty/tiff 
> -I/<>/debian/build/Utilities/ParseOGLExt 
> -I/<>/Utilities/ParseOGLExt 
> -I/<>/debian/build/Utilities/EncodeString 
> -I/<>/Utilities/EncodeString 
> -I/<>/debian/build/GUISupport/QtOpenGL 
> -I/<>/GUISupport/QtOpenGL -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVTK_USE_BOOST  
> -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -o 
> CMakeFiles/vtkGUISupportQtOpenGL.dir/QVTKGraphicsItem.cxx.o -c 
> /<>/GUISupport/QtOpenGL/QVTKGraphicsItem.cxx
> [ 85%] Building CXX object 
> Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/vtkQtInitialization.cxx.o
> cd /<>/debian/build/Rendering/Qt && /usr/bin/mpic++ 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DVTK_IN_VTK 
> -DvtkRenderingQt_EXPORTS -I/<>/debian/build/Filters/Sources 
> -I/<>/Filters/Sources 
> -I/<>/debian/build/Common/ComputationalGeometry 
> -I/<>/Common/ComputationalGeometry 
> -I/<>/debian/build/Common/DataModel 
> -I/<>/Common/DataModel 
> -I/<>/debian/build/Common/Math -I/<>/Common/Math 
> -I/<>/debian/build/Common/Core -I/<>/Common/Core 
> -I/<>/d

Bug#976977: marked as done (vtk6 FTBFS with freetype 2.10.4)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 21:21:00 +
with message-id 
and subject line Bug#976977: fixed in vtk6 6.3.0+dfsg2-7
has caused the Debian Bug report #976977,
regarding vtk6 FTBFS with freetype 2.10.4
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.)


-- 
976977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtk6
Version: 6.3.0+dfsg2-6
Severity: serious
Tags: ftbfs

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

...
/<>/Rendering/FreeType/vtkFreeTypeUtilities.cxx:336:1: error: 
expected constructor, destructor, or type conversion before 
‘vtkFreeTypeUtilitiesFaceRequester’
  336 | vtkFreeTypeUtilitiesFaceRequester(FTC_FaceID face_id,
  | ^
/<>/Rendering/FreeType/vtkFreeTypeUtilities.cxx: In member 
function ‘void vtkFreeTypeUtilities::InitializeCacheManager()’:
/<>/Rendering/FreeType/vtkFreeTypeUtilities.cxx:484:27: error: 
‘vtkFreeTypeUtilitiesFaceRequester’ was not declared in this scope; did you 
mean ‘vtkFreeTypeUtilitiesCleanup’?
  484 |   vtkFreeTypeUtilitiesFaceRequester,
  |   ^
  |   vtkFreeTypeUtilitiesCleanup
...
--- End Message ---
--- Begin Message ---
Source: vtk6
Source-Version: 6.3.0+dfsg2-7
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated vtk6 
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, 11 Dec 2020 20:12:37 +0100
Source: vtk6
Architecture: source
Version: 6.3.0+dfsg2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gianfranco Costamagna 
Closes: 975135 976977
Changes:
 vtk6 (6.3.0+dfsg2-7) unstable; urgency=medium
 .
   [ Gert Wollny ]
   * d/*: remove support for QT, no reverse deps, Closes: #975135
   * d/control: Update standards, no changes
 .
   [ Gianfranco Costamagna ]
   * Team upload
   * debian/patches/3edc0de2b04ae1e100c229e592d6b9fa94f2915a.patch:
 - cherry-pick and rebase upstream build fix for new freetype (Closes:
   #976977)
Checksums-Sha1:
 a87687d178681182073c10fefa71ca8939e4bb2a 2964 vtk6_6.3.0+dfsg2-7.dsc
 c74147804f0ac5e0a01967e25f041735c9af2a9a 31644 vtk6_6.3.0+dfsg2-7.debian.tar.xz
 a45b522d31ce10d76d56a6f5c2cf1f5aca619919 13719 
vtk6_6.3.0+dfsg2-7_source.buildinfo
Checksums-Sha256:
 d8607b6eac1f3059515d35a68c3061a8d4e079e9c04650519a23e6d2faebad4c 2964 
vtk6_6.3.0+dfsg2-7.dsc
 4e72c1640b79b0aca5d145c3b3252e455ef3533e9e52601c569a2d7ffb10ce31 31644 
vtk6_6.3.0+dfsg2-7.debian.tar.xz
 d2c7a23c4e74fbc6a55627558ec159c1ed36a46644e36378da8b4c15e523bdd5 13719 
vtk6_6.3.0+dfsg2-7_source.buildinfo
Files:
 bf68877499b12696202e229d6b3b05f5 2964 graphics optional vtk6_6.3.0+dfsg2-7.dsc
 f9ec7ff5ae0f0a450a05cbb1ca39c970 31644 graphics optional 
vtk6_6.3.0+dfsg2-7.debian.tar.xz
 f6fcc78f7937caa6f7e5276aaedb047f 13719 graphics optional 
vtk6_6.3.0+dfsg2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/T4C0ACgkQ0+Fzg8+n
/wa1VA//a7CcGOJSSZyUdCEMf52uL4/OveIYfEC8vLmwIGCSVkHiJWNyKfsrCzvp
RH1SGXcj8TA6GvcSwxQuiMOo7MSKaBcaymCL7QdbjKny1t6jaVlC0ngMdXQSyrYL
7CbRbh+Wzq7WiXtB6hqLz4BMZtC84Ep+HiO+emvThMgXdCU70y9XLj2xfmSBPFgM
EDtovbdS5hTGwIWQG4t8OupNi2BhQpTaEioaxc1ADm65NfQmmgUwdryZeKtHuztB
PZVcSQ3JHBq7ZoCSaFJ9e85R0ZMep+sbbo/T10jE+P9MEtV1WAK1n1Q8JoU1ak/A
qcAIqaiW5BYHB0ZlxeK9KbwYBon6415kaoPUHNwGY325nbpGe0ijTRMGDbC41mbJ
vW/OXdozLjML9fWc8GHKlBQ4JA65LEfwQ0juew0u0S5AD3D5dR4HYzPZ0pN1+kt/
Qkdj4TqBQwqQuOBGrYszTObupKdNNg8oHLD4tQk1PVtzdJhJDTganMerv2W7NAoG
4EFxrZ3bxKUWFTZ7ypYKU+85JhfBvkGk76cmOYZqIhFxql8uHUddFDGPD1c0Oe80
RgOMZaba6X01Bk7cbx9vrqOw37VTQFHtagx9ugbXeJMG+iOl0EdQgn5fy9JeP3hr
u6mg3wFknte4OhNAsPPI9tuWzu9e13W1QpN4rcX3SJ5yMkTLZKg=
=K40m
-END PGP SIGNATURE End Message ---

Bug#939951: marked as done (keybinder-3.0: fails to build with gtk-doc 1.32)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 21:06:01 +
with message-id 
and subject line Bug#939951: fixed in keybinder-3.0 0.3.2-1.1
has caused the Debian Bug report #939951,
regarding keybinder-3.0: fails to build with gtk-doc 1.32
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.)


-- 
939951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keybinder-3.0
Severity: important
Control: block 939500 by -1

Hello,

Your package seems to fail to build from source with the new gtk-doc-tools 1.32 
(currently in experimental).
The issue seems to be that your sgml files include a file that's no longer 
being generated when there's no content to put in it.

https://gitlab.gnome.org/GNOME/gtk-doc/commit/97541700fe55bf5ba1522773dd242a4598cac187

"... As a notable change we don't output empty tree_index files
anymore."


The build failure snippet looks something similar to this:

warning: failed to load external entity "../xml/tree_index.sgml"
../foobar.sgml:63: element include: XInclude error : could not load 
../xml/tree_index.sgml, and no fallback was found

Possible solutions could be:
- remove the lines referencing the non-existant (and previously empty) 
tree_index.sgml file.
- extend the include of tree_index.sgml with additional  tags.

For an example of the first alternative see:
https://salsa.debian.org/gnome-team/brasero/blob/f38e3a5838157432799c0ee29cebcca334af8f5a/debian/patches/0002-Stop-referencing-empty-Object-Hierarchy.patch

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: keybinder-3.0
Source-Version: 0.3.2-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated keybinder-3.0 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, 11 Dec 2020 21:25:52 +0100
Source: keybinder-3.0
Architecture: source
Version: 0.3.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Starr-Bochicchio 
Changed-By: Paul Gevers 
Closes: 887344 939951
Changes:
 keybinder-3.0 (0.3.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Andreas Beckmann ]
   * Ship README.rst.  (Closes: #887344)
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Paul Gevers ]
   * Fix FTBFS by not referencing documents that were empty (Closes:
 #939951)
Checksums-Sha1:
 d321fb22d567635a4fe44fb1148a72148786c212 2028 keybinder-3.0_0.3.2-1.1.dsc
 6a12d94b325b98b796b79ce5e3088b272f822e60 3624 
keybinder-3.0_0.3.2-1.1.debian.tar.xz
Checksums-Sha256:
 ae1af61455baeb3e86ed46b4ca32777f4056811c0e8d5fc7f58cfa5590b3b895 2028 
keybinder-3.0_0.3.2-1.1.dsc
 59d4f3371dc07537856fb8fe38bb9b450c2c58d663bc2ba146647f8f4953b3de 3624 
keybinder-3.0_0.3.2-1.1.debian.tar.xz
Files:
 7888dd9043eee8fdb46e5c16b27f2375 2028 libs optional keybinder-3.0_0.3.2-1.1.dsc
 f1afa9d6c42488f18c6aad1bfe4fbc91 3624 libs optional 
keybinder-3.0_0.3.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl/T1wwACgkQnFyZ6wW9
dQqjSgf/cDuDlfFs0aAsETt0Nq+2Npi92dyLkJoxcGJEBgAz4mCbzGZKl+8Qyjnv
6j9xjv77RHWfd+Oa4F7V84YIKEs971iVcy0iXZJ7NbaSsrn/vAHk83AZ5x/CVrwn
nCZC1mPb8XFWfXNgbajYjrqdeivQ1uQfO5d/LZ+Ep2k0FbPICFmcukVBoWVfLN0Z
VSv5XKfvHHfObEcKH8NXpz2P4VzG/bArMxNsJHX62HBxr90L4CsnlugHqB2Rx4k8
Jyjez/K4DF4LIWqasfEykKD58r14BPsOPczDHwyjmiI6RjfNynvMO70wC8u6oNwk
xFbqE48OyhWfLOk+oOa8jFnbffxY5Q==
=EUIo
-END PGP SIGNATURE End Message ---

Bug#963654: marked as done (pillow: FTBFS with Sphinx 3.1: /<>/docs/conf.py:292: RemovedInSphinx40Warning: The app.add_javascript() is deprecated. Please use app.add_js_file() instead.)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 21:40:44 +0100
with message-id <8a309805-fa02-0d1a-48e4-0d97884ac...@debian.org>
and subject line Re: pillow: FTBFS with Sphinx 3.1: 
/<>/docs/conf.py:292: RemovedInSphinx40Warning: The 
app.add_javascript() is deprecated. Please use app.add_js_file() instead.
has caused the Debian Bug report #963654,
regarding pillow: FTBFS with Sphinx 3.1: /<>/docs/conf.py:292: 
RemovedInSphinx40Warning: The app.add_javascript() is deprecated. Please use 
app.add_js_file() instead.
to be marked as done.

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

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


-- 
963654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow
Version: 7.0.0-4
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx3.1

Hi,

pillow fails to build with Sphinx 3.1, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/docs'
> sphinx-build -b html -W --keep-going -d _build/doctrees   . _build/html
> Running Sphinx v3.1.1
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 73 source files that are out of date
> updating environment: [new config] 73 added, 0 changed, 0 removed
> reading sources... [  1%] PIL
> reading sources... [  2%] about
> reading sources... [  4%] deprecations
> reading sources... [  5%] handbook/appendices
> reading sources... [  6%] handbook/concepts
> reading sources... [  8%] handbook/image-file-formats
> reading sources... [  9%] handbook/index
> reading sources... [ 10%] handbook/overview
> reading sources... [ 12%] handbook/tutorial
> reading sources... [ 13%] handbook/writing-your-own-file-decoder
> reading sources... [ 15%] index
> reading sources... [ 16%] installation
> reading sources... [ 17%] porting
> reading sources... [ 19%] reference/ExifTags
> reading sources... [ 20%] reference/Image
> reading sources... [ 21%] reference/ImageChops
> reading sources... [ 23%] reference/ImageCms
> reading sources... [ 24%] reference/ImageColor
> reading sources... [ 26%] reference/ImageDraw
> reading sources... [ 27%] reference/ImageEnhance
> reading sources... [ 28%] reference/ImageFile
> reading sources... [ 30%] reference/ImageFilter
> reading sources... [ 31%] reference/ImageFont
> reading sources... [ 32%] reference/ImageGrab
> reading sources... [ 34%] reference/ImageMath
> reading sources... [ 35%] reference/ImageMorph
> reading sources... [ 36%] reference/ImageOps
> reading sources... [ 38%] reference/ImagePalette
> reading sources... [ 39%] reference/ImagePath
> reading sources... [ 41%] reference/ImageQt
> reading sources... [ 42%] reference/ImageSequence
> reading sources... [ 43%] reference/ImageStat
> reading sources... [ 45%] reference/ImageTk
> reading sources... [ 46%] reference/ImageWin
> reading sources... [ 47%] reference/PSDraw
> reading sources... [ 49%] reference/PixelAccess
> reading sources... [ 50%] reference/PyAccess
> reading sources... [ 52%] reference/TiffTags
> reading sources... [ 53%] reference/block_allocator
> reading sources... [ 54%] reference/index
> reading sources... [ 56%] reference/internal_design
> reading sources... [ 57%] reference/limits
> reading sources... [ 58%] reference/open_files
> reading sources... [ 60%] reference/plugins
> reading sources... [ 61%] releasenotes/2.7.0
> reading sources... [ 63%] releasenotes/2.8.0
> reading sources... [ 64%] releasenotes/3.0.0
> reading sources... [ 65%] releasenotes/3.1.0
> reading sources... [ 67%] releasenotes/3.1.1
> reading sources... [ 68%] releasenotes/3.1.2
> reading sources... [ 69%] releasenotes/3.2.0
> reading sources... [ 71%] releasenotes/3.3.0
> reading sources... [ 72%] releasenotes/3.3.2
> reading sources... [ 73%] releasenotes/3.4.0
> reading sources... [ 75%] releasenotes/4.0.0
> reading sources... [ 76%] releasenotes/4.1.0
> reading sources... [ 78%] releasenotes/4.1.1
> reading sources... [ 79%] releasenotes/4.2.0
> reading sources... [ 80%] releasenotes/4.2.1
> reading sources... [ 82%] releasenotes/4.3.0
> reading sources... [ 83%] releasenotes/5.0.0
> reading sources... [ 84%] releasenotes/5.1.0
> reading sources... [ 86%] releasenotes/5.2.0
> reading sources... [ 87%] releasenotes/5.3.0
> reading sources... [ 89%] releasenotes/5.4.0
> reading sources... [ 90%] releasenotes/5.4.1
> reading sources... [ 91%] releasenotes/6.0.0
> reading sources... [ 93%] releasenotes/6.1.0
> reading sources... [ 94%] releasenotes/6.2.0
> reading sources... [ 95%] releasenotes/6.2.1
> r

Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

[Mike Gabriel]

Hi Paul,

On  Fr 11 Dez 2020 20:43:00 CET, Paul Gevers wrote:


Hi Mike,

All bugs have caused the packages to be on the list for autoremoval. It
seems there is one bug to be filed still, can you please do that?

Paul




screenkey: screenkey<- unfiled yet (added this year)


I have just filed a new bug against screenke and I have also added it  
as a blocker to this tracking bug).


Mike

--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpcNBdmp315q.pgp
Description: Digitale PGP-Signatur

Processed: Please switch to Ayatana AppIndicator

[Debian Bug Tracking System]

Processing control commands:

> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; 
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956762 956771 956781 974146 956767 956764 956779 906026 
956778 956776 956765 956761 956772 956777 956782 956770 956774 956780 956769 
921339 956768 956775 956766 956773
895037 was blocking: 895038
Added blocking bug(s) of 895037: 977156

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

Bug#939952: marked as done (keybinder: fails to build with gtk-doc 1.32)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 20:39:02 +
with message-id 
and subject line Bug#939952: fixed in keybinder 0.3.1-2.1
has caused the Debian Bug report #939952,
regarding keybinder: fails to build with gtk-doc 1.32
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.)


-- 
939952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keybinder
Severity: important
Control: block 939500 by -1

Hello,

Your package seems to fail to build from source with the new gtk-doc-tools 1.32 
(currently in experimental).
The issue seems to be that your sgml files include a file that's no longer 
being generated when there's no content to put in it.

https://gitlab.gnome.org/GNOME/gtk-doc/commit/97541700fe55bf5ba1522773dd242a4598cac187

"... As a notable change we don't output empty tree_index files
anymore."


The build failure snippet looks something similar to this:

warning: failed to load external entity "../xml/tree_index.sgml"
../foobar.sgml:63: element include: XInclude error : could not load 
../xml/tree_index.sgml, and no fallback was found

Possible solutions could be:
- remove the lines referencing the non-existant (and previously empty) 
tree_index.sgml file.
- extend the include of tree_index.sgml with additional  tags.

For an example of the first alternative see:
https://salsa.debian.org/gnome-team/brasero/blob/f38e3a5838157432799c0ee29cebcca334af8f5a/debian/patches/0002-Stop-referencing-empty-Object-Hierarchy.patch

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: keybinder
Source-Version: 0.3.1-2.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated keybinder 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, 11 Dec 2020 20:58:40 +0100
Source: keybinder
Architecture: source
Version: 0.3.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Starr-Bochicchio 
Changed-By: Paul Gevers 
Closes: 939952
Changes:
 keybinder (0.3.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS by not referencing documents that were empty (Closes:
 #939952)
Checksums-Sha1:
 814954858e3e7c5b1a78721b1cddebea699b8097 1842 keybinder_0.3.1-2.1.dsc
 a041b54cd7953fd69f865d0813ef307d26225d76 6484 keybinder_0.3.1-2.1.debian.tar.xz
Checksums-Sha256:
 49162b0662903da55468a6ac95231e6138f6d1d6cdea7bf294293df1dc8b43e0 1842 
keybinder_0.3.1-2.1.dsc
 6617ece232fa9d1a80b32e8f2a707171151648a8b433513a1da21bcc959dacc6 6484 
keybinder_0.3.1-2.1.debian.tar.xz
Files:
 b43c0c8c8dbbc78e7bc0c5859ed33e29 1842 libs optional keybinder_0.3.1-2.1.dsc
 a86866a255ae763705fc81f014e3f653 6484 libs optional 
keybinder_0.3.1-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl/T030ACgkQnFyZ6wW9
dQpKSgf7BMNJkYrrBiAc8vixH8ikspmbpS4BfCKA4VAbrXjmxJm3NKewomABDvOl
dzTFpcoZwc/0VJpfcedX18wCD0KHk9IagsAAStzrVqKCtM2GtpJcXSbvTYhjWatl
ty/S2fxr03+ntDkw3BXsfEkhh9tyvgjMS0HMzpMz6FIttRCG7MbjuP8/pYhMaTxr
uXx056a5B4idSjUUBqVuxldHjJEtSXtx0k7luqU77Yte/yZXFThAQqz97Uzz1Ts+
boJEQxnm/QOe/CbeXxpTN2ywxu/YsG+E92xBhDOmw+UsuORi8MsaHH6uOzPtFROu
qUjFOpFO/9wvA6CcMUJxg9PsT96XSg==
=mNry
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#976976 closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#976976: fixed in vtk7 7.1.1+dfsg2-5)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #976976 {Done: Gianfranco Costamagna } [src:vtk7] 
vtk7 FTBFS with freetype 2.10.4
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vtk7/7.1.1+dfsg2-5.

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

Processed: Re: keybinder, keybinder-3.0, kylin-burner: fails to build with gtk-doc 1.32

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #939952 [src:keybinder] keybinder: fails to build with gtk-doc 1.32
Added tag(s) pending.

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

Bug#939952: keybinder, keybinder-3.0, kylin-burner: fails to build with gtk-doc 1.32

[Paul Gevers]

Control: tags -1 pending

Hi,

I uploaded a fixed package. The changes are in the bug-939952 branch in
the salsa archive.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976976: closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#976976: fixed in vtk7 7.1.1+dfsg2-5)

[Adrian Bunk]

Control: reopen -1

On Fri, Dec 11, 2020 at 07:21:08PM +, Debian Bug Tracking System wrote:
>...
>  vtk7 (7.1.1+dfsg2-5) unstable; urgency=medium
>...
>* debian/patches/3edc0de2b04ae1e100c229e592d6b9fa94f2915a.patch:
>  - cherry-pick and rebase upstream build fix for new freetype (Closes:
>#976976)
>...

Still FTBFS:
https://buildd.debian.org/status/package.php?p=vtk7&suite=sid

cu
Adrian

Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

[Paul Gevers]

Hi Mike,

All bugs have caused the packages to be on the list for autoremoval. It
seems there is one bug to be filed still, can you please do that?

Paul

elbrus@coccia:~$ dak rm --no-action -R  --suite testing libappindicator
Will remove the following packages from testing:

gir1.2-appindicator-0.1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
gir1.2-appindicator3-0.1 |   0.4.92-8 | amd64, arm64, armel, armhf,
i386, mips64el, mipsel, ppc64el, s390x
libappindicator |   0.4.92-8 | source
libappindicator-dev |   0.4.92-8 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libappindicator-doc |   0.4.92-8 | all
libappindicator1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libappindicator3-1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libappindicator3-dev |   0.4.92-8 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x

Maintainer: Debian QA Group 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
autokey: autokey-gtk#956762
fusion-icon: fusion-icon#956767 (fixed today)
gromit-mpx: gromit-mpx  #956769 (fixed today)
hime: hime  #956772
kylin-burner: libburner-media3-1#956774
osdlyrics: osdlyrics#956776
parcellite: parcellite  #956778
psensor: psensor#921339
redshift: redshift-gtk  #956779
screenkey: screenkey<- unfiled yet (added this year)

# Broken Build-Depends:
gcin: libappindicator3-dev  #956766
gromit-mpx: libappindicator3-dev#956769 (fixed today)
hime: libappindicator-dev   #956772
kylin-burner: libappindicator3-dev (>= 0.0.7)   #956774
osdlyrics: libappindicator-dev  #956776
parcellite: libappindicator-dev #956778
psensor: libappindicator3-dev   #921339
zeal: libappindicator-dev   #956782

Dependency problem found.




elbrus@coccia:~$ dak rm --no-action -R  --suite testing libindicator
Will remove the following packages from testing:

libindicator |0.5.0-4 | source
libindicator-dev |0.5.0-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libindicator-tools |0.5.0-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libindicator3-7 |0.5.0-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libindicator3-dev |0.5.0-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libindicator3-tools |0.5.0-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
libindicator7 |0.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x

Maintainer: Debian QA Group 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
libappindicator: libappindicator1   # well.
 libappindicator3-1

# Broken Build-Depends:
libappindicator: libindicator-dev (>= 0.3.90)   # well.
 libindicator3-dev (>= 0.3.90)

Dependency problem found.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976976: marked as done (vtk7 FTBFS with freetype 2.10.4)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 19:20:00 +
with message-id 
and subject line Bug#976976: fixed in vtk7 7.1.1+dfsg2-5
has caused the Debian Bug report #976976,
regarding vtk7 FTBFS with freetype 2.10.4
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.)


-- 
976976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtk7
Version: 7.1.1+dfsg2-4
Severity: serious
Tags: ftbfs

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

...
/<>/Rendering/FreeType/vtkFreeTypeTools.cxx:277:1: error: expected 
constructor, destructor, or type conversion before 
‘vtkFreeTypeToolsFaceRequester’
  277 | vtkFreeTypeToolsFaceRequester(FTC_FaceID face_id,
  | ^
[ 49%] Building CXX object 
Filters/Sources/CMakeFiles/vtkFiltersSourcesJava.dir/vtkGraphToPolyDataJava.cxx.o
cd /<>/debian/build/Filters/Sources && /usr/bin/mpic++ 
-DVTK_IN_VTK -DvtkFiltersSourcesJava_EXPORTS 
-I/<>/debian/build/Filters/Sources 
-I/<>/Filters/Sources 
-I/<>/debian/build/Common/ComputationalGeometry 
-I/<>/Common/ComputationalGeometry 
-I/<>/debian/build/Common/Core -I/<>/Common/Core 
-I/<>/debian/build/Utilities/KWIML 
-I/<>/Utilities/KWIML 
-I/<>/debian/build/Utilities/KWSys 
-I/<>/Utilities/KWSys 
-I/<>/debian/build/Common/DataModel 
-I/<>/Common/DataModel -I/<>/debian/build/Common/Math 
-I/<>/Common/Math -I/<>/debian/build/Common/Misc 
-I/<>/Common/Misc -I/<>/debian/build/Common/System 
-I/<>/Common/System 
-I/<>/debian/build/Common/Transforms 
-I/<>/Common/Transforms 
-I/<>/debian/build/Common/ExecutionModel 
-I/<>/Common/ExecutionModel 
-I/<>/debian/build/Filters/Core -I/<>/Filters/Core 
-I/<>/debian/build/Filters/General 
-I/<>/Filters/General 
-I/<>/debian/build/Wrapping/Java -I/<>/Wrapping/Java 
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -o 
CMakeFiles/vtkFiltersSourcesJava.dir/vtkGraphToPolyDataJava.cxx.o -c 
/<>/debian/build/Filters/Sources/vtkGraphToPolyDataJava.cxx
/<>/Rendering/FreeType/vtkFreeTypeTools.cxx: In member function 
‘virtual FT_Error vtkFreeTypeTools::CreateFTCManager()’:
/<>/Rendering/FreeType/vtkFreeTypeTools.cxx:1132:26: error: 
‘vtkFreeTypeToolsFaceRequester’ was not declared in this scope; did you mean 
‘vtkFreeTypeToolsCleanupCounter’?
 1132 |  vtkFreeTypeToolsFaceRequester,
  |  ^
  |  vtkFreeTypeToolsCleanupCounter
...
--- End Message ---
--- Begin Message ---
Source: vtk7
Source-Version: 7.1.1+dfsg2-5
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated vtk7 
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, 11 Dec 2020 20:05:14 +0100
Source: vtk7
Architecture: source
Version: 7.1.1+dfsg2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 
Changed-By: Gianfranco Costamagna 
Closes: 976976
Changes:
 vtk7 (7.1.1+dfsg2-5) unstable; urgency=medium
 .
   * Team upload
   * debian/patches/3edc0de2b04ae1e100c229e592d6b9fa94f2915a.patch:
 - cherry-pick and rebase upstream build fix for new freetype (Closes:
   #976976)
Checksums-Sha1:
 a3c3a5e991a5cc1658c6cfa852e4d521cd19fe04 3905 vtk7_7.1.1+dfsg2-5.dsc
 38cadf77fbc1129f35dfb2f90df9957f8818b219 27872 vtk7_7.1.1+dfsg2-5.debian.tar.xz
 a5ff7b51799be0d0e7874103907a63aff68706db 22994 
vtk7_7.1.1+dfsg2-5_source.buildinfo
Checksums-Sha256:
 9da653bbfecaea0708b0f9b236f150cd1d6d1903ee745ebf53a9799c38e57d91 3905 
vtk7_7.1.1+dfsg2-5.dsc
 0e63009faabf6e68f92a7c5472cdba8fdcdfe15b0639e6f064b2c5b50a43c0de 27872 
vtk7_7.1.1+dfsg2-5.debian.tar.xz
 0cab9c99b99bacb96edb01378ac0b23d48014e8e195412d23d7ce32a895da546 22994 
vtk7_7.1.1+dfsg2-5_source.buildinfo
Files:
 83f8de1c8d1ce9762603977bd4b

Bug#974705: Changes to job handling cause hangs in wait

[Michael Biebl]

Hi Herbert

On Mon, 7 Dec 2020 14:55:06 +1100 Herbert Xu  
wrote:

> Sorry, my bad.  wait(1) with no arguments ignores the error status
> of the child and always return zero.  wait(1) specifically on a
> child obviously returns the error status of that child.  Since the
> child was killed, we need to ignore that, so this works for me:
> 
>   wait $MONPID 2> /dev/null || :

Hah, I basically came to the same result in
https://salsa.debian.org/systemd-team/systemd/-/commit/85438481ca690f627c58d86aad6193f0ad5df21c

I see that this has been addressed in dash now as well, so thanks for
that!


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

Bug#976906: marked as done (libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 18:33:45 +
with message-id 
and subject line Bug#976906: fixed in libpll 0.3.2-4
has caused the Debian Bug report #976906,
regarding libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: 
parse_utree.h: No such file or directory
to be marked as done.

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

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


-- 
976906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpll
Version: 0.3.2-3
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package currently has
ppc64el binary packages in unstable (so this is a regression).

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
>  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 
> -O3 -fPIC -g -c -o libpll_la-lex_utree.lo `test -f 'lex_utree.c' || echo 
> './'`lex_utree.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c fasta.c  -fPIC -DPIC -o .libs/libpll_la-fasta.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c pll.c  -fPIC -DPIC -o .libs/libpll_la-pll.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c likelihood.c  -fPIC -DPIC -o .libs/libpll_la-likelihood.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c maps.c  -fPIC -DPIC -o .libs/libpll_la-maps.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c output.c  -fPIC -DPIC -o .libs/libpll_la-output.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c utree.c  -fPIC -DPIC -o .libs/libpll_la-utree.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c utree_moves.c  -fPIC -DPIC -o .libs/libpll_la-utree_moves.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c models.c  -fPIC -DPIC -o .libs/libpll_la-models.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c parsimony.c  -fPIC -DPIC -o .libs/libpll_la-parsimony.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c core_partials.c  -fPIC -DPIC -o .libs/libpll_la-core_partials.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c derivatives.c  -fPIC -DPIC -o .libs/libpll_la-derivatives.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c utree_svg.c  -fPIC -DPIC -o .libs/libpll_la-utree_svg.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c gamma.c  -fPIC -DPIC -o .libs/libpll_la-gamma.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c rtree.c  -fPIC -DPIC -o .libs/libpll_la-rtree.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c list.c  -fPIC -DPIC -o .libs/libpll_la-list.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c partials.c  -fPIC -DPIC -o .libs/libpll_la-partials.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -fPIC -g 
> -c compress.c  -fPIC -DPIC -o .libs/libpll_la-compress.o
> libtool: comp

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

[Andreas Tille]

Hi Frédéric

On Fri, Dec 11, 2020 at 09:59:03AM +0100, Frédéric Bonnard wrote:
> Here is a patch based on this :
> https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html
> 
> Tested on a power machine (where the build failed) and it seems to work.

Thanks a lot

   Andreas.

-- 
http://fam-tille.de

Bug#976299: marked as done (xalan: FTBFS during separate binary-indep build)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 18:05:08 +
with message-id 
and subject line Bug#976299: fixed in xalan 1.12-3
has caused the Debian Bug report #976299,
regarding xalan: FTBFS during separate binary-indep build
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.)


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

Hi,

xalan FTBFS during a separate binary-indep build, i.e. dpkg-buildpackage -A,
because it tries to run unittests whose binaries have not been built.
This will be a problem for a source-only upload since the buildds will build
the 'amd64' and the 'all' binary packages in separate runs.

   dh_auto_test -i
cd obj-x86_64-linux-gnu && make -j3 test ARGS\+=-j3
make[1]: Entering directory '/build/xalan-1.12/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j3
Test project /build/xalan-1.12/obj-x86_64-linux-gnu
  Start  1: CompileStylesheet
Could not find executable 
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/CompileStylesheet
Looked in the following places:
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Release/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Release/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Debug/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Debug/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/MinSizeRel/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/MinSizeRel/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/RelWithDebInfo/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/RelWithDebInfo/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Deployment/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Deployment/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Development/CompileStylesheet
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/Development/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Release/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Release/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Debug/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Debug/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/MinSizeRel/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/MinSizeRel/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/RelWithDebInfo/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/RelWithDebInfo/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Deployment/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Deployment/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Development/CompileStylesheet
build/xalan-1.12/obj-x86_64-linux-gnu/samples/Development/CompileStylesheet
Unable to find executable: 
/build/xalan-1.12/obj-x86_64-linux-gnu/samples/CompileStylesheet
 1/21 Test  #1: CompileStylesheet ***Not Run   0.00 sec
[...]


Andreas


xalan_1.12-1_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xalan
Source-Version: 1.12-3
Done: William Blough 

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

Debian distribution maintenance software
pp.
William Blough  (supplier of updated xalan 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, 11 Dec 2020 12:24:22 -0500
Source: xalan
Architecture: source
Version: 1.12-3
Distribution: experimental
Urgency: medium
Maintainer: William Blough 
Changed-By: 

Processed: Bug#976900 marked as pending in pyside2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976900 [src:pyside2] pyside2 hard-codes Python 3.8 in it's install files
Added tag(s) pending.

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

Bug#976900: marked as pending in pyside2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #976900 in pyside2 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/qt-kde-team/qt/pyside2/-/commit/23baba66e952ef6a03f5b6cf7bd3e5bf314e8c6b


Stop hardcoding py3.8 in debian/shiboken2-doc.docs.

Just py3* will work even if there are two supported Python versions:
dh_installdocs will process two directories one after the other, and
the contents of the last directory will remain.

Closes: #976900.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976900

Bug#935313: marked as done (missing ebtables dependency)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 12:50:40 -0500
with message-id <87lfe4ut8v@angela.anarc.at>
and subject line Re: missing ebtables dependency
has caused the Debian Bug report #935313,
regarding missing ebtables dependency
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.)


-- 
935313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon
Version: 5.0.0-4
Severity: grave
File: /usr/sbin/libvirtd

Vagrant, using the libvirt backend, started failing me recently, with
something like this:

anarcat@curie:stretch64(master)$ vagrant up --provider libvirt
Bringing machine 'default' up with 'libvirt' provider...
==> default: Checking if box 'debian/stretch64' version '9.9.0' is up to date...
Error while activating network: Call to virNetworkCreate failed: internal 
error: Failed to initialize a valid firewall backend.
[1]anarcat@curie:stretch64(master)$ 

Syslog had more details, but nothing really informative:

aoû 21 09:24:16 curie NetworkManager[819]:   [1566393856.0718] manager: 
(virbr1): new Bridge device (/org/freedesktop/NetworkManager/Devices/5) 
aoû 21 09:24:16 curie systemd-udevd[24139]: Using default interface naming 
scheme 'v240'. 
aoû 21 09:24:16 curie systemd-udevd[24139]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable. 
aoû 21 09:24:16 curie systemd-udevd[24139]: Could not generate persistent MAC 
address for virbr1: No such file or directory 
aoû 21 09:24:16 curie kernel: tun: Universal TUN/TAP device driver, 1.6 
aoû 21 09:24:16 curie NetworkManager[819]:   [1566393856.0795] manager: 
(virbr1-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/6) 
aoû 21 09:24:16 curie systemd-udevd[24144]: Using default interface naming 
scheme 'v240'. 
aoû 21 09:24:16 curie systemd-udevd[24144]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable. 
aoû 21 09:24:16 curie libvirtd[1862]: internal error: Failed to initialize a 
valid firewall backend 
aoû 21 09:24:16 curie kernel: virbr1: port 1(virbr1-nic) entered blocking state 
aoû 21 09:24:16 curie kernel: virbr1: port 1(virbr1-nic) entered disabled state 
aoû 21 09:24:16 curie kernel: device virbr1-nic entered promiscuous mode 
aoû 21 09:24:16 curie kernel: device virbr1-nic left promiscuous mode 
aoû 21 09:24:16 curie kernel: virbr1: port 1(virbr1-nic) entered disabled state 
aoû 21 09:24:16 curie systemd[3139]: Starting pull emails with syncmaildir... 
aoû 21 09:24:16 curie NetworkManager[819]:   [1566393856.1114] device 
(virbr1-nic): released from master device virbr1 
aoû 21 09:24:16 curie libvirtd[1862]: Failed to open file 
'/sys/class/net/virbr1-nic/operstate': Aucun fichier ou dossier de ce type 
aoû 21 09:24:16 curie libvirtd[1862]: unable to read: 
/sys/class/net/virbr1-nic/operstate: Aucun fichier ou dossier de ce type 

Restarting libvirtd, however, did provide some insightful input:

aoû 21 10:10:05 curie systemd[1]: Starting Virtualization daemon...
aoû 21 10:10:05 curie libvirtd[31223]: libvirt version: 5.0.0, package: 4 
(Guido Günther  Mon, 17 Jun 2019 19:05:40 +0200)
aoû 21 10:10:05 curie libvirtd[31223]: hostname: curie
aoû 21 10:10:05 curie libvirtd[31223]: Libvirt doesn't support VirtualBox API 
version 610
aoû 21 10:10:05 curie systemd[1]: Started Virtualization daemon.
aoû 21 10:10:05 curie libvirtd[31223]: direct firewall backend requested, but 
/usr/sbin/ebtables is not available: Aucun fichier ou dossier de ce type
aoû 21 10:10:05 curie libvirtd[31223]: internal error: Failed to initialize a 
valid firewall backend

`apt install ebtables` fixed this problem, so I feel this should be
marked as a runtime dependency for the package. Obviously, it would be
better to migrate to nftables, but that's another story...

a.

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CA.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 libvirt-daemon depends on:
ii  libacl1 2.2.53-4
ii  libapparmor12.13.2-10
ii  libaudit1   1:2.8.4-3
ii  libavahi-client30.7-4+b1
ii  libavahi-common30.7-4+b1
ii  libblkid1   2.33.1-0.1
ii  libc6   2.28-10
ii  libcap-ng0  0.7.9-2
ii  libcurl3-gnu

Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue

[tony mancill]

Hi Sven!

On Fri, Dec 11, 2020 at 11:17:55AM +0100, Sven Mueller wrote:
> libopencensus-java is used via libgoogle-http-client-java
>  ...
> So libopencensus-java depends on grpc-context in io.grpc (provided by
> package libgrpc-java).
> But it turns out that we rebuild against debian-testing as of early
> November, which had version: 0.23.0+ds-1 - and that had no declared
> dependency on libgrpc-java.
> 0.24.0-1 does have that dependency.

I am glad that you brought this to the list.  It gives us an opportunity
to talk about this type of ephemeral bug with transitive dependencies.
The package was FTBFS in testing and the declared dependencies didn't
help expose that.  

In retrospect, what I should have done is either: (a) declare a versioned
dependency on libopencensus-java (which seems wrong, because it's not
the actual version of opencensus that makes the difference); or (b) add
libgrpc-java to the build-deps for anything that uses opencensus, as you
suggested.

Or at a minimum, we could have filed a bug against libopencensus-java
and marked it as affecting all reverse build-deps.

So, my apologies for the confusion this created.  Even though it is
resolved now, it could bite us during a backport, so I am going to add
the dependency on libgrpc-java in the next upload.

Thank you,
tony


signature.asc
Description: PGP signature

Bug#977139: geeqie: fails immediatly after start

[Ilya Ovchinnikov]

On 11.12.2020 19:17, Andreas Ronnquist wrote:

On Fri, 11 Dec 2020 17:50:07 +0300
Ilya Ovchinnikov  wrote:


Package: geeqie
Version: 1:1.6-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last upgrade geeqie fails to start:

% geeqie

(geeqie:987585): Gtk-CRITICAL **: 17:45:52.857:
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar



Thanks for the report -

Is that all that gets printed, and you get a prompt immediately after?
Or does it give a segfault or similar?


It shows the main window for a moment, and hangs till Ctrl+C


What video-card are you using?


Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)


I am guessing you are running X? (You can quickly find out by the
command

echo $XDG_SESSION_TYPE
in the terminal.)


x11



/Andreas




~% gdb /usr/bin/geeqie
GNU gdb (Debian 10.1-1.3) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/geeqie...
(No debugging symbols found in /usr/bin/geeqie)
(gdb) run
Starting program: /usr/bin/geeqie
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7117700 (LWP 990914)]
[New Thread 0x7fffe6916700 (LWP 990915)]
[New Thread 0x7fffe6115700 (LWP 990916)]
[New Thread 0x7fffe5914700 (LWP 990917)]
[New Thread 0x7fffe4fcb700 (LWP 990918)]
[New Thread 0x7fffc700 (LWP 990919)]
[Detaching after vfork from child process 990920]
[Detaching after vfork from child process 990922]
[Detaching after vfork from child process 990924]
[Detaching after vfork from child process 990926]

(geeqie:990910): Gtk-CRITICAL **: 19:28:20.690: gtk_box_gadget_distribute: assertion 'size 
>= 0' failed in GtkScrollbar

[New Thread 0x7fffcf7fe700 (LWP 990928)]
[New Thread 0x7fffceffd700 (LWP 990929)]
[Detaching after vfork from child process 990930]
[Detaching after vfork from child process 990932]
[Detaching after vfork from child process 990934]
[Detaching after vfork from child process 990936]
[Thread 0x7fffceffd700 (LWP 990929) exited]
^C
Thread 1 "geeqie" received signal SIGINT, Interrupt.
0x7617a39f in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x7617a39f in poll () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x77230e1e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7723117b in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x77a407a5 in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x555c9916 in  ()
#5  0x760add0a in __libc_start_main () at 
/lib/x86_64-linux-gnu/libc.so.6
#6  0x555ca54a in  ()
(gdb)

Bug#976451: marked as done (springlobby: FTBFS in with libjsoncpp/experimental)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 16:35:13 +
with message-id 
and subject line Bug#976451: fixed in springlobby 0.270-3
has caused the Debian Bug report #976451,
regarding springlobby: FTBFS in with libjsoncpp/experimental
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.)


-- 
976451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: springlobby
Version: 0.270-2
Severity: important
tags: patch

Hello, looks like springlobby fails to build with newer jsoncpp because the 
cmake looks for features.h header file, something
that disappeared in newer libjsoncpp.

Looking for json.h header file works as a patch.

Please apply if possible, and forward upstream if you think its needed.

--- springlobby-0.270.orig/src/downloader/lib/cmake/FindJsoncpp.cmake
+++ springlobby-0.270/src/downloader/lib/cmake/FindJsoncpp.cmake
@@ -14,7 +14,7 @@ if(PKG_CONFIG_FOUND)
 endif()
 # Include dir
 find_path(Jsoncpp_INCLUDE_DIR
-  NAMES json/features.h
+  NAMES json/json.h
   PATH_SUFFIXES jsoncpp
   PATHS ${Jsoncpp_PKGCONF_INCLUDE_DIRS} # /usr/include/jsoncpp/json
 )


G.
--- End Message ---
--- Begin Message ---
Source: springlobby
Source-Version: 0.270-3
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
springlobby package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Dec 2020 18:24:00 +0100
Source: springlobby
Architecture: source
Version: 0.270-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Gianfranco Costamagna 
Closes: 976451
Changes:
 springlobby (0.270-3) unstable; urgency=medium
 .
   * Team upload
   * debian/patches/libjsoncpp.patch:
 Fix build with newer jsoncpp (Closes: #976451)
Checksums-Sha1:
 56ca15ff0a9d01366da5086b7ad364d9a5bc861d 2150 springlobby_0.270-3.dsc
 3f950e5568a0a76f89abf916caaf0354935607ca 17452 
springlobby_0.270-3.debian.tar.xz
 a439097bc749d661ff721ef90e3d3411d1b7e442 10025 
springlobby_0.270-3_source.buildinfo
Checksums-Sha256:
 28e34bc8934c4fa20357c4c2b43258e8d5be13c5366e0d817f5bbe1fd419aba6 2150 
springlobby_0.270-3.dsc
 33b766f61358c31c79fb857444e7d26d5ac6c3dde107476d4824221592e8da10 17452 
springlobby_0.270-3.debian.tar.xz
 a27fd878c93cbd300249d054bd9b32ffb09cb815e08a738ec6f2d5d86fd232ff 10025 
springlobby_0.270-3_source.buildinfo
Files:
 f67e879bca8727cd95d6ea30bdc45317 2150 games optional springlobby_0.270-3.dsc
 d5336c8564e1e0ecad2e488ff3290201 17452 games optional 
springlobby_0.270-3.debian.tar.xz
 c2aeb2350d384ade8ebf80f9b3943c60 10025 games optional 
springlobby_0.270-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl/Tm7sACgkQ808JdE6f
Xdk0tw//ZH0MGB4wHhYYXva4k11GjbdCoWDQpBPUDAxeGI4tBxy5MI8t9RKtr1Mx
u21qrLtX7cfHjXJRcsv7DICWXjwaelV5JXrncdsnDcEq7ZRl3ky9Q6xiiTpgh/2p
1AqWCCDbGVLWKXJuSUAVbTcizPWUHvXYXRedpSE50B1HBZL0p7F9vPCaXqlIcBxs
CuMWNY3txs9Yml36bHU4HkcF5avbgZVP9Frkm+IBespCX00hyLlICX49HGnj+B0h
9Y9MTaYBUC3pnom422hazz6u1KgWiiBouWCbTXZyHPet/Kfm2s5LaJ7wltZxhfDh
/rhlKowImOpwwu6q9hdkl1aanJjTNUw5RFfTqd4qnY/C1egkRAFUgBwNEYoE9vkN
2AiOFKO28QrgVPDIc9dZWIhFQLRLPuX0JKnBMWkfOVJxrRNVlgV7bm+/7yBlkgCt
aPl3weof3phpay7qovT39wAmu/7EWjMuMhXP89z6gsnZdThNQMng1Nxh+TPh4P9s
SGBlrs4Y5T5+62DDQeZjg4qpztHtRDakBhHDDLw/bWfwQzoKGLmAnBFsVH7/AoSf
IS3DIy3EJVJOnaKixeXL19OlS/69vBWiEKovPb1BoADdu8rU8fwhuyjtjPnVfPfv
UviPUFE1816oBvzn8f8Y0DwArvONmiucRfS9nzhcq3a7r49m0Js=
=MBxy
-END PGP SIGNATURE End Message ---

Bug#976452: marked as done (spring: FTBFS in with libjsoncpp/experimental)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 16:35:07 +
with message-id 
and subject line Bug#976452: fixed in spring 104.0+dfsg-8
has caused the Debian Bug report #976452,
regarding spring: FTBFS in with libjsoncpp/experimental
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.)


-- 
976452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spring
Version: 104.0+dfsg-7
Severity: important
tags: patch

Hello, looks like spring fails to build with newer jsoncpp because the cmake 
looks for features.h header file, something
that disappeared in newer libjsoncpp.

Looking for json.h header file works as a patch.

Please apply if possible, and forward upstream if you think its needed.

--- spring-104.0+dfsg.orig/tools/pr-downloader/cmake/FindJsoncpp.cmake
+++ spring-104.0+dfsg/tools/pr-downloader/cmake/FindJsoncpp.cmake
@@ -14,7 +14,7 @@ if(PKG_CONFIG_FOUND)
 endif()
 # Include dir
 find_path(Jsoncpp_INCLUDE_DIR
-  NAMES json/features.h
+  NAMES json/json.h
   PATH_SUFFIXES jsoncpp
   PATHS ${Jsoncpp_PKGCONF_INCLUDE_DIRS} # /usr/include/jsoncpp/json
 )



G.
--- End Message ---
--- Begin Message ---
Source: spring
Source-Version: 104.0+dfsg-8
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated spring 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Dec 2020 18:21:59 +0100
Source: spring
Architecture: source
Version: 104.0+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Gianfranco Costamagna 
Closes: 976452
Changes:
 spring (104.0+dfsg-8) unstable; urgency=medium
 .
   * Team upload
   * debian/patches/libjsoncpp.patch:
 Fix build with newer jsoncpp (Closes: #976452)
Checksums-Sha1:
 74ade797527428b2655e70ba4fe8d9a9d31e115c 2368 spring_104.0+dfsg-8.dsc
 7a2b0046e2e022290096ee5665ccd5f9b405ecc8 20296 
spring_104.0+dfsg-8.debian.tar.xz
 6dc877c714da7991d30b452d51a55599527a8083 15613 
spring_104.0+dfsg-8_source.buildinfo
Checksums-Sha256:
 34d291c70e54c9dad41f8cb372f54967ad0bc58898133392cbede2eaba0a5dac 2368 
spring_104.0+dfsg-8.dsc
 84bff325b2c3f48e533fd70d49e334e39b61e87f6925936396470936a58334fb 20296 
spring_104.0+dfsg-8.debian.tar.xz
 5a25ca5d384c219b4313f466dccf1a0e30404ad31d0e7389a060a1f5205c1d6b 15613 
spring_104.0+dfsg-8_source.buildinfo
Files:
 3b2f0cde2c5269514299ff5f98b05e3e 2368 games optional spring_104.0+dfsg-8.dsc
 3fa35c73cc1791785f229ad6d63eb525 20296 games optional 
spring_104.0+dfsg-8.debian.tar.xz
 a6d2836a882a0063f856b95e772a8201 15613 games optional 
spring_104.0+dfsg-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl/Tm44ACgkQ808JdE6f
Xdmo7hAAqy+Mu1Dy/6ucGJGDq+okRrPHVLdNc9IbaD7iNh0vxXCrlykiRc6dYhsr
DJOp2NxPlgiQiBFvg9gP2CowB8cG92FkyIpgU3Zvo1StGu2VWJla7nmSEx8PLiTk
OeUkCgoDmbFY5iKq2uU/Uo7oaDB3siszVqpIV25Y51e93uRfv73aqy8dPYIfq2Xr
73CSWuMFDJfyZjWHgeLhmqBcINVTbURtozyRr2vqpjySECBcI1yDgBOyTmFqE8Kn
ewM31jZ+n72wNEvgdrGA03PAYE5jmh91cmeixclUBKLQJKXAA+rYpzazicQ3Ib48
//vsCtrI/S4oa+huPv6XB6eQFoF/yFQvFBLyhX2SpCZDRR7EwPyoSeP0PSZXgYpr
wcVc/tMhU6qleixBfS3fY9Mu8ESvS0K23XrS7/T4+/l4SexJC7jV6jl0ZV3ENptC
bJH6o9KgnDFys5BRQbn5GP+qLA0qvEIUPelK82+foB6zEey7037D4w7iIo1+batZ
JY4kRErdGje6DEOme8sI1MeIJFVnLf4hHsLUzn5DjtkaF9lnbKAIQHhnGyiHDsi/
6QZSwj5V3AfmG92SxVDJMOgYj1kxHTJ3X5hngW9JVhcIllRnTsr1tEGcKdrYjukp
Zxz/FfPVsbq0J5NOKXQzMhQwjWodCinTyyf5q+2FtdEhHVtaNHY=
=HAnt
-END PGP SIGNATURE End Message ---

Processed (with 1 error): python-poppler-qt5 fix was forwarded upstream

[Debian Bug Tracking System]

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

> unarchive 971217
> forwarded 971217 https://github.com/frescobaldi/python-poppler-qt5/pull/41
Bug #971217 {Done: Dmitry Shachnev } 
[src:python-poppler-qt5] python-poppler-qt5: FTBFS: sip: Unable to find file 
"QtCore/QtCoremod.sip"
Set Bug forwarded-to-address to 
'https://github.com/frescobaldi/python-poppler-qt5/pull/41'.
> archive 971217
Bug #971217 {Done: Dmitry Shachnev } 
[src:python-poppler-qt5] python-poppler-qt5: FTBFS: sip: Unable to find file 
"QtCore/QtCoremod.sip"
archived 971217 to archive/17 (from 971217)
> unarchive 964131
Bug #964131 {Done: Dmitry Shachnev } 
[src:python-poppler-qt5] python-poppler-qt5: Please switch from sip4 to sip5
Unarchived Bug 964131
> forwarded 964131 https://github.com/frescobaldi/python-poppler-qt5/pull/41
Bug #964131 {Done: Dmitry Shachnev } 
[src:python-poppler-qt5] python-poppler-qt5: Please switch from sip4 to sip5
Set Bug forwarded-to-address to 
'https://github.com/frescobaldi/python-poppler-qt5/pull/41'.
> archive 964131
Bug #964131 {Done: Dmitry Shachnev } 
[src:python-poppler-qt5] python-poppler-qt5: Please switch from sip4 to sip5
archived 964131 to archive/31 (from 964131)
> thanks
Stopping processing here.

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

Processed: Unarchive #971217

[Debian Bug Tracking System]

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

> unarchive 971217
Bug #971217 {Done: Dmitry Shachnev } 
[src:python-poppler-qt5] python-poppler-qt5: FTBFS: sip: Unable to find file 
"QtCore/QtCoremod.sip"
Unarchived Bug 971217
>
End of message, stopping processing here.

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

Bug#977139: geeqie: fails immediatly after start

[Andreas Ronnquist]

On Fri, 11 Dec 2020 17:50:07 +0300
Ilya Ovchinnikov  wrote:

>Package: geeqie
>Version: 1:1.6-2
>Severity: grave
>Justification: renders package unusable
>
>Dear Maintainer,
>
>Since last upgrade geeqie fails to start:
>
>% geeqie
>
>(geeqie:987585): Gtk-CRITICAL **: 17:45:52.857:
>gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
>

Thanks for the report -

Is that all that gets printed, and you get a prompt immediately after?
Or does it give a segfault or similar?

What video-card are you using? 

I am guessing you are running X? (You can quickly find out by the
command

echo $XDG_SESSION_TYPE

in the terminal.)

/Andreas

Processed: xscreensaver tag 967892 967232

[Debian Bug Tracking System]

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

> tag 967892 fixed-upstream
Bug #967892 [src:xscreensaver] xscreensaver: depends on deprecated libglade2
Added tag(s) fixed-upstream.
> tag 967232 fixed-upstream
Bug #967232 [src:xscreensaver] xscreensaver: Unversioned Python removal in 
sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#976935: inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #976935 [src:inkscape] inkscape: FTBFS on ppc64el: make[3]: *** No rule to 
make target 'po/zh_TW.gmo', needed by 
'share/templates/default_templates.timestamp'. Stop.
Added tag(s) unreproducible.

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

Bug#976108: marked as done (php-pear: CVE-2020-28948 CVE-2020-28949)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 15:34:11 +
with message-id 
and subject line Bug#976108: fixed in php-pear 1:1.10.9+submodules+notgz-1.1
has caused the Debian Bug report #976108,
regarding php-pear: CVE-2020-28948 CVE-2020-28949
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.)


-- 
976108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-pear
Version: 1:1.10.9+submodules+notgz-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/pear/Archive_Tar/issues/33
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:1.10.6+submodules+notgz-1.1

Hi,

The following vulnerabilities were published for php-pear.

CVE-2020-28948[0]:
| Archive_Tar through 1.4.10 allows an unserialization attack because
| phar: is blocked but PHAR: is not blocked.


CVE-2020-28949[1]:
| Archive_Tar through 1.4.10 has :// filename sanitization only to
| address phar attacks, and thus any other stream-wrapper attack (such
| as file:// to overwrite files) can still succeed.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-28948
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28948
[1] https://security-tracker.debian.org/tracker/CVE-2020-28949
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28949
[2] https://github.com/pear/Archive_Tar/issues/33
[3] 
https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: php-pear
Source-Version: 1:1.10.9+submodules+notgz-1.1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated php-pear 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: Sun, 06 Dec 2020 14:40:37 +0100
Source: php-pear
Architecture: source
Version: 1:1.10.9+submodules+notgz-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 976108
Changes:
 php-pear (1:1.10.9+submodules+notgz-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * ensure we catch additional malicious/crafted filenames (CVE-2020-28948,
 CVE-2020-28949) (Closes: #976108)
Checksums-Sha1: 
 6ec1497268182c17a91e53a94ec05c2350f6ba15 2244 
php-pear_1.10.9+submodules+notgz-1.1.dsc
 db0fdb55ba71146bd8f11533e219cf45bad1a508 8424 
php-pear_1.10.9+submodules+notgz-1.1.debian.tar.xz
Checksums-Sha256: 
 f12a5b900701e297b79a0d5b73bb340cfd8826002278c69b60c3db2fa5c4ec04 2244 
php-pear_1.10.9+submodules+notgz-1.1.dsc
 f3d7d9ad8a60e632b1e4e9a48646a61f2e52fa67a41c0e3a3c74b15a165b3d0c 8424 
php-pear_1.10.9+submodules+notgz-1.1.debian.tar.xz
Files: 
 f10792a3cff915ca643632425e14aeae 2244 php optional 
php-pear_1.10.9+submodules+notgz-1.1.dsc
 a52bd46f320e07e95e8714ef7df64c76 8424 php optional 
php-pear_1.10.9+submodules+notgz-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl/M8QxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ea/QP/jWS2MXHS3vwICe+exCMi6TUoFufXELW
4JxOz9iLSfISXsDcGqKJB9Lo3Ff7avWYv2GfJBfCjIOjh4e2HGfgfOupa5FdGISh
1AyriRFb0PmWrr6ljxZmtJWVNyH4snePTha+3m52HxciPE+wfbfqIZDMye1N3nyw
aLNMv+z8iNntg/sSSfJuYfAoqNK01pTECalqzWwR3Gzxs9ZLI+xPJyMbWyzlTPtJ
WtLVQ8BECP0wVfZ8xAdwjfQEAedfU2zOg4l4sEfs3qN3UMuxpUG4RvZpbNtzbNNQ
72DHLhh1dtTMngh9u2qrIPBDSyly/x1rj4Gn96b2tReXPUJd/KYtfu7pzABGCZBj
/KaA2pOjSaFdFpYWaCePrJwGi+Zi472P0trTA7byj8glZw6IFh5bNgoPEPh1LjH6
IF0Ucqxpoz27NgyT2oCcvsmCH8P6bACa4sWt1Mc+i4JUcuTpxxFwx1jKddeCyKgF
qm5O9dxrpT28EbGrUCT4N4X8ucKckNOrhybIGWWWaf8AufR67Ko63a75+yHQicNa
uHWGRBM9Gq87A/RsyvcjjvTWoEMGVL

Processed: Re: Bug#973505: akregator: Feeds no longer update

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #973505 [akregator] akregator: Feeds no longer update
Added tag(s) moreinfo.
> severity -1 normal
Bug #973505 [akregator] akregator: Feeds no longer update
Severity set to 'normal' from 'grave'

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

Bug#973505: akregator: Feeds no longer update

[Sandro Knauß]

control: tags -1 + moreinfo
control: severity -1 normal

Hey,

> library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so:
> (/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found
> (required by /lib/x86_64-linux-gnu/libQt5Network.so.5))

I cannot reproduce the issue you described. And from my side it seems, like 
you mixed packages, that are build against different qt versions. Can you 
verify that it is still an issue?

Regards,

hefee


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

Bug#977139: geeqie: fails immediatly after start

[Ilya Ovchinnikov]

Package: geeqie
Version: 1:1.6-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last upgrade geeqie fails to start:

% geeqie

(geeqie:987585): Gtk-CRITICAL **: 17:45:52.857:
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar


With best regards,
Ilya Ovchinnikov

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

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages geeqie depends on:
ii  geeqie-common1:1.6-2
ii  libc62.31-5
ii  libcairo21.16.0-4
ii  libchamplain-0.12-0  0.12.20-1
ii  libchamplain-gtk-0.12-0  0.12.20-1
ii  libclutter-1.0-0 1.26.4+dfsg-2
ii  libclutter-gtk-1.0-0 1.8.4-4
ii  libcogl201.22.8-2
ii  libdjvulibre21   3.5.28-1
ii  libexiv2-27  0.27.3-3
ii  libffmpegthumbnailer4v5  2.1.1-0.2+b1
ii  libgcc-s110.2.1-1
ii  libgdk-pixbuf-2.0-0  2.40.0+dfsg-10
ii  libglib2.0-0 2.66.3-2
ii  libgtk-3-0   3.24.23-3
ii  libheif1 1.9.1-1
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  liblcms2-2   2.9-4+b1
ii  liblirc-client0  0.10.1-6.2+b1
ii  liblua5.1-0  5.1.5-8.1+b3
ii  libopenjp2-7 2.3.1-1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpoppler-glib8 20.09.0-3
ii  libstdc++6   10.2.1-1
ii  libtiff5 4.1.0+git191117-2
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  sensible-utils   0.0.12+nmu1

Versions of packages geeqie recommends:
ii  cups-bsd [lpr]   2.3.3op1-3
ii  exiftran 2.10-4
ii  exiv20.27.3-3
ii  imagemagick  8:6.9.11.24+dfsg-1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.24+dfsg-1+b2
ii  librsvg2-common  2.50.2+dfsg-1
ii  ufraw-batch  0.22-4
ii  zenity   3.32.0-6

Versions of packages geeqie suggests:
pn  geeqie-dbg   
ii  gimp 2.10.22-2
ii  libjpeg-turbo-progs [libjpeg-progs]  1:2.0.5-1.1
ii  ufraw0.22-4
pn  xpaint   

-- no debconf information

Bug#956769: marked as done (gromit-mpx: Depends on deprecated libappindicator)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 15:03:27 +
with message-id 
and subject line Bug#956769: fixed in gromit-mpx 1.4-2
has caused the Debian Bug report #956769,
regarding gromit-mpx: Depends on deprecated libappindicator
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.)


-- 
956769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gromit-mpx
Version: 1.3-1
Tags: sid bullseye
Severity: important
Control: block 895037 by -1
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatana-appindicator

This package Build-Depends on libappindicator3-dev, which is
deprecated and unmaintained. The supported replacement appears to be
libayatana-appindicator3-dev.

Please see #895037 and
https://wiki.debian.org/Ayatana/IndicatorsTransition for more details
of this deprecation.

This bug might get escalated to 'serious' severity (making it
release-critical) if the maintainers of the Ayatana stack are serious about
getting libappindicator removed from Debian before bullseye.

smcv
--- End Message ---
--- Begin Message ---
Source: gromit-mpx
Source-Version: 1.4-2
Done: b...@debian.org (Barak A. Pearlmutter)

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated gromit-mpx 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, 11 Dec 2020 12:42:56 +
Source: gromit-mpx
Architecture: source
Version: 1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Closes: 956769
Changes:
 gromit-mpx (1.4-2) unstable; urgency=medium
 .
   * switch from deprecated libappindicator3-dev to
 libayatana-appindicator3-dev (closes: #956769)
Checksums-Sha1:
 6d8bfd6f43bc326f65866ad55fd2f2426bb476c4 1908 gromit-mpx_1.4-2.dsc
 536d0f88abe07fdb3e4432a77af5305abc4a0234 3184 gromit-mpx_1.4-2.debian.tar.xz
 a2d6685b3e89df494bc563dd71f8ac0b583d02d4 15101 
gromit-mpx_1.4-2_source.buildinfo
Checksums-Sha256:
 3023e4662dac6e7802841051b3f22522c64fee6d1295c84cf161d08798afc6a5 1908 
gromit-mpx_1.4-2.dsc
 add1783cfc0e3e7bb8bd4341a701e0a5e1f3d74a842014fe590136b8b1dfde7b 3184 
gromit-mpx_1.4-2.debian.tar.xz
 0b3a8c76ee3ecb06b52606da2b96b25cafb0bcb940ceba71dc562d359b783c3c 15101 
gromit-mpx_1.4-2_source.buildinfo
Files:
 d978587776dc6eafb90d9d10ae9a9c32 1908 x11 optional gromit-mpx_1.4-2.dsc
 b03d4ecc6882c86310b79e03c844c45b 3184 x11 optional 
gromit-mpx_1.4-2.debian.tar.xz
 a52cb289b5b3d614411493eab35da9c1 15101 x11 optional 
gromit-mpx_1.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAl/ThfsPHGJhcEBkZWJp
YW4ub3JnAAoJEJnrHqTSM3uI2ZsP/0bElBnlSGDztkjWMGYEe+F4+ku5anjeIF2M
k0uJMLgSkGmcvxk+oo9MZq4NAN5W7ke0DiJtscSAR1Guf+ty0jKCYqKOf+1Pj4ui
cZjlUiQ8Adlvb2ESvfTtA7Y8zquPapFTOp5IgM9ei68QikXtqrOaSzqh+gy+IeLG
k7U6uwxx422y3YocPLMNZI4xKr+fOcZCFJzclGtBXETMpduTAgULs/G2tMo9VfvT
r8nac2ZTVF2mMWcyX9/RaFQw4GxcltwBxj/zAe82whcd0F5NsEuYMWFyXvh3kl+q
uBX5bYO8bcd9gRXM0itOztLgLr7IpdaMZ2ixCyG/RDpKA9yzCVy/rXfSrJDObVhO
j/8bgcm0Mc4eGd+f2LNjGhOAsFtp7EXFfuLufcmNdAc0uIIZYysWFN9sNhYK3xOA
9FHblo7UCC0XakZXlf4ZOK9+e+IkJpnYLRUiaKRO3GPJlLQvNJ3pt0JQGSy/x3zh
X5N/1UN+VRs+/dUR7A3Iqleo4VtzTD5pK4jRIkiGw3uEqMTTXpwR+pOdKVMeWYbd
2yuVa1ammZH0dMXKjYh80Q904Ix1P0q+V5O2pvC0jMxrpMsLiSrRCteqGF3u0Si4
HTh6QLLw9Vr/pmSExCqUYAC+I0pmUDqEPHjrwN4zS4V1+wGdOy5N/7tnlJ4/xu4z
tZfXcZzO
=kTyo
-END PGP SIGNATURE End Message ---

Bug#976833: marked as done (src:procenv: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 14:34:57 +
with message-id 
and subject line Bug#976833: fixed in procenv 0.51-0.2
has caused the Debian Bug report #976833,
regarding src:procenv: invalid maintainer address
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.)


-- 
976833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: procenv
Version: 0.51-0.1
Severity: serious
X-Debbugs-Cc: Gianfranco Costamagna 

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
Subject: Mail delivery failed: returning message to sender
Date: Thu, 03 Dec 2020 18:49:39 +

> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es)
> failed:
> 
>   jamesodh...@ubuntu.com
>     host mx.canonical.com [91.189.95.10]
>     SMTP error from remote mail server after RCPT
> TO::
>     550 5.1.1 : Recipient address rejected:
>     User unknown in virtual alias table
--- End Message ---
--- Begin Message ---
Source: procenv
Source-Version: 0.51-0.2
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated procenv 
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, 11 Dec 2020 14:51:56 +0100
Source: procenv
Architecture: source
Version: 0.51-0.2
Distribution: unstable
Urgency: medium
Maintainer: James Hunt 
Changed-By: Gianfranco Costamagna 
Closes: 976833
Changes:
 procenv (0.51-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Change maintainer address to the one used to develop on github. (Closes:
 #976833)
Checksums-Sha1:
 f35ff2071983ec42e436ce0eda1ed6ac6cdbca7b 2061 procenv_0.51-0.2.dsc
 a9e084069ba0a45bd4c3be2999f2e7ec8e84e538 71232 procenv_0.51-0.2.debian.tar.xz
 56469d149c8b64eee415a62c42c1ca3c164ff25e 7079 procenv_0.51-0.2_source.buildinfo
Checksums-Sha256:
 c5dd74a90ef19800ff51813fd458eb538d1b338da8474710c3dcbd59b226e6ee 2061 
procenv_0.51-0.2.dsc
 edc9fd09256b7c51561f7572fad391a191b99c741e5b1be72eccdc0c8b0f160d 71232 
procenv_0.51-0.2.debian.tar.xz
 18d37be6b8d38c0f4f4eb621dd282cfec9df1f0ce8b70d5cd2ce9212af324b38 7079 
procenv_0.51-0.2_source.buildinfo
Files:
 b81187fd0cad4f5bb7f8bb9a8d6682a5 2061 utils optional procenv_0.51-0.2.dsc
 66ff3b2bb9dafafe2329b1241edc88d2 71232 utils optional 
procenv_0.51-0.2.debian.tar.xz
 2b1871bae83a0c9129ce02aad37959f9 7079 utils optional 
procenv_0.51-0.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl/TeZwACgkQ808JdE6f
Xdmkcw/+NQYORjBAr0Q545qnL8qzsdrVlbMubM+S0ro8p5+5vSPTEnQ5C0gBtySB
4p/L9QGDIaJD0s90Z8JhHQwvK7TaVJeDvZrNM/IHBh+l6gQMvpTFGofP742plFHA
7F+knYl3vpNSIupm+ein11J55yP/VbGYBUK+cPIrYIKfN+NY2C+VB4B9D8rgAPyP
rwMliOUxXjzuWJL2lLgUqyqI2W20t5sYQQDge0mBsxVqKHilmU/dPIrfBAmeuw2y
SAFhR7dSP3pv3Az2j/Uxa7mE2Ytrc/RlRoJF1kldkE2yxDI3w4X2Xhtsq5EFO3ng
s94wyQzA1hfX+lFAs3tzMvDSbeF0JQ4+iJn/HxRLn5NEzJHUeGPEIVcTgpDSl5Mo
4c7oxfVnsEBvCxcnDvoeYxyX1k1YLQ6YVBwQ11FHWpqDcLs8QDDTJOdP5teaaDKZ
kJWOxIxiQfVTE85XkQ+U8DGiR9McFXAbTHPRXTL/Ekmu9uO95tnf1xrMRs/odyKV
1n1XDZAp7mPLYXn/Lcc515qZK3ph4rwe5/czuKpm11IJq+UOgrzEtHZkKIXMGd69
e2DPPA2nqSZ0NbXDlK504VY7CH0Uq1tYoei0e2M8BAo7Zi67yF0VFjFVteVhhUQe
hoBsGdYfGRbkzUVNk7NdWSYqY0LHxl2e9soNYrDPvP9IPGf6LuQ=
=BFXS
-END PGP SIGNATURE End Message ---

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Michael Biebl]

Am 11.12.20 um 09:09 schrieb Lucas Nussbaum:

On 10/12/20 at 22:12 +0100, Michael Biebl wrote:

Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz:

Hi Michael!

On 12/10/20 8:42 PM, Michael Biebl wrote:


Testsuite summary for systemd-bootchart 233

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



Did the test machine you used actually have that many cores?


No idea


I tried building with SMT off (so the machine only has 20 visible
cores). I could reproduce the failure. (I disabled SMT at runtime using
ppc64_cpu --smt=off)

It also fails when running 'make check VERBOSE=1' (so it's not caused by
parallelism).

It crashes with:
(gdb) r -o /tmp/tmp.k64Np1I2cr -n 10 -r -p
Starting program: /root/systemd-bootchart-233/systemd-bootchart -o 
/tmp/tmp.k64Np1I2cr -n 10 -r -p
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00014d04 in svg_ps_bars (interval=, 
graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1,
 n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187
1187i = ps->sample->next->sampledata->counter;
(gdb) bt
#0  0x00014d04 in svg_ps_bars (interval=, 
graph_start=2775.3698308829998, ps_first=0x1000505d0,
 n_cpus=1, n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187


This looks a lot like

https://github.com/systemd/systemd-bootchart/pull/37
specifically
https://github.com/systemd/systemd-bootchart/pull/37/commits/65320230f5fcb02e81df5131a4dc03092558c263

Could you give this PR a try?

Bug#977134: qtmir-tests: Cannot fulfill the dependencies

[Adrian Bunk]

Package: qtmir-tests
Version: 0.6.1-4
Severity: serious

The following packages have unmet dependencies:
 qtmir-tests : Depends: autopilot-qt5 but it is not installable
   Depends: python3-autopilot but it is not installable
   Depends: qtdeclarative5-qtmir-plugin but it is not installable

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

On 11/12/20 at 13:42 +0100, Michael Biebl wrote:
> Am 11.12.20 um 09:09 schrieb Lucas Nussbaum:
> > 0x00014d04 in svg_ps_bars (interval=, 
> > graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1,
> >  n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187
> 
> looking at n_cpus=1,
> what's the output of /proc/schedstat?

After disabling SMT, I have:

*** lnussbaum@drac-9:~$ cat /proc/schedstat 
version 15
timestamp 4299098065
cpu0 0 0 0 0 0 0 12635131978 3504474686 123639
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu8 0 0 0 0 0 0 18601438478 5316535000 217422
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu16 0 0 0 0 0 0 9761507934 1007811740 35918
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu24 0 0 0 0 0 0 4163593780 317911678 16896
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu32 0 0 0 0 0 0 6767731546 515373412 44034
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu40 0 0 0 0 0 0 8813679098 826269308 29314
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu48 0 0 0 0 0 0 16805123862 646123252 55517
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu56 0 0 0 0 0 0 19693171880 1240342130 101541
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu64 0 0 0 0 0 0 23792508504 832970334 28997
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu72 0 0 0 0 0 0 17135726608 788801790 51002
domain0 ,,0101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu80 0 0 0 0 0 0 4285484062 453270872 112751
domain0 01010101,01010101,0101,, 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu88 0 0 0 0 0 0 1066062920 45108636 4891
domain0 01010101,01010101,0101,, 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu96 0 0 0 0 0 0 1028913816 59808984 9706
domain0 01010101,01010101,0101,, 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu104 0 0 0 0 0 0 1028350934 66980336 8086
domain0 01010101,01010101,0101,, 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu112 0 0 0 0 0 0 1015745558 48708372 5503
domain0 01010101,01010101,0101,, 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
domain1 01010101,01010101,01010101,01010101,01010101 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
cpu120 0 0 0 0 0 0 989949982 85398080 4758
domain0 01010101,01010101,01010

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

On 11/12/20 at 13:45 +0100, Michael Biebl wrote:
> Am 11.12.20 um 09:26 schrieb Lucas Nussbaum:
> > I tried to reproduce this on another system (ARM64, 256 visible cores
> > because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also
> > segfaults.
> > 
> > I tried to reproduce on yet another system (x86_64, 128 visible cores
> > because 4x Intel Xeon Gold 6130, 16 cores/cpu, 2 threads/core), and it
> > also segfaults.
> > 
> > My guess would be that the test suite depends on the system it is
> > running on (it just generates the output for the local system), and
> > there's something it doesn't like about large numbers of cores, but
> > there's nothing specific to ppc64el here.
> 
> There is also
> $ grep MAXCPUS -R
> src/bootchart.h:#define MAXCPUS16
> src/bootchart.h:double runtime[MAXCPUS];
> src/bootchart.h:double waittime[MAXCPUS];
> src/store.c:if (r < 0 || c > MAXCPUS -1)
> src/store.c:/* Oops, we only have room for
> MAXCPUS data */

Indeed, it also crashes on an x86_64 system with only 64 visible cores
(but not on one with 36 visible cores)

Lucas

Bug#975970: marked as done (bacula-director-mysql broken SQL schema for mariadb-server-10.5)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 13:03:52 +
with message-id 
and subject line Bug#975970: fixed in bacula 9.6.7-1
has caused the Debian Bug report #975970,
regarding bacula-director-mysql broken SQL schema for mariadb-server-10.5
to be marked as done.

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

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


-- 
975970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director-mysql
Version: 9.6.6-2
Severity: important


After recent version bump of mariadb-server in Bullseye, the schema in
bacula-director-mysql:
/usr/share/dbconfig-common/data/bacula-director-mysql/install/mysql is
no longer compatible with the database server


```
# /usr/bin/mysql -NB bacula <
/usr/share/dbconfig-common/data/bacula-director-mysql/install/mysql
ERROR 1005 (HY000) at line 35: Can't create table `bacula`.`File`
(errno: 150 "Foreign key constraint is incorrectly formed")
```

Any help or response will be appreciated.

Best regards
bodik



## packages installed
```
ii  bacula-bscan 9.6.6-2
amd64network backup service - bscan tool
ii  bacula-common9.6.6-2
amd64network backup service - common support files
ii  bacula-common-mysql  9.6.6-2
amd64network backup service - MySQL common files
ii  bacula-console   9.6.6-2
amd64network backup service - text console
ii  bacula-director  9.6.6-2
amd64network backup service - Director daemon
ii  bacula-director-mysql9.6.6-2
all  network backup service - MySQL storage for Director
ii  bacula-fd9.6.6-2
amd64network backup service - file daemon
ii  bacula-sd9.6.6-2
amd64network backup service - storage daemon

ii  libdbd-mariadb-perl  1.21-1+b1
amd64Perl5 database interface to the MariaDB/MySQL databases
ii  libmariadb3:amd641:10.5.8-3
amd64MariaDB database client library
ii  mariadb-client-10.5  1:10.5.8-3
amd64MariaDB database client binaries
ii  mariadb-client-core-10.5 1:10.5.8-3
amd64MariaDB database core client binaries
ii  mariadb-common   1:10.5.8-3
all  MariaDB common configuration files
ii  mariadb-server   1:10.5.8-3
all  MariaDB database server (metapackage depending on the
latest version)
ii  mariadb-server-10.5  1:10.5.8-3
amd64MariaDB database server binaries
ii  mariadb-server-core-10.5 1:10.5.8-3
amd64MariaDB database core server files
```



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bacula
Source-Version: 9.6.7-1
Done: Sven Hartge 

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

Debian distribution maintenance software
pp.
Sven Hartge  (supplier of updated bacula 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, 11 Dec 2020 12:46:12 +0100
Source: bacula
Architecture: source
Version: 9.6.7-1
Distribution: unstable
Urgency: high
Maintainer: Debian Bacula Team 
Changed-By: Sven Hartge 
Closes: 975970
Changes:
 bacula (9.6.7-1) unstable; urgency=high
 .
   * New upstream version 9.6.7
+ Adds compatibility for MariaDB 10.5 (Closes: #975970)
+ Fixes sporadic deadlock issues with MariaDB
+ Fixes compile errors with GCC10
 .
   [ Sven Hartge ]
   * Add rudimentary man-pages for b*json commands
   * Remove patches added upstream
+ fix-narrowing-magic-numbers
+ fix_en_AR.po_errors
 .
   [ Debian Janitor ]
   * Fixing Lintian tags
+ Fix day-of-week for changelog entries 1.36.3-2, 1.34.6-1, 1.32f-5-3.1.
+ Use secure URI in Homepage field.
Checksums-Sha1:
 6c1ab99b449ae95e99935dd77f8449b200ecf81c 3671 bacula_9.6.7-1.dsc
 cf548f4ab0b22761dfe2ddd5e9f0f29e0ccf77c8 4168102 bacula_9.6.7.orig.tar.gz
 37121a8deb4848c371b05dfd7cfd

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Michael Biebl]

Am 11.12.20 um 09:26 schrieb Lucas Nussbaum:

I tried to reproduce this on another system (ARM64, 256 visible cores
because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also
segfaults.

I tried to reproduce on yet another system (x86_64, 128 visible cores
because 4x Intel Xeon Gold 6130, 16 cores/cpu, 2 threads/core), and it
also segfaults.

My guess would be that the test suite depends on the system it is
running on (it just generates the output for the local system), and
there's something it doesn't like about large numbers of cores, but
there's nothing specific to ppc64el here.


There is also
$ grep MAXCPUS -R
src/bootchart.h:#define MAXCPUS16
src/bootchart.h:double runtime[MAXCPUS];
src/bootchart.h:double waittime[MAXCPUS];
src/store.c:if (r < 0 || c > MAXCPUS -1)
src/store.c:/* Oops, we only have room 
for MAXCPUS data */

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Michael Biebl]

Am 11.12.20 um 09:09 schrieb Lucas Nussbaum:

0x00014d04 in svg_ps_bars (interval=, 
graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1,
 n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187


looking at n_cpus=1,
what's the output of /proc/schedstat?

Bug#957016: marked as done (astronomical-almanac: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 12:33:21 +
with message-id 
and subject line Bug#957016: fixed in astronomical-almanac 5.6-7
has caused the Debian Bug report #957016,
regarding astronomical-almanac: ftbfs with GCC-10
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.)


-- 
957016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:astronomical-almanac
Version: 5.6-6
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/astronomical-almanac_5.6-6_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
  |  ^
kfiles.c:92:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   92 |  fgets( s, 80, f );
  |  ^
kfiles.c:94:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   94 |  fgets( s, 80, f );
  |  ^
kfiles.c:134:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  134 |  fgets( s, 80, f );
  |  ^
kfiles.c:137:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  137 |  fgets( s, 80, f );
  |  ^
kfiles.c:140:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  140 |  fgets( s, 80, f );
  |  ^
kfiles.c:153:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  153 |  fgets( s, 80, f );
  |  ^
kfiles.c: In function ‘fincat’:
kfiles.c:341:2: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  341 |  fgets( str1, 126, f );
  |  ^
kfiles.c:346:3: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  346 |   fgets( str2, 126, f );
  |   ^
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o lightt.o lightt.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o lonlat.o lonlat.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o nutate.o nutate.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o precess.o precess.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o refrac.o refrac.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o rplanet.o rplanet.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o rstar.o rstar.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o sidrlt.o sidrlt.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o sun.o sun.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o domoon.o domoon.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o trnsit.o trnsit.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o vearth.o vearth.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o zatan2.o zatan2.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o gplan.o gplan.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mer404.o mer404.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o ven404.o ven404.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o ear404.o ear404.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mar404.o mar404.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o jup404.o jup404.c
gcc -O2 -Wall -Wdate-time -D_FORTIFY_SOURC

Processed: closing 966392

[Debian Bug Tracking System]

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

> close 966392
Bug #966392 [src:php-codecoverage] php-codecoverage: FTBFS 4 tests failed
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #975202 [src:pikepdf] pikepdf: FTBFS: RuntimeError: Prohibited to create 
memoryview without Py_buffer
Added tag(s) patch.

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

Bug#975202: add patch

[Matthias Klose]

Control: tags -1 + patch

patch at
https://launchpad.net/ubuntu/+source/pikepdf/1.17.3+dfsg-1ubuntu1

Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue

[Sven Mueller]

Looks like you are right:

libopencensus-java is used via libgoogle-http-client-java
In there,
/usr/share/maven-repo/io/opencensus/opencensus-api/0.23.0/opencensus-api-0.23.0.pom
has this:



io.grpc
grpc-context
debian
compile



So libopencensus-java depends on grpc-context in io.grpc (provided by
package libgrpc-java).
But it turns out that we rebuild against debian-testing as of early
November, which had version: 0.23.0+ds-1 - and that had no declared
dependency on libgrpc-java.
0.24.0-1 does have that dependency.

Sorry for the noise.


Am Fr., 11. Dez. 2020 um 10:41 Uhr schrieb Sven Mueller <
sven.muelle...@gmail.com>:

> Hi Tony.
>
> You might be right and I'll try to debug a little more.
> I'll share the build log with you directly. As it is from an internal
> build, I suspect I might have missed removing some internal names that I
> don't want to see published on bugs.debian.org.
>
> Cheers,
> Sven
>
> Am Do., 10. Dez. 2020 um 18:45 Uhr schrieb tony mancill <
> tmanc...@debian.org>:
>
>> On Thu, Dec 10, 2020 at 04:51:53PM +0100, Sven Mueller wrote:
>> > Hi.
>> >
>> > I just re-ran tests after adding a build dependency on libgrpc-java and
>> > that fixed the reported issue.
>>
>> Hi Sven,
>>
>> Would you mind sharing the build logs for the failed build?  It's fine
>> if you send them to me directly.
>>
>> I'm not able to reproduce the build failure locally in a clean sid
>> chroot, and the build failure doesn't occur on the buildds [1], so I
>> just want to make sure that we're addressing the right package and/or
>> root cause.
>>
>> It feels like it might be a transitive dependency issue, like the one
>> addressed in #975842 [2].
>>
>> Thanks,
>> tony
>>
>> [1]
>> https://buildd.debian.org/status/package.php?p=google-oauth-client-java
>> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975842
>>
>

Bug#977038: marked as done (google-oauth-client-java: FTBFS: Failed to execute goal on project google-oauth-client: Could not resolve dependencies for project com.google.api-client:google-api-client:j

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 11:17:55 +0100
with message-id 

and subject line Re: Bug#977038: Confirmed: build-dep on libgrpc-java fixes the 
issue
has caused the Debian Bug report #977038,
regarding google-oauth-client-java: FTBFS: Failed to execute goal on project 
google-oauth-client: Could not resolve dependencies for project 
com.google.api-client:google-api-client:jar:1.27.1: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
io.grpc:grpc-context:jar:debian has not been downloaded from it before.
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.)


-- 
977038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-oauth-client-java
Version: 1.28.0-1
Severity: serious

This can likely be fixed with a build dependency on grpc-java

[ERROR] Failed to execute goal on project google-oauth-client: Could not
resolve dependencies for project
com.google.oauth-client:google-oauth-client:jar:1.28.0: Cannot access
central (https://repo.maven.apache.org/maven2) in offline mode and the
artifact io.grpc:grpc-context:jar:debian has not been downloaded from it
before. -> [Help 1]
--- End Message ---
--- Begin Message ---
Looks like you are right:

libopencensus-java is used via libgoogle-http-client-java
In there,
/usr/share/maven-repo/io/opencensus/opencensus-api/0.23.0/opencensus-api-0.23.0.pom
has this:



io.grpc
grpc-context
debian
compile



So libopencensus-java depends on grpc-context in io.grpc (provided by
package libgrpc-java).
But it turns out that we rebuild against debian-testing as of early
November, which had version: 0.23.0+ds-1 - and that had no declared
dependency on libgrpc-java.
0.24.0-1 does have that dependency.

Sorry for the noise.


Am Fr., 11. Dez. 2020 um 10:41 Uhr schrieb Sven Mueller <
sven.muelle...@gmail.com>:

> Hi Tony.
>
> You might be right and I'll try to debug a little more.
> I'll share the build log with you directly. As it is from an internal
> build, I suspect I might have missed removing some internal names that I
> don't want to see published on bugs.debian.org.
>
> Cheers,
> Sven
>
> Am Do., 10. Dez. 2020 um 18:45 Uhr schrieb tony mancill <
> tmanc...@debian.org>:
>
>> On Thu, Dec 10, 2020 at 04:51:53PM +0100, Sven Mueller wrote:
>> > Hi.
>> >
>> > I just re-ran tests after adding a build dependency on libgrpc-java and
>> > that fixed the reported issue.
>>
>> Hi Sven,
>>
>> Would you mind sharing the build logs for the failed build?  It's fine
>> if you send them to me directly.
>>
>> I'm not able to reproduce the build failure locally in a clean sid
>> chroot, and the build failure doesn't occur on the buildds [1], so I
>> just want to make sure that we're addressing the right package and/or
>> root cause.
>>
>> It feels like it might be a transitive dependency issue, like the one
>> addressed in #975842 [2].
>>
>> Thanks,
>> tony
>>
>> [1]
>> https://buildd.debian.org/status/package.php?p=google-oauth-client-java
>> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975842
>>
>
--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> tags 976906 confirmed upstream patch
Bug #976906 [src:libpll] libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal 
error: parse_utree.h: No such file or directory
Added tag(s) confirmed, upstream, and patch.
>
End of message, stopping processing here.

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

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

[Frédéric Bonnard]

Here is a patch based on this :
https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html

Tested on a power machine (where the build failed) and it seems to work.

F.
Description: Fix parallel build
This happened here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906
Solution found here : 
https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html
Author: Frédéric Bonnard 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -8,6 +8,8 @@
 AM_YFLAGS = -d -p `${SED} -n 's/.*_\(.*\)/pll_\1_/p' <<<"$*"`
 AM_LFLAGS = -P `${SED} -n 's/.*_\(.*\)/pll_\1_/p' <<<"$*"` -o lex.yy.c
 
+BUILT_SOURCES = parse_rtree.h parse_utree.h
+
 libpll_la_SOURCES=\
 fasta.c \
 gamma.c \


signature.asc
Description: PGP signature

Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue

[Sven Mueller]

Hi Tony.

You might be right and I'll try to debug a little more.
I'll share the build log with you directly. As it is from an internal
build, I suspect I might have missed removing some internal names that I
don't want to see published on bugs.debian.org.

Cheers,
Sven

Am Do., 10. Dez. 2020 um 18:45 Uhr schrieb tony mancill :

> On Thu, Dec 10, 2020 at 04:51:53PM +0100, Sven Mueller wrote:
> > Hi.
> >
> > I just re-ran tests after adding a build dependency on libgrpc-java and
> > that fixed the reported issue.
>
> Hi Sven,
>
> Would you mind sharing the build logs for the failed build?  It's fine
> if you send them to me directly.
>
> I'm not able to reproduce the build failure locally in a clean sid
> chroot, and the build failure doesn't occur on the buildds [1], so I
> just want to make sure that we're addressing the right package and/or
> root cause.
>
> It feels like it might be a transitive dependency issue, like the one
> addressed in #975842 [2].
>
> Thanks,
> tony
>
> [1]
> https://buildd.debian.org/status/package.php?p=google-oauth-client-java
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975842
>

Bug#976934: fixed in notmuch 0.31.2-4

[Lucas Nussbaum]

Hi,

>  notmuch (0.31.2-4) unstable; urgency=medium
>  .
>* Move prerequisite to file targets from phony ones. Thanks to
>  Lucas Nussbaum for the report. (Closes: #976934).

I confirm that 0.31.2-4 builds fine under the same test conditions as
the original failure.

Lucas

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

[Lucas Nussbaum]

Here is a patch based on this :
https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html

Tested on a power machine (where the build failed) and it seems to work.

F.
Description: Fix parallel build
This happened here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906
Solution found here : 
https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html
Author: Frédéric Bonnard 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -8,6 +8,8 @@
 AM_YFLAGS = -d -p `${SED} -n 's/.*_\(.*\)/pll_\1_/p' <<<"$*"`
 AM_LFLAGS = -P `${SED} -n 's/.*_\(.*\)/pll_\1_/p' <<<"$*"` -o lex.yy.c
 
+BUILT_SOURCES = parse_rtree.h parse_utree.h
+
 libpll_la_SOURCES=\
 fasta.c \
 gamma.c \

Processed: Re: rails: please drop Build-Depends on qunit-selenium

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #976291 [src:rails] rails: please drop Build-Depends on qunit-selenium
Added tag(s) pending.

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

Bug#976291: rails: please drop Build-Depends on qunit-selenium

[Pirate Praveen]

Control: tags -1 pending

On Wed, 2 Dec 2020 22:11:27 +0100 Paul Gevers  wrote:
> I love tests. As one of the maintainers of the ci.debian.net
> infrastructure, I really do. However, with my Release Team member hat
> on, I'm asking you to stop Build-Depending on qunit-selenium which 
you

> need to run your build time tests.
>
> The reason I'm asking is that we want to remove chromium from 
bullseye
> because it's currently in a bad shape and qunit-selenium Depends on 
it,

> so has to go too.

This is now applied in the git repo. Utkarsh wanted to make some more 
changes before the upload.

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

[Lucas Nussbaum]

On 10/12/20 at 18:20 +0100, Andreas Tille wrote:
> Hi Mathieu,
> 
> On Thu, Dec 10, 2020 at 11:10:17AM +0100, Mathieu Malaterre wrote:
> > "make -j160"
> > 
> > that would be my guess :)
> 
> This sounds pretty likely, thought.  Thanks for the hint.

Hi,

I tried building with SMT off (so the machine only has 20 visible
cores), and the build succeeded. So yes, it's likely caused by
parallelism.

Lucas

Bug#973815: marked as done (knot: 'make distclean' deletes src/libknot/xdp/bpf-kernel-obj.c which is not regenerated)

[Debian Bug Tracking System]

Your message dated Fri, 11 Dec 2020 08:50:01 +
with message-id 
and subject line Bug#973815: fixed in knot 3.0.2-3
has caused the Debian Bug report #973815,
regarding knot: 'make distclean' deletes src/libknot/xdp/bpf-kernel-obj.c which 
is not regenerated
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.)


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

Hi,

knot/experimental FTBFS twice in a row. 'debian/rules clean' after the
first build removes 'src/libknot/xdp/bpf-kernel-obj.c' via 'make distclean',
but that file is not regenerated during the second build causing the
build to fail. I did not check whether the package in sid has the same problem.

[...]
 debian/rules clean
dh clean \
 --exclude=.la --exclude=example.com.zone \
 --with python3
   dh_auto_clean -O--exclude=.la -O--exclude=example.com.zone
make -j3 distclean
make[1]: Entering directory '/build/knot-3.0.1'
Making distclean in src
make[2]: Entering directory '/build/knot-3.0.1/src'
Making distclean in libknot/xdp
make[3]: Entering directory '/build/knot-3.0.1/src/libknot/xdp'
test -z "bpf-kernel.ll bpf-kernel.o bpf-kernel-obj.c" || rm -f bpf-kernel.ll 
bpf-kernel.o bpf-kernel-obj.c
[...]
dpkg-source: warning: ignoring deletion of file 
src/libknot/xdp/bpf-kernel-obj.c, use --include-removal to override
[...]
   dh_auto_build -O--exclude=.la -O--exclude=example.com.zone -Nknot-doc 
-Npython3-libknot
make -j3
[...]
make[4]: *** No rule to make target 'libknot/xdp/bpf-kernel-obj.c', needed by 
'libknot/xdp/la-bpf-kernel-obj.lo'.  Stop.
[...]


Andreas


knot_3.0.1-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: knot
Source-Version: 3.0.2-3
Done: =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?= 

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

Debian distribution maintenance software
pp.
Santiago Ruano Rincón  (supplier of updated knot 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, 10 Dec 2020 21:59:10 +0100
Source: knot
Architecture: source
Version: 3.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: knot packagers 
Changed-By: Santiago Ruano Rincón 
Closes: 973815
Changes:
 knot (3.0.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Disable xdp on armel. Create d/libknot11.symbols.armel accordingly.
   * Disable fastparser on sh4.
   * Add 
d/patches/0001-xdp-rework-Makefile.am-to-avoid-make-distcheck-issue.patch
 (Closes: #973815)
   * Remove build-deps not available on hurd and kfreebsds: libbpf-dev,
 libelf-dev linux-libc-dev. Create symbols files accordingly.
Checksums-Sha1:
 3c7cd44cecdb5252c65789ecfa99536546925022 2871 knot_3.0.2-3.dsc
 377536f3415dbd0f5bc12e2f8b12ec48f2f6c173 33028 knot_3.0.2-3.debian.tar.xz
 f34fa9b3dcab3b6992d56879adfa035280092023 12294 knot_3.0.2-3_amd64.buildinfo
Checksums-Sha256:
 6dd2c3039edad58aa4ccd3aea08eec470672a4d6b08a705241238730550a71b6 2871 
knot_3.0.2-3.dsc
 39e5f12784f78bbefab55006e5dea5e9f7db649dc221c78a862d7e06d9069add 33028 
knot_3.0.2-3.debian.tar.xz
 a9d017a7896dbe38fbd750c691064ba5d39f3898b95870363ffb0a236b4d8e6f 12294 
knot_3.0.2-3_amd64.buildinfo
Files:
 bf75862246147e2438dd62d2961e4009 2871 net optional knot_3.0.2-3.dsc
 6eb71a964aa45465fa37e52ce97f0225 33028 net optional knot_3.0.2-3.debian.tar.xz
 0fa6d0627e42b6fd80f0bed4029e17ac 12294 net optional 
knot_3.0.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYIADIWIQRZVjztY8b+Ty43oH1itBCJKh26HQUCX9MtHhQcc2FudGlhZ29A
ZGViaWFuLm9yZwAKCRBitBCJKh26HcyVAQCtAamYRUspAUjGPYmiL3r8u9dNajTS
R1PiVOWCE8aWNAEAmBEpN1hFXA7htPMeOSwsSuzipb+V/83sBtAyhfO0nQU=
=2e5Z
-END PGP SIGNATURE End Message ---

Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0

[Andrei POPESCU]

Control: reassign -1 ruby-gollum-rugged-adapter 0.4.4.2-2

On Jo, 10 dec 20, 22:57:26, peter green wrote:
> package: ruby-gollum-rugged-apapter
> Version: 0.4.4.2-2
> Severity: serious
> 
> The autopkgtest for ruby-gollum-rugged-adapter is failing with ruby-rugged 
> 1.1.0.
> 
> > ┌──┐
> > │ Checking Rubygems dependency resolution on ruby2.7
> >│
> > └──┘
> > 
> > GEM_PATH= ruby2.7 -e gem\ \"gitlab-gollum-rugged_adapter\"
> > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in 
> > block in activate_dependencies': Could not find 'rugged' (~> 0.25) among 60 
> > total gem(s) (Gem::MissingSpecError)
> > Checked in 
> > 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/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'
> >  at: 
> > /usr/share/rubygems-integration/all/specifications/gitlab-gollum-rugged_adapter-0.4.4.2.gemspec,
> >  execute `gem env` for more information
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block 
> > in activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
> > `activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
> > `activate'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `block in gem'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `synchronize'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `gem'
> > from -e:1:in `'
> > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could 
> > not find 'rugged' (~> 0.25) - did find: [rugged-1.1.0] 
> > (Gem::MissingSpecVersionError)
> > Checked in 
> > 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/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'
> >  , execute `gem env` for more information
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block 
> > in activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
> > `activate_dependencies'
> > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
> > `activate'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `block in gem'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `synchronize'
> > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> > `gem'
> > from -e:1:in `'
> 
> This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 
> transition) from migrating to
> testing.

Fixing typo in package name.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Processed: Re: Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ruby-gollum-rugged-adapter 0.4.4.2-2
Bug #977108 [ruby-gollum-rugged-apapter] ruby-gollum-rugged-adapter, 
autopkgtest failure with ruby-rugged 1.1.0
Warning: Unknown package 'ruby-gollum-rugged-apapter'
Bug reassigned from package 'ruby-gollum-rugged-apapter' to 
'ruby-gollum-rugged-adapter'.
No longer marked as found in versions 0.4.4.2-2.
Ignoring request to alter fixed versions of bug #977108 to the same values 
previously set
Bug #977108 [ruby-gollum-rugged-adapter] ruby-gollum-rugged-adapter, 
autopkgtest failure with ruby-rugged 1.1.0
Marked as found in versions ruby-gollum-rugged-adapter/0.4.4.2-2.

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

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

On 10/12/20 at 22:12 +0100, Michael Biebl wrote:
> Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz:
> > Hi Michael!
> > 
> > On 12/10/20 8:42 PM, Michael Biebl wrote:
> > > 
> > > Testsuite summary for systemd-bootchart 233
> > > 
> > > # TOTAL: 1
> > > # PASS:  1
> > > # SKIP:  0
> > > # XFAIL: 0
> > > # FAIL:  0
> > > # XPASS: 0
> > > # ERROR: 0
> > > 
> > 
> > Did the test machine you used actually have that many cores?
> 
> No idea

I tried building with SMT off (so the machine only has 20 visible
cores). I could reproduce the failure. (I disabled SMT at runtime using
ppc64_cpu --smt=off)

It also fails when running 'make check VERBOSE=1' (so it's not caused by
parallelism).

It crashes with:
(gdb) r -o /tmp/tmp.k64Np1I2cr -n 10 -r -p
Starting program: /root/systemd-bootchart-233/systemd-bootchart -o 
/tmp/tmp.k64Np1I2cr -n 10 -r -p
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00014d04 in svg_ps_bars (interval=, 
graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1, 
n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187
1187i = ps->sample->next->sampledata->counter;
(gdb) bt
#0  0x00014d04 in svg_ps_bars (interval=, 
graph_start=2775.3698308829998, ps_first=0x1000505d0, 
n_cpus=1, n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187
#1  svg_do (overrun=0, interval=, log_start=2775.3698308829998, 
graph_start=2775.3698308829998, n_cpus=1, 
pscount=11940, n_samples=, ps_first=, 
head=0x100050770, 
build=0x1000509e0 "Debian GNU/Linux bullseye/sid", of=0x1000503f0) at 
src/svg.c:1371
#2  main (argc=, argv=) at src/bootchart.c:497

The segfault can be reproduced on Debian stable outside the chroot, just
running '/lib/systemd/systemd-bootchart -n 1'.

At the same time, 'systemd-analyze plot' works fine (I'm attaching its
output in case it hints at something).

Lucas

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

On 11/12/20 at 09:09 +0100, Lucas Nussbaum wrote:
> On 10/12/20 at 22:12 +0100, Michael Biebl wrote:
> > Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz:
> > > Hi Michael!
> > > 
> > > On 12/10/20 8:42 PM, Michael Biebl wrote:
> > > > 
> > > > Testsuite summary for systemd-bootchart 233
> > > > 
> > > > # TOTAL: 1
> > > > # PASS:  1
> > > > # SKIP:  0
> > > > # XFAIL: 0
> > > > # FAIL:  0
> > > > # XPASS: 0
> > > > # ERROR: 0
> > > > 
> > > 
> > > Did the test machine you used actually have that many cores?
> > 
> > No idea
> 
> I tried building with SMT off (so the machine only has 20 visible
> cores). I could reproduce the failure. (I disabled SMT at runtime using
> ppc64_cpu --smt=off)
> 
> It also fails when running 'make check VERBOSE=1' (so it's not caused by
> parallelism).
> 
> It crashes with:
> (gdb) r -o /tmp/tmp.k64Np1I2cr -n 10 -r -p
> Starting program: /root/systemd-bootchart-233/systemd-bootchart -o 
> /tmp/tmp.k64Np1I2cr -n 10 -r -p
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
> "/lib/powerpc64le-linux-gnu/libthread_db.so.1".
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00014d04 in svg_ps_bars (interval=, 
> graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1, 
> n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187
> 1187  i = ps->sample->next->sampledata->counter;
> (gdb) bt
> #0  0x00014d04 in svg_ps_bars (interval=, 
> graph_start=2775.3698308829998, ps_first=0x1000505d0, 
> n_cpus=1, n_samples=10, head=0x100050770, of=0x1000503f0) at 
> src/svg.c:1187
> #1  svg_do (overrun=0, interval=, 
> log_start=2775.3698308829998, graph_start=2775.3698308829998, n_cpus=1, 
> pscount=11940, n_samples=, ps_first=, 
> head=0x100050770, 
> build=0x1000509e0 "Debian GNU/Linux bullseye/sid", of=0x1000503f0) at 
> src/svg.c:1371
> #2  main (argc=, argv=) at src/bootchart.c:497
> 
> The segfault can be reproduced on Debian stable outside the chroot, just
> running '/lib/systemd/systemd-bootchart -n 1'.
> 
> At the same time, 'systemd-analyze plot' works fine (I'm attaching its
> output in case it hints at something).

I tried to reproduce this on another system (ARM64, 256 visible cores
because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also
segfaults.

I tried to reproduce on yet another system (x86_64, 128 visible cores
because 4x Intel Xeon Gold 6130, 16 cores/cpu, 2 threads/core), and it
also segfaults.

My guess would be that the test suite depends on the system it is
running on (it just generates the output for the local system), and
there's something it doesn't like about large numbers of cores, but
there's nothing specific to ppc64el here.

Lucas