On Wed, Nov 04, 2020 at 01:12:23PM -0500, Jeremy O'Brien wrote:
> On Wed, Nov 4, 2020, at 11:37, Chris Bennett wrote:
> > Easy answer. System libraries that these packages were built with have
> > changed. Package is the same except for being rebuilt with newer
> > libraries.
> >
>
> This
On Thu, Nov 5, 2020, at 03:38, Stuart Henderson wrote:
> The current package on mirrors has changed since your downloaded file
> (at least glib2 was updated) so maybe it's just because you're looking
> at an old file.
>
Sigh. I double-checked my /etc/installurl. Apparently it’s set to
On 2020-11-04, Chris Bennett wrote:
> On Mon, Nov 02, 2020 at 07:03:27AM -0500, Jeremy O'Brien wrote:
>> Hey misc,
>>
>> I'm trying to understand the various scenarios that can trigger a package
>> update in 'pkg_add -u'. I thought package updates were triggered only
>> through explicit
On Wed, Nov 4, 2020, at 11:37, Chris Bennett wrote:
>
> You haven't supplied any information for answering this question well.
> Are you running -current and updating to a new snapshot?
>
I upgraded to a new snapshot.
> Easy answer. System libraries that these packages were built with have
>
On Mon, Nov 02, 2020 at 07:03:27AM -0500, Jeremy O'Brien wrote:
> Hey misc,
>
> I'm trying to understand the various scenarios that can trigger a package
> update in 'pkg_add -u'. I thought package updates were triggered only through
> explicit version bumps, or signature changes. I'm seeing
Hey misc,
I'm trying to understand the various scenarios that can trigger a package
update in 'pkg_add -u'. I thought package updates were triggered only through
explicit version bumps, or signature changes. I'm seeing that that isn't always
the case however, as shown here:
x1$ pkg_info -S
6 matches
Mail list logo
