On 04/09/17 16:46,
schoone...@btinternet.com wrote:
On 04/09/17 16:38, 'machinen' via
Machinekit wrote:
Oh, thanks.
I think that the 14-something serial is from the February
image, tryin
On 04/09/17 16:38, 'machinen' via
Machinekit wrote:
Oh, thanks.
I think that the 14-something serial is from the February image,
trying on newer I have gotten something like:
Depends:
machin
Oh, thanks.
I think that the 14-something serial is from the February image, trying on
newer I have gotten something like:
Depends: machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~
1jessie) but 0.1.1504208693-1mk.travis.pr1265.git00ce6961~1jessie is to be
installed
On Mond
OK I have found the problem.
You were unlucky, because it does not affect every flavour and OS
A problem whereby a PR submission got pushed into the repo before
merge, has screwed some of the packages files.
The package serials for machinekit-xenomai and machinekit
>
> why do you run machinekit with that configuration as well as the run.py
> script?
>
I probably expressed myself wrong. What I did mean is that I ran machinekit
command, from the example configuration command selected Fabrikator Mini
CRAMPS (so I used the config files which came with machi
I actually looked at the repository and source list as first thing, but I
didn't see anything odd. I am for this endeavour using the "latest"
official machinekit image
bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz from
elinux.org/Beagleboard:BeagleBoneBlack_Debian which is from februa
> On 04 Sep 2017, at 14:38, 'machinen' via Machinekit
> wrote:
>
> Somehow I didn't have the fdm folder on my system - probably from mucking
> around. However I did a new flash of clean
> bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and sure there
> it is. Unfortunately when
Look at http://deb.machinekit.io/debian/pool/main/m/machinekit/
There is no package 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
that serial is
ancient.
You need to check your /etc/apt/sources.list and the files in
/etc/apt/sources.list.d and
Somehow I didn't have the fdm folder on my system - probably from mucking
around. However I did a new flash of clean
bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and sure there
it is. Unfortunately when the first thing when I log into this new install
I do is run machinekit and
On 04/09/17 09:02,
schoone...@btinternet.com wrote:
On 03/09/17 23:37, 'machinen' via
Machinekit wrote:
The dist-aupgrade removes machinekit packages
from system. There is this problem:
On 03/09/17 23:37, 'machinen' via
Machinekit wrote:
The dist-aupgrade removes machinekit packages from
system. There is this problem:
The following packages
have unmet dependencies:
machinekit-xenoma
The dist-aupgrade removes machinekit packages from system. There is this
problem:
The following packages have unmet dependencies:
machinekit-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis.
luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.
gitcbd2dfd3~1jessie is
you could try sudo apt-get dist-upgrade for held back packages...
On Tuesday, August 29, 2017 at 2:08:30 AM UTC-4, Pranav Pandey wrote:
>
> Hi Folks,
>
> This is my first post on this group. I am working on integrating 3d
> printing and CNC Milling in a single machine. I have worked with Arduino
I have run this in the past with no issues.
My current testing machine is targeting the BBGW though, so it's using
rt-preempt (so wireless works) and the BeBoPr config instead (as CRAMPS
shares pins with the wifi/bluetooth module)
So I can't directly assist you atm.
On Sunday, September 3, 201
Hi,
I am in somewhat similar situation to yours and I have few questions for
you:
Were you able to upgrade your installation? Because the ready-made image
for BBB is quite old and when doing update/upgrade, the Machinekit
package(s) is(are) being kept back and it is because dependency error. Th
15 matches
Mail list logo
