geomacy commented on issue #150: BROOKLYN-597 Remove md5/sha1 - DO NOT MERGE URL: https://github.com/apache/brooklyn-dist/pull/150#issuecomment-566806880 Well unfortunately I still don't have this going. I caught up to latest masters and added the `rpm` and `deb` flags to the build; this time I didn't get the error in the ui utils directory any more, I guess that is due to your brooklyn-ui#158 @tbouron. But after churning away for over an hour building everything I got to the CLI artifacts stage, which failed as you see: ``` Make CLI artifacts + mkdir /var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T//release-working-dir/bin//apache-brooklyn-1.0.0-SNAPSHOT-client-cli-linux + mkdir /var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T//release-working-dir/bin//apache-brooklyn-1.0.0-SNAPSHOT-client-cli-windows + mkdir /var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T//release-working-dir/bin//apache-brooklyn-1.0.0-SNAPSHOT-client-cli-macosx + cp /var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T//release-working-dir/source/apache-brooklyn-1.0.0-SNAPSHOT-src/brooklyn-client/cli/target/bin/linux.386/br /var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T//release-working-dir/bin//apache-brooklyn-1.0.0-SNAPSHOT-client-cli-linux cp: /var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T//release-working-dir/source/apache-brooklyn-1.0.0-SNAPSHOT-src/brooklyn-client/cli/target/bin/linux.386/br: No such file or directory ``` My build command was `./brooklyn-dist/release/make-release-artifacts.sh -r1 -n` issued from the Brooklyn root dir. I don't know what's up here and it's a bit late to start investigating that - I have pushed the addition flags commit. I "tested" the signing changes by running just that chunk of the script, and it succeeds to the extent that it signs the artifacts that it finds in the directory as it should, but in my case it fails because there is no .rpm file in the directory - due to the real build failing as above. @tbouron I'm fairly confident in the correctness of the changes but can't demonstrate them yet. Also I won't be able to get to look at this stuff again at least until Thursday. Happy to do that but if you want to do anything with it yourself and/or merge it on the basis of your own tests, feel free. I've invited you as a collaborator on my repo so you can update my branch if you like.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
