On 3/8/23 13:23, Hans Unzner wrote:
PS: In the README.md, I guess there is a linebreak intended between
`docker pull debian:bookworm` and ` docker build ...`. It's displayed on
GitHub in one line...
Thanks, fixed.
--
Sebastian Kuzminsky
___
Am 08.03.23 um 21:10 schrieb Sebastian Kuzminsky:
On 3/8/23 12:21, Hans Unzner wrote:
Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky:
On 1/4/23 05:09, Hans Unzner wrote:
However, I have some annotations:
- You could mention that the tests need to be run as sudo (at least
for it only
On 3/8/23 12:21, Hans Unzner wrote:
Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky:
On 1/4/23 05:09, Hans Unzner wrote:
However, I have some annotations:
- You could mention that the tests need to be run as sudo (at least
for it only worked so) and need Python >= 3.8
Hmm, I run them as a
Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky:
On 1/4/23 05:09, Hans Unzner wrote:
However, I have some annotations:
- You could mention that the tests need to be run as sudo (at least
for it only worked so) and need Python >= 3.8
Hmm, I run them as a regular user. Maybe you just
To be talking about support on Bullseye when it's at the end of its useful
life before Linuxcnc has any public method to install on that platform
other than from compiling the source belies belief.
Yes I know there is now a buildbot for it, but existence seems to be a
closely guarded secret no
Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky:
On 1/4/23 05:09, Hans Unzner wrote:
However, I have some annotations:
- You could mention that the tests need to be run as sudo (at least
for it only worked so) and need Python >= 3.8
Hmm, I run them as a regular user. Maybe you just
On 1/4/23 05:09, Hans Unzner wrote:
However, I have some annotations:
- You could mention that the tests need to be run as sudo (at least for
it only worked so) and need Python >= 3.8
Hmm, I run them as a regular user. Maybe you just installed docker.io,
and you have to log out and log back
t;Rod Webster"
An: "EMC developers"
Betreff: Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy,
qtvcp, and more!
It has to be tested on Bookworm because once it becomes the Debian release
version in a few short months, Linuxcnc is deployed with it. Bullseye does
n
gt; Betreff: Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy,
> qtvcp, and more!
>
> It has to be tested on Bookworm because once it becomes the Debian release
> version in a few short months, Linuxcnc is deployed with it. Bullseye does
> not have the linuxcnc-us
It has to be tested on Bookworm because once it becomes the Debian release
version in a few short months, Linuxcnc is deployed with it. Bullseye does
not have the linuxcnc-uspace package the tests use.
I must say it's great to see some testing on Bullseye. So much of the GUI's
are broken. Hats
Really great, thank you!
However, I have some annotations:
- You could mention that the tests need to be run as sudo (at least for
it only worked so) and need Python >= 3.8
- The stderr file only shows something like "+ su --pty -c 'linuxcnc
11 matches
Mail list logo
