[Bug 229906] mail/thunderbird-i18n: Insane sanity check

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Jul 20 16:46:49 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229906

            Bug ID: 229906
           Summary: mail/thunderbird-i18n: Insane sanity check
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: gecko at FreeBSD.org
          Reporter: se at FreeBSD.org
             Flags: maintainer-feedback?(gecko at FreeBSD.org)
          Assignee: gecko at FreeBSD.org

The sanity check in the thunderbird-i18n port breaks upgrades with portmaster,
since distfiles are fetched before the port build starts. 

Specifically, if both thunderbird and thunderbird-i18n are to be upgraded, then
make checksum will be performed in the background, while the old thunderbird
version is still installed.

This results to an error, which can easily be reproduced with "make
check-sanity" in mail/thunderbird-i18n, while an outdated thunderbird package
is installed:

# make check-sanity
===>  thunderbird-i18n-60.0 cannot install: thunderbird versions mismatch:
thunderbird-52 is installed and wanted version is thunderbird-.
*** Error code 1

This sanity check is valid when the i18n port is going to be built, but it
prevents fetching of the distfiles for version 60 while version 52 is still in
use.

I did not find a way to perform "make fetch checksum" (which implies "make
check-sanity") in this case. (Is there some parameter, e.g. NO_SANITY, which
prevents these checks, if I know they'll be later performed before the port is
extracted?)

Since I did not check whether other ports are affected in similar ways, I do
not know whether this should rather be a defect against the ports framework ...

A secondary defect is the incomplete error message: "wanted version is
thunderbird-.", but I'd rather get rid of the error abort and do not care too
much about that particular message.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list