Bug#1057947: marked as done (hp48cc: missing error trapping in Makefile)

[Debian Bug Tracking System]

Your message dated Fri, 22 Dec 2023 07:50:13 +
with message-id 
and subject line Bug#1057947: fixed in hp48cc 1.3-7
has caused the Debian Bug report #1057947,
regarding hp48cc: missing error trapping in Makefile
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.)


-- 
1057947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hp48cc
Version: 1.0-3
Severity: serious
Justification: policy section 4.6

Debian policy section 4.6 requires that failures from a build step are
propagated rather than continuing and possibly misbuilding. hp48cc
violates this in the upstream build system. The toplevel Makefile.in
says:

| all install clean realclean mostyclean:
|   @for f in $(subdirs); do \
|   (cd $$f && $(MAKE) $@) \
|   done

If any of these fails, no failure is raised and the build continues. I
suggest adding "set -e" before the loop to fix this.

Helmut
--- End Message ---
--- Begin Message ---
Source: hp48cc
Source-Version: 1.3-7
Done: Roberto Lumbreras 

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

Debian distribution maintenance software
pp.
Roberto Lumbreras  (supplier of updated hp48cc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Dec 2023 07:43:15 +0100
Source: hp48cc
Architecture: source
Version: 1.3-7
Distribution: unstable
Urgency: low
Maintainer: Roberto Lumbreras 
Changed-By: Roberto Lumbreras 
Closes: 1057947
Changes:
 hp48cc (1.3-7) unstable; urgency=low
 .
   * Fix missing error trapping in Makefile. (closes: #1057947)
   * Updated standards.
Checksums-Sha1:
 383909c9496c2154f76fcd10200455138be9ce5b 1726 hp48cc_1.3-7.dsc
 34616fc50e4561e7729431bdfef5d48b0fd3cfe4 5316 hp48cc_1.3-7.debian.tar.xz
 c4b9097c5d2cadbfd06280caf47ec9e70fb1d814 6386 hp48cc_1.3-7_amd64.buildinfo
Checksums-Sha256:
 6dfe0ad86e6e36dfbb6aa793f844938ab08a1e4dbab72a8191a7bc99fae9fbb8 1726 
hp48cc_1.3-7.dsc
 705836d22d5568cc7b975d4529e38356de2e036f9beaebac60be2518ba16d581 5316 
hp48cc_1.3-7.debian.tar.xz
 948ff638f8fa3ddf235b758069212097f69c57a9c03976cba0be604137316f33 6386 
hp48cc_1.3-7_amd64.buildinfo
Files:
 325cb7006bcd0c5cc5875a7c3cb5fe3a 1726 devel optional hp48cc_1.3-7.dsc
 c0299ab918ee9a9d37c46564d0a9cd0c 5316 devel optional hp48cc_1.3-7.debian.tar.xz
 b593a447418f2f66f07bed71e04dcc2a 6386 devel optional 
hp48cc_1.3-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE0P8TF3YtXzyApcdAtn7iEBIpC00FAmWFOpMRHHJvdmVyQGRl
Ymlhbi5vcmcACgkQtn7iEBIpC03sjw/+KlXvliJA8oTzKR2wf7Uh7+w3GVQrcCQy
W3YZC0pa7od/ze+FMak835O71quko0lutFOlC3Mf4noTq2einL/Bsrg738Db8P7o
3NrtHsMHosV9xoPKHCGmQD5gqwKp7D4plGEmtxMpWJB6q9/Xaf1fCgV2OF7hOh9n
R7bBAqP+V+dkJj80HtTK/4q1SB2RmtL5a/2WASZ3+zHIPbofdOntGs2R1/ab5gUP
pon39n64ACMjXzhBS3wXbedAmdCJuNOPGw06Fs7d9/2qqHmit4NkepOQ5PketgCD
a4wbkKf9XVLYAf6Cog954DhaQ3BYkW67CUjTWe2EXqC/zM+e7JNRXIbgJNevlz2a
jyblzF8N83/jhEvWTxLM4SPcgVLkzV/pIck2/+SzfyPK/euOKHKXUMFC+xRYkiWI
FvO2+zQ+OrFu3q73Q+bCZwXUxLGtF/JSV+G6afndFjWYAitc+j3KK/VcLWEpns7C
Y6FLSEnPIRR+Z4I/Q74cfK5s9YzlltffsakL8FIWcIQtfqrBl0t47wS0d81dGBa2
6SxT7wj8oBttxumMiPC+XYIj2tN7KBVoOQr5haxtAX8AD4z5jrIvtIZo9xqWXLG2
YSnz85LjSTx2LPm8foAxdIFBZEG+g4busKVYRQjese4sB0UFKTHd5sTJ1sUFwDFt
76+H7XJLe40=
=NaYB
-END PGP SIGNATURE End Message ---

Bug#1058177: marked as done (sphinxtesters: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Fri, 22 Dec 2023 07:34:49 +
with message-id 
and subject line Bug#1058177: fixed in sphinxtesters 0.2.3-3
has caused the Debian Bug report #1058177,
regarding sphinxtesters: FTBFS: AttributeError: module 'configparser' has no 
attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)


-- 
1058177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxtesters
Version: 0.2.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean 
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence 
> '\s'
>   LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
>   File "/<>/setup.py", line 29, in 
> version=versioneer.get_version(),
> 
>   File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
>   File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
>   ^^
>   File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
>  ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. 
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make: *** [debian/rules:5: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/sphinxtesters_0.2.3-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results

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

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sphinxtesters
Source-Version: 0.2.3-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated sphinxtesters package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 22 Dec 2023 08:13:34 +0100
Source: sphinxtesters
Architecture: source
Version: 0.2.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1058177
Changes:
 sphinxtesters (0.2.3-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Andreas Tille ]
   * Set DPT maintainer
   * Replace SafeConfigParser deprecated in Python3.12
 Closes: #1058177
   * Transparently skip test_bad_pagebuilder instead of ignoring test suite
 errors
Checksums-Sha1:
 669c735b9702d2cfdbfe2a64db63b8bfb34d1c85 2092 sphinxtesters_0.2.3-3.dsc
 f4c7232c8468a75f68d57351f4c6b2609612655e 2968 
sphinxtesters_0.2.3-3.debian.tar.xz
 157dd4680db552a018c8ff4d59e79cf13ab487cc 8001 
sphinxtesters_0.2.3-3_amd64.buildinfo
Checksums-Sha256:
 

Processed: severity of 1059163 is important

[Debian Bug Tracking System]

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

> severity 1059163 important
Bug #1059163 {Done: Anibal Monsalve Salazar } [cpio] cpio: 
Path traversal vulnerability
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#1059163: marked as done (cpio: Path traversal vulnerability)

[Debian Bug Tracking System]

Your message dated Fri, 22 Dec 2023 06:19:25 +
with message-id 
and subject line Bug#1059163: fixed in cpio 2.14+dfsg-1
has caused the Debian Bug report #1059163,
regarding cpio: Path traversal vulnerability
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.)


-- 
1059163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpio
Version: 2.13+dfsg-7.1
Severity: grave

The patch "revert-CVE-2015-1197-handling" (to close bugs #946267 and #946469)
re-enables path traversal vulnerability with maliciously crafted cpio archives.
--- End Message ---
--- Begin Message ---
Source: cpio
Source-Version: 2.14+dfsg-1
Done: Anibal Monsalve Salazar 

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

Debian distribution maintenance software
pp.
Anibal Monsalve Salazar  (supplier of updated cpio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 22 Dec 2023 16:38:54 +1100
Source: cpio
Architecture: source
Version: 2.14+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Anibal Monsalve Salazar 
Closes: 925021 1049402 1059163 1059238
Changes:
 cpio (2.14+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
 Closes: #1049402
 Noteworthy changes in this release:
 - New option --ignore-dirnlink
   Valid in copy-out mode, it instructs cpio to ignore the actual number
   of links reported for each directory member and always store 2
   instead.
 - Changes in --reproducible option
   The --reproducible option implies --ignore-dirlink.  In other words,
   it is equivalent to --ignore-devno --ignore-dirnlink --renumber-inodes.
 - Use GNU ls algorithm for deciding timestamp format in -tv mode
 - Bugfixes
   - Fix cpio header verification.
   - Fix handling of device numbers on copy out.
   - Fix calculation of CRC in copy-out mode.
   - Rewrite the fix for CVE-2015-1197.
   - Fix combination of --create --append --directory.
   - Fix appending to archives bigger than 2G.
   * Update uploaders list
 Closes: #925021
   * Standards-Version: 4.6.2
   * Fix Path traversal vulnerability due to partial revert of fix for 
CVE-2015-1197
 Closes: #1059163
   * cpio-win32 is no longer needed
 Closes: #1059238
Checksums-Sha1:
 eb78be01c0a20b510407d20c8b6271aafa6359b8 1906 cpio_2.14+dfsg-1.dsc
 c07f9046d70b4d83f873138bb7561e7b218ce6b9 1515680 cpio_2.14+dfsg.orig.tar.bz2
 9336fac43abbb385ffc8637c67120a90e508ec0d 15096 cpio_2.14+dfsg-1.debian.tar.xz
 0b09f929fb782060d6594b90aa49d8d7326bebd5 5582 cpio_2.14+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 1317473ea3b00cebce77af6ed954f98088087a460aa7a804c87c5def78b990a3 1906 
cpio_2.14+dfsg-1.dsc
 a45e1c39445fe663e0184d4d72b9f3d5f7ca273e875ce1992fafe49babff592c 1515680 
cpio_2.14+dfsg.orig.tar.bz2
 345cacb20aa4407f5db41ce9ea47c53a0304db8cec7031536f033bc1c44ac957 15096 
cpio_2.14+dfsg-1.debian.tar.xz
 d3468c3b3527726a39db610cd94eecd15c718cd96e9c9f46251ea9cdce4f6273 5582 
cpio_2.14+dfsg-1_amd64.buildinfo
Files:
 24196598763567c4564a0444d0f4863e 1906 utils important cpio_2.14+dfsg-1.dsc
 a13f5918ce2580c1da5ea98dd8b34722 1515680 utils important 
cpio_2.14+dfsg.orig.tar.bz2
 33392e3b8e3a8d5acf3ef044ef2ace1c 15096 utils important 
cpio_2.14+dfsg-1.debian.tar.xz
 75094246fbcf85ac90766840c2d36711 5582 utils important 
cpio_2.14+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExgRcgTiHt3wt/5elfFas/pR4l9gFAmWFIcUACgkQfFas/pR4
l9hmTQ//SNNwjdHybVL6YDzuOy4I0mfLiWzu22NJyl6LrkpX5fhvL6RKKAN8gkSE
OuT/WE3HnXF4Yi/zyYxdzCHAJMrRNzIq9gGU77trgMGiFRrL/oLvAZt02a4TfwkE
ZvnWjpgws/jw3hQRik0SMK0u60G+IVDWjSu3EeJWaQudw6ssdOKpc+OBFTQpXwYI
2W6NhXTEMpKIPChUXLevHlPJOf9XvA8CA/NxRyGpAUt9d0miubE4qjLGVo617Jv7
CXoy/vACeK47nd4POYaSXqqo2M96btqc8AKPMkdk9/ZlHR9PEor0GWVCatXyXckK
7oWBoUdCuwsMu3mRukDd+sPNyIdtvakLzdRLn5VzeWviqVSRmn1PZDYWA74S37Ur
QQe8G8V3kdr33vkTrQV3feFcYnH1v0zupMb9lqCCuiVdXmgK0AbBUwdtrgvYH9M4

Bug#1036869: O: ghostscript -- interpreter for the PostScript language and for PDF

[Steven Robbins]

On Mon, 24 Oct 2022 15:17:20 +0200 Jonas Smedegaard  wrote:

> I have orphaned the ghostscript package, due to lack of time.

I'm willing to take on -- and hopefully, share -- the ghostscript maintenance.
If anyone wants to team up, let me know!

-Steve



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

Bug#1059249: designer-qt6: Segmentation fault in /usr/lib/qt6/bin/designer at launch

[Matthew A. Lukowicz]

Package: designer-qt6
Version: 6.6.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: mlukow...@sdf.org

Hey,

Designer segfaults on launch; seems the bug might be with qt6 xcb integration.

Valgrind reports the following output:

matt@pancakehut:~$ valgrind /usr/lib/qt6/bin/designer 
==947004== Memcheck, a memory error detector 
==947004== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. 
==947004== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info 
==947004== Command: /usr/lib/qt6/bin/designer 
==947004==  
==947004== Syscall param writev(vector[0]) points to uninitialised byte(s) 
==947004==at 0x6A911BD: __writev (writev.c:26) 
==947004==by 0x6A911BD: writev (writev.c:24) 
==947004==by 0x7D46FBF: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) 
==947004==by 0x7D47800: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) 
==947004==by 0x7D48E24: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) 
==947004==by 0x7D48EA0: xcb_wait_for_reply (in 
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) 
==947004==by 0xA933D83: 
QXcbConnection::initializeScreensFromMonitor(xcb_screen_iterator_t*, int, 
QXcbScreen**, bool) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA934927: QXcbConnection::initializeScreens(bool) (in 
/usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA925F42: 
QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char 
const*) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA950B15: QXcbIntegration::QXcbIntegration(QList 
const&, int&, char**) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0x486546F: ??? (in 
/usr/lib/x86_64-linux-gnu/qt6/plugins/platforms/libqxcb.so) 
==947004==by 0x5C06F97: QGuiApplicationPrivate::createPlatformIntegration() 
(in /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x5C08887: QGuiApplicationPrivate::createEventDispatcher() (in 
/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==  Address 0xa2699c5 is 4,533 bytes inside a block of size 21,176 
alloc'd 
==947004==at 0x48459F3: calloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) 
==947004==by 0x7D46990: xcb_connect_to_fd (in 
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) 
==947004==by 0x7D4B191: xcb_connect_to_display_with_auth_info (in 
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) 
==947004==by 0x6E8BD09: _XConnectXCB (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0) 
==947004==by 0x6E7C0C6: XOpenDisplay (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0) 
==947004==by 0xA92EB71: QXcbBasicConnection::QXcbBasicConnection(char 
const*) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA925CF4: 
QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char 
const*) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA950B15: QXcbIntegration::QXcbIntegration(QList 
const&, int&, char**) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0x486546F: ??? (in 
/usr/lib/x86_64-linux-gnu/qt6/plugins/platforms/libqxcb.so) 
==947004==by 0x5C06F97: QGuiApplicationPrivate::createPlatformIntegration() 
(in /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x5C08887: QGuiApplicationPrivate::createEventDispatcher() (in 
/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x6332545: QCoreApplicationPrivate::init() (in 
/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.6.1) 
==947004==  
==947004== Invalid read of size 8 
==947004==at 0x637970A: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.6.1) 
==947004==by 0x5C0D9E5: QGuiApplication::screenAdded(QScreen*) (in 
/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x5C66DB8: 
QWindowSystemInterface::handleScreenAdded(QPlatformScreen*, bool) (in 
/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0xA934A6F: QXcbConnection::initializeScreens(bool) (in 
/usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA925F42: 
QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char 
const*) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0xA950B15: QXcbIntegration::QXcbIntegration(QList 
const&, int&, char**) (in /usr/lib/x86_64-linux-gnu/libQt6XcbQpa.so.6.6.1) 
==947004==by 0x486546F: ??? (in 
/usr/lib/x86_64-linux-gnu/qt6/plugins/platforms/libqxcb.so) 
==947004==by 0x5C06F97: QGuiApplicationPrivate::createPlatformIntegration() 
(in /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x5C08887: QGuiApplicationPrivate::createEventDispatcher() (in 
/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x6332545: QCoreApplicationPrivate::init() (in 
/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.6.1) 
==947004==by 0x5C0890F: QGuiApplicationPrivate::init() (in 
/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6.6.1) 
==947004==by 0x54BCDDC: 

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Rafael Laboissière]

* Sébastien Villemot  [2023-12-21 15:23]:


Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit :

* Santiago Vila  [2023-12-20 22:03]:


El 20/12/23 a las 21:08, Rafael Laboissière escribió:

HOME := $(shell mktemp -d)

so that the same directory is never used twice between consecutive builds.


Yes, this is a much better solution. Thanks for the suggestion. I am 
just wondering: is there a simple way to delete the temporary 
directory after he build is finished ?


I don't know, but most people build packages in temporary/disposable chroots, 
so if the package just writes a few files which are also small, it's not 
something for which I would worry too much.


Yes, it not really a worrisome issue. However, I have just noticed that 
the solution that you proposed with mktemp is a little bit intrusive. 
Indeed, a new temporary directory is created at each invocation of 
debain/rules, such that I end up with five /tmp/tmp.* directories after 
package building, with only the last one being actually used. I will try 
another approach, probably by changing the dh_octave_check script, which 
is the one that eventually needs a writable $HOME directory.


Note that within the context of a shell script, the following ensures 
that the directory is automatically deleted upon exit:


 tmpdir=$(mktemp -d)
 cleanup ()
 {
rm -rf "${tmpdir}"
 }
 trap cleanup EXIT


Thanks, Sébastien.

I think that it is possible to do something similar in Perl (the language 
in which dh_octave_check is written) by using the %SIG hash. I will take 
a look at it.


Best,

Rafael

Bug#1059163: cpio: Path traversal vulnerability

[Aníbal Monsalve Salazar]

On Wed, 2023-12-20 19:55:30 +0100, Ingo Brückl wrote:
> Package: cpio
> Version: 2.13+dfsg-7.1
> Severity: grave
> 
> The patch "revert-CVE-2015-1197-handling" (to close bugs #946267 and #946469)
> re-enables path traversal vulnerability with maliciously crafted cpio 
> archives.

Hello Ingo,

I have been working on a new Debian version of cpio for the last couple
of days. I hope to upload it today. I will appreciate it very much if
you could give it a try after uploading it.

Thank you for your previous messages related to this security
vulnerability.

I will send those messages to Salvatore.

Kind regards,

Aníbal

Bug#1059245: gdm3: GDM3 fails to start on Wayland, maybe due to org.freedesktop.systemd1 failing to activate

[Olivier Mehani]

Package: gdm3
Version: 45.0.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

GDM3 doesn't seem to be able to start a Wayland session (nor a fallback Xorg 
session, but I'm less concerned about this, and this seems to be a 
separate permission issue). This seems to be related to 
org.freedesktop.systemd1 failing to activate (and triggering the 
fallback to Xorg).

The smoking gun implicating org.freedesktop.systemd1 is

  déc. 22 03:17:17 desktop gdm-launch-environment][28769]: 
pam_unix(gdm-launch-environment:session): session opened for user 
Debian-gdm(uid=113) by (uid=0)
  déc. 22 03:17:17 desktop /usr/libexec/gdm-wayland-session[28792]: 
dbus-daemon[28792]: [session uid=113 pid=28792] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=113 pid=28785 
comm="/usr/libexec/gdm-wayland-session dbus-run-session ")
  déc. 22 03:17:17 desktop /usr/libexec/gdm-wayland-session[28792]: 
dbus-daemon[28792]: [session uid=113 pid=28792] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  déc. 22 03:17:17 desktop /usr/libexec/gdm-wayland-session[28785]: Unable to 
register display with display manager
  déc. 22 03:17:17 desktop gdm-launch-environment][28769]: 
pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm

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

   * What led up to the situation?

Rebooting the machine after a long uptime and some updates. This was 
with gdm3-43 on bookworm; the same is observed after installing gdm3-45 from 
testing.

libgdm1:amd64 (43.0-3) was updated on 2023-10-10 via unattended 
upgrades, but the system successfully rebooted a few times since then.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

* Re-rebooting the machine.
* Making sure that the the system was not in degraded mode according to systemd 
(systemctl stop and systemctl reset-failed).
* Configuring the Wi-Fi network with nmcli (in addition to pre-existing 
functional ethernet connectivity, just in case some network dependency blocked 
the org.freedesktop.systemd1 activatio)
* Installing gdm3-45 from testing

   * What was the outcome of this action?

Nothing fixed the issue.

   * What outcome did you expect instead?

Getting a graphical login prompt.

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


-- System Information:
Debian Release: 12.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-15-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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 gdm3 depends on:
ii  accountsservice   22.08.8-6
ii  adduser   3.134
ii  dbus [default-dbus-system-bus]1.14.10-1~deb12u1
ii  dbus-bin  1.14.10-1~deb12u1
ii  dbus-daemon   1.14.10-1~deb12u1
ii  dconf-cli 0.40.0-4
ii  dconf-gsettings-backend   0.40.0-4
ii  debconf [debconf-2.0] 1.5.82
ii  gir1.2-gdm-1.045.0.1-1
ii  gnome-session [x-session-manager] 43.0-1+deb12u1
ii  gnome-session-bin 43.0-1+deb12u1
ii  gnome-session-common  43.0-1+deb12u1
ii  gnome-settings-daemon 43.0-4
ii  gnome-shell   43.9-0+deb12u1
ii  gnome-terminal [x-terminal-emulator]  3.46.8-1
ii  gsettings-desktop-schemas 43.0-1
ii  libaccountsservice0   22.08.8-6
ii  libaudit1 1:3.0.9-1
ii  libc6 2.36-9+deb12u3
ii  libcanberra-gtk3-00.30-10
ii  libcanberra0  0.30-10
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libgdm1   45.0.1-1
ii  libglib2.0-0  2.78.3-1
ii  libglib2.0-bin2.78.3-1
ii  libgtk-3-03.24.38-2~deb12u1
ii  libgudev-1.0-0237-2
ii  libkeyutils1  1.6.3-2
ii  libpam-modules1.5.2-6+deb12u1
ii  libpam-runtime1.5.2-6+deb12u1
ii  libpam-systemd [logind]   252.19-1~deb12u1
ii  libpam0g  1.5.2-6+deb12u1
ii  librsvg2-common   2.54.7+dfsg-1~deb12u1
ii  libselinux1   3.4-1+b6
ii  libsystemd0   252.19-1~deb12u1
ii  libx11-6  2:1.8.4-2+deb12u2
ii  libxau6   1:1.0.9-1
ii  libxcb1   1.15-1
ii  libxdmcp6 

Bug#1057421: marked as done (sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp))

[Debian Bug Tracking System]

Your message dated Fri, 22 Dec 2023 01:22:18 +
with message-id 
and subject line Bug#1057421: fixed in sysstat 12.6.1-1.1
has caused the Debian Bug report #1057421,
regarding sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) 
"debian/tmp/lib/systemd/" (tried in ., debian/tmp)
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.)


-- 
1057421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysstat
Version: 12.6.1-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught before making the change; we'd
like to apologize.

FTBFS log snippet:
>> if [ -n "/usr/lib/systemd/system" -a -n "/usr/lib/systemd/system-sleep" -a 
>> -d "/<>/debian/tmp/usr/lib/systemd/system-sleep" ]; then \
>>  install -m 755 cron/sysstat.sleep 
>> /<>/debian/tmp/usr/lib/systemd/system-sleep; \
>> fi
>> make[2]: Leaving directory '/<>'
>> mv /<>/debian/tmp/usr/bin/sar 
>> /<>/debian/tmp/usr/bin/sar.sysstat
>> mv /<>/debian/tmp/usr/share/man/man1/sar.1 
>> /<>/debian/tmp/usr/share/man/man1/sar.sysstat.1
>> rm -rf /<>/debian/tmp/usr/doc
>> make[1]: Leaving directory '/<>'
>>dh_install
>> dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" 
>> (tried in ., debian/tmp)
>> 
>> dh_install: warning: sysstat missing files: debian/tmp/lib/systemd/
>> dh_install: error: missing files, aborting
>> make: *** [debian/rules:23: binary] Error 25
>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
>> status 2


It seems likely you'll need to adapt a debhelper .install file for
the /usr path.

Note: if you intend to backport your package to bookworm or earlier,
please revert any changes for moving to /usr.

Best,
Chris



sysstat_12.6.1-1.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sysstat
Source-Version: 12.6.1-1.1
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated sysstat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 15 Dec 2023 01:23:13 +0100
Source: sysstat
Architecture: source
Version: 12.6.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda 
Changed-By: Chris Hofstaedtler 
Closes: 1057421
Changes:
 sysstat (12.6.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS after systemdsystemunitdir changed in systemd.pc
 (Closes: #1057421)
Checksums-Sha1:
 3ff803276a6d270679e8cc3b9729972fc3b70eed 2011 sysstat_12.6.1-1.1.dsc
 cf2434b8e5b3fd53998dfbdc7325dc7411918cd2 37036 sysstat_12.6.1-1.1.debian.tar.xz
 0843f7c1278d20cb9390a40af5be22c6e6ac3660 6822 
sysstat_12.6.1-1.1_arm64.buildinfo
Checksums-Sha256:
 bdb95eca51e029b6d1b22f193a1ebf8ed08f659a6d4ed28250125f6fac0c 2011 
sysstat_12.6.1-1.1.dsc
 6fb2605dd7c7e2b6bd2a85cd7992c57f208be8d5ffaad47068c943b27eddeeca 37036 
sysstat_12.6.1-1.1.debian.tar.xz
 01c5028b726394593071d1da54e3e7cd41c83510b4e140c9aaac362da10a2d00 6822 
sysstat_12.6.1-1.1_arm64.buildinfo
Files:
 9223e2a410fb331c5c2cea256237e289 2011 admin optional sysstat_12.6.1-1.1.dsc
 30a978dc8e0fc71a4603ab8b901f4e65 37036 admin optional 
sysstat_12.6.1-1.1.debian.tar.xz
 638026c2565ada5640916ae2899ed817 6822 admin optional 
sysstat_12.6.1-1.1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmV7nM4ACgkQXBPW25MF
LgMHDA//XL2vIhTcE/2dMVCHQvsBdIU4+5USI9aMH2ABkuB+atY5/rnYlEleOdGW
zyTVlH71d/wmadmQpstjaERpEACtmCfUvIUiU/GqlivXX2ethzOm1opx4EEaWwxV
JzAf5UW1AzzwDLUEUHwIxMoPs0R8qpWLsvnHvs590ucTTp+WIlyaNLk0qaRH2qxF
HHKLjXRe2QarQWxjaRsiKJY/aLfCTMlc4oOyYP52V0MnFcxNXOrV22KzAVqd6K+K
mdjdsGKnD4crvkdG1KWsq9GchwzWAXXFZbL9u4ByFsdvrt8wXbVF9+HZ9Mtmfvvr

Bug#999937: marked as done (tup: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Fri, 22 Dec 2023 00:38:13 +
with message-id 
and subject line Bug#37: fixed in tup 0.7.11-4
has caused the Debian Bug report #37,
regarding tup: depends on obsolete pcre3 library
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.)


-- 
37: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tup
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: tup
Source-Version: 0.7.11-4
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated tup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 22 Dec 2023 01:11:31 +0100
Source: tup
Architecture: source
Version: 0.7.11-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 37 1030553
Changes:
 tup (0.7.11-4) unstable; urgency=medium
 .
   * QA upload.
   * Drop emacs integration which fails the build.
   * Build with pcre2. (Closes: #37)
 .
   [ Helge Deller ]
   * Fix ftbfs on hppa. (Closes: #1030553)
Checksums-Sha1:
 e8923d501e3e222dfda6359fd3e5d45c227303ea 1786 tup_0.7.11-4.dsc
 de54d1e053f9621560ec561a95fea54cc286667c 11680 tup_0.7.11-4.debian.tar.xz
 382e2db789a895b6855739ab732a437d074f5881 5992 tup_0.7.11-4_source.buildinfo
Checksums-Sha256:
 eb38a649fe1c08ac29018ba2b2840668c6981829ea4e184f34be1aab0a3da27b 1786 
tup_0.7.11-4.dsc
 275e1d3a8a4ce7deaa06ce568a54c5f0ffef1b076b047ca68ebb543e947c8e30 11680 
tup_0.7.11-4.debian.tar.xz
 2b9ee47f9b6588beb57784ed3aedd98970b03068d26cea983bf9eacc93373697 5992 
tup_0.7.11-4_source.buildinfo
Files:
 9bc22798ec379a97c88ed7a38a1c9b32 1786 devel optional tup_0.7.11-4.dsc
 1da71158e9a5a019939b2452f61eb2ff 11680 devel optional 
tup_0.7.11-4.debian.tar.xz
 def9865a85a826ab2d545b7714f0418c 5992 devel optional 
tup_0.7.11-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmWE1+sQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPJcDACrcQkHfPs2PbRgkRg6z/atVMMYGT/0VpbP
ER1EEJD47+fmXZAWc+KP+2Bw1CMvVHvojsEWhcseLO1tt67JXhkuLi6MCLWNk8GB
DGTF5QR5Z9zmOA922Z/vWV//4OFckTu1BYaFqncz1ZhXzdUfc+kDVgoPe6T6U10y
XVe4Z9piDn2Sb0ciK0JFwW/FQqYTBFEkHGdg1+a+RUOPzTmNEDf7yMwk289dn1mv
0S/d1FO0DUFPvrWTJtkXZTIRHhPE0zHkY/ExU4RfGoDjLde89rLwMXwR7hsupLR8
rQ83nQyRvVnZGsIVKRxdco6L3mGYUPwGLcS3ToqAYi6HAahKfUyaLeil3ASG3tB0
4hQmDAQMGYpN8qVLF6DKMDyvIyQpujQ5qKglfJAwFWHAMymOvk0SX0i+jS/GZ3jp
AFinHqq784N52BoHBMyUOqt5oSBiSXiZZXoJ/l0s0Kzc9lRH6IXPQYcHnzCZO5dc
7tYo7IEkHDy1nJuuZoIk0t9uvFuj9rs=
=Fpr7
-END PGP SIGNATURE End Message ---

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Gregor Riepl]

Hi Carsten,


I can see that 3.0.1 is currently in experimental, but it would be enough to
upgrade to the latest 2.x to fix this issue.


this makes not really sense to me. Flask 3.0.0 and Werkzeug 3.0.0 was
released on 09-30-2023, so almost three months before. Putting energy
into Flask 2.3.5 and fix other related packages while 3.x is on the way
is a waste of time in my eyes as we would need to work at least twice on
some packages...


Absolutely!

My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit 
for release, it should be enough to upgrade to 2.3.5 to address these 
unit test failures.



flask-login got recent updates which so far I've seen will fix these
issues in the test suite. So if you want to push things further try to
update/patch flask-login to a recent version targeting experimental.
Just rebuilding flask-login against the version of python3-werkzeug in
experimental will not fix the problems, so also not an intermediate
update to 2.3.5, Python 3.12 is now very strict about deprecation
warnings.


That doesn't make any sense to me. These deprecations are obviously in 
werkzeug and not flask-login. Why would changes in flask-login fix them?


Not saying flask-login shouldn't be updated, but that's not the right 
scope for this bug report.


Regards,
Gregor

Bug#1055733: marked as done (pytango ftbfs with Python 3.12 (test failures))

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 22:10:36 +
with message-id 
and subject line Bug#1055733: fixed in pytango 9.5.0-1~exp1
has caused the Debian Bug report #1055733,
regarding pytango ftbfs with Python 3.12 (test failures)
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.)


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

Package: src:pytango
Version: 9.4.2-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12


[...]
Can't create notifd event supplier. Notifd event not available
=== short test summary info 


FAILED tests/test_event.py::test_subscribe_change_event[Asyncio]
FAILED tests/test_event.py::test_subscribe_data_ready_event[Asyncio]
FAILED tests/test_event.py::test_subscribe_interface_event[Asyncio]
FAILED tests/test_event.py::test_push_event_with_timestamp[Asyncio]
FAILED 
tests/test_event.py::test_subscribe_change_event_from_user_thread[Asyncio]

FAILED tests/test_server.py::test_empty_device[Asyncio]
FAILED tests/test_server.py::test_set_state[ON-Asyncio]
FAILED tests/test_server.py::test_set_state[OFF-Asyncio]
FAILED tests/test_server.py::test_set_state[CLOSE-Asyncio]
FAILED tests/test_server.py::test_set_state[OPEN-Asyncio]
FAILED tests/test_server.py::test_set_state[INSERT-Asyncio]
FAILED tests/test_server.py::test_set_state[EXTRACT-Asyncio]
FAILED tests/test_server.py::test_set_state[MOVING-Asyncio]
FAILED tests/test_server.py::test_set_state[STANDBY-Asyncio]
FAILED tests/test_server.py::test_set_state[FAULT-Asyncio]
FAILED tests/test_server.py::test_set_state[INIT-Asyncio]
FAILED tests/test_server.py::test_set_state[RUNNING-Asyncio]
FAILED tests/test_server.py::test_set_state[ALARM-Asyncio]
FAILED tests/test_server.py::test_set_state[DISABLE-Asyncio]
FAILED tests/test_server.py::test_set_state[UNKNOWN-Asyncio]
FAILED tests/test_server.py::test_user_dev_state_status[Asyncio]
FAILED tests/test_server.py::test_set_status[Asyncio]
FAILED tests/test_server.py::test_attr_quality_checked_with_state[Asyncio]
FAILED tests/test_server.py::test_identity_command[int-Asyncio]
FAILED tests/test_server.py::test_identity_command[float-Asyncio]
FAILED tests/test_server.py::test_identity_command[str-Asyncio]
FAILED tests/test_server.py::test_identity_command[bool-Asyncio]
FAILED tests/test_server.py::test_identity_command[(int,)-Asyncio]
FAILED tests/test_server.py::test_identity_command[(float,)-Asyncio]
FAILED tests/test_server.py::test_identity_command[(str,)-Asyncio]
FAILED tests/test_server.py::test_decorated_command[Asyncio]
FAILED tests/test_server.py::test_command_isallowed[Asyncio]
FAILED tests/test_server.py::test_dynamic_command[Asyncio-True]
FAILED tests/test_server.py::test_dynamic_command[Asyncio-False]
FAILED tests/test_server.py::test_polled_command[Asyncio]
FAILED tests/test_server.py::test_wrong_command_result[Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[int-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[float-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[str-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[bool-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[(int,)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[(float,)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[(str,)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[(bool,)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[((int,),)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[((float,),)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[((str,),)-Asyncio]
FAILED tests/test_server.py::test_read_write_attribute[((bool,),)-Asyncio]
FAILED 
tests/test_server.py::test_read_write_attribute_with_unbound_functions[Asyncio]
FAILED 
tests/test_server.py::test_read_write_attribute_decorated_methods[Asyncio]

FAILED tests/test_server.py::test_read_write_wvalue_attribute[int-Asyncio]
FAILED tests/test_server.py::test_read_write_wvalue_attribute[float-Asyncio]
FAILED tests/test_server.py::test_read_write_wvalue_attribute[str-Asyncio]
FAILED tests/test_server.py::test_read_write_wvalue_attribute[bool-Asyncio]
FAILED 
tests/test_server.py::test_read_write_wvalue_attribute[(int,)-Asyncio]
FAILED 
tests/test_server.py::test_read_write_wvalue_attribute[(float,)-Asyncio]
FAILED 
tests/test_server.py::test_read_write_wvalue_attribute[(str,)-Asyncio]
FAILED 

Bug#1057862: marked as done (pytango ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 22:10:36 +
with message-id 
and subject line Bug#1055733: fixed in pytango 9.5.0-1~exp1
has caused the Debian Bug report #1055733,
regarding pytango ftbfs with Python 3.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.)


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

Package: src:pytango
Version: 9.4.2-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pytango fails hundreds of tests with Python 3.12

see
https://buildd.debian.org/status/fetch.php?pkg=pytango=amd64=9.4.2-1%2Bb2=1702122194=0
--- End Message ---
--- Begin Message ---
Source: pytango
Source-Version: 9.5.0-1~exp1
Done: Santiago Ruano Rincón 

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

Debian distribution maintenance software
pp.
Santiago Ruano Rincón  (supplier of updated pytango 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Dec 2023 18:24:21 -0300
Source: pytango
Architecture: source
Version: 9.5.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Santiago Ruano Rincón 
Closes: 1049843 1055733
Changes:
 pytango (9.5.0-1~exp1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream version 9.5.0
 * Fix FTBFS with Python 3.12 (Closes: #1049843, #1055733). Although, it
   builds for the default python version only.
   * Add d/gbp.conf
   * Set RELEASE to experimental in debian/salsa-ci.yml
   * Add and/or update Build-Depends: cmake, libboost-python-dev (>= 1.83.0),
 tango >= 9.5.0, pybuild-plugin-pyproject, python3-pathspec,
 python3-pyproject-metadata and python3-scikit-build-core
   * Update d/patches/0002-Added-gevent-to-instal_requires.patch and
 remove-junitxml-report.patch to use pyproject.toml
   * Update debian/patches/ftbfs-ipv6.patch
Checksums-Sha1:
 0a5fd2f38f4b66593ca05dd6fbc6233faeb060b9 2263 pytango_9.5.0-1~exp1.dsc
 08a2e7f144cb6b604739cfe8ccb569e39d489395 4980756 pytango_9.5.0.orig.tar.gz
 6acf8ebaacdd7983c10e751db660796b1b22056e 13624 
pytango_9.5.0-1~exp1.debian.tar.xz
 bee5947fe3021e676cec3a2dbe70755b812a6643 13123 
pytango_9.5.0-1~exp1_amd64.buildinfo
Checksums-Sha256:
 7a1d3f9393f53d801386b3e77319fdf20c153640c17f926618bf00bfe3723c28 2263 
pytango_9.5.0-1~exp1.dsc
 559cb367c8f336c382cfcc3fb86a523a599c6f01d00bc9ad89ca7a363793182c 4980756 
pytango_9.5.0.orig.tar.gz
 ffa2b5f5e360cde3820f2dd944789e71e2a1dbb187db123ffd03ede7b1b71ec3 13624 
pytango_9.5.0-1~exp1.debian.tar.xz
 c734da6147e5722cac709b2c0b9ae9780c56ff780cc5606091ffeec104c86a13 13123 
pytango_9.5.0-1~exp1_amd64.buildinfo
Files:
 2bc81d9b2d7832b708058fe201088852 2263 science optional pytango_9.5.0-1~exp1.dsc
 259172ed22fa958bc52cdd47a92d9385 4980756 science optional 
pytango_9.5.0.orig.tar.gz
 52d2f9a961583d413ee96e689541bdc6 13624 science optional 
pytango_9.5.0-1~exp1.debian.tar.xz
 79d8885ec54f39899e3e1c8d18bc3672 13123 science optional 
pytango_9.5.0-1~exp1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCZYS1eQAKCRBitBCJKh26
HXpEAP95EJEFpnhAb7KUlM5cXOSBLAwk6BaQTDNlwtRUnjgmPwEAhe4OC6dtpO/D
jXpNz5zuq/d0dJukFwbeJzHhhZvrXgs=
=QDCd
-END PGP SIGNATURE End Message ---

Bug#1000010: marked as done (ohcount: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 22:09:28 +
with message-id 
and subject line Bug#110: fixed in ohcount 4.0.0-4
has caused the Debian Bug report #110,
regarding ohcount: depends on obsolete pcre3 library
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.)


-- 
110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ohcount
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: ohcount
Source-Version: 4.0.0-4
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated ohcount package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Dec 2023 22:11:19 +0100
Source: ohcount
Architecture: source
Version: 4.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Sylvestre Ledru 
Changed-By: Sylvestre Ledru 
Closes: 110
Changes:
 ohcount (4.0.0-4) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository.
 .
   [ Sylvestre Ledru ]
   * Depends on obsolete pcre3 library (Closes: #110)
 Thanks to Yavor Doganov for the patch
Checksums-Sha1:
 f4f9cf1b4c5cb2c194c49644d3bea6d22275721e 2009 ohcount_4.0.0-4.dsc
 c67ed84e9224348eaf19f956429b247e5622ab14 14292 ohcount_4.0.0-4.debian.tar.xz
 37fbe06ba1d99cac02356146f24ff020bc68b121 10083 ohcount_4.0.0-4_amd64.buildinfo
Checksums-Sha256:
 7e88ed55af6110a3b1bacb893dad1fd1cc149c6b93ef449c3da49682403455a6 2009 
ohcount_4.0.0-4.dsc
 a04b692b8002bc031cedcd93d524288bfb9130db3ed23790295b52a3ed1832c5 14292 
ohcount_4.0.0-4.debian.tar.xz
 eff6bbb2cf566a903ebc72598ceff8c920cc448c71e027b3d784f17c1db79bfe 10083 
ohcount_4.0.0-4_amd64.buildinfo
Files:
 c171380be8f7a6e5432da83580b4371c 2009 utils optional ohcount_4.0.0-4.dsc
 60715895c55e29e82469518a2227a2d0 14292 utils optional 
ohcount_4.0.0-4.debian.tar.xz
 b0a8b1d580fc4a62a49ff53883339c0b 10083 utils optional 
ohcount_4.0.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmWErQQACgkQfmUo2nUv
G+GQ/Q//dD8wezay+vOmfF8zamGhltAalb3eNNNz5li0pX/t/o+jlmjFHm05gm4g
e2XrqSak9QjouQMKMTmfAaQqbZ0kfWaIrSn3NJe1ldSAajnm2aQq5o72kSXQsy+L
urBgvBHMlLvAb51KlWGrXrHuRhwUZuH0KNAkto0RB0+/w8S+A00JuoRuzB9yUjFr
YcEF/X7wzLxUrdKsc2RylhZaVrwG5j5k97njGZcnAZz0hvYYDkwpLVe8jMe9Vmgc
6c6oqPltjb1QRSxisFVBYYVqw5+JkldXb6cq5h7pCNhXqL0Ga8pge0MZbAU3fN9w
cYhCWS+UOJOX5h4CS4I1qq5C38pPxt2EytqrXTAckegi85ovBUU8pLhHZUTz4wCA
sc+CUQJQFbi+/7q2DjogWBwoQi/M1lL3e8PVeduNnIB6OZJHILBa0eD0dgql2+Su
DhRxNv+9jsA2ucdUjmumvW04hvHcF1ro1ulB0PEJzgBQU/25Dtm55b1aw0Rci0st
cqzAWr5qtU3sNUd/jfRxrnECIMTAvB+Casx9pyvXWxVoswvngoR8ug3iHp58nZ08
oMZ+UOy2QcR/EiWhSgzfKBLg5dRXRZS5UvOS0JsI7Yt5MRqkolXo2hB+721jmkS5
4DVhFLYCjunr1cSjxKWpXqlYa9UHQi0r+7/Vn3zE7nDH5FHn2JU=
=rbzN
-END PGP SIGNATURE End Message ---

Bug#1056080: marked as done (flightcrew: FTBFS: boost1.83 transition)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 22:05:13 +
with message-id 
and subject line Bug#1056080: fixed in flightcrew 0.9.3+dfsg-2
has caused the Debian Bug report #1056080,
regarding flightcrew: FTBFS: boost1.83 transition
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.)


-- 
1056080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flightcrew
Version: 0.9.3+dfsg-1
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition

Hi,

we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.

Relevant part (hopefully):

-

/<>/src/FlightCrew/Validators/SaxSchemaValidator.cpp:38:12: error: 
‘scoped_ptr’ is not a member of ‘boost’; did you mean ‘shared_ptr’?
   38 | boost::scoped_ptr< xc::SAX2XMLReader > parser( 
xc::XMLReaderFactory::createXMLReader() );
  |^~
  |shared_ptr



-

To reproduce this behavior, you can install  -dev Boost packages from the
experimental repository, as shown in the following command:

  apt install libboost-dev -t experimental


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/flightcrew_0.9.3+dfsg-1_unstable_boost181.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-boost183-transition;users=gl...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-boost183-transition=gl...@debian.org=1=1=1=1#results

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the 
meantime.
--- End Message ---
--- Begin Message ---
Source: flightcrew
Source-Version: 0.9.3+dfsg-2
Done: Francois Mazen 

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

Debian distribution maintenance software
pp.
Francois Mazen  (supplier of updated flightcrew 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: Wed, 20 Dec 2023 21:01:55 +0100
Source: flightcrew
Architecture: source
Version: 0.9.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Mazen 
Changed-By: Francois Mazen 
Closes: 1056080
Changes:
 flightcrew (0.9.3+dfsg-2) unstable; urgency=medium
 .
   [ Francois Mazen ]
   * Fix FTBS with Boost 1.83 (Closes: #1056080)
   * Update missing-sources with some xhtml data
   * Bump standard version to 4.6.2
   * Flag patch forwarding as not-needed because upstream code have been 
archived
 .
   [ Mattia Rizzolo ]
   * Build with -D_FORTIFY_SOURCE=2
   * Bump debhelper compat level to 13
   * Drop explicit dh_missing --fail-missing
Checksums-Sha1:
 5e1966f64a611d0e2ccb02d72af7f187c522d8eb 2395 flightcrew_0.9.3+dfsg-2.dsc
 007e7108be96a7de7aa48f47bdaa7849de9ccd14 16436 
flightcrew_0.9.3+dfsg-2.debian.tar.xz
 4291316ba696debff96c170b1885b7c5bb7abff4 13678 
flightcrew_0.9.3+dfsg-2_source.buildinfo
Checksums-Sha256:
 f143334a20aa73bfc5e9abd0b780b0d06ee92605382b8bbe3d8a6793ca266ce8 2395 
flightcrew_0.9.3+dfsg-2.dsc
 5e1232e1ae7c90b9486a9a2b01bf9921f7f555c18cbba34167f5695a76149307 16436 
flightcrew_0.9.3+dfsg-2.debian.tar.xz
 d3bd1cc0fafa94ffb8ea26d5c33700c422a645023b48013a44d4e619abd3b3fc 13678 
flightcrew_0.9.3+dfsg-2_source.buildinfo
Files:
 6602c89cbc38ab15549c65f105da4801 2395 text optional flightcrew_0.9.3+dfsg-2.dsc
 55892f5908c3064d09e383b9fa774253 16436 text optional 
flightcrew_0.9.3+dfsg-2.debian.tar.xz
 c5239c9ccda3a429718eda4e3c9740c5 13678 text optional 
flightcrew_0.9.3+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEhqWr1v/bCgx/UFfTR5f6chw1HJ4FAmWErYUPHG16ZkBkZWJp
YW4ub3JnAAoJEEeX+nIcNRyeoBEQAItI/R5TASe8QMLh4sR++KcSQ7VIob0+HLXF

Bug#1058937: /usr-move: Do we support upgrades without apt?

[David Kalnischkies]

On Thu, Dec 21, 2023 at 02:42:56PM +, Matthew Vernon wrote:
> On 21/12/2023 09:41, Helmut Grohne wrote:
> > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > using apt unsupported until we no longer deal with aliasing?
> 
> I incline towards "no"; if an upgrade has failed part-way (as does happen),
> people may then reasonably use dpkg directly to try and un-wedge the upgrade
> (e.g. to try and configure some part-installed packages, or try installing
> some already-downloaded packages).

You can configure half-installed packages, no problem, this is about
unpacking (which is the first step in an install, where only Conflicts
and Pre-Depends matter, if you are not deep into dpkg vocabulary)


The "try installing" part is less straight forward. In general, you
are running into dpkg "features" (e.g. not handling pre-depends) or
into dpkg bugs (e.g. #832972, #844300): In the best case your system
state became a bit worse and hence harder to "un-wedge". In the worst
case a maintainer script has run amok as nobody tested this.
But yeah, most of the time you will indeed be lucky and hence come to
the unreasonable conclusion that its reasonable to call dpkg directly.


Anyway, if your upgrade failed part-way, you are probably in luck given
that its more likely the upgrade failed in unpack/configure than in
removal – so if you aren't too eager to install more packages by hand
but limit yourself to e.g. (re)installing the ones who failed you are
fine as apt will have removed the conflictors already for you (or
upgraded them, if that can resolve the conflict).


But lets assume you are not:
As you are driving dpkg by hand you also have the time to read what it
prints, which in the problematic case is (as exampled by #1058937):
| dpkg: considering removing libnfsidmap-regex:amd64 in favour of 
libnfsidmap1:amd64 ...
| dpkg: yes, will remove libnfsidmap-regex:amd64 in favour of libnfsidmap1:amd64
(and the same for libnfsidmap2:amd64 as well. If your terminal supports
 it parts of these messages will be in bold)

Note that the similar "dpkg: considering deconfiguration of …" which is
the result of Breaks relations is not a problematic case.

(Also note that this exact situation is indeed another reason why
 interacting with dpkg by hand is somewhat dangerous as you might not
 expect packages to be removed from your system while you just told
 dpkg to unpack something… just remember that the next time you happen
 to "dpkg -i" some random deb file onto your system.)

That is of course no hint that a file might have been lost due to
aliasing if you don't know that this could be the case, but on the
upside it is not entirely a silent file lose situation either. We could
write something in the release notes if someone happens to read them AND
also encounters this message.


Query your memory: Did you encounter this message before? Nothing in
the /usr merge plan makes that particularly more likely to be encountered
for a user and not all of the encounters will actually exhibit the file
lose. So if you haven't – and I would argue that most people haven't –
there is a pretty good chance you wont have a problem in the future
either…


So, in summary: Yes, there are theoretic relatively easy ways to trigger
it with dpkg directly. That isn't the question. The question is if a real
person who isn't actively trying to trigger it is likely to run into it
by accident (and/or if such a person can even reasonably exist) so that
we have to help them by generating work for many people and potentially
new upgrade problems for everyone – or if we declare them, existing or
not, a non-issue at least for the upgrade to trixie.


And on a sidenote: I would advise to reconsider interacting with dpkg
too casually – but luck is probably on your side in any case.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#1000010: ohcount: depends on obsolete pcre3 library

[Sylvestre Ledru]

oh, cool, thanks :)

I will upload it /i/n a second


Le 21/12/2023 à 21:33, Yavor Doganov a écrit :

Control: tags -1 + patch

Please find a patch attached.

Bug#1058937: /usr-move: Do we support upgrades without apt?

[David Kalnischkies]

On Thu, Dec 21, 2023 at 03:31:55PM +0100, Marc Haber wrote:
> On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote:
> > On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> > > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > > using apt unsupported until we no longer deal with aliasing?
> > 
> > I think so, yes. I don't think it's likely that there are people doing
> > upgrades on running systems not using apt.
> 
> Do those GUI frontends that work via packagekit or other frameworks
> count as "using apt"?

I explained that in full detail in my mail to the pause-thread:
https://lists.debian.org/debian-devel/2023/12/msg00039.html

In short: helmuts "apt" (my "APT") includes everything that uses libapt.
That is apt, apt-get, python-apt, aptitude, synaptics, everything based
on packagekit, …

I know of only cupt and dselect which don't count, but I have some
suspicion that they would work anyhow. IF you don't run into other
problems with them, like that they do not implement Multi-Arch.


So this thread is really about:
How much are people REALLY fiddling with dpkg directly in an upgrade
and can we just say its unsupported – because, at least that is my view,
in practice nobody does it and its therefore also completely untested.

Case in point: We have this thread not because someone found it while
working with dpkg directly even through they had potentially years, but
because Helmut ended up triggering an edge case in which apt interacts
with dpkg in this way and only after that people looked for how to
trigger it with dpkg because triggering it with apt is hard (= as Helmut
checked, no package (pair) in current unstable is known to exhibit the
required setup).

(I will write another mail in another subthread about the finer details
 of what interacting with dpkg in an upgrade means and what might be
 problematic if you aren't careful – in general, not just with aliasing)


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#1000010: ohcount: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find a patch attached.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/110
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2023-12-21
---

--- ohcount-4.0.0.orig/build
+++ ohcount-4.0.0/build
@@ -31,7 +31,7 @@
   # You shouldn't have to change the following.
   CFLAGS="-fno-common -g"
   WARN="-Wall -Wno-parentheses"
-  SHARED="-dynamiclib -L$LIB_DIR -lpcre"
+  SHARED="-dynamiclib -L$LIB_DIR -lpcre2-8"
   SHARED_NAME=libohcount.dylib
   RB_SHARED="-dynamic -bundle -lruby"
   RB_SHARED_NAME=ohcount.bundle
@@ -97,7 +97,7 @@
   build_parser_o
   echo "Building Ohcount"
   mkdir -p bin/
-  sh -c "$cc src/ohcount.c $files -o bin/ohcount -lpcre -lmagic" || exit 1
+  sh -c "$cc src/ohcount.c $files -o bin/ohcount -lpcre2-8 -lmagic" || exit 1
 }
 
 build_test_suite()
@@ -105,7 +105,7 @@
   build_hash_headers
   build_parser_o
   echo "Building test suite"
-  sh -c "$cc test/unit/all_tests.c $files -o test/unit/run_tests -lpcre 
-lmagic" \
+  sh -c "$cc test/unit/all_tests.c $files -o test/unit/run_tests -lpcre2-8 
-lmagic" \
 || exit 1
 }
 
@@ -127,10 +127,10 @@
mkdir -p ruby/$arch
 echo $cc $RB_SHARED ruby/ohcount_wrap.c $files -o 
ruby/$arch/$RB_SHARED_NAME \
 -I$RUBY_HEADER_DIR -I$RUBY_CONFIG_DIR  
-I/usr/include/$rbconfig_arch/ruby-$RUBY_VERSION  \
--lpcre -lmagic
+-lpcre2-8 -lmagic
   sh -c "$cc $RB_SHARED ruby/ohcount_wrap.c $files -o 
ruby/$arch/$RB_SHARED_NAME \
 -I$RUBY_HEADER_DIR -I$RUBY_CONFIG_DIR  
-I/usr/include/$rbconfig_arch/ruby-$RUBY_VERSION  \
--lpcre -lmagic" || exit 1
+-lpcre2-8 -lmagic" || exit 1
   sh -c "cd test/unit/ruby && ruby ruby_test.rb" || exit 1
 }
 
--- ohcount-4.0.0.orig/src/structs.h
+++ ohcount-4.0.0/src/structs.h
@@ -4,7 +4,8 @@
 #ifndef OHCOUNT_STRUCTS_H
 #define OHCOUNT_STRUCTS_H
 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 
 /**
  * @struct License
@@ -24,7 +25,7 @@
   const char *re;
 
   /** PCRE flags for re. (Typically PCRE_CASELESS or PCRE_MULTILINE). */
-  int re_flags;
+  uint32_t re_flags;
 
   /**
* A PCRE regular expression for text that matches re, but should not match
@@ -33,13 +34,13 @@
   const char *exclude_re;
 
   /** PCRE flags for exclude_re. */
-  int exclude_re_flags;
+  uint32_t exclude_re_flags;
 
   /** The PCRE object for re. (This field is set automatically.) */
-  pcre *regexp;
+  pcre2_code *regexp;
 
   /** The PCRE object for exclude_re. (This field is set automatically.) */
-  pcre *exclude_regexp;
+  pcre2_code *exclude_regexp;
 
 } License;
 
--- ohcount-4.0.0.orig/src/detector.c
+++ ohcount-4.0.0/src/detector.c
@@ -889,7 +889,8 @@
   return NULL; // only blanks
 }
 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 
 // strnlen is not available on OS X, so we roll our own
 size_t mystrnlen(const char *begin, size_t maxlen) {
@@ -906,24 +907,35 @@
  return NULL;
 
/* prepare regular expressions */
-   const char *error;
-   int erroffset;
+   int error;
+   PCRE2_SIZE erroffset;
 
/* try harder with optional spaces */
-   pcre *keyword;
-   keyword = 
pcre_compile("^\\s*(ensure|content|notify|require|source)\\s+=>",
-   PCRE_MULTILINE, , , NULL);
-
-   if (pcre_exec(keyword, NULL, p, mystrnlen(p, 1), 0, 0, NULL, 0) > 
-1)
+   pcre2_code *keyword;
+   pcre2_match_data *md;
+   keyword = pcre2_compile((PCRE2_SPTR)
+   
"^\\s*(ensure|content|notify|require|source)\\s+=>",
+   PCRE2_ZERO_TERMINATED, PCRE2_MULTILINE,
+   , , NULL);
+   md = pcre2_match_data_create(30, NULL);
+   if (pcre2_match(keyword, (PCRE2_SPTR)p, mystrnlen(p, 1),
+   0, 0, md, NULL) > -1) {
+   pcre2_match_data_free(md);
return LANG_PUPPET;
+   }
 
/* check for standard puppet constructs */
-   pcre *construct;
-   construct = 
pcre_compile("^\\s*(define\\s+[\\w:-]+\\s*\\(|class\\s+[\\w:-]+(\\s+inherits\\s+[\\w:-]+)?\\s*[\\({]|node\\s+\\'?[\\w:\\.-]+\\'?\\s*{|import\\s+\"|include\\s+[\"']?[\\w:-][\"']?)",
-   PCRE_MULTILINE, , , NULL);
-
-   if (pcre_exec(construct, NULL, p, mystrnlen(p, 1), 0, 0, NULL, 0) > 
-1)
+   pcre2_code *construct;
+   construct = 
pcre2_compile((PCRE2_SPTR)"^\\s*(define\\s+[\\w:-]+\\s*\\(|class\\s+[\\w:-]+(\\s+inherits\\s+[\\w:-]+)?\\s*[\\({]|node\\s+\\'?[\\w:\\.-]+\\'?\\s*{|import\\s+\"|include\\s+[\"']?[\\w:-][\"']?)",
+ PCRE2_ZERO_TERMINATED, PCRE2_MULTILINE,
+ , , NULL);
+
+   if (pcre2_match(construct, (PCRE2_SPTR)p, mystrnlen(p, 1),
+   0, 0, md, NULL) > -1) {
+   pcre2_match_data_free(md);
return LANG_PUPPET;
+   }
+   pcre2_match_data_free(md);
 
return LANG_PASCAL;
 }
@@ -934,11 +946,19 @@
 return NULL;
 
 

Processed: Re: Bug#1000010: ohcount: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #110 [src:ohcount] ohcount: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Michael Biebl]

Am 21.12.23 um 11:50 schrieb Christoph Berg:

Re: Helmut Grohne

Is it ok to call upgrade scenarios failures that cannot be reproduced
using apt unsupported until we no longer deal with aliasing?

If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
with no action calling the scenario unsupported.


I think we should only deal with problems that can reasonably happen
in practice. If an extra hammer is required to hit the problem, we
should not spend extra effort on it.


A (dist-)upgrade not using apt is very much a corner case/niche use case.

I'd be interested if #1058937 can be reproduced using aptitude, though.
While the release notes explicitly recommend using apt/apt-get, I do 
think that dist-upgrades using aptitude should not run into those file 
loss issues.


If aptitude is safe, I'd consider #1058937 a bug, that is not release 
critical and I'd assign low(er) priority to it.
Other issues, like getting all packages updated to move their files to 
/usr, have higher priority.


Michael



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054485: marked as done (postfix: installs a systemd unit twice when dh_installsystemd installs below /usr)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 19:21:31 +
with message-id 
and subject line Bug#1054485: fixed in postfix 3.8.3-1
has caused the Debian Bug report #1054485,
regarding postfix: installs a systemd unit twice when dh_installsystemd 
installs below /usr
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.)


-- 
1054485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postfix
Version: 3.8.2-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to modify dh_installsystemd such that units get installed below
/usr in order to finalize the /usr-merge transition via DEP17. When
doing so at least one unit gets installed both below /lib (via
debian/rules) and to /usr/lib (via dh_installsystemd). Doing so is a
policy violation and therefore this bug will become release-critical
once I upload debhelper. I propose installing all units using
dh_installsystemd, because bookworm's dh_installsystemd (even in
bookworm-backports) will continue to install to /lib. Doing so will
later move all units to /usr in trixie, but the generator needs a
separate change. You may use dh-sequence-movetousr, which will also be a
noop in bookworm-backports, to that end.

Helmut
diff -Nru postfix-3.8.2/debian/changelog postfix-3.8.2/debian/changelog
--- postfix-3.8.2/debian/changelog  2023-09-14 20:08:10.0 +0200
+++ postfix-3.8.2/debian/changelog  2023-10-24 11:19:42.0 +0200
@@ -1,3 +1,10 @@
+postfix (3.8.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install units using dh_installsystemd only. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 24 Oct 2023 11:19:42 +0200
+
 postfix (3.8.2-1) unstable; urgency=medium
 
   [Scott Kitterman]
diff -Nru postfix-3.8.2/debian/postfix-resolvconf.path 
postfix-3.8.2/debian/postfix-resolvconf.path
--- postfix-3.8.2/debian/postfix-resolvconf.path2023-09-14 
19:53:19.0 +0200
+++ postfix-3.8.2/debian/postfix-resolvconf.path1970-01-01 
01:00:00.0 +0100
@@ -1,11 +0,0 @@
-[Unit]
-Description=Watch for resolv.conf updates and restart postfix
-ConditionPathExists=/etc/resolv.conf
-
-[Path]
-PathChanged=/etc/resolv.conf
-Unit=postfix-resolvconf.service
-
-[Install]
-WantedBy=multi-user.target
-
diff -Nru postfix-3.8.2/debian/postfix-resolvconf.service 
postfix-3.8.2/debian/postfix-resolvconf.service
--- postfix-3.8.2/debian/postfix-resolvconf.service 2023-09-14 
19:53:19.0 +0200
+++ postfix-3.8.2/debian/postfix-resolvconf.service 1970-01-01 
01:00:00.0 +0100
@@ -1,9 +0,0 @@
-[Unit]
-Description=Copies updated resolv.conf to postfix chroot and restarts postfix.
-
-[Service]
-Type=simple
-ExecStart=/etc/resolvconf/update-libc.d/postfix
-
-[Install]
-WantedBy=multi-user.target
diff -Nru postfix-3.8.2/debian/postfix.dirs postfix-3.8.2/debian/postfix.dirs
--- postfix-3.8.2/debian/postfix.dirs   2023-09-14 19:53:19.0 +0200
+++ postfix-3.8.2/debian/postfix.dirs   2023-10-24 11:19:42.0 +0200
@@ -34,5 +34,4 @@
 var/spool/postfix/usr/lib/sasl2
 var/log
 var/lib/postfix
-lib/systemd/system
 lib/systemd/system-generators
diff -Nru postfix-3.8.2/debian/postfix.postfix-resolvconf.path 
postfix-3.8.2/debian/postfix.postfix-resolvconf.path
--- postfix-3.8.2/debian/postfix.postfix-resolvconf.path1970-01-01 
01:00:00.0 +0100
+++ postfix-3.8.2/debian/postfix.postfix-resolvconf.path2023-09-14 
19:53:19.0 +0200
@@ -0,0 +1,11 @@
+[Unit]
+Description=Watch for resolv.conf updates and restart postfix
+ConditionPathExists=/etc/resolv.conf
+
+[Path]
+PathChanged=/etc/resolv.conf
+Unit=postfix-resolvconf.service
+
+[Install]
+WantedBy=multi-user.target
+
diff -Nru postfix-3.8.2/debian/postfix.postfix-resolvconf.service 
postfix-3.8.2/debian/postfix.postfix-resolvconf.service
--- postfix-3.8.2/debian/postfix.postfix-resolvconf.service 1970-01-01 
01:00:00.0 +0100
+++ postfix-3.8.2/debian/postfix.postfix-resolvconf.service 2023-09-14 
19:53:19.0 +0200
@@ -0,0 +1,9 @@
+[Unit]
+Description=Copies updated resolv.conf to postfix chroot and restarts postfix.
+
+[Service]
+Type=simple
+ExecStart=/etc/resolvconf/update-libc.d/postfix
+
+[Install]
+WantedBy=multi-user.target
diff -Nru postfix-3.8.2/debian/rules postfix-3.8.2/debian/rules
--- postfix-3.8.2/debian/rules  2023-09-14 19:53:19.0 +0200
+++ postfix-3.8.2/debian/rules  2023-10-24 11:19:36.0 +0200
@@ -193,8 +193,6 @@
 
install debian/configure-instance.sh $(libdir)
install 

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Carsten Schoenert]

Hello Gregor,

Am Thu, Dec 21, 2023 at 02:00:40PM +0100 schrieb Gregor Riepl:
> I don't see any other errors in the log except for the ast.Str deprecation
> warnings, and they all come from python-werkezug and not this package.
> 
> Reassiging the bug.
> Upstream has already fixed this in in 2.3.5, by the way:
> https://github.com/pallets/werkzeug/issues/2704
> 
> I can see that 3.0.1 is currently in experimental, but it would be enough to
> upgrade to the latest 2.x to fix this issue.

this makes not really sense to me. Flask 3.0.0 and Werkzeug 3.0.0 was
released on 09-30-2023, so almost three months before. Putting energy
into Flask 2.3.5 and fix other related packages while 3.x is on the way
is a waste of time in my eyes as we would need to work at least twice on
some packages...

flask-login got recent updates which so far I've seen will fix these
issues in the test suite. So if you want to push things further try to
update/patch flask-login to a recent version targeting experimental.
Just rebuilding flask-login against the version of python3-werkzeug in
experimental will not fix the problems, so also not an intermediate
update to 2.3.5, Python 3.12 is now very strict about deprecation
warnings.

Regards
Carsten

Bug#1056247: marked as done (flask's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 19:05:18 +
with message-id 
and subject line Bug#1056247: fixed in flask 3.0.0-1
has caused the Debian Bug report #1056247,
regarding flask's autopkg tests fail with Python 3.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.)


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

Package: src:flask
Version: 2.2.5-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

flask's autopkg tests fail with Python 3.12:


[...]
281s -=-=-=-=-=-=-=- running tests for python3.12 -=-=-=-=-=-=-=-=-
281s $ python3.12 -m pytest -k "not test_main_module_paths" tests
282s = test session starts 
==

282s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
282s rootdir: /tmp/autopkgtest.UCcMIG/autopkgtest_tmp
282s collected 483 items
282s
282s tests/test_appctx.py .. 
 [  2%]
282s tests/test_async.py  
 [  4%]
282s tests/test_basic.py 
 [ 15%]
282s 
 
[ 30%]
282s ...F. 
 [ 32%]
283s tests/test_blueprints.py 
... [ 41%]
283s .. 
 [ 43%]
283s tests/test_cli.py 
.. [ 55%]
283s . 
 [ 55%]
283s tests/test_config.py .. 
 [ 59%]
283s tests/test_converters.py .. 
 [ 59%]
283s tests/test_helpers.py ... 
 [ 65%]
283s tests/test_instance_config.py ... 
 [ 68%]
284s tests/test_json.py ... 
 [ 74%]
284s tests/test_json_tag.py .. 
 [ 77%]
284s tests/test_logging.py .. 
 [ 78%]
284s tests/test_regression.py . 
 [ 78%]
284s tests/test_reqctx.py ...ss. 
 [ 81%]
284s tests/test_session_interface.py . 
 [ 81%]
284s tests/test_signals.py ... 
 [ 83%]
284s tests/test_subclassing.py . 
 [ 83%]
284s tests/test_templating.py  
 [ 90%]
284s tests/test_testing.py . 
 [ 95%]
284s tests/test_user_error_handler.py . 
 [ 97%]
284s tests/test_views.py . 
 [100%]

284s
284s === FAILURES 
===
284s _ test_max_cookie_size 
_

284s
284s app = , client = >
284s recwarn = WarningsRecorder(record=True)
284s
284s def test_max_cookie_size(app, client, recwarn):
284s app.config["MAX_COOKIE_SIZE"] = 100
284s
284s # outside app context, default to Werkzeug static value,
284s # which is also the default config
284s response = flask.Response()
284s default = flask.Flask.default_config["MAX_COOKIE_SIZE"]
284s assert response.max_cookie_size == default
284s
284s # inside app context, use app config
284s with app.app_context():
284s assert flask.Response().max_cookie_size == 100
284s
284s @app.route("/")
284s def index():
284s r = flask.Response("", status=204)
284s r.set_cookie("foo", "bar" * 100)
284s return r
284s
284s client.get("/")
284s >   assert len(recwarn) == 1
284s E   assert 4 == 1
284s E+  where 4 = len(WarningsRecorder(record=True))
284s
284s tests/test_basic.py:1962: AssertionError
--- End Message ---
--- Begin Message ---
Source: flask
Source-Version: 3.0.0-1
Done: Carsten Schoenert 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Dec 2023 07:22:23 +0100
Source: flask
Architecture: source
Version: 3.0.0-1
Distribution: 

Bug#1054485: postfix: diff for NMU version 3.8.2-1.1

[Scott Kitterman]

On Monday, December 18, 2023 7:31:47 PM EST Chris Hofstaedtler wrote:
> Control: tags 1054485 + patch
> Control: tags 1054485 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for postfix (versioned as 3.8.2-1.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer. Better, upload yourself in the meantime.
> 
> Best,
> Chris

Thank you for preparing this.  I've just done a maintainer upload with this 
change as well as a new upstream release. 

Scott K

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

Bug#999921: xymon: depends on obsolete pcre3 library

[Axel Beckert]

Hi Yavor,

Yavor Doganov wrote:
> Please find a patch which I've been testing for a while with no ill
> effects AFAICT.  However, I'm not familiar at all with this package so
> it's possible that I've missed something.  I also couldn't test all
> available functionality.

Thanks a lot also for that patch! I have enough servers and clients
around to test the patch. (And thanks in general that you seemingly
crawl through all these annoying PCRE3→2 bugs and provide patches.
Much appreciated!)

Upstream said, they're having it on their roadmap, too, but I haven't
seen anything in that direction yet in the upstream SVN repo. (And I'm
tracking trunk.)

So I'll also forward the patch there, maybe first notify them, then
test it and then forward it.

> Unfortunately the patch does not apply cleanly to the latest upstream
> release (4.4-alpha) but I am ready and willing to rebase it, whenever
> you decide to package it.  Just let me know.

Also on my todo list, but that's first planned for experimental, not
yet unstable.

So I wouldn't say no to a rebased patch set for 4.4alpha as that's
where upstream is currently working on.

Will likely work on these (and ccze) over the holidays.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: tagging 1000053

[Debian Bug Tracking System]

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

> tags 153 + fixed-upstream
Bug #153 [src:courier] courier: depends on obsolete pcre3 library
Bug #154 [src:courier] courier: depends on obsolete pcre3 library
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1058815: marked as done (calcium: FTBFS: /usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 17:49:37 +
with message-id 
and subject line Bug#1058916: Removed package(s) from unstable
has caused the Debian Bug report #1058815,
regarding calcium: FTBFS: /usr/include/fmpz_extras.h:208:1: error: static 
declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration
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.)


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

gcc -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-I/<> -I/usr/local/include -I/usr/local/include -I/usr/include 
-I/usr/local/include -I/usr/local/include -c write.c -o 
../build/calcium/write.lo -MMD -MP -MF "../build/calcium/write.d" -MT 
"../build/calcium/write.d" -MT "../build/calcium/write.lo"
In file included from /usr/include/fmpr.h:30,
 from /usr/include/arf.h:27,
 from /usr/include/acb.h:22,
 from /<>/calcium.h:24,
 from write.c:13:
/usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ 
follows non-static declaration
  208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
  | ^~
In file included from /<>/calcium.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’ 
with type ‘void(fmpz *, mp_limb_t,  mp_limb_t)’ {aka ‘void(long int *, long 
unsigned int,  long unsigned int)’}
  422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
  |  ^~
/usr/include/fmpr.h: In function ‘fmpr_set_ui’:
/usr/include/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated. Use 
'flint_ctz' instead.
  360 | count_trailing_zeros(b, c);
  |   ^ 
  
/usr/include/fmpr.h: In function ‘fmpr_set_si’:
/usr/include/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated. Use 
'flint_ctz' instead.
  375 | count_trailing_zeros(b, c);
  |   ^ 
  
In file included from /usr/include/fmpr.h:30,
 from /usr/include/arf.h:27,
 from /usr/include/acb.h:22,
 from /<>/calcium.h:24,
 from version.c:12:
/usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ 
follows non-static declaration
  208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
  | ^~
In file included from /<>/calcium.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’ 
with type ‘void(fmpz *, mp_limb_t,  mp_limb_t)’ {aka ‘void(long int *, long 
unsigned int,  long unsigned int)’}
  422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
  |  ^~
/usr/include/arf.h: In function ‘arf_init_set_ui’:
/usr/include/arf.h:435:11: error: 'count_leading_zeros' is deprecated. Use 
'flint_clz' instead.
  435 | count_leading_zeros(c, v);
  |   ^~~~  
 
/usr/include/arf.h: In function ‘arf_set_ui’:
/usr/include/arf.h:467:11: error: 'count_leading_zeros' is deprecated. Use 
'flint_clz' instead.
  467 | count_leading_zeros(c, v);
  |   ^~~~  
 
/usr/include/fmpr.h: In function ‘fmpr_set_ui’:
/usr/include/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated. Use 
'flint_ctz' instead.
  360 | count_trailing_zeros(b, c);
  |   ^ 
  
/usr/include/fmpr.h: In function ‘fmpr_set_si’:
/usr/include/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated. Use 
'flint_ctz' instead.
  375 | count_trailing_zeros(b, c);
  |   ^ 
  
/usr/include/arf.h: In function ‘arf_bits’:
/usr/include/arf.h:656:11: error: 'count_trailing_zeros' is deprecated. Use 
'flint_ctz' instead.
  656 | count_trailing_zeros(c, xp[0]);
  |   ^ 
  
In file included from /usr/include/fmpr.h:30,
 from /usr/include/arf.h:27,
 from /usr/include/acb.h:22,
  

Bug#999937: tup: depends on obsolete pcre3 library

[Yavor Doganov]

On Tue, Aug 29, 2023 at 03:18:26PM +0200, Bastian Germann wrote:
> On Tue, 31 Jan 2023 21:36:46 +0800 Bo YU  wrote:
> > The upstream has tried to switch pcre2[0], but the backporting is
> > not easy, so maybe waiting a new release is good iead.
> 
> I have started a backport in git but there is at least one linker
> flag missing.

That's right; the attached patch makes the build succeed for me but I
have not tested further (sorry for the patch noise; it's because I had
to "quilt refresh").
>From 2b6f55b4d9f476646072d2be197b4fc1defcf7ac Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Thu, 21 Dec 2023 19:20:23 +0200
Subject: [PATCH] pcre2.patch: Add missing linker flag; refresh

---
 debian/patches/pcre2.patch | 81 +-
 1 file changed, 37 insertions(+), 44 deletions(-)

diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
index 9d012bb..031b6a7 100644
--- a/debian/patches/pcre2.patch
+++ b/debian/patches/pcre2.patch
@@ -6,11 +6,9 @@ Subject: Update pcre 8.44 -> pcre2 10.42
 libpcre is no longer maintained, and was replaced by libpcre2. This
 requires some minor API changes.
 ---
-diff --git a/Tupfile b/Tupfile
-index 107c81cca..cc6ed1ce5 100644
 a/Tupfile
-+++ b/Tupfile
-@@ -30,7 +30,7 @@ srcs += src/sqlite3/*.o
+--- tup.orig/Tupfile
 tup/Tupfile
+@@ -30,7 +30,7 @@
  endif
  
  ifeq ($(use_system_pcre),y)
@@ -19,11 +17,9 @@ index 107c81cca..cc6ed1ce5 100644
  else
  srcs += src/pcre/*.o
  endif
-diff --git a/Tuprules.tup b/Tuprules.tup
-index 3cdab0ffc..a7fd6cb66 100644
 a/Tuprules.tup
-+++ b/Tuprules.tup
-@@ -99,7 +99,7 @@ else
+--- tup.orig/Tuprules.tup
 tup/Tuprules.tup
+@@ -89,7 +89,7 @@
  use_system_pcre = $(TUP_USE_SYSTEM_PCRE)
  endif
  ifeq ($(use_system_pcre),y)
@@ -32,11 +28,18 @@ index 3cdab0ffc..a7fd6cb66 100644
  else
  CFLAGS += -I$(TUP_CWD)/src/pcre
  CFLAGS += -DPCRE_STATIC
-diff --git a/build.sh b/build.sh
-index 7fecb8914..6ac7041e6 100755
 a/build.sh
-+++ b/build.sh
-@@ -80,6 +80,7 @@ mkdir luabuiltin
+--- tup.orig/build.sh
 tup/build.sh
+@@ -27,7 +27,7 @@
+ 	echo "Error: invalid TUP_SERVER \"$server\"" 1>&2
+ 	exit 1
+ fi
+-LDFLAGS="$LDFLAGS -lm"
++LDFLAGS="$LDFLAGS -lm -lpcre2-8"
+ : ${CC:=gcc}
+ case "$os" in
+ 	Linux)
+@@ -80,6 +80,7 @@
  ./lua ../src/luabuiltin/xxd.lua builtin.lua luabuiltin/luabuiltin.h
  
  CFLAGS="$CFLAGS -DTUP_SERVER=\"$server\""
@@ -44,11 +47,9 @@ index 7fecb8914..6ac7041e6 100755
  CFLAGS="$CFLAGS -DHAVE_CONFIG_H"
  
  for i in ../src/tup/*.c ../src/tup/tup/main.c ../src/tup/monitor/null.c ../src/tup/flock/fcntl.c ../src/inih/ini.c ../src/pcre/*.c $plat_files; do
-diff --git a/src/tup/entry.c b/src/tup/entry.c
-index 90e1b80c0..96842bc4b 100644
 a/src/tup/entry.c
-+++ b/src/tup/entry.c
-@@ -151,7 +151,7 @@ static int rm_entry(tupid_t tupid, int safe)
+--- tup.orig/src/tup/entry.c
 tup/src/tup/entry.c
+@@ -151,7 +151,7 @@
  		string_tree_rm(>parent->entries, >name);
  	}
  	if(tent->re) {
@@ -57,7 +58,7 @@ index 90e1b80c0..96842bc4b 100644
  	}
  	free_tent_tree(>stickies);
  	free_tent_tree(>group_stickies);
-@@ -504,11 +504,13 @@ static struct tup_entry *new_entry(tupid_t tupid, tupid_t dt,
+@@ -473,11 +473,13 @@
  	RB_INIT(>entries);
  
  	if(tent->dt == exclusion_dt()) {
@@ -75,7 +76,7 @@ index 90e1b80c0..96842bc4b 100644
  			return NULL;
  		}
  	} else {
-@@ -795,14 +797,16 @@ int exclusion_match(FILE *f, struct tent_entries *exclusion_root, const char *s,
+@@ -767,14 +769,16 @@
  	*match = 0;
  	RB_FOREACH(tt, tent_entries, exclusion_root) {
  		int rc;
@@ -95,10 +96,8 @@ index 90e1b80c0..96842bc4b 100644
  			fprintf(f, "tup error: Regex failed to execute: %s\n", tt->tent->name.s);
  			return -1;
  		}
-diff --git a/src/tup/entry.h b/src/tup/entry.h
-index 332849842..1b37e077e 100644
 a/src/tup/entry.h
-+++ b/src/tup/entry.h
+--- tup.orig/src/tup/entry.h
 tup/src/tup/entry.h
 @@ -26,9 +26,9 @@
  #include "string_tree.h"
  #include "db_types.h"
@@ -110,7 +109,7 @@ index 332849842..1b37e077e 100644
  
  struct variant;
  struct estring;
-@@ -51,7 +51,7 @@ struct tup_entry {
+@@ -51,7 +51,7 @@
  	_Atomic int refcount;
  
  	/* For exclusions */
@@ -119,11 +118,9 @@ index 332849842..1b37e077e 100644
  
  	/* For command strings */
  	char *flags;
-diff --git a/src/tup/parser.c b/src/tup/parser.c
-index ce057737f..71ee32c79 100644
 a/src/tup/parser.c
-+++ b/src/tup/parser.c
-@@ -2288,6 +2288,7 @@ struct path_list *new_pl(struct tupfile *tf, const char *s, int len, struct bin_
+--- tup.orig/src/tup/parser.c
 tup/src/tup/parser.c
+@@ -2235,6 +2235,7 @@
  	pl->pel = NULL;
  	pl->bin = NULL;
  	pl->re = NULL;
@@ -131,7 +128,8 @@ index ce057737f..71ee32c79 100644
  	memcpy(pl->mem, s, len);
  	pl->mem[len] = 0;
  	pl->orderid = orderid;
-@@ -2316,13 +2317,16 @@ struct path_list *new_pl(struct tupfile *tf, const char *s, int len, struct bin_
+@@ -2262,14 +2263,17 @@
+ 		}
  	} else if(p[0] == '^') {
  		/* Exclusion */
 -		const char *error;
@@ -152,7 +150,7 @@ 

Bug#999921: xymon: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find a patch which I've been testing for a while with no ill
effects AFAICT.  However, I'm not familiar at all with this package so
it's possible that I've missed something.  I also couldn't test all
available functionality.

Unfortunately the patch does not apply cleanly to the latest upstream
release (4.4-alpha) but I am ready and willing to rebase it, whenever
you decide to package it.  Just let me know.
>From d626686d8e004bbb9e1f5f0074ff825f27d1c2e5 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Thu, 21 Dec 2023 18:44:44 +0200
Subject: [PATCH] Port to PCRE2 (#21).

---
 debian/changelog  |5 +
 debian/control|2 +-
 debian/patches/93_pcre2.patch | 2167 +
 debian/patches/series |1 +
 debian/rules  |2 +-
 5 files changed, 2175 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/93_pcre2.patch

diff --git a/debian/changelog b/debian/changelog
index b406ada..1c01d47 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -37,6 +37,11 @@ xymon (4.3.30-2) UNRELEASED; urgency=medium
   * xymon: update xymonserver.cfg: ntpdate obsoleted the "-p" option.
 (Closes: #1057044)
 
+  [ Yavor Doganov ]
+  * debian/patches/93_pcre2.patch: New; port to PCRE2 (Closes: #21).
+  * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+  * debian/rules (override_dh_auto_configure): Use pcre2-config.
+
  -- Axel Beckert   Mon, 10 Aug 2020 04:39:28 +0200
 
 xymon (4.3.30-1) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 6766762..aaa40b3 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper-compat (= 13),
imagemagick,
libc-ares-dev,
libldap2-dev,
-   libpcre3-dev,
+   libpcre2-dev,
librrd-dev,
libssl-dev,
libtirpc-dev,
diff --git a/debian/patches/93_pcre2.patch b/debian/patches/93_pcre2.patch
new file mode 100644
index 000..7c163fd
--- /dev/null
+++ b/debian/patches/93_pcre2.patch
@@ -0,0 +1,2167 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/21
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2023-12-21
+---
+
+--- xymon.orig/lib/acknowledgementslog.c
 xymon/lib/acknowledgementslog.c
+@@ -26,7 +26,8 @@
+ #include 
+ #include 
+ 
+-#include 
++#define PCRE2_CODE_UNIT_WIDTH 8
++#include 
+ 
+ #include "libxymon.h"
+ 
+@@ -103,16 +104,17 @@
+   char title[200];
+ 
+   /* For the PCRE matching */
+-  const char *errmsg = NULL;
+-  int errofs = 0;
+-  pcre *pageregexp = NULL;
+-  pcre *expageregexp = NULL;
+-  pcre *hostregexp = NULL;
+-  pcre *exhostregexp = NULL;
+-  pcre *testregexp = NULL;
+-  pcre *extestregexp = NULL;
+-  pcre *rcptregexp = NULL;
+-  pcre *exrcptregexp = NULL;
++  int err;
++  PCRE2_SIZE errofs;
++  pcre2_code *pageregexp = NULL;
++  pcre2_code *expageregexp = NULL;
++  pcre2_code *hostregexp = NULL;
++  pcre2_code *exhostregexp = NULL;
++  pcre2_code *testregexp = NULL;
++  pcre2_code *extestregexp = NULL;
++  pcre2_code *rcptregexp = NULL;
++  pcre2_code *exrcptregexp = NULL;
++  pcre2_match_data *ovector;
+ 
+   if (maxminutes && (fromtime || totime)) {
+   fprintf(output, "Only one time interval type is 
allowed!");
+@@ -147,14 +149,14 @@
+ 
+   if (!maxcount) maxcount = 100;
+ 
+-  if (pageregex && *pageregex) pageregexp = pcre_compile(pageregex, 
PCRE_CASELESS, , , NULL);
+-  if (expageregex && *expageregex) expageregexp = 
pcre_compile(expageregex, PCRE_CASELESS, , , NULL);
+-  if (hostregex && *hostregex) hostregexp = pcre_compile(hostregex, 
PCRE_CASELESS, , , NULL);
+-  if (exhostregex && *exhostregex) exhostregexp = 
pcre_compile(exhostregex, PCRE_CASELESS, , , NULL);
+-  if (testregex && *testregex) testregexp = pcre_compile(testregex, 
PCRE_CASELESS, , , NULL);
+-  if (extestregex && *extestregex) extestregexp = 
pcre_compile(extestregex, PCRE_CASELESS, , , NULL);
+-  if (rcptregex && *rcptregex) rcptregexp = pcre_compile(rcptregex, 
PCRE_CASELESS, , , NULL);
+-  if (exrcptregex && *exrcptregex) exrcptregexp = 
pcre_compile(exrcptregex, PCRE_CASELESS, , , NULL);
++  if (pageregex && *pageregex) pageregexp = pcre2_compile(pageregex, 
strlen(pageregex), PCRE2_CASELESS, , , NULL);
++  if (expageregex && *expageregex) expageregexp = 
pcre2_compile(expageregex, strlen(expageregex), PCRE2_CASELESS, , , 
NULL);
++  if (hostregex && *hostregex) hostregexp = pcre2_compile(hostregex, 
strlen(hostregex), PCRE2_CASELESS, , , NULL);
++  if (exhostregex && *exhostregex) exhostregexp = 
pcre2_compile(exhostregex, strlen(exhostregex), PCRE2_CASELESS, , , 
NULL);
++  if (testregex && *testregex) testregexp = pcre2_compile(testregex, 
strlen(testregex), 

Processed: Re: Bug#999921: xymon: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #21 [src:xymon] xymon: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Simon McVittie]

On Thu, 21 Dec 2023 at 15:31:55 +0100, Marc Haber wrote:
> Do those GUI frontends that work via packagekit or other frameworks
> count as "using apt"?

Managing apt/dpkg packages via packagekit uses libapt-pkg6.0 (via
/usr/lib/*/packagekit-backend/libpk_backend_apt.so). I don't know whether
that's enough to give it the specific desirable behaviour around Conflicts
that Helmut is referring to, but I hope it is.

Other non-CLI package management like unattended-upgrades is generally
in a similar situation, using libapt-pkg or its language bindings,
but not the apt(8) or apt-get(8) CLIs specifically.

smcv

Bug#1057580: nfstrace: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

[Sven Joachim]

Control: tags -1 + patch

On 2023-12-05 23:07 +0100, Santiago Vila wrote:

> Package: src:nfstrace
> Version: 0.4.3.2+git20200805+b220d04-2.2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> 
> [  7%] Building CXX object 
> analyzers/src/watch/CMakeFiles/watch.dir/nc_windows/header_window.cpp.o
> cd /<>/obj-x86_64-linux-gnu/analyzers/src/watch && /usr/bin/c++ 
> -Dwatch_EXPORTS -I/<>/src -I/usr/include/tirpc 
> -I/<>/analyzers/src/watch -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -pedantic -Wall -Werror -Wextra 
> -Wno-invalid-offsetof -Wno-error=address-of-packed-member -fPIC 
> -fvisibility=hidden -fPIC -MD -MT 
> analyzers/src/watch/CMakeFiles/watch.dir/nc_windows/header_window.cpp.o -MF 
> CMakeFiles/watch.dir/nc_windows/header_window.cpp.o.d -o 
> CMakeFiles/watch.dir/nc_windows/header_window.cpp.o -c 
> /<>/analyzers/src/watch/nc_windows/header_window.cpp
> /<>/analyzers/src/watch/nc_windows/header_window.cpp: In member 
> function ‘void HeaderWindow::resize(MainWindow&)’:
> /<>/analyzers/src/watch/nc_windows/header_window.cpp:90:72: 
> error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
>90 | _window = subwin(m._window, 
> std::min(static_cast(m._window->_maxy), GUI_HEADER_HEIGHT), 
> std::min(static_cast(m._window->_maxx), GUI_LENGTH), 0, 0);
>   |   
>  ^~
> In file included from 
> /<>/analyzers/src/watch/nc_windows/header_window.h:25,
>  from 
> /<>/analyzers/src/watch/nc_windows/header_window.cpp:28:
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> /<>/analyzers/src/watch/nc_windows/header_window.cpp:90:137: 
> error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
>90 | _window = subwin(m._window, 
> std::min(static_cast(m._window->_maxy), GUI_HEADER_HEIGHT), 
> std::min(static_cast(m._window->_maxx), GUI_LENGTH), 0, 0);
>   |   
>   ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> make[3]: *** [analyzers/src/watch/CMakeFiles/watch.dir/build.make:79: 
> analyzers/src/watch/CMakeFiles/watch.dir/nc_windows/header_window.cpp.o] 
> Error 1

The attached patch fixes these errors and similar ones in
analyzers/src/watch/nc_windows/statistics_window.cpp.  Note that
getmaxx(window) returns window->_maxx + 1, and similar for getmaxy().

Disclaimer: I have only tested that the package builds, not if it works.

Cheers,
   Sven

From dcffbee1fa8170fdf6906791eb0239fac63e5333 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Thu, 21 Dec 2023 17:12:56 +0100
Subject: [PATCH] Fix FTBFS with opqaque ncurses

Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be addressed directly.  Use the getmaxy/getmaxx
functions ncurses provides for this purpose instead.
---
 analyzers/src/watch/nc_windows/header_window.cpp | 2 +-
 analyzers/src/watch/nc_windows/statistics_window.cpp | 8 
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/analyzers/src/watch/nc_windows/header_window.cpp b/analyzers/src/watch/nc_windows/header_window.cpp
index a376488..047d555 100644
--- a/analyzers/src/watch/nc_windows/header_window.cpp
+++ b/analyzers/src/watch/nc_windows/header_window.cpp
@@ -87,7 +87,7 @@ void HeaderWindow::resize(MainWindow& m)
 }
 if(m._window != nullptr)
 {
-_window = subwin(m._window, std::min(static_cast(m._window->_maxy), GUI_HEADER_HEIGHT), std::min(static_cast(m._window->_maxx), GUI_LENGTH), 0, 0);
+_window = subwin(m._window, std::min(static_cast(getmaxy(m._window) - 1 ), GUI_HEADER_HEIGHT), std::min(static_cast(getmaxx(m._window) - 1 ), GUI_LENGTH), 0, 0);
 }
 if(_window != nullptr)
 {
diff --git a/analyzers/src/watch/nc_windows/statistics_window.cpp b/analyzers/src/watch/nc_windows/statistics_window.cpp
index b580bba..c2e27fc 100644
--- a/analyzers/src/watch/nc_windows/statistics_window.cpp
+++ b/analyzers/src/watch/nc_windows/statistics_window.cpp
@@ -50,7 +50,7 @@ void StatisticsWindow::destroy()

 bool StatisticsWindow::canWrite(unsigned int i)
 {
-return (i >= _scrollOffset.at(_activeProtocol) + STATISTICS::FIRST_OPERATION_LINE && i - _scrollOffset.at(_activeProtocol) + BORDER_SIZE < static_cast(_window->_maxy));
+return (i >= _scrollOffset.at(_activeProtocol) + 

Processed: Re: Bug#1057580: nfstrace: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1057580 [src:nfstrace] nfstrace: FTBFS: error: invalid use of incomplete 
type ‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.

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

Bug#1059140: [Debian-med-packaging] Bug#1059140: sight: FTBFS: error: ‘void* __builtin_memcpy(void*, const void*, long unsigned int) ’ forming offset [32, 34] is out of the bounds [0, 32] of object ‘

[Flavien Bridault]

Dear Andreas,

Thank you for the notice. It looks like a optimizer compiler bug... 
Anyway, I managed to patch it using a different syntax.


I pushed it in the repository. Please have a look and upload it if 
that's good enough.


Cheers.


*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE


Le 20/12/2023 à 12:30, Sebastian Ramacher a écrit :

Source: sight
Version: 23.1.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc:sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=sight=amd64=23.1.0-1%2Bb1=1702935225=0

[ 50%] Building CXX object 
libs/filter/dicom/CMakeFiles/filter_dicom.dir/IFilter.cpp.o
cd /<>/obj-x86_64-linux-gnu/libs/filter/dicom && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_BIND_GLOBAL_PLACEHOLDERS -DBOOST_CHRONO_DYN_LINK 
-DBOOST_CHRONO_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_DATE_TIME_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_NO_LIB -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_IOSTREAMS_NO_LIB -DBOOST_LOG_DYN_LINK -DBOOST_LOG_NO_LIB 
-DBOOST_LOG_SETUP_DYN_LINK -DBOOST_LOG_SETUP_NO_LIB -DBOOST_REGEX_DYN_LINK -DBOOST_REGEX_NO_LIB -DBOOST_SPIRIT_USE_PHOENIX_V3 -DBOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0 -DBOOST_THREAD_DYN_LINK 
-DBOOST_THREAD_NO_LIB -DBOOST_THREAD_PROVIDES_FUTURE -DBOOST_THREAD_VERSION=2 -DFILTER_DICOM_EXPORTS -DNDEBUG -DSIGHT_SOURCE_DIR=\"/<>\" -Dfilter_dicom_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/libs/filter/dicom/include -I/<>/libs -I/<>/libs/core -I/<>/obj-x86_64-linux-gnu/libs/core/core/include 
-I/<>/obj-x86_64-linux-gnu/libs/core/data/include -I/<>/obj-x86_64-linux-gnu/libs/geometry/data/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=gnu++20 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra 
-Wconversion -march=x86-64 -mtune=generic -mfpmath=sse -fopenmp -Werror -Wno-error=deprecated-declarations -fopenmp -Winvalid-pch -include 
/<>/obj-x86_64-linux-gnu/libs/core/pch/pchCore/CMakeFiles/pchCore.dir/cmake_pch.hxx -MD -MT libs/filter/dicom/CMakeFiles/filter_dicom.dir/IFilter.cpp.o -MF CMakeFiles/filter_dicom.dir/IFilter.cpp.o.d -o 
CMakeFiles/filter_dicom.dir/IFilter.cpp.o -c /<>/libs/filter/dicom/IFilter.cpp
In file included from /usr/include/c++/13/string:42,
  from 
/usr/include/boost/algorithm/string/std/string_traits.hpp:15,
  from 
/usr/include/boost/algorithm/string/std_containers_traits.hpp:19,
  from /usr/include/boost/algorithm/string.hpp:18,
  from 
/<>/obj-x86_64-linux-gnu/libs/core/pch/pchCore/CMakeFiles/pchCore.dir/cmake_pch.hxx:5,
  from :
In static member function ‘static constexpr std::char_traits::char_type* 
std::char_traits::copy(char_type*, const char_type*, std::size_t)’,
 inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, 
_Alloc>::basic_string(std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&&) [with _CharT = 
char; _Traits = std::char_traits; _Alloc = std::allocator]’ at 
/usr/include/c++/13/bits/basic_string.h:683:23,
 inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Allocator> 
std::operator+(__cxx11::basic_string<_CharT, _Traits, _Allocator>&&, __cxx11::basic_string<_CharT, _Traits, 
_Allocator>&&) [with _CharT = char; _Traits = char_traits; _Alloc = allocator]’ at 
/usr/include/c++/13/bits/basic_string.h:3668:43,
 inlined from ‘std::string sight::core::com::SlotBase::getTypeName() const [with F = 
void(double)]’ at /<>/libs/core/core/com/SlotBase.hpp:227:99,
 inlined from ‘sight::core::com::Slot::Slot() [with R = void; A = {double}]’ 
at /<>/libs/core/core/com/Slot.hxx:48:33:
/usr/include/c++/13/bits/char_traits.h:445:56: error: ‘void* __builtin_memcpy(void*, const 
void*, long unsigned int)’ forming offset [32, 34] is out of the bounds [0, 32] of object 
‘’ with type ‘std::__cxx11::basic_string’ 
[-Werror=array-bounds=]
   445 | return static_cast(__builtin_memcpy(__s1, __s2, 
__n));
   |
^
In file included from /<>/libs/core/core/com/SlotRun.hpp:27,
  from /<>/libs/core/core/com/SlotCall.hpp:27,
  from /<>/libs/core/core/com/Slot.hpp:27,
  from /<>/libs/core/service/IService.hpp:30,
  from /<>/libs/core/service/IRegisterer.hpp:26,
 

Bug#1052856: marked as done (httpcore: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 16:19:02 +
with message-id 
and subject line Bug#1052856: fixed in httpbin 0.10.1+dfsg-2
has caused the Debian Bug report #1052856,
regarding httpcore: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.11 returned exit code 13
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.)


-- 
1052856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httpcore
Version: 0.17.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_trace.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_synchronization.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_utils.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_models.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_api.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> copying httpcore/_ssl.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore
> creating 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/socks_proxy.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/http_proxy.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/interfaces.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/connection_pool.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/http11.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/http2.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> copying httpcore/_async/connection.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_async
> creating 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/anyio.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/base.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/sync.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/trio.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/auto.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> copying httpcore/_backends/mock.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_backends
> creating /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/socks_proxy.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/http_proxy.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/interfaces.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/connection_pool.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/http11.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/http2.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> copying httpcore/_sync/connection.py -> 
> /<>/.pybuild/cpython3_3.11_httpcore/build/httpcore/_sync
> running egg_info
> creating httpcore.egg-info
> writing 

Processed: Bug#1052856 marked as pending in httpbin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052856 [src:httpcore] httpcore: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.

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

Bug#1058126: marked as done (tkcalendar: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 16:54:41 +0100
with message-id <20231221165441.5fae1...@debian.org>
and subject line 1058126
has caused the Debian Bug report #1058126,
regarding tkcalendar: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tkcalendar
Version: 1.6.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> HOME=/tmp xvfb-run -a dh_auto_test
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12/build; 
> python3.12 -m unittest discover -v 
> /<>/.pybuild/cpython3_3.12/build/tkcalendar/calendar_.py:221: 
> SyntaxWarning: invalid escape sequence '\ '
>   font = kw.pop("font", "Liberation\ Sans 9")
> test_calendar_buttons_functions 
> (tests.test_calendar.TestCalendar.test_calendar_buttons_functions) ... ERROR
> test_calendar_calevents 
> (tests.test_calendar.TestCalendar.test_calendar_calevents) ... ok
> test_calendar_get_set 
> (tests.test_calendar.TestCalendar.test_calendar_get_set) ... ok
> test_calendar_init (tests.test_calendar.TestCalendar.test_calendar_init) ... 
> ERROR
> test_calendar_other_fcts 
> (tests.test_calendar.TestCalendar.test_calendar_other_fcts) ... ok
> test_calendar_selection 
> (tests.test_calendar.TestCalendar.test_calendar_selection) ... ok
> test_calendar_virtual_events 
> (tests.test_calendar.TestCalendar.test_calendar_virtual_events) ... ok
> test_dateentry_drop_down 
> (tests.test_dateentry.TestDateEntry.test_dateentry_drop_down)
> Check whether drop down opens on click. ... ok
> test_dateentry_functions 
> (tests.test_dateentry.TestDateEntry.test_dateentry_functions) ... ERROR
> test_dateentry_get_set 
> (tests.test_dateentry.TestDateEntry.test_dateentry_get_set) ... ok
> test_dateentry_init (tests.test_dateentry.TestDateEntry.test_dateentry_init) 
> ... ok
> test_tooltip (tests.test_tooltip.TestTooltip.test_tooltip) ... ok
> test_tooltip_config 
> (tests.test_tooltip.TestTooltipWrapper.test_tooltip_config) ... ok
> test_tooltipwrapper 
> (tests.test_tooltip.TestTooltipWrapper.test_tooltipwrapper) ... ok
> test_tooltipwrapper_init 
> (tests.test_tooltip.TestTooltipWrapper.test_tooltipwrapper_init) ... ok
> 
> ==
> ERROR: test_calendar_buttons_functions 
> (tests.test_calendar.TestCalendar.test_calendar_buttons_functions)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.12/build/tests/test_calendar.py", line 
> 194, in test_calendar_buttons_functions
> widget.selection_set(format_date(date(2018, 12, 31), 'short'))
>  
>   File "/<>/.pybuild/cpython3_3.12/build/tests/__init__.py", 
> line 30, in format_date
> return babel.dates.format_date(date, length, locale)
>^
>   File "/usr/lib/python3/dist-packages/babel/dates.py", line 726, in 
> format_date
> locale = Locale.parse(locale)
>  
>   File "/usr/lib/python3/dist-packages/babel/core.py", line 330, in parse
> raise UnknownLocaleError(input_id)
> babel.core.UnknownLocaleError: unknown locale 'c'
> 
> ==
> ERROR: test_calendar_init 
> (tests.test_calendar.TestCalendar.test_calendar_init)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.12/build/tests/test_calendar.py", line 
> 38, in test_calendar_init
> today = format_date(date.today(), 'short')
> ^^
>   File "/<>/.pybuild/cpython3_3.12/build/tests/__init__.py", 
> line 30, in format_date
> return babel.dates.format_date(date, length, locale)
>^
>   File "/usr/lib/python3/dist-packages/babel/dates.py", line 726, in 
> format_date
> locale = Locale.parse(locale)
>  
>   File "/usr/lib/python3/dist-packages/babel/core.py", line 330, in parse
> raise 

Bug#1052856: marked as pending in httpbin

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1052856 in httpbin 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/httpbin/-/commit/5cb1ee47ba39aab5815289108a9b54c042dc8441


Patch: Support Flask >= 2.3.0, and avoid deprecation warnings in >= 2.2.0. 
(Closes: #1052856)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052856

Bug#1058302: marked as done (patsy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 15:35:35 +
with message-id 
and subject line Bug#1058302: fixed in patsy 0.5.4-1
has caused the Debian Bug report #1058302,
regarding patsy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: patsy
Version: 0.5.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dpkg-query: no packages found matching ipython
> py3versions: no X-Python3-Version in control file, using supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.12 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/patsy
> copying patsy/tokens.py -> build/lib/patsy
> copying patsy/compat.py -> build/lib/patsy
> copying patsy/__init__.py -> build/lib/patsy
> copying patsy/test_state.py -> build/lib/patsy
> copying patsy/desc.py -> build/lib/patsy
> copying patsy/test_splines_crs_data.py -> build/lib/patsy
> copying patsy/redundancy.py -> build/lib/patsy
> copying patsy/missing.py -> build/lib/patsy
> copying patsy/parse_formula.py -> build/lib/patsy
> copying patsy/version.py -> build/lib/patsy
> copying patsy/test_splines_bs_data.py -> build/lib/patsy
> copying patsy/builtins.py -> build/lib/patsy
> copying patsy/test_regressions.py -> build/lib/patsy
> copying patsy/origin.py -> build/lib/patsy
> copying patsy/build.py -> build/lib/patsy
> copying patsy/contrasts.py -> build/lib/patsy
> copying patsy/design_info.py -> build/lib/patsy
> copying patsy/state.py -> build/lib/patsy
> copying patsy/mgcv_cubic_splines.py -> build/lib/patsy
> copying patsy/user_util.py -> build/lib/patsy
> copying patsy/constraint.py -> build/lib/patsy
> copying patsy/splines.py -> build/lib/patsy
> copying patsy/infix_parser.py -> build/lib/patsy
> copying patsy/eval.py -> build/lib/patsy
> copying patsy/highlevel.py -> build/lib/patsy
> copying patsy/categorical.py -> build/lib/patsy
> copying patsy/compat_ordereddict.py -> build/lib/patsy
> copying patsy/util.py -> build/lib/patsy
> copying patsy/test_highlevel.py -> build/lib/patsy
> copying patsy/test_build.py -> build/lib/patsy
> python3.11 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> dh_auto_build
>   pybuild --build -i python{version} -p "3.12 3.11"
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update 

Bug#1058904: marked as done (python3-apt: apt_pkg.TagFile segfaults on files with comments)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 15:20:03 +
with message-id 
and subject line Bug#1058904: fixed in python-apt 2.7.3
has caused the Debian Bug report #1058904,
regarding python3-apt: apt_pkg.TagFile segfaults on files with comments
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.)


-- 
1058904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-apt
Version: 2.7.2
Severity: serious
X-Debbugs-Cc: stu...@debian.org

Dear Maintainer,

With the upgrade to python3-apt 2.7.2, CI for python-debian started
failing for both python3.11 and python3.12. The particular test where
the segfault is found feeds apt_pkg.TagFile data that contains comments
in the form permitted by Policy for source package control files.

https://salsa.debian.org/stuart/python-debian/-/blob/master/tests/test_deb822.py?ref_type=heads#L1279

Previous versions raised apt_pkg.Error for erronous data.

They key feature of the data that is causing the segfault is the
inclusion of a comment in a multiline field.

While users of python-debian's deb822 wrappers are encouraged to not use
apt_pkg.TagFile for anything other than archive-generated files such as
the Sources and Packages files, there are legacy users and
out-of-archive users that could be doing so. Unparsable data should also
not segfault the interpreter but generate an exception.

regards
Stuart


Steps to reproduce (output below are for git HEAD with a slightly
rearranged directory structure; current version in sid does the same):

$ debcheckout python-debian
$ cd python-debian
$ python3.11 -m pytest -k test_iter_paragraphs_comments_use_apt_pkg
== test session starts 
==
platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0 -- 
/usr/bin/python3.11
cachedir: .pytest_cache
rootdir: /tmp/pkgs/python-debian
configfile: pyproject.toml
testpaths: src, tests
plugins: cov-4.1.0
collected 295 items / 294 deselected / 1 selected

tests/test_deb822.py::TestDeb822::test_iter_paragraphs_comments_use_apt_pkg 
Fatal Python error: Segmentation fault

Current thread 0x7f97ca55a040 (most recent call first):
File "/tmp/pkgs/python-debian/src/debian/deb822.py", line 740 in iter_paragraphs
File "/tmp/pkgs/python-debian/tests/test_deb822.py", line 1297 in 
test_iter_paragraphs_comments_use_apt_pkg
File "/usr/lib/python3/dist-packages/_pytest/python.py", line 194 in 
pytest_pyfunc_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1792 in runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 169 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 261 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 350 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 325 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 271 in wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 318 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File 

Bug#1058657: marked as done (python3-apt: undefined symbol: PyAptWarning)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 15:20:03 +
with message-id 
and subject line Bug#1058657: fixed in python-apt 2.7.3
has caused the Debian Bug report #1058657,
regarding python3-apt: undefined symbol: PyAptWarning
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.)


-- 
1058657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-apt
Version: 2.7.2
Severity: serious

Dear Maintainer,

This morning I see :

,
| dak@christian ~ % dak dominate
| Traceback (most recent call last):
|   File "/usr/bin/dak", line 43, in 
| import daklib.utils
|   File "/usr/lib/python3/dist-packages/daklib/utils.py", line 32, in 
| import apt_inst
| ImportError: 
/usr/lib/python3/dist-packages/apt_inst.cpython-311-x86_64-linux-gnu.so: 
undefined symbol: PyAptWarning
`

Christian


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

Kernel: Linux 6.6.7-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)

Versions of packages python3-apt depends on:
ii  distro-info-data   0.60
ii  libapt-pkg6.0  2.7.7
ii  libc6  2.37-13
ii  libgcc-s1  13.2.0-8
ii  libstdc++6 13.2.0-8
ii  python-apt-common  2.7.2
ii  python33.11.6-1

Versions of packages python3-apt recommends:
ii  iso-codes4.15.0-1
ii  lsb-release  12.0-2

Versions of packages python3-apt suggests:
ii  apt 2.7.7
pn  python-apt-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-apt
Source-Version: 2.7.3
Done: Julian Andres Klode 

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated python-apt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Dec 2023 16:00:06 +0100
Source: python-apt
Architecture: source
Version: 2.7.3
Distribution: unstable
Urgency: medium
Maintainer: APT Development Team 
Changed-By: Julian Andres Klode 
Closes: 1058657 1058904
Changes:
 python-apt (2.7.3) unstable; urgency=medium
 .
   * Handle null pointer deference in error handler (Closes: #1058904)
   * Actually register apt_pkg.Warning object
   * apt_inst: Import apt_pkg.Warning and export it again (Closes: #1058657)
   * d/tests/control: Add allow-stderr Restriction
Checksums-Sha1:
 806bd78bcaf7bd830b3a06dfa72e32daa24c6059 2366 python-apt_2.7.3.dsc
 781d6a3a149009e51c4c839668ff16c368ed2d04 352868 python-apt_2.7.3.tar.xz
 0021290f6be83797803d804d2762631f6f21baac 9643 python-apt_2.7.3_source.buildinfo
Checksums-Sha256:
 86e9adf38a5633878cdaf91f3237b0ff3f71965f7cb9904bcee20bdefd28bace 2366 
python-apt_2.7.3.dsc
 775e90648db9db5746cf0f9d03562af8861f3c98084e4edd459ea4aba46720f8 352868 
python-apt_2.7.3.tar.xz
 0d0e26cb895a88e2ba576c0f02d1629ad78a241f8b387cf1cdfc2c5a57d5cb8d 9643 
python-apt_2.7.3_source.buildinfo
Files:
 9630f522a848ce0087092149b3bfcf86 2366 python optional python-apt_2.7.3.dsc
 9cbe2cf6fb11e9694bd2bbf67765edb5 352868 python optional python-apt_2.7.3.tar.xz
 8ce33bb0abbc6bbe99e523c999717cf3 9643 python optional 
python-apt_2.7.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEruHIqqrwt2hAGcVGAhs2G2sDGwAFAmWEVBQPHGpha0BkZWJp
YW4ub3JnAAoJEAIbNhtrAxsAlfUP/0Fkx42pKY/fRz84ZKy0KVXl3UhiBMFB92Eh
blsvKzadVa3TeBynfxZ8S5k5Ir94Zeokg29z1vLcO9uFsMQKgKvtHo+ln0H7o/PO
DV40UoRzsGHe4Bm5u51VDA33wGg+kpX68tQBWOkGqZUskrj3XaWhtpgcX4kaErdk
jC49VnL7JjSpWkRNwUClOxKUB9BLzToE1p3XYl297vCZeIwbYepenyvM+AsNhnRU
BnCjoRCprO7i1aJbcxrb4Dgd3aozdfr3aMF/wPWP/g/eSAtc9ExCJ5AP1gxZdPm/
/ZBhS4hyw4DpRuRzgLIOphtOnLIWfLA8dw5j+hGUTmxCNW7zCmUW6jUrKTCjwwkz

Bug#1058657: marked as pending in python-apt

[Julian Andres Klode]

Control: tag -1 pending

Hello,

Bug #1058657 in python-apt 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/apt-team/python-apt/-/commit/c64748b17f875ae16783755122064e5abdc0cf0c


apt_inst: Import apt_pkg.Warning and export it again

Like apt_pkg.Error, we need to also proxy apt_pkg.Warning, and
specifically the PyAptWarning variable needs to be declared and
initialized with the object from apt_pkg as otherwise we get a
missing symbol from dlopen()

Fixes: 81a5896ee410c62ccf140b48142a5358a07331ca
   ("Issue warnings as apt_pkg.Warning instead of discarding when
   there is no error")
Closes: #1058657


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058657

Processed: Bug#1058657 marked as pending in python-apt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058657 [python3-apt] python3-apt: undefined symbol: PyAptWarning
Added tag(s) pending.

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

Bug#1058876: marked as done (libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod))

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 14:50:15 +
with message-id 
and subject line Bug#1058876: fixed in openmpi 4.1.6-3
has caused the Debian Bug report #1058876,
regarding libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)
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.)


-- 
1058876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi-dev
Version: 4.1.6-2
Severity: serious
Justification: ftbfs (other)

openmpi 4.1.6-2 moved the fortran mod files from /usr/lib to
/usr/include.  This is probably correct, but has some consequences we
need to sort out. Applications using cmake for configuration are still
looking for the mod files in /usr/lib, so their builds now fail.

An example is adios2, with error message:

[384/1029] /usr/bin/gfortran 
-I/build/adios2-2.9.2+dfsg1/examples/hello/bpWriter 
-I/build/adios2-2.9.2+dfsg1/build-mpi/bindings/Fortran 
-I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi -I/usr/lib/x86_
64-linux-gnu/openmpi/lib -g -O2 -ffile-prefix-map=/build/adios2-2.9.2+dfsg1=. 
-fstack-protector-strong -fstack-clash-protection -fcf-protection 
-Jexamples/hello/bpWriter -fpreprocessed -c examples/hello/bpWriter
/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90-pp.f90 -o 
examples/hello/bpWriter/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90.o
FAILED: 
examples/hello/bpWriter/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90.o 
/usr/bin/gfortran -I/build/adios2-2.9.2+dfsg1/examples/hello/bpWriter 
-I/build/adios2-2.9.2+dfsg1/build-mpi/bindings/Fortran 
-I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi 
-I/usr/lib/x86_64-linux-gn
u/openmpi/lib -g -O2 -ffile-prefix-map=/build/adios2-2.9.2+dfsg1=. 
-fstack-protector-strong -fstack-clash-protection -fcf-protection 
-Jexamples/hello/bpWriter -fpreprocessed -c examples/hello/bpWriter/CMakeFiles
/hello_bpWriter_f_mpi.dir/helloBPWriter.F90-pp.f90 -o 
examples/hello/bpWriter/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90.o
/build/adios2-2.9.2+dfsg1/examples/hello/bpWriter/helloBPWriter.F90:3:9:

3 | use mpi
  | 1
Fatal Error: Cannot open module file ‘mpi.mod’ for reading at (1): No such file 
or directory
compilation terminated.

We can see that the compilation got configured to use
-I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi
which would be why it can't find mpi.mod in /usr/include

As far as I can tell, adios2 is not making assumptions itself about
the location of the mod files.  I suspect the configuration is coming
from cmake's FindMPI.cmake

I guess we don't want openmpi 4.1.6-2 to migrate to testing until this
issue is resolved, which is why I've marked Severity: serious.

There are openmpi's pkgconfig files.
$ pkg-config --cflags mpi-fort
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/lib 

The fortrandir variable set in ompi-fort.pc is also located in
/usr/lib (perhaps it should be so)

So /usr/include is not used in the include path flags. But /usr/lib is.
This must be the origin of the problem.  cmake's FindMPI.cmake does
indeed use pkgconfig to extract the paths:
"if(_MPI_PKG AND PKG_CONFIG_FOUND)"



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

Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libopenmpi-dev depends on:
ii  gfortran [gfortran-mod-15] 4:13.2.0-2
ii  gfortran-11 [gfortran-mod-15]  11.4.0-7
ii  gfortran-12 [gfortran-mod-15]  12.3.0-13
ii  gfortran-13 [gfortran-mod-15]  13.2.0-9
ii  libevent-dev   2.1.12-stable-8
ii  libhwloc-dev   2.10.0-1
ii  libibverbs-dev 48.0-1
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui1.13.2+dfsg-1
ii  libopenmpi34.1.6-2
ii  libpmix-dev5.0.1-4
ii  openmpi-bin4.1.6-2
ii  openmpi-common 4.1.6-2
ii  zlib1g-dev 1:1.3.dfsg-3

Versions of packages libopenmpi-dev recommends:
ii  libcoarrays-openmpi-dev  2.10.1-1+b1

Processed: Bug#1058904 marked as pending in python-apt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058904 [python3-apt] python3-apt: apt_pkg.TagFile segfaults on files with 
comments
Added tag(s) pending.

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

Bug#1058904: marked as pending in python-apt

[Julian Andres Klode]

Control: tag -1 pending

Hello,

Bug #1058904 in python-apt 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/apt-team/python-apt/-/commit/735ff09c8688fb2bb5f984e439ac222dfd97c76b


Handle null pointer deference in error handler

The commit introducing support for warnings accidentally moved the Res
check outside of the if when it moved it to the end, causing a crash.

Fixes: 81a5896ee410c62ccf140b48142a5358a07331ca
   ("Issue warnings as apt_pkg.Warning instead of discarding when
   there is no error")
Closes: #1058904


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058904

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Matthew Vernon]

Hi,

On 21/12/2023 09:41, Helmut Grohne wrote:


Is it ok to call upgrade scenarios failures that cannot be reproduced
using apt unsupported until we no longer deal with aliasing?


I incline towards "no"; if an upgrade has failed part-way (as does 
happen), people may then reasonably use dpkg directly to try and 
un-wedge the upgrade (e.g. to try and configure some part-installed 
packages, or try installing some already-downloaded packages).


It may be that the mitigations necessary are worse than the risk, but I 
think the behaviour as described in #1058937 is definitely buggy.


Regards,

Matthew

Bug#1058216: marked as done (pygopherd: FTBFS: ModuleNotFoundError: No module named 'imp')

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 14:37:58 +
with message-id 
and subject line Bug#1058216: fixed in pygopherd 3.0.0~git20221126.02c65d60-5
has caused the Debian Bug report #1058216,
regarding pygopherd: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)


-- 
1058216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygopherd
Version: 3.0.0~git20221126.02c65d60-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/logger.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/gopherentry.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/sighandlers.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/fileext.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/initialization.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/GopherExceptions.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/testutil.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> copying pygopherd/server.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd
> creating 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/mbox.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/tal.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/dir.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/gophermap.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/HandlerMultiplexer.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/base.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/scriptexec.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/html.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/pyg.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/virtual.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/ZIP.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/url.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/file.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> copying pygopherd/handlers/UMN.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/handlers
> creating 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/spartan.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/wap.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/enhanced.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/rfc1436.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/base.py -> 
> /<>/.pybuild/cpython3_3.12_pygopherd/build/pygopherd/protocols
> copying pygopherd/protocols/gopherp.py -> 
> 

Bug#1057931: marked as done (greetd: FTBFS: failed to select a version for the requirement `rpassword = "^6.0"`)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 14:35:34 +
with message-id 
and subject line Bug#1057931: fixed in greetd 0.9.0-6
has caused the Debian Bug report #1057931,
regarding greetd: FTBFS: failed to select a version for the requirement 
`rpassword = "^6.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.)


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

Package: src:greetd
Version: 0.9.0-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --buildsystem=cargo
   dh_update_autotools_config -O--buildsystem=cargo
   dh_autoreconf -O--buildsystem=cargo
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po '^\S+') 
> debian/cargo-checksum.json;
make[1]: Leaving directory '/<>'
   dh_auto_configure -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] [] 
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<>/debian/cargo_registry/
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# actually does the build
DEB_BUILD_OPTIONS= dh_auto_test -- --release
debian cargo wrapper: options, profiles, parallel, lto: [] [] [] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
'--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
error: failed to select a version for the requirement `rpassword = "^6.0"`
candidate versions found which didn't match: 7.2.0
location searched: directory source `/<>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
required by package `agreety v0.9.0 (/<>/agreety)`
perhaps a crate was updated and forgotten to be re-vendored?
dh_auto_test: error: /usr/share/cargo/bin/cargo build --release returned exit 
code 101
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: greetd
Source-Version: 0.9.0-6
Done: Marc Dequènes (Duck) 

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

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated greetd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Dec 2023 23:17:58 +0900
Source: greetd
Architecture: source
Version: 0.9.0-6
Distribution: unstable
Urgency: medium
Maintainer: Marc Dequènes (Duck) 
Changed-By: Marc Dequènes (Duck) 
Closes: 1057931
Changes:
 greetd (0.9.0-6) unstable; urgency=medium
 .
   * Relax dependency on rpassword (Closes: #1057931).
Checksums-Sha1:
 17976c547250ae6f7f577af0f5d44abd590a66c6 

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Marc Haber]

On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote:
> On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > using apt unsupported until we no longer deal with aliasing?
> 
> I think so, yes. I don't think it's likely that there are people doing
> upgrades on running systems not using apt.

Do those GUI frontends that work via packagekit or other frameworks
count as "using apt"? I now that WE recommend using apt in a text
console outside of X, but even many of our own users do what their
Desktop Environment does, and our downstreams like *b*nt* recommend
other ways to upgrade as well.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Jussi Pakkanen]

On Thu, 21 Dec 2023 at 14:57, Paul Gevers  wrote:

> The Release Team considers packages that are out-of-sync between testing
> and unstable for more than 30 days as having a Release Critical bug in
> testing [1]. Your package src:meson has been trying to migrate for 31
> days [2]. Hence, I am filing this bug. The version in unstable fails its
> own autopkgtest on arm64 and i386 (and armel, but that's not a regression).

The reason for this is the following (on i86, but the same applies to
arm64 too):

2428s = note: /usr/bin/ld:
/usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inflate.o):
in function `.L707':
2428s (.text+0x2c79): undefined reference to `__stack_chk_fail_local'
2428s /usr/bin/ld:
/usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inflate.o):
in function `inflateSync':
2428s (.text+0x3471): undefined reference to `__stack_chk_fail_local'
2428s /usr/bin/ld:
/usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inftrees.o):
in function `inflate_table':
2428s (.text+0xea7): undefined reference to `__stack_chk_fail_local'
2428s /usr/bin/ld: prog: hidden symbol `__stack_chk_fail_local' isn't defined
2428s /usr/bin/ld: final link failed: bad value
2428s collect2: error: ld returned 1 exit status

This happens when mixing code compiled natively with code compiled
with rustc. To the best of our knowledge, this is a Rust toolchain bug
because the exact same compilation commands work on other platforms.
The missing symbol has double leading underscores implying it is a
compiler internal thing and the test we are using does not attempt to
do anything magical, only compile and link C and Rust code together in
the same binary.

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Sébastien Villemot]

Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit :
> * Santiago Vila  [2023-12-20 22:03]:
> 
> > El 20/12/23 a las 21:08, Rafael Laboissière escribió:
> > > > HOME := $(shell mktemp -d)
> > > > 
> > > > so that the same directory is never used twice between consecutive 
> > > > builds.
> > > 
> > > Yes, this is a much better solution. Thanks for the suggestion. I am 
> > > just wondering: is there a simple way to delete the temporary 
> > > directory after he build is finished ?
> > 
> > I don't know, but most people build packages in temporary/disposable 
> > chroots, 
> > so if the package just writes a few files which are also small, it's not 
> > something for which I would worry too much.
> 
> Yes, it not really a worrisome issue. However, I have just noticed that 
> the solution that you proposed with mktemp is a little bit intrusive. 
> Indeed, a new temporary directory is created at each invocation of 
> debain/rules, such that I end up with five /tmp/tmp.* directories after 
> package building, with only the last one being actually used. I will try 
> another approach, probably by changing the dh_octave_check script, which 
> is the one that eventually needs a writable $HOME directory.

Note that within the context of a shell script, the following ensures
that the directory is automatically deleted upon exit:

tmpdir=$(mktemp -d)
cleanup ()
{
rm -rf "${tmpdir}"
}
trap cleanup EXIT

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Antonio Terceiro]

On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> ## Upgrading using dpkg directly?
> 
> We already have quite a number of packages that use Conflicts to prevent
> file loss in upgrades in a very similar way to #1058937 (Ben's
> libnfsidmap1 bug) even in released versions of Debian. For instance,
> dhcpcd-base's Replaces were upgraded to Conflicts, see #1053657. If you
> employ dpkg, you can still experience the problem there.
> 
> Is it ok to call upgrade scenarios failures that cannot be reproduced
> using apt unsupported until we no longer deal with aliasing?

I think so, yes. I don't think it's likely that there are people doing
upgrades on running systems not using apt.

If there are, they already need to deal with doing the dpkg calls in the
right order anyway -- basically doing the apt dependency resolution by
hand -- that this is just another corner case that they need to handle;
there could be already Conflicts in there for other reasons than
/usr-merge.


signature.asc
Description: PGP signature

Bug#1058096: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

[Michael R. Crusoe]

On Thu, 21 Dec 2023 14:30:34 +0100 Andreas Tille  wrote:
> Control: tags -1 pending
>
> Hi,
>
> I intended to fix bug #1058096. Since I realised there is a new
> upstream version I was considering an upgrade which I pushed to Salsa.
> Unfortunately there are other test suite errors as you can see in Salsa
> CI[1]:


Hey Andreas,

Please don't upgrade python3-antlr4 ; its version should match that of 
the antlr4 package.


Yes, I know the versions don't currently match, and that antlr4 is a bit 
behind and has been for a while. But they come from the same source tree 
and further upgrades without matching will likely only make the 
situation worse.


Maybe you can add the above note to debian/README.Source after you 
reverse the upgrade?



--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058096: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

[Andreas Tille]

Control: tags -1 pending

Hi,

I intended to fix bug #1058096.  Since I realised there is a new
upstream version I was considering an upgrade which I pushed to Salsa.
Unfortunately there are other test suite errors as you can see in Salsa
CI[1]:

==
ERROR: test.__main__ (unittest.loader._FailedTest.test.__main__)
--
ImportError: Failed to import test module: test.__main__
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 419, in _find_test_path
module = self._get_module_from_name(name)
 
  File "/usr/lib/python3.11/unittest/loader.py", line 362, in 
_get_module_from_name
__import__(name)
  File "/usr/lib/python3.11/test/__main__.py", line 2, in 
main(_add_python_opts=True)
  File "/usr/lib/python3.11/test/libregrtest/main.py", line 671, in main
ns = _parse_args(sys.argv[1:], **kwargs)
 ^^^
  File "/usr/lib/python3.11/test/libregrtest/cmdline.py", line 402, in 
_parse_args
parser.error("unrecognized arguments: %s" % arg)
  File "/usr/lib/python3.11/test/libregrtest/cmdline.py", line 182, in error
super().error(message + "\nPass -h or --help for complete help.")
  File "/usr/lib/python3.11/argparse.py", line 2642, in error
self.exit(2, _('%(prog)s: error: %(message)s\n') % args)
  File "/usr/lib/python3.11/argparse.py", line 2629, in exit
_sys.exit(status)
SystemExit: 2
...
(see more in Salsa CI log[1])


Since this looks pretty much as if the reason for this failur is that
the PiPY downloadable tarball is lacking the directory test/ (which was
included in the currently packaged version) I checked Github for these
files and added these inside a multi-source tarball (a script to create
this tarball is commited as well).  While the first three tests that
were importing from test/ are passing now.  I've also fixed bug #1058096
in a patch[2] (thus tagging this bug pending).  However, that new version
has now new test failures which you can find in the new Salsa CI build
log which includes the (fixed) tests[3].  It starts with

==
ERROR: TestTokenStreamRewriter 
(unittest.loader._FailedTest.TestTokenStreamRewriter)
--
ImportError: Failed to import test module: TestTokenStreamRewriter
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 419, in _find_test_path
module = self._get_module_from_name(name)
 
  File "/usr/lib/python3.11/unittest/loader.py", line 362, in 
_get_module_from_name
__import__(name)
  File 
"/builds/python-team/packages/python3-antlr4/debian/output/source_dir/.pybuild/cpython3_3.11_antlr4/build/test/TestTokenStreamRewriter.py",
 line 8, in 
from mocks.TestLexer import TestLexer, TestLexer2
  File 
"/builds/python-team/packages/python3-antlr4/debian/output/source_dir/.pybuild/cpython3_3.11_antlr4/build/test/mocks/TestLexer.py",
 line 19, in 
class TestLexer(Lexer):
  File 
"/builds/python-team/packages/python3-antlr4/debian/output/source_dir/.pybuild/cpython3_3.11_antlr4/build/test/mocks/TestLexer.py",
 line 20, in TestLexer
atn = ATNDeserializer().deserialize(serializedATN())
  ^^
  File 
"/builds/python-team/packages/python3-antlr4/debian/output/source_dir/.pybuild/cpython3_3.11_antlr4/build/antlr4/atn/ATNDeserializer.py",
 line 28, in deserialize
self.checkVersion()
  File 
"/builds/python-team/packages/python3-antlr4/debian/output/source_dir/.pybuild/cpython3_3.11_antlr4/build/antlr4/atn/ATNDeserializer.py",
 line 50, in checkVersion
raise Exception("Could not deserialize ATN with version " + str(version) + 
" (expected " + str(SERIALIZED_VERSION) + ").")
Exception: Could not deserialize ATN with version   (expected 4).
...

and I have no idea how to fix this.

Kind regards
Andreas.


[1] https://salsa.debian.org/python-team/packages/python3-antlr4/-/jobs/5066603
[2] 
https://salsa.debian.org/python-team/packages/python3-antlr4/-/blob/master/debian/patches/assertEquals.patch?ref_type=heads
[3] https://salsa.debian.org/python-team/packages/python3-antlr4/-/jobs/5067599

-- 
http://fam-tille.de
#!/bin/sh
# The archive at PiPy is not featuring the test suite files
# This script is fetching the files and creates a tarball that is suited for 
multi-source tarball

UGIT=https://github.com/antlr/antlr4/
UVERSION=$(dpkg-parsechangelog --file ./changelog | grep '^Version' | cut -d' ' 
-f2  | cut -f1 -d-)
tarball=$(dpkg-parsechangelog --file ./changelog | awk '/^Source:/ {print 
$2}')_${UVERSION}.orig-tests.tar.gz
set -x

tmpdir=$(mktemp -d /tmp/python3-antlr4-testsuite)
curdir=$PWD
cd $tmpdir

git clone ${UGIT}
cd 

Processed: Bug#1058258 marked as pending in networking-sfc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058258 [src:networking-sfc] networking-sfc: FTBFS: KeyError: slice(1, 
None, None)
Added tag(s) pending.

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

Bug#1058258: marked as pending in networking-sfc

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058258 in networking-sfc 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/neutron-plugins/networking-sfc/-/commit/e215d2325a490376b3cb19c8678e8b2492f8292e


Add do-not-use-assertDictContainsSubset.patch (Closes: #1058258).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058258

Processed: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1058096 [src:python3-antlr4] python3-antlr4: FTBFS: AttributeError: 
'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 
'assertEqual'?
Ignoring request to alter tags of bug #1058096 to the same tags previously set

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

Processed: Bug#1058096 marked as pending in python3-antlr4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058096 [src:python3-antlr4] python3-antlr4: FTBFS: AttributeError: 
'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 
'assertEqual'?
Added tag(s) pending.

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

Bug#1058096: marked as pending in python3-antlr4

[Andreas Tille]

Control: tag -1 pending

Hello,

Bug #1058096 in python3-antlr4 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/python3-antlr4/-/commit/574cadec5ac04dc328898f4ab41ece529672a2eb


s/assertEquals/assertEqual/ in tests (Closes: #1058096)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058096

Processed: Re: Bug#1056460: python-bytecode's autopkg tests fail with Python 3.12 (armhf)

[Debian Bug Tracking System]

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

> severity 1056460 important
Bug #1056460 [src:python-bytecode] python-bytecode's autopkg tests fail with 
Python 3.12 (armhf)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1056460: python-bytecode's autopkg tests fail with Python 3.12 (armhf)

[Julian Gilbey]

severity 1056460 important
thanks

On Wed, Nov 22, 2023 at 02:29:47PM +0100, Matthias Klose wrote:
> Package: src:python-bytecode
> Version: 0.15.1-1
> Severity: important
> Tags: sid trixie
> User: debian-pyt...@lists.debian.org
> Usertags: python3.12
> 
> python-bytecode's autopkg tests fail with Python 3.12 (armhf):
> 
> [...]

Upstream don't have much idea of what might be causing this.  For the
time being, I have found that finishing a test early on armhf prevents
the crash from happening.  On the other hand, just disabling the test
does not, which is bizarre.

So downgrading the severity of this bug to important for now.

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1058318 https://github.com/pallets/werkzeug/issues/2704
Bug #1058318 [src:python-werkzeug] flask-login: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Set Bug forwarded-to-address to 
'https://github.com/pallets/werkzeug/issues/2704'.
> thanks
Stopping processing here.

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

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Gregor Riepl]

I don't see any other errors in the log except for the ast.Str 
deprecation warnings, and they all come from python-werkezug and not 
this package.


Reassiging the bug.
Upstream has already fixed this in in 2.3.5, by the way:
https://github.com/pallets/werkzeug/issues/2704

I can see that 3.0.1 is currently in experimental, but it would be 
enough to upgrade to the latest 2.x to fix this issue.


Please push a new python-werkzeug release ASAP.
Thank you!

Bug#1058142: marked as done (pysmi: FTBFS: ModuleNotFoundError: No module named 'imp')

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 13:55:07 +0100
with message-id <75352fc4-6e33-4c0b-a671-66e563a0a...@debian.org>
and subject line Re: r4d is marked for autoremoval from testing
has caused the Debian Bug report #1058142,
regarding pysmi: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)


-- 
1058142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysmi
Version: 0.3.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
> I: pybuild base:310: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> copying pysmi/compat.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> copying pysmi/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> copying pysmi/mibinfo.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> copying pysmi/error.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> copying pysmi/compiler.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> copying pysmi/debug.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi
> creating /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/localfile.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/httpclient.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/ftpclient.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/base.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/url.py -> 
> /<>/.pybuild/cpython3_3.12_pysmi/build/pysmi/reader
> copying pysmi/reader/callback.py -> 
> 

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> reassign 1058318 src:python-werkzeug
Bug #1058318 [src:flask-login] flask-login: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Bug reassigned from package 'src:flask-login' to 'src:python-werkzeug'.
No longer marked as found in versions flask-login/0.6.3-1.
Ignoring request to alter fixed versions of bug #1058318 to the same values 
previously set
> forwarded -1 https://github.com/pallets/werkzeug/issues/2704
Failed to set the forwarded-to-address of -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_forwarded did not pass regex check
.

> thanks
Stopping processing here.

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

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Paul Gevers]

Source: meson
Version: 1.2.3-1
Severity: serious
Control: close -1 1.3.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:meson has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable fails its 
own autopkgtest on arm64 and i386 (and armel, but that's not a regression).


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=meson



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3.0-2
Bug #1059223 [src:meson] src:meson: fails to migrate to testing for too long: 
fails autopkgtest on arm64 and i386
Marked as fixed in versions meson/1.3.0-2.
Bug #1059223 [src:meson] src:meson: fails to migrate to testing for too long: 
fails autopkgtest on arm64 and i386
Marked Bug as done

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

Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

[Paul Gevers]

Source: pv
Version: 1.8.0-3
Severity: serious
Control: close -1 1.8.5-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:pv has been trying to migrate for 31 days 
[2]. Hence, I am filing this bug. The version in unstable failed to 
build on armhf.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=pv



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:pv: fails to migrate to testing for too long: FTBFS on armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.8.5-1
Bug #1059222 [src:pv] src:pv: fails to migrate to testing for too long: FTBFS 
on armhf
Marked as fixed in versions pv/1.8.5-1.
Bug #1059222 [src:pv] src:pv: fails to migrate to testing for too long: FTBFS 
on armhf
Marked Bug as done

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

Bug#1059220: src:restic: fails to migrate to testing for too long: new Build-Depends is no migration candidate

[Paul Gevers]

Source: restic
Version: 0.16.0-1
Severity: serious
Control: close -1 0.16.2-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:restic has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable has a new 
Build-Depends that isn't ready to migrate yet: 
golang-github-backblaze-blazer. Please ensure it migrates.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=restic



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:restic: fails to migrate to testing for too long: new Build-Depends is no migration candidate

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.16.2-1
Bug #1059220 [src:restic] src:restic: fails to migrate to testing for too long: 
new Build-Depends is no migration candidate
Marked as fixed in versions restic/0.16.2-1.
Bug #1059220 [src:restic] src:restic: fails to migrate to testing for too long: 
new Build-Depends is no migration candidate
Marked Bug as done

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

Bug#1059154: marked as done (gem2deb: autopkgtest failures [PATCH])

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 12:49:01 +
with message-id 
and subject line Bug#1059154: fixed in gem2deb 2.2.1
has caused the Debian Bug report #1059154,
regarding gem2deb: autopkgtest failures [PATCH]
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.)


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

Package: gem2deb
Version: 2.2
Severity: serious
Tags: patch


Hello, in Ubuntu the following was added to fix an autopkgtest failure

gem2deb (2.2ubuntu1) noble; urgency=medium

  * d/t/control: add fakeroot to the gem2deb test.
The test is failing due to fakeroot not being installed. It probably
started to happen because the fakeroot dependency was dropped from
devscripts recently.

 -- Danilo Egea Gondolfo   Thu, 14 Dec 2023 
09:07:59 +


Thanks for considering the patch.

--- gem2deb-2.2/debian/tests/control2023-10-19 22:34:35.0 +0200
+++ gem2deb-2.2ubuntu1/debian/tests/control 2023-12-14 10:07:59.0 
+0100
@@ -3,7 +3,7 @@
 Restrictions: rw-build-tree allow-stderr
 
 Tests: gem2deb

-Depends: gem2deb, build-essential, moreutils
+Depends: fakeroot, gem2deb, build-essential, moreutils
 Restrictions: allow-stderr
 
 Tests: dh-make-ruby




OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gem2deb
Source-Version: 2.2.1
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated gem2deb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Dec 2023 08:34:52 -0300
Source: gem2deb
Architecture: source
Version: 2.2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1059154
Changes:
 gem2deb (2.2.1) unstable; urgency=medium
 .
   [ Danilo Egea Gondolfo ]
   * d/t/control: add fakeroot as a dependency of gem2deb test
 (Closes: #1059154)
Checksums-Sha1:
 6b3260c5ef53bd044cf2d250f95758db0faed582 2317 gem2deb_2.2.1.dsc
 bad939cb7b30ba6a54c5c67bbe6613711ff6c3a3 79876 gem2deb_2.2.1.tar.xz
 ccaf7a79d6cbd233ac7fff40a1a17e9b9ae33fb9 13347 gem2deb_2.2.1_source.buildinfo
Checksums-Sha256:
 306b673258a4960fcf83acd4a3f70605c12a38d433b690eb5bc7ba521c57a174 2317 
gem2deb_2.2.1.dsc
 a1a568470a5c57fea30559a955d00562c4ff54f5ddd9030b630dcea38d1223f4 79876 
gem2deb_2.2.1.tar.xz
 ad876cf1170996e09da04fb7b8496498ddb278a1d13611543644c7de0bd73030 13347 
gem2deb_2.2.1_source.buildinfo
Files:
 1aedbf4baf5d4573e5e9c8bf11d97d53 2317 ruby optional gem2deb_2.2.1.dsc
 dd3845a92875adb4bed748fad48e48ed 79876 ruby optional gem2deb_2.2.1.tar.xz
 11e566a44b4b264e716ae575a98d4f55 13347 ruby optional 
gem2deb_2.2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmWEM8YACgkQ/A2xu81G
C96wHRAAhbNw2iEBp7xOxsq731raMhKfupx3I1D341y8AgFKTX60dj87VX7RUbbI
hL223pFWIZEEJdHI8pkiTVw+ptIs3bd0o9VmaliQhpLoxQNjUPjJFQ8dE6KFgEsT
P58oFYmfGpUm/8QUgYcftZe1nXxKhWfUS1F2atBq/6LQaY4vzEI6WpHnPLDPnVBg
ogBTPGfAk/qbZqkV61xF3ah4Nd9R8d/nDkMSiveM3YjlYeTvX0fvuC7RyNPzP50R
ZCiiYoK3u5hIndpIRS9IpKiEjwq0nKoyqB94p2u6ivFLbrkKjr/Od2DDv9LU+rxz
C0lnSCapJD2f+EMOe6Gh8es4DaVXa549DeEdqnYLAacb9Tiu7qBFZ760oWR+osh8
oZE/BgujGNMGEPvHpkNM3EdFyVTPOrgEJNhlTw/bMhhudWtZPveSD/5xPBBHi4nx
19lr0+XEOWYx/tlC2MISTLvRb0RED/+jLp+JF8tP8yBTF940itYrXEAegrqrxjF/
M/7zHE6HUoSc1I9HvNWN+Boe6d4L6GtJYPtq3Hu/2/sk8BQVWh8ZBLPfFP8vyLJh
LxyscdWeKVKs4R5ZLbNq8Vepy2WHZrK4ulYKCpolqn34ws5mnIb+eWmt+bV8IfTi
QIJryIgdBpB5NRGKCPm9S2rnRdyTpvnMlJB/jC0jO8g6S38zbzY=
=tJGK
-END PGP SIGNATURE End Message ---

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

[Marc Haber]

On Mon, Dec 18, 2023 at 10:09:10AM +0100, Marc Haber wrote:
> Thanks for the work, I was never able to fully grasp the issue and the
> inner workings of the solution, and thank you for allowing me to remain
> silent during the process of finding and implementing the solution.

I'd like to report that it Works For Me. I downgraded molly-guard and
systemd to trixie and then did an upgrade, which worked.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Christoph Berg]

Re: Helmut Grohne
> Is it ok to call upgrade scenarios failures that cannot be reproduced
> using apt unsupported until we no longer deal with aliasing?
> 
> If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
> with no action calling the scenario unsupported.

I think we should only deal with problems that can reasonably happen
in practice. If an extra hammer is required to hit the problem, we
should not spend extra effort on it.

Christoph

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Helmut Grohne]

Hi,

this installment serves a dual purpose. Let me first give an update of
the status quo and then pose a consensus question on how we want to deal
with a particular problem.

I Cc d-release@l.d.o as upgrades are an integral part of releases.
I Cc d-ctte@l.d.o for advisory feedback with experience due to earlier
decisions on merged-/usr.

# Status

As I detailed earlier, diversions have been proving more difficult than
anticipated. I spent significant time on molly-guard to get to a working
mitigation and thanks to Francois and Daniel, all of the diverters of
/sbin/halt and others have been updated in experimental for wider
testing. This is looking promising and passing all testing that has been
performed thus far.

Meanwhile Chris Hofstaedler and kind folks in Cambridge worked a lot on
M-A:same shared file loss (DEP17 P7) and got us down to one
(reintroduced) issue.  Pending further reintroductions, this aspect is
done. Cool! I've since uploaded debhelper and dh_installudev will now
also install to /usr. udevdir in udev.pc has been changed in a NEW
upload to experimental as well and is expected to hit unstable before
too long (thanks Michael and Luca).

Earlier, I requested a pause of /usr merges. Since we have a better
understanding and solutions that seem to be working now, I am happy for
you to move stuff again more widely. For moves involving diversions in
any way, consider having me review your change ahead of upload.

At the time of this writing, there are 1237 source packages in unstable
that still ship something aliased. This is the number we need to get
down to 0 for trixie. Of these 860 involve a systemd unit and of these
761 only have systemd units aliased many of which can be converted by a
no-change upload due to changed debhelper and systemd.pc behaviour.

# The problem with conflicts

The idea in DEP17 was to use Conflicts as a mitigation strategy in
agreement with a naive reading of Debian policy. As it turns out, that
doesn't exactly match reality (#1057199 debian-policy) and there are
situations where files can be lost despite Conflicts having been
declared. In theory, this subtlety should be irrelevant and
unobservable, but aliasing (which breaks dpkg's assumptions) makes this
observable.

We move a file from / to /usr in $PKGA.

AND one of

The file is also being moved to a different package (causing DEP17 P1).

OR

The file is being diverted (causing DEP17 P3).

AND

The mitigation involves declaring a Conflict for unpack ordering (i.e.
M7 for P1 or M18 for P3).

AND one of

The upgrade is being performed using a direct dpkg invocation
without apt in a way that unpacks the package declaring the conflict
before the conflicted package is removed. Example: #1058937 (Ben's
libnfsidmap1 bug)

OR

The involved packages declare a mutual conflict (or mutual conflicts
+ breaks) and therefore apt invokes dpkg as in the earlier point.
Example: An earlier version of the molly-guard mitigation declared
versioned Breaks for systemd-sysv.

This condition is complex, so let me try to break it down into something
simpler. We'll have somewhere between 20 and 100 instances of P1 + P3 I
guess and we aimed for mitigating most of them using Conflicts (i.e.
first two conditions). The horny part is the last one. It basically says
that as long as we only ever use apt and avoid mutual conflicts, the
issue is not practically observable.

That mutual conflict condition is delicate on its own. There are
basically two ways to trigger it. The way my molly-guard patch did it
was having two versioned Conflicts or Breaks declarations. I checked the
archive and there is no instance of any package combination doing this.
Hypothetically, another way to trigger this is unversioned Conflicts
combined with a package that drops Provides in a later version (thanks
David), but we haven't seen any practical instance and I haven't figured
a good way to gauge this problem yet.

## Options (combinations possible)

When mitigating P1, we can opt for protective diversions (M8) instead of
Conflicts (M7), though that is more fragile.

When mitigating P3, we can avoid the mutual conflicts. For molly-guard
that has been more involved, but it seems manageable. For other
packages (that do not need to access diverted files), it becomes
simpler.

We can restore lost files in a postinst. For this to work, we must
duplicate (e.g. hard link) affected files in the data.tar.
Example: #1057220 (systemd-sysv upgrade file loss)
Note that this approach is not policy compliant for essential packages
as they must work when unpacked and this is relevant for gzip being
diverted by zutils for instance.

We can introduce "barrier" packages (one or more) and have them enforce
conflicting packages removed before the conflictor being unpacked
(thanks Julian).

We can - and this is the crux of the matter - argue that upgrading with
bare dpkg is unsupported and you get to keep the pieces if you do so
anyway.

Processed: Re: Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Debian Bug Tracking System]

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

> retitle 1059168 flaky autopkgtest
Bug #1059168 [nodejs] autopkgtest failures on i386
Changed Bug title to 'flaky autopkgtest' from 'autopkgtest failures on i386'.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was elb...@debian.org).
> usertag 1059168 flaky
There were no usertags set.
Usertags are now: flaky.
> thanks
Stopping processing here.

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

Bug#1059168: Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Paul Gevers]

retitle 1059168 flaky autopkgtest
user debian...@lists.debian.org
usertag 1059168 flaky
thanks
BCC: control@b.d.o

Hi,

On 21-12-2023 10:04, Jérémy Lal wrote:
Thank you for https://bugs.debian.org/1059168 



I noticed "Marked as found in versions nodejs/18.19.0+dfsg-6 and reopened."
while the test is flaky, retrying it will make it pass, so the bug is 
not as important as it seems.
And indeed, https://tracker.debian.org/pkg/zlib 
 is no longer blocked by nodejs.


It happens that I typically file bugs about flaky tests with severity 
serious with the following reasoning:

"""
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.
"""

Having said that, I hardly ever fight over the severity if the 
maintainer(s) drop severity. It depends a bit on how flaky the test is, 
passing 1/3 or worse is really bad, passing more than 9/10 can be 
defended as acceptable but ideally should be fixed. My personal boundary 
for filing flaky bugs seems to lay around 1/5 to failures.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Jérémy Lal]

Le jeu. 21 déc. 2023 à 08:59, Paul Gevers  a écrit :

> Hi,
>
> On 20-12-2023 23:08, Jérémy Lal wrote:
> > I did the one for burp.
>
> Thanks for that.
>
> > Dolfin has active maintainers, though.
>
> I think I need to file a "flaky autopkgtest" bug report against dolfin.


Thank you for https://bugs.debian.org/1059168

I noticed "Marked as found in versions nodejs/18.19.0+dfsg-6 and reopened."
while the test is flaky, retrying it will make it pass, so the bug is not
as important as it seems.
And indeed, https://tracker.debian.org/pkg/zlib is no longer blocked by
nodejs.

Jérémy

Bug#1056457: [Debichem-devel] Bug#1056457: python-ase's autopkg tests fail with Python 3.12

[s3v]

Hi,

On Thu, 21 Dec 2023 08:39:54 +0200 Andrius Merkys  wrote:
> Is there a way to ignore DeprecationWarnings, but leave them in to the
> output? They are quite helpful to see, but not worth failing the build
> at the time being.
>

You're right, deprecation outputs are useful.
I've just tried by commenting "error" in ase/test/pytest.ini for stop
treating warnings as errors. Outputs are in place and tests don't fail
as well.


= warnings 
summary ==
...
...
test_forcecurve.py::test_forcecurve
  /usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: DeprecationWarning: 
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in 
a future version. Use timezone-aware objects
to represent datetimes in UTC: datetime.datetime.fromtimestamp(timestamp, 
datetime.UTC).
    EPOCH = datetime.datetime.utcfromtimestamp(0)

test_parsemath.py: 109 warnings
constraints/test_parameteric_constr.py: 66 warnings
fio/test_aims_io.py: 66 warnings
  
/build/python-ase-3.22.1/.pybuild/cpython3_3.12_ase/build/ase/utils/parsemath.py:146:
 DeprecationWarning: ast.Num is deprecated and will be removed in Python 3.14; 
use ast.Constant instead
    if isinstance(node, ast.Num):  # 

test_parsemath.py: 50 warnings
constraints/test_parameteric_constr.py: 64 warnings
fio/test_aims_io.py: 45 warnings
  
/build/python-ase-3.22.1/.pybuild/cpython3_3.12_ase/build/ase/utils/parsemath.py:147:
 DeprecationWarning: Attribute n is deprecated and will be removed in Python 
3.14; use value instead
    return node.n



Thanks for maintaining python-ase!

Bug#1058373: marked as done (python-oslotest: FTBFS: failed tests)

[Debian Bug Tracking System]

Your message dated Thu, 21 Dec 2023 08:40:26 +
with message-id 
and subject line Bug#1058373: fixed in python-oslotest 1:4.5.0-5
has caused the Debian Bug report #1058373,
regarding python-oslotest: FTBFS: failed tests
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.)


-- 
1058373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslotest
Version: 1:4.5.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + echo WARNING: --no-py2 is deprecated, and always on.
> WARNING: --no-py2 is deprecated, and always on.
> + shift
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = no ]
> + [ no = yes ]
> + [ 3.12 = disabled ]
> + echo 3.12
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -x /usr/bin/python3-stestr ]
> + STESTR=stestr
> + rm -rf .stestr
> + PYTHON=python3.12 stestr run --parallel --subunit
> + subunit2pyunit
> oslotest.tests.unit.test_modules.CreateDisableModuleTest.test_disable_module
> oslotest.tests.unit.test_modules.CreateDisableModuleTest.test_disable_module 
> ... FAIL
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_default
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_default 
> ... ok
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_debug
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_debug
>  ... ok
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_debug_int
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_debug_int
>  ... ok
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_log_capture
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_log_capture
>  ... ok
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_trace_int
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_trace_int
>  ... ok
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_warning
> oslotest.tests.unit.test_log.ConfigureLoggingTestCase.test_fake_logs_with_warning
>  ... ok
> oslotest.tests.unit.test_base.TestTempFiles.test_create_bad_encoding
> oslotest.tests.unit.test_base.TestTempFiles.test_create_bad_encoding ... ok
> oslotest.tests.unit.test_base.TestTempFiles.test_create_unicode_files
> oslotest.tests.unit.test_base.TestTempFiles.test_create_unicode_files ... ok
> oslotest.tests.unit.test_base.TestTempFiles.test_create_unicode_files_encoding
> oslotest.tests.unit.test_base.TestTempFiles.test_create_unicode_files_encoding
>  ... ok
> oslotest.tests.unit.test_base.TestTempFiles.test_create_unicode_files_multi_encoding
> oslotest.tests.unit.test_base.TestTempFiles.test_create_unicode_files_multi_encoding
>  ... ok
> oslotest.tests.unit.test_base.TestTempFiles.test_prefix
> oslotest.tests.unit.test_base.TestTempFiles.test_prefix ... ok
> oslotest.tests.unit.test_base.TestTempFiles.test_wrong_length
> oslotest.tests.unit.test_base.TestTempFiles.test_wrong_length ... ok
> oslotest.tests.unit.test_base.TestManualMock.test_mock_patch_manually
> oslotest.tests.unit.test_base.TestManualMock.test_mock_patch_manually ... ok
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_create_bad_encoding
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_create_bad_encoding
>  ... ok
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_create_unicode_files
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_create_unicode_files
>  ... ok
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_create_unicode_files_encoding
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_create_unicode_files_encoding
>  ... ok
> oslotest.tests.unit.test_createfile.CreateFileWithContentTest.test_ext
> 

Processed: Bug#1058531 marked as pending in heat

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058531 [src:heat] heat: FTBFS: AttributeError: 'FileFinder' object has no 
attribute 'find_module'
Added tag(s) pending.

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

Bug#1058531: marked as pending in heat

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058531 in heat 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/heat/-/commit/8a0a2d4c8dcf6dd78b63ec3a186bf4774c7a6a43


* Add patches for Python 3.12 fixes (Closes: #1058531):
- find_spec-not-find_module.patch
- py3.12-deprecated-importlib-apis.patch
- py3.12-use-assert_has_calls.patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058531

Processed: Bug#1058373 marked as pending in python-oslotest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058373 [src:python-oslotest] python-oslotest: FTBFS: failed tests
Added tag(s) pending.

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

Bug#1058373: marked as pending in python-oslotest

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058373 in python-oslotest 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/oslo/python-oslotest/-/commit/956daf69a0b5de63bb3c7905dee3324657ff65bf


Add py3.12-fix-modules-fixture.patch (Closes: #1058373).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058373

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Paul Gevers]

Hi,

On 20-12-2023 23:08, Jérémy Lal wrote:

I did the one for burp.


Thanks for that.


Dolfin has active maintainers, though.


I think I need to file a "flaky autopkgtest" bug report against dolfin.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature