Date: 09 Jun 2002 18:55:10 +0100 From: "S. Roberts" <sroberts@dsl.pipex.com> To: Kent Stewart <kstewart@owt.com> Cc: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: Portupgrade failure today after latest cvsup of ports tree Message-ID: <1023645311.318.56.camel@Demon.Strobe.org> In-Reply-To: <3D038787.5080600@owt.com> References: <1023622158.316.10.camel@Demon.Strobe.org> <001b01c20fbd$f8068e50$0800a8c0@e nder> <1023631477.316.29.camel@Demon.Strobe.org> <3D037DA2.8010502@owt.com> <1023639325.318.16.camel@Demon.Strobe.org> <3D038787.5080600@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-J4xtT2lLqK2mE+2f4hhp Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Thanks for the bg info. I'll just update x-screensaver manually, just to save time and grief over this. My first nature is to chase the port-maintainer "into the ground" over this, but for something as minor as this, I'll leave it well alone. I have seen postings from DougB over the last day, so I know he's "around" - can't imagine why he's not gotten back to me though. I'll wait to see if he does indeed post a reply to me eventually, if not, I'll think about dropping this port altogether. I am willing to participate as much as my own knowledge and capabilities allow, but I cannot afford to have ports installed for which there is less than co-operative feedback. Thanks again for the information, Kent - its proven to be quite an elightenment! Stacey On Sun, 2002-06-09 at 17:51, Kent Stewart wrote: >=20 >=20 > S. Roberts wrote: >=20 > > Hi Kent, > > I *do* run portsd -Uu after each cvsup ports-supfile (which is still > > configured with ports-all).=20 > > I got spooked by the lack of response from the list after my initial > > posting - thinking that there was some glaringly publicised update to > > ruby that I missed somehow. >=20 >=20 > I haven't noticed anything and I try to follow them closely. The cvsup=20 > mirrors are all clogged right now. I have to update my mirror manually=20 > otherwise I get a cvsup.log that is 210 bytes long. I also log all of=20 > my cvsup of ports and convert the log into html for later viewing. I=20 > haven't looked at that yet. >=20 > There is a bunch of nasty comments by portsdb on ruby-* when it is=20 > trying to create the INDEX. We may be in the middle of a massive=20 > change of some sort. >=20 >=20 > >=20 > > But I'm just happy with the fact that I got things back on stream now. > > There is another outstanding query I have posted to the list (on which = I > > need advice on how to progress) about the inability to upgrade > > x-screensaver. >=20 >=20 > I use kde-3 and can't comment. I ran my search shell script and get >=20 > coral# search screensaver > Port: xscreensaver-4.04.2 > Path: /usr/ports/x11/xscreensaver > Info: Save your screen while you entertain your cat > Maint: DougB@FreeBSD.org > Index: x11 > B-deps: Mesa-3.4.2_2 XFree86-libraries-4.2.0_1 expat-1.95.2=20 > freetype2-2.1.0_1 gettext-0.11.1_3 gle-3.0.3 glib-1.2.10_5=20 > gmake-3.79.1_2 gtk-1.2.10_4 imake-4.2.0_1 libiconv-1.7.0.1=20 > libxml-1.8.17_1 pkgconfig-0.12.0 > R-deps: Mesa-3.4.2_2 XFree86-libraries-4.2.0_1 expat-1.95.2=20 > freetype2-2.1.0_1 gettext-0.11.1_3 gle-3.0.3 glib-1.2.10_5=20 > gtk-1.2.10_4 imake-4.2.0_1 libiconv-1.7.0.1 libxml-1.8.17_1=20 > pkgconfig-0.12.0 >=20 > In case you are interested >=20 > coral# cat search > #! /bin/sh > cd /usr/ports > make search name=3D$1 >=20 > I got tired of moving to ports and then doing the make search. >=20 > There are times when I think portupgrade is designed to handle normal=20 > changes. When you get out side of normal too far, you have to manually=20 > update code. >=20 > I just noticed that DougB was the port manager. If you go back on=20 > archives cvs-all or hackers, you will find a very curt message where=20 > he deleted his commit bit. There were no comments and it left people=20 > baffled. I am hearsay at this point. I think the commit priviledges=20 > are different by area. If he hasn't responded, it is time for=20 > ports@freebsd.org to know. However, if you check >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/xscreensaver/ >=20 > You can see he made changes in the last 4 days. The changes to=20 > xcreensaver may be too massive for portupgrade to deal with and a=20 > manual update is needed. When ports are deleted, seems to be a point=20 > of difficulty with portupgrade. I don't think too long about it and do=20 > the manual changes, run portsdb -F and proceed with life. >=20 >=20 > >=20 > > I posted to the list as well as the port maintainer (as listed in the > > ports directory at freebsd.org/ports, but haven't had any responses > > (worryingly, from the port maintainer) on this issue. > >=20 > > What other options are open for me to chase this alternatively? >=20 >=20 > You should follow up on freebsd-ports@freebsd.org. The port manager=20 > reads ports@freebsd.org. If it has been more than 4 or 5 days, someone=20 > may look into it. There are parts of the world where people may have=20 > started their holiday, which we call vacation. >=20 >=20 > >=20 > > Stacey > >=20 > > On Sun, 2002-06-09 at 17:09, Kent Stewart wrote: > >=20 > >> > >>S. Roberts wrote: > >> > >> > >>>Been there, done that....., > >>> > >>>Thanks all the same - I sorted this on my own soon after my post. > >>> > >>>One thing though.., where does information concerning the removal (as > >>>you put it) of a port get displayed / sent to? I heard nothing about > >>>this, and if this is something that happens pretty regularly, then it'= d > >>>be in my interest to check that information source often. > >>> > >> > >>I think you need to portsdb -uU after every cvsup of ports-all. That=20 > >>is how I do my cvsups. That updates the INDEX.* files in /usr/ports=20 > >>when you update the structure. > >> > >>I think what happended is your INDEX still had the ruby port in it but=20 > >>it was deleted from /usr/ports/ > >> > >>Kent > >> > >> > >> > >>>Stacey > >>> > >>>On Sun, 2002-06-09 at 15:00, Carl Petersen wrote: > >>> > >>> > >>>>----- Original Message -----=20 > >>>>From: "S. Roberts" <sroberts@dsl.pipex.com> > >>>>To: "FreeBSD-Questions" <freebsd-questions@freebsd.org> > >>>>Cc: <knu@FreeBSD.org> > >>>>Sent: Sunday, June 09, 2002 7:29 AM > >>>>Subject: Portupgrade failure today after latest cvsup of ports tree > >>>> > >>>>Work around - remove ruby and reinstall. devel/ruby-fnmatch has been = removed. > >>>> > >>>> > >>>>To Unsubscribe: send mail to majordomo@FreeBSD.org > >>>>with "unsubscribe freebsd-questions" in the body of the message > >>>> > >>>> > >> > >>--=20 > >>Kent Stewart > >>Richland, WA > >> > >>http://users.owt.com/kstewart/index.html > >> > >> >=20 >=20 > --=20 > Kent Stewart > Richland, WA >=20 > http://users.owt.com/kstewart/index.html >=20 --=20 Stacey Roberts B.Sc. (HONS) Computer Science Network Systems Engineer --=-J4xtT2lLqK2mE+2f4hhp 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 Thanks for the bg info. I'll just update x-screensaver manually, just to save time and grief over this. My first nature is to chase the port-maintainer "into the ground" over this, but for something as minor as this, I'll leave it well alone. I have seen postings from DougB over the last day, so I know he's "around" - can't imagine why he's not gotten back to me though. I'll wait to see if he does indeed post a reply to me eventually, if not, I'll think about dropping this port altogether. I am willing to participate as much as my own knowledge and capabilities allow, but I cannot afford to have ports installed for which there is less than co-operative feedback. Thanks again for the information, Kent - its proven to be quite an elightenment! Stacey On Sun, 2002-06-09 at 17:51, Kent Stewart wrote: >=20 >=20 > S. Roberts wrote: >=20 > > Hi Kent, > > I *do* run portsd -Uu after each cvsup ports-supfile (which is still > > configured with ports-all).=20 > > I got spooked by the lack of response from the list after my initial > > posting - thinking that there was some glaringly publicised update to > > ruby that I missed somehow. >=20 >=20 > I haven't noticed anything and I try to follow them closely. The cvsup=20 > mirrors are all clogged right now. I have to update my mirror manually=20 > otherwise I get a cvsup.log that is 210 bytes long. I also log all of=20 > my cvsup of ports and convert the log into html for later viewing. I=20 > haven't looked at that yet. >=20 > There is a bunch of nasty comments by portsdb on ruby-* when it is=20 > trying to create the INDEX. We may be in the middle of a massive=20 > change of some sort. >=20 >=20 > >=20 > > But I'm just happy with the fact that I got things back on stream now. > > There is another outstanding query I have posted to the list (on which = I > > need advice on how to progress) about the inability to upgrade > > x-screensaver. >=20 >=20 > I use kde-3 and can't comment. I ran my search shell script and get >=20 > coral# search screensaver > Port: xscreensaver-4.04.2 > Path: /usr/ports/x11/xscreensaver > Info: Save your screen while you entertain your cat > Maint: DougB@FreeBSD.org > Index: x11 > B-deps: Mesa-3.4.2_2 XFree86-libraries-4.2.0_1 expat-1.95.2=20 > freetype2-2.1.0_1 gettext-0.11.1_3 gle-3.0.3 glib-1.2.10_5=20 > gmake-3.79.1_2 gtk-1.2.10_4 imake-4.2.0_1 libiconv-1.7.0.1=20 > libxml-1.8.17_1 pkgconfig-0.12.0 > R-deps: Mesa-3.4.2_2 XFree86-libraries-4.2.0_1 expat-1.95.2=20 > freetype2-2.1.0_1 gettext-0.11.1_3 gle-3.0.3 glib-1.2.10_5=20 > gtk-1.2.10_4 imake-4.2.0_1 libiconv-1.7.0.1 libxml-1.8.17_1=20 > pkgconfig-0.12.0 >=20 > In case you are interested >=20 > coral# cat search > #! /bin/sh > cd /usr/ports > make search name=3D$1 >=20 > I got tired of moving to ports and then doing the make search. >=20 > There are times when I think portupgrade is designed to handle normal=20 > changes. When you get out side of normal too far, you have to manually=20 > update code. >=20 > I just noticed that DougB was the port manager. If you go back on=20 > archives cvs-all or hackers, you will find a very curt message where=20 > he deleted his commit bit. There were no comments and it left people=20 > baffled. I am hearsay at this point. I think the commit priviledges=20 > are different by area. If he hasn't responded, it is time for=20 > ports@freebsd.org to know. However, if you check >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/xscreensaver/ >=20 > You can see he made changes in the last 4 days. The changes to=20 > xcreensaver may be too massive for portupgrade to deal with and a=20 > manual update is needed. When ports are deleted, seems to be a point=20 > of difficulty with portupgrade. I don't think too long about it and do=20 > the manual changes, run portsdb -F and proceed with life. >=20 >=20 > >=20 > > I posted to the list as well as the port maintainer (as listed in the > > ports directory at freebsd.org/ports, but haven't had any responses > > (worryingly, from the port maintainer) on this issue. > >=20 > > What other options are open for me to chase this alternatively? >=20 >=20 > You should follow up on freebsd-ports@freebsd.org. The port manager=20 > reads ports@freebsd.org. If it has been more than 4 or 5 days, someone=20 > may look into it. There are parts of the world where people may have=20 > started their holiday, which we call vacation. >=20 >=20 > >=20 > > Stacey > >=20 > > On Sun, 2002-06-09 at 17:09, Kent Stewart wrote: > >=20 > >> > >>S. Roberts wrote: > >> > >> > >>>Been there, done that....., > >>> > >>>Thanks all the same - I sorted this on my own soon after my post. > >>> > >>>One thing though.., where does information concerning the removal (as > >>>you put it) of a port get displayed / sent to? I heard nothing about > >>>this, and if this is something that happens pretty regularly, then it'= d > >>>be in my interest to check that information source often. > >>> > >> > >>I think you need to portsdb -uU after every cvsup of ports-all. That=20 > >>is how I do my cvsups. That updates the INDEX.* files in /usr/ports=20 > >>when you update the structure. > >> > >>I think what happended is your INDEX still had the ruby port in it but=20 > >>it was deleted from /usr/ports/ > >> > >>Kent > >> > >> > >> > >>>Stacey > >>> > >>>On Sun, 2002-06-09 at 15:00, Carl Petersen wrote: > >>> > >>> > >>>>----- Original Message -----=20 > >>>>From: "S. Roberts" <sroberts@dsl.pipex.com> > >>>>To: "FreeBSD-Questions" <freebsd-questions@freebsd.org> > >>>>Cc: <knu@FreeBSD.org> > >>>>Sent: Sunday, June 09, 2002 7:29 AM > >>>>Subject: Portupgrade failure today after latest cvsup of ports tree > >>>> > >>>>Work around - remove ruby and reinstall. devel/ruby-fnmatch has been = removed. > >>>> > >>>> > >>>>To Unsubscribe: send mail to majordomo@FreeBSD.org > >>>>with "unsubscribe freebsd-questions" in the body of the message > >>>> > >>>> > >> > >>--=20 > >>Kent Stewart > >>Richland, WA > >> > >>http://users.owt.com/kstewart/index.html > >> > >> >=20 >=20 > --=20 > Kent Stewart > Richland, WA >=20 > http://users.owt.com/kstewart/index.html >=20 - --=20 Stacey Roberts B.Sc. (HONS) Computer Science Network Systems Engineer -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQA/AwUBPQOWffdn4A8qiCO5EQJTjACgga5NlT00ldQ/1CuWAZ2MUr8nVx0AoKdA GbR1DLMKjmrkLCtzHA0iIpD0 =7PwI -----END PGP SIGNATURE----- --=-J4xtT2lLqK2mE+2f4hhp-- 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?1023645311.318.56.camel>