Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Nov 2005 13:07:15 -0700
From:      Danny MacMillan <flowers@users.sourceforge.net>
To:        "Michael C. Shultz" <ringworm01@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: portmanager -slid deletes the wrong port!
Message-ID:  <4374F9F3.8030806@users.sourceforge.net>
In-Reply-To: <200511092320.38002.ringworm01@gmail.com>
References:  <4372EE56.3060802@users.sourceforge.net> <200511092320.38002.ringworm01@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Michael C. Shultz wrote:
> On Wednesday 09 November 2005 22:53, Danny MacMillan wrote:
>>
>>I'm running portmanager to do some port maintenance on one of my
>>servers.  I'm trying to delete devel/cvs2svn.  Each time I try to delete
>>it, it deletes devel/python instead.  This is exceedingly disconcerting.
> 
> Just underwent major revision, bound to be a few glitches, sorry about that.
> The upgrade portion is pretty solid but looks like you might have found a bug 
> in -slid, if so I'll post a fix tomorrow. If your not at version 0.3.3_2 then 
> cvsup again and let me know for sure if that version has this problem.

Hi, Mike.

The version of portmanager I was using when I experienced the problem
was definitely 0.3.3_2; I verified the version when I saw it was
misbehaving.  And although this is somewhat belated, here's the uname -a
output on the affected system:

FreeBSD hobbit.emerald-associates.com 6.0-RELEASE FreeBSD 6.0-RELEASE
#0: Wed Nov  9 04:09:55 MST 2005
root@hobbit.emerald-associates.com:/usr/obj/usr/src/sys/HOBBIT  i386

After portmanager failed to work properly with cvs2svn, I did not
attempt to use it to delete any other ports, so cvs2svn is the only case
I know wasn't working.  I used pkg_delete to delete cvs2svn instead, so
I can not verify the operation of the updated portmanager by using it to
delete that port.  However, I just upgraded to the latest version of
portmanager (0.3.4) and tested it against a different package and it
worked properly.  Unless you receive other problem reports, I'd call the
issue resolved.

Thanks for the speedy response.

-- 
Danny MacMillan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4374F9F3.8030806>