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
