Re: odd postgresql error

[Patrick Welche <prlw1%welche.eu@localhost>]

On Tue, Apr 01, 2025 at 11:22:40AM +0200, Benny Siegert wrote:
> On Tue, Apr 1, 2025 at 10:33 AM Patrick Welche <prlw1%welche.eu@localhost> wrote:
> > Puzzled as I'm not using MirBSD
> 
> What does MirBSD have to do with this? :)

The only recent change was removing the MirBSD special case, which has
nothing to do with it.

Now I see what changed: this is the first time I upgrade postgresql17.
I was running postgresql16 until a fortnight ago.

$ diff -u postgresql16/Makefile.common  postgresql17/Makefile.common
...
 .if !empty(PKGNAME:M*-*-*)
 module=                ${PKGNAME:C/-[0-9].*$//:C/^.*-//}
-CONFLICTS+=    postgresql[2-9][0-9]-${module}-[0-9]*
+CONFLICTS+=    postgresql[1-9][0-9]-${module}-[0-9]*
 .endif
...

so I'll make the 17 version as inaccurate as the 16 one after a quick
pbulk check, which will at least render it harmless.


Cheers,

Patrick