LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Wednesday, July 3rd, 2019
| Time |
Event |
| 2:44p |
Security updates for Wednesday
Security updates have been issued by Debian (pdns), Fedora (kernel and kernel-headers), Mageia (cgit and firefox), Oracle (libssh2 and qemu-kvm), Red Hat (openstack-ironic-inspector, openstack-tripleo-common, and qemu-kvm-rhev), Scientific Linux (libssh2 and qemu-kvm), SUSE (bzip2, cronie, libtasn1, nmap, php7, php72, python-Twisted, and taglib), and Ubuntu (thunderbird and znc). | | 2:52p |
Stable kernel updates Stable kernels 5.1.16, 4.19.57, and 4.14.132 have been released. They all contain important fixes and users should upgrade. | | 5:02p |
[$] Debian and code names Debian typically uses code names to refer to its releases, starting with the Toy Story character names used (mostly) instead of numbers. The "Buster" release is due on July 6 and you will rarely hear it referred to as "Debian 10". There are some other code names used for repository (or suite) names in the Debian infrastructure; "stable", "testing", "unstable", "oldstable", and sometimes even "oldoldstable" are all used as part of the sources for the APTpackaging tool. But code names of any sort are hard to keep track of; a discussion on the debian-devel mailing list looks at moving away from, at least, some of the repository code names. | | 11:02p |
[$] Fedora mulls its "python" version
There is no doubt that the transition from Python 2 to Python 3
has been a difficult one, but Linux distributions have been particularly
hard hit. For many people, that transition is largely over; Python 2 will be
retired at the end of this year, at least by the core development team.
But distributions will have to support Python 2 for quite a while
after that. As part of any transition, the version that gets run from
the
python binary (or symbolic link) is something that needs to be
worked out. Fedora is currently discussing what to do about that for
Fedora 31. |
|