Bug 184281 - Update mail/dcc-dccd to 1.3.152
Summary: Update mail/dcc-dccd to 1.3.152
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-25 11:10 UTC by nagy.attila
Modified: 2014-08-19 14:52 UTC (History)
3 users (show)

See Also:

Attachments
file.diff (845 bytes, patch)
2013-11-25 11:10 UTC, nagy.attila 		no flags Details | Diff
patch-dcc-dccd-1.3.154.txt (912 bytes, patch)
2014-04-20 06:46 UTC, Alexander Moisseev 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description nagy.attila 2013-11-25 11:10:00 UTC 
Attached is a patch to upgrade mail/dcc-dccd to its latest release, 1.3.152

Fix: Patch attached with submission follows:
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-11-25 11:10:08 UTC 
Maintainer of mail/dcc-dccd,

Please note that PR ports/184281 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/184281

-- 
Edwin Groothuis via the GNATS Auto Assign Tool
edwin@FreeBSD.org
Comment 2 Edwin Groothuis freebsd_committer freebsd_triage 2013-11-25 11:10:09 UTC 
State Changed
From-To: open->feedback

Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
Comment 3 Alexander Moisseev 2014-04-20 06:46:28 UTC 
Update to 1.3.154
Comment 4 John Marino freebsd_committer freebsd_triage 2014-07-12 00:18:34 UTC 
The maintainer, Craig, is going to get reset soon since this port isn't staged.

These updates are not sufficient, they need to provide stage support.
Comment 5 John Marino freebsd_committer freebsd_triage 2014-07-12 00:19:49 UTC 
(Repeat for Alexander)

The maintainer, Craig, is going to get reset soon since this port isn't staged.
These updates are not sufficient, they need to provide stage support.
Comment 6 John Marino freebsd_committer freebsd_triage 2014-07-12 00:20:18 UTC 
(Repeat for Alexander #2, bugzilla issue)

The maintainer, Craig, is going to get reset soon since this port isn't staged.
These updates are not sufficient, they need to provide stage support.
Comment 7 Alexander Moisseev 2014-07-12 05:48:43 UTC 
(In reply to John Marino from comment #6)
> (Repeat for Alexander #2, bugzilla issue)
> 
> The maintainer, Craig, is going to get reset soon since this port isn't
> staged.
> These updates are not sufficient, they need to provide stage support.

I am not interested in maintainership because I am not use the port.
Comment 8 John Marino freebsd_committer freebsd_triage 2014-07-12 07:32:55 UTC 
The point wasn't if the port is maintained or not.

The port is not staged.
The current maintainer is going to be reset for failing to stage it.  When that happens, the port will be deprecated.  If still nobody stages it, the port will be removed.

So a patch that updates the version also needs to provide stage support - that's the point.
Comment 9 John Marino freebsd_committer freebsd_triage 2014-07-27 10:41:30 UTC 
This port is no longer maintained.
This PR will not be applied because it doesn't add stage support.
The port will be removed in a few weeks unless this patch is updated to include stage support.
Comment 10 John Marino freebsd_committer freebsd_triage 2014-08-19 14:52:28 UTC 
upgrade will not happen on unstaged port, closing.