Fwd: gmerlin-avdecoder_1.0.1-2_amd64.changes REJECTED

Reinhard Tartler siretart at tauware.de
Thu Dec 3 08:55:33 UTC 2009

fabrice <coutadeurf at gmail.com> writes:

> I'm almost done with the copyright, but the lib/libwin32dll directory is
> a copyright nightmare: code 'stolen' from other projects (this is what
> is written in the source code of one source :-/), no copyright header in
> most of the files, ...
> As it seems to be a windows only part of the application, I really think
> we can and should get rid of it to get gmerlin-avdecoder accepted.
> What do  you think about it?
> Also, how can be the repack part achieved with git? Or should I generate
> by my own repack source tarball, as usual?

I suggest the following procedure (untested, might need improvement):

 - git checkout upstream
 - do necessary changes (e.g. version bump), file removals, etc. as needed
 - commit
 - from this commit, create a new tarball in '..'. git-archive(1) might
   be helpful for this
 - Optionally, use 'pristine-tar commit ../newtarball' to collect
   pristine-tar data
 - git checkout master
 - bump debian/changelog for new version number of the tarball
 - git push origin upstream pristine-tar --tags
   (basically ensure that the new commits in the 'upstream' and
   'pristine-tar' branches are published on git.debian.org

Using pristine-tar for repacked branches might seem overkill, but using
it anyway has IMO the following advantages:

 * our team documentation and workflow remains consistent with branches
   that do use pristine-tar.

 * less communication overhead for questions like "did you really want no
   pristine-tar data or did you just forget to push your branches?".

Reinhard Tartler, KeyID 945348A4

More information about the pkg-multimedia-maintainers mailing list