Re: HEADS UP: ports/ and 10.0-CURRENT
Kevin Oberman writes: > On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote: > >> With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be >> expected, ports/ is going to be essentially unusable for a while. >> >> The issue stems from configure scripts (to choose something completely >> at random) assuming that FreeBSD would never jump to a double-digit >> major version number, and as such, various regexps for "freebsd1*" (ie: >> FreeBSD 1.1.x) are now matching "freebsd10". [...] > > aDe, > > Could an entry to this effect be added to UPDATING (with a matching > entry when ports/ is "unbroken"). Also mention a workaround, e.g. $ export UNAME_r='9.9-BLAH' ___ 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: HEADS UP: ports/ and 10.0-CURRENT
> It just means that folks didn't plan ahead and didn't think up > proper contingency plans. First off, apologies to Garrett, I'm not picking on you directly, but I kinda knew this would come up. The undeniable fact is that configure scripts in general have chosen to do things a certain way. Unfortunately for us (us being FreeBSD), we have now broken these conceptions by moving to a dual-digit major release. Emails have been passed around (somewhere starting around the 7.x series when it became obvious we would be hitting 10.x a lot sooner than expected). It is no-one's fault that 23,000+ third party applications couldn't be tweaked prior to a trivial change in /sys/conf/newvers.sh that resulted in this "oops". The message I wanted to set across is that until such time as us ports folks have had a chance to really work out the damage, and start on fixing it, then for those running 10-CURRENT, things are likely to be non-linear for a while. Our primary responsibility right now is to ensure that a proper set of packages gets built for the impending 9.0-RELEASE. We haven't forgotten you bleeding edge folks, it's just that right now, you're somewhat down the food chain. Make no mistake. This move to a double-digit major version number is going to cause serious pain. We will do our best to fix, hack, slash, and whatever around it, but right now the focus is the last of our remaining single-digit releases. Until that is out the door, do not be expecting tree-wide commits to fix things. -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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 9:56 PM, Kevin Oberman wrote: > On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote: >> With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be >> expected, ports/ is going to be essentially unusable for a while. >> >> The issue stems from configure scripts (to choose something completely >> at random) assuming that FreeBSD would never jump to a double-digit >> major version number, and as such, various regexps for "freebsd1*" (ie: >> FreeBSD 1.1.x) are now matching "freebsd10". >> >> This is going to be some fairly fundamental breakage. >> >> However, until such time as 9.0-RELEASE is completely out of the door, >> with autotools hat on, I will _not_ be committing any changes to >> infrastructural ports to "fix" this. >> >> That is to say, until 9.0-R happens, and for some considerable period >> afterwards, ya'll can pretty much expect ports/ to be non-functional on >> HEAD. PRs mentioning this will be gleefully closed referencing this >> message. > > aDe, > > Could an entry to this effect be added to UPDATING (with a matching > entry when ports/ is "unbroken"). Being a pessimist, ports will never be fully unbroken unless all the thousands of autotools based ports as fixed, due to unfortunately code duplication. That being said, I think that a note in /usr/ports/UPDATING as well as /usr/src/UPDATING is a VERY good idea. > Anyone running CURRENT should be reading your message, but I'm a "belt > and suspenders" type of > guy on this sort of thing. Backing out of CURRENT and moving to > 9-STABLE can be a REAL pain that > will likely rapidly get worse as HEAD gets less and less frozen. It's not the FreeBSD dev's fault. Unfortunately the autotools folks were microoptimizing and didn't consider that the future would come sooner than it actually did. Thanks, -Garrett ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 10:15 PM, Kevin Oberman wrote: > On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote: >> It's not the FreeBSD dev's fault. Unfortunately the autotools folks >> were microoptimizing and didn't consider that the future would come >> sooner than it actually did. > > First, I'm not complaining or criticizing any of the developers and I > am very grateful to > aDe for maintaining them as I get a headache every time I start looking at > them. > > I am baffled in my attempts to parse "didn't consider that the future > would come sooner > than it actually did". Is that what you really meant, because it's > self-contradictory? Or > am I just confused. It just means that folks didn't plan ahead and didn't think up proper contingency plans. FWIW FreeBSD has developed faster in the last couple of years than most folks would have expected -- including myself -- and the release cycles reflect that change. That's more of what I was addressing in my previous reply. Corner cases are the bane of all software developers. -Garrett ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote: > It's not the FreeBSD dev's fault. Unfortunately the autotools folks > were microoptimizing and didn't consider that the future would come > sooner than it actually did. Garrett, First, I'm not complaining or criticizing any of the developers and I am very grateful to aDe for maintaining them as I get a headache every time I start looking at them. I am baffled in my attempts to parse "didn't consider that the future would come sooner than it actually did". Is that what you really meant, because it's self-contradictory? Or am I just confused. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote: > With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be > expected, ports/ is going to be essentially unusable for a while. > > The issue stems from configure scripts (to choose something completely > at random) assuming that FreeBSD would never jump to a double-digit > major version number, and as such, various regexps for "freebsd1*" (ie: > FreeBSD 1.1.x) are now matching "freebsd10". > > This is going to be some fairly fundamental breakage. > > However, until such time as 9.0-RELEASE is completely out of the door, > with autotools hat on, I will _not_ be committing any changes to > infrastructural ports to "fix" this. > > That is to say, until 9.0-R happens, and for some considerable period > afterwards, ya'll can pretty much expect ports/ to be non-functional on > HEAD. PRs mentioning this will be gleefully closed referencing this > message. aDe, Could an entry to this effect be added to UPDATING (with a matching entry when ports/ is "unbroken"). Anyone running CURRENT should be reading your message, but I'm a "belt and suspenders" type of guy on this sort of thing. Backing out of CURRENT and moving to 9-STABLE can be a REAL pain that will likely rapidly get worse as HEAD gets less and less frozen. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.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"
HEADS UP: ports/ and 10.0-CURRENT
With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be expected, ports/ is going to be essentially unusable for a while. The issue stems from configure scripts (to choose something completely at random) assuming that FreeBSD would never jump to a double-digit major version number, and as such, various regexps for "freebsd1*" (ie: FreeBSD 1.1.x) are now matching "freebsd10". This is going to be some fairly fundamental breakage. However, until such time as 9.0-RELEASE is completely out of the door, with autotools hat on, I will _not_ be committing any changes to infrastructural ports to "fix" this. That is to say, until 9.0-R happens, and for some considerable period afterwards, ya'll can pretty much expect ports/ to be non-functional on HEAD. PRs mentioning this will be gleefully closed referencing this message. -aDe Reply-To set to me. Please honor it. ___ 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: [jh...@dataix.net: security/hydra 7.0 add include path.]
On (09/26/11 22:11), Ruslan Mahmatkhanov wrote:
> Problem confirmed and solution is confirmed too. Thanks a lot.
>
> I checked other options and all is fine with them, the problem is only
> in WITH_SSH, so i think your patch is sufficient. This pr is submitted:
>
> http://bugs.freebsd.org/161039
>
> Ryan, may be you can get it, since you touched it recently. Thanks.
>
> Jason Hellenthal wrote on 26.09.2011 18:44:
> >
> > Meant to CC ports.
> >
> > - Forwarded message from Jason Hellenthal -
> >
> > Date: Mon, 26 Sep 2011 10:43:59 -0400
> > From: Jason Hellenthal
> > To: cvs-...@yandex.ru
> > Subject: security/hydra 7.0 add include path.
> >
> >
> > When building the new hydra with options WITH_SSH you need to add
> > /usr/local/include to the to -I
> >
> > This may be a temporary solution to work around line 34 of hydra.h but
> > it works.
> >
> > .if defined(WITH_SSH)
> > LIB_DEPENDS+= ssh.4:${PORTSDIR}/security/libssh
> > CFLAGS+=-I/usr/local/include
> > .endif
> >
>
>
> --
> Regards,
> Ruslan
>
> Tinderboxing kills... the drives.
A fix for this has been committed. Thanks!
-r
--
Ryan Steinmetz
PGP: EF36 D45A 5CA9 28B1 A550 18CD A43C D111 7AD7 FAF2
___
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: Shared libs problem with ports under 10-CURRENT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/26/11 11:25, Chris Rees wrote: > On 26 September 2011 11:55, Rainer Hurling > wrote: >> This morning I tried to upgrade my ports after installing the new >> 10-CURRENT (amd64). >> >> Unfortunately now I am not able to build ports using shared >> libraries like ports/libXext any more. They only build .a and .la >> files, but not .so ones. >> >> Is it possible that there is something wrong now with libtool-2.4 >> (or the linker /usr/bin/ld)? >> >> #libtool --features host: amd64-portbld-freebsd10.0 disable >> shared libraries enable static libraries >> >> >> Does anyone else observes this behaviour? I would really >> appreciate some help. >> > > Excerpt from libtool configure script: > > dgux*) archive_cmds='$LD -G -h $soname -o $lib $libobjs $deplibs > $linker_flags' hardcode_libdir_flag_spec='-L$libdir' > hardcode_shlibpath_var=no ;; > > freebsd1*) ld_shlibs=no ;; > > # FreeBSD 2.2.[012] allows us to include c++rt0.o to get C++ > constructor # support. Future versions do this automatically, but > an explicit c++rt0.o # does not break anything, and helps > significantly (at the cost of a little # extra space). > freebsd2.2*) > > I've mentioned this to an autotools member, who has offered to fix > it fairly soon :) I'm thinking this needs a full audit as well. A lot of ports hardcode knowledge about freebsd 1.x and mistakenly use 'freebsd1*' to match them, due to copy of GNU autotools code. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJOgOfKAAoJEATO+BI/yjfB2+0IALXGpsdosAqZg5qzrFXfyJcx aOX48azLOZSMcPiDU9jJfHzR2bseB0EWbeclWJ8kcC+A3tIkIwqFLiU5YB81pfi1 cy9f1ow0ZF4F/76Me2N1OtnzuexvcWRnL9EJ7Mk5TdIkWlp5uFtFP5QvIgcBDj25 ejgfSiZDO7xOHku1yvZvNYKwSc5MfGEHKeozeIGyRiSu3TUhB3f/dQ0lpbxLPXJC IaDfefeNAARHUna5Hr8gJs8rGhy6fZoTiSm4NgDz5/yEiS/4dXr7E1mufooEsgtn +7RQ0KvVycCfB/WjoxrCyIOvHWKbi5debcdS+ANBeW06su8nmuG78+dRT4l/q6w= =nBye -END PGP SIGNATURE- ___ 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: Shared libs problem with ports under 10-CURRENT
Hi Chris, On 26.09.2011 20:25 (UTC+2), Chris Rees wrote: On 26 September 2011 11:55, Rainer Hurling wrote: This morning I tried to upgrade my ports after installing the new 10-CURRENT (amd64). Unfortunately now I am not able to build ports using shared libraries like ports/libXext any more. They only build .a and .la files, but not .so ones. Is it possible that there is something wrong now with libtool-2.4 (or the linker /usr/bin/ld)? #libtool --features host: amd64-portbld-freebsd10.0 disable shared libraries enable static libraries Does anyone else observes this behaviour? I would really appreciate some help. Excerpt from libtool configure script: dgux*) archive_cmds='$LD -G -h $soname -o $lib $libobjs $deplibs $linker_flags' hardcode_libdir_flag_spec='-L$libdir' hardcode_shlibpath_var=no ;; freebsd1*) ld_shlibs=no ;; yes, this seems to be one problem. The configure script does not discriminate between FreeBSD version 1.* and 10.*. There are several places in the script, which should be corrected. After changing these and similar entries manually libtool gives #libtool --features host: amd64-portbld-freebsd10.0 enable shared libraries enable static libraries But there also must be another problem. When I try to rebuild the complete xorg-7.5.1 tree several libs where build without shared files (.so). libpng and libpython are built with shared libraries, the next port devel/pcre is built without shared libs, others follow. -r--r--r-- 1 root wheel -173312 26 Sep 22:01:13 2011 libpng.so.6 lrwxr-xr-x 1 root wheel -11 26 Sep 22:01:13 2011 libpng.so -> libpng.so.6 -r--r--r-- 1 root wheel -259088 26 Sep 22:01:13 2011 libpng.a -r-xr-xr-x 1 root wheel - 2927606 26 Sep 22:04:39 2011 libpython2.7.a -r-xr-xr-x 1 root wheel - 1708416 26 Sep 22:05:31 2011 libpython2.7.so.1 lrwxr-xr-x 1 root wheel -17 26 Sep 22:05:31 2011 libpython2.7.so -> libpython2.7.so.1 -rwxr-xr-x 1 root wheel - 904 26 Sep 22:09:08 2011 libpcreposix.la -rw-r--r-- 1 root wheel - 5350 26 Sep 22:09:08 2011 libpcreposix.a -rwxr-xr-x 1 root wheel - 898 26 Sep 22:09:08 2011 libpcrecpp.la -rw-r--r-- 1 root wheel - 59456 26 Sep 22:09:08 2011 libpcrecpp.a -rwxr-xr-x 1 root wheel - 863 26 Sep 22:09:08 2011 libpcre.la -rw-r--r-- 1 root wheel -345458 26 Sep 22:09:08 2011 libpcre.a Thanks for answering. Rainer # FreeBSD 2.2.[012] allows us to include c++rt0.o to get C++ constructor # support. Future versions do this automatically, but an explicit c++rt0.o # does not break anything, and helps significantly (at the cost of a little # extra space). freebsd2.2*) I've mentioned this to an autotools member, who has offered to fix it fairly soon :) 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: Shared libs problem with ports under 10-CURRENT
On 26 September 2011 11:55, Rainer Hurling wrote: > This morning I tried to upgrade my ports after installing the new 10-CURRENT > (amd64). > > Unfortunately now I am not able to build ports using shared libraries like > ports/libXext any more. They only build .a and .la files, but not .so ones. > > Is it possible that there is something wrong now with libtool-2.4 (or the > linker /usr/bin/ld)? > > #libtool --features > host: amd64-portbld-freebsd10.0 > disable shared libraries > enable static libraries > > > Does anyone else observes this behaviour? I would really appreciate some > help. > Excerpt from libtool configure script: dgux*) archive_cmds='$LD -G -h $soname -o $lib $libobjs $deplibs $linker_flags' hardcode_libdir_flag_spec='-L$libdir' hardcode_shlibpath_var=no ;; freebsd1*) ld_shlibs=no ;; # FreeBSD 2.2.[012] allows us to include c++rt0.o to get C++ constructor # support. Future versions do this automatically, but an explicit c++rt0.o # does not break anything, and helps significantly (at the cost of a little # extra space). freebsd2.2*) I've mentioned this to an autotools member, who has offered to fix it fairly soon :) 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: [jh...@dataix.net: security/hydra 7.0 add include path.]
Problem confirmed and solution is confirmed too. Thanks a lot.
I checked other options and all is fine with them, the problem is only
in WITH_SSH, so i think your patch is sufficient. This pr is submitted:
http://bugs.freebsd.org/161039
Ryan, may be you can get it, since you touched it recently. Thanks.
Jason Hellenthal wrote on 26.09.2011 18:44:
Meant to CC ports.
- Forwarded message from Jason Hellenthal -
Date: Mon, 26 Sep 2011 10:43:59 -0400
From: Jason Hellenthal
To: cvs-...@yandex.ru
Subject: security/hydra 7.0 add include path.
When building the new hydra with options WITH_SSH you need to add
/usr/local/include to the to -I
This may be a temporary solution to work around line 34 of hydra.h but
it works.
.if defined(WITH_SSH)
LIB_DEPENDS+= ssh.4:${PORTSDIR}/security/libssh
CFLAGS+=-I/usr/local/include
.endif
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
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: Options for emulators/wine?
On 26 September 2011 09:27, Thomas Mueller wrote: > from Michael Holmes : > >> HAL shouldn't be necessary, but you might need to manually set up >> CUPS. Winemaker is just a tool for building open-source Windows apps >> on Wine with ease. There are a few GUI tools to set up CUPS, but if I >> recall correctly, the web interface to CUPS is pretty >> self-explanatory. HP do have a nice GUI called HPLIP for utilising >> their printers on Linux (and ported to FreeBSD) available on ports as >> print/hplip, but it doesn't work with the GENERIC console config, and >> seems to be quite awkward to set up (you apparently cannot load USB >> mass storage until the printer is 'adopted' by the generic USB stack). > > I don't know what you mean by "adopted" (by the generic USB stack): seems > mystic to me. Some rather strange printers will be recognised by umass before ugen recognises them; you have to plug it in before umass is loaded or it becomes a mass storage device. > CUPS would be necessary to setup printing for BSD and Linux, but would it be > necessary when using Wine and going the MS-Windows way? I'm not sure that the Windows printer stack is included in Wine, why would you rather do that than use CUPS? The gutenprint drivers are often of a higher quality than the manufacturer's provided ones, and they install less trash. > Package message said that ulpt had to be turned off in kernel config and not > loaded as a module. > > On the older computer, I tried unsuccessfully to setup the printer last June > 29 from both NetBSD and FreeBSD, using hplip in both cases. Predominant > message was "No devices found". > > NetBSD pkgsrc had only an outdated hpijs, but pkgsrc-wip > (http://pkgsrc-wip.sourceforge.net/) had hplip. Message said also to disable > umass, but that was too harsh, and prevented recognizing USB sticks. As mentioned before, disable umass, and once the printer has been recognise reload umass. > Would Linux offer a better chance with hplip than BSD? I tried also with > Linux (Slackware 13.0), but hplip version was behind, and that failed. > > There is also the Ethernet option with the printer, but I need an Ethernet > switch or additional router for that, which I intend to order. > > First attempt to build hplip on the new computer failed due to libieee1284 > dependency being for i386 only. Subsequently I turned off that option after > finding it was for parallel-port scanners only, not USB. > CUPS almost always makes things printer-related a million times easier. Don't forget it's the main printing system in the modern Macs-- Apple manage to make it work with almost anything! 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: Retiring of databases/py-pysqlite2x
Please note that all the consumers were handled, so i submitted this pr: http://bugs.freebsd.org/161038 Thank you all for working on this. Ruslan Mahmatkhanov wrote on 30.08.2011 08:14: Baptiste Daroussin wrote on 30.08.2011 01:48: They may be safely removed after all of this guys will be committed: audio/pytone ports/160053 commited databases/py-axiom ports/160260 wen@ databases/py-sqlobject ports/160059 wen@ deskutils/gourmet ports/160165 beech@ deskutils/griffith ports/160161 unassigned devel/bzr-git ports/160069 glarkin@ games/anki ports/160055 eadler@ games/gcompris ports/160054 gnome@ multimedia/gpodder ports/160155 commited multimedia/miro ports/160070 unassigned approved security/umit ports/160072 unassigned security/zenmap ports/160071 unassigned sysutils/flyback ports/160157 commited textproc/translate-toolkit ports/160261 jpaetzel@ www/roundup ports/160220 sbz@ deskutils/conduit ports/160063 gnome@ multimedia/pyjama ports/160065 eadler@ multimedia/py-openlp ports/160285 tabthorpe@ security/hotssh ports/160066 unassigned should be ashish@ security/pwman3 ports/160288 unassigned Thank you very much for that work, I should have time soon to work on this if noone already did it. regards, Bapt eadler@ taken two of them, so i've updated the aforementioned list. Thank you. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
x11-toolkits/gtkextra2 broken
This port fails to build with: ===> gtkextra-2.1.2 Bad autotool stanza: libtool:22. *** Error code 1 Stop in /usr/ports/x11-toolkits/gtkextra2. Libtool big and scary; anyone want to have a quick look? Robert Huff ___ 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"
[jh...@dataix.net: security/hydra 7.0 add include path.]
Meant to CC ports.
- Forwarded message from Jason Hellenthal -
Date: Mon, 26 Sep 2011 10:43:59 -0400
From: Jason Hellenthal
To: cvs-...@yandex.ru
Subject: security/hydra 7.0 add include path.
When building the new hydra with options WITH_SSH you need to add
/usr/local/include to the to -I
This may be a temporary solution to work around line 34 of hydra.h but
it works.
.if defined(WITH_SSH)
LIB_DEPENDS+= ssh.4:${PORTSDIR}/security/libssh
CFLAGS+=-I/usr/local/include
.endif
- End forwarded message -
___
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: "math/fftw3" port broken
On Mon, 26 Sep 2011 08:40:06 -0400 b. f. articulated: > On 9/26/11, Stephen Montgomery-Smith wrote: > > On 09/25/2011 08:19 PM, Jerry wrote: > >> When attempting to build the "math/fftw3" port, the following error > >> message is immediately displayed and the build halted: > >> > >>Variable CFLAGS is recursive. > ... > > I am unable to reproduce this problem. Is it possible that > > something is wrong in your /etc/make.conf file? > > It only happens when the non-default option WITH_OPTIMIZED_CFLAGS is > enabled. I am fixing it now. I had to remove the config file since if I tried to run "make config" it bombed out with the error message I originally listed. However, once I did that it worked fine. If you happen to know, exactly what happened that caused this problem. It obviously worked fine before since I had previously built the port with the optimized cflags option. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: "math/fftw3" port broken
On 9/26/11, Stephen Montgomery-Smith wrote: > On 09/25/2011 08:19 PM, Jerry wrote: >> When attempting to build the "math/fftw3" port, the following error >> message is immediately displayed and the build halted: >> >> Variable CFLAGS is recursive. ... > I am unable to reproduce this problem. Is it possible that something is > wrong in your /etc/make.conf file? It only happens when the non-default option WITH_OPTIMIZED_CFLAGS is enabled. I am fixing it now. b. ___ 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: "math/fftw3" port broken
On 09/25/2011 08:19 PM, Jerry wrote: When attempting to build the "math/fftw3" port, the following error message is immediately displayed and the build halted: Variable CFLAGS is recursive. I have filed a PR against it. I am unable to reproduce this problem. Is it possible that something is wrong in your /etc/make.conf file? ___ 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: Replacing procmail with maildrop
Selon Warren Block le lun 26 sep 06:01:13 2011 : Recent discussion here about the desirability of replacing procmail finally convinced me to switch to maildrop. It turned out to be relatively painless. I took some notes that may be helpful for others considering the change: http://www.wonkity.com/~wblock/docs/html/maildrop.html Great! I was looking for someone able to convert the recipes of ports/mail/spambnc ;-) -- Th. Thomas. ___ 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"
Current problem reports assigned to po...@freebsd.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. No matches to your query ___ 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"
Current unassigned ports problem reports
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker Resp. Description
o ports/161030[maintainer update] Update of cakephp13 to version 1.3
o ports/161027Update Dradis port
o ports/161024[Maintainer-Update] sysutils/battray
o ports/161020Update unSSH port
o ports/161019audio/ario: Changed libsoup dependecny
f ports/161005graphics/geos: CLANG : for functional-style cast from
o ports/161004version update
f ports/160991net/opennx : Unexpected termination of nxssh
f ports/160988[UPDATE] devel/py-zopeInterface: update to 3.8.0
o ports/160978[MAINTAINER] devel/py-pyro: update to 4.9
o ports/160977[MAINTAINER] graphics/gimp-gmic-plugin: update to 1.5.
o ports/160974[Maintainer] www/squid31: implement SQUID_SSL_CRTD, ad
f ports/160969[patch] sysutils/zfs-snapshot-mgmt: embed ruby version
o ports/160962NEW PORT: mail/spamdb-curses Curses interface for Open
f ports/160927lang/gauche: needs upgrade
f ports/160891[UPDATE]: audio/qmpdclient Update to new release, 1.2.
f ports/160882Update to the www/fusionpbx port to 2.0.9
o ports/160881update to misc/freeswitch-scripts port
o ports/160880port upgrade for misc/freeswitch-pizzademo
o ports/160879Update to net/freeswitch-core port
o ports/160870www/mod_security port not updated
o ports/160861New port: security/racoon-tool Manage setkey and racoo
o ports/160852[maintainer] [patch] mail/milter-greylist-devel update
o ports/160851multimedia/libkate: compiler errors with gcc flag -O3
o ports/160850New Port: www/graphite-web
o ports/160849New Port: databases/py-carbon
o ports/160844[PATCH] devel/py-mercurialserver update to v1.2.0
o ports/160843portsnap3.FreeBSD.org, Snapshot appears to be more tha
f ports/160842[ERROR] cannot install ports/devel/google-perftools
o ports/160825[MAINTAINER] www/MT: Perl modules introduced when usin
o ports/160824[PATCH] net/rabbitmq-c-devel: Upgrade to changeset cbe
o ports/160823[NEW PORT] devel/pecl-amqp: AMQP API
f ports/160821audio/libmp3splt: Building WITHOUT_ID3 fails
o ports/160820maintainer update: mail/dovecot2 and dovecot2-pigeonho
o ports/160817Can not build mew port with zh_TW.Big5 as value of LC_
o ports/160805[update] lang/php52 CVE vulnerabilities fixes
o ports/160797[UPDATE] Mk/bsd.xfce.mk
o ports/160768Old Version: ports/security/openssh
f ports/160748[PATCH] www/limesurvey: Add knobs to reduce dependenci
o ports/160714[patch] misc/{py-,}xdelta3: update to 3.0.0 (stable re
f ports/160712graphics/geos: CLANG compilation error
o ports/160707Update Port: audio/libamrwb 7.0.0.4
f ports/160705[patch] net/clamz: pkg-message on how to .amz-download
o ports/160668[patch] graphics/zathura: add zathurarc.5 under NOPORT
o ports/160667[patch] audio/xmmix: fix WARNING pid 4826 (xmmix): ioc
o ports/160666[maintainer-update] p5-Sys-Filesystem default package
f ports/160654[PATCH] databases/cassandra: scripts must be world exe
f ports/160640[patch] devel/php5-blitz new version
f ports/160626[patch] www/py-rssdler: deprecate in favor of www/py-f
o ports/160606[PATCH] devel/rlog: update to 1.4
o ports/160566[new port] mail/dbmail-devel: dbmail upgraded to versi
f ports/160539[PATCH] security/botan: update to 1.10.1
f ports/160511[PATCH] make math/py-graphtool actually work
f ports/160389[patch] security/openssh-portable: fix build on 9.x
f ports/160378x11-toolkits/py-wxPython28-common: CLANG compilation f
o ports/160366New port: misc/xmonad-log-applet An applet that will d
o ports/160353[patch] update www/linux-opera to 11.51
f ports/160352net-im/pidgin-sipe has undocumented NSS dependency
o ports/160323[PATCH] japanese/p5-Mail-SpamAssassin. fix sa-update,
o ports/160319[New Port] pidgin-audacious-remote (plugin for pidgin)
o ports/160313New port:databases/pg_reorg
o ports/160308[MAINTAINER] dns/powerdns: fix loading a whole new set
o ports/160265[NEW PORT] lang/pypy 1.6
o ports/160262New port: net-mgmt/better-cacti-templates - bett
Shared libs problem with ports under 10-CURRENT
This morning I tried to upgrade my ports after installing the new 10-CURRENT (amd64). Unfortunately now I am not able to build ports using shared libraries like ports/libXext any more. They only build .a and .la files, but not .so ones. Is it possible that there is something wrong now with libtool-2.4 (or the linker /usr/bin/ld)? #libtool --features host: amd64-portbld-freebsd10.0 disable shared libraries enable static libraries Does anyone else observes this behaviour? I would really appreciate some help. Thanks in advance, Rainer Hurling ___ 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: INDEX build for 10-CURRENT
On Mon, Sep 26, 2011 at 12:01:47PM +0200, Erwin Lansing wrote: >> When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-) > Later today. Running a test run as we speak :-) What about INDEX-9, DESCRIBE.9 / INDEX-10, DESCRIBE.10 for portsnap? -- Adios ___ 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: INDEX build for 10-CURRENT
On Sep 26, 2011, at 11:32 AM, Sergey V. Dyatko wrote: > Hi Erwin, > Hi Sergey, > When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-) > Later today. Running a test run as we speak :-) Erwin ___ 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"
INDEX build for 10-CURRENT
Hi Erwin, When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-) laptop# make fetchindex -C /usr/ports/ fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2: Not Found *** Error code 1 Stop in /usr/ports. -- wbr, tiger ___ 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: Replacing procmail with maildrop
On Mon, 26 Sep 2011 04:16:01 -0500
"Matthew D. Fuller" wrote:
> On Mon, Sep 26, 2011 at 04:07:31AM -0500 I heard the voice of
> Conrad J. Sabatier, and lo! it spake thus:
> >
> > OK, I'm starting to get a little better of an idea of what to do.
> > My main concern so far has been the ability to nest a set of
> > commands within a recipe the way procmail allows.
>
> Well, it's C-like; you can put braces around the body of the if and
> have however much you want inside there.
>
>
> > I don't want to use the full list name as it appears in the List-Id
> > header, but a simpler, pared down version of it. This was fairly
> > easy to do in procmail; I just have to work out the correct syntax
> > for doing it with maildrop.
>
> What I had there
>
> > > if(/^List-ID: freebsd-([a-z]+).freebsd.org/)
> > > to FreeBSD/$MATCH1
>
> should give you (mod bugs in my top-of-my-head'ing of course) the same
> sorta result as your
>
> >> :0
> >> * ^List-Id:.*freebsd.org
> >> {
> >> ListId=`formail -c -x List-Id: | \
> >> sed -e 's/^.*.*$//' \
> >> -e 's/\.freebsd\.org//' \
> >> -e 's/^freebsd-//'`
> >>
> >> :0:FreeBSD$LOCKEXT
> >> | $STORE +FreeBSD/${ListId}
> >> }
>
> in that it winds up in FreeBSD/[the stuff between "freebsd-" and
> ".freebsd.org"]. Except without forking off a bunch of external
> programs, just to pull out a piece of a header :p
Yes, I realized that just moments after my last reply. Somehow
that went right over my head at first. :-)
I like this already! Thanks again.
Conrad
--
Conrad J. Sabatier
conr...@cox.net
___
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: Replacing procmail with maildrop
On Mon, 26 Sep 2011 03:45:17 -0500 "Matthew D. Fuller" wrote: > On Mon, Sep 26, 2011 at 02:43:50AM -0500 I heard the voice of > Conrad J. Sabatier, and lo! it spake thus: > > > > I'm just wondering, though, if you could offer any advice on how to > > convert something like the following procmail recipe I use for my > > FreeBSD mailing lists. > > I work off the envelope sender, but you can adapt it. Maildrop gives > you subexpression matches. > > if($RETPATH =~ /^ to $MBOXDIR/f-$MATCH1 > > (of course, the cvs list ends up having to be special cased) > > > So you'd just match the List-ID header similarly, something like > > if(/^List-ID: freebsd-([a-z]+).freebsd.org/) > to FreeBSD/$MATCH1 > > (totally untested of course...) Oh, I see now! So the match result on the parenthesized subexpression will, in fact, be exactly what I'm looking for already. No more need to "manually" strip away all the unwanted stuff with sed, as I was doing for procmail. No need for [re]formail, either. Neat-o! :-) Thanks again. -- Conrad J. Sabatier conr...@cox.net ___ 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: Replacing procmail with maildrop
On Mon, Sep 26, 2011 at 04:07:31AM -0500 I heard the voice of
Conrad J. Sabatier, and lo! it spake thus:
>
> OK, I'm starting to get a little better of an idea of what to do.
> My main concern so far has been the ability to nest a set of
> commands within a recipe the way procmail allows.
Well, it's C-like; you can put braces around the body of the if and
have however much you want inside there.
> I don't want to use the full list name as it appears in the List-Id
> header, but a simpler, pared down version of it. This was fairly
> easy to do in procmail; I just have to work out the correct syntax
> for doing it with maildrop.
What I had there
> > if(/^List-ID: freebsd-([a-z]+).freebsd.org/)
> > to FreeBSD/$MATCH1
should give you (mod bugs in my top-of-my-head'ing of course) the same
sorta result as your
>> :0
>> * ^List-Id:.*freebsd.org
>> {
>> ListId=`formail -c -x List-Id: | \
>> sed -e 's/^.*.*$//' \
>> -e 's/\.freebsd\.org//' \
>> -e 's/^freebsd-//'`
>>
>> :0:FreeBSD$LOCKEXT
>> | $STORE +FreeBSD/${ListId}
>> }
in that it winds up in FreeBSD/[the stuff between "freebsd-" and
".freebsd.org"]. Except without forking off a bunch of external
programs, just to pull out a piece of a header :p
--
Matthew Fuller (MF4839) | fulle...@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
___
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: Replacing procmail with maildrop
On Mon, 26 Sep 2011 03:45:17 -0500 "Matthew D. Fuller" wrote: > On Mon, Sep 26, 2011 at 02:43:50AM -0500 I heard the voice of > Conrad J. Sabatier, and lo! it spake thus: > > > > I'm just wondering, though, if you could offer any advice on how to > > convert something like the following procmail recipe I use for my > > FreeBSD mailing lists. > > I work off the envelope sender, but you can adapt it. Maildrop gives > you subexpression matches. > > if($RETPATH =~ /^ to $MBOXDIR/f-$MATCH1 > > (of course, the cvs list ends up having to be special cased) > > > So you'd just match the List-ID header similarly, something like > > if(/^List-ID: freebsd-([a-z]+).freebsd.org/) > to FreeBSD/$MATCH1 > > (totally untested of course...) OK, I'm starting to get a little better of an idea of what to do. My main concern so far has been the ability to nest a set of commands within a recipe the way procmail allows. I don't want to use the full list name as it appears in the List-Id header, but a simpler, pared down version of it. This was fairly easy to do in procmail; I just have to work out the correct syntax for doing it with maildrop. I see now that the maildrop package includes a formail-like equivalent, "reformail", so that's good news. Looks like it won't be all that difficult at all, really, to convert my existing recipes. Will just have to spend some more time familiarizing myself with the maildrop rc file format/syntax and getting used to the differences between it and procmail. Thanks! -- Conrad J. Sabatier conr...@cox.net ___ 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: Replacing procmail with maildrop
On Mon, Sep 26, 2011 at 02:43:50AM -0500 I heard the voice of Conrad J. Sabatier, and lo! it spake thus: > > I'm just wondering, though, if you could offer any advice on how to > convert something like the following procmail recipe I use for my > FreeBSD mailing lists. I work off the envelope sender, but you can adapt it. Maildrop gives you subexpression matches. if($RETPATH =~ /^http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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: Maintainer timeout ports/159786 (security/ossec-hids-server)
On Mon, 2011-09-26 at 14:54 +0800, wen heping wrote:
> Hi,
>
>The build failed and below is the error message.
>Would you fix it ? Thanks.
>
> wen
>
>
Ok this is fixed in the attached patch.
>
> ===> Building package for ossec-hids-client-2.6_1
> tar: ossec-hids/active-response/bin/default-firewall-drop.sh: Cannot
> stat: No such file or directory
> tar: Error exit delayed from previous errors.
> pkg_create: make_dist: tar command failed with code 256
> *** Error code 1
>
> Stop in /a/ports/security/ossec-hids-client.
> Deleting ossec-hids-client-2.6_1
> pkg_delete: file
> '/usr/local/ossec-hids/active-response/bin/default-firewall-drop.sh'
> doesn't exist
> pkg_delete: couldn't entirely delete package (perhaps the packing list is
> incorrectly specified?)
>
> === Checking filesystem state
>
> === Checking filesystem state after all packages deleted
> cmp: EOF on /etc/group-save
> === /etc/group was modified:
> --- /etc/group-save 2011-09-26 03:28:48.0 +
> +++ /etc/group2011-09-26 03:29:24.0 +
> @@ -29,3 +29,4 @@
> www:*:80:
> nogroup:*:65533:
> nobody:*:65534:
> +ossec:*:1001:
> cmp: EOF on /etc/master.passwd-save
> === /etc/master.passwd was modified:
> --- /etc/master.passwd-save 2011-09-26 03:28:48.0 +
> +++ /etc/master.passwd2011-09-26 03:29:24.0 +
> @@ -21,3 +21,4 @@
> pop:*:68:6::0:0:Post Office Owner:/nonexistent:/usr/sbin/nologin
> www:*:80:80::0:0:World Wide Web Owner:/nonexistent:/usr/sbin/nologin
> nobody:*:65534:65534::0:0:Unprivileged user:/nonexistent:/usr/sbin/nologin
> +ossec:*:1001:1001::0:0:User &:/usr/local/ossec-hids:/sbin/nologin
>
> build of /usr/ports/security/ossec-hids-client ended at Mon Sep 26
> 03:29:28 UTC 2011
> ___
> 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"
Thanks
Jake
diff -ruN ossec-hids-client.bak/pkg-plist.client
ossec-hids-client/pkg-plist.client
--- ossec-hids-client.bak/pkg-plist.client 2011-08-15 10:04:21.859266000
+0100
+++ ossec-hids-client/pkg-plist.client 2011-09-26 09:14:06.214577546 +0100
@@ -7,6 +7,7 @@
%%PORTNAME%%/active-response/bin/pf.sh
%%PORTNAME%%/active-response/bin/restart-ossec.sh
%%PORTNAME%%/active-response/bin/route-null.sh
+%%PORTNAME%%/bin/agent-auth
%%PORTNAME%%/bin/manage_agents
%%PORTNAME%%/bin/ossec-agentd
%%PORTNAME%%/bin/ossec-control
diff -ruN ossec-hids-server.bak/Makefile ossec-hids-server/Makefile
--- ossec-hids-server.bak/Makefile 2011-03-19 13:15:29.0 +
+++ ossec-hids-server/Makefile 2011-08-08 16:55:11.734157451 +0100
@@ -6,7 +6,7 @@
#
PORTNAME= ossec-hids
-PORTVERSION= 2.5.1
+PORTVERSION= 2.6
PORTREVISION= 1
CATEGORIES=security
MASTER_SITES= http://www.ossec.net/files/ \
@@ -18,10 +18,10 @@
USE_RC_SUBR= ossec-hids
-.if defined(WITH_DB)
-USE_MYSQL= yes
-USE_PGSQL= yes
-USE_BDB= yes
+.if !defined(CLIENT_ONLY)
+OPTIONS= MYSQL "Enable MySQL support" off \
+ PGSQL "Enable PostgreSQL support" off \
+ BDB "Enable with Berkeley DB" off
.endif
SUB_LIST= PORTNAME=${PORTNAME}
@@ -31,6 +31,23 @@
.include
+.if !defined(CLIENT_ONLY)
+.if defined(WITH_MYSQL)
+WITH_DB= yes
+USE_MYSQL= yes
+.endif
+
+.if defined(WITH_PGSQL)
+WITH_DB= yes
+USE_PGSQL= yes
+.endif
+
+.if defined(WITH_BDB)
+WITH_DB= yes
+USE_BDB= yes
+.endif
+.endif
+
.if defined(CLIENT_ONLY)
PKGNAMESUFFIX= -client
CONFLICTS= ossec-hids-server-[0-9]* ossec-hids-local-[0-9]*
diff -ruN ossec-hids-server.bak/distinfo ossec-hids-server/distinfo
--- ossec-hids-server.bak/distinfo 2010-12-14 00:41:09.0 +
+++ ossec-hids-server/distinfo 2011-08-08 15:30:27.165325589 +0100
@@ -1,2 +1,2 @@
-SHA256 (ossec-hids-2.5.1.tar.gz) =
e7bb4701a6b9a40f76d4e2c3c39106ded3c37f13ccc3ce476029da1f0e9c9f9e
-SIZE (ossec-hids-2.5.1.tar.gz) = 740470
+SHA256 (ossec-hids-2.6.tar.gz) =
37a6b14a0c41252852b51fd06cc186a8b66bd9e01821efd70305a6dd782a2b4c
+SIZE (ossec-hids-2.6.tar.gz) = 758125
diff -ruN ossec-hids-server.bak/pkg-plist ossec-hids-server/pkg-plist
--- ossec-hids-server.bak/pkg-plist 2010-12-14 00:41:09.0 +
+++ ossec-hids-server/pkg-plist 2011-09-26 09:13:57.262575174 +0100
@@ -14,6 +14,7 @@
%%PORTNAME%%/bin/ossec-agentd
%%PORTNAME%%/bin/ossec-agentlessd
%%PORTNAME%%/bin/ossec-analysisd
+%%PORTNAME%%/bin/ossec-authd
%%PORTNAME%%/bin/ossec-control
%%PORTNAME%%/bin/ossec-csyslogd
%%PORTNAME%%/bin/ossec-dbd
@@ -49,10 +50,13 @@
%%PORTNAME%%/rules/arpwatch_rules.xml
%%PORTNAME%%/rules/asterisk_rules.xml
%%PORTNAME%%/rules/attack_rules.xml
+%%PORTNAME%%/rules/bro-ids_rules.xml
%%PORTNAME%%/rules/cimserver_rules.xml
%%PORTNAME%%/rules/cisco-io
Re: Options for emulators/wine?
from Michael Holmes : > HAL shouldn't be necessary, but you might need to manually set up > CUPS. Winemaker is just a tool for building open-source Windows apps > on Wine with ease. There are a few GUI tools to set up CUPS, but if I > recall correctly, the web interface to CUPS is pretty > self-explanatory. HP do have a nice GUI called HPLIP for utilising > their printers on Linux (and ported to FreeBSD) available on ports as > print/hplip, but it doesn't work with the GENERIC console config, and > seems to be quite awkward to set up (you apparently cannot load USB > mass storage until the printer is 'adopted' by the generic USB stack). I don't know what you mean by "adopted" (by the generic USB stack): seems mystic to me. CUPS would be necessary to setup printing for BSD and Linux, but would it be necessary when using Wine and going the MS-Windows way? Package message said that ulpt had to be turned off in kernel config and not loaded as a module. On the older computer, I tried unsuccessfully to setup the printer last June 29 from both NetBSD and FreeBSD, using hplip in both cases. Predominant message was "No devices found". NetBSD pkgsrc had only an outdated hpijs, but pkgsrc-wip (http://pkgsrc-wip.sourceforge.net/) had hplip. Message said also to disable umass, but that was too harsh, and prevented recognizing USB sticks. Would Linux offer a better chance with hplip than BSD? I tried also with Linux (Slackware 13.0), but hplip version was behind, and that failed. There is also the Ethernet option with the printer, but I need an Ethernet switch or additional router for that, which I intend to order. First attempt to build hplip on the new computer failed due to libieee1284 dependency being for i386 only. Subsequently I turned off that option after finding it was for parallel-port scanners only, not USB. Tom ___ 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: Replacing procmail with maildrop
On Sun, 25 Sep 2011 22:01:13 -0600 (MDT)
Warren Block wrote:
> Recent discussion here about the desirability of replacing procmail
> finally convinced me to switch to maildrop. It turned out to be
> relatively painless. I took some notes that may be helpful for
> others considering the change:
>
> http://www.wonkity.com/~wblock/docs/html/maildrop.html
Thank you for that! I've been reluctant to switch from procmail to
anything else just yet (although I know I'll have to do so eventually,
if this port is going to be expired), but these tips you've provided
certainly will help.
I'm just wondering, though, if you could offer any advice on how
to convert something like the following procmail recipe I use for my
FreeBSD mailing lists.
I like to store my FreeBSD lists each under a separate MH folder under
$MAILDIR/FreeBSD, so the following recipe strips off everything
outside the angle brackets in the List-Id header (including the
brackets themselves, of course), and then the trailing ".freebsd.org"
and leading "freebsd-" and from the actual list name, to derive the
correct folder name.
So, for instance. the list name "freebsd-ports.freebsd.org" winds up as
the folder name "ports".
One problem is, without procmail's "formail" utility, how to
extract and strip the List-Id header. Does maildrop include a tool
similar to formail? Also, can one define a custom "to" command, in
order to use the nmh "rcvstore" command?
I've included only the parts of my .procmailrc needed to provide a
clear picture of what's going on:
# Path to executables from the nmh package
NMH_PATH=/usr/local/libexec/nmh
# Make sure everything we need is here
PATH=/bin:/usr/bin:/usr/local/bin:${NMH_PATH}
# Probably not necessary, but doesn't hurt either
MAILDIR=${HOME}/Mail
SHELL=/bin/sh
# the nmh command to store mail into a folder
STORE=rcvstore
# extension to use for lockfiles
LOCKEXT=.lock
# recipe for FreeBSD lists
:0
* ^List-Id:.*freebsd.org
{
ListId=`formail -c -x List-Id: | \
sed -e 's/^.*.*$//' \
-e 's/\.freebsd\.org//' \
-e 's/^freebsd-//'`
:0:FreeBSD$LOCKEXT
| $STORE +FreeBSD/${ListId}
}
Thanks in advance for any help!
--
Conrad J. Sabatier
conr...@cox.net
___
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: Maintainer timeout ports/159786 (security/ossec-hids-server)
Hi,
The build failed and below is the error message.
Would you fix it ? Thanks.
wen
building ossec-hids-client-2.6_1 in directory /usr/local/tinderbox/9.0-FreeBSD
build started at Mon Sep 26 03:28:48 UTC 2011
port directory: /usr/ports/security/ossec-hids-client
building for: 9.0-CURRENT i386
maintained by: valerio.dae...@gmail.com
Makefile ident: $FreeBSD: ports/security/ossec-hids-client/Makefile,v
1.3 2007/12/30 10:54:16 rafan Exp $
prefixes: LOCALBASE=usr/local PREFIX=/usr/local
Begin Configuration:
---Begin Environment---
PACKAGE_BUILDING=1
ARCH=i386
USER=root
CCACHE_DIR=
BRANCH=CURRENT
CCACHE_NOLINK=1
HOST_WORKDIR=
HOME=/root
OLDPWD=/
BATCH=1
FTP_TIMEOUT=900
PKGZIPCMD=bzip2
HAVE_MOTIF=1
defaultUpdateHost=cvsup.FreeBSDChina.org
HTTP_TIMEOUT=900
DISTFILE_CACHE=/usr/ports/distfiles
pb=/usr/local/tinderbox
OSREL=9.0
PYTHON_DEFAULT_VERSION=python2.7
defaultUpdateType=CSUP
TINDERD_LOGFILE=/dev/null
PORTOBJFORMAT=elf
DISTDIR=/tmp/distfiles
WRKDIRPREFIX=/work
DISTCACHE=/distcache
CCACHE_LOGFILE=
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
PACKAGES=/tmp/packages
TIMEOUT=7200
PKGSUFFIX=.tbz
OSVERSION=900021
__DSVERSION__=3.2
OPTIONS_ENABLED=0
TINDERD_SLEEPTIME=120
UNAME_n=tinderbox.host
__MKLVL__=1
LOCALBASE=/usr/local
CCACHE_JAIL=0
CCACHE_MAX_SIZE=1G
MASTER_SITE_OVERRIDE=file:///distcache/${DIST_SUBDIR}/
DISTFILE_URI=
X_WINDOW_SYSTEM=xorg
UNAME_r=9.0-CURRENT
OPTIONS_DIR=
USA_RESIDENT=YES
UNAME_s=FreeBSD
PARALLEL_PACKAGE_BUILD=1
PWD=/usr/ports/security/ossec-hids-client
UNAME_v=FreeBSD 9.0-CURRENT #0: Mon Sep 26 11:25:37 CST 2011
r...@tinderbox.host:/usr/src/sys/magic/kernel/path
FTP_PASSIVE_MODE=yes
CCACHE_ENABLED=0
INDEXFILE=INDEX-9
---End Environment---
---Begin OPTIONS List---
---End OPTIONS List---
End Configuration.
FETCH_DEPENDS=
PATCH_DEPENDS=
EXTRACT_DEPENDS=
BUILD_DEPENDS=
RUN_DEPENDS=
add_pkg
===> License check disabled, port has not defined LICENSE
=> ossec-hids-2.6.tar.gz doesn't seem to exist in /tmp/distfiles/.
=> Attempting to fetch file:///distcache//ossec-hids-2.6.tar.gz
ossec-hids-2.6.tar.gz 740 kB 92 MBps
=> SHA256 Checksum OK for ossec-hids-2.6.tar.gz.
add_pkg
===> License check disabled, port has not defined LICENSE
===> Extracting for ossec-hids-client-2.6_1
=> SHA256 Checksum OK for ossec-hids-2.6.tar.gz.
add_pkg
===> Patching for ossec-hids-client-2.6_1
===> Applying FreeBSD patches for ossec-hids-client-2.6_1
add_pkg
===> Configuring for ossec-hids-client-2.6_1
===> Building for ossec-hids-client-2.6_1
INFO: Little endian set.
*** Making zlib (by Jean-loup Gailly and Mark Adler) ***
gcc -c -g -Wall -I../../ -I../../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"zlib\" -DXML_VAR=\"var\" -DOSSECHIDS *.c
ar cru libz.a *.o
ranlib libz.a
cp -pr zlib.h zconf.h ../../headers/
cp -pr libz.a ../
*** Making os_xml ***
gcc -DXML_VAR=\"var\" -g -Wall -I../ -I../headers -DCLIENT
-DUSE_OPENSSL -DARGV0=\"os_xml\" -DXML_VAR=\"var\" -DOSSECHIDS -c
os_xml.c os_xml_access.c os_xml_node_access.c os_xml_variables.c
os_xml_writer.c
ar cru os_xml.a os_xml.o os_xml_access.o os_xml_node_access.o
os_xml_variables.o os_xml_writer.o
ranlib os_xml.a
*** Making os_regex ***
gcc -g -Wall -I../ -I../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"os_regex\" -DXML_VAR=\"var\" -DOSSECHIDS -c *.c -Wall
ar cru os_regex.a *.o
ranlib os_regex.a
*** Making os_net ***
gcc -g -Wall -I../ -I../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"os_net\" -DXML_VAR=\"var\" -DOSSECHIDS -c os_net.c
ar cru os_net.a os_net.o
ranlib os_net.a
*** Making os_crypto ***
gcc -g -Wall -I../../ -I../../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"blowfish_op\" -DXML_VAR=\"var\" -DOSSECHIDS -c bf_op.c
bf_skey.c bf_enc.c
ar cru bf_op.a bf_op.o bf_skey.o bf_enc.o
ranlib bf_op.a
gcc -g -Wall -I../../ -I../../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"md5_op\" -DXML_VAR=\"var\" -DOSSECHIDS -c md5.c md5_op.c
ar cru md5_op.a md5_op.o md5.o
ranlib md5_op.a
gcc -g -Wall -I../../ -I../../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"sha1_op\" -DXML_VAR=\"var\" -DOSSECHIDS -c sha1_op.c
ar cru sha1_op.a sha1_op.o
ranlib sha1_op.a
gcc -g -Wall -I../../ -I../../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"md5_sha1_op\" -DXML_VAR=\"var\" -DOSSECHIDS -c ../md5/md5.c
md5_sha1_op.c
ar cru md5_op.a md5_sha1_op.o ../md5/md5.o
ranlib md5_op.a
gcc -g -Wall -I../../ -I../../headers -DCLIENT -DUSE_OPENSSL
-DARGV0=\"shared\" -DXML_VAR=\"var\" -DOSSECHIDS -c *.c
ar cru shared.a *.o
ranlib shared.a
ar cru os_crypto.a blowfish/bf_op.o blowfish/bf_skey.o
blowfish/bf_enc.o md5/md5_
