On Saturday, April 22, 2017 07:28:00 PM Niels Thykier wrote: > On Sat, 15 Apr 2017 00:39:56 +0000 JC <prog...@andrele.org> wrote: > > Hi Scott, > > > > Le ven. 14 avr. 2017 à 19:59, Scott Kitterman <deb...@kitterman.com> a > > > > écrit : > > > Thanks for the patch. > > > I still need to review the underlying issue. I suspect it is user > > > error. > > > Scott K > > > > Well, I was not sure myself, so I did install postfix into new jessie and > > stretch VMs and I've seen myself the same differences between the > > dynamicmaps.cf. > > > > The thing is: when you upgrade, the file is already created and > > provisioned > > with the map entries; but they are just not valid anymore with a stretch > > postfix installation, since the pathnames changed from > > /usr/lib/postfix/dict_XXX.so to postfix-XXX.so (notice the full path > > removal _and_ the file name change). > > > > I did compare the addmap function from the debian/functions file between > > jessie and stretch and they _do_ differ in the map line generated. > > > > So the map lines already there _do_ need to get updated, either by the > > user > > itself (in such case we should announce it in a README.upgrade or > > equivalent) or by Debian. My opinion here is that the postinst script > > could > > manage this upgrade here without much "conffile" modification conflict. > > :-) > > Hey Scott, > > Did you have any comments to the above? > > (FTR, "dynamicmaps.cf" can't be a conffile unless the original postinst > is RC buggy as it seems to generate dynamicmaps.cf - or are you talking > about a different file?) > > Thanks > ~Niels
I do not think it's the correct fix for the problem. I hope to work on this in the next day or three. This may mask an issue, but it's not a fix. Scott K
