Re: port outdated show updates, port upgrade outdated say no updates available
On Sat, May 29, 2010 at 17:13, Joshua Root j...@macports.org wrote: Josh Very odd indeed. I can't replicate this with test ports with the same versions and revisions. I take it 'port echo outdated' also gives you nothing? Yes $ port outdated The following installed ports are outdated: gcc44 4.4.1_0 4.4.4_1 $ port echo outdated $ Anything interesting shown with -d? No. Is gcc44 inactive? No: $ port installed gcc44 The following ports are currently installed: gcc44 @4.4.1_0 (active) $ Does 'port -v installed gcc44' or 'port -v outdated' show anything unusual? No. The gcc44 port was at version 4.4.1_0 a while ago, i.e. for at least 7 months, and as I upgrade my outdated ports about once a week this has been a problem for a while and can't be related to the switch to 1.9.0-rc1. This has started showing up as of 1.9.0-rc1, but clearly its been a problem for a while otherwise I'd be running something newer than 4.4.1_0. Is there a way the registry could have got corrupted in some strange way that would result port to think gcc44 wasn't installed? Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On 2010-5-31 12:47 , Adam Mercer wrote: The gcc44 port was at version 4.4.1_0 a while ago, i.e. for at least 7 months, and as I upgrade my outdated ports about once a week this has been a problem for a while and can't be related to the switch to 1.9.0-rc1. This has started showing up as of 1.9.0-rc1, but clearly its been a problem for a while otherwise I'd be running something newer than 4.4.1_0. Is there a way the registry could have got corrupted in some strange way that would result port to think gcc44 wasn't installed? Maybe. Post the contents of the receipt. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On 2010-5-31 13:32 , Joshua Root wrote: On 2010-5-31 12:47 , Adam Mercer wrote: The gcc44 port was at version 4.4.1_0 a while ago, i.e. for at least 7 months, and as I upgrade my outdated ports about once a week this has been a problem for a while and can't be related to the switch to 1.9.0-rc1. This has started showing up as of 1.9.0-rc1, but clearly its been a problem for a while otherwise I'd be running something newer than 4.4.1_0. Is there a way the registry could have got corrupted in some strange way that would result port to think gcc44 wasn't installed? Maybe. Post the contents of the receipt. The quickest way to get to the bottom of this may be for you to do some good old fashioned printf debugging in get_outdated_ports, to see at what point gcc44 gets excluded from the list. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On Sun, May 30, 2010 at 22:32, Joshua Root j...@macports.org wrote: Is there a way the registry could have got corrupted in some strange way that would result port to think gcc44 wasn't installed? Maybe. Post the contents of the receipt. I've uploaded it to http://www.lsc-group.phys.uwm.edu/~ram/files/receipt.bz2, as I'm not sure what to look for. Is this the correct one for the sqlite registry? Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On Sun, May 30, 2010 at 22:41, Joshua Root j...@macports.org wrote: The quickest way to get to the bottom of this may be for you to do some good old fashioned printf debugging in get_outdated_ports, to see at what point gcc44 gets excluded from the list. I'll take a look, although I'm not very familier with the base code... Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On 2010-5-31 13:53 , Adam Mercer wrote: On Sun, May 30, 2010 at 22:41, Joshua Root j...@macports.org wrote: The quickest way to get to the bottom of this may be for you to do some good old fashioned printf debugging in get_outdated_ports, to see at what point gcc44 gets excluded from the list. I'll take a look, although I'm not very familier with the base code... You want proc get_outdated_ports, which in trunk starts at line 707 of src/port/port.tcl. Hopefully it's not too hard to follow. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On Sun, May 30, 2010 at 23:01, Joshua Root j...@macports.org wrote: You want proc get_outdated_ports, which in trunk starts at line 707 of src/port/port.tcl. Hopefully it's not too hard to follow. Thanks, found it... just got to learn the basic of tcl now :-) Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On 2010-5-31 13:52 , Adam Mercer wrote: On Sun, May 30, 2010 at 22:32, Joshua Root j...@macports.org wrote: Is there a way the registry could have got corrupted in some strange way that would result port to think gcc44 wasn't installed? Maybe. Post the contents of the receipt. I've uploaded it to http://www.lsc-group.phys.uwm.edu/~ram/files/receipt.bz2, as I'm not sure what to look for. Is this the correct one for the sqlite registry? Well, that actually explains a lot. The receipt has 'epoch 2', while the current portfile is at epoch 1. No idea how it got there unless you used a modified portfile at some point, but in any case the epoch value would have been carried over into the sqlite registry. (You can check this by opening the registry.db with the sqlite3 tool and running the .dump command.) But the real question is now why 'port outdated' is *incorrectly* showing gcc44 as outdated. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On Sun, May 30, 2010 at 23:06, Joshua Root j...@macports.org wrote: Well, that actually explains a lot. The receipt has 'epoch 2', while the current portfile is at epoch 1. No idea how it got there unless you used a modified portfile at some point, but in any case the epoch value would have been carried over into the sqlite registry. (You can check this by opening the registry.db with the sqlite3 tool and running the .dump command.) Yes, it's marked as epoch 2: INSERT INTO ports VALUES(39,'gcc44','',NULL,'/opt/local/var/macports/software/gcc44/4.4.1_0',2,'4.4.1',0,'','','installed',1252817603,'image','',0,'',''); I can't recall bumping the epoch, but this is from at least 7 months ago... But the real question is now why 'port outdated' is *incorrectly* showing gcc44 as outdated. How can I be of help in tracking that down? Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On 2010-5-31 14:14 , Adam Mercer wrote: On Sun, May 30, 2010 at 23:06, Joshua Root j...@macports.org wrote: Well, that actually explains a lot. The receipt has 'epoch 2', while the current portfile is at epoch 1. No idea how it got there unless you used a modified portfile at some point, but in any case the epoch value would have been carried over into the sqlite registry. (You can check this by opening the registry.db with the sqlite3 tool and running the .dump command.) Yes, it's marked as epoch 2: INSERT INTO ports VALUES(39,'gcc44','',NULL,'/opt/local/var/macports/software/gcc44/4.4.1_0',2,'4.4.1',0,'','','installed',1252817603,'image','',0,'',''); I can't recall bumping the epoch, but this is from at least 7 months ago... But the real question is now why 'port outdated' is *incorrectly* showing gcc44 as outdated. How can I be of help in tracking that down? I think I got it (r68286). Please test. :-) - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port outdated show updates, port upgrade outdated say no updates available
On 2010-5-30 03:25 , Adam Mercer wrote: Hi Just updated to base 1.9.0-rc1, and switched to sqlite based registry, and found an interesting problem: $ port outdated The following installed ports are outdated: gcc44 4.4.1_0 4.4.4_1 $ sudo port -u upgrade outdated Error: No ports matched the given expression $ any idea why port outdated is saying that gcc44 requires an update but when I try to perform the update there are no matching ports? If I specify the portname, i.e. gcc44, the upgrade starts as expected. Very odd indeed. I can't replicate this with test ports with the same versions and revisions. I take it 'port echo outdated' also gives you nothing? Anything interesting shown with -d? Is gcc44 inactive? Does 'port -v installed gcc44' or 'port -v outdated' show anything unusual? - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
