On Thu, Aug 09, 2007 at 01:24:05PM +0200, Goswin von Brederlow wrote: > retitle 435663 Debmirror should guard against too much change severity > important thanks > > Peter Baumann <[EMAIL PROTECTED]> writes: > > > Package: debmirror Version: 20070123 > > > > --- Please enter the report below this line. --- > > > > Sorry. I didn't get the mails from the other people providing > > additional information to this bug. As debuged this with Damyan > > Ivanov (see #435656) and the buggy version of libcompress-zlib-perl > > is no longer available in unstable, I closed this bug. > > > > But after thinking it through, it would still make sense to have the > > conflict or have debmirror depend on libcompress-zlib-perl-2.0005-2 > > > > -Peter > > I don't think a conflict will do any good now. People that have > libcompress-zlib-perl-2.0005-2 installed already did run into the > problem so there is no helping them. And people that don't can't > anymore. > Yes. Thats true. But on the other hand people having the buggy lib already and freshly installing debmirror will get into trouble. A conflict would at least prevent that case.
> But debmirror should guard against a case such as this in generall. I > think debmirror should abort (unless some option is given) if the > mirror grows or shrinks by more than 10%. > > Is 10% a good limit? Maybe limit it to 2GB? What do you think? > I'd prefere an absolut limit like the above mentioned 2GB over a relative limit. If this could be made configurable on the cmdline, this would be best. -Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
