I just told MacPorts to upgrade Subversion. As part of doing this, it decided to upgrade openssl. However, there was no difference in version string! ---> Deactivating openssl 0.9.8d_0+darwin_8 ---> Uninstalling openssl 0.9.8d_0+darwin_8 ---> Installing openssl 0.9.8d_0+darwin_8 ---> Activating openssl 0.9.8d_0+darwin_8 Any idea why it decided to do this? -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
Ok, looking further it seems zlib and apr also did this. So for some reason, `sudo port upgrade -uf subversion` decided to reinstall *all* dependencies, as near as I can tell. Any ideas what's going on? On Dec 25, 2006, at 10:04 PM, Kevin Ballard wrote:
I just told MacPorts to upgrade Subversion. As part of doing this, it decided to upgrade openssl. However, there was no difference in version string!
---> Deactivating openssl 0.9.8d_0+darwin_8 ---> Uninstalling openssl 0.9.8d_0+darwin_8 ---> Installing openssl 0.9.8d_0+darwin_8 ---> Activating openssl 0.9.8d_0+darwin_8
Any idea why it decided to do this?
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
On Dec 25, 2006, at 21:42, Kevin Ballard wrote:
On Dec 25, 2006, at 10:04 PM, Kevin Ballard wrote:
I just told MacPorts to upgrade Subversion. As part of doing this, it decided to upgrade openssl. However, there was no difference in version string!
---> Deactivating openssl 0.9.8d_0+darwin_8 ---> Uninstalling openssl 0.9.8d_0+darwin_8 ---> Installing openssl 0.9.8d_0+darwin_8 ---> Activating openssl 0.9.8d_0+darwin_8
Any idea why it decided to do this?
Ok, looking further it seems zlib and apr also did this.
So for some reason, `sudo port upgrade -uf subversion` decided to reinstall *all* dependencies, as near as I can tell.
Any ideas what's going on?
Yes -- you told it to. That's what "-f" does. It forces the reinstall, even if MacPorts doesn't think it needs to. If you just want to reinstall Subversion and not its dependencies, also use the "-n" flag.
Ah, then the meaning has changed. I always pass -f to upgrade because otherwise MacPorts refuses to deactivate the old version if the are any ports which depend on it, despite the fact that it's about to activate the new version. In times past, the -f flag did not force it to upgrade dependencies that didn't need the upgrade. I want to upgrade out-of-date dependencies, I just also want to actually install the damn thing. Is there any solution to this right now? On Dec 26, 2006, at 12:57 AM, Ryan Schmidt wrote:
Yes -- you told it to. That's what "-f" does. It forces the reinstall, even if MacPorts doesn't think it needs to.
If you just want to reinstall Subversion and not its dependencies, also use the "-n" flag.
-- Kevin Ballard http://kevin.sb.org kevin@sb.org http://www.tildesoft.com
On Dec 26, 2006, at 00:05, Kevin Ballard wrote:
On Dec 26, 2006, at 12:57 AM, Ryan Schmidt wrote:
Yes -- you told it to. That's what "-f" does. It forces the reinstall, even if MacPorts doesn't think it needs to.
If you just want to reinstall Subversion and not its dependencies, also use the "-n" flag.
Ah, then the meaning has changed. I always pass -f to upgrade because otherwise MacPorts refuses to deactivate the old version if the are any ports which depend on it, despite the fact that it's about to activate the new version.
Yeah, annoying.
In times past, the -f flag did not force it to upgrade dependencies that didn't need the upgrade.
I didn't know that.
I want to upgrade out-of-date dependencies, I just also want to actually install the damn thing.
Is there any solution to this right now?
Personally, I know which of the ports I use require which other ports, so I manually "sudo port -ncuf upgrade foo" for each port, in the correct order (e.g., if apr, apr-util and subversion all need updating, do them in that order). I don't know if there's a better more-automated way.
On Dec 26, 2006, at 1:19 AM, Ryan Schmidt wrote:
In times past, the -f flag did not force it to upgrade dependencies that didn't need the upgrade.
I didn't know that.
Yep, but that changed a while ago (1.2-1.3 IIRC).
I want to upgrade out-of-date dependencies, I just also want to actually install the damn thing.
Is there any solution to this right now?
Personally, I know which of the ports I use require which other ports, so I manually "sudo port -ncuf upgrade foo" for each port, in the correct order (e.g., if apr, apr-util and subversion all need updating, do them in that order).
I don't know if there's a better more-automated way.
If you're really lucky, you can do: port -dvnf upgrade outdated ... but if you need to rebuild in a specific order to satisfy dependencies correctly, then it probably won't work. patches to the upgrade code to make it smarter are, of course, welcome :) -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
Hi all, I hope someone can help me with the following problem: On a clean, updated, synced installation of MacPorts, OSX 10.4.8, I cannot build py-wxpython. All dependencies build and install fine, but py-wxpython itself fails with a slew of errors, the first few of which are: src/helpers.cpp:2763: error: 'stream' was not declared in this scope src/helpers.cpp:2763: error: expected %<,%> or %<;%> before '{' token src/helpers.cpp:2786: error: 'bool wxPyImageHandler::LoadFile' is not a static member of 'class wxPyImageHandler' src/helpers.cpp:2786: error: 'wxImage' was not declared in this scope src/helpers.cpp:2786: error: 'image' was not declared in this scope src/helpers.cpp:2786: error: 'wxInputStream' was not declared in this scope src/helpers.cpp:2786: error: 'stream' was not declared in this scope src/helpers.cpp:2787: error: expected primary-expression before "bool" src/helpers.cpp:2787: error: expected primary-expression before "int" src/helpers.cpp:2787: error: initializer expression list treated as compound expression I get the impression there's a small typo somewhere in helpers.cpp, but I don't know any c++... TIA Bas
On 29.12.2006, at 12.46, Bas den Hond wrote:
Hi all,
I hope someone can help me with the following problem:
On a clean, updated, synced installation of MacPorts, OSX 10.4.8, I cannot build py-wxpython. All dependencies build and install fine, but py-wxpython itself fails with a slew of errors, the first few of which are:
src/helpers.cpp:2763: error: 'stream' was not declared in this scope src/helpers.cpp:2763: error: expected %<,%> or %<;%> before '{' token src/helpers.cpp:2786: error: 'bool wxPyImageHandler::LoadFile' is not a static member of 'class wxPyImageHandler' src/helpers.cpp:2786: error: 'wxImage' was not declared in this scope src/helpers.cpp:2786: error: 'image' was not declared in this scope src/helpers.cpp:2786: error: 'wxInputStream' was not declared in this scope src/helpers.cpp:2786: error: 'stream' was not declared in this scope src/helpers.cpp:2787: error: expected primary-expression before "bool" src/helpers.cpp:2787: error: expected primary-expression before "int" src/helpers.cpp:2787: error: initializer expression list treated as compound expression
I get the impression there's a small typo somewhere in helpers.cpp, but I don't know any c++...
TIA
Bas
Hi, wxWidgets (2.8.0) and py-wxpython (2.8.0.1) seem to be out of sync at the moment, can you wait a while!? Current py-wxpython port is targeted to wxWidgets 2.6.3 (its version is 2.6.3.2), it is no wonder it does not build. The current wxWidgets tarball is missing a file (at least one) making it impossible to build py-wxpython just now. ! ! Jyrki Wahlstedt ! skype:jyrkiwahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386
Hi Jyrki, Thanks for clearing that up. I'll be patient... But this brings up, for me at least, two questions about how MacPorts works. - Shouldn't the 'port' program have told me that py-wxpython can't find the wxWidgets version it has to work with, instead of having gcc stumble around until some fatal error comes around? - Wouldn't my problem be solved right now if the maintainer of wxWidgets had kept the older version available? Is it yet somewhere to be had? Please tell me if I should direct questions/suggestions of this nature somewhere else, instead of to this list. Bas
Hi, wxWidgets (2.8.0) and py-wxpython (2.8.0.1) seem to be out of sync at the moment, can you wait a while!? Current py-wxpython port is targeted to wxWidgets 2.6.3 (its version is 2.6.3.2), it is no wonder it does not build.
The current wxWidgets tarball is missing a file (at least one) making it impossible to build py-wxpython just now. ! ! Jyrki Wahlstedt ! skype:jyrkiwahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386
On 29.12.2006, at 12.46, Bas den Hond wrote:
Hi all,
I hope someone can help me with the following problem:
On a clean, updated, synced installation of MacPorts, OSX 10.4.8, I cannot build py-wxpython. All dependencies build and install fine, but py-wxpython itself fails with a slew of errors, the first few of which are:
src/helpers.cpp:2763: error: 'stream' was not declared in this scope src/helpers.cpp:2763: error: expected %<,%> or %<;%> before '{' token src/helpers.cpp:2786: error: 'bool wxPyImageHandler::LoadFile' is not a static member of 'class wxPyImageHandler' src/helpers.cpp:2786: error: 'wxImage' was not declared in this scope src/helpers.cpp:2786: error: 'image' was not declared in this scope src/helpers.cpp:2786: error: 'wxInputStream' was not declared in this scope src/helpers.cpp:2786: error: 'stream' was not declared in this scope src/helpers.cpp:2787: error: expected primary-expression before "bool" src/helpers.cpp:2787: error: expected primary-expression before "int" src/helpers.cpp:2787: error: initializer expression list treated as compound expression
I get the impression there's a small typo somewhere in helpers.cpp, but I don't know any c++...
TIA
Bas
Bas den Hond <lists@butdifferent.com> on Friday, December 29, 2006 at 2:46 AM -0800 wrote:
I hope someone can help me with the following problem:
On a clean, updated, synced installation of MacPorts, OSX 10.4.8, I cannot build py-wxpython. All dependencies build and install fine, but py-wxpython itself fails with a slew of errors, the first few of which are:
src/helpers.cpp:2763: error: 'stream' was not declared in this scope src/helpers.cpp:2763: error: expected %<,%> or %<;%> before '{' token src/helpers.cpp:2786: error: 'bool wxPyImageHandler::LoadFile' is not a static member of 'class wxPyImageHandler' src/helpers.cpp:2786: error: 'wxImage' was not declared in this scope src/helpers.cpp:2786: error: 'image' was not declared in this scope src/helpers.cpp:2786: error: 'wxInputStream' was not declared in this scope src/helpers.cpp:2786: error: 'stream' was not declared in this scope src/helpers.cpp:2787: error: expected primary-expression before "bool" src/helpers.cpp:2787: error: expected primary-expression before "int" src/helpers.cpp:2787: error: initializer expression list treated as compound expression
I get the impression there's a small typo somewhere in helpers.cpp, but I don't know any c++...
You could download 2.8.0.1 from http://www.wxpython.org, find the checksum (openssl sha1 /path-to-download/wxPython-src) and then change the version and checksum in the portfile, then try to install it like normal. The old version must have broken with the wxwidget 2.8.0 update. If it works then the port could be updated. mww is the maintainer but he hasn't been active lately. I'm on a slow download link and can't try it now. Mark
Tried it. No luck... After changing the version and the checksum, and converting the bz2 source file to gz, I could extract and patch. But when I start the build, I get essentially the same errors. Under port -v build, the first few are all in this vein: In file included from src/helpers.cpp:16: include/wx/wxPython/wxPython_int.h:19:19: error: wx/wx.h: No such file or directory This sounds like wxWidgets isn't putting its header files where it should, or wxpython isn't looking where it should. It would be interesting to try and put back the old version of wxWidgets the same way... Bas
Bas den Hond <lists@butdifferent.com> on Friday, December 29, 2006 at 2:46 AM -0800 wrote:
I hope someone can help me with the following problem:
On a clean, updated, synced installation of MacPorts, OSX 10.4.8, I cannot build py-wxpython. All dependencies build and install fine, but py-wxpython itself fails with a slew of errors, the first few of which are:
src/helpers.cpp:2763: error: 'stream' was not declared in this scope src/helpers.cpp:2763: error: expected %<,%> or %<;%> before '{' token src/helpers.cpp:2786: error: 'bool wxPyImageHandler::LoadFile' is not a static member of 'class wxPyImageHandler' src/helpers.cpp:2786: error: 'wxImage' was not declared in this scope src/helpers.cpp:2786: error: 'image' was not declared in this scope src/helpers.cpp:2786: error: 'wxInputStream' was not declared in this scope src/helpers.cpp:2786: error: 'stream' was not declared in this scope src/helpers.cpp:2787: error: expected primary-expression before "bool" src/helpers.cpp:2787: error: expected primary-expression before "int" src/helpers.cpp:2787: error: initializer expression list treated as compound expression
I get the impression there's a small typo somewhere in helpers.cpp, but I don't know any c++...
You could download 2.8.0.1 from http://www.wxpython.org, find the checksum (openssl sha1 /path-to-download/wxPython-src) and then change the version and checksum in the portfile, then try to install it like normal. The old version must have broken with the wxwidget 2.8.0 update. If it works then the port could be updated. mww is the maintainer but he hasn't been active lately. I'm on a slow download link and can't try it now.
Mark
Bas den Hond <lists@butdifferent.com> on Monday, January 1, 2007 at 4:25 PM -0800 wrote:
It would be interesting to try and put back the old version of wxWidgets the same way...
If you want to try an old port (MacPorts has no facility for this), go to the wiki and click the "sources" link and find out the changes that were made in the update and reverse them on your local copy. Then re-install. If you want to see if paths have changed, do a 'port contents wxwidgets' before downgrading it. Mark
Do you mean the 'Browse source' link? I tried digging around, but I only found the latest portfile for wxWidgets.
find out the changes that were made in the update and reverse them on your local copy.
Could you be a bit more specific about 'finding out the changes'? TIA, Bas
Bas den Hond <lists@butdifferent.com> on Tuesday, January 2, 2007 at 3:36 PM -0800 wrote:
Do you mean the 'Browse source' link? I tried digging around, but I only found the latest portfile for wxWidgets.
find out the changes that were made in the update and reverse them on your local copy.
Could you be a bit more specific about 'finding out the changes'?
TIA,
Bas
http://trac.macosforge.org/projects/macports/browser/trunk/dports/graphics/w... Revision log -> Changeset (for 2.8.0 update) and you'll see a diff that will tell you what changes were made. Anytime you want to see source changes, just go to the Wiki and click "Browse Sources", locate your portfile in the tree and do the same thing. Mark
Ok, I have upgraded py-wxpython to 2.8.0.1. It, however, means that wxWidgets depends now on wxWdigets-devel, because wxWidgets 2.8.0 has at least one file missing (wx/srchctrl.h). wxWidgets-level is from their CVS_HEAD. This had to be used, because the next wxWidgets release will be 2.8.1, I suppose. I'll update py-wxpython as soon as it's available, provided all the tarballs are in sync, which was not the case with 2.8.0. HTH, On 2.1.2007, at 2.25, Bas den Hond wrote:
Tried it. No luck...
After changing the version and the checksum, and converting the bz2 source file to gz, I could extract and patch. But when I start the build, I get essentially the same errors. Under port -v build, the first few are all in this vein:
In file included from src/helpers.cpp:16: include/wx/wxPython/wxPython_int.h:19:19: error: wx/wx.h: No such file or directory
This sounds like wxWidgets isn't putting its header files where it should, or wxpython isn't looking where it should.
It would be interesting to try and put back the old version of wxWidgets the same way...
Bas
Bas den Hond <lists@butdifferent.com> on Friday, December 29, 2006 at 2:46 AM -0800 wrote:
I hope someone can help me with the following problem:
On a clean, updated, synced installation of MacPorts, OSX 10.4.8, I cannot build py-wxpython. All dependencies build and install fine, but py-wxpython itself fails with a slew of errors, the first few of which are:
src/helpers.cpp:2763: error: 'stream' was not declared in this scope src/helpers.cpp:2763: error: expected %<,%> or %<;%> before '{' token src/helpers.cpp:2786: error: 'bool wxPyImageHandler::LoadFile' is not a static member of 'class wxPyImageHandler' src/helpers.cpp:2786: error: 'wxImage' was not declared in this scope src/helpers.cpp:2786: error: 'image' was not declared in this scope src/helpers.cpp:2786: error: 'wxInputStream' was not declared in this scope src/helpers.cpp:2786: error: 'stream' was not declared in this scope src/helpers.cpp:2787: error: expected primary-expression before "bool" src/helpers.cpp:2787: error: expected primary-expression before "int" src/helpers.cpp:2787: error: initializer expression list treated as compound expression
I get the impression there's a small typo somewhere in helpers.cpp, but I don't know any c++...
You could download 2.8.0.1 from http://www.wxpython.org, find the checksum (openssl sha1 /path-to-download/wxPython-src) and then change the version and checksum in the portfile, then try to install it like normal. The old version must have broken with the wxwidget 2.8.0 update. If it works then the port could be updated. mww is the maintainer but he hasn't been active lately. I'm on a slow download link and can't try it now.
Mark
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
! ! Jyrki Wahlstedt ! skype:jyrkiwahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386
Thanks a lot! Meanwhile, I succeeded yesterday in making do with wxWidgets 2.6.3, by putting back the old Portfile that I found at the legacy Darwinports site (less work than working out the diff from the MacPorts site). But having 2.8.0.1 is much better, I'm led to believe, so I'll start trying it out right away. I learned my lesson, though: I am now a collector of Portfiles, and I will be backing up, not throwing away the old ones... Bas
Ok, I have upgraded py-wxpython to 2.8.0.1. It, however, means that wxWidgets depends now on wxWdigets-devel, because wxWidgets 2.8.0 has at least one file missing (wx/srchctrl.h). wxWidgets-level is from their CVS_HEAD. This had to be used, because the next wxWidgets release will be 2.8.1, I suppose. I'll update py-wxpython as soon as it's available, provided all the tarballs are in sync, which was not the case with 2.8.0.
HTH,
On 2.1.2007, at 2.25, Bas den Hond wrote:
On Jan 7, 2007, at 15:49, Bas den Hond wrote:
I learned my lesson, though: I am now a collector of Portfiles, and I will be backing up, not throwing away the old ones...
There is no need to do anything like that. You could instead switch your port tree over to a Subversion checkout, and then you can "update" any file to any prior version with the "svn up" command.
participants (6)
-
Bas den Hond
-
Daniel J. Luke
-
Jyrki Wahlstedt
-
Kevin Ballard
-
Mark Duling
-
Ryan Schmidt