Martin, It is in canonical, but publishing seems weird.
Is there a reason the ewlib app would be published to 5.8.1, but the erlware release would publish to 5.8.2? My preferred erts vsn is set to 5.8.2 Log: diginux@heisenberg:~/code/erlware$ faxien publish Faxien is currently set to publish to: ["http://repo.erlware.org/writable";] Do you want to publish the app: /home/diginux/code/erlware/_build/development/apps/gas-8.0.2 Enter (y)es, (n)o, or yes to (a)ll? > ? n Do you want to publish the app: /home/diginux/code/erlware/_build/development/apps/fslib-5.5.2 Enter (y)es, (n)o, or yes to (a)ll? > ? n Do you want to publish the app: /home/diginux/code/erlware/_build/development/apps/ewrepo-0.20.0.0 Enter (y)es, (n)o, or yes to (a)ll? > ? n Do you want to publish the app: /home/diginux/code/erlware/_build/development/apps/ewlib-0.9.7.2 Enter (y)es, (n)o, or yes to (a)ll? > ? y Publishing "/home/diginux/code/erlware/_build/development/apps/ewlib-0.9.7.2" package Publishing generic package Creating ewlib.tar.gz from ewlib-0.9.7.2 a ewlib-0.9.7.2/ebin/ewl_string_manip.beam a ewlib-0.9.7.2/ebin/ewl_config_diff.beam a ewlib-0.9.7.2/ebin/ewl_file.beam a ewlib-0.9.7.2/ebin/ewl_get_opt.beam a ewlib-0.9.7.2/ebin/ewlib.app a ewlib-0.9.7.2/ebin/ewl_package_paths.beam a ewlib-0.9.7.2/ebin/ewl_talk.beam a ewlib-0.9.7.2/ebin/ewl_elwrap_h.beam a ewlib-0.9.7.2/ebin/ewl_sinan_paths.beam a ewlib-0.9.7.2/ebin/ewl_installed_paths.beam a ewlib-0.9.7.2/ebin/ewl_plists.beam a ewlib-0.9.7.2/src/ewl_talk.erl a ewlib-0.9.7.2/src/ewl_string_manip.erl a ewlib-0.9.7.2/src/ewl_file.erl a ewlib-0.9.7.2/src/ewl_package_paths.erl a ewlib-0.9.7.2/src/ewl_elwrap_h.erl a ewlib-0.9.7.2/src/ewl_config_diff.erl a ewlib-0.9.7.2/src/ewl_plists.erl a ewlib-0.9.7.2/src/ewl_installed_paths.erl a ewlib-0.9.7.2/src/ewl_sinan_paths.erl a ewlib-0.9.7.2/src/ewl_get_opt.erl Publishing to [" http://repo.erlware.org/writable/5.8.1/Meta/ewlib/0.9.7.2/checksum";] Do you want to publish the release: /home/diginux/code/erlware/_build/development/tar/erlware-0.5.1.1.tar.gz Enter (y)es, (n)o, or yes to (a)ll? > ? y Publishing "/home/diginux/code/erlware/_build/development/tar/erlware-0.5.1.1.tar.gz" package Publishing release package It appears the package does not contain a valid control file. Lets create a basic one. Enter the package owners full name > ? Martin Logan Enter a contact email address > ? [email protected] Enter from the list below. Separate multiple categories with commas: web, tool, test, server, net, misc, math, graphic, game, driver, database, > ? tool Enter a short description of the package > ? Misc erlware tools Would you like to specify additional control information? [yes|no] > ? no {control,"erlware", [{package_owner,"Martin Logan"}, {package_owner_email,"[email protected]"}, {categories,["tool"]}, {description,"Misc erlware tools"}]}. Above is the control information collected about this package. This information will be placed under the root directory of the package in a file named "control". **If done manually for the next publish be sure to include the period after the term** Creating erlware.tar.gz from erlware-0.5.1.1 a erlware-0.5.1.1/releases/erlware-0.5.1.1/erlware.script a erlware-0.5.1.1/releases/erlware-0.5.1.1/sys.config a erlware-0.5.1.1/releases/erlware-0.5.1.1/erlware.rel a erlware-0.5.1.1/releases/erlware-0.5.1.1/erlware.boot a erlware-0.5.1.1/control a erlware-0.5.1.1/bin/resource_discovery Publishing to [" http://repo.erlware.org/writable/5.8.2/Generic/releases/erlware/0.5.1.1/erlware.tar.gz "] On Tue, Jan 18, 2011 at 7:51 AM, Jordan Wilberding <[email protected]>wrote: > Reviewing. > > On Mon, Jan 17, 2011 at 11:54 PM, GitHub <[email protected]> wrote: > >> ericbmerritt wants someone to pull from ericbmerritt:master: >> >> adds related unit tests. >> >> they should have been there to begin with. >> >> View Pull Request: https://github.com/erlware/erlware/pull/9 >> > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
