From owner-freebsd-ports-announce@FreeBSD.ORG Wed Aug 20 16:27:42 2014 Return-Path: Delivered-To: ports-announce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2F695E1 for ; Wed, 20 Aug 2014 16:27:42 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C134E34A8 for ; Wed, 20 Aug 2014 16:27:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.9/8.14.9) with ESMTP id s7KGRg70071448 for ; Wed, 20 Aug 2014 16:27:42 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.9/8.14.9/Submit) id s7KGRgEv071444 for ports-announce@FreeBSD.org; Wed, 20 Aug 2014 16:27:42 GMT (envelope-from bdrewery) Received: (qmail 47055 invoked from network); 20 Aug 2014 11:27:41 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 20 Aug 2014 11:27:41 -0500 Message-ID: <53F4CC79.5000607@FreeBSD.org> Date: Wed, 20 Aug 2014 11:27:37 -0500 From: Bryan Drewery Reply-To: pkg@FreeBSD.org Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: ports@FreeBSD.org, pkg@FreeBSD.org OpenPGP: id=6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="goqP9LIaLMvlJuh91T8kFTTU9U6VSeSmR" X-Mailman-Approved-At: Wed, 20 Aug 2014 17:07:09 +0000 Subject: [FreeBSD-Ports-Announce] HEADS UP: Pkg 1.3.7 will require rebuilding all packages and manual commands on clients recommended X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2014 16:27:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --goqP9LIaLMvlJuh91T8kFTTU9U6VSeSmR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable There are 2 parts to this notice. One is strictly for those who build their own packages with poudriere or other means. The other part is for client-side users of Pkg (including ports users [1]). Regardless of which version of Pkg you are on now (1.0, 1.1, 1.2, ..., 1.3.4, 1.3.6) it is recommended you follow these steps once upgrading to 1.3.7 or later. Note that following these directions should only be followed once 1.3.7 is released in a few days. Impact of doing nothing: 'pkg upgrade' will suggest reinstalling packages due to 'needed shared library changed'. This can result in wasted bandwidth, time and IO on your systems. It should eventually work itself out though, but may cause various 'pkg upgrade' issues. Background: Pkg tracks shared libraries that are both required and provided by packages. It determines these when building or installing the package. This is also true for using ports since it just registers a new package on install. Before 1.3.0 Pkg would often incorrectly register a shared library with the wrong name internally rather than the official SONAME of the library. This could result in a library dependency as libname.so.1.2.3 and the package providing the library advertising libname.so.1. Due to packages built from 1.3.0 onwards registering the proper name, the upgrade solver had difficulty in finding the proper packages for needed shared libraries. A workaround put in place for 1.3.6 was to ignore the shlib versions. This was not adequate though. In 1.3.7 we are removing the workaround from 1.3.6. There is also a fix in 1.3.7 for Pkg sometimes incorrectly registering a package as requiring its own shared libraries. This also causes solver confusion. Package builders: For the sake of your users having proper packages available you should remove all existing packages and rebuild them once 1.3.7 is released. Poudriere can accomplish this with the '-c' flag to bulk. Or you can just remove All/* from your package repository. If your repository is using WITH_PKGNG=3Ddevel then you can do this now as alpha11 has the fixe= s. Pkg users: It is recommended, but not required, to follow these steps once Pkg 1.3.7 is available. 1. Upgrade Pkg to 1.3.7. Only upgrade Pkg, nothing else. 2. As root run 'pkg check -Ba'. This will analyze all of your installed packages and fix their registered required/provided shared library names. It may take anywhere between 1-15 minutes to complete. 3. Proceed with normal upgrade. Example automated script: pkg update pkg_local_ver=3D`pkg query %v ports-mgmt/pkg` pkg_remote_ver=3D`pkg rquery -U %v ports-mgmt/pkg` # Special handling needed for upgrading <=3D1.3.6 to 1.3.7+ if [ "`pkg version -t ${pkg_local_ver} 1.3.7)`" =3D "<" ]; then pkg install -Uy ports-mgmt/pkg pkg check -Ba fi # Normal upgrade can proceed... pkg upgrade -Uy You might wonder why we do not just force the 1.3.7 upgrade to auto run 'pkg check -Ba'. The problem is that 1.3.0-1.3.6 self-upgrade is not properly running the new Pkg as it did in 1.2. Thus after 'pkg upgrade' self-upgrades to 1.3.7 it would still be running 1.3.6 until you reran 'pkg upgrade'. We may still add an automatic check, or periodic scrub script, in future versions. [1] Ports users: If you strictly use ports and not remote packages then it is not required that you do anything. However if you do ever decide to switch to packages you will face the same 'needed shared library changed' message. It is recommend you also run 'pkg check -Ba' after upgrading to 1.3.7. It is possible tools such as portmaster may utilize this information some day, so it is good to ensure it is recorded properly. --=20 Regards, Bryan Drewery --goqP9LIaLMvlJuh91T8kFTTU9U6VSeSmR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJT9Mx5AAoJEDXXcbtuRpfPFdsIAKmvl5r8dq29yppU9EqDXGRE 7oj3wyG+5iZdstf46VRTqnpR4jiUUKEAkFsPWtgouRzV4CL08lRfqlY9MQAJn4X0 tW4anbLFWvFCBcMpjqKuW/8p+YztlJQ4ScnM7xT1ZLh5/vtaelBLnT67z1vxgaSk 2+rS14ohY2mAbm0eh94mDKVlDzsHgoCNTYIrvXx/+r4zwfPSevvpb4MyeE0tCxgy bF/ip5/VNtAJ/w2XVQNRydxVl6VPbDOTNHJajezVL80TLTU6D4yzmKJD0PI3aV5K GE2V+Up9OPzZhC1WFi2vYoey3h0R8VJORQ7ln0zRDbH3q70YNPFAWD3pkPdVfts= =FYDF -----END PGP SIGNATURE----- --goqP9LIaLMvlJuh91T8kFTTU9U6VSeSmR-- From owner-freebsd-ports-announce@FreeBSD.ORG Wed Aug 20 16:34:30 2014 Return-Path: Delivered-To: ports-announce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 82DC896D for ; Wed, 20 Aug 2014 16:34:30 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F46B3578 for ; Wed, 20 Aug 2014 16:34:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.9/8.14.9) with ESMTP id s7KGYUop074432 for ; Wed, 20 Aug 2014 16:34:30 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.9/8.14.9/Submit) id s7KGYUGb074427 for ports-announce@FreeBSD.org; Wed, 20 Aug 2014 16:34:30 GMT (envelope-from bdrewery) Received: (qmail 23391 invoked from network); 20 Aug 2014 11:34:26 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 20 Aug 2014 11:34:26 -0500 Message-ID: <53F4CE0E.8040106@FreeBSD.org> Date: Wed, 20 Aug 2014 11:34:22 -0500 From: Bryan Drewery Reply-To: Ports FreeBSD Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Ports FreeBSD , pkg@freebsd.org References: <523D79CD.2090302@FreeBSD.org> In-Reply-To: <523D79CD.2090302@FreeBSD.org> OpenPGP: id=6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K5G4LOnFU7x5CMaL6D0wm5KIVLpq9PTjB" X-Mailman-Approved-At: Wed, 20 Aug 2014 17:14:38 +0000 Subject: [FreeBSD-Ports-Announce] [CFT] SSP Package Repository available X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2014 16:34:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --K5G4LOnFU7x5CMaL6D0wm5KIVLpq9PTjB Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 9/21/2013 5:49 AM, Bryan Drewery wrote: > Ports now support enabling Stack Protector [1] support on FreeBSD 10 > i386 and amd64, and older releases on amd64 only currently. >=20 > Support may be added for earlier i386 releases once all ports properly > respect LDFLAGS. >=20 > To enable, just add WITH_SSP=3Dyes to your make.conf and rebuild all po= rts. >=20 > The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all > may optionally be set instead. >=20 > Please help test this on your system. We would like to eventually enabl= e > this by default, but need to identify any major ports that have run-tim= e > issues due to it. >=20 > [1] https://en.wikipedia.org/wiki/Buffer_overflow_protection >=20 We have not had any feedback on this yet and want to get it enabled by default for ports and packages. We now have a repository that you can use rather than the default to help test. We need your help to identify any issues before switching the default. This repository is available for: head 10.0 9.1,9.2,9.3 It is not available for 8.4. If someone is willing to test on 8.4 I will build a repository for it. Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf: FreeBSD: { enabled: no } FreeBSD_ssp: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/ssp", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes } Once that is done you should force reinstall packages from this repositor= y: pkg update pkg upgrade -f Thanks for your help! Bryan Drewery On behalf of portmgr. --K5G4LOnFU7x5CMaL6D0wm5KIVLpq9PTjB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJT9M4OAAoJEDXXcbtuRpfPudQH/RV3dAPGOMV+RRC3IGo0l7bB rjr5J5xQK4FuIYenMhkEV+p8Wh/ow9P3GXBQtR4ki/x3Jgk7Xw5YlC4PfJyPdFpM 90wx0IjtT9i5CLTGF+psTgeV5Oh50jWnpy8wggsK+CfFtgqRebdbQvqIWOtKuDdT R5QtxF9U4ZDHCJTEVLsiCeY4SP3N2eqwS4MHX1/92I1xJxbETDQ0CjvoQ5ojfmEi crtNhk4QNUxmmElmxM71iiElbZPfdf3UbqDupQm80eTHNj5Adda8+Mo1ZmUsJYM6 YimDcpNTumctOVLXobpBZEJtOExAsajO1v/aFGWJz4kp2AkGwCLXHowNpHbb/u4= =ElhW -----END PGP SIGNATURE----- --K5G4LOnFU7x5CMaL6D0wm5KIVLpq9PTjB-- From owner-freebsd-ports-announce@FreeBSD.ORG Thu Aug 21 05:06:54 2014 Return-Path: Delivered-To: ports-announce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B129E3D; Thu, 21 Aug 2014 05:06:54 +0000 (UTC) Received: from 0xd0.org (0xd0.org [188.165.222.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "0xd0.org", Issuer "0xd0.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1A35354F; Thu, 21 Aug 2014 05:06:50 +0000 (UTC) Received: from 0xd0.org (localhost [127.0.0.1]) by 0xd0.org (8.14.7/8.14.7) with ESMTP id s7L56l4R030217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 21 Aug 2014 07:06:47 +0200 (CEST) (envelope-from culot@0xd0.org) Received: (from culot@localhost) by 0xd0.org (8.14.7/8.14.7/Submit) id s7L56lHI030216; Thu, 21 Aug 2014 07:06:47 +0200 (CEST) (envelope-from culot) Date: Thu, 21 Aug 2014 07:06:46 +0200 From: Frederic Culot To: ports-announce@FreeBSD.org, developers@FreeBSD.org Message-ID: <20140821050646.GH71349@culot.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RCcFxJ34+mAtH0DM" Content-Disposition: inline X-PGP-Key: http://culot.org/public/pgp-key.txt User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Thu, 21 Aug 2014 11:35:14 +0000 Subject: [FreeBSD-Ports-Announce] Happy 20th birthday FreeBSD ports tree! X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 05:06:54 -0000 --RCcFxJ34+mAtH0DM Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline It all started with this commit from Jordan Hubbard on August 21, 1994: Commit my new ports make macros Still not 100% complete yet by any means but fairly usable at this stage. Twenty years later the ports tree is still there and actively maintained. A video [1] was prepared to celebrate the event and to thank all of you who give some of their spare time and energy to the project! Frederic on behalf of portmgr [1] http://youtu.be/LiFq5D-zmBs --RCcFxJ34+mAtH0DM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJT9X5mAAoJENgpTsO7xNfVSNwH/0ir9b0vit5raByDb5R2wN7N 14TsUFxkwncRwoLOKwLdvSc2I7br+vpfYaB45/eiVC/nM/ZWfIlpTf2FOW+3LNSE z5fK/yfrN1RXyTHYkvpJcTCloa+7oeYo4zjpRSZs2fNsPA1XGnjDheFfMwMJAe1Q l9lFcpvER2B2Sbywt2glRWUvmC2HGkdyOdlym0pSJ0DLYX79MZlsQzLzLgEMEZZI Cwy+mUSMOJSogJe6FqjhVsjCPxQnYrQo1LGZ9gvOBJmfrZ5nn+bWNORh9rRUCJmn h/jygpsKuQD3h5kA/DZV0MXokCI2BBC//3ti9LGxu4G4aajQfDfaVQP7Iu5Dbcs= =vLHB -----END PGP SIGNATURE----- --RCcFxJ34+mAtH0DM-- From owner-freebsd-ports-announce@FreeBSD.ORG Thu Aug 21 16:04:36 2014 Return-Path: Delivered-To: ports-announce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 97D194C6 for ; Thu, 21 Aug 2014 16:04:36 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 78DD63745 for ; Thu, 21 Aug 2014 16:04:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.9/8.14.9) with ESMTP id s7LG4ajp052178 for ; Thu, 21 Aug 2014 16:04:36 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.9/8.14.9/Submit) id s7LG4ang052174 for ports-announce@FreeBSD.org; Thu, 21 Aug 2014 16:04:36 GMT (envelope-from bdrewery) Received: (qmail 16816 invoked from network); 21 Aug 2014 11:04:34 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 21 Aug 2014 11:04:34 -0500 Message-ID: <53F6188D.7090505@FreeBSD.org> Date: Thu, 21 Aug 2014 11:04:29 -0500 From: Bryan Drewery Reply-To: Ports FreeBSD Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: pkg@FreeBSD.org, ports@FreeBSD.org References: <53F4CC79.5000607@FreeBSD.org> In-Reply-To: <53F4CC79.5000607@FreeBSD.org> OpenPGP: id=6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bW0h5JBC3910nRI983d546LfjipXd7SbV" X-Mailman-Approved-At: Thu, 21 Aug 2014 16:33:57 +0000 Subject: Re: [FreeBSD-Ports-Announce] HEADS UP: Pkg 1.3.7 will require rebuilding all packages and manual commands on clients recommended X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 16:04:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bW0h5JBC3910nRI983d546LfjipXd7SbV Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To clarify: Only people serving packages for distribution need to rebuild so that their users have fixed packages. If you are running Poudriere/Tinderbox/Custom and are serving packages to other people or machines, you should rebuild them on the build system AFTER 1.3.7 is out. Running pkg check -Ba on the end systems (after upgrading to 1.3.7) will then prevent needing to reinstall anything. If you are building from ports then you do not need to rebuild all. You do not need to reinstall all. The goal of this announcement is to avoid anyone needing to reinstall anything unneeded. Sorry for the inconvenience. On 8/20/2014 11:27 AM, Bryan Drewery wrote: > There are 2 parts to this notice. One is strictly for those who build > their own packages with poudriere or other means. The other part is for= > client-side users of Pkg (including ports users [1]). >=20 > Regardless of which version of Pkg you are on now (1.0, 1.1, 1.2, ..., > 1.3.4, 1.3.6) it is recommended you follow these steps once upgrading t= o > 1.3.7 or later. >=20 > Note that following these directions should only be followed once 1.3.7= > is released in a few days. >=20 >=20 > Impact of doing nothing: >=20 > 'pkg upgrade' will suggest reinstalling packages due to 'needed shared > library changed'. This can result in wasted bandwidth, time and IO on > your systems. It should eventually work itself out though, but may caus= e > various 'pkg upgrade' issues. >=20 >=20 > Background: >=20 > Pkg tracks shared libraries that are both required and provided by > packages. It determines these when building or installing the package. > This is also true for using ports since it just registers a new package= > on install. >=20 > Before 1.3.0 Pkg would often incorrectly register a shared library with= > the wrong name internally rather than the official SONAME of the > library. This could result in a library dependency as libname.so.1.2.3 > and the package providing the library advertising libname.so.1. Due to > packages built from 1.3.0 onwards registering the proper name, the > upgrade solver had difficulty in finding the proper packages for needed= > shared libraries. A workaround put in place for 1.3.6 was to ignore the= > shlib versions. This was not adequate though. In 1.3.7 we are removing > the workaround from 1.3.6. There is also a fix in 1.3.7 for Pkg > sometimes incorrectly registering a package as requiring its own shared= > libraries. This also causes solver confusion. >=20 >=20 > Package builders: >=20 > For the sake of your users having proper packages available you should > remove all existing packages and rebuild them once 1.3.7 is released. > Poudriere can accomplish this with the '-c' flag to bulk. Or you can > just remove All/* from your package repository. If your repository is > using WITH_PKGNG=3Ddevel then you can do this now as alpha11 has the fi= xes. >=20 >=20 > Pkg users: >=20 > It is recommended, but not required, to follow these steps once Pkg > 1.3.7 is available. >=20 > 1. Upgrade Pkg to 1.3.7. Only upgrade Pkg, nothing else. > 2. As root run 'pkg check -Ba'. This will analyze all of your installed= > packages and fix their registered required/provided shared library > names. It may take anywhere between 1-15 minutes to complete. > 3. Proceed with normal upgrade. >=20 > Example automated script: > pkg update > pkg_local_ver=3D`pkg query %v ports-mgmt/pkg` > pkg_remote_ver=3D`pkg rquery -U %v ports-mgmt/pkg` > # Special handling needed for upgrading <=3D1.3.6 to 1.3.7+ > if [ "`pkg version -t ${pkg_local_ver} 1.3.7)`" =3D "<" ]; then > pkg install -Uy ports-mgmt/pkg > pkg check -Ba > fi >=20 > # Normal upgrade can proceed... > pkg upgrade -Uy >=20 >=20 > You might wonder why we do not just force the 1.3.7 upgrade to auto run= > 'pkg check -Ba'. The problem is that 1.3.0-1.3.6 self-upgrade is not > properly running the new Pkg as it did in 1.2. Thus after 'pkg upgrade'= > self-upgrades to 1.3.7 it would still be running 1.3.6 until you reran > 'pkg upgrade'. We may still add an automatic check, or periodic scrub > script, in future versions. >=20 >=20 > [1] Ports users: >=20 > If you strictly use ports and not remote packages then it is not > required that you do anything. However if you do ever decide to switch > to packages you will face the same 'needed shared library changed' > message. It is recommend you also run 'pkg check -Ba' after upgrading t= o > 1.3.7. It is possible tools such as portmaster may utilize this > information some day, so it is good to ensure it is recorded properly. >=20 --=20 Regards, Bryan Drewery --bW0h5JBC3910nRI983d546LfjipXd7SbV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJT9hiNAAoJEDXXcbtuRpfP9DcH+QGC2FP3kVj1ODFQONaBtJcl 1J/R6oWXqfqkxjBXcwq2LfJJjsxZJuInTqMK1yj8CblACBmf31dOfRqXaPhF7IWk 5QkA7NeNqKzEW1rBUNORedes39EmKUAQ3Q8iyrTKb8cs1wTNPsryegWFZtqojQag d4O+n5SbkGjCaPOhRd1CVmEmFZ30Rsc2wRqu48Y9nshE1iyJNqWIQXmOVjdCloaG 2m2TXA/1tfbzxL28+j257LZuAmhq81kPxk3UqhT3wCWVNMu1rPsrI66qP1US8bIV x6QLC0OC7X8BGds9nQl6ghFaABMNvpXSiKiMi8qa2PPwzdgWxc6Bu+xViYWjvU8= =elxk -----END PGP SIGNATURE----- --bW0h5JBC3910nRI983d546LfjipXd7SbV-- From owner-freebsd-ports-announce@FreeBSD.ORG Thu Aug 21 18:56:49 2014 Return-Path: Delivered-To: freebsd-ports-announce@FreeBSD.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7098D40C; Thu, 21 Aug 2014 18:56:49 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id BF43F23CEB4; Thu, 21 Aug 2014 20:56:47 +0200 (CEST) Message-ID: <53F640EF.7000200@FreeBSD.org> Date: Thu, 21 Aug 2014 20:56:47 +0200 From: Matthias Andree Reply-To: ports-list freebsd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-ports-announce@FreeBSD.org Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 21 Aug 2014 19:04:36 +0000 Cc: ports-list freebsd Subject: [FreeBSD-Ports-Announce] HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 18:56:49 -0000 Greetings, The time has now come to remove these db4* ports, Berkeley DB versions 4.0 to 4.7, inclusively. Most of their dependent ports can cope with upgrades to db48, db5, or db6, most of the others could be patched to work. I will wait a few hours after this announcement has appeared on the lists before committing the change. I had marked most of the Berkeley DB ports in databases/db4* (db4o-mono is part of this group) deprecated many months ago. Released between 2001 and 2008, all have fallen out of the upstream's support many years ago, too -- and the db5 API is mostly compatible. IMPORTANT: for some of the ports that use advanced Berkeley DB features such as the built-in locking, transactional or replication features, the applications that use Berkeley DB may require special handling ... BEFORE YOU UPGRADE BERKELEY DB OR REBUILD THE APPLICATION! Usually these can be recognized from storing log.* and __db.* files next to the actual *.db database files. You must make sure that the applications shut down with a consistent database state, and wherever possible see to it that you have the data exported to a format that can later be reimported with the new BerkeleyDB version, just to be on the safe side. The exact steps to be taken are too diverse to describe here, because they depend on the exact version that you are upgrading from, and how exactly some application is using Berkeley DB. I have created a Wiki page that contains instructions, and points to SleepyCat's or Oracle's upgrading documentation, at . Please be sure to check these BEFORE upgrading Berkeley DB or your applications. When, among the upgrade steps on the WIki, you have reached the point where it is safe to upgrade the Berkeley DB and applications, there is a helper script in Tools/scripts/BDB-upgrade-helper.sh uses portmaster or portupgrade to rebuild the applications to use a newer Berkeley DB, and then offer to delete the old Berkeley DB ports. Corresponding upgrade documentation will be committed to ports/UPDATING along with the relevant changes once this becomes effective. The binary package upgrades will follow on their regular rebuild schedule and pick db5 (actually db5.3) by default; I have chosen to pick db6 only for from-source builds on systems that already have db6 installed because db6 switched to the less liberal Affero GNU General Public License v3 that requires its users to open-source software offered as a service, too. If you have further questions, please ask them on the freebsd-ports@ mailing list, and feel free to Cc: me, but do make sure your mailer does not break threading, and do keep the Subject line intact. Thanks for your attention. Matthias Andree (*) The exception is mail/popular which will lose its BDB4 plugin along the way because fixing goes beyond the scope of the ports mailing list.