[Shipwright] Shipwright Builder errors

[sunnavy]

Hi Sam

I'm very happy to see you resolved it by yourself!
I'm super busy in the last few days, sorry about it.

Regards
sunnavy

> On Dec 16, 2014, at 3:53 AM, Wenck, Samuel <samuel.wenck at lmco.com> wrote:
> 
> I have resolved my issue by replacing the relative path for the shipwright-builder command with a full path:
>  
> ./bin/shipwright-builder --verbose  --flags mysql --install-base  /opt/rt_build/rt${RT_VERSION}_vessel/shipwright/vessel
>  
> - Sam
>  
> From: Shipwright [mailto:shipwright-bounces at lists.bestpractical.com] On Behalf Of Wenck, Samuel
> Sent: Monday, December 15, 2014 2:09 PM
> To: shipwright at lists.bestpractical.com
> Subject: EXTERNAL: Re: [Shipwright] Shipwright Builder errors
>  
> I have reverted back to the version of Perl bundled with CentOS 6.5 (Perl 5.10.1) and I am still getting these errors when running the shipwright builder command:
>  
> [wencks at samdev65 shipwright]$ ./shipbuild.rt4.2.9
> + RT_VERSION=4.2.9
> + rm -Rf /opt/rt_build/rt4.2.9_vessel/shipwright/vessel
> + mkdir /opt/rt_build/rt4.2.9_vessel/shipwright/vessel
> + cd /opt/rt_build/rt4.2.9_vessel/shipwright/yard
> + ./bin/shipwright-builder --verbose --flags mysql --install-base ../vessel
> building RT
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for perl... /usr/bin/perl
> checking for chosen layout... inplace
> checking if group rt3 exists... not found
> checking if group rt exists... not found
> checking if group apache exists... found
> checking if database name is set... yes
> checking if database name is valid... yes
> checking for dot... no
> checking for gdlib-config... no
> checking for gpg... yes
> checking for openssl... yes
> configure: creating ./config.status
> config.status: creating etc/upgrade/3.8-ical-extension
> config.status: creating etc/upgrade/4.0-customfield-checkbox-extension
> config.status: creating etc/upgrade/split-out-cf-categories
> config.status: creating etc/upgrade/generate-rtaddressregexp
> config.status: creating etc/upgrade/upgrade-articles
> config.status: creating etc/upgrade/vulnerable-passwords
> config.status: creating etc/upgrade/switch-templates-to
> config.status: creating sbin/rt-attributes-viewer
> config.status: creating sbin/rt-preferences-viewer
> config.status: creating sbin/rt-session-viewer
> config.status: creating sbin/rt-dump-metadata
> config.status: creating sbin/rt-setup-database
> config.status: creating sbin/rt-test-dependencies
> config.status: creating sbin/rt-email-digest
> config.status: creating sbin/rt-email-dashboards
> config.status: creating sbin/rt-clean-sessions
> config.status: creating sbin/rt-shredder
> config.status: creating sbin/rt-validator
> config.status: creating sbin/rt-validate-aliases
> config.status: creating sbin/rt-email-group-admin
> config.status: creating sbin/rt-server
> config.status: creating sbin/rt-server.fcgi
> config.status: creating sbin/standalone_httpd
> config.status: creating sbin/rt-setup-fulltext-index
> config.status: creating sbin/rt-fulltext-indexer
> config.status: creating sbin/rt-serializer
> config.status: creating sbin/rt-importer
> config.status: creating bin/rt-crontool
> config.status: creating bin/rt-mailgate
> config.status: creating bin/rt
> config.status: creating Makefile
> config.status: creating etc/RT_Config.pm
> config.status: creating lib/RT/Generated.pm
> config.status: creating t/data/configs/apache2.2+mod_perl.conf
> config.status: creating t/data/configs/apache2.2+fastcgi.conf
> ================================================================================
> binmode() on closed filehandle $fh at inc/YAML/Tiny.pm line 579.
> flock() on closed filehandle $fh at inc/YAML/Tiny.pm line 581.
> Couldn't lock '../vessel/Linux_installed.yml' for reading: Bad file descriptor at inc/YAML/Tiny.pm line 581.
> seek() on closed filehandle $fh at inc/YAML/Tiny.pm line 586.
> print() on closed filehandle $fh at inc/YAML/Tiny.pm line 593.
> Failed to close file '../vessel/Linux_installed.yml': Bad file descriptor at ./bin/shipwright-builder line 933
>  
> The vessel seems to be creatd after these errors but I am concerned that my vessel will have issues in the future.
>  
> Thanks in advance, Sam
>  
> From: Shipwright [mailto:shipwright-bounces at lists.bestpractical.com] On Behalf Of Wenck, Samuel
> Sent: Monday, December 08, 2014 4:57 PM
> To: shipwright at lists.bestpractical.com
> Subject: EXTERNAL: [Shipwright] Shipwright Builder errors
>  
> Hello,
>  
> I am using the new version Shipwright (2.4.40) on CentOS 6.5 with a GIT repository as my back end store. I am using the following commands to export the repository:
>  
> RT_VERSION="4.2.9"
> export SHIP_BASE="/opt/rt_build/rt${RT_VERSION}_vessel/shipwright/"
> export REPO=/opt/rt_build/rt${RT_VERSION}_vessel/shipwright/repo/rt${RT_VERSION}.git
> cd $REPO
> git archive --format=tar --prefix=yard/ HEAD | (cd $SHIP_BASE && tar xf -)
>  
> This creates a shipwright area at /opt/rt_build/rt4.2.9_vessel/shipwright/yard  with no issues. However, when I attempt to issue the shipwright builder command I get the following errors:
>  
> + RT_VERSION=4.2.9
> + rm -Rf /opt/rt_build/rt4.2.9_vessel/shipwright/vessel
> + mkdir /opt/rt_build/rt4.2.9_vessel/shipwright/vessel
> + cd /opt/rt_build/rt4.2.9_vessel/shipwright/yard
> + ./bin/shipwright-builder --verbose --flags mysql --install-base ../vessel
> Unknown PerlIO layer "encoding" at inc/YAML/Tiny.pm line 184.
> flock() on closed filehandle $fh at inc/YAML/Tiny.pm line 191.
> Couldn't lock 'shipwright/order.yml' for reading: Bad file descriptor at inc/YAML/Tiny.pm line 191.
> readline() on closed filehandle $fh at inc/YAML/Tiny.pm line 199.
>  
> I would appreciate any help or direction on this issue, thanks in advance, Sam
>  
> _______________________________________________
> Shipwright mailing list
> Shipwright at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/shipwright