This may seem obvious to some, but makes no sense to me. Why is it that mkisofs has a different release number (-1mdk) than the other packages built from it? Release needs to be incremented for all of them when it is rebuilt for any reason. it is annoying (and potentially confusing to end users) enough that the changelog for the binary RPM reflects the cdrecord, as opposed to mkisofs, version without the release number also being out of sync.
On a side note, can we get the zisofs patch (included in ftp://ftp.kernel.org/pub/linux/utils/fs/zisofs/zisofs-tools-1.0.1.tar.bz2) applied to this? With the zisofs kernel option going into the Linus tree in 2.4.14 and already in the ac kernels, this could be useful :) (We would also need a zisofs-tools package to generate the compressed tree to make compressed ISO's from) -- Anton Graham GPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request Outside of a dog, a book is man's best friend. Inside of a dog, it is too dark to read.
