From owner-freebsd-questions@FreeBSD.ORG Wed Jan 21 23:34:12 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2904A7F3 for ; Wed, 21 Jan 2015 23:34:12 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B331FF94 for ; Wed, 21 Jan 2015 23:34:11 +0000 (UTC) Received: from r56.edvax.de (port-92-195-61-84.dynamic.qsc.de [92.195.61.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id A697D3CCDD; Thu, 22 Jan 2015 00:34:01 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t0LNY0Wo002826; Thu, 22 Jan 2015 00:34:00 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 22 Jan 2015 00:34:00 +0100 From: Polytropon To: "William A. Mahaffey III" Subject: Re: frequency of pkg updates Message-Id: <20150122003400.c91771b9.freebsd@edvax.de> In-Reply-To: <54C01E7B.6090403@hiwaay.net> References: <54BFFB43.7060208@networktest.com> <54C01B26.1080407@FreeBSD.org> <54C01E7B.6090403@hiwaay.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2015 23:34:12 -0000 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 >> 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@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@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. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...