Bug#1039871: python-xarray: FTBFS (PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent')

[Sebastiaan Couwenberg]

Control: tags -1 patch

The attached patch resolves the FTBFS by nbsphinx_allow_errors = False 
from doc/conf.py


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1diff -Nru python-xarray-2023.06.0/debian/changelog 
python-xarray-2023.06.0/debian/changelog
--- python-xarray-2023.06.0/debian/changelog2023-06-27 15:47:04.0 
+0200
+++ python-xarray-2023.06.0/debian/changelog2023-06-29 06:58:55.0 
+0200
@@ -1,3 +1,11 @@
+python-xarray (2023.06.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix FTBFS.
+(closes: #1039871)
+
+ -- Bas Couwenberg   Thu, 29 Jun 2023 06:58:55 +0200
+
 python-xarray (2023.06.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-xarray-2023.06.0/debian/patches/series 
python-xarray-2023.06.0/debian/patches/series
--- python-xarray-2023.06.0/debian/patches/series   2023-06-27 
15:47:04.0 +0200
+++ python-xarray-2023.06.0/debian/patches/series   2023-06-29 
06:55:24.0 +0200
@@ -12,3 +12,4 @@
 xfail-pad-constant.patch
 no-sphinx-design.patch
 xfail-on-random-patch
+xarray_tutorial_data.patch
diff -Nru python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch 
python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch
--- python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch   
1970-01-01 01:00:00.0 +0100
+++ python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch   
2023-06-29 06:58:55.0 +0200
@@ -0,0 +1,16 @@
+Description: Fix FBTBFS, docs write to $HOME.
+Author: Bas Couwenberg 
+Bug-Debian: https://bugs.debian.org/1039871
+Forwarded: not-needed
+
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -63,8 +63,6 @@ except ImportError:
+ ]
+ )
+ 
+-nbsphinx_allow_errors = False
+-
+ # -- General configuration 
+ 
+ # If your documentation needs a minimal Sphinx version, state it here.

Bug#1039875: transition: gnustep-performance

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-06-29 09:23:03 +0300, Yavor Doganov wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: gnustep-performa...@packages.debian.org
> Control: affects -1 + src:gnustep-performance
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-gnustep-performance.html
> 
> We (GNUstep team) would like to update gnustep-performance
> (libperformance0.5 -> 0.6).  The new version is sitting in
> experimental and the sole reverse dependency gnustep-sqlclient builds
> fine against it.

Please go ahead

Cheers
-- 
Sebastian Ramacher

Bug#1039875: transition: gnustep-performance

[Yavor Doganov]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: gnustep-performa...@packages.debian.org
Control: affects -1 + src:gnustep-performance
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-gnustep-performance.html

We (GNUstep team) would like to update gnustep-performance
(libperformance0.5 -> 0.6).  The new version is sitting in
experimental and the sole reverse dependency gnustep-sqlclient builds
fine against it.

Thanks.

Bug#1039874: ITP: python-ocspbuilder -- library for generating OCSP requests and responses

[Michael Fladischer]

Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-ocspbuilder
  Version : 0.10.2
  Upstream Contact: Will Bond 
* URL : https://github.com/wbond/ocspbuilder
* License : Expat
  Programming Lang: Python
  Description : library for generating OCSP requests and responses

 ocspbuilder is a Python library for constructing OCSP requests and responses. 
It
 provides a high-level interface with knowledge of RFC 6960 to produce, valid,
 correct OCSP messages without terrible APIs or hunting through RFCs.

I intend to maintain this as part of the DPT.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmSdH8ARHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90Wq6Egf/TdyqNT9AXj6LVJODRroBfHdV+r4MAXxQ
EdkLYqPTH/g5MRhjeSI+/KIppXMD3+7PIqB60jsZzFcISU1it9ZEEfa4U3DN9KCt
xP6vQ5COIm2zKPwxMH5FA9EYqX8QG2Y81FNZYYF0+c6OqX8djHR2KZZJcSuwT3Nq
87R9lPwzprGVyL7TfAhp5in7j96fj6NdXDyapNb1Lty2FLN9J+61GHHaVVqae3tz
siqcsXRVOmtN+gXMIcnNuE89otjwzY5S8FqTusb0RTVzrbYulGawVCDYOyfFhXfh
6f+6b2mlijNcRlKwa6YVYWuz23m2go/fqRziYe3ZV1Q/6KCIVRcriw==
=Lihu
-END PGP SIGNATURE-

Bug#1039873: pam-auth-update --disable does not work

[duck]

Package: libpam-runtime
Severity: normal
Version: 1.5.2-6


Quack,

Thanks for adding the feature in #1004000 but it unfortunately does not 
work.


I don't recall if I tested the feature extensively but I updated my 
Ansible rules and it is ineffective. After switching a machine to 
bookworm I still get the module I want disabled around (it is reenabled 
during upgrade) and that breaks authentication.


I then started to check manually:
# grep sss /etc/pam.d/*
/etc/pam.d/common-account:account	[default=bad success=ok 
user_unknown=ignore]	pam_sss.so
/etc/pam.d/common-auth:auth	[success=2 default=ignore]	pam_sss.so 
use_first_pass

/etc/pam.d/common-password:password sufficient  
pam_sss.so use_authtok
/etc/pam.d/common-session:session   optional
pam_sss.so
# pam-auth-update --disable sss
=> same result
# pam-auth-update --force --disable sss
=> same result

If I use pam-auth-update interactively and uncheck sss then it works.

I then used `pam-auth-update --enable sss` and sss reappeared in the 
config and tried again --disable but to no avail.


Could you please have a look?
Regards.
\_o<

--
Marc Dequènes

Bug#1039510: mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?

[Nilesh Patra]

Dirk, Andreas,

On Wed, Jun 28, 2023 at 10:49:24AM +0200, Andreas Tille wrote:
> Yes, so I keep on updating r-cran- packages after freeze and save my
> time to repeat myself.

I probably should not be the one to add fuel to the fire, but allow me
to present some statistics.
The debian R team team currently has 1151 packages, and at the time of
writing this mail, there are only 2-3 volunteers who do the job of
maintaining this chunk of work, which means each volunteer is
maintaining at least ~384 packages just in the R team (and I'm speaking
this in the context of team uploads, and not according to the name
mentioned in uploaders field). Here's upload stats[2].

In addition to that, the said volunteers are also maintaining packages
in other debian teams. For instance, my packages span across ~10-12
different teams, and same goes for Andreas. On top of that, there's also
RFP requests from people and we have to constantly work on packaging new
and relevant software for debian.

@Dirk, you, on the other hand have most of the packages you maintain out
of maintainer teams, and as far as I can see, you currently have 179
packages[3], and you mostly upload only those packages, so it is likely easier
to bring them to cran latest at most times. I'm not trying to
draw any comparison, but only stating facts.

As you may see, the load that's on each volunteer is quite a lot, and it
gets humanely impossible to keep all those number of packages into an
updated state. We'd love to be at versions that CRAN (or bioconductor)
is at currently, but there simply aren't enough cycles most of the
times.

I'd also like to point out that despite the constraints,
during the past year, the number of stale packages were
consistently less than '30' which is ~CRAN latest.

Now is an anomally because freeze just ended, and there's a huge delta.

[1]: 
https://qa.debian.org/developer.php?email=r-pkg-team%40alioth-lists.debian.net
[2]: http://blends.debian.net/liststats/uploaders_r-pkg.png
[3]: https://qa.debian.org/developer.php?login=edd&comaint=yes

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1039872: Improve firmware package inclusion

[Steve McIntyre]

Package: debian-installer
Severity: normal

As mentioned in #1038440 and elsewhere, some of our media builds are
too big and this is mostly due to inclusion of firmware packages. Some
growth is not unexpected, but we're including firmware packages that
are not useful, e.g.:

 * nvidia firmware packages from the nvidia-graphics-drivers* source
   package are not useful without non-free drivers that we're not
   shipping in our images
   (https://lists.debian.org/debian-boot/2023/01/msg00157.html)
 * we're currently including raspi-firmware for all arches, while it's
   only useful for arm*

I think we could really do with some extra metadata for the firmware
packages to help us determine what to include on media. Maybe:

 * "this firmware works/does not work with free drivers in Debian"
 * "this is generic firmware, useful for all arches"
 * "this firmware is useful for arches <> only"

What other information would be helpful?

In the meantime, I'm about to add support for firmware-ignore list(s)
in debian-cd.

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

Kernel: Linux 5.10.0-22-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1039871: python-xarray: FTBFS (PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent')

[Bas Couwenberg]

Source: python-xarray
Version: 2023.06.0-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

Dear Maintainer,

Your package FTBFS on the buildds:

 Notebook error:
 CellExecutionError in examples/ERA5-GRIB-example.ipynb:
 --
 ds = xr.tutorial.load_dataset("era5-2mt-2019-03-uk.grib", engine="cfgrib")
 --
 
 
[0;31m---[0m
 [0;31mPermissionError[0m   Traceback (most recent call 
last)
 File [0;32m/usr/lib/python3/dist-packages/pooch/utils.py:258[0m, in 
[0;36mmake_local_storage[0;34m(path, env)[0m
 [1;32m255[0m [38;5;66;03m# When running in parallel, it's possible 
that multiple jobs will[39;00m
 [1;32m256[0m [38;5;66;03m# try to create the path at the same time. 
Use exist_ok to avoid[39;00m
 [1;32m257[0m [38;5;66;03m# raising an error.[39;00m
 [0;32m--> 258[0m 
[43mos[49m[38;5;241;43m.[39;49m[43mmakedirs[49m[43m([49m[43mpath[49m[43m,[49m[43m
 [49m[43mexist_ok[49m[38;5;241;43m=[39;49m[38;5;28;43;01mTrue[39;49;00m[43m)[49m
 [1;32m259[0m [38;5;28;01melse[39;00m:
 
 File [0;32m:215[0m, in [0;36mmakedirs[0;34m(name, mode, exist_ok)[0m
 
 File [0;32m:215[0m, in [0;36mmakedirs[0;34m(name, mode, exist_ok)[0m
 
 File [0;32m:225[0m, in [0;36mmakedirs[0;34m(name, mode, exist_ok)[0m
 
 [0;31mPermissionError[0m: [Errno 13] Permission denied: '/sbuild-nonexistent'
 
 The above exception was the direct cause of the following exception:
 
 [0;31mPermissionError[0m   Traceback (most recent call 
last)
 Cell [0;32mIn [2], line 1[0m
 [0;32m> 1[0m ds [38;5;241m=[39m 
[43mxr[49m[38;5;241;43m.[39;49m[43mtutorial[49m[38;5;241;43m.[39;49m[43mload_dataset[49m[43m([49m[38;5;124;43m"[39;49m[38;5;124;43mera5-2mt-2019-03-uk.grib[39;49m[38;5;124;43m"[39;49m[43m,[49m[43m
 
[49m[43mengine[49m[38;5;241;43m=[39;49m[38;5;124;43m"[39;49m[38;5;124;43mcfgrib[39;49m[38;5;124;43m"[39;49m[43m)[49m
 
 File [0;32m/<>/xarray/tutorial.py:206[0m, in 
[0;36mload_dataset[0;34m(*args, **kwargs)[0m
 [1;32m169[0m [38;5;28;01mdef[39;00m 
[38;5;21mload_dataset[39m([38;5;241m*[39margs, 
[38;5;241m*[39m[38;5;241m*[39mkwargs) [38;5;241m-[39m[38;5;241m>[39m Dataset:
 [1;32m170[0m [38;5;250m[39m[38;5;124;03m"""[39;00m
 [1;32m171[0m [38;5;124;03mOpen, load into memory, and close a dataset 
from the online repository[39;00m
 [1;32m172[0m [38;5;124;03m(requires internet).[39;00m
 [0;32m   (...)[0m
 [1;32m204[0m [38;5;124;03mload_dataset[39;00m
 [1;32m205[0m [38;5;124;03m"""[39;00m
 [0;32m--> 206[0m [38;5;28;01mwith[39;00m 
[43mopen_dataset[49m[43m([49m[38;5;241;43m*[39;49m[43margs[49m[43m,[49m[43m 
[49m[38;5;241;43m*[39;49m[38;5;241;43m*[39;49m[43mkwargs[49m[43m)[49m 
[38;5;28;01mas[39;00m ds:
 [1;32m207[0m [38;5;28;01mreturn[39;00m ds[38;5;241m.[39mload()
 
 File [0;32m/<>/xarray/tutorial.py:160[0m, in 
[0;36mopen_dataset[0;34m(name, cache, cache_dir, engine, **kws)[0m
 [1;32m157[0m url [38;5;241m=[39m 
[38;5;124mf[39m[38;5;124m"[39m[38;5;132;01m{[39;00mbase_url[38;5;132;01m}[39;00m[38;5;124m/raw/[39m[38;5;132;01m{[39;00mversion[38;5;132;01m}[39;00m[38;5;124m/[39m[38;5;132;01m{[39;00mpath[38;5;241m.[39mname[38;5;132;01m}[39;00m[38;5;124m"[39m
 [1;32m159[0m [38;5;66;03m# retrieve the file[39;00m
 [0;32m--> 160[0m filepath [38;5;241m=[39m 
[43mpooch[49m[38;5;241;43m.[39;49m[43mretrieve[49m[43m([49m[43murl[49m[38;5;241;43m=[39;49m[43murl[49m[43m,[49m[43m
 
[49m[43mknown_hash[49m[38;5;241;43m=[39;49m[38;5;28;43;01mNone[39;49;00m[43m,[49m[43m
 [49m[43mpath[49m[38;5;241;43m=[39;49m[43mcache_dir[49m[43m)[49m
 [1;32m161[0m ds [38;5;241m=[39m _open_dataset(filepath, 
engine[38;5;241m=[39mengine, [38;5;241m*[39m[38;5;241m*[39mkws)
 [1;32m162[0m [38;5;28;01mif[39;00m [38;5;129;01mnot[39;00m cache:
 
 File [0;32m/usr/lib/python3/dist-packages/pooch/core.py:223[0m, in 
[0;36mretrieve[0;34m(url, known_hash, fname, path, processor, downloader, 
progressbar)[0m
 [1;32m220[0m [38;5;66;03m# Create the local data directory if it doesn't 
already exist and make the[39;00m
 [1;32m221[0m [38;5;66;03m# path absolute.[39;00m
 [1;32m222[0m path [38;5;241m=[39m cache_location(path, 
env[38;5;241m=[39m[38;5;28;01mNone[39;00m, 
version[38;5;241m=[39m[38;5;28;01mNone[39;00m)
 [0;32m--> 223[0m [43mmake_local_storage[49m[43m([49m[43mpath[49m[43m)[49m
 [1;32m225[0m full_path [38;5;241m=[39m path[38;5;241m.[39mresolve() 
[38;5;241m/[39m fname
 [1;32m226[0m action, verb [38;5;241m=[39m download_action(full_path, 
known_hash)
 
 File [0;32m/usr/lib/python3/dist-packages/pooch/utils.py:273[0m, in 
[0;36mmake_local_storage[0;34m(path, env)[0m
 [1;32m269[0m [38;5;28;01mif[39;00m env [38;5;129;01mis[39;00m 
[38;5;129;01mnot[39;00m [38;5;28;01mNone[39;00m:
 [1;32m270[0m message[38;5;241m.[39mappend(
 [1;32m271[0m [38;5;124mf[39m[38;5;124m"[39m[38;5;124mUse 
environment variable 
[39m[38;5;124m'[39

Bug#955620: cloud-init - debian/rules clean fails from git repo

[Noah Meyerhans]

Control: tags -1 + patch

Proposed fix is at 
https://salsa.debian.org/cloud-team/cloud-init/-/merge_requests/9

Bug#1039743: phpunit 10 transition [Was: Bug#1039743: christianriesen-base32: FTBFS with phpunit 10: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2]

[David Prévot]

Hi,

Le 29/06/2023 à 00:24, Athos Ribeiro a écrit :

On Wed, Jun 28, 2023 at 10:31:53PM +0100, Adam D. Barratt wrote:

On Wed, 2023-06-28 at 17:57 -0300, Athos Ribeiro wrote:

[…]

Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

[…]

I've picked up an arbitrary bug from the set to reply to here.


Thank you for the follow up.


[…] Should I go ahead and re-set the severity for those bugs?


I doubt we’ll manage to handle this transition within a month. Having 
packages being autoremoved from testing before the transition is ready 
doesn’t help. So yes, please demote the severity to important. Given the 
proper usertags you set, it should be easy to handle them in mass.


[…]

I wonder if the processes you are describing here is documented
somewhere (severities, when to mass file bugs for transitions, and
transition timing expectations after those are filed) so I can avoid
generating any unnecessary noise in the future.


https://wiki.debian.org/Teams/ReleaseTeam/Transitions#How_transitions_work_in_general

Of course, our case is a bit specific (the RT can’t BinNMU arch:all 
packages), but this gives an idea. We’re around stage 5 according to 
this check list. Ideally, the recent bugs should have been set as 
blocking the (not yet existant) transition bug, but again, given the 
existing usertags, it sourd be easy to handle this in mass soon.


Regards

taffit



OpenPGP_signature
Description: OpenPGP digital signature

Bug#955733: cloud-init does not set locale specified in user data

[Noah Meyerhans]

On Sat, Apr 04, 2020 at 11:49:42AM +0100, Nick Holloway wrote:
> Package: cloud-init
> Version: 18.3-6

Confirmed that the behavior as described is still an issue in cloud-init
22.4.2-1 in bookworm.

> The command "locale-gen" does not accept a locale as an argument, but
> only generates the locales listed in "/etc/locale.gen".  So the locale
> requested does not get generated, and causes the subsequent failure when
> setting locale.
> 
> 2020-04-04 10:00:43,196 - util.py[DEBUG]: Running command 
> ['update-locale', '--locale-file=/etc/default/locale', 'LANG=en_GB.UTF-8'] 
> with allowed return codes [0] (shell=False, capture=False)
> 

I think that each of the components is working correct if viewed in
isolation, but the end result is not what you expect.  If we document
that you must first populate /etc/locale.gen with the desired list of
available locales, that may be sufficient.  For example, the following
sets the desired locale:

admin@ip-10-0-3-7:~$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
write_files:
- path: /etc/locale.gen
  content: ZW5fR0IuVVRGLTggVVRGLTgK
  encoding: base64
locale: en_GB.UTF-8
admin@ip-10-0-3-7:~$ echo "ZW5fR0IuVVRGLTggVVRGLTgK" | openssl base64 -d
en_GB.UTF-8 UTF-8

Do Ubuntu systems list all known locales in /etc/locale.gen?  That would
make the locale module work without additional configuration, but seems
unnecessarily expensive.

noah

Bug#1039869: lintian: extend Vcs-* checks to upstream Repository/Repository-Browser URLs too

[Paul Wise]

Package: lintian
Version: 2.116.3
Severity: wishlist

I noticed that a few packages use ssh:// URLs for the Repository field
in the upstream metadata file. These are suboptimal since the user
might not have an account or might not be the person in the URL when a
username is hardcoded. The vcs-field-uses-not-recommended-uri-format
tag covers this problem for the Debian Vcs-* fields, but lintian does
not appear to check the upstream Repository/Repository-Browse fields.

https://codesearch.debian.net/search?q=path%3A%2Fdebian%2Fupstream+Repository.*ssh%3A&literal=0

In addition there are some packages with insecure URLs to git repos and
the vcs-field-uses-insecure-uri tag does not flag those packages yet.

https://codesearch.debian.net/search?q=path%3A%2Fdebian%2Fupstream+Repository.*git%3A&literal=0

I think it would be a good idea to extend all of the Vcs-* field checks
to also check the upstream Repository/Repository-Browse fields too.

https://wiki.debian.org/UpstreamMetadata

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1038876: ntpq: missing empty lines between command outputs

[Richard Laager]

I forwarded this upstream. I'm not sure how much upstream will care. But 
hopefully I can get a firm answer either way.


--
Richard

Bug#1039857: podman crashes my systemd-managed sway session on exit

[Antoine Beaupré]

On 2023-06-28 17:42:18, Antoine Beaupre wrote:

[...]

> The real fix here would be for Sway to send something to sd-daemon. Of
> course, the easiest way to do this would be to do a clever call to
> sd_notify() just at the right place in the Sway source code, but
> there's little chance such a patch would be merged upstream...
>
> I looked at the code, and the actual sd_notify() call is not *that*
> complex. It opens a UNIX socket and shoves a message in there,
> probably just READY=1. Surely Sway could figure out how to write to a
> socket on its own?
>
> Hell, it could even just vendor this stupid piece of code here:
>
> https://sources.debian.org/src/systemd/253-4/src/libsystemd/sd-daemon/sd-daemon.c/#L453-L602
>
> Anyway, I don't mean to troll here, but this was a really complicated
> bug to figure out and to fix for me (thanks #debian-systemd folks!),
> so I figured I would at *least* document it here somehow.
>
> The best case scenario for me is that sway gets sd_notify support. A
> working compromise could be an update to the README.Debian file or
> even better a sample sway config that has the right knobs.

Actually, it looks like Sway *already* links against libsystemd or at
least *can* link against it, if I parse the meson build files right. So
we could "just" have a patch that does indeed call sd_notify properly
without adding anything new to the dependency tree.

anarcat@angela:sway-1.7$ rg -i systemd
debian/sway.install
10:debian/config.d/50-systemd-user.conf /etc/sway/config.d/

debian/control
20:   libsystemd-dev (>= 239) | libelogind-dev (>= 239),

debian/changelog
97:  * Add a config file to set environment variables in systemd
208:   - Make build-deps libsystemd-dev and libelogind-dev alternatives
256:Thus explicitly listing wayland-protocols and libsystemd as

meson_options.txt
11:option('sd-bus-provider', type: 'combo', choices: ['auto', 'libsystemd', 
'libelogind', 'basu'], value: 'auto', description: 'Provider of the sd-bus 
library')

meson.build
95: sdbus = dependency(['libsystemd', 'libelogind'],
116:conf_data.set10('HAVE_LIBSYSTEMD', sdbus.found() and sdbus.name() == 
'libsystemd')

debian/config.d/50-systemd-user.conf
4:# and 
https://github.com/systemd/systemd/blob/dfc637d0ff756889e8e5b7cb4ec991eb06069aa1/xorg/50-systemd-user.sh
9:dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY 
SWAYSOCK

include/swaybar/tray/tray.h
5:#if HAVE_LIBSYSTEMD
6:#include 

-- 
What this country needs is more unemployed politicians.
- Angela Davis

Bug#1038115: transition: gdal

[Sebastiaan Couwenberg]

On 6/23/23 10:45, Sebastiaan Couwenberg wrote:

On 6/21/23 12:31, Sebastiaan Couwenberg wrote:

On 6/20/23 23:49, Sebastian Ramacher wrote:

On 2023-06-15 17:15:27 +0200, Bas Couwenberg wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: g...@packages.debian.org
Control: affects -1 + src:gdal
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-gdal.html

Control: block -1 by 1030129 998833 1037920 984398 1037976

For the Debian GIS team I'd like to transition to GDAL 3.7.0.


Please go ahead.


gdal (3.7.0+dfsg-1) has been uploaded to unstable and is now built & 
installed on all release architectures.


Please also binNMU mysql-workbench which builds successfully now that 
the ca-certificates-java workaround is in unstable.


mysql-workbench still needs to be rebuilt in unstable.

r-base is blocking testing migration of 
r-cran-rgdal/r-cran-sf/r-cran-terra which in turn prevents the removal 
of libgdal32 from testing.


Kind Regards,

Bas

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

Bug#1029456: RFP: veracrypt -- Cross-platform on-the-fly encryption.

[Blair Noctis]

Control: owner -1 !
Control: retitle -1 ITP: veracrypt -- Cross-platform on-the-fly disk encryption
with strong security based on TrueCrypt
thanks

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038315: lxd: AppArmor profile violations cause PrivateNetwork=yes services in the container fail to start

[Bagas Sanjaya]

On 6/24/23 22:19, Mathias Gibbens wrote:
>> systemd-hostnamed.service is probably also affected, but in my case I
>> paved over the issue by setting PrivateNetwork=no in an override.
> 
>   For the moment setting PrivateNetwork=no for affected services is
> probably a better approach than totally removing the container's
> apparmor profile.
> 

Hi Mathias, sorry for late reply.

Indeed, overriding affected services with PrivateNetwork=no works.
Thanks for the better workaround!

-- 
An old man doll... just what I always wanted! - Clara

Bug#1039868: logrotate: logrotate -s /dev/null replaces /dev/null with a regular file

[Arnaud Rebillout]

Package: logrotate
Version: 3.18.0-2+deb11u1
Severity: normal
User: de...@kali.org
Usertags: origin-kali

Dear Maintainer,

this bug affects Debian bullseye (ie. logrotate 3.18). It was fixed
upstream in version 3.19.

The command 'logrotate --state /dev/null ...' happily replaces the
device /dev/null with a regular file, breaking the system badly, in a
non-obvious way.

Steps to reproduce:

  # ls -l /dev/null
  crw-rw-rw- 1 root root 1, 3 Jun 29 01:43 /dev/null
  # logrotate --state /dev/null /etc/logrotate.conf
  # ls -l /dev/null
  -rw-rw--w- 1 root root 1257 Jun 29 02:19 /dev/null

Steps to recover:

  # rm -f /dev/null; mknod -m 0666 /dev/null c 1 3

I looked at the 'bullseye' branch of the Salsa repo [1], I've seen that
you imported a number of patches related to the state file. In
particular, the patch Do-not-lock-state-file-dev-null.patch is what lead
me to shot myself in the foot, since it adds two lines in the manual
page, suggesting to use /dev/null as a state file:

  ++If \fI/dev/null\fR is given as the state file, then \fBlogrotate\fR will
  ++not try to lock or write the state file.

However, in your series of upstream patches, I think you missed this one:

  https://github.com/logrotate/logrotate/commit/45669264

Given the potential for destruction of 'logrotate -s /dev/null', and
seeing how simple is the patch above, would you consider doing an
upload to fix it in bullseye?

Best,

Arnaud



[1] https://salsa.debian.org/debian/logrotate/-/tree/bullseye

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[Richard Laager]

On 2023-06-28 20:14, forest.ow...@riseup.net wrote:

On 2023-06-28 02:39, Richard Laager wrote:

The original submitter replied off the tracker (probably by accident). I'll 
summarize here.

The ntp.conf he included is the stock ntp.conf.

He indicated he will try to get a backtrace.


I'm trying to setup ntpsec to get a backtrace.  I installed the
ntpsec-dbgsym package, but I'm not sure that I did it correctly.
Shouldn't the output from this file command include the text "no
stripped".


I don't think it should change that. I think the debug symbols end up 
somewhere else.


--
Richard

Bug#1039867: release.debian.org: Site uses old favicon.ico

[Nick Hastings]

Package: release.debian.org
Severity: minor
X-Debbugs-Cc: nicholaschasti...@gmail.com

Hi,

the site https://release.debian.org uses an old version
of the debian favicon.ico that renders poorly on dark
backgrounds. Please use the same favicon.ico as https://www.debian.org

Note that this is also a problem on https://backports.debian.org and
https://search.debian.org. I have already attempted to alert the relevant
people for those sites.

Regards,

Nick.

Bug#1039517: trixie : no more install bug

[Jean-Claude CATY]

Hello,

no more bug with 2023-06-26's iso (net install)


OpenPGP_0x3165709FEE52B44B.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[forest . owlet]

On 2023-06-28 02:39, Richard Laager wrote:
> The original submitter replied off the tracker (probably by accident). I'll 
> summarize here.
> 
> The ntp.conf he included is the stock ntp.conf.
> 
> He indicated he will try to get a backtrace.

I'm trying to setup ntpsec to get a backtrace.  I installed the
ntpsec-dbgsym package, but I'm not sure that I did it correctly. 
Shouldn't the output from this file command include the text "no
stripped".

root@karita:/home/root# file /usr/sbin/ntpd
/usr/sbin/ntpd: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=8bc6f9398efb6b8c446b2d719831f5738d563c84, for GNU/Linux
3.2.0, stripped
root@karita:/home/root#

Regards,


Roy

Bug#1039866: openssh-server: bookworm config enforces outdated extern sftp-server, unable to override

[Marc Lehmann]

Package: openssh-server
Version: 1:9.2p1-2
Severity: normal

Dear Maintainer,

after upgrading to bookworm, sshd did not come up again. The reason is
that the config file now enforces the usage of the outdated sftp-server
subsystem, and this is not overridable.

Please consider NOT enforcing a specific sftp implementation (going with
the defaults and letting users override it in separate4 conf files), or,
if it has to be done, make it easier to override it, or possibly default
to the modern "internal-sftp" implementation which allows chroot (and thus
provides better defense-in-dpeth in most cases).

Thanks for your work!

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'oldstable-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.1.35-schmorp (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssh-server depends on:
ii  adduser3.134
ii  debconf [debconf-2.0]  1.5.82
ii  init-system-helpers1.65.2
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9
ii  libcom-err21.47.0-2
ii  libcrypt1  1:4.4.33-2
ii  libgssapi-krb5-2   1.20.1-2
ii  libkrb5-3  1.20.1-2
ii  libpam-modules 1.5.2-6
ii  libpam-runtime 1.5.2-6
ii  libpam0g   1.5.2-6
ii  libselinux13.4-1+b6
ii  libssl33.0.9-1
ii  libsystemd0252.6-1
ii  libwrap0   7.6.q-32
ii  lsb-base   11.6
ii  openssh-client 1:9.2p1-2
ii  openssh-sftp-server1:9.2p1-2
ii  procps 2:4.0.2-3
ii  runit-helper   2.15.2
ii  sysvinit-utils [lsb-base]  3.06-4
ii  ucf3.0043+nmu1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  252.6-1
ii  ncurses-term 6.4-4
ii  xauth1:1.1.2-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
ii  ssh-askpass   1:1.2.4.1-16
pn  ufw   

-- debconf information excluded

Bug#1036752: bat: Manpage exists, use it

[johnny]

Package: bat
Version: 0.22.1-4
Followup-For: Bug #1036752
X-Debbugs-Cc: ro...@gmail.com

Control: severity -1 important

The manpage existed and still exists upstream.

It's really unfortunate that the package made it into stable release of 
bookworm without a manpage. Please fix for bookworm point release.

Bug#1015915: pipewire-pulse leaking memory

[Witold Baryluk]

Package: pipewire-pulse
Followup-For: Bug #1015915
X-Debbugs-Cc: witold.bary...@gmail.com
Control: notfound -1 0.3.65-3
Control: fixed -1

thanks

Cannot reproduce with 0.3.65-3 on same system. Closing.

Cheers.

Bug#1039741: libapache-poi-java: reproducible builds: timezone-specific timestamp in poi.jar

[Vagrant Cascadian]

On 2023-06-29, Jan-Benedict Glaw wrote:
> On Wed, 2023-06-28 13:34:31 -0700, Vagrant Cascadian 
>  wrote:
>> diff --git a/debian/rules b/debian/rules
>> index c94adb7..9ddad46 100755
>> --- a/debian/rules
>> +++ b/debian/rules
>> @@ -10,7 +10,7 @@ VERSION := $(shell echo $(DEB_VERSION_UPSTREAM) | sed 
>> 's/+dfsg//')
>>  dh $@ --with maven-repo-helper --with javahelper
>>  
>>  override_dh_auto_build:
>> -dh_auto_build -- -Dversion.id=$(VERSION) -DDSTAMP=$(shell date 
>> '--date=@$(SOURCE_DATE_EPOCH)' +%Y%m%d) jar maven-poms javadocs
>> +dh_auto_build -- -Dversion.id=$(VERSION) -DDSTAMP=$(shell date '--utc 
>> --date=@$(SOURCE_DATE_EPOCH)' +%Y%m%d) jar maven-poms javadocs
>>  
>>  override_dh_auto_test:
>>  ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
>
> IMHO the `--utc` is misplaced within the `--date` quoting.

Ah, sure ... although not sure that the '' are even necessary, as
SOURCE_DATE_EPOCH is an integer...

Regardless, the patch consistently works for me! :)

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1039450: ndctl: Split ndctl-monitor (and cxl-monitor?) into own package

[Witold Baryluk]

Package: ndctl
Version: 76.1-1
Followup-For: Bug #1039450
X-Debbugs-Cc: witold.bary...@gmail.com

Cześć Adamie.

I often use a custom livecd verision of Debian with various utilities
pre-installed, so they can be easily used offline, or without needing to
reinstall them after each reboot.

Among many other utilities I do have cxl and nvm dimm tools.

But often, if I boot this same livecd on a machine that does not have cxl
or nvm dimm devices, deamon will complain, and fail at boot (with big red
warning), and sytemd will continue restarting it afaik (or maybe not, it
looks like it tries to run it only once on my system, then gives up).

root@debian:~# systemctl status ndctl-monitor.service 
× ndctl-monitor.service - Ndctl Monitor Daemon
 Loaded: loaded (/lib/systemd/system/ndctl-monitor.service; enabled; 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2023-06-28 22:11:35 UTC; 
25min ago
   Duration: 89ms
Process: 2412 ExecStart=/usr/bin/ndctl monitor (code=exited, status=250)
   Main PID: 2412 (code=exited, status=250)
CPU: 9ms

Jun 28 22:11:35 debian systemd[1]: Started ndctl-monitor.service - Ndctl 
Monitor Daemon.
Jun 28 22:11:35 debian ndctl[2412]: no dimms to monitor, exiting
Jun 28 22:11:35 debian systemd[1]: ndctl-monitor.service: Main process exited, 
code=exited, status=250/n/a
Jun 28 22:11:35 debian systemd[1]: ndctl-monitor.service: Failed with result 
'exit-code'.


It is not a big deal, but something that is not perfect in my opinion.

For my livecd, I can clearly modify some systemd unit files manually
(using build scripts for live-build), but I wonder if defaulting to
running a daemon by default is a good idea in general. Most of the time
probably yes, but sometimes not.

As of smartmontools you mentioned. I have exactly same issue. I need
smartctl tools for troubleshooting various computers on my livecd, but I
DO NOT WANT smartd to start. For very similar reason I opened a bug
against smartmontools few days ago: https://bugs.debian.org/1039454


Feel free to downgrade to wishlist and think if this makes sense at all.

Cheers,
Witold

Bug#1039865: valgrind: reproducible-builds: differing permissions on debian.supp

[Vagrant Cascadian]

Source: valgrind
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: umask
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The permissions debian.supp differs depending on the umask of the build
environment:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/valgrind.html

  
-rw-r--r--···0·root·(0)·root·(0)·1136·2022-08-28·10:40:16.00·./usr/lib/valgrind/debian.supp
  vs.
  
-rw-rw-r--···0·root·(0)·root·(0)·1136·2022-08-28·10:40:16.00·./usr/lib/valgrind/debian.supp


The attached patch to debian/rules explicitly sets the permissions on
debian.supp after dh_fixperms is run.

Another approach is to remove the exclusion on .supp files from the
dh_fixperms call, though presumeably this was added for a reason and
that might need to be fixed some other way.

According to my local tests, with this patch applied valgrind should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining valgrind!

live well,
  vagrant
From 6438e2e60aaf4c84222ea578fc80357c3f5c0d19 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 28 Jun 2023 15:31:58 -0700
Subject: [PATCH] debian/rules: Explicitly set permissions on debian.supp file.

https://tests.reproducible-builds.org/debian/issues/unstable/different_due_to_umask_issue.html
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index 1dba244..5c7fcec 100755
--- a/debian/rules
+++ b/debian/rules
@@ -44,6 +44,7 @@ override_dh_install:
 
 override_dh_fixperms:
 	dh_fixperms -X.css -X.html -X.js -X.so -X.supp -X.xml
+	chmod u=rw,go=r debian/valgrind/usr/lib/valgrind/debian.supp
 
 override_dh_installchangelogs:
 	dh_installchangelogs NEWS
-- 
2.39.2



signature.asc
Description: PGP signature

Bug#1039741: libapache-poi-java: reproducible builds: timezone-specific timestamp in poi.jar

[Jan-Benedict Glaw]

On Wed, 2023-06-28 13:34:31 -0700, Vagrant Cascadian 
 wrote:
> diff --git a/debian/rules b/debian/rules
> index c94adb7..9ddad46 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -10,7 +10,7 @@ VERSION := $(shell echo $(DEB_VERSION_UPSTREAM) | sed 
> 's/+dfsg//')
>   dh $@ --with maven-repo-helper --with javahelper
>  
>  override_dh_auto_build:
> - dh_auto_build -- -Dversion.id=$(VERSION) -DDSTAMP=$(shell date 
> '--date=@$(SOURCE_DATE_EPOCH)' +%Y%m%d) jar maven-poms javadocs
> + dh_auto_build -- -Dversion.id=$(VERSION) -DDSTAMP=$(shell date '--utc 
> --date=@$(SOURCE_DATE_EPOCH)' +%Y%m%d) jar maven-poms javadocs
>  
>  override_dh_auto_test:
>  ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))

IMHO the `--utc` is misplaced within the `--date` quoting.

MfG, JBG

-- 


signature.asc
Description: PGP signature

Bug#1039863: DDPO: Add markers for toolchain and key packages

[Guillem Jover]

Package: qa.debian.org
Severity: wishlist

Hi!

During the freeze it's important to know which packages are part
of the toolchain and key package sets, and as those definitions are
under the purview of the release-team, so it might not always be
immediately obvious to the package maintainers whether the packages
they maintain fall under these. Which can cause disruption if an
accidental upload happens.

It would be nice to have a marker to denote toolchain packages, an
icon would be nice (such as 🔧 or ⚒), and another one for key
packages (such as 🔑). Probably linking to the pages defining
those package sets.

key → https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
toolchain → https://release.debian.org/testing/essential-and-build-essential.txt

Thanks,
Guillem

Bug#1039864: tracker.debian.org: Add markers for toolchain and key packages

[Guillem Jover]

Package: tracker.debian.org
Severity: wishlist

Hi!

During the freeze it's important to know which packages are part
of the toolchain and key package sets, and as those definitions are
under the purview of the release-team, so it might not always be
immediately obvious to the package maintainers whether the packages
they maintain fall under these. Which can cause disruption if an
accidental upload happens.

It would be nice to have a marker to denote toolchain packages, an
icon would be nice (such as 🔧 or ⚒), and another one for key
packages (such as 🔑). Probably linking to the pages defining
those package sets.

key → https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
toolchain → https://release.debian.org/testing/essential-and-build-essential.txt

Thanks,
Guillem

Bug#999850: Remaining changes

[Jelmer Vernooij]

Current todo list in terms of crate changes:

python-pkginfo: in NEW
cargo-config2: package v0.1.7
cfg-expr: update to v0.15.2
toml: update to v0.7.4
serde_spanned: update to v0.6.2
toml_datetime: update to v0.6.2
toml_edit: update to v0.19.10
serde_spanned: update to v0.6.2
winnow: update to v0.4.6
dirs: update to v5.0.1
dirs-sys: update to v0.4.1
option-ext: update to v0.2.0
cargo_metadata: update to v0.15.4
clap_complete_command: update to v0.5.1
clap_complete_fig: update to v4.2.0
fat-macho: update to v0.4.6
goblin: update to v0.6.1
scroll: update to v0.11.0
scroll_derive: update to v0.11.0
syn: update to v1.0.109
lddtree: update to v0.3.2
multipart v0.18.0
normpath: update to v1.1.1
trycmd: update to v0.14.11
humantime-serde: update to v1.1.1
snapbox: update to v0.4.4
concolor: update to v0.0.11
bitflags: update to v1.3.2

Note that "update to X" can also mean patching maturin to use the
version currently in the Debian archive.

Cheers,

Jelmer

Bug#1039860: bullseye-pu: package nvidia-graphics-drivers-tesla-470/470.199.02-1~deb11u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
Control: clone -1 -2
Control: retitle -2 bookworm-pu: package 
nvidia-graphics-drivers-tesla-470/470.199.02-1~deb12u1
Control: tag -2 = bookworm
Control: usertag -2 pu

[ Reason ]
Let's update nvidia-graphics-drivers-tesla-470 in bookworm/bullseye
to a new upstream release fixing some CVEs.

[ Impact ]
A proprietary graphics driver with more CVEs open.

[ Tests ]
Only module building has been tested. Anything else would require
certain hardware and driver usage.

[ Risks ]
Low. Upgrading to a new nvidia driver release in stable is an
established procedure.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  (excluding the blobs)
  [x] attach debdiff against the package in (old)stable
  (excluding the blobs)
  [x] the issue is verified as fixed in unstable

[ Changes ]
This is a rebuild of the package from sid with no further changes.
No packaging changes this time ;-)

[ Other info ]
The bookworm upload will be 470.199.02-1~deb12u1

Andreas
diff --git a/debian/README.source b/debian/README.source
index 05196920..f12ec8c5 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -33,7 +33,7 @@ Upstream support timeframes
 Tesla 460 (PB)  01/2022 EoL
 Tesla 470 (LTSB)07/2024
 Tesla 510 (PB)  01/2023 EoL
-Tesla 515 (PB)  05/2023
+Tesla 515 (PB)  05/2023 EoL
 Tesla 525 (PB)  12/2023
 
 
@@ -67,20 +67,12 @@ The branch structure in the GIT repository
 460-tesla   EoL   (bullseye)  470-tesla, tesla-460/main
 tesla-460/main  EoL   (bullseye),(sid)tesla-470/main, 
tesla-460/transition-470
 tesla-460/transition-470  bullseye,sid
-470   bullseye510, 470-tesla
-470-tesla (bullseye)  510-tesla, tesla-470/main
-tesla-470/mainbullseye,bookworm,sid tesla-510/main
-510 EoL   (bookworm),sid  515, 510-tesla
-510-tesla   EoL   (bookworm)  515-tesla, tesla-510/main
-tesla-510/main  EoL   (bookworm),(sid)tesla/510, 
tesla-510/transition
-tesla-510/transition  sid
-tesla/510   EoL   (bookworm),sid  tesla/515
-515   (bookworm),sid  525, 515-tesla
-515-tesla (bookworm)  525-tesla, tesla/515
-tesla/515 (bookworm),sid  tesla/525
-525   (bookworm),sid  YYY, 525-tesla
+470   bullseye525, 470-tesla
+470-tesla (bullseye)  525-tesla, tesla-470/main
+tesla-470/mainbullseye,bookworm,sid tesla/525
+525   bookworm,sidYYY, 525-tesla
 525-tesla (bookworm)  ZZZ-tesla, tesla/525
-tesla/525 (bookworm),sid  tesla/ZZZ
+tesla/525 bookworm,sidtesla/ZZZ
 main  sid YYY
 tesla/mainsid
 YYY   experimentalZZZ, (main)
diff --git a/debian/changelog b/debian/changelog
index b814ff31..f40fa976 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,43 @@
+nvidia-graphics-drivers-tesla-470 (470.199.02-1~deb11u1) bullseye; 
urgency=medium
+
+  * Rebuild for bullseye.
+
+ -- Andreas Beckmann   Thu, 29 Jun 2023 00:17:37 +0200
+
+nvidia-graphics-drivers-tesla-470 (470.199.02-1) unstable; urgency=medium
+
+  * New upstream production branch release 470.199.02 (2023-06-26).
+* Fixed CVE-2023-25515, CVE-2023-25516.  (Closes: #1039684)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5468
+* Improved compatibility with recent Linux kernels.
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+
+ -- Andreas Beckmann   Thu, 29 Jun 2023 00:16:48 +0200
+
+nvidia-graphics-drivers (470.199.02-1) bullseye; urgency=medium
+
+  * New upstream production branch release 470.199.02 (2023-06-26).
+* Fixed CVE-2023-25515, CVE-2023-25516.  (Closes: #1039678)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5468
+* Improved compatibility with recent Linux kernels.
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+  * Upload to bullseye.
+
+ -- Andreas Beckmann   Wed, 28 Jun 2023 23:20:58 +0200
+
+nvidia-graphics-drivers-tesla-470 (470.182.03-2) unstable; urgency=medium
+
+  * Backport vm_area_struct_has_const_vm_flags changes from 470.199.02 to fix
+kernel module build for Linux 6.3.  (Closes: #1038004)
+  * Backport drm_driver_has_dumb_destroy changes from 525.116.03 to fix kernel
+module build for Linux 6.4.
+
+ -- Andreas Beckmann   Sun, 18 Jun 2023 14:02:19 +0200
+
 nvidia-graphics-drivers-tesla-470 (470.182.03-1~deb11u1) bullseye; 
urgency=medium
 
   * Rebuild for bullseye.
@@ -30,6 +70,12 @@ nvidia-graphics-driv

Bug#1039040: bullseye-pu: cups/2.3.3op2-3+deb11u3

[Thorsten Alteholz]

On Mon, 26 Jun 2023, Jonathan Wiltshire wrote:

Please go ahead.


Great, thanks ...

... and uploaded.

  Thorsten

Bug#1039026: bookworm-pu: cups/2.4.2-3+deb12u1

[Thorsten Alteholz]

On Sun, 25 Jun 2023, Jonathan Wiltshire wrote:


Please go ahead.


Great, thanks ...

... and uploaded.

  Thorsten

Bug#1039862: bookworm-pu: cpdb-libs/1.2.0-2+deb12u1

[Thorsten Alteholz]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu


The attached debdiff for cpdb-libs fixes CVE-2023-34095 Bookworm. This CVE 
has been marked as no-dsa by the security team.


The fix just restricts the usable buffer and should have no side effects.

  Thorsten
diff -Nru cpdb-libs-1.2.0/debian/changelog cpdb-libs-1.2.0/debian/changelog
--- cpdb-libs-1.2.0/debian/changelog2023-01-12 22:03:02.0 +0100
+++ cpdb-libs-1.2.0/debian/changelog2023-06-27 22:03:02.0 +0200
@@ -1,3 +1,10 @@
+cpdb-libs (1.2.0-2+deb12u1) bookworm; urgency=medium
+
+  * CVE-2023-34095 (Closes: #1038253)
+buffer overflow via improper use of scanf()/fscanf()
+
+ -- Thorsten Alteholz   Tue, 27 Jun 2023 22:03:02 +0200
+
 cpdb-libs (1.2.0-2) unstable; urgency=medium
 
   * source upload
diff -Nru cpdb-libs-1.2.0/debian/patches/CVE-2023-34095.patch 
cpdb-libs-1.2.0/debian/patches/CVE-2023-34095.patch
--- cpdb-libs-1.2.0/debian/patches/CVE-2023-34095.patch 1970-01-01 
01:00:00.0 +0100
+++ cpdb-libs-1.2.0/debian/patches/CVE-2023-34095.patch 2023-06-27 
22:03:02.0 +0200
@@ -0,0 +1,161 @@
+Description: backported fix for CVE-2023-34095
+Index: cpdb-libs/demo/print_frontend.c
+===
+--- cpdb-libs.orig/demo/print_frontend.c   2023-06-28 06:57:31.699739106 
+0200
 cpdb-libs/demo/print_frontend.c2023-06-28 08:01:19.416613086 +0200
+@@ -48,7 +48,7 @@
+ {
+ printf("> ");
+ fflush(stdout);
+-scanf("%s", buf);
++scanf("%99s", buf);
+ if (strcmp(buf, "stop") == 0)
+ {
+ disconnect_from_dbus(f);
+@@ -84,7 +84,7 @@
+ {
+ char printer_id[100];
+ char backend_name[100];
+-scanf("%s%s", printer_id, backend_name);
++scanf("%99s%99s", printer_id, backend_name);
+ g_message("Getting all attributes ..\n");
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ 
+@@ -106,7 +106,7 @@
+ else if (strcmp(buf, "get-default") == 0)
+ {
+ char printer_id[100], backend_name[100], option_name[100];
+-scanf("%s%s%s", option_name, printer_id, backend_name);
++scanf("%99s%99s%99s", option_name, printer_id, backend_name);
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ char *ans = get_default(p, option_name);
+ if (!ans)
+@@ -117,7 +117,7 @@
+ else if (strcmp(buf, "get-setting") == 0)
+ {
+ char printer_id[100], backend_name[100], setting_name[100];
+-scanf("%s%s%s", setting_name, printer_id, backend_name);
++scanf("%99s%99s%99s", setting_name, printer_id, backend_name);
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ char *ans = get_setting(p, setting_name);
+ if (!ans)
+@@ -128,7 +128,7 @@
+ else if (strcmp(buf, "get-current") == 0)
+ {
+ char printer_id[100], backend_name[100], option_name[100];
+-scanf("%s%s%s", option_name, printer_id, backend_name);
++scanf("%99s%99s%99s", option_name, printer_id, backend_name);
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ char *ans = get_current(p, option_name);
+ if (!ans)
+@@ -139,7 +139,7 @@
+ else if (strcmp(buf, "add-setting") == 0)
+ {
+ char printer_id[100], backend_name[100], option_name[100], 
option_val[100];
+-scanf("%s %s %s %s", option_name, option_val, printer_id, 
backend_name);
++scanf("%99s %99s %99s %99s", option_name, option_val, printer_id, 
backend_name);
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ printf("%s : %s\n", option_name, option_val);
+ add_setting_to_printer(p, get_string_copy(option_name), 
get_string_copy(option_val));
+@@ -147,7 +147,7 @@
+ else if (strcmp(buf, "clear-setting") == 0)
+ {
+ char printer_id[100], backend_name[100], option_name[100];
+-scanf("%s%s%s", option_name, printer_id, backend_name);
++scanf("%99s%99s%99s", option_name, printer_id, backend_name);
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ clear_setting_from_printer(p, option_name);
+ }
+@@ -155,7 +155,7 @@
+ {
+ char printer_id[100];
+ char backend_name[100];
+-scanf("%s%s", printer_id, backend_name);
++scanf("%99s%99s", printer_id, backend_name);
+ PrinterObj *p = find_PrinterObj(f, printer_id, backend_name);
+ printf("%s\n", get_state(p));
+ }
+@@ -163,7 +163,7 @@
+ {
+ char printer_id[100];
+ char backend_name[100];
+-scanf("%s%s", print

Bug#1039743: christianriesen-base32: FTBFS with phpunit 10: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2

[Athos Ribeiro]

On Wed, Jun 28, 2023 at 10:31:53PM +0100, Adam D. Barratt wrote:

On Wed, 2023-06-28 at 17:57 -0300, Athos Ribeiro wrote:

Source: christianriesen-base32
Version: 1.6.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a
test
rebuild, christianriesen-base32 was found to FTBFS.


I've picked up an arbitrary bug from the set to reply to here.


Hi Adam,

thanks for the input here :)


Transitions should be co-ordinated with the Release Team, and I can't
see a tracking bug or discussion for this one (or the related symfony
transition). Have I simply missed it?


This was a follow-up on the onging discussion in
https://alioth-lists.debian.net/pipermail/pkg-php-pear/2023-June/022316.html


FTBFS bugs relating to transitions should be filed at severities below
RC until the transition has actually started.


Sorry for the noise. taffit did warn me about the severities when I was
already in the end of the process. Should I go ahead and re-set the
severity for those bugs?


I'm not one of the team members who regularly handles transitions any
more, but looking at the list of bugs you have filed so far tonight,
any transition that introduces over 100 build failures in other
packages is in no sense ready to happen "soon".


By soon I meant whenever we are done working on the list of bugs I
filled. Maybe "soon" was just poor wording here, but still, it is not
setting a target in time but leaving this rather open.

I wonder if the processes you are describing here is documented
somewhere (severities, when to mass file bugs for transitions, and
transition timing expectations after those are filed) so I can avoid
generating any unnecessary noise in the future.


Regards,

Adam



--
Athos Ribeiro

Bug#1039727: debian-installer configures ifupdown instead of NetworkManager even if a Desktop Environment is chosen

[Austin Moss]

Perhaps you may be on to something - my SSID has caused some issues on systems 
that cannot handle some characters. Strange that it ended up in the network 
configuration regardless. 

I would agree, it is not a "BIG" issue from my perspective. More of a nuisance 
I suppose. I would have to test with my other "normal" SSID to see if it works 
as expected but again, don't believe it's a big issue, so I'm not sure that's 
really necessary.
-Austin

On Wed, Jun 28, 2023, at 2:47 PM, Cyril Brulebois wrote:
> Austin Moss  (2023-06-28):
> > Thank you for taking a look at this. Attached an archive with
> > /var/log/installer/syslog for you.
> 
> The relevant parts of the log are likely the following:
> 
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Network config complete
> Jun 27 22:03:08 netcfg[4939]: DEBUG: No interface given; clearing 
> /etc/network/interfaces
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing informative header
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Success!
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing loopback interface
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Success!
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing DHCP stanza for wlp4s0
> Jun 27 22:03:08 netcfg[4939]: INFO: Detected wlp4s0 as a hotpluggable 
> device
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing wireless options for wlp4s0
> Jun 27 22:03:08 netcfg[4939]: DEBUG: Success!
> Jun 27 22:03:09 netcfg[4939]: INFO: Unable to open file for writing 
> network-manager configuration. The connection id (¯\_(ツ)_/¯) might not be set 
> to a proper value.
> 
> And later:
> 
> Jun 28 03:20:31 finish-install: info: Running 
> /usr/lib/finish-install.d/55netcfg-copy-config
> Jun 28 03:20:31 netcfg: DEBUG: copy-config: /tmp/connection_type not 
> found: netcfg did not complete or was compiled without network-manager 
> support; exiting.
> 
> While I'm not familiar with all the details, it looks to me the funky
> connection ID prevented some initial configuration, which led to a
> missing file expected at the end of the installation, which in turn led
> to a fallback /e/n/i configuration instead of the detected/desired NM
> configuration. But seeing how the last DEBUG message leads to an early
> exit in the finish-install script (responsible for copying things
> around), I'm not sure why/how /e/n/i got copied from the installer's
> context to the installed system…
> 
> 
> In any case, this might not be a “big issue” as I feared, just
> particular circumstances?
> 
> 
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
> 
> 
> *Attachments:*
>  • signature.asc

Bug#1039859: Screenshot

[Randall Flagg]

Bug#1039859: mixxx: Mixxx GUI is broken / elements not rendered

[lynthian4]

Package: mixxx
Version: 2.3.3~dfsg-2+b2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: lynthi...@trash-mail.com

Dear Maintainer,

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

   * What led up to the situation?
Upgrading from Debain 11 to Debian 12 caused the issue to appear.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Starting mixxx
   * What was the outcome of this action?
GUI is not being rendered correctly. Some elements, like the two waveforms on 
top, are 'transparent' and show a glitched view of the window below the mixxx 
application. Since these waveforms are part of the main GUI and a visual guide 
for mixing track this makes the package ununsable.
   * What outcome did you expect instead?
GUI being displayed normally, as it was the case in Debian 11.

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


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

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

Versions of packages mixxx depends on:
ii  libavcodec597:5.1.3-1
ii  libavformat59   7:5.1.3-1
ii  libavutil57 7:5.1.3-1
ii  libc6   2.36-9
ii  libchromaprint1 1.5.1-2+b1
ii  libebur128-11.2.6-1+b1
ii  libflac12   1.4.2+ds-2
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-2
ii  libhidapi-libusb0   0.13.1-1
ii  libid3tag0  0.15.1b-14
ii  liblilv-0-0 0.24.14-1
ii  libmad0 0.15.1b-10.1+b1
ii  libmodplug1 1:0.8.9.0-3
ii  libmp3lame0 3.100-6
ii  libogg0 1.3.5-3
ii  libopus01.3.1-3
ii  libopusfile00.12-4
ii  libportaudio2   19.6.0-1.2
ii  libportmidi01:217-6.1
ii  libprotobuf-lite32  3.21.12-3
ii  libqt5core5a5.15.8+dfsg-11
ii  libqt5dbus5 5.15.8+dfsg-11
ii  libqt5gui5  5.15.8+dfsg-11
ii  libqt5keychain1 0.13.2-5
ii  libqt5network5  5.15.8+dfsg-11
ii  libqt5opengl5   5.15.8+dfsg-11
ii  libqt5script5   5.15.8+dfsg-2
ii  libqt5scripttools5  5.15.8+dfsg-2
ii  libqt5sql5  5.15.8+dfsg-11
ii  libqt5sql5-sqlite   5.15.8+dfsg-11
ii  libqt5svg5  5.15.8-3
ii  libqt5widgets5  5.15.8+dfsg-11
ii  libqt5x11extras55.15.8-2
ii  libqt5xml5  5.15.8+dfsg-11
ii  librubberband2  3.1.2+dfsg0-1
ii  libsndfile1 1.2.0-1
ii  libsoundtouch1  2.3.2+ds1-1
ii  libsqlite3-03.40.1-2
ii  libssl3 3.0.9-1
ii  libstdc++6  12.2.0-14
ii  libswresample4  7:5.1.3-1
ii  libtag1v5   1.13-2
ii  libupower-glib3 0.99.20-2
ii  libusb-1.0-02:1.0.26-1
ii  libvorbis0a 1.3.7-1
ii  libvorbisenc2   1.3.7-1
ii  libvorbisfile3  1.3.7-1
ii  libwavpack1 5.6.0-1
ii  libx11-62:1.8.4-2+deb12u1
ii  mixxx-data  2.3.3~dfsg-2

mixxx recommends no packages.

Versions of packages mixxx suggests:
ii  evince [pdf-viewer]  43.1-2+b1

-- no debconf information

Bug#1039858: Missing dependencies on json-c >= 0.13, openssl >= 1.1.0, libkeyutils

[Michael Biebl]

Package: libnvme-dev
Version: 1.4-3
Severity: serious

The libnvme.pc declares the following dependencies:
Requires.private: json-c >= 0.13, openssl >= 1.1.0, libkeyutils

Those need to be added to the Depends of libnvme-dev, otherwise
pkgconfig will fail to e.g. resolve cflags.

# pkgconf --cflags libnvme
Package json-c was not found in the pkg-config search path.
Perhaps you should add the directory containing `json-c.pc'
to the PKG_CONFIG_PATH environment variable
Package 'json-c', required by 'libnvme', not found
Package 'openssl', required by 'libnvme', not found
Package 'libkeyutils', required by 'libnvme', not found

Bug#940960: ITP: linenoise -- Minimal replacement for readline

[Blair Noctis]

On 2023-06-18 05:10, Jeremy Sowden wrote:
>>> Yes, absolutely.  Apologies for taking three weeks to reply.
>>>
>>> J.
>>
>> And I took two days ;)

This time took literally two weeks, haha. Dragged away by $work.

> You've gone a for a less elaborate build process for the shared library
> than I did:
> 
>   
> https://github.com/antirez/linenoise/pull/174/commits/ab860406520ad7fc5e7e8e91fcf60cdc43a786f0
> 
> but that's probably fine.  I do have one observation, however.  The
> shared library should be liblinenoise.so.0.0.0 and there should be two
> sym-links: liblinenoise.so.0, which is needed by the library's
> dependencies at run-time, and liblinenoise.so which is needed by its
> dependencies at build-time.
> 
> I've attached a patch-series with some suggested changes.
> 
> J.

I've applied the patches after reading them. It's great to learn from code.

OTOH I saw your salsa repo. Since you've done that much I think it's probably
better to let you finish it?

-- 
Sdrager,
Blair Noctis



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039857: podman crashes my systemd-managed sway session on exit

[Antoine Beaupre]

Package: sway
Version: 1.8.1-1
Severity: minor

This is a rather hairy problem.

I have made the perhaps-ill-advised configuration of hooking up my
wayland / sway session as a systemd --user unit.

When i run containers with podman and they exit with an error, the whole 
session crashes.

The last lines before death are:


jun 28 16:53:39 angela podman[298210]: 2023-06-28 16:53:39.53329688 -0400 EDT 
m=+1.000110624 container died 
de96bebba97ba50229c01a93e1a0928c34b954b50ca1ea295c20c1d3c2970137 
(image=quay.io/minio/mc:latest [...]
jun 28 16:53:39 angela podman[298287]: 2023-06-28 16:53:39.624658051 -0400 EDT 
m=+0.086326242 container cleanup [...]
jun 28 16:53:39 angela systemd[296508]: sway.service: Main process exited, 
code=exited, status=1/FAILURE


The podman lines have way more stuff in there, but i spare you the
details...

My .config/systemd/user/ setup is documented in 
https://anarc.at/software/desktop/wayland/#systemd-integration

A plain:

podman run docker.io/library/debian:bookworm-slim

... can reproduce the issue. Note that the command needs to be ran
from a terminal spawned by Sway itself, say with $mod-Return. If I
start it from a separate unit or with `systemd-run`, it doesn't crash
the session on exit.

If I run:

podman run -it --rm docker.io/library/debian:bookworm-slim

I notice that `conmon(8)` takes over the Main PID which is
essentially the core of the problem here. Because Sway refuses to
support systemd:

https://github.com/swaywm/sway/issues/5160

... it does not send a proper "READY" state through sd_notify as other
services might normally do.

In general, that's not *too* much of a problem: systemd can start and
manage services fine without this. But in this case, I'm starting
other units that *do* depend on Sway being ready to run, so I *do*
need this state to properly chain dependencies here.

So I have this horror in my sway config:

exec dbus-update-activation-environment --systemd XDG_CURRENT_DESKTOP=sway \
  && systemctl --user import-environment SWAYSOCK \
 DISPLAY \
 I3SOCK \
 WAYLAND_DISPLAY \
 XCURSOR_SIZE \
 XCURSOR_THEME \
  && systemd-notify --ready


And the systemd sway.service has:

NotifyAccess=all

... which is how conmon is able to hijack the Main PID.

A workaround is to change the Sway keybindings to start processes with
systemd, like this:

# start a terminal
#
# we start it as a systemd unit on the fly otherwise podman takes over
# the Main PID of the sway.service and container exits crash the whole
# session
bindsym $mod+Return exec systemd-run --user foot

The real fix here would be for Sway to send something to sd-daemon. Of
course, the easiest way to do this would be to do a clever call to
sd_notify() just at the right place in the Sway source code, but
there's little chance such a patch would be merged upstream...

I looked at the code, and the actual sd_notify() call is not *that*
complex. It opens a UNIX socket and shoves a message in there,
probably just READY=1. Surely Sway could figure out how to write to a
socket on its own?

Hell, it could even just vendor this stupid piece of code here:

https://sources.debian.org/src/systemd/253-4/src/libsystemd/sd-daemon/sd-daemon.c/#L453-L602

Anyway, I don't mean to troll here, but this was a really complicated
bug to figure out and to fix for me (thanks #debian-systemd folks!),
so I figured I would at *least* document it here somehow.

The best case scenario for me is that sway gets sd_notify support. A
working compromise could be an update to the README.Debian file or
even better a sample sway config that has the right knobs.

Failing that, I'm happy to just see this bug closed and add this to
the pile of custom weird shit I carry around everywhere.

Cheers! :)

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), 
(1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages sway depends on:
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libevdev21.13.0+dfsg-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgl1-mesa-dri  22.3.6-1+deb12u1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-2
ii  libinput10   1.22.1-1
ii  libjson-c5   0.16-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpcre2-8-0 10.42-1
ii  libpixman-1-00.42.2-1
ii  libsystemd0  

Bug#1039856: symfony: FTBFS with phpunit 10: PHP Fatal error: Trait "PHPUnit\Framework\TestListenerDefaultImplementation" not found in /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsL

[Athos Ribeiro]

Source: symfony
Version: 5.4.24+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, symfony was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ln -s ./src/Symfony ./Symfony
> mkdir --parents vendor
> cp debian/autoload_runtime.php vendor
> phpab --output vendor/autoload.php \
>   --whitelist '*\\tests\\*' \
>   --tolerant \
>   --template debian/autoload.php.tests.tpl \
>   --blacklist 
> 'symfony\\component\\dependencyinjection\\tests\\fixtures\\container\\projectservicecontainer'
>  \
>   --exclude 
> 'Symfony/Bridge/ProxyManager/Tests/LazyProxy/PhpDumper/Fixtures/proxy-implem.php'
>  \
>   --exclude 
> 'Symfony/Component/Routing/Tests/Fixtures/AttributesFixtures/*' \
>   Symfony
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory Symfony
> 
> Autoload file vendor/autoload.php generated.
> 
> # Actual tests suite
> components=$(find src/Symfony -mindepth 3 -maxdepth 4 -type f -name 
> phpunit.xml.dist -printf '%h\n') && \
>  echo "$components" | parallel --gnu --keep-order '/bin/echo -e "\\nRunning 
> {} tests"; SYMFONY_DEPRECATIONS_HELPER=weak php -d assert.exception=1 -d 
> zend.assertions=1 /usr/bin/phpunit -v --colors=always --exclude-group 
> network,tty,benchmark,intl-data,functional,composer {} || (/bin/echo -e 
> "\\e[41mKO\\e[0m {}" && $(exit 1));';
> 
> Running src/Symfony/Bridge/Doctrine tests
> KO src/Symfony/Bridge/Doctrine
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Bridge/ProxyManager tests
> KO src/Symfony/Bridge/ProxyManager
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Bridge/Monolog tests
> KO src/Symfony/Bridge/Monolog
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Bridge/PhpUnit tests
> KO src/Symfony/Bridge/PhpUnit
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Bridge/Twig tests
> KO src/Symfony/Bridge/Twig
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/Semaphore tests
> KO src/Symfony/Component/Semaphore
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/Translation tests
> KO src/Symfony/Component/Translation
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/PasswordHasher tests
> KO src/Symfony/Component/PasswordHasher
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/Dotenv tests
> KO src/Symfony/Component/Dotenv
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/ExpressionLanguage tests
> KO src/Symfony/Component/ExpressionLanguage
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/Cache tests
> KO src/Symfony/Component/Cache
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php
>  on line 26
> 
> Running src/Symfony/Component/PropertyInfo tests
> KO src/Symfony/Component/PropertyInfo
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /<>/src/S

Bug#1039738: bullseye-pu: package nvidia-graphics-drivers-tesla-450/450.248.02-1~deb11u1

[Andreas Beckmann]

Followup-For: Bug #1039738

here comes the forgotten diff
diff --git a/debian/README.source b/debian/README.source
index 05196920..f12ec8c5 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -33,7 +33,7 @@ Upstream support timeframes
 Tesla 460 (PB)  01/2022 EoL
 Tesla 470 (LTSB)07/2024
 Tesla 510 (PB)  01/2023 EoL
-Tesla 515 (PB)  05/2023
+Tesla 515 (PB)  05/2023 EoL
 Tesla 525 (PB)  12/2023
 
 
@@ -67,20 +67,12 @@ The branch structure in the GIT repository
 460-tesla   EoL   (bullseye)  470-tesla, tesla-460/main
 tesla-460/main  EoL   (bullseye),(sid)tesla-470/main, 
tesla-460/transition-470
 tesla-460/transition-470  bullseye,sid
-470   bullseye510, 470-tesla
-470-tesla (bullseye)  510-tesla, tesla-470/main
-tesla-470/mainbullseye,bookworm,sid tesla-510/main
-510 EoL   (bookworm),sid  515, 510-tesla
-510-tesla   EoL   (bookworm)  515-tesla, tesla-510/main
-tesla-510/main  EoL   (bookworm),(sid)tesla/510, 
tesla-510/transition
-tesla-510/transition  sid
-tesla/510   EoL   (bookworm),sid  tesla/515
-515   (bookworm),sid  525, 515-tesla
-515-tesla (bookworm)  525-tesla, tesla/515
-tesla/515 (bookworm),sid  tesla/525
-525   (bookworm),sid  YYY, 525-tesla
+470   bullseye525, 470-tesla
+470-tesla (bullseye)  525-tesla, tesla-470/main
+tesla-470/mainbullseye,bookworm,sid tesla/525
+525   bookworm,sidYYY, 525-tesla
 525-tesla (bookworm)  ZZZ-tesla, tesla/525
-tesla/525 (bookworm),sid  tesla/ZZZ
+tesla/525 bookworm,sidtesla/ZZZ
 main  sid YYY
 tesla/mainsid
 YYY   experimentalZZZ, (main)
diff --git a/debian/changelog b/debian/changelog
index 3e8acfbf..5f41b72d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,35 @@
+nvidia-graphics-drivers-tesla-450 (450.248.02-1~deb11u1) bullseye; 
urgency=medium
+
+  * Rebuild for bullseye.
+
+ -- Andreas Beckmann   Wed, 28 Jun 2023 20:20:39 +0200
+
+nvidia-graphics-drivers-tesla-450 (450.248.02-1) unstable; urgency=medium
+
+  * New upstream Tesla release 450.248.02 (2023-06-26).
+* Fixed CVE-2023-25515, CVE-2023-25516.  (Closes: #1039682)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5468
+* Improved compatibility with recent Linux kernels.
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+
+ -- Andreas Beckmann   Wed, 28 Jun 2023 20:01:45 +0200
+
+nvidia-graphics-drivers-tesla-450 (450.236.01-3) UNRELEASED; urgency=medium
+
+  * Backport drm_driver_has_dumb_destroy changes from 525.116.03 to fix kernel
+module build for Linux 6.4.
+
+ -- Andreas Beckmann   Fri, 16 Jun 2023 18:29:09 +0200
+
+nvidia-graphics-drivers-tesla-450 (450.236.01-2) unstable; urgency=medium
+
+  * Backport vm_area_struct_has_const_vm_flags changes from 470.199.02 to fix
+kernel module build for Linux 6.3.
+
+ -- Andreas Beckmann   Fri, 16 Jun 2023 10:54:54 +0200
+
 nvidia-graphics-drivers-tesla-450 (450.236.01-1~deb11u1) bullseye; 
urgency=medium
 
   * Rebuild for bullseye.
@@ -1072,6 +1104,20 @@ nvidia-graphics-drivers (430.14-1) experimental; 
urgency=medium
 
  -- Andreas Beckmann   Sat, 25 May 2019 13:49:09 +0200
 
+nvidia-graphics-drivers-tesla-418 (418.226.00-12) UNRELEASED; urgency=medium
+
+  * Backport drm_driver_has_dumb_destroy changes from 525.116.03 to fix kernel
+module build for Linux 6.4.
+
+ -- Andreas Beckmann   Fri, 16 Jun 2023 17:43:27 +0200
+
+nvidia-graphics-drivers-tesla-418 (418.226.00-11) unstable; urgency=medium
+
+  * Backport vm_area_struct_has_const_vm_flags changes from 470.199.02 to fix
+kernel module build for Linux 6.3.
+
+ -- Andreas Beckmann   Thu, 15 Jun 2023 14:07:08 +0200
+
 nvidia-graphics-drivers-tesla-418 (418.226.00-10) unstable; urgency=medium
 
   * Backport acpi_op_remove changes from 470.182.03 to fix kernel module build
@@ -2014,6 +2060,20 @@ nvidia-graphics-drivers (396.18-1) experimental; 
urgency=medium
 
  -- Andreas Beckmann   Sun, 22 Apr 2018 13:59:45 +0200
 
+nvidia-graphics-drivers (390.157-4) UNRELEASED; urgency=medium
+
+  * Backport drm_driver_has_dumb_destroy changes from 525.116.03 to fix kernel
+module build for Linux 6.4.
+
+ -- Andreas Beckmann   Fri, 16 Jun 2023 17:29:02 +0200
+
+nvidia-graphics-drivers (390.157-3) UNRELEASED; urgency=medium
+
+  * Backport vm_area_struct_has_const_vm_flags changes from 470.199.02 to fix
+kernel module build for Linux 6.3.
+
+ -- Andreas Beckmann   Thu, 15 Jun 2023 10:01:34 +0200
+
 nvidia-graphics-drivers (390

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

[Jeremy Bícha]

Control: severity -1 serious

On Wed, Jun 28, 2023 at 5:29 PM Dirk Eddelbuettel  wrote:
> Feel free to change the severity back if you truly think it is that serious.

Done.

Feel free to close the bug once r-base is ready to migrate to Testing.
This is mostly just a tracking bug that people may find easier than
browsing the mailing list.

> I maintain that r-base is fine.  I have no control over how other people use
> my package, and if all other maintainers put breaking autopkgtests in well
> yes then they do hold r-base hostage and it will take "forever" to migrate to
> testing.  We have been there before.

Some just set this field in debian/control:
Testsuite: autopkgtest-pkg-r

Thank you,
Jeremy Bícha

Bug#1039855: shaarli: FTBFS with phpunit 10: dh_auto_test: error: make -j1 test returned exit code 2

[Athos Ribeiro]

Source: shaarli
Version: 0.12.1+dfsg-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, shaarli was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 25 errors:
> 
> 1) 
> Shaarli\Front\Controller\Admin\ManageTagControllerTest::testSaveRenameTagValid
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ManageTagControllerTest.php:113
> /usr/bin/phpunit:74
> 
> 2) 
> Shaarli\Front\Controller\Admin\ManageTagControllerTest::testSaveDeleteTagValid
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ManageTagControllerTest.php:166
> /usr/bin/phpunit:74
> 
> 3) 
> Shaarli\Front\Controller\Admin\PluginsControllerTest::testSavePluginParameters
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/PluginsControllerTest.php:149
> /usr/bin/phpunit:74
> 
> 4) 
> Shaarli\Front\Controller\Admin\ShaareManageControllerTest\ChangeVisibilityBookmarkTest::testSetMultipleBookmarksPrivate
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaareManageControllerTest/ChangeVisibilityBookmarkTest.php:200
> /usr/bin/phpunit:74
> 
> 5) 
> Shaarli\Front\Controller\Admin\ShaareManageControllerTest\ChangeVisibilityBookmarkTest::testChangeVisibilityMultipleBookmarksOneNotFound
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaareManageControllerTest/ChangeVisibilityBookmarkTest.php:304
> /usr/bin/phpunit:74
> 
> 6) 
> Shaarli\Front\Controller\Admin\ShaareManageControllerTest\DeleteBookmarkTest::testDeleteMultipleBookmarks
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaareManageControllerTest/DeleteBookmarkTest.php:115
> /usr/bin/phpunit:74
> 
> 7) 
> Shaarli\Front\Controller\Admin\ShaareManageControllerTest\DeleteBookmarkTest::testDeleteMultipleBookmarksOneNotFound
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaareManageControllerTest/DeleteBookmarkTest.php:235
> /usr/bin/phpunit:74
> 
> 8) 
> Shaarli\Front\Controller\Admin\ShaarePublishControllerTest\DisplayCreateFormTest::testDisplayCreateFormWithUrlAndWithMetadataRetrieval
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaarePublishControllerTest/DisplayCreateFormTest.php:83
> /usr/bin/phpunit:74
> 
> 9) 
> Shaarli\Front\Controller\Admin\ShaarePublishControllerTest\DisplayCreateFormTest::testDisplayCreateFormWithUrlAndWithoutMetadata
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaarePublishControllerTest/DisplayCreateFormTest.php:149
> /usr/bin/phpunit:74
> 
> 10) 
> Shaarli\Front\Controller\Admin\ShaarePublishControllerTest\SaveBookmarkTest::testSaveBookmark
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaarePublishControllerTest/SaveBookmarkTest.php:97
> /usr/bin/phpunit:74
> 
> 11) 
> Shaarli\Front\Controller\Admin\ShaarePublishControllerTest\SaveBookmarkTest::testSaveExistingBookmark
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/admin/ShaarePublishControllerTest/SaveBookmarkTest.php:188
> /usr/bin/phpunit:74
> 
> 12) 
> Shaarli\Front\Controller\Visitor\BookmarkListControllerTest::testThumbnailUpdateFromLinkList
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/visitor/BookmarkListControllerTest.php:355
> /usr/bin/phpunit:74
> 
> 13) 
> Shaarli\Front\Controller\Visitor\BookmarkListControllerTest::testThumbnailUpdateFromPermalink
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/front/controller/visitor/

Bug#1039854: bullseye-pu: package nvidia-graphics-drivers/470.199.02-1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
Let's update nvidia-graphics-drivers in bullseye to a new
upstream release fixing some CVEs.

[ Impact ]
A proprietary graphics driver with more CVEs open.

[ Tests ]
Only module building has been tested. Anything else would require
certain hardware and driver usage.

[ Risks ]
Low. Upgrading to a new nvidia driver release in stable is an
established procedure.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  (excluding the blobs)
  [x] attach debdiff against the package in (old)stable
  (excluding the blobs)
  [ ] the issue is verified as fixed in unstable
  will be fixed with an upload of the 525 driver soon

[ Changes ]
This package is nearly identical to
src:nvidia-graphics-drivers-tesla-470 470.199.02-1* in
sid/bookworm (soon)/bullseye (soon).
There are no packaging changes this time ;-)

[ Other info ]
n/a

Andreas
diff --git a/debian/README.source b/debian/README.source
index 05196920..f12ec8c5 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -33,7 +33,7 @@ Upstream support timeframes
 Tesla 460 (PB)  01/2022 EoL
 Tesla 470 (LTSB)07/2024
 Tesla 510 (PB)  01/2023 EoL
-Tesla 515 (PB)  05/2023
+Tesla 515 (PB)  05/2023 EoL
 Tesla 525 (PB)  12/2023
 
 
@@ -67,20 +67,12 @@ The branch structure in the GIT repository
 460-tesla   EoL   (bullseye)  470-tesla, tesla-460/main
 tesla-460/main  EoL   (bullseye),(sid)tesla-470/main, 
tesla-460/transition-470
 tesla-460/transition-470  bullseye,sid
-470   bullseye510, 470-tesla
-470-tesla (bullseye)  510-tesla, tesla-470/main
-tesla-470/mainbullseye,bookworm,sid tesla-510/main
-510 EoL   (bookworm),sid  515, 510-tesla
-510-tesla   EoL   (bookworm)  515-tesla, tesla-510/main
-tesla-510/main  EoL   (bookworm),(sid)tesla/510, 
tesla-510/transition
-tesla-510/transition  sid
-tesla/510   EoL   (bookworm),sid  tesla/515
-515   (bookworm),sid  525, 515-tesla
-515-tesla (bookworm)  525-tesla, tesla/515
-tesla/515 (bookworm),sid  tesla/525
-525   (bookworm),sid  YYY, 525-tesla
+470   bullseye525, 470-tesla
+470-tesla (bullseye)  525-tesla, tesla-470/main
+tesla-470/mainbullseye,bookworm,sid tesla/525
+525   bookworm,sidYYY, 525-tesla
 525-tesla (bookworm)  ZZZ-tesla, tesla/525
-tesla/525 (bookworm),sid  tesla/ZZZ
+tesla/525 bookworm,sidtesla/ZZZ
 main  sid YYY
 tesla/mainsid
 YYY   experimentalZZZ, (main)
diff --git a/debian/changelog b/debian/changelog
index 3cfb9f5c..13cf2635 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,25 @@
+nvidia-graphics-drivers (470.199.02-1) bullseye; urgency=medium
+
+  * New upstream production branch release 470.199.02 (2023-06-26).
+* Fixed CVE-2023-25515, CVE-2023-25516.  (Closes: #1039678)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5468
+* Improved compatibility with recent Linux kernels.
+
+  [ Andreas Beckmann ]
+  * Refresh patches.
+  * Upload to bullseye.
+
+ -- Andreas Beckmann   Wed, 28 Jun 2023 23:20:58 +0200
+
+nvidia-graphics-drivers (470.182.03-2) UNRELEASED; urgency=medium
+
+  * Backport vm_area_struct_has_const_vm_flags changes from 470.199.02 to fix
+kernel module build for Linux 6.3.
+  * Backport drm_driver_has_dumb_destroy changes from 525.116.03 to fix kernel
+module build for Linux 6.4.
+
+ -- Andreas Beckmann   Sun, 18 Jun 2023 14:02:19 +0200
+
 nvidia-graphics-drivers (470.182.03-1) bullseye; urgency=medium
 
   * New upstream production branch release 470.182.03 (2023-03-30).
@@ -6,6 +28,12 @@ nvidia-graphics-drivers (470.182.03-1) bullseye; 
urgency=medium
   CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191.
   https://nvidia.custhelp.com/app/answers/detail/a_id/5452
   (Closes: #1033774)
+- Fixed a bug that could cause fullscreen PRIME Render Offload
+  applications and/or X to crash when an NVIDIA GPU is driving
+  multiple displays with Reverse PRIME.
+- Added support for console restoration when using simpledrm.
+- Disabled Fixed Rate Link (FRL) when using passive DisplayPort
+  to HDMI dongles, which are incompatible with FRL.
 * Improved compatibility with recent Linux kernels.
 
   [ Andreas Beckmann ]
@@ -546,6 +574,20 @@ nvidia-graphics-drivers (465.24.02-1) expe

Bug#1039853: roundcube: FTBFS with phpunit 10: make[1]: *** [debian/rules:105: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: roundcube
Version: 1.6.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, roundcube was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 42 PHPUnit test runner warnings:
> 
> 1) Class GroupAddmembers cannot be found in 
> /<>/tests/Actions/Contacts/GroupAddmembers.php
> 
> 2) Class GroupCreate cannot be found in 
> /<>/tests/Actions/Contacts/GroupCreate.php
> 
> 3) Class GroupDelete cannot be found in 
> /<>/tests/Actions/Contacts/GroupDelete.php
> 
> 4) Class GroupDelmembers cannot be found in 
> /<>/tests/Actions/Contacts/GroupDelmembers.php
> 
> 5) Class GroupRename cannot be found in 
> /<>/tests/Actions/Contacts/GroupRename.php
> 
> 6) Class SearchCreate cannot be found in 
> /<>/tests/Actions/Contacts/SearchCreate.php
> 
> 7) Class SearchDelete cannot be found in 
> /<>/tests/Actions/Contacts/SearchDelete.php
> 
> 8) Class UploadPhoto cannot be found in 
> /<>/tests/Actions/Contacts/UploadPhoto.php
> 
> 9) Class Enigma cannot be found in 
> /<>/plugins/enigma/tests/Enigma.php
> 
> 10) Class Managesieve cannot be found in 
> /<>/plugins/managesieve/tests/Managesieve.php
> 
> 11) Class Acl cannot be found in /<>/plugins/acl/tests/Acl.php
> 
> 12) Class AdditionalMessageHeaders cannot be found in 
> /<>/plugins/additional_message_headers/tests/AdditionalMessageHeaders.php
> 
> 13) Class Archive declared in 
> /<>/plugins/archive/tests/Archive.php does not extend 
> PHPUnit\Framework\TestCase
> 
> 14) Class AttachmentReminder cannot be found in 
> /<>/plugins/attachment_reminder/tests/AttachmentReminder.php
> 
> 15) Class Autologon cannot be found in 
> /<>/plugins/autologon/tests/Autologon.php
> 
> 16) Class Autologout cannot be found in 
> /<>/plugins/autologout/tests/Autologout.php
> 
> 17) Class DatabaseAttachments cannot be found in 
> /<>/plugins/database_attachments/tests/DatabaseAttachments.php
> 
> 18) Class DebugLogger cannot be found in 
> /<>/plugins/debug_logger/tests/DebugLogger.php
> 
> 19) Class Emoticons cannot be found in 
> /<>/plugins/emoticons/tests/Emoticons.php
> 
> 20) Class ExampleAddressbook cannot be found in 
> /<>/plugins/example_addressbook/tests/ExampleAddressbook.php
> 
> 21) Class FilesystemAttachments cannot be found in 
> /<>/plugins/filesystem_attachments/tests/FilesystemAttachments.php
> 
> 22) Class Help cannot be found in /<>/plugins/help/tests/Help.php
> 
> 23) Class HideBlockquote cannot be found in 
> /<>/plugins/hide_blockquote/tests/HideBlockquote.php
> 
> 24) Class HttpAuthentication cannot be found in 
> /<>/plugins/http_authentication/tests/HttpAuthentication.php
> 
> 25) Class Identicon cannot be found in 
> /<>/plugins/identicon/tests/Identicon.php
> 
> 26) Class IdentitySelect cannot be found in 
> /<>/plugins/identity_select/tests/IdentitySelect.php
> 
> 27) Class Jqueryui declared in 
> /<>/plugins/jqueryui/tests/Jqueryui.php does not extend 
> PHPUnit\Framework\TestCase
> 
> 28) Class KrbAuthentication cannot be found in 
> /<>/plugins/krb_authentication/tests/KrbAuthentication.php
> 
> 29) Class Markasjunk declared in 
> /<>/plugins/markasjunk/tests/Markasjunk.php does not extend 
> PHPUnit\Framework\TestCase
> 
> 30) Class NewUserDialog cannot be found in 
> /<>/plugins/new_user_dialog/tests/NewUserDialog.php
> 
> 31) Class NewUserIdentity cannot be found in 
> /<>/plugins/new_user_identity/tests/NewUserIdentity.php
> 
> 32) Class NewmailNotifier cannot be found in 
> /<>/plugins/newmail_notifier/tests/NewmailNotifier.php
> 
> 33) Class Password cannot be found in 
> /<>/plugins/password/tests/Password.php
> 
> 34) Class RedundantAttachments cannot be found in 
> /<>/plugins/redundant_attachments/tests/RedundantAttachments.php
> 
> 35) Class ShowAdditionalHeaders cannot be found in 
> /<>/plugins/show_additional_headers/tests/ShowAdditionalHeaders.php
> 
> 36) Class SquirrelmailUsercopy cannot be found in 
> /<>/plugins/squirrelmail_usercopy/tests/SquirrelmailUsercopy.php
> 
> 37) Class SubscriptionsOption cannot be found in 
> /<>/plugins/subscriptions_option/tests/SubscriptionsOption.php
> 
> 38) Class Userinfo cannot be found in 
> /<>/plugins/userinfo/tests/Userinfo.php
> 
> 39) Class VcardAttachments cannot be found in 
> /<>/plugins/vcard_attachments/tests/VcardAttachments.php
> 
> 40) Class VirtuserFile cannot be found in 
> /<>/plugins/virtuser_file/tests/VirtuserFile.php
> 
> 41) Class VirtuserQuery cannot be found in 
> /<>/plugins/virtuser_query/tests/VirtuserQuery.php
> 
> 42) Class Zipdownload declared in 
> /<>/plugins/zipdownload/tests/Zipdownload.php does not extend 
> PHPUnit\Framework\TestCase
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML c

Bug#1039852: php-zeta-console-tools: FTBFS with phpunit 10: unsatisfiable build-dependency: phpunit (< 10~~) but 10.2.2-1 is to be installed

[Athos Ribeiro]

Source: php-zeta-console-tools
Version: 1.7.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-zeta-console-tools was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> php-zeta-base, php-zeta-unit-test, phpab, phpunit, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> php-zeta-base, php-zeta-unit-test, phpab, phpunit, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [693 B]
> Get:5 copy:/<>/apt_archive ./ Packages [725 B]
> Fetched 2027 B in 0s (0 B/s)
> Reading package lists...
> Get:1 file:/<>/resolver-DdI70m/apt_archive ./ InRelease
> Ign:1 file:/<>/resolver-DdI70m/apt_archive ./ InRelease
> Get:2 file:/<>/resolver-DdI70m/apt_archive ./ Release [609 B]
> Get:2 file:/<>/resolver-DdI70m/apt_archive ./ Release [609 B]
> Get:3 file:/<>/resolver-DdI70m/apt_archive ./ Release.gpg
> Ign:3 file:/<>/resolver-DdI70m/apt_archive ./ Release.gpg
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  php-zeta-unit-test : Depends: phpunit (< 10~~) but 10.2.2-1 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-zeta-console-tools/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039851: php-zeta-base: FTBFS with phpunit 10: unsatisfiable build-dependency: phpunit (< 10~~) but 10.2.2-1 is to be installed

[Athos Ribeiro]

Source: php-zeta-base
Version: 1.9.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-zeta-base was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> imagemagick, php-zeta-unit-test, phpab, phpunit, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> imagemagick, php-zeta-unit-test, phpab, phpunit, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [691 B]
> Get:5 copy:/<>/apt_archive ./ Packages [723 B]
> Fetched 2023 B in 0s (0 B/s)
> Reading package lists...
> Get:1 file:/<>/resolver-UqKW2Z/apt_archive ./ InRelease
> Ign:1 file:/<>/resolver-UqKW2Z/apt_archive ./ InRelease
> Get:2 file:/<>/resolver-UqKW2Z/apt_archive ./ Release [609 B]
> Get:2 file:/<>/resolver-UqKW2Z/apt_archive ./ Release [609 B]
> Get:3 file:/<>/resolver-UqKW2Z/apt_archive ./ Release.gpg
> Ign:3 file:/<>/resolver-UqKW2Z/apt_archive ./ Release.gpg
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  php-zeta-unit-test : Depends: phpunit (< 10~~) but 10.2.2-1 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-zeta-base/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039849: php-zend-eventmanager: FTBFS with phpunit 10: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-zend-eventmanager
Version: 3.10.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-zend-eventmanager was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 3 errors:
> 
> 1) 
> LaminasTest\EventManager\AbstractListenerAggregateTest::testDetachRemovesAttachedListeners
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/test/ListenerAggregateTraitTest.php:25
> 
> 2) 
> LaminasTest\EventManager\LazyListenerAggregateTest::testAttachAttachesLazyListenersViaClosures
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/test/LazyListenerAggregateTest.php:153
> 
> 3) 
> LaminasTest\EventManager\ListenerAggregateTraitTest::testDetachRemovesAttachedListeners
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/test/ListenerAggregateTraitTest.php:25
> 
> --
> 
> 19 tests triggered 19 PHPUnit deprecations:
> 
> 1) 
> LaminasTest\EventManager\EventManagerTest::testAttachShouldAddReturnTheListener
> Data Provider method 
> LaminasTest\EventManager\EventManagerTest::eventArguments() is not static
> 
> /<>/test/EventManagerTest.php:123
> 
> 2) 
> LaminasTest\EventManager\EventManagerTest::testAttachRaisesExceptionForInvalidEventType
> Data Provider method 
> LaminasTest\EventManager\EventManagerTest::invalidEventsForAttach() is not 
> static
> 
> /<>/test/EventManagerTest.php:523
> 
> 3) 
> LaminasTest\EventManager\EventManagerTest::testPassingInvalidEventTypeToDetachRaisesException
> Data Provider method 
> LaminasTest\EventManager\EventManagerTest::invalidEventsForDetach() is not 
> static
> 
> /<>/test/EventManagerTest.php:754
> 
> 4) 
> LaminasTest\EventManager\EventManagerTest::testTriggeringAnEventWithAnEmptyNameRaisesAnException
> Data Provider method 
> LaminasTest\EventManager\EventManagerTest::eventsMissingNames() is not static
> 
> /<>/test/EventManagerTest.php:809
> 
> 5) 
> LaminasTest\EventManager\FilterIteratorTest::testInsertShouldRaiseExceptionOnNonCallableDatum
> Data Provider method 
> LaminasTest\EventManager\FilterIteratorTest::invalidFilters() is not static
> 
> /<>/test/FilterIteratorTest.php:100
> 
> 6) 
> LaminasTest\EventManager\LazyEventListenerTest::testConstructorRaisesExceptionForInvalidEventType
> Data Provider method 
> LaminasTest\EventManager\LazyEventListenerTest::invalidTypes() is not static
> 
> /<>/test/LazyEventListenerTest.php:37
> 
> 7) 
> LaminasTest\EventManager\LazyEventListenerTest::testConstructorRaisesExceptionForInvalidListenerType
> Data Provider method 
> LaminasTest\EventManager\LazyEventListenerTest::invalidTypes() is not static
> 
> /<>/test/LazyListenerTest.php:63
> 
> 8) 
> LaminasTest\EventManager\LazyEventListenerTest::testConstructorRaisesExceptionForInvalidMethodType
> Data Provider method 
> LaminasTest\EventManager\LazyEventListenerTest::invalidTypes() is not static
> 
> /<>/test/LazyListenerTest.php:92
> 
> 9) 
> LaminasTest\EventManager\LazyListenerAggregateTest::testPassingInvalidListenerTypesAtInstantiationRaisesException
> Data Provider method 
> LaminasTest\EventManager\LazyListenerAggregateTest::invalidListenerTypes() is 
> not static
> 
> /<>/test/LazyListenerAggregateTest.php:74
> 
> 10) 
> LaminasTest\EventManager\LazyListenerAggregateTest::testPassingInvalidListenersAtInstantiationRaisesException
> Data Provider method 
> LaminasTest\EventManager\LazyListenerAggregateTest::invalidListeners() is not 
> static
> 
> /<>/test/LazyListenerAggregateTest.php:85
> 
> 11) 
> LaminasTest\EventManager\LazyListenerTest::testConstructorRaisesExceptionForInvalidListenerType
> Data Provider method 
> LaminasTest\EventManager\LazyListenerTest::invalidTypes() is not static
> 
> /<>/test/LazyListenerTest.php:63
> 
> 12) 
> LaminasTest\EventManager\LazyListenerTest::testConstructorRaisesExceptionForInvalidMethodType
> Data Provider method 
> LaminasTest\EventManager\LazyListenerTest::invalidTypes() is not static
> 
> /<>/test/LazyListenerTest.php:92
> 
> 13) 
> LaminasTest\EventManager\SharedEventManagerTest::testAttachRaisesExceptionForInvalidIdentifer
> Data Provider method 
> LaminasTest\EventManager\SharedEventManagerTest::invalidIdentifiers() is not 
> static
> 
> /<>/test/SharedEventManagerTest.php:68
> 
> 14) 
> LaminasTest\EventManager\SharedEventManagerTest::testAttachRaisesExceptionForInvalidEvent
> Data Provi

Bug#1039850: php-zend-stdlib: FTBFS with phpunit 10: make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-zend-stdlib
Version: 3.16.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-zend-stdlib was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner warning:
> 
> 1) Class LaminasTest\Stdlib\StringWrapper\CommonStringWrapperTest declared in 
> /<>/test/StringWrapper/CommonStringWrapperTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 30 tests triggered 30 PHPUnit deprecations:
> 
> 1) LaminasTest\Stdlib\ArrayUtilsTest::testFiltersArray
> Data Provider method LaminasTest\Stdlib\ArrayUtilsTest::filterArrays() is not 
> static
> 
> /<>/test/ArrayUtilsTest.php:569
> 
> 2) LaminasTest\Stdlib\GlobTest::testPatterns
> Data Provider method LaminasTest\Stdlib\GlobTest::patternsProvider() is not 
> static
> 
> /<>/test/GlobTest.php:65
> 
> 3) LaminasTest\Stdlib\GlobTest::testFlagsIsEqualsToMethod
> Data Provider method 
> LaminasTest\Stdlib\GlobTest::flagsIsEqualsToMethodDataProvider() is not static
> 
> /<>/test/GlobTest.php:137
> 
> 4) LaminasTest\Stdlib\StringUtilsTest::testIsSingleByteEncodingReturnsTrue
> Data Provider method 
> LaminasTest\Stdlib\StringUtilsTest::getSingleByEncodings() is not static
> 
> /<>/test/StringUtilsTest.php:58
> 
> 5) LaminasTest\Stdlib\StringUtilsTest::testIsSingleByteEncodingReturnsFalse
> Data Provider method 
> LaminasTest\Stdlib\StringUtilsTest::getNonSingleByteEncodings() is not static
> 
> /<>/test/StringUtilsTest.php:78
> 
> 6) LaminasTest\Stdlib\StringUtilsTest::testIsValidUtf8
> Data Provider method 
> LaminasTest\Stdlib\StringUtilsTest::getUtf8StringValidity() is not static
> 
> /<>/test/StringUtilsTest.php:160
> 
> 7) LaminasTest\Stdlib\StringWrapper\IconvTest::testStrlen
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IconvTest::strlenProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:44
> 
> 8) LaminasTest\Stdlib\StringWrapper\IconvTest::testSubstr
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IconvTest::substrProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:77
> 
> 9) LaminasTest\Stdlib\StringWrapper\IconvTest::testStrpos
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IconvTest::strposProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:109
> 
> 10) LaminasTest\Stdlib\StringWrapper\IconvTest::testConvert
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IconvTest::convertProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:145
> 
> 11) LaminasTest\Stdlib\StringWrapper\IconvTest::testWordWrap
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IconvTest::wordWrapProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:224
> 
> 12) LaminasTest\Stdlib\StringWrapper\IconvTest::testStrPad
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IconvTest::strPadProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:287
> 
> 13) LaminasTest\Stdlib\StringWrapper\IntlTest::testStrlen
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IntlTest::strlenProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:44
> 
> 14) LaminasTest\Stdlib\StringWrapper\IntlTest::testSubstr
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IntlTest::substrProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:77
> 
> 15) LaminasTest\Stdlib\StringWrapper\IntlTest::testStrpos
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IntlTest::strposProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:109
> 
> 16) LaminasTest\Stdlib\StringWrapper\IntlTest::testConvert
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IntlTest::convertProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:145
> 
> 17) LaminasTest\Stdlib\StringWrapper\IntlTest::testWordWrap
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IntlTest::wordWrapProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:224
> 
> 18) LaminasTest\Stdlib\StringWrapper\IntlTest::testStrPad
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\IntlTest::strPadProvider() is not static
> 
> /<>/test/StringWrapper/CommonStringWrapperTest.php:287
> 
> 19) LaminasTest\Stdlib\StringWrapper\MbStringTest::testStrlen
> Data Provider method 
> LaminasTest\Stdlib\StringWrapper\MbStringTest::strlenProvider() is not stati

Bug#1039848: php-zend-code: FTBFS with phpunit 10: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-zend-code
Version: 4.8.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-zend-code was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There was 1 error:
> 
> 1) 
> LaminasTest\Code\Generic\Prototype\PrototypeClassFactoryTest::testSetNameOnGenericIsCalledOnce
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/test/Generic/Prototype/PrototypeClassFactoryTest.php:48
> 
> --
> 
> There was 1 risky test:
> 
> 1) 
> LaminasTest\Code\Generic\Prototype\PrototypeClassFactoryTest::testSetNameOnGenericIsCalledOnce
> This test did not perform any assertions
> 
> /<>/test/Generic/Prototype/PrototypeClassFactoryTest.php:45
> 
> ERRORS!
> Tests: 1191, Assertions: 1724, Errors: 1, Deprecations: 1, Skipped: 3, Risky: 
> 1.
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-zend-code/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039847: php-webimpress-safe-writer: FTBFS with phpunit 10: make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-webimpress-safe-writer
Version: 2.2.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-webimpress-safe-writer was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> D.SF...   23 / 23 
> (100%)
> 
> Time: 00:06.461, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There was 1 failure:
> 
> 1) WebimpressTest\SafeWriter\FileWriterTest::testMultipleWriters with data 
> set "standard-writer"
> Response codes: []
> Reader errors: 
> Failed asserting that true is identical to false.
> 
> /<>/test/FileWriterTest.php:141
> 
> --
> 
> 4 tests triggered 4 PHPUnit deprecations:
> 
> 1) 
> WebimpressTest\SafeWriter\ExceptionTest::testExceptionIsInstanceOfExceptionInterface
> Data Provider method WebimpressTest\SafeWriter\ExceptionTest::exception() is 
> not static
> 
> /<>/test/ExceptionTest.php:43
> 
> 2) WebimpressTest\SafeWriter\ExceptionTest::testExceptionIsNotInstantiable
> Data Provider method WebimpressTest\SafeWriter\ExceptionTest::exception() is 
> not static
> 
> /<>/test/ExceptionTest.php:53
> 
> 3) WebimpressTest\SafeWriter\FileWriterTest::testCorrectChmodIsSet
> Data Provider method WebimpressTest\SafeWriter\FileWriterTest::permission() 
> is not static
> 
> /<>/test/FileWriterTest.php:61
> 
> 4) WebimpressTest\SafeWriter\FileWriterTest::testMultipleWriters
> Data Provider method WebimpressTest\SafeWriter\FileWriterTest::writer() is 
> not static
> 
> /<>/test/FileWriterTest.php:93
> 
> FAILURES!
> Tests: 23, Assertions: 36, Failures: 1, Deprecations: 5, Skipped: 1.
> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-webimpress-safe-writer/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039743: christianriesen-base32: FTBFS with phpunit 10: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2

[Adam D. Barratt]

On Wed, 2023-06-28 at 17:57 -0300, Athos Ribeiro wrote:
> Source: christianriesen-base32
> Version: 1.6.0-3
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: pkg-php-p...@lists.alioth.debian.org
> Usertags: phpunit
> 
> Hi,
> 
> We will start the phpunit 10 transition in unstable soon. During a
> test
> rebuild, christianriesen-base32 was found to FTBFS.

I've picked up an arbitrary bug from the set to reply to here. 

Transitions should be co-ordinated with the Release Team, and I can't
see a tracking bug or discussion for this one (or the related symfony
transition). Have I simply missed it?

FTBFS bugs relating to transitions should be filed at severities below
RC until the transition has actually started.

I'm not one of the team members who regularly handles transitions any
more, but looking at the list of bugs you have filed so far tonight,
any transition that introduces over 100 build failures in other
packages is in no sense ready to happen "soon".

Regards,

Adam

Bug#1039846: phpunit-recursion-context: FTBFS with phpunit 10: make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: phpunit-recursion-context
Version: 4.0.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, phpunit-recursion-context was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap src/autoload.php
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> FF...SSS  36 / 36 
> (100%)
> 
> Time: 00:00.010, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 14 failures:
> 
> 1) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #0
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, bool given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 2) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #1
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, bool given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 3) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #2
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, null given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 4) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #3
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, string given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 5) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #4
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, int given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 6) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #5
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, float given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 7) SebastianBergmann\RecursionContext\ContextTest::testAddFails with data set 
> #6
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::add(): Argument #1 ($value) must 
> be of type object|array, resource given, called in 
> /<>/tests/ContextTest.php on line 93" at
> /<>/tests/ContextTest.php:93
> .
> 
> 8) SebastianBergmann\RecursionContext\ContextTest::testContainsFails with 
> data set #0
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::contains(): Argument #1 ($value) 
> must be of type object|array, bool given, called in 
> /<>/tests/ContextTest.php on line 104" at
> /<>/tests/ContextTest.php:104
> .
> 
> 9) SebastianBergmann\RecursionContext\ContextTest::testContainsFails with 
> data set #1
> Failed asserting that exception of type "TypeError" matches expected 
> exception "SebastianBergmann\RecursionContext\Exception". Message was: 
> "SebastianBergmann\RecursionContext\Context::contains(): Argument #1 ($value) 
> must be of type object|array, bool giv

Bug#1039845: phpunit-object-enumerator: FTBFS with phpunit 10: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: phpunit-object-enumerator
Version: 4.0.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, phpunit-object-enumerator was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> ..10 / 10 
> (100%)
> 
> Time: 00:00.006, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 8 errors:
> 
> 1) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesSingleObject
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:35
> 
> 2) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesArrayWithSingleObject
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:45
> 
> 3) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesArrayWithTwoReferencesToTheSameObject
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:55
> 
> 4) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesArrayOfObjects
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:66
> 
> 5) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesObjectWithAggregatedObject
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:81
> 
> 6) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesObjectWithAggregatedObjectsInArray
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:95
> 
> 7) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesObjectsWithCyclicReferences
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:110
> 
> 8) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesClassThatThrowsException
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/EnumeratorTest.php:121
> 
> --
> 
> There were 8 risky tests:
> 
> 1) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesSingleObject
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:31
> 
> 2) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesArrayWithSingleObject
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:41
> 
> 3) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesArrayWithTwoReferencesToTheSameObject
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:51
> 
> 4) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesArrayOfObjects
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:61
> 
> 5) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesObjectWithAggregatedObject
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:73
> 
> 6) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesObjectWithAggregatedObjectsInArray
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:88
> 
> 7) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesObjectsWithCyclicReferences
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:102
> 
> 8) 
> SebastianBergmann\ObjectEnumerator\EnumeratorTest::testEnumeratesClassThatThrowsException
> This test did not perform any assertions
> 
> /<>/tests/unit/EnumeratorTest.php:117
> 
> ERRORS!
> Tests: 10, Assertions: 2, Errors: 8, Deprecations: 1, Risky: 8.
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/phpunit-object-enumerator/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039844: phpunit-global-state: FTBFS with phpunit 10: make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: phpunit-global-state
Version: 5.0.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, phpunit-global-state was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> ..E...26 / 26 
> (100%)
> 
> Time: 00:00.878, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There was 1 error:
> 
> 1) SebastianBergmann\GlobalState\SnapshotTest::testStaticAttributes
> Error: Call to undefined method 
> SebastianBergmann\ObjectReflector\ObjectReflector::getAttributes()
> 
> /<>/tests/unit/SnapshotTest.php:46
> 
> --
> 
> There was 1 risky test:
> 
> 1) SebastianBergmann\GlobalState\SnapshotTest::testStaticAttributes
> This test did not perform any assertions
> 
> /<>/tests/unit/SnapshotTest.php:40
> 
> ERRORS!
> Tests: 26, Assertions: 53, Errors: 1, Deprecations: 1, Risky: 1.
> make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/phpunit-global-state/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039843: phpunit-diff: FTBFS with phpunit 10: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: phpunit-diff
Version: 4.0.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, phpunit-diff was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> D..  63 / 314 ( 
> 20%)
> ... 126 / 314 ( 
> 40%)
> ... 189 / 314 ( 
> 60%)
> ... 252 / 314 ( 
> 80%)
> ..  314 / 314 
> (100%)
> 
> Time: 00:03.376, Memory: 71.10 MB
> 
> There was 1 PHPUnit test runner warning:
> 
> 1) Class SebastianBergmann\Diff\LongestCommonSubsequenceTest declared in 
> /<>/tests/LongestCommonSubsequenceTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 27 tests triggered 31 PHPUnit deprecations:
> 
> 1) 
> SebastianBergmann\Diff\DifferTest::testArrayRepresentationOfDiffCanBeRenderedUsingTimeEfficientLcsImplementation
> Data Provider method SebastianBergmann\Diff\DifferTest::arrayProvider() is 
> not static
> 
> /<>/tests/DifferTest.php:43
> 
> 2) 
> SebastianBergmann\Diff\DifferTest::testTextRepresentationOfDiffCanBeRenderedUsingTimeEfficientLcsImplementation
> Data Provider method SebastianBergmann\Diff\DifferTest::textProvider() is not 
> static
> 
> /<>/tests/DifferTest.php:51
> 
> 3) 
> SebastianBergmann\Diff\DifferTest::testArrayRepresentationOfDiffCanBeRenderedUsingMemoryEfficientLcsImplementation
> Data Provider method SebastianBergmann\Diff\DifferTest::arrayProvider() is 
> not static
> 
> /<>/tests/DifferTest.php:62
> 
> 4) 
> SebastianBergmann\Diff\DifferTest::testTextRepresentationOfDiffCanBeRenderedUsingMemoryEfficientLcsImplementation
> Data Provider method SebastianBergmann\Diff\DifferTest::textProvider() is not 
> static
> 
> /<>/tests/DifferTest.php:70
> 
> 5) SebastianBergmann\Diff\DifferTest::testSplitStringByLines
> Data Provider method 
> SebastianBergmann\Diff\DifferTest::provideSplitStringByLinesCases() is not 
> static
> 
> /<>/tests/DifferTest.php:342
> 
> 6) 
> SebastianBergmann\Diff\Output\AbstractChunkOutputBuilderTest::testGetCommonChunks
> Data Provider method 
> SebastianBergmann\Diff\Output\AbstractChunkOutputBuilderTest::provideGetCommonChunks()
>  is not static
> 
> /<>/tests/Output/AbstractChunkOutputBuilderTest.php:27
> 
> 7) 
> SebastianBergmann\Diff\Output\DiffOnlyOutputBuilderTest::testDiffDoNotShowNonDiffLines
> Data Provider method 
> SebastianBergmann\Diff\Output\DiffOnlyOutputBuilderTest::textForNoNonDiffLinesProvider()
>  is not static
> 
> /<>/tests/Output/DiffOnlyOutputBuilderTest.php:26
> 
> 8) 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::testIntegrationUsingPHPFileInVendorGitApply
> Data Provider method 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::provideFilePairs()
>  is not static
> 
> /<>/tests/Output/Integration/StrictUnifiedDiffOutputBuilderIntegrationTest.php:82
> 
> 9) 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::testIntegrationUsingPHPFileInVendorPatch
> Data Provider method 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::provideFilePairs()
>  is not static
> 
> /<>/tests/Output/Integration/StrictUnifiedDiffOutputBuilderIntegrationTest.php:109
> 
> 10) 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::testIntegrationOfUnitTestCasesGitApply
> * Data Provider method 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::provideOutputBuildingCases()
>  is not static
> 
> * Data Provider method 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::provideSample()
>  is not static
> 
> * Data Provider method 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::provideBasicDiffGeneration()
>  is not static
> 
> /<>/tests/Output/Integration/StrictUnifiedDiffOutputBuilderIntegrationTest.php:131
> 
> 11) 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::testIntegrationOfUnitTestCasesPatch
> * Data Provider method 
> SebastianBergmann\Diff\Output\StrictUnifiedDiffOutputBuilderIntegrationTest::provideOutputBuildingCases()
>  is not static
> 
> * D

Bug#1039841: php-twig: FTBFS with phpunit 10: PHP Fatal error: Trait "PHPUnit\Framework\TestListenerDefaultImplementation" not found in /usr/share/php/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListen

[Athos Ribeiro]

Source: php-twig
Version: 3.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-twig was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> SYMFONY_DEPRECATIONS_HELPER=weak phpunit
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /usr/share/php/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php on 
> line 26
> make[1]: *** [debian/rules:90: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-twig/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039842: phpunit-comparator: FTBFS with phpunit 10: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: phpunit-comparator
Version: 4.0.8-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, phpunit-comparator was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 2 PHPUnit errors:
> 
> 1) 
> SebastianBergmann\Comparator\MockObjectComparatorTest::testAssertEqualsSucceeds
> The data provider specified for 
> SebastianBergmann\Comparator\MockObjectComparatorTest::testAssertEqualsSucceeds
>  is invalid
> Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/MockObjectComparatorTest.php:58
> 
> 2) 
> SebastianBergmann\Comparator\MockObjectComparatorTest::testAssertEqualsFails
> The data provider specified for 
> SebastianBergmann\Comparator\MockObjectComparatorTest::testAssertEqualsFails 
> is invalid
> Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/MockObjectComparatorTest.php:73
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 45 tests triggered 45 PHPUnit deprecations:
> 
> 1) SebastianBergmann\Comparator\ArrayComparatorTest::testAcceptsFails
> Data Provider method 
> SebastianBergmann\Comparator\ArrayComparatorTest::acceptsFailsProvider() is 
> not static
> 
> /<>/tests/ArrayComparatorTest.php:137
> 
> 2) SebastianBergmann\Comparator\ArrayComparatorTest::testAssertEqualsSucceeds
> Data Provider method 
> SebastianBergmann\Comparator\ArrayComparatorTest::assertEqualsSucceedsProvider()
>  is not static
> 
> /<>/tests/ArrayComparatorTest.php:147
> 
> 3) SebastianBergmann\Comparator\ArrayComparatorTest::testAssertEqualsFails
> Data Provider method 
> SebastianBergmann\Comparator\ArrayComparatorTest::assertEqualsFailsProvider() 
> is not static
> 
> /<>/tests/ArrayComparatorTest.php:162
> 
> 4) SebastianBergmann\Comparator\DOMNodeComparatorTest::testAcceptsSucceeds
> Data Provider method 
> SebastianBergmann\Comparator\DOMNodeComparatorTest::acceptsSucceedsProvider() 
> is not static
> 
> /<>/tests/DOMNodeComparatorTest.php:127
> 
> 5) SebastianBergmann\Comparator\DOMNodeComparatorTest::testAcceptsFails
> Data Provider method 
> SebastianBergmann\Comparator\DOMNodeComparatorTest::acceptsFailsProvider() is 
> not static
> 
> /<>/tests/DOMNodeComparatorTest.php:137
> 
> 6) 
> SebastianBergmann\Comparator\DOMNodeComparatorTest::testAssertEqualsSucceeds
> Data Provider method 
> SebastianBergmann\Comparator\DOMNodeComparatorTest::assertEqualsSucceedsProvider()
>  is not static
> 
> /<>/tests/DOMNodeComparatorTest.php:147
> 
> 7) SebastianBergmann\Comparator\DOMNodeComparatorTest::testAssertEqualsFails
> Data Provider method 
> SebastianBergmann\Comparator\DOMNodeComparatorTest::assertEqualsFailsProvider()
>  is not static
> 
> /<>/tests/DOMNodeComparatorTest.php:164
> 
> 8) SebastianBergmann\Comparator\DateTimeComparatorTest::testAcceptsFails
> Data Provider method 
> SebastianBergmann\Comparator\DateTimeComparatorTest::acceptsFailsProvider() 
> is not static
> 
> /<>/tests/DateTimeComparatorTest.php:166
> 
> 9) 
> SebastianBergmann\Comparator\DateTimeComparatorTest::testAssertEqualsSucceeds
> Data Provider method 
> SebastianBergmann\Comparator\DateTimeComparatorTest::assertEqualsSucceedsProvider()
>  is not static
> 
> /<>/tests/DateTimeComparatorTest.php:176
> 
> 10) SebastianBergmann\Comparator\DateTimeComparatorTest::testAssertEqualsFails
> Data Provider method 
> SebastianBergmann\Comparator\DateTimeComparatorTest::assertEqualsFailsProvider()
>  is not static
> 
> /<>/tests/DateTimeComparatorTest.php:191
> 
> 11) SebastianBergmann\Comparator\DoubleComparatorTest::testAcceptsSucceeds
> Data Provider method 
> SebastianBergmann\Comparator\DoubleComparatorTest::acceptsSucceedsProvider() 
> is not static
> 
> /<>/tests/DoubleComparatorTest.php:94
> 
> 12) SebastianBergmann\Comparator\DoubleComparatorTest::testAcceptsFails
> Data Provider method 
> SebastianBergmann\Comparator\DoubleComparatorTest::acceptsFailsProvider() is 
> not static
> 
> /<>/tests/DoubleComparatorTest.php:104
> 
> 13) 
> SebastianBergmann\Comparator\DoubleComparatorTest::testAssertEqualsSucceeds
> Data Provider method 
> SebastianBergmann\Comparator\DoubleComparatorTest::assertEqualsSucceedsProvider()
>  is not static
> 
> /<>/tests/DoubleComparatorTest.php:114
> 
> 14) SebastianBergmann\Comparator\DoubleComparatorTest::testAssertEqualsFails
> Data Provider method 
> SebastianBergmann\Comparator\DoubleComparatorTest::assertEqualsFailsProvider()
>  is not static
> 
> /<>/tests/DoubleComparatorTest.php:129
> 
> 15) SebastianBergmann\Comparator\

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

[Dirk Eddelbuettel]

Feel free to change the severity back if you truly think it is that serious.

Some of the autopkgtests may be stumbling about the graphics API change and
may need a rebuild of packages interfacing it:  svglite, ggplot2, ragg,
tikzdevice.  As some of these are widely used the rest may be repercussions.
There is also the usual mess with the (bulk ?) update of BioConductor which
generally releases a few weeks after R and did so again.

I maintain that r-base is fine.  I have no control over how other people use
my package, and if all other maintainers put breaking autopkgtests in well
yes then they do hold r-base hostage and it will take "forever" to migrate to
testing.  We have been there before.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1024129: ITP: tacacs+ -- TACACS+ authentication daemon

[Daniel Gröber]

Hi Pawel,

I'm also interested in having tacacs+ available in Debian. I wanted to test
your packages but unfortunately mentors removes packages after a while and
so they are gone from there now.

The git repo you linked to doesn't seem to contain debian packaging. Could
you re-upload to mentors or push your packaging/debian branch?

Thanks,
--Daniel

Bug#1039840: php-tijsverkoyen-css-to-inline-styles: FTBFS with phpunit 10: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-tijsverkoyen-css-to-inline-styles
Version: 2.2.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-tijsverkoyen-css-to-inline-styles was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap src/autoload.php
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> . 45 / 45 
> (100%)
> 
> Time: 00:00.016, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner warning:
> 
> 1) Class RuleTest cannot be found in 
> /<>/tests/Css/Rule/RuleTest.php
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> WARNINGS!
> Tests: 45, Assertions: 94, Warnings: 1, Deprecations: 1.
> make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-tijsverkoyen-css-to-inline-styles/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039839: php-text-password: FTBFS with phpunit 10: make[1]: *** [debian/rules:6: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-text-password
Version: 1.2.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-text-password was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd Text_Password-* && \
> phpunit --do-not-cache-result tests
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> 
> E...  20 / 20 
> (100%)
> 
> Time: 00:00.006, Memory: 6.00 MB
> 
> There were 5 errors:
> 
> 1) Text_Password_Test::testCreateNumericWithLength
> Error: Call to undefined method Text_Password_Test::assertRegExp()
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:78
> 
> 2) Text_Password_Test::testCreateFromABCWithLength
> Error: Call to undefined method Text_Password_Test::assertRegExp()
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:84
> 
> 3) Text_Password_Test::testCreateAlphabeticWithLength
> Error: Call to undefined method Text_Password_Test::assertRegExp()
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:91
> 
> 4) Text_Password_Test::testCreateUnpronouncableWithAllClasses
> Error: Call to undefined method Text_Password_Test::assertRegExp()
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:97
> 
> 5) Text_Password_Test::testCreateUnpronouncableShortWithAllClasses
> Error: Call to undefined method Text_Password_Test::assertRegExp()
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:113
> 
> --
> 
> There were 5 risky tests:
> 
> 1) Text_Password_Test::testCreateNumericWithLength
> This test did not perform any assertions
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:74
> 
> 2) Text_Password_Test::testCreateFromABCWithLength
> This test did not perform any assertions
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:81
> 
> 3) Text_Password_Test::testCreateAlphabeticWithLength
> This test did not perform any assertions
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:87
> 
> 4) Text_Password_Test::testCreateUnpronouncableWithAllClasses
> This test did not perform any assertions
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:94
> 
> 5) Text_Password_Test::testCreateUnpronouncableShortWithAllClasses
> This test did not perform any assertions
> 
> /<>/Text_Password-1.2.1/tests/Text_Password_Test.php:110
> 
> ERRORS!
> Tests: 20, Assertions: 23, Errors: 5, Risky: 5.
> make[1]: *** [debian/rules:6: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-text-password/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039838: php-symfony-security-acl: FTBFS with phpunit 10: PHP Fatal error: Trait "PHPUnit\Framework\TestListenerDefaultImplementation" not found in /usr/share/php/Symfony/Bridge/PhpUnit/Legacy/Sym

[Athos Ribeiro]

Source: php-symfony-security-acl
Version: 3.3.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-symfony-security-acl was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpabtpl composer.json > debian/autoload.php.tpl
> phpab \
>   --output autoload.php \
>   --template debian/autoload.php.tpl \
>   --blacklist '*\\tests\\*' \
>   .
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory .
> 
> Autoload file autoload.php generated.
> 
> mkdir --parents Symfony/Component/Security vendor
> phpabtpl \
>   --require doctrine/common \
>   --require doctrine/dbal \
>   --require symfony/cache \
>   --require symfony/phpunit-bridge \
>   --require symfony/security-acl \
>   > debian/autoload.tests.php.tpl
> Proceeding without a composer.json file.phpab \
>   --output vendor/autoload.php \
>   --template debian/autoload.tests.php.tpl \
>   Tests
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory Tests
> 
> Autoload file vendor/autoload.php generated.
> 
> ln -s ../../.. Symfony/Component/Security/Acl
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> SYMFONY_DEPRECATIONS_HELPER=weak phpunit
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /usr/share/php/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php on 
> line 26
> make[1]: *** [debian/rules:27: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-symfony-security-acl/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039837: php-symfony-polyfill: FTBFS with phpunit 10: make[1]: *** [debian/rules:53: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-symfony-polyfill
Version: 1.27.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-symfony-polyfill was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 5 PHPUnit test runner warnings:
> 
> 1) Class Symfony\Polyfill\Tests\Intl\Icu\AbstractCollatorTest declared in 
> /<>/tests/Intl/Icu/AbstractCollatorTest.php is abstract
> 
> 2) Class Symfony\Polyfill\Tests\Intl\Icu\AbstractIcuTest declared in 
> /<>/tests/Intl/Icu/AbstractIcuTest.php is abstract
> 
> 3) Class Symfony\Polyfill\Tests\Intl\Icu\AbstractIntlDateFormatterTest 
> declared in /<>/tests/Intl/Icu/AbstractIntlDateFormatterTest.php 
> is abstract
> 
> 4) Class Symfony\Polyfill\Tests\Intl\Icu\AbstractLocaleTest declared in 
> /<>/tests/Intl/Icu/AbstractLocaleTest.php is abstract
> 
> 5) Class Symfony\Polyfill\Tests\Intl\Icu\AbstractNumberFormatterTest declared 
> in /<>/tests/Intl/Icu/AbstractNumberFormatterTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There was 1 error:
> 
> 1) Symfony\Polyfill\Tests\Iconv\IconvTest::testIconvMimeDecodeIllegal
> Error: Call to undefined method 
> Symfony\Polyfill\Tests\Iconv\IconvTest::expectNotice()
> 
> /<>/tests/Iconv/IconvTest.php:137
> 
> --
> 
> There were 3 failures:
> 
> 1) Symfony\Polyfill\Tests\Php83\Php83Test::testInvalidOptionsProvided with 
> data set #0
> Failed asserting that exception of type "Error" matches expected exception 
> "ValueError". Message was: "Call to undefined method 
> Symfony\Polyfill\Tests\Php83\Php83Test::expectErrorMessage()" at
> /<>/tests/Php83/Php83Test.php:66
> .
> 
> 2) Symfony\Polyfill\Tests\Php83\Php83Test::testInvalidOptionsProvided with 
> data set #1
> Failed asserting that exception of type "Error" matches expected exception 
> "ValueError". Message was: "Call to undefined method 
> Symfony\Polyfill\Tests\Php83\Php83Test::expectErrorMessage()" at
> /<>/tests/Php83/Php83Test.php:66
> .
> 
> 3) Symfony\Polyfill\Tests\Php83\Php83Test::testInvalidOptionsProvided with 
> data set #2
> Failed asserting that exception of type "Error" matches expected exception 
> "ValueError". Message was: "Call to undefined method 
> Symfony\Polyfill\Tests\Php83\Php83Test::expectErrorMessage()" at
> /<>/tests/Php83/Php83Test.php:66
> .
> 
> --
> 
> 145 tests triggered 145 PHPUnit deprecations:
> 
> 1) Symfony\Polyfill\Tests\Ctype\CtypeTest::testValidCtypeAlnum
> Data Provider method 
> Symfony\Polyfill\Tests\Ctype\CtypeTest::provideValidAlnums() is not static
> 
> /<>/tests/Ctype/CtypeTest.php:24
> 
> 2) Symfony\Polyfill\Tests\Ctype\CtypeTest::testInvalidCtypeAlnum
> Data Provider method 
> Symfony\Polyfill\Tests\Ctype\CtypeTest::provideInvalidAlnum() is not static
> 
> /<>/tests/Ctype/CtypeTest.php:47
> 
> 3) Symfony\Polyfill\Tests\Ctype\CtypeTest::testValidCtypeAlpha
> Data Provider method 
> Symfony\Polyfill\Tests\Ctype\CtypeTest::provideValidAlphas() is not static
> 
> /<>/tests/Ctype/CtypeTest.php:79
> 
...
> 
> --
> 
> There was 1 risky test:
> 
> 1) Symfony\Polyfill\Tests\Iconv\IconvTest::testIconvMimeDecodeIllegal
> This test did not perform any assertions
> 
> /<>/tests/Iconv/IconvTest.php:134
> 
> ERRORS!
> Tests: 20611, Assertions: 403536, Errors: 1, Failures: 3, Warnings: 5, 
> Deprecations: 320, Skipped: 87, Risky: 1.
> make[1]: *** [debian/rules:53: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-symfony-polyfill/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039836: php-symfony-contracts: FTBFS with phpunit 10: make[1]: *** [debian/rules:56: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-symfony-contracts
Version: 2.5.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-symfony-contracts was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner warning:
> 
> 1) Class Symfony\Contracts\Service\Test\ServiceLocatorTest declared in 
> /<>/Service/Test/ServiceLocatorTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 4 errors:
> 
> 1) Symfony\Contracts\Tests\Cache\CacheTraitTest::testSave
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/Tests/Cache/CacheTraitTest.php:37
> 
> 2) Symfony\Contracts\Tests\Cache\CacheTraitTest::testNoCallbackCallOnHit
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/Tests/Cache/CacheTraitTest.php:63
> 
> 3) Symfony\Contracts\Tests\Cache\CacheTraitTest::testRecomputeOnBetaInf
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/Tests/Cache/CacheTraitTest.php:94
> 
> 4) Symfony\Contracts\Tests\Cache\CacheTraitTest::testExceptionOnNegativeBeta
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/Tests/Cache/CacheTraitTest.php:114
> 
> --
> 
> 9 tests triggered 9 PHPUnit deprecations:
> 
> 1) Symfony\Contracts\Translation\Test\TranslatorTest::testTrans
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getTransTests() is not 
> static
> 
> /<>/Translation/Test/TranslatorTest.php:59
> 
> 2) 
> Symfony\Contracts\Translation\Test\TranslatorTest::testTransChoiceWithExplicitLocale
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getTransChoiceTests() is 
> not static
> 
> /<>/Translation/Test/TranslatorTest.php:69
> 
> 3) 
> Symfony\Contracts\Translation\Test\TranslatorTest::testTransChoiceWithDefaultLocale
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getTransChoiceTests() is 
> not static
> 
> /<>/Translation/Test/TranslatorTest.php:81
> 
> 4) 
> Symfony\Contracts\Translation\Test\TranslatorTest::testTransChoiceWithEnUsPosix
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getTransChoiceTests() is 
> not static
> 
> /<>/Translation/Test/TranslatorTest.php:91
> 
> 5) Symfony\Contracts\Translation\Test\TranslatorTest::testInterval
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getInternal() is not static
> 
> /<>/Translation/Test/TranslatorTest.php:145
> 
> 6) Symfony\Contracts\Translation\Test\TranslatorTest::testChoose
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getChooseTests() is not 
> static
> 
> /<>/Translation/Test/TranslatorTest.php:170
> 
> 7) 
> Symfony\Contracts\Translation\Test\TranslatorTest::testThrowExceptionIfMatchingMessageCannotBeFound
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::getNonMatchingMessages() 
> is not static
> 
> /<>/Translation/Test/TranslatorTest.php:187
> 
> 8) Symfony\Contracts\Translation\Test\TranslatorTest::testFailedLangcodes
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::failingLangcodes() is not 
> static
> 
> /<>/Translation/Test/TranslatorTest.php:301
> 
> 9) Symfony\Contracts\Translation\Test\TranslatorTest::testLangcodes
> Data Provider method 
> Symfony\Contracts\Translation\Test\TranslatorTest::successLangcodes() is not 
> static
> 
> /<>/Translation/Test/TranslatorTest.php:310
> 
> --
> 
> There were 4 risky tests:
> 
> 1) Symfony\Contracts\Tests\Cache\CacheTraitTest::testSave
> This test did not perform any assertions
> 
> /<>/Tests/Cache/CacheTraitTest.php:24
> 
> 2) Symfony\Contracts\Tests\Cache\CacheTraitTest::testNoCallbackCallOnHit
> This test did not perform any assertions
> 
> /<>/Tests/Cache/CacheTraitTest.php:53
> 
> 3) Symfony\Contracts\Tests\Cache\CacheTraitTest::testRecomputeOnBetaInf
> This test did not perform any assertions
> 
> /<>/Tests/Cache/CacheTraitTest.php:80
> 
> 4) Symfony\Contracts\Tests\Cache\CacheTraitTest::testExceptionOnNegativeBeta
> This test did not perform any assertions
> 
> /<>/Tests/Cache/CacheTraitTest.php:111
> 
> ERRORS!
> Tests: 104, Assertions: 127, Errors: 4, Warnings: 1, Deprecations: 10, Risky: 
> 4.
> make[1]: *** [debian/rules:56: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-s

Bug#1039835: php-slim-psr7: FTBFS with phpunit 10: unsatisfiable build-dependency: phpunit (< 10~~) but 10.2.2-1 is to be installed

[Athos Ribeiro]

Source: php-slim-psr7
Version: 1.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-slim-psr7 was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> php-fig-http-message-util, php-getallheaders, php-phpspec-prophecy, 
> php-phpspec-prophecy-phpunit, php-psr-http-factory, php-psr-http-message, 
> php-symfony-polyfill-php80, phpab, phpunit, pkg-php-tools (>= 1.41~), 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> php-fig-http-message-util, php-getallheaders, php-phpspec-prophecy, 
> php-phpspec-prophecy-phpunit, php-psr-http-factory, php-psr-http-message, 
> php-symfony-polyfill-php80, phpab, phpunit, pkg-php-tools (>= 1.41~), 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [854 B]
> Get:5 copy:/<>/apt_archive ./ Packages [886 B]
> Fetched 2349 B in 0s (0 B/s)
> Reading package lists...
> Get:1 file:/<>/resolver-jwAYFd/apt_archive ./ InRelease
> Ign:1 file:/<>/resolver-jwAYFd/apt_archive ./ InRelease
> Get:2 file:/<>/resolver-jwAYFd/apt_archive ./ Release [609 B]
> Get:2 file:/<>/resolver-jwAYFd/apt_archive ./ Release [609 B]
> Get:3 file:/<>/resolver-jwAYFd/apt_archive ./ Release.gpg
> Ign:3 file:/<>/resolver-jwAYFd/apt_archive ./ Release.gpg
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  php-phpspec-prophecy-phpunit : Depends: phpunit (< 10~~) but 10.2.2-1 is to 
> be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-slim-psr7/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039834: php-slim: FTBFS with phpunit 10: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-slim
Version: 3.12.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-slim was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 3 PHPUnit test runner warnings:
> 
> 1) Class CallableTest cannot be found in 
> /<>/tests/Mocks/CallableTest.php
> 
> 2) Class InvocationStrategyTest cannot be found in 
> /<>/tests/Mocks/InvocationStrategyTest.php
> 
> 3) Class InvokableTest cannot be found in 
> /<>/tests/Mocks/InvokableTest.php
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 13 errors:
> 
> 1) Slim\Tests\AppTest::testInvokeWithPimpleCallable
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/AppTest.php:1617
> 
> 2) Slim\Tests\AppTest::testRespondIndeterminateLength
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/AppTest.php:2086
> 
> 3) Slim\Tests\AppTest::testExceptionErrorHandlerDoesNotDisplayErrorDetails
> Error: Call to undefined method Slim\Tests\AppTest::assertNotRegExp()
> 
> /<>/tests/AppTest.php:2238
> 
> 4) Slim\Tests\AppTest::testExceptionPhpErrorHandlerDoesNotDisplayErrorDetails
> Error: Call to undefined method Slim\Tests\AppTest::assertNotRegExp()
> 
> /<>/tests/AppTest.php:2277
> 
> 5) Slim\Tests\AppTest::testExceptionErrorHandlerDisplaysErrorDetails
> Error: Call to undefined method Slim\Tests\AppTest::assertRegExp()
> 
> /<>/tests/AppTest.php:2475
> 
> 6) Slim\Tests\DeferredCallableTest::testItBindsClosuresToContainer
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/DeferredCallableTest.php:30
> 
> 7) Slim\Tests\Handlers\ErrorTest::testPreviousException
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/Handlers/ErrorTest.php:90
> 
> 8) Slim\Tests\Handlers\NotAllowedTest::testNotFoundContentType
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/Handlers/NotAllowedTest.php:63
> 
> 9) Slim\Tests\Handlers\NotFoundTest::testNotFoundContentType
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/Handlers/NotFoundTest.php:50
> 
> 10) Slim\Tests\Handlers\PhpErrorTest::testNotFoundContentType
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/Handlers/PhpErrorTest.php:76
> 
> 11) Slim\Tests\Http\RequestTest::testGetRequestTargetWithSlimPsr7Uri
> Error: Call to undefined method Slim\Tests\Http\RequestTest::prophesize()
> 
> /<>/tests/Http/RequestTest.php:458
> /usr/bin/phpunit:74
> 
> 12) Slim\Tests\Http\RequestTest::testGetRequestTargetWithNonSlimPsr7Uri
> Error: Call to undefined method Slim\Tests\Http\RequestTest::prophesize()
> 
> /<>/tests/Http/RequestTest.php:477
> /usr/bin/phpunit:74
> 
> 13) Slim\Tests\Http\UploadedFilesTest::testMoveToStream
> Error: Call to undefined method 
> Slim\Tests\Http\UploadedFilesTest::assertFileNotExists()
> 
> /<>/tests/Http/UploadedFilesTest.php:231
> /usr/bin/phpunit:74
> 
> --
> 
> There were 2 failures:
> 
> 1) Slim\Tests\ContainerTest::testGetWithErrorThrownByFactoryClosure
> Failed asserting that exception of type "Error" matches expected exception 
> "InvalidArgumentException". Message was: "Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()" at
> /<>/tests/ContainerTest.php:76
> .
> 
> 2) Slim\Tests\Handlers\ErrorTest::testNotFoundContentType
> Failed asserting that exception of type "Error" matches expected exception 
> "UnexpectedValueException". Message was: "Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()" at
> /<>/tests/Handlers/ErrorTest.php:73
> .
> 
> --
> 
> 10 tests triggered 10 PHPUnit deprecations:
> 
> 1) Slim\Tests\Handlers\ErrorTest::testError
> Data Provider method Slim\Tests\Handlers\ErrorTest::errorProvider() is not 
> static
> 
> /<>/tests/Handlers/ErrorTest.php:39
> 
> 2) Slim\Tests\Handlers\ErrorTest::testErrorDisplayDetails
> Data Provider method Slim\Tests\Handlers\ErrorTest::errorProvider() is not 
> static
> 
> /<>/tests/Handlers/ErrorTest.php:57
> 
> 3) Slim\Tests\Handlers\NotAllowedTest::testInvalidMethod
> Data Provider method 
> Slim\Tests\Handlers\NotAllowedTest::invalidMethodProvider() is not static
> 
> /<>/tests/Handlers/NotAllowedTest.php:35
> 
> 4) Slim\Tests\Handlers\NotFoundTest::testNotFound
> Data Provider method Slim\Tests\Hand

Bug#1039833: php-seld-signal-handler: FTBFS with phpunit 10: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-seld-signal-handler
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-seld-signal-handler was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit -v
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> ESE..E10 / 10 
> (100%)
> 
> Time: 00:00.009, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 3 errors:
> 
> 1) Seld\Signal\SignalHandlerTest::testLoggingAndDefault
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/SignalHandlerTest.php:21
> 
> 2) Seld\Signal\SignalHandlerTest::testAutoGCOnPHP8
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/SignalHandlerTest.php:66
> 
> 3) Seld\Signal\SignalHandlerTest::testNestingWorks
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/SignalHandlerTest.php:140
> 
> --
> 
> There were 3 risky tests:
> 
> 1) Seld\Signal\SignalHandlerTest::testLoggingAndDefault
> This test did not perform any assertions
> 
> /<>/tests/SignalHandlerTest.php:14
> 
> 2) Seld\Signal\SignalHandlerTest::testAutoGCOnPHP8
> This test did not perform any assertions
> 
> /<>/tests/SignalHandlerTest.php:60
> 
> 3) Seld\Signal\SignalHandlerTest::testNestingWorks
> This test did not perform any assertions
> 
> /<>/tests/SignalHandlerTest.php:134
> 
> ERRORS!
> Tests: 10, Assertions: 6, Errors: 3, Deprecations: 1, Skipped: 5, Risky: 3.
> make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-seld-signal-handler/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039832: phpseclib: FTBFS with phpunit 10: PHP Fatal error: Cannot override final method PHPUnit\Framework\Assert::assertIsArray() in /<>/tests/PhpseclibTestCase.php on line 106

[Athos Ribeiro]

Source: phpseclib
Version: 1.0.20-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, phpseclib was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpabtpl --basedir phpseclib composer.json > debian/autoload.php.tpl
> phpab \
>   --output phpseclib/phpseclib.autoloader.php \
>   --template debian/autoload.php.tpl \
>   phpseclib
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory phpseclib
> 
> Autoload file phpseclib/phpseclib.autoloader.php generated.
> 
> cp phpseclib/bootstrap.php phpseclib/phpseclib.bootstrap.php
> mkdir --parents vendor
> phpabtpl \
>   --require phpseclib/phpseclib \
>   > debian/autoload.test.php.tpl
> Proceeding without a composer.json file.phpab \
>   --output vendor/autoload.php \
>   --template debian/autoload.test.php.tpl \
> tests
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory tests
> 
> Autoload file vendor/autoload.php generated.
> 
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> phpunit --include-path phpseclib --bootstrap vendor/autoload.php
> PHP Fatal error:  Cannot override final method 
> PHPUnit\Framework\Assert::assertIsArray() in 
> /<>/tests/PhpseclibTestCase.php on line 106
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/phpseclib/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039831: php-sabre-xml: FTBFS with phpunit 10: make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255

[Athos Ribeiro]

Source: php-sabre-xml
Version: 1.4.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-sabre-xml was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --configuration tests/phpunit.xml.dist
> 
> 
> An error occurred inside PHPUnit.
> 
> Message:  Class "PHPUnit_Framework_TestCase" not found
> Location: /<>/tests/Sabre/Xml/ContextStackTest.php:12
> 
> #0 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(112): require_once()
> #1 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(47): 
> PHPUnit\Runner\TestSuiteLoader->loadSuiteClassFile()
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(244): 
> PHPUnit\Runner\TestSuiteLoader->load()
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(261): 
> PHPUnit\Framework\TestSuite->addTestFile()
> #4 /usr/share/php/PHPUnit/TextUI/Configuration/Xml/TestSuiteMapper.php(77): 
> PHPUnit\Framework\TestSuite->addTestFiles()
> #5 /usr/share/php/PHPUnit/TextUI/Configuration/TestSuiteBuilder.php(58): 
> PHPUnit\TextUI\XmlConfiguration\TestSuiteMapper->map()
> #6 /usr/share/php/PHPUnit/TextUI/Application.php(348): 
> PHPUnit\TextUI\Configuration\TestSuiteBuilder->build()
> #7 /usr/share/php/PHPUnit/TextUI/Application.php(102): 
> PHPUnit\TextUI\Application->buildTestSuite()
> #8 /usr/bin/phpunit(74): PHPUnit\TextUI\Application->run()
> #9 {main}
> make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-sabre-xml/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039830: php-sabre-vobject: FTBFS with phpunit 10: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-sabre-vobject
Version: 2.1.7-6.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-sabre-vobject was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 2 PHPUnit test runner warnings:
> 
> 1) Class ICalendarTest cannot be found in 
> /<>/tests/Sabre/VObject/Splitter/ICalendarTest.php
> 
> 2) Class VCardTest cannot be found in 
> /<>/tests/Sabre/VObject/Splitter/VCardTest.php
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 7 tests triggered 7 PHPUnit deprecations:
> 
> 1) Sabre\VObject\Component\VAlarmTest::testInTimeRange
> Data Provider method Sabre\VObject\Component\VAlarmTest::timeRangeTestData() 
> is not static
> 
> /<>/tests/Sabre/VObject/Component/VAlarmTest.php:14
> 
> 2) Sabre\VObject\Component\VCalendarTest::testExpand
> Data Provider method Sabre\VObject\Component\VCalendarTest::expandData() is 
> not static
> 
> /<>/tests/Sabre/VObject/Component/VCalendarTest.php:12
> 
> 3) Sabre\VObject\Component\VCardTest::testValidate
> Data Provider method Sabre\VObject\Component\VCardTest::validateData() is not 
> static
> 
> /<>/tests/Sabre/VObject/Component/VCardTest.php:12
> 
> 4) Sabre\VObject\Component\VEventTest::testInTimeRange
> Data Provider method Sabre\VObject\Component\VEventTest::timeRangeTestData() 
> is not static
> 
> /<>/tests/Sabre/VObject/Component/VEventTest.php:12
> 
> 5) Sabre\VObject\Component\VJournalTest::testInTimeRange
> Data Provider method 
> Sabre\VObject\Component\VJournalTest::timeRangeTestData() is not static
> 
> /<>/tests/Sabre/VObject/Component/VJournalTest.php:12
> 
> 6) Sabre\VObject\Component\VTodoTest::testInTimeRange
> Data Provider method Sabre\VObject\Component\VTodoTest::timeRangeTestData() 
> is not static
> 
> /<>/tests/Sabre/VObject/Component/VTodoTest.php:12
> 
> 7) Sabre\VObject\TimezoneUtilTest::testCorrectTZ
> Data Provider method Sabre\VObject\TimezoneUtilTest::getMapping() is not 
> static
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:10
> 
> --
> 
> There were 279 risky tests:
> 
> 1) Sabre\VObject\PropertyTest::testParameterNotExists
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/PropertyTest.php:46
> 
> 2) Sabre\VObject\RecurrenceIteratorFifthTuesdayProblemTest::testGetDTEnd
> This test did not perform any assertions
> 


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-sabre-vobject/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039829: php-sabre-uri: FTBFS with phpunit 10: make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255

[Athos Ribeiro]

Source: php-sabre-uri
Version: 1.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-sabre-uri was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --configuration tests/phpunit.xml.dist --bootstrap lib/autoload.php
> 
> 
> An error occurred inside PHPUnit.
> 
> Message:  Class "PHPUnit_Framework_TestCase" not found
> Location: /<>/tests/BuildTest.php:5
> 
> #0 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(112): require_once()
> #1 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(47): 
> PHPUnit\Runner\TestSuiteLoader->loadSuiteClassFile()
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(244): 
> PHPUnit\Runner\TestSuiteLoader->load()
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(261): 
> PHPUnit\Framework\TestSuite->addTestFile()
> #4 /usr/share/php/PHPUnit/TextUI/Configuration/Xml/TestSuiteMapper.php(77): 
> PHPUnit\Framework\TestSuite->addTestFiles()
> #5 /usr/share/php/PHPUnit/TextUI/Configuration/TestSuiteBuilder.php(58): 
> PHPUnit\TextUI\XmlConfiguration\TestSuiteMapper->map()
> #6 /usr/share/php/PHPUnit/TextUI/Application.php(348): 
> PHPUnit\TextUI\Configuration\TestSuiteBuilder->build()
> #7 /usr/share/php/PHPUnit/TextUI/Application.php(102): 
> PHPUnit\TextUI\Application->buildTestSuite()
> #8 /usr/bin/phpunit(74): PHPUnit\TextUI\Application->run()
> #9 {main}
> make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-sabre-uri/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039828: php-sabre-http: FTBFS with phpunit 10: make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255

[Athos Ribeiro]

Source: php-sabre-http
Version: 4.2.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-sabre-http was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --configuration tests/phpunit.xml
> 
> 
> An error occurred inside PHPUnit.
> 
> Message:  Class "PHPUnit_Framework_TestCase" not found
> Location: /<>/tests/HTTP/Auth/AWSTest.php:8
> 
> #0 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(112): require_once()
> #1 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(47): 
> PHPUnit\Runner\TestSuiteLoader->loadSuiteClassFile()
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(244): 
> PHPUnit\Runner\TestSuiteLoader->load()
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(261): 
> PHPUnit\Framework\TestSuite->addTestFile()
> #4 /usr/share/php/PHPUnit/TextUI/Configuration/Xml/TestSuiteMapper.php(77): 
> PHPUnit\Framework\TestSuite->addTestFiles()
> #5 /usr/share/php/PHPUnit/TextUI/Configuration/TestSuiteBuilder.php(58): 
> PHPUnit\TextUI\XmlConfiguration\TestSuiteMapper->map()
> #6 /usr/share/php/PHPUnit/TextUI/Application.php(348): 
> PHPUnit\TextUI\Configuration\TestSuiteBuilder->build()
> #7 /usr/share/php/PHPUnit/TextUI/Application.php(102): 
> PHPUnit\TextUI\Application->buildTestSuite()
> #8 /usr/bin/phpunit(74): PHPUnit\TextUI\Application->run()
> #9 {main}
> make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-sabre-http/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039827: php-sabre-event: FTBFS with phpunit 10: make[1]: *** [debian/rules:10: override_dh_auto_test] Error 255

[Athos Ribeiro]

Source: php-sabre-event
Version: 3.0.0~as2.0.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-sabre-event was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap lib/autoload.php
> 
> 
> An error occurred inside PHPUnit.
> 
> Message:  Class "PHPUnit_Framework_TestCase" not found
> Location: /<>/tests/ContinueCallbackTest.php:5
> 
> #0 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(112): require_once()
> #1 /usr/share/php/PHPUnit/Runner/TestSuiteLoader.php(47): 
> PHPUnit\Runner\TestSuiteLoader->loadSuiteClassFile()
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(244): 
> PHPUnit\Runner\TestSuiteLoader->load()
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(261): 
> PHPUnit\Framework\TestSuite->addTestFile()
> #4 /usr/share/php/PHPUnit/TextUI/Configuration/Xml/TestSuiteMapper.php(77): 
> PHPUnit\Framework\TestSuite->addTestFiles()
> #5 /usr/share/php/PHPUnit/TextUI/Configuration/TestSuiteBuilder.php(58): 
> PHPUnit\TextUI\XmlConfiguration\TestSuiteMapper->map()
> #6 /usr/share/php/PHPUnit/TextUI/Application.php(348): 
> PHPUnit\TextUI\Configuration\TestSuiteBuilder->build()
> #7 /usr/share/php/PHPUnit/TextUI/Application.php(102): 
> PHPUnit\TextUI\Application->buildTestSuite()
> #8 /usr/bin/phpunit(74): PHPUnit\TextUI\Application->run()
> #9 {main}
> make[1]: *** [debian/rules:10: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-sabre-event/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039563: qa.debian.org: Procedure needed to report mishandled bug reports

[Bart Martens]

On Tue, Jun 27, 2023 at 10:30:53AM +0200, debbug@sideload.33mail.com wrote:
> Debian bugs are mishandled too often, which suggests there is no
> oversight of mishandled cases. I have an example at hand:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026922
> 
> A valid, credible bug report was tagged “wontfix”, which in itself is
> often fair enough but in this case the action /should/ have been to
> mirror the bug report upstream because upstream is the source of the
> bug. “wontfix” would only be sensible if the source of the bug was in
> the debian pkging & the Debian maintainer opts not to fix it in
> Debian.

This is an example of different opinions about bug >< feature.

Quoting from 1026922:
> Directing users to report bugs upstream goes against Debian
> conventions. It’s the duty of the maintainer to mirror bugs upstream:
>   https://www.debian.org/Bugs/Reporting

This text is about preventing duplicate effort.

I understand your frustration. I doubt however that wrapping 1026922 in a
request for addressing mishandled bugs would be helpful.

Cheers,

Bart

Bug#1039826: php-sabredav: FTBFS with phpunit 10: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-sabredav
Version: 1.8.12-10
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-sabredav was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 11 PHPUnit test runner warnings:
> 
> 1) Class Sabre\CalDAV\Backend\AbstractPDOTest declared in 
> /<>/tests/Sabre/CalDAV/Backend/AbstractPDOTest.php is abstract
> 
> 2) Class Sabre\CardDAV\AbstractPluginTest declared in 
> /<>/tests/Sabre/CardDAV/AbstractPluginTest.php is abstract
> 
> 3) Class Sabre\CardDAV\Backend\AbstractPDOTest declared in 
> /<>/tests/Sabre/CardDAV/Backend/AbstractPDOTest.php is abstract
> 
> 4) Class SupportedAddressDataTest cannot be found in 
> /<>/tests/Sabre/CardDAV/Property/SupportedAddressDataTest.php
> 
> 5) Class SogoStripContentTypeTest cannot be found in 
> /<>/tests/Sabre/CardDAV/SogoStripContentTypeTest.php
> 
> 6) Class Sabre\DAV\Auth\Backend\AbstractPDOTest declared in 
> /<>/tests/Sabre/DAV/Auth/Backend/AbstractPDOTest.php is abstract
> 
> 7) Class Sabre\DAV\Locks\Backend\AbstractTest declared in 
> /<>/tests/Sabre/DAV/Locks/Backend/AbstractTest.php is abstract
> 
> 8) Class ServerPreconditionTest cannot be found in 
> /<>/tests/Sabre/DAV/ServerPreconditionTest.php
> 
> 9) Class NeedPrivilegesExceptionTest cannot be found in 
> /<>/tests/Sabre/DAVACL/Exception/NeedPrivilegesExceptionTest.php
> 
> 10) Class Sabre\DAVACL\PrincipalBackend\AbstractPDOTest declared in 
> /<>/tests/Sabre/DAVACL/PrincipalBackend/AbstractPDOTest.php is 
> abstract
> 
> 11) Class Sabre\DAVServerTest declared in 
> /<>/tests/Sabre/DAVServerTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 10 tests triggered 10 PHPUnit deprecations:
> 
> 1) Sabre\CalDAV\CalendarQueryValidatorTest::testValid
> Data Provider method Sabre\CalDAV\CalendarQueryValidatorTest::provider() is 
> not static
> 
> /<>/tests/Sabre/CalDAV/CalendarQueryValidatorTest.php:12
> 
> 2) Sabre\CalDAV\Notifications\Notification\InviteReplyTest::testSerializers
> Data Provider method 
> Sabre\CalDAV\Notifications\Notification\InviteReplyTest::dataProvider() is 
> not static
> 
> /<>/tests/Sabre/CalDAV/Notifications/Notification/InviteReplyTest.php:13
> 
> 3) Sabre\CalDAV\Notifications\Notification\InviteTest::testSerializers
> Data Provider method 
> Sabre\CalDAV\Notifications\Notification\InviteTest::dataProvider() is not 
> static
> 
> /<>/tests/Sabre/CalDAV/Notifications/Notification/InviteTest.php:13
> 
> 4) Sabre\CalDAV\Notifications\Notification\SystemStatusTest::testSerializers
> Data Provider method 
> Sabre\CalDAV\Notifications\Notification\SystemStatusTest::dataProvider() is 
> not static
> 
> /<>/tests/Sabre/CalDAV/Notifications/Notification/SystemStatusTest.php:13
> 
> 5) Sabre\CalDAV\Property\ScheduleCalendarTranspTest::testSerialize
> Data Provider method 
> Sabre\CalDAV\Property\ScheduleCalendarTranspTest::values() is not static
> 
> /<>/tests/Sabre/CalDAV/Property/ScheduleCalendarTranspTest.php:37
> 
> 6) Sabre\CalDAV\Property\ScheduleCalendarTranspTest::testUnserializer
> Data Provider method 
> Sabre\CalDAV\Property\ScheduleCalendarTranspTest::values() is not static
> 
> /<>/tests/Sabre/CalDAV/Property/ScheduleCalendarTranspTest.php:66
> 
> 7) Sabre\CardDAV\ValidateFilterTest::testFilter
> Data Provider method Sabre\CardDAV\ValidateFilterTest::data() is not static
> 
> /<>/tests/Sabre/CardDAV/ValidateFilterTest.php:12
> 
> 8) Sabre\DAV\ClientTest::testSpecificHTTPErrors
> Data Provider method Sabre\DAV\ClientTest::supportedHTTPCodes() is not static
> 
> /<>/tests/Sabre/DAV/ClientTest.php:491
> 
> 9) Sabre\DAV\PartialUpdate\SpecificationTest::testUpdateRange
> Data Provider method Sabre\DAV\PartialUpdate\SpecificationTest::data() is not 
> static
> 
> /<>/tests/Sabre/DAV/PartialUpdate/SpecificationTest.php:43
> 
> 10) Sabre\DAV\StringUtilTest::testTextMatch
> Data Provider method Sabre\DAV\StringUtilTest::dataset() is not static
> 
> /<>/tests/Sabre/DAV/StringUtilTest.php:10
> 
> WARNINGS!
> Tests: 1176, Assertions: 2175, Warnings: 11, Deprecations: 11, Skipped: 54.
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-sabredav/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039825: php-roundcube-rtf-html-php: FTBFS with phpunit 10: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-roundcube-rtf-html-php
Version: 2.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-roundcube-rtf-html-php was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap src/autoload.php tests
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> 
> ...   11 / 11 
> (100%)
> 
> Time: 00:00.011, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner warning:
> 
> 1) Class FontFamilyTest cannot be found in 
> /<>/tests/FontFamilyTest.php
> 
> WARNINGS!
> Tests: 11, Assertions: 11, Warnings: 1.
> make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-roundcube-rtf-html-php/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039821: php-pimple: FTBFS with phpunit 10: PHP Fatal error: Trait "PHPUnit\Framework\TestListenerDefaultImplementation" not found in /usr/share/php/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsList

[Athos Ribeiro]

Source: php-pimple
Version: 3.5.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-pimple was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpabtpl composer.json > debian/autoload.php.tpl
> phpab \
>   --output src/Pimple/autoload.php \
>   --blacklist 'pimple\\tests\\*' \
>   --template debian/autoload.php.tpl \
>   src/Pimple
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory src/Pimple
> 
> Autoload file src/Pimple/autoload.php generated.
> 
> mkdir --parents vendor
> phpabtpl \
>   --require symfony/phpunit-bridge \
>   composer.json > debian/autoload.tests.php.tpl
> phpab \
>   --output vendor/autoload.php \
>   --template debian/autoload.tests.php.tpl \
>   --basedir vendor \
>   src/Pimple
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory src/Pimple
> 
> Autoload file vendor/autoload.php generated.
> 
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> SYMFONY_DEPRECATIONS_HELPER=weak phpunit
> PHP Fatal error:  Trait "PHPUnit\Framework\TestListenerDefaultImplementation" 
> not found in 
> /usr/share/php/Symfony/Bridge/PhpUnit/Legacy/SymfonyTestsListenerForV7.php on 
> line 26
> make[1]: *** [debian/rules:23: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-pimple/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039822: php-proxy-manager: FTBFS with phpunit 10: make[1]: *** [debian/rules:27: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-proxy-manager
Version: 2.11.1+1.0.14-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-proxy-manager was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There were 2 PHPUnit errors:
> 
> 1) 
> ProxyManagerTest\Functional\FatalPreventionFunctionalTest::testCodeGeneration
> The data provider specified for 
> ProxyManagerTest\Functional\FatalPreventionFunctionalTest::testCodeGeneration 
> is invalid
> Empty data set provided by data provider
> 
> /<>/tests/ProxyManagerTest/Functional/FatalPreventionFunctionalTest.php:51
> 
> 2) 
> ProxyManagerTest\Functional\MultipleProxyGenerationTest::testCanGenerateMultipleDifferentProxiesForSameClass
> The data provider specified for 
> ProxyManagerTest\Functional\MultipleProxyGenerationTest::testCanGenerateMultipleDifferentProxiesForSameClass
>  is invalid
> Too few arguments to function PHPUnit\Framework\TestCase::__construct(), 0 
> passed in 
> /<>/tests/ProxyManagerTest/Functional/MultipleProxyGenerationTest.php
>  on line 116 and exactly 1 expected
> 
> /<>/tests/ProxyManagerTest/Functional/MultipleProxyGenerationTest.php:62
> 
> --
> 
> There were 4 PHPUnit test runner warnings:
> 
> 1) No tests found in class 
> "ProxyManagerTest\Functional\FatalPreventionFunctionalTest".
> 
> 2) No tests found in class 
> "ProxyManagerTest\Functional\MultipleProxyGenerationTest".
> 
> 3) Class ProxyManagerTest\ProxyGenerator\AbstractProxyGeneratorTest declared 
> in 
> /<>/tests/ProxyManagerTest/ProxyGenerator/AbstractProxyGeneratorTest.php
>  is abstract
> 
> 4) Class 
> ProxyManagerTest\ProxyGenerator\PropertyGenerator\AbstractUniquePropertyNameTest
>  declared in 
> /<>/tests/ProxyManagerTest/ProxyGenerator/PropertyGenerator/AbstractUniquePropertyNameTest.php
>  is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 5 errors:
> 
> 1) 
> ProxyManagerTest\Factory\RemoteObject\Adapter\BaseAdapterTest::testBaseAdapter
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/ProxyManagerTest/Factory/RemoteObject/Adapter/BaseAdapterTest.php:29
> 
> 2) 
> ProxyManagerTest\Factory\RemoteObject\Adapter\BaseAdapterTest::testBaseAdapterWithServiceMap
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/ProxyManagerTest/Factory/RemoteObject/Adapter/BaseAdapterTest.php:63
> 
> 3) 
> ProxyManagerTest\Factory\RemoteObject\Adapter\JsonRpcTest::testCanBuildAdapterWithJsonRpcClient
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/ProxyManagerTest/Factory/RemoteObject/Adapter/JsonRpcTest.php:26
> 
> 4) 
> ProxyManagerTest\Factory\RemoteObject\Adapter\SoapTest::testCanBuildAdapterWithSoapRpcClient
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/ProxyManagerTest/Factory/RemoteObject/Adapter/SoapTest.php:26
> 
> 5) 
> ProxyManagerTest\Factory\RemoteObject\Adapter\XmlRpcTest::testCanBuildAdapterWithXmlRpcClient
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/ProxyManagerTest/Factory/RemoteObject/Adapter/XmlRpcTest.php:26
> 
> --
> 
> There was 1 failure:
> 
> 1) 
> ProxyManagerTest\GeneratorStrategy\FileWriterGeneratorStrategyTest::testGenerateWillFailIfTmpFileCannotBeWrittenToDisk
> Failed asserting that exception of type 
> "ProxyManager\Exception\FileNotWritableException" is thrown.
> 
> --
> 
> 67 tests triggered 67 PHPUnit deprecations:
> 
> 1) 
> ProxyManagerTest\Functional\AccessInterceptorScopeLocalizerFunctionalTest::testPropertyReadAccess
> Data Provider method 
> ProxyManagerTest\Functional\AccessInterceptorScopeLocalizerFunctionalTest::getPropertyAccessProxies()
>  is not static
> 
> /<>/tests/ProxyManagerTest/Functional/AccessInterceptorScopeLocalizerFunctionalTest.php:215
> 
> 2) 
> ProxyManagerTest\Functional\AccessInterceptorScopeLocalizerFunctionalTest::testPropertyWriteAccess
> Data Provider method 
> ProxyManagerTest\Functional\AccessInterceptorScopeLocalizerFunctionalTest::getPropertyAccessProxies()
>  is not static
> 
> /<>/tests/ProxyManagerTest/Functional/AccessInterceptorScopeLocalizerFunctionalTest.php:228
> 
> 3) 
> ProxyManagerTest\Functional\AccessInterceptorScopeLocalizerFunctionalTest::testPropertyExistence
> Data Provider method 
> ProxyManagerTest\Functional\AccessInterceptorScopeLocalizerFunctionalTest::getPropertyAccessProxies()
>  is not static
> 
> /<>/tests/Pr

Bug#1039823: php-ramsey-collection: FTBFS with phpunit 10: unsatisfiable build-dependency: phpunit (< 10~~) but 10.2.2-1 is to be installed

[Athos Ribeiro]

Source: php-ramsey-collection
Version: 1.2.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-ramsey-collection was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> php-faker, php-mockery, php-phpspec-prophecy-phpunit, phpab, phpunit, 
> pkg-php-tools (>= 1.41~), build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-phpcomposer, 
> php-faker, php-mockery, php-phpspec-prophecy-phpunit, phpab, phpunit, 
> pkg-php-tools (>= 1.41~), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [782 B]
> Get:5 copy:/<>/apt_archive ./ Packages [770 B]
> Fetched 2161 B in 0s (0 B/s)
> Reading package lists...
> Get:1 file:/<>/resolver-Gs6m3s/apt_archive ./ InRelease
> Ign:1 file:/<>/resolver-Gs6m3s/apt_archive ./ InRelease
> Get:2 file:/<>/resolver-Gs6m3s/apt_archive ./ Release [609 B]
> Get:2 file:/<>/resolver-Gs6m3s/apt_archive ./ Release [609 B]
> Get:3 file:/<>/resolver-Gs6m3s/apt_archive ./ Release.gpg
> Ign:3 file:/<>/resolver-Gs6m3s/apt_archive ./ Release.gpg
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  php-phpspec-prophecy-phpunit : Depends: phpunit (< 10~~) but 10.2.2-1 is to 
> be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-ramsey-collection/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039824: php-react-promise: FTBFS with phpunit 10: make[1]: *** [debian/rules:25: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-react-promise
Version: 2.9.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-react-promise was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 6 errors:
> 
> 1) React\Promise\DeferredTest::notifyShouldAllowResolveAfterProgress
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:238
> 
> 2) React\Promise\DeferredTest::notifyShouldAllowRejectAfterProgress
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:260
> 
> 3) React\Promise\LazyPromiseTest::notifyShouldAllowResolveAfterProgress
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:238
> 
> 4) React\Promise\LazyPromiseTest::notifyShouldAllowRejectAfterProgress
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:260
> 
> 5) React\Promise\PromiseTest::notifyShouldAllowResolveAfterProgress
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:238
> 
> 6) React\Promise\PromiseTest::notifyShouldAllowRejectAfterProgress
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\Builder\InvocationMocker::withConsecutive()
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:260
> 
> --
> 
> There were 6 risky tests:
> 
> 1) React\Promise\DeferredTest::notifyShouldAllowResolveAfterProgress
> This test did not perform any assertions
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:233
> 
> 2) React\Promise\DeferredTest::notifyShouldAllowRejectAfterProgress
> This test did not perform any assertions
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:255
> 
> 3) React\Promise\LazyPromiseTest::notifyShouldAllowResolveAfterProgress
> This test did not perform any assertions
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:233
> 
> 4) React\Promise\LazyPromiseTest::notifyShouldAllowRejectAfterProgress
> This test did not perform any assertions
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:255
> 
> 5) React\Promise\PromiseTest::notifyShouldAllowResolveAfterProgress
> This test did not perform any assertions
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:233
> 
> 6) React\Promise\PromiseTest::notifyShouldAllowRejectAfterProgress
> This test did not perform any assertions
> 
> /<>/tests/PromiseTest/NotifyTestTrait.php:255
> 
> ERRORS!
> Tests: 576, Assertions: 955, Errors: 6, Deprecations: 1, Risky: 6.
> make[1]: *** [debian/rules:25: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-react-promise/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039820: php-phpstan-phpdoc-parser: FTBFS with phpunit 10: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-phpstan-phpdoc-parser
Version: 1.16.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-phpstan-phpdoc-parser was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 7 tests triggered 36 PHPUnit deprecations:
> 
> 1) PHPStan\PhpDocParser\Parser\ConstExprParserTest::testParse
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideTrueNodeParseData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideFalseNodeParseData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideNullNodeParseData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideIntegerNodeParseData()
>  is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideFloatNodeParseData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideStringNodeParseData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideArrayNodeParseData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideFetchNodeParseData() 
> is not static
> 
> /<>/tests/PHPStan/Parser/ConstExprParserTest.php:46
> 
> 2) PHPStan\PhpDocParser\Parser\ConstExprParserTest::testParseWithTrimStrings
> Data Provider method 
> PHPStan\PhpDocParser\Parser\ConstExprParserTest::provideWithTrimStringsStringNodeParseData()
>  is not static
> 
> /<>/tests/PHPStan/Parser/ConstExprParserTest.php:364
> 
> 3) PHPStan\PhpDocParser\Parser\FuzzyTest::testTypeParser
> Data Provider method 
> PHPStan\PhpDocParser\Parser\FuzzyTest::provideTypeParserData() is not static
> 
> /<>/tests/PHPStan/Parser/FuzzyTest.php:39
> 
> 4) PHPStan\PhpDocParser\Parser\FuzzyTest::testConstExprParser
> Data Provider method 
> PHPStan\PhpDocParser\Parser\FuzzyTest::provideConstExprParserData() is not 
> static
> 
> /<>/tests/PHPStan/Parser/FuzzyTest.php:59
> 
> 5) PHPStan\PhpDocParser\Parser\PhpDocParserTest::testParse
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideTagsWithNumbers() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideSpecializedTags() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideParamTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideTypelessParamTagsData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideVarTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideReturnTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideThrowsTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideMixinTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideDeprecatedTagsData() is 
> not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::providePropertyTagsData() is 
> not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideMethodTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideSingleLinePhpDocData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideMultiLinePhpDocData() is 
> not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideTemplateTagsData() is 
> not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideExtendsTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideTypeAliasTagsData() is 
> not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideTypeAliasImportTagsData()
>  is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideAssertTagsData() is not 
> static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Parser\PhpDocParserTest::provideRealWorldExampleData() 
> is not static
> 
> * Data Provider method 
> PHPStan\PhpDocParser\Pars

Bug#1039819: php-phpspec-prophecy-phpunit: FTBFS with phpunit 10: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-phpspec-prophecy-phpunit
Version: 2.0.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-phpspec-prophecy-phpunit was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> F   5 / 5 
> (100%)
> 
> Time: 00:00.094, Memory: 6.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 5 failures:
> 
> 1) /<>/tests/MockFailure.phpt
> Failed asserting that string matches format description.
> --- Expected
> +++ Actual
> @@ @@
> -PHPUnit %s
> -
> -F %s 1 / 1 (100%)
> -
> -Time: %s
> -
> -There was 1 failure:
> -
> -1) Prophecy\PhpUnit\Tests\Fixtures\MockFailure::testMethod
> -Some predictions failed:
> -Double\DateTime\P1:
> -  Expected exactly 2 calls that match:
> -  Double\DateTime\P1->format(exact("Y-m-d"))
> -but 1 were made:
> -  - format("Y-m-d") @ fixtures/MockFailure.php:%d
> -
> -%s/ProphecyTrait.php:%d
> -%s/tests/run_test.php:%d
> -
> -FAILURES!
> -Tests: 1, Assertions: 1, Failures: 1.
> +Fatal error: Uncaught Error: Class "PHPUnit\TextUI\Command" not found in 
> /<>/tests/run_test.php:17
> +Stack trace:
> +#0 Standard input code(5): Prophecy\PhpUnit\Tests\runTest()
> +#1 {main}
> +  thrown in /<>/tests/run_test.php on line 17
> 
> /<>/tests/MockFailure.phpt:10
> 
> 2) /<>/tests/NoProphecy.phpt
> Failed asserting that string matches format description.
> --- Expected
> +++ Actual
> @@ @@
> -PHPUnit %s
> -
> -. %s 1 / 1 (100%)
> -
> -Time: %s
> -
> -OK (1 test, 1 assertion)
> +Fatal error: Uncaught Error: Class "PHPUnit\TextUI\Command" not found in 
> /<>/tests/run_test.php:17
> +Stack trace:
> +#0 Standard input code(5): Prophecy\PhpUnit\Tests\runTest()
> +#1 {main}
> +  thrown in /<>/tests/run_test.php on line 17
> 
> /<>/tests/NoProphecy.phpt:10
> 
> 3) /<>/tests/SpyFailure.phpt
> Failed asserting that string matches format description.
> --- Expected
> +++ Actual
> @@ @@
> -PHPUnit %s
> -
> -F %s 1 / 1 (100%)
> -
> -Time: %a
> -
> -There was 1 failure:
> -
> -1) Prophecy\PhpUnit\Tests\Fixtures\SpyFailure::testMethod
> -No calls have been made that match:
> -  Double\DateTime\P1->format(exact("Y-m-d"))
> -but expected at least one.
> -
> -%s/tests/run_test.php:%d
> -
> -FAILURES!
> -Tests: 1, Assertions: 1, Failures: 1.
> +Fatal error: Uncaught Error: Class "PHPUnit\TextUI\Command" not found in 
> /<>/tests/run_test.php:17
> +Stack trace:
> +#0 Standard input code(5): Prophecy\PhpUnit\Tests\runTest()
> +#1 {main}
> +  thrown in /<>/tests/run_test.php on line 17
> 
> /<>/tests/SpyFailure.phpt:10
> 
> 4) /<>/tests/Success.phpt
> Failed asserting that string matches format description.
> --- Expected
> +++ Actual
> @@ @@
> -PHPUnit %s
> -
> -. %s 1 / 1 (100%)
> -
> -Time: %s
> -
> -OK (1 test, 1 assertion)
> +Fatal error: Uncaught Error: Class "PHPUnit\TextUI\Command" not found in 
> /<>/tests/run_test.php:17
> +Stack trace:
> +#0 Standard input code(5): Prophecy\PhpUnit\Tests\runTest()
> +#1 {main}
> +  thrown in /<>/tests/run_test.php on line 17
> 
> /<>/tests/Success.phpt:10
> 
> 5) /<>/tests/WrongCall.phpt
> Failed asserting that string matches format description.
> --- Expected
> +++ Actual
> @@ @@
> -PHPUnit %s
> -
> -E %s 1 / 1 (100%)
> -
> -Time: %a
> -
> -There was 1 error:
> -
> -1) Prophecy\PhpUnit\Tests\Fixtures\WrongCall::testMethod
> -Prophecy\Exception\Doubler\MethodNotFoundException: Method 
> `Double\stdClass\P1::talk()` is not defined.
> -
> -%a%s/fixtures/WrongCall.php:%d
> -%s/tests/run_test.php:%d
> -
> -ERRORS!
> -Tests: 1, Assertions: 0, Errors: 1.
> +Fatal error: Uncaught Error: Class "PHPUnit\TextUI\Command" not found in 
> /<>/tests/run_test.php:17
> +Stack trace:
> +#0 Standard input code(5): Prophecy\PhpUnit\Tests\runTest()
> +#1 {main}
> +  thrown in /<>/tests/run_test.php on line 17
> 
> /<>/tests/WrongCall.phpt:10
> 
> FAILURES!
> Tests: 5, Assertions: 5, Failures: 5, Deprecations: 1.
> make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-phpspec-prophecy-phpunit/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039818: php-phpspec-prophecy: FTBFS with phpunit 10: PHP Warning: require_once(Doctrine/Instantiator/autoload.php): Failed to open stream: No such file or directory in /<>/src/Prophe

[Athos Ribeiro]

Source: php-phpspec-prophecy
Version: 1.17.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-phpspec-prophecy was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHP Warning:  require_once(Doctrine/Instantiator/autoload.php): Failed to 
> open stream: No such file or directory in 
> /<>/src/Prophecy/autoload.php on line 4
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Error in bootstrap script: Error:
> Failed opening required 'Doctrine/Instantiator/autoload.php' 
> (include_path='.:/usr/share/php')
> #0 /<>/vendor/autoload.php(4): require_once()
> #1 /usr/share/php/PHPUnit/TextUI/Application.php(291): include_once('...')
> #2 /usr/share/php/PHPUnit/TextUI/Application.php(97): 
> PHPUnit\TextUI\Application->loadBootstrapScript()
> #3 /usr/bin/phpunit(74): PHPUnit\TextUI\Application->run()
> #4 {main}
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-phpspec-prophecy/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039817: php-phpseclib: FTBFS with phpunit 10: make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-phpseclib
Version: 2.0.44-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-phpseclib was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There was 1 failure:
> 
> 1) Functional_Net_SFTPUserStoryTest::testBadHostname
> Failed asserting that exception of type "PHPUnit\Framework\Error\Notice" is 
> thrown.
> 
> --
> 
> 17 tests triggered 17 PHPUnit deprecations:
> 
> 1) Unit_Crypt_AES_McryptTest::testEncryptDecryptWithContinuousBuffer
> Data Provider method Unit_Crypt_AES_McryptTest::continuousBufferCombos() is 
> not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:79
> 
> 2) Unit_Crypt_AES_McryptTest::testContinuousBufferBattery
> Data Provider method 
> Unit_Crypt_AES_McryptTest::continuousBufferBatteryCombos() is not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:178
> 
> 3) Unit_Crypt_AES_McryptTest::testNonContinuousBufferBattery
> Data Provider method 
> Unit_Crypt_AES_McryptTest::continuousBufferBatteryCombos() is not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:225
> 
> 4) Unit_Crypt_AES_OpenSSLTest::testEncryptDecryptWithContinuousBuffer
> Data Provider method Unit_Crypt_AES_OpenSSLTest::continuousBufferCombos() is 
> not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:79
> 
> 5) Unit_Crypt_AES_OpenSSLTest::testContinuousBufferBattery
> Data Provider method 
> Unit_Crypt_AES_OpenSSLTest::continuousBufferBatteryCombos() is not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:178
> 
> 6) Unit_Crypt_AES_OpenSSLTest::testNonContinuousBufferBattery
> Data Provider method 
> Unit_Crypt_AES_OpenSSLTest::continuousBufferBatteryCombos() is not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:225
> 
> 7) Unit_Crypt_AES_PurePHPTest::testEncryptDecryptWithContinuousBuffer
> Data Provider method Unit_Crypt_AES_PurePHPTest::continuousBufferCombos() is 
> not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:79
> 
> 8) Unit_Crypt_AES_PurePHPTest::testContinuousBufferBattery
> Data Provider method 
> Unit_Crypt_AES_PurePHPTest::continuousBufferBatteryCombos() is not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:178
> 
> 9) Unit_Crypt_AES_PurePHPTest::testNonContinuousBufferBattery
> Data Provider method 
> Unit_Crypt_AES_PurePHPTest::continuousBufferBatteryCombos() is not static
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:225
> 
> 10) Unit_Crypt_BlowfishTest::testVectors
> Data Provider method Unit_Crypt_BlowfishTest::engineVectors() is not static
> 
> /<>/tests/Unit/Crypt/BlowfishTest.php:75
> 
> 11) Unit_Crypt_RC2Test::testVectors
> Data Provider method Unit_Crypt_RC2Test::engineVectors() is not static
> 
> /<>/tests/Unit/Crypt/RC2Test.php:111
> 
> 12) Unit_Crypt_RC4Test::testVectors
> Data Provider method Unit_Crypt_RC4Test::engineVectors() is not static
> 
> /<>/tests/Unit/Crypt/RC4Test.php:202
> 
> 13) Unit_Crypt_RandomTest::testStringLength
> Data Provider method Unit_Crypt_RandomTest::stringLengthData() is not static
> 
> /<>/tests/Unit/Crypt/RandomTest.php:22
> 
> 14) Unit_Crypt_TripleDESTest::testVectors
> Data Provider method Unit_Crypt_TripleDESTest::engineVectors() is not static
> 
> /<>/tests/Unit/Crypt/TripleDESTest.php:105
> 
> 15) Unit_Crypt_TripleDESTest::testVectorsWithIV
> Data Provider method Unit_Crypt_TripleDESTest::engineIVVectors() is not static
> 
> /<>/tests/Unit/Crypt/TripleDESTest.php:156
> 
> 16) Unit_Net_SSH1Test::testFormatLog
> Data Provider method Unit_Net_SSH1Test::formatLogDataProvider() is not static
> 
> /<>/tests/Unit/Net/SSH1Test.php:30
> 
> 17) Unit_Net_SSH2UnitTest::testFormatLog
> Data Provider method Unit_Net_SSH2UnitTest::formatLogDataProvider() is not 
> static
> 
> /<>/tests/Unit/Net/SSH2UnitTest.php:33
> 
> --
> 
> There were 302 risky tests:
> 
> 1) Unit_Crypt_AES_McryptTest::testNonContinuousBufferBattery with data set #0
> This test did not perform any assertions
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:225
> 
> 2) Unit_Crypt_AES_McryptTest::testNonContinuousBufferBattery with data set #1
> This test did not perform any assertions
> 
> /<>/tests/Unit/Crypt/AES/TestCase.php:225
> 
> 3) Unit_Crypt_AES_McryptTest::testNonContinuousBufferBattery with data set #2
> This test did not perform any assertions
> 

The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-phpseclib/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039816: php-phpoption: FTBFS with phpunit 10: make[1]: *** [debian/rules:12: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-phpoption
Version: 1.8.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-phpoption was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit -v --include-path src --bootstrap src/PhpOption/autoload.php
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> .R..  56 / 56 
> (100%)
> 
> Time: 00:00.012, Memory: 8.00 MB
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There were 12 errors:
> 
> 1) PhpOption\Tests\LazyOptionTest::testGetWithArgumentsAndConstructor
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 2) PhpOption\Tests\LazyOptionTest::testGetWithArgumentsAndCreate
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 3) PhpOption\Tests\LazyOptionTest::testGetWithoutArgumentsAndConstructor
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 4) PhpOption\Tests\LazyOptionTest::testGetWithoutArgumentsAndCreate
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 5) PhpOption\Tests\LazyOptionTest::testCallbackReturnsNull
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 6) 
> PhpOption\Tests\LazyOptionTest::testExceptionIsThrownIfCallbackReturnsNonOption
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 7) PhpOption\Tests\LazyOptionTest::testInvalidCallbackAndConstructor
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 8) PhpOption\Tests\LazyOptionTest::testInvalidCallbackAndCreate
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 9) PhpOption\Tests\LazyOptionTest::testifDefined
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 10) PhpOption\Tests\LazyOptionTest::testForAll
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 11) PhpOption\Tests\LazyOptionTest::testOrElse
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> 12) PhpOption\Tests\LazyOptionTest::testFoldLeftRight
> Error: Call to undefined method 
> PHPUnit\Framework\MockObject\MockBuilder::setMethods()
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:22
> 
> --
> 
> There were 12 risky tests:
> 
> 1) PhpOption\Tests\LazyOptionTest::testGetWithArgumentsAndConstructor
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:26
> 
> 2) PhpOption\Tests\LazyOptionTest::testGetWithArgumentsAndCreate
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:43
> 
> 3) PhpOption\Tests\LazyOptionTest::testGetWithoutArgumentsAndConstructor
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:60
> 
> 4) PhpOption\Tests\LazyOptionTest::testGetWithoutArgumentsAndCreate
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:76
> 
> 5) PhpOption\Tests\LazyOptionTest::testCallbackReturnsNull
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:93
> 
> 6) 
> PhpOption\Tests\LazyOptionTest::testExceptionIsThrownIfCallbackReturnsNonOption
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:119
> 
> 7) PhpOption\Tests\LazyOptionTest::testInvalidCallbackAndConstructor
> This test did not perform any assertions
> 
> /<>/tests/PhpOption/Tests/LazyOptionTest.php:138
> 
> 8) PhpOption\Tests\LazyOptionTest::testInvalidCallbackAndCreate
> This test did not perform any assertions
> 
> /<>/tests/Php

Bug#1039814: php-parser: FTBFS with phpunit 10: make[1]: *** [debian/rules:24: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-parser
Version: 4.15.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-parser was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> There was 1 PHPUnit test runner warning:
> 
> 1) Class PhpParser\ParserTest declared in 
> /<>/test/PhpParser/ParserTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> There was 1 error:
> 
> 1) PhpParser\NodeAbstractTest::testConstruct with data set #0
> Error: Call to undefined method 
> PhpParser\NodeAbstractTest::assertObjectHasAttribute()
> 
> /<>/test/PhpParser/NodeAbstractTest.php:68
> 
> --
> 
> 59 tests triggered 61 PHPUnit deprecations:
> 
> 1) PhpParser\Builder\ClassConstTest::testValues
> Data Provider method 
> PhpParser\Builder\ClassConstTest::provideTestDefaultValues() is not static
> 
> /<>/test/PhpParser/Builder/ClassConstTest.php:148
> 
> 2) PhpParser\Builder\EnumCaseTest::testValues
> Data Provider method 
> PhpParser\Builder\EnumCaseTest::provideTestDefaultValues() is not static
> 
> /<>/test/PhpParser/Builder/EnumCaseTest.php:63
> 
> 3) PhpParser\Builder\ParamTest::testDefaultValues
> Data Provider method PhpParser\Builder\ParamTest::provideTestDefaultValues() 
> is not static
> 
> /<>/test/PhpParser/Builder/ParamTest.php:24
> 
> 4) PhpParser\Builder\ParamTest::testTypes
> * Data Provider method PhpParser\Builder\ParamTest::provideTestTypes() is not 
> static
> 
> * Data Provider method 
> PhpParser\Builder\ParamTest::provideTestNullableTypes() is not static
> 
> * Data Provider method PhpParser\Builder\ParamTest::provideTestUnionTypes() 
> is not static
> 
> /<>/test/PhpParser/Builder/ParamTest.php:92
> 
> 5) PhpParser\Builder\PropertyTest::testDefaultValues
> Data Provider method 
> PhpParser\Builder\PropertyTest::provideTestDefaultValues() is not static
> 
> /<>/test/PhpParser/Builder/PropertyTest.php:105
> 
> 6) PhpParser\BuilderFactoryTest::testFactory
> Data Provider method PhpParser\BuilderFactoryTest::provideTestFactory() is 
> not static
> 
> /<>/test/PhpParser/BuilderFactoryTest.php:19
> 
> 7) PhpParser\CodeParsingTest::testParse
> Data Provider method PhpParser\CodeParsingTest::provideTestParse() is not 
> static
> 
> /<>/test/PhpParser/CodeParsingTest.php:13
> 
> 8) PhpParser\CommentTest::testReformatting
> Data Provider method PhpParser\CommentTest::provideTestReformatting() is not 
> static
> 
> /<>/test/PhpParser/CommentTest.php:27
> 
> 9) PhpParser\ConstExprEvaluatorTest::testEvaluate
> Data Provider method PhpParser\ConstExprEvaluatorTest::provideTestEvaluate() 
> is not static
> 
> /<>/test/PhpParser/ConstExprEvaluatorTest.php:11
> 
> 10) PhpParser\ConstExprEvaluatorTest::testEvaluateSilently
> Data Provider method 
> PhpParser\ConstExprEvaluatorTest::provideTestEvaluateSilently() is not static
> 
> /<>/test/PhpParser/ConstExprEvaluatorTest.php:102
> 
> 11) PhpParser\ErrorTest::testColumnInfo
> Data Provider method PhpParser\ErrorTest::provideTestColumnInfo() is not 
> static
> 
> /<>/test/PhpParser/ErrorTest.php:44
> 
> 12) PhpParser\Internal\DifferTest::testDiff
> Data Provider method PhpParser\Internal\DifferTest::provideTestDiff() is not 
> static
> 
> /<>/test/PhpParser/Internal/DifferTest.php:32
> 
> 13) PhpParser\Internal\DifferTest::testDiffWithReplacements
> Data Provider method 
> PhpParser\Internal\DifferTest::provideTestDiffWithReplacements() is not static
> 
> /<>/test/PhpParser/Internal/DifferTest.php:51
> 
> 14) PhpParser\JsonDecoderTest::testDecodingError
> Data Provider method PhpParser\JsonDecoderTest::provideTestDecodingError() is 
> not static
> 
> /<>/test/PhpParser/JsonDecoderTest.php:27
> 
> 15) PhpParser\Lexer\EmulativeTest::testReplaceKeywords
> Data Provider method 
> PhpParser\Lexer\EmulativeTest::provideTestReplaceKeywords() is not static
> 
> /<>/test/PhpParser/Lexer/EmulativeTest.php:19
> 
> 16) PhpParser\Lexer\EmulativeTest::testReplaceKeywordsUppercase
> Data Provider method 
> PhpParser\Lexer\EmulativeTest::provideTestReplaceKeywords() is not static
> 
> /<>/test/PhpParser/Lexer/EmulativeTest.php:30
> 
> 17) PhpParser\Lexer\EmulativeTest::testNoReplaceKeywordsAfterObjectOperator
> Data Provider method 
> PhpParser\Lexer\EmulativeTest::provideTestReplaceKeywords() is not static
> 
> /<>/test/PhpParser/Lexer/EmulativeTest.php:41
> 
> 18) 
> PhpParser\Lexer\EmulativeTest::testNoReplaceKeywordsAfterObjectOperatorWithSpaces
> Data Provider method 
> PhpParser\Lexer\EmulativeTest::provideTestReplaceKeywords() is not static
> 
> /<>/test/PhpParser/Lexer/EmulativeTest.php:53
> 
> 19) 

Bug#1039815: php-phpdocumentor-reflection-common: FTBFS with phpunit 10: make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-phpdocumentor-reflection-common
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-phpdocumentor-reflection-common was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap src/Common/autoload.php
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> D 17 / 17 
> (100%)
> 
> Time: 00:00.004, Memory: 6.00 MB
> 
> There was 1 PHPUnit test runner warning:
> 
> 1) Test results may not be as expected because the XML configuration file did 
> not pass validation:
> 
>   Line 9:
>   - Element 'filter': This element is not expected.
> 
> 
> --
> 
> 2 tests triggered 2 PHPUnit deprecations:
> 
> 1) phpDocumentor\Reflection\FqsenTest::testValidFormats
> Data Provider method phpDocumentor\Reflection\FqsenTest::validFqsenProvider() 
> is not static
> 
> /<>/tests/unit/FqsenTest.php:28
> 
> 2) phpDocumentor\Reflection\FqsenTest::testInValidFormats
> Data Provider method 
> phpDocumentor\Reflection\FqsenTest::invalidFqsenProvider() is not static
> 
> /<>/tests/unit/FqsenTest.php:61
> 
> WARNINGS!
> Tests: 17, Assertions: 17, Warnings: 1, Deprecations: 2.
> make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-phpdocumentor-reflection-common/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039813: php-parsedown: FTBFS with phpunit 10: make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-parsedown
Version: 1.7.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-parsedown was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHP Warning:  foreach() argument must be of type array|object, null given in 
> /<>/test/ParsedownTest.php on line 98
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> D...4 / 4 
> (100%)
> 
> Time: 00:00.004, Memory: 8.00 MB
> 
> There was 1 PHPUnit error:
> 
> 1) ParsedownTest::test_
> The data provider specified for ParsedownTest::test_ is invalid
> Empty data set provided by data provider
> 
> /<>/test/ParsedownTest.php:44
> 
> --
> 
> There was 1 PHPUnit test runner warning:
> 
> 1) Test results may not be as expected because the XML configuration file did 
> not pass validation:
> 
>   Line 4:
>   - Element 'testsuite': The attribute 'name' is required but missing.
> 
> 
> --
> 
> 1 test triggered 1 PHPUnit deprecation:
> 
> 1) ParsedownTest::test_
> Data Provider method ParsedownTest::data() is not static
> 
> /<>/test/ParsedownTest.php:44
> 
> WARNINGS!
> Tests: 4, Assertions: 10, Warnings: 1, Deprecations: 1.
> make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-parsedown/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039812: php-oscarotero-gettext: FTBFS with phpunit 10: make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-oscarotero-gettext
Version: 4.8.7-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-oscarotero-gettext was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --do-not-cache-result
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> DDDD. 65 / 99 ( 
> 65%)
> .D99 / 99 
> (100%)
> 
> Time: 00:00.049, Memory: 10.00 MB
> 
> There was 1 PHPUnit test runner warning:
> 
> 1) Class Gettext\Tests\AbstractTest declared in 
> /<>/tests/AbstractTest.php is abstract
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> --
> 
> 4 tests triggered 4 PHPUnit deprecations:
> 
> 1) Gettext\Tests\StringsTest::testStringFromPhp
> Data Provider method Gettext\Tests\StringsTest::stringFromPhpProvider() is 
> not static
> 
> /<>/tests/StringsTest.php:35
> 
> 2) Gettext\Tests\StringsTest::testStringToPo
> Data Provider method Gettext\Tests\StringsTest::poStringsProvider() is not 
> static
> 
> /<>/tests/StringsTest.php:54
> 
> 3) Gettext\Tests\StringsTest::testStringFromPo
> Data Provider method Gettext\Tests\StringsTest::poStringsProvider() is not 
> static
> 
> /<>/tests/StringsTest.php:62
> 
> 4) Gettext\Tests\StringsTest::testStringFromPo2
> Data Provider method Gettext\Tests\StringsTest::stringFromPo2Provider() is 
> not static
> 
> /<>/tests/StringsTest.php:85
> 
> WARNINGS!
> Tests: 99, Assertions: 1102, Warnings: 1, Deprecations: 18.
> make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-oscarotero-gettext/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039811: php-opis-closure: FTBFS with phpunit 10: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-opis-closure
Version: 3.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-opis-closure was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p vendor
> phpab \
>   -o vendor/autoload.php \
>   -t debian/autoload.php.test.tpl \
>   tests
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory tests
> 
> Autoload file vendor/autoload.php generated.
> 
> ln -s ../functions.php src/functions.php
> phpunit -v --include-path src
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> ...  63 / 111 ( 
> 56%)
> 111 / 111 
> (100%)
> 
> Time: 00:00.039, Memory: 10.00 MB
> 
> There were 2 PHPUnit test runner warnings:
> 
> 1) Class NamespaceFullyQualifiedTest cannot be found in 
> /<>/tests/NamespaceFullyQualifiedTest.php
> 
> 2) Class NamespaceGroupTest cannot be found in 
> /<>/tests/NamespaceGroupTest.php
> 
> --
> 
> There was 1 PHPUnit test runner deprecation:
> 
> 1) Your XML configuration validates against a deprecated schema. Migrate your 
> XML configuration using "--migrate-configuration"!
> 
> WARNINGS!
> Tests: 111, Assertions: 241, Warnings: 2, Deprecations: 1.
> make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-opis-closure/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039810: php-nrk-predis: FTBFS with phpunit 10: PHP Fatal error: Cannot override final method PHPUnit\Framework\Assert::assertMatchesRegularExpression() in /<>/tests/PHPUnit/PredisTe

[Athos Ribeiro]

Source: php-nrk-predis
Version: 2.2.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-nrk-predis was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> redis-server --daemonize yes
> phpunit
> PHP Fatal error:  Cannot override final method 
> PHPUnit\Framework\Assert::assertMatchesRegularExpression() in 
> /<>/tests/PHPUnit/PredisTestCase.php on line 140
> make[1]: *** [debian/rules:12: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-nrk-predis/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039809: php-nikic-fast-route: FTBFS with phpunit 10: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1

[Athos Ribeiro]

Source: php-nikic-fast-route
Version: 1.3.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-nikic-fast-route was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # keep in sync with debian/tests/run-upstream-tests
> phpunit --do-not-cache-result --bootstrap test/autoload.php
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml
> 
> D..  63 / 204 ( 
> 30%)
> ... 126 / 204 ( 
> 61%)
> ..S 189 / 204 ( 
> 92%)
> ... 204 / 204 
> (100%)
> 
> Time: 00:00.027, Memory: 8.00 MB
> 
> There were 2 PHPUnit test runner warnings:
> 
> 1) Test results may not be as expected because the XML configuration file did 
> not pass validation:
> 
>   Line 12:
>   - Element 'phpunit', attribute 'backupStaticAttributes': The attribute 
> 'backupStaticAttributes' is not allowed.
>   - Element 'phpunit', attribute 'convertErrorsToExceptions': The attribute 
> 'convertErrorsToExceptions' is not allowed.
>   - Element 'phpunit', attribute 'convertNoticesToExceptions': The attribute 
> 'convertNoticesToExceptions' is not allowed.
>   - Element 'phpunit', attribute 'convertWarningsToExceptions': The attribute 
> 'convertWarningsToExceptions' is not allowed.
>   - Element 'phpunit', attribute 'syntaxCheck': The attribute 'syntaxCheck' 
> is not allowed.
> 
>   Line 19:
>   - Element 'filter': This element is not expected.
> 
> 
> 2) Class FastRoute\Dispatcher\DispatcherTest declared in 
> /<>/test/Dispatcher/DispatcherTest.php is abstract
> 
> --
> 
> 14 tests triggered 14 PHPUnit deprecations:
> 
> 1) FastRoute\Dispatcher\CharCountBasedTest::testFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\CharCountBasedTest::provideFoundDispatchCases() is not 
> static
> 
> /<>/test/Dispatcher/DispatcherTest.php:34
> 
> 2) FastRoute\Dispatcher\CharCountBasedTest::testNotFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\CharCountBasedTest::provideNotFoundDispatchCases() is 
> not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:46
> 
> 3) FastRoute\Dispatcher\CharCountBasedTest::testMethodNotAllowedDispatches
> Data Provider method 
> FastRoute\Dispatcher\CharCountBasedTest::provideMethodNotAllowedDispatchCases()
>  is not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:59
> 
> 4) FastRoute\Dispatcher\GroupCountBasedTest::testFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\GroupCountBasedTest::provideFoundDispatchCases() is not 
> static
> 
> /<>/test/Dispatcher/DispatcherTest.php:34
> 
> 5) FastRoute\Dispatcher\GroupCountBasedTest::testNotFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\GroupCountBasedTest::provideNotFoundDispatchCases() is 
> not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:46
> 
> 6) FastRoute\Dispatcher\GroupCountBasedTest::testMethodNotAllowedDispatches
> Data Provider method 
> FastRoute\Dispatcher\GroupCountBasedTest::provideMethodNotAllowedDispatchCases()
>  is not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:59
> 
> 7) FastRoute\Dispatcher\GroupPosBasedTest::testFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\GroupPosBasedTest::provideFoundDispatchCases() is not 
> static
> 
> /<>/test/Dispatcher/DispatcherTest.php:34
> 
> 8) FastRoute\Dispatcher\GroupPosBasedTest::testNotFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\GroupPosBasedTest::provideNotFoundDispatchCases() is not 
> static
> 
> /<>/test/Dispatcher/DispatcherTest.php:46
> 
> 9) FastRoute\Dispatcher\GroupPosBasedTest::testMethodNotAllowedDispatches
> Data Provider method 
> FastRoute\Dispatcher\GroupPosBasedTest::provideMethodNotAllowedDispatchCases()
>  is not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:59
> 
> 10) FastRoute\Dispatcher\MarkBasedTest::testFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\MarkBasedTest::provideFoundDispatchCases() is not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:34
> 
> 11) FastRoute\Dispatcher\MarkBasedTest::testNotFoundDispatches
> Data Provider method 
> FastRoute\Dispatcher\MarkBasedTest::provideNotFoundDispatchCases() is not 
> static
> 
> /<>/test/Dispatcher/DispatcherTest.php:46
> 
> 12) FastRoute\Dispatcher\MarkBasedTest::testMethodNotAllowedDispatches
> Data Provider method 
> FastRoute\Dispatcher\MarkBasedTest::provideMethodNotAllowedDispatchCases() is 
> not static
> 
> /<>/test/Dispatcher/DispatcherTest.php:5

Bug#1039808: atf: reproducible-builds: Embedded path to bash in various binaries

[Vagrant Cascadian]

Source: atf
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The path to bash is embedded differently in various binaries depending
on weather it is built in a usrmerge or non-usrmerge environment:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/atf.html

  /usr/bin/atf-sh

  /bin/bash
  vs.
  /usr/bin/bash

The attached patch fixes this by passing ATF_SHELL to dh_auto_build in
debian/rules.

According to my local tests, with this patch applied atf should build
reproducibly on tests.reproducible-builds.org when it migrates to
trixie/testing! Unfortunately, there are still unresolved build path
issues which are tested on unstable and experimental.

Thanks for maintaining atf!

live well,
  vagrant
From bc4307d7b3dd7a1e9a6606dee1975525b37aaa59 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 28 Jun 2023 14:04:56 -0700
Subject: [PATCH] debian/rules: Pass ATF_SHELL to dh_auto_build.

Otherwise, the path to bash is embedded differently in a usrmerge and
non-usrmerge environment. Use /bin/bash, as that is present in both cases.

https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index 33c3a6c..2176966 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,5 +5,8 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 %:
 	dh $@
 
+override_dh_auto_build:
+	dh_auto_build -- ATF_SHELL=/bin/bash
+
 override_dh_auto_test:
 	-dh_auto_test -- installcheck-kyua
-- 
2.39.2



signature.asc
Description: PGP signature

Bug#1039807: php-net-ldap2: FTBFS with phpunit 10: PHP Fatal error: Cannot override final method PHPUnit\Framework\Assert::assertTrue() in /<>/tests/Net_LDAP2_TestBase.php on line 4

[Athos Ribeiro]

Source: php-net-ldap2
Version: 2.2.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-net-ldap2 was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir Net_LDAP2-2.2.1
> ln -st Net_LDAP2-2.2.1 ../doc ../Net ../tests
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=phppear
>   cp package.xml ./Net_LDAP2-2.2.1/package.xml
>   sed -i -e s/md5sum=\"\[^\"\]\*\"// -e s/sha1sum=\"\[^\"\]\*\"// 
> ./Net_LDAP2-2.2.1/package.xml
>dh_auto_build -O--buildsystem=phppear
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> phpunit --include-path Net_LDAP2-2.2.1 ./Net_LDAP2-2.2.1/tests
> PHP Fatal error:  Cannot override final method 
> PHPUnit\Framework\Assert::assertTrue() in 
> /<>/tests/Net_LDAP2_TestBase.php on line 4
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 255


The full build logs and additional context is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/0/php-net-ldap2/

A phpunit reverse-dependencies rebuild status is available at
http://people.ubuntu.com/~athos-ribeiro/rebuilds/phpunit10/index.html

-- 
Athos Ribeiro

Bug#1039806: php-nesbot-carbon: FTBFS with phpunit 10: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2

[Athos Ribeiro]

Source: php-nesbot-carbon
Version: 2.65.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: pkg-php-p...@lists.alioth.debian.org
Usertags: phpunit

Hi,

We will start the phpunit 10 transition in unstable soon. During a test
rebuild, php-nesbot-carbon was found to FTBFS.

To reproduce this locally, you need to install the phpunit 10 package (and any
other dependency, which should also be available) from experimental on an
unstable system or build chroot.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpabtpl \
>   --require nesbot/carbon \
>   --require doctrine/dbal \
>   > debian/autoload.php.test.tpl
> Proceeding without a composer.json file.phpab \
>   -o tests/autoload.php \
>   -t debian/autoload.php.test.tpl \
>   --blacklist 'carbon\\cli' \
>   --blacklist 'symfony\\component\\translation\\translatorinterface' \
>   tests
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory tests
> 
> Autoload file tests/autoload.php generated.
> 
> phpunit -v --bootstrap tests/autoload.php --include-path src
> PHPUnit 10.2.2 by Sebastian Bergmann and contributors.
> 
> Runtime:   PHP 8.2.7
> Configuration: /<>/phpunit.xml.dist
> 
> D   61 / 5618 (  
> 1%)
> .  122 / 5618 (  
> 2%)
> .  183 / 5618 (  
> 3%)
> .  244 / 5618 (  
> 4%)
> .  305 / 5618 (  
> 5%)
> .  366 / 5618 (  
> 6%)
> .  427 / 5618 (  
> 7%)
> .  488 / 5618 (  
> 8%)
> .  549 / 5618 (  
> 9%)
> .  610 / 5618 ( 
> 10%)
> .  671 / 5618 ( 
> 11%)
> .  732 / 5618 ( 
> 13%)
> .  793 / 5618 ( 
> 14%)
> .  854 / 5618 ( 
> 15%)
> .  915 / 5618 ( 
> 16%)
> .  976 / 5618 ( 
> 17%)
> . 1037 / 5618 ( 
> 18%)
> . 1098 / 5618 ( 
> 19%)
> . 1159 / 5618 ( 
> 20%)
> . 1220 / 5618 ( 
> 21%)
> . 1281 / 5618 ( 
> 22%)
> . 1342 / 5618 ( 
> 23%)
> .SF.. 1403 / 5618 ( 
> 24%)
> . 1464 / 5618 ( 
> 26%)
> . 1525 / 5618 ( 
> 27%)
> . 1586 / 5618 ( 
> 28%)
> . 1647 / 5618 ( 
> 29%)
> . 1708 / 5618 ( 
> 30%)
> . 1769 / 5618 ( 
> 31%)
> . 1830 / 5618 ( 
> 32%)
> . 1891 / 5618 ( 
> 33%)
> . 1952 / 5618 ( 
> 34%)
> . 2013 / 5618 ( 
> 35%)
> ...E. 2074 / 5618 ( 
> 36%)
> .SS.. 2135 / 5618 ( 
> 38%)
> . 2196 / 5618 ( 
> 39%)
> . 2257 / 5618 ( 
> 40%)
> . 2318 / 5618 ( 
> 41%)
> .N... 2379 / 5618 ( 
> 42%)
> . 2440 / 5618 ( 
> 43%)
> . 2501 / 5618 ( 
> 44%)
> . 2562 / 5618 ( 
> 45%)
> . 2623 / 5618 ( 
> 46%)
>