On Tue, 2014-05-27 at 00:39:56 +0200, Guillem Jover wrote: > I agree though, that this is quite suboptimal behavior, and I guess I'll > be changing it to check all applied patches, and failing whenever one of > the patches will fail to apply, which might impose a slight performance > degradation, particularly in packages with either tons of patches, or > huge patches. But I don't think there's any other sane way to improve > the heuristic here, and handle legitimate cases like yours.
Sorry, the logic there was wrong. I'll change the code to try each patch, if the first one applies, then apply them all, otherwise try each other and as long as none applies, ignore that as assuming they are already applied, but if a single patch applies when the previous ones all failed, then abort because there's something fishy. Which should also have no performance impact on the normal case, as unpacking should succeed when applying the first patch. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
