From owner-freebsd-ports-bugs@freebsd.org Wed Mar 3 17:42:49 2021 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 1C0D554A03E for ; Wed, 3 Mar 2021 17:42:49 +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 4DrLtd05mGz4cB6 for ; Wed, 3 Mar 2021 17:42:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0354454A4DA; Wed, 3 Mar 2021 17:42:49 +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 0316954A245 for ; Wed, 3 Mar 2021 17:42:49 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DrLtc6bCJz4cH2 for ; Wed, 3 Mar 2021 17:42:48 +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 D4A7A5C57 for ; Wed, 3 Mar 2021 17:42:48 +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 123HgmDW092939 for ; Wed, 3 Mar 2021 17:42:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 123Hgmvd092938 for ports-bugs@FreeBSD.org; Wed, 3 Mar 2021 17:42:48 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 253567] sysutils/anacron: does not start after resume Date: Wed, 03 Mar 2021 17:42:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed 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 Some People X-Bugzilla-Who: walter.von.entferndt@posteo.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? merge-quarterly? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: 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: Wed, 03 Mar 2021 17:42:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253567 Walter von Entferndt changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|Closed |In Progress --- Comment #7 from Walter von Entferndt = --- I can't see the fix in the updates of the /latest/ ports branch (I have both latest & quarterly). What can I do to help get that done? Was it that I changed the state to "fixed/CLOSED" is preventing an update? Then it's a b= ug in this web interface: it should not allow me to set such flags when I'm not supposed to do that. Maybe it's just that the maintainer is busy with other stuff, and we'll see an update in a week or two, that's fine with me. Should I file in a bug report on that a bug reporter should not be allowed = to set "maintainer approval"? Now the description was updated to be more prec= ise? Seems I misunderstood this. "Set (?) to request MAINTAINER approval" Since the maintainer's e-mail is known to the system, I found it logical the syst= em asks for my e-mail address here (although that's known, too). My english is= not overly bad (english =3D ancient gaelic? + ancient german with latin grammat= ics, loosely speaking), so this must have been much more misleading for others w= hose native tongue is further away from english. --=20 You are receiving this mail because: You are the assignee for the bug.=