Thank you for the quick feedback, Rod!
On 28.01.22 14:02, Rod Webster wrote:
Thanks Stefan,
I was unable to download any of the files to my Chromebook. I will try
again on a real PC in the morning.
I know Drive has added some extra security around possible cyber attacks
through drive. Its possible downloads are blocked.
Hm. Ok. I have a regular website that we can also use. Tell me if these
problems persist.
It did tell me to try enabling third party cookies in chrome but it made no
difference.
Tomorrow morning I am going to be installing Deban 11.2 on a X86 device so
I may have had time to try this as well.
I had 2 goes today at the X86 installation and for some reason I had
troubles today after 2 attempts with debian 11.2 because some dependencies
including suffixes on the versions similar to this:
libmount-dev : Depends: libblkid-dev but it is not going to be installed
Depends: libmount1 ( 2.36.1-8) but 2.36.1-8+deb11u1 is to
be installed
I suggest you install aptitude and then run "sudo aptitude install
libmount-dev" which then proposes a solution to get this installed.
Its a bit annoying because I have LCNC running on three Debian 11 PC's
already and the machine in question was running 11.0 installed about 2
weeks before the official Bullseye release (eg when it was testing).. These
errors are pretty deep in the dependency tree so hard to find the actual
problem packages (Ghostscript is one).
-> aptitude
Anyway tomorrow I am trying a scripted approach developed by James Walker
which is intended to become part of QTPYVCP.
https://github.com/joco-nz/lcnc-bullseye-installer
but am open to ideas...
I proposed a simplification on
https://github.com/joco-nz/lcnc-bullseye-installer/pull/1
Best,
Steffen
On Fri, 28 Jan 2022 at 22:30, Steffen Möller <[email protected]> wrote:
Hello again,
I built the arm64 packages on an odroid that runs armbian's bullseye
variant. Placed it on
https://drive.google.com/drive/folders/1kTr7uigCQY3c-layLJKdXqN5sRsXJnWo?usp=sharing
It worked just fine, except that armbian apparently does not have that
gpl2-variant of the readline library, so I prepared a respective pull
request to ease that. No problems with the boost libraries.
For what it's worth, I gpg-signed the packages (the changes and dsc file
to be exact) with my Debian-developer-key, so you can have the same
trust in the packages as if you received them via Debian:
$ dpkg-sig -l *deb
Processing linuxcnc-doc-en_2.9.0~pre0_all.deb...
builder
Processing linuxcnc-doc-es_2.9.0~pre0_all.deb...
builder
builder0
Processing linuxcnc-doc-fr_2.9.0~pre0_all.deb...
builder
Processing linuxcnc-doc-zh-cn_2.9.0~pre0_all.deb...
builder
Processing linuxcnc-uspace_2.9.0~pre0_arm64.deb...
builder
Processing linuxcnc-uspace-dbgsym_2.9.0~pre0_arm64.deb...
builder
Processing linuxcnc-uspace-dev_2.9.0~pre0_arm64.deb...
builder
If the "builder" does not show then the package was not signed.
Best,
Steffen
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
