Bug#1028434: kodi: FTBFS in bullseye (fatal error: date/tz.h: No such file or directory)

[Alban Browaeys]

 date/tz.h: No such file or directory

This date/tz.h comes from kodi source directory ./libdate-tz-
embedded/include/date/tz.h

It is not included in the bullseye debian/rules but in the bullseye-
backports one it is by 
DATE_COMPONENT = libdate-tz-embedded
KODI_OPTS=\
(...)
-DDATE_INCLUDE_DIR:PATH=$(CURDIR)/$(DATE_COMPONENT)/include


override_dh_auto_configure:
(...)
dh_auto_configure -- $(KODI_OPTS)





my pbuilder dh_auto_configure (bullseye build environment but building
bullseye-backports kodi 19.4):
dh_auto_configure -- -DVERBOSE=1 -DUSE_LTO=5 -
DCMAKE_BUILD_TYPE=RelWithDebInfo -DENABLE_AIRTUNES=ON -DENABLE_ALSA=ON
-DENABLE_AVAHI=ON -DENABLE_BLURAY=ON -DENABLE_CEC=ON -DENABLE_DBUS=ON -
DENABLE_DEBUGFISSION=OFF -DENABLE_DVDCSS=OFF -DENABLE_EVENTCLIENTS=ON -
DENABLE_INTERNAL_CROSSGUID=OFF -DENABLE_INTERNAL_DATE=OFF -
DENABLE_INTERNAL_FFMPEG=OFF -DENABLE_INTERNAL_KISSFFT=OFF -
DENABLE_MICROHTTPD=ON -DENABLE_MYSQLCLIENT=ON -DENABLE_NFS=ON -
DENABLE_OPTICAL=ON -DENABLE_PULSEAUDIO=ON -DENABLE_SMBCLIENT=ON -
DENABLE_UDEV=ON -DENABLE_UPNP=ON -DENABLE_VAAPI=ON -DENABLE_VDPAU=ON -
DENABLE_XSLT=ON -
DLIBDVDREAD_URL=tools/depends/target/libdvdread/libdvdread-$(grep
VERSION tools/depends/target/libdvdread/DVDREAD-VERSION | sed
's/^[^=]*=//').tar.xz -
DLIBDVDNAV_URL=tools/depends/target/libdvdnav/libdvdnav-$(grep VERSION
tools/depends/target/libdvdnav/DVDNAV-VERSION | sed
's/^[^=]*=//').tar.xz -DENABLE_LIRCCLIENT=ON -DNEON=False -
DCORE_PLATFORM_NAME="x11 wayland gbm" -DAPP_RENDER_SYSTEM=gl -
DDATE_LIBRARY_RELEASE:FILEPATH=/build/kodi-19.4+dfsg2/lib/date/libdate-
tz.a -DDATE_INCLUDE_DIR:PATH=/build/kodi-19.4+dfsg2/libdate-tz-
embedded/include  -DWITH_ARCH=x86_64-linux



your dh_auto_configure:
dh_auto_configure -- -DVERBOSE=1 -DUSE_LTO=1 -
DCMAKE_BUILD_TYPE=RelWithDebInfo -DENABLE_AIRTUNES=ON -DENABLE_ALSA=ON
-DENABLE_AVAHI=ON -DENABLE_BLURAY=ON -DENABLE_CEC=ON -DENABLE_DBUS=ON -
DENABLE_DVDCSS=OFF -DENABLE_EVENTCLIENTS=ON -
DENABLE_INTERNAL_CROSSGUID=OFF -DENABLE_INTERNAL_FFMPEG=OFF -
DENABLE_MICROHTTPD=ON -DENABLE_MYSQLCLIENT=ON -DENABLE_NFS=ON -
DENABLE_OPTICAL=ON -DENABLE_PULSEAUDIO=ON -DENABLE_SMBCLIENT=ON -
DENABLE_UDEV=ON -DENABLE_UPNP=ON -DENABLE_VAAPI=ON -DENABLE_VDPAU=ON -
DENABLE_XSLT=ON -DDATE_URL=tools/depends/target/date/libdate-tz-$(grep
VERSION tools/depends/target/date/DATE-VERSION | sed
's/^[^=]*=//').tar.xz -
DLIBDVDREAD_URL=tools/depends/target/libdvdread/libdvdread-$(grep
VERSION tools/depends/target/libdvdread/DVDREAD-VERSION | sed
's/^[^=]*=//').tar.xz -
DLIBDVDNAV_URL=tools/depends/target/libdvdnav/libdvdnav-$(grep VERSION
tools/depends/target/libdvdnav/DVDNAV-VERSION | sed
's/^[^=]*=//').tar.xz -DENABLE_LIRCCLIENT=ON -DNEON=False -
DCORE_PLATFORM_NAME="x11 wayland gbm" -DAPP_RENDER_SYSTEM=gl


Note the missing:
-DDATE_LIBRARY_RELEASE:FILEPATH=/build/kodi-
19.4+dfsg2/lib/date/libdate-tz.a -DDATE_INCLUDE_DIR:PATH=/build/kodi-
19.4+dfsg2/libdate-tz-embedded/include


Those were added to the bullseye-backports branch
https://salsa.debian.org/multimedia-team/kodi-media-center/kodi/-/commit/e7b14cb2206bebd5668f33a5e076fde124721898

So maybe this should be backported to bullseye versoin as date/tz.h is
not provided by any Debian package in bullseye (and maybe in unrelated
libhowardhinnant-date-dev in bullseye-backports and above).

Cheers,
Alban

Bug#1024820: marked as done (emperor: FTBFS/autopkgtest fail with pandas 1.5)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2023 07:19:10 +
with message-id 
and subject line Bug#1024820: fixed in emperor 1.0.3+ds-7
has caused the Debian Bug report #1024820,
regarding emperor: FTBFS/autopkgtest fail with pandas 1.5
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.)


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

Package: python3-emperor
Version: 1.0.3+ds-4
Control: block 1022571 by -1

Tests fail with pandas 1.5 (currently in experimental).

Build log:
https://launchpadlibrarian.net/633828020/buildlog_ubuntu-lunar-amd64.emperor_1.0.3+ds-4_BUILDING.txt.gz
Autopkgtest log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/e/emperor/28542504/log.gz
--- End Message ---
--- Begin Message ---
Source: emperor
Source-Version: 1.0.3+ds-7
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated emperor 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, 26 Jan 2023 07:54:27 +0100
Source: emperor
Architecture: source
Version: 1.0.3+ds-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1024820
Changes:
 emperor (1.0.3+ds-7) unstable; urgency=medium
 .
   * Team upload.
   * Section: python
   * DEP3
   * Add upstream patch fpr pandas 1.5 compatibility
 Closes: #1024820
   * Drop unused lintian-overrides
   * Fix description
Checksums-Sha1:
 cbee6017082ad9a7dff67f7f24986dc9114fb4c3 2552 emperor_1.0.3+ds-7.dsc
 29f693469390eb02551279e89812e2e8b1c4ba2c 7188 emperor_1.0.3+ds-7.debian.tar.xz
 4e1c21007d54ac362a7d881fc4f3dc44d2effecd 15451 
emperor_1.0.3+ds-7_amd64.buildinfo
Checksums-Sha256:
 facd3b2ef9f8af7c8fcd1aa15cc635cca24eb1531e8956d3274d15aa5494274c 2552 
emperor_1.0.3+ds-7.dsc
 860500af0f7c971c357338b860bae6450bfd20fbd618b9cc88236b192d54f915 7188 
emperor_1.0.3+ds-7.debian.tar.xz
 13be895605093359ecf520d5041bfbf373e8da0cb04e97da67dc8a6883aba435 15451 
emperor_1.0.3+ds-7_amd64.buildinfo
Files:
 b29417043cb952223d46dfd641a8eb94 2552 science optional emperor_1.0.3+ds-7.dsc
 85fd08a927cbff3f9496774c1d251e32 7188 science optional 
emperor_1.0.3+ds-7.debian.tar.xz
 55f7f78609ca0cbf27e5ce78881c2240 15451 science optional 
emperor_1.0.3+ds-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPSJzMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFuJA//SDeXoCiJgjpdZ9ybleoJw9Y28aGQNItV
7JsE4u4ZTK+LDWXqGMOkFRZlxq8573vG7fJBKtsMEokW6zLupucSyPtHkWSYtD79
Sqn6pGw9BvSHxyhtC4elQAhegEp6qo5krj6mFrXL7uERpKnC9FXFHKUB8U07NkSr
i/f79YGV2PZGhuW6R9K8oCutaEFIW0rsQwyuE/+f6TbVNEX0iVX9+3aEslFQQL0z
V7k+ap12ad3uj7BMCeXOS9eicYeRR2jheI3duLGnVhvwAIz4h9eVkpXkQ2v5O5u0
65DM1q7U1IEhWS/rQa/k0JQyn4yIAjmY92VyQpbiJ5cXXvB6RfdRIl1dj9tePnhA
JcG9dPj+UnIiYVcrLd3dPKd2D/fg/2H25FfHQf9pQnSIXfutAzc5NajDMQiLSSTG
ZUomEc5kkR9My6eDpJ3hCx23RMHoS/DuKxLyVq92ZLelZeX7OSC6UazoUgjmGoPN
je/Q2sbCiGerHKW4qy/ID4ezfkxu5nZs7HyR7WnAkX44CHdQx8UdYt32aneIaXep
HTn0Zjoqdvfpcrk0RbqYi0e073NvXmE9brXUmC4FXwf1wZj2d/eCRtnHiz+cWYzH
Ha0IAhCr7O5fEr/uCPc110j0oGXvXncLHBWkek/H84D2ENg25pf7ZeTWnfGm+wDe
FPpQApzVRkY=
=e8MN
-END PGP SIGNATURE End Message ---

Bug#1029114: marked as done (git: CVE-2022-23521 CVE-2022-41903)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2023 06:34:31 +
with message-id 
and subject line Bug#1029114: fixed in git 1:2.39.1-0.1
has caused the Debian Bug report #1029114,
regarding git: CVE-2022-23521 CVE-2022-41903
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.)


-- 
1029114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.30.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:2.39.0-1

Hi,

The following vulnerabilities were published for git.

CVE-2022-23521[0]:
| gitattributes parsing integer overflow

CVE-2022-41903[1]:
| heap overflow in `git archive` and `git log --format`

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-23521
https://www.cve.org/CVERecord?id=CVE-2022-23521
[1] https://security-tracker.debian.org/tracker/CVE-2022-41903
https://www.cve.org/CVERecord?id=CVE-2022-41903

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.39.1-0.1
Done: Aron Xu 

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated git 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, 26 Jan 2023 13:43:04 +0800
Source: git
Architecture: source
Version: 1:2.39.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Nieder 
Changed-By: Aron Xu 
Closes: 1029114
Changes:
 git (1:2.39.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream stable release (Closes: #1029114)
 Fixes CVE-2022-23521 and CVE-2022-41903.
Checksums-Sha1:
 e823bf4a2ca4769c92ab7ae79ea79a892d7401c9 2459 git_2.39.1-0.1.dsc
 3a35d0571c517f7f4cb2e1dfbd315e7c32023e2b 7160744 git_2.39.1.orig.tar.xz
 d93598b6386ea611a7dd8e21883fb38384fc0701 739356 git_2.39.1-0.1.debian.tar.xz
 348693a4dfb3f49a4063f68e07108b2553be4c6d 7405 git_2.39.1-0.1_source.buildinfo
Checksums-Sha256:
 87f9907d0f775692103217101fb7a08a37f3ba688f03d3f12ae3d51e7dc4c4a7 2459 
git_2.39.1-0.1.dsc
 40a38a0847b30c371b35873b3afcf123885dd41ea3ecbbf510efa97f3ce5c161 7160744 
git_2.39.1.orig.tar.xz
 2cf3a5cf45404a182e2b8dda108958ce9de37403d662a83d41d8d125dfc0e8d2 739356 
git_2.39.1-0.1.debian.tar.xz
 ff930860e8264e8bb111da240aff4f35819d9077505a1705b522c3607b5e73b9 7405 
git_2.39.1-0.1_source.buildinfo
Files:
 48bf61441a16307f212a03f8e1eb7d2f 2459 vcs optional git_2.39.1-0.1.dsc
 74b450a513504fd7b3f5016f80de5e54 7160744 vcs optional git_2.39.1.orig.tar.xz
 1754ad5f621314bcd24b6d8590bcac7e 739356 vcs optional 
git_2.39.1-0.1.debian.tar.xz
 327ca040f49e099bce5f5bf190956a86 7405 vcs optional 
git_2.39.1-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhhz+aYQl/Bp4OTA7O1LKKgqv2VQFAmPSGMkACgkQO1LKKgqv
2VQn1gf9F4pwWr7H0Cx6ClZh69yUSr74DHZxUr2sqgROFePXHNdzUSsFEo/3UWR8
5vX0nnv8s2sxPIgt09ItLXWSnfkYQ/sph9FaPzSNm67cAcSxrXD8wx2bq4hlZN96
Y5sBjLvU87sX87ksO4mGvTD2TRtxyllkdjgXspa3tEG2vblOUzyqh6xiWhazZ1Ry
7ymnlRyYMHg0/D6sB23GC2KxGfrlJA1LweRQen22W7XJD0t+J3ieaJey6S52pem+
FIDeiEh9ZnkHXkSK3yq2ggRNHbef1kHaVHA/olFZl1V7n4wzpvFZBme5ye7nTFBe
fjBNWTrQiU039FzeDLflaQeD0tKGzQ==
=ChIa
-END PGP SIGNATURE End Message ---

Bug#1029597: Login is broken and URLs do not work

[Don Armstrong]

On Wed, 25 Jan 2023, William Desportes wrote:
> I suggested a FTP RM that was refused for now: #1028968

Thanks for the report; I agree with the removal.

[Note for future, the right approach is to file a bug against the
package first before requesting removal.]

-- 
Don Armstrong  https://www.donarmstrong.com

The smallest quantity of bread that can be sliced and toasted has yet
to be experimentally determined. In the quantum limit we must
necessarily encounter fundamental toast particles which the author
will unflinchingly designate here as "croutons".
 -- Cser, Jim. Nanotechnology and the Physical Limits of Toastability.
AIR 1:3, June, 1995.

Bug#1028994: [Pkg-mailman-hackers] Bug#1028994: mailman3: (autopkgtest) needs update for Python 3.11

[Sebastiaan Couwenberg]

On Tue, 17 Jan 2023 15:32:53 +0100 Pierre-Elliott Bécue wrote:

I intend to do a full sweep on mailman suite in the next week, so don't
worry too much! :)


How is that going?

mailman3 is the last major blocker for testing migration of 
python3-defaults.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: downgrading and forwarding

[Debian Bug Tracking System]

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

> severity 1028540 important
Bug #1028540 [xrdp] xrdp 0.9.21 black screen with cursor
Severity set to 'important' from 'critical'
> forwarded 1028540 https://github.com/neutrinolabs/xrdp/issues/2496
Bug #1028540 [xrdp] xrdp 0.9.21 black screen with cursor
Set Bug forwarded-to-address to 
'https://github.com/neutrinolabs/xrdp/issues/2496'.
> thanks
Stopping processing here.

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

Bug#1029661: Cannot authenticate with Google

[Josh Triplett]

Package: gcalcli
Version: 4.3.0-1
Severity: grave
Tags: upstream
X-Debbugs-Cc: j...@joshtriplett.org

Google no longer allows gcalcli to authenticate. Upstream recommends
manually creating a developer account and registering gcalcli as your
own app. This is a *much* more cumbersome setup process, and the simple
oauth2 workflow that gcalcli uses by default doesn't work with no
indication of why.

At a minimum, this should be documented and the flow for not having
authenticated yet should give better guidance to the user and not try an
authentication that won't work.

https://github.com/insanum/gcalcli/issues/580


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

Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 gcalcli depends on:
ii  python33.11.1-1
ii  python3-dateutil   2.8.2-1
ii  python3-googleapi  1.7.12-1
ii  python3-httplib2   0.20.4-3
ii  python3-oauth2client   4.1.3-3
ii  python3-parsedatetime  2.6-3
ii  python3-six1.16.0-4

Versions of packages gcalcli recommends:
pn  python3-vobject  

gcalcli suggests no packages.

-- no debconf information

Bug#1029660: nipype FTBFS: ModuleNotFoundError: No module named 'nibabel.trackvis'

[Nilesh Patra]

Package: nipype
Version: 1.7.1-2
Severity: serious

Dear Maintainer,

nipype is incompatible with nibabel 4.0 and FTBFS with several errors of
type:

| _ ERROR collecting interfaces/mrtrix/tests/test_auto_Tensor2Vector.py 
__
| ImportError while importing test module 
'/<>/nipype/interfaces/mrtrix/tests/test_auto_Tensor2Vector.py'.
| Hint: make sure your test modules/packages have valid Python names.
| Traceback:
| /usr/lib/python3.11/importlib/__init__.py:126: in import_module
|return _bootstrap._gcd_import(name[level:], package, level)
| ../nipype/interfaces/mrtrix/__init__.py:36: in 
|from .convert import MRTrix2TrackVis
| ../nipype/interfaces/mrtrix/convert.py:6: in 
|import nibabel.trackvis as trk
| E   ModuleNotFoundError: No module named 'nibabel.trackvis'

It has also been out of testing for quite sometime.

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

Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1029556: marked as done (espeak-ng: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2023 00:49:09 +
with message-id 
and subject line Bug#1029556: fixed in espeak-ng 1.51+dfsg-10
has caused the Debian Bug report #1029556,
regarding espeak-ng: autopkgtest regression
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.)


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

Source: espeak-ng
Version: 1.51+dfsg-9
Severity: serious
tags: patch

Hello, autopkgtests started to fail I presume since llvm-default change.
To fix, you need to depend on clang-rt when you use fsanitize=fuzzer)

clang++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.4x6n726o/downtmp/build.8AY/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o tests/dummy.o 
tests/dummy.cpp
/bin/bash ./libtool  --tag=CXX   --mode=link clang++  -g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.4x6n726o/downtmp/build.8AY/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -fsanitize=fuzzer 
-Wl,-z,relro -o tests/ssml-fuzzer.test tests/ssml_fuzzer_test-ssml-fuzzer.o 
tests/dummy.o -lespeak-ng  -lsonic
libtool: link: clang++ -g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.4x6n726o/downtmp/build.8AY/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -fsanitize=fuzzer 
-Wl,-z -Wl,relro -o tests/ssml-fuzzer.test tests/ssml_fuzzer_test-ssml-fuzzer.o 
tests/dummy.o  -lespeak-ng -lsonic
/usr/bin/ld: cannot find 
/usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.fuzzer-x86_64.a: No 
such file or directory
/usr/bin/ld: cannot find 
/usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.fuzzer_interceptors-x86_64.a:
 No such file or directory
/usr/bin/ld: cannot find 
/usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.ubsan_standalone-x86_64.a:
 No such file or directory
/usr/bin/ld: cannot find 
/usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.ubsan_standalone_cxx-x86_64.a:
 No such file or directory

This untested patch should do the trick:
 Tests: fuzz
 Architecture: amd64 arm64 i386
-Depends: @builddeps@, clang, libespeak-ng-dev
+Depends: @builddeps@, clang, clang-rt, libespeak-ng-dev

thanks

Gianfranco


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: espeak-ng
Source-Version: 1.51+dfsg-10
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated espeak-ng 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, 26 Jan 2023 01:09:47 +0100
Source: espeak-ng
Architecture: source
Version: 1.51+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Closes: 1029556
Changes:
 espeak-ng (1.51+dfsg-10) unstable; urgency=medium
 .
   * watch: Use API instead of releases page.
   * tests/control: Build-depend on libclang-rt-dev (Closes: Bug#1029556).
Checksums-Sha1:
 54d7dfef32b64982a4b747ac4be3bc5cf8463859 2628 espeak-ng_1.51+dfsg-10.dsc
 5a0c21bfa2fe8f9c4593337baf227756a69d33d8 46856 
espeak-ng_1.51+dfsg-10.debian.tar.xz
 160d981ec84c483c476ba98ee8d63c008a4cd134 9514 
espeak-ng_1.51+dfsg-10_source.buildinfo
Checksums-Sha256:
 deb8dc254f1b5631d05f5ded3e2790ce149013987b80fdfdc49b5d83cad9cc9d 2628 
espeak-ng_1.51+dfsg-10.dsc
 b55c7451d789c450dfe7f07055a2b79cd35a89921d8f9fc6ed201a37be621faf 46856 
espeak-ng_1.51+dfsg-10.debian.tar.xz
 ccb90a8a5d773754df878730fd0ae82e3640026ce8d2aab1ce918384b0c6e5d6 9514 
espeak-ng_1.51+dfsg-10_source.buildinfo
Files:
 ce7972a9c7dca59699311d14acca48d1 2628 sound optional espeak-ng_1.51+dfsg-10.dsc
 cb7b7cfe8d985964bddb87786105d932 46856 sound optional 
espeak-ng_1.51+dfsg-10.debian.tar.xz
 1c79020ef56618710ba34038f9a93f4a 9514 sound optional 
espeak-ng_1.51+dfsg-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEZTSF1IMOAGwT71n/aHTOWK4tfj8FAmPRxO8VHHN0aGliYXVs
dEBkZWJpYW4ub3JnAAoJEGh0zliuLX

Bug#1026479: marked as done (ruby-faraday-middleware: FTBFS: ERROR: Test "ruby3.1" failed: RuntimeError:)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2023 00:50:13 +
with message-id 
and subject line Bug#1026479: fixed in ruby-faraday-middleware 1.2.0-1
has caused the Debian Bug report #1026479,
regarding ruby-faraday-middleware: FTBFS: ERROR: Test "ruby3.1" failed: 
RuntimeError:
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.)


-- 
1026479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-faraday-middleware
Version: 1.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  RuntimeError:
>missing dependency for FaradayMiddleware::ParseYaml: cannot load such 
> file -- safe_yaml/load
>  # 
> /usr/share/rubygems-integration/all/gems/faraday-1.1.0/lib/faraday/dependency_loader.rb:20:in
>  `new'
>  # ./spec/spec_helper.rb:31:in `block in included'
>  # ./spec/spec_helper.rb:45:in `process'
>  # ./spec/unit/parse_yaml_spec.rb:24:in `block (3 levels) in  (required)>'
> 
> Finished in 0.58474 seconds (files took 0.90228 seconds to load)
> 260 examples, 9 failures
> 
> Failed examples:
> 
> rspec ./spec/unit/parse_yaml_spec.rb:49 # FaradayMiddleware::ParseYaml chokes 
> on invalid yaml
> rspec ./spec/unit/parse_yaml_spec.rb:64 # FaradayMiddleware::ParseYaml 
> SafeYAML options passes relevant options to SafeYAML load
> rspec ./spec/unit/parse_yaml_spec.rb:43 # FaradayMiddleware::ParseYaml with 
> regexp type matching ignores json body of incorrect type
> rspec ./spec/unit/parse_yaml_spec.rb:38 # FaradayMiddleware::ParseYaml with 
> regexp type matching parses json body of correct type
> rspec ./spec/unit/parse_yaml_spec.rb:5 # FaradayMiddleware::ParseYaml no type 
> matching doesn't change nil body
> rspec ./spec/unit/parse_yaml_spec.rb:9 # FaradayMiddleware::ParseYaml no type 
> matching returns false for empty body
> rspec ./spec/unit/parse_yaml_spec.rb:13 # FaradayMiddleware::ParseYaml no 
> type matching parses yaml body
> rspec ./spec/unit/parse_yaml_spec.rb:29 # FaradayMiddleware::ParseYaml with 
> preserving raw can opt out of preserving raw
> rspec ./spec/unit/parse_yaml_spec.rb:23 # FaradayMiddleware::ParseYaml with 
> preserving raw parses yaml body
> 
> Randomized with seed 20471
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> ./spec/integration/follow_redirects_spec.rb ./spec/unit/chunked_spec.rb 
> ./spec/unit/encode_json_spec.rb ./spec/unit/follow_redirects_spec.rb 
> ./spec/unit/mashify_spec.rb ./spec/unit/method_override_spec.rb 
> ./spec/unit/oauth2_spec.rb ./spec/unit/oauth_spec.rb 
> ./spec/unit/parse_dates_spec.rb ./spec/unit/parse_json_spec.rb 
> ./spec/unit/parse_marshal_spec.rb ./spec/unit/parse_xml_spec.rb 
> ./spec/unit/parse_yaml_spec.rb ./spec/unit/rashify_spec.rb 
> ./spec/unit/response_middleware_spec.rb failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/ruby-faraday-middleware_1.0.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: ruby-faraday-middleware
Source-Version: 1.2.0-1
Done: Daniel Leidert 

We believe that the bug you reported is fixed in the latest version of
ruby-faraday-middleware, 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 1026...@bugs.

Processed: Bug#1026479 marked as pending in ruby-faraday-middleware

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026479 [src:ruby-faraday-middleware] ruby-faraday-middleware: FTBFS: 
ERROR: Test "ruby3.1" failed: RuntimeError:
Added tag(s) pending.

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

Bug#1026479: marked as pending in ruby-faraday-middleware

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1026479 in ruby-faraday-middleware 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/ruby-team/ruby-faraday-middleware/-/commit/c67c1a2471b6796fd410a95d224abae7dea3114c


Fix build

  * d/control (Build-Depends): Add ruby-safe-yaml (closes: #1026479).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026479

Processed: tagging 1029556

[Debian Bug Tracking System]

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

> tags 1029556 + pending
Bug #1029556 [src:espeak-ng] espeak-ng: autopkgtest regression
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1028512: marked as done (python3-sqlmodel: Depends: python3-sqlalchemy (< 1.4.46) but 1.4.46+ds1-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2023 00:08:40 +
with message-id 
and subject line Bug#1028512: fixed in sqlmodel 0.0.8-4
has caused the Debian Bug report #1028512,
regarding python3-sqlmodel: Depends: python3-sqlalchemy (< 1.4.46) but 
1.4.46+ds1-1 is to be installed
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.)


-- 
1028512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sqlmodel
Version: 0.0.8-3
Severity: grave

The following packages have unmet dependencies:
 python3-sqlmodel : Depends: python3-sqlalchemy (< 1.4.46) but 1.4.46+ds1-1 is 
to be installed
--- End Message ---
--- Begin Message ---
Source: sqlmodel
Source-Version: 0.0.8-4
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated sqlmodel 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, 26 Jan 2023 00:51:55 +0100
Source: sqlmodel
Architecture: source
Version: 0.0.8-4
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Bastian Germann 
Closes: 1028512
Changes:
 sqlmodel (0.0.8-4) unstable; urgency=medium
 .
   * Team upload
   * Allow sqlalchemy dep version < 2.0 (Closes: #1028512)
Checksums-Sha1:
 a2db306a0a5017a0bf252ea5c4960d81c8a0ef52 2106 sqlmodel_0.0.8-4.dsc
 79aba224ff4140623acb7d6bb47aff091fdc87c3 4876 sqlmodel_0.0.8-4.debian.tar.xz
 002195257e9a96857f319eab556f88c0fbed6303 7920 sqlmodel_0.0.8-4_source.buildinfo
Checksums-Sha256:
 ed2a358d924fb3d9517cc63ca61101a85c0bbe0d68f92b624ec3b00f03751b28 2106 
sqlmodel_0.0.8-4.dsc
 462b32ca4c2934a0ddab9c754966713456b508148f13d3958ca74b65baea30fa 4876 
sqlmodel_0.0.8-4.debian.tar.xz
 7cf1bdf42910f2d04015c45a0dab08f86b3800ea887d65843c0ca7bdb4050af7 7920 
sqlmodel_0.0.8-4_source.buildinfo
Files:
 f3d9e6ddae701eb506575943f6e594c5 2106 python optional sqlmodel_0.0.8-4.dsc
 6a84eef56a64abfbd8fcde607f9c4e51 4876 python optional 
sqlmodel_0.0.8-4.debian.tar.xz
 bd0b123331609c3a2b084708e50bf55d 7920 python optional 
sqlmodel_0.0.8-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPRwdsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPpiC/4vcssMrb8elIF6U7x1w3wCskfbprStLYik
1kJfuWRuae3yBG5Zv7GbyxSEljfu0OhOhxAakF/RgRFzzvx8iiRCry7m84gNdWuI
pLH73XKlF9MnjnEJCTnqBi9IHAeyGZWi3t9bq6Bo18j8fVgk+KniRgLQ7F7PSfJE
weiPq+H69kLnPj63gHcLIBfS2Oz3NhmYlTprZPytXtyUhOcs425uRzXyziJCcB8X
rHHq8Xq8Fp0w8pQsTQGohw1oUa04Ymv+6lKjQ8wzMQElHNcZV7gIaiO7r3s8m3gE
OUnVRW/Aq+Un3Yv9KsM+y66PqpTMZezBMj0yyLn9ScBb6zAOEg4UrKbcTLVQzWn6
7q64hiFPzmtTg0E/ilfVB7h6FtML0T3IHuXdkfkRUDAVVmwbndS/iiRweq5mika4
/1ZDQn0gzFN11DNIW4ZOiBBVK/HvzvaP0p4UkyHQPgv8ZDz+qfxOWFjc3Xqlos02
AwGXnVhO/+jFUog06guvroJow4KqWHg=
=eDPP
-END PGP SIGNATURE End Message ---

Bug#1005631: marked as done (ruby-handlebars-assets: FTBFS: Failed to load /dev/null because it doesn't contain valid YAML hash)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2023 00:07:51 +
with message-id 
and subject line Bug#1005631: fixed in ruby-handlebars-assets 2:0.23.9+dfsg-1
has caused the Debian Bug report #1005631,
regarding ruby-handlebars-assets: FTBFS: Failed to load /dev/null because it 
doesn't contain valid YAML hash
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.)


-- 
1005631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-handlebars-assets
Version: 2:0.23.8+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p vendor/assets/javascripts
> ln -s /usr/share/javascript/handlebars/handlebars.js 
> vendor/assets/javascripts/handlebars.js
> ln -s /usr/share/javascript/handlebars.runtime/handlebars.runtime.js 
> vendor/assets/javascripts/handlebars.runtime.js
> dh_auto_build
>   dh_ruby --build
>dh_ruby --build
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=ruby
>   dh_ruby --test
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>dh_auto_install --destdir=debian/ruby-handlebars-assets/ 
> -O--buildsystem=ruby
>   dh_ruby --install 
> /<>/ruby-handlebars-assets-0.23.8\+dfsg/debian/ruby-handlebars-assets
>dh_ruby --install
> /usr/bin/ruby2.7 -S gem build --config-file /dev/null --verbose 
> /tmp/d20220212-715032-1jyqjgk/gemspec
> Failed to load /dev/null because it doesn't contain valid YAML hash
> WARNING:  vendor/assets/javascripts/handlebars.js is a symlink, which is not 
> supported on all platforms
> WARNING:  vendor/assets/javascripts/handlebars.runtime.js is a symlink, which 
> is not supported on all platforms
> WARNING:  open-ended dependency on tilt (>= 1.2) is not recommended
>   if tilt is semantically versioned, use:
> add_runtime_dependency 'tilt', '~> 1.2'
> WARNING:  open-ended dependency on sprockets (>= 2.0.0) is not recommended
>   if sprockets is semantically versioned, use:
> add_runtime_dependency 'sprockets', '~> 2.0', '>= 2.0.0'
> WARNING:  open-ended dependency on appraisal (>= 0, development) is not 
> recommended
>   use a bounded requirement, such as '~> x.y'
> WARNING:  See https://guides.rubygems.org/specification-reference/ for help
>   Successfully built RubyGem
>   Name: handlebars_assets
>   Version: 0.23.8
>   File: handlebars_assets-0.23.8.gem
> /usr/bin/ruby2.7 -S gem install --config-file /dev/null --verbose --local 
> --verbose --no-document --ignore-dependencies --install-dir 
> debian/ruby-handlebars-assets/usr/share/rubygems-integration/all 
> /tmp/d20220212-715032-1jyqjgk/handlebars_assets-0.23.8.gem
> Failed to load /dev/null because it doesn't contain valid YAML hash
> ERROR:  While executing gem ... (Gem::Package::SymlinkError)
> installing symlink 'vendor/assets/javascripts/handlebars.js' pointing to 
> parent path /usr/share/javascript/handlebars/handlebars.js of 
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8
>  is not allowed
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8/lib/handlebars_assets.rb
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8/lib/handlebars_assets/config.rb
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8/lib/handlebars_assets/engine.rb
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8/lib/handlebars_assets/handlebars.rb
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8/lib/handlebars_assets/handlebars_template.rb
> /<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8/lib/handlebars_assets/version.rb
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:54:in `run': /usr/bin/ruby2.7 -S gem 
> install --config-file /dev/null --verbose --local --verbose --no-document 
> --ignore-dependencies --install-dir 
> debian/ruby-handlebars-assets/usr/share/rubygems-integration/all 
> /tmp/d20220212-715032-1jyqjgk/handlebars_assets-0.23.8.gem 
> (Gem2Deb::CommandFailed)
>   from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:212:in `run_gem'
>   from /usr/lib/ruby/vendor_ruby/ge

Bug#1028512: marked as pending in sqlmodel

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1028512 in sqlmodel 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/sqlmodel/-/commit/d2526aa61e661c041e63ecabaec1a3c43802d26c


Allow sqlalchemy dep version < 2.0 (Closes: #1028512)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028512

Processed: Bug#1028512 marked as pending in sqlmodel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028512 [python3-sqlmodel] python3-sqlmodel: Depends: python3-sqlalchemy 
(< 1.4.46) but 1.4.46+ds1-1 is to be installed
Added tag(s) pending.

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

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

[Pascal Hambourg]

Sorry for the late (and long) answer...

On 23/01/2023 à 19:36, Oleg A. Arkhangelsky wrote:


I tried this *.deb (Pascal approach). It doesn't change behaviour
introduced after this patch [1]. Yes, restart for "allow-hotplug"
interfaces work but I got the same system boot lag in Jeff configuration.


In your reply to Jeff on 21/01/2023, you acknowledged it was correct 
behaviour. You get the same delay with an unplugged interface marked 
"auto". I suspect that using "allow-hotplug" instead may have been used 
as a workaround to hide the delay in the background. Not the best way to 
fix things IMO.



Cyril's latest solution seems to work. I just added "-" to /bin/sh to
deal with cases when we have a device that is really hotplug and absent:

(...)

I got fast boot (as without bad patch) and working restart. One minute
long blocking during `systemctl restart networking` when DHCP is not
respoding (as in Jeff config) is expected.


Right, but you can add --no-block to avoid the delay.

This delay is caused by dhclient which becomes a daemon only after 
acquiring an address or 1-minute time-out. A solution would be to run 
dhclient with the option -nw to become a daemon immediately.
Why should ifup wait until an IP address is acquired ? dhclient and ifup 
return status 0 anyway.


udhcpc causes a shorter delay (10s) than dhclient, but it has no option 
to run in the background from the start.


I also had another idea: interfaces marked "allow-hotplug" are brought 
up by udev events, so why not restart them by replaying events with udevadm:


udevadm trigger --action=add --subsystem-match=net

First, a summary of relevant files in the ifupdown package:

/lib/systemd/system/networking.service:
ExecStart=/sbin/ifup -a --read-environment
ExecStop=/sbin/ifdown -a --read-environment --exclude=lo

/lib/udev/rules.d/80-ifupdown.rules:
SUBSYSTEM=="net", ACTION=="add|remove", RUN+="ifupdown-hotplug"

/lib/udev/ifupdown-hotplug:
TARGET_IFACE=$(/sbin/ifquery --allow hotplug -l "$INTERFACE")
systemctl --no-block start $(systemd-escape --template ifup@.service 
$TARGET_IFACE)


/lib/systemd/system/ifup@.service:
ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifquery --state %I'
ExecStop=/sbin/ifdown %I

On net add events, udev runs ifupdown-hotplug which starts instantiated 
ifup@.service for interfaces marked "allow-hotplug".

ifup@.service configures interfaces marked "allow-hotplug".

Problem: when networking.service stops interfaces, it does not stop the 
instantiated ifup@*.service. The above udevadm command triggers 
ifupdown-hotplug as expected, but starting ifup@*service which are 
already started is a no-op so ifup is not run again and the interfaces 
stay down.


Is this on purpose ?

If no, the obvious fix is to stop all ifup@*.service when 
networking.service is stopped, so that they can be restarted by udev.

So I ended up adding these two lines in networking.service:

 ExecStart=udevadm trigger --action=add --subsystem-match=net
 ExecStop=systemctl --no-block stop ifup@*.service

Maybe there is a more elegant way to stop ifup@*.service, e.g. using 
systemd unit dependencies but I am not familiar enough with this topic.


This setup causes no delay when (re)starting networking.service by hand 
at boot time or by hand. However if an interface marked "allow-hotplug" 
was manually stopped with ifdown without stopping the associated 
ifup@.service, it is not restarted when restarting networking.service.


Any thoughts ?

Additional questions:

networking.service starts only interfaces marked "auto", so shouldn't it 
stop only those interfaces ?


Alternatively, interfaces marked "allow-hotplug" are started by udev 
even if networking.service is not started (not started yet, stopped, 
disabled). This brings a significant difference between interfaces 
marked "auto" and "allow-hotplug": interfaces marked "allow-hotplug" are 
started when booting in recovery mode while interfaces marked "auto" are 
started only when booting in normal mode (multi-user.target). Is it 
desirable ?

Bug#1029534: marked as done (libreoffice-common: breaks libreoffice-core from the same version)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 23:27:24 +
with message-id 
and subject line Bug#1029534: fixed in libreoffice 4:7.5.0~rc3-1
has caused the Debian Bug report #1029534,
regarding libreoffice-common: breaks libreoffice-core from the same version
to be marked as done.

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

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


-- 
1029534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-common
Version: 4:7.4.4-7
Severity: serious

The Breaks in libreoffice-common need to be adjusted for the recent
epoch bumps.  Among others, libreoffice-common Breaks
libreoffice-core (>= 1:7.5~), making libreoffice-core 4:7.4.4-7
not installable.

Good luck figuring out what other relationships need to be changed, and
take your time.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 4:7.5.0~rc3-1
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 25 Jan 2023 23:17:31 +0100
Source: libreoffice
Architecture: source
Version: 4:7.5.0~rc3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 1029534
Changes:
 libreoffice (4:7.5.0~rc3-1) experimental; urgency=medium
 .
   * The "(More) 'Fun' with epochs" release.
 .
   * New upstream release candidate
 .
   * debian/control.in:
 - update -common Breaks: on -core after the epoch bumps (and add
   -core-nogui) (closes: #1029534)
Checksums-Sha1:
 5d1107cbd248810e6c932fd6cb6d2456febf6529 32895 libreoffice_7.5.0~rc3-1.dsc
 9650784eb274ec95dbb956bb2f00bf19ce114519 165037844 
libreoffice_7.5.0~rc3.orig-helpcontent2.tar.xz
 440e9fac5a20930772525991aab2de2ecdafac79 203862236 
libreoffice_7.5.0~rc3.orig-translations.tar.xz
 bbaf6337d162e115c8fabf312561404800a3fd5c 266035636 
libreoffice_7.5.0~rc3.orig.tar.xz
 679095be8a70269b8b5713ecb8dac7ff02b18022 833 
libreoffice_7.5.0~rc3.orig.tar.xz.asc
 0355c0d663d32c3ce6980be22f73cdf05f320388 25047164 
libreoffice_7.5.0~rc3-1.debian.tar.xz
 d075a040f2172cf0a302634f75e05d42a8bb8fda 35359 
libreoffice_7.5.0~rc3-1_source.buildinfo
Checksums-Sha256:
 19df916e0df9cb1d9581e8d458d84a57f59e1bf4516dde4ed636e2dd9bcd400d 32895 
libreoffice_7.5.0~rc3-1.dsc
 b8311f482f8251e7a4b9408420f2cf888760e3f86ebd7cff594b9dcf3098e462 165037844 
libreoffice_7.5.0~rc3.orig-helpcontent2.tar.xz
 4a70dcdc7b93dc9ec1466a334d0bc76fab901ada041a16413f7c1598282afeb5 203862236 
libreoffice_7.5.0~rc3.orig-translations.tar.xz
 f5120fa3ae80a7deb08150038a6e78335bcab578bd7c41ddc733c2057977003b 266035636 
libreoffice_7.5.0~rc3.orig.tar.xz
 4d7be83dc55cf1a6f801adc78a7e9a87d12c383a61c9c356c68f59ce51aeda91 833 
libreoffice_7.5.0~rc3.orig.tar.xz.asc
 a5d64f7e7370088e1748cee63f8f62df1b4c0d464b52352c09551b3deb32fe86 25047164 
libreoffice_7.5.0~rc3-1.debian.tar.xz
 89b5312f5f638b00a2b8a2d48af84a59fdf3df29dda09c863026cda451986ae5 35359 
libreoffice_7.5.0~rc3-1_source.buildinfo
Files:
 cd1dbe6914032b295f72f0faf39bb75a 32895 editors optional 
libreoffice_7.5.0~rc3-1.dsc
 edb7b3090ffe9a3b7a1425050089d12a 165037844 editors optional 
libreoffice_7.5.0~rc3.orig-helpcontent2.tar.xz
 60154dcbc86de83276ca8231c4478502 203862236 editors optional 
libreoffice_7.5.0~rc3.orig-translations.tar.xz
 3e7066685b3e786af93ec581ca377496 266035636 editors optional 
libreoffice_7.5.0~rc3.orig.tar.xz
 e938262e41f56b9c0027f15fc01b3a90 833 editors optional 
libreoffice_7.5.0~rc3.orig.tar.xz.asc
 a15a72eaf85fe49b4524eca85439a749 25047164 editors optional 
libreoffice_7.5.0~rc3-1.debian.tar.xz
 530cefcd7e2d5d1ba260b737f6b05ab6 35359 editors optional 
libreoffice_7.5.0~rc3-1_source.buildinfo

-BEGIN PGP

Bug#1029657: python-os-ken: FTBFS randomly (BlockingIOError: [Errno 11] write could not complete without blocking)

[Santiago Vila]

Package: src:python-os-ken
Version: 2.5.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
make: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:28: warning: overriding recipe for target 'override_dh_auto_test'
debian/rules:25: warning: ignoring old recipe for target 'override_dh_auto_test'
dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils

[...]

os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix
 ... ok
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix_invalid_rd
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix_invalid_rd
 ... ok
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix_not_str
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix_not_str
 ... ok
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix_short_rd
os_ken.tests.unit.services.protocols.bgp.utils.test_validation.Test_Utils_Validation.test_is_valid_vpnv6_prefix_short_rd
 ... ok
12  bytearray(b'1\x05\n\x01\x00\x1eb\xf8\xc0\xa8\x00\x02')
(49, 5, 10, 1, 30, 25336, b'\xc0\xa8\x00\x02')
78 
bytearray(b'33\x00\x00\x00\x12\x00\x00^\x00\x02\x80\x86\xddl\x00\x00\x00\x00@p\xff
 \x01\r\xb8 
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x03\xff\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x121\x80c\x01\x00o\xcf\xfb
 \x01\r\xb8 \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01')
78 
bytearray(b'33\x00\x00\x00\x12\x00\x00^\x00\x02\x80\x86\xddl\x00\x00\x00\x00@p\xff
 \x01\r\xb8 
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x03\xff\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x121\x80c\x01\x00o\xcf\xfb
 \x01\r\xb8 \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01')
78 
bytearray(b'33\x00\x00\x00\x12\x00\x00^\x00\x02\x80\x86\xddl\x00\x00\x00\x00@p\xff
 \x01\r\xb8 
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x03\xff\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x121\x80c\x01\x00o\xcf\xfb
 \x01\r\xb8 \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01')
24  bytearray(b'1\x05\n\x01\x00\x1e)\xc9 \x01\r\xb8 
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02')
(49, 5, 10, 1, 30, 10697, b' \x01\r\xb8 
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02')

==
FAIL: os_ken.tests.unit.cmd.test_manager.Test_Manager.test_help
os_ken.tests.unit.cmd.test_manager.Test_Manager.test_help
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/mock.py", line 1379, in patched
return func(*newargs, **newkeywargs)
  File "/<>/os_ken/tests/unit/cmd/test_manager.py", line 44, in 
test_help
self.assertRaises(SystemExit, main)
  File "/usr/lib/python3.10/unittest/case.py", line 738, in assertRaises
return context.handle('assertRaises', args, kwargs)
  File "/usr/lib/python3.10/unittest/case.py", line 201, in handle
callable_obj(*args, **kwargs)
  File "/<>/os_ken/cmd/manager.py", line 71, in main
CONF(args=args, prog=prog,
  File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2153, in 
__call__
self._namespace = self._parse_cli_opts(args if args is not None
  File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2924, in 
_parse_cli_opts
return self._parse_config_files()
  File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2960, in 
_parse_config_files
self._oparser.parse_args(self._args, namespace)
  File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 1936, in 
parse_args
return super(_CachedArgumentParser, self).parse_args(args, namespace)
  File "/usr/lib/python3.10/argparse.py", line 1838, in parse_args
args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.10/argparse.py", line 1871, in parse_known_args
namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.10/argparse.py", line 2084, in _parse_known_args
start_index = consume_optional(start_index)
  File "/usr/lib/python3.10/argparse.py", line 2024, in consume_optional
take_action(action, args, option_string)
  File "/usr/lib/python3.10/argparse.py", line 1948, in take

Bug#1029342: Fwd: [request-tracker-maintainers] Bug#1026669: request-tracker5: FTBFS: can't locate java: No such file or directory

[bert schulze]

Hi Lucas, Niko,

Niko Tyni (Sat, Jan 21, 2023 at 02:41:28PM +):
> Control: clone -1 -2
> Control: retitle -2 jexec: can't locate java: No such file or directory
> Control: reassign -2 openjdk-17-jre-headless 17.0.5+8-2
>
> On Wed, Jan 18, 2023 at 04:10:02AM +0100, Ángel wrote:
> > The error here is that ./debian/build-final-ckeditor.sh fails with
> > « can't locate java: No such file or directory »
> >
> > This script is actually calling ckbuilder ( jexec /usr/bin/ckbuilder --
> > build ... )


  please just use "java -jar /usr/bin/ckbuilder" instead, details below.


> >
> > However, the package correctly lists ckbuilder as a build-dep, and
> > ckbuilder itself depends on java ( default-jre | java{7..11}-runtime)
>
> > > update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> > > amd64/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode
>
> Yeah, it looks to me like jexec from openjdk-17-jre-headless
> is just broken on sid?

Yes and it somewhat has ever been broken with regard to the way it is
being shipped within Debian.

The sole purpose for jexec is to use readlink(3) to find the correct
path of bin/java and execute a jar with a certian version of java.
(and to enable double click executions of jar files by binfmt magic).

This of course only works by invoking jexec with an absolute path,
e.g. running "/usr/bin/jexec /usr/bin/ckbuilder" should fix this.


All JDK source packages ship with patches to jexec to somehow
"emulate" this behaviour, which looks less than ideal to me. ;)

  openjdk-8-8u352-ga/debian/patches/jexec.diff.in
  openjdk-11-11.0.17+8/debian/patches/jexec.diff
  openjdk-17-17.0.5+8/debian/patches/jexec.diff


Open JDK 8 (pass)
---
readlink -sf /etc/alternatives/jexec
 => /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec

$ strace -e execve jexec 2>&1 |grep -E '(jexec|java)'

execve("/usr/bin/jexec", ["jexec"], 0x7ffd7c115b50 /* 59 vars */) = 0
execve("/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java",
  ["/usr/lib/jvm/java-8-openjdk-amd6"..., "-jar"], 0x7ffd657e2a18 /* 59
vars */) = 0

Open JDK 11 (pass)
---
readlink -sf /etc/alternatives/jexec
 => /usr/lib/jvm/java-11-openjdk-amd64/lib/jexec

$ strace -e execve jexec 2>&1 |grep -E '(jexec|java)'

execve("/usr/bin/jexec", ["jexec"], 0x7ffed43a0f20 /* 59 vars */) = 0
execve("/usr/lib/jvm/java-11-openjdk-amd64/bin/java",
  ["/usr/lib/jvm/java-11-openjdk-amd"..., "-jar"], 0x7ffdc7e44058 /* 59
vars */) = 0

Open JDK 17 (fail)
---
readlink -f /bin/jexec
 => /usr/lib/jvm/java-17-openjdk-amd64/lib/jexec

$ strace -e execve jexec 2>&1 |grep -E '(jexec|java)'

execve("/usr/bin/jexec", ["jexec"], 0x7fffb95f2cc0 /* 59 vars */) = 0
can't locate java: No such file or directory


To make things complicated further: what about users deciding to use
antoher JDK e.g. the (former Adoptium) Eclipse Temurin builds?
(everyone has to remember the "portability" joke right here:)


Temurin JDK 8 (fail)
---
readlink -sf /etc/alternatives/jexec
 => /usr/lib/jvm/temurin-8-jdk-amd64/lib/jexec

$ strace -e execve jexec 2>&1 |grep -E '(jexec|java)'

execve("/usr/bin/jexec", ["jexec"], 0x7ffe6c1b9320 /* 59 vars */) = 0
can't locate java: No such file or directory

Temurin JDK 11 (fail)
---
readlink -sf /etc/alternatives/jexec
 => /usr/lib/jvm/temurin-11-jdk-amd64/lib/jexec

$ strace -e execve jexec 2>&1 |grep -E '(jexec|java)'

execve("/usr/bin/jexec", ["jexec"], 0x7fff1d218450 /* 59 vars */) = 0
can't locate java: No such file or directory

Temurin JDK 17 (fail)
---
readlink -sf /etc/alternatives/jexec
 => /usr/lib/jvm/temurin-17-jdk-amd64/lib/jexec

$ strace -e execve jexec 2>&1 |grep -E '(jexec|java)'

execve("/usr/bin/jexec", ["jexec"], 0x7ffd110128b0 /* 59 vars */) = 0
can't locate java: No such file or directory


> I'm cloning a separate bug about this.

Yes, to be discussed further in #1029342

> Not sure why jexec is used here though. Just running /usr/bin/ckbuilder
> works for me (but the request-tracker5 build fails later, presumably
> due to a different bug.)

see my TLDR above

> --
> Niko Tyni   nt...@debian.org

BR
bert schulze

Bug#1029534: marked as done (libreoffice-common: breaks libreoffice-core from the same version)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 23:15:44 +
with message-id 
and subject line Bug#1029534: fixed in libreoffice 4:7.4.4-8
has caused the Debian Bug report #1029534,
regarding libreoffice-common: breaks libreoffice-core from the same version
to be marked as done.

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

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


-- 
1029534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-common
Version: 4:7.4.4-7
Severity: serious

The Breaks in libreoffice-common need to be adjusted for the recent
epoch bumps.  Among others, libreoffice-common Breaks
libreoffice-core (>= 1:7.5~), making libreoffice-core 4:7.4.4-7
not installable.

Good luck figuring out what other relationships need to be changed, and
take your time.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 4:7.4.4-8
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 25 Jan 2023 22:43:15 +0100
Source: libreoffice
Architecture: source
Version: 4:7.4.4-8
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 1029534
Changes:
 libreoffice (4:7.4.4-8) unstable; urgency=medium
 .
   * The "(More) 'Fun' with epochs" release.
 .
   * debian/control.in:
 - update -common Breaks: on -core after the epoch bumps (and add
   -core-nogui) (closes: #1029534)
Checksums-Sha1:
 91d38ae65741fce7e6a2584cac716e7d53a1eed9 32105 libreoffice_7.4.4-8.dsc
 5a6aa34cda1c1251051e8ec115ac50a86f7e7edf 24746620 
libreoffice_7.4.4-8.debian.tar.xz
 2215f3a3bd73402ec453becb62c8b5e089a25829 34670 
libreoffice_7.4.4-8_source.buildinfo
Checksums-Sha256:
 79b334a42072fdda67f2e7cd2cf8c66d36a8ed21aaddca63d991b7e07414442b 32105 
libreoffice_7.4.4-8.dsc
 2d0f581068d6ae86f30d0387fe3e99daa52b61a4ce5150715d6fa107ea19f35b 24746620 
libreoffice_7.4.4-8.debian.tar.xz
 29f0180692a2e3e201c7de5f994633885b3414590649056faa99929a0149e440 34670 
libreoffice_7.4.4-8_source.buildinfo
Files:
 dd1488d4ce908ea57e1692c3c3412641 32105 editors optional libreoffice_7.4.4-8.dsc
 a23b2a7e2f51cca2dd9bffc85c775c2d 24746620 editors optional 
libreoffice_7.4.4-8.debian.tar.xz
 d0b1a3eda3b176d142d928053e0cfeb0 34670 editors optional 
libreoffice_7.4.4-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmPRq5kQHHJlbmVAZGVi
aWFuLm9yZwAKCRAKoEVx0D4+cAh8EACbL0E/NRgytnXLq6N5n1dToM6ydiSXsAy4
v21n3BI0vnhmaPgtJHAIpsNjNvgjJTVXQ1rWuh7cy2FvWaYV+SquhJtpkRA/ZR6Z
SEKEy1MP3oQ4DpYROAbLvLXUDg1jUAMxaGe8zG9GP4mxzPCJWARMIxhjfeHf//X3
aCF9fZheIoC0RvwCtdwH61A2Ok8nsPKJxbiQ5RaZzbdBnIo8ta6JSJpc4R2nV2ER
b4PacyjFQfDE7Ea4dBgAt05Z3exeGKSrszUSCB6dzAHNmzr+KveO9hEwplTWw0JW
0nlKZ9v808qh2fDAerIrlof/EFC3bR8b+Sr5wt+Cg9TdLlr9giM1hBqQqd1A3fr/
UHK4fnzwXhUCVI95A5rBmhgrN2hZ8sTP9lwCehFxM80u8gVKOrgnj4WJ+/OAvM3f
WI7Bzwa8AM08ogCvdBFGRRdUq0lCcAHV1REXMK4sw6gokhBy/lqc/OVLk2hFAOU3
wtrMvUy1P4AMCsCWdiLY3wbqhTMNthl33HaMaCXSGKvFInSTP1BnjNiudA8pFPnV
1J4aWHoQPgT0A8+p48ALh8fB1zocgn4T89FiCVSedpLpLFelVFe5F0Bk3m2EDTF2
fly8nswShrlgFbbHWq8wQLLsP4B+vpUGdU1Vs46kMWk8E2drP9kJmzvrT+mymhw4
jN8w2y8rTw==
=PFLe
-END PGP SIGNATURE End Message ---

Bug#1029611: marked as done (lxqt-config: FTBFS: Unexpected libkscreen transition)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 23:06:03 +
with message-id 
and subject line Bug#1029611: fixed in libkscreen 4:5.26.90-3
has caused the Debian Bug report #1029611,
regarding lxqt-config: FTBFS: Unexpected libkscreen 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.)


-- 
1029611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxqt-config
X-Debbugs-Cc: Debian Qt/KDE Maintainers 
Version: 1.2.0-1
Severity: serious
Tags: ftbfs

Dear LXQt packaging team,

I has been raised to my attention that lxqt-config depends on
libkscreen, which I thought was used only by Plasma components.
So it turns out I have started an unplanned transition with my recent
upload of Plasma 5.26.90 (5.27 beta).

I’ll discuss with the release team how to sort the issue in a separate  
bug report but in the meantime I’ve started rebuilding rdeps with the
new libkscreen and unfortunately lxqt-config fails to build.

You’ll find a amd64 sbuild log at [0].

I’d appreciate if you could investigate the matter quickly so we can
find a fix.


Please accept my apology for this, and we will handle future libkscreen
and Plasma libs soname bumps as proper transitions obviously…


[0] 
https://people.debian.org/~coucouf/lxqt-config_1.2.0-1_amd64-2023-01-25T10:31:32Z.build


Thanks for your help.
--
Aurélien
--- End Message ---
--- Begin Message ---
Source: libkscreen
Source-Version: 4:5.26.90-3
Done: Aurélien COUDERC 

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

Debian distribution maintenance software
pp.
Aurélien COUDERC  (supplier of updated libkscreen 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, 25 Jan 2023 23:07:51 +0100
Source: libkscreen
Architecture: source
Version: 4:5.26.90-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Aurélien COUDERC 
Closes: 1029611
Changes:
 libkscreen (4:5.26.90-3) unstable; urgency=medium
 .
   * Add patch to support consumers using less than c++17 (thanks Sune Vuorela).
   * Add patch to restore a transitive include fixing FTBFS in downstream
 packages (thanks Sune Vuorela, closes: #1029611).
Checksums-Sha1:
 27e1ea4690cbfe2402b9ed9c307af4358097fce8 3045 libkscreen_5.26.90-3.dsc
 99ca7bbeac0fe59f8fe7437ac4be3fc050e14d54 21572 
libkscreen_5.26.90-3.debian.tar.xz
 21f8be18ede92f2bd8c40c194397d2c4b85d40cf 15684 
libkscreen_5.26.90-3_amd64.buildinfo
Checksums-Sha256:
 3c6ee823aed2df077fcdd56d5c380af0578554754899b9f8b79baacba80a10a3 3045 
libkscreen_5.26.90-3.dsc
 dbe6886ae824d76b7b96568dbcc7bca79f309ac6577e3272982d811f9541d0de 21572 
libkscreen_5.26.90-3.debian.tar.xz
 1aaf2b2ddcb3aad7dd321aa822789b5cb574c54d392961dd3992b498130b5f00 15684 
libkscreen_5.26.90-3_amd64.buildinfo
Files:
 09669ab4cce7c8da7c43728ef6ed 3045 libs optional libkscreen_5.26.90-3.dsc
 079c6e3ba4e5caf9006fc6daa869e928 21572 libs optional 
libkscreen_5.26.90-3.debian.tar.xz
 5896703592c1c762c4a623bb6d4f06ab 15684 libs optional 
libkscreen_5.26.90-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmPRqKUTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJOHpD/4gCXbHs+HJblDlAcHmCgrvnd3fQ4+b
eRojHEyCNzAXbXq0b5aKzRbTk/Q30hitERPw6mV7CfJ9gsZW8+MPSBuzmohROoCJ
x7GvIa8U4aK007U+C39nwVRrpTDgPE4NJ/M04gotqLfVKZP1rj0e/yu8ltPn3AcJ
h4VP8pUre7O1xCeysN5IuoAYsEwplR4QMMYEPFqQZZ3UkVRvmA2ASoA+mC3SXgo2
574KLizZpUWqpnxusKAkz3PtGbbiHphJP3WNfIpSbnPCFrhOYX0pxcHQmDLo6/p/
6zFT2SWb7YnwAuxST/kZCc5gQnRQp/U9GBiBPDONWUtReOyErD7J8UM40G3K4bx/
taYbGtFauXrV/8S0bJW+i9EGTtl4kXO+FHbxeTPjkzqhXzP6tHN06B21RQhwhhKC
pnDXhqb598PGgDTU0WpRTfKPd2IZmGBpMnjNeqBPqD+pyMFyb2xKdKVj3zAqVQK5
GZj8PJsMPdticUbazOmKzXmH8RMbY3tL8VRgboj89JlRrrKK7k8K5yhuEUWbYJ5Z
ACosNgJYYJzdTTgRCnFKkb957A0I3ROsxo20MjXHI755AWtaqaeP6URqWMkAEPUQ
KsQXdqNyloelUUZwnKPIImTL7rtB2USpg5GzMBvdjC+j/DAwCdfCQa//U3pbkAK/
GSb2RO0M7JgVCw==
=pHQV
-END PGP SIGNATURE End Message ---

Bug#1029613: ukui-settings-daemon FTBFS: Unexpected libkscreen transition

[Aurélien COUDERC]

With the help of Sune Vuorela I was able to patch some workarounds into
libkscreen 4:5.26.90-3 and the compilation made some more progress but still
fails:

https://people.debian.org/~coucouf/ukui-settings-daemon_3.1.1.1-1_amd64-2023-01-25T15:02:13Z.build

xrandr-manager.cpp: In member function ‘void XrandrManager::monitorsInit()’:
xrandr-manager.cpp:1200:50: error: ‘isPrimaryChanged’ is not a member of 
‘KScreen::Output’
 1200 | connect(output.data(), &KScreen::Output::isPrimaryChanged, 
this, [this](){
  |  ^~~~
xrandr-manager.cpp:1292:47: error: ‘primaryOutputChanged’ is not a member of 
‘KScreen::Config’
 1292 | connect(mConfig.data(), &KScreen::Config::primaryOutputChanged,
  |   ^~~~

Bug#1029612: ukui-control-center: FTBFS: Unexpected libkscreen transition

[Aurélien COUDERC]

With the help of Sune Vuorela I was able to patch some workarounds into
libkscreen 4:5.26.90-3 and the compilation made some more progress but still
fails:

https://people.debian.org/~coucouf/ukui-control-center_3.0.5.1-1_amd64-2023-01-25T14:51:50Z.build

widget.cpp: In member function ‘void Widget::setConfig(const 
KScreen::ConfigPtr&, bool)’:
widget.cpp:222:47: error: ‘primaryOutputChanged’ is not a member of 
‘KScreen::Config’
  222 | connect(mConfig.data(), &KScreen::Config::primaryOutputChanged,
  |   ^~~~
widget.cpp: In member function ‘bool Widget::isBacklight()’:
widget.cpp:767:18: warning: ‘void QProcess::start(const QString&, 
QIODevice::OpenMode)’ is deprecated: Use QProcess::start(const QString 
&program, const QStringList &arguments,OpenMode mode = ReadWrite) instead 
[-Wdeprecated-declarations]
  767 | process.start(cmd);
  | ~^
/usr/include/x86_64-linux-gnu/qt5/QtCore/qprocess.h:168:10: note: declared here
  168 | void start(const QString &command, OpenMode mode = ReadWrite);
  |  ^
mv -f libshortcut.so ../../libshortcut.so
widget.cpp: In member function ‘void Widget::setActiveScreen(QString)’:
widget.cpp:1221:21: warning: operation on ‘enableCount’ may be undefined 
[-Wsequence-point]
 1221 | enableCount = (output->isEnabled() ? (++enableCount) : 
enableCount);
  | 
^~~

Processed: Bug#1005631 marked as pending in ruby-handlebars-assets

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005631 [src:ruby-handlebars-assets] ruby-handlebars-assets: FTBFS: Failed 
to load /dev/null because it doesn't contain valid YAML hash
Ignoring request to alter tags of bug #1005631 to the same tags previously set

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

Bug#1005631: marked as pending in ruby-handlebars-assets

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1005631 in ruby-handlebars-assets 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/ruby-team/ruby-handlebars-assets/-/commit/4a863d6cb4532d68be3d1548bbfbd58dec6e598c


Fix tests with Ruby HAML 6

  * debian/patches/0005-Fix-syntax-for-ruby-haml-6.patch: Add patch.
- Fix syntax for Ruby HAML 6 (closes: #1005631).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005631

Bug#562702: python-pam: Debian differences not clearly separated from upstream source

[Bastian Germann]

Control: severity -1 normal

On Wed, 25 Jan 2023 22:24:39 +0100 Sebastian Ramacher  
wrote:

This seems like it would be easy enough to fix.


Yes but it also shows that pam-python is not really a replacement for 
python-pam.
So I am resetting the severity.

Processed: Re: Bug#562702: python-pam: Debian differences not clearly separated from upstream source

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #562702 [python-pam] python-pam: Debian differences not clearly separated 
from upstream source
Severity set to 'normal' from 'serious'

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

Bug#1011445: marked as done (ruby-gitlab-license-finder,ruby-license-finder: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:59:16 +
with message-id 
and subject line Bug#1011445: fixed in ruby-license-finder 7.0.1-2
has caused the Debian Bug report #1011445,
regarding ruby-gitlab-license-finder,ruby-license-finder: error when trying to 
install together
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.)


-- 
1011445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-gitlab-license-finder,ruby-license-finder
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.14.2.1-2
Control: found -1 7.0.1-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-license-finder.
  Preparing to unpack .../ruby-license-finder_7.0.1-1_all.deb ...
  Unpacking ruby-license-finder (7.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-license-finder_7.0.1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/license_finder', which is also in package 
ruby-gitlab-license-finder 6.14.2.1-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-license-finder_7.0.1-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/license_finder

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-gitlab-license-finder=6.14.2.1-2_ruby-license-finder=7.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-license-finder
Source-Version: 7.0.1-2
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-license-finder 
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, 25 Jan 2023 22:01:52 +0100
Source: ruby-license-finder
Architecture: source
Version: 7.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Daniel Leidert 
Closes: 1011445
Changes:
 ruby-license-finder (7.0.1-2) unstable; urgency=medium
 .
   * Team upload.
   * d/control: Declare a conflict with ruby-gitlab-license-finder
 (closes: #1011445).
Checksums-Sha1:
 f9dd1227482b15729cab64a9e083a8fe4a36a423 2266 ruby-license-finder_7.0.1-2.dsc
 d36f05011fcb39937927d97fcf99e6abb86207cc 3328 
ruby-license-finder_7.0.1-2.debian.tar.xz
 47187cc8f1f7173c6fe21b7c790593c8912a5236 9880 
ruby-license-finder_7.0.1-2_amd64.buildinfo
Checksums-Sha256:
 93f1ffa264a9e64906e859f355b24992cf328cc55cd71a8a5b6830fdd41118bd 2266 
ruby-license-finder_7.0.1-2.dsc
 0d51cf3a0bb448bc452596fabdc4b9c1cf60dac41db85e923f40df5f5a0ecbc8 3328 
ruby-license-finder_7.0.1-2.debian.tar.xz
 422878cc6f0838972cc3df439

Bug#1028949: marked as done (php-horde-token: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:58:29 +
with message-id 
and subject line Bug#1028949: fixed in php-horde-token 2.0.9-9
has caused the Debian Bug report #1028949,
regarding php-horde-token: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-token
Version: 2.0.9-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-token fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-tokenfrom testing2.0.9-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-token/30356871/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
..PHP Deprecated:  Creation of dyna

Bug#1028947: marked as done (php-horde-text-diff: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:58:12 +
with message-id 
and subject line Bug#1028947: fixed in php-horde-text-diff 2.2.1-3
has caused the Debian Bug report #1028947,
regarding php-horde-text-diff: (autopkgtest) needs update for php8.2: 
deprecation warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-text-diff
Version: 2.2.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-text-diff 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-text-difffrom testing2.2.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-text-diff/30356869/log.gz


PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$ychanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xchanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$ychanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xchanged is depre

Bug#1029534: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1029534 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/dd5021c6b741549e80d5b0e50bface7779c526ff


update -common Breaks: on -core after the epoch bumps (and add -core-nogui) 
(closes: #1029534)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029534

Processed: Bug#1029534 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029534 [libreoffice-common] libreoffice-common: breaks libreoffice-core 
from the same version
Ignoring request to alter tags of bug #1029534 to the same tags previously set

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

Bug#1028948: marked as done (php-horde-text-flowed: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:58:21 +
with message-id 
and subject line Bug#1028948: fixed in php-horde-text-flowed 2.0.4-3
has caused the Debian Bug report #1028948,
regarding php-horde-text-flowed: (autopkgtest) needs update for php8.2: 
deprecation warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-text-flowed
Version: 2.0.4-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-text-flowed 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-text-flowed  from testing2.0.4-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-text-flowed/30356870/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.hfseeczg/downtmp/build.wgj/src/Horde_Text_Flowed-2.0.4/test/Horde/Text/Flowed/phpunit.xml


PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
. 3 / 3 
(100%)


Time: 00:00.003, Memory: 6.00 MB

OK (3 tests, 9 assertions)
autopkgtest [06:17:32]: test phpunit



OpenPGP_signature
De

Bug#1028942: marked as done (php-horde-passwd: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:57:59 +
with message-id 
and subject line Bug#1028942: fixed in php-horde-passwd 5.0.7-9
has caused the Debian Bug report #1028942,
regarding php-horde-passwd: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-passwd
Version: 5.0.7-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-passwd fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-passwd   from testing5.0.7-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-passwd/30356864/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/phpunit.xml


PHP Deprecated:  Creation of dynamic property 
Passwd_Factory_Driver::$backends is deprecated in 
/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Driver/SqlTest.php 
on line 26
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.PHP Deprecated:  Creation of dynamic property 
Passwd_Factory_Driver::$backends is deprecated in 
/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Driver/SqlTest.php 
on line 26
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.III   5 / 5 
(100%)


Time: 00:00.013, Memory: 6.00 MB

There were 3 incomplete tests:

1) Passwd_Unit_Factory_DriverTest::testGettingSubdriversWorks
Factories with configuration files don't work out of the box.

/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Factory/DriverTest.php:19

2) Passwd_Unit_Factory_DriverTest::testGetBackendsReturnsResultOfSetBackends
Factories with configuration files don't work out of the box.

/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Factory/DriverTest.php:19

3) Passwd_Unit_Factory_DriverTest::testGettingTheSameDriverTwiceWorks
Factories with configuration files don't work out of the box.

/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Factory/DriverTest.php:19

OK, but incomplete, skipped, or risky tests!
Tes

Bug#1028933: marked as done (php-horde-http: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:57:51 +
with message-id 
and subject line Bug#1028933: fixed in php-horde-http 2.1.7-11
has caused the Debian Bug report #1028933,
regarding php-horde-http: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-http
Version: 2.1.7-10
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-http fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-http from testing2.1.7-10
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-http/30356854/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/test/Horde/Http/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


...PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is

Bug#1028961: marked as done (dpkg: reverts to using insecure cryptographic algorithms by default)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:49:08 +
with message-id 
and subject line Bug#1028961: fixed in dpkg 1.21.19
has caused the Debian Bug report #1028961,
regarding dpkg: reverts to using insecure cryptographic algorithms by default
to be marked as done.

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

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


-- 
1028961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.21.13
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team 

Hi,

dpkg 1.21.13 introduced passing "--openpgp" to GnuPG by default due to
some conflict between the dpkg maintainer and gnupg upstream. This
causes GnuPG to use insecure cryptographic algorithms like the SHA-1
digest algorithm by default.

Please revert 
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?h=1.21.13&id=b83114daa69c50d368199d00fbb67e190068b273

I do not think that cryptographic default from over 15 years ago are
a good default choice today; rather they are a security issue (just
like, for example, reverting to using SSL3 instead of TLS1.3).

Ansgar

-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

I think this message should be removed as it confuses users.
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.21.19
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Jan 2023 23:39:50 +0100
Source: dpkg
Architecture: source
Version: 1.21.19
Distribution: unstable
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 1028961 1028981
Changes:
 dpkg (1.21.19) unstable; urgency=medium
 .
   [ Guillem Jover ]
   * Architecture support:
 - Revert "arch: Add support for loong64 CPU". See #1028654.
   * Perl modules:
 - Dpkg::OpenPGP::Backend::GnuPG: Set secure signing preferred algorithms.
   Closes: #1028961
 - Dpkg::OpenPGP::Backend::GnuPG: Touch trustedkeys.gpg on temporary gpg
   home.
 - Dpkg::OpenPGP::Backend::GnuPG: Fallback to use «gpg dearmor» if
   present. Reported by Sven Joachim  (on IRC).
 - Dpkg::Vendor::Ubuntu: Fix lto feature to honor DEB_BUILD_OPTIONS.
   * Test suite:
 - Set the permissions explicitly for the copied ChangeLog.old file.
 - Add unit tests for lto build flags handling in Ubuntu.
   Thanks to Shengjing Zhu .
   See https://bugs.launchpad.net/bugs/2002582.
   * Localization:
 - Update Catalan translation.
 - Update Portuguese man pages translation.
   Thanks to Américo Monteiro . Closes: #1028981
 .
   [ Sven Joachim ]
   * Localization:
 - Update German programs translation.
 .
   [ Helge Kreutzmann ]
   * Localization:
 - Update German man pages translation.
Checksums-Sha1:
 df80449cb4534cdb53f22f8825c82ebffe67ce77 3060 dpkg_1.21.19.dsc
 1e6c6037cd27bc620b84423823c40f3f396edbfc 5360888 dpkg_1.21.19.tar.xz
 bb7e4555cd129b2af38341df6551e440e41e2756 7958 dpkg_1.21.19_amd64.buildinfo
Checksums-Sha256:
 2c7cf3f3d10473510515af27bd99bde56f1ec123ecff8e61869984d88fb8769d 3060 
dpkg_1.21.19.dsc
 cdfd0b36676a77a9cfc53597697c9096f3ffcbc25750944c34142af025101c92 5360888 
dpkg_1.21.19.tar.xz
 6b7c52df3cae17f66d6f78497d73075384f234291f8d296a3eec5b0480bb86fb 7958 
dpkg_1.21.19_amd64.buildinfo
Files:
 ee7639c9c28d84ffc1efd583386edd0e 3060 admin required dpkg_1.21.19.dsc
 1aafd3b59b3e1709ad1b0c2c7a7dd2dc 5360888 admin required dpkg_1.21.19.tar.xz
 1f28d9d90e1ab146d88717b750ced7ad 7958 admin required 
dpkg_1.21.19_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAmPQYQcACgkQuXK/PqSu
V6NapRAAs9F/4VaHGAII2AGETnJroWkrKiwdf/mLkno0NejUbBh55ATqKrxWovnI
gG8

Processed: Bug#1029534 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029534 [libreoffice-common] libreoffice-common: breaks libreoffice-core 
from the same version
Added tag(s) pending.

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

Bug#1029534: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1029534 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/dd5021c6b741549e80d5b0e50bface7779c526ff


update -common Breaks: on -core after the epoch bumps (and add -core-nogui) 
(closes: #1029534)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029534

Bug#1028961: dpkg: reverts to using insecure cryptographic algorithms by default

[James Addison]

Package: dpkg
Version: 1.21.18
Followup-For: Bug #1028961

Are SHA224 and SHA384 used widely by dpkg and/or Debian?

Bug#1028949: marked as pending in php-horde-token

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1028949 in php-horde-token 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/horde-team/php-horde-token/-/commit/37b7a5ae4b81f5593752fe90003975acbfabde94


debian/patches: Add 1012_php8.2.patch. Fix PHP 8.2 deprecation warnings. 
(Closes: #1028949).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028949

Processed: Bug#1028949 marked as pending in php-horde-token

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028949 [src:php-horde-token] php-horde-token: (autopkgtest) needs update 
for php8.2: deprecation warnings on stderr
Added tag(s) pending.

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

Processed: fixed 975501 in 2.3.1-3

[Debian Bug Tracking System]

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

> fixed 975501 2.3.1-3
Bug #975501 {Done: Adrian Bunk } [libopendht-dev] FTBFS: 
undefined reference to symbol 'SSL_get_verify_callback@@OPENSSL_1_1_0'
Marked as fixed in versions opendht/2.3.1-3.
> thanks
Stopping processing here.

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

Bug#1028587: Acknowledgement (datefudge: 64-bit time_t functions are not implemented/exposed)

[adrien]

I was wondering why my answer wasn't showing up in the web interface.
Well, I replied only to Matthias. I'm re-sending here with a some
additional infos. Apologies for the duplication. :) 

First thing is that I was wrong: faketime exhibits the same issue. This
isn't a big surprise. I've also looked at Fedora, Opensuse and Arch
Linux; it seems none of them have patches for this class of issue.

For the record, two packages use datefudge and around thirty use
faketime, mostly for tests and for making documentation reproducible.
Only three use faketime at runtime: debrepro.sh, reprotests, and ...
doxygen which would make many packages non-reproducible (NB: the actual
embedders of timestamps are latex tools); only one uses it for a reproducible
python source file (pyacidobasic) and one for reproducible images
(x4d-icons).

For reference, I've opened a bug upstream:
https://github.com/wolfcw/libfaketime/issues/418
(and I probably need to open a bug against the faketime package but
won't do so this evening)

I don't have a list of binaries using this ABI but there are probably
only a few, if any, such files outside of coreutils. Considering the
current freeze, it seems very unlikely that new issues will crop up for
the release and there's probably no need to hurry too much.

On the Ubuntu side, I think it wouldn't be reasonable to fix that later
than for 23.10.

On Wed, Jan 18, 2023, Matthias Urlichs wrote:
> On 18.01.23 15:51, adrien wrote:
> > As far as I can see, libfaketime doesn't have an equivalent to
> > datefudge's -s (static time) but I'm not sure if it's really needed in
> > practice and if it is, I'm confident we can add it to libfaketime.
> 
> [ Author of datefudge here ]
> 
> I assume that datefudge is used to support reproducible builds; in that case
> it most likely *is* necessary to use the '-s' option, as build times are not
> going to be constant.

I checked again and it implements the same -s behavior but does so based
on the time specification the is provided. You can either provide an
absolute and static time, an absolute and dynamic time, or a relative
and dynamic time (I didn't notice relative and static but didn't try to
find it either). I prefer -s but at least libfaketime should do what we
need.

> I do recommend switching to a supported library. I'm sorry to say that my
> time budget already is negative for the foreseeable future, thus resuming
> support for datefudge is out of the question unfortunately.

I definitely understand your situation.

Also, it seems libfaketime has gotten more attention and, by now, many
more features. It would be difficult to come close to it (I never
thought a time-faking library could have so many features).

Bug#975501: marked as done (FTBFS: undefined reference to symbol 'SSL_get_verify_callback@@OPENSSL_1_1_0')

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 23:25:33 +0200
with message-id 
and subject line Fixed since 2.3.1-3
has caused the Debian Bug report #975501,
regarding FTBFS: undefined reference to symbol 
'SSL_get_verify_callback@@OPENSSL_1_1_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.)


-- 
975501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpaste
Version: 0.4.0-1
Severity: serious
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org

Dear Maintainer,

When rebuild your package, it FTBFS

g++ -std=c++17  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++17  
-Wl,-z,relro -Wl,-z,now -o dpaste dpaste-main.o libdpaste.a -lopendht -lnettle 
-lgnutls -largon2 -lhttp_parser -lpthread -lglibmm-2.4 -lgobject-2.0 -lglib-2.0 
-lsigc-2.0 -Llib/x86_64-linux-gnu -lcurlpp -Wl,-z,relro -lcurl -lb64 -lgpgmepp 
-L/usr/lib/x86_64-linux-gnu -lgpgme -lassuan -lgpg-error 
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libopendht.a(http.cpp.o): undefined 
reference to symbol 'SSL_get_verify_callback@@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libssl.so.1.1: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
--- End Message ---
--- Begin Message ---
opendht (2.3.1-3) unstable; urgency=medium
...
  * Added pkgconfig-extras.patch with libraries needed to link
simple C++ client.
...
 -- Petter Reinholdtsen   Mon, 26 Dec 2022 07:55:50 +0100--- End Message ---

Bug#562702: python-pam: Debian differences not clearly separated from upstream source

[Sebastian Ramacher]

Hi Bastian

On 2022-12-03 11:21:01 +0100, Bastian Germann wrote:
> Control: severity -1 serious
> X-Debbugs-Cc: d...@debian.org
> 
> On Sun, 27 Dec 2009 17:28:04 +1100 Ben Finney  
> wrote:
> > However, the ‘python-pam_0.4.2.orig.tar.gz’ does not match the actual
> > file at http://www.pangalactic.org/PyPAM/PyPAM-0.4.2.tar.gz>,
> > with many significant changes.
> > 
> > These changes should be separated from the pristine upstream source
> > (in a ‘python-pam_0.4.2-nn.diff.gz’, if using the Debian source format
> > 1.0) and the ‘python-pam_0.4.2.orig.tar.gz’ should match the tarball
> > available from upstream.
> > 
> > The provenance of these changes should also be recorded in the Debian
> > copyright file for the package.
> 
> The upstream source is no longer available. There is a fork including py3 
> support available at
> https://github.com/openEuler-BaseService/PyPAM.
> 
> We should switch to that as upstream or drop this package entirely.
> I am copying Matthias as he worked on the package mostly since it was 
> abandoned.
> For now, make this serious, to keep this out of bookworm in favour of 
> pam-python.

This will have no effect. python-pam is a key package and so won't be
removed automatically from bookworm because of this bug.

Also:

$ dak rm -Rn -s testing python-pam
Will remove the following packages from testing:

python-pam |   0.4.2-16 | source
python3-pam |   0.4.2-16 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x

Maintainer: Debian QA Group 

--- Reason ---

--

Checking reverse dependencies...
# Broken Build-Depends:
pam-python: python3-pam

Dependency problem found.


This seems like it would be easy enough to fix.

Cheers
-- 
Sebastian Ramacher

Processed: Move where the bug was

[Debian Bug Tracking System]

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

> reassign 975501 libopendht-dev 2.3.1-1
Bug #975501 [dpaste] FTBFS: undefined reference to symbol 
'SSL_get_verify_callback@@OPENSSL_1_1_0'
Bug reassigned from package 'dpaste' to 'libopendht-dev'.
No longer marked as found in versions dpaste/0.4.0-1.
Ignoring request to alter fixed versions of bug #975501 to the same values 
previously set
Bug #975501 [libopendht-dev] FTBFS: undefined reference to symbol 
'SSL_get_verify_callback@@OPENSSL_1_1_0'
Marked as found in versions opendht/2.3.1-1.
> affects 975501 src:dpaste
Bug #975501 [libopendht-dev] FTBFS: undefined reference to symbol 
'SSL_get_verify_callback@@OPENSSL_1_1_0'
Added indication that 975501 affects src:dpaste
> thanks
Stopping processing here.

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

Processed: reassign to closing package

[Debian Bug Tracking System]

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

> reassign 1027939 src:halide
Bug #1027939 {Done: Gianfranco Costamagna } 
[clang-14] clang-14 lost its (indirect) dependency on libclang-rt-14-dev
Bug reassigned from package 'clang-14' to 'src:halide'.
No longer marked as found in versions llvm-toolchain-14/1:14.0.6-10~exp4.
No longer marked as fixed in versions halide/14.0.0-3.
> fixed 1027939 14.0.0-3
Bug #1027939 {Done: Gianfranco Costamagna } 
[src:halide] clang-14 lost its (indirect) dependency on libclang-rt-14-dev
Marked as fixed in versions halide/14.0.0-3.
> thanks
Stopping processing here.

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

Bug#1028933: marked as pending in php-horde-http

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1028933 in php-horde-http 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/horde-team/php-horde-http/-/commit/e4b8ae3cd4363e9a9bc81f257418922b4da1eecf


d/patches: Add 1012_php8.2.patch. Fix PHP 8.2 deprecation warnings. (Closes: 
#1028933).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028933

Processed: Bug#1028933 marked as pending in php-horde-http

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028933 [src:php-horde-http] php-horde-http: (autopkgtest) needs update 
for php8.2: deprecation warnings on stderr
Added tag(s) pending.

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

Bug#1011445: marked as pending in ruby-license-finder

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1011445 in ruby-license-finder 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/ruby-team/ruby-license-finder/-/commit/c8a2a2c0bed2b9f683068eb4c635ddad8891ec96


Conflict with ruby-gitlab-license-finder

  * d/control: Declare a conflict with ruby-gitlab-license-finder
(closes: #1011445).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011445

Processed: Bug#1011445 marked as pending in ruby-license-finder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011445 [ruby-gitlab-license-finder,ruby-license-finder] 
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install 
together
Added tag(s) pending.

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

Bug#1028944: marked as done (php-horde-serialize: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 20:58:30 +
with message-id 
and subject line Bug#1028944: fixed in php-horde-serialize 2.0.5-10
has caused the Debian Bug report #1028944,
regarding php-horde-serialize: (autopkgtest) needs update for php8.2: 
deprecation warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-serialize
Version: 2.0.5-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-serialize 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-serializefrom testing2.0.5-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-serialize/30356866/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.wmpitqx9/downtmp/build.mjM/src/Horde_Serialize-2.0.5/test/Horde/Serialize/phpunit.xml


..PHP Deprecated:  Function utf8_encode() is deprecated in 
/usr/share/php/Horde/String.php on line 119
..8 / 8 
(100%)


Time: 00:00.009, Memory: 6.00 MB

OK (8 tests, 77 assertions)
autopkgtest [06:17:13]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: php-horde-serialize
Source-Version: 2.0.5-10
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated php-horde-serialize 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2023 21:40:52 +0100
Source: php-horde-serialize
Architecture: source
Version: 2.0.5-10
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers 
Changed-By: Mike Gabriel 
Closes: 1028944
Changes:
 php-horde-serialize (2.0.5-10) unstable; urgency=medium
 .
   * d/watch: Switch to format version 4.
   * d/control: Bump Standards-Version: to 4.6.2. No changes needed.
   * d/t/control: Explicitly require php-horde-util (>= 2.5.12-2~) to silence 
PHP
 8.2 deprecation warnings in autopkgtest. (Closes: #1028944).
Checksums-Sha1:
 0a5e49d2439a3ea001db5ef21039abc3d80d0e28 2234 php-horde-serialize_2.0.5-10.dsc
 c812ee71343320077e9e673f13523652511c56a2 4172 
php-horde-serialize_2.0.5-10.debian.tar.xz
 2ab89bfa2efbac9d068bc6dab77e9e052a4d327a 6947 
php-horde-serialize_2.0.5-10_source.buildinfo
Checksums-Sha256:
 046bd2709b3f9cb9c56f65f96085f4f756b2cff58cef26d022c8

Bug#1028943: marked as done (php-horde-secret: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 20:58:23 +
with message-id 
and subject line Bug#1028943: fixed in php-horde-secret 2.0.6-10
has caused the Debian Bug report #1028943,
regarding php-horde-secret: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-secret
Version: 2.0.6-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-secret fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-secret   from testing2.0.6-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-secret/30356865/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.ucs68m9x/downtmp/build.55S/src/Horde_Secret-2.0.6/test/Horde/Secret/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
.PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
.PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
.PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
..PHP Deprecated:  Creation of dynamic property 
Horde_Crypt_Blowfish::$iv is deprecated in 
/usr/share/php/Horde/Crypt/Blowfish.php on line 173

...8 / 8 (100%)

Time: 00:00.020, Memory: 6.00 MB

OK (8 tests, 8 assertions)
autopkgtest [06:17:10]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: php-horde-secret
Source-Version: 2.0.6-10
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated php-horde-secret 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2023 21:30:51 +0100
Source: php-horde-secret
Architecture: source
Version: 2.0.6-10
Distribution: unstable
Urgency: medium
Maintainer: Horde Main

Bug#1029654: sofia-sip: CVE-2023-22741: heap-over-flow in stun_parse_attribute

[Salvatore Bonaccorso]

Source: sofia-sip
Version: 1.12.11+20110422.1+1e14eea~dfsg-3
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for sofia-sip.

CVE-2023-22741[0]:
| Sofia-SIP is an open-source SIP User-Agent library, compliant with the
| IETF RFC3261 specification. In affected versions Sofia-SIP **lacks
| both message length and attributes length checks** when it handles
| STUN packets, leading to controllable heap-over-flow. For example, in
| stun_parse_attribute(), after we get the attribute's type and length
| value, the length will be used directly to copy from the heap,
| regardless of the message's left size. Since network users control the
| overflowed length, and the data is written to heap chunks later,
| attackers may achieve remote code execution by heap grooming or other
| exploitation methods. The bug was introduced 16 years ago in sofia-sip
| 1.12.4 (plus some patches through 12/21/2006) to in tree libs with
| git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@3774
| d0543943-73ff-0310-b7d9-9358b9ac24b2. Users are advised to upgrade.
| There are no known workarounds for this vulnerability.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-22741
https://www.cve.org/CVERecord?id=CVE-2023-22741
[1] 
https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-8599-x7rq-fr54
[2] 
https://github.com/freeswitch/sofia-sip/commit/9defd6f72dd416ee4fcc1a23cccbb159990da0f6

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1028942: marked as pending in php-horde-passwd

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1028942 in php-horde-passwd 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/horde-team/php-horde-passwd/-/commit/76128e7fa8bf390a788981a2915f136d43a9


d/t/control: Explicitly require php-horde-db (>= 2.4.1-8~) to silence PHP 8.2 
deprecation warnings in autopkgtest. (Closes: #1028942).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028942

Processed: Bug#1028942 marked as pending in php-horde-passwd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028942 [src:php-horde-passwd] php-horde-passwd: (autopkgtest) needs 
update for php8.2: deprecation warnings on stderr
Added tag(s) pending.

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

Bug#1026607: marked as done (ruby-jekyll-paginate-v2: FTBFS: ERROR: Test "ruby3.1" failed: :85:in `require': cannot load such fi

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 21:27:32 +0100
with message-id 
and subject line Unreproducible
has caused the Debian Bug report #1026607,
regarding ruby-jekyll-paginate-v2: FTBFS: ERROR: Test "ruby3.1" failed: 
:85:in 
`require': cannot load such file -- jekyll-paginate-v2/version (LoadError)
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.)


-- 
1026607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jekyll-paginate-v2
Version: 3.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> :85:in
>  `require': cannot load such file -- jekyll-paginate-v2/version (LoadError)
> Did you mean?  jekyll-watch/version
>   from 
> :85:in
>  `require'
>   from /<>/spec/spec_helper.rb:5:in `'
>   from /<>/spec/generator/defaults_spec.rb:1:in 
> `require_relative'
>   from /<>/spec/generator/defaults_spec.rb:1:in ` (required)>'
>   from 
> :85:in
>  `require'
>   from 
> :85:in
>  `require'
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in 
> `block in '
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
> `select'
>   from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
> `'
> rake aborted!
> Command failed with status (1): [ruby -w -I"specs" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "spec/generator/defaults_spec.rb" "spec/generator/paginationPage_spec.rb" 
> "spec/generator/paginator_spec.rb" "spec/generator/utils_spec.rb"  -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/ruby-jekyll-paginate-v2_3.0.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 ---
Hi,

I cannot reproduce the bug. The package builds fine. It might have been
affected by the broken jekyll package, which has already been fixed. We will do
several rebuilds during the ruby3.1 transition anyways. If this issue pops up
again, we'll deal with it.

Regards, Daniel--- End Message ---

Bug#1029154: marked as done (swift: CVE-2022-47950)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 19:49:58 +
with message-id 
and subject line Bug#1029200: fixed in swift 2.26.0-10+deb11u1
has caused the Debian Bug report #1029200,
regarding swift: CVE-2022-47950
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.)


-- 
1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for swift.

CVE-2022-47950:
OSSA-2023-001: Arbitrary file access through custom S3 XML entities

Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML
parser. By supplying specially crafted XML files an authenticated user
may coerce the S3 API into returning arbitrary file contents from the
host server resulting in unauthorized read access to potentially
sensitive data; this impacts both s3api deployments (Rocky or later),
and swift3 deployments (Queens and earlier, no longer actively
developed). Only deployments with S3 compatibility enabled are
affected.

https://www.openwall.com/lists/oss-security/2023/01/17/1




If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-47950
https://www.cve.org/CVERecord?id=CVE-2022-47950

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: swift
Source-Version: 2.26.0-10+deb11u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated swift 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, 19 Jan 2023 17:07:48 +0100
Source: swift
Architecture: source
Version: 2.26.0-10+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1029200
Changes:
 swift (2.26.0-10+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2022-47950 / OSSA-2023-001: Arbitrary file access through custom S3 XML
 entities. Add upstream patch backported to Bullseye:
 CVE-2022-47950-stable-victoria.patch (Closes: #1029200).
   * Exclude test TestCNAMELookup.test_host_is_storage_domain().
Checksums-Sha1:
 342039f97da0f053e6743b98af2a05a3fd8189a6 3331 swift_2.26.0-10+deb11u1.dsc
 25d8adad840c4da26213d01ecbc2541216c846a3 2302476 swift_2.26.0.orig.tar.xz
 ac4a72c7311d3d963586b164a543323e564e535f 26220 
swift_2.26.0-10+deb11u1.debian.tar.xz
 0a9351e376484f3b9a8cabd6aa7dd9451649aacd 15172 
swift_2.26.0-10+deb11u1_amd64.buildinfo
Checksums-Sha256:
 4c8b3083b0438ac282174db9d808fed50c454b48a4b53dbacfdfac2079808df5 3331 
swift_2.26.0-10+deb11u1.dsc
 68b57dce54445c4d0554dbf9efc112eccc1fd961e75015900474d8cae013ead9 2302476 
swift_2.26.0.orig.tar.xz
 16955caed337163096dc9b7a6f4b1ef78ac4753f31498bacef35bd666c5eb2cd 26220 
swift_2.26.0-10+deb11u1.debian.tar.xz
 0f653bd60f337e1143c0721c51950d7f7ce846c7a9d2dae31e75e8717e34454b 15172 
swift_2.26.0-10+deb11u1_amd64.buildinfo
Files:
 41f851b43a8b358fff7b31e39c104186 3331 net optional swift_2.26.0-10+deb11u1.dsc
 611351b21eade1272085bddcea8259a1 2302476 net optional swift_2.26.0.orig.tar.xz
 ba3f5f5b8b1af62b23151e5928e06724 26220 net optional 
swift_2.26.0-10+deb11u1.debian.tar.xz
 4a086a53f4d6feae529374c62e14d014 15172 net optional 
swift_2.26.0-10+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE3+Kkgn20FPaRPp/ST56os/RrPrsFAmPKUs8ACgkQT56os/Rr
PrtVfRAAh49w0DFqyrehSNr/eX5TT7h7KVtxTUOaK2RNxu4D5UNF0XNQ04Irzvpd
A3ZxZFm2gzd2xvP62blfXeRb4se3B/BlvR0dyKFnr76vKSG/PuOVmMUosL0Gsvnv
FryvzJ/v9XAinnp0QADdKgrBhY6omPbCia1ic+S2JtcUomzCGLuSPZm1O5OV3kIL
Q5Ujtg9w1RO9uo5hOyILA+kkFvLYfeu4vJcofrQsikUca13GQab4QwBGJJ3/AVPl
V9bTrAa1na4wXPJCPzz+KB1q9JnmOvbbfkXxByECyOYOXL0WnQG3IKJi/AwKHlpC
GpiwEWM+pZtxpfO67DIDIaBCKyChQRHEkLwLo31kA/gurdOzNloe6Hc60agysYqf
bDdJqAqiSezs30k7Pi9toEUm

Bug#1029200: marked as done (CVE-2022-47950: Arbitrary file access through custom S3 XML entities)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 19:49:58 +
with message-id 
and subject line Bug#1029200: fixed in swift 2.26.0-10+deb11u1
has caused the Debian Bug report #1029200,
regarding CVE-2022-47950: Arbitrary file access through custom S3 XML entities
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.)


-- 
1029200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift-proxy
Version: 2.26.0-10
Severity: serious
Tags: patch

Title: Arbitrary file access through custom S3 XML entities
Reporter: Sébastien Meriot (OVH)
Products: Swift
Affects: <2.28.1, >=2.29.0 <2.29.2, ==2.30.0

Description:
Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML
parser. By supplying specially crafted XML files an authenticated
user may coerce the S3 API into returning arbitrary file contents
from the host server resulting in unauthorized read access to
potentially sensitive data; this impacts both s3api deployments
(Rocky or later), and swift3 deployments (Queens and earlier, no
longer actively developed). Only deployments with S3 compatibility
enabled are affected.

See attached patches. Unless a flaw is discovered in them, these
patches will be merged to their corresponding branches on the public
disclosure date. The master branch patch applies cleanly to
stable/zed, stable/yoga, stable/xena and stable/wallaby branches,
but separate copies of it are attached for each for the sake of
clarity. The fix could be applied with some fuzz to branches as old
as stable/train, and with some minor unit test adjustments as far
back as stable/rocky. Note that the stable/wallaby branch is under
extended maintenance (as are older branches) and will receive no new
point releases, but a patch for it is provided as a courtesy.

CVE: CVE-2022-47950

Proposed public disclosure date/time:
2023-01-17, 1500UTC
Please do not make the issue public (or release public patches)
before this coordinated embargo date.

Original private report:
https://launchpad.net/bugs/1998625
For access to read and comment on this report, please reply to me
with your Launchpad username and I will subscribe you.
--- End Message ---
--- Begin Message ---
Source: swift
Source-Version: 2.26.0-10+deb11u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated swift 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, 19 Jan 2023 17:07:48 +0100
Source: swift
Architecture: source
Version: 2.26.0-10+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1029200
Changes:
 swift (2.26.0-10+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2022-47950 / OSSA-2023-001: Arbitrary file access through custom S3 XML
 entities. Add upstream patch backported to Bullseye:
 CVE-2022-47950-stable-victoria.patch (Closes: #1029200).
   * Exclude test TestCNAMELookup.test_host_is_storage_domain().
Checksums-Sha1:
 342039f97da0f053e6743b98af2a05a3fd8189a6 3331 swift_2.26.0-10+deb11u1.dsc
 25d8adad840c4da26213d01ecbc2541216c846a3 2302476 swift_2.26.0.orig.tar.xz
 ac4a72c7311d3d963586b164a543323e564e535f 26220 
swift_2.26.0-10+deb11u1.debian.tar.xz
 0a9351e376484f3b9a8cabd6aa7dd9451649aacd 15172 
swift_2.26.0-10+deb11u1_amd64.buildinfo
Checksums-Sha256:
 4c8b3083b0438ac282174db9d808fed50c454b48a4b53dbacfdfac2079808df5 3331 
swift_2.26.0-10+deb11u1.dsc
 68b57dce54445c4d0554dbf9efc112eccc1fd961e75015900474d8cae013ead9 2302476 
swift_2.26.0.orig.tar.xz
 16955caed337163096dc9b7a6f4b1ef78ac4753f31498bacef35bd666c5eb2cd 26220 
swift_2.26.0-10+deb11u1.debian.tar.xz
 0f653bd60f337e1143c0721c51950d7f7ce846c7a9d2dae31e75e8717e34454b 15172 
swift_2.26.0-10+deb11u1_amd64.buildinfo
Files:
 41f851b43a8b358fff7b31e39c104186 3331 net optional swift_2.26.0-10+deb11u1.dsc
 611351b21eade1272085bddcea8259a1 2302476 net optional swift_2.26.0.orig.tar.xz
 ba3f5f5b8b1af62b23151

Bug#1029622: tuxguitar-alsa fails to install

[Helmar Gerloni]

Hi Tony,

sorry for causing so much work with tuxguitar, and thanks for your efforts!

Do you think it would make sense to merge all the tuxguitar* packages into one 
package tuxguitar with arch-any? Maybe this would solve these build problems.

I could try this out and put a new package on mentors; just let me know.

Regards,   Helmar.

Bug#1028941: marked as done (php-horde-notification: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 19:35:18 +
with message-id 
and subject line Bug#1028941: fixed in php-horde-notification 2.0.4-10
has caused the Debian Bug report #1028941,
regarding php-horde-notification: (autopkgtest) needs update for php8.2: 
deprecation warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-notification
Version: 2.0.4-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-notification 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-notification from testing2.0.4-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-notification/30356863/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


.IIPHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_Handler_Decorator_LogTest::$logger 
is deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/Handler/Decorator/LogTest.php 
on line 36
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_Handler_Decorator_LogTest::$log is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/Handler/Decorator/LogTest.php 
on line 37
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$handler is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$handler is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 3

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1029438 texlive-latex-base
Bug #1029438 [src:auctex] auctex: FTBFS in bookworm (LaTeX Error: File 
`pdftexcmds.sty' not found)
Bug reassigned from package 'src:auctex' to 'texlive-latex-base'.
No longer marked as found in versions auctex/12.2-1.
Ignoring request to alter fixed versions of bug #1029438 to the same values 
previously set
> forcemerge 1025985 1029438
Bug #1025985 {Done: Hilmar Preusse } [texlive-latex-base] 
hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra
Bug #1029460 {Done: Hilmar Preusse } [texlive-latex-base] 
glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)
Bug #1029438 [texlive-latex-base] auctex: FTBFS in bookworm (LaTeX Error: File 
`pdftexcmds.sty' not found)
Marked Bug as done
Added indication that 1029438 affects src:glosstext,src:glosstex
Marked as fixed in versions texlive-base/2022.20230122-1.
Marked as found in versions texlive-base/2022.20220923-1.
Added tag(s) bookworm and sid.
Bug #1029460 {Done: Hilmar Preusse } [texlive-latex-base] 
glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)
Merged 1025985 1029438 1029460
> affects 1025985 src:auctex
Bug #1025985 {Done: Hilmar Preusse } [texlive-latex-base] 
hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra
Bug #1029438 {Done: Hilmar Preusse } [texlive-latex-base] 
auctex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)
Bug #1029460 {Done: Hilmar Preusse } [texlive-latex-base] 
glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found)
Added indication that 1025985 affects src:auctex
Added indication that 1029438 affects src:auctex
Added indication that 1029460 affects src:auctex
> thanks
Stopping processing here.

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

Bug#1028940: marked as done (php-horde-mime: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 19:20:50 +
with message-id 
and subject line Bug#1028940: fixed in php-horde-mime 2.11.2-2
has caused the Debian Bug report #1028940,
regarding php-horde-mime: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-mime
Version: 2.11.2-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-mime fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-mime from testing2.11.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-mime/30356862/log.gz

.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decod

Bug#1028939: marked as done (php-horde-mapi: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 19:20:41 +
with message-id 
and subject line Bug#1028939: fixed in php-horde-mapi 1.0.10-5
has caused the Debian Bug report #1028939,
regarding php-horde-mapi: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-mapi
Version: 1.0.10-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-mapi fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-mapi from testing1.0.10-4
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-mapi/30356861/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/phpunit.xml


..PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111
.PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111
.PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111
.PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111

.  6 / 6 (100%)

Time: 00:00.041, Memory: 6.00 MB

OK (6 tests, 183 assertions)
autopkgtest [06:17:10]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: php-horde-mapi
Source-Version: 1.0.10-5
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated php-horde-mapi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2023 19:53:59 +0100
Source: php-horde-mapi
Architecture: source
Version: 1.0.10-5
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers

Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Martin]

Sorry, that went to the wrong bug report :-(

Laurent, Jeremy, Iain, I hope you are OK with the upload to
experimental!


On 2023-01-25 15:11, Sebastian Reichel wrote:
> [[PGP Signed Part:Undecided]]
> Hi Martin,
>
> On Tue, Jan 24, 2023 at 10:50:52PM +, Martin wrote:
>> Hi Sebastian,
>> 
>> I wonder, if I should upload libproxy with your github patch¹ to
>> experimental. Then people affected (or not affected) by the bug can test
>> easily. Or you may upload, of course! :-)
>> 
>> Cheers
>> 
>> ¹ https://github.com/libproxy/libproxy/issues/199#issuecomment-1401124997
>
> sure, feel free to upload it to experimental. FWIW I do not
> understand the root cause of this issue. I'm a bit worried,
> that the patch masks a security relevant bug. It would be great
> if somebody with better C++ knowledge can look into this.
>
> The bug seems quite strange considering the segmentation fault is
> happening due to the destruction of an empty vector from the standard
> library and only in combination with glib-networking.
>
> FWIW long term the problem will be solved by glib-networking
> removing the libproxy dependency:
>
> https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/205
>
> Greetings,
>
> -- Sebastian
>
> [[End of PGP Signed Part]]

Bug#1028941: marked as pending in php-horde-notification

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1028941 in php-horde-notification 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/horde-team/php-horde-notification/-/commit/f4240b7a5a8a2ba8535f92eacf03aaa3fa0d5b50


debian/patches: Add 1012_php8.2.patch. Fix PHP 8.2 deprecation warnings. 
(Closes: #1028941).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028941

Processed: Bug#1028941 marked as pending in php-horde-notification

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028941 [src:php-horde-notification] php-horde-notification: (autopkgtest) 
needs update for php8.2: deprecation warnings on stderr
Added tag(s) pending.

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

Processed: Bug#1028940 marked as pending in php-horde-mime

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028940 [src:php-horde-mime] php-horde-mime: (autopkgtest) needs update 
for php8.2: deprecation warnings on stderr
Added tag(s) pending.

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

Bug#1028940: marked as pending in php-horde-mime

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1028940 in php-horde-mime 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/horde-team/php-horde-mime/-/commit/ed7ca7892bf4683e0cacaad6b03318624214f904


d/t/control: Explicitly require php-horde-util (>= 2.5.12-2~) to silence PHP 
8.2 deprecation warnings in autopkgtest. (Closes: #1028940).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028940

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1029460 texlive-latex-base
Bug #1029460 [src:glosstex] glosstex: FTBFS in bookworm (LaTeX Error: File 
`pdftexcmds.sty' not found)
Bug reassigned from package 'src:glosstex' to 'texlive-latex-base'.
No longer marked as found in versions glosstex/0.4.dfsg.1-4.
Ignoring request to alter fixed versions of bug #1029460 to the same values 
previously set
> forcemerge 1025985 1029460
Bug #1025985 {Done: Hilmar Preusse } [texlive-latex-base] 
hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra
Bug #1029460 [texlive-latex-base] glosstex: FTBFS in bookworm (LaTeX Error: 
File `pdftexcmds.sty' not found)
Marked Bug as done
Added indication that 1029460 affects src:glosstext,src:glosstex
Marked as fixed in versions texlive-base/2022.20230122-1.
Marked as found in versions texlive-base/2022.20220923-1.
Merged 1025985 1029460
> thanks
Stopping processing here.

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

Bug#1028837: python-zstandard 0.19.0-1 possibly no more compatible with python3.10

[Étienne Mollier]

Hi s3v,

s3v, on 2023-01-23:
> On Mon, 23 Jan 2023 19:06:01 +0100 s3v  wrote:
> > exceptiongroup module has been packaged in Debian [1]
> 
> Sorry for the mess, there is the link:
> 
> https://tracker.debian.org/pkg/python-exceptiongroup

Don't be sorry, on the contrary many thanks for the pointer!  :)

Not sure how come lousy me missed that package.  I will use your
suggestion because the current approach with bumping to Python
3.11 only is currently stalling in unstable, due to reverse
dependencies in testing failing their autopkgtest[2].
Supporting python 3.10 a little longer shouldn't hurt.

[2]: https://qa.debian.org/excuses.php?package=python-zstandard

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.
On air: Marillion - The Web


signature.asc
Description: PGP signature

Processed: Re: Bug#1029044: gcc-12-cross-mipsen: source and binary version go out of sync

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs
Bug #1029044 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Added tag(s) ftbfs.
> clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Bug #1029044 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug 1029044 cloned as bugs 1029634-1029642
> reassign -2 src:gcc-10-cross
Bug #1029634 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug reassigned from package 'src:gcc-12-cross-mipsen' to 'src:gcc-10-cross'.
No longer marked as found in versions gcc-12-cross-mipsen/1+c2.
Ignoring request to alter fixed versions of bug #1029634 to the same values 
previously set
> retitle -2 gcc-10-cross: source and binary version go out of sync
Bug #1029634 [src:gcc-10-cross] gcc-12-cross-mipsen: source and binary version 
go out of sync
Changed Bug title to 'gcc-10-cross: source and binary version go out of sync' 
from 'gcc-12-cross-mipsen: source and binary version go out of sync'.
> reassign -3 src:gcc-10-cross-ports
Bug #1029635 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug reassigned from package 'src:gcc-12-cross-mipsen' to 
'src:gcc-10-cross-ports'.
No longer marked as found in versions gcc-12-cross-mipsen/1+c2.
Ignoring request to alter fixed versions of bug #1029635 to the same values 
previously set
> retitle -3 gcc-10-cross-ports: source and binary version go out of sync
Bug #1029635 [src:gcc-10-cross-ports] gcc-12-cross-mipsen: source and binary 
version go out of sync
Changed Bug title to 'gcc-10-cross-ports: source and binary version go out of 
sync' from 'gcc-12-cross-mipsen: source and binary version go out of sync'.
> reassign -4 src:gcc-11-cross
Bug #1029636 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug reassigned from package 'src:gcc-12-cross-mipsen' to 'src:gcc-11-cross'.
No longer marked as found in versions gcc-12-cross-mipsen/1+c2.
Ignoring request to alter fixed versions of bug #1029636 to the same values 
previously set
> retitle -4 gcc-11-cross: source and binary version go out of sync
Bug #1029636 [src:gcc-11-cross] gcc-12-cross-mipsen: source and binary version 
go out of sync
Changed Bug title to 'gcc-11-cross: source and binary version go out of sync' 
from 'gcc-12-cross-mipsen: source and binary version go out of sync'.
> reassign -5 src:gcc-11-cross-ports
Bug #1029637 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug reassigned from package 'src:gcc-12-cross-mipsen' to 
'src:gcc-11-cross-ports'.
No longer marked as found in versions gcc-12-cross-mipsen/1+c2.
Ignoring request to alter fixed versions of bug #1029637 to the same values 
previously set
> retitle -5 gcc-11-cross-ports: source and binary version go out of sync
Bug #1029637 [src:gcc-11-cross-ports] gcc-12-cross-mipsen: source and binary 
version go out of sync
Changed Bug title to 'gcc-11-cross-ports: source and binary version go out of 
sync' from 'gcc-12-cross-mipsen: source and binary version go out of sync'.
> reassign -6 src:gcc-11-cross-mipsen
Bug #1029638 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug reassigned from package 'src:gcc-12-cross-mipsen' to 
'src:gcc-11-cross-mipsen'.
No longer marked as found in versions gcc-12-cross-mipsen/1+c2.
Ignoring request to alter fixed versions of bug #1029638 to the same values 
previously set
> retitle -6 gcc-11-cross-mipsen: source and binary version go out of sync
Bug #1029638 [src:gcc-11-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Changed Bug title to 'gcc-11-cross-mipsen: source and binary version go out of 
sync' from 'gcc-12-cross-mipsen: source and binary version go out of sync'.
> block -6 by -4
Bug #1029638 [src:gcc-11-cross-mipsen] gcc-11-cross-mipsen: source and binary 
version go out of sync
1029638 was not blocked by any bugs.
1029638 was not blocking any bugs.
Added blocking bug(s) of 1029638: 1029636
> reassign -7 src:gcc-12-cross
Bug #1029639 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
Bug reassigned from package 'src:gcc-12-cross-mipsen' to 'src:gcc-12-cross'.
No longer marked as found in versions gcc-12-cross-mipsen/1+c2.
Ignoring request to alter fixed versions of bug #1029639 to the same values 
previously set
> retitle -7 gcc-12-cross: source and binary version go out of sync
Bug #1029639 [src:gcc-12-cross] gcc-12-cross-mipsen: source and binary version 
go out of sync
Changed Bug title to 'gcc-12-cross: source and binary version go out of sync' 
from 'gcc-12-cross-mipsen: source and binary version go out of sync'.
> block -1 by -7
Bug #1029044 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary 
version go out of sync
1029044 was not blocked by any bugs.
1029044 was not blocking any bugs.
Added blocking bug(s) of 1029044: 1029639
> reassign -8 s

Bug#1029044: gcc-12-cross-mipsen: source and binary version go out of sync

[Adrian Bunk]

Control: tags -1 ftbfs
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 src:gcc-10-cross
Control: retitle -2 gcc-10-cross: source and binary version go out of sync
Control: reassign -3 src:gcc-10-cross-ports
Control: retitle -3 gcc-10-cross-ports: source and binary version go out of sync
Control: reassign -4 src:gcc-11-cross
Control: retitle -4 gcc-11-cross: source and binary version go out of sync
Control: reassign -5 src:gcc-11-cross-ports
Control: retitle -5 gcc-11-cross-ports: source and binary version go out of sync
Control: reassign -6 src:gcc-11-cross-mipsen
Control: retitle -6 gcc-11-cross-mipsen: source and binary version go out of 
sync
Control: block -6 by -4
Control: reassign -7 src:gcc-12-cross
Control: retitle -7 gcc-12-cross: source and binary version go out of sync
Control: block -1 by -7
Control: reassign -8 src:gcc-12-cross-ports
Control: retitle -8 gcc-12-cross-ports: source and binary version go out of sync
Control: reassign -9 src:gcc-13-cross
Control: retitle -9 gcc-13-cross: source and binary version go out of sync
Control: reassign -10 src:gcc-13-cross-ports
Control: retitle -10 gcc-13-cross-ports: source and binary version go out of 
sync

On Mon, Jan 16, 2023 at 09:21:52PM +0100, Paul Gevers wrote:
> Source: gcc-12-cross-mipsen
> Version: 1+c2
> Severity: serious
> 
> Dear maintainer,
> 
> The current version in unstable is stuck, because the mips64el build
> is kept in Uploaded state. Asking around on #d-buildd, I got the
> following discussion:
> 
> [20:09:34]  mips64el 3days in uploaded state feels like an issue, 
> right? https://buildd.debian.org/status/package.php?p=gcc-12-cross-mipsen
> [20:18:32]  probably means dak rejected it
> [20:18:45]  Your upload included the binary package 
> cpp-12-mips-linux-gnu, version 12.2.0-13cross1, for mips64el,
> [20:18:48]  however unstable already has version 12.2.0-14cross2.
> [20:19:09]  
> coccia:/srv/ftp-master.debian.org/queue/reject/gcc-12-cross-mipsen_3+c1_mips64el-buildd.changes.reason
> [20:29:57]  the higher version is
> [20:29:57]  Source: gcc-12-cross-mipsen (2+c1)
> [20:30:23]  so the generated version numbers are broken
> [20:32:07]  not for the first time afair
> [[21:04:30]  adsb: thanks for looking; but the source is 3+c1, no? or 
> did the older one generate a newer binary?
> 
> You may want to check your logic.

The packaging is copied from gcc-12-cross,
problems have to be fixed there first,
and also in the other gcc-*-cross* packages.

There are at least 3 problems:

1. The way debian/new_cross_version.sh uses "apt-cache policy" to create 
a version number makes the package not reproducible even if the same 
versions of the build dependencies are installed, and it also causes 
problems like this one here.

Other packages using {binutils,gcc-*,gdb}-source seem to get it right, e.g.:

Package: gcc-xtensa-lx106
Source: gcc-xtensa-lx106 (8)
Version: 10.2.1-6+8+b1
Built-Using: gcc-10 (= 10.2.1-6)

There is no reason why the gcc-*-cross* packages could not use similar 
versioning.


2. binary-any packages built from the same gcc-*-cross* packages 
currently have >= dependencies on binary-all packages built from
the same sources. Since the version number of the gcc-*-cross* packages
packages contains the version of the gcc-*-source package, this does
not only prevent binNMUs (which itself is already an RC bug) but also
similarly causes problems like #1028441 when packages are built later
on an architecture (in this case due to #1026129, which was caused by
#1026245 in src:gcc-12).

The correct solution is to make such binary-all packages binary-any,
which allows = dependencies and removes all such race conditions and
non-binNMUableness.


3. Built-Using in the binary-all packages is something that should IMHO 
become a non-overridable automatic REJECT in dak.

The gcc-*-cross* packages seem to avoid the 
built-using-field-on-arch-all-package
lintian tag by not declaring the Built-Using in debian/control, but 
adding it during the build.[1]

Example package: lib32gcc-s1-s390x-cross

I've just filed #1029633 asking for a lintian tag for that.


> Paul

cu
Adrian

[1] https://sources.debian.org/src/gcc-12/12.2.0-14/debian/rules.conf/#L1286

Bug#1027605: marked as done (findpython: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 18:19:10 +
with message-id 
and subject line Bug#1027605: fixed in findpython 0.2.3-1
has caused the Debian Bug report #1027605,
regarding findpython: FTBFS: ImportError: cannot import name 'LegacyVersion' 
from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py)
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.)


-- 
1027605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: findpython
Version: 0.2.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build" 
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.10 
> * Building wheel...
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/wrappers.py", line 319, in 
> _call_hook
> raise BackendUnavailable(data.get('traceback', ''))
> pep517.wrappers.BackendUnavailable: Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 77, in _build_backend
> obj = import_module(mod_path)
>   File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1050, in _gcd_import
>   File "", line 1027, in _find_and_load
>   File "", line 1006, in _find_and_load_unlocked
>   File "", line 688, in _load_unlocked
>   File "", line 883, in exec_module
>   File "", line 241, in _call_with_frames_removed
>   File "/usr/lib/python3/dist-packages/pdm/pep517/api.py", line 10, in 
> 
> from pdm.pep517.editable import EditableBuilder
>   File "/usr/lib/python3/dist-packages/pdm/pep517/editable.py", line 13, in 
> 
> from pdm.pep517.wheel import WheelBuilder
>   File "/usr/lib/python3/dist-packages/pdm/pep517/wheel.py", line 24, in 
> 
> from pdm.pep517.base import Builder
>   File "/usr/lib/python3/dist-packages/pdm/pep517/base.py", line 12, in 
> 
> from pdm.pep517.metadata import Metadata
>   File "/usr/lib/python3/dist-packages/pdm/pep517/metadata.py", line 20, in 
> 
> from pdm.pep517.version import DynamicVersion
>   File "/usr/lib/python3/dist-packages/pdm/pep517/version.py", line 10, in 
> 
> from pdm.pep517.scm import get_version_from_scm
>   File "/usr/lib/python3/dist-packages/pdm/pep517/scm.py", line 17, in 
> 
> from packaging.version import LegacyVersion, Version
> ImportError: cannot import name 'LegacyVersion' from 'packaging.version' 
> (/usr/lib/python3/dist-packages/packaging/version.py)
> 
> ERROR Backend 'pdm.pep517.api' is not available.
> E: pybuild pybuild:388: build: plugin pyproject failed with: exit code=1: 
> python3.10 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:9: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/findpython_0.2.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: findpython
Source-Version: 0.2.3-1
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest 

Bug#1028936: marked as done (php-horde-itip: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 18:09:17 +
with message-id 
and subject line Bug#1028936: fixed in php-horde-itip 2.1.2-9
has caused the Debian Bug report #1028936,
regarding php-horde-itip: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-itip
Version: 2.1.2-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-itip fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-itip from testing2.1.2-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-itip/30356858/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_It

Bug#1028937: marked as done (php-horde-log: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 18:09:24 +
with message-id 
and subject line Bug#1028937: fixed in php-horde-log 2.3.0-9
has caused the Debian Bug report #1028937,
regarding php-horde-log: (autopkgtest) needs update for php8.2: deprecation 
warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-log
Version: 2.3.0-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-log fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-log  from testing2.3.0-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-log/30356859/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/phpunit.xml


PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$log is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$logger is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$log is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$logger is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ExactLevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ExactLevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ExactLevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ExactLevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ExactLevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ExactLevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_LevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/LevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_LevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/LevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_LevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/

Bug#1025366: Note that the bug is also present in 7.0.6

[Gianfranco Costamagna]

Hello,

Please then send the full dkms.log message, because I can't really reproduce it.

G.

On Wed, 25 Jan 2023 18:09:57 +0100 Eric Valette  wrote:

On 25/01/2023 10:36, Gianfranco Costamagna wrote:
> 
> On Sun, 4 Dec 2022 11:19:52 +0100 Eric Valette  
> wrote:
>> Already fixed there same ways but did not report the bug hoping it 
>> will be soon fixed.

>>
>> -- eric
>>
> 
> Hello, please try 7.0.6

> thanks

Same error, same fix. As long as the file does not chnage...

-- eric




OpenPGP_signature
Description: OpenPGP digital signature

Processed: fixed in 7.0.6 according to https://ci.debian.net/data/autopkgtest/testing/amd64/v/virtualbox/30688552/log.gz

[Debian Bug Tracking System]

Processing control commands:

> fixed 1025366 7.0.6-dfsg-1
Bug #1025366 [virtualbox-dkms] virtualbox-dkms does not compile with gcc-12
Marked as fixed in versions virtualbox/7.0.6-dfsg-1.
> close 1025366
Bug #1025366 [virtualbox-dkms] virtualbox-dkms does not compile with gcc-12
Marked Bug as done

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

Bug#1025366: fixed in 7.0.6 according to https://ci.debian.net/data/autopkgtest/testing/amd64/v/virtualbox/30688552/log.gz

[Gianfranco Costamagna]

control: fixed 1025366 7.0.6-dfsg-1
control: close 1025366
thanks

Looks fixed according to ci.debian.net

G.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1028937: marked as pending in php-horde-log

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1028937 in php-horde-log 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/horde-team/php-horde-log/-/commit/56ba788a631422c8845887b4f4bc342d9158eb51


debian/patches: Add 1012_php8.2.patch. Fix PHP 8.2 deprecation warnings. 
(Closes: #1028937).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028937

Bug#1028935: marked as done (php-horde-injector: (autopkgtest) needs update for php8.2: deprecation warnings on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 17:37:24 +
with message-id 
and subject line Bug#1028935: fixed in php-horde-injector 2.0.5-12
has caused the Debian Bug report #1028935,
regarding php-horde-injector: (autopkgtest) needs update for php8.2: 
deprecation warnings on stderr
to be marked as done.

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

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


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

Source: php-horde-injector
Version: 2.0.5-11
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-injector 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-injector from testing2.0.5-11
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-injector/30356857/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


..PHP Deprecated:  Creation of dynamic property 
ClosureInjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ClosureTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
ClosureInjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ClosureTest.php 
on line 56
...PHP Deprecated:  Creation of dynamic property 
InjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 44
PHP Deprecated:  Creation of dynamic property 
InjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 98
PHP Deprecated:  Creation of dynamic property 
InjectorFactoryTestMockFactory::$_injector is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 90
.PHP Deprecated:  Creation of dynamic property 
InjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 64
PHP Deprecated:  Creation of dynamic property 
InjectorFactoryTestMockFactory::$_injector is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 90
..PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ImplementationTest.php 
on line 6
.PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.c

Processed: Bug#1028937 marked as pending in php-horde-log

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028937 [src:php-horde-log] php-horde-log: (autopkgtest) needs update for 
php8.2: deprecation warnings on stderr
Added tag(s) pending.

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

Bug#1027403: marked as done (metalfinder: flaky autopkgtest (host dependent?): tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is not a valid FLAC file)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 17:37:16 +
with message-id 
and subject line Bug#1027403: fixed in metalfinder 2.1.6-2
has caused the Debian Bug report #1027403,
regarding metalfinder: flaky autopkgtest (host dependent?): 
tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is not a valid 
FLAC file
to be marked as done.

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

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


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

Source: metalfinder
Version: 2.1.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. The failures seem related on the host that runs 
the test. ci-worker13 is a beefy machine [1], while the other amd64 
workers are much more moderate [2]. It's also flaky on ppc64el, but 
those hosts are (or should be) all the same.


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

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

Paul

[1] https://metal.equinix.com/product/servers/m3-large/
[2] https://aws.amazon.com/ec2/instance-types/m5/

https://ci.debian.net/data/autopkgtest/testing/amd64/m/metalfinder/29786825/log.gz

=== FAILURES 
===
_ test_issue28 
_


cachedir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/cache')
musicdir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/music')
caplog = <_pytest.logging.LogCaptureFixture object at 0x7f705a5efad0>

def test_issue28(cachedir, musicdir, caplog):
"""Test metalfinder continues running if a file passed through 
get_artist()

   raises an exception"""
caplog.set_level(logging.WARNING)
for filename in ['no_header.flac', 'no_artist.flac', 
'arch_enemy.flac']:

_ = move_testfile(filename, musicdir)
artist_list = mfs.scan_wrapper(str(musicdir), str(cachedir))
assert artist_list == {'Arch Enemy'}
>   assert NO_ARTIST_ERROR in caplog.records[0].args[1]
E   assert ": 'artist'" in "'mutagen.flac.FLACNoHeaderError'>: 
'/tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is 
not a valid FLAC file"


tests/test_scan.py:170: AssertionError


https://ci.debian.net/data/autopkgtest/testing/ppc64el/m/metalfinder/29794715/log.gz

=== FAILURES 
===
_ test_issue28 
_


cachedir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/cache')
musicdir = PosixPath('/tmp/pytest-of-debci/pytest-0/test_issue280/music')
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fff8e0ec4d0>

def test_issue28(cachedir, musicdir, caplog):
"""Test metalfinder continues running if a file passed through 
get_artist()

   raises an exception"""
caplog.set_level(logging.WARNING)
for filename in ['no_header.flac', 'no_artist.flac', 
'arch_enemy.flac']:

_ = move_testfile(filename, musicdir)
artist_list = mfs.scan_wrapper(str(musicdir), str(cachedir))
assert artist_list == {'Arch Enemy'}
>   assert NO_ARTIST_ERROR in caplog.records[0].args[1]
E   assert ": 'artist'" in "'mutagen.flac.FLACNoHeaderError'>: 
'/tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' is 
not a valid FLAC file"


tests/test_scan.py:170: AssertionError



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: metalfinder
Source-Version: 2.1.6-2
Done: Louis-Philippe Véronneau 

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated metalfinder 
package)

(This message was generated automatica

Processed: owner 1029622

[Debian Bug Tracking System]

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

> owner 1029622 !
Bug #1029622 [tuxguitar-alsa] tuxguitar-alsa fails to install
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#983913: marked as done (puppet-master,puppet-master-passenger: depends on unavailable puppet-server)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 12:10:23 -0500
with message-id 
and subject line Re: puppet-master,puppet-master-passenger: depends on 
unavailable puppet-server
has caused the Debian Bug report #983913,
regarding puppet-master,puppet-master-passenger: depends on unavailable 
puppet-server
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.)


-- 
983913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-master,puppet-master-passenger
Version: 6.16.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed puppet-master*/experimental is not
installable due to an unsatisfiable dependency on puppet-server


Cheers,

Andreas
--- End Message ---
--- Begin Message ---

Version: 7.9.3-3

This is fixed in the latest upload: the puppet-master and 
puppet-master-passenger are now transitional packages for puppetserver.


-- Jérôme--- End Message ---

Bug#1025366: Note that the bug is also present in 7.0.6

[Eric Valette]

On 25/01/2023 10:36, Gianfranco Costamagna wrote:


On Sun, 4 Dec 2022 11:19:52 +0100 Eric Valette  
wrote:
Already fixed there same ways but did not report the bug hoping it 
will be soon fixed.


-- eric



Hello, please try 7.0.6
thanks


Same error, same fix. As long as the file does not chnage...

-- eric

Bug#1027403: marked as pending in metalfinder

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #1027403 in metalfinder 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/metalfinder/-/commit/7ea6232620b4e1c48a626d982c4a4a8f1cfb3904


d/patches: add 0002 to skip flaky test. (Closes: #1027403)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027403

Processed: Bug#1027403 marked as pending in metalfinder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1027403 [src:metalfinder] metalfinder: flaky autopkgtest (host 
dependent?): tmp/pytest-of-debci/pytest-0/test_issue280/music/no_header.flac' 
is not a valid FLAC file
Added tag(s) pending.

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

Bug#1026298: marked as done (datalad: FTBFS without network access)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 11:09:19 -0500
with message-id 
and subject line resolved
has caused the Debian Bug report #1026298,
regarding datalad: FTBFS without network access
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.)


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

Hi Maintainer

As can be seen on reproducible builds [1], datalad 0.17.10-1 FTBFS
without network access.  I've copied what I hope is the relevant part
of a successful build below.

Regards
Graham


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


Installed /<>
Processing dependencies for datalad==0.17.10
Searching for chardet<5.0.0,>=3.0.4
Reading https://pypi.org/simple/chardet/
/usr/lib/python3/dist-packages/pkg_resources/__init__.py:123:
PkgResourcesDeprecationWarning:  is an invalid version and will not be
supported in a future release
  warnings.warn(
Downloading 
https://files.pythonhosted.org/packages/19/c7/fa589626997dd07bd87d9269342ccb74b1720384a4d739a1872bd84fbe68/chardet-4.0.0-py2.py3-none-any.whl#sha256=f864054d66fd9118f2e67044ac8981a54775ec5b67aed0441892edb553d21da5
Best match: chardet 4.0.0
Processing chardet-4.0.0-py2.py3-none-any.whl
Installing chardet-4.0.0-py2.py3-none-any.whl to /<>/bin
Adding chardet 4.0.0 to easy-install.pth file
Installing chardetect script to bin
--- End Message ---
--- Begin Message ---
Version: 0.18.1-1

We patched away upper boundary for chardet version dependency. It was
also proposed and accepted upstream so should be included in 0.18.2

PS I am afraid we have a problem with our t...@datalad.org email since I
got no original reports... TODO

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik



signature.asc
Description: PGP signature
--- End Message ---

Bug#1029452: marked as done (python-skbio: (autopkgtest) needs update for NumPy 1.24)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 16:38:07 +
with message-id 
and subject line Bug#1029452: fixed in python-skbio 0.5.8-2
has caused the Debian Bug report #1029452,
regarding python-skbio: (autopkgtest) needs update for NumPy 1.24
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.)


-- 
1029452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-skbio
Version: 0.5.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

The autopkgtests of python-skbio fail with NumPy 1.24 [1].  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-skbio/testing/amd64/


=== FAILURES ===
___ TestLoc.test_multiindex_complicated_axis ___

self = 

def test_multiindex_complicated_axis(self):
a = RNA("UUAG", metadata={0: 0}, positional_metadata={0: [1, 2, 3, 4]})
b = RNA("UAAG", metadata={1: 0}, positional_metadata={1: [1, 2, 3, 4]})
c = RNA("UAA-", metadata={2: 0}, positional_metadata={2: [1, 2, 3, 4]})
d = RNA("UA-G", metadata={3: 0}, positional_metadata={3: [1, 2, 3, 4]})
msa = TabularMSA([a, b, c, d], metadata={'x': 'y'},
 positional_metadata={'c': ['a', 'b', 'c', 'd']},
 index=[('a', 'x', 0), ('a', 'x', 1), ('a', 'y', 2),
('b', 'x', 0)])

>   self.assertEqual(self.get(msa, (([False, True, False, True],
 'x', 0), Ellipsis)),
 TabularMSA([d], metadata={'x': 'y'},
positional_metadata={'c': ['a', 'b', 'c',
   'd']},
index=[('b', 'x', 0)]))

skbio/alignment/tests/test_tabular_msa.py:1373:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
skbio/alignment/tests/test_tabular_msa.py:1271: in get
return obj.loc[indexable]
skbio/alignment/_indexing.py:39: in __getitem__
return self._handle_both_axes(*indexable)
skbio/alignment/_indexing.py:53: in _handle_both_axes
r = self._slice_on_first_axis(self._obj, seq_index)
skbio/alignment/_indexing.py:77: in _slice_on_first_axis
return self._slice_sequences(obj, indexable)
skbio/alignment/_indexing.py:202: in _slice_sequences
self._assert_bool_vector_right_size(indexable, axis=0)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
indexable = ([False, True, False, True], 'x', 0), axis = 0

def _assert_bool_vector_right_size(self, indexable, axis):
if isinstance(indexable, np.ndarray):
pass
elif hasattr(indexable, '__iter__'):
>   indexable = np.asarray(list(indexable))
E   ValueError: setting an array element with a sequence. The
requested array has an inhomogeneous shape after 1 dimensions. The
detected shape was (3,) + inhomogeneous part.

skbio/alignment/_indexing.py:116: ValueError
___ TestLoc.test_multiindex_complicated_axis_empty_selection ___

self = 

@unittest.skipIf(tuple(map(int, pd.__version__.split('.'))) < (1, 2, 5),
 "Old pandas will return empty frame")
def test_multiindex_complicated_axis_empty_selection(self):
a = RNA("UUAG", metadata={0: 0}, positional_metadata={0: [1, 2, 3, 4]})
b = RNA("UAAG", metadata={1: 0}, positional_metadata={1: [1, 2, 3, 4]})
c = RNA("UAA-", metadata={2: 0}, positional_metadata={2: [1, 2, 3, 4]})
d = RNA("UA-G", metadata={3: 0}, positional_metadata={3: [1, 2, 3, 4]})
msa = TabularMSA([a, b, c, d], metadata={'x': 'y'},
 positional_metadata={'c': ['a', 'b', 'c', 'd']},
 index=[('a', 'x', 0), ('a', 'x', 1), ('a', 'y', 2),
('b', 'x', 0)])
# Pandas will KeyError when the intersection is empty
# change appears to have happened in:
# https://github.com/pandas-dev/pandas/pull/42245
# but this was not bisected to confirm
with self.assertRaises(KeyError):
>   self.get(msa, (([False, True, False, True], 'x', 2), Ellipsis))

skbio/alignment/tests/test_tabular_msa.py:1396:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
skbio/alignment/tests/test_tabular_msa.py:1271: in get
return

Bug#1027219: marked as done (python-skbio: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 16:38:07 +
with message-id 
and subject line Bug#1029452: fixed in python-skbio 0.5.8-2
has caused the Debian Bug report #1029452,
regarding python-skbio: autopkgtest fail with numpy/1.24.1
to be marked as done.

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

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


-- 
1029452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-skbio
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: python-skbio
Source-Version: 0.5.8-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-skbio 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, 25 Jan 2023 16:31:24 +0100
Source: python-skbio
Architecture: source
Version: 0.5.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1029452
Changes:
 python-skbio (0.5.8-2) unstable; urgency=medium
 .
   [ Michael R. Crusoe ]
   * d/control,d/patches/local_inventory: python-numpy-doc is no longer built,
 so remove the build-dep and reference
 .
   [ Nilesh Patra ]
   * Adapt to numpy 1.24
 Closes: #1029452
Checksums-Sha1:
 9aba0b4fbaef5db0d5e5f2de0b8ad4b5f0ad276d 2742 python-skbio_0.5.8-2.dsc
 009916c4f617002bfcce2642427578fb35b5574d 10024 
python-skbio_0.5.8-2.debian.tar.xz
 b80c075581730ceb1b2cc16a8d20108a24dc1e9b 21190 
python-skbio_0.5.8-2_source.buildinfo
Checksums-Sha256:
 603781c38f1993a68945785b239b4fd8eef6082fa087fe45ec4cf85ef7de99ae 2742 
python-skbio_0.5.8-2.dsc
 753a1253c110a2801f8f2da6820cb30d0e660efe36ab3f4dff068934504d09a2 10024 
python-skbio_0.5.8-2.debian.tar.xz
 3e98990b45ec1d57c7628a927bf96007950bbd03492b57e9dd0d65018b58928c 21190 
python-skbio_0.5.8-2_source.buildinfo
Files:
 14aaae24e3d2dd09b5e187626b0e6cdf 2742 python optional python-skbio_0.5.8-2.dsc
 4488353c1a9f22f0151cb0e64f6daa86 10024 python optional 
python-skbio_0.5.8-2.debian.tar.xz
 fb57435559a5adb3e58bc0503797c159 21190 python optional 
python-skbio_0.5.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPRUwAOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHvwxAAgST3OLz38shvl9pUpGlxFjBfL/2+xWY7Sj5k
3pdBm9MLS31o+GZaMbJO+Ji+RsAPY18WwL3uMT5Iexf8/2iwhMlvysnts4s5Wz8o
UH7R+je3XU7EYP7Ws3B4fnmjuYNNn3NT0to88rnHrkBS0h+wnn2/8TWLoFNah9Py
WWnDRhmDyDbjDJJwWzvps/8kYCzNIG7/CANN6IEXlpkbrqfM3pT5EAM4G5aYykcr
c8Q3ZNopk3cBU1IQFknnJU82EYPQBlghS4YdEpu1NXT2qGJQI0VO37eI07+edPm+
26feCyPmTGx92ofByV1lRx/Is983Pw2KHAk+HkJuS4HukYKXu/D6RlbTRMbh1xzd
ACtm4dwXc6dE2InDwJVTjzF5cjQQe48ceLm4JHpTby0txKrz+Ey7A3KoEfajILD5
ox+I5CK5PgP/G520F79+ExG+jOWuSl2o3ChIXzjKIHz8g9/3hQKhSyNs3WUDTyTW

Bug#1029626: pagure fails to purge when adduser is not installed

[Adrian Bunk]

Package: pagure
Version: 5.11.3+dfsg-1
Severity: serious

https://piuparts.debian.org/sid/fail/pagure_5.11.3+dfsg-2.log

...
  Purging configuration files for pagure (5.11.3+dfsg-2) ...
  /var/lib/dpkg/info/pagure.postrm: 22: deluser: not found
  dpkg: error processing package pagure (--purge):
   installed pagure package post-removal script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   pagure
0m58.6s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpemwrio1i', 'dpkg', '--purge', 'pagure']
  (Reading database ... 8052 files and directories currently installed.)
  Purging configuration files for pagure (5.11.3+dfsg-2) ...
  /var/lib/dpkg/info/pagure.postrm: 22: deluser: not found
  dpkg: error processing package pagure (--purge):
   installed pagure package post-removal script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   pagure



https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#summary-of-ways-maintainer-scripts-are-called

The postrm script is called after the package’s files have been removed or 
replaced. The package whose postrm is being called may have previously been 
deconfigured and only be “Unpacked”, at which point subsequent package changes 
do not consider its dependencies. Therefore, all postrm actions must only rely 
on essential packages and must gracefully skip any actions that require the 
package’s dependencies if those dependencies are unavailable.

Bug#1029625: python3-txi2p-tahoe: piuparts error

[Adrian Bunk]

Package: python3-txi2p-tahoe
Version: 0.3.7-2
Severity: serious
X-Debbugs-Cc: Andrius Merkys 

https://piuparts.debian.org/sid/fail/python3-txi2p-tahoe_0.3.7-2.log

...
0m35.7s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/lib/python3/dist-packages/twisted/plugins/dropin.cache
...

Bug#1029624: gvmd-common fails to install

[Adrian Bunk]

Package: gvmd-common
Version: 22.4.1-1
Severity: serious

https://piuparts.debian.org/sid/fail/gvmd-common_22.4.1-1.log

...
Setting up gvmd-common (22.4.1-1) ...
  find: '/var/lib/gvm/gvmd': No such file or directory
  dpkg: error processing package gvmd-common (--configure):
   installed gvmd-common package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.36-8) ...
  Errors were encountered while processing:
   gvmd-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#1029622: tuxguitar-alsa fails to install

[Adrian Bunk]

Package: tuxguitar-alsa
Version: 1.5.6+dfsg1-4
Severity: serious
X-Debbugs-Cc: tony mancill 

https://piuparts.debian.org/sid/fail/tuxguitar-alsa_1.5.6+dfsg1-4.log

...
  Preparing to unpack .../136-tuxguitar-alsa_1.5.6+dfsg1-4_amd64.deb ...
  Unpacking tuxguitar-alsa (1.5.6+dfsg1-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-EyzlMb/136-tuxguitar-alsa_1.5.6+dfsg1-4_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/maven-repo/org/herac/tuxguitar/tuxguitar-pom/1.5.6/tuxguitar-pom-1.5.6.pom',
 which is also in package tuxguitar 1.5.6+dfsg1-4
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-EyzlMb/136-tuxguitar-alsa_1.5.6+dfsg1-4_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#1029621: falkon fails to install

[Adrian Bunk]

Package: falkon
Version: 22.12.1-1
Severity: serious

https://piuparts.debian.org/sid/fail/falkon_22.12.1-1.log

...
Setting up falkon (22.12.1-1) ...
  update-alternatives: using /usr/bin/falkon to provide /usr/bin/x-www-browser 
(x-www-browser) in auto mode
  mkdir: cannot create directory '/usr/share/qt5/qtwebengine_dictionaries': 
File exists
  dpkg: error processing package falkon (--configure):
   installed falkon package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.36-8) ...
  Errors were encountered while processing:
   falkon
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#1029550: marked as done (scipy: (s390x autopkgtest) needs update for NumPy 1.24)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2023 14:51:26 +
with message-id 
and subject line Bug#1029550: fixed in scipy 1.8.1-22
has caused the Debian Bug report #1029550,
regarding scipy: (s390x autopkgtest) needs update for NumPy 1.24
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.)


-- 
1029550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scipy
Version: 1.8.1-21
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

The autopkgtests of scipy fail with NumPy 1.24 on s390x [1].  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/s/scipy/testing/s390x/


=== FAILURES ===
___ test_atol[bicg] 
/usr/lib/python3/dist-packages/scipy/sparse/linalg/_isolve/tests/test_iterative.py:422:
in test_atol
assert_(err <= max(atol, atol2))
E   AssertionError
A  = array([[14.31948217,  3.3445992 ,  3.22423163,
3.66544887,  2.50463135,
 4.00888703,  2.25486222,  2.03568917...3162,  2.82956812,
3.1425076 ,  2.17335779,
 3.2446288 ,  2.1821021 ,  2.22427957,  3.32031818, 13.42463446]])
M  = array([[ 4.28038557e-06, -1.74616643e-06, -1.99641947e-06,
-1.90276202e-06,  1.64630749e-06,  5.72226274e-07,
... 3.21342987e-06, -2.58609835e-06,
 5.90349817e-06, -3.87886046e-06, -3.52856621e-06,
 8.23227307e-06]])
M0 = array([[ 4.28038557, -1.74616643, -1.99641947,
-1.90276202,  1.64630749,
 0.57222627,  2.76279583, -1.83101351...4479, -0.1760489 ,
-3.53709722,  3.21342987,
-2.58609835,  5.90349817, -3.87886046, -3.52856621,  8.23227307]])
Ms = [None, array([[ 4.28038557e-06, -1.74616643e-06,
-1.99641947e-06,
-1.90276202e-06,  1.64630749e-06,  5.7222627...0526, -2586098.34883972,
 5903498.16585825, -3878860.45678975, -3528566.20527011,
 8232273.07488767]])]
atol   = 1e-10
atol2  = 0.0
b  = array([767.11662838, 708.11536198, 796.86718373,
557.76082843,
   965.83653199, 147.15689989,  29.64700054, 593.89349262,
   114.06569874, 950.80985008])
b_norm = 2064.248986245918
err= 1.0001923322085594e-10
info   = 0
residual   = array([ 5.61612978e-11,  3.16049409e-11,
3.50155460e-11, -5.11590770e-12,
2.50111043e-12,  1.06581410e-11, -8.84625706e-13, -3.93356459e-11,
   -1.50635060e-12, -5.41149348e-11])
solver = 
tol= 0.0
tols   = array([0.e+00, 1.e-10, 1.e-08, 1.e-06, 1.e-04,
1.e-02, 1.e+00, 1.e+02,
  inf])
x  = array([ 28.6604403 ,  29.98361995,  37.7931594 ,
 9.81468974,
63.06966912, -30.30519745, -21.60229055,  28.36084453,
   -30.2321986 ,  50.7269506 ])
--- End Message ---
--- Begin Message ---
Source: scipy
Source-Version: 1.8.1-22
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated scipy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2023 15:32:10 +0100
Source: scipy
Architecture: source
Version: 1.8.1-22
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Drew Parsons 
Closes: 1029550
Changes:
 scipy (1.8.1-22) unstable; urgency=medium
 .
   * Team upload.
   * skip test_atol[bicg] on s390x. Closes: #1029550.
Checksums-Sha1:
 62e833dfc95d4055a9bdd83425a4719d61bbea68 2842 scipy_1.8.1-22.dsc
 b7bc409df622f0f756ff1968e69a5c732a496739 37656 scipy_1.8.1-22.debian.tar.xz
 8deb77ee05a3bb360b996e4bc5c25bd944a76fb9 10420 scipy_1.8.1-22_source.buildinfo
Checksums-Sha256:
 7b5c1b5319bb7d2bc422d52214b3aa494ed07cf4e5ba37d6b13877dbbea37015 2842 
scipy_1.8.1-22.dsc
 387794d867b5efffc7bb4a6caff38ef957bf57e104d728f

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Sebastian Reichel]

Hi Martin,

On Tue, Jan 24, 2023 at 10:50:52PM +, Martin wrote:
> Hi Sebastian,
> 
> I wonder, if I should upload libproxy with your github patch¹ to
> experimental. Then people affected (or not affected) by the bug can test
> easily. Or you may upload, of course! :-)
> 
> Cheers
> 
> ¹ https://github.com/libproxy/libproxy/issues/199#issuecomment-1401124997

sure, feel free to upload it to experimental. FWIW I do not
understand the root cause of this issue. I'm a bit worried,
that the patch masks a security relevant bug. It would be great
if somebody with better C++ knowledge can look into this.

The bug seems quite strange considering the segmentation fault is
happening due to the destruction of an empty vector from the standard
library and only in combination with glib-networking.

FWIW long term the problem will be solved by glib-networking
removing the libproxy dependency:

https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/205

Greetings,

-- Sebastian


signature.asc
Description: PGP signature