DPorts: don't sync past 1819967

Matthew Dillon dillon at backplane.com
Thu Feb 16 15:16:59 PST 2017

Ok, we've fixed the DragonFly git mirrors for dports, so the stay is
lifted.  However, this required doing a reset HEAD~4.  Anyone who updated
their dports repo in the last 2 days probably needs to do some fixing up.

In your dports you need to clean out the last few commits, reset the HEAD,
then re-pull.  In the example below the git checkout I do just makes sure
that everything is clean before re-pulling.  If you are working on a
repo-only git repo without a working tree, use --soft instead of --hard.

git reset --hard 18199674ad72bd93914f38
git checkout .
git pull


On Thu, Feb 16, 2017 at 2:24 PM, John Marino <dragonflybsd at marino.st> wrote:

> The last 4 commits on DPorts are wrong.
> The dragonfly dports mirror was pointing at jrmarino/DPorts which in turn
> was pointing at DragonFlyBSD/DPorts.
> I forked DragonFlyBSD/DPorts and now the mirror is reflecting my local
> changes.  Matt has to fix this.
> This is the last good commit:
> https://gitweb.dragonflybsd.org/dports.git/commit/18199674ad
> 72bd93914f38e4acb89cecf1f9541f
> Don't use anything past that if you build from source until this is sorted
> out.
> John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20170216/aa4bf99c/attachment.html>

More information about the Users mailing list