Your message dated Sat, 21 Jan 2023 16:13:49 +0100
with message-id <y8wblwrokoeeq...@ramacher.at>
and subject line Re: Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2
has caused the Debian Bug report #1014460,
regarding transition: php8.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1014460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
to prevent the situation from the last time, I am kind of "starting"
the transition to PHP 8.2 now with PHP 8.2.0~alpha2. I will be uploading
packages to experimental as I will be updating them to support PHP 8.2.
Ondrej
Ben file:
title = "php8.2";
is_affected = .depends ~ "phpapi-20210902" | .depends ~ "phpapi-20210903";
is_good = .depends ~ "phpapi-20210903";
is_bad = .depends ~ "phpapi-20210902";
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmLFlsdfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcL5Bg//eTOW8HuuF15R/5SPKReyizaG9oB75HIVUBWTwnovNcJx3UNvlpoGCrdK
jWEaAD+Pv9b321gZikPuauYgwT3N0sGeA7L51aRO1m4BCEvmOTnY6VbmLvS66KM9
AWZigYK+/ZLDxju5edAdhfA25a8GLeFuXHg9YZERmpIoZH+++iVFnNZtrWbJ+NB0
cpcMapq9jIkuz3qKKEccKFTCD1Yy63rCVgqaTWg0oHydKyx1n4OQjZhmDMOgHdPg
hgN+9Kc5YLYcK3ReyKCxaernWcPtP9Zw8JJx3b62EmvKV6fglWNMzt++dQhGzM+5
iwWHeAaR/UaGf43T1DtT4j55quUXRNaJda3GQ27xoBDZRf8k7LZSp+rnhUZDlNRe
fX2LYyCe2IBkATiKIa1A3JfuPf6/6i1OEXP6keMVgf9LdLSi+yGZ//DLy+ObhCOF
+Q0yBv8eYSpOUk4EChFCKBvLLVv+PDdo896FK1E0z42XpJvWVVHGJ8ZZ9IljnLM7
l8Ccnr4Iov9aETXWBE+seEV1P6G034yj6CxmSBgTnJ2gKJLhT/mLPbLfqZsl0saF
xwCyq03p1Xz1DZtZJXCFNNe2LV56vYYmvxs/EnrSN2jgziIKvHPQffl+QRVelbza
BJ7ZIWxDLmSJfdkJbd91PPKnPePkUo5WsMyCFI+PCNQjox7xeXk=
=jKgC
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2023-01-11 21:31:39 +0100, Ondřej Surý wrote:
> Sorry for top posting…
>
> It’s easier for me to wait as I don’t want use custom repository for my
> sbuild chroots. Hence the wait…
Thanks everyone. php-defaults migrated and php8.1 got removed from
testing.
Cheers
>
> Ondrej
> --
> Ondřej Surý <ond...@sury.org> (He/Him)
>
> > On 11. 1. 2023, at 21:01, Paul Gevers <elb...@debian.org> wrote:
> >
> > Hi Ondřej,
> >
> >> On 11-01-2023 20:42, Ondřej Surý wrote:
> >> Now, what should I do about:
> >> • Not built on buildd: arch amd64 binaries uploaded by ondrej
> >> • Not built on buildd: arch all binaries uploaded by ondrej, a new
> >> source-only upload is needed to allow migration
> >> Do I really have to reupload everything that had to pass NEW with
> >> no-change source-only upload?
> >
> > I have already NMU'd one of them (no change source only), because yes, our
> > infrastructure currently doesn't enable us to do binNMU that survives for
> > arch:all (we can do arch:any).
> >
> >>> yes, I will take care of those, I’m just uploading them in batches as the
> >>> dependencies require.
> >
> > Just in case you aren't aware, if the problem is that Build-Dependencies
> > aren't available yet (because of your previous batch), you don't need to
> > wait with uploading. The buildd's will know what to do and the package will
> > stay in "Builds Dependencies unavailable" until their B-D's are built and
> > available on the buildd.
> >
> > Paul
>
--
Sebastian Ramacher
--- End Message ---
