From owner-freebsd-ports@freebsd.org Wed Jan 17 04:12:24 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90ABBE78B7F for ; Wed, 17 Jan 2018 04:12:24 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.io-tx.com", Issuer "AlphaSSL CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69F477B26C for ; Wed, 17 Jan 2018 04:12:23 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.15.2/8.15.2) with ESMTPSA id w0H41dFY033692 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Jan 2018 22:01:39 -0600 (CST) (envelope-from ted@io-tx.com) Date: Tue, 16 Jan 2018 22:01:39 -0600 (CST) From: Ted Hatfield To: Dave Horsfall cc: FreeBSD Ports Subject: Re: Mailman has mismatched checksums In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.99.2 at io-tx.com X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=5.0 on io-tx.com tests=ALL_TRUSTED, AWL, T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 user=root X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on io-tx.com X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 04:12:24 -0000 Dave, The same thing happened to me. I am also running mailman-2.1.25. I pulled the Defaults.py and Defaults.pyc from the package distribution file and did a diff on the pkg files and the installed files and this is what I found. diff Defaults.py /tmp/Defaults.py < DEFAULT_EMAIL_HOST = 'mailman.obfucscated.com' < DEFAULT_URL_HOST = 'mailman.obfuscated.com' --- > DEFAULT_EMAIL_HOST = '//' > DEFAULT_URL_HOST = '//' 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. Since I have DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST set in my mm_cfg.py file I assume it's safe to reset these variables in the Defaults.py file but I haven't taken the time to test it yet. I hope this helps. Ted Hatfield On Wed, 17 Jan 2018, Dave Horsfall wrote: > When trying to get Mailman going (and seeing what looked like several updates > in quick succession), I completely cleaned it out, waited a bit for any more > updates, installed the package, waited a bit for any more updates, and I was > hoping that this would go away: > > 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 > > No configuration whatsoever was done; I merely installed the package and > waited for any more updates to arrive. > > So, what can I do about it? > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will > suffer." > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >