Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Dec 2016 09:56:10 -0500
From:      mfv <>
To:        Peter Harrison via freebsd-questions <>
Cc:        Peter Harrison <>
Subject:   Re: Chromium pkg not updated...
Message-ID:  <20161213095610.7736fb8a@gecko4>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> On Mon, 2016-12-12 at 22:52 Peter Harrison via freebsd-questions
> <> wrote:
>Hello list.
>Anyone know why the chromium pkg doesn't seem to be being updated even
>though the port is?
>Peter Harrison.
> mailing list
>To unsubscribe, send any mail to


I noticed the same situation and sent the following message to
freebsd-pkg yesterday:
Infrequently, I've noticed that the pkg system seems to get
constipation, that is, a build process is marked as stopped:done: but
the repository is not updated.

The data for the most recent incident follows:

According to the
date/time of the last repository is dated 2016-Dec-06 10:16, that is, 6
days ago.

However since then there have two builds as per

 Build#  stopped:done:
 ------  -----------------
 428092  2016-12-09  08:02
 428262  2016-12-11  08:10

Thus, the last build was finished more than a day ago.

But a 'pkg update' results in the following message:

Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.

Just wondering why a build status is marked as stopped:done: but the
repository is not updated.

In any event I'm very pleased with the pkg system.  Many thanks and
kudos to the developers.
No reply so far.

Cheers ...


Want to link to this message? Use this URL: <>