[Pkg-samba-maint] OpenChange packages: looking for a review and sponsorship

[Jelmer Vernooij]

On Tue, Jun 17, 2008 at 08:27:19PM -0700, Steve Langasek wrote:
> On Tue, Jun 17, 2008 at 10:05:53PM +0200, Jelmer Vernooij wrote:
> > Am Dienstag, den 17.06.2008, 12:12 -0700 schrieb Steve Langasek:

> > > > Uploaders: Jelmer Vernooij <jelmer at samba.org>
> > > > Build-Depends: debhelper (>> 5.0.0), libparse-pidl-perl, libmagic-dev,
> > > > libdcerpc-dev, libtalloc-dev, libldb-samba4-dev, samba4-dev
> > > > Standards-Version: 3.8.0
> > > > Vcs-Svn: svn://svn.debian.org/pkg-samba/trunk/openchange

> > > ... is it worth me asking for a pkg-samba bzr repo?  I wonder if it really
> > > makes sense to push new packages into svn.  What's the upstream VCS for
> > > openchange?
> > +1! though I don't have much problems with the current setup; bzr
> > builddeb + bzr-svn also work fine with it.
> One thing I found when trying out bzr-svn was that the log entries visible
> from native svn clients seemed to be limited to whatever message was used
> when pushing to that branch; so using bzr for offline commits and then
> pushing with bzr-svn makes collaboration with svn users harder than just
> using svn directly.
I'm not sure I understand what you mean here. If you do some offline
commits and then push them once you come online all of the commit
messages will end up in "svn log".  Right hand side revisions of
merges are not pushed into Subversion because it has no way of
representing them. This last bit is likely to be fixed with the next
version of bzr-svn (and Subversion 1.5).

> Likewise, bzr of course makes it very, very easy to
> merge between branches (including bzr-svn branches), but AFAICS it doesn't
> make it very easy to find the svn revision ids corresponding to the contents
> of a merge - which means that the (horrid, and yet) traditional method of
> tracking svn merges, by annotating the merge state via commit messages,
Not sure what you mean here. Merging between svn branches using
bzr-svn works exactly the same way as merging between bzr branches, no
need to remember revision ids - bzr-svn tracks what has been merged
and what hasn't in file properties.

Cheers,

Jelmer