Date: Sun, 12 May 2019 17:17:02 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-pkg@freebsd.org Subject: Re: pkg upgrade has no description of what -x does Message-ID: <287b9740-eae6-26b5-ee25-0dbf85e890a2@FreeBSD.org> In-Reply-To: <20190512153756.GC15462@rpi3.zyxst.net> References: <20190512122930.GB15462@rpi3.zyxst.net> <fa9bf06a-df5c-bc10-23c6-a8880361611f@FreeBSD.org> <20190512153756.GC15462@rpi3.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PVRHrX1P7faozfHOzKgrTw1XQ03HauDas Content-Type: multipart/mixed; boundary="6shDGfmKppFEVHap1ISxeM98rruaszxns"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-pkg@freebsd.org Message-ID: <287b9740-eae6-26b5-ee25-0dbf85e890a2@FreeBSD.org> Subject: Re: pkg upgrade has no description of what -x does References: <20190512122930.GB15462@rpi3.zyxst.net> <fa9bf06a-df5c-bc10-23c6-a8880361611f@FreeBSD.org> <20190512153756.GC15462@rpi3.zyxst.net> In-Reply-To: <20190512153756.GC15462@rpi3.zyxst.net> --6shDGfmKppFEVHap1ISxeM98rruaszxns Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 12/05/2019 16:37, tech-lists wrote: > On Sun, May 12, 2019 at 02:59:17PM +0100, Matthew Seaman wrote: >=20 >> Good catch -- that's definitely an omission from the man page. >=20 > happy to help ;) >=20 > I found this on my way to trying to figure out how to get pkg upgrade t= o > exclude a pattern from the upgrade. Is there a way? or does this break > something else? That's not really supported. Partial upgrades are a bit of a mine-field and can lead to your system getting into an inconsistent state with broken functionality entirely possible. Which isn't to say that you absolutely /can't/ do a partial upgrade, just that you will need to study exactly what pkg(8) proposes changing and understand how that could affect other parts of your system. The general recommendation is just to upgrade everything -- the package repository will have been build as a self-consistent set of packages, thus avoiding that particular pitfall. What exactly are your reasons for avoiding upgrading some packages? In most cases there are work-arounds, including, but not limited to, just waiting for a few days so that a fix can be committed to the ports and an updated package set produced. Cheers, Matthew --6shDGfmKppFEVHap1ISxeM98rruaszxns-- --PVRHrX1P7faozfHOzKgrTw1XQ03HauDas Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlzYRv5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcACgkQAFE/EOCp 5OfNFRAAlsFXP88ZNdlSSKHKTp1xRrD8oJ646IVMw8GImBuz/eEIcDTCIPZPLNa8 Wm/xbwvQlBFVKiktX0BFkNx3VLHQKL014JtbuDJyr8+WsOY1f1C/natesmTvscHY 8BCuhFuQBdpar/TfPW/A6bQIr1Obqn8Vl+TwSwXBUMw86lQ3rVWO/7wGVRoQpuNn CFmMQvnV6a+wXC2YSd/oZliNPqfaD00A1JyWHGZ9T28SPeJxW8oaBx9ldO/65blq X9W+miQmHfPxsIC9XXlV6BrTOPgUcAkOsP5F30yxA5PgljSoH8avslUuNxgF+zkz 8gNqoKqy7A2sGrRiJi9hbPJ3cSXMPyjg0gnyT2XVvfDUNIaRb7Pbf2gxkfvS+eHL OBCm9x55FJfta1C7gjUNEkE+6exDWDtNHFwtXCnMzsSOmHgAd40jUmnyNC9xwYRJ 1elekAV1xHaKLJsvvXShb6dnZw4tDoJ/y07eksz88/Lh4I45j/xPdE+bxiVjfpj3 duO3eURcBATqw0ousyIzxJEBwbfMrmRtBAbSeWQJP9JMN1h0zlnVZeg+58fz4Alo 1uylhZAxd1GsYFyHEgLAn9tNWQ1gi7mpR0MmuvJ0/kQoiaclBvRfF058QjEiqZmS cRdcFfI1OymbuFNMX3D/BH4Fqyld9D0U1HKY922d7TXzCh6PW5I= =8KSX -----END PGP SIGNATURE----- --PVRHrX1P7faozfHOzKgrTw1XQ03HauDas--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?287b9740-eae6-26b5-ee25-0dbf85e890a2>