From owner-freebsd-ports@freebsd.org Mon Nov 12 16:21:08 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F03A110A13F for ; Mon, 12 Nov 2018 16:21:08 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E85A6753F8 for ; Mon, 12 Nov 2018 16:21:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from leaf.local (unknown [88.202.132.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 8FA1361D5 for ; Mon, 12 Nov 2018 16:21:05 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/8FA1361D5; dkim=none; dkim-atps=neutral Subject: Re: pkg falls behind port version - how do ports become pkg's? To: freebsd-ports@freebsd.org References: <09E24A9CF2EF0A4276923670@[10.12.30.106]> From: Matthew Seaman Message-ID: Date: Mon, 12 Nov 2018 16:20:52 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <09E24A9CF2EF0A4276923670@[10.12.30.106]> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: E85A6753F8 X-Spamd-Result: default: False [-102.13 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ALLOW_DOMAIN_WHITELIST(-100.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[FreeBSD.org]; MX_GOOD(-0.01)[cached: mx1.FreeBSD.org]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; IP_SCORE(-0.02)[country: GB(-0.10)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2018 16:21:08 -0000 On 12/11/2018 14:58, Karl Pielorz wrote: > How long does it usually take for an updated port (e.g. mysql56-server > which in ports is at 5.6.42) to be available as a pkg? (pkg under FBSD > 11.2 is currently 5.6.41). Which branch are you trcking in your pkg(8) config? If it's 'latest', then you'll get the updated mysql after about 1-3 days assuming there aren't any problems with that port of any of its dependencies. If it's 'quarterly' (which is the default) then you'll not get an update until the beginning of the next quarter -- which would be the start of January 2019. The exception to this is when there's a security fix for the package in question, which should appear within a day or so. Use 'pkg -vv' to examine your config settings, particularly the 'url' field under 'Repositories' towards the end of that output. > I had previously thought all of this was mostly automated > behind-the-scenes "magic" kind of stuff - but four weeks after the MySQL > port was updated the pkg isn't yet :( - so I'm guessing it's not really > that magic, and does involve human time & effort? :) No, packages are automatically built, and usually show up within a few days. It involves human time and effort when things go wrong, but that's primarily from the maintainers of the ports in question, and not usually the pkg-builder admins. > Are ports turned into pkg's by the maintainers? - Is it done as-and-when > - or is there some kind of 'every x days / once per quarter' kind of thing? Nope. Official packages are built on the official package building cluster. The certainly aren't built by random port maintainers who may be of particularly uncertain provenance and are not absolutely guaranteed to have your best interests at heart.[*] Cheers, Matthew [*] The requirements for becoming a port maintainer are no more stringent than: * Having a working e-mail address * Expressing a willingness to maintain a port * Being able to generate a diff and attach it to a Bugzilla ticket. It's down to ports committers to verify that there's nothing untoward about what they commit to the ports. The requirements on authenticating/identifying yourself when becoming a ports committer are rather stricter than for a port maintainer.