Hi Olivier,

This is the version of debhelper that I have on my ubuntu12.04.
> root@dikim-virtual-machine:~# dpkg -l |grep debhelper
> ii  debhelper                                    9.20120115ubuntu3            
>                     helper programs for debian/rules
> ii  dh-apparmor                                  2.7.102-0ubuntu3.7           
>                     AppArmor debhelper routines

BTW, I think I fixed the apitest building issue in a temporary solution
I tried to comment out the following lines (149-152) in /usr/bin/packman
>         #if ($rc == ERROR) {
>         #    die "ERROR: Impossible to install " . join (", ", @pkgs) . " ("
>         #        . join ("\n", @output) . ")";
>         #}


OK. the problem came from "smart_install" in PackMan.pm (e.g., "($rc, @output) 
= $pm->smart_install(@pkgs)") because the current smart_install of PackMan does 
not take care of the deb and it does not know what to do and returns an error.

If we do not really use smart_install for deb-based system, why don't we update 
"packman" to check if the system is deb-based or not? If it is a deb-based 
system, let "packman" ignore the implementation of "smart_install".

I would like to dig into more how a deb-based system manages the 
installation/dependency process.
 
Regards,

--
- DongInn

On Jun 13, 2013, at 4:35 AM, LAHAYE Olivier <olivier.lah...@cea.fr> wrote:

> 
> Hi DongInn,
> 
> Excellent news! I see that most important stuffs are here for building 
> everything except oscar-packager.
> 
> I'm fixing some build dependancies on systemimager and other packages on 
> ubuntu-12.10, so I assume that this may help on ubuntu-12.04...
> 
> Note also that I've fixed a few thinks on systemimager (upstream). (Added 
> (per request) support for including /lib/firmware in generated initramfs 
> images by using --include-system-firmware and --firmware-dir= options) (not 
> yet tested)
> 
> Fixed build dependancies on jobmonarch for debian side and rhel side as well.
> 
> Still have a problem on rhel side for jobmonarch. the postinstall uses 
> apache.apache as file owners, and our ganglia package uses root.root 
> in/usr/share/ganglia. I need to fix this upstream....
> 
> As for you dependancies problem, I saw that you installed debian-7 rapt and 
> depedancies, and this may be the source of your dependacies problems (needs 
> debhelper deb6 vs debhelper deb7) (just suppositions).
> 
> IMHO, now that you've successfully created a debian-6-x86_64 repo, I would 
> restart from scratch using this repo.
> 
> BTW, before starting from scratch, what is your debhelper installed version?
> dpkg -l |grep debhelper
> oscar-packager requires debhelper >= 8
> 
> Olivier.
> 
> -- 
>    Olivier LAHAYE
>    CEA DRT/LIST/DCSI/DIR
> De : DongInn Kim [di...@cs.indiana.edu]
> Date d'envoi : jeudi 13 juin 2013 00:18
> À : oscar-devel@lists.sourceforge.net
> Objet : Re: [Oscar-devel] Packaging build process on the debian-base system
> 
> OK, building process seems to be OK but I still have several packages not 
> built.
> 
> BTW, I think that there is a problem with sync_files + oscar-utils.
> 
>> root@cutter:/var/log# apt-get install sync-files
>> Reading package lists... Done
>> Building dependency tree       
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>> 
>> The following packages have unmet dependencies:
>>  sync-files : Depends: oscar-utils (>= 6.1.2) but 6.1.2~svn20130306-0ol1 is 
>> to be installed
>> E: Unable to correct problems, you have held broken packages.
>> root@cutter:/var/log# 
> 
> I have already oscar-utils 6.1.2 - svn version installed but it seems that 
> the dependency was not properly setup on sync_files?
> 
> BTW, debian-6-x86_64 repository is now available for ubuntu 12.04. :-)
> http://svn.oscar.openclustergroup.org/repos/unstable/debian-6-x86_64/
>  
> Regards,
> 
> --
> - DongInn
> 
> On Jun 12, 2013, at 5:52 PM, DongInn Kim <di...@cs.indiana.edu> wrote:
> 
>> OK, I just used the one in the OSCAR repository and it seems to be working 
>> fine.
>> http://svn.oscar.openclustergroup.org/repos/unstable/debian-7-x86_64/
>> 
>> Regards,
>> 
>> --
>> - DongInn
>> 
>> On Jun 12, 2013, at 5:44 PM, DongInn Kim <di...@cs.indiana.edu> wrote:
>> 
>>> Hi Olivier,
>>> 
>>> How did you get over the "rapt" dependency issue?
>>> 
>>>> dikim@dikim-virtual-machine:/tmp/oscar_build$ sudo dpkg -i *.deb(Reading 
>>>> database ... 204198 files and directories currently installed.)
>>>> Preparing to replace opkgc 1.0.2-1 (using opkgc_1.0.2-1_all.deb) ...
>>>> Unpacking replacement opkgc ...
>>>> Selecting previously unselected package oscar-packager.
>>>> Unpacking oscar-packager (from oscar-packager_1.1.0-1_all.deb) ...
>>>> Preparing to replace packman 3.2.0-1 (using packman_3.2.0-1_all.deb) ...
>>>> Unpacking replacement packman ...
>>>> Setting up opkgc (1.0.2-1) ...
>>>> dpkg: dependency problems prevent configuration of oscar-packager:
>>>> oscar-packager depends on rapt; however:
>>>>  Package rapt is not installed.
>>>> dpkg: error processing oscar-packager (--install):
>>>> dependency problems - leaving unconfigured
>>>> Setting up packman (3.2.0-1) ...
>>>> Processing triggers for man-db ...
>>>> Processing triggers for python-central ...
>>>> Errors were encountered while processing:
>>>> oscar-packager
>>>> dikim@dikim-virtual-machine:/tmp/oscar_build$ sudo apt-get install rapt
>>>> Reading package lists... Done
>>>> Building dependency tree       
>>>> Reading state information... Done
>>>> Package rapt is not available, but is referred to by another package.
>>>> This may mean that the package is missing, has been obsoleted, or
>>>> is only available from another source
>>>> 
>>>> E: Package 'rapt' has no installation candidate
>>>> dikim@dikim-virtual-machine:/tmp/oscar_build$ ls
>>>> opkgc_1.0.2-1_all.deb  oscar-packager_1.1.0-1_all.deb  
>>>> packman_3.2.0-1_all.deb
>>>> dikim@dikim-virtual-machine:/tmp/oscar_build$
>>> 
>>> It seems that it is not available on ubuntu 12.04.
>>> 
>>> Regards,
>>> 
>>> --
>>> - DongInn
>>> 
>>> On Jun 12, 2013, at 12:28 PM, LAHAYE Olivier <olivier.lah...@cea.fr> wrote:
>>> 
>>>> 
>>>> You need to install debian package build tools:
>>>> 
>>>> apt-get install dpkg-dev
>>>> 
>>>> Then you should have the dpkg-buildpackage command available.
>>>> 
>>>> Olivier.
>>>> 
>>>> --
>>>>  Olivier LAHAYE
>>>>  CEA DRT/LIST/DCSI/DIR
>>>> 
>>>> ________________________________________
>>>> De : DongInn Kim [di...@cs.indiana.edu]
>>>> Date d'envoi : mercredi 12 juin 2013 18:17
>>>> À : LAHAYE Olivier
>>>> Cc: Devel OSCAR
>>>> Objet : Re: Packaging build process on the debian-base system
>>>> 
>>>>> 1: build oscar base:
>>>>> svn co https://svn.oscar.openclustergroup.org/svn/oscar/trunk oscar
>>>>> cd oscar
>>>>> make deb
>>>> ..
>>>> ./packages/nfs/config.xml
>>>> ./packages/nfs/configurator.html
>>>> ./packages/nfs/doc/
>>>> ./packages/nfs/doc/README
>>>> ./CREDITS
>>>> ./tmp/
>>>> /bin/sh: 6: dpkg-buildpackage: not found
>>>> make: *** [basedebs] Error 127
>>>> dikim@dikim-virtual-machine:~/oscar/trunk$
>>>> 
>>>> I got this error.
>>>> 
>>>> Any idea of this?
>>>> 
>>>> 
>>>> Regards,
>>>> 
>>>> --
>>>> - DongInn
>>>> 
>>>> On Jun 12, 2013, at 12:13 PM, LAHAYE Olivier <olivier.lah...@cea.fr> wrote:
>>>> 
>>>>> 
>>>>> hi dongInn,
>>>>> 
>>>>> Do you mean bootrapping the oscar-packager from scratch?
>>>>> 
>>>>> I did the following on fedora17 and ubuntu-12.10
>>>>> 
>>>>> 1: build oscar base:
>>>>> svn co https://svn.oscar.openclustergroup.org/svn/oscar/trunk oscar
>>>>> cd oscar
>>>>> make deb
>>>>> apt-get install ../*.deb
>>>>> 
>>>>> 2: build opkgc, packman and oscar-packager
>>>>> svn co https://svn.oscar.openclustergroup.org/svn/oscar/pkgsrc
>>>>> cd pkgsrc/opkgc/trunk
>>>>> dpkg-buildpackage -b -uc -us
>>>>> mv ../*.deb /tmp
>>>>> 
>>>>> cd ../../packman/trunk
>>>>> dpkg-buildpackage -b -uc -us
>>>>> mv ../*.deb /tmp
>>>>> 
>>>>> cd ../../oscar-packager/trunk
>>>>> dpkg-buildpackage -b -uc -us
>>>>> mv ../*.deb /tmp
>>>>> 
>>>>> apt-get install /tmp/*.deb
>>>>> 
>>>>> 3: configure oscar repository
>>>>> oscar-config --setup-distro ubuntu-1204-x86_64
>>>>> 
>>>>> 4: use oscar-packager as usual......
>>>>> oscar-packager --debug --verbose --all unstable.
>>>>> 
>>>>> Those steps are from memory and is the way I would go when starting from 
>>>>> a blank system with no existing repository.
>>>>> Of course, you'll rebuild all the above package with oscar-packager to 
>>>>> make sur that no optional deps were forgotten.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Olivier.
>>>>> --
>>>>> Olivier LAHAYE
>>>>> CEA DRT/LIST/DCSI/DIR
>>>>> 
>>>>> ________________________________________
>>>>> De : DongInn Kim [di...@cs.indiana.edu]
>>>>> Date d'envoi : mercredi 12 juin 2013 17:38
>>>>> À : LAHAYE Olivier
>>>>> Cc: Devel OSCAR
>>>>> Objet : Packaging build process on the debian-base system
>>>>> 
>>>>> Hi Olivier,
>>>>> 
>>>>> Can you please help to bring me back to the right track to build the 
>>>>> OSCAR packages on the deb-based system?
>>>>> 
>>>>> I am working on Ubuntu12.04-server X86_64.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> --
>>>>> - DongInn
>>>>> 
>>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Windows:
>>> 
>>> Build for Windows Store.
>>> 
>>> http://p.sf.net/sfu/windows-dev2dev
>>> _______________________________________________
>>> Oscar-devel mailing list
>>> Oscar-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>> 
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>> 
>> Build for Windows Store.
>> 
>> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
>> Oscar-devel mailing list
>> Oscar-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oscar-devel
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> Oscar-devel mailing list
> Oscar-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to