Solved BSDSAR installation fails.

I am attempting to install the following package with ports, however it fails with the following.

Code:
====> Compressing man pages (compress-man)
===>  Installing for bsdsar-1.10_2
===>  Checking if bsdsar already installed
===>  Registering installation for bsdsar-1.10_2
pkg-static: Unable to access file /usr/ports/sysutils/bsdsar/work/stage/usr/local/bin/bsdsar: No such file or directory
pkg-static: Unable to access file /usr/ports/sysutils/bsdsar/work/stage/usr/local/bin/bsdsar_gather: No such file or directory
pkg-static: Unable to access file /usr/ports/sysutils/bsdsar/work/stage/usr/local/etc/bsdsar.conf.sample: No such file or directory
pkg-static: Unable to access file /usr/ports/sysutils/bsdsar/work/stage/usr/local/share/doc/bsdsar/CHANGELOG: No such file or directory
pkg-static: Unable to access file /usr/ports/sysutils/bsdsar/work/stage/usr/local/share/doc/bsdsar/README: No such file or directory
pkg-static: lstat(/usr/ports/sysutils/bsdsar/work/stage/usr/local/share/doc/bsdsar/): No such file or directory
*** Error code 74

Stop.
make: stopped in /usr/ports/sysutils/bsdsar

I have never had this issue before and have already updated the ports collection with the latest fetch.

Code:
# which bsdsar_gather
/usr/local/bin/bsdsar_gather

# which bsdsar
/usr/local/bin/bsdsar

# make deinstall clean
===>  Deinstalling for bsdsar
===>  bsdsar not installed, skipping
===>  Cleaning for bsdsar-1.10_2

# ls /usr/local/bin/bsd
bsdcpio*  bsdsar*  bsdsar_gather* bsdtar*

Mail keeps spamming with the following from the installed crontab.

Code:
Message 3:
From root@redacted Fri Mar 25 04:00:03 2016
Date: Fri, 25 Mar 2016 04:00:00 -0400 (EDT)
From: root@redacted (Cron Daemon)
To: root@redacted
Subject: Cron <root@redacted>  /usr/local/bin/bsdsar_gather
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>

/usr/local/bin/bsdsar_gather: not found

Can anybody tell me what I am doing wrong here?
 
You - maybe nothing. The port may be broken in some way. What I find interesting is that I do not have this port in my ports tree, how can that be? Is that port really really new, or is your ports tree outdated?

I would check if the files which are complained about are listed in the pkg-plist and try to remove them from there, as a quick workaround. That might get it past this, but if it will be a solution I can not say.
 
Apparently this port had expired some years ago not sure why it's still showing up in my ports tree.

Code:
# grep -i bsdsar MOVED
MOVED:sysutils/bsdsar||2013-03-03|Has expired: No more upstream, no more public distfiles

I ran a portsnap fetch update last night and I thought this should have removed any dated ports. I generally do an upgrade on my ports every couple of months.

The MOVED file actually shows quite a handful of expired ports.

I ended up running a script against those ports in the MOVED file to delete those ports.

Is there a cleaner way of doing that in the future?
 
i think portsnap frequently misses cleanups.
You can blow /usr/ports away (included cache) and redo the whole portsnap fetch extract or just switch to svn instead.
 
I was hoping that was the cause of it missing on the cleanup and not a larger problem. I'm kinda lazy and didn't want to reconfigure my config files for a full fetch on ports.

I had forgotten that svn can be used for ports and I will have to do some reading on that.
 
Back
Top