[Pkg-clamav-devel] libclamunrar repo recreated

[Sebastian Andrzej Siewior]

Hi,

Scott noticed that the stable branches are slightly broken. I've thrown
the old repo away (libclamunrar.old.git is still available) and imported
mostly everything from the .dsc files.

Now the reason why stable branches were broken is probably a bad git dpm
work flow on my side and a few attempts to fix it. While importing the
two wheezy release I tried to write everything down the way *I* think it
should be done. If there is a better / recommended way to do so please
don't hesitate and shout at me!

Unstable:
~~~~~~~~~
- git dpm import-new-upstream --rebase ../libclamunrar_0.98.5.orig.tar.xz
- pristine-tar commit ../libclamunrar_0.98.5.orig.tar.xz f00c4e9d974252e8e650ceb96d8b859a5272ff84
- changes
- git dpm tag
 
Next release:
~~~~~~~~~~~~~
- git dpm import-new-upstream --rebase ../libclamunrar_0.99.orig.tar.xz
- pristine-tar commit ../libclamunrar_0.99.orig.tar.xz da1d48dcae97ca642065f1a4b596b8ed79146d98
- changes
- git dpm tag

First backport for wheezy:
~~~~~~~~~~~~~~~~~~~~~~~~~~
- git checkout -b wheezy
- changes
- git dpm tag
 
Next backport for wheezy:
~~~~~~~~~~~~~~~~~~~~~~~~~
- Assuming `upstream-unstable' points to the `libclamunrar_0.99.orig.tar.xz' import:
    git dpm record-new-upstream ../libclamunrar_0.99.orig.tar.xz upstream-unstable
  This will create a new `upstream-wheezy' branch which is identical to the
   `upstream-unstable' branch (that means both have the same commit ID). This is important.
- With patches `git-dpm rebase-patched' is required as the next action.
- once done, `git dpm tag'
     'upstream-0.99' already up to date
     Creating new tag 'patched-0.99-0+deb7u1'...
     Creating new tag 'debian-0.99-0+deb7u1'...
  It only created patched + debian tag because the upstream tag is the same compared to the
  upstream release.

Sebastian