Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Apr 2015 21:41:28 +0200
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Alex Aminoff <aminoff@nber.org>
Cc:        freebsd-pkg@freebsd.org
Subject:   Re: after pkg 1.5.1 pkg upgrade seg faults
Message-ID:  <20150417194127.GY39658@ivaldir.etoilebsd.net>
In-Reply-To: <55315C92.4000005@nber.org>
References:  <55315C92.4000005@nber.org>

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

--oWEYV0WmY9Kcrzh0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 17, 2015 at 03:18:42PM -0400, Alex Aminoff wrote:
> We are running FreeBSD 10.1-RELEASE. pkg likes to upgrade itself before=
=20
> doing anything else, so I went ahead and accepted the self-upgrade to=20
> pkg 1.5.1. Unfortunately, now pkg upgrade seg faults.
>=20
>=20
>   # pkg check -r
> Checking all packages:  16%
>=20
> Checking all packages: 100%
>   # pkg update -f
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%    944 B   0.9kB/s    00:01
> Fetching packagesite.txz: 100%    5 MiB   1.3MB/s    00:04
> Processing entries: 100%
> FreeBSD repository update completed. 23839 packages processed.
>   # pkg upgrade
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> All repositories are up-to-date.
> Checking for upgrades (352 candidates):  25%
> p5-libapreq2 has no direct installation candidates, change it to=20
> p5-libapreq2? [Y/n]:
> Checking for upgrades (352 candidates): 100%
> Processing candidates (352 candidates): 100%
>=20
> openssl-1.0.1_16 is locked and may not be modified
> Child process pid=3D4705 terminated abnormally: Segmentation fault
>=20
>=20
> I can still do pkg upgrade on individual packages, its just the overall=
=20
> pkg upgrade that segfaults.
>=20
> I have googled and found some references to segfaults in pkg, but they=20
> all seem to be referring to older versions. I hope this is a known thing=
=20
> that there is a simple fix for; I think it is unlikely that we are the=20
> first to discover a problem.
>=20

Can you run pkg -o DEBUG_LEVEL=3D4 upgrade ?

and send me the output (beware this might be very verbose)

And yes you are the first to report that...

Best regards,
Bapt

--oWEYV0WmY9Kcrzh0
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlUxYecACgkQ8kTtMUmk6Ez71gCgvGGPGlreYytKMcQBQqnCrsS3
Su8An1vIZz34fsuEZG4B1vPo8p45s8mo
=pgzi
-----END PGP SIGNATURE-----

--oWEYV0WmY9Kcrzh0--



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