PDA

View Full Version : FREEBSD PORT BROKEN



T. J. Angstman
2004-11-01, 10:21
> I'm sorry to hear it does not work for you, it works here. I can't do

> anything to help you if you don't provide a bug report with some content

> in it.

My previous post's subject did not identify the Freebsd Port. Sorry for not
linking this up. I want to track the released port for ease of upgrading,
but everything is working now with the 10/31 nightly. I had previously
posted the following information:

I installed a new FreeBSD server (5.2.1). Rather than download from slim's
website, I installed the FreeBSD port which installed perfectly without
error. I decided to simply use the FreeBSD port and track the released
versions rather than track the nightly upgrades, as I have done in the past.
The version in the FreeBSD ports collection is 5.3.1.

The server is up and running and can play Shoutcast streams by using my
remote. When connecting via a browser, I just get a blank html screen, the
source of the page served up looks like this:


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<HTML><HEAD>

<META http-equiv=Content-Type content="text/html;

charset=windows-1252"></HEAD>

<BODY></BODY></HTML>


Using the KDE browser I get the little slimserver icon in the address bar,
so I know it is connecting to the server. Obviously I cannot set any of the
options, as nothing appears to configure.

T. J. Angstman


-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Brooks Davis
Sent: Monday, November 01, 2004 3:46 AM
To: Slim Devices Discussion
Subject: [slim] FREEBSD PORT BROKEN

On Sun, Oct 31, 2004 at 08:03:49PM -0700, Thomas J. Angstman wrote:
> OK. After trials and tribulations, I finally figured it out that the
> FreeBSD port is broken. It does not work with a clean install. The
> only way to fix it was to deinstall the port and then delete all the
> configuration files and rm -r /usr/local/slimserver. Then, I simply
> extracted the tar.gz from slimdevices and installed normally.
> Everything is back up and running now.

I'm sorry to hear it does not work for you, it works here. I can't do
anything to help you if you don't provide a bug report with some content
in it.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4

Brooks Davis
2004-11-01, 14:20
On Mon, Nov 01, 2004 at 10:21:21AM -0700, T. J. Angstman wrote:
> > I'm sorry to hear it does not work for you, it works here. I can't do
>
> > anything to help you if you don't provide a bug report with some content
>
> > in it.
>
> My previous post's subject did not identify the Freebsd Port. Sorry for not
> linking this up. I want to track the released port for ease of upgrading,
> but everything is working now with the 10/31 nightly. I had previously
> posted the following information:
>
> I installed a new FreeBSD server (5.2.1). Rather than download from slim's
> website, I installed the FreeBSD port which installed perfectly without
> error. I decided to simply use the FreeBSD port and track the released
> versions rather than track the nightly upgrades, as I have done in the past.
> The version in the FreeBSD ports collection is 5.3.1.
>
> The server is up and running and can play Shoutcast streams by using my
> remote. When connecting via a browser, I just get a blank html screen, the
> source of the page served up looks like this:
>
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>
> <HTML><HEAD>
>
> <META http-equiv=Content-Type content="text/html;
>
> charset=windows-1252"></HEAD>
>
> <BODY></BODY></HTML>
>
>
> Using the KDE browser I get the little slimserver icon in the address bar,
> so I know it is connecting to the server. Obviously I cannot set any of the
> options, as nothing appears to configure.

Hmm, this is weird. My guess would be a problem with the template
library. You might try running "make depends" in
/usr/ports/audio/slimserver. I've seen cases where portupgrade fails
to install dependences of upgraded ports and we grew several more in the
last update.

-- Brooks