Hi Seb,
It never hurts to double tag team when wrestling a problem out.
I think your correct that having yapps2-runtime | python-yapps for dev
is a correct solution and I can test that on a fresh install in the morning.
JT
On 7/10/19 4:35 PM, Sebastian Kuzminsky wrote:
On 7/10/19 2:59 PM, John Thornton wrote:
I deleted yapps2-runtime from debian/control.top.in in the dev
section as that is the only place grep can find yapps2-runtime and
rebuilt. Now dev installs without complaining. I tested halcompile
and it runs, is there anything else in dev besides halcompile?
Hi JT, it looks like you and i have been duplicating effort on this
yapps thing today.
If you remove yapps2-runtime from linuxcnc-dev's runtime dependencies
it will install on Buster, but halcompile will not run -- it needs to
import yapps.
In the older distros that we support on 2.7 (Lucid, Precise, and
Wheezy through Stretch), the yapps runtime is in `yapps2-runtime.deb`,
but in Buster it moved to `python-yapps`. So the simple fix there is
to have linuxcnc-dev depend on `yapps2-runtime | python-yapps` instead
of just `yapps2-runtime`.
I have been hacking a bit on the yapps issue today and I have a couple
of branches nearly ready to go that i think addresses this yapps thing
for Buster, and also cleans up the whole yapps situation a bunch by
removing the old copy of yapps from our git repo, and instead
build-depending on the packaged yapps from the distro. I'll add you
as a reviewer on the PR when i make it shortly.
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
