Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 Jul 2016 13:30:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 210873] security/hashcat: move to security/hashcat-legacy
Message-ID:  <bug-210873-13-1WlaW5z2b9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210873-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-210873-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210873

Matthew Seaman <matthew@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthew@FreeBSD.org
           Assignee|freebsd-ports-bugs@FreeBSD. |matthew@FreeBSD.org
                   |org                         |

--- Comment #1 from Matthew Seaman <matthew@FreeBSD.org> ---
The MOVED entry would have the effect that users of the existing
security/hashcat will automatically update to security/hashcat-legacy.

If the intention is that users should update to the new-codebase version of
security/hashcat instead, then I should copy security/hashcat to
security/hashcat-legacy and apply the upgrade to security/hashcat in close
proximity.  In which case, could you add a patch with the security/hashcat
changes to this PR please? For this alternative an UPDATING entry to suggest
installing hashcat-legacy if desired would be a good idea.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210873-13-1WlaW5z2b9>