> Okay, I used a git snapshot for the version and tarball, and all seems well.
Excellent! that's a very good news.
It's impressive to see all tests to pass from the first attempt. lintian finds
a small issue in the debian/copyright file, but that's all that I see.
https://salsa.debian.org/deb
Okay, I used a git snapshot for the version and tarball, and all seems well.
The reason I'm tracking is because I actually use the generated packages.
But I'm totally unfamiliar with the salsa continuous integration
stuff. Wouldn't mind learning though.
Happy to change workflow, maybe do development on a different branch?
Or, could make snapshot upstream releases 1.0.20+g
Thanks, it helps the salsa pipeline. But it fails right after, because the git
content is too different from the tarball of 1.0.20...
I guess there is no easy way to make this pipeline work before the release of
1.1.0. I tend to think that our issues come from the remote tracking of
upstream's
Done. I reverted to 1.0.20 but left debian/watch untouched, so uscan
alerts about 1.0.20-hotfix being available.
If that's a problem I can edit the watch file, just let me know; I
kind of enjoy tweaking them, as it happens.
Guess now we wait for the actual 1.1.0 release.
I fully agree for not uploading before 1.1.0, so I'd go for the
easiest way to please uscan: probably not -hotfix.
I prefer not to mess with uscan files, as I confess to I kinda dislike
this formalism. But if you insist, I can do.
Mt
--
It is easier to port a shell than a shell script. -- L
Sure, can change it to 1.0.20-hotfix-1 or can edit debian/watch to
skip the -hotfix tag and change it to 1.0.20-1. Or use 1.0.20-1 and
let uscan whine about 1.0.20-hotfix.
Given the changes all around, I don't think we want to actually push
into Debian until 1.1.0 is released anyway. So whether th
Le Mon, Jun 28, 2021 at 12:52:02AM +0100, Barak A. Pearlmutter a écrit :
> There is a pristine-tar branch on both salsa and my GitHub fork repo
I *think* that the issue comes from uscan:
| W: Unable to locate package xournalpp
| Trying uscan --download --download-current-version ...
| uscan warn:
There is a pristine-tar branch on both salsa and my GitHub fork repo
barak/...
Ok, the pipeline is launched. Thanks for the invitation ;)
I would not say that I'm very involved, actually. If I can help, I'm glad, but
if I don't have to, I'm happy :)
If you have difficulties with something, drop me an email.
As for the pipeline, it failed, because it seems that there is no
Sure, always happy for help. Please do!
Would you like to take the package, or co-maintain, team-maintain,
whatever it's called nowadays?
I was using it for teaching, whereas you seem much more involved.
Thanks for the update (and for all the work).
Is it OK if I change what needs to be so that the package gets automatically
built on salsa's CI, with lintian and everything launched on it?
(I'm a DD so I have the technical right to do so, but I'm asking for your
permission anyway)
Thanks, Mt.
Yeah, I think right now it's in good shape. I'm waiting for an
official upstream release, at which point I'll upload.
Since it's not in Debian right now, there's no reason to hold off
until after the Debian release. (If there were I'd upload to
Debian/experimental.)
I've been tracking the upstream
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/-/
14 matches
Mail list logo
