faxien - Project Hosting on Google Code

Yesterday 37 hours ago faxien-launcher-i386-Darwin-9.8.0-V10.sh (Mac Intel 10.5 Leopard (kernel version 9.8.0 or greater requ...) file uploaded by martinjlogan - Labels: Type-Installer OpSys-OSX Labels: Type-Installer OpSys-OSX Older Nov 30, 2009 issue 129 (Faxien crashes when there is not enough disk space) reported by zishan.mirza18 - What steps will reproduce the problem? 1. Run the bootstrapper when there is not enough disk space. What is the expected output? What do you see instead? Expected output: If there is not enough disk space, then Faxien should issue a warning about this. Actual output (output sent from Henrik Sandklef): Henrik Sandklef sent this log: tar: lib/xmerl-1.1.12/include/xmerl.hrl: Cannot open: No such file or directory tar: lib/xmerl-1.1.12/include/xmerl_xsd.hrl: Cannot open: No such file or directory tar: lib/xmerl-1.1.12/ebin: Cannot mkdir: No such file or directory tar: lib/xmerl-1.1.12/ebin/xmerl_b64Bin.beam: Cannot open: No such file or directory tar: lib/xmerl-1.1.12/ebin/xmerl_ucs.beam: Cannot open: No such file or directory gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now * Faxien is now installed * What steps will reproduce the problem? 1. Run the bootstrapper when there is not enough disk space. What is the expected output? What do you see instead? Expected output: If there is not enough disk space, then Faxien should issue a warning about this. Actual output (output sent from Henrik Sandklef): Henrik Sandklef sent this log: tar: lib/xmerl-1.1.12/include/xmerl.hrl: Cannot open: No such file or directory tar: lib/xmerl-1.1.12/include/xmerl_xsd.hrl: Cannot open: No such file or directory tar: lib/xmerl-1.1.12/ebin: Cannot mkdir: No such file or directory tar: lib/xmerl-1.1.12/ebin/xmerl_b64Bin.beam: Cannot open: No such file or directory tar: lib/xmerl-1.1.12/ebin/xmerl_ucs.beam: Cannot open: No such file or directory gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now * Faxien is now installed * Nov 27, 2009 issue 128 (faxien install PREFIX detection failure.) reported by kogakazuo - What steps will reproduce the problem? 1. Install faxien to default /usr/local/erlware 2. $ cd /usr/local/bin && ln -s /usr/local/erlware/bin/faxien . 3. $ /usr/local/bin/faxien help What is the expected output? What do you see instead? faxien command failed. /usr/local/bin/faxien: line 25: /usr/local/erts-5.7.1/bin/erlexec: No such file or directory What version of the product are you using? On what operating system? Darwin my.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386 faxien-launcher-i386-Darwin-9.7.0-V9.sh Please provide any additional information below. Could you pull patch? git://github.com/kkazuo/faxien.git What steps will reproduce the problem? 1. Install faxien to default /usr/local/erlware 2. $ cd /usr/local/bin && ln -s /usr/local/erlware/bin/faxien . 3. $ /usr/local/bin/faxien help What is the expected output? What do you see instead? faxien command failed. /usr/local/bin/faxien: line 25: /usr/local/erts-5.7.1/bin/erlexec: No such file or directory What version of the product are you using? On what operating system? Darwin my.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386 faxien-launcher-i386-Darwin-9.7.0-V9.sh Please provide any additional information below. Could you pull patch? git://github.com/kkazuo/faxien.git Aug 06, 2009 issue 127 (faxien breaks SSL by removing exec bits from ssl_esock) reported by emofine - What steps will reproduce the problem? Linux xxxx 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009 x86_64 GNU/Linux Faxien Version is 0.42.1.2 1. Ensure that the ssl application is installed (faxien ia ssl) 2. Change the exec flags of ssl_esock (chmod +x $EWHOME/lib/ssl-XXX/priv/bin/ssl_esock) 3. Find or write an app that uses the above Erlang ssl application and has it as a dependency in the .app file. 4. Build it with sinan dist. 5. Check the file permissions of ssl_esock. The execute bits will be set. 6. Check the execute bits in the Sinan-produced tarball file (_build/development/tar/...). They will also be set. 7. Install the app using faxien (faxien ir). 8. Check the file permissions of ssl_esock. The execute bits will be cleared. Conclusion: faxien, or something it uses, it wrongly clearing the bits on the ssl_esock file, causing this error to occur EVERY TIME the application is installed using faxien ir and the executed: exec: 1: /usr/local/erlware/lib/ssl-3.10.3/priv/bin/ssl_esock: Permission denied This has caused HOURS of problems. Please consider this to be a top priority CRITICAL bug for anyone using ssl and Erlware. The workaround, of course, is to set the ssl_esock file permissions correctly "by hand" (chmod +x $EWHOME/lib/ssl-XXX/priv/bin/ssl_esock), but this is a Very Bad Thing to have to do and to have to remember to put in startup scripts and the like. It begs the question: which other files may be installed with the incorrect permissions? It's worth fixing this in a general way. Finally, please note that this bug has been reported before by me and at least one other person, and reportedly fixed by a patch from Mikael Magnusson in December '08 (see http://www.mail-archive.com/erlware-dev@googlegroups.com/msg00259.html). However, the patch evidently either did not work or still has not been included in the Erlware release. What steps will reproduce the problem? Linux xxxx 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009 x86_64 GNU/Linux Faxien Version is 0.42.1.2 1. Ensure that the ssl application is installed (faxien ia ssl) 2. Change the exec flags of ssl_esock (chmod +x $EWHOME/lib/ssl-XXX/priv/bin/ssl_esock) 3. Find or write an app that uses the above Erlang ssl application and has it as a dependency in the .app file. 4. Build it with sinan dist. 5. Check the file permissions of ssl_esock. The execute bits will be set. 6. Check the execute bits in the Sinan-produced tarball file (_build/development/tar/...). They will also be set. 7. Install the app using faxien (faxien ir). 8. Check the file permissions of ssl_esock. The execute bits will be cleared. Conclusion: faxien, or something it uses, it wrongly clearing the bits on the ssl_esock file, causing this error to occur EVERY TIME the application is installed using faxien ir and the executed: exec: 1: /usr/local/erlware/lib/ssl-3.10.3/priv/bin/ssl_esock: Permission denied This has caused HOURS of problems. Please consider this to be a top priority CRITICAL bug for anyone using ssl and Erlware. The workaround, of course, is to set the ssl_esock file permissions correctly "by hand" (chmod +x $EWHOME/lib/ssl-XXX/priv/bin/ssl_esock), but this is a Very Bad Thing to have to do and to have to remember to put in startup scripts and the like. It begs the question: which other files may be installed with the incorrect permissions? It's worth fixing this in a general way. Finally, please note that this bug has been reported before by me and at least one other person, and reportedly fixed by a patch from Mikael Magnusson in December '08 (see http://www.mail-archive.com/erlware-dev@googlegroups.com/msg00259.html). However, the patch evidently either did not work or still has not been included in the Erlware release. Jul 30, 2009 issue 126 (upgrade-all-apps doesn't) changed by martinjlogan - The problem is a directory in your erlware/lib called "booble". This was my fault and came from my adding directories booble and boble during a smoke test but only deleting one of them before creating the bootstrapper. The current bootstrappers don't have this problem but you still have it as a remnant of using the old bootstrapper. Delete this directory and the function will work. Status: Invalid Owner: martinjlogan The problem is a directory in your erlware/lib called "booble". This was my fault and came from my adding directories booble and boble during a smoke test but only deleting one of them before creating the bootstrapper. The current bootstrappers don't have this problem but you still have it as a remnant of using the old bootstrapper. Delete this directory and the function will work. Status: Invalid Owner: martinjlogan Jul 30, 2009 issue 30 (Refactor faxien in such a way as to make it more testable - ...) Status changed by martinjlogan - Status: WontFix Status: WontFix Jul 30, 2009 issue 126 (upgrade-all-apps doesn't) Status changed by martinjlogan - I will look into this. Can you send me a directory listing of your erlware/lib directory? Status: Accepted I will look into this. Can you send me a directory listing of your erlware/lib directory? Status: Accepted Jul 30, 2009 issue 126 (upgrade-all-apps doesn't) reported by emofine - # faxien upgrade-all-apps "The package directory provided is not of the form <name>-<version>" Suggestions: - Make sure you have the correct permissions to run Faxien - For sasl log information look at "/tmp/faxien.sasl_log" What version of the product are you using? On what operating system? Faxien Version is 0.42.1.2 The preferred erts version "5.7.2" Linux xxx 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Linux Please provide any additional information below. # faxien upgrade-all-apps "The package directory provided is not of the form <name>-<version>" Suggestions: - Make sure you have the correct permissions to run Faxien - For sasl log information look at "/tmp/faxien.sasl_log" What version of the product are you using? On what operating system? Faxien Version is 0.42.1.2 The preferred erts version "5.7.2" Linux xxx 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Linux Please provide any additional information below. Jul 28, 2009 issue 116 (install-release error if any dot-directories in app bin dire...) changed by martinjlogan - This is quite odd. I will reproduce and fix. The book writing is making things a bit slow and I am going out of the country starting aug 1 to aug 9. I will get to it after that. If you don't see a fix shortly thereafter please ping me again and I will look at this. Status: Accepted Owner: martinjlogan This is quite odd. I will reproduce and fix. The book writing is making things a bit slow and I am going out of the country starting aug 1 to aug 9. I will get to it after that. If you don't see a fix shortly thereafter please ping me again and I will look at this. Status: Accepted Owner: martinjlogan Jul 28, 2009 issue 116 (install-release error if any dot-directories in app bin dire...) commented on by emofine - A new behavior now: faxien will not copy the bin directory if there are any files starting with '.' (period). This is a killer because I use Vim and when editing a script in the bin directory, there is a .scriptname.swp file open in the bin directory. This is repeatable and easy to see, because if I remove the ..swp files from the bin directory in the tarball, along with any .svn or .git subdirectories, faxien says "Replacing binary file foo". If I don't remove such files, the message does not appear and I don't get my script changes. The workaround is to run a script that cleans the tarball of all .svn, .git. and ..sw? files. But if I forget to do this, I am in trouble. A new behavior now: faxien will not copy the bin directory if there are any files starting with '.' (period). This is a killer because I use Vim and when editing a script in the bin directory, there is a .scriptname.swp file open in the bin directory. This is repeatable and easy to see, because if I remove the ..swp files from the bin directory in the tarball, along with any .svn or .git subdirectories, faxien says "Replacing binary file foo". If I don't remove such files, the message does not appear and I don't get my script changes. The workaround is to run a script that cleans the tarball of all .svn, .git. and ..sw? files. But if I forget to do this, I am in trouble. Jul 04, 2009 issue 125 (Crypto-1.6.0 is broken related Issue-124) commented on by justin.venus - Martin, permisions are messed up and even after this is fixed dynamic linking is still broken for the ports driver. I found another broken ports drivers as well "ssl". The attached script will patch, configure and build an otp release for all posix systems that i have access too (Solaris sparc, Solaris x86_64, PPC OSX, i386 OSX, i386 linux, ppc linux, and x86_64 linux). I have used this script build releases for myself since R12 was released. Martin, permisions are messed up and even after this is fixed dynamic linking is still broken for the ports driver. I found another broken ports drivers as well "ssl". The attached script will patch, configure and build an otp release for all posix systems that i have access too (Solaris sparc, Solaris x86_64, PPC OSX, i386 OSX, i386 linux, ppc linux, and x86_64 linux). I have used this script build releases for myself since R12 was released. Jun 24, 2009 issue 121 (Publish says it fails on HTTP 204 but doesn't) commented on by martinjlogan - I don't know either, I am going to go look tonight. I don't know either, I am going to go look tonight. Jun 23, 2009 issue 116 (install-release error if any dot-directories in app bin dire...) commented on by emofine - This doesn't cause crashes any more, but dot-files are still copied even if they are not binaries. This doesn't cause crashes any more, but dot-files are still copied even if they are not binaries. Jun 23, 2009 issue 121 (Publish says it fails on HTTP 204 but doesn't) commented on by emofine - I don't know if this was changed or not but I have not seen that error for a while now. You can probably close this. I don't know if this was changed or not but I have not seen that error for a while now. You can probably close this. Jun 23, 2009 issue 71 (Flip the switch to using .epkg) Status changed by martinjlogan - No longer a priority Status: WontFix No longer a priority Status: WontFix Jun 23, 2009 issue 110 (support for inter-release dependencies) Labels changed by martinjlogan - Labels: Priority-Low −Priority-Medium Labels: Priority-Low −Priority-Medium Jun 23, 2009 issue 119 (Existing sys.config overwritten without asking) Status changed by martinjlogan - Status: Invalid Status: Invalid Jun 23, 2009 issue 49 (Get Faxien working on windows) Labels changed by martinjlogan - Labels: Priority-Low −Priority-High Labels: Priority-Low −Priority-High Jun 23, 2009 issue 125 (Crypto-1.6.0 is broken related Issue-124) Status changed by martinjlogan - Is the crypto_drv not there, or are the perms messed up? Status: Acknowledged Is the crypto_drv not there, or are the perms messed up? Status: Acknowledged Jun 23, 2009 issue 125 (Crypto-1.6.0 is broken related Issue-124) reported by justin.venus - What steps will reproduce the problem? 1. Fedora 11 x86_64 2. application:start(crypto) What is the expected output? What do you see instead? Erlang R13B (erts-5.7.1) [source] [64-bit] [smp:2:2] [rq:2] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.7.1 (abort with ^G) 1> application:start(crypto). sh: line 0: exec: crypto_drv: not found =INFO REPORT==== 23-Jun-2009::09:41:30 === application: crypto exited: {shutdown,{crypto_app,start,[normal,[]]}} type: temporary {error,{shutdown,{crypto_app,start,[normal,[]]}}} Please use labels and text to provide additional information. Issue-124 explains how to fix this issue. What steps will reproduce the problem? 1. Fedora 11 x86_64 2. application:start(crypto) What is the expected output? What do you see instead? Erlang R13B (erts-5.7.1) [source] [64-bit] [smp:2:2] [rq:2] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.7.1 (abort with ^G) 1> application:start(crypto). sh: line 0: exec: crypto_drv: not found =INFO REPORT==== 23-Jun-2009::09:41:30 === application: crypto exited: {shutdown,{crypto_app,start,[normal,[]]}} type: temporary {error,{shutdown,{crypto_app,start,[normal,[]]}}} Please use labels and text to provide additional information. Issue-124 explains how to fix this issue. Jun 18, 2009 faxien-launcher-i686-Linux-V9.sh (Linux i686) file uploaded by martinjlogan - Labels: Type-Installer OpSys-Linux Labels: Type-Installer OpSys-Linux Jun 17, 2009 faxien-launcher-x86_64-Linux-2.6.29-V9.sh (Linux x86_64) file uploaded by dave.peticolas - Labels: Featured Type-Installer OpSys-Linux Labels: Featured Type-Installer OpSys-Linux Jun 14, 2009 faxien-launcher-i386-FreeBSD-6.2-V9.sh (FreeBSD) file uploaded by martinjlogan - Labels: Type-Installer OpSys-FreeBSD Labels: Type-Installer OpSys-FreeBSD Jun 12, 2009 faxien-launcher-i386-Darwin-9.7.0-V9.sh (Mac Intel 10.5 Leopard (kernel version 9.4.0 or greater requ...) file uploaded by martinjlogan - Labels: Type-Installer OpSys-OSX Labels: Type-Installer OpSys-OSX May 13, 2009 faxien-launcher-Power-Macintosh-Darwin-8.11.0-V8.sh (Mac Tiger Intel) file uploaded by martinjlogan - Labels: Type-Installer OpSys-OSX Labels: Type-Installer OpSys-OSX May 13, 2009 faxien-launcher-x86_64-Linux-V8.sh (Linux x86_64) file uploaded by martinjlogan - Labels: OpSys-Linux Type-Installer Labels: OpSys-Linux Type-Installer May 12, 2009 faxien-launcher-i686-Linux-V8.sh (Linux i686) file uploaded by martinjlogan - Labels: Type-Installer OpSys-Linux Labels: Type-Installer OpSys-Linux May 11, 2009 BuildingBootstrapperUnix Wiki page edited by martinjlogan May 09, 2009 faxien-launcher-i386-Darwin-9.6.0-V8.sh (Mac Intel 10.5 Leopard (kernel version 9.4.0 or greater requ...) file uploaded by martinjlogan - Labels: Type-Installer OpSys-OSX Labels: Type-Installer OpSys-OSX Mar 29, 2009 issue 124 (Crypto module (crypto-1.5.2) is broken) commented on by justin.venus - ignore "--prefix=%{_prefix} \" it will break. ignore "--prefix=%{_prefix} \" it will break. Mar 28, 2009 issue 124 (Crypto module (crypto-1.5.2) is broken) reported by justin.venus - What steps will reproduce the problem? 1. ${PATH_TO_ERLWARE}/erlware/bin/erl 2. crypto:start() 3. fail What is the expected output? What do you see instead? On Fedora 10 x86-64 crypto:start() reports Eshell V5.6.3 (abort with ^G) 1> crypto:start(). {error,{shutdown,{crypto_app,start,[normal,[]]}}} =INFO REPORT==== 28-Mar-2009::13:01:04 === application: crypto exited: {shutdown,{crypto_app,start,[normal,[]]}} type: temporary 2> sh: line 0: exec: crypto_drv: not found On OSX 10.5 crypto starts but is missing alot of the documented functions. http://erlang.org/doc/man/crypto.html What version of the product are you using? On what operating system? R12b3 OSX 10.5 and Fedora10 x86-64 Please provide any additional information below. If erlang is build with the following modifications everything works as it should. It is also part of the specfile for erlang from Fedora 9. cd $OTP_SRC_DIR # enable dynamic linking for ssl # sorry this is messy, but portable to all POSIX systems sed 's\|SSL_DYNAMIC_ONLY=no\|SSL_DYNAMIC_ONLY=yes\|' erts/configure > zzz mv zzz erts/configure sed 's\|^LD.=.\|LD = gcc -shared\|' lib/common_test/c_src/Makefile > zzz mv zzz lib/common_test/c_src/Makefile CFLAGS="-fno-strict-aliasing" ./configure \ --enable-threads \ --enable-kernel-poll \ --prefix=%{_prefix} \ --exec-prefix=/usr \ --bindir=/usr/bin \ --libdir=/usr/lib \ --disable-sctp \ --enable-dynamic-ssl-lib \ --enable-hipe make make INSTALL_PREFIX=/tmp/erlang install #clean up garbage find /tmp/erlang/usr/lib/erlang -perm 0775 \| xargs chmod 755 find /tmp/erlang/usr/lib/erlang -name Makefile \| xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \.o \| xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \.bat \| xargs rm -f find /tmp/erlang/usr/lib/erlang -name index.txt.old \| xargs rm -f #sorry this is messy, but it is portable to all POSIX systems cd /tmp/erlang/usr/lib/erlang cd erts* sed "s\|/tmp/erlang\|\|" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s\|/tmp/erlang\|\|" bin/start > zzz mv zzz bin/start chmod 755 bin/start cd .. sed "s\|/tmp/erlang\|\|" releases/RELEASES >zzz mv zzz releases/RELEASES sed "s\|/tmp/erlang\|\|" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s\|/tmp/erlang\|\|" bin/start > zzz mv zzz bin/start chmod 755 bin/start What steps will reproduce the problem? 1. ${PATH_TO_ERLWARE}/erlware/bin/erl 2. crypto:start() 3. fail What is the expected output? What do you see instead? On Fedora 10 x86-64 crypto:start() reports Eshell V5.6.3 (abort with ^G) 1> crypto:start(). {error,{shutdown,{crypto_app,start,[normal,[]]}}} =INFO REPORT==== 28-Mar-2009::13:01:04 === application: crypto exited: {shutdown,{crypto_app,start,[normal,[]]}} type: temporary 2> sh: line 0: exec: crypto_drv: not found On OSX 10.5 crypto starts but is missing alot of the documented functions. http://erlang.org/doc/man/crypto.html What version of the product are you using? On what operating system? R12b3 OSX 10.5 and Fedora10 x86-64 Please provide any additional information below. If erlang is build with the following modifications everything works as it should. It is also part of the specfile for erlang from Fedora 9. cd $OTP_SRC_DIR # enable dynamic linking for ssl # sorry this is messy, but portable to all POSIX systems sed 's\|SSL_DYNAMIC_ONLY=no\|SSL_DYNAMIC_ONLY=yes\|' erts/configure > zzz mv zzz erts/configure sed 's\|^LD.=.\|LD = gcc -shared\|' lib/common_test/c_src/Makefile > zzz mv zzz lib/common_test/c_src/Makefile CFLAGS="-fno-strict-aliasing" ./configure \ --enable-threads \ --enable-kernel-poll \ --prefix=%{_prefix} \ --exec-prefix=/usr \ --bindir=/usr/bin \ --libdir=/usr/lib \ --disable-sctp \ --enable-dynamic-ssl-lib \ --enable-hipe make make INSTALL_PREFIX=/tmp/erlang install #clean up garbage find /tmp/erlang/usr/lib/erlang -perm 0775 \| xargs chmod 755 find /tmp/erlang/usr/lib/erlang -name Makefile \| xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \.o \| xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \.bat \| xargs rm -f find /tmp/erlang/usr/lib/erlang -name index.txt.old \| xargs rm -f #sorry this is messy, but it is portable to all POSIX systems cd /tmp/erlang/usr/lib/erlang cd erts* sed "s\|/tmp/erlang\|\|" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s\|/tmp/erlang\|\|" bin/start > zzz mv zzz bin/start chmod 755 bin/start cd .. sed "s\|/tmp/erlang\|\|" releases/RELEASES >zzz mv zzz releases/RELEASES sed "s\|/tmp/erlang\|\|" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s\|/tmp/erlang\|\|" bin/start > zzz mv zzz bin/start chmod 755 bin/start Jan 12, 2009 issue 123 (fixes for header.txt and create_bootstrap.sh) changed by martinjlogan - Status: Acknowledged Owner: dizzyd Status: Acknowledged Owner: dizzyd Jan 12, 2009 issue 120 (bootstrap-builder fails on solaris) changed by martinjlogan - Status: Acknowledged Owner: dizzyd Status: Acknowledged Owner: dizzyd Jan 12, 2009 issue 123 (fixes for header.txt and create_bootstrap.sh) reported by justin.venus - What steps will reproduce the problem? 1. Solaris 5.10+ 2. ./create_bootstrap.sh What is the expected output? What do you see instead? should be:"faxien-launcher-i86pc-SunOS-5.11-V6.sh" is: (epic failure) ./create_bootstrap.sh: syntax error at line 37: `ERTS_VSN=$' unexpected What version of the product are you using? On what operating system? Solaris 5.11 Please provide any additional information below. 1) bootstrap.patch fixes create_bootstrap.sh. 2) header_txt.patch will allow for a workable bootstrap to be created. These patches will still allow the resulting shell scripts to work on other systems. Tested on OSX 10.5 and Solaris. What steps will reproduce the problem? 1. Solaris 5.10+ 2. ./create_bootstrap.sh What is the expected output? What do you see instead? should be:"faxien-launcher-i86pc-SunOS-5.11-V6.sh" is: (epic failure) ./create_bootstrap.sh: syntax error at line 37: `ERTS_VSN=$' unexpected What version of the product are you using? On what operating system? Solaris 5.11 Please provide any additional information below. 1) bootstrap.patch fixes create_bootstrap.sh. 2) header_txt.patch will allow for a workable bootstrap to be created. These patches will still allow the resulting shell scripts to work on other systems. Tested on OSX 10.5 and Solaris. Jan 12, 2009 issue 120 (bootstrap-builder fails on solaris) commented on by justin.venus - The main issue you are facing with create_bootstrap.sh is that it is /bin/sh script with bashism's in it. Most Linux distros symlink /bin/sh to /bin/bash, not the case on solaris. Another issue you will run into is the way tar works on solaris. The attached patch will generate "faxien-launcher-i86pc-SunOS-5.11-V6.sh". /usr/gnu/bin/patch create_bootstrap.sh < bootstrap.patch The launcher script also needs to be modified for solaris, because /usr/bin/tail does not work the way the laucher script expects, you can use /usr/xpg4/bin/tail for that and fix the bashisms. When you finally get faxien installed you will need to edit the shabang line from #!/bin/sh to #!/bin/bash good luck. Justin Venus The main issue you are facing with create_bootstrap.sh is that it is /bin/sh script with bashism's in it. Most Linux distros symlink /bin/sh to /bin/bash, not the case on solaris. Another issue you will run into is the way tar works on solaris. The attached patch will generate "faxien-launcher-i86pc-SunOS-5.11-V6.sh". /usr/gnu/bin/patch create_bootstrap.sh < bootstrap.patch The launcher script also needs to be modified for solaris, because /usr/bin/tail does not work the way the laucher script expects, you can use /usr/xpg4/bin/tail for that and fix the bashisms. When you finally get faxien installed you will need to edit the shabang line from #!/bin/sh to #!/bin/bash good luck. Justin Venus Dec 21, 2008 issue 97 (named repos & optional publish args) commented on by emofine - Thinking along similar lines, what if a consulting firm has multiple clients, each of which have a different repository that should be used? I would like faxien to look at the _build.cfg, in which is something like publish_repositories : ["http://my.main.client/erlware", "http://my.private.repo/ew"], faxien publish would then push out the release only to the listed repos. How potentially disastrous (and legally expensive) would it be if you published the code (source and all!) for one customer and it would up on all customers' repo sites??!! Thinking along similar lines, what if a consulting firm has multiple clients, each of which have a different repository that should be used? I would like faxien to look at the _build.cfg, in which is something like publish_repositories : ["http://my.main.client/erlware", "http://my.private.repo/ew"], faxien publish would then push out the release only to the listed repos. How potentially disastrous (and legally expensive) would it be if you published the code (source and all!) for one customer and it would up on all customers' repo sites??!! Dec 09, 2008 issue 122 (faxien search enhancement request) commented on by emofine - The describe-app is very nice - I just tried it. Now all you need is a describe-rel :) I am not sure why you would have to make any more HTTP requests than you do now, because when doing a faxien ur (for example), to get the highest version of a release on the repo you have to look through all the versions, right? Unless something has changed; I remember looking through the code when (IIRC) I had the sys.config file overwrite issue and you and I were doing debug logs and I saw all the HTTP requests being made. You did say you wanted to make it more efficient, so have you done that now and that makes it hard(er) to get the data you need for this enhancement? The describe-app is very nice - I just tried it. Now all you need is a describe-rel :) I am not sure why you would have to make any more HTTP requests than you do now, because when doing a faxien ur (for example), to get the highest version of a release on the repo you have to look through all the versions, right? Unless something has changed; I remember looking through the code when (IIRC) I had the sys.config file overwrite issue and you and I were doing debug logs and I saw all the HTTP requests being made. You did say you wanted to make it more efficient, so have you done that now and that makes it hard(er) to get the data you need for this enhancement? Dec 09, 2008 issue 121 (Publish says it fails on HTTP 204 but doesn't) commented on by emofine - Thank you. Much appreciated -- if you have the time. Thank you. Much appreciated -- if you have the time. Dec 09, 2008 issue 122 (faxien search enhancement request) changed by martinjlogan - This is actually something I have wanted to do but find difficult. Basically I would need to make a ton of HTTP requests to do this. When you find a lib you can run faxien describe-app on it to see the app file on the the latest version of an app, releases don't have the same functionality. I will take this into account and think on it. Status: Acknowledged Labels: Type-Enhancement Priority-Low Usability OpSys-All This is actually something I have wanted to do but find difficult. Basically I would need to make a ton of HTTP requests to do this. When you find a lib you can run faxien describe-app on it to see the app file on the the latest version of an app, releases don't have the same functionality. I will take this into account and think on it. Status: Acknowledged Labels: Type-Enhancement Priority-Low Usability OpSys-All Dec 09, 2008 issue 121 (Publish says it fails on HTTP 204 but doesn't) Status changed by martinjlogan - Yes, I can add this error code as a correct code. I was supposed to do that a while back. The change is easy, it is in the ewrepo code I believe. I can do this shortly. Status: Acknowledged Yes, I can add this error code as a correct code. I was supposed to do that a while back. The change is easy, it is in the ewrepo code I believe. I can do this shortly. Status: Acknowledged Dec 09, 2008 issue 122 (faxien search enhancement request) reported by emofine - Faxien search currently only shows the names of the libraries and the releases. The help doesn't seem to show anything that would support extended information. Could you add a verbose option that will show the highest version number in a repository, and the URL of the repository in which it was found? Usage: search [[verbose] [space separated repos] [both\|lib\|releases] [normal\|regexp] search_string] The output should be similar to faxien installed. Example: faxien search verbose mylib Applications (install with: faxien install-app) mylib-1 1.2.5 (http://other.example.com/erlware) mylib-1 1.2.3 (http://example.com/erlware) mylib-2 1.0.1 (http://other.example.com/erlware) mylib-2 1.0.0 (http://example.com/erlware) Releases (install with: faxien install-release) mylib 1.2.5 (http://other.example.com/erlware) mylib 1.2.3 (http://example.com/erlware) ok This would really help to know what was out there and avoid groveling through the repos directly. It also should not be too much of a pain because you already get all that info while you are searching - it's just a question of keeping what you collect and displaying it. I would offer to do this myself but right now I am too busy, and it's not a high priority anyway; it's a nice to have. Faxien search currently only shows the names of the libraries and the releases. The help doesn't seem to show anything that would support extended information. Could you add a verbose option that will show the highest version number in a repository, and the URL of the repository in which it was found? Usage: search [[verbose] [space separated repos] [both\|lib\|releases] [normal\|regexp] search_string] The output should be similar to faxien installed. Example: faxien search verbose mylib Applications (install with: faxien install-app) mylib-1 1.2.5 (http://other.example.com/erlware) mylib-1 1.2.3 (http://example.com/erlware) mylib-2 1.0.1 (http://other.example.com/erlware) mylib-2 1.0.0 (http://example.com/erlware) Releases (install with: faxien install-release) mylib 1.2.5 (http://other.example.com/erlware) mylib 1.2.3 (http://example.com/erlware) ok This would really help to know what was out there and avoid groveling through the repos directly. It also should not be too much of a pain because you already get all that info while you are searching - it's just a question of keeping what you collect and displaying it. I would offer to do this myself but right now I am too busy, and it's not a high priority anyway; it's a nice to have. Dec 09, 2008 issue 121 (Publish says it fails on HTTP 204 but doesn't) commented on by emofine - It appears that this error message happens repeatably (with the one site I use, anyway) if I have published the same release before and needed to overwrite it with an updated release but the same release number. I know you are not supposed to publish a release over the same release, but it happens a lot. Especially when I can't remember if I have published that release already (there seems to be no faxien facility to show the release number of apps in a repository - faxien search doesn't provide that data - I am going to put in an enhancement request.) It appears that this error message happens repeatably (with the one site I use, anyway) if I have published the same release before and needed to overwrite it with an updated release but the same release number. I know you are not supposed to publish a release over the same release, but it happens a lot. Especially when I can't remember if I have published that release already (there seems to be no faxien facility to show the release number of apps in a repository - faxien search doesn't provide that data - I am going to put in an enhancement request.) Oct 26, 2008 issue 119 (Existing sys.config overwritten without asking) commented on by emofine - This was a misunderstanding. I have not re-tested it for multiple config files yet, so it may well work. Sorry. This was a misunderstanding. I have not re-tested it for multiple config files yet, so it may well work. Sorry. Oct 26, 2008 issue 119 (Existing sys.config overwritten without asking) commented on by martinjlogan - Hmm, that sucks, I thought I fixed it for multiple in the latest version... I will have to take a look and do some more testing. Hmm, that sucks, I thought I fixed it for multiple in the latest version... I will have to take a look and do some more testing. Oct 25, 2008 issue 119 (Existing sys.config overwritten without asking) commented on by emofine - This now seems to work. What breaks it is if there is more than one .config file in the config directory. I have removed all files other than sys.config in my app and the diff now gets done nicely. Thank you. This now seems to work. What breaks it is if there is more than one .config file in the config directory. I have removed all files other than sys.config in my app and the diff now gets done nicely. Thank you. Oct 25, 2008 issue 121 (Publish says it fails on HTTP 204 but doesn't) reported by emofine - What steps will reproduce the problem? 1. Find a WebDAV URL that returns a 2xx code other than 200 2. Try to publish something to it. What version of the product are you using? On what operating system? 0.39.0.4 Please provide any additional information below. publish error {publish_failure,"Failed for", [{"http://0.0.0.0/erlware",because {error,{http_return_code,"204"}}}]} After rooting around in the various DAV repos to which I publish, it appears (AFAICS) that the data gets there. This error is very misleading and ulcer-inducing :) I suggest accepting all appropriate 2xx HTTP codes. What steps will reproduce the problem? 1. Find a WebDAV URL that returns a 2xx code other than 200 2. Try to publish something to it. What version of the product are you using? On what operating system? 0.39.0.4 Please provide any additional information below. publish error {publish_failure,"Failed for", [{"http://0.0.0.0/erlware",because {error,{http_return_code,"204"}}}]} After rooting around in the various DAV repos to which I publish, it appears (AFAICS) that the data gets there. This error is very misleading and ulcer-inducing :) I suggest accepting all appropriate 2xx HTTP codes. Oct 22, 2008 issue 120 (bootstrap-builder fails on solaris) reported by twoggle - Running "./create_bootstrap.sh" produces: ./create_bootstrap.sh: syntax error at line 37: `ERTS_VSN=$' unexpected According to faxien-launcher-universal-0.3.4.py I'm on i86pc-SunOS-5.11. Running "./create_bootstrap.sh" produces: ./create_bootstrap.sh: syntax error at line 37: `ERTS_VSN=$' unexpected According to faxien-launcher-universal-0.3.4.py I'm on i86pc-SunOS-5.11. Sep 20, 2008 issue 119 (Existing sys.config overwritten without asking) commented on by emofine - I sent you the error log file in a private email. I sent you the error log file in a private email. Sep 19, 2008 issue 119 (Existing sys.config overwritten without asking) Status changed by martinjlogan - perplexing, ok, can you send me the error log file? Status: Started perplexing, ok, can you send me the error log file? Status: Started Sep 19, 2008 issue 119 (Existing sys.config overwritten without asking) commented on by emofine - No, I just rechecked by making a significant change to the actual data in the sys.config and it still did not migrate it. Maybe it does not work if you first do a remove-release and then an install-release. I'll try with portius but not tonight. No, I just rechecked by making a significant change to the actual data in the sys.config and it still did not migrate it. Maybe it does not work if you first do a remove-release and then an install-release. I'll try with portius but not tonight.

issue 124 (Crypto module (crypto-1.5.2) is broken) reported by justin.venus - What steps will reproduce the problem? 1. ${PATH_TO_ERLWARE}/erlware/bin/erl 2. crypto:start() 3. fail What is the expected output? What do you see instead? On Fedora 10 x86-64 crypto:start() reports Eshell V5.6.3 (abort with ^G) 1> crypto:start(). {error,{shutdown,{crypto_app,start,[normal,[]]}}} =INFO REPORT==== 28-Mar-2009::13:01:04 === application: crypto exited: {shutdown,{crypto_app,start,[normal,[]]}} type: temporary 2> sh: line 0: exec: crypto_drv: not found On OSX 10.5 crypto starts but is missing alot of the documented functions. http://erlang.org/doc/man/crypto.html What version of the product are you using? On what operating system? R12b3 OSX 10.5 and Fedora10 x86-64 Please provide any additional information below. If erlang is build with the following modifications everything works as it should. It is also part of the specfile for erlang from Fedora 9. cd $OTP_SRC_DIR # enable dynamic linking for ssl # sorry this is messy, but portable to all POSIX systems sed 's|SSL_DYNAMIC_ONLY=no|SSL_DYNAMIC_ONLY=yes|' erts/configure > zzz mv zzz erts/configure sed 's|^LD.*=.*|LD = gcc -shared|' lib/common_test/c_src/Makefile > zzz mv zzz lib/common_test/c_src/Makefile CFLAGS="-fno-strict-aliasing" ./configure \ --enable-threads \ --enable-kernel-poll \ --prefix=%{_prefix} \ --exec-prefix=/usr \ --bindir=/usr/bin \ --libdir=/usr/lib \ --disable-sctp \ --enable-dynamic-ssl-lib \ --enable-hipe make make INSTALL_PREFIX=/tmp/erlang install #clean up garbage find /tmp/erlang/usr/lib/erlang -perm 0775 | xargs chmod 755 find /tmp/erlang/usr/lib/erlang -name Makefile | xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \*.o | xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \*.bat | xargs rm -f find /tmp/erlang/usr/lib/erlang -name index.txt.old | xargs rm -f #sorry this is messy, but it is portable to all POSIX systems cd /tmp/erlang/usr/lib/erlang cd erts* sed "s|/tmp/erlang||" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s|/tmp/erlang||" bin/start > zzz mv zzz bin/start chmod 755 bin/start cd .. sed "s|/tmp/erlang||" releases/RELEASES >zzz mv zzz releases/RELEASES sed "s|/tmp/erlang||" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s|/tmp/erlang||" bin/start > zzz mv zzz bin/start chmod 755 bin/start

What steps will reproduce the problem? 1. ${PATH_TO_ERLWARE}/erlware/bin/erl 2. crypto:start() 3. fail What is the expected output? What do you see instead? On Fedora 10 x86-64 crypto:start() reports Eshell V5.6.3 (abort with ^G) 1> crypto:start(). {error,{shutdown,{crypto_app,start,[normal,[]]}}} =INFO REPORT==== 28-Mar-2009::13:01:04 === application: crypto exited: {shutdown,{crypto_app,start,[normal,[]]}} type: temporary 2> sh: line 0: exec: crypto_drv: not found On OSX 10.5 crypto starts but is missing alot of the documented functions. http://erlang.org/doc/man/crypto.html What version of the product are you using? On what operating system? R12b3 OSX 10.5 and Fedora10 x86-64 Please provide any additional information below. If erlang is build with the following modifications everything works as it should. It is also part of the specfile for erlang from Fedora 9. cd $OTP_SRC_DIR # enable dynamic linking for ssl # sorry this is messy, but portable to all POSIX systems sed 's|SSL_DYNAMIC_ONLY=no|SSL_DYNAMIC_ONLY=yes|' erts/configure > zzz mv zzz erts/configure sed 's|^LD.*=.*|LD = gcc -shared|' lib/common_test/c_src/Makefile > zzz mv zzz lib/common_test/c_src/Makefile CFLAGS="-fno-strict-aliasing" ./configure \ --enable-threads \ --enable-kernel-poll \ --prefix=%{_prefix} \ --exec-prefix=/usr \ --bindir=/usr/bin \ --libdir=/usr/lib \ --disable-sctp \ --enable-dynamic-ssl-lib \ --enable-hipe make make INSTALL_PREFIX=/tmp/erlang install #clean up garbage find /tmp/erlang/usr/lib/erlang -perm 0775 | xargs chmod 755 find /tmp/erlang/usr/lib/erlang -name Makefile | xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \*.o | xargs chmod 644 find /tmp/erlang/usr/lib/erlang -name \*.bat | xargs rm -f find /tmp/erlang/usr/lib/erlang -name index.txt.old | xargs rm -f #sorry this is messy, but it is portable to all POSIX systems cd /tmp/erlang/usr/lib/erlang cd erts* sed "s|/tmp/erlang||" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s|/tmp/erlang||" bin/start > zzz mv zzz bin/start chmod 755 bin/start cd .. sed "s|/tmp/erlang||" releases/RELEASES >zzz mv zzz releases/RELEASES sed "s|/tmp/erlang||" bin/erl > zzz mv zzz bin/erl chmod 755 bin/erl sed "s|/tmp/erlang||" bin/start > zzz mv zzz bin/start chmod 755 bin/start

Yesterday

Older