Staging error - OSP

Hi all,
I was wondering if anyone familiar with the Oracle Software Packager (osp) software had run into the following error when trying to import Oracle 8i components into a new staging area:
Oracle Help for Java (Compressed)::
Oracle Help for Java (Compressed)::Staging Component "Oracle Help for Java (Compressed)"
Oracle Help for Java (Compressed)::Copying files from previous staging area
Oracle Help for Java (Compressed)::Finished copying compIns.jar
Oracle Help for Java (Compressed)::Finished copying CompRes.jar
Oracle Help for Java (Compressed)::Finished copying help jars
Oracle Help for Java (Compressed)::Finished copying DataFiles directory.
Oracle Help for Java (Compressed)::Updating inventory
Oracle Help for Java (Compressed)::Error : Library fileActions version 1.6.0.7.0 with a minimum installer version 1.5.0.0.0 not found.
Oracle Help for Java (Compressed)::Exception occurred during staging.
Any help or suggestions would be much appreciated.
Thanks!
Jon

I have not worked with osp but here ( http://otn.oracle.com/products/osp/index.html ) there is good papers about it. Perhaps in it you can find something useful for your task.
Joel P�rez

Similar Messages

  • Need info on Staging Error Tables ( Please Very urgent)

    Hi Friends,
    I am new to ERP. I need Information on Staging Error Tables in ERP. Please Let me know if anybody have an idea on this.
    Thanks

    I am new to ERP. I need Information on Staging Error Tables in ERP. Please Let me know if anybody have an idea on this.https://forums.oracle.com/forums/search.jspa?threadID=&q=Staging+AND+Tables&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
    Thanks,
    Hussein

  • Staging error adautostg.pl

    Hi Group, i am new to Oracle Apps,how can i reslove this error .
    D:\DVD-R Drive\Disk1\rapidwiz>perl adautostg.pl
    Failed to copy adautostg.pl to c:\temp\staging
    The log file is located at c:\temp\07261249\adautostaging.log
    Press <ENTER> to leave this session
    this will created a empty stage directory.
    What we can do to solve this problem?
    Thanks and Regards.
    sneha

    Looks like invalid "perl" program in use. To implement the solution, please execute the following steps:
    - Download Active Perl which is available at Active Perl
    http://www.activestate.com/store/activeperl/
    - Make sure that the environment is setup to use Active Perl:
    Type "which perl"
    If you don't get proper "perl" program, please add the location of your "perl" to the PATH variable.
    set PATH=<path to perl program>;%PATH%
    - Rerun "perl adautostg.pl"

  • Freevo - staging error

    Hi
    I tried installing Freevo from the staging repo - but got the following error:
    checking for file conflicts...
    error: the following file conflicts were found:
    usr/lib/perl5/site_perl/current/i686-linux-thread-multi/auto/Tk/pTk/extralibs. ld: exists in "perl-tk" (target) and "perl-tk-tablematrix" (target)
    errors occurred, no packages were upgraded.
    I am unsure about what it means - could someone clarify?

    murkus wrote:
    molinero wrote:
    Hi
    I tried installing Freevo from the staging repo - but got the following error:
    checking for file conflicts...
    error: the following file conflicts were found:
    usr/lib/perl5/site_perl/current/i686-linux-thread-multi/auto/Tk/pTk/extralibs. ld: exists in "perl-tk" (target) and "perl-tk-tablematrix" (target)
    errors occurred, no packages were upgraded.
    I am unsure about what it means - could someone clarify?
    I got the same error. I think that means that there is extralibs.ld in both perl-tk and perl-tk-tablematrix. The other already exists in your system and the other package isn't explicitly replacing it, creating confilct. Sadly, I can't do anything about it.
    .murkus
    By doing pacman -Sf freevo I got it to install. But now when trying to run, I get following:
    [12:43] murkus@
    [/home/murkus] # freevo
    Can't find all Python dependencies:
    No module named Image
    Not all requirements of Freevo are installed on your system.
    Please check the INSTALL file for more informations.
    .murkus

  • MF60 Material staging (Error E7021 by staging)

    Hi,
    I've tried to stage the components through the T.Code MF60. I get 100 pc in the storage location and I need 120 for my production order. I got an error(E7021) 20 pc shortfall.
    I would like to stage the available goods 100 pc in spite of the difference and get a warm message instead of an error.
    Thanks
    Dede

    Dear Dede,
    In MF60,under global settings select all the indicator except for Include all requirements.
    Execute and you will be able to stage the available 100 quantity.
    I guess you have not selected the indicator for Stock transfer requirement in the global settings.
    If this is not included means then directly the stock will be transffered from one storage location to
    another.If included means then only a stock transfer reservations gets generated.
    This Reservation no can be seen in MB25,and stock transfer can be made in MB1B for the reservation
    no.
    check and revert back.
    Regards
    Mangalraj.S

  • Need Information On R12 Error tables.

    Hi Friends,
    I need information on R12 Error Tables and Staging Error tables. Can you please send me any documention on this.
    Little bit urgent.
    Thanks

    Thanks for you Reply.
    Actually i am new to Apps. I am a OBIEE Developer. Here i will tell you the process. From Flat files to Staging area they are Loading the Data using some Scripts. After that they are using some concurrent programes for clensing the data and load them in to the Interface Tables. Then Those tables are loaded in to the Main oracle Tables.
    Mean while when they loading the data from staging to Interface they clensing the data. If Any errors occur they are moving those tables into some Built in Tables like (MTL_Interface_Errors). This is the process.
    And i don't know how to find the error tables..
    Thanks.
    Edited by: 806756 on Nov 9, 2011 1:34 AM

  • Issue w/ Case Differences Using the IBM Directory Server MA

    We have the following issue using the IBM Directory Server MA using FIM 2010 R2 (Version 4.1.3479.0).
    We provision a new object, e.g., uid=jdoe,ou=users,o=contoso, into an instance of IBM Directory Server
    The object is created in IBM Directory Server as uid=jdoe,ou=users,o=contoso
    A Full Import on the IBM Directory Server MA runs and confirms the export
    Subsequent imports, sync, and exports run successfully
    <Time passes>
    A Full Import on the IBM Directory Server MA runs, and this object shows up as a staging-error (uid=jdoe,ou=Users,o=contoso)
    Subsequent imports and syncs report errors on this object (staging-error)
    Note that we do not manipulate the anchor (DN) of this object once it is created in IBM Directory Server. Other attributes are synchronized, but the object is never renamed/moved. This case change does not happen with all of the objects brought
    in during the Full Import, but the number of instances do increase periodically. At this point, it does look like the import is changing from a lowercase "u" to an uppercase "U" but not vice versa.
    I found a related
    TechNet article containing the following remark:
    "IBM Directory Server does not guarantee that the case of a DN component will match in all instances. On a synchronization or import from IBM Directory Server, this can manifest itself as an unexpected update. For example, if you create
    O=TEST, and then create the user cn=MikeDan,O=TEST, this might be imported from IBM Directory Server as
    cn=MikeDan,O=test. Because of the case difference, FIM treats this as an update on subsequent full imports."
    Unfortunately, the article does not propose a resolution.
    Has anyone encountered this issue? More importantly has anyone resolved this or found an acceptable workaround?
    Note that deleting the connector space is not an acceptable workaround. :)

    I remember experiencing this issue when we were on 5.0, and I believe it persists through 5.1 as well.
    There is a comment in the 5.2 release notes that something similar was fixed:
    Changing case sensitive attribute values failed in MMR. (4624693)
    If I had to take a wild guess, I would say that the server does some internal checking to see if the value has changed, possibly based on the attribute syntax, to avoid replicating "changes" that really don't change anything except case. I doubt that all your custom attributes are case-sensitive, though. Enabling replication probably "turns on" this behavior, which doesn't go away even if replication is disabled.
    In any case, you're probably out of luck unless/until you upgrade to 5.2.

  • Problem building modules in kernel-2.6.29.6-rt

    Hi, im trying to compile 2.6.29.6 rt patched, and when i type
    make modules
    and i get this:
    CC [M] drivers/staging/agnx/pci.o
    drivers/staging/agnx/pci.c:426: aviso: inicialización desde un tipo de puntero incompatible
    CC [M] drivers/staging/agnx/xmit.o
    CC [M] drivers/staging/agnx/table.o
    CC [M] drivers/staging/agnx/sta.o
    CC [M] drivers/staging/agnx/phy.o
    drivers/staging/agnx/phy.c: En la función 'card_interface_init':
    drivers/staging/agnx/phy.c:936: aviso: el tamaño de marco de 4124 bytes es mayor que 1024 bytes
    LD [M] drivers/staging/agnx/agnx.o
    CC [M] drivers/staging/asus_oled/asus_oled.o
    CC [M] drivers/staging/at76_usb/at76_usb.o
    CC [M] drivers/staging/comedi/comedi_fops.o
    In file included from drivers/staging/comedi/comedidev.h:40,
    from drivers/staging/comedi/comedi_fops.c:45:
    drivers/staging/comedi/interrupt.h:27: error: tipos en conflicto para 'irqreturn_t'
    include/linux/irqreturn.h:14: nota: la declaración previa de 'irqreturn_t' estaba aquí
    En el fichero incluído de drivers/staging/comedi/comedidev.h:40,
    de drivers/staging/comedi/comedi_fops.c:45:
    drivers/staging/comedi/interrupt.h:30:1: aviso: se redefinió "IRQ_RETVAL"
    En el fichero incluído de include/linux/interrupt.h:10,
    de drivers/staging/comedi/interrupt.h:22,
    de drivers/staging/comedi/comedidev.h:40,
    de drivers/staging/comedi/comedi_fops.c:45:
    include/linux/irqreturn.h:15:1: aviso: esta es la ubicación de la definición previa
    make[3]: *** [drivers/staging/comedi/comedi_fops.o] Error 1
    make[2]: *** [drivers/staging/comedi] Error 2
    make[1]: *** [drivers/staging] Error 2
    make: *** [drivers] Error 2
    bash-4.0#
    Any idea?
    Last edited by B4RR13N705 (2009-07-16 16:46:46)

    It should not (depends how far you want to go). I just did a search and it seems that bug was introduced ~.5
    You can always try to build or disable this option from kernel config file.
    I don't use rt kernels and in -rc staging drivers just appeared. Because I don't use them, I de-select whole branch, so I don't have your problem. However even if I would enble this, I might not see your error as it seems related to other rt stuff.
    sorry that I can't help more.

  • How to import multi-value reference with Granfeldt PowerShell MA?

    Hi,
    I am trying to import multi-value reference into FIM (Group object).
    I can import all attributes from source SQL, except Multivalue reference (into members attribute on Group object).
    I have defined schema like this:
    $obj = New-Object -Type PSCustomObject
    $obj | Add-Member -Type NoteProperty -Name "Anchor-axs_profid|String" -Value ""
    $obj | Add-Member -Type NoteProperty -Name "objectClass|String" -Value "role"
    $obj | Add-Member -Type NoteProperty -Name "name|String" -Value ""
    $obj | Add-Member -Type NoteProperty -Name "member|Reference[]" -Value ""
    $obj
    On source attribute I have members defined in one attribute, divided by ",". 
    Import script:
    $Obj = @{}
    $Obj.Add("objectClass", "role")
    $Obj.Add("[DN]", "Role_"+$Object.$("axs_profid"))
    $Obj.Add("axs_profid", $Object.$("axs_profid").ToString())
    $Obj.Add("name", $Object.$("name").ToString())
    if($Object.$("member").ToString() -ne "")
    [string[]]$members = $Object.$("member").ToString().Split(',')
    $Obj.Add("member", $members)
    $Obj
    When Full import is triggered, I get following error for roles with multiple users:
    FIM Sync = staging-error
    Event log = 
    The server encountered an unexpected error in the synchronization engine:
     "BAIL: MMS(9588): d:\bt\32669\private\source\miis\shared\utils\libutils.cpp(7045): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\utils.cpp(229): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\nscsimp.cpp(5348): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\nscsimp.cpp(5753): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\nscsimp.cpp(686): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\csobj.cpp(12876): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\csobj.cpp(13976): 0x8023040e (The distinguished name is invalid)
    BAIL: MMS(9588): d:\bt\32669\private\source\miis\server\sqlstore\csobj.h(1252): 0x8023040e (The distinguished name is invalid)
    ERR_: MMS(9588): d:\bt\32669\private\source\miis\server\sync\syncstage.cpp(2018): ERR_: MMS(9588): d:\bt\32669\private\source\miis\server\sync\syncstage.cpp(612): ERR_: MMS(9588): d:\bt\32669\private\source\miis\server\sync\syncstage.cpp(647): Staging failed
    0x8023040e: [21]ERR_: MMS(9588): d:\bt\32669\private\source\miis\server\sync\syncmonitor.cpp(2528): SE: Rollback SQL transaction for: 0x8023040e
    Forefront Identity Manager 4.1.3559.0"
    If I change the script to return only first member:
    $Obj.Add("member", $members[0])
    import is successfull and I can see referenced member in Group.
    I have also tried to specify DN for both users and roles with the same outcome.
    $Obj.Add("[DN]", "Role_"+$Object.$("axs_profid"))
    I am using the latest version of  PSMA: 5.5
    Thanks for your help guys!

    I managed to solve this issue.
    The problem was in string array (I always appended "," at the end of each value). MA then expected another value after the last comma.
    The wrong approach:
    [string[]]$members = $Object.$("member").ToString().Split(',')
    The right approach:
    [string[]]$members = $Object.$("member").ToString().TrimEnd(',').Split(',')

  • Pacman is shitting a brick!

    I don't know what's going on but something is seriously a-bork:
    03:02:59 <+delysid|~> sudo pacman -Syu
    :: Synchronizing package databases...
    gnustep [/var/abs/gnustep.repo/] 100% LOCAL
    testing [################] 100% 1K 4.8K/s 00:00:00
    current [################] 100% 39K 51.5K/s 00:00:00
    extra [################] 100% 136K 223.0K/s 00:00:00
    unstable [################] 100% 1K 5.7K/s 00:00:00
    error: could not cwd to /tur/bfinch/: 550 /tur/bfinch/: No such file or directory
    failed to synchronize bfinch
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize contrasutra
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize deepfreeze
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize dp
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize hapy
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize kritoke
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize roberto
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize staging
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize twm
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize whatah
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize xentac
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize brice
    error: anonymous login failed
    Control socket read failed: Success
    failed to synchronize tpowa
    :: j2re-1.5.0_beta1-1: local version is newer
    :: j2sdk-1.5.0_beta1-2: local version is newer
    :: mplayer-1.0pre3.2-1: ignoring package upgrade (1.0pre4-1)
    :: prelink-20021002-2: local version is newer
    :: Above packages will be skipped. To manually upgrade use 'pacman -S <pkg>'
    Targets: binutils-2.15-1t1 cvsup-16.1h-2t1 glibc-2.3.3-1t1 initscripts-0.6-9
    iputils-021109-1t1 rhythmbox-0.8.3-1 sox-12.17.4-3
    Proceed with upgrade? [Y/n] y
    :: Retrieving packages from testing...
    error: anonymous login failed
    Control socket read failed: Success
    error: failed to retrieve some files from testing
    :: Retrieving packages from current...
    error: anonymous login failed
    Control socket read failed: Success
    initscripts-0.6-9 [################] 100% 7K 3.5K/s 00:00:02
    :: Retrieving packages from extra...
    error: anonymous login failed
    Control socket read failed: Success
    rhythmbox-0.8.3-1 [################] 100% 1206K 67.4K/s 00:00:17
    sox-12.17.4-3 [################] 100% 238K 56.7K/s 00:00:04
    After downloading those files it does not install them (presumably because it was unable to download some dependencies).
    I haven't seen any other posts about this so perhaps this problem just arose?

    tehdely wrote:
    dp, I actually went ahead and added that line as I didn't have one.  ( I always trash the pacman.conf.pacnew whenever pacman upgrades and keep my old one, so it's gotten a bit stale with the times, heh ).
    After I added it, it was able to sync and upgrade with all the main repositories.  TURs are still broken, however (perhaps the directory structure on the TUR server has changed?)
    Also how do I make wget less verbose, the interface was previously so nice and clean
    for wget i dont know anything else than
    -q for no output
    or
    -nv for only basic output

  • Still can't upgrade the system smoothly

    First of all, I'd like to apologize for disturbing you guys again about the wretched glibc update. I tried everything according to the wiki
    The grep '^lib/' /var/lib/pacman/local/*/files command gives me :-
    [hellknight@AX-64 ~]$ grep '^lib/' /var/lib/pacman/local/*/files
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-linux-x86-64.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libSegFault.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc.so.6
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm.so.6
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libmemusage.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpcprofile.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread.so.0
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv.so.2
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db-1.0.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db.so.1
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil-2.16.so
    /var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil.so.1
    [hellknight@AX-64 ~]$
    And, find /lib -exec pacman -Qo -- {} + command gives me
    error: cannot determine ownership of directory '/lib'
    error: cannot determine ownership of directory '/lib/firmware'
    error: No package owns /lib/firmware/sihp1018.dl
    error: cannot determine ownership of directory '/lib/modules'
    error: cannot determine ownership of directory '/lib/modules/2.6.36-ARCH'
    error: cannot determine ownership of directory '/lib/modules/2.6.36-ARCH/kernel'
    error: cannot determine ownership of directory '/lib/modules/2.6.36-ARCH/kernel/misc'
    error: cannot determine ownership of directory '/lib/modules/2.6.36-ARCH/misc'
    error: No package owns /lib/modules/2.6.36-ARCH/misc/vboxnetadp.ko
    error: No package owns /lib/modules/2.6.36-ARCH/misc/vboxdrv.ko
    error: No package owns /lib/modules/2.6.36-ARCH/misc/vboxnetflt.ko
    error: cannot determine ownership of directory '/lib/modules/3.2.6-1-ARCH'
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.builtin.bin
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.softdep
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.dep.bin
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.dep
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.symbols.bin
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.alias
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.devname
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.alias.bin
    error: No package owns /lib/modules/3.2.6-1-ARCH/modules.symbols
    error: cannot determine ownership of directory '/lib/modules/3.2.6-2-ARCH'
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.builtin.bin
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.softdep
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep.bin
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols.bin
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.devname
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias.bin
    error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight'
    error: No package owns /lib/modules/2.6.37-hellknight/modules.builtin.bin
    error: No package owns /lib/modules/2.6.37-hellknight/modules.softdep
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/arch'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/arch/x86'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu/cpufreq'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu/cpufreq/p4-clockmod.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu/cpufreq/powernow-k8.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu/cpufreq/mperf.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu/cpufreq/speedstep-lib.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/ext4'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/ext4/ext4.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/quota'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/quota/quota_tree.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/dlm'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/dlm/dlm.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/configfs'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/configfs/configfs.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/ocfs2'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/ocfs2/ocfs2_stackglue.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/ocfs2/dlmfs'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/ocfs2/dlmfs/ocfs2_dlmfs.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/ocfs2/cluster'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/ocfs2/cluster/ocfs2_nodemanager.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/ocfs2/ocfs2.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/fat'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/fat/vfat.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/fat/fat.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/fat/msdos.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/jbd2'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/jbd2/jbd2.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/fuse'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/fuse/fuse.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/mbcache.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/jbd'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/jbd/jbd.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/ext3'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/ext3/ext3.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/gfs2'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/gfs2/gfs2.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/fs/nls'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/fs/nls/nls_cp437.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/crypto'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/crypto/sha1_generic.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/crypto/crc32c.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/crypto/hmac.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/synth'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/synth/snd-util-mem.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/synth/emux'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/synth/emux/snd-emux-synth.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/core'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd-timer.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd-page-alloc.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/core/oss'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/oss/snd-pcm-oss.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/oss/snd-mixer-oss.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd-rawmidi.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/core/seq'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq-midi-emul.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq-midi.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq-virmidi.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq-dummy.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/core/seq/oss'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/oss/snd-seq-oss.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq-midi-event.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/seq/snd-seq-device.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd-hrtimer.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd-pcm.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/core/snd-hwdep.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-als4000.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-via82xx.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/cs5535audio'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/cs5535audio/snd-cs5535audio.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-sonicvibes.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/rme9652'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/rme9652/snd-hdsp.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/rme9652/snd-hdspm.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/rme9652/snd-rme9652.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-maestro3.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/lx6464es'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/lx6464es/snd-lx6464es.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/ice1712'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ice1712/snd-ice17xx-ak4xxx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ice1712/snd-ice1724.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ice1712/snd-ice1712.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/ymfpci'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ymfpci/snd-ymfpci.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/ca0106'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ca0106/snd-ca0106.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-intel8x0.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/emu10k1'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/emu10k1/snd-emu10k1x.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/emu10k1/snd-emu10k1-synth.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/emu10k1/snd-emu10k1.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-ad1889.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-atiixp.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-bt87x.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/nm256'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/nm256/snd-nm256.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-via82xx-modem.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/trident'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/trident/snd-trident.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-cmipci.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-rme32.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/pcxhr'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/pcxhr/snd-pcxhr.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-cs4281.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-intel8x0m.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/ac97'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ac97/snd-ac97-codec.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/korg1212'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/korg1212/snd-korg1212.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/ctxfi'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ctxfi/snd-ctxfi.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/hda'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-cirrus.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-idt.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-analog.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-si3054.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-conexant.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-hdmi.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-intel.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-via.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-realtek.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-cmedia.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/hda/snd-hda-codec-ca0110.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-azt3328.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-ens1371.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-es1968.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-cs5530.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-es1938.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/asihpi'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/asihpi/snd-asihpi.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-atiixp-modem.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-indigoiox.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-mia.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-mona.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-darla24.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-indigoio.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-gina20.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-indigo.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-layla20.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-indigodjx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-layla24.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-indigodj.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-echo3g.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-darla20.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/echoaudio/snd-gina24.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/oxygen'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/oxygen/snd-oxygen-lib.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/oxygen/snd-oxygen.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/oxygen/snd-hifier.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/oxygen/snd-virtuoso.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/mixart'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/mixart/snd-mixart.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/riptide'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/riptide/snd-riptide.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/ali5451'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/ali5451/snd-ali5451.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-als300.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-fm801.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/au88x0'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/au88x0/snd-au8810.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/au88x0/snd-au8830.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/au88x0/snd-au8820.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/cs46xx'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/cs46xx/snd-cs46xx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-ens1370.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pci/vx222'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/vx222/snd-vx222.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pci/snd-rme96.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/isa'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/isa/sb'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/isa/sb/snd-sb16-dsp.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/isa/sb/snd-sb-common.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/ac97_bus.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/soc'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/soc/snd-soc-core.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/usb'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/usb/usx2y'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/usb/usx2y/snd-usb-us122l.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/usb/usx2y/snd-usb-usx2y.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/usb/caiaq'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/usb/caiaq/snd-usb-caiaq.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/usb/snd-usb-audio.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/usb/snd-usbmidi-lib.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/usb/misc'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/usb/misc/snd-ua101.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/soundcore.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/i2c'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/snd-cs8427.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/i2c/other'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/other/snd-pt2258.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/other/snd-tea575x-tuner.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/other/snd-ak4113.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/other/snd-ak4114.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/other/snd-ak4xxx-adda.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/other/snd-ak4117.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/i2c/snd-i2c.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/drivers'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/drivers/snd-virmidi.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/drivers/opl3'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/drivers/opl3/snd-opl3-synth.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/drivers/opl3/snd-opl3-lib.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/drivers/vx'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/drivers/vx/snd-vx-lib.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/drivers/mpu401'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/drivers/snd-dummy.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pcmcia'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pcmcia/pdaudiocf'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pcmcia/pdaudiocf/snd-pdaudiocf.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/sound/pcmcia/vx'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/sound/pcmcia/vx/snd-vxpocket.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/misc'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/acpi'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/acpi/thermal.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/acpi/processor.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/acpi/button.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/acpi/container.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/parport'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/parport/parport_pc.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/parport/parport.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/pci'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/pci/hotplug'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/pci/hotplug/shpchp.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/pci/hotplug/pci_hotplug.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/common'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tuner-simple.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tuner-xc2028.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tda18271.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/xc5000.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tea5761.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tda827x.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/mxl5005s.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/mt20xx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tda8290.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tuner-types.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/mc44s803.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tea5767.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/common/tuners/tda9887.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/btcx-risc.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/v4l1-compat.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/em28xx'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/em28xx/em28xx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx18'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx18/cx18.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx18/cx18-alsa.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx231xx'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx231xx/cx231xx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx231xx/cx231xx-alsa.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/videobuf-dma-sg.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx2341x.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/v4l2-compat-ioctl32.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/tlg2300'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/tlg2300/poseidon.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/saa7134'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/saa7134/saa6752hs.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/saa7134/saa7134-empress.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/saa7134/saa7134.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/saa7134/saa7134-alsa.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx88'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx88/cx88-alsa.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx88/cx8800.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx88/cx88xx.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/v4l2-common.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/videobuf-dvb.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/tuner.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/tveeprom.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/videodev.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx25840'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cx25840/cx25840.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/videobuf-vmalloc.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/v4l2-int-device.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/cs5345.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/video/videobuf-core.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/IR'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/IR/ir-common.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/IR/lirc_dev.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/IR/ir-core.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/dvb'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/dvb/frontends'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/dvb/frontends/s5h1409.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/media/dvb/dvb-core'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/media/dvb/dvb-core/dvb-core.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/hid'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-logitech.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-belkin.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-chicony.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-ezkey.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-monterey.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-a4tech.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-kensington.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-apple.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/hid/usbhid'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/usbhid/usbhid.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-kye.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-cypress.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-microsoft.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hid/hid-cherry.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/usb'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/usb/core'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/usb/core/usbcore.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/usb/host'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/usb/host/ehci-hcd.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/usb/host/ohci-hcd.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/usb/storage'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/usb/storage/usb-storage.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/usb/gadget'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/usb/gadget/g_audio.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/usb/gadget/net2280.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/ata'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ata/libahci.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ata/libata.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ata/ahci.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ata/pata_acpi.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ata/pata_atiixp.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ata/ahci_platform.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/edac'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/edac/edac_mce_amd.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/edac/edac_core.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/hwmon'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/hwmon/k10temp.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/uio'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/uio/uio.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/video'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/video/via'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/video/via/viafb.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/cdrom'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/cdrom/cdrom.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/i2c'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/i2c/busses'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/i2c/busses/i2c-piix4.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/i2c/algos'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/i2c/algos/i2c-algo-bit.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/i2c/i2c-core.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/platform'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/platform/x86'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/platform/x86/wmi.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/input'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/input/evdev.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/input/misc'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/input/misc/pcspkr.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/input/ff-memless.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/cpufreq'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/cpufreq/cpufreq_ondemand.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/cpufreq/cpufreq_stats.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/cpufreq/freq_table.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/staging'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/staging/line6'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/staging/line6/line6usb.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/staging/tm6000'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/staging/tm6000/tm6000.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/staging/tm6000/tm6000-alsa.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/staging/cx25821'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/staging/cx25821/cx25821.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/staging/cx25821/cx25821-alsa.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/staging/go7007'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/staging/go7007/go7007.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/ide'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ide/ide-core.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/ide/ide-cd_mod.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/pcmcia'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/pcmcia/pcmcia_rsrc.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/pcmcia/pcmcia_core.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/pcmcia/pcmcia.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/net'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/net/cnic.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/net/mii.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/net/bnx2.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/net/r8169.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/block'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/block/pktcdvd.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/scsi'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/scsi_transport_iscsi.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/drivers/scsi/bnx2i'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/bnx2i/bnx2i.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/sr_mod.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/scsi_mod.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/sd_mod.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/scsi_wait_scan.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/scsi_transport_fc.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/libiscsi.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/drivers/scsi/sg.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/net'
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/net/sctp'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/net/sctp/sctp.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/net/ipv6'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/net/ipv6/ipv6.ko
    error: cannot determine ownership of directory '/lib/modules/2.6.37-hellknight/kernel/lib'
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/lib/libcrc32c.ko
    error: No package owns /lib/modules/2.6.37-hellknight/kernel/lib/crc16.ko
    error: No package owns /lib/modules/2.6.37-hellknight/modules.builtin
    error: No package owns /lib/modules/2.6.37-hellknight/modules.dep.bin
    error: No package owns /lib/modules/2.6.37-hellknight/modules.dep
    error: No package owns /lib/modules/2.6.37-hellknight/modules.symbols.bin
    error: No package owns /lib/modules/2.6.37-hellknight/modules.pcimap
    error: No package owns /lib/modules/2.6.37-hellknight/source
    error: No package owns /lib/modules/2.6.37-hellknight/modules.alias
    error: No package owns /lib/modules/2.6.37-hellknight/modules.devname
    error: No package owns /lib/modules/2.6.37-hellknight/modules.ccwmap
    error: No package owns /lib/modules/2.6.37-hellknight/modules.usbmap
    error: No package owns /lib/modules/2.6.37-hellknight/modules.ieee1394map
    error: No package owns /lib/modules/2.6.37-hellknight/modules.alias.bin
    error: No package owns /lib/modules/2.6.37-hellknight/modules.isapnpmap
    error: No package owns /lib/modules/2.6.37-hellknight/modules.seriomap
    error: No package owns /lib/modules/2.6.37-hellknight/modules.symbols
    error: No package owns /lib/modules/2.6.37-hellknight/modules.ofmap
    error: No package owns /lib/modules/2.6.37-hellknight/build
    error: No package owns /lib/modules/2.6.37-hellknight/modules.inputmap
    error: No package owns /lib/modules/2.6.37-hellknight/modules.order
    error: cannot determine ownership of directory '/lib/modules/3.1.9-2-ARCH'
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.pcimap
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ccwmap
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.usbmap
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ieee1394map
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.isapnpmap
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.seriomap
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ofmap
    error: No package owns /lib/modules/3.1.9-2-ARCH/modules.inputmap
    error: cannot determine ownership of directory '/lib/modules/3.0-ARCH'
    error: cannot determine ownership of directory '/lib/modules/3.0-ARCH/misc'
    error: No package owns /lib/modules/3.0-ARCH/misc/vboxnetadp.ko
    error: No package owns /lib/modules/3.0-ARCH/misc/vboxdrv.ko
    error: No package owns /lib/modules/3.0-ARCH/misc/vboxnetflt.ko
    error: No package owns /lib/modules/3.0-ARCH/misc/vboxpci.ko
    [hellknight@AX-64 ~]$
    Please help. I can't seem to understand what to delete and what not.

    did you care to read the appropriate wiki page completely?
    you compiled your own kernel, if you still want to use it, you need to rebuild it, If not, then simply delete it.

  • Error while loading metadata in HPCM application using Import Staging table

    Hello All,
    I was loading metadata in HPCM using Import Staging table. I successfully uploaded Driver Definition metadata.
    However while loading "Driver Exception" metadata, I am not able to load it successfully. I have checked the HPCM logs but found nothing. I then checked the "Import Exception" table and found the following error message.
    ERROR_POPULATED_DIM_COLUMNS_DO_NOT_MATCH_STAGE_DEFINITIONCan anyone please help me with this.
    Regards,
    -SM

    It is a bug and there is a patch available.
    Oracle Support - "Bug 12905298 : INTERFACE FAILS TO INTEGRATE ON STEP "LOAD DATA INTO PLANNING"
    Patch = 12905298: INTERFACE FAILS TO INTEGRATE ON STEP "LOAD DATA INTO PLANNING"
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error when deploying a mapping to Staging in OWB 11gr2

    Hi,
    I recieve the following error when I try to deploy a simple Source to Stage mapping:
    RPE-01012: Cannot deploy PL/SQL maps to this target schema. The target schema must be in the same instance as the Control Center and have the OWB_USER role granted.
    I have spent few hours researching it, but have not yet found a solution.
    My environment:
    DB 11gr2 on Red Hat Linux. (OWB Server is on linux and the same machine as its Repository and the 11gr2 db).
    Source is on an Oracle 10.2 DB server in Texas;
    Target (Staging env) is in California, also on Oracle 10.2.
    I can validate the mapping and the Staging table was deployed sucessfully to the Staging DB.
    Do I need to create a repository and workspace on the Target DB (Oracle 10.2) using Repository Assistant? (If that's the case, then would one also need to create OWBSYS?)
    Please help.

    This is an urgent request. Would appreciate it if someone could point out what I may be doing wrong.
    To summarize, my target DB is on Oracle 10.2 in a remote location, so I ran the 3 scripts that OWB Install documents require: Section: Configuring OWB Installed as a Standalone Instance.
    Cat_web.sql, reset_owbcc_home.sql, and remote_owb_install.sql.
    But, when I run the Repository assistant, I get the error above (asking me to install compatible OWB version.)
    Here are the detailed steps:
    1. Ran clean_owbsys.sql
    2. Ran cat_owb.sql (Against USERS Tablespace)
    3. reset_owbcc_home.sql (?? Ora home for Target???)
    4. Ran remote_owb_install.sql (??Ora Home for Target???) -- I have tried different combinations, but no difference.
    For Repository Assistant, here are the detailed steps:
    1. Provide connect info for the remote db (host:Port:Service)
    2. Selected "Managed Warehouse Build Workspaces"
    3. Selected "Create a new Warehouse Builder Workspace"
    4. Select "Create a workspace with an existing user as workspace owner" (Since we have user already defined for this role. Should I create a new one??)
    5. Entered Workspace Owner's User Name, Password and created WKS1 as the Workspace.
    6. Entered System / and Password to logon
    7. Provided Owbsys user id and Password and clicked on Next
    8. As soon as I hit Next on the OWBSYS Information screen, I get the error:
    "OWB software with the compatible version must be installed locally on the database server machine". If it is installed, acquire the DBA user credentials,
    and run the remote_owb_install.sql script on the Oracle Database server machine..."
    (I have tried with different paths for the reset_owbcc_home and remote_owb_install scripts)

  • Error while passing HCM-Staging Data to Identity Center

    Hello
    We are implementing IDM 7.1 SP2 and using HCM-Integrations Scenario.
    The extracting scenario over vds into the HR-Staging are is working fine.
    We do have troubles while running the task  270/Write HCM Employee To SAP Master .
    There we get always the error "sap_getSysUname Par: [20090210-99991231]<PERNR>!![20090210-
    99991231] Invalid SyUname: [20090210-99991231] does not exist or is
    not valid todayPass stopped by script.
    We have checked the OSS Note 1308250 - it doesn't helped - it justed hide the error message.
    We have checked with debbuging the hr - data . The field syuname is filled and delivered.
    a.) does anybody knows about this problem or can give some tipps to fix this error?
    b.) we have a lot of jobs with errors know in the job qeue - we can stop them, but not delete or cancel?
    anybody knows how to kill the jobs in IDM 7.1 ?
    kind regards, Reto

    Hi,
        I was not able to use the new VDS Template 'HCM LDAPEXTRACT to IDM' because it was causing a problem while integrating with HCM and IDM. Hence I have used the old template 'HR Export to IDM Identity Center' which seems to be working fine.
        But since the reprot RPLDAP_EXTRACT_IDM pushes the records with the time part prefixed, and that I'm not able to use the new VDS Template which has a job HR_Staging_Area  which performs the job of pushing the HCM data from Staging to Productive Identity Store. Since I see that you have implemented it, it will be of great help if you can share the steps and details of how to use the new VDs template and the jobs related to it.

  • Oracle 8.1.5 Invalid Staging Area Error

    I get an error message: Invalid staging area. There is no top level components for Windows NT available for installing
    from this staging area. I installed this version successfully running win98, but i get this error with XP. I tried renaming the symcjit.dll
    as suggested in some of the earlier posting with no success. Any help is appreciated.
    Thanks,
    Will

    copy disk to hardrive in a temporary directory. go to properties for setup.exe (right click on file used to install oracle). Select the compatiblity tab. make sure the check box "run this program in compatibility mode" is checked. In combo box select windows 98.

Maybe you are looking for