Date: Tue, 8 Dec 2015 13:29:22 -0500 From: Dan Langille <dan@langille.org> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-pkg@freebsd.org Subject: Re: Cannot upgrade from custom repo Message-ID: <7DBDE53F-7D79-4206-B76B-0C3CB2FB9D40@langille.org> In-Reply-To: <56508D3A.2060600@FreeBSD.org> References: <9D053084-3D0D-4CAF-A309-37D3C5766D43@langille.org> <564E3C62.8070306@FreeBSD.org> <9EE4925F-1E32-4162-8E32-4A285D9E30B5@langille.org> <564E5142.4020408@FreeBSD.org> <DD532562-FC46-49A7-ACFB-AFB510B540DB@langille.org> <564ED623.5060005@FreeBSD.org> <9E018871-ECE4-45AA-849B-BA2DCF2EEB41@langille.org> <56508D3A.2060600@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Solved, while composing this email and trying again. > On Nov 21, 2015, at 10:26 AM, Matthew Seaman <matthew@FreeBSD.org> wrote: > > On 20/11/2015 14:37, Dan Langille wrote: >> FYI, someone tried working with repo, and they were able to >> install mysql56 5.6.27 from my repo; they succeeded: https://forums.freebsd.org/threads/cannot-upgrade-pkg-from-custom-repo.54080/#post-304454 >> >> That tells me it's an issue wth the box, not with the repo. Agreed? > > I cannot fault that logic, although I am at a loss to imagine /what/ is > wrong with the box to result in the observed effect. Let's start fresh: $ uname -a FreeBSD zuul-mysql.vpn.unixathome.org 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 14:19:39 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 $ pkg -vv Version : 1.6.2 PKG_DBDIR = "/var/db/pkg"; PKG_CACHEDIR = "/var/cache/pkg"; PORTSDIR = "/usr/ports"; INDEXDIR = ""; INDEXFILE = "INDEX-10"; HANDLE_RC_SCRIPTS = false; DEFAULT_ALWAYS_YES = false; ASSUME_ALWAYS_YES = false; REPOS_DIR [ "/usr/local/etc/pkg/repos/", ] PLIST_KEYWORDS_DIR = ""; SYSLOG = true; ABI = "FreeBSD:10:amd64"; ALTABI = "freebsd:10:x86:64"; DEVELOPER_MODE = false; VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.bz2"; FETCH_RETRY = 3; PKG_PLUGINS_DIR = "/usr/local/lib/pkg/"; PKG_ENABLE_PLUGINS = true; PLUGINS [ ] DEBUG_SCRIPTS = false; PLUGINS_CONF_DIR = "/usr/local/etc/pkg/"; PERMISSIVE = false; REPO_AUTOUPDATE = true; NAMESERVER = ""; HTTP_USER_AGENT = "pkg/1.6.2"; EVENT_PIPE = ""; FETCH_TIMEOUT = 30; UNSET_TIMESTAMP = false; SSH_RESTRICT_DIR = ""; PKG_ENV { } PKG_SSH_ARGS = ""; DEBUG_LEVEL = 0; ALIAS { } CUDF_SOLVER = ""; SAT_SOLVER = ""; RUN_SCRIPTS = true; CASE_SENSITIVE_MATCH = false; LOCK_WAIT = 1; LOCK_RETRIES = 5; SQLITE_PROFILE = false; WORKERS_COUNT = 0; READ_LOCK = false; PLIST_ACCEPT_DIRECTORIES = false; IP_VERSION = 0; AUTOMERGE = true; VERSION_SOURCE = ""; CONSERVATIVE_UPGRADE = true; PKG_CREATE_VERBOSE = false; AUTOCLEAN = false; DOT_FILE = ""; REPOSITORIES { } Repositories: local: { url : "pkg+http://fedex.unixathome.org/packages/102amd64-default-master-list/", enabled : yes, priority : 0, mirror_type : "SRV", signature_type : "PUBKEY", pubkey : "/etc/ssl/slocum.unixathome.org.cert" } $ $ sudo pkg update -f 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% 185 KiB 189.1kB/s 00:01 Processing entries: 100% local repository update completed. 709 packages processed. $ pkg info -x mysql mysql56-client-5.6.27 mysql56-server-5.6.26 $ pkg search -x mysql56 mysql56-client-5.6.27 Multithreaded SQL database (client) mysql56-server-5.6.27 Multithreaded SQL database (server) $ sudo pkg upgrade 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 .... but wait, you just said there was..... What about globs? $ sudo pkg upgrade --glob mysql56* Updating local repository catalogue... local repository is up-to-date. All repositories are up-to-date. pkg: No packages available to upgrade matching 'mysql56*' have been found in the repositories Let's try another package name: $ sudo pkg upgrade --glob bash* Updating local repository catalogue... local repository is up-to-date. All repositories are up-to-date. Checking integrity... done (0 conflicting) Your packages are up to date. Does the above bring any ideas to mind? I can always try deleting the package... $ sudo pkg delete mysql56-server mysql56-server-5.6.26 is locked and may not be modified Checking integrity... done (0 conflicting) Package(s) not found! Oh wait... WHAT? $ sudo pkg upgrade mysql56-server Updating local repository catalogue... local repository is up-to-date. All repositories are up-to-date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: mysql56-server: 5.6.26 -> 5.6.27 The process will require 21 KiB more space. 8 MiB to be downloaded. Proceed with this action? [y/N]: Oh, I think this is a bug! — Dan Langille http://langille.org/ [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQJ8BAEBCgBmBQJWZyGIXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1MTE2RjM0ODIzRDdERDM4OTY0OUJBNzdF QjIxNTlERUU5NzI3MzlGAAoJEOshWd7pcnOfrBIP/2FOWV8n6yklu6qmv+is+Jca 9SEe65LeQ3yGKVYAl+pJ+yMK05sxBxGTypJVUKCD1IKQC491C9h8DMG7zACyJcgX 1qO8BcYD93VRYo+IvaJMDPgH41maTPy5HhgrXk8Jqfq5SjbMT3PifjNn+aaYqcsq ryGq9hZ+yHnY/siw/eT1q6+309bYkf8CUI5UrFTD2Mn13nlxkkG+2MupfWAcaHfQ KZV52XaRj1sHEFuRH2MI1oL1w/L3GB3ftjqte7zYsYdVNbAkhdhUoRbzmNQHkaUD 32uGkD4qrKVsDHnxqIi5kCG9trcNzWGPZ5WyVBf4DMaoLFuEUkhBH5XfItFI3YHl 7nlSjgZFuISIZqltjpMj25oBwS8rJsVQjJZBrGyIC7ZVPDNBFcRD4KOmOD59iLko 4Bh4XPbBYb4vwefdkAz9sIJI1jihBL5fCw2CxEmSDZgVybwxTREp6CtpY0nuAo2H Z5RgMDTXtFJ7S+fTDvEUn/YXqG++ch1ytF4Rjb8qnEY2ltl9qakYyIGfmYb5iQe1 Owc8gJ79lM2ZOhrmAKZ1NZNMbxjLJMwlAyMFSXjW3DEkHmPKmZgEbnsWs5r1+lJ7 WPoStj2kk7DI/fSlwPrctQrYKtjOpDXuPtcDZPFPlBkGocqVn0arn+sFE2k8Fq9P sMxFCwEr/Yaqg9ku5Xjm =Zoqd -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7DBDE53F-7D79-4206-B76B-0C3CB2FB9D40>