diff options
Diffstat (limited to 'ChangeLog.rss')
| -rw-r--r-- | ChangeLog.rss | 62 |
1 files changed, 60 insertions, 2 deletions
diff --git a/ChangeLog.rss b/ChangeLog.rss index 3cb0b6a54..1284c6b7c 100644 --- a/ChangeLog.rss +++ b/ChangeLog.rss @@ -11,10 +11,68 @@ <description>Tracking Slackware development in git.</description> <language>en-us</language> <id xmlns="http://www.w3.org/2005/Atom">urn:uuid:c964f45e-6732-11e8-bbe5-107b4450212f</id> - <pubDate>Wed, 12 Sep 2018 21:19:38 GMT</pubDate> - <lastBuildDate>Thu, 13 Sep 2018 07:00:29 GMT</lastBuildDate> + <pubDate>Thu, 13 Sep 2018 21:41:51 GMT</pubDate> + <lastBuildDate>Fri, 14 Sep 2018 07:00:28 GMT</lastBuildDate> <generator>maintain_current_git.sh v 1.10</generator> <item> + <title>Thu, 13 Sep 2018 21:41:51 GMT</title> + <pubDate>Thu, 13 Sep 2018 21:41:51 GMT</pubDate> + <link>https://git.slackware.nl/current/tag/?h=20180913214151</link> + <guid isPermaLink="false">20180913214151</guid> + <description> + <![CDATA[<pre> +a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt. + rc.6: it was reported by birdboy that JFS is not properly unmounted unless + the order of unmounting local filesystems followed by remounting the root + filesystem read-only is inverted. I tried that, and although it did get rid + of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was + still checked at boot (and found to be clean). I believe that the existing + order of unmounting non-root filesystems followed by remounting the root + filesystem as read-only is the correct order, and found that putting + another sync between these also gets rid of the error on shutdown, so I've + done that. When using JFS as the root filesystem there's still another + similar error message that's generated earlier in the boot, though. I'm + unable to find any way to shut down a JFS root partition in a way that + leaves it clean enough that fsck will not check it at boot, but it is always + found to be clean so this should only be cosmetic. I recall this behavior of + JFS going all the way back to when it was first added to the kernel. If + anyone has a better fix, I'll take a look at it, but in my opinion it's not + really anything to worry about. +ap/ghostscript-9.25-x86_64-1.txz: Upgraded. + This release fixes problems with argument handling, some unintended + results of the security fixes to the SAFER file access restrictions + (specifically accessing ICC profile files), and some additional + security issues over the recent 9.24 release. + For more information, see: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509 + (* Security fix *) +ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded. + Linked against libzstd.so.1. Thanks to alienBOB. +ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded. +d/binutils-2.31.1-x86_64-4.txz: Rebuilt. + Since baldzhang has pointed out a valid use case for windres on Linux, + we are restoring the "Windows only" utilities, as none of them are + very large and there may be valid uses for the other ones as well. +l/freetype-2.9.1-x86_64-2.txz: Rebuilt. + Patched to build properly if windres is present on the machine. +l/sg3_utils-1.44-x86_64-1.txz: Upgraded. +l/zstd-1.3.5-x86_64-1.txz: Added. + Thanks to alienBOB. +xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded. +isolinux/initrd.img: Rebuilt. + Use the ter-114v terminus font. It has been reported that the font we were + using (ter-v14v) restricts the available console colors from 16 to 8 due + to needing an extra bit for the higher number of available glyphs (though + in testing here I couldn't see any difference). The new font covers + ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's + the best choice, so additional input is welcomed. + Thanks to bormant. +usb-and-pxe-installers/usbboot.img: Rebuilt. + Use the ter-114v terminus font. + </pre>]]> + </description> + </item> + <item> <title>Wed, 12 Sep 2018 21:19:38 GMT</title> <pubDate>Wed, 12 Sep 2018 21:19:38 GMT</pubDate> <link>https://git.slackware.nl/current/tag/?h=20180912211938</link> |