This one time, at band camp, Michael Tautschnig said: > > Hi all, > > > > I'd just like to seek some coordination for packaging the new upstream > > release. > > As it wouldn't be the first time I do this, I should manage to get the new > > stuff > > merged in our git repository. I should be able to find some time to do so on > > Saturday, unless someone else steps up and prefers to do it themselves. > > [...] > > It was suggested that I list the steps that it took to get a new release > packaged. I'm using the recipe Stephen gave earlier [1], but some of those > steps need some tweaking. Furthermore, upstream switched to git.
First, thanks for doing the work, and second, thanks for actually
posting the steps to getting it working.
I'm hoping that now that upstream has settled into git a little more
comfortably that we won't need to do quite as many tweaks like this
as we go. Part of the problem so far has been (gitk --all is really
useful for visualizing this sort of thing) that upstream will diverge
from before the current tag to begin working on the next one, so you
end up with graphs like:
HEAD
|
| 0.95.3
debian | /
| | |
0.95.2 | |
\| |
| |
|/
This is very difficult for git to get right, as there is no straight
line fast forward path between 0.95.2 and 0.95.3 (much less from
debian/unstable to upstream/0.95.3).
Cheers,
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : [email protected] |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
signature.asc
Description: Digital signature
_______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-clamav-devel
