Re: pkg problem
Hello, > On Mar 28, 2017, at 2:48 PM, Alan Somers wrote: > > Try setting DEFAULT_VERSIONS=pgsql=9.6 in /etc/make.conf. Then any > ports that use postgres will have to be rebuilt from ports instead of > installed through pkg. > -Alan I believe he's using packages. > >> On Tue, Mar 28, 2017 at 12:24 PM, Jim Ohlstein wrote: >> Hello, >> >> [cc'ing to ports mailing list since it seems more appropriate there] >> >>> On 3/28/17 10:25 AM, m...@ft-c.de wrote: >>> >>> Hello, >>> >>> when I update/upgrade freebsd with pkg, >>> pkg would install the postgresql93-client, >>> but postgresql* version 9.6 is installed. >> >> >> >> It appears as though $something that you are trying to upgrade has a >> dependency on postgresql-client. Since postgresql93 is the default version >> for FreeBSD packages, $something is built against postgresql93-client, and >> is trying to pull it in as a dependency. That would cause >> postgresql96-client to be deinstalled, which would then cause pretty much >> anything postgresql96 related to be removed. Those packages are locked, >> hence the failure. >> >> >>> >>> What's going wrong? >>> Have someoen a solution? >>> >>> I get the following messages: >>> >>> % pkg upgrade >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up-to-date. >>> All repositories are up-to-date. >>> >>> postgresql96-plpython-9.6.0_1 is locked and may not be modified >>> postgresql96-plperl-9.6.0_1 is locked and may not be modified >>> postgresql96-contrib-9.6.1 is locked and may not be modified >>> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >>> postgresql96-server-9.6.1_1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-contrib-9.6.1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-plperl-9.6.0_1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> postgresql96-plperl-9.6.0_1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> postgresql96-plpython-9.6.0_1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-server-9.6.1_1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-server-9.6.1_1 is locked and may not be modified >>> postgresql96-contrib-9.6.1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> >>> The following 32 package(s) will be affected (of 0 checked): >>> >>> New packages to be INSTALLED: >>>postgresql93-client: 9.3.15_1 >>> >>> Installed packages to be UPGRADED: >>>php70-zlib: 7.0.16 -> 7.0.17 >>>... (more) >>>php70-pgsql: 7.0.16 -> 7.0.17 >>>php70-pdo_sqlite: 7.0.16 -> 7.0.17 >>>php70-pdo_pgsql: 7.0.16 -> 7.0.17 >>>php70-pdo: 7.0.16 -> 7.0.17 >>>... (more) >>>nspr: 4.13.1 -> 4.14 >>>mod_php70: 7.0.16 -> 7.0.17 >>>git: 2.11.0_3 -> 2.12.1 >>> >>> Installed packages to be REINSTALLED: >>>apache24-2.4.25_1 (options changed) >>> >>> Number of packages to be installed: 1 >>> Number of packages to be upgraded: 30 >>> Number of packages to be reinstalled: 1 >>> >>> The process will require 10 MiB more space. >>> 234 KiB to be downloaded. >>> >>> >>> >>> % pkg upgrade git >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up-to-date. >>> All repositories are up-to-date. >>> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >>> ... (more: see above) >>> >>> Checking integrity... >>> Assertion failed: (cun != NULL), function >>> pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499. >>> Child process pid=2230 terminated abnormally: Abort trap >>> >>> >>> >>> % uname -a >>> FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 >>> 06:55:27 UTC 2016 >>> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> >> >> -- >> Jim Ohlstein >> >> >> "Never argue with a fool, onlookers may not be able to tell the difference." >> - Mark Twain >> >> ___ >> freebsd-sta...@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___
Re: pkg problem
Try setting DEFAULT_VERSIONS=pgsql=9.6 in /etc/make.conf. Then any ports that use postgres will have to be rebuilt from ports instead of installed through pkg. -Alan On Tue, Mar 28, 2017 at 12:24 PM, Jim Ohlstein wrote: > Hello, > > [cc'ing to ports mailing list since it seems more appropriate there] > > On 3/28/17 10:25 AM, m...@ft-c.de wrote: >> >> Hello, >> >> when I update/upgrade freebsd with pkg, >> pkg would install the postgresql93-client, >> but postgresql* version 9.6 is installed. > > > > It appears as though $something that you are trying to upgrade has a > dependency on postgresql-client. Since postgresql93 is the default version > for FreeBSD packages, $something is built against postgresql93-client, and > is trying to pull it in as a dependency. That would cause > postgresql96-client to be deinstalled, which would then cause pretty much > anything postgresql96 related to be removed. Those packages are locked, > hence the failure. > > >> >> What's going wrong? >> Have someoen a solution? >> >> I get the following messages: >> >> % pkg upgrade >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up-to-date. >> All repositories are up-to-date. >> >> postgresql96-plpython-9.6.0_1 is locked and may not be modified >> postgresql96-plperl-9.6.0_1 is locked and may not be modified >> postgresql96-contrib-9.6.1 is locked and may not be modified >> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >> postgresql96-server-9.6.1_1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-contrib-9.6.1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-plperl-9.6.0_1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> postgresql96-plperl-9.6.0_1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> postgresql96-plpython-9.6.0_1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-server-9.6.1_1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-server-9.6.1_1 is locked and may not be modified >> postgresql96-contrib-9.6.1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> >> The following 32 package(s) will be affected (of 0 checked): >> >> New packages to be INSTALLED: >> postgresql93-client: 9.3.15_1 >> >> Installed packages to be UPGRADED: >> php70-zlib: 7.0.16 -> 7.0.17 >> ... (more) >> php70-pgsql: 7.0.16 -> 7.0.17 >> php70-pdo_sqlite: 7.0.16 -> 7.0.17 >> php70-pdo_pgsql: 7.0.16 -> 7.0.17 >> php70-pdo: 7.0.16 -> 7.0.17 >> ... (more) >> nspr: 4.13.1 -> 4.14 >> mod_php70: 7.0.16 -> 7.0.17 >> git: 2.11.0_3 -> 2.12.1 >> >> Installed packages to be REINSTALLED: >> apache24-2.4.25_1 (options changed) >> >> Number of packages to be installed: 1 >> Number of packages to be upgraded: 30 >> Number of packages to be reinstalled: 1 >> >> The process will require 10 MiB more space. >> 234 KiB to be downloaded. >> >> >> >> % pkg upgrade git >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up-to-date. >> All repositories are up-to-date. >> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >> ... (more: see above) >> >> Checking integrity... >> Assertion failed: (cun != NULL), function >> pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499. >> Child process pid=2230 terminated abnormally: Abort trap >> >> >> >> % uname -a >> FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 >> 06:55:27 UTC 2016 >> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >> >> > > -- > Jim Ohlstein > > > "Never argue with a fool, onlookers may not be able to tell the difference." > - Mark Twain > > ___ > freebsd-sta...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg problem
Hello, [cc'ing to ports mailing list since it seems more appropriate there] On 3/28/17 10:25 AM, m...@ft-c.de wrote: Hello, when I update/upgrade freebsd with pkg, pkg would install the postgresql93-client, but postgresql* version 9.6 is installed. It appears as though $something that you are trying to upgrade has a dependency on postgresql-client. Since postgresql93 is the default version for FreeBSD packages, $something is built against postgresql93-client, and is trying to pull it in as a dependency. That would cause postgresql96-client to be deinstalled, which would then cause pretty much anything postgresql96 related to be removed. Those packages are locked, hence the failure. What's going wrong? Have someoen a solution? I get the following messages: % pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. postgresql96-plpython-9.6.0_1 is locked and may not be modified postgresql96-plperl-9.6.0_1 is locked and may not be modified postgresql96-contrib-9.6.1 is locked and may not be modified pgtcl-postgresql96-2.0.0_1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgtcl-postgresql96-2.0.0_1 is locked and may not be modified postgresql96-server-9.6.1_1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-contrib-9.6.1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-plperl-9.6.0_1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified postgresql96-plperl-9.6.0_1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified postgresql96-plpython-9.6.0_1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-server-9.6.1_1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-server-9.6.1_1 is locked and may not be modified postgresql96-contrib-9.6.1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified The following 32 package(s) will be affected (of 0 checked): New packages to be INSTALLED: postgresql93-client: 9.3.15_1 Installed packages to be UPGRADED: php70-zlib: 7.0.16 -> 7.0.17 ... (more) php70-pgsql: 7.0.16 -> 7.0.17 php70-pdo_sqlite: 7.0.16 -> 7.0.17 php70-pdo_pgsql: 7.0.16 -> 7.0.17 php70-pdo: 7.0.16 -> 7.0.17 ... (more) nspr: 4.13.1 -> 4.14 mod_php70: 7.0.16 -> 7.0.17 git: 2.11.0_3 -> 2.12.1 Installed packages to be REINSTALLED: apache24-2.4.25_1 (options changed) Number of packages to be installed: 1 Number of packages to be upgraded: 30 Number of packages to be reinstalled: 1 The process will require 10 MiB more space. 234 KiB to be downloaded. % pkg upgrade git Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. pgtcl-postgresql96-2.0.0_1 is locked and may not be modified ... (more: see above) Checking integrity... Assertion failed: (cun != NULL), function pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499. Child process pid=2230 terminated abnormally: Abort trap % uname -a FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Jim Ohlstein "Never argue with a fool, onlookers may not be able to tell the difference." - Mark Twain ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg problem, not severe but tedious.
On Sun, 12 Jul 2015 18:48:32 -0700 Jeffrey Bouquet via freebsd-ports wrote > Each time across major versions I find it convenient to install one or two > upgrades ( portupgrade and another, in this case) > > pkg install portupgrade [the installworld just completed an hour or two > ago] > > I use a > script reinstall.log pkg install portupgrade > > Because > the deinstalls called for are too numerous, no option to delay [ another SQL > field? ] > > For instance > > Those two reinstalls (major version) require removal of some 200-400 of which > I note manually 35 or so for immediate reinstall later today. > > In this case > Not trivial... > > serf > apr > subversion > w3m > firefox > vte > intltool > gnutls > gsasl > gtk2 > cups-base > ...and twenty-odd others of the several hundred to be removed upon > the upgrade of portupgrade from another major version and another ruby > version to the latest one. > > So it is handy workaround, but I wonder if a combination of > 1... "delay these til later" > 2... "to be removed and logged in a /var/log/pkg-removed.log " file > 3... or some other scenario should make it more simple. > 4... a 2nd field in the 'to be removed' ... some removed because of the >ruby21 upgrade, some removed for some other reason... one could maybe > craft the request to pkg in a more orderly fashion if more information was > known at that step. Maybe. > > Obviously this does not occur in the usual course of upgrading... but those > to be removed could probably still be of use in the meantime... Not that is > is too problematic to reinstall them (usually but not always )... but it is > not as automatic as it maybe could be eventually. > > Thanks for reading. Just a thought. But what if you could NOT uninstall the many ports it uninstalls? For example; pkg install portupgrade .. the following ports/packages will be installed portupgrade BlahLib BlahApp BlahBlahApp 20mb additional space required [y]es [n]o Y .. the following 30,000 ports will be uninstalled (reclaims 10Tb) [y]es [no] N You chose NO (pkg(8) will ask this question again, next time it is used) I think something like this might be easier to implement. The only other warning that I can think that might need to be addressed, would be if one of the (proposed) deinstalls, was to satisfy the need to upgrade supporting lib(s), or applications. But in such a case, it seems it should just default to a no-op, and proceed as tho you had stated yes (for those only). Just a thought. --Chris > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pkg problem, not severe but tedious.
Each time across major versions I find it convenient to install one or two upgrades ( portupgrade and another, in this case) pkg install portupgrade [the installworld just completed an hour or two ago] I use a script reinstall.log pkg install portupgrade Because the deinstalls called for are too numerous, no option to delay [ another SQL field? ] For instance Those two reinstalls (major version) require removal of some 200-400 of which I note manually 35 or so for immediate reinstall later today. In this case Not trivial... serf apr subversion w3m firefox vte intltool gnutls gsasl gtk2 cups-base ...and twenty-odd others of the several hundred to be removed upon the upgrade of portupgrade from another major version and another ruby version to the latest one. So it is handy workaround, but I wonder if a combination of 1... "delay these til later" 2... "to be removed and logged in a /var/log/pkg-removed.log " file 3... or some other scenario should make it more simple. 4... a 2nd field in the 'to be removed' ... some removed because of the ruby21 upgrade, some removed for some other reason... one could maybe craft the request to pkg in a more orderly fashion if more information was known at that step. Maybe. Obviously this does not occur in the usual course of upgrading... but those to be removed could probably still be of use in the meantime... Not that is is too problematic to reinstall them (usually but not always )... but it is not as automatic as it maybe could be eventually. Thanks for reading. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg problem
On Thu, Nov 20, 2014 at 04:24:46AM -0800, Jeffrey Bouquet via freebsd-stable wrote: > > On 11/20/14 04:19, Jeffrey Bouquet wrote: > > Only one port has not failed at "pkg install port" ... after today's > > update and > > also failed at deinstall pkg >> install pkg-devel to try to fix it. > > > > [ Duplicate post, so I could post the error and this update. ] > > > > > > Script started on Thu Nov 20 04:09:36 2014 > > > > > > pkg --version > > 1.4.0.beta2 # pkg-devel newly installed, did not fix the below. > > > > pkg install tk86 > > Updating FreeBSD repository catalogue... > > FreeBSD repository is up-to-date. > > All repositories are up-to-date. > > > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, p2, > > PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function > > pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. Child > > process pid=41497 terminated abnormally: Abort trap: 6 > > > > > > Script done on Thu Nov 20 04:10:25 2014 Is that with pkg.freebsd.org repository, or custom one? regards, Bapt pgpS_BBzSecoI.pgp Description: PGP signature
Re: pkg problem
On 11/20/14 04:19, Jeffrey Bouquet wrote: > Only one port has not failed at "pkg install port" ... after today's > update and > also failed at deinstall pkg >> install pkg-devel to try to fix it. > > [ Duplicate post, so I could post the error and this update. ] > > > Script started on Thu Nov 20 04:09:36 2014 > > > pkg --version > 1.4.0.beta2 # pkg-devel newly installed, did not fix the below. > > pkg install tk86 > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > > Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, p2, > PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function > pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. Child > process pid=41497 terminated abnormally: Abort trap: 6 > > > Script done on Thu Nov 20 04:10:25 2014 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
