Originally Posted by twaelti

Please check the maemo wiki for an article about py2deb!

Originally Posted by LABAUDIO

OK TX TX TX a lot BrentDC

binutils instaled...

Now all work very good

after launch the script, all is create

but...

in my .deb in final, no sounds .wav is in....

iam shure its cause maybe 2 think

-i have a syntax error in my script...
-or my .wav sounds is not in good folder for be passed into deb when script work...

so here my script again

Code:

#!/bin/sh

# This script should be run from within the directory with the wav files.

# First, create the empty tree under a new "build" directory
# (the name "build" is completely arbitrary here)
mkdir -p build/usr/share/sounds/

# Put the sounds in the sounds directory
cp -v ui-*.wav build/usr/share/sounds/

# move into the build directory, make a docs directory
cd build
mkdir -p usr/share/doc/themevista

# write the README file
cat > usr/share/doc/themevista/README <<END
This package provides replacement sound effects for Maemo.

It moves the original sounds aside using dpkg-divert(8), and 
restores them upon uninstallation.
END

# write the control file
cat > control <<END
Package: ThemeVista
Version: 3.1
Section: user/themes
Priority: optional
Architecture: all
Installed-Size: `du -ks usr|cut -f 1`
Maintainer: Alex Vevey <Alex-vevey@hotmail.com>
Description: New Maemo sound effects (Vista Style), with auto-backup of the originals
 
 This package contains a set of sound effects for the OSSO Maemo ui. This
 version will preserve your current sounds using dpkg-divert(8) and
 restore them upon uninstallation.
 
 Updates to this package might be posted at
 Alex Vevey-Alex-vevey@hotmail.com
END

# write the pre-installation script
cat > preinst <<END
#!/bin/sh
if [ "$1" = install ]; then
    for f in ui-battery_low.wav ui-charging_started.wav ui-confirmation_note.wav ui-connection_lost.wav ui-default_beep.wav ui-general_warning.wav ui-gesture_number_recognized.wav ui-information_note.wav ui-key_press.wav ui-new_email.wav ui-operation_ready.wav ui-pen_down.wav ui-recharge_battery.wav ui-shutdown.wav ui-thumb_keyboard_launch.wav ui-wake_up_tune.wav ui-window_close.wav ui-window_open.wav ui-wrong_charger.wav; do
        dpkg-divert --themevista --rename --add /usr/share/sounds/$f
    done
fi
END

# write the post-removal script
cat > postrm <<END
#!/bin/sh
if [ "$1" = remove ]; then
    for f in ui-battery_low.wav ui-charging_started.wav ui-confirmation_note.wav ui-connection_lost.wav ui-default_beep.wav ui-general_warning.wav ui-gesture_number_recognized.wav ui-information_note.wav ui-key_press.wav ui-new_email.wav ui-operation_ready.wav ui-pen_down.wav ui-recharge_battery.wav ui-shutdown.wav ui-thumb_keyboard_launch.wav ui-wake_up_tune.wav ui-window_close.wav ui-window_open.wav ui-wrong_charger.wav; do
        dpkg-divert --themevista --rename --remove /usr/share/sounds/$f
    done
fi
END

# Setting this environment variable fixes Apple's modified GNU tar so that
# it won't make dot-underscore AppleDouble files. Google it for details...
export COPY_EXTENDED_ATTRIBUTES_DISABLE=1

# create the data tarball
# (the tar options "czvf" mean create, zip, verbose, and filename.)
tar czvf data.tar.gz usr/share/sounds/ usr/share/doc/

# create the control tarball
tar czvf control.tar.gz control preinst postrm

# create the debian-binary file
echo 2.0 > debian-binary

# create the ar (deb) archive
ar -r themevista.deb debian-binary control.tar.gz data.tar.gz

# move the new deb up a directory
mv themevista.deb ..

# remove the tarballs, and cd back up to where we started
rm data.tar.gz control.tar.gz
cd ..

maybe the path for sounds is not good
or my sounds is not in the good folder when i try packaged...

TX to help me
iam almost

Originally Posted by jolouis

Hey LAB, you can try to narrow the problem down a bit by doing some troubleshooting.
1) Does the build/usr/share/sounds directory that the script creates actaully contain any sound files after you've finished running the script (the script cleans up the .tar.gz's it makes, but not your build directories so they should still be there). If not, it's probably a path/file location problem
2) If #1 is ok, next step is to check to see if your data.tar.gz file actually had the sound files in it. Go into your script and place a # sign infront of the second last line that reads

Code:

rm data.tar.gz control.tar.gz

Then run the script, go to your "build" directory, and issue

Code:

 tar -tf data.tar.gz

And see if it lists any files.