On Wed, 17 Jan 2024 09:05:47 -0500 Scott Kitterman
wrote:
> On Wednesday, January 17, 2024 9:03:29 AM EST Richard Rosner wrote:
> > I've updated all mariadb packages to 10.11.6 and all postfix packages.
> > Everything still working.
> >
> Excellent news. Thanks for testing.
Postfix packages
On Wednesday, January 17, 2024 9:03:29 AM EST Richard Rosner wrote:
> I've updated all mariadb packages to 10.11.6 and all postfix packages.
> Everything still working.
>
Excellent news. Thanks for testing.
Scott K
signature.asc
Description: This is a digitally signed message part.
I've updated all mariadb packages to 10.11.6 and all postfix packages.
Everything still working.
Am Mittwoch, 17. Januar 2024 00:34 CET, schrieb Scott Kitterman
:
They accepted mariadb 10.11.6 as a proposed update and I rebuilt postfix again.
Updated packages (and the first ones also, note
They accepted mariadb 10.11.6 as a proposed update and I rebuilt postfix again.
Updated packages (and the first ones also, note the slightly different revision
number) at the same location:
https://kitterman.com/debian/
I'm not sure if you'll need to upgrade your mariadb packages. If so, they
Good to know. Thanks.
Am Dienstag, 16. Januar 2024 21:00 CET, schrieb Scott Kitterman
:
So, the magic needed to build the new update exceeds my grasp, but it's
debian/changelog discusses fixing regressions. On that basis, I think the
thing to do is reassign the bug to mariadb and mark it as
So, the magic needed to build the new update exceeds my grasp, but it's
debian/changelog discusses fixing regressions. On that basis, I think the
thing to do is reassign the bug to mariadb and mark it as affecting postfix.
I'll also bring it to the stable release manager's attention.
Scott K
Excellent. On that basis, I think blaming mariadb for the regression is
appropriate. I see there's another mariadb update pending. If would up for
another test, I'd like to see if that update solves the problem. I'll build
another set of packages against that and if that works, then we just
These packages do work without a problem.
Am Dienstag, 16. Januar 2024 19:35 CET, schrieb Scott Kitterman
:
Rebuild binaries are available (for the moment) at:
https://kitterman.com/debian/
I'll remove them once we've done testing. That's all the binaries built by
postfix. You'll need to
Rebuild binaries are available (for the moment) at:
https://kitterman.com/debian/
I'll remove them once we've done testing. That's all the binaries built by
postfix. You'll need to download and then use dpkg -i to install all the ones
you have on your system, not just postfix-mysql. At a
It's slightly more complicated because you have to make sure you get the old
version of mariadb. I'll build it and send you a link.
Scott K
On Tuesday, January 16, 2024 1:08:51 PM EST Richard Rosner wrote:
> Would that be more than
>
> sudo apt build-dep postfix-mysql
> sudo apt install
Would that be more than
sudo apt build-dep postfix-mysql
sudo apt install build-essential
apt source postfix-mysql
cd postfix-mysql*
dpkg-buildpackage -us -uc
? Otherwise, if you want to build it, I can test it, no problem.
Am Dienstag, 16. Januar 2024 18:19 CET, schrieb Scott Kitterman
:
I
I agree it's odd. I don't use postfix with any of the external map types, so
this isn't something I can really test.
Can you rebuild 3.7.9 against the older mariadb or if not, and I build it, will
you test it?
Scott K
On January 16, 2024 5:05:54 PM UTC, Richard Rosner
wrote:
>
>No Idea
No Idea when was the last update to mariadb, but the fact that the stable
version has problems the stable-updates version doesn't while not changing
anything else shows that something is broken. Maybe just the communication with
postfix. Maybe the breaking change was in postfix and not
On Tue, 16 Jan 2024 15:09:18 +0100 Richard Rosner wrote:
> Package: postfix-mysql
> Version: 3.7.9-0+deb12u1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> With the update in stable-updates, this package seems to be no longer
working. removing it and going
Package: postfix-mysql
Version: 3.7.9-0+deb12u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
With the update in stable-updates, this package seems to be no longer working.
removing it and going back to 3.7.6 solves the issue. This is what it writes to
journal:
Jan
15 matches
Mail list logo