Date: Thu, 16 Apr 2015 09:47:52 +0100 From: Matthew Seaman <matthew@freebsd.org> To: freebsd-pkg@freebsd.org Subject: Re: perl version woe Message-ID: <552F7738.1070703@freebsd.org> In-Reply-To: <20150416080754.GA18442@admin.sibptus.tomsk.ru> References: <20150416042738.GA99219@admin.sibptus.tomsk.ru> <552F5FF3.7090908@FreeBSD.org> <20150416080754.GA18442@admin.sibptus.tomsk.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ed3uMmqcC8ElRL9ExhHP46GgGQqDaqsHx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/16/15 09:07, Victor Sudakov wrote: > Do you mean to say, I should be able to safely run "pkg upgrade" and > pkg will resolve this for me? Yes, pretty much. You can run 'pkg upgrade' safely, as it will show you what packages it will install, remove or reinstall and ask you for confirmation before it does. (Assuming you haven't overridden that behaviour in pkg.conf) Check what it tells you carefully, and just hit 'n' if you don't agree with it. In fact, for "difficult" upgrades it tends to do that twice, once with the information in the repository catalog, and then again after it has downloaded all the new packages and so has access to the complete list of files in each package manifest. The second pass of the solver is where it handles all the packages trying to install conflicting files, which is something that tends to happen when doing a switch between different version of perl or ruby or the like. You should be able to avoid the two-solver-passes effect by pulling down the new packages using 'pkg fetch -u' before trying the upgrade. Generally, if pkg can't work out how to upgrade it will end up asking you to remove some items from the upgrade and then end up not doing anything. Although pkg-1.5 should be less prone to that sort of thing no= w. > I'd better try on a copy of the system. To be sure. There's no such thing as "too paranoid" where systems administration is concerned. pkg(8) should not be causing you any grief though, and even if it does, we'd like to know about it[*] so we can avoid the problem in future. Cheers, Matthew [*] Ie. we'd like a copy of your package database and maybe access to your repo, or details of your repo setup so we can try and reproduce the problem. --ed3uMmqcC8ElRL9ExhHP46GgGQqDaqsHx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJVL3c4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnleIP/3YR+W7XH2Gv/O7LV39mICiv NalAuW2vhGtSVkih+9tNO66AwR935BR+3lF9TCKnZ9xe5+QWrfwd54AyjK8nSo0n qj8gaOWrtXPhtbW+6kz25bTQLSRK63kzxof4PPDTeMHXAcvAbIUs/EfXp4A8WWnO 4JWEOwnanPEv3+/AFKt+73g3MDhNuYyEHnSG9KRl2YIrLoh8k0c2g4r07eciRBUe c35wW25BiDbkKJbG0Y9vpTBVloYQbpiLYH6anyDbOJolIiYUlnw12Urz6p6ME70w CUknyDLBLk8D/X3OMjaFmO8sBZaqChd/nzIsKeYHbgCYYuTU8LHdR+dYRA6nNELH mMgIc4gUTkSySfuaoTEpq0/NM2fn7AD8x31W6yq2TrhT7CDSW3IDStU7AJepgymf lr7LSra/vG9u1O5koeYNGgRZW/FpwhMnjbKKEBYKz5Y9/vnKtPbBySZjTiHhzRye rsMdQjg+f1Slu+eErU6NSc8zV0dR1x5fNFvARJKbP7OU+vMHVSv3i8lxFNkoC7HP ZHJQqkAEk44VMsWYaeq5D56U37h76YZ5cY1ilE4KhyEOgxvMMA6p/YEDRb88DD7y lJmikQ9onYEOKxtaLAdPJ5oOKrklAwKGC4NpY4Ee6iB6yUIANJKkak2veK3SPCUY ArmrMFOGhMubqcAvOPzj =RRXB -----END PGP SIGNATURE----- --ed3uMmqcC8ElRL9ExhHP46GgGQqDaqsHx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?552F7738.1070703>