Re: trouble running spamass-milter as spamd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My apologies for taking so long to get back to you.
Let me first start by saying I do not know much about postfix.
I emulated your spamass-milter settings on my system, and had no
problems, but after looking even closer at it, it seems to me you might
want to try run sa-spamd with -u spamd, as spamass-milter is behaving as
it ought to.
I hope this helps.
Thomas
On Tue, 13 Mar 2007 02:04:10 -0700
Peter Losher <[EMAIL PROTECTED]> wrote:
> I am integrating spamass-milter into my postfix-based MX's, and while
> mail to me works and is processed by spamd (as I have an account on
> the box), mail to non-existant users throws up errors when it's
> invoked:
>
> -=-
> Mar 13 08:48:20 no-mx spamd[657]: spamd: handle_user unable to find
> user: 'boom'
> Mar 13 08:48:20 no-mx spamd[657]: spamd: still running as root: user
> not specified with -u, not found, or set to root, falling back to
> nobody at /usr/local/bin/spamd line 1144, line 4.
> -=-
>
> Now in /etc/rc.conf I have -u set to spamd:
>
> -=-
> spamass_milter_enable="YES"
> spamass_milter_socket="/var/run/spamass-milter.sock"
> spamass_milter_flags="-f -p ${spamass_milter_socket} -r 10 -m -u
> spamd" -=-
>
> and ps verifies this:
>
> -=-
> root 620 0.0 0.7 3640 1652 ?? Ss1:08AM 0:01.38
> /usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock -r
> 10 -m -u spamd
> -=-
>
> and spamd is a valid user on this system; I even gave it a proper
> shell in case that was the problem:
>
> -=-
> % finger spamd
> Login: spamdName: SpamAssassin user
> Directory: /var/spool/spamd Shell: /bin/csh
> Never logged in.
> No Mail.
> No Plan
> -=-
>
> So am I missing something here?
>
> Best Wishes - Peter
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFF+Mva5Gm/jNBp8qARAk2EAJ9DD1zugEg8130oMqunQq6c12HY4wCfdOOx
5MzBCCdt5byZ/CWnPEkN0TY=
=zrZQ
-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]"
Re: php4 port - undefined ref to getopt_long
On Wed, Mar 14, 2007 at 06:37:01PM -0900, Beech Rintoul wrote: > Regardless of what the individual maintainers do to support 4.x, the > build infrastructure will not support it much longer. [EMAIL PROTECTED] [EMAIL PROTECTED] of 2007/03/06 06:21:46@ See: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=118171+0+archive/2007/freebsd-ports/20070311.freebsd-ports http://docs.freebsd.org/cgi/getmsg.cgi?fetch=641712+0+archive/2007/cvs-all/20070311.cvs-all mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php4 port - undefined ref to getopt_long
On Thu, Mar 15, 2007 at 12:41:16PM +1100, andrew clarke wrote: > I have a FreeBSD 4.10-REL system here with a still-working ports system, > using the latest ports tree. Actually, you don't. If you read UPDATING you'll find out that I removed the remmants of the 4.X support from bsd.port.mk. This was in accordance with what we had been saying in email for months, and which I specifically did a HEADSUP for, to ports@, a day earlier. In particular, I warned anyone still using 4.X _not_ to track the bsd.port.mk update, or any other further infrastructure update, and that instead to stay with the RELENG4_EOL tag. > Should ports maintainers still be encouraged to support 4.x if it is not > a lot of trouble? We removed the requirement that maintainers support 4.X many months ago, and within the past few weeks have been recommending against them spending any further time on it because of the upcoming update. > (I do intend to upgrade to 6.x at some stage, but not until a lot of > ports that I use start to fail to build, and there is no sign of that > happening yet :-) Various maintainers have, with portmgr's permission and now encouragement, been removing the 4.X special-case code from ports in the ports tree to start simplifying the code. Summary: you are now using a configuration that we are not supporting. I'm sorry, but we have been talking about doing this for over a year, on public lists, to try to cut down the demands that we put on our committers and maintainers: that they support _four_ branches (three major releases plus -CURRENT). This was simply holding us back. I think you will find that 6.2 is far better for almost every purpose except high performance on uniprocessor systems, and in the latest work on -CURRENT, even that is being addressed. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php4 port - undefined ref to getopt_long
On Wednesday 14 March 2007 17:41, andrew clarke said: > On Wed, Mar 14, 2007 at 12:37:48PM -0700, Chuck Swiger wrote: > > Please be aware that FreeBSD 4.11 is no longer supported-- the > > ports framework has been updated in a fashion which is no longer > > backwards compatible with that version of the OS, so you're going > > to be rolling your own software from here on out if you want to > > stay with that version. > > I have a FreeBSD 4.10-REL system here with a still-working ports > system, using the latest ports tree. Judging from your comment > above, this is impossible, unless I've misunderstood you. > > Should ports maintainers still be encouraged to support 4.x if it > is not a lot of trouble? Recently I've sent mail to two port > maintainers with very minor patches to build ports on 4.x. As Kris Kennaway wrote a few weeks ago: "Now that 4.x is unsupported we will begin to remove the legacy support code that has been accumulating for the past 7+ years and complicating certain aspects of the ports tree." "This means that in the near future the ports tree will definitely become broken on 4.x and older systems." "Therefore maintainers are also no longer required to provide any form of support for running their ports on FreeBSD 4.x, and may also remove any legacy support code at their convenience." Regardless of what the individual maintainers do to support 4.x, the build infrastructure will not support it much longer. This should definitely be taken as a "heads up" to upgrade ASAP. > > (I do intend to upgrade to 6.x at some stage, but not until a lot > of ports that I use start to fail to build, and there is no sign of > that happening yet :-) > > Regards > Andrew Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- pgpwfZpGnQ8t2.pgp Description: PGP signature
Re: php4 port - undefined ref to getopt_long
On Wed, Mar 14, 2007 at 12:37:48PM -0700, Chuck Swiger wrote: > Please be aware that FreeBSD 4.11 is no longer supported-- the ports > framework has been updated in a fashion which is no longer backwards > compatible with that version of the OS, so you're going to be rolling > your own software from here on out if you want to stay with that > version. I have a FreeBSD 4.10-REL system here with a still-working ports system, using the latest ports tree. Judging from your comment above, this is impossible, unless I've misunderstood you. Should ports maintainers still be encouraged to support 4.x if it is not a lot of trouble? Recently I've sent mail to two port maintainers with very minor patches to build ports on 4.x. (I do intend to upgrade to 6.x at some stage, but not until a lot of ports that I use start to fail to build, and there is no sign of that happening yet :-) Regards Andrew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Gfortran migration status is now `stablize'
On Wed, 14 Mar 2007, Maho NAKATA wrote: > According to http://people.freebsd.org/~maho/gfortran/gfortran.html , > gfortran migration is almost done. Congratulations! > After the stabilization period is over, we are planning to add a knob > like USE_FORTRAN=yes [gfortran42(default), gfortran43, ifort, g95, > gfortran41, f77, g77-34] and change the Makefile again for simpler > Makefile. This will be very welcome... > To do so, I must change some of /usr/port/Mk/*.mk files beforehand, and > I'll announce again when we are ready. ...and I will do my best to support you as far as I can there (as maintainer of Mk/bsd.gcc.mk)! Gerald ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why so many tcl's and tk's
On Wed, Mar 14, 2007 at 08:45:32PM +0100, Martin Tournoij wrote: > It seems most ports work fine with tcl84, and that tcl<84 deps are > historical rather than technical (no one looked if the ports works > with tcl84). There is probably some low-hanging fruit which can be fixed for free just by changing the dependency, but the last time I checked most of the ports that are still stuck on old versions are there for a reason (i.e. they do not build or run with the newer version). > Anyway, I started working on this. Great! Kris pgpzaxvf5ylWa.pgp Description: PGP signature
Re: Why so many tcl's and tk's
On Wed 14 Mar 2007 01:03, Kris Kennaway wrote: > On Tue, Mar 13, 2007 at 05:48:56PM -0500, Stephen Montgomery-Smith wrote: > > Kris Kennaway wrote: > > >On Tue, Mar 13, 2007 at 04:09:26PM -0500, Stephen Montgomery-Smith wrote: > > > > > >>Are the different versions of tcl and tk really not backwards compatible > > >>with earlier versions? > > > > > > > > >No, they are not. > > > > What a pity. So how come the various linux distributions seem to get > > away with only one version of tcl and tk? > > Probably the various incompatibilities are usually minor, so someone > with basic knowledge of tcl/tk can forward-port the legacy code to the > latest version. I'd be happy if someone were to do this for FreeBSD, > at least for the older tcl/tk versions. > > Kris It seems most ports work fine with tcl84, and that tcl<84 deps are historical rather than technical (no one looked if the ports works with tcl84). Anyway, I started working on this. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why so many tcl's and tk's
On Wed, Mar 14, 2007 at 07:26:25AM -0700, Garrett Cooper wrote: > >Are the different versions of tcl and tk really not backwards > >compatible with earlier versions? > No, they are not. > >>> > >>>What a pity. So how come the various linux distributions seem to > >>>get away with only one version of tcl and tk? > >> > >>Better versioning in their package infrastructure? > > > >Dunno what you mean by this. > > > >Kris > > Actually after doing a bit of research it appears that what I meant > in my reply is incorrect. From what I can see Linux uses a method of > branching with its tcl and tk packages similar to what FreeBSD does. > I know my sample size is small, but I'm pretty sure it's a defacto > standard if these two distros do the branch versioning that I see: > > Debian (scroll almost all the way to the bottom to find the tk refs): > - http://packages.debian.org/stable/libs/ > Gentoo: > - http://packages.gentoo.org/search/?sstring=tcl This makes better sense and is in line with what I would expect. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: Vpopmail + spamassassin doesn't work for aliases? - solved
Hi, AD> So .qmail-radek:krejca should become: AD> &[EMAIL PROTECTED] Thank you it works. In qmail appears anyway but in .qmail-* file is it different. -- Regards, Bc. Radek Krejca [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php4 port - undefined ref to getopt_long
On Mar 14, 2007, at 11:56 AM, timmartin wrote: this is all on freebsd 4.11 Please be aware that FreeBSD 4.11 is no longer supported-- the ports framework has been updated in a fashion which is no longer backwards compatible with that version of the OS, so you're going to be rolling your own software from here on out if you want to stay with that version. 1) a while back i stopped being able to make my own ports index because of a bunch of gstreamer-plugins that wouldn't let me "make index" so i started having to "make fetchindex" instead. Sometimes this happens when people don't download the entire, complete port tree. Other times, the dependency tree for the Index really is broken...normally, the committers will fix it shortly so re-updating your ports tree a day later will let you rebuild the index locally. It's a moot point now, however. 2) when i look at "portversion" outputs it seems as though it doesn't really know what versions are in the ports tree -- many ports have been updated and it doesn't seem to think so. When i ran portupgrade on said ports it worked just fine -- just portversion didn't know what was going on. Try running "pkgdb -Fu". 3) today i stopped being able to build php4 -- i get the following error that stops the upgrade: ext/standard/basic_functions.lo(.text+0x1507): undefined reference to `getopt_long' Anybody have an idea on how i can fix the situation? The only one that really sucks is the last problem -- the other two i can live with although it'd be nice to fix them too. getopt_long is part of the standard C library under 5.x and later, but is not present in 4.x. If you can't update to a more recent version of FreeBSD, try installing the /usr/ports/devel/libgnugetopt port and convince PHP to build against it. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php4 port - undefined ref to getopt_long
On Wednesday 14 March 2007 10:56, timmartin said: > First let me say I'm not a programmer, just a humble designer who > happens to know enough to make himself dangerous. Anyway, three > things started happening with my ports tree that make me unhappy. > They may be unrelated, but since I don't know i'll list all three. > > this is all on freebsd 4.11 > > 1) a while back i stopped being able to make my own ports index > because of a bunch of gstreamer-plugins that wouldn't let me "make > index" so i started having to "make fetchindex" instead. > > 2) when i look at "portversion" outputs it seems as though it > doesn't really know what versions are in the ports tree -- many > ports have been updated and it doesn't seem to think so. When i ran > portupgrade on said ports it worked just fine -- just portversion > didn't know what was going on. > > 3) today i stopped being able to build php4 -- i get the following > error that stops the upgrade: > > ext/standard/basic_functions.lo(.text+0x1507): undefined reference > to `getopt_long' > > Anybody have an idea on how i can fix the situation? The only one > that really sucks is the last problem -- the other two i can live > with although it'd be nice to fix them too. > > .tim On January 31st, FreeBSD 4.11 and earlier releases will have reached its End of Life dates and will no longer be supported by the FreeBSD Ports Team. Users are encouraged to upgrade to FreeBSD 6.2. Compatibility with 4.x has been removed from most of the ports. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
php4 port - undefined ref to getopt_long
First let me say I'm not a programmer, just a humble designer who happens to know enough to make himself dangerous. Anyway, three things started happening with my ports tree that make me unhappy. They may be unrelated, but since I don't know i'll list all three. this is all on freebsd 4.11 1) a while back i stopped being able to make my own ports index because of a bunch of gstreamer-plugins that wouldn't let me "make index" so i started having to "make fetchindex" instead. 2) when i look at "portversion" outputs it seems as though it doesn't really know what versions are in the ports tree -- many ports have been updated and it doesn't seem to think so. When i ran portupgrade on said ports it worked just fine -- just portversion didn't know what was going on. 3) today i stopped being able to build php4 -- i get the following error that stops the upgrade: ext/standard/basic_functions.lo(.text+0x1507): undefined reference to `getopt_long' Anybody have an idea on how i can fix the situation? The only one that really sucks is the last problem -- the other two i can live with although it'd be nice to fix them too. .tim -- View this message in context: http://www.nabble.com/php4-port---undefined-ref-to-getopt_long-tf3404132.html#a9481052 Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vpopmail + spamassassin doesn't work for aliases?
Bc. Radek Krejca ha scritto: In .qmail-radek:krejca I have this /usr/local/vpopmail/domains/2/starnet.cz/darius/Maildir/ You should modify your aliases to be forwards (as qmailadmin does). So .qmail-radek:krejca should become: &[EMAIL PROTECTED] -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: Vpopmail + spamassassin doesn't work for aliases?
Hi, AD> Yes and no. Only local Maildirs are checked. Aliases normally point to AD> local Maildirs, so they are checked in any case at a later stage. If you AD> have a forward to a remote address, then no checking is done. I don't think so or I have a problem. I have physical maildir darius created over qmailadmin. Then I have alias radek.krejca pointed to darius. Mail sended to radek.krejca isn't checked. In .qmail-radek:krejca I have this /usr/local/vpopmail/domains/2/starnet.cz/darius/Maildir/ -- Regards, Bc. Radek Krejca [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsnap and local patches
--On Tuesday, March 13, 2007 23:26:26 -0700 Nate Eldredge <[EMAIL PROTECTED]>
wrote:
Hi all,
portsnap is a very nice way to keep your ports tree in sync, but it has
the disadvantage that it keeps your ports tree in sync :) If you make
local changes (e.g. adding a patch) they get clobbered. Does anyone know
of a convenient way to keep ports up to date while preserving local
patches?
That's why God made shell scripting???
if [ -f ${port/path/mypatch} ]; then
cp $mypatch ${port/path/mypatch}
fi
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
Re: Vpopmail + spamassassin doesn't work for aliases?
Bc. Radek Krejca ha scritto: I have installed vpopmail port where you are maintainer. I check spamassassin patch, It works well but some e-mails aren't checked. It looks that only physical mailboxess are checked but aliases not. Is it possible? Yes and no. Only local Maildirs are checked. Aliases normally point to local Maildirs, so they are checked in any case at a later stage. If you have a forward to a remote address, then no checking is done. What may I change to test all e-mails? Don't use the vpopmail patch, but integrate SpamAssassin at the SMTP layer. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why so many tcl's and tk's
On Mar 13, 2007, at 10:47 PM, Kris Kennaway wrote: On Tue, Mar 13, 2007 at 06:46:48PM -0700, Garrett Cooper wrote: Begin forwarded message: From: Stephen Montgomery-Smith <[EMAIL PROTECTED]> Date: March 13, 2007 3:48:56 PM PDT To: freebsd-ports@freebsd.org Subject: Re: Why so many tcl's and tk's Kris Kennaway wrote: On Tue, Mar 13, 2007 at 04:09:26PM -0500, Stephen Montgomery-Smith wrote: Are the different versions of tcl and tk really not backwards compatible with earlier versions? No, they are not. What a pity. So how come the various linux distributions seem to get away with only one version of tcl and tk? Better versioning in their package infrastructure? Dunno what you mean by this. Kris Actually after doing a bit of research it appears that what I meant in my reply is incorrect. From what I can see Linux uses a method of branching with its tcl and tk packages similar to what FreeBSD does. I know my sample size is small, but I'm pretty sure it's a defacto standard if these two distros do the branch versioning that I see: Debian (scroll almost all the way to the bottom to find the tk refs): - http://packages.debian.org/stable/libs/ Gentoo: - http://packages.gentoo.org/search/?sstring=tcl -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsnap and local patches
On Wednesday 14 March 2007 02:12, Scot Hetzel wrote: > On 3/14/07, Nate Eldredge <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > portsnap is a very nice way to keep your ports tree in sync, but > > it has the disadvantage that it keeps your ports tree in sync :) > > If you make local changes (e.g. adding a patch) they get > > clobbered. Does anyone know of a convenient way to keep ports up > > to date while preserving local patches? > > One way to keep your local changes is to use cvs to checkout and > update the ports tree, you then make your modifications to the > port. > > You will need to fix any conflicts manually between an updated port > and your changes. > > Scot csup/cvsup has the nice feature of not touching files that shouldn't be there, so my solution to that problem is to create a new directory for my local changes, which csup/cvsup will nicely ignore. -- Thanks, Josh Paetzel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Vpopmail + spamassassin doesn't work for aliases?
Hi, I have installed vpopmail port where you are maintainer. I check spamassassin patch, It works well but some e-mails aren't checked. It looks that only physical mailboxess are checked but aliases not. Is it possible? What may I change to test all e-mails? Thank you Radek -- Regards, Bc. Radek Krejca STARNET, s. r. o. [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why so many tcl's and tk's
Stephen Montgomery-Smith wrote / napísal(a): > Are the different versions of tcl and tk really not backwards > compatible with earlier versions? I can guess that there have been > heated conversations about this, but a my look at the mailing list > archives didn't give me anything. But it sure would be much nicer if > there was just a tcl and a tcl-devel port or something like that. Are > there really applications that need tcl83 but break on tcl84? > > Stephen > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" The various Tcl and Tk versions do have incompatible changes in the interfaces and in the command syntax. It is very much like Berkeley DB - you have several versions, too. You have to rewrite your program to support more (or newer) Tcl versions. The idea on the current implementation in the FreeBSD ports tree is to stay compatible with older tcl scripts and libraries, too. But the structure of the supporting bsd.tcl.mk is very old and does not suit the needs of current applications anymore. Another recent issue is the handling of threaded and non-threaded versions of Tcl 8.4 and 8.5. The current implementation ist just a workaround, so that applications that explicitly require a threaded Tcl build can use it. A threaded Tcl build is 100% compatible to a non-threaded Tcl. As far as I know, threaded Tcl 8.4 builds and runs on all common FreeBSD architectures. A very clean and good solution would to have a threaded Tcl only. I will test this against all libraries from the FreeBSD ports that extend Tcl to check if they work with the threaded version correctly. I am working with miwi@ on a new implementation of bsd.tcl.mk A first working version can be viewed under: http://www.matuska.org/martin/cgi/viewvc.cgi/ports/Mk/bsd.tcl.mk The final version will probably be different - the threading part might be removed completely in favour of using threaded tcl by default. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Gfortran migration status is now `stablize'
Dear maintainers (who uses/have used FORTRAN in your ports) According to http://people.freebsd.org/~maho/gfortran/gfortran.html , gfortran migration is almost done. Except for ports/science/hdf, and still there are some build issues. I'd like to move the status to stabilize and wait for ~one month. After the stabilization period is over, we are planning to add a knob like USE_FORTRAN=yes [gfortran42(default), gfortran43, ifort, g95, gfortran41, f77, g77-34] and change the Makefile again for simpler Makefile. To do so, I must change some of /usr/port/Mk/*.mk files beforehand, and I'll announce again when we are ready. Discussion for changes are very welcome. BTW: I'll be unavailable until mid of April. I'm too busy in these days. Hope I can answer your e-mails immediately. Greg: your port is broken for FreeBSD 7, so we should add something...but I as wrote, your port doesn't build for me. So I cannot check. Help is really appreciated. Many thanks for your patience, and cooperation. All the best, -- Nakata Maho ([EMAIL PROTECTED]) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
