Re: [lmi] Creating a chroot for cross-building lmi

[Greg Chicares]

On 2016-09-26 01:35, Greg Chicares wrote:

[...ran same commands that had worked before to create a new chroot, then...]

> schroot --chroot=xlmi --user=root --directory=/
> address@hidden:/# dpkg --add-architecture i386
> address@hidden:/# cat >/usr/sbin/policy-rc.d <<EOF
>> #!/bin/sh
>> exit 101
>> EOF
> address@hidden:/# chmod a+x /usr/sbin/policy-rc.d
> address@hidden:/# dpkg-divert --divert /usr/bin/ischroot.debianutils --rename 
> /usr/bin/ischroot
> Adding 'local diversion of /usr/bin/ischroot to /usr/bin/ischroot.debianutils'
> address@hidden:/# ln -s /bin/true /usr/bin/ischroot
> address@hidden:/# mount -t devpts devpts /dev/pts
> address@hidden:/# mount -t proc proc /proc
> address@hidden:/# apt-get [...]

Now, after entering the new chroot as a normal user, 'wine' no longer works
immediately as it did before--but ultimately that's fixed below.

$winecfg
cat: /home/greg/.wine/system.reg: No such file or directory
/usr/bin/winecfg: 32: exec: winecfg.exe: not found

There isn't even a '.wine' subdirectory (they call this a
"wine prefix"):

/home/greg[127]$ls -a
.   .bash_logout  .gitconfig  .profile    .zshrc
..  .bashrc       .history    .zcompdump  ltmain.sh.patch

Trying a different wine program--same symptoms:

/home/greg[0]$regedit
cat: /home/greg/.wine/system.reg: No such file or directory
/usr/bin/regedit: 32: exec: regedit.exe: not found

/home/greg[0]$which wine
/usr/bin/wine
/home/greg[0]$file $(which wine)
/usr/bin/wine: POSIX shell script, ASCII text executable
/home/greg[0]$echo $path
/opt/lmi/local/bin /opt/lmi/local/lib /usr/local/bin /usr/bin /bin
/home/greg[0]$which winecfg
/usr/bin/winecfg

Looks like wine was installed but some initialization step was missed,
perhaps due to '/usr/sbin/policy-rc.d'? Or perhaps 'jessie' now provides
a newer version of wine than I had previously installed in other chroots.
Or maybe in other chroots I did "something" that created a proper wine
prefix--this is why it takes so much effort to come up with a reproducible
process for creating a chroot.

Random flailing...

$wine control
wine: created the configuration directory '/home/greg/.wine'
wine: configuration in '/home/greg/.wine' has been updated.

...seems to solve the problem. Now 'winecfg' works. Perhaps
  wineboot --init
would work as well while feeling less like a kludge.

For reference, this idea:

https://wiki.archlinux.org/index.php/wine#WINEPREFIX
| ~/.wine ... is created/updated automatically whenever you run a
| Windows program or one of Wine's bundled programs such as winecfg.

specifically did not work.