15 packages needing updates for modular X.
by Ralph Loader
Hi,
I ran the following to look for programs & libraries referencing the
old /usr/X11R6/ directories:
find /usr/bin /usr/lib /usr/libexec -type f |
while read X
do
strings "$X" | grep /X11R6 && echo -e "**** $X\n\n"
done | tee X11R6.log
and then went through the output by hand looking for things that
actually need fixing (lots of things, e.g., search paths, are harmless
to still contain /usr/X11R6).
I came up with the following list. I don't have every Fedora RPM
installed, so there are probably others.
a2ps ghostscript htmlview openoffice libxklavier mesa ncurses openssh
pyxf86config-0.3.22-1 SDL ttmkfdir valgrind xorg-x11-drv-ati-6.5.7-1
xscreensaver
Details on the individual files are below.
Cheers,
Ralph.
a2ps:
$IBMFONTS="/usr/X11R6/lib/X11/fonts/Type1/cour*.pfa";
**** /usr/bin/ogonkify
ghostscript:
X11HOME=/usr/X11R6
**** /usr/bin/unix-lpr.sh
htmlview:
TERMS_GENERIC="/usr/bin/rxvt /usr/X11R6/bin/xterm /usr/bin/Eterm"
**** /usr/bin/htmlview
openoffice:
/usr/X11R6/lib/X11/fonts/truetype
/usr/X11R6/lib/X11/fonts/Type1
**** /usr/lib/openoffice.org2.0/program/libpsp680li.so
libxklavier:
-I/usr/X11R6/lib/X11/xkb
/usr/X11R6/lib/X11/xkb/rules/%s.xml
/usr/X11R6/lib/X11/xkb/rules/%s
/usr/X11R6/lib/X11/xkb/xkbcomp
**** /usr/lib/libxklavier.so.10.0.0
mesa:
/usr/X11R6/lib/modules/dri
**** /usr/lib/libGL.so.1.2
ncurses:
if [ -f /usr/X11R6/bin/resize ]; then
**** /usr/bin/resetall
openssh:
/usr/X11R6/bin/xauth
**** /usr/bin/ssh
pyxf86config-0.3.22-1:
/usr/X11R6
**** /usr/lib/python2.4/site-packages/ixf86configmodule.so
SDL:
/usr/X11R6/lib/X11/Metro/.version
**** /usr/lib/libSDL-1.2.so.0.7.2
ttmkfdir:
-e, --encoding name of the encoding directory file, default is
"/usr/X11R6/lib/X11/fonts/encodings/encodings.dir"
/usr/X11R6/lib/X11/fonts/encodings/encodings.dir
**** /usr/bin/ttmkfdir
valgrind:
obj:/usr/X11R6/lib*/libX11.so.6.2
obj:/usr/X11R6/lib*/libXt.so.6.0
obj:/usr/X11R6/lib*/libXaw.so.7.0
**** /usr/lib/valgrind/default.supp (& heaps more).
xorg-x11-drv-ati-6.5.7-1:
/usr/X11R6/lib/modules/multimedia/rt2_pmem.bin
**** /usr/lib/xorg/modules/multimedia/theatre200_drv.so
xscreensaver:
*textFile: /usr/X11R6/README
**** /usr/bin/xscreensaver (and others)
xterm:
/usr/X11R6/bin/luit
filename of locale converter (/usr/X11R6/bin/luit)
**** /usr/bin/xterm
18 years, 4 months
Build error on devel: libSM dependency
by Michel Salim
One of my package, grhino, fails to compile on devel because libSM has
been split from xorg into its own package, and none of the current
build dependencies include it.
The package (grhino) currently pulls its build dependencies from
desktop-file-utils (to handle the .desktop file), libgnomeui-devel and
scrollkeeper ; libgnomeui-devel depends on gtk2-devel, which in turns
(as of FC-4) depends on XFree86-devel.
So which package should I file a bug against - how are the X.org
dependencies supposed to be handled in the upcoming, modularized X
packaging?
Thanks,
--
Michel Salim 林智勇
http://www.cs.indiana.edu/~msalim
--
Michel Salim 林智勇
http://www.cs.indiana.edu/~msalim
18 years, 4 months
Re: Build error on devel: libSM dependency
by Jeremy Katz
On Fri, 2005-11-18 at 17:55 -0500, Michel Salim wrote:
> One of my package, grhino, fails to compile on devel because libSM has
> been split from xorg into its own package, and none of the current
> build dependencies include it.
>
> The package (grhino) currently pulls its build dependencies from
> desktop-file-utils (to handle the .desktop file), libgnomeui-devel and
> scrollkeeper ; libgnomeui-devel depends on gtk2-devel, which in turns
> (as of FC-4) depends on XFree86-devel.
>
> So which package should I file a bug against - how are the X.org
> dependencies supposed to be handled in the upcoming, modularized X
> packaging?
libSM is almost certainly being pulled in for libgnomeui -- so that's
where the bug belongs
Jeremy
18 years, 4 months
Another modular X11 report (#2 from me)
by Bojan Smojver
This is for Compaq Evo D510 machine, which has an Intel based graphics
chip (i845 or something like that). Today's Rawhide went up to the box
fine. The following works on the box:
- flicking between X11 and text consoles
- direct rendering
- VMWare 5.5.0 (RC2)
- suspend/resume to disk using built in kernel code
Again, top marks!
--
Bojan
18 years, 4 months
X move - app-defaults?
by Bill Nottingham
app-defaults used to be in /usr/X11R6/lib/X11/app-defaults, for all
arches.
Now, with the directory move, they are in *either*
/usr/lib/X11/app-defaults, or /usr/lib64/X11/app-defaults. Shouldn't
they continue to be in a constant directory (and really, shouldn't
that be under /usr/share?)
Bill
18 years, 4 months
Re: How to move package from extras to core ?
by Nils Philippsen
On Wed, 2005-11-16 at 21:02 -0800, Ankit Patel wrote:
> I think almost 90% of people are satisfied with the default
> installation of Fedora core. Nobody wants to try new stuffs. So, it's
> good to provide them directly, then only they realize the importance
> of the application. That's the only reason i want it to move from
> extras to core.
I'd really like to abuse people of the notion that Extras were somehow
inferior to Core. I think this stems from that Extras packages are only
installable once the system is running -- if my memory doesn't betray
me, getting Extras installable directly from anaconda has been
discussed, have these discussions born any fruit?
Nils
--
Nils Philippsen / Red Hat / nphilipp(a)redhat.com
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
18 years, 4 months
Services enabled by default
by Rahul Sundaram
Hi
There has been several services enabled by default in Fedora on the
basic assumption that whoever doesnt need it can disable it by default
while in many cases users who need it may not be aware of the
requirements. Many services that are enabled by that are being done so
for really non obvious reasons and has been the source of complaints. We
should be documenting the rationale for each and every services thats
being enabled for the different classes of installation. So here is what
we need to work out, which of the services are enabled by default for
the following installation options
* Personal Desktop
* Workstation
* Server
* Custom
If you are doing a new installation, development or one of the test
releases, check this out and post to the list. If you dont see a good
reason why a service needs to be enabled by default, question that. If
we decide its not useful for the usual scenarios, file bug reports
against the specific components in http://bugzilla.redhat.com to disable
them and post the bug numbers to the list.
All of the discussion will be kept track in
http://fedoraproject.org/wiki/DefaultServices
regards
Rahul
18 years, 4 months
init observations
by Luke Macken
I've been playing around with initng quite a bit lately and have had a
good amount of luck getting it running successfully on my rawhide laptop, a
VMWare test environment, and my FC4 desktop. Had a few issues right off the
bat, but eventually worked most of them out (thanks to the help of
Daniel Malmgren). I believe fedora related patches even hit their repos
as well.
Here's what I've seen so far...
initng - http://initng.thinktux.net
======
Pros
o Dynamic service dependencies
o Service monitoring
o Automatic respawning of services
o Parallelized service startup
o Plugin support
o Very active and helpful community
- Extremely open to getting initng working by default in Fedora
o Supports /etc/rc.* scripts via a plugin, but uses it's own format by
default (also supports xml init scripts via plugin)
o FAST AS HELL[0]
Cons
o Gentoo look-and-feel (brings back old memories)
- Having such an open-minded community, giving initng a more
unified/professional feel would hopefully be accepted
o No inherent D-BUS support
- initng's plugin support would allow this to be accomplished (but I
would bring it up to the developers; who knows, they might want it
upstream?)
- - -
After talking with Harald about his SystemManager, apparently he hasn't
actually gotten it complete enough to successfully start a system with
it yet, but he kindly answered all of the questions I had.
SystemManager - :pserver:anonymous@rhlinux.redhat.com:/usr/local/CVS servicemanager
=============
Pros
o /etc/rc replacement; so integration into our current SysVinit setup
would be close to trivial
o Will work with our current init scripts without modification
o Automatic/On-demand respawing of services
o Exporting of services as D-BUS objects
o Dynamic service dependencies
Cons
o Not complete/tested
o Still supports the /etc/rc.d/rc$i.d framework (which is horrible by
design)
- - -
I'm sure I missed many aspects of the init/bootup procedure in the above
observations, as this is far from a complete analysis. Please jump in if
you have any additional observations/questions/comments/corrections.
So.. our first step ?
Getting initng into extras definitely won't hurt. It will give everyone
a chance to play it with, and hopefully will help work most of the kinks out.
As far as SystemManager goes; it's definitely a project with lots of
potential, and if the demand is there, I'm ready to start hacking.
What does everyone else think ?
luke
[0]: I generated bootcharts for a default FC4 install with minimal
tweaking (removed a few unnecessary services) and FC4 with a
default initng install. These are in no way supposed to be an accurate
measurement of the true speeds of either of these versions of init
(they are also both running different init scripts).
http://people.redhat.com/lmacken/initng-bootchart.png
http://people.redhat.com/lmacken/SysVinit-bootchart.png
18 years, 4 months
large number of scriptlet errors from todays rawhide
by Jason Dravet
I did a yum update this morning and there are several scriptlet errors.
Should I put these errors in bugzilla?
Thanks,
Jason
Running Transaction
Updating : redhat-menus ##################### [ 1/202]
error: %post(redhat-menus-5.0.6-1.noarch) scriptlet failed, exit status 255
Updating : glibc-common ##################### [ 3/202]
error: %post(glibc-common-2.3.90-17.i386) scriptlet failed, exit status 255
Updating : glibc ##################### [ 4/202]
error: %post(glibc-2.3.90-17.i686) scriptlet failed, exit status 255
Updating : fontconfig ##################### [ 5/202]
error: %post(fontconfig-2.3.92-3.i386) scriptlet failed, exit status 255
Updating : libsepol ##################### [ 6/202]
error: %post(libsepol-1.9.40-1.i386) scriptlet failed, exit status 255
Updating : libselinux ##################### [ 7/202]
error: %post(libselinux-1.27.22-1.i386) scriptlet failed, exit status 255
Updating : gtk+ ##################### [ 14/202]
error: %pre(glibc-headers-2.3.90-17.i386) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping
glibc-headers-2.3.90-17
Updating : parted ##################### [ 17/202]
error: %post(parted-1.6.25-3.i386) scriptlet failed, exit status 255
Updating : control-center ##################### [ 18/202]
error: %post(control-center-2.12.1-4.i386) scriptlet failed, exit status 255
Updating : glibc-devel ##################### [ 21/202]
error: %post(glibc-devel-2.3.90-17.i386) scriptlet failed, exit status 255
error: %pre(xorg-x11-xfs-0.99.2-4.i386) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping xorg-x11-xfs-0.99.2-4
Updating : krb5-workstation ##################### [ 23/202]
error: %post(krb5-workstation-1.4.3-1.i386) scriptlet failed, exit status
255
Updating : krb5-devel ##################### [ 24/202]
error: %pre(nscd-2.3.90-17.i386) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping nscd-2.3.90-17
error: %pre(gdm-2.8.0.4-13.i386) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping gdm-2.8.0.4-13
Updating : urw-fonts ##################### [ 28/202]
error: %post(urw-fonts-2.3-5.noarch) scriptlet failed, exit status 255
Updating : kudzu ##################### [ 32/202]
error: %post(kudzu-1.2.13-1.i386) scriptlet failed, exit status 255
Updating : dhcdbd ##################### [ 36/202]
error: %post(dhcdbd-1.10-1.FC5.i386) scriptlet failed, exit status 255
Updating : filesystem ##################### [ 38/202]
error: %pre(kernel-2.6.14-1.1688_FC5.i686) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping
kernel-2.6.14-1.1688_FC5
Installing: kernel-devel ##################### [ 40/202]
error: %post(kernel-devel-2.6.14-1.1688_FC5.i686) scriptlet failed, exit
status 255
Updating : xorg-x11-drv-mouse ##################### [ 44/202]
error: %pre(xorg-x11-server-Xorg-0.99.3-6.i386) scriptlet failed, exit
status 255
error: install: %pre scriptlet failed (2), skipping
xorg-x11-server-Xorg-0.99.3-6
Updating : java-1.4.2-gcj-compat ##################### [ 98/202]
error: %post(java-1.4.2-gcj-compat-1.4.2.0-40jpp_55rh.i386) scriptlet
failed, exit status 255
Updating : gnu-crypto-sasl-jdk1.4 ##################### [ 99/202]
error: %post(gnu-crypto-sasl-jdk1.4-2.0.1-1jpp_8fc.i386) scriptlet failed,
exit status 255
Updating : gnu-crypto-jce-jdk1.4 ##################### [100/202]
error: %post(gnu-crypto-jce-jdk1.4-2.0.1-1jpp_8fc.i386) scriptlet failed,
exit status 255
Updating : gnu-crypto ##################### [101/202]
error: %post(gnu-crypto-2.0.1-1jpp_8fc.i386) scriptlet failed, exit status
255
Updating : jessie ##################### [102/202]
error: %post(jessie-1.0.0-9.noarch) scriptlet failed, exit status 255
18 years, 4 months