Page MenuHomeLubuntu Development

New lxqt-build-tools version 0.8.0

Authored by apt-ghetto on Nov 26 2020, 1:30 PM.



Package new upstream version 0.8.0 of lxqt-build-tools

Test Plan

Build it with schroot and check, that the build does not fail

Diff Detail

rLXQTBUILDTOOLSPACKAGING lxqt-build-tools Packaging
No Linters Available
No Unit Test Coverage
Build Status
Buildable 214
Build 214: arc lint + arc unit

Event Timeline

apt-ghetto created this revision.
kc2bez requested changes to this revision.Nov 29 2020, 6:50 PM

One tiny question in-line on the copyright. Once that is answered it looks ok to proceed.


I'm not sure about this change since Alf didn't actually modify anything here since 2019. @tsimonq2 is that correct?

This revision now requires changes to proceed.Nov 29 2020, 6:50 PM
In D103#2197, @kc2bez wrote:

One tiny question in-line on the copyright. Once that is answered it looks ok to proceed.

Yes, I was not sure and would appreciate more detailed instructions on the copyright handling. I was checking the diff between 0.7.0 and the master branch and did not see any changes related to copyright. But maybe there are better ways to do it.

I guess, it makes also more sense to upload it first to the Debian archives?


Of course don't we actually make changes relative to the Debian files? If that's the case, maybe leave Alf's copyright but add ours from whenever we started packaging.

@apt-ghetto @tsimonq2 and @teward both agree that we should not change the Debian copyright. However, we should add in ours where needed.

We should probably make a little less of a fuss about copyright going forward. Kubuntu, like us, has a tendency to package from upstream and rely less on the merges. Asking there, they say that ideally the copyrights would get updated in those cases, but in practice, no. For packages not regulated to a flavor packageset, even where packaging changes are made to resolve merge conflicts, I think it's uncommon to see copyright changes. That said, I don't think we need to worry about this. Sorry for all the hassle, @apt-ghetto.