Skip Menu |
 
rt.cpan.org will be shut down on March 1st, 2021.

This queue is for tickets about the MySQL-Sandbox CPAN distribution.

Report information
The Basics
Id: 59879
Status: open
Priority: 0/
Queue: MySQL-Sandbox

People
Owner: Nobody in particular
Requestors: cosimo [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 3.0.12
Fixed in: (no value)



Subject: make_sandbox_from_installed script fails due to duplicate lib/lib64 links
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 1555
Download (untitled) / with headers
text/plain 1.5k
Hello Giuseppe, We're using MySQL::Sandbox to create mysql instances for functional test runs. It's working great, using 'make_sandbox_from_installed' to set up a new mysql sandbox from the installed system mysql. Apparently, the script fails in systems where /usr/lib64 is symlinked to /usr/lib, causing it to try to create a $sandbox_root/lib link twice, one for 'lib64' and one for 'lib'. For now we're overwriting the script with a patched version, but that's messy and less than awesome. I'm not sure what the appropriate fix is, but these two strategies work: 1) Comment out the 'lib64' line from @binaries, line 64. 2) Apply the following diff: --- make_sandbox_from_installed.3.0.12 2010-07-30 16:18:32.000000000 +0200 +++ make_sandbox_from_installed.cosimo 2010-07-30 16:19:39.000000000 +0200 @@ -61,7 +61,7 @@ {files => 'my*', from => 'bin/', to => 'bin'}, {files => 'resolveip', from => 'bin/', to => 'bin'}, {files => 'mysql_install_db', from => 'scripts/', to => 'bin', optional => 1}, - {files => 'mysql*', from => 'lib64/', to => 'lib', optional => 1}, + {files => 'mysql*', from => 'lib64/', to => 'lib64', optional => 1}, {files => 'mysql*', from => 'lib/', to => 'lib', optional => 1}, {files => 'mysql*', from => 'libexec/', to => 'bin', optional =>1}, {files => 'mysql*', from => 'sbin/', to => 'bin', optional =>1}, Please let me know if you can do something about this.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-20566-1315314083-1068.59879-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 20
Any updates on this?
MIME-Version: 1.0
In-Reply-To: <rt-3.8.HEAD-20566-1315314083-1068.59879-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
References: <rt-3.8.HEAD-20566-1315314083-1068.59879-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-19815-1341243386-1945.59879-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
From: icestar [...] inbox.ru
X-RT-Original-Encoding: utf-8
Content-Length: 36
I've faced exactly the same problem.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.