Re: php5-extensions failed to install with lastest ports tree
On Dec 11, 2010, at 22:11 , Andres Chavez wrote: I just fixed it with a simple portupgrade -F and then reinstalled autoconf as usual ;) Regretfully, the way in which php* embeds autconf in the phpize script is a little tricky to work around. Suffice to say that whilst things are still a little fluid in autofoo land, work is in progress, and has been for many cpu years, to make things a little easier. -aDe ___ 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: emacs and gconf troubles
On 12/11/10 16:18, Ashish SHUKLA wrote: Hi Andrea, Sorry for the late reply. No problem! Really, thanks for your help. Okay, I'm able to reproduce warnings. As emacs tries to lookup DBUS session bus in the environment, and if it doesn't find one, it starts one. And dbus keeps running in the same TTY after you close emacs, so when you try to exit From the SSH session, it hangs waiting for all processes (attached to current TTY) to exit, and therefore you've to kill the SSH session forcibly. To verify this, you can kill the started dbus-daemon (attached to the same TTY) and you should be able to exit from SSH session as usual. I'm not sure if my explanation is correct for this behavior. I think it only explains part of it. Scenario A: _ dbus is running on localhost; _ I run Konsole and start Emacs from there; _ I get the warning (but DBUS is running!!!); _ after I exit Emacs, Konsole usually closes, but not always (!!!). Scenario B: _ dbus is running on localhost; _ I run Konsole and SSH into another box; _ on the remote box dbus is not running; _ I run Emacs, get the warning and DBUS is started; _ after I exit Emacs I cannot close Konsole unless I also close DBUS. So your explanation fits the second scenario perfectly, but does not explain the first. Also, I read I shouldn't run DBUS on the remote machine, but let Emacs connect to the one on localhost? Is this true? How do I do it? Should I run DBUS from rc on every box? bye Thanks av. ___ 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: emacs and gconf troubles
Andrea Venturoli writes: On 12/11/10 16:18, Ashish SHUKLA wrote: Hi Andrea, Sorry for the late reply. No problem! Really, thanks for your help. Okay, I'm able to reproduce warnings. As emacs tries to lookup DBUS session bus in the environment, and if it doesn't find one, it starts one. And dbus keeps running in the same TTY after you close emacs, so when you try to exit From the SSH session, it hangs waiting for all processes (attached to current TTY) to exit, and therefore you've to kill the SSH session forcibly. To verify this, you can kill the started dbus-daemon (attached to the same TTY) and you should be able to exit from SSH session as usual. I'm not sure if my explanation is correct for this behavior. I think it only explains part of it. Scenario A: _ dbus is running on localhost; _ I run Konsole and start Emacs from there; _ I get the warning (but DBUS is running!!!); _ after I exit Emacs, Konsole usually closes, but not always (!!!). Okay, DBus runs in two modes, system-mode, and session-mode. In system-mode, it's started by rc(8) during boot and exposes itself to all system-wide services (like HAL, Avahi, etc.), whereas in session-mode it's usually started by the desktop environment and provides service to all applications specific to the user session. In case, DBus wasn't found running in the session, it's started. So, what I think happening in your case is kdm isn't starting the DBus on startup of your session, which is why it only gets activated (started) when you start Emacs (or any other DBus consumer application). I use startx(1) and following is my $HOME/.xinitrc, where I start DBus prior to starting xmonad: #v+ chateau.d.if!abbe:~ % cat .xinitrc #!/bin/sh xrdb ~/.Xdefaults xmodmap ~/.Xmodmap exec dbus-launch --exit-with-session ck-launch-session xmonad 21 $HOME/.xsession-errors #v- Scenario B: _ dbus is running on localhost; _ I run Konsole and SSH into another box; _ on the remote box dbus is not running; _ I run Emacs, get the warning and DBUS is started; _ after I exit Emacs I cannot close Konsole unless I also close DBUS. So your explanation fits the second scenario perfectly, but does not explain the first. Also, I read I shouldn't run DBUS on the remote machine, but let Emacs connect to the one on localhost? Is this true? How do I do it? Should I run DBUS from rc on every box? And for good overall desktop experience, please make sure dbus gets started on system startup, as well as session startup. Lots of services expect DBus to be running. If you're running Emacs on server and don't want DBus to be started, then exclude DBUS using make config and reinstall the port. bye Thanks av. HTH -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! pgpzDR1z6MOBn.pgp Description: PGP signature
Re: JFYI: cyclic dependency on audio/jack and audio/pulseaudio
On 12/7/10 12:32 PM, Norikatsu Shigemura wrote: Hi. I found a cyclic dependency on audio/jack and audio/pulseaudio: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (snip) === pulseaudio-0.9.22 depends on shared library: jack.0 - not found ===Verifying install clean for jack.0 in /usr/ports/audio/jack === jackit-0.118.0_2 depends on executable: doxygen - not found ===Verifying install clean for doxygen in /usr/ports/devel/doxygen (snip) === doxygen-1.7.2 depends on executable: dot - not found ===Verifying install clean for dot in /usr/ports/graphics/graphviz (snip) === graphviz-2.26.3_3 depends on shared library: IL - not found ===Verifying install clean for IL in /usr/ports/graphics/devil === devil-1.7.8_6,1 depends on file: /usr/local/bin/sdl-config - not found ===Verifying install clean for /usr/local/bin/sdl-config in /usr/ports/devel/sdl12 (snip) === sdl-1.2.14_2,2 depends on shared library: pulse-simple.0 - not found ===Verifying install clean for pulse-simple.0 in /usr/ports/audio/pulseaudio : - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - By some OPTIONS set, pulseaudio depends on jack, cyclickly. In this time, JFYI. I'll try to test more deep. I don't just want to disable JACK in pulse. I wonder if some of those other dependencies (e.g. in doxygen) couldn't be better refined. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Problem with net-im/libnice
On 12/6/10 3:03 AM, Mattia Rossi wrote: Hi Marcus, just had some problems building and installing farsight2 : it couldn't find nice.0. So looking at libnice, I found that it doesn't install libnice.so.0 anymore (as per pkg-plist), but libnice.so.9 Changing farsight2 to nice.9 works, and it builds and installs fine. Don't know how much else depends on libnice though, so you might want to check that. libnice does still install libnice.so.0. You must have a problem with your libtool port. Rebuild and reinstall libtool, then rebuild and reinstall libnice. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: [Fwd: Re: acroread9 crashes after maybe 10 seconds ofoperation.]
Just an update: ti...@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.1-STABLE FreeBSD 8.1-STABLE #3: Thu Sep 16 22:18:48 CEST 2010 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 r...@kg-v2# portversion -v | grep acroread acroread9-9.3.4 = up-to-date with port acroreadwrapper-0.0.20100806 = up-to-date with port r...@kg-v2# portversion -v | grep ^linux linux-f10-atk-1.24.0= up-to-date with port linux-f10-cairo-1.8.0_1 = up-to-date with port linux-f10-curl-7.19.6_1 = up-to-date with port linux-f10-cyrus-sasl2-2.1.22_1 = up-to-date with port linux-f10-expat-2.0.1 = up-to-date with port linux-f10-flashplugin-10.1r102.65 = up-to-date with port linux-f10-fontconfig-2.6.0 = up-to-date with port linux-f10-gdk-pixbuf-0.22.0 = up-to-date with port linux-f10-gtk2-2.14.7_2 = up-to-date with port linux-f10-jpeg-6b = up-to-date with port linux-f10-libssh2-0.18 = up-to-date with port linux-f10-libxml2-2.7.3_2 = up-to-date with port linux-f10-nspr-4.7.6= up-to-date with port linux-f10-nss-3.12.3.99.3_1 = up-to-date with port linux-f10-openldap-2.4.12_1 = up-to-date with port linux-f10-openssl-0.9.8g= up-to-date with port linux-f10-pango-1.22.3_1= up-to-date with port linux-f10-png-1.2.37_1 = up-to-date with port linux-f10-sqlite3-3.5.9_1 = up-to-date with port linux-f10-tiff-3.8.2= up-to-date with port linux-f10-xorg-libs-7.4_1 = up-to-date with port linux-libgtkembedmoz-0.0.20100806 = up-to-date with port linux_base-f10-10_3 = up-to-date with port On the first start of acroread, I got this: ti...@kg-v2$ acroread (process:91859): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (acroread:91859): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:91859): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:91859): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:91859): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:91859): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:91859): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 libfam.so.0: cannot open shared object file: No such file or directory Failed to load module: /usr/lib/gio/modules/libgiofam.so terminate called after throwing an instance of 'RSException' On subsequent starts, I get this: ti...@kg-v2$ acroread (process:96112): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (acroread:96112): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:96112): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:96112): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:96112): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:96112): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 (acroread:96112): Gtk-WARNING **: /usr/local/lib/gtk-2.0/2.10.0/engines/libxfce.so: wrong ELF class: ELFCLASS64 terminate called after throwing an instance of 'RSException' But - if I start it from root, it works: r...@kg-v2# DISPLAY=:0.0 acroread (process:97831): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. libfam.so.0: cannot open shared object file: No such file or directory Failed to load module: /usr/lib/gio/modules/libgiofam.so (acroread:97831): GLib-GIO-WARNING **: Could not initialize inotify (acroread:97831): GLib-GIO-WARNING **: Could not initialize inotify (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type (acroread:97831): Gtk-WARNING **: Unable to find default local directory monitor type even if it does complain a lot. Strange? -- Regards,
coovachilling 1.2.5 for freebsd?
Hi the current version on ports for coovachilling is 1.0.12_1 so the lastest one at the official website of the project is version 1.2.5. So who's mantaining this port right now ? i would to figure out how to deal with the configure script to make it work on 8.1 ? cheers -- *Andrés Chavez IT System / Network Administrator CPF FreeBSD Server Administrator http://www.andreschavez.com.ve* ___ 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: coovachilling 1.2.5 for freebsd?
Hi, On Sun, Dec 12, 2010 at 8:51 PM, Andres Chavez fluxboxtrem...@gmail.com wrote: Hi the current version on ports for coovachilling is 1.0.12_1 so the lastest one at the official website of the project is version 1.2.5. So who's mantaining this port right now ? i would to figure out how to deal with the configure script to make it work on 8.1 ? r...@kg-vm# cd /usr/ports/net-mgmt/coovachilli; make maintainer ventur...@geeklan.co.uk Or just use freshports.org -- Regards, Torfinn Ingolfsen ___ 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: Updating Claws-Mail
Dnia 2010-12-11, o godz. 21:26:24 Alexander Leidinger alexan...@leidinger.net napisał(a): Pawel/Martin, yes, I would like to use the --disable-manual part (building the manual by default) to offer the possibility to not have that much dependencies (build depends). Pawel, Claws-Mail 3.7.7 was not building the pdf part of the docs for me. Did it for you? If yes, we have a missing build depends for the manual... There was change in pdf building requirements: 2010-12-03 [paul] 3.7.7cvs11 * configure.ac * manual/xml2pdf ** REMOVED ** * manual/dist/pdf/Makefile.am * manual/es/dist/pdf/Makefile.am * manual/fr/dist/pdf/Makefile.am * manual/pl/dist/pdf/Makefile.am simplify check for tools needed for manual building, remove xml2pdf and use docbook2pdf instead docbook2pdf is part of textproc/docbook-utils so now we have all dependencies correctly set. Pawel, are you interested to take over maintainership of CM itself? I can take over. -- pozdrawiam / with regards Paweł Pękala ___ 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: Updating Claws-Mail
On Sun, 12 Dec 2010 21:54:31 +0100 Paweł Pękala c...@o2.pl wrote: Dnia 2010-12-11, o godz. 21:26:24 Alexander Leidinger alexan...@leidinger.net napisał(a): Pawel/Martin, yes, I would like to use the --disable-manual part (building the manual by default) to offer the possibility to not have that much dependencies (build depends). Pawel, Claws-Mail 3.7.7 was not building the pdf part of the docs for me. Did it for you? If yes, we have a missing build depends for the manual... There was change in pdf building requirements: 2010-12-03 [paul] 3.7.7cvs11 * configure.ac * manual/xml2pdf ** REMOVED ** * manual/dist/pdf/Makefile.am * manual/es/dist/pdf/Makefile.am * manual/fr/dist/pdf/Makefile.am * manual/pl/dist/pdf/Makefile.am simplify check for tools needed for manual building, remove xml2pdf and use docbook2pdf instead docbook2pdf is part of textproc/docbook-utils so now we have all dependencies correctly set. Yes, but we don't want them ;) -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Security updates for packages?
Hi, Having not used FreeBSD for several years, I did a fresh install yesterday of 8.1-RELEASE, and then used pkg_add -r to install several packages. I then came across portaudit, ran it, and it indicated that I had three vulnerable packages (git, ruby, and sudo). Looking at http://www.vuxml.org/freebsd/, it appears that these were reported in July, August, and September respectively. Basically, I would think a freshly installed system would not have security vulnerabilities from months prior. Is that an erroneous assumption on my part, am I just misunderstanding something, or do I have something misconfigured? Do only ports get security updates, and not packages? Or is this related to the fact that I picked RELEASE, versus CURRENT or STABLE? Thanks, Kevin ___ 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: Security updates for packages?
On 12/12/2010 12:28, Kevin Kreamer wrote: Hi, Having not used FreeBSD for several years, I did a fresh install yesterday of 8.1-RELEASE, and then used pkg_add -r to install several packages. I then came across portaudit, ran it, and it indicated that I had three vulnerable packages (git, ruby, and sudo). Looking at http://www.vuxml.org/freebsd/, it appears that these were reported in July, August, and September respectively. How did you install the package? -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: Security updates for packages?
On 13.12.2010 00:25, Doug Barton wrote: On 12/12/2010 12:28, Kevin Kreamer wrote: Hi, Having not used FreeBSD for several years, I did a fresh install yesterday of 8.1-RELEASE, and then used pkg_add -r to install several packages. I then came across portaudit, ran it, and it indicated that I had three vulnerable packages (git, ruby, and sudo). Looking at http://www.vuxml.org/freebsd/, it appears that these were reported in July, August, and September respectively. How did you install the package? He said he installed it using pkg_add -r, which will have pulled the package from the 8.1-RELEASE repository which is quite old by now. Kevin: You can set PACKAGESITE environment variable to a different path, to get packages that are more up to date: PACKAGESITE=ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest pkg_add -r something Hope this helps, Thomas Steen Rasmussen ___ 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: Security updates for packages?
Am 12.12.2010 21:28, schrieb Kevin Kreamer: Hi, Having not used FreeBSD for several years, I did a fresh install yesterday of 8.1-RELEASE, and then used pkg_add -r to install several packages. I then came across portaudit, ran it, and it indicated that I had three vulnerable packages (git, ruby, and sudo). Looking at http://www.vuxml.org/freebsd/, it appears that these were reported in July, August, and September respectively. Basically, I would think a freshly installed system would not have security vulnerabilities from months prior. Is that an erroneous assumption on my part, am I just misunderstanding something, or do I have something misconfigured? Do only ports get security updates, and not packages? Or is this related to the fact that I picked RELEASE, versus CURRENT or STABLE? I'd advise to use portsnap to get an up to date ports tree (if you haven't used it, run portsnap fetch extract for the first time, and every time you feel like updating, you run portsnap fetch update). I'd also advise to install portmaster and upgrade your vulnerable ports with that, i. e.: portsnap fetch update# or extract if you're bootstrapping cd /usr/ports/ports-mgmt/portmaster make install clean # as root or toor or under sudo less /usr/src/UPDATING # check if there are relevant entries for your ports portmaster sudo git ruby That's it. For details, see the portsnap and portmaster manuals. HTH -- Matthias Andree ___ 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 Port: hercules-3.05_3 - Is 3.07 on the Horizon?
Hi There: Just wondering if Hercules version 3.07 (the latest version) will be ported to FreeBSD soon? I am trying to configure the existing version (3.05) with OS/360 and am having problems. The docs for Hercules are based on 3.07. I realize that you are probably quite busy with other issues, just thought I would ask, Kevin mcqui...@sfu.ca ___ 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
