Bug#529160: zita-convolver: FTBFS: dpkg-genchanges: failure: cannot read files list file: No such file or directory

[Reinhard Tartler]

Jaromír Mikeš <mira.mikes at seznam.cz> writes:

> clone git branch will be probably right choice for me.
> Can you please write for me all steps how to do it ... 

First, locate the branch on git.debian.org. Then notice that Free has
created a repository, but without any revisions in it?

Free, could you please check the branch? I guess you missed to type a
git push or something.

> I want to place it here:
> http://wiki.debian.org/DebianMultimedia/DevelopPackaging
> It can be useful for me latter and for other beginners too.

Please see [1] which is a online version of the git-buildpackage
documentation. I've added that to the wiki page.

Moreover, [2] has a short introduction to using git for packaging.

To me, I'm really not sure what would help beginners most. Duplicating
(parts of) the git-buildpackage (or even git) manual leads to too much
maintenance work necessary to keep it up to date, so better would be a
short introduction like [2]. If you find that wiki page helpful, we
should perhaps also link to that as well.

For beginners, I'd suggest the following workflow (I hope that is
wiki-like syntax so that it can easily be copied, please someone review
and copy it to the wiki):

 * locate the packaging branch on http://git.debian.org. All
   pkg-multimedia branches have pkg-multimedia in their url.

 * click on the leftmost link in that line. That will bring you to the
   summary of the project.

 * Note the metadata just above the shortlog, it contains 2 URLs, one of
   them starting with git. E.g. [3] has this link: [4]

 * then git-clone(1) to get a copy of the repository:

   $ git clone git://git.debian.org/pkg-multimedia/jack-audio-connection-kit.git

 * Do changes to that branch, build the package, test your changes, and
   commit early and often! See also the pkg-multimedia development
   policy.

 * If someone else has committed while you are working on the branch,
   you need to integrate his changes. For this you have 2 options:

   - if your local changes are rather minor and clean, use git rebase:

     $ git fetch origin
     $ git rebase origin/master

  - if you rather don't want to break your history because you think
    that your changes are rather large and are likely to interfere with
    the other changes, better merge them with git-pull(1):

    $ git pull origin

 * In case you want to cleanup your local commits before pushing, use
   git-rebase(1):

   $ git rebase -i origin/master

   You will be presented a textfile where you can specify what of your
   local commits you want to modify, drop or squish (merge with the
   previous one). You can also improve your commit message here.

   Make sure that you don't rewrite already published commits.

 * In order to get comments on your (preferably cleaned up) commits, use
   git-format-patch(1) to generate patches of your commits and email
   them to the mailing list. Any committer can do this while preservin
   attribution.

 * None of the steps above require membership in the pkg-multimedia
   alioth group. All of that can be done totally anonymously!

Was that helpful for you?

[1]
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html

[2]
http://wiki.debian.org/PackagingWithGit

[3]
http://git.debian.org/?p=pkg-multimedia/jack-audio-connection-kit.git;a=summary

[4]
git://git.debian.org/pkg-multimedia/jack-audio-connection-kit.git

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4