#4829 closed defect (invalid)
can't activate openssh after upgrade
Reported by: | vincent-opdarw@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.0 |
Keywords: | Cc: | ||
Port: |
Description
I've upgraded openssh to 4.2_0, but it couldn't be activated.
$ sudo port -d activate openssh 4.2_0 ---> Activating openssh 4.2_0 DEBUG: Image error: /Library/StartupItems/OpenSSH already exists and does not belong to a registered port. Unable to activate port openssh.
while executing
"_activate_contents $name $imagefiles $imagedir"
(procedure "portimage::activate" line 50) invoked from within
"portimage::activate $portname $portversion" port activate failed: Image error: /Library/StartupItems/OpenSSH already exists and does not belong to a registered port. Unable to activate port openssh.
Same problem with openssh 4.1_0.
Change History (3)
comment:1 Changed 19 years ago by vincent-opdarw@…
Summary: | can't active openssh after upgrade → can't activate openssh after upgrade |
---|
comment:2 Changed 19 years ago by olegb@…
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 Changed 19 years ago by vincent-opdarw@…
Yes, I forgot I had reinstalled these files as a workaround of an openssh bug (which is still present, BTW).
As you might have expected, upgrade will *not* overwrite any of your files unless you ask it to with force (-f).
When activating openssh there was a file "in the way", so upgrade/activation fails - If you dont care about your /Library/StartupItems/OpenSSH (you installed it *not*darwinports) use -f when upgrading and darwinports wont yell about it.
This is *not* a bug! It is sane expected behaviour. Read port(1) for more information.