Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)

2024-02-05 Thread Otto Kekäläinen
> $ grep mariadb results/* > results/results_dumped.txt:libmariadb-dev > results/results_failed.txt:libmariadbd-dev > results/results_none.txt:libmariadb-dev > $ > > There was nothing unintentional here. libmariadb-dev is clean wrt time_t. > libmariadbd-dev failed to be analyzed because it has

Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)

2024-02-05 Thread Steve Langasek
On Sun, Feb 04, 2024 at 04:08:43PM -0800, Otto Kekäläinen wrote: > +1 for MariaDB for the above. Also I think the package name change was > done for the wrong package, it should probably have been done for > libmariadb3 and not for libmariabd19. > apt-cache rdepends --no-recommends --no-suggests

Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)

2024-02-04 Thread Otto Kekäläinen
> Re: Steve Langasek > > Christoph Berg > >postgresql-16 (U) > > Please do not upload postgresql-16 before I ack the diff. > > I'll also note that *ALL* nmu diffs I've seen so far are using the > wrong version number in debian/changelog, missing the "~exp1" upload > from the actual upload.

postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)

2024-02-04 Thread Christoph Berg
Re: Steve Langasek > Christoph Berg >postgresql-16 (U) Please do not upload postgresql-16 before I ack the diff. I'll also note that *ALL* nmu diffs I've seen so far are using the wrong version number in debian/changelog, missing the "~exp1" upload from the actual upload. I've imported some