Changelog has changed
in [Slackware]
|
Prev: Slack 12.2 - gnuplot and wxt
Next: radeon kms
From: Loki Harfagr on 2 Mar 2010 14:47 Tue, 02 Mar 2010 05:54:25 +0000, Robby Workman did cat : > On 2010-03-02, Michael Black <et472(a)ncf.ca> wrote: >> Who knows what was going on, but today, March 1st, there are a massive >> number of updates listed in the changelog page, 25 pages as seen by >> Lynx. > > > Yep, and at least two problems. > > 1. Go ahead and upgrade gmp early in the process. > 1a. If you don't, you'll later need to manually extract the package > to / and then ( cd / ; sh install/doinst.sh ; rm -rf /install ) > > 2. libpng is an unmitigated disaster. ditto, this woman should be found and stopped!-) > Apparently the concept of > *why* shared libraries have those annoying numbers after them is > entirely foreign to them. Kill the manual symlink kludge in the > build script and build 1.4.0 yourself and all will be fine, at least > for now. > 2a. I speak for me, not for Slackware, BoB, Jehovah, or Ginsberg, > unless of course he Howls at me. Hope nobody's howling ,-) Just a footshoot note here for people like me that also use an extended for loop-aes util-linux-ng package: after the update-upgrade, *think* about thinking and if possible upgrade the standard util-l pkg or if mandatory for your reboot *think* about rebuilding it _/*before*/_ rebooting ;-) > > >> I don't really see anything to indicate why it took a month from the >> last update, but while I'm getting better at reading the changelog >> because I'm reading it regularly now, I'm not yet an expert. > > > Patience, grasshopper. :-) > > -RW
From: Martin on 2 Mar 2010 15:40 Michael Black wrote: > Who knows what was going on, but today, March 1st, there are a massive > number of updates listed in the changelog page, 25 pages as seen by Lynx. Excellent, an upgrade of libexif! The previous version was 3 years old. At last Olympus cameras are supported by the Gimp and DCRaw (unless you compiled your own libexif in the past). Martin
From: Richard Herbert on 2 Mar 2010 22:16 On Tue, 02 Mar 2010 05:54:25 +0000, Robby Workman wrote: > Patience, grasshopper. :-) I'll wait for 13.1. -- Richard Herbert Registered Linux user 14329 If there's nothing wrong with me, then ... there must be something wrong with the Universe!
From: Mikhail Zotov on 3 Mar 2010 09:00 On Tue, 02 Mar 2010 08:26:35 -0500 "John K. Herreshoff" <nope(a)not.here> wrote: > Mikhail Zotov wrote: > > > On Tue, 2 Mar 2010 00:13:42 -0500 > > Michael Black <et472(a)ncf.ca> wrote: > > > >> Who knows what was going on, but today, March 1st, there are a > >> massive number of updates listed in the changelog page > > > > http://alien.slackbook.org/blog/slackware-changelog-stalling-or-not/ > > > > Take your time with this :-) Why wait? :-) The framebuffer console is screwed up by DRM & friends, and a printer had to be reinstalled. Other than these, everything I have tried thus far works flawlessly :-) -- Mikhail
From: Ewald Pfau on 3 Mar 2010 16:31
Richard Herbert <rherbert(a)sympatico.ca>: > On Tue, 02 Mar 2010 05:54:25 +0000, Robby Workman wrote: > >> Patience, grasshopper. :-) > > I'll wait for 13.1. ----------- Take a look at /var/log/Xorg.0.log --> | X.Org X Server 1.7.5 | Release Date: 2010-02-16 | X Protocol Version 11, Revision 0 | Build Operating System: Slackware 13.1 Slackware Linux Project ----------- Having installed fresh new X, for me this has broken access to X via Intel driver. This is for hardware with 915GM. Before, I made use of old versions which are below 'extra', but those won't load anymore. <modprobe i915> throws back: WARNING: Error inserting button (/lib/modules/2.6.33-smp/kernel/drivers/acpi/button.ko): Invalid module format WARNING: Error inserting i2c_algo_bit (/lib/modules/2.6.33-smp/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module format WARNING: Error inserting agpgart (/lib/modules/2.6.33-smp/kernel/drivers/char/agp/agpgart.ko): Invalid module format WARNING: Error inserting drm (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm.ko): Invalid module format WARNING: Error inserting drm_kms_helper (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module format FATAL: Error inserting i915 (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format Results are similar when configuring 'intel' in xorg.conf. It just won't start. There is an xorgsetup program. This will freeze access to the machine perfectly (background jobs seem to continue). This is bizarre. So I went along configuring 'vesa' in xorg.conf, instead of 'intel'. Seems I have to wait. Or find some other trick. Or enough time, to find out, what to recompile on my own, in order to access X via 1600x1200 again, instead of lousy 1024x768 - vesa won't give me more than that. |