Add 1.4.4 source distribution
Prepare for 1.4.4 release
Added measure_label method provided by Matthias M.
Add 1.4.3 source distribution
Prepare for 1.4.3 release
Add 1.4.2 source distribution
Prepare for 1.4.2 release
fl_xid() fix provided by Dima Kogan
fixed subclassing Fl_Valuator
Fixed license regression in setup.py for pypi
Fixed license to LGPL2
Updated some documentation
Removed msys/mingw support from MakeSwig.py
Fix deprecated Python API: PyEval_CallObject
Updated README to include LGPL2 license
Patch for test/glimage.py submitted by D. Kogan
Add back linker path for external image libraries required for MacOS Homebrew FLTK package
Change project name to all lowercase to comply with PEP 625 as required by PyPI
create new source distribution tarball
fix test/demos.py to work on different platforms
fix project name and update README.md
update source distribution tarball and docs for cmake command
changed version number syntax and modified install instructions
Add new release instructions and update release notes
Updated version number and source tarball
Add check for correct FLTK development version
prepare for 1.4 release
switch back to fltk import string instead of fltk14
Fixed setup.py for macos build and only require env var FLTK_HOME for Windows
Added simple_terminal demo and fix for wizard demo
Reapply fl_xid() patch provided by Dima K.
Updated setup.py to use setuptools instead of distutils
Fix release year typo
Updated V1.3.9 source distribution
Setup.py requires wheel
Prepare release V1.3.9
Fix linking library directory for macOS
fix macOS arch for arm cpu
Fix for new swig 4.1.0
Prepared source distributions for V1.3.8
Prepared release V1.3.8
apply fl_xid() patch provided by Dima Kogan to trunk
Fixed license regression in setup.py for pypi
Fixed license to LGPL2
Updated some documentation
Removed msys/mingw support from MakeSwig.py
Fix deprecated Python API: PyEval_CallObject
Updated README to include LGPL2 license
Patch for test/glimage.py submitted by D. Kogan
On Mon, Jul 15, 2024 at 6:49 PM Moosems moosems@users.sourceforge.net wrote: [bugs:#27] Mac install breaks Status: unread Group: Created: Tue Jul 16, 2024 01:49 AM UTC by Moosems Last Updated: Tue Jul 16, 2024 01:49 AM UTC Owner: nobody Moosems $ brew install fltk Warning: fltk 1.3.9 is already installed and up-to-date. To reinstall 1.3.9, run: brew reinstall fltk Moosems $ pip3 install pyfltk --break-system-packages Collecting pyfltk Using cached pyFltk-1.3.9.tar.gz (587 kB) Preparing metadata (setup.py)...
Upgraded from Ubuntu 18.04 to 20.04 and now all clients have kernel panic during boot. I re-installed drbl drblsrv -i drblpush -i Tried both stable and unstable drbl. Also tried old 4.15 kernel using mknic-nbi. Here is the client boot up video https://youtu.be/mZw7de1TlWg at 37 seconds in the video I noticed that kernel modules are not loading during client boot process. Did anyone experience this problem before?
Add Fl_JPEG_Image from memory buffer
Update PyObject Buffer Protocol
Silence compiler format not a string literal warnings
Comment out printf in remove timeout
Okay, not sure if I solved this the right way but it seems to be working now. I got the clients to get the microcode update. created the image file by sshing into a client as root. ucode_tool --scan-system --write-earlyfw=./early.img /lib/firmware/intel-ucode now back on server cp /tftpboot/nodes/192.168.xx.xx/root/early.img /tftpboot/nbi_img/ now edit the config file vim /tftpboot/nbi_img/pxelinux.cfg/default under label drbl menu add early.img as below. No spaces (comma separated) kernel vmlinuz-pxe...
I'm noticing (using dmesg) that client systems are not getting cpu microcode updates. dmesg | grep early The method to update the microcode must be early updates. see man iucode_tool "Updating microcode early is safer. It can only be done at boot and it requires an initramfs, but it is strongly recommended: late microcode updates (which read microcode data from lib/firmware) cannot safely change visible processor features." also in the man page is an example how to create the initramfs image (but...
drbl boots the os of the server. so if your server is debian then clients can boot debian. Also, you can boot the local os of the client HD. Another option, I think, is clients can boot a small live distro like DSL. On Sun, Oct 21, 2018 at 7:32 PM amirul aliff yen971@users.sourceforge.net wrote: hey! iam using debian for my drbl server can my client boot two os like debian and centos? if can, can i get the command for configuration. can server drbl boot two os? Sent from sourceforge.net because you...
On Thu, May 24, 2018 at 3:58 PM, Subbarao Ganeshna subbaraoganeshn@users.sourceforge.net wrote: hi guys, i'm using drbl which is using 14.10, now python 3 is not running on diskless clients. so i want to update it. Does it work if i simply change initrd-pxe.img and vmlinz-pxe ? i tried and goes to initframes prompt. how can i update it without having to reinstall it. you can't update the OS simply with a new kernel or initial ram disk (initrd). You have to update the whole OS. I don't think Ubuntu...
Maybe the live version is newer and supports the clients better. Also be sure your...