Date: Sun, 24 Jan 2021 21:20:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 252983] Error in Makefile for comms/hackrf-devel Message-ID: <bug-252983-7788-Hw4fCdOlAy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252983-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-252983-7788@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=3D252983 --- Comment #2 from Robert William Vesterman <bob@vesterman.com> --- I see that the change that broke this (ports r562478) has now been reverted (ports r562511) "to unbreak INDEX", but I've since done a "portsnap fetch update" and received the same error. The comms/hackrf-devel directory was actually created (as a copy of comms/hackrf) in the change that had been reverted, but it still exists on = my machine (even after the "portsnap fetch update"). If I do a "pkg search hackrf-devel", it does NOT show up, though, so (if I'm understanding correc= tly) I guess its entry did get removed from the index, but /usr/ports/comms/hackrf-devel didn't get removed, and synth still checks it (and still gets the same error). I do not know enough about the low-level details of the ports system to kno= w if any or all of this is expected, or in any case what to do about it. Should I just "rm -rf /usr/ports/comms/hackrf-devel"? --=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-252983-7788-Hw4fCdOlAy>