[BUG] yelp depends on mozilla?
by Leo
Hi all,
I hope this is the right mail list to raise this question. I'm running
FC5 and both mozilla and firefox are installed. But when I removed
mozilla, yelp is also removed. I think there is a bug here. Any
comments?
--
Leon
17 years, 11 months
Confused about /usr/bin/nm, linker, and stripped libs
by John Ellson
These days rpm installs most libs stripped of their symbols, which is
fine as it makes them smaller and presumably load faster.
But how does the linker resolve symbols against stripped libs? And if
the linker can do it, why can't /usr/bin/nm ?
John
17 years, 11 months
Best practices wrt. Changelog entries in spec file (upstream vs. specfile)
by Joost Soeterbroek
Hi,
I have a question regarding Changelog entries in spec files. When
packaging for a new upstream version of a given package you have to deal
with 2 different changelog informations:
1) upstream/source specific changelog information
2) spec file/packager specific changelog information
I am unsure how best to deal with both of these. The FE guidelines
regarding Changelogs in
http://fedoraproject.org/wiki/Packaging/Guidelines only mentions spec
file specific changelog info, but says nothing about upstream. I do
think it is relevant to include upstream changelog also.
As an example, I have just bumped the heartbeat package in Fedora Extras
from 2.0.4-2 to 2.0.5-1. I ended up using a combination of minuses for
the package specific changelog entries and indented plusses for the
upstream changelog which seemed acceptable to rpmlint, as in:
%changelog
* Date Name Packager
- package changelog
+ upstream changelog
Example for heartbeat package:
%changelog
* Thu Apr 27 2006 Joost Soeterbroek <fedora(a)soeterbroek.com> - 2.0.5-1
- upstream version 2.0.5
- removed patch2 - ownership of /heartbeat/crm/cib.xml is no longer
set in cts/CM_LinuxHAv2.py.in
+ Version 2.0.5 - significant bug fixes and a few feature deficits fixed
+ various portability fixes
+ enable GUI to run with pygtk 2.4
+ significant GUI improvements and speedups
Comments,ideas?
Joost <fedora(a)soeterbroek.com>
17 years, 11 months
Something screwy with new glibc-kernheaders
by sean darcy
With glibc-kernheaders-3.0-18.x86_64.rpm I get thiss error
trying to build kino:
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -Wall
-I/usr/include/alsa -I/usr/include/libxml2 -pthread
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
-I/usr/include/libglade-2.0 -I/usr/include/gtk-2.0
-I/usr/include/libxml2 -I/usr/lib64/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/pango-1.0 -I/usr/include/ffmpeg
-D_FILE_OFFSET_BITS=64
-DKINO_PLUGINDIR=\""/usr/lib64/kino-gtk2"\"
-DDATADIR=\""/usr/share"\" -D_REENTRANT -O2 -fPIC
-funswitch-loops -fvisibility-inlines-hidden
-ftree-vectorize -march=k8 -pipe -mfpmath=sse
-frename-registers -MT jogshuttle.o -MD -MP -MF
".deps/jogshuttle.Tpo" -c -o jogshuttle.o jogshuttle.cc; \
then mv -f ".deps/jogshuttle.Tpo" ".deps/jogshuttle.Po";
else rm -f ".deps/jogshuttle.Tpo"; exit 1; fi
/usr/include/linux/input.h:803: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:807: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:808: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:809: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:810: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:811: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:812: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:813: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:814: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:815: error: 'kernel_ulong_t' does
not name a type
/usr/include/linux/input.h:817: error: 'kernel_ulong_t' does
not name a type
make[3]: *** [jogshuttle.o] Error 1
Going back to glibc-kernheaders-3.0-6.x86_64.rpm fixes it.
sean
17 years, 11 months
Beware of bash 3.1
by Callum Lerwick
Okay, I originally posted about this a few months ago:
http://www.redhat.com/archives/rhl-devel-list/2006-January/msg00491.html
A seemingly harmless corner case. Here's another one:
<BobJensen> one of my guys ran a java install script as sudo and fubar'd
the box
<BobJensen> he was following these instructions
http://fedorasolved.org/browser-solutions/java-i386/
Step 9, which looks like this:
cat <<EOF > /etc/profile.d/java.sh
export JAVA_HOME=/opt/jre1.5.0_06
export PATH=$JAVA_HOME/bin:$PATH
EOF
Results in this:
# cat /etc/profile.d/java.sh
export JAVA_HOME=/opt/jre1.5.0_06
export PATH=/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
Which is wrong. The fix is of course:
# cat <<EOF > ~/java.sh
> export JAVA_HOME=/opt/jre1.5.0_06
> export PATH=\$JAVA_HOME/bin:\$PATH
> EOF
# cat ~/java.sh
export JAVA_HOME=/opt/jre1.5.0_06
export PATH=$JAVA_HOME/bin:$PATH
So... bash 3.1 has definitely changed the way variable expansion is
done, namely it expands things it didn't used to expand. Bug or feature?
Either way, beware.
(And there's the larger issue, being that those instructions suck,
instead you should be using http://www.city-fan.org/tips/JpackageJava
which is linked from http://www.fedoraproject.org/wiki/JavaFAQ and thus
appears to be officially blessed. But that's not really an issue for
-devel...)
17 years, 11 months
kernel-2.6.16-1.2171_FC6 : "Cannot allocate memory"
by sean darcy
Using kernel-2.6.16-1.2171_FC6 on amd64. On boot, both ntpd
and nfsd fail:
Apr 29 14:14:13 localhost ntpdate[1877]:
sendto(127.127.1.0): Cannot allocate memory
Apr 29 14:15:30 localhost nfsd[1914]: nfssvc: Cannot
allocate memory
2.6.16-1.2153_FC6 works fine.
There some trick with the new kernel??
sean
17 years, 11 months
Q. about debugging/troubleshooting Thunderbird
by Philip Prindeville
I was trying to build an image of Thunderbird from the FC3 SRPM's, and
tweaked the .spec and sources to include a patch someone sent me and to
replace the --disable-debug in the config file with --enable-debug instead.
Unfortunately, when I run the build image, there's no sign at all of where
the output is going.
What am I missing?
If I kick off the process from the command line, and then do a "ps",
I see a couple of wrapper processes hanging around, and then the binary
itself as the youngest child process... Doing an "lsof" on that process
shows various .so's open, .jars, .msf's... sockets, etc... And yes, even the
controlling terminal. But the printf's don't seem to be going anywhere.
Any ideas?
Thanks,
-Philip
17 years, 11 months