Re: FreeBSD Port: delegate-9.5.6 problem
Hello! Сергей Святкин wrote on 10-5-2007 5:39: > Hello! > > The problem when start under freebsd 6.2 > > # uname -a > FreeBSD mail.svgc.ru 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Wed Apr 4 10:02:02 > SAMST 2007 > [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MAILKERNEL i386 > > install delegated from ports: > > # cd /usr/ports/net/delegate > # make install > > then try to start: > > # delegated > DeleGate/9.5.6 (April 5, 2007) > AIST-Product-ID: 2000-ETL-198715-01, H14PRO-049, H15PRO-165, H18PRO-443 > Copyright (c) 1994-2000 Yutaka Sato and ETL,AIST,MITI > Copyright (c) 2001-2006 National Institute of Advanced Industrial Science and > Technology (AIST) > Thank you for the report. Stripping the binary seems to invalidate the internal checksum check. I will send in an update for the port to not strip the binary for the time being. You can do this yourself by adding to the Makefile: 'STRIP= ' after the PLIST_FILES line. Greets, Nils ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Popularity contest
Since a little while, Debian has been using a popularity contest, that sends anonymous usage details of various packages that Debian users have installed. These details are summarized at http://popcon.debian.org/ I figure something like this would be a huge advantage for the FreeBSD ports-community as well, and would like to propose starting something like this up for FreeBSD as well (unless I am misinformed, nothing to the sort exists at this point), either by porting popcon to FreeBSD, or by doing something completely different. Any thoughts? Greets, Nils signature.asc Description: OpenPGP digital signature
Re: FreeBSD Port: poptop-1.3.0
Molokanov kaN5300 Ilya wrote on 18-12-2006 17:05: > Hello. I am small ISP admin from Russia. Sorry at first for my English. No worries, I understood you just fine :-) > > > With such config i have some flood in my /var/log/debug like this: > > Dec 18 18:58:00 utm pptpd[29009]: GRE: accepting packet #45534 > Dec 18 18:58:00 utm pptpd[29009]: GRE: accepting packet #45535 > > Ti avoid this i have to edit pptpgre.c:402 > > syslog(LOG_DEBUG, "GRE: accepting packet #%d", seq); > > /* syslog(LOG_DEBUG, "GRE: accepting packet #%d", > seq); */ > > I am new in FreeBSD. So, maybe i do thomething wrong or, maybe i can > make some patch to ur port? It would be better to not include the debug level in your logfiles, to save you some space. You can do this by changing your syslog.conf. For exact syntax, consult the syslog.conf(8) manpage. Kind regards, Nils -- Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one. ~Benjamin Franklin (American Statesman, Scientist, Philosopher, Printer, Writer and Inventor. 1706-1790) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to construct this port?
Hi ! I'm trying to set up a new port, but I'm unsure how to proceed, until now I've only maintained already existing ports. The port is a plugin for an already existing port, giving extra functionality, but is maintained as a seperate package. In order to compile the port, you need a sourcetree of both the original port and the port of the plugin, where the sourcetree of the original port has to have been ./configure-d How would I go about this? Greetings, Nils ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to construct this port?
Chuck Swiger wrote on 28-12-2006 20:20: > Ion-Mihai IOnut Tetcu wrote: >> On Thu, 28 Dec 2006 12:53:34 -0500 >> Chuck Swiger <[EMAIL PROTECTED]> wrote: >>> However, sometimes mail systems go down or block traffic for whatever >>> reason: postmaster's job is a thankless task, and this was true even >>> before spam and viral email appeared. Nowadays, it's harder to get >>> things mostly right (nevermind "perfect"), so postmasters make >>> imperfect decisions because they are faced with undesirable tradeoffs. >> >> Indeed :-( >> >> However banning a hole country isn't a tradeoff in my book, it's just >> plain [inset_the_word_here]. And sin[c]e it's giving a 5XX code there's >> really no way to reach the person in question. > > I agree that blocking a whole country is a mistake. Short of posting > to the mailing list, there's no way to reach whoever it is. > > Although I've CC:ed him on the thread. The country-blocks have been in my mail config for ages, and I didn't think of them as I decided to become port maintainer. I understand that it is important as a port maintainer to answer user questions on the port, and so I have, at the moment the blocks became apparent and a nuisance, removed them. Looks like im going to turn postgrey after all :-) >>> It has not been my observation that insisting people not make any >>> mistakes commonly results in fewer mistakes being made, or much less, >>> in zero mistakes being made. :-) Rather than try to insist they >>> "are not allowed" to do something, I'd prefer to let people make >>> their own decisions and learn which ones are mistakes. YMMV >> >> The problem is that, IMHO, this kind of rejecting affects us all as I >> think that being a port maintainer implies receiving and replying to >> users' email. > > Certainly true. > > People doing stuff with FreeBSD ought to whitelist @freebsd.org in > particular; that would make committers lives easier. But email and > even Internet access are not completely reliable; people go away on > vacations sometimes, for a timely example. (Merry Christmas/holidays > all. :-) Ha, good idea! Implemented ... :-) (And a Happy Holidays to you too!) > For a maintainer timeout to be useful, there needs to be a pending PR > and/or someone else willing to be more accessible. Update the current > PR with the bounce and set responsible to Nivo, committing the change > or not as you feel best; or file a new PR listing another maintainer > if one is available and wait for the standard timeout period pending > resolution by the hat-wearing demigods known as [EMAIL PROTECTED] Apart from me thinking it may be a bit much to go for maintainer switch right away due to a restrictive mail config, what PR are we talking about now, so that I can have a look into it ;) Greetings, Nils ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to construct this port?
Ion-Mihai IOnut Tetcu wrote on 28-12-2006 13:57: > On Thu, 28 Dec 2006 14:36:16 +0200 > Vasil Dimov <[EMAIL PROTECTED]> wrote: > > >> Interesting: >> >> Do you really block all mails coming from Bulgaria? >> > > Romania also. > > > Nils, you're a port maintainer, please fix this $&^*@ > Fixed! Those blocks have been in there for ages, so I forgot all about them, oops! Gr, Nils ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
