Date: 09 Jun 2002 18:19:30 +0100 From: "S. Roberts" <sroberts@dsl.pipex.com> To: Michael <michael.lawver@pointoflightproducts.com> Cc: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: Orphaned ruby port Message-ID: <1023643171.318.31.camel@Demon.Strobe.org> In-Reply-To: <3D038B2F.90407@pointoflightproducts.com> References: <1023574023.304.197.camel@Demon.Strobe.org> <3D0282EC.9020704@pointoflightpr oducts.com> <1023581031.304.227.camel@Demon.Strobe.org> <3D029FC0.8090405@pointoflightproducts.com> <1023626550.316.25.camel@Demon.Strobe.org> <3D038B2F.90407@pointoflightproducts.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-bSe+eULhK6ijZRwPqAGz
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
No worries!
Stacey
On Sun, 2002-06-09 at 18:06, Michael wrote:
> Excellent!
>=20
> Thanks for your dilegence and detailed steps.
>=20
> From the other postings I'm seeing it looks like the problem was in the=20
> Ruby install itself so I'll do the package delete as you mention and=20
> reinstall the port.
>=20
> Thanks a lot Stacey!!!
>=20
> Michael :o)
>=20
> S. Roberts wrote:
>=20
> >Hi Mike,
> > After no response from anyone else on this I went read ahead, poked
> >around and I believe, sorted this myself.=20
> >The procedure is as follows:
> >1] Re-run cvsup ports-supfile (might not be required, but just in case)
> >2] cd /var/db/pkg
> >3] ls -la portupgrade* (returns current installed version)
> >4] Run pkg_delete portupgrade{version_number}
> >5] cd /usr/ports/sysutils/portupgrade
> >6] Run make --|
> >7] Run make install--|---- Can be done with # make install clean
> >8] Run make clean --|
> >9] cd /usr/share/examples/cvsup; cvsup ports-supfile
> >10] cd /usr/ports; pkg_version -v
> >
> >You should now see that=20
> >a] ruby-fnmatch-1.1b_1 is no longer listed
> >b] portupgrade has a new version number
> >
> >11] Update any out-of-date ports with portupgrade
> >12] Run portsdb -Uu to update the ports index
> >
> >You're done.
> >
> >This situation appears to have come out of an update applied to either
> >portupgrade itself, or the ruby infrastructure in some fashion.
> >
> >Hope it goes well with you, good luck!
> >
> >Stacey
> >
> >On Sun, 2002-06-09 at 01:22, Michael wrote:
> > =20
> >
> >>Thank you Stacey!! :o)
> >>
> >>I've been reading other lists that are reporting the same issue so were=
=20
> >>not alone :o)
> >>
> >>Thanks for the feedback I appreciate it!!
> >>
> >>Michael :o)
> >>
> >>S. Roberts wrote:
> >>
> >> =20
> >>
> >>>Hi Mike,
> >>> if you go to http://www.freebsd.org/ports/devel.html, click on the
> >>>"Long Description" link, and you'll see (disturbingly) that this port =
is
> >>>actually listed there are being non-existent!
> >>>
> >>>I've sent a query off to the port maintainer (as listed at the above
> >>>link) asking for some information on the status of this port, as well =
as
> >>>some advice on a work-around.
> >>>
> >>>Stacey
> >>>
> >>>On Sat, 2002-06-08 at 23:19, Michael wrote:
> >>>=20
> >>>
> >>> =20
> >>>
> >>>>Interesting, I just found the same thing.
> >>>>
> >>>>I went in and did a cvsup to all my ports and found this to be orphan=
ed=20
> >>>>as well.
> >>>>
> >>>># uname -a
> >>>>FreeBSD <snip> 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Sat Jun 1 12:49:2=
4=20
> >>>>PDT 2002 <snip>:/usr/src/sys/compile/xeon i386
> >>>>
> >>>>Michael
> >>>>
> >>>>S. Roberts wrote:
> >>>>
> >>>> =20
> >>>>
> >>>> =20
> >>>>
> >>>>>Hello,
> >>>>> I just cvsup'd my ports tree and pkg_version -v returns the
> >>>>>following for a ruby module:
> >>>>>
> >>>>>ruby-fnmatch-1.1b_1 ? orphaned: devel/ruby-fnmatch
> >>>>>
> >>>>>I don't know much about ruby stuff, and would appreciate some advice=
on
> >>>>>how to proceed with this message / statement here. Uname info:
> >>>>># uname -a
> >>>>>FreeBSD <snip> 4.6-RC FreeBSD 4.6-RC #0: Sun May 26 11:20:25 BST
> >>>>>2002 <snip>:/usr/obj/usr/src/sys/<snip> i386
> >>>>>#=20
> >>>>>
> >>>>>Thanks for the time.
> >>>>>
> >>>>>Stacey
> >>>>>
> >>>>>
> >>>>> =20
> >>>>>
> >>>>> =20
> >>>>>
> >>>> =20
> >>>>
> >>>> =20
> >>>>
> >>
> >>
> >> =20
> >>
>=20
>=20
>=20
>=20
--=20
Stacey Roberts B.Sc. (HONS) Computer Science
Network Systems Engineer
--=-bSe+eULhK6ijZRwPqAGz
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
No worries!
Stacey
On Sun, 2002-06-09 at 18:06, Michael wrote:
> Excellent!
>=20
> Thanks for your dilegence and detailed steps.
>=20
> From the other postings I'm seeing it looks like the problem was in the=20
> Ruby install itself so I'll do the package delete as you mention and=20
> reinstall the port.
>=20
> Thanks a lot Stacey!!!
>=20
> Michael :o)
>=20
> S. Roberts wrote:
>=20
> >Hi Mike,
> > After no response from anyone else on this I went read ahead, poked
> >around and I believe, sorted this myself.=20
> >The procedure is as follows:
> >1] Re-run cvsup ports-supfile (might not be required, but just in case)
> >2] cd /var/db/pkg
> >3] ls -la portupgrade* (returns current installed version)
> >4] Run pkg_delete portupgrade{version_number}
> >5] cd /usr/ports/sysutils/portupgrade
> >6] Run make --|
> >7] Run make install--|---- Can be done with # make install clean
> >8] Run make clean --|
> >9] cd /usr/share/examples/cvsup; cvsup ports-supfile
> >10] cd /usr/ports; pkg_version -v
> >
> >You should now see that=20
> >a] ruby-fnmatch-1.1b_1 is no longer listed
> >b] portupgrade has a new version number
> >
> >11] Update any out-of-date ports with portupgrade
> >12] Run portsdb -Uu to update the ports index
> >
> >You're done.
> >
> >This situation appears to have come out of an update applied to either
> >portupgrade itself, or the ruby infrastructure in some fashion.
> >
> >Hope it goes well with you, good luck!
> >
> >Stacey
> >
> >On Sun, 2002-06-09 at 01:22, Michael wrote:
> > =20
> >
> >>Thank you Stacey!! :o)
> >>
> >>I've been reading other lists that are reporting the same issue so were=
=20
> >>not alone :o)
> >>
> >>Thanks for the feedback I appreciate it!!
> >>
> >>Michael :o)
> >>
> >>S. Roberts wrote:
> >>
> >> =20
> >>
> >>>Hi Mike,
> >>> if you go to http://www.freebsd.org/ports/devel.html, click on the
> >>>"Long Description" link, and you'll see (disturbingly) that this port =
is
> >>>actually listed there are being non-existent!
> >>>
> >>>I've sent a query off to the port maintainer (as listed at the above
> >>>link) asking for some information on the status of this port, as well =
as
> >>>some advice on a work-around.
> >>>
> >>>Stacey
> >>>
> >>>On Sat, 2002-06-08 at 23:19, Michael wrote:
> >>>=20
> >>>
> >>> =20
> >>>
> >>>>Interesting, I just found the same thing.
> >>>>
> >>>>I went in and did a cvsup to all my ports and found this to be orphan=
ed=20
> >>>>as well.
> >>>>
> >>>># uname -a
> >>>>FreeBSD <snip> 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Sat Jun 1 12:49:2=
4=20
> >>>>PDT 2002 <snip>:/usr/src/sys/compile/xeon i386
> >>>>
> >>>>Michael
> >>>>
> >>>>S. Roberts wrote:
> >>>>
> >>>> =20
> >>>>
> >>>> =20
> >>>>
> >>>>>Hello,
> >>>>> I just cvsup'd my ports tree and pkg_version -v returns the
> >>>>>following for a ruby module:
> >>>>>
> >>>>>ruby-fnmatch-1.1b_1 ? orphaned: devel/ruby-fnmatch
> >>>>>
> >>>>>I don't know much about ruby stuff, and would appreciate some advice=
on
> >>>>>how to proceed with this message / statement here. Uname info:
> >>>>># uname -a
> >>>>>FreeBSD <snip> 4.6-RC FreeBSD 4.6-RC #0: Sun May 26 11:20:25 BST
> >>>>>2002 <snip>:/usr/obj/usr/src/sys/<snip> i386
> >>>>>#=20
> >>>>>
> >>>>>Thanks for the time.
> >>>>>
> >>>>>Stacey
> >>>>>
> >>>>>
> >>>>> =20
> >>>>>
> >>>>> =20
> >>>>>
> >>>> =20
> >>>>
> >>>> =20
> >>>>
> >>
> >>
> >> =20
> >>
>=20
>=20
>=20
>=20
- --=20
Stacey Roberts B.Sc. (HONS) Computer Science
Network Systems Engineer
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBPQOOIfdn4A8qiCO5EQL9RQCguKdTznXEdFAsLXvt8WUBhKGzYmYAoPDm
Qo9Sc91GN93XFYQ6OL/bB7wm
=PSdR
-----END PGP SIGNATURE-----
--=-bSe+eULhK6ijZRwPqAGz--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1023643171.318.31.camel>