Update from gnulib list: https://lists.gnu.org/archive/html/bug-gnulib/2021-01/msg00315.html
Basically, drop in extra includes to keep their stuff from stomping on it. I think that's a terrible solution, but it's way easier than ripping out gnulib so my plan is: Build 3.4 today with the patches to fix the date. The repo will have a non-public commit on it for a bit. Add the includes, update gnulib to the latest, fix whatever *other* issue crop up. Add the --fix cmdline argument patches that have been on hold. How's that sound to everyone? I don't want to update gnulib first, since I anticipate some unknown other thing breaking, and we have a known decent release teetering on the edge of release. Thanks, Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
