Re: spurious "Service Unavailable"

From: Dimitry Andric <dim_at_FreeBSD.org>
Date: Fri, 20 Sep 2013 14:11:28 +0200
On Sep 20, 2013, at 01:39, Glen Barber <gjb_at_freebsd.org> wrote:

> On Thu, Sep 19, 2013 at 01:29:35PM -1000, David Cornejo wrote:
>> On CURRENT Revsion 255706
>> 
>> I am trying to rebuild a bunch of ports in screen and I'm getting the
>> string "Service unavailable" in the output between the package creation and
>> the cleaning phases for each port:
>> 
>> ===>   Generating temporary packing list
>> install  -o root -g wheel -m 555   dialog4ports /usr/local/bin/dialog4ports
>> install -o root -g wheel -m 444 dialog4ports.1.gz  /usr/local/man/man1
>> ===>   Registering installation for dialog4ports-0.1.5_1 as automatic
>> Installing dialog4ports-0.1.5_1... done
>> ===>  Building package for dialog4ports-0.1.5_1
>> Creating package for dialog4ports-0.1.5_1
>> Service unavailable===>  Cleaning for dialog4ports-0.1.5_1
>> --->  Cleaning out obsolete shared libraries
>> --->  Reinstalling 'm4-1.4.16_1,1' (devel/m4)
>> --->  Building '/usr/ports/devel/m4'
>> ===>  Cleaning for m4-1.4.16_1,1
>> 
>> Is this dangerous?  Anyone know what's making that happen?
>> 
> 
> These are, as far as I can tell, harmless messages.  It is due to
> libarchive and statically linked binaries (pig-static).

See this recent thread:
http://lists.freebsd.org/pipermail/freebsd-current/2013-August/043824.html

It is a problem in our iconv implementation in libc, which should really
be fixed before 10.0-RELEASE.

-Dimitry


Received on Fri Sep 20 2013 - 10:11:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:41 UTC