Bug#945718: Python 3 Version

[Soren Stoutner]

Does anyone know if there is a Python 3 version planned, or is this the end of 
life for ownCloud Dolphin integration?

-- 
Soren Stoutner
623-262-6169
so...@stoutner.com

Bug#922396: [Pkg-mozext-maintainers] Bug#922396: Updated package / patch and status information

[Ximin Luo]

I was the last person to upload noscript in 2018.

The reason why I haven't updated it since 2018 is because I've moved onto using 
umatrix personally and also maintaining it in debian.

umatrix gives you more fine-grained permissions including cookies, XHR, etc, so 
you don't need to install a 2nd extension to manage your cookies. It's written 
by the same author as ublock-origin.

>From what I remember noscript maintenance in terms of Debian packaging was 
>also a pain. umatrix maintenance is pretty simple.

I encourage everyone to move to umatrix and drop noscript.

Best,
Ximin

Helge Kreutzmann:
> tags 922396 + patch
> thanks
> 
> Hello,
> this is a central package, so I had a look at it. Unfortunately,
> README.source is outdated, the following recipe works:
> 
>  * apt-get source
>  * cd mozilla-noscript-10.1.9.6
>  * uscan
>  * create appropriate directory, cd into it and tar xJvf 
> ../mozilla-noscript_….orig.tar.xz
>  * copy over debian directory from 10.1.9.6
>  * export QUILT_PATCHES=debian/patches
>  * quilt new 0002b-remove-websites-from-default-white-list.patch
>  * quilt edit common/Policy.js
>  * quilt refresh
>  * comment out 0002 (original) patch in debian/patches/series
>  * dch -i und Changelog-Eintrag vorgenommen (Note: version number)
>  * debuild
> 
> for version 11.0.34 the (new/updated) patch is as follows:
> Author: Ximin Luo , Helge Kreutzmann 
> 
> Description: remove websites from default white list
>  Original patch by
>  From: arno 
>  Date: Tue, 25 Aug 2009 23:32:30 +0200
>  Subject: remove websites from default white list
> 
> Index: mozilla-noscript-11.0.34/common/Policy.js
> ===
> --- mozilla-noscript-11.0.34.orig/common/Policy.js
> +++ mozilla-noscript-11.0.34/common/Policy.js
> @@ -294,21 +294,7 @@ var {Permissions, Policy, Sites} = (() =
>function defaultOptions() {
>  return {
>sites:{
> -trusted: `addons.mozilla.org
> -  afx.ms ajax.aspnetcdn.com
> -  ajax.googleapis.com bootstrapcdn.com
> -  code.jquery.com firstdata.com firstdata.lv gfx.ms
> -  google.com googlevideo.com gstatic.com
> -  hotmail.com live.com live.net
> -  maps.googleapis.com mozilla.net
> -  netflix.com nflxext.com nflximg.com nflxvideo.net
> -  noscript.net
> -  outlook.com passport.com passport.net passportimages.com
> -  paypal.com paypalobjects.com
> -  securecode.com securesuite.net sfx.ms tinymce.cachefly.net
> -  wlxrs.com
> -  yahoo.com yahooapis.com
> -  yimg.com youtube.com 
> ytimg.com`.split(/\s+/).map(Sites.secureDomainKey),
> +trusted: ``.split(/\s+/).map(Sites.secureDomainKey),
>  untrusted: [],
>  custom: {},
>},
> 
> Now I have to check if this updated version works …
> 
> Btw., version 10.1.9.6. still seems to work in firefox 68.10.0esr-1.
> 
> Greetings
> 
>   Helge
> 
> P.S. If someone takes over mozilla-noscript, README.source should be 
>  updated as well
> 
> 
> ___
> Pkg-mozext-maintainers mailing list
> pkg-mozext-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mozext-maintainers
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#967224: closing 967224

[Ximin Luo]

close 967224 3.5.20-1
thanks

In fact I'm not sure why this bug was even filed, there is no python dependency.

Unless you mean transitively through mozilla-devscripts, which you fixed a 
short while ago. But then the bug report should only have been on that package, 
since it takes a single fix to fix it.

Bug#967230: closing 967230

[Ximin Luo]

close 967230 1.4.0+dfsg-1
thanks

In fact I'm not sure why this bug was even filed, there is no python dependency.

Unless you mean transitively through mozilla-devscripts, which you fixed a 
short while ago. But then the bug report should only have been on that package, 
since it takes a single fix to fix it.

Processed: closing 967230

[Debian Bug Tracking System]

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

> close 967230 1.4.0+dfsg-1
Bug #967230 [src:umatrix] umatrix: Unversioned Python removal in sid/bullseye
Marked as fixed in versions umatrix/1.4.0+dfsg-1.
Bug #967230 [src:umatrix] umatrix: Unversioned Python removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 967224

[Debian Bug Tracking System]

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

> close 967224
Bug #967224 [src:tree-style-tab] tree-style-tab: Unversioned Python removal in 
sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 967224

[Debian Bug Tracking System]

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

> close 967224 3.5.20-1
Bug #967224 {Done: Ximin Luo } [src:tree-style-tab] 
tree-style-tab: Unversioned Python removal in sid/bullseye
The source 'tree-style-tab' and version '3.5.20-1' do not appear to match any 
binary packages
Marked as fixed in versions tree-style-tab/3.5.20-1.
Bug #967224 {Done: Ximin Luo } [src:tree-style-tab] 
tree-style-tab: Unversioned Python removal in sid/bullseye
Bug 967224 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: Reopen #966903

[Debian Bug Tracking System]

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

> reopen 966903
Bug #966903 {Done: Kari Pahula } [src:gecode] gecode: FTBFS: 
gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such 
file or directory
'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 gecode/6.2.0-4.
> thanks
Stopping processing here.

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

Bug#966472: marked as done (bcbio: B-D biobambam2 not available in testing)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 22:18:30 +
with message-id 
and subject line Bug#966472: fixed in biobambam2 2.0.173+ds-1
has caused the Debian Bug report #966472,
regarding bcbio: B-D biobambam2 not available in testing
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.)


-- 
966472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bcbio
Version: 1.2.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: block -1 with 966470

bcbio cannot be rebuilt in testing because the build-dependency biobambam2
is not in testing.


Andreas
--- End Message ---
--- Begin Message ---
Source: biobambam2
Source-Version: 2.0.173+ds-1
Done: =?utf-8?q?=C3=89tienne_Mollier?= 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated biobambam2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Aug 2020 18:51:02 +0200
Source: biobambam2
Architecture: source
Version: 2.0.173+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 966470 966472
Changes:
 biobambam2 (2.0.173+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   * d/control: added zlib1g-dev to dependencies of biobambam2.
 Closes: #966470, #966472
   * d/upstream/metadata: filled Repository and Repository-Browse per lintian
 informational message  upstream-metadata-missing-repository.
Checksums-Sha1:
 25e173439e690e275e92e94db5b9f990773d9baf 2075 biobambam2_2.0.173+ds-1.dsc
 c91d092a4789aff875c73d2d59a6207c3237077e 244700 
biobambam2_2.0.173+ds.orig.tar.xz
 fac39885912b9c090f07d46503cc2cd3e1fb648a 1031832 
biobambam2_2.0.173+ds-1.debian.tar.xz
 de24430a5cd98872e7db4b9e41d241f1e02126d7 5764 
biobambam2_2.0.173+ds-1_amd64.buildinfo
Checksums-Sha256:
 c4cceb89d49017f636b03c7b2bf1518aa68d36c2858a6896f4feb096e8bd0f59 2075 
biobambam2_2.0.173+ds-1.dsc
 596eb71f4384177033949107f85c0c69ffc659347583d3b1611b15aea49d5a96 244700 
biobambam2_2.0.173+ds.orig.tar.xz
 7a2718088eab790f6b206bffb56cd97af52e82cb100e1ef4715930026f649599 1031832 
biobambam2_2.0.173+ds-1.debian.tar.xz
 c6f5d1e49e1a226c3b8b2c9d49f073319e6358d1b2e1660561eec2912b14abc1 5764 
biobambam2_2.0.173+ds-1_amd64.buildinfo
Files:
 5a9f2120d4ccc5e249bf1372ab3b5bf6 2075 science optional 
biobambam2_2.0.173+ds-1.dsc
 7f9f274cf2329eb8eb2efcd1a4054fc2 244700 science optional 
biobambam2_2.0.173+ds.orig.tar.xz
 3ef7bb2f2a8e6b6f2a45b9b1f2296e5d 1031832 science optional 
biobambam2_2.0.173+ds-1.debian.tar.xz
 8fe4a4f9c51ea46743043943682df25c 5764 science optional 
biobambam2_2.0.173+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8vIRgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEVpQ//SBY6SfmwSsIMFNIF9NvBOIcA+fbmBqta
T+rajNuut1+TqZ1OMjGFXl//+DnW04tW73J6nzF2NU0HUNYNRyUMjoTrx295+4sT
XqEGLVNlNCB4FyPzEKzOVidxjMO4Lnzqu+F27YzD44d1pBJrszmTaVUg9B7WuILY
nyceYPhXgJGqe8Mdohr3vrRyyvRPbSmTZW3PB/DMT8xaASldfopUpSWK6BuKRni0
yjWGsOOqVjigWXJAcrbDnif+pF0h31f91tOduHQeXkS+R7KVwj2j4wD9yr540gRM
5sZP0a39EFl6ib7vBS6lV5fyaHMLQ+rdlJ4udk68Y55bMWeX9tNq+VgcJBqVK7DP
aporo4oBRHhhIaIyniA/+kAy8Ch2qZGE23G6oOjDLKQLmmNqVu42TYu/UPmUFEK2
RtlUhwy7bYjfohYTIztFHzG9zv60BJfY8rtbB49kefDoud2vi/TrEjEE7GMWeLi4
QeSwHGHhzItL2Oq9FXgB/TdmOG2CdBgiYr0iUvCB/CvxZx68ufl2U8bTsmna+e2+
SqWu7B6HNcnqTJoQCJ8ovIxOJMUUQEanvv+OrU032ZVPV+M/Kk5H52VSCYenXo4b
OSBnw5/xaM0hOnh9YBKYK0xR7WiLOc/Dw6729Q2xxRbCnx0AG+A55MA6YhnAsB74
LKK9bbUOoUI=
=fEJu
-END PGP SIGNATURE End Message ---

Bug#957841: marked as done (squidguard: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 22:19:11 +
with message-id 
and subject line Bug#957841: fixed in squidguard 1.6.0-1.1
has caused the Debian Bug report #957841,
regarding squidguard: 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.)


-- 
957841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:squidguard
Version: 1.6.0-1
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/squidguard_1.6.0-1_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

[...]
sg.y:108.16-21: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  108 | %type  NUMBER
  |^~
sg.y:109.14-17: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  109 | %type  TVAL
  |  ^~~~
sg.y:110.16-19: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  110 | %type  DVAL
  |^~~~
sg.y:111.16-23: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  111 | %type  DVALCRON
  |^~~~
sg.y:112.16-19: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  112 | %type  CHAR
  |^~~~
sg.y:113.16-20: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  113 | %type  SUBST 
  |^
sg.y:114.16-21: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  114 | %type  IPADDR
  |^~
sg.y:115.16-21: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  115 | %type  DBHOME LOGDIR
  |^~
sg.y:115.23-28: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  115 | %type  DBHOME LOGDIR
  |   ^~
sg.y:116.16-19: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  116 | %type  CIDR
  |^~~~
sg.y:117.16-22: warning: POSIX yacc reserves %type to nonterminals [-Wyacc]
  117 | %type  IPCLASS
  |^~~
gcc -I.. -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include 
-DHAVE_CONFIG_H -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DLDAP_DEPRECATED 
-I/usr/include -I/usr/include -c y.tab.c
In file included from /usr/include/string.h:495,
 from sg.h:27,
 from sg.y:21:
In function ‘strncpy’,
inlined from ‘is_blacklisted’ at sg.y:2589:4:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin___strncpy_chk’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
sg.y: In function ‘is_blacklisted’:
sg.y:2581:7: note: length computed here
 2581 |   if (strlen(domain)+strlen(suffix)+1>MAX_BUF)
  |   ^~
gcc -I.. -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include 
-DHAVE_CONFIG_H -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DLDAP_DEPRECATED 
-I/usr/include -I/usr/include -c lex.yy.c
gcc -Wl,-z,relro -Wl,-z,now -L/usr/lib -L/usr/lib -o squidGuard main.o sgLog.o 
sgDb.o HTParse.o sgDiv.o sgFree.o y.tab.o lex.yy.o -lpthread  -lldap -L/usr/lib 
-ldb
/usr/bin/ld: sgLog.o:./src/sg.h:340: multiple definition of `lineno'; 
main.o:./src/sg.h:340: first defined here
/usr/bin/ld: 

Bug#966470: marked as done (biobambam2: autopkgtest failures: Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 22:18:30 +
with message-id 
and subject line Bug#966470: fixed in biobambam2 2.0.173+ds-1
has caused the Debian Bug report #966470,
regarding biobambam2: autopkgtest failures: Segmentation fault bamsormadup < 
SRR11728627.bam > SRR11728627.sorted.bam
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.)


-- 
966470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: biobambam2
Version: 2.0.164+ds-1
Severity: serious

Hi,

biobambam2 fails its autopkg tests:

https://ci.debian.net/packages/b/biobambam2/testing/amd64/

autopkgtest [17:40:54]: test run-unit-test: [---
[93m[1mTest 1[0m
/tmp/autopkgtest-lxc.hkbkydv5/downtmp/build.3IE/src/debian/tests/run-unit-test: 
line 20:   794 Segmentation fault  bamsormadup < SRR11728627.bam > 
SRR11728627.sorted.bam
autopkgtest [17:40:55]: test run-unit-test: ---]
autopkgtest [17:40:55]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
run-unit-testFAIL non-zero exit status 139

Andreas
--- End Message ---
--- Begin Message ---
Source: biobambam2
Source-Version: 2.0.173+ds-1
Done: =?utf-8?q?=C3=89tienne_Mollier?= 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated biobambam2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Aug 2020 18:51:02 +0200
Source: biobambam2
Architecture: source
Version: 2.0.173+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 966470 966472
Changes:
 biobambam2 (2.0.173+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   * d/control: added zlib1g-dev to dependencies of biobambam2.
 Closes: #966470, #966472
   * d/upstream/metadata: filled Repository and Repository-Browse per lintian
 informational message  upstream-metadata-missing-repository.
Checksums-Sha1:
 25e173439e690e275e92e94db5b9f990773d9baf 2075 biobambam2_2.0.173+ds-1.dsc
 c91d092a4789aff875c73d2d59a6207c3237077e 244700 
biobambam2_2.0.173+ds.orig.tar.xz
 fac39885912b9c090f07d46503cc2cd3e1fb648a 1031832 
biobambam2_2.0.173+ds-1.debian.tar.xz
 de24430a5cd98872e7db4b9e41d241f1e02126d7 5764 
biobambam2_2.0.173+ds-1_amd64.buildinfo
Checksums-Sha256:
 c4cceb89d49017f636b03c7b2bf1518aa68d36c2858a6896f4feb096e8bd0f59 2075 
biobambam2_2.0.173+ds-1.dsc
 596eb71f4384177033949107f85c0c69ffc659347583d3b1611b15aea49d5a96 244700 
biobambam2_2.0.173+ds.orig.tar.xz
 7a2718088eab790f6b206bffb56cd97af52e82cb100e1ef4715930026f649599 1031832 
biobambam2_2.0.173+ds-1.debian.tar.xz
 c6f5d1e49e1a226c3b8b2c9d49f073319e6358d1b2e1660561eec2912b14abc1 5764 
biobambam2_2.0.173+ds-1_amd64.buildinfo
Files:
 5a9f2120d4ccc5e249bf1372ab3b5bf6 2075 science optional 
biobambam2_2.0.173+ds-1.dsc
 7f9f274cf2329eb8eb2efcd1a4054fc2 244700 science optional 
biobambam2_2.0.173+ds.orig.tar.xz
 3ef7bb2f2a8e6b6f2a45b9b1f2296e5d 1031832 science optional 
biobambam2_2.0.173+ds-1.debian.tar.xz
 8fe4a4f9c51ea46743043943682df25c 5764 science optional 
biobambam2_2.0.173+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8vIRgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEVpQ//SBY6SfmwSsIMFNIF9NvBOIcA+fbmBqta
T+rajNuut1+TqZ1OMjGFXl//+DnW04tW73J6nzF2NU0HUNYNRyUMjoTrx295+4sT
XqEGLVNlNCB4FyPzEKzOVidxjMO4Lnzqu+F27YzD44d1pBJrszmTaVUg9B7WuILY
nyceYPhXgJGqe8Mdohr3vrRyyvRPbSmTZW3PB/DMT8xaASldfopUpSWK6BuKRni0
yjWGsOOqVjigWXJAcrbDnif+pF0h31f91tOduHQeXkS+R7KVwj2j4wD9yr540gRM
5sZP0a39EFl6ib7vBS6lV5fyaHMLQ+rdlJ4udk68Y55bMWeX9tNq+VgcJBqVK7DP
aporo4oBRHhhIaIyniA/+kAy8Ch2qZGE23G6oOjDLKQLmmNqVu42TYu/UPmUFEK2
RtlUhwy7bYjfohYTIztFHzG9zv60BJfY8rtbB49kefDoud2vi/TrEjEE7GMWeLi4
QeSwHGHhzItL2Oq9FXgB/TdmOG2CdBgiYr0iUvCB/CvxZx68ufl2U8bTsmna+e2+
SqWu7B6HNcnqTJoQCJ8ovIxOJMUUQEanvv+OrU032ZVPV+M/Kk5H52VSCYenXo4b

Bug#968106: phosh: Shell doesn't start

[Michel Le Bihan]

Package: phosh
Version: 0.4.3-1
Severity: grave
Justification: renders package unusable

Hello,

On a freshly created Debian sid live system:
```
sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video-
all,phosh --arch amd64 sid debian-live-root http://ftp.pl.debian.org/debian/
sudo chroot debian-live-root passwd
sudo chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1
123456) user
sudo chroot debian-live-root systemctl enable phosh
cp debian-live-root/vmlinuz .; cp debian-live-root/initrd.img .
sudo mksquashfs debian-live-root root.squashfs -comp lz4
python3 -m http.server -b localhost 8080
qemu-system-x86_64 -machine accel=kvm -m 4G -device virtio-net-pci,netdev=net0
-serial stdio -monitor vc -netdev
user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian-
live -kernel ./vmlinuz -initrd ./initrd.img -append "console=ttyS0
ip=frommedia boot=live nopersistence
fetch=http://10.0.2.252:8080/root.squashfs;
```
(last command is to start the test VM)

Phosh doesn't start. On the console I see:
```
traps: phoc[362] trap int3 ip:7f684a6d9585 sp:7ffccc2cfe90 error:0 in
libglib-2.0.so.0.6400.4[7f684a69f000+81000]
```

When attempting to start it manually:
```
user@debian:~$ phoc

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.384:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.393: [backend/session/direct-
ipc.c:30] Do not have root privileges; cannot become DRM master

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.396:
[backend/session/session.c:96] Failed to load session backend

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.405: [backend/backend.c:286]
Failed to start a DRM session

(phoc:468): phoc-server-ERROR **: 18:03:33.407: Could not create backend
[   76.891092] traps: phoc[468] trap int3 ip:7feeea992585 sp:7ffe555d1130
error:0 in libglib-2.0.so.0.6400.4[7feeea958000+81000]
Trace/breakpoint trap
```

```
user@debian:~$ phoc -E '/usr/bin/phosh -U' -C /usr/share/phosh/phoc.ini

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.976:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.978: [backend/session/direct-
ipc.c:30] Do not have root privileges; cannot become DRM master

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.981:
[backend/session/session.c:96] Failed to load session backend

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.983: [backend/backend.c:286]
Failed to start a DRM session

(phoc:517): phoc-server-ERROR **: 18:04:01.986: Could not create backend
```

Starting phosh as root doesn't help:
```
root@debian:~# phosh
/usr/bin/phosh: 12: gnome-session: not found

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.488:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.490:
[backend/session/direct.c:176] Could not get current tty number: Inappropriate
ioctl for device

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.494:
[backend/session/session.c:96] Failed to load session backend

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.496: [backend/backend.c:195]
failed to start a session

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.498: [backend/backend.c:235]
failed to start backend 'drm'

(phoc:558): phoc-server-ERROR **: 18:06:37.500: Could not create backend
```

root@debian:~# phoc -E '/usr/bin/phosh -U' -C /usr/share/phosh/phoc.ini

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.418:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.421:
[backend/session/direct.c:176] Could not get current tty number: Inappropriate
ioctl for device

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.425:
[backend/session/session.c:96] Failed to load session backend

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.428: [backend/backend.c:286]
Failed to start a DRM session

(phoc:611): phoc-server-ERROR **: 18:07:10.431: Could not create backend
```

It's also possible that I missed an important step, but I couldn't find
anything related in the doc.

Michel Le Bihan



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

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

Versions of packages phosh depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  fonts-lato   2.0-2
ii  gsettings-desktop-schemas3.36.1-1
ii  libc62.31-2
ii  libcairo21.16.0-4
pn  libfeedback-0.0-0  

Bug#957188: marked as done (exiv2: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 22:05:43 +
with message-id 
and subject line Bug#957188: fixed in exiv2 0.27.3-1
has caused the Debian Bug report #957188,
regarding exiv2: 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.)


-- 
957188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:exiv2
Version: 0.27.2-8
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/exiv2_0.27.2-8_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

[...]
+#MISSING: 0.27.2-8# 
(optional=templinst)_ZNSt6vectorISt4pairIPKhjESaIS3_EEaSERKS5_@Base 0.25
  
(optional=templinst)_ZNSt6vectorISt4pairIiiESaIS1_EE17_M_realloc_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.27.2
  
(optional=templinst)_ZNSt6vectorISt4pairIjjESaIS1_EE17_M_realloc_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.27.2
  (optional=templinst|arch=amd64 arm64 ia64 mips64el ppc64 ppc64el riscv64 
s390x 
sparc64)_ZNSt6vectorISt4pairImmESaIS1_EE17_M_realloc_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.27.2
@@ -1326,44 +1326,44 @@
  
(optional=templinst)_ZNSt6vectorIsSaIsEE17_M_realloc_insertEN9__gnu_cxx17__normal_iteratorIPsS1_EERKs@Base
 0.27.2
  
(optional=templinst)_ZNSt6vectorItSaItEE17_M_realloc_insertEN9__gnu_cxx17__normal_iteratorIPtS1_EERKt@Base
 0.27.2
  
(optional=templinst)_ZNSt7__cxx1110_List_baseIN5Exiv29ExifdatumESaIS2_EE8_M_clearEv@Base
 0.25
- 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIN9__gnu_cxx17__normal_iteratorIPKcS4_vT_SB_St20forward_iterator_tag@Base
 0.27.2
+#MISSING: 0.27.2-8# 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIN9__gnu_cxx17__normal_iteratorIPKcS4_vT_SB_St20forward_iterator_tag@Base
 0.27.2
  
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 0.27.2
- 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 0.27.2
- 
(optional=templinst)_ZNSt7__cxx114listIN5Exiv29ExifdatumESaIS2_EE18_M_assign_dispatchISt20_List_const_iteratorIS2_EEEvT_S8_St12__false_type@Base
 0.27.2
+#MISSING: 0.27.2-8# 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 0.27.2
+#MISSING: 0.27.2-8# 
(optional=templinst)_ZNSt7__cxx114listIN5Exiv29ExifdatumESaIS2_EE18_M_assign_dispatchISt20_List_const_iteratorIS2_EEEvT_S8_St12__false_type@Base
 0.27.2
  
(optional=templinst)_ZNSt7__cxx114listIN5Exiv29ExifdatumESaIS2_EE4sortIPFbRKNS1_9MetadatumES8_EEEvT_@Base
 0.25
  
(optional=templinst)_ZNSt7__cxx114listIN5Exiv29ExifdatumESaIS2_EE5mergeIPFbRKNS1_9MetadatumES8_EEEvRS4_T_@Base
 0.25
- 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueERKS5_@Base
 0.27.2
- 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 0.27.2
+#MISSING: 0.27.2-8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueERKS5_@Base
 0.27.2
+#MISSING: 0.27.2-8# 

Bug#961856: marked as pending in kodi

[Balint Reczey]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/kodi/-/commit/a94664834dfbda1b01912a248b24a36d70571ad2


Don't enable SSE in i386 builds

Closes: #961856


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/961856

Processed: Bug#961856 marked as pending in kodi

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#967205: No python package

[Marcos Fouces]

Hi!

I think that rfdump package is not related with Python. I think there
is a mistake.

Greetings, 
Marcos

Bug#966781: marked as done (python-pam: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:52:56 +
with message-id 
and subject line Bug#966781: fixed in python-pam 0.4.2-13.3
has caused the Debian Bug report #966781,
regarding python-pam: Unversioned Python 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.)


-- 
966781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pam
Version: 0.4.2-13.2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: python-pam
Source-Version: 0.4.2-13.3
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python-pam 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, 08 Aug 2020 22:11:37 +0200
Source: python-pam
Architecture: source
Version: 0.4.2-13.3
Distribution: unstable
Urgency: medium
Maintainer: Dima Barsky 
Changed-By: Matthias Klose 
Closes: 67203 966781
Changes:
 python-pam (0.4.2-13.3) unstable; urgency=medium
 .
   * No-change rebuild to generate dependencies on python2.
 Closes: #966781, #67203.
   * Bump standards and debhelper versions.
Checksums-Sha1:
 8f9bad5dcc04fc9e6fc38c47704611a9158a6751 1740 python-pam_0.4.2-13.3.dsc
 a61bc7d472b8648f7d1203640328fca7106d798d 2152 python-pam_0.4.2-13.3.diff.gz
 8725bcc7b7c2a68c04c53c2c62ad6c2db10cf6f2 6872 
python-pam_0.4.2-13.3_source.buildinfo
Checksums-Sha256:
 7698991055365c3e09b0cc2b86c2f4065b0ef28eead54448c2aa2ff01a3619ef 1740 
python-pam_0.4.2-13.3.dsc
 abe27899bc6b32f25cd1752fda25dfd13b2501a393a50be7c6cfbb679bea2ebf 2152 
python-pam_0.4.2-13.3.diff.gz
 e6a440799100783fd7f30a52b6cb759c8433ad5db2d0c9cbffbe2c4f8eca022d 6872 
python-pam_0.4.2-13.3_source.buildinfo
Files:
 16d20e6bf0a7db11c9706def12dcd81d 1740 python optional python-pam_0.4.2-13.3.dsc
 70c87eb7e2fffc9688219dfc4aaf42b9 2152 python optional 
python-pam_0.4.2-13.3.diff.gz
 0f9bb0856ad8d4c60139ac02b673d42b 6872 python optional 
python-pam_0.4.2-13.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8vB8YQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9SWEEACKNeZcalZsnzQq80wUhphZNKQCsVvp59Dj
PwrhAP1VVWfJqUXFfX+ihKUjZka14WiaAtTS8CMpAymLt0jSDtJlPnLdd1Xixhtc
uPxQ0CcINUScJXCl4C+6pr3tqEN/RHn2KiBdWhuDIWTSKt7wNGBpqmNTl9v1pi5S
rNLF3svymOnyLFrh/dFcPJ/WRAsaIYokg+dk74EV0frjU8H2wxIguZEcktCLLASx
QOMjvtrB3NyU4GFr/+MwIwNjkWie7a7Ek1FHsiOLR/6Y6VJYZkQtKLnVSuqBOKdM
5dbiq7Xi/HA4PcHVYVbJMWeGPm4C6sbRdf60gy/6S3RtLvkT3hmXGmLS+Srr+aO4
fAr63o22FUk8JySVoBNvub+q+QVfmUppz0zOQCW0zR5c8oso8k/FSRiGu+jF9Cv/
DyhqIyaXoS/JZBtWoE5uZ01CJ/lQQGngNcBI3ra6gXrObz++OmyVBr8594mIil9d
3RPcK6l4emsxIhIpTdR3sxjfB4QovkpBLORMgCgQJ/TP0cOR2RzAPZxztWTlr7mg
i+ngvIiFyR1ciC6fRONxBlyM0hs9/w8MO7EHoJ71OqJsmC1i09ln4n9Gnis5dJRU
U4hqyFijYZMvQI45hxVit4ciJUDzw/3lGuV2QyB4q+Hwv7IN/5JPLC8mgvLFrS/e
Zq5TB3m0eQ==
=ePev
-END PGP SIGNATURE End Message ---

Bug#966792: marked as done (scid: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:53:03 +
with message-id 
and subject line Bug#966792: fixed in scid 1:4.7.0+dfsg1-1.1
has caused the Debian Bug report #966792,
regarding scid: Unversioned Python 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.)


-- 
966792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scid
Version: 1:4.7.0+dfsg1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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-1.1
Done: Matthias Klose 

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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (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: SHA256

Format: 1.8
Date: Sat, 08 Aug 2020 22:28:10 +0200
Source: scid
Architecture: source
Version: 1:4.7.0+dfsg1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jose G. López 
Changed-By: Matthias Klose 
Closes: 966792
Changes:
 scid (1:4.7.0+dfsg1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using dh-python. Closes: #966792.
Checksums-Sha1:
 8b77ab7b9e5d99627f9d440bf9338317c93875d3 2006 scid_4.7.0+dfsg1-1.1.dsc
 4879dbf057fac037b2353df43318a07ff4454526 17892 
scid_4.7.0+dfsg1-1.1.debian.tar.xz
 c47651908f49d24697ce0f4856cbc070f8a963fc 7361 
scid_4.7.0+dfsg1-1.1_source.buildinfo
Checksums-Sha256:
 a387e5b704d9ff4871ca4a72d79769a9d26063a5404beaa6370ce583b37ea255 2006 
scid_4.7.0+dfsg1-1.1.dsc
 928e1424deddf0a2e72f2785c619951ee1bc527a516e56857b41887524f76f40 17892 
scid_4.7.0+dfsg1-1.1.debian.tar.xz
 f658e411fec8edb1a5330e7037a4bcbb867015fcad318b8c781648171ab5a8b3 7361 
scid_4.7.0+dfsg1-1.1_source.buildinfo
Files:
 bceaf67b98c39348aad0db57e7d6942a 2006 games optional scid_4.7.0+dfsg1-1.1.dsc
 6a80018c65aab8eb06ffa41cdf47db29 17892 games optional 
scid_4.7.0+dfsg1-1.1.debian.tar.xz
 9e13c79314533d5532c56e16cb683bbf 7361 games optional 
scid_4.7.0+dfsg1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8vCzEQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9baSD/0dva0ui/oj1qQB3sCnZgdO6lieI5FwLLO+
f8z3Q+VFkMchua3qSYMbnRda+Q5nJdB1Je+bb+CucZy4QxUPbU1Tj2H69yj/ccOT
co8ArRDmzLHvqlCRyN0G0BJ5QHjyalPlERka/SnlYXDAE14RSSdL8qTXeiLZ/4p2
db1BvgxTCFawDdUjm8fBBAXSG9IMp7D7W5AVTEugtzTtz6/8HLe873DU9ALAyIpu
EjeHO2R8HvP1FzW+BLfmgWsCJxZY/2Adub2hdwOkA6ZQJYzj3JNGqjy53qBmCbiM
02NBc4IX/k00WxxSMJqWg8n4Ovqm0m8Qr7DhwKIAMbdv8EKJlHKENWaR2tfdsubz
0m2tN7wCLXmvwja8rLFyre019TCddVTWAJ28M8eLI5tfFTG6HCEpY46LjfkG8XUb
42n0xvqHKJ1ONfsMILg5RC22+MkXMXT6eLgWloeVnKufxqxFxzrwcoOUCZz99tDn
4aeumjBsZyo4xjQx5xMz/S2dwVmmSZkZXszSizu7WYVsIApPZbiMlBh34dCSGtBQ
i6MzwdCT3wiDCJjb+nr5GkfCMFKVtEReXMdxsuC2ESas3tEO97AIt4kormicImKY
0ReYHBhNKqWXuoFVs3htfCzQhhvOQ2U/QtNDZfLRNCoPB0EHCzsy7XgtDeOuRNX3
fbBYDfiG3g==
=c7Ld
-END PGP SIGNATURE End Message ---

Bug#967163: marked as done (libiptcdata: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:52:35 +
with message-id 
and subject line Bug#967163: fixed in libiptcdata 1.0.5-2.2
has caused the Debian Bug report #967163,
regarding libiptcdata: Unversioned Python 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.)


-- 
967163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libiptcdata
Version: 1.0.5-2.1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: libiptcdata
Source-Version: 1.0.5-2.2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libiptcdata 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, 08 Aug 2020 22:18:23 +0200
Source: libiptcdata
Architecture: source
Version: 1.0.5-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Matthias Klose 
Closes: 966753 967163
Changes:
 libiptcdata (1.0.5-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using python2. Closes: #967163, #966753.
Checksums-Sha1:
 14563368432de20443d953c509eb8b5f755b7689 2439 libiptcdata_1.0.5-2.2.dsc
 5dbfd583a12d83b30773692324fcfed21cc72638 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 5e3e7f50945f9c0328d70b3d4dbb805d3f4d3ae2 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Checksums-Sha256:
 7dcada987dfbae875616470faf2b53cd1a99ab94f8317e4049d71366ca46bbec 2439 
libiptcdata_1.0.5-2.2.dsc
 15e3958a7b0fe95571bc6ca899536bd052597a76cde446fda7e2f6d7cc49d4f2 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 c0876eaf787d83c62a4b487d6f9d4509425a0008b12244d3fceef080b9f3ef4f 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Files:
 3f8055cc8689634a4d3a1cd5e45052d6 2439 libs optional libiptcdata_1.0.5-2.2.dsc
 7a720283e34e14cf2a2e50069040 7784 libs optional 
libiptcdata_1.0.5-2.2.debian.tar.xz
 a4edd570b1521e12a53b1cee77959ff9 9247 libs optional 
libiptcdata_1.0.5-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8vCesQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9YlVD/sHwLpH0sCISkf+2XHG9HsVFGeQ+T9IovCh
mBqlcU0QKUWzYW98mS5Kdw9hp3+/3/ctNbsOldcCEGkecv8Q4OGWYaqvR9AM43ka
OoTyeA9JuXMpQUBoEUnC5AKUE28LT7N/i5b9MAK/P/ZytTjT7uDyfUhZbQbSwJzf
GOh7WUv2n3dM/lDanQLh9wLVueBdhClxBRAU9J25iWW6p9qadfmw/I4B2RS1KS1V
SN8Zn/ft5aLSU9hlI9Kw0nm0EUzXp+g5eXVI8p3hyMp1E26FcFD4ioSqcNFIznbL
4iJzqVTXuaRBFAIeloHHBnzQvND+SExd9oJoxVrgwl8bGGU2qWHYwoswNtEk/7oZ
2P38hUmzJS/Ahwv0oujsIZIOooKVEDRt7/jpehOZU8zoz0l+yxtOapUW/5Cc0u2D
rziSZMvFormO6xQ7T8kTDuBYbX/U3mn7aTXYYRYF3Fv0EQWTSxr8tbf17Y6bSGKa
oxlGLCsBOjezuuOyAIkHuBEo/G+iuvOpPkdM22aPCXL/xOZV5vORWGLPDgBErxnG
b9IJn2ClCAdwp3KNhA1hGPKGAece9rd2sh17fjdYx2NKOQhoioJg3+bhc9lUu6kb
kpcV+eOfXML2Y0uf1uS+daTLxYJ7mosgBetgnRIM7uRmqVRO9g2aGEgrve3kyfge
5Rmfb6gmoQ==
=gYsd
-END PGP SIGNATURE End Message ---

Bug#966753: marked as done (libiptcdata: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:52:35 +
with message-id 
and subject line Bug#966753: fixed in libiptcdata 1.0.5-2.2
has caused the Debian Bug report #966753,
regarding libiptcdata: Unversioned Python 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.)


-- 
966753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libiptcdata
Version: 1.0.5-2.1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: libiptcdata
Source-Version: 1.0.5-2.2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libiptcdata 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, 08 Aug 2020 22:18:23 +0200
Source: libiptcdata
Architecture: source
Version: 1.0.5-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Matthias Klose 
Closes: 966753 967163
Changes:
 libiptcdata (1.0.5-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using python2. Closes: #967163, #966753.
Checksums-Sha1:
 14563368432de20443d953c509eb8b5f755b7689 2439 libiptcdata_1.0.5-2.2.dsc
 5dbfd583a12d83b30773692324fcfed21cc72638 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 5e3e7f50945f9c0328d70b3d4dbb805d3f4d3ae2 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Checksums-Sha256:
 7dcada987dfbae875616470faf2b53cd1a99ab94f8317e4049d71366ca46bbec 2439 
libiptcdata_1.0.5-2.2.dsc
 15e3958a7b0fe95571bc6ca899536bd052597a76cde446fda7e2f6d7cc49d4f2 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 c0876eaf787d83c62a4b487d6f9d4509425a0008b12244d3fceef080b9f3ef4f 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Files:
 3f8055cc8689634a4d3a1cd5e45052d6 2439 libs optional libiptcdata_1.0.5-2.2.dsc
 7a720283e34e14cf2a2e50069040 7784 libs optional 
libiptcdata_1.0.5-2.2.debian.tar.xz
 a4edd570b1521e12a53b1cee77959ff9 9247 libs optional 
libiptcdata_1.0.5-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8vCesQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9YlVD/sHwLpH0sCISkf+2XHG9HsVFGeQ+T9IovCh
mBqlcU0QKUWzYW98mS5Kdw9hp3+/3/ctNbsOldcCEGkecv8Q4OGWYaqvR9AM43ka
OoTyeA9JuXMpQUBoEUnC5AKUE28LT7N/i5b9MAK/P/ZytTjT7uDyfUhZbQbSwJzf
GOh7WUv2n3dM/lDanQLh9wLVueBdhClxBRAU9J25iWW6p9qadfmw/I4B2RS1KS1V
SN8Zn/ft5aLSU9hlI9Kw0nm0EUzXp+g5eXVI8p3hyMp1E26FcFD4ioSqcNFIznbL
4iJzqVTXuaRBFAIeloHHBnzQvND+SExd9oJoxVrgwl8bGGU2qWHYwoswNtEk/7oZ
2P38hUmzJS/Ahwv0oujsIZIOooKVEDRt7/jpehOZU8zoz0l+yxtOapUW/5Cc0u2D
rziSZMvFormO6xQ7T8kTDuBYbX/U3mn7aTXYYRYF3Fv0EQWTSxr8tbf17Y6bSGKa
oxlGLCsBOjezuuOyAIkHuBEo/G+iuvOpPkdM22aPCXL/xOZV5vORWGLPDgBErxnG
b9IJn2ClCAdwp3KNhA1hGPKGAece9rd2sh17fjdYx2NKOQhoioJg3+bhc9lUu6kb
kpcV+eOfXML2Y0uf1uS+daTLxYJ7mosgBetgnRIM7uRmqVRO9g2aGEgrve3kyfge
5Rmfb6gmoQ==
=gYsd
-END PGP SIGNATURE End Message ---

Bug#936880: marked as done (libiptcdata: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:52:35 +
with message-id 
and subject line Bug#966753: fixed in libiptcdata 1.0.5-2.2
has caused the Debian Bug report #966753,
regarding libiptcdata: 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.)


-- 
966753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libiptcdata
Version: 1.0.5-2.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:libiptcdata

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: libiptcdata
Source-Version: 1.0.5-2.2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libiptcdata 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, 08 Aug 2020 22:18:23 +0200
Source: libiptcdata
Architecture: source
Version: 1.0.5-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Matthias Klose 
Closes: 966753 967163
Changes:
 libiptcdata (1.0.5-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using python2. Closes: #967163, #966753.
Checksums-Sha1:
 14563368432de20443d953c509eb8b5f755b7689 2439 libiptcdata_1.0.5-2.2.dsc
 5dbfd583a12d83b30773692324fcfed21cc72638 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 5e3e7f50945f9c0328d70b3d4dbb805d3f4d3ae2 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Checksums-Sha256:
 7dcada987dfbae875616470faf2b53cd1a99ab94f8317e4049d71366ca46bbec 2439 
libiptcdata_1.0.5-2.2.dsc
 15e3958a7b0fe95571bc6ca899536bd052597a76cde446fda7e2f6d7cc49d4f2 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 c0876eaf787d83c62a4b487d6f9d4509425a0008b12244d3fceef080b9f3ef4f 9247 

Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:52:12 +
with message-id 
and subject line Bug#966903: fixed in gecode 6.2.0-4
has caused the Debian Bug report #966903,
regarding gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: 
parser.tab.hpp: 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.)


-- 
966903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gecode
Version: 6.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -I. -fcx-limited-range -fno-signaling-nans -fno-rounding-math 
> -ffinite-math-only -fno-math-errno -fno-strict-aliasing  -fvisibility=hidden 
> -ggdb -std=c++11 -pipe -Wall -Wextra -fPIC -pthread -DNDEBUG -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2  
> -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_CORE_LIB  -I. -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ \
>  \
> -c -o gecode/flatzinc/parser.tab.o  gecode/flatzinc/parser.tab.cpp
> gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such 
> file or directory
>   526 | #include "parser.tab.hpp"
>   |  ^~~~
> compilation terminated.
> make[2]: *** [Makefile:1492: gecode/flatzinc/parser.tab.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/gecode_6.2.0-3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Kari Pahula  (supplier of updated gecode 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, 08 Aug 2020 19:03:19 +0300
Source: gecode
Architecture: source
Version: 6.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Kari Pahula 
Changed-By: Kari Pahula 
Closes: 966903
Changes:
 gecode (6.2.0-4) unstable; urgency=medium
 .
   * Leave gecode/flatzinc/parser.tab.hpp name as is since the generated
 file gecode/flatzinc/parser.tab.cpp includes it. (Closes: #966903)
   * Standards-Version 4.5.0 and dh compat 13.
Checksums-Sha1:
 e1946499ee34d5c5512983679bc091aa3108dc39 2157 gecode_6.2.0-4.dsc
 512e7f5e5c3c4382f4805e9ad8926cac7c60f818 16692 gecode_6.2.0-4.debian.tar.xz
 8e082b62e5fa717b94b7a16cf7049129c75539e6 10455 gecode_6.2.0-4_source.buildinfo
Checksums-Sha256:
 ff054ed55e4a492097f3448075420373041823d881d8b7e2edec9ef1f747c42a 2157 
gecode_6.2.0-4.dsc
 f53103390cde3861a89f0a28a1cf117399f6ed47f3a7e31421d3c548d5bbc9b9 16692 
gecode_6.2.0-4.debian.tar.xz
 1a553d0aa3ff3fb948725fc4d3a1cd40cef3a5bb1d93ff878aeb55e8eef0c5af 10455 
gecode_6.2.0-4_source.buildinfo
Files:
 d8a46946c0ea0878f37e111aaa552636 2157 libs optional gecode_6.2.0-4.dsc
 16803d8ecbeeb7789ccc7b7bd9b521f8 16692 libs optional 
gecode_6.2.0-4.debian.tar.xz
 6429e8ed91c373d5e2ed3493d3ef92ad 10455 libs optional 
gecode_6.2.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECcOX/lMRGGlaUzRFhAhn7p2PJlwFAl8vAb8ACgkQhAhn7p2P
JlzkfQ/8DvwoZYfA6mqHBU8e1in8LsBAQ/mW/1hknwd/cRqYBw/bIajDcLASqXnA

Bug#966905: marked as done (minizinc: FTBFS: parser.tab.cpp:178:10: fatal error: parser.tab.hh: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:52:41 +
with message-id 
and subject line Bug#966905: fixed in minizinc 2.4.3-3
has caused the Debian Bug report #966905,
regarding minizinc: FTBFS: parser.tab.cpp:178:10: fatal error: parser.tab.hh: 
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.)


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++  -DHAS_GECODE -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -std=gnu++11 -o 
> CMakeFiles/minizinc_parser.dir/regex_lexer.yy.cpp.o -c 
> /<>/obj-x86_64-linux-gnu/regex_lexer.yy.cpp
> /<>/obj-x86_64-linux-gnu/parser.tab.cpp:178:10: fatal error: 
> parser.tab.hh: No such file or directory
>   178 | #include "parser.tab.hh"
>   |  ^~~
> compilation terminated.
> make[3]: *** [CMakeFiles/minizinc_parser.dir/build.make:88: 
> CMakeFiles/minizinc_parser.dir/parser.tab.cpp.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/minizinc_2.4.3-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Kari Pahula  (supplier of updated minizinc 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, 08 Aug 2020 23:13:21 +0300
Source: minizinc
Architecture: source
Version: 2.4.3-3
Distribution: unstable
Urgency: medium
Maintainer: Kari Pahula 
Changed-By: Kari Pahula 
Closes: 966905
Changes:
 minizinc (2.4.3-3) unstable; urgency=medium
 .
   * Symlink parser.tab.hh and regex_parser.tab.hh in build dir root to
 make Bison 3.7 generated parser.tab.cpp and regex_parser.tab.cpp
 happy.  (Closes: #966905)
   * Disambiguate file glob in debian/copyright.
Checksums-Sha1:
 68bc6e89acd50e42a32d3f38c1984cb600051ed2 1798 minizinc_2.4.3-3.dsc
 a831fdcbe77187a756d93d09bd778c50428e5a3d 9580 minizinc_2.4.3-3.debian.tar.xz
 82cc511494c26550fc6dfbe83fe23912011002cd 11994 
minizinc_2.4.3-3_source.buildinfo
Checksums-Sha256:
 679e6588a56e0ac8958af43d6743364694f8a4832074170b467e4849cf9f7c00 1798 
minizinc_2.4.3-3.dsc
 9098e6260e6afb2fd3733272e02e32145665e7a5b9437e67e3955389adbaa87f 9580 
minizinc_2.4.3-3.debian.tar.xz
 6f22bcf97357d717cda79426bbd4d7c4b5f13ef5242aa7cd9f84349678f3bfa1 11994 
minizinc_2.4.3-3_source.buildinfo
Files:
 d6a080c3af6f293560513e3f18f7c43f 1798 devel optional minizinc_2.4.3-3.dsc
 79b8289b09eb8c1e5d71bd12fe2d0d44 9580 devel optional 
minizinc_2.4.3-3.debian.tar.xz
 dd34a7903d994242879c6ec1ecfe4045 11994 devel optional 
minizinc_2.4.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECcOX/lMRGGlaUzRFhAhn7p2PJlwFAl8vB54ACgkQhAhn7p2P
Jlw2og//XBZ8QX8xcQ5LZETBs/62M3QKtQ0r5d1Ql9sC2bZYa/iSXIT7Q5MoIrxE
JcjGLakFRvWDfjyJMl1IvGK/J3krbC/awABTE6tJApT1uZevrl9OWQ5Lk/flaFVK
acz1/kdEkLnFOuT8J3mS9fvzRCCkOCi6ZeR1MPhsdR95QWw4xxBdt38IyqjUrbHf
R7au3bJFuDuvW33iuGdS4wWXXynls7pNHpIhLafmrrX3laQTkhNhrMfEMncARGI3
d9LRTkF68wnkGU45v4FnOTMis5ZQiM1mDs7lQyrcKTtfMHmo++QKtKG7zGDleD2Y
4trjD8GsCsBr7Ifz+wbnC+hFPxA+5nMj4/ORoz22PEhrKDeW7joemVA5tKFS5Zdq
WP4A6LTvWzJ/rW9UkaF9SbZsNgcWm4MqBN02/W1tx7lFkPFbDjBwaHukhi7/1blv

Bug#967175: marked as done (mozilla-devscripts: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 20:30:24 +
with message-id 
and subject line Bug#967175: fixed in mozilla-devscripts 0.54.1
has caused the Debian Bug report #967175,
regarding mozilla-devscripts: Unversioned Python 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.)


-- 
967175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mozilla-devscripts
Version: 0.54
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: mozilla-devscripts
Source-Version: 0.54.1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated mozilla-devscripts 
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, 08 Aug 2020 21:43:05 +0200
Source: mozilla-devscripts
Architecture: source
Version: 0.54.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Matthias Klose 
Closes: 967175
Changes:
 mozilla-devscripts (0.54.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * No-change upload to generate dependency on python2. Closes: #967175.
Checksums-Sha1:
 8be7d4a0f66c9564da7fe88fe0fc794e94557f71 1807 mozilla-devscripts_0.54.1.dsc
 5f302c0901b65e7a51c9ba84b00863ac8206d139 42376 mozilla-devscripts_0.54.1.tar.xz
 e43dde402322ea8e1add8a7687bfaeb0bfd7f090 6951 
mozilla-devscripts_0.54.1_source.buildinfo
Checksums-Sha256:
 af2660b398b41f4cbfb6724f2d475f89797c8bcf912158832b8848d0fc1815da 1807 
mozilla-devscripts_0.54.1.dsc
 39e80b2be956b087f00a64d1b7f5a82645a815bb3d823dbfc8110fae5c6a1c89 42376 
mozilla-devscripts_0.54.1.tar.xz
 168bd5860743aa0f540bdb34586ecf5548505ba4bae67b34bedfdb9e8ec39dc5 6951 
mozilla-devscripts_0.54.1_source.buildinfo
Files:
 7cd7a8583d7aacade4f20ff7ad45c368 1807 devel optional 
mozilla-devscripts_0.54.1.dsc
 a979a76b1c8d084b78d9cf538c0f446f 42376 devel optional 
mozilla-devscripts_0.54.1.tar.xz
 2831f45d43bfb8edc135e89a790cdf72 6951 devel optional 
mozilla-devscripts_0.54.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8vAhIQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9Zg7D/4p3MB6+374mKz4QlQW1PM2qTupTwIZx3yT
K1Yq3GQVq0vpnUdjnilRHuQMxbZ6g5GHPn0DUTfr1lhim1sZG4YXYNAA5h4qEne3
7xPohcUMZUMtwJDRT1quBSVPTSCP74Ig/IVxZe8FwTNhg5Ott+qWKd2nreQf/Qv9
efwmEM78fKQuGpRd5aGvnafSXkgkusifnk0NxNZl4lUSoiYH1WFiQKeuLEz2F9rn
p/CcgyIVIXeA1XFGZKXytvTpS5HHe1deVJNoM6ynWD0cCcCPAnoA8k5zR+bUCPU5
gBDRBVhvdqkUcbkG3C/DW+fuFXrQ+0Dzqnr7FGwgh69O+YewyTbn+tb1qDBRW8ns
p3Zfw5qeJjXH7o6/G7zIXD3U64Utoq8/K4Mr8YaxjahalZ6ZBGkwU6V1jzE0l+nC
uoH8WR0Q0R6mOp7F7MlqVugSXES3Ek6hCxYHzqTV84Q0j/LI1yQg4Xlo+h4jLxxk
6KX+XZiNChtTZmG/Dgr/7FPYpAsSM0gj5faFLQFVYkbxKKZdaI2ORISt/ZKQqfZe
ZrHVmLVjo4hbFAsJm0yy5rjODnIVFLEfiNtaISVsRTbSA7t8dwz5jzj1nxv68rsi
kQMj5IWK5S/EcjoBqm10kk3jaH8QZco+bsrMaACJrP5i1N0rxduBy6UhJTN6D9d1
hfICaRtntw==
=Bzh9
-END PGP 

Bug#957370: marked as done (ipv6toolkit: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 19:49:34 +
with message-id 
and subject line Bug#957370: fixed in ipv6toolkit 2.0+ds.1-1
has caused the Debian Bug report #957370,
regarding ipv6toolkit: 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.)


-- 
957370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipv6toolkit
Version: 2.0-1
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/ipv6toolkit_2.0-1_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

[...]
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package ipv6toolkit
dpkg-buildpackage: info: source version 2.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Octavio Alvarez 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean 
dh: warning: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 9 are deprecated (level 8 
in use)
make -j1 clean
make[1]: Entering directory '/<>'
rm -f addr6 blackhole6 flow6 frag6 icmp6 jumbo6 na6 ni6 ns6 path6 ra6 rd6 rs6 
scan6 script6 tcp6 udp6 libipv6.o
rm -f data/ipv6toolkit.conf
make[1]: Leaving directory '/<>'
   dh_clean
dh_clean: warning: Compatibility levels before 9 are deprecated (level 8 in use)
 debian/rules build
dh build 
dh: warning: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 9 are deprecated (level 
8 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mkdir -p data
dh_auto_build
dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 8 
in use)
make -j1
make[2]: Entering directory '/<>'
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c -o libipv6.o tools/libipv6.c
tools/libipv6.c: In function ‘in_chksum’:
tools/libipv6.c:982:2: warning: converting a packed ‘struct ipv6pseudohdr’ 
pointer (alignment 1) to a ‘uint16_t’ {aka ‘short unsigned int’} pointer 
(alignment 2) may result in an unaligned pointer value 
[-Waddress-of-packed-member]
  982 |  w= (uint16_t *) 
  |  ^
In file included from tools/libipv6.c:64:
tools/libipv6.h:269:8: note: defined here
  269 | struct ipv6pseudohdr{
  |^
In file included from /usr/include/string.h:495,
 from /usr/include/netinet/icmp6.h:22,
 from tools/libipv6.c:36:
In function ‘strncpy’,
inlined from ‘sel_src_addr’ at tools/libipv6.c:3521:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ output may be truncated copying 15 bytes from a string of 
length 15 [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -o addr6 tools/addr6.c libipv6.o -Wl,-z,relro 
-Wl,-z,now -lpcap -lm 
cp tools/blackhole6 ./
gcc 

Bug#967932: marked as done (redland-bindings: FTBFS: lots of undefined reference errors from ld)

[Debian Bug Tracking System]

Your message dated Sat, 8 Aug 2020 21:39:38 +0200
with message-id <40d7978e-bb7b-759f-bc0e-a94d2772f...@debian.org>
and subject line Re: redland-bindings: FTBFS: lots of undefined reference 
errors from ld
has caused the Debian Bug report #967932,
regarding redland-bindings: FTBFS: lots of undefined reference errors from ld
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.)


-- 
967932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redland-bindings
Version: 1.0.17.1+dfsg-1.3
Severity: serious
Tags: bullseye sid ftbfs

I was looking at #966787, and while the fix for that bug should be easy
(just remove python-librdf's hardcoded python dependency), I could not
build the package in a current amd64 sid chroot:

,
| gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/rasqal -I/usr/include/raptor2  -DSWIG_PYTHON_SILENT_MEMLEAK -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security Redland_wrap.so  -Wl,-z,relro  -lrdf  -lrasqal 
-lraptor2  -o _Redland
| /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/Scrt1.o: in function 
`_start':
| (.text+0x20): undefined reference to `main'
| /usr/bin/ld: Redland_wrap.so: in function `SWIG_Python_ErrorType':
| ./python2.7/./Redland_wrap.c:955: undefined reference to `PyExc_IOError'
| /usr/bin/ld: ./python2.7/./Redland_wrap.c:952: undefined reference to 
`PyExc_MemoryError'
`

In the last successful build[1], the corresponding gcc commandline used
"-shared" and ended with "-o _Redland.so" rather "-o _Redland", so
trying to build an executable is apparently want went wrong here.

A build log is attached for reference.


1. 
https://buildd.debian.org/status/fetch.php?pkg=redland-bindings=amd64=1.0.17.1%2Bdfsg-1.3%2Bb9=1584636898=0



redland-bindings_1.0.17.1+dfsg-1.3_amd64.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
not sure what the bug submitter was trying, but 1.0.17.1+dfsg-1.4 just built 
fine.--- End Message ---

Bug#966210: marked as done (src:django-ranged-response: fails to migrate to testing for too long: maintainer built arch:all binary)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 19:34:11 +
with message-id 
and subject line Bug#966210: fixed in django-ranged-response 0.2.0-4.1
has caused the Debian Bug report #966210,
regarding src:django-ranged-response: fails to migrate to testing for too long: 
maintainer built arch:all binary
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.)


-- 
966210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-ranged-response
Version: 0.2.0-2
Severity: serious
Control: close -1 0.2.0-4
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: django-ranged-response
Source-Version: 0.2.0-4.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated django-ranged-response 
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, 24 Jul 2020 20:41:06 +0200
Source: django-ranged-response
Architecture: source
Version: 0.2.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: FreedomBox packaging team 

Changed-By: Paul Gevers 
Closes: 966210
Changes:
 django-ranged-response (0.2.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #966210)
Checksums-Sha1:
 262e001fe5231ba357db1b1bfb0ce4bf5e17f5d0 2097 
django-ranged-response_0.2.0-4.1.dsc
 69f60c49383451f65f5b10118878a0bc266c5c2a 3456 
django-ranged-response_0.2.0-4.1.debian.tar.xz
Checksums-Sha256:
 9e89e3658509d9161e756c22a3be4aaec1d96b006cf59d5f7da3e3fdcdb36776 2097 
django-ranged-response_0.2.0-4.1.dsc
 2509a06280fe4b8ea82a71bc72ebc3d853b7134f76cead3afc0ef41b26d29b4e 3456 
django-ranged-response_0.2.0-4.1.debian.tar.xz
Files:
 472b02546b7ec27e119887dfaf297973 2097 python optional 
django-ranged-response_0.2.0-4.1.dsc
 20dc3755806d2d60e39edb1385d9e8e5 3456 python optional 
django-ranged-response_0.2.0-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl8bK2YACgkQnFyZ6wW9
dQpUdQf/RQ/sjiyv5V6Q78257G0ocTyp4XnqLrqRzTUFFC9tDYWfe+PKXgV7If7l

Bug#957086: chordii: diff for NMU version 4.5.3+repack-0.2

[Sudip Mukherjee]

Control: tags 957086 + patch
Control: tags 957086 + pending

Dear maintainer,

I've prepared an NMU for chordii (versioned as 4.5.3+repack-0.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru chordii-4.5.3+repack/debian/changelog 
chordii-4.5.3+repack/debian/changelog
--- chordii-4.5.3+repack/debian/changelog   2017-01-03 12:27:24.0 
+
+++ chordii-4.5.3+repack/debian/changelog   2020-08-08 20:23:47.0 
+0100
@@ -1,3 +1,10 @@
+chordii (4.5.3+repack-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957086)
+
+ -- Sudip Mukherjee   Sat, 08 Aug 2020 20:23:47 
+0100
+
 chordii (4.5.3+repack-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru chordii-4.5.3+repack/debian/patches/fix_ftbfs.patch 
chordii-4.5.3+repack/debian/patches/fix_ftbfs.patch
--- chordii-4.5.3+repack/debian/patches/fix_ftbfs.patch 1970-01-01 
01:00:00.0 +0100
+++ chordii-4.5.3+repack/debian/patches/fix_ftbfs.patch 2020-08-08 
20:23:23.0 +0100
@@ -0,0 +1,38 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957086
+Forwarded: no
+
+---
+
+--- chordii-4.5.3+repack.orig/src/chordii.h
 chordii-4.5.3+repack/src/chordii.h
+@@ -74,12 +74,14 @@ struct kcs {
+   int s1,s2,s3,s4,s5,s6;
+   int origin;
+   int difficult;
+-  } dummy_kcs;
++  };
++extern struct kcs dummy_kcs;
+ 
+ struct chord_struct {
+   struct chord_struct *next;
+   struct kcs *chord;
+-  } dummy_chord_struct;
++  };
++extern struct chord_struct dummy_chord_struct;
+ 
+ struct sub_title_struct {
+   struct sub_title_struct *next_sub;
+--- chordii-4.5.3+repack.orig/src/grid.c
 chordii-4.5.3+repack/src/grid.c
+@@ -19,6 +19,8 @@
+ 
+ struct chord_struct *so_chordtab = NULL;
+ struct kcs *so_known_chords = NULL;
++struct kcs dummy_kcs;
++struct chord_struct dummy_chord_struct;
+ 
+ int   nb_chord = 0;
+ int   first_ptr = 0;
diff -Nru chordii-4.5.3+repack/debian/patches/series 
chordii-4.5.3+repack/debian/patches/series
--- chordii-4.5.3+repack/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ chordii-4.5.3+repack/debian/patches/series  2020-08-08 20:23:47.0 
+0100
@@ -0,0 +1 @@
+fix_ftbfs.patch

Processed: chordii: diff for NMU version 4.5.3+repack-0.2

[Debian Bug Tracking System]

Processing control commands:

> tags 957086 + patch
Bug #957086 [src:chordii] chordii: ftbfs with GCC-10
Added tag(s) patch.
> tags 957086 + pending
Bug #957086 [src:chordii] chordii: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#964611: libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Abou Al Montacir]

Hi Paul

On Fri, 2020-08-07 at 15:16 +0200, Abou Al Montacir wrote:
> I'm going to upload both FPC 3.2.0 and Lazarus 2.0.10. So maybe you can wait
> until I upload them before fixing this?
I've just pushed new sources for libqtpat 2.6+2.0.10+dfsg.
I've verified in cowbuilder that we have the very same issue, so you should not
have any particular issue when applying your patch to the new release.
Please upload to SID as soon as you are done.
-- 
Cheers,
Abou Al Montacir


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

Bug#963394: marked as done (apper: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 18:48:34 +
with message-id 
and subject line Bug#962567: fixed in debconf-kde 1.0.3-4
has caused the Debian Bug report #962567,
regarding apper: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && 
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DDEBCONF_SUPPORT=ON -DAPPSTREAM=ON -DAUTOREMOVE=ON 
-DEDIT_ORIGNS_DESKTOP_NAME=software-properties-kde .. returned exit code 1
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -Skde -- -DDEBCONF_SUPPORT=ON -DAPPSTREAM=ON 
> -DAUTOREMOVE=ON -DEDIT_ORIGNS_DESKTOP_NAME=software-properties-kde
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
> -DDEBCONF_SUPPORT=ON -DAPPSTREAM=ON -DAUTOREMOVE=ON 
> -DEDIT_ORIGNS_DESKTOP_NAME=software-properties-kde ..
> -- The C compiler identification is GNU 9.3.0
> -- The CXX compiler identification is GNU 9.3.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) 
> -- Installing in the same prefix as Qt, adopting their path scheme.
> -- Looking for __GLIBC__
> -- Looking for __GLIBC__ - found
> -- Performing Test _OFFT_IS_64BIT
> -- Performing Test _OFFT_IS_64BIT - Success
> -- Performing Test HAVE_DATE_TIME
> -- Performing Test HAVE_DATE_TIME - Success
> -- Could not set up the appstream test. appstreamcli is missing.
> -- Found KF5Config: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5DocTools: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5GuiAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5GuiAddons/KF5GuiAddonsConfig.cmake (found 
> version "5.70.0") 
> -- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
> -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5KCMUtils: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5KCMUtils/KF5KCMUtilsConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5DBusAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5KIO: /usr/lib/x86_64-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5Notifications: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Notifications/KF5NotificationsConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5IconThemes: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5: success (found version "5.70.0") found components: Config 
> DocTools GuiAddons I18n KCMUtils DBusAddons KIO Notifications IconThemes 
> -- Building Apper with auto remove: ON
> -- Building Apper with AppStream support: ON
> -- Building Apper with Limba support: OFF
> CMake Error at 
> /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
> (find_package):
>   By not providing "FindKF5TextWidgets.cmake" in CMAKE_MODULE_PATH this
>   project has asked CMake to find a 

Bug#962567: marked as done (libdebconf-kde-dev misses dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 18:48:34 +
with message-id 
and subject line Bug#962567: fixed in debconf-kde 1.0.3-4
has caused the Debian Bug report #962567,
regarding libdebconf-kde-dev misses dependencies
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.)


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

Package: apper
Version: 1.0.0-2
Severity: serious
Tags: bullseye, sid, patch

http://buildd.raspbian.org/status/fetch.php?pkg=apper=armhf=1.0.0-2%2Bb4=1591727741

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


CMake Error at /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
(find_package):
   By not providing "FindKF5TextWidgets.cmake" in CMAKE_MODULE_PATH this
   project has asked CMake to find a package configuration file provided by
   "KF5TextWidgets", but CMake did not find one.

   Could not find a package configuration file provided by "KF5TextWidgets"
   with any of the following names:

 KF5TextWidgetsConfig.cmake
 kf5textwidgets-config.cmake

   Add the installation prefix of "KF5TextWidgets" to CMAKE_PREFIX_PATH or set
   "KF5TextWidgets_DIR" to a directory containing one of the above files.  If
   "KF5TextWidgets" provides a separate development package or SDK, be sure it
   has been installed.
Call Stack (most recent call first):
   /usr/lib/arm-linux-gnueabihf/cmake/DebconfKDE/DebconfKDEConfig.cmake:100 
(find_dependency)
   CMakeLists.txt:71 (find_package)


-- Configuring incomplete, errors occurred!

This appears to be a case of a missing build-dependency on libkf5textwidgets-dev


It seems it was previously pulled in indirectly but that is no longer the case

--- End Message ---
--- Begin Message ---
Source: debconf-kde
Source-Version: 1.0.3-4
Done: Pino Toscano 

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated debconf-kde package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Aug 2020 20:23:55 +0200
Source: debconf-kde
Architecture: source
Version: 1.0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Pino Toscano 
Closes: 962567
Changes:
 debconf-kde (1.0.3-4) unstable; urgency=medium
 .
   * Team upload.
   * Add the configuration for the CI on salsa.
   * Drop the Debian man page, as it is outdated.
   * Remove the unused 'testsuite' autopkgtest.
   * Explicitly add the gettext build dependency.
   * Update the dependencies of libdebconf-kde-dev to what the cmake config file
 requires: (Closes: #962567)
 - add libkf5coreaddons-dev, libkf5i18n-dev, libkf5iconthemes-dev,
   libkf5textwidgets-dev, and libkf5widgetsaddons-dev
   * Bump the debhelper compatibility to 13:
 - switch the debhelper-compat build dependency to 13
   * Remove breaks/replaces for versions older than what is in oldstable.
Checksums-Sha1:
 abf9e1ad58e2ec7059118a4b6f95fa3be394f69c 2827 debconf-kde_1.0.3-4.dsc
 774060cef434e2b02bc96e255ecb65803100d860 9780 debconf-kde_1.0.3-4.debian.tar.xz
 74d8419ba8a02db7f9f8c59a3c6712a7c9c8c86c 13177 
debconf-kde_1.0.3-4_source.buildinfo
Checksums-Sha256:
 f57d4dd316fd68eba556789a8f43f8ce058424471be52d486e294926559d85d5 2827 
debconf-kde_1.0.3-4.dsc
 17980dfca2ae672a6c43dad8b34cb682245ee1434657759d1b2c55ed8c3cdefd 9780 
debconf-kde_1.0.3-4.debian.tar.xz
 08b401a430d61a5294ac67693b43452f13d353ed486fc1218430c6145b6af9b4 13177 
debconf-kde_1.0.3-4_source.buildinfo
Files:
 21c7a4ebfd7872bada6b1191e3ba7554 2827 kde optional debconf-kde_1.0.3-4.dsc
 b54efa85e8f04541dfd07f91e20080bb 9780 kde optional 
debconf-kde_1.0.3-4.debian.tar.xz
 e724e97e5ca560691cea8a35cbcf 13177 kde optional 
debconf-kde_1.0.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl8u7eYACgkQLRkciEOx
P00DMA//WBKxviuv1ADToy8J00i7Rh7n6qPWJNGAGU/rV2jeK15slTPg8M+Bu0FR

Bug#963432: marked as done (muon: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 18:48:34 +
with message-id 
and subject line Bug#962567: fixed in debconf-kde 1.0.3-4
has caused the Debian Bug report #962567,
regarding muon: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && 
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. returned 
exit code 1
to be marked as done.

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

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


-- 
962567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: muon
Version: 4:5.8.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_testdir  
> dh_auto_configure '--buildsystem=kf5' --parallel  
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
> -- The C compiler identification is GNU 9.3.0
> -- The CXX compiler identification is GNU 9.3.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Could not set up the appstream test. appstreamcli is missing.
> -- Looking for __GLIBC__
> -- Looking for __GLIBC__ - found
> -- Performing Test _OFFT_IS_64BIT
> -- Performing Test _OFFT_IS_64BIT - Success
> -- Performing Test HAVE_DATE_TIME
> -- Performing Test HAVE_DATE_TIME - Success
> -- Found KF5KIO: /usr/lib/x86_64-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5DBusAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake 
> (found version "5.70.0") 
> -- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
> -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5IconThemes: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake 
> (found version "5.70.0") 
> -- Found KF5XmlGui: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found 
> version "5.70.0") 
> -- Found KF5: success (found version "5.70.0") found components: KIO 
> DBusAddons I18n IconThemes XmlGui 
> CMake Error at 
> /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
> (find_package):
>   By not providing "FindKF5TextWidgets.cmake" in CMAKE_MODULE_PATH this
>   project has asked CMake to find a package configuration file provided by
>   "KF5TextWidgets", but CMake did not find one.
> 
>   Could not find a package configuration file provided by "KF5TextWidgets"
>   with any of the following names:
> 
> KF5TextWidgetsConfig.cmake
> kf5textwidgets-config.cmake
> 
>   Add the installation prefix of "KF5TextWidgets" to CMAKE_PREFIX_PATH or set
>   "KF5TextWidgets_DIR" to a directory containing one of the above files.  If
>   "KF5TextWidgets" provides a separate development package or SDK, be sure it
>   has been installed.
> Call Stack (most recent call first):
>   /usr/lib/x86_64-linux-gnu/cmake/DebconfKDE/DebconfKDEConfig.cmake:100 
> (find_dependency)
>   CMakeLists.txt:22 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build 

Bug#944401: marked as done (pgcli: does not start due to unmet psycopg2 requirement)

[Debian Bug Tracking System]

Your message dated Sat, 8 Aug 2020 20:12:21 +0200
with message-id 
and subject line Re: pgcli: does not start due to unmet psycopg2 requirement
has caused the Debian Bug report #944401,
regarding pgcli: does not start due to unmet psycopg2 requirement
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.)


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

Dear Maintainer,

When starting /usr/bin/pgcli the script terminates with a Version
conflict error.
It seems like the packaged python3-psycopg2 version is too recent for
the packaged pgcli release.

$ pgcli
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 791, in 
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (psycopg2 2.8.3 
(/usr/lib/python3/dist-packages), Requirement.parse('psycopg2<2.8,>=2.7.4'), 
{'pgcli'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/pgcli", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3250, 
in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3234, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3263, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 585, in 
_build_master
return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 598, in 
_build_from_requirements
dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'psycopg2<2.8,>=2.7.4' distribution was 
not found and is required by pgcli


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

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

Versions of packages pgcli depends on:
ii  python3 3.7.5-1
ii  python3-click   7.0-2
ii  python3-configobj   5.0.6-3
ii  python3-humanize0.5.1-3
ii  python3-pgspecial   1.9.0-2
ii  python3-prompt-toolkit  1.0.15-1
ii  python3-psycopg22.8.3-2
ii  python3-pygments2.3.1+dfsg-1
ii  python3-setproctitle1.1.10-1+b2
ii  python3-sqlparse0.2.4-1
ii  python3-tabulate0.8.2-1.1
ii  python3-terminaltables  3.1.0-2

pgcli recommends no packages.

pgcli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
close 944401 2.2.0-2
thanks

Hi,

thank you for reporting this bug, it has been fixed as of pgcli 2.2.0-2
some time ago (which adds compatibility for psycopg2 >=2.8).

Regards,
Daniel--- End Message ---

Processed: tagging 962567

[Debian Bug Tracking System]

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

> tags 962567 + pending
Bug #962567 [libdebconf-kde-dev] libdebconf-kde-dev misses dependencies
Bug #963394 [libdebconf-kde-dev] apper: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DDEBCONF_SUPPORT=ON -DAPPSTREAM=ON -DAUTOREMOVE=ON 
-DEDIT_ORIGNS_DESKTOP_NAME=software-properties-kde .. returned exit code 1
Bug #963432 [libdebconf-kde-dev] muon: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. returned 
exit code 1
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#960463: marked as done (mycli doesn't work the prompt-toolkit >= 3.0.0)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 18:03:42 +
with message-id 
and subject line Bug#960463: fixed in mycli 1.22.2-0.1
has caused the Debian Bug report #960463,
regarding mycli doesn't work the prompt-toolkit >= 3.0.0
to be marked as done.

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

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


-- 
960463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mycli
Version: 1.21.1-1
Severity: important
Tags: patch

Dear Maintainer,

mycli version 1.21.1-1 claims to fix incompatibility with
prompt-toolkit 3.0 but that does not seem to be the case with my
system.  Using prompt-toolkit 3.0.5-2, I get the following traceback.

Traceback (most recent call last):
  File "/usr/bin/mycli", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3259, 
in 
def _initialize_master_working_set():
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3242, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3271, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 586, in 
_build_master
return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 599, in 
_build_from_requirements
dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 787, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'prompt_toolkit<3.0.0,>=2.0.6' 
distribution was not found and is required by mycli

To get it to work, I had to apply the following patch.

--- setup.py~   2020-05-12 16:01:55.0 -0500
+++ setup.py2020-05-12 16:10:54.314829760 -0500
@@ -19,7 +19,7 @@
 install_requirements = [
 'click >= 7.0',
 'Pygments >= 1.6',
-'prompt_toolkit>=2.0.6,<3.0.0',
+'prompt_toolkit>=2.0.6,<4.0.0',
 'PyMySQL >= 0.9.2',
 'sqlparse>=0.3.0,<0.4.0',
 'configobj >= 5.0.5',

This is an adaptation of upstream commit
08d56d8b479111641094f86d324f1ff232451b05.  This version preserves
compatibility with prompt-toolkit 2.x.

David Engel


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

Kernel: Linux 5.6.0-1-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mycli depends on:
ii  python3 3.8.2-3
ii  python3-click   7.0-3
ii  python3-configobj   5.0.6-4
ii  python3-cryptography2.8-4
ii  python3-pkg-resources   46.1.3-1
ii  python3-prompt-toolkit  3.0.5-2
ii  python3-pygments2.3.1+dfsg-3
ii  python3-pymysql 0.9.3-2
ii  python3-sqlparse0.3.1-1
ii  python3-tabulate0.8.2-1.1
ii  python3-terminaltables  3.1.0-3

mycli recommends no packages.

mycli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mycli
Source-Version: 1.22.2-0.1
Done: Daniel Baumann 

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

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

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated mycli 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Aug 2020 17:41:43 +0200
Source: mycli
Architecture: source
Version: 1.22.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Lennart Weller 
Changed-By: Daniel Baumann 
Closes: 960463 966385
Changes:
 mycli (1.22.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (Closes: #966385):
 - 

Bug#966857: libtpms: FTBFS: tpm2/NVDynamic.c:126:10: error: ‘nvHandle’ may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Seunghun Han]

Hi Lucas,

On Mon, Aug 3, 2020 at 5:12 PM Lucas Nussbaum  wrote:
>
> Source: libtpms
> Version: 0.8.0~dev1-1.1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200802 ftbfs-bullseye
> ... [snip] ...
> > tpm2/NVDynamic.c: In function ‘NvNextByType’:
> > tpm2/NVDynamic.c:126:10: error: ‘nvHandle’ may be used uninitialized in 
> > this function [-Werror=maybe-uninitialized]
> >   126 |  *handle = nvHandle;
> >   |  ^~

Thank you for your notification. I just fixed the FTBFS bug and will
upload the newer version 0.8.0~dev1-1.2 soon.

Best regards,

Seunghun

Bug#940793: marked as done (Please replace transitional dependency polkit-kde-1 with polkit-kde-agent-1)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 17:33:25 +
with message-id 
and subject line Bug#940793: fixed in apper 1.0.0-3
has caused the Debian Bug report #940793,
regarding Please replace transitional dependency polkit-kde-1 with 
polkit-kde-agent-1
to be marked as done.

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

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


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

Source: apper
Version: 1.0.0-2
Severity: wishlist

Hi,

The next version of the polkit-kde-agent-1 package will drop the transitional 
polkit-kde-1 package. As the transitional package has been around for quite a 
while now. Please update apper to depend on polkit-kde-agent-1.


Happy hacking,

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

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

--
"La duración de un minuto depende de que lado del baño estés."
-- Ley de la Relatividad (Burke)
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: apper
Source-Version: 1.0.0-3
Done: Matthias Klumpp 

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated apper 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, 08 Aug 2020 18:45:46 +0200
Source: apper
Architecture: source
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp 
Changed-By: Matthias Klumpp 
Closes: 925252 940793
Changes:
 apper (1.0.0-3) unstable; urgency=medium
 .
   [ Matthias Klumpp ]
   * Update-AppStream-metainfo.patch: Sync metainfo data with upstream
   * Refresh all patches
   * Bump standards version (no changes needed)
   * Set flag that d/rules doesn't require root
 .
   [ John Scott ]
   * Fix crash by iterating variable properly. Thanks to Alexander
 Kernozhitsky for authoring the upstream patch. (Closes: #925252)
   * Switch dependency on transitional polkit-kde-1 for polkit-kde-agent-1.
 (Closes: #940793)
   * Add formerly-transitive dependency libkf5textwidgets-dev explicitly.
   * Cherrypick upstream patch to fix build with Qt 5.14.
   * debian/copyright: Update links and upgrade to HTTPS as suggested by duck.
Checksums-Sha1:
 65530c9989950e630cf02565654eda21ec4d016a 2442 apper_1.0.0-3.dsc
 0179aa0b458fa1d9c593ee0c00c5958385b66e78 2056124 apper_1.0.0.orig.tar.xz
 d9228952ef31fb4fae7160947dce9459a82fbd89 16032 apper_1.0.0-3.debian.tar.xz
 599aa656beec01c34930e8e06c6ffe59502c4700 24443 apper_1.0.0-3_source.buildinfo
Checksums-Sha256:
 ab71a5ce3d3f915487a3c6e3799268348f0d00e137361068b15f2d1b3b746e17 2442 
apper_1.0.0-3.dsc
 1a30be92aab8bd258c2a8824f533c5646b934e06b4268edbd11724ea450f4923 2056124 
apper_1.0.0.orig.tar.xz
 1f76b71c85ac6a3a8318241f59aaa4eaacf09763b76fee5fce6cd9352a13e4d7 16032 
apper_1.0.0-3.debian.tar.xz
 fa77f9707c10fbd072bc7b31bf92f3c4bdfe6cd51d04a5f4460def1dc3870dcc 24443 
apper_1.0.0-3_source.buildinfo
Files:
 9faa7d3ff74ff4840efdf2c5a5af199c 2442 kde optional apper_1.0.0-3.dsc
 7068ee7a0a175daed7aac1fb561d8df8 2056124 kde optional apper_1.0.0.orig.tar.xz
 9e3089a1ccdd3916f5cf7499e75e1be9 16032 kde optional apper_1.0.0-3.debian.tar.xz
 828d7fe09cadd6b3430411048699b141 24443 kde optional 
apper_1.0.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAl8u3LAPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/TezrO4MP/1iZnRL/GI5RJHjMV+aLp1yL9F4LuMy0vSz4

Processed: tagging 946341, tagging 950631, tagging 957188

[Debian Bug Tracking System]

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

> tags 946341 + pending
Bug #946341 [src:exiv2] exiv2: CVE-2019-17402
Added tag(s) pending.
> tags 950631 + pending
Bug #950631 [src:exiv2] exiv2: please mark one symbol as optional
Added tag(s) pending.
> tags 957188 + pending
Bug #957188 [src:exiv2] exiv2: ftbfs with GCC-10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#966470: fix for #966470: biobambam2 autopkgtest failures

[Étienne Mollier]

Control: tags -1 pending

Good day,

I had a look at the autopkgtest failure affecting biobambam2,
and since these segmentation faults were showing up only in my
autopkgtest environment, and not when using the package directly
on my system, it felt like a missing dependency.  So I trapped
system calls issued by the `bamsormadup` command using `strace`
within the run-unit-test script, and it turned out the program
was searching for a libz.so library.

After appending the zlib1g-dev package to dependencies of the
biobambam2 package, the autopkgtest suite fully executes without
errors.  Changes are pushed on Salsa, available for review:

https://salsa.debian.org/med-team/biobambam2

As a side note I also updated the package to version 2.0.173, as
it has been released lately, and cleaned an informational entry
that was showing up in lintian.  This should also unblock and
resolve #966472; should it be mentioned through a "Closes"
statement in the changelog ?

Kind Regards,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/3, please excuse my verbosity.


signature.asc
Description: PGP signature

Processed: fix for #966470: biobambam2 autopkgtest failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #966470 [biobambam2] biobambam2: autopkgtest failures: Segmentation fault 
bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
Added tag(s) pending.

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

Bug#967150: closed by Debian FTP Masters (reply to tony mancill ) (Bug#967150: fixed in jython 2.7.2+repack1-2)

[tony mancill]

Hi Gilles,

On Wed, Aug 05, 2020 at 11:36:05PM +, Debian Bug Tracking System wrote:

> Date: Wed, 05 Aug 2020 16:01:50 -0700
> Source: jython
> Architecture: source
> Version: 2.7.2+repack1-2
> Distribution: experimental
> Urgency: medium
> Maintainer: Debian Java Maintainers 
> 
> Changed-By: tony mancill 
> Closes: 936776 967150
> Changes:
>  jython (2.7.2+repack1-2) experimental; urgency=medium
>  .
>* Team upload
>* Update build dependencies for python 3 (Closes: #936776, #967150)
>* Upload to experimental to give users a chance to test.

Regarding my recent upload of jython, do you have any concerns with me
uploading it to unstable?

I initially uploaded to experimental because it felt odd to build a
package that implements a Python2 runtime using Python3, but I realize
now that it's not odd and I was just being silly.  The build toolchain
version of Python isn't tied to the jython implementation.

The package in experimental functions as an interactive Python
interpreter - i.e., it passes a smoke test.  Do you have suggestions for
a more comprehensive set of tests before uploading?

Thank you,
tony


signature.asc
Description: PGP signature

Processed: bug 966904 is forwarded to https://sourceforge.net/p/pfstools/bugs/48/

[Debian Bug Tracking System]

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

> forwarded 966904 https://sourceforge.net/p/pfstools/bugs/48/
Bug #966904 [src:pfstools] pfstools: FTBFS: array2d.h:173:9: error: 
‘__assert_fail’ was not declared in this scope; did you mean 
‘MagickCore::__assert_fail’?
Set Bug forwarded-to-address to 'https://sourceforge.net/p/pfstools/bugs/48/'.
> thanks
Stopping processing here.

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

Bug#963396: marked as done (jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 15:48:41 +
with message-id 
and subject line Bug#963396: fixed in jimfs 1.1-6
has caused the Debian Bug report #963396,
regarding jimfs: FTBFS: [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) 
on project jimfs: Compilation failure
to be marked as done.

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

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


-- 
963396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jimfs
Version: 1.1-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -d 0755 jimfs/target/classes/META-INF/services/
> echo com.google.common.jimfs.SystemJimfsFileSystemProvider \
>   > 
> jimfs/target/classes/META-INF/services/java.nio.file.spi.FileSystemProvider
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [WARNING] The project com.google.jimfs:jimfs-parent:pom:1.1 uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Jimfs Parent   
> [pom]
> [INFO] Jimfs   
> [bundle]
> [WARNING] The POM for org.apache.maven.plugins:maven-gpg-plugin:jar:1.4 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-gpg-plugin:1.4: Plugin 
> org.apache.maven.plugins:maven-gpg-plugin:1.4 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-gpg-plugin:jar:1.4 has not been downloaded 
> from it before.
> [WARNING] The POM for org.apache.maven.plugins:maven-gpg-plugin:jar:1.4 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-gpg-plugin:1.4: Plugin 
> org.apache.maven.plugins:maven-gpg-plugin:1.4 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-gpg-plugin:jar:1.4 has not been downloaded 
> from it before.
> [INFO] 
> [INFO] ---< com.google.jimfs:jimfs-parent 
> >
> [INFO] Building Jimfs Parent 1.1  
> [1/2]
> [INFO] [ pom 
> ]-
> [WARNING] The POM for org.apache.maven.plugins:maven-gpg-plugin:jar:1.4 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-gpg-plugin:1.4: Plugin 
> org.apache.maven.plugins:maven-gpg-plugin:1.4 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the 

Processed: Debian bugs #958005

[Debian Bug Tracking System]

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

> forwarded 958005 https://sourceforge.net/p/xtrkcad-fork/bugs/390/
Bug #958005 [src:xtrkcad] xtrkcad: ftbfs with GCC-10
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/xtrkcad-fork/bugs/390/'.
> --
Stopping processing here.

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

Bug#966787: marked as done (redland-bindings: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 15:22:31 +
with message-id 
and subject line Bug#966787: fixed in redland-bindings 1.0.17.1+dfsg-1.4
has caused the Debian Bug report #966787,
regarding redland-bindings: Unversioned Python 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.)


-- 
966787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:redland-bindings
Version: 1.0.17.1+dfsg-1.3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: redland-bindings
Source-Version: 1.0.17.1+dfsg-1.4
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated redland-bindings 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, 08 Aug 2020 16:54:36 +0200
Source: redland-bindings
Architecture: source
Version: 1.0.17.1+dfsg-1.4
Distribution: unstable
Urgency: medium
Maintainer: Dave Beckett 
Changed-By: Matthias Klose 
Closes: 966787
Changes:
 redland-bindings (1.0.17.1+dfsg-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * python-librdf: Don't hard-code python. Closes: #966787.
Checksums-Sha1:
 053b0d3cd0a29cd29af6387a9bce201751c5304b 2184 
redland-bindings_1.0.17.1+dfsg-1.4.dsc
 869e88fc18b8bdf17edf8016065fbe0bf8c4cc5a 6560 
redland-bindings_1.0.17.1+dfsg-1.4.debian.tar.xz
 a8d222e6d7e05edac8f5d9c8bac53092ad82450c 6525 
redland-bindings_1.0.17.1+dfsg-1.4_source.buildinfo
Checksums-Sha256:
 49807df671efe8ce6df57eb3e33e786319d40570be67af263181054ccda3b09a 2184 
redland-bindings_1.0.17.1+dfsg-1.4.dsc
 3650d8ca3f32cc24e1c5df2525c0dc29c2cbba6c8e7670aec71f8cd737ab10b0 6560 
redland-bindings_1.0.17.1+dfsg-1.4.debian.tar.xz
 876e147ec145f5dce4beef3867b722b68cab398e20d789033e8cc5e62b99df14 6525 
redland-bindings_1.0.17.1+dfsg-1.4_source.buildinfo
Files:
 124cc67dd1ba2ff556d975556c465120 2184 devel optional 
redland-bindings_1.0.17.1+dfsg-1.4.dsc
 f53e6f63869c30258c76f578eeef0c9b 6560 devel optional 
redland-bindings_1.0.17.1+dfsg-1.4.debian.tar.xz
 3a2fc2fdadd15841c6690c0f5fa2f6e8 6525 devel optional 
redland-bindings_1.0.17.1+dfsg-1.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8uvQgQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9bxkD/9klTHzq8JxUaIhFxJlIrT3XmNteID5UMJo
UBFLZLb0tR5P9Hcom9ZxxBJ0gQGJ3SgTsaj1P9QsTBuj7gGBnfjGpht0iQyBou+S
rteSp0riymTUe3qBi0TYXHmYjXzsj6A9gtryjPDFHot/7CprLdU4HbWar3dQ7DPr
V0/puO4YPsN/qTpp200VdjE6FBc3sy/X5fju3VCvopWIkZjZr+wmPQdF99gigpFo
iBzqeAg2Fw5acAQyIlSBuO0AeGl0uUCEoK1LAUWyyN5UJ7l6PeE/ZeDhTiS0zEKO
lz3vi0xw6Q1zNFBnRNY/wl0O3BiTrflPfNrnlK0qoe+UPnVe/CC+FDBhzHy5NLfw
/0cnNFxw8dI3U8CbixAY9WqFYxWgSHNgVVQlvYQrCrYtlY5jJ/d1FazwVas2KHXe
6wZVcvmLABTsTf2NiB1wR3No/l89G4mKnOBcv3z9Zf9CyUvoMmPLUiHlGtuGF7pt
6guHSXPSGI6EjGWza8g1qNu5+DewvTaSKqYpcQVvRrn+JQ9p/p6wdmCatCYOz2h8
pExiHOUON8HLfHEuQ6J7OyEqZ1VUiytLRwgXkm28gu/2ENGTITfvQIzvsrYNoNDN

Bug#966740: marked as done (giella-core: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 15:03:32 +
with message-id 
and subject line Bug#966740: fixed in giella-core 0.1.1~r129227+svn121148-2.1
has caused the Debian Bug report #966740,
regarding giella-core: Unversioned Python 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.)


-- 
966740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:giella-core
Version: 0.1.1~r129227+svn121148-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: giella-core
Source-Version: 0.1.1~r129227+svn121148-2.1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated giella-core 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, 08 Aug 2020 16:46:10 +0200
Source: giella-core
Architecture: source
Version: 0.1.1~r129227+svn121148-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Matthias Klose 
Closes: 966740
Changes:
 giella-core (0.1.1~r129227+svn121148-2.1) unstable; urgency=medium
 .
   * Non-maintianer upload.
   * Build using python2. Closes: #966740.
Checksums-Sha1:
 528859f19da218d4ece080715bc2a8f3a6a15445 2165 
giella-core_0.1.1~r129227+svn121148-2.1.dsc
 4414fe978a3bcfdfac6074d2607c42f9b3474eb0 3052 
giella-core_0.1.1~r129227+svn121148-2.1.debian.tar.xz
 4624eb44e59c12469c1e734ddaf8b275bf18ec4c 6507 
giella-core_0.1.1~r129227+svn121148-2.1_source.buildinfo
Checksums-Sha256:
 5d166ab6be0552651852c8e6c1a66ab6ed06a64222ffaca1c3c702673ac1e39c 2165 
giella-core_0.1.1~r129227+svn121148-2.1.dsc
 640e3683ed1a1cbee3c138342bbbdd48388522c008f749323167c56ffdd43bf2 3052 
giella-core_0.1.1~r129227+svn121148-2.1.debian.tar.xz
 9169746535abbb0188250e8c29261d9e955bc9303160e9971c8fac9177a90178 6507 
giella-core_0.1.1~r129227+svn121148-2.1_source.buildinfo
Files:
 f196027fc1cb62759d120ab0f3fa23e2 2165 science optional 
giella-core_0.1.1~r129227+svn121148-2.1.dsc
 fac00418305b62a6c01e282db89e5cd0 3052 science optional 
giella-core_0.1.1~r129227+svn121148-2.1.debian.tar.xz
 2d2727661a4b626f025e7a6ff11d96c9 6507 science optional 
giella-core_0.1.1~r129227+svn121148-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8uuyUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9V50D/9y/gKa4yA+K273guzPY2fEcbCDNo9LpnkA
Er56D5EzPMJtGxK6n4BG3iNhw9WSSfUehyXZ4GvQhhM9FvOmQooxFrakK781zIws
OZEpAxt2ced252zl345zUnnMucEnUOd34RKsW+jj//m2ti+VHvoq4kKdNUG9c/aY
N2xWEqSJDOqEVOByrbRyWSR8mvvw6HA82+EArB4sUHdLnhh+di4D/IWOw62S8Qwk
qaIxlMMhjRtgkkTLtTwLo2Dk7uAVam/TVqamDaeByQfV3DGsXKZKhv3QWnbVbxqZ
9AFcGctejXA03Tx7NkGoYfcBOqnx+DAYWaJC7JvqtLM/ie4x5Eet6WZD5fjE1odY
lA+R389VbTjkWuBINlfkTjrrEqcFTOSiJL6tsRHTPG6D2jNST6I/ZZSlWUiAmOq2
0B5jg3cQ87fP8/jQz+K2LRBfYd7Oja5fuj6So4ofNMbHoB1ctCQYO/GWZhNGMqyz
GJ+LZhFdSLe39Pg3V74jhXjyXbeCuBj6yJTwEm7lAbodafs1v8MTQZ/DJ1FdpuHi

Bug#964686: marked as done (node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 14:35:58 +
with message-id 
and subject line Bug#964637: fixed in typescript-types 20200808-1
has caused the Debian Bug report #964637,
regarding node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh 
-ex ../debian/nodejs/m3u8stream/build returned exit code 2
to be marked as done.

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

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


-- 
964637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-ytdl-core
Version: 2.1.3+dfsg+~cs2.16.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-ytdl-core
> dpkg-buildpackage: info: source version 2.1.3+dfsg+~cs2.16.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>   rm -rf html-entities/node_modules/.cache
>   rm -rf m3u8stream/node_modules/.cache
>   rm -rf miniget/node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-ytdl-core using existing 
> ./node-ytdl-core_2.1.3+dfsg+~cs2.16.2.orig-html-entities.tar.xz
> dpkg-source: info: building node-ytdl-core using existing 
> ./node-ytdl-core_2.1.3+dfsg+~cs2.16.2.orig-m3u8stream.tar.xz
> dpkg-source: info: building node-ytdl-core using existing 
> ./node-ytdl-core_2.1.3+dfsg+~cs2.16.2.orig-miniget.tar.xz
> dpkg-source: info: building node-ytdl-core using existing 
> ./node-ytdl-core_2.1.3+dfsg+~cs2.16.2.orig.tar.xz
> dpkg-source: info: building node-ytdl-core in 
> node-ytdl-core_2.1.3+dfsg+~cs2.16.2-1.debian.tar.xz
> dpkg-source: info: building node-ytdl-core in 
> node-ytdl-core_2.1.3+dfsg+~cs2.16.2-1.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>   mkdir node_modules
>   mkdir -p ./node_modules/\@types
>   ln -s /usr/share/nodejs/\@types/node ./node_modules/\@types/
>   ln -s ../html-entities node_modules/html-entities
>   ln -s ../m3u8stream node_modules/m3u8stream
>   ln -s ../miniget node_modules/miniget
>   mkdir -p m3u8stream/node_modules
>   ln -s ../../miniget m3u8stream/node_modules/miniget
>   ln -s ../../debian/build_modules/\@types/sax node_modules/\@types/sax
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> Found debian/nodejs/miniget/build
>   cd ./miniget && sh -ex ../debian/nodejs/miniget/build
> + set -e
> + set -x
> + mkdir -p node_modules/@types
> + ln -s ../../../debian/build_modules/@types/sax node_modules/@types/sax
> + tsc -p tsconfig.build.json
> + rm -rf node_modules
> Found debian/nodejs/m3u8stream/build
>   cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build
> + set -e
> + set -x
> + mkdir -p node_modules/@types
> + ln -s ../../../debian/build_modules/@types/sax node_modules/@types/sax
> + tsc -p tsconfig.build.json
> src/dash-mpd-parser.ts(187,31): error TS2769: No overload matches this call.
>   Overload 1 of 2, '(chunk: any, cb?: (error: Error) => void): boolean', gave 
> the following error.
> Argument of type 'string' is not assignable to parameter of type '(error: 
> Error) => void'.
>   Overload 2 of 2, '(chunk: any, encoding: BufferEncoding, cb?: (error: 
> Error) => void): boolean', gave the following error.
> Argument of type 'string' is not assignable to parameter of type 
> 'BufferEncoding'.
> dh_auto_build: error: cd ./m3u8stream && sh -ex 
> ../debian/nodejs/m3u8stream/build returned exit code 2
> make: *** [debian/rules:8: binary] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/07/09/node-ytdl-core_2.1.3+dfsg+~cs2.16.2-1_unstable.log

A list of current common problems and possible soluti

Bug#964637: marked as done (node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 14:35:58 +
with message-id 
and subject line Bug#964637: fixed in typescript-types 20200808-1
has caused the Debian Bug report #964637,
regarding node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex 
debian/nodejs/./build returned exit code 1
to be marked as done.

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

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


-- 
964637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup
Version: 1.12.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-rollup
> dpkg-buildpackage: info: source version 1.12.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>   rm -rf turbocolor/node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-rollup using existing 
> ./node-rollup_1.12.0.orig-turbocolor.tar.gz
> dpkg-source: info: building node-rollup using existing 
> ./node-rollup_1.12.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-rollup in node-rollup_1.12.0-2.debian.tar.xz
> dpkg-source: info: building node-rollup in node-rollup_1.12.0-2.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>   mkdir node_modules
>   ln -s /usr/share/nodejs/acorn ./node_modules/
>   ln -s /usr/share/nodejs/chalk ./node_modules/
>   ln -s /usr/share/nodejs/chokidar ./node_modules/
>   ln -s /usr/share/nodejs/estree-walker ./node_modules/
>   ln -s /usr/share/nodejs/immutable ./node_modules/
>   ln -s /usr/share/nodejs/magic-string ./node_modules/
>   ln -s /usr/share/nodejs/micromatch ./node_modules/
>   ln -s /usr/share/nodejs/pretty-ms ./node_modules/
>   ln -s /usr/share/nodejs/rollup-pluginutils ./node_modules/
>   ln -s /usr/share/nodejs/source-map ./node_modules/
>   ln -s ../turbocolor node_modules/turbocolor
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> Found debian/nodejs/./build
>   cd ./. && sh -ex debian/nodejs/./build
> + mkdir -p node_modules
> + mkdir -p node_modules/@types
> + ln -s /usr/share/nodejs/@types/chokidar node_modules/@types
> + ln -s /usr/share/nodejs/@types/minimist node_modules/@types
> + ln -s /usr/share/nodejs/@types/pretty-ms node_modules/@types
> + ln -s /usr/share/nodejs/@types/node node_modules/@types
> + ln -s /usr/share/nodejs/@types/estree node_modules/@types
> + tsc --esModuleInterop
> src/watch/fileWatchers.ts:89:34 - 
> error TS2769: No overload matches this call.
>   Overload 1 of 4, '(filename: PathLike, options: "hex" | "ascii" | "utf8" | 
> "utf-8" | "utf16le" | "ucs2" | "ucs-2" | "base64" | "latin1" | "binary" | { 
> encoding?: BufferEncoding; persistent?: boolean; recursive?: boolean; }, 
> listener?: (event: string, filename: string) => void): FSWatcher', gave the 
> following error.
> Argument of type '{ encoding: string; persistent: boolean; }' is not 
> assignable to parameter of type '"hex" | "ascii" | "utf8" | "utf-8" | 
> "utf16le" | "ucs2" | "ucs-2" | "base64" | "latin1" | "binary" | { encoding?: 
> BufferEncoding; persistent?: boolean; recursive?: boolean; }'.
>   Type '{ encoding: string; persistent: boolean; }' is not assignable to 
> type '{ encoding?: BufferEncoding; persistent?: boolean; recursive?: boolean; 
> }'.
> Types of property 'encoding' are incompati

Bug#961224: marked as done (python-cobra: test failures on s390x)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 14:35:46 +
with message-id 
and subject line Bug#961224: fixed in python-cobra 0.18.1-2
has caused the Debian Bug report #961224,
regarding python-cobra: test failures on s390x
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.)


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

Source: python-cobra
Version: 0.18.0-1
Severity: serious

Three of the last four builds of python-cobra on s390x have failed with.


=== FAILURES ===
___ test_model_summary_to_frame_with_fva[optlang-glpk-0.95] 

model = , opt_solver = 'optlang-glpk'
fraction = 0.95

 @pytest.mark.parametrize("fraction", [0.95])
 def test_model_summary_to_frame_with_fva(model, opt_solver, fraction):
 """Test model summary.to_frame() (using FVA)."""
 if opt_solver == "optlang-gurobi":
 pytest.xfail("FVA currently buggy")
 # test non-fva version (these should be fixed for textbook model)
 expected_in_fluxes = ['o2_e', 'glc__D_e', 'nh4_e', 'pi_e', np.nan,
   np.nan, np.nan, np.nan, np.nan, np.nan, np.nan,
   np.nan]
 expected_out_fluxes = ['h2o_e', 'co2_e', 'h_e', 'for_e', 'ac_e', 
'acald_e',
'pyr_e', 'etoh_e', 'lac__D_e', 'succ_e', 
'akg_e',
'glu__L_e']
 
 model.solver = opt_solver

 solution = model.optimize()
 out_df = model.summary(solution, fva=fraction).to_frame()
 
 assert out_df[('IN_FLUXES', 'ID')].tolist() == expected_in_fluxes

>   assert out_df[('OUT_FLUXES', 'ID')].tolist() == expected_out_fluxes
E   AssertionError: assert ['h2o_e', 'co... 'pyr_e', ...] == ['h2o_e', 
'co2...acald_e', ...]
E At index 5 diff: 'pyr_e' != 'acald_e'
E Use -v to get the full diff


--- End Message ---
--- Begin Message ---
Source: python-cobra
Source-Version: 0.18.1-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-cobra 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, 08 Aug 2020 14:59:14 +0200
Source: python-cobra
Architecture: source
Version: 0.18.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 961224
Changes:
 python-cobra (0.18.1-2) unstable; urgency=medium
 .
   * Exclude s390x from list of architectures since one test of the test
 suite fails on this architecture and there are no resources to track
 this down.
 Closes: #961224
Checksums-Sha1:
 b89855092aa8ab7bacd4db20b9bcc2b86c2dfc0b 2927 python-cobra_0.18.1-2.dsc
 bf138cbfa7e681affdee4d6f6a1f0b9babe88e9e 7856 
python-cobra_0.18.1-2.debian.tar.xz
 5ca0d5e762a7a0dce21dfccfa971b9c3a3b5bdd2 9646 
python-cobra_0.18.1-2_amd64.buildinfo
Checksums-Sha256:
 80e8633e7e8fdac783a38db94724b34d138525cf0ba1223f996482d526dc81b5 2927 
python-cobra_0.18.1-2.dsc
 524f1e3f4a7de9d652fd24b4cd0579e5cd0e816e9130c136c998b717c42ee517 7856 
python-cobra_0.18.1-2.debian.tar.xz
 f3f7749259a2f49afaaf720992c9ddd52dafb11794802102664ca3cc0b513a03 9646 
python-cobra_0.18.1-2_amd64.buildinfo
Files:
 62e436d5ca806619b249e8f29eadd6d1 2927 python optional python-cobra_0.18.1-2.dsc
 5c8be7d6e4af7cba7f40545c30f1c1e9 7856 python optional 
python-cobra_0.18.1-2.debian.tar.xz
 00a4606f3babffce51403dee4f86f558 9646 python optional 
python-cobra_0.18.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8urkoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFRRRAAg0JuZ2PFVDkfatYr3wBuN+s2J8ByDhm8
9mQQ/6cXQH9VtArHr3WJmonjHFPjh4IKPjs+Ohjb2R7LRwjAFdlCnlog98Tn6fzE
ixNFR6GTzdVIa5UZFXld9BbntswPDJZLLyIYx7m1YIES9OMXqJc4ld7fXjtSnpGl
yTiynhPTSveeBkqfCCEwgJHoFvNY92dUh3MBA71LevlN7nl2mEYMjXtUY9+52bMS

Bug#964637: marked as pending in typescript-types

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #964637 in typescript-types 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/js-team/typescript-types/-/commit/133f9971c44d6927bd5dd027483f785ed35801d9


Fix @types/node version

Closes: #964637


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964637

Processed: Bug#964637 marked as pending in typescript-types

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964637 [node-typescript-types] node-rollup: FTBFS: dh_auto_build: error: 
cd ./. && sh -ex debian/nodejs/./build returned exit code 1
Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: 
error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned 
exit code 2
Added tag(s) pending.
Added tag(s) pending.

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

Bug#961224: python-cobra: test failures on s390x

[Andreas Tille]

Hi,

On Sat, May 23, 2020 at 02:56:22PM +0300, Adrian Bunk wrote:
> [ debian-s390 added ]
> 
> On Thu, May 21, 2020 at 05:03:19PM +0100, peter green wrote:
> > Source: python-cobra
> > Version: 0.18.0-1
> > Severity: serious
> > 
> > Three of the last four builds of python-cobra on s390x have failed with.
> > 
> > > === FAILURES 
> > > ===
> > > ___ test_model_summary_to_frame_with_fva[optlang-glpk-0.95] 
> > > 
> > > 
> > > model = , opt_solver = 'optlang-glpk'
> > > fraction = 0.95
> > > 
> > >  @pytest.mark.parametrize("fraction", [0.95])
> > >  def test_model_summary_to_frame_with_fva(model, opt_solver, 
> > > fraction):
> > >  """Test model summary.to_frame() (using FVA)."""
> > >  if opt_solver == "optlang-gurobi":
> > >  pytest.xfail("FVA currently buggy")
> > >  # test non-fva version (these should be fixed for textbook model)
> > >  expected_in_fluxes = ['o2_e', 'glc__D_e', 'nh4_e', 'pi_e', 
> > > np.nan,
> > >np.nan, np.nan, np.nan, np.nan, np.nan, 
> > > np.nan,
> > >np.nan]
> > >  expected_out_fluxes = ['h2o_e', 'co2_e', 'h_e', 'for_e', 'ac_e', 
> > > 'acald_e',
> > > 'pyr_e', 'etoh_e', 'lac__D_e', 'succ_e', 
> > > 'akg_e',
> > > 'glu__L_e']
> > >  model.solver = opt_solver
> > >  solution = model.optimize()
> > >  out_df = model.summary(solution, fva=fraction).to_frame()
> > >  assert out_df[('IN_FLUXES', 'ID')].tolist() == expected_in_fluxes
> > > >   assert out_df[('OUT_FLUXES', 'ID')].tolist() == 
> > > > expected_out_fluxes
> > > E   AssertionError: assert ['h2o_e', 'co... 'pyr_e', ...] == 
> > > ['h2o_e', 'co2...acald_e', ...]
> > > E At index 5 diff: 'pyr_e' != 'acald_e'
> > > E Use -v to get the full diff
> > 
> 
> Can an s390x porter please have a look?

The issue remains in next upstream version.  I will exclude s390x from
the list of architectures since it seems nobody manages to care for this
issue.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#967032: marked as done (nodejs: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 12:33:28 +
with message-id 
and subject line Bug#967032: fixed in nodejs 12.18.3~dfsg-4
has caused the Debian Bug report #967032,
regarding nodejs: Unversioned Python 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.)


-- 
967032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nodejs
Version: 12.18.2~dfsg-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

see https://ci.debian.net/data/autopkgtest/testing/amd64/n/nodejs/6517579/log.gz

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: nodejs
Source-Version: 12.18.3~dfsg-4
Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= 

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Aug 2020 14:09:43 +0200
Source: nodejs
Architecture: source
Version: 12.18.3~dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 967032
Changes:
 nodejs (12.18.3~dfsg-4) unstable; urgency=medium
 .
   * python3 patch: use env.PYTHON in two tests
 Closes: #967032 for good.
Checksums-Sha1:
 ddad6719c9611d933d8e2d6582e6bf920bbe4cbe 3161 nodejs_12.18.3~dfsg-4.dsc
 cbd3abdb3bdae33e202d8455ee36acf6084ada67 132852 
nodejs_12.18.3~dfsg-4.debian.tar.xz
 17fb444f739419e3b340176c5e0d4d7d8fa0d8d5 9056 
nodejs_12.18.3~dfsg-4_source.buildinfo
Checksums-Sha256:
 2c448156fac5c3952f82bb738c85240c630f1f198427ab81d6b6fd56db5acb6a 3161 
nodejs_12.18.3~dfsg-4.dsc
 f7c9b1989f0cbc09d41eca2a5d3f960c8f09c08cc862f962c5b3cfd13cb6f48f 132852 
nodejs_12.18.3~dfsg-4.debian.tar.xz
 a72dc9deedd582d12ae2bfda3096429a563aef17d77d77e53b8d7f5c7211383f 9056 
nodejs_12.18.3~dfsg-4_source.buildinfo
Files:
 f586f97fc8cc6605ef43bef9e569ff5f 3161 javascript optional 
nodejs_12.18.3~dfsg-4.dsc
 2cc38968246915055da49693d9be3caf 132852 javascript optional 
nodejs_12.18.3~dfsg-4.debian.tar.xz
 f0826c72bdb108b1f30a6a7251d41fa7 9056 javascript optional 
nodejs_12.18.3~dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl8ulhwSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN03LsP+gNWgZPngc9ya/ctDsa4iwb/3f5RjG89
NaMkFJg/qJSEFjNCOUpAR2W53N/sTlMUXooUOYV9RlUEPg3qv3t4dpx1kuyJEiPX
x1MZjttR4yFUlWLMNARa2AHwF0W3A1IikGUM6cGJ5UOOOaKPXgZA73/6tR4pBY9y
psB2QyCI5TT2guOReDtciO45N8f4jNtlMaKtb6nb66PJycm7BhA5MGjSm2Ivkhih
b3u81+gZi2gRUsbJokjEpxwHqg0FzbTcObReeWt99F3QWSIi37OMgAEXckWjFG4y
aD/vemws3X7uvhp74GdxaDWML/Am4N1OGZ+BbwhLoalmp7DP6q2gWd1no45DOcsd
+vMKRAKeLxs0XZJlAjvCp3BgzRqfRbn2x0YipL7CHiOxknksH6+niuLLyA4BtGYZ
0JNxL/ryis4NLi9zIA3pRnvADbzcBDo1z/4zhbSOkDj56VG9ppfAVRlYDZ+OvsMz
du/BoXPVa6JqPYn0H+KLXbO9efC0DINYG4okQvdwUPKcNCsEosBFV5ZKh4phQowA
8hOuT4oHtaWe3owYcqEdLPvAvqwFxGLpWKLkkybEJxcvhhTO8YNDPzlxWh2T1ZKb
Ed3CzBQhJWBq4a3og7tjt6Tos0bs5ukXHSTCNeRp/XH94FZOS3XFrAwq7WzjpOAi
mZrhc/gDue5w
=3cXm
-END PGP 

Bug#968079: [Python-modules-team] Bug#968079: libapache2-mod-wsgi: Package is not installable. Needs older Python2.

[Emmanuel Arias]

Hi,

That problem seems to be fixed on salsa, but I am
waiting for a review.

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El sáb., 8 de ago. de 2020 a la(s) 04:15, greylistd Python issue
(n...@dagami.org) escribió:
>
> Package: libapache2-mod-wsgi
> Version: 4.6.8-1+b1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> When trying to install the package, the following message is displayed:
>
> == begin 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to be 
> installed
>   Depends: libpython-stdlib (= 2.7.17-2) but it is not going to be 
> installed
>   Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> ==  end  
> The problem is that my Python2 is:
> python22.7.18-2 amd64
>
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to fr_FR.UTF-8), LANGUAGE=en_US:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages libapache2-mod-wsgi depends on:
> ii  apache2-bin [apache2-api-20120211]  2.4.43-1
> ii  libc6   2.31-3
> ii  libpython2.72.7.18-1
> pn  python  
>
> libapache2-mod-wsgi recommends no packages.
>
> libapache2-mod-wsgi suggests no packages.
>
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Bug#957230: Bug#966370: bsdmainutils: 12.1.3 removal of lorder breaks rdeps

[Michael Meskes]

> > I'm surprised it is actually used as it was pointed out to me that
> > the script
> > has been non-functional for quite a while.
> 
> I do recall having an issue with it at one point a few years back and
> meaning to submit a patch to bsdmainutils to fix it, but resolved it
> one way or another without that, though can't find any evidence of
> that
> nor can I remember what the problem was. But regardless, it was
> working
> well enough for the freebsd-* packages to build fine.

My guess would be that its functionality is not needed at all.

> > Anyway, it cannot easily be "restored"
> > because the old bsdmainutils package does not exist anymore. All
> > tools except
> > ncal and calendar, which are now in their own package, are now
> > build out of
> > util-linux. Would it be possible to include lorder.sh in one of the
> > affected
> > freebsd packages?
> 
> Yeah, it's possible, and that's no doubt what I'll end up doing. But
> I

I'm glad you agree, I will therefore close this bug.

> really don't appreciate all the breakage that's come about from
> bsdmainutils in the past few months. The util-linux handover was

Pas few months is a slight exaggeration but whatever.

> poorly-handled causing all kinds of problems across the archives

It is well documented that the changes caused more issues than
expected, but all packages received the necessary fixes as quickly as
possible. Having to go through NEW certainly caused some delay, too,
but again stuff like this happens, it's called unstable for a reason.

> (release and ports), and this removal of something, and thus
> *deliberately breaking* the package's "API", should have been done
> more
> carefully by checking whether anyone is actually using it (archive-
> wide
> rebuilds like is done for the new GCC versions is the
> easy-but-computationally-expensive way to do it). As it stands, I got

Come again please? Is this a joke or are you really suggesting we
should rebuild the whole archive to figure out if any package still
uses a non-functional tool in its build process?

> hit with a surprise set of RC bugs from the first archive-wide
> rebuild
> after this change landed, and I therefore have to react in a
> time-pressured way to fix it lest packages be removed from testing
> (though, arguably, testing doesn't matter so much for these given
> kfreebsd-* aren't release architectures). This really should have 

So why do you bring up this point then?

> been
> found out first, with Severity: important bugs filed a month or more
> in
> advance of making the change, that can then be upgraded to be
> release-critical further down the line. So, please, never do a
> transition like this again.

Just for the record, I do not consider removing lorder.sh a transition
of any kind. Nor do I think removing a faulty tool that apparently had
no real functionality anymore warrants the kind of lecture you're
giving me.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org

Processed: affects 964686

[Debian Bug Tracking System]

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

> affects 964686 node-ytdl-core
Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: 
error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned 
exit code 2
Bug #964637 [node-typescript-types] node-rollup: FTBFS: dh_auto_build: error: 
cd ./. && sh -ex debian/nodejs/./build returned exit code 1
Added indication that 964686 affects node-ytdl-core
Added indication that 964637 affects node-ytdl-core
> thanks
Stopping processing here.

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

Processed: affects 964637

[Debian Bug Tracking System]

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

> affects 964637 rollup
Bug #964637 [node-typescript-types] node-rollup: FTBFS: dh_auto_build: error: 
cd ./. && sh -ex debian/nodejs/./build returned exit code 1
Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: 
error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned 
exit code 2
Added indication that 964637 affects rollup
Added indication that 964686 affects rollup
> thanks
Stopping processing here.

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

Processed: raise severity

[Debian Bug Tracking System]

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

> severity 953006 serious
Bug #953006 [dbacl] Switch to current libreadline
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: reassign 964686 to node-typescript-types, forcibly merging 964686 964637

[Debian Bug Tracking System]

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

> reassign 964686 node-typescript-types
Bug #964686 [src:node-ytdl-core] node-ytdl-core: FTBFS: dh_auto_build: error: 
cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned exit code 2
Bug reassigned from package 'src:node-ytdl-core' to 'node-typescript-types'.
No longer marked as found in versions node-ytdl-core/2.1.3+dfsg+~cs2.16.2-1.
Ignoring request to alter fixed versions of bug #964686 to the same values 
previously set
> forcemerge 964686 964637
Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: 
error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned 
exit code 2
Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: 
error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned 
exit code 2
Added tag(s) experimental.
Bug #964637 [node-typescript-types] node-rollup: FTBFS: dh_auto_build: error: 
cd ./. && sh -ex debian/nodejs/./build returned exit code 1
Removed indication that 964637 affects rollup
Merged 964637 964686
> thanks
Stopping processing here.

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

Bug#964611: [Pkg-pascal-devel] Bug#964611: libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Abou Al Montacir]

Hi Paul,

On Fri, 2020-08-07 at 19:55 +0200, Paul Gevers wrote:
> Hi,
> I am preparing an upload with the symbols file removed as there seems tobe
> consensus that using symbols files for C++ projects in Debian isn'tworth the
> effort.

It will probably require to use 2.0.10 based libQtPas, as I' uploaded both FPC
and Lazarus. So 2.0.8 based one will not build anymore.
-- 
Cheers,
Abou Al Montacir


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

Bug#946046: marked as done (unison-all should also depend on the old unison version, compatible with Debian 10)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 10:33:55 +
with message-id 
and subject line Bug#946046: fixed in meta-unison 2.48.4+3
has caused the Debian Bug report #946046,
regarding unison-all should also depend on the old unison version, compatible 
with Debian 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.)


-- 
946046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unison-all
Version: 2.48+2
Severity: grave
Justification: renders package unusable

The purpose of unison-all is the following (see the latest sentence
in particular):

Description: file synchronization tool (all console versions)
 This is a metapackage that depends on all supported console versions
 of Unison, a file synchronization tool.
 .
 Each of the supported versions uses a different protocol version;
 installing this metapackage ensures the ability to synchronize with
 old systems.

But it currently depends only on unison, which is no longer compatible
with Debian 10 (buster), i.e. the current Debian/stable.

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

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

Versions of packages unison-all depends on:
ii  unison  2.48.4-1+b1

unison-all recommends no packages.

unison-all suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: meta-unison
Source-Version: 2.48.4+3
Done: =?utf-8?q?St=C3=A9phane_Glondu?= 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated meta-unison package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Aug 2020 12:01:50 +0200
Source: meta-unison
Architecture: source
Version: 2.48.4+3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 946046
Changes:
 meta-unison (2.48.4+3) unstable; urgency=medium
 .
   * Remove -all packages (Closes: #946046)
Checksums-Sha1:
 53f8b5ccaa175a32f1171bc55410864d5d278f34 1479 meta-unison_2.48.4+3.dsc
 b86eba1527cb4ddc59f4c6e2e04ce3a830deb735 2032 meta-unison_2.48.4+3.tar.xz
Checksums-Sha256:
 e1a12b31de4875b489fae35eb33ea0949f8c4fb31ffc29c5b925de91e53f5101 1479 
meta-unison_2.48.4+3.dsc
 4238f0b7266222dd28f8415885afd5c79685ea7a94b95acdca6caedbebb13fbc 2032 
meta-unison_2.48.4+3.tar.xz
Files:
 ebada0e08c662767250c2035260c8544 1479 metapackages optional 
meta-unison_2.48.4+3.dsc
 1fa78afad9d5d04439dd464d0d324442 2032 metapackages optional 
meta-unison_2.48.4+3.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl8ueQ4SHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCB3fkH/2+LuLHjHEPUcbXef7ZL8AXHQ8V8WluC
Se+Q+vN9p0oFb+815AXaOXYkPIpj5ZWDVwGD8sG7fT/4qefOYK8PSe6CfgV/IuOW
G5c2g8HKRs0Y7HQrz4sLBzU6C1XVNoHlp26iEPCxeDTDSDNE75YIVB5WMG0hlt4k
E72sdXXcwFmzUH9cSpuxVNjPo3RZzsPuA5hoR8KYfPZjxT+lXHBy19V0voTkd7km
j/waANAQK3vR86wZ+r10pQEiO5xpBo3wciLMp5O9j+gf0VSAzHv7xPa1+wdM540o
0aN7YcOalelxAEOch+WGI3ONEhZbEGaALZG66zZRG/C2hXqqf/P0bJI=
=y885
-END PGP SIGNATURE End Message ---

Processed: Bug#946046 marked as pending in meta-unison

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946046 [unison-all] unison-all should also depend on the old unison 
version, compatible with Debian 10
Added tag(s) pending.

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

Bug#946046: marked as pending in meta-unison

[Stéphane Glondu]

Control: tag -1 pending

Hello,

Bug #946046 in meta-unison 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/ocaml-team/meta-unison/-/commit/4984b3d51df5683035c5bcef6c9fb6a57dd8219e


Remove -all packages (Closes: #946046)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946046

Bug#946046: not fixed

[Vincent Lefevre]

On 2020-08-08 10:04:10 +0200, Stéphane Glondu wrote:
> I still think it is useful to have a unison 2.48 compiled with OCaml
> 4.08.1 around.

Perhaps, but you should make sure that this version cannot be used
together with buster's unison 2.48, because there are not compatible
and can corrupt archive files.

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

Bug#946046: not fixed

[Vincent Lefevre]

On 2020-08-08 09:53:21 +0200, Stéphane Glondu wrote:
> Le 08/08/2020 à 03:25, Vincent Lefevre a écrit :
> > The wontfix does not make any sense. The unison-all package is
> > described as follows:
> > 
> > Description: file synchronization tool (all console versions)
> >  This is a metapackage that depends on all supported console versions
> >  of Unison, a file synchronization tool.
> >  .
> >  Each of the supported versions uses a different protocol version;
> >  installing this metapackage ensures the ability to synchronize with
> >  old systems.
> > 
> > See the latest sentence. That's the *only* purpose of the unison-all
> > metapackage.
> 
> Ah right, the "ability to synchronize with old systems" is not correct
> and never will be.

This was correct in the past and really allowed me to have old unison
versions automatically installed. I suppose that either the unison
data formats in the protocol did not depend on the OCaml version at
that time, or it was not needed to rebuild the package after the
Debian release, so this was working in practice.

> For me, the purpose of unison-all is just to have all supported
> versions. For now, there is only one, but there could be many.

I think that this is of little interest if you can't guarantee
synchronization with the previous stable release at least (I
mean between 2 stable releases, or between the current stable
and unstable/testing).

> I accept this bug as an error in the description. Severity serious
> for this seems overreacted, don't you think?

I don't see this as an error in the description in the sense that
users probably installed unison-all to do synchronization between
2 releases, and starting with bullseye (currently unstable), this
is failing. This makes using this package useless, which is RC.

And note that worse than that, only the fact that trying to
synchronize with buster may currently corrupt the archive files
(as I could see). This requires the user to remove these files,
and though unison will not lose any data (in some sense) from a
state with no archive files, fixing the mess needs to be done
manually, and this can be difficult and take much time.

> > So, either you are able to fix the issue in some way via unison-all
> > (I can see only a rather ugly solution, though the end user would
> > not see the ugly part), or the issue cannot be fixed in a clean way,
> > and the unison-all package should just be removed from Debian as
> > being broken by design (co-instability of the stable versions and the
> > unstable version should be sufficient, without needing unison-all),
> > which is probably the easiest was to fix this bug.
> 
> So you think that having a metapackage just to install all supported
> versions is useless? Or even misleading? Then, I will remove unison-all
> and unison-all-gtk.

Yes, this is really misleading. While "ensures the ability to
synchronize with old systems" is clear enough (if it works), the
notion of "supported versions" is confusing, because the user will
have to ask himself whether this means he can synchronize with
older systems. It is better to document in the default package for
the current distribution that if the user wishes to synchronize
with an older distribution, he will have to install the version
from this distribution if it is different (the version being
composed of the version of the unison source and the version of
OCaml used to build unison).

Note: This applies between 2 Debian distributions, which is rather
easy via /etc/apt/sources.list, and with a non-Debian distribution,
the user will have to find a working pair of binaries anyway.

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

Processed: Re: catimg: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #957066 [src:catimg] catimg: ftbfs with GCC-10
Added tag(s) fixed-upstream.
> tags -1 patch
Bug #957066 [src:catimg] catimg: ftbfs with GCC-10
Added tag(s) patch.

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

Bug#957066: catimg: ftbfs with GCC-10

[Étienne Mollier]

Control: tags -1 fixed-upstream
Control: tags -1 patch

Greetings,

The "master" branch of the upstream repository has a change that
includes a fix for the failure to build from source with Gcc 10:


https://github.com/posva/catimg/commit/05b946cc5cb96ffc36aea41dfcdac9ddbce2cb33

The patch in attachment applies against the existing catimg
version 2.6.0 available in Debian Sid to fix that very specific
bug, but I suppose updating the software to version 2.7.0 would
be a more appropriate approach.

Kind Regards,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/6, please excuse my verbosity.
Description: fix ftbfs with gcc 10
Author: Étienne Mollier 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957066
Forwarded: not-needed
Applied-Upstream: https://github.com/posva/catimg/commit/05b946cc5cb96ffc36aea41dfcdac9ddbce2cb33
Last-Update: 2020-08-08
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- catimg-2.6.0.orig/src/sh_color.h
+++ catimg-2.6.0/src/sh_color.h
@@ -36,9 +36,9 @@
 } color_yuv_t;
 
 #define N_COLORS 247 ///< Number of colors in terminal
-uint32_t color_map[N_COLORS]; ///< palette of the terminal colors in RGB 0x00RRGGBB
+extern uint32_t color_map[N_COLORS]; ///< palette of the terminal colors in RGB 0x00RRGGBB
 // yuv equivalents
-color_yuv_t yuv_color_map[N_COLORS]; ///< palette of the terminal colors in YUV format
+__attribute__((__common__)) color_yuv_t yuv_color_map[N_COLORS]; ///< palette of the terminal colors in YUV format
 
 
 /**


signature.asc
Description: PGP signature

Bug#946046: not fixed

[Stéphane Glondu]

Le 08/08/2020 à 02:41, Vincent Lefevre a écrit :
> unison-2.48 should have never been created: buster has a unison
> package with version number 2.48.4-1, thus one has the impression
> that this is compatible with unison-2.48, while this is not the
> case. The package should have been named unison-2.48+4.08.1 right
> now to avoid this confusion.

I agree with you, retrospectively.

Note that there will never be a unison-2.48+X.XX.X for X.XX.X <> 4.08.1
since unison 2.48.x does not compile with recent versions of OCaml (and
the fix looks too invasive).

> Moreover, unison-2.48 provides /usr/bin/unison-2.48; this is not fine
> since buster also has /usr/bin/unison-2.48, which is not compatible.
> As the client will start a server with the same version number on
> the remote machine (by using the recommended "addversionno = true"),
> this means that one will likely get an archive corruption (which
> happened to me). The OCaml version must be part of the version and
> attached to the name of the unison executable.

Yes, I realized that too late. My hope is to release bullseye with
unison-2.51+X.XX.X and without unison-2.48 at all.

I still think it is useful to have a unison 2.48 compiled with OCaml
4.08.1 around.


Cheers,

-- 
Stéphane

Bug#946046: not fixed

[Stéphane Glondu]

Le 08/08/2020 à 03:25, Vincent Lefevre a écrit :
> The wontfix does not make any sense. The unison-all package is
> described as follows:
> 
> Description: file synchronization tool (all console versions)
>  This is a metapackage that depends on all supported console versions
>  of Unison, a file synchronization tool.
>  .
>  Each of the supported versions uses a different protocol version;
>  installing this metapackage ensures the ability to synchronize with
>  old systems.
> 
> See the latest sentence. That's the *only* purpose of the unison-all
> metapackage.

Ah right, the "ability to synchronize with old systems" is not correct
and never will be. For me, the purpose of unison-all is just to have all
supported versions. For now, there is only one, but there could be many.

I accept this bug as an error in the description. Severity serious for
this seems overreacted, don't you think?

> So, either you are able to fix the issue in some way via unison-all
> (I can see only a rather ugly solution, though the end user would
> not see the ugly part), or the issue cannot be fixed in a clean way,
> and the unison-all package should just be removed from Debian as
> being broken by design (co-instability of the stable versions and the
> unstable version should be sufficient, without needing unison-all),
> which is probably the easiest was to fix this bug.

So you think that having a metapackage just to install all supported
versions is useless? Or even misleading? Then, I will remove unison-all
and unison-all-gtk.

Thank you for your feedback!


Cheers,

-- 
Stéphane

Bug#957217: marked as done (forked-daapd: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 07:33:30 +
with message-id 
and subject line Bug#957217: fixed in forked-daapd 26.4+dfsg1-2
has caused the Debian Bug report #957217,
regarding forked-daapd: 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.)


-- 
957217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:forked-daapd
Version: 26.4+dfsg1-1
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/forked-daapd_26.4+dfsg1-1_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

[...]
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output between 17 and 26 bytes into a destination of 
size 21
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ^~~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
library/filescanner_itunes.o library/filescanner_itunes.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
inputs/file_http.o inputs/file_http.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o inputs/pipe.o 
inputs/pipe.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o outputs/raop.o 
outputs/raop.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 

Bug#968079: libapache2-mod-wsgi: Package is not installable. Needs older Python2.

[greylistd Python issue]

Package: libapache2-mod-wsgi
Version: 4.6.8-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to install the package, the following message is displayed:

== begin 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to be 
installed
  Depends: libpython-stdlib (= 2.7.17-2) but it is not going to be 
installed
  Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed
E: Unable to correct problems, you have held broken packages.
==  end  
The problem is that my Python2 is:
python22.7.18-2 amd64


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

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libapache2-mod-wsgi depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.43-1
ii  libc6   2.31-3
ii  libpython2.72.7.18-1
pn  python  

libapache2-mod-wsgi recommends no packages.

libapache2-mod-wsgi suggests no packages.

Bug#957217: marked as pending in forked-daapd

[Sebastian Ramacher]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/forked-daapd/-/commit/fea74a5caf77a8d59cc00efbba33623d6e85dac7


Fix build with GCC 10

Closes: #957217


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957217

Bug#966166: marked as done (src:v4l-utils: fails to migrate to testing for too long: maintainer built arch:all)

[Debian Bug Tracking System]

Your message dated Sat, 08 Aug 2020 07:05:48 +
with message-id 
and subject line Bug#966166: fixed in v4l-utils 1.20.0-1.1
has caused the Debian Bug report #966166,
regarding src:v4l-utils: fails to migrate to testing for too long: maintainer 
built arch:all
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.)


-- 
966166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: v4l-utils
Version: 1.18.1-1
Severity: serious
Control: close -1 1.20.0-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: v4l-utils
Source-Version: 1.20.0-1.1
Done: Paul Gevers 

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated v4l-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 24 Jul 2020 08:11:41 +0200
Source: v4l-utils
Architecture: source
Version: 1.20.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gregor Jasny 
Changed-By: Paul Gevers 
Closes: 966166
Changes:
 v4l-utils (1.20.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #966166)
Checksums-Sha1:
 fdd107c7612fa418e3000b86c235c674b661ab9b 2881 v4l-utils_1.20.0-1.1.dsc
 44ca94a4e8c092601c267f7991765036547dca53 19484 
v4l-utils_1.20.0-1.1.debian.tar.xz
Checksums-Sha256:
 e9216d723a1af642f1435122a135d152237279048713e45aae8d56543a5ac590 2881 
v4l-utils_1.20.0-1.1.dsc
 96f360dbcdf13fe5ce1fa138f83c73ee581183e771f3190dc88a58b6406dfe88 19484 
v4l-utils_1.20.0-1.1.debian.tar.xz
Files:
 bc0dd4ede11a6af5c26e89086d9f1820 2881 video optional v4l-utils_1.20.0-1.1.dsc
 4b2bc969ad6c85a1b4de97066d196016 19484 video optional 
v4l-utils_1.20.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl8afCcACgkQnFyZ6wW9
dQpnBAf/THuX5DFpG42C2pzbz9T9UIqAFMjkkygy8sF+VeWgIB05Z+GR+zrVwLgf
9dP3nt18qc3qnw2ocyfUzsfp2fbq9GsI5ifOG3QgzWHkONBGOM0Kc1P3OXikW+gP
p+f/W+HMgMX//HflstnM+8F87UQvx9sOGnF+qhMehHMoFro9yBQ+tyqk7aIZ/zvZ
o9/wKHcLzjMKMFPVgecNiJAZxEmDvwlpeUkcFNqUCrnPAGZf+n9fBTM3IZYimo1X
F9etxjZvLyWA/84svz8x4pca78yTRVPcccOqFolFVVHVN96/NEKnSf9WhlxQ1973

Processed: Bug#957217 marked as pending in forked-daapd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #957217 [src:forked-daapd] forked-daapd: ftbfs with GCC-10
Added tag(s) pending.

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

Processed: tagging 957122

[Debian Bug Tracking System]

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

> tags 957122 + pending
Bug #957122 [src:davfs2] davfs2: ftbfs with GCC-10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#957217: forked-daapd: ftbfs with GCC-10

[Sebastian Ramacher]

On 2020-07-31 12:37:13 +0200, Gianfranco Costamagna wrote:
> control: tags -1 patch
> 
> 
> Description: Fix build with gcc-10
> Author: Gianfranco Costamagna 
> Last-Update: 2020-07-31
> 
> --- forked-daapd-26.4+dfsg1.orig/src/input.h
> +++ forked-daapd-26.4+dfsg1/src/input.h
> @@ -137,7 +137,7 @@ struct input_definition
>  /*
>   * Input modules should use this to test if playback should end
>   */
> -int input_loop_break;
> +static int input_loop_break;
> 
>  /*
>   * Transfer stream data to the player's input buffer. The input evbuf will be
> 
> 
> I uploaded this patch in Ubuntu, fixing the FTBFS.
> (upstream heavily refactored that code, so my suggestion is to move to the 
> new upstream release if possible)

Yes, the patch fixes the FTBFS bug, but is wrong. From its documentation
this should be declared with extern and a definition added to
src/input.c.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#968076: bind-dyndb-ldap FTBFS on 32bit: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘unsigned int’

[Adrian Bunk]

Source: bind-dyndb-ldap
Version: 11.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=bind-dyndb-ldap=sid

...
../../src/syncrepl.c: In function ‘sync_task_add’:
../../src/syncrepl.c:460:15: error: format ‘%lu’ expects argument of type ‘long 
unsigned int’, but argument 4 has type ‘unsigned int’ [-Werror=format=]
  460 |  log_debug(2, "adding task %p to syncrepl list; %lu tasks in list",
  |   ^~~~