Thanks to both of you. Generally when I've seen these "underscore" updates, I try to recompile and the make file indicates there is nothing to do. But that may be because my configuration file doesn't use a option that caused the "underscore" to be added.
The Freshports page timed out, but assuming bdb is the Berkeley database, I will give the update a try later since I do use that database. Email is critical, so I'm always reluctant to fix what ain't broke! I'm on a VPS, so I image just in the event I can't fix the problem the update caused. Thus far postfix updates haven't broken anything, even going from 2 to 3. Nice work! Original Message From: Łukasz Wąsikowski Sent: Wednesday, August 24, 2016 11:29 PM To: li...@lazygranch.com; Postfix users Subject: Re: Postfix update on Freebsd W dniu 2016-08-25 o 08:09, li...@lazygranch.com pisze: > I'm running Postfix 3.1.1 on Freebsd 10.2. After running portsnap, I see > there is an update. Well sort of. Checking the postfix website, there is no > update, and as you can see, the output from > pkg version -v | grep postfix > > postfix-3.1.1,1 < needs updating (index has 3.1.1_2,1) > > the rev hasn't changed. > > Any ideas what is going on here? Read here about FreeBSD ports naming schemes: https://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html And here you can check what caused PORTREVISION bump: http://www.freshports.org/mail/postfix/ (look at commit history) Change from 3.1.1,1 to 3.1.1._2,1 was caused by cleanup of bdb port (so postfix had to be recompiled) and patch for building with libressl-devel. -- best regards, Lukasz Wasikowski
