Bug 247101 - devel/frink: pets pkg-fallout, adds LICENSE
Summary: devel/frink: pets pkg-fallout, adds LICENSE
Status: Closed DUPLICATE of bug 246163
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Kubilay Kocak
Depends on:
Reported: 2020-06-09 02:47 UTC by Chris Hutchinson
Modified: 2020-06-10 03:33 UTC (History)
0 users

See Also:

patch for devel/frink; pets pkg-fallout, adds LICENSE (993 bytes, patch)
2020-06-09 02:47 UTC, Chris Hutchinson
portmaster: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Hutchinson 2020-06-09 02:47:16 UTC
Created attachment 215382 [details]
patch for devel/frink; pets pkg-fallout, adds LICENSE

This port was recently updated/modified. But the patch
applied wasn't my own (bug #246163). As a result, it
appears to still be broken -- according to the pkg-fallout
messages I receive. The patch attached to this pr fixes
these problems.


NO_MAN=	regretfully ==> MK_MAN=	no

That's it.

Thanks! :-)

Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2020-06-09 02:58:16 UTC
@Chris I am closing this as a dupe of bug 246163, and have re-opened that issue (after closing) it so that the original trail/references are not lost/fragmented in separate issues

*** This bug has been marked as a duplicate of bug 246163 ***
Comment 2 Chris Hutchinson 2020-06-09 16:48:51 UTC
(In reply to Kubilay Kocak from comment #1)
My reason for opening this pr, as opposed to using
bug #246163 is that in bug #246163, mi <at> ALDAN.algebra.com
is listed as MAINTAINER. Whereas currently; I am the
MAINTAINER. So it seemed more prudent and less confusing
to open a different pr. :-)

Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2020-06-10 03:33:16 UTC
(In reply to Chris Hutchinson from comment #2)

The maintainer-feedback flag can and should always be updated to reflect the current maintainer.

New/separate issues should only be created for logically distinct/separate changes, and/or in cases where maintainership or responsibility (assignment) is with different people