Thanks Agustin.
I noticed both dapl packages, 1.2.4 and 2.0.6 are from the ofed kit. Are
both provided by the ofed kit?
-Liming
March, Agustin M wrote:
Liming,
Yes, both packages came from the same packages.
lrwxrwxrwx 1 root root 62 Mar 27 16:12
/depot/repos/1000/Server/dapl-1.2.1.1-6.el5.i386.rpm ->
../../../kits/rhel/5/x86_64/Server/dapl-1.2.1.1-6.el5.i386.rpm
lrwxrwxrwx 1 root root 79 Mar 27 16:13
/depot/repos/1000/Server/dapl-1.2.4-0.285.ofed20080207.x86_64.rpm ->
../../../kits/ofed/1.3/noarch/dapl-1.2.4-0.285.ofed20080207.x86_64.rpm
lrwxrwxrwx 1 root root 79 Mar 27 16:13
/depot/repos/1000/Server/dapl-2.0.6-0.286.ofed20080207.x86_64.rpm ->
../../../kits/ofed/1.3/noarch/dapl-2.0.6-0.286.ofed20080207.x86_64.rpm
lrwxrwxrwx 1 root root 68 Mar 27 16:12
/depot/repos/1000/Server/dapl-devel-1.2.1.1-6.el5.i386.rpm ->
../../../kits/rhel/5/x86_64/Server/dapl-devel-1.2.1.1-6.el5.i386.rpm
lrwxrwxrwx 1 root root 85 Mar 27 16:13
/depot/repos/1000/Server/dapl-devel-1.2.4-0.285.ofed20080207.x86_64.rpm
->
../../../kits/ofed/1.3/noarch/dapl-devel-1.2.4-0.285.ofed20080207.x86_64
.rpm
lrwxrwxrwx 1 root root 85 Mar 27 16:13
/depot/repos/1000/Server/dapl-devel-2.0.6-0.286.ofed20080207.x86_64.rpm
->
../../../kits/ofed/1.3/noarch/dapl-devel-2.0.6-0.286.ofed20080207.x86_64
.rpm
lrwxrwxrwx 1 root root 92 Mar 27 16:13
/depot/repos/1000/Server/dapl-devel-static-1.2.4-0.285.ofed20080207.x86_
64.rpm ->
../../../kits/ofed/1.3/noarch/dapl-devel-static-1.2.4-0.285.ofed20080207
.x86_64.rpm
lrwxrwxrwx 1 root root 92 Mar 27 16:13
/depot/repos/1000/Server/dapl-devel-static-2.0.6-0.286.ofed20080207.x86_
64.rpm ->
../../../kits/ofed/1.3/noarch/dapl-devel-static-2.0.6-0.286.ofed20080207
.x86_64.rpm
lrwxrwxrwx 1 root root 85 Mar 27 16:13
/depot/repos/1000/Server/dapl-utils-1.2.4-0.285.ofed20080207.x86_64.rpm
->
../../../kits/ofed/1.3/noarch/dapl-utils-1.2.4-0.285.ofed20080207.x86_64
.rpm
lrwxrwxrwx 1 root root 85 Mar 27 16:13
/depot/repos/1000/Server/dapl-utils-2.0.6-0.286.ofed20080207.x86_64.rpm
->
../../../kits/ofed/1.3/noarch/dapl-utils-2.0.6-0.286.ofed20080207.x86_64
.rpm
Regards,
Agustin
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Tsai Li Ming
Sent: Thursday, March 27, 2008 2:40 PM
To: Users of Kusu
Subject: Re: [Kusu-users] [RPM LIST]
Agustin,
Both packages are from the same kit?
Could you do a ls -l on /depot/repos/1000/Server/dapl-*.rpm?
Thanks,
Liming
March, Agustin M wrote:
Hi Liming,
This is the ouput
[EMAIL PROTECTED] ~]# rpm -qp
/depot/repos/1000/Server/dapl-2.0.6-0.286.ofed20080207.x86_64.rpm
--qf="%{NAME} %{EPOCH} %{VERSION} %{RELEASE}\n"
dapl (none) 2.0.6 0.286.ofed20080207
[EMAIL PROTECTED] ~]# rpm -qp
/depot/repos/1000/Server/dapl-1.2.4-0.285.ofed20080207.x86_64.rpm
--qf="%{NAME} %{EPOCH} %{VERSION} %{RELEASE}\n"
dapl (none) 1.2.4 0.285.ofed20080207
Regards,
Agustin
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Tsai Li Ming
Sent: Thursday, March 27, 2008 12:39 PM
To: Users of Kusu
Subject: Re: [Kusu-users] [RPM LIST]
Hi Agustin,
It could be a bug in repoman. To help me isolate this, can you run the
following on both packages:
rpm -qp <pkg> --qf="%{NAME} %{EPOCH} %{VERSION} %{RELEASE}\n"
-Liming
March, Agustin M wrote:
Hi,
Yes, there two packages with different version of the same
architecture. Is it possible to select on of them? So, How Could I
select, the ngedit does not allow it?
One example of this is the ofed package 1.3, the following packages
are
in the repo
dapl-1.2.4-0.285.x86_64.rpm
dapl-2.0.6-0.286.x86_64.rpm
Regards,
Agustin
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Tsai Li Ming
Sent: Wednesday, March 19, 2008 10:50 PM
To: Users of Kusu
Subject: Re: [Kusu-users] [RPM LIST]
Hi
Are there more than 1 rpm of the same package name in the repo,
Nmame?
You can find the packages using:
/depot/repos/<repoid> -name "*<pkg name>*"?
repoid can be found using "repoman -l".
You can use rpm -qa | grep or rpm -qi to identify the packages once
they
are installed.
HTH,
Liming
March, Agustin M wrote:
Hi,
I am working with external packages from KUSU and some kits
distribution. So, I would to add to compute nodes, so I did the
following but without success.
Because, I could not identify the correct rpm name used by the kusu
in
the packages tables.
cp *.rpm /depot/kit/somekitassociatedtoaRepo/
repoman -u -r "Nmame"
insert the rpm name into the database.
Since, there two version of the same name packages, kusu installs
both.
Is there any way to identify those package in the kusu?
Thank you
Agustin March <mailto:[EMAIL PROTECTED]>
Argentina Distributing Computing Solution
+54 351 5265618
Intel Argentina S.A.
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
