Pkg upgrade updating repository catalogue error

I was very enthusiastic about pkg (then called pkgng), and I'm very much dissapointed that several YEARS of its existence and bug reports (yes, I've submitted them to the right mailing list), have had no effect and it is now as broken as it was in the beginning in a critical area: it doesn't handle inter-package dependencies in a robust manner.Currently, the only significant way package dependancies are honoured at all is when a package is first installed.There may be defunct repositories listed and there may be active mirrors that are not listed as options.You may edit or add new repo configuration files as necessary. The normal use case is that someone builds specific packages (e.g.Avalon will have new packages first and they'll be updated as a set.The others are mirrors and may be much, much faster depending on the user's location, but there will be a period between set updates where the mirror is mix of old and new packages. If you want to switch off the overloaded Avalon, simply change the The provided may not be up to date.For pkg(8) version 1.5.1 or later, the "prime-list" alias is predefined in the pre-installed pkg.conf, so you can run the following command: The file ~/contains the list of packages that were manually installed.For example, if an Administrator only requested on package to be installed, Libreoffice, pkg(8) might pull in 200 dependencies, but ~/would only contain the name of a single package.

To force a reinstallation of dependent packages, type: Several people have run into problem upgrading binary packages when default versions change (e.g.As an illustration, consider a system which has the following packages installed: php53-5.3.27 PHP Scripting Language php53-bz2-5.3.27 The bz2 shared extension for php php53-ctype-5.3.27 The ctype shared extension for php php53-curl-5.3.27_1 The curl shared extension for php php53-dom-5.3.27 The dom shared extension for php php53-exif-5.3.27 The exif shared extension for php php53-extensions-1.6 A "meta-port" to install PHP extensions php53-filter-5.3.27 The filter shared extension for php php53-gd-5.3.27 The gd shared extension for php php53-hash-5.3.27 The hash shared extension for php php53-iconv-5.3.27 The iconv shared extension for php php53-json-5.3.27 The json shared extension for php php53-ldap-5.3.27 The ldap shared extension for php php53-mbstring-5.3.27 The mbstring shared extension for php php53-mcrypt-5.3.27 The mcrypt shared extension for php php53-openssl-5.3.27_1 The openssl shared extension for php php53-pcntl-5.3.27 The pcntl shared extension for php php53-pdo-5.3.27 The pdo shared extension for php php53-pdo_sqlite-5.3.27 The pdo_sqlite shared extension for php php53-pgsql-5.3.27 The pgsql shared extension for php php53-posix-5.3.27 The posix shared extension for php php53-session-5.3.27 The session shared extension for php php53-simplexml-5.3.27 The simplexml shared extension for php php53-soap-5.3.27 The soap shared extension for php php53-sockets-5.3.27 The sockets shared extension for php php53-sqlite-5.3.27 The sqlite shared extension for php php53-sqlite3-5.3.27 The sqlite3 shared extension for php php53-tokenizer-5.3.27 The tokenizer shared extension for php php53-xml-5.3.27 The xml shared extension for php php53-xmlreader-5.3.27 The xmlreader shared extension for php php53-xmlwriter-5.3.27 The xmlwriter shared extension for php php53-zip-5.3.27 The zip shared extension for php php53-zlib-5.3.27 The zlib shared extension for php This was obviously a system installed some time ago, last upgraded when the current version of PHP was 5.3.27. Updating database digests format: 100% pkg: libxml2 has a missing dependency: pkg-config pkg: php53 has a missing dependency: pkg-config The following 1 packages will be affected (of 0 checked): New packages to be INSTALLED: php53-fileinfo: 5.3.29_3 The process will require 2 Mi B more space. done (0 conflicting) [1/1] Installing php53-fileinfo-5.3.29_3... [1/1] Extracting php53-fileinfo-5.3.29_3: 100% # pkg upgrade php53 Updating Free BSD repository catalogue... This means that new versions of popular packages arrive into the repositories shortly after they are released by the upstream project.The current version of PHP is 5.3.29 and when I tried to install another PHP extension (which is a # pkg install php53-fileinfo Updating Free BSD repository catalogue... In case of PHP, the installed versions become out of sync with the freshest ones in the repos very fast, and currently the only possible way of upgrading PHP is to upgrade each and every extension separately - an operation which, because of the broken dependancy tracking, may install new binaries (, leaving it broken until manually and individually fixed.On the other hand, many people use pkg(8) by itself and never install the optional portupgrade or portmaster tools.Dragon Fly daily snapshots and Releases (starting with 3.4) come with pkg(8) already installed.

Search for pkg upgrade updating repository catalogue error:

pkg upgrade updating repository catalogue error-43pkg upgrade updating repository catalogue error-41pkg upgrade updating repository catalogue error-40

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “pkg upgrade updating repository catalogue error”