Cannot upgrade from custom repo

[Dan Langille]

> On Nov 19, 2015, at 4:17 PM, Matthew Seaman <matthew at FreeBSD.org> wrote:
> 
> On 19/11/2015 20:43, Dan Langille wrote:
>> FreeBSD 10.2-RELEASE-p7 in a jail, using pkg-1.6.1_2
>> 
>> I have a custom repo. I've been using it for some time. Today I wanted to upgrade databases/mysql56-server, but I cannot.
>> 
>> 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
>> 
> 
> 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.
> 
> You can force it to update the repo by:
> 
>   pkg update -f
> 
> 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    
[zuul-mysql.vpn.unixathome.org] Fetching packagesite.txz: 100%  184 KiB 188.5kB/s    00:01    
Processing entries: 100%
local repository update completed. 708 packages processed.


> 
>> 
>> OK, let's look at All:
>> 
>> Code:
>> $ pkg -vv | grep url
>>    url             : "pkg+http://fedex.unixathome.org/packages/102amd64-default-master-list/",
>> $ 
>> 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
>> 
>> $ ls -l All
>> -rw-r--r--  1 dan  dan  90209 Nov 19 20:16 All
>> $ date
>> Thu Nov 19 20:17:14 UTC 2015
>> 
>> $ grep mysql All
>> <a href="mysql55-client-5.5.46.txz">mysql55-client-5.5.46.txz</a>                          19-Nov-2015 16:26             1666804
>> <a href="mysql55-server-5.5.46.txz">mysql55-server-5.5.46.txz</a>                          19-Nov-2015 16:32             6672556
>> <a href="mysql56-client-5.6.27.txz">mysql56-client-5.6.27.txz</a>                          18-Nov-2015 17:44             2077388
>> <a href="mysql56-server-5.6.27.txz">mysql56-server-5.6.27.txz</a>                          19-Nov-2015 20:09             8470408
>> <a href="php55-mysql-5.5.30.txz">php55-mysql-5.5.30.txz</a>                             06-Oct-2015 04:46               17552
>> 
>> 
>> 
>> I see mysql56-server in there. Definitely.
> 
> Usually, all the above could be replaced by:
> 
> pkg search -x mysql56
> 
> 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 at 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 at zuul-mysql:~] # pkg info -x mysql
mysql56-client-5.6.27
mysql56-server-5.6.26
[root at zuul-mysql:~] # 


> 
>> Let's force a download:
>> 
>> 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
>> 
> 
> 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.
> 
> 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


> 
> 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.

From two terminal sessions, I checked the date by hand: 1s difference, but that's my keyboard swapping between terminal time'.

> 
> 	Cheers
> 
> 	Matthew
> 
> 

— 
Dan Langille
http://langille.org/