07 January 2007

Lots of updates

PiterPUNK has released updated packages and sources of udev-104 and sysvinit-2.86 for testing on Slackware 11.0 - nearly identical packages are also hosted here.

I've released updated packages of Xfce-4.4rc2 with vte split from the main package; you will need to install the vte package after upgrading to the new Xfce package. If you were using the Xfce package built against dbus and dbus-glib, it's been removed - the Xfce /testing package now requires all of dbus, dbus-glib, and gamin (plus the common dependency of vte), so be sure to get all of those if you want all of the "bells and whistles" in the new 4.4 release candidates. I debated moving this out of /testing into the main repository, as it seems very stable and usable here and in feedback I've gotten, but for the time being, I'm going to leave it in /testing.

I've also rebuilt quite a few packages in the last few days after cleaning up the build scripts; I caught at least one bug in my patch to apcupsd, so that was a productive exercise. Check the ChangeLog to see the full list.

I've rearranged the site a fair amount over the last few days too - the SlackBuilds Section is now much less populated, as package sources are no longer placed there. Instead, I moved all of the package sources here to maintain better compliance with the GPL (which means I don't have to bother with email requests for sources any more) :).

Finally, we've been busy over at SlackBuilds.org too - we had more than 25 new commits in the last ChangeLog there. Thanks to all of the other admins and all the submitters for the great work!

Labels: , , , , ,


At 14/1/07 07:16 , Anonymous Anonymous said...

Hi,i have some problems
with new udev-104(i tried your udev and piterpunk udev)
but at boot
"wait_for_sysfs: waiting for '/sys/devices/virtual/vc/vcs6/bus' failed"
is full of line similar to this
then arrive at "udevtrigger failed" and stop..system won't boot
With udev-103 works all(is from linuxpackages).
My kernel is 2.6.20-rc5,can you help me?

At 14/1/07 22:34 , Anonymous Anonymous said...

Some way of contacting you would have been nice, but I guess we'll just hope you check back here...

Did you move over all of the rc.*.new files into their proper place?

Also, to my knowledge, neither of us have looked at this with a pre-release kernel. There have been some changes in the 2.6.20 development cycle, and since it hasn't released yet, we don't know what they are. Please try to reproduce this with the official stock Slackware kernel.


Post a Comment

Subscribe to Post Comments [Atom]

<< Home