CentOS - Mar 2005 - dag

Hi,

    After setting up dag.repo in /etc/yum.repo, and tried yum update, yum
will try to update my system from dag even it is originally from centos.org.
The reason for us to choose CentOs instead of Fedora is the stability of the
OS. And the reason of getting pacakages from dag is there is something we
need, which is not offered by CentOs. If dag packages will overwritten
CentOs, surprises may arises.

    Is there a method that yum only update packages from CentOs if it is
originally from CentOs, and update from dag if it is originally from dag?

Jason

On Mon, Mar 21, 2005 at 12:57:40PM +0800, Jason enlightened
us:
>    After setting up dag.repo in /etc/yum.repo, and tried yum update, yum
> will try to update my system from dag even it is originally from
> centos.org. The reason for us to choose CentOs instead of Fedora is the
> stability of the OS. And the reason of getting pacakages from dag is there
> is something we need, which is not offered by CentOs. If dag packages will
> overwritten CentOs, surprises may arises.
>
>    Is there a method that yum only update packages from CentOs if it is
> originally from CentOs, and update from dag if it is originally from dag?
>
The best way to currently do this is to disable the dag repo in your
dag.repo file.

[dag]
...
enabled=0

When you need to install a package from the dag repository, you can enable
it on the command line

yum --enablerepo=dag install foobar

Matt

--
Matt Hyclak
Department of Mathematics
Department of Social Work
Ohio University
(740) 593-1263
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.caosity.org/pipermail/centos/attachments/20050321/f48914ce/attachment.bin

Thank you.

Jason

----- Original Message -----
From: "Matt Hyclak" <hyclak@math.ohiou.edu>
To: <centos@caosity.org>
Sent: Monday, March 21, 2005 2:15 PM
Subject: Re: [Centos] dag

> _______________________________________________
> CentOS mailing list
> CentOS@caosity.org
> http://lists.caosity.org/mailman/listinfo/centos
>

Hi,

I''m fiddling around with the CentOS 4 installation, and I _thought_ I
had instructed the installer to add Java as well.

Doing a: rpm -qa | grep java

Shows:
java-1.4.2-gcj-compat-1.4.2.0-26jpp
gcc-java-3.4.3-9.EL4

Yet, when trying to call javac, it cannot be found on the system...

When doing:  find / -name "javac" -print

Indeed nothing is found :(

Can anyone tell me how to properly set it up, and also, can anyone tell
me which PATH and CLASSPATH settings need to be set/changed in order to
get the base classes etc. found?

Cheers!
Olafo

the rpms you have are the gcc java compiler. They are not
''standard''
java compiler.
the java runtime is j2re (yum search j2re)
if you want to compile, look for a java sdk (jdk at sun''s website)

Sophana

Olaf Greve wrote:
> Hi,
>
> I''m fiddling around with the CentOS 4 installation, and I
_thought_ I
> had instructed the installer to add Java as well.
>
> Doing a: rpm -qa | grep java
>
> Shows:
> java-1.4.2-gcj-compat-1.4.2.0-26jpp
> gcc-java-3.4.3-9.EL4
>
> Yet, when trying to call javac, it cannot be found on the system...
>
> When doing:  find / -name "javac" -print
>
> Indeed nothing is found :(
>
> Can anyone tell me how to properly set it up, and also, can anyone
> tell me which PATH and CLASSPATH settings need to be set/changed in
> order to get the base classes etc. found?
>
> Cheers!
> Olafo
>
> _______________________________________________
> CentOS mailing list
> CentOS@caosity.org
> http://lists.caosity.org/mailman/listinfo/centos
>

Hi,
> the rpms you have are the gcc java compiler. They are not
''standard''
> java compiler. the java runtime is j2re (yum search j2re)
> if you want to compile, look for a java sdk (jdk at sun''s website)
Thank you very much. Meanwhile, I myself have simply downloaded the
Linux rpm from the Sun site. I downloaded the file
j2sdk-1_4_2_07-linux-i586-rpm.bin
Set the permission to executable (as root), ran it, and the added the
resulting rpm by doing a "rpm -i j2sdk-1_4_2_07-linux-i586-rpm".

Alright, so far, so good, but....

I think my CLASSPATH settings are not quite hunky-dorey, as I keep
getting Exceptions like the following:
********************************************************************
Exception in thread "main" com.thales_rts.splice.ClassError: Class
java.lang.String does not contain any fields which can be accessed.
Accessable fields must be defined public and non-static.
    at
com.thales_rts.splice.TypeDescriptor.getAccessableFields(java.lang.Class)
(Unknown Source)
********************************************************************

My classpath is set in /etc/profile to be:
/usr/java/j2sdk1.4.2_07/lib/dt.jar:/usr/java/j2sdk1.4.2_07/lib/tools.jar:/usr/java/j2sdk1.4.2_07/jre/lib/rt.jar

At a later stage, this is extended with the .jars for the actual
applications...

Can anyone tell me whether the above CLASSPATH setting ought to be
correct, or whether I''m missing something...?

Cheers!
Olafo

PS: Sorry for such basic questions, but I have to get this machine set
up by tomorrow, and my Java knowledge is rather rusty (as I pretty much
haven''t used it for some 5 years or so)...

Hi,

Yesterday I wrote:
> I think my CLASSPATH settings are not quite hunky-dorey, as I keep
> getting Exceptions like the following:
> ********************************************************************
> Exception in thread "main" com.thales_rts.splice.ClassError:
Class
> java.lang.String does not contain any fields which can be accessed.
> Accessable fields must be defined public and non-static.
>    at
> com.thales_rts.splice.TypeDescriptor.getAccessableFields(java.lang.Class)
> (Unknown Source)
> ********************************************************************
>
> My classpath is set in /etc/profile to be:
>
/usr/java/j2sdk1.4.2_07/lib/dt.jar:/usr/java/j2sdk1.4.2_07/lib/tools.jar:/usr/java/j2sdk1.4.2_07/jre/lib/rt.jar
I partially figured out what the issue is: it seems there are issues
with JDK 1.4.2 installations....

I installed version 1.3.1_15 (next to the 1.4.2_07 which has the issues)
and everything now seems to work a charm (for both installations I later
simply left the CLASSPATH variable empty.

Has anyone else encountered such issues with JDK 1.4.2?
I remember that last year on a Debian machine we also had similar
issues. That machine was not installed by me though, so I don''t kow
exactly how that got solved...

Cheers!
Olafo