From owner-freebsd-pkg@FreeBSD.ORG Fri Apr 17 19:41:32 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F2FAE9A for ; Fri, 17 Apr 2015 19:41:32 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 109EC1AF for ; Fri, 17 Apr 2015 19:41:32 +0000 (UTC) Received: by widdi4 with SMTP id di4so33698732wid.0 for ; Fri, 17 Apr 2015 12:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=O3yQt1Y1b/FSRYNsqTTqiEYpVrXh0uNcNVkBE8kwiVo=; b=qdKSEF9MxHF4yh3P11mJ8QDE/LX+BYj9MfixQM6S9trXfbbqo0FjKYqgUYuG3iFTPk Oy5paoKx0FbTO5VO/yAzpE9pudeKpUFbmy69VsYWuS2GNhvLUl6WaNmoOsDs8tu8/0pz TlDoHcXepReFH9xGHReVFYBgcMEWjpNCTMAddKZGvRhJ1xe+PiJ4nKElasyPWqcCbOqa PCU0PFZlcKu8Mi/I3sM/KgbRI66RQPRpTGsaC/WlZeJU2yXITW4C26xzukEgStCVMVoI OE+vG+sxyMznIgWLnTC+/CABCOMG+fmzhkoG73wtNhDZ3zj/AAgE1VpjID6GW/sBwI8Z hfPQ== X-Received: by 10.194.237.34 with SMTP id uz2mr8646866wjc.157.1429299690476; Fri, 17 Apr 2015 12:41:30 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id js3sm15930938wjc.5.2015.04.17.12.41.29 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Apr 2015 12:41:29 -0700 (PDT) Sender: Baptiste Daroussin Date: Fri, 17 Apr 2015 21:41:28 +0200 From: Baptiste Daroussin To: Alex Aminoff Cc: freebsd-pkg@freebsd.org Subject: Re: after pkg 1.5.1 pkg upgrade seg faults Message-ID: <20150417194127.GY39658@ivaldir.etoilebsd.net> References: <55315C92.4000005@nber.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oWEYV0WmY9Kcrzh0" Content-Disposition: inline In-Reply-To: <55315C92.4000005@nber.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2015 19:41:32 -0000 --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--