From owner-freebsd-pkg@freebsd.org Thu Nov 19 22:12:26 2015 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF25AA339F5 for ; Thu, 19 Nov 2015 22:12:26 +0000 (UTC) (envelope-from dan@langille.org) Received: from clavin1.langille.org (clavin.langille.org [162.208.116.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "clavin.langille.org", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CF5E1647 for ; Thu, 19 Nov 2015 22:12:25 +0000 (UTC) (envelope-from dan@langille.org) Received: from (clavin1.int.langille.org (clavin1.int.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id 6EE304809 for ; Thu, 19 Nov 2015 22:12:11 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: Cannot upgrade from custom repo From: Dan Langille In-Reply-To: <564E3C62.8070306@FreeBSD.org> Date: Thu, 19 Nov 2015 17:12:11 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <9EE4925F-1E32-4162-8E32-4A285D9E30B5@langille.org> References: <9D053084-3D0D-4CAF-A309-37D3C5766D43@langille.org> <564E3C62.8070306@FreeBSD.org> To: freebsd-pkg@freebsd.org X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 22:12:27 -0000 > On Nov 19, 2015, at 4:17 PM, Matthew Seaman = wrote: >=20 > On 19/11/2015 20:43, Dan Langille wrote: >> FreeBSD 10.2-RELEASE-p7 in a jail, using pkg-1.6.1_2 >>=20 >> I have a custom repo. I've been using it for some time. Today I = wanted to upgrade databases/mysql56-server, but I cannot. >>=20 >> Code: >> $ sudo pkg upgrade -r local mysql56-server >> Updating local repository catalogue... >> local repository is up-to-date. >> All repositories are up-to-date. >> pkg: No packages available to upgrade matching 'mysql56-server' have = been found in the repositories >>=20 >=20 > Hmmm... this didn't actually download an updated catalogue from your > repo -- it seemed to think that what you already had was up to date. >=20 > You can force it to update the repo by: >=20 > pkg update -f >=20 > That's a good thing to try any time pkg(8) isn't doing what you = expect. I had tried that, but didn't show my work. # pkg update -f -r local Updating local repository catalogue... [zuul-mysql.vpn.unixathome.org] Fetching meta.txz: 100% 820 B = 0.8kB/s 00:01 =20 [zuul-mysql.vpn.unixathome.org] Fetching packagesite.txz: 100% 184 KiB = 188.5kB/s 00:01 =20 Processing entries: 100% local repository update completed. 708 packages processed. >=20 >>=20 >> OK, let's look at All: >>=20 >> Code: >> $ pkg -vv | grep url >> url : = "pkg+http://fedex.unixathome.org/packages/102amd64-default-master-list/", >> $=20 >> fetch = http://fedex.unixathome.org/packages/102amd64-default-master-list/All >> fetch: = http://fedex.unixathome.org/packages/102amd64-default-master-list/All: = size of remote file is not known >> All 88 kB 722 = kBps 00m00s >>=20 >> $ ls -l All >> -rw-r--r-- 1 dan dan 90209 Nov 19 20:16 All >> $ date >> Thu Nov 19 20:17:14 UTC 2015 >>=20 >> $ grep mysql All >> mysql55-client-5.5.46.txz = 19-Nov-2015 16:26 1666804 >> mysql55-server-5.5.46.txz = 19-Nov-2015 16:32 6672556 >> mysql56-client-5.6.27.txz = 18-Nov-2015 17:44 2077388 >> mysql56-server-5.6.27.txz = 19-Nov-2015 20:09 8470408 >> php55-mysql-5.5.30.txz = 06-Oct-2015 04:46 17552 >>=20 >>=20 >>=20 >> I see mysql56-server in there. Definitely. >=20 > Usually, all the above could be replaced by: >=20 > pkg search -x mysql56 >=20 > but in this case, it would just be repeating the same result as 'pkg > install' or 'pkg upgrade' -- pkg thinks that the local copy of the > catalog is up to date, but it isn't and the old copy you have doesn't > contain any mysql56-server packages. What I have now: [root@zuul-mysql:~] # pkg search -x mysql56 mysql56-client-5.6.27 Multithreaded SQL database (client) mysql56-server-5.6.27 Multithreaded SQL database (server) [root@zuul-mysql:~] # pkg info -x mysql mysql56-client-5.6.27 mysql56-server-5.6.26 [root@zuul-mysql:~] #=20 >=20 >> Let's force a download: >>=20 >> Code: >> $ sudo pkg install -r local mysql56-server >> Updating local repository catalogue... >> local repository is up-to-date. >> All repositories are up-to-date. >> pkg: No packages available to install matching 'mysql56-server' have = been found in the repositories >>=20 >=20 > This hasn't forced anything much. There isn't really much difference > between 'install' and 'upgrade' nowadays when the package you're = dealing > with already has an older version installed. >=20 > Try 'pkg update -f' and then retry installing mysl56-server. See above and: # pkg upgrade -r local mysql56-server Updating local repository catalogue... local repository is up-to-date. All repositories are up-to-date. pkg: No packages available to upgrade matching 'mysql56-server' have = been found in the repositories >=20 > The problem you're seeing could be caused by the clocks on your jail = and > on your repo being out of synch, causing pkg(8) to get it wrong about > which copy of the repo catalogue is newer. Perhaps. =46rom two terminal sessions, I checked the date by hand: 1s difference, = but that's my keyboard swapping between terminal time'. >=20 > Cheers >=20 > Matthew >=20 >=20 =E2=80=94=20 Dan Langille http://langille.org/