…bian.org/debian-backports/dists/sarge-backports/contrib/binary-i386/Packages while the Release file uses MD5Sum. Some programs like apt-mirror are case sensitive and break when confronted with MD5Sum in a Packages file. (Thanks for the consistency debian.)
Current behavior of freight-add treats the first unrecognized file type as the beginning of the repositories. Common build artifacts, like .build and .changes files are unrecognized by freight and cause freight-add to prematurely begin collecting repositories. This can cause problems if those files are in the directory being imported and a glob like * or package_* is used. This patch seeks to address that by recognizing .build and .changes files, but doing nothing with them.
The $package_debian.tar.gz format is the new and shiny format (3.0 - http://www.infodrom.org/Debian/doc/maint/Maintenance-pkgbuild.html). To quote briefly: A Debian source package usually consists of three files: .dsc containing meta information about the source package .diff.gz containing all patches that Debian applied to the package or .debian.tar.gz containing all patches that Debian applied to the package (new source format 3.0) .orig.tar.gz containing the pristine upstream source tarball Freight doesn't currently handle debian.tar.gz style diffs. This commit seeks to address that by, during apt_source_cache checking for a debian.tar.gz file and if not found, falling back to a diff.gz file. It also changes the behavior of freight-add to discover and link these files as with other debian package files.