Bug 234278 - mail/opendkim: not included in pkg on fbsd 12? mimedefang does not run anymore after update!
Summary: mail/opendkim: not included in pkg on fbsd 12? mimedefang does not run anymor...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Kubilay Kocak
Depends on: 223568
  Show dependency treegraph
Reported: 2018-12-22 20:17 UTC by mam
Modified: 2019-01-07 12:02 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description mam 2018-12-22 20:17:40 UTC
After upgrade to 12.0 my opendkim is gone and cannot be found in the pkg repositories. It IS listed in the ports tree, but no binary package is available (yet?).

This is a bit annoying, the update broke my mailserver and its quite hard to get it back up running (sendmail with opendkim and mimedefang).

Part 2 deals with mimedefang/spamassassin. After the update all mails are rejected because the old compiled rules are not accepted by the new binaries. This is just annoying, you need to delete the rule dir and run sa-compile to get it back up. The killer problem for a newbie is that before you delete the old rules, sa-compile refuses to run too with the same evil error message. You need to be bold and delete them, then sa-compile runs again and creates a new set of rules. Afterwards everything is running smoothly again.
Comment 1 Daniel Austin 2018-12-22 20:38:28 UTC
(In reply to mam from comment #0)
Please see:


It's waiting to be merged into the quarterly branch :-(
Comment 2 mam 2018-12-22 20:44:12 UTC
tnx for the info. 
I will stop updates to 12 on the other machines until all packages are available again.
(Luckily this was only a backup testing machine, no real harm was done yet.)
Comment 3 Daniel Austin 2018-12-22 20:45:30 UTC
(In reply to mam from comment #2)
if you use "latest" instead of "quarterly" branch in your pkg.conf, it will work - but latest is not as stable as the quarterly branch of course.
Comment 4 mam 2018-12-22 20:52:48 UTC
tnx again, I will wait then.
Its not because I am afraid of stability, I just do not want to change defaults unless it is not desperately needed. 

And I am not really in a hurry, the servers are running fine, no need to update or change anything. 

I can wait another few months and retry then..
Comment 5 mam 2018-12-23 07:16:56 UTC
Ok, I see, the problem with opendkim has already been solved, sorry for reporting it again but my bughunt here did not show me the already "bug in progress".

So the real bug is that the documentation for FBSD 12 Update does not contain a warning about the unavailability of the port. You could state that it only will be a temporally problem, but the DVDs are out and also lack the port. DVD update wont happen too soon, so its likely that some more people will face the problem in the future.

should i file a different but report for the wrong update of mimedefang here or does somebody already noted that there needs to be a change done?
Comment 6 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-23 08:30:59 UTC
(In reply to mam from comment #5)

I would report the mimedefang/spamassassin issue separately, such that it can be addressed by the maintainer(s) of those ports independently.

On the opendkim package not being available, you are correct that it is a temporary issue, and also correct that that unfortunately means that for ISO images that include packages, will be missing opendkim.

However, it is not strictly limited to opendkim, but also any port that wasn't able to be build its package at the time of release (on the quarterly branch), which includes any port that didn't build with OpenSSL at the time (a large list, See Also: bug 231931), but also for any other reason (an additional long list).

At a higher level, I'm not sure what could or should be done to improve the situation in a viable way.

If we were for example to re-roll the DVD images to get opendkim back in (once its fixed), then we would also want to do that for other (all?) ports/packages. Further, -RELEASES are 'supposed' (intended) to ship packages that were current at the time of the release. The only way to absolutely resolve the issue would be to have a quarterly branch that had 'no' failures at some point in time, and snapshot that, which I can't see being possible.

On the issue of documenting such issues of missing packages, the list would be non-trivial, and only marginally valuable, in that the documentation would need to be read first, and only if the user hadn't already identified the problem post install already.

On the "and also lack the port" issue, as soon as bug 223568 is closed (the reason I depended on it), anyone using the default quarterly ports tree on 12.0-RELEASE will be able to build it.

The best short answer here is going to look/sound something like "The packages on DVD images are at best a quickly-outdated, best-effort source of packages for users that have major challenges with regard to bandwidth/compute resources, so much so that using the FreeBSD package mirrors or the ports framework to fetch sources and build them, instead, is not viable."
Comment 7 mam 2018-12-23 10:12:33 UTC
(In reply to Kubilay Kocak from comment #6)
I see the problem, I know there is no satisfying solution.

I am using FBSD for some decades now (I guess, I've started with 4.0 or 4.5), never had problems with updates before.

(dont get me wrong, I do not complain, you folks are doing a great work and I am grateful for it)

My (and I guess a lot of other people's too) main reason for using it is stability, and reliability. I dont need fancy things or "always the newest" stuff. 

Ahead of a major Update, I do read the release notes, they should contain warnings about things like this. 

Ok, I agree, the port stuff does not belong to the OS, therefor the release notes are not really the correct place to put in such a warning, but it is the only thing an external person gets to see, so please take it into consideration.

my personal vote would have been: Do not release 12.x at all until all mayor ports are back up running and included. One could have long discussion if something belongs to a "mayor port" or not, but if you focus on server features then it is fairly easy to decide what is needed and what can be left out. For a "real" mailserver today, a blank sendmail is surely not enough anymore. But this is only my personal opinion, to critics.

keep on the good work!
Comment 8 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-28 06:24:58 UTC
I'm happy to wait for the dependent bug to be closed before closing this issue. At least then anyone using the default package repository configuration on 12.0 will be able to install the package, as well as anyone using (latest) quarterly ports
Comment 9 Kubilay Kocak freebsd_committer freebsd_triage 2019-01-07 12:02:15 UTC
New quarterly branch has been cut, and the head commit from bug 223568 that fixes the build with OpenSSL 1.1.x is now in the (new) 2019Q1 branch.