Re: Ports Index Update Error - mail/lmtpd Failure
Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. Wanted tp provide an update. CVSup'd my system and upgraded the INDEX (portsdb -uU). Everything went well. Did receive warnings of dup- licate entries of two ports in the INDEX, but apparently nothing major. Thanks again for your support. Bob Perry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index Update Error - mail/lmtpd Failure
On Sun, May 09, 2004 at 07:16:02AM -0400, Bob Perry wrote: Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. Wanted tp provide an update. CVSup'd my system and upgraded the INDEX (portsdb -uU). Everything went well. Did receive warnings of dup- licate entries of two ports in the INDEX, but apparently nothing major. Yeah, that's expected when you have certain ports installed (e.g. gtk); some ports exist in multiple variants (e.g. with and without gtk support by default), but they detect the installed port and end up with the same name. It's harmless, so you can safely ignore it. Thanks again for your support. Thanks for following up. Kris pgp0.pgp Description: PGP signature
Re: Ports Index Update Error - mail/lmtpd Failure
On (05/05/04 10:18), Kent Stewart wrote: From: Kent Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Ports Index Update Error - mail/lmtpd Failure Date: Wed, 5 May 2004 10:18:15 -0700 User-Agent: KMail/1.6.2 Cc: Joshua Lokken [EMAIL PROTECTED], Bob Perry [EMAIL PROTECTED] On Wednesday 05 May 2004 09:42 am, Joshua Lokken wrote: * Bob Perry [EMAIL PROTECTED] [2004-05-04 22:04]: Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. The upgrade process is fairly basic beginning with a backup of /var/db/pkg, followed with pkgdb -Fv, cvsup -g -L 2 -z cvsupfile, and then portsdb -uU. The error ocurred during the index update and a message followed describing the error stating Makefile, line 47: You cannot use DB3 and DB4 in the same time. I've been using the ports collection happily for a couple of years now, and portsdb -Uu has correctly made me an index once. I believe it's redundant, though, to immediately follow a cvsup with a portsdb -Uu, as the cvsup takes care of the index for you. I wouldn't worry too much; I've seen other folks recommend recvsupping and trying again; It should be ok to ignore it; at least I always have. This is really not true. INDEX is updated infrequently and depending on the version cvsup downloads will leave you with a version that can be as much as 2 months out of date. If you don't use ports such as portupgrade, it doesn't matter because make will use the proper parameters from the port location. If you want to use portupgrade, you have to rebuild INDEX[-5] and INDEX.db after every cvsup. If you check the update dates on INDEX, you will see that it was updated on 1 May, 28 Apr, 3 Apr, and then on 13 Feb. You could have missed an important security fix because none of the ports such as portversion or pkg_version would have recognized that the port had been updated. If it has only made a proper INDEX twice for you, I really suspect that you are refusing ports that are important to the make index process. I build the INDEXs twice a day and the last time make index failed was on 12-13 Apr. FWIW, portsdb -U now uses make index to build INDEX. First, I need to thank all who took the time to respond for your contrib- utions. I'm as much a newbie to FreeBSD as I am to sysadmin so I'm sure you'll understand why I prefer to work within the box at this time. The portsdb man page recommends running portsdb -uU after every CVSup and I feel more comfortable following those guidelines. This is the first time I've ever had a problem with INDEX so I'll treat it as an opportunity. My INDEX file was last updated Apr 30 so if I understand your recommendations, I can CVSup again, followed by portsdb -uU and hope for a clean build, or use make INDEX and work with the advice provided if it fails again. If that's unsucessful, run pkg_deinstall db3 since it's not required by any other package and try again. I've also checked my /etc/make.conf and the only settings that are uncommented include CFLAGS= -O -pipe, BDECFLAGS= (whole list of stuff), NOPROFILE= true, WITH_FAM= yes, and WITH_LAME= yes. Not sure what they do (another opportunity). Will let you know how things work out. BTW, I was also very glad to see my message posted finally. Just set up mutt and unfortunately had an ill-configured sendmail file that prevented me from sucessfully sending mail out for over a week. All better now, I hope. Thanks again. Bob Perry I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index Update Error - mail/lmtpd Failure
On Wed, May 05, 2004 at 10:40:39PM -0400, E. Eusey wrote: 2. Realizing that DB3 was a 'leaf package' (nothing depended on it), I simply You check dependancies by running 'pkg_info -a | grep -A 15 db3' at the command line. Look for a Required By: line. That's rather more neatly expressed as: % pkg_info -R db3-\* Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Ports Index Update Error - mail/lmtpd Failure
* Bob Perry [EMAIL PROTECTED] [2004-05-04 22:04]: Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. The upgrade process is fairly basic beginning with a backup of /var/db/pkg, followed with pkgdb -Fv, cvsup -g -L 2 -z cvsupfile, and then portsdb -uU. The error ocurred during the index update and a message followed describing the error stating Makefile, line 47: You cannot use DB3 and DB4 in the same time. I've been using the ports collection happily for a couple of years now, and portsdb -Uu has correctly made me an index once. I believe it's redundant, though, to immediately follow a cvsup with a portsdb -Uu, as the cvsup takes care of the index for you. I wouldn't worry too much; I've seen other folks recommend recvsupping and trying again; It should be ok to ignore it; at least I always have. -- Joshua Mmmm, unguarded breakfasts; the sweetest taboo. -- Homer Simpson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index Update Error - mail/lmtpd Failure
On Wednesday 05 May 2004 09:42 am, Joshua Lokken wrote: * Bob Perry [EMAIL PROTECTED] [2004-05-04 22:04]: Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. The upgrade process is fairly basic beginning with a backup of /var/db/pkg, followed with pkgdb -Fv, cvsup -g -L 2 -z cvsupfile, and then portsdb -uU. The error ocurred during the index update and a message followed describing the error stating Makefile, line 47: You cannot use DB3 and DB4 in the same time. I've been using the ports collection happily for a couple of years now, and portsdb -Uu has correctly made me an index once. I believe it's redundant, though, to immediately follow a cvsup with a portsdb -Uu, as the cvsup takes care of the index for you. I wouldn't worry too much; I've seen other folks recommend recvsupping and trying again; It should be ok to ignore it; at least I always have. This is really not true. INDEX is updated infrequently and depending on the version cvsup downloads will leave you with a version that can be as much as 2 months out of date. If you don't use ports such as portupgrade, it doesn't matter because make will use the proper parameters from the port location. If you want to use portupgrade, you have to rebuild INDEX[-5] and INDEX.db after every cvsup. If you check the update dates on INDEX, you will see that it was updated on 1 May, 28 Apr, 3 Apr, and then on 13 Feb. You could have missed an important security fix because none of the ports such as portversion or pkg_version would have recognized that the port had been updated. If it has only made a proper INDEX twice for you, I really suspect that you are refusing ports that are important to the make index process. I build the INDEXs twice a day and the last time make index failed was on 12-13 Apr. FWIW, portsdb -U now uses make index to build INDEX. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index Update Error - mail/lmtpd Failure
* Kent Stewart [EMAIL PROTECTED] [2004-05-05 10:28]: On Wednesday 05 May 2004 09:42 am, Joshua Lokken wrote: This is really not true. INDEX is updated infrequently and depending on the version cvsup downloads will leave you with a version that can be as much as 2 months out of date. Maybe so; still, I've hardly ever (3 times) used portsdb -Uu, and I've had very few problems installing ports, or using portupgrade to upgrade ports, and my ports/pkgdb has always been nice and clean. I don't refuse any ports. If you don't use ports such as portupgrade, it doesn't matter because make will use the proper parameters from the port location. If you want to use portupgrade, you have to rebuild INDEX[-5] and INDEX.db after every cvsup. If you check the update dates on INDEX, you will see that it was updated on 1 May, 28 Apr, 3 Apr, and then on 13 Feb. You could have missed an important security fix because none of the ports such as portversion or pkg_version would have recognized that the port had been updated. If it has only made a proper INDEX twice for you, I really suspect that you are refusing ports that are important to the make index process. I build the INDEXs twice a day and the last time make index failed was on 12-13 Apr. FWIW, portsdb -U now uses make index to build INDEX. From my own experience with ports, all of that work seems quite unnecessary. -- Joshua Mmm Jar-Jar; everyone hates you, but me. -- Comic Book Guy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index Update Error - mail/lmtpd Failure
On Wed, May 05, 2004 at 09:42:14AM -0700, Joshua Lokken wrote: * Bob Perry [EMAIL PROTECTED] [2004-05-04 22:04]: Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. The upgrade process is fairly basic beginning with a backup of /var/db/pkg, followed with pkgdb -Fv, cvsup -g -L 2 -z cvsupfile, and then portsdb -uU. The error ocurred during the index update and a message followed describing the error stating Makefile, line 47: You cannot use DB3 and DB4 in the same time. I've been using the ports collection happily for a couple of years now, and portsdb -Uu has correctly made me an index once. I believe it's redundant, though, to immediately follow a cvsup with a portsdb -Uu, as the cvsup takes care of the index for you. I wouldn't worry too much; I've seen other folks recommend recvsupping and trying again; It should be ok to ignore it; at least I always have. No, you have to build index yourself if you want it to be up-to-date. Kris pgp0.pgp Description: PGP signature
Re: Ports Index Update Error - mail/lmtpd Failure
I ran into the same issue. I found two solutions that worked. Neither is
very pretty.
1. Realizing that I would never install lmtpd, I simply commented out the
lines in the makefile pertaining to DB3. The Makefile ended up looking like
this:
# .if defined(WITH_DB3)
# LIB_DEPENDS+= db3.3:${PORTSDIR}/databases/db3
# CONFIGURE_ARGS+=--with-db3=${LOCALBASE}/include/db3 --without-db4
# .else
# CONFIGURE_ARGS+=--without-db3
# .endif
.if defined(WITH_DB4)
LIB_DEPENDS+= db4:${PORTSDIR}/databases/db4
CONFIGURE_ARGS+=--with-db4=${LOCALBASE}/include/db4 --without-db3
.else
CONFIGURE_ARGS+=--without-db4
.endif
Why this sucked: I had to hand-edit the Makefile everytime I cvsuped the ports
directory.
2. Realizing that DB3 was a 'leaf package' (nothing depended on it), I simply
ran 'pkg_deinstall db3' at the command line. You check dependancies by
running 'pkg_info -a | grep -A 15 db3' at the command line. Look for a
Required By: line. As a safeguard, pkg_deinstall won't let you remove db3
if it's required by other packages.
On Tuesday 04 May 2004 12:24 am, Bob Perry wrote:
Was unsucessful at upgrading my ports system Saturday due to a
failure during the port index update. More specifically, I
received an error message stating that mail/lmtpd file failed.
The upgrade process is fairly basic beginning with a backup of
/var/db/pkg, followed with pkgdb -Fv, cvsup -g -L 2 -z cvsupfile,
and then portsdb -uU. The error ocurred during the index update
and a message followed describing the error stating Makefile,
line 47: You cannot use DB3 and DB4 in the same time.
I located line 47 in the Makefile but didn't recognize any
error. I also ran pkg_info to track down the lmtpd package
but didn't find it.
Not sure where to go from here. Any advice would be appreciated.
Thanks,
Bob Perry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports Index Update Error - mail/lmtpd Failure
Was unsucessful at upgrading my ports system Saturday due to a failure during the port index update. More specifically, I received an error message stating that mail/lmtpd file failed. The upgrade process is fairly basic beginning with a backup of /var/db/pkg, followed with pkgdb -Fv, cvsup -g -L 2 -z cvsupfile, and then portsdb -uU. The error ocurred during the index update and a message followed describing the error stating Makefile, line 47: You cannot use DB3 and DB4 in the same time. I located line 47 in the Makefile but didn't recognize any error. I also ran pkg_info to track down the lmtpd package but didn't find it. Not sure where to go from here. Any advice would be appreciated. Thanks, Bob Perry -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
