On 30/08/2019 17:44, Xi Ruoyao via blfs-dev wrote: > On 2019-08-30 10:24 -0500, Douglas R. Reno wrote: >> On 2019-08-30 10:22, Xi Ruoyao via blfs-dev wrote: >>> On 2019-08-30 09:20 -0500, Bruce Dubbs via blfs-dev wrote: >>>> All packages have now been tagged and all tickets closed for the 9.0 >>>> release. What other things are remaining that we need to address >>>> before >>>> the Sunday release? >>>> >>>> -- Bruce >>> >>> It seems #12448 and #12459 contain various security fixes. Should we >>> backport >>> them to 9.0? >>> -- >>> Xi Ruoyao <[email protected]> >>> School of Aerospace Science and Technology, Xidian University >> >> #12456 (Ruby) has a fix for two vulnerabilities - one from 2012 and one >> from 2015. The problem with backporting updates is that I believe that >> everything that links to them has to be retested. That being said >> though, I'd give a +1 to backporting them. > > I'll try a full jhalfs build to verify 9.0 tomorrow. I hope I can use jhalfs > correctly and my 16-core workstation will work fine. But I can't guarantee > any > success. >
If you need anything, please tell me. I think a full blfs can be built by editing at most 30 scripts, most notably: - PAM (choose which "system-password" file) - openldap (choose between server and client) - mariadb and posgresql (add a sleep 1 after starting the daemon, and some config files for mariadb) - kerberos (the config needs to be done manually) - aspell (choose a dictionary) - sendmail, postfix, and exim (choose one, and verify config files) - openssh (needs manual intervention for generating key and sending it to remote) - rust (the instructions for creating /opt/rust are wrongly wrapped into porg instructions, if you use porg) - bind, bind-utils, and unbound (choose one, and verify config files) - cups, and some other packages, may have instructions like gtk-update-icon-cache or update-desktop-database before the corresponding program is installed. - java binary (choose 32/64 bits) - openjdk (unset MAKEFLAGS) - gtk2 (check config) - dhcp, dhcpcd (choose one, and check config) - tripwire - almost all the packages that install bootscripts which need some configuration in /etc/sysconfig (ftp programs, DM, and DE, network interfaces, etc) - package using tex (need to add the directory of tex binaries to PATH when running sudo, not sure it is needed anymore, but I do it :) - mozilla packages (edit config) - the environment scripts (xorg-env, kf5-intro) - kf5-frameworks and plasma (remove bash -e and exit, since they break scripts), and also edit some /opt settings. Also, it is usually necessary to rebuild poppler after qt5 (if built before), otherwise okular does not compile. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
