portupgrade-devel: portversion -vl'' does not show current version
After upgrading from portupgrade to portupgrade-devel the command $ portversion -vl'' does not show the _current_ version anymore. Why was it removed? I found the information useful. before: gnutls-2.4.0 needs updating (port has 2.4.1) now: gnutlsneeds updating (port has 2.4.1) S. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-devel: portversion -vl'' does not show current version
Sandra Kachelmann wrote: After upgrading from portupgrade to portupgrade-devel the command $ portversion -vl'' does not show the _current_ version anymore. Why was it removed? I found the information useful. before: gnutls-2.4.0 needs updating (port has 2.4.1) now: gnutlsneeds updating (port has 2.4.1) Looks like it's a side effect of new options implementation. Now you can use -Fvl options. But I'll think to back this functionality. Thanks. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
clamav bug
Hi,
I have just update m ports collection. My FreeBSD is 6.0-RELEASE, and when I
tried to install clamav from ports collection it returned an error:
# make install
=== Building for clamav-0.93.1_2
make all-recursive
Making all in libclamunrar
Making all in libclamunrar_iface
Making all in libclamav
Making all in lzma
Making all in .
Making all in clamscan
/bin/sh /usr/local/bin/libtool --tag=CC--mode=link cc -O2
-fno-strict-aliasing -pipe -L/usr/local/lib -lthr -o clamscan output.o
getopt.o cfgparser.o misc.o options.o clamscan.o others.o manager.o
treewalk.o ../libclamav/libclamav.la -lthr
cc -O2 -fno-strict-aliasing -pipe -o .libs/clamscan output.o getopt.o
cfgparser.o misc.o options.o clamscan.o others.o manager.o treewalk.o
-L/usr/local/lib ../libclamav/.libs/libclamav.so
/usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar_iface/.libs/libcl
amunrar_iface.so
/usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar/.libs/libclamunra
r.so -lbz2 /usr/local/lib/libgmp.so -lz -lthr -Wl,--rpath
-Wl,/usr/local/lib
../libclamav/.libs/libclamav.so: undefined reference to `gethostbyname_r'
*** Error code 1
Stop in /usr/ports/security/clamav/work/clamav-0.93.1/clamscan.
*** Error code 1
Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
*** Error code 1
Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
*** Error code 1
Stop in /usr/ports/security/clamav.
*** Error code 1
Stop in /usr/ports/security/clamav.
Tried to modify Makefile into the following:
CONFIGURE_ARGS= --with-dbdir=${DBDIR} \
--with-zlib=/usr \
--without-thread \
--disable-gethostbyname_r \
--disable-zlib-vcheck \
--disable-clamuko \
--disable-clamav \
--disable-pthread \
--enable-bigstack \
--enable-readdir_r \
Please advise.
Kind regards,
Yance
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea for next portupgrade
Albert Shih wrote: Hi all I want to thanks the dev of portupgrade. It save lots of my time and work fine. But I just think about our new computer with the lot of core, a standard server have dual proc with quad-core that's mean 8 core availble. In the next version of portupgrade, IMHO it's good idea to have option to make portupgrade working with many proc. Because what I known many ports cannot by compile with «-j8» option. In that case when we make portupgrade --all -b we have just one compilation. It's enough when we have 1 or 2 procs. But now with 8 or more proc If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. But it's just a idea. Maybe it's already in the roadmap ... I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. If somebody could, I would take patches with pleasure. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea for next portupgrade
Le 03/07/2008 à 17:23:52+0400, Sergey Matveychuk a écrit Albert Shih wrote: If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. But it's just a idea. Maybe it's already in the roadmap ... I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. I understand. What you've done is already fantastic. Thanks for you time. If somebody could, I would take patches with pleasure. Humm...as I say I'm not progammer and I never write event «hello world» in ruby. Regards. -- Albert SHIH SIO batiment 15 Observatoire de Paris Meudon 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26 Heure local/Local time: Jeu 3 jul 2008 15:42:06 CEST ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea for next portupgrade
Sergey Matveychuk writes: If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. It is also my understanding that ruby (used to manage the ports database) a) is not re-entrant and/or b) does not lock the files it is using/changing. Having two instances running at once causes Bad Things(tm) to happen. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
UPDATING entry 20080701
For me the following command does nothing for me even though I currently have neon26-0.26.4_1 installed: $ portupgrade -o www/neon28 neon Adding -f doesn't help either. I think that this is an old and known regression[*]. Just wanted to remind about this issue and warn unsuspecting ports users. Just in case: my system is 6.3/amd64, portupgrade is not -devel. Reference: http://freebsd.monkey.org/freebsd-ports/200706/msg00120.html -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea for next portupgrade
Robert Huff wrote: Sergey Matveychuk writes: If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. It is also my understanding that ruby (used to manage the ports database) a) is not re-entrant and/or b) does not lock the files it is using/changing. Having two instances running at once causes Bad Things(tm) to happen. It's not a ruby issue. Now you can run a few portupgrade processes if sets of updating ports is not intercepted. Otherwise one portupgrade process can clear a port directory when another process build the port. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clamav bug
Hi, In message [EMAIL PROTECTED], yance [EMAIL PROTECTED] writes I have just update m ports collection. My FreeBSD is 6.0-RELEASE, and when I tried to install clamav from ports collection it returned an error: The problem is not clamav - it's your old and unsupported operating system. 6.0-RELEASE is End of Life and no longer supported by the ports collection. There's been one thread about clamav in recent days, where the maintainer responded that the necessary support in the port for these EoL versions of FreeBSD has been removed. You are strongly recommended to upgrade to a supported version of FreeBSD - 6.3-RELEASE or 7.0-RELEASE. Information on the supported versions and their respective End of Life dates can be found at http://www.freebsd.org/security/index.html (look towards the bottom of the page). FreeBSD 6.0-RELEASE went end of life on 31 January 2007, I believe. Best wishes, David -- David Wood [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Akode-plugins problem
Does anyone know best way to deal with this one?? I am going round in circles here!!! #portupgrade -a [Gathering depends. ...] [Gathering depends for audio/akode-plugins-mpc .. done] [Gathering depends for audio/akode-plugins-mpeg . done] [Gathering depends for audio/akode-plugins-oss .. done] ** Port directory not found: audio/akode-plugins-polypaudio /usr/local/sbin/portupgrade:1362:in `get_pkgname': port directory error (PortDirError) from /usr/local/sbin/portupgrade:623:in `main' from /usr/local/sbin/portupgrade:618:in `each' from /usr/local/sbin/portupgrade:618:in `main' from /usr/local/sbin/portupgrade:582:in `catch' from /usr/local/sbin/portupgrade:582:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1299:in `catch' ... 6 levels... from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:228:in `new' from /usr/local/sbin/portupgrade:228:in `main' from /usr/local/sbin/portupgrade:2115 [EMAIL PROTECTED] /usr/ports/audio]# pkgdb -F --- Checking the package registry database Stale origin: 'audio/akode-plugins-polypaudio': perhaps moved or obsoleted. - The port 'audio/akode-plugins-polypaudio' was removed on 2008-01-01 because: Polypaudio is obsolete in favor of pulseaudio - Hint: akode-plugins-polypaudio-2.0.1_1,1 is required by the following package(s): kdemultimedia-3.5.8 kde-3.5.8 - Hint: checking for overwritten files... - No files installed by akode-plugins-polypaudio-2.0.1_1,1 have been overwritten by other packages. Deinstall akode-plugins-polypaudio-2.0.1_1,1 ? [no] y --- Deinstalling 'akode-plugins-polypaudio-2.0.1_1,1' pkg_delete: package 'akode-plugins-polypaudio-2.0.1_1,1' is required by these other packages and may not be deinstalled: kde-3.5.8 kdemultimedia-3.5.8 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! akode-plugins-polypaudio-2.0.1_1,1(pkg_delete failed) Command failed [exit code 1]: /usr/local/sbin/pkg_deinstall akode-plugins-polypaudio-2.0.1_1,1 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea for next portupgrade
On Thu, Jul 3, 2008 at 10:33 AM, Sergey Matveychuk [EMAIL PROTECTED] wrote: Robert Huff wrote: Sergey Matveychuk writes: If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. This is a VERY useful idea, and it would be great to get it implemented I wonder if someone would start a bounty, and have several people donate $50 - $100 via paypal maybe we could pay someone for a working patch. I am in for $50 Sam Fourman Jr. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cfengine fatal error
Well it works fine outside of a jail. Are you using the ldd command inside the jail, or outside of it? You need to make sure all of those libraries are available inside the jail... On Jul 2, 2008, at 5:25 PM, EVERS ROB wrote: Hi Sergei, When running cfengine 2.2.7 (and before that 2.2.3) (in a jail) on my FreeBSD 6.3 box the cfservd crashes after client connect. Sys version FreeBSD cfengine.debank.tv 6.3-STABLE FreeBSD 6.3-STABLE #0: Wed Jun 4 05:22:14 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ FLAPPIE amd64 Last piece of cfservd -d1 output: LastSeen(cvs.debank.tv) reg IPV4 address sockaddr_ntop(192.168.1.33) Found address (192.168.1.33) for host cvs.debank.tv GetMacroValue(server,LastSeenExpireAfter) GetMacroValue(server,LastSeenExpireAfter): using scope 'server' for variable 'LastSeenExpireAfter' READ -192.168.1.33 WriteDB = -192.168.1.33 WriteDB = Thu:Hr02:Min10_15 Transmission empty or timed out... Transaction Receive [][] RecvSocketStream(0) cfservd terminating NULL transmission! Terminating thread... ***Closing socket 5 from 192.168.1.26 Fatal error 'kse_exit() failed for system scope thread' at line 1215 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) [EMAIL PROTECTED]:~#ldd `which cfservd` /usr/local/sbin/cfservd: libdb-4.6.so.0 = /usr/local/lib/libdb-4.6.so.0 (0x8006bd000) libpthread.so.2 = /usr/lib/libpthread.so.2 (0x8008ef000) libcrypto.so.4 = /lib/libcrypto.so.4 (0x800a1a000) libm.so.4 = /lib/libm.so.4 (0x800c61000) libc.so.6 = /lib/libc.so.6 (0x800d7d000) libpthread.so.2 = /lib/libpthread.so.2 (0x800f8f000) It looks like a threading error but I can't seem to figure out what exactly goes wrong ( a ktrace doesn't reveal anything), any ideas on this or what debugging do I need to provide to make it more clear. Thanks, Rob Evers P.S. please cc me as I'm not on ports@ -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnash-0.8.3: build fails on 6.3
on 01/07/2008 22:36 Dmitry Marakasov said the following: * Andriy Gapon ([EMAIL PROTECTED]) wrote: Any news on the problem? I've gon 2 more reports of gnash failure on 6.3. I've tried to reproduce bug in 6.3 jail, but with no luck (tried rebuilding everything with different suspicios options that may affect gnash or ports it depends on (WITH_OPTIMIZED_CFLAGS, WITHOUT_DEBUG), also tried to build everything when multiple versions of gcc are present - it just builds without problems. I also tried clean re-install (as opposed to upgrade via portupgrade) and that resulted in the same error. Could you please mail me your make.conf and `pkg_info` output? Let me send those a bit later. Now an important finding - it seems that g++42 tries to use different libstdc++, not its own. I verified with nm that missing symbols are present in /usr/local/lib/gcc-4.2.4/libstdc++.so.6, but g++42 doesn't see them. I explicitly added the library to command line and then linking succeeded. I am quite puzzled as to why g++42 would not see its own libstdc++ or prefer other libstdc++ over its own. Might this be because of -L/usr/lib in the command line? BTW, I have the following GCCs installed: gcc-4.2.4_20080430 gcc-4.3.2_20080626 gcc-ooo-3.4.1_3 Plus base GCC 3.4.6. And their libs: /usr/lib/libstdc++.so /usr/lib/libstdc++.so.5 /usr/lib32/libstdc++.so /usr/lib32/libstdc++.so.5 /usr/local/lib/gcc-4.2.4/libstdc++.so /usr/local/lib/gcc-4.2.4/libstdc++.so.6 /usr/local/lib/gcc-4.3.2/libstdc++.so /usr/local/lib/gcc-4.3.2/libstdc++.so.6 -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnash-0.8.3: build fails on 6.3
on 03/07/2008 20:46 Andriy Gapon said the following: Now an important finding - it seems that g++42 tries to use different libstdc++, not its own. I verified with nm that missing symbols are present in /usr/local/lib/gcc-4.2.4/libstdc++.so.6, but g++42 doesn't see them. I explicitly added the library to command line and then linking succeeded. I am quite puzzled as to why g++42 would not see its own libstdc++ or prefer other libstdc++ over its own. Might this be because of -L/usr/lib in the command line? Seems so - I added -v flag tp g++42 linking invocation and here's a snippet from output: /usr/local/libexec/gcc/x86_64-portbld-freebsd6.3/4.2.4/collect2 -V -dynamic-linker /libexec/ld-elf.so.1 -o .libs/gprocessor /usr/lib/crt1.o /usr/lib/crti.o /usr/local/lib/gcc-4.2.4/gcc/x86_64-portbld-freebsd6.3/4.2.4/crtbegin.o -L/usr/local/lib -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib/gcc-4.2.4/gcc/x86_64-portbld-freebsd6.3/4.2.4 -L/usr/local/lib/gcc-4.2.4/gcc/x86_64-portbld-freebsd6.3/4.2.4/../../.. /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -rpath ... A s we can see -L/usr/lib comes before gcc-4.2.4 path and thus base libstdc+ is picked over the correct one. Since you can not reproduce this in clean environment I wonder where that -L/usr/lib comes from. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade 2.4.4
On Tue, Jul 01, 2008 at 06:24:48PM +0400, Sergey Matveychuk wrote: Hi. After a long time when a new employment and real life(c) having eaten all my time, a new version of portupgrade was released. The modifying _all_ packages +CONTENTS bug still present in this version (as in stable too): --- Updating dependency info --- Modifying /var/db/pkg/GeoIP-1.4.4/+CONTENTS --- Modifying /var/db/pkg/xxkb-1.11/+CONTENTS --- Modifying /var/db/pkg/zidrav-1.2.0/+CONTENTS --- Modifying /var/db/pkg/zip-2.32/+CONTENTS -- http://ache.pp.ru/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade 2.4.4
On Thu, Jul 03, 2008 at 11:15:47PM +0400, Andrey Chernov wrote: On Tue, Jul 01, 2008 at 06:24:48PM +0400, Sergey Matveychuk wrote: Hi. After a long time when a new employment and real life(c) having eaten all my time, a new version of portupgrade was released. The modifying _all_ packages +CONTENTS bug still present in this version (as in stable too): --- Updating dependency info --- Modifying /var/db/pkg/GeoIP-1.4.4/+CONTENTS --- Modifying /var/db/pkg/xxkb-1.11/+CONTENTS --- Modifying /var/db/pkg/zidrav-1.2.0/+CONTENTS --- Modifying /var/db/pkg/zip-2.32/+CONTENTS Additional note: modification of /var/db/pkg/*/+CONTENTS (or any non-trivial subset of it) is quite dangerous. Once, I had a machine paniced during portupgrade doing the pass of +CONTENTS files, and due to SU, lost almost all of them. It would be helpful if +CONTENTS file were backed up (e.g., moved to +CONTENTS.bak) instead of removed and created. pgp0IxhqiAII4.pgp Description: PGP signature
Re: Idea for next portupgrade
Robert Huff wrote: Sergey Matveychuk writes: If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. It is also my understanding that ruby (used to manage the ports database) a) is not re-entrant and/or b) does not lock the files it is using/changing. Having two instances running at once causes Bad Things(tm) to happen. Robert Huff Correct, this is on the Project Ideas page ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade 2.4.4
Andrey Chernov wrote: On Tue, Jul 01, 2008 at 06:24:48PM +0400, Sergey Matveychuk wrote: Hi. After a long time when a new employment and real life(c) having eaten all my time, a new version of portupgrade was released. The modifying _all_ packages +CONTENTS bug still present in this version (as in stable too): --- Updating dependency info --- Modifying /var/db/pkg/GeoIP-1.4.4/+CONTENTS --- Modifying /var/db/pkg/xxkb-1.11/+CONTENTS --- Modifying /var/db/pkg/zidrav-1.2.0/+CONTENTS --- Modifying /var/db/pkg/zip-2.32/+CONTENTS Yes, I know. It's only issue, I couldn't find in limit time. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade 2.4.4
Kostik Belousov пишет: On Thu, Jul 03, 2008 at 11:15:47PM +0400, Andrey Chernov wrote: On Tue, Jul 01, 2008 at 06:24:48PM +0400, Sergey Matveychuk wrote: Hi. After a long time when a new employment and real life(c) having eaten all my time, a new version of portupgrade was released. The modifying _all_ packages +CONTENTS bug still present in this version (as in stable too): --- Updating dependency info --- Modifying /var/db/pkg/GeoIP-1.4.4/+CONTENTS --- Modifying /var/db/pkg/xxkb-1.11/+CONTENTS --- Modifying /var/db/pkg/zidrav-1.2.0/+CONTENTS --- Modifying /var/db/pkg/zip-2.32/+CONTENTS Additional note: modification of /var/db/pkg/*/+CONTENTS (or any non-trivial subset of it) is quite dangerous. Once, I had a machine paniced during portupgrade doing the pass of +CONTENTS files, and due to SU, lost almost all of them. It would be helpful if +CONTENTS file were backed up (e.g., moved to +CONTENTS.bak) instead of removed and created. portupgrade copy a work file in temp one, and move back with changes. I'm not sure /var/db/pkg/*/ is a good place for backups. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea for next portupgrade
On Thu, 3 Jul 2008 09:57:00 -0400 Robert Huff [EMAIL PROTECTED] wrote: Sergey Matveychuk writes: If portupgrade can calculate the depency and launch many ports build in same time for non-depending ports it's can be wonderful. I'm sure it's a good idea. I'd use it too. But I have a very little free time with my current employment. So I can't implement it. Sorry. It is also my understanding that ruby (used to manage the ports database) a) is not re-entrant and/or b) does not lock the files it is using/changing. Having two instances running at once causes Bad Things(tm) to happen. Presumably most of the work can be done in parallel with the critical stages serialised. There's already a build tool that builds several ports in parallel, I presume that's how it works. I can't remember what it's called offhand. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: avahi-gtk
On Wed, 2008-07-02 at 15:57 -0400, Chuck Robey wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having problems building this, it dpoesn't see it's own defintion for symbol avahi_init_i18n (it's defined it it's own code but I guess not linked in). I went and googled it, it's apparently been spotted as a problem with all avahi-gtk versions at 6.22.2 and earlier, and it seems that our port is at 6.22.1. it was fixed for sure in .4. Myu problem is, I can't for the life of me see where the damn minor version is set. All i can see is, it's set to 6.22, and no hint of a trailing .1. So, either, if anyone knows what the fix is, OR if anyone knows where the minor is being set, I'd be happy enough. You know, just as an aside, one of my problems with today's ports are the huge reliance on sub-makefiles. It nearly always makes things more difficult to trace out errors. Yes, it's more elegant, but I just don't believe that selling out for elegance is a good idea; I would rather have it easier to see and fix, that just seems so obvious to me. Don't get me wrong, I very much like things like bsd.port.mk, it's things like hiding the names, version numbers, things like that about the ports that I dislike, like the bsd.gnome.mk, and all the masterdirs. I just personally don't see the gain it making references unobvious. It isn't in any of the sub-makefiles. Port net/avahi-gtk is a slave of net/avahi-app (according to MASTERDIR). Your answer is in net/avahi-app/Makefile. BTW, avahi (and slaves) is versioned 0.6.22, not 6.22. You want to change it to 0.6.22.4 I guess... -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhr3aoACgkQz62J6PPcoOnT+wCgnMNr2jxKd3TVfsdAJnTWsDCO 1G8Anivr6mIL0xX4brtR5PkwBAv/q0dy =wrL7 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Coleman Kane signature.asc Description: This is a digitally signed message part
RE: cfengine fatal error
Hi Sergei, When running cfengine 2.2.7 (and before that 2.2.3) (in a jail) on my FreeBSD 6.3 box the cfservd crashes after client connect. Sys version FreeBSD cfengine.debank.tv 6.3-STABLE FreeBSD 6.3-STABLE #0: Wed Jun 4 05:22:14 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ FLAPPIE amd64 Last piece of cfservd -d1 output: LastSeen(cvs.debank.tv) reg IPV4 address sockaddr_ntop(192.168.1.33) Found address (192.168.1.33) for host cvs.debank.tv GetMacroValue(server,LastSeenExpireAfter) GetMacroValue(server,LastSeenExpireAfter): using scope 'server' for variable 'LastSeenExpireAfter' READ -192.168.1.33 WriteDB = -192.168.1.33 WriteDB = Thu:Hr02:Min10_15 Transmission empty or timed out... Transaction Receive [][] RecvSocketStream(0) cfservd terminating NULL transmission! Terminating thread... ***Closing socket 5 from 192.168.1.26 Fatal error 'kse_exit() failed for system scope thread' at line 1215 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) [EMAIL PROTECTED]:~#ldd `which cfservd` /usr/local/sbin/cfservd: libdb-4.6.so.0 = /usr/local/lib/libdb-4.6.so.0 (0x8006bd000) libpthread.so.2 = /usr/lib/libpthread.so.2 (0x8008ef000) libcrypto.so.4 = /lib/libcrypto.so.4 (0x800a1a000) libm.so.4 = /lib/libm.so.4 (0x800c61000) libc.so.6 = /lib/libc.so.6 (0x800d7d000) libpthread.so.2 = /lib/libpthread.so.2 (0x800f8f000) It looks like a threading error but I can't seem to figure out what exactly goes wrong ( a ktrace doesn't reveal anything), any ideas on this or what debugging do I need to provide to make it more clear. Thanks, Rob Evers P.S. please cc me as I'm not on ports@ -Original Message- From: Jo Rhett [mailto:[EMAIL PROTECTED] Sent: Friday, 4 July 2008 4:50 AM To: EVERS ROB Cc: [EMAIL PROTECTED] Subject: Re: cfengine fatal error Well it works fine outside of a jail. Are you using the ldd command inside the jail, or outside of it? You need to make sure all of those libraries are available inside the jail... Jo, Thank you for your response, The ldd is performed inside of the jail, the jail is a full or fat jail managed with ezjail so I have a complete copy of the base system available. Rob Evers smime.p7s Description: S/MIME cryptographic signature
Re: gnash-0.8.3: build fails on 6.3
* Andriy Gapon ([EMAIL PROTECTED]) wrote: A s we can see -L/usr/lib comes before gcc-4.2.4 path and thus base libstdc+ is picked over the correct one. Since you can not reproduce this in clean environment I wonder where that -L/usr/lib comes from. Seems like you're right, I don't have -L/usr/lib in gcc args when building gnash. Could you please send me conf* files from the workdir (config.log etc.) and all Makefile* files (Makefile, Makefile.in from all subdirs). -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D [EMAIL PROTECTED] ..: jabber: [EMAIL PROTECTED]http://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: mpd-5.1_1 - patch proposal
Hello, I've created a patch for MPD adding a new feature. Could you please review it and, possibly, include it in the mpd or the ports tree, or at least like a port option? The details for the patch are here : http://sourceforge.net/tracker/index.php?func=detailatid=314145aid=2010154group_id=14145 Looking forward to hearing from you! Kind regards, Doichin Dokov NetOne - Silistra Bulgaria ___ 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: quagga-0.99.9_7
Hi Boris,
I am sorry for my late answer. I was on holidays.
I remember Makefile has ENABLE_VTY_GROUP knob, so You may use it. Is it what
You need?
egrep ENABLE_VTY_GROUP /usr/ports/net/quagga/Makefile
.if defined(ENABLE_VTY_GROUP)
CONFIGURE_ARGS+=--enable-vty-group=${ENABLE_VTY_GROUP}
@${ECHO} ENABLE_VTY_GROUP Specify group for vty socket ownership
But it seems it is not enabled, isn´t it ?
I'm not sure if this is it, but I would like to behave the quagga in Debian
(Linux) and FreeBSD consistently.
In contrast, FreeBSD, Linux also has a file named quagga in the directory
/etc/pam.d/.
This file is not in FreeBSD in directory /usr/local/etc/pam.d or /etc/pam.d,
which I would in the case of second option even understand.
Perhaps to FreeBSD is not needed, but then what exactly in the table the
options of quagga when compiling means the possibility of PAM PAM
authentication for vtysh ?
However, the aim is this:
I have an user XXX and I want him to give sufficient privileges to manipulate
the quagga. I do not want to give him permission through sudo or through su
commands. In addition, I want in order to when in the vtysh.conf file, the user
XXX is set with the possibility of nopassword, vtysh not ask me for a password
to the quagga.
Sh interpreter is preset to FreeBSD systems, so that the goal is for these
above-mentioned conditions, to run vtysh straight and asks for nothing.
So far, only what the user see the error message:
Vtysh
Exiting: failed to connect to any daemons.
I do not know how to do, to ask me, but the goal is identical behavior quagga
on FreeBSD to Linux systems and that´s all, not more and not less.
Thank you.
Regards,
Daniel
-Original Message-
From: Boris Kovalenko [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 5:45 AM
To: [EMAIL PROTECTED]
Subject: Re: FreeBSD Port: quagga-0.99.9_7
Hello, Daniel!
I remember Makefile has ENABLE_VTY_GROUP knob, so You may use it. Is it what
You need?
Hi Boris,
I would like to turn your attention on one little bug in quagga on
FreeBSD.
Why don´t we user groupname quaggavty from the beginning when the
quagga had been ported to FreeBSD ?
What do I mena ? I will show you the diffrence between quagga on
Debian and on our FreeBSD.
They use group quaggavty for command vtysh and they help themself with
pam.d/quagga file.
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ls -l /etc/pam.d/quagga
-rw-r--r-- 1 root root 162 2007-09-26 08:20 /etc/pam.d/quagga user$
cat /etc/pam.d/quagga # Any user may call vtysh but only those
belonging to the group quaggavty can # actually connect to the socket
and use the program.
auth sufficient pam_permit.so
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] whoami user [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ls -l /etc/quagga/vtysh.conf
-rw-rw 1 quagga quaggavty 63 2008-01-10 01:28
/etc/quagga/vtysh.conf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] cat
/etc/quagga/vtysh.conf username user nopassword username root
nopassword log syslog [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] egrep
quaggavty /etc/group quaggavty:x:106:user [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] vtysh Hello, this is Quagga (version 0.99.5).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
server# exit
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
So here it works, now FreeBSD:
whoami
resu
ls -l /etc/pam.d/quagga
ls: /etc/pam.d/quagga: No such file or directory
ls -l /usr/local/etc/pam.d/quagga
ls: /usr/local/etc/pam.d/quagga: No such file or directory
ls -l /usr/local/etc/quagga/vtysh.conf
-rw-rw-r-- 1 quagga quagga 129 10 led 01:52
/usr/local/etc/quagga/vtysh.conf
cat /usr/local/etc/quagga/vtysh.conf
username resu nopassword
username root nopassword
log syslog
pw group show quagga
quagga:*:101:resu
vtysh
Exiting: failed to connect to any daemons.
Is possible to repair it ? How can I assit you ?
It would be good if new version 0.99.10 will count with vtysh like on
Debian.
Thank you.
Bye.
Daniel
Regards,
Boris
___
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: quagga-0.99.9_7
Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) Hi Boris, The problem I haven´t solved since February, when I met with him again by chance in July when dealing with another problem, a new multicast api in FreeBSD 7. I will write another report the following e-mail on multicast. I found out that this strange number [: 34978: unexpected operator is not at all a number of lines of code, but it is PID! It is a PID of daemon, which was running, but for some reason has been terminated, for example by signal 11 and an integral condition is that in /var/run/ quagga is the rest of the daemon, the pid file is opened. So when a user runs /usr/local/etc/rc.d/quagga start|stop|restart so it just appears these nonsenses on some unexpected operators. I can not repeat it because I do not know how to simulate freezing process expediently. But I am sure that this is PID number, because in the list of running processes ps aux were two processes ospfd and one of them had the same number like the number in error message. When I was killed the process with the number from error message and restarted quagga, the error message suddenly disappeared, it would lead to think that, between February to July the error unexpected end of the process become, and that I am, of course, it could not even see, and finally that it is rare phenomenon. Respect, Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... Thanks. Bye. Daniel Respect, Boris ___ 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: quagga-0.99.9_7
Hi Boris again, :) I would like to thank you retrospectively to that my proposal is realised, and if this view has ceased to function, so I have to respond. I am afraid that in the last two committed changes in quagga, the error occurred. I have three systems, where I have installed three different versions to the latest display completely ceased to function. SYSTEM1: system1# pkg_info | grep quagga quagga-0.99.9_7 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system1# /etc2/rc.d/quagga status quagga is running as pid 1116. quagga is running as pid 1122. quagga is running as pid 1128. Sleeping 10 seconds to obtain dynamic routing information... system1# It is old style. SYSTEM2: system2# pkg_info | grep quagga quagga-0.99.10 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system2# /etc2/rc.d/quagga status zebra is running as pid 1517. ospfd is running as pid 1523. ospf6d is running as pid 1529. bgpd is running as pid 1535. Sleeping 10 seconds to obtain dynamic routing information... system2# It is new style. SYSTEM3: system3# pkg_info | grep quagga quagga-0.99.10_2Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system3# /etc2/rc.d/quagga status Sleeping 10 seconds to obtain dynamic routing information... system3# It is new broken style. :D Respect, Daniel -Original Message- From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 11:43 AM To: 'Boris Kovalenko' Cc: '[EMAIL PROTECTED]' Subject: RE: FreeBSD Port: quagga-0.99.9_7 Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, Question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ 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: samba-3.0.30,1
On Thu, Jul 3, 2008 at 5:03 AM, Dmitry [EMAIL PROTECTED] wrote: Hello. What about samba 3.2.0? Later, possibly after 3.2.1 - too many problems with it. Cheers, Timur, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
