lubuntu-qa team mailing list archive

[Jonathan Marsden <jmarsden@xxxxxxxxxxx>]

On 07/25/2013 08:05 AM, Phill Whiteside wrote:

> it is to ensure there are no 64 bit  instructions in the 32 bit version.
> To err is human, to mess things up completely requires a computer :)
> 
> Whilst this may seem like over kill, it is a 100% sure fire way to
> ensure that should the unthinkable happen, it is not missed.

So, in the multi-year history of Ubuntu, has this issue ever happened?
Can you point to a single LaunchPad bug of this kind?

I think the chances are so low that it is not worth worrying about.  By
all means do a quick check, such as:

  file $(echo $PATH|sed -e 's%:%/* %g') | grep 64-bit

or similar, to check for 64bit binaries on an installed image... this
can be done on any 32bit installation, including one installed and
running on a 64-bit capable CPU, virtual or physical.

But let's not discourage use of 64-bit capable hardware, or VMs on
64-bit capable hardware, for testing ISOs.

Jonathan