Date: Sat, 08 Mar 2014 20:51:32 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: the reason for upgraded pkgs Message-ID: <531B82D4.5020208@FreeBSD.org> In-Reply-To: <20140308202328.289540@gmx.com> References: <20140308202328.289540@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--eLVNwgCK3jxPXMuwGqaagJQu5CxCxN8lX
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 08/03/2014 20:23, eocene wrote:
> I'm new to freebsd, running 10.0.
>=20
> With pkg upgrade, is there a way to know what the reasons are behind
> each upgraded package? For instance, "This fixes security problem
> such-and-such", "This one fixes this handful of bugs", "This one
> brings these new features, has these new configuration options, etc."
You get some information from pkg upgrade, but it's mostly about
packages that were reinstalled for indirect reasons -- because a package
they depend on was upgraded. Packages that are upgraded directly don't
have any sort of explanation accessible through pkg(8). But direct
upgrades only occur when there's a new version available.
If you want to find out why a new version is available, then there are
two main resources:
pkg audit
Running this *before* upgrading will flag up any packages you have
installed that have know security vulnerabilities. Usually that means
there will be an upgrade to the vulnerable package, but sometimes that
can be delayed for a few days.
http://svnweb.freebsd.org/ports/head/, or equivalently the
SVN-Ports-All mailing list
These allow you to see the commit messages for any updates to the ports
you're interested in. These should describe what changed about the port
in that commit -- which may just say 'upgraded to version foo' when
pulling in an update from upstream. Many committers will put a pointer
to any change logs or release notes for a version upgrade, or include a
summary of what changed with the new version, but this is not a practice
universally followed.
A large number of updates at the moment are due to infrastructure
changes within the ports itself, much of which has been inspired by the
advent of pkg(8) and the imminent demise of the old pkg_tools. There's
going to be quite a lot of this sort of activity going forwards over the
next year or two as the switch to pkg(8) allows a number of ideas which
the ports has been in great need of finally to be implemented.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
--eLVNwgCK3jxPXMuwGqaagJQu5CxCxN8lX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJ8BAEBCgBmBQJTG4LcXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC
QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATck0QAIlstFcEZ+cycdgrqJTz9AoD
FC17jsMWiJAJ08EpkNZhvtviAWw5Dm/rAjXFbP2mHalYoxls8E7ql2nkJAaxqamo
8+tdkvUoC3MNgOB2/Tn4mEStlFA9pzJlkIxvtIQd9P3p3wfdsUachayoKpvExNDb
g+jmIbEFpKSKUpvMuNfWTpD2n1Ud50Znl8Jtc/XfQMFLkmF0ZhBIW5dtFbvmo/om
twNjE7eAXnxWlOcf9OnMrMPFxiSMM2ppCbJLnQz/S4NBTaE9epbcltM9XCI03LgX
1DowAu4GoPVAHDKg7wmg7c2McJU/iQ/JaT3udvcbanN6p9DTtGl0L5A57iE8EH8m
lvwIoit6v2nnqKLvULHbzjtsl0mKWkw7lNecoAJWi/bRHfYVxCCbawLCVdmZH5Ob
n7l+gO/wu9WuB7jc9+QTHiU7C9a94JzT1ZhTkQPnNQ98W1xBifWFsCDb5ZcGF+R3
XvRNffXCLoFHwbQa2sV762DB+9pOnj82kMxM9rZ5mff94DIPKhi3nK/oPW0CJIaq
mPFb1xqiloGpUY21xkOpO3APj9oKylXoqFFg7qjuX9teYJQqRLdn04Y+VJNDPodL
3SmqzN4ao9whG/uPhfgiKgptlWiMssBVt9JBt7T05fXcbFwoKjPkBmXjWDSSSEs9
8/d/W15t1PeIlsICh1u/
=+sP5
-----END PGP SIGNATURE-----
--eLVNwgCK3jxPXMuwGqaagJQu5CxCxN8lX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?531B82D4.5020208>