Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

I got my "broken" hardware to work quiete fine, after leaving Whezzy and 
going to Jessie and installing machinekit with RT-Preempt kernel


I have not made jet any optimisation, so all 4 kernel are aktive, etc.

See Latency test and gmoccapy running on amd-64 with UEFI BIOS.

OK I still have to find a way to make linuxcnc find the RT-PREEMPT 
kernel, any help is wellcome.





Norbert
--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[schoone...@btinternet.com]

Just checking the first box in 'make menuconfig' for building a 64 bit 
kernel will be enough.

My configs disable various 'features' I don't want, like suspend to RAM 
/ disk etc so may not be what you require.

regards

On 02/01/2016 20:04, emc-developers-requ...@lists.sourceforge.net wrote:
> Tahnks for the hint, I just checked on that and it seems that the named
> .config is for an x86 kernel,
> So I have to walk through the xconfig stuff without understandig waht I
> do, or...


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[EBo]

On Jan 2 2016 7:23 PM, Gene Heskett wrote:
> On Saturday 02 January 2016 12:08:19 andy pugh wrote:
>
>> On 2 January 2016 at 16:04, Niemand Sonst  wrote:
>> >> I am sorry you purchased defective hardware.  You should consider
>> >> returning it for a refund if you still can.
>> >
>> > The hardware is not defect, it is just new and does what it is
>> > suposed to do.
>>
>> It is broken by design, but it is still broken.
>
> I am with Andy. It may be by design, but its still broken, return it 
> and
> insist on getting something that does work.  The one sure way to get
> those nitwits attention is to bounce the product back at them for a
> refund.

While I have to agree with Andy about the brokenness of OS locked Bios, 
I have also found that it is as likely they will refuse the return 
because you did something unexpected/non-standard to it.  If you can 
return it and get a different one.  If you cannot, then complain all 
over the place -- bad PR is something that chips away a little by little 
at this typ of crap.  Also, take a look at the low end Sager/Clevo 
laptops.  There are companies which configure them with linux installed. 
I use high end versions of these at work and home.

   EBo --


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

So again, the notebook does not Block the install of other OS!!!

I installed
- Windows 7
- Windows 8.1
- Debian 8.2 amd64 (twice)

and I can boot also from:
- Clonezilla
- Boot repair disk
- Linux Mint Live

So it is OK!

Just Linuxcnc ISO is 32-bit and therefor not suited!

I am satisfied with the hardware, it has good design, is powerfull and I 
got it at a resonable price (€ 699)

IHMO not the Laptop is wrong, but we will have to see how linuxcnc will 
handle modern hardware in the future.


@EBo
I just llog for a Sager/Clevo notebook and the new ones do have UEFI 
Bios like my one  ;-)

Norbert


Am 03.01.2016 um 12:02 schrieb EBo:
> On Jan 2 2016 7:23 PM, Gene Heskett wrote:
>> On Saturday 02 January 2016 12:08:19 andy pugh wrote:
>>
>>> On 2 January 2016 at 16:04, Niemand Sonst  wrote:
> I am sorry you purchased defective hardware.  You should consider
> returning it for a refund if you still can.
 The hardware is not defect, it is just new and does what it is
 suposed to do.
>>> It is broken by design, but it is still broken.
>> I am with Andy. It may be by design, but its still broken, return it
>> and
>> insist on getting something that does work.  The one sure way to get
>> those nitwits attention is to bounce the product back at them for a
>> refund.
> While I have to agree with Andy about the brokenness of OS locked Bios,
> I have also found that it is as likely they will refuse the return
> because you did something unexpected/non-standard to it.  If you can
> return it and get a different one.  If you cannot, then complain all
> over the place -- bad PR is something that chips away a little by little
> at this typ of crap.  Also, take a look at the low end Sager/Clevo
> laptops.  There are companies which configure them with linux installed.
> I use high end versions of these at work and home.
>
> EBo --
>
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[EBo]

@Norbert

the Sager/Clevo notebook are suported for Linux, so if you have a 
problem they, unlike Best Buy, do not try to claim that I violated the 
warranty by installing Linux.

On Jan 3 2016 5:40 AM, Niemand Sonst wrote:
> So again, the notebook does not Block the install of other OS!!!
>
> I installed
> - Windows 7
> - Windows 8.1
> - Debian 8.2 amd64 (twice)
>
> and I can boot also from:
> - Clonezilla
> - Boot repair disk
> - Linux Mint Live
>
> So it is OK!
>
> Just Linuxcnc ISO is 32-bit and therefor not suited!
>
> I am satisfied with the hardware, it has good design, is powerfull 
> and I
> got it at a resonable price (€ 699)
>
> IHMO not the Laptop is wrong, but we will have to see how linuxcnc 
> will
> handle modern hardware in the future.
>
>
> @EBo
> I just llog for a Sager/Clevo notebook and the new ones do have UEFI
> Bios like my one  ;-)
>
> Norbert
>
>
> Am 03.01.2016 um 12:02 schrieb EBo:
>> On Jan 2 2016 7:23 PM, Gene Heskett wrote:
>>> On Saturday 02 January 2016 12:08:19 andy pugh wrote:
>>>
 On 2 January 2016 at 16:04, Niemand Sonst  wrote:
>> I am sorry you purchased defective hardware.  You should 
>> consider
>> returning it for a refund if you still can.
> The hardware is not defect, it is just new and does what it is
> suposed to do.
 It is broken by design, but it is still broken.
>>> I am with Andy. It may be by design, but its still broken, return 
>>> it
>>> and
>>> insist on getting something that does work.  The one sure way to 
>>> get
>>> those nitwits attention is to bounce the product back at them for a
>>> refund.
>> While I have to agree with Andy about the brokenness of OS locked 
>> Bios,
>> I have also found that it is as likely they will refuse the return
>> because you did something unexpected/non-standard to it.  If you can
>> return it and get a different one.  If you cannot, then complain all
>> over the place -- bad PR is something that chips away a little by 
>> little
>> at this typ of crap.  Also, take a look at the low end Sager/Clevo
>> laptops.  There are companies which configure them with linux 
>> installed.
>> I use high end versions of these at work and home.
>>
>> EBo --
>>
>>
>> 
>> --
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>
>
>
> 
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

Hallo,

I have to come back to this matter, because I got my new Laptop to get a 
second development system for 2.7 and master.
This machine is an ACER E5-771G-7169, it has an Intel I7, 8 GB Ram, and 
a hybrid graphic card (Intel / Nvidia M840).
As standard OS it has Windows 8.1. It was not too hard to use Windows to 
reparation the 100 GB hard disk to get space for Debian installations.
I splited it to 4 partitions (Windows 8.1 , Debian 8.2 MATE ; Debian 8.2 
LXDE LinuxCNC and one for common data).

I took the first hurdle, the UEFI Bios and could install Debian 8.2 - 
amd64 - MATE, but the second hurdle installing LinuxCNC from the ISO 
could not be taken, because UEFI Bios only accept 64-bit operating 
systems, even with security boot disabled! Fortunately ACER has a custom 
mode for other operating systems, otherwise it would not have been 
possible to boot debian, because the uefi bootloader is not certified!

Off topic : Where the hell are we going? Hardware is able to decide 
witch operating system is allowed. And trying to install debian on some 
SAMSUNG laptops can kill the laptop!

OK; back to the present:
- The ISO is 32 bit and does not support UEFI BIOS
- Wheesy is not any more the stable version

As buildbot says for 2.7-rt-preempt:
Jessie (uspace: realtime with RT-Preempt, and simulation)
architectures: amd64, i386
I decided to install debian 8.2 - amd64 with LXDE, what was not that 
complicated after getting the Laptop to boot from the USB Stick.
Very strange behavior, no sound, no wlan and the touchpad not working 
properly, installed from USB Stick with ISO 
debian-8.2.0-amd64-lxde-CD1.iso, but on the other partition from 
debian-8.2.0-amd64-netinstall.iso everything works just like a charm. 
After sorting most of the stuff out, I added the linuxcnc repositories:

deb http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt
deb-src http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt

and installed LinuxCNC.

OK Latency test shows 32035966 ns, that is the highest I ever got! Even a 
virtual machine is better ;-) But i did no optimation till now.
I decides to start LinuxCNC and the gmoccapy, my baby ;-)

Error: in module player, component "playbin" not found:

After installing "gstreamer0.10-plugins-base" the start went OK. Jeff could you 
please add that dependence? gmoccapy and gscreen depend on that.
Neverthereless the code for both GUI must be adapted to avoid such an error, 
only for not beeing present "sound". I will fix that as soon as my
new development system is running.

I do connect the laptop with WLAN0 to the world and want to use eth0 to connect 
to a MESA 7i76E to control my testing hardware.
But as far as I found out till now, that will not be possible, because ther is 
no realtime kernel for Jessie 64 bit
and the info on buildbot is not correct.

So, what to do?
- Does wheesy support 64 bit completly ?
- do all the optimation to the installed lenny system?
- change over to mint?
- Sit back and wait for others to fix my sistem ;-)

For the future IMO:
- We need a UEFI Booting 64-bit system, as for new hardware it will be 
absolutely necessary.
- As discussion about the OS GUI we should put at least two of in the 
new ISO, I would suggest LXDE / XFCE and MATE.


So lets discuss and solve!

Norbert (gmoccapy)


Am 22.12.2015 um 22:24 schrieb Jeff Epler:
>> Date: Tue, 29 Sep 2015 15:43:16 -0500
>> From: Jeff Epler 
>> To: emc-developers@lists.sourceforge.net
>> Subject: [Emc-developers] LinuxCNC operating system support in master branch 
>> / for eventual LinuxCNC 2.8
>>
>> For LinuxCNC 2.7 we produce packages for
>>  Ubuntu 10.04 "Lucid Lynx" (rtai realtime)
>>  Ubuntu 12.04 "Precise Pangolin" (rtai realtime)
>>  Debian 7.x "Wheezy" (rtai and rt-preempt realtime)
>>  Debian 8.x "Jessie" (rt-preempt realtime)
>>
>> Canonical's extended release cycle for Ubuntu 10.04 has now ended.
>>
>> In addition, I have identified two benefits from dropping support for
>> Ubuntu 10.04 in the master branch, meaning that the oldest OSes that
>> would be supported in the 2.8 release would be Ubuntu 12.04 and Debian
>> 7.x.
>>
>>   - The LD_PRELOAD workaround for the libgl bug can be dropped
>>   - The minimum Python version requirement can be increased to 2.7.
>>
>> The second benefit is the major one -- Python 2.7.x has a lot of items
>> that can ease the porting process to Python3.  Because Python 2.7 has
>> end-of-life in 2020, and our release cycle is frequently greater than 1
>> year, we need to start this process soon.
>>
>> I am happy to postpone this plan by a release cycle if a developer plans
>> to maintain 10.04 compatibility during the current release cycle.  If
>> you plan to do that, please speak up.
>>
>> Jeff
> http://mid.gmane.org/20150929204315.GB63865%40unpythonic.net
>
> (the process of python3 porting alluded to in that message has not started at
> all)
>
> Jeff
>
> 

Re: [Emc-developers] Who changed the requiered python version?

[andy pugh]

On 2 January 2016 at 16:04, Niemand Sonst  wrote:
>> I am sorry you purchased defective hardware.  You should consider
>> returning it for a refund if you still can.
>
> The hardware is not defect, it is just new and does what it is suposed
> to do.

It is broken by design, but it is still broken.

-- 
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python, version?

[schoone...@btinternet.com]

On 02/01/16 17:09, emc-developers-requ...@lists.sourceforge.net wrote:
> You are right, no realtime kernel till now! The coment in buildbot
> should be adapted to reflect this and make clear there is no rt Kernel
> for Jessie.
It is simple to build a rt-preempt kernel for Jessie, I am currently 
running an amd64 version of 4.1.15-rt17

Peter Wallace did a guide some while back too, just replace version 
numbers with current ones.
http://sourceforge.net/p/emc/mailman/message/33665819/

regards


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

Please see my comments:

Am 02.01.2016 um 16:39 schrieb Jeff Epler:
> On Sat, Jan 02, 2016 at 01:08:41PM +0100, Niemand Sonst wrote:
>> I took the first hurdle, the UEFI Bios and could install Debian 8.2 -
>> amd64 - MATE, but the second hurdle installing LinuxCNC from the ISO
>> could not be taken, because UEFI Bios only accept 64-bit operating
>> systems, even with security boot disabled!
> I am sorry you purchased defective hardware.  You should consider
> returning it for a refund if you still can.

The hardware is not defect, it is just new and does what it is suposed 
to do. In future we will see any more hardware with BIOS. The UEFI is 
the new BIOS and Acer is one of the few manufactures supporting also the 
custom mode. By the way, Microsoft himself insistat in that mode to 
allow other OS to be installed on the hardware.

> [...]
>> After sorting most of the stuff out, I added the linuxcnc repositories:
>>
>> deb http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt
>> deb-src http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt
>>
>> and installed LinuxCNC.
>>
>> OK Latency test shows 32035966 ns, that is the highest I ever got! Even a 
>> virtual machine is better ;-) But i did no optimation till now.
> It is quite likely that after performing these steps *you are not
> operating with a realtime kernel*.  uspace will run both on vanilla
> kernels (but without using realtime task priority) and on preempt-rt
> kernels (using realtime task priority).  Only in the latter case (and if
> your computer has acceptable RT performance) will you get good latency.

You are right, no realtime kernel till now! The coment in buildbot 
should be adapted to reflect this and make clear there is no rt Kernel 
for Jessie.
> Unfortunately, a preempt-rt kernel is not currently available from
> Debian for 8.x -- there *was* one in jessie-backports, but they deleted
> it.
>
> Seb's RTAI kernel for 64-bit systems crashes, so I similarly can't
> recommend that.

Sep, if you go on with the development, let me know, I am willing to test.

> However, for developing user interface software, uspace non-realtime is
> typically adequate.  For running attached hardware over ethernet, not so

For sim development no reason for the rt-kernel, but I test my stuff 
also on hardware!

> much.  I woudln't recommend it even for testing.
>
>> After installing "gstreamer0.10-plugins-base" the start went OK. Jeff could 
>> you please add that dependence?
> Yes.   Done.

Thanks.

>> Neverthereless the code for both GUI must be adapted to avoid such an error, 
>> only for not beeing present "sound". I will fix that as soon as my
>> new development system is running.
>>
>> I do connect the laptop with WLAN0 to the world and want to use eth0 to 
>> connect to a MESA 7i76E to control my testing hardware.
>> But as far as I found out till now, that will not be possible, because ther 
>> is no realtime kernel for Jessie 64 bit
>> and the info on buildbot is not correct.
> So, nobody has written the install instructions for Debian Jessie with
> preempt-rt.  It should be possible using snapshot.debian.org, which
> still has an archive of the preempt-rt kernel from jessie-backports.
> (The kernel was withdrawn not because it was broken, but because Debian
> testing's development moved on to a kernel without a RT patch)
>
>  http://snapshot.debian.org/package/linux/4.1.3-1/
>
> .. but having just spent 15 minutes trying to do so I haven't yet been
> successful at getting apt to automatically download and install these
> packages.

I will look on that and keep you informed.

>> - Does wheesy support 64 bit completly ?
> I used wheezy with preempt-rt kernel in the past.  There is a preempt-rt
> kernel in main for wheezy.
> https://packages.debian.org/search?suite=wheezy=linux-image-rt-amd64
>
> Jeff

So I will try to make another installation with Wheesy.

> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

Hallo Viesturs,

OK, I can see your opinion, but I do not share it.
The hardware has a 64 bit architectur and allows running all kind of OS 
as far as they support UEFI. Most do!
But UEFI is designed for 64 bit oppenrating systems. So The hardware is 
fine.

The question is, how we (linuxcnc) will handle that in the future, as 
new hardware will more and more in that direction, bringing more 
security and flexibility on multiboot systems to the user.

I have not checked what happen, if I switch the in the UEFI settings 
from UEFI to legacy, IMHO it should enable also running 32 bit OS.
But why cut the performance of a system and lock out my Windows CAD / 
CAM program?

So please check the requierments for future ISO Disks. Debian shows, 
that one disk can handle UEFI and Normal Boot.

Norbert

Am 02.01.2016 um 19:56 schrieb Viesturs Lācis:
> 2016-01-02 19:49 GMT+02:00 Niemand Sonst :
>> Do you mean that every new hardware witch include new developments and
>> new features is broken by design?
> I guess that he meant that implementing a solution (UEFI) which
> basically accepts OS from particular vendor (read: Microsoft) and does
> not fully support anything else is fucked-up idea and shitty (read:
> broken) design by default.
> So yes, I do support bringing that computer back to store and asking
> for a refund, because you purchased a computer, which has problem -
> there is no way to install 32-bit opensource OS there. They did not
> warn you about that prior the purchase, thus it should be treated as a
> defective device.
>
> Viesturs
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python, version?

[Niemand Sonst]

Tahnks for the hint, I just checked on that and it seems that the named 
.config is for an x86 kernel,
So I have to walk through the xconfig stuff without understandig waht I 
do, or...

could you post your kernel .config file, I will just test then.

Norbert

Am 02.01.2016 um 18:18 schrieb schoone...@btinternet.com:
> On 02/01/16 17:09, emc-developers-requ...@lists.sourceforge.net wrote:
>> You are right, no realtime kernel till now! The coment in buildbot
>> should be adapted to reflect this and make clear there is no rt Kernel
>> for Jessie.
> It is simple to build a rt-preempt kernel for Jessie, I am currently
> running an amd64 version of 4.1.15-rt17
>
> Peter Wallace did a guide some while back too, just replace version
> numbers with current ones.
> http://sourceforge.net/p/emc/mailman/message/33665819/
>
> regards
>
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Jeff Epler]

On Sat, Jan 02, 2016 at 01:08:41PM +0100, Niemand Sonst wrote:
> I took the first hurdle, the UEFI Bios and could install Debian 8.2 - 
> amd64 - MATE, but the second hurdle installing LinuxCNC from the ISO 
> could not be taken, because UEFI Bios only accept 64-bit operating 
> systems, even with security boot disabled!

I am sorry you purchased defective hardware.  You should consider
returning it for a refund if you still can.

[...]
> After sorting most of the stuff out, I added the linuxcnc repositories:
> 
> deb http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt
> deb-src http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt
> 
> and installed LinuxCNC.
> 
> OK Latency test shows 32035966 ns, that is the highest I ever got! Even a 
> virtual machine is better ;-) But i did no optimation till now.

It is quite likely that after performing these steps *you are not
operating with a realtime kernel*.  uspace will run both on vanilla
kernels (but without using realtime task priority) and on preempt-rt
kernels (using realtime task priority).  Only in the latter case (and if
your computer has acceptable RT performance) will you get good latency.

Unfortunately, a preempt-rt kernel is not currently available from
Debian for 8.x -- there *was* one in jessie-backports, but they deleted
it.

Seb's RTAI kernel for 64-bit systems crashes, so I similarly can't
recommend that.

However, for developing user interface software, uspace non-realtime is
typically adequate.  For running attached hardware over ethernet, not so
much.  I woudln't recommend it even for testing.

> After installing "gstreamer0.10-plugins-base" the start went OK. Jeff could 
> you please add that dependence?

Yes.   Done.

> Neverthereless the code for both GUI must be adapted to avoid such an error, 
> only for not beeing present "sound". I will fix that as soon as my
> new development system is running.
> 
> I do connect the laptop with WLAN0 to the world and want to use eth0 to 
> connect to a MESA 7i76E to control my testing hardware.
> But as far as I found out till now, that will not be possible, because ther 
> is no realtime kernel for Jessie 64 bit
> and the info on buildbot is not correct.

So, nobody has written the install instructions for Debian Jessie with
preempt-rt.  It should be possible using snapshot.debian.org, which
still has an archive of the preempt-rt kernel from jessie-backports.
(The kernel was withdrawn not because it was broken, but because Debian
testing's development moved on to a kernel without a RT patch)

http://snapshot.debian.org/package/linux/4.1.3-1/

.. but having just spent 15 minutes trying to do so I haven't yet been
successful at getting apt to automatically download and install these
packages.

> - Does wheesy support 64 bit completly ?

I used wheezy with preempt-rt kernel in the past.  There is a preempt-rt
kernel in main for wheezy.
https://packages.debian.org/search?suite=wheezy=linux-image-rt-amd64

Jeff

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

Am 02.01.2016 um 18:08 schrieb andy pugh:
> On 2 January 2016 at 16:04, Niemand Sonst  wrote:
>>> I am sorry you purchased defective hardware.  You should consider
>>> returning it for a refund if you still can.
>> The hardware is not defect, it is just new and does what it is suposed
>> to do.
> It is broken by design, but it is still broken.
>
Andy,

I do not understand what you mean.
It is brandnew hardware, it is working with Windows 8.1, Windows 7 and 
Debian 8.2, all in 64 bit.
Also boot repair disk, clonezilla and Mint Live do work as a charme.
So I do not understand what you think is broken.

Do you mean that every new hardware witch include new developments and 
new features is broken by design?
If so, we should all go back to Comodore 64?

So please help me to understand what you mean?

Norbert

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Viesturs Lācis]

2016-01-02 19:49 GMT+02:00 Niemand Sonst :
> Do you mean that every new hardware witch include new developments and
> new features is broken by design?

I guess that he meant that implementing a solution (UEFI) which
basically accepts OS from particular vendor (read: Microsoft) and does
not fully support anything else is fucked-up idea and shitty (read:
broken) design by default.
So yes, I do support bringing that computer back to store and asking
for a refund, because you purchased a computer, which has problem -
there is no way to install 32-bit opensource OS there. They did not
warn you about that prior the purchase, thus it should be treated as a
defective device.

Viesturs

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Gene Heskett]

On Saturday 02 January 2016 12:08:19 andy pugh wrote:

> On 2 January 2016 at 16:04, Niemand Sonst  wrote:
> >> I am sorry you purchased defective hardware.  You should consider
> >> returning it for a refund if you still can.
> >
> > The hardware is not defect, it is just new and does what it is
> > suposed to do.
>
> It is broken by design, but it is still broken.

I am with Andy. It may be by design, but its still broken, return it and 
insist on getting something that does work.  The one sure way to get 
those nitwits attention is to bounce the product back at them for a 
refund.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[EBo]

I cannot speak to the testing script, but I will say that there are a 
handful of changes that need to be done to make 2.7 code run in 3.0+.  I 
doubt that LCNC will run on any python3 interrupter (and would be happy 
to be proven wrong).

That said, we really should get all the python scripts running in 2.7 
and 3.4 as they are the most stable.

EBo --


On Dec 22 2015 12:39 PM, Niemand Sonst wrote:
> OK I installed python 3.1
> Same error
>
> I made: alias python=python3
> Same error
>
> I made: sudo update-alternatives -- install /usr/bin/python
> /usr/bin/python2   10
> Same error
>
> What now?
>
> 3.1 is newer than 2.7!
>
> from a frustrated Norbert
>
> Am 22.12.2015 um 20:26 schrieb Niemand Sonst:
>> Hallo,
>>
>> I am working on the merge of the gmoccapy 2.0 version (5 axis) to 
>> master.
>> I made a fresh pull on my development machine (Ubuntu 10.04) and got
>> during ./configure the error
>>
>> Python Version too old (2.7 or newer requiered)
>>
>> When did this change happen?
>> We do lock out all users with the very stable and good looking 
>> UBUNTU 10.04!
>>
>> So I stop now and go to vacations first, as I do not like this 
>> behavior,
>> without being announced in advance!
>>
>> Norbert
>>
>> 
>> --
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>
>
>
> 
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Chris Morley]

Norbert you must use 2.7 or change the requirements back to 2.6.
3.x is a very different animal.
This change was because it was decided to drop 10.04 for master.
basically you can't develop master with Ubuntu 10.04 anymore.
If you didn't happen to see the discussion in IRC I guess you didn't 
need to know. :(
I'm gonna try mint soon - Debian is too annoying for use on my main 
laptop (the one I do most everything on).

Chris M

> To: emc-developers@lists.sourceforge.net
> From: nie...@web.de
> Date: Tue, 22 Dec 2015 20:39:33 +0100
> Subject: Re: [Emc-developers] Who changed the requiered python version?
> 
> OK I installed python 3.1
> Same error
> 
> I made: alias python=python3
> Same error
> 
> I made: sudo update-alternatives -- install /usr/bin/python 
> /usr/bin/python2   10
> Same error
> 
> What now?
> 
> 3.1 is newer than 2.7!
> 
> from a frustrated Norbert
> 
> Am 22.12.2015 um 20:26 schrieb Niemand Sonst:
> > Hallo,
> >
> > I am working on the merge of the gmoccapy 2.0 version (5 axis) to master.
> > I made a fresh pull on my development machine (Ubuntu 10.04) and got
> > during ./configure the error
> >
> > Python Version too old (2.7 or newer requiered)
> >
> > When did this change happen?
> > We do lock out all users with the very stable and good looking UBUNTU 10.04!
> >
> > So I stop now and go to vacations first, as I do not like this behavior,
> > without being announced in advance!
> >
> > Norbert
> >
> > --
> > ___
> > Emc-developers mailing list
> > Emc-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
> >
> 
> 
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
  
--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Chris Morley]

I stand corrected and apologize for my quip. I just didn't remember this at 
all.and I do understand it needs to happen.
1004 is just so nice to use :)

Chris M

- Reply message -
From: "Sebastian Kuzminsky" 
To: "EMC developers" 
Subject: [Emc-developers] Who changed the requiered python version?
Date: Tue, Dec 22, 2015 12:23 PM


On 12/22/15 1:10 PM, Chris Morley wrote:
> This change was because it was decided to drop 10.04 for master.
> basically you can't develop master with Ubuntu 10.04 anymore.
> If you didn't happen to see the discussion in IRC I guess you didn't
> need to know. :(

Jeff proposed it on the emc-developers list in September:
> I am happy to postpone this plan by a release cycle if a developer plans
> to maintain 10.04 compatibility during the current release cycle.  If
> you plan to do that, please speak up.

Here's the full email:

http://article.gmane.org/gmane.linux.distributions.emc.devel/15246


--
Sebastian Kuzminsky

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Jeff Epler]

> Date: Tue, 29 Sep 2015 15:43:16 -0500
> From: Jeff Epler 
> To: emc-developers@lists.sourceforge.net
> Subject: [Emc-developers] LinuxCNC operating system support in master branch 
> / for eventual LinuxCNC 2.8
>
> For LinuxCNC 2.7 we produce packages for
> Ubuntu 10.04 "Lucid Lynx" (rtai realtime)
> Ubuntu 12.04 "Precise Pangolin" (rtai realtime)
> Debian 7.x "Wheezy" (rtai and rt-preempt realtime)
> Debian 8.x "Jessie" (rt-preempt realtime)
> 
> Canonical's extended release cycle for Ubuntu 10.04 has now ended.
> 
> In addition, I have identified two benefits from dropping support for
> Ubuntu 10.04 in the master branch, meaning that the oldest OSes that
> would be supported in the 2.8 release would be Ubuntu 12.04 and Debian
> 7.x.
> 
>  - The LD_PRELOAD workaround for the libgl bug can be dropped
>  - The minimum Python version requirement can be increased to 2.7.
> 
> The second benefit is the major one -- Python 2.7.x has a lot of items
> that can ease the porting process to Python3.  Because Python 2.7 has
> end-of-life in 2020, and our release cycle is frequently greater than 1
> year, we need to start this process soon.
> 
> I am happy to postpone this plan by a release cycle if a developer plans
> to maintain 10.04 compatibility during the current release cycle.  If
> you plan to do that, please speak up.
> 
> Jeff
http://mid.gmane.org/20150929204315.GB63865%40unpythonic.net

(the process of python3 porting alluded to in that message has not started at
all)

Jeff

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

OK I installed python 3.1
Same error

I made: alias python=python3
Same error

I made: sudo update-alternatives -- install /usr/bin/python 
/usr/bin/python2   10
Same error

What now?

3.1 is newer than 2.7!

from a frustrated Norbert

Am 22.12.2015 um 20:26 schrieb Niemand Sonst:
> Hallo,
>
> I am working on the merge of the gmoccapy 2.0 version (5 axis) to master.
> I made a fresh pull on my development machine (Ubuntu 10.04) and got
> during ./configure the error
>
> Python Version too old (2.7 or newer requiered)
>
> When did this change happen?
> We do lock out all users with the very stable and good looking UBUNTU 10.04!
>
> So I stop now and go to vacations first, as I do not like this behavior,
> without being announced in advance!
>
> Norbert
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Sebastian Kuzminsky]

On 12/22/15 1:10 PM, Chris Morley wrote:
> This change was because it was decided to drop 10.04 for master.
> basically you can't develop master with Ubuntu 10.04 anymore.
> If you didn't happen to see the discussion in IRC I guess you didn't
> need to know. :(

Jeff proposed it on the emc-developers list in September:
> I am happy to postpone this plan by a release cycle if a developer plans
> to maintain 10.04 compatibility during the current release cycle.  If
> you plan to do that, please speak up.

Here's the full email:

http://article.gmane.org/gmane.linux.distributions.emc.devel/15246


-- 
Sebastian Kuzminsky

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers