Processed: severity 1026001 serious

[Debian Bug Tracking System]

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

> severity 1026001 serious
Bug #1026001 [libpam-cap] libpam-cap: file conflict with package libcap2-bin
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1026007: nss-pem FTBFS on s390x: -Werror=stringop-overread

[Helmut Grohne]

Source: nss-pem
Version: 1.0.8-1
Severity: serious
Tags: ftbfs

nss-pem fails to build from source in unstable on s390x. This is not
reproducible on amd64. A build ends as follows:

| cc -o OBJS/hash.o -c -std=c99 -g -O2 
-ffile-prefix-map=/home/helmutg/nss-pem/nss-pem-1.0.8/nss=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I../nss/dist/private/nss -I../nss/dist/private/nss -Wall -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC   -pipe -ffunction-sections -fdata-sections 
-DHAVE_STRERROR -DLINUX -Dlinux -Wall -Wshadow -Werror -DXP_UNIX -DXP_UNIX 
-UDEBUG -DNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
-DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -UDEBUG -DNDEBUG -D_DEFAULT_SOURCE 
-D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT 
-DNSS_DISABLE_AVX2 -DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY 
-DNO_NSPR_10_SUPPORT -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -DSTDC_HEADERS 
-DHAVE_STRERROR -DHAVE_SNPRINTF -DMEMMOVE -D__DBINTERFACE_PRIVATE 
-I/usr/include/nspr -I/home/helmutg/nss-pem/nss-pem-1.0.8/nss/dist/include 
-I/home/helmutg/nss-pem/nss-pem-1.0.8/nss/dist/public/dbm 
-I/home/helmutg/nss-pem/nss-pem-1.0.8/nss/dist/private/dbm  hash.c
| hash.c: In function 'flush_meta':
| hash.c:629:19: error: 'write' reading 260 bytes from a region of size 4 
[-Werror=stringop-overread]
|   629 | ((wsize = write(fp, (char *)whdrp, sizeof(HASHHDR))) == -1))
|   |   ^
| In file included from hash.c:71:
| /home/helmutg/nss-pem/nss-pem-1.0.8/nss/dist/private/dbm/hash.h:81:11: note: 
source object 'magic' of size 4
|81 | int32 magic; /* Magic NO for hash tables */
|   |   ^
| In file included from hash.c:62:
| /usr/include/unistd.h:378:16: note: in a call to function 'write' declared 
with attribute 'access (read_only, 2, 3)'
|   378 | extern ssize_t write (int __fd, const void *__buf, size_t __n) __wur
|   |^
| cc1: all warnings being treated as errors
| make[8]: *** [../../../coreconf/rules.mk:292: OBJS/hash.o] Error 1
| make[8]: Leaving directory 
'/home/helmutg/nss-pem/nss-pem-1.0.8/nss/nss/lib/dbm/src'
| make[7]: *** [../../coreconf/rules.mk:44: src] Error 2
| make[7]: Leaving directory 
'/home/helmutg/nss-pem/nss-pem-1.0.8/nss/nss/lib/dbm'
| make[6]: *** [../coreconf/rules.mk:44: dbm] Error 2
| make[6]: Leaving directory '/home/helmutg/nss-pem/nss-pem-1.0.8/nss/nss/lib'
| make[5]: *** [coreconf/rules.mk:44: lib] Error 2
| make[5]: Leaving directory '/home/helmutg/nss-pem/nss-pem-1.0.8/nss/nss'
| make[4]: *** [manifest.mn:21: all] Error 2
| make[4]: Leaving directory '/home/helmutg/nss-pem/nss-pem-1.0.8/nss/nss'
| make[3]: *** [debian/rules:101: override_dh_auto_build] Error 2
| make[3]: Leaving directory '/home/helmutg/nss-pem/nss-pem-1.0.8/nss'
| make[2]: *** [debian/rules:195: build] Error 2
| make[2]: Leaving directory '/home/helmutg/nss-pem/nss-pem-1.0.8/nss'
| make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/home/helmutg/nss-pem/nss-pem-1.0.8'
| make: *** [debian/rules:12: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

The issue also is reproducible by cross building from amd64 to s390x,
but it seems fairly recent as https://crossqa.debian.net/src/nss-pem
doesn't have any trace of it. Also reproducible builds hasn't seen it
either. The build above was performed on zelenka.debian.org to rule out
any local and emulation issues.

Helmut

Bug#1026005: cumin FTBFS: Tries to use $HOME

[Adrian Bunk]

Source: cumin
Version: 4.1.1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cumin&ver=4.1.1-2

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
SETUPTOOLS_SCM_PRETEND_VERSION="4.1.1-2" python3 setup.py develop --user
/usr/lib/python3/dist-packages/setuptools/dist.py:530: UserWarning: Normalizing 
'4.1.1-2' to '4.1.1.post2'
  warnings.warn(tmpl.format(**locals()))
running develop
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
and pip and other standards-based tools.
  warnings.warn(
error: [Errno 13] Permission denied: '/sbuild-nonexistent'
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1


This can be reproduced with
  HOME=/sbuild-nonexistent dpkg-buildpackage

Bug#1026004: sunpy FTBFS with Python 3.11

[Adrian Bunk]

Source: sunpy
Version: 4.0.6-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sunpy&arch=amd64&ver=4.0.6-1%2Bb1&stamp=1670443464&raw=0

...
=
 FAILURES 
=
__ 
test_popitem_with_keycomments 
___

atomic_weights_keycomments = [['hydrogen', 1], ['chromium', 24], ['mercury', 
80], ['iridium', 77], ['keycomments', {'MERCURY': 'Hg', 'chromium': 'Cr', 
'extra key 1': 'foo', 'extra key 2': 'bar'}]]
empty_keycomments = [['keycomments', {}]]

def test_popitem_with_keycomments(atomic_weights_keycomments, 
empty_keycomments):
"""
Test `MetaDict.popitem(...)` removes corresponding keycomments.
"""
md = MetaDict(atomic_weights_keycomments)

assert md.popitem(last=False) == ('hydrogen', 1)
assert md.popitem(last=False) == ('chromium', 24)
assert md.popitem(last=False) == ('mercury', 80)
assert md.popitem(last=False) == ('iridium', 77)
>   check_contents_and_insertion_order(md, empty_keycomments)

sunpy/util/tests/test_metadata.py:389: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ 
sunpy/util/tests/test_metadata.py:47: in check_contents_and_insertion_order
check_contents(metadict_inst, expected)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ 

metadict_inst = MetaDict([('keycomments', {'chromium': 'Cr', 'MERCURY': 
'Hg'})]), expected = [['keycomments', {}]]

def check_contents(metadict_inst, expected):
"""
Ensure that the key/values of `metadict_inst` match those of the 
key/value
pairs in `expected`.

The case of the keys is ignored, as is the order.
"""
assert len(metadict_inst) == len(expected)

for key, val in expected:
>   assert metadict_inst[key.upper()] == val
E   AssertionError: assert {'MERCURY': '...romium': 'Cr'} == {}
E Left contains 2 more items:
E {'MERCURY': 'Hg', 'chromium': 'Cr'}
E Use -v to get more diff

sunpy/util/tests/test_metadata.py:19: AssertionError
=
 warnings summary 
=
../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1252
  /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1252: 
PytestConfigWarning: Unknown config option: mpl-results-path
  
self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1252
  /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1252: 
PytestConfigWarning: Unknown config option: mpl-use-full-test-name
  
self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
= 
short test summary info 
==
FAILED sunpy/util/tests/test_metadata.py::test_popitem_with_keycomments - 
AssertionError: assert {'MERCURY': '...romium': 'Cr'} == {}
= 1 failed, 2204 passed, 278 skipped, 10 
deselected, 5 xfailed, 2 xpassed, 2 warnings in 118.82s (0:01:58) 
=
E: pybuild pybuild:386: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_sunpy/build; python3.11 -m pytest -k 
"not figure and not online"
...


This is different from #1024248, which seems to be temporarily fixed
by shipping a release and not a git snapshot.

Bug#1022255: fixed in python-xarray 2022.11.0-2

[Antonio Valentino]

Dear Alastair,

Il 12/12/22 12:34, Alastair McKinstry ha scritto:

Dear Antonio


Apologies but I saw this too late to stop the transition to testing.

At this stage, I believe the best solution is to work on the issues in 
satpy and dask; I can help.


Thanks for your kind offer.
Luckily I was able to implement a patch with a workaround for satpy.
I have uploaded a new version that, hopefully, should be able to migrate 
without problems.

We still do not have the CI tests on all platforms anyway.


Kind regards
antonio


On 07/12/2022 08:38, Antonio Valentino wrote:

Dear Alastair,

On Mon, 21 Nov 2022 15:12:02 + Debian FTP Masters 
 wrote:

Source: python-xarray
Source-Version: 2022.11.0-2
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated 
python-xarray package)


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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Nov 2022 14:37:38 +
Source: python-xarray
Architecture: source
Version: 2022.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 


Changed-By: Alastair McKinstry 
Closes: 1004869 1022255 1023222
Changes:
 python-xarray (2022.11.0-2) unstable; urgency=medium
 .
   * Ack bogs fixed in this and previous releases:
 Closes: #1022255, #1004869, #1023222
Checksums-Sha1:
 25bfc4ad68c46f9f7428c7a008736478f3bd2fa7 3395 
python-xarray_2022.11.0-2.dsc
 9d5fa48523ea38b6684f9b18e3d3a10a8aee2875 14092 
python-xarray_2022.11.0-2.debian.tar.xz

Checksums-Sha256:
 2921fcf4d7b5b82ed54813180ceacb2261264e99eb22e1b9bcf11e8660755e6e 
3395 python-xarray_2022.11.0-2.dsc
 c480af287094772516773b559ac385d6eed33001e1ded8aa1ddab4db721fc91b 
14092 python-xarray_2022.11.0-2.debian.tar.xz

Files:
 16ee7843761bf700d78213b6a8061f38 3395 python optional 
python-xarray_2022.11.0-2.dsc
 b483b08efbb572a27c4af434d3df17d1 14092 python optional 
python-xarray_2022.11.0-2.debian.tar.xz


-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmN7jiUACgkQy+a7Tl2a
06Vb0Q//YmFju6NG15oqqygNRQiiGIGPXS+qvtwPbXKGJDq6g3rX24KdF2tP77i6
Aw9LjfskclEe7TRQCwaS/49qh+6CE+Tndv47nMGb3jnBGL0vYa9YqOn3XeBAHCcw
aYCvbkks5HxDWizJ6Kh2Ohef0okEl2Q/pHDKMDfF+Q8DEvGh7iFtedVF6ARquPSW
95u3V6QhCCQPws26cYPz1L2a+QJuEf49lohoVDC8u4EtaJHbv1NKXtQP1srEqf10
zqbSd6KDqT3mn4dONtF7etxzQGxSHRySEPJpXQ+2kkdmcueLUT5UAEazC6SCdCUB
GMCqMFbwi4kY7CaaK5646XxCm3QQUg3UeZAMHqsBI9gYModfKG8twRhlyA4N9mam



Unfortunately version 2022.11.2 and 2022.12.0 of xarray still causes 
test failures in satpy.
According to the satpy upstream developers [1] (also reported in one 
of the previous messages [2]), the problem should be related to some 
kind of incompatibility between new versions of xarray and the version 
of dask currently in Debian (2022.02.0).


I can confirm that updating dask to 2022.11.1 fixes the issues and 
satpy tests pass with dask 2022.11.1 and xarray 2022.12.0.


I have started preparing a Merge Request [3] to update the dask package.
Unfortunately, while the Python package itself builds and works well, 
it is currently not possible to build the -doc package because of 
outdated build dependencies or new build dependencies still not in 
debian.


In addition, there are some other test failures in satpy that are not 
related to xarray/dask and could be fixed with an update to the latest 
upstream version of satpy (0.38.0).
I have the packaging work done (locally), but I cannot upload until 
the problem with xarray/dask is solved.


In conclusion the satpy version currently in testing works perfectly 
with xarray 2022.06.0, but the migration of xarray 2022.12.0 would 
break satpy and make it unbuildable both in testing and unstable.


Honestly I'm not sure about what is the best way to proceed.
In principle I think that this issue should be re-open and xarray 
2022.12.0 should not migrate, for the moment at least.


But then the way forward is not clear to me.
Waiting for an update of dask could take some time.
Of course I would be more that happy to help to prepare a new version 
of the dask package.


What is your idea about how to proceed?

[1] https://github.com/pytroll/satpy/issues/2248#issuecomment-1296325915
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022255#16
[3] https://salsa.debian.org/python-team/packages/dask/-/merge_requests/1


kind regards




--
Antonio Valentino

Bug#1026002: FTBFS gcc: error: LinuxMachineDefines: linker input file not found: No such file or directory

[sun min]

Source: xlax
Version: 2.4-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-multime...@lists.debian.org

Dear Maintainer,

xlax failed to build from source for architecture riscv64,it complains:
gcc: warning: LinuxMachineDefines: linker input file unused because linking not 
done
gcc: error: LinuxMachineDefines: linker input file not found: No such file or 
directory
make[1]: *** [: xlax.o] Error 1
make[1]: Leaving directory '/<>/builddir'
make: *** [debian/rules:37: builddir/xlax] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: riscv64

Kernel: Linux 5.10.102.1-microsoft-standard-WSL2+ (SMP w/4 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: unable to detect

Bug#1025954: would you like to test new patch?

[Vagrant Cascadian]

On 2022-12-13, 张 宁 wrote:
> I understand why it fail to boot.
>
> static int parse_label(char **c, struct pxe_menu *cfg)
> it failed to parse "kalsrseed", and move to uplayer, and uplayer still don't 
> know how to handle it.
> and affected "append"

Thanks for looking into it!

> I don't have old version u-boot, thus can't test it out.
>
> I have a new patch, would you like to have a try.
> diff --git a/u-boot-update b/u-boot-update
> index 90c4087..ebcf8cf 100755
> --- a/u-boot-update
> +++ b/u-boot-update
> @@ -257,6 +257,7 @@ label l${_NUMBER}
>   ${_FDT}
>   ${_FDTOVERLAYS}
>   append ${U_BOOT_ROOT} ${U_BOOT_PARAMETERS}"
> + kalsrseed
>  
>   fi

Yeah, this is basically the same as what Arnaud Ferraris proposed.

I worry a bit that this is just a workaround a deeper problem... though
maybe it is the best we have.

For now I uploaded a version that reverted the kaslrseed support and
will test more thoroughly before re-uploading with the kaslrseed support
enabled again.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1024299: pythonmagick: b-d on python3-all-dev, but not built for all supported Python3 versions

[Stuart Prescott]

Control: block -1 by 1025658

On Fri, 18 Nov 2022 17:53:28 +0200 Stefano Rivera  
wrote:


> That's an easy fix. However... the resulting binary fails to import
> under Python 3.11. That needs more debugging.

Given the Build-Depends on libboost-python-dev, the failure to import 
will be #1025658 again.


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

Processed: Re: Bug#1024299: pythonmagick: b-d on python3-all-dev, but not built for all supported Python3 versions

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1025658
Bug #1024299 [src:pythonmagick] pythonmagick: only default python3 version 
extension is published in deb
1024299 was not blocked by any bugs.
1024299 was not blocking any bugs.
Added blocking bug(s) of 1024299: 1025658

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

Bug#1025954: would you like to test new patch?

[张 宁]

Hi,
I understand why it fail to boot.

static int parse_label(char **c, struct pxe_menu *cfg)
it failed to parse "kalsrseed", and move to uplayer, and uplayer still don't 
know how to handle it.
and affected "append"

I don't have old version u-boot, thus can't test it out.

I have a new patch, would you like to have a try.
diff --git a/u-boot-update b/u-boot-update
index 90c4087..ebcf8cf 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -257,6 +257,7 @@ label l${_NUMBER}
 	${_FDT}
 	${_FDTOVERLAYS}
 	append ${U_BOOT_ROOT} ${U_BOOT_PARAMETERS}"
+	kalsrseed
 
 	fi
 

Processed: tagging 1025986, tagging 1025985

[Debian Bug Tracking System]

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

> tags 1025986 + sid bookworm
Bug #1025986 [src:runawk] FTBFS: install: cannot change owner and permissions 
of ‘/<>/debian/.debhelper/generated/_source/home’: Operation not 
permitted
Added tag(s) sid and bookworm.
> tags 1025985 + sid bookworm
Bug #1025985 [src:glosstex] glosstext: FTBFS: LaTeX Error: File 
`pdftexcmds.sty' not found.
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#985520: marked as done (shove: broken symlink: /usr/bin/shove -> ../share/shove/bin/shove)

[Debian Bug Tracking System]

Your message dated Tue, 13 Dec 2022 01:34:21 +
with message-id 
and subject line Bug#985520: fixed in shove 0.8.4-2
has caused the Debian Bug report #985520,
regarding shove: broken symlink: /usr/bin/shove -> ../share/shove/bin/shove
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.)


-- 
985520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shove
Version: 0.8.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m22.8s ERROR: FAIL: Broken symlinks:
  /usr/bin/shove -> ../share/shove/bin/shove (shove)


cheers,

Andreas


shove_0.8.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: shove
Source-Version: 0.8.4-2
Done: ChangZhuo Chen (陳昌倬) 

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated shove package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Dec 2022 09:04:34 +0800
Source: shove
Architecture: source
Version: 0.8.4-2
Distribution: unstable
Urgency: medium
Maintainer: ChangZhuo Chen (陳昌倬) 
Changed-By: ChangZhuo Chen (陳昌倬) 
Closes: 985520
Changes:
 shove (0.8.4-2) unstable; urgency=medium
 .
   * Fix /usr/bin/shove installation. (Closes: #985520)
   * Bump Standards-Version to 4.6.1.
   * Update Build-Depends.
   * Update d/watch for GitHub.
   * Add d/gbp.conf.
Checksums-Sha1:
 e7fc87170e1d5909869cbe93a1285ba3b1eb230f 1818 shove_0.8.4-2.dsc
 14f28d46975e74e042cb33505514618a3a19f752 2504 shove_0.8.4-2.debian.tar.xz
 2a4cfd9654bd2fa039a5868c83ba65ac9867e682 6373 shove_0.8.4-2_amd64.buildinfo
Checksums-Sha256:
 fdabec19870d825f1bb47ca00474086d23489d1dcf57cd91a2f461a56ead6cef 1818 
shove_0.8.4-2.dsc
 4aa96ce4a36f69e10603e42531032b8b713db863e5b174ac2a22cddef32a5e27 2504 
shove_0.8.4-2.debian.tar.xz
 e66e329fea5b15a65b63e8c09d5a3cf18633f7baa4aed7889a5b81978c680ac8 6373 
shove_0.8.4-2_amd64.buildinfo
Files:
 5e7a61c9d2cc2a4e32707829953f0578 1818 devel optional shove_0.8.4-2.dsc
 71fa7dbb43a99ac60a7bbe8db72bb44f 2504 devel optional 
shove_0.8.4-2.debian.tar.xz
 592bfa627a3bfaa0c4167ec8f5b5550d 6373 devel optional 
shove_0.8.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEugQ0bcLh/mPHkIeTzGWwzewnXVsFAmOX0HYACgkQzGWwzewn
XVsYWA//WfdN5vradgvlvHO/2dmDDJrixFS8kol7Ut5WxSToRUQP2zIi6zD93Y/z
GA81XEzgTr2xIvWpkLIKdpfStNHhjL6hjWUhzu7dqA14HtJ1ZBy9UUBwOEmDUqaL
RQ7Ia4bnYPjRXBI+vfEqu5APAI8i7hPNzXYBzn7/sh3SgmU5PceoMW+7zkVS26Mq
ZhM0nq5zub3AEsg41H3EWy+xzWuV3U0LPbjFAoLn0ZL6Vwq4/BKsHhhEMmSDm0mC
FGsiBengBPBOMnhKUUFcefNtCixNkKaGMPkhJVwlij6kUZD+bcCMkqrHMdCTgtrC
87xBC23kueZjOkdyZhP0JrT0bYICOnunJ2sKI04PZTYU+EKx20zvo8QSN2wnuCd+
HBc3mGZg8vnTYP54c/rtNoGiwTFHL/5fnQYrCrJb9fpuvU3puQwRIPhY500dmBJv
nFi60+HiRoK8nRlubU58DgWD9ruI5nmpHVWAYZVRehX/HWX3K+RTVPr0tRzC6YMy
AwbwgU9amaVOcoyj2tWKZuN/5H2aXC0cO4KWCziyWby4/ORbcYPk9+pDnmOG9UIY
gn7+Wam33THammewTY5l7ajPzDOe2jxKz6RxD5lJeMSUHV/VPlSNcY8aSKYZARVx
ibB9L+agti1I+wnjpVmbHtRiB3YvpixjqtkHgxq0M5Zuwylm5WY=
=OUqM
-END PGP SIGNATURE End Message ---

Bug#1025908: marked as done (systemd: flaky autopkgtest: test_resolved_domain_restricted_dns)

[Debian Bug Tracking System]

Your message dated Tue, 13 Dec 2022 00:35:38 +
with message-id 
and subject line Bug#1025908: fixed in systemd 252.3-2
has caused the Debian Bug report #1025908,
regarding systemd: flaky autopkgtest: test_resolved_domain_restricted_dns
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.)


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

Source: systemd
Version: 251.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. It seems that DNS either times out or isn't 
really reliable. I suggest to either increase the timeout (if that's the 
cause, skip the test, or make it retry at least once.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/i386/s/systemd/29214658/log.gz

==
ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
   File 
"/tmp/autopkgtest-lxc.45d4ds2y/downtmp/build.g5f/src/test/networkd-test.py", 
line 686, in test_resolved_domain_restricted_dns
 out = subprocess.check_output(['resolvectl', 'query', 
'search.example.com'])

   File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
 return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
   File "/usr/lib/python3.10/subprocess.py", line 526, in run
 raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['resolvectl', 'query', 
'search.example.com']' returned non-zero exit status 1.


--


https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/29160541/log.gz

==
ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
   File 
"/tmp/autopkgtest-lxc.65kf3irc/downtmp/build.HiP/src/test/networkd-test.py", 
line 686, in test_resolved_domain_restricted_dns
 out = subprocess.check_output(['resolvectl', 'query', 
'search.example.com'])

   File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
 return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
   File "/usr/lib/python3.10/subprocess.py", line 526, in run
 raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['resolvectl', 'query', 
'search.example.com']' returned non-zero exit status 1.






OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 252.3-2
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Dec 2022 01:03:58 +0100
Source: systemd
Architecture: source
Version: 252.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Closes: 1025908
Changes:
 systemd (252.3-2) unstable; urgency=medium
 .
   * Skip flaky test_resolved_domain_restricted_dns in networkd-test.py.
 This test is part of DnsmasqClientTest and does not work reliably under
 LXC/debci, so skip i

Bug#965835: tcd-utils: NMU to fix RC bugs

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to NMU to fix RC bugs #965835 and #999110

The debdiff is attached.

My plan is I'll wait until 20th Dec and then upload to delay/10 queue.

Yours,
Paul
diff -Nru tcd-utils-20061127/debian/changelog 
tcd-utils-20061127/debian/changelog
--- tcd-utils-20061127/debian/changelog 2022-12-13 08:35:09.0 +0800
+++ tcd-utils-20061127/debian/changelog 2022-12-13 08:10:54.0 +0800
@@ -1,3 +1,12 @@
+tcd-utils (20061127-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use DebSrc3.0 (quilt) format.
+  * Bump debhelper compat to 12 (Closes: #965835)
+  * debian/rules: Use dh (Closes: #999110)
+
+ -- Ying-Chun Liu (PaulLiu)   Tue, 13 Dec 2022 08:10:54 
+0800
+
 tcd-utils (20061127-2) unstable; urgency=low
 
   * Bug fix: "tcd-utils: FTBFS: checking for tcd.h... no".  Forgot to add
diff -Nru tcd-utils-20061127/debian/compat tcd-utils-20061127/debian/compat
--- tcd-utils-20061127/debian/compat2022-12-13 08:35:09.0 +0800
+++ tcd-utils-20061127/debian/compat1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru tcd-utils-20061127/debian/control tcd-utils-20061127/debian/control
--- tcd-utils-20061127/debian/control   2022-12-13 08:35:09.0 +0800
+++ tcd-utils-20061127/debian/control   2022-12-13 08:10:54.0 +0800
@@ -1,8 +1,8 @@
 Source: tcd-utils
 Section: science
-Priority: extra
+Priority: optional
 Maintainer: Peter S Galbraith 
-Build-Depends: debhelper (>= 5), autotools-dev, libtcd-dev
+Build-Depends: debhelper-compat (= 12), libtcd-dev
 Standards-Version: 3.7.2
 
 Package: tcd-utils
@@ -13,4 +13,4 @@
  tcd-utils are command-line tools for converting Tide Constituent Database
  (TCD) files to and from other formats.  They are used to create tidal
  harmonics files used by XTide (see the xtide package), such as those found
- in the xtide-data package.
\ 檔案末沒有 newline 字元
+ in the xtide-data package.
diff -Nru tcd-utils-20061127/debian/rules tcd-utils-20061127/debian/rules
--- tcd-utils-20061127/debian/rules 2022-12-13 08:35:09.0 +0800
+++ tcd-utils-20061127/debian/rules 2022-12-13 08:10:54.0 +0800
@@ -15,87 +15,8 @@
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 
+%:
+   dh $@
 
-CFLAGS = -Wall -g
-
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-   CFLAGS += -O0
-else
-   CFLAGS += -O2
-endif
-
-config.status: configure
-   dh_testdir
-   # Add here commands to configure the package.
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-   cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-   cp -f /usr/share/misc/config.guess config.guess
-endif
-   ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) 
--prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info 
CFLAGS="$(CFLAGS)" LDFLAGS="-Wl,-z,defs"
-
-
-build: build-stamp
-
-build-stamp:  config.status
-   dh_testdir
-
-   $(MAKE)
-
-   touch $@
-
-clean:
-   dh_testdir
-   dh_testroot
-   rm -f build-stamp 
-   -$(MAKE) distclean
-   rm -f config.sub config.guess
-
-   dh_clean 
-
-install: build
-   dh_testdir
-   dh_testroot
-   dh_clean -k 
-   dh_installdirs
-   $(MAKE) DESTDIR=$(CURDIR)/debian/tcd-utils install
-
-
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
-# Build architecture-dependent files here.
-binary-arch: build install
-   dh_testdir
-   dh_testroot
-   dh_installchangelogs ChangeLog
-   dh_installdocs
-   dh_installexamples
-#  dh_install
-#  dh_installmenu
-#  dh_installdebconf   
-#  dh_installlogrotate
-#  dh_installemacsen
-#  dh_installpam
-#  dh_installmime
-#  dh_python
-#  dh_installinit
-#  dh_installcron
-#  dh_installinfo
-   dh_installman
-   dh_link
-   dh_strip
-   dh_compress
-   dh_fixperms
-#  dh_perl
-#  dh_makeshlibs
-   dh_installdeb
-   dh_shlibdeps
-   dh_gencontrol
-   dh_md5sums
-   dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+override_dh_auto_configure:
+   dh_auto_configure -- --prefix=/usr --mandir=\$${prefix}/share/man 
--infodir=\$${prefix}/share/info
diff -Nru tcd-utils-20061127/debian/source/format 
tcd-utils-20061127/debian/source/format
--- tcd-utils-20061127/debian/source/format 1970-01-01 08:00:00.0 
+0800
+++ tcd-utils-20061127/debian/source/format 2022-12-13 08:10:54.0 
+0800
@@ -0,0 +1 @@
+3.0 (quilt)


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023341: Fails to add any event due to too new python3-tzlocal

[Daniele Tricoli]

Hello,

On 02/11/2022 17:04, Guido Günther wrote:

[CUT]


This because khal can't cope with recent python3-tzlocal from bookworm (4.2-1),
downgrading python3-tzlocal (2.1-1) makes adding events work again (Got that
hint https://github.com/pimutils/khal/issues/1092)


It seems to be fixed in version in 0.10.5¹, changelog mention this entry:

- FIX support for tzlocal >= 4.0

So updating the package should fix this.

Cheers,

¹ https://github.com/pimutils/khal/issues/1196

--
Daniele Tricoli
https://mornie.org


OpenPGP_0x8BAF522C0D6CCEDD.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1025908: marked as pending in systemd

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #1025908 in systemd 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/systemd-team/systemd/-/commit/ecc39a3106a6bf9ccbbc3b98c7b5d72074b68431


Skip flaky test_resolved_domain_restricted_dns in networkd-test.py

This test is part of DnsmasqClientTest and does not work reliably under
LXC/debci, so skip it for the time being.

Closes: #1025908


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025908

Processed: Bug#1025908 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025908 [src:systemd] systemd: flaky autopkgtest: 
test_resolved_domain_restricted_dns
Added tag(s) pending.

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

Bug#965861: vcheck: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to fix this RC bugs by NMU.

Please see the attached debdiff.

I'll wait until 20th Dec and then upload to delay/10 queue.

Yours,
Paul
diff -Nru vcheck-1.2.1/debian/changelog vcheck-1.2.1/debian/changelog
--- vcheck-1.2.1/debian/changelog   2015-08-27 00:56:56.0 +0800
+++ vcheck-1.2.1/debian/changelog   2022-12-13 08:01:53.0 +0800
@@ -1,3 +1,10 @@
+vcheck (1.2.1-7.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Bimp debhelper compat to 12. (Closes: #965861)
+
+ -- Ying-Chun Liu (PaulLiu)   Tue, 13 Dec 2022 08:01:53 
+0800
+
 vcheck (1.2.1-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru vcheck-1.2.1/debian/compat vcheck-1.2.1/debian/compat
--- vcheck-1.2.1/debian/compat  2011-02-11 09:04:07.0 +0800
+++ vcheck-1.2.1/debian/compat  1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru vcheck-1.2.1/debian/control vcheck-1.2.1/debian/control
--- vcheck-1.2.1/debian/control 2011-02-11 09:17:24.0 +0800
+++ vcheck-1.2.1/debian/control 2022-12-13 07:57:11.0 +0800
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Dario Minnucci 
 Standards-Version: 3.9.1
-Build-Depends: debhelper (>= 7.0.50~), perl, libwww-perl (>= 5.0)
+Build-Depends: debhelper-compat (= 12), perl, libwww-perl (>= 5.0)
 Homepage: http://www.tu-ilmenau.de/~gomar/stuff/vcheck
 Vcs-Git: git://git.debian.org/collab-maint/vcheck.git
 Vcs-Browser: http://git.debian.org/?p=collab-maint/vcheck.git
diff -Nru vcheck-1.2.1/debian/copyright vcheck-1.2.1/debian/copyright
--- vcheck-1.2.1/debian/copyright   2011-02-11 11:20:57.0 +0800
+++ vcheck-1.2.1/debian/copyright   2022-12-13 07:58:51.0 +0800
@@ -5,12 +5,12 @@
 Files: *
 Copyright: 1999-2001 Marco Goetze  
 License: Artistic
-On a Debian system a copy of the Perl license can be found in the file
-'/usr/share/common-licenses/Artistic'.
 
 Files: debian/*
 Copyright: 2002-2004, Ardo van Rangelrooij 
2007-2011, Dario Minnucci  
 License: Artistic
-On a Debian system a copy of the Perl license can be found in the file
-'/usr/share/common-licenses/Artistic'.
+
+License: Artistic
+ On a Debian system a copy of the Perl license can be found in the file
+ '/usr/share/common-licenses/Artistic'.


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1025286: marked as done (nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 23:50:46 +
with message-id 
and subject line Bug#1025286: fixed in nvidia-graphics-drivers-tesla-510 
510.108.03-1
has caused the Debian Bug report #1025286,
regarding nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, 
CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, 
CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
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.)


-- 
1025286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5415

CVE-2022-34670  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an unprivileged
regular user can cause truncation errors when casting a primitive to a
primitive of smaller size causes data to be lost in the conversion,
which may lead to denial of service or information disclosure.

CV

Bug#1025279: marked as done (nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CV

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 23:50:46 +
with message-id 
and subject line Bug#1025279: fixed in nvidia-graphics-drivers-tesla-510 
510.108.03-1
has caused the Debian Bug report #1025279,
regarding nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, 
CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, 
CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
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.)


-- 
1025279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, 
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, 
CVE-2022-42264
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, 
CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, 
CVE-2022-42263, CVE-2022-42264
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5415

CVE-2022-34670  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer handler, where an unprivileged
regular user can cause truncation errors when casting a primitive to a
primitive of smaller size causes data to be lost in the conversion,
which may lead to denial of service or information disclosure.

CVE-2022-422

Bug#965747: netsend: NMU to fix RC bugs.

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to fix RC bugs #965747 and #999046 by NMU.

Please see the debdiff as attachment.

I'll wait until 20th Dec and then upload it to delay/10 queue.

Yours,
Paul
diff -Nru netsend-0.0~svnr250/debian/changelog 
netsend-0.0~svnr250/debian/changelog
--- netsend-0.0~svnr250/debian/changelog2022-12-13 07:49:30.0 
+0800
+++ netsend-0.0~svnr250/debian/changelog2022-12-13 07:24:55.0 
+0800
@@ -1,3 +1,12 @@
+netsend (0.0~svnr250-1.5) unstable; urgency=low
+
+  * Non-maintainer upload. (Closes: #1011647)
+  * Bump debhelper compat to 12 (Closes: #965747)
+  * debian/rules: Use dh. (Closes: #999046)
+  * Port to DebSrc3.0 (quilt).
+
+ -- Ying-Chun Liu (PaulLiu)   Tue, 13 Dec 2022 07:24:55 
+0800
+
 netsend (0.0~svnr250-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru netsend-0.0~svnr250/debian/compat netsend-0.0~svnr250/debian/compat
--- netsend-0.0~svnr250/debian/compat   2022-12-13 07:49:30.0 +0800
+++ netsend-0.0~svnr250/debian/compat   1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru netsend-0.0~svnr250/debian/control netsend-0.0~svnr250/debian/control
--- netsend-0.0~svnr250/debian/control  2022-12-13 07:49:30.0 +0800
+++ netsend-0.0~svnr250/debian/control  2022-12-13 07:24:55.0 +0800
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Martin Peylo 
-Build-Depends: debhelper (>= 5), linux-libc-dev, perl
+Build-Depends: debhelper-compat (= 12), linux-libc-dev, perl
 Standards-Version: 3.7.3
 Homepage: http://netsend.berlios.de/
 
diff -Nru netsend-0.0~svnr250/debian/netsend.examples 
netsend-0.0~svnr250/debian/netsend.examples
--- netsend-0.0~svnr250/debian/netsend.examples 1970-01-01 08:00:00.0 
+0800
+++ netsend-0.0~svnr250/debian/netsend.examples 2022-12-13 07:24:55.0 
+0800
@@ -0,0 +1 @@
+unit_test.sh
diff -Nru netsend-0.0~svnr250/debian/netsend.manpages 
netsend-0.0~svnr250/debian/netsend.manpages
--- netsend-0.0~svnr250/debian/netsend.manpages 1970-01-01 08:00:00.0 
+0800
+++ netsend-0.0~svnr250/debian/netsend.manpages 2022-12-13 07:24:55.0 
+0800
@@ -0,0 +1 @@
+netsend.1
diff -Nru netsend-0.0~svnr250/debian/patches/0001_Makefile.patch 
netsend-0.0~svnr250/debian/patches/0001_Makefile.patch
--- netsend-0.0~svnr250/debian/patches/0001_Makefile.patch  1970-01-01 
08:00:00.0 +0800
+++ netsend-0.0~svnr250/debian/patches/0001_Makefile.patch  2022-12-13 
07:24:55.0 +0800
@@ -0,0 +1,11 @@
+--- netsend-0.0~svnr250.orig/Makefile
 netsend-0.0~svnr250/Makefile
+@@ -44,7 +44,7 @@
+   @bash configure
+ 
+ $(TARGET): $(OBJECTS)
+-  $(CC) $(LIBS) $(CFLAGS) -o $(TARGET) $(OBJECTS)
++  $(CC) $(CFLAGS) -o $(TARGET) $(OBJECTS) $(LIBS)
+ 
+ %.o: %.c analyze.h error.h global.h xfuncs.h Makefile
+   $(CC) $(CFLAGS) -c  $< -o $@
diff -Nru netsend-0.0~svnr250/debian/patches/0002_netsend_pod.patch 
netsend-0.0~svnr250/debian/patches/0002_netsend_pod.patch
--- netsend-0.0~svnr250/debian/patches/0002_netsend_pod.patch   1970-01-01 
08:00:00.0 +0800
+++ netsend-0.0~svnr250/debian/patches/0002_netsend_pod.patch   2022-12-13 
07:24:55.0 +0800
@@ -0,0 +1,14 @@
+--- netsend-0.0~svnr250.orig/netsend.pod
 netsend-0.0~svnr250/netsend.pod
+@@ -128,6 +128,11 @@
+ 
+ =back
+ 
++=back
++
++=back
++
++=back
+ 
+ =head1 EXIT STATUS
+ 
diff -Nru netsend-0.0~svnr250/debian/patches/0003_proto_udplite_recv.patch 
netsend-0.0~svnr250/debian/patches/0003_proto_udplite_recv.patch
--- netsend-0.0~svnr250/debian/patches/0003_proto_udplite_recv.patch
1970-01-01 08:00:00.0 +0800
+++ netsend-0.0~svnr250/debian/patches/0003_proto_udplite_recv.patch
2022-12-13 07:24:55.0 +0800
@@ -0,0 +1,10 @@
+--- netsend-0.0~svnr250.orig/proto_udplite_recv.c
 netsend-0.0~svnr250/proto_udplite_recv.c
+@@ -22,6 +22,7 @@
+ 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru netsend-0.0~svnr250/debian/patches/0004_proto_udplite_trans.patch 
netsend-0.0~svnr250/debian/patches/0004_proto_udplite_trans.patch
--- netsend-0.0~svnr250/debian/patches/0004_proto_udplite_trans.patch   
1970-01-01 08:00:00.0 +0800
+++ netsend-0.0~svnr250/debian/patches/0004_proto_udplite_trans.patch   
2022-12-13 07:24:55.0 +0800
@@ -0,0 +1,10 @@
+--- netsend-0.0~svnr250.orig/proto_udplite_trans.c
 netsend-0.0~svnr250/proto_udplite_trans.c
+@@ -24,6 +24,7 @@
+ 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru netsend-0.0~svnr250/debian/patches/series 
netsend-0.0~svnr250/debian/patches/series
--- netsend-0.0~svnr250/debian/patches/series   1970-01-01 08:00:00.0 
+0800
+++ netsend-0.0~svnr250/debian/patches/series   2022-12-13 07:24:55.0 
+0800
@@ -0,0 +1,4 @@
+0001_Makefile.patch
+0002_netsend_pod.patch
+0003_proto_udplite_recv.patch
+0004_proto_udplite_trans.patch
diff -Nru netsend-0.0~svnr250/debian/rules netsend-0.0~svnr250/debian/rules
--- netsend-0.0~svnr250/debian/ru

Bug#1011647: RM: netsend -- RoQA, RC-buggy, dead-upstream, unmaintained, low popcon

[Ying-Chun Liu (PaulLiu)]

Hi,

I plan to NMU this package to fix RC bugs.

Yours,
Paul


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1025954: u-boot-menu | add kalsrseed support (!7)

[Zhang Ning]

On Mon, Dec 12, 2022 at 09:29:25PM +, Vagrant Cascadian (@vagrant) wrote:
> 
> 
> 
> Vagrant Cascadian commented:
> 
> 
> This apparently causes issues with older u-boot versions:
> 
> https://bugs.debian.org/1025954

it just prints warning to  console, does it reject to boot?



> 
> I will revert this change until more testing can be done...
> 
> -- 
> Reply to this email directly or view it on GitLab: 
> https://salsa.debian.org/debian/u-boot-menu/-/merge_requests/7#note_361514
> You're receiving this email because of your account on salsa.debian.org.
> 
> 

Bug#965589: iat: NMU to fix RC bugs.

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to NMU iat to fix #965589 and #999305.
Please see the debdiff as attachment.

My plan is I'll wait until 20th Dec. And then upload it to delay/10 queue.

Yours,
Paul

diff -Nru iat-0.1.3/debian/changelog iat-0.1.3/debian/changelog
--- iat-0.1.3/debian/changelog  2022-12-13 06:28:02.0 +0800
+++ iat-0.1.3/debian/changelog  2022-12-13 06:09:17.0 +0800
@@ -1,3 +1,12 @@
+iat (0.1.3-7.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Bump debhelper compat to 12. (Closes: #965589)
+  * Port to DebSrc3.0 (quilt)
+  * debian/rules: use dh (Closes: #999305)
+
+ -- Ying-Chun Liu (PaulLiu)   Tue, 13 Dec 2022 06:09:17 
+0800
+
 iat (0.1.3-7) unstable; urgency=low
 
   * My email address has been changed.
diff -Nru iat-0.1.3/debian/clean iat-0.1.3/debian/clean
--- iat-0.1.3/debian/clean  1970-01-01 08:00:00.0 +0800
+++ iat-0.1.3/debian/clean  2022-12-13 06:09:17.0 +0800
@@ -0,0 +1,9 @@
+Makefile.in
+Makefile
+config.status
+config.h
+config.log
+src/Makefile.in
+src/Makefile
+src/iat
+src/*.o
diff -Nru iat-0.1.3/debian/compat iat-0.1.3/debian/compat
--- iat-0.1.3/debian/compat 2022-12-13 06:28:02.0 +0800
+++ iat-0.1.3/debian/compat 1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru iat-0.1.3/debian/control iat-0.1.3/debian/control
--- iat-0.1.3/debian/control2022-12-13 06:28:02.0 +0800
+++ iat-0.1.3/debian/control2022-12-13 06:09:17.0 +0800
@@ -1,13 +1,13 @@
 Source: iat
 Section: otherosfs
-Priority: extra
+Priority: optional
 Maintainer: Dmitry E. Oboukhov 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper-compat (= 12)
 Standards-Version: 3.7.3
 
 Package: iat
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Converts many CD-ROM image formats to iso9660
  iat (Iso9660 Analyzer Tool) is a tool for detecting the structure 
  of many types of CD-ROM image file formats, such as BIN, MDF, PDI, 
diff -Nru iat-0.1.3/debian/patches/0001_iat_c.patch 
iat-0.1.3/debian/patches/0001_iat_c.patch
--- iat-0.1.3/debian/patches/0001_iat_c.patch   1970-01-01 08:00:00.0 
+0800
+++ iat-0.1.3/debian/patches/0001_iat_c.patch   2022-12-13 06:09:17.0 
+0800
@@ -0,0 +1,717 @@
+--- iat-0.1.3.orig/src/iat.c
 iat-0.1.3/src/iat.c
+@@ -14,84 +14,99 @@
+ along with this program; if not, write to the
+ Free Software Foundation, Inc.,
+ 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
+-*/
++*/
+ 
+-/* Support Large File */
+ 
++/*
++ * Modified by Dmitry E. Oboukhov 
++ *  [+] Use 'getopt' function;
++ *  [+] Use STDOUT as output file (if not defined);
++ *  [*] Fix percent output.
++ */
++
++/* Support Large File */
+ #define _FILE_OFFSET_BITS 64
+ 
++#include 
+ #include 
+-#include 
+-#include 
+-#include 
++#include 
++#include 
++#include 
+ #include 
+ 
++
+ #define VERSION "0.1.3"
+ #define BLOCK_ISO_CD 2048
+ 
+-/* Signature for Image ISO-9660 */
+-const char ISO_9660_START[] = { 
+-  (char) 0x01,
+-  (char) 0x43,
+-  (char) 0x44,
+-  (char) 0x30,
+-  (char) 0x30,
+-  (char) 0x31,
+-  (char) 0x01,
+-  (char) 0x00
+-};
+-
+-const char ISO_9660[] = { 
+-  (char) 0x02,
+-  (char) 0x43,
+-  (char) 0x44,
+-  (char) 0x30,
+-  (char) 0x30,
+-  (char) 0x31,
+-  (char) 0x01,
+-  (char) 0x00
+-};
+-
+-const char ISO_9660_END[] = { 
+-  (char) 0xFF,
+-  (char) 0x43,
+-  (char) 0x44,
+-  (char) 0x30,
+-  (char) 0x30,
+-  (char) 0x31,
+-  (char) 0x01,
+-  (char) 0x00
+-};
+-
+-/* Signature for RAW image */
+-const char SYNC_RAW[12] = { 
+-  (char) 0x00,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0xFF,
+-  (char) 0x00
++
++#define OPTIONS_LIST   "h"
++
++
++static char *input_file=0, *output_file=0;
++
++/* Signature for Image ISO-9660 */
++const char ISO_9660_START[] = { 
++  (char) 0x01,
++  (char) 0x43,
++  (char) 0x44,
++  (char) 0x30,
++  (char) 0x30,
++  (char) 0x31,
++  (char) 0x01,
++  (char) 0x00
++};
++
++const char ISO_9660[] = { 
++  (char) 0x02,
++  (char) 0x43,
++  (char) 0x44,
++  (char) 0x30,
++  (char) 0x30,
++  (char) 0x31,
++  (char) 0x01,
++  (char) 0x00
++};
++
++const char ISO_9660_END[] = { 
++  (char) 0xFF,
++  (char) 0x43,
++  (char) 0x44,
++  (char) 0x30,
++  (char) 0x30,
++  (char) 0x31,
++  (char) 0x01,
++  (char) 0x00
++};
++
++/* Signature for RAW image */
++const char SYNC_RAW[12] = { 
++  (char) 0x00,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0xFF,
++  (char) 0x00
+ };
+ 
+ const char SYNC_RAW_2[8] = {
+-  (char) 0x00,
+-  (char) 0x00,
+-  (char) 0x08,
+-  (char) 0x00,
+-  (char) 0x00,
+-  (char) 0x00,
+-  (char) 0x08,
+-  (char) 0x00,
++  (char) 0x00,
++  (char) 0x00,
++  (char) 0x08,
++  (char) 0x00,
++  (char) 0x00,
++  (char) 0x00,
++  (char) 0x08,
++  (c

Processed: severity of 1025986 is serious

[Debian Bug Tracking System]

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

> severity 1025986 serious
Bug #1025986 [src:runawk] FTBFS: install: cannot change owner and permissions 
of ‘/<>/debian/.debhelper/generated/_source/home’: Operation not 
permitted
Ignoring request to change severity of Bug 1025986 to the same value.
> thanks
Stopping processing here.

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

Bug#1025986: FTBFS: install: cannot change owner and permissions of ‘/<>/debian/.debhelper/generated/_source/home’: Operation not permitted

[Aurelien Jarno]

Source: runawk
Version: 1.6.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

Your package fails to build with:

| dh build-arch --buildsystem=mkcmake
| dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
|dh_update_autotools_config -a -O--buildsystem=mkcmake
|dh_auto_configure -a -O--buildsystem=mkcmake
| dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
| install: cannot change owner and permissions of 
‘/<>/debian/.debhelper/generated/_source/home’: Operation not 
permitted
| dh_auto_configure: error: install -m0755 -o 0 -g 0 -d 
/<>/debian/.debhelper/generated/_source/home returned exit code 1
| make: *** [debian/rules:6: build-arch] Error 25
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

The full build log is available from:
  
https://buildd.debian.org/status/fetch.php?pkg=runawk&arch=riscv64&ver=1.6.0-2%2Bb1&stamp=1670843999&raw=0
  
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/runawk_1.6.0-2.rbuild.log.gz

Regards
Aurelien

Bug#1025985: glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found.

[Aurelien Jarno]

Source: glosstex
Version: 0.4.dfsg.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

Your package fails to build with:

|Writing index file glosstex.idx
|(/usr/share/texlive/texmf-dist/tex/latex/hypdoc/hypdoc.sty
|(/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty)
|(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
|(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
|(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
|
|! LaTeX Error: File `pdftexcmds.sty' not found.
|
|Type X to quit or  to proceed,
|or enter new name. (Default extension: sty)
|
|Enter file name: 
|! Emergency stop.
| 
| 
|l.111 \RequirePackage{pdftexcmds}[2018/09/10]
| ^^M
|No pages of output.
|Transcript written on glosstex.log.
|make[1]: *** [Makefile:83: glosstex.dvi] Error 1
|make[1]: Leaving directory '/<>'
|make: *** [debian/rules:12: install/glosstex] Error 2
|dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2

The full build log is available from:
  
https://buildd.debian.org/status/fetch.php?pkg=glosstex&arch=riscv64&ver=0.4.dfsg.1-4%2Bb1&stamp=1670830203&raw=0
  
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glosstex_0.4.dfsg.1-4.rbuild.log.gz

Regards
Aurelien

Bug#1024029: marked as done (minitube: FTBFS with mpv 0.35)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 22:07:45 +
with message-id 
and subject line Bug#1024029: fixed in minitube 3.9.3-2
has caused the Debian Bug report #1024029,
regarding minitube: FTBFS with mpv 0.35
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.)


-- 
1024029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minitube
Version: 3.9.3-1
Severity: important
Tags: sid bookworm ftbfs
X-Debbugs-Cc: sramac...@debian.org

minitube FTBFS with mpv 0.35.0:

g++ -c -pipe -g -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 
-std=gnu++1z -fno-rtti -fno-exceptions -Wall -Wextra -D_REENTRANT -fPIC 
-DAPP_VERSION=3.9.3 -DAPP_NAME=Minitube -DAPP_UNIX_NAME=minitube -DAPP_SNAPSHOT 
-DQT_NO_DEBUG_OUTPUT -DQT_USE_QSTRINGBUILDER -DQT_STRICT_ITERATORS 
-DQT_DEPRECATED_WARNINGS -DHTTP -DMEDIA_MPV -DAPP_LINUX 
-DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/minitube\" 
-DQT_NO_DYNAMIC_CAST -DQT_NO_EXCEPTIONS -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB 
-DQT_DBUS_LIB -DQT_CORE_LIB -I. -Ilib/http/src -Ilib/idle/src -Ilib/js 
-Ilib/promises -Ilib/media/src -Ilib/media/src/mpv -Isrc/qtsingleapplication 
-Isrc/yt -Isrc/yt/invidious -Isrc/yt/ytjs -Isrc -Ilocale 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtX11Extras 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtQml 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtSql 
-I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild/moc 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
build/obj/src/yt/invidious/ivlistparser.o src/yt/invidious/ivlistparser.cpp
In file included from lib/media/src/mpv/mpvwidget.cpp:1:
lib/media/src/mpv/mpvwidget.h:12:79: warning: ‘constexpr 
QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero = int 
QFlags::Private::*]’ is deprecated: Use default constructor 
instead [-Wdeprecated-declarations]
   12 | MpvWidget(mpv_handle *mpv, QWidget *parent = nullptr, 
Qt::WindowFlags f = nullptr);
  | 
  ^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1299,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/QtWidgetsDepends:3,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QtWidgets:3,
 from lib/media/src/mpv/mpvwidget.h:4:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
  123 | QT_DEPRECATED_X("Use default constructor instead") Q_DECL_CONSTEXPR 
inline QFlags(Zero) noexcept : i(0) {}
  | 
   ^~
lib/media/src/mpv/mpvwidget.cpp: In member function ‘virtual void 
MpvWidget::initializeGL()’:
lib/media/src/mpv/mpvwidget.cpp:33:74: error: too many initializers for 
‘mpv_opengl_init_params’
   33 | mpv_opengl_init_params gl_init_params{get_proc_address, this, 
nullptr};
  | 
 ^
lib/media/src/mpv/mpvwidget.cpp: At global scope:
lib/media/src/mpv/mpvwidget.cpp:8:14: warning: ‘void* get_proc_address(void*, 
const char*)’ defined but not used [-Wunused-function]
8 | static void *get_proc_address(void *ctx, const char *name) {
  |  ^~~~
make[1]: *** [Makefile:2514: build/obj/lib/media/src/mpv/mpvwidget.o] Error 1
make[1]: *** Waiting for unfinished jobs
In file included from lib/media/src/mpv/mediampv.cpp:7:
lib/media/src/mpv/mpvwidget.h:12:79: warning: ‘constexpr 
QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero = int 
QFlags::Private::*]’ is deprecated: Use default constructor 
instead [-Wdeprecated-declarations]
   12 | MpvWidget(mpv_handle *mpv, QWidget *parent = nullptr, 
Qt::WindowFlags f = nullptr);
  | 
  ^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1299,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:4,
 from lib/media/src/mpv/mediampv.h:4,
 from lib/media/src/mpv/mediampv.cpp:1:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qfl

Bug#965567: gramophone2: NMU to fix RC bugs.

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to NMU this package. The debdiff is as attachment.

I'll wait to 20th Dec and then upload to delay/10 queue.

Yours,
Paul
diff -Nru gramophone2-0.8.13a/debian/changelog 
gramophone2-0.8.13a/debian/changelog
--- gramophone2-0.8.13a/debian/changelog2020-03-28 08:24:28.0 
+0800
+++ gramophone2-0.8.13a/debian/changelog2022-12-13 05:48:33.0 
+0800
@@ -1,3 +1,17 @@
+gramophone2 (0.8.13a-3.2) unstable; urgency=low
+
+  [ Ying-Chun Liu (PaulLiu)  ]
+  * Non-maintainer upload.
+  * Bump debhelper compat to 10. (Closes: #965567)
+  [ Lukas Märdian  ]
+  * Fix FTBFS by gcc-10 (Closes: #966862)
+  [ Nicolas Sévelin-Radiguet  ]
+  * Fix FTBFS by clang (Closes: #760662)
+  [ Andreas Moog  ]
+  * Include patches from Ubuntu (Closes: #738279)
+
+ -- Ying-Chun Liu (PaulLiu)   Tue, 13 Dec 2022 05:48:33 
+0800
+
 gramophone2 (0.8.13a-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gramophone2-0.8.13a/debian/compat gramophone2-0.8.13a/debian/compat
--- gramophone2-0.8.13a/debian/compat   2020-03-28 07:55:12.0 +0800
+++ gramophone2-0.8.13a/debian/compat   2022-12-13 05:48:23.0 +0800
@@ -1 +1 @@
-5
+10
diff -Nru gramophone2-0.8.13a/debian/control gramophone2-0.8.13a/debian/control
--- gramophone2-0.8.13a/debian/control  2020-03-28 07:55:12.0 +0800
+++ gramophone2-0.8.13a/debian/control  2022-12-13 05:48:30.0 +0800
@@ -2,7 +2,7 @@
 Section: sound
 Priority: optional
 Maintainer: Francesco Namuri 
-Build-Depends: debhelper (>= 5), cdbs, bison, flex, dpkg-dev (>= 1.16.1~), 
quilt
+Build-Depends: debhelper (>= 10), cdbs, bison, flex, dpkg-dev (>= 1.16.1~), 
quilt
 Standards-Version: 3.9.5
 Homepage: http://gramophone2.sourceforge.net/
 
diff -Nru gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch 
gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch
--- gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch1970-01-01 
08:00:00.0 +0800
+++ gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch2022-12-13 
05:48:33.0 +0800
@@ -0,0 +1,14 @@
+Description: fix FTBFS with clang [-Wreturn-type]
+Author: Nicolas Sévelin-Radiguet 
+Last-Update: 2014-09-06
+--- a/midifile.c
 b/midifile.c
+@@ -156,7 +156,7 @@
+   int format, ntrks, division;
+ 
+   if ( readmt("MThd") == EOF )
+-  return;
++  return -1;
+ 
+   Mf_toberead = read32bit();
+   format = read16bit();
diff -Nru gramophone2-0.8.13a/debian/patches/fix_gcc.patch 
gramophone2-0.8.13a/debian/patches/fix_gcc.patch
--- gramophone2-0.8.13a/debian/patches/fix_gcc.patch2020-03-28 
08:23:54.0 +0800
+++ gramophone2-0.8.13a/debian/patches/fix_gcc.patch1970-01-01 
08:00:00.0 +0800
@@ -1,27 +0,0 @@
-Description: Fix FTBFS with GCC
-
-Author: Sudip Mukherjee 
-

-
 gramophone2-0.8.13a.orig/Makefile
-+++ gramophone2-0.8.13a/Makefile
-@@ -1,7 +1,8 @@
- CC=gcc
- #CFLAGS+=-O2
- #Decomment this line if you use Linux:
--CFLAGS+=-O2 -lm
-+CFLAGS+=-O2
-+LIBS+=-lm
- 
- DESTDIR=/usr/local
- 
-@@ -9,7 +10,7 @@ default:  GRAMophone.tab.c
-   $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) -o gramophone2 
GRAMophone.c\
-   grammyVM.c init.c midicode.c\
-   midifile.c expcode.c debug.c errors.c\
--  hash.c GRAMophone.tab.c
-+  hash.c GRAMophone.tab.c $(LIBS)
- 
- GRAMophone.tab.c: lex.yy.c
-   bison -d GRAMophone.y
diff -Nru gramophone2-0.8.13a/debian/patches/Makefile.diff 
gramophone2-0.8.13a/debian/patches/Makefile.diff
--- gramophone2-0.8.13a/debian/patches/Makefile.diff2020-03-28 
07:55:12.0 +0800
+++ gramophone2-0.8.13a/debian/patches/Makefile.diff2022-12-13 
05:48:33.0 +0800
@@ -1,6 +1,26 @@
 a/Makefile
-+++ b/Makefile
-@@ -6,7 +6,7 @@
+Description: The included Makefile for unix has some problems:
+ It adds -lm to the CFLAGS. -lm is a linker option and as such
+ has no place in CFLAGS (which are used for compiler flags).
+ Due to this, -lm appears on the command line way before any
+ object files. This leads to it being discarded when the linker
+ flag --as-needed is set. An example failure can be observed under
+ Ubuntu: /«PKGBUILDDIR»/grammyVM.c:1498: undefined reference to `log10'
+Forwarded: yes, 
https://sourceforge.net/p/gramophone2/bugs/3/attachment/Makefile
+Bug: https://sourceforge.net/p/gramophone2/bugs/3/
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1277954
+
+Index: gramophone2-0.8.13a/Makefile
+===
+--- gramophone2-0.8.13a.orig/Makefile  2014-02-08 21:45:36.087812116 +0100
 gramophone2-0.8.13a/Makefile   2014-02-08 21:46:00.875811707 +0100
+@@ -1,15 +1,16 @@
+ CC=gcc
+ #CFLAGS+=-O2
+ #Decomment this line if you use Linux:
+-CFLAGS+=-O2 -lm
++CFLAGS+=-O2
++LDLIBS+=-lm
+ 
  DESTDIR=/usr/local
  
  default:  GRAMophone.tab.c
@@ -8,4 +28,8 @@
 +

Processed: fixed 1002622 in 3.6.0-3+deb11u1

[Debian Bug Tracking System]

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

> fixed 1002622 3.6.0-3+deb11u1
Bug #1002622 {Done: Georg Faerber } [schleuder] schleuder: 
ActiveRecord >= 6.0 changes boolean serialization, makes existing mailing lists 
fail
Marked as fixed in versions schleuder/3.6.0-3+deb11u1.
> thanks
Stopping processing here.

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

Bug#1025957: libcap-dev is wrongly marked Multi-Arch: same

[Christian Kastner]

Hi Helmut,

you're quick!

On 2022-12-12 15:17, Helmut Grohne wrote:
> Package: libcap-dev
> Version: 1:2.63-1
> Severity: serious
> Jutsification: fails to install with an unpack errror
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Coinstalling libcap-dev fails:
> 
> | Unpacking libcap-dev:amd64 (1:2.63-1) ...
> | dpkg: error processing archive 
> /var/cache/apt/archives/libcap-dev_1%3a2.63-1_amd64.deb (--unpack):
> |  trying to overwrite shared '/usr/lib/libcap2/tests/cap_test', which is 
> different from other instances of package libcap-dev:amd64
> | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> | Errors were encountered while processing:
> |  /var/cache/apt/archives/libcap-dev_1%3a2.63-1_amd64.deb
> | E: Sub-process /usr/bin/dpkg returned an error code (1)

I noticed this myself only too late -- lintian flagged all of these
errors, but I had a bug in my workflow, and only source package checks
were performed.

> I suppose that the test binaries were recently added to the -dev
> package. There are basically three ways of dealing with this:
> 
> a) Drop Multi-Arch: same. This is a little inconvenient for some users,
>but is really something we can do. Most cross builds will continue
>working in the absence of Multi-Arch: same.
> 
> b) Move those test binaries to architecture-dependent paths.

This is what I did whilst preparing the 2.66 upload. I was going to wait
for 2.63 to migrate, but might as well just push that now.

> c) Move those test binaries to a different package. An obvious candidate
>would be a new package libcap-tests. Prior art: dbus-tests. If you
>do, it would be awesome to support the noinsttest build profile.

Thanks for the prior art on that, I was unsure how to handle that. It
definitely feels cleaner than shipping this with libcap-dev. I'll wait
for 2.66 to migrate to testing first.

Best,
Christian

Bug#1025980: texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex

[Hilmar Preuße]

Control: reassign -1 latexml

Am 12.12.2022 um 21:56 teilte Paul Gevers mit:

Hi Paul,


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



The issue is in latexml. It is known in upstream and the (soon to be
relased) new version has the fix.

H.
--
sigfault

Processed: Bug#1025980: texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 latexml
Bug #1025980 [src:texlive-extra, src:latexml] texlive-extra breaks latexml 
autopkgtest: Couldn't convert t/structure/glossary.tex
Bug reassigned from package 'src:texlive-extra, src:latexml' to 'latexml'.
No longer marked as found in versions latexml/0.8.6-5 and 
texlive-extra/2022.20221123-1.
Ignoring request to alter fixed versions of bug #1025980 to the same values 
previously set

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

Processed: ariba status in the vcs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - pending
Bug #1021675 [src:ariba] ariba: autopkgtest regression and ftbfs with samtools 
1.16
Bug #1022508 [src:ariba] ariba: ftbfs with samtools 1.16
Removed tag(s) pending.
Removed tag(s) pending.

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

Bug#1021675: ariba status in the vcs

[Étienne Mollier]

Control: tags -1 - pending

Hi, removing the pending tag, as there are still some test
failures which seem related to bowtie2 this time.  Given the
output, results look off by two.  I don't know for sure if this
is significant or might just need refresh as well.  See below:

_ TestMapping.test_run_bowtie2 
_
self = 
def test_run_bowtie2(self):
'''Test run_bowtie2 unsorted'''
self.maxDiff = None
ref = os.path.join(data_dir, 'mapping_test_bowtie2_ref.fa')
reads1 = os.path.join(data_dir, 
'mapping_test_bowtie2_reads_1.fq')
reads2 = os.path.join(data_dir, 
'mapping_test_bowtie2_reads_2.fq')
out_prefix = 'tmp.out.bowtie2'
mapping.run_bowtie2(
reads1,
reads2,
ref,
out_prefix,
bowtie2=extern_progs.exe('bowtie2'),
bowtie2_version=extern_progs.version('bowtie2'),
)
expected = get_sam_columns(os.path.join(data_dir, 
'mapping_test_bowtie2_unsorted.bam'))
got = get_sam_columns(out_prefix + '.bam')
>   self.assertListEqual(expected, got)
E   AssertionError: Lists differ: [('1'[508 chars]5', 99, 'ref', 0, 
[(4, 2), (0, 23)], 'CCTCCACA[346 chars]AT')] != [('1'[508 chars]5', 97, 'ref', 
0, [(4, 2), (0, 23)], 'CCTCCACA[346 chars]AT')]
E   
E   First differing element 8:
E   ('5', 99, 'ref', 0, [(4, 2), (0, 23)], 
'CCTCCACAGGATGGTGGTATACCTG')
E   ('5', 97, 'ref', 0, [(4, 2), (0, 23)], 
'CCTCCACAGGATGGTGGTATACCTG')
E   
E [('1', 99, 'ref', 0, [(4, 5), (0, 20)], 
'AGCCCTCCACAGGATGGTGGTATAC'),
E  ('1', 147, 'ref', 30, [(0, 25)], 
'AGGATACAGATCTTGTGGGAAAGGT'),
E  ('2', 99, 'ref', 124, [(0, 25)], 
'TAATGTTCTTAGGGCTTACCATAGA'),
E  ('2', 147, 'ref', 170, [(0, 20), (4, 5)], 
'TCCACCTTAGCTAAGCGCAGACTCG'),
E  ('3', 73, 'ref', 86, [(0, 25)], 'TCGGGTCTGTACAAGGACGGATGGT'),
E  ('3', 133, None, 86, [], 'CGTACTGACTGACTGACGTACTGCA'),
E  ('4', 99, 'ref', 55, [(0, 25)], 'CCGCCGGGAAGTCCTTCTGTCGTGC'),
E  ('4', 147, 'ref', 136, [(0, 25)], 
'GGCTTACCATAGAGGTACACT'),
E   -  ('5', 99, 'ref', 0, [(4, 2), (0, 23)], 
'CCTCCACAGGATGGTGGTATACCTG'),
E   ? ^
E   
E   +  ('5', 97, 'ref', 0, [(4, 2), (0, 23)], 
'CCTCCACAGGATGGTGGTATACCTG'),
E   ? ^
E   
E   -  ('5', 147, 'ref', 166, [(0, 24), (4, 1)], 
'TTCATCCACCTTAGCTAAGCGCAGA'),
E   ?  ^
E   
E   +  ('5', 145, 'ref', 166, [(0, 24), (4, 1)], 
'TTCATCCACCTTAGCTAAGCGCAGA'),
E   ?  ^
E   
E  ('6', 77, None, -1, [], 'CAGTTGCATGACGTCATGCAGTCAT'),
E  ('6', 141, None, -1, [], 'AATGAGTATGATGAGTAATGGTATG'),
E   -  ('7', 99, 'ref', 56, [(4, 1), (0, 23), (4, 1)], 
'ACGCCGGGAAGTCCTTCTGTCGTGT'),
E   ? ^
E   
E   +  ('7', 97, 'ref', 56, [(4, 1), (0, 23), (4, 1)], 
'ACGCCGGGAAGTCCTTCTGTCGTGT'),
E   ? ^
E   
E   -  ('7', 147, 'ref', 136, [(0, 24), (4, 1)], 
'GGCTTACCATAGAGGTACACTAAAT')]
E   ?  ^
E   
E   +  ('7', 145, 'ref', 136, [(0, 24), (4, 1)], 
'GGCTTACCATAGAGGTACACTAAAT')]
E   ?  ^
ariba/tests/mapping_test.py:62: AssertionError
- Captured stderr call 
-
[E::idx_find_and_load] Could not retrieve index file for 
'/builds/med-team/ariba/debian/output/source_dir/.pybuild/cpython3_3.10_ariba/build/ariba/tests/data/mapping_test_bowtie2_unsorted.bam'
[E::idx_find_and_load] Could not retrieve index file for 
'tmp.out.bowtie2.bam'
 TestMapping.test_run_bowtie2_and_sort 
_
self = 
def test_run_bowtie2_and_sort(self):
'''Test run_bowtie2 sorted'''
ref = os.path.join(data_dir, 'mapping_test_bowtie2_ref.fa')
reads1 = os.path.join(data_dir, 
'mapping_test_bowtie2_reads_1.fq')
reads2 = os.path.join(data_dir, 
'mapping_test_bowtie2_reads_2.fq')
out_prefix = 'tmp.out.bowtie2'
mapping.run_bowtie2(
reads1,
reads2,
ref,
out_prefix,
sort=True,
bowtie2=extern_progs.exe('bowtie2'),
bowtie2_version=extern_progs.version('bowtie2'),
)
expected = get_sam_columns(os.path.join(data_dir, 
'mapping_test_

Bug#1025954: marked as done (u-boot-menu: renders system unbootable with u-boot 21.10)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 21:50:40 +
with message-id 
and subject line Bug#1025954: fixed in u-boot-menu 4.2.1
has caused the Debian Bug report #1025954,
regarding u-boot-menu: renders system unbootable with u-boot 21.10
to be marked as done.

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

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


-- 
1025954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: u-boot-menu
Version: 4.2.0
Severity: important
Tags: patch
X-Debbugs-Cc: aferra...@debian.org

Dear Maintainer,

Using u-boot 21.10 (which does not have support for KASLR), the generated
extlinux.conf makes the system unbootable.
This is most likely a bug in u-boot, causing it to ignore any unknown command
*and all the following ones*:

  Retrieving file: /extlinux/extlinux.conf
  843 bytes read in 17 ms (47.9 KiB/s)
  Ignoring unknown command: kaslrseed
  Ignoring unknown command: append
  Ignoring unknown command: kaslrseed
  Ignoring unknown command: append

Attached is a patch working around this issue in u-boot-menu.

Thanks,
Arnaud


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

Kernel: Linux 6.0.0-5-amd64 (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

Versions of packages u-boot-menu depends on:
ii  linux-base  4.9

Versions of packages u-boot-menu recommends:
ii  rsync  3.2.6-4+b1

Versions of packages u-boot-menu suggests:
pn  flash-kernel  
>From 3cd399d3c853f452711b6e5b37098b89e1633c51 Mon Sep 17 00:00:00 2001
From: Arnaud Ferraris 
Date: Mon, 12 Dec 2022 14:59:44 +0100
Subject: [PATCH] u-boot-update: put `kaslrseed` last

When using a version of u-boot without KASLR support (21.10 in this
case), having this command set makes all following lines to be ignored,
even though they contain valid commands:

  Retrieving file: /extlinux/extlinux.conf
  843 bytes read in 17 ms (47.9 KiB/s)
  Ignoring unknown command: kaslrseed
  Ignoring unknown command: append
  Ignoring unknown command: kaslrseed
  Ignoring unknown command: append

Ensuring `kaslrseed` is the last command is enough this work around this
`u-boot` bug.
---
 u-boot-update | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/u-boot-update b/u-boot-update
index effd304..f42cacb 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -189,8 +189,8 @@ label l${_NUMBER}
${_INITRD}
${_FDT}
${_FDTOVERLAYS}
-   kaslrseed
-   append ${U_BOOT_ROOT} ${U_BOOT_PARAMETERS}"
+   append ${U_BOOT_ROOT} ${U_BOOT_PARAMETERS}
+   kaslrseed"
 
fi
 
-- 
2.35.1

--- End Message ---
--- Begin Message ---
Source: u-boot-menu
Source-Version: 4.2.1
Done: Vagrant Cascadian 

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated u-boot-menu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 13:26:47 -0800
Source: u-boot-menu
Architecture: source
Version: 4.2.1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Vagrant Cascadian 
Closes: 1025954
Changes:
 u-boot-menu (4.2.1) unstable; urgency=medium
 .
   * Revert "add kalsrseed support" (Closes: #1025954)
Checksums-Sha1:
 9fb47548ff52247e882851be155b919625394775 1055 u-boot-menu_4.2.1.dsc
 83c3e630847918eb5938aebd921f842cef221960 14248 u-boot-menu_4.2.1.tar.xz
 9cd5f60a35be098665e95400f2bf85ba9f3faeea 5426 u-boot-menu_4.2.1_arm64.buildinfo
Checksums-Sha256:
 340174a373579a45704b4a04c731b02cb1e5dff7bff348296b1f413cb512a246 1055 
u-boot-menu_4.2.1.dsc
 2fe45b20bfd10a836e7ca5817aba95995255d9fc50fa7ee6e0ddd3b2c89aa502 14248 
u-boot-menu_4.2.1.tar.xz
 f451a07cf6c65aa634bf33b112a616694d5ca596a7d001f6ae582c

Bug#1025954: marked as pending in u-boot-menu

[Vagrant Cascadian]

Control: tag -1 pending

Hello,

Bug #1025954 in u-boot-menu 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/debian/u-boot-menu/-/commit/ce91ec282087632dea7b1d5be444bf9aac3cfd6f


Revert "add kalsrseed support" (Closes: #1025954)

This reverts commit ff483d04dc558e7339f7904205564dcfd889db79.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025954

Processed: Bug#1025954 marked as pending in u-boot-menu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025954 {Done: Vagrant Cascadian } [u-boot-menu] 
u-boot-menu: renders system unbootable with u-boot 21.10
Added tag(s) pending.

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

Processed (with 1 error): Re: texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex

[Debian Bug Tracking System]

Processing control commands:

> reasssign -1 latexml
Unknown command or malformed arguments to command.

> forwarded -1 https://github.com/brucemiller/LaTeXML/issues/1985
Bug #1025980 [src:texlive-extra, src:latexml] texlive-extra breaks latexml 
autopkgtest: Couldn't convert t/structure/glossary.tex
Set Bug forwarded-to-address to 
'https://github.com/brucemiller/LaTeXML/issues/1985'.
> tags -1 + fixed-upstream pending
Bug #1025980 [src:texlive-extra, src:latexml] texlive-extra breaks latexml 
autopkgtest: Couldn't convert t/structure/glossary.tex
Added tag(s) fixed-upstream and pending.

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

Bug#1025980: texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex

[Hilmar Preuße]

Control: reasssign -1 latexml
Control: forwarded -1 https://github.com/brucemiller/LaTeXML/issues/1985
Control: tags -1 + fixed-upstream pending

Am 12.12.2022 um 21:56 teilte Paul Gevers mit:

Hi Paul,


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



The issue is in latexml. It is known in upstream and the (soon to be
relased) new version has the fix.

H.
--
sigfault

Bug#965484: dbench: NMU to fix RC bugs.

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to NMU to fix #965484 and #999156

The debdiff is as attachment.

I'll wait until 20th Dec and upload to delay/10 queue.

Yours,
Paul
diff -Nru dbench-4.0/dbench.1 dbench-4.0/dbench.1
--- dbench-4.0/dbench.1 2022-12-13 05:40:37.0 +0800
+++ dbench-4.0/dbench.1 2008-02-18 08:49:35.0 +0800
@@ -2,7 +2,7 @@
 .\" First parameter, NAME, should be all caps
 .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
 .\" other parameters are allowed: see man(7), man(1)
-.TH DBENCH 1 "June 18, 2005"
+.TH DBENCH 1 "October 15, 2001"
 .\" Please adjust this date whenever revising the manpage.
 .\"
 .\" Some roff macros, for reference:
@@ -43,17 +43,15 @@
 and WindowsNT.
 .br
 Given the requirements of running netbench (60 and 150 Windows PCs all
-on switched fast ethernet and a really grunty server, and some way to
-nurse all those machines along so they will run a very fussy benchmark
-suite without crashing), these programs were written to open up
+on switched fast ethernet and a really grunty server, and a to open up
 netbench to the masses.
 .br
 Both \fBdbench\fP and \fBtbench\fP read a load description file called
-client.txt that was derived from a network sniffer dump of a real
-netbench run. client.txt is about 4MB and describes the 90 thousand
-operations that a netbench client does in a typical netbench run. They
-parse client.txt and use it to produce the same load without having to
-buy a huge lab.
+client.txt that was derived from a capture of a real
+netbench run. client.txt is about 25MB and describes the
+500 thousand operations that a netbench client does in a typical
+netbench run. They parse client.txt and use it to produce
+the same load without having to buy a huge lab.
 .br
 dbench produces only the filesystem load. It does all the same IO
 calls that the smbd server in Samba would produce when confronted with
@@ -92,6 +90,10 @@
 should be invoked on that server before invoking \fBtbench\fP.
 \fBtbench\fP can also take the following options:
 .TP
+.B \-c loadfile
+Use this as the full path name of the client.txt file (the default is
+/usr/share/dbench/client.txt).
+.TP
 .B \-T option[,...]
 This sets the socket options for the connection to the server.  The
 options are a comma-separated list of one or more of the following:
@@ -112,13 +114,12 @@
 for details about these options.
 .br
 The \fBtbench_srv\fP can only take one option:
-.B \-T option[,...]
+.B \-t option[,...]
 as documented above.
 .SH SEE ALSO
 .I /usr/share/doc/dbench/README
 contains the original README by Andrew Tridgell which accompanies the
 dbench source.
 .SH AUTHOR
-This manual page was originally written by Paul Russell 
,
-for the Debian GNU/Linux system (but may be used by others). Modified and 
updated by
-Mattias Nordstrom .
+This manual page was written by Paul Russell ,
+for the Debian GNU/Linux system (but may be used by others).
diff -Nru dbench-4.0/debian/changelog dbench-4.0/debian/changelog
--- dbench-4.0/debian/changelog 2022-12-13 05:40:37.0 +0800
+++ dbench-4.0/debian/changelog 2022-12-12 22:43:32.0 +0800
@@ -1,3 +1,12 @@
+dbench (4.0-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Bump debhelper compat to 12. (Closes: #965484)
+  * debian/rules: use dh. (Closes: #999156)
+  * Port to DebSrc3.0 (quilt)
+
+ -- Ying-Chun Liu (PaulLiu)   Mon, 12 Dec 2022 22:43:32 
+0800
+
 dbench (4.0-2) unstable; urgency=low
 
   * Added build-depends on autoconf, fixes FTBFS (closes: #524415)
diff -Nru dbench-4.0/debian/clean dbench-4.0/debian/clean
--- dbench-4.0/debian/clean 1970-01-01 08:00:00.0 +0800
+++ dbench-4.0/debian/clean 2022-12-12 22:43:32.0 +0800
@@ -0,0 +1,4 @@
+Makefile
+config.h
+config.log
+config.status
diff -Nru dbench-4.0/debian/compat dbench-4.0/debian/compat
--- dbench-4.0/debian/compat2022-12-13 05:40:37.0 +0800
+++ dbench-4.0/debian/compat1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru dbench-4.0/debian/control dbench-4.0/debian/control
--- dbench-4.0/debian/control   2022-12-13 05:40:37.0 +0800
+++ dbench-4.0/debian/control   2022-12-12 22:43:32.0 +0800
@@ -1,13 +1,13 @@
 Source: dbench
 Section: utils
-Priority: extra
+Priority: optional
 Maintainer: Mattias Nordstrom 
-Build-Depends: debhelper (>> 5.0.0), autoconf, libpopt-dev
+Build-Depends: debhelper-compat (= 12), autoconf, libpopt-dev
 Standards-Version: 3.8.1.0
 
 Package: dbench
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Homepage: http://samba.org/ftp/tridge/dbench/
 Description: The dbench (disk) and tbench (TCP) benchmarks
  dbench and tbench simulate the load of the netbench "industry
diff -Nru dbench-4.0/debian/dbench.manpages dbench-4.0/debian/dbench.manpages
--- dbench-4.0/debian/dbench.manpages   1970-01-01 08:00:00.0 +0800
+++ dbench-4.0/debian/dbench.manpages   2022-12-12 22:43:32.0 +0800
@@ -0,0 +1 @@
+dbench.1
diff -Nru dbench-4.

Bug#1025957: marked as done (libcap-dev is wrongly marked Multi-Arch: same)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 21:35:27 +
with message-id 
and subject line Bug#1025957: fixed in libcap2 1:2.66-1
has caused the Debian Bug report #1025957,
regarding libcap-dev is wrongly marked Multi-Arch: same
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.)


-- 
1025957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcap-dev
Version: 1:2.63-1
Severity: serious
Jutsification: fails to install with an unpack errror
User: helm...@debian.org
Usertags: rebootstrap

Coinstalling libcap-dev fails:

| Unpacking libcap-dev:amd64 (1:2.63-1) ...
| dpkg: error processing archive 
/var/cache/apt/archives/libcap-dev_1%3a2.63-1_amd64.deb (--unpack):
|  trying to overwrite shared '/usr/lib/libcap2/tests/cap_test', which is 
different from other instances of package libcap-dev:amd64
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  /var/cache/apt/archives/libcap-dev_1%3a2.63-1_amd64.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)

I suppose that the test binaries were recently added to the -dev
package. There are basically three ways of dealing with this:

a) Drop Multi-Arch: same. This is a little inconvenient for some users,
   but is really something we can do. Most cross builds will continue
   working in the absence of Multi-Arch: same.

b) Move those test binaries to architecture-dependent paths.

c) Move those test binaries to a different package. An obvious candidate
   would be a new package libcap-tests. Prior art: dbus-tests. If you
   do, it would be awesome to support the noinsttest build profile.

We can also do option a) as a stop-gap measure and move to a different
solution later.

Helmut
--- End Message ---
--- Begin Message ---
Source: libcap2
Source-Version: 1:2.66-1
Done: Christian Kastner 

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

Debian distribution maintenance software
pp.
Christian Kastner  (supplier of updated libcap2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Dec 2022 15:49:58 +0100
Source: libcap2
Architecture: source
Version: 1:2.66-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Kastner 
Changed-By: Christian Kastner 
Closes: 1024918 1025957
Changes:
 libcap2 (1:2.66-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   [ Helmut Grohne ]
   * Support the noudeb build profile (Closes: #1024918)
 .
   [ Christian Kastner ]
   * Install tests in arch-specific directory (Closes: #1025957)
   * Rework autopkgtests
   * Add chrpath to Build-Depends, for removing RPATH from test binaries
   * Fix existing lintian override pattern
   * Add lintian overrides for static test binaries
   * Add missing Build-Depends-Package to symbols file
   * Move pam_cap manpages from libcap2-bin to libpam-cap
   * Add lintian override for pam_cap man page
   * Bump d/copyright
Checksums-Sha1:
 4a628d6c70d7c3aca59b5d945483cda9f34375fa 2204 libcap2_2.66-1.dsc
 d440e60686bd542e2a6481986c63ee8de625563e 181592 libcap2_2.66.orig.tar.xz
 33b489cbb872aa44a6765ea8ccddb24fde25a7d8 19976 libcap2_2.66-1.debian.tar.xz
 81fb943e72fc4a1835d96a1e82a6955518cbae2f 5828 libcap2_2.66-1_source.buildinfo
Checksums-Sha256:
 fa17fd46fe4459802e62493c4af29ee9a870cff89a59c796288b64504ffb0b17 2204 
libcap2_2.66-1.dsc
 15c40ededb3003d70a283fe587a36b7d19c8b3b554e33f86129c059a4bb466b2 181592 
libcap2_2.66.orig.tar.xz
 5aae2e96a32c6cb68b562e3baf8f9fe35f330fee3824d0c675b862ea97041313 19976 
libcap2_2.66-1.debian.tar.xz
 3b4813f11dead36a66937921d3dbc4ed509a1bb0eab56eb222d9aff9f7c34f0b 5828 
libcap2_2.66-1_source.buildinfo
Files:
 cc7b8a29663c6e079460fc1103b4044a 2204 libs optional libcap2_2.66-1.dsc
 00afd6e13bc94b2543b1a70770bdb41f 181592 libs optional libcap2_2.66.orig.tar.xz
 70f0d86e6645238690d566689c0c891c 19976 libs optional 
libcap2_2.66-1.debian.tar.xz
 6c7b6a6053cbb61f5b24f5c67c907bd2 5828 libs optional 
libcap2_2.66-1_source.buildinfo

-

Processed: block 1024101 with 1025777

[Debian Bug Tracking System]

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

> block 1024101 with 1025777
Bug #1024101 {Done: Christoph Berg } [src:js8call] js8call: 
QCustomPlot transition
1024101 was not blocked by any bugs.
1024101 was not blocking any bugs.
Added blocking bug(s) of 1024101: 1025777
> thanks
Stopping processing here.

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

Bug#1025982: python-mitogen: autopkgtest needs update for new version of ansible-core

[Paul Gevers]

Source: python-mitogen
Version: 0.3.3-7
Severity: serious
X-Debbugs-CC: ansible-c...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ansible-core

Dear maintainer(s),

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


   passfail
ansible-core   from testing2.14.0-1
python-mitogen from testing0.3.3-7
all others from testingfrom testing

I copied some of the output at the bottom of this report. Your package 
has a hard requirement on older version of either ansible-core or 
ansible than the current ones.


Currently this regression is blocking the migration of ansible-core to 
testing [1]. Of course, ansible-core shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in ansible-core was intended and your package needs to update to 
the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from ansible-core should 
really add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


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=ansible-core

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

The following packages have unmet dependencies:
 ansible-mitogen : Depends: ansible-core (< 2.14) but 2.14.0-1 is to be 
installed or
ansible (< 6) but it is not going to be 
installed


OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-mitogen: autopkgtest needs update for new version of ansible-core

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ansible-core
Bug #1025982 [src:python-mitogen] python-mitogen: autopkgtest needs update for 
new version of ansible-core
Added indication that 1025982 affects src:ansible-core

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

Bug#1025981: ansible-core breaks ansible-lint autopkgtest: Ansible requires the locale encoding to be UTF-8; Detected None.

[Paul Gevers]

Source: ansible-core, ansible-lint
Control: found -1 ansible-core/2.14.0-1
Control: found -1 ansible-lint/6.3.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
ansible-core   from testing2.14.0-1
ansible-lint   from testing6.3.0-2
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=ansible-core

https://ci.debian.net/data/autopkgtest/testing/amd64/a/ansible-lint/29251798/log.gz

ERROR: Ansible requires the locale encoding to be UTF-8; Detected None.
Traceback (most recent call last):
  File "/usr/bin/ansible-lint", line 8, in 
sys.exit(_run_cli_entrypoint())
  File "/usr/lib/python3/dist-packages/ansiblelint/__main__.py", line 
252, in _run_cli_entrypoint

sys.exit(main(sys.argv))
  File "/usr/lib/python3/dist-packages/ansiblelint/__main__.py", line 
165, in main

app = get_app(offline=options.offline)
  File "/usr/lib/python3/dist-packages/ansiblelint/app.py", line 247, 
in get_app

app = App(options=default_options)
  File "/usr/lib/python3/dist-packages/ansiblelint/app.py", line 57, in 
__init__

self.runtime = Runtime(isolated=True)
  File "/usr/lib/python3/dist-packages/ansible_compat/runtime.py", line 
96, in __init__

self.config = AnsibleConfig()
  File "/usr/lib/python3/dist-packages/ansible_compat/config.py", line 
422, in __init__

config_dump = subprocess.check_output(
  File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ansible-config', 'dump']' 
returned non-zero exit status 1.

0a1,992


OpenPGP_signature
Description: OpenPGP digital signature

Processed: ansible-core breaks ansible-lint autopkgtest: Ansible requires the locale encoding to be UTF-8; Detected None.

[Debian Bug Tracking System]

Processing control commands:

> found -1 ansible-core/2.14.0-1
Bug #1025981 [src:ansible-core, src:ansible-lint] ansible-core breaks 
ansible-lint autopkgtest: Ansible requires the locale encoding to be UTF-8; 
Detected None.
Marked as found in versions ansible-core/2.14.0-1.
> found -1 ansible-lint/6.3.0-2
Bug #1025981 [src:ansible-core, src:ansible-lint] ansible-core breaks 
ansible-lint autopkgtest: Ansible requires the locale encoding to be UTF-8; 
Detected None.
Marked as found in versions ansible-lint/6.3.0-2.

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

Processed: block 1024047 with 1025513

[Debian Bug Tracking System]

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

> block 1024047 with 1025513
Bug #1024047 [src:python-line-profiler] python-line-profiler FTBFS with Python 
3.11 as supported version
1024047 was not blocked by any bugs.
1024047 was not blocking any bugs.
Added blocking bug(s) of 1024047: 1025513
> thanks
Stopping processing here.

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

Processed: texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex

[Debian Bug Tracking System]

Processing control commands:

> found -1 texlive-extra/2022.20221123-1
Bug #1025980 [src:texlive-extra, src:latexml] texlive-extra breaks latexml 
autopkgtest: Couldn't convert t/structure/glossary.tex
Marked as found in versions texlive-extra/2022.20221123-1.
> found -1 latexml/0.8.6-5
Bug #1025980 [src:texlive-extra, src:latexml] texlive-extra breaks latexml 
autopkgtest: Couldn't convert t/structure/glossary.tex
Marked as found in versions latexml/0.8.6-5.

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

Bug#1025980: texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex

[Paul Gevers]

Source: texlive-extra, latexml
Control: found -1 texlive-extra/2022.20221123-1
Control: found -1 latexml/0.8.6-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
texlive-extra  from testing2022.20221123-1
latexmlfrom testing0.8.6-5
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=texlive-extra

https://ci.debian.net/data/autopkgtest/testing/amd64/l/latexml/29254215/log.gz

PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" 
"-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 
'blib/lib', 'blib/arch')" t/*.t

# #   LaTeXML version 0.8.6
#   XML::LibXML 2.0134; libxml2 20914
#   XML::LibXSLT 2.002000; libxslt 10135
#   TeX 3.141592653 (TeX Live 2022/Debian)
t/000_test_context.t .. 1..1
ok 1 - Test Context
ok
t/002_unit_findfile.t . ok 1 - use LaTeXML;
ok 2 - use LaTeXML::Core::State;
ok 3 - use LaTeXML::Core::Stomach;
ok 4 - use LaTeXML::Common::Model;
ok 5 - use LaTeXML::Global;
ok 6 - use LaTeXML::Package;
ok 7 - use LaTeXML::Common::Error;
ok 8 - amsmath.sty did not resolve as amsmath.sty.ltxml
ok 9 - amsmath2.sty did not resolve as amsmath.sty.ltxml
ok 10 - amsmath3-1.sty did not resolve as amsmath.sty.ltxml
ok 11 - amsmathv2.sty did not resolve as amsmath.sty.ltxml
ok 12 - amsmath_v2.sty did not resolve as amsmath.sty.ltxml
ok 13 - amsmath2019.sty did not resolve as amsmath.sty.ltxml
ok 14 - amsmath_v2019.sty did not resolve as amsmath.sty.ltxml
ok 15 - amsmath_2019.sty did not resolve as amsmath.sty.ltxml
ok 16 - amsmath_05_2019.sty did not resolve as amsmath.sty.ltxml
ok 17 - amsmath052019.sty did not resolve as amsmath.sty.ltxml
ok 18 - amsmath_052019.sty did not resolve as amsmath.sty.ltxml
ok 19 - amsmath05_2019.sty did not resolve as amsmath.sty.ltxml
ok 20 - amsmath05-2019.sty did not resolve as amsmath.sty.ltxml
ok 21 - amsmath_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 22 - amsmath2_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 23 - amsmath2019_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 24 - amsmath_05-2019_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 25 - amsmath_05-2019_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 26 - amsmath95.sty did not resolve as amsmath.sty.ltxml
ok 27 - amsmath_conference.sty did not resolve as amsmath.sty.ltxml
ok 28 - amsmath2019_conference.sty did not resolve as amsmath.sty.ltxml
ok 29 - amsmath_v2-workshop.sty did not resolve as amsmath.sty.ltxml
1..29
ok
t/00_unittest.t ... ok 1 - use LaTeXML;
ok 2 - use LaTeXML::Package;
ok 3 - Make Token (x)
ok 4 - Got correct token (x)
ok 5 - Make Token (x)
ok 6 - Got correct deref (x)
ok 7 - Make Token (z)
ok 8 - Got correct token (z)
ok 9 - Make Tokens (x)
ok 10 - Got correct token (x)
ok 11 - Make Tokens from Token's (x,x,x)
ok 12 - Got correct tokens
ok 13 - Make Tokens from Tokens (x,x,x)
ok 14 - Make Token (z)
ok 15 - Got correct deref (x,x,x)
ok 16 - Make Tokens from Token's (z,z,z)
ok 17 - Got correct tokens (z,z,z)
ok 18 - Make Tokens from Tokens (x,x,x)
ok 19 - Got correct tokens (x,x,x)
ok 20 - Make balanced tokens
ok 21 - Check is balanced
ok 22 - Make unbalanced tokens
ok 23 - Check is not balancde
ok 24 - substitute tokens w/o params
ok 25 - Got correct (non)substitution
ok 26 - make tokens w/ params
ok 27 - subsitute tokens w/params
ok 28 - Got correct substitution
ok 29 - Strip no braces
ok 30 - Strip one brace
ok 31 - Strip spaces
ok 32 - Strip brace & spaces
ok 33 - Strip spaces, not inner space
ok 34 - Strip outer braces
ok 35 - Don't strip unbalanced braces
ok 36 - strip outermost braces
1..36
ok
t/05_tokenize.t ... 1..17
ok 1 - use LaTeXML::Core;
ok 2 - t/tokenize/alltt
ok 3 # skip No file t/tokenize/badchars.xml
ok 4 - t/tokenize/comment
ok 5 - t/tokenize/equality
ok 6 - t/tokenize/file_read
ok 7 - t/tokenize/hashes
ok 8 - t/tokenize/ligatures
ok 9 - t/tokenize/mathtokens
ok 10 # skip No file t/tokenize/newlines-input.xml
ok 11 - t/tokenize/newlines
ok 12 - t/tokenize/percent
ok 13 # skip No file t/tokenize/snippet.xml
ok 14 - t/tokenize/trailingspaces
ok 15 - t/tokenize/url
ok 16 - t/tokenize/verb
ok 17 - t/tokenize/verbata
ok
t/10

Bug#1025979: puppet-beaker: autopkgtest needs update for new version of ruby-net-scp: Could not find 'net-scp' (~> 3.0)

[Paul Gevers]

Source: puppet-beaker
Version: 4.30.0-2
Severity: serious
X-Debbugs-CC: ruby-net-...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-net-scp

Dear maintainer(s),

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


   passfail
ruby-net-scp   from testing4.0.0-1
puppet-beaker  from testing4.30.0-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of ruby-net-scp to 
testing [1]. Of course, ruby-net-scp shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in ruby-net-scp was intended and your package needs to update to 
the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from ruby-net-scp should 
really add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


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=ruby-net-scp

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet-beaker/29263144/log.gz


┌──┐
│ Checking Rubygems dependency resolution on ruby3.0 
  │

└──┘

GEM_PATH= ruby3.0 -e gem\ \"beaker\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in 
block in activate_dependencies': Could not find 'net-scp' (~> 3.0) among 
123 total gem(s) (Gem::MissingSpecError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' 
at: 
/usr/share/rubygems-integration/all/specifications/beaker-4.30.0.gemspec, 
execute `gem env` for more information
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
in activate_dependencies'

from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
`activate_dependencies'

from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
`activate'
	from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`block in gem'
	from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'

from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': 
Could not find 'net-scp' (~> 3.0) - did find: [net-scp-4.0.0] 
(Gem::MissingSpecVersionError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' 
, execute `gem env` for more information
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
in activate_dependencies'

from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
`activate_dependencies'

from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
`activate'
	from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`block in gem'
	from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'

from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'
abbrev (default: 0.1.0)
archive-tar-minitar (0.9)
base64 (default: 0.1.0)
bcrypt_pbkdf (1.1.0)
beaker (4.30.0)
beaker-hostgenerator (1.7.1)
benchmark (default: 0.1.1)
bigdecimal (default: 3.0.0)
bundler (default: 2.2.33)
byebug (11.1.3)
cgi (default: 0.2.1)
coderay (1.1.3)
columnize (0.9.0)
csv (default: 3.1.9)
date (default: 3.1.3)
dbm (default: 1.1.0)
debug (default: 0.2.1)
deep_merge (1.1.1)
delegate (default: 0.2.0)
did_you_mean (default: 1.5.0)
diff-lcs (1.5.0)
digest (default: 3.0.0)
docile (1.1.5)
drb (default: 2.0.5)
ed25519 (1.3.0)
english (default: 0.7.1)
erb (default: 2.2.0)
etc (default:

Processed: puppet-beaker: autopkgtest needs update for new version of ruby-net-scp: Could not find 'net-scp' (~> 3.0)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ruby-net-scp
Bug #1025979 [src:puppet-beaker] puppet-beaker: autopkgtest needs update for 
new version of ruby-net-scp: Could not find 'net-scp' (~> 3.0)
Added indication that 1025979 affects src:ruby-net-scp

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

Bug#1025978: libsyntax-keyword-dynamically-perl breaks libtangence-perl autopkgtest: Future::AsyncAwait version 0.6 required--this is only version 0.59

[Paul Gevers]

Source: libsyntax-keyword-dynamically-perl, libtangence-perl
Control: found -1 libsyntax-keyword-dynamically-perl/0.11-1
Control: found -1 libtangence-perl/0.30-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
libsyntax-keyword-dynamically-perl from testing0.11-1
libtangence-perl   from testing0.30-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 of 
libsyntax-keyword-dynamically-perl to testing [1]. Due to the nature of 
this issue, I filed this bug report against both packages. Can you 
please investigate the situation and reassign the bug to the right package?


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

Paul

[1] 
https://qa.debian.org/excuses.php?package=libsyntax-keyword-dynamically-perl


https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtangence-perl/29260907/log.gz

t/00use.t .. ok 1 - use Tangence;
ok 2 - use Tangence::Class;
ok 3 - use Tangence::Client;
ok 4 - use Tangence::Constants;
ok 5 - use Tangence::Message;
ok 6 - use Tangence::Object;
ok 7 - use Tangence::ObjectProxy;
ok 8 - use Tangence::Property;
not ok 9 - use Tangence::Registry;

#   Failed test 'use Tangence::Registry;'
#   at t/00use.t line 16.
# Tried to use 'Tangence::Registry'.
# Error:  Future::AsyncAwait version 0.6 required--this is only 
version 0.59 at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 112.

# BEGIN failed--compilation aborted.
# Compilation failed in require at 
/usr/share/perl5/Tangence/Compiler/Parser.pm line 12.
# BEGIN failed--compilation aborted at 
/usr/share/perl5/Tangence/Compiler/Parser.pm line 12.
# Compilation failed in require at /usr/share/perl5/Tangence/Registry.pm 
line 20.
# BEGIN failed--compilation aborted at 
/usr/share/perl5/Tangence/Registry.pm line 20.

# Compilation failed in require at t/00use.t line 16.
# BEGIN failed--compilation aborted at t/00use.t line 16.
ok 10 - use Tangence::Server;
ok 11 - use Tangence::Server::Context;
ok 12 - use Tangence::Stream;
1..12
# Looks like you failed 1 test of 12.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/12 subtests t/01compiler-parser.t .. ok 1 - keys of t/Ball.tan
ok 2 - 't.Colourable meta' isa 'Tangence::Meta::Class'
ok 3 - t.Colourable name
ok 4 - t.Colourable perlname
ok 5 - t.Colourable direct props
ok 6 - 't.Colourable prop colour' isa 'Tangence::Meta::Property'
ok 7 - t.Colourable prop colour name
ok 8 - t.Colourable prop colour dimension
ok 9 - 't.Colourable prop colour type' isa 'Tangence::Meta::Type'
ok 10 - t.Colourable prop colour type sig
ok 11 - t.Colourable prop colour !smashed
ok 12 - t.Colourable props
ok 13 - t.Colourable ->property
ok 14 - 't.Ball meta' isa 'Tangence::Meta::Class'
ok 15 - t.Ball direct methods
ok 16 - 't.Ball method bounce' isa 'Tangence::Meta::Method'
ok 17 - t.Ball method bounce class
ok 18 - t.Ball method bounce name
ok 19 - t.Ball method bounce has 1 argument
ok 20 - t.Ball method bounce arg[0] name
ok 21 - 't.Ball method bounce arg[0] type' isa 'Tangence::Meta::Type'
ok 22 - t.Ball method bounce arg[0] type sig
ok 23 - t.Ball method bounce argtypes sigs
ok 24 - 't.Ball method bounce ret' isa 'Tangence::Meta::Type'
ok 25 - t.Ball method bounce ret sig
ok 26 - t.Ball methods
ok 27 - t.Ball ->method
ok 28 - t.Ball direct events
ok 29 - 't.Ball event bounced' isa 'Tangence::Meta::Event'
ok 30 - t.Ball event bounced class
ok 31 - t.Ball event bounced name
ok 32 - t.Ball event bounced has 1 argument
ok 33 - t.Ball event bounced arg[0] name
ok 34 - 't.Ball event bounced arg[0] type' isa 'Tangence::Meta::Type'
ok 35 - t.Ball event bounced arg[0] type sig
ok 36 - t.Ball event bounced argtypes sigs
ok 37 - t.Ball events
ok 38 - t.Ball ->event
ok 39 - t.Ball direct props
ok 40 - t.Ball prop size class
ok 41 - t.Ball prop size name
ok 42 - t.Ball prop size dimension
ok 43 - 't.Ball prop size type' isa 'Tangence::Meta::Type'
ok 44 - t.Ball prop size type sig
ok 45 - t.Ball prop size smashed
ok 46 - t.Ball props
ok 47 - t.Ball ->property
ok 48 - t.Ball direct superclasses
ok 49 - t.Ball superclasses
ok 50 - t.TestObj prop array dimension
ok 51 - t.TestObj prop array type sig
ok 52 - t.TestObj prop hash dimension
ok 53 - t.TestObj prop hash type sig
ok 54 - t.TestObj prop queue dimension
ok 55 - t.TestObj prop queue type sig
ok 56 - t.TestObj prop scalar dimension
ok 57 - t.TestObj prop scalar type
ok 58 - t.TestObj prop objset dimensio

Processed: bug 1024064 is forwarded to https://github.com/sagemath/cypari2/issues/114

[Debian Bug Tracking System]

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

> forwarded 1024064 https://github.com/sagemath/cypari2/issues/114
Bug #1024064 [src:cypari2] cypari2 FTBFS with Python 3.11 as supported version
Set Bug forwarded-to-address to 
'https://github.com/sagemath/cypari2/issues/114'.
> thanks
Stopping processing here.

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

Processed: libsyntax-keyword-dynamically-perl breaks libtangence-perl autopkgtest: Future::AsyncAwait version 0.6 required--this is only version 0.59

[Debian Bug Tracking System]

Processing control commands:

> found -1 libsyntax-keyword-dynamically-perl/0.11-1
Bug #1025978 [src:libsyntax-keyword-dynamically-perl, src:libtangence-perl] 
libsyntax-keyword-dynamically-perl breaks libtangence-perl autopkgtest: 
Future::AsyncAwait version 0.6 required--this is only version 0.59
Marked as found in versions libsyntax-keyword-dynamically-perl/0.11-1.
> found -1 libtangence-perl/0.30-1
Bug #1025978 [src:libsyntax-keyword-dynamically-perl, src:libtangence-perl] 
libsyntax-keyword-dynamically-perl breaks libtangence-perl autopkgtest: 
Future::AsyncAwait version 0.6 required--this is only version 0.59
Marked as found in versions libtangence-perl/0.30-1.

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

Processed: Re: Bug#1025954: u-boot-menu: renders system unbootable with u-boot 21.10

[Debian Bug Tracking System]

Processing control commands:

> severity 1025954 serious
Bug #1025954 [u-boot-menu] u-boot-menu: renders system unbootable with u-boot 
21.10
Severity set to 'serious' from 'important'

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

Bug#1025406: tpm2-pytss: FTBFS in sid

[Bastian Germann]

Also: Does v2.0.0 help?

Processed: tagging 1019172

[Debian Bug Tracking System]

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

> tags 1019172 + ftbfs
Bug #1019172 [src:opengrm-ngram] opengrm-ngram FTBFS against libfst 1.7.9
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1024907: marked as done (deepdiff: (autopkgtest) needs update for python3.11: AssertionError)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 16:04:24 +
with message-id 
and subject line Bug#1024907: fixed in deepdiff 6.2.2-1
has caused the Debian Bug report #1024907,
regarding deepdiff: (autopkgtest) needs update for python3.11: AssertionError
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.)


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

Source: deepdiff
Version: 5.8.2-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
deepdiff   from testing5.8.2-3
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/deepdiff/28726222/log.gz

=== FAILURES 
===
_ TestDeepDiffText.test_enums 
__


self = 

def test_enums(self):
from enum import Enum
class MyEnum(Enum):
A = 1
B = 2
ddiff = DeepDiff(MyEnum.A, MyEnum(1))
result = {}
assert ddiff == result
ddiff = DeepDiff(MyEnum.A, MyEnum.B)
result = {
'values_changed': {
'root._name_': {
'old_value': 'A',
'new_value': 'B'
},
'root._value_': {
'old_value': 1,
'new_value': 2
},
'root.name': {
'old_value': 'A',
'new_value': 'B'
},
'root.value': {
'old_value': 1,
'new_value': 2
},
}
}

  assert ddiff == result
E   AssertionError: assert {'values_chan...d_value': 1}}} == 
{'values_chan...d_value': 1}}}

E Differing items:
E {'values_changed': {'root._name_': {'new_value': 'B', 
'old_value': 'A'}, 'root._sort_order_': {'new_value': 1, 'old_value': 
0}, 'root._value_': {'new_value': 2, 'old_value': 1}, 'root.name': 
{'new_value': 'B', 'old_value': 'A'}, ...}} != {'values_changed': 
{'root._name_': {'new_value': 'B', 'old_value': 'A'}, 'root._value_': 
{'new_value': 2, 'old_value': 1}, 'root.name': {'new_value': 'B', 
'old_value': 'A'}, 'root.value': {'new_value': 2, 'old_value': 1}}}

E Use -v to get more diff

tests/test_diff_text.py:584: AssertionError
__ TestDeepHashPrep.test_enum 
__


self = 

def test_enum(self):
class MyEnum(Enum):
A = 1
B = 2
>   assert DeepHashPrep(MyEnum.A)[MyEnum.A] == 
r'objMyEnum:{str:_name_:str:A;str:_value_:int:1}'
E   AssertionError: assert 'objMyEnum:{s...value_:int:1}' == 
'objMyEnum:{s...value_:int:1}'

E - objMyEnum:{str:_name_:str:A;str:_value_:int:1}
E + 
objMyEnum:{str:_name_:str:A;str:_sort_order_:int:0;str:_value_:int:1}

E ?  +++

tests/test_hash.py:269: AssertionError


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: deepdiff
Source-Version: 6.2.2-1
Done: Louis-Philippe Véronneau 

We believe that the bug you reported is fixed in the latest version of
deepdiff, 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 yo

Bug#1012989: marked as done (libsass: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 15:16:17 +
with message-id 
and subject line Bug#1012989: fixed in libsass 3.6.5+20220909-1
has caused the Debian Bug report #1012989,
regarding libsass: ftbfs with GCC-12
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.)


-- 
1012989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsass
Version: 3.6.5+20211226-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

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

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/libsass_3.6.5+20211226-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
@@ -4879,9 +4906,9 @@
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS5_S7_EE@Base
 3.6.4-2~
- 
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EEC1ERKS7_@Base
 3.6.4-4~
+#MISSING: 3.6.5+20211226-1# 
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EEC1ERKS7_@Base
 3.6.4-4~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EEC1ESt16initializer_listIS5_ERKS6_@Base
 3.6.4-2~
- 
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EEC2ERKS7_@Base
 3.6.4-4~
+#MISSING: 3.6.5+20211226-1# 
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EEC2ERKS7_@Base
 3.6.4-4~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EEC2ESt16initializer_listIS5_ERKS6_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EED1Ev@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EED2Ev@Base
 3.6.4-2~
@@ -4892,6 +4919,8 @@
  
(optional=templinst)_ZNSt6vectorIS_IS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EESaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EESaIS7_EE17_M_realloc_insertIJRKS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base
 3.6.4-2~
+ 
_ZNSt6vectorIS_IS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EESaIS7_EEC1ESt16initializer_listIS7_ERKS8_@Base
 3.6.5+20211226-1
+ 
_ZNSt6vectorIS_IS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EESaIS7_EEC2ESt16initializer_listIS7_ERKS8_@Base
 3.6.5+20211226-1
  
(optional=templinst)_ZNSt6vectorIS_IS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EESaIS7_EED

Bug#965695: libuninum: NMU to fix RC bugs.

[Ying-Chun Liu (PaulLiu)]

Hi all,

I plan to fix #965695 and #999178

The debdiff is as attachment.

Will upload to delay/10 queue after 10 days

Yours,
Paul


diff -Nru libuninum-2.7/debian/changelog libuninum-2.7/debian/changelog
--- libuninum-2.7/debian/changelog  2022-12-12 21:19:30.0 +0800
+++ libuninum-2.7/debian/changelog  2022-12-12 17:56:29.0 +0800
@@ -1,3 +1,13 @@
+libuninum (2.7-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Bump debhelper compat to 12 (Closes: #965695)
+  * debian/rules: use dh. (Closes: #999178)
+  * Port to DebSrc3.0 (quilt) format.
+  * Add autopkgtest
+
+ -- Ying-Chun Liu (PaulLiu)   Mon, 12 Dec 2022 17:56:29 
+0800
+
 libuninum (2.7-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libuninum-2.7/debian/compat libuninum-2.7/debian/compat
--- libuninum-2.7/debian/compat 2022-12-12 21:19:30.0 +0800
+++ libuninum-2.7/debian/compat 1970-01-01 08:00:00.0 +0800
@@ -1 +0,0 @@
-5
diff -Nru libuninum-2.7/debian/control libuninum-2.7/debian/control
--- libuninum-2.7/debian/control2022-12-12 21:19:30.0 +0800
+++ libuninum-2.7/debian/control2022-12-12 17:56:29.0 +0800
@@ -1,7 +1,7 @@
 Source: libuninum
-Priority: extra
+Priority: optional
 Maintainer: Bartosz Fenski 
-Build-Depends: debhelper (>= 5), autotools-dev, libgmp3-dev
+Build-Depends: debhelper-compat (= 12), libgmp3-dev
 Standards-Version: 3.7.3
 Section: libs
 Homepage: http://billposer.org/Software/libuninum.html
@@ -9,7 +9,7 @@
 Package: libuninum-dev
 Section: libdevel
 Architecture: any
-Depends: libuninum5 (>= ${binary:Version})
+Depends: libuninum5 (= ${binary:Version}), ${misc:Depends}
 Description: development files for Libuninum library
  Libuninum is a library for converting Unicode strings to numbers and numbers 
to
  Unicode strings. Standard functions like strtoul, strtod, and sprintf do
@@ -24,7 +24,7 @@
 Package: libuninum5
 Section: libs
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: library for handling numbers as Unicode strings
  Libuninum is a library for converting Unicode strings to numbers and numbers 
to
  Unicode strings. Standard functions like strtoul, strtod, and sprintf do
@@ -36,7 +36,7 @@
 Package: numconv
 Section: utils
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: utility for conversion numbers as Unicode strings
  numconv is an utility handling number system conversions and provides 
  a convenient way to delimit numbers generated by other programs without 
diff -Nru libuninum-2.7/debian/libuninum5.install 
libuninum-2.7/debian/libuninum5.install
--- libuninum-2.7/debian/libuninum5.install 2022-12-12 21:19:30.0 
+0800
+++ libuninum-2.7/debian/libuninum5.install 2022-12-12 17:56:29.0 
+0800
@@ -1 +1 @@
-usr/lib/lib*.so.*
+usr/lib/*/lib*.so.*
diff -Nru libuninum-2.7/debian/libuninum-dev.install 
libuninum-2.7/debian/libuninum-dev.install
--- libuninum-2.7/debian/libuninum-dev.install  2022-12-12 21:19:30.0 
+0800
+++ libuninum-2.7/debian/libuninum-dev.install  2022-12-12 17:56:29.0 
+0800
@@ -1,3 +1,3 @@
 usr/include/uninum/*
-usr/lib/lib*.a
-usr/lib/lib*.so
+usr/lib/*/lib*.a
+usr/lib/*/lib*.so
diff -Nru libuninum-2.7/debian/patches/0001_uninum.patch 
libuninum-2.7/debian/patches/0001_uninum.patch
--- libuninum-2.7/debian/patches/0001_uninum.patch  1970-01-01 
08:00:00.0 +0800
+++ libuninum-2.7/debian/patches/0001_uninum.patch  2022-12-12 
17:52:42.0 +0800
@@ -0,0 +1,19 @@
+--- libuninum-2.7.orig/uninum.c
 libuninum-2.7/uninum.c
+@@ -35,11 +35,11 @@
+  */
+ 
+ 
+-#define ucslen(x) wcslen((signed long *) x)
+-#define ucscpy(x,y) (UTF32 *)wcscpy((signed long *)x,(signed long *)y)
+-#define ucscat(x,y) (UTF32 *)wcscat((signed long *)x,(signed long *)y)
+-#define ucschr(x,y) (UTF32 *)wcschr((signed long *)x,(signed long)y)
+-#define ucsrchr(x,y) (UTF32 *)wcsrchr((signed long *)x,(signed long)y)
++#define ucslen(x) wcslen((wchar_t *) x)
++#define ucscpy(x,y) (UTF32 *)wcscpy((wchar_t *)x,(wchar_t *)y)
++#define ucscat(x,y) (UTF32 *)wcscat((wchar_t *)x,(wchar_t *)y)
++#define ucschr(x,y) (UTF32 *)wcschr((wchar_t *)x,(wchar_t)y)
++#define ucsrchr(x,y) (UTF32 *)wcsrchr((wchar_t *)x,(wchar_t)y)
+ 
+ #define UNINUM
+ 
diff -Nru libuninum-2.7/debian/patches/0002_unicode.patch 
libuninum-2.7/debian/patches/0002_unicode.patch
--- libuninum-2.7/debian/patches/0002_unicode.patch 1970-01-01 
08:00:00.0 +0800
+++ libuninum-2.7/debian/patches/0002_unicode.patch 2022-12-12 
17:52:57.0 +0800
@@ -0,0 +1,18 @@
+--- libuninum-2.7.orig/unicode.h
 libuninum-2.7/unicode.h
+@@ -1,8 +1,10 @@
+-typedef unsigned long UTF32;  /* at least 32 bits */
+-typedef unsigned shortUTF16;  /* at least 16 bits */
+-typedef unsigned shortUCS2;   /* at least 16 bits */
+-typedef unsigned char UTF8;   /* 8 bits */
+-typedef unsigned c

Bug#1024632: [Pkg-erlang-devel] Bug#1024632: Bug#1024632: erlang: CVE-2022-37026 Client Authentication Bypass

[Sergei Golovan]

Hi Salvatore,

On Fri, Dec 9, 2022 at 12:15 AM Salvatore Bonaccorso  wrote:
>
> The upcoming point release for 11.6 is scheduled for 17th with
> uploading window closing the upcoming weekend. If we are confident
> enough about potential regressions, can you make sure the fix land in
> the next bullseye point release?

Unfortunately, I've found a few regressions in the Erlang test suite,
and I couldn't fix them myself yet. I'll try my best to do that
tonight and tomorrow, but I'm afraid I'd suggest postponing uploading
patched Erlang to stable.

Cheers!
-- 
Sergei Golovan

Bug#1025957: libcap-dev is wrongly marked Multi-Arch: same

[Helmut Grohne]

Package: libcap-dev
Version: 1:2.63-1
Severity: serious
Jutsification: fails to install with an unpack errror
User: helm...@debian.org
Usertags: rebootstrap

Coinstalling libcap-dev fails:

| Unpacking libcap-dev:amd64 (1:2.63-1) ...
| dpkg: error processing archive 
/var/cache/apt/archives/libcap-dev_1%3a2.63-1_amd64.deb (--unpack):
|  trying to overwrite shared '/usr/lib/libcap2/tests/cap_test', which is 
different from other instances of package libcap-dev:amd64
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  /var/cache/apt/archives/libcap-dev_1%3a2.63-1_amd64.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)

I suppose that the test binaries were recently added to the -dev
package. There are basically three ways of dealing with this:

a) Drop Multi-Arch: same. This is a little inconvenient for some users,
   but is really something we can do. Most cross builds will continue
   working in the absence of Multi-Arch: same.

b) Move those test binaries to architecture-dependent paths.

c) Move those test binaries to a different package. An obvious candidate
   would be a new package libcap-tests. Prior art: dbus-tests. If you
   do, it would be awesome to support the noinsttest build profile.

We can also do option a) as a stop-gap measure and move to a different
solution later.

Helmut

Bug#1024344: marked as done (precious - new version of rust-serial-test.)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 14:35:54 +0100
with message-id <167085215414.969220.12251404927710635...@auryn.jones.dk>
and subject line Re: Bug#1024344: precious - new version of rust-serial-test.
has caused the Debian Bug report #1024344,
regarding precious - new version of rust-serial-test.
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.)


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

Package: precious
Version: 0.3.0-1
Severity: serious

I've just uploaded version 0.9 of rust-serial-test, the dependencies in precious
need updating to match. A debdiff is attatched.

If I get no response i'll probablly NMU this in a week or so.diff -Nru precious-0.3.0/debian/changelog precious-0.3.0/debian/changelog
--- precious-0.3.0/debian/changelog 2022-10-04 15:00:58.0 +
+++ precious-0.3.0/debian/changelog 2022-11-17 20:57:47.0 +
@@ -1,3 +1,11 @@
+precious (0.3.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch 1001_serial_test.patch to bump serial_test dev-dependency to 0.9
+and update build-depedencies accordingly.
+
+ -- Peter Michael Green   Thu, 17 Nov 2022 20:57:47 +
+
 precious (0.3.0-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru precious-0.3.0/debian/control precious-0.3.0/debian/control
--- precious-0.3.0/debian/control   2022-10-04 14:56:55.0 +
+++ precious-0.3.0/debian/control   2022-11-17 20:53:32.0 +
@@ -28,7 +28,7 @@
  librust-regex-1+default-dev,
  librust-serde-1+default-dev (>= 1.0.130),
  librust-serde-1+derive-dev (>= 1.0.130),
- librust-serial-test-0.5+default-dev ,
+ librust-serial-test-0.9+default-dev ,
  librust-tempfile-3+default-dev ,
  librust-thiserror-1+default-dev (>= 1.0.30),
  librust-toml-0.5+default-dev (>= 0.5.8),
diff -Nru precious-0.3.0/debian/patches/1001_serial_test.patch 
precious-0.3.0/debian/patches/1001_serial_test.patch
--- precious-0.3.0/debian/patches/1001_serial_test.patch1970-01-01 
00:00:00.0 +
+++ precious-0.3.0/debian/patches/1001_serial_test.patch2022-11-17 
20:52:35.0 +
@@ -0,0 +1,34 @@
+Index: precious-0.3.0/precious-core/Cargo.toml
+===
+--- precious-0.3.0.orig/precious-core/Cargo.toml
 precious-0.3.0/precious-core/Cargo.toml
+@@ -31,4 +31,4 @@ which = ">= 3.0.0, < 5.0.0"
+ [dev-dependencies]
+ precious-testhelper = { version = "0.3.0", path = "../precious-testhelper" }
+ pretty_assertions = "1.1.0"
+-serial_test = "0.5.1"
++serial_test = "0.9"
+Index: precious-0.3.0/precious-exec/Cargo.toml
+===
+--- precious-0.3.0.orig/precious-exec/Cargo.toml
 precious-0.3.0/precious-exec/Cargo.toml
+@@ -16,5 +16,5 @@ which = ">= 3.0.0, < 5.0.0"
+ 
+ [dev-dependencies]
+ pretty_assertions = "1.1.0"
+-serial_test = "0.5.1"
++serial_test = "0.9"
+ tempfile = "3.3.0"
+Index: precious-0.3.0/precious-integration/Cargo.toml
+===
+--- precious-0.3.0.orig/precious-integration/Cargo.toml
 precious-0.3.0/precious-integration/Cargo.toml
+@@ -13,7 +13,7 @@ regex = "1.5.5"
+ precious-core = { version = "0.3.0", path = "../precious-core" }
+ precious-exec = { version = "0.3.0", path = "../precious-exec" }
+ precious-testhelper = { version = "0.3.0", path = "../precious-testhelper" }
+-serial_test = "0.5.1"
++serial_test = "0.9"
+ 
+ [[test]]
+ name = "integration_tests"
diff -Nru precious-0.3.0/debian/patches/series 
precious-0.3.0/debian/patches/series
--- precious-0.3.0/debian/patches/series2022-10-04 14:50:23.0 
+
+++ precious-0.3.0/debian/patches/series2022-11-17 20:50:58.0 
+
@@ -1,3 +1,4 @@
 2001_clap.patch
 2001_regex.patch
 2002_privacy.patch
+1001_serial_test.patch
--- End Message ---
--- Begin Message ---
Version: 0.4.0-1

Quoting Jonas Smedegaard (2022-11-24 11:21:12)
> > I've just uploaded version 0.9 of rust-serial-test, the dependencies in 
> > precious
> > need updating to match. A debdiff is attatched.
> > 
> > If I get no response i'll probablly NMU this in a week or so.
> 
> Thanks!
> 
> I expect to update precious in a few days - preferably to newer upstream
> release, if bugs #1024747, #1024749 and #1024750 can be easily fixed,
> otherwise without that version change.  I.e. no need for an NMU here -
> thanks for the offer.

...and this was done with packaging release 0.4.0-1.

Thanks again.

 -

Bug#1024278: libgssglue: autopkgtest failure with pkgconf

[Philipp Kern]

Hey Simon,

On 12.12.22 10:02, Simon Josefsson wrote:

Philipp Kern  writes:


Hey Simon,

On Thu, Nov 17, 2022 at 12:46:19PM +0100, Sebastian Ramacher wrote:

I see.  If so, it would be good if pkgconf was made consistent with
pkg-config here, if the intention is to replace it.


This discussion needs to happen with the pkgconf maintainer / upstream.
But since this is the only package where the extra whitespace seems to
be an issue, I'd just be pragmatic on the libgssglue side.


Could we be pragmatic here and fix it in Debian in the meantime? It'd be
a shame if we had a couple of packages autoremoved from testing due to
this, if it's basically a one character change somewhere.


Feel free to work on the pkgconf bug upstream, or within Debian, or work
around the pkgconf bug within libgssglue, or something else, as you (or
someone else) prefers.  I'm tagging the bug report with 'help'; the
package is already marked LowNMU and I've sent [VAC] to debian-private.


Right, thanks for pointing that out - I had missed that. NMU debdiff 
attached. Thanks!


Kind regards
Philipp Kerndiff -Nru libgssglue-0.7/debian/changelog libgssglue-0.7/debian/changelog
--- libgssglue-0.7/debian/changelog 2022-08-16 01:29:01.0 +0200
+++ libgssglue-0.7/debian/changelog 2022-12-12 13:03:24.0 +0100
@@ -1,3 +1,12 @@
+libgssglue (0.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Be more lenient when checking for pkg-config's cflags output
+in the autopkgtest. libs output was already leniently checked.
+(Closes: #1024278)
+
+ -- Philipp Kern   Mon, 12 Dec 2022 13:03:24 +0100
+
 libgssglue (0.7-1) unstable; urgency=medium
 
   * New upstream version 0.7
diff -Nru libgssglue-0.7/debian/tests/libgssglue 
libgssglue-0.7/debian/tests/libgssglue
--- libgssglue-0.7/debian/tests/libgssglue  2022-08-16 01:26:24.0 
+0200
+++ libgssglue-0.7/debian/tests/libgssglue  2022-12-12 13:03:16.0 
+0100
@@ -6,7 +6,7 @@
 trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
 
 pkg-config --cflags libgssglue
-pkg-config --cflags libgssglue | grep '^-I/usr/include/gssglue$'
+pkg-config --cflags libgssglue | grep '^-I/usr/include/gssglue'
 echo PASS: pkg-config --cflags libgssglue
 
 pkg-config --libs libgssglue

Bug#1024278: marked as done (libgssglue: autopkgtest failure with pkgconf)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 12:49:00 +
with message-id 
and subject line Bug#1024278: fixed in libgssglue 0.7-1.1
has caused the Debian Bug report #1024278,
regarding libgssglue: autopkgtest failure with pkgconf
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.)


-- 
1024278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgssglue
Version: 0.7-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgssglue/28379714/log.gz

Removing autopkgtest-satdep (0) ...
autopkgtest [11:01:24]: test libgssglue: [---
-I/usr/include/gssglue 
autopkgtest [11:01:25]: test libgssglue: ---]
autopkgtest [11:01:25]: test libgssglue:  - - - - - - - - - - results - - - - - 
- - - - -
libgssglue   FAIL non-zero exit status 1
autopkgtest [11:01:25]:  summary
libgssglue   FAIL non-zero exit status 1

It looks like the additional white space makes the autopkgtest fail.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libgssglue
Source-Version: 0.7-1.1
Done: Philipp Kern 

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated libgssglue package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 13:03:24 +0100
Source: libgssglue
Architecture: source
Version: 0.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Simon Josefsson 
Changed-By: Philipp Kern 
Closes: 1024278
Changes:
 libgssglue (0.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Be more lenient when checking for pkg-config's cflags output
 in the autopkgtest. libs output was already leniently checked.
 (Closes: #1024278)
Checksums-Sha1:
 755158a6f6c244a85a718b98ff8c104dfd819f5c 1666 libgssglue_0.7-1.1.dsc
 7cd5f2d2456ea5b5acf856f7f5eec7ace351db63 8160 libgssglue_0.7-1.1.debian.tar.xz
 43708f3b930527eacae087cd86e133b6fe9cb123 6448 
libgssglue_0.7-1.1_amd64.buildinfo
Checksums-Sha256:
 0ca5217ec2afd271cca78312239aecbd9b9607cf57da4c157486e005e75ef1c8 1666 
libgssglue_0.7-1.1.dsc
 fc707b9dfcb79fc6877fe983dea365741a0b5c8d9f03afe724d1a53308a8e9cf 8160 
libgssglue_0.7-1.1.debian.tar.xz
 9b67e1933489ef3d9f059a1d0caa55c653a7db96a473e32466801b81e775afc4 6448 
libgssglue_0.7-1.1_amd64.buildinfo
Files:
 5cd5909653944b7f4f124656f5910da9 1666 libs optional libgssglue_0.7-1.1.dsc
 f7fd0064ba1a50845d34b2dde7ad9970 8160 libs optional 
libgssglue_0.7-1.1.debian.tar.xz
 6d5de6d98b801278669571f9832594b8 6448 libs optional 
libgssglue_0.7-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAmOXHiERHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuxueQgAlt+EigtdryReIlGtH/nysrfD1HB/P9GZ
K3r8NEj0SlQxSXBDcEzkAylDEvhggdIjQ6Hk2yskwA7ivuUyHOb8uQEs4LPqUzUh
YSmNjkvA7T30kmEYep3QMPtwRRDbpF4tV9EKk9uKQzXqmW7d8UqKR6XgCiDfDvkX
7vF6YjaPi7Fp67GbLjDMWsSDORvGKXIy1FIEtOdAE8klg7zInLDuIDpS6iKna/tt
vWUKGOGCndEhxHeTcl1PiXdLT1omyBwp83r5Om81N1yhB6IoTSLzlADbnFciRAQ+
xP95U1fqYThq4MWo6pEoE374To7l6aLNdoWieDEQhP3REh2AINREEw==
=30Bp
-END PGP SIGNATURE End Message ---

Bug#1025947: marked as done (kdegraphics-thumbnailers: missing Breaks+Replaces: kdegraphics-mobipocket (<< 4:22.12.0))

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 12:34:46 +
with message-id 
and subject line Bug#1025947: fixed in kdegraphics-thumbnailers 4:22.12.0-2
has caused the Debian Bug report #1025947,
regarding kdegraphics-thumbnailers: missing Breaks+Replaces: 
kdegraphics-mobipocket (<< 4:22.12.0)
to be marked as done.

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

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


-- 
1025947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdegraphics-thumbnailers
Version: 4:22.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../kdegraphics-thumbnailers_4%3a22.12.0-1_amd64.deb ...
  Unpacking kdegraphics-thumbnailers (4:22.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kdegraphics-thumbnailers_4%3a22.12.0-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/mobithumbnail.so', which is also in 
package kdegraphics-mobipocket 4:21.12.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kdegraphics-thumbnailers_4%3a22.12.0-1_amd64.deb


The existing
  Breaks+Replaces: kdegraphics-mobipocket (<< 4:21.12.3)
are insufficiently versioned.


cheers,

Andreas


kdegraphics-mobipocket=4:21.12.3-1_kdegraphics-thumbnailers=4:22.12.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kdegraphics-thumbnailers
Source-Version: 4:22.12.0-2
Done: Aurélien COUDERC 

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

Debian distribution maintenance software
pp.
Aurélien COUDERC  (supplier of updated 
kdegraphics-thumbnailers package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 13:04:40 +0100
Source: kdegraphics-thumbnailers
Architecture: source
Version: 4:22.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Aurélien COUDERC 
Closes: 1025947
Changes:
 kdegraphics-thumbnailers (4:22.12.0-2) unstable; urgency=medium
 .
   [ Aurélien COUDERC ]
   * Use correct Breaks/Replaces versions against kdegraphics-mobipocket.
 (Closes: #1025947)
Checksums-Sha1:
 09a4e4838bdd1d8ccd3b4508cbd414a9f28ba6fd 2748 
kdegraphics-thumbnailers_22.12.0-2.dsc
 20c8b05f2402cb2b677ba79e35c938b47e265c07 9776 
kdegraphics-thumbnailers_22.12.0-2.debian.tar.xz
 cbd1006e80de6c5882257ed88ea2c09897638bf5 15826 
kdegraphics-thumbnailers_22.12.0-2_amd64.buildinfo
Checksums-Sha256:
 4defe35efb85c4a2bc575820f0359d27f2f4d9ca9d258c5a3b379095e5d60cae 2748 
kdegraphics-thumbnailers_22.12.0-2.dsc
 189af369ea099b22d0f6d629b1f979ba5fc0770e0f4e306cec7827dbb99c9fb6 9776 
kdegraphics-thumbnailers_22.12.0-2.debian.tar.xz
 970544ec3a6902383538fb10337fc58f388bf260b2e1d89b08e3826aa0fda108 15826 
kdegraphics-thumbnailers_22.12.0-2_amd64.buildinfo
Files:
 37d9e6b5ec7dec6ef3489e8d6c4ccf7f 2748 kde optional 
kdegraphics-thumbnailers_22.12.0-2.dsc
 4eeed3495f425909c8f9783d10db84e4 9776 kde optional 
kdegraphics-thumbnailers_22.12.0-2.debian.tar.xz
 19dd75416fdaa3b8428da406d3742368 15826 kde optional 
kdegraphics-thumbnailers_22.12.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmOXGawTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJNKPD/9NbRbSMvN68Tpbhjl4njy+WPdF82t7
KswqSKrqs7aoNg5mOhqTy+l9MKPKAKJ5yW4B8IhwAnLA/f9tihbcNkK/NJngYILq
T+w55QGx1W29IQ2wONKjWukGUDPMDAk2ncBdFNwqVE7f/xnD3L9LlvAi0eatOnZb
0H4H78WjHQ/uvjuPKDcQYlx90yNS+Gr6836Y0H5ESk5qgnLFnoxkU3P5GJfXcYjo
rT0y1JzBLpRZ0cf2M2jQvyrmQgYljNJV07FwRbFlGlqUSKhhmiszkt2PqwcljngP
ApXBywXUCJzSyo8TQdp45JazjwB1tJtX+

Bug#1025020: marked as done (python-azure-devtools: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 12:35:04 +
with message-id 
and subject line Bug#1025020: fixed in python-azure-devtools 1.2.0-4
has caused the Debian Bug report #1025020,
regarding python-azure-devtools: (autopkgtest) needs update for python3.11: 
module 'inspect' has no attribute 'getargspec'
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.)


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

Source: python-azure-devtools
Version: 1.2.0-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
python-azure-devtools  from testing1.2.0-3
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-azure-devtools/28728879/log.gz

=== FAILURES 
===
_ test_preparer_order 
__


def test_preparer_order():
# Mimic a real test runner, for better compat 2.7 / 3.x
suite = unittest.TestSuite()
suite.addTest(_TestClassSample('example_test'))
unittest.TextTestRunner().run(suite)
>   assert len(traces) == 4
E   AssertionError: assert 3 == 4
E+  where 3 = len(['create A', 'create B', 'remove A'])

tests/test_preparer_order.py:38: AssertionError
- Captured stderr call 
-

E
==
ERROR: example_test 
(tests.test_preparer_order._TestClassSample.example_test)

--
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/azure_devtools/scenario_tests/preparers.py", 
line 50, in _preparer_wrapper

fn(test_class_instance, **kwargs)
  File 
"/usr/lib/python3/dist-packages/azure_devtools/scenario_tests/preparers.py", 
line 47, in _preparer_wrapper

trim_kwargs_from_test_function(fn, kwargs)
  File 
"/usr/lib/python3/dist-packages/azure_devtools/scenario_tests/utilities.py", 
line 73, in trim_kwargs_from_test_function
args, _, kw, _ = inspect.getargspec(fn)  # pylint: 
disable=deprecated-method

 ^^
AttributeError: module 'inspect' has no attribute 'getargspec'

--
Ran 1 test in 0.001s

FAILED (errors=1)
=== short test summary info 

FAILED tests/test_preparer_order.py::test_preparer_order - 
AssertionError: as...
== 1 failed, 16 passed, 1 deselected in 0.15s 
==

autopkgtest [23:00:54]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-azure-devtools
Source-Version: 1.2.0-4
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-azure-devtools 
p

Bug#1025947: kdegraphics-thumbnailers: missing Breaks+Replaces: kdegraphics-mobipocket (<< 4:22.12.0)

[Aurélien COUDERC]

Dear Andreas,

Le lundi 12 décembre 2022, 12:54:36 CET Andreas Beckmann a écrit :
> Package: kdegraphics-thumbnailers
> Version: 4:22.12.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
[…]
> The existing
>   Breaks+Replaces: kdegraphics-mobipocket (<< 4:21.12.3)
> are insufficiently versioned.

thank you for your bug report, I’ve uploaded the fix.


Happy hacking,
--
Aurélien

Processed: tagging 1024278

[Debian Bug Tracking System]

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

> tags 1024278 + pending
Bug #1024278 [src:libgssglue] libgssglue: autopkgtest failure with pkgconf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1025000: python-qtawesome: Includes non-source Font Awesome 5

[Andrius Merkys]

Hi,

On 2022-12-12 00:17, Bastian Germann wrote:

finalcif's source has some fa5 prefixes, so the package might be affected.
Andrius, can you please comment on this?


Yes, these are calls to qtawesome.icon('fa5.save') and the like. But if 
fonts can be drop-in-replaced with ones from fonts-fork-awesome then I 
think these icon functions should work as expected.


Andrius

Processed: Bug#1025020 marked as pending in python-azure-devtools

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025020 [src:python-azure-devtools] python-azure-devtools: (autopkgtest) 
needs update for python3.11: module 'inspect' has no attribute 'getargspec'
Added tag(s) pending.

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

Bug#1025020: marked as pending in python-azure-devtools

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-azure-devtools/-/commit/743a5b73258c88f9710a340ecf6b1cb88e44fda8


* Team upload.
  * Add py3.11-getargspec-is-removed.patch (Closes: #1025020)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025020

Bug#1024166: marked as done (blist: dead upstream, no maintainer upload since 2015)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 12:02:24 +
with message-id 
and subject line Bug#1025932: Removed package(s) from unstable
has caused the Debian Bug report #1024166,
regarding blist: dead upstream, no maintainer upload since 2015
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.)


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

Package: src:blist
Severity: serious
X-Debbugs-CC: s...@debian.org

Hi,

The blist package, currently team-maintained by the Debian Python Team, 
has not been updated by its maintainer since 2015. 4 uploads fixing 
either important bugs, or making sure it respects the DPT policy have 
been made since then.


As such, I consider this package is not currently maintained by anyone, 
and thus violates the DPT policy.


Moreover, blist is dead upstream: no commit has been made to the project 
since 2014. This is problematic, as we are now carrying patches for 
Python 3.9, 3.10 and 3.11.


As such, I don't think this package should make it to Bookworm. It 
probably should eventually be RMed too.


I'm CC-ing Sebastien Delafond explicitly, as he seems to be the 
maintainer of all the packages in the archive that depend or 
build-depend on blist (python-raccoon, python-panwid, elastalert).


In a perfect world, those packages should migrate away from blist in 
time for the freeze. If not possible, it would be nice if it could have 
an active maintainer again.


Cheers,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.3.6-10+rm

Dear submitter,

as the package blist has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1025932

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#957209: marked as done (flang: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 11:56:46 +
with message-id 
and subject line Bug#1025890: Removed package(s) from unstable
has caused the Debian Bug report #957209,
regarding flang: ftbfs with GCC-10
to be marked as done.

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

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


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/flang_20190329-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
cd /<>/debian/build/runtime/libpgmath/lib/x86_64 && /usr/bin/cc 
-DFN_PROTO_SUFFIX=_avx2 -DHOST_LINUX -DLINUX -DLINUX86 -DLINUX8664 
-DMAXCPUS=256 -DMAXCPUSL=8 -DMAXCPUSR=8 -DPG_PIC -DTARGET_LINUX 
-DTARGET_LINUX_X86 -DTARGET_LINUX_X8664 -DTARGET_X86 -DTARGET_X8664 
-D_GNU_SOURCE -D_ISOC99_SOURCE -D__gnu_linux__ 
-I/<>/runtime/libpgmath/lib/common 
-I/<>/runtime/libpgmath/lib/x86_64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC   -m64 -O3 -Wall -W -Wstrict-prototypes 
-Wwrite-strings -Werror  -mavx2 -mfma -ffp-contract=fast -o 
CMakeFiles/avx2.dir/datan.c.o   -c 
/<>/runtime/libpgmath/lib/x86_64/datan.c
[ 73%] Building C object lib/x86_64/CMakeFiles/avx2.dir/dcosh.c.o
cd /<>/debian/build/runtime/libpgmath/lib/x86_64 && /usr/bin/cc 
-DFN_PROTO_SUFFIX=_avx2 -DHOST_LINUX -DLINUX -DLINUX86 -DLINUX8664 
-DMAXCPUS=256 -DMAXCPUSL=8 -DMAXCPUSR=8 -DPG_PIC -DTARGET_LINUX 
-DTARGET_LINUX_X86 -DTARGET_LINUX_X8664 -DTARGET_X86 -DTARGET_X8664 
-D_GNU_SOURCE -D_ISOC99_SOURCE -D__gnu_linux__ 
-I/<>/runtime/libpgmath/lib/common 
-I/<>/runtime/libpgmath/lib/x86_64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC   -m64 -O3 -Wall -W -Wstrict-prototypes 
-Wwrite-strings -Werror  -mavx2 -mfma -ffp-contract=fast -o 
CMakeFiles/avx2.dir/dcosh.c.o   -c 
/<>/runtime/libpgmath/lib/x86_64/dcosh.c
[ 73%] Building C object lib/x86_64/CMakeFiles/avx2.dir/dexp2.c.o
cd /<>/debian/build/runtime/libpgmath/lib/x86_64 && /usr/bin/cc 
-DFN_PROTO_SUFFIX=_avx2 -DHOST_LINUX -DLINUX -DLINUX86 -DLINUX8664 
-DMAXCPUS=256 -DMAXCPUSL=8 -DMAXCPUSR=8 -DPG_PIC -DTARGET_LINUX 
-DTARGET_LINUX_X86 -DTARGET_LINUX_X8664 -DTARGET_X86 -DTARGET_X8664 
-D_GNU_SOURCE -D_ISOC99_SOURCE -D__gnu_linux__ 
-I/<>/runtime/libpgmath/lib/common 
-I/<>/runtime/libpgmath/lib/x86_64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC   -m64 -O3 -Wall -W -Wstrict-prototypes 
-Wwrite-strings -Werror  -mavx2 -mfma -ffp-contract=fast -o 
CMakeFiles/avx2.dir/dexp2.c.o   -c 
/<>/runtime/libpgmath/lib/x86_64/dexp2.c
[ 74%] Building C object lib/x86_64/CMakeFiles/avx2.dir/dexp.c.o
cd /<>/debian/build/runtime/libpgmath/lib/x86_64 && /usr/bin/cc 
-DFN_PROTO_SUFFIX=_avx2 -DHOST_LINUX -DLINUX -DLINUX86 -DLINUX8664 
-DMAXCPUS=256 -DMAXCPUSL=8 -DMAXCPUSR=8 -DPG_PIC -DTARGET_LINUX 
-DTARGET_LINUX_X86 -DTARGET_LINUX_X8664 -DTARGET_X86 -DTARGET_X8664 
-D_GNU_SOURCE -D_ISOC99_SOURCE -D__gnu_linux__ 
-I/<>/runtime/libpgmath/lib/common 
-I/<>/runtime/libpgmath/lib/x86_64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC   -m64 -O3 -Wall -W -Wstrict-prototypes 
-Wwrite-strings -Werror  -mavx2 -mfma -ffp-contract=fast -o 
CMakeFiles/avx2.dir/dexp.c.o   -c 
/<>/runtime/libpgmath/lib/x86_64/dexp.c
[ 74%] Building C object lib/x86_64/CMakeFiles/avx2.dir/dlog.c

Bug#947437: marked as done (flang: Please update to llvm-9)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 11:56:46 +
with message-id 
and subject line Bug#1025890: Removed package(s) from unstable
has caused the Debian Bug report #947437,
regarding flang: Please update to llvm-9
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.)


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

Package: flang
Severity: important

Dear Maintainer,

Please upgrade to llvm 9. 7 isn't maintained and will be removed soon.

Thanks
Sylvestre

-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'buildd-unstable'), (500, 
'oldstable'), (300, 'experimental')

Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 20190329-5+rm

Dear submitter,

as the package flang has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1025890

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1025947: kdegraphics-thumbnailers: missing Breaks+Replaces: kdegraphics-mobipocket (<< 4:22.12.0)

[Andreas Beckmann]

Package: kdegraphics-thumbnailers
Version: 4:22.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../kdegraphics-thumbnailers_4%3a22.12.0-1_amd64.deb ...
  Unpacking kdegraphics-thumbnailers (4:22.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kdegraphics-thumbnailers_4%3a22.12.0-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/mobithumbnail.so', which is also in 
package kdegraphics-mobipocket 4:21.12.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kdegraphics-thumbnailers_4%3a22.12.0-1_amd64.deb


The existing
  Breaks+Replaces: kdegraphics-mobipocket (<< 4:21.12.3)
are insufficiently versioned.


cheers,

Andreas


kdegraphics-mobipocket=4:21.12.3-1_kdegraphics-thumbnailers=4:22.12.0-1.log.gz
Description: application/gzip

Bug#1025923: marked as done (python3-adios fails to install: update-alternatives: error: alternative path /usr/lib/python3/dist-packages/adios_openmpi/adios_mpi..so doesn't exist)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 11:34:07 +
with message-id 
and subject line Bug#1025923: fixed in adios 1.13.1-31
has caused the Debian Bug report #1025923,
regarding python3-adios fails to install: update-alternatives: error: 
alternative path /usr/lib/python3/dist-packages/adios_openmpi/adios_mpi..so 
doesn't exist
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.)


-- 
1025923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-adios
Version: 1.13.1-30+b3
Severity: serious

python3-adios fails to install in unstable on amd64:

| Setting up python3-adios (1.13.1-30+b3) ...
| update-alternatives: error: alternative path 
/usr/lib/python3/dist-packages/adios_openmpi/adios_mpi..so doesn't exist
| dpkg: error processing package python3-adios (--configure):
|  installed python3-adios package post-installation script subprocess returned 
error exit status 2
| Processing triggers for libc-bin (2.36-5) ...
| Errors were encountered while processing:
|  python3-adios
| E: Sub-process /usr/bin/dpkg returned an error code (1)

Helmut
--- End Message ---
--- Begin Message ---
Source: adios
Source-Version: 1.13.1-31
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated adios package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Dec 2022 10:56:54 +
Source: adios
Architecture: source
Version: 1.13.1-31
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1025923
Changes:
 adios (1.13.1-31) unstable; urgency=medium
 .
* ABITAG in update-alternatives not set correctly when multiple python3
  versions offered. Closes: #1025923
   * Standards-Version: 4.6.1
Checksums-Sha1:
 d7ffb2d26b2887be0d0e5c098f62cc380046fc82 3138 adios_1.13.1-31.dsc
 ed39d7927ec166a0d8ad35e1c8f38aabf1ac7be7 24180 adios_1.13.1-31.debian.tar.xz
Checksums-Sha256:
 2844ecf3a67f823a1d33c07674008db73dbf9727c73833faa5a607fd23012188 3138 
adios_1.13.1-31.dsc
 162114557e23b86dc20ee0fbab5390a4993cc0d090e7e718cf3b55af01181c47 24180 
adios_1.13.1-31.debian.tar.xz
Files:
 effc973c8238c4a0acfaded9cbe1536f 3138 science optional adios_1.13.1-31.dsc
 8fb63e9a9c1cd919c8519f68b42d1384 24180 science optional 
adios_1.13.1-31.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmOXDvkACgkQy+a7Tl2a
06XvDg//boWl4tfqjXWyULzAf6/SPaPN4s/T7qyegHGIM6E8RFhVUfpNkV2ZOGMG
dA73Mqb+sLumb/63M40zq792snookM253OM9sGF0NmRH4o12fz6TVJxOQv1Vc0BW
cNN0ygDCXwYRF6Wh/s/Y//NVxaWMcpq+DHYEg6Sbw9Xm24QCBtPQl/MLv7wBaemg
AAlPINo1GingZKlggCmH75OqytiL6Uqflz9bfg9xjULMzcLVWrF18o6yWBqZ8bCM
aJohSJ9uWC2dfQ6M2mWHoo5KvcV9BgWUmOmGJOZx+vARGzmAaoaZQGacVYtw6RkR
XSITLdzw9NtRcfoUqDcxASaglhh7ogyTAbgtZw8p/a49x1tuFGWMEXAgYiZusWuq
grPL0qOoz4t+279DShIuLOQbulhvfo9wBK1TlG1MAlvsFuGtM/tel6AhhnRPk1v9
A8ssJmIL5mA6L6koHXgKjiEnWGvS7VG1F5WGJWBTD20OKm1dmoja4OhalHUS4WgJ
BLxuoseG0oki17d23FvuqPycUVWvgOBkuXOsIhE9OAck7Iot/iQWrf8Ce7SJaMZI
P/YNMx2Z9I4Lx2nJSwqp1M3cm58IF81XcC70vbAG3uHJeYE4zljNbjxuJoxQAUuv
yMtvWgv+heZJdi0bdC9wkBuuFuyEIfxJuHeKfc+W3DAnQ1KwQ0s=
=PyOT
-END PGP SIGNATURE End Message ---

Bug#1022255: fixed in python-xarray 2022.11.0-2

[Alastair McKinstry]

Dear Antonio


Apologies but I saw this too late to stop the transition to testing.

At this stage, I believe the best solution is to work on the issues in 
satpy and dask; I can help.


Best regards

Alastair


On 07/12/2022 08:38, Antonio Valentino wrote:

Dear Alastair,

On Mon, 21 Nov 2022 15:12:02 + Debian FTP Masters 
 wrote:

Source: python-xarray
Source-Version: 2022.11.0-2
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated 
python-xarray package)


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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Nov 2022 14:37:38 +
Source: python-xarray
Architecture: source
Version: 2022.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 


Changed-By: Alastair McKinstry 
Closes: 1004869 1022255 1023222
Changes:
 python-xarray (2022.11.0-2) unstable; urgency=medium
 .
   * Ack bogs fixed in this and previous releases:
 Closes: #1022255, #1004869, #1023222
Checksums-Sha1:
 25bfc4ad68c46f9f7428c7a008736478f3bd2fa7 3395 
python-xarray_2022.11.0-2.dsc
 9d5fa48523ea38b6684f9b18e3d3a10a8aee2875 14092 
python-xarray_2022.11.0-2.debian.tar.xz

Checksums-Sha256:
 2921fcf4d7b5b82ed54813180ceacb2261264e99eb22e1b9bcf11e8660755e6e 
3395 python-xarray_2022.11.0-2.dsc
 c480af287094772516773b559ac385d6eed33001e1ded8aa1ddab4db721fc91b 
14092 python-xarray_2022.11.0-2.debian.tar.xz

Files:
 16ee7843761bf700d78213b6a8061f38 3395 python optional 
python-xarray_2022.11.0-2.dsc
 b483b08efbb572a27c4af434d3df17d1 14092 python optional 
python-xarray_2022.11.0-2.debian.tar.xz


-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmN7jiUACgkQy+a7Tl2a
06Vb0Q//YmFju6NG15oqqygNRQiiGIGPXS+qvtwPbXKGJDq6g3rX24KdF2tP77i6
Aw9LjfskclEe7TRQCwaS/49qh+6CE+Tndv47nMGb3jnBGL0vYa9YqOn3XeBAHCcw
aYCvbkks5HxDWizJ6Kh2Ohef0okEl2Q/pHDKMDfF+Q8DEvGh7iFtedVF6ARquPSW
95u3V6QhCCQPws26cYPz1L2a+QJuEf49lohoVDC8u4EtaJHbv1NKXtQP1srEqf10
zqbSd6KDqT3mn4dONtF7etxzQGxSHRySEPJpXQ+2kkdmcueLUT5UAEazC6SCdCUB
GMCqMFbwi4kY7CaaK5646XxCm3QQUg3UeZAMHqsBI9gYModfKG8twRhlyA4N9mam



Unfortunately version 2022.11.2 and 2022.12.0 of xarray still causes 
test failures in satpy.
According to the satpy upstream developers [1] (also reported in one 
of the previous messages [2]), the problem should be related to some 
kind of incompatibility between new versions of xarray and the version 
of dask currently in Debian (2022.02.0).


I can confirm that updating dask to 2022.11.1 fixes the issues and 
satpy tests pass with dask 2022.11.1 and xarray 2022.12.0.


I have started preparing a Merge Request [3] to update the dask package.
Unfortunately, while the Python package itself builds and works well, 
it is currently not possible to build the -doc package because of 
outdated build dependencies or new build dependencies still not in 
debian.


In addition, there are some other test failures in satpy that are not 
related to xarray/dask and could be fixed with an update to the latest 
upstream version of satpy (0.38.0).
I have the packaging work done (locally), but I cannot upload until 
the problem with xarray/dask is solved.


In conclusion the satpy version currently in testing works perfectly 
with xarray 2022.06.0, but the migration of xarray 2022.12.0 would 
break satpy and make it unbuildable both in testing and unstable.


Honestly I'm not sure about what is the best way to proceed.
In principle I think that this issue should be re-open and xarray 
2022.12.0 should not migrate, for the moment at least.


But then the way forward is not clear to me.
Waiting for an update of dask could take some time.
Of course I would be more that happy to help to prepare a new version 
of the dask package.


What is your idea about how to proceed?

[1] https://github.com/pytroll/satpy/issues/2248#issuecomment-1296325915
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022255#16
[3] https://salsa.debian.org/python-team/packages/dask/-/merge_requests/1


kind regards


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry

Processed: Re: Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025943 [dolphin] dolphin: copy/move files: only the first item is copied 
to the clipboard
Ignoring request to change severity of Bug 1025943 to the same value.

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

Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard

[Aurélien COUDERC]

Control: severity -1 serious

Le lundi 12 décembre 2022, 11:45:56 CET antonio a écrit :
> Dear Maintainer,

Dear Antonio,

> there is a kde bug that makes it problematic to copy/move files, see link
> https://bugs.kde.org/show_bug.cgi?id=462928
> 
> I went back to the previous version 4:22.08.1-1

thank you for your bug report.

I’m keeping 22.12.0 in unstable, but raising the severity of this bug report so 
the new version doesn’t migrate to testing.


Happy hacking,
--
Aurélien

Processed: Re: Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1025943 [dolphin] dolphin: copy/move files: only the first item is copied 
to the clipboard
Severity set to 'serious' from 'normal'

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

Bug#1024496: marked as done (qiskit-terra: FTBFS with Python 3.11 as a supported version)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 10:50:37 +
with message-id 

and subject line qiskit-terra: FTBFS with Python 3.11 as a supported version
has caused the Debian Bug report #1024496,
regarding qiskit-terra: FTBFS with Python 3.11 as a supported version
to be marked as done.

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

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


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

Hi Maintainer

qiskit-terra FTBFS during the recent rebuild adding Python 3.11 as a
supported version [1].  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=qiskit-terra


=== FAILURES ===
___ TestPassManagerRun.test_default_pass_manager_two ___
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
  File "/usr/lib/python3.11/concurrent/futures/process.py", line 256,
in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
^
  File "/usr/lib/python3.11/concurrent/futures/process.py", line 205,
in _process_chunk
return [fn(*args) for args in chunk]
   ^
  File "/usr/lib/python3.11/concurrent/futures/process.py", line 205,
in 
return [fn(*args) for args in chunk]
^
  File "/<>/.pybuild/cpython3_3.11/build/qiskit/tools/parallel.py",
line 69, in _task_wrapper
return task(value, *task_args, **task_kwargs)
   ^^
  File 
"/<>/.pybuild/cpython3_3.11/build/qiskit/transpiler/passmanager.py",
line 206, in _in_parallel
running_passmanager = dill.loads(pm_dill)._create_running_passmanager()
  ^^^
  File "/usr/lib/python3/dist-packages/dill/_dill.py", line 327, in loads
return load(file, ignore, **kwds)
   ^^
  File "/usr/lib/python3/dist-packages/dill/_dill.py", line 313, in load
return Unpickler(file, ignore=ignore, **kwds).load()
   ^
  File "/usr/lib/python3/dist-packages/dill/_dill.py", line 525, in load
obj = StockUnpickler.load(self)
  ^
  File "/usr/lib/python3/dist-packages/dill/_dill.py", line 659, in _create_code
if len(args) == 16: return CodeType(*args)
   ^^^
TypeError: code() argument 13 must be str, not int
"""

The above exception was the direct cause of the following exception:

self = 

def test_default_pass_manager_two(self):
"""Test default_pass_manager.run(circuitS).

circuit1 and circuit2:
qr0:-[H]--.  -> 1
  |
qr1:-(+)--.  -> 2
  |
qr2:-(+)--.  -> 3
  |
qr3:-(+)---  -> 5

device:
0  -  1  -  2  -  3  -  4  -  5  -  6

  | | | | | |

  13 -  12  - 11 -  10 -  9  -  8  -   7
"""
qr = QuantumRegister(4, 'qr')
circuit1 = QuantumCircuit(qr)
circuit1.h(qr[0])
circuit1.cx(qr[0], qr[1])
circuit1.cx(qr[1], qr[2])
circuit1.cx(qr[2], qr[3])

circuit2 = QuantumCircuit(qr)
circuit2.cx(qr[1], qr[2])
circuit2.cx(qr[0], qr[1])
circuit2.cx(qr[2], qr[3])

coupling_map = FakeMelbourne().configuration().coupling_map
basis_gates = FakeMelbourne().configuration().basis_gates
initial_layout = [None, qr[0], qr[1], qr[2], None, qr[3]]

pass_manager = level_1_pass_manager(TranspileConfig(
basis_gates=basis_gates,
coupling_map=CouplingMap(coupling_map),
initial_layout=Layout.from_qubit_list(initial_layout),
seed_transpiler=42,
optimization_level=1))
>   new_circuits = pass_manager.run([circuit1, circuit2])

test/python/transpiler/test_passmanager_run.py:112:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
qiskit/transpiler/passmanager.py:195: in run
return self._run_several_circuits(circuits)
qiskit/transpiler/passmanager.py:219: in _run_several_circuits
return parallel_map(PassManager._in_parallel, circuits,
qiskit/tools/parallel.py:

Bug#1024958: marked as done (mistral-dashboard: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'. Did you mean: 'getargs'?)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 10:07:03 +
with message-id 
and subject line Bug#1024958: fixed in mistral-dashboard 15.0.0-2
has caused the Debian Bug report #1024958,
regarding mistral-dashboard: (autopkgtest) needs update for python3.11: module 
'inspect' has no attribute 'getargspec'. Did you mean: 'getargs'?
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.)


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

Source: mistral-dashboard
Version: 15.0.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
mistral-dashboard fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
mistral-dashboard  from testing15.0.0-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mistral-dashboard/28711966/log.gz

/tmp/autopkgtest-lxc._qtzsg39/downtmp/build.uyw/src/debian/tests/unittests: 
11: CURDIR: not found
+ PYTHONPATH=/debian/tmp/usr/lib/python3/dist-packages 
NOSE_WITH_OPENSTACK=1 NOSE_OPENSTACK_COLOR=1 NOSE_OPENSTACK_RED=0.05 
NOSE_OPENSTACK_YELLOW=0.025 NOSE_OPENSTACK_SHOW_ELAPSED=1 
http_proxy=127.0.0.1:9 https_proxy=127.0.0.9:9 HTTP_PROXY=127.0.0.1:9 
HTTPS_PROXY=127.0.0.1:9 
DJANGO_SETTINGS_MODULE=mistraldashboard.test.settings PYTHON=python3.11 
python3.11 -m coverage run manage.py test mistraldashboard 
--settings=mistraldashboard.test.settings

Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc._qtzsg39/downtmp/build.uyw/src/manage.py", 
line 23, in 

execute_from_command_line(sys.argv)
  File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 419, in execute_from_command_line

utility.execute()
  File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 413, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
line 23, in run_from_argv

super().run_from_argv(argv)
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 354, in run_from_argv

self.execute(*args, **cmd_options)
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 398, in execute

output = self.handle(*args, **options)
 ^
  File 
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
line 55, in handle

failures = test_runner.run_tests(test_labels)
   ^^
  File "/usr/lib/python3/dist-packages/django/test/runner.py", line 
728, in run_tests

self.run_checks(databases)
  File "/usr/lib/python3/dist-packages/django/test/runner.py", line 
665, in run_checks

call_command('check', verbosity=self.verbosity, databases=databases)
  File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 181, in call_command

return command.execute(*args, **defaults)
   ^^
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 398, in execute

output = self.handle(*args, **options)
 ^
  File 
"/usr/lib/python3/dist-packages/django/core/management/commands/check.py", 
line 63, in handle

self.check(
  File "/usr/lib/python3/dist-packages/django/core/management/base.py", 
line 419, in check

all_issues = checks.run_checks(
 ^^
  File "/usr/lib/python3/dist-packages/

Bug#1024074: marked as done (bitshuffle FTBFS with Python 3.11 as supported version)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 09:59:14 +
with message-id 

and subject line bitshuffle FTBFS with Python 3.11 as supported version
has caused the Debian Bug report #1024074,
regarding bitshuffle FTBFS with Python 3.11 as supported version
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=bitshuffle&arch=arm64&ver=0.3.5-4%2Bb2&stamp=1668425942&raw=0

...
==
ERROR: test_filter (bitshuffle.tests.test_h5filter.TestFilter.test_filter)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11_bitshuffle/build/bitshuffle/tests/test_h5filter.py",
 line 27, in test_filter
h5.create_dataset(f, b"range", shape, dtype, chunks,
  File "bitshuffle/h5.pyx", line 175, in bitshuffle.h5.create_dataset
  File "h5py/_debian_h5py_mpi/_objects.pyx", line 54, in 
h5py._debian_h5py_mpi._objects.with_phil.wrapper
  File "h5py/_debian_h5py_mpi/_objects.pyx", line 55, in 
h5py._debian_h5py_mpi._objects.with_phil.wrapper
  File "h5py/_debian_h5py_mpi/h5d.pyx", line 87, in 
h5py._debian_h5py_mpi.h5d.create
  File "h5py/_debian_h5py_mpi/defs.pyx", line 365, in 
h5py._debian_h5py_mpi.defs.H5Dcreate
RuntimeError: Unspecified error in H5Dcreate (return value <0)
...
--
Ran 61 tests in 6.774s

FAILED (errors=4)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_bitshuffle/build; python3.11 -m 
unittest discover -v 
--- End Message ---
--- Begin Message ---
Latest givebacks succeeded [1] so appears to have been resolved
elsewhere.  Closing.


[1] https://buildd.debian.org/status/package.php?p=bitshuffle&suite=sid--- End Message ---

Processed: bug 1025000 is forwarded to https://github.com/spyder-ide/qtawesome/issues/220

[Debian Bug Tracking System]

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

> forwarded 1025000 https://github.com/spyder-ide/qtawesome/issues/220
Bug #1025000 [python-qtawesome-common] python-qtawesome: Includes non-source 
Font Awesome 5
Set Bug forwarded-to-address to 
'https://github.com/spyder-ide/qtawesome/issues/220'.
> thanks
Stopping processing here.

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

Processed: Bug#1024958 marked as pending in mistral-dashboard

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1024958 [src:mistral-dashboard] mistral-dashboard: (autopkgtest) needs 
update for python3.11: module 'inspect' has no attribute 'getargspec'. Did you 
mean: 'getargs'?
Added tag(s) pending.

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

Bug#1024958: marked as pending in mistral-dashboard

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1024958 in mistral-dashboard 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/openstack-team/horizon-plugins/mistral-dashboard/-/commit/5cb9ed4b73a3c778945ffed850f5c3eca86dbaa1


* Fix Python 3.11 compat (Closes: #1024958):
- add py3.11-getargspec-is-removed.patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024958

Bug#1024896: marked as done (ghostscript-doc: missing HTML files, package almost empty)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 09:49:23 +
with message-id 
and subject line Bug#1024896: fixed in ghostscript 10.0.0~dfsg-9
has caused the Debian Bug report #1024896,
regarding ghostscript-doc: missing HTML files, package almost empty
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.)


-- 
1024896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript-doc
Version: 10.0.0~dfsg-7
Severity: grave
Justification: renders package unusable

ghostscript-doc is supposed to contain the documentation,
but the documentation is entirely missing!

When upgrading the package:

Processing triggers for doc-base (0.11.1) ...
Processing 2 changed doc-base files...
Error in `/usr/share/doc-base/ghostscript-doc.ghostscript', line 10: all 
`Format' sections are invalid.
Note: `install-docs --verbose --check file_name' may give more details about 
the above error.

Indeed, /usr/share/doc-base/ghostscript-doc.ghostscript contains

Format: HTML
Index: /usr/share/doc/ghostscript/index.html
Files: /usr/share/doc/ghostscript/*.htm*

but the package contains no HTML files, except "News.htm".

It seems that previous versions contained them:

zira:~> apt-file search /usr/share/doc/ghostscript/index.html
ghostscript-doc: /usr/share/doc/ghostscript/index.html

so they have been silently dropped (the NEWS.Debian.gz and
changelog.Debian.gz don't say anything).

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

ghostscript-doc depends on no packages.

ghostscript-doc recommends no packages.

Versions of packages ghostscript-doc suggests:
ii  ghostscript  10.0.0~dfsg-7

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 10.0.0~dfsg-9
Done: Håvard F. Aasen 

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

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated ghostscript 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 07:45:09 +0100
Source: ghostscript
Architecture: source
Version: 10.0.0~dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard F. Aasen 
Closes: 1024896 1024964
Changes:
 ghostscript (10.0.0~dfsg-9) unstable; urgency=medium
 .
   * QA upload.
   * Build docs with sphinx. Closes: #1024896, #1024964
Checksums-Sha1:
 a7e1c8c99bb9bb05c0310190ca538719807de4e9 2828 ghostscript_10.0.0~dfsg-9.dsc
 5c3fefd754ab47472df3f7e971c7c9b0852069f8 83816 
ghostscript_10.0.0~dfsg-9.debian.tar.xz
 c21499cef2d99b77e09f144c8cb5841bc3b349f6 10080 
ghostscript_10.0.0~dfsg-9_source.buildinfo
Checksums-Sha256:
 7dd9a4c2236791828ecc4c051b9572920f82716043a321dc92347208a27a9081 2828 
ghostscript_10.0.0~dfsg-9.dsc
 4cdc001db308e32296cea4ccefe209447c02dbc314660c245517d1c9a01b4e6c 83816 
ghostscript_10.0.0~dfsg-9.debian.tar.xz
 2fada5f5f952c9673e7edc363de86a704948564bd0d6259e08d4d6df943d1475 10080 
ghostscript_10.0.0~dfsg-9_source.buildinfo
Files:
 b9c9240815ab42ce56b1490ff53a3b1c 2828 text optional 
ghostscript_10.0.0~dfsg-9.dsc
 c9fc029500e690594abb583744e6e511 83816 text optional 
ghostscript_10.0.0~dfsg-9.debian.tar.xz
 5ae90cce99bcccd31cc1a9c0536bce82 10080 text optional 
ghostscript_10.0.0~dfsg-9_sourc

Bug#1002092: marked as done (ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.7" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 15:17:10 +0530
with message-id 
and subject line Re: ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.7" failed.
has caused the Debian Bug report #1002092,
regarding ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.7" 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.)


-- 
1002092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sidekiq-cron
Version: 1.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-sidekiq-cron/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"sidekiq-cron\"
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-sidekiq-cron/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-sidekiq-cron/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -S rake -f debian/ruby-tests.rake
> ./debian/start-redis-server.sh ruby2.7 -S rake -f 
> /<>/debian/ruby-tests.rake test
> + PID=953086
> + trap cleanup INT EXIT TERM ALRM
> + ruby2.7 -S rake -f /<>/debian/ruby-tests.rake test
> + redis-server
> 953086:C 20 Dec 2021 19:06:25.740 # oO0OoO0OoO0Oo Redis is starting 
> oO0OoO0OoO0Oo
> 953086:C 20 Dec 2021 19:06:25.740 # Redis version=6.0.16, bits=64, 
> commit=, modified=0, pid=953086, just started
> 953086:C 20 Dec 2021 19:06:25.740 # Warning: no config file specified, using 
> the default config. In order to specify a config file use redis-server 
> /path/to/redis.conf
> 953086:M 20 Dec 2021 19:06:25.740 * Increased maximum number of open files to 
> 10032 (it was originally set to 1024).
> 953086:M 20 Dec 2021 19:06:25.741 * Running mode=standalone, port=6379.
> 953086:M 20 Dec 2021 19:06:25.741 # Server initialized
> 953086:M 20 Dec 2021 19:06:25.741 # WARNING overcommit_memory is set to 0! 
> Background save may fail under low memory condition. To fix this issue add 
> 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the 
> command 'sysctl vm.overcommit_memory=1' for this to take effect.
> 953086:M 20 Dec 2021 19:06:25.741 # WARNING you have Transparent Huge Pages 
> (THP) support enabled in your kernel. This will create latency and memory 
> usage issues with Redis. To fix this issue run the command 'echo madvise > 
> /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your 
> /etc/rc.local in order to retain the setting after a reboot. Redis must be 
> restarted after THP is disabled (set to 'madvise' or 'never').
> 953086:M 20 Dec 2021 19:06:25.741 * Ready to accept connections
> /usr/bin/ruby2.7 -w -I"lib:test" 
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb
>  "test/unit/job_test.rb" 
> /<>/test/test_helper.rb:50: warning: `*' interpreted as argument 
> prefix
> /<>/lib/sidekiq/cron/job.rb:308: warning: assigned but unused 
> variable - e
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85: warning: 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85: warning: 
> loading in progress, circular require considered harmful - 
> /<>/lib/sidekiq/cron.rb
>   from 
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in
>   `'
>   from 
> /usr/share/rubygems-inte

Processed: affects

[Debian Bug Tracking System]

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

> affects 1003242 python3-django-hyperkitty
Bug #1003242 [python3-mailman-hyperkitty] python3-mailman-hyperkitty: Need a 
newer version to match mailman core
Added indication that 1003242 affects python3-django-hyperkitty
> severity 1003242 grave
Bug #1003242 [python3-mailman-hyperkitty] python3-mailman-hyperkitty: Need a 
newer version to match mailman core
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1025013: marked as done (murano: (autopkgtest) needs update for python3.11: 'NoneType' object has no attribute 'object_store')

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 09:21:31 +
with message-id 
and subject line Bug#1025013: fixed in murano 1:14.0.0-3
has caused the Debian Bug report #1025013,
regarding murano: (autopkgtest) needs update for python3.11: 'NoneType' object 
has no attribute 'object_store'
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.)


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

Source: murano
Version: 1:14.0.0-1.1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
murano from testing1:14.0.0-1.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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/m/murano/28728875/log.gz

/tmp/autopkgtest-lxc.kds0pukh/downtmp/build.RVv/src/murano/db/models.py:292: 
SAWarning: implicitly coercing SELECT object to scalar subquery; please 
use the .scalar_subquery() method to produce a scalar subquery.

  package_count = sa_orm.column_property(
2022-11-27 23:02:40.207 11285 INFO oslo_db.sqlalchemy.provision [-] The 
mysql+pymysql backend is unavailable: (pymysql.err.OperationalError) 
(2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] 
ECONNREFUSED)")

(Background on this error at: https://sqlalche.me/e/14/e3q8)
Exception ignored in: 0x7f987e85d6c0>

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.kds0pukh/downtmp/build.RVv/src/murano/dsl/murano_object.py", 
line 410, in __del__

self.executor.object_store.schedule_object_destruction(self)
^^
AttributeError: 'NoneType' object has no attribute 'object_store'
Exception ignored in: 0x7f987e85d6c0>

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.kds0pukh/downtmp/build.RVv/src/murano/dsl/murano_object.py", 
line 410, in __del__

self.executor.object_store.schedule_object_destruction(self)
^^
AttributeError: 'NoneType' object has no attribute 'object_store'
Exception ignored in: 0x7f987e85d6c0>

murano.tests.unit.dsl.test_agent.TestAgent.test_agent_disabled
murano.tests.unit.dsl.test_agent.TestAgent.test_agent_disabled ... ok
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.kds0pukh/downtmp/build.RVv/src/murano/dsl/murano_object.py", 
line 410, in __del__

self.executor.object_store.schedule_object_destruction(self)
^^
2022-11-27 23:02:40.266 11273 WARNING murano.engine.system.agent [None 
dummy-request test_user test_tenant - - - -] Key file %s does not exist. 
Message signing is disabled

AttributeError: 'NoneType' object has no attribute 'object_store'
murano.tests.unit.dsl.test_agent.TestAgent.test_agent_enabled
murano.tests.unit.dsl.test_agent.TestAgent.test_agent_enabled ... ok
2022-11-27 23:02:40.272 11273 WARNING murano.engine.system.agent [None 
dummy-request test_user test_tenant - - - -] Key file %s does not exist. 
Message signing is disabled


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: murano
Source-Version: 1:14.0.0-3
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
murano, 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 1025...@bugs.debian.org,
and

Bug#1025028: marked as done (python-cinderclient: (autopkgtest) needs update for python3.11: conflicting subparser: another-fake-action)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 09:07:14 +
with message-id 
and subject line Bug#1025028: fixed in python-cinderclient 1:9.1.0-3
has caused the Debian Bug report #1025028,
regarding python-cinderclient: (autopkgtest) needs update for python3.11: 
conflicting subparser: another-fake-action
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.)


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

Source: python-cinderclient
Version: 1:9.1.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
python-cinderclientfrom testing1:9.1.0-2
all others from testingfrom testing

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

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


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

Paul

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

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

==
FAIL: 
cinderclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_actions_with_versioned_args

cinderclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_actions_with_versioned_args
--
testtools.testresult.real._StringException: Traceback (most recent call 
last):

  File "/usr/lib/python3.11/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
   ^
  File 
"/tmp/autopkgtest-lxc.sogz78te/downtmp/build.8vO/src/cinderclient/tests/unit/test_shell.py", 
line 538, in test_load_actions_with_versioned_args

shell._find_actions(subparsers, fake_actions_module,
  File 
"/tmp/autopkgtest-lxc.sogz78te/downtmp/build.8vO/src/cinderclient/shell.py", 
line 427, in _find_actions

subparser = subparsers.add_parser(
^^
  File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument : conflicting subparser: 
another-fake-action



==
FAIL: 
cinderclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_versioned_actions

cinderclient.tests.unit.test_shell.TestLoadVersionedActions.test_load_versioned_actions
--
testtools.testresult.real._StringException: Traceback (most recent call 
last):
  File 
"/tmp/autopkgtest-lxc.sogz78te/downtmp/build.8vO/src/cinderclient/tests/unit/test_shell.py", 
line 392, in test_load_versioned_actions

shell._find_actions(subparsers, fake_actions_module,
  File 
"/tmp/autopkgtest-lxc.sogz78te/downtmp/build.8vO/src/cinderclient/shell.py", 
line 427, in _find_actions

subparser = subparsers.add_parser(
^^
  File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument : conflicting subparser: 
fake-action



==
FAIL: cinderclient.tests.unit.test_shell.ShellTest.test_help
cinderclient.tests.unit.test_shell.ShellTest.test_help
--
testtools.testresult.real._StringException: Traceback (most recent call 
last):
  File 
"/tmp/autopkgtest-lxc.sogz78te/downtmp/build.8vO/src/cinderclient/tests/unit/test_shell.py", 
line 129, in test_help

self.ass

Bug#1025013: marked as pending in murano

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1025013 in murano 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/openstack-team/services/murano/-/commit/84b2a4860d9bbab5cad6b10448259d8855afbbdd


* Fix Python 3.11 related unit test failures (Closes: #1025013):
- add py3.11-getargspec-removed.patch
- add py3.11-U-mode-removed.patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025013

Processed: Bug#1025013 marked as pending in murano

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025013 [src:murano] murano: (autopkgtest) needs update for python3.11: 
'NoneType' object has no attribute 'object_store'
Added tag(s) pending.

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

Processed: Re: Bug#1024278: libgssglue: autopkgtest failure with pkgconf

[Debian Bug Tracking System]

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

> tags 1024278 help
Bug #1024278 [src:libgssglue] libgssglue: autopkgtest failure with pkgconf
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#1024278: libgssglue: autopkgtest failure with pkgconf

[Simon Josefsson]

tags 1024278 help
thanks

Philipp Kern  writes:

> Hey Simon,
>
> On Thu, Nov 17, 2022 at 12:46:19PM +0100, Sebastian Ramacher wrote:
>> > I see.  If so, it would be good if pkgconf was made consistent with
>> > pkg-config here, if the intention is to replace it.
>> 
>> This discussion needs to happen with the pkgconf maintainer / upstream.
>> But since this is the only package where the extra whitespace seems to
>> be an issue, I'd just be pragmatic on the libgssglue side.
>
> Could we be pragmatic here and fix it in Debian in the meantime? It'd be
> a shame if we had a couple of packages autoremoved from testing due to
> this, if it's basically a one character change somewhere.

Feel free to work on the pkgconf bug upstream, or within Debian, or work
around the pkgconf bug within libgssglue, or something else, as you (or
someone else) prefers.  I'm tagging the bug report with 'help'; the
package is already marked LowNMU and I've sent [VAC] to debian-private.

/Simon


signature.asc
Description: PGP signature

Bug#1025203: Reopen

[Andreas Tille]

reopen -1

Reopening again since also preventing parallel builds did not helped.

Kind regards
Andreas.

Bug#1024952: marked as done (ironic-inspector: (autopkgtest) needs update for python3.11: Failed to resolve the hostname (meow) for node uuid1)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 09:35:38 +0100
with message-id <1244d3ac-37ad-95d9-232b-a29262689...@debian.org>
and subject line Cannot reproduce FTBFS either
has caused the Debian Bug report #1024952,
regarding ironic-inspector: (autopkgtest) needs update for python3.11: Failed 
to resolve the hostname (meow) for node uuid1
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.)


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

Source: ironic-inspector
Version: 11.1.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
ironic-inspector fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
ironic-inspector   from testing11.1.0-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 of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/i/ironic-inspector/28726237/log.gz

ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_additional_fields
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_additional_fields 
... ok
   ERROR [ironic_inspector.utils] [node: ] 
Failed to resolve the hostname (meow) for node uuid1

ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_bad_hostname_errors
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_bad_hostname_errors 
... ok

ironic_inspector.test.unit.test_acl.TestACLDeprecated.test_abort_baremetal_admin
ironic_inspector.test.unit.test_acl.TestACLDeprecated.test_abort_baremetal_admin 
... ok

ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_good_hostname_resolves
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_good_hostname_resolves 
... ok
 WARNING [keystonemiddleware.auth_token] AuthToken middleware is set 
with keystone_authtoken.service_token_roles_required set to False. This 
is backwards compatible but deprecated behaviour. Please set this to True.
 WARNING [keystonemiddleware.auth_token] Use of the auth_admin_prefix, 
auth_host, auth_port, auth_protocol, identity_uri, admin_token, 
admin_user, admin_password, and admin_tenant_name configuration options 
was deprecated in the Mitaka release in favor of an auth_plugin and its 
related options. This class may be removed in a future release.
 WARNING [keystonemiddleware.auth_token] Configuring admin URI using 
auth fragments was deprecated in the Kilo release, and will be removed 
in the Newton release, use 'identity_uri' instead.
 WARNING [keystonemiddleware.auth_token] Configuring 
www_authenticate_uri to point to the public identity endpoint is 
required; clients may not be able to authenticate against an admin endpoint

ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_ipmi_bridging_enabled
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_ipmi_bridging_enabled 
... ok

   ERROR [ironic_inspector.utils] Access denied by policy
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_ipv4_in_resolves
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_ipv4_in_resolves 
... ok

ironic_inspector.test.unit.test_acl.TestACLDeprecated.test_abort_baremetal_observer
ironic_inspector.test.unit.test_acl.TestACLDeprecated.test_abort_baremetal_observer 
... ok

ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_ipv6_in_resolves
ironic_inspector.test.unit.test_common_ironic.TestGetIpmiAddress.test_ipv6_in_resolves 
... ok
 WARNING [keystonemiddleware.auth_token] AuthToken middleware is set 
with ke

Bug#1023679: marked as done (gcc-mingw-w64 build depends on gcc-10 that should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2022 08:35:59 +
with message-id 
and subject line Bug#1023679: fixed in gcc-mingw-w64 25
has caused the Debian Bug report #1023679,
regarding gcc-mingw-w64 build depends on gcc-10 that should not be in bookworm
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.)


-- 
1023679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-mingw-w64
Version: 24.4
Severity: serious
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.
--- End Message ---
--- Begin Message ---
Source: gcc-mingw-w64
Source-Version: 25
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated gcc-mingw-w64 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 09:00:34 +0100
Source: gcc-mingw-w64
Architecture: source
Version: 25
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 1023679
Changes:
 gcc-mingw-w64 (25) unstable; urgency=medium
 .
   * Upgrade to GCC 12. Closes: #1023679. It is no longer possible to tweak
 the installation directory for different thread models, so the -posix
 and -win32 packages are no longer co-installable.
   * Drop “Built-Using” from “Architecture: all” packages.
   * Since the POSIX and Win32 packages are no longer co-installable,
 drop support for alternatives and use symlinks to provide the full
 set of command names.
   * Standards-Version 4.6.1, no change required.
Checksums-Sha1:
 8a66780ec6f78e17ba31e8e357db103c3b681bb9 6769 gcc-mingw-w64_25.dsc
 203b034dde080dff1d87028aa8a863e594aafa24 32920 gcc-mingw-w64_25.tar.xz
 1d7b67617cc71f6f05da560767d67d7c02225bb7 7451 gcc-mingw-w64_25_source.buildinfo
Checksums-Sha256:
 43a1296800d482ed56a7b32a5ad7defdef48d33e834a9fbb022f727c6c023806 6769 
gcc-mingw-w64_25.dsc
 f6fabb6577d7e5794353678a8e74e55e5b45f09f5561e72506c7d92e8b69f613 32920 
gcc-mingw-w64_25.tar.xz
 f59c6675ee62e48dbbf47be3026cc7442814491d6dd07e6c5fe2e8262df84258 7451 
gcc-mingw-w64_25_source.buildinfo
Files:
 8de949dbb15ef13af37c3c9934a28bfe 6769 devel optional gcc-mingw-w64_25.dsc
 9072b03673ee28e7db1239611ba30840 32920 devel optional gcc-mingw-w64_25.tar.xz
 712ed4bc25c22d37cffc07320428463a 7451 devel optional 
gcc-mingw-w64_25_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmOW3+cACgkQgNMC9Yht
g5xKbRAAmBnvmz2HC+A4CUwftwDgyzefUsayLwYxDpiIKYZtOghVfyWn9MBN8Iw+
yQVOsWiNjdn1DVfet9dnFa2rIkSTqJebq/vEn6TcdiGhCfhQUzntJI2qvSDifLOy
TBjziKjwH0jNpLa9T2jDYTbCWUMwdOgrI8n7hUZb/68VUDnw1gJ1kGnfkHP9Jr7z
KcrdWUzkm2wcN/rDV/r68rkQmXCpP9Ka8p0qkRLNHYjTKIL+LXFYAHOEQRuwZOsL
bxjcggxhB0FJ9W3faJ41R/4NdQ35blslMI+FtsnzSSOwiE5xt2oskFRir/rk2WOu
ApoeyRt+wfKbsJgBHNAhioyDi5M6tGRLVpQm5cFnD2arCp8YkvM4Z6T44MhL/A1I
G265J+boz0g0EyU3eT5FHG5nDZT/5psZSjH9iiTlgbZYvK7cpuDDxRWcoVEbUq13
XMpEqo1DRe/1Nj/QzcrF8E1bwLBorX5eFwRO6EDMGOT9abAev/5bb1ruNtkvN0C7
GEfXxwdz22seOl9ez8vFgB668G6NR/O3TFxntt4gd7WimHAs3sdCdf4+hPgxxBCM
XExOWLrIR2GVERpeQ747rR4vQRfCo58xehlRC7N80legpryJNpTlD6ZFHI0/d91N
K/eEVXA4naQrtWtbK/JcUAgqae/zrXi15SwRN/ap2sNqZigLvTk=
=nyCi
-END PGP SIGNATURE End Message ---