Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Apr 2009 11:40:05 GMT
From:      Donald Allen <donaldcallen@gmail.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: misc/133957: /usr/ports/security/gnome-keyring fails to build
Message-ID:  <200904241140.n3OBe5jN000217@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/133957; it has been noted by GNATS.

From: Donald Allen <donaldcallen@gmail.com>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: misc/133957: /usr/ports/security/gnome-keyring fails to build
Date: Fri, 24 Apr 2009 07:31:02 -0400

 --000325579e82d9c0ef04684b5476
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: 7bit
 
 I encountered this error in attempting to upgrade epiphany using
 portupgrade. I subsequently tried the epiphany upgrade using portmaster and
 succeeded, which included getting this port compiled and installed. I'm
 guessing that the ordering of the upgrading of the ports matters and
 portmaster got it right and portupgrade didn't (or perhaps it was
 pilot-error on my part in my use of portupgrade). In any case, I now believe
 there is nothing wrong with this port and I think the PR can be closed.
 
 --000325579e82d9c0ef04684b5476
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 I encountered this error in attempting to upgrade epiphany using portupgrad=
 e. I subsequently tried the epiphany upgrade using portmaster and succeeded=
 , which included getting this port compiled and installed. I&#39;m guessing=
  that the ordering of the upgrading of the ports matters and portmaster got=
  it right and portupgrade didn&#39;t (or perhaps it was pilot-error on my p=
 art in my use of portupgrade). In any case, I now believe there is nothing =
 wrong with this port and I think the PR can be closed.<br>
 <br>
 
 --000325579e82d9c0ef04684b5476--



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