FreeBSD Port: inn-2.4.5
Hi - I'm running FBSD 7.1-p2 and inn-2.4.5 with largefile support and ovdb overview in a jail without any difficulties sofar. The recent Perl-upgrade to 5.8.9 crashes innd (core dump) at start-up, reproducible. I did re-compile all ports including inn, same result. Then I removed Perl support during configuration, re-compiled, and now innd starts and runs as expected. I just want to bring this to your attention, if you won't know this already. I couldn't find reports at the ports-mailing list sofar. Hope that this isn't to difficult to fix. Let me know if you need help in further debugging. Thanks and regards, Michael ___ 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
perl 5.8.9 port bug...
Hello, It seems like there is a bug in perl which doesnt allow suidperl to work at all. After upgrading to perl 5.8.9, I couldnt run any suid scripts. Fortunately there is a fix for the issue, can you add this to the port as a patch? References to the fix: http://www.perlmonks.org/?node_id=731836 http://www.gossamer-threads.com/lists/perl/porters/234551 Thanks, Evren ___ 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: tinderbox - tinderd and nullfs?
Torfinn Ingolfsen tin...@gmail.com writes: Hello, I have installed tinderbox[1] and is now trying to get tinderd to work. I have read the information at the web page[2], but it is very terse. There is a README file at LOCALBASE/tinderbox/scripts. It was (almost always) sufficient for me to configure tinderbox. Note: I am using nullfs instead of nfs. Even if I added -nullfs to tinderd_flags, tinderd just sits there and doesn't want to start a build. You should configure tinderbox as well. Please, read the above mentioned README file and show: # $LOCALBASE/tinderbox/scripts/tc configGet And there is a port in the queue: r...@kg-vm# ./tc listBuildPortsQueue +=+===+===+==+ | Id | Build Name| Port Directory | Pri | +=+===+===+===+ | 1 | 7.1-FreeBSD | net-p2p/amule2 | 10 | +-+---+-+-+ But tinderd does nothing: r...@kg-vm# ps ax | grep tinder 51574 p0 S+ 0:00.00 grep tinder 50765 p2 I 0:00.02 /bin/sh -T /usr/local/tinderbox/scripts/tinderd -nullfs What am I doing wrong? References: 1) http://www.freshports.org/ports-mgmt/tinderbox/ 2) http://tinderbox.marcuscom.com/ WBR -- bsam ___ 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
Periodic script for FreeBSD port of aide
Hello aide port maintainer,
I wrote a periodic script for aide port (attached). It run aide
--check. ${daily_status_security_aide_enable} defaults to NO, so it
need to be enabled in /etc/periodic.conf with:
daily_status_security_aide_enable=YES
I thought you might be interested in including it.
Regards,
--
Krzysztof Burghardt krzysz...@burghardt.pl
http://www.burghardt.pl/
405.aide
Description: Binary data
___
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
Scilab 5.0
Hello Will Scilab 5 be ported to FreeBSD? Thanks Otacílio ___ 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: DragonFlyBSD mail agent
Michel Talon ta...@lpthe.jussieu.fr 2009-01-08: would it not be interesting to have the DragonFlyBSD mail agent in FreeBSD? [...] http://www.freebsd.org/cgi/query-pr.cgi?pr=130658 New port: mail/dma - The DragonFly Mail Agent. Includes an optional quick hack (ruby wrapper) to add -t sendmail option support, needed to make send-pr(1) happy with dma. For simplicity i have a tarball here: http://www.lpthe.jussieu.fr/~talon/dma.tgz Note that this dma.tgz is behind the latest DragonFly sources. -- Daniel Roethlisberger http://daniel.roe.ch/ ___ 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
textproc/libxml2 and failed patching after using portsnap...
Hello, This is just a notice that a patch is no longer needed with textproc/libxml2 -- it appears to have been checked in upstream: === Applying FreeBSD patches for libxml2-2.7.2_1 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to include/libxml/parser.h.rej 19 out of 24 hunks failed--saving rejects to parser.c.rej Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to parserInternals.c.rej = Patch patch-CVE-2008-3281 failed to apply cleanly. *** Error code 1 This isn't noted in the CVSweb interface, so I assume the file is stale. However, it was recently synced (today at ~noon) with portsnap. I've seen similar things in the past on a handful of occasions with portsnap (not csup) with stale files -- is this an infrastructure bug, just stale data that's going to get cycled out, or something else? The fix is trivial (delete the file) but it still is a bit of an annoyance. 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: textproc/libxml2 and failed patching after using portsnap...
On Sat, Jan 17, 2009 at 1:49 PM, Garrett Cooper yanef...@gmail.com wrote: Hello, This is just a notice that a patch is no longer needed with textproc/libxml2 -- it appears to have been checked in upstream: === Applying FreeBSD patches for libxml2-2.7.2_1 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to include/libxml/parser.h.rej 19 out of 24 hunks failed--saving rejects to parser.c.rej Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to parserInternals.c.rej = Patch patch-CVE-2008-3281 failed to apply cleanly. *** Error code 1 This isn't noted in the CVSweb interface, so I assume the file is stale. However, it was recently synced (today at ~noon) with portsnap. I've seen similar things in the past on a handful of occasions with portsnap (not csup) with stale files -- is this an infrastructure bug, just stale data that's going to get cycled out, or something else? The fix is trivial (delete the file) but it still is a bit of an annoyance. Thanks, -Garrett I ran into more issues like this with x11-toolkits/gtk20 ;( (4 patches failed to apply cleanly)... -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: textproc/libxml2 and failed patching after using portsnap...
Garrett Cooper wrote: This is just a notice that a patch is no longer needed with textproc/libxml2 -- it appears to have been checked in upstream: This isn't noted in the CVSweb interface, so I assume the file is stale. However, it was recently synced (today at ~noon) with portsnap. Does running 'portsnap extract textproc/libxml2' make the problem patch go away? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ 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: textproc/libxml2 and failed patching after using portsnap...
On Sat, Jan 17, 2009 at 2:40 PM, Colin Percival cperc...@freebsd.org wrote: Garrett Cooper wrote: This is just a notice that a patch is no longer needed with textproc/libxml2 -- it appears to have been checked in upstream: This isn't noted in the CVSweb interface, so I assume the file is stale. However, it was recently synced (today at ~noon) with portsnap. Does running 'portsnap extract textproc/libxml2' make the problem patch go away? Yes. Is this an issue with the `update' logic? 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: textproc/libxml2 and failed patching after using portsnap...
Garrett Cooper wrote: On Sat, Jan 17, 2009 at 2:40 PM, Colin Percival cperc...@freebsd.org wrote: Garrett Cooper wrote: This is just a notice that a patch is no longer needed with textproc/libxml2 -- it appears to have been checked in upstream: This isn't noted in the CVSweb interface, so I assume the file is stale. However, it was recently synced (today at ~noon) with portsnap. Does running 'portsnap extract textproc/libxml2' make the problem patch go away? Yes. Is this an issue with the `update' logic? I suppose that it's possible that there's a bug in the 'portsnap update' logic, but usually problems like this occur as a result of someone trying to use both portsnap and cvsup/csup. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ 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 failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: pdftk-1.41: no entry for /usr/ports/lang/gcc41 make_index: pdftk-1.41: no entry for /usr/ports/lang/gcc41 Committers on the hook: amdmi3 beech db gerald linimon lioux tabthorpe Most recent CVS update was: U comms/fldigi/Makefile U comms/fldigi/distinfo U comms/fldigi/pkg-plist U comms/fldigi/files/patch-src_dialogs_fl_digi.cxx U comms/fldigi/files/patch-src_fileselector_fileselect.cxx U comms/fldigi/files/patch-src_include_configuration.h U comms/fldigi/files/patch-src_include_threads.h U comms/fldigi/files/patch-src_main.cxx U comms/fldigi/files/patch-src_spot_pskrep.cxx U games/burrtools/Makefile U games/burrtools/distinfo U games/burrtools/pkg-plist U games/numptyphysics/Makefile U graphics/qcomicbook/Makefile U lang/Makefile U mail/dovecot/Makefile U mail/dovecot/distinfo U mail/dovecot/files/dovecot.sh.in U mail/squirrelmail-password_forget-plugin/Makefile U mail/squirrelmail-password_forget-plugin/distinfo U mail/squirrelmail-password_forget-plugin/pkg-plist U mail/squirrelmail-vlogin-plugin/Makefile U mail/squirrelmail-vlogin-plugin/distinfo U mail/squirrelmail-vlogin-plugin/pkg-plist U ports-mgmt/portmk/Mk/bsd.port.mk U science/vis5d+/Makefile U textproc/asciidoc/Makefile U textproc/asciidoc/distinfo U textproc/asciidoc/pkg-plist U textproc/asciidoc/files/patch-Makefile.in U textproc/rubygem-rdiscount/Makefile U textproc/rubygem-rdiscount/distinfo U www/rubygem-sinatra/Makefile U www/rubygem-sinatra/distinfo ___ 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
Scilab 5.0
Hello Will Scilab 5 be ported to FreeBSD? Thanks Otacílio Yes, I hope to soon, but I am busy at the moment. I'd be interested in hearing whether users of the existing scilab 4.x port would like the new version, which is Java-based, to replace the old port -- or just be added in addition to it. Regards, 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: An update regarding CONFIGURE_ENV and ${F77}, ${FC}, ${FFLAGS}
On Sun, 18 Jan 2009, Gerald Pfeifer wrote:
the following ports contain snippets along the lines of
CONFIGURE_ENV+= FC=${FC} F77=${F77} FFLAGS=${FFLAGS}
These are no longer necessary after recent improvement I have made to
the Mk/bsd.gcc.mk infrastructure related to the USE_FORTRAN knob.
Please update your ports removing these.
To provide a concrete example, in the case of science/dcl, something
like the following would move into the right direction (untested):
Gerald
Index: Makefile
===
RCS file: /home/ncvs/ports/science/dcl/Makefile,v
retrieving revision 1.8
diff -u -3 -p -r1.8 Makefile
--- Makefile26 Sep 2008 08:54:21 - 1.8
+++ Makefile18 Jan 2009 05:44:19 -
@@ -20,10 +20,7 @@ USE_XORG=x11 xext
GNU_CONFIGURE= yes
CONFIGURE_ARGS=--prefix=${PREFIX} --disable-gtk2 --disable-gtk --with-x
-WANT_FORTRAN= yes #dummy but future use
-BUILD_DEPENDS+=gfortran42:${PORTSDIR}/lang/gcc42
-FC=gfortran42
-CONFIGURE_ENV+=FC=${FC} FFLAGS=${FFLAGS}
+USE_FORTRAN= yes
DOCFILES= CHECK CREDITS HISTORY README README_clrmap README_gt2dlib \
README_itr51 README_pslib README_umfmap
___
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: Call for testers: MythTV 0.21 port upgrade
On Thursday, 15 January 2009 at 17:35:40 -0500, Greg Larkin wrote: Hello all of you MythTV supporters with the collective patience of the universe! I recently committed mythtv-frontend (PR 127856) and mythtv-themes (PR 127857), and please let me know if you see any problems with the updates. OK, I've built mythtv-frontend. On a machine with no prior installation, it finds the machine running a MythTV 0.21 back end (how?). I needed to extract the password to the MySQL database from the back end, but then it seems to work. On another machine, where I have a MySQL server with an old version of the mythconverg database, I can't start it: it connects to the database, finds that it's the wrong version, and stops again. I suspect that I could fix that with mythtv-setup, but the port doesn't install it. Would it be difficult to get it to do so? Also, every time I stop the front end, it SIGSEGVs. I haven't investigated why. Greg -- See complete headers for address and phone numbers. pgpfx7JOZdOcb.pgp Description: PGP signature
Re: Periodic script for FreeBSD port of aide
In message 80bd11420901171136q67733119y8028838118245...@mail.gmail.com,
Krzy
sztof Burghardt writes:
Hello aide port maintainer,
I wrote a periodic script for aide port (attached). It run aide
--check. ${daily_status_security_aide_enable} defaults to NO, so it
need to be enabled in /etc/periodic.conf with:
daily_status_security_aide_enable=YES
I thought you might be interested in including it.
I have a few thoughts on this issue.
The intention is to run it daily. What if the user wants to run it weekly
or monthly or a combination thereof?
One option might be that you maintain it on a web site or FTP site
somewhere and the port fetches the script and installs it. I'm not
convinced that this is a good idea but I'm throwing it out there anyway.
Could we genericice the script for use with aide, tripwire, and integrit?
The periodic scripts run at 03:01, 04:15. and 05;30. I've usually run
tripwire and aide as close to coming into work in the morning as possible
so that the window of opportunity of something being altered and my finding
out about it is as small as possible. Is the periodic infrastructure the
best place to run the script from or should it be run using a separate cron
job?
--
Cheers,
Cy Schubert cy.schub...@komquats.com
FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org
e**(i*pi)+1=0
___
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 now builds successfully on 6.x
___ 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
