https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218673

Jan Beich <jbe...@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|freebsd-ports-bugs@FreeBSD. |freebsd-bugs@FreeBSD.org
                   |org                         |
           Hardware|amd64                       |Any
           Severity|Affects Only Me             |Affects Some People
            Version|Latest                      |11.0-RELEASE
                 CC|freebsd-ports-bugs@FreeBSD. |
                   |org                         |
          Component|Individual Port(s)          |bin
            Summary|graphics/opencv-core: fails |graphics/opencv-core: fails
                   |to build                    |to build because
                   |                            |portsnap(8) didn't purge
                   |                            |old files
            Product|Ports & Packages            |Base System

--- Comment #11 from Jan Beich <jbe...@freebsd.org> ---
(In reply to Peter C B Henderson from comment #10)
> downloading the correct file using portsnap

Many ports/ committers use portsnap + poudriere to do QA. In my case the
"default" tree was (re)created on -CURRENT around 2015-11-13 and catched both
renames without issues.

portsnap(8) stores its state under /var/db/portsnap by default (.snap for
poudriere). To learn more why it got inconsistent after regular usage you may
need to upload the state and the tree just before the bad update. Even if
portsnap(8) got confused how "graphics/opencv" directory disappeared then
reappeared it doesn't explain why up ports r423215 is missing despite being
*before* the rename.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to