Bug 92990
| Summary: | sysutils/fcron | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Brad Huntting <huntting> | ||||
| Component: | Individual Port(s) | Assignee: | Sam Lawrance <lawrance> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | huntting | ||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Class Changed From-To: maintainer-update->change-request Fix category (submitter is not maintainer) State Changed From-To: open->feedback Awaiting maintainers feedback I dont understand, why was this classified as "Fix category (submitter
is not maintainer)" when it was I, the maintainer, who submited the
patch in the first place?
Did I miss something?
brad
P.S. Please apply the patch.
> Maintainer of sysutils/fcron,
>
> Please note that PR ports/92990 has just been submitted.
>
> If it contains a patch for an upgrade, an enhancement or a bug fix
> you agree on, reply to this email stating that you approve the patch
> and a committer will take care of it.
>
> The full text of the PR can be found at:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/92990
State Changed From-To: feedback->open Submitter is maintainer. Brad, the script that changed the PR from maintainer-update is automatic and works by comparing the MAINTAINER address to the submitter's address. The address you sent from didn't match, which is why this one was changed. Responsible Changed From-To: freebsd-ports-bugs->lawrance Take it. State Changed From-To: open->closed Committed, thanks! |
The new stable release (3.0.1) of fcron: Changes to the port include: Update version from fcron version 3.0.0 to fcron version 3.0.1. Changed MASTER_SITES and PORTVERSION appropriately. 'fcrondyn' is now installed with the port. This was previously disabled because it activated a bug which passed a bad timeval to select(). French documentation should be installed if MANLANG=fr Added Installation reminder about installing pam files. Since nothing works without them, should we just install the pam files in ${DESTDIR}/pam.d/ (assuming they dont already exist)? fcron pseudouser and group are now created (if necessary) with uid,gid=247 (<1000). This should prevent the fcron pseudouser from showing up as a regular user on login screens like kdm and gdm. Fix: ------------------------------ cut here ------------------------------