Re: fvwm 2.5.17 Issue
In message <[EMAIL PROTECTED]>, Parv writes: > in message <[EMAIL PROTECTED]>, wrote Cy > Schubert thusly... > > > > Fvwm2 2.5.17 was released, however it contains a nasty little bug > > which causes it to ignore colour specification for the text in a > > title bar. Until this issue is addressed, I will hold off on > > updating the port. > > Thanks Cy for both being current with the fvwm release & holding > back till the bug is fixed. I noticed other bugs in it too, such as various config statements no longer being recognised yet the strings exist in the source and the binary. I haven't looked at it closely yet but I suspect a serious yet small bug in pointer arithmetic, it's doing strange things. The more I look at it, it looks much less likely that that this release will ever be committed to the ports tree. I'm hoping that 2.5.18 will fix these bugs. Anyhow, for those who are gluttons for punishment, you can get 2.5.17 from http://komquats.com/ports/fvwm2-devel-2.5.17.tar.bz2. The files will not be available this weekend as my network will be down much of the weekend and possibly even parts of next week. -- Cheers, Cy Schubert <[EMAIL PROTECTED]> FreeBSD UNIX: <[EMAIL PROTECTED]> Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unfetchable distfiles reminder
Dear porters, This is just a reminder to please periodically check the list of unfetchable distfiles at http://people.freebsd.org/~fenner/portsurvey/ . In particular, the list of ports with no MAINTAINER with distfile problems, which currently has 150 bad ports, is http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. In addition, the list of all ports with any unfetchable distfile is http://people.freebsd.org/~fenner/portsurvey/bad.html if you don't mind coordinating your fixes with the port MAINTAINER. Thanks for your help! Bill "distfiles" Fenner ___ 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: gettext-0.14.5_2 - BROKEN PORT!
"alexus" <[EMAIL PROTECTED]> writes: > ===> Building for gettext-0.14.5_2 > Making all in autoconf-lib-link > Making all in m4 > Making all in tests > Making all in gettext-runtime > make all-recursive > Making all in doc > Making all in intl > /bin/sh /usr/local/bin/libtool --mode=compile cc -c > -DLOCALEDIR=\"/usr/local/share/locale\" > -DLOCALE_ALIAS_PATH=\"/usr/local/share/locale\" > -DLIBDIR=\"/usr/local/libdata\" -DIN_LIBINTL -DENABLE_RELOCATABLE=1 > -DIN_LIBRARY -DINSTALLDIR=\"/usr/local/lib\" -DNO_XMALLOC > -Dset_relocation_prefix=libintl_set_relocation_prefix > -Drelocate=libintl_relocate -DDEPENDS_ON_LIBICONV=1 -DHAVE_CONFIG_H -I. -I. > -I.. -I/usr/local/include -O2 -fno-strict-aliasing -pipe ./bindtextdom.c > libtool: compile: unable to infer tagged configuration > libtool: compile: specify a tag with `--tag' > *** Error code 1 > > Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime/intl. > *** Error code 1 > > Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime. > *** Error code 1 > > Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime. > *** Error code 1 > > Stop in /usr/ports/devel/gettext/work/gettext-0.14.5. > *** Error code 1 > > Stop in /usr/ports/devel/gettext. > *** Error code 1 > > Stop in /usr/ports/devel/popt. > *** Error code 1 > > Stop in /usr/ports/archivers/rpm. > *** Error code 1 > > Stop in /usr/ports/emulators/linux_base-fc4. > dev# uname -a > FreeBSD dev.hotcamsluts.com 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #0: Mon > Jul 3 01:22:25 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP > i386 > dev# It works for me. Are you sure you have followed the updating instructions in /usr/ports/UPDATING? [In this case, particularly the libtool update note from 20060223, but you should check the file whenever you update your ports tree.] ___ 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: gettext-0.14.5_2 - BROKEN PORT!
Lowell Gilbert wrote: "alexus" <[EMAIL PROTECTED]> writes: ===> Building for gettext-0.14.5_2 Making all in autoconf-lib-link Making all in m4 Making all in tests Making all in gettext-runtime make all-recursive Making all in doc Making all in intl /bin/sh /usr/local/bin/libtool --mode=compile cc -c -DLOCALEDIR=\"/usr/local/share/locale\" -DLOCALE_ALIAS_PATH=\"/usr/local/share/locale\" -DLIBDIR=\"/usr/local/libdata\" -DIN_LIBINTL -DENABLE_RELOCATABLE=1 -DIN_LIBRARY -DINSTALLDIR=\"/usr/local/lib\" -DNO_XMALLOC -Dset_relocation_prefix=libintl_set_relocation_prefix -Drelocate=libintl_relocate -DDEPENDS_ON_LIBICONV=1 -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -O2 -fno-strict-aliasing -pipe ./bindtextdom.c libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime/intl. *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime. *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime. *** Error code 1 Stop in /usr/ports/devel/gettext/work/gettext-0.14.5. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/popt. *** Error code 1 Stop in /usr/ports/archivers/rpm. *** Error code 1 Stop in /usr/ports/emulators/linux_base-fc4. dev# uname -a FreeBSD dev.hotcamsluts.com 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #0: Mon Jul 3 01:22:25 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 dev# It works for me. Are you sure you have followed the updating instructions in /usr/ports/UPDATING? [In this case, particularly the libtool update note from 20060223, but you should check the file whenever you update your ports tree.] it's a fresh bare minimum install, all i need is a linux support, so i went to /usr/ports/emulators/linux_base-fc4 and tried building it, and gettext wouldn't build.. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is somebody working on a xorg 7.1 port to FreeBSD ?
On Fri, 2006-07-21 at 08:51 +0200, Andreas Klemm wrote: > Hi, > > interested to know, if there was only a talk or work going > on to bring xorg 7.1 into freebsd ports. Yes, see: http://agrajag.ijs.si/trac/wiki/X11R7.0 -- Joel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: google earth port broken
Florent Thoumie wrote: > On Tue, 2006-07-11 at 09:16 +0200, Alex Dupre wrote: >> h wrote: >>> i just installed google earth from a fresh ports tree, and when it starts, >>> first it complains about open gl emulation (while my xorg is on nvidia >>> drivers) (you can get rid of the warning) and then it hangs ... it draws >>> some >>> windows, but never earth. >>> >>> it always hangs on the "loading myplaces, ..." window. >>> Version 4.0.1693 also crashes on my box (Dell Latitude D810, ATI X600 video card -> OpenGL emulation) after drawing the main window. Removing ~/.googleearth does not help. It returns error code 76 to the shell. The first ported version worked slow but well... Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 ___ 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 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 - Installed cvsup - Ran cvsup ports-all - Attempted to install portupgrade with BDB4; ruby-bdb failed to build - Uninstalled all ports, changed LOCALBASE to /opt and X11BASE to $LOCALBASE - 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. Thanks, Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Switch from exim to exim-ldap
Hi all. I currently have exim installed via ports, but I've now found that I need ldap for lookups. Do I need to switch from exim to exim-ldap2, and if so, what's the best way do do it? Or do I just backup my config, deinstall exim and install exim-ldap2 instead? Best regards, Andreas ___ 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: Can't install ruby-bdb on RELEASE-6.1
On Fri, July 21, 2006 12:10 pm, Donald J. O'Neill wrote: > 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.) >> > >> 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? I don't have the complete error message anymore, but it was basically "don't know how to make 'all'" after running extconf.rb. IIRC I had db41 installed; on at least one attempt I tried installing db44 instead (and setting WITH_BDB_VER=44). >> - 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? I'm saying I uninstalled all installed ports, in order to change LOCALBASE. > Is there a reason you are messing with LOCALBASE? Is this a linux thing > you're doing? Sort of, but not really. I'm changing LOCALBASE because I prefer having my filesystems at root level, and want my ports on a separate filesystem from /usr. /opt happens to be used by both Linux and Solaris. Note that while this is a new system (and my first 6.x system), I've been managing a 4.x system for at least six years now; I'm not new to FreeBSD or ports. > What is the output from 'df -m'? I'll send this later, when I'm at home where the system is. Offhand, /usr and /opt each are 20G partitions with plenty of free space. > Do you have anything in /etc/make.conf? Only LOCALBASE, X11BASE, and WITH_BDB_VER when those are defined. > I would suggest installing /usr/ports/databases/db43 before trying to > install portupgrade. It might work out a little better for you. OK, I'll try against that version as well. Thanks, Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade boost-python fails
# portupgrade -R boost-python ** Port marked as IGNORE: lang/python: at line 1477 (evaluated to true) ** Proceeding anyway since NO_IGNORE is defined ** Invalid package name: lang/python: 1 open conditional:: Must not contain whitespace. ---> Skipping 'devel/boost-python' (boost-python-1.33.1) because a requisite package 'python-2.4.3' (lang/python) failed (specify -k to force) ** Listing the failed packages (*:skipped / !:failed) ! lang/python (python-2.4.3)(invalid package name) * devel/boost-python (boost-python-1.33.1) ---> Packages processed: 0 done, 0 ignored, 1 skipped and 1 failed When I tried without the -R I got something similar: # portupgrade boost-python ** Port marked as IGNORE: devel/boost-python: at line 1477 (evaluated to true) ** Proceeding anyway since NO_IGNORE is defined ** Invalid package name: devel/boost-python: 1 open conditional:: Must not contain whitespace. ** Listing the failed packages (*:skipped / !:failed) ! devel/boost-python (boost-python-1.33.1) (invalid package name) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed David -- Sure God created the world in only six days, but He didn't have an established user-base. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade boost-python fails
On Friday 21 July 2006 19:00, David J Brooks wrote: > # portupgrade -R boost-python > ** Port marked as IGNORE: lang/python: > at line 1477 (evaluated to true) > ** Proceeding anyway since NO_IGNORE is defined > ** Invalid package name: lang/python: 1 open conditional:: Must not contain > whitespace. > ---> Skipping 'devel/boost-python' (boost-python-1.33.1) because a > requisite package 'python-2.4.3' (lang/python) failed (specify -k to force) > ** Listing the failed packages (*:skipped / !:failed) > ! lang/python (python-2.4.3)(invalid package name) > * devel/boost-python (boost-python-1.33.1) > ---> Packages processed: 0 done, 0 ignored, 1 skipped and 1 failed > > When I tried without the -R I got something similar: > > # portupgrade boost-python > ** Port marked as IGNORE: devel/boost-python: > at line 1477 (evaluated to true) > ** Proceeding anyway since NO_IGNORE is defined > ** Invalid package name: devel/boost-python: 1 open conditional:: Must not > contain whitespace. > ** Listing the failed packages (*:skipped / !:failed) > ! devel/boost-python (boost-python-1.33.1) (invalid package > name) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > > David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is somebody working on a xorg 7.1 port to FreeBSD ?
On Fri, 2006-07-21 at 15:53 +0200, Joel Dahl wrote: > On Fri, 2006-07-21 at 08:51 +0200, Andreas Klemm wrote: > > Hi, > > > > interested to know, if there was only a talk or work going > > on to bring xorg 7.1 into freebsd ports. > > Yes, see: http://agrajag.ijs.si/trac/wiki/X11R7.0 Erm, don't pay attention to that page, as it hasn't been updated in *ages*. Almost everything is done, it needs some polishing though. You can have a look at the repo (xorg-modular-exp) and the timeline for recent changes. There are still some open issues like the prefix merge which has been discussed already more than enough. I think we also need to take care of the upgrade process. Meta-ports should make it easy, but you don't know until you try, and I haven't tried myself yet. I'll let Eric or Dejan correct me if I said anything silly. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
portsdb -Uu broken on AMD64 system
Hi folks, how are you all doing? My AMD64 system running FreeBSD 6.1 gave me a very strange error when trying to update my ports. I used the cvsup -g -L -2 command and everything went smooth, but after I did the portsdb -Uu command this is what I get: portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..1 open conditional: at line 1477 (evaluated to true) make: fatal errors encountered -- cannot continue ===> arabic/ae_fonts_mono failed *** Error code 1 1 open conditional: at line 22 (evaluated to true) make: fatal errors encountered -- cannot continue ===> accessibility/at-spi failed *** Error code 1 2 errors Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the "ports-all" collection, and have no "refuse" files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with "make fetchindex". *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error I already tried the make fetchindex but that gives the same error. My make.conf looks like: # added by use.perl 2006-02-28 15:03:26 PERL_VER=5.8.8 PERL_VERSION=5.8.8 The last time I had troubles is when I tried to compile the port scilab and it complained about my tk installation. I left it like that. Hope somebody can help. Here's my uname -a : FreeBSD zouk.tiscali.nl 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #6: Mon Jun 26 21:04:39 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL amd64 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb -Uu broken on AMD64 system
This has already been fixed. Please re-cvsup and try again. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is somebody working on a xorg 7.1 port to FreeBSD ?
On Fri, Jul 21, 2006 at 09:57:24PM +0100, Florent Thoumie wrote: > On Fri, 2006-07-21 at 15:53 +0200, Joel Dahl wrote: > > On Fri, 2006-07-21 at 08:51 +0200, Andreas Klemm wrote: > > > Hi, > > > > > > interested to know, if there was only a talk or work going > > > on to bring xorg 7.1 into freebsd ports. > > > > Yes, see: http://agrajag.ijs.si/trac/wiki/X11R7.0 > > Erm, don't pay attention to that page, as it hasn't been updated in > *ages*. Almost everything is done, it needs some polishing though. You > can have a look at the repo (xorg-modular-exp) and the timeline for > recent changes. Thanks for the informations ! ;-) Maybe I rebuild my machine/ports this or next weekend. Lets see how hard the heat hurts ;-) > There are still some open issues like the prefix merge which has been > discussed already more than enough. I think we also need to take care of > the upgrade process. Meta-ports should make it easy, but you don't know > until you try, and I haven't tried myself yet. Well, without metaport it could become an interesting thing to install X. Maybe there is a readme telling whats needed as a base. If somebody should have a meta port for testing I would like to give it a try then. I didn't find instructions yet, how to best use your "beta ports" in the wiki system. Maybe I overlooked something. Can I remotely checkout somehow ? Would need a tip. I only know "remote cvs" operation. Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb -Uu broken on AMD64 system
Awesomeeverything works fine again! You are getting faster and faster at these forums as time progresses:-) Just today I presented a plan at the company where I'm employed to use a open source BI tool and emphasized that the support from the community is excellent!! FreeBSD is NO EXCEPTION!!! Thanks --- Mark Linimon <[EMAIL PROTECTED]> wrote: > This has already been fixed. Please re-cvsup and > try again. > > mcl > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is somebody working on a xorg 7.1 port to FreeBSD ?
IMHO you should wait until we are ready to do a test-run on pointyhat. Otherwise you are going to be finding problems one-at-a-time that we can otherwise find out in bulk. To reiterate: there is very active work to get us to xorg7. It's not as trivial as some people have thought it is. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade boost-python fails
I just ran cvsup again and retried the portupgrade -R. Everything builds cleanly now. :) David -- Sure God created the world in only six days, but He didn't have an established user-base. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
