Problems with portsdb -Uu on FreeBSD 6.3
Hi people. Well I have time locking for a solution for this problem I have, I have googling around and have not found a solution, I have 2 serves running FreeBSD 6.1/6.2, normally I update my ports tree each day, but I already stop doing that because I still cannot fix the problems with the commmand: portsdb -Uu, each time I run that command on both servers I receive this error: Updating the ports index ... Generating INDEX.tmp - please wait.."Makefile", line 56: Could not find bsd.port.options.mk make: fatal errors encountered -- cannot continue ===> sysutils/apcupsd failed *** Error code 1 I try to follow some sites solutions but no luck, I remove the port "portupgrade" and install again but again no luck, download the Index file, etc, etc, today I build a server, fresh install, update my ports with portsnap, them run the portsdb -Uu and again the same error. This could not be the sync of the server and my files, because the last time I try to sync my servers this was the same error I got today. I don't know if this is the only way we can have our ports sync: portsnap fetch && portsnap update && portsdb -Uu ? This is my normal commands I use to sync my ports, maybe I am wrong please confirm this if I'am wrong, but the error appear right in my server, what could I do to fix this error? I have seen other people with the same error and no solution yet. "sysutils/apcupsd failed" Thanks all for your time!!! FreeBSD 6.3-Release!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
-- From: "perikillo" <[EMAIL PROTECTED]> Sent: Monday, September 08, 2008 5:41 PM To: "FreeBSD Mailing List" Subject: Problems with portsdb -Uu on FreeBSD 6.3 Hi people. Well I have time locking for a solution for this problem I have, I have googling around and have not found a solution, I have 2 serves running FreeBSD 6.1/6.2, normally I update my ports tree each day, but I already stop doing that because I still cannot fix the problems with the commmand: portsdb -Uu, each time I run that command on both servers I receive this error: Updating the ports index ... Generating INDEX.tmp - please wait.."Makefile", line 56: Could not find bsd.port.options.mk make: fatal errors encountered -- cannot continue ===> sysutils/apcupsd failed *** Error code 1 CVSUP your tree to straighten it out. I noticed that portsnap will not fix damaged/missing files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Mon, Sep 8, 2008 at 6:12 PM, Sean Cavanaugh <[EMAIL PROTECTED]> wrote: > -- > From: "perikillo" <[EMAIL PROTECTED]> > Sent: Monday, September 08, 2008 5:41 PM > To: "FreeBSD Mailing List" > Subject: Problems with portsdb -Uu on FreeBSD 6.3 > >> Hi people. >> >> Well I have time locking for a solution for this problem I have, I have >> googling around and have not found a solution, I have 2 serves running >> FreeBSD 6.1/6.2, normally I update my ports tree each day, but I already >> stop doing that because I still cannot fix the problems with the commmand: >> >> portsdb -Uu, each time I run that command on both servers I receive this >> error: >> >> Updating the ports index ... Generating INDEX.tmp - please >> wait.."Makefile", >> line 56: Could not find bsd.port.options.mk >> make: fatal errors encountered -- cannot continue >> ===> sysutils/apcupsd failed >> *** Error code 1 > > > CVSUP your tree to straighten it out. I noticed that portsnap will not fix > damaged/missing files. Portsnap will if you do "extract". It WONT if you do "update." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
http://www.freebsd.org/doc/en/books/handbook/portsnap.html I supposes that "portsnap extract" have to run just once, latter u have to just run portsnap fetch && portsnap update? Sean, u say that I better mix cvsup + portsnap? This is normal? This would not broke my tree? Right now I already run cvsup and is running portsdb -Uu, I will let u know what happend, thanks!!! On Mon, Sep 8, 2008 at 3:19 PM, Schiz0 <[EMAIL PROTECTED]> wrote: > On Mon, Sep 8, 2008 at 6:12 PM, Sean Cavanaugh <[EMAIL PROTECTED]> > wrote: > > -- > > From: "perikillo" <[EMAIL PROTECTED]> > > Sent: Monday, September 08, 2008 5:41 PM > > To: "FreeBSD Mailing List" > > Subject: Problems with portsdb -Uu on FreeBSD 6.3 > > > >> Hi people. > >> > >> Well I have time locking for a solution for this problem I have, I have > >> googling around and have not found a solution, I have 2 serves running > >> FreeBSD 6.1/6.2, normally I update my ports tree each day, but I already > >> stop doing that because I still cannot fix the problems with the > commmand: > >> > >> portsdb -Uu, each time I run that command on both servers I receive this > >> error: > >> > >> Updating the ports index ... Generating INDEX.tmp - please > >> wait.."Makefile", > >> line 56: Could not find bsd.port.options.mk > >> make: fatal errors encountered -- cannot continue > >> ===> sysutils/apcupsd failed > >> *** Error code 1 > > > > > > CVSUP your tree to straighten it out. I noticed that portsnap will not > fix > > damaged/missing files. > > Portsnap will if you do "extract". It WONT if you do "update." > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
-- From: "perikillo" <[EMAIL PROTECTED]> Sent: Monday, September 08, 2008 7:25 PM To: "FreeBSD Mailing List" Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 http://www.freebsd.org/doc/en/books/handbook/portsnap.html I supposes that "portsnap extract" have to run just once, latter u have to just run portsnap fetch && portsnap update? Sean, u say that I better mix cvsup + portsnap? This is normal? This would not broke my tree? Right now I already run cvsup and is running portsdb -Uu, I will let u know what happend, thanks!!! I've never fully trusted portsnap. I do run portsnap fetch before every portupgrade but I always follow it up with CVSUP and I usually find some more files that get changed anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
up, nsupdate #WITH_BIND_LIBS=# Install the BIND libs and include files # # To build sys/modules when building the world (our old way of doing things) #MODULES_WITH_WORLD=# do not build modules when building kernel # # The list of modules to build instead of all of them. #MODULES_OVERRIDE= linux ipfw # # The list of modules to never build, applied *after* MODULES_OVERRIDE. #WITHOUT_MODULES= bktr plip # # NO_MANCOMPRESS= #PRINTERDEVICE= ps BOOTWAIT=0 # COM1: = 0x3F8, COM2: = 0x2F8, COM3: = 0x3E8, COM4: = 0x2E8 #BOOT_COMCONSOLE_PORT= 0x3F8 BOOT_COMCONSOLE_SPEED= 115200 #LOADER_TFTP_SUPPORT= YES #ENABLE_SUID_K5SU= #SUP_UPDATE= # #SUP=/usr/bin/csup #SUPFLAGS= -g -L 2 #SUPHOST=cvsup.uk.FreeBSD.org #SUPFILE=/usr/share/examples/cvsup/standard-supfile #PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile #DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile #TOP_TABLE_SIZE= 101 DOC_LANG= en_US.ISO8859-1 #SENDMAIL_MC=/etc/mail/myconfig.mc #SENDMAIL_SUBMIT_MC=/etc/mail/mysubmit.mc #SENDMAIL_ADDITIONAL_MC=/etc/mail/foo.mc /etc/mail/bar.mc #SENDMAIL_CF_DIR=/usr/local/share/sendmail/cf #SENDMAIL_M4_FLAGS= #with SASLv1: # SENDMAIL_CFLAGS=-I/usr/local/include/sasl1 -DSASL # SENDMAIL_LDFLAGS=-L/usr/local/lib # SENDMAIL_LDADD=-lsasl # #with SASLv2: # SENDMAIL_CFLAGS=-I/usr/local/include -DSASL=2 # SENDMAIL_LDFLAGS=-L/usr/local/lib # SENDMAIL_LDADD=-lsasl2 #SENDMAIL_CFLAGS= #SENDMAIL_LDFLAGS= #SENDMAIL_LDADD= #SENDMAIL_DPADD= #SENDMAIL_SET_USER_ID= #SENDMAIL_MAP_PERMS= NO_WPA_SUPPLICANT_EAPOL=true # added by use.perl 2008-09-06 19:36:04 PERL_VER=5.8.8 PERL_VERSION=5.8.8 This could be a bug or what? What else I could do? Thanks for your support!!! On Mon, Sep 8, 2008 at 4:43 PM, Sean Cavanaugh <[EMAIL PROTECTED]>wrote: > -- > From: "perikillo" <[EMAIL PROTECTED]> > Sent: Monday, September 08, 2008 7:25 PM > To: "FreeBSD Mailing List" > Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 > > http://www.freebsd.org/doc/en/books/handbook/portsnap.html >> >> I supposes that "portsnap extract" have to run just once, latter u have >> to >> just run portsnap fetch && portsnap update? >> >> Sean, u say that I better mix cvsup + portsnap? >> >> This is normal? This would not broke my tree? >> >> Right now I already run cvsup and is running portsdb -Uu, I will let u >> know what happend, thanks!!! >> >> > I've never fully trusted portsnap. I do run portsnap fetch before every > portupgrade but I always follow it up with CVSUP and I usually find some > more files that get changed anyway. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
perikillo wrote: > http://www.freebsd.org/doc/en/books/handbook/portsnap.html > > I supposes that "portsnap extract" have to run just once, latter u have > to > just run portsnap fetch && portsnap update? > > Sean, u say that I better mix cvsup + portsnap? > > This is normal? This would not broke my tree? > >Right now I already run cvsup and is running portsdb -Uu, I will let u > know what happend, thanks!!! [snip] Unless you have a specific overriding reason to do -Uu you might want to try -uF instead. It's what I use and it's always worked. In fact, this is what I do to see if I need an upgrade: csup -L 2 ports && portsdb -uF && pkgdb -u && portversion But since I have never used portsnap don't really know anything about it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
I have been trying a lot of things, I want to start again, I think I just need to delete /usr/ports? Let me read again the manual and see those Flags. I remember that the first time u run portsdb the manuals recommend to sue Uu, but let read the manual page, I will back soon!!! Thanks all for your support!!! On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell <[EMAIL PROTECTED]>wrote: > perikillo wrote: > > > http://www.freebsd.org/doc/en/books/handbook/portsnap.html > > > > I supposes that "portsnap extract" have to run just once, latter u have > > to > > just run portsnap fetch && portsnap update? > > > > Sean, u say that I better mix cvsup + portsnap? > > > > This is normal? This would not broke my tree? > > > >Right now I already run cvsup and is running portsdb -Uu, I will let u > > know what happend, thanks!!! > [snip] > > Unless you have a specific overriding reason to do -Uu you might want to > try -uF instead. It's what I use and it's always worked. In fact, this is > what I do to see if I need an upgrade: > > csup -L 2 ports && portsdb -uF && pkgdb -u && portversion > > But since I have never used portsnap don't really know anything about it. > > -Mike > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Mon, 8 Sep 2008 19:43:14 -0400 "Sean Cavanaugh" <[EMAIL PROTECTED]> wrote: > I've never fully trusted portsnap. I do run portsnap fetch before > every portupgrade but I always follow it up with CVSUP and I usually > find some more files that get changed anyway. "portsnap fetch" doesn't affect your ports tree at all, you need to follow it with "portsnap update". There's no sense in in routinely mixing the two tools on the same tree. If you do find that portsnap isn't updating the tree correctly then you've either found a bug or have some corrupt data somewhere. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Mon, 8 Sep 2008 17:57:16 -0700 perikillo <[EMAIL PROTECTED]> wrote: > On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell > <[EMAIL PROTECTED]>wrote: > Please don't top-post. > > > > Unless you have a specific overriding reason to do -Uu you might > > want to try -uF instead. It's what I use and it's always worked. In > > fact, this is what I do to see if I need an upgrade: > > > > csup -L 2 ports && portsdb -uF && pkgdb -u && portversion > > > > But since I have never used portsnap don't really know anything > > about it. > > > > -Mike >I have been trying a lot of things, I want to start again, I think > I just need to delete /usr/ports? > >Let me read again the manual and see those Flags. > >I remember that the first time u run portsdb the manuals recommend > to sue Uu, but let read the manual page, I will back soon!!! portsdb -F and portsdb -U, both update the index file. The first downloads it, the second creates it from scratch (which is slow). Portsnap handles this automatically, so neither will be needed. The work done by portsdb -u will be done automatically when portupgrade is next run, but it may save a little time later. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Tue, Sep 9, 2008 at 6:13 AM, RW <[EMAIL PROTECTED]> wrote: > On Mon, 8 Sep 2008 17:57:16 -0700 > perikillo <[EMAIL PROTECTED]> wrote: > > On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell > > <[EMAIL PROTECTED]>wrote: > > > Please don't top-post. > > > > > > Unless you have a specific overriding reason to do -Uu you might > > > want to try -uF instead. It's what I use and it's always worked. In > > > fact, this is what I do to see if I need an upgrade: > > > > > > csup -L 2 ports && portsdb -uF && pkgdb -u && portversion > > > > > > But since I have never used portsnap don't really know anything > > > about it. > > > > > > -Mike > >I have been trying a lot of things, I want to start again, I think > > I just need to delete /usr/ports? > > > >Let me read again the manual and see those Flags. > > > >I remember that the first time u run portsdb the manuals recommend > > to sue Uu, but let read the manual page, I will back soon!!! > > > portsdb -F and portsdb -U, both update the index file. The first > downloads it, the second creates it from scratch (which is slow). > Portsnap handles this automatically, so neither will be needed. > > The work done by portsdb -u will be done automatically when portupgrade > is next run, but it may save a little time later. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > After finally realize that running portsdb -Uu each time I sync my ports is not a good way, I will follow the Michael Powell tip. Thanks all for your help, I still don't know why always appear the port apcupsd went this thing crush. Thanks all for your great help!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
