Bug#1008286: Should nglister be removed?

[John Goerzen]

severity 1008286 normal
reassign 1008286 ftp.debian.org
retitle 1008286 RM: nglister -- RoM; unmaintained
thx


On Fri, Mar 25 2022, Moritz Muehlenhoff wrote:

> Source: nglister
> Version: 1.0.2
> Severity: serious
>
> Your package came up as a candidate for removal from Debian:
>
> - Last upload in 2016
> - Removed from testing since 2019
> - Multiple RC bugs
>
> If you disagree and want to continue to maintain this package,
> please just close this bug (and fix the open issues).
>
> If you agree with the removal, please reassign to ftp.debian.org
> by sending the following commands to cont...@bugs.debian.org:
>
> --
> severity $BUGNUM normal
> reassign $BUGNUM ftp.debian.org
> retitle $BUGNUM RM:  -- RoM; 
> thx
> --
>
> Otherwise I'll move forward and request it's removal in a month.
>
> Cheers,
> Moritz

Processed (with 5 errors): Re: Bug#1008286: Should nglister be removed?

[Debian Bug Tracking System]

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

> severity 1008286 normal
Bug #1008286 [src:nglister] Should nglister be removed?
Severity set to 'normal' from 'serious'
> reassign 1008286 ftp.debian.org
Bug #1008286 [src:nglister] Should nglister be removed?
Bug reassigned from package 'src:nglister' to 'ftp.debian.org'.
No longer marked as found in versions nglister/1.0.2.
Ignoring request to alter fixed versions of bug #1008286 to the same values 
previously set
> retitle 1008286 RM: nglister -- RoM; unmaintained
Bug #1008286 [ftp.debian.org] Should nglister be removed?
Changed Bug title to 'RM: nglister -- RoM; unmaintained' from 'Should nglister 
be removed?'.
> thx
Unknown command or malformed arguments to command.
> On Fri, Mar 25 2022, Moritz Muehlenhoff wrote:
Unknown command or malformed arguments to command.
> > Source: nglister
Unknown command or malformed arguments to command.
> > Version: 1.0.2
Unknown command or malformed arguments to command.
> > Severity: serious
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#1008265: CVE-2018-25032: zlib memory corruption on deflate

[Mark Brown]

On Fri, Mar 25, 2022 at 10:50:51PM +0100, Salvatore Bonaccorso wrote:

> Here is a preliminary debdiff to address this.

Thanks, that's roughly what I uploaded - it looks like your mail
raced with my own update.


signature.asc
Description: PGP signature

Bug#1007234: Test suite fails on all but amd64 arches

[Bryan Henderson]

I don't know familiar you are with debuggers, C, or C arithmetic, so I'm
attaching a diagnostic version of the program and will also explain where I
think the problem lies in case you want to investigate on your own.

If you put this .c file in converter/other/pnmtopalm/ and rebuild and run the
'palmtopnm' executable that results, it should detect the failure and write
some useful diagnostic messages.  Tell me what happens.


The problem is in function 'readPackBitsRow16'.  The variable 'j' is getting
too large -- absurdly large, apparently because a bit code that is supposed to
encode a negative signed integer is being interpreted as a positive unsigned
one somewhere.  It should not be hard to pinpoint where the arithmetic is
generating such a a large number.

-- 
Bryan Henderson   San Jose, California/**
 palmtopnm
***
  By Bryan Henderson, San Jose, California, June 2004.

  Inspired by and using methods from Tbmptopnm by Ian Goldberg
  , and Bill Janssen .

  Major fixes and new capability added by Paul Bolle 
  in late 2004 / early 2005.

  Bryan's work is contributed to the public domain by its author.
**/

#include 
#include 

#include "pm_c_util.h"
#include "pnm.h"
#include "shhopt.h"
#include "mallocvar.h"

#include "palm.h"
#include "palmcolormap.h"



enum PalmCompressionType {
COMPRESSION_NONE,
COMPRESSION_RLE,
COMPRESSION_SCANLINE,
COMPRESSION_PACKBITS
};

struct PalmHeader {
unsigned short cols;
unsigned short rows;
unsigned short bytesPerRow;
unsigned short flags;
bool   directColor;
/* The header indicates a direct color raster, either by flag
   (the old way) or by pixel format (the new way)
*/
bool   hasColormap;
bool   hasTransparency;
unsigned char  pixelSizeCode;
unsigned int   pixelSize;
unsigned char  version;
unsigned int   transparentIndex;
enum PalmCompressionType compressionType;
/* version 3 encoding specific */
unsigned char  size;
unsigned char  pixelFormat;
unsigned short density;
unsigned long  transparentValue;
};



struct DirectPixelFormat {
unsigned int redbits;
unsigned int greenbits;
unsigned int bluebits;
};



struct DirectColorInfo {
struct DirectPixelFormat pixelFormat;
ColormapEntrytransparentColor;
};




struct CmdlineInfo {
/* All the information the user supplied in the command line,
   in a form easy for the program to use.
*/
const char * inputFilespec;
unsigned int verbose;
unsigned int rendition;
unsigned int showhist;
unsigned int transparent;
};


static void
parseCommandLine(int argc, const char ** argv,
 struct CmdlineInfo *cmdlineP) {
/*
   Note that the file spec array we return is stored in the storage that
   was passed to us as the argv array.
-*/
optEntry * option_def;
/* Instructions to pm_optParseOptions3 on how to parse our options.
 */
optStruct3 opt;

unsigned int renditionSpec;

unsigned int option_def_index;

MALLOCARRAY_NOFAIL(option_def, 100);

option_def_index = 0;   /* incremented by OPTENTRY */
OPTENT3(0, "verbose", OPT_FLAG, NULL,
>verbose,  0);
OPTENT3(0, "showhist",OPT_FLAG, NULL,
>showhist, 0);
OPTENT3(0, "transparent",OPT_FLAG, NULL,
>transparent, 0);
OPTENT3(0, "rendition",  OPT_UINT, >rendition,
, 0);

opt.opt_table = option_def;
opt.short_allowed = FALSE;  /* We have no short (old-fashioned) options */
opt.allowNegNum = FALSE;  /* We may have parms that are negative numbers */

pm_optParseOptions3(, (char **)argv, opt, sizeof(opt), 0);
/* Uses and sets argc, argv, and some of *cmdlineP and others. */


if (renditionSpec) {
if (cmdlineP->rendition < 1)
pm_error("The -rendition value must be at least 1");
} else
cmdlineP->rendition = 1;

if (cmdlineP->transparent && cmdlineP->showhist)
pm_error("You can't specify -showhist with -transparent");

if (argc-1 < 1)
cmdlineP->inputFilespec = "-";
else {
cmdlineP->inputFilespec = argv[1];
if (argc-1 > 1)
pm_error("Too many arguments (%d).  The only non-option "
 "argument is the file name", argc-1);
}
free(option_def);
}



static xelval *
createGraymap(unsigned int const ncolors,
  xelval   const maxval) {
int i;
xelval *map;

MALLOCARRAY_NOFAIL(map, ncolors);
  

Bug#1008265: marked as done (CVE-2018-25032: zlib memory corruption on deflate)

[Debian Bug Tracking System]

Your message dated Sat, 26 Mar 2022 00:04:03 +
with message-id 
and subject line Bug#1008265: fixed in zlib 1:1.2.11.dfsg-4
has caused the Debian Bug report #1008265,
regarding CVE-2018-25032: zlib memory corruption on deflate
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.)


-- 
1008265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zlib
Version: 1:1.2.11.dfsg-2
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2018-25032:
https://www.openwall.com/lists/oss-security/2022/03/24/1
https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: zlib
Source-Version: 1:1.2.11.dfsg-4
Done: Mark Brown 

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

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated zlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Mar 2022 23:32:05 +
Source: zlib
Architecture: source
Version: 1:1.2.11.dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 1008265
Changes:
 zlib (1:1.2.11.dfsg-4) unstable; urgency=medium
 .
   * Pick upstream patch for CVE-2018-25032 (closes: #1008265).
Checksums-Sha1:
 d6fb58df5fcb6c8365b82240736ae26e3b7a74d8 2397 zlib_1.2.11.dfsg-4.dsc
 7997cc9e7fffb7f29f50dd7ec7455a383ba192da 23316 zlib_1.2.11.dfsg-4.debian.tar.xz
Checksums-Sha256:
 3ce1b7907cf1b35ffa95b06104d951314c48aa3463b78eddc0025ae59e9537cd 2397 
zlib_1.2.11.dfsg-4.dsc
 b2e66b33c5aeeafa1cd00b2e06e671faf1345fc1ac13e5e2dcb12360df2fd677 23316 
zlib_1.2.11.dfsg-4.debian.tar.xz
Files:
 9fa2b1dd1e8c011079a493f087c30abf 2397 libs optional zlib_1.2.11.dfsg-4.dsc
 6f2c395b7aa8156dc8321f6e03082793 23316 libs optional 
zlib_1.2.11.dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmI+U5gTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0Hx8B/0W9FUwM/qu8+QndlJ3SOvt5J7gZGzL
KC5DhsJOosdPXpqT/1ZMEAWw/QfYvfmGxHgrkGwx8sITG63fffz+Gr2XmiZl6JrW
aQJKsSrJnpgY5FhrK8MFnjDmS0nc3y44ZgVPNinYLpVgPvDKGH2y3PQRmzaGxr0W
P6u5a79HgfJ0028FALPxt/IHXWLTa2gGUQIAqrCcooDoUbqPCgUmjl9/6w41eE28
K5mvthkAutqRQWEJLKwnVyN0PG1WVjB+rmsIqg/pVIkBEsdcANVm+gr+7KivhZfa
WwraQOf6Dab1M4CclY17HGH6tmtf2JQUd5Fn7/yAoontJnppVWjkPDAE
=665W
-END PGP SIGNATURE End Message ---

Bug#1008285: Should zorp be removed?

[Moritz Muehlenhoff]

Source: zorp
Version: 7.0.1~alpha2-3
Severity: serious

Your package came up as a candidate for removal from Debian:

- Last upload in 2019, removed from testing since 2017
- Still depends on Python 2.7 and thus RC-buggy

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008286: Should nglister be removed?

[Moritz Muehlenhoff]

Source: nglister
Version: 1.0.2
Severity: serious

Your package came up as a candidate for removal from Debian:

- Last upload in 2016
- Removed from testing since 2019
- Multiple RC bugs  

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008265: CVE-2018-25032: zlib memory corruption on deflate

[Salvatore Bonaccorso]

Control; tags -1 + patch

Hi Mark,

On Fri, Mar 25, 2022 at 05:31:44PM +0100, Moritz Muehlenhoff wrote:
> Source: zlib
> Version: 1:1.2.11.dfsg-2
> Severity: grave
> Tags: security
> X-Debbugs-Cc: Debian Security Team 
> 
> This was assigned CVE-2018-25032:
> https://www.openwall.com/lists/oss-security/2022/03/24/1
> https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531

Here is a preliminary debdiff to address this.

Regards,
Salvatore
diff -Nru zlib-1.2.11.dfsg/debian/changelog zlib-1.2.11.dfsg/debian/changelog
--- zlib-1.2.11.dfsg/debian/changelog   2022-03-18 01:21:37.0 +0100
+++ zlib-1.2.11.dfsg/debian/changelog   2022-03-25 22:46:38.0 +0100
@@ -1,3 +1,11 @@
+zlib (1:1.2.11.dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix a bug that can crash deflate on some input when using Z_FIXED
+(CVE-2018-25032) (Closes: #1008265)
+
+ -- Salvatore Bonaccorso   Fri, 25 Mar 2022 22:46:38 +0100
+
 zlib (1:1.2.11.dfsg-3) unstable; urgency=low
 
   * Add build-arch and build-indep (#999292).
diff -Nru 
zlib-1.2.11.dfsg/debian/patches/Fix-a-bug-that-can-crash-deflate-on-some-input-when-.patch
 
zlib-1.2.11.dfsg/debian/patches/Fix-a-bug-that-can-crash-deflate-on-some-input-when-.patch
--- 
zlib-1.2.11.dfsg/debian/patches/Fix-a-bug-that-can-crash-deflate-on-some-input-when-.patch
  1970-01-01 01:00:00.0 +0100
+++ 
zlib-1.2.11.dfsg/debian/patches/Fix-a-bug-that-can-crash-deflate-on-some-input-when-.patch
  2022-03-25 22:46:38.0 +0100
@@ -0,0 +1,347 @@
+From: Mark Adler 
+Date: Tue, 17 Apr 2018 22:09:22 -0700
+Subject: Fix a bug that can crash deflate on some input when using Z_FIXED.
+Origin: 
https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531
+Bug-Debian: https://bugs.debian.org/1008265
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-25032
+
+This bug was reported by Danilo Ramos of Eideticom, Inc. It has
+lain in wait 13 years before being found! The bug was introduced
+in zlib 1.2.2.2, with the addition of the Z_FIXED option. That
+option forces the use of fixed Huffman codes. For rare inputs with
+a large number of distant matches, the pending buffer into which
+the compressed data is written can overwrite the distance symbol
+table which it overlays. That results in corrupted output due to
+invalid distances, and can result in out-of-bound accesses,
+crashing the application.
+
+The fix here combines the distance buffer and literal/length
+buffers into a single symbol buffer. Now three bytes of pending
+buffer space are opened up for each literal or length/distance
+pair consumed, instead of the previous two bytes. This assures
+that the pending buffer cannot overwrite the symbol table, since
+the maximum fixed code compressed length/distance is 31 bits, and
+since there are four bytes of pending space for every three bytes
+of symbol space.
+---
+ deflate.c | 74 ---
+ deflate.h | 25 +--
+ trees.c   | 50 +++--
+ 3 files changed, 79 insertions(+), 70 deletions(-)
+
+diff --git a/deflate.c b/deflate.c
+index 425babc00c33..19cba873ae98 100644
+--- a/deflate.c
 b/deflate.c
+@@ -255,11 +255,6 @@ int ZEXPORT deflateInit2_(strm, level, method, 
windowBits, memLevel, strategy,
+ int wrap = 1;
+ static const char my_version[] = ZLIB_VERSION;
+ 
+-ushf *overlay;
+-/* We overlay pending_buf and d_buf+l_buf. This works since the average
+- * output size for (length,distance) codes is <= 24 bits.
+- */
+-
+ if (version == Z_NULL || version[0] != my_version[0] ||
+ stream_size != sizeof(z_stream)) {
+ return Z_VERSION_ERROR;
+@@ -329,9 +324,47 @@ int ZEXPORT deflateInit2_(strm, level, method, 
windowBits, memLevel, strategy,
+ 
+ s->lit_bufsize = 1 << (memLevel + 6); /* 16K elements by default */
+ 
+-overlay = (ushf *) ZALLOC(strm, s->lit_bufsize, sizeof(ush)+2);
+-s->pending_buf = (uchf *) overlay;
+-s->pending_buf_size = (ulg)s->lit_bufsize * (sizeof(ush)+2L);
++/* We overlay pending_buf and sym_buf. This works since the average size
++ * for length/distance pairs over any compressed block is assured to be 31
++ * bits or less.
++ *
++ * Analysis: The longest fixed codes are a length code of 8 bits plus 5
++ * extra bits, for lengths 131 to 257. The longest fixed distance codes 
are
++ * 5 bits plus 13 extra bits, for distances 16385 to 32768. The longest
++ * possible fixed-codes length/distance pair is then 31 bits total.
++ *
++ * sym_buf starts one-fourth of the way into pending_buf. So there are
++ * three bytes in sym_buf for every four bytes in pending_buf. Each symbol
++ * in sym_buf is three bytes -- two for the distance and one for the
++ * literal/length. As each symbol is consumed, the pointer to the next
++ * sym_buf value to read moves forward three bytes. 

Processed: found 1008265 in 1:1.2.11.dfsg-1

[Debian Bug Tracking System]

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

> found 1008265 1:1.2.11.dfsg-1
Bug #1008265 [src:zlib] CVE-2018-25032: zlib memory corruption on deflate
Marked as found in versions zlib/1:1.2.11.dfsg-1.
> thanks
Stopping processing here.

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

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

[Thorsten Glaser]

Package: pstoedit
Version: 3.75-1
Severity: serious
Justification: unusable by some users
X-Debbugs-Cc: t...@mirbsd.de, hill...@web.de, debian-tex-ma...@lists.debian.org
Control: affects -1 purifyeps

I’ve noticed purifyeps (which is needed for Tₑχ/LᴬTᴇΧ to process .eps files)
fails on some inputs and could trace this down to pstoedit’s output for the
broken files to be much too small.

I’m attaching the full testcase with sources and all intermediate files.

This is on a bullseye system (plus two debugging prints in purifyeps which
Hilmar should just ignore comparing his output to mine).

The full screen log of the process (from SVG via PDF to EPS) follows, for
a sampling of two files, one of which succeeds, the other doesn’t. Very
noticeable, besides the test-1.mp size, is “x: 99 y: 99 x: 0 y: 0”
(failure) vs. x: 0 y: 0 x: 22 y: 13 (success).


$ inkscape -D --export-filename=test1.pdf --export-type=pdf 
--export-pdf-version=1.4 teckids_logo_image.svg

(inkscape:25600): dbind-WARNING **: 22:09:15.196: AT-SPI: 
Error retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files
$ pdftops -eps test1.pdf test1-a.eps
$ purifyeps test1-a.eps test1-b.eps
D: running: pstoedit -ssp -f mpost -fontmap "/usr/share/pstoedit/mpost.fmp" 
"test1-a.eps" "/tmp/purifyeps-V7yHSU2q.mp" 1>&2
pstoedit: version 3.75 / DLL interface 108 (built: Jan  2 2020 - release build 
- g++ 9.2.1 20191130 - 64-bit) : Copyright (C) 1993 - 2020 Wolfgang Glunz
D: running: echo X | mpost /tmp/purifyeps-V7yHSU2q.mp 1>&2
This is MetaPost, version 2.00 (TeX Live 2020/Debian) (kpathsea version 6.3.2)
(/usr/share/texlive/texmf-dist/metapost/base/mpost.mp
(/usr/share/texlive/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.005) ) (/tmp/purifyeps-V7yHSU2q.mp )
Transcript written on purifyeps-V7yHSU2q.log.
purifyeps: No such file or directory (/tmp/purifyeps-V7yHSU2q.1)
D: tempbase=/tmp/purifyeps-V7yHSU2q
$ pstoedit -v -ssp -f mpost -fontmap "/usr/share/pstoedit/mpost.fmp" 
test1-a.eps test-1.mp
pstoedit: version 3.75 / DLL interface 108 (built: Jan  2 2020 - release build 
- g++ 9.2.1 20191130 - 64-bit) : Copyright (C) 1993 - 2020 Wolfgang Glunz
loading plugins from /usr/lib/x86_64-linux-gnu/pstoedit using suffix: .so
loading plugin: /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvmagick++.so
creating Dynloader for /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvmagick++.so
loading dynamic library /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvmagick++.so 
completed successfully
loading plugin: /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvwmf.so
creating Dynloader for /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvwmf.so
loading dynamic library /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvwmf.so 
completed successfully
loading plugin: /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvlplot.so
creating Dynloader for /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvlplot.so
loading dynamic library /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvlplot.so 
completed successfully
loading plugin: /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvstd.so
creating Dynloader for /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvstd.so
loading dynamic library /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvstd.so 
completed successfully
loading plugin: /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvpptx.so
creating Dynloader for /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvpptx.so
loading dynamic library /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvpptx.so 
completed successfully
path to myself: /usr/bin/pstoedit
pstoedit home directory : /usr/bin
pstoedit data directory : /usr/share/pstoedit
Loading fontmap from /usr/share/pstoedit/mpost.fmp
loading system specific fontmap from /usr/share/pstoedit/windows.fmp

Looking up where to find the PostScript interpreter.
GS not set, trying registry for common/gstocall
nothing found so far, trying default: gs
Value found is:gs

Looking up specific options for the PostScript interpreter.
First trying registry for common/GS_LIB
still not found an entry - now trying GS_LIB env var.
GS_LIB not set
Value returned:

now calling the interpreter via: gs -dDELAYBIND -dWRITESYSTEMDICT -dESTACKPRINT 
-dNODISPLAY -dDELAYSAFER -dNOEPS "/tmp/psine2b20s"
GPL Ghostscript 9.53.3 (2020-10-01)
Copyright (C) 2020 Artifex Software, Inc.  All rights reserved.
This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY:
see the file COPYING for details.
Now checking the temporary output
 got 1 page(s) from /tmp/psoutFgTRot
x: 99 y: 99 x: 0 y: 0
now postprocessing the interpreter output
postprocessing the interpreter output finished
closing dynamic library /usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvmagick++.so
not really closing dynamic library because of pthread problem under Linux - 
contact author for details or check dynload.cpp from pstoedit source code 
/usr/lib/x86_64-linux-gnu/pstoedit/libp2edrvmagick++.so
destroying Dynloader 

Processed: pstoedit: silently fails with success return for some purifyeps use cases

[Debian Bug Tracking System]

Processing control commands:

> affects -1 purifyeps
Bug #1008280 [pstoedit] pstoedit: silently fails with success return for some 
purifyeps use cases
Added indication that 1008280 affects purifyeps

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

Processed: src:libinovasdk: fails to migrate to testing for too long: missing libinovasdk1 in armhf upload

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3.6-2
Bug #1008276 [src:libinovasdk] src:libinovasdk: fails to migrate to testing for 
too long: missing libinovasdk1 in armhf upload
Marked as fixed in versions libinovasdk/1.3.6-2.
Bug #1008276 [src:libinovasdk] src:libinovasdk: fails to migrate to testing for 
too long: missing libinovasdk1 in armhf upload
Marked Bug as done

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

Bug#1008276: src:libinovasdk: fails to migrate to testing for too long: missing libinovasdk1 in armhf upload

[Paul Gevers]

Source: libinovasdk
Version: 1.3.6-1
Severity: serious
Control: close -1 1.3.6-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:libinovasdk has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your build on armhf included 
libinovasdk-dev but not libinovasdk1 on which it depends.


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: important xscreensaver oom

[Debian Bug Tracking System]

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

> severity 1007724 important
Bug #1007724 [xscreensaver] xscreensaver: xscreensaver-auth says it should be 
installed setuid root
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1008274: Should sandsifter be removed?

[Moritz Muehlenhoff]

Source: sandsifter
Version: 1.04-1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still uses Python 2.7 and thus RC buggy
- Last upload in 2019 and not in testing since 2019

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008273: Should python-nemu be removed?

[Moritz Muehlenhoff]

Source: python-nemu
Version: 0.3.1-1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Last upload in 2016 and dropped from testing in 2019
- Still uses Python 2.7 and not fixed upstream either

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008272: Should postnews be removed?

[Moritz Muehlenhoff]

Source: postnews
Version: 0.7-1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Removed from testing for ~ two years, no followup to RC bugs
- Also no changes upstream since 2017

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008271: Should arriero be removed?

[Moritz Muehlenhoff]

Source: arriero
Version: 0.6-1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Last upload in 2017
- Still uses Python 2.7 and thus RC buggy
- Missed the last two stable releases and removed from testing since 2018

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Processed: tagging 1008264

[Debian Bug Tracking System]

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

> tags 1008264 + upstream
Bug #1008264 [src:pluxml] Multiple security issues
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: tagging 1008265

[Debian Bug Tracking System]

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

> tags 1008265 + upstream fixed-upstream
Bug #1008265 [src:zlib] CVE-2018-25032: zlib memory corruption on deflate
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#1001372: marked as done (python-aiosmtpd: autopkgtest tests for all supported python3s but fails to install them)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 19:05:08 +
with message-id 
and subject line Bug#1001372: fixed in python-aiosmtpd 1.4.2-3
has caused the Debian Bug report #1001372,
regarding python-aiosmtpd: autopkgtest tests for all supported python3s but 
fails to install them
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.)


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

Source: python-aiosmtpd
Version: 1.4.2-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python2.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-aiosmtpd fails in testing when that autopkgtest is run with 
the binary packages of python3-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-aiosmtpdfrom testing1.4.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the 
test tries to test for all supported Python3 versions, but fails to 
ensure all those versions are actually installed during the test.


Currently this regression is blocking the migration of python3-defaults 
to testing [1].


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=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-aiosmtpd/17393457/log.gz

/tmp/autopkgtest-lxc.dowwqyup/downtmp/build.d73/src/debian/tests/python3-aiosmtpd: 
line 7: python3.10: command not found

autopkgtest [12:14:23]: test python3-aiosmtpd



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-aiosmtpd
Source-Version: 1.4.2-3
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated python-aiosmtpd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Mar 2022 14:35:59 -0400
Source: python-aiosmtpd
Architecture: source
Version: 1.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1001372
Changes:
 python-aiosmtpd (1.4.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Depend on python3-all for the autopkgtest. (Closes: #1001372)
   * Patch: Python 3.10 support.
Checksums-Sha1:
 ceee0b9c222759ded778df86f8fc4189e4ab9f0a 1711 python-aiosmtpd_1.4.2-3.dsc
 6b94a860e393a39db664a3eb963a4abd891a0f47 8708 
python-aiosmtpd_1.4.2-3.debian.tar.xz
 bfcbfd8689b1127dcee749b5ebf7dca89e57f97a 7099 
python-aiosmtpd_1.4.2-3_source.buildinfo
Checksums-Sha256:
 a657ad2898d06cd56fcc6dbb00507c6e0c8f3d4d0c05324bdd35db778ae1c829 1711 
python-aiosmtpd_1.4.2-3.dsc
 27f97d12732379a7d1b0f44e67290ddb4e16433f74994cd42912401a2de95ae9 8708 
python-aiosmtpd_1.4.2-3.debian.tar.xz
 cf086983b70f9af8a51c607da44da5f26a137b1939a0ee192d42f6ca489806d5 7099 
python-aiosmtpd_1.4.2-3_source.buildinfo
Files:
 e55e734a62f2161ccc13c4c85f54c319 1711 python optional 
python-aiosmtpd_1.4.2-3.dsc
 1029e3e88176d4a42dc147f8d3560111 8708 python optional 
python-aiosmtpd_1.4.2-3.debian.tar.xz
 cc80ebe6e0bc377e2e75833f82f2339b 7099 python optional 
python-aiosmtpd_1.4.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYj4LqRQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2JzgAP45V/d6vFbwGRsU1U1zkygMvrnyJUTJ
5yw9jYFSH5/DLgD/Q/3hPgp9BzCRfGX3xjBsdYcNI3k9XvyEzdfgfCcGyAk=
=JwBY
-END PGP SIGNATURE End Message ---

Bug#967187: marked as done (openfst: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 19:00:13 +
with message-id 
and subject line Bug#967187: fixed in openfst 1.7.9-1
has caused the Debian Bug report #967187,
regarding openfst: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: openfst
Source-Version: 1.7.9-1
Done: Kartik Mistry 

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated openfst package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 23 Mar 2022 10:55:15 +0530
Source: openfst
Binary: libfst-dev libfst-tools libfst-tools-dbgsym libfst22 libfst22-dbgsym 
libfst22-plugins-base libfst22-plugins-base-dbgsym
Architecture: source amd64
Version: 1.7.9-1
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 libfst-dev - weighted finite-state transducers library (development)
 libfst-tools - weighted finite-state transducers library (tools)
 libfst22   - weighted finite-state transducers library (runtime)
 libfst22-plugins-base - weighted finite-state transducers library (base 
plugins)
Closes: 967187
Changes:
 openfst (1.7.9-1) experimental; urgency=low
 .
   [ Kartik Mistry ]
   * Updated to new upstream release 1.7.9 (Closes: #967187)
   * Migrate project under debian-science project.
   * Added Salsa CI support (debian/gitlab-ci.yml)
   * debian/control:
 + Updated Maintainer field.
 + Bumped to dh 13.
 + Updated Standards-Version to 4.6.0
 + Added Rules-Requires-Root field.
   * Updated debian/copyright.
   * Removed unused files:
 + debian/source/lintian-overrides
 + debian/addons/man/fstrandmod.1
 .
   [ Tino Didriksen ]
   * debian/control:
 + Updated package names for soname bump: libfst8 -> libfst22
 + Forbid multiple versions of the library, and forcibly replace previous
   libfst8.
   * Add C++17 and SSE patches, where the SSE patch is only for i386/amd64.
Checksums-Sha1:
 8cdbaf803adf46476795315328bfbf819b58543f 2181 openfst_1.7.9-1.dsc
 3448826216be9be2e2c79b340e2d9f5d0205f236 1320008 openfst_1.7.9.orig.tar.gz
 3be229a85fd9fdfe23e923d0b1fd034693c00c96 15080 openfst_1.7.9-1.debian.tar.xz
 365957a9d4f92403f9acd07c255e7f7f7519d4cd 332672 libfst-dev_1.7.9-1_amd64.deb
 d935da736b75273d66dc8f590fbb604b4affbb99 9922620 
libfst-tools-dbgsym_1.7.9-1_amd64.deb
 cc41ffc5826b1c32e5ea9132e622f3e56305e87b 500608 libfst-tools_1.7.9-1_amd64.deb
 02c7bf2f39ba4f975312cc834d4b9b4e4a1e8850 96685604 
libfst22-dbgsym_1.7.9-1_amd64.deb
 d21e18bfbd6226a46b538a6872eaf5ee3066a020 26269472 
libfst22-plugins-base-dbgsym_1.7.9-1_amd64.deb
 9c982688e5883ba3a24c2211aba258244eecca16 873604 

Bug#1008197: marked as done (at-spi2-core: move gsettings-desktop-schemas to package Depends)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 18:18:45 +
with message-id 
and subject line Bug#1008197: fixed in at-spi2-core 2.44.0-3
has caused the Debian Bug report #1008197,
regarding at-spi2-core: move gsettings-desktop-schemas to package Depends
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.)


-- 
1008197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: at-spi2-core
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: juli...@ubuntu.com

In Ubuntu, the attached patch was applied to achieve the following:

  * Move the gsettings-desktop-schemas from tests/control to the main
package Depends. This package is absolutely necessary for the bus
service to start.

You can see the same issue in other tests, adding the dependency for
the tests only, when it is required for the service to start does not
make much sense - it's still a missing Depends.

Thanks for considering the patch.

-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy
  APT policy: (500, 'jammy'), (500, 'impish-security'), (500, 'impish')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2022-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru at-spi2-core-2.44.0/debian/control at-spi2-core-2.44.0/debian/control
--- at-spi2-core-2.44.0/debian/control  2022-03-20 17:30:24.0 +0100
+++ at-spi2-core-2.44.0/debian/control  2022-03-24 10:21:06.0 +0100
@@ -24,7 +24,7 @@
 Package: at-spi2-core
 Architecture: any
 Multi-Arch: foreign
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, gsettings-desktop-schemas
 Description: Assistive Technology Service Provider Interface (dbus core)
  This package contains the core components of GNOME Accessibility.
 
diff -Nru at-spi2-core-2.44.0/debian/tests/control 
at-spi2-core-2.44.0/debian/tests/control
--- at-spi2-core-2.44.0/debian/tests/control2022-03-20 18:03:41.0 
+0100
+++ at-spi2-core-2.44.0/debian/tests/control2022-03-24 10:19:58.0 
+0100
@@ -1,2 +1,2 @@
 Tests: memory dbind
-Depends: libatspi2.0-dev, build-essential, xauth, xvfb, dbus, at-spi2-core, 
gsettings-desktop-schemas
+Depends: libatspi2.0-dev, build-essential, xauth, xvfb, dbus, at-spi2-core
--- End Message ---
--- Begin Message ---
Source: at-spi2-core
Source-Version: 2.44.0-3
Done: Samuel Thibault 

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

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

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated at-spi2-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Mar 2022 18:55:45 +0100
Source: at-spi2-core
Architecture: source
Version: 2.44.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Closes: 1008197
Changes:
 at-spi2-core (2.44.0-3) unstable; urgency=medium
 .
   * control: Add gsettings-desktop-schemas dep to at-spi2-core
 (Closes: Bug#1008197)
   * tests/control: Drop gsettings-desktop-schemas dep.
Checksums-Sha1:
 c0325a3b900a16e10ff3aaed20dddc07b005bb75 2743 at-spi2-core_2.44.0-3.dsc
 d320f07fc1aa94c7497fc03d37bad96d8c81f3b0 11896 
at-spi2-core_2.44.0-3.debian.tar.xz
 fd8898a0d83b05e2bcc1ffd5724502626528acfa 15425 
at-spi2-core_2.44.0-3_amd64.buildinfo
Checksums-Sha256:
 a1fc91ef1d34305678f7a2223810c8631ab65b87b77b767d1a1352f48a9df02b 2743 
at-spi2-core_2.44.0-3.dsc
 60c996f063bb9722c729aa191b9e7a0ef51e479872544cf008d613ddb6a22c6d 11896 
at-spi2-core_2.44.0-3.debian.tar.xz
 

Processed: Re: Bug#1008197: at-spi2-core: move gsettings-desktop-schemas to package Depends

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1008197 [at-spi2-core] at-spi2-core: move gsettings-desktop-schemas to 
package Depends
Added tag(s) pending.

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

Bug#1008197: at-spi2-core: move gsettings-desktop-schemas to package Depends

[Samuel Thibault]

Control: tags -1 + pending

Hello,

Julian Andres Klode, le jeu. 24 mars 2022 10:24:37 +0100, a ecrit:
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * Move the gsettings-desktop-schemas from tests/control to the main
> package Depends. This package is absolutely necessary for the bus
> service to start.

Ok, so that explains why the tests were failing. That's new in bookworm,
but ok, I applied the patch and will upload.

Thanks!
Samuel

Bug#1005582: marked as done (gettext: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 17:49:30 +
with message-id 
and subject line Bug#1005582: fixed in gettext 0.21-5
has caused the Debian Bug report #1005582,
regarding gettext: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
to be marked as done.

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

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


-- 
1005582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gettext
Version: 0.21-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/gettext-tools/tests'
> PASS: gettext-1
> PASS: gettext-2
> SKIP: intl-1
> SKIP: intl-2
> SKIP: intl-4
> PASS: intl-5
> SKIP: intl-6
> SKIP: intl-3
> SKIP: intl-setlocale-1
> SKIP: intl-setlocale-2
> SKIP: intl-thread-1
> SKIP: intl-thread-2
> PASS: intl-version
> SKIP: intl-thread-3
> PASS: msgattrib-1
> PASS: msgattrib-2
> PASS: msgattrib-3
> PASS: msgattrib-4
> PASS: msgattrib-5
> PASS: msgattrib-6
> PASS: msgattrib-7
> PASS: msgattrib-8
> PASS: msgattrib-9
> PASS: msgattrib-10
> PASS: msgattrib-11
> PASS: msgattrib-12
> PASS: msgattrib-13
> PASS: msgattrib-14
> PASS: msgattrib-15
> PASS: msgattrib-16
> PASS: msgattrib-17
> PASS: msgattrib-18
> PASS: msgattrib-19
> PASS: msgattrib-properties-1
> PASS: msgcat-1
> PASS: msgcat-2
> PASS: msgcat-3
> PASS: msgcat-4
> PASS: msgcat-5
> PASS: msgcat-6
> PASS: msgcat-7
> PASS: msgcat-8
> PASS: msgcat-9
> PASS: msgcat-10
> PASS: msgcat-11
> PASS: msgcat-12
> PASS: msgcat-14
> PASS: msgcat-13
> PASS: msgcat-16
> PASS: msgcat-15
> PASS: msgcat-18
> FAIL: msgcat-17
> PASS: msgcat-20
> PASS: msgcat-19
> PASS: msgcat-properties-1
> PASS: msgcat-21
> PASS: msgcat-properties-2
> PASS: msgcat-stringtable-1
> PASS: msgcmp-1
> PASS: msgcmp-2
> PASS: msgcmp-3
> PASS: msgcomm-1
> PASS: msgcomm-2
> PASS: msgcmp-4
> PASS: msgcomm-3
> PASS: msgcomm-4
> PASS: msgcomm-5
> PASS: msgcomm-6
> PASS: msgcomm-7
> PASS: msgcomm-8
> PASS: msgcomm-9
> PASS: msgcomm-10
> PASS: msgcomm-11
> PASS: msgcomm-12
> PASS: msgcomm-13
> PASS: msgcomm-14
> PASS: msgcomm-15
> PASS: msgcomm-16
> PASS: msgcomm-17
> PASS: msgcomm-18
> PASS: msgcomm-19
> PASS: msgcomm-20
> PASS: msgcomm-21
> PASS: msgcomm-22
> PASS: msgcomm-24
> PASS: msgcomm-25
> PASS: msgcomm-23
> PASS: msgcomm-26
> PASS: msgcomm-27
> PASS: msgcomm-28
> PASS: msgconv-1
> PASS: msgconv-2
> PASS: msgconv-3
> PASS: msgconv-4
> PASS: msgconv-6
> PASS: msgconv-5
> PASS: msgconv-7
> PASS: msgen-3
> PASS: msgen-2
> PASS: msgen-1
> PASS: msgen-4
> PASS: msgexec-2
> PASS: msgexec-3
> PASS: msgexec-1
> PASS: msgexec-5
> PASS: msgexec-4
> PASS: msgfilter-1
> PASS: msgfilter-3
> PASS: msgexec-6
> PASS: msgfilter-2
> PASS: msgfilter-4
> PASS: msgfilter-6
> PASS: msgfilter-5
> PASS: msgfilter-7
> FAIL: msgfilter-sr-latin-1
> PASS: msgfilter-8
> PASS: msgfilter-quote-1
> PASS: msgfmt-1
> PASS: msgfmt-4
> PASS: msgfmt-3
> PASS: msgfmt-2
> PASS: msgfmt-6
> PASS: msgfmt-7
> PASS: msgfmt-5
> PASS: msgfmt-8
> PASS: msgfmt-9
> PASS: msgfmt-11
> PASS: msgfmt-10
> PASS: msgfmt-13
> PASS: msgfmt-12
> PASS: msgfmt-14
> PASS: msgfmt-16
> PASS: msgfmt-15
> PASS: msgfmt-18
> PASS: msgfmt-17
> PASS: msgfmt-19
> PASS: msgfmt-qt-1
> PASS: msgfmt-qt-2
> PASS: msgfmt-properties-1
> PASS: msgfmt-desktop-3
> PASS: msgfmt-desktop-1
> PASS: msggrep-1
> PASS: msgfmt-xml-1
> PASS: msgfmt-desktop-2
> PASS: msggrep-2
> PASS: msggrep-3
> PASS: msggrep-4
> PASS: msgfmt-xml-2
> PASS: msggrep-5
> PASS: msggrep-6
> PASS: msggrep-7
> PASS: msggrep-8
> PASS: msggrep-9
> PASS: msggrep-10
> PASS: msggrep-11
> PASS: msginit-1
> PASS: msginit-2
> PASS: msginit-3
> PASS: msgmerge-1
> PASS: msginit-4
> PASS: msgmerge-2
> PASS: msgmerge-3
> PASS: msgmerge-4
> PASS: msgmerge-6
> PASS: msgmerge-5
> PASS: msgmerge-7
> PASS: msgmerge-8
> PASS: msgmerge-9
> PASS: msgmerge-10
> FAIL: msgmerge-11
> PASS: msgmerge-13
> PASS: msgmerge-12
> PASS: msgmerge-14
> PASS: msgmerge-15
> PASS: msgmerge-16
> PASS: msgmerge-17
> PASS: msgmerge-18
> PASS: msgmerge-20
> PASS: msgmerge-19
> PASS: msgmerge-21
> PASS: msgmerge-22
> PASS: msgmerge-25
> PASS: msgmerge-23
> PASS: msgmerge-24
> PASS: msgmerge-26
> PASS: msgmerge-compendium-1
> PASS: msgmerge-29
> PASS: msgmerge-27
> PASS: msgmerge-28
> PASS: msgmerge-compendium-2
> PASS: msgmerge-compendium-4
> PASS: msgmerge-compendium-3
> PASS: msgmerge-properties-1
> PASS: msgmerge-properties-2
> PASS: msgmerge-update-1
> PASS: 

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1008156 sid
Bug #1008156 [telegram-desktop] telegram-desktop: Crash when switch account
Added tag(s) sid.
>
End of message, stopping processing here.

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

Bug#1001423: marked as done (python-molotov: (autopkgtest) needs update for python3.10: TypeError: gather() got an unexpected keyword argument 'loop')

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 17:05:10 +
with message-id 
and subject line Bug#1001423: fixed in python-molotov 2.1-3
has caused the Debian Bug report #1001423,
regarding python-molotov: (autopkgtest) needs update for python3.10: TypeError: 
gather() got an unexpected keyword argument 'loop'
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.)


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

Source: python-molotov
Version: 2.1-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-molotov fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-molotov from testing2.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/17396154/log.gz

=== FAILURES 
===
_ TestFmwk.test_runner 
_


self = 

@dedicatedloop
def test_runner(self):
with coserver():

  return self._runner(console=False)


molotov/tests/test_fmwk.py:172: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ molotov/tests/test_fmwk.py:163: 
in _runner

results = Runner(args)()
molotov/runner.py:73: in __call__
return self._launch_processes()
molotov/runner.py:119: in _launch_processes
self._process()
molotov/runner.py:199: in _process
display = self.gather(update, display)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
futures = (running at 
/tmp/autopkgtest-lxc.xbv3jus_/downtmp/build.fz...t-lxc.xbv3jus_/downtmp/build.fzI/src/molotov/sharedconsole.py:36> 
created at /usr/lib/python3.10/asyncio/tasks.py:638>)


def gather(self, *futures):

  return asyncio.gather(*futures, loop=self.loop, return_exceptions=True)

E   TypeError: gather() got an unexpected keyword argument 'loop'

molotov/runner.py:57: TypeError
- Captured stderr call 
-

127.0.0.1 - - [08/Dec/2021 15:20:12] "GET / HTTP/1.1" 200 -
_ TestFmwk.test_runner_console 
_


self = 

@dedicatedloop
def test_runner_console(self):
with coserver():

  return self._runner(console=True)


molotov/tests/test_fmwk.py:177: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ molotov/tests/test_fmwk.py:163: 
in _runner

results = Runner(args)()
molotov/runner.py:73: in __call__
return self._launch_processes()
molotov/runner.py:119: in _launch_processes
self._process()
molotov/runner.py:199: in _process
display = self.gather(update, display)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
futures = (running at 
/tmp/autopkgtest-lxc.xbv3jus_/downtmp/build.f...t-lxc.xbv3jus_/downtmp/build.fzI/src/molotov/sharedconsole.py:36> 
created at /usr/lib/python3.10/asyncio/tasks.py:638>)


def gather(self, *futures):

  return asyncio.gather(*futures, loop=self.loop, return_exceptions=True)

E   TypeError: gather() got an unexpected keyword argument 'loop'

molotov/runner.py:57: TypeError
- Captured stderr call 
-

127.0.0.1 - - [08/Dec/2021 15:20:12] "GET / HTTP/1.1" 200 -
__ TestFmwk.test_runner_multiprocess_console 

Bug#1008211: marked as done (libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 17:04:28 +
with message-id 
and subject line Bug#1008211: fixed in libtickit-widget-tabbed-perl 0.026-2
has caused the Debian Bug report #1008211,
regarding libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest
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.)


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

Source: libobject-pad-perl, libtickit-widget-tabbed-perl
Control: found -1 libobject-pad-perl/0.63-1
Control: found -1 libtickit-widget-tabbed-perl/0.026-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of libobject-pad-perl the autopkgtest of 
libtickit-widget-tabbed-perl fails in testing when that autopkgtest is 
run with the binary packages of libobject-pad-perl from unstable. It 
passes when run with only packages from testing. In tabular form:


  passfail
libobject-pad-perlfrom testing0.63-1
libtickit-widget-tabbed-perl  from testing0.026-1
all othersfrom testingfrom testing

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

Currently this regression is blocking the migration of 
libobject-pad-perl to testing [1]. Due to the nature of this issue, I 
filed this bug report against both packages. Can you please investigate 
the situation and reassign the bug to the right package?


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=libobject-pad-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtickit-widget-tabbed-perl/20265825/log.gz


#   Failed test ' /usr/bin/perl -w -M"Tickit::Widget::Tabbed" -e 1 2>&1 
produced no (non-whitelisted) output'

#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Tickit::Widget::Tabbed" -e 1 2>&1 produced no (non-whitelisted) output'

#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.
# Looks like you failed 2 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4
# field initialiser expression is experimental and may be changed or 
removed without notice at 
/usr/share/perl5/Tickit/Widget/Tabbed/Ribbon.pm line 302.
ok 1 -  /usr/bin/perl -w -M"Tickit::Widget::Tabbed" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"Tickit::Widget::Tabbed" -e 1 2>&1 
produced no (non-whitelisted) output
# field initialiser expression is experimental and may be changed or 
removed without notice at 
/usr/share/perl5/Tickit/Widget/Tabbed/Ribbon.pm line 302.
ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Tickit::Widget::Tabbed" -e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Tickit::Widget::Tabbed" -e 1 2>&1 produced no (non-whitelisted) output

Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests
Test Summary Report
---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 512 Tests: 
4 Failed: 2)

  Failed tests:  2, 4
  Non-zero exit status: 2
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.22 cusr 
0.01 csys =  0.25 CPU)

Result: FAIL
autopkgtest [07:15:45]: test autodep8-perl



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libtickit-widget-tabbed-perl
Source-Version: 0.026-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libtickit-widget-tabbed-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Mar 2022 17:48:05 +0100
Source: libtickit-widget-tabbed-perl
Architecture: source
Version: 0.026-2

Bug#1008211: marked as pending in libtickit-widget-tabbed-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #1008211 in libtickit-widget-tabbed-perl 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/perl-team/modules/packages/libtickit-widget-tabbed-perl/-/commit/acfd11c615e488ee6dedbe66727cdaf090549dd1


autopkgtests: temporarily allow warning output.

Closes: #1008211


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008211

Processed: Bug#1008211 marked as pending in libtickit-widget-tabbed-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008211 [libtickit-widget-tabbed-perl] libobject-pad-perl breaks 
libtickit-widget-tabbed-perl autopkgtest
Added tag(s) pending.

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

Bug#1008180: marked as done (php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 16:50:00 +
with message-id 
and subject line Bug#1008180: fixed in php-pear 
1:1.10.13+submodules+notgz+2022032202-2
has caused the Debian Bug report #1008180,
regarding php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not 
installable
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.)


-- 
1008180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-pear
Version: 1:1.10.12+submodules+notgz+20210212-1
Severity: serious
Justification: uninstallable / unsatisfied Depends
X-Debbugs-Cc: car...@debian.org

Hi

It looks php-pear got a new Depends which makes the package
uninstallable:

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

The following packages have unmet dependencies:
 php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable
E: Unable to correct problems, you have held broken packages.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: php-pear
Source-Version: 1:1.10.13+submodules+notgz+2022032202-2
Done: Joseph Nahmias 

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

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

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

Debian distribution maintenance software
pp.
Joseph Nahmias  (supplier of updated php-pear package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 23 Mar 2022 21:58:01 -0400
Source: php-pear
Architecture: source
Version: 1:1.10.13+submodules+notgz+2022032202-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Joseph Nahmias 
Closes: 1008180
Changes:
 php-pear (1:1.10.13+submodules+notgz+2022032202-2) unstable; urgency=medium
 .
   [ Joseph Nahmias]
   * Team upload to unstable
 .
   [ Ondřej Surý ]
   * Revert "Update debian/php-pear.substvars-static" (Closes: #1008180)
 .
 php-pear (1:1.10.13+submodules+notgz+2022032202-1) unstable; urgency=medium
 .
   * Revert local change to XML_Util
Checksums-Sha1:
 a4545ebf1c4486d52a36ce5ab0661dfea0b43a99 2174 
php-pear_1.10.13+submodules+notgz+2022032202-2.dsc
 38f7cef1af4b55c5cebefb9ed0fc7d0f18feb4d8 2208581 
php-pear_1.10.13+submodules+notgz+2022032202.orig.tar.gz
 cc1acb1a4f92388b0a5b8932fa5cdf5e52576f9f 6888 
php-pear_1.10.13+submodules+notgz+2022032202-2.debian.tar.xz
 ce234c3e67359f2a9ce0d43592efefee845651cb 6553 
php-pear_1.10.13+submodules+notgz+2022032202-2_amd64.buildinfo
Checksums-Sha256:
 db750e366881faee00b4f42ae487374df9238199da52cd2e09aeba3b58d5d60d 2174 
php-pear_1.10.13+submodules+notgz+2022032202-2.dsc
 2c7aba34b9fbf556fe4fb2036d1cec69c3d2f16e80f49e8ddfe7da64bed93668 2208581 
php-pear_1.10.13+submodules+notgz+2022032202.orig.tar.gz
 849d19f62af421243f5a94ea6be0c56250c18094e64d73b80571594590fd847b 6888 
php-pear_1.10.13+submodules+notgz+2022032202-2.debian.tar.xz
 ebb4b04a3f7e3002cd23a53a8ae37fda63e0bc3eb99af57e0f2da27cedc797c8 6553 
php-pear_1.10.13+submodules+notgz+2022032202-2_amd64.buildinfo
Files:
 600014ebf2837d5c3d2a49e72d0b7282 2174 php optional 
php-pear_1.10.13+submodules+notgz+2022032202-2.dsc
 d1350ee8eca0d6df042d083436e72eb9 2208581 php optional 
php-pear_1.10.13+submodules+notgz+2022032202.orig.tar.gz
 f2c49ffd8a83ba23dca46b8fc2c4daa3 6888 php optional 
php-pear_1.10.13+submodules+notgz+2022032202-2.debian.tar.xz
 8950f4360ae329fc75c0ff0db22510be 6553 php optional 
php-pear_1.10.13+submodules+notgz+2022032202-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcxc7CTsDz7hRCK0UsRvZGQeaO5gFAmI973wACgkQsRvZGQea
O5ic3A//aHeyPEGBD0/By003/U7lPQAJCxvzpanTLMZl+tivgu5tm7pi75S/Rajn
DKuWi5NisXdpJHoXQVaRXNFx7QDbaPGG0yGa70C1T4P5qP+qq877Tpb5lqO1bkNl
U6+/5iOU1hHmHDgvGPSIgoE872nHiBq592slcCRiQGb8EuBYeKmXulDKaGrGzJ+9

Processed: reassign 1008211 to libtickit-widget-tabbed-perl

[Debian Bug Tracking System]

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

> reassign 1008211 libtickit-widget-tabbed-perl 0.026-1
Bug #1008211 [src:libobject-pad-perl, src:libtickit-widget-tabbed-perl] 
libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest
Bug reassigned from package 'src:libobject-pad-perl, 
src:libtickit-widget-tabbed-perl' to 'libtickit-widget-tabbed-perl'.
No longer marked as found in versions libtickit-widget-tabbed-perl/0.026-1 and 
libobject-pad-perl/0.63-1.
Ignoring request to alter fixed versions of bug #1008211 to the same values 
previously set
Bug #1008211 [libtickit-widget-tabbed-perl] libobject-pad-perl breaks 
libtickit-widget-tabbed-perl autopkgtest
Marked as found in versions libtickit-widget-tabbed-perl/0.026-1.
> thanks
Stopping processing here.

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

Processed: Bug#1001423 marked as pending in python-molotov

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001423 [src:python-molotov] python-molotov: (autopkgtest) needs update 
for python3.10: TypeError: gather() got an unexpected keyword argument 'loop'
Added tag(s) pending.

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

Bug#1001423: marked as pending in python-molotov

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1001423 in python-molotov 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/packages/python-molotov/-/commit/ed7e4d2fd9e241e5fb5a3309354151f5b86246c0


Patch: Python 3.10 support (Closes: #1001423).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001423

Bug#1008265: CVE-2018-25032: zlib memory corruption on deflate

[Moritz Muehlenhoff]

Source: zlib
Version: 1:1.2.11.dfsg-2
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2018-25032:
https://www.openwall.com/lists/oss-security/2022/03/24/1
https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531

Cheers,
Moritz

Bug#1008264: Multiple security issues

[Moritz Muehlenhoff]

Source: pluxml
Version: 5.6-1
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

CVE-2022-25020:
https://github.com/MoritzHuppert/CVE-2022-25020/blob/main/CVE-2022-25020.pdf

CVE-2022-25018:
https://github.com/MoritzHuppert/CVE-2022-25018/blob/main/CVE-2022-25018.pdf

CVE-2022-24587:
https://github.com/Nguyen-Trung-Kien/CVE/blob/main/CVE-2022-24587/CVE-2022-24587.pdf

CVE-2022-24586:
https://github.com/Nguyen-Trung-Kien/CVE/blob/main/CVE-2022-24586/CVE-2022-24586.pdf

CVE-2022-24585:
https://github.com/Nguyen-Trung-Kien/CVE/blob/main/CVE-2022-24585/CVE-2022-24585.pdf

CVE-2021-38603:
http://packetstormsecurity.com/files/163823/PluXML-5.8.7-Cross-Site-Scripting.html
https://github.com/KielVaughn/CVE-2021-38603

CVE-2021-38602:
https://github.com/KielVaughn/CVE-2021-38602
 
Cheers,
Moritz

Processed: severity of 563095 is serious

[Debian Bug Tracking System]

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

> severity 563095 serious
Bug #563095 [memtest86] memtest86: does not install in chroot/debian-live
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 540972 is grave

[Debian Bug Tracking System]

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

> severity 540972 grave
Bug #540972 [memtest86] After moving to grub-pc memtest86+ does not launch.
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1007983: marked as done (node-puppeteer: broken autopkgtest keeping chromium from migrating to testing)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 15:29:58 +
with message-id <9e2043f1-0ffc-bb34-ba25-5cfba374b...@debian.org>
and subject line Re: node-puppeteer: broken autopkgtest keeping chromium from 
migrating to testing
has caused the Debian Bug report #1007983,
regarding node-puppeteer: broken autopkgtest keeping chromium from migrating to 
testing
to be marked as done.

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

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


-- 
1007983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-puppeteer
Control: found -1 node-puppeteer/13.1.0+dfsg-6
Control: affects -1 chromium
Severity: serious
Tags: sid bookworm

node-puppeteer is keeping chromium from migrating; as
https://tracker.debian.org/pkg/chromium describes,

"Issues preventing migration:
∙ ∙ autopkgtest for node-puppeteer/13.1.0+dfsg-6: amd64: Regression ♻
  (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻
  (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Not a
  regression"

One of the failure logs is here:
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20095690/log.gz

  1 failing

  1) AriaQueryHandler
   queryOne (Chromium web test)
 should find by role "button":
 Error: expect(received).toEqual(expected) // deep equality

- Expected  - 0
+ Received  + 1

  Array [
"node5",
"node6",
+   "node7",
"node8",
"node10",
"node21",
  ]



I'm not entirely sure why it's failing, as the test in
node-puppeteer-13.1.0+dfsg/test/ariaqueryhandler.spec.ts seems to be
searching for button nodes and finds an extra (hidden) button:



it('should find by role "button"', async () => {
  const { page } = getTestState();
  const found = await
page.$$('aria/[role="button"]'); const ids =
await getIds(found); expect(ids).toEqual(['node5', 'node6',
'node8', 'node10', 'node21']); });



Please fix the test; or if this is an actual bug in chromium, please
reassign and let me know.

Thanks,
Andres
--- End Message ---
--- Begin Message ---

Package: node-puppeteer
Version: 13.4.1+dfsg-1

I had forgotten to close this bug with my last upload, which fixes those 
issues.



--
Martina Ferrari (Tina)--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1008156 serious
Bug #1008156 [telegram-desktop] telegram-desktop: Crash when switch account
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: fixed 1008171 1.7.0-2

[Debian Bug Tracking System]

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

> fixed 1008171 1.7.0-2
Bug #1008171 [src:python-confluent-kafka] python-confluent-kafka: FTBFS on 
big-endian
Marked as fixed in versions python-confluent-kafka/1.7.0-2.
>
End of message, stopping processing here.

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

Bug#1008171: marked as done (python-confluent-kafka: FTBFS on big-endian)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 16:11:40 +0100
with message-id <088da397-4cb2-65bb-81f3-c13c918c2...@debian.org>
and subject line Fixed in last upload
has caused the Debian Bug report #1008171,
regarding python-confluent-kafka: FTBFS on big-endian
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.)


-- 
1008171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-confluent-kafka
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: debian-s...@lists.debian.org, ol...@debian.org

Hi Maintainer

Since the upload of 1.7.0-1, python-confluent-kafka FTBFS on s390x and
some other big-endian architectures (e.g. powerpc, ppc64) [1].  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=python-confluent-kafka


=== FAILURES ===
__ test_purge __

def test_purge():
"""
Verify that when we have a higher message.timeout.ms timeout,
we can use purge()
to stop waiting for messages and get delivery reports
"""
p = Producer(
{"socket.timeout.ms": 10, "error_cb": error_cb,
"message.timeout.ms": 3}
)  # 30 seconds

# Hack to detect on_delivery was called because inner
functions can modify nonlocal objects.
# When python2 support is dropped, we can use the "nonlocal"
keyword instead
cb_detector = {"on_delivery_called": False}

def on_delivery(err, msg):
cb_detector["on_delivery_called"] = True
# Because we are purging messages, we should see a
PURGE_QUEUE kafka error
assert err.code() == KafkaError._PURGE_QUEUE

# Our message won't be delivered, but also won't timeout yet
because our timeout is 30s.
p.produce(topic="some_topic", value="testing", partition=9,
callback=on_delivery)
p.flush(0.002)
assert not cb_detector["on_delivery_called"]

# When in_queue set to false, we won't purge the message and
get delivery callback
p.purge(in_queue=False)
p.flush(0.002)
>   assert not cb_detector["on_delivery_called"]
E   assert not True

tests/test_Producer.py:267: AssertionError
- Captured stderr call -
%5|1647555748.271|CONFWARN|rdkafka#producer-27| [thrd:app]: No
`bootstrap.servers` configured: client will not be able to connect to
Kafka cluster
=== short test summary info 
FAILED tests/test_Producer.py::test_purge - assert not True
=== 1 failed, 61 passed, 4 skipped in 19.19s ===
--- End Message ---
--- Begin Message ---

 End Message ---

Bug#1007234: Test suite fails on all but amd64 arches

[Mathieu Malaterre]

For some reason I never got your answer. So I've subscribed to
`1007...@bugs.debian.org`

> I'm sure this is easy to diagnose for someone who can reproduce it.

I've followed the instructions from:
* https://wiki.debian.org/RISC-V#debootstrap

I have now a RISCV-64 arch on my amd64 machine.

Now:

$ dget -u 
http://deb.debian.org/debian/pool/main/n/netpbm-free/netpbm-free_10.97.00-1.dsc
$ cd netpbm*
$ debuild -B

So I have a complete built tree of netpbm. What should I do now for issue:

...

== palm-roundtrip.test ==
pamdepth: promoting from black and white to grayscale
palmtopnm: Invalid Palm image input.  Header says 30 bytes per row
after uncompressing from 8-bit Packbits, but we counted 4294967069
bytes in a row, before we stopped processing the row
pnmcolormap: making histogram...
pnmcolormap: Scanning image 0
pnmcolormap: 20314 colors so far
pnmcolormap: 20314 colors found
pnmcolormap: choosing 256 colors...
pnmremap: 256 colors found in colormap
palmtopnm: Invalid Palm image input.  Header says 228 bytes per row
after uncompressing from 8-bit Packbits, but we counted 4294967044
bytes in a row, before we stopped processing the row
palm-roundtrip.test: FAILURE
...

Thanks

Bug#1001393: marked as pending in python-logfury

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1001393 in python-logfury 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/packages/python-logfury/-/commit/53dd3eb55e9d8d020b57b11e30448b01d220ed87


Supports Python 3.10. (Closes: #1001393)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001393

Processed: Bug#1001393 marked as pending in python-logfury

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001393 [python3-logfury] python-b2sdk: (autopkgtest) needs update for 
python3.10: UploadUrlPool.__init__() takes 1 positional argument but 2 were 
given
Bug #1002324 [python3-logfury] python-b2sdk: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Added tag(s) pending.
Added tag(s) pending.

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

Processed: reassign 1001393 to python3-logfury, affects 1001393

[Debian Bug Tracking System]

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

> reassign 1001393 python3-logfury 0.1.2-4
Bug #1001393 [src:python-b2sdk] python-b2sdk: (autopkgtest) needs update for 
python3.10: UploadUrlPool.__init__() takes 1 positional argument but 2 were 
given
Bug #1002324 [src:python-b2sdk] python-b2sdk: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Bug reassigned from package 'src:python-b2sdk' to 'python3-logfury'.
Bug reassigned from package 'src:python-b2sdk' to 'python3-logfury'.
No longer marked as found in versions python-b2sdk/1.3.0-2.
No longer marked as found in versions python-b2sdk/1.3.0-2.
Ignoring request to alter fixed versions of bug #1001393 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1002324 to the same values 
previously set
Bug #1001393 [python3-logfury] python-b2sdk: (autopkgtest) needs update for 
python3.10: UploadUrlPool.__init__() takes 1 positional argument but 2 were 
given
Bug #1002324 [python3-logfury] python-b2sdk: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Marked as found in versions python-logfury/0.1.2-4.
Marked as found in versions python-logfury/0.1.2-4.
> affects 1001393 python-b2sdk
Bug #1001393 [python3-logfury] python-b2sdk: (autopkgtest) needs update for 
python3.10: UploadUrlPool.__init__() takes 1 positional argument but 2 were 
given
Bug #1002324 [python3-logfury] python-b2sdk: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Added indication that 1001393 affects python-b2sdk
Added indication that 1002324 affects python-b2sdk
> thanks
Stopping processing here.

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

Bug#996077: marked as done (gnome-shell-mailnag: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 13:34:50 +
with message-id 
and subject line Bug#996077: fixed in gnome-shell-mailnag 40.0-2
has caused the Debian Bug report #996077,
regarding gnome-shell-mailnag: does not declare compatibility with GNOME Shell 
41
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.)


-- 
996077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-mailnag
Version: 40.0-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-mailnag
Source-Version: 40.0-2
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-shell-mailnag 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Mar 2022 09:08:36 -0400
Source: gnome-shell-mailnag
Built-For-Profiles: noudeb
Architecture: source
Version: 40.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jeremy Bicha 
Closes: 996077
Changes:
 gnome-shell-mailnag (40.0-2) unstable; urgency=medium
 .
   * Add patch to mark compatible with GNOME Shell 41 & 42 (Closes: #996077)
   * debian/control: Specify the GNOME Shell version dependency
 to match metadata.json
Checksums-Sha1:
 040d7c7cde678450f331e6fe7c22c21311f74007 1857 gnome-shell-mailnag_40.0-2.dsc
 bdc007e0c6b1d483d6c4ea259c237325553baae1 3540 
gnome-shell-mailnag_40.0-2.debian.tar.xz
 09e19d55b3fd37492bdc6fbfb1848dc76716e7b4 12193 
gnome-shell-mailnag_40.0-2_source.buildinfo
Checksums-Sha256:
 31e2ca7e52cab40d88f1f69a6f20eb950510c068431f261e1023a86b48c1a793 1857 
gnome-shell-mailnag_40.0-2.dsc
 d51948b63cfb8d8f6261291696adcef1d097828177bd8d2fb2a043b5e507874b 3540 
gnome-shell-mailnag_40.0-2.debian.tar.xz
 6e54f81d268b572bf3467c51c04eb99a38c3d1cc0b1ab2f50edfc0f06d26 12193 
gnome-shell-mailnag_40.0-2_source.buildinfo
Files:
 a962c08e6396e6523c244c75fa1edf3c 1857 gnome optional 
gnome-shell-mailnag_40.0-2.dsc
 fae790eab9d244deb3871e999c476b8c 3540 gnome optional 
gnome-shell-mailnag_40.0-2.debian.tar.xz
 aca2dbddee5f6495d29f0206ad3ee5b1 12193 gnome optional 
gnome-shell-mailnag_40.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmI9v5EACgkQ5mx3Wuv+
bH0EGw/8DrAJhCT23KiDPoeVL02foQn1VleylmQ7Xv063+bhsw0Pc9Gub3W17NlC
8k6IJ1EbqvxVlzLebTntMtPse8u1dahWfS7EL9cDrO+UPnuhu0i9LrbJ+vPIyoSK
xXLjkPNwc5xCvQcjoR2ywhxHactnKCxBamjrK/NX0TKfYOeacTI+fOlliUmzc/eE
8HNVRpna97zMTgU3bj4rQNriS2AWdwO5VNJLFKrJnACDVb3APDCYLrvRkIznPqe8
85rS1l9tMB50eJSasKiD+Gr2A2Rtcrr/ypUYZCvdZPy/ibenKj2FuSRsL//8RHNF
7/Iq1sG/zL5lFSe4AGUXOJe0O1MWOBSqla+2TX3VsB9gqswntea/p4Jynndrh8Ni
sL4bhSpBs0opqctFB8KBDr36s7/SarjKT2ejWeXKoGxtJLGjD0zf2v96F/4BHk4j

Bug#1008259: mypy: FTBFS in unstable and testing

[Graham Inggs]

Source: mypy
Version: 0.931-1
Severity: serious
Tags: ftbfs

Hi Maintainer

Since sometime around mid-March, mypy started to FTBFS in unstable and
testing [1].  I've copied what I hope is the relevant part of the log
below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/mypy.html


=== FAILURES ===
_ testBlocker __
[gw4] linux -- Python 3.10.3 /usr/bin/python3.10
data: /build/1st/mypy-0.931/test-data/unit/cmdline.test:1235:
/build/1st/mypy-0.931/mypy/test/testcmdline.py:39: in run_case
test_python_cmdline(testcase, step)
/build/1st/mypy-0.931/mypy/test/testcmdline.py:101: in test_python_cmdline
assert_string_arrays_equal(expected_out, out,
E   AssertionError: Invalid output
(/build/1st/mypy-0.931/test-data/unit/cmdline.test, line 1235)
- Captured stderr call -
Expected:
  pkg/x.py:1: error: invalid syntax. Perhaps you forgot a comma? (diff)
  Found 1 error in 1 file (errors prevented further checking)
  == Return code: 2
Actual:
  pkg/x.py:1: error: invalid syntax (diff)
  Found 1 error in 1 file (errors prevented further checking)
  == Return code: 2

Alignment of first line difference:
  E: ...: error: invalid syntax. Perhaps you forgot a comma?
  A: ...: error: invalid syntax
   ^

Bug#1005582: gettext: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Sebastien Bacher]

Hi. The patch does not apply cleanly for me, but maybe it's because 
I'm trying to get the patch from the web interface.


I'll try from the git repository and will let you know how it goes.


Right, I used git and cherry picked with success for Ubuntu
https://launchpadlibrarian.net/592963111/gettext_0.21-4ubuntu3_0.21-4ubuntu4.diff.gz

Bug#1008252: salmon: FTBFS in unstable and testing

[Graham Inggs]

Source: salmon
Version: 1.6.0+ds1-1
Severity: serious
Tags: ftbfs

Hi Maintainer

Since sometime around the end of January, salmon started to FTBFS in
unstable and testing [1].  I've copied what I hope is the relevant
part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/salmon.html


test 1
Start 1: unit_tests

1: Test command: /usr/bin/cmake
"-DTOPLEVEL_DIR=/build/1st/salmon-1.6.0+ds1" "-P"
"/build/1st/salmon-1.6.0+ds1/cmake/UnitTests.cmake"
1: Test timeout computed to be: 1000
1: -- For unit tests, will set working directory to
/build/1st/salmon-1.6.0+ds1/tests
1: 
===
1: All tests passed (2008800 assertions in 4 test cases)
1:
1/2 Test #1: unit_tests ...   Passed0.37 sec
test 2
Start 2: salmon_read_test_quasi

2: Test command: /usr/bin/cmake
"-DTOPLEVEL_DIR=/build/1st/salmon-1.6.0+ds1" "-P"
"/build/1st/salmon-1.6.0+ds1/cmake/TestSalmonQuasi.cmake"
2: Test timeout computed to be: 1000
2: sample_data/
2: sample_data/reads_2.fastq
2: sample_data/sample_alignments.bam
2: sample_data/transcripts.fasta
2: sample_data/reads_1.fastq
2: index ["sample_salmon_quasi_index"] did not previously exist  . . .
creating it
2: [2022-03-23 05:24:43.592] [jLog] [warning] The salmon index is
being built without any decoy sequences.  It is recommended that decoy
sequence (either computed auxiliary decoy sequence or the genome of
the organism) be provided during indexing. Further details can be
found at 
https://salmon.readthedocs.io/en/latest/salmon.html#preparing-transcriptome-indices-mapping-based-mode.
2: [2022-03-23 05:24:43.592] [jLog] [info] building index
2: out : sample_salmon_quasi_index
2: [2022-03-23 05:24:43.592] [puff::index::jointLog] [info] Running fixFasta
2:
2: [Step 1 of 4] : counting k-mers
2:
2: [2022-03-23 05:24:43.596] [puff::index::jointLog] [info] Replaced 0
non-ATCG nucleotides
2: [2022-03-23 05:24:43.596] [puff::index::jointLog] [info] Clipped
poly-A tails from 0 transcripts
2: wrote 15 cleaned references
2: CMake Error at
/build/1st/salmon-1.6.0+ds1/cmake/TestSalmonQuasi.cmake:17 (message):
2:   Error running
2:
2:
2/2 Test #2: salmon_read_test_quasi ...***Failed0.07 sec
sample_data/
sample_data/reads_2.fastq
sample_data/sample_alignments.bam
sample_data/transcripts.fasta
sample_data/reads_1.fastq
index ["sample_salmon_quasi_index"] did not previously exist  . . . creating it
[2022-03-23 05:24:43.592] [jLog] [warning] The salmon index is being
built without any decoy sequences.  It is recommended that decoy
sequence (either computed auxiliary decoy sequence or the genome of
the organism) be provided during indexing. Further details can be
found at 
https://salmon.readthedocs.io/en/latest/salmon.html#preparing-transcriptome-indices-mapping-based-mode.
[2022-03-23 05:24:43.592] [jLog] [info] building index
out : sample_salmon_quasi_index
[2022-03-23 05:24:43.592] [puff::index::jointLog] [info] Running fixFasta

[Step 1 of 4] : counting k-mers

[2022-03-23 05:24:43.596] [puff::index::jointLog] [info] Replaced 0
non-ATCG nucleotides
[2022-03-23 05:24:43.596] [puff::index::jointLog] [info] Clipped
poly-A tails from 0 transcripts
wrote 15 cleaned references
CMake Error at /build/1st/salmon-1.6.0+ds1/cmake/TestSalmonQuasi.cmake:17
(message):
  Error running




50% tests passed, 1 tests failed out of 2

Total Test time (real) =   0.44 sec

The following tests FAILED:
 2 - salmon_read_test_quasi (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8

Bug#1007248: [Pkg-javascript-devel] Bug#1007248:

[Nilesh Patra]

On 25 March 2022 4:51:44 pm IST, hardpenguin13  wrote:
>Was also affected by this, ended up removing affected nodejs packages and
>installing them again. No attempt to overwrite reported by dpkg.

Same, I saw this yesterday and the same workaround worked.

Bug#1007248:

[hardpenguin13]

Was also affected by this, ended up removing affected nodejs packages and
installing them again. No attempt to overwrite reported by dpkg.

Bug#1005582: gettext: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Santiago Vila]

El 25/3/22 a las 11:32, Sebastien Bacher escribió:

The issue is due to the new libunistring and should be fixed by this change

https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commit;h=56dc658db752c2894861ee574866d507f12a17f8 


Hi. The patch does not apply cleanly for me, but maybe it's because I'm 
trying to get the patch from the web interface.


I'll try from the git repository and will let you know how it goes.

Thanks a lot!

Bug#984413: marked as done (wings3d: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 10:50:24 +
with message-id 
and subject line Bug#984413: fixed in wings3d 2.2.8-1
has caused the Debian Bug report #984413,
regarding wings3d: ftbfs with GCC-11
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.)


-- 
984413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wings3d
Version: 2.2.5-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/wings3d_2.2.5-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_tesselation.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_text.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_tweak.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_tweak_win.erl
erlc '-Dwings_branch=""' -pa /<>/wings-2.2.5/ebin -Werror -I ../.. 
-I../_deps +debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_u.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_undo.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_util.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_va.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_vbo.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_vec.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_vertex.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_vertex_cmd.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_view.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_we.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_we_build.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin 
wings_we_util.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wings_wm.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I ../.. -I../_deps 
+debug_info '-Dwings_version="2.2.5"' -pa ../intl_tools -o../ebin wpa.erl
erlc -pa /<>/wings-2.2.5/ebin -Werror -I 

Bug#1005582: gettext: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Sebastien Bacher]

The issue is due to the new libunistring and should be fixed by this change

https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commit;h=56dc658db752c2894861ee574866d507f12a17f8

Bug#1007824: marked as done (chemeq: autopkgtest failure on i386 (but no information))

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 10:03:44 +
with message-id 
and subject line Bug#1007824: fixed in chemeq 2.23-2
has caused the Debian Bug report #1007824,
regarding chemeq: autopkgtest failure on i386 (but no information)
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.)


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

Source: chemeq
Version: 2.22-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package chemeq, great. 
However, it fails on i386. Currently this failure is blocking the 
migration to testing [1]. Can you please investigate the situation and 
fix it?


I copied all of the output of the test itself at the bottom of this 
report. There's nothing to see though.


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=chemeq

https://ci.debian.net/data/autopkgtest/testing/i386/c/chemeq/19841417/log.gz

autopkgtest [21:09:59]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: chemeq
Source-Version: 2.23-2
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated chemeq 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, 24 Mar 2022 19:40:18 +0100
Source: chemeq
Architecture: source
Version: 2.23-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 1007824
Changes:
 chemeq (2.23-2) unstable; urgency=medium
 .
   * maybe fixed the branch pristine-tar
   * checked that autopkgtest succeeds. Closes: #1007824
Checksums-Sha1:
 dd25aa7667ac11fcbb44eb24a2f3fba8ddd41693 1843 chemeq_2.23-2.dsc
 10866cc6734a5289869ecf351af40b6fcb6a3d1c 6376 chemeq_2.23-2.debian.tar.xz
 62d86771b0e9dd3005ef24a4fb6af0b9d7f11452 5725 chemeq_2.23-2_source.buildinfo
Checksums-Sha256:
 5c2b62f3f2021192ea1127990e65f4b3b5a2ed123db38127d503040d4464db54 1843 
chemeq_2.23-2.dsc
 02b0f601bf96d1fa5814a7b4c0865491bad7bd599c1989ec872472b888f4f804 6376 
chemeq_2.23-2.debian.tar.xz
 27ef70760f4dd88cc738ee232311a04cd543eedf043fad2cd75e0f586f5fa316 5725 
chemeq_2.23-2_source.buildinfo
Files:
 be5f6abab78fc2310d8eabe9ab160c93 1843 tex optional chemeq_2.23-2.dsc
 890be9324fccaf099af838a7af4949b6 6376 tex optional chemeq_2.23-2.debian.tar.xz
 14237c1e7e182db376aa635a0ec9ad81 5725 tex optional 
chemeq_2.23-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmI9j5AUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmsPQ//dUK957EGssZsqlnubbIpp60WVpgB
UsLYGu0tMLEsi598z2edyKVvVwJhxUMW65xnkeT0S4n2R1+U08VSdFwOznkjYRQF
X1jVBOk4MU9pvONkD5XZrZX8G0zYtYy/W4QHd7fXc0ajnTDOmK6RSw6FTF16pQN3
BI9q4mNdrG/aPCEkgULeEWYWf058WZf2l9yiLWyoPQ41Kn0sM4SvJh+y82g1slJq
q49vquMH4NjXHQOi3AT0lcclrskuJqtyw461KoOSSxhr6H7vrTO7kdcagTS+ENtt
4JbATvKXXkS9JIpdBt9IlS42/BdKxMdFlrQHkMyV+Xw+hn+XndOWig/fpJziNSxx
NmEkV2JNOs/kL+YLTW5WDV8SVtSJIPerJShKbSQmLp+Q22d1zXj9sso9xwwzI4AM
lyQHc/x0xsU0oE4771nPFwRkm1zhOodPE7hSkNbZK0k7I0AZEt7mH3WGhEoSOPvi
Tt5439Rmao+cZb2h3+9Ne9jAjX9yNh/8M6SaeF4nuK+SQHwiPSheJln9XWpfMvMD
8FJK224umg5+Ydwk14dzjddkXYuWonvMkK8xiqCfKQIFC9T1f0A6e3sIps6j2Gq0
U1bm54AWjPIy3m/9qo5bJ3I/PYdfE5f4feJ4K4W9QUFG2BnrTYl7la66FQ3SlGjg
HzB3mxoOD7RO3c4=
=xBzr
-END PGP SIGNATURE End Message ---

Bug#1004756: marked as done (src:python-confluent-kafka: fails to migrate to testing for too long: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2022 08:49:14 +
with message-id 
and subject line Bug#1004756: fixed in python-confluent-kafka 1.7.0-2
has caused the Debian Bug report #1004756,
regarding src:python-confluent-kafka: fails to migrate to testing for too long: 
FTBFS on s390x
to be marked as done.

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

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


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

Source: python-confluent-kafka
Version: 1.3.0-2
Severity: serious
Control: close -1 1.7.0-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:python-confluent-kafka has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. Your package fails 
to build from source on s390x while it built there in the past.


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-confluent-kafka
Source-Version: 1.7.0-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-confluent-kafka 
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: Tue, 08 Mar 2022 10:11:59 +0100
Source: python-confluent-kafka
Architecture: source
Version: 1.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Thomas Goirand 
Closes: 1004756
Changes:
 python-confluent-kafka (1.7.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Do not run test_purge() that fails in s390x (Closes: #1004756).
Checksums-Sha1:
 f8946ea0bc59e50075f8e5d179fec18f69bb0ead 2404 
python-confluent-kafka_1.7.0-2.dsc
 56d56a9305792fe627658e9f292ea7428396c04e 3300 
python-confluent-kafka_1.7.0-2.debian.tar.xz
 48bbd0c4bc8b1ffc7af1e1fd62ff962df0a092ab 8553 
python-confluent-kafka_1.7.0-2_amd64.buildinfo
Checksums-Sha256:
 604b626b5a68a33a8e25a79fffebae0cf31ca2452408f71253533ff68c064ed4 2404 
python-confluent-kafka_1.7.0-2.dsc
 7bcfdb947ea0454f75ffbe5f29ac4d1e4875e14044e6ecf1d26d327764c02852 3300 
python-confluent-kafka_1.7.0-2.debian.tar.xz
 a22f5910090431f0a0ffd56fa6955a70185a362ec968ffbe582a9cb1513f1ce9 8553 
python-confluent-kafka_1.7.0-2_amd64.buildinfo
Files:
 80a0079eb79140c777f7fea2492c8788 2404 python optional 
python-confluent-kafka_1.7.0-2.dsc
 db4a5d7b6a4b9036caaa81922d5199f7 3300 python optional 
python-confluent-kafka_1.7.0-2.debian.tar.xz
 d4ad353bef039768896206769b4b9411 8553 python optional 
python-confluent-kafka_1.7.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-