[Bug 251196] mail/nullmailer: upgrade problem
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Nov 16 23:47:19 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251196
Bug ID: 251196
Summary: mail/nullmailer: upgrade problem
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: uffe at uffe.org
Hi,
Last week I submitted bug 251074 - mail/nullmailer: update to 2.2
My patch was accepted and over the weekend it seems that the new nullmailer-2.2
package has been built and have become available for all users as an update to
the old nullmailer-1.13 package...
Before submitting the port patch for nullmailer I have done numerous pkg
delete/install etc on my own system to test the install/upgrade scenarios...
But the only thing that I could not test locally now seems to fail... upgrade
For some reason pkg upgrade works different that the local pkg install/delete
operations...
My guess is that it must have something to do with the inner workings of the
new pre/postexec and pre/postunexec - but I miss a clear picture here...
Scenario:
1) I had the old nullmailer-1.13 package installed
2) over the weekend the new nullmailer-2.2 package became available online
3) On my local system I somply issued "pkg upgrade" - and nullmailer was
upgraded to the new version 2.2
4) after the upgrade the the filesystem fifo file that should be located here
/var/spool/nullmailer/trigger is missing.
5) the missing /var/spool/nullmailer/trigger fifo file will cause nullmailer to
commit (queue) new mails to disk - but never send them :-S
6) uninstalling nullmailer-2.2 and installing nullmailer-2.2 again fixed the
problem - but upgrades should work as well
I hope that you can help here - the problem is quite urgent as nullmailers
users that perform the package upgrade seems to have all their new mails stuck
in their queues forever after upgrade :-S
Thanks in advance
/Uffe
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list