On 22 January 2017 at 13:53, Christoph Biedl <debian.a...@manchmal.in-ulm.de> wrote: > Christoph Biedl wrote... > >> Good to hear. Ping me if I should test a few things before you NMU - and >> I shouldn't have to remind you there's not too much time left to get a >> fresh nikola into stretch. > > With no additional input and just some three days left to resolve the > issue, I wasted several hours trying to provide a solution on my own, > basically by reverting the changes in resize_image mostly. The > .gitignore covering *.patch took an extra hour, some glitches in the > documentation (it's appearently ".. image", not "..image") disturbed me > as well. Now I'm caught by some python stack traces I fail to > understand. Also there is a need for configuration upgrade instructions > I did not find and certainly lack the competence to create. > > Therefore, I hereby I give up. Trying to salvage nikola for stretch, and > using nikola at all. It's not funny to see each static blog compiler I > try goes boom instantly. It's been nanoblogger, then chronicle, now > nikola. Let's see how hugo does.
Nikola isn’t to blame here. We write our software with an assumption that hard dependencies will be always present. If you are trying to work around that, you’re going to make things harder for yourself. And Nikola is not alone in this: all software is written with the assumption that some hard dependencies must be installed for it to work, and if you don’t install them, it will crash. This entire debacle is caused by Debian policy — and do you think you would IMPROVE things by ripping out features at random? How would you re-implement the missing parts we use piexif for? Would Debian’s package have different output than upstream code? That isn’t better than running around with an ancient version. We’ve already fought over this when Debian made an equally arbitrary decision to remove our bootstrap3 themes. Feel free to delete Nikola from stretch. And if you believe you do not have the resources to do it in testing/sid in the future, it’s better to have no package than a horribly outdated or broken/incompatible one — just make sure to let the users of this package know that they should remove it and use a different install method if that’s what you’re going for. -- Chris Warrick <https://chriswarrick.com/> PGP: 5EAAEA16
