2023

2022

2021

2020

2019

2018

2017

2016

2015

List overview
Download

Dev August 2016

dev@lists.clearlinux.org

2 participants
2 discussions

Start a nNew thread

Clear Linux Highlights #3

by Hutanu

[Clear Linux highlights.PNG] Key component updates We updated Firefox* to version 48 and OpenSSH to version 7.3. In addition we updated the core toolchain components: Glibc is updated to version 2.24, and Binutils is updated to version 2.27. We updated the go version to the final release candidate of 1.7. Noteworthy items This week we made the HTTP/2 protocol the default internet protocol in Clear Linux. HTTP/2 is a huge improvement over HTTP version 1.1, which is the workhorse of the internet since all web pages and the bulk of file transfers use HTTP. HTTP/2 has less latency and increased reliability and performance. All modern web browsers prefer HTTP/2 nowadays, but it is rarely enabled by Linux distributions. In Clear Linux, we now default to HTTP/2 for both the server components as well as our client components such as our software update. Clear Linux OS images are now available in Dockerhub. Docker* users can now "docker pull clearlinux" and get a basic Clear Linux image with os-core and os-core-update bundles installed on it. This allows you to use Clear Linux optimized binaries on other distributions. You can also readily explore Clear Linux functionality for future use and leverage Clear Linux bundles working in concert with Docker to encapsulate complete features and use cases like machine learning or a LAMP stack. In order to play with Clear Linux from any Linux distro, just type: docker run -it clearlinux after which the normal "swupd bundle-add" command can be used to add functionality to the bare-bones image. Component highlights The following components changed between release 9540 and 9890: * Updated components: o acpica-unix2<https://github.com/clearlinux-pkgs/acpica-unix2> 20160729 o alsa-lib<https://github.com/clearlinux-pkgs/alsa-lib> 1.1.2 o binutils<https://github.com/clearlinux-pkgs/binutils> 2.27 o btrfs-progs<https://github.com/clearlinux-pkgs/btrfs-progs> 4.7 o ciao<https://github.com/clearlinux-pkgs/ciao> 23 o curl<https://github.com/clearlinux-pkgs/curl> 7.50.1 o Cython<https://github.com/clearlinux-pkgs/Cython> 0.24.1 o diffutils<https://github.com/clearlinux-pkgs/diffutils> 3.4 o Django<https://github.com/clearlinux-pkgs/Django> 1.10 o firefox<https://github.com/clearlinux-pkgs/firefox> 48.0 o glibc<https://github.com/clearlinux-pkgs/glibc> 2.24 o go<https://github.com/clearlinux-pkgs/go> 1.7rc6 o guile<https://github.com/clearlinux-pkgs/guile> 2.0.12 o gvim<https://github.com/clearlinux-pkgs/gvim> 7.4.2181 o hwloc<https://github.com/clearlinux-pkgs/hwloc> 1.11.3 o libdrm<https://github.com/clearlinux-pkgs/libdrm> 2.4.70 o libinput<https://github.com/clearlinux-pkgs/libinput> 1.4.1 o libpcap<https://github.com/clearlinux-pkgs/libpcap> 1.8.0 o libpng<https://github.com/clearlinux-pkgs/libpng> 1.6.24 o libtasn1<https://github.com/clearlinux-pkgs/libtasn1> 4.9 o linux-lts<https://github.com/clearlinux-pkgs/linux-lts> 4.4.16 o nginx<https://github.com/clearlinux-pkgs/nginx> 1.11.3 o openssh<https://github.com/clearlinux-pkgs/openssh> 7.3p1 o php<https://github.com/clearlinux-pkgs/php> 5.6.24 o scipy<https://github.com/clearlinux-pkgs/scipy> 0.18.0 o soletta<https://github.com/clearlinux-pkgs/soletta> 1 o sqlite-autoconf<https://github.com/clearlinux-pkgs/sqlite-autoconf> 3140000 o strace<https://github.com/clearlinux-pkgs/strace> 4.13 o tcl<https://github.com/clearlinux-pkgs/tcl> 8.6.6 o tcpdump<https://github.com/clearlinux-pkgs/tcpdump> 4.8.0 o tk<https://github.com/clearlinux-pkgs/tk> 8.6.6 o vim<https://github.com/clearlinux-pkgs/vim> 7.4.2181 * New components: o matplotlib<https://github.com/clearlinux-pkgs/matplotlib> 1.5.2 o nghttp2<https://github.com/clearlinux-pkgs/nghttp2> 1.13.0 o scikit-image<https://github.com/clearlinux-pkgs/scikit-image> 0.12.3

6 years, 9 months

1
0
0 0

Trying to contact the Clear Linux packager of xorriso

by Thomas Schmitt

Hi, i am upstream developer of xorriso and want to contact its packager or the keeper of the automat which does the packaging. There are two issues: -------------------------------------------------------------------- https://github.com/clearlinux-pkgs/xorriso/blob/master/upstream mentions xorriso-1.4.5.tar.gz . This is the current development snapshot which gets overwritten several times between releases. (Most recently today.) The current release of GNU xorriso is http://ftp.gnu.org/gnu/xorriso/xorriso-1.4.4.tar.gz verificable by http://ftp.gnu.org/gnu/xorriso/xorriso-1.4.4.tar.gz.sig after gpg --keyserver keys.gnupg.net --recv-keys ABC0A854 If you use an automat which grabs what looks like the newest tarball on a web site, then let it watch http://ftp.gnu.org/gnu/xorriso/ rather than https://www.gnu.org/software/xorriso/ -------------------------------------------------------------------- I wonder why you package GNU xorriso and not the dynamic libraries libburn, libisofs, and libisoburn, which together provide the same functionality. The xorriso binary would then be built from libisoburn. Most distros prefer packaging the libraries which also may serve underneath Xfburn and Brasero. The libraries would also offer the advantage of not existing as unstable development tarballs. Current are: http://files.libburnia-project.org/releases/libburn-1.4.4.tar.gz http://files.libburnia-project.org/releases/libburn-1.4.4.tar.gz.sig http://files.libburnia-project.org/releases/libisofs-1.4.4.tar.gz http://files.libburnia-project.org/releases/libisofs-1.4.4.tar.gz.sig http://files.libburnia-project.org/releases/libisoburn-1.4.4.tar.gz http://files.libburnia-project.org/releases/libisoburn-1.4.4.tar.gz.sig libisoburn depends on libburn and libisofs. libburn additionally builds a binary named cdrskin. -------------------------------------------------------------------- Have a nice day :) Thomas

6 years, 9 months

2
2
0 0