Problem with binary package and dupload
-----BEGIN PGP SIGNED MESSAGE-----
I first put this on debian-devel and was told it should be moved here.
I finally have my first package functioning and ready to upload.
The dupload program, however, claims that I don't have anything to upload,
so I figure I've misread the manual and have done something wrong in my
.changes files. I'm attaching one of them here. If someone can see
what I messed up, please let me know.
The package is a binary-only package, released with no changes in source
code. There are four parts to the package, totalling 45 megs worth of
.debs. The original files were obtained from the NOAO site in 512k chunks
(which is how they're stored there). They were reconstructed into .tar.gz
files by catting them together on my local hard drive, and the original
chunks deleted. Binaries were stripped, and permissions changed to match
the policy guidelines. Some freebsd-specific files were deleted. No
other changes were made. My understanding was that for such a binary
package the only files that needed uploading were the compiled .deb and
the .changes file for it. Dupload doesn't like the changes file listed
below. It returns the following:
Uploading (ftp) to
master.debian.org:/home/Debian/ftp/private/project/Incoming/
[ job iraf-common_2.11.1-1 from iraf-common_2.11.1-1.changes
announce (iraf-common_2.11.1-1.changes) to
debian-devel-changes@lists.debian.org will be sent: not a changes file ]
Nothing to upload
=============================================================================
Zed Pobre <zcp@po.cwru.edu> | PGP key on servers, fingerprint on finger
=============================================================================
Format: 1.5
Date: Sat Mar 7 18:58:39 CST 1998
Source: iraf-common
Binary: iraf-common
Architecture: i386
Version: 2.11.1-1
Distribution: unstable
Priority: optional
Urgency: low
Maintainer: Zed Pobre <zed@debian.org>
Description: IRAF - Common files/sources
These are the IRAF support files common across all architectures.
In theory, it should be possible to completely rebuild the entire IRAF
binary system from these files. In practice, it may be a little more
difficult.
Changes:
Initial upload
Files:
e0146bb9811e91553db0b73e6a9f6b2d 16467642 contrib/misc optional iraf-common_2.11.1-1.deb
-----BEGIN PGP SIGNATURE-----
Version: 5.0
Charset: noconv
iQEVAwUBNQMDWdwPDK/EqFJbAQGPfwgAlCdLOK9U/RfrTM7B+ML/KG1HSQzvOREM
nkhfPYrmPAnjfzpFFvwFML2Gai8IAVxHqiNGGGTiceVk84c1kuCQ4JpddN4u9V4d
H9Jc6a1zGRgQ/jaygx6+mbK5TEh45pz5mba4Ds9buzpls4i78iqBeW+nUIHdwAWp
bRgxCpiaKBUJp+g8fX4x/E4TgdrdMsfAitUejC/thtqpd4fb+fvlGTd3PMfoGF3K
3Jlb/tSU/lXo7hQt5Jnuhmqd2yakE3ZlO9/y4QY29vPMWQoo+eVhDGfYpSmwN4Ql
cqWZWFHf3eNOtRiKTUIEDChd8P23ukD8NO/2T8DR2itkM0u8wz5VYg==
=XYu7
-----END PGP SIGNATURE-----
Reply to: