> In sarge, we have 0.13.4-5. This version is not a development version, > it is just horribly outdated.
Oh, ok I was probably just confused about it, I thought Ben was using an odd second number in the version to indicate the development branch. I would image you know better than me on that. > > The current stable and unstable branches don't play nice together, as > > other bug reporters have reported. > > You mean, rdiff-backup stable and unstable release. But.. the one remaining > in testing is just a question of time before it is replaced by the migrated > sid version. So, there is no rdiff-backup stable release in debian (except > sarge, but sarge does not ship the current stable release of rdiff-backup > either). So what is actually the problem then? Yes, the development (1.1.5) doesn't play nice with the stable (1.0.3), I was unclear. The problem is that rdiff-backup in Debian in incompatible with rdiff-backup in other distros (like Gentoo) that use the stable branch. I run sarge, but I'm trading backups with a friend running Gentoo, so I did an apt-get source to create up to date packages so we wouldn't be using much different versions, and it was a surprise to find out they still didn't work together because Debian doesn't use the stable branch. That's up to you to decide which ones go in unstable I guess. > Besides.. for sarge you can use my packages at backports.org which are > always in sync with the packages in sid. Thanks, I didn't know about that. Still, the fact remains that the packages in Debian (including the backports) are not compatible with other distros that use the stable branch. I can't really argue that my friend should change versions, since it makes more sense to me to put the stable branch in a distro. Do they have a "clarification" classification for bugs? This wasn't really a bug, but I probably wasn't the only person wondering. Thanks, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
