Hi Simon,
On Tue, Jan 30, 2024 at 03:50:18AM -0800, Simon Chopin wrote:
> > On Tue, Jan 23, 2024 at 02:02:15AM -0800, Simon Chopin wrote:
> > > Hi Release Team,
> > > It seems we have a few big transitions either in progress (perl,
> > > python) or about to start in the coming weeks (php, armhf 6
Hi Steve,
> On Tue, Jan 23, 2024 at 02:02:15AM -0800, Simon Chopin wrote:
> > Hi Release Team,
>
> > It seems we have a few big transitions either in progress (perl,
> > python) or about to start in the coming weeks (php, armhf 64bit time_t).
> > My original plans for glibc would add fuel to that
On Tue, Jan 23, 2024 at 02:02:15AM -0800, Simon Chopin wrote:
> Hi Release Team,
> It seems we have a few big transitions either in progress (perl,
> python) or about to start in the coming weeks (php, armhf 64bit time_t).
> My original plans for glibc would add fuel to that fire, as I projected
>
Hi Graham,
> > A possible way to reduce the friction introduced by a new glibc verison
> > would be to delay it until after Feature Freeze: fewer packages would
> > pick up the new symbols and thus wouldn't get blocked waiting for the
> > glibc rdeps autopkgtests to clear.
>
> Does it need to be a
Hi Simon
On Tue, 23 Jan 2024 at 12:03, Simon Chopin wrote:
> It seems we have a few big transitions either in progress (perl,
> python) or about to start in the coming weeks (php, armhf 64bit time_t).
> My original plans for glibc would add fuel to that fire, as I projected
> to upload it to -pro
Hi Release Team,
It seems we have a few big transitions either in progress (perl,
python) or about to start in the coming weeks (php, armhf 64bit time_t).
My original plans for glibc would add fuel to that fire, as I projected
to upload it to -proposed in about 2 weeks.
A possible way to reduce t
