Hello Barak, I'm glad to see that you are still progressing in the packaging of xournalpp. Last year, you said that the main show stopper was the svg licenses, that were unclear. But if I understand correctly, you fixed it too with the following commit. https://salsa.debian.org/debian/xournalpp/-/commit/c58bef48700738fc05e48bc1d4f61cf3830f708c Now, the debian/copyright file looks good to me. Am I right? Is there anything else that should be done, or are we only waiting for the Debian release before you can upload this package to unstable? How could we help? I have another question about the version of xournalpp that you are packaging. It seems to me that you are tracking upstream master, right? Wouldn't it be preferable to track released versions instead? I'm unsure here as I did not dig into upstream releasing policy, so my first feeling may well be wrong. Finally, would you mind if I change what should be on the repo to activate the automatic build pipelines from https://salsa.debian.org/salsa-ci-team/pipeline ? That would give us the packages as build artefact, so that I can use your version of the package without building locally ;) Thanks for all the good job done here, Mt. -- The great thing about TCP jokes is that you always get them.
Attachment:
signature.asc
Description: PGP signature