The MacPorts team is very proud to announce our third release of MacPorts within several days. The pace of change has been fast and furious. This time we're just furious: Release 1.4.3 (17-Apr-2007): - Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151). - add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148). If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue. James
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate DarwinPorts base version 1.101 installed Selfupdate failed: couldn't open "/opt/local/var/db/dports/sources/ rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file or directory
Greg Shenaut On Apr 17, 2007, at 5:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Hi Greg, You have darwinports 1.101 installed? We hoped we'd left all those users behind (or better, that they'd all upgraded by now). Support for upgrades from 1.1 was lost sometime around 1.4. Your best bet will be to re-install from the MacPorts 1.4 disk image available at http://trac.macosforge.org/projects/macports/browser/downloads/ MacPorts-1.4.0. Doing that should install a new copy of the MacPorts code over darwinports, hopefully leaving your installed ports intact. Did I get all that right? James On Apr 17, 2007, at 6:26 PM, Greg Shenaut wrote:
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate DarwinPorts base version 1.101 installed Selfupdate failed: couldn't open "/opt/local/var/db/dports/sources/ rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file or directory
Greg Shenaut
On Apr 17, 2007, at 5:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those users behind (or better, that they'd all upgraded by now).
Support for upgrades from 1.1 was lost sometime around 1.4. Your best bet will be to re-install from the MacPorts 1.4 disk image available at http://trac.macosforge.org/projects/macports/browser/ downloads/MacPorts-1.4.0.
Doing that should install a new copy of the MacPorts code over darwinports, hopefully leaving your installed ports intact.
Did I get all that right?
Well, now it says
DarwinPorts base version 1.400 installed Downloaded MacPorts base version 1.430 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: selfupdate failed: Error installing new MacPorts base: shell command "cd /opt/local/var/db/dports/sources/ rsync.rsync.darwinports.org_dpupdate1/base && ./configure --prefix=/ opt/local --with-install-user=root --with-install-group=admin -- with-tclpackage=/Library/Tcl && make && make install" returned error 2 ... sha1cmd.c: In function 'SHA1Cmd': sha1cmd.c:79: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function) sha1cmd.c:79: error: (Each undeclared identifier is reported only once sha1cmd.c:79: error: for each function it appears in.) sha1cmd.c:100: warning: implicit declaration of function 'SHA1_File' sha1cmd.c:79: warning: unused variable 'buf' make[2]: *** [sha1cmd.o] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
Greg
James
On Apr 17, 2007, at 6:26 PM, Greg Shenaut wrote:
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate DarwinPorts base version 1.101 installed Selfupdate failed: couldn't open "/opt/local/var/db/dports/ sources/rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file or directory
Greg Shenaut
On Apr 17, 2007, at 5:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Hi Greg, What Mac OS X system version are you running? And have you installed the latest xcode? James On Apr 17, 2007, at 8:29 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those users behind (or better, that they'd all upgraded by now).
Support for upgrades from 1.1 was lost sometime around 1.4. Your best bet will be to re-install from the MacPorts 1.4 disk image available at http://trac.macosforge.org/projects/macports/browser/ downloads/MacPorts-1.4.0.
Doing that should install a new copy of the MacPorts code over darwinports, hopefully leaving your installed ports intact.
Did I get all that right?
Well, now it says
DarwinPorts base version 1.400 installed Downloaded MacPorts base version 1.430 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: selfupdate failed: Error installing new MacPorts base: shell command "cd /opt/local/var/db/dports/ sources/rsync.rsync.darwinports.org_dpupdate1/base && ./configure --prefix=/opt/local --with-install-user=root --with-install- group=admin --with-tclpackage=/Library/Tcl && make && make install" returned error 2 ... sha1cmd.c: In function 'SHA1Cmd': sha1cmd.c:79: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function) sha1cmd.c:79: error: (Each undeclared identifier is reported only once sha1cmd.c:79: error: for each function it appears in.) sha1cmd.c:100: warning: implicit declaration of function 'SHA1_File' sha1cmd.c:79: warning: unused variable 'buf' make[2]: *** [sha1cmd.o] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
Greg
James
On Apr 17, 2007, at 6:26 PM, Greg Shenaut wrote:
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate DarwinPorts base version 1.101 installed Selfupdate failed: couldn't open "/opt/local/var/db/dports/ sources/rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file or directory
Greg Shenaut
On Apr 17, 2007, at 5:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Apr 17, 2007, at 8:33 PM, James Berry wrote:
Hi Greg,
What Mac OS X system version are you running? And have you installed the latest xcode?
10.4.9 PPC, XCODE 2.4 Greg
James
On Apr 17, 2007, at 8:29 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those users behind (or better, that they'd all upgraded by now).
Support for upgrades from 1.1 was lost sometime around 1.4. Your best bet will be to re-install from the MacPorts 1.4 disk image available at http://trac.macosforge.org/projects/macports/ browser/downloads/MacPorts-1.4.0.
Doing that should install a new copy of the MacPorts code over darwinports, hopefully leaving your installed ports intact.
Did I get all that right?
Well, now it says
DarwinPorts base version 1.400 installed Downloaded MacPorts base version 1.430 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: selfupdate failed: Error installing new MacPorts base: shell command "cd /opt/local/var/db/dports/ sources/rsync.rsync.darwinports.org_dpupdate1/base && ./configure --prefix=/opt/local --with-install-user=root --with-install- group=admin --with-tclpackage=/Library/Tcl && make && make install" returned error 2 ... sha1cmd.c: In function 'SHA1Cmd': sha1cmd.c:79: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function) sha1cmd.c:79: error: (Each undeclared identifier is reported only once sha1cmd.c:79: error: for each function it appears in.) sha1cmd.c:100: warning: implicit declaration of function 'SHA1_File' sha1cmd.c:79: warning: unused variable 'buf' make[2]: *** [sha1cmd.o] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
Greg
James
On Apr 17, 2007, at 6:26 PM, Greg Shenaut wrote:
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate DarwinPorts base version 1.101 installed Selfupdate failed: couldn't open "/opt/local/var/db/dports/ sources/rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file or directory
Greg Shenaut
On Apr 17, 2007, at 5:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Apr 17, 2007, at 8:55 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 8:33 PM, James Berry wrote:
Hi Greg,
What Mac OS X system version are you running? And have you installed the latest xcode?
10.4.9 PPC, XCODE 2.4
Greg. Hmm. I haven't seen any issues with that sha1 code in practically forever, and it certainly hasn't been changed recently. I suspect you have a funky copy of openssl installed, perhaps in /usr/ local? Or something weird with your headers? The copy of /usr/include/ openssl/sha.h on my system certainly has those thing in it, but perhaps some other header is being picked up for you? James
Greg
James
On Apr 17, 2007, at 8:29 PM, Greg Shenaut wrote:
On Apr 17, 2007, at 6:44 PM, James Berry wrote:
Hi Greg,
You have darwinports 1.101 installed? We hoped we'd left all those users behind (or better, that they'd all upgraded by now).
Support for upgrades from 1.1 was lost sometime around 1.4. Your best bet will be to re-install from the MacPorts 1.4 disk image available at http://trac.macosforge.org/projects/macports/ browser/downloads/MacPorts-1.4.0.
Doing that should install a new copy of the MacPorts code over darwinports, hopefully leaving your installed ports intact.
Did I get all that right?
Well, now it says
DarwinPorts base version 1.400 installed Downloaded MacPorts base version 1.430 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: selfupdate failed: Error installing new MacPorts base: shell command "cd /opt/local/var/db/dports/ sources/rsync.rsync.darwinports.org_dpupdate1/base && ./ configure --prefix=/opt/local --with-install-user=root --with- install-group=admin --with-tclpackage=/Library/Tcl && make && make install" returned error 2 ... sha1cmd.c: In function 'SHA1Cmd': sha1cmd.c:79: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function) sha1cmd.c:79: error: (Each undeclared identifier is reported only once sha1cmd.c:79: error: for each function it appears in.) sha1cmd.c:100: warning: implicit declaration of function 'SHA1_File' sha1cmd.c:79: warning: unused variable 'buf' make[2]: *** [sha1cmd.o] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
Greg
James
On Apr 17, 2007, at 6:26 PM, Greg Shenaut wrote:
What does this message mean? (And what do I need to do about it?)
% sudo port selfupdate DarwinPorts base version 1.101 installed Selfupdate failed: couldn't open "/opt/local/var/db/dports/ sources/rsync.rsync.opendarwin.org_dpupdate1/base/dp_version": no such file or directory
Greg Shenaut
On Apr 17, 2007, at 5:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Apr 17, 2007, at 8:58 PM, James Berry wrote:
The MacPorts team is very proud to announce our third release of MacPorts within several days.
The pace of change has been fast and furious. This time we're just furious:
Release 1.4.3 (17-Apr-2007):
- Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151).
- add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148).
I upgraded MacPorts to 1.4.3 and am having serious issues with X11. I have reinstalled X11User.pkg and X11SDK.pkg, and along the way X11Update2006.pkg. When trying to install gnuplot I get XFree86 listed as a dependency. Does anybody have any idea how I can fix things? gnuplot has library dependencies on: expat fontconfig freetype gd2 jpeg pdflib libiconv libpng ncurses readline teTeX XFree86 zlib Thanks, George
If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue.
James _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
On Apr 20, 2007, at 20:25, George A. Dowding wrote:
I upgraded MacPorts to 1.4.3 and am having serious issues with X11. I have reinstalled X11User.pkg and X11SDK.pkg, and along the way X11Update2006.pkg. When trying to install gnuplot I get XFree86 listed as a dependency. Does anybody have any idea how I can fix things?
gnuplot has library dependencies on: expat fontconfig freetype gd2 jpeg pdflib libiconv libpng ncurses readline teTeX XFree86 zlib
I don't think there's any problem here. gnuplot will find Apple's X11 if it's installed, and use the XFree86 port otherwise, just like every other port that uses X. Did you actually try to install gnuplot?
participants (4)
-
George A. Dowding
-
Greg Shenaut
-
James Berry
-
Ryan Schmidt