We have installed a package called xen-utils on our Debian Squeeze box.

Now we have applied a patch to the xen-utils package. The patch adds 3 shell-scripts to the package.

The problem is, the new package installs everything correctly except the 3 shell scripts created by the patch.

We have applied the patch correctly. When we call dpkg-buildpackage -b -uc -us to build the package, a log file reports that the shell-scripts have been created. They reside in a directory called,
/home/walter/workdir/xen-4.0.1/debian/build/install-utils_amd64/etc/xen/scripts

This looks right--

but when I install the package the scripts are not moved from

/home/walter/workdir/xen-4.0.1/debian/build/install-utils_amd64/etc/xen/scripts

to

/etc/xen/scripts

Any ideas why those scripts are not being moved?

I would like to know how you think the installation will move those scripts from their default location?

Good question. What I mean is, how do I indicate the 3 files I want to install, located in ..[install-utils].../etc/xen/scripts, so that they are included in the package?

For example, below I copy output from dkpg-deb -c MY_PACKAGE. You can see, directories under /usr have been included.

Somewhere, I should think, there must be a rule or statement indicating that files in the path cited above, ...install-utils_PATH... should be included in the package.

Where do I add that rule or otherwise ensure that those files are to be included also?


walter@vm2:~/workdir$
walter@vm2:~/workdir$ sudo dpkg-deb -c xen-utils-4.0_4.0.1-4_amd64.deb
drwxr-xr-x root/root 0 2012-02-29 15:11 ./
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/boot/
-rw-r--r-- root/root 431832 2012-02-29 15:11 ./usr/lib/xen-4.0/boot/hvmloader
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/
-rw-r--r-- root/root 9462 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/libflask.a
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/ufs/
-rw-r--r-- root/root 7760 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/ufs/fsimage.so
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/zfs/
-rw-r--r-- root/root 23536 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/zfs/fsimage.so
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/reiserfs/
-rw-r--r-- root/root 12624 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/reiserfs/fsimage.so
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/iso9660/
-rw-r--r-- root/root 7344 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/iso9660/fsimage.so
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/ext2fs-lib/
-rw-r--r-- root/root 13640 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/ext2fs-lib/fsimage.so
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/fat/
-rw-r--r-- root/root 9040 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/fs/fat/fsimage.so
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/python/
-rw-r--r-- root/root 171 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/python/xen-3.0.egg-info
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/python/xen/
-rw-r--r-- root/root 2 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/__init__.py
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/python/xen/sv/
-rw-r--r-- root/root 2 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/__init__.py
-rw-r--r-- root/root 2777 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/Main.py
-rw-r--r-- root/root 2453 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/NodeInfo.py
-rw-r--r-- root/root 3007 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/util.py
-rw-r--r-- root/root 7955 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/CreateDomain.py
-rw-r--r-- root/root 9115 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/Wizard.py
-rw-r--r-- root/root 1401 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/HTMLBase.py
-rw-r--r-- root/root 1615 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/RestoreDomain.py
-rw-r--r-- root/root 9486 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/DomInfo.py
-rw-r--r-- root/root 4954 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/sv/GenTabbed.py
drwxr-xr-x root/root 0 2012-02-29 15:11 ./usr/lib/xen-4.0/lib/python/xen/remus/
-rw-r--r-- root/root 0 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/remus/__init__.py
-rw-r--r-- root/root 2056 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/remus/util.py
-rw-r--r-- root/root 8782 2010-08-29 16:13 ./usr/lib/xen-4.0/lib/python/xen/remus/netlink.py

...

Usually you would add "new files to be installed" to 'rules', I guess.

In xen(-4.0.1) it seems to be "rules.real" > xen_4.0.1-4.debian.tar.gz
> > http://ftp.de.debian.org/debian/pool....debian.tar.gz

http://packages.debian.org/source/squeeze/xen

.

Thanks very much--if rules proves better I will use that. In the meantime, on the same level (under debian/), I appear to have solved the problem by adding a file of name {PACKAGE_NAME}.install containing a single line:

/etc/xen/scripts/{domain-lock,vm-monitor}


In brackets are the names of the 2 files I needed to install; the 3rd file is a separate problem.

yes that {package_name].install file did the trick, now testing shows.

and as for copying the third file, that was accomplished in the makefile for the utility,

with a simple line: cp $(DEST_DIR)$(XEN_SCRIPT_DIR)/vm-monitor $(DEST_DIR)$(XEN_SCRIPT_DIR)/set-lock