Re: portupgrade portupgrade leaves an error....
On Friday 30 June 2006 18:51, David J Brooks wrote: > After running 'portupgrade portupgrade' I am left with the following error > when I run portversion or portupgrade, or pretty much any program that > addresses the ports collection: > > /libexec/ld-elf.so.1: > /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so: Undefined symbol > "db_version" > > Any ideas on how to fix it? > > David pkg_delete portupgrade-whatever the number, pkg_add -r portupgrade. This gets you an older version of portupgrade. I ran into the same problem today. It's a way around the problem until it's fixed. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade portupgrade leaves an error....
On Monday 03 July 2006 04:01, gareth wrote: > On Fri 2006-06-30 (20:44), Donald J. O'Neill wrote: > > pkg_delete portupgrade-whatever the number, pkg_add -r portupgrade. This > > gets you an older version of portupgrade. > > > > I ran into the same problem today. It's a way around the problem until > > it's fixed. > > i tried that: > > # pkg_delete portupgrade-2.1.3.2,2 > # pkg_add -r portupgrade > Error: FTP Unable to get > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/po >rtupgrade.tbz: Not Found pkg_add: unable to fetch > 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/p >ortupgrade.tbz' by URL > >(sure enough the url doesn't exist) > OK, then you're going to have to get a bit more aggressive. This is what I did to take care of the problem on my 6.1-STABLE system: mv /usr/ports/INDEX-6.db --> INDEX-6.db.org mv /var/db/pkg/pkgdb.db --> pkgdb.db.org pkg_delete portupgrade-2.1.3.1,2 pkg_delete ruby18-bdb-0.5.9 pkg_delete ruby18-bdb1-0.2.2 pkg_delete db4-4.0.14_1,1 pkg_delete db41-4.1.25_3 pkg_delete db42-4.2.52_4 I left db43-4.3.29, It would be needed later and reomoving it would cause too many other things to have to be rebuilt (or I get a bite in the ass if I don't). 'cd /usr/ports/sysutils/portupgrade' 'make conf' - select bdb4, it'll use db43 as that's what's installed. 'make package-recursive' 'pkgdb -F'fix the dependencies and rebuild pkgdb.db portversion -v |grep needs rebuilds portsdb (and rechecks pkgdb.db) and I find out what ports need upgrading. 'portsnap fetch update' 'portversion -v |grep needs' It works and I now have a working portupgrade-2.1.3.2,2 I did a lot of reading about this problem and a lot of looking at dependencies using pkg_info -r and -R to come up with the way I corrected the problem. I have two other 6.1 systems (one STABLE, one RELEASE) to fix the problem on. They are a little different as they don't have the same things installed on them that are on my personal system, but they are similar in what I'm going to do to fix them. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: sysutils/daemontools
On Wednesday 19 July 2006 17:06, Alan Aldrich wrote: > Not having any luck installing this port > > [3:01pm [EMAIL PROTECTED]:/usr/ports/sysutils/daemontools] make install clean > ===> Vulnerability check disabled, database not found > => daemontools-0.76.tar.gz doesn't seem to exist in /usr/ports/ > distfiles/. > => Attempting to fetch from http://cr.yp.to/daemontools/. > fetch: http://cr.yp.to/daemontools/daemontools-0.76.tar.gz: size unknown > => Attempting to fetch from ftp://cr.yp.to/daemontools/. > fetch: ftp://cr.yp.to/daemontools/daemontools-0.76.tar.gz: Connection > refused > => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ > distfiles/. > fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ > daemontools-0.76.tar.gz: File unavailable (e.g., file not found, no > access) > => Couldn't fetch it - please try to retrieve this > => port manually into /usr/ports/distfiles/ and try again. > *** Error code 1 > > Stop in /usr/ports/sysutils/daemontools. > > > Just did a cvsup so believe I have the latest > > any idea? > > also having problems with dns/djbdns and sysutils/ucspi-tcp with > similar 'not found' messages > > > Alan Aldrich > CIS Data Systems Inc. > IT Manager > fax: 866-393-8923 > office: 866-645-7700 x617 > [EMAIL PROTECTED] > > Are you trying to install them seperately? dns/djbdns should install all of them. You can find, and download, daemontools-0.76.tar.gz and ucspi-tcp-0.88.tar.gz here: http://cr.yp.to/djb.html . Put them in /usr/ports/distfiles and try again. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't install ruby-bdb on RELEASE-6.1
On Friday 21 July 2006 09:45, Jim Trigg wrote: > On Fri, July 21, 2006 2:22 am, Sergey Matveychuk wrote: > > Jim Trigg wrote: > >> I'm setting up a new system with 6.1-RELEASE, and I forgot to install > >> portupgrade from a package during the OS install. ruby-bdb fails to > >> build, complaining that it doesn't know how to make 'all' (it doesn't > >> specify which directory it's in, but it's right after it runs > >> extconf.rb). Any clues? > >> > >> (Note: when I posted this earlier I mentioned changing LOCALBASE. > >> Further > >> testing has shown that it fails regardless of LOCALBASE setting.) > > > > Make sure you have a fresh ports tree. > > May be you should reinstall ruby. > > I did have a fresh ports tree, and I've tried that. > > Full list of what I've done: > - Installed 6.1-RELEASE from CD OK, fine. > - Installed cvsup > - Ran cvsup ports-all Please explain this a little more. What's ports-all? Is that the name of a sup-file you're using? If so, what's in it? > - Attempted to install portupgrade with BDB4; ruby-bdb failed to build What is the failure message. The failure could have occurred at the beginning of ruby-bdb. Do you have /usr/ports/databases/db(what version?) installed? > - Uninstalled all ports, changed LOCALBASE to /opt and X11BASE to > $LOCALBASE Are you saying you uninstalled the ports-tree and reinstalled it using cvsup, or are you saying you uninstalled the installed ports? Is there a reason you are messing with LOCALBASE? Is this a linux thing you're doing? > - Attempted to install portupgrade with BDB4; ruby-bdb failed to > build - Uninstalled all ports, changed LOCALBASE back to /usr/local > - Installed ruby18, attempted to install ruby-bdb; ruby-bdb failed to build > - Uninstalled all ports, changed LOCALBASE back to /opt > - Installed portupgrade with BDB1. See below. > > Thanks, > Jim > > ___ Jim - I would suggest that you use portsnap rather than cvsup for the ports tree. Cvsup will work, and it will work fine, but portsnap will work better and faster and with less problems. I suggest you do it this way: actually the way I do it is: perf500# script /home/script/portsnap/20060721 (that's today's date) Script started, output file is /home/script/portsnap/20060721 perf500# portsnap fetch extract You don't have to run 'script', but in case there's a failure, I like to have something to look at to see if I can find what went wrong. You could just run 'portsnap fetch extract'. NOTE: unless you blow the ports-tree off, you only run 'portsnap fetch extract' once. After that you use: 'portsnap fetch update'. The first time you do this, it takes a bit of time to complete. After that, on my systems anyway, it takes about 2 minutes as compared to 15 to 20 using cvsup. If you're blowing off the ports-tree and rerunning cvsup to install it, portsnap is going to be way faster. What is the output from 'df -m'? Do you have anything in /etc/make.conf? I would suggest installing /usr/ports/databases/db43 before trying to install portupgrade. It might work out a little better for you. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with kmail
On Saturday 05 August 2006 18:49, Beech Rintoul wrote: > I just started getting the following error while trying to login to gmail: > > The process for the pop3s://pop.gmail.com protocol died unexpectedly. > > I'm running FreeBSD 7.0-CURRENT with the kde ports all up to date. I've > double checked the configs and they are correct. I can log into pop3 on > gmail from my windows box with no problems, so it's not a gmail problem. I > tried rebuilding kdepim and it didn't help. Dos anyone have a suggestion? I > have no clue what to do next. > > Thanks, > > Beech I can give you a quick work around to try. It won't solve the problem, but it'll put it off for a while, if I'm understanding your problem correctly. Go back into settings/configure kmail/accounts/receiving and re-enter your gmail password in the appropriate account. It should work after that. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with kmail
On Saturday 05 August 2006 20:59, Beech Rintoul wrote: > Thanks for the suggestion, but that didn't help. There seems to be a > problem regarding secure login, as the rest of my insecure pop3 logins > work. This all started after my last -current update. > > Beech Gmail uses ssl, do you have that set correctly in your kmail config? It should be port 995 and on the extras page, you should have ssl selected and clear text login. After this, I'm not any help. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with kmail
On Saturday 05 August 2006 21:21, Beech Rintoul wrote: > Yes that's all set up. I'm wondering if the recent update of openssl broke > something. That's quite possible. You could try deinstalling it and going back to the base ssl. TAke a look at /usr/ports/UPGRADING, at 20060108 there is a message about upgrading kde 3.4.3 to 3.5.0 and openssl is mentioned. The part about openssl may be worth you time to reread. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX build failed for 4.x
On Monday 28 August 2006 09:06, Erwin Lansing wrote: > INDEX build failed with errors: > Generating INDEX - please wait.. Done. > make_index: htdig-3.2.0.b6_2: no entry for /usr/ports > > Committers on the hook: > clsung dougb jylefort krion miwi pav sat skv sumikawa > > Most recent CVS update was: > U audio/Makefile < snip - to protect whoever> > U www/campsite/distinfo > U www/campsite/pkg-plist > U www/campsite/files/patch-transfer_images.php > U x11-fm/gentoo/Makefile > U x11-fm/gentoo/distinfo > U x11-fm/gentoo/pkg-plist > U x11-wm/pawm/Makefile > U x11-wm/pawm/distinfo > U x11-wm/pawm/files/patch-src__pafont.c Hello Irwin, I'm curious. Do you have a purpose in sending all these messages to the list? Are you asking a question without actually asking it? Making a statement of some kind without explicitly saying what it is? What? Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INDEX build failed for 4.x
On Monday 28 August 2006 10:27, LI Xin wrote: > > Well, the world is imperfect, and sometimes the automated bots run by us > will not be able to explicitly point out which port is getting problem... > > All the purpose of this sort of letters (e.g. tinderbox build failure > reports, etc) is in the hope that someone can pick up the work and fix > it before users actually being hit by a bug and thus save their time. > In other words, this is something like "Look out! Ports tree have some > *known* trouble now and please do not report problems (without patch, of > course) until things gets fixed." > > Cheers, Thank you for your reply. Tinderbox failure reports I understand. I guess this type of report goes into my ignore category, unless I'm willing to help of course. Not in this case though, I only have 6-STABLE systems. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
