In data domenica 17 novembre 2019 13:59:59 CET, Sandro Knauß ha scritto: > thanks for your last update of calligra! That at least makes it build again > *yeah* But for me it seems like, the whole Akonadi dependency isn't used at > all. Sure, it is only checked at cmake time, and apparently not actually used. > Why this is not built and shipped and still we have the dependency? I do not see any akonadi dependency in the binary packages, can you please explain exactly what you see? > calligra is identified as fake candidate (for the moment) every reverse > dependency is built correctly and it is nothing to do left expect for wait > till kdepim will go to testing. > > Just for the record, for thise who are not familiar with the other red > crosses: > libkf5sieve, kf5-messagelib, kmail, libkf5mailcommon and kmail can only be > built for 5 archs, that are supported by qtwebengine. This is because the tracker for the transition is partially wrong: - it considers "affected" all the sources that only build-depend on PIM packages: while this is generally correct, it ought to check both the actual bad _and_ good runtime dependencies instead - the "good" check seems correctly checking for the "new library names" - the "bad" check is basically "everything that does not depend on depend on the new names"... which is wrong -- it ought to explicitly check for the _old_ names instead - also I see whitespaces in all the regexps in the HTML page of the transition -- not sure whether it is actually like that in the ben file, or just a glitch in the HTML page This would explain why: - calligra is considered "bad" - libkf5sieve, kf5-messagelib, kmail, libkf5mailcommon, and kmail are considered "bad" in all the architectures where they are not actually built - maybe (although I'm not sure about this) also all the "?!" states Please fix the ben file for this transition, so its status can be checked properly. -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.