The problem is that there is difference between the upstream tarballs of the two versions.
In version 1.1.1~bzr20081010 (the one currently in intrepid) the tests/data/deb is a symlink to aptdeb/dists/component/binary-i386, while in version 1.2 (the target of this SRU) tests/data/deb is actually a directory, which has however the very same contents as aptdeb/dists/component/binary-i386. I'm going to check with the upstream developers if this was intentional or not.
The problem can be fixed manually by replacing the symlink with a copy of its target directory, but as far as I know these changes are not representable in a diff, so I'm attaching the diff.gz and .dsc to be used against the smart_1.2.orig.tar.gz tarball already in karmic/jaunty. This new attachment also fixes the Maintainer field.
The problem is that there is difference between the upstream tarballs of the two versions.
In version 1.1.1~bzr20081010 (the one currently in intrepid) the tests/data/deb is a symlink to aptdeb/ dists/component /binary- i386, while in version 1.2 (the target of this SRU) tests/data/deb is actually a directory, which has however the very same contents as aptdeb/ dists/component /binary- i386. I'm going to check with the upstream developers if this was intentional or not.
The problem can be fixed manually by replacing the symlink with a copy of its target directory, but as far as I know these changes are not representable in a diff, so I'm attaching the diff.gz and .dsc to be used against the smart_1. 2.orig. tar.gz tarball already in karmic/jaunty. This new attachment also fixes the Maintainer field.