compile time error in audio/xmixer 8.2-STABLE
I just updated my ports tree (csup -L2 ports-supfile) and while I was building audio/xmixer I got the following unexpected error: ===> Building for xmixer-gtk-0.9.4_6 [snip] cc -O2 -fno-strict-aliasing -pipe -std=gnu89 -I/usr/local/include/ -I/usr/local/include -DDEFAULT_MIXER=\"/dev/mixer\" -DOSS -I. -I./icons -DVERSION=\"0.9.4\" `pkg-config gtk+ --cflags` -c gui_gtk.c gui_gtk.c:480: warning: cast from pointer to integer of different size gui_gtk.c:480: error: initializer element is not constant gui_gtk.c:480: error: (near initialization for 'menu_items[1].callback_action') gui_gtk.c:481: warning: cast from pointer to integer of different size gui_gtk.c:481: error: initializer element is not constant gui_gtk.c:481: error: (near initialization for 'menu_items[2].callback_action') gui_gtk.c:485: warning: cast from pointer to integer of different size gui_gtk.c:485: error: initializer element is not constant gui_gtk.c:485: error: (near initialization for 'menu_items[6].callback_action') gui_gtk.c: In function 'gui_main': gui_gtk.c:655: warning: cast from pointer to integer of different size *** Error code 1 Stop in /usr/ports/audio/xmixer/work/xmixer. *** Error code 1 Stop in /usr/ports/audio/xmixer. What is this compile error caused by and how do I workaround it? Thanks. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template ->| ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/net/click anyone ?
On Fri, Jul 1, 2011 at 1:41 PM, Luigi Rizzo wrote: > [Cc to ports@freebsd,org, but please followup at n...@freebsd.org] > > anyone interested in taking over maintainership of ports/net/click ? > We have 1.5.0 in the tree, which is old and partly broken. Luigi, coming back to an earlier email post you had on click has someone taken maintainership, Id be willing since I am using it in development areas, and belive it should be part of the ports tree still ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On 25 November 2011 15:06, Julian H. Stacey wrote: > Hi, > Kaya Saman wrote: >> On 11/25/2011 02:51 PM, Julian H. Stacey wrote: >> > Kaya Saman wrote: >> >> Hi, >> >> >> >> I'm running FreeBSD version 8.0 x64 edition on my server with multiple >> >> jails. >> > < Detail deleted> >> > >> >> Can anyone help with my issues?? >> > 8.0 is too old, November 2009 >> > http://www.freebsd.org/releases/ >> > >> > 8.0 Is not supported. >> > http://www.freebsd.org/security/security.html#sup >> > >> > My machine ceased to crash when I moved from 8.0 to 8.2, >> > I seem to recall other problems eased too. >> > >> > So upgrade to at least 8.1 ! >> > >> > If you management are saying stay at `proven' 8.0 rather than 8.2, >> > think again. >> > >> > It's well known that .0 releases can be problematic, which is I >> > recall why 8.1 has extended support (even beyond 8.2), useful for >> > those who don't want to keep upgrading. >> > >> > Yes, 9.0-RC2 is available for test for those wanting new features, >> > not for you if you'r still on 8.0. One would expect less stability >> > from 9.0-RC2 than 8.0.& no more from 9.0 than 8.0, so go for 8.1 >> > or 8.2 then wait for 9.1 not 9.0. >> > >> > Cheers, >> > Julian >> How is the upgrade of versions done? >> >> I'm sorry I've never done it before; from my linux experience on Debian >> at least it's a bit messy. >> >> I found this: >> >> http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html >> >> So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var >> >> then do: >> >> freebsd-update -r 8.2-RELEASE upgrade >> >> freebsd-update install >> >> shutdown -r now >> >> freebsd-update install >> >> # portupgrade -f ruby >> # rm /var/db/pkg/pkgdb.db >> # portupgrade -f ruby18-bdb >> # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db >> # portupgrade -af >> >> freebsd-update install >> >> >> How will this affect my Jails though? Will I need to rebuild them also? >> >> I mean how will I know if everything is the same as before the upgrade >> but obviously just newer? > > Sorry, short of time here, so in brief: > This the wrong list to ask about upgrades. > Read http://www.freebsd.org > I dont personaly keep up to date with latest fancy BSD-specific > update scripts (as I've been doing Unix decades, & by reflex > make all of src/ & ports/ that I use, but certainly back up etc > & var first ) > Others may have more time to add info, but better ask on hackers@ > (or questions@ re upgrades) > > I would guess jails from 8.0 would survive on 8.2, Try on a spare box. This actually looks kinda like an INDEX issue. # make -C /usr/ports fetchindex should fix it. Also, since portupgrade is unmaintained, may I suggest getting to know portmaster Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/162877: [PATCH] lang/php5: turn on Apache module build by default
On Fri, Nov 25, 2011 at 5:26 PM, wrote: > Synopsis: [PATCH] lang/php5: turn on Apache module build by default > > State-Changed-From-To: open->closed > State-Changed-By: ale > State-Changed-When: Fri Nov 25 15:25:31 UTC 2011 > State-Changed-Why: > Not the right thing, you should build mod_php5 tailored to your apache > installation. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=162877 Could you please explain it in detail? What you mean by 'tailored'? Do you understand that port (I mean package) is almost completely useless without mod_php enabled? Thanks in advance! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10 fix & www/neon29 - no shared lib
On 11/25/2011 15:25, Lev Serebryakov wrote: Hello, freebsd-ports. My port shows strange behavior on -CURRENT now: it uses gnome-libtool, and configure itself with enabled share library. But on "install" stage it doesn't install shared library at all. I don't understand all this "FREEBSD10 FIX" magic, and don't understand what goes wrong. Setting UNAME_r to '9.9-HACK' doesn't help. Any ideas? Actually i cant confirm that, did u upgrade from 9.X to 10? if so then please rebuild libtools and all dependency ports. - Martin -- +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD 10 fix & www/neon29 - no shared lib
Hello, freebsd-ports. My port shows strange behavior on -CURRENT now: it uses gnome-libtool, and configure itself with enabled share library. But on "install" stage it doesn't install shared library at all. I don't understand all this "FREEBSD10 FIX" magic, and don't understand what goes wrong. Setting UNAME_r to '9.9-HACK' doesn't help. Any ideas? -- // Black Lion AKA Lev Serebryakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
Hi, Reference: > From: Kaya Saman > Date: Fri, 25 Nov 2011 15:41:26 +0200 > Message-id: <4ecf9b06.1090...@gmail.com> Kaya Saman wrote: > This is a multi-part message in MIME format. > --080607030603050400060904 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > On 11/25/2011 02:51 PM, Julian H. Stacey wrote: > > Kaya Saman wrote: > >> Hi, > >> > >> I'm running FreeBSD version 8.0 x64 edition on my server with multiple > >> jails. > > < Detail deleted> > > > >> Can anyone help with my issues?? > > 8.0 is too old, November 2009 > > http://www.freebsd.org/releases/ > > > > 8.0 Is not supported. > > http://www.freebsd.org/security/security.html#sup > > > > My machine ceased to crash when I moved from 8.0 to 8.2, > > I seem to recall other problems eased too. > > > > So upgrade to at least 8.1 ! > > > > If you management are saying stay at `proven' 8.0 rather than 8.2, > > think again. > > > > It's well known that .0 releases can be problematic, which is I > > recall why 8.1 has extended support (even beyond 8.2), useful for > > those who don't want to keep upgrading. > > > > Yes, 9.0-RC2 is available for test for those wanting new features, > > not for you if you'r still on 8.0. One would expect less stability > > from 9.0-RC2 than 8.0.& no more from 9.0 than 8.0, so go for 8.1 > > or 8.2 then wait for 9.1 not 9.0. > > > > Cheers, > > Julian > How is the upgrade of versions done? > > I'm sorry I've never done it before; from my linux experience on Debian > at least it's a bit messy. > > I found this: > > http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html > > So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var > > then do: > > freebsd-update -r 8.2-RELEASE upgrade > > freebsd-update install > > shutdown -r now > > freebsd-update install > > # portupgrade -f ruby > # rm /var/db/pkg/pkgdb.db > # portupgrade -f ruby18-bdb > # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db > # portupgrade -af > > freebsd-update install > > > How will this affect my Jails though? Will I need to rebuild them also? > > I mean how will I know if everything is the same as before the upgrade > but obviously just newer? Sorry, short of time here, so in brief: This the wrong list to ask about upgrades. Read http://www.freebsd.org I dont personaly keep up to date with latest fancy BSD-specific update scripts (as I've been doing Unix decades, & by reflex make all of src/ & ports/ that I use, but certainly back up etc & var first ) Others may have more time to add info, but better ask on hackers@ (or questions@ re upgrades) I would guess jails from 8.0 would survive on 8.2, Try on a spare box. > --080607030603050400060904 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: 7bit No HTML duplicates Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On Fri, 25 Nov 2011 12:14:40 +0200 Kaya Saman wrote: > I used the: > > portsnap fetch extract upgrade I assume you mean update rather than upgrade. You don't need to run extract and update together. You run extract the first time to extract the full snapshot and then update subsequently. That's not your problem though. > command in order to get the latest editions of each port. > > Then ran portupgrade -a > > > for some weird reason the packages listed below didn't get upgraded; > upon the error output 'portupgrade' was trying to replace the port > with the same version: eg. apache-2.2.13 error came up with the fact > that apache-2.2.13 was to be installed again but was already > installed so I needed to run: make deinstall; make install; make > clean in order to re-install apache22.. It would have been more useful to see the actual output with some context. > # pkg_version -v | grep updating Try running pkg_version -Iv to see if it's an INDEX problem ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On 11/25/2011 04:05 PM, Daniel Nebdal wrote: On Fri, Nov 25, 2011 at 2:56 PM, Kaya Saman wrote: On 11/25/2011 03:44 PM, Daniel Nebdal wrote: On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizenwrote: On Fri, 25 Nov 2011, the wise Kaya Saman wrote: Then ran portupgrade -a for some weird reason the packages listed below didn't get upgraded; upon the error output 'portupgrade' was trying to replace the port with the same version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 was to be installed again but was already installed so I needed to run: make deinstall; make install; make clean in order to re-install apache22.. Did you csup your portstree first? He used portsnap, which does the same thing. By the way: "portsnap fetch extract update" is pointless: "extract" gives you a clean copy of the last fetched version, and "update" extracts only what has changed since the last extract or update. Use "portsnap fetch extract" once, then "portsnap fetch update" from then on. (Or replace "fetch" with "cron" if you're doing this automatically - it adds a random delay to not overload the servers at popular times of the day.) Thanks for the tip! It's my first time updating/upgrading a FreeBSD system so any 'experienced' advice is always valid and welcome :-) Ah, right. :) The nice thing with "update" is that it's much faster than "extract" - as I'm sure you'll notice. Would you also advise to upgrade my BSD 'release'? If so I would upgrade to 8.2 as stated in a previous posting but since I'm running jails and many services aggregated into one machine, what's the best way to proceed? I'm currently just backing up /etc, /var, /usr/shared, /usr/local/etc, /usr/local/var, and /usr/local/shared. Will the freebsd-upgrade tool wipe all my config files? Or will the upgrade be seamless? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen wrote: > On Fri, 25 Nov 2011, the wise Kaya Saman wrote: > >> Then ran portupgrade -a >> >> for some weird reason the packages listed below didn't get upgraded; upon >> the error output 'portupgrade' was trying to replace the port with the same >> version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 >> was to be installed again but was already installed so I needed to run: make >> deinstall; make install; make clean in order to re-install apache22.. > > Did you csup your portstree first? > He used portsnap, which does the same thing. By the way: "portsnap fetch extract update" is pointless: "extract" gives you a clean copy of the last fetched version, and "update" extracts only what has changed since the last extract or update. Use "portsnap fetch extract" once, then "portsnap fetch update" from then on. (Or replace "fetch" with "cron" if you're doing this automatically - it adds a random delay to not overload the servers at popular times of the day.) -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On Fri, Nov 25, 2011 at 2:56 PM, Kaya Saman wrote: > On 11/25/2011 03:44 PM, Daniel Nebdal wrote: >> >> On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen wrote: >>> >>> On Fri, 25 Nov 2011, the wise Kaya Saman wrote: >>> Then ran portupgrade -a for some weird reason the packages listed below didn't get upgraded; upon the error output 'portupgrade' was trying to replace the port with the same version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 was to be installed again but was already installed so I needed to run: make deinstall; make install; make clean in order to re-install apache22.. >>> >>> Did you csup your portstree first? >>> >> He used portsnap, which does the same thing. >> By the way: "portsnap fetch extract update" is pointless: "extract" >> gives you a clean copy of the last fetched version, and "update" >> extracts only what has changed since the last extract or update. Use >> "portsnap fetch extract" once, then "portsnap fetch update" from then >> on. (Or replace "fetch" with "cron" if you're doing this automatically >> - it adds a random delay to not overload the servers at popular times >> of the day.) >> > Thanks for the tip! > > It's my first time updating/upgrading a FreeBSD system so any 'experienced' > advice is always valid and welcome :-) > Ah, right. :) The nice thing with "update" is that it's much faster than "extract" - as I'm sure you'll notice. -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On 11/25/2011 03:44 PM, Daniel Nebdal wrote: On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen wrote: On Fri, 25 Nov 2011, the wise Kaya Saman wrote: Then ran portupgrade -a for some weird reason the packages listed below didn't get upgraded; upon the error output 'portupgrade' was trying to replace the port with the same version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 was to be installed again but was already installed so I needed to run: make deinstall; make install; make clean in order to re-install apache22.. Did you csup your portstree first? He used portsnap, which does the same thing. By the way: "portsnap fetch extract update" is pointless: "extract" gives you a clean copy of the last fetched version, and "update" extracts only what has changed since the last extract or update. Use "portsnap fetch extract" once, then "portsnap fetch update" from then on. (Or replace "fetch" with "cron" if you're doing this automatically - it adds a random delay to not overload the servers at popular times of the day.) Thanks for the tip! It's my first time updating/upgrading a FreeBSD system so any 'experienced' advice is always valid and welcome :-) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On 11/25/2011 02:51 PM, Julian H. Stacey wrote: Kaya Saman wrote: Hi, I'm running FreeBSD version 8.0 x64 edition on my server with multiple jails. < Detail deleted> Can anyone help with my issues?? 8.0 is too old, November 2009 http://www.freebsd.org/releases/ 8.0 Is not supported. http://www.freebsd.org/security/security.html#sup My machine ceased to crash when I moved from 8.0 to 8.2, I seem to recall other problems eased too. So upgrade to at least 8.1 ! If you management are saying stay at `proven' 8.0 rather than 8.2, think again. It's well known that .0 releases can be problematic, which is I recall why 8.1 has extended support (even beyond 8.2), useful for those who don't want to keep upgrading. Yes, 9.0-RC2 is available for test for those wanting new features, not for you if you'r still on 8.0. One would expect less stability from 9.0-RC2 than 8.0.& no more from 9.0 than 8.0, so go for 8.1 or 8.2 then wait for 9.1 not 9.0. Cheers, Julian How is the upgrade of versions done? I'm sorry I've never done it before; from my linux experience on Debian at least it's a bit messy. I found this: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var then do: freebsd-update -r 8.2-RELEASE upgrade freebsd-update install shutdown -r now freebsd-update install # portupgrade -f ruby # rm /var/db/pkg/pkgdb.db # portupgrade -f ruby18-bdb # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db # portupgrade -af freebsd-update install How will this affect my Jails though? Will I need to rebuild them also? I mean how will I know if everything is the same as before the upgrade but obviously just newer? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
On Fri, 25 Nov 2011, the wise Kaya Saman wrote: Then ran portupgrade -a for some weird reason the packages listed below didn't get upgraded; upon the error output 'portupgrade' was trying to replace the port with the same version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 was to be installed again but was already installed so I needed to run: make deinstall; make install; make clean in order to re-install apache22.. Did you csup your portstree first? Regards, Marco -- Happy feast of the pig! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
Kaya Saman wrote: > Hi, > > I'm running FreeBSD version 8.0 x64 edition on my server with multiple > jails. < Detail deleted > > Can anyone help with my issues?? 8.0 is too old, November 2009 http://www.freebsd.org/releases/ 8.0 Is not supported. http://www.freebsd.org/security/security.html#sup My machine ceased to crash when I moved from 8.0 to 8.2, I seem to recall other problems eased too. So upgrade to at least 8.1 ! If you management are saying stay at `proven' 8.0 rather than 8.2, think again. It's well known that .0 releases can be problematic, which is I recall why 8.1 has extended support (even beyond 8.2), useful for those who don't want to keep upgrading. Yes, 9.0-RC2 is available for test for those wanting new features, not for you if you'r still on 8.0. One would expect less stability from 9.0-RC2 than 8.0. & no more from 9.0 than 8.0, so go for 8.1 or 8.2 then wait for 9.1 not 9.0. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
change in portupgrade reporting for editors/koffice-kde4
I have noticed a small change in reporting from portupgrade for koffice-kde4. Current behaviour reports as below even when koffice-kde4 is up to date. Previously if koffice-kde4 was up to date there was no such report. The previous behaviour seemed preferable as one only checked to update koffice when the report, as shown below, appeared. Now one always has to check! Is the change intentional - if so why? [root@dns1 /usr/ports/x11-toolkits/qt33]# portupgrade -a [Updating the pkgdb in /var/db/pkg ... - 1046 packages found (-2 +2) (...).. done] ** Port marked as IGNORE: editors/koffice-kde4: does not build with x11-toolkits/qt33 installed. Please deinstall qt-3.x first ** Listing the failed packages (-:ignored / *:skipped / !:failed) - editors/koffice-kde4 (marked as IGNORE) Thanks in advance david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Strange issues while upgrading ports
Hi, I'm running FreeBSD version 8.0 x64 edition on my server with multiple jails. #uname -a FreeBSD Server 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 A few weeks back I performed a portupgrade on all my installed ports for the / root filesystem (not jails). I used the: portsnap fetch extract upgrade command in order to get the latest editions of each port. Then ran portupgrade -a for some weird reason the packages listed below didn't get upgraded; upon the error output 'portupgrade' was trying to replace the port with the same version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 was to be installed again but was already installed so I needed to run: make deinstall; make install; make clean in order to re-install apache22.. # pkg_version -v | grep updating adodb-4.99.1 < needs updating (port has 4.99.2) apache-2.2.13 < needs updating (port has 2.2.21) cacti-0.8.7g < needs updating (port has 0.8.7h) curl-7.20.1 < needs updating (port has 7.21.3_2) drupal5-5.20 < needs updating (port has 5.22) gtk-2.16.6 < needs updating (port has 2.24.6) libltdl-2.2.6a < needs updating (port has 2.2.6b) mod_python-3.3.1_2 < needs updating (port has 3.3.1_3) mpg123-1.9.0 < needs updating (port has 1.13.4) mutt-1.4.2.3_3 < needs updating (port has 1.4.2.3_6) oss-4.2.b2000 < needs updating (port has 4.2.b2005) php5-5.2.11 < needs updating (port has 5.3.8) php5-bcmath-5.2.11 < needs updating (port has 5.3.8) php5-gd-5.2.11 < needs updating (port has 5.3.8) php5-mbstring-5.2.11 < needs updating (port has 5.3.8) php5-mysql-5.2.11 < needs updating (port has 5.3.8) php5-pcre-5.2.11 < needs updating (port has 5.3.8) php5-session-5.2.11 < needs updating (port has 5.3.8) php5-simplexml-5.2.11 < needs updating (port has 5.3.8) php5-snmp-5.2.11 < needs updating (port has 5.3.8) php5-sockets-5.2.11 < needs updating (port has 5.3.8) php5-spl-5.2.11 < needs updating (port has 5.3.8) php5-sqlite-5.2.11 < needs updating (port has 5.3.8) php5-xml-5.2.11 < needs updating (port has 5.3.8) squid-2.7.7 < needs updating (port has 2.7.9_1) xmms2-0.6_1 < needs updating (port has 0.7_2) I really can't work out why the versions specified from pkg_version -v are not in my ports tree even with updating it with the latest versions?? Additionally I have an issue with Munin and Logwatch since the upgrade in that Munin comes up with this error in /var/log/messages: Nov 25 12:03:03 Server kernel: <6>pid 72181 (perl), uid 1001: exited on signal 11 (UID of Munin is 1001), and no data is generated in the graphs. Logwatch doesn't output the full information anymore: ### Logwatch 7.4.0 (03/01/11) Processing Initiated: Fri Nov 25 04:02:02 2011 Date Range Processed: yesterday ( 2011-Nov-24 ) Period is day. Detail Level of Output: 10 Type of Output/Format: mail / text Logfiles for Host: Server ## - Disk Space Begin Filesystem 512-blocks Used Avail Capacity Mounted on /dev/ad4s1a 71079512 43091732 2230142066%/ devfs2 2 0 100%/dev ZFS_POOL_1 7662907136 5955981824 170692531278%/mnt/zfs devfs2 2 0 100%/var/jail/named_1/dev devfs2 2 0 100%/var/jail/named_2/dev devfs2 2 0 100%/var/jail/squid/dev devfs2 2 0 100%/var/jail/postfix/dev devfs2 2 0 100%/mnt/zfs/jail/imap/dev devfs => 100% Used. Warning. Disk Filling up. devfs => 100% Used. Warning. Disk Filling up. devfs => 100% Used. Warning. Disk Filling up. devfs => 100% Used. Warning. Disk Filling up. devfs => 100% Used. Warning. Disk Filling up. devfs => 100% Used. Warning. Disk Filling up. -- Disk Space End - ## Logwatch End # and instead just shows the above. I'm guessing there's a problem with Perl reading the logfiles hence the fact that it's mentioned in Munin's error log in Messages and the fact that logwatch is basically a Perl script. Can anyone help with my issues?? Thanks. Kaya ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
