While browsing LTSpice's directory structure, I discovered LTSpice's
executable is a 64 bit Windows executable. Knowing, wine64 could be
installed and run without issues on ASCII, I copied the entire
directory tree to a disk and copied it to Devuan where wine64 expects
Windows programs to be
On Sun, 19 Aug 2018 13:23:42 +1000
terryc wrote:
> In my experience with "linux"(25 years), if it doesn't work, you can
> either fix it yourself(good luck)
If the "good luck" above is intended to mean you're unlikely to fix it
yourself, I disagree, assuming you use my definition of "fix".
On Sat, 18 Aug 2018 14:12:54 +0200
Edward Bartolo wrote:
> Maybe, apt-cache depends can shed some light. It seems wine32 depends
> on libwine:i386 and the latter breaks wine32.
There is a fix-missing on one of apt/apt-get/aptitude/? , I forget
which. It MAY fix stuff, but it could just break
I installed ascii/wine this week on two machines, using:
apt-get -t ascii-backports install wine wine32 fonts-wine
I've got both 32 and 64 bit wine executables, though I don't think I
actually have any 64 bit windows software to test with.
Maybe you'd do better to install from backports?
On 18-08-18 14:12, Edward Bartolo wrote:
> Maybe, apt-cache depends can shed some light. It seems wine32 depends
> on libwine:i386 and the latter breaks wine32.
>
> Here is the output:
>
> $ apt-cache depends libwine:i386
> libwine:i386
> Depends: libc6:i386
> Depends: libfontconfig1:i386
>
Maybe, apt-cache depends can shed some light. It seems wine32 depends
on libwine:i386 and the latter breaks wine32.
Here is the output:
$ apt-cache depends libwine:i386
libwine:i386
Depends: libc6:i386
Depends: libfontconfig1:i386
Depends: libfreetype6:i386
Depends: libncurses5:i386
On 18-08-18 11:44, Edward Bartolo wrote:
> Jaromil wrote:
> -
>> 1. dpkg --print-architechture
>> 2. dpkg --print-foreign-architectures
>> 3. list of enabled repositories (+ architechture)
>> 4. dpkg -l | grep wine
> I'm sorry to see that Ed moved on to RANT instead of providing
dear Ed,
On Sat, 18 Aug 2018, Edward Bartolo wrote:
> Jaromil wrote:
> -
> > 1. dpkg --print-architechture
> > 2. dpkg --print-foreign-architectures
> > 3. list of enabled repositories (+ architechture)
> > 4. dpkg -l | grep wine
> I provided that information already. I do not
Jaromil wrote:
-
> 1. dpkg --print-architechture
> 2. dpkg --print-foreign-architectures
> 3. list of enabled repositories (+ architechture)
> 4. dpkg -l | grep wine
I'm sorry to see that Ed moved on to RANT instead of providing basic
information to those of use who were patiently
On Fri, 17 Aug 2018, Evilham wrote:
>
> Snippet from a previous email after fixing command typos, can you post
> all this?
>
> 1. dpkg --print-architechture
> 2. dpkg --print-foreign-architectures
> 3. list of enabled repositories (+ architechture)
> 4. dpkg -l | grep wine
I'm sorry to see that
On 17/08/2018, Evilham wrote:
[...]
>
> Snippet from a previous email after fixing command typos, can you post
> all this?
>
> 1. dpkg --print-architechture
> 2. dpkg --print-foreign-architectures
> 3. list of enabled repositories (+ architechture)
> 4. dpkg -l | grep wine
>
This is the output.
Am 17.08.2018 um 10:27 schrieb Edward Bartolo:
> On 13/08/2018, KatolaZ wrote:
> [...]
>>
>> Random guess: which repo are you using? If you are still using
>> packages.devuan.org or *.mirror.devuan.org, then you should switch to
>> deb.devuan.org, since we know of existing glitches with ascii in
On 13/08/2018, KatolaZ wrote:
[...]
>
> Random guess: which repo are you using? If you are still using
> packages.devuan.org or *.mirror.devuan.org, then you should switch to
> deb.devuan.org, since we know of existing glitches with ascii in the
> original amprolla.
>
I carefully edited my
On Mon, Aug 13, 2018 at 06:42:07PM +0200, Evilham wrote:
> Am 13.08.2018 um 18:39 schrieb Edward Bartolo:
> > On 13/08/2018, info at smallinnovations dot nl
> > wrote:
> > [...]
> >>
> >> I suspect your system is not multiarch atm. You can add i386 with the
> >> command
> >>
> >> dpkg
Am 13.08.2018 um 18:39 schrieb Edward Bartolo:
> On 13/08/2018, info at smallinnovations dot nl
> wrote:
> [...]
>>
>> I suspect your system is not multiarch atm. You can add i386 with the
>> command
>>
>> dpkg --add-architecture i386
>>
>
> I have already added the i386 architecture. This is
Am 13.08.2018 um 15:58 schrieb Edward Bartolo:
> You write like someone wanting to hit me. Well, I am on Blessed Devuan
> ASCII and my system is refusing to install wine32 because of missing
> libraries it cannot resolve. So, it is Devuan at blame.
Sorry if you read that, I just hoped instead of
On 13/08/2018, info at smallinnovations dot nl wrote:
[...]
>
> I suspect your system is not multiarch atm. You can add i386 with the
> command
>
> dpkg --add-architecture i386
>
I have already added the i386 architecture. This is what dpkg tells me:
dpkg --print-foreign-architectures
i386
On 13-08-18 15:58, Edward Bartolo wrote:
> On 13/08/2018, Evilham wrote:
> 08.2018 um 14:30 schrieb Edward Bartolo:
>>> apt-get laments:
> [...]
>>> Can I continue using Devuan ASCII and have wine32?
>> None of that is Devuan-specific. Have you read this?
>>
>> https://wiki.debian.org/Wine
>> --
On 13/08/2018, Evilham wrote:
08.2018 um 14:30 schrieb Edward Bartolo:
>> apt-get laments:
[...]
>> Can I continue using Devuan ASCII and have wine32?
>
> None of that is Devuan-specific. Have you read this?
>
> https://wiki.debian.org/Wine
> --
> Evilham
>
OK, so I RTFM irrespective of knowing
Am 13.08.2018 um 14:30 schrieb Edward Bartolo:
> apt-get laments:
>
> # apt-get install wine32
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or
apt-get laments:
# apt-get install wine32
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required
21 matches
Mail list logo
