Re: pkgng vs. portupgrade reporting ports outdated
On 04/04/2014 23:02, sindrome wrote: So I still keep my source, ports and docs in sync via svn update. Here's where the issue comes in. After I have done the pkg upgrade and it tells me all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens of ports that are not up-to-date and further the versions it's saying I have installed are not consistent with the versions that were installed through pkgng. If I try and portupgrade it won't upgrade the ports and just returns me to the prompt as if there is nothing out of date. Why is there such a difference here? It seems that if I do a pkgng update / pkg upgrade it should be consistent with the same versions that are being reported after an 'svn update' and report back that all ports are up-to-date no matter which command I type. So now I can't seem to upgrade through portupgrade to get the rest of the ports to the versions reported in the ports tree and pkgng says I'm up-to-date. Once you have switched to pkg(8), the old pkg_tools commands will return bogus results. You *cannot* mix usage of pkg(8) and pkg_tools. I don't know why this seems to be such a difficult concept for people to understand. In your case, you need to use 'pkg version -v' not 'pkg_version -v'. Actually instead of this: pkg version -v | grep needs Try this: pkg version -vIl\ That compares your installed ports to what is listed as available in the ports index. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: pkgng vs. portupgrade reporting ports outdated
On 04/04/2014 23:49, Robert Huff wrote: pkgng can do almost everything the old system can, and does it better. s/almost// pkg(8) does a damn sight more than the old pkg_tools. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: pkgng vs. portupgrade reporting ports outdated
On 05/04/2014 00:44, sindrome wrote: foo:109:/home/foobar# pkg_version -v |grep needs it shows 240 ports that need updating. It shows that you have out-of-date data in the remains of the old-style /var/db/pkg that pkg2ng leaves in place. Please execute the following command to clean up /var/db/pkg and leave just the database that pkg(8) uses: # find /var/db/pkg -mindepth 1 -type d -print0 | xargs -0 rm -rf Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
Matthew Seaman matt...@freebsd.org writes: pkg(8) does a damn sight more than the old pkg_tools. Granted, though much of it I currently have little use for. :-) pkgng can do almost everything the old system can, and does it better. s/almost// OK, Obi-wan - what's the replacement for: a) portsclean with the C, D (single and double), and L options? (Use no more than two commands.) b) pkg_sort ? With these, I will cheerfully delete portupgrade. Robert Huff ___ 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: pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
On Sat, 05 Apr 2014 07:55:48 -0400 Robert Huff wrote: Matthew Seaman matt...@freebsd.org writes: pkg(8) does a damn sight more than the old pkg_tools. Granted, though much of it I currently have little use for. :-) pkgng can do almost everything the old system can, and does it better. s/almost// OK, Obi-wan - what's the replacement for: a) portsclean with the C, D (single and double), and L options? (Use no more than two commands.) b) pkg_sort ? With these, I will cheerfully delete portupgrade. portupgrade isn't part of the old pkg_tools ___ 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: pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
-Original Message- From: Robert Huff OK, Obi-wan - what's the replacement for: a) portsclean with the C, D (single and double), and L options? (Use no more than two commands.) b) pkg_sort ? With these, I will cheerfully delete portupgrade. portupgrade != pkg_old Actually, for me portupgrade with pkgng is getting close the ideal solution, made yesterday the portsnap fetch upgrade portversion -v | grep -v '=' portupgrade -rf php5 dance and got the whole php rebuild from source with one minor hitch. Due the way extensions.ini is rebuilt every php installation I got wrong module order and couple of modules got signal 11's when trying to rebuild. After manually correcting extensions.ini order I just portupgrade -f'd the 2 failed packages in dependency order, this time without any problems. pkgng pretty nicely built just the stuff that needed rebuild, not half the installed ports. I'm already running php in cgi mode, so no mod for apache was needed (and due the recent improvement, the said mod was not autoinstalled to my httpd.conf either). -Reko ___ 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
pkgng vs. portupgrade reporting ports outdated
I'm a bit confused so I figured to see if someone can help me understand the new pkgng system better. Before using it, I have always done a cvs update (now svn update) to the ports tree and I would do a simple 'pkg_version -v|grep needs' to see what ports were out-of-date and then portupgrade those specific ports. After I successfully built the latest versions everything was in sync. With pkgng I issue a 'pkg update' followed by a 'pkg upgrade' and it shows me x number of ports that need to be updated. So it updates and completes just fine and of course it's much faster than building from source. So I still keep my source, ports and docs in sync via svn update. Here's where the issue comes in. After I have done the pkg upgrade and it tells me all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens of ports that are not up-to-date and further the versions it's saying I have installed are not consistent with the versions that were installed through pkgng. If I try and portupgrade it won't upgrade the ports and just returns me to the prompt as if there is nothing out of date. Why is there such a difference here? It seems that if I do a pkgng update / pkg upgrade it should be consistent with the same versions that are being reported after an 'svn update' and report back that all ports are up-to-date no matter which command I type. So now I can't seem to upgrade through portupgrade to get the rest of the ports to the versions reported in the ports tree and pkgng says I'm up-to-date. It's one thing if pkgng doesn't have all the packages pre-compiled but then it should let me portupgrade from the ports tree for those ports that aren't available through pkgng. I would like to get the rest of my ports up-to-date with the ports tree like it used to work. ___ 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: pkgng vs. portupgrade reporting ports outdated
sindrome sindr...@gmail.com With pkgng I issue a 'pkg update' followed by a 'pkg upgrade' and it shows me x number of ports that need to be updated. So it updates and completes just fine and of course it's much faster than building from source. So I still keep my source, ports and docs in sync via svn update. Here's where the issue comes in. After I have done the pkg upgrade and it tells me all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens of ports that are not up-to-date and further the versions it's saying I have installed are not consistent with the versions that were installed through pkgng. It is my understanding it is generally a bad idea to mix the old and new package systems. (It can be done, but it's beyond my pay grade and if you're asking this I'd guess it is - at the moment - beyond yours.) pkgng can do almost everything the old system can, and does it better. (Now if it only had a replacement for pkg_sort ) Each records its status quo in distinct and incompatible ways. When I want to know what needs updating I use: huff pkg version -v -l \ which I can send either to a file, or to e-mail, or to a script wrapped around portmaster. Does this help? Respectfully, Robert Huff ___ 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: pkgng vs. portupgrade reporting ports outdated
It is my understanding it is generally a bad idea to mix the old and new package systems. (It can be done, but it's beyond my pay grade and if you're asking this I'd guess it is - at the moment - beyond yours.) pkgng can do almost everything the old system can, and does it better. (Now if it only had a replacement for pkg_sort ) Each records its status quo in distinct and incompatible ways. When I want to know what needs updating I use: huff pkg version -v -l \ which I can send either to a file, or to e-mail, or to a script wrapped around portmaster. Does this help? Thanks Robert, but that wasn't the question. There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says. Pkgng is reporting that everything is up-to-date and pkg_version is saying there are dozens of ports not up to date.I'd be more than happy to use pkgng but it's clearly not seeing the same information as pkg_version. ___ 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: pkgng vs. portupgrade reporting ports outdated
-Original Message- From: sindrome [mailto:sindr...@gmail.com] Sent: Friday, April 04, 2014 6:37 PM To: 'Robert Huff' Cc: po...@freebsd.org Subject: RE: pkgng vs. portupgrade reporting ports outdated It is my understanding it is generally a bad idea to mix the old and new package systems. (It can be done, but it's beyond my pay grade and if you're asking this I'd guess it is - at the moment - beyond yours.) pkgng can do almost everything the old system can, and does it better. (Now if it only had a replacement for pkg_sort ) Each records its status quo in distinct and incompatible ways. When I want to know what needs updating I use: huff pkg version -v -l \ which I can send either to a file, or to e-mail, or to a script wrapped around portmaster. Does this help? Here's more information foo:107:/home/foobar# pkg update Updating repository catalogue foo:108:/home/foobar# pkg upgrade Updating repository catalogue Nothing to do Now when I do a 'pkg_version -v|grep needs' I have foo:109:/home/foobar# pkg_version -v |grep needs it shows 240 ports that need updating. akonadi-1.11.0_1 needs updating (port has 1.12.0) analitza-4.12.2needs updating (port has 4.12.4) apr-1.4.8.1.5.3needs updating (port has 1.5.0.1.5.3) ark-4.12.2 needs updating (port has 4.12.4) avogadro-1.1.1_1 needs updating (port has 1.1.1_2) bash-4.2.45_1 needs updating (port has 4.3.0_1) blinken-4.12.2 needs updating (port has 4.12.4) bomber-4.12.2 needs updating (port has 4.12.4) bovo-4.12.2needs updating (port has 4.12.4) ca_root_nss-3.15.4 needs updating (port has 3.15.5) cantor-4.12.2 needs updating (port has 4.12.4) clang33-3.3_5 needs updating (port has 3.3_6) cmake-2.8.12.1 needs updating (port has 2.8.12.1_4) cups-client-1.5.4_1needs updating (port has 1.7.1) cups-image-1.5.4_1 needs updating (port has 1.7.1) curl-7.35.0needs updating (port has 7.36.0) cyrus-sasl-2.1.26_4needs updating (port has 2.1.26_5) dconf-0.14.1 needs updating (port has 0.14.1_1) dejavu-2.34_2 needs updating (port has 2.34_3) docbook-4.1_4 needs updating (port has 4.5_1) docbook-4.2needs updating (port has 4.5_1) docbook-4.3needs updating (port has 4.5_1) docbook-4.4_2 needs updating (port has 4.5_1) docbook-sk-4.1.2_4 needs updating (port has 5.0_1) docbook-xml-4.3needs updating (port has 5.0_1) docbook-xml-4.4_1 needs updating (port has 5.0_1) docbook-xml-4.5needs updating (port has 5.0_1) dragon-player-4.12.2 needs updating (port has 4.12.4) eigen-3.2.0needs updating (port has 3.2.1) facile-1.1_2 needs updating (port has 1.1_3) file-5.16 needs updating (port has 5.18) filelight-4.12.2 needs updating (port has 4.12.4) flex-2.5.38_2 needs updating (port has 2.5.39) fping-3.5 needs updating (port has 3.8) freetype2-2.5.2needs updating (port has 2.5.3) gamin-0.1.10_6 needs updating (port has 0.1.10_7) ghostscript9-9.06_4needs updating (port has 9.06_5) gmp-5.1.3 needs updating (port has 5.1.3_1) gnupg1-1.4.16 needs updating (port has 1.4.16_1) gnutls-2.12.23_3 needs updating (port has 2.12.23_4) granatier-4.12.2 needs updating (port has 4.12.4) gwenview-4.10.5_1 needs updating (port has 4.12.4) imlib2-1.4.6,2 needs updating (port has 1.4.6_1,2) isc-dhcp42-server-4.2.6needs updating (port has 4.2.6_1) ja-kiten-4.12.2needs updating (port has 4.12.4) jovie-4.12.2 needs updating (port has 4.12.4) juk-4.12.2 needs updating (port has 4.12.4) kaccessible-4.12.2 needs updating (port has 4.12.4) kactivities-4.10.5_3 needs updating (port has 4.12.4) kactivitymanagerd-4.10.5_3 needs updating (port has 4.12.4) kajongg-4.10.5_1 needs updating (port has 4.12.4) kalgebra-4.12.2needs updating (port has 4.12.4) kalzium-4.12.2 needs updating (port has 4.12.4) kamera-4.12.2
Re: pkgng vs. portupgrade reporting ports outdated
On Fri, Apr 4, 2014 at 4:44 PM, sindrome sindr...@gmail.com wrote: Here's more information foo:107:/home/foobar# pkg update Updating repository catalogue foo:108:/home/foobar# pkg upgrade Updating repository catalogue Nothing to do Now when I do a 'pkg_version -v|grep needs' I have pkg_* tools use the old packages database, while the pkg tool uses its own, new, database. After you upgraded to pkgng and started using it for all your package needs, your old database stopped being updated (because the old pkg_* tools aren't being used to install packages anymore). This is why the old pkg_* tools are still reporting old version information - they only see what's in their old database. Anton ___ 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: pkgng vs. portupgrade reporting ports outdated
On Fri, 4 Apr 2014, sindrome wrote: There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says. Of course. pkg_version looks at the text files in /var/db/pkg, while pkg looks at the database local.sqlite in that directory. The first step in using pkg is running pkg2ng, which imports the old information from the text files into the sqlite table. After that, pkg_version should not be used. It's getting information from an outdated database. ___ 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: pkgng vs. portupgrade reporting ports outdated
So now the way to keep ports up-to-date is to execute 'pkg update' and 'pkg upgrade'? Are you saying I shouldn't svn update the ports tree anymore? oz:132:/usr/local/etc# pkg update oz:133:/usr/local/etc# pkg upgrade -Original Message- From: Warren Block [mailto:wbl...@wonkity.com] Sent: Friday, April 04, 2014 9:23 PM To: sindrome Cc: 'Robert Huff'; po...@freebsd.org Subject: RE: pkgng vs. portupgrade reporting ports outdated On Fri, 4 Apr 2014, sindrome wrote: There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says. Of course. pkg_version looks at the text files in /var/db/pkg, while pkg looks at the database local.sqlite in that directory. The first step in using pkg is running pkg2ng, which imports the old information from the text files into the sqlite table. After that, pkg_version should not be used. It's getting information from an outdated database. ___ 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: pkgng vs. portupgrade reporting ports outdated
Okay so just 'pkg update' followed by 'pkg upgrade' after svn update? On Apr 4, 2014, at 11:09 PM, Warren Block wbl...@wonkity.com wrote: On Fri, 4 Apr 2014, sindrome wrote: From: Warren Block [mailto:wbl...@wonkity.com] Sent: Friday, April 04, 2014 9:23 PM To: sindrome Cc: 'Robert Huff'; po...@freebsd.org Subject: RE: pkgng vs. portupgrade reporting ports outdated On Fri, 4 Apr 2014, sindrome wrote: There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says. Of course. pkg_version looks at the text files in /var/db/pkg, while pkg looks at the database local.sqlite in that directory. The first step in using pkg is running pkg2ng, which imports the old information from the text files into the sqlite table. After that, pkg_version should not be used. It's getting information from an outdated database. So now the way to keep ports up-to-date is to execute 'pkg update' and 'pkg upgrade'? Are you saying I shouldn't svn update the ports tree anymore? No, I did not say that. By switching from the old pkg_* tools to pkg, all you have done is changed which database is being used to track what is installed. Nothing else needs to change. ___ 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: pkgng vs. portupgrade reporting ports outdated
On Fri, 4 Apr 2014, sindrome wrote: From: Warren Block [mailto:wbl...@wonkity.com] Sent: Friday, April 04, 2014 9:23 PM To: sindrome Cc: 'Robert Huff'; po...@freebsd.org Subject: RE: pkgng vs. portupgrade reporting ports outdated On Fri, 4 Apr 2014, sindrome wrote: There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says. Of course. pkg_version looks at the text files in /var/db/pkg, while pkg looks at the database local.sqlite in that directory. The first step in using pkg is running pkg2ng, which imports the old information from the text files into the sqlite table. After that, pkg_version should not be used. It's getting information from an outdated database. So now the way to keep ports up-to-date is to execute 'pkg update' and 'pkg upgrade'? Are you saying I shouldn't svn update the ports tree anymore? No, I did not say that. By switching from the old pkg_* tools to pkg, all you have done is changed which database is being used to track what is installed. Nothing else needs to change. ___ 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: pkgng vs. portupgrade reporting ports outdated
On Fri, 4 Apr 2014, Sindrome wrote: On Apr 4, 2014, at 11:09 PM, Warren Block wbl...@wonkity.com wrote: On Fri, 4 Apr 2014, sindrome wrote: From: Warren Block [mailto:wbl...@wonkity.com] On Fri, 4 Apr 2014, sindrome wrote: There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says. Of course. pkg_version looks at the text files in /var/db/pkg, while pkg looks at the database local.sqlite in that directory. The first step in using pkg is running pkg2ng, which imports the old information from the text files into the sqlite table. After that, pkg_version should not be used. It's getting information from an outdated database. So now the way to keep ports up-to-date is to execute 'pkg update' and 'pkg upgrade'? Are you saying I shouldn't svn update the ports tree anymore? No, I did not say that. By switching from the old pkg_* tools to pkg, all you have done is changed which database is being used to track what is installed. Nothing else needs to change. Okay so just 'pkg update' followed by 'pkg upgrade' after svn update? [Please stop top-posting, it makes replying to your messages more difficult.] No. If you want to use ports (I do), use ports. pkg will keep track of them. Commands like pkg info replace the old versions of those commands, like pkg_info. pkg update or pkg upgrade are only used when the user wants to use binary packages instead of ports. ___ 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
