From owner-freebsd-current@FreeBSD.ORG Tue Sep 21 14:14:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1471B16A4CE for ; Tue, 21 Sep 2004 14:14:56 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBA4C43D1F for ; Tue, 21 Sep 2004 14:14:55 +0000 (GMT) (envelope-from rob@pythonemproject.com) Received: from [192.168.1.102] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc13) with ESMTP id <2004092114145401500eip4ee> (Authid: europax); Tue, 21 Sep 2004 14:14:55 +0000 Message-ID: <415037A2.9060702@pythonemproject.com> Date: Tue, 21 Sep 2004 07:16:02 -0700 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040816 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-current@freebsd.org References: <20040920114237.GA87896@sirius.speicher.org> <20040921122925.GB93142@sirius.speicher.org> In-Reply-To: <20040921122925.GB93142@sirius.speicher.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: XMMS Fatal error at line 83 (core dumped) FreeBSD 6.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 14:14:56 -0000 Geoff Speicher wrote: > On Tue, Sep 21, 2004 at 07:07:30AM +0200, John Asher wrote: > >>Thank you for helping me. >> >>xmms works now, however if I want to listen to winamp radio, I have other >>lib errors. >> >>I am now upgrading all ports depending on gettext, (after deleting and >>upgrading gettext) as I have seen in a newsgroup, that will probably solve >>that library error. >> >>Are there some ways I can protect myself in future for this type of >>problems? > > > Please copy the list in your replies to me so that others can benefit > from and/or contribute to this discussion. > > To protect yourself against the unexpected in the future, you can follow > the following advice excerpted from the FreeBSD Handbook, section > 19.2.1.4 [Using FreeBSD-CURRENT]: > > Join the freebsd-current and the cvs-all lists. This is not > just a good idea, it is essential. If you are not on the > freebsd-current list, you will not see the comments that people > are making about the current state of the system and thus will > probably end up stumbling over a lot of problems that others > have already found and solved. Even more importantly, you will > miss out on important bulletins which may be critical to your > system's continued health. > > The cvs-all list will allow you to see the commit log entry for > each change as it is made along with any pertinent information > on possible side-effects. > > In this case, you would have seen this particular issue discussed on > freebsd-current several times over the course of the last month or two, > and it probably would have allowed you to preempt it from ever happening > to you. > > In addition to the above, don't forget to: > > - Read /usr/src/UPDATING > - Read /usr/ports/UPDATING > > every time you cvsup. > > Geoff > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Is xmms back in ports now? I have been compiling it from the www.xmms.org source for some time now with very good success. Sincerely, Rob Lytle