Opened 9 years ago

Closed 7 years ago

#33179 closed defect (wontfix)

xymon and xymon-server disagree about whether clientlaunch.cfg should be registered to the port or not

Reported by: ryandesign (Ryan Schmidt) Owned by: fclaire@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc:
Port: xymon

Description

Installing xymon, then uninstalling xymon, then installing xymon-server, results in an activation failure:

$ sudo port install xymon-server
--->  Computing dependencies for xymon-server
--->  Fetching archive for xymon-server
--->  Attempting to fetch xymon-server-4.3.7_0.darwin_10.x86_64.tbz2 from http://packages.macports.org/xymon-server
--->  Fetching xymon-server
--->  Verifying checksum(s) for xymon-server
--->  Extracting xymon-server
--->  Applying patches to xymon-server
--->  Configuring xymon-server
--->  Building xymon-server
--->  Staging xymon-server into destroot
--->  Installing xymon-server @4.3.7_0
--->  Activating xymon-server @4.3.7_0
Error: Target org.macports.activate returned: Image error: /opt/local/lib/xymon/client/etc/clientlaunch.cfg already exists and does not belong to a registered port.  Unable to activate port xymon-server. Use 'port -f activate xymon-server' to force the activation.
Log for xymon-server is at: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_net_xymon-server/xymon-server/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Change History (2)

comment:1 Changed 9 years ago by fclaire@…

Thanks for reporting this problem.

xymon and xymon-server packages conflict each other and only one should be installed on a given machine. The workaround is to remove the directories ${prefix}/lib/xymon and ${prefix}/var/log/xymon.

This behavior is coming from the way config files are managed. I followed what's recommended here: https://trac.macports.org/wiki/PortfileRecipes#configfiles "The current solution is to rename any config files to append a .dist or .sample extension to them so that the proper name of the config file is not part of the port."

I'm doing this in the post-destroot phase:

post-destroot {
    xinstall -d -o ${xymonuser} -g ${xymongroup} ${destroot}${xylogdir}
    xinstall -d -o ${xymonuser} -g ${xymongroup} ${destroot}${xytmpdir}
    # Adding a suffix to config files
    foreach f { clientlaunch.cfg localclient.cfg xymonclient.cfg } {
        move ${destroot}${xyetcdir}/${f} ${destroot}${xyetcdir}/${f}.${version}
    }
}

Is it the wrong phase ? Why does the port believes the original .cfg file belong to the other xymon port ?

When will #2365 be closed ?

comment:2 Changed 7 years ago by mf2k (Frank Schima)

Resolution: wontfix
Status: newclosed

Closing this since the xymon port is now a stub.

Note: See TracTickets for help on using tickets.