I have also been working in my spare time on packaging rssowl for FC5
[sic]. I can post my .spec file if wanted. Here's my list of unfixed
libgcj bugs that need to be fixed before rssowl will run natively
reliably. These are both threading bugs.
"Thread.interrupt sometimes causes abort if thread is already dead"
This gets hits about 25%-50% of the time on quitting rssowl, and
occassionaly also when I press the little red stop button at the bottom of
the window. I can provide a backtrace if wanted.
Unfortunately rssowl only saves any changes upon quit, so this means
that any changes (including preferences and even the record of which feed
items have been read) will be lost 25-50% of the time - unacceptable,
"AttachCurrentThread() not working"
This is an old bug. It only triggered for me once I rebuilt gcc for
Athlon (32bit) with a private threading patch, but now it triggers 100% of
the time, every time I try to view the Dilbert comic in rssowl. Again,
backtrace available on request. I am convinced that it is a real bug in
the existing code, not a bug in my patch. After all, bad memory accesses
don't always trigger SIGSEGVs. Sometimes they just cause memory
corruptions. So probably, previously it was just causing memory
corruptions instead of SIGSEGVs for some subtle reason.
Feel free to add to this list.
From what I can tell, Fedora Core 4 provides a very good Java 1.4.2
development environment. The one thing that I cannot find is Java API
documentation (the equivalent of JPackage's java-1.4.2-sun-manual).
Have I just missed it, or is it not available?
Ian Pilcher i.pilcher(a)comcast.net
I came across a weird issue while trying to build rssowl. I've attached
the test file. Trying this works:
while this appears to hang:
ecj -encoding utf8 RSSOwlI18nZHtw.java
I can reproduce this behaviour on both an x86 box running an Eclipse 3.1
ecj (built myself) and on a ppc box running Eclipse 3.1 RC3 (the RPMs we
have in rawhide). Using Sun's javac (on the x86 box) does not hang when
I use "-encoding utf8". All are FC4 machines (with gcc*-4.0.0-11 in the
x86 case and gcc*-4.0.0-13 in the ppc case).
To add to the bizarre-ness, this appears to be as small as I can make
the test file without it being unable to reproduce the problem; I can't
seem to remove any of the lines if I want to continue to reproduce. In
another interesting twist, renaming the file (and class) to "TestUTF8"
does not reproduce the problem.
Anyone know what's going on?
Those of you who are interested in JOnAS might like to know that
the version I just built, jonas-4.3.3-1jpp_3fc, actually a) runs
and b) serves pages! It's very crunchy at the moment, but any
testing will be sorely appreciated.
1. When you try and start it note that "service jonas start"
never returns control to the shell so you'll have to tail
/var/log/jonas/jonas to see when it's started. Look for
a message like "The JOnAS Server 'jonas' version 4.3.3 is
2. It locks up during startup fairly frequently. If the last
line in /var/log/jonas/jonas is "jmx service started" or
"jtm service started" then you probably want to kill it
and have another go.
3. You may get a load of database errors. If so, try removing
dbm from jonas.services in /etc/jonas/jonas.properties and
uninstalling the jonas-examples rpm.
4. "service jonas stop" doesn't seem to work, but the server
can be halted quickly and easily by trying to look at the
memory graph in the admin application.
Ville Skyttä wrote:
> IMO that would be too much dictating local policies from our part, and
> subject to inherent distributed bitrot because folks usually download
> jpackage.repo only once. And I'm sure this stuff would not be limited
> to postgresql-jdbc.
I don't understand your argument. Are you saying that the file can
never be changed? Probably, it should be put into it's own package
in the Fedora repos.
There's a larger question here. What is the "co-existence strategy"
for JPackage and Fedora Core? I'm trying to figure out how to set up
a Java development/Tomcat server environment on FC4, and I'm very
unsure how to set things up so that yum doesn't eventually leave me with
an incompatible mishmash of JPackage (Java) and Fedora (gcj) packages.
> Maybe the FC postgresql-jdbc package could have a versioned Provides:
> using the full version number (including the build) of the drivers it
> contains, like the corresponding JPP one has in its version field?
> Would that work the way you'd expect? (What would you expect, BTW?)
Getting the Fedora postgresql-jdbc package to somehow reflect the
version of the driver would be a good start. I'm not sure how to do
this, though. I haven't had great luck getting responses to bugs that
I put into Red Hat's bugzilla, let alone RFEs.
There's also the fact that the Fedora package contains multiple builds
of the driver, for use with multiple JVM versions; the JPackage package
only contains a single build (JDBC 3?). So even if the JPackage RPM
were updated to a later driver version, there's a case for not replacing
the Fedora package.
Out of curiosity, what distributions *don't* include the PostgreSQL
JDBC drivers? (I.e. why does the JPackage RPM exist?)
Ian Pilcher i.pilcher(a)comcast.net
I know it shouldn't be done, but we ran Eclipse as root. It seemed to
freeze the whole system, mouse pointer, keyboard input etc... No kernel
panic was produced and Eclipse runs fine as a normal user. Is this well
known behaviour for eclipse?
School of Computing, Mathematics and Information Sciences,
University of Brighton.
On 6/28/05, Build System <buildsys(a)redhat.com> wrote:
Please fix so I can have my cup of java :D
yum groupinstall "Eclipse"
--> Running transaction check
--> Processing Dependency: java-1.4.2-gcj-compat =
0:184.108.40.206-40jpp_30rh for package: java-1.4.2-gcj-compat-devel
--> Finished Dependency Resolution
Error: Missing Dependency: java-1.4.2-gcj-compat =
0:220.127.116.11-40jpp_30rh is needed by package java-1.4.2-gcj-compat-devel
fedora-test-list mailing list
This is a reminder of the mailing lists for the Fedora Project, and
the purpose of each list. You can view this information at
When you're using these mailing lists, please take the time to choose
the one that is most appropriate to your post. If you don't know the
right mailing list to use for a question or discussion, please contact
me. This will help you get the best possible answer for your question,
and keep other list subscribers happy!
Mailing lists are email addresses which send email to all users
subscribed to the mailing list. Sending an email to a mailing list
reaches all users interested in discussing a specific topic and users
available to help other users with the topic.
The following mailing lists are available. To subscribe, send email to <listname>-request(a)redhat.com
(replace <listname> with the desired mailing list name such as
fedora-list) with the word subscribe in the subject.
fedora-announce-list - Announcements of changes and events. To stay
aware of news, subscribe to this list.
fedora-list - For users of releases. If you want help with a problem
installing or using , this is the list for you.
fedora-test-list - For testers of test releases. If you would like to
discuss experiences using TEST releases, this is the list for you.
fedora-devel-list - For developers, developers, developers. If you are
interested in helping create releases, this is the list for you.
fedora-extras-list - For users and developers of Fedora Extras
fedora-docs-list - For participants of the docs project
fedora-desktop-list - For discussions about desktop issues such as user
interfaces, artwork, and usability
fedora-config-list - For discussions about the development of
fedora-tools-list - For discussions about the toolchain (gcc, gdb,
etc...) within Fedora
fedora-devel-java-list - For discussions about Java-related Fedora
fedora-patches-list - For submitting patches to Fedora maintainers, and
used in line with BugWeek
fedora-legacy-announce - For announcements about the Fedora Legacy
fedora-legacy-list - For discussions about the Fedora Legacy Project
fedora-selinux-list - For discussions about the Fedora SELinux Project
fedora-marketing-list - For discussions about marketing and expanding
the Fedora user base
fedora-de-list - For discussions about Fedora in the German language
fedora-es-list - For discussions about Fedora in the Spanish language
fedora-ja-list - For discussions about Fedora in the Japanese language
fedora-i18n-list - For discussions about the internationalization of
fedora-trans-list - For discussions about translating the software and
documentation associated with the Fedora Project
Brazilian Portuguese: fedora-trans-pt_br
Simplified Chinese: fedora-trans-zh_cn
Traditional Chinese: fedora-trans-zh_tw
> I did a yum upgrade and it gave me new jonas and jonas-client packages.
> And they work!
> At least the /jonasAdmin things work (after guessing the user/password).
> I can even add new http connectors (although https doesn't seem to work
> yet) and query lots of the installed MBeans. As you said the graphs
> don't work yet and seem to crash the server since it tries to access our
> AWT gtk+ peers that want a Display connected. We need to figure out how
> to work in headless mode for server-side things.
Sun Java has the same problem, they added to 1.4 the system property java.awt.headless. Whatever you
do using Fedora / gcj / classpath should be compatible, using the same property.
s, Fernando Lozano