Jan Hlodan wrote:
> Hello,
> 
> I need to edit package SUNWslim-utils (add translated strings for
> Desktop Icons in LiveCD)
> This package can be found in
> "/net/paradise.sfbay/export/integrate_dock/nv/nv_osol0811/i386"
> I am able to extract "SUNWslim-utils/archive/none.bz2" :
> 
> sh-3.2# bunzip2 none.bz2
> sh-3.2# cpio -id < none
> 195 blocks
> sh-3.2# ls
> jack  lib  none  sbin  usr  var
> 
> and edit files in "SUNWslim-utils/archive/jack/Desktop/*"
> (ddu.desktop, install_opensolaris.desktop, getting_started.desktop,
> opensolaris-license.desktop).
> But I have problem to publish these files into localhost repository as
> a IPS package.
> 
> I think that easier way is edit files (ddu.desktop,
> install_opensolaris.desktop, getting_started.desktop,
> opensolaris-license.desktop) via 'mc' (it allows me edit 'none'
> archive directly, I don't have to unpack it first) and then publish
> SVR4 package as a usual.
> But I always get error message like this:
> 
> 
> sh-3.2# eval `pkgsend open SUNWslim-utils at 0.5.11,5.11-0.101`
> sh-3.2# pkgsend import SUNWslim-utils
> Traceback (most recent call last):
>   File "/usr/bin/pkgsend", line 350, in ?
>     ret = main_func()
>   File "/usr/bin/pkgsend", line 325, in main_func
>     trans_import(pcfg, pargs)
>   File "/usr/bin/pkgsend", line 276, in trans_import
>     action)
>   File "/usr/lib/python2.4/vendor-packages/pkg/publish/transaction.py",
> line 101, in add
>     datastream = action.data()
>   File "/usr/lib/python2.4/vendor-packages/pkg/actions/generic.py",
> line 118, in file_opener
>     return open(data, "rb")
> IOError: [Errno 2] No such file or directory:
> 'SUNWslim-utils/reloc/jack/Desktop/getting_started.desktop'
> sh-3.2#
> 
> I don't know why I get this error, because directory 'reloc' was
> already empty at the beginning.
> I guess that checksum or pkgmap don't match...
> Can you help me please, how to update pkgmap and pkginfo files or how
> to recreate SVR4 package?
> 

The package is built from the caiman sources, which are in the 
caiman/slim_source hg repo.  You'll likely find it far simpler to pull a 
clone of that and follow the short instructions to build it.

Dave

Reply via email to