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 Monday, September 4, 2017 at 5:13:34 PM UTC+2, Schooner wrote: > > 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 don't match so > dependencies can never be met > > I cannot however find any reference to 0.1.1486851828-1mk.travis.master. > gitcbd2dfd3~1jessie and have no idea where that came from. > > I am going to have to rebuild the repo manually, removing the rogue > packages back to the last proper merge. > > Don't attempt any further update etc. until you hear back. > > > On 04/09/17 15:48, 'machinen' via Machinekit wrote: > > 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 february so I am > not surprised that it is old. > > However in sources.list there is: > > deb http://httpredir.debian.org/debian/ jessie main contrib non-free#deb-src > http://httpredir.debian.org/debian/ jessie main contrib non-free > > deb http://httpredir.debian.org/debian/ jessie-updates main contrib > non-free#deb-src http://httpredir.debian.org/debian/ jessie-updates main > contrib non-free > > deb http://security.debian.org/ jessie/updates main contrib non-free#deb-src > http://security.debian.org/ jessie/updates main contrib non-free > #deb http://httpredir.debian.org/debian jessie-backports main contrib > non-free##deb-src http://httpredir.debian.org/debian jessie-backports main > contrib non-free > > deb [arch=armhf] http://deb.machinekit.io/debian jessie main#deb-src > [arch=armhf] http://deb.machinekit.io/debian jessie main > #Kernel source (repos.rcn-ee.com) : > https://github.com/RobertCNelson/linux-stable-rcn-ee##git clone > https://github.com/RobertCNelson/linux-stable-rcn-ee#cd > ./linux-stable-rcn-ee#git checkout `uname -r` -b tmp# > deb [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main#deb-src > [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main > > And the sources.list.d folder is empty. And I didn't change anything. > > > > > On Monday, September 4, 2017 at 3:14:57 PM UTC+2, Schooner wrote: >> >> 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 see where this is coming from >> >> I don't know how you can be getting this error, if your one and only >> machinekit reference is *deb.machinekit.io <http://deb.machinekit.io>*, >> as it should be. >> The package list there only refers to *0.1.1504202989* >> >> Have to suspect that your image is old and also points to >> deb.dovetail-automata.com or similar, but that serial is not there >> either AFAICT >> >> As far as FDM stuff goes I have no idea I'm afraid, don't use it, >> hopefully someone else can talk you through it once you get machinekit back >> running. >> >> >> >> On 04/09/17 13: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 the first thing when I log into this new install >> I do is run machinekit and select the Fabrikator Mini CRAMPS configuration, >> then try the ./run.py script I still get the same error. >> >> And the combination of sudo apt-get remove machinekit >> machinekit-xenomai/update/install machinekit-xenomai only removes >> machinekit packages from system and when installing it still falls on the >> same error. I will try purge next with new clean install. >> >> On Monday, September 4, 2017 at 10:02:12 AM UTC+2, Schooner wrote: >>> >>> >>> 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-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis. >>> luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master >>> .gitcbd2dfd3~1jessie is to be installed >>> E: Unable to correct problems, you have held broken packages. >>> >>> Problem is that as I don't speak Python, I don't know where the file >>> (assembly?) fdm.config should be or better yet from which file it is >>> attempting to load/import. >>> >>> >>> I don't speak parseltongue either, but this is nothing to do with python >>> >>> This is the package list for Jessie armhf >>> http://deb.machinekit.io/debian/dists/wheezy/main/binary-armhf/Packages >>> >>> As you will see the machinekit-xenomai and machinekit versions are both >>> at *0.1.1504202989*, so if your apt is trying to fetch *0.1**.* >>> *1486851828* it is working from an old package list, which means it has >>> not been updated properly. >>> >>> apt-get remove machinekit machinekit-xenomai >>> apt-get update >>> apt-get install machinekit-xenomai >>> >>> should hopefully restore things. ( If apt uninstalls other packages >>> when you do the uninstall, make sure you install those again too) >>> >>> As for where the fdm stuff is installed, >>> */usr/lib/python2.7/dist-packages/fdm* >>> It has not changed for yonks, so updating packages achieves nothing. >>> >>> >>> -- >>> website: http://www.machinekit.io blog: http://blog.machinekit.io >>> github: https://github.com/machinekit >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Machinekit" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> Visit this group at https://groups.google.com/group/machinekit. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >> website: http://www.machinekit.io blog: http://blog.machinekit.io >> github: https://github.com/machinekit >> --- >> You received this message because you are subscribed to the Google Groups >> "Machinekit" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> Visit this group at https://groups.google.com/group/machinekit. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > https://github.com/machinekit > --- > You received this message because you are subscribed to the Google Groups > "Machinekit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit https://groups.google.com/d/optout. > > > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
