frequency of pkg updates

[William A. Mahaffey III]

On 01/21/15 17:34, Polytropon wrote:
> On Wed, 21 Jan 2015 15:47:39 -0600, William A. Mahaffey III wrote:
>> On 01/21/15 15:33, Matthew Seaman wrote:
>>> On 2015/01/21 19:17, David Newman wrote:
>>>> How often is the FreeBSD pkg repository updated?
>>>>
>>>> Asking because 'sudo pkg audit' sometimes shows vulnerabilities in one
>>>> or more packages, yet 'sudo pkg update && sudo pkg upgrade -f <pkg
>>>> name>' offers only to reinstall the vulnerable version.
>>>>
>>>> An updated pkg can take days to show up. The ports tree is updated much
>>>> faster, but I'm trying to move to pkg where possible. (Yes, I know I
>>>> could run poudriere and create a pkg repository, but I'm asking here
>>>> about FreeBSD's pkg system.)
>>>>
>>>> This is on 10.1-RELEASE-p4 amd64.
>>> Packages are built weekly from a snapshot of the ports taken on a
>>> Wednesday at (I think) 01:00 UTC.  It's definitely some time on
>>> Wednesday though.  The package builders then build all of the packages
>>> for all the supported release branches + HEAD, which takes until some
>>> time the following weekend.
>>>
>>> Thus if a package of interest to you updates on a Thursday, it can be
>>> about 10 days before an updated package is available from the repos.
>>>
>>> More hardware is being procured to cut down the time it takes to build
>>> packages, so the update frequency should improve.
>>>
>>> 	Cheers,
>>>
>>> 	Matthew
>>>
>>> _______________________________________________
>>> freebsd-questions at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>>>
>> Hmmmm .... So the individual pkg's are actually built by .... who ? The
>> pkg maintainer ? A central coordinating body ? Somebody/Something else ?
> It's an automated build system, a build cluster I think.
> The port maintainers are responsible for making sure the
> Makefile and the patches work, they primarily do the porting
> (when the original software has been created on and for Linux)
> and the testing. Then they commit the changes to the official
> ports tree, for example, when they updated foo-1.2.3 to foo-1.2.4.
> The build system then uses that version for the next scheduled
> build session.
>
> Note that the update might be in the ports tree a bit earlier
> than the binary packages become available. If you urgently
> require bleeding-edge ports, using portsnap (or probably
> even better: svn) is the way to go. With binary packages,
> you'll have to wait a little.
>
>
>
>> Inquiring minds wanna know .... They might also be interested in
>> contributing hardware if that would noticeably speed things up ;-) ....
> Provide a time machine so the scheduled day of the week can
> be deployed to _all_ of the seven weekdays at once. ;-)

I'll get right on that ;-) ....

-- 

	William A. Mahaffey III

  ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                            -- Gen. George S. Patton Jr.