Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Sep 2013 14:11:28 +0200
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Glen Barber <gjb@freebsd.org>
Cc:        David Cornejo <dave@dogwood.com>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: spurious "Service Unavailable"
Message-ID:  <6ABA7660-46F3-4AF7-8106-1037A0072758@FreeBSD.org>
In-Reply-To: <20130919233939.GE2302@glenbarber.us>
References:  <CAFnjQbvPEAmphK4_h0LNcrRgSeRzqzxZW7ghDKozLBan2BTsGg@mail.gmail.com> <20130919233939.GE2302@glenbarber.us>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_3965F554-8EA6-47AA-A85E-C69992C60137
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Sep 20, 2013, at 01:39, Glen Barber <gjb@freebsd.org> wrote:

> On Thu, Sep 19, 2013 at 01:29:35PM -1000, David Cornejo wrote:
>> On CURRENT Revsion 255706
>>=20
>> 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:
>>=20
>> =3D=3D=3D>   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
>> =3D=3D=3D>   Registering installation for dialog4ports-0.1.5_1 as =
automatic
>> Installing dialog4ports-0.1.5_1... done
>> =3D=3D=3D>  Building package for dialog4ports-0.1.5_1
>> Creating package for dialog4ports-0.1.5_1
>> Service unavailable=3D=3D=3D>  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'
>> =3D=3D=3D>  Cleaning for m4-1.4.16_1,1
>>=20
>> Is this dangerous?  Anyone know what's making that happen?
>>=20
>=20
> 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


--Apple-Mail=_3965F554-8EA6-47AA-A85E-C69992C60137
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)

iEYEARECAAYFAlI8O3QACgkQsF6jCi4glqOyEACgyBrkQJN7ZzY58MTzVp9dZ2jm
dOAAnim6J1nbWD7znk2OYis62cZJBbVf
=0XLn
-----END PGP SIGNATURE-----

--Apple-Mail=_3965F554-8EA6-47AA-A85E-C69992C60137--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ABA7660-46F3-4AF7-8106-1037A0072758>