date:20200202

Bug#937435: pyexiv2: Python2 removal in sid/bullseye

2020-02-02 Thread Michal Čihař

Hi

Sandro Tosi píše v So 01. 02. 2020 v 12:01 -0500:
> > I'd preffer to drop pyexiv2 completely. The recommended upstream
> > approach was to use GI (and gir1.2-gexiv2-0.10) and that's where
> > most
> > of the reverese dependencies have migrated.
> 
> Sure, that sounds like a good plan: do you want me to file the RM
> bug?

Just did that. Thanks for pushing me :-)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950465

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/

Bug#950401: arora: should it be removed from Debian

2020-02-02 Thread Sune Stolborg Vuorela

reassign -1 ftp.debian.org
retitle -1 RM: RoM: Arora - ftbfs - dead upstream
severity -1 normal
thanks

Yeah. let's let it go.

/Sune

On Saturday, February 1, 2020 7:16:51 AM CET Paul Gevers wrote:
> Source: arora
> Version: 0.11.0+qt5+git2014-04-06-1
> Severity: serious
> Justification: ftbfs
> Tags: ftbfs
> 
> Dear Sune,
> 
> Arora has been removed from testing three years ago and is not part of
> buster. Isn't it better if you request removal from Debian if you don't
> intent to fix it?
> 
> If you haven't it done yourself and don't object, I'm going to reassign
> this bug to ftp.debian.org and ask for aroras removal in a couple of weeks.
> 
> Paul

Bug#950470: breezy still fails with one autopkg test on the binary-indep buid

2020-02-02 Thread Matthias Klose

Package: src:breezy
Version: 3.0.2-3
Severity: serious
Tags: sid bullseye

see
https://buildd.debian.org/status/fetch.php?pkg=breezy&arch=all&ver=3.0.2-3&stamp=1580478666&raw=0

==
ERROR:
breezy.tests.per_branch.test_stacking.TestStackingConnections.test_open_stacked_relative(RemoteBranchFormat-v2)
--
Traceback (most recent call last):
testtools.testresult.real._StringException: lost connection during test
'breezy.tests.per_branch.test_stacking.TestStackingConnections.test_open_stacked_relative(RemoteBranchFormat-v2)'
--
Ran 24171 tests in 6121.269s

FAILED (errors=1, known_failure_count=52)
3101 tests skipped

Processed: bug 948130 is forwarded to https://github.com/teejee2008/timeshift/pull/476

2020-02-02 Thread Debian Bug Tracking System

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

> forwarded 948130 https://github.com/teejee2008/timeshift/pull/476
Bug #948130 [src:timeshift] timeshift FTBFS: vala error: Creation method of 
abstract class cannot be public.
Set Bug forwarded-to-address to 
'https://github.com/teejee2008/timeshift/pull/476'.
> thanks
Stopping processing here.

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

Bug#947556: FTBFS with scons 3.1.2-1

2020-02-02 Thread Reiner Herrmann

Control: tags -1 + patch

Dear maintainer,

attached is a patch that fixes the build with the new Python3-enabled
scons version.

Regards,
  Reiner
diff -Nru create-resources-0.1.3/debian/patches/scons.patch create-resources-0.1.3/debian/patches/scons.patch
--- create-resources-0.1.3/debian/patches/scons.patch	1970-01-01 01:00:00.0 +0100
+++ create-resources-0.1.3/debian/patches/scons.patch	2020-02-02 11:38:17.0 +0100
@@ -0,0 +1,91 @@
+Author: Reiner Herrmann 
+Description: Fix build with Python3-enabled scons
+Bug-Debian: https://bugs.debian.org/947556
+
+--- a/SConstruct
 b/SConstruct
+@@ -2,17 +2,17 @@
+ #prefix = "/usr/share"
+ 
+ 
+-opts = Options()
+-opts.Add(PathOption('PREFIX', 'Install prefix', '/usr'))
++opts = Variables()
++opts.Add(PathVariable('PREFIX', 'Install prefix', '/usr'))
+ env = Environment(options = opts)
+ 
+ #prefix=ARGUMENTS.get('prefix', '/usr/share')
+ 
+ 
+-print "Preparing Create Resource Files ..."
++print("Preparing Create Resource Files ...")
+ Export('env')
+ 
+-print 'Preparing Package Documentation ...'
++print('Preparing Package Documentation ...')
+ packagedocs = ['COPYING', 'INSTALL']
+ installdir=env['PREFIX'] + '/share/doc/create'
+ env.Install(installdir, packagedocs)
+--- a/brushes/gimp/SConscript
 b/brushes/gimp/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Brushes (Gimp)...'
++print('Preparing Brushes (Gimp)...')
+ brushesgimp = [
+ '10x10square16.gbr',
+ '10x10squareBlur16.gbr',
+--- a/docs/SConscript
 b/docs/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Documentation ...'
++print('Preparing Documentation ...')
+ docs = ['spec_0.1.1.html', 'styles.css']
+ 
+ installdir=env['PREFIX'] + '/share/doc/create'
+--- a/gradients/gimp/SConscript
 b/gradients/gimp/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Gradients (Gimp) ...'
++print('Preparing Gradients (Gimp) ...')
+ gradgimp = [
+ 'Abstract_1.ggr',
+ 'Abstract_2.ggr',
+--- a/gradients/karbon14/SConscript
 b/gradients/karbon14/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Gradients (Karbon14) ...'
++print('Preparing Gradients (Karbon14) ...')
+ gradk14 = ['allcolors.kgr', 'simple.kgr']
+ 
+ installdir=env['PREFIX'] + '/share/create/gradients/karbon14'
+--- a/patterns/bitmap/16bit/SConscript
 b/patterns/bitmap/16bit/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Patterns (16 bit Bitmap) ...'
++print('Preparing Patterns (16 bit Bitmap) ...')
+ patterns16bit = [
+ '3dgreen.pat',
+ 'amethyst.pat',
+--- a/patterns/bitmap/8bit/SConscript
 b/patterns/bitmap/8bit/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Patterns (8 bit Bitmap) ...'
++print('Preparing Patterns (8 bit Bitmap) ...')
+ patterns8bit = [
+ '3dgreen.pat',
+ 'amethyst.pat',
+--- a/swatches/SConscript
 b/swatches/SConscript
+@@ -1,5 +1,5 @@
+ Import('env')
+-print 'Preparing Swatches ...'
++print('Preparing Swatches ...')
+ swatches = ['Bears', 'Bgold', 'Blues', 'Borders', 'Browns_And_Yellows', 'Caramel', 'Cascade',
+ 'China', 'Coldfire', 'Cool_Colors', 'Cranes', 'Dark_pastels', 'Default', 'Ega', 'Firecode', 
+ 'GNOME_HIG', 'Gold', 'Grayblue', 'Grays', 'GrayViolet', 'Greens', 'Hilite', 'Kahki',
diff -Nru create-resources-0.1.3/debian/patches/series create-resources-0.1.3/debian/patches/series
--- create-resources-0.1.3/debian/patches/series	2013-10-09 13:45:36.0 +0200
+++ create-resources-0.1.3/debian/patches/series	2020-02-02 11:38:17.0 +0100
@@ -1 +1,2 @@
 0001-add_name_header_to_GIMP_palettes.patch
+scons.patch


signature.asc
Description: PGP signature

Processed: Re: FTBFS with scons 3.1.2-1

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #947556 [src:create-resources] FTBFS with scons 3.1.2-1
Added tag(s) patch.

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

Bug#950445: python-couchdb: should this package be removed?

2020-02-02 Thread David Paleino

Hello Sandro,

On 01/02/2020 20:47, Sandro Tosi wrote:
> [..]
>
> If i dont hear a good reason to keep this package in Debian within a week, 
> i'll
> file for its removal.

Please go ahead.

Thank you,
David




signature.asc
Description: OpenPGP digital signature

Processed: tagging 948080

2020-02-02 Thread Debian Bug Tracking System

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

> tags 948080 + fixed
Bug #948080 {Done: Andreas Tille } [src:python-cogent] 
python-cogent build depends on and recommends the removed blast2 transitional 
package
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#950474: python-cogent FTBFS on armel and i386: test failures

2020-02-02 Thread Adrian Bunk

Source: python-cogent
Version: 2019.12.6a+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-cogent&arch=armel&ver=2019.12.6a%2Bdfsg-1&stamp=1579377813&raw=0

...
==
FAIL: test_col_uncertainty (tests.test_maths.test_util.ArrayMathTests)
column_uncertainty: should handle pos/neg/zero/empty arrays
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8_cogent3/build/tests/test_maths/test_util.py",
 line 137, in test_col_uncertainty
column_uncertainty(array([[-2]]))
AssertionError: FloatingPointError not raised
...


https://buildd.debian.org/status/fetch.php?pkg=python-cogent&arch=i386&ver=2019.12.6a%2Bdfsg-1&stamp=1579375248&raw=0

...
==
FAIL: test_jsm (tests.test_maths.test_measure.TestJensenShannon)
case1 is testing if the jsm between two identical distributions is 0.0
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8_cogent3/build/tests/test_maths/test_measure.py",
 line 242, in test_jsm
assert_allclose(
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
1514, in assert_allclose
assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
841, in assert_array_compare
raise AssertionError(msg)
AssertionError: 
Not equal to tolerance rtol=1e-07, atol=0
Testing case4 for jsm failed
Mismatch: 100%
Max absolute difference: 2.10734243e-08
Max relative difference: inf
 x: array(2.107342e-08)
 y: array(0.)
...


The armel port has no FPU in the baseline,
and the math emulation does not handle all corner cases correctly.

The i386 port uses the 387 FPU that has excess precision.

Since this package likely has no users on armel or i386,
I'd suggest to file an RM bug for the old binaries and
then lower the severity of this bug.

Bug#950091: marked as done (node-prop-types FTBFS: Error: Can't resolve)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 11:19:49 +
with message-id 
and subject line Bug#950091: fixed in node-prop-types 15.6.0+ds-4
has caused the Debian Bug report #950091,
regarding node-prop-types FTBFS: Error: Can't resolve
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.)


-- 
950091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-prop-types
Version: 15.6.0+ds-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-prop-types.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-prop-types-15.6.0+ds'
webpack --config debian/webpack.config.js --output-library=PropTypes \
--entry index.js --output ./prop-types.js --mode development
Hash: e061ebce6ca8f90025b2
Version: webpack 4.7.0
Time: 1190ms
Built at: 02/27/2021 10:52:30 PM
Asset  Size  Chunks Chunk Names
prop-types.js  28.9 KiBnull  [emitted]  null
Entrypoint null = prop-types.js
[./checkPropTypes.js] 2.81 KiB {null} [built]
[./factoryWithTypeCheckers.js] 19.4 KiB {null} [built]
[./index.js] 956 bytes {null} [built]
[./lib/ReactPropTypesSecret.js] 314 bytes {null} [built]

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'fbjs/lib/emptyFunction' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 10:20-53
 @ ./index.js

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'fbjs/lib/invariant' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 11:16-45
 @ ./index.js

ERROR in ./checkPropTypes.js
Module not found: Error: Can't resolve 'fbjs/lib/invariant' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./checkPropTypes.js 11:18-47
 @ ./factoryWithTypeCheckers.js
 @ ./index.js

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'fbjs/lib/warning' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 12:14-41
 @ ./index.js

ERROR in ./checkPropTypes.js
Module not found: Error: Can't resolve 'fbjs/lib/warning' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./checkPropTypes.js 12:16-43
 @ ./factoryWithTypeCheckers.js
 @ ./index.js

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'object-assign' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 13:13-37
 @ ./index.js
make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: node-prop-types
Source-Version: 15.6.0+ds-4

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-prop-types package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 11:52:17 +0100
Source: node-prop-types
Architecture: source
Version: 15.6.0+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 950091
Changes:
 node-prop-types (15.6.0+ds-4) unstable; urgency=medium
 .
   * Team upload
   * Add debian/gbp.conf
   * Add upstream/metadata
   * Update debian/watch to use github repository
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
   * Update webpack paths (Closes: #950091)
   * Fix build dependencies
   * Update lintian overrides
   * Add debian/clean
   * Update pkg-js-tools version and remove old debian/tests/* files
   * Update copyright
   * Update homepage
Checksums-Sha1: 
 047d14a4f2acfaa96ec3c175abcf53af47ac5464 2143 node-prop-types_15.6.0+ds-4.dsc
 19391b85054028b280dfba7181a21ae6512246b0 2876 
node-prop-types_15.6.0+ds-4.debian.tar.xz
Checksums-Sha256: 
 c628c90954e639a55256d063eca9e2651e3c77a99f1ea4e4233a8c9664102f6b 2143 
node-prop-types_15.6.0+ds-4.dsc
 0ef38d72c3f21e0f019c60d4e035159e6cb368c2934001bd7d4aa191fd0d5076 2876 
node-prop-types_15.6.0+ds-4.debian.tar.xz
Files: 
 c62462b6cabef1f59a388c9ebc87e1

Bug#949732: package ftbfs on some archs, and has missing dependencies

2020-02-02 Thread Matthias Klose

Control: tags -1 + patch

patch for the uninstallability issue at
http://launchpadlibrarian.net/462915143/mlpack_3.2.2-2ubuntu1_3.2.2-2ubuntu2.diff.gz

Processed: tagging 948206

2020-02-02 Thread Debian Bug Tracking System

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

> tags 948206 - newcomer
Bug #948206 [mitmproxy] mitmproxy incompatible with python3-wsproto=0.15.0-2
Removed tag(s) newcomer.
> thanks
Stopping processing here.

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

Processed: Re: package ftbfs on some archs, and has missing dependencies

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #949732 [src:mlpack] package ftbfs on some archs, and has missing 
dependencies
Added tag(s) patch.

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

Bug#950450: libm4ri and libm4rie

2020-02-02 Thread Julien Puydt

Hi,

indeed, the NEW queue wasn't processed in the same order as the
uploads, so the first library it still in and the second already got
through...

Let's be patient.

JP

Processed: bug 938734 is forwarded to https://github.com/habnabit/txsocksx/issues/19

2020-02-02 Thread Debian Bug Tracking System

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

> forwarded 938734 https://github.com/habnabit/txsocksx/issues/19
Bug #938734 [src:txsocksx] txsocksx: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 
'https://github.com/habnabit/txsocksx/issues/19'.
> thanks
Stopping processing here.

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

Bug#950482: apertium-ca-it FTBFS with apertium 3.6.1

2020-02-02 Thread Adrian Bunk

Source: apertium-ca-it
Version: 0.1.1~r57554-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-ca-it.html

...
apertium-validate-dictionary apertium-ca-it.ca-it.dix
lt-comp rl apertium-ca-it.ca-it.dix it-ca.autobil.bin
main@standard 19237 125346
apertium-validate-dictionary apertium-ca-it.it.dix
apertium-ca-it.it.dix:368: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['S__cantate'] in unique identity-constraint 
'pardef-unique'.
apertium-ca-it.it.dix:372: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['S__cantate'] in unique identity-constraint 
'pardef-unique'.
apertium-ca-it.it.dix:2397: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['tedesc/o__adj'] in unique 
identity-constraint 'pardef-unique'.
apertium-ca-it.it.dix:2890: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['terme__n'] in unique identity-constraint 
'pardef-unique'.
apertium-ca-it.it.dix:4238: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['chi__prn'] in unique identity-constraint 
'pardef-unique'.
apertium-ca-it.it.dix:5454: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['d/are__vblex'] in unique identity-constraint 
'pardef-unique'.
apertium-ca-it.it.dix:7149: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['na/scere__vblex'] in unique 
identity-constraint 'pardef-unique'.
apertium-ca-it.it.dix:8009: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['perma/nere__vblex'] in unique 
identity-constraint 'pardef-unique'.
lt-comp rl apertium-ca-it.it.dix ca-it.autogen.bin 
final@inconditional 11 65
main@standard 11272 23332
xsltproc translate-to-default-equivalent.xsl apertium-ca-it.ca.dix | xsltproc 
--stringparam lang cat --stringparam side left filter.xsl - | xsltproc 
--stringparam alt std alt.xsl - > apertium-ca-it.ca.dixtmp2
apertium-validate-dictionary apertium-ca-it.ca.dixtmp2
apertium-ca-it.ca.dixtmp2:4875: element pardef: Schemas validity error : 
Element 'pardef': Duplicate key-sequence ['inn/ocu__adj'] in unique 
identity-constraint 'pardef-unique'.
lt-comp rl apertium-ca-it.ca.dixtmp2 it-ca.autogen.bin
final@inconditional 7 17
main@standard 71942 131336
regexp@standard 52 1191
rm apertium-ca-it.ca.dixtmp2
apertium-validate-dictionary apertium-ca-it.post-it.dix
lt-comp lr apertium-ca-it.post-it.dix ca-it.autopgen.bin
main@standard 107 404
apertium-validate-dictionary apertium-ca-it.post-ca.dix
lt-comp lr apertium-ca-it.post-ca.dix it-ca.autopgen.bin
main@standard 309 1990
apertium-validate-transfer apertium-ca-it.ca-it.t1x
apertium-preprocess-transfer apertium-ca-it.ca-it.t1x ca-it.t1x.bin
apertium-validate-interchunk apertium-ca-it.ca-it.t2x
apertium-preprocess-transfer apertium-ca-it.ca-it.t2x ca-it.t2x.bin
apertium-validate-postchunk apertium-ca-it.ca-it.t3x
apertium-preprocess-transfer apertium-ca-it.ca-it.t3x ca-it.t3x.bin
apertium-validate-transfer apertium-ca-it.it-ca.t1x
apertium-preprocess-transfer apertium-ca-it.it-ca.t1x it-ca.t1x.bin
apertium-validate-interchunk apertium-ca-it.it-ca.t2x
apertium-preprocess-transfer apertium-ca-it.it-ca.t2x it-ca.t2x.bin
apertium-validate-postchunk apertium-ca-it.it-ca.t3x
apertium-preprocess-transfer apertium-ca-it.it-ca.t3x it-ca.t3x.bin
apertium-validate-modes modes.xml
apertium-gen-modes modes.xml
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:804: modes/it-ca.mode] Error 1

Bug#950484: apertium-is-sv FTBFS with apertium 3.6.1

2020-02-02 Thread Adrian Bunk

Source: apertium-is-sv
Version: 0.1.0~r76450-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-is-sv.html

...
make -j15
make[1]: Entering directory '/build/1st/apertium-is-sv-0.1.0~r76450'
apertium-validate-dictionary apertium-is-sv.is-sv.dix
apertium-validate-dictionary apertium-is-sv.is-sv.dix
apertium-validate-dictionary apertium-is-sv.is.dix
apertium-validate-dictionary apertium-is-sv.sv.dix
apertium-validate-dictionary apertium-is-sv.sv.dix
apertium-validate-dictionary apertium-is-sv.is.dix
apertium-validate-transfer apertium-is-sv.is-sv.t1x
apertium-validate-interchunk apertium-is-sv.is-sv.t2x
apertium-validate-postchunk apertium-is-sv.is-sv.t3x
apertium-validate-transfer apertium-is-sv.sv-is.t1x
apertium-validate-interchunk apertium-is-sv.sv-is.t2x
apertium-validate-postchunk apertium-is-sv.sv-is.t3x
cg-comp apertium-is-sv.is-sv.rlx is-sv.rlx.bin
cg-comp apertium-is-sv.sv-is.rlx sv-is.rlx.bin
apertium-preprocess-transfer apertium-is-sv.is-sv.t2x is-sv.t2x.bin
apertium-preprocess-transfer apertium-is-sv.sv-is.t2x sv-is.t2x.bin
apertium-preprocess-transfer apertium-is-sv.sv-is.t3x sv-is.t3x.bin
apertium-preprocess-transfer apertium-is-sv.is-sv.t3x is-sv.t3x.bin
apertium-validate-modes modes.xml
apertium-is-sv.sv.dix:3511: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['nå__vblex'] in unique identity-constraint 
'pardef-unique'.
apertium-is-sv.sv.dix:3696: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['måst/a__vblex'] in unique 
identity-constraint 'pardef-unique'.
apertium-preprocess-transfer apertium-is-sv.is-sv.t1x is-sv.t1x.bin
apertium-is-sv.sv-is.rlx: Warning: Expected closing ; on line 70 after previous 
rule!
apertium-is-sv.sv.dix:3511: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['nå__vblex'] in unique identity-constraint 
'pardef-unique'.
apertium-is-sv.sv.dix:3696: element pardef: Schemas validity error : Element 
'pardef': Duplicate key-sequence ['måst/a__vblex'] in unique 
identity-constraint 'pardef-unique'.
apertium-gen-modes modes.xml
Sections: 1, Rules: 9, Sets: 19, Tags: 74
apertium-preprocess-transfer apertium-is-sv.sv-is.t1x sv-is.t1x.bin
Sections: 1, Rules: 78, Sets: 117, Tags: 125
cp *.mode modes/
cp: cannot stat '*.mode': No such file or directory
make[1]: *** [Makefile:725: modes/is-sv.mode] Error 1

Bug#936808: marked as done (kopanocore: Python2 removal in sid/bullseye)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 12:34:38 +
with message-id 
and subject line Bug#936808: fixed in kopanocore 8.7.0-6
has caused the Debian Bug report #936808,
regarding kopanocore: 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.)


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

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: kopanocore
Source-Version: 8.7.0-6

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kopanocore 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 13:09:00 +0100
Source: kopanocore
Architecture: source
Version: 8.7.0-6
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Carsten Schoenert 
Closes: 936808 946659
Changes:
 kopanocore (8.7.0-6) unstable; urgency=medium
 .
   [ Steve Langasek ]
   * [0f7f9e8] apparmor kopano-server: allow ldconfig{,.real} call
 (Closes: #946659)
 .
   [ Carsten Schoenert ]
   * [a351358] rebuild patch queue from patch-queue branch
 Added patch (cherry-picked from upstream):
 freebusy-avoid-out-of-bounds-access-in-HrAddFBBlock.patch
 Fixes CVE-2019-19907
 Updated patch:
 Use-python3-everywhere.patch
 We need to adjust the shebang within more Python files so debhelper isn't
 adding a dependency on Python2 because '/usr/bin/python' was found.
 (Closes: #936808)
   * [5e65048] mv service file to current dh name schema
 As recent debhelper isn't detecting a service file
 $b

Bug#950485: evolution-dev still depends on libenchant-dev instead of libenchant-2-dev

2020-02-02 Thread Gerardo Malazdrewicz

Package: evolution-dev
Version: 3.34.1-3
Severity: grave

evolution switched to enchant-2 in 3.34.1-3.

However evolution-dev didn't, still depends on libenchant-dev, and pulls
enchant, libenchant-dev, and libenchant1c2a.
Should Depend on libenchant-2-dev instead.

Thanks,
 Gerardo Malazdrewicz



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

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

Versions of packages evolution-dev depends on:
ii  libcamel1.2-dev  3.34.3-1
ii  libebackend1.2-dev   3.34.3-1
ii  libedataserver1.2-dev3.34.3-1
ii  libedataserverui1.2-dev  3.34.3-1
pn  libenchant-dev   
ii  libevolution 3.34.1-3
ii  libgnome-desktop-3-dev   3.34.2-2
ii  libgtk-3-dev 3.24.13-1
ii  libwebkit2gtk-4.0-dev2.27.4-1

evolution-dev recommends no packages.

evolution-dev suggests no packages.

Bug#936869: libgnatcoll-bindings: Python2 removal in sid/bullseye

2020-02-02 Thread Nicolas Boulenguez

Package: src:libgnatcoll-bindings
Followup-For: Bug #936869
Control: tags -1 + pending

Hello.

An upload to unstable is planned as part of the gnat-9 transition.
It will include explicit python2 dependencies.

Processed: Re: libgnatcoll-bindings: Python2 removal in sid/bullseye

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + pending
Bug #936869 [src:libgnatcoll-bindings] libgnatcoll-bindings: Python2 removal in 
sid/bullseye
Added tag(s) pending.

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

Bug#947005: nethack: buffer overflow when parsing config files

2020-02-02 Thread Reiner Herrmann

Version 3.6.5 has been released, which fixes additional security issues:
 CVE-2020-5209, CVE-2020-5210, CVE-2020-5211, CVE-2020-5212,
 CVE-2020-5213, CVE-2020-5214.

See also:
 https://nethack.org/v365/release.html
 https://www.nethack.org/security/


signature.asc
Description: PGP signature

Bug#950487: apertium-pt-gl FTBFS with apertium 3.6.1

2020-02-02 Thread Adrian Bunk

Source: apertium-pt-gl
Version: 0.9.2~r57551-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-pt-gl.html

...
make -j16
make[1]: Entering directory '/build/1st/apertium-pt-gl-0.9.2~r57551'
make  all-am
make[2]: Entering directory '/build/1st/apertium-pt-gl-0.9.2~r57551'
apertium-validate-dictionary apertium-pt-gl.pt.dix
apertium-validate-dictionary apertium-pt-gl.gl.dix
lt-comp lr apertium-pt-gl.pt-gl.dix pt-gl.autobil.bin
lt-comp rl apertium-pt-gl.pt-gl.dix gl-pt.autobil.bin
apertium-validate-dictionary apertium-pt-gl.gl.dix
apertium-validate-dictionary apertium-pt-gl.pt.dix
apertium-validate-dictionary apertium-pt-gl.post-gl.dix
apertium-validate-dictionary apertium-pt-gl.post-pt.dix
apertium-validate-transfer apertium-pt-gl.pt-gl.t1x
apertium-validate-transfer apertium-pt-gl.gl-pt.t1x
apertium-gen-modes modes.xml
apertium-gen-modes modes.xml
lt-comp lr apertium-pt-gl.post-gl.dix pt-gl.autopgen.bin
lt-comp lr apertium-pt-gl.post-pt.dix gl-pt.autopgen.bin
main@standard 89 259
apertium-preprocess-transfer apertium-pt-gl.gl-pt.t1x \
 gl-pt.t1x.bin
cp *.mode modes/
main@standard 184 503
cp: cannot stat '*.mode': No such file or directory
make[2]: *** [Makefile:772: pt-gl.mode] Error 1

Bug#942895: marked as done (CVE-2019-18224)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:08 +
with message-id 
and subject line Bug#942895: fixed in libidn2 2.0.5-1+deb10u1
has caused the Debian Bug report #942895,
regarding CVE-2019-18224
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.)


-- 
942895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libidn2
Severity: grave
Tags: security

This was assigned CVE-2019-18224: 
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12420

Patch: 
https://github.com/libidn/libidn2/commit/e4d1558aa2c1c04a05066ee8600f37603890ba8c

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Source: libidn2
Source-Version: 2.0.5-1+deb10u1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 Jan 2020 23:15:38 +0100
Source: libidn2
Architecture: source
Version: 2.0.5-1+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian Libidn team 
Changed-By: Salvatore Bonaccorso 
Closes: 942895 949705
Changes:
 libidn2 (2.0.5-1+deb10u1) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix free of random (stack) value in idn2_to_ascii_4i()
   * idn2_to_ascii_4i(): Restrict output length to 63 (CVE-2019-18224)
 (Closes: #942895)
   * Fail make if 'ronn' doesn't exist when building docs
   * Fix generation of idn2.1 man page file
   * Move texinfo from Build-Depends-Indep to Build-Depends (Closes: #949705)
Checksums-Sha1: 
 bded069a9cfc83faeead5a1b817cc22668bdf898 2501 libidn2_2.0.5-1+deb10u1.dsc
 91a5122511f873f1b700f23c487aaf0dbd9e 2091929 libidn2_2.0.5.orig.tar.gz
 40e6d1b1a8e25ae4f799703087d1ac4cd44b3f97 10286540 
libidn2_2.0.5-1+deb10u1.debian.tar.xz
Checksums-Sha256: 
 6c4eac5dc85983e4cf37ee8deea5e23cfb9e1620f7a94a858726676c8858b498 2501 
libidn2_2.0.5-1+deb10u1.dsc
 53f69170886f1fa6fa5b332439c7a77a7d22626a82ef17e2c1224858bb4ca2b8 2091929 
libidn2_2.0.5.orig.tar.gz
 37cfdc06e4e2f03e932af5bb309cbe94f8466f8b347aa34fa7c1e03a425556b2 10286540 
libidn2_2.0.5-1+deb10u1.debian.tar.xz
Files: 
 b29eb22f7dd8e80e73f2ca7b32225f27 2501 libs optional libidn2_2.0.5-1+deb10u1.dsc
 eaf9a5b9d03b0cce3760f34b3124eb36 2091929 libs optional 
libidn2_2.0.5.orig.tar.gz
 e9a6a022a92476fcb233d8c0a3cd245f 10286540 libs optional 
libidn2_2.0.5-1+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl4zWldfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E58AQAKAC9d15tIIlnGUs+LnZCqex5l1N8L3j
GXQqtiQziTC3fW4S/v/EkuqluL3QJvZL3Of9qhZ6hwsHL1JGgeqydwoRrcBvDXRQ
aL0YTC8Jv6+zvIgOZ7oRaC+dx5vIi73uZ8bS8p01JHqKrm2oFxYTGosgHL56bUfp
9XItBi8kOtPiGOMkVfU2vajgFKWmnAvj/acy2yVWLqtGnPCWH5Up6/CnKJOSb02p
CxU73zPe/qQBz0NUY+6zgwFdYTBdMR4BC9+GJ6/aKI8YVoad72L/nh8aEooQltRU
GPOP31MAVgWI0WyDmvwYIa0koEj7OCvcZQbQo214/yBXVLeiHDutuZCtZGZlu3J9
CF7N4b3Cnl3WIGhaut5Vd7Ha3BYRypZY8niAQXf+ks1mTfc+jHdHDvF8HhkDMtVy
H5QFDT6ZsVXAvvo9l5DUHLRL++E/Uc8c0cP/XvAzsmtAFfPpVSGawLERbzaaI/N7
j73DPWryJDo0TU/FCLL++Om5ps1DIWPR1x0LIxPqCoI7h1/84n3/gxSY0QhCkBtY
GIYhwSzL8WXu8EC7PLsyIrAZvXtwLApw3Am9b+nleaPS33TcuZdxVDWtjAcfuw7U
1T8NQYYE4Ui0Yov+XGTAOXTukfyVlZMzcN73zHsKWVL1Lu+cH7jIJ5qLL++yse4g
AktOoMwIE6oM
=cHeG
-END PGP SIGNATURE End Message ---

Bug#948195: marked as done (nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic after the upgrade to 340.108-1)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:18 +
with message-id 
and subject line Bug#948195: fixed in nvidia-graphics-drivers-legacy-340xx 
340.108-3~deb10u1
has caused the Debian Bug report #948195,
regarding nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic 
after the upgrade to 340.108-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.)


-- 
948195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-legacy-340xx-driver
Version: 340.108-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After todays upgrade to 340.108, the system fails to boot in the desktop
enviroment and dmesg reports a kernel panic, as seen on the paste here
https://paste.debian.net/1124712

The lockup is so bad that even ssh-ing to the machine and issuing a reboot does
not work, so I had to reisub out of it every time.
Disabling the display manager (lightdm) and booting to command line works, but
the same happens as soon as I use startx.

Downgrading to kernel 5.3 does not solve the problem and I had to complete
remove nvidia and use nouveau to get back to the desktop and write this bug
report. Now I am trying to install 340.107 from the snapshot repo, but it will
take a lot of time as it seems because of the many dependencies.

Thank you in advance.



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

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

Versions of packages nvidia-legacy-340xx-driver depends on:
pn  nvidia-installer-cleanup 
pn  nvidia-legacy-340xx-alternative  
pn  nvidia-legacy-340xx-driver-bin   
pn  nvidia-legacy-340xx-driver-libs  
pn  nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10  
pn  nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10  
pn  nvidia-legacy-340xx-vdpau-driver 
pn  nvidia-support   
pn  xserver-xorg-video-nvidia-legacy-340xx   

Versions of packages nvidia-legacy-340xx-driver recommends:
pn  nvidia-persistenced   
pn  nvidia-settings-legacy-340xx  

Versions of packages nvidia-legacy-340xx-driver suggests:
pn  nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-source  
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-340xx
Source-Version: 340.108-3~deb10u1

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-340xx, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-340xx 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: Sun, 02 Feb 2020 12:26:56 +0100
Source: nvidia-graphics-drivers-legacy-340xx
Architecture: source
Version: 340.108-3~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 923815 934295 941788 946137 948032 948195
Changes:
 nvidia-graphics-drivers-legacy-340xx (340.108-3~deb10u1) buster; urgency=medium
 .
   * Rebuild for buster.
 .
 nvidia-graphics-drivers-legacy-340xx (340.108-3) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.5.0. No changes needed.
 .
 nvidia-graphics-drivers-legacy-340xx (340.108-2) unstable; urgency=medium
 .
   * Restore kmem_cache_create_usercopy.patch.  (Closes: #948032, #948195)
   * Add NEWS entry w.r.t. EoL state.
   * Use substitution to keep Standards-Version in sync (430.64-5).
 .
 nvidia-graphics-drivers-legacy-340xx (340.108-1) unstable;

Bug#892723: marked as done (dehydrated: Dehydrated broken in stable due to unhandled redirect)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:49 +
with message-id 
and subject line Bug#892723: fixed in dehydrated 0.6.2-2+deb10u1~deb9u1
has caused the Debian Bug report #892723,
regarding dehydrated: Dehydrated broken in stable due to unhandled redirect
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.)


-- 
892723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dehydrated
Version: 0.3.1-3+deb9u1
Severity: normal

Since recently, updating a cert no longer works. The challenge works, and the 
new cert is created, but creating the cert chain fails:

...
 + Creating fullchain.pem...
   + ERROR: An error occurred while sending get-request to 
http://cert.int-x3.letsencrypt.org/ (Status 301)
...

The new cert is consequently not "actived" by symlinks, and the deploy scripts 
are not run.
The reason is a new redirect at Let's Encrypt, and curl does not follow 
redirects unless the "-L" switch is given.

This was fixed upstrem by 


Arne

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

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), 
LANGUAGE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages dehydrated depends on:
ii  ca-certificates  20161130+nmu1
ii  curl 7.52.1-5+deb9u4
ii  openssl  1.1.0f-3+deb9u1

dehydrated recommends no packages.

dehydrated suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dehydrated
Source-Version: 0.6.2-2+deb10u1~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated dehydrated package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Jan 2020 17:33:15 +0100
Source: dehydrated
Binary: dehydrated dehydrated-apache2 letsencrypt.sh letsencrypt.sh-apache2
Architecture: source all
Version: 0.6.2-2+deb10u1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Let's Encrypt Team 
Changed-By: Mattia Rizzolo 
Description:
 dehydrated - ACME client implemented in Bash
 dehydrated-apache2 - dehydrated challenge response support for Apache2
 letsencrypt.sh - ACME client - transitional dummy package to dehydrated
 letsencrypt.sh-apache2 - letsencrypt.sh support for Apache2 - transitional 
dummy package
Closes: 892723 896697
Changes:
 dehydrated (0.6.2-2+deb10u1~deb9u1) stretch; urgency=medium
 .
   * Backport 0.6.2-2 from buster into stretch.
 + In the process, retain the letsencrypt.sh compatibility binaries.
 + Also, revert debhelper compat bump and Multi-Arch field.
 + Add a NEWS item regarding the default ACME endpoint change.
 .
 dehydrated (0.6.2-2+deb10u1) buster; urgency=medium
 .
   * Add three more patches from upstream.
 Fixing the following bug:
  + Fixed fetching of account information.
  + Followup fixes for account ID handling, and APIv1 compatibility.
 .
 dehydrated (0.6.2-2) unstable; urgency=medium
 .
   * Add a number of patches from upstream.
 Fixing the following bugs:
  + HTTP/2 support, where header names are lowercase
  + Avoid over matching, checking for the Replay-Nonce header only at BOL
  + A bug causing deletion of domains.txt when incorrect parameters are used
  + Document the DOMAINS_D config option
  + Impoent POST-as-GET, for the upcoming change in LE's API
  + Document PRIVATE_KEY_ROLLOVER per-cert config option
   * d/control: bump Standards-Version to 4.3.0, no changes needed.
 .
 dehydrated (0.6.2-1) unstable; urgency=medium
 .
   * New upstream release 0.6.2.
   * Remove all patches - applied upstream.
   * d/control: update Homepage field.
 .
 dehydrated (0.

Bug#950258: marked as done (src:spamassassin: arbitrary code execution when processing rules files)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:20 +
with message-id 
and subject line Bug#950258: fixed in spamassassin 3.4.2-1+deb10u2
has caused the Debian Bug report #950258,
regarding src:spamassassin: arbitrary code execution when processing rules files
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.)


-- 
950258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:spamassassin
Version: 3.4.2-1+deb10u1
Severity: grave
Tags: security

CVE-2020-1930:
Apache SpamAssassin 3.4.4 was recently released, and fixes an issue
of security note where nefarious rule configuration (.cf) files can be
configured to run system commands similar to CVE-2018-11805.  With this
bug unpatched, exploits can be injected in a number of scenarios
including the same privileges as spamd is run which may be elevated
though doing so remotely is difficult.  In addition to upgrading to SA
3.4.4, we again recommend that users should only use update channels or
3rd party .cf files from trusted places.  If you cannot upgrade, do not
use 3rd party rulesets, do not use sa-compile and do not run spamd as an
account with elevated privileges.

CVE-2020-1931:
Apache SpamAssassin 3.4.4 was recently released, and fixes an issue
of security note where nefarious rule configuration (.cf) files can be
configured to run system commands similar to CVE-2018-11805.  This issue
is less stealthy and attempts to exploit the issue will throw warnings.
Thanks to Damian Lukowski at credativ for reporting the issue
ethically.  With this bug unpatched, exploits can be injected in a
number of scenarios though doing so remotely is difficult.  In addition
to upgrading to SA 3.4.4, we again recommend that users should only use
update channels or 3rd party .cf files from trusted places.

sid and bullseye are not affected as 3.4.4-rc1 contains the fixes
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.2-1+deb10u2

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated spamassassin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 30 Jan 2020 08:50:54 -0800
Source: spamassassin
Binary: sa-compile spamassassin spamc spamc-dbgsym
Architecture: source all amd64
Version: 3.4.2-1+deb10u2
Distribution: buster-security
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 950258
Changes:
 spamassassin (3.4.2-1+deb10u2) buster-security; urgency=medium
 .
   * Security update to address
 - CVE-2020-1930. Arbitrary code execution via malicious rule files.
 - CVE-2020-1931. Arbitrary code execution via malicious rule files.
 (Closes: #950258)
Checksums-Sha1:
 4984bfe8a30b463bbacc93370101397b7bd84417 2469 spamassassin_3.4.2-1+deb10u2.dsc
 737bb856643e4fb97514886ab241bee4a59e0251 65316 
spamassassin_3.4.2-1+deb10u2.debian.tar.xz
 968502e5faba2c59eee351c4f681e2bc081fa4cd 48172 
sa-compile_3.4.2-1+deb10u2_all.deb
 e06c85e5e76802fd5aeba259aeba38ed3babace0 1125252 
spamassassin_3.4.2-1+deb10u2_all.deb
 d2f8066aa6743affc9f3d49836b1473d472c0292 6607 
spamassassin_3.4.2-1+deb10u2_amd64.buildinfo
 aaf4a589e4f29b45dc28ddfd13c2ee750b686564 51644 
spamc-dbgsym_3.4.2-1+deb10u2_amd64.deb
 c5ea964c158b911558bab7b19a8ea557d353039c 83176 spamc_3.4.2-1+deb10u2_amd64.deb
Checksums-Sha256:
 aa55673e46737b1e479b9275b1415060e4e713618bf616d46272f9e4311f349d 2469 
spamassassin_3.4.2-1+deb10u2.dsc
 e0d4de636e91ebfc1416efabb49bbdf3f89f170766afcb46559deea803c00b30 65316 
spamassassin_3.4.2-1+deb10u2.debian.tar.xz
 9f73a21dfc40e3e94a040bc18f1a8d8f7778aa52c9fb70ee887e1ad1b25ec1a7 48172 
sa-compile_3.4.2-1+deb10u2_all.deb
 35f8e49235dbe7b71f56912436f2c669b2f56f43c3770dbc1715752ad5d07b6a 1125252 
spamassassin_

Bug#948195: marked as done (nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic after the upgrade to 340.108-1)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:51 +
with message-id 
and subject line Bug#948195: fixed in nvidia-graphics-drivers-legacy-340xx 
340.108-3~deb9u1
has caused the Debian Bug report #948195,
regarding nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic 
after the upgrade to 340.108-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.)


-- 
948195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-legacy-340xx-driver
Version: 340.108-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After todays upgrade to 340.108, the system fails to boot in the desktop
enviroment and dmesg reports a kernel panic, as seen on the paste here
https://paste.debian.net/1124712

The lockup is so bad that even ssh-ing to the machine and issuing a reboot does
not work, so I had to reisub out of it every time.
Disabling the display manager (lightdm) and booting to command line works, but
the same happens as soon as I use startx.

Downgrading to kernel 5.3 does not solve the problem and I had to complete
remove nvidia and use nouveau to get back to the desktop and write this bug
report. Now I am trying to install 340.107 from the snapshot repo, but it will
take a lot of time as it seems because of the many dependencies.

Thank you in advance.



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

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

Versions of packages nvidia-legacy-340xx-driver depends on:
pn  nvidia-installer-cleanup 
pn  nvidia-legacy-340xx-alternative  
pn  nvidia-legacy-340xx-driver-bin   
pn  nvidia-legacy-340xx-driver-libs  
pn  nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10  
pn  nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10  
pn  nvidia-legacy-340xx-vdpau-driver 
pn  nvidia-support   
pn  xserver-xorg-video-nvidia-legacy-340xx   

Versions of packages nvidia-legacy-340xx-driver recommends:
pn  nvidia-persistenced   
pn  nvidia-settings-legacy-340xx  

Versions of packages nvidia-legacy-340xx-driver suggests:
pn  nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-source  
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-340xx
Source-Version: 340.108-3~deb9u1

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-340xx, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-340xx 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: Sun, 02 Feb 2020 12:56:28 +0100
Source: nvidia-graphics-drivers-legacy-340xx
Binary: nvidia-legacy-340xx-driver nvidia-legacy-340xx-driver-bin 
nvidia-legacy-340xx-driver-libs nvidia-legacy-340xx-driver-libs-i386 
xserver-xorg-video-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx 
libnvidia-legacy-340xx-glcore libegl1-nvidia-legacy-340xx 
libgles1-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx 
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-cfg1 
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-kernel-support 
nvidia-legacy-340xx-kernel-dkms nvidia-legacy-340xx-kernel-source 
nvidia-legacy-340xx-vdpau-driver nvidia-legacy-340xx-smi 
libnvidia-legacy-340xx-cuda1 libnvidia-legacy-340xx-cuda1-i386 
libnvidia-legacy-340xx-compiler libnvidia-legacy-340xx-nvcuvid1 
libnvidia-legacy-340xx-encode1 libnvidia-legacy-340xx-ifr1 
libnvidia-legacy-34

Bug#950258: marked as done (src:spamassassin: arbitrary code execution when processing rules files)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:53 +
with message-id 
and subject line Bug#950258: fixed in spamassassin 3.4.2-1~deb9u3
has caused the Debian Bug report #950258,
regarding src:spamassassin: arbitrary code execution when processing rules files
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.)


-- 
950258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:spamassassin
Version: 3.4.2-1+deb10u1
Severity: grave
Tags: security

CVE-2020-1930:
Apache SpamAssassin 3.4.4 was recently released, and fixes an issue
of security note where nefarious rule configuration (.cf) files can be
configured to run system commands similar to CVE-2018-11805.  With this
bug unpatched, exploits can be injected in a number of scenarios
including the same privileges as spamd is run which may be elevated
though doing so remotely is difficult.  In addition to upgrading to SA
3.4.4, we again recommend that users should only use update channels or
3rd party .cf files from trusted places.  If you cannot upgrade, do not
use 3rd party rulesets, do not use sa-compile and do not run spamd as an
account with elevated privileges.

CVE-2020-1931:
Apache SpamAssassin 3.4.4 was recently released, and fixes an issue
of security note where nefarious rule configuration (.cf) files can be
configured to run system commands similar to CVE-2018-11805.  This issue
is less stealthy and attempts to exploit the issue will throw warnings.
Thanks to Damian Lukowski at credativ for reporting the issue
ethically.  With this bug unpatched, exploits can be injected in a
number of scenarios though doing so remotely is difficult.  In addition
to upgrading to SA 3.4.4, we again recommend that users should only use
update channels or 3rd party .cf files from trusted places.

sid and bullseye are not affected as 3.4.4-rc1 contains the fixes
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.4.2-1~deb9u3

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated spamassassin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 30 Jan 2020 13:09:03 -0800
Source: spamassassin
Binary: spamassassin spamc sa-compile
Architecture: source all amd64
Version: 3.4.2-1~deb9u3
Distribution: stretch-security
Urgency: medium
Maintainer: Noah Meyerhans 
Changed-By: Noah Meyerhans 
Description:
 sa-compile - Tools for compiling SpamAssassin rules into C
 spamassassin - Perl-based spam filter using text analysis
 spamc  - Client for SpamAssassin spam filtering daemon
Closes: 950258
Changes:
 spamassassin (3.4.2-1~deb9u3) stretch-security; urgency=medium
 .
   * Security update to address
 - CVE-2020-1930. Arbitrary code execution via malicious rule files.
 - CVE-2020-1931. Arbitrary code execution via malicious rule files.
 (Closes: #950258)
Checksums-Sha1:
 4891b552747f3c3229458192c64875365248b4c6 2440 spamassassin_3.4.2-1~deb9u3.dsc
 1136b93dd5a316a23dc1f437bcb4baa9292f885f 60540 
spamassassin_3.4.2-1~deb9u3.debian.tar.xz
 f008e62114432a8a50b6fa607e5f365b7c9b163e 47794 
sa-compile_3.4.2-1~deb9u3_all.deb
 c926bd7e48354c50bd94190ae1b829618bc38ae4 1123144 
spamassassin_3.4.2-1~deb9u3_all.deb
 18d0040b01088aa51e3e5aa9e81ef595be8d26db 7046 
spamassassin_3.4.2-1~deb9u3_amd64.buildinfo
 cce4732d3d6ff2cc7c334d058748cc9b91aff75e 43824 
spamc-dbgsym_3.4.2-1~deb9u3_amd64.deb
 014b00741b043bfb34e1957a5a06a557e09c5983 82926 spamc_3.4.2-1~deb9u3_amd64.deb
Checksums-Sha256:
 bb7224848fdaa0bbfcb66a2440e962676293d8b0a6d231e03a6f4250e5a23e47 2440 
spamassassin_3.4.2-1~deb9u3.dsc
 0cdaf99fed841195c7b0d7671fd121fc7ee451560d5eea51e6a19722f8e938b8 60540 
spamassassin_3.4.2-1~deb9u3.debian.tar.xz
 125034874c511feb264f27bb4fe4cfbb4db7ffe9b9b324b11a403162b27eec99 47794 
sa-compile_3.4.2-1~deb9u3_all.deb
 dbaa55fbb34f0180fa053530b83d4dfa78eec415ba7706e1dfa88722fd384358 1123144 
spamassassin_3.4.2-1~deb9u3_all.deb
 a

Bug#949705: marked as done (libidn2: binary-arch target depends on makeinfo (but texinfo is in Build-Depends-Indep))

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 13:47:08 +
with message-id 
and subject line Bug#949705: fixed in libidn2 2.0.5-1+deb10u1
has caused the Debian Bug report #949705,
regarding libidn2: binary-arch target depends on makeinfo (but texinfo is in 
Build-Depends-Indep)
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.)


-- 
949705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libidn2
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Control: found -1 2.0.5-1

Hi

The binary-arch target would depend on makeinfo, but texinfo is only
listed in Build-Depends-Indep. 

When there is need to patch libidn2 and builds are then done by
buildds this would cause FTBFS on every architecture. How to
reproduce:

Install only the Build-Depends as done on buildds.

touch lib/lookup.c and only build the arch:any binary packages
(dpkg-buildpackage -G or debian/rules build-arch). From the build log:

> [...]
> mkdir -p `dirname texi/lookup.c.texi`
> ../doc/gdoc -texinfo  ../lib/lookup.c > texi/lookup.c.texi
> mkdir -p `dirname texi/idn2_lookup_u8.texi`
> ../doc/gdoc -texinfo  -function idn2_lookup_u8 ../lib/lookup.c > 
> texi/idn2_lookup_u8.texi
> mkdir -p `dirname texi/idn2_lookup_ul.texi`
> ../doc/gdoc -texinfo  -function idn2_lookup_ul ../lib/lookup.c > 
> texi/idn2_lookup_ul.texi
> mkdir -p `dirname texi/idn2_to_ascii_4i.texi`
> ../doc/gdoc -texinfo  -function idn2_to_ascii_4i ../lib/lookup.c > 
> texi/idn2_to_ascii_4i.texi
> mkdir -p `dirname texi/idn2_to_ascii_4i2.texi`
> ../doc/gdoc -texinfo  -function idn2_to_ascii_4i2 ../lib/lookup.c > 
> texi/idn2_to_ascii_4i2.texi
> mkdir -p `dirname texi/idn2_to_ascii_4z.texi`
> ../doc/gdoc -texinfo  -function idn2_to_ascii_4z ../lib/lookup.c > 
> texi/idn2_to_ascii_4z.texi
> mkdir -p `dirname texi/idn2_to_ascii_8z.texi`
> ../doc/gdoc -texinfo  -function idn2_to_ascii_8z ../lib/lookup.c > 
> texi/idn2_to_ascii_8z.texi
> mkdir -p `dirname texi/idn2_to_ascii_lz.texi`
> ../doc/gdoc -texinfo  -function idn2_to_ascii_lz ../lib/lookup.c > 
> texi/idn2_to_ascii_lz.texi
> restore=: && backupdir=".am$$" && \
> am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (/bin/bash /build/libidn2-2.2.0/build-aux/missing makeinfo --version) 
> >/dev/null 2>&1; then \
>   for f in libidn2.info libidn2.info-[0-9] libidn2.info-[0-9][0-9] 
> libidn2.i[0-9] libidn2.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>   done; \
> else :; fi && \
> cd "$am__cwd"; \
> if /bin/bash /build/libidn2-2.2.0/build-aux/missing makeinfo   -I . \
>  -o libidn2.info libidn2.texi; \
> then \
>   rc=0; \
>   CDPATH="${ZSH_VERSION+.}:" && cd .; \
> else \
>   rc=$?; \
>   CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   $restore $backupdir/* `echo "./libidn2.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> /build/libidn2-2.2.0/build-aux/missing: line 81: makeinfo: command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> make[6]: *** [Makefile:1173: libidn2.info] Error 127
> make[6]: Leaving directory '/build/libidn2-2.2.0/doc'
> make[5]: *** [Makefile:1426: all-recursive] Error 1
> make[5]: Leaving directory '/build/libidn2-2.2.0/doc'
> make[4]: *** [Makefile:1131: all] Error 2
> make[4]: Leaving directory '/build/libidn2-2.2.0/doc'
> make[3]: *** [Makefile:1098: all-recursive] Error 1
> make[3]: Leaving directory '/build/libidn2-2.2.0'
> make[2]: *** [Makefile:1007: all] Error 2
> make[2]: Leaving directory '/build/libidn2-2.2.0'
> dh_auto_build: error: make -j1 returned exit code 2
> make[1]: *** [debian/rules:34: override_dh_auto_build] Error 25
> make[1]: Leaving directory '/build/libidn2-2.2.0'
> make: *** [debian/rules:7: build-arch] Error 2

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libidn2
Source-Version: 2.0.5-1+deb10u1

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

A summary of the changes between this version and the pre

Processed: tagging 947559

2020-02-02 Thread Debian Bug Tracking System

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

> tags 947559 + fixed-upstream
Bug #947559 [src:d2x-rebirth] FTBFS with scons 3.1.2-1
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: FTBFS with scons 3.1.2-1

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #947566 [src:klick] FTBFS with scons 3.1.2-1
Added tag(s) patch.

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

Bug#947566: FTBFS with scons 3.1.2-1

2020-02-02 Thread Reiner Herrmann

Control: tags -1 + patch

Dear maintainer,

attached is a patch that fixes the build with the new scons version.

Regards,
  Reiner
diff -Nru klick-0.12.2/debian/patches/scons.patch klick-0.12.2/debian/patches/scons.patch
--- klick-0.12.2/debian/patches/scons.patch	1970-01-01 01:00:00.0 +0100
+++ klick-0.12.2/debian/patches/scons.patch	2020-02-02 15:03:42.0 +0100
@@ -0,0 +1,29 @@
+Author: Reiner Herrmann 
+Description: Fix build failure with recent scons version
+Bug-Debian: https://bugs.debian.org/947566
+
+--- a/SConstruct
 b/SConstruct
+@@ -12,14 +12,14 @@
+ )
+ 
+ # build options
+-opts = Options('scache.conf')
+-opts.AddOptions(
+-PathOption('PREFIX', 'install prefix', '/usr/local'),
+-PathOption('DESTDIR', 'intermediate install prefix', '', PathOption.PathAccept),
+-BoolOption('DEBUG', 'debug mode', False),
+-BoolOption('OSC', 'OSC support', True),
+-BoolOption('TERMINAL', 'terminal control support', True),
+-BoolOption('RUBBERBAND', 'use Rubber Band for pitch shifting', False),
++opts = Variables('scache.conf')
++opts.AddVariables(
++PathVariable('PREFIX', 'install prefix', '/usr/local'),
++PathVariable('DESTDIR', 'intermediate install prefix', '', PathVariable.PathAccept),
++BoolVariable('DEBUG', 'debug mode', False),
++BoolVariable('OSC', 'OSC support', True),
++BoolVariable('TERMINAL', 'terminal control support', True),
++BoolVariable('RUBBERBAND', 'use Rubber Band for pitch shifting', False),
+ )
+ opts.Update(env)
+ opts.Save('scache.conf', env)
diff -Nru klick-0.12.2/debian/patches/series klick-0.12.2/debian/patches/series
--- klick-0.12.2/debian/patches/series	2016-07-11 23:55:33.0 +0200
+++ klick-0.12.2/debian/patches/series	2020-02-02 15:03:42.0 +0100
@@ -1,2 +1,3 @@
 01-hardening_fix.patch
 02-gcc_6.patch
+scons.patch


signature.asc
Description: PGP signature

Processed: Re: FTBFS with scons 3.1.2-1

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #947578 [src:rafkill] FTBFS with scons 3.1.2-1
Added tag(s) patch.

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

Bug#947578: FTBFS with scons 3.1.2-1

2020-02-02 Thread Reiner Herrmann

Control: tags -1 + patch

Dear maintainer,

the attached patch fixes the build failure with the Python3-enabled
scons.

Regards,
  Reiner
diff -Nru rafkill-1.2.2/debian/patches/scons.patch rafkill-1.2.2/debian/patches/scons.patch
--- rafkill-1.2.2/debian/patches/scons.patch	1970-01-01 01:00:00.0 +0100
+++ rafkill-1.2.2/debian/patches/scons.patch	2020-02-02 15:43:25.0 +0100
@@ -0,0 +1,89 @@
+Author: Reiner Herrmann 
+Description: Fix build with Python3-enabled scons
+Bug-Debian: https://bugs.debian.org/947578
+
+--- a/SConstruct
 b/SConstruct
+@@ -6,7 +6,7 @@
+ 
+ # env.Append( CCFLAGS = flags, CPPPATH = [ "../src" ] );
+ 
+-print "Use 'scons -h' for help"
++print("Use 'scons -h' for help")
+ 
+ prefix = '/usr/local/games'
+ bin = '/usr/local/bin'
+@@ -19,9 +19,9 @@
+ 	prefix = 'gen'
+ 	bin = 'gen'
+ 
+-opts = Options( 'rafkill.conf' )
+-opts.Add( PathOption('prefix', 'Directory to install under', prefix ) )
+-opts.Add( PathOption('bin', 'Directory where symlinked executable should go', bin ) )
++opts = Variables( 'rafkill.conf' )
++opts.Add( PathVariable('prefix', 'Directory to install under', prefix ) )
++opts.Add( PathVariable('bin', 'Directory where symlinked executable should go', bin ) )
+ opts.Update( env )
+ opts.Save( 'rafkill.conf', env )
+ 
+@@ -34,7 +34,7 @@
+ 	env.Append( CCFLAGS = [ '-pg' ] )
+ 	env.Append( LINKFLAGS = [ '-pg' ] )
+ 
+-env.BuildDir( 'build/', 'src/' )
++env.VariantDir( 'build/', 'src/' )
+ env.Append( LIBS = [ 'aldmb', 'dumb' ] );
+ if sys.platform == 'win32':
+ 	env.Append( CCFLAGS = [ '-DWINDOWS' ] )
+@@ -51,11 +51,11 @@
+ 
+ # SConscript( 'src/SConscript', build_dir='build', exports = 'env' );
+ sources = SConscript( 'src/SConscript', exports = 'env' );
+-rafkill = env.Program( 'rafkill', map( lambda x: 'build/' + x, sources ) )
++rafkill = env.Program( 'rafkill', list(map( lambda x: 'build/' + x, sources )) )
+ 
+ def installReminder( target, source, env ):
+ 	print
+-	print "Run 'scons install' to install rafkill"
++	print("Run 'scons install' to install rafkill")
+ 	return 0
+ 
+ def ShutUp( target, source, env ):
+@@ -71,7 +71,7 @@
+ env.Alias( 'package', 'src/source.tar' )
+ 
+ def install( target, source, env ):
+-	print "Installing!"
++	print("Installing!")
+ 	return 0
+ 
+ installDir = '$prefix/'
+@@ -81,7 +81,7 @@
+ def addData( file ):
+ 	env.Install( installDir + 'rafkill/data', "data/%s" % file )
+ 
+-map( lambda x: addData( x ), Split( """
++list(map( lambda x: addData( x ), Split( """
+ 1.pck
+ 2.pck
+ 3.pck
+@@ -103,7 +103,7 @@
+ sound.dat
+ table.col
+ vulture.fnt
+-"""));
++""")));
+ 
+ def addMusic( file ):
+ 	env.Install( installDir + 'rafkill/music', "music/%s" % file )
+--- a/src/SConscript
 b/src/SConscript
+@@ -150,7 +150,7 @@
+ """)));
+ 
+ import re
+-headers = map( lambda x: re.compile( 'cpp' ).sub( 'h', x ), sources )
++headers = list(map( lambda x: re.compile( 'cpp' ).sub( 'h', x ), sources ))
+ headers.extend( [ 'fonts.h', 'sound.h', 'wormhole.h' ] )
+ 
+ import os
diff -Nru rafkill-1.2.2/debian/patches/series rafkill-1.2.2/debian/patches/series
--- rafkill-1.2.2/debian/patches/series	2018-01-19 14:24:15.0 +0100
+++ rafkill-1.2.2/debian/patches/series	2020-02-02 15:43:25.0 +0100
@@ -5,3 +5,4 @@
 103_gcc_4.3_fixes
 104_gcc-4.7.patch
 105_glibc-2.26.patch
+scons.patch


signature.asc
Description: PGP signature

Bug#947560: marked as done (FTBFS with scons 3.1.2-1)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 15:06:22 +
with message-id 
and subject line Bug#947560: fixed in ffmpeg2theora 0.30-2
has caused the Debian Bug report #947560,
regarding FTBFS with scons 3.1.2-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.)


-- 
947560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffmpeg2theora
Version: 0.30-1
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

dpkg-checkbuilddeps: error: Unmet build dependencies: libavcodec-dev (>= 6:10~) 
libavdevice-dev (>= 6:10~) libavfilter-dev libavformat-dev (>= 6:10~) 
libavutil-dev libkate-dev libogg-dev liboggkate-dev libpostproc-dev 
libswresample-dev (>= 6:10~) libswscale-dev (>= 6:10~) libtheora-dev 
libvorbis-dev
[1;33mW: Unmet build-dependency in source[0m
dh clean --with quilt
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/data/entwicklung/linux/debian/trans_scons/ffmpeg2theora-0.30'
dh_auto_clean
make -j1 clean
make[2]: Entering directory 
'/data/entwicklung/linux/debian/trans_scons/ffmpeg2theora-0.30'
scons -c
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Cleaning targets ...
scons: done cleaning targets.
Removing autogenerated directory .sconf_temp
make[2]: Leaving directory 
'/data/entwicklung/linux/debian/trans_scons/ffmpeg2theora-0.30'
rm -rf .sconf_temp/ .sconsign.dblite config.log
make[1]: Leaving directory 
'/data/entwicklung/linux/debian/trans_scons/ffmpeg2theora-0.30'
   dh_quilt_unpatch
Removing patch link-libm.patch
Restoring SConstruct

No patches applied
   dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying link-libm.patch
dpkg-source: info: building ffmpeg2theora using existing 
./ffmpeg2theora_0.30.orig.tar.bz2
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building ffmpeg2theora in ffmpeg2theora_0.30-1.debian.tar.xz
dpkg-source: info: building ffmpeg2theora in ffmpeg2theora_0.30-1.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: including full source code in upload
dpkg-source: info: unapplying link-libm.patch
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Fri Dec 27 12:32:37 CET 2019[0m
[0mI: pbuilder-time-stamp: 1577446357[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tgz][0m
[0mI: copying local configuration[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: Mounting /var/cache/debs[0m
[0mI: policy-rc.d already exists[0m
[1;33mW: Could not create compatibility symlink because /tmp/buildd exists and 
it is not a directory[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [../ffmpeg2theora_0.30-1.dsc][0m
[0mI: copying [../ffmpeg2theora_0.30.orig.tar.bz2][0m
[0mI: copying [../ffmpeg2theora_0.30-1.debian.tar.xz][0m
[0mI: Extracting source[0m
dpkg-source: warning: extracting unsigned source package 
(ffmpeg2theora_0.30-1.dsc)
dpkg-source: info: extracting ffmpeg2theora in ffmpeg2theora-0.30
dpkg-source: info: unpacking ffmpeg2theora_0.30.orig.tar.bz2
dpkg-source: info: unpacking ffmpeg2theora_0.30-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying link-libm.patch
[0mI: using fakeroot in build.[0m
[0mI: Installing the build-deps[0m
[0mI: user script /var/cache/pbuilder/build//416979/tmp/hooks/D05dep

Bug#944366: marked as done (FTBFS with OCaml 4.08.1 (safe strings))

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 15:10:29 +
with message-id 
and subject line Bug#944366: fixed in ocaml-res 5.0.1-1
has caused the Debian Bug report #944366,
regarding FTBFS with OCaml 4.08.1 (safe strings)
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.)


-- 
944366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocaml-res
Version: 4.0.3-4
Severity: serious
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

ocaml-res FTBFS with OCaml 4.08.1 because -safe-string is now the
default:

  https://buildd.debian.org/status/package.php?p=ocaml-res


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: ocaml-res
Source-Version: 5.0.1-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 15:40:23 +0100
Source: ocaml-res
Architecture: source
Version: 5.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 925073 944366
Changes:
 ocaml-res (5.0.1-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release (Closes: #944366)
   * Update Homepage and debian/watch
   * Remove Lifeng from Uploaders (Closes: #925073)
   * Update Vcs-*
   * Bump debhelper compat level to 12
   * Bump Standards-Version to 4.5.0
   * Add Rules-Requires-Root: no
Checksums-Sha1:
 5bfba087466f748bb1d16f17cc32aec292db9384 1703 ocaml-res_5.0.1-1.dsc
 0910d09fab1e54c6e9b747bacb676525d19e27c6 31771 ocaml-res_5.0.1.orig.tar.gz
 1baa45bbd4b561cc407924c5c32ad130a3ce14c3 3376 ocaml-res_5.0.1-1.debian.tar.xz
Checksums-Sha256:
 f2560fa1748220c616787ce0c3c99d62faa4ec52cfab25ae187a42567ad6c0ce 1703 
ocaml-res_5.0.1-1.dsc
 df7965f5021a4422a462545647aad420a50dd8ba69c504eff74b3c346593b70d 31771 
ocaml-res_5.0.1.orig.tar.gz
 88f56e23853ebd2c4b6fe03fcf4df75e2a236632ffa41006f415b6394331c985 3376 
ocaml-res_5.0.1-1.debian.tar.xz
Files:
 3069c3fa4ad4754ad8dcf7570429e3c1 1703 ocaml optional ocaml-res_5.0.1-1.dsc
 fa41fa793bc26d55ce6916ff67de3489 31771 ocaml optional 
ocaml-res_5.0.1.orig.tar.gz
 160ede9776e782b6da73f39f795ae632 3376 ocaml optional 
ocaml-res_5.0.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl424LUSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBV4IIAI5NYmy7XrEuDxPuGoHk/e+9XduwJ+lY
6RKxar9kSK5b3pbBjo7EJQGh6/BMcn8n1vSNIaSpdec9ITGHcX2EMHuj9y9kenNV
Bg3aaitACqbN8oj6jEuXMqjfsPLYIRwWSpGMxTI2DwKpduvPAct5raIu+oJW1h6/
hdLMv4f64cwl5IDV0prwaIeBL6hKfQBGAxAmtOylgsJPohvVN+c6Jrc4aEEdOg1V
/wyA8IulN8qX2vlA4CbUGGmX17if1YBBfDtMnfpiRrrJ0Zm7MX34M0rzzYbwlbP9
mqIPwoI/Jpo3IQac5tarv7EBpxOnpEqgwIM7rbz8eAiPmbk28Msd6is=
=KyoM
-END PGP SIGNATURE End Message ---

Bug#950496: msgpack-c: FTBFS on 32-bit: error: narrowing conversion of ‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’}

2020-02-02 Thread Andreas Beckmann

Package: msgpack-c
Version: 3.2.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

msgpack-c/experimental on all 32-bit architectures:
https://buildd.debian.org/status/package.php?p=msgpack-c&suite=experimental

[17/122] /usr/bin/c++   -I../build-gtest/install/include -I../include -Iinclude 
-DMSGPACK_DEFAULT_API_VERSION=3 -std=c++11 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall -Wextra 
-Wconversion -MD -MT test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -MF 
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o.d -o 
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -c 
../test/msgpack_cpp11.cpp
FAILED: test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o 
/usr/bin/c++   -I../build-gtest/install/include -I../include -Iinclude 
-DMSGPACK_DEFAULT_API_VERSION=3 -std=c++11 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall -Wextra 
-Wconversion -MD -MT test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -MF 
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o.d -o 
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -c 
../test/msgpack_cpp11.cpp
../test/msgpack_cpp11.cpp: In member function ‘virtual void 
MSGPACK_TIMESPEC_timespec_pack_convert_32bit_sec_Test::TestBody()’:
../test/msgpack_cpp11.cpp:1081:36: error: narrowing conversion of ‘4294967295’ 
from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’} [-Wnarrowing]
 1081 | timespec val1{ 0xUL, 0 };
  |^
../test/msgpack_cpp11.cpp: In member function ‘virtual void 
MSGPACK_TIMESPEC_timespec_object_with_zone_32bit_sec_Test::TestBody()’:
../test/msgpack_cpp11.cpp:1097:36: error: narrowing conversion of ‘4294967295’ 
from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’} [-Wnarrowing]
 1097 | timespec val1{ 0xUL, 0 };
  |^


Andreas

Processed: FTBFS against opencv 4.0.1 (exp)

2020-02-02 Thread Debian Bug Tracking System

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

> severity 922583 serious
Bug #922583 [src:gst-plugins-bad1.0] FTBFS against opencv 4.0.1 (exp)
Ignoring request to change severity of Bug 922583 to the same value.
> thanks
Stopping processing here.

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

Bug#950496: msgpack-c: FTBFS on 32-bit: error: narrowing conversion of ‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’}

2020-02-02 Thread James McCoy

Control: tag -1 fixed-upstream

On Sun, Feb 02, 2020 at 04:47:26PM +0100, Andreas Beckmann wrote:
> msgpack-c/experimental on all 32-bit architectures:
> https://buildd.debian.org/status/package.php?p=msgpack-c&suite=experimental

Yes, that and #950460 are the main reasons I haven't uploaded this to
unstable yet.

Upstream already has a fix, which I was already working on backporting.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Processed: Re: Bug#950496: msgpack-c: FTBFS on 32-bit: error: narrowing conversion of ‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’}

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 fixed-upstream
Bug #950496 [msgpack-c] msgpack-c: FTBFS on 32-bit: error: narrowing conversion 
of ‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’}
Added tag(s) fixed-upstream.

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

Bug#947559: d2x-rebirth: diff for NMU version 0.58.1-1.2

2020-02-02 Thread Stephen Kitt

Control: tags 947559 + patch
Control: tags 947559 + pending

Dear maintainer,

I've prepared an NMU for d2x-rebirth (versioned as 0.58.1-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,

Stephen
diff -Nru d2x-rebirth-0.58.1/debian/changelog d2x-rebirth-0.58.1/debian/changelog
--- d2x-rebirth-0.58.1/debian/changelog	2017-12-09 15:16:38.0 +0100
+++ d2x-rebirth-0.58.1/debian/changelog	2020-02-02 18:18:43.0 +0100
@@ -1,3 +1,10 @@
+d2x-rebirth (0.58.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Allow building with Python 3. Closes: #947559.
+
+ -- Stephen Kitt   Sun, 02 Feb 2020 18:18:43 +0100
+
 d2x-rebirth (0.58.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru d2x-rebirth-0.58.1/debian/patches/python3.patch d2x-rebirth-0.58.1/debian/patches/python3.patch
--- d2x-rebirth-0.58.1/debian/patches/python3.patch	1970-01-01 01:00:00.0 +0100
+++ d2x-rebirth-0.58.1/debian/patches/python3.patch	2020-02-02 18:18:43.0 +0100
@@ -0,0 +1,179 @@
+--- a/SConstruct
 b/SConstruct
+@@ -12,19 +12,8 @@
+ 	def get(self,name,value=None):
+ 		return self.ARGUMENTS.get('%s_%s' % (self.prefix, name), self.ARGUMENTS.get(name,value))
+ 
+-# endianess-checker
+-def checkEndian():
+-import struct
+-array = struct.pack('', '\x01', '\x02', '\x03', '\x04')
+-i = struct.unpack('i', array)
+-if i == struct.unpack('i', array):
+-return "big"
+-return "unknown"
+-
+ class DXXCommon:
+-	__endian = checkEndian()
++	__endian = sys.byteorder
+ 	class UserSettings:
+ 		def __init__(self,ARGUMENTS):
+ 			# Paths for the Videocore libs/includes on the Raspberry Pi
+@@ -57,7 +46,7 @@
+ 			builddir_suffix = ARGUMENTS.get('builddir_suffix', None)
+ 			default_builddir = builddir_prefix or ''
+ 			if builddir_prefix is not None or builddir_suffix is not None:
+-if os.environ.has_key('CC'):
++if 'CC' in os.environ:
+ 	default_builddir += '%s-' % os.path.basename(os.environ['CC'])
+ for a in (
+ 	('debug', 'dbg'),
+@@ -131,7 +120,7 @@
+ flags = self.__pkg_config_sdl[cmd]
+ 			except KeyError as e:
+ if (program.user_settings.verbosebuild != 0):
+-	print "%s: reading SDL settings from `%s`" % (program.PROGRAM_NAME, cmd)
++	print("%s: reading SDL settings from `%s`" % (program.PROGRAM_NAME, cmd))
+ self.__pkg_config_sdl[cmd] = env.backtick(cmd)
+ flags = self.__pkg_config_sdl[cmd]
+ 			env.MergeFlags(flags)
+@@ -156,31 +145,31 @@
+ 		self.env.Append(CPPDEFINES = ['NETWORK'])
+ 		# Get traditional compiler environment variables
+ 		for cc in ['CC', 'CXX']:
+-			if os.environ.has_key(cc):
++			if cc in os.environ:
+ self.env[cc] = os.environ[cc]
+ 		for flags in ['CFLAGS', 'CXXFLAGS']:
+-			if os.environ.has_key(flags):
++			if flags in os.environ:
+ self.env[flags] += SCons.Util.CLVar(os.environ[flags])
+ 
+ 	def check_endian(self):
+ 		# set endianess
+ 		if (self.__endian == "big"):
+-			print "%s: BigEndian machine detected" % self.PROGRAM_NAME
++			print("%s: BigEndian machine detected" % self.PROGRAM_NAME)
+ 			self.asm = 0
+ 			self.env.Append(CPPDEFINES = ['WORDS_BIGENDIAN'])
+ 		elif (self.__endian == "little"):
+-			print "%s: LittleEndian machine detected" % self.PROGRAM_NAME
++			print("%s: LittleEndian machine detected" % self.PROGRAM_NAME)
+ 
+ 	def check_platform(self):
+ 		# windows or *nix?
+ 		if sys.platform == 'win32':
+-			print "%s: compiling on Windows" % self.PROGRAM_NAME
++			print("%s: compiling on Windows" % self.PROGRAM_NAME)
+ 			platform = self.Win32PlatformSettings
+ 		elif sys.platform == 'darwin':
+-			print "%s: compiling on Mac OS X" % self.PROGRAM_NAME
++			print("%s: compiling on Mac OS X" % self.PROGRAM_NAME)
+ 			platform = self.DarwinPlatformSettings
+ 		else:
+-			print "%s: compiling on *NIX" % self.PROGRAM_NAME
++			print("%s: compiling on *NIX" % self.PROGRAM_NAME)
+ 			platform = self.LinuxPlatformSettings
+ 		self.platform_settings = platform(self.user_settings)
+ 		# Acquire environment object...
+@@ -194,15 +183,15 @@
+ 		# opengl or software renderer?
+ 		if (self.user_settings.opengl == 1) or (self.user_settings.opengles == 1):
+ 			if (self.user_settings.opengles == 1):
+-print "%s: building with OpenGL ES" % self.PROGRAM_NAME
++print("%s: building with OpenGL ES" % self.PROGRAM_NAME)
+ env.Append(CPPDEFINES = ['OGLES'])
+ 			else:
+-print "%s: building with OpenGL" % self.PROGRAM_NAME
++print("%s: building with OpenGL" % self.PROGRAM_NAME)
+ 			env.Append(CPPDEFINES = ['OGL'])
+ 
+ 		# assembler code?
+ 		if (self.user_settings.asm == 1) and (self.user_settings.opengl == 0):
+-			print "%s: including: ASSEMBLER" % self.PROGRAM_NAME
++			print("%s: including: ASSEMBLER" % self.PROGRAM_NAME)
+ 			env.Replace(AS = 'nasm')
+ 			env.Append(ASCOM = ' -f ' + str(self.platform_settings.osasmdef) + ' -d' + str(self.platform_settings.osdef) + ' -Itexmap/ ')
+ 			self.common_sources += asm_s

Processed: d2x-rebirth: diff for NMU version 0.58.1-1.2

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags 947559 + patch
Bug #947559 [src:d2x-rebirth] FTBFS with scons 3.1.2-1
Added tag(s) patch.
> tags 947559 + pending
Bug #947559 [src:d2x-rebirth] FTBFS with scons 3.1.2-1
Added tag(s) pending.

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

Bug#947558: d1x-rebirth: diff for NMU version 0.58.1-1.1

2020-02-02 Thread Stephen Kitt

On Sun, 02 Feb 2020 02:44:51 +1100, Dmitry Smirnov  wrote:
> On Sunday, 2 February 2020 2:28:04 AM AEDT Stephen Kitt wrote:
> > I've prepared an NMU for d1x-rebirth (versioned as 0.58.1-1.1) and
> > uploaded it to DELAYED/5.  
> 
> Thank you very much for doing this, Stephen. Much appreciated.

You’re very welcome! I’ve just done the same for d2x-rebirth (with a very
similar patch). The srcdir handling at the end of SConstruct is dealt with in
a rather ham-fisted manner in my patches, but I couldn’t figure out the
proper fix in a reasonable amount of time...

Regards,

Stephen

pgpBea6gGdABy.pgp
Description: OpenPGP digital signature

Processed: py2removal bugs severity updates - 2020-02-02 17:35:45.212926+00:00

2020-02-02 Thread Debian Bug Tracking System

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-jdcal is a module and has 0 external rdeps or not in testing
> severity 936762 serious
Bug #936762 [src:jdcal] jdcal: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-et-xmlfile is a module and has 0 external rdeps or not in testing
> severity 937738 serious
Bug #937738 [src:python-et-xmlfile] python-et-xmlfile: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: limit source to symfony, tagging 949045

2020-02-02 Thread Debian Bug Tracking System

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

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

> tags 949045 + pending
Bug #949045 [src:symfony] symfony: autopkgtest regression: fails and loads of 
*warnings* on stderr
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#950111: libvigraimpex-doc: unhandled symlink to directory conversion: /usr/share/doc/libvigraimpex-dev/html

2020-02-02 Thread Andreas Metzler

On 2020-01-28 Andreas Beckmann  wrote:
> Package: libvigraimpex-doc
> Version: 1.11.1+dfsg-6
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts

> Hi,

> an upgrade test with piuparts revealed that your package installs files
> over existing symlinks and possibly overwrites files owned by other
> packages. This usually means an old version of the package shipped a
> symlink but that was later replaced by a real (and non-empty)
> directory. This kind of overwriting another package's files cannot be
> detected by dpkg.

> This was observed on the following upgrade paths:

>   buster -> bullseye
[...]
> It is recommended to use the dpkg-maintscript-helper commands
> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
> to perform the conversion, ideally using d/$PACKAGE.maintscript.
> See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.

Hello Andreas,

thanks for report and pointers.

Afaiu (and that is what my tests showed) dpkg-maintscript-helper will
help me for upgrades from before-the-move to after-the-move but will not
fix the broken installations that have already upgraded from
before-the-move to 1.11.1+dfsg-6 and I will need to handle this
separately in the maintainerscripts. - Or am I missing something?

I have already got some draft packages, but they will probably not be
uploaded before next weekend.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#949045: marked as done (symfony: autopkgtest regression: fails and loads of warnings on stderr)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 18:35:49 +
with message-id 
and subject line Bug#949045: fixed in symfony 4.4.4-1
has caused the Debian Bug report #949045,
regarding symfony: autopkgtest regression: fails and loads of *warnings* on 
stderr
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.)


-- 
949045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: symfony
Version: 4.4.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of symfony the autopkgtest of symfony fails in
testing when that autopkgtest is run with the binary packages of symfony
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
symfonyfrom testing4.4.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? On top of that, the
upload also caused regression in the autopkgtest of php-doctrine-bundle;
I haven't check that one yet.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/symfony/4000881/log.gz

autopkgtest [09:16:11]: test phpunit: [---
+ patch -p1
patching file src/Symfony/Component/Cache/Tests/LockRegistryTest.php
+ mkdir --parents vendor
+ phpab --output vendor/autoload.php --whitelist '*\\tests\\*'
--tolerant --template debian/autoload.php.tests.tpl --blacklist
'symfony\\component\\dependencyinjection\\tests\\fixtures\\container\\projectservicecontainer'
--exclude
src/Symfony/Bridge/ProxyManager/Tests/LazyProxy/PhpDumper/Fixtures/proxy-implem.php
src/Symfony
phpab %development% - Copyright (C) 2009 - 2020 by Arne Blankerts and
Contributors

Scanning directory src/Symfony

Autoload file vendor/autoload.php generated.

+ set +x
PHP Warning:  require_once(GuzzleHttp/Promise/autoload.php): failed to
open stream: No such file or directory in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9
PHP Fatal error:  require_once(): Failed opening required
'GuzzleHttp/Promise/autoload.php' (include_path='.:/usr/share/php') in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9

Running src/Symfony/Bundle/WebProfilerBundle tests
[41mKO[0m src/Symfony/Bundle/WebProfilerBundle

Running src/Symfony/Bundle/TwigBundle tests
[41mKO[0m src/Symfony/Bundle/TwigBundle
PHP Warning:  require_once(GuzzleHttp/Promise/autoload.php): failed to
open stream: No such file or directory in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9
PHP Fatal error:  require_once(): Failed opening required
'GuzzleHttp/Promise/autoload.php' (include_path='.:/usr/share/php') in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9

Running src/Symfony/Bundle/FrameworkBundle tests
[41mKO[0m src/Symfony/Bundle/FrameworkBundle
PHP Warning:  require_once(GuzzleHttp/Promise/autoload.php): failed to
open stream: No such file or directory in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9
PHP Fatal error:  require_once(): Failed opening required
'GuzzleHttp/Promise/autoload.php' (include_path='.:/usr/share/php') in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9
PHP Warning:  require_once(GuzzleHttp/Promise/autoload.php): failed to
open stream: No such file or directory in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9
PHP Fatal error:  require_once(): Failed opening required
'GuzzleHttp/Promise/autoload.php' (include_path='.:/usr/share/php') in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9

Running src/Symfony/Bundle/DebugBundle tests
[41mKO[0m src/Symfony/Bundle/DebugBundle

Running src/Symfony/Bundle/SecurityBundle tests
[41mKO[0m src/Symfony/Bundle/SecurityBundle
PHP Warning:  require_once(GuzzleHttp/Promise/autoload.php): failed to
open stream: No such file or directory in
/tmp/autopkgtest-lxc.5s4ujzl9/downtmp/build.Zhk/src/vendor/autoload.php
on line 9
PHP Fatal error:  require_once(): Failed opening required
'GuzzleHttp/Promi

Bug#947555: marked as done (FTBFS with scons 3.1.2-1)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 19:04:33 +
with message-id 
and subject line Bug#947555: fixed in btanks 0.9.8083-9
has caused the Debian Bug report #947555,
regarding FTBFS with scons 3.1.2-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.)


-- 
947555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: btanks
Version: 0.9.8083-8
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

dpkg-checkbuilddeps: error: Unmet build dependencies: libgl1-mesa-dev | 
libgl-dev libglu1-mesa-dev | libglu-dev libsdl-image1.2-dev libsdl1.2-dev 
libsigc++-2.0-dev libsmpeg-dev libvorbis-dev sharutils
[1;33mW: Unmet build-dependency in source[0m
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/data/entwicklung/linux/debian/trans_scons/btanks-0.9.8083'
dh_auto_clean
rm -rf .sconf_temp build
make[1]: Leaving directory 
'/data/entwicklung/linux/debian/trans_scons/btanks-0.9.8083'
   dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building btanks using existing ./btanks_0.9.8083.orig.tar.bz2
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: warning: ignoring deletion of file engine/sl08/sl08.h, use 
--include-removal to override
dpkg-source: info: building btanks in btanks_0.9.8083-8.debian.tar.xz
dpkg-source: info: building btanks in btanks_0.9.8083-8.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: not including original source code in upload
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Fri Dec 27 11:47:53 CET 2019[0m
[0mI: pbuilder-time-stamp: 1577443673[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tgz][0m
[0mI: copying local configuration[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: Mounting /var/cache/debs[0m
[0mI: policy-rc.d already exists[0m
[1;33mW: Could not create compatibility symlink because /tmp/buildd exists and 
it is not a directory[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [../btanks_0.9.8083-8.dsc][0m
[0mI: copying [../btanks_0.9.8083.orig.tar.bz2][0m
[0mI: copying [../btanks_0.9.8083-8.debian.tar.xz][0m
[0mI: Extracting source[0m
dpkg-source: warning: extracting unsigned source package (btanks_0.9.8083-8.dsc)
dpkg-source: info: extracting btanks in btanks-0.9.8083
dpkg-source: info: unpacking btanks_0.9.8083.orig.tar.bz2
dpkg-source: info: unpacking btanks_0.9.8083-8.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying remove_default_optimizations.patch
dpkg-source: info: applying rename-currency-symbol.patch
dpkg-source: info: applying gcc-4.6.patch
dpkg-source: info: applying gcc-4.7.patch
dpkg-source: info: applying pow10f.patch
[0mI: using fakeroot in build.[0m
[0mI: Installing the build-deps[0m
[0mI: user script /var/cache/pbuilder/build//284956/tmp/hooks/D05deps 
starting[0m
Get:1 file:/var/cache/debs ./ InRelease
Ign:1 file:/var/cache/debs ./ InRelease
Get:2 file:/var/cache/debs ./ Release
Ign:2 file:/var/cache/debs ./ Release
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packages
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/va

Bug#948508: marked as done (CVE-2019-5188: malicious fs can cause stack underflow in e2fsck)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 19:17:08 +
with message-id 
and subject line Bug#948508: fixed in e2fsprogs 1.44.5-1+deb10u3
has caused the Debian Bug report #948508,
regarding CVE-2019-5188: malicious fs can cause stack underflow in e2fsck
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.)


-- 
948508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.43.4-2+deb9u1
Severity: grave
Tags: security
Justification: user security hole

E2fsprogs 1.45.5 contains a bug fix for CVE-2019-5188 / TALOS-2019-0973.
The following commits need to be backported to address this
vulnerability in Debian Buster and Debian Stretch:

8dd73c14 - e2fsck: abort if there is a corrupted directory block when rehashing
71ba1375 - e2fsck: don't try to rehash a deleted directory

The impact of this bug is that if an attacker can tricker the system
into running e2fsck on an untrustworthy file system, a maliciously
crafted file system could result in a stack underflow.  The primary
concern is on 32-bit systems; due to limitations in the kind of stack
corruption which can be triggered due to this bug, it is probably not
exploitable on 64-bit systems.
--- End Message ---
--- Begin Message ---
Source: e2fsprogs
Source-Version: 1.44.5-1+deb10u3

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

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

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

Debian distribution maintenance software
pp.
Theodore Y. Ts'o  (supplier of updated e2fsprogs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 09 Jan 2020 20:19:57 -0500
Source: e2fsprogs
Architecture: source
Version: 1.44.5-1+deb10u3
Distribution: buster
Urgency: medium
Maintainer: Theodore Y. Ts'o 
Changed-By: Theodore Y. Ts'o 
Closes: 948508 948517
Changes:
 e2fsprogs (1.44.5-1+deb10u3) buster; urgency=medium
 .
   * Fix CVE-2019-5188: potential stack underflow in e2fsck (Closes: #948508)
   * Fix use after free in e2fsck (Closes: #948517)
Checksums-Sha1:
 3415765e85e55240f8ba87d55333ff93f710c640 2903 e2fsprogs_1.44.5-1+deb10u3.dsc
 4d02f7e775f06bdf8ed5c526df2776fb1290ad68 82412 
e2fsprogs_1.44.5-1+deb10u3.debian.tar.xz
Checksums-Sha256:
 acdc31d6fd491f9db97aabc96340559d8492b98e3549df32d8369690e03058dc 2903 
e2fsprogs_1.44.5-1+deb10u3.dsc
 0114857448922a218613f369f665f03f1b1435004c9d79ce5ee1a8a8a6cec53f 82412 
e2fsprogs_1.44.5-1+deb10u3.debian.tar.xz
Files:
 bf870a591ecae238eb9a2176aa89a885 2903 admin required 
e2fsprogs_1.44.5-1+deb10u3.dsc
 06b5d0e4023d94add08971e8e58c8264 82412 admin required 
e2fsprogs_1.44.5-1+deb10u3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEK2m5VNv+CHkogTfJ8vlZVpUNgaMFAl4sbPkACgkQ8vlZVpUN
gaOcgAf+KiRHnD/Dyw5n2JxIQsWrcTMOUVlUnDJl2Kb8FYINmfPKGwxVw8EY5vYw
x4PzD+voyw4Js7SsE9pKxncwSehaqSuoMWeUYWIFlj5rBEDkyjRezPdGbSbm8qxp
M+QAvUV4RZMVXUK9pOq9xp4vKJhOb4+svVgZ4b+WAIiCWqj5JEVsYORujAj1CaNY
IigdWmAWfq/kskc3Rb4W8tzsfMeP+S6Q6m94P/YUzfRpKScCw/+5oePxVjB9QTPk
LFpFdtNgsnL8T37YGFITjxTFwJPRIYrYOHuHqWQEAWS/FKGllVDI8r/UnaSQjUrL
N+7Qd30WpIzhYprseJhuIc6J3/wCCA==
=dJMD
-END PGP SIGNATURE End Message ---

Bug#946242: marked as done (fatal: privsep_preauth: preauth child terminated by signal 31)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 19:17:09 +
with message-id 
and subject line Bug#946242: fixed in openssh 1:7.9p1-10+deb10u2
has caused the Debian Bug report #946242,
regarding fatal: privsep_preauth: preauth child terminated by signal 31
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.)


-- 
946242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:7.9p1-10+deb10u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? apt upgrade lead to openssh-server
   * being unusable.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?  bug #941663 supposedly fixed this issue in the
 version I upgraded to but the symptom remains. Also tried
 installing 8.1 version but that did not fix the issue either. I am
 running a 3.16 kernel because a 4.x kernel is not supported on my 
 hardware (AMD Geode LX processor).
   * What was the outcome of this action? no change
   * What outcome did you expect instead? to login

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.2
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.71
ii  dpkg   1.19.7
ii  libaudit1  1:2.8.4-3
ii  libc6  2.28-10
ii  libcom-err21.44.5-1+deb10u2
ii  libgssapi-krb5-2   1.17-3
ii  libkrb5-3  1.17-3
ii  libpam-modules 1.3.1-5
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libselinux12.8-1+b1
ii  libssl1.1  1.1.1d-0+deb10u2
ii  libsystemd0241-7~deb10u2
ii  libwrap0   7.6.q-28
ii  lsb-base   10.2019051400
ii  openssh-client 1:7.9p1-10+deb10u1
ii  openssh-sftp-server1:7.9p1-10+deb10u1
ii  procps 2:3.3.15-2
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  241-7~deb10u2
ii  ncurses-term 6.1+20181013-2+deb10u2
ii  xauth1:1.0.10-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- Configuration Files:
/etc/default/ssh changed:
SSHD_OPTS=-4


-- debconf information:
* ssh/use_old_init_script: true
* openssh-server/permit-root-login: true
  ssh/encrypted_host_key_but_no_keygen:
  openssh-server/password-authentication: false
  ssh/vulnerable_host_keys:
  ssh/new_config: true
  ssh/disable_cr_auth: false
--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:7.9p1-10+deb10u2

We believe that the bug you reported is fixed in the latest version of
openssh, 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.
Colin Watson  (supplier of updated openssh 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, 31 Jan 2020 20:55:34 +
Source: openssh
Architecture: source
Version: 1:7.9p1-10+deb10u2
Distribution: buster
Urgency: medium
Maintainer: Debian OpenSSH Maintainers 
Changed-By: Colin Watson 
Closes: 946242
Changes:
 openssh (1:7.9p1-10+deb10u2) buster; urgency=medium
 .
   * Apply upstream patch to deny (non-fatally) ipc in the seccomp sandbox,
 fixing failures with OpenSSL 1.1.1d and Linux < 3.19 on some
 architectures (closes: #946242).  Note that this also drops the previous
 change to allow ipc on s390, since upstream has security concerns with
 that and

Bug#950508: debos: broken in Buster: libresolv.so.2: cannot open shared object file

2020-02-02 Thread Sascha Silbe

Package: debos
Version: 1.0.0+git20190123.d6e16be-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after the upgrade to Buster debos stopped working. This happens even
with the minimal example from the man page. The output when run with
--show-boot suggests a shared library issue inside the VM:

sascha@brick:~$ debos --show-boot example.yaml 
[0.00] Linux version 4.19.0-6-amd64 (debian-ker...@lists.debian.org) 
(gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 
(2019-11-11)
[0.00] Command line: console=ttyS0 panic=-1 
systemd.unit=fakemachine.service
[...]
[0.713821] Run /init as init process
/bin/busybox: error while loading shared libraries: libresolv.so.2: cannot open 
shared object file: No such file or directory
[0.715660] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
[...]
[0.728779] Kernel Offset: 0x3800 from 0x8100 (relocation 
range: 0x8000-0xbfff)
open /tmp/fakemachine-785139448/result: no such file or directory
sascha@brick:~$

The same happens in a VM where I did a fresh install of debos so it's
very likely to affect all debos users on Buster (hence severity
grave).

Kind regards,
Sascha

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable'), (500, 'stable-debug'), 
(500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en:en_US:C:de_DE:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debos depends on:
ii  busybox1:1.30.1-4
ii  debootstrap1.0.114
ii  libc6  2.28-10
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libostree-1-1  2019.1-1
ii  qemu-system-x861:3.1+dfsg-8+deb10u3
ii  qemu-user-static   1:3.1+dfsg-8+deb10u3
ii  systemd-container  241-7~deb10u2

Versions of packages debos recommends:
ii  bmap-tools 3.5-2
ii  bzip2  1.0.6-9.2~deb10u1
ii  e2fsprogs  1.44.5-1+deb10u2
ii  linux-image-amd64  4.19+105+deb10u1
ii  mount  2.33.1-0.1
ii  ovmf   0~20181115.85588389-3
ii  parted 3.2-25
ii  udev   241-7~deb10u2
ii  xz-utils   5.2.4-1
ii  zip3.0-11+b1

debos suggests no packages.

-- no debconf information

Bug#947554: marked as done (FTBFS with scons 3.1.2-1)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 19:34:21 +
with message-id 
and subject line Bug#947554: fixed in boswars 2.7+svn160110-5
has caused the Debian Bug report #947554,
regarding FTBFS with scons 3.1.2-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.)


-- 
947554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boswars
Version:  2.7+svn160110-4
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



boswars_2.7+svn160110-4_amd64.build
Description: Binary data


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: boswars
Source-Version: 2.7+svn160110-5

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 19:52:49 +0100
Source: boswars
Architecture: source
Version: 2.7+svn160110-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 927916 944900 947554
Changes:
 boswars (2.7+svn160110-5) unstable; urgency=medium
 .
   [ Reiner Herrmann ]
   * Team upload.
   * Fix build with Python3-enabled scons versions (Closes: #947554)
   * Extend description of data package.
   * Update debhelper compat to 12.
   * Replace broken png image.
 Thanks to Alexander Kuznetsov and Steve the Fiddle for providing
 fixed versions. (Closes: #927916, #944900)
   * Update Standards-Version to 4.5.0:
 - declare that d/rules does not require root
Checksums-Sha1:
 e0450a579f40c65735001dfd2949ade1d85c9605 2300 boswars_2.7+svn160110-5.dsc
 5c795909e15d9152be5b49daca867251684de123 244636 
boswars_2.7+svn160110-5.debian.tar.xz
 7d96738858c727be8eb3ba8bf649e3eb1e5d3e34 10824 
boswars_2.7+svn160110-5_amd64.buildinfo
Checksums-Sha256:
 d55269ddedf2fc6e2123a8fd8646c56f8afc261ea54318a3d3f568b50b02d28b 2300 
boswars_2.7+svn160110-5.dsc
 8c50f46760cacf97fa6b9ef7cdd603e6929a5b11e04edf7c206dde42cf913733 244636 
boswars_2.7+svn160110-5.debian.tar.xz
 c3f5d20b83648b07d19946a5f36dcfa11ece0feffcba0718e2483841279ea238 10824 
boswars_2.7+svn160110-5_amd64.buildinfo
Files:
 3d5acf9a9f125309c781836422b6c1b4 2300 games optional 
boswars_2.7+svn160110-5.dsc
 edf8e7d314ce1603fcbec00e02232e22 244636 games optional 
boswars_2.7+svn160110-5.debian.tar.xz
 e00472e03c5a7c296cd14b608397aba6 10824 games optional 
boswars_2.7+svn160110-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl43HVhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkGBgQAIF5LalyDHWCMHEPCGq6GlM8pAPIgFDiHDCH
pBMmdFFOXisBt0JwwbKo70JDkCtjR5NRyiOMzuqvFZcMsGFiLyUQGX5VEYrTnlHh
3jPI224sT71S5IvJ3kuruIFFO1PKjC4W81OZzh3cZdPw5W31OaAC+BxDFiL212tU
xN+gN/jpEYtUzMdnLrJGCc8rjrEouPhMrxMTY61EOaAJGVtprtwO8q4Goq/37A+h
CzUW0fq17GXlATe6xd/JRh1e0NolAhku/MDhYcIlqfXp9FHhFII5ni7dKtQNjker
9YIlNDN/WRxtxnbm972EN6C0HF2/F+tS/bCJvXt3ZS9Ayrd6gg5RIgTJ6+Hgf+Nu
dOQg8xEnpQ+WkzbJEnAfNwkKyuB3SHkCWeuPI/QPClyvNOZgDqL5IW2U1VZgVFEi
ckzJ98OymCATj0aPsVvKvK1xezZVuKHlkCawsYL2fWo1FFgbwRqkE8TvGIRDGC

Bug#947585: marked as done (FTBFS with scons 3.1.2-1)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 19:52:11 +
with message-id 
and subject line Bug#947585: fixed in xboxdrv 0.8.8-2
has caused the Debian Bug report #947585,
regarding FTBFS with scons 3.1.2-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.)


-- 
947585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xboxdrv
Version: 0.8.8-1
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



xboxdrv_0.8.8-1_amd64.build
Description: Binary data


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: xboxdrv
Source-Version: 0.8.8-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 20:12:24 +0100
Source: xboxdrv
Architecture: source
Version: 0.8.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 895734 947585
Changes:
 xboxdrv (0.8.8-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Phil Wyett ]
   * Fix build with Python3-enabled scons. (Closes: #947585)
 .
   [ Reiner Herrmann ]
   * Update watch file. (Closes: #895734)
   * debian/control:
 - update homepage.
 - point Vcs-* URLs to salsa.
 - update debhelper compat to 12
 - update Standards-Version to 4.5.0
 - declare that d/rules does not require root
   * Use https URL for copyright format.
   * Drop unused lintian override.
Checksums-Sha1:
 4af973ecef4df9035c8a8aad2237d29ff35274c7 2135 xboxdrv_0.8.8-2.dsc
 ae0e02e2f2fe97e66fa00671eddce63d1326b874 9616 xboxdrv_0.8.8-2.debian.tar.xz
 d73e9c928dfb28dffcba35e5b720aa201e2f056c 8209 xboxdrv_0.8.8-2_amd64.buildinfo
Checksums-Sha256:
 fdfdd232e4d923d8a5cc3c214dad91826f561926614371ac19b224693d782296 2135 
xboxdrv_0.8.8-2.dsc
 4b91c1f51abd40662d689b1267c9d70e2e54b8a763251a2c41c463d559f7f064 9616 
xboxdrv_0.8.8-2.debian.tar.xz
 98f002aeaee3de4fd1a336fd5c064e91a6246d261c44c76b3cf272d12e9fb2da 8209 
xboxdrv_0.8.8-2_amd64.buildinfo
Files:
 4a8250cdf6c49890aa69b9df5fa49c85 2135 utils optional xboxdrv_0.8.8-2.dsc
 d0981237f975177d77db591f67e6eefa 9616 utils optional 
xboxdrv_0.8.8-2.debian.tar.xz
 1bfa5040e46b3d68147cd5e52dbbcdd2 8209 utils optional 
xboxdrv_0.8.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl43IadfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkKCAQAIWR3VCbsHr2ayGD8WOZVBlbUExsCHBheLmm
3u+zltXryRgvMJLnvBxgMh0Bfi1aXp1GL18KiRHh3pzI6i5fLTC9+HoE2hkoXpox
dnOp3iFTgf04mi1cK+mY6iRejgI4le/5jEr02TNxVHbfgDtsgAuA7Iva2KiJ9Eme
nYjkNcJ4pZhAQ8R/jGj8fpx9zL0MAz7BouqlyGMs66NEhIGf+ouraz042TQ/tiIb
qeCNW0eJOFWtlW9FQcjhtGMwxOoPCZKeFd9Q1jCRnFSEVY8fYojHzcr6vdiWR4qB
a941E7S0zN9beXBhD4vLmQ+zyYpEgZT/feFFPY7usmLt3xisMCN6Chor18ocJ8JX
ve9zIVoj8UPUohVMKOFOhPTb2fGJt5vgBdkJdzQIeTiakxgW8J+GlCD0amzZLMWk
T06PAWObLJpu2LfrjyhtXmS9ETtZd68t2Svu4LrBAAsy+zAlm5Qjb6ZHS3WrLyNw
KfMd/5cbHYiVeQs1CjWiWDy0fydhqjKMcDStJnQpV9brYn3znFUq5EyRZ4ilzpjw
ibrpModJAR/dBpaKyswwVNsrjUUFHW6CcmixgO3L7h+jdKc

Bug#936762: jdcal: diff for NMU version 1.0-1.3

2020-02-02 Thread Sandro Tosi

Control: tags 936762 + patch


Dear maintainer,

I've prepared an NMU for jdcal (versioned as 1.0-1.3). The diff
is attached to this message.

Consider maintaining this package with the DPMT

Regards.

diff -Nru jdcal-1.0/debian/changelog jdcal-1.0/debian/changelog
--- jdcal-1.0/debian/changelog	2017-09-24 21:15:10.0 -0400
+++ jdcal-1.0/debian/changelog	2020-02-02 15:10:30.0 -0500
@@ -1,3 +1,10 @@
+jdcal (1.0-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936762
+
+ -- Sandro Tosi   Sun, 02 Feb 2020 15:10:30 -0500
+
 jdcal (1.0-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru jdcal-1.0/debian/control jdcal-1.0/debian/control
--- jdcal-1.0/debian/control	2017-09-24 21:15:10.0 -0400
+++ jdcal-1.0/debian/control	2020-02-02 15:09:56.0 -0500
@@ -2,24 +2,12 @@
 Section: python
 Priority: optional
 Maintainer: Yaroslav Halchenko 
-Build-Depends: debhelper (>= 9), python, python3, dh-python
+Build-Depends: debhelper (>= 9), python3, dh-python
 Standards-Version: 3.9.6
 Homepage: https://github.com/phn/jdcal
 Vcs-Git: http://github.com/neurodebian/jdcal -b debian
 Vcs-Browser: http://github.com/neurodebian/jdcal
 
-Package: python-jdcal
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Description: Julian dates from proleptic Gregorian and Julian calendars
- This module contains functions for converting between Julian dates
- and calendar dates.
- .
- Different regions of the world switched to Gregorian calendar from
- Julian calendar on different dates. Having separate functions for
- Julian and Gregorian calendars allow maximum flexibility in choosing
- the relevant calendar.
-
 Package: python3-jdcal
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}
diff -Nru jdcal-1.0/debian/rules jdcal-1.0/debian/rules
--- jdcal-1.0/debian/rules	2014-12-10 00:49:59.0 -0500
+++ jdcal-1.0/debian/rules	2020-02-02 15:10:26.0 -0500
@@ -3,15 +3,6 @@
 # output every command that modifies files on the build system.
 #DH_VERBOSE = 1
 
-PYVERS = $(shell pyversions -vr)
-PY3VERS = $(shell py3versions -vr)
-
 # main packaging script based on dh7 syntax
 %:
-	dh $@ --with=python2,python3
-
-
-override_dh_auto_install: ${PYVERS:%=python-install%} ${PY3VERS:%=python-install%}
-python-install%:
-	echo "$*" | grep -q '^3' && PY=3 || PY= ; \
-python$$PY setup.py install --install-layout=deb --root=$(CURDIR)/debian/python$$PY-jdcal
+	dh $@ --with=python3 --buildsystem=pybuild

Processed: jdcal: diff for NMU version 1.0-1.3

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags 936762 + patch
Bug #936762 [src:jdcal] jdcal: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#937738: python-et-xmlfile: diff for NMU version 1.0.1-2.1

2020-02-02 Thread Sandro Tosi

Control: tags 937738 + patch


Dear maintainer,

I've prepared an NMU for python-et-xmlfile (versioned as 1.0.1-2.1). The diff
is attached to this message.

Consider maintaining this package with the DPMT

Regards.

diff -Nru python-et-xmlfile-1.0.1/debian/changelog python-et-xmlfile-1.0.1/debian/changelog
--- python-et-xmlfile-1.0.1/debian/changelog	2016-04-26 21:36:21.0 -0400
+++ python-et-xmlfile-1.0.1/debian/changelog	2020-02-02 15:13:55.0 -0500
@@ -1,3 +1,10 @@
+python-et-xmlfile (1.0.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937738
+
+ -- Sandro Tosi   Sun, 02 Feb 2020 15:13:55 -0500
+
 python-et-xmlfile (1.0.1-2) unstable; urgency=medium
 
   * Use compliant binary package names (Closes: #822742)
diff -Nru python-et-xmlfile-1.0.1/debian/control python-et-xmlfile-1.0.1/debian/control
--- python-et-xmlfile-1.0.1/debian/control	2016-04-26 21:48:03.0 -0400
+++ python-et-xmlfile-1.0.1/debian/control	2020-02-02 15:13:44.0 -0500
@@ -5,34 +5,17 @@
 Build-Depends:
 	debhelper (>=9),
 	dh-python,
-# Python2
-	python-all,
-	python-setuptools,
-	python-lxml (>= 3.4),
 # Python3
 	python3-all,
 	python3-setuptools,
 	python3-lxml (>= 3.4),
 # Test-Depends:
-	python-pytest,
 	python3-pytest,
 Standards-Version: 3.9.8
 Homepage: https://bitbucket.org/openpyxl/et_xmlfile
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/python-et-xmlfile.git
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/python-et-xmlfile.git
 
-Package: python-et-xmlfile
-Architecture: all
-Depends:
-	${python:Depends},
-	${misc:Depends},
-Description: low memory library for creating large XML files (Python 2)
- et_xmlfile is based upon the xmlfile module from lxml with the aim of
- allowing code to be developed that will work with both libraries. It was
- developed initially for the openpyxl project but is now a standalone module.
- .
- This package installs the library for Python 2.
-
 Package: python3-et-xmlfile
 Architecture: all
 Depends:
diff -Nru python-et-xmlfile-1.0.1/debian/rules python-et-xmlfile-1.0.1/debian/rules
--- python-et-xmlfile-1.0.1/debian/rules	2016-04-26 21:30:50.0 -0400
+++ python-et-xmlfile-1.0.1/debian/rules	2020-02-02 15:13:51.0 -0500
@@ -5,4 +5,4 @@
 export PYBUILD_NAME=et-xmlfile
 
 %:
-	dh $@  --with python2,python3 --buildsystem=pybuild
+	dh $@  --with python3 --buildsystem=pybuild

Processed: python-et-xmlfile: diff for NMU version 1.0.1-2.1

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tags 937738 + patch
Bug #937738 [src:python-et-xmlfile] python-et-xmlfile: Python2 removal in 
sid/bullseye
Added tag(s) patch.

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

Bug#950258: fixed in spamassassin 3.4.2-1~deb9u3

2020-02-02 Thread Damian

Will there be a fix for jessie?

On Sun, 02 Feb 2020 13:47:53 + Debian FTP Masters
 wrote:

> Source: spamassassin
> Source-Version: 3.4.2-1~deb9u3
>
> We believe that the bug you reported is fixed in the latest version of
> spamassassin, 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 950...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.

Bug#936762: marked as done (jdcal: Python2 removal in sid/bullseye)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 20:52:05 +
with message-id 
and subject line Bug#936762: fixed in jdcal 1.0-1.3
has caused the Debian Bug report #936762,
regarding jdcal: 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.)


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

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: jdcal
Source-Version: 1.0-1.3

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated jdcal 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: Sun, 02 Feb 2020 15:10:30 -0500
Source: jdcal
Architecture: source
Version: 1.0-1.3
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Sandro Tosi 
Closes: 936762
Changes:
 jdcal (1.0-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936762
Checksums-Sha1:
 c6d5a0ef742b235fe10f21761297445f8920487b 1812 jdcal_1.0-1.3.dsc
 2f9b7e49bb5619574073d6dac99c538c2569d90e 2284 jdcal_1.0-1.3.debian.tar.xz
 a7e2c65421ad39c32a91b9944957c7828d93ae59 7316 jdcal_1.0-1.3_amd64.buildinfo
Checksums-Sha256:
 521312d1ba0870710bc5b4dbe06146bf1558973109c08c03af97a0d33edb545a 1812 
jdcal_1.0-1.3.dsc
 cbe0263ee98da350ed7571140782d384c60ebcef0411649fc0f3f2aac7df089c 2284 
jdcal_1.0-1.3.debian.tar.xz
 79a903306d5a8fffb1d13203f7b8a38a0b2003df64c9d1b09a869e58bb8307df 7316 
jdcal_1.0-1.3_amd64.buildinfo
Files:
 706d32ec762066abffa50d44d53cce02 1812 python optional jdcal_1.0-1.3.dsc
 92f3225ca0893fb7987ec94a278514d7 2284 python optional 
jd

Bug#937738: marked as done (python-et-xmlfile: Python2 removal in sid/bullseye)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 20:55:20 +
with message-id 
and subject line Bug#937738: fixed in python-et-xmlfile 1.0.1-2.1
has caused the Debian Bug report #937738,
regarding python-et-xmlfile: 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.)


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

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: python-et-xmlfile
Source-Version: 1.0.1-2.1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-et-xmlfile 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: Sun, 02 Feb 2020 15:13:55 -0500
Source: python-et-xmlfile
Architecture: source
Version: 1.0.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Afif Elghraoui 
Changed-By: Sandro Tosi 
Closes: 937738
Changes:
 python-et-xmlfile (1.0.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937738
Checksums-Sha1:
 f73ebc7c42529fa396f5953ded7fdd4e6b2203c3 2043 python-et-xmlfile_1.0.1-2.1.dsc
 1f37f2246d3f4a6f73f0d9aab229d0c2eab4fd89 2032 
python-et-xmlfile_1.0.1-2.1.debian.tar.xz
 6998e9b3f34c1d976766359d93e37740af93deb6 8079 
python-et-xmlfile_1.0.1-2.1_amd64.buildinfo
Checksums-Sha256:
 ca2418240e0f8f0d9429d65fcaa452edca8aa79a33ea1a0e990fa3fe969d51d9 2043 
python-et-xmlfile_1.0.1-2.1.dsc
 ddca42ebb683b1f6207230d475be0567656fb8ce8a3ea8ce09f28f474fcfeb37 2032 
python-et-xmlfile_1.0.1-2.1.debian.tar.xz
 1c7b23b3c5eaf8f3d7cb7180ce021272971f1b187bd787c2e01b59a

Bug#950512: quotecolors: not usable anymore with TB>= 68.x

2020-02-02 Thread Carsten Schoenert

Source: quotecolors
Severity: serious

Hello Christoph,

xul-ext-quotecolors isn't usable with Thunderbird 68.x due API
incompatibilities.

There is no new version provided by upstream which is usable again with
recent Thunderbird versions so this package is useless now.
The whole package should be removed from the archives.

Regards
Carsten

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

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

Bug#937485: pymvpa2: Python2 removal in sid/bullseye

2020-02-02 Thread Stuart Prescott

Dear maintainers,

In the last update on pymvpa2, it sounded like upstream would soon have sorted 
Python 3 compatibility and the FTBFS bugs for the package would soon be fixed. 
However, there has been no upstream activity in the referenced PR 
https://github.com/PyMVPA/PyMVPA/pull/525 for many months.

What are the prospects for a fixed package in the buster release cycle? Given 
that it will have to go through NEW to gain the Python 3 module package in any 
case, are we at the stage where it should just be removed from Debian, perhaps 
to be reintroduced later when upstream work is completed?

(There's a cost to keeping buggy packages in Debian in that they occupy 
people's time when dealing with transitions or bug squashing. Even finding the 
packaging Vcs to see if there has been yet-to-be uploaded progress on these 
bugs is excessively difficult right now)

Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#950450: marked as done (libm4rie-0.0.20200125: Depends on libm4ri-0.0.20200115)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 22:17:49 +0100
with message-id <9ae64def18a52eaaa0c305ec4fb9a0c253a3c9f1.ca...@laposte.net>
and subject line libm4ri cleared NEW : problem gone
has caused the Debian Bug report #950450,
regarding libm4rie-0.0.20200125: Depends on libm4ri-0.0.20200115
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.)


-- 
950450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libm4rie-0.0.20200125
Version: 20200125-1
Severity: serious

Hi,

seems that something went wrong with the binary upload of libm4rie on amd64. On 
this architecture libm4rie-0.0.20200125 depends on libm4ri-0.0.20200115 which 
makes it uninstallable. This might be fixable with a source-only-upload.

Best,
Tobias
--- End Message ---
--- Begin Message ---
Hi,

I just got notified that libm4ri had cleared NEW, so libm4rie should be
ok soon.

Cheers,

JP--- End Message ---

Processed: found 950445 in 0.10-1.1, tagging 950445, tagging 924310, found 916178 in 1.8.14-2 ...

2020-02-02 Thread Debian Bug Tracking System

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

> found 950445 0.10-1.1
Bug #950445 [python-couchdb] python-couchdb: should this package be removed?
Marked as found in versions python-couchdb/0.10-1.1.
> tags 950445 + sid bullseye
Bug #950445 [python-couchdb] python-couchdb: should this package be removed?
Added tag(s) sid and bullseye.
> tags 924310 + moreinfo unreproducible
Bug #924310 [xrdp] xrdp: post-install script fails
Added tag(s) unreproducible and moreinfo.
> found 916178 1.8.14-2
Bug #916178 [src:roger-router] roger-router-cli: missing dependency on cups
Marked as found in versions roger-router/1.8.14-2.
> found 950452 2.4+cvs20120801-1
Bug #950452 [getlive] getlive: Is this program still working at all?
Marked as found in versions getlive/2.4+cvs20120801-1.
> thanks
Stopping processing here.

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

Bug#937738: python-et-xmlfile: diff for NMU version 1.0.1-2.1

2020-02-02 Thread Afif Elghraoui

On ٨‏/٦‏/١٤٤١ هـ ١٢:١٥ م, Sandro Tosi wrote:
> Control: tags 937738 + patch
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for python-et-xmlfile (versioned as 1.0.1-2.1). The diff
> is attached to this message.
> 
> Consider maintaining this package with the DPMT
> 

I'd have been happy to, but at the time, DPMT was using git-dpm and it
didn't seem worth learning to use an unmaintained tool just to package a
couple of python modules.

Thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
https://afif.ghraoui.name

Bug#937738: python-et-xmlfile: diff for NMU version 1.0.1-2.1

2020-02-02 Thread Sandro Tosi

> I'd have been happy to, but at the time, DPMT was using git-dpm and it
> didn't seem worth learning to use an unmaintained tool just to package a
> couple of python modules.

yeah, i feel you, and since then we migrated to salsa and a plain gbp
+ pristine-tar workflow

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Processed: tagging 949312, unblock 950348 with 950345 950247 950343, tagging 950348, tagging 947027 ...

2020-02-02 Thread Debian Bug Tracking System

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

> tags 949312 - sid bullseye
Bug #949312 [ftp.debian.org] RM: txsocksx -- RoQA; python2-only; leaf package; 
no progress on upstream py3k port
Removed tag(s) sid and bullseye.
> unblock 950348 with 950345 950247 950343
Bug #950348 [src:golang-github-docker-engine-api] 
golang-github-docker-engine-api: obsolete, incompatible with current docker 
version
950348 was blocked by: 950345 950247 950343
950348 was not blocking any bugs.
Removed blocking bug(s) of 950348: 950345, 950343, and 950247
> tags 950348 - moreinfo
Bug #950348 [src:golang-github-docker-engine-api] 
golang-github-docker-engine-api: obsolete, incompatible with current docker 
version
Removed tag(s) moreinfo.
> tags 947027 - sid bullseye
Bug #947027 [ftp.debian.org] RM: sgmltools-lite -- RoQA, py2, duperseeded by 
docbook-utils
Removed tag(s) sid and bullseye.
> tags 948555 - sid bullseye
Bug #948555 [ftp.debian.org] RM: python-soappy -- RoQA; python2-only; leaf 
package; upstream suggests to use 'suds'; better alternatives exist
Removed tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#949915: marked as done (gr-limesdr is missing the b-d on dh-python)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 23:10:11 +
with message-id 
and subject line Bug#949915: fixed in gr-limesdr 3.0.1-1
has caused the Debian Bug report #949915,
regarding gr-limesdr is missing the b-d on dh-python
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.)


-- 
949915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gr-limesdr
Version: 2.0.0-27-gca01a64-3
Severity: serious
Tags: sid bullseye patch

gr-limesdr is missing the b-d on dh-python. patch at
http://launchpadlibrarian.net/462215973/gr-limesdr_2.0.0-27-gca01a64-3build1_2.0.0-27-gca01a64-3ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: gr-limesdr
Source-Version: 3.0.1-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated gr-limesdr 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: Sun, 02 Feb 2020 21:57:34 +0100
Source: gr-limesdr
Binary: gr-limesdr gr-limesdr-dbgsym libgnuradio-limesdr3.0.1 
libgnuradio-limesdr3.0.1-dbgsym
Architecture: source amd64
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Description:
 gr-limesdr - LimeSDR blocks for GnuRadio
 libgnuradio-limesdr3.0.1 - LimeSDR blocks for GnuRadio (runtime library)
Closes: 949915
Changes:
 gr-limesdr (3.0.1-1) unstable; urgency=medium
 .
   * New upstream version with new soname.
   * B-D on dh-python. (Closes: #949915)
   * debian/watch: Remove broken and unnecessary opts.
Checksums-Sha1:
 10770d1390e2145ce82684fbd66dcfbb4be30665 2269 gr-limesdr_3.0.1-1.dsc
 4e105d51c2e7847bfcd163ad954a9d59b9f46108 2992883 gr-limesdr_3.0.1.orig.tar.gz
 b528573b624b6bc543fefd8117f9bcae6a76a59a 3492 gr-limesdr_3.0.1-1.debian.tar.xz
 3382bb86a67438e3ea81a189ac60a206723f0003 834272 
gr-limesdr-dbgsym_3.0.1-1_amd64.deb
 b2bb1ccbdc5f66605e7ec2077c5e4f708874ff4c 17878 
gr-limesdr_3.0.1-1_amd64.buildinfo
 dc913d2dff45fbdc4409facebd949c047a8d1e47 233440 gr-limesdr_3.0.1-1_amd64.deb
 9c7cd684131b5b0dd010d0af396977a3f1364749 777384 
libgnuradio-limesdr3.0.1-dbgsym_3.0.1-1_amd64.deb
 5d24aac9b6c82513140e98270f72c423960f90db 52608 
libgnuradio-limesdr3.0.1_3.0.1-1_amd64.deb
Checksums-Sha256:
 e7886262dd058c9c7742a725e96617fce358a72b687d9f3e016a289fc4d6990d 2269 
gr-limesdr_3.0.1-1.dsc
 b18442b744f4411439edb0d384186053d54360d7daadcb0b47a2ddad45e17aed 2992883 
gr-limesdr_3.0.1.orig.tar.gz
 2056ce0e8201e7cf30549c74e8c7b0b6238dd36a6e17a6bcb8584e8e2a77647f 3492 
gr-limesdr_3.0.1-1.debian.tar.xz
 84c725209333f7b4c4e6c4dd3d83f0886c45820c9c66cff464cfcc5e24a34a3d 834272 
gr-limesdr-dbgsym_3.0.1-1_amd64.deb
 cf7aa266743edc2ff769f635e3b63f14c54d08c2a2bc19a7076f9818a76fb659 17878 
gr-limesdr_3.0.1-1_amd64.buildinfo
 196ba8fd1af96509af9d000b4b0485e88cca018530842c3765085ddd413b6e43 233440 
gr-limesdr_3.0.1-1_amd64.deb
 c0d6a0c8b2b6467caf9e52755d533b7e977db3d2f70fe21c98d36e4d6535860c 777384 
libgnuradio-limesdr3.0.1-dbgsym_3.0.1-1_amd64.deb
 1196b0bf9a992964b4e3d5fdfb06da335063296c198480e0fb4b18e13812b3f9 52608 
libgnuradio-limesdr3.0.1_3.0.1-1_amd64.deb
Files:
 81324052fce847679f588c699a7b43ce 2269 hamradio optional gr-limesdr_3.0.1-1.dsc
 9771a271177242030697ab9e76000619 2992883 hamradio optional 
gr-limesdr_3.0.1.orig.tar.gz
 c1f8517a233f9b3b8bd0e8eccc2da261 3492 hamradio optional 
gr-limesdr_3.0.1-1.debian.tar.xz
 6b5b64b82ee2d46bf9576fee7972623e 834272 debug optional 
gr-limesdr-dbgsym_3.0.1-1_amd64.deb
 a9c4050c980542d5c3f9a5549f4eabff 17878 hamradio optional 
gr-limesdr_3.0.1-1_amd64.buildinfo
 b6d618e7843c7f646a14520de51ad12c 233440 hamradio optional 
gr-limesdr_3.0.1-1_amd64.deb
 8ff73ec988a706b97e6087fafb4180ef 777384 debug optional 
libgnuradio-limesdr3.0.1-dbgsym_3.0.1-1_amd64.deb
 ec29f0f0b99d9de66568fe8b8364cf16 52608 libs optional 
libgnuradio-limesdr3.0.1_3.0.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl43OQIACgkQTFprqxLS
p6

Processed: reassign 950445 to ftp.debian.org ...

2020-02-02 Thread Debian Bug Tracking System

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

> reassign 950445 ftp.debian.org
Bug #950445 [python-couchdb] python-couchdb: should this package be removed?
Bug reassigned from package 'python-couchdb' to 'ftp.debian.org'.
No longer marked as found in versions python-couchdb/0.10-1.1.
Ignoring request to alter fixed versions of bug #950445 to the same values 
previously set
> retitle 950445 RM: python-couchdb -- RoQA; python2-only; leaf package; 
> deprecated upstream
Bug #950445 [ftp.debian.org] python-couchdb: should this package be removed?
Changed Bug title to 'RM: python-couchdb -- RoQA; python2-only; leaf package; 
deprecated upstream' from 'python-couchdb: should this package be removed?'.
> thanks
Stopping processing here.

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

Processed: reassign 949859 to ftp.debian.org ...

2020-02-02 Thread Debian Bug Tracking System

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

> reassign 949859 ftp.debian.org
Bug #949859 [src:google-apputils-python] google-apputils-python: should this 
package be removed?
Bug reassigned from package 'src:google-apputils-python' to 'ftp.debian.org'.
No longer marked as found in versions google-apputils-python/0.4.1-1.
Ignoring request to alter fixed versions of bug #949859 to the same values 
previously set
> retitle 949859 RM: google-apputils-python -- RoQA; leaf package; deprecated 
> upstream; RC buggy
Bug #949859 [ftp.debian.org] google-apputils-python: should this package be 
removed?
Changed Bug title to 'RM: google-apputils-python -- RoQA; leaf package; 
deprecated upstream; RC buggy' from 'google-apputils-python: should this 
package be removed?'.
> thanks
Stopping processing here.

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

Bug#950169: marked as done (gexiv2 ftbfs with libexiv2-27)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Sun, 02 Feb 2020 23:41:54 +
with message-id 
and subject line Bug#950169: fixed in gexiv2 0.12.0-2
has caused the Debian Bug report #950169,
regarding gexiv2 ftbfs with libexiv2-27
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.)


-- 
950169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gexiv2
Version: 0.12.0-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.

Paul

Tail of log for gexiv2 on amd64:

../gexiv2/gexiv2-metadata.cpp:184:14: error: conflicting return type
specified for ‘virtual long int {anonymous}::GioIo::size() const’
  184 | long int size() const {
  |  ^~~~
In file included from /usr/include/exiv2/exiv2.hpp:34,
 from ../gexiv2/gexiv2-metadata-private.h:14,
 from ../gexiv2/gexiv2-metadata.cpp:12:
/usr/include/exiv2/basicio.hpp:213:24: note: overridden function is
‘virtual size_t Exiv2::BasicIo::size() const’
  213 | virtual size_t size() const = 0;
  |^~~~
[6/23] c++ -Igexiv2/1a6c516@@gexiv2@sha -Igexiv2 -I../gexiv2 -Igexiv2/..
-I../gexiv2/.. -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount
-I/usr/include/blkid -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c++11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-gps.cpp.o' -MF
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-gps.cpp.o.d' -o
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-gps.cpp.o' -c
../gexiv2/gexiv2-metadata-gps.cpp
[7/23] c++ -Igexiv2/1a6c516@@gexiv2@sha -Igexiv2 -I../gexiv2 -Igexiv2/..
-I../gexiv2/.. -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount
-I/usr/include/blkid -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c++11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-exif.cpp.o' -MF
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-exif.cpp.o.d' -o
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-exif.cpp.o' -c
../gexiv2/gexiv2-metadata-exif.cpp
[8/23] c++ -Igexiv2/1a6c516@@gexiv2@sha -Igexiv2 -I../gexiv2 -Igexiv2/..
-I../gexiv2/.. -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount
-I/usr/include/blkid -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c++11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-iptc.cpp.o' -MF
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-iptc.cpp.o.d' -o
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-iptc.cpp.o' -c
../gexiv2/gexiv2-metadata-iptc.cpp
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja
-j4 -v returned exit code 1
make: *** [debian/rules:13: binary-arch] Error 25



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gexiv2
Source-Version: 0.12.0-2

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

Debian distribution maintenance software
pp.
Jason Crain  (supplier of updated gexiv2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 04:29:42 -0700
Source: gexiv2
Architecture: source
Version: 0.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Jason Crain 
Changed-By: Jason Crain 
Closes: 942519 950169
Changes:
 gexiv2 (0.12.0-2) unstable; urgency=medium
 .
   * Drop patch Use-exiv2-version-0.25.patch.
 Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
 can build a

Bug#947995: ncbi-entrez-direct: ncbi-entrez-direct FTBFS in testing/unstable

2020-02-02 Thread Aaron M. Ucko

> If any of the commits was not helpful just rebase.

Thanks!  I've uploaded with your generic commits cherry-picked (and a
bunch of changes of my own), but Salsa rejected my force pushes to
protected branches.  Could you please adjust the project's permissions?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: py2removal bugs severity updates - 2020-02-03 03:35:41.061989+00:00

2020-02-02 Thread Debian Bug Tracking System

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-mpmath is a module and has 0 external rdeps or not in testing
> severity 937089 serious
Bug #937089 [src:mpmath] mpmath: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-pyglet is a module and has 0 external rdeps or not in testing
> severity 937445 serious
Bug #937445 [src:pyglet] pyglet: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-serial is a module and has 0 external rdeps or not in testing
> severity 937533 serious
Bug #937533 [src:pyserial] pyserial: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-gmpy is a module and has 0 external rdeps or not in testing
> severity 937791 serious
Bug #937791 [src:python-gmpy] python-gmpy: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#947995: marked as done (ncbi-entrez-direct FTBFS in testing/unstable)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Mon, 03 Feb 2020 03:53:53 +
with message-id 
and subject line Bug#947995: fixed in ncbi-entrez-direct 12.0.20190816+ds-1
has caused the Debian Bug report #947995,
regarding ncbi-entrez-direct FTBFS in testing/unstable
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.)


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

source: ncbi-entrez-direct
version: 10.9.20190219+ds-1
severity: serious
tags: bullseye, sid, ftbfs

ncbi-entrez-direct FTBFS in testing/unstable, I first noticed this on a 
raspbian autobuilder, but it's also happening on the reproducible builds tests, 
so it's not raspbian specific.


go build -v -gccgoflags '-g -O2 
-ffile-prefix-map=/build/1st/ncbi-entrez-direct-10.9.20190219+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed' -o bin/xtract \
 xtract.go common.go
go build: when using gc toolchain, please pass compile flags using -gcflags, 
and linker flags using -ldflags
failed to initialize build cache at /nonexistent/first-build/.cache/go-build: 
mkdir /nonexistent: permission denied
make[1]: *** [debian/rules:84: override_dh_auto_build] Error 1


--- End Message ---
--- Begin Message ---
Source: ncbi-entrez-direct
Source-Version: 12.0.20190816+ds-1

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated ncbi-entrez-direct 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: Sun, 02 Feb 2020 22:02:43 -0500
Source: ncbi-entrez-direct
Architecture: source
Version: 12.0.20190816+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 947995
Changes:
 ncbi-entrez-direct (12.0.20190816+ds-1) unstable; urgency=medium
 .
   [ Aaron M. Ucko ]
   * New upstream release.  (Not fully caught up, but uploading anyway to
 address an FTBFS bug that turned up.)
   * debian/control:
 - Build-depend on github-gedex-inflector-dev.
 - Declare a nominal XS-Go-Import-Path to placate dh-golang.
   * debian/examples: Install BioThings support as examples for now: bt-*
 (including one data file currently expected to live alongside scripts)
 and xplore.
   * debian/man/{download-ncbi-data,esample,exclude-uid-lists,index-bioc,j2x,
 pm-collect,xml2tbl}.1: Document new commands.
   * debian/man/{download-{pubmed,sequence},efetch,efilter,esearch,fetch-pubmed,
 ftp-{cp,ls},index-pubmed,intersect-uid-lists,nquire,pm-index,rchive,
 transmute,xtract}.1: Update for new release.
   * debian/man/download-sequence.1: Fix copy-and-paste error (wrong name
 left in DESCRIPTION).
   * debian/rules:
 - Belatedly use FIX_PERL_SHEBANG for bin/edirect.
 - Factor out GH and GL macros for github.com and golang.org respectively.
 - Factor out a pattern rule for building Go executables (and a
   supporting rule for the gounidecode compatibility symlink).
 - Add $(GH)/gedex/inflector to GOLIBSRC_ (for xtract).
 - Account for new download script download-ncbi-data; as-is scripts
   esample, exclude-uid-lists, index-bioc, pm-collect, and xml2tbl; and Go
   executable j2x (which does not use common.go).
 - Set GOCACHE to avoid needing a writable (or simply existent!) HOME;
   wipe the cache in override_dh_auto_clean.  (Closes: 947995.)
   * .gitignore: Ignore the new go-cache tree.
 .
   [ Andreas Tille ]
   * d/watch: simplify + version=4
   * Standards-Version: 4.5.0 (routine-update)
   * debhelper-compat 12 (routine-update)
Checksums-Sha1:
 0248ea599892ca50dfda09c7395d7e78541d62c7 2575 
ncbi-entrez-direct_12.0.20190816+ds-1.dsc
 3c346cd1b9b6dd9be30d87ffb40d919c5cde19a4 150844 
ncbi-entrez-direct_12.0.20190816+ds.orig.tar.xz
 b6ce4fc226af8c7d00701482161b164bb012c499 26660 
ncbi-entrez-direct_12.0.20190816+ds-1.debian.tar.xz
Checksums-Sha256:
 c70582a001882ff0555403cb9af3e6ea4e8e917f

Bug#950099: marked as done (fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists")

2020-02-02 Thread Debian Bug Tracking System

Your message dated Mon, 03 Feb 2020 05:15:10 +0100
with message-id 
and subject line fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"
has caused the Debian Bug report #950099,
regarding fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"
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.)


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

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

...
  debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/fonts-inter-3.11'
fontmake -i -o otf -g src/Inter.glyphs
INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs 
source
INFO:glyphsLib.classes:Parsing "src/Inter.glyphs" file into 
Traceback (most recent call last):
  File "/usr/bin/fontmake", line 11, in 
load_entry_point('fontmake==2.0.7', 'console_scripts', 'fontmake')()
  File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 425, in main
project.run_from_glyphs(glyphs_path, **args)
  File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 670, in 
run_from_glyphs
write_skipexportglyphs=write_skipexportglyphs,
  File "/usr/lib/python3/dist-packages/fontTools/misc/loggingTools.py", line 
367, in wrapper
return func(*args, **kwds)
  File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 156, in 
build_master_ufos
ufo_module=ufoLib2,
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/__init__.py", line 
111, in to_designspace
return builder.designspace
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/builders.py", line 
260, in designspace
list(self.masters)  # Make sure that the UFOs are built
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/builders.py", line 
222, in masters
ufo_glyph = ufo_layer.newGlyph(glyph.name)
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/layer.py", line 120, in 
newGlyph
raise KeyError("glyph %r already exists" % name)
KeyError: "glyph 'asterisk' already exists"
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---

Same like,
https://bugs.debian.org/950103--- End Message ---

Bug#937791: Blocked on reverse dependencies

2020-02-02 Thread Sandro Tosi

> > $ apt-cache rdepends python-gmpy
> > python-gmpy
> > Reverse Depends:
> >obfsproxy
> >python-tlslite-ng
> >python-sympy
> >python-gmpy-doc
> >
> >
>
> Dependencies on obfsproxy and python-sympy documented with affects and
> blocks. python-tlslite-ng has been removed already,

there are no more reverse dependencies on python-gmpy, what should we
do next? i see the source package doesnt produce any python3 package,
and the last changelog entry contains:

  * Override python-foo-but-no-python3-foo Lintian warning, since this package
is end-of-life after Python 2 support ends.

should we remove this package then? or do you want to generate a python3-gmpy?

> and we can rename
> python-gmpy-doc to python3-gmpy-doc once the blocking bugs are resolved.

please dont, -doc package must preserve the python- prefix.

Cheers,
Sandro

Processed: Bug#937089 marked as pending in mpmath

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #937089 [src:mpmath] mpmath: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#937089: marked as pending in mpmath

2020-02-02 Thread Sandro Tosi

Control: tag -1 pending

Hello,

Bug #937089 in mpmath 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/python-team/modules/mpmath/commit/87e752fc36e1ec78272e95334504942c86a1b08a


Drop python2 support; Closes: #937089


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937089

Bug#947995: ncbi-entrez-direct: ncbi-entrez-direct FTBFS in testing/unstable

2020-02-02 Thread Andreas Tille

On Sun, Feb 02, 2020 at 10:30:31PM -0500, Aaron M. Ucko wrote:
> > If any of the commits was not helpful just rebase.
> 
> Thanks!  I've uploaded with your generic commits cherry-picked (and a
> bunch of changes of my own), but Salsa rejected my force pushes to
> protected branches.  Could you please adjust the project's permissions?

Done (hopefully), Andreas. 

-- 
http://fam-tille.de

Bug#937089: marked as done (mpmath: Python2 removal in sid/bullseye)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Mon, 03 Feb 2020 05:19:29 +
with message-id 
and subject line Bug#937089: fixed in mpmath 1.1.0-2
has caused the Debian Bug report #937089,
regarding mpmath: 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.)


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

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: mpmath
Source-Version: 1.1.0-2

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated mpmath package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 00:03:56 -0500
Source: mpmath
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 937089
Changes:
 mpmath (1.1.0-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937089
   * debian/control
 - bump Standards-Version to 4.5.0 (no changes needed)
   * debian/copyright
 - extend packaging copyright years
   * Add upstream metadata information
Checksums-Sha1:
 07c1bcf5fcb810b9ee96f1689fb23400d757a869 2129 mpmath_1.1.0-2.dsc
 49e333a5e4811ac88258ccae343118b68b4b3018 5852 mpmath_1.1.0-2.debian.tar.xz
 3900c5cff5882003a306b5c78a5d2c97a0fb84ad 6274 mpmath_1.1.0-2_source.buildinfo
Checksums-Sha256:
 f390e7bde893b6554ff0674b004dbc2f98b08efe1045d4b64d2e93178af0458f 2129 
mpmath_1.1.0-2.dsc
 a30dbbaa42ab5f72235f45fbbb2b0a283741ff34cd2d3de20eec4e88ac4e4ac9 5852 
mpmath_1.1.0-2.debian.tar.xz
 0caba4491a01c9f36454c8679aacada207431d9096a2c3eebab6a91c42ec62e7 6274 
mpmath_1

Bug#950525: broken symlink: /usr/lib/gcc//9/libgcc_s.so{,.1}

2020-02-02 Thread YunQiang Su

Package: src:gcc-9
Version: 9.2.1-25
Severity: serious
X-Debug-Cc: debian-s...@lists.debian.org

On i386
# file /usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1
/usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1: broken symbolic link to
/lib/i386-linux-gnu/libgcc_s.so.1

On s390x:
$ file /usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so*
/usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so: broken symbolic link to
/lib/s390x-linux-gnu/libgcc_s.so.1

Which make some packages ftbfs on s390x:
https://buildd.debian.org/status/fetch.php?pkg=zlib&arch=s390x&ver=1%3A1.2.11.dfsg-1.2&stamp=1580704985&raw=0

Bug#950525: broken symlink: /usr/lib/gcc//9/libgcc_s.so{,.1}

2020-02-02 Thread Matthias Klose

On 2/3/20 6:39 AM, YunQiang Su wrote:
> Package: src:gcc-9
> Version: 9.2.1-25
> Severity: serious
> X-Debug-Cc: debian-s...@lists.debian.org
> 
> On i386
> # file /usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1
> /usr/lib/gcc/i686-linux-gnu/9/libgcc_s.so.1: broken symbolic link to
> /lib/i386-linux-gnu/libgcc_s.so.1
> 
> On s390x:
> $ file /usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so*
> /usr/lib/gcc/s390x-linux-gnu/9/libgcc_s.so: broken symbolic link to
> /lib/s390x-linux-gnu/libgcc_s.so.1
> 
> Which make some packages ftbfs on s390x:
> https://buildd.debian.org/status/fetch.php?pkg=zlib&arch=s390x&ver=1%3A1.2.11.dfsg-1.2&stamp=1580704985&raw=0

yes, fix in progress, although I need some disk space on zelenka ...

Processed: unarchiving 744698, reopening 744698, unarchiving 787350, reopening 787350, unarchiving 799311 ...

2020-02-02 Thread Debian Bug Tracking System

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

> # these bugs were open when the package was removed, reopening them after it 
> was reintroduced
> unarchive 744698
Bug #744698 {Done: Debian FTP Masters } 
[src:fontmatrix] [fontmatrix] [DFSG] missing source
Unarchived Bug 744698
> reopen 744698
Bug #744698 {Done: Debian FTP Masters } 
[src:fontmatrix] [fontmatrix] [DFSG] missing source
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 787350
Bug #787350 {Done: Debian FTP Masters } 
[src:fontmatrix] [RC][cc-by-nc-sa] Please clarify license of a few svg files
Unarchived Bug 787350
> reopen 787350
Bug #787350 {Done: Debian FTP Masters } 
[src:fontmatrix] [RC][cc-by-nc-sa] Please clarify license of a few svg files
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 799311
Bug #799311 {Done: Debian FTP Masters } 
[src:fontmatrix] fontmatrix: FTBFS: error: invalid new-expression of abstract 
class type 'IcuFontImpl'
Bug #854596 {Done: Debian FTP Masters } 
[src:fontmatrix] fontmatrix: uninstallable -at least under stretch, fontmatrix 
: Dépend: libicu52 (>= 52~m1-1~) which is a virtual package and is not provided 
by any available package
Unarchived Bug 799311
Unarchived Bug 854596
> reopen 799311
Bug #799311 {Done: Debian FTP Masters } 
[src:fontmatrix] fontmatrix: FTBFS: error: invalid new-expression of abstract 
class type 'IcuFontImpl'
Bug #854596 {Done: Debian FTP Masters } 
[src:fontmatrix] fontmatrix: uninstallable -at least under stretch, fontmatrix 
: Dépend: libicu52 (>= 52~m1-1~) which is a virtual package and is not provided 
by any available package
'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 0.6.0+svn20110930-1.1+rm.
No longer marked as fixed in versions 0.6.0+svn20110930-1.1+rm.
> unarchive 579314
Bug #579314 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: does not see TTC fonts
Unarchived Bug 579314
> reopen 579314
Bug #579314 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: does not see TTC fonts
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 602823
Bug #602823 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: No documentation available
Unarchived Bug 602823
> reopen 602823
Bug #602823 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: No documentation available
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 784463
Bug #784463 {Done: Debian FTP Masters } 
[src:fontmatrix] [fontmatrix] Qt4's WebKit removal
Unarchived Bug 784463
> reopen 784463
Bug #784463 {Done: Debian FTP Masters } 
[src:fontmatrix] [fontmatrix] Qt4's WebKit removal
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 545187
Bug #545187 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: Does not handle removed fonts well -> Segmentation 
fault
Unarchived Bug 545187
> reopen 545187
Bug #545187 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: Does not handle removed fonts well -> Segmentation 
fault
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 607148
Bug #607148 {Done: Debian FTP Masters } 
[fontmatrix] Fix FTBFS with ld --as-needed
Unarchived Bug 607148
> reopen 607148
Bug #607148 {Done: Debian FTP Masters } 
[fontmatrix] Fix FTBFS with ld --as-needed
'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 0.6.0+svn20110930-1.1+rm.
> unarchive 623475
Bug #623475 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: does not have name for some unicode ranges
Unarchived Bug 623475
> reopen 623475
Bug #623475 {Done: Debian FTP Masters } 
[fontmatrix] fontmatrix: does not have name for some unicode ranges
'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 reope

Bug#937445: marked as pending in pyglet

2020-02-02 Thread Sandro Tosi

Control: tag -1 pending

Hello,

Bug #937445 in pyglet 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/python-team/modules/pyglet/commit/290705fb3dcee6371631781b2c729cf1a2850d1a


Drop python2 support; Closes: #937445


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937445

Processed: Bug#937445 marked as pending in pyglet

2020-02-02 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #937445 [src:pyglet] pyglet: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#937445: marked as done (pyglet: Python2 removal in sid/bullseye)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Mon, 03 Feb 2020 07:20:44 +
with message-id 
and subject line Bug#937445: fixed in pyglet 1.4.10-1
has caused the Debian Bug report #937445,
regarding pyglet: 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.)


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

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: pyglet
Source-Version: 1.4.10-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyglet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 01:55:30 -0500
Source: pyglet
Architecture: source
Version: 1.4.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937445 950039
Changes:
 pyglet (1.4.10-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * New upstream release
 - ensure compatibility with python 3.8; Closes: #950039
   * debian/watch
 - update to detect even latest upstream releases
   * debian/copyright
 - add proper upstream copyright notice
   * debian/patches
 - drop, refresh, update patches
   * Drop python2 support; Closes: #937445
   * debian/rules
 - exclude also test_player_silent_audio_driver tests
   * debian/docs
 - install README.md, renamed from README
Checksums-Sha1:
 31109a1a8c0483572ce888fffea78180c4fab267 2443 pyglet_1.4.10-1.dsc
 0490f63b06336f95fcb97cb48fe9c98bb7684218 3496600 pyglet_1.4.10.orig.tar.xz
 76cdfe879843c797fb33

Bug#950039: marked as done (pyglet FTBFS with Python 3.8 as supported version)

2020-02-02 Thread Debian Bug Tracking System

Your message dated Mon, 03 Feb 2020 07:20:44 +
with message-id 
and subject line Bug#950039: fixed in pyglet 1.4.10-1
has caused the Debian Bug report #950039,
regarding pyglet FTBFS with Python 3.8 as supported version
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.)


-- 
950039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyglet
Version: 1.4.1-3
Severity: serious
Tags: ftbfs

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

...
I: pybuild base:217: cd 
/build/1st/pyglet-1.4.1/.pybuild/cpython3_3.8_pyglet/build; python3.8 -m pytest 
>/dev/null 2>&1; cd /build/1st/pyglet-1.4.1/.pybuild/cpython3_3.8_pyglet/build; 
xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac 
+extension GLX +render -noreset" python3.8 -m pytest -v -k " not interactive 
and not PulseAudio and not test_pulse and not test_player_play and not 
test_player_play_multiple and not test_freetype_face and not test_fontconfig 
and not test_linux_fontconfig and not test_driver and not test_openal and not 
ClockTimingTestCase"
ImportError while loading conftest 
'/build/1st/pyglet-1.4.1/.pybuild/cpython3_3.8_pyglet/build/tests/conftest.py'.
tests/conftest.py:18: in 
from .base.event_loop import event_loop
tests/base/event_loop.py:10: in 
from pyglet.graphics import Batch
pyglet/graphics/__init__.py:171: in 
from pyglet.gl import *
pyglet/gl/__init__.py:222: in 
from .xlib import XlibConfig as Config
pyglet/gl/xlib.py:40: in 
from pyglet.canvas.xlib import XlibCanvas
pyglet/canvas/__init__.py:112: in 
from pyglet.canvas.xlib import XlibDisplay as Display
pyglet/canvas/xlib.py:53: in 
from . import xlib_vidmoderestore
pyglet/canvas/xlib_vidmoderestore.py:57: in 
from pyglet.libs.x11 import xlib
pyglet/libs/x11/xlib.py:2962: in 
XEHeadOfExtensionList.argtypes = [XEDataObject]
E   TypeError: item 1 in _argtypes_ passes a union by value, which is 
unsupported.
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=4: cd 
/build/1st/pyglet-1.4.1/.pybuild/cpython3_3.8_pyglet/build; python3.8 -m pytest 
>/dev/null 2>&1; cd {build_dir}; xvfb-run --auto-servernum --server-num=20 -s 
"-screen 0 1024x768x24 -ac +extension GLX +render -noreset" python{version} -m 
pytest -v -k " not interactive and not PulseAudio and not test_pulse and not 
test_player_play and not test_player_play_multiple and not test_freetype_face 
and not test_fontconfig and not test_linux_fontconfig and not test_driver and 
not test_openal and not ClockTimingTestCase"
dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned 
exit code 13
make: *** [debian/rules:32: build] Error 25
--- End Message ---
--- Begin Message ---
Source: pyglet
Source-Version: 1.4.10-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyglet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Feb 2020 01:55:30 -0500
Source: pyglet
Architecture: source
Version: 1.4.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937445 950039
Changes:
 pyglet (1.4.10-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * New upstream release
 - ensure compatibility with python 3.8; Closes: #950039
   * debian/watch
 - update to detect even latest upstream releases
   * debian/copyright
 - add proper upstream copyright notice
   * debian/patches
 - drop, refresh, update patches
   * Drop python2 support; Closes: #937445
   * debian/rules
 - exclude also test_player_silent_audio_driver tests
   * debian/docs
 - install README.md, renamed from README
Checksums-Sha1:
 31109a1a8c0483572ce888fffea78180c4fab267 2443 pyglet_1.4.10-1.dsc
 0490f63b06336f95fcb97cb48fe9c98bb7684218 3496600 pyglet_1.4.10.orig.tar.xz
 76cdfe8

Bug#950300: Fixed in upstream version 0.9.1

2020-02-02 Thread Fiona Klute

This has been fixed upstream since version 0.9.1.

89 matches

Mail list logo