Hi, I have just rebuilt all reverse-dependencies of closure-compiler again, ckbuilder and ckeditor also build fine now. Thus the upload of ckbuilder 2.4.3+dfsg-2 was successful.
> Should we clone this bug to ensure we have a proper (tracking) solution > after the bookworm release. If binaries need rebuilds for new versions > of build dependencies, we need to figure out how we can automatically > detect that. One way (very unpretty) is to hardcode the version which > it's going to be build against, than dose [1] will at least tell us. That's a good idea. In general the Javascript maintainers should be more considerate when it comes to packages like rhino or closure-compiler. The latter has been neglected for ten years but still many Javascript packages depend on it. It is only a matter of time when other issues in closure-compiler will surface. > > > The rebuild should be done after #1036249 in closure-compiler has been > > resolved. > > Which is not the case yet, is the 2.4.3+dfsg-2 upload futile and should > this bug be reopened? (To be safe, I'm reopening now). @yadd If you haven't done so already, could you please file an unblock request for ckbuilder? Thanks Markus
signature.asc
Description: This is a digitally signed message part
