Hi, Quoting Sam Hartman (2014-10-07 13:30:52) > These still aren't in a state wwhere both patches can be applied right?
correct. #763766 is blocked by debhelper while #752409 is blocked by debhelper and the Jessie release. > I wonder whether it would be better to close these bugs and open new > bugs when you're actually in a position that applying a complete patch > would be useful to you and would not break the package working with dak, > debhelper or anything else? We opened the bugs to track this issue with krb5. At any time where either of the two bugs was not blocked by another, it would've been okay to apply them to krb5 without breaking something. This was the case for at least #763766 for a while. Since #763766 was not yet resolved I posted a follow-up patch which makes use of not-yet-merged debhelper functionality. If it would mean you'd apply the patch earlier, then I can follow up on #763766 with a patch that doesn't require a newer debhelper version. Originally two bugs were filed because at some point in time, one (#763766) was resolvable immediately while the other (#752409) had to wait until #744246 was resolved. Now we know that #744246 will only be resolved once Jessie is released. If you want to wait with applying anything until Jessie is released, then I think it makes sense to close #763766 and keep #752409 open. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
