15 minutes qui vont changer le futur de votre business - ports de openbsd.org
Content-Transfer-Encoding: 8bit Bonjour, 15 minutes, c'est le temps necessaire a la mise en place de votre prospection automatisee par e-mail : c'est rapide, c'est gratuit et c'est d'une efficacite redoutable. EWI est tres fiere de vous presenter son nouveau PACK PROSPECT : Le Pack Prospect est un logiciel de prospection commerciale par email qui recherche les adresses email de vos clients et leur envoie votre publicite. C'est facile. Il suffit de choisir les mots-cles correspondant votre cible : le pack prospect va creer votre liste de prospection. C'est rapide Moins de 15 minutes apres avoir cree votre publicite, vos premiers clients commencent a la recevoir. C'est gratuit Apres avoir achete le pack prospect, la prospection par email ne coute rien. C'est efficace Grace au ciblage de vos clients par mots-cles, vous touchez rapidement des internautes dont vous etes certain qu'ils s'intressent vos produits. Decouvrez les avantages d'utiliser le pack prospect et les methodes qui vont vous permettre de trouver de nouveaux clients en moins de 15 minutes sur : www.packprospect.com Toute l'equipe du Pack prospect Ps : Pour vous desabonner de cette newsletter http://www.bullesdozer.com/fr/packprospect/newsletter.php?destinataire=ports%40openbsd.org&radio=NON Cet email est sans accentuation pour des raisons de compatilite avec votre client de messagerie
Re: OpenNX
I've no idea but, # gdb -core opennx.core GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-openbsd4.4". Core was generated by `opennx'. Program terminated with signal 11, Segmentation fault. #0 0x1c01c25f in ?? () ¿Any clues? When I try to establish de NX connection I don't see any rare at tcp/ip level sniffing with tcpdump(1). The auth process go well; the app hangs up when it tries to initialize the session: "OpenNX session startup failed" -- Thanks, Jordi Espasa Clofent
Re: potentially unsafe operations
On 2008/10/17 01:58, frantisek holop wrote: > i am just doing a full upgrade, and these messages are > somewhat annoying esp because they interrupt the > upgrade session and i think they could be supressed > in well defined cases. imho, having the messages for the common cases (updating icons/desktop db/xml) is slightly dangerous, because it makes people run -Fupdate all the time, so they end up not seeing the messages which _are_ important. > what about a function for pkg_add to suppress > @exec warnings for a list of external programs > commonly called by ports? > what do you think? > > i can try and make a patch, but it will take > some time, i am boarding a ship from japan > to vladivostok in a couple of hours :] seems like a good idea..
Re: OpenNX
On 2008/10/17 10:44, Jordi Espasa Clofent wrote: > I've no idea but, > > # gdb -core opennx.core > > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-openbsd4.4". > Core was generated by `opennx'. > Program terminated with signal 11, Segmentation fault. > #0 0x1c01c25f in ?? () > > ¿Any clues? no clues from this; try cleaning the build directory and $ make DEBUG="-O0 -g" INSTALL_STRIP="" repackage reinstall then hopefully gdb will give you more information.
Upgrading port - choosing new version.
I am trying something new with a new 4.4 (CDs arrived!) setup and I have a puzzle. I have a build-machine and I did an install of all the sets (bar games) plus the ports tree. I did "make package" for a small port I use that never gets onto the issue CD. Sweet. I then populated /usr/ports/packages/i386/all with the packages supplied on the CD and proceeded to build packages for the ports I use that I cannot (yet) get packages for by ftp. All very straightforward. So far. I have a machine that was loaded with 4.3 and a bunch of stuff from packages and I decided to test the upgrade process on it. The OS upgrade went well. sysmergeis great. I pointed PKG_PATH at my build machine and proceeded to do an upgrade using: pkg_add -ui -F update -F updatedepends and nearly everything went OK. I had postfix (stable, no flavors) from 4.3 on there and I had built a snapshot version from ports for 4.4. and the pkg_add said it could not find an update for postfix. When I built the 4.4 postfix stable version it updated but I really expected that it would have offered me the snapshot version that was there all along. Is there no way to choose between the two? What criteria are in play in such a case? Rod/ ** please: CC is unnecessary, I'm subscribed. Replies to the sender address (except from the list server are tarpitted. The reply-to: works but should not be needed. Thanx.*** Rod/ >From the land "down under": Australia. Do we look from up over?
Re: OpenNX
no clues from this; try cleaning the build directory and $ make DEBUG="-O0 -g" INSTALL_STRIP="" repackage reinstall then hopefully gdb will give you more information. I've done it. The nasty thing is now the OpenNX stills not working and, moreover, I can get any core dump about. I've discovered: * the OpenNX hang seems to do a completely freeze system (I've never seen an OpenBSD completly hang up!) when I you try it in GNOME environment. This very odd behavior doesn't happen in XFCE4 environment. * if I try "Available ares" as Dispaly, OpenNX hangs up and shows to you the startup failed message. But if I try, for example, "800x600", it doesn't show the error message and client hangs up in its graphical scroll progress. ¿?¿ -- Thanks, Jordi Espasa Clofent
Re: OpenNX
On 2008/10/17 13:29, Jordi Espasa Clofent wrote: >> no clues from this; try cleaning the build directory and >> >> $ make DEBUG="-O0 -g" INSTALL_STRIP="" repackage reinstall >> >> then hopefully gdb will give you more information. > > I've done it. The nasty thing is now the OpenNX stills not working > and, moreover, I can get any core dump about. try running "gdb opennx" (if you need any command line options then do "set args ") and "run" at the gdb prompt. > * the OpenNX hang seems to do a completely freeze system (I've never > seen an OpenBSD completly hang up!) when I you try it in GNOME > environment. This very odd behavior doesn't happen in XFCE4 > environment. it may be panicking (you wouldn't see this if X has control of the screen unless you have serial console).
Re: [syslog-ng] UPDATE: sysutils/syslog-ng
Brian, Steven, Jakob,
I just wanted to tell you how much I appreciate your work on OpenBSD
ports of syslog-ng.
Just tell me if you need assistance on my part, information,
communication or anything.
Brian already was nice enough to convince me to publish my internal git
repository :)
On Thu, 2008-10-16 at 11:59 -0400, Brian A. Seklecki wrote:
> Damnit!
>
> I've been waiting for my 4.4 CDs since July/August and you beat me to
> the update by 8 days. :)
>
> I did mine as a new port, based on the old one, as some people may want
> to run the 1.6.x bitrot version.
>
> http://people.collaborativefusion.com/~seklecki/openbsd44_port_syslog-ng209_eventlog027.tar
>
> # syslog-ng -V
> syslog-ng 2.0.9
>
> # uname -a
> OpenBSD cauldron-obsd-44stable-i386 4.4 GENERIC.MP#844 i386
>
> Lets get this bad boy tested and updated before 4.5 is released!
>
> ~BAS
>
>
> # tar cvf openbsd44_port_syslogng209_etlog027.tar eventlog/ syslog-ng2/
> eventlog
> eventlog/Makefile
> eventlog/distinfo
> eventlog/pkg
> eventlog/pkg/DESCR
> eventlog/pkg/PLIST
> eventlog/pkg/PFRAG.shared
> syslog-ng2
> syslog-ng2/CVS
> syslog-ng2/CVS/Repository
> syslog-ng2/CVS/Entries
> syslog-ng2/CVS/Tag
> syslog-ng2/pkg
> syslog-ng2/pkg/CVS
> syslog-ng2/pkg/CVS/Repository
> syslog-ng2/pkg/CVS/Entries
> syslog-ng2/pkg/CVS/Tag
> syslog-ng2/pkg/DESCR
> syslog-ng2/pkg/PLIST
> syslog-ng2/pkg/PLIST.orig
> syslog-ng2/pkg/MESSAGE
> syslog-ng2/Makefile
> syslog-ng2/distinfo
> syslog-ng2/files
> syslog-ng2/files/syslog-ng.conf
> syslog-ng2/patches
> syslog-ng2/patches/patch-tests_loggen_loggen_c
>
> # tar tzvf /usr/ports/packages/i386/all/syslog-ng-2.0.9.tgz
> -r--r--r-- 1 root wheel 721 Oct 16 11:46 +CONTENTS
> -r--r--r-- 1 root wheel 568 Oct 16 11:46 +DESC
> -r--r--r-- 1 root wheel 216 Oct 16 11:46 +DISPLAY
> -r--r--r-- 1 root bin 5899 Oct 16 11:46 man/man5/syslog-ng.conf.5
> -r--r--r-- 1 root bin 3268 Oct 16 11:46 man/man8/syslog-ng.8
> -r-xr-xr-x 1 root bin1277148 Oct 16 11:46 sbin/syslog-ng
> -r--r--r-- 1 root bin 8837 Oct 16 11:46 share/examples/syslog-ng.conf
> -r-xr-xr-x 1 root bin 10948 Oct 16 11:46 bin/loggen
>
> # make install
> ===> Verifying specs: glib-2.0 c glib-2.0
> ===> found glib-2.0.1600.2 c.48.0
> ===> Installing syslog-ng-2.0.9 from /usr/ports/packages/i386/all/
> syslog-ng-2.0.9: complete
> --- syslog-ng-2.0.9 ---
> Add the following to rc.local(8):
>
> if [ -x /usr/local/sbin/syslog-ng -a -f /etc/syslog-ng.conf ]; then
> /usr/local/sbin/syslog-ng
> echo "syslog-ng2"
> fi
>
> Thanks for shopping balabit.hu and company.
>
>
>
> On Wed, 2008-10-08 at 21:34 +0200, Steven Mestdagh wrote:
> > this requires the new sysutils/eventlog port sent earlier.
> >
> > please test/comment/ok.
> >
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/sysutils/syslog-ng/Makefile,v
> > retrieving revision 1.8
> > diff -u -r1.8 Makefile
> > --- Makefile6 Oct 2008 16:09:13 - 1.8
> > +++ Makefile8 Oct 2008 19:29:28 -
> > @@ -2,50 +2,39 @@
> >
> > COMMENT= syslogd replacement
> >
> > +DISTNAME= syslog-ng-2.1.1
> > CATEGORIES=sysutils
> >
> > -DISTNAME= syslog-ng-1.6.8
> > -LIBOL= libol-0.3.16
> > +MAINTAINER=Steven Mestdagh <[EMAIL PROTECTED]>
> >
> > -MAINTAINER=Jakob Schlyter <[EMAIL PROTECTED]>
> > +HOMEPAGE = http://www.balabit.com/network-security/syslog-ng/
> >
> > -MASTER_SITE_SYSLOGNG=\
> > - http://www.balabit.com/downloads/files/syslog-ng/sources/
> > +# GPL v2
> > +PERMIT_PACKAGE_CDROM = Yes
> > +PERMIT_PACKAGE_FTP = Yes
> > +PERMIT_DISTFILES_CDROM = Yes
> > +PERMIT_DISTFILES_FTP = Yes
> >
> > -MASTER_SITES= ${MASTER_SITE_SYSLOGNG:=1.6/src/}
> > -MASTER_SITES0= ${MASTER_SITE_SYSLOGNG:=libol/0.3/}
> > +MASTER_SITES =
> > http://www.balabit.com/downloads/files/syslog-ng/sources/2.1/src/
> >
> > -HOMEPAGE= http://www.balabit.com/products/syslog_ng/
> > +WANTLIB = c iconv intl wrap
> >
> > -DISTFILES= ${DISTNAME}.tar.gz \
> > - ${LIBOL}.tar.gz:0
> > +LIB_DEPENDS = glib-2.0::devel/glib2 \
> > + evtlog::sysutils/eventlog
> >
> > -# GPL
> > -PERMIT_PACKAGE_CDROM= Yes
> > -PERMIT_PACKAGE_FTP=Yes
> > -PERMIT_DISTFILES_CDROM=Yes
> > -PERMIT_DISTFILES_FTP= Yes
> > -WANTLIB= c
> > +CONFIGURE_STYLE = gnu
> > +CONFIGURE_ARGS += --enable-tcp-wrapper
> >
> > -CONFIGURE_STYLE= gnu
> > -CONFIGURE_ARGS+= --with-libol=${WRKDIR}/${LIBOL} \
> > - --enable-tcp-wrapper
> > +DOC = ${PREFIX}/share/doc/syslog-ng/
> > +EXAMPLES = ${PREFIX}/share/examples/syslog-ng/
> >
> > -DOC= ${PREFIX}/share/doc/syslog-ng
> > -EXAMPLES= ${PREFIX}/share/examples/syslog-ng
> > -
> > -pre-configure:
> > - cp -f ${PORTSDIR}/infrast
Re: OpenNX
try running "gdb opennx" (if you need any command line options then do "set args ") and "run" at the gdb prompt. [EMAIL PROTECTED] [~] [15:25:03] $ gdb opennx GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-openbsd4.4"... (gdb) run Starting program: /usr/local/bin/opennx [New process 19493] [New process 19493, thread 0x8bae6c00] In first attempt, the OpenNX shows an "Exit 1" In second attempt, the program simply hangs up with its progress bar stopped in "Starting session" point. Anything happens until I force the termination of app using a ^C keystroke. As my initial message shows (I've post my dmesg) maybe it's a --current related problem, not OpenNX problem itself. -- Thanks, Jordi Espasa Clofent
Re: Upgrading port - choosing new version.
On Friday 17 October 2008, Rod Whitworth wrote: > I had postfix (stable, no flavors) from 4.3 on there and I had built > a snapshot version from ports for 4.4. and the pkg_add said it could > not find an update for postfix. > > When I built the 4.4 postfix stable version it updated but I really > expected that it would have offered me the snapshot version that was > there all along. > > Is there no way to choose between the two? What criteria are in play > in such a case? Hi Rod, Your use of the terms "stable" and "snapshot" above are not particularly clear, or more likely, I'm just reading it wrong. Both the -STABLE and -RELEASE trees will not officially exist (publicly) until the date of the release (Nov 1). What you have on the CD's is of course, the -RELEASE tree. Mixing things from one "snapshot" of the many provided during the development cycle (i.e. the continual builds of the -CURRENT tree) with the RELEASE (as provided on the official CD) is not a good idea. If any last minute bug fixes to the ports/packages systems were committed prior to RELEASE, they could potentially break any of the previously built "snapshot" packages. Attempting to install packages created with an older version of the ports/packages system on a newer OS version can make a mess of the system. Equally, attempting to install packages created with a newer version of the ports/packages system on an older OS version can also cause a real mess. Though I've got my "Shinny shinny shinny" new 4.4 disks sitting right here, I haven't gotten to installing it yet. --Possibly the new ports/packages system in 4.4 now intentionally prevents the first way of making a real mess? As for the second way of making a real mess... Some idiot fumble fingered a cvs update on a newly installed box, and attempted to build/install -CURRENT ports/packages, on a box running 4.3 -RELEASE. The result was the ports/packages "mysteriously" installed incorrectly and stuffed up the packages database. Said idiot did not even realize his mistake, and went so far as to file a bug report about the incorrect installation locations. (sigh) The idiot who filed the ports/5837 bug was me. Even if the developers did idiot-proof the first way of making a real mess by preventing the installation of old packages on a newer OS, there's always an improved idiot out there who will find a way to totally screw things up. Kind Regards, JCR
Re: update: editors/vim 7.1.315 -> 7.2.25
On Thu, Oct 16, 2008 at 09:54:19PM -0700, Chris Kuethe wrote: > two happy vim users already, but i'd like to see some more test coverage I see a problem with the no_x11 flavor: ===> Building package for vim-7.2.25-no_x11 Create /usr/ports/packages/amd64/all/vim-7.2.25-no_x11.tgz Error in package: /usr/ports/mystuff/editors/vim/w-vim-7.2.25-no_x11/fake-amd64-no_x11//usr/local/bin/gvimtutor does not exist gvimtutor shouldn't really be in the no_x11 package, I guess. -- simon
Re: UPDATE: graphics/gimp
On Fri, Oct 03, 2008 at 10:58:07AM +0200, Giovanni Bechis wrote: > Update to latest version, gegl-0.18 is needed to build it and gimp-2.4 > needs to be uninstalled. I think you forgot to add gegl-0.0::grahpics/gegel to LIB_DEPENDS and babl-0.0 to WANTLIB. At least that's what the allmighty tools are telling me on i386. (no reason to send another diff, I'm already building it with the necessary changes on arm and powerpc) Ciao, Kili
Re: Upgrading port - choosing new version.
On Fri, 17 Oct 2008 07:21:26 -0700, J.C. Roberts wrote: >Your use of the terms "stable" and "snapshot" above are not particularly >clear, or more likely, I'm just reading it wrong. > The postfix port has stable and snapshot versions to choose from. I'm building on 4.4 release using 4.4 release ports tree and trying to get a 4.3 release box with postfix to update to 4.4 (that worked well) and to the snapshot version of postfix that comes with the 4.4 ports tree. Eventually I built the stable postfix for 4.4 and the (was)4.3 (now) 4.4 machine saw the postfix-stable as an update option and took it. The puzzle is: How do I get the update to Postfix-snapshot (for 4.4) to apply? Nice hearing from you again! Rod. ** please: CC is unnecessary, I'm subscribed. Replies to the sender address (except from the list server are tarpitted. The reply-to: works but should not be needed. Thanx.***
Re: Upgrading port - choosing new version.
On Sat, Oct 18, 2008 at 07:48:09AM +1100, Rod Whitworth wrote:
> The postfix port has stable and snapshot versions to choose from.
>
> I'm building on 4.4 release using 4.4 release ports tree and trying to
> get a 4.3 release box with postfix to update to 4.4 (that worked well)
> and to the snapshot version of postfix that comes with the 4.4 ports
> tree.
>
> Eventually I built the stable postfix for 4.4 and the (was)4.3 (now)
> 4.4 machine saw the postfix-stable as an update option and took it.
>
> The puzzle is: How do I get the update to Postfix-snapshot (for 4.4) to
> apply?
You've to run pkg_add -r manually. pkg_add -u looks at the subdir
comment and possible @pkgpath markers, it doesn't recognize any
relationship between mail/postfix/{stable,snapshot}.
Ciao,
Kili
Re: Upgrading port - choosing new version.
On Fri, 17 Oct 2008 23:01:56 +0200, Matthias Kilian wrote:
>On Sat, Oct 18, 2008 at 07:48:09AM +1100, Rod Whitworth wrote:
>> The postfix port has stable and snapshot versions to choose from.
>>
>> I'm building on 4.4 release using 4.4 release ports tree and trying to
>> get a 4.3 release box with postfix to update to 4.4 (that worked well)
>> and to the snapshot version of postfix that comes with the 4.4 ports
>> tree.
>>
>> Eventually I built the stable postfix for 4.4 and the (was)4.3 (now)
>> 4.4 machine saw the postfix-stable as an update option and took it.
>>
>> The puzzle is: How do I get the update to Postfix-snapshot (for 4.4) to
>> apply?
>
>You've to run pkg_add -r manually. pkg_add -u looks at the subdir
>comment and possible @pkgpath markers, it doesn't recognize any
>relationship between mail/postfix/{stable,snapshot}.
>
That works like a charm! The best part of your message though was the
explanation of the mechanism that caused the "problem". That never was
obvious in my manpage scanning or other search attempts.
We live to learn.
Thanks heaps Kili.
Rod/
Rod/
>From the land "down under": Australia.
Do we look from up over?
dillo2 + fltk2
Attached are two new ports, one fro dillo2 and the other for fltk2. They were put together rather quickly today, so any suggestions are always welcome. Tested on i386 and amd64. -- James Turner BSD Group Consulting http://www.bsdgroup.org dillo2.tar Description: Unix tar archive fltk2.tar Description: Unix tar archive
