Re: Unable to build /x11/kdelibs3 with updated jpeg-7 port

2009-07-23 Thread Milan Obuch
On Thursday 23 July 2009 23:58:03 Mel Flynn wrote: > On Tuesday 21 July 2009 02:59:29 Milan Obuch wrote: > > On Tuesday 21 July 2009 12:40:34 Jerry wrote: > > > It appears that the /x11/kdelibs3 ports insists on using the older > > > "libjpeg.so.9" library. Since updating to jpeg-7, this library is

Re: Typo in screen's manpage

2009-07-23 Thread Anonymous
Reinout Stevens writes: > Hi, > > Today I spotted a typo in screen's manpage: it's useful instead of > usefull. I've made a small diff in case that's necessary. I also filed > a "bug" in the screen dev's bugtracker. > I'll disappoint you. It was fixed long ago. http://git.savannah.gnu.org/cgit/

Re: needing install OpenOffice.org without messing up perl

2009-07-23 Thread Scott Bennett
On Wed, 22 Jul 2009 22:44:08 +0100 Matthew Seaman wrote: >Lowell Gilbert wrote: >> Scott Bennett writes: > >>> Why wouldn't OOo, once installed, simply use whatever were >>> installed as /usr/local/bin/perl? >>=20 >> Because perl doesn't tend to be backwards-compatible. > >Untrue. > >pe

Re: needing install OpenOffice.org without messing up perl

2009-07-23 Thread Scott Bennett
Hi Alexey, On Wed, 22 Jul 2009 20:01:33 +0200 Alexey Shuvaev wrote: >On Wed, Jul 22, 2009 at 07:52:11AM -0500, Scott Bennett wrote: >> I wrote: >> > Sure, but OOo is so huge and requires so much other stuff >> >that there is almost certainly something it wants installed that >> >I do

Re: FreeBSD Port: python31-3.1_2

2009-07-23 Thread James Butler
2009/7/24 Sahil Tandon : > On Thu, 23 Jul 2009, Adam Townsend wrote: > >> I'm using the ports online (from the freebsd.org site) to get ports for my >> my computers running FreeBSD (running on dial-up). I found that the Python >> 3.1 source links are all broken. They all contain >> "/ftp/python//P

Re: FreeBSD Port: python31-3.1_2

2009-07-23 Thread Sahil Tandon
On Thu, 23 Jul 2009, Adam Townsend wrote: > I'm using the ports online (from the freebsd.org site) to get ports for my > my computers running FreeBSD (running on dial-up). I found that the Python > 3.1 source links are all broken. They all contain > "/ftp/python//Python-.tgz" in the urls. I foun

x11/kdebase4 build on CURRENT/BETA2

2009-07-23 Thread bsduser
Hi List, On recent CURRENT x11/kdebase4 won't build because usbdevices.h includes usb_revision.h which doesn't exist. Removing that include will at least cause kdebase4 to build successful again. Affected file: x11/kdebase4/work/kdebase-4.2.4/apps/kinfocenter/usbview/usbdevices.h Before the l

Re: Unable to build /x11/kdelibs3 with updated jpeg-7 port

2009-07-23 Thread Mel Flynn
On Tuesday 21 July 2009 02:59:29 Milan Obuch wrote: > On Tuesday 21 July 2009 12:40:34 Jerry wrote: > > It appears that the /x11/kdelibs3 ports insists on using the older > > "libjpeg.so.9" library. Since updating to jpeg-7, this library is > > no-longer available. Therefore, I cannot build this po

FreeBSD Port: python31-3.1_2

2009-07-23 Thread Adam Townsend
Hello, I'm using the ports online (from the freebsd.org site) to get ports for my my computers running FreeBSD (running on dial-up). I found that the Python 3.1 source links are all broken. They all contain "/ftp/python//Python-.tgz" in the urls. I found that the correct path in the urls is "/ft

Re: status of FreeBSD ports you maintain as of 20090705

2009-07-23 Thread Martin Tournoij
I now know more than ever why I switched to OpenBSD. FreeBSD people no longer seem to care about broken ports, or making people who submit broken patches maintainers, or even replying to my messages. Really, I have better things to do, I would have liked to do this in a nicer way, but I've been wa

Re: FreeBSD Port: mplayer-0.99.11_14

2009-07-23 Thread Peter Pentchev
On Thu, Jul 23, 2009 at 10:52:30AM -0400, Michael D. Stackhouse wrote: > Downloaded most current source snapshot, ran the configure command which > completed successfully. When I tried make command - get this error: > > "config.mak", line 4: Need an operator > "Makefile", line 820: warning: dupl

RE: FreeBSD Port: mplayer-0.99.11_14

2009-07-23 Thread Michael D. Stackhouse
Downloaded most current source snapshot, ran the configure command which completed successfully. When I tried make command - get this error: "config.mak", line 4: Need an operator "Makefile", line 820: warning: duplicate script for target "%.d" ignored "Makefile", line 823: warning: duplicate sc

multimedia/mplayer-devel ?

2009-07-23 Thread Andriy Gapon
Maybe it's time for multimedia/mplayer-devel? I am not volunteering, I am begging. Sorry about that :) -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "

Re: graphics/jpeg especially UPDATING

2009-07-23 Thread Jason J. Hellenthal
If you pkg_delete -r that will remove every package that depends on jpeg. This is not the right way of just getting rid of jpeg considering it involves the complete almost full re-installation of the entire system manually. A better route to upgrade would be: pkg_delete -f jpeg-\* reinstall the

Typo in screen's manpage

2009-07-23 Thread Reinout Stevens
Hi, Today I spotted a typo in screen's manpage: it's useful instead of usefull. I've made a small diff in case that's necessary. I also filed a "bug" in the screen dev's bugtracker. Regards, Reinout *** screen.1 2009-07-17 23:27:18.0 +0200 --- screenfix.1 2009-07-17 23:31:31.0

PHP gd issues

2009-07-23 Thread mediaslut von abfab
I had the same fatallibpngerror discovered yesterday. It seems like libpng version 1.2.37 was buggy. And version 1.2.38 is not available yet on FreeBSD Ports (although, I don't know if this bug is fixed in this version?). I have downgraded to version 1.2.35 and the error has gone away. Here's jus

PHP gd issues

2009-07-23 Thread mediaslut von abfab
I had the same fatallibpngerror discovered yesterday. It seems like libpng version 1.2.37 was buggy. And version 1.2.38 is not available yet on FreeBSD Ports (although, I don't know if this bug is fixed in the newest version?). I have downgraded to version 1.2.35 and the error has gone away. Here