Date: Sun, 08 Jan 2006 08:05:18 +0900 From: KOMATSU Shinichiro <koma2@lovepeers.org> To: Ceri Davies <ceri@submonkey.net> Cc: ports@freebsd.org, Mike Jakubik <mikej@rogers.com> Subject: Re: Portupgrade confused about editors/emacs Message-ID: <43C0492E.3080802@lovepeers.org> In-Reply-To: <20060106132130.GB86645@submonkey.net> References: <834B3A07-EC76-4645-8E1B-7ABEA4EC999A@submonkey.net> <43BE57E9.9060507@rogers.com> <20060106132130.GB86645@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ceri Davies wrote:
> On Fri, Jan 06, 2006 at 06:43:37AM -0500, Mike Jakubik wrote:
>
>>Ceri Davies wrote:
>>
>>>After today's portsnap run:
>>>
>>> # portversion -v emacs
>>> emacs-21.3_9 > succeeds port (port has 19.34b_1) (=>
>>>'editors/emacs19')
>>>
>>>I thought that this may have been my fault, so I removed the package
>>>and reinstalled from the editors/emacs port, but the result is the
>>>same. I assume that this is down to the ordering of these two lines
>>>in /usr/ports/MOVED, but then I don't see why I haven't seen this
>>>problem before:
>>>
>>> editors/emacs|editors/emacs19|2004-03-20|emacs 19.x moved to a
>>>non-default port location
>>> editors/emacs21|editors/emacs|2004-03-20|emacs 21.x moved to default
>>>port location
>>
>>If you are using portupgrade-2.0.1 then know that its broken, and cant
>>deal with moved ports well. The issue has been brought up many times,
>>but it doesn't seem like anything is being done about it. A continuing
>>trend for freebsd it seems.
>
>
> It seems that the commit on January 3rd tried to address this exact
> issue, but failed. Thanks for the info.
Yes, I tried to fix this issue on portupgrade-2.0.1,
but later I knew it failed.
I am now trying to work out this, but until then,
when you find a port that causes problem,
please add it to IGNORE_MOVED in pkgtools.conf such as:
IGNORE_MOVED = [
'editors/emacs',
]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43C0492E.3080802>