Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-20 Thread Scott Kitterman
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 in bookworm-proposed-updates have been rebuilt against the new 
mariadb, so I think this can be closed now.  If anyone runs into this problem 
with the packages from bookworm-updates/stable-updates, install the rebuilt 
version from bookworm/stable-proposed-updates.  After the next point release, 
this will be entirely OBE.

Scott K

signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-17 Thread Scott Kitterman
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.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-17 Thread Richard Rosner

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 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 can
currently be found in incoming:

http://incoming.debian.org/debian-buildd/pool/main/m/mariadb/

After the next dinstall they will be available in the bookworm-proposed
updates repository. For incoming, you'll need to wget the binaries and use
dpkg to install them. For bookworm-proposed-updates, you can use apt with an
appropriate entry in your sources.list.

Please test and let me know how it goes:

Thanks,

Scott K

On Tuesday, January 16, 2024 3:39:43 PM EST Richard Rosner wrote:
> 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 affecting postfix. I'll also bring it to the stable release
> manager's attention.
>
> Scott K
>
> On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> > 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
> > need to make sure we get that update accepted and rebuild postfix.
> >
> > Scott K
 


smime.p7s
Description: S/MIME cryptographic signature


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread 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 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 can 
currently be found in incoming:

http://incoming.debian.org/debian-buildd/pool/main/m/mariadb/

After the next dinstall they will be available in the bookworm-proposed 
updates repository.  For incoming, you'll need to wget the binaries and use 
dpkg to install them.  For bookworm-proposed-updates, you can use apt with an 
appropriate entry in your sources.list.

Please test and let me know how it goes:

Thanks,

Scott K

On Tuesday, January 16, 2024 3:39:43 PM EST Richard Rosner wrote:
> 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 affecting postfix. I'll also bring it to the stable release
> manager's attention.
> 
> Scott K
> 
> On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> > 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
> > need to make sure we get that update accepted and rebuild postfix.
> > 
> > Scott K



signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Richard Rosner

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 affecting postfix.
I'll also bring it to the stable release manager's attention.

Scott K

On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> 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
> need to make sure we get that update accepted and rebuild postfix.
>
> Scott K


smime.p7s
Description: S/MIME cryptographic signature


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread 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 affecting postfix.  
I'll also bring it to the stable release manager's attention.

Scott K

On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> 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
> need to make sure we get that update accepted and rebuild postfix.
> 
> Scott K
> 
> On Tuesday, January 16, 2024 2:25:13 PM EST Richard Rosner wrote:
> > 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 download and then use dpkg -i to install all the
> > ones you have on your system, not just postfix-mysql. At a minimum it will
> > be postfix and postfix-mysql.
> > 
> > Let me know how it goes.
> > 
> > Scott K



signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Scott Kitterman
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 need to 
make sure we get that update accepted and rebuild postfix.

Scott K

On Tuesday, January 16, 2024 2:25:13 PM EST Richard Rosner wrote:
> 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 download and then use dpkg -i to install all the
> ones you have on your system, not just postfix-mysql. At a minimum it will
> be postfix and postfix-mysql.
> 
> Let me know how it goes.
> 
> Scott K



signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Richard Rosner

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 download and then use dpkg -i to install all the ones
you have on your system, not just postfix-mysql. At a minimum it will be
postfix and postfix-mysql.

Let me know how it goes.

Scott K


smime.p7s
Description: S/MIME cryptographic signature


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread 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 download and then use dpkg -i to install all the ones 
you have on your system, not just postfix-mysql.  At a minimum it will be 
postfix and postfix-mysql.

Let me know how it goes.

Scott K

On Tuesday, January 16, 2024 1:14:02 PM EST Scott Kitterman wrote:
> 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 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 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  
> aachen.de> wrote:
> > >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
> > >postfix-mysql, I can't tell. Just that v3.7.9 refuses to accept mysql as
> > >a
> > >valid option. Also, for me the logs look like postfix doesn't know what
> > >it
> > >should do with mysql, not like it can't reach a mysql server=



signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Scott Kitterman
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 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 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 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
> >postfix-mysql, I can't tell. Just that v3.7.9 refuses to accept mysql as a
> >valid option. Also, for me the logs look like postfix doesn't know what it
> >should do with mysql, not like it can't reach a mysql server=



signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Richard Rosner

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 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 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 postfix-mysql, 
>I can't tell. Just that v3.7.9 refuses to accept mysql as a valid option. 
>Also, for me the logs look like postfix doesn't know what it should do with 
>mysql, not like it can't reach a mysql server=


smime.p7s
Description: S/MIME cryptographic signature


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Scott Kitterman
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 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 postfix-mysql, 
>I can't tell. Just that v3.7.9 refuses to accept mysql as a valid option. 
>Also, for me the logs look like postfix doesn't know what it should do with 
>mysql, not like it can't reach a mysql server=



Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Richard Rosner

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 postfix-mysql, I 
can't tell. Just that v3.7.9 refuses to accept mysql as a valid option. Also, 
for me the logs look like postfix doesn't know what it should do with mysql, 
not like it can't reach a mysql server.

Am Dienstag, 16. Januar 2024 17:48 CET, schrieb Scott Kitterman 
:
 I'm not sure where this comes from. There are no mysql related changes in
this update. I note that the mariadb version is different, so I would think
it's more likely the issue is related to a change there.

Scott K


smime.p7s
Description: S/MIME cryptographic signature


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Scott Kitterman
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 back to 3.7.6 solves the issue. This is what it 
writes to journal:
> 
> Jan 16 14:58:32 mail postfix/smtpd[14969]: error: unsupported dictionary 
type: mysql
> Jan 16 14:58:32 mail postfix/smtpd[14969]: connect from localhost[127.0.0.1]
> Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: error: unsupported 
dictionary type: mysql
> Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: mysql:/etc/
postfix/mysql-forwards.cf is unavailable. unsupported dictionary type: mysql
> Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: 
virtual_alias_domains: mysql:/etc/postfix/mysql-forwards.cf: table lookup 
problem
> Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: mysql:/etc/
postfix/mysql-forwards.cf is unavailable. unsupported dictionary type: mysql
> Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: 
virtual_alias_domains: mysql:/etc/postfix/mysql-forwards.cf: table lookup 
problem
> Jan 16 14:58:32 mail postfix/smtpd[14969]: warning: mysql:/etc/postfix/mysql-
forwards.cf is unavailable. unsupported dictionary type: mysql
> Jan 16 14:58:32 mail postfix/smtpd[14969]: warning: mysql:/etc/postfix/mysql-
forwards.cf lookup error for "recei...@domain.de"
> Jan 16 14:58:32 mail postfix/smtpd[14969]: NOQUEUE: reject: RCPT from 
localhost[127.0.0.1]: 451 4.3.0 : Temporary lookup 
failure; from= to= proto=ESMTP 
helo=
> 
> So it simply stops providing the mysql support it was made for, which 
renders postfix itself unusable unless you where to move away from mysql.
> 
> 
> -- System Information:
> Debian Release: 12.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.1.0-16-amd64 (SMP w/2 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages postfix-mysql depends on:
> ii  libc62.36-9+deb12u3
> ii  libmariadb3  1:10.11.4-1~deb12u1
> ih  postfix  3.7.9-0+deb12u1

I'm not sure where this comes from.  There are no mysql related changes in 
this update.  I note that the mariadb version is different, so I would think 
it's more likely the issue is related to a change there.

Scott K


signature.asc
Description: This is a digitally signed message part.


Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-16 Thread Richard Rosner
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 16 14:58:32 mail postfix/smtpd[14969]: error: unsupported dictionary type: 
mysql
Jan 16 14:58:32 mail postfix/smtpd[14969]: connect from localhost[127.0.0.1]
Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: error: unsupported 
dictionary type: mysql
Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: 
mysql:/etc/postfix/mysql-forwards.cf is unavailable. unsupported dictionary 
type: mysql
Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: 
virtual_alias_domains: mysql:/etc/postfix/mysql-forwards.cf: table lookup 
problem
Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: 
mysql:/etc/postfix/mysql-forwards.cf is unavailable. unsupported dictionary 
type: mysql
Jan 16 14:58:32 mail postfix/trivial-rewrite[14972]: warning: 
virtual_alias_domains: mysql:/etc/postfix/mysql-forwards.cf: table lookup 
problem
Jan 16 14:58:32 mail postfix/smtpd[14969]: warning: 
mysql:/etc/postfix/mysql-forwards.cf is unavailable. unsupported dictionary 
type: mysql
Jan 16 14:58:32 mail postfix/smtpd[14969]: warning: 
mysql:/etc/postfix/mysql-forwards.cf lookup error for "recei...@domain.de"
Jan 16 14:58:32 mail postfix/smtpd[14969]: NOQUEUE: reject: RCPT from 
localhost[127.0.0.1]: 451 4.3.0 : Temporary lookup 
failure; from= to= proto=ESMTP 
helo=

So it simply stops providing the mysql support it was made for, which renders 
postfix itself unusable unless you where to move away from mysql.


-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-16-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages postfix-mysql depends on:
ii  libc62.36-9+deb12u3
ii  libmariadb3  1:10.11.4-1~deb12u1
ih  postfix  3.7.9-0+deb12u1

postfix-mysql recommends no packages.

postfix-mysql suggests no packages.

-- no debconf information