Bug#1008259: marked as done (mypy: FTBFS in unstable and testing)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 02:38:42 +
with message-id 
and subject line Bug#1008259: fixed in mypy 0.942-1
has caused the Debian Bug report #1008259,
regarding mypy: FTBFS in unstable and 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.)


-- 
1008259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
   ^
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 0.942-1
Done: Stefano Rivera 

We believe that the bug you reported is fixed in the latest version of
mypy, 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.
Stefano Rivera  (supplier of updated mypy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Apr 2022 22:07:43 -0400
Source: mypy
Architecture: source
Version: 0.942-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1008259
Changes:
 mypy (0.942-1) unstable; urgency=medium
 .
   [ Stefano Rivera ]
   * Team upload.
   * New upstream version
   * Patch: Python 3.10.3 support. Closes: #1008259
 .
   [ Michael R. Crusoe ]
   * Drop the python 3.10.1 patch, no longer needed
Checksums-Sha1:
 040c7d2a45ecfb98edbde5bc867a57f085b9629b 2060 mypy_0.942-1.dsc
 3c4ff6c128a30e37ea6d0b63eb776154bf2a1855 2651177 mypy_0.942.orig.tar.gz
 fcced188ecc6c37a5df0aff715c5913e41bd76d5 14576 mypy_0.942-1.debian.tar.xz
 6fade47a064024ff2d9c37fe8d8ca3fb0f025a83 8062 mypy_0.942-1_source.buildinfo
Checksums-Sha256:
 753598e9e98ac5b2bc1a12ea231f686d1147d236d211cf23903077dbed2cac85 2060 
mypy_0.942-1.dsc
 17e44649fec92e9f82102b48a3bf7b4a5510ad0cd22fa21a104826b5db4903e2 2651177 
mypy_0.942.orig.tar.gz
 5c05c1b05f24dbbfcedf090cad98fd9321d3a887b3b2ade0aa51fc1279856382 14576 
mypy_0.942-1.debian.tar.xz
 ab87cd80408ac5660779f59e5ba5b1462480483e69d75fb0338bf7add2b7eade 8062 
mypy_0.942-1_source.buildinfo
Files:
 536739f54ceef6287a30af40bc832e3d 2060 utils optional mypy_0.942-1.dsc
 b90a8d32a65a758c1f1cfe9c9cfae766 2651177 utils optional mypy_0.942.orig.tar.gz
 ff6762d097b1f85553205543003d95a6 14576 utils optional 
mypy_0.942-1.debian.tar.xz
 f175405e6a7594097c1028489845d9c0 8062 utils optional 
mypy_0.942-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYkkBtRQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2L10AP4pT+fD6sVnmQN6mOSy6lCkhXigwB/j
7Xi/Xpl6b9+qgwD/aaDz/sM5+Lj6g5lwwy3Yl2xisMULUorN+CG+hOYP3Q8=
=v24E
-END PGP SIGNATURE End Message ---

Bug#1008259: marked as pending in mypy

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1008259 in mypy 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/mypy/-/commit/cbe43e81dea6a3f12be53cf9a29b98e9d73e5bd3


Patch: Python 3.10.3 support. Closes: #1008259


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008259

Processed: Bug#1008259 marked as pending in mypy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008259 [src:mypy] mypy: FTBFS in unstable and testing
Added tag(s) pending.

-- 
1008259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008259
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]

Dixi quod…

>Package: pstoedit
>Version: 3.78-1
>Followup-For: Bug #1008280

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008280
for the full story and reproducer.

With the help of http://www.calvina.de/pstoedit/pstoedit.htm#section_69
I may have found a workaround (which indicates a bug in pstoedit’s ps
handling, per the instructions there).

The bug appears when doing:

$ inkscape -D --export-filename=test1.pdf --export-type=pdf \
--export-pdf-version=1.4 teckids_logo_image.svg
$ pdftops -eps test1.pdf test1-a.eps
$ purifyeps test1-a.eps test1-b.eps
 which calls
  pstoedit -ssp -f mpost -fontmap /usr/share/pstoedit/mpost.fmp \
test1-a.eps tmp.mp

If I instead run…
$ purifyeps test1.pdf test3.eps
(which is NOT documented, purifyeps says it takes PostScript only
as input but since it relies on pstoedit, this seems to work) then
I get a result file that at least looks the same with gs.

So something weird happens in pdftops from poppler-utils :/
(Huh. I’d have thought pdftops is part of ghostscript… apparently not.)

Looking at this more: pdftops -eps test1.pdf test1a-$distro.eps
followed by purifyeps test1a-$distro.eps test1b-$distro.eps

This fails on all chroots I tested: stretch 0.48.0-2+deb9u4,
buster 0.71.0-5, bullseye 20.09.0-3.1, sid 22.02.0-3

Another experiment, getting rid of poppler-utils in the middle:

-BEGIN cutting here may damage your screen surface-
$ pdf2ps test1.pdf test4-1.ps
$ ps2eps test4-1.ps
Input files: test4-1.ps
Processing: test4-1.ps
Rendering with existing %%BoundingBox: 0 0 234 187
Calculating Bounding Box...ready. %%BoundingBox: 0 0 234 187
Creating output file test4-1.eps ... ready.
$ purifyeps test4-1.eps test4-2.eps
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
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-PG1MlbvQ.mp )
Transcript written on purifyeps-PG1MlbvQ.log.
purifyeps: No such file or directory (/tmp/purifyeps-PG1MlbvQ.1)
-END cutting here may damage your screen surface-

Looks like it’s not poppler at fault here though :~

Any idea? (Also, I can’t find where pstoedit’s bugtracker is.)

bye,
//mirabilos
-- 
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so
reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~
(as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)

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

[Thorsten Glaser]

Package: pstoedit
Version: 3.78-1
Followup-For: Bug #1008280
X-Debbugs-Cc: t...@mirbsd.de

This is reproducible on sid.

It also occurs on buster, although with a different failure mode:

-BEGIN cutting here may damage your screen surface-
$ purifyeps test1-a.eps test1-b.eps
pstoedit: version 3.73 / DLL interface 108 (built: Jul 11 2018 - release build 
- g++ 7.3.0 - 32-bit) : Copyright (C) 1993 - 2018 Wolfgang Glunz
Error: /undefined in .makeoperator
Operand stack:
   false   rectfill   rectfill   --nostringval--
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1991   1   3   %oparray_pop   
1990   1   3   %oparray_pop   1978   1   3   %oparray_pop   1833   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   
--nostringval--   --nostringval--
Dictionary stack:
   --dict:1033/1123(G)--   --dict:0/20(G)--   --dict:216/300(L)--   
--dict:1033/1123(G)--
Current allocation mode is global
Current file position is 14841
GPL Ghostscript 9.27: Unrecoverable error, exit code 1
PostScript/PDF Interpreter finished. Return status 256 executed command : gs -q 
-dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS "/tmp/psinbqMIs2"
The interpreter seems to have failed, cannot proceed !
purifyeps: The following command failed with exit code 1:
pstoedit -ssp -f mpost -fontmap "/usr/share/pstoedit/mpost.fmp" 
"test1-a.eps" "/tmp/purifyeps-hn9Vq58x.mp"
-END cutting here may damage your screen surface-

stretch looks similar to bullseye though:

-BEGIN cutting here may damage your screen surface-
$ purifyeps test1-a.eps test1-b.eps
pstoedit: version 3.70 / DLL interface 108 (built: Oct 11 2016 - release build 
- g++ 6.2.1 20161215 - 32-bit) : Copyright (C) 1993 - 2014 Wolfgang Glunz
This is MetaPost, version 1.9991 (TeX Live 2016/Debian) (kpathsea version 6.2.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-nUGj2O9a.mp )
Transcript written on purifyeps-nUGj2O9a.log.
purifyeps: No such file or directory (/tmp/purifyeps-nUGj2O9a.1)
-END cutting here may damage your screen surface-

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

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages pstoedit depends on:
ii  ghostscript  9.55.0~dfsg-3
ii  libc62.33-7
ii  libpstoedit0c2a  3.78-1
ii  libstdc++6   12-20220319-1

pstoedit recommends no packages.

Versions of packages pstoedit suggests:
pn  xfig | ivtools-bin | tgif | transfig  

-- no debconf information

Bug#1008351: marked as done (go-for-it: FTBFS: TaskTimer.vala:35.42-35.50: error: value is less accessible than constant `GOFI.TaskTimer.UPDATE_INTERVAL')

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 01:05:02 +
with message-id 
and subject line Bug#1008351: fixed in go-for-it 1.9.6-2
has caused the Debian Bug report #1008351,
regarding go-for-it: FTBFS: TaskTimer.vala:35.42-35.50: error: value is less 
accessible than constant `GOFI.TaskTimer.UPDATE_INTERVAL'
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.)


-- 
1008351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: go-for-it
Version: 1.9.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/aa.mo /<>/po/aa.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ab.mo /<>/po/ab.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ae.mo /<>/po/ae.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/af.mo /<>/po/af.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ak.mo /<>/po/ak.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/am.mo /<>/po/am.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/an.mo /<>/po/an.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ar.mo /<>/po/ar.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/as.mo /<>/po/as.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ast.mo /<>/po/ast.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/av.mo /<>/po/av.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ay.mo /<>/po/ay.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/az.mo /<>/po/az.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ba.mo /<>/po/ba.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/be.mo /<>/po/be.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bg.mo /<>/po/bg.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bh.mo /<>/po/bh.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bi.mo /<>/po/bi.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bm.mo /<>/po/bm.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bn.mo /<>/po/bn.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bo.mo /<>/po/bo.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/br.mo /<>/po/br.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bs.mo /<>/po/bs.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ca.mo /<>/po/ca.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ce.mo /<>/po/ce.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ch.mo /<>/po/ch.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ckb.mo /<>/po/ckb.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/co.mo /<>/po/co.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cr.mo /<>/po/cr.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cs.mo /<>/po/cs.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cu.mo /<>/po/cu.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cv.mo /<>/po/cv.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cy.mo /<>/po/cy.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/da.mo /<>/po/da.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/de.mo /<>/po/de.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> 

Bug#1008402: khmer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Stefano Rivera]

Hi Lucas (2022.03.26_17:21:07_-0400)
> > self = FileType('wb'), string = '-'
> > 
> > def __call__(self, string):
> > # the special argument "-" means sys.std{in,out}
> > if string == '-':
> > if 'r' in self._mode:
> > return _sys.stdin.buffer if 'b' in self._mode else 
> > _sys.stdin
> > elif any(c in self._mode for c in 'wax'):
> > >   return _sys.stdout.buffer if 'b' in self._mode else 
> > > _sys.stdout
> > E   AttributeError: '_io.StringIO' object has no attribute 
> > 'buffer'

I assume the big relevant change here is
https://bugs.python.org/issue14156 being fixed

I experimented a little and got to this patch, but it isn't complete
yet.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
--- a/tests/khmer_tst_utils.py
+++ b/tests/khmer_tst_utils.py
@@ -44,18 +44,13 @@
 import sys
 import traceback
 import subprocess
-from io import open  # pylint: disable=redefined-builtin
+from io import BufferedWriter, BytesIO, StringIO, TextIOWrapper
 from hashlib import md5
 
 from khmer import reverse_complement as revcomp
 
 import pytest
 
-try:
-from StringIO import StringIO
-except ImportError:
-from io import StringIO
-
 
 def _equals_rc(query, match):
 return (query == match) or (revcomp(query) == match)
@@ -151,6 +146,25 @@
 return -1
 
 
+class StdIOBuffer(TextIOWrapper):
+'''Replacement for writable io.StringIO that behaves more like real file
+Unlike StringIO, provides a buffer attribute that holds the underlying
+binary data, allowing it to replace sys.stdout/sys.stderr in more
+contexts.
+'''
+
+name = 'StdIOBuffer'
+
+def __init__(self, initial_value='', newline='\n'):
+initial_value = initial_value.encode('utf-8')
+super().__init__(BufferedWriter(BytesIO(initial_value)),
+ 'utf-8', newline=newline)
+
+def getvalue(self):
+self.flush()
+return self.buffer.raw.getvalue().decode('utf-8')
+
+
 def runscript(scriptname, args, in_directory=None,
   fail_ok=False, sandbox=False):
 """Run a Python script using exec().
@@ -172,9 +186,8 @@
 sys.argv = sysargs
 
 oldout, olderr = sys.stdout, sys.stderr
-sys.stdout = StringIO()
-sys.stdout.name = "StringIO"
-sys.stderr = StringIO()
+sys.stdout = StdIOBuffer()
+sys.stderr = StdIOBuffer()
 
 if in_directory:
 os.chdir(in_directory)
--- a/khmer/khmer_args.py
+++ b/khmer/khmer_args.py
@@ -158,14 +158,16 @@
 
 # Temporary fix to argparse FileType which ignores the
 # binary mode flag. Upstream bug tracked in https://bugs.python.org/issue14156
+# Fixed in 3.9.12 and 3.10.3.
 # pylint: disable=too-few-public-methods,missing-docstring
 class FileType(argparse.FileType):
 def __call__(self, fname):
 # detect if stdout is being faked (StringIO during unit tests) in
 # which case we do not have to do anything
 if (fname == '-' and
-sys.version_info.major == 3 and
-not isinstance(sys.stdout, StringIO)):
+not isinstance(sys.stdout, StringIO) and
+(sys.version_info < (3, 9, 12) or
+ (3, 10) < sys.version_info < (3, 10, 3))):
 if 'r' in self._mode:
 fname = sys.stdin.fileno()
 elif 'w' in self._mode:
--- a/khmer/kfile.py
+++ b/khmer/kfile.py
@@ -209,6 +209,8 @@
 """Take in a file object and checks to see if it's a block or fifo."""
 if fthing is sys.stdout or fthing is sys.stdin:
 return True
+elif not hasattr(fthing, 'name'):
+return True
 else:
 mode = os.stat(fthing.name).st_mode
 return S_ISBLK(mode) or S_ISCHR(mode)
--- a/scripts/trim-low-abund.py
+++ b/scripts/trim-low-abund.py
@@ -512,7 +512,7 @@
 
 if args.output is None:
 log_info('output in *.abundtrim')
-elif args.output.name == 1:
+elif not hasattr(args.output, 'name') or args.output.name == 1:
 log_info('output streamed to stdout')
 elif args.output.name:
 log_info('output in {}'.format(args.output.name))

Processed: Re: libphp-jpgraph: uses deprecated PHP functions

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #631280 [libphp-jpgraph] libphp-jpgraph: uses deprecated PHP functions
Severity set to 'serious' from 'important'

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

Bug#1008854: Packages using gnuradio-dev FTBFS

[A. Maitland Bottoms]

>> affects -1 src:gr-limesdr src:gr-funcube src:gr-rds src:gr-hpsdr 
>> src:gr-fosphor src:gr-satellites src:gr-radar src:gr-iqbal
> Bug #1008854 [gnuradio-dev] Packages using gnuradio-dev FTBFS
> Added indication that 1008854 affects src:gr-limesdr, src:gr-funcube, 
> src:gr-rds, src:gr-hpsdr, src:gr-fosphor, src:gr-satellites, src:gr-radar, 
> and src:gr-iqbal
>
> -- 
> 1008854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008854
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

OK.

I am preparing gnuradio_3.10.2.0-2 which explicitly uses 'posix_prefix'
from Python3's sysconfig in GrPython.cmake

The other gr-* packages will then have the expected python path for the
.install files to work as well.

Lots of other improvements - uploading to unstable.

-Maitland

Bug#1008787: Deep dive discovered partial fix

[Thomas Ward]

So, it seems that this problem leads to a deeper problem, one with a 
fix, and one that leaves the s390x support at an impasse.


Firstly, mips64el has libluajit available.  We can fix the mips64el 
builds by adding libluajit-5.1-dev as an explicit dependency for mips64el.


However, we can NO LONGER use lua-nginx on any Debian release that has 
no libluajit because Upstream has changed dependencies. As such, we 
cannot package the Lua module for s390x, which makes this package still 
unsuitable for s390x as a result of nginx-extras depending on the Lua 
module.  Per upstream on that module:


> Since version |v0.10.16| of this module, the standard Lua interpreter 
(also known as "PUC-Rio Lua") is not supported anymore. [1]


This means that s390x support for NGINX will need to be dropped, or the 
Lua module will need to be dropped, or the Lua module will need 
*downgraded* to v0.10.15 which was the last version of the module to 
support liblua as a dependency.


If it is chosen to drop s390x support in nginx here, then the liblua 
dependency can be dropped entirely from build depends.  If it is chosen 
to downgrade the module to v0.10.15 then liblua will still work and the 
build dependencies will not need changed.


(Note that downstream in Ubuntu, the Lua module was dropped because of 
the problem with it later now requiring resty-core as a dependency, 
which the Ubuntu Server Team downstream no longer wishes to include just 
to get Lua working, and is pushing people who need Lua module to just 
use Open Resty.)




Thomas

[1]: https://github.com/openresty/lua-nginx-module#description

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1008623 src:gnuradio
Bug #1008623 [gnuradio] gnuradio cannot be installed in sid: failed dependency 
python3 (<< 3.10)
Bug reassigned from package 'gnuradio' to 'src:gnuradio'.
No longer marked as found in versions gnuradio/3.10.1.1-1.
Ignoring request to alter fixed versions of bug #1008623 to the same values 
previously set
> forcemerge 1008794 1008623
Bug #1008794 {Done: A. Maitland Bottoms } [src:gnuradio] 
gnuradio: FTBFS with python 3.10 as default
Bug #1008623 [src:gnuradio] gnuradio cannot be installed in sid: failed 
dependency python3 (<< 3.10)
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions gnuradio/3.10.1.1-2 and gnuradio/3.10.2.0~rc1-1.
Marked as found in versions gnuradio/3.10.1.1-1.
Added tag(s) sid, ftbfs, bookworm, and experimental.
Merged 1008623 1008794
> affects 1008794 gnuradio
Bug #1008794 {Done: A. Maitland Bottoms } [src:gnuradio] 
gnuradio: FTBFS with python 3.10 as default
Bug #1008623 {Done: A. Maitland Bottoms } [src:gnuradio] 
gnuradio cannot be installed in sid: failed dependency python3 (<< 3.10)
Added indication that 1008794 affects gnuradio
Added indication that 1008623 affects gnuradio
> thanks
Stopping processing here.

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

Processed: Packages using gnuradio-dev FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gr-limesdr src:gr-funcube src:gr-rds src:gr-hpsdr 
> src:gr-fosphor src:gr-satellites src:gr-radar src:gr-iqbal
Bug #1008854 [gnuradio-dev] Packages using gnuradio-dev FTBFS
Added indication that 1008854 affects src:gr-limesdr, src:gr-funcube, 
src:gr-rds, src:gr-hpsdr, src:gr-fosphor, src:gr-satellites, src:gr-radar, and 
src:gr-iqbal

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

Bug#1008854: Packages using gnuradio-dev FTBFS

[Adrian Bunk]

Package: gnuradio-dev
Version: 3.10.1.1-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:gr-limesdr src:gr-funcube src:gr-rds src:gr-hpsdr 
src:gr-fosphor src:gr-satellites src:gr-radar src:gr-iqbal

https://buildd.debian.org/status/fetch.php?pkg=gr-limesdr=amd64=3.0.1-4%2Bb1=1648925444=0

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) "usr/lib/python*" (tried in 
., debian/tmp)

dh_install: warning: gr-limesdr missing files: usr/lib/python*
dh_install: error: missing files, aborting



This might be related to #1008794 ?

Bug#1008746: marked as done (mrgingham: FTBFS with Python 3.10 as default)

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 19:49:46 +
with message-id 
and subject line Bug#1008746: fixed in mrgingham 1.20-5
has caused the Debian Bug report #1008746,
regarding mrgingham: FTBFS with Python 3.10 as default
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.)


-- 
1008746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mrgingham
Version: 1.20-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], mrgingham FTBFS with Python
3.10 as the default version.  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/mrgingham.html


pod2man --center="mrgingham: chessboard corner finder"
--name=MRGINGHAM --release="mrgingham 2.1" --section=1 mrgingham.pod
mrgingham.1
pod2man --center="mrgingham: chessboard corner finder"
--name=MRGINGHAM --release="mrgingham 2.1" --section=1
mrgingham-observe-pixel-uncertainty.pod
mrgingham-observe-pixel-uncertainty.1
pod2man: unable to format mrgingham-observe-pixel-uncertainty.pod
make[2]: *** [Makefile:75: mrgingham-observe-pixel-uncertainty.1] Error 1
--- End Message ---
--- Begin Message ---
Source: mrgingham
Source-Version: 1.20-5
Done: Dima Kogan 

We believe that the bug you reported is fixed in the latest version of
mrgingham, 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.
Dima Kogan  (supplier of updated mrgingham package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Apr 2022 12:21:14 -0700
Source: mrgingham
Architecture: source
Version: 1.20-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Dima Kogan 
Closes: 1008746
Changes:
 mrgingham (1.20-5) unstable; urgency=medium
 .
   * Build works with python3.10 (Closes: #1008746)
Checksums-Sha1:
 e42012b3069148586f7c33fc96e72c1f634da410 2268 mrgingham_1.20-5.dsc
 7c016ebb12d7559408ab5503483c2ef3761c1016 7524 mrgingham_1.20-5.debian.tar.xz
 65898c6bfac4298fb810cb29af8a0d3930983cac 19998 mrgingham_1.20-5_amd64.buildinfo
Checksums-Sha256:
 066f892987ef41c046f4a82cc38afd4d95a9eedeffdc01fbde31174c4146f7af 2268 
mrgingham_1.20-5.dsc
 f51cb0dd5e7b675676aac107ecfe9b217b85ce4df54e970e6279df0010e4c5f4 7524 
mrgingham_1.20-5.debian.tar.xz
 1cc0eb7882a1f208021dd66747c74ee8eca29388a511ca770eebfb98c4df43c6 19998 
mrgingham_1.20-5_amd64.buildinfo
Files:
 6a9bb7bc245b13d8e7e3e0533f50761b 2268 devel optional mrgingham_1.20-5.dsc
 d47643944b002bdfb969ef613d3e1698 7524 devel optional 
mrgingham_1.20-5.debian.tar.xz
 244343bb7058c80b4b8ef392b7490bdb 19998 devel optional 
mrgingham_1.20-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmJIpYkACgkQrMfCzzCU
EYilAhAAjSMp8keX15Yz7SxkRZkmiRVx9LvbjfaKyb6MOcoK4stFbjKj8MmYBACf
kUKlQA/TjV3Njkf46JqwTWHo+wN2dDMgGWsxGzS7aE7q3ZRSRY1PlpPpISp8RC9G
5xfACEEzDM4desI+KhnLsgnjDA3rzRTybZGfXH1kuMOnj6THD9NPIiUsSnws1uvh
MICIP/fQr0jZdNnJQDn+ad4xVzD2lN/fKsgR+tAdjE4CkrRzN4quMnBVqZ0MBkgw
PzuX7IqScQRPx5gNBgZNbduGWHOdIqIwe4H9bPCwnq1/hXqnflAwxksPf2yZsidr
p7XQPSIOZbabwZrS60hfcNYDPk+v5ooxycNJvMs75rfbLnXtlPgfiCGUh/C+CJGh
F0/+cTOAWEpmS7h3LdxoP4uks/GhVnF74G3EeAMgIyJDOH1bSPb9cQqXsVtWDmdm
jxdxNNzv+I8+yTakvrXU+zwisQtbZddk7zKLt/DJ6SWLFvcWLQtsanopna1p0Cru
2sX/a74qAo7lEBTQd1bcmBULAocqphbXW9FL38g9pEyJ0XnZaZH/5IsMsPz6jChX
yNjHcu7hZQoPwPEeFi6JNedrm57HfHPAHqFiATU4eXVR7CTJgWRldS4asa7KkkpY
RSfejM6zq8btU94dJ9KSLozWNBL3O0vMZ6blvrQcDHDi/VEAzno=
=WOxs
-END PGP SIGNATURE End Message ---

Processed: tagging 1008850

[Debian Bug Tracking System]

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

> tags 1008850 + sid bookworm
Bug #1008850 [src:tulip] tulip: FTBFS on s390x
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#1008850: tulip: FTBFS on s390x

[Sebastian Ramacher]

Source: tulip
Version: 5.4.0+dfsg-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

tulip FTBFS on s390x:


/<>/thirdparty/OGDF/include/coin/CoinHelperFunctions.hpp:707:66: 
warning: ISO C++17 does not allow ‘register’ storage class specifier 
[-Wregister]
  707 | CoinDeleteEntriesFromArray(register T * arrayFirst, register T * 
arrayLast,
  |  
^
/<>/thirdparty/OGDF/src/coin/CoinUtils/CoinMessageHandler.cpp: In 
member function ‘CoinMessageHandler& CoinMessageHandler::operator<<(double)’:
/<>/thirdparty/OGDF/src/coin/CoinUtils/CoinMessageHandler.cpp:764:20:
 error: format not a string literal and no format arguments 
[-Werror=format-security]
  764 | sprintf(messageOut_,format_+2);
  | ~~~^~~
In file included from 
/<>/thirdparty/OGDF/src/coin/CoinUtils/CoinMessageHandler.cpp:7:


See
https://buildd.debian.org/status/fetch.php?pkg=tulip=s390x=5.4.0%2Bdfsg-3%2Bb2=1648507220=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1008028: marked as done (hydra: fails to propagate errors from sub-configure to make)

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 19:03:54 +
with message-id 
and subject line Bug#1008028: fixed in hydra 9.3-2
has caused the Debian Bug report #1008028,
regarding hydra: fails to propagate errors from sub-configure to make
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.)


-- 
1008028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hydra
Version: 9.3-1
Severity: serious
Justifictation: policy 4.6

When the sub-configure invocation for hydra-gtk fails, the error is
ignored and the build attempts to continue. Such behaviour is prohibited
by the Debian policy section 4.6:

| cd hydra-gtk && sh ./make_xhydra.sh
| Trying to compile xhydra now (hydra gtk gui) - don't worry if this fails, 
this is really optional ...
...
| Error: configure wasnt happy. Analyse this:
| make[1]: [Makefile:74: xhydra] Error 1 (ignored)
| 
| Now type make install
| make[1]: Leaving directory '/<>'

Note that xhydra is a non-optional component from a Debian packaging
point of view.

Helmut
--- End Message ---
--- Begin Message ---
Source: hydra
Source-Version: 9.3-2
Done: Daniel Echeverri 

We believe that the bug you reported is fixed in the latest version of
hydra, 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.
Daniel Echeverri  (supplier of updated hydra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Apr 2022 12:35:54 -0500
Source: hydra
Architecture: source
Version: 9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Daniel Echeverri 
Closes: 1008028
Changes:
 hydra (9.3-2) unstable; urgency=medium
 .
   * debian/patches
 + Add 11_change_exit_output.diff patch.
   + Make build fails when xhydra can't compile. (Closes: #1008028)
   * debian/upstream/metadata
 + Remove obsolete field Name.
Checksums-Sha1:
 a9d315cce2873bbcf9217f3a769e54c3b2d3792b 2236 hydra_9.3-2.dsc
 ae26c33db2e0b0e5d9f403dfd05cc7c75b5bf509 15908 hydra_9.3-2.debian.tar.xz
 58f65f436d2947107630e1a69100df1f6787db5e 14994 hydra_9.3-2_amd64.buildinfo
Checksums-Sha256:
 af10027e63cd90816eef87fd3d076f7bfe131f9a53960da330736f855b7ff2be 2236 
hydra_9.3-2.dsc
 e52ec95ff6ac0d57d7a4d0b1f1fd4d0cab035dfc9ab76ab6f157e113a6d188ef 15908 
hydra_9.3-2.debian.tar.xz
 9ae5e7baa2f2c0458cf44a52a953c0355bf1a957e94b7076e27289afcf3c0f95 14994 
hydra_9.3-2_amd64.buildinfo
Files:
 5a5bc6472961bb452db559757392d050 2236 net optional hydra_9.3-2.dsc
 cf0f6d3423b3aebf7769c5a78d4b3100 15908 net optional hydra_9.3-2.debian.tar.xz
 daae61e40aa20366687a243dcebf396f 14994 net optional hydra_9.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAmJImjATHGVwc2lsb25A
ZGViaWFuLm9yZwAKCRAh/ClQS1Iw21VeD/0YKxLTv9h48YvCnDfSKuqVMSbg2Ksk
5fOkqEiN/lhNi//4GtA6ajQjUkAnAoJwYijMX0KjkDl/OxeRI6+LB8HOCAnKUiao
K95hxqH7y+JnWU9Dz0VvawI4RhElcu/LsO6GIBsZ17/ClNCB1fFQNDnnHaEqnUV/
faqkPyJhMy9eqQnAeYi46jJMFfaxYVYpt4wD0DKv8AzKBr3wDuyhOEHiq8QnHG4F
U975+hJ0dT2YFcn+R4s7JGbqo5Sc733XkujM/0isf+Iga1jAmztlceoTrmEZrqza
xjC+s4tX9aGxE/gupklIUDGHxK1uOyCMkSCkpRA+qnQw2X1yfjQXnHXnb2gYObaO
xnCSLxt0A4oi+iDzPK3kCerymIt4OB+ynA5Tbbfr9xzmydnja1gBDd2RelG+Fq6u
eGFs312y9gqGemlTjB1PI443Mj54/2I3+6fSXZBtgq5CtVloGYOt7XS25BdGu0BQ
BSSkicepIKj/Zqhku8ajJ++beLnFXNK2ZlkIXgIUmvps7zO3S5h3K2akC1ZR5Gw6
ca/ahrV0z+D6apgtHhR4Y/V9dlL7S7Fty/RL0z1DUYjzKEbufDr+pxfulR18xA3D
j3b+X50tYKzhlZ0PBdIdcYoIowPZt7W2SntTGbTq5Od5j2slWWMyLkRm4bvNleUj
yP07dlTWm9DRbw==
=nPm8
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#984049: enblend-enfuse: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11
Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11
Bug #1003547 [src:libvigraimpex] hugin: Hugun begins to block for a great 
number of packages
Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages
Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages
Bug #1004563 [src:libvigraimpex] enblend and enfuse depend on libgsl25 that is 
nonexistent and replaced by libgsl27
Bug #1004564 [src:libvigraimpex] enblend and enfuse depend on libgsl25 that is 
nonexistent and replaced by libgsl27
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.

-- 
1003547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003547
1003549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003549
1003550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003550
1004563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004563
1004564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004564
984049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984049
984213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1008801: gnucash: FTBFS on armel

[Adrian Bunk]

Control: retitle -1 gnucash: FTBFS on armhf when built on 64bit hardware
Control: found -1 1:4.4-1

On Fri, Apr 01, 2022 at 08:53:42PM +0200, Sebastian Ramacher wrote:
> Source: gnucash
> Version: 1:4.10-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>...
> The following tests FAILED:
>57 - test-gnc-timezone (Bus error)
>58 - test-gnc-datetime (Bus error)
>...

It is an old existing alignment issue on 64bit hardware:
https://buildd.debian.org/status/logs.php?pkg=gnucash=armhf

I've written more information in the upstream bug.

> Cheers

cu
Adrian

Processed: Re: Bug#1008801: gnucash: FTBFS on armel

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnucash: FTBFS on armhf when built on 64bit hardware
Bug #1008801 [src:gnucash] gnucash: FTBFS on armhf
Changed Bug title to 'gnucash: FTBFS on armhf when built on 64bit hardware' 
from 'gnucash: FTBFS on armhf'.
> found -1 1:4.4-1
Bug #1008801 [src:gnucash] gnucash: FTBFS on armhf when built on 64bit hardware
Marked as found in versions gnucash/1:4.4-1.

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

Processed: tagging 1008847

[Debian Bug Tracking System]

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

> tags 1008847 + sid bookworm
Bug #1008847 [src:rust-atk-sys] rust-atk-sys
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 1008847

[Debian Bug Tracking System]

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

> tags 1008847 + fixed-upstream
Bug #1008847 [src:rust-atk-sys] rust-atk-sys
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 1008847

[Debian Bug Tracking System]

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

> tags 1008847 + a11y
Bug #1008847 [src:rust-atk-sys] rust-atk-sys
Added tag(s) a11y.
> thanks
Stopping processing here.

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

Bug#1008847: rust-atk-sys

[Samuel Thibault]

Source: rust-atk-sys
Version: 0.7.0-1
Severity: serious
Tags: upstream patch
Justification: Prevents atk1.0 migration
Control: fixed-upstream -1

Hello,

rust-atk-sys was hardcoding the value of ATK_STATE_LAST_DEFINED,
and thus its autopkgtest fails with the newer atk1.0 package
version 2.38, which introduces ATK_STATE_COLLAPSED thus bumping
ATK_STATE_LAST_DEFINED.  Upstream actually stopped hardcoding the value
in 22f00076493c040b5b20d434bd0348d047027f61 

Until that newer upstream version gets packaged, could you please apply
the attached patch to update ATK_STATE_LAST_DEFINED so atk1.0 version
2.38 can migrate to testing?

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.17.0 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -255,7 +255,8 @@ pub const ATK_STATE_CHECKABLE: AtkStateT
 pub const ATK_STATE_HAS_POPUP: AtkStateType = 40;
 pub const ATK_STATE_HAS_TOOLTIP: AtkStateType = 41;
 pub const ATK_STATE_READ_ONLY: AtkStateType = 42;
-pub const ATK_STATE_LAST_DEFINED: AtkStateType = 43;
+pub const ATK_STATE_COLLAPSED: AtkStateType = 43;
+pub const ATK_STATE_LAST_DEFINED: AtkStateType = 44;
 
 pub type AtkTextAttribute = c_int;
 pub const ATK_TEXT_ATTR_INVALID: AtkTextAttribute = 0;
--- a/tests/abi.rs
+++ b/tests/abi.rs
@@ -829,6 +829,7 @@ const RUST_CONSTANTS: &[(, )] =
 ("(gint) ATK_STATE_BUSY", "3"),
 ("(gint) ATK_STATE_CHECKABLE", "39"),
 ("(gint) ATK_STATE_CHECKED", "4"),
+("(gint) ATK_STATE_COLLAPSED", "43"),
 ("(gint) ATK_STATE_DEFAULT", "36"),
 ("(gint) ATK_STATE_DEFUNCT", "5"),
 ("(gint) ATK_STATE_EDITABLE", "6"),
@@ -844,7 +845,7 @@ const RUST_CONSTANTS: &[(, )] =
 ("(gint) ATK_STATE_INDETERMINATE", "30"),
 ("(gint) ATK_STATE_INVALID", "0"),
 ("(gint) ATK_STATE_INVALID_ENTRY", "33"),
-("(gint) ATK_STATE_LAST_DEFINED", "43"),
+("(gint) ATK_STATE_LAST_DEFINED", "44"),
 ("(gint) ATK_STATE_MANAGES_DESCENDANTS", "29"),
 ("(gint) ATK_STATE_MODAL", "14"),
 ("(gint) ATK_STATE_MULTISELECTABLE", "16"),
--- a/tests/constant.c
+++ b/tests/constant.c
@@ -203,6 +203,7 @@ int main() {
 PRINT_CONSTANT((gint) ATK_STATE_BUSY);
 PRINT_CONSTANT((gint) ATK_STATE_CHECKABLE);
 PRINT_CONSTANT((gint) ATK_STATE_CHECKED);
+PRINT_CONSTANT((gint) ATK_STATE_COLLAPSED);
 PRINT_CONSTANT((gint) ATK_STATE_DEFAULT);
 PRINT_CONSTANT((gint) ATK_STATE_DEFUNCT);
 PRINT_CONSTANT((gint) ATK_STATE_EDITABLE);

Bug#1008817: libphonenumber8: breaks evolution

[tony mancill]

On Sat, Apr 02, 2022 at 08:11:39PM +0300, Adrian Bunk wrote:
> On Sat, Apr 02, 2022 at 10:39:13AM -0600, Neil Mayhew wrote:
> > On 2022-04-02 09:14, tony mancill wrote:
> > > I will work on patching 8.12.46 and also mention this upstream. The
> > > changelogs for 8.12.45 and 8.12.46 only reference metadata updates.
> > 
> > If there was a non-metadata change that wasn't mentioned in the changelog,
> > it will be the second time this has happened in a fairly short period. The
> > other one was https://github.com/google/libphonenumber/pull/2698 which was
> > merged on Jan 7.
> 
> The problem is 
> https://github.com/google/libphonenumber/commit/5719f3a724d254b21196393d952b71ec3052e6a3
> 
> I have an approximate fix I can polish later this evening,
> unless Tony already has something similar.

Hi Adrian,

Thank you for the pointer.  I started picking through the delta between
8.12.44 and 8.12.46 and it appears that libphonenumber needs to ensure
that absl/hash/internal/hash.cc is linked.  I won't have a chance to
work on patch until later in my day (GMT-7) and so would be glad to
receive yours.  Otherwise, I will work on it tonight.

I will do a full reverse build-deps (ratt) build before uploading.

Cheers,
tony

Bug#1005912: hydrogen: autopkgtest regression on arm64 and ppc64el: H2Core::Instrument::dequeue(): Assertion `__queued > 0' failed.

[Paul Gevers]

Hi Nicholas

On 02-04-2022 00:13, Nicholas D Steeves wrote:

On 24-02-2022 06:13, Nicholas D Steeves wrote:

Paul and Debian CI team, do you know if a dummy alsa driver (and dummy
sequencer driver) can be enabled on DebCI systems?


You are in control of your testbed, can't you do this in your test? Or
can you only do this in isolation-machine testbeds (not sure how this
driver thing works)?


I was thinking that this would require a `modprobe snd-dummy`, and I'm
assuming loading arbitrary kernel modules is blocked on DebCI systems.


We don't "block" anything. But on ci.d.n things need to work in lxc for 
now. Again, I'm not into the details, but I think indeed that you need 
isolation-machine for that.



It's been a few months since I contacted the CI Team about
isolation-machines, but they're not yet ready for use either.


That's still correct, and I don't expect that to change in the short 
term. We're more focused on adding other architectures to enable the 
Release Team to test all release architectures and maintaining the 
infrastructure as-is. That's already more work that I'd expected upfront.



My request for snd-dummy on DebCI isn't arm64 specific; I noticed that
jackd2 doesn't have autopkgtest enabled, and hypothesised that missing
audio hardware was the reason why.  Jackd2 maintainers are now in CC
because would know better than I :-)


I see a lot of flaky tests with jack mentioned in the error (failure to 
start or something). Maybe that's remotely related?



To be honest, I don't really like tweaking the hosts, as other
autopkgtest instances outside our control would need to learn to do this
too.



I completely understand, and the only way this request would be
justifiable is if it provided a meaningful boost in quality assurance
for audio-related packages.


I'm wondering if this warrants a new autopkgtest restrictions (probably 
not): isolation-machine-or-needs-${group-of-defined-kernel-modules}. I 
have the feeling that could become a big list for all kind of use cases.



When I run autopkgtests locally they now error due to missing audio
hardware where previously they passed, and this wasn't the case when the
package was uploaded.


The test on ppc64el now passed after several failure due to segmentation
faults. Not sure if this is now a highly flaky test, or just that the
issue has been fixed in the mean time on ppc64el



When I contacted upstream, I learned that the cause may be that the CLI
utilities are poorly maintained.  Is this sufficient justification for
disabling the autopkgtests ie: that it's due diligence and not laziness?


Well, if a test is truly flaky for whatever reason, ci.d.n and the 
Release Team agree that the test should either not be run or marked as 
flaky. The latter only has value if some human still regularly checks. 
The same goes for failure on a particular architecture. If you believe 
the failure is due to CI and not because the package itself is wrong, 
then just don't test there (Architecture field in d/t/control). If the 
package is broken and can't reasonably be fixed, have it removed from 
that architecture (in unstable; ftp.debian.org pseudo package) and don't 
build on that architecture anymore. In that case CI found out that the 
package is broken and that's a good thing.



Thank you again for having this conversation.  I want to support our CI
team and technical excellence rather than just "unblock migration to
testing", but will of course defer to your recommendations.


Sometimes you need to (for the time being) take a practical stance. I'm 
not saying yet that we'll not enable the snd-dummy module (I hope for 
follow-up), but in the present case, if the test can't reliably run on 
the present infrastructure, and nobody is promising a solution on the 
short term, you should not make your own live too hard and you should 
not run the tests for now. Or prepare for the isolation-machine 
situation (I think Ubuntu has that on most architectures) and hope it 
will arrive someday in Debian too.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008817: libphonenumber8: breaks evolution

[Adrian Bunk]

On Sat, Apr 02, 2022 at 10:39:13AM -0600, Neil Mayhew wrote:
> On 2022-04-02 09:14, tony mancill wrote:
> > I will work on patching 8.12.46 and also mention this upstream. The
> > changelogs for 8.12.45 and 8.12.46 only reference metadata updates.
> 
> If there was a non-metadata change that wasn't mentioned in the changelog,
> it will be the second time this has happened in a fairly short period. The
> other one was https://github.com/google/libphonenumber/pull/2698 which was
> merged on Jan 7.

The problem is 
https://github.com/google/libphonenumber/commit/5719f3a724d254b21196393d952b71ec3052e6a3

I have an approximate fix I can polish later this evening,
unless Tony already has something similar.

cu
Adrian

Processed: perdition: diff for NMU version 2.2-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 999659 + patch
Bug #999659 [perdition] perdition: failed to install, failed to uninstall 
(error in initscript)
Added tag(s) patch.
> tags 999659 + pending
Bug #999659 [perdition] perdition: failed to install, failed to uninstall 
(error in initscript)
Added tag(s) pending.

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

Bug#999659: perdition: diff for NMU version 2.2-3.2

[Marcos Talau]

Control: tags 999659 + patch
Control: tags 999659 + pending

Dear maintainer,

I've prepared an NMU for perdition (versioned as 2.2-3.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru perdition-2.2/debian/changelog perdition-2.2/debian/changelog
--- perdition-2.2/debian/changelog	2019-08-02 08:11:02.0 -0300
+++ perdition-2.2/debian/changelog	2022-03-31 22:39:14.0 -0300
@@ -1,3 +1,22 @@
+perdition (2.2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add exit code true after invoke-rc.d in the files below (Closes: #999659).
+Thanks to Sergey Spiridonov.
+- perdition-ldap.postinst
+- perdition-ldap.prerm
+- perdition-mysql.postinst
+- perdition-mysql.prerm
+- perdition-odbc.postinst
+- perdition-odbc.prerm
+- perdition-postgresql.postinst
+- perdition-postgresql.prerm
+- perdition.postinst
+- perdition.preinst
+- perdition.prerm
+
+ -- Marcos Talau   Thu, 31 Mar 2022 22:39:14 -0300
+
 perdition (2.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru perdition-2.2/debian/perdition-ldap.postinst perdition-2.2/debian/perdition-ldap.postinst
--- perdition-2.2/debian/perdition-ldap.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-ldap.postinst	2022-03-31 21:37:32.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-ldap.prerm perdition-2.2/debian/perdition-ldap.prerm
--- perdition-2.2/debian/perdition-ldap.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-ldap.prerm	2022-03-31 21:39:51.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "purge"  -o "$1" = "remove" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-mysql.postinst perdition-2.2/debian/perdition-mysql.postinst
--- perdition-2.2/debian/perdition-mysql.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-mysql.postinst	2022-03-31 21:40:01.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-mysql.prerm perdition-2.2/debian/perdition-mysql.prerm
--- perdition-2.2/debian/perdition-mysql.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-mysql.prerm	2022-03-31 21:40:12.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "purge"  -o "$1" = "remove" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-odbc.postinst perdition-2.2/debian/perdition-odbc.postinst
--- perdition-2.2/debian/perdition-odbc.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-odbc.postinst	2022-03-31 21:40:22.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-odbc.prerm perdition-2.2/debian/perdition-odbc.prerm
--- perdition-2.2/debian/perdition-odbc.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-odbc.prerm	2022-03-31 21:40:57.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "purge"  -o "$1" = "remove" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-postgresql.postinst perdition-2.2/debian/perdition-postgresql.postinst
--- perdition-2.2/debian/perdition-postgresql.postinst	2016-11-28 07:58:24.0 -0200
+++ perdition-2.2/debian/perdition-postgresql.postinst	2022-03-31 21:41:09.0 -0300
@@ -7,7 +7,7 @@
 
 if [ "$1" = "configure" ]; then
 	if [ -f /etc/init.d/perdition ]; then
-		invoke-rc.d perdition stop
+		invoke-rc.d perdition stop || true
 	fi
 	if [ -f /etc/init.d/perdition ]; then
 		invoke-rc.d perdition start
diff -Nru perdition-2.2/debian/perdition-postgresql.prerm perdition-2.2/debian/perdition-postgresql.prerm
--- perdition-2.2/debian/perdition-postgresql.prerm	2014-09-11 00:40:14.0 -0300
+++ perdition-2.2/debian/perdition-postgresql.prerm	2022-03-31 21:41:20.0 -0300
@@ -7,7 +7,7 @@
 
 if [ 

Bug#1008817: libphonenumber8: breaks evolution

[Neil Mayhew]

On 2022-04-02 09:14, tony mancill wrote:
I will work on patching 8.12.46 and also mention this upstream. The 
changelogs for 8.12.45 and 8.12.46 only reference metadata updates.


If there was a non-metadata change that wasn't mentioned in the 
changelog, it will be the second time this has happened in a fairly 
short period. The other one was 
https://github.com/google/libphonenumber/pull/2698 which was merged on 
Jan 7.

Processed: lives: diff for NMU version 3.0.2-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 997240 + patch
Bug #997240 [src:lives] lives: FTBFS: htmsocket.c:41:10: fatal error: 
rpc/rpc.h: No such file or directory
Added tag(s) patch.
> tags 997240 + pending
Bug #997240 [src:lives] lives: FTBFS: htmsocket.c:41:10: fatal error: 
rpc/rpc.h: No such file or directory
Added tag(s) pending.

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

Bug#1007977: marked as done (android-platform-system-core: builds adb which is also built (at a higher version) by android-platform-tools)

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 15:48:55 +
with message-id 
and subject line Bug#1007977: fixed in android-platform-system-core 
1:10.0.0+r36-10
has caused the Debian Bug report #1007977,
regarding android-platform-system-core: builds adb which is also built (at a 
higher version) by android-platform-tools
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.)


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

Package: android-platform-system-core
Version: 1:10.0.0+r36-9
Severity: serious

The android-platform-system-core source package builds the adb and fastboot
binary packages which are also built (with a higher version number) by
android-platform-tools, I belive this is what lead to the rejection of 
the amd64
build, it would certainly cause rejections if the package was reuploaded 
now.


Please consider dropping the build of the adb binary package so your package
can be accepted on all architectures and the fix for migrate to testing.
--- End Message ---
--- Begin Message ---
Source: android-platform-system-core
Source-Version: 1:10.0.0+r36-10
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
android-platform-system-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: Sat, 02 Apr 2022 17:34:49 +0200
Source: android-platform-system-core
Architecture: source
Version: 1:10.0.0+r36-10
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1007977
Changes:
 android-platform-system-core (1:10.0.0+r36-10) unstable; urgency=medium
 .
   * Team upload.
   * Drop adb and fastboot (Closes: #1007977)
   * Mark autopkgtest superficial
Checksums-Sha1:
 a47fca9166b973599db8dd94841c194755981b8b 5499 
android-platform-system-core_10.0.0+r36-10.dsc
 ff463ae5550be30159133df06ccd6ab5b08eacc7 22836 
android-platform-system-core_10.0.0+r36-10.debian.tar.xz
 d1e9841698f246deb8823bda798bcb9c3c5c085f 6292 
android-platform-system-core_10.0.0+r36-10_source.buildinfo
Checksums-Sha256:
 f7463bb3d8fbd8a782c6bdce86d6a138e091d014056d5be1f11c73405bb27f5d 5499 
android-platform-system-core_10.0.0+r36-10.dsc
 3972b7b444febbed164f8bc4453943c0191d0a7c045566f074c42f72b1aebf53 22836 
android-platform-system-core_10.0.0+r36-10.debian.tar.xz
 0bbd43ab2f2ede83b720b42fcc3f35a070faf2c037bb328838bd727b394aa986 6292 
android-platform-system-core_10.0.0+r36-10_source.buildinfo
Files:
 6f8fd32a028a20c1a28480f4abb2739a 5499 devel optional 
android-platform-system-core_10.0.0+r36-10.dsc
 7e813e752f73b7d4145fd2371d1104e9 22836 devel optional 
android-platform-system-core_10.0.0+r36-10.debian.tar.xz
 4ceb0b58e8cc1481ffb690c55d021b10 6292 devel optional 
android-platform-system-core_10.0.0+r36-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmJIb5MACgkQW//cwljm
lDP26A//Xh6xsBoG0kEKe3h/4DwbciNYthDj9YhV7CI8Fimq8MBH6/hFoft0ieQd
ViKvMGH0oQsQsdGKomJ96UUnbnZlu8libyUCY8leIjWtfYlt7/6q/Dv9d4v2S+g2
PBguLAyiFLQoLoDl8PsnXWoKSrIo9NajwnrojgjqOM4PSRFZtnPpQea2fC3+g1PZ
ezt9cAsCGB0Qc4I6T/H1WxuLet7Kenv0ZiH707zzC3fPD2k7ZRirnJ6+nB77R2Bq
i7qiYrleobK2UirjRreRnbDJp0tFTzURQO7wEKCnBdOKAbYGSwNGOq8llZMOOW9p
de00EmG5RmW4FjlwmFvu81eF2X0Gu0B7E8zAO0oWrFXWDZL+lInLtDxyksWPuAsy
deYFx/0wM09c08Yd8DgnS4ZzY3rO+WgWPTufzsdBE577e+t5aLpLcnCLrAZmT0Bx
tBvV4Id1k7IZSkXnR0NawvDGhXv4avds4y/b70wEvtsiFr7RYA1HTt93r6VCyazI
ksRoPPakFOBqNgVd80o7jVzuVP+wNFoaSIr5oZvC/bVAap+nFy0BYuOX+Mt3uzis
KYzHz4PBLfta4BhpO9v0Dm9GP7Bd9aJRMn1rti7gqw8HwbgxMxsnB3woqaL8dpD9
jerZrYKMswNvAmC0GfxOyG3roXEN14IuCP5KoYHyPCPnBQyZwCY=
=wJRO
-END PGP SIGNATURE End Message ---

Processed: tagging 1008794, tagging 1008781, tagging 1008792, tagging 1008791

[Debian Bug Tracking System]

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

> tags 1008794 + experimental
Bug #1008794 {Done: A. Maitland Bottoms } [src:gnuradio] 
gnuradio: FTBFS with python 3.10 as default
Added tag(s) experimental.
> tags 1008781 + sid bookworm
Bug #1008781 [src:nemiver] nemiver: Intent to remove from Debian
Added tag(s) bookworm and sid.
> tags 1008792 + sid bookworm
Bug #1008792 [src:vmtk] Should vmtk be removed?
Added tag(s) bookworm and sid.
> tags 1008791 + sid bookworm
Bug #1008791 [src:googlefontdirectory-tools] Should googlefontdirectory-tools 
be removed?
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1008817: libphonenumber8: breaks evolution

[Christoph Anton Mitterer]

On Sat, 2022-04-02 at 08:14 -0700, tony mancill wrote:
> Thank you for the bug report Chris, for setting the severity so
> as to block the migration, and noting the affected packages.

Actually, the latter two were done by some other helpers :-)


Thanks,
Chris.

Bug#981831: marked as done (dbcsr FTBFS: dbcsr_perf:inputs/test_square_sparse_rma.perf (Failed))

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 15:19:02 +
with message-id 
and subject line Bug#981831: fixed in dbcsr 2.2.0-1
has caused the Debian Bug report #981831,
regarding dbcsr FTBFS: dbcsr_perf:inputs/test_square_sparse_rma.perf (Failed)
to be marked as done.

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

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


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

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

...
 8/18 Test #10: dbcsr_perf:inputs/test_square_sparse_rma.perf 
.***Failed0.91 sec
 DBCSR| CPU Multiplication driver   BLAS
 DBCSR| Multrec recursion limit  512
 DBCSR| Multiplication stack size   1000
 DBCSR| Maximum elements for imagesUNLIMITED
 DBCSR| Multiplicative factor virtual images   1
 DBCSR| Use multiplication densification   T
 DBCSR| Multiplication size stacks 3
 DBCSR| Use memory pool for CPU allocation F
 DBCSR| Number of 3D layers   SINGLE
 DBCSR| Use MPI memory allocation  F
 DBCSR| Use RMA algorithm  T
 DBCSR| Use Communication thread   T
 DBCSR| Communication thread load100
 DBCSR| MPI: My node id0
 DBCSR| MPI: Number of nodes   2
 DBCSR| OMP: Current number of threads 2
 DBCSR| OMP: Max number of threads 2
 DBCSR| Split modifier for TAS multiplication algorithm  1.0E+00
 numthreads   2
 numnodes   2
 matrix_sizes100010001000
 sparsities  0.90002   0.90002   
0.90002 
 trans NN
 symmetries NNN
 type3
 alpha_in   1.0. 
 beta_in   1.0. 
 limits   11000   11000   11000
 retain_sparsity F
 nrep  10
 bs_m   1   5
 bs_n   1   5
 bs_k   1   5

 ***
 *   ___   *
 *  /   \  *
 * [ABORT] *
 *  \___/ MPI error 53 in mpi_win_create @ mp_win_create_dv : MPI_ERR_WIN: *
 *|   invalid window   *
 *  O/|*
 * /| |*
 * / \ dbcsr_mpiwrap.F:853 *
 ***


 = Routine Calling Stack = 

7 mp_win_create_dv
6 win_setup
5 multiply_3D
4 dbcsr_multiply_generic
3 perf_multiply
2 dbcsr_perf_multiply_low
1 dbcsr_performance_driver
--
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--
...
94% tests passed, 1 tests failed out of 18

Total Test time (real) = 606.45 sec

The following tests FAILED:
 10 - dbcsr_perf:inputs/test_square_sparse_rma.perf (Failed)
Errors while running CTest
make[1]: *** [Makefile:129: test] Error 8
--- End Message ---
--- Begin Message ---
Source: dbcsr
Source-Version: 2.2.0-1
Done: Michael Banck 

We believe that the bug you reported is fixed in the latest version of
dbcsr, which is due to be installed in 

Bug#1008817: libphonenumber8: breaks evolution

[tony mancill]

On Sat, Apr 02, 2022 at 07:34:59AM +0200, Christoph Anton Mitterer wrote:
> Package: libphonenumber8
> Version: 8.12.46-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> 
> Hi.
> 
> 8.12.46-1 causes evolution to fail:
> $ evolution
> evolution: symbol lookup error: 
> /usr/lib/x86_64-linux-gnu/libphonenumber.so.8: undefined symbol: 
> _ZN4absl7debian213hash_internal9HashState5kSeedE

Hi Chris,

Thank you for the bug report Chris, for setting the severity so
as to block the migration, and noting the affected packages.

I will work on patching 8.12.46 and also mention this upstream.  The
changelogs for 8.12.45 and 8.12.46 only reference metadata updates.

Thank you,
tony

Processed: owner 1008817

[Debian Bug Tracking System]

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

> owner 1008817 !
Bug #1008817 [libphonenumber8] libphonenumber8: breaks evolution
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Dear maintainer,

I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.
(Note: the previous upload as per
 has been
canceled, this one here will replace it.)

The diff is based on what I previously sent to this bugreport in
, but now
updated to use "golang-go" as per Shengjing Zhu's hint in
 (and yes,
we could have saved a roundtrip here ...).

The binary package debdiff just lists
| $ debdiff kubernetes-client_1.20.5+really1.20.2-1_amd64.deb 
kubernetes-client_1.20.5+really1.20.2-1.1_amd64.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Installed-Size: [-40405-] {+37547+}
| Version: [-1.20.5+really1.20.2-1-] {+1.20.5+really1.20.2-1.1+}

I tested the kubectl binary against a local KinD cluster and found no
issues. Basic testing as follows:
| [ ... same (successful) results as before snipped ...]
| $ ./kubectl version
| Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", 
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"archive", 
BuildDate:"2022-04-02T14:49:13Z", GoVersion:"go1.18", Compiler:"gc", 
Platform:"linux/amd64"}
| Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", 
GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", 
BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", 
Platform:"linux/amd64"}

Please also find attached the local build log.

Best regards,
Flo
diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog
--- kubernetes-1.20.5+really1.20.2/debian/changelog	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/changelog	2022-04-02 16:49:13.0 +0200
@@ -1,3 +1,10 @@
+kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using golang-go (Closes: #1000980)
+
+ -- Florian Ernst   Sat, 02 Apr 2022 16:49:13 +0200
+
 kubernetes (1.20.5+really1.20.2-1) unstable; urgency=medium
 
   * This is actually still 1.20.2
diff -Nru kubernetes-1.20.5+really1.20.2/debian/control kubernetes-1.20.5+really1.20.2/debian/control
--- kubernetes-1.20.5+really1.20.2/debian/control	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/control	2022-04-02 16:49:00.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Janos Lenart 
-Build-Depends: debhelper (>= 12~), bash-completion, golang-1.15-go, jq, rsync
+Build-Depends: debhelper (>= 12~), bash-completion, golang-go, jq, rsync
 Standards-Version: 4.5.0
 Homepage: http://kubernetes.io/
 
diff -Nru kubernetes-1.20.5+really1.20.2/debian/rules kubernetes-1.20.5+really1.20.2/debian/rules
--- kubernetes-1.20.5+really1.20.2/debian/rules	2020-10-21 13:29:24.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/rules	2022-04-02 16:49:00.0 +0200
@@ -2,7 +2,7 @@
 
 export DH_VERBOSE = 1
 export GOPATH = $(CURDIR)/.go
-export PATH := /usr/lib/go-1.15/bin:$(PATH)
+export PATH := /usr/lib/go/bin:$(PATH)
 export CGO_ENABLED = 0
 
 %:
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on fernst.no-ip.org

+==+
| kubernetes 1.20.5+really1.20.2-1.1 (amd64)   Sat, 02 Apr 2022 14:51:12 + |
+==+

Package: kubernetes
Version: 1.20.5+really1.20.2-1.1
Source Version: 1.20.5+really1.20.2-1.1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-84aad74e-1348-46a6-8c5c-123eb8e424d9'
 with '<>'
I: NOTICE: Log filtering will replace 'build/kubernetes-6AFsTn/resolver-UBQyvV' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://127.0.0.1:3142/deb.debian.org/debian unstable InRelease [165 kB]
Get:2 http://127.0.0.1:3142/deb.debian.org/debian unstable/main 
Sources.diff/Index [63.6 kB]
Get:3 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2022-04-02-1404.31-F-2022-04-02-0803.27.pdiff [12.7 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2022-04-02-1404.31-F-2022-04-02-0803.27.pdiff [12.7 kB]
Get:5 http://127.0.0.1:3142/deb.debian.org/debian 

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Shengjing Zhu]

Hi

On Sat, Apr 2, 2022 at 9:57 PM Florian Ernst  wrote:
>
> Control: tags 1000980 + patch
> Control: tags 1000980 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
> and uploaded it to DELAYED/7. Please feel free to tell me if I should
> delay it longer.
>
> The diff is based on what I previously sent to this bugreport in
> .

Could you upgrade to golang-1.18 too? It would be even better if you
could just use the meta package `golang-go`.

We intend to remove golang-1.17 from the archive soon as well.

-- 
Shengjing Zhu

Processed: Indicate that bug affects evolution

[Debian Bug Tracking System]

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

> affects 1008817 src:evolution
Bug #1008817 [libphonenumber8] libphonenumber8: breaks evolution
Added indication that 1008817 affects src:evolution
> thanks
Stopping processing here.

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

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Florian Ernst]

Control: tags 1000980 + patch
Control: tags 1000980 + pending

Dear maintainer,

I've prepared an NMU for kubernetes (versioned as 1.20.5+really1.20.2-1.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.

The diff is based on what I previously sent to this bugreport in
.
The binary package debdiff just lists
| $ debdiff kubernetes-client_1.20.5+really1.20.2-1_amd64.deb 
kubernetes-client_1.20.5+really1.20.2-1.1_amd64.deb
| File lists identical (after any substitutions)
| 
| Control files: lines which differ (wdiff format)
| 
| Installed-Size: [-40405-] {+38907+}
| Version: [-1.20.5+really1.20.2-1-] {+1.20.5+really1.20.2-1.1+}

I tested the kubectl binary against a local KinD cluster and found no
issues. Basic testing as follows:
| 15:47:27 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl create deployment nginx 
--image=nginx
| deployment.apps/nginx created
| 15:47:57 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl expose deployment nginx 
--type LoadBalancer --port 80
| service/nginx exposed
| 15:48:04 ⌁0% 1d :~/debian/temp/kubernetes $ kubectl get svc nginx
| NAMETYPE   CLUSTER-IP EXTERNAL-IPPORT(S)AGE
| nginx   LoadBalancer   10.96.54.121   172.19.255.1   80:30032/TCP   14s
| 15:48:18 ⌁0% 1d :~/debian/temp/kubernetes $ curl 172.19.255.1
| 
| 
| 
| Welcome to nginx!
| 
| html { color-scheme: light dark; }
| body { width: 35em; margin: 0 auto;
| font-family: Tahoma, Verdana, Arial, sans-serif; }
| 
| 
| 
| Welcome to nginx!
| If you see this page, the nginx web server is successfully installed and
| working. Further configuration is required.
| 
| For online documentation and support please refer to
| http://nginx.org/;>nginx.org.
| Commercial support is available at
| http://nginx.com/;>nginx.com.
| 
| Thank you for using nginx.
| 
| 
| 15:48:25 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl get po
| NAME READY   STATUSRESTARTS   AGE
| nginx-6799fc88d8-v5ms9   1/1 Running   0  77s
| 15:48:59 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl exec -it 
nginx-6799fc88d8-v5ms9 -- hostname
| nginx-6799fc88d8-v5ms9
| 15:49:20 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl delete deploy,svc nginx
| deployment.apps "nginx" deleted
| service "nginx" deleted
| 15:49:36 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl get po
| No resources found in default namespace.
| 15:49:41 ⌁0% 1d :~/debian/temp/kubernetes $ ./kubectl version
| Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", 
GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"archive", 
BuildDate:"2022-04-02T13:36:06Z", GoVersion:"go1.17.8", Compiler:"gc", 
Platform:"linux/amd64"}
| Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", 
GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", 
BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", 
Platform:"linux/amd64"}

Please also find attached the local build log.

Best regards,
Flo
diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog
--- kubernetes-1.20.5+really1.20.2/debian/changelog	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/changelog	2022-04-02 15:36:06.0 +0200
@@ -1,3 +1,10 @@
+kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using golang-1.17-go (Closes: #1000980)
+
+ -- Florian Ernst   Sat, 02 Apr 2022 15:36:06 +0200
+
 kubernetes (1.20.5+really1.20.2-1) unstable; urgency=medium
 
   * This is actually still 1.20.2
diff -Nru kubernetes-1.20.5+really1.20.2/debian/control kubernetes-1.20.5+really1.20.2/debian/control
--- kubernetes-1.20.5+really1.20.2/debian/control	2021-06-13 09:08:18.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/control	2022-02-27 13:55:20.0 +0100
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Janos Lenart 
-Build-Depends: debhelper (>= 12~), bash-completion, golang-1.15-go, jq, rsync
+Build-Depends: debhelper (>= 12~), bash-completion, golang-1.17-go, jq, rsync
 Standards-Version: 4.5.0
 Homepage: http://kubernetes.io/
 
diff -Nru kubernetes-1.20.5+really1.20.2/debian/rules kubernetes-1.20.5+really1.20.2/debian/rules
--- kubernetes-1.20.5+really1.20.2/debian/rules	2020-10-21 13:29:24.0 +0200
+++ kubernetes-1.20.5+really1.20.2/debian/rules	2022-02-27 13:55:20.0 +0100
@@ -2,7 +2,7 @@
 
 export DH_VERBOSE = 1
 export GOPATH = $(CURDIR)/.go
-export PATH := /usr/lib/go-1.15/bin:$(PATH)
+export PATH := /usr/lib/go-1.17/bin:$(PATH)
 export CGO_ENABLED = 0
 
 %:
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on fernst.no-ip.org

+==+
| kubernetes 1.20.5+really1.20.2-1.1 (amd64)   Sat, 02 Apr 2022 13:38:32 + |

Processed: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1000980 + patch
Bug #1000980 [src:kubernetes] kubernetes: Please upgrade to golang-1.17
Added tag(s) patch.
> tags 1000980 + pending
Bug #1000980 [src:kubernetes] kubernetes: Please upgrade to golang-1.17
Added tag(s) pending.

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

Bug#1008212: marked as done (openmolcas: autopkgtest regression: SIGABRT)

[Debian Bug Tracking System]

Your message dated Sat, 2 Apr 2022 15:42:12 +0200
with message-id <624852b4.1c69fb81.8a5b3.d...@mx.google.com>
and subject line Re: [Debichem-devel] Bug#1008212: openmolcas: autopkgtest 
regression: SIGABRT
has caused the Debian Bug report #1008212,
regarding openmolcas: autopkgtest regression: SIGABRT
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.)


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

Source: openmolcas
Version: 22.02-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of openmolcas the autopkgtest of openmolcas fails 
in testing when that autopkgtest is run with the binary packages of 
openmolcas from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
openmolcas from testing22.02-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmolcas/20265826/log.gz

Running test standard: 000... (5%) OK
Running test standard: 001... (10%) Failed! (scf)
Running test standard: 002... (15%) Failed! (scf)
Running test standard: 004... (21%) OK
Running test standard: 005... (26%) OK
Running test standard: 006... (31%) OK
Running test standard: 009... (36%) OK
Running test standard: 010... (42%) OK
Running test standard: 011... (47%) OK
Running test standard: 012... (52%) OK
Running test standard: 014... (57%) OK
Running test standard: 015... (63%) OK
Running test standard: 016... (68%) OK
Running test standard: 019... (73%) OK
Running test standard: 023... (78%) OK
Running test standard: 025... (84%) OK
Running test standard: 026... (89%) OK
Running test standard: 028... (94%) OK
Running test standard: 029... (100%) OK

A total of 2 test(s) failed, with 2 critical failure(s).

Please check the directory:
  failed
for the .out/.err files of the failed tests,
and check the submit directory:
  tmp
for the working directories of the last run.

> 001.err:
Note: The following floating-point exceptions are signalling: 
IEEE_INVALID_FLAG IEEE_DIVIDE_BY_ZERO IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
scf.exe: functionals.c:287: xc_func_init: Assertion 
`nspin==XC_UNPOLARIZED || nspin==XC_POLARIZED' failed.


Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0  0x7feb89b378d2 in ???
#1  0x7feb89b36a65 in ???
#2  0x7feb897c691f in ???
#3  0x7feb897c68a1 in raise
#4  0x7feb897b0545 in abort
#5  0x7feb897b042e in ???
#6  0x7feb897bf221 in __assert_fail
#7  0x7feb88c71692 in xc_func_init
#8  0x7feb89de64ed in __xc_f03_lib_m_MOD_xc_f03_func_init
#9  0x5648b32a5b76 in ???
#10  0x5648b32a666a in ???
#11  0x5648b32a66e8 in ???
#12  0x5648b3192cca in ???
#13  0x5648b317b80c in ???
#14  0x5648b3156f46 in ???
#15  0x5648b3156cf6 in ???
#16  0x7feb897b17fc in __libc_start_main
#17  0x5648b3156d49 in ???
#18  0x in ???
> 001.out:
  Basis functions   114   114


  Input file to MOLDEN was generated!

--- Stop Module: seward at Wed Mar 23 07:16:03 2022 /rc=_RC_ALL_IS_WELL_ ---
--- Module seward spent 1 second ---
--- Start Module: check at Wed Mar 23 07:16:03 2022 ---
--- Stop Module: check at Wed Mar 23 07:16:03 2022 
/rc=_RC_NOT_AVAILABLE_ ---


Checking results:
All values match the reference


EXPORT DFT = BLYP


*** symbolic link created: INPORB -> standard__001.GssOrb
--- Start Module: scf at Wed Mar 23 07:16:03 2022 ---

-- Input validation for scf
lxml python module not found, no validation possible
--
The total execution time is limited to 600 seconds.

()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()



   only a single process is used
  available to each process: 2.0 GB of memory, 56 
threads

 pid: 2065

Bug#1008832: freeradius-python3: Module not linked with libpython when built with Python 3.10

[Adrian Bunk]

Package: freeradius-python3
Version: 3.0.25+dfsg-1
Severity: serious
Forwarded: https://github.com/FreeRADIUS/freeradius-server/issues/4441

Package: freeradius-python3
Version: 3.0.25+dfsg-1+b1
Depends: freeradius (= 3.0.25+dfsg-1+b1), libc6 (>= 2.4), libpython3.9 (>= 
3.9.1)

$ objdump -p /usr/lib/freeradius/rlm_python3.so | grep NEEDED  NEEDED   
libpython3.9.so.1.0
  NEEDED   libpthread.so.0
  NEEDED   libdl.so.2
  NEEDED   libc.so.6
  NEEDED   ld-linux-x86-64.so.2
$

Package: freeradius-python3
Version: 3.0.25+dfsg-1+b2
Depends: freeradius (= 3.0.25+dfsg-1+b2), libc6 (>= 2.4)

$ objdump -p /usr/lib/freeradius/rlm_python3.so | grep NEEDED
  NEEDED   libpthread.so.0
  NEEDED   libdl.so.2
  NEEDED   libc.so.6
  NEEDED   ld-linux-x86-64.so.2
$

Bug#1008559: marked as done (gnome-shell-extension-top-icons-plus: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 12:34:54 +
with message-id 
and subject line Bug#1008559: fixed in gnome-shell-extension-top-icons-plus 27-7
has caused the Debian Bug report #1008559,
regarding gnome-shell-extension-top-icons-plus: does not declare compatibility 
with GNOME Shell 42
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.)


-- 
1008559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-top-icons-plus
Version: 27-6
Severity: normal
Tags: bookworm sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. I don't know whether actual code changes will be necessary.

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-top-icons-plus
Source-Version: 27-7
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-top-icons-plus, 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.
Simon McVittie  (supplier of updated 
gnome-shell-extension-top-icons-plus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Apr 2022 11:48:24 +0100
Source: gnome-shell-extension-top-icons-plus
Architecture: source
Version: 27-7
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Closes: 1008559
Changes:
 gnome-shell-extension-top-icons-plus (27-7) unstable; urgency=medium
 .
   * Mark as compatible with GNOME Shell 42 (Closes: #1008559)
Checksums-Sha1:
 33fde34a51dd23e7db1c366acf69696f2b9b3f19 2398 
gnome-shell-extension-top-icons-plus_27-7.dsc
 c89b95d05e97d0abd244bbddcff2ea7690168aea 5728 
gnome-shell-extension-top-icons-plus_27-7.debian.tar.xz
 8b79a6f430004ad226f11c5e576e8ff89ac67d63 5736 
gnome-shell-extension-top-icons-plus_27-7_source.buildinfo
Checksums-Sha256:
 c955999a3cace46eba0bc74df069b47f247d99582811799df7451821d8c3c82c 2398 
gnome-shell-extension-top-icons-plus_27-7.dsc
 f922a843325f72cbb0715430136b6994d9f0b188029e04bd70c943d7dac725d6 5728 
gnome-shell-extension-top-icons-plus_27-7.debian.tar.xz
 e1ea878f14f1cd37b3b28be4a24c444fc7e9e522903b36d491232883c0b86227 5736 
gnome-shell-extension-top-icons-plus_27-7_source.buildinfo
Files:
 63864f599938071b17a3ddb83d7ed03a 2398 gnome optional 
gnome-shell-extension-top-icons-plus_27-7.dsc
 5a85edb765306c771ac1897f1add0799 5728 gnome optional 
gnome-shell-extension-top-icons-plus_27-7.debian.tar.xz
 4b12637fad99fb1cf2cbc42a4d8eb89c 5736 gnome optional 
gnome-shell-extension-top-icons-plus_27-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmJIPmIACgkQ4FrhR4+B
TE8AcxAAhKXn6svR2fuF6FdTakKFHAYErdDVar+L3wL1HdjOzZ1XzWThJLW7j15i
vVFIbyWUdqgSplOH3QV+ZiaSLWqGohYPNvC7kMSDjJDGUKyPsedXulir1ampha9F
gXCXHiSfP6VCd44ZHkmdy3MXl2OQ4L8xqM45k1TF+wT12gA5H8ywb91FFOhmylkd
tnjrsBAV+9Li4gA6u8uk5B5XU0F0yJnyjVJMtZRsJtJ3/4BhmNApMjVLhH1ZHmRl
ATwDQcoaICB5vSaU7hS4j2dydxUSVWZrXboy40eyR3X7zpVUluoyr/Ay6XjqsIYL
lx7rVe+KnEZYjD8dzF0QUhUBkSwFWXu6EEYArgpH3JrYIvVCZ9fIdShyw4i4Gl6b
g4Z/7GjtjnjuoFnItv/1qZFxpoKa2LmTJ1nFfT15gwA/00210yjAcd2kFRprlTwj
RoQNKjyMcXzo4Mc23cTzk7J5MItKBF2sp21eF6IRiVmjzKk8vsnO6N4fTpQxj5x7
5jsC+fHhIYRns58FtbZCRd9RFI75Pv5+aPVplOGgkVAAdsXExlFD5P8FMOgzZBT4
QTYGp2ZOEPf9FrLvF8KGAm2qdELrtb5wMu/6lXfYUDxqyzmv3UsuGTtrtaaNDyay
Q6Jnj5lF34/QzCnZN0ymsEmSF8aV6yK/y5WsTlpasMQeJA8He+Y=
=xKrB
-END PGP SIGNATURE End Message ---

Bug#1008120: marked as done (gnome-shell-extension-bluetooth-quick-connect: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 12:34:47 +
with message-id 
and subject line Bug#1008120: fixed in 
gnome-shell-extension-bluetooth-quick-connect 26-2
has caused the Debian Bug report #1008120,
regarding gnome-shell-extension-bluetooth-quick-connect: does not declare 
compatibility with GNOME Shell 42
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.)


-- 
1008120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-bluetooth-quick-connect
Version: 26-1
Severity: important
Tags: bookworm sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42
Forwarded: https://github.com/bjarosze/gnome-bluetooth-quick-connect/issues/53

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. It looks like changes are genuinely needed:
https://github.com/bjarosze/gnome-bluetooth-quick-connect/issues/53

smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-bluetooth-quick-connect
Source-Version: 26-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-bluetooth-quick-connect, 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.
Simon McVittie  (supplier of updated 
gnome-shell-extension-bluetooth-quick-connect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Apr 2022 12:00:02 +0100
Source: gnome-shell-extension-bluetooth-quick-connect
Architecture: source
Version: 26-2
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Closes: 1008120
Changes:
 gnome-shell-extension-bluetooth-quick-connect (26-2) unstable; urgency=medium
 .
   * Add patches for compatibility with GNOME Shell 42 (Closes: #1008120)
Checksums-Sha1:
 68ffb18945bfb3e3578eb959c338dba328dbf0e5 2526 
gnome-shell-extension-bluetooth-quick-connect_26-2.dsc
 fce11fabee2f5315ab52c47f8c2080fb220c8392 5284 
gnome-shell-extension-bluetooth-quick-connect_26-2.debian.tar.xz
 d579edd112f14a88f716867c45d568f0d4b4365c 5790 
gnome-shell-extension-bluetooth-quick-connect_26-2_source.buildinfo
Checksums-Sha256:
 437c5502ae2bce01280d41732746ea4e725e7aacf15b26c14ed19931420e1978 2526 
gnome-shell-extension-bluetooth-quick-connect_26-2.dsc
 7603a71d3b9e0081ef498be6a7f01f354eec42a28ccfcd95bf872b5e29a418a8 5284 
gnome-shell-extension-bluetooth-quick-connect_26-2.debian.tar.xz
 7850b495a10795efb7fdfe36fb4fbfc9cc3aa289b3223f06c2754577d709d84d 5790 
gnome-shell-extension-bluetooth-quick-connect_26-2_source.buildinfo
Files:
 ec3bd34a763127d8f804a6af04393a9c 2526 gnome optional 
gnome-shell-extension-bluetooth-quick-connect_26-2.dsc
 617070bcfd8356fdf712d1dcb31181ab 5284 gnome optional 
gnome-shell-extension-bluetooth-quick-connect_26-2.debian.tar.xz
 9743097ac00e73f1daf1a3c6414a1e47 5790 gnome optional 
gnome-shell-extension-bluetooth-quick-connect_26-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmJIPpAACgkQ4FrhR4+B
TE8ExQ/+JAuUVXuQhu7jSslCg817kuTcCEGsg4FNDkngK8Mlmxu46P+Av90nhMm0
8y7SbaezZ4KfyAU2BZIDdHB5Kia0Ob3/uaunzh5Vm49tCkTgF9Et43jO7qESEez7
Z3UmAhPUXhxEMdjtK5rJT8Acopow19bxFjhWHPxRQkzi0nqLv/GDkcx5H1GMGdF+
4sVmgu/jbma6l76ZyZUspaBZeu8fZ2p+PR1BPtJLxzvUDFOMsiIuQn9bt4JxLWTE
U95H6J91CVYMlqTVosJ+ii5h0EIMo/fzV0m+lLJiTXKOUDgW+QA/8UavqUYIJ3y7
Ng1nVJr44714Smir6dheMc8wSQy7CYkJpEhEOh2f5WfzlfCKWoCD7J92i2nbUqcl
xfdY8kPdjYPy1xRLhnRP0Z0P2VUfxf6FvEkxPZr9VkMkI5C0bCwslMa08Mr6Fqzk
u/NhEfHl8CnPVIcDJ/jGjZ6LQCLKAReMsIU00p+xPpI/ORqxsSNDHoHpRUs5WraO
8MtL0nKlY9CXclaUPbHiGeyy5QBo8cCln9pigmgFdG++ThXZZgVIfUnR8SUUMvDq
sStTr8MXlGSX2ZFpO2d7TWItIeOdbmPY4n2pbAAVWIzJum1rIIBJfizrcpKsnKYz
CgLb85mTcTNmz2cYnXITrS4LQ6QMdEg85FkxHb6hjEE8VBHtFLo=
=OpAW
-END PGP SIGNATURE End Message ---

Bug#1008828: python3-spf-engine: fails with ImportError: cannot import name 'own_socketfile' from 'spf_engine.util'

[Scott Kitterman]

This is already fixed in Testing.  I plan to do a Stable to address it as well.

Scott K

On April 2, 2022 10:18:28 AM UTC, "Bjørn Mork"  wrote:
>Package: python3-spf-engine
>Version: 2.9.2-1
>Severity: grave
>Justification: renders package unusable
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Dear Maintainer,
>
>Installing pyspf-milter with default dependencies and settings results
>in
>
># journalctl -u pyspf-milter
>- -- Journal begins at Sat 2022-03-26 15:26:01 CET, ends at Sat 2022-04-02 
>12:11:13 CEST. --
>Apr 02 12:04:07 canardo systemd[1]: Started pySPF Milter.
>Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call 
>last):
>Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call 
>last):
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File "/usr/bin/pyspf-milter", 
>line 11, in 
>Apr 02 12:04:07 canardo pyspf-milter[372481]: 
>load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in 
>load_entry_point
>Apr 02 12:04:07 canardo pyspf-milter[372481]: return 
>get_distribution(dist).load_entry_point(group, name)
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in 
>load_entry_point
>Apr 02 12:04:07 canardo pyspf-milter[372481]: return ep.load()
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
>Apr 02 12:04:07 canardo pyspf-milter[372481]: return self.resolve()
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in 
>resolve
>Apr 02 12:04:07 canardo pyspf-milter[372481]: module = 
>__import__(self.module_name, fromlist=['__name__'], level=0)
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in 
>Apr 02 12:04:07 canardo pyspf-milter[372481]: from spf_engine.util import 
>own_socketfile
>Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name 
>'own_socketfile' from 'spf_engine.util' 
>(/usr/lib/python3/dist-packages/spf_engine/util.py)
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File "/usr/bin/pyspf-milter", 
>line 11, in 
>  
> load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in 
>load_entry_point
>  return 
> get_distribution(dist).load_entry_point(group, name)
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in 
>load_entry_point
>  return ep.load()
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
>  return self.resolve()
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in 
>resolve
>  module = 
> __import__(self.module_name, fromlist=['__name__'], level=0)
>Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
>"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in 
>  from spf_engine.util import 
> own_socketfile
>Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name 
>'own_socketfile' from 'spf_engine.util' 
>(/usr/lib/python3/dist-packages/spf_engine/util.py)
>Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Main process exited, 
>code=exited, status=1/FAILURE
>Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Failed with result 
>'exit-code'.
>
>
>No need to clutter the archive with completely broken and untested packages.
>
>
>- -- System Information:
>Debian Release: 11.3
>  APT prefers stable-security
>  APT policy: (700, 'stable-security'), (700, 'stable'), (699, 
> 'stable-updates')
>Architecture: amd64 (x86_64)
>
>Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
>set
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>Versions of packages python3-spf-engine depends on:
>ii  python3  3.9.2-3
>ii  python3-authres  1.2.0-2
>ii  python3-spf  2.0.14-2
>
>python3-spf-engine recommends no packages.
>
>python3-spf-engine suggests no packages.
>
>- -- no debconf information
>
>-BEGIN PGP SIGNATURE-
>
>iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgi8Q4cYmpvcm5AbW9y

Processed: closing 1008360

[Debian Bug Tracking System]

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

> close 1008360 0.13.0-1
Bug #1008360 [src:phoc] phoc: FTBFS: ../src/layer_shell.c:244:72: error: 
‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’
Marked as fixed in versions phoc/0.13.0-1.
Bug #1008360 [src:phoc] phoc: FTBFS: ../src/layer_shell.c:244:72: error: 
‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1008718: src:yosys: fails to migrate to testing for too long: FTBFS on mips64el and s390x & autopkgtest regression

[Paul Gevers]

Hi Daniel,

On 01-04-2022 23:09, Daniel Gröber wrote:

How would I go about documenting and excluding s390x from building yosys


You'll need to ask for the removal of the s390x binary from unstable at 
least (ftp.debian.org pseudo packages). If you fear it could start 
building successfully by accident again you could document that in the 
Architecture field in the debian/control file, which is meant for that 
purpose (but if you believe this will be fixed in the future and no 
accidental successful build will happen before it's really fixed, it's 
typically recommended to leave "Architecture: any").



and is there anything I need to do about the non-offical Debian ports
architectures or can I just let those builds fail without it affecting
yosys' migration?


No, ports don't count for migration, only release architectures.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'

[Bjørn Mork]

Package: pysrs-bin
Version: 1.0.3-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

# envfrom2srs
Traceback (most recent call last):
  File "/usr/bin/envfrom2srs", line 14, in 
from ConfigParser import ConfigParser, DuplicateSectionError
ModuleNotFoundError: No module named 'ConfigParser'

# srs2envtol
Traceback (most recent call last):
  File "/usr/bin/srs2envtol", line 14, in 
from ConfigParser import ConfigParser, DuplicateSectionError
ModuleNotFoundError: No module named 'ConfigParser'

No need to clutter the archive with broken and untested packages.
Please remove

- -- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (700, 'stable-security'), (700, 'stable'), (699, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pysrs-bin depends on:
ii  python3  3.9.2-3
ii  python3-srs  1.0.3-2

pysrs-bin recommends no packages.

pysrs-bin suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgktA4cYmpvcm5AbW9y
ay5ubwAKCRDXSuqSjBsiyUJdAJ4zvzZBL6hIfzScL01SNMcAQDNSEQCfZZJU9yuy
jyC6TtdcMxqBEPpi278=
=yarJ
-END PGP SIGNATURE-

Bug#1008828: python3-spf-engine: fails with ImportError: cannot import name 'own_socketfile' from 'spf_engine.util'

[Bjørn Mork]

Package: python3-spf-engine
Version: 2.9.2-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

Installing pyspf-milter with default dependencies and settings results
in

# journalctl -u pyspf-milter
- -- Journal begins at Sat 2022-03-26 15:26:01 CET, ends at Sat 2022-04-02 
12:11:13 CEST. --
Apr 02 12:04:07 canardo systemd[1]: Started pySPF Milter.
Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call last):
Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call last):
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File "/usr/bin/pyspf-milter", 
line 11, in 
Apr 02 12:04:07 canardo pyspf-milter[372481]: 
load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in 
load_entry_point
Apr 02 12:04:07 canardo pyspf-milter[372481]: return 
get_distribution(dist).load_entry_point(group, name)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in 
load_entry_point
Apr 02 12:04:07 canardo pyspf-milter[372481]: return ep.load()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
Apr 02 12:04:07 canardo pyspf-milter[372481]: return self.resolve()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in 
resolve
Apr 02 12:04:07 canardo pyspf-milter[372481]: module = 
__import__(self.module_name, fromlist=['__name__'], level=0)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in 
Apr 02 12:04:07 canardo pyspf-milter[372481]: from spf_engine.util import 
own_socketfile
Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name 
'own_socketfile' from 'spf_engine.util' 
(/usr/lib/python3/dist-packages/spf_engine/util.py)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File "/usr/bin/pyspf-milter", 
line 11, in 
  
load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in 
load_entry_point
  return 
get_distribution(dist).load_entry_point(group, name)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in 
load_entry_point
  return ep.load()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
  return self.resolve()
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in 
resolve
  module = 
__import__(self.module_name, fromlist=['__name__'], level=0)
Apr 02 12:04:07 canardo pyspf-milter[372481]:   File 
"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in 
  from spf_engine.util import 
own_socketfile
Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name 
'own_socketfile' from 'spf_engine.util' 
(/usr/lib/python3/dist-packages/spf_engine/util.py)
Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Main process exited, 
code=exited, status=1/FAILURE
Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Failed with result 
'exit-code'.


No need to clutter the archive with completely broken and untested packages.


- -- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (700, 'stable-security'), (700, 'stable'), (699, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-spf-engine depends on:
ii  python3  3.9.2-3
ii  python3-authres  1.2.0-2
ii  python3-spf  2.0.14-2

python3-spf-engine recommends no packages.

python3-spf-engine suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgi8Q4cYmpvcm5AbW9y
ay5ubwAKCRDXSuqSjBsiyarCAKCAzlYvQ8KoeYFTwu57/rcZUaVWZgCeJh9IDyHM
qzAsx/mDicjW7tkbafU=
=TY8J
-END PGP SIGNATURE-

Bug#1008826: seafile-gui: Depends: libseafile0 (>= 8.0.6+ds1) but 8.0.6-1 is to be installed

[Adrian Bunk]

Package: seafile-gui
Version: 8.0.6+ds1-1
Severity: serious

The following packages have unmet dependencies:
 seafile-gui : Depends: libseafile0 (>= 8.0.6+ds1) but 8.0.6-1 is to be 
installed
   Depends: seafile-daemon (>= 8.0.6+ds1) but it is not going to be 
installed

Bug#1008825: glom FTBFS with Python 3.10

[Adrian Bunk]

Source: glom
Version: 1.30.4-6.1
Severity: serious
Tags: ftbfs bookworm sid patch
Forwarded: 
https://gitlab.gnome.org/GNOME/glom/-/commit/118563d2693626c73cdeeb5af917b3eb0e158c6d

https://buildd.debian.org/status/logs.php?pkg=glom=1.30.4-6.1%2Bb5

...
checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
:1: DeprecationWarning: The distutils package is deprecated and slated 
for removal in Python 3.12. Use setuptools or check PEP 632 for potential 
alternatives
tail -v -n \+0 config.log

Processed: closing 1008377

[Debian Bug Tracking System]

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

> close 1008377
Bug #1008377 [src:zanshin] zanshin: FTBFS: unsatisfiable build-dependencies: 
libkf5akonadi-dev (>= 4:21.08.40~), libkf5akonadicalendar-dev (>= 4:21.08.40~), 
libkf5kontactinterface-dev (>= 21.08.40~)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1008751: marked as done (pytest-mpi: autopkgtest regression: versioned test depends only in experimental)

[Debian Bug Tracking System]

Your message dated Sat, 02 Apr 2022 09:34:28 +
with message-id 
and subject line Bug#1008751: fixed in pytest-mpi 0.6-3
has caused the Debian Bug report #1008751,
regarding pytest-mpi: autopkgtest regression: versioned test depends only in 
experimental
to be marked as done.

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

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


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

Source: pytest-mpi
Version: 0.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of pytest-mpi the autopkgtest of pytest-mpi fails 
in testing when that autopkgtest is run with the binary packages of 
pytest-mpi from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
pytest-mpi from testing0.6-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. I notice that 
the required version is only available in experimental.


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=pytest-mpi

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-mpi/20466039/log.gz


autopkgtest [17:12:04]:  apt-source pytest-mpi
Get:1 http://deb.debian.org/debian unstable/main pytest-mpi 0.6-2 (dsc) 
[2,323 B]
Get:2 http://deb.debian.org/debian unstable/main pytest-mpi 0.6-2 (tar) 
[41.6 kB]
Get:3 http://deb.debian.org/debian unstable/main pytest-mpi 0.6-2 (diff) 
[4,912 B]

gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.RlS7vbFC/trustedkeys.kbx': 
General error

gpgv: Signature made Thu 17 Mar 2022 01:21:45 AM UTC
gpgv:using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify signature ./pytest-mpi_0.6-2.dsc
autopkgtest [17:12:05]: testing package pytest-mpi version 0.6-2
autopkgtest [17:12:05]: build not needed
autopkgtest [17:12:05]: test command1: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on python3-sybil:amd64 < none | 
2.0.1-3 @un uH > (>= 3.0.0~)
  Removing autopkgtest-satdep:amd64 because I can't find 
python3-sybil:amd64

Done
 Done


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pytest-mpi
Source-Version: 0.6-3
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
pytest-mpi, 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.
Drew Parsons  (supplier of updated pytest-mpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Apr 2022 10:34:48 +0200
Source: pytest-mpi
Architecture: source
Version: 0.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Drew Parsons 
Closes: 1008751
Changes:
 pytest-mpi (0.6-3) unstable; urgency=medium
 .
   * debian patch test_sybil.patch enables tests to run with
 python3-sybil < 3. cf. scrapy commit #67994d1. Closes: #1008751.
Checksums-Sha1:
 108c69e715a9fc516e55d32dd752472aadf88c28 2323 pytest-mpi_0.6-3.dsc
 8f764655370e45a69a7b234b409f70f48e17c589 5168 pytest-mpi_0.6-3.debian.tar.xz
Checksums-Sha256:
 0c5be67720c9f5de2e21079306d990f0f91baaee70481d4e3c655a9da83d5353 2323 
pytest-mpi_0.6-3.dsc
 77a83c10977adf8b70f28519251ba0392f146398626e604ef34bb57915ca6389 5168 

Processed: your mail

[Debian Bug Tracking System]

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

> found 1008265 1:1.2.8.dfsg-5
Bug #1008265 {Done: Mark Brown } [src:zlib] CVE-2018-25032: 
zlib memory corruption on deflate
Marked as found in versions zlib/1:1.2.8.dfsg-5.
> 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#1005554: marked as done (fprintd: FTBFS: ../src/meson.build:18:0: ERROR: gnome.gdbus_codegen keyword argument 'sources' was of type array[CustomTarget] but should have been array[str | File])

[Debian Bug Tracking System]

Your message dated Sat, 2 Apr 2022 10:48:10 +0200
with message-id 
and subject line Re: Bug#1005554: fprintd: FTBFS: ../src/meson.build:18:0: 
ERROR: gnome.gdbus_codegen keyword argument 'sources' was of type 
array[CustomTarget] but should have been array[str | File]
has caused the Debian Bug report #1005554,
regarding fprintd: FTBFS: ../src/meson.build:18:0: ERROR: gnome.gdbus_codegen 
keyword argument 'sources' was of type array[CustomTarget] but should have been 
array[str | File]
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.)


-- 
1005554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fprintd
Version: 1.94.1-1
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[1]: Entering directory '/<>'
> dh_auto_configure -- -Dpam=true -Dsystemd_system_unit_dir=/lib/systemd/system 
> -Dgtk_doc=true
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpam=true 
> -Dsystemd_system_unit_dir=/lib/systemd/system -Dgtk_doc=true
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: fprintd
> Project version: 1.94.1
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Compiler for C supports arguments -fno-strict-aliasing: YES 
> Compiler for C supports arguments -Wcast-align: YES 
> Compiler for C supports arguments -Werror=address: YES 
> Compiler for C supports arguments -Werror=array-bounds: YES 
> Compiler for C supports arguments -Werror=empty-body: YES 
> Compiler for C supports arguments -Werror=implicit: YES 
> Compiler for C supports arguments -Werror=init-self: YES 
> Compiler for C supports arguments -Werror=int-to-pointer-cast: YES 
> Compiler for C supports arguments -Werror=main: YES 
> Compiler for C supports arguments -Werror=missing-braces: YES 
> Compiler for C supports arguments -Werror=nonnull: YES 
> Compiler for C supports arguments -Werror=pointer-to-int-cast: YES 
> Compiler for C supports arguments -Werror=redundant-decls: YES 
> Compiler for C supports arguments -Werror=return-type: YES 
> Compiler for C supports arguments -Werror=sequence-point: YES 
> Compiler for C supports arguments -Werror=trigraphs: YES 
> Compiler for C supports arguments -Werror=write-strings: YES 
> Compiler for C supports arguments -Wformat-nonliteral: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Wformat=2: YES 
> Compiler for C supports arguments -Wignored-qualifiers: YES 
> Compiler for C supports arguments -Wimplicit-function-declaration: YES 
> Compiler for C supports arguments -Wlogical-op: YES 
> Compiler for C supports arguments -Wmissing-declarations: YES 
> Compiler for C supports arguments -Wmissing-format-attribute: YES 
> Compiler for C supports arguments -Wmissing-include-dirs: YES 
> Compiler for C supports arguments -Wmissing-noreturn: YES 
> Compiler for C supports arguments -Wmissing-prototypes: YES 
> Compiler for C supports arguments -Wnested-externs: YES 
> Compiler for C supports arguments -Wold-style-definition: YES 
> Compiler for C supports arguments -Wpointer-arith: YES 
> Compiler for C supports arguments -Wshadow: YES 
> Compiler for C supports arguments -Wstrict-prototypes: YES 
> Compiler for C supports arguments -Wtype-limits: YES 
> Compiler for C supports arguments -Wundef: YES 
> Compiler for C supports arguments -Wunused: YES 
> Compiler for C supports arguments -Wno-unused-parameter: YES 
> Compiler for C supports arguments -Wno-pedantic: YES 
> Compiler for C supports arguments 
> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56: YES 
> Compiler for C supports arguments 
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56: YES 
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency gio-unix-2.0 found: YES 2.70.3
> Run-time dependency gmodule-2.0 found: YES 2.70.3
> Run-time dependency libfprint-2 found: YES 1.94.2
> Run-time dependency polkit-gobject-1 found: YES 0.105
> Did not find 

Bug#1008818: needrestart: creates root-owned .rpmdb in non-root user $HOME, possibly corrupting existing one

[Thorsten Glaser]

Package: needrestart
Version: 3.5-4
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: t...@mirbsd.de

I did notice root-owned .rpmdb directories in my user home and,
after log inspection, was able to track it down to apt-get runs.

Some reproducing and grepping later I found it’s needrestart
which does that.


-- Package-specific info:
needrestart output:
Your outdated processes:
dbus-daemon[18689], dconf-service[25185], dirmngr[19601], lynx[690], 
mksh[13426, 2187, 19552], screen[2866, 2185], xdg-desktop-por[25155], 
xdg-document-po[25162], xdg-permission-[25166]



-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages needrestart depends on:
ii  binutils   2.35.2-2
ii  dpkg   1.20.9
ii  gettext-base   0.21-4
ii  libintl-perl   1.26-3
ii  libmodule-find-perl0.15-1
ii  libmodule-scandeps-perl1.30-1
ii  libproc-processtable-perl  0.59-2+b1
ii  libsort-naturally-perl 1.03-2
ii  libterm-readkey-perl   2.38-1+b2
ii  perl   5.32.1-4+deb11u2
ii  xz-utils   5.2.5-2

Versions of packages needrestart recommends:
ii  sysvinit-core  2.96-7+deb11u1

Versions of packages needrestart suggests:
ii  iucode-tool  2.3.1-1
pn  needrestart-session | libnotify-bin  

-- no debconf information

Bug#1006779: marked as done (flint-arb: FTBFS on mips64el: erfinv....Exception (FLINT memory_manager). Unable to allocate memory (145776024000).)

[Debian Bug Tracking System]

Your message dated Sat, 2 Apr 2022 10:11:36 +0300
with message-id <20220402071136.GA21107@localhost>
and subject line Fixed in 1:2.22.1-2
has caused the Debian Bug report #1006779,
regarding flint-arb: FTBFS on mips64el: erfinvException (FLINT 
memory_manager). Unable to allocate memory (145776024000).
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.)


-- 
1006779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flint-arb
Version: 1:2.22.1-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

flint-arb FTBFS on mips64el:

1f1_integration2f1_integrationairy_zerobessel_i_integrationPASS
bessel_jPASS
bessel_k_integrationPASS
bessel_yPASS
central_bin_uiPASS
ciPASS
coulomb_seriesPASS
erfPASS
erfinvException (FLINT memory_manager). Unable to allocate memory 
(145776024000).
make[3]: *** [../Makefile.subdirs:84: ../build/arb_hypgeom/test/t-erf_RUN] 
Aborted
make[3]: *** Waiting for unfinished jobs
PASS
PASS
PASS
make[3]: Leaving directory '/<>/arb_hypgeom'
make[2]: *** [Makefile:168: check] Error 2

See
https://buildd.debian.org/status/fetch.php?pkg=flint-arb=mips64el=1%3A2.22.1-1=1644766513=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1:2.22.1-2

flint-arb (1:2.22.1-2) unstable; urgency=medium

  * Add patch fixing a mips64el issue (Closes: #1007980).

 -- Julien Puydt   Fri, 01 Apr 2022 20:15:17 +0200--- End Message ---

Processed: affects 1008817

[Debian Bug Tracking System]

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

> affects 1008817 src:kitinerary
Bug #1008817 [libphonenumber8] libphonenumber8: breaks evolution
Added indication that 1008817 affects src:kitinerary
> thanks
Stopping processing here.

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

Processed: block 1008748 with 1008817

[Debian Bug Tracking System]

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

> block 1008748 with 1008817
Bug #1008748 [release.debian.org] Transition: KDEPIM 21.12
1008748 was not blocked by any bugs.
1008748 was not blocking any bugs.
Added blocking bug(s) of 1008748: 1008817
> thanks
Stopping processing here.

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