Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Jan 2006 21:15:57 -0600
From:      "Jeremy Messenger" <mezz7@cox.net>
To:        "Donald Byrd" <don@tig.org>
Cc:        gnome@freebsd.org
Subject:   Re: Libsoup broke (part deux)
Message-ID:  <op.s2r8ovkx9aq2h7@mezz.mezzweb.com>
In-Reply-To: <20060103024740.18BE75C1C@precious.home.tig>
References:  <20060103024740.18BE75C1C@precious.home.tig>

next in thread | previous in thread | raw e-mail | index | archive | help
Re-add gnome@FreeBSD.org back in CC, do not lose that.

On Mon, 02 Jan 2006 20:47:36 -0600, Donald Byrd <don@tig.org> wrote:

> Thanks Jeremy, but that's not gong to happen. That's the problem with  
> open
> source; every user is expected to be a senior programmer.

Your wrong, same as for every closed source apps. All of us need the more  
informations. You just can't call to Microsoft and tell them that your  
Windows has crashed, that's it. Of course, they will asking what error are  
you seeing (that one you have never show us), what is version of Windows,  
what were last thing that you did to the Windows and how did you reproduce  
it. Do you have to be programmer for this? No.

> I honestly don't
> have time to debug all the code I use. Maybe that sounds selfish, but if
> I
> have no time left to use the code I debug, then there isn't any point in
> debugging it.

http://www.freebsd.org/gnome/docs/bugging.html
====================================================
A good bug report should at least include the following information:

	-Exact version of the operating system (usually output of uname -a).

	-List of all packages installed on your system (output of pkg_info).

	-Your environment (output of /usr/bin/env).

	-If you are building from ports, note approximately how long it has been  
since you last updated your ports tree. If it has been more than a day, or  
if you have not run portupgrade -a, do not bother sending a bug report  
until you have run cvsup and portupgrade.

	-Information specific for each type of breakage:
		*If a port will not build, provide a full log of the unsuccessful build.
====================================================

This will only taking five to ten minutes.

> I was just trying to let somebody know there was an issue.  
> gnome@freebsd.org
> was listed as the caretaker for libsoap, so I dropped an e-mail and hope  
> for
> the best.

That don't work well. Don't bother to send us an email if you are not  
planning to give us the more informations.

Cheers,
Mezz

> Good luck to you and thank you for all your hard work.
>
> -----Original Message-----
> From: Jeremy Messenger [mailto:mezz7@cox.net]
> Sent: Monday, January 02, 2006 9:41 PM
> To: Donald Byrd
> Cc: gnome@freebsd.org
> Subject: Re: Libsoup broke (part deux)
>
> On Mon, 02 Jan 2006 19:38:01 -0600, Donald Byrd <don@tig.org> wrote:
>
>> I was able to get libsoup 2.2.7 to build when I did a port upgrade on
>> pkgconfig. I guess there is a problem with libsoup's dependencies that
>> something else that pkgconfig depended upon upgraded. Wish I could be
>> more specific.
>
> Please follow this: http://www.freebsd.org/gnome/docs/bugging.html
>
> Cheers,
> Mezz


-- 
mezz7@cox.net  -  mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.s2r8ovkx9aq2h7>