LWN.net Logo

Slackware updates

From:  changelog-AT-mrgoblin.is-a-geek.org
To:  changelog-AT-mrgoblin.is-a-geek.org
Subject:  Slackware Changelog Notice!!
Date:  Tue, 14 Mar 2006 23:16:58 +1300


        	Slackware Current ChangeLog Notice.

The following additions have been made to The Current ChangeLog.txt

		Please do not Reply to this email

-------------------------------------------------------------------
Mon Mar 13 18:53:57 CST 2006
a/aaa_base-10.2.0-noarch-3.tgz:  Added /var/empty directory.
a/gawk-3.1.5-i486-2.tgz:  Applied bugfix from the gawk mailing list to fix a
  problem with newer glibc versions pulling that "*** free(): invalid pointer"
  trick we all love.  :-)  Thanks to Grant for sending in a link to the fix.
a/glibc-solibs-2.3.6-i486-3.tgz:  Recompiled against 2.4.32 and 2.6.15.6
  kernel headers.  Yes, I have seen that shiny-looking glibc-2.4 release on
  ftp.gnu.org, but glibc-2.4 completely drops support for linuxthreads, and
  therefore will not support vanilla Linux 2.4.x kernels.  I don't think
  we're quite ready for that yet around here.
a/glibc-zoneinfo-2.3.6-noarch-3.tgz:  Updated timezone data from tzdata2006c.
a/kernel-ide-2.4.32-i486-3.tgz:  Recompiled with gcc-3.4.6.
a/kernel-modules-2.4.32-i486-4.tgz:  Recompiled with gcc-3.4.6.
  Thanks to Piter Punk for all the help revising the default entries in 
  /etc/rc.d/rc.modules.new to be more accurate for 2.6.x kernels.  I've tried
  to make it function in the default state under 2.4.x kernels too, though
  some of the modules have different names in 2.4 vs. 2.6...
  Also thanks to Didier Spaier for suggesting an example for DMA usage in the 
  section of rc.modules that loads the parallel-port support.
d/gcc-3.4.6-i486-1.tgz:  Upgraded to gcc-3.4.6.
d/gcc-g++-3.4.6-i486-1.tgz:  Upgraded to gcc-3.4.6.
d/gcc-g77-3.4.6-i486-1.tgz:  Upgraded to gcc-3.4.6.
d/gcc-gnat-3.4.6-i486-1.tgz:  Upgraded to gcc-3.4.6.
d/gcc-java-3.4.6-i486-1.tgz:  Upgraded to gcc-3.4.6.
d/gcc-objc-3.4.6-i486-1.tgz:  Upgraded to gcc-3.4.6.
l/alsa-driver-1.0.11rc3_2.4.32-i486-1.tgz:  Upgraded to alsa-driver-1.0.11rc3
  compiled for Linux 2.4.32.  The 2.6.15.6 kernel does not work properly using
  the modules in alsa-driver-1.0.10, but works fine with these.  Although I'm
  normally against using release candidates, I thought in this case that the
  version of alsa-driver used by the 2.4 and 2.6 kernels should be the same
  since the package does install some header files that would overlap.  It's
  worked fine on both 2.4.32 and 2.6.15.6 here, and the other alsa-* packages
  compile against it without errors (so I don't see a need to update those).
  I think this will work, but let me know if this upgrade causes any problems.
l/db44-4.4.20-i486-1.tgz:  For consistency, change the name of this package from
  db4 to db44, and move the header files into /usr/include/db44/, since that's
  the directory where the next version of Python will be looking for them.
  Oh, and on that topic, I've had a few people send in or provide links to
  patches that fix compiling the latest Python with db-4.4.  Thanks, but it's
  still a more conservative approach to wait until db-4.4 is officially
  supported upstream.  BTW, none of the patches were exactly the same.  :-)
  db-4.3 would also work, but it's probably not worth introducing yet-another
  already old version of db over.
  Added the --enable-cxx option.  (Suggested by Kevin Brammer)
l/glibc-2.3.6-i486-3.tgz:  Recompiled against 2.4.32 and 2.6.15.6 kernel
  headers.  Added /var/run/nscd/ directory (thanks to Dirk van Deun).
  Updated timezone data from tzdata2006c.
l/glibc-i18n-2.3.6-noarch-3.tgz:  Rebuilt.
l/glibc-profile-2.3.6-i486-3.tgz:  Recompiled against 2.4.32 and 2.6.15.6
  kernel headers.
l/gtk+2-2.8.14-i486-1.tgz:  Upgraded to gtk+2-2.8.14.
n/gnupg-1.4.2.2-i486-1.tgz:  Upgraded to gnupg-1.4.2.2.
  There have been two security related issues reported recently with GnuPG.
  From the GnuPG 1.4.2.1 and 1.4.2.2 NEWS files:
    Noteworthy changes in version 1.4.2.2 (2006-03-08)
    * Files containing several signed messages are not allowed any
      longer as there is no clean way to report the status of such
      files back to the caller.  To partly revert to the old behaviour
      the new option --allow-multisig-verification may be used.
   Noteworthy changes in version 1.4.2.1 (2006-02-14)
    * Security fix for a verification weakness in gpgv.  Some input
      could lead to gpgv exiting with 0 even if the detached signature
      file did not carry any signature.  This is not as fatal as it
      might seem because the suggestion as always been not to rely on
      th exit code but to parse the --status-fd messages.  However it
      is likely that gpgv is used in that simplified way and thus we
      do this release.  Same problem with "gpg --verify" but nobody
      should have used this for signature verification without
      checking the status codes anyway.  Thanks to the taviso from
      Gentoo for reporting this problem.
  (* Security fix *)
n/popa3d-1.0.1-i486-1.tgz:  Upgraded to popa3d-1.0.1.
n/stunnel-4.15-i486-1.tgz:  Upgraded to stunnel-4.15.
bootdisks/*:  Rebuilt using the recompiled 2.4.32 kernels.
extra/k3b/k3b-0.12.14-i486-1.tgz:  Upgraded to k3b-0.12.14.
extra/k3b/k3b-i18n-0.12.14-noarch-1.tgz:  Upgraded to k3b-i18n-0.12.14.
extra/linux-wlan-ng/linux-wlan-ng-0.2.1pre25_2.4.32-i486-3.tgz:
  Recompiled with gcc-3.4.6.
extra/linux-wlan-ng/linux-wlan-ng-0.2.3_2.6.15.6-i486-1.tgz:
  Recompiled with gcc-3.4.6 for Linux 2.6.15.6.
kernels/*.?/*:  Recompiled 2.4.32 kernels with gcc-3.4.6, upgraded
  test26.s kernel to 2.6.15.6.
pasture/gnupg-1.2.7-i486-1.tgz:  This can rest here for a little while
  just in case gnupg-1.4.2.2 causes any problems, but I doubt it will.
  I also think gnupg-1.2.7 is still secure when used securely (if that
  makes any sense ;-), or I wouldn't even leave it in /pasture...
testing/packages/linux-2.6.15.6/alsa-driver-1.0.11rc3_2.6.15.6-i486-1.tgz
  Upgraded to alsa-driver-1.0.11rc3 compiled for Linux 2.6.15.6.
  This should fix the "free_hot_cold_page" issue that was occuring with
  alsa-driver-1.0.10 and the 2.6.15+ kernels.  It fixes it here,
  anyway.  :-)
testing/packages/linux-2.6.15.6/kernel-generic-2.6.15.6-i486-1.tgz
  Upgraded to Linux 2.6.15.6 generic kernel.
testing/packages/linux-2.6.15.6/kernel-headers-2.6.15.6-i386-1.tgz
  Upgraded to Linux 2.6.15.6 kernel headers.
testing/packages/linux-2.6.15.6/kernel-modules-2.6.15.6-i486-1.tgz
  Upgraded to Linux 2.6.15.6 kernel modules.
testing/packages/linux-2.6.15.6/kernel-source-2.6.15.6-noarch-1.tgz
  Upgraded to Linux 2.6.15.6 kernel source.
+--------------------------+


	If for some reason you no longer wish to be notified of 
	Entries to the ChangeLog Please send an email 
	To: mrgoblin@userlocal.com
	Subject: "unsubscribe slacklog"
	and the subscribed email address in the body of the message.

	Thank you

	mRgOBLIN


(Log in to post comments)

Copyright © 2006, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds