Dealing with an external manpage
I was successful at creating the manpage for the port i'm working on. My problem is I'm not sure how to install it. The porter's Handbook wasn't much help. The manpage is in files and I need to compress and install it in man8 like a normal manpage from workdir, I'm just not sure what to put in the makefile. Could someone give me a hand here? Most of the examples I found dealt with extra docs. Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | Alaska Paradise Travel \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpHGPvOYkDa1.pgp Description: PGP signature
Re: Dealing with an external manpage
> I was successful at creating the manpage for the port i'm working on.
> My problem is I'm not sure how to install it. The porter's Handbook
> wasn't much help. The manpage is in files and I need to compress and
> install it in man8 like a normal manpage from workdir, I'm just not
> sure what to put in the makefile. Could someone give me a hand here?
> Most of the examples I found dealt with extra docs.
Have a look at ${INSTALL_MAN}. Take ports/dns/sshfp as an example.
HTH
Emanuel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dealing with an external manpage
Beech Rintoul wrote: > I was successful at creating the manpage for the port i'm working on. My > problem is I'm not sure how to install it. The porter's Handbook wasn't much > help. The manpage is in files and I need to compress and install it in man8 > like a normal manpage from workdir, I'm just not sure what to put in the > makefile. Could someone give me a hand here? Most of the examples I found > dealt with extra docs. Check out sysutils/portmaster/Makefile. hth, Doug -- This .signature sanitized for your protection ___ 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 S Tracker Resp. Description f ports/106007proftpd security bugs f ports/106594ftp/tnftpd - fix critical bug o ports/106595[xmms-avi] [patch] xmms-avi does not compile - patch f o ports/106596[xmms-avi] [patch] xmms-avi does not compile - patch f o ports/106597[xmms-avi] [patch] xmms-avi does not compile - patch f o ports/106598[xmms-avi] [patch] xmms-avi does not compile - patch f 6 problems total. Serious problems S Tracker Resp. Description f ports/92706 vmware3 panic on 6.0-RELEASE o ports/94894 multimedia/fxtv causes freeze and reboot on DGA failur f ports/95081 Problem with enabling logwtmp on POPtop s ports/99623 ksh93 dumps core on FBSD 6.1 f ports/100067New port: devel/gdb65 GNU GDB 6.5 o ports/100358sysutils/portmanager: OpenOffice.org 2.0 Requires Conf f ports/103367pglogd fails to start f ports/103672cups-base wont compile/nor is it capable of being port f ports/103970print/cups-base will not install f ports/104546net/nss_ldap bug f ports/104769tcllib-1.7_1 won't build anymore in FreeBSD 6.2-BETA2/ o ports/106547[UPDATE]: mambo 4.5.4 to 4.6.1 (big update and securit 12 problems total. Non-critical problems S Tracker Resp. Description s ports/57502 ports that define USE_* too late s ports/59254 ports that write something after bsd.port.mk s ports/67815 graphics/ImageMagick no longer recognizes FlashPix s ports/88900 www/flashplugin-mozilla causes Firefox to crash f ports/95019 New port: www/suphp-devel: suPHP 0.6.1 f ports/95279 (New Port) FreeBPX: a web gui to the asterisk PBX f ports/95990 New Port: emulators/xjoypad s ports/96576 R 2.3.0 fails to compile: undefined reference to `R_ru s ports/96731 textproc/docbook-utils doesn`t build f ports/96891 [patch] port dns/powerdns does not have option for com f ports/99535 New port: mail/qmail-scanner2 qmail-scanner2 with st p f ports/99553 cannot use proxy in net-im/gaim-openq f ports/100650audio/moc dumps core when detach/quit f ports/100789net-p2p/verlihub-plugins: compile failure o ports/100896[new ports] emulators/vmware-server-guestd1 emulators/ o ports/101423[NEW PORT] ruby/ruby18-doc-stdlib: Documentation for R o ports/101680mail/poppassd: update of passwd prompts for pam_passwd f ports/102093new port (restoring from Attic): fix games/myth2_demo o ports/103395gnome-ssh-askpass interferes with gnome-screensaver f ports/103813www/p5-Apache-DBI: fix package dependenies when WITH_M f ports/104033nagios trends report images wrong size f ports/104234net/linneighborhood: Problem with mounting a smb share o ports/104453[NEW PORT] russian/proftpd f ports/104498missing entries in ports/multimedia/pvrxxx/distinfo o ports/104680New port: emulators/linux_base-slackware - Slackware b s ports/104725request new port: x11/nvidia-driver-devel f ports/104754/ports/chinese/stardict2-dict-zh_CN place files to wr f ports/104779update cad/varkon to 1.18A f ports/104997
Re: Update on X11BASE status
On Sun, Dec 03, 2006 at 09:28:40PM +0800, Rong-En Fan wrote: > > > > http://pointyhat.freebsd.org/errorlogs/i386-5-exp-latest/index-maintainer.html > > > > We're now down to fewer than 110 ports that need to be corrected to > > deal with a non-standard X11BASE location (the rest are more general > > port problems). By now only 17 of those broken ports are > > unmaintained, so the majority of them are waiting on individual > > maintainers to step up and/or approve fixes already submitted by other > > users. > > One major problem I encountered so far is math/vtk* and > science/paraview. They all uses CMake system (devel/cmake). > > I'm not quite sure what's the best way to make its makefile accepts > correct X11BASE. One possibility is to patch its FindX11 module, but > it seems to me that these ports contain their CMake/ in their > distribution, i.e., we need to patch each ports. > > Any cmake experts? I fixed cmake yesterday. Now vtk* ports should be just fine. Regards, Rong-En Fan pgpwGaYpxQTH2.pgp Description: PGP signature
Re: FreeBSD Port: unrar-3.60,4
On Mon, Dec 11, 2006 at 10:29:37AM +0800, Chun-Tien Chang (?i?g??) wrote: > I found that LC_ALL is not working well in unrar with some charset like > (zh_TW.Big5, zh_CN.GBK, zh_CN.GB2312,zh_CN.eucCN) Please contact Rar author on this issue. There may be some security considerations in just disabling IsNameUsable. > > +if (WideToChar(ArcFileNameW,Name)/* && IsNameUsable(Name)*/) > -- http://ache.pp.ru/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [CFR] ftp/curl update and API incompatibility
On Fri, Dec 08, 2006 at 08:24:25PM +0200, Peter Pentchev wrote: > On Fri, Dec 08, 2006 at 07:57:59PM +0200, Peter Pentchev wrote: > > On Wed, Dec 06, 2006 at 02:56:57PM +0200, Peter Pentchev wrote: > > > Hi, > > > > > > I'm writing to you all because you are listed as maintainers of ports > > > that depend directly on ftp/curl. Attached is a patch that updates > > > ftp/curl to version 7.16.0; however, this update might need some testing. > > > > After some comments from some of the maintainers, here's an updated > > version of the patch, which also takes care of the ports that do not > > specify a shared library version in the curl dependency (i.e. they depend > > on "curl", not "curl.3"). This patch also: > > - bumps the PORTREVISION of the ftp/php4-curl, ftp/php5-curl, and > > www/pecl-pecl_http ports; > [snip] > > And of course, as Alex Dupre kindly pointed out, the PORTREVISION on > php5-curl should be 1, not 2. Updated curl-16-03.patch available at > http://people.FreeBSD.org/~roam/patches/curl/ Now, for final testing, curl-16-04.patch is available at http://people.FreeBSD.org/~roam/patches/curl/ It includes some catching-up with recent updates to astro/gaia (it compiles fine now), audio/herrie, audio/xmms2, comms/xastir, security/gnupg, and textproc/libnxml, as well as a fix to the (also updated) textproc/raptor so that the configure script actually uses curl-config --cflags and realizes that libcurl is, indeed, installed. If there are no objections, I'll commit the cURL update (and this patch) tomorrow. G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 What would this sentence be like if it weren't self-referential? pgptMBShEIGvc.pgp Description: PGP signature
failure of policy
It seems that the change log on freshports for the databases/slony1 port shows that someone somewhere is confused as to who's the maintainer of the port. The Makefile clearly shows it is still me. On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to 1.2.0 which had known errors in it which cause data loss. Somehow it was applied. A few days later a manual patch was added to work around that. The initial update indicates that whomever submitted the port was either claiming to be or was assumed to be the maintainer. Then on 8 Dec 2006, another update was issued and applied, to 1.2.1. Today I saw in my email a patch to correct some error in the pkg- plist file, which is how I noticed that someone had updated the slony1 port. This is not how it is supposed to work. I should have gotten these notices on *every* PR submitted with a patch against this port. There is no reason that 1.2.0 should have *ever* hit the ports tree as it was broken out of the gate. This is one of the reason ports have maintainers: to ensure broken things don't get thrown into the collection. If the committers are not going to follow the rules, then why should anyone bother to be a maintainer? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: failure of policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 11 Dec 2006 11:23:09 -0500 Vivek Khera <[EMAIL PROTECTED]> wrote: > It seems that the change log on freshports for the databases/slony1 > port shows that someone somewhere is confused as to who's the > maintainer of the port. The Makefile clearly shows it is still me. Sorry, it was definietly my fault. I thought its a maintainer-timeout case. It was my mistake and I hope you forgive me for this mistake. > > On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to > 1.2.0 which had known errors in it which cause data loss. Somehow > it was applied. A few days later a manual patch was added to work > around that. The initial update indicates that whomever submitted > the port was either claiming to be or was assumed to be the > maintainer. For this update of 1.2.0 gives a pr show here http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/105575 here is my mistake thats commit is after 7 days not 14 days. This is my mistake right. After this commit, I received a private email with a bugfix. Description of the problem: http://gborg.postgresql.org/project/slony1/bugs/bugupdate.php?1591 Then I committed a fix for this problem. Yes without approval from maintainer then i forgot to double check the maintainer mail. > Then on 8 Dec 2006, another update was issued and applied, to 1.2.1. Yes here telling me the self People with a patch of 1.2.1, i check this on my tinderbox this build fine and committed this. Yes I looked not yet on more maintainer mail. > > Today I saw in my email a patch to correct some error in the pkg- > plist file, which is how I noticed that someone had updated the > slony1 port. > > This is not how it is supposed to work. I should have gotten these > notices on *every* PR submitted with a patch against this port. > There is no reason that 1.2.0 should have *ever* hit the ports tree > as it was broken out of the gate. This is one of the reason ports > have maintainers: to ensure broken things don't get thrown into the > collection. > > If the committers are not going to follow the rules, then why should > anyone bother to be a maintainer? I could say this is all my fault a concatenation of stupid mistakes :( I hope you forgive me for this mistake. - - Martin - -- Martin Wilke| irc.unixfreunde.de #bsd [EMAIL PROTECTED] | [EMAIL PROTECTED] FreeBSD Committer | Power to Serve -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFfZnJPrCIFpjWZiwRAk+6AJ9yu1Cb2CpO9tBNkEsI+5EbC+kBQACfUY/Y jb2MtcMsi3jM89HoKbm63bM= =G8dt -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: HEADS UP : security/gnupg will be upgraded to 2.0.1
Jun Kuriyama wrote: > Hi, > > I'm planning to upgrade security/gnupg to 2.0.1. This upgrade > includes portrevision bumps to indicate dependency changes. > > I'm testing conditional plist, upgrading procedure by portupgrade. > But I think it's almost ready to commit. > > If you have further suggestions, please let me know. Jun, Thanks for letting us know what you're plans are. I think you know what I'm going to say next. ;) As I suggested when I wrote to you in private e-mail some time ago, I think it would be more in line with the plans that the developers have for GnuPG 2.x to keep the existing gnupg port dedicated to the 1.x branch, and repo copy gnupg-devel to gnupg2. Quoting from the README for 2.x: GnuPG 2.0 is the stable version of GnuPG integrating support for OpenPGP and S/MIME. It does not conflict with an installed 1.4 OpenPGP-only version. Note that there is no binary gpg but a gpg2 so that this package won't conflict with a GnuPG 1.4 installation. gpg2 behaves just like gpg. GNUPG 1.4 AND GNUPG 2.0 === GnuPG 2.0 is a newer version of GnuPG with additional support for S/MIME. It has a different design philosophy that splits functionality up into several modules. Both versions may be installed simultaneously without any conflict (gpg is called gpg2 in GnuPG 2). In fact, the gpg version from GnuPG 1.4 is able to make use of the gpg-agent as included in GnuPG 2 and allows for seamless passphrase caching. The advantage of GnuPG 1.4 is its smaller size and no dependency on other modules at run and build time. Further, in discussion on the gnupg-users list the developers have clearly stated that they will continue working on at least the 1.4.x branch of GnuPG for the foreseeable future. Therefore I think it would be more in line with the development goals for the GnuPG project, and less confusing for new users coming to FreeBSD from other platforms, to adopt the naming scheme that I proposed, although not necessarily the exact patches I sent you to implement it. If you choose not to go that direction, I would be interested in hearing your reasoning. Thanks, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: failure of policy
On Dec 11, 2006, at 12:47 PM, Martin Wilke wrote: On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to 1.2.0 which had known errors in it which cause data loss. Somehow it was applied. A few days later a manual patch was added to work around that. The initial update indicates that whomever submitted the port was either claiming to be or was assumed to be the maintainer. For this update of 1.2.0 gives a pr show here http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/105575 here is my mistake thats commit is after 7 days not 14 days. This is my mistake right. After this commit, I received a private email with a bugfix. I never got any email regarding this one. Also, 1.2.1 still has some issues that need to be fixed; 1.2.2 should be out soon, and that is the one I would have committed to the tree, but now that cat is out of the bag and we have to live with it, I suppose.
Re: failure of policy
On Dec 11, 2006, at 12:47 PM, Martin Wilke wrote: For this update of 1.2.0 gives a pr show here http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/105575 here is my mistake thats commit is after 7 days not 14 days. This is my mistake right. After this commit, I received a private email with a bugfix. Reading this PR more closely it seems I was not even notified, as "Oleg Gawriloff" <[EMAIL PROTECTED]> is described as the maintainer and is the one responding to maintainer queries, which he is not.
Re: failure of policy
On Mon, Dec 11, 2006 at 06:47:53PM +0100, Martin Wilke wrote: > > If the committers are not going to follow the rules, then why should > > anyone bother to be a maintainer? > > I could say this is all my fault a concatenation of stupid mistakes :( > I hope you forgive me for this mistake. Vivek, miwi@ has been spanked quite a bit (both in Email and on IRC) about this mistake. His track record is amazingly clean, so it's important to remember that we're all human and that mistakes do get made. He's feeling pretty bad, so we need not rub his face in it any more. All of your points are completely valid (I'll be surprised if someone argues otherwise), but that said, don't be too hard on him. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Pfstat trouble, no data in database file
Hello list, After some more troubleshooting I've come a step further. I have run the '/usr/local/bin/pfstat -q' command from a shell and found some problems with my /usr/local/etc/pfstat.conf file. After solving these problems I get the following message issueing the '/usr/local/bin/pfstat -q' command: [EMAIL PROTECTED] etc # /usr/local/bin/pfstat -q ioctl: DIOCGETALTQS: Operation not supported by device pf_query: query_queues() failed I couldn't find anything usefull on these strings via Google. Any help is much appreciated. MTIA Cheers, Lars. > _ > From: Lars Wittebrood > Sent: Sunday, December 10, 2006 9:51 PM > To: 'freebsd-ports@freebsd.org' > Subject: Pfstat trouble, no data in database file > > Hello list, > > I've installed and configure the Pfstat port on a FreeBSD 6.1 RELEASE > system acting as a firewall based on PF. > > FreeBSD servername 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Fri Nov > 24 13:33:18 CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ALPHA > i386 > > The trouble I have is that I get no data at all in the Pfstat data > file! > > My Pfstat /etc/crontab entries > # > # Gather Pfstat output continually > * * * * * root/usr/local/bin/pfstat > -q >> /var/db/pfstat.db > # > # Generate Pfstat graphs every 5 minutes > */5 * * * * root/usr/local/bin/pfstat > -c /etc/pfstat.conf -d /var/db/pfstat.db > # > # Glean old Pfstat data > 1 1 1 * * root/usr/local/bin/pfstat > -t 31:365 > > Entries from my cron log: > Dec 10 21:40:00 servername /usr/sbin/cron[39679]: (root) CMD ( > /usr/libexec/atrun) > Dec 10 21:41:00 servername /usr/sbin/cron[502]: (*system*) RELOAD > (/etc/crontab) > Dec 10 21:41:00 servername /usr/sbin/cron[39687]: (root) CMD > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > Dec 10 21:42:00 servername /usr/sbin/cron[39696]: (root) CMD > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > Dec 10 21:43:00 servername /usr/sbin/cron[39701]: (root) CMD > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > Dec 10 21:44:00 servername /usr/sbin/cron[39714]: (root) CMD > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > Dec 10 21:44:00 servername /usr/sbin/cron[39715]: (operator) CMD > (/usr/libexec/save-entropy) > Dec 10 21:45:00 servername /usr/sbin/cron[39734]: (root) CMD > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > Dec 10 21:45:00 servername /usr/sbin/cron[39735]: (root) CMD ( > /usr/libexec/atrun) > Dec 10 21:45:00 servername /usr/sbin/cron[39733]: (root) CMD > (/usr/local/bin/pfstat -c /etc/pfstat.conf -d /var/db/pfstat.db) > > [EMAIL PROTECTED] db # ll /var/db/pfstat.db > -rw-r--r--1 root wheel 0 Dec 10 21:21 > /var/db/pfstat.db > > As you can see pfstat.db stays zero bytes! Anyone any idea why this is > happening? My /etc/pf.conf has a set loginterface entry! > > MTIA. > > Cheers, > Lars. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP : security/gnupg will be upgraded to 2.0.1
On Mon, Dec 11, 2006 at 07:42:00PM +, Shaun Amott wrote: > > In addition: I would guess that mail/imp, and maybe others, expect > bin/gpg to be present. If this is indeed the case, it would need > additional patching. > Sorry - ignore that last bit. I wasn't thinking. :-) -- Shaun Amott // PGP: 0x6B387A9A "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson pgpUnCOcRxkto.pgp Description: PGP signature
Re: [ports/security/gnupg] portupgrade fails on 4.11
El domingo 10 de diciembre a las 16:15:07 CET, GalaxyPC.Net escribió: > install-info --quiet /usr/local/info/gnupg1.info /usr/local/info/dir > install-info: menu item `gpg' already exists, for file `gpg' http://lists.freebsd.org/pipermail/freebsd-questions/2006-February/114123.html Check if /usr/local/bin is placed before /usr/bin in your PATH (bad idea). Regards -- http://personales.ya.com/banach pgpgkjuelgqGm.pgp Description: PGP signature
Re: Pfstat trouble, no data in database file
On Monday 11 December 2006 20:29, Lars Wittebrood wrote: > Hello list, > > After some more troubleshooting I've come a step further. > > I have run the '/usr/local/bin/pfstat -q' command from a shell and > found some problems with my /usr/local/etc/pfstat.conf file. After > solving these problems I get the following message issueing the > '/usr/local/bin/pfstat -q' command: > > [EMAIL PROTECTED] etc # /usr/local/bin/pfstat -q > ioctl: DIOCGETALTQS: Operation not supported by device > pf_query: query_queues() failed > > I couldn't find anything usefull on these strings via Google. > > Any help is much appreciated. pfstat 2.2 seems to assume that ALTQ support is enabled in the kernel. For now the only way to work around your problem seems to be to build a kernel with ALTQ support. Alternatively you can replace files/patch-pf.c in sysutils/pfstat with the attached and rebuild pfstat. > MTIA > > Cheers, > Lars. > > > _ > > From: Lars Wittebrood > > Sent: Sunday, December 10, 2006 9:51 PM > > To: 'freebsd-ports@freebsd.org' > > Subject:Pfstat trouble, no data in database file > > > > Hello list, > > > > I've installed and configure the Pfstat port on a FreeBSD 6.1 RELEASE > > system acting as a firewall based on PF. > > > > FreeBSD servername 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Fri > > Nov 24 13:33:18 CET 2006 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ALPHA i386 > > > > The trouble I have is that I get no data at all in the Pfstat data > > file! > > > > My Pfstat /etc/crontab entries > > # > > # Gather Pfstat output continually > > * * * * * root/usr/local/bin/pfstat > > -q >> /var/db/pfstat.db > > # > > # Generate Pfstat graphs every 5 minutes > > */5 * * * * root/usr/local/bin/pfstat > > -c /etc/pfstat.conf -d /var/db/pfstat.db > > # > > # Glean old Pfstat data > > 1 1 1 * * root/usr/local/bin/pfstat > > -t 31:365 > > > > Entries from my cron log: > > Dec 10 21:40:00 servername /usr/sbin/cron[39679]: (root) CMD ( > > /usr/libexec/atrun) > > Dec 10 21:41:00 servername /usr/sbin/cron[502]: (*system*) RELOAD > > (/etc/crontab) > > Dec 10 21:41:00 servername /usr/sbin/cron[39687]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > > Dec 10 21:42:00 servername /usr/sbin/cron[39696]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > > Dec 10 21:43:00 servername /usr/sbin/cron[39701]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > > Dec 10 21:44:00 servername /usr/sbin/cron[39714]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > > Dec 10 21:44:00 servername /usr/sbin/cron[39715]: (operator) CMD > > (/usr/libexec/save-entropy) > > Dec 10 21:45:00 servername /usr/sbin/cron[39734]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) > > Dec 10 21:45:00 servername /usr/sbin/cron[39735]: (root) CMD ( > > /usr/libexec/atrun) > > Dec 10 21:45:00 servername /usr/sbin/cron[39733]: (root) CMD > > (/usr/local/bin/pfstat -c /etc/pfstat.conf -d /var/db/pfstat.db) > > > > [EMAIL PROTECTED] db # ll /var/db/pfstat.db > > -rw-r--r--1 root wheel 0 Dec 10 21:21 > > /var/db/pfstat.db > > > > As you can see pfstat.db stays zero bytes! Anyone any idea why this > > is happening? My /etc/pf.conf has a set loginterface entry! > > > > MTIA. > > > > Cheers, > > Lars. > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgp9Jzrfe7vAX.pgp Description: PGP signature
Re: HEADS UP : security/gnupg will be upgraded to 2.0.1
On Mon, Dec 11, 2006 at 10:15:59AM -0800, Doug Barton wrote: > > Jun Kuriyama wrote: > > Hi, > > > > I'm planning to upgrade security/gnupg to 2.0.1. This upgrade > > includes portrevision bumps to indicate dependency changes. > > > > I'm testing conditional plist, upgrading procedure by portupgrade. > > But I think it's almost ready to commit. > > > > If you have further suggestions, please let me know. > > Jun, > > Thanks for letting us know what you're plans are. I think you know > what I'm going to say next. ;) As I suggested when I wrote to you in > private e-mail some time ago, I think it would be more in line with > the plans that the developers have for GnuPG 2.x to keep the existing > gnupg port dedicated to the 1.x branch, and repo copy gnupg-devel to > gnupg2. Quoting from the README for 2.x: > I agree with Doug. Moving gnupg to gnupg1 implies to me that gnupg 2.x is a drop-in upgrade for gnupg 1.x, but this certainly doesn't seem to be the case. It's also rather strange to upgrade the "main" port (implying that 2.x is the recommended and default version), and then point all dependant ports at the *old* version. In addition: I would guess that mail/imp, and maybe others, expect bin/gpg to be present. If this is indeed the case, it would need additional patching. Regards, Shaun -- Shaun Amott // PGP: 0x6B387A9A "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson pgpVHHWplNzYn.pgp Description: PGP signature
Re: freebsd port: Please update GRASS GIS to 6.2 thanks (eom)
Hi, I'm quite busy and tired. Maybe I'll update it in a few week, before the the end of the year. The 6.2.1 must be out then. It's good to see that this port is usefull to someone. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Pfstat trouble, no data in database file
List doesn't like text/x-csrc it seems. Resend as text/plain.
On Monday 11 December 2006 21:10, Max Laier wrote:
> On Monday 11 December 2006 20:29, Lars Wittebrood wrote:
> > Hello list,
> >
> > After some more troubleshooting I've come a step further.
> >
> > I have run the '/usr/local/bin/pfstat -q' command from a shell and
> > found some problems with my /usr/local/etc/pfstat.conf file. After
> > solving these problems I get the following message issueing the
> > '/usr/local/bin/pfstat -q' command:
> >
> > [EMAIL PROTECTED] etc # /usr/local/bin/pfstat -q
> > ioctl: DIOCGETALTQS: Operation not supported by device
> > pf_query: query_queues() failed
> >
> > I couldn't find anything usefull on these strings via Google.
> >
> > Any help is much appreciated.
>
> pfstat 2.2 seems to assume that ALTQ support is enabled in the kernel.
> For now the only way to work around your problem seems to be to build a
> kernel with ALTQ support. Alternatively you can replace
> files/patch-pf.c in sysutils/pfstat with the attached and rebuild
> pfstat.
>
> > MTIA
> >
> > Cheers,
> > Lars.
> >
> > > _
> > > From: Lars Wittebrood
> > > Sent: Sunday, December 10, 2006 9:51 PM
> > > To: 'freebsd-ports@freebsd.org'
> > > Subject: Pfstat trouble, no data in database file
> > >
> > > Hello list,
> > >
> > > I've installed and configure the Pfstat port on a FreeBSD 6.1
> > > RELEASE system acting as a firewall based on PF.
> > >
> > > FreeBSD servername 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Fri
> > > Nov 24 13:33:18 CET 2006
> > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ALPHA i386
> > >
> > > The trouble I have is that I get no data at all in the Pfstat data
> > > file!
> > >
> > > My Pfstat /etc/crontab entries
> > > #
> > > # Gather Pfstat output continually
> > > * * * * * root
> > > /usr/local/bin/pfstat -q >> /var/db/pfstat.db
> > > #
> > > # Generate Pfstat graphs every 5 minutes
> > > */5 * * * * root
> > > /usr/local/bin/pfstat -c /etc/pfstat.conf -d /var/db/pfstat.db
> > > #
> > > # Glean old Pfstat data
> > > 1 1 1 * * root
> > > /usr/local/bin/pfstat -t 31:365
> > >
> > > Entries from my cron log:
> > > Dec 10 21:40:00 servername /usr/sbin/cron[39679]: (root) CMD (
> > > /usr/libexec/atrun)
> > > Dec 10 21:41:00 servername /usr/sbin/cron[502]: (*system*) RELOAD
> > > (/etc/crontab)
> > > Dec 10 21:41:00 servername /usr/sbin/cron[39687]: (root) CMD
> > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db)
> > > Dec 10 21:42:00 servername /usr/sbin/cron[39696]: (root) CMD
> > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db)
> > > Dec 10 21:43:00 servername /usr/sbin/cron[39701]: (root) CMD
> > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db)
> > > Dec 10 21:44:00 servername /usr/sbin/cron[39714]: (root) CMD
> > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db)
> > > Dec 10 21:44:00 servername /usr/sbin/cron[39715]: (operator) CMD
> > > (/usr/libexec/save-entropy)
> > > Dec 10 21:45:00 servername /usr/sbin/cron[39734]: (root) CMD
> > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db)
> > > Dec 10 21:45:00 servername /usr/sbin/cron[39735]: (root) CMD (
> > > /usr/libexec/atrun)
> > > Dec 10 21:45:00 servername /usr/sbin/cron[39733]: (root) CMD
> > > (/usr/local/bin/pfstat -c /etc/pfstat.conf -d /var/db/pfstat.db)
> > >
> > > [EMAIL PROTECTED] db # ll /var/db/pfstat.db
> > > -rw-r--r--1 root wheel 0 Dec 10 21:21
> > > /var/db/pfstat.db
> > >
> > > As you can see pfstat.db stays zero bytes! Anyone any idea why this
> > > is happening? My /etc/pf.conf has a set loginterface entry!
> > >
> > > MTIA.
> > >
> > > Cheers,
> > > Lars.
> >
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to
> > "[EMAIL PROTECTED]"
--
/"\ Best regards, | [EMAIL PROTECTED]
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED]
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
--- pf.c.orig Thu May 11 23:41:07 2006
+++ pf.cMon Dec 11 21:08:31 2006
@@ -67,10 +67,8 @@
/* first, find out how many queues there are */
memset(&pa, 0, sizeof(pa));
- if (ioctl(fd, DIOCGETALTQS, &pa)) {
- fprintf(stderr, "ioctl: DIOCGETALTQS: %s\n", strerror(errno));
- return (1);
- }
+ if (ioctl(fd, DIOCGETALTQS, &pa))
+ return (0);
mnr = pa.nr;
/* fetch each of those queues */
@@ -144,23 +142,24 @@
query_ifaces(int fd, void (*cb)(int, const char *, int, double))
{
struct pfioc_iface io;
- struct pfi_kif ifs[256];
+ struct pfi_if ifs[256];
int i, j;
memset(&io, 0, sizeof(io));
io.pfiio_buffer = ifs;
io
FreeBSD Port: mpd4-4.0b5
Good time of the day to you! Had the following prob: analogous config (conf+ links + secret). mpd4.0b4 works fine, but the latest b5 -- failed. Server: FreeBSD from 6.1-RELEASE to 6.2-PRERELEASE. client: m$ xp native error on connection to b5: #778 that says "it was not possible to verify the identity of the server". conf: default: load pptp0 pptp0: new -i ng0 pptp0 pptp0 set ipcp ranges 192.168.0.1/32 192.168.0.12/32 load pptp_standard pptp_standard: set iface disable on-demand set bundle disable multilink set bundle enable noretry set bundle disable ipv6cp set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 60 180 set link mtu 1460 set link mru 1460 set ipcp yes vjcomp set ipcp dns 192.168.0.1 # set ipcp nbns 192.168.0.254 set iface enable proxy-arp set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless set bundle yes crypt-reqd set pptp self some.host.name.ru set pptp enable incoming set pptp disable originate set iface enable tcpmssfix set pptp disable windowing === end of conf === log: Dec 1 00:30:44 proxy mpd: mpd: pid 8804, version 4.0b5 ([EMAIL PROTECTED] 00:26 1-Dec-2006) Dec 1 00:30:44 proxy mpd: Label 'startup' not found Dec 1 00:30:44 proxy mpd: [pptp0] ppp node is "mpd8804-pptp0" Dec 1 00:30:44 proxy mpd: tcpmss node is "mpd8804-mss" Dec 1 00:30:44 proxy mpd: [pptp0] using interface ng0 Dec 1 00:31:32 proxy mpd: mpd: PPTP connection from xx.yy.zz.aa 3030 Dec 1 00:31:32 proxy mpd: pptp0: attached to connection with xx.yy.zz.aa 3030 Dec 1 00:31:32 proxy mpd: [pptp0] opening link "pptp0"... Dec 1 00:31:32 proxy mpd: [pptp0] link: OPEN event Dec 1 00:31:32 proxy mpd: [pptp0] LCP: Open event Dec 1 00:31:32 proxy mpd: [pptp0] LCP: state change Initial --> Starting Dec 1 00:31:32 proxy mpd: [pptp0] LCP: LayerStart Dec 1 00:31:32 proxy mpd: [pptp0] attaching to peer's outgoing call Dec 1 00:31:32 proxy mpd: [pptp0] link: UP event Dec 1 00:31:32 proxy mpd: [pptp0] link: origination is remote Dec 1 00:31:32 proxy mpd: [pptp0] LCP: Up event Dec 1 00:31:32 proxy mpd: [pptp0] LCP: state change Starting --> Req-Sent Dec 1 00:31:32 proxy mpd: [pptp0] LCP: SendConfigReq #1 Dec 1 00:31:32 proxy mpd: ACFCOMP Dec 1 00:31:32 proxy mpd: PROTOCOMP Dec 1 00:31:32 proxy mpd: MRU 1500 Dec 1 00:31:32 proxy mpd: MAGICNUM aed8ff48 Dec 1 00:31:32 proxy mpd: AUTHPROTO CHAP MSOFTv2 Dec 1 00:31:32 proxy mpd: pptp0-0: ignoring SetLinkInfo Dec 1 00:31:32 proxy mpd: [pptp0] LCP: rec'd Configure Request #0 link 0 (Req-Sent) Dec 1 00:31:32 proxy mpd: MRU 1400 Dec 1 00:31:32 proxy mpd: MAGICNUM 0f5c56cc Dec 1 00:31:32 proxy mpd: PROTOCOMP Dec 1 00:31:32 proxy mpd: ACFCOMP Dec 1 00:31:32 proxy mpd: CALLBACK Dec 1 00:31:32 proxy mpd:Not supported Dec 1 00:31:32 proxy mpd: [pptp0] LCP: SendConfigRej #0 Dec 1 00:31:32 proxy mpd: CALLBACK Dec 1 00:31:32 proxy mpd: [pptp0] LCP: rec'd Configure Request #1 link 0 (Req-Sent) Dec 1 00:31:32 proxy mpd: MRU 1400 Dec 1 00:31:32 proxy mpd: MAGICNUM 0f5c56cc Dec 1 00:31:32 proxy mpd: PROTOCOMP Dec 1 00:31:32 proxy mpd: ACFCOMP Dec 1 00:31:32 proxy mpd: [pptp0] LCP: SendConfigAck #1 Dec 1 00:31:32 proxy mpd: MRU 1400 Dec 1 00:31:32 proxy mpd: MAGICNUM 0f5c56cc Dec 1 00:31:32 proxy mpd: PROTOCOMP Dec 1 00:31:32 proxy mpd: ACFCOMP Dec 1 00:31:32 proxy mpd: [pptp0] LCP: state change Req-Sent --> Ack-Sent Dec 1 00:31:34 proxy mpd: [pptp0] LCP: SendConfigReq #2 Dec 1 00:31:34 proxy mpd: ACFCOMP Dec 1 00:31:34 proxy mpd: PROTOCOMP Dec 1 00:31:34 proxy mpd: MRU 1500 Dec 1 00:31:34 proxy mpd: MAGICNUM aed8ff48 Dec 1 00:31:34 proxy mpd: AUTHPROTO CHAP MSOFTv2 Dec 1 00:31:34 proxy mpd: [pptp0] LCP: rec'd Configure Ack #2 link 0 (Ack-Sent) Dec 1 00:31:34 proxy mpd: ACFCOMP Dec 1 00:31:34 proxy mpd: PROTOCOMP Dec 1 00:31:34 proxy mpd: MRU 1500 Dec 1 00:31:34 proxy mpd: MAGICNUM aed8ff48 Dec 1 00:31:34 proxy mpd: AUTHPROTO CHAP MSOFTv2 Dec 1 00:31:34 proxy mpd: [pptp0] LCP: state change Ack-Sent --> Opened Dec 1 00:31:34 proxy mpd: [pptp0] LCP: auth: peer wants nothing, I want CHAP Dec 1 00:31:34 proxy mpd: [pptp0] CHAP: sending CHALLENGE len:17 Dec 1 00:31:34 proxy mpd: [pptp0] LCP: LayerUp Dec 1 00:31:34 proxy mpd: [pptp0] LCP: rec'd Ident #2 link 0 (Opened) Dec 1 00:31:34 proxy mpd: MESG: MSRASV5.10 Dec 1 00:31:34 proxy mpd: [pptp0] LCP: rec'd Ident #3 link 0 (Opened) Dec 1 00:31:34 proxy mpd: MESG: MSRAS-0-INDIAN Dec 1 00:31:34 proxy mpd: pptp0-0: ignoring SetLinkInfo Dec 1 00:31:34 proxy mpd: [pptp0] CHAP: rec'd RESPONSE #1 Dec 1 00:31:34 proxy mpd: Name: "alex" Dec 1 00:31:34 proxy mpd: [pptp0] AUTH: Auth-Thread started Dec 1 00:31:34 proxy mpd: [pptp0] AUTH: Trying secret file: mpd.secret Dec 1 00:31:34 proxy mpd: Peer name: "alex" Dec 1 00:31:34 proxy mpd: [pptp0] AUTH: Auth-Thread finished normally Dec 1 00:31:34 proxy mpd: [pptp0] CHAP: Cha
Re: lang/gnat-gcc41 build error
Petr, GNAT/GPL and GNAT/GCC are two different products. I made gnat-gcc* ports as an experimental alternative to the gnat port (GNAT 2005/GPL). They are not meant to be complete or supported neither they are expected to pass all the tests. These are actually not the problems of the porting process but development of the GCC itself, so I suggest you find more on their mailing lists. > BTW - why is gnat-gcc34 dependent on perl, while > gnat-gcc41 is dependent on libiconv? Is this correct? Perl dependency is probably inherited from the gnat port, I do not remember ATM. I'll take a look at this, but you could also try to prove it yourself and post the results here. Libiconv is part of the GCC 4.1 build process, don't ask me about the details :) > I think we should also modify the dependent ports like > gtkada and xmlada (I need to resurrect this one...) to > support both gnat 2005 and gnat-gcc41. Further I should > upgrade gtkada to 2.8.0 and probably we should upgrade > florist and asis and create compatible port for glade and > maybe add aws port (nice to have for building web > services in Ada easily). I admire your enthusiasm. Please take a look at Martin Krischik's site at http://ada.krischik.com/index.php and bring back the subject on comp.lang.ada. -- Regards, Karel Miklav ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: failure of policy
On Mon, Dec 11, 2006 at 01:23:54PM -0500, Vivek Khera wrote: > Reading this PR more closely it seems I was not even notified, as > "Oleg Gawriloff" <[EMAIL PROTECTED]> is described as the maintainer > and is the one responding to maintainer queries, which he is not. What isn't detected well is if someone who isn't the maintainer submits a PR with the 'maintainer-update' state. Edwin and I need to look at our respective codebases and figure out what happened in this situation. But you're right, this is not the way that it is supposed to work. Please accept my apologies, and we'll look at the code. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: failure of policy
> But you're right, this is not the way that it is supposed to work. Please > accept my apologies, and we'll look at the code. Well, this looks to have been a combination of two human errors (on that particular PR), which the code really doesn't know how to deal with. But after looking at it, I'm not too sure what we could have done differently. So please folks, "let's be careful out there" as the old US TV show said, and respect the maintainers' prerogatives. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: failure of policy
On Mon, Dec 11, 2006 at 05:13:27PM -0600, Mark Linimon wrote: > On Mon, Dec 11, 2006 at 01:23:54PM -0500, Vivek Khera wrote: > > Reading this PR more closely it seems I was not even notified, as > > "Oleg Gawriloff" <[EMAIL PROTECTED]> is described as the maintainer > > and is the one responding to maintainer queries, which he is not. > > What isn't detected well is if someone who isn't the maintainer submits > a PR with the 'maintainer-update' state. Edwin and I need to look at > our respective codebases and figure out what happened in this situation. As I explained to linimon on #bsdports, the original PR didn't get caught by the PR-assignment-software because it couldn't determine the ports name (it said slony1 instead of databases/slony1). So it got in a "tomorrow when I'm awake I'll look at it again" list (this happened in the middle of the night). When I woke up and checked the list, I saw that miwi already grabbed it and ignored it for the rest. Which is what I normally do when people take PRs before they are rescued. For people with access to freefall: tail -f /hub/g/hubgnats/gnats-aa/incoming-PRs/log/foo and you can see which ones are caught and which ones are not caught. If you hear a ^G, then it's one which is not caught. Fix the portname in the synopsis of the original email and bounce the email to gnats-aa at frietbsd dot gro (confused domain to prevent spammers, you can decode it easily if you need), and it might fix itself. Otherwise you will have to wait until I'm awake, or back from dayjob, beach, sun, surf etc. Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP : security/gnupg will be upgraded to 2.0.1
At Mon, 11 Dec 2006 10:15:59 -0800, Doug Barton wrote: > Thanks for letting us know what you're plans are. I think you know > what I'm going to say next. ;) As I suggested when I wrote to you in > private e-mail some time ago, I think it would be more in line with > the plans that the developers have for GnuPG 2.x to keep the existing > gnupg port dedicated to the 1.x branch, and repo copy gnupg-devel to > gnupg2. Quoting from the README for 2.x: > > GnuPG 2.0 is the stable version of GnuPG integrating support for > OpenPGP and S/MIME. It does not conflict with an installed 1.4 > OpenPGP-only version. > > Note that there is no binary gpg but a gpg2 so > that this package won't conflict with a GnuPG 1.4 installation. gpg2 > behaves just like gpg. > > GNUPG 1.4 AND GNUPG 2.0 > === > GnuPG 2.0 is a newer version of GnuPG with additional support for > S/MIME. It has a different design philosophy that splits > functionality up into several modules. Both versions may be installed > simultaneously without any conflict (gpg is called gpg2 in GnuPG 2). > In fact, the gpg version from GnuPG 1.4 is able to make use of the > gpg-agent as included in GnuPG 2 and allows for seamless passphrase > caching. The advantage of GnuPG 1.4 is its smaller size and no > dependency on other modules at run and build time. > > > Further, in discussion on the gnupg-users list the developers have > clearly stated that they will continue working on at least the 1.4.x > branch of GnuPG for the foreseeable future. > > Therefore I think it would be more in line with the development goals > for the GnuPG project, and less confusing for new users coming to > FreeBSD from other platforms, to adopt the naming scheme that I > proposed, although not necessarily the exact patches I sent you to > implement it. > > If you choose not to go that direction, I would be interested in > hearing your reasoning. At first, thank you for your helping to upgrade our gnupg world to 2.0.x. And sorry I cannot explain as you can feel reasonable. I just think "security/gnupg" should be used as "what you should choose" for "GnuPG". If new ports user wants to install GnuPG, I hope there is "security/gnupg" as recommended stable version. I understand GnuPG developers think 1.4.x will be kept, but I think dependents will migrate to use modularized 2.0.x line. Though development is continue, Number of API consumer of 1.4.x line will be getting smaller. So, for 1 or 2 years later, I think existance of good stable "security/gnupg" and historical "security/gnupg1" will be less confusing (IMHO). GnuPG development will continue. So there will be GnuPG 3.x line. Above approach can be adopted. Anyway, this way maybe old-porters thinking. I liked to use "/" directory name (without version number). Using version number in ports directory is very exceptional event for keeping old ports (like "emacs", "emacs19", "emacs20"). I thought this is the way to indicate "what you should choose" for port users. But, there are port directories with version number than past. I can change my mind if it is suitable recently. -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP : security/gnupg will be upgraded to 2.0.1
On 12/12/06, Jun Kuriyama <[EMAIL PROTECTED]> wrote:
I just think "security/gnupg" should be used as "what
you should choose" for "GnuPG". If new ports user
wants to install GnuPG, I hope there is
"security/gnupg" as recommended stable version.
An unversioned directory is the maintainer-designated
default version of a port. Unless its upgrades break
a whole bunch of ports (like python did), it's none
of our business when and why they happen. An advance
heads-up is nice, but redundant.
Doug, privately kept, but prompt versioning ways are
one of the ports {trade,hall}marks. Gentoo is broken
and Debian is stale, we're fighting somewhere in
between, thanks to sane decisions our contributors
make.
Shaun, whatever versioned dirs might seem to imply,
they don't imply (in)stability or (in)compatibility.
The unversioned one is the default one, that's it.
Hitting users with new versions, but leaving them
a chance to survive seems like a nice policy to me.
To conclude, I understand how Jun feels and think
that instead of bitching about his reasoning, we
should be insanely grateful for more than 8 years
of his impeccable gnupg maintainership.
THANKS, JUN!!!
This is all my humble 4:30AM opinion anyway :-)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysutils/xbattbar for !i386
Recently, I installed a FreeBSD/amd64 laptop. I found this port uses apm (i386 only) interface to get battery information. The patch below changes it to use sysctl(3). Thus, it is usable on amd64. http://people.freebsd.org/~rafan/xbattbar.diff It works on my ThinkPad X60 (-CURRENT). If you are running this port, please have a test. Thanks, Rong-En Fan pgpepRVAHOkbM.pgp Description: PGP signature
Re: freebsd port: Please update GRASS GIS to 6.2 thanks (eom)
Since as far as I can tell no one has said this to you yet, you may want to have a look at the URL below and take a shot at updating this yourself. Good luck, Doug http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Pfstat trouble, no data in database file
Thank you very much Max. The patch did the trick for me. Regards, Lars. -Original Message- From: Max Laier [mailto:[EMAIL PROTECTED] Sent: Monday, December 11, 2006 9:10 PM To: freebsd-ports@freebsd.org Cc: Lars Wittebrood Subject: Re: Pfstat trouble, no data in database file On Monday 11 December 2006 20:29, Lars Wittebrood wrote: > Hello list, > > After some more troubleshooting I've come a step further. > > I have run the '/usr/local/bin/pfstat -q' command from a shell and > found some problems with my /usr/local/etc/pfstat.conf file. After > solving these problems I get the following message issueing the > '/usr/local/bin/pfstat -q' command: > > [EMAIL PROTECTED] etc # /usr/local/bin/pfstat -q > ioctl: DIOCGETALTQS: Operation not supported by device > pf_query: query_queues() failed > > I couldn't find anything usefull on these strings via Google. > > Any help is much appreciated. pfstat 2.2 seems to assume that ALTQ support is enabled in the kernel. For now the only way to work around your problem seems to be to build a kernel with ALTQ support. Alternatively you can replace files/patch-pf.c in sysutils/pfstat with the attached and rebuild pfstat. > MTIA > > Cheers, > Lars. > > > _ > > From: Lars Wittebrood > > Sent: Sunday, December 10, 2006 9:51 PM > > To: 'freebsd-ports@freebsd.org' > > Subject:Pfstat trouble, no data in database file > > > > Hello list, > > > > I've installed and configure the Pfstat port on a FreeBSD 6.1 > > RELEASE system acting as a firewall based on PF. > > > > FreeBSD servername 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Fri > > Nov 24 13:33:18 CET 2006 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ALPHA i386 > > > > The trouble I have is that I get no data at all in the Pfstat data > > file! > > > > My Pfstat /etc/crontab entries > > # > > # Gather Pfstat output continually > > * * * * * root /usr/local/bin/pfstat > > -q >> /var/db/pfstat.db > > # > > # Generate Pfstat graphs every 5 minutes > > */5 * * * * root /usr/local/bin/pfstat > > -c /etc/pfstat.conf -d /var/db/pfstat.db # # Glean old Pfstat data > > 1 1 1 * * root /usr/local/bin/pfstat > > -t 31:365 > > > > Entries from my cron log: > > Dec 10 21:40:00 servername /usr/sbin/cron[39679]: (root) CMD ( > > /usr/libexec/atrun) > > Dec 10 21:41:00 servername /usr/sbin/cron[502]: (*system*) RELOAD > > (/etc/crontab) > > Dec 10 21:41:00 servername /usr/sbin/cron[39687]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) Dec 10 21:42:00 > > servername /usr/sbin/cron[39696]: (root) CMD (/usr/local/bin/pfstat > > -q >> /var/db/pfstat.db) Dec 10 21:43:00 servername > > /usr/sbin/cron[39701]: (root) CMD (/usr/local/bin/pfstat -q >> > > /var/db/pfstat.db) Dec 10 21:44:00 servername /usr/sbin/cron[39714]: > > (root) CMD (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) Dec 10 > > 21:44:00 servername /usr/sbin/cron[39715]: (operator) CMD > > (/usr/libexec/save-entropy) > > Dec 10 21:45:00 servername /usr/sbin/cron[39734]: (root) CMD > > (/usr/local/bin/pfstat -q >> /var/db/pfstat.db) Dec 10 21:45:00 > > servername /usr/sbin/cron[39735]: (root) CMD ( > > /usr/libexec/atrun) > > Dec 10 21:45:00 servername /usr/sbin/cron[39733]: (root) CMD > > (/usr/local/bin/pfstat -c /etc/pfstat.conf -d /var/db/pfstat.db) > > > > [EMAIL PROTECTED] db # ll /var/db/pfstat.db > > -rw-r--r--1 root wheel 0 Dec 10 21:21 > > /var/db/pfstat.db > > > > As you can see pfstat.db stays zero bytes! Anyone any idea why this > > is happening? My /etc/pf.conf has a set loginterface entry! > > > > MTIA. > > > > Cheers, > > Lars. > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP : security/gnupg will be upgraded to 2.0.1
Jun Kuriyama wrote:
> At first, thank you for your helping to upgrade our gnupg world to
> 2.0.x. And sorry I cannot explain as you can feel reasonable.
I just want to make sure that the relevant issues are well thought
out, which it sounds like you have done.
> I just think "security/gnupg" should be used as "what you should
> choose" for "GnuPG". If new ports user wants to install GnuPG, I hope
> there is "security/gnupg" as recommended stable version.
Well, I think that's a reasonable position in terms of how things are
traditionally done in our ports system. I'm not sure I would agree
that we should be pushing users toward adopting 2.x as the default
just yet, but I don't have a strong argument for either position.
If this is your plan, it leads me to the next question, which is how
are you going to handle the fact that GnuPG 2.x does not install a
binary named "gpg?" Will you install a symlink if gnupg1 is not
installed? And if so, will it CONFLICT with that port? If we are going
to suggest to users that 2.x is the default, I think we need to
provide support for those legacy(?) apps that think gnupg is spelled gpg.
> I understand GnuPG developers think 1.4.x will be kept, but I think
> dependents will migrate to use modularized 2.0.x line. Though
> development is continue, Number of API consumer of 1.4.x line will be
> getting smaller.
I don't disagree with you necessarily, I just don't think that's a
good reason to make our default 2.x at this time.
> Anyway, this way maybe old-porters thinking. I liked to use
> "/" directory name (without version number).
> Using version number in ports directory is very exceptional event for
> keeping old ports (like "emacs", "emacs19", "emacs20"). I thought
> this is the way to indicate "what you should choose" for port users.
>
> But, there are port directories with version number than past. I can
> change my mind if it is suitable recently.
I think that given your intention of making 2.x the default, your plan
is the right way to achieve that. I'm just not sure it's the right way
to go forward, at least in the short term.
Andrew Pantyukhin wrote:
> An unversioned directory is the maintainer-designated
> default version of a port.
Traditionally that has been the case, yes.
> Unless its upgrades break
> a whole bunch of ports (like python did), it's none
> of our business when and why they happen. An advance
> heads-up is nice, but redundant.
I do not agree with this at all. GnuPG 2 is a completely different way
of accomplishing the same tasks. Personally, I think it will be a POLA
violation for users expecting to be able to install
"ports/security/gnupg" and have something that "just works" as gnupg
1.x does. At minimum 2.x requires at least one pinentry program, and
you don't really get all the benefit from 2.x unless you set up
gpg-agent at least. And that doesn't even begin to account for the
differences in library dependencies, the modular nature of the various
functionality in the new tools, etc.
> Doug, privately kept, but prompt versioning ways are
> one of the ports {trade,hall}marks. Gentoo is broken
> and Debian is stale, we're fighting somewhere in
> between, thanks to sane decisions our contributors
> make.
Sorry, I can't parse this paragraph at all.
> Shaun, whatever versioned dirs might seem to imply,
> they don't imply (in)stability or (in)compatibility.
> The unversioned one is the default one, that's it.
>
> Hitting users with new versions, but leaving them
> a chance to survive seems like a nice policy to me.
And in my mind, leaving the gnupg port alone and offering a gnupg2
port to allow users to make a more gradual and pain free migration
(which is what the GnuPG developers seem to intend) is the way to go.
> To conclude, I understand how Jun feels and think
> that instead of bitching about his reasoning,
Just in case it isn't already clear, no one is "bitching" about
anything here. It's perfectly reasonable for developers to have
different ideas about how something should be done, and there is
nothing wrong with hashing it out before moving forward. In fact,
that's what grownups do in situations like this.
> we should be insanely grateful for more than 8 years
> of his impeccable gnupg maintainership.
Having spent a non-zero amount of time working on a gnupg2 port for my
own use, not to mention the updates of the related ports to get 2.x to
build, I agree with you that we should be appreciative of Jun's
efforts, and I hope that he understands that nothing I've said is
intended in any way to be critical of him or his work.
Doug
--
This .signature sanitized for your protection
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysutils/xbattbar for !i386
On 12/12/06, Rong-En Fan <[EMAIL PROTECTED]> wrote: Recently, I installed a FreeBSD/amd64 laptop. I found this port uses apm (i386 only) interface to get battery information. The patch below changes it to use sysctl(3). Thus, it is usable on amd64. http://people.freebsd.org/~rafan/xbattbar.diff It works on my ThinkPad X60 (-CURRENT). If you are running this port, please have a test. Works on my HP dv8135nr (-CURRENT) system. 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]"
