From owner-freebsd-ports-bugs@freebsd.org Mon Nov 16 23:47:19 2020 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1B9D2475200 for ; Mon, 16 Nov 2020 23:47:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4CZm2b05Lhz4kwZ for ; Mon, 16 Nov 2020 23:47:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 031F4475190; Mon, 16 Nov 2020 23:47:19 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 02E80474DEB for ; Mon, 16 Nov 2020 23:47:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CZm2Z6cGCz4lJ0 for ; Mon, 16 Nov 2020 23:47:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CBFB216796 for ; Mon, 16 Nov 2020 23:47:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0AGNlIY3068749 for ; Mon, 16 Nov 2020 23:47:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0AGNlIUF068748 for ports-bugs@FreeBSD.org; Mon, 16 Nov 2020 23:47:18 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251196] mail/nullmailer: upgrade problem Date: Mon, 16 Nov 2020 23:47:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: uffe@uffe.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2020 23:47:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251196 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@FreeBSD.org Reporter: uffe@uffe.org Hi, Last week I submitted bug 251074 - mail/nullmailer: update to 2.2=20 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... upgra= de For some reason pkg upgrade works different that the local pkg install/dele= te 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 he= re /var/spool/nullmailer/trigger is missing. 5) the missing /var/spool/nullmailer/trigger fifo file will cause nullmaile= r 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 st= uck in their queues forever after upgrade :-S Thanks in advance /Uffe --=20 You are receiving this mail because: You are the assignee for the bug.=