Hi Olivier,
How did you manage the torque build on FC-17?
> [root@fedora noarch]# rpm -ivh drmaa-python-0.5-2.noarch.rpm
> error: Failed dependencies:
> libdrmaa.so.0()(64bit) is needed by drmaa-python-0.5-2.noarch
> [root@fedora noarch]#
It seems that torque requires drmaa-python but I can not install it without
libdrmaa.so.0 which is available in torque-drmaa.
It seems that I can install the torque-drmaa package that FC-18 provides but it
looks odd that we are building a torque package which are already available on
a distro. I understand that we need to build a customized torque package for
OSCAR though.
Anyway, I tried to proceed further by install torque-drmaa which is provided in
FC-18 but the oscar-packager process still failed with blcr-devel dependencies.
> [root@fedora fc-17-x86_64]# rpm -ivh blcr-devel-0.8.5-1.x86_64.rpm
> blcr-libs-0.8.5-1.x86_64.rpm
> error: Failed dependencies:
> libc.so.6 is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.0) is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.1) is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.1.3) is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.15) is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.3.2) is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.3.4) is needed by blcr-libs-0.8.5-1.x86_64
> libc.so.6(GLIBC_2.4) is needed by blcr-libs-0.8.5-1.x86_64
> libdl.so.2 is needed by blcr-libs-0.8.5-1.x86_64
> libdl.so.2(GLIBC_2.0) is needed by blcr-libs-0.8.5-1.x86_64
> libdl.so.2(GLIBC_2.1) is needed by blcr-libs-0.8.5-1.x86_64
> libpthread.so.0 is needed by blcr-libs-0.8.5-1.x86_64
> libpthread.so.0(GLIBC_2.0) is needed by blcr-libs-0.8.5-1.x86_64
> libpthread.so.0(GLIBC_2.1) is needed by blcr-libs-0.8.5-1.x86_64
> libpthread.so.0(GLIBC_2.3.2) is needed by blcr-libs-0.8.5-1.x86_64
> [root@fedora fc-17-x86_64]#
How did you solve the libc dependencies?
Regards,
--
- DongInn
On Apr 2, 2013, at 1:36 PM, DongInn Kim <di...@cs.indiana.edu> wrote:
> Hi Olivier,
>
> Thanks a lot for doing this.
>
> I was off for a while and probably I can play a little with the new
> oscar-packager later today.
>
> Regards,
>
> --
> - DongInn
>
> On Apr 2, 2013, at 1:22 PM, LAHAYE Olivier <olivier.lah...@cea.fr> wrote:
>
>>
>> Hi,
>>
>> I've fixed many problems in oscar-packager. It still need some work, but
>> I've progressed a lot.
>> - Fixed the fact that a package could be built up to 5 times (example
>> torque).
>> - Support for multiple source files in package.cfg using the {} syntax.
>> (downloading was already working as the wget was called using the shell),
>> but then the copy routing failed trying to copy the last source with a
>> trailing }.
>> - Fixed the fact that if an rpm is not build from src.rpm, options defined
>> in the build.cfg were ignored.
>>
>> It's almost done, I need to do the following:
>>
>> - Check if there is a way to avoid triggering the "make rpm" if the build is
>> successfull.
>> - fix the new torque package failing to build on fedora. (a strange man is
>> generated but unpackaged).
>>
>> After these 2 fixes, the rpmside of oscar-packager should be working as
>> expected.
>> For the debian side, it should be ok, but I'll give a look to see if we can
>> enhance it.
>>
>> For those who were curious on what was going on the multiple build, here is
>> the explanation:
>>
>> The multiple build was very tricky to understand. What was occuring was the
>> following:
>> When the torque package was about to be built, the prepare_prereqs called by
>> create_package called by do_packaging did build the torque rpms one time for
>> the noarch architecture and one time for the binary architecture..
>> Undortunately it forgot to specify the --target, thus both build we doing
>> the same binary build: 2 build (build method: SVN triggered friom
>> /etc/oscar/oscar-packager/included_unstable.cfg)
>>
>> Then, another call to prepare_prereqs was done elswhere (build methode
>> TARBALL) with the same 2 build again.(after looking at the torque-oscar.cfg
>> file).
>>
>> Then, once the prereqs were satisfied (we are at 4 build now) the make rpm
>> (line 368) was triggered missing the the build.cfg options and resulting in
>> the same binary rpms.
>>
>> At the end provided that the build was successfull, we eneded up with 5
>> build of the binary rpms and 0 build of the noarch rpms.
>>
>> Bes regards,
>>
>> Olivier.
>> --
>> Olivier LAHAYE
>> CEA DRT/LIST/DCSI/DIR
>> ------------------------------------------------------------------------------
>> Minimize network downtime and maximize team effectiveness.
>> Reduce network management and security costs.Learn how to hire
>> the most talented Cisco Certified professionals. Visit the
>> Employer Resources Portal
>> http://www.cisco.com/web/learning/employer_resources/index.html_______________________________________________
>> Oscar-devel mailing list
>> Oscar-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
