portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage

[Stacey Roberts]

Hi Adam,

----- Original Message -----
From: "Adam Weinberger <adamw at FreeBSD.org>"
To: To Stacey Roberts
Date: Sun, 08 Feb, 2004 21:42 GMT
Subject: Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage

> >> (02.08.2004 @ 1625 PST): Stacey Roberts said, in 4.1K: <<
> > Hello Adam,
> > 
> > ----- Original Message -----
> > From: "Adam Weinberger <adamw at FreeBSD.org>"
> > To: To Stacey Roberts
> > Date: Sun, 08 Feb, 2004 17:23 GMT
> > Subject: Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage
> > 
> > > >> (02.08.2004 @ 0625 PST): Stacey Roberts said, in 15K: <<
> > > > Hello Adam,
> > > > 
> > > > I've just ran the commands that Mezz recommended, with the same results, same errors:
> > > > 
> > > > # portsclean -C
> > > > Cleaning out /usr/ports/*/*/work...
> > > > Delete /usr/ports/net/gnomemeeting/work
> > > > done.
> > > > Demon# portupgrade -f gnomemeeting\*
> > > > --->  Upgrading 'gnomemeeting-0.98.5_1' to 'gnomemeeting-0.98.5_2' (net/gnomemeeting)
> > > > --->  Building '/usr/ports/net/gnomemeeting'
> > > > ===>  Cleaning for gnomemeeting-0.98.5_2
> > > > ===>  Vulnerability check disabled
> > > > ===>  Extracting for gnomemeeting-0.98.5_2
> > > > >> Checksum OK for gnomemeeting-0.98.5.tar.bz2.
> > > > ===>  Patching for gnomemeeting-0.98.5_2
> > > > ===>  Applying FreeBSD patches for gnomemeeting-0.98.5_2
> > > > ===>   gnomemeeting-0.98.5_2 depends on file: /nonexistent - found
> > > >
> > > > <snip, snip>
> > > >
> > > > checking for PTLib includes...
> > > > checking for /usr/ports/net/gnomemeeting/../../devel/pwlib/work/pwlib/include/ptlib/pprocess.h... no
> > > > configure: error: You need PTLib's header files to build GnomeMeeting
> > > > ===>  Script "configure" failed unexpectedly.
> > > > Please report the problem to roger at FreeBSD.org [maintainer] and attach the
> > > > "/usr/ports/net/gnomemeeting/work/gnomemeeting-0.98.5/config.log" including
> > > > the output of the failure of your make command. Also, it might be a good idea
> > > > to provide an overview of all packages installed on your system (e.g. an `ls
> > > > /var/db/pkg`).
> > > > *** Error code 1
> > > >   
> > > > Stop in /usr/ports/net/gnomemeeting.
> > > > ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade63486.0 make
> > > > ** Fix the problem and try again.
> > > > ** The following packages were not installed or upgraded (*:skipped / !:failed)
> > > >         ! net/gnomemeeting (gnomemeeting-0.98.5_1)      (configure error)
> > > > #
> > > > 
> > > > What would then be the best way forward now?
> > > > 
> > > > Regards,
> > > > 
> > > > Stacey
> > > >> end of "Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage" from Stacey Roberts <<
> > > 
> > > Stacey -
> > > 
> > > If you have a file /nonexistent on your system, delete it.
> > > 
> > 
> > Err.., I've just noticed that there are two similarly sounding dirs:
> > ~ $ ls /
> > COPYRIGHT       dev             kernel.GENERIC  nonexistant     stand
> > bin             dist            kernel.old      nonexistent     sys
> > boot            etc             mnt             proc            tmp
> > cdrom           home            modules         root            usr
> > compat          kernel          modules.old     sbin            var
> > stacey at Demon ~ $
> > 
> > One was produced when I created a machine account (this server acts as the samba PDC here on my network):
> > stacey at Demon ~ $ ls -la /nonexistent/
> > total 20
> > drwxr-xr-x   2 <snipped>$       <snipped>$       512 Nov 30 13:30 .
> > drwxr-xr-x  20 root       wheel      512 Dec  6 18:27 ..
> > -rw-r--r--   1 <snipped>$  <snipped>$  771 Nov 30 13:30 .cshrc
> > -rw-r--r--   1 <snipped>$  <snipped>$  255 Nov 30 13:30 .login
> > -rw-r--r--   1 <snipped>$  <snipped>$  165 Nov 30 13:30 .login_conf
> > -rw-------   1 <snipped>$  <snipped>$  371 Nov 30 13:30 .mail_aliases
> > -rw-r--r--   1 <snipped>$  <snipped>$  331 Nov 30 13:30 .mailrc
> > -rw-r--r--   1 <snipped>$  <snipped>$  801 Nov 30 13:30 .profile
> > -rw-------   1 <snipped>$  <snipped>$  276 Nov 30 13:30 .rhosts
> > -rw-r--r--   1 <snipped>$  <snipped>$  852 Nov 30 13:30 .shrc
> > stacey at Demon ~ $
> > 
> > So.., I'm not sure of the meaning behind your thinking that I should blast this dir
> > 
> > Do get back to me on this.., I'm very intrigued by this suggestion.
> > 
> > Regards,
> > 
> > Stacey
> >> end of "Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage" from Stacey Roberts <<
> 
> Yes. You should not have a user with /nonexistent as its home dir.
> Change that user's homedir to something else and remove /nonexistent and
> gnomemeeting will build fine.

Err.., /nonexistent is where a lot of system accounts are:
www, pop, nobody, gdm, as well as the machine accounts have been *created by the system* in that location. This wasn't something I elected to do..,

> 
> This sort of thing is why homedirs go under /home or /usr/home.
> 

Understood, but as I mentioned above.., this would not have been a setting that I would have chosen.., Saying that., I'm now reluctant to pursue (please don't take this wrongly!) this action given that www and pop are listed with /nonexistent as their respective *system-designated* home account names..,

One the other hand.., if this is where these account home dirs are created, why would gnomemeeting be looking to the same location for build-dependent configs? Also, why wasn't this an issue *before* having to upgrade to Gnome2-2.4.2?

Regards,

Stacey

> # Adam
> 
> 
> --
> Adam Weinberger
> adam at vectors.cx // adamw at FreeBSD.org // adamw at magnesium.net
> http://www.vectors.cx

-- 
Stacey Roberts
B. Sc (HONS) Computer Science

Web: www.vickiandstacey.com