Date: Thu, 18 Jan 2018 10:10:20 +1100 (EST) From: Dave Horsfall <dave@horsfall.org> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Mailman has mismatched checksums Message-ID: <alpine.BSF.2.21.1801180953590.53849@aneurin.horsfall.org> In-Reply-To: <alpine.BSF.2.20.1801162200140.33525@io-tx.com> References: <alpine.BSF.2.21.1801170754350.53849@aneurin.horsfall.org> <alpine.BSF.2.20.1801162200140.33525@io-tx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Jan 2018, Ted Hatfield wrote:
> My best guess is that some time in the past I changed the variables
> DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in the Defaults.py file rather
> than mm_cfg.py, and the files Defaults.py and Defaults.pyc didn't change
> when I did a pkg update.
After further investigation (a complete removal of Mailman, updated the
"locate" database, and confirmed that not a skerrick of Mailman was left
on the server), I did another installation of the package (not the port),
and stood back and waited for the overnight check.
And...
Checking for packages with mismatched checksums:
mailman-2.1.25: /usr/local/mailman/Mailman/Defaults.py
mailman-2.1.25: /usr/local/mailman/Mailman/Defaults.pyc
Suspicious (since *I* hadn't touched anything), I looked further, and
found:
DEFAULT_EMAIL_HOST = 'aneurin.horsfall.org'
DEFAULT_URL_HOST = 'aneurin.horsfall.org'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
In other words, the installation gratuitously changes a file that by its
own admission should not be changed, and then the system has the hide to
complain that it has been changed i.e. it installs itself as
pre-corrupted...
I'm surprised that this breakage hasn't been noted until now.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1801180953590.53849>