Hello Joerg,

Joerg Jaspert [2017-03-09  9:18 +0100]:
> > So I'm looking for advice from you: would you rather have an inline copy of
> > COPYING.bower? Is it acceptable/preferrable to generate this during package
> > build from COPYING.bower with some seddery, or would you rather have a 
> > static
> > snapshot in the source?
> 
> Yes, Debian wants it in the copyright file.
> [..]
> Unlike the control file, which you must not rebuild during a package
> build, we don't much care how the copyright file gets created. So do
> what works for you, as long as it is the one source of truth (and, for
> those folks over there, reproducible :) ).

Ack. Manually keeping it up to date is not realistically going to be precise
(I've seen to many grossly out of date copyright files for large packages), so
I wrote a script [1] to generate debian/copyright from a .template and
machine-inspecting bower_components/* and parsing out licenses and copyrights
from those. It still requires some manual cleanup afterwards [2], but provides
a good basis. So this is meant to run manually for a new upstream release, so I
refrained from calling it during package build.

Unfortunately I uploaded a package without the manual cleanup of the copyright
file [2], so can you please reject the current upload and I upload the right
one?

Thanks, and sorry for the trouble,

Pitti

[1] 
https://anonscm.debian.org/cgit/collab-maint/cockpit.git/commit/?id=e9eb287b1a
[2] 
https://anonscm.debian.org/cgit/collab-maint/cockpit.git/commit/?id=13f2400074

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to