Bug#425928: bug closing?
Gerfried Fuchs [EMAIL PROTECTED] (27/09/2007): Hi! Lo! As this is not a bug in slony itself and a build was uploaded to work around this problem (it's now in sync on all archs) and the actual bug lies in a different package - can we close this bugreport so that the package can transition to testing? I can't see any “work around” in either slony1's changelog, and the blocking bug isn't fixed, so I can't tell. But if a later version of slony1 includes a workaround (w/o mentioning it in its changelog), I guess just closing this bug with that version is fine. Cheers, -- Cyril Brulebois pgp3Ni6ka0ul7.pgp Description: PGP signature
Bug#425928: bug closing?
* Cyril Brulebois [EMAIL PROTECTED] [2007-09-30 09:03:00 CEST]: Gerfried Fuchs [EMAIL PROTECTED] (27/09/2007): As this is not a bug in slony itself and a build was uploaded to work around this problem (it's now in sync on all archs) and the actual bug lies in a different package - can we close this bugreport so that the package can transition to testing? I can't see any “work around” in either slony1's changelog, and the blocking bug isn't fixed, so I can't tell. There is no need for a workaround in slony because this is no slony bug. Please read it up again, thanks. But if a later version of slony1 includes a workaround A workaround for a breakage that isn't in slony's scope? If we are going to incorporate workarounds for breakages in parts that aren't really related the whole archive will be filled with such workarounds - they are of no help in the long term, just unneeded bloat. So long, Rhonda
Bug#425928: bug closing?
Hi! As this is not a bug in slony itself and a build was uploaded to work around this problem (it's now in sync on all archs) and the actual bug lies in a different package - can we close this bugreport so that the package can transition to testing? Just curious, Rhonda -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
