This problem seems to have been "fixed" by modifying the conffile in sid to be the same as the one in sarge. This isn't a very good solution, because you might decide that you actually want to both change the contents of the conffile between stable releases, and change the package owning the conffile. But anyway.
I'm not going to close this bug, on the premise that this is the maintainers responsibility, and they should really bother to respond to their bugs (even if they are not "release critical"), and care if their package is in testing or not. Just for fun, I looked at the binary packages generated by cupsys2 which contain client.conf: 2031324435f8f317fdfcc39dfa0fe333 libcupsys2-gnutls10_1.1.23-10_i386.deb 2031324435f8f317fdfcc39dfa0fe333 libcupsys2-gnutls10_1.1.23-10sarge1_i386.deb 2031324435f8f317fdfcc39dfa0fe333 libcupsys2_1.1.23-12_i386.deb 2031324435f8f317fdfcc39dfa0fe333 libcupsys2_1.1.23-15_i386.deb 2031324435f8f317fdfcc39dfa0fe333 libcupsys2_1.1.99.b1.r4885-1_i386.deb 6626b6c3efff30870b7f92e495c299fc libcupsys2_1.1.14-5woody12_i386.deb Steve, were you able to reproduce this bug? It seems to me that this is a woody-only problem (well, sarge actually, since thats where the fix would be required). I don't know what was the contents of that file between -10 and -12, since -10 was the *week after* snapshot's disk lost information, and snapshot gives me permissions errors for -12 (and everything else) anyway. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
