Hello Aurelien :-)
For the integration of Ghostwriter in the scope of the Qt/KDE packaging
team, I agree, no worries, I also had the case at openSUSE and I'm looking
how I could in the following days, pass all that on to Debian as well.
As for gitlab, I have trouble communicating with it, I can't even do that
from my terminal anymore, I have a legal problem, so I do everything from
the risky web interface. I more or less gave up on the git business. But I
will give you the rights.
I haven't worked with the repository long enough, I work directly from home
and a folder. I would like to help in other packages but again I stumble on
the use of gitlab.
I'll try to free up time to make the changes but it's not said. I don't
have any Debian around right now.
Best regards.
Le mar. 20 déc. 2022 à 13:30, Aurélien COUDERC <li...@coucouf.fr> a écrit :
> Le mercredi 12 octobre 2022, 11:41:50 CET Sebastien Chavaux a écrit :
> > Absolutely, I'm so in my head that I don't see what is the simplest...
>
> Dear Sebastien,
>
> as Ghostwriter has been onboarded as a KDE Project, I’d like to offer to
> integrate the package into the perimeter of the Qt/KDE Packaging Team.
>
> We have an « extras » group [0] for packages that are related to KDE but
> not part of the main KDE Frameworks / Plasma / Gear releases that I think
> would be suitable.
>
> How we would do this is :
> - give me (couc...@debian.org) or one of the team members owner access to
> your packaging repo so we can move it to the qt-kde-team/extras group
> - change the Maintainer field to : Debian KDE Extras Team <
> pkg-kde-ext...@alioth-lists.debian.net>
> - put yourself in the Uploaders field
>
> What you would get :
> - you keep your usual access to the repo and can work on the package as
> you used to
> - team members and myself would be considered welcome to contribute to
> that repository too
> - it would gives additional scrutiny to the package that would show on our
> DDPO dashboard
> - you’re welcome to help on other packages of the team :)
>
> Whether you’re interested or not, you’re welcome to hang out on the
> #debian-qt-kde on Debian’s IRC for help and feedback or upload sponsorship.
>
>
> To follow up on the RFS discussion:
> - MathJax3 is currently not packaged so it’s fine to keep it vendored
> (3rdparty) for now. We can migrate to the Debian package once it’s
> available.
> - The source-is-missing lintian tags are false positives to me (if lintian
> still really emits them, I haven’t checked). The folders
> 3rdparty/{MathJax,react} contain valid, human modifiable source files.
> Please add a comment in the lintian-overrides file to explain so.
> - You should use the Files-Excluded directive in debian/copyright [1] to
> describe which files should be removed from the upstream source. That
> should be the debian/ folder + 3rd party libraries already available in
> Debian.
> - I would prefer the +ds suffix instead of +dfsg, +dfsg is more
> appropriate for cases where we remove upstream sources due to licensing
> concerns which is not the case here IIUC.
> - uscan --download-current-version fails, it should work from a clean
> clone of the repo (the uupdate is not required unless I’m missing
> something), and…
> - it would be preferable for debian/watch to target the invent.kde.org
> repo which is now the reference repo, you have examples for GitLab tags
> here [2].
> - In the git packaging repo you have the « source » folder next to the
> « debian » folder, it should be *inside* it.
> - source/options can be removed.
> - Remove debian/compat and replace the debhelper (>= 11) build dependency
> by a debhelper-compat (= 13) build dep.
> - Remove debian/git-build-recipe.manifest ? I don’t know what it’s for so
> it’s probably not useful. :)
>
>
> Feel free to ping me or the team on IRC about any of the above.
>
>
> [0] https://salsa.debian.org/qt-kde-team/extras
> [1] https://wiki.debian.org/UscanEnhancements
> [2] https://wiki.debian.org/debian/watch#Gitlab
>
>
> Thanks for your response & cheers,
> --
> Aurélien, on behalf of the Qt/KDE Packaging Team
>
>
>
