Opened 6 months ago

Closed 6 months ago

#60410 closed defect (worksforme)

gnuradio: gnuradio-runtime.conf already exists and does not belong to a registered port

Reported by: ea3iav Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: Cc:
Port: gnuradio


I have followed rearly all procedures I have found. I have installed all dependencies and apps asked on several tutorials. Mac Ports is installed but I can't go any further I am using Mac OSx mojave 10.14.6 (18G4032)

Attachments (1) (771.6 KB) - added by ea3iav 6 months ago.

Download all attachments as: .zip

Change History (4)

Changed 6 months ago by ea3iav

Attachment: added


comment:1 Changed 6 months ago by ryandesign (Ryan Schmidt)

Keywords: gnuradio removed
Milestone: MacPorts 2.6.3
Owner: set to michaelld
Port: gnuradio added
Status: newassigned
Summary: Unable to install Gnuradiognuradio: gnuradio-runtime.conf already exists and does not belong to a registered port

The relevant error in the log appears to be:

:error:activate Failed to activate gnuradio: Image error: /opt/local/etc/gnuradio/conf.d/gnuradio-runtime.conf already exists and does not belong to a registered port.  Unable to activate port gnuradio. Use 'port -f activate gnuradio' to force the activation.

Do you know why this file already exists?

Is this a configuration file that users are intended to edit?

comment:2 Changed 6 months ago by michaelld (Michael Dickens)

This file is a "default" configuration file. You can edit it in place or copy it to a local location and edit it there to specify runtime preferences. I'd recommend just removing that file then trying the install again; hopefully this time it will install cleanly. If any other such files are found inside /opt/local for when activating GNU Radio, I'd think you can safely remove them.

comment:3 Changed 6 months ago by michaelld (Michael Dickens)

Resolution: worksforme
Status: assignedclosed

FYI this is not an issue with MacPorts or the GNU Radio port itself. This is an issue with your specific install. We can't say why; stuff happens! I'm closing this issue as "worksforme" since it does. I regularly rebuild and install GR with different patches to test them, and MacPorts makes this simple and easy; I almost never have issues with stray files, and when I do I can safely say I know it's because I installed something into /opt/local outside of MacPorts & hence it is my "fault".

Note: See TracTickets for help on using tickets.