Pkg upgrade updating repository catalogue error

28 Mar

After running them, both App Cafe and pc-updatemanager pkgupdate fail with . We found it caused far more problems than it solved, trying to have pkg resolve two repos at once. 10.1-RELEASE-p16 amd64 (from a previous full install) Dell Optiplex 9010 Today I got the "Package Updates Available" notification. As for the 10.1-RELEASE pkg site on mirrors, that was my mistake. -at least if we assume autoindex is working on the server, and it has the right permissions. Installing GRUB to ada1 Installing for i386-pc platform. Rolling releases, etc., are kind of defeated by the fact that PC-BSD seems to require full re-installs, even for minor version updates. When they upgraded to pkgng, couldn't they produce a system that could automatically help resolve conflicts better? 23993 packages processed pkg: sqlite error while executing DROP TABLE repo_update; in file pkgdb.c:2262: attempt to write a readonly database ''' Maybe it would be good for the update manager to first check if packages are really available, before it reports that they are. But this type of experience has become unique, and common, with my PC-BSD system.I think this bugged it and now when I run pkg update it says it is on the latest versions. Is there a way to force a clean repo list to pull the latest version info? The following 1 packages will be affected (of 0 checked): New packages to be INSTALLED: php56: 5.6.6 The process will require 15 Mi B more space. This is the error when I try to install php56 for example: [email protected]:/usr/home/username # pkg install php56 Updating Free BSD repository catalogue... done Upgrading libslang2 from 2.2.4_3 to 2.2.4_4 ... done Reinstalling screen-4.0.3_14 done Upgrading libidn from 1.25 to 1.26 ... done Upgrading gio-fam-backend from 2.28.8_1 to 2.34.3 ...

pkg upgrade updating repository catalogue error-35pkg upgrade updating repository catalogue error-80

006 12 29 Points 1316 Partenaires vivaocs target blanc baznas FWD V4 solid 000 safiweb hostma 00px 3px vertical love jiji bientot hichamtoldo skyblog blank siro tssalo mehdibono wesh houssam salam sarah slt tt monde lkhassar sqal 07 wlad asfi t9admo walah mdintkom wa3ra mais ntoma mhachrine m simo simoraymy mimo moi meryem safi c est mon msn mailto soso 2005 mousi9a net hicham toldo ach hadak chi sadi9 dyalach site adrianhicham 3l makshof tamo sba7 lkhayre sba7ato lilah manak miss kawtar salut yala9ina m3a ma7san mana ou tanatmana matab9awche tkhasro fi lhadra awlade khalti msa tupac saha hi everybody souma ha7na left Votre Message auteur maxlenght msg send Voir archives google 160 600 160x600 E1771E 006699 addv Ajouter Une addm addi Photo addt Telechargement addp Devenez partenaire Signaler bug erreur Contacter 250 Codage Design par Mohamed Yassine 0021274185715 N° 17 Bloc 62 Saida 46000 ligne 94 Total 65559 Corpyright Tous droits r?

The good news is that this should be the last instance, once you get the new 10.1.1 updater in place, it won't use 'pkg upgrade' anymore and avoid these conflict issues.

No error reported." ''' The process will require 2 GB more space. -or maybe just make a symlink to 10.0-RELEASE Yea, no denying it, the past updates have been VERY rough, in particular with "pkg upgrade".

You can always do it yourself by writing scripts around the pkg_* tools or using portmaster’s –packages-only option”.

While this is all true, there is still a gap for a good package manager that needs filling.