Re: ports/138698: lang/php5: PHP session.save_path vulnerability
Old Synopsis: PHP session.save_path vulnerability New Synopsis: lang/php5: PHP session.save_path vulnerability Responsible-Changed-From-To: freebsd-www->freebsd-ports Responsible-Changed-By: remko Responsible-Changed-When: Thu Sep 10 10:24:18 UTC 2009 Responsible-Changed-Why: reassign to ports team; this has nothing to do with the webmasters queue http://www.freebsd.org/cgi/query-pr.cgi?pr=138698 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/14057: new port: net/libunp
Synopsis: new port: net/libunp Responsible-Changed-From-To: freebsd-ports->freebsd-doc Responsible-Changed-By: remko Responsible-Changed-When: Wed Nov 11 08:44:10 UTC 2009 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=14057 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/14058: new port: net/libunpipc
Synopsis: new port: net/libunpipc Responsible-Changed-From-To: freebsd-ports->freebsd-doc Responsible-Changed-By: remko Responsible-Changed-When: Wed Nov 11 08:44:15 UTC 2009 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=14058 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/14059: New port: roottail-0.0.4B
Synopsis: New port: roottail-0.0.4B Responsible-Changed-From-To: freebsd-ports->freebsd-doc Responsible-Changed-By: remko Responsible-Changed-When: Wed Nov 11 08:44:21 UTC 2009 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=14059 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/14057: new port: net/libunp
Synopsis: new port: net/libunp Responsible-Changed-From-To: freebsd-doc->freebsd-ports Responsible-Changed-By: remko Responsible-Changed-When: Wed Nov 11 08:45:03 UTC 2009 Responsible-Changed-Why: Reassign to ports. http://www.freebsd.org/cgi/query-pr.cgi?pr=14057 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/14058: new port: net/libunpipc
Synopsis: new port: net/libunpipc Responsible-Changed-From-To: freebsd-doc->freebsd-ports Responsible-Changed-By: remko Responsible-Changed-When: Wed Nov 11 08:45:31 UTC 2009 Responsible-Changed-Why: Reassign to ports, typo. http://www.freebsd.org/cgi/query-pr.cgi?pr=14058 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/14059: New port: roottail-0.0.4B
Synopsis: New port: roottail-0.0.4B Responsible-Changed-From-To: freebsd-doc->freebsd-ports Responsible-Changed-By: remko Responsible-Changed-When: Wed Nov 11 08:45:46 UTC 2009 Responsible-Changed-Why: Reassign to ports, typo http://www.freebsd.org/cgi/query-pr.cgi?pr=14059 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/148450: devel/glib20: recent glib20 __STDC_ISO_10646__ fix causes pidgin to crash
Old Synopsis: recent glib20 __STDC_ISO_10646__ fix causes pidgin to crash New Synopsis: devel/glib20: recent glib20 __STDC_ISO_10646__ fix causes pidgin to crash Responsible-Changed-From-To: freebsd-bugs->freebsd-ports Responsible-Changed-By: remko Responsible-Changed-When: Thu Jul 8 14:57:18 UTC 2010 Responsible-Changed-Why: reassign to ports http://www.freebsd.org/cgi/query-pr.cgi?pr=148450 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports/115308: multimedia/jahshaka fails to open GUI - ends with "preferences OK" but nothing happens
Synopsis: multimedia/jahshaka fails to open GUI - ends with "preferences OK" but nothing happens Responsible-Changed-From-To: ports->freebsd-ports-bugs Responsible-Changed-By: remko Responsible-Changed-When: Mon Dec 17 06:47:54 UTC 2007 Responsible-Changed-Why: Reassign to appropriate maintainer http://www.freebsd.org/cgi/query-pr.cgi?pr=115308 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
Sergey Matveychuk wrote: Shaun Amott wrote: On Fri, Jul 28, 2006 at 03:03:43PM +1000, Joel Hatton wrote: FYI, Red Hat released an advisory today about a vulnerability in Ruby. So far it doesn't appear in the VuXML, but am I correct in presuming it will soon? I've added it; thanks for the report. Can we get patches somewhere? I can't find any. It is said that the patches are available through the CVSweb but all the information I could fine was in japanese, which is a bit difficult to read for me (read: i do not speak nor read japanese at all). We might have a shot on how different vendors resolved this issue and generate patches from that.. -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
Sergey Matveychuk wrote: Sergey Matveychuk wrote: Good. There is three patches there. I'll test if they fix the vulnerabilities. FYI The fixes was committed. Thanks a lot for the work Sergey! -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dixit port bad management
On May 2, 2010, at 9:59 PM, Tim A wrote: > > 1) I don't understand why the Textproc/Dixit port is so badly managed. The > program itself is at version 10.4, while your unprofessional port still stays > at version 1.0.1, claiming that the GCC 4.2 compilation is broken. > > 2) I don't understand either why you don't use Dixit sourceforge RSS feeds to > know when a new version is available. > > 3) I don't understand how your Dixit port points to files which don't exist > anymore. > > 4) I don't understand the suprematism attitude of the maintainers in charge, > who don't give a penny on the programs they are suppose to maintain. They are > only interested in the statistics generated by their unprofessional ports, > but not in their quality. > > > > Tim > Dear Tim, Thank you for sending this email. As you might understand, people come and go on the project, things get fixed, imported, and left alone. But.. the great part of our community is.. you can help! I see that this is hurting you badly.. you can change this, you can help us upgrading the port, and making sure it entirely works. How about that? I invite you to become an active member of the community and help us to get proper support. Untill then, your email is noted and hopefully someone will have the time/motivation etc to fix this. Thank you for using FreeBSD! -- /"\ Best regards,| re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/| / \ 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 "freebsd-ports-unsubscr...@freebsd.org"
Re: Wordpress outputs an empty page after ports upgrade
On Jul 19, 2010, at 11:11 AM, Yuri wrote: > My e-mail to the maintainer of www/wordpress bounced. > > Please make sure there is the valid maintainer e-email specified for > wordpress. > > Yuri > Thank you for volunteering to continuesly scan the maintainer addresses whether or not they are still right and working, and persons are still behind their MAINTAINER Line. If I am somehow confused by you volunteering, then you wont mind that I tell you that it's a hideous process and unless you can resolve that, you should learn to live with it. After all all the ports@ people are doing their very best to keep things working and maintained but sometimes things fall between the ship and shore. Somehow I get the feeling that you do not understand Volunteer projects and that you are not thankfull for the hours people spend on software for YOU. Thanks, Remko -- /"\ Best regards, | re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/| / \ 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 "freebsd-ports-unsubscr...@freebsd.org"
Re: Wordpress outputs an empty page after ports upgrade
On Jul 20, 2010, at 7:52 PM, Yuri wrote: > On 07/20/2010 10:45, Remko Lodder wrote: >> Somehow I get the feeling that you do not understand Volunteer projects and >> that you are not >> thankfull for the hours people spend on software for YOU. >> > > Remko, > > What makes you think that I "do not understand Volunteer projects" and "not > thankfull for the hours people spend"? > > I just reported the issue with the maintainer's e-mail. Since I don't have > the commit privileges the only thing I can do aboutn this is to report it to > po...@. Am I wrong? Not about the mentioned parts. But you are about: "Please make sure there is the valid maintainer e-email specified for wordpress." Without context and the like (should I mention that the original report to the maintainer's email address is "lacking information" ?) you seem to have this against the entire Ports Community. That can only be resolved if you volunteer to do the work to make it happen. Else you need to learn to live with it that sometimes addresses get bogus. Did you consider that the guy might have been taken out of his email? that ther emight be issues at the provider? That he might have changed ISP's and didn't change email addresses yet? Or one of the many other reasons that we can think of? Its like this: You emailed with limited information, to an email address that is currently not responding. Whether that has it's reasons or not, or whether that's on purpose is something we cannot comment on and need to see whether this might or might not is a problem. On the other end: i tested this and his primairy MX seems to refuse connections, whilst the secondary does not allow relay. That might be a transient problem. Please wait and see, and file a PR in case this is a real problem for you. > > Yuri -- /"\ Best regards,| re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/| / \ 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 "freebsd-ports-unsubscr...@freebsd.org"
Re: Wordpress outputs an empty page after ports upgrade
>> > > You are really reading much more into my message than was actually put there. > Sorry if that's my the style that triggered this. But I would like to assure > you that I wasn't even close to put anything against the ports or FreeBSD > community. > > I communicate to maintainers a lot. And usually quite productive. This case > caught attention and I posted on po...@. Brief, just to let people know. > That's all to it. I also don't have much time to investigate myself, have > hundreds of things to do. > > What concerns wordpress problem, that's really all info I have: with the > current 8.1 and ports it produces blank output. I really don't have more > information. > > Thanks, > Yuri Fair enough, please consider writing something like "hey, $maintainer, if you are reading this, please understand that your email address is not working" or something so that it's clear for others that there is something going on but that is not the ports@ problem. Wordpress has the option to enable debugging, can you please try that? My website (see my signature) is running on 8-STABLE, without issues, version from thursday or something so fairly recent. Thanks, Remko (p.s. does httpd mention any BUS errors or SEGFAULTS?) -- /"\ Best regards,| re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/| / \ 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 "freebsd-ports-unsubscr...@freebsd.org"
Re: need an explanation of "make serarch" output
Aryeh M. Friedman wrote: > If I do "make search key=XXX display=[br]deps" it displays the deps in > question twice... is there a difference between the two and if so if > want to know what needs to be build before the port can be built or > run which list do I use? > Did you ever RTFM at all? "bdeps (searches the port build-time dependency), rdeps (searches the port run-time dependency)" it's just there in ports(7). -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: who do I report this to?
Can you please STOP cross posting to various mailinglists all at once? It is causing all kinds of unneeded messages to various addresses (yeah I am now guilty of that as well); stop it. If you have issues with if_re, please ask it's maintainer for support, and rule that out first and then proceed to the next item if the problem still continues, generating loads of emails with "my " content which includes "but this and this and this and this might also be the combination" etc is NOT going to help resolve this because the options are too legio (could be the software, could be your hardware, could be a user flaw, could be the remote switch etc). Please do it step by step with the maintainers as much as possible, and where possible please try to avoid overloading the mailinglists with things you run into on a day by day basis, personally I find it not very interesting to read them anymore because "its just another thing", that might not be the thing we are persuing here, but with all of your emails, I do get this feeling. //Remko On Tue, November 20, 2007 8:11 am, Aryeh M. Friedman wrote: > Who do I report the following issue to (it falls into at least 3 camps)? > > If I am downloading a torrent in deluge 0.5.6.2_1 *AND* am logged into > gmail (*WITH* a chat open) my network connection looses about 90% of > it's capacity (for all applications), re(4) with the following: > > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: Submitting a new port if send-pr is broken
On Mon, November 26, 2007 7:01 am, Chris Haulmark wrote: > Hi Aryeh! >> Due to a ISP firewall it is not possible for me to send/recv mail how >> do I submit a new port since send-pr requires email? > > If you have a web browser, you can submit it via FreeBSD's website: > > http://www.freebsd.org/support/bugreports.html > > The link is "Submit a Problem Report". > > Chris > Indeed, that is the online version, be sure to mark the correct category etc though (Aryeh did that wrong when submitting the bug). -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: Submitting a new port if send-pr is broken
On Mon, November 26, 2007 9:55 am, Aryeh M. Friedman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > >> >> Indeed, that is the online version, be sure to mark the correct category >> etc though (Aryeh did that wrong when submitting the bug). > > Ok how is ports not the right category for graphics/libfpx ? > The ticket was submitted to freebsd-bugs with the category misc; it should have been freebsd-ports-bugs with category ports, so yes the ports category is correct; but it wasn't like that. > -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: duration of the ports freeze
On Tue, November 27, 2007 8:20 am, Aryeh M. Friedman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > What is the current ETA on when the ports freeze will end? > See the freebsd.org release pages. > -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: duration of the ports freeze
On Tue, November 27, 2007 8:50 am, Aryeh M. Friedman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Remko Lodder wrote: >> On Tue, November 27, 2007 8:20 am, Aryeh M. Friedman wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> What is the current ETA on when the ports freeze will end? >>> >> >> See the freebsd.org release pages > > I know you will kill me for this but the URL? > > Perhaps use your golden fingers to check the website itself? it's two clicks away from the frontpage... goodluck! -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: running port as non-root
rihad wrote:
> Hi, I'm trying to run the net/openradius port as non-root
> by first changing /usr/local/etc/rc.d/openradius:
>
> . /etc/rc.subr
>
> name="openradius"
> rcvar=`set_rcvar`
>
> load_rc_config ${name}
>
> : ${openradius_enable="NO"}
> : ${openradius_flags="-o /var/log/openradius.log"}
>
> -command=/usr/local/sbin/radiusd
> +command=/usr/local/bin/sudo
> +flags="-u radius /usr/local/sbin/radiusd"
>
> run_rc_command "$1"
>
> (Lines marked with -/+ were removed/added by me, respectively).
>
> Then I add the radius user, allow it to run without sudo's asking for
> the password, and finally start the thing up:
> # pw useradd radius -d /nonexistent -s /usr/sbin/nologin
> # visudo
> # ... do the necessary chown/chmod on openradius logs/dictionaries ...
> # /usr/local/etc/rc.d/openradius start
>
> All fine so far: everything starts up fine and runs. The problem starts
> here:
> # /usr/local/etc/rc.d/openradius stop
> openradius not running?
> # ps -auxww | fgrep radiusd
> radius 89300 0.0 0.0 3756 1588 ?? Is 10:56AM 0:00.00
> /usr/local/sbin/radiusd
> ...
>
> any built-in way to make "stop" work, without changing rc.d/ too much?
>
> Thanks.
probably the user does not have rights to write /var/run/radiusd.pid or
whatever pid file it uses, I think the ``stop`` command cats that file
and seeks for the PID in the processtree and kills it { sort off }.
hope this helps!
--
/"\ Best regards, | [EMAIL PROTECTED]
\ / Remko Lodder | [EMAIL PROTECTED]
Xhttp://www.evilcoder.org/ |
/ \ 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: [RFC/P] Port System Re-Engineering
Aryeh M. Friedman wrote: > Ade Lovett wrote: > > > Then the community needs to make up it's mind because I have been > criticized for making a wiki for a similar issue (SATA issues on > ICH9(R)) You do sound like Marie Antonetta. For the time being > as far I can tell the consensus is to keep most things on mailing > lists (not my choice). You missed the whole point there (a couple of times already :(), The point with that thread was that you were looking for the solution of a ATA driver thingy etc, which does not need to have a Wiki for it because you need to discuss with the clueful people out there. Starting a totally new project with new foundations etc DOES require such a Wiki because you can easily outline your ideas / requirements there and allow you and others to participate to generate code etc. As I stated a couple of times before (perhaps hiddenly), please try to research a bit more and -read- what is being told. Then sleep a day over the issue and THEN email the rest to see what they think; you are quite ambitious, which is appreciated, or at least I think that there should be room for ambition all the time, but you are using it the wrong way, causing people to ignore you (high sound / noise ratio) and there goes the ambition, "lost" in space. Dont do that to yourself or the project. Thanks. remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: [RFC/P] Port System Re-Engineering
David Southwell wrote: > Just what is your agenda here? That's so november 2007, we dont use calenders nowadays > > Why all the spite and venom? > > If you do not have anything practical to contribute to the current discussion > that takes it forward then why waste your energies saying anything at all? > please step away from the Mirror. Now, stop this thread, stop the discussion, build something, and come back, if you cannot code or produce something with whatever you think the tree should be using, then *silence*. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: Limitations of Ports System
Aryeh M. Friedman wrote: > Remko Lodder wrote: >> David Southwell wrote: >>> On Friday 14 December 2007 08:08:54 Paul Schmehl wrote: >>>> --On Friday, December 14, 2007 12:19:06 + RW >>>> >>>> <[EMAIL PROTECTED]> wrote: >>>>> On Thu, 13 Dec 2007 22:34:58 -0500 >>>>> >>>>> "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: >>>>>> Namely if I build abc with options 123 and 345 and def with >>>>>> 345 and 678 then 345 will be cached for def since we >>>>>> already set it for abc. >>>>> How do you know the user wants 345 set on both ports? >>>>> >>>>> It might be a useful stable feature on "abc", but causes >>>>> lock-ups on "def" >>>> SInce I've already killfiled Aryeh, I can only infer what you >>>> are responding to and respond to him. But let me state this >>>> emphatically in the hopes it will get through his thick skull. >>>> >>> I do wish you could acquire the maturity to distinguish between >>> the advantages that could come arguing your case clearly and >>> collegially and the disadvantages that acrue from being >>> personally antagonistic towards someone with whose analysis you >>> happen to disagree. >>> >>> For me when someone becomes abusive they destroy their own >>> credibility and get to sound as though they believe their >>> opinions antitle them to be hateful and that their own views are >>> somehow godgiven. >>> >>> >>>> IT IS NOT THE JOB OF PORTS TO MAKE DECISIONS FOR USERS. >>> IMHO Shouting make you less rather than more credible. >>>> \Please repeat that one hundred times until it gets through. >>>> >>> Endless repetition does not add strength to analysis!! >>>> No port should *ever* make decisions on a users behalf. >>>> Suggestions, yes (e.g. OPTIONS that are enabled by default.) >>>> Decisions, no. If you depend on another port *and* on certain >>>> knobs in that dependency being enabled, then *tell* the user >>>> that during your port's install and let them decide how to >>>> handle it. DO NOT enable those knobs yourself, no matter how >>>> tempting it may be. >>> IMHO You would sound more credible if you used the IMHO a bit >>> more!! You might also gain some respect if you followed your own >>> advice. Make suggestions for others to consider - do not decide, >>> in advance, they are thick skulled if they do not agree with >>> you!! >>>> It is beyond impossible for anyone to know what every user who >>>> is installing ports already has on their boxes or what they >>>> might want to add or ***what you might break***. Once you >>>> begin making decisions for them, you could well stomp all over >>>> something that was functioning perfectly normally and break a >>>> critical box. >>>> >>>> DON'T DO IT. That is so Microsoftian it's not funny. >>> IMHO Shouting, hectoring and lecturing does not add weight to >>> anyones point of view. >>> >>> >> These threads have gone far enough, please consider taking this off >> the FreeBSD mailinglists and discuss this privately. The majority >> does not like the current ideas and want to see something usefull >> first. People like Aryeh and David are not really persons that one >> would see as the persons generating the ports-infrastructure-ng >> till they have code. > >> If you both keep pissing off people that have a fair share in the >> ports collection already, please do it by other means, dont crowd >> the mailinglists with it. Your ideas might be perfect in your world >> but they aint in ours (till you have shown working code). > >> So please stfu till you have some code and be done with it . > > Developing in a vacuum is a recipe for disaster we are making > fairly good progress believe it or not I only see an other 1 or 2 > threads being needed before actual coding starts, *BUT* producing a > system no one wants is pointless thus it is wise to gather as much > input as possible... why is it that everyone who sees the whole > concept as being negative has offered no input what so ever about what > should be done (even saying "the current system is fine" is useful to us) > simply because we have seen it failing a lot of times. Please take this offlist,discuss this and generate a nice PoC, t
Re: Limitations of Ports System
David Southwell wrote: > On Friday 14 December 2007 08:08:54 Paul Schmehl wrote: >> --On Friday, December 14, 2007 12:19:06 + RW >> >> <[EMAIL PROTECTED]> wrote: >>> On Thu, 13 Dec 2007 22:34:58 -0500 >>> >>> "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote: >>>> Namely if I build abc with options 123 and 345 and >>>> def with 345 and 678 then 345 will be cached for def since we already >>>> set it for abc. >>> How do you know the user wants 345 set on both ports? >>> >>> It might be a useful stable feature on "abc", but causes lock-ups on >>> "def" >> SInce I've already killfiled Aryeh, I can only infer what you are >> responding to and respond to him. But let me state this emphatically in >> the hopes it will get through his thick skull. > I do wish you could acquire the maturity to distinguish between the > advantages > that could come arguing your case clearly and collegially and the > disadvantages that acrue from being personally antagonistic towards someone > with whose analysis you happen to disagree. > > For me when someone becomes abusive they destroy their own credibility and > get > to sound as though they believe their opinions antitle them to be hateful and > that their own views are somehow godgiven. > > >> IT IS NOT THE JOB OF PORTS >> TO MAKE DECISIONS FOR USERS. > > IMHO Shouting make you less rather than more credible. >> \Please repeat that one hundred times until it >> gets through. >> > Endless repetition does not add strength to analysis!! >> No port should *ever* make decisions on a users behalf. Suggestions, yes >> (e.g. OPTIONS that are enabled by default.) Decisions, no. If you depend >> on another port *and* on certain knobs in that dependency being enabled, >> then *tell* the user that during your port's install and let them decide >> how to handle it. DO NOT enable those knobs yourself, no matter how >> tempting it may be. > > IMHO You would sound more credible if you used the IMHO a bit more!! You > might > also gain some respect if you followed your own advice. Make suggestions for > others to consider - do not decide, in advance, they are thick skulled if > they do not agree with you!! >> It is beyond impossible for anyone to know what every user who is >> installing ports already has on their boxes or what they might want to add >> or ***what you might break***. Once you begin making decisions for them, >> you could well stomp all over something that was functioning perfectly >> normally and break a critical box. >> >> DON'T DO IT. That is so Microsoftian it's not funny. > > IMHO Shouting, hectoring and lecturing does not add weight to anyones point > of view. > > These threads have gone far enough, please consider taking this off the FreeBSD mailinglists and discuss this privately. The majority does not like the current ideas and want to see something usefull first. People like Aryeh and David are not really persons that one would see as the persons generating the ports-infrastructure-ng till they have code. If you both keep pissing off people that have a fair share in the ports collection already, please do it by other means, dont crowd the mailinglists with it. Your ideas might be perfect in your world but they aint in ours (till you have shown working code). So please stfu till you have some code and be done with it . -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: Maintain PHP4 and MySQL 4.0
On Wed, January 2, 2008 6:34 pm, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Yeongsik Son wrote: >> I'm working at a hosting company, and the company has got lots of >> clients >> who are using PHP4 and MySQL 4.0. >> According to the Makefile of mysql40-server, it seems to be ripped out >> of >> 4.x, but the clients said they had problems with migrate their databases >> to >> 5.x. >> Also, PHP 4.x will be supported unitl August 8, 2008 according to >> PHP.net. >> FreeBSD 6 seems to be supported until May 30, 2010, according to FreeBSD >> Security Advisory, and I wonder that ports maintainers will continue to >> maintain 4.x until that date. >> Do they have the plan of estimated EOL of PHP and MySQL 4.x? >> If you they got, please let me know about it to force or cooperate with >> the >> clients. > Just grabbing one of the replies to the thread: Also note that PHP 4.x will have a security case-by-case ONLY support till that time, it will not be -supported anymore- at all (just on individual cases). Since PHP is an external third party application, please do not mixup the FreeBSD supported versions and ports with eachother. We will support FreeBSD RELENG_6 still May 30, 2010, PHP support for PHP 4.x will vanish at some point (most likely long before 2010). My personal preference would be that we should double-consider whether we want to keep these versions in the ports system (in the foreseeable future) since the versions are no longer regularly supported, mostly likely contain more and more bugs, and are only fixed on a case by case basis, which potentially could cause harm to users using PHP (and MySQL). That said; the period from 4.X to 5.X in both MySQL and PHP form were rather extensive (in my experience) so people should have had the time already to upgrade their software; if not face it that it will be costly if people will find bugs and cannot resolve them anymore for that specific version (support will be more and more expensive), in addition 5.X is mostly backward compatible with 4.x (except for a few things that are not backward compatible). Do what you want ofcourse (And what your business sees as good practise) but I would strongly suggest upgrading to PHP5(.2.5) and MySQL 5.0.51 Thanks, Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: CFT: Adobe Reader 8 + SCIM/UIM (was Adobe Reader and SCIM)
On Tue, January 8, 2008 8:27 am, Aryeh M. Friedman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Remko Lodder wrote: >> [snip irrelevant info] >> >>> Where do I find acroread8? >> >> [snip irrelevant info] >> >> Sigh, you never -ever- learn do you? >> >> checkout www.freshports.org for a real easy search option, or what >> I just > > Never heard of freshports upto now. What a suprise to read this from you... > >> did: >> >> grep ^acroread /usr/ports/INDEX-6 > > It was not in the ports collection or the index thus the question. it is (As you obviously can see) >> >> acroread8-8.1.1_1|/usr/ports/print/acroread8| >> >> that wasn't SO hard right? > > Now back our regular program of idiot vs. idiot. I prefer the program: Idiot vs someone who at least can find information, a little google query could have helped you as well, but again and again you make the same mistakes. Please -learn-. > > > - -- > Aryeh M. Friedman > FloSoft Systems, Java Developer Tools > http://www.flosoft-systems.com > Developer, not business, friendly. ^ mostly developers are able to find information, and business people do not, are you sure the signature is correct here and didn't you revert the information by accident? -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: CFT: Adobe Reader 8 + SCIM/UIM (was Adobe Reader and SCIM)
[snip irrelevant info] > > Where do I find acroread8? >> [snip irrelevant info] Sigh, you never -ever- learn do you? checkout www.freshports.org for a real easy search option, or what I just did: grep ^acroread /usr/ports/INDEX-6 acroread8-8.1.1_1|/usr/ports/print/acroread8| that wasn't SO hard right? -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: howto use Konqueror as root while another user ?
On Thu, February 14, 2008 8:06 am, Erich Dollansky wrote: > Hi, > > I think he wants to use konqueror locally just to see his files and he > cannot get access to his root files. > > Erich > The advise remains the same, dont do it. Normally documentation and all is just readable as every users, so I dont see the point in using root for that either. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: howto use Konqueror as root while another user ?
On Thu, February 14, 2008 6:47 am, Erich Dollansky wrote: > Hi, > > Piotr wrote: >> hi >> >> howto use Konqueror as root while another user from the wheel group ? >> I've tried kdesu konqueror, but it doesn't work and I get a lot of >> errors. >> I'm using freeBSD 6.3 with KDE 3.5 > > open a terminal window, switch to root and start konqueror. > > It works on my 6.3 machine. > > When you start konqueror from the menu, you are using your own account > but not root. > > Erich >> INSERT BIG HORRIBLE WARNING *** DONT use browsers and mailreaders and the like as root. If something is fishy on the other end (mostly you dont control the other side!) you'll be screwed. Your data will get compromised, and your machine might be joining a ghost network, hitting on others. I strongly STRONGLY (did I say STRONGLY!) dis-advise that you will be using this. //remko Hat: . -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: FreeBSD imapsync port
[EMAIL PROTECTED] wrote: Hello, There are some trouble getting imapsync port running: First, it would be nice adding a patch to change the shebang to /usr/local/bin/perl. I don't expect anybody having perl on FreeBSD at /usr/bin/perl. Secondly imapsync will not run with Mail::IMAPClient from ports, as said by imapsync itself: Subroutine Authuser redefined at /usr/local/bin/imapsync line 2557. imapsync needs perl lib Mail::IMAPClient release 2.2.9 exactly, future imapsync release may suppoort 3.0.x, but sorry not now. See file BUG_IMAPClient_3.xx # Looks like your test died before it could output anything. Mail::IMAPClient provided with imapsync src should be used instead. Regards, Adam #!/usr/bin/perl is installed as symlink for consistency. The line does not have to be changed in my eyes. I also do not see us removing the symlink anytime soon so lets just leave it like that :-). About the rest of the stuff: I cannot judge about that. Cheers Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: FreeBSD imapsync port
On Sat, June 21, 2008 9:09 pm, Ion-Mihai Tetcu wrote: > On Sat, 21 Jun 2008 18:51:15 +0200 > Remko Lodder <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] wrote: >> > Hello, >> > >> > There are some trouble getting imapsync port running: >> > >> > First, it would be nice adding a patch to change the shebang to >> > /usr/local/bin/perl. I don't expect anybody having perl on FreeBSD >> > at /usr/bin/perl. >> > >> > Secondly imapsync will not run with Mail::IMAPClient from ports, >> > as said by imapsync itself: >> > >> > Subroutine Authuser redefined at /usr/local/bin/imapsync line 2557. >> > imapsync needs perl lib Mail::IMAPClient release 2.2.9 exactly, future >> > imapsync release may suppoort 3.0.x, but sorry not now. See file >> > BUG_IMAPClient_3.xx >> > # Looks like your test died before it could output anything. >> > >> > Mail::IMAPClient provided with imapsync src should be used instead. >> > >> > Regards, >> > Adam >> > >> >> #!/usr/bin/perl is installed as symlink for consistency. The line does >> not have to be changed in my eyes. I also do not see us removing the >> symlink anytime soon so lets just leave it like that :-). > > Actually it should. > # PERL - Set to full path of perl5, either in the system > or > # installed from a port, but without the > version number. > # Use this if you need to replace "#!" > lines in scripts. > That does not say it SHOULD be set to /usr/local/bin/perl, all perl scripts I have seen so far are /usr/bin/perl, why break that without general concensus? :) Cheers Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: FreeBSD Port: openospfd-4.0_2
NetOne - Doichin Dokov wrote: Hi, Dear Doichin, Some people from Snow.nl have a test setup that actively uses the openospf that you are refering to. I used that both on 6.X and on 7.x based machines, without any problems. There are around 8 nodes in the network talking in the same OSPF network. If you want you can send me your configuration and we'll try to reproduce it. Thanks, Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: New pkg audit / vuln.xml failures (php55, unzoo)
Please send these things to ports-sect...@freebsd.org so that they can have a look at these please. Thanks, Remko > On 23 May 2015, at 17:30, Roger Marquis wrote: > > FYI regarding these new and significant failures of FreeBSD security > policy and procedures. > > PHP55 vulnerabilities announced over a week ago > <https://www.dotdeb.org/2015/05/22/php-5-5-25-for-wheezy/>) have still > not been ported to lang/php55. You can, however, edit the Makefile, > increment the PORTVERSION from 5.5.24 to 5.5.25, and 'make makesum > deinstall reinstall clean' to secure a server without waiting for the > port to be updated. Older versions of PHP may also have unpatched > vulnerabilities that are not noted in the vuln.xml database. > > New CVEs for unzoo (and likely zoo as well) have not yet shown up in 'pkg > audit -F' or vuln.xml. Run 'pkg remove unzoo zoo' at your earliest > convenience if you have these installed. > > HEADS-UP: anyone maintaining public-facing FreeBSD servers who is > depending on 'pkg audit' to report whether a server is secure it should > be noted that this method is no longer reliable. > > If you find a vulnerability such as a new CVE or mailing list > announcement please send it to the port maintainer and > as quickly as possible. They are whoefully > understaffed and need our help. Though freebsd.org indicates that > security alerts should be sent to this is > incorrect. If the vulnerability is in a port or package send an alert to > ports-secteam@ and NOT secteam@ as the secteam will generally not reply > to your email or forward the alerts to ports-secteam. > > Roger > >> Does anyone know what's going on with vuln.xml updates? Over the last >> few weeks and months CVEs and application mailing lists have announced >> vulnerabilities for several ports that in some cases only showed up in >> vuln.xml after several days and in other cases are still not listed >> (despite email to the security team). > ___ > freebsd-secur...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org" -- /"\ Best regards, | re...@freebsd.org \ / Remko Lodder | remko@EFnet Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News signature.asc Description: Message signed with OpenPGP using GPGMail
Re: portupgrade to Perl 5.10.0 ??
David Southwell wrote: If we had to argue for every port on these terms everyone would spend their time arguing and we would have none atall. It is not as though Perl is an obscure bit of buggy code that none uses. If there is a request then simply a response to your last question is needed. Enough david. So, when can I expect your updated work on the port, build all dependencies to make sure they keep on working etc? I understand that we want to have this as soon as possible, but also do keep in mind that we would like to make sure as much as possible that the code can actually work. I am not aware of the reason for this taking longer then some of you expect. But I am sure that there is a reason. It all remains volunteer work and people might choose to do different things then satisfy your specific need. Not that I am saying we shouldnt do it, but I am stating that there is more then just your wish. Thanks, remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: portupgrade to Perl 5.10.0 ??
David Southwell wrote: On Friday 11 July 2008 14:02:09 Remko Lodder wrote: David Southwell wrote: On Friday 11 July 2008 11:53:50 you wrote: David Southwell wrote: If we had to argue for every port on these terms everyone would spend their time arguing and we would have none atall. It is not as though Perl is an obscure bit of buggy code that none uses. If there is a request then simply a response to your last question is needed. Enough david. So, when can I expect your updated work on the port, build all dependencies to make sure they keep on working etc? I understand that we want to have this as soon as possible, but also do keep in mind that we would like to make sure as much as possible that the code can actually work. I am not aware of the reason for this taking longer then some of you expect. But I am sure that there is a reason. It all remains volunteer work and people might choose to do different things then satisfy your specific need. Not that I am saying we shouldnt do it, but I am stating that there is more then just your wish. Thanks, remko This started because I asked a simple question. Is there a possibility of getting perl 5.10.0 and when. I did not expect the third degree Admittedly I am curious why it is taking six months when most ports do not take that long - but curiosity does not imply personal antagonism, criticsm or sarcasm. Thanks david It also doesn't imply that you can "demand" that people import 5.10.0 because you want it, need it or whatever. It does mean that probably work is underway but that it stalled or something for a reason. "thanks" remko I have hear no demand from anyone only reasonable curiosity following six months delay. It is: 1. reasonable to ask when 2. Courteous to give a reply. David David And I told that you are entitled to do so, but your 'between the lines' stated more then just a question, which I ofcourse can understand. You have had your reply: I think work is underway, we do not know when it's available, but it will be as soon as possible. Thanks, remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: compile failure _www/mod_python3/work/mod_python-3.3.1.
David Southwell wrote: structure or union apxs:Error: Command failed with rc=65536 . The error appears to be telling you that apxs doesn't support the thing you want to do with it. Did you look into your apache build already? //Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: compile failure _www/mod_python3/work/mod_python-3.3.1._SOLVED
David Southwell wrote: On Saturday 26 July 2008 03:37:01 David Southwell wrote: On Saturday 26 July 2008 03:06:10 Remko Lodder wrote: David Southwell wrote: structure or union apxs:Error: Command failed with rc=65536 . The error appears to be telling you that apxs doesn't support the thing you want to do with it. Did you look into your apache build already? //Remko Strange you should say that because I was asking myself the same question. I am just doing a portupgrade -fr apache. I will report results when finished. David BTW I would have thought, if that is the case, that mod_python would have reported a dependency error. The other thing is that we were doing an upgrade from the earlier version which was working fine.. So I doubt whether that is the cause of the error. Well after a massive recompile of portupgrade -fr apache-2.2.9 mod_python3 compiled and installed fine. So problem is solved, the solution to the problem known, but the source of the problem undefined !!! Thnaks all David David Well lets not make a biggy out of that. Obviously things changed in your machine, different dependencies and such, so undefined but probably something you caused yourself. You fixed it, so be happy and enjoy the nice (at least here) weekend :D Cheers Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: ports missing their packages.
On Wed, October 29, 2008 9:09 am, FBSD1 wrote: > It's my understanding that a port maintainer has to install the port for > real any time a change is made to the port make files or a update to the > source of the software to test and verify the changes work as wanted. > Creating the package after this is just one command and a ftp upload to > the > package server. Why are maintainers being given approval to apply their > changes without creating the required package? This is just lax management > on the part of the people who do the authorizing of the changes. Missing > packages increases user frustration level and makes FreeBSD look like its > being mis-managed. > > An alternate solution to this problem is to allow users to upload missing > packages to the package server direct or to a staging ftp server so > port/pkg > management staff can review first and them populate the production package > server. > There is a certain guideline in place which committers follow. If you have constructive feedback surely someone will listen to it. Spitting your frustration is not likely to help. Do note that we have a lot of maintainers which try to satify each and everyone of us, sending messages like this is not going to help *you*. I would have a strong opinion -against- people uploading towarsd the FTP server directly. That will not be done. . To give you a better understanding; We have a ports-cluster which builds packages and uploads them to the appropriate place on the FTP servers, sometimes that takes a little to become available, donate more facilities so that we can do that better. Also note that QAT (a ports tinderbox) runs periodically to make sure every thing is just fine! Thanks, Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: ports missing their packages.
On Wed, October 29, 2008 9:53 am, joeb wrote: > On Wed, October 29, 2008 9:09 am, FBSD1 wrote: >> It's my understanding that a port maintainer has to install the port for >> real any time a change is made to the port make files or a update to the >> source of the software to test and verify the changes work as wanted. >> Creating the package after this is just one command and a ftp upload to >> the >> package server. Why are maintainers being given approval to apply their >> changes without creating the required package? This is just lax >> management >> on the part of the people who do the authorizing of the changes. Missing >> packages increases user frustration level and makes FreeBSD look like >> its >> being mis-managed. >> >> An alternate solution to this problem is to allow users to upload >> missing >> packages to the package server direct or to a staging ftp server so >> port/pkg >> management staff can review first and them populate the production >> package >> server. >> > > There is a certain guideline in place which committers follow. If you have > constructive feedback surely someone will listen to it. Spitting your > frustration is not likely to help. Do note that we have a lot of > maintainers which try to satify each and everyone of us, sending messages > like this is not going to help *you*. > > I would have a strong opinion -against- people uploading towarsd the FTP > server directly. That will not be done. . > > To give you a better understanding; We have a ports-cluster which builds > packages and uploads them to the appropriate place on the FTP servers, > sometimes that takes a little to become available, donate more facilities > so that we can do that better. Also note that QAT (a ports tinderbox) runs > periodically to make sure every thing is just fine! > > Thanks, > Remko > > -- > /"\ Best regards, | [EMAIL PROTECTED] > \ / Remko Lodder | [EMAIL PROTECTED] > Xhttp://www.evilcoder.org/ | > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > > -Original Message- > From: Remko Lodder [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 29, 2008 4:17 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] ORG; [EMAIL PROTECTED] > Subject: Re: ports missing their packages. > > > Well if you have this cluster build process why have some ports never been > built all the way back to release 5.0 like kdenetwork-kopete-0.12.8. That > is > almost 3 years of waiting to get in the cluster build process. There might be reasons for packages not being built, sometimes it's an license issue, sometimes the package does not build etc. It's not something that you can demand that you need a package that it gets there. There is more to it then just build the freaking thing ;-) > I am > grateful > to the maintainers for the great job they do, but completing the job by > building the package is such a small additional task in light of they > already have everything in place to build the package. It's not, we have guidelines that we have to follow in order to keep things managable. > Posting a email to [EMAIL PROTECTED] or posting a bug report about package > missing does not get the missing package built. Its just considered as > background noise. I have brought this problem to light in past years and > new > releases keep coming out with the same packages missing. Then apparantly there is no need for your idea and it will not get implemented. Stating that a package is missing, soit, we build packages all the time and as said there are reasons for some ports not being build into packages etc. First investigate that before complaining this loud. We have been in this proces before with you (Bob was your name back then if I remember correctly). Thnx, Remko > > > > > > -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ 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: pciVideoPtr typedef problem
Apparantly for the ports to function they need a "pciVideoPtr" typedef. It does not seem to include this by default, so it's marked as IGNORE so that it does not get build. On Fri, March 13, 2009 3:24 pm, David Southwell wrote: > > Hi > > Anyone know what is happening here..: > Portupgrade produces the following: > > ** Port marked as IGNORE: x11-drivers/xf86-video-cyrix: > requires pciVideoPtr typedef > ** Port marked as IGNORE: x11-drivers/xf86-video-imstt: > requires pciVideoPtr typedef > ** Port marked as IGNORE: x11-drivers/xf86-video-vga: > is marked as broken: Needs to be removed > ** Port marked as IGNORE: x11-drivers/xf86-video-via: > requires pciVideoPtr typedef > Thanks in advance > > David > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- /"\ Best regards, | re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/ | / \ 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 "freebsd-ports-unsubscr...@freebsd.org"
Re: Lynx -vulnerabilities- is this permanent?
On Wed, Apr 25, 2007 at 03:50:53PM +0800, Foxfair Hu wrote: > Simon L. Nielsen wrote: > >On 2007.04.19 19:01:39 +0800, Foxfair Hu wrote: > >>vuxml -> security-team's baby. > >>Cc added. > > > >The problem is caused by interesting version numbering in the > >www/lynx-current port which now conflicts with www/lynx: > > > >[EMAIL PROTECTED]:lynx-current] make -V PKGNAME > >lynx-2.8.7d4 > > > >Basically the problem was fixed in lynx-current (I assume, I haven't > >checked) 2.8.6d14 which really should have been 2.8.6.d14 to avoid > >problems like this. > > > >[EMAIL PROTECTED]:~] pkg_version -t 2.8.6d14 2.8.6_4 > >[EMAIL PROTECTED]:~] pkg_version -t 2.8.6.d14 2.8.6_4 > >< > > > >I will try to have a look at how to work around this tonight, but I > >don't know if I will get to it today. > > > > [Cut off individuals Cc] > > Can we remove 2nd and 4th entry? Look at the version info on lynx > site, I don't think current statement is a correct one: > > lynx >2.8.6* <2.8.6d14 > ja-lynx >2.8.6* <2.8.6d14 > > Diff as below: > - > cvs diff: Diffing . > Index: vuln.xml > === > RCS file: /home/pcvs/ports/security/vuxml/vuln.xml,v > retrieving revision 1.1317 > diff -u -d -b -w -r1.1317 vuln.xml > --- vuln.xml23 Apr 2007 14:12:10 - 1.1317 > +++ vuln.xml25 Apr 2007 04:01:21 - > @@ -11487,7 +11487,6 @@ > lynx > ja-lynx > 2.8.5_1 > - 2.8.6*2.8.6d14 > > > lynx-ssl Hello Foxfair, I think this is not a good idea; as long as 2.8.6X is vulnerable and some of them are not, we need to mark them up, you are currently proposing to delist it which isn't a really good idea. Cheers, remko -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd mx's in sorbs
Craig Butler wrote: > Hi All > > FreeBSD's mx has somehow got onto SORBS black list and my server is > actively bouncing all the mailing list mails. > > http://www.us.sorbs.net/lookup.shtml?69.147.83.53 > > I will also raise a pr > > Please could you forward this email to the people responsible for the > mail servers > > Cheers > > Craig Butler > Hello Craig, The postmaster team is already aware of the issue, (postmaster@) and can only do so much to try and get us out of the SORBS list. Filing a PR regarding these things is not the way to go, there are no postmasters anywhere on the PR lists so they should be contacted directly when having issues. That said; as mentioned in my PR reply and in the follow-up on this email by Lupe, there aren't many things you can do to avoid getting in the RBL, if enough people (manually or automatically) tell the system you are a spamhost, it will list you without additional checking, SORBS and a couple of others are known (At least to me) to have false positives every now and then. Beyond that people are free to choose the DNSbl they want to, but they should also cope with the fall out from their own decision. Thanks again for the willingness to improve FreeBSD! Cheers, remko -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ 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: mysql-server-3.23.59.n.20050301_3
Bob wrote: > Using the apache port as the standard example of how ports should be > installed > I have noticed 2 things wrong with the mysql-server port. > > First the port allocates the location for the databases to /var/db/mysql. > This location has no space allocated to hold database data. > It should be changed to /usr/local/mysql > > Next the mysql manual should be included in the port just like the apache > manual is. > > These are not technical changes but will make the FBSD port of mysql more > easy to use. > > Looking for feedback from the port team about these suggestions. Ah, you are back on the mailinglists! For the record (beyond the responses from people that already did reply): You are referring to an old release of MySQL in your subject; this is no longer supported (afair) by the MySQL team and you are encouraged to chase the latest GA release (which is 5.0.41 at the moment). Regards, Remko -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the coming cold ... I mean freeze
[LoN]Kamikaze wrote: > I hope that when the freeze comes (wasn't that supposed to happen today?) the > maintainer updates from before the freeze will still get committed. It seems > that under the current workload the committing takes a little longer than > usual. Hi, Yeah the tree is frozen actually, Erwin Lansing send out an email because of that, but it didn't show up on the ports@ mailinglist yet. Hopefully we'll see it soon :-). Cheers remko -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New portmgr member: Pav Lucistnik
On Thu, 2006-11-23 at 20:05 +0100, Erwin Lansing wrote: > Portmgr is pleased to announce that Pav Lucistnik has accepted the > challenge of being a portmgr member. Pav has been with the project for > a long time and is one of our most active committers and bug busters. > He has been working on the ports infrastructure and will now be working > with the other portmgr members on integrating infrastructure patches > and quality assurance in addition to other portmgr tasks. > > Wish him luck! > > -erwin > Muwhahaha! That's the price of being active ! Muwhahaah ! Congratulations Pav! You deserve it, I hope you can keep the enthusiasm you had so far :) Cheers, Remko -- Kind Regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD ** [EMAIL PROTECTED] Unix Engineer Snow B.V ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
