[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: .changes files without source packages

Le Fri, Dec 03, 2010 at 06:08:42PM -0800, Daniel Lazzari a écrit :
> /eme-assets
> /eme-assets/DEBIAN
> /eme-assets/DEBIAN/control
> /eme-assets/DEBIAN/postinst
> /eme-assets/DEBIANprerm
> /eme-assets/opt
> /eme-assets/opt/image.jpg
> /eme-assets/opt/libmine.so
> I package it up using "dpkg -b eme-assets eme-assets_2.0.1.8936_i386.deb"
> This gives me a debian package I can install, but there is no .changes file.
> Hope that provides a little better picture of what I'm trying to do.

dpkg-genchanges was designed to be run in an unpacked source package after
binary packages were built. It therefore expects files like debian/changelog
or debian/files.

Perhaps the fastest way for you to get a .changes file for mini-dinstall is
to write a script that creates one from scratch. The format is simple
and explained in the Debian policy, section 5.5:


Something along these lines:

# Your package

# Informations about your package in DEBIAN/control
ARCH=$(grep Architecture $CONTROL | sed 's/Architecture: //')
VERS=$(grep Version $CONTROL | sed 's/Version: //')
DESC=$(grep Description $CONTROL | sed 's/Description: //')
DATE=$(date -R)
MAINT=$(grep Maintainer $CONTROL | sed 's/Maintainer: //')

# The binary package

# The changes file
cat <<CHANGES > ${PACK}_${VERS}_${ARCH}.changes
Format: 1.8
Date: $DATE
Source: $PACK
Binary: $PACK
Architecture: $ARCH
Version: $VERS
Distribution: unstable
Maintainer: $MAINT
Description: $DESC
 $PACK (${VERS}) unstable; urgency=low
  * New release
 $(md5sum $DEB | cut -f1 -d' ') $(ls -l $DEB | cut -f5 -d' ') $(basename $DEB)

Note that since I do not know how complex is your realy system, this may be
too simplistic…

Another solution would be to make a proper source package.


Charles Plessy
Tsurumi, Kanagawa, Japan

Reply to: