Re: Bundling Kwiki
Hi, Quote from http://search.cpan.org/src/INGY/Kwiki-0.39/README Kwiki is *really* simple to install now. _All_ the Perl dependencies come with Kwiki, and are /preinstalled/. This means you just need Perl 5.8.3 and a web server. Well actually we give you a web server too!... ... ... Eventually all this work will make it back to CPAN, but likely not for a while. The kwiki-trunk-*.tar.gz already do so (bundling almost every plugin) I think I'd better take off these plugins from ports tree before 'Ingy dot net' put them back. Just IMHO. :-) On Mon, Apr 23, 2007 at 09:57:44AM +0400, Andrew Pantyukhin wrote: First of all, thanks for taking up the initiative and updating Kwiki. It's a worthy project. Do we want to bundle Kwiki into a single port? In ports we usually consider bundling (of any software project) a harmful thing, as opposed to modularizing. I haven't looked at those new Kwiki snapshots, but is it too hard to update all those p5-Kwiki-* ports instead of merging them into the main one? Never mind if it's too much work... Thanks! -- Alan Cheng-Lung Sung - clsung@ pgprWfwH7irIk.pgp Description: PGP signature
Re: Bundling Kwiki
On 4/23/07, Cheng-Lung Sung [EMAIL PROTECTED] wrote: Hi, Quote from http://search.cpan.org/src/INGY/Kwiki-0.39/README Kwiki is *really* simple to install now. _All_ the Perl dependencies come with Kwiki, and are /preinstalled/. This means you just need Perl 5.8.3 and a web server. Well actually we give you a web server too!... ... ... Eventually all this work will make it back to CPAN, but likely not for a while. The kwiki-trunk-*.tar.gz already do so (bundling almost every plugin) I think I'd better take off these plugins from ports tree before 'Ingy dot net' put them back. Just IMHO. :-) That *really* simple was directed to poor Linux/Solaris admins, who mostly have to install everything manually. Bundles are evil :-) It's your call, of course, and considering the devs aren't going to push the stuff back to CPAN for a while, it seems you've made the right choice. Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports 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. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems Serious problems S Tracker Resp. Description o ports/105549ports/www/squid_radius_auth doesn't work on sparc64 o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode o ports/107536editors/scite: Can't write on SciTE text editor f ports/108077www/linux-flashplugin9 crashes linux-firefox f ports/108105building biology/platon fails. f ports/108413net/vnc does not works. f ports/108537print/hplip: Build failure f ports/108606Courier MTA terminates abnormaly after installation f ports/108748mod_fcgid 1.10 does not work inside jail f ports/109160net/samba3 crashes freebsd when accessing a share resi f ports/110035Port fix for sysutils/be_agent f ports/110454Joomla port Makefile has incorrect url for package f ports/110767[UPDATE]java/jboss3:update to jboss3.2.8 f ports/110768[UPDATE]java/jboss4:fix some FATAL error noticed by po o ports/110932[NEW PORT]geronimo:open source j2ee 5 application serv f ports/110943start-dccifd chowns /var/run to user dcc f ports/111012quagga's ripd does not see ng interfaces f ports/51ports/lang/stklos: l/bin/stklos-install is a buggy she o ports/111224 ports [PATCH] security/pam_per_user conflicts with security/ f ports/111338graphics/yafray: doesn't respect CXX, CXXFLAGS and eve f ports/111462syslog-ng2 default configuration file path o ports/111480emulators/vmware3 port crashes under FreeBSD 6.2 o ports/111923databases/unixODBC overwrites config file on package i f ports/111966Clamav-milter no up f ports/111980multimedia/mplayer: compilation error 26 problems total. Non-critical problems S Tracker Resp. Description s ports/59254 ports that write something after bsd.port.mk o ports/94921 isakmpd fails on amd64 o ports/95854 New Port: www/ochusha s ports/96731 textproc/docbook-utils doesn`t build o ports/100896[new ports] emulators/vmware-server-guestd1 emulators/ o ports/101275bug fixed in sudo that prevented use in LDAP user acco o ports/103395security/gnome-ssh-askpass interferes with gnome-scree o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM f ports/107368audio/normalize: [patch] - normalize-mp3 and normalize f ports/107621net/proxychains doens't compile on 4 and 5 f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut f ports/108104print/hplip: documentation gets installed though NOPOR o ports/108595pstree (sysutils/psmisc) don't work in jail f ports/108723kxgenerator never worked for me f ports/108788[patch] sysutils/fusefs-kmod: Add BASE option f ports/108801www/mod_perl2: Apache-2.0.59 / mod_perl-2-2.0.3_1 freq f ports/108853Contradiction of CONFLICTS¡¡ f ports/109041security/tinyca doesn't allow for user installed OpenS f ports/109045security/xca compile fails: x509rev.cpp:63: error: inv o ports/109344restore .svn support to security/metasploit-devel f ports/109535Eggdrop SSL error o ports/110144New port: math/Matlab7 f ports/110320[security/vpnc] rc script
Re: Mailman GID problem
Jeffrey Goldberg wrote:
On Apr 20, 2007, at 9:26 PM, Paul Schmehl wrote:
--On April 20, 2007 7:54:45 PM -0500 Jeffrey Goldberg
[EMAIL PROTECTED] wrote:
So the first fix (modifying the owner of data/aliases{,.db}) is the
right way to go, but instead of making those files owned by nobody
(which does seem dangerous because than anything running as nobody
could change those file) they should be owned by root with mailman as
the group and permissions like 664.
Nobody is an unprivileged user.
Thank you. I forgot about that. I was treating nobody like www or
mail. It entirely slipped my mind that nobody really is different.
it would break to ownership of the aliases file so that we would have
the mismatch between what the uid postfix gives the the wrapper
(mailman) and what the wrapper demands (nobody).
Nope. I've been running mailman for years now, and it works perfectly
fine. The owner of the data directory is mailman, and the group is
mailman.
ls -lsa /usr/local/mailman/data/
total 132
2 drwxrwsr-x 2 mailman mailman512 Apr 7 19:47 .
2 drwxrwsr-x 20 mailman mailman512 Nov 28 17:48 ..
48 -rw-r--r-- 1 mailman mailman 65536 Sep 6 2005 .db
2 -rw-r- 1 mailman mailman 41 Sep 6 2005 adm.pw
6 -rw-r--r-- 1 root mailman 4383 Oct 14 2005 aliases
4 -rw-r- 1 mailman mailman 3984 Sep 8 2005 aliases.bak
48 -rw-r- 1 mailman mailman 49152 May 5 2006 aliases.db
0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005
bounce-events-00446.pck
0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005
bounce-events-00449.pck
0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005
bounce-events-00467.pck
0 -rw-rw-rw- 1 mailman mailman 0 Jan 27 2006
bounce-events-00567.pck
0 -rw-rw-rw- 1 mailman mailman 0 Oct 13 2005
bounce-events-38840.pck
2 -rw-r- 1 mailman mailman 41 Sep 6 2005 creator.pw
2 -rw-r--r-- 1 root mailman 10 Nov 28 17:48
last_mailman_version
2 -rw-rw 1 mailman mailman 4 Apr 1 08:31 master-qrunner.pid
14 -rw-r--r-- 1 root mailman 14114 Nov 28 17:48 sitelist.cfg
I am fairly confident that if that is working for you, than you are not
running with /usr/local/mailman/mail/mailman that was compiled with the
current port with the postfix option set. The binary mailman has a gid
compiled into it. Given the current port WITH_POSTFIX.
Installing the current port WITH_POSTFIX will produce a mailman binary
which will only allow itself to be run by nobody. Yours must have
mailman compiled in where nobody is in what I (and David) get.
[EMAIL PROTECTED] /usr/local/mailman/mail]$ strings mailman | tail
leave
post
owner
request
unsubscribe
Mailman mail-wrapper
nobody
Illegal command: %s
Usage: %s program [args...]
$FreeBSD: src/lib/csu/i386-elf/crtn.S,v 1.6 2005/05/19 07:31:06 dfr Exp $
What is your result on your system? If you get mailman where I have
nobody then one of my earlier suggestions (change MAIL_GID for the
postfix setting from nobody to mailman in the port Makefile) may be
the right thing. That is what is most consistent with the mailman
install instructions.
From /usr/local/share/doc/mailman/mailman-install.txt
In section 6.1.1 Integrating Postfix and Mailman
* When you configure Mailman, use the --with-mail-gid=mailman
switch;
However, the current ports Makefile compiles mailman --with-mail-gid=nobody
The same section also says
Make sure that the owner of the data/aliases and data/aliases.db
file is mailman, that the group owner for those files is mailman,
or whatever user and group you used in the configure command, and
that both files are group writable:
% su
% chown mailman:mailman data/aliases*
% chmod g+w data/aliases*
It is the *group* that matters to postfix, *not* the owner. Per the
pkg-message file:
Mailman has been installed, but requires further configuration before
use!
You will have to configure both your MTA (mail server) and web server to
integrate with Mailman. If the port's documentation has been installed,
extensive post-installation instructions may be found in:
%%DOCSDIR%%/FreeBSD-post-install-notes
Note (1): If you use an alternate (non-Sendmail) MTA, you MUST be sure
that the correct value of MAIL_GID was used when this port or package
was built. Performing a make options in the Mailman port directory
will list required values for various mail servers.
Note that MAIL_GID is what matters. That is the *group* not the owner
of the files. Note also that the group only has read writes to the
aliases file, although it does have read/write access to the
bounce-events files.
However it is the owner of the file containing the pipe alias that
matters to postfix local deliveries. See local(8).
So maybe the problem is with check_perms and not with the port at all
(well the port
Greylisting - postgrey
Hi I wonder if someone could be kind enough to post examples of the entries required in relevant configuration files to implement postgrey on mailserver having a number of virtual mail hosts and for which it also supports mailman for a number of virtual apache hosts. Please bear in mind I am very new to postfix, mailman postgrey chuckles thanks in advance david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ports apache22 stupid quitestion.
Sorry for my stupid question, but after googling I wan't able to find it. How can I set default build options for www/apache22 ports, because I build it with_mpm=worker and when I do make package-recursive on php or some other dependent port it builds default prefok, not worker apache and it breaks all my packages. (I know I can pass with_mpm=worker on make package-recursive but I often forget). thanks very much! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports apache22 stupid quitestion.
You might set it in make.conf(5), but apache22 doesn't seem to use /var/db/ports/apache22/options. In either case, regardless, you'd still be replicating a file across all of the systems that you wish to remain homogeneous. ~BAS On Mon, 2007-04-23 at 18:33 +0300, Anton - Valqk wrote: because I build it with_mpm=worker and when I do -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports apache22 stupid quitestion.
On 4/23/07, Anton - Valqk [EMAIL PROTECTED] wrote: Sorry for my stupid question, but after googling I wan't able to find it. How can I set default build options for www/apache22 ports, because I build it with_mpm=worker and when I do make package-recursive on php or some other dependent port it builds default prefok, not worker apache and it breaks all my packages. (I know I can pass with_mpm=worker on make package-recursive but I often forget). Install ports-mgmt/portconf, and then add WITH_MPM=worker to PREFIX/etc/ports.conf. # cat PREFIX/etc/ports.conf www/apache22: WITH_MPM=worker | WITH_LDAP | WITH_THREADS Portsconf allows you to set defaults for ports that can be used by any of the ports management tools (portmaster, portupgrade, .., cd /usr/ports/to/install ; make install) Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeMat 3.0 doesn't call functions and help
Il Sunday 22 April 2007 21:38:12 Thierry Thomas ha scritto: Le Jeu 19 avr 07 à 1:00:38 +0200, Vittorio De Martino [EMAIL PROTECTED] écrivait : I have just upgraded FreeMAT to 3.1, which fixes the inv() problem, and which should fix this Help on line bug too; could you please check it? Yes, with the new version 3.1 inv now works fine. Unfortunately the Help on line still doesn't work. I think that something worsened because with this new port now I cannot use the help on line even as root (in the previous version Help online as root worked quite well). Could you please script (1) a session with only `truss FreeMat', just calling the help and exiting? Then please send me the compresed log of this session. If you had created some symlinks, please don't forget to remove them. Regards, I cannot truss anything victor# truss /bin/echo hello truss: cannot open /proc/curproc/mem: No such file or directory any other solution or workaround? Vittorio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeMat 3.0 doesn't call functions and help
Il Sunday 22 April 2007 21:38:12 Thierry Thomas ha scritto: Le Jeu 19 avr 07 à 1:00:38 +0200, Vittorio De Martino [EMAIL PROTECTED] écrivait : I have just upgraded FreeMAT to 3.1, which fixes the inv() problem, and which should fix this Help on line bug too; could you please check it? Yes, with the new version 3.1 inv now works fine. Unfortunately the Help on line still doesn't work. I think that something worsened because with this new port now I cannot use the help on line even as root (in the previous version Help online as root worked quite well). Could you please script (1) a session with only `truss FreeMat', just calling the help and exiting? Then please send me the compresed log of this session. If you had created some symlinks, please don't forget to remove them. Regards, I cannot truss anything victor# truss /bin/echo hello truss: cannot open /proc/curproc/mem: No such file or directory any other solution or workaround? Vittorio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeMat 3.0 doesn't call functions and help
Vittorio De Martino [EMAIL PROTECTED] wrote: Il Sunday 22 April 2007 21:38:12 Thierry Thomas ha scritto: Le Jeu 19 avr 07 à 1:00:38 +0200, Vittorio De Martino [EMAIL PROTECTED] écrivait : I have just upgraded FreeMAT to 3.1, which fixes the inv() problem, and which should fix this Help on line bug too; could you please check it? Yes, with the new version 3.1 inv now works fine. Unfortunately the Help on line still doesn't work. I think that something worsened because with this new port now I cannot use the help on line even as root (in the previous version Help online as root worked quite well). Could you please script (1) a session with only `truss FreeMat', just calling the help and exiting? Then please send me the compresed log of this session. If you had created some symlinks, please don't forget to remove them. Regards, I cannot truss anything victor# truss /bin/echo hello truss: cannot open /proc/curproc/mem: No such file or directory any other solution or workaround? truss needs procfs: mount_procfs /dev/mem /proc Fabian signature.asc Description: PGP signature
FreeBSD Port: gotmail-0.8.9
Receive this error message when running GotMail Can't exec curl: No such file or directory at /usr/local/bin/gotmail line 677. Use of uninitialized value in concatenation (.) or string at /usr/local/bin/gotmail line 677. curl: not found Could not open /var/tmp/tmp.3.pnPErXgotmail_curlstderr35146 : No such file or directory at /usr/local/bin/gotmail line 774. Curl is installed ,any ideas what is causing this? Thanks -- Darrell [EMAIL PROTECTED] -- Looks like I Picked the Wrong Week to Stop Sniffing Glue. -- Steve McCroskey -- Live ATC Feed from Toledo Express Airport http://audio.liveatc.net:8012/ktol.m3u ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port needing security/py-m2crypto built with OpenSSL =0.9.8
Hallo Alejandro Pulver, I am making ports for two bittorrent clients based on the ABC one. Both needing py-m2crypto compiled with OpenSSL =3D 0.9.8. In my FreeBSD 6.2-RELEASE, for example, I have OpenSSL 0.9.7.x and the py-m2crypto port now uses the one in the base system, so the ports won't work. Apparently there are 2 ports which use it: net-im/cjc and net-im/py-pyxmpp (by default, not considering optional dependencies). What would be the best solution? Make it always use the port? I liket to suggest you make a slave port of py-m2crypto which use the port. Apps are in trouble when they are not linked against the same version. so each App should be linked with openssl he same way as its dependencies. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED] http://people.freebsd.org/~dinoex/errorlogs/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports apache22 stupid quitestion.
Thanks a lot! works just great! Scot Hetzel wrote: On 4/23/07, Anton - Valqk [EMAIL PROTECTED] wrote: Sorry for my stupid question, but after googling I wan't able to find it. How can I set default build options for www/apache22 ports, because I build it with_mpm=worker and when I do make package-recursive on php or some other dependent port it builds default prefok, not worker apache and it breaks all my packages. (I know I can pass with_mpm=worker on make package-recursive but I often forget). Install ports-mgmt/portconf, and then add WITH_MPM=worker to PREFIX/etc/ports.conf. # cat PREFIX/etc/ports.conf www/apache22: WITH_MPM=worker | WITH_LDAP | WITH_THREADS Portsconf allows you to set defaults for ports that can be used by any of the ports management tools (portmaster, portupgrade, .., cd /usr/ports/to/install ; make install) Scot -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printable Porters' Handbook ghostscript-gpl-nox11 problem
On Monday 23 April 2007 03:26:05 pm Jeffrey Goldberg wrote: I would like to get a printable (US letter) copy of the Porters' Handbook (pdf, ps, or even dvi). It didn't seem to come on 6.2 RELENG except as HTML and plain text. You can find in several printable formats here: ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook David -- The new Congressmen say they're going to turn the government around. I hope I don't get run over again. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeMat 3.0 doesn't call functions and help
Il Monday 23 April 2007 18:10:44 Fabian Keil ha scritto: Vittorio De Martino [EMAIL PROTECTED] wrote: Il Sunday 22 April 2007 21:38:12 Thierry Thomas ha scritto: Le Jeu 19 avr 07 à 1:00:38 +0200, Vittorio De Martino [EMAIL PROTECTED] écrivait : I have just upgraded FreeMAT to 3.1, which fixes the inv() problem, and which should fix this Help on line bug too; could you please check it? Yes, with the new version 3.1 inv now works fine. Unfortunately the Help on line still doesn't work. I think that something worsened because with this new port now I cannot use the help on line even as root (in the previous version Help online as root worked quite well). Could you please script (1) a session with only `truss FreeMat', just calling the help and exiting? Then please send me the compresed log of this session. If you had created some symlinks, please don't forget to remove them. Regards, I cannot truss anything victor# truss /bin/echo hello truss: cannot open /proc/curproc/mem: No such file or directory any other solution or workaround? truss needs procfs: mount_procfs /dev/mem /proc Fabian I'm attaching the truss logfile obtained as a generic user issuing truss FreeMat, calling the Help online and exiting. Ciao Vittorio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: apache-2.2.4_2
Hi, Clement. I was wondering if you can point me to documentation about the profiles feature of apache. I've looked around the docs at http://httpd.apache.org, put Google to work for me, and asked on a couple of lists, but it appears this is kind of a secret feature, and maybe unique to the FreeBSD port. I've figured out enough to see that adding apache22_profiles=profile1 profile2 to /etc/rc.conf will start the process, and I suppose I could brute-force my way through figuring out how it should work, but I hoped you could point me to some kind of documentation on the feature, perhaps with some examples of how it was intended to be used. Specifically, I'm thinking this feature may make it easier for me to run two copies of apache: one hosting Bugzilla sites, another with WebDAV enabled for Subversion, using different users with mutually exclusive permissions. (The O'Reilly Apache Cookbook suggests running separate instances is a really good idea with DAV involved.) Thanks for any pointers you can give me. -- Bruce Wilson [EMAIL PROTECTED] PGP KeyID: 5430B995, http://www.toomuchblue.com/ “There are two ways to write error-free programs. Unfortunately, only the third one works.” ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: apache-2.2.4_2
Bruce Wilson wrote: Hi, Clement. I was wondering if you can point me to documentation about the profiles feature of apache. I've looked around the docs at http://httpd.apache.org, put Google to work for me, and asked on a couple of lists, but it appears this is kind of a secret feature, and maybe unique to the FreeBSD port. I've figured out enough to see that adding apache22_profiles=profile1 profile2 I kind of had to guess too. ## httpd 2.2.x apache22_enable=YES apache22_http_accept_enable=YES apache22_profiles=www ssl mp php python ruby apache22_www_flags=-DSQL apache22_www_configfile=/usr/local/etc/apache22/httpd.conf apache22_ssl_flags=-DSSL -DSQL apache22_ssl_configfile=/usr/local/etc/apache22/httpd.conf apache22_mp_flags=-DSQL -DMP2 apache22_mp_configfile=/usr/local/etc/apache22/httpd.conf I'd be willing to take a stab at documenting it but I don't have time at the moment. -- Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708 Consultant / http://p6m7g8.net/Resume/resume.shtml Senior Software Engineer - TicketMaster - http://ticketmaster.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
security/gnupg seems to need security/pinentry
Hello, I've updated GnuPG to latest version (2.0.3) from ports, and it stopped working until I installed security/pinentry. This is what it was displaying prior to installing pinentry: % gpg --clearsign configure bla Warning: using insecure memory! You need a passphrase to unlock the secret key for user: ... 1024-bit DSA key, ID ..., created 2004-07-05 gpg-agent[86284]: can't connect server: `ERR 67109133 can't exec `/usr/local/bin/pinentry': No such file or directory' gpg-agent[86284]: can't connect to the PIN entry module: IPC connect call failed gpg-agent[86284]: command get_passphrase failed: No pinentry gpg: problem with the agent: No pinentry gpg: no default secret key: General error gpg: configure: clearsign failed: General error Exit 2 security/pinentry is not a requisite for security/gnupg. Should it be? Regards. ps: please keep me in Cc:, as I'm not subscribed to this list. -- Ricardo Nabinger Sanchez [EMAIL PROTECTED],wait4.org} Powered by FreeBSD Left to themselves, things tend to go from bad to worse. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
setting ENV VARs in make.conf/ports.conf ?
hi,
i've installed FreeBSD v6.2-RELEASE, plus 'portconf' 'ccache' from ports.
i've setup,
/etc/make.conf
-
PERL_VER=5.8.8
PERL_VERSION=5.8.8
USE_OPENSSL_PORT=true
OPENSSLBASE=/usr/local
USE_OPENSSH_PORT=true
WITHOUT_X11=yes
CPUTYPE?=pentium-mmx
CFLAGS= -O2 -pipe
COPTFLAGS= -O2 -pipe
## Begin portconf settings
## Do not touch these lines
.if !empty(.CURDIR:M/usr/ports*) exists(/usr/local/libexec/portconf)
_PORTCONF!=/usr/local/libexec/portconf
.for i in ${_PORTCONF:S/|/ /g}
${i:S/%/ /g}
.endfor
.endif
## End portconf settings
.if !defined(NOCCACHE)
CC=/usr/local/libexec/ccache/cc
CXX=/usr/local/libexec/ccache/c++
CPP=/usr/local/libexec/ccache/cpp
.endif
-
so that i can turn OFF use of ccache for individual ports.
i find that different ports 'respond' only to specific ways of setting
the NOCCACHE var.
e.g., in,
cat /usr/local/etc/ports.conf
-
*:\
CFLAGS= -O2 -pipe -funroll-loops -s -frename-registers
-fomit-frame-pointer | \
CXXFLAGS= -O2 -pipe -funroll-loops -s -frename-registers
databases/sqlite3-threads:NOCCACHE=true | \
WITHOUT_DEBUG=true|WITH_DOCS=true|WITH_FTS1=true|WITH_TCLWRAPPER=true|BATCH=Yes
sysutils/pflogx:MAKE_ENV= NOCCACHE=true | \
WITH_EXPAT=true|BATCH=Yes
-
pflogx and sqlite3 require DIFFERENT specifications of NOCCACHE ...
swapping formate, e.g., causes the conditional .if
!defined(NOCCACHE) to fail; meaning, that the CC/CXX/CPP defs
pointing to ccahce/* are oncorrectly used.
is this expected/normal? i would've expected the same method of
defining ENV VAR knobs ...
is there a _consistent_ way of turning off NOCCACHE via the ports.conf?
thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
