Tue Jun 19 22:35:25 UTC 201820180619223525

a/acl-2.2.53-x86_64-1.txz:  Upgraded.
a/attr-2.4.48-x86_64-1.txz:  Upgraded.
n/gnupg-1.4.23-x86_64-1.txz:  Upgraded.
  Sanitize the diagnostic output of the original file name in verbose mode.
  By using a made up file name in the message it was possible to fake status
  messages. Using this technique it was for example possible to fake the
  verification status of a signed mail.
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
  (* Security fix *)
x/libXaw3d-1.6.3-x86_64-1.txz:  Upgraded.
x/libinput-1.11.1-x86_64-1.txz:  Upgraded.
x/xf86-input-mouse-1.9.3-x86_64-1.txz:  Upgraded.
testing/packages/pkgtools-15.0-noarch-20.txz:  Rebuilt.
  This update is a bit scarier than usual, so we're going to test it here
  first and then move it into the main tree in a couple of days if there
  are no serious bug reports. It's well-tested here, and works with the
  slackpkg that's in -current now, but I don't know about slackpkg+ so that's
  another reason to let it cool down here first. The purpose of this update
  is to migrate the package database and directories from /var/log to
  /var/lib/pkgtools. /var/log was never a good place for this data, as it is
  considered by many to be a directory that could be wiped to free up some
  space. Originally the package database was in /var/adm, but the FSSTND
  (later FHS) group decided that directory should be a symlink to /var/log,
  and I went along with that since it was years ago and I was a n00b and didn't
  know any better. /var/lib/pkgtools will be a better and safer location.
  The removed_packages and removed_scripts directories are really just logs
  that aren't actually used for anything - those will remain under /var/log,
  but moved into /var/log/pkgtools. Everything under /var/log will be
  considered potentially non-permanent by the pkgtools - if any directories or
  symlinks disappear from there, the pkgtools will automatically recreate them
  as needed. In fact, the migration process will create symlinks from all the
  old directory locations to the new ones, so anything that expects the old
  locations (including slackpkg, for now) should continue to work. Once this
  moves into the main tree, the plan is to fix other packages to use the new
  installer script directory (/var/lib/pkgtools/setup) and change the installer
  and slackpkg to use the new native locations for everything. When slackpkg
  is changed over to use the new native locations, I'll also make sure to float
  that in testing/ for a few days before moving it to the main tree to avoid
  more unintentional disruption to slackpkg+ users.
  Be aware that the package database migration is a one-way operation, but even
  so if you later downgrade to an older version of the pkgtools it will still
  work through the compatibility symlinks.

1 files changed, 55 insertions, 2 deletions

diff --git a/ChangeLog.rss b/ChangeLog.rss
index 3b8d8306..99b885e2 100644
--- a/ChangeLog.rss
+++ b/ChangeLog.rss
@@ -11,10 +11,63 @@
       <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>Tue, 19 Jun 2018 05:47:22 GMT</pubDate>
-      <lastBuildDate>Tue, 19 Jun 2018 19:00:30 GMT</lastBuildDate>
+      <pubDate>Tue, 19 Jun 2018 22:35:25 GMT</pubDate>
+      <lastBuildDate>Wed, 20 Jun 2018 07:00:28 GMT</lastBuildDate>
       <generator>maintain_current_git.sh v 1.10</generator>
       <item>
+         <title>Tue, 19 Jun 2018 22:35:25 GMT</title>
+         <pubDate>Tue, 19 Jun 2018 22:35:25 GMT</pubDate>
+         <link>https://git.slackware.nl/current/tag/?h=20180619223525</link>
+         <guid isPermaLink="false">20180619223525</guid>
+         <description>
+           <![CDATA[<pre>
+a/acl-2.2.53-x86_64-1.txz:  Upgraded.
+a/attr-2.4.48-x86_64-1.txz:  Upgraded.
+n/gnupg-1.4.23-x86_64-1.txz:  Upgraded.
+  Sanitize the diagnostic output of the original file name in verbose mode.
+  By using a made up file name in the message it was possible to fake status
+  messages. Using this technique it was for example possible to fake the
+  verification status of a signed mail.
+  For more information, see:
+    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
+  (* Security fix *)
+x/libXaw3d-1.6.3-x86_64-1.txz:  Upgraded.
+x/libinput-1.11.1-x86_64-1.txz:  Upgraded.
+x/xf86-input-mouse-1.9.3-x86_64-1.txz:  Upgraded.
+testing/packages/pkgtools-15.0-noarch-20.txz:  Rebuilt.
+  This update is a bit scarier than usual, so we're going to test it here
+  first and then move it into the main tree in a couple of days if there
+  are no serious bug reports. It's well-tested here, and works with the
+  slackpkg that's in -current now, but I don't know about slackpkg+ so that's
+  another reason to let it cool down here first. The purpose of this update
+  is to migrate the package database and directories from /var/log to
+  /var/lib/pkgtools. /var/log was never a good place for this data, as it is
+  considered by many to be a directory that could be wiped to free up some
+  space. Originally the package database was in /var/adm, but the FSSTND
+  (later FHS) group decided that directory should be a symlink to /var/log,
+  and I went along with that since it was years ago and I was a n00b and didn't
+  know any better. /var/lib/pkgtools will be a better and safer location.
+  The removed_packages and removed_scripts directories are really just logs
+  that aren't actually used for anything - those will remain under /var/log,
+  but moved into /var/log/pkgtools. Everything under /var/log will be
+  considered potentially non-permanent by the pkgtools - if any directories or
+  symlinks disappear from there, the pkgtools will automatically recreate them
+  as needed. In fact, the migration process will create symlinks from all the
+  old directory locations to the new ones, so anything that expects the old
+  locations (including slackpkg, for now) should continue to work. Once this
+  moves into the main tree, the plan is to fix other packages to use the new
+  installer script directory (/var/lib/pkgtools/setup) and change the installer
+  and slackpkg to use the new native locations for everything. When slackpkg
+  is changed over to use the new native locations, I'll also make sure to float
+  that in testing/ for a few days before moving it to the main tree to avoid
+  more unintentional disruption to slackpkg+ users.
+  Be aware that the package database migration is a one-way operation, but even
+  so if you later downgrade to an older version of the pkgtools it will still
+  work through the compatibility symlinks.
+           </pre>]]>
+         </description>
+      </item>
+      <item>
          <title>Tue, 19 Jun 2018 05:47:22 GMT</title>
          <pubDate>Tue, 19 Jun 2018 05:47:22 GMT</pubDate>
          <link>https://git.slackware.nl/current/tag/?h=20180619054722</link>